Last Call: <draft-leiba-cotton-iana-5226bis-08.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Thu, 02 October 2014 13:47 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBB621A0392 for <ietf-announce@ietfa.amsl.com>; Thu, 2 Oct 2014 06:47:42 -0700 (PDT)
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] autolearn=ham
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 6Pae6Dko9QM1 for <ietf-announce@ietfa.amsl.com>; Thu, 2 Oct 2014 06:47:41 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 973841A0384 for <ietf-announce@ietf.org>; Thu, 2 Oct 2014 06:47:41 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-leiba-cotton-iana-5226bis-08.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20141002134741.24737.61232.idtracker@ietfa.amsl.com>
Date: Thu, 02 Oct 2014 06:47:41 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/Bt4Dk1vlaGLJ-Ic_zKb4g1Upkgw
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
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, 02 Oct 2014 13:47:43 -0000

The IESG has received a request from an individual submitter to consider
the following document:
- 'Guidelines for Writing an IANA Considerations Section in RFCs'
  <draft-leiba-cotton-iana-5226bis-08.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2014-10-30. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   Many protocols make use of points of extensibility that use constants
   to identify various protocol parameters.  To ensure that the values
   used in these fields do not have conflicting uses, and to promote
   interoperability, their allocation is often coordinated by a central
   authority.  For IETF protocols, that role is filled by the Internet
   Assigned Numbers Authority (IANA).

   To make assignments in a given namespace prudently, IANA needs
   guidance describing the conditions under which new values should be
   assigned, as well as when and how modifications to existing values
   can be made.  This document defines a framework for the documentation
   of these guidelines by specification authors, in order to assure that
   the guidance given to IANA is clear and addresses the various issues
   that are likely in the operation of a registry.

   This is the third edition, and obsoletes RFC 5226.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis/ballot/


No IPR declarations have been submitted directly on this I-D.