Re: [bess] A couple of question about draft-ietf-bess-evpn-ac-aware-bundling

Alexander Vainshtein <Alexander.Vainshtein@rbbn.com> Tue, 06 February 2024 13:55 UTC

Return-Path: <alexander.vainshtein@rbbn.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 4F5FEC14F70F for <bess@ietfa.amsl.com>; Tue, 6 Feb 2024 05:55:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 (1024-bit key) header.d=rbbn.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 q5QmmPXepy42 for <bess@ietfa.amsl.com>; Tue, 6 Feb 2024 05:55:00 -0800 (PST)
Received: from usb-smtp-delivery-110.mimecast.com (usb-smtp-delivery-110.mimecast.com [170.10.151.110]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 393FAC14F68C for <bess@ietf.org>; Tue, 6 Feb 2024 05:55:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rbbn.com; s=mimecast20230413; t=1707227699; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Wyarp1v/SnV7a86rVE6TQWiwp9DvNFVyHcY5QLY+hCQ=; b=O2P/VaShQ5cqXY7ocB0t4/+qjCbkn9tWI4sUsPBAxnkTXShOWGr7MlFK8dlOqp6U0QInMG oGGx1UoZy/c24KjT03QXoOBVmdiI8rz1MhV4EnCQzlAxXQWaOLvzLv4SYo2VEdjb4bDAdE sQeBU2QodNycUEcR8mfgEF4Upt1Rugk=
Received: from BN8PR05CU002.outbound.protection.outlook.com (mail-eastus2azlp17013021.outbound.protection.outlook.com [40.93.12.21]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id usb-mta-39-pgx4FlRnNguBZIY8OlchSg-1; Tue, 06 Feb 2024 05:54:53 -0800
X-MC-Unique: pgx4FlRnNguBZIY8OlchSg-1
Received: from PH0PR03MB6300.namprd03.prod.outlook.com (2603:10b6:510:e2::5) by SJ2PR03MB7330.namprd03.prod.outlook.com (2603:10b6:a03:562::6) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7249.36; Tue, 6 Feb 2024 13:54:49 +0000
Received: from PH0PR03MB6300.namprd03.prod.outlook.com ([fe80::c771:5454:2384:e312]) by PH0PR03MB6300.namprd03.prod.outlook.com ([fe80::c771:5454:2384:e312%5]) with mapi id 15.20.7249.035; Tue, 6 Feb 2024 13:54:49 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@rbbn.com>
To: "draft-ietf-bess-evpn-ac-aware-bundling@ietf.org" <draft-ietf-bess-evpn-ac-aware-bundling@ietf.org>
CC: "bess@ietf.org" <bess@ietf.org>
Thread-Topic: A couple of question about draft-ietf-bess-evpn-ac-aware-bundling
Thread-Index: AdpZALeX0OUpDl5/T6KckC4m9sZvmwAAv6jw
Date: Tue, 06 Feb 2024 13:54:49 +0000
Message-ID: <PH0PR03MB63002AA6019CF145648592BDF6462@PH0PR03MB6300.namprd03.prod.outlook.com>
References: <PH0PR03MB63003473CBEA5A22D1BE1B3CF6462@PH0PR03MB6300.namprd03.prod.outlook.com>
In-Reply-To: <PH0PR03MB63003473CBEA5A22D1BE1B3CF6462@PH0PR03MB6300.namprd03.prod.outlook.com>
Accept-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: PH0PR03MB6300:EE_|SJ2PR03MB7330:EE_
x-ms-office365-filtering-correlation-id: 262cd07c-9907-4dce-ecc2-08dc271b2f90
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0
x-microsoft-antispam-message-info: TRtEPhi0dIX9wruoEBx1xwKBvjlfqTcJvpBFomMclcZxWqrAlseSOS1iipZE+q/gwiAjxN1JmaNPJS3U1Fc2y/yqSPmJiHxVvqrNXO+6l7DsbA/HaNwjZQAsM2/3dOUywMHK/1S08XbNU7AzWjFctu93ovUahIEDmPBTAeBavI+FTgTQe5rdebnM4v5QeEBUOV0mvbT4oALE5XRFmiatyxsABVQwUW/R63MqzTsQW3JayTvi1D4AfXx0nTePqiN0F2adObOW6E5+MM9KWIxl1ufecn1cUNlEvVL0ItWwlrMGhvQNF5OGHPeywvvhs8TEty36lLYO5hfQwQrC+dQD6FOdMn4iPEkO10WSn/EwHLAV2nGiwL9aycoa6q5Vw4P5bTJDWb3PeiulGJO7iqsDBOWPoY5pEzPVi6/++cgbiwXKiA0eibeoMfTzC0pfROjTDPgxxNgXEz/tNLNHScEuFCpW/NWDRMBMTewL9MFEDFJJFtRT7fMfzCu65gTj8PH5nSjlp90PVoJW7EuViywnUyseCbHqmhsS74ERUEs3QAW5eGectj2b/iMwRfOByESD70ucEqWDV1NjL46Wp6fRAL1dua7FHWhysUNL61DHJ38=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:PH0PR03MB6300.namprd03.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230031)(136003)(39860400002)(396003)(366004)(346002)(376002)(230922051799003)(451199024)(64100799003)(1800799012)(186009)(166002)(2906002)(83380400001)(38100700002)(122000001)(55016003)(66899024)(41300700001)(26005)(38070700009)(6916009)(66476007)(66946007)(64756008)(66446008)(66556008)(316002)(76116006)(52536014)(86362001)(450100002)(4326008)(8676002)(8936002)(9326002)(53546011)(7696005)(6506007)(9686003)(33656002)(2940100002)(71200400001)(5660300002)(478600001); DIR:OUT; SFP:1102
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: tXB+iy33IsLHR2MLvhRaQAZB19G7PeAcved2KA4ehOXHNEN6y1RzqcIs7lFNAJS4g6GdZYUBnnReBbRmmTBGgcD75P5o+hUetnITIPL8jyVf9PBWt9FPMJ4fleXESoLX3iir0rpsMOOINiobiQ1LqpYqZEukfSVNw1vsQ7DRq9tvx5qNL96AtlAYa5odAGnQGZNOrCBL8uiEDh/h49Qcbt9ZhY4Iv2842QVGXta8EDonMnCYvw9X+HbTpF9a7JU76nWB0OVNov/WZvT/x2Nc3c2onyVOi4Cy6KjENmvw5jcR3rvB/yWH6SNX4aU8uuI6aEPpqO/fhZfwnpXv/Eh/cFyE+xyEPLKleysVmVCATpKiiukcOOjJ6UbRnJhVPBop7YGcgEY7/nC//b6NLzsNqQAy2tT9E/CMEe8xYNukSazvzGGEVzrSBMGcvTVwSnpEewi0lCnvCcd5wU76Zqhj+RDSQCQYdBLPlRaIjrNY13IS0+PV+IAYfFHtub4swdkEdcEg1LiPUDeZFSdost3nk9U+c5lMwut/bBKT9To12bVZyELIaV8QrugtMvQxxa6q/NSdcYwsmkBY6EOU1f4U6bZIvYIUSWd3xS85zcOVWLKM26n13zC9KaSpV27+yX6VHP8nX3S/YsB6FTKT7NWhx7ONG1F508K7o4oEMByBoxG741nOkFkAnXlwhKKddUohC+Ahcp0sbMJGa5d4ecQA3IuqM8xzPYTzrdd43dpy2flQvM1jXavl9p+Hdr7LENXkzQSAK8FappXhlwusjTCraku1Eq5u/UJEBcm6DakdsKkbr3kblNDXOSnC1xA+l3nr2FvF9Qo+LyER+kIbEdLzRkh+ZqAn+kIip5XzicPtMLckE0vtTcBDf6sq3F57Ic7YWQqJtNKELr3rQDAQys/3aWml6SZ+g0pad3RQd56P18d6xlZqqNW2Jbyx0chuFbSU5KC8XQ98fDbXy8CV38f8KmbnCM15o4G3onh/gOXpgzInkHDbnmfuAtIii0pGLqUA0BKqLUpQUm18oRwkYT4QpFzS2P+vRDtAPPFFVb01TfOnW2AtR8DHp55u13mRmM2XSEqPniOgoTSxnXdn+wp67PjlEiN6hVOLfAt+XtzK3fgoMOuTAbzSLctTZBPjq7of0bxQlazdWLZgA+k0v7nUd6CkWVXuolBoH7nET+DELoj3DCbAY2sFO6mbM/hu99p6ziRcH5U3ku3ms7Z5JCxGqS1M3hYSe4tM5FL20UR9H9OUqRGVsxO8L42H0cxu6oKgbCPSIanDb8sob3uJaAZLXAH1ajDsTzAoaOvkR8PsjTVwT+eOm68xHVJVHjlSceJIM0Tj89sqY2+xzTtJ2iLlEYw5zmXiTLhA4n5I5xslL5mqO8Lv0Cqm25VkrfZSdYzFPzso9FhUmxCLmdUfyW0hWL0lurmHNfUEi3FwVGJott2/NRPd4HZEEV67aXrvw9Z35jX6R6j2Clq3pLEUF3rUr1j+dAvXHlcMZAmOv5xHQWIXkD8bLNHp/LdgLBZCkwnZh4xeMwjDj+ed3lLjr98JZdkxNWZasKFajWW/lvUZjyRRfoQ+xktbCqBIH7GKavk2
MIME-Version: 1.0
X-OriginatorOrg: rbbn.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PH0PR03MB6300.namprd03.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 262cd07c-9907-4dce-ecc2-08dc271b2f90
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Feb 2024 13:54:49.5033 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 29a671dc-ed7e-4a54-b1e5-8da1eb495dc3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: q4zCURxWxkXsnEweAWCwJfGTSrYZR4FeuoO2JGUdzUnDCJr1dsSLglWK+EBmSe13sAkoqvZ52+ljzIILhB/+8A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SJ2PR03MB7330
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: rbbn.com
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_PH0PR03MB63002AA6019CF145648592BDF6462PH0PR03MB6300namp_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/1hizRqeZMI5YRNygUMMSXxK6cKA>
Subject: Re: [bess] A couple of question about draft-ietf-bess-evpn-ac-aware-bundling
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, 06 Feb 2024 13:55:04 -0000

Hi,
Regarding my Q2:

I have encountered deployments in which an EVPN IRB is configured with multiple IP subnets while the single attachment circuit of the broadcast domain it uses is delimited by a single VLAN.

Regards,
Sasha

From: Alexander Vainshtein
Sent: Tuesday, February 6, 2024 3:51 PM
To: draft-ietf-bess-evpn-ac-aware-bundling@ietf.org
Cc: bess@ietf.org
Subject: A couple of question about draft-ietf-bess-evpn-ac-aware-bundling
Importance: High

Hi,
I have a couple of question about the AC-aware bundling draft<https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-ac-aware-bundling-04> .
The background for these questions is given below.


1.       Section 6.2 of RFC 7432<https://datatracker.ietf.org/doc/html/rfc7432#section-6.2> that defines VLAN Bundle Service Interface says that "MAC addresses MUST be unique across all VLANs for that EVI in order for this service to work" .

a.       This requirement is not limited to multihomed PEs

b.       No mechanisms for enforcement of this requirement (e.g., by detecting and handling of possible violations) are defined

c.       Any manipulation of VLAN tags is strictly prohibited with this service interface

2.       The draft in question defines a similar requirement and effectively provides a way to enforce it. However:

a.       Detection of misconfiguration is explicitly limited to just multihomed PEs (as can be seen from the title of Section 5)

b.       The draft does not impose any limitations on VLAN manipulation (this is expected in the case of inter-subnet traffic (with each subnet differentiated by a VLAN) within a single broadcast domain)

c.       The draft seems to deal just with the situation in which multiple subnets in the same broadcast domain are differentiated by VLANs.

And now my questions:

Q1: What is the rationale for restricting detection and handling of violation of the above-mentioned rule to just multi-homed PEs?
Q2: Does the draft support the situations in which multiple IP subnets in the same broadcast domain are NOT differentiated by different VLANs?
Q3: Is VLAN translation with AC-aware bundling service interface allowed for intra-subnet traffic that undergoes "pure Layer 2 switching" in the single broadcast domain?

Your feedback would be highly appreciated.

Regards, and lots of thanks in advance,
Sasha

Disclaimer

This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.