Re: [Idr] Changes to draft-ietf-idr-bgp-ls-registry

Susan Hares <shares@ndzh.com> Tue, 08 December 2020 22:21 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 D738A3A126C; Tue, 8 Dec 2020 14:21:35 -0800 (PST)
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, 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 iFsyc_OQRTGy; Tue, 8 Dec 2020 14:21:34 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 F052C3A126B; Tue, 8 Dec 2020 14:21:32 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=50.107.69.45;
From: "Susan Hares" <shares@ndzh.com>
To: <adrian@olddog.co.uk>, "'IDR List'" <idr@ietf.org>
Cc: <idr-chairs@ietf.org>
References: <0e3501d6cda2$fbf19d40$f3d4d7c0$@olddog.co.uk>
In-Reply-To: <0e3501d6cda2$fbf19d40$f3d4d7c0$@olddog.co.uk>
Date: Tue, 8 Dec 2020 17:21:15 -0500
Message-ID: <003a01d6cdb0$78d288d0$6a779a70$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGajGRKThIcpkdudESaynUGnDXA0apmR71A
Content-Language: en-us
X-Antivirus: AVG (VPS 201207-4, 12/07/2020), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/v48nSIjfWw3FoJrsZMZ4o5PzHZ4>
Subject: Re: [Idr] Changes to draft-ietf-idr-bgp-ls-registry
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: Tue, 08 Dec 2020 22:21:36 -0000

Adrian: 

Since I do not want things to "get it the way", 
Let  me ask if you are ready for another WG LC on this text? 

Sue

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Adrian Farrel
Sent: Tuesday, December 8, 2020 3:45 PM
To: 'IDR List'
Cc: idr-chairs@ietf.org
Subject: [Idr] Changes to draft-ietf-idr-bgp-ls-registry

Hi,

Thanks to all for the useful input and sorry for the long delay while
"things" got in the way.

I made some changes to the draft according to Alvaro's comments and then
updated the DE guidance per the discussions on list.

Ketan noted that point 6 of the guidance in RFC 7370 talks about "timeouts"
per RFC 7120. That only applies to early allocations, and that's not what
we're doing. I think it is still worth carrying text about what happens if
the document never becomes an RFC, so I have retained something similar, but
different. I hope this is consistent with what Les said.

Acee additionally suggested that code point requests should be "fully
transparent to the LSR list". I haven't added this, but it would be simple
to do if there is support for it.

Since the text changes are pretty much the whole draft, the easiest thing
seems to be to post an update and then invite you to review and comment. So
that's what I have done.

https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ls-registry

Cheers,
Adrian

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