RFC 8722 on Defining the Role and Function of IETF Protocol Parameter Registry Operators
rfc-editor@rfc-editor.org Thu, 27 February 2020 18:20 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 D66B83A07AF for <ietf-announce@ietfa.amsl.com>; Thu, 27 Feb 2020 10:20:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 P_wiCNqbCA0A for <ietf-announce@ietfa.amsl.com>; Thu, 27 Feb 2020 10:20:07 -0800 (PST)
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 6D8B13A0763 for <ietf-announce@ietf.org>; Thu, 27 Feb 2020 10:20:07 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 397EBF40721; Thu, 27 Feb 2020 10:19:53 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8722 on Defining the Role and Function of IETF Protocol Parameter Registry Operators
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
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200227181953.397EBF40721@rfc-editor.org>
Date: Thu, 27 Feb 2020 10:19:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/05fgchTi7TKiI4lXv-p8Do40BzE>
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: Thu, 27 Feb 2020 18:20:16 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8722
Title: Defining the Role and Function
of IETF Protocol Parameter Registry Operators
Author: D. McPherson, Ed.,
O. Kolkman, Ed.,
J. Klensin, Ed.,
G. Huston, Ed.
Status: Informational
Stream: IAB
Date: February 2020
Mailbox: dmcpherson@verisign.com,
kolkman@isoc.org,
john-ietf@jck.com,
gih@apnic.net
Pages: 11
Obsoletes: RFC 6220
I-D Tag: draft-ietf-iasa2-rfc6220bis-04.txt
URL: https://www.rfc-editor.org/info/rfc8722
DOI: 10.17487/RFC8722
Many Internet Engineering Task Force (IETF) protocols make use of
commonly defined values that are passed in messages or packets. To
ensure consistent interpretation of these values between independent
implementations, there is a need to ensure that the values and
associated semantic intent are uniquely defined. The IETF uses
registry functions to record assigned protocol parameter values and
their associated semantic intentions. For each IETF protocol
parameter, it is current practice for the IETF to delegate the role
of Protocol Parameter Registry Operator to a nominated entity. This
document provides a description of, and the requirements for, these
delegated functions. This document obsoletes RFC 6220 to replace all
references to the IETF Administrative Support Activity (IASA) and
related structures with those defined by the IASA 2.0 Model.
This document is a product of the Internet Architecture Board.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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