Re: [Idr] Early Code Point allocation for draft-ietf-idr-eag-distribution-05 (12/8 to 12/22)

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 14 February 2018 02:40 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1922129511; Tue, 13 Feb 2018 18:40:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 UmDwZXM9n_h4; Tue, 13 Feb 2018 18:40:04 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB87B1270A3; Tue, 13 Feb 2018 18:40:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8693; q=dns/txt; s=iport; t=1518576003; x=1519785603; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=9ZVIR5oLSwaFYxwWj9lVfHLiLQGHKUcv7R1BqhVmEJg=; b=dywlXsB9MAGQ3J9AgrxVNdsvRy7TlVGnMAYHjW/Nzw85mRV6mH0WgY2T j+9pMik4GznPh7snEl1Fy89IZLlrULGgf4pGnhFfrW470Tn89HdUluLvL QCQo0HE4GJskkATXpsjIvVROcGCGKCYnRwMloiGw6ZQ+QvhSMLA/8bo29 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DvAABloINa/4ENJK1dGQEBAQEBAQEBAQEBAQcBAQEBAYJaeGZwKAqNf44mggKBF5BmhVuCGAqFOwKCaFQYAQIBAQEBAQECayiFIwEBAQQtTBACAQgOAwQBASgHMhQJCAEBBAENBQiJSWSyRoh/ghMBAQEBAQEBAQEBAQEBAQEBAQEBAQEdhQGCFYFXhRaFWIVGBZomiggJApV5lE2XawIRGQGBOwEfOYFQcBU9gkaDCoFteIxtgRkBAQE
X-IronPort-AV: E=Sophos;i="5.46,510,1511827200"; d="scan'208,217";a="356904326"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Feb 2018 02:40:02 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id w1E2e2hc004876 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 14 Feb 2018 02:40:02 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 13 Feb 2018 20:40:01 -0600
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1320.000; Tue, 13 Feb 2018 20:40:01 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "idr-chairs@ietf.org" <idr-chairs@ietf.org>, Alvaro Retana <aretana.ietf@gmail.com>
Thread-Topic: [Idr] Early Code Point allocation for draft-ietf-idr-eag-distribution-05 (12/8 to 12/22)
Thread-Index: AdORn7v43YRSQoYwSe+55gJblUBfMATnQLRA
Date: Wed, 14 Feb 2018 02:40:01 +0000
Message-ID: <1d73e50ba66841de9c07e47a531a3745@XCH-ALN-001.cisco.com>
References: <001e01d391a1$128e8a90$37ab9fb0$@ndzh.com>
In-Reply-To: <001e01d391a1$128e8a90$37ab9fb0$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.162.4]
Content-Type: multipart/alternative; boundary="_000_1d73e50ba66841de9c07e47a531a3745XCHALN001ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/GMxN3Y3ABr4OBK40hOs3EdgLyY8>
Subject: Re: [Idr] Early Code Point allocation for draft-ietf-idr-eag-distribution-05 (12/8 to 12/22)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Feb 2018 02:40:06 -0000

Sue -

Has early allocation been completed?
I don't see any code point assigned in the BGP-LS registry (apologies if I missed it).

Thanx.

    Les


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Friday, January 19, 2018 7:45 PM
To: idr@ietf.org
Cc: idr-chairs@ietf.org
Subject: Re: [Idr] Early Code Point allocation for draft-ietf-idr-eag-distribution-05 (12/8 to 12/22)

WG:

We've received 7 positive comments for early allocation of the draft-ietf-idr-eag-distribution-05.txt work.  There were no problems pointed to with the draft-ietf-idr-eag-distribution-05.txt specification.   The WG chairs usually like a few more positive comments, but the December time period (12/8 to 12/22) may have reduced the number of comments.  We received no substantial number of comments after the first week.

Cisco has completed an implementation and is looking for an interoperability test prior to shipping code. The work has implementations that need the early allocation, a stable specification, and these positive comments on the list.  I've received several comments requesting the processing of this call.  Based on the WG continued request to get implementations early allocation of code points, I'm going to declare WG consensus on allocating these code points.  I will forward this early allocation request to Alvaro Retana for processing.

I think this points to the fact that we should go to single week early allocation request.   The drafts either succeed or fail on the first week's work.


Sue Hares
WG Co-chair

PS - I think this points to the fact that we should go to single week early allocation request.   The drafts either succeed or fail on the first week's work.   John and I are always looking for feedback to determine if we are following the wishes of the IDR WG in getting this early allocations.