Hi Robert, From: rtgwg <[email protected]<mailto:[email protected]>> on behalf of Robert Raszuk <[email protected]<mailto:[email protected]>> Date: Thursday, November 17, 2016 at 8:13 PM To: Routing WG <[email protected]<mailto:[email protected]>> Subject: Draft-rtgyangdt-rtgwg-routing-types
Hi, I have a question on the intention on how complete the document should be ? As example on vpn section why RT is described and SOO is not mentioned ? This was taken from one of the other models. Can you indicate what is missing from the syntax of the RT for Site of Origin (SOO)? Similar why extended communities are mentioned and no format is defined for standard or cost communities also necessary for some vpn provisioning ? We will check with the BGP and L3VPN model owners. Similar I do not see defined format for static mpls labels ... This could be something we could add. For router-id is this per protocol, global or per vrf ? This router-id type could apply to any of these. It is the type as opposed to an instance of a router-id. In other words is the intention here to only list cherry picked elements which are found in at least two protocols ? Yes - this is to allow common definitions without having to redefine them or import entire models. Thanks, Acee I think to make it complete much more work is needed ... provided I understand the main objective of this proposal. Many thx, R.
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
