Changing the LoST Location Profile Registry Policy

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 29 March 2021.¶

Copyright Notice

Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶

Table of Contents

1. Document Scope

This document changes the policy of the Location-to-Service Translation (LoST) Location Profile registry [reg] established by [RFC5222] from Standards Action to Specification Required (as defined in [RFC8126]). This allows standards development organizations (SDOs) other than the IETF to add new values.¶

2. Introduction

The Location-to-Service Translation Protocol, LoST [RFC5222] uses a location profile when conveying location (e.g., in a mapping request and a service boundary result). [RFC5222] established an IANA registry of location profiles [reg], 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 an SDO that makes significant use of LoST in its emergency call specifications (e.g., [NENA-i3]) 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.¶

3. Security Considerations

No new security considerations are identified by this change in registry policy.¶

4. IANA Considerations

IANA is requested to change the policy of the Location-to-Service Translation (LoST) Location Profile Registry (established by [RFC5222]) to Specification Required. The expert reviewer is designated by the responsible area director. The reviewer should verify that any proposed new value is specified by the IETF, NENA, or a similar SDO, and meets a criteria of a clear need and unambiguous, interoperable definition.¶

Author's Address