Re: [bess] Poll for adoption: draft-rabadan-bess-evpn-ac-df

2016-09-05 Thread Nagaraj, Kiran (Nokia - US) 
Support as co-author not aware of IPR related to this draft
Thanks
Kiran

From: Henderickx, Wim (Nokia - BE) [mailto:wim.henderi...@nokia.com]
Sent: Monday, September 05, 2016 11:18 AM
To: Wen Lin; EXT - thomas.mo...@orange.com; bess@ietf.org
Cc: draft-rabadan-bess-evpn-ac...@ietf.org
Subject: Re: [bess] Poll for adoption: draft-rabadan-bess-evpn-ac-df

Support as co-author not aware of IPR related to this draft

From: BESS > on behalf of 
Wen Lin >
Date: Monday 5 September 2016 at 16:29
To: "EXT - thomas.mo...@orange.com" 
>, 
"bess@ietf.org" >
Cc: 
"draft-rabadan-bess-evpn-ac...@ietf.org"
 
>
Subject: Re: [bess] Poll for adoption: draft-rabadan-bess-evpn-ac-df


Support as a co-author.  I am unaware of any IPR related to this draft.

Thanks,
Wen



On 8/30/16, 1:45 AM, "Thomas Morin" 
> wrote:

Hello working group,

This email starts a two-week poll on adopting
draft-rabadan-bess-evpn-ac-df-05 [1] as a Working Group document.

Please state on the list if you support adoption or not (in both cases,
please also state the reasons).

This poll runs until *September 14th*.

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 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.

At this date, no IPR has been disclosed against this Document.

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

Thank you

Martin & Thomas
bess chairs

[1] https://datatracker.ietf.org/doc/draft-rabadan-bess-evpn-ac-df

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] Poll for adoption: draft-rabadan-bess-evpn-ac-df

2016-09-05 Thread Oya Luengo, Roberto (Nokia - US) 
Support

On Sep 5, 2016, at 11:18 AM, Henderickx, Wim (Nokia - BE) 
> wrote:

Support as co-author not aware of IPR related to this draft

From: BESS > on behalf of 
Wen Lin >
Date: Monday 5 September 2016 at 16:29
To: "EXT - thomas.mo...@orange.com" 
>, 
"bess@ietf.org" >
Cc: 
"draft-rabadan-bess-evpn-ac...@ietf.org"
 
>
Subject: Re: [bess] Poll for adoption: draft-rabadan-bess-evpn-ac-df


Support as a co-author.  I am unaware of any IPR related to this draft.

Thanks,
Wen



On 8/30/16, 1:45 AM, "Thomas Morin" 
> wrote:

Hello working group,

This email starts a two-week poll on adopting
draft-rabadan-bess-evpn-ac-df-05 [1] as a Working Group document.

Please state on the list if you support adoption or not (in both cases,
please also state the reasons).

This poll runs until *September 14th*.

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 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.

At this date, no IPR has been disclosed against this Document.

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

Thank you

Martin & Thomas
bess chairs

[1] https://datatracker.ietf.org/doc/draft-rabadan-bess-evpn-ac-df

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

[bess] RTG Dir QA review: draft-ietf-bess-evpn-overlay-04.txt

2016-09-05 Thread Keyur Patel 
Hello,

I have been selected as the Routing Directorate QA reviewer for 
draft-ietf-bess-evpn-overlay-04.txt.


The Routing Directorate QA reviews are intended to be a support to improve the 
quality of RTG Area documents as they pass through the IETF process. This is 
the QA review at the time of the WG document adoption poll.


Summary:


This document describes how Ethernet VPN (EVPN) [RFC7432] can be used as a 
Network Virtualization Overlay (NVO) solution and explores the various tunnel 
encapsulation options over IP and their impact on the EVPN control-plane and 
procedures. In particular, the following encapsulation options are analyzed: 
VXLAN, NVGRE, and MPLS over GRE.



The document is well written, easy to read and follow. Some minor comments are 
listed below:


Comments:


1) Introduction section suggests xmpp based approach as an alternative to the 
BGP as a control plane. It is unclear how the draft sections 8-10 and the 
security section 12 relate to the alternative solution. My suggestion would be 
to remove the reference if possible considering the draft is specific to BGP as 
a control plane.


2) Section 5.1.2.1 defines Autoderivation RT which suggests the use of 2 byte 
AS number. Do we need to consider 4 byte AS number as well? []


3) Section 6: Minor Nit. Consider replacing "statically" with "locally".


4) Section 7.1: Talks about using RD value of 0. RD as a type:value field. Type 
0 RD requires the usage of 2 byte AS number (private values are strongly 
discouraged) which needs to be 0 for RD value to be 0. AS 0 according to IANA 
is reserved. Seems to be like usage of AS 0 is prohibited. Would a reserve RD 
value be more appropriate?


5) section 8.3.1 describes the draft constrain wrt mpls over gre versus 
vxlan/nvgre. Perhaps it would be great to highlight the constrain upfront in 
the introduction section?


6) Do you need to add text to describe ARP/ND suppression in presence of 
default route?


Best Regards,

Keyur
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess