Re: [bess] A question pertaining to validation of LSP Ping Echo requests in draft-ietf-bess-evpn-lsp-ping-08

Alexander Vainshtein <Alexander.Vainshtein@rbbn.com> Mon, 21 November 2022 11:04 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 DC950C1524BB; Mon, 21 Nov 2022 03:04:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 (2048-bit key) header.d=rbbn.com header.b=ASvL4RHL; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=sonusnetworks.onmicrosoft.com header.b=oLVyg1vc
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 dR3khg3tv9Nm; Mon, 21 Nov 2022 03:04:34 -0800 (PST)
Received: from mail1.bemta34.messagelabs.com (mail1.bemta34.messagelabs.com [195.245.231.2]) (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 66484C1524AF; Mon, 21 Nov 2022 03:04:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rbbn.com; s=rbbnselector03122020; t=1669028671; i=@rbbn.com; bh=SqdR/Vw2KsySdhHmrhu1SbIVb/3eUs+LgZrtQNt60Cs=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=ASvL4RHLwPGsWZdWVTVOg5QIwgAwi0a9TmckCgB3EUD+Uyoz3phPskeZ2FQWYuVQo y7Ff0mC7IG3Ph1BKgU0Q+5YrC7Vt0gmjP3vOUueDughv5oQ3XCAkn9EPf7CxwVsH7W sEHVw5opK06tGgFQapJuCgw8ecIR2TthB6EH0mv0R16UyAZxQw5ibVwM6s03021LoY BwMHWcu1FvvLoxJSRIqWHvsNqnPj61cSIZvKZqe5bFZBMvAVqMOJFhAE9BEo9sMd1z hb9yE1iSWyLDHBm8qHafNdXAPMQNMo4JAWMxmup7TOneedUOR3WVbOGOP0JadPROxj 7fSOCJWNeIovw==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOJsWRWlGSWpSXmKPExsWSoW+xUtcuujr Z4McFWYsVx2cyW3yb3cnkwOSxZMlPpgDGKNbMvKT8igTWjC3nW5kLHhxjrLhw8wRjA+OzTYxd jFwcjAJLmSXWvz3GCuEsYpXYPnsFO4SzilGic/4fsDIWgd3MEje+HGAGcYQE5jFJnP1/mB3Cu c8o8ffLDiCHk4NNwEri9/szLCC2iECYxIuzT5lAipgFTjJK7F1/gQkkISyQL3HnfQsrRFGBxK Smc0wQtpHEulONYHFOAQGJX+2zwAZJCPBKTJl7EmwBi4CqxJ1lJ9hAbF6BWInpezaD2UJA9qM dzxgheuMknrW+YQaxGQXEJL6fWgM2n1lAXOLWk/lMEDMFJJbsOc8MYYtKvHz8jxWivkji8sM1 jBBxWYlL87uhbHuJ7vvPgXo5gGxfiYdHdCDCchKreh9CnSkvMW3Re3YIW0biwY3tbCC/Swj8Y ZWY8OgBM4RzjUXi8a7JUB0GEvO+HWGbwKg7C8l9EHaexOltM8FsXgFBiZMzn7BAxPUl9kw8BW VrSyxb+JoZwtaTuLfjLyuy+AJG9lWMZsWpRWWpRbqGBnpJRZnpGSW5iZk5eolVuol6qaW65an FJbpGeonlxXqpxcV6xZW5yTkpenmpJZsYgWkrpVilbwfj22V/9A4xSnIwKYnyaglWJwvxJeWn VGYkFmfEF5XmpBYfYpTh4FCS4HUJB8oJFqWmp1akZeYAUyhMWoKDR0mEtx8kzVtckJhbnJkOk TrF6MpxZdvevcwcKw9fAZK7weTU2f/2M3Ns2td1gFmIJS8/L1VKnPePN1CzAEhzRmke3GhY+r /EKCslzMvIwMAgxFOQWpSbWYIq/4pRnINRSZg3JhBoCk9mXgncBa+AjmMCOk7NogrkuJJEhJR UA5P/w3eOMXUt/5w3VbQHnFn4gT9F7YSxTkdQ63v+FRnbPtZ7LnCpNm/r9rXg7M34//SVY+m3 QzWP7jGHfFWeZmhlsbZzy+a+wLVPfxdxR+5+xvkxQYSf4X3ga+/o01qLGDI+/w/23DKrOm9h0 ItXiT9vFT2N+nO2KES43zXZOc35zPHlWtY2lu7fRZOvn2Wwlz2iVT0n06Qta+mv35EdIfeDV0 x0mbahudh/Tjq/pfim679t5E8XRbPNWCpUtGJFItuE7QLfOS9OPOSeV59kkJeitqO1Q79A593 dNPb15y5/fiXzjcd37Zuvya6R/N+3tIc5bfY+8iToTEHbW89/E++XNoscunQmP/OSuGKruRJL cUaioRZzUXEiALTErVd6BAAA
X-Env-Sender: Alexander.Vainshtein@rbbn.com
X-Msg-Ref: server-3.tower-548.messagelabs.com!1669028669!190857!1
X-Originating-IP: [104.47.56.169]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.101.1; banners=rbbn.com,-,-
X-VirusChecked: Checked
Received: (qmail 24292 invoked from network); 21 Nov 2022 11:04:30 -0000
Received: from mail-co1nam11lp2169.outbound.protection.outlook.com (HELO NAM11-CO1-obe.outbound.protection.outlook.com) (104.47.56.169) by server-3.tower-548.messagelabs.com with ECDHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 21 Nov 2022 11:04:30 -0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=b81qJvNEJnn0JxRG7jwA1YpfUwucIlqDa4N8udk8b17joxbIEGQk20fTm1wU8MLPC3GF1lcAhK5lz36ak8IlWB27JJiBEcN7ZC2ay4WMZz+8Idj0snFIbz3XRxfWcHsPNZVoOe7NBbHXkVxtCbFBdZOCOmMejy5GGzvu88IfkoofFP0z/CC3DoZ0Yc1Ag03PqKL/fBAoRwUlRM6auZ8z/AxW1h6c8S1+GVsEoMCfBkH++QbUJOPZk7UZZB6lbee0SsPR+WPgqA5vrCTp4Ru10ALzASuJvN7ZPL3oG+6L3eUeAqJt/br1K5bPrSHxjq7u9vFWlJnqyFYT4Xnl4anoGg==
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=Gfss6KpeLdUicW0exhsIMTbkUWChmDD/0JAc3vU5Sjc=; b=nsiN1KxKvEHNc3xKI0v3rDL58sFnTNymwcBLpyUCqsIWnry9FKSsrjdRYFsY7+Gqh295dGJ6YwFJVaNB63bp3Qxywkx49npmRTTxl4fb28bK58CqEoOEzTZq3S0onqY/0GQSxHYZHiDBjpEszcjcX+7pxDRy+iuLoplupO6isWbggznxNRvJjxHFhy24tmUZlF8pz1sksu52yKN/9IZqWwanGJpcGBTEA2DUiG0fj8/6bwwZuOgbthm+qR5K6663ZraQgXjvMhjUuRi+9rtgVSa11jjrPshmYS1ELL+ch5rZm6gzEctDFyZIByZtUmLXrtt8udIsYEroaa4qcaQ3XA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=rbbn.com; dmarc=pass action=none header.from=rbbn.com; dkim=pass header.d=rbbn.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=SonusNetworks.onmicrosoft.com; s=selector2-SonusNetworks-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Gfss6KpeLdUicW0exhsIMTbkUWChmDD/0JAc3vU5Sjc=; b=oLVyg1vcwoLQ+UpCOINUvXYDjwMXYuiRf3YWfDMIYQIYXVmGk8GrNKn/MDCG3V1UlbBYmFjfMcqg00q6WHK1k3e7/sd+vTJzqSE6SZzS3yCq/lzqqcTUJJUMZr+SvW1HhxYnVdRXN/QsXxHenv4JEGb0AsIihlyxzCba5HnNK3Q=
Received: from PH0PR03MB6300.namprd03.prod.outlook.com (2603:10b6:510:e2::5) by SJ0PR03MB5614.namprd03.prod.outlook.com (2603:10b6:a03:282::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5834.9; Mon, 21 Nov 2022 11:04:24 +0000
Received: from PH0PR03MB6300.namprd03.prod.outlook.com ([fe80::de52:63cc:b8e0:a73d]) by PH0PR03MB6300.namprd03.prod.outlook.com ([fe80::de52:63cc:b8e0:a73d%5]) with mapi id 15.20.5834.015; Mon, 21 Nov 2022 11:04:23 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@rbbn.com>
To: "draft-ietf-bess-evpn-lsp-ping@ietf.org" <draft-ietf-bess-evpn-lsp-ping@ietf.org>
CC: "bess@ietf.org" <bess@ietf.org>, Alexander Ferdman <Alexander.Ferdman@rbbn.com>, Dmitry Valdman <Dmitry.Valdman@rbbn.com>, Ron Sdayoor <Ron.Sdayoor@rbbn.com>, Nitsan Dolev <Nitsan.Dolev@rbbn.com>
Thread-Topic: A question pertaining to validation of LSP Ping Echo requests in draft-ietf-bess-evpn-lsp-ping-08
Thread-Index: Adj4B7V9mca+IcmXRqmUVALIYzDlkgFjpkIQ
Importance: high
X-Priority: 1
Date: Mon, 21 Nov 2022 11:04:23 +0000
Message-ID: <PH0PR03MB6300E956726E0F5E599CB0FAF60A9@PH0PR03MB6300.namprd03.prod.outlook.com>
References: <PH0PR03MB6300CA076A6687E06E3D010DF6059@PH0PR03MB6300.namprd03.prod.outlook.com>
In-Reply-To: <PH0PR03MB6300CA076A6687E06E3D010DF6059@PH0PR03MB6300.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: PH0PR03MB6300:EE_|SJ0PR03MB5614:EE_
x-ms-office365-filtering-correlation-id: c870668f-bb1b-489b-bb77-08dacbb025ff
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: pdsmSxNQNKf05W1pqWsCVqilvrW6pmWnpbWyzkw3ewPFiSXXKx+5klY9/UxfR07FvY3k3fCanp1de65sI3FQtxhzAKQYDdB5GacJRgdUTZ9xQKGwx20w3IICjcE/UBZxdpyS0ubSzDumsYG9Y0KWaa/S3nWcclsGuzIgKBgGYMsl064bROQGSsIS6vCsiyeFwfPyAXaoPHepAzQ96KlwCzn21vwW83YgjuTfIA3dNRwaAlDqQD+CwTpqoitEhBHhPZ7VcqH1szKzXsTBD2N5JV9K7G65gfJ8zz+8a6p5KNMcnBGd7Qz25lb5VRcXni0H+w2/79Z65tvUxGYKvsKvJDPEoh96w2yGCb9MItTK/3gxHiNI7k27uTTCQ0jQqtbt1bclUOI2wlGBMhWtLI5KUOzFod7pK+zriPHiMTAQgsADVEUydyXIKYvPJWjNrgyV2SsIrDB+1oVT9IqMZPMXz/san72DvxF/YR5iTfKFYRsg0PL9GiAw/4v8qDV8Eeow3ZZ2Qchekrhtitu3SU3kAgmjAz50F10DfyvbT5bDcdgp2TbsYwpUwZPIQtvNRSXMuEaifOsT8JInFI251pUPLaDnd/skIFD2DNS1tTuqQ8VwG/YgflxjeK7InJROBJivnUMxNrYT2bKOXWxLaCAQ41gsUO2xnKDdIXaC/ixxWKcE0axP1jEt8tG31vq1PDQAF47rb0sezquBqcYM7UqFeQ==
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:(13230022)(396003)(366004)(39860400002)(346002)(376002)(136003)(451199015)(66946007)(316002)(6916009)(71200400001)(478600001)(8676002)(5660300002)(41300700001)(52536014)(450100002)(66446008)(76116006)(8936002)(66556008)(64756008)(4326008)(54906003)(66476007)(55016003)(2906002)(38070700005)(86362001)(66899015)(166002)(33656002)(26005)(9686003)(83380400001)(53546011)(186003)(7696005)(6506007)(38100700002)(107886003)(122000001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: z2eFIROhK6g/dJfUQ7QOVJX6QUjtn70m1a2Lu08ZkBBmlClIfqcGUHz6TM6zwFgrjb0lRZcom41yNiJpSGyeqpgBpP48912zoTT0mIJET3sndUwY6/Im+J2VQ4+Bu38KyKI1phtiWOyRMujx2hiUhT7mJ59iUK9+wl6nNuxAiwNJaKoTbi3bxPGqBHuEoxWKgapbqH9YOavpiQbBD1ORTm62N7ngPmMYk405XUtn4GYA/qhS7KwK1uPjtllClnxQqvRjsG8ABQyqY7rjCgwXKlsIMbDb+w9yTDwRr8+J6TagCuqumvyccGQuwJ7tITdS4EAcpfgdxqQIiG/pQLU+39FxzdVrE2LdBOanixB7jO6kfOclXJnIDCBY26kF0I8S7Vv1t7W47IamUClQ7NNgHPG342y66ENTPD/yl8c3bXQ9Aw885kMUs/vGxJWb79R98uAU+peSM2j8ZAkLd+N3p9oJcyGBT7V04KIuyy1HDhVLpE83Qzag9wKkjjU3ffNl/TUkFTYuYjWxl+tgXmKqGlzAxQh9LKr+xmmbNmvJqzV2v2tHCUsjdyyYFdpdrQYnK4WvWNsBJwYuZS2jHtr9syLxG7qpeT4MlqJxnF+JEc8MMBP0AfEG5nHDUP7MvnDAALjrUcepQzbhR6CV8v8/mIzelUH7WFlhT1gSMNsrfStPPXi6F35z6dlGFxYGb0lZFTeTF0ymHdLaLJBXQ3rCpv+QoMsnZdPVOtOhCzJmFzVyuylic7yyszZ22VM8LnMLRhjZhcJeX8dd5DkkDf9/TnZn8avCFxHwVEOYxATNSy/FASW4XFxD5WVU7wSyV9R83UA6xKhtiEypchsbmdHOYHmUr2Bbho+1Wgl5QqpvNZuOHXE4uEvwYcAThRg1qXdHCzXXzW0dm00QqM7VQ59TCcAM+vnduVhE8DtzUSM9GKGcvyrHUwBNx328hNNRes4DjHnle1ZXnPxcNygAIrxDjDT6FG6UVXUaaZqqA/TX82wZ9tfbuxSmtBI4lPO0iWGIRiMCIbDH7U8Shklwl47TjNdgsZYXdsM15Rp1J359ul6tr4tx5xOgxXxdscCmblsHicNr81cNg+/q0szP/1UPZW7yjSeNum9iaf8x0L1spPh+GWDV1IWZtKZrbGctQoNFsEBOawNjtQx+Vr8olCRE8ISEunc+v29cR6VKUqJ79y6b2V470cxyZ7LF55Xu8+mcAYz9n1tam6fLTnmIu2Sa5AaIkZ+gl20AatBhWxmaqPFF7wXqhj1sx/DIHoAJ2GmFcUKlAwig29QBDstk31l+5HuFmwY0O0Osd99YvbuA8g8YeH9YCVr/DRbQEzXbe8C5ciL4ffLLqdZ8vJR5KNGVmjyFyl4wvRD4PYhiXsXHfdPeGBZEKkIecojL/T+Yr4PzJ9gFfIPZEs8bXquFbYn09wfwtHDsjHd7BXxBvhMr52rBNv/wm+yIxJm21WWJgYtIukDXp6GXTdeSwLBa21r4oTXJAZRi3do2GMLjS/ypvZJd+OMQ7dG3G63tbmSS6HNh2VDIHKxeCu6WvEcN6MzrGpsEkhMWnjbtNU/AlIpGwWQ/UGFABdgD/n5IVhw4R0QF
Content-Type: multipart/alternative; boundary="_000_PH0PR03MB6300E956726E0F5E599CB0FAF60A9PH0PR03MB6300namp_"
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: c870668f-bb1b-489b-bb77-08dacbb025ff
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Nov 2022 11:04:23.8233 (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: S7IPjiJqoAuSNTkt0ZoEyWG9XuPiGgkCUIhndFycA/w9hXuWCnSX0oyjDOnwqwczc2H0e9kyG+Zwc7ZSvMgQMQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SJ0PR03MB5614
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/YTbNJ_SmvB9coT8v0g-NT7FcbeE>
Subject: Re: [bess] A question pertaining to validation of LSP Ping Echo requests in draft-ietf-bess-evpn-lsp-ping-08
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: Mon, 21 Nov 2022 11:04:38 -0000

Hi all,
I would like to add one more question (#5 - highlighted) to the previous list.

Your timely feedback would be highly appreciated.

Regards, and lots of thanks in advance,
Sasha

From: Alexander Vainshtein
Sent: Monday, November 14, 2022 11:36 AM
To: draft-ietf-bess-evpn-lsp-ping@ietf.org
Cc: bess@ietf.org; Alexander Ferdman <Alexander.Ferdman@rbbn.com>; Dmitry Valdman <Dmitry.Valdman@rbbn.com>; Ron Sdayoor <Ron.Sdayoor@rbbn.com>; Nitsan Dolev <Nitsan.Dolev@rbbn.com>
Subject: A question pertaining to validation of LSP Ping Echo requests in draft-ietf-bess-evpn-lsp-ping-08
Importance: High

Hi all,
My colleagues and I have a question about the validation rules for LSP Ping Echo Requests associated with EVPN Type 2 routes in draft-ietf-bess-evpn-lsp-ping-08<https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-lsp-ping-08>.

The problematic text in Section 4.1 of the draft says:

   The LSP Echo Request is sent using the EVPN MPLS label(s) associated
   with the MAC/IP Advertisement route announced by a remote PE and the
   MPLS transport label(s) to reach the remote PE.  When remote PE
   processes the received LSP Echo Request packet, the remote PE
   validates the MAC state if the MAC/IP Sub-TLV contains only MAC
   address.  If the MAC/IP Sub-TLV contains both MAC and IP address, the
   PE validates the ARP/ND state.

Here are our questions:

1.       Suppose that some MAC address:

a.       Has been learned by the intended egress PE from the Data Plane from an All-Active MH ES and advertised in a MAC-only route EVPN Type 2 route

b.       An EVPN Type 2 route for some IP→MAC pair with the same MAC address has been advertised by another PE attached to the same All-Active MH ES

c.       An LSP Ping Echo request with the IP→MAC pair in question and the label that has been advertised by the intended egress PE in the Label1 field of an EVPN Type 2 route for the MAC address in question is received
What is the expected result of the validation taking into account that the egress PE has not ever advertised an EVPN Type 2 route for the IP→MAC pair in question?

2.       Suppose that:

a.       Some MAC address as been learned by the egress PE only via the control plane (ARP/ND) and advertised In an EVPN Type 2 route for an IP→MAC pair

b.       A MAC-only LSP Ping request for the MAC address in question with the label advertised in the Label1 field of the EVPN Type 2 route for an IP→MAC pair in question has been received
What is the expected result of the validation taking into account that the egress PE has not advertised any MAC-only routes for the MAC address in question?

3.       Suppose that:

a.       We are dealing with a BD that is used by a Symmetric EVPN IRB

b.       Some MAC address as been learned by the egress PE only via the control plane (ARP/ND)  and has been advertised In an EVPN Type 2 route for an IP→MAC pair with Label2 field present

c.       A MAC-only LSP Ping request for the MAC address in question with the label advertised in the Label2field of the EVPN Type 2 route for an IP→MAC pair in question has been received
What is the expected result of the validation?

4.       Same as #3 above, but the LSP Ping request is for the IP→MAC pair in question and with the label advertised in the Label2 field of the EVPN Type 2 route for an IP→MAC pair in question?

  1.  RFC 8214<https://tools.ietf.org/html/rfc8214> defines usage of per EVI EVPN A-D (Type 1) routes in EVPN-VPWS in addition to their usage for aliasing/backup path defined in RFC 7432.  Suppose that the operator tries to perform a connectivity check to the aliasing function of some EVI but the PE that receives an LSP Ping Echo request with the EVPN Ethernet AD sub-TLV in the target label stack and label has advertised this FEC and label for a specific Attachment Circuit of an EVPN-VPWS instance. Is there any way it can indicate in the Echo Reply message that the label matches the target FEC but this FEC and label are used for EVPN-VPWS and not for aliasing?

>From my POV the simplest way to answer all these questions would be to say that the information and the label in the LSP Ping Echo request should be validated vs. the set of EVPN Type 2 routes advertised by the egress PE and succeed (yielding return code 3) only in the case of an exact match. Scenarios described in #1, #2 and #3 above could be treated as partial matches and yielding some new return codes while scenario 4 would be treated as success.

Your timely feedback would be highly appreciated.

Regards, and lots of thanks in advance,
Sasha


Notice: 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.