[Idr] draft-ietf-idr-capabilities-registry-change-05.txt - WG LC []6/9/2019 to 6/16/2019]

"Susan Hares" <shares@ndzh.com> Sun, 09 June 2019 17:33 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 6E48A120091 for <idr@ietfa.amsl.com>; Sun, 9 Jun 2019 10:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.948
X-Spam-Level:
X-Spam-Status: No, score=0.948 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] 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 mXcuDtE8X-D9 for <idr@ietfa.amsl.com>; Sun, 9 Jun 2019 10:33:36 -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 E9CB712002E for <idr@ietf.org>; Sun, 9 Jun 2019 10:33:35 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=166.177.57.113;
From: "Susan Hares" <shares@ndzh.com>
To: <idr@ietf.org>
Date: Sun, 9 Jun 2019 13:33:27 -0400
Message-ID: <094d01d51ee9$7329cc30$597d6490$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_094E_01D51EC7.EC1A2800"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdUe6OUjvDIGwFT+SrOBwJKEuiJdmw==
Content-Language: en-us
X-Antivirus: AVG (VPS 190609-2, 06/09/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/GkVQ0WGkH7P9cOJDdXAZrRbrz-o>
Subject: [Idr] draft-ietf-idr-capabilities-registry-change-05.txt - WG LC []6/9/2019 to 6/16/2019]
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: Sun, 09 Jun 2019 17:33:37 -0000

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