Re: [bess] Shepherd's review of draft-ietf-bess-evpn-ac-df

Hi Jorge, Thanks for your answers. Pls find more inline [SLI2] -Original Message- From: Rabadan, Jorge (Nokia - US/Mountain View) [mailto:jorge.raba...@nokia.com] Sent: Tuesday, January 30, 2018 16:20 To: LITKOWSKI Stephane OBS/OINIS; draft-ietf-bess-evpn-ac-df.auth...@ietf.org Cc: bes

Re: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

Hi John, Speaking as doc shepherd for the ac-df draft, I agree that this make sense and this will provide more backward compatibility with the behavior defined in RFC7432. Brgds, From: John E Drake [mailto:jdr...@juniper.net] Sent: Tuesday, January 30, 2018 17:17 To: Rabadan, Jorge (Nokia - US

[bess] I-D Action: draft-ietf-bess-mvpn-expl-track-05.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the BGP Enabled ServiceS WG of the IETF. Title : Explicit Tracking with Wild Card Routes in Multicast VPN Authors : Andrew Dolganow

[bess] I-D Action: draft-ietf-bess-mvpn-expl-track-06.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the BGP Enabled ServiceS WG of the IETF. Title : Explicit Tracking with Wild Card Routes in Multicast VPN Authors : Andrew Dolganow

Re: [bess] Comments on draft-ietf-bess-mvpn-expl-track-03

Thanks for delving into the details here.  This part of the writeup is very confusing (for which I have no one to blame but myself); I've tried to clarify in the -06 revision. On 1/18/2018 9:51 PM, Xiejingrong wrote: Issue clarification: According to chap 5.2 of this document: In a [Ingress

Re: [bess] WG Last Call (including implem status) for draft-ietf-bess-evpn-ac-df

Yes, this will be consistent with the existing framework. Thanks, —Satya From: BESS mailto:bess-boun...@ietf.org>> on behalf of "stephane.litkow...@orange.com" mailto:stephane.litkow...@orange.com>> Date: Wednesday, January 31, 2018 at 12:55 AM To: "jdr...@

[bess] RFC 8317 on Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN)

A new Request for Comments is now available in online RFC libraries. RFC 8317 Title: Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN) Author: A. Sajassi, Ed.,