draft-ietf-ecrit-lost-sync-13.txt   draft-ietf-ecrit-lost-sync-14.txt 
ECRIT H. Schulzrinne ECRIT H. Schulzrinne
Internet-Draft Columbia University Internet-Draft Columbia University
Intended status: Experimental H. Tschofenig Intended status: Experimental H. Tschofenig
Expires: May 3, 2012 Nokia Siemens Networks Expires: July 14, 2012 Nokia Siemens Networks
October 31, 2011 January 11, 2012
Synchronizing Location-to-Service Translation (LoST) Protocol based Synchronizing Location-to-Service Translation (LoST) Protocol based
Service Boundaries and Mapping Elements Service Boundaries and Mapping Elements
draft-ietf-ecrit-lost-sync-13.txt draft-ietf-ecrit-lost-sync-14.txt
Abstract Abstract
The Location-to-Service Translation (LoST) protocol is an XML-based The Location-to-Service Translation (LoST) protocol is an XML-based
protocol for mapping service identifiers and geodetic or civic protocol for mapping service identifiers and geodetic or civic
location information to service URIs and service boundaries. In location information to service URIs and service boundaries. In
particular, it can be used to determine the location-appropriate particular, it can be used to determine the location-appropriate
Public Safety Answering Point (PSAP) for emergency services. Public Safety Answering Point (PSAP) for emergency services.
The main data structure, the <mapping> element, used for The main data structure, the <mapping> element, used for
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 3, 2012. This Internet-Draft will expire on July 14, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 27 skipping to change at page 3, line 27
4.2. Behavior of the LoST Sync Destination . . . . . . . . . . 14 4.2. Behavior of the LoST Sync Destination . . . . . . . . . . 14
4.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.3. Example . . . . . . . . . . . . . . . . . . . . . . . . . 15
5. Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5. Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6. RelaxNG . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 6. RelaxNG . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
7. Operational Considerations . . . . . . . . . . . . . . . . . . 22 7. Operational Considerations . . . . . . . . . . . . . . . . . . 22
8. Security Considerations . . . . . . . . . . . . . . . . . . . 23 8. Security Considerations . . . . . . . . . . . . . . . . . . . 23
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
9.1. Content-type registration for 9.1. Content-type registration for
'application/lostsync+xml' . . . . . . . . . . . . . . . . 24 'application/lostsync+xml' . . . . . . . . . . . . . . . . 24
9.2. LoST Sync Relax NG Schema Registration . . . . . . . . . . 25 9.2. LoST Sync Relax NG Schema Registration . . . . . . . . . . 25
9.3. LoST Synchronization Namespace Registration . . . . . . . 25 9.3. LoST Synchronization Namespace Registration . . . . . . . 26
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 28
11.1. Normative References . . . . . . . . . . . . . . . . . . . 28 11.1. Normative References . . . . . . . . . . . . . . . . . . . 28
11.2. Informative References . . . . . . . . . . . . . . . . . . 28 11.2. Informative References . . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29
1. Introduction 1. Introduction
The LoST (Location-to-Service Translation) protocol [RFC5222] maps The LoST (Location-to-Service Translation) protocol [RFC5222] maps
service identifiers and geodetic or civic location information to service identifiers and geodetic or civic location information to
skipping to change at page 24, line 13 skipping to change at page 24, line 13
adversary itself then it might impersonate PSAPs. adversary itself then it might impersonate PSAPs.
9. IANA Considerations 9. IANA Considerations
9.1. Content-type registration for 'application/lostsync+xml' 9.1. Content-type registration for 'application/lostsync+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application Type name: application
MIME subtype name: lostsync+xml Subtype name: lostsync+xml
Mandatory parameters: none Required parameters: none
Optional parameters: charset Optional parameters: charset
Indicates the character encoding of enclosed XML. Indicates the character encoding of enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See RFC characters, depending on the character encoding used. See RFC
3023 [RFC3023], Section 3.2. 3023 [RFC3023], Section 7.1.
Security considerations: This content type is designed to carry LoST Security considerations: This content type is designed to carry LoST
Syncronization protocol payloads. Syncronization protocol payloads described in RFCXXXX. [NOTE TO
IANA/RFC-EDITOR: Please replace XXXX with the RFC number of this
specification.]
Interoperability considerations: None Interoperability considerations: None
Published specification: RFCXXXX [NOTE TO IANA/RFC-EDITOR: Please Published specification: RFCXXXX [NOTE TO IANA/RFC-EDITOR: Please
replace XXXX with the RFC number of this specification.] replace XXXX with the RFC number of this specification.]
Applications which use this media type: Emergency and Location-based Applications which use this media type: Emergency and Location-based
Systems Systems
Additional information: Additional information:
Magic Number: None Magic number(s): None
File Extension: .lostsyncxml File extension(s): .lostsyncxml
Macintosh file type code: 'TEXT' Macintosh file type code(s): 'TEXT'
Personal and email address for further information: Hannes Person & email address to contact for further information: Hannes
Tschofenig, Hannes.Tschofenig@nsn.com Tschofenig <Hannes.Tschofenig@gmx.net>
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: Restrictions on usage: None
Author: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Change controller:
This specification is a work item of the IETF ECRIT working group, This specification is a work item of the IETF ECRIT working group,
with mailing list address <ecrit@ietf.org>. with mailing list address <ecrit@ietf.org>.
Change controller: Change controller:
The IESG <iesg@ietf.org> The IESG <iesg@ietf.org>
9.2. LoST Sync Relax NG Schema Registration 9.2. LoST Sync Relax NG Schema Registration
skipping to change at page 27, line 16 skipping to change at page 27, line 16
Robins George, Cullen Jennings, Karl Heinz Wolf, Richard Barnes, Robins George, Cullen Jennings, Karl Heinz Wolf, Richard Barnes,
Mayutan Arumaithurai, Alexander Mayrhofer, and Andrew Newton provided Mayutan Arumaithurai, Alexander Mayrhofer, and Andrew Newton provided
helpful input. Jari Urpalainen assisted with the Relax NG schema. helpful input. Jari Urpalainen assisted with the Relax NG schema.
We would also like to thank our PROTO shepherd Roger Marshall for his We would also like to thank our PROTO shepherd Roger Marshall for his
help with the document. help with the document.
We would like to particularly thank Andrew Newton for his timely and We would like to particularly thank Andrew Newton for his timely and
valuable review of the XML-related content. valuable review of the XML-related content.
We would like to thank Robert Sparks for his AD review feedback. We would like to thank Robert Sparks for his AD review feedback, and
Bjoern Hoehrmann for his media type review.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
 End of changes. 16 change blocks. 
18 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/