Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

Hi Thomas, I have incorporated your comments into rev11 of the document. Cheers, Ali On 12/8/17, 1:45 AM, "Thomas Morin" wrote: Ali, A few nits, sorry for not answering earlier: > > I added the following paragraph to section 6 for

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

Ali, A few nits, sorry for not answering earlier: > > I added the following paragraph to section 6 for clarification: > “When a PE advertises multiple supported encapsulations, it MUST > advertise encapsulations that use the same EVPN procedures including > procedures associated with

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

Ali Sajassi (sajassi), 2017-12-08 03:01: > M8.2. These should also be Normative: RFC7348, NVGRE, VXLAN- > > GPE, RFC4023 > > > > [Ali] Please refer to Thomas explanation on this which is copied > > here for your convenience: > > “My process fu is weakening, but if this specification is standard

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

ess-cha...@ietf.org>, Cisco Employee <saja...@cisco.com> Cc: Thomas Morin <thomas.mo...@orange.com>, "bess@ietf.org" <bess@ietf.org> Subject: Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08 On December 5, 2017 at 10:53:02 PM, Ali Sajassi (sajassi) (saja...@cis

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

On December 5, 2017 at 10:53:02 PM, Ali Sajassi (sajassi) (saja...@cisco.com) wrote: Ali: Hi! Thanks for the review. Please refer to my replies to your comments marked with [Ali] inline. I have incorporated them in rev09 of the draft that has just been published. Please let me know if you have

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

I will add the following sentence to the abstract. “This specification is also applicable to other NVO encapsulations such as GENEVE, GPE, and GUE; however, these encapsulations may require additional incremental work and thus will be specified in separate document(s).” I think that

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

On December 6, 2017 at 6:52:42 AM, Ali Sajassi (sajassi) (saja...@cisco.com) wrote: Martin Vigoureux, 2017-12-05 11:34: Perhaps draft-ietf-bess-evpn-overlay could hint on such a Geneve work for EVPN; something like: "Adapting the EVPN control plane to the Geneve encapsulation is out of the

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

On December 4, 2017 at 5:16:49 PM, John E Drake (jdr...@juniper.net) wrote: (1) Coordination with nv03 For the Chairs: Except for some clarification comments [1] related to the current version, I see no other traffic in the nvo3 list related to this document. Was there some other

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

Hi Thomas, Please see my reply inline. On 12/5/17, 6:25 AM, "BESS on behalf of thomas.mo...@orange.com" wrote: All, Martin Vigoureux, 2017-12-05 11:34: Perhaps draft-ietf-bess-evpn-overlay could hint on such a

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

behalf of Alvaro Retana <aretana.i...@gmail.com> Date: Monday, December 4, 2017 at 1:49 PM To: "bess-cha...@ietf.org" <bess-cha...@ietf.org> Cc: Thomas Morin <thomas.mo...@orange.com>, "bess@ietf.org" <bess@ietf.org> Subject: [bess] AD Review of draft-ietf-be

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

Alvaro, the docs are draft-boutros-bess-evpn-geneve-00 draft-rabadan-nvo3-evpn-applicability-00 -m Le 05/12/2017 à 23:08, Alvaro Retana a écrit : On December 5, 2017 at 9:25:39 AM, thomas.mo...@orange.com (thomas.mo...@orange.com

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

On December 5, 2017 at 9:25:39 AM, thomas.mo...@orange.com ( thomas.mo...@orange.com) wrote: > > [...] > > > M8. References > > > M8.1. TUNNEL-ENCAP (aka ) should be > Normative, which btw is marked to Obsolete rfc5512; I mention this > because both are listed in several parts, so you should take

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

Perfect, thanks! Is that draft already in the works, or just planned? [Ali] It is already in the works: https://tools.ietf.org/html/draft-boutros-bess-evpn-geneve-00 Cheers, Ali Alvaro. ___ BESS mailing list BESS@ietf.org

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

On December 5, 2017 at 9:25:39 AM, thomas.mo...@orange.com ( thomas.mo...@orange.com) wrote: > > > (2) Document Status > > > Why is this a Standards Track document? The Abstract/Introduction > say > that “this document describes how Ethernet VPN (EVPN) can be used > as an > NVO solution and

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

All, Martin Vigoureux, 2017-12-05 11:34: > > Alvaro: [...] > > > > What about Geneve (draft-ietf-nvo3-geneve)? The nvo3 WG is > > focusing on > > Geneve as the Standard encapsulation, but this document doesn’t > > even mention it. > > Indeed. But The decision by NVO3 to work on Geneve is

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

Hello Alvaro, thanks for your review. Please see in-line regarding the two first points. -m Le 04/12/2017 à 22:49, Alvaro Retana a écrit : Dear Authors: I just finished reading this document (finally!). I have a some comments (see below) which I think should be easy to address. I also have

Re: [bess] AD Review of draft-ietf-bess-evpn-overlay-08

draft-ietf-bess-evpn-overlay-08 Dear Authors: I just finished reading this document (finally!). I have a some comments (see below) which I think should be easy to address. I also have some bigger issues that we’ll need the Chairs’ help to solve: (1) Coordination with nv03 For the Chairs:

[bess] AD Review of draft-ietf-bess-evpn-overlay-08

Dear Authors: I just finished reading this document (finally!). I have a some comments (see below) which I think should be easy to address. I also have some bigger issues that we’ll need the Chairs’ help to solve: (1) Coordination with nv03 For the Chairs: Except for some clarification