This draft has one of this highest usefulness vs. length ratios I've ever seen. I very much support publication. My only comment is that there's an obvious typo in section 3, "secirity".
Cheers, Andy On Thu, Jun 12, 2014 at 9:42 AM, Martin Vigoureux < [email protected]> wrote: > Working Groups, > > This is to start a 2-week Working Group Last Call in three Working > Groups (idr, l3vpn and mpls) on draft-ietf-l3vpn-pmsi-registry-02. > > The draft has been made a WG Document by WG Chairs decision. > > In RFC 6514 (BGP Encodings and Procedures for Multicast in MPLS/BGP IP > VPNs), an optional transitive BGP attribute called the > "P-Multicast Service Interface Tunnel (PMSI Tunnel) attribute" is > specified. This BGP attribute uses an octet field to specify the > PMSI tunnel type. RFC 6514 allocates the values 0-7. > > There now is need to make further code point allocations from this > name space. In particular, draft-ietf-mpls-seamless-mcast > needs to make such an allocation. That draft is currently in WG Last > Call in the MPLS Working Group. > > draft-ietf-l3vpn-pmsi-registry creates a new IANA registry called > "P-Multicast Service Interface Tunnel (PMSI Tunnel) Tunnel Types" for these > code points. > The registry is created in the "Border Gateway Protocol (BGP) > Parameters" registry. > > Please send comments to the l3vpn mailing list ([email protected]). > > The WG LC will end on Friday the 27th of June. > > > Martin, on behalf of the WGs co-chairs > > _______________________________________________ > mpls mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/mpls >
