Re: [bess] Queries to authors of https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html

"Dikshit, Saumya" <saumya.dikshit@hpe.com> Tue, 05 March 2024 02:23 UTC

Return-Path: <saumya.dikshit@hpe.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E67A4C165518; Mon, 4 Mar 2024 18:23:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.793
X-Spam-Level:
X-Spam-Status: No, score=-2.793 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_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hpe.com
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 VijJP3HrIttK; Mon, 4 Mar 2024 18:22:59 -0800 (PST)
Received: from mx0a-002e3701.pphosted.com (mx0a-002e3701.pphosted.com [148.163.147.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 433A1C151985; Mon, 4 Mar 2024 18:22:59 -0800 (PST)
Received: from pps.filterd (m0150242.ppops.net [127.0.0.1]) by mx0a-002e3701.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 424LMYtL002719; Tue, 5 Mar 2024 02:22:58 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hpe.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=pps0720; bh=HdKbVk2/N6+2RPsxUn9VPs7KeS0Epc/72sU6SnDLnP4=; b=j9Mk0bKZ87/ijQDxsbi8fEIs4J6AQgim4ZVf5vIf+BaFE9+wMjEl4hZuz0VRELYU3jOO LALEs3wCmVYLGemY/qUm2OsFgA2/5Gg22LIZ3s8FMf61x7/maw5yerpsIy1uPuDmmzS+ 6nGheDkTYOd8siwORlbGNO9mBuSuvZ5JjAHD4xoR2M2mPzFpR6jQiR88zOmuHufBsapm JDOqsM0H4Nd/KVOgtSI4YOto6S4mcVQxpyYinQyaRaPj0cHSC6L0s8/w9a4U4HLisnpj RH4y4qez/u0zpW65hELPRz/fQ6+o8xC2YiTQJPRRu1u12lD7mrPUDH2/SqTxjwiR7kay /Q==
Received: from p1lg14881.it.hpe.com ([16.230.97.202]) by mx0a-002e3701.pphosted.com (PPS) with ESMTPS id 3wnp5fuan8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 05 Mar 2024 02:22:58 +0000
Received: from p1wg14925.americas.hpqcorp.net (unknown [10.119.18.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by p1lg14881.it.hpe.com (Postfix) with ESMTPS id AB0E0804DD8; Tue, 5 Mar 2024 02:22:57 +0000 (UTC)
Received: from p1wg14927.americas.hpqcorp.net (10.119.18.117) by p1wg14925.americas.hpqcorp.net (10.119.18.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.42; Mon, 4 Mar 2024 14:22:39 -1200
Received: from p1wg14923.americas.hpqcorp.net (10.119.18.111) 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.986.42; Mon, 4 Mar 2024 14:22:39 -1200
Received: from p1wg14919.americas.hpqcorp.net (16.230.19.122) by p1wg14923.americas.hpqcorp.net (10.119.18.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.42 via Frontend Transport; Mon, 4 Mar 2024 14:22:39 -1200
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (192.58.206.35) by edge.it.hpe.com (16.230.19.122) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.42; Mon, 4 Mar 2024 14:22:38 -1200
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SiupzJQb97bzgnVzE8NsQ2U8v9KsStAb90M1u3EgckaS3uuCz7RkI1MZeuH/loFS5ubBwlQlCMtydqGbKwzLnlKHdEZsa/EykFHHw8PDOdtFCL7h+GG2Xh6Eipbv73MBpVDXbqeC3dh2y2D9gc37WAyubaBZkkxOZufhZ96Iu/CSGstAl4/jyJ+gpAEihBXvae3T1z8F+G4qeLCKgdo+5B6etNWOq0BHigrWLaN6VJaPe9NPe3e0XVCqvzXwqVwazxH41EarpJTXTXUoFEfkk0ognpi9QxvF9rfiu1kyE/EBKpPexFN//6wtcSyhym1nhtGnRb+bfE8dRdEuAc5V2Q==
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=fMZ6KkAlS2E2hyZ1ns1jjqYeMxdBSy9DBshxuwDyR4A=; b=dpUaOSp3HpvRn9i342dflgaQGPS/wOlKraB0icaEtR5eozisH6bLHwXo0xftolqtUnJOgQndHNoxdZg9l2sakEufg/A4E6PO32CzUD2McE59w35m8+i/nY3QRPWhB2QRtJ2RqANnG1GXiFH7j/4647cC+SXjEomeE38SaEMupNub+UfIllUEqQ0coASA0QMpTF6ez7TUns7mWWzX1aaIVoigr/CW6z/V8OBW58JvTI3WygdkqlN5DsxwjXOAum6PGX4D9V27thaX4wnlbJHyz3qO/HEkhBXDkoUJ83G1O94xEB3IURGpaLxto+2aEdn0qlTQvAXcz+RbywBIgZoWdw==
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 SA1PR84MB3958.NAMPRD84.PROD.OUTLOOK.COM (2603:10b6:806:3e1::6) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7362.22; Tue, 5 Mar 2024 02:22:36 +0000
Received: from SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM ([fe80::1886:d59f:a929:8023]) by SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM ([fe80::1886:d59f:a929:8023%3]) with mapi id 15.20.7339.019; Tue, 5 Mar 2024 02:22:36 +0000
From: "Dikshit, Saumya" <saumya.dikshit@hpe.com>
To: "Jorge Rabadan (Nokia)" <jorge.rabadan=40nokia.com@dmarc.ietf.org>, "Allu, Ramaprasad" <ramprasad.na@hpe.com>, "bess@ietf.org" <bess@ietf.org>, "draft-sajassi-bess-evpn-ip-aliasing@ietf.org" <draft-sajassi-bess-evpn-ip-aliasing@ietf.org>
CC: "bess-chairs@ietf.org" <bess-chairs@ietf.org>
Thread-Topic: Queries to authors of https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html
Thread-Index: AQHaZLP3+FZAGvk3UkqcM6UNKbda0bEnKHTwgADxh2CAAGL1EA==
Date: Tue, 05 Mar 2024 02:22:36 +0000
Message-ID: <SJ0PR84MB211019903AA1E46B96FD333294222@SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM>
References: <DM4PR84MB1830AEC3FCC57F3A127AF76382572@DM4PR84MB1830.NAMPRD84.PROD.OUTLOOK.COM> <DM4PR84MB183025E380A2252E6595458782232@DM4PR84MB1830.NAMPRD84.PROD.OUTLOOK.COM> <DS7PR08MB6862B8659BFE7F8879676987F7232@DS7PR08MB6862.namprd08.prod.outlook.com>
In-Reply-To: <DS7PR08MB6862B8659BFE7F8879676987F7232@DS7PR08MB6862.namprd08.prod.outlook.com>
Accept-Language: en-IN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: SJ0PR84MB2110:EE_|SA1PR84MB3958:EE_
x-ms-office365-filtering-correlation-id: 2e11b237-1f6a-4017-d7dd-08dc3cbb1f80
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: T5n+h+QhrTk8NxDduu3Cs/jtNDJslsTPENpIRmx45jKd025wtBLmdlq+tlXfJItu+yRML73JTG8kv22hJAdsK8uB048RfX5rzYtSW8AOHcYNDJXHXpW4Dvgtzjf8e8090cb7/jE3eY7U8i7UWrHlxzcCpcvWdLgceVrLx6+XI08/RKpufcuIp2WVNGtwKqi4dUAdDjaVNNNYOxDYo/4HOlHOsjAR1/rzAZwQ7GHrrPXMTonCYeD6xRQCfhCpDXI5wNvmaBlm5OI1zoeVpS+57gkTrZEpSiHbalMaLjczYxb/I5DbQ3L2uv+fapAUfBkIqE73HOrxmPNBp5KNKWOczopMdOuT5RMqGZMTmTUBxwO2rBQBZDfezFrNF/o62/Bma6+FHDcizqQUeBkobaDjN03CqWCKvz9Io0owG0hEtIZIIIW6p74UyPwvyRimV5t/sS4h7NKOND1BG4J3oEAgVLy/qQyd/BGL7N12babxWKkXttk8HJsBl1WST/m6f2uZhcu/+FgO1GZ7SNvrpg1K7SWp2ur7UC38ZSBWD/BwwCwrwQWUgXYMR9efIGX3Sr3spXS3Wt66hENOztyvXthl72CdcalFCkYB3YY5sE+3P1VjU1+LWfLdofOihnmwAWi14G/+yX89NWmqUnFphgIpVw+ESm4ncjC/veim1ifYZmw=
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:(13230031)(376005)(38070700009); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: xoeEt8u42/4q5lcCVV9ii9jkhD4UjiMAWwkTDTPonsSHe9RT7wePUxDAXNdd1CQlqJkPF0IKoflnH/XcsidPTb++f/0HpPRtK2X3cgWt2mBJczmx0RR/jmTkXVnfrvpBA0d8J0S2iRwcxfnC/KqU+quUV2eOXvUnGvpUPRfsRIV/lRm01SB7KcKaMJktMN5QjcuHx650sb1xYVU1VQByFrh7Z6KMtHfkkE0c0v/xmbvrIPHoEVnyK/gGTEhyNGYLxb4fPnfgxXOpN7Elovq0so2UdZP/SeTh1Bq5nbKoqEbLSK2maMet0dygo460vy7tgJPk+iXmcrhFrNTEfFk6OmhqyrjD1pgKyXLzNIsUNfUCn8eUg3FpV8gxBcdgUZotM7Av7epThXllUQSqiON9HvUeZmpKeABtFqq2czm4J3i1M6dolJMcHCPxkSButlyHj9W+viOK9fIQC0IWpwtb0YmeOcPDM5/ZPey/p1PzPlw5BgnR45WsImK9S3Pk4YunceVlKu0K+rZcYKFwM2nuGOeziED76aolQeF3MLBReyLWWQ2ap7/ovvXLiuAjLV42qBwQX1FIti6H6Y1+rXnkTeAIQz9EGancB/JOW0iAxkIlF7gwkeQD6GseUtGxZcXXw4CUWYam1vQDufX6f/NX2DBmF9nv3RvqvfUr82Ldl16uWPhdPNl07IOYMYl9S9IBNz0C2PIacmNykYrf24BAWFhWdr/dXm+JSX+w7ZNWpQOZTWejzfoO2ExnFLk8bjHy5VbiTWFSGH9R8JhCYB0Iev9nT88csJN142iXUwvyNiXDZTdc1GBBC+5hskKtWXlr9/uejuyn9Yc4gjXTyYCLtQUd2JCCozuuv3t447yUT45JiYwWwT/6hNKctNkLuCO9mt8msfRhZKbmNuuXg4vvQ6gXwpFggacbVcMTBDjMA19eU5UQvOVdRZQdEdOdvp6Jnx+lYExhtMDNOx97MwQpBhKPqQVJYp+izRjazs4x1h8nenRsGzYAy7GJRNBGW3rR2Bgn2lTco1+r6oX9BN/qARXJOnPo3ikzT8YiKGBQnEX7CRTzcfPJen1e/dCiDSUIM1gWIuCMIYuBrjYvnKFjA72EnAkUrPgEe7/V1wZREu/hxuByj4wuEh/bYj0nahYWnkYS3lCPbBigBhJT9Zuk2iKD7KBliNd06M6Vnb4+fQFCfEkqFcdzvt5+c2TH5CUGiSPQx9pow4zPLt4E3+uM40x3YtUYiLcD9SnxYqm4yFyzcwE9WqPF1FcUJHrfPZg/yywpFpYLATZHrWUN4+YfLEpF2JGthkiXprWUBNO/k/2JFowNDC/C5w5quPZt93nXrSpA39D/y1KNusrTUXtP8lzVNSwu/VbxbPPKrKIXpaWzRCqPgGUN3s2rBcxZawseJhF+FUe/j1RjZZky7hSX4NpcDgXxLNS1Q3/S20g4qPtLnHrO1oUL6ZljJYFki712gTooQ98tP+86ApTRx+sKWoar++rf21jI7mNIo7CaqjpayIIxW8gk8Anx8zmuzClkX5GYRQswMduDVUSQ53YnS7PlRqWB/leAzBtfUvfgcAyeaG5LvuvPNMtUUttW/zYe
Content-Type: multipart/alternative; boundary="_000_SJ0PR84MB211019903AA1E46B96FD333294222SJ0PR84MB2110NAMP_"
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 2e11b237-1f6a-4017-d7dd-08dc3cbb1f80
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Mar 2024 02:22:36.4256 (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: UkGWFQNZMXccHsBtnIICw1A0UxAHK0eyuV8BRwVg7p+NhFCb2QKYJDPa3mdpmflacu88EpCcoWQ37QKoxx1DXw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SA1PR84MB3958
X-OriginatorOrg: hpe.com
X-Proofpoint-ORIG-GUID: 4tlsfhevnEqn-yddrICViLyheUAWYsv5
X-Proofpoint-GUID: 4tlsfhevnEqn-yddrICViLyheUAWYsv5
X-Proofpoint-UnRewURL: 12 URL's were un-rewritten
MIME-Version: 1.0
X-HPE-SCL: -1
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.1011,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2024-03-04_20,2024-03-04_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 spamscore=0 impostorscore=0 phishscore=0 malwarescore=0 lowpriorityscore=0 mlxlogscore=999 mlxscore=0 adultscore=0 clxscore=1011 suspectscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2311290000 definitions=main-2403050016
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/gi0_mKA2Vz1Xdfe59_-B5gssYG0>
Subject: Re: [bess] Queries to authors of https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Mar 2024 02:23:04 -0000

Hi Jorge,

Is this the same RD for IP VRF (uniquely defined for IP-AD per EVI route), that should be leveraged for host routes in Route Type-2 and Prefix Routes in Route Type-5 ? Is that the safe assumption (as per rfc9135/9134) ?

In case yes, then If we have a unique RD for the IP-VRF, what RD should be used for the NLRI in the Route-Type-2 carrying MAC/IP for tied to MAC-VRF and IP-VRF ?  Should it be MAC-VRF RD or IP-VRF RD.

Regards,
Saumya.

From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of Jorge Rabadan (Nokia)
Sent: Tuesday, March 5, 2024 1:57 AM
To: Allu, Ramaprasad <ramprasad.na@hpe.com>; bess@ietf.org; draft-sajassi-bess-evpn-ip-aliasing@ietf.org
Cc: bess-chairs@ietf.org; Dikshit, Saumya <saumya.dikshit@hpe.com>
Subject: Re: [bess] Queries to authors of https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html

Hi Ramaprasad,

About this:


“If MPLS label field is not considered for BGP route key, then BGP RIB will have only one route entry at any given point of time.

That is, IP A-D per EVI route overwrites Ethernet AD per EVI and vice-versa if same RD is used for IP-VRF and MAC-VRF.”

The Ethernet AD per EVI route and IP AD per EVI routes must use different RDs. It was sort of implicit, since the former one uses the RD of the MAC-VRF and the latter the RD of the IP-VRF, but we added this in rev 01 to make sure there is no misunderstanding:

          *  The Route-Distinguisher is for the corresponding IP-VRF.  The
            Route-Distinguisher allocated for the IP-VRF MUST be unique in the
            PE.

Hope it helps.

Thank you,
Jorge

From: Allu, Ramaprasad <ramprasad.na@hpe.com<mailto:ramprasad.na@hpe.com>>
Date: Sunday, March 3, 2024 at 10:04 PM
To: bess@ietf.org<mailto:bess@ietf.org> <bess@ietf.org<mailto:bess@ietf.org>>, draft-sajassi-bess-evpn-ip-aliasing@ietf.org<mailto:draft-sajassi-bess-evpn-ip-aliasing@ietf.org> <draft-sajassi-bess-evpn-ip-aliasing@ietf.org<mailto:draft-sajassi-bess-evpn-ip-aliasing@ietf.org>>
Cc: bess-chairs@ietf.org<mailto:bess-chairs@ietf.org> <bess-chairs@ietf.org<mailto:bess-chairs@ietf.org>>, Dikshit, Saumya <saumya.dikshit@hpe.com<mailto:saumya.dikshit@hpe.com>>
Subject: Re: Queries to authors of https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html>
You don't often get email from ramprasad.na@hpe.com<mailto:ramprasad.na@hpe.com>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>


CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information.


Hi Authors,

Gentle reminder.
Can you please take a look at it and respond to below query?

Thanks,
Ramaprasad
From: Allu, Ramaprasad <ramprasad.na@hpe.com<mailto:ramprasad.na@hpe.com>>
Date: Wednesday, 21 February 2024 at 5:40 PM
To: bess@ietf.org<mailto:bess@ietf.org> <bess@ietf.org<mailto:bess@ietf.org>>, draft-sajassi-bess-evpn-ip-aliasing@ietf.org<mailto:draft-sajassi-bess-evpn-ip-aliasing@ietf.org> <draft-sajassi-bess-evpn-ip-aliasing@ietf.org<mailto:draft-sajassi-bess-evpn-ip-aliasing@ietf.org>>
Cc: bess-chairs@ietf.org<mailto:bess-chairs@ietf.org> <bess-chairs@ietf.org<mailto:bess-chairs@ietf.org>>, Dikshit, Saumya <saumya.dikshit@hpe.com<mailto:saumya.dikshit@hpe.com>>
Subject: Queries to authors of https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html>
Hi Authors of draft https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html<https://www.ietf.org/archive/id/draft-ietf-bess-evpn-ip-aliasing-00.html>

I have a following query on the draft.  Please help with your response.


Context of section https://www.ietf.org/archive/id/draft-sajassi-bess-evpn-ip-aliasing-09.html#section-3.1<https://www.ietf.org/archive/id/draft-sajassi-bess-evpn-ip-aliasing-09.html#section-3.1>,

In the section, it is mentioned that the construction of the IP A-D per EVI route is same as that of the Ethernet A-D per EVI route. The NLRI consists of the following,

                +---------------------------------------+

                |  Route Distinguisher (RD) (8 octets)  |

                +---------------------------------------+

                |Ethernet Segment Identifier (10 octets)|

                +---------------------------------------+

                |  Ethernet Tag ID (4 octets)           |

                +---------------------------------------+

                |  MPLS Label (3 octets)                |

                +---------------------------------------+



And as per https://www.rfc-editor.org/rfc/rfc7432.html#section-7.1<https://www.rfc-editor.org/rfc/rfc7432.html#section-7.1>, “ for the purpose of BGP route key processing, only the Ethernet

   Segment Identifier and the Ethernet Tag ID are considered to be part

   of the prefix in the NLRI.  The MPLS Label field is to be treated as

   a route attribute as opposed to being part of the route”



If MPLS label field is not considered for BGP route key, then BGP RIB will have only one route entry at any given point of time.

That is, IP A-D per EVI route overwrites Ethernet AD per EVI and vice-versa if same RD is used for IP-VRF and MAC-VRF.



Is there any reason for explicit mention of not using MPLS label field as key for BGP route or not carrying two labels one for Ethernet A-D per EVI and another for IP-AD per VRF?

In this case, I see only MPLS Label (VNI in case of VXLAN) is the distinguisher if same RD is used for both IP-VRF and MAC-VRF.



And to keep two separate routes in BGP RIB, we need to use MPLS label also one of the keys in addition to RD, ESI and ETAG fields.

Or Carry both the labels and extended communities as part of single A-D per EVI route and store single route in the global BGP RIB.



Please let me know what you think.



Thanks,

Ramaprasad