Re: SIMPLE and Emergency Services
"DRAGE, Keith (Keith)" <[email protected]> Thu, 1 Nov 2012 19:40:11 +0100
| Newsgroups | gmane.ietf.simple |
|---|---|
| Message-ID | <EDC0A1AE77C57744B664A310A0B23AE202D2F6F6E3@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> |
--===============1380200587218306309== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_EDC0A1AE77C57744B664A310A0B23AE202D2F6F6E3FRMRSSXCHMBSC_" --_000_EDC0A1AE77C57744B664A310A0B23AE202D2F6F6E3FRMRSSXCHMBSC_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable As regards presence usage in 3GPP, my statement about presence related to e= mergency usage only. As a capability, 3GPP specified presence in release 6, in 3GPP TS 24.141. T= his is an endorsement of IETF SIMPLE documents with the minor exception of = collection of presence information about the user using existing 3GPP inter= nal interfaces (e.g. status from HSS, location from GMLC), which are then a= dapted into SIMPLE protocols. OMA subsequently specified their stuff which enhances and expands on IETF S= IMPLE. TISPAN took the 3GPP presence usage, but took the OMA XDM stuff to cover th= e list management. GSMA took the OMA documents to create RCS. Operators could be deploying any of this, but I suspect they are using RCS = primarily. And as said, none of this applies to emergency call to my knowledge, except= possibly in the context of the PSAP being a normal user and being able to = watch with those capabilities. Keith ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of= Olle E. Johansson Sent: 01 November 2012 18:27 To: DRAGE, Keith (Keith) Cc: Bernard Aboba; [email protected] Subject: Re: [Simple] SIMPLE and Emergency Services 1 nov 2012 kl. 16:44 skrev "DRAGE, Keith (Keith)" <keith.drage@alcatel-luce= nt.com<mailto:[email protected]>>: Release 11 of 3GPP IMS specifications add session based media to emergency = call usage in addition to voice and real time text. For messaging, that inc= ludes MSRP. While many countries are trying to ensure that PSAPs can handle SMS (which = is not session based), this needs to be regarded as something that exists w= here nothing else does - as it provides the responder with no ability to in= terrogate the user to obtain more information. For presence, nothing special has been specified by 3GPP. Keith, Please guide me through this. Is 3gpp not using the OMA specs? For me that is classified as "special" and not part of the IETF specs. :-) If not, have 3gpp tested interoperability of SIMPLE across vendors? The abi= lity to add buddies and share buddy lists, regardless of client? Just curio= us of the process. /O Keith ________________________________ From: [email protected]<mailto:[email protected]> [mailto:simpl= [email protected]<mailto:[email protected]>] On Behalf Of Bernard Aboba Sent: 31 October 2012 22:08 To: [email protected]<mailto:[email protected]> Subject: Re: [Simple] SIMPLE and Emergency Services In response to Olle's question about whether SIMPLE is an abject and irrede= emable failure, I would note that SIMPLE is still under consideration for = use in emergency services, if only because XMPP isn't yet a viable alternat= ive. For example, both NENA i3 and ECRIT PhoneBCP mention SIMPLE, but refer= to XMPP support of emergency services as future work. In emergency scenari= os, presence and address books are typically not considered since the PSAP = is neither a presentity nor a watcher. Instead, SIMPLE is used as a way of= conveying information between the caller and PSAP, including location, a m= essage body and additional data. With SMS to 911 under active discussion with regulatory bodies, the questio= n about whether we can rely on SIMPLE for emergency use has become a "hot i= ssue". As an example, there has been a suggestion that MESSAGE could be use= d to support conveyance of SMS text messages to a "text gateway" that would= then pass them on to the PSAP (possibly in a different form, such as trans= lating to TTY/TDD). Not only might this help standardize the transport of = SMS messages to 911, but it would also support future uses of MESSAGE for n= ext generation emergency services. While documents like NENAi3 and ECRIT PhoneBCP still point to SIMPLE specs,= some folks have pointed to the lack of support for MESSAGE in SIP trunking= services as an indication that even basic uses of SIMPLE are unlikely to s= ee much deployment, and that alternatives for disabled access to emergency = services (such as RFC 4103 realtime text) should be given priority. IMHO, unless XMPP for emergency uses is specified by IETF in the near futur= e, it is likely that SIMPLE will find its way into emergency services archi= tectures in some form. Since the IETF is still recommending SIMPLE in docum= ents such as ECRIT PhoneBCP, IMHO the IETF has a responsibility to public s= afety to address interop issues that will arise in next generation emergenc= y services scenarios. AFAIK, SIMPLE interop issues haven't killed anyone ye= t. Hopefully this will remain true in the future. Olle E. Johansson said: "Any other thoughts in regards to SIMPLE? Is it a failure or not? Do we have a chance of fixing this within the IETF? Is anyone interested in fixing it so we actually reach the WG goal of inter= operability?" _______________________________________________ Simple mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/simple --_000_EDC0A1AE77C57744B664A310A0B23AE202D2F6F6E3FRMRSSXCHMBSC_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"> <meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)"> <base href=3D"x-msg://17/"> <!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--> <style> <!-- /* Font Definitions */ @font-face {font-family:Helvetica; panose-1:2 11 6 4 2 2 2 2 2 4;} @font-face {font-family:"MS Mincho"; panose-1:2 2 6 9 4 2 5 8 3 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:"\@MS Mincho"; panose-1:0 0 0 0 0 0 0 0 0 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman";} h1 {mso-margin-top-alt:auto; margin-right:0cm; mso-margin-bottom-alt:auto; margin-left:0cm; font-size:24.0pt; font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {color:blue; text-decoration:underline;} pre {margin:0cm; margin-bottom:.0001pt; font-size:10.0pt; font-family:"Courier New";} span.EmailStyle19 {mso-style-type:personal-reply; font-family:Arial; color:navy;} @page Section1 {size:595.3pt 841.9pt; margin:72.0pt 90.0pt 72.0pt 90.0pt;} div.Section1 {page:Section1;} --> </style> </head> <body lang=3DEN-GB link=3Dblue vlink=3Dblue style=3D'word-wrap: break-word;= -webkit-nbsp-mode: space; -webkit-line-break: after-white-space'> <div class=3DSection1> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'>As regards presence usage in 3GPP, my statement about presence related to emergency usage only.<o:p></o:p></span>= </font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'>As a capability, 3GPP specified presen= ce in release 6, in 3GPP TS 24.141. This is an endorsement of IETF SIMPLE documents with the minor exception of collection of presence information ab= out the user using existing 3GPP internal interfaces (e.g. status from HSS, location from GMLC), which are then adapted into SIMPLE protocols.<o:p></o:= p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'>OMA subsequently specified their stuff which enhances and expands on IETF SIMPLE.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'>TISPAN took the 3GPP presence usage, b= ut took the OMA XDM stuff to cover the list management.<o:p></o:p></span></fon= t></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'>GSMA took the OMA documents to create = RCS.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'>Operators could be deploying any of th= is, but I suspect they are using RCS primarily.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'>And as said, none of this applies to emergency call to my knowledge, except possibly in the context of the PSAP being a normal user and being able to watch with those capabilities.<o:p></= o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'>Keith<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm = 4.0pt'> <div> <div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz= e=3D3 face=3D"Times New Roman"><span lang=3DEN-US style=3D'font-size:12.0pt'> <hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1> </span></font></div> <p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span>= </font></b><font size=3D2 face=3DTahoma><span lang=3DEN-US style=3D'font-size:10.0pt;font-fa= mily:Tahoma'> [email protected] [mailto:[email protected]] <b><span style=3D'font-weight:bold'>On Behalf Of </span></b>Olle E. Johansson<br> <b><span style=3D'font-weight:bold'>Sent:</span></b> 01 November 2012 18:27= <br> <b><span style=3D'font-weight:bold'>To:</span></b> DRAGE, Keith (Keith)<br> <b><span style=3D'font-weight:bold'>Cc:</span></b> Bernard Aboba; simple@ie= tf.org<br> <b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [Simple] SIMPLE= and Emergency Services</span></font><span lang=3DEN-US><o:p></o:p></span></p> </div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'><o:p> </o:p></span></font></p> <div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'>1 nov 2012 kl. 16:44 skrev "DRAGE, Keith (Keith)" <<a href=3D"mailto:[email protected]">[email protected]= om</a>>:<o:p></o:p></span></font></p> </div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'><br> <br> <o:p></o:p></span></font></p> <div link=3Dblue vlink=3D"#606420" style=3D'orphans: 2;text-align:-webkit-a= uto; widows: 2;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px; word-spacing:0px'> <div> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'>Release 11 of 3GPP IMS specifications = add session based media to emergency call usage in addition to voice and real t= ime text. For messaging, that includes MSRP.<u1:p></u1:p></span></font><o:p></o= :p></p> </div> <div> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'> </span></font><o:p></o:p></p> </div> <div> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'>While many countries are trying to ens= ure that PSAPs can handle SMS (which is not session based), this needs to be regarded as something that exists where nothing else does – as it provides the responder with no ability to interrogate the user to obtain mo= re information.<u1:p></u1:p></span></font><o:p></o:p></p> </div> <div> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'> </span></font><o:p></o:p></p> </div> <div> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'>For presence, nothing special has been specified by 3GPP.</span></font><o:p></o:p></p> </div> </div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'>Keith,<o:p></o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'>Please guide me through this. Is 3gpp not using the OMA specs? = ;<o:p></o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'>For me that is classified as "special" and not part of th= e IETF specs. :-)<o:p></o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'>If not, have 3gpp tested interoperability of SIMPLE across vendors?= The ability to add buddies and share buddy lists, regardless of client? Just curious of the process.<o:p></o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'>/O<o:p></o:p></span></font></p> </div> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'><br> <br> <o:p></o:p></span></font></p> <u1:p></u1:p> <div link=3Dblue vlink=3D"#606420" style=3D'orphans: 2;text-align:-webkit-a= uto; widows: 2;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px; word-spacing:0px'> <div> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'> </span></font><o:p></o:p></p> </div> <div> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'>Keith<u1:p></u1:p></span></font><o:p><= /o:p></p> </div> <div> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style= =3D'font-size: 10.0pt;font-family:Arial;color:navy'> </span></font><o:p></o:p></p> </div> <div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm = 4.0pt'> <div> <div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz= e=3D3 face=3D"Times New Roman"><span lang=3DEN-US style=3D'font-size:12.0pt'> <hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1> </span></font></div> <div> <p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span>= </font></b><span class=3Dapple-converted-space><font size=3D2 face=3DTahoma><span lang=3DEN-= US style=3D'font-size:10.0pt;font-family:Tahoma'> </span></font></span><f= ont size=3D2 face=3DTahoma><span lang=3DEN-US style=3D'font-size:10.0pt;font-fa= mily:Tahoma'><a href=3D"mailto:[email protected]"><font color=3D"#606420"><span style=3D'color:#606420'>[email protected]</span></font></a><span class=3Dapple-converted-space> </span>[mailto:simple-<a href=3D"mailto:[email protected]"><font color=3D"#606420"><span style=3D'col= or:#606420'>[email protected]</span></font></a>]<span class=3Dapple-converted-space> </span><b><span style=3D'font-weight:bo= ld'>On Behalf Of<span class=3Dapple-converted-space> </span></span></b>Bernar= d Aboba<br> <b><span style=3D'font-weight:bold'>Sent:</span></b><span class=3Dapple-converted-space> </span>31 October 2012 22:08<br> <b><span style=3D'font-weight:bold'>To:</span></b><span class=3Dapple-converted-space> </span><a href=3D"mailto:[email protected]= g"><font color=3D"#606420"><span style=3D'color:#606420'>[email protected]</span></fon= t></a><br> <b><span style=3D'font-weight:bold'>Subject:</span></b><span class=3Dapple-converted-space> </span>Re: [Simple] SIMPLE and Emergenc= y Services</span></font><o:p></o:p></p> </div> </div> <u1:p></u1:p> <div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'> <o:p></o:p></span></font></p> </div> <div> <h1><b><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-f= amily: Calibri;font-weight:normal'>In response to Olle's question about whether SI= MPLE is an abject and irredeemable failure, I would note that SIMPLE is st= ill under consideration for use in emergency services, if only because XMPP isn= 't yet a viable alternative.<span class=3Dapple-converted-space> </span><= /span><span style=3D'white-space:pre-wrap'></font></b><font size=3D3 face=3DCalibri><sp= an style=3D'font-size:12.0pt;font-family:Calibri'>For example, both NENA i3 an= d ECRIT PhoneBCP mention SIMPLE, but refer to XMPP support of emergency servi= ces as future work. In emergency scenarios, presence and address books are typically not considered since the PSAP is neither a presentity nor a watcher. Instead, SIMPLE is used as a way of conveying information between the caller and PSAP, including location, a message body and additio= nal data. </span></span></font><o:p></o:p></h1> <u1:p></u1:p> <div> <div> <p class=3DMsoNormal><font size=3D3 face=3DCalibri><span style=3D'white-spa= ce:pre-wrap'><span style=3D'font-size:12.0pt;font-family:Calibri'>With SMS to 911 under active discussion with regulatory bodies, the question about whether we can rely o= n SIMPLE for emergency use has become a "hot issue". As an example, there has been a suggestion that MESSAGE could be used to <span style=3D'white-space:pre-wrap'>support conveyance of SMS text messages to a "text gateway" that would then pass them on to the PSAP (possibly= in a different form, such as translating to TTY/TDD). Not only might thi= s help standardize the transport of SMS messages to 911, but it would also support future uses of MESSAGE for next generation emergency services. </sp= an></span><u1:p></u1:p></span></font><o:p></o:p></p> </div> </div> <div><span style=3D'white-space:pre-wrap'> <div> <p class=3DMsoNormal><font size=3D3 face=3DCalibri><span style=3D'font-size= :12.0pt; font-family:Calibri'><br> <br> <br> </span></font><o:p></o:p></p> </div> </div> <u1:p></u1:p> <div> <div> <p class=3DMsoNormal><font size=3D3 face=3DCalibri><span style=3D'font-size= :12.0pt; font-family:Calibri'>While documents like NENAi3 and ECRIT PhoneBCP still p= oint to SIMPLE specs, some folks have pointed to the lack of support for MESSAGE= in SIP trunking services as an indication that even basic uses of SIMPLE are unlikely to see much deployment, and that alternatives for disabled access = to emergency services (such as RFC 4103 realtime text) should be given priorit= y. </span><u1:p></u1:p></font><o:p></o:p></p> </div> </div> </span> <div><span style=3D'white-space:pre-wrap'> <div> <p class=3DMsoNormal><font size=3D3 face=3DCalibri><span style=3D'font-size= :12.0pt; font-family:Calibri'><br> <br> <br> </span></font><o:p></o:p></p> </div> </div> <u1:p></u1:p> <div> <div> <p class=3DMsoNormal><font size=3D3 face=3DCalibri><span style=3D'font-size= :12.0pt; font-family:Calibri'>IMHO, unless XMPP for emergency uses is specified by I= ETF in the near future, it is likely that SIMPLE will find its way into emergen= cy services architectures in some form. Since the IETF is still recommending SIMPLE in documents such as ECRIT PhoneBCP, IMHO the IETF has a responsibil= ity to public safety to address interop issues that will arise in next generati= on emergency services scenarios. AFAIK, SIMPLE interop issues haven't killed anyone yet. Hopefully this will remain true in the future. </span><u1:p></u= 1:p></font><o:p></o:p></p> </div> </div> </span> <div> <div> <p class=3DMsoNormal><font size=3D3 face=3DCalibri><span style=3D'white-spa= ce:pre-wrap'><span style=3D'font-size:12.0pt;font-family:Calibri'><br> <br> <br> </span></font><o:p></o:p></p> </div> </div> <u1:p></u1:p></span> <div><span style=3D'white-space:pre-wrap'> <div> <p class=3DMsoNormal><font size=3D3 face=3DCalibri><span style=3D'font-size= :12.0pt; font-family:Calibri'>Olle E. Johansson said: </span><u1:p></u1:p></fon= t><o:p></o:p></p> </div> </div> </span><pre style=3D'white-space:pre-wrap;word-wrap: break-word'><font size= =3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri'>"A= ny other thoughts in regards to SIMPLE?<u1:p></u1:p></span></font><o:p></o:= p></pre><pre><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '> </span></font><o:p></o:p></pre><pre><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '>Is it a failure or not?<u1:p></u1:p></span></font><o:p></o:p></pre><pre><= font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '> </span></font><o:p></o:p></pre><pre><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '>Do we have a chance of fixing this within the IETF?<u1:p></u1:p></span></= font><o:p></o:p></pre><pre><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '> </span></font><o:p></o:p></pre><pre><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '>Is anyone interested in fixing it so we actually reach the WG goal of int= eroperability?"<u1:p></u1:p></span></font><o:p></o:p></pre><pre><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '> </span></font><o:p></o:p></pre><pre><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '> </span></font><o:p></o:p></pre></div> </div> <p class=3DMsoNormal><font size=3D4 face=3DHelvetica><span style=3D'font-si= ze:13.5pt; font-family:Helvetica'>_______________________________________________<br> Simple mailing list<br> <a href=3D"mailto:[email protected]"><font color=3D"#606420"><span style=3D'c= olor:#606420'>[email protected]</span></font></a><br> <a href=3D"https://www.ietf.org/mailman/listinfo/simple"><font color=3D"#60= 6420"><span style=3D'color:#606420'>https://www.ietf.org/mailman/listinfo/simple</span>= </font></a><o:p></o:p></span></font></p> </div> </div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D= 'font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> </div> </body> </html> --_000_EDC0A1AE77C57744B664A310A0B23AE202D2F6F6E3FRMRSSXCHMBSC_-- --===============1380200587218306309== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Simple mailing list [email protected] https://www.ietf.org/mailman/listinfo/simple --===============1380200587218306309==--