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

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 08 August 2019 12:24 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 A9AF112017C for <idr@ietfa.amsl.com>; Thu, 8 Aug 2019 05:24:22 -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=DH9LMPns; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=wH++KFib
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 immR9LPKeM_T for <idr@ietfa.amsl.com>; Thu, 8 Aug 2019 05:24:20 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C95912001A for <idr@ietf.org>; Thu, 8 Aug 2019 05:24:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=34494; q=dns/txt; s=iport; t=1565267060; x=1566476660; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=GG/UfW7k4glSysnYj6aMaadGjruMH9qkbve2In/jDac=; b=DH9LMPnsR/3lU8eRKW9+B2yek4VVsO5eYITlANa31Nytpv4zMi4O5oyQ 9ZyfmCnVhN/sDrUdz812ZnAiwbiM3ABKQfJwwqO/Ewj3wnmRL8mSdTJ6g KKiX0DJKEJgmvfcyCByZEkc85bnGyEkiyTpq5zn3i8JTlro4TSQvCaM5K M=;
IronPort-PHdr: 9a23:DZIPQR1cvPDQg/bIsmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxGOt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQCkDnJfj2Ryc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANAAAHFExd/5xdJa1hBRoBAQEBAQIBAQEBBwIBAQEBgVQEAQEBAQsBgRUvJCwDbVUgBAsqhB6DRwOLNIJbfpZigS6BJANUCQEBAQwBASAJBAIBAYQ/AheCPyM1CA4BBAEBBAEBBAEKbYUnDAkIhTkBAQEBAxILBgoTAQEpAwsBDwIBBgIRBAEBIQcDAgICMBQJCAIEAQ0FCBqDAYEdTQMdAQIMkA2QYQKBOIhgcYEygnoBAQWFFxiCFAmBNAGIRYMeF4FAP4ERRoIXNT6CYQQYgTsOKwkIgk0ygiaKKIRnhQiIfY4qCQKCHYZfjWWCMG2GQo5XjVCHXZAcAgQCBAUCDgEBBYFSAzOBWHAVO4JsCYI5DBeDTopTcgEBE4EUi3ABAQ
X-IronPort-AV: E=Sophos;i="5.64,361,1559520000"; d="scan'208,217";a="303400833"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 Aug 2019 12:24:10 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x78COAxT011918 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 8 Aug 2019 12:24:10 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 8 Aug 2019 07:24:09 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 8 Aug 2019 07:24:09 -0500
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 8 Aug 2019 07:24:09 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Cnyvbnm41quzMaPwnvoI/F54BUQ6UknyvwZvCw7mHjTcxuTodEYLUdNkkdXg2r7z4VrUhsQb/MyOAdSGPbqeKzy+s3k7IOXSSb81uai+zHMaEYy4Wp7nNBtUbxX5mVCbO+xHv0Ro388G6CAhIhRQxeL5DxpkJOSeORd74ArZzQtjSVGh0qm/2pF5oSsdnYaprRVKL3QwMD2ToZq3X96rjZwar1aPatIbVbvW0QpxIoSrNQwYenVGruT9MxBVNt3Hy6f+xcSKQP8rXK1+Ug8dvx5NpSaez9rW8gJ3uQARAxDQOlgLic6HhyDLL/6/SafJQKkL7ivl4dk2HkrYKJQl4Q==
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=GG/UfW7k4glSysnYj6aMaadGjruMH9qkbve2In/jDac=; b=jdmWWS/SfhtFoJIgDAFOd4Y0HTxkBOjWVh2R3jfFBFagYLOySxIQLZxL2kgvYF3OWIzfYx795IDTpb0IiiFuBCe59XbVhAqUeXL5Ty3LvGDzWwLEknkX//+3TDEx0d9vAs6xl5d09nQdO6QW8AxBbK5uIsjFu4TqQ4OLXWfzRs0kOZaAxdM3eX0VLLBQBVojwlRFoS4JqKg+OGRs0Ny3QcyUsyDAr3tGvKTk/+yqAQpNmMTnTaQYxbGYQJELrzETZuRGAO8vdOb+rvjj7G59gxoHHmDmbmza4j+Pyd5wo86x6oArF6wTXvnJodsxoTYnplJxUbzWct447XZtESCTNg==
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=GG/UfW7k4glSysnYj6aMaadGjruMH9qkbve2In/jDac=; b=wH++KFibovk9UP2iB/csNBeIoFM9ZQeUCFZsYtK5aP/Fjz4RY8+/fKngFzNy4afdKyUIavrq00e9CErH93GpgghnzByUej/E+yEZA5LQaj8DBUNh5cwkSkarp7+c93EroFmjkQ6Rk0LDsNCRRe0cpSwbFZ8LZTJEKh5AT62sfSw=
Received: from BYAPR11MB3558.namprd11.prod.outlook.com (20.178.206.75) by BYAPR11MB3749.namprd11.prod.outlook.com (20.178.238.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2157.18; Thu, 8 Aug 2019 12:24:07 +0000
Received: from BYAPR11MB3558.namprd11.prod.outlook.com ([fe80::3d73:9b60:6c26:2d0c]) by BYAPR11MB3558.namprd11.prod.outlook.com ([fe80::3d73:9b60:6c26:2d0c%6]) with mapi id 15.20.2136.018; Thu, 8 Aug 2019 12:24:07 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'John Scudder' <jgs=40juniper.net@dmarc.ietf.org>
CC: "idr@ietf.org" <idr@ietf.org>, 'Hares Susan' <shares@ndzh.com>
Thread-Topic: [Idr] WG adoption of draft-farrell-idr-bgp-ls-registry-02.txt
Thread-Index: AQHVRBN2QAWZjK+8H0G6IjONTt4ntKbsvJmAgABkXICABALwcIAAEsGAgAAIw3A=
Date: Thu, 08 Aug 2019 12:24:07 +0000
Message-ID: <BYAPR11MB3558008E8ED9116CCEEEF9CFC1D70@BYAPR11MB3558.namprd11.prod.outlook.com>
References: <1564187800_127314@FUMC-WEB2> <046501d54ba2$6169da90$243d8fb0$@olddog.co.uk> <28C69218-A611-4291-B1D7-9281B627E77B@juniper.net> <BYAPR11MB3558B6C771F1DF0A5A6412C2C1D70@BYAPR11MB3558.namprd11.prod.outlook.com> <01d001d54ddf$683c0f70$38b42e50$@olddog.co.uk>
In-Reply-To: <01d001d54ddf$683c0f70$38b42e50$@olddog.co.uk>
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: [2001:420:c0e0:1005::2b8]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 01eb8d70-0517-4858-b22f-08d71bfb4f5a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB3749;
x-ms-traffictypediagnostic: BYAPR11MB3749:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BYAPR11MB3749A1CEA3340FD13A6B04B7C1D70@BYAPR11MB3749.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 012349AD1C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(366004)(39860400002)(396003)(136003)(376002)(189003)(199004)(53754006)(606006)(2501003)(76116006)(316002)(7736002)(66946007)(6246003)(64756008)(53936002)(25786009)(4326008)(236005)(74316002)(66446008)(66476007)(66556008)(54906003)(110136005)(8936002)(9326002)(81156014)(8676002)(81166006)(9686003)(99286004)(5660300002)(55016002)(6306002)(790700001)(229853002)(2906002)(6116002)(54896002)(7696005)(446003)(966005)(11346002)(476003)(14454004)(71200400001)(71190400001)(186003)(76176011)(102836004)(6506007)(53546011)(52536014)(486006)(478600001)(256004)(14444005)(86362001)(33656002)(6436002)(46003); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3749; H:BYAPR11MB3558.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: n19RyvTG9OLIc6NDI8gfXG0Wge1FP7mDJ4EaDCtlBe/6FRIm50gEqSG+anMWbPgeCT1o8nxkCWe+o/so9VZv4nvZk6YVFYcQvQG2K79ATnTlIZfNtArZN0ZE5t0MZs7OUoYHCGQjORjEGkIX3LZAgVT0ts4yp/xm/EqBwq1VBEGWg3mAcpRGuU8dfd+fdgu/17Mc6D0jxjpX05AgSaqgxOgjD7nQYrb4kYYSue8AKtpU5Yb8OxLmD4+ztPetoKpQtLdYmiRkcMYPLGK5kEZArWukfbMtBs17YQusLpWaP5iGoINDIRRgPG9bVsftXvKKOZfp6V9W9ZEd0NHiQsv4LfmeAbgZklECk7I8ObtMcaz7yjZMFtUEfiSIsdqQhsoBOPNIWF5qS/Cy33uFKxqlHxMqLq5ic4SjSGM2OrH/Iug=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB3558008E8ED9116CCEEEF9CFC1D70BYAPR11MB3558namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 01eb8d70-0517-4858-b22f-08d71bfb4f5a
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Aug 2019 12:24:07.6570 (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: ketant@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3749
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ZtaNI0zSAxUdVykqNDeGM2rndKc>
Subject: Re: [Idr] WG adoption of draft-farrell-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: Thu, 08 Aug 2019 12:24:23 -0000

Hi Adrian,

Thanks and I’ll work with you on similar updates to 7752bis offline.

Regarding the speed of progression of drafts and how urgently we should get this change in place, I will defer to the Chairs on how to proceed 😊

Thanks,
Ketan

From: Adrian Farrel <adrian@olddog.co.uk>
Sent: 08 August 2019 17:20
To: Ketan Talaulikar (ketant) <ketant@cisco.com>; 'John Scudder' <jgs=40juniper.net@dmarc.ietf.org>
Cc: idr@ietf.org; 'Hares Susan' <shares@ndzh.com>
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=