RFC 6220 on Defining the Role and Function of IETF Protocol Parameter Registry Operators
rfc-editor@rfc-editor.org Thu, 14 April 2011 18:26 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfc.amsl.com
Delivered-To: ietf-announce@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 8E252E08B3 for <ietf-announce@ietfc.amsl.com>; Thu, 14 Apr 2011 11:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.117
X-Spam-Level:
X-Spam-Status: No, score=-102.117 tagged_above=-999 required=5 tests=[AWL=-0.440, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9DtbSqzpOrNL for <ietf-announce@ietfc.amsl.com>; Thu, 14 Apr 2011 11:26:08 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [64.170.98.47]) by ietfc.amsl.com (Postfix) with ESMTP id BFBC8E08B6 for <ietf-announce@ietf.org>; Thu, 14 Apr 2011 11:26:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 35E7CE0784; Thu, 14 Apr 2011 11:26:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6220 on Defining the Role and Function of IETF Protocol Parameter Registry Operators
From: rfc-editor@rfc-editor.org
Message-Id: <20110414182605.35E7CE0784@rfc-editor.org>
Date: Thu, 14 Apr 2011 11:26:05 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 14 Apr 2011 18:26:08 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6220 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., Internet Architecture Board Status: Informational Stream: IAB Date: April 2011 Mailbox: dmcpherson@verisign.com, olaf@NLnetLabs.nl, john+ietf@jck.com, gih@apnic.net, iab@iab.org Pages: 11 Characters: 23733 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iab-iana-08.txt URL: http://www.rfc-editor.org/rfc/rfc6220.txt 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 is not an Internet Standards Track specification; it is published for informational purposes. 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 http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. 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