Subject: RFC 9036 on Changing the Location-to-Service Translation (LoST) Location Profiles Registry Policy

From: [email-masked]
Date: Thu, 3 Jun 2021 23:40:31 -0700 (PDT)

A new Request for Comments is now available in online RFC libraries.

        RFC 9036

        Title:      Changing the Location-to-Service Translation (LoST) 
                    Location Profiles Registry Policy 
        Author:     R. Gellens
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2021
        Mailbox:    [email-masked]
        Pages:      4
        Updates:    RFC 5222

        I-D Tag:    draft-ietf-ecrit-location-profile-registry-policy-02.txt

        URL:        https://www.rfc-editor.org/info/rfc9036

        DOI:        10.17487/RFC9036

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.

This document is a product of the Emergency Context Resolution with Internet Technologies Working Group of the IETF.

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC