Changing the Location-to-Service Translation (LoST) Location Profiles Registry Policy
updates
- rfc-5222 — LoST: A Location-to-Service Translation Protocol
Extracted elements (6)
The registry policy was changed from Standards Action to Specification Required because NENA, an SDO that makes significant use of LoST in emergency call specifications, identified a need for additional location profiles that the previous policy blocked. Specification Required allows non-IETF SDOs to contribute values without requiring a Standards Track RFC.
The Expert Reviewer for new registry entries must verify that the proposed value is specified by the IETF, NENA, or a similar SDO in which location profiles are in scope.
The Expert Reviewer must verify that the profile specification is unambiguous and interoperable.
The Expert Reviewer must verify that the proposed new location profile value has a clear need, which includes there not being an existing profile that already meets that need.
The 'Location-to-Service Translation (LoST) Location Profiles' IANA registry, originally established by RFC 5222 with a Standards Action policy, is updated by this document to Specification Required. This allows SDOs other than the IETF (such as NENA) to add new location profile values.
No new security considerations are identified by this change in registry policy from Standards Action to Specification Required.