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

Jeff Tantsura <jefftant.ietf@gmail.com> Mon, 19 March 2018 18:34 UTC

Return-Path: <jefftant.ietf@gmail.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 B26C41241F3; Mon, 19 Mar 2018 11:34:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level:
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 PgBwkjyXXs4A; Mon, 19 Mar 2018 11:34:22 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 396BF1241F5; Mon, 19 Mar 2018 11:34:22 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id l9so7903013wmh.2; Mon, 19 Mar 2018 11:34:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=zJ178U0kNCf0GjFn7shi/QYm8XG/LPJdbbYDv8HRR6o=; b=eqdBxm6jShyhld5Wo6kMgDXGWaGhYo4Aw3pJAohW2GFjZeElkwMdAztLGsDA6l9I1L VL7y9NZsv1KgG1YNMiVgUTUoG7CbxBoBlph6JDMDyavqoQ6bik/07FVk4Lfg7YHn2pju xdh9sdhL7Vdy5Bz4xrnp88E1bbxWAky82F6WAxgQI3aLXxen/8BT8pbIwjGh7D5qDzBn q2Jp2hg40A8sXIEyfyTs4CMZymGWLzOSZeQ5v9FnSU7+kLIeaVYMh93p+/zBRcCHkS9j NUsQpOrgnlvJ8NcXlbdCjq7iOSvL6Y5yAAdlRRl71udmGY59HNqEDTcjcKqnQf0GZUBL ugcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=zJ178U0kNCf0GjFn7shi/QYm8XG/LPJdbbYDv8HRR6o=; b=crmoK+HmJcje19AKc66t5qiusWgRcBPxN8RclctSz5/3e5Y0BtcUnHfZdScVeK5kCh 8mM5PvFihmIIHQSgD+5hbx4K3aswrXnDHZGxXdqnN9wafA4DO78E1OD/xRcbO04XJ8+O SkdLm0DGgYcSfabxKslbLTnGKnvrE3KMywQ2poJ+pr1MdwOtqV6UfjRpS1ycsnm38jFl g16CbJ/jBWNzMqnfveqfAu/VkZSCCqmsby5lKCvz8gIU46pi1vrxFI77DmA38lBUoBL/ D0uvQ/ljGu/qa8h69ITcfsf8mZW7dxYI9d+W4598lMJuo/oScnXwB8Ks3etwrZsLmyXu fJVA==
X-Gm-Message-State: AElRT7Hm1YzvshTf/EU+/08UF0LbQMOHmo+RO5RbD5P9UI5EZ052Yjvc xG0a9YuEE2ZZhDKuPkUnvcY=
X-Google-Smtp-Source: AG47ELuuhn2r4Gh+JUsTA0afqShCehF/zoccnfhoOD5ADdvYZsB7ag/Qw7rzIRy7VDTC/bnu9QDyYQ==
X-Received: by 10.28.69.93 with SMTP id s90mr9473028wma.29.1521484460712; Mon, 19 Mar 2018 11:34:20 -0700 (PDT)
Received: from [31.133.145.240] ([2001:67c:1232:144:84ba:9dc2:ca38:1b1b]) by smtp.gmail.com with ESMTPSA id s125sm74542wmf.4.2018.03.19.11.34.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Mar 2018 11:34:20 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/10.a.0.180210
Date: Mon, 19 Mar 2018 18:34:18 +0000
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "John G. Scudder" <jgs@juniper.net>
CC: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "idr@ietf.org" <idr@ietf.org>, Hares Susan <shares@ndzh.com>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, <bill.wu@huawei.com>, <wangzitao@huawei.com>
Message-ID: <011D09B5-FBC1-430A-8595-CDBCE4DA11F3@gmail.com>
Thread-Topic: [Idr] Early Code Point allocation for draft-ietf-idr-eag-distribution-05 (12/8 to 12/22)
References: <001e01d391a1$128e8a90$37ab9fb0$@ndzh.com> <1d73e50ba66841de9c07e47a531a3745@XCH-ALN-001.cisco.com> <8B1A8B67-712B-424D-8054-CBD051927582@juniper.net> <4F021758-BD99-4C30-B6AE-CE3357FB136D@gmail.com> <41D985C5-F4E3-4D99-A6AC-01EBBF8119B2@juniper.net>
In-Reply-To: <41D985C5-F4E3-4D99-A6AC-01EBBF8119B2@juniper.net>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3604329259_1531427660"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/tlpR8b1W4q_AAqF8XxB5gyBaNlE>
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 18:34:26 -0000

John,

 

In order to keep the naming consistent with RFC7308, the updated (extended) name is Extended Administrative Group.

Thanks!

 

Cheers,

Jeff

From: "John G. Scudder" <jgs@juniper.net>
Date: Monday, March 19, 2018 at 18:12
To: Jeff Tantsura <jefftant.ietf@gmail.com>
Cc: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>om>, "idr@ietf.org" <idr@ietf.org>rg>, Hares Susan <shares@ndzh.com>om>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Subject: Re: [Idr] Early Code Point allocation for draft-ietf-idr-eag-distribution-05 (12/8 to 12/22)

 

And to be clear, symbolic name and so on are as given in Table 1?

 

--John

 

On Mar 19, 2018, at 6:09 PM, Jeff Tantsura <jefftant.ietf@gmail.com> wrote:

 

Hi John,

 

The authors  request assigning a code-point from the registry "BGP- LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs".

 

The draft will be updated to reflect.

 

Thanks and apologies for the confusion!

 

Cheers,

Jeff

From: Idr <idr-bounces@ietf.org> on behalf of "John G. Scudder" <jgs@juniper.net>
Date: Monday, March 19, 2018 at 11:04
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
Cc: "idr@ietf.org" <idr@ietf.org>rg>, Hares Susan <shares@ndzh.com>om>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>
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> 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
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.    

 

_______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr