[GROW] Re: Comments on draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib-01 : applicability to EVPN/IRB and inter-VRF leaking
"Dikshit, Saumya" <saumya.dikshit@hpe.com> Sat, 01 August 2026 10:27 UTC
Return-Path: <saumya.dikshit@hpe.com>
X-Original-To: grow@mail2.ietf.org
Delivered-To: grow@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 4875812209E99; Sat, 1 Aug 2026 03:27:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785580076; bh=URj4Q+ss1TpaKsVl2EfB/s5ywXc+9aWpk+suj/lbCuo=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=qSeaTtrtr4fGTFd5jH8p20oNnEooV1+08pl8wE3cygKgbvgSh2jSOw0Stswwrb5PT WwE3hKQLi7wR9sn5/TFBD/U26ZdjLSaFQHNfDHRYgFzXuXjr6zkA2tnUT2UYUK2APG XgjOFbgvzAyNfoTLxiEcxpX0SJ4vmfyS2KGF7+0Y=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.794
X-Spam-Level:
X-Spam-Status: No, score=-2.794 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=hpe.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fPmAcqGgdD7a; Sat, 1 Aug 2026 03:27:55 -0700 (PDT)
Received: from mx0a-002e3701.pphosted.com (mx0a-002e3701.pphosted.com [148.163.147.86]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 3690612209E8E; Sat, 1 Aug 2026 03:27:55 -0700 (PDT)
Received: from pps.filterd (m0150242.ppops.net [127.0.0.1]) by mx0a-002e3701.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 6719puNS536490; Sat, 1 Aug 2026 10:27:32 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hpe.com; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to; s=pps0720; bh=URj4Q+ss1TpaKsVl2EfB/s5ywX c+9aWpk+suj/lbCuo=; b=QIRq9zP28u81wcJDETnAAlvOstIepEYGvmhNbrWBYy x963JrlHHrcyGUjvc4DX6NCMyqW+d+Q8RHW1ke30vNF6fD16NxjNF47/Hy/i8lK7 72i/VMvG7ikzk/pYnVlqZbOg09VoadfBF3NOrryc7v3ICKTJLFAY2b1nwnBTrS0L qxQRRtc6JIGCcw4Z5kxMGKMeJiMQZLc2NUu0Kkja6dcWXwKF1n62KzFJziCIAAi2 TxW7wCwvQPNj0bqg4mDOwRZgG0O2nEhigBtS7QJ5OWdZ0kqO92Dgnb7bkv9dcc8Z uIu7fp0oQ/ruIwO8rYDyaGZKJAxoOXvk6SMBBFA51EQw==
Received: from p1lg14879.it.hpe.com (p1lg14879.it.hpe.com [16.230.97.200]) by mx0a-002e3701.pphosted.com (PPS) with ESMTPS id 4fs7f7bx2f-1 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Sat, 01 Aug 2026 10:27:32 +0000 (GMT)
Received: from p1wg14926.americas.hpqcorp.net (unknown [10.119.18.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by p1lg14879.it.hpe.com (Postfix) with ESMTPS id 05D9D12EAD; Sat, 1 Aug 2026 10:27:30 +0000 (UTC)
Received: from p1wg14927.americas.hpqcorp.net (10.119.18.117) by p1wg14926.americas.hpqcorp.net (10.119.18.115) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43; Fri, 31 Jul 2026 22:27:30 -1200
Received: from p1wg14924.americas.hpqcorp.net (10.119.18.113) by p1wg14927.americas.hpqcorp.net (10.119.18.117) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43; Fri, 31 Jul 2026 22:27:30 -1200
Received: from p1wg14921.americas.hpqcorp.net (16.230.19.124) by p1wg14924.americas.hpqcorp.net (10.119.18.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43 via Frontend Transport; Fri, 31 Jul 2026 22:27:30 -1200
Received: from DS2PR08CU001.outbound.protection.outlook.com (192.58.206.38) by edge.it.hpe.com (16.230.19.124) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43; Fri, 31 Jul 2026 22:27:29 -1200
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=oD+Iyb+QDanHHsUxtWRcw57Lik9SsCzPSZmQGCCAwUdZhEp4+y1KN47dpGnM25/f/aL3K1o6X2XPGPyq5cIhViaRAA63QJU/I5ysEdoR2TNdmyaNOE3eeumOvBlR1AHt+6UjLuxAf7URklu5RxEhbi+LIIoWFxNEWwcmfMINniz9bINnONnzaVPo1AczKpxju1+/MEBbIi571CO3fO+sV7+/VRzgm1YOKqKsspYMalanOTiyuq827myE9by0kM8KGcGq4KaTJquhmb80WM/y6plZlSFw7hdyOkhwPYTx9HqRtN8IJEzyMHGYDYVsT5qXuX5bkuL249uWaIhpTheRGA==
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=URj4Q+ss1TpaKsVl2EfB/s5ywXc+9aWpk+suj/lbCuo=; b=ux+mPgCwRxrTFxI70NEoOFar3foMzEOcQnTlsKbWgesbK1fKQ2NYiOz65YJJ9EmhDvEn0jQy9UNJHZxp7j64fSFVTd+bVystBNbPNTsuEyT3xBsTCf2GFNxULyLG2TMRdbZ0wTZyJAsFY2EXXbD/fZ16LZmvfljpJUanVjWT9etndUOYWtgSkZDokFpOaAld0sfkEzH1HZI795vgrhmOvbRou9VeGWJT0z9fw99fpkJb0hpxbmM1yBrggRrbe001JuFeg/g5xteXpzrXyOBIH5ABFTBHAN9o7Gtp5+3t2C3Bd9Q4MRNJG9UblQ/lZuVZN5wzX8kpwzEtJmfRCUoYcA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=hpe.com; dmarc=pass action=none header.from=hpe.com; dkim=pass header.d=hpe.com; arc=none
Received: from SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM (2603:10b6:a03:435::16) by DS4PR84MB4018.NAMPRD84.PROD.OUTLOOK.COM (2603:10b6:8:29d::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.21.270.16; Sat, 1 Aug 2026 10:27:23 +0000
Received: from SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM ([fe80::b948:e341:5504:1d03]) by SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM ([fe80::b948:e341:5504:1d03%3]) with mapi id 15.21.0270.015; Sat, 1 Aug 2026 10:27:23 +0000
From: "Dikshit, Saumya" <saumya.dikshit@hpe.com>
To: gengnan <gengnan@huawei.com>, Zhuangshunwan <zhuangshunwan@huawei.com>, "grow@ietf.org" <grow@ietf.org>
Thread-Topic: [GROW] Comments on draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib-01 : applicability to EVPN/IRB and inter-VRF leaking
Thread-Index: AQHdHOsSkAuAmGa8fUeLhmiy2Sv1eraCUT3wgABzWeaABIxZkIABtWRf
Date: Sat, 01 Aug 2026 10:27:23 +0000
Message-ID: <SJ0PR84MB21105D7334EE7E2555C6BEA494D72@SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM>
References: <SJ0PR84MB211003FD13ADE79116CF95A794CD2@SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM> <17ac2aa7c36a4382bb16f5e3794ae0ba@huawei.com> <SJ0PR84MB2110D08B444B99E4BB9DBD5B94CB2@SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM> <a0152674820b4b7f86f80193a7064b89@huawei.com>
In-Reply-To: <a0152674820b4b7f86f80193a7064b89@huawei.com>
Accept-Language: en-IN, en-US
Content-Language: en-IN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-reactions: allow
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: SJ0PR84MB2110:EE_|DS4PR84MB4018:EE_
x-ms-office365-filtering-correlation-id: 6e25bd99-5238-4b04-edeb-08deefb77990
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|1800799024|376014|366016|23010399003|18002099003|38070700021|5023799004|56012099006|4143699003|10067099003|8096899003|22082099003;
x-microsoft-antispam-message-info: qyLTY8xpvBUomMFA8lGz7OMCDDJK7qLPPG83ydq7KtrnBLrgtBwId+zvFRimFOY3bQooXp0KmeFzEvF2jQJe5CgADNBKEXikB0sHQ65aCsojLR44vgLO31PHhsInGif8jX/EcvZiZ2b7Ut9GA01iS0MOPOny02K/t0os/A+oKfbY3CirhFHVJFJoRz8L4MH+g8VzEA2fgmkainHqE1LVVLKlvXgOSUYuMV3cizPa+joK5qtwq8k8gaejkPTXIzNAE81WNF6OGpCIMyxXHYiGvstjensK5r9ghk8LvSuIsbz99AMgqlZRjrfbWgU74fcPA4txSOZtbUFw1iNx7w/VqLzHVQyxGFIVJ5+viQVvsxviUP1ABKBlSbAtbFoRaSuLQqqxBBmewXKluJtCY0Z0OAxUvRJNkJL0pIfElFFF19zIwkbSSyf6e/6KSQtmArIl/6CPupPMt8sKvAARMyrv7RjF82MMXUuzAKVfBT3dvztgRhXTh1TaOaxrjIB3Di93hG1mGiJDh6wJqyZbcQ/oh1SsZI4/fHVXeBdYL5tcXq1GE23nDVsrVZjxCjmjgJdPBSnPtBVFVVwwYnJLEZlWr7jXCTWGZ6qMgnseKZYuS9IqdF4dpr6WiKpydmgvfdYSPBxfbXWHCKENDrYSUSRgIKeiVLoRK8tm3CB0uqsh/FikvRhzsy3/fUaf0YHEpu1e/s9rKOcp9EhX/Az9o/dyxeqTIrg1J+MzfUDM5KSJjmU=
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(13230040)(1800799024)(376014)(366016)(23010399003)(18002099003)(38070700021)(5023799004)(56012099006)(4143699003)(10067099003)(8096899003)(22082099003);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: S5jKnQELevP9avyokt1DWTRDt1aLXy923hLjis0bNheYXVTSYL893n8TvGMNlNDekW5XdKRyoGGfCvwbWqOko/mNH6PrVJiU4SuDb+lWVXh5X533wekJGOTQ9mv4kBRgoZmjUsQWr6mJ71MAvVDQ/zUPyuzUZJr4XeaPHkikfzRrD7VvugvacYVhhrzsukW89tdyQDeG6gdqiHNE6MwgyeKt1zfufh4aIySBskp0eeW6/WK1lRSVFo53r9YAPmXUdsRTSStUXQ2MQKh/ltiYffSp6nvgYZDisbxBKxROHv8vbIgqJoIyZ7cSFOwN7x51Ub1BddUYXw7E9JaSER/elr9J+Samvbes3xMWfG9mdfn28HXNd8lgXLckWvobHOAnHAcBKwgcpXFGns4H3ZQR1aiM0187P3ZcDXHVSuXfL2NmTrMcFLCJKGJjWNoEE4dGo0OX30YFnunP2KSTQRWt3f2zNJUSAhIhIktvI9/DfpSp2dpcnhpws0Cl9DaUz5sVwdfollOx4426DcN2kXj+9Kiz5bpLTGEnzlnqzj8t5jMkNxk2letaQYws94TgpRlsRfZfXSRSmD+NBdxW892evnNIYI63E5WNFltcSbqHGtoaBvqqsvW/+ZM98FN40vRmut+e0LKygtwyxbM+mD4J0OtDrJGKDNy3oqEcKDZ0HPR3BccgFC+PuekQuYCPiBO5IXiOzFI9NXXcGCckRna+2iVvYH9kar9V8iDSBuNE593BdQ+cfaiSSzUYjyohU+Pd8+Z80Uqhwn6pS2UZNfowS4P/ljBkNEnHZXUZUOlaycM2XErhf4dUCDWUt26GSHPNMSGH4IBtaDm5gBqsrwrl0ahRP2JEDtLmNmXgXfgavoKfGuAklhNoz+2l6d7MZWNXnJAl/cbXiZo2PNnhJKUZ97W2YoPNI+aVM8+PVXjramYUyayqSrUVwRgkkEhUOkdVInFkrdilTbgpCGeDQWrL6idNnW6QzQrxRerGKPoKLqyOurKXlDHONpCHp2zlwQHpFfmMFoaKEYs7M29MDTc+52ffPNg/hxmHKi5ZR5D35o+cF61lTjLv04QmqLHSp9zzkFWufv2ooMssqBRbN6ESCkdexByth8PbjrIIEePgmhJOiYFo3EWX3jVmTWxl4tlDzTus5zGiQHG+0mlTdpV79C9BwvDISlxGzc/uzeguEX7NzLnmEv+nFQyLkG86Yki1MiL1zySmXn6n4DLnHT2vjX4PuUTXLnWwKpDyFknZTICtTFl8KulSPEtJ3oaxNiiDMrAyb2JpPq1v0DknFZ8sCH9MTAeDkZd1Dl/ufhZfWrh8OY1UPM30PDHR/sE6Pai1ffr8kCsWss0e5cgHgJpF8Qfdge25zWvmsI35RYx1WqscROF5LVOGJx9Scp/pvXECB+5YqtOxkoMDgir/ZdtUBsA3KiM1gvtHNp5L/8mUfhU9uNJZd7Mx3tGbOFow4szmJ4GTLpb3UrvoBaIDPqBU7mqIk3p2uESSMkoLsNS5cE1WC3i0chXSwTZqTHCHO7NOdTudPl20IPhdq1hJ7f+Nxwe/4uGMSyXHiZDeu2IQJGb3k48o3JG0IOFe0bJIxwln6sY819mydtI5Ejwn8Jx2yxmV9yvR6pYlyGDqJ61lsFYbN2C5h0Yl3WdD/5f3Cs3/6EYt5ZA9BMqbEEOFvhB7++qfzmLmsZ+rRhUBTM0Kq/VNjXn0oF3ZrGloQnwacyDuTJfcGytb04R4qPTTp6LF3qAY33iTBAGYSndh5j9D5FE=
Content-Type: multipart/alternative; boundary="_000_SJ0PR84MB21105D7334EE7E2555C6BEA494D72SJ0PR84MB2110NAMP_"
MIME-Version: 1.0
X-Exchange-RoutingPolicyChecked: Jz6lUmAxnegNvSVGAkF/3pry5UEqRjXbz54rLURT4SjZcTIw2QSoF0OWItbFN0DvkvZGCX1dU1+9yWYDUx78aJZ68rISOaR4zYaJsFLJNnKuhOdsTn15lFWBOQ17KLrg7F9mhmMbKlAiy0T1mRZZtrSqMqZ3bEQNGMl4cHyjRANMxKWyf+V8aRaW4fbZdcM5UPjwb8qaYjKnK0567Py96afadTgPe0r0acxY2vqZ1ki7bwzfUShst8mtDgFNzWKGksBFbainfx4WgTxnXxKl6boj8Gbixd8RcS87CHUADUwHQXPXS71KShYn2RtXRzJ20LUiu2rgH3hyFmmvJFs5lQ==
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 6e25bd99-5238-4b04-edeb-08deefb77990
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Aug 2026 10:27:23.0371 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: bI8lYfxMxMKKYwaIcaGXSZpdgMLH3Yz/jvvurZ3hq/z3FAw2LvCl6dxZKdF/G7Wv+axzt1fW1K0MIeVXZ6KcEA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DS4PR84MB4018
X-OriginatorOrg: hpe.com
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwODAxMDA3OSBTYWx0ZWRfX4fJj65c0g4YG UnscNwvq+nLhKgOvbg908j0u/2Bm6vqfMpHTg/2J5eiVb5R3x+FMRvkxlT8bduqAk7P7KAIcd3r SAENtWlzNCl0WbsXqQu5dOw2GCtyDdf5aEHtI5R72132Cz/aOhSUBKCLnDTbUHUxQ46QSUuMZmq T/Km5S5qYcIF/4myI2nksJP29Ub69XqPO7HzpVMJ1G7MBAmrL0xRqSkHkUfkEjnEiDP/j7PI/RF gH7fZLc2AlWt6a7trG4LvHaMUT51b7qrIqmkLymXq50ng31x4W412yLbHwGdlpkjg12nFYBhVcr whTj0O08dSGN85Ie7ZiEfOXrp4nVm2tlGcbEfCATO6S/SPEuJHCfWKYd1S73tCJwN4DyUHkd0Mc 9gdefBFJeOlQn/ikXcGLvgfPMBgv5+HKITboQkvmb4fJn7P0jlsh+DXa1rUzE4D4Y/RNV6Jsw9u jb7P/t9g1Nv9pKxw2aA==
X-Authority-Analysis: v=2.4 cv=OLEXGyaB c=1 sm=1 tr=0 ts=6a6dca14 cx=c_pps a=5jkVtQsCUlC8zk5UhkBgHg==:117 a=5jkVtQsCUlC8zk5UhkBgHg==:17 a=z/mQ4Ysz8XfWz/Q5cLBRGdckG28=:19 a=lCpzRmAYbLLaTzLvsPZ7Mbvzbb8=:19 a=xqWC_Br6kY4A:10 a=Sv0fKeRqtYgA:10 a=VkNPw1HP01LnGYTKEx00:22 a=gQcMVamqm3wCPoSYhaRC:22 a=J0OTuHAx6l5K1fCpvPfz:22 a=NEAV23lmAAAA:8 a=i0EeH86SAAAA:8 a=MvuuwTCpAAAA:8 a=48vgC7mUAAAA:8 a=UtV5FjuMAAAA:8 a=pIy3aK3ZneHFoVeVIsUA:9 a=lqcHg5cX4UMA:10 a=QEXdDO2ut3YA:10 a=EMfNrW2h4Hi0SXIO:21 a=hTZeC7Yk6K0A:10 a=_W_S_7VecoQA:10 a=ehT88nhQmDs7a44Z_RBH:22
X-Proofpoint-ORIG-GUID: fkrUBHxm_qEJDkD-PEPowGyN0ijmh8ze
X-Proofpoint-Spam-Info: AW1haW4tMjYwODAxMDA3OSBTYWx0ZWRfX1/F7pNRA4SRO sQpeoKfRm3nNkR8arEvbVqTuU7vccgkbxGxZLOmsQ08MUYU0u37fOW6CCOeANdMw+L8f/P/1Btl +zFr/Q2Jg3118blOkArXaJxTBfSKJ5k=
X-Proofpoint-GUID: fkrUBHxm_qEJDkD-PEPowGyN0ijmh8ze
X-HPE-SCL: -1
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1143,Hydra:6.1.134,FMLib:17.12.100.49 definitions=2026-07-31_07,2026-07-30_01,2025-10-01_01
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 malwarescore=0 spamscore=0 impostorscore=0 adultscore=0 lowpriorityscore=0 clxscore=1015 suspectscore=0 bulkscore=0 priorityscore=1501 phishscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2606150000 definitions=main-2608010079
Message-ID-Hash: CTCY5WYCGJVNPI73EDBOQJYD2IEEQDKN
X-Message-ID-Hash: CTCY5WYCGJVNPI73EDBOQJYD2IEEQDKN
X-MailFrom: saumya.dikshit@hpe.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-grow.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib@ietf.org" <draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib@ietf.org>, "Srivastava, Mukul" <mukul.srivastava@hpe.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [GROW] Re: Comments on draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib-01 : applicability to EVPN/IRB and inter-VRF leaking
List-Id: Grow Working Group Mailing List <grow.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/l-fugInsAlvFfanmeOIY5D5bbGY>
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>
Thank you Nan, I will do that by early next week. Looking forward to a fruitful collab. Best Regards, Saumya. ________________________________ From: gengnan <gengnan@huawei.com> Sent: Friday, July 31, 2026 2:04:06 pm To: Dikshit, Saumya <saumya.dikshit@hpe.com>; Zhuangshunwan <zhuangshunwan@huawei.com>; grow@ietf.org <grow@ietf.org> Cc: draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib@ietf.org <draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib@ietf.org>; Changwang Lin <linchangwang.04414@h3c.com>; Srivastava, Mukul <mukul.srivastava@hpe.com> Subject: RE: [GROW] Comments on draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib-01 : applicability to EVPN/IRB and inter-VRF leaking Hi Saumya, Thank you for your proposal. We can work together to figure out how to integrate your contributed content, and some points may need discussion during this process. Could you please create a PR to the repo (https://github.com/XiaoTianCan/BMP-docs)? Once merged, we can bring the discussion outcomes back to the WG. Thanks. Contributions and comments from other WG members are also welcome. Best, Nan From: Dikshit, Saumya <saumya.dikshit@hpe.com> Sent: Tuesday, July 28, 2026 7:03 PM To: Zhuangshunwan <zhuangshunwan@huawei.com>; grow@ietf.org Cc: draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib@ietf.org; Changwang Lin <linchangwang.04414@h3c.com>; Srivastava, Mukul <mukul.srivastava@hpe.com> Subject: Re: [GROW] Comments on draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib-01 : applicability to EVPN/IRB and inter-VRF leaking Hi Shunwan, Nan, Haibo, Thanks for the quick and positive turnaround. I am glad the Remote VRF Information TLV generalization is useful. Below is a concrete proposal for the EVPN/IRB text and worked example we'd like to contribute to -02. 1. Proposed addition: New subsection under Section 2.1 (Remote VRF Information TLV), e.g., "2.1.4. Applicability to EVPN Type-5/IRB Inter-VRF Route Leaking”. The TLV as defined (Information Type/Length, Index, AFI, SAFI, Remote BGP ID, Remote Route Distinguisher) already generalizes cleanly to EVPN (AFI=25, SAFI=70) without any wire-format change, only an applicability statement and example are needed. Proposed text: “" The Remote VRF Information TLV defined in Section 2.1 applies equally to EVPN Loc-RIB [RFC9069] reporting for EVPN Route Type 5 (IP Prefix Route) [RFC7432] [RFC9135] routes that have been leaked between EVPN Instances (EVIs) via Integrated Routing and Bridging (IRB), by setting AFI=25, SAFI=70 in the TLV. This addresses the "dynamic inter-VRF route leaking (IVRL)” gap noted in [I-D.saum-grow-bmp-afi-safi-evpn], which defines per-EVI counters (Stats Type=1) that quantify how many routes were leaked into a given EVI, but does not itself identify which remote EVI each leaked route came from. This document's TLV supplies that missing "from which remote EVI" detail; the two mechanisms are intended to be used together, not as alternatives. “" 2. Proposed worked example (parallel to Figures 1-4/8-9, EVPN/IRB case): PE1 hosts EVI11 (RD11, import RT1) with a symmetric-IRB L3VNI. PE2 hosts EVI21 (RD21, export RT1), whose locally attached CE advertises IP Prefix P1 as an EVPN Route Type 5. PE1 imports P1 into EVI11 via IRB. Today, PE1 reporting the Loc-RIB routing information in EVI11 to the BMP server only shows: Prefix: P1 Nexthop: <PE2 address> Peer Distinguisher: RD11 --> The RD of EVI11 on PE1 Peer Address: 0.0.0.0 Peer BGP ID: <PE1 router-id> --> The router-id of EVI11 And, with no way for the collector to tell that P1 was leaked in from EVI21 on PE2 specifically (as opposed to being locally originate in EVI11, or leaked from some other EVI sharing RT1). Using the Remote VRF Information TLV (AFI=25, SAFI=70): Prefix: P1 Nexthop: <PE2 address> Peer Distinguisher: RD11 --> The RD of EVI11 on PE1 Peer Address: 0.0.0.0 Peer BGP ID: <PE1 router-id> --> The router-id of EVI11 Remote BGP ID: <PE2 address> Remote Route Distinguisher: RD21 --> The RD of the remote EVI A collector correlating this with the per-EVI leaked-route gauge ([I-D.saum-grow-bmp-afi-safi-evpn] Section 2.2, Stats Type=1, Subtype=5 for Route Type 5) can now attribute both "how many routes were leaked into EVI11" (the gauge) and "specifically which remote EVI they came from" (this TLV) from a single, correlated BMP feed. 3. Registry note: our companion draft [I-D.dikshit-grow-bmp-rd-scoped-rib-stats] already reserves Family value 1 ("L3VPN (VPN-IPv4/VPN-IPv6 Loc-RIB)") in its RD-Scoped Statistics Family registry as an offer for this document (or a companion) to adopt as a statistics-side complement to the Remote VRF Information TLV, should you want a gauge (e.g. "leaked routes from remote RD X") alongside the TLV rather than only per-route TLV attachment. No action needed on your side unless useful ; flagging it since it's directly relevant to the EVPN/IRB text above. Would you prefer we send the above as a literal text diff against your -01 .txt/.xml source, or is a prose description like the above enough for you to fold in yourselves for -02? Thanks again. Looking forward to working on this together. Best regards, Saumya (on behalf of Mukul Srivastava and Changwang Lin, co-authors of [I-D.saum-grow-bmp-afi-safi-evpn] and [I-D.dikshit-grow-bmp-rd-scoped-rib-stats]) From: Zhuangshunwan <zhuangshunwan@huawei.com<mailto:zhuangshunwan@huawei.com>> Date: Tuesday, 28 July 2026 at 11:59 AM To: Dikshit, Saumya <saumya.dikshit@hpe.com<mailto:saumya.dikshit@hpe.com>>; grow@ietf.org<mailto:grow@ietf.org> <grow@ietf.org<mailto:grow@ietf.org>> Cc: draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib@ietf.org<mailto:draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib@ietf.org> <draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib@ietf.org<mailto:draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib@ietf.org>>; Changwang Lin <linchangwang.04414@h3c.com<mailto:linchangwang.04414@h3c.com>>; Srivastava, Mukul <mukul.srivastava@hpe.com<mailto:mukul.srivastava@hpe.com>> Subject: RE: [GROW] Comments on draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib-01 : applicability to EVPN/IRB and inter-VRF leaking Hi Saumya, Greatly appreciate your positive feedback on the Remote VRF Information TLV approach. Please feel free to integrate your team's ideas and proposals into the -02 version. Let's collaborate to shape a comprehensive new version together. Best regards, Shunwan (on behalf of the co-authors of draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib) From: Dikshit, Saumya <saumya.dikshit@hpe.com<mailto:saumya.dikshit@hpe.com>> Sent: Sunday, July 26, 2026 6:50 PM To: grow@ietf.org<mailto:grow@ietf.org> Cc: draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib@ietf.org<mailto:draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib@ietf.org>; Changwang Lin <linchangwang.04414@h3c.com<mailto:linchangwang.04414@h3c.com>>; Srivastava, Mukul <mukul.srivastava@hpe.com<mailto:mukul.srivastava@hpe.com>> Subject: [GROW] Comments on draft-zhuang-grow-bmp-enhancement-for-vrf-loc-rib-01 : applicability to EVPN/IRB and inter-VRF leaking Hi Shunwan, Nan, Haibo, The Remote VRF Information TLV nicely closes the "which remote VPN instance did this best-path come from" gap in RFC 9069 Loc-RIB reporting. I believe there's a directly analogous problem on the EVPN side that this draft's mechanism could cover with minor generalization: * draft-saum-grow-bmp-afi-safi-evpn defines per-EVI EVPN RIB stats keyed by RD (Section 2.2), and separately calls out "dynamic inter-VRF route leaking (IVRL)" for EVPN Type-5/IRB routes as an area needing counters. * Today your draft scopes the Remote VRF Information TLV to VPNv4/VPNv6 Loc-RIB only (Figure 1 example). * Would you be open to extending the applicability statement to the EVPN AFI/SAFI (25/70). * Thus, single Remote VRF Information TLV mechanism covers both L3VPN and EVPN-IRB inter-VRF leak visibility? * If that's in scope for a -02, we'd like to contribute the EVPN-side text and an example (analogous to your Figure 1) showing an EVPN Type-5 (prefix) route leaked across VRFs with the Remote VRF Information TLV attached. (Hi Nan, a separate topic from your rel-enhancement/filtering thread which I was trying keep pace with. Just flagging in case both land in your inbox close together.) Let us know if a joint revision makes sense, happy to send a draft diff. @Srivastava, Mukul<mailto:mukul.srivastava@hpe.com> and @Changwang Lin<mailto:linchangwang.04414@h3c.com> are also co-author to draft-saum-grow-bmp-afi-safi-evpn Thanks , Saumya
- [GROW] Comments on draft-zhuang-grow-bmp-enhancem… Dikshit, Saumya
- [GROW] Re: Comments on draft-zhuang-grow-bmp-enha… Zhuangshunwan
- [GROW] Re: Comments on draft-zhuang-grow-bmp-enha… Dikshit, Saumya
- [GROW] Re: Comments on draft-zhuang-grow-bmp-enha… gengnan
- [GROW] Re: Comments on draft-zhuang-grow-bmp-enha… Dikshit, Saumya
- [GROW] Re: Comments on draft-zhuang-grow-bmp-enha… Dikshit, Saumya
- [GROW] Re: Comments on draft-zhuang-grow-bmp-enha… Dikshit, Saumya
- [GROW] Re: Comments on draft-zhuang-grow-bmp-enha… gengnan
- [GROW] Re: Comments on draft-zhuang-grow-bmp-enha… Dikshit, Saumya
- [GROW] Re: Comments on draft-zhuang-grow-bmp-enha… gengnan
- [GROW] Re: Comments on draft-zhuang-grow-bmp-enha… Dikshit, Saumya
- [GROW] Re: Comments on draft-zhuang-grow-bmp-enha… Dikshit, Saumya
- [GROW] Re: Comments on draft-zhuang-grow-bmp-enha… Dikshit, Saumya