Re: [Idr] WG adoption of draft-farrel-idr-bgp-ls-registry-02.txt

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Sat, 02 November 2019 06:10 UTC

Return-Path: <ketant@cisco.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 0FACB12013B for <idr@ietfa.amsl.com>; Fri, 1 Nov 2019 23:10:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=j5ZfJ9Es; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=m9ZFxu1G
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 lzANorQXT_NN for <idr@ietfa.amsl.com>; Fri, 1 Nov 2019 23:10:08 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95A1912012A for <idr@ietf.org>; Fri, 1 Nov 2019 23:10:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=49580; q=dns/txt; s=iport; t=1572675007; x=1573884607; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=dCXbNzYRFTcdiofBb2f+w6Ly1yMoui5SRvNMGzGznxk=; b=j5ZfJ9EsQCQmtpEe9L7jtrOoIABZFvq4/FbVzN4snwP8DXo+9X9Rrj8M 4vmw8kGHHu1fyqr/5sSfGSC0f4WLZHdD7SnRbbciKKEZTHvFcJYC3e023 ArNvUSdfwnWmaE4PMfwDEY+Mgd5/DD246X0c8ZZaeiCt5xSQah+0T0x6X Q=;
IronPort-PHdr: =?us-ascii?q?9a23=3A9H43bxWwfnUCP/lSFqhu3RLM4DDV8LGuZFwc94?= =?us-ascii?q?YnhrRSc6+q45XlOgnF6O5wiEPSANSJ8OpK3uzRta2oGXcN55qMqjgjSNRNTF?= =?us-ascii?q?dE7KdehAk8GIiAAEz/IuTtank5EdhLUkNN9HCgOk8TE8H7NBXf?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AjAQB3Hb1d/5ldJa1mGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBEQEBAQEBAQEBAQEBgX2BHC8kBScFbFggBAsqhCmDRgOKdIJ?= =?us-ascii?q?ef5Z+glIDVAkBAQEMAQEgCQQCAQGEQAIXg2QkOBMCAwsBAQQBAQECAQUEbYU?= =?us-ascii?q?3DAkFA4VAAQEBBBILBgoTAQEpAwIJAQ8CAQgRAwEBASEBBgMCAgIwFAkIAQE?= =?us-ascii?q?EAQ0FCBcDgwGBeU0DLgEOpVYCgTiIYHWBMoJ+AQEFhRoYghcJgTaFGINbgx4?= =?us-ascii?q?YgUA/gRFGghc1PoJiBBiBSQwSDQkIglIygiyKd4UGhTuJOY8ECoIkhxGOQII?= =?us-ascii?q?8coZoj0+OQogukSYCBAIEBQIOAQEFgWkigVhwFTuCbAlHERSDBgwXgQQBCYJ?= =?us-ascii?q?CilN0AQETgRONRQEB?=
X-IronPort-AV: E=Sophos;i="5.68,258,1569283200"; d="scan'208,217";a="658344876"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Nov 2019 06:09:48 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id xA269mp3031154 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 2 Nov 2019 06:09:48 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 2 Nov 2019 01:09:47 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 2 Nov 2019 02:09:46 -0400
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sat, 2 Nov 2019 01:09:46 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RMAv0SdEKESN93wEh4PrlE23Brt//WPf3GhduZ5Sk9fS3XFhhk0rEvZZbtl81MeVhD4Ls6kgYfoDcoU+HTwdxfLqDbxi+zeiaidbckdF6HgjdulknQfUygLx7FJWA47WHl/KKZCvwhxndCi/FRo7oIRGcB0N6ykM6bq2eslGTdEJl30oAHSs0E5ZJl2MNurVSd+avMYv5jH9EuOKjJ/rCPeKojzttQjUEXdzVY/SRySHJ+n7Aqg7gNueovUVd8eEbSO+GDCd2MT+Rn9gU6vQWlEHmUT+aN08aRvkNQ/Qf5Z/OYvS4H2q/Pd6uKv3SX6RTH1mCQICRDbXv7zhdhJxUw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=dCXbNzYRFTcdiofBb2f+w6Ly1yMoui5SRvNMGzGznxk=; b=XClPNSQ4ZK6ViaUSmmLsIbzdFMv5FeiYWfC6dLNGfojAlXlAIYqoj9Dqg0GuWEN6sbj+DPXuvxefuZgpuFxLUHjG9+Ij24bkKbPIh4A7lIIZLRt6Wzq9r90Ns/WCCV4ZL6E1dCnF7JwAuhb9PYtfbE/a/A2/yv5K99HJmab+lHOeV1kWsYwIdU77kItT7WTEVHynqTShVNUhldhDQCuBxncAoxEAjAESTc5bkZ65ZBGoujYzidpkhBDLzv+SBn1JjL4TFq7eBN5ITffw8R9y56P3xixh89u1n4kdfkjxryQMq+4nHyoOL0s12C0loMGowX8P8Lbsk2fj6Hfdn7AxUQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=dCXbNzYRFTcdiofBb2f+w6Ly1yMoui5SRvNMGzGznxk=; b=m9ZFxu1GwrVmPBrCmr0qVHgjdkbJzLfSMdUXIZgeqN6g/i/JO5di9ej4pHsQDERd1tysu0knAdrqrM4e5WRrIW8jH4Z9aXswyTk3Z9Iy3Gpu7u1D27l6MPQ8qlqfCxymd1qTh+G6IOgPm0BAmgDvgh8JuP8lhi8O0qCHOhVDzkI=
Received: from CY4PR11MB1541.namprd11.prod.outlook.com (10.172.68.150) by CY4PR11MB1909.namprd11.prod.outlook.com (10.175.61.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.22; Sat, 2 Nov 2019 06:09:44 +0000
Received: from CY4PR11MB1541.namprd11.prod.outlook.com ([fe80::d3a:84a6:be65:e33f]) by CY4PR11MB1541.namprd11.prod.outlook.com ([fe80::d3a:84a6:be65:e33f%11]) with mapi id 15.20.2387.028; Sat, 2 Nov 2019 06:09:44 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, Susan Hares <shares@ndzh.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "'John Scudder'" <jgs=40juniper.net@dmarc.ietf.org>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] WG adoption of draft-farrel-idr-bgp-ls-registry-02.txt
Thread-Index: AdWRALeK+IyxU/wYTFGXRiiFdBAzMgACZ60A///GnAD//1MnsA==
Date: Sat, 2 Nov 2019 06:09:44 +0000
Message-ID: <CY4PR11MB154133D0BF6D96D4AEA705C7C17D0@CY4PR11MB1541.namprd11.prod.outlook.com>
References: <00b801d59102$0b7b26c0$22717440$@olddog.co.uk> <011501d5910a$572a0610$057e1230$@ndzh.com> <C2558FB8-8E43-4C90-B208-096F25EE659E@cisco.com>
In-Reply-To: <C2558FB8-8E43-4C90-B208-096F25EE659E@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ketant@cisco.com;
x-originating-ip: [2405:201:1800:c766:3561:9fe4:5e7b:45f6]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0ce5b23b-302e-42ad-5cd9-08d75f5b41cc
x-ms-traffictypediagnostic: CY4PR11MB1909:
x-ms-exchange-purlcount: 1
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <CY4PR11MB190957E96DE265A950B21097C17D0@CY4PR11MB1909.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0209425D0A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(346002)(396003)(136003)(39850400004)(376002)(53754006)(199004)(189003)(6306002)(55016002)(54896002)(316002)(236005)(66556008)(76176011)(7696005)(76116006)(229853002)(4326008)(74316002)(25786009)(52536014)(5660300002)(66946007)(606006)(14454004)(6246003)(6436002)(66476007)(478600001)(99286004)(7736002)(966005)(64756008)(102836004)(46003)(186003)(86362001)(81166006)(11346002)(256004)(33656002)(110136005)(81156014)(9686003)(476003)(446003)(2501003)(790700001)(71190400001)(71200400001)(8936002)(14444005)(6116002)(53546011)(6506007)(486006)(2906002)(66446008)(8676002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR11MB1909; H:CY4PR11MB1541.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: MhS+15+Mx9cvn/4m5E8wgWVgjDuZ5avJE3K6GxZNryrsDYCXBmyHqFTcqGLBhzJM2921msl9EliZJ9rOkmNfqqRlDbzxz26hEerVXHYF4ZsJuFxB5Ij3tjo/tiGDfgdR7PNST8TXK8C3YQSzOuoY/M8vs8E9bp4xDUUYq/rkHjkBcvjdTuKu9VXFw+TA/FdCaORNPRe9ycooZK9xs4+6WNev3jNTiapuR1MhRTfhj9R953sdVco2DEkdZOc35DIpD6vbol/U25WIE8Y1pthAgamYNcd5nq5S49NANtDgekLwxsJVKj5hBuxETTAB4uVE2IDkJLD5dMjAqd0tqgKEpy/ftYA0Cj4iDWzG4weF+IMIA4psEzuT3VbHnQeKfDd4+IEQC8Yc8ZtTDuBJg5TNZcdFbo+dU3wWQDr03/ejqfG7C+dg91OLOiXZVged3os1R+5jXofjGWCwW6gYpS2BntofJfg60w0Njok2vd/NvH4=
Content-Type: multipart/alternative; boundary="_000_CY4PR11MB154133D0BF6D96D4AEA705C7C17D0CY4PR11MB1541namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0ce5b23b-302e-42ad-5cd9-08d75f5b41cc
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Nov 2019 06:09:44.5120 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /W6wWPIYMPgyScgwbjUVvB0FHgGPh6xnjl3ablUhc32o6B006sJ92+/R0E0mDrMMKBP1jGykoFHErLugCOp1uw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR11MB1909
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/3835hqk0kJAl8n6-0Nro22SSy50>
Subject: Re: [Idr] WG adoption of draft-farrel-idr-bgp-ls-registry-02.txt
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: Sat, 02 Nov 2019 06:10:12 -0000

+1 (and I had indicated the same during the adoption call as well)

From: Idr <idr-bounces@ietf.org> On Behalf Of Acee Lindem (acee)
Sent: 02 November 2019 05:21
To: Susan Hares <shares@ndzh.com>om>; adrian@olddog.co.uk; 'John Scudder' <jgs=40juniper.net@dmarc.ietf.org>
Cc: idr@ietf.org
Subject: Re: [Idr] WG adoption of draft-farrel-idr-bgp-ls-registry-02.txt

FWIW – I support adoption…
Thanks,
Acee

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> on behalf of Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Date: Friday, November 1, 2019 at 7:16 PM
To: Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>, 'John Scudder' <jgs=40juniper.net@dmarc.ietf.org<mailto:jgs=40juniper.net@dmarc.ietf.org>>
Cc: IDR List <idr@ietf.org<mailto:idr@ietf.org>>
Subject: Re: [Idr] WG adoption of draft-farrel-idr-bgp-ls-registry-02.txt

Adrian:

This one dropped through an open gap in the IDR calls.   I got a medium amount of response for adoption.   I will start a call indicating the chairs intend to adopt later this evening.   Please plan to attend IDR for first session.

Thanks!

Sue

From: Adrian Farrel [mailto:adrian@olddog.co.uk]
Sent: Friday, November 1, 2019 6:17 PM
To: 'Susan Hares'; 'John Scudder'
Cc: idr@ietf.org<mailto:idr@ietf.org>
Subject: RE: [Idr] WG adoption of draft-farrel-idr-bgp-ls-registry-02.txt

Hello chairs, WG,

I may have taken my eye off the IDR list for a while, but it seems to me that my draft is languishing.

Did the WG last call complete? Did we decide to adopt or discard?

Thanks,
Adrian

From: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Sent: 09 August 2019 16:15
To: adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>; 'Ketan Talaulikar (ketant)' <ketant@cisco.com<mailto:ketant@cisco.com>>; 'John Scudder' <jgs=40juniper.net@dmarc.ietf.org<mailto:jgs=40juniper.net@dmarc.ietf.org>>
Cc: idr@ietf.org<mailto:idr@ietf.org>
Subject: RE: [Idr] WG adoption of draft-farrell-idr-bgp-ls-registry-02.txt

Adrian and WG:

<WG chair hat on>
Ketan and his co-authors have been carefully working RFC7752bis
prior to adopting in the WG.  However, given the comments to the list –
I would like to make sure the WG is not rushed to address all known
Issues in RFC752.

We can usually send through registry drafts quickly.

The WG can progress both drafts in parallel.
<Chair hat off>

<wg member hat on>
I suggest we put both drafts as one of our
Key milestones for IDR.
<wg member hat off>

Cheers, Sue



From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Adrian Farrel
Sent: Thursday, August 8, 2019 7:50 AM
To: 'Ketan Talaulikar (ketant)'; 'John Scudder'
Cc: idr@ietf.org<mailto:idr@ietf.org>; 'Hares Susan'
Subject: Re: [Idr] WG adoption of draft-farrell-idr-bgp-ls-registry-02.txt

Hi Ketan,

Yes.

We’re assuming that 7752bis will take a while to progress through the working group (I might be wrong) while we could advance draft-farrel-idr-bgp-ls-registry pretty fast.

If I’m wrong we should simply roll my draft into 7752bis and be done.

If I’m right:
•        My draft runs to completion
•        7752bis needs to obsolete 7752 and the RFC that my draft will become, and the IANA section has to be updated to reflect what the registry will say at that time.

Best,
Adrian

From: Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>>
Sent: 08 August 2019 11:47
To: John Scudder <jgs=40juniper.net@dmarc.ietf.org<mailto:jgs=40juniper.net@dmarc.ietf.org>>; Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>
Cc: idr@ietf.org<mailto:idr@ietf.org>; Hares Susan <shares@ndzh.com<mailto:shares@ndzh.com>>
Subject: RE: [Idr] WG adoption of draft-farrell-idr-bgp-ls-registry-02.txt

Hi All,

I obviously support this “easing of process overhead” for BGP-LS code point allocations. Apologies for not responding earlier.

Adrian, can you please also let know if the same text needs to be also updated in draft-ketant-idr-rfc7752bis which is also up for WG adoption and would result in obsoleting RFC7752?

Thanks,
Ketan

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of John Scudder
Sent: 06 August 2019 02:57
To: Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>
Cc: idr@ietf.org<mailto:idr@ietf.org>; Hares Susan <shares@ndzh.com<mailto:shares@ndzh.com>>
Subject: Re: [Idr] WG adoption of draft-farrell-idr-bgp-ls-registry-02.txt

Well obviously I (with my “working group member” rubber mask and fright wig) kind of want them but I was holding off on saying so because that's kind of obvious.

To reiterate for others’ benefit why I think this is worthwhile vs. early allocation:

- It reflects the author’s original intent, for whatever that’s worth. (The WG’s current intent is more important.)
- It provides the minimum of red tape, less even than early allocation.
- Because the number space is large, resolving the tension between red tape and the risk of something silly being allocated in favor of permissiveness is OK.
- Let’s not forget there’s still at least two humans in the loop (the Designated Expert and IANA).

That said, if the WG can’t generate enough enthusiasm to say “yes please” then I won’t cry, although I also won’t (with “WG co-chair” spangled epaulets and cravat on) feel as sympathetic next time someone tells me it’s too hard to get a code point.

—John

On Aug 5, 2019, at 11:28 AM, Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>> wrote:

Hi WG,

I just want to rattle the bars of the cage a bit, here.

John (reliably) informs me that he had a number of conversations about the BGP-LS registries and their allocation policies: people (it seems) wanted more-relaxed rules.

It is possible that the advocates are the authors of the set of drafts that have just been pushed forward for “early allocation” and so no one cares any more.

Or it is possible that everyone is too busy.

Or, perhaps, no one wants these changes.

Thanks,
Adrian

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Susan Hares
Sent: 27 July 2019 01:37
To: idr@ietf.org<mailto:idr@ietf.org>
Subject: [Idr] WG adoption of draft-farrell-idr-bgp-ls-registry-02.txt

This begins a 2 week WG adoption call for draft-farrel-idr-bgp-ls-registry-02.txt.

Let the discussion begin and in midst of your comments please remember to include "support" or "no support".


Adrian enjoy the discussion.

Cheerily  Sue



Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE smartphone
_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_idr&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=hLt5iDJpw7ukqICc0hoT7A&m=m2Z21XyyBWfE7-JRpCBMd9mW5AU5UenqFDS0r2Wjmi0&s=n3RyYdF5g5JgzuEcUrayd07c_83FTSigaOWGlLpIku0&e=