Reminder: Early allocation process steps

Michelle Cotton <> Mon, 14 September 2020 19:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 45B533A0EC1 for <>; Mon, 14 Sep 2020 12:25:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EKf9e54UD4zP for <>; Mon, 14 Sep 2020 12:25:38 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9B78D3A0EBF for <>; Mon, 14 Sep 2020 12:25:38 -0700 (PDT)
Received: from ( []) by ( with ESMTPS id 08EJPbqI018961 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <>; Mon, 14 Sep 2020 19:25:38 GMT
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.659.4; Mon, 14 Sep 2020 12:25:36 -0700
Received: from ([]) by ([]) with mapi id 15.02.0659.006; Mon, 14 Sep 2020 12:25:36 -0700
From: Michelle Cotton <>
To: "" <>
Subject: Reminder: Early allocation process steps
Thread-Topic: Reminder: Early allocation process steps
Thread-Index: AQHWiszSdRlDc9nrW0GKF6FPHYmuOw==
Date: Mon, 14 Sep 2020 19:25:36 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
user-agent: Microsoft-MacOutlook/16.36.20041300
x-originating-ip: []
x-source-routing-agent: Processed
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha256; boundary="B_3682931135_1236294513"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-09-14_07:2020-09-14, 2020-09-14 signatures=0
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 14 Sep 2020 19:25:40 -0000

Attention Working Group Chairs:


This is just a friendly reminder about the early allocation process and what role you have as Working Group chairs.


RFC7120 outlines the rules for how the early allocation process works.

Please remember that this process should only be used according to criteria in RFC 7120.

We have noticed that many of the registrations get multiple renewals and are in the registries for many years.


Instructions for Working Group Chairs:


Step 1 - Request is sent to the Working Group chair by the editor/author


Step 2 - The WG chairs determine whether the conditions for early allocations described in Section 2 are met, particularly conditions (c) and (d).


Step 3 - The WG chairs gauge whether there is consensus within the WG that early allocation is appropriate for the given document.


Step 4 - If steps 2) and 3) are satisfied, the WG chairs request approval from the Area Director(s).  The Area Director(s) may apply judgement to the request, especially if there is a risk of registry depletion.


Step 5 - If the Area Directors approve step 4), the WG chairs request IANA to make an early allocation.

These requests can be sent to



If the early allocation needs a renewal after 1 year, approval from both the Working Group chair and the responsible Area Director is required.

In rare circumstances, if additional renewals are needed, IESG approval is required.


If you have any questions, do not hesitate to ask. 


Thank you and have a great week.


Michelle Cotton

Protocol Parameters Engagement Sr. Manager

IANA Services