Support as a co-author. I am not aware of any undisclosed IPR.
Cheers,
Ali
From: "stephane.litkow...@orange.com"
Date: Monday, February 18, 2019 at 7:53 AM
To: "draft-rabadan-sajassi-bess-evpn-ipvpn-interwork...@ietf.org"
, "bess@ietf.org"
Cc: "bess-cha...@ietf.org"
Subject: WG adoption
Hi,
The WGLC has ended.
A new revision of the draft is required based on the discussions.
Authors,
Please publish the new revision, so we can proceed to the next step.
Brgds,
From: Andrew G. Malis [mailto:agma...@gmail.com]
Sent: Monday, January 28, 2019 15:37
To: John E Drake
Cc:
Hi WG,
The document has been updated to fulfil the comments raised by the WG.
The document is now ready to go to the next step.
Brgds,
From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com]
Sent: Thursday, January 31, 2019 03:25
To: LITKOWSKI Stephane OBS/OINIS; bess@ietf.org;
Hi All,
--
||
PORT1 | DEVICE1 |PORT3
--| PE1|-
| 1/5| 2.2.2.2 | 1/4 |
| || |
|
Thanks a lot Jide, for the reply.
Please find my response below [Jai]
Thanks & Regards
Jaikumar S
From: Jide Akintola
Sent: Monday, February 18, 2019 5:00 PM
To: bess@ietf.org; Jaikumar Somasundaram
Subject: Re: [bess] A question on using EVPN label and Alias label in load
balancing
Hi
Hi Jaikumar,
As per the rfc, aliasing is define as the ability of a PE to signal that it has
reachability to an EVPN instance on a given ES even when it has learned no MAC
addresses from that EVI/ES. It is advertised with Ethernet A-D per EVI type 1
routes.
Aliasing improves load-balancing by
Hi Jaikumar,
You need to make a distinction between Alias label and several other EVPN
routes labels defined in the RFC7432. Kindly check that RFC for the route
encoding and their different usage/function.
As detailed in my previous email, alias label is a "hint" to the remote PE to
load
It “sounds” to me that Jaikumar’s question might be related to comparing
MPLS-based vs MAC-based forwarding models.
RFC8388 may help, sections 6-8.
My 2 cents.
Thx
Jorge
From: BESS on behalf of Jide Akintola
Date: Monday, February 18, 2019 at 1:23 PM
To: "bess@ietf.org" , Jaikumar
As co-author
Support.
Not aware of any undisclosed IPR.
Thanks,
Jim Uttaro
From: stephane.litkow...@orange.com
Sent: Monday, February 18, 2019 10:53 AM
To: draft-rabadan-sajassi-bess-evpn-ipvpn-interwork...@ietf.org; bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: WG adoption
Support the adoption.
Thanks
Mankamana
From: "stephane.litkow...@orange.com"
Date: Monday, February 18, 2019 at 7:53 AM
To: "draft-rabadan-sajassi-bess-evpn-ipvpn-interwork...@ietf.org"
, "bess@ietf.org"
Cc: "bess-cha...@ietf.org"
Subject: WG adoption and IPR poll for
This email begins a two-week poll for adoption of
draft-rabadan-sajassi-bess-evpn-ipvpn-interworking-02
[1]
Please review the draft and post any comments to the BESS working group list.
We are also polling for knowledge of any undisclosed IPR that applies to this
Document, to ensure that IPR
As co-author, I support this document for adoption.
Not aware of any relevant IPR.
Thank you.
Jorge
From: "stephane.litkow...@orange.com"
Date: Monday, February 18, 2019 at 4:53 PM
To: "draft-rabadan-sajassi-bess-evpn-ipvpn-interwork...@ietf.org"
, "bess@ietf.org"
Cc: "bess-cha...@ietf.org"
Support. I'm not aware of any IPR.
Yours Irrespectively,
John
From: stephane.litkow...@orange.com
Sent: Monday, February 18, 2019 10:53 AM
To: draft-rabadan-sajassi-bess-evpn-ipvpn-interwork...@ietf.org; bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: WG adoption and IPR poll for
Ok, let me elaborate.
A remote PE sending known unicast traffic to any PE attached to the all-active
Ethernet Segment (non-DF or DF, it’s irrelevant here!), has to use a label that
identifies the Broadcast Domain at the egress PE for a MAC lookup (if MAC-based
forwarding) or a label that
Yes/support
Cheers,
Jeff
On Feb 18, 2019, 7:53 AM -0800, stephane.litkow...@orange.com, wrote:
> This email begins a two-week poll for adoption of
> draft-rabadan-sajassi-bess-evpn-ipvpn-interworking-02
> [1]
>
> Please review the draft and post any comments to the BESS working group list.
>
>
15 matches
Mail list logo
