Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

PM To: Sami Boutros <sbout...@vmware.com<mailto:sbout...@vmware.com>> Cc: bess@ietf.org<mailto:bess@ietf.org> Subject: Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03 Hi Sami, I thought about this BW topic further, and have

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

27, 2016 at 2:41 PM > To: Sami Boutros <sbout...@vmware.com> > Cc: "bess@ietf.org" <bess@ietf.org> > Subject: RE: [bess] FW: WG Last Call (including implem status & shepherd) for > draft-ietf-bess-evpn-vpws-03 > > Hi Sami, > > I thought about

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Zhang" <zzh...@juniper.net<mailto:zzh...@juniper.net>> Date: Friday, May 27, 2016 at 2:41 PM To: Sami Boutros <sbout...@vmware.com<mailto:sbout...@vmware.com>> Cc: "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>> Subject: R

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

are.com>> Cc: "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>> Subject: RE: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03 Hi Sami, I thought about this BW topic further, and have the

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hi Sami, I thought about this BW topic further, and have the following question: - Even for the originally stated purpose, i.e. for PE1 to request PE2 to request BW reservation in the network, why does it have to be signaled from PE1? Why can’t you provision PE2 to request that BW reservation?

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Sami, Please see zzh3> below. I’ve trimmed some text. From: Sami Boutros [mailto:sbout...@vmware.com] Sent: Wednesday, May 18, 2016 4:23 PM To: Jeffrey (Zhaohui) Zhang <zzh...@juniper.net> Cc: bess@ietf.org Subject: Re: [bess] FW: WG Last Call (including implem status & shepherd) fo

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hi Sami, Some text snipped … Please see zzh2> below. Zzh> When it comes to PIC, the closed thing I can find in section 5 is the following: Upon link or node failure, EVPN can trigger failover with the withdrawal of a single BGP route per EVPL service or multiple EVPL services,

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

g<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>> Subject: RE: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03 Hi Sami, Please see zzh> below. I trimmed some text. ... eliminates the need for single-segmen

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hi Jeffrey, Thanks for your comments, Please see responses inline. Hi, As the document shepherd, I have the following questions/comments. Some of which are just editorial nits. This document describes how EVPN can be used to support virtual private wire service (VPWS) in MPLS/IP

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Ali > >Thanks. > >Jeffrey > >> -Original Message- >> From: Rabadan, Jorge (Nokia - US) [mailto:jorge.raba...@nokia.com] >> Sent: Thursday, May 12, 2016 2:28 PM >> To: Jeffrey (Zhaohui) Zhang <zzh...@juniper.net>; BESS <bess@ietf.org> >> Subject: R

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hi Jeffrey, This is a draft based on RF7432 and as such we are expecting tag manipulation wrt vlan-based service to be consistent with RFC 7432. Additional comments below Š On 5/12/16, 11:27 AM, "BESS on behalf of Rabadan, Jorge (Nokia - US)"

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

HI Jeffrey, On 5/12/16, 8:13 PM, "BESS on behalf of EXT Jeffrey (Zhaohui) Zhang" wrote: >Hi Jorge, > >> >If a PE sends a route w/o setting P-bit, wouldn't that indicate it is a >> backup? Why would it bother sending the route if it does

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hi Jorge, > >If a PE sends a route w/o setting P-bit, wouldn't that indicate it is a > backup? Why would it bother sending the route if it does not want to be > the backup? > > [JORGE] Let’s assume you have 3 PEs in ES-1 (PE1/2/3) that is a single- > active ES. PE4 is a remote PE doing backup

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

12, 2016 7:44 AM >> To: Jeffrey (Zhaohui) Zhang <zzh...@juniper.net>; BESS <bess@ietf.org> >> Subject: Re: [bess] FW: WG Last Call (including implem status & shepherd) >> for draft-ietf-bess-evpn-vpws-03 >> >> Jeffrey, >> >> I’m sure we will fix

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hi Jorge, > -Original Message- > From: Rabadan, Jorge (Nokia - US) [mailto:jorge.raba...@nokia.com] > Sent: Thursday, May 12, 2016 7:44 AM > To: Jeffrey (Zhaohui) Zhang <zzh...@juniper.net>; BESS <bess@ietf.org> > Subject: Re: [bess] FW: WG Last Call (includi

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Jeffrey, I’m sure we will fix the editorial changes… Just wanted to comment on a few questions you had on the VIDs, eth-tags, P/B bits and ES label. Please see in-line with [JORGE]. Thank you! Jorge On 5/11/16, 8:13 PM, "BESS on behalf of EXT Jeffrey (Zhaohui) Zhang"

Re: [bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

Hi, As the document shepherd, I have the following questions/comments. Some of which are just editorial nits. This document describes how EVPN can be used to support virtual private wire service (VPWS) in MPLS/IP networks. Please capitalize "virtual private wire service". There are two

[bess] FW: WG Last Call (including implem status & shepherd) for draft-ietf-bess-evpn-vpws-03

FYI Yours Irrespectively, John -Original Message- From: John E Drake [mailto:jdr...@juniper.net] Sent: Monday, May 09, 2016 9:54 AM To: EXT - thomas.mo...@orange.com; Rabadan, Jorge (Nokia - US); draft-ietf-bess-evpn-v...@ietf.org; EXT Ali Sajassi (sajassi); EXT Sami Boutros Cc: BESS