Re: [Idr] draft-ietf-idr-capabilities-registry-change-05.txt - WG LC []6/9/2019 to 6/16/2019] - extending this for a 3rd week (7/8 to 7/15)

"Susan Hares" <shares@ndzh.com> Mon, 08 July 2019 16:59 UTC

Return-Path: <shares@ndzh.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 02BEE1202AC for <idr@ietfa.amsl.com>; Mon, 8 Jul 2019 09:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.949
X-Spam-Level:
X-Spam-Status: No, score=0.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 8KHPH4gfkp_C for <idr@ietfa.amsl.com>; Mon, 8 Jul 2019 09:59:49 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (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 77BF51202FD for <idr@ietf.org>; Mon, 8 Jul 2019 09:59:44 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.25.161.218;
From: "Susan Hares" <shares@ndzh.com>
To: <idr@ietf.org>
Date: Mon, 8 Jul 2019 12:59:38 -0400
Message-ID: <015901d535ae$874b7a70$95e26f50$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_015A_01D5358D.003C2460"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdU1rm8JfKzi+/aVSh+TUngEcaoIPg==
Content-Language: en-us
X-Antivirus: AVG (VPS 190704-0, 07/04/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/l-XCcBQapHtgqEoWpGIkh2ruvIY>
Subject: Re: [Idr] draft-ietf-idr-capabilities-registry-change-05.txt - WG LC []6/9/2019 to 6/16/2019] - extending this for a 3rd week (7/8 to 7/15)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Jul 2019 17:00:00 -0000

Greetings: 

 

The email list support for this draft did not receive as many comments as I
expected.   Perhaps, this lack of comments was due to vacations or due to
this idea "just making sense".  

 

Since one of the WG chairs is an author, I do need a strong sense of
support.  Please send in comments or just a comment for "support" or "no
support" for this draft. 

 

Cheerily, Susan Hares

 

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Sunday, June 9, 2019 1:33 PM
To: idr@ietf.org
Subject: [Idr] draft-ietf-idr-capabilities-registry-change-05.txt - WG LC
[]6/9/2019 to 6/16/2019]

 

This begins a 2 week IDR  WG Last Call (LC) on
ft-ietf-idr-capabilities-registry-change-05.txt.  

 

The document is at: 

https://datatracker.ietf.org/doc/draft-ietf-idr-capabilities-registry-change
/

 

As registration document, there is no implementation report.  

 

Please indicate in comments to the IDR "support" or "no support" for WG LC. 

Consider:

 

1)      Does this change to registration procedures for BGP capability codes
help speed up processing? 

2)      Is there any technical or operational issue in making this change? 

3)      Do we need to pass this to the IESG at the same time as any GROW
document? 

 

John Scudder is an author so I am the shepherd/chair on this draft.  

 

Cheerily, Susan Hares