From nobody Thu Sep 22 17:03:24 2022
Return-Path: <tievens@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id E3DACC14F718
 for <grow@ietfa.amsl.com>; Thu, 22 Sep 2022 17:03:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.606
X-Spam-Level: 
X-Spam-Status: No, score=-14.606 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001,
 RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001,
 RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001,
 T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001,
 URIBL_ZEN_BLOCKED_OPENDNS=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=m8Z+wWIB;
 dkim=pass (1024-bit key)
 header.d=cisco.onmicrosoft.com header.b=lKLGWLKo
Received: from mail.ietf.org ([50.223.129.194])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id wSKKIsIxSmxA for <grow@ietfa.amsl.com>;
 Thu, 22 Sep 2022 17:03:19 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89])
 (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id F259FC14CE37
 for <grow@ietf.org>; Thu, 22 Sep 2022 17:03:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
 d=cisco.com; i=@cisco.com; l=6146; q=dns/txt; s=iport;
 t=1663891391; x=1665100991;
 h=from:to:cc:subject:date:message-id:references:
 in-reply-to:mime-version;
 bh=OlHflIJDsxVcDsbl3K1F2Em7nSZP9jWHaWPrv/nOTQ4=;
 b=m8Z+wWIBApL4AXkLal3yTaVcw61QrZ/TgWQ0sUBcXrJStUYukRU4bJVv
 0qzfLIGEGzHfuewDe+LxJpyIeg+KUvRUzav1WT+WMel3N1EAuxvmxWa73
 1Gwi08zrunmRNqbBh1CoX1/IFG6b7VQ02KcR9zBQ6abqjc/6R+RWn4rpk s=;
X-IPAS-Result: =?us-ascii?q?A0ADAABe9yxjmIQNJK1aGgEBAQEBAQEBAQEDAQEBARIBA?=
 =?us-ascii?q?QEBAgIBAQEBQIE7BQEBAQELAYEgMVJ/Alk6RYgaA4RQX4gWA5BnhWSFGoEsF?=
 =?us-ascii?q?IERA1QLAQEBDQEBQgQBAYUFAoRsAiU0CQ4BAgQBAQEBAwIDAQEBAQEBAwEBB?=
 =?us-ascii?q?QEBAQIBBwQUAQEBAQEBAQEdGQUOECeFaA2GQgEBAQECARIuAQE3AQQLAgEID?=
 =?us-ascii?q?gouMiUCBAENBQgaglsBghZXAw0jAwGfeQGBPwKKH3iBNIEBgggBAQYEBIURG?=
 =?us-ascii?q?II4CYE9AYMxhReDOIQoJxyBSUSBFUOCZz6BBYFdBIFFARqEDIIumRcHNwNEH?=
 =?us-ascii?q?UEDC0I0AxUDFAMFJAcDGQ8jDQ0EFgcMAwMFJQMCAhsHAgIDAgYTBQICTTYIB?=
 =?us-ascii?q?AgEKyQPBQIHLwUELwIeBAUGEQgCFgIGBAQEBBUCEAgCCCYXBxMzGQEFWRAJI?=
 =?us-ascii?q?RwOGg0FBhMDIG8FRA8oMWsrHRsKgQwqKBUDBAQDAgYTAwMiAhAqMRQEKRMSL?=
 =?us-ascii?q?QcrcwkCAyJnBQMDBCgsAwkgBBwHKCY8B1g6AQQDAxAiPQYDCQMCJFqBLigFA?=
 =?us-ascii?q?w0ZJggFIxcdBAg8AgUGVxMCChIDmmIGgTOBPBFuR5JXgluKY6E5CoNYoFQWq?=
 =?us-ascii?q?QSXCiCiFBgBhHMCBAIEBQIOAQEGgWE6gVtwFYMiURkPjiAZg1mKXnUCOQIGC?=
 =?us-ascii?q?wEBAwmKagEB?=
IronPort-PHdr: A9a23:WI6U+h++npSlT/9uWCXoyV9kXcBvk7n3PwtA7J0hhvoOd6m45J3tM
 QTZ4ukll17GW4jXqpcmw+rbuqztQyoMtJCGtn1RfJlFTRRQj8IQkkQpC9KEDkuuKvnsYmQ6E
 c1OWUUj8Wu8NB1eGd31YBvZpXjhhQM=
IronPort-Data: A9a23:7KAWLKPPurhWsmDvrR1Dl8FynXyQoLVcMsEvi/4bfWQNrUon1zcPn
 WAfWT2PP//fMTH9edwgYIji90sGv5SGz4AxQXM5pCpnJ55oRWUpJjg4wmPYZX76whjrFRo/h
 ykmQoCcaphyFBcwnz/1WlTbhSEUOZqgG/ytU4YoBggrHVU+EHZ700o48wIEqtcAbeaRUlvlV
 eza+6UzCHf9s9KjGjtJg04rgEoHUMXa4Fv0jHRnDRx4lAO2e00uMX4qDfrZw00U7WVjNrXSq
 +7rlNlV945ClvsnIovNfr3TKiXmTlNOVOSDoiI+ZkSsvvRNjgA09pwJFaY8VWNWtB/SxohY0
 cpkmKXlHG/FPoWU8AgcexBcFyc7Nqpc9fqeeT60sNeYyAvNdH6EL/dGVR5te9ZGvL8sRzgVr
 5T0KxhVBvyHr/63zay2TPJEjcU4J86tN4Qa0p1l5WCFVaZ7EcufG80m4/dKjRN3r8NpMM2dP
 fgkeDp9NhnCYzZ2bwJ/5JUWxbf02SaXnydjgF2PorUf4mXPwkp2yreFGMLcfdiNbcNJggCeq
 36u12b2GTkYKdqe0TeftHShmofnmCrrcJgcH+fjrKIsh0ecrkQXFQAVfV2/p/Sljke0QJRZL
 yQ86CozpK4970y2SMb0WTW4vXebsx9aUN1Ve8U46AiE0YLM7RySQG8eQVZ8hMcOvcsyQ3kh0
 UWE2oqxQzduq7aSD3ma8994sA9eJwA5K0s4Vw5YbTch4ubJ+9hrpwvQZ/taRfvdYsLOJRn8x
 DWDrS4bjroVjNIW26jTwbwhq2/xznQuZlNojjg7Tl5J/SsiP9f8ONLABUzzqKcectnIFzFtq
 VBew6CjAPYy4YZhfcBnaMwJGLyvjxpuGGKB2Qc0d3XNGsjExpJOVYlU5Dc7L0BzP4NdIXniY
 VTYvkVa45o70JqWgU1fPtLZ5ycClPeI+THZuhb8NYImjn9ZL1Xvwc2WTRTMt10BaWB1+U3FB
 b+VcNy3EVERArl9wTy9So81iOF1nXBhnD+IGMiikHxLNIZyglbIFt/p13PTPogEAF+s/G05D
 v4GbZLRkkUDOAEASniIrOb/0mzm3VBiVcyp9KS7h8aIIxFtHyk6GuTNzLY6E7GJbIwL/tokC
 kqVAxcCoHKm3CWvAVzTNhhLNui1Nb4h9i1TAMDZFQvys5TVSdzxvP53mlpeVeRPydGPOtYtF
 qRZJ5/ZXakRItkFkhxEBaTAQEVZXEzDrWqz0+CNOmBkF3K8b2QlIuPZQzY=
IronPort-HdrOrdr: A9a23:asHhxalegqH9VI2FwlLrq/z8WQbpDfOSimdD5ihNYBxZY6Wkfp
 +V8sjzhCWatN9OYh0dcIi7SdW9qXO1z+8Q3WBjB8bcYOCGghrkEGgG1+rfKlLbalXDH4JmpM
 Vdmu1FeaDN5DtB/IrHCWuDYq0dKbC8mcjC74q/vhRQpENRGttdBmxCe2Gm+zhNNXB77O0CZf
 yhD6R81l+dUEVSSv7+KmgOXuDFqdGOvonhewQ6Cxku7xTLpS+06ZbheiLokSs2Yndq+/MP4G
 LFmwv26uGIqPeg0CLR0GfV8tB/hMbh8N1eH8aB4/JlZAkEyzzYJbiJaYfy/wzdk9vfqmrCV+
 O85ivICv4Dq085uFvF5ScFlTOQlwrGoEWSt2NwyUGT0PARAghKTfaoQeliA0PkA41KhqAk7E
 sD5RPoi7NHSRzHhyjz/N7OSlVjkVe1u2MrlaoJg2VYSpZ2Us4YkWUzxjIiLH47JlOy1Kk3VO
 11SM3M7vdfdl2XK3jfo2l02dSpGnA+BA2PTEQOstGcl2E+pgEy82IIgMgE2nsQ/pM0TJdJo+
 zCL6RzjblLCssbd7h0CusNSda+TmbNXRXPOmSPJkmPLtBNB1vd75rspLkl7uCjf5IFiJM0hZ
 TaSVtd8XU/fkr/YPf+q6GjMiq9NFlVcQ6dv/22vaIJyYEUbICbQxG+dA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.93,337,1654560000"; 
 d="scan'208,217";a="940858340"
Received: from alln-core-10.cisco.com ([173.36.13.132])
 by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA;
 23 Sep 2022 00:02:52 +0000
Received: from mail.cisco.com (xfe-rtp-001.cisco.com [64.101.210.231])
 by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id 28N02p5a004251
 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK);
 Fri, 23 Sep 2022 00:02:51 GMT
Received: from xfe-rtp-003.cisco.com (64.101.210.233) by xfe-rtp-001.cisco.com
 (64.101.210.231) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.9; Thu, 22 Sep
 2022 20:02:50 -0400
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (64.101.32.56) by
 xfe-rtp-003.cisco.com (64.101.210.233) with Microsoft SMTP Server
 (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.9
 via Frontend Transport; Thu, 22 Sep 2022 20:02:50 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
 b=oIru9uXlQLbbw+pkDZOndd6bvYED7Z+OB+Zrai5Hc9tJLGKC1nSzZX/y/ZRkeDvmMcvfPkq2YBVD+YkO2lqjsug4nEYDnArw1+tbu4Rx5vtVFPTPqyClsrNwHD86sPDhNBzsoVGtH6ob04FqKXvmRsXqYGv32/uAZho08G2kz4/u1uewXgctAtQRnQ0uMGzRlYMHrlViNvo6l0YnQccOySXEI9jSQW+wP9eTRmbCMNiNqcYX7FC/rnbhYEYUGCvbCjm2pNzt3uWyHgb3jFL3l+6MWWEcUKg7vJWtnHcLKrQ144xdUy+hL4Gq6DrNZjgsjtW5au3JQzz6iBaaIWDFdg==
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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1;
 bh=TVuwbQozRW8PCGVTQR0BtBxs9bjVc4znChltpJvpv0E=;
 b=enwEWADNV44KBoaRhet0HwUinhum2q90WOg9unowaXCv914vP4OoiTdDpCZmGfl97AGCMIqyD+STkqRIPfXSgg6neN27q+XhrP+xvAzO1GuKPGcb66wu+DDoBvCqXYDkDX+pJLoIXylSI8mTxpOJjRZwwl9b1bTEW+jlLIHQXUWO1gkRPXFUKgQjOa0Exlm+3WJDn+el7NL6Fyp/z5Zga65IRNdvpFB09jkHKEW13S3iPlLeajm29vEgEcwl8SdAkBKNOYicu0pdEiyXHq297+LSKQfpd1n+nOEXhgQoYC7zxhq4Q9TT2oTjWqyzFFBkYukGH1D7Cx9UoiZq/FLF3Q==
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=TVuwbQozRW8PCGVTQR0BtBxs9bjVc4znChltpJvpv0E=;
 b=lKLGWLKo6dKcTpxm9DUGCJHFVtUJc/L3CbH6x0rdroR+nASt5Mh528yhcHabivSU2LJaGsPuZWA+DM527o9Ol0gAeZwNxFSRmN6zWfX0GnJdWOZxPjYotd/ARI5abYp4/EkjSzQCcMUh6D6HY69F3Tj9Fa1XeVMZoX1XmrcNs3E=
Received: from MW3PR11MB4651.namprd11.prod.outlook.com (2603:10b6:303:2c::21)
 by CY8PR11MB7172.namprd11.prod.outlook.com (2603:10b6:930:93::10)
 with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5654.16; Fri, 23 Sep
 2022 00:02:49 +0000
Received: from MW3PR11MB4651.namprd11.prod.outlook.com
 ([fe80::3ce:16a8:57d8:6fea]) by MW3PR11MB4651.namprd11.prod.outlook.com
 ([fe80::3ce:16a8:57d8:6fea%8]) with mapi id 15.20.5654.017; Fri, 23 Sep 2022
 00:02:49 +0000
From: "Tim Evens (tievens)" <tievens@cisco.com>
To: Jeffrey Haas <jhaas@pfrc.org>, Zhuangshunwan <zhuangshunwan@huawei.com>
CC: Luuk Hendriks <luuk@nlnetlabs.nl>, Maximilian Wilhelm <max@rfc2324.org>,
 John Scudder <jgs@juniper.net>, Paolo Lucente <paolo@ntt.net>,
 "grow@ietf.org" <grow@ietf.org>
Thread-Topic: [GROW] [Idr] RFC7854: EoR
Thread-Index: AQHYxubzuadynDm96kKEM7KBZVjVvq3cQMuAgAMDKACAACbKAIAAJTaAgAJMpgCABUylboACp1GAgAH8n4CAAGSk1g==
Date: Fri, 23 Sep 2022 00:02:49 +0000
Message-ID: <MW3PR11MB4651FED3E4009777B8F94FBDB6519@MW3PR11MB4651.namprd11.prod.outlook.com>
References: <bd7c5fb4-b398-c979-6f6b-0de82fd2ee12@bernat.ch>
 <dba40193-138e-5981-a4c2-6fc44fadde51@bernat.ch>
 <20220912203612.GA18968@pfrc.org>
 <6CB8C0EB-DC6E-48A8-993A-C98DEBD0D04A@juniper.net>
 <463DBA4E-3136-4A0F-A298-D081FEB123EB@pfrc.org>
 <20220914230819.GD27304@principal.rfc2324.org>
 <20220916101510.GA1365691@corley.shackle.nl>
 <MW3PR11MB4651FA81C4FC0E6C0F488DB4B64D9@MW3PR11MB4651.namprd11.prod.outlook.com>
 <058bcd84a50a4f3fa3fee62d0cf74da6@huawei.com>
 <0496725C-927F-4E62-9542-2C35874C8FDE@pfrc.org>
In-Reply-To: <0496725C-927F-4E62-9542-2C35874C8FDE@pfrc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dkim=none (message not signed)
 header.d=none;dmarc=none action=none header.from=cisco.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: MW3PR11MB4651:EE_|CY8PR11MB7172:EE_
x-ms-office365-filtering-correlation-id: 9eac2b94-6b87-4303-95d0-08da9cf6f3b7
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 1On+bQLuq8u7osj6kXbh+5MbpwbIJVyk87qCGkvZt/YkVdUY+h9sENBoTeMOdWjlprqRPgeLnisA2jEUz567kN0Ikc8K7in8t7gS5fytCS5QhyyybLDaGEF0Re0qnMdDE360pU1kHSl0dQ9q5MnfZVWKajmBaUqrH6HDPTxpQcKyEKOpF82YwSCnuXgQsUfPGLRaAzGaiZf/VRsgxzvBQltj3RxZvUGYOk0EWVpByfZUbGDK/6tDcqBoaxjCM6j+uuQwdd6wHqu6EtGgIAqox1IG26M5LfPEEpZLIwBAHGL7T5+eMiTiHzejOoEgnVW2O2MbfzzLJG3MCXi4zn5nqK3V0S9CgvXImafJzP4dmWJbtNoMDDh/S9t1/xMO+OADiNhj3anvJ9Rq2ZigBSF3unI1i91gEQgvT/8yNCCXO5K0+bglO4oqz38q5OVpyP184b6bGZwStienotPrQ68MkUKP1kQIVTKpz/u39DAep1zmznKIELxFSPDMQNaMono25IO0ButXd+VST+Hy9upYAQGA+oa6G/1geQphIgIWvPR/IpLnCBeLjo8HHpMHH/aKW+JiPYNLnJ8L4EgvwU33AActy0D9zCfWwAkVrHJoA5X8Dpc9z9VTR2EPipVQj6EZP6Iboa2v3BXyAI2XX3z3UnaiDUE1dWpU/QlpqyIPpXV5BWR6YHK6vXan11fugoiG6zdMJDfuFGpdcdwBd9NkgTs9u97E1Q0BPd1Q2EtlVRcs2VRotrBeYltLDbj8BEPh17LOE8NVOYf8N2JIwTCTmw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; 
 IPV:NLI; SFV:NSPM;
 H:MW3PR11MB4651.namprd11.prod.outlook.com; PTR:; CAT:NONE; 
 SFS:(13230022)(4636009)(136003)(396003)(376002)(346002)(39860400002)(366004)(451199015)(54906003)(316002)(110136005)(478600001)(91956017)(66556008)(76116006)(66946007)(53546011)(5660300002)(52536014)(41300700001)(8936002)(4326008)(9686003)(7696005)(66574015)(71200400001)(55016003)(2906002)(38100700002)(8676002)(6506007)(186003)(33656002)(64756008)(122000001)(66446008)(66476007)(83380400001)(38070700005)(86362001);
 DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?Windows-1252?Q?0rKofBm+/GJ5maha4h+nNLBYCsDa25XThCr6YMZUg0CsCsbfvWGIuTya?=
 =?Windows-1252?Q?dWp+BdwWhyIgT6fDd8qN5AzSuVf1m0QKh2tsgXhjll1VRKYFxXuatDJG?=
 =?Windows-1252?Q?ltZgzad7zcP3PzH+0XbPRl0+7CozBahLy6z5hkwkSOIOFirxfb3W0eyP?=
 =?Windows-1252?Q?bpP6ZZ7Hpx89HZX56n/Cjd+ddxvhNrdiFWXVaDIJbAdnhZ6E+r5wGmcj?=
 =?Windows-1252?Q?VfYle8pByLxMV6PecXuSA9+qm2zbOgSmFVUQNUgg51wBXuQ0IkZkEJpH?=
 =?Windows-1252?Q?qM8RgVP9wxsgyidm1mlAplsOIBJ6YcPaHnibDm0smhioedHIKp+ZcmDO?=
 =?Windows-1252?Q?N4z4jaSOZFCZf5Xgl1jA+l7TaxmWRi5bemztS95pwrA6AN7irH9y0KSq?=
 =?Windows-1252?Q?UyiCxKC/+cyQ14CIkkksIuy+80SIDlxf+FHhdoUo/kvYPx+znxIeXs/b?=
 =?Windows-1252?Q?KBUHfVLUGcUkvWY2K9jIZp5cLievI71Ll3YVFHHdjoHmQjoEAAfZAc/Q?=
 =?Windows-1252?Q?1xNePPkABg4ZXrY4SyyDXo4FoeeW3c+O2rjreaKyDFRdIhEf2rH9kcid?=
 =?Windows-1252?Q?KfvZCoUHnTpEMbyM+mnfros6026/SKvX8t/dfjajpmBfMlR80ojbPpRE?=
 =?Windows-1252?Q?GFrFDrlxtZMbmeufIRXzthYrDZKf1IVoJ4oMC5QzBI21JMFOz08+sC/A?=
 =?Windows-1252?Q?MhsgiSS5mtnfpmZCWHbGyV0QihNdESoHUvv+m+1e/CZ27bWe/+aUPpHI?=
 =?Windows-1252?Q?N2GctWkj9HYBOCKkdY2mNQigqiI40K1e3sufIOHyeRrnXgKPhc1eth+W?=
 =?Windows-1252?Q?K7dk46kmwqeLuYsPnGNl2nuWF6TwWOfxdzGi7woAmSPNxeKe5h4BENBY?=
 =?Windows-1252?Q?4eoF9/0f2zoq50u2RmiasCxt/8TK5mpiSU2oo7tOdpmzFQ3sWBlQsIKK?=
 =?Windows-1252?Q?Iaf/gKa2IS7CZchV1rCtroGrD1+AqZVKelVicWhefMCp3r2OHXMeHAf5?=
 =?Windows-1252?Q?bQa94mBdgORGxC+gjwHuBm9/g7wYBUIBjAzAh93/N6GI2PwjPUW07Z1d?=
 =?Windows-1252?Q?8JEkROMya8/G1dyOz30QZQDyEwIktkW3ODUZOf5rz509B/OzVR7mlb8v?=
 =?Windows-1252?Q?oOYyeuSxyUui/I476sceNeNWkhPc1lBfKd6Ky6uMsuB3PuJ4iSrGVWIS?=
 =?Windows-1252?Q?hn2Hkd9FXO4kwH5nUiCb7Yqz+u3cOOzBocGWsMEaZBv5ZFjArYXJKsUw?=
 =?Windows-1252?Q?t0jSqL3fOTSPW3K+z4JmFPWdjm4LebXC08yWpgAIG8IV1mTUrOyK6+H0?=
 =?Windows-1252?Q?HkgLhLdBfzxU7g7UynrlZECDStmSFZevZ2wdf0hSzRYwlWV8mksJGUhd?=
 =?Windows-1252?Q?wa1QCaHXNc7wRRfIaPEnhTFuox+tK1z/zAE6rgqfHSWSkVTzuy70EbCQ?=
 =?Windows-1252?Q?E+Jvu2k5Va/vV2+/jyCBC6GCP0HlGiifRc+w+PbmT9aNO4KMOy+8BWJE?=
 =?Windows-1252?Q?x8rUs70XxKtJWqWNOj8YNZ0WAYvQF2634ssGccZLuKOlR5glqb/T3T4n?=
 =?Windows-1252?Q?O7hxvKoYjYJQaFHxXkO5fXTwobTruo3w7stjKpoBGC3wCaZMv5KHhxAT?=
 =?Windows-1252?Q?4mM4BmpWalbPsLngZFq6IIGUHgbbLmINS5Y3J76T1tH17tNYPk7RV41C?=
 =?Windows-1252?Q?m442FHXvjKCto2IlegptZ38Za9DxPInxw8PRCQMwyfLbycqAeIoBH8Vv?=
 =?Windows-1252?Q?0C9dxQ2USdJaLHKiVfM=3D?=
Content-Type: multipart/alternative;
 boundary="_000_MW3PR11MB4651FED3E4009777B8F94FBDB6519MW3PR11MB4651namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MW3PR11MB4651.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9eac2b94-6b87-4303-95d0-08da9cf6f3b7
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Sep 2022 00:02:49.0973 (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: B+ak2A60D2HalsG7KhpuopznV74efdYSy0XaGSc9rP4cYW1PsRn6y41sVyKMag2pOLIWnnxBHTQCEIam5sVE5g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY8PR11MB7172
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 64.101.210.231, xfe-rtp-001.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/wo3qlghB4VvbAN5laJ_rvejoF9g>
Subject: Re: [GROW] [Idr] RFC7854: EoR
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>,
 <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>,
 <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Sep 2022 00:03:23 -0000

--_000_MW3PR11MB4651FED3E4009777B8F94FBDB6519MW3PR11MB4651namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

When I wrote route-refresh, that was from the router/sender side, not BMP r=
eceiver sending a route-refresh. BMP is still write-only.

There are use-cases for re-syncing the RIB to the BMP receiver.  Some of th=
e methods today are to clear the peer, request a route-refresh in, or to re=
set the BMP feed. This is a bit intrusive to the router (sender) and BMP re=
ceiver. Having to go to the router to request a refresh to the BMP server, =
IMO, is still okay.  The problem is that control knobs for refresh are at t=
he BGP peer level, not BMP.  For Adj-RIB-In Pre-Policy, it makes sense to d=
o that on the peer, but for Post-Policy, Adj-RIB-Out and Local-RIB, it does=
n=92t really make sense.  Having a knob to initiate BMP side refresh would =
be very nice and hopefully less intrusive.

Regardless of the BMP server needing a refresh, a BMP server does not know =
when someone has requested route-refresh IN at the peer level (maybe it was=
 requested for policy change, =85) Instead, the BMP receiver, blindly, rece=
ives a boat load of updates with no awareness that it was a new RIB dump or=
 controlled refresh. In this case, it would appear to be churn.  IMO, there=
 is value in having a message to signal the receiver that a refresh is comi=
ng, followed by an EoR.  A PEER_UP could be used for this, but that is intr=
usive and misuse of PEER_UP.

--Tim

On 9/22/22, 11:03 AM, "Jeffrey Haas" <jhaas@pfrc.org> wrote:



> On Sep 21, 2022, at 7:42 AM, Zhuangshunwan <zhuangshunwan=3D40huawei.com@=
dmarc.ietf.org> wrote:
>
> Hi Tim and All,
>
> I think the idea of a "BMP route refresh" would be appreciated,  it will =
helps keep the information synchronized between the BMP Server and the BMP =
Client.

Would someone clarify what they mean by a bmp route refresh?

The BMP protocol was intentionally designed as write-only.

-- Jeff

--_000_MW3PR11MB4651FED3E4009777B8F94FBDB6519MW3PR11MB4651namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style>
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72" style=3D"word-wrap:=
break-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">When I wrote route-refresh, that was from the router=
/sender side, not BMP receiver sending a route-refresh. BMP is still write-=
only.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There are use-cases for re-syncing the RIB to the BM=
P receiver.&nbsp; Some of the methods today are to clear the peer, request =
a route-refresh in, or to reset the BMP feed. This is a bit intrusive to th=
e router (sender) and BMP receiver. Having
 to go to the router to request a refresh to the BMP server, IMO, is still =
okay.&nbsp; The problem is that control knobs for refresh are at the BGP pe=
er level, not BMP.&nbsp; For Adj-RIB-In Pre-Policy, it makes sense to do th=
at on the peer, but for Post-Policy, Adj-RIB-Out
 and Local-RIB, it doesn=92t really make sense.&nbsp; Having a knob to init=
iate BMP side refresh would be very nice and hopefully less intrusive. &nbs=
p;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regardless of the BMP server needing a refresh, a BM=
P server does not know when someone has requested route-refresh IN at the p=
eer level (maybe it was requested for policy change, =85) Instead, the BMP =
receiver, blindly, receives a boat load
 of updates with no awareness that it was a new RIB dump or controlled refr=
esh. In this case, it would appear to be churn. &nbsp;IMO, there is value i=
n having a message to signal the receiver that a refresh is coming, followe=
d by an EoR. &nbsp;A PEER_UP could be used
 for this, but that is intrusive and misuse of PEER_UP. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">--Tim<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">On 9/22/22, 11:03 AM, &qu=
ot;Jeffrey Haas&quot; &lt;jhaas@pfrc.org&gt; wrote:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:0in;margin-right:0in;mar=
gin-bottom:12.0pt;margin-left:.5in">
<br>
<br>
&gt; On Sep 21, 2022, at 7:42 AM, Zhuangshunwan &lt;zhuangshunwan=3D40huawe=
i.com@dmarc.ietf.org&gt; wrote:<br>
&gt; <br>
&gt; Hi Tim and All,<br>
&gt;&nbsp; <br>
&gt; I think the idea of a &quot;BMP route refresh&quot; would be appreciat=
ed,&nbsp; it will helps keep the information synchronized between the BMP S=
erver and the BMP Client.<br>
<br>
Would someone clarify what they mean by a bmp route refresh?<br>
<br>
The BMP protocol was intentionally designed as write-only.&nbsp; <br>
<br>
-- Jeff<o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_MW3PR11MB4651FED3E4009777B8F94FBDB6519MW3PR11MB4651namp_--

