Changing the Location-to-Service Translation (LoST) Location Profiles Registry Policy
Core Technology Consulting
United States of America
rg+ietf@coretechnologyconsulting.com
http://www.coretechnologyconsulting.com
Applications and Real Time
ecrit
This document changes the policy of the "Location-to-Service Translation (LoST) Location Profiles" IANA registry established by RFC 5222 from Standards Action to Specification Required. This allows standards development organizations (SDOs) other than the IETF to add new values.
Introduction
The Location-to-Service Translation (LoST) Protocol uses a location profile when conveying location (e.g., in a mapping request and a service boundary result). established an IANA registry of location profiles with a registry policy of Standards Action. This requires a Standards Track RFC for any new registry values. The National Emergency Number Association (NENA) is a standards development organization (SDO) that makes significant use of LoST in its emergency call specifications (e.g., ) and has identified a need for additional location profiles. This document changes the registry policy to Specification Required, allowing other SDOs such as NENA to add values.
Document Scope
This document changes the policy of the "Location-to-Service Translation (LoST) Location Profiles" IANA registry established by from Standards Action to Specification Required (as defined in ). This allows SDOs other than the IETF to add new values.
Security Considerations
No new security considerations are identified by this change in registry policy.
IANA Considerations
IANA has changed the policy of the "Location-to-Service Translation (LoST) Location Profiles" registry (established by
) to Specification Required. IANA has also added this document as a reference for the registry. The Expert Reviewer is designated per . The reviewer should verify that:
- the proposed new value is specified by the IETF, NENA, or a similar SDO in which location profiles are in scope;
- the proposed new value has a clear need (which includes there not being an existing profile that meets the need); and
- the profile specification is unambiguous and interoperable.
References
Normative References
Location-to-Service Translation (LoST) Location Profiles
IANA
Informative References
Detailed Functional and Interface Standards for the NENA i3 Solution
National Emergency Number Association (NENA)
NENA i3 Solution - Stage 3, NENA-STA-010.2-2016
Acknowledgements
Many thanks to for his helpful review and suggestions and to for his suggestion to clarify that "clear need" includes there not being an existing profile.