,
>
>
>
> In-line, please.
>
> Thanks,
>
> Jorge
>
>
>
> *From: *Gyan Mishra
> *Date: *Thursday, March 26, 2020 at 8:50 AM
> *To: *"Rabadan, Jorge (Nokia - US/Mountain View)" >
> *Cc: *BESS , "UTTARO, JAMES"
> *Subject: *Re: [
Hi Gyan,
In-line, please.
Thanks,
Jorge
From: Gyan Mishra
Date: Thursday, March 26, 2020 at 8:50 AM
To: "Rabadan, Jorge (Nokia - US/Mountain View)"
Cc: BESS , "UTTARO, JAMES"
Subject: Re: [bess] vxlan evpn and L3 vpn interworking standard
Hi Jorge
Thank you for the c
e
>
>
>
>
>
> *From: *BESS on behalf of Gyan Mishra <
> hayabusa...@gmail.com>
> *Date: *Wednesday, March 25, 2020 at 10:44 PM
> *To: *"UTTARO, JAMES"
> *Cc: *BESS
> *Subject: *Re: [bess] vxlan evpn and L3 vpn interworking standard
>
>
>
&g
uot;
Cc: BESS
Subject: Re: [bess] vxlan evpn and L3 vpn interworking standard
Hi Jim
I read through the draft. This is exactly what I was looking for. So in our
scenario we would use the gateway PE option where we are exporting the EVPN
routes & importing VPNv4 & VPNv6 and vice versa and
Hi Jim
I read through the draft. This is exactly what I was looking for. So in
our scenario we would use the gateway PE option where we are exporting the
EVPN routes & importing VPNv4 & VPNv6 and vice versa and would use the "D
Path" attribute for loop avoidance between domains. Our DCI
Thank you!!
Gyan
On Wed, Mar 25, 2020 at 3:30 AM Rabadan, Jorge (Nokia - US/Mountain View) <
jorge.raba...@nokia.com> wrote:
> Hi Gyan,
>
>
>
> The evpn ipvpn interworking draft was adopted as:
>
>
>
> https://tools.ietf.org/html/draft-ietf-bess-evpn-ipvpn-interworking-02
>
>
>
> Thx
>
> Jorge
Hi Gyan,
The evpn ipvpn interworking draft was adopted as:
https://tools.ietf.org/html/draft-ietf-bess-evpn-ipvpn-interworking-02
Thx
Jorge
From: BESS on behalf of Gyan Mishra
Date: Wednesday, March 25, 2020 at 6:38 AM
To: BESS
Subject: [bess] vxlan evpn and L3 vpn interworking standard
