New rules for IANA early allocation

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 28 August 2013 11:49 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70AE021F9E80 for <routing-discussion@ietfa.amsl.com>; Wed, 28 Aug 2013 04:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ydPLMy-6-uf5 for <routing-discussion@ietfa.amsl.com>; Wed, 28 Aug 2013 04:49:34 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 43A7221F9D68 for <routing-discussion@ietf.org>; Wed, 28 Aug 2013 04:49:31 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7SBnUIu032031 for <routing-discussion@ietf.org>; Wed, 28 Aug 2013 12:49:31 +0100
Received: from 950129200 (ixe-nat1.juniper.net [193.110.54.36]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7SBnPZN031972 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <routing-discussion@ietf.org>; Wed, 28 Aug 2013 12:49:29 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: routing-discussion@ietf.org
Subject: New rules for IANA early allocation
Date: Wed, 28 Aug 2013 12:49:26 +0100
Message-ID: <052a01cea3e4$a8470260$f8d50720$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6j5FenyiejcAjDRzSqZP7ALlhjmA==
Content-Language: en-gb
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 11:49:39 -0000

All,

Please review this document during IETF last call.

Thanks,
Adrian

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 27 August 2013 22:52
> To: IETF-Announce
> Subject: Last Call: <draft-cotton-rfc4020bis-01.txt> (Early IANA Allocation of
> Standards Track Code Points) to Best Current Practice
> 
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Early IANA Allocation of Standards Track Code Points'
>   <draft-cotton-rfc4020bis-01.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 2013-09-24. 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
> 
>    This memo describes the process for early allocation of code points
>    by IANA from registries for which "Specification Required", "RFC
>    Required", "IETF Review", or "Standards Action" policies apply.  This
>    process can be used to alleviate the problem where code point
>    allocation is needed to facilitate desired or required implementation
>    and deployment experience prior to publication of an RFC that would
>    normally trigger code point allocation.
> 
>    This document obsoletes RFC 4020.
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-cotton-rfc4020bis/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-cotton-rfc4020bis/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.