Re: SIMPLE and Emergency Services
"DRAGE, Keith (Keith)" <[email protected]> Thu, 1 Nov 2012 16:44:28 +0100
| Newsgroups | gmane.ietf.simple |
|---|---|
| Message-ID | <EDC0A1AE77C57744B664A310A0B23AE202D2F6F6A9@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> |
--===============2927064636604831185== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_EDC0A1AE77C57744B664A310A0B23AE202D2F6F6A9FRMRSSXCHMBSC_" --_000_EDC0A1AE77C57744B664A310A0B23AE202D2F6F6A9FRMRSSXCHMBSC_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of= Bernard Aboba Sent: 31 October 2012 22:08 To: [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?" --_000_EDC0A1AE77C57744B664A310A0B23AE202D2F6F6A9FRMRSSXCHMBSC_ 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)"> <!--[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:"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"; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {color:#606420; text-decoration:underline;} p {mso-margin-top-alt:auto; margin-right:0cm; mso-margin-bottom-alt:auto; margin-left:0cm; font-size:12.0pt; font-family:"Times New Roman";} 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=3D"#606420"> <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'>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.<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'>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.<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'>For presence, nothing special has been specified by 3GPP.<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>Bernard Aboba<br> <b><span style=3D'font-weight:bold'>Sent:</span></b> 31 October 2012 22:08<= br> <b><span style=3D'font-weight:bold'>To:</span></b> [email protected]<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> <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><span style=3D'white-space:pre-wrap'>For example, both NENA i3 and ECRIT PhoneBCP mention SIMPLE, but refer to XMPP support of emergency services as future work. In emergency scenarios, prese= nce 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 conveyi= ng information between the caller and PSAP, including location, a message body= and additional data. </span></span></font></b><font face=3DCalibri><span style=3D'font-family:Calibri'><o:p></o:p></span></font></h1> <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><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><o:p></o:p></span></font></p> </div> <div><span style=3D'white-space:pre-wrap'> <p class=3DMsoNormal><font size=3D3 face=3DCalibri><span style=3D'font-size= :12.0pt; font-family:Calibri'><br> <br> <o:p></o:p></span></font></p> </div> </span> <div><span style=3D'white-space:pre-wrap'> <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><o:p></o:p></span></font></p> </div> <div><span style=3D'white-space:pre-wrap'> <p class=3DMsoNormal><font size=3D3 face=3DCalibri><span style=3D'font-size= :12.0pt; font-family:Calibri'><br> <br> <o:p></o:p></span></font></p> </div> </span> <div><span style=3D'white-space:pre-wrap'> <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><o:p></o:= p></span></font></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'><br> <br> <o:p></o:p></span></font></p> </div> </span> <div><span style=3D'white-space:pre-wrap'> <p class=3DMsoNormal><font size=3D3 face=3DCalibri><span style=3D'font-size= :12.0pt; font-family:Calibri'>Olle E. Johansson said: </span><o:p></o:p></span>= </font></p> </div> <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?<o:p></o:p></span></font></pre><pre>= <font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '><o:p> </o:p></span></font></pre><pre><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '>Is it a failure or not?<o:p></o:p></span></font></pre><pre><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '><o:p> </o:p></span></font></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?<o:p></o:p></span></fo= nt></pre><pre><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '><o:p> </o:p></span></font></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?"<o:p></o:p></span></font></pre><pre><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '><o:p> </o:p></span></font></pre><pre><font size=3D3 face=3DCalibri><span style=3D'font-size:12.0pt;font-family:Calibri= '><o:p> </o:p></span></font></pre></div> </div> </div> </body> </html> --_000_EDC0A1AE77C57744B664A310A0B23AE202D2F6F6A9FRMRSSXCHMBSC_-- --===============2927064636604831185== 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 --===============2927064636604831185==--