Re: [Ecrit] RFC 5222 on LoST: A Location-to-Service Translation Protocol

["Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig at nsn.com>]

After years of work we finally finished the LoST specification. 

Thank you all for the hard work!


>-----Original Message-----
>From: ecrit-bounces at ietf.org [mailto:ecrit-bounces at ietf.org] 
>On Behalf Of ext rfc-editor at rfc-editor.org
>Sent: 06 August, 2008 01:47
>To: ietf-announce at ietf.org; rfc-dist at rfc-editor.org
>Cc: ecrit at ietf.org; rfc-editor at rfc-editor.org
>Subject: [Ecrit] RFC 5222 on LoST: A Location-to-Service 
>Translation Protocol
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>        
>        RFC 5222
>
>        Title:      LoST: A Location-to-Service Translation Protocol 
>        Author:     T. Hardie, A. Newton,
>                    H. Schulzrinne, H. Tschofenig
>        Status:     Standards Track
>        Date:       August 2008
>        Mailbox:    hardie at qualcomm.com, 
>                    andy at hxr.us, 
>                    hgs+ecrit at cs.columbia.edu,
>                    Hannes.Tschofenig at nsn.com
>        Pages:      69
>        Characters: 123252
>        Updates/Obsoletes/SeeAlso:   None
>
>        I-D Tag:    draft-ietf-ecrit-lost-10.txt
>
>        URL:        http://www.rfc-editor.org/rfc/rfc5222.txt
>
>This document describes an XML-based protocol for mapping 
>service identifiers and geodetic or civic location information 
>to service contact URIs.  In particular, it can be used to 
>determine the location-appropriate Public Safety Answering 
>Point (PSAP) for emergency services.  [STANDARDS TRACK]
>
>This document is a product of the Emergency Context Resolution 
>with Internet Technologies Working Group of the IETF.
>
>This is now a Proposed Standard Protocol.
>
>STANDARDS TRACK: This document specifies an Internet standards 
>track protocol for the Internet community,and requests 
>discussion and suggestions for improvements.  Please refer to 
>the current edition of the Internet Official Protocol 
>Standards (STD 1) for the standardization state and status of 
>this protocol.  Distribution of this memo is unlimited.
>
>This announcement is sent to the IETF-Announce and rfc-dist lists.
>To subscribe or unsubscribe, see
>  http://www.ietf.org/mailman/listinfo/ietf-announce
>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
>For searching the RFC series, see 
>http://www.rfc-editor.org/rfcsearch.html.
>For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
>
>Requests for special distribution should be addressed to 
>either the author of the RFC in question, or to 
>rfc-editor at rfc-editor.org.  Unless specifically noted 
>otherwise on the RFC itself, all RFCs are for unlimited distribution.
>
>
>The RFC Editor Team
>USC/Information Sciences Institute
>
>
>_______________________________________________
>Ecrit mailing list
>Ecrit at ietf.org
>https://www.ietf.org/mailman/listinfo/ecrit
>
_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www.ietf.org/mailman/listinfo/ecrit