BCP 26, RFC 8126 on Guidelines for Writing an IANA Considerations Section in RFCs
rfc-editor@rfc-editor.org Tue, 20 June 2017 20:03 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 1B5B7131645 for <ietf-announce@ietfa.amsl.com>; Tue, 20 Jun 2017 13:03:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 EK2sdwJXUIAp for <ietf-announce@ietfa.amsl.com>; Tue, 20 Jun 2017 13:03:48 -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 B2491131646 for <ietf-announce@ietf.org>; Tue, 20 Jun 2017 13:03:26 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3E93FB81365; Tue, 20 Jun 2017 13:03:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 26, RFC 8126 on Guidelines for Writing an IANA Considerations Section in RFCs
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
Message-Id: <20170620200307.3E93FB81365@rfc-editor.org>
Date: Tue, 20 Jun 2017 13:03:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/0zMZIlnZTB2H-gliSjfhNUSdVW4>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 20 Jun 2017 20:03:50 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 26
RFC 8126
Title: Guidelines for Writing an
IANA Considerations Section in RFCs
Author: M. Cotton,
B. Leiba,
T. Narten
Status: Best Current Practice
Stream: IETF
Date: June 2017
Mailbox: michelle.cotton@iana.org,
barryleiba@computer.org,
narten@us.ibm.com
Pages: 47
Characters: 109907
Obsoletes: RFC 5226
See Also: BCP 26
I-D Tag: draft-leiba-cotton-iana-5226bis-20.txt
URL: https://www.rfc-editor.org/info/rfc8126
DOI: 10.17487/RFC8126
Many protocols make use of points of extensibility that use constants
to identify various protocol parameters. To ensure that the values
in these fields do not have conflicting uses and to promote
interoperability, their allocations are often coordinated by a
central record keeper. For IETF protocols, that role is filled by
the Internet Assigned Numbers Authority (IANA).
To make assignments in a given registry prudently, guidance
describing the conditions under which new values should be assigned,
as well as when and how modifications to existing values can be made,
is needed. This document defines a framework for the documentation
of these guidelines by specification authors, in order to assure that
the provided guidance for the IANA Considerations is clear and
addresses the various issues that are likely in the operation of a
registry.
This is the third edition of this document; it obsoletes RFC 5226.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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