Re: [bess] AD Review of draft-ietf-bess-evpn-vpws-07

["Shah, Himanshu" <[e-mail]>]

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.

Thus, when ESI link to primary fails, remote PE can quickly change the next hop
to next priority PE multi-home member.

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?).

If there are multiple primary PEs, and if one of them fail, why not switchover to other
primary PE, so on and so forth..

So what is the intent?

One primary, one backup
Multiple primary, one backup
Or (one or) multiple primaries, multiple backups?

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?

Thanks,
Himanshu

From: BESS [mailto:[e-mail]] On Behalf Of Sami Boutros
Sent: Tuesday, February 07, 2017 2:06 PM
To: Sami Boutros <[e-mail]>; Iftekhar Hussain <[e-mail]>
Cc: Jeffrey Zhang <[e-mail]>; Alvaro Retana (aretana) <[e-mail]>; [e-mail]; [e-mail]; [e-mail]
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