Re: [Idr] Working group adoption call for draft-snijders-idr-deprecate-30-31-129

"Susan Hares" <> Fri, 04 November 2016 02:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 03C53129449 for <>; Thu, 3 Nov 2016 19:36:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9hhi7o8EC6zf for <>; Thu, 3 Nov 2016 19:36:46 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 99D2B127ABE for <>; Thu, 3 Nov 2016 19:36:46 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: "Susan Hares" <>
To: "'Robert Raszuk'" <>, "'John G. Scudder'" <>
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Date: Thu, 3 Nov 2016 22:34:28 -0400
Message-ID: <04b601d23643$f7c6b7f0$e75427d0$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_04B7_01D23622.70B5DB40"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG4XNVJbFLLu0eQmTL8gVJbAkCFVwDjdK5pAXaolZsCtVg7VQJ3ydgGAXttr6YCEsrS1KCjFl8Q
Content-Language: en-us
Archived-At: <>
Cc: 'IETF IDR Working Group' <>
Subject: Re: [Idr] Working group adoption call for draft-snijders-idr-deprecate-30-31-129
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 04 Nov 2016 02:36:48 -0000



<chair hat on> 

At the time RFC7120 was published, the IDR chairs and the RTG ADs invited all drafts that were written and published prior to that point to submit requests for early allocation with a simple IANA process.   Prior to RFC7210, there was an way to get this drafts done if we ask the IESG to review the documents.  The early allocation process did not start with RFC7120, but was simplified.   


By the way, draft-vandevelde-idr-remote-next-hop-00.txt was included in:   You will find this on the IDR web page.   On the  draft-marques-l3vpn-mcast-edge-01,  if the authors are working on this draft – then it is a bess draft.   If the authors have problems with the early code point allocation, then can copy me and I will transfer information to the appropriate BESS chairs.  I will ask the ADs to present a quick summary of Early Allocation processes to the whole Area so that people will have a better understanding of Early Allocation.  I realize the process may be frustrating to you and others.  I am willing to help solve the problems for specific drafts or via a proposal such as Jeff Haas made for private space.  However, this discussion should be done in a separate discussion thread or privately. 

<chair hat off> 





From: Idr [] On Behalf Of Robert Raszuk
Sent: Tuesday, November 1, 2016 11:04 AM
To: John G. Scudder
Cc: IETF IDR Working Group
Subject: Re: [Idr] Working group adoption call for draft-snijders-idr-deprecate-30-31-129




I'm not aware of there having been an early allocation request for any of the code points in question.


​Well I am not sure how some of the documents in question could ask for early allocation based on RFC7120 published in 2014 if they were written and published well before that date ...