From: Yu Tianpeng <>
Date: Wednesday, January 9, 2019 at 4:03 AM
To: Cisco Employee <>
Cc: "" <>, 
"" <>
Subject: Re: [bess] WGLC, IPR and implementation poll for 

Thanks a lot Ali for the updating.
Looks fine for me apart from one point.
Correct me if I am wrong for what mentioned below.
This document aims to enable capability of evpn to be used on ENNI. But ENNI 
also have EVPL, ELAN and ETREE services.  This document have a brilliant 
solution, but overall current document only mentions usage in ELAN, so the 
question is how about ETREE and VPWS? As the solution in this document is vES 
based, I believe it should work for ETREE and VPWS without much extra 
considerations.  So if authors agree, I prefer to cover this in the current 
document. It is also fine for me if authors' choice is out of scope and prefer 
to cover other scenarios in a separate document.

I have already added VPWS. However, there is no point to list every EVPN 
solution in this document or else we have to list not just evpn-etree but 
evpn-overlay, evpn-irb, evpn-mcast, evpn-fxc, etc.

By the way another nits..
Sub type in figure 6 is not consistent with description above. I got lost on 
this as previous version was still 0x04.. so if 0x07 is the correct one please 
fix the value in the figure

That has already been corrected.


Thanks a lot.


On Wed, 9 Jan 2019, 00:31 Mankamana Mishra (mankamis) 
<<> wrote:
Thanks ali. I took look at the diff, it looks ok to me to move forward.


From: BESS <<>> on behalf of 
"Ali Sajassi (sajassi)" <<>>
Date: Tuesday, January 8, 2019 at 3:17 PM
To: Tim <<>>, 
"<>" <<>>
Subject: Re: [bess] WGLC, IPR and implementation poll for 

Tim, Mankamana,

The rev02 of the draft has the updates to address your latest comments.


From: BESS <<>> on behalf of 
Tim <<>>
Date: Monday, January 7, 2019 at 2:53 PM
To: "<>" 
"<>" <<>>
Subject: Re: [bess] WGLC, IPR and implementation poll for 


Support this work as an individual. This document is a great and elegant step 
for EVPN towards SP network.

Some small comments by the way:

1. Figure 2 shows the scope of EVPN network but the other figures in the 
document not. Please kindly update, then it is more readable.

2. There are 2 Figure 2

3. Document is lack of mention on E-Tree, it should work without any extra 
consideration right?

4. Please fix format issue in section 8 and update TBD in section 9.



On 2018/12/3 18:43,<> wrote:

Hello Working Group,

This email starts a two-week Working Group Last Call on 
draft-ietf-bess-evpn-virtual-eth-segment [1]

This poll runs until *the 17th of December*.

We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this Document please respond 
to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.

There is currently no IPR disclosed.

If you are not listed as an Author or a Contributor, then please explicitly 
respond only if you are aware of any IPR that has not yet been disclosed in 
conformance with IETF rules.

We are also polling for any existing implementation as per [2].

    Thank you,

    Stephane & Matthew




Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.


BESS mailing list<>
BESS mailing list

Reply via email to