[GROW] Re: Question on draft-geng-grow-bmp-rel-enhancement

"Narasimha Prasad S N (snprasad)" <snprasad@cisco.com> Tue, 29 September 2026 08:56 UTC

Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 830594B for <grow@ietf.org>; Tue, 29 Sep 2026 08:56:28 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=cisco.com header.s=iport01 header.b=MLsYvds1; dmarc=pass (policy=reject) header.from=cisco.com; arc=pass ("microsoft.com:s=arcselector10001:i=1"); spf=pass (mx.ietf.org: domain of snprasad@cisco.com designates 173.37.142.92 as permitted sender) smtp.mailfrom=snprasad@cisco.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.com; i=@cisco.com; l=126402; q=dns/txt; s=iport01; t=1790672188; x=1791881788; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=u3FIvpqeIZ9PWNushjGtFOk+WNwpS6HoCe1oWaPJHuM=; b=MLsYvds1dYnOsKsZFe0rnxL1c8hovdFIBJQEqN1d49Auw7UhVj0wkwDo eqjK1d4SapnV5QH3MUk+4t5onU64pMU+qUTwp8nMQ6flE6P7/+V7dqdmJ 8zkcNeJMFjEZeEQkkVLWKB9LRq5CSkSUOoyjbzBsbga+qH1qMdtkvOwVY Qq+8MmIdZoFEwGhWI0I4NUePF4hMRQYt5ubElhXJ2th4X0D9wA5ebtDCJ 8c3/idpLbvMXJC2gBTngbcHmpGqH6DTkn/1J+ZBp36+fsIIJedTF+IPhj YY1gQ3PAXcJITTQCTKpZW8sjjkCUmKv0frcHHzkSiJaHyFoRDvAdnsshF Q==;
X-CSE-ConnectionGUID: TzIJx2DLQ+K4HnIH/Tp6SA==
X-CSE-MsgGUID: LIYXpaZKRkWeHziewpfbow==
X-IPAS-Result: A0B2BQADfLtq/48QJK1agS6CaDEqKYELgSNJhFeDTAOFK4h5A4J+iGaFZYxlgWoPAQEBDQI9FAQBAYUFAhaNcgImOBMBAgQDAgMBAQEBAQEBAQEBAQEKAQEFAQEBAgEHBYEOE4ZPDZASAQEBAQIBGgkKOhIFCwIBCBEDAQEBIQEGAwICAi8TAQkIAgQOBQgMghZZgh0dAxAnAwECDrVTAoodeoEygQGDbUHcCAaBTYVAgwMbAQErSWwDDoJMgSM0IIFHgnonG4INgRVCgWeBAj6CH0ICAgGBJwEBEgEJGh4WgyU6gjAEgQ5/FXoSG4EhHiMqMgSEDoMphCSGeFJyIgMmMywBVRMXCwcFgSNDAyovLSNLBS0dgSMhHRcRHlgbBgUSICpBQ12BWj8jGTZ6gQlegSspYAECDhdGQYIHAoJUgSNeAgFJQw4HRVMJJT4HEkcmIggSCQETGjALgSE4QQkoP209NxUZAwSBNQWPVEgZHoFpewI8JgQtFhAgPQkfE0YLNhMBBwGPVQmDSAo6gzOLYo5gk1lNcQqEHowij0SGLBeEBKYEZ5kII4I2izGECZFXB4UnAgQCBAUCEAEBBoF/JSs+cHAVO4JnUxkPjisDFoEUAQiHVscGeQIBOgIHAgcOAwuGRoskLYFPAQE
IronPort-PHdr: A9a23:LYJmAhSUchtOxICZWZZTuRoCFtpso47LVj580XJvo7tKdqLm+IztI wmGo/5sl1TOG47c7qEMh+nXtvX4UHcbqdaasX8EeYBRTRJNl8gMngIhDcLEQU32JfLndWo7S exJVURu+DewNk09JQ==
IronPort-Data: A9a23:5vvUHaJe50b5emYyFE+RlpQlxSXFcZb7ZxGr2PjKsXjdYENS1T0Fx 2tJC2CCbvuOamOgedolao20pB8D6pHdyd5jHgMd+CA2RRqmiyZq6fd1j6vUF3nPRiEWZBs/t 63yUvGZcoZpCCea+Uf1WlTYhSEU/bmSQbbhA/LzNCl0RAt1IA8skhsLd9QR2uaEuvDnRVnS0 T/Oi5eHYgH9imQlajt8B5+r8XuDgtyj4Fv0gXRmDRx7lAe2v2UYCpsZOZawIxPQKqFIHvS3T vr017qw+GXU5X8FUrtJRZ6iLyXm6paLVeS/oiI+t5qK23CulQRuukoPD8fwXG8M49m/c3+d/ /0W3XC4YV9B0qQhA43xWTEAe811FfUuFLMqvRFTvOTLp3AqfUcAzN1SHmAULdc03t80Ij1u8 904bwwVMCuq0rfeLLKTEoGAh+wqKM3teYdasXZ6wHSBU7AtQIvIROPB4towMDUY358VW62AI ZNHL2MzN3wsYDUXUrsTIIk4hP2hnXDzWzZZs1mS46Ew5gA/ySQhjeawb4eKK4DiqcN9umepl nrPzUfDAS4XFM6exCWd/Hirmbqa9c/8cMdIfFGizdZlmlqM7m0eFBNQUkG0ycRVkWa3X9ZZb khR8S00oO1qqgqgT8L2WFuzp3vsUgMgZue82tYSsWml4qHV+A2eQGMDS1Z8hBYO7afamRRCO oe1ou7U
IronPort-HdrOrdr: A9a23:1HL0cK9PVr1RRm4dRLFuk+HRdr1zdoMgy1knxilNoENuA6+lfp GV/MjziyWUtN9IYgBfpTnhAsW9qXO1z+8S3WBjB8bSYOCGghrlEGgM1/qZ/9SNIVybygcZ79 YeT0EcMqy+MbEZt7eG3ODQKb9Jq7f3ktHMuQ6d9QYQcegAUdAY0+4NMHfhLqQAfng/OXNWLu v62uN34xCbVTA8aMO9CnMZX+7FieHqufvdCyIuNloM0iXLqSmnxoLbPnGjsys2Yndi0L0i+W /Kn0jD4Lm/s/a08xnY12XCxZVbktnsx7J4dYKxY84uRQnEu0KNXsBMSreCtDc6rKWE81Axiu TBpB8mIoBa927RVnvdm2qs5yDQlBIVr1Pyw16RhnXu5ebjQighNsZHjYVFNjPE9ksbus1m2q 4j5RPbi3MXN2KDoM3O3amNa/hYrDvynZPkq59Us5Vra/paVFaWl/1HwKoaKuZZIMuw0vFWLA AnNrCu2B8RSyLaU1np+k9y3derQnM/Wj2CQkQEp4ip9gI+pgEj86Pdr/Zvw0vpM/kGOsN5zv WBPaJymL5USMgKKap7GecaWMOyTnfAWBTWLQupUB/a/Yw8SjvwQqTMkf0IzfDvfIZNwIo5mZ zHXl8dvWkue1j2AcnL2JFQ6BjCTGi0QDyok6hlltVEk6y5QKCuPTyISVgoncflq/IDAtfDU/ L2PJ5NGffsIWbnBI4M1QzjXJtZL2UYTaQuy5wGckPLptiOJpzht+TdfvqWLL3xESw8Ume6GX cHVCibHrQ30qlqYA6OvPH8YQKYRqWkx+MDLEHzxZln9LQw
X-Talos-CUID: 9a23:zQqYtW3efgmqTpQaa5T2v7xfJtIEUG2H4FPpYGzkKWBIaPqpUQGr0fYx
X-Talos-MUID: 9a23:uqp2HQ2V3/7JM94NvCmh42yOXzUjx4WfOFgEo7Y8uPaJFT5xNiiFgj6wXdpy
X-IronPort-Anti-Spam-Filtered: true
Received: from alln-l-core-06.cisco.com ([173.36.16.143]) by alln-iport-5.cisco.com with ESMTP/TLS/TLS_AES_256_GCM_SHA384; 29 Sep 2026 08:56:27 +0000
Received: from alln-opgw-1.cisco.com (alln-opgw-1.cisco.com [173.37.147.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by alln-l-core-06.cisco.com (Postfix) with ESMTPS id 4E09C18000104 for <grow@ietf.org>; Tue, 29 Sep 2026 08:56:27 +0000 (GMT)
X-CSE-ConnectionGUID: sFdFhs4XQPaSJMic0TBHsA==
X-CSE-MsgGUID: UdlSIAjPTd2Xvtua0w8uAQ==
X-IronPort-AV: E=Sophos;i="6.27,130,1787011200"; d="scan'208,217";a="87810461"
Received: from mail-eastusazon11012064.outbound.protection.outlook.com (HELO BL0PR03CU003.outbound.protection.outlook.com) ([52.101.53.64]) by alln-opgw-1.cisco.com with ESMTP/TLS/TLS_AES_256_GCM_SHA384; 29 Sep 2026 08:56:26 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=iO1TyBnu1gmGPCf5f+9V8rdLd0YQX/MMF1StmsXqsp8Dna4uaMi3BYH+wSJq777n2e8ehTld4zIKrnM6BPjNsbH+RU2bEuYhJ7f6KYfceezOiIUxzUAnpzAFpOta3S8MvZCFAxbBuGxbatQAchoMj765v8+DRidoCk7biWyyG9U6XGBVolVghmakz5GY3trIo9nbdvkbUoo48J+o/SZBSiq52Io28aX6vBM7uwRj6Vj2tmYAACy6drjbKYk7d53vSs4dMaG2Y+sbxPaLe9T2IyT9U6FZQIyfIKG3L6lKEoZ9h01iOQVMMFB/gryHUJZix14GKNrbQ70zw5dUEzWSOQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; 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=u3FIvpqeIZ9PWNushjGtFOk+WNwpS6HoCe1oWaPJHuM=; b=goOeiycWquRnyfpu4bFODbEr5DLEvZYCtd0MJKvYuLXNhnR0N3tdDMB0jy+ic4zPwI8FQP2giZsDO1cKIHrIdKRea/z3/1mnT2lrisTcRZctBlWA2RYh4M0oNtB4FzDZo3GuBapNAgloIh0UJtKgRVQEdBzhM1dp2WtQX42ct/R38BSV45+fb2M3UiBBjtNuG9p0ykOaQKp7rRr9/D7C0SPdRaTVOxm9bmhrJwJk8eOU2GOEHWQqEthXCxIfAticaUkZX9lyL4MZFW+W0uvpDbts7Fuyw16fcQXzw0uu1jsM08DJmfl++sNXq7crJH25DP0JWojUgvfwBWAm8UBZ/Q==
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
Received: from SA1PR11MB9525.namprd11.prod.outlook.com (2603:10b6:806:4c5::16) by DSVPR11MB9958.namprd11.prod.outlook.com (2603:10b6:8:3bc::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.21.451.26; Tue, 29 Sep 2026 08:56:23 +0000
Received: from SA1PR11MB9525.namprd11.prod.outlook.com ([fe80::5ff1:767d:b719:a60d]) by SA1PR11MB9525.namprd11.prod.outlook.com ([fe80::5ff1:767d:b719:a60d%7]) with mapi id 15.21.0451.022; Tue, 29 Sep 2026 08:56:23 +0000
From: "Narasimha Prasad S N (snprasad)" <snprasad@cisco.com>
To: gengnan <gengnan@huawei.com>, "Dikshit, Saumya" <saumya.dikshit@hpe.com>
Thread-Topic: [GROW] Re: Question on draft-geng-grow-bmp-rel-enhancement
Thread-Index: AQHdGotAzslS1wz/j0+SWlnWs8V53rZ9ykcAgACSlQCAAT/dAIAEqDIAgACqWoCAAIgugIBgMrTg
Date: Tue, 29 Sep 2026 08:56:23 +0000
Message-ID: <SA1PR11MB9525716DAC2FB2E28D2C0113C88C2@SA1PR11MB9525.namprd11.prod.outlook.com>
References: <648916035.904507.1784742155064.ref@mail.yahoo.com> <648916035.904507.1784742155064@mail.yahoo.com> <4d9876ebfd6a42ed913a05e1cc76db6f@huawei.com> <SJ0PR84MB2110F1FBB9AC38D9FAF0D7A294CE2@SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM> <CH3PR84MB3569FEC18151E4A6102D936282CE2@CH3PR84MB3569.NAMPRD84.PROD.OUTLOOK.COM> <SJ0PR84MB2110E4FDD1CE79B357B5166C94CD2@SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM> <4bb2d3bd3a8e48a996e5ad00891ce2f7@huawei.com> <SJ0PR84MB211049BA71AC6FDC286FE2C194CA2@SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM> <ca4b2766a8114748a32f1033896b711e@huawei.com>
In-Reply-To: <ca4b2766a8114748a32f1033896b711e@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: SA1PR11MB9525:EE_|DSVPR11MB9958:EE_
x-ms-office365-filtering-correlation-id: 6fa7f866-aafa-40e4-3f8f-08df1e0789a1
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|366016|376014|1800799024|23010399003|10067099003|56012099006|11063799006|5023799004|4143699003|3023799007|6133799003|8096899003|18002099003|22082099003|13003099007|38070700021;
x-microsoft-antispam-message-info: z89BWaSnlu3X0dcjaUkrW+CnmNYpGXNzshgj712wwA88ZCiHglUmfj0dZC3niWnOeS1x1ZlGcOdv69srQC/48b3F7IxOmFtMAn3Bl8QQZARuhRDJI2TfasKnWNLDWUtEFbtt70yLikYiYikaVyaaykplGzs6jaQdK2rIhYfdmJNaqV5uFwB8Lup941UKmT8dXWgI06Kz4yOci3cYV9QpFP/Vv+EuHS2oZx1KzsFGiAw9dxe790zhHYctBo7HQn3XAZh4IGGFm7OpzsrjyOOS2eoVTR18/xLwMFBwNVpM+WnJv6PtiU13xfdwkPlW3r1wChfZvzP7vxcJq7x1q3s8zuvjud8AMfH6b9LiK+96pBuPbCO3qtR4E0j83x4zPtMf1tjEY7jbmMtTGzPIhm8wlZOA5HV84o1doHtEMIeENPQziQfkxFgLvjV9ONptXRvWZ6jwpD7OurVp/m62K23SJxYHoWzUAgR7qZ99XAMO3aZtNE6znW/xs+JK7wSsem9nMQ6MGghEJPMu9nRD+Dr/axkjSZYTlsV/SIFUnCNgq+mTrPZDwCuMLtk4UQXpWDcpXx3TmNPVQ8kDmYE05iaZMiUJPsncUvG9KkkMCRzcUfc0WHGW/Ys8DOLpQkwbvTEKT0Hu3u5fJTRJ8oegpDynEtzf8CsQm93zx4kRUHNyDVk4uzjitJ+U7uXVPGuL7/WJV+BK+WpkzJzz+mJUE2YcqQFwkEmDKw9ZtnF/0N1wnPg=
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:SA1PR11MB9525.namprd11.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(366016)(376014)(1800799024)(23010399003)(10067099003)(56012099006)(11063799006)(5023799004)(4143699003)(3023799007)(6133799003)(8096899003)(18002099003)(22082099003)(13003099007)(38070700021);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: d3RqkjIrcDTZtfXml//iunJ60tQgwIT24CgaMEpeoR9UH+PKHP+tpesbAaG7sSL/0DhkAE1MrA2CZRp2i0lBF1X7Y0S4ySVIGxNo7feK5DDyBasaPR0y4+XcqmMMyZ2Z6rklYsaBUB1zTXP6egfZNfPxo8rkgJXfKdzboi+hW2/AvkIeBZp6mI7hclUxhLmhyQ7Whv85vC6o8YdL8U7FZrWsR40KnlVVtSo60ZNifeOvqmK7+TjEflg+f1+sWOYH3QmycGxUWO9hQTIrpNpzXDdCig1FddcOIFyMjgqgTh5xBpwF/+brc8Sl4Mteek6e8Ho0BXq8WaH+p6CHnH70qph3xK+RhGnnC9y6u/NOozHiEhgAPq9qjH1nEnbdmMf4B/oFbiJB4hFhWQrOwEywwu0VFxRufaCw5UmwfJSVsnOKvIo+r1X0K1Ef63J5aMglZDt0NKeMdUkADQu027Lu0WqNhig7IQgOb3Dxgxvg/+krCotg29/XZGyAxiaWzc+nf9YCM+2FHsvsvZsScNjJrMCrMvFE81X58wTPJYCTeVWPXvhGkkzBEHQZAbAtZQWrzb7vs8LdK9iN6otSYXHfjHGdv0XH+Ap4lDJ/rs87xmILQf+KbA4MTB88ttd6swfiqbUhux54oSxUVUeWS6tN8qUxlUF8ECj+yE8FCuBNRmwcRQNwqhVpeE/1JXkX82GACn6SfbZc2uqnbCiuSroQvm/gRGbS7hYgVULDzaB7UsvhGF+YXjTW5QtBfHyCVKZDTmRx7R0bahpGvi+V96N5l9rsXe+CGvevjttQgks0Ivq0uQzXyk6QGKrx9pzyQb1BgaI9AAERsFK0PeR2IlzB3Dr4hnPrOT7tQkszxbz78ZtOIAeADCdrBbiRgIwXZ3Wea48x2RDSPfdM6wemHaJ0+xOI1xmdE/AJRtsEDiDiUr4r5yE0GnM0ALU4R32Qd2Lm1Y/gS8/0zSx0qnk9OJHC1VQyCbxpNgsXIqfwbz5q6PmjwThQipkTT/ZsmAstakdAM9v6AGxlzkAbMuNOJGuw3Hfp38Wf9HCt3voGCoOZQa4tuRD7cJx0fuKs9EZLVqY3pc0QzwSSJQhaSoEWXx/YdwU92zAf4DvDUqiwyOMZ7j9iKhgCIGQ1E7lINpCyleRXG+OjNOzUWdF7l/B7Zc0Nj75QKDB3byfCah2hX9CTfhzHjZIRQYDD5o5SZ5pyWSfZ+kMtIn8tYeKUfVNuC4R4ZWt49siUZqovqSOACtc1Ymrc3otJZ5lfTeGO5vGHAvWecjDmWCNC2XQ+tfBu7GifFiraxS7qwHri1OwfP5Kk/veSekeReNmpPgR6qqoUxPRnf5aBvVOBFL9NDZ3EoEYr2VJRrQTn1FXupa6Y68lVoCRdYiYkK5VKnuclXWMVAFr+DVfS1hVY+2K3dwj7z5cbRB+SD7q7FPG0TVyCGxapciNa7ZnH+RC66xo5DSmKMx2TMAoItrDvb+Wqmff2UEgqG98rzgBbUcyD2wVLLr6PjP1yCB1C+rg79k6pXt8aCzEor30ODJnzWbg2TIm0/fOB3Zo6oeC2R6PipD672vIM+qwaUpRLiAswV5fG9+4o8xS2ZcVLXJcoUPm0FlbpWHerGpZ9RB0bQbDViDiew3JjFira1vySxRG4/6dfrp07ezQDXAAXfDutX5aiHKy6e1xd63KFXHtsxI2tq5juh2kI0F469ZC+OxyU5T5KL26aA03i
Content-Type: multipart/alternative; boundary="_000_SA1PR11MB9525716DAC2FB2E28D2C0113C88C2SA1PR11MB9525namp_"
MIME-Version: 1.0
X-Exchange-RoutingPolicyChecked: VMOcz1hb6aDEqUWyHJaZrTKRufyeDsZRNjTYg135LMEhXdeQfDW/CaZoGTSm+Hb21gBknJb84Vz+HfoMt0cdajKlOKx3saZsLY0LjvfpHiAu6AWi6dGHsVlOEz3ltuqeg3jcK6kXe9wRp7E/eB9U3Y/4DMlM/BKQHjKUtbENgy6mOfWeMEKbVcZNxalyN1+bChflRWfuvhNCEuEg4N7+iv/E04MG+r4uRrg4TeL24wLoHbyTXH+YlLyJg3w36K25xtWvlxbzRe27cjWvf4lfcbckMQdJ392MMcpZw6tN0SLweF93B0yxwuxEpkXh8FDlUc8uCqUjCdB4AIomBdqSzw==
X-OriginatorOrg: cisco.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SA1PR11MB9525.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6fa7f866-aafa-40e4-3f8f-08df1e0789a1
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Sep 2026 08:56:23.2211 (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: IvaEgJ6hfZpF3Dth1Jk6MSzK/urlfzntxqW7+616En3OIMGhpWA7955/RQRFxrsAIGy4+ISNFeNVtH2xsWPGcw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DSVPR11MB9958
X-Outbound-Client-TLS: ANONYMOUS;alln-opgw-1.cisco.com [173.37.147.229];TLSv1.3;TLS_AES_256_GCM_SHA384;256
X-Outbound-SMTP-Client: 173.37.147.229, alln-opgw-1.cisco.com
X-Outbound-Node: alln-l-core-06.cisco.com
X-Spamd-Bar: ------
Message-ID-Hash: LFWSGT5HCMMVSLW5J2MY3276SKL6WCGS
X-Message-ID-Hash: LFWSGT5HCMMVSLW5J2MY3276SKL6WCGS
X-MailFrom: snprasad@cisco.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-grow.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Grow <grow@ietf.org>, Zhuangshunwan <zhuangshunwan=40huawei.com@dmarc.ietf.org>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [GROW] Re: Question on draft-geng-grow-bmp-rel-enhancement
List-Id: Grow Working Group Mailing List <grow.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/lOT5g0oMPqVprxPHPKi68tiHFyQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Owner: <mailto:grow-owner@ietf.org>
List-Post: <mailto:grow@ietf.org>
List-Subscribe: <mailto:grow-join@ietf.org>
List-Unsubscribe: <mailto:grow-leave@ietf.org>

  *   The current rel-enhancement draft follows with the framework of bmp-rel. Since the WG is discussing a unified event reporting framework, personally I think an event filter or suppressed marker is better addressed there.

Thank you, Nan, for the cc-ing us. Sorry for the late ack, I have gone thru the discussions on the list. We will capture this as a requirement for the event framework as we plan to merge aspects of https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-rel/ and https://datatracker.ietf.org/doc/draft-sp-grow-bmp-gen/ per the WG discussion at IETF126 before, during and after my GROW preso.

Best Regards,
/snnp
(Prasad)


From: gengnan <gengnan@huawei.com>
Sent: 30 July 2026 09:18
To: Dikshit, Saumya <saumya.dikshit@hpe.com>
Cc: Grow <grow@ietf.org>; paolo@ntt.net; Narasimha Prasad S N (snprasad) <snprasad@cisco.com>; Zhuangshunwan <zhuangshunwan=40huawei.com@dmarc.ietf.org>
Subject: RE: [GROW] Re: Question on draft-geng-grow-bmp-rel-enhancement

Hi Saumya,

> Hi Nan  rel-enhancement is already allocating Log Action code points
> (TBD5-TBD7), so would it make sense to add one there:

>   *  TBD8 = Events-Suppressed.  This event indicates that the
>     reporting device is locally filtering or rate-limiting routing
>     event reporting, and that the event stream is therefore
>     incomplete.  Optional data contains a 4 bytes value representing
>     the observed timeframe in seconds, followed by a 4 bytes value
>     indicating the number of events suppressed within that
>     timeframe.

Thanks for the proposal.

The current rel-enhancement draft follows with the framework of bmp-rel. Since the WG is discussing a unified event reporting framework, personally I think an event filter or suppressed marker is better addressed there.

If such a marker is needed, it should take all types of BMP events into consideration, not only REL-enhancement or "Routing and Validation Event".

Best,
Nan


From: Dikshit, Saumya <saumya.dikshit@hpe.com<mailto:saumya.dikshit@hpe.com>>
Sent: Thursday, July 30, 2026 3:41 AM
To: Zhuangshunwan <zhuangshunwan=40huawei.com@dmarc.ietf.org<mailto:zhuangshunwan=40huawei.com@dmarc.ietf.org>>; Srivastava, Mukul <mukul.srivastava@hpe.com<mailto:mukul.srivastava@hpe.com>>; gengnan <gengnan@huawei.com<mailto:gengnan@huawei.com>>; Reshad Rahman <reshad@yahoo.com<mailto:reshad@yahoo.com>>
Cc: Grow <grow@ietf.org<mailto:grow@ietf.org>>
Subject: Re: [GROW] Re: Question on draft-geng-grow-bmp-rel-enhancement

Hi Shunwan,

Answering both your notes together, and correcting one thing I said on 26 July.


F cannot be reused for REL events
---------------------------------

I suggested rel-enhancement could say events reuse the Peer F Flag.
draft-ietf-grow-bmp-rel-06 Section 3.3 rules that out - it redefines
the flags field for REL rather than inheriting the RFC 7854 one:

                       0 1 2 3 4 5 6 7
                      +-+-+-+-+-+-+-+-+
                      |V|A| Reserved  |
                      +-+-+-+-+-+-+-+-+

   "The remaining bits are reserved for future use.  They MUST be
    transmitted as 0 and their values MUST be ignored on receipt."

So an F bit set there is non-conformant on send and discarded on
receipt. Section 3 also makes the Per-Peer Header "mandatory or
optional depending on the Event Type", so for Health events there may
be no peer header to carry a flag at all.

Your original instinct for a separate indication on the event side was
right,


Text Update
----------------------------------------

Having said that, I do not think events need anything invented either.
bmp-rel Section 3.2.2 already describes almost exactly this situation -
BMP preempted under load, implementations discarding internal state
defensively - and concludes:



Hi Nan  rel-enhancement is already allocating Log Action code points
(TBD5-TBD7), so would it make sense to add one there:

   *  TBD8 = Events-Suppressed.  This event indicates that the
      reporting device is locally filtering or rate-limiting routing
      event reporting, and that the event stream is therefore
      incomplete.  Optional data contains a 4 bytes value representing
      the observed timeframe in seconds, followed by a 4 bytes value
      indicating the number of events suppressed within that
      timeframe.

The data format deliberately mirrors the existing "Route unstable" (2)
code point, which already carries a timeframe and an occurrence count.

That needs no change to bmp-rel, no new TLV type and no peer flag

Reshad - would the Log Action code point above close your original
question?

Thanks,
Saumya

From: Zhuangshunwan <zhuangshunwan=40huawei.com@dmarc.ietf.org<mailto:zhuangshunwan=40huawei.com@dmarc.ietf.org>>
Date: Wednesday, 29 July 2026 at 3:01 PM
To: Dikshit, Saumya <saumya.dikshit@hpe.com<mailto:saumya.dikshit@hpe.com>>; Srivastava, Mukul <mukul.srivastava@hpe.com<mailto:mukul.srivastava@hpe.com>>; gengnan <gengnan@huawei.com<mailto:gengnan@huawei.com>>; Reshad Rahman <reshad@yahoo.com<mailto:reshad@yahoo.com>>
Cc: Grow <grow@ietf.org<mailto:grow@ietf.org>>
Subject: RE: [GROW] Re: Question on draft-geng-grow-bmp-rel-enhancement

Hi Saumya,

I have a question regarding the following point you raised:
Section 4 says "In Stats messages, counts MUST reflect the filtered RIB numbers and not the original RIB ones," but it stops short of stating that the F flag itself be set consistently in the Stats message's Peer Header for that same session.

To make sure I'm following correctly, let me walk through a quick scenario:
Suppose Peer 1 (a BMP client) receives two types of routes from its neighbor, tagged with Community 1 and Community 2 respectively. There are N1 routes with Community 1 and N2 routes with Community 2.

Now, suppose Peer 1 applies an outbound filtering policy, sending only the N1 routes (tagged with Community 1) to the BMP server via Route Monitoring (RM) Adj-RIB-In messages. Naturally, these BMP RM messages will have the F Flag set.

According to Section 4, for Stats messages, "counts MUST reflect the filtered RIB numbers and not the original RIB ones." This means Peer 1 should report a count of N1 to the BMP server via Stat Type 7 (Number of routes in Adj-RIBs-In).

My question is: Does this mean the BMP server no longer needs to know the total/original count (N1 + N2) present in Peer 1's actual Adj-RIB-In?
Or is there a scenario where the server still needs visibility into the unfiltered baseline? I’d love to hear your thoughts on this.

Best regards,
Shunwan


From: Dikshit, Saumya <saumya.dikshit=40hpe.com@dmarc.ietf.org<mailto:saumya.dikshit=40hpe.com@dmarc.ietf.org>>
Sent: Sunday, July 26, 2026 6:24 PM
To: Srivastava, Mukul <mukul.srivastava=40hpe.com@dmarc.ietf.org<mailto:mukul.srivastava=40hpe.com@dmarc.ietf.org>>; gengnan <gengnan@huawei.com<mailto:gengnan@huawei.com>>; Reshad Rahman <reshad@yahoo.com<mailto:reshad@yahoo.com>>
Cc: Grow <grow@ietf.org<mailto:grow@ietf.org>>
Subject: [GROW] Re: Question on draft-geng-grow-bmp-rel-enhancement


Hi Mukul,

That's a helpful clarification, thank you.

It's good to be reminded that F flag lives in the shared Peer Header rather than being RM-specific, so it's structurally available to Stats messages too.



Looking at the current adj-ribs-filtered-00 text again with that in mind, I think it actually pins down exactly the gap:

• Section 4 says "In Stats messages, counts MUST reflect the filtered RIB numbers and not the original RIB ones," but it stops short of stating that the F flag itself be set consistently in the Stats message's Peer Header for that same session.
• So as written, an implementation could arguably satisfy the letter of the text by adjusting the counts while leaving F unset (or inconsistent) on the Stats side
o  This is exactly the inconsistency you flagged as unhelpful for correlation.



Would it make sense to tighten this into an explicit MUST, something like:

• "The Peer F Flag MUST be set consistently across all BMP message types that share this Peer Header for the lifetime of the session (Route Monitoring, Stats Report, Route Mirroring).
• An implementation MUST NOT report F=1 in one message type while reporting F=0 (or omitting the equivalent filtered-count adjustment) in another, for the same peer."

Since you're already a co-author on adj-ribs-filtered, that operational-consideration addition (Section 5, or as a normative bullet in Section 4) seems like the cleanest, lowest-overhead fix and no new TLV needed for the RIB/Stats side at all.



That said, it doesn't fully close Reshad/Nan's original question: adj-ribs-filtered-00 only talks about Adj-RIB-In/Out and Stats messages and says nothing about routing-event messages (draft-geng-grow-bmp-rel-enhancement's actual subject). On that note, would it make sense for rel-enhancement to explicitly say event messages reuse this same Peer F Flag bit (with the same cross-message consistency rule above), rather than defining a separate mechanism?
• That would give collectors one consistent signal to check across RM, Stats, and event messages, with a single small text addition on each side rather than a new generic flag.



Your thoughts Nan, Reshad, Mukul on this ?

Happy to help draft the exact text for either document if useful.



Thanks,
Saumya

From: Srivastava, Mukul <mukul.srivastava=40hpe.com@dmarc.ietf.org<mailto:mukul.srivastava=40hpe.com@dmarc.ietf.org>>
Date: Saturday, 25 July 2026 at 8:50 PM
To: Dikshit, Saumya <saumya.dikshit@hpe.com<mailto:saumya.dikshit@hpe.com>>; gengnan <gengnan@huawei.com<mailto:gengnan@huawei.com>>; Reshad Rahman <reshad@yahoo.com<mailto:reshad@yahoo.com>>
Cc: Grow <grow@ietf.org<mailto:grow@ietf.org>>
Subject: Re: [GROW] Re: Question on draft-geng-grow-bmp-rel-enhancement

Hello Saumya

>>>>>> If a router locally rate-limits or drops events (per the mitigation text in draft-geng-grow-bmp-rel-enhancement) and separately reports gauges such as the ones in

  *   draft-ietf-grow-bmp-bgp-rib-stats (RFC 9972) or
  *   the policy-driven counters in draft-smc-grow-bmp-route-change-stats,
a collector has no way to know that an observed gauge delta might not be fully explained by the event stream it received it may look like an unexplained jump.

—

[MS] - The BMP stats messages have BMP peer header. The filter flag is part of the BMP peer header.  If the  filter flag is not set in stats message, while the other msg had filter flag set, then the collector should use caution and know that the data it received was filtered while the stats count is not filtered.

I would assume for ideal operation, the router should have flag set/unset for all events/data/stats message for a session. Inconsistency in this flag state between different messages, will not help in meaningful correlation at collector.

I think we should add this in the operational consideration for filtered drafts, if it isn’t present already.

Thanks
Mukul

From: Dikshit, Saumya <saumya.dikshit=40hpe.com@dmarc.ietf.org<mailto:saumya.dikshit=40hpe.com@dmarc.ietf.org>>
Date: Saturday, July 25, 2026 at 2:37 AM
To: gengnan <gengnan=40huawei.com@dmarc.ietf.org<mailto:gengnan=40huawei.com@dmarc.ietf.org>>; Reshad Rahman <reshad@yahoo.com<mailto:reshad@yahoo.com>>
Cc: Grow <grow@ietf.org<mailto:grow@ietf.org>>
Subject: [GROW] Re: Question on draft-geng-grow-bmp-rel-enhancement
Hi Nan, Reshad,

I was going through the draft and couldn’t help bringing up another angle, (though not-unrelated) to the email chain discussion :

The same blind spot effects statistics consumers, not just event-log consumers. If a router locally rate-limits or drops events (per the mitigation text in draft-geng-grow-bmp-rel-enhancement) and separately reports gauges such as the ones in

  *   draft-ietf-grow-bmp-bgp-rib-stats (RFC 9972) or
  *   the policy-driven counters in draft-smc-grow-bmp-route-change-stats,
a collector has no way to know that an observed gauge delta might not be fully explained by the event stream it received it may look like an unexplained jump.

Rather than defining filtering-indication independently for events (in this draft) and for RIB streams (bmp-adj-ribs-filtered), would it make sense to define one small, generic TLV/flag,  that any BMP consumer event, RM, or SR message can check?  This would definitely help in achieving "telemetry completeness"

More than happy and willing to sketch this as a short  contribution if there's appetite, as we hit a related need while defining the per-peer gauges in draft-smc-grow-bmp-route-change-stats.

Thanks,
Saumya.

From: gengnan <gengnan=40huawei.com@dmarc.ietf.org<mailto:gengnan=40huawei.com@dmarc.ietf.org>>
Date: Thursday, 23 July 2026 at 3:39 PM
To: Reshad Rahman <reshad@yahoo.com<mailto:reshad@yahoo.com>>
Cc: Grow <grow@ietf.org<mailto:grow@ietf.org>>
Subject: [GROW] Re: Question on draft-geng-grow-bmp-rel-enhancement
Hi Reshad,

As stated in Section 3 of draft-ietf-grow-bmp-adj-ribs-filtered:
> ... be informative to the rest of the system that they should not make decisions assuming that this stream is transmitting all the information about it.

The same logic seems to apply to event reporting. If critical events are filtered locally without any signal to the collector, monitoring systems may draw incorrect conclusions based on incomplete data. It would therefore be valuable to consider a mechanism to convey this filtering state for events.

Best,
Nan

From: Reshad Rahman <reshad=40yahoo.com@dmarc.ietf.org<mailto:reshad=40yahoo.com@dmarc.ietf.org>>
Sent: Thursday, July 23, 2026 1:43 AM
To: Grow <grow@ietf.org<mailto:grow@ietf.org>>
Subject: [GROW] Question on draft-geng-grow-bmp-rel-enhancement

Hi,


   Appropriate caution SHOULD be taken when picking routing events to

   report, as next-hop related updates may produce heavy message loads

   during network instability.  Mitigation measures SHOULD be deployed

   on both reporting and receiving sides.  For example, local endpoints

   can apply event filtering controls, while receivers maintain

   corresponding processing mechanisms to handle potential high-volume

   event bursts gracefully.



During the meeting today the text above was highlighted by Nan (based on feedback from Prasad). I have no issue with the feedback and text, but is there any indication of filtering sent to the collector? draft-ietf-grow-bmp-adj-ribs-filtered which was presented earlier adds a Peer F flag for Adj-Rib-In/Out, IIUC that doesn't cover events in draft-geng-grow-bmp-rel-enhancement? IMO we want indication of filtering for "critical" events.



Regards,

Reshad.