From nobody Thu Dec  1 03:17:34 2022
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 38326C14F74D;
 Thu,  1 Dec 2022 03:17:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level: 
X-Spam-Status: No, score=-2.095 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_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001,
 RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001, 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 (2048-bit key)
 header.d=rbbn.com header.b=b2jemSax;
 dkim=fail (1024-bit key)
 reason="fail (body has been altered)"
 header.d=sonusnetworks.onmicrosoft.com header.b=RMGOnag/
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 inaaGm2ZQIdy; Thu,  1 Dec 2022 03:17:28 -0800 (PST)
Received: from mail1.bemta32.messagelabs.com (mail1.bemta32.messagelabs.com
 [195.245.230.1])
 (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 0BC2CC14F747;
 Thu,  1 Dec 2022 03:17:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rbbn.com;
 s=rbbnselector03122020; t=1669893443; i=@rbbn.com;
 bh=8LMkLk/g2Ae0FWRy+ZD41LbuNBm+lrbIEYdnSCbtiuU=;
 h=From:To:CC:Subject:Date:Message-ID:Content-Type:MIME-Version;
 b=b2jemSaxce/gRVlCkZjjAN4PSQOIW0iC19loFytgxiSJyxbEe439iCYihgrYJquzl
 qMcGC8NyCSquwW5jE4475MUyKbuA3RLewchuvmWbXY6mivDHEomVG80+d82dZwoXFL
 pa3gE6lCZVvSjZd3un2iEO5zTDMfn9KfRgLY7D0DmpIfSJ60b4QjtuDk2/6r6Riamw
 QjjZMqpHJMtDyrIFDVP0gzB7mADjSvL8K6x6IZaKmStihOK8OBQmnZa0hGFgB6mgZM
 4doeMCPN8x/Ismd2Pm5l9lbb4saSYlSMZpBjy3bI3ngd4HLplAuxGtmppqaFw7nsjE
 i5uOqZ5E/r4sQ==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNJsWRWlGSWpSXmKPExsWSoe9lqOvU25F
 scLpNyGLF8ZnMFhuuH2dzYPJYsuQnUwBjFGtmXlJ+RQJrxslnBgXzfCquz5/E3sB41qWLkYuD
 UWAps0TTootMEM4iVomTa/6wQDirGCU65/9hBHFYBHYzSzR+XALmCAnMZZJYduAIE4Rzj1Hi8
 LaHbF2MnBxsAlYSv9+fYQGxRQSyJCb3TmcGKWIWWMgosXn5PkaQhLCAq8TrvU8ZIYq8JJ603Y
 Nq0JO4fK+RFcTmFBCQ+NU+CywuIcArMWXuSXYQm0VARaK5dwoziM0rECtxYcIksBpGATGJ76f
 WMIHYzALiEreezGeC6BWQWLLnPDOELSrx8vE/Voj6IonLD9cwQsRlJS7N74ay7SUedcPs9ZXo
 m/QAKi4nsar3IVRcXmLaovfsELaMxIMb29kg7D1sEicvS4M8LCGwnUViwfbXUM0GEvO+HWGDS
 GwQkOh6tpoZ4tI8ibsTNjNNYNSeheTwWUhSs8AeFZQ4OfMJC0RcR2LB7k9sELa2xLKFr5lh7D
 MHHjMhiy9gZF/FaFacWlSWWqRraKCXVJSZnlGSm5iZo5dYpZuol1qqW55aXKJrqJdYXqyXWly
 sV1yZm5yTopeXWrKJEZiyUopZ4ncwPlz2R+8QoyQHk5Iob3VnR7IQX1J+SmVGYnFGfFFpTmrx
 IUYZDg4lCV7LNqCcYFFqempFWmYOMH3CpCU4eJREeG1AWnmLCxJzizPTIVKnGL05rmzbu5eZ4
 8GJk0By5eErQHI3mLy2fsE+Zo5N+7oOMAux5OXnpUqJ81aAjBAAGZFRmge3AJYHLjHKSgnzMj
 IwMAjxFKQW5WaWoMq/YhTnYFQS5r0KMoUnM68E7o5XQCcyAZ0YKdYGcmJJIkJKqoGJwzN2f7z
 h0d6W/79Od2pNXdiaWcnp2XzrieqTyJZePokwLuajDnfeeoZNs2F5dZBbROLZ8uf/8i1/yZvH
 hu+efMFp8ftSl8iPP04rX9f7fXDe+1vbDrcKLJnsmjZfUeVHSsRHjYO6KR02Pza/rbpzQSVup
 0tCqd73acHhn/l+3y3N6Ll2U0QiQ3TeXc+s6M51umsXzQnTLLprof6NWZRdXUdydeK6J6+cDR
 b7Pz9j5nbygSrrC7Gg69fXl3lN2BiiKG8aH8I/4/z+7Ye23i+wqfnnqzk7RTxc9u4Bfy7L6K2
 xJ66WqtnpMmTVZ7BOdVSZeMZZYRr3DKHdhv/OGATFXnoVfu599WSv53vSYoqVWIozEg21mIuK
 EwEzEqZ8fgQAAA==
X-Env-Sender: Alexander.Vainshtein@rbbn.com
X-Msg-Ref: server-21.tower-587.messagelabs.com!1669893441!83140!1
X-Originating-IP: [104.47.74.49]
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 30914 invoked from network); 1 Dec 2022 11:17:22 -0000
Received: from mail-bn8nam04lp2049.outbound.protection.outlook.com (HELO
 NAM04-BN8-obe.outbound.protection.outlook.com) (104.47.74.49)
 by server-21.tower-587.messagelabs.com with ECDHE-RSA-AES256-GCM-SHA384
 encrypted SMTP; 1 Dec 2022 11:17:22 -0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
 b=eCEFMlh/nbl5QsT/AlihPUzvwg4JVke8eld4RT55Ex272JGDAOH7RRNs8ZnKhUpMosh8BC6nrdvZs3eM/OqNCLN+AvbXF/G4x3p8LgJOjnDfM/nyDo8m5G0xxdAEwOe+fLCXbNU2/V3XdMoco5DYK8jId08cIa7Pb3vlq1JeVZySyMzPRF3eIRAfGaHoxrpDM5QwRmKl8zY0tr/2Ql54i6eyPqicq4enCzfYXxIGV9029djkFNsNfBqsRwtP73ujG9zxzL4hI2UoZtn7u6yvJSDeS93rf14p1DqGwoZm6dPW9S+JhtAqPbD0XL1z6ICYvSwGB5hUn/Yc0JMy0n6Iww==
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=ichkLhrROOmS9Ot0HJ2dy1CdXwFmqkjXPEKOXM9sGGw=;
 b=jINBdvh+zTTe51XaPvCkpM7Kiu6iRgZAxjkCI+MWefyWjbojFJuGu5PRe5HAq0eSh895HptHk/W9Eo0WISEZ1UlA6ahtRfTwnQcMIa4iaJIFR9aq4G942+QIjOVizCGVdfQ9b+6/9kmTJHU3clwPJzquFnuhrvrXZWP7IxuWojGhjmoc2MWq3+hA5w32hOOyw6TRrA2jgqQY/i5lMPBC1JNBkt73jQLIJL5AR7K7HUW3b3reMM2Lgiq/60iot3XNeyAy2A7WLCew+V753cG5DzdyW9DgWzZ8ECxoVJFQIEijRux8fqIItAH/eKiZIUT46lF17+qkSNDDDJzIGFyTdw==
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=ichkLhrROOmS9Ot0HJ2dy1CdXwFmqkjXPEKOXM9sGGw=;
 b=RMGOnag/QJsDHTr2u7nMKK2FHieKuOkE/GWky6XdkHncN7Mn7pySIe1WLmE0zVlQbp4t6LXIYlah5V8WfLP/grZepg0+UrUftya7vOsDKSdtL0dho2moUyBocIOKmM69G6qgaOuXQv6smExBoorQ38kw1TkkQhK/39JXpCI17oY=
Received: from PH0PR03MB6300.namprd03.prod.outlook.com (2603:10b6:510:e2::5)
 by SJ0PR03MB6224.namprd03.prod.outlook.com (2603:10b6:a03:303::18) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5880.8; Thu, 1 Dec
 2022 11:17:18 +0000
Received: from PH0PR03MB6300.namprd03.prod.outlook.com
 ([fe80::de52:63cc:b8e0:a73d]) by PH0PR03MB6300.namprd03.prod.outlook.com
 ([fe80::de52:63cc:b8e0:a73d%7]) with mapi id 15.20.5857.023; Thu, 1 Dec 2022
 11:17:18 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@rbbn.com>
To: "draft-ietf-bess-evpn-l2gw-proto.authors@ietf.org"
 <draft-ietf-bess-evpn-l2gw-proto.authors@ietf.org>
CC: Nitsan Dolev <Nitsan.Dolev@rbbn.com>, Shell Nakash
 <Shell.Nakash@rbbn.com>, Alexander Ferdman <Alexander.Ferdman@rbbn.com>,
 "bess@ietf.org" <bess@ietf.org>
Thread-Topic: MAC Move events in EVPN Single Flow-Active Multi-Homing mode
Thread-Index: AdkFc6hj9jpb4yHSTmS5+9vcHnfr0Q==
Importance: high
X-Priority: 1
Date: Thu, 1 Dec 2022 11:17:18 +0000
Message-ID: <PH0PR03MB6300D10CA4C954FBB8ABB8B4F6149@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_|SJ0PR03MB6224:EE_
x-ms-office365-filtering-correlation-id: e594ae87-2adf-43c3-6788-08dad38d9bf7
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: HSSPMs4RpXUlzr2iqzI5abZe6bPdcHnWmtUyv1MZwTK5CH9X/jr2m+yNsyDGA2t2SGAUmB8gTKUkc46OtbYbzxu4E7a1q8cedzyOAfwLCiEcREfd27VFun/S7aExYWKyzN05PBNBd65UWj/4rrwDbajRwbVeNT1R0riwy3wrfdaKthNI+JBEnGpQaeQk+v/AsblHkdwSyMvpqZ5bmp0QlsrG0fiImoiSipwO5PC74tybv6YxelqwqrolSeXnSQp9YHU4uQeL+KyjaR5+W6Og7wGmh3ZauKBsJfY5U9xKw7Ib4+FhWJvSKQqZNT41NudXdjO49Y3wh2MlJ7E2fJqNOO0GwehJpfHw/6WCa6X/MbKkA//zEpYcPD8OUNrQ97lsZn95yRsAqhu1UydGWNGy5PhhihYMQBlQ4d/41VFoTyqfbn7mLMHUFDKQG+UiAwL+zDu0r6ucOx+wri5R1BfdIBMfsQ2gaHShILDeoIoD4MkSmC0k20R9ViNuB/44bq5QwvMXeYN3ZrtNDNHCursE7v4hvktyDyykwmv78VuXR3rMulARDO/1jqFXFPBjbGiMq1ShljpV70jiZ/WG6iQGO3KSBAgAda11Npk70pKa5MMA6ntQo/O/ENKKHFct+bPtOzaLh1O7tCW1WnnhOSgHmQ6gtm5UEkSorky2x7Qr6V/Ty0VAAgc3ii9arBEtqYYvzXMJbTLyIF7114zZ/S3fW713F0sykrL2u76HyVZosZ95qAOMHqQF2nlZwDxfPLv6XgXhVrKBWQodKAjipmGixg==
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)(39860400002)(136003)(346002)(396003)(376002)(366004)(451199015)(8676002)(4326008)(76116006)(450100002)(5660300002)(41300700001)(52536014)(2906002)(8936002)(66476007)(66946007)(66446008)(64756008)(66556008)(316002)(6916009)(54906003)(38100700002)(122000001)(478600001)(71200400001)(26005)(7696005)(6506007)(9686003)(33656002)(186003)(83380400001)(38070700005)(55016003)(166002)(86362001);
 DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?jIfReAhoJD7iz5hAHy2M5Au7rkahfUnBAZUI0CPq/ICi4IcGRk5Apbh9Y4HX?=
 =?us-ascii?Q?0YFRJsvN75Gn3EBLSNJVZVZDbGzksBQye/PY1tP0UJPWjM4c1qpe/0GN+t9J?=
 =?us-ascii?Q?vKylQSL3d6IPHIvnzXaoEaDH93VwJ6aHPiLhfpWoAQbKJxLoMmnUKwiXORh8?=
 =?us-ascii?Q?I5t+ldFQ3HBR9J2xSbw5ff6RsNxBr4yGxujmFrQcDeb+eiB0474JCDNrv5Xz?=
 =?us-ascii?Q?4Q0LjhRr/QmlhqG2FqjsnvaUlSGijMoIb0aMg3kMDRCgEEEH3VcyLb896npH?=
 =?us-ascii?Q?aMHX+tqIMn/zAcBithdxzOvGbmb6mAHqTHCSw4JM0usmVumGuA84lz5Ppl5F?=
 =?us-ascii?Q?mNgtcX3VwC7PrZVKdL5eXbHPO5tjSvw0ZwpeowQ1iKH2k4OzmLIeYy/fNKoS?=
 =?us-ascii?Q?lqt7m2N5Xa5tTNYby2yPq7bd37mfxINBH5rsvybffm9AnCRaMb4VFkKTdxe7?=
 =?us-ascii?Q?zWn70B00APXqDvccokkmLMSIX24l9F880EUbiBRwAPHbV+oKTV+hPfpMHTzE?=
 =?us-ascii?Q?qvQrC1WJXKhwg/lDUXS4FwFdV69l5aaPhi3MD26Otz0l8b7cDr2wd2KZmQI7?=
 =?us-ascii?Q?IBTj4imXTf2QQqiWzmsETCDy4ITfKGQe5SZHDlndxxVvkuCewQMZqPy0B0mX?=
 =?us-ascii?Q?FfwWjDEwadJK3LGZk7IKBhcbW3wnROwZ9nS7pGuNM+dwZzWVm2Tf2er0CI8o?=
 =?us-ascii?Q?qSajB4EPEd4jOBQwSoUylwT8A0xwiu/a0JrOg0N7MTMxtm9fHSarWt+zWE4+?=
 =?us-ascii?Q?bcYnEF+wKe8kszOOYNcvFxRYmELONzCa6F6T+8LYMj3Zv4ozFKjizojLv6XF?=
 =?us-ascii?Q?z4ErOztv0Xpprzt4SkH1JG0mx2xe/tXFJQmLiNUzMb22rGyVr/Ga3cSYnlwf?=
 =?us-ascii?Q?x2e7Itjy4kQwXoyaRCDM4s9ivxvw5EXRvDec2I2chxZ41NC24dkiDcLikFcJ?=
 =?us-ascii?Q?Z+KST4IO8heTzYDfIk3HkiXRoHwJoxLbYsraezi1fdS7kFX8dvGCWLaiVqpb?=
 =?us-ascii?Q?xytGYXYFEx67BmH6OWNdTNzHKpYHf7V2eE8KGcYNPtlf79rZrn/EhCTI0IHh?=
 =?us-ascii?Q?+3dDmVhJsdM80ovEPfjls59rlZ+y3yes8Vvnt14/5MRpsN31dpolS2mLMnsI?=
 =?us-ascii?Q?1/qCUrjfte3gCDnKxvzuZyY3ymUgZTGPJouRIyKCuzfnGNcLIYpiQosTGSpj?=
 =?us-ascii?Q?VmLadclQDT8Wf2vNxBOc3uDEBjGdbzOSbjQwmAt7CCSAua57WGOmPEssmmnj?=
 =?us-ascii?Q?lHZNWHwDsA+xiwK7Ss+OttQKHmiK4Bk8Lq6gJ5nOeMXQuLNAqjqNV/pUiadm?=
 =?us-ascii?Q?KgbrkSMuWC85ydMUAbHyupobtM1L8s6Ujhj8GJvaXhJhnzCq5JYszKhoBJQO?=
 =?us-ascii?Q?t1ZIyjGCyCcamgrpp2P9GJNKjpei7/YBZsS8r87jOuBld5Bt0QxFWG42v0FX?=
 =?us-ascii?Q?bbGCrltonpQSEwP5SaS9jdTy8bKZUzX/iF7/BpiZfGbFgwOapD4kkT2CVs7u?=
 =?us-ascii?Q?gQVbdn0oYcT5RpTRVVXXKAzWwcJ329KqXDD34Mn3AFMtH+657msak/ExOuNF?=
 =?us-ascii?Q?vLbClU+ee6va8niYpO0HeeglIO9DQbebByv/Y7fq?=
Content-Type: multipart/alternative;
 boundary="_000_PH0PR03MB6300D10CA4C954FBB8ABB8B4F6149PH0PR03MB6300namp_"
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: e594ae87-2adf-43c3-6788-08dad38d9bf7
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Dec 2022 11:17:18.6253 (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: CPimuDSQHBaIc2wADwGJS8rLF5GDfaQ/aHdrhpp0v9TiPWnrd2u3jcJhkzl8VbI0gxKueaZDTad+ZTeZanQ9fg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SJ0PR03MB6224
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/A5dXoJFZrTTu1r8MZ51BTGT1Gl4>
Subject: [bess] MAC Move events in EVPN Single Flow-Active Multi-Homing mode
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: Thu, 01 Dec 2022 11:17:33 -0000

--_000_PH0PR03MB6300D10CA4C954FBB8ABB8B4F6149PH0PR03MB6300namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,
I have a question about handling of MAC Move events in EVPN Single Flow-Ac=
tive (SFA) multi-homing.

Section 15 of RFC 7432<https://www.rfc-editor.org/rfc/rfc7432.html#section=
-15> defines MAC Move events as following (the relevant text is highlighte=
d):

   It is possible for a given host or end-station (as defined by its MAC
   address) to move from one Ethernet segment to another; this is
   referred to as 'MAC Mobility' or 'MAC move', and it is different from
   the multihoming situation in which a given MAC address is reachable
   via multiple PEs for the same Ethernet segment.


With SFA multi-homing, at any given moment each specific customer MAC addr=
ess is reachable via just one of the multiple PEs for the same Ethernet se=
gment.
And indeed,  Section 5 of the SFA draft<https://datatracker.ietf.org/doc/h=
tml/draft-ietf-bess-evpn-l2gw-proto-02#section-5> states:


   When a host moves to PE2 from the PE1 L2GW peer, the MAC mobility

   sequence number is incremented to signal to remote peers that a

   'move' has occurred and the routing tables must be updated to PE2.

PE2 and PE1 in Figure 1 in the draft are attached to the same MH ES in SFA=
 mode, therefore my reading of the quoted text above is that, with SFA mul=
ti-homing, MAC Move events are recognized and advertised as such even when=
 a given host moves between two PEs attached to the same MH ES.

However, the quoted text appears in only in Section 5 "Inter-Subnet Forwar=
ding" of the draft, and this section contains multiple references to RFC 9=
135.
Therefore, it is not clear to me whether the same rule is applicable to th=
e scenarios in which SFA multi-homing should be applicable for intra-subne=
t forwarding scenarios.
My guess (FWIW) that it should be equally applicable, but an explicit clar=
ification 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, dis=
closure, 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.
--_000_PH0PR03MB6300D10CA4C954FBB8ABB8B4F6149PH0PR03MB6300namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-mic=
rosoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"ht=
tp://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii=
">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
=09{font-family:"Cambria Math";
=09panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
=09{font-family:Calibri;
=09panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
=09{margin:0cm;
=09text-align:right;
=09direction:rtl;
=09unicode-bidi:embed;
=09font-size:11.0pt;
=09font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
=09{mso-style-priority:99;
=09color:#0563C1;
=09text-decoration:underline;}
pre
=09{mso-style-priority:99;
=09mso-style-link:"HTML Preformatted Char";
=09margin:0cm;
=09margin-bottom:.0001pt;
=09font-size:10.0pt;
=09font-family:"Courier New";}
span.EmailStyle17
=09{mso-style-type:personal-compose;
=09font-family:"Calibri",sans-serif;
=09color:windowtext;}
span.HTMLPreformattedChar
=09{mso-style-name:"HTML Preformatted Char";
=09mso-style-priority:99;
=09mso-style-link:"HTML Preformatted";
=09font-family:"Courier New";}
.MsoChpDefault
=09{mso-style-type:export-only;
=09font-family:"Calibri",sans-serif;}
@page WordSection1
=09{size:612.0pt 792.0pt;
=09margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
=09{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72" style=3D"word-wrap=
:break-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed">Hi all,<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed">I have a question about handling of MAC Move events in EVPN Single=
 Flow-Active (SFA) multi-homing.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><a href=3D"https://www.rfc-editor.org/rfc/rfc7432.html#section-15"=
>Section 15 of RFC 7432</a> defines MAC Move events as following (the rele=
vant text is
<span style=3D"background:yellow;mso-highlight:yellow">highlighted</span>)=
:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">&nbsp;&nbsp; It is possible for a given host or end-station=
 (as defined by its MAC<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">&nbsp;&nbsp; address)=20to move from one Ethernet segment t=
o another; this is<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">&nbsp;&nbsp; referred to as 'MAC Mobility' or 'MAC move', a=
nd
<span style=3D"background:yellow;mso-highlight:yellow">it is different fro=
m</span><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">&nbsp;&nbsp;
<span style=3D"background:yellow;mso-highlight:yellow">the multihoming sit=
uation in which a given MAC address is reachable</span><o:p></o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">&nbsp;&nbsp;
<span style=3D"background:yellow;mso-highlight:yellow">via multiple PEs fo=
r the same Ethernet segment</span>.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed">With SFA multi-homing, at any given moment each specific customer =
MAC address is reachable via just one of the multiple PEs for the same Eth=
ernet segment.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed">And indeed, &nbsp;<a href=3D"https://datatracker.ietf.org/doc/html=
/draft-ietf-bess-evpn-l2gw-proto-02#section-5">Section 5 of the SFA draft<=
/a> states:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><o:p>&nbsp;</o:p></p>
<pre><span style=3D"color:black">&nbsp;&nbsp; When a host moves to=20PE2 f=
rom the PE1 L2GW peer, the MAC mobility<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; sequence number is increment=
ed to signal to remote peers that a<o:p></o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp; 'move' has occurred and the =
routing tables must be updated to PE2.<o:p></o:p></span></pre>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed">PE2 and PE1 in Figure 1 in the draft are attached to the same MH E=
S in SFA mode, therefore my reading of the quoted text above is that, with=
 SFA multi-homing,
<b><i>MAC Move events are recognized and advertised as such even when a gi=
ven host moves between two PEs attached to the same MH ES</i></b>. &nbsp;<=
o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed">However,=20the quoted text appears in only in Section 5 &quot;Inte=
r-Subnet Forwarding&quot; of the draft, and this section contains multiple=
 references to RFC 9135.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed">Therefore, it is not clear to me whether the same rule is applicab=
le to the scenarios in which SFA multi-homing should be applicable for int=
ra-subnet forwarding scenarios.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed">My guess (FWIW) that it should be equally applicable, but an expli=
cit clarification would be highly appreciated.<o:p></o:p></p>
<p class=3D"MsoNormal" dir=3D"RTL"><span dir=3D"LTR"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed">Regards, and lots of thanks in advance,<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:left;direction:ltr;unicode-bidi=
:embed">Sasha<o:p></o:p></p>
<p class=3D"MsoNormal" dir=3D"RTL"><span dir=3D"LTR"><o:p>&nbsp;</o:p></sp=
an></p>
</div>
<br clear=3D"both">
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, dis=
closure, 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.<BR>
</body>
</html>

--_000_PH0PR03MB6300D10CA4C954FBB8ABB8B4F6149PH0PR03MB6300namp_--

