Re: [Idr] Update to update to BGP-LS registries
"Adrian Farrel" <adrian@olddog.co.uk> Fri, 26 July 2019 23:47 UTC
Return-Path: <adrian@olddog.co.uk>
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 0109C1201CF for <idr@ietfa.amsl.com>; Fri, 26 Jul 2019 16:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 T15l_kP4inNZ for <idr@ietfa.amsl.com>; Fri, 26 Jul 2019 16:47:42 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DA4E120181 for <idr@ietf.org>; Fri, 26 Jul 2019 16:47:42 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id x6QNlb9C011030; Sat, 27 Jul 2019 00:47:37 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id EB8EB2203B; Sat, 27 Jul 2019 00:47:36 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS id D67FD2203A; Sat, 27 Jul 2019 00:47:36 +0100 (BST)
Received: from LAPTOPK7AS653V ([207.115.96.130]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id x6QNlZHx017177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 27 Jul 2019 00:47:36 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: "'Ketan Talaulikar (ketant)'" <ketant@cisco.com>, 'John Scudder' <jgs@juniper.net>
Cc: 'idr wg' <idr@ietf.org>
References: <0b0a01d543bf$f5336ba0$df9a42e0$@olddog.co.uk> <DM5PR11MB2027839B3DD1CE0786AF3289C1C00@DM5PR11MB2027.namprd11.prod.outlook.com> <E9AC1BEC-2013-4E93-9E02-0BBF23A2850D@juniper.net> <DM5PR11MB20279E5CFEACA444111D2293C1C00@DM5PR11MB2027.namprd11.prod.outlook.com>
In-Reply-To: <DM5PR11MB20279E5CFEACA444111D2293C1C00@DM5PR11MB2027.namprd11.prod.outlook.com>
Date: Sat, 27 Jul 2019 00:47:34 +0100
Organization: Old Dog Consulting
Message-ID: <0bc801d5440c$80538070$80fa8150$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLkl3mY83GCwxCSU79jTED04JkmqQLxEcwxAsyAqUIA17HGRKSKPlRA
Content-Language: en-gb
X-Originating-IP: 207.115.96.130
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24804.000
X-TM-AS-Result: No--32.057-10.0-31-10
X-imss-scan-details: No--32.057-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24804.000
X-TMASE-Result: 10--32.057500-10.000000
X-TMASE-MatchedRID: jFqw+1pFnMweimh1YYHcKHFPUrVDm6jtekMgTOQbVFshhinnYz32Ykg9 oIEl5+Xgguo6jdL62F8r6x2u8/a0KPUWuHlgOr4b4MrrDfG1YogHgh3sKJBzPyNBWGZQkFR8LOr nEveTxrvuaIINGihz7+TPthZ3iYU4KdFDPGM5RCC5Xsf6ykoeE+DTYjejIZTwF55N1tH/HwhJcB XvKYkUg8q0YAX9pWYdQZth5Ml6nDW8JA1vjfBQiJDVKd6th34Qv+Qg1T/0LH5SasGAkNQYrFiqA yk7LkbkwU/xqV35aDSO0joadW8QGlzwZOz5IWNfWnQHHkRrIIX4qCLIu0mtIAbYcy9YQl6eo9Wa 4y0zn8/ZNoMZfQFtO+ypoNloSuEKolMbrItxSe3tP6Pv+A+w8/XuWpt5ue19e1OjQ/WyxP79gRa xWZjuWNPDna39iaW9zzX1CfyBw5t486MriXIMeEsh+mzT1UnbOhJ9m53n4aBetEe1EXuPlCj53a EB5qDLTdSH9orMuitVP8kEFSBLJIDVR1zNwvHuOUWbqnaOytq8Nh50Bvk6wJLBwsVwuMFlPyeUi p5R3W2zeIXFukxqduIOw7aLjJF6TSoF6P7smzEH9dSeYYY46rwEm7iogq9pIyM6bqaAlyvRHXZN MPa2OzH8TZZ9RbAmFoEWlriP/Jd09yt1Yp3gn7llPmifeo7SSTyFqAhtoaaynk7TnYzMuoFgfGk QkLJNn03GpFuyt0mm3cvlUWpW2wFJUSWQPXgmyf21YeIsPYZ+0wZAOyZD1fv7ndOc2uMkYQXbtp S6AVP5cBTwjIVLtntjE+95XBt6fDDFL+oKuV6eAiCmPx4NwFkMvWAuahr8RTPcgmZKtSB88Plw9 Yn011Om2gN+nomsxEHRux+uk8irEHfaj14ZyVVoEXK0hBS3
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0HEpM_d1lLfMPUGMdljFk7rKecc>
Subject: Re: [Idr] Update to update to BGP-LS registries
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: Fri, 26 Jul 2019 23:47:46 -0000
Thanks Ketan, I believe you have captured all elements of this discussion. *If* an I-D can reliably be considered as "permanent" reference, then Specification Required would, indeed, be fine. And you are right that one way to get the effect we want is to change (or clarify) 8126 so that I-Ds can be considered permanent records. There are those in the community who consider this to already be the case. There are some who say that the Designated Expert can make this judgement for a Specification Required registry. There are some who say "over my dead body!" 8126 is an IETF wide document and we can expect making an IETF consensus change to be slow under the best of circumstances. In the case where there is division, we can achieve what we want by just changing the policy for our own registry. Path of least resistance (TM). Best, Adrian -----Original Message----- From: Ketan Talaulikar (ketant) <ketant@cisco.com> Sent: 27 July 2019 00:11 To: John Scudder <jgs@juniper.net> Cc: adrian@olddog.co.uk; idr wg <idr@ietf.org> Subject: RE: [Idr] Update to update to BGP-LS registries Hi John, I have absolutely no issue (and completely agree) with the text that Adrian has proposed for the DE guidelines in https://datatracker.ietf.org/doc/html/draft-farrel-idr-bgp-ls-registry-01#section-2.1 and I do defer to his expertise & experience on this. (Adrian, now it is in writing 😉) My only point was that we are changing the policy from Specification Required to Expert Review only because of this bit about IDs not being "permanent". As such it perhaps needs a broader look from IANA and as advised by Alvaro, I will share this feedback with them. The point regarding process overheads and additional gatekeepers that you referred to was with the Early Allocation Process defined in RFC7120. However, I believe we are talking "allocation" under Specification Required and not "early allocation" - so the process described in RFC7120 does not apply? I somehow got the impression that RFC7120 was more about the schemes that were more stringent that Specification Required as described in RFC8126. I may be wrong. In any case, I have no issues with the proposal on table and I will just share my feedback with IANA for them to review. Thanks, Ketan -----Original Message----- From: John Scudder <jgs@juniper.net> Sent: 26 July 2019 13:05 To: Ketan Talaulikar (ketant) <ketant@cisco.com> Cc: adrian@olddog.co.uk; idr wg <idr@ietf.org> Subject: Re: [Idr] Update to update to BGP-LS registries Hi Ketan, I am hoping our hallway conversation after the meeting resolved your concern, but if it didn’t please follow up. Regards, —John > On Jul 26, 2019, at 11:49 AM, Ketan Talaulikar (ketant) <ketant@cisco.com> wrote: > > Hello Adrian, > > IMO Specification Required is still the right and correct mechanism - we do need a specification that is available permanently! > > Just because of a misalignment between "permanent archival/availability" aspect and this text related to I-Ds that say they are "temporary", we should not fall back to Expert Review. Specification Required includes Expert Review. > > Why can't RFC8126 be fixed to say that for the purpose of Specification Required, the I-Ds are acceptable. We definitely do need defined TLVs and documentation of their usage. Otherwise, things can get chaotic. > > Please excuse my ignorance of the IANA/IETF procedures and correct me. > > Thanks, > Ketan > > -----Original Message----- > From: Idr <idr-bounces@ietf.org> On Behalf Of Adrian Farrel > Sent: 26 July 2019 10:40 > To: 'idr wg' <idr@ietf.org> > Subject: [Idr] Update to update to BGP-LS registries > > Hi, > > jgs spotted some typos (I didn't have time to run spell check before this morning). > Donald pointed out a concern with the guidance to the DE. > > Best, > Adrian > > -----Original Message----- > From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of > internet-drafts@ietf.org > Sent: 26 July 2019 15:35 > To: i-d-announce@ietf.org > Subject: I-D Action: draft-farrel-idr-bgp-ls-registry-01.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title : Updates to the Allocation Policy for the Border > Gateway Protocol - Link State (BGP-LS) Parameters Registries > Author : Adrian Farrel > Filename : draft-farrel-idr-bgp-ls-registry-01.txt > Pages : 4 > Date : 2019-07-26 > > Abstract: > RFC 7752 defines Border Gateway Protocol - Link State (BGP-LS). IANA > created a registry consistent with that document called the "Border > Gateway Protocol - Link State (BGP-LS) Parameters Registry" with a > number of sub-registries. The allocation policy applied by IANA for > those policies is "Specification Required" as defined in RFC 8126. > > This document updates RFC 7752 by changing the allocation policy for > all of the registries to "Expert Review." > > > The IETF datatracker status page for this draft is: > https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf. > org_doc_draft-2Dfarrel-2Didr-2Dbgp-2Dls-2Dregistry_&d=DwICAg&c=HAkYuh6 > 3rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=hLt5iDJpw7ukqICc0hoT7A&m=xPuRgN > J7XqUv2y23lo-jodi1lW8oPwP-ZWnWxJHrpJE&s=R1TAcTsN7xepgditnUCKDpLV9WoW1P > q8yEAdIAOIML0&e= > > There are also htmlized versions available at: > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_ht > ml_draft-2Dfarrel-2Didr-2Dbgp-2Dls-2Dregistry-2D01&d=DwICAg&c=HAkYuh63 > rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=hLt5iDJpw7ukqICc0hoT7A&m=xPuRgNJ > 7XqUv2y23lo-jodi1lW8oPwP-ZWnWxJHrpJE&s=S5GHtyQ8611WNm2lZsg5gHK7S3OHDqJ > 0NCZORFqiUYg&e= > https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf. > org_doc_html_draft-2Dfarrel-2Didr-2Dbgp-2Dls-2Dregistry-2D01&d=DwICAg& > c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=hLt5iDJpw7ukqICc0hoT7A > &m=xPuRgNJ7XqUv2y23lo-jodi1lW8oPwP-ZWnWxJHrpJE&s=i4FEaExODAwpnFJQR3e6O > 36ktmC3FMS47b1UywCuKlI&e= > > A diff from the previous version is available at: > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_rfcd > iff-3Furl2-3Ddraft-2Dfarrel-2Didr-2Dbgp-2Dls-2Dregistry-2D01&d=DwICAg& > c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=hLt5iDJpw7ukqICc0hoT7A > &m=xPuRgNJ7XqUv2y23lo-jodi1lW8oPwP-ZWnWxJHrpJE&s=7GEPMinWav-18F06WFmdw > 7SgfQg3n0cgNlMwWK1pOCQ&e= > > > Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > https://urldefense.proofpoint.com/v2/url?u=ftp-3A__ftp.ietf.org_intern > et-2Ddrafts_&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r= > hLt5iDJpw7ukqICc0hoT7A&m=xPuRgNJ7XqUv2y23lo-jodi1lW8oPwP-ZWnWxJHrpJE&s > =IlXninzcXMEA64Whqq0Lu0psLnm57lYZSTLOg0dbPJY&e= > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mail > man_listinfo_i-2Dd-2Dannounce&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-n > db3voDTXcWzoCI&r=hLt5iDJpw7ukqICc0hoT7A&m=xPuRgNJ7XqUv2y23lo-jodi1lW8o > PwP-ZWnWxJHrpJE&s=lB5_82MdDfY71CZaIl5KCSjrLUf823qSf16l8uu-EB4&e= > Internet-Draft directories: > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ietf.org_shado > w.html&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=hLt5iD > Jpw7ukqICc0hoT7A&m=xPuRgNJ7XqUv2y23lo-jodi1lW8oPwP-ZWnWxJHrpJE&s=h1qZh > Df_9V-RiTRaBSdkcIqtk1eLBDoq63Z_U0XLpYo&e= or > https://urldefense.proofpoint.com/v2/url?u=ftp-3A__ftp.ietf.org_ietf_1 > shadow-2Dsites.txt&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWz > oCI&r=hLt5iDJpw7ukqICc0hoT7A&m=xPuRgNJ7XqUv2y23lo-jodi1lW8oPwP-ZWnWxJH > rpJE&s=TXmVN0zz6g0IT2v2aS4u2HZwPuq0Mj5AshgV4MCs4sw&e= > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mail > man_listinfo_idr&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoC > I&r=hLt5iDJpw7ukqICc0hoT7A&m=xPuRgNJ7XqUv2y23lo-jodi1lW8oPwP-ZWnWxJHrp > JE&s=8jy4XcQxEbAIMIuFA0l9SrXl0bCu66z0XXvJ0VoJSF0&e= > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mail > man_listinfo_idr&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=hLt5iDJpw7ukqICc0hoT7A&m=xPuRgNJ7XqUv2y23lo-jodi1lW8oPwP-ZWnWxJHrpJE&s=8jy4XcQxEbAIMIuFA0l9SrXl0bCu66z0XXvJ0VoJSF0&e=
- [Idr] Update to update to BGP-LS registries Adrian Farrel
- Re: [Idr] Update to update to BGP-LS registries Ketan Talaulikar (ketant)
- Re: [Idr] Update to update to BGP-LS registries John Scudder
- Re: [Idr] Update to update to BGP-LS registries Ketan Talaulikar (ketant)
- Re: [Idr] Update to update to BGP-LS registries Adrian Farrel
- Re: [Idr] Update to update to BGP-LS registries Donald Eastlake