Hi,Jeffrey Section 3 said: RFC 6514 specifies that MCAST-VPN routes carry a Route Distinguisher (RD). For GTM, it SHOULD be possible to configure an RD that is used only for MCAST-VPN A-D routes for the global table. The RD can be defaulted to a special 64-bit all-zero value (denoted as RD 0:0). This means we can configure the RD when GTM is enable, right? Here is a question: In a large network, there are many different administrators,what if admin1 configures the value 1:1 in his manage area(area1), and admin2 configures the valure 2:2 in another area(area2)?
If I miss something please point out.Thanks! BRs Linda Wang > Hi, > > This is an update to draft-zzhang-mboned-mvpn-global-table-mcast-00. > > We have re-homed it to l3vpn, and hopefully addressed most comments > that Eric had. > > Your review and comments are appreciated. > > Thanks. > Jeffrey > > -----Original Message----- > From: internet-drafts at ietf.org [mailto:internet-drafts at ietf.org] > Sent: Friday, July 12, 2013 3:55 PM > To: Dante J.Pacella; Lenny Giuliano; Jason Schiller; Lenny Giuliano; > Jeffrey (Zhaohui) Zhang > Subject: New Version Notification for draft-zzhang-l3vpn-mvpn- > global-table-mcast-00.txt > > > A new version of I-D, draft-zzhang-l3vpn-mvpn-global-table-mcast-00.txt > has been successfully submitted by Jeffrey Zhang and posted to the > IETF repository. > > Filename: draft-zzhang-l3vpn-mvpn-global-table-mcast > Revision: 00 > Title: Global Table Multicast with BGP-MVPN Procedures > Creation date: 2013-07-12 > Group: Individual Submission > Number of pages: 14 > URL: http://www.ietf.org/internet-drafts/draft-zzhang- > l3vpn-mvpn-global-table-mcast-00.txt > Status: http://datatracker.ietf.org/doc/draft-zzhang-l3vpn- > mvpn-global-table-mcast > Htmlized: http://tools.ietf.org/html/draft-zzhang-l3vpn-mvpn- > global-table-mcast-00 > > > Abstract: > This document describes a way to implement Global Table Multicast, > aka Internet Multicast, using BGP encodings and procedures for MVPN > as specified in [RFC6514]. > > No protocol modification/extension is required. This is purely for > informational and clarifying purposes only. > > > > > The IETF Secretariat > > > -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
