Subject: [bess] Sync between l2vpn service models

From: Rotem Cohen <[email-masked]>
Date: Thu, 3 Dec 2015 15:02:02 +0000

Dear authors of L2VPN service model drafts,

Can you clarify please the relation between draft-shah-bess-l2vpn-yang<https://tools.ietf.org/html/draft-shah-bess-l2vpn-yang-00> and draft-xie-l3sm-l2vpn-service-model-00<https://tools.ietf.org/html/draft-xie-l3sm-l2vpn-service-model-00>?

There are fundamental differences between L2VPN and L3VPN services and it does not seem right to derive one model from the other. draft-xie-l3sm-l2vpn-service-model-00<https://tools.ietf.org/html/draft-xie-l3sm-l2vpn-service-model-00> made the effort to explain these differences but if the starting point had not been the L3VPN service model then it would not be necessary to do so.
VPLS and VPWS are widely deployed in MPLS-TP networks which do not assume any IP routing/forwarding capabilities and therefore using L3VPN constructs to define L2VPN services is not natural for these applications.

Relating to the conclusion section, the structure of L2VPN service is quite clear and modelling it without relying on L3VPN should not be regarded as reinventing a new wheel.

Thanks & regards,

Rotem Cohen

PTS System Architecture Group Manager

T:

+972.3.926.8247

M:

+972.54.926.8247

E:

[email-masked]<mailto:[email-masked]>

www.ecitele.com<http://www.ecitele.com/>