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

[Sami Boutros <[e-mail]>]

Hi Iftekhar,


The management entity you are looking for is the evpn VPWS service instance, fxc can map more than one AC to this. I will add a definition in the doc to this evpn VPWS instance and mention that only one AC can be xconnected to it. Will that be ok?

[Iftekhar2] An issue pointed earlier that I see with the current solution is that there is no per service level entity for statistic counters on the PSN side. The LSP provides aggregate counters for all the services carried on that LSP.

[Sami] The EVPN-VPWS LSP here carries only one service not multiple servcies. Here is what I added. I hope this will be good enough.

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


A LSP could be carrying multiple VPWS-EVPN services. My suggestion is that it would be better to sort this out. Again, if other folks are happy with the current state of the doc, I don’t want to hold your doc.

Thanks,
Iftekhar

Thanks,

Sami