Hi Sami, To make my comments clear (in case it didn’t come through earlier emails), I am summarizing my comments again.
1. Clearly identify the role of AC and ES for point-to-point services 2. Clearly identify and document the reference model for the point-to-point services. For example, here is what I believe the model should look like. [cid:[email protected]] 3. Define an entity to toward PSN – see the picture above. Like I said earlier, if we don’t fix it now, it is only get worse/confusing as other extensions are added. 4. I would reiterate again – please summarize the functionality of RFC7432 that applies to point-to-point services and which does not. Users who are only interested in point-to-point services, could use this document to implement it without getting drowned information which is not relevant in such scenarios. Point-to-point services should be treated as services in their own wright – rather than after thought or extension of multipoint services. Hope this makes it clear the type of updates I am looking for. Thanks, Iftekhar From: Sami Boutros [mailto:[email protected]] Sent: Tuesday, February 07, 2017 11:55 AM To: Iftekhar Hussain Cc: Alvaro Retana (aretana); Jeffrey Zhang; [email protected]; [email protected]; [email protected] Subject: Re: [bess] AD Review of draft-ietf-bess-evpn-vpws-07 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
image001.emz
Description: image001.emz
oledata.mso
Description: oledata.mso
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
