Re: [Idr] Update to update to BGP-LS registries

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Fri, 26 July 2019 15:50 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 CB696120044 for <idr@ietfa.amsl.com>; Fri, 26 Jul 2019 08:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=d6vWiYVE; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=OZU3n9Of
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 VZerX0K8Ym4T for <idr@ietfa.amsl.com>; Fri, 26 Jul 2019 08:50:07 -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 7366B120041 for <idr@ietf.org>; Fri, 26 Jul 2019 08:50:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3271; q=dns/txt; s=iport; t=1564156207; x=1565365807; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=4NcrNqRxrQ6XlaI7FexsiQSAUUotJS1j3cDJtQWH/Uk=; b=d6vWiYVE2nabmvcCaKe7iaO/EQRL8USGuNm52L8s4YYncody5KGlHSFb VxgPA6BJDawxntF3+zykSP6A3Wf99GI9PRNGJuROQiFRfnbBWvDWeBHrf EOGLdhzIRmA1mFOZUkHOWd0tYunu5FL0LwOnE7vnGf6NWaOg++3GpeCf3 4=;
IronPort-PHdr: 9a23:rq6L6BEGf7gOPRqJjezFr51GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4w3Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+ef3ncyU8AOxJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CHAADVIDtd/4UNJK1lHAEBAQQBAQcEAQGBUwcBAQsBgUNQA21VIAQLKodlA4RSiC1Mgg+XU4EugSQDVAkBAQEMAQEYDQgCAQGEQAKCYiM0CQ4BAwEBBAEBAgEGbYUeDIVKAQEBAQMBARAoBgEBKQMMCwQCAQgRBAEBHxAnCx0IAQEEARIIARmDAYFqAx0BDqBTAoE4iGCCI4J6AQEFgTIBAwIOQYMBGIITCYE0AYRxhm0XgUA/gRFGgh4uPoJWCwEBAQEBARaBSTCDC4ImqnkJAoIahlmNUoIubYY4jjqNO4ExhhmEWIszAgQCBAUCDgEBBYFQOCqBLnAVGiGCbAmCOYNxhRSFP3IBgSiLBCqCKAEB
X-IronPort-AV: E=Sophos;i="5.64,311,1559520000"; d="scan'208";a="298358880"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Jul 2019 15:49:56 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id x6QFnujl030407 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 26 Jul 2019 15:49:56 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 26 Jul 2019 10:49:55 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 26 Jul 2019 10:49:55 -0500
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 26 Jul 2019 10:49:55 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IThHGGfy6Wj/wIER6v5Xw+2PuzQrjk+bTwoT2qbuMTvMdKJ4oXDTqx3OqUf0TfaMwVijDLKRqcey+VQaL6rFrYJCdUsxt+/ANHyAgI+dE6PKjgRwq9WVFilF4njJ3tZb/mrc8q7eUiKkd/X9MKOl3hbf3nFtivqauSdr35rvAhiz5SpNOVXYIxKnTfabBRVXEw+JvefemqwyVr3iP71rxX5QjdDpsmdkznCrU2EQX6YuDZdQuaqHdwI2ETJQGal1uLVmyzcquihu898qdZ+xbHwTRoDl0dZ14+FQRAhDHuDwGlrw6U/ZXvvLc8ySUnLkVZ5mv9RZRY9ukzYcVz5/zw==
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=Q9ghTsvXO1aVyNtw8hBOFa2V946WgiUCpIZfGvT7O68=; b=ZCLdXV62WnMO/H+Ttg0agmerNOq7/R/H5TqB3xV7k4NmIIAWF4PexsnwjUke7b24QWs06+dx95BabSSSsOrzthkALtc9fIaWaBbmqzgE7EbWTXh3yN5Y/s5w8oTLg8C3n8DMuFqboJJavGtS0q+NTMfzJq8XYUVEC95kOK6SvN3oXEeIpJCL3qNShsET0qKdiOjZUCNo97+jimgKcnaTvqALstXd1ryHI5T7+/b7qLJ7PF2D+i+om+gdb1/tyBbEx++SoMHfccIUAA0wSyGVjigFPAAzPd2KNY2/frC5kUZkcLzMnu9EUWUz4QCOb9Nd5InYnp34cxoqCE0PM5oyTg==
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=Q9ghTsvXO1aVyNtw8hBOFa2V946WgiUCpIZfGvT7O68=; b=OZU3n9OfCXffEmmGRrJiUdyhDJEVKFdjZZD3FBiMnlkTaj280j3uzV6OkMxrQ4nOgFqaiwJQUf1KDxoGJ6KaYvSEuhJ3R7pfrT85Rqi75n0ZptiIWxBbRmBE0wEcpcU8NApBREpEzHKEE3dlCRVCOeTjV+rqr0U1tE/iUj9FPLE=
Received: from DM5PR11MB2027.namprd11.prod.outlook.com (10.168.103.22) by DM5PR11MB1642.namprd11.prod.outlook.com (10.172.36.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.16; Fri, 26 Jul 2019 15:49:53 +0000
Received: from DM5PR11MB2027.namprd11.prod.outlook.com ([fe80::2ce9:4479:69b6:d12c]) by DM5PR11MB2027.namprd11.prod.outlook.com ([fe80::2ce9:4479:69b6:d12c%4]) with mapi id 15.20.2094.013; Fri, 26 Jul 2019 15:49:53 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'idr wg' <idr@ietf.org>
Thread-Topic: [Idr] Update to update to BGP-LS registries
Thread-Index: AdVDv/GTv6HGmnXrRCKmrXif4UTtawACR2IA
Date: Fri, 26 Jul 2019 15:49:53 +0000
Message-ID: <DM5PR11MB2027839B3DD1CE0786AF3289C1C00@DM5PR11MB2027.namprd11.prod.outlook.com>
References: <0b0a01d543bf$f5336ba0$df9a42e0$@olddog.co.uk>
In-Reply-To: <0b0a01d543bf$f5336ba0$df9a42e0$@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:c0c8:1002::bb]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 95258512-55c5-4aee-d4fc-08d711e0e6d0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM5PR11MB1642;
x-ms-traffictypediagnostic: DM5PR11MB1642:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <DM5PR11MB1642F3ADD6D7E7A39613C481C1C00@DM5PR11MB1642.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01106E96F6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(39860400002)(346002)(136003)(366004)(396003)(199004)(189003)(13464003)(5660300002)(14454004)(66446008)(52536014)(86362001)(256004)(64756008)(2906002)(66476007)(2420400007)(14444005)(66556008)(76116006)(66946007)(15650500001)(110136005)(6116002)(229853002)(25786009)(99286004)(478600001)(81156014)(81166006)(8936002)(966005)(71190400001)(71200400001)(316002)(486006)(68736007)(66574012)(74316002)(6306002)(305945005)(6246003)(6436002)(476003)(55016002)(446003)(11346002)(46003)(9686003)(53936002)(8676002)(53546011)(33656002)(76176011)(102836004)(6506007)(7736002)(186003)(7110500001)(7696005)(2501003); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1642; H:DM5PR11MB2027.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: r9kNCGiyjasVV2RRv0qmJiZMpsTWjlX9PbDHFPl6VDALOWKAH7oTRKEHjTYMeHkFfR2mUw80o7wGYaI73LmEvsWlywyeNnr/wwDLb9gJoQyQ4y1wpOSJmZz0cuHQW9XwjcYgggyL5BRwvZ1ZaPzH8Mcb4IdBPJG3lrO/+8ZE3n/371UyLwrn1Lm0D5s/dc3fVAz6K6KtCkQ0AEGnaNMZENNmElUcPPYji07cNTyPVat88hu2ZgYOT4XdlTx4+pD1UfbVN1G8JPjT5ABoUbctAU92jsqs+qNfwY/jvjRh00BV8r/86b/qdeYxzLU7VxYrnYRWuJX3YrsExiE66l+g1Gpgvqmd4QNeWwBz34vOKirznxKcTzolTnB7zU4GMh2I2Ufxv52bsiID2Kcv4cDAmwK0hqj+X/eRo6B0tdq4uOA=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 95258512-55c5-4aee-d4fc-08d711e0e6d0
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jul 2019 15:49:53.6814 (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: DM5PR11MB1642
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.17, xch-aln-007.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/F0LX75YeYgjCmYGo30WaKn20IUw>
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 15:50:10 -0000

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://datatracker.ietf.org/doc/draft-farrel-idr-bgp-ls-registry/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-farrel-idr-bgp-ls-registry-01
https://datatracker.ietf.org/doc/html/draft-farrel-idr-bgp-ls-registry-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-farrel-idr-bgp-ls-registry-01


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:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

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