Re: [bess] [Bier] [pim] WGLC: draft-ietf-bier-mvpn-05

On reflection, I think it's best if there is no requirement for a PE's BFR-Prefix to appear in the NLRI of any of the MVPN routes, no requirement for it to appear in the VRF Route Import EC, no requirement for it to appear in any next hop field, no requirement for it to appear in the

Re: [bess] [pim] WGLC: draft-ietf-bier-mvpn-05

We won’t need signaling. It will depend on ingress PE. If ingress PE does not send ipv6 explicit NULL, it should announce different upstream assigned label for afi. Egress PE should work in both scenario without any signaling of what ingress PE has implemented. Regards Swadesh On 6/21/17,

Re: [bess] [pim] WGLC: draft-ietf-bier-mvpn-05

Rosen MLDP MVPN(vpnid) and many other profiles have same tunnel for v4 and v6. I think it’s pretty standard to send ipv6 traffic with ipv6 explicit NULL. It was never required to be explicitly mention in RFC. Mandating to have different upstream assign label does not look correct. Should

Re: [bess] [pim] WGLC: draft-ietf-bier-mvpn-05

On 6/21/2017 2:22 PM, Swadesh Agrawal (swaagraw) wrote: It can be achieved by having ipv6 explicit NULL in data path. We may not need different label to identify AFI. We could have a rule saying that if MVPN payload packet is an IPv6 packet, then v6 explicit null must be pushed before the

Re: [bess] [Bier] [pim] WGLC: draft-ietf-bier-mvpn-05

Hi Eric, >> For BIER, I was thinking that the BFR-Prefix of the egress PE should >> appear in the "originating router's IP address" field of the Leaf A-D >> NLRI. However, it is probably better to allow the "originating router's >> IP address" to be different than the BFR-Prefix, and in that

Re: [bess] Slots requests for BESS WG session - IETF 99 - Prague

Hi Martin. EVPN / L2VPN Yang (10 min for both) Thanks Regards, Patrice Brissette On 2017-06-21, 4:33 AM, "BESS on behalf of Martin Vigoureux" wrote: All, it is time we start building the BESS WG agenda for Prague.

Re: [bess] WG Last Call for draft-ietf-bess-evpn-optimized-ir

Support it as a co-author and not aware of any IPR. Thanks Mukul From: Aldrin Isaac > Date: Wednesday, June 21, 2017 at 8:09 AM To: "EXT - thomas.mo...@orange.com"

Re: [bess] [pim] WGLC: draft-ietf-bier-mvpn-05

Stig, thanks for your comments.+ On 6/19/2017 5:47 PM, Stig Venaas wrote: Hi I think this draft is mostly ready. I just have a couple of comments. In section 1: This revision of the document does not specify the procedures necessary to support MVPN customers that are using BIDIR-PIM.

Re: [bess] WG Last Call for draft-ietf-bess-evpn-optimized-ir

Support this document for publication as an RFC. Not aware of any IPR that relates to this document. Cheers, Aldrin From: Aldrin Isaac Date: Friday, June 16, 2017 at 6:09 PM To: Ravi Shekhar , "Rabadan, Jorge (Nokia - US/Mountain View)"

Re: [bess] WG Last Call for draft-ietf-bess-evpn-optimized-ir

Support. Not aware of any IPR. From: BESS > on behalf of Aldrin Isaac > Date: Friday, June 16, 2017 at 9:09 PM To: Ravi Shekhar >, "Rabadan, Jorge

[bess] I-D Action: draft-ietf-bess-evpn-pref-df-00.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 of the IETF. Title : Preference-based EVPN DF Election Authors : Jorge Rabadan Senthil Sathappan

Re: [bess] Call for adoption: draft-rabadan-bess-evpn-pref-df / adopted !

Hi everyone, We have a new working group document! Can authors please repost as draft-ietf-bess-evpn-pref-df-00 ? Thanks, Thomas & Martin 2017-06-06, Thomas Morin: Hello working group, This email starts a two-week call for adoption on draft-rabadan-bess-evpn-pref-df-02 [1] as a Working

[bess] Slots requests for BESS WG session - IETF 99 - Prague

All, it is time we start building the BESS WG agenda for Prague. The IETF agenda (still preliminary) is available at: https://datatracker.ietf.org/meeting/99/agenda.html The BESS WG session (2h) is scheduled on Thursday, July 20, 2017 / Afternoon session II / 15:50-17:50 (local time) Please

Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage

WG, the WG LC has ended and we have support to move forward. I'll shepherd the document. -m Le 06/06/2017 à 16:11, Martin Vigoureux a écrit : Hello Working Group, This email starts a Working Group Last Call on draft-ietf-bess-evpn-usage-04 [1] which is considered mature and ready for a final