Re: [bess] MAC Move events in EVPN Single Flow-Active Multi-Homing mode

Luc André Burdet <laburdet.ietf@gmail.com> Fri, 02 December 2022 04:20 UTC

Return-Path: <laburdet.ietf@gmail.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 816C2C1522A9; Thu, 1 Dec 2022 20:20:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=gmail.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 Z3TIEtySjOeo; Thu, 1 Dec 2022 20:20:31 -0800 (PST)
Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 CCFE4C14F731; Thu, 1 Dec 2022 20:20:31 -0800 (PST)
Received: by mail-io1-xd30.google.com with SMTP id q79so1397060iod.4; Thu, 01 Dec 2022 20:20:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:content-language:accept-language:in-reply-to :references:message-id:date:thread-index:thread-topic:subject:cc:to :from:from:to:cc:subject:date:message-id:reply-to; bh=mLipmzkEjdenXqsqfRehw6muqNldFTShH7EYRDNOEbE=; b=iOxtIHOCC20bQGefrXlEq8SV3OF1eS9H+tv5feLeoB1M6DGi4do2aW6I2PYrZLRWz5 9cGGBhoSkrw4AjEm9oitALh70CukUdPOgr25o9IUHtwWQKsIo71NtaxYDpiiSgzCzwMZ GoRGOLcRxHoofYVM8q0t9IZXKzKYsOrZy6HNdRRJMgHBV8SViSRaJBsOBuTdXyS6y/4f DtHKrI6KLeR+wIgiM85ZwyMdb7Wx/p2KAvIZPmIZHicNBnoFgr767tO2RJ6JWNXFcmdx HCGPFPnPuFUONwaJs/0dkjP88oMB/bzWegtXVvbfmPxBy4PSb5Tn8uwyplH0HqqWVkVV /EGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:content-language:accept-language:in-reply-to :references:message-id:date:thread-index:thread-topic:subject:cc:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mLipmzkEjdenXqsqfRehw6muqNldFTShH7EYRDNOEbE=; b=q0HPFG6HRspWqDdSAy3SRwAW329R0xsYmm3X0D/7fAfAiQiezWXWN/UKkcLBODjHFr aRRpQckwaBqnUeDYlFaX16T4D4jFPnfRi3iWFD3wqsneQy/4aL+4xDjDspS1yEtEuYO+ uccYlzEskNHoGUnsqI7m19+MMvcZFGYMXHO7cAgZoyPc0b4R5qLiXyXODq2Bbjn+wPQy s+DP0EGmi/PqHazxG73pikfQ0t0ZelMmUnaKFdCft1KW+XYiS+Ha/B/3ndArUVpRwxif P0iDk5zUWnJGNDKSpfXK1P8uXka3GTf8eccavIMi68zpbldsozVpJWLhw+3VCWurOCnR fZxw==
X-Gm-Message-State: ANoB5pkYqvDerT5hiX0d67nmaE1YWpPikReYsYC+eFTjiTjIPLeBRjte Bnqh1/MFqucx8ynyd0Ay+QfNlWcguqk=
X-Google-Smtp-Source: AA0mqf5bylo+RljU8Tjpu1Tq2WH7bBDh8h3vEBomkV3uGidh020owtUi0ftZIVHudptH4GRidJ5v1Q==
X-Received: by 2002:a02:864e:0:b0:374:25b8:6fb with SMTP id e72-20020a02864e000000b0037425b806fbmr33564404jai.28.1669954830914; Thu, 01 Dec 2022 20:20:30 -0800 (PST)
Received: from DM8P221MB0454.NAMP221.PROD.OUTLOOK.COM ([2603:1036:301:2847::5]) by smtp.gmail.com with ESMTPSA id v3-20020a056602058300b006dfe3511ee0sm858712iox.24.2022.12.01.20.20.30 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Dec 2022 20:20:30 -0800 (PST)
From: Luc André Burdet <laburdet.ietf@gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@rbbn.com>, "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+9vcHnfr0QAkYrMn
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Fri, 02 Dec 2022 04:20:29 +0000
Message-ID: <DM8P221MB045468914B2F674E3EBA90BBAF179@DM8P221MB0454.NAMP221.PROD.OUTLOOK.COM>
References: <PH0PR03MB6300D10CA4C954FBB8ABB8B4F6149@PH0PR03MB6300.namprd03.prod.outlook.com>
In-Reply-To: <PH0PR03MB6300D10CA4C954FBB8ABB8B4F6149@PH0PR03MB6300.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-CA
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_DM8P221MB045468914B2F674E3EBA90BBAF179DM8P221MB0454NAMP_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/rSIyCuE5rmjDPxlGU4QNH5mGKN4>
Subject: Re: [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: Fri, 02 Dec 2022 04:20:35 -0000

Hi Sasha,
Thanks for noticing... I think you are right.
In the sections above, the negative scenario mentions incrementing MAC & MAC-IP when it **doesn’t** move but I will uopdate the text somewhere to reflect the procedure you highlight below is MAC and MAC-IP both when the MAC moves also to other SFA PE.

Will include an update in next up-rev

Regards,
Luc André

Luc André Burdet |  Cisco  |  laburdet.ietf@gmail.com  |  Tel: +1 613 254 4814


From: BESS <bess-bounces@ietf.org> on behalf of Alexander Vainshtein <Alexander.Vainshtein@rbbn.com>
Date: Thursday, December 1, 2022 at 06:17
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>
Subject: [bess] MAC Move events in EVPN Single Flow-Active Multi-Homing mode
Hi all,
I have a question about handling of MAC Move events in EVPN Single Flow-Active (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 highlighted):

   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 address is reachable via just one of the multiple PEs for the same Ethernet segment.
And indeed,  Section 5 of the SFA draft<https://datatracker.ietf.org/doc/html/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 multi-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 Forwarding" of the draft, and this section contains multiple references to RFC 9135.
Therefore, it is not clear to me whether the same rule is applicable to the scenarios in which SFA multi-homing should be applicable for intra-subnet forwarding scenarios.
My guess (FWIW) that it should be equally applicable, but an explicit clarification 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.