draft-ietf-l3vpn-mvpn-mldp-nlri-08.txt   draft-ietf-l3vpn-mvpn-mldp-nlri-09.txt 
skipping to change at page 1, line 16 skipping to change at page 1, line 16
Updates: 6514 Eric C. Rosen Updates: 6514 Eric C. Rosen
Expires: May 25, 2015 Juniper Networks, Inc. Expires: May 25, 2015 Juniper Networks, Inc.
Uwe Joorde Uwe Joorde
Deutsche Telekom Deutsche Telekom
November 25, 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-08.txt draft-ietf-l3vpn-mvpn-mldp-nlri-09.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 6, line 15 skipping to change at page 6, line 15
- 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 routes 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 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
Leaf A-D route apply as well to the C-Multicast Source Tree Join Leaf A-D route apply as well to the C-Multicast Source Tree Join
route for C-multicast mLDP, the S-PMSI A-D route for C-multicast route for C-multicast mLDP, the S-PMSI A-D route for C-multicast
mLDP, and the Leaf A-D route for C-multicast mLDP, respectively. mLDP, and the Leaf A-D route for C-multicast mLDP, respectively.
However, the NLRI of these three new route types is constructed However, the NLRI of these three new route types is constructed
differently than the NLRI of the corresponding routes from [MVPN- differently than the NLRI of the corresponding routes from [MVPN-
BGP]: the "Multicast Source Length", "Multicast Source", "Multicast BGP]: the "Multicast Source Length", "Multicast Source", "Multicast
skipping to change at page 8, line 22 skipping to change at page 8, line 22
- Range 0x43-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 6 bits. If one of the two codepoints
is not actually needed, it should be registered anyway, and marked as is not actually needed, it should be registered anyway, and marked as
"reserved". "reserved".
When the BGP MCAST-VPN Route Types registry is created, it should When the BGP MCAST-VPN Route Types registry is created, it should
contain the following assignments: contain the following assignments:
Value Meaning Reference Value Meaning Reference
0x00 Reserved This RFC 0x00 Reserved This RFC
0x01 Intra-AS I-PMSI A-D route This RFC, RFC6514 0x01 Intra-AS I-PMSI A-D route This RFC, RFC6514
 End of changes. 3 change blocks. 
3 lines changed or deleted 3 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/