Dear Authors,

I have reviewed the draft-ietf-bess-l3vpn-yang-04. And I have the following 
comment:
# First of all, this draft has expired, and L3VPN YANG is a very useful model, 
so please update it as soon as possible.
And for the YANG model,
# Is it necessary to define two branches to distinguish IPv4 and IPv6? Why not 
define a type to distinguish the IPv4 and IPv6?
# Why does the export-to-global not refers to routing-policy?
# Is it necessary to configure routing-table-limit both in network-instance and 
bgp:ipv4-unicast?
# Why the instance attribute within import-from-global does not use the leafref 
to refer to network-instance?

Best Regards!
-Michael


_______________________________________________
BESS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bess

Reply via email to