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

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Fri, 26 July 2019 23:11 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 57A571201C6 for <idr@ietfa.amsl.com>; Fri, 26 Jul 2019 16:11:14 -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=JahjdfWC; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=N1Rod+5C
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 EpZpewCPsh16 for <idr@ietfa.amsl.com>; Fri, 26 Jul 2019 16:11:11 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CA441201D0 for <idr@ietf.org>; Fri, 26 Jul 2019 16:11:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10412; q=dns/txt; s=iport; t=1564182660; x=1565392260; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=mMW1JZbj976BfZFgF/WCuZrqvl3+Ck2jxk3hlCK6Egk=; b=JahjdfWCCYETAhaHaefamTpGWu/VK0TU6AbhELikeqQv7dEugVCaL3fa Zf45bGKSEOGOYm7LFW08cPkc8d2pSfL9iM3K8Iem58fNOp5KP7FdWGAiI vc/FGLjZh3LUTOtwQ3zYlgdxuh3IDY6Wbc3FOn2BPWNvYvSXz0KDWHPb3 U=;
IronPort-PHdr: =?us-ascii?q?9a23=3ACtP8xBbkranOBeTumX9oT2b/LSx94ef9IxIV55?= =?us-ascii?q?w7irlHbqWk+dH4MVfC4el20Q6bRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn?= =?us-ascii?q?1NksAKh0olCc+BB1f8KavpYjAzGthqX15+9Hb9Ok9QS47z?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAADchztd/5RdJa1mGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUwQBAQEBAQsBgUNQA21VIAQLKoQeg0cDhFKILYJbl1O?= =?us-ascii?q?BLoEkA1QJAQEBDAEBJQQEAgEBhEACF4JLIzQJDgEDAQEEAQECAQZthR4MCQi?= =?us-ascii?q?FOQEBAQECARIREQwBASkDCwEEBwQCAQYCDgMEAQEBAgImAgICMBUICAEBBA4?= =?us-ascii?q?FCBqDAYFqAw4PAQ6PZZBgAoE4iGBxgTKCegEBBYFGQYMCGIITCYEMKAGEcYN?= =?us-ascii?q?Qgx0XgUA/gRFGgh4uPoJhAQECAQEWgUmDCTKCJo5+m3sJAoIahlmNUoIubYY?= =?us-ascii?q?4jjqObIYZkAsCBAIEBQIOAQEFgVA4gVhwFRohgmwJgjmDcYUUhT9yAQETgRS?= =?us-ascii?q?KeyqCKAEB?=
X-IronPort-AV: E=Sophos;i="5.64,312,1559520000"; d="scan'208";a="603168164"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Jul 2019 23:10:58 +0000
Received: from XCH-RCD-010.cisco.com (xch-rcd-010.cisco.com [173.37.102.20]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x6QNAw44008278 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 26 Jul 2019 23:10:59 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 26 Jul 2019 18:10:58 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 26 Jul 2019 19:10:57 -0400
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 26 Jul 2019 19:10:57 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MLcrwSsHC+gZ91SF83K12JsuYzHo8bU+NtZjrFLzNKMVd0aG1pMsJFBv7yaDqNl+owd4oTo/MTqmluzENkDQPsx1kAjv5/jhcmhcpPcc5/ZJxp70dkPQVzd5R2Fq0+H9bR/mgojGGp6Aq6q5Lgz9ydlSi5urOAlzmTfIokb/zWSJ76V7i3VCC0UB3roseG3/9KBID+YSNsiIK59XQj23fwWWKlUfn3Ugb4zxEZVogtBVokf1/WDzSL5OeVzZqe+i3n+HJDRyEQi7cDeIwgdWPqNik0InRyup45UeyScKzS4y8xH+ZnHxePDeEcSbMQhN/hixRlkGJDlv247riHbVCw==
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=mMW1JZbj976BfZFgF/WCuZrqvl3+Ck2jxk3hlCK6Egk=; b=FpjOKhpqEdnvhrEBGeHefA0Q4M4WLDEOv7vzQNrUVXn0blVYxH/3FbxGmKN/4COFsdYFKxWfkwJphaLnb74ElUzW3rW4ojFAcC7Xy3S8uEa7e/pWAKJPUWf3RSWQvowGPjyM407I3LhJtQMonBzA7B90cs2yM/X0iRTUwt1/cA9I447U2OUdryYsD78LmQrozfQ+v9AWRDb7DfJvyC/KT0u18uWeyAAHfbJA4aXizEXOslLdzspC46vt3uj6xc7IB6FuZwsNlG3L28QYqH9jRinINGoLEPg0miuEgq9QtPsRczZKiWbwPm0zeL4MkURw2XcXGr2FmVdVdVQWKTSjxw==
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=mMW1JZbj976BfZFgF/WCuZrqvl3+Ck2jxk3hlCK6Egk=; b=N1Rod+5C7s7jduK/0k7KTiwQccw9zKa7AULrlw8opMufeN1w0FKQybKF4IwUFl2Nm91tLoCSmoFDvA7qeyZw/ec7YZf0DxKq2WB6+wOxsZkRgLT3BgyY2Q7AfGIGBi1URRn4Mop0pbmPOXmYgQfrN6gysh6eJuzp4Te3wTvTIbQ=
Received: from DM5PR11MB2027.namprd11.prod.outlook.com (10.168.103.22) by DM5PR11MB1354.namprd11.prod.outlook.com (10.168.108.146) 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 23:10:55 +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 23:10:55 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: John Scudder <jgs@juniper.net>
CC: "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/GTv6HGmnXrRCKmrXif4UTtawACR2IAAALJDIAADGgNYA==
Date: Fri, 26 Jul 2019 23:10:55 +0000
Message-ID: <DM5PR11MB20279E5CFEACA444111D2293C1C00@DM5PR11MB2027.namprd11.prod.outlook.com>
References: <0b0a01d543bf$f5336ba0$df9a42e0$@olddog.co.uk> <DM5PR11MB2027839B3DD1CE0786AF3289C1C00@DM5PR11MB2027.namprd11.prod.outlook.com> <E9AC1BEC-2013-4E93-9E02-0BBF23A2850D@juniper.net>
In-Reply-To: <E9AC1BEC-2013-4E93-9E02-0BBF23A2850D@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: [2001:420:c0c8:1002::bb]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2ef99fd5-ca5a-43bd-7d04-08d7121e8351
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM5PR11MB1354;
x-ms-traffictypediagnostic: DM5PR11MB1354:
x-ms-exchange-purlcount: 8
x-microsoft-antispam-prvs: <DM5PR11MB13545AF51DA3064D63CBF598C1C00@DM5PR11MB1354.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:2201;
x-forefront-prvs: 01106E96F6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(366004)(376002)(396003)(136003)(346002)(189003)(199004)(13464003)(53546011)(66556008)(64756008)(5660300002)(19627235002)(66476007)(6116002)(66446008)(305945005)(6506007)(486006)(14444005)(6916009)(46003)(14454004)(66946007)(256004)(7736002)(76176011)(316002)(7696005)(86362001)(76116006)(71200400001)(2906002)(66574012)(6306002)(8676002)(4326008)(229853002)(561944003)(15650500001)(81166006)(9686003)(446003)(54906003)(55016002)(476003)(81156014)(11346002)(68736007)(478600001)(6436002)(6246003)(71190400001)(1941001)(52536014)(33656002)(74316002)(102836004)(8936002)(99286004)(25786009)(186003)(53936002)(966005); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1354; H:DM5PR11MB2027.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: SZqmYo4Ufa1JzWdV6UEZqvgORBOwOUI6VUXRkBSDnw0AXmf6McJcuMKqVArAykIaH8P9Tw9dKxNa4x8IC651zJ4c2HbGk9fy4aU0ePD022vaD9Q9/CnXz4MP8ZuFi4GZdV78HdLjX6BKC3yr5+zRlM5BWyGqAhJwihmIqVIDZ7b6s8jWq9A4u3X82hhD4MnU5Yniq09g+2ThSe6/v4TAw9SRdN0QknYpMD1dEUB4gWSc92ODhHLZOR8KQ63TgqIZemjESZWBVMmsMASatKLg7ZvZ/VVW4LufsyfjgbcQpnjzEIKKyBQPKqf5h9/45LTCuj5mUhyHSBBzcY7qi2+OOxDVJi7QFd6RkGwZ/x8dLpJuv+m+48hga5yr45thJSReQzlAkLNi5J6pIH422ReRi5y0VZYQvLaY2tQhM6o3iro=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2ef99fd5-ca5a-43bd-7d04-08d7121e8351
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jul 2019 23:10:55.6277 (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: DM5PR11MB1354
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.20, xch-rcd-010.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/dJ3n_8VGC5kYYkBqX4Z6138IZao>
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:11:14 -0000

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=