BCP 100, RFC 7120 on Early IANA Allocation of Standards Track Code Points

rfc-editor@rfc-editor.org Sat, 25 January 2014 00:36 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65E9F1A02E5 for <ietf-announce@ietfa.amsl.com>; Fri, 24 Jan 2014 16:36:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.953
X-Spam-Level:
X-Spam-Status: No, score=0.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 aEv8wQ_aroM4 for <ietf-announce@ietfa.amsl.com>; Fri, 24 Jan 2014 16:36:37 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 391F81A0345 for <ietf-announce@ietf.org>; Fri, 24 Jan 2014 16:36:37 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8F0AE7FC3A1; Fri, 24 Jan 2014 16:36:34 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 100, RFC 7120 on Early IANA Allocation of Standards Track Code Points
From: rfc-editor@rfc-editor.org
Message-Id: <20140125003634.8F0AE7FC3A1@rfc-editor.org>
Date: Fri, 24 Jan 2014 16:36:34 -0800
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Sat, 25 Jan 2014 00:36:38 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 100        
        RFC 7120

        Title:      Early IANA Allocation of Standards 
                    Track Code Points 
        Author:     M. Cotton
        Status:     Best Current Practice
        Stream:     IETF
        Date:       January 2014
        Mailbox:    michelle.cotton@icann.org
        Pages:      9
        Characters: 17722
        Obsoletes:  RFC 4020
        See Also:   BCP 100

        I-D Tag:    draft-cotton-rfc4020bis-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7120.txt

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, which would
normally trigger code point allocation.  The procedures in this
document are intended to apply only to IETF Stream documents.


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
  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/search/rfc_search.php
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