draft-ietf-l3vpn-mvpn-mldp-nlri-07.txt   draft-ietf-l3vpn-mvpn-mldp-nlri-08.txt 
L3VPN Working Group IJsbrand Wijnands L3VPN Working Group IJsbrand Wijnands
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Intended Status: Proposed Standard Intended Status: Proposed Standard
Updates: 6514 Eric C. Rosen Updates: 6514 Eric C. Rosen
Expires: April 26, 2015 Juniper Networks, Inc. Expires: May 25, 2015 Juniper Networks, Inc.
Uwe Joorde Uwe Joorde
Deutsche Telekom Deutsche Telekom
October 26, 2014 November 25, 2014
Encoding mLDP FECs in the NLRI of BGP MCAST-VPN Routes Encoding mLDP FECs in the NLRI of BGP MCAST-VPN Routes
draft-ietf-l3vpn-mvpn-mldp-nlri-07.txt draft-ietf-l3vpn-mvpn-mldp-nlri-08.txt
Abstract Abstract
Many service providers offer "BGP/MPLS IP VPN" service to their Many service providers offer "BGP/MPLS IP VPN" service to their
customers. Existing IETF standards specify the procedures and customers. Existing IETF standards specify the procedures and
protocols that a service provider uses in order to offer this service protocols that a service provider uses in order to offer this service
to customers who have IP unicast and IP multicast traffic in their to customers who have IP unicast and IP multicast traffic in their
VPNs. It is also desirable to be able to support customers who have VPNs. It is also desirable to be able to support customers who have
MPLS multicast traffic in their VPNs. This document specifies the MPLS multicast traffic in their VPNs. This document specifies the
procedures and protocol extensions that are needed to support procedures and protocol extensions that are needed to support
skipping to change at page 3, line 17 skipping to change at page 3, line 17
customers. When a customer has IP multicast traffic in its VPN, the customers. When a customer has IP multicast traffic in its VPN, the
service provider needs to signal the customer multicast states across service provider needs to signal the customer multicast states across
the backbone. A customer with IP multicast traffic is typically the backbone. A customer with IP multicast traffic is typically
using PIM ("Protocol Independent Multicast") [PIM] and/or IGMP using PIM ("Protocol Independent Multicast") [PIM] and/or IGMP
("Internet Group Management Protocol") [IGMP] as the multicast ("Internet Group Management Protocol") [IGMP] as the multicast
control protocol in its VPN. The IP multicast states of these control protocol in its VPN. The IP multicast states of these
protocols are commonly denoted as "(S,G)" and/or "(*,G)" states, protocols are commonly denoted as "(S,G)" and/or "(*,G)" states,
where "S" is a multicast source address and "G" is a multicast group where "S" is a multicast source address and "G" is a multicast group
address. [MVPN-BGP] specifies the way an SP may use BGP to signal a address. [MVPN-BGP] specifies the way an SP may use BGP to signal a
customer's IP multicast states across the SP backbone. This is done customer's IP multicast states across the SP backbone. This is done
by using "Multiprotocol BGP" Updates whose "Subsequent Address by using "Multiprotocol BGP" Updates whose "Subsequent Address Family
Family" (SAFI) value is "MCAST-VPN" (5). The NLRI ("Network Layer Identifier" (SAFI) value is "MCAST-VPN" (5). The NLRI ("Network
Reachability Information") field of these Updates includes a customer Layer Reachability Information") field of these Updates includes a
Multicast Source field and a customer Multicast Group field, thus customer Multicast Source field and a customer Multicast Group field,
enabling the customer's (S,G) or (*,G) states to be encoded in the thus enabling the customer's (S,G) or (*,G) states to be encoded in
NLRI. the NLRI.
It is also desirable for the BGP/MPLS IP VPN service to be able to It is also desirable for the BGP/MPLS IP VPN service to be able to
support customers who are using MPLS multicast, either instead of, or support customers who are using MPLS multicast, either instead of, or
in addition to, IP multicast. This document specifies the procedures in addition to, IP multicast. This document specifies the procedures
and protocol extensions needed to support customers who use mLDP and protocol extensions needed to support customers who use mLDP
("Multicast Extensions to Label Distribution Protocol") [mLDP] to ("Multicast Extensions to Label Distribution Protocol") [mLDP] to
create and maintain Point-to-Multipoint (P2MP) and/or Multipoint-to- create and maintain Point-to-Multipoint (P2MP) and/or Multipoint-to-
Multipoint (MP2MP) Label Switched Paths (LSPs). While mLDP is not Multipoint (MP2MP) Label Switched Paths (LSPs). While mLDP is not
the only protocol that can be used to create and maintain multipoint the only protocol that can be used to create and maintain multipoint
LSPs, consideration of other MPLS multicast control protocols is LSPs, consideration of other MPLS multicast control protocols is
outside the scope of this document. outside the scope of this document.
When a customer is using mLDP in its VPN, the customer multicast When a customer is using mLDP in its VPN, the customer multicast
states associated with mLDP are denoted by an mLDP "FEC Element" states associated with mLDP are denoted by an mLDP "FEC Element"
("Forwarding Equivalance Class element", see [mLDP]), instead of by ("Forwarding Equivalence Class element", see [mLDP]), instead of by
an (S,G) or (*,G). Thus it is necessary to have a way to encode a an (S,G) or (*,G). Thus it is necessary to have a way to encode a
customer's mLDP FEC Elements in the NLRI field of the BGP MCAST-VPN customer's mLDP FEC Elements in the NLRI field of the BGP MCAST-VPN
routes. routes.
While [MVPN-BGP] does specify a way of encoding an mLDP FEC Element While [MVPN-BGP] does specify a way of encoding an mLDP FEC Element
in the MCAST-VPN NLRI field, the encoding specified therein makes a in the MCAST-VPN NLRI field, the encoding specified therein makes a
variety of restrictive assumptions about the customer's use of mLDP. variety of restrictive assumptions about the customer's use of mLDP.
(These assumptions are described in section 2 of this document.) The (These assumptions are described in section 2 of this document.) The
purpose of this document is to update [MVPN-BGP] so that customers purpose of this document is to update [MVPN-BGP] so that customers
using mLDP in their VPNs can be supported even when those assumptions using mLDP in their VPNs can be supported even when those assumptions
skipping to change at page 6, line 9 skipping to change at page 6, line 9
multicast control protocol. multicast control protocol.
This document defines three new route types: This document defines three new route types:
- C-Multicast Source Tree Join route for C-multicast mLDP - C-Multicast Source Tree Join route for C-multicast mLDP
- S-PMSI A-D route for C-multicast mLDP - S-PMSI A-D route for C-multicast mLDP
- Leaf A-D route for C-multicast mLDP. - Leaf A-D route for C-multicast mLDP.
The term "C-multicast mLDP" in the names of these route types is The term "C-multicast mLDP" in the names of these route types is
intended to indicate that the NLRI of these route contains mLDP FEC intended to indicate that the NLRI of these routes contains mLDP FEC
elements. elements.
Each of these route types corresponds to a route type defined in Each of these route types corresponds to a route type defined in
[MVPN-BGP]. IANA has been requested to allocate codepoints for these [MVPN-BGP]. IANA has been requested to allocate codepoints for these
three route types such that (a) the high order two bits have the three route types such that (a) the high order two bits have the
value 0x01, and (b) the low order bit six bits have the same value as value 0x01, and (b) the low order bit six bits have the same value as
the codepoints for the corresponding route types from [MVPN-BGP]. the codepoints for the corresponding route types from [MVPN-BGP].
In general, the procedures defined in other MVPN specifications for In general, the procedures defined in other MVPN specifications for
the C-Multicast Source Tree Join route, the S-PMSI A-D route, and the the C-Multicast Source Tree Join route, the S-PMSI A-D route, and the
skipping to change at page 7, line 49 skipping to change at page 7, line 49
control protocol is outside the scope of this document. control protocol is outside the scope of this document.
5. IANA Considerations 5. IANA Considerations
[MVPN-BGP] does not create a registry for the allocation of new [MVPN-BGP] does not create a registry for the allocation of new
MCAST-VPN Route Type values. In retrospect, it seems that it should MCAST-VPN Route Type values. In retrospect, it seems that it should
have done so. IANA is requested to create a new registry called "BGP have done so. IANA is requested to create a new registry called "BGP
MCAST-VPN Route Types", referencing this document and [MVPN-BGP]. MCAST-VPN Route Types", referencing this document and [MVPN-BGP].
The registry should be created under the "top-level" registry: The registry should be created under the "top-level" registry:
"Border Gateway Protocol (BGP) Parameters "Border Gateway Protocol (BGP) Parameters
http://www.iana.org/assignments/bgp-parameters/bgp-parameters.xhtml". http://www.iana.org/assignments/bgp-parameters/bgp-parameters". The
The allocation policy should be "Standards Action". Values may be allocation policy should be "Standards Action". Values may be
assigned from one of several ranges: assigned from one of several ranges:
- Range 0x01-0x3f: Generic/PIM Range. Values are assigned from - Range 0x01-0x3f: Generic/PIM Range. Values are assigned from
this range when the NLRI format associated with the route type this range when the NLRI format associated with the route type
presupposes that PIM or IGMP is the C-multicast control protocol, presupposes that PIM or IGMP is the C-multicast control protocol,
or when the the NLRI format associated with the route type is or when the NLRI format associated with the route type is
independent of the C-multicast control protocol. independent of the C-multicast control protocol.
- Range 0x41-0x7f: mLDP Range. Values are assigned from this range - Range 0x43-0x7f: mLDP Range. Values are assigned from this range
when the NLRI format associated with the route type presupposes when the NLRI format associated with the route type presupposes
that mLDP is the C-multicast control protocol. that mLDP is the C-multicast control protocol.
- Range 0x80-0xff: This range is reserved; values should not be - Range 0x80-0xff: This range is reserved; values should not be
assigned from this range. assigned from this range.
In general, whenever an assignment is requested from this registry, In general, whenever an assignment is requested from this registry,
two codepoints should be requested at the same time: one from the two codepoints should be requested at the same time: one from the
Generic/PIM range and one from the mLDP range. The two codepoints Generic/PIM range and one from the mLDP range. The two codepoints
should have the same low-order 5 bits. If one of the two codepoints should have the same low-order 5 bits. If one of the two codepoints
skipping to change at page 11, line 20 skipping to change at page 11, line 20
[MVPN-BGP] "BGP Encodings and Procedures for Multicast in MPLS/BGP IP [MVPN-BGP] "BGP Encodings and Procedures for Multicast in MPLS/BGP IP
VPNs", Aggarwal, Rosen, Morin, Rekhter, RFC 6514, February 2012 VPNs", Aggarwal, Rosen, Morin, Rekhter, RFC 6514, February 2012
[RFC2119] "Key words for use in RFCs to Indicate Requirement [RFC2119] "Key words for use in RFCs to Indicate Requirement
Levels.", Bradner, RFC 2119, March 1997 Levels.", Bradner, RFC 2119, March 1997
10. Informative References 10. Informative References
[BGP-ERR] "Revised Error Handling for BGP UPDATE Messages", Chen, [BGP-ERR] "Revised Error Handling for BGP UPDATE Messages", Chen,
Scudder, Mohapatra, Patel, draft-ietf-idr-error-handling-15.txt, Scudder, Mohapatra, Patel, draft-ietf-idr-error-handling-16.txt,
October 2014 November 2014
[GTM] "Global Table Multicast with BGP-MVPN Procedures", Zhang, [GTM] "Global Table Multicast with BGP-MVPN Procedures", Zhang,
Giuliano, Rosen, Subramanian, Pacella, Schiller, draft-ietf-l3vpn- Giuliano, Rosen, Subramanian, Pacella, Schiller, draft-ietf-l3vpn-
mvpn-global-table-mcast-00.txt, June 2014 mvpn-global-table-mcast-00.txt, June 2014
[IGMP] "Internet Group Management Protocol, Version 3", Cain, [IGMP] "Internet Group Management Protocol, Version 3", Cain,
Deering, Kouvelas, Fenner, Thyagarajan, RFC 3376, October 2002 Deering, Kouvelas, Fenner, Thyagarajan, RFC 3376, October 2002
[LDP-MT] "LDP Extensions for Multi-Topology", Zhao, et. al., RFC [LDP-MT] "LDP Extensions for Multi-Topology", Zhao, et. al., RFC
7307, July 2014 7307, July 2014
 End of changes. 10 change blocks. 
17 lines changed or deleted 17 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/