Re: [bess] AD Review of draft-ietf-bess-fat-pw-bgp-03

2018-01-26 Thread Sami Boutros
Hi Albaro, Agreed with all comments, and we can change the “is requesting the ability” to “announce the ability”. Do we need to submit a new draft with the changes? Thanks, Sami From: Alvaro Retana mailto:aretana.i...@gmail.com>> Date: Friday, January 26, 2018 at 1:54 PM To: "draft-ietf-bess-

[bess] Last Call: (Usage and applicability of BGP MPLS based Ethernet VPN) to Informational RFC

2018-01-26 Thread The IESG
The IESG has received a request from the BGP Enabled ServiceS WG (bess) to consider the following document: - 'Usage and applicability of BGP MPLS based Ethernet VPN' as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Pleas

[bess] AD Review of draft-ietf-bess-evpn-usage-06

2018-01-26 Thread Alvaro Retana
Dear authors: Not much I can say about this document, except that it would have been nice if it was published earlier to provide background to other EVPN document. Thanks for your work!! I just have a couple of comments on the references (see below). I am starting the IETF Last Call. Alvaro.

[bess] Last Call: (Extensions to BGP Signaled Pseudowires to support Flow-Aware Transport Labels) to Proposed Standard

2018-01-26 Thread The IESG
The IESG has received a request from the BGP Enabled ServiceS WG (bess) to consider the following document: - 'Extensions to BGP Signaled Pseudowires to support Flow-Aware Transport Labels' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comm

[bess] AD Review of draft-ietf-bess-fat-pw-bgp-03

2018-01-26 Thread Alvaro Retana
Dear authors: I just finished reading this document. Thank you for a well written and straight forward document!! I have some comments (see below) that I think are easy to address. I am then starting the IETF Last Call. Thanks! Alvaro. Major: M1. All the rfc2119 keywords in this text shoul

[bess] Last Call: (Interconnect Solution for EVPN Overlay networks) to Proposed Standard

2018-01-26 Thread The IESG
The IESG has received a request from the BGP Enabled ServiceS WG (bess) to consider the following document: - 'Interconnect Solution for EVPN Overlay networks' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send

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

2018-01-26 Thread Alvaro Retana
Jorge: Thanks for the update. I’m starting the IETF LC, but I need you to please fix the nits related to the references: == Missing Reference: 'RFC8174' is mentioned on line 125, but not defined -- No information found for draft-ietf-bess-evpn-vpls-integration - is the name correct?

[bess] Protocol Action: 'A Network Virtualization Overlay Solution using EVPN' to Proposed Standard (draft-ietf-bess-evpn-overlay-11.txt)

2018-01-26 Thread The IESG
The IESG has approved the following document: - 'A Network Virtualization Overlay Solution using EVPN' (draft-ietf-bess-evpn-overlay-11.txt) as Proposed Standard This document is the product of the BGP Enabled ServiceS Working Group. The IESG contact persons are Alvaro Retana, Alia Atlas and De

Re: [bess] I-D Action: draft-ietf-bess-dci-evpn-overlay-06.txt

2018-01-26 Thread Rabadan, Jorge (Nokia - US/Mountain View)
Annop, That’s fine. We can certainly add something like this: “Advertising all the DC MAC addresses in the control/management plane is usually the case when the NVEs reside in hypervisors. Refer to [EVPN-Overlays] section 7.” Thank you. Jorge From: on behalf of Anoop Ghanwani Date: Thursday