Re: [bess] Last mile for WGLC on draft-ietf-bess-evpn-ipvpn-interworking-04 => need IDR review

["Rabadan, Jorge (Nokia - US/Mountain View)" <[e-mail]>]

Hi Jim,

Happy New Year!
I think what you say should be discussed offline, outside the context of this Last Call, since it is new work.
We don’t want to delay the progress of the evpn-ipvpn-interworking draft, which has been implemented by some vendors and it is being implemented by others.

Would you agree?

Thanks,
Jorge


From: Idr <[e-mail]> on behalf of UTTARO, JAMES <[e-mail]>
Date: Monday, January 4, 2021 at 8:31 AM
To: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>
Cc: [e-mail] <[e-mail]>
Subject: Re: [Idr] [bess] Last mile for WGLC on draft-ietf-bess-evpn-ipvpn-interworking-04 => need IDR review
Jorge,

              When we first began specifying this draft we had three models. The composite PE ( Ships in the Night ), Inter-Working PE and exchange of state using RRs where the set of PEs supporting EVPN, L3VPN and IP share a common reachability domain i.e BGP LU ( 3107 ). Currently the draft does not specify the RR model as we decided that would not be in the original version. As this draft is moving quickly would a subsequent revision/bis specify the RR model?  IMO the RR model is quite desirable as there are traffic can follow the “best path” with that is lowest cost, performance, availability, geo-political concerns etc.. There are broad implications for network slicing when traffic has to traverse discreet gateways in the network. The same reasons operators like Option C as opposed to A or B apply here. I have attached a few slides where we discussed this..

Thanks,
              Jim Uttaro

[cid:image001.jpg@01D6E27A.1280B280]

[cid:image002.jpg@01D6E27A.1280B280]
From: BESS <[e-mail]> On Behalf Of [e-mail]
Sent: Monday, January 04, 2021 6:24 AM
To: [e-mail]
Cc: [e-mail]
Subject: [bess] Last mile for WGLC on draft-ietf-bess-evpn-ipvpn-interworking-04 => need IDR review

Hi IDR WG,

We are in the last mile for the WGLC of draft-ietf-bess-evpn-ipvpn-interworking-04 in BESS WG.
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-ipvpn-interworking<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-bess-evpn-ipvpn-interworking__;!!BhdT!xbIM5_c0J3-GuSHDrQlLm4v7batDnrDlmsTU9EryGl65wjWlrugLwQiVgVo$>

Couple of comments from our groups have been already addressed.

As BESS WG co-chair, I would like to get your feedback on the document.

There are couple of point that need to be looked at:

-          The draft defines a new path attributes DPATH for loop prevention across “domains” (domain does not mean AS here).

-          It defines some propagation / non propagation rules of attributes by the gateway PE (in uniform mode). I would like to spot your attention here. One consequence is that for any new attribute defined in BESS or IDR, we’ll have to define the propagation rules by gateway PEs. I would like to hear the opinion of the IDR group and IDR chairs on that point.

-          It defines aggregation rules of attributes in the context of the IP VRF. I would like also to hear opinion from the group and chair on this.

Thanks to provide your feedback as soon as possible (pls cross post in IDR and BESS).


Brgds,

Stephane