RFC 9036 on Changing the Location-to-Service Translation (LoST) Location Profiles Registry Policy
rfc-editor@rfc-editor.org Fri, 04 June 2021 06:41 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E37E3A2BBF; Thu, 3 Jun 2021 23:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 98fXnFSC_MxS; Thu, 3 Jun 2021 23:40:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63B4D3A2BBB; Thu, 3 Jun 2021 23:40:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 47491F40725; Thu, 3 Jun 2021 23:40:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9036 on Changing the Location-to-Service Translation (LoST) Location Profiles Registry Policy
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ecrit@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210604064031.47491F40725@rfc-editor.org>
Date: Thu, 03 Jun 2021 23:40:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/jTH0g4-r6KjK2wNAWwTivTG3m78>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jun 2021 06:41:03 -0000
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: rg+ietf@coretechnologyconsulting.com
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 rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC