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

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 08 August 2019 10:47 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 B55C6120135 for <idr@ietfa.amsl.com>; Thu, 8 Aug 2019 03:47:11 -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=NIbgMIAi; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=xITahIi5
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 TkbXNVh4umCv for <idr@ietfa.amsl.com>; Thu, 8 Aug 2019 03:47:09 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AB0812011C for <idr@ietf.org>; Thu, 8 Aug 2019 03:47:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19022; q=dns/txt; s=iport; t=1565261229; x=1566470829; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=A3Lc6oCZDB5oAN060RXbq9ph+hFFrcv2IJKiaJI778A=; b=NIbgMIAiMByS7m1XMjy+8aQVaXU6Q2oe2Pf9b/FFD7rv6LzWwcLuMEbd KMVvebfSur/c5CdSSS0LSpn6ujhSAM6hBGpvTZtN5FLccgnvbBL4vowIt ShUMu13ExpmuolqvGhJ4Q4aavLG9F3T7bib29b9tVaeW+qGfNcIylIyJJ I=;
IronPort-PHdr: =?us-ascii?q?9a23=3AvoGNARy4hlM+01PXCy+N+z0EezQntrPoPwUc9p?= =?us-ascii?q?sgjfdUf7+++4j5YR2N/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZuGBFHyKuLCZC0hF8MEX1hgrDm2?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ATAABz/Etd/4YNJK1mGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBVQMBAQEBCwGBFS8kLANtVSAECyqEHoNHA4szglt+kgiEWoE?= =?us-ascii?q?ugSQDVAkBAQEMAQEgCQQCAQGEPwIXgj8jNgcOAQQBAQQBAQQBCm2FJwwJCIU?= =?us-ascii?q?5AQEBBBILBgoTAQEpAwsBDwIBCBEEAQEoAwICAjAUCQgCBAENBQgXA4MBgR1?= =?us-ascii?q?NAx0BAgygZwKBOIhgcYEygnoBAQWFGRiCFAmBNAGIRYMeF4FAP4ERRoIXNT6?= =?us-ascii?q?CYQQYgUkrCQiCTTKCJoonhGeFCIh7jioJAoIchl2NZIIwbYZCjlWNToddkBw?= =?us-ascii?q?CBAIEBQIOAQEFgVcKJ4FYcBU7gmwJgjkMF4NOilNyAQETgRSNfQEB?=
X-IronPort-AV: E=Sophos;i="5.64,360,1559520000"; d="scan'208,217";a="311381908"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 08 Aug 2019 10:47:08 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x78Al8Hw000360 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 8 Aug 2019 10:47:08 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 8 Aug 2019 05:47:07 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 8 Aug 2019 05:47:06 -0500
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 8 Aug 2019 05:47:06 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FUGmN1X7RrepY+caHcPwJa5Pd6ChFpGyQ9Z0peeVUAmbtkuMj4d/cRoQlYiTOdXiero9ABoLMWa7RU+MxxMzT633M3riOFZQm4GvbYbtQoXk4jW6kIyzqz1zEfWUPi3B/VEyic7uqRI/h05tfhQkJBjtuoXClwlSXX32uvChC0ZzzrFasosihG23IB8g+ft8DZFgWkiOn6jhbccOyMUG6g9Anjs5VCp+u/jdnUjnYxlhP/uoxIb2e23YTmyyXmGzVjwl065NPILLAV35may1Npf04Xl92hmoZ8X+bWiZ//AXmk4WX541LfkI4wBwo+r/xpdC2RQh7T07wYDRpdTXzw==
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=A3Lc6oCZDB5oAN060RXbq9ph+hFFrcv2IJKiaJI778A=; b=KVCXddVV25aLwwV9BL3mocUafsz0y/TXS2Pk4UZ9965PDfViG7gr4CwIYG58NoJ+RaHF2Od/k0OB9czx4Efo7mofVnqFKEHzbh9Fr3mgqfwwOBuQvfBG9EGuB0jrQKlzoaLGdePnyT6MYz2mY1tdJPFFLHGNlg33aUMzxZAEbGB8gapXhG0LqZJNNh3YioHXtBATPjkxc+ytj/3viEOqmW6eKJh4UGpMOIM+PnKzu3hkkU2JwuC63Zm3uVVh/2rhLEJD0C6I7ct0F1nfK+FIlBN+O9ZX+i8IX3Fwktgi/anmQ+6eR8Vk6C8r2jRjJnj8Rr2DO7TVgdf7nlul3urCGA==
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=A3Lc6oCZDB5oAN060RXbq9ph+hFFrcv2IJKiaJI778A=; b=xITahIi5+natgKFBZJj4uiodQwd8n4AwAX4Qgf5YCrBiONCxHOXmlf+q98RGydyfiNfntGH7yKgQ9/4QksEwfFd6ilV05G1QAx7fLKq9Vbffg6PjhM4nlP/u3lOOyA3E/eAlJIffOd8OgBTp1ybKsJo5llLuA0XKnahwqgd/qkc=
Received: from BYAPR11MB3558.namprd11.prod.outlook.com (20.178.206.75) by BYAPR11MB3653.namprd11.prod.outlook.com (20.178.237.78) 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 10:47:05 +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 10:47:05 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: John Scudder <jgs=40juniper.net@dmarc.ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
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+8H0G6IjONTt4ntKbsvJmAgABkXICABALwcA==
Date: Thu, 8 Aug 2019 10:47:05 +0000
Message-ID: <BYAPR11MB3558B6C771F1DF0A5A6412C2C1D70@BYAPR11MB3558.namprd11.prod.outlook.com>
References: <1564187800_127314@FUMC-WEB2> <046501d54ba2$6169da90$243d8fb0$@olddog.co.uk> <28C69218-A611-4291-B1D7-9281B627E77B@juniper.net>
In-Reply-To: <28C69218-A611-4291-B1D7-9281B627E77B@juniper.net>
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:70eb:a4e4:ed89:e1ee]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b44f78ba-9332-4ba1-26c8-08d71bedc10f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB3653;
x-ms-traffictypediagnostic: BYAPR11MB3653:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BYAPR11MB365340FD2BE49282B4084987C1D70@BYAPR11MB3653.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 012349AD1C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(136003)(376002)(366004)(346002)(396003)(53754006)(199004)(189003)(6116002)(790700001)(86362001)(478600001)(8936002)(256004)(2906002)(71200400001)(71190400001)(99286004)(966005)(9326002)(9686003)(14444005)(6306002)(54896002)(14454004)(606006)(55016002)(316002)(7736002)(33656002)(6436002)(6506007)(53546011)(102836004)(25786009)(7696005)(76176011)(6246003)(74316002)(236005)(110136005)(54906003)(53936002)(8676002)(229853002)(66446008)(64756008)(66556008)(66476007)(66946007)(5660300002)(76116006)(446003)(81156014)(486006)(81166006)(11346002)(476003)(52536014)(186003)(4326008)(46003); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3653; H:BYAPR11MB3558.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-message-info: SwkodfSKRXrz63aTa0jLS25byKzSXlMi6lfQIJx0crpkZmn7+rx69fwwXXSBCEMaHqJ3veT/F7mHRqIzEdkuZ39UP5eS2sULn+n3KFzurVg8lbamulLWcFyY+56Tn1SKhGg74dFUOYWAPJNtY9wS2Qf7604TG9m6I7mlkq0hba4SIQss2xB9CJQzVdeVqFmjV+v8yUo11z3tMCMRA9bmd07SzgqbjaW7Ut35kesju2x60Xqf4wlGaHrFW0vwewnr/BfYNAm91UVPbAHsib/kXsnJ9mUP2CVUdt6Tr6MbgpRdRWrir4edGI2uFF1u0SS2mvcGgdAMcqj/LHHOFLdzk9Oykxm9uISwBZUMcXBvD2EYLX7IElFdDUaj0I12qW3Iw2ZzSWBqvFWfJ4Wb5hnfg4QCfy/X09gX0ooXF6p927o=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB3558B6C771F1DF0A5A6412C2C1D70BYAPR11MB3558namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b44f78ba-9332-4ba1-26c8-08d71bedc10f
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Aug 2019 10:47:05.4640 (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: BYAPR11MB3653
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.18, xch-rcd-008.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/UBwUq1HmBGkO4-bvh6SeccPZkOY>
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 10:47:12 -0000

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> On Behalf Of John Scudder
Sent: 06 August 2019 02:57
To: Adrian Farrel <adrian@olddog.co.uk>
Cc: idr@ietf.org; Hares Susan <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=