Saumya, Jorge and all,
FWIW I concur with Jorge.
The draft states than an IP per EVI EVPN A-D route:
1. Includes RD of IO-VEF in its NLRI
2. Carries RT of IP-VRF.
Assuming that Import RTs of MAC-VRFs and IP-VRFs in any given PE are different,
I do not see any potential for wrong mapping.
My 2c,
Sasha
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Jorge Rabadan (Nokia) <jorge.raba...@nokia.com>
Sent: Friday, March 24, 2023, 23:26
To: Dikshit, Saumya <saumya.diks...@hpe.com>; Alexander Vainshtein
<alexander.vainsht...@rbbn.com>
Cc: bess@ietf.org <bess@ietf.org>
Subject: [EXTERNAL] Re: New Version Notification for
draft-sajassi-bess-evpn-ip-aliasing-06.txt
Hi Saumya,
I don’t think there is any need for especial flagging and the route-target will
identify in which VRF the route needs to be imported.
We have other cases in which a route type can be imported into a MAC-VRF or
IP-VRF (see RFC9135) and there is no especial ‘flag’ for it. This has not
caused any issues so I don’t see why A-D routes would create issues either, to
me it is the same thing.
Thanks.
Jorge
From: Dikshit, Saumya <saumya.diks...@hpe.com>
Date: Friday, March 24, 2023 at 6:50 AM
To: Jorge Rabadan (Nokia) <jorge.raba...@nokia.com>, Alexander Vainshtein
<alexander.vainsht...@rbbn.com>
Cc: bess@ietf.org <bess@ietf.org>
Subject: RE: New Version Notification for
draft-sajassi-bess-evpn-ip-aliasing-06.txt
CAUTION: This is an external email. Please be very careful when clicking links
or opening attachments. See
https://clicktime.symantec.com/15siFA3PedCRuwP2WEnEr?h=E0vKoxusvwRmg-2Wi4QRWfCEVPf2V0B7GpSJdjOAu1Q=&u=http://nok.it/ext
for additional information.
Thank You Jorge.
Since it’s already on the field, I have few follow up queries related to
“Interworking with BGP-Peers capable of ONLY MAC-aliasing”:
As I understand that the draft does not proposes any new PDU constructs and
leverages existing ones (as defined for MAC-aliasing in rfc7432) to publish IP
A-D per ES and IP A-D per EVI (EVPN Route Type 1) for IP-aliasing and
fast-convergence respectively.
1. For interworking with “BGP-EVPN peers” that comply only to MAC-aliasing
and not to IP-aliasing, are there any explicit procedures defined in the draft ?
2. As it’s expected to be Route-Target based absorption/dropping of the IP
A-D (per ES or EVI) NLRI,
a. is the ONLY implicit way for receive-side BGP-EVPN-Peers (only
expecting MAC-aliasing in network) to ignore the IP A-D routes.
b. If “a” is true, then is there a possibility that EVI mappings (MPLS
Labels, VNIs and corresponding Route-Targets) sent in IP A-D is being leveraged
by MAC-Aliasing for an Layer-2 configuration (Bridge-domain and corresponding
Route Targets) and can lead to error in processing.
3. Instead, will it apt to call out the IP A-D from MAC A-D via an
explicit flagging in the route itself. It will save the receive side BGP-EVPN
peer (only doing MAC-aliasing) from processing the IP A-D with no avail. Thus
saving some processing cycles which may lead to an error state.
It will be great to have a section for “backward compatibility with
MAC-aliasing ONLY peers”.
Regards,
Saumya.
From: Jorge Rabadan (Nokia) [mailto:jorge.raba...@nokia.com]
Sent: Thursday, March 23, 2023 3:58 PM
To: Dikshit, Saumya <saumya.diks...@hpe.com>; Alexander Vainshtein
<alexander.vainsht...@rbbn.com>
Cc: bess@ietf.org
Subject: Re: New Version Notification for
draft-sajassi-bess-evpn-ip-aliasing-06.txt
Hi Saumya,
Yes, there are implementations deployed in networks.
For the vendor I’m aware of, it includes pretty much all transport tunnels -
vxlan, mpls, sr-mpls, SRv6…
The use cases in the draft are agnostic of the transport.
Thx
Jorge
________________________________
From: Dikshit, Saumya <saumya.diks...@hpe.com<mailto:saumya.diks...@hpe.com>>
Sent: Thursday, March 23, 2023 09:51
To: Alexander Vainshtein
<alexander.vainsht...@rbbn.com<mailto:alexander.vainsht...@rbbn.com>>; Jorge
Rabadan (Nokia) <jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>
Cc: bess@ietf.org<mailto:bess@ietf.org> <bess@ietf.org<mailto:bess@ietf.org>>
Subject: RE: New Version Notification for
draft-sajassi-bess-evpn-ip-aliasing-06.txt
CAUTION: This is an external email. Please be very careful when clicking links
or opening attachments. See
http://nok.it/ext<https://clicktime.symantec.com/15siFA3PedCRuwP2WEnEr?h=E0vKoxusvwRmg-2Wi4QRWfCEVPf2V0B7GpSJdjOAu1Q=&u=http://nok.it/ext>
for additional information.
Hello Authors of draft-sajassi-bess-evpn-ip-aliasing,
If there is an implementation reference from any Vendor for this draft
https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-ip-aliasing/<https://clicktime.symantec.com/15siKzEg7Et2KtCx3oBPU?h=wNU3T3Cevp1QqxepBtv7LOJDxf-F4f7-WvODlSy5Hos=&u=https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-ip-aliasing/>.
It will be good to know if the reference fabric for the implementation. Does it
includes Vxlan, if not others ?
Regards,
Saumya.
From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Alexander Vainshtein
Sent: Tuesday, January 10, 2023 9:14 PM
To: Jorge Rabadan (Nokia)
<jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>
Cc: bess@ietf.org<mailto:bess@ietf.org>
Subject: Re: [bess] New Version Notification for
draft-sajassi-bess-evpn-ip-aliasing-06.txt
Jorge and all,
I have read the latest revision of the draft and I agree that it is ready for
the WG adoption call.
>From my POV it meets the two conditions that, IMHO, define WG adoption:
It addresses a real problem
It provides a reasonably good start for solution of this problem.
My 2c,
Sasha
From: BESS <bess-boun...@ietf.org<mailto:bess-boun...@ietf.org>> On Behalf Of
Jorge Rabadan (Nokia)
Sent: Tuesday, January 10, 2023 3:52 PM
To: bess@ietf.org<mailto:bess@ietf.org>
Subject: [EXTERNAL] [bess] FW: New Version Notification for
draft-sajassi-bess-evpn-ip-aliasing-06.txt
FYI
We just updated this draft based on the comments made by Sasha on the list. We
also fixed some nits and updated references.
We’d like to reiterate that document is ready for WG adoption call.
Thanks.
Jorge
From: internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>
<internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>>
Date: Tuesday, January 10, 2023 at 2:40 PM
To: A. Sajassi <saja...@cisco.com<mailto:saja...@cisco.com>>, G. Badoni
<gbad...@cisco.com<mailto:gbad...@cisco.com>>, J. Drake
<jdr...@juniper.net<mailto:jdr...@juniper.net>>, Jorge Rabadan (Nokia)
<jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>, L. Krattiger
<lkrat...@cisco.com<mailto:lkrat...@cisco.com>>, P. Warade
<pwar...@cisco.com<mailto:pwar...@cisco.com>>, S. Pasupula
<surpa...@cisco.com<mailto:surpa...@cisco.com>>, Ali Sajassi
<saja...@cisco.com<mailto:saja...@cisco.com>>, Gaurav Badoni
<gbad...@cisco.com<mailto:gbad...@cisco.com>>, John Drake
<jdr...@juniper.net<mailto:jdr...@juniper.net>>, Jorge Rabadan (Nokia)
<jorge.raba...@nokia.com<mailto:jorge.raba...@nokia.com>>, Lukas Krattiger
<lkrat...@cisco.com<mailto:lkrat...@cisco.com>>, Priyanka Warade
<pwar...@cisco.com<mailto:pwar...@cisco.com>>
Subject: New Version Notification for draft-sajassi-bess-evpn-ip-aliasing-06.txt
A new version of I-D, draft-sajassi-bess-evpn-ip-aliasing-06.txt
has been successfully submitted by J. Rabadan and posted to the
IETF repository.
Name: draft-sajassi-bess-evpn-ip-aliasing
Revision: 06
Title: EVPN Support for L3 Fast Convergence and Aliasing/Backup Path
Document date: 2023-01-10
Group: Individual Submission
Pages: 20
URL:
https://www.ietf.org/archive/id/draft-sajassi-bess-evpn-ip-aliasing-06.txt<https://clicktime.symantec.com/15siVeDMbsp2p1wKgTxN4?h=Bx1_zlXLVe5CXSl4uPQinOw4O-VdjSd1bRQf_MxBmjQ=&u=https://www.ietf.org/archive/id/draft-sajassi-bess-evpn-ip-aliasing-06.txt>
Status:
https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-ip-aliasing/<https://clicktime.symantec.com/15siKypngeSqz8HUbMA4p?h=izZF6rfMzUeFiWQGKAhvgPS53_OWNi_PQUtGVJSJxQo=&u=https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-ip-aliasing/>
Htmlized:
https://datatracker.ietf.org/doc/html/draft-sajassi-bess-evpn-ip-aliasing<https://clicktime.symantec.com/15siQp259G8SQ57Q8uZDS?h=oAVtm-7JQjfNt-rdM331nh6a308FM7ntGGsF4o4NBws=&u=https://datatracker.ietf.org/doc/html/draft-sajassi-bess-evpn-ip-aliasing>
Diff:
https://author-tools.ietf.org/iddiff?url2=draft-sajassi-bess-evpn-ip-aliasing-06<https://clicktime.symantec.com/15siF9dWE2mFaBTZ3nkvC?h=tpILk5e82UtksHG0WfCcO2FrK_oHNes6kqzFmThK-S8=&u=https://author-tools.ietf.org/iddiff?url2=draft-sajassi-bess-evpn-ip-aliasing-06>
Abstract:
This document proposes an EVPN extension to allow several of its
multihoming functions, fast convergence and aliasing/backup path, to
be used in conjunction with inter-subnet forwarding. The extension
is limited to All-Active and Single-Active redundancy modes.
The IETF Secretariat
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.
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.
_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
