Hi Himanshu, Please see comments inline.
From: "Shah, Himanshu" <hs...@ciena.com<mailto:hs...@ciena.com>> Date: Tuesday, February 7, 2017 at 12:45 PM To: Sami Boutros <sbout...@vmware.com<mailto:sbout...@vmware.com>>, Sami Boutros <boutros.s...@gmail.com<mailto:boutros.s...@gmail.com>>, Iftekhar Hussain <ihuss...@infinera.com<mailto:ihuss...@infinera.com>> Cc: Jeffrey Zhang <zzh...@juniper.net<mailto:zzh...@juniper.net>>, "Alvaro Retana (aretana)" <aret...@cisco.com<mailto:aret...@cisco.com>>, "bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>" <bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>>, "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>, "draft-ietf-bess-evpn-v...@ietf.org<mailto:draft-ietf-bess-evpn-v...@ietf.org>" <draft-ietf-bess-evpn-v...@ietf.org<mailto:draft-ietf-bess-evpn-v...@ietf.org>> Subject: RE: [bess] AD Review of draft-ietf-bess-evpn-vpws-07 Hi Sami – It seems to me that single-active multihoming case could use some more clarification text. I think there should be an additional field in L2 extended community as (for example) “election priority” so that each multi-homed member can definitely tell to each other as well as to remote PE who/what primary election order would be. [Sami] In single active, there would be only one primary as per definition below in this e-mail. Thus, when ESI link to primary fails, remote PE can quickly change the next hop to next priority PE multi-home member. [Sami] Extending the DF election is not in scope for the draft and I doubt we will include it, however there are other drafts extending DF election like rabadan-evpn-pref-df. The text in VPWS draft is not very clear. It seems to suggest there could be multiple primaries and backups. But if that is true how would remote PE can independently switchover to backup PE (i.e. which backup PE?). [Sami] As per draft, "A remote PE receiving B=1 from more than one PE will select only one backup PE." If there are multiple primary PEs, and if one of them fail, why not switchover to other primary PE, so on and so forth.. [Sami] In single active there should be only one primary, having more than one primary will be transit in this case. So what is the intent? [Sami] As per EVPN, the intent is to support A/A in which all will be primary, or A/S in which only one primary and one backup. One primary, one backup Multiple primary, one backup Or (one or) multiple primaries, multiple backups? [Sami] We are not redefining what single active or all active mean, this is as per EVPN RFC7432 Single-Active Redundancy Mode: When only a single PE, among all the PEs attached to an Ethernet segment, is allowed to forward traffic to/from that Ethernet segment for a given VLAN, then the Ethernet segment is defined to be operating in Single-Active redundancy mode. I.e. One primary and one/multiple backup. All-Active Redundancy Mode: When all PEs attached to an Ethernet segment are allowed to forward known unicast traffic to/from that Ethernet segment for a given VLAN, then the Ethernet segment is defined to be operating in All-Active redundancy mode. I.e. Multiple Primary Also, there has to be corresponding understanding/configuration in CE as well. So if the CE+multi-hommed-PEs configuration is consistent and if all the parties, (CE, multi-homed PEs and remote PE) are aware of this, selection algorithm would work better? [Sami] Again, we are not redefining EVPN multihoming or DF election, those are following base EVPN. Thanks, Sami Thanks, Himanshu From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Sami Boutros Sent: Tuesday, February 07, 2017 2:06 PM To: Sami Boutros <boutros.s...@gmail.com<mailto:boutros.s...@gmail.com>>; Iftekhar Hussain <ihuss...@infinera.com<mailto:ihuss...@infinera.com>> Cc: Jeffrey Zhang <zzh...@juniper.net<mailto:zzh...@juniper.net>>; Alvaro Retana (aretana) <aret...@cisco.com<mailto:aret...@cisco.com>>; bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org>; draft-ietf-bess-evpn-v...@ietf.org<mailto:draft-ietf-bess-evpn-v...@ietf.org> Subject: Re: [bess] AD Review of draft-ietf-bess-evpn-vpws-07 Hi Iftekhar, Are you ok with what I added to the doc? For presenting the entity for Management. VPWS Service Instance: It is represented by a pair of EVPN service labels associated with a pair of endpoints. Each label is downstream assigned and advertised by the disposition PE through an Ethernet A-D per-EVI route. The downstream label identifies the endpoint on the disposition PE. A VPWS service instance can be associated with only one VPWS service identifier. Thanks, Sami
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
