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

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Mon, 19 March 2018 13:33 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 5696F126D3F; Mon, 19 Mar 2018 06:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.529
X-Spam-Level:
X-Spam-Status: No, score=-14.529 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, 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 wUWmI_kkeT6W; Mon, 19 Mar 2018 06:33:18 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A34CC128896; Mon, 19 Mar 2018 06:33:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=24090; q=dns/txt; s=iport; t=1521466395; x=1522675995; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=yFDTPkwC4YCcBLzTwkWMvtlAC+B9K2gnBlEVTKFcg5U=; b=mQDut3rmp5a+kkiW64LtpTDKlrVk8Fi7NGnQwYhmqRu2WTp3WhT+rzp7 nhtPOuO5RB12zA7OSJrOsg50W8BmArVUYQFPxhHptyr4SerWkacpvAi4Q Rfbg89kJDWdASdEIKjq7gUskJWI/m6qWFGQTfz2R3DP9zHXJAjAilTthF M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AEAQAQu69a/4kNJK1dGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYJadmZyKAqDU4objXmCA3sbhxOMbRSBfguFEAIagyQhNBg?= =?us-ascii?q?BAgEBAQEBAQJrKIUlAQEBBCMKTBACAQgRBAEBKAMCAgIfERQJCAEBBA4FCIQ?= =?us-ascii?q?sTAMVqEqCJocdDYEtgg6FM4IVgVWBVIJtM4JagXkBEgFVglKCYQOROYZNMAk?= =?us-ascii?q?CjAyDGYFXg3yHZIdCgiiGJAIREwGBKQEeOGFxcBU6gkOCY44IdI1ZgSKBGAE?= =?us-ascii?q?BAQ?=
X-IronPort-AV: E=Sophos;i="5.48,330,1517875200"; d="scan'208,217";a="372594254"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Mar 2018 13:33:14 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w2JDXEgJ010494 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 19 Mar 2018 13:33:14 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 19 Mar 2018 08:33:13 -0500
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; Mon, 19 Mar 2018 08:33:13 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "John G. Scudder" <jgs@juniper.net>
CC: Hares Susan <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>, "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+55gJblUBfMATnQLRABpfF4AAABU/wcA==
Date: Mon, 19 Mar 2018 13:33:13 +0000
Message-ID: <7a89d77e75f442299847bd423ae5a411@XCH-ALN-001.cisco.com>
References: <001e01d391a1$128e8a90$37ab9fb0$@ndzh.com> <1d73e50ba66841de9c07e47a531a3745@XCH-ALN-001.cisco.com> <8B1A8B67-712B-424D-8054-CBD051927582@juniper.net>
In-Reply-To: <8B1A8B67-712B-424D-8054-CBD051927582@juniper.net>
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.24.57.2]
Content-Type: multipart/alternative; boundary="_000_7a89d77e75f442299847bd423ae5a411XCHALN001ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/vmvgf0OR9pIuTM3LTBuHwcn7fKQ>
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: Mon, 19 Mar 2018 13:33:20 -0000

John –

I don’t own this draft. ☺
I was just interested in following up on this as we have  implementations.

Please nag the authors.

   Les

From: John G. Scudder <jgs@juniper.net>
Sent: Monday, March 19, 2018 4:04 AM
To: Les Ginsberg (ginsberg) <ginsberg@cisco.com>
Cc: Hares Susan <shares@ndzh.com>om>; idr@ietf.org; idr-chairs@ietf.org; Alvaro Retana <aretana.ietf@gmail.com>
Subject: Re: [Idr] Early Code Point allocation for draft-ietf-idr-eag-distribution-05 (12/8 to 12/22)

Hi Les,

I was just reviewing the draft prior to sending the allocation request in. Right now the IANA section reads

   IANA maintains the registry for the TLVs.  BGP Extended Admin Group
   link attribute TLV will require one new type code defined in this
   document.

This is not very clear direction for IANA. Can you update the IANA section? See RFC 8126, "Guidelines for Writing an IANA Considerations Section in RFCs". Section 1.3 has a short-form cheatsheet, you can skip down to the "If you are registering into an existing registry" part. I presume you want the "Border Gateway Protocol - Link State (BGP-LS) Parameters -- BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs" registry. I presume the rest is what's in your Table 1.

Probably the cleanest way to move forward is for you to simply update the draft, although you can also reply to this email with the info.

Thanks,

--John

On Feb 14, 2018, at 2:40 AM, Les Ginsberg (ginsberg) <ginsberg@cisco.com<mailto:ginsberg@cisco.com>> wrote:

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<mailto:idr@ietf.org>
Cc: idr-chairs@ietf.org<mailto: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.