draft-wijnands-mpls-mldp-in-band-wildcard-encoding-02.txt   draft-wijnands-mpls-mldp-in-band-wildcard-encoding-03.txt 
MPLS Working Group IJ. Wijnands, Ed. MPLS Working Group IJ. Wijnands, Ed.
Internet-Draft E. Rosen Internet-Draft E. Rosen
Intended status: Standards Track Cisco Intended status: Standards Track Cisco
Expires: June 9, 2014 A. Gulko Expires: July 12, 2014 A. Gulko
Thomson Reuters Thomson Reuters
U. Joorde U. Joorde
Deutsche Telekom Deutsche Telekom
J. Tantsura J. Tantsura
Ericsson Ericsson
December 6, 2013 January 8, 2014
mLDP In-Band Signaling with Wildcards mLDP In-Band Signaling with Wildcards
draft-wijnands-mpls-mldp-in-band-wildcard-encoding-02 draft-wijnands-mpls-mldp-in-band-wildcard-encoding-03
Abstract Abstract
There are scenarios in which an IP multicast tree traverses an MPLS There are scenarios in which an IP multicast tree traverses an MPLS
domain. In these scenarios, it can be desirable to convert the IP domain. In these scenarios, it can be desirable to convert the IP
multicast tree "seamlessly" to an MPLS multipoint label switched path multicast tree "seamlessly" to an MPLS multipoint label switched path
(MP-LSP) when it enters the MPLS domain, and then to convert it back (MP-LSP) when it enters the MPLS domain, and then to convert it back
to an IP multicast tree when it exits the MPLS domain. Previous to an IP multicast tree when it exits the MPLS domain. Previous
documents specify procedures that allow certain kinds of IP multicast documents specify procedures that allow certain kinds of IP multicast
trees (either "Source-Specific Multicast" trees or "Bidirectional trees (either "Source-Specific Multicast" trees or "Bidirectional
skipping to change at page 2, line 7 skipping to change at page 2, line 7
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 9, 2014. This Internet-Draft will expire on July 12, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Definitions . . . . . . . . . . . . . . . . . 5 2. Terminology and Definitions . . . . . . . . . . . . . . . . . 5
3. Wildcards in mLDP Opaque Value TLVs . . . . . . . . . . . . . 6 3. Wildcards in mLDP Opaque Value TLVs . . . . . . . . . . . . . 7
3.1. Encoding the Wildcards . . . . . . . . . . . . . . . . . 7 3.1. Encoding the Wildcards . . . . . . . . . . . . . . . . . 7
3.2. Wildcard Semantics . . . . . . . . . . . . . . . . . . . 7 3.2. Wildcard Semantics . . . . . . . . . . . . . . . . . . . 7
3.3. Backwards Compatibility . . . . . . . . . . . . . . . . . 8 3.3. Backwards Compatibility . . . . . . . . . . . . . . . . . 8
3.4. Applicability Restrictions with regard to ASM . . . . . . 8 3.4. Applicability Restrictions with regard to ASM . . . . . . 8
4. Some Wildcard Use Cases . . . . . . . . . . . . . . . . . . . 9 4. Some Wildcard Use Cases . . . . . . . . . . . . . . . . . . . 9
4.1. PIM shared tree forwarding . . . . . . . . . . . . . . . 9 4.1. PIM shared tree forwarding . . . . . . . . . . . . . . . 9
4.2. IGMP/MLD Proxying . . . . . . . . . . . . . . . . . . . . 10 4.2. IGMP/MLD Proxying . . . . . . . . . . . . . . . . . . . . 10
4.3. Selective Source mapping . . . . . . . . . . . . . . . . 10 4.3. Selective Source mapping . . . . . . . . . . . . . . . . 11
5. Procedures for Wildcard Source Usage . . . . . . . . . . . . 11 5. Procedures for Wildcard Source Usage . . . . . . . . . . . . 11
6. Procedures for Wildcard Group Usage . . . . . . . . . . . . . 12 6. Procedures for Wildcard Group Usage . . . . . . . . . . . . . 12
7. Determining the MP-LSP Root (Ingress LSR) . . . . . . . . . . 12 7. Determining the MP-LSP Root (Ingress LSR) . . . . . . . . . . 13
8. Anycast RP . . . . . . . . . . . . . . . . . . . . . . . . . 13 8. Anycast RP . . . . . . . . . . . . . . . . . . . . . . . . . 13
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
11. Security Considerations . . . . . . . . . . . . . . . . . . . 13 11. Security Considerations . . . . . . . . . . . . . . . . . . . 13
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
12.1. Normative References . . . . . . . . . . . . . . . . . . 13 12.1. Normative References . . . . . . . . . . . . . . . . . . 13
12.2. Informative References . . . . . . . . . . . . . . . . . 14 12.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
[RFC6826] and [I-D.ietf-l3vpn-mldp-vrf-in-band-signaling] specify [RFC6826] and [I-D.ietf-l3vpn-mldp-vrf-in-band-signaling] specify
procedures for mLDP ("Multicast Extensions to the Label Distribution procedures for mLDP ("Multicast Extensions to the Label Distribution
Protocol") that allow an IP multicast tree (either a "Source-Specific Protocol") that allow an IP multicast tree (either a "Source-Specific
Multicast" tree or a "Bidirectional multicast" tree) to be attached Multicast" tree or a "Bidirectional multicast" tree) to be attached
"seamlessly" to an MPLS Multipoint Label Switched Path (MP-LSP). "seamlessly" to an MPLS Multipoint Label Switched Path (MP-LSP).
This can be useful, for example, when there is multicast data that This can be useful, for example, when there is multicast data that
originates in a domain that supports IP multicast, then has to be originates in a domain that supports IP multicast, then has to be
skipping to change at page 7, line 30 skipping to change at page 7, line 37
3.2. Wildcard Semantics 3.2. Wildcard Semantics
If the IP Source Address sub-field contains the wildcard, and the IP If the IP Source Address sub-field contains the wildcard, and the IP
Group Address sub-field contains an IP multicast group address that Group Address sub-field contains an IP multicast group address that
is NOT in the SSM address range (see Section 4.8 of [RFC4601]), the is NOT in the SSM address range (see Section 4.8 of [RFC4601]), the
TLV identifies a PIM-SM shared tree. Please see Section 3.4 for the TLV identifies a PIM-SM shared tree. Please see Section 3.4 for the
applicability restrictions that apply to this case. applicability restrictions that apply to this case.
If the IP Source Address sub-field contains the wildcard, and the IP If the IP Source Address sub-field contains the wildcard, and the IP
Group Address sub-field contains an IP multicast group address that Group Address sub-field contains an IP multicast group address that
is in the SSM address range, the TLV identifies the collection of is in the SSM address range, the TLV identifies the collection of PIM
PIM-SSM trees with the given group address. trees with the given group address.
If the IP Source Address sub-field contains a non-zero IP address, If the IP Source Address sub-field contains a non-zero IP address,
and the IP Group Address sub-field contains the wildcard, the TLV and the IP Group Address sub-field contains the wildcard, the TLV
identifies the collection of PIM-SSM trees that have the source identifies the collection of PIM-SSM trees that have the source
address as their root. address as their root.
Procedures for the use of the wildcards are discussed in Sections 4, Procedures for the use of the wildcards are discussed in Sections 4,
5 and 6. Please note that, as always, the structure of the Opaque 5 and 6. Please note that, as always, the structure of the Opaque
Value TLVs does not actually affect the operation of mLDP, but only Value TLVs does not actually affect the operation of mLDP, but only
affects the interface between mLDP and IP multicast at the Ingress affects the interface between mLDP and IP multicast at the Ingress
skipping to change at page 14, line 25 skipping to change at page 14, line 35
"Multipoint LDP In-Band Signaling for Point-to-Multipoint "Multipoint LDP In-Band Signaling for Point-to-Multipoint
and Multipoint-to-Multipoint Label Switched Paths", RFC and Multipoint-to-Multipoint Label Switched Paths", RFC
6826, January 2013. 6826, January 2013.
12.2. Informative References 12.2. Informative References
[I-D.zzhang-l3vpn-mvpn-global-table-mcast] [I-D.zzhang-l3vpn-mvpn-global-table-mcast]
Zhang, J., Giuliano, L., Rosen, E., Subramanian, K., Zhang, J., Giuliano, L., Rosen, E., Subramanian, K.,
Pacella, D., and J. Schiller, "Global Table Multicast with Pacella, D., and J. Schiller, "Global Table Multicast with
BGP-MVPN Procedures", draft-zzhang-l3vpn-mvpn-global- BGP-MVPN Procedures", draft-zzhang-l3vpn-mvpn-global-
table-mcast-01 (work in progress), October 2013. table-mcast-02 (work in progress), December 2013.
[RFC3446] Kim, D., Meyer, D., Kilmer, H., and D. Farinacci, "Anycast [RFC3446] Kim, D., Meyer, D., Kilmer, H., and D. Farinacci, "Anycast
Rendevous Point (RP) mechanism using Protocol Independent Rendevous Point (RP) mechanism using Protocol Independent
Multicast (PIM) and Multicast Source Discovery Protocol Multicast (PIM) and Multicast Source Discovery Protocol
(MSDP)", RFC 3446, January 2003. (MSDP)", RFC 3446, January 2003.
[RFC3618] Fenner, B. and D. Meyer, "Multicast Source Discovery [RFC3618] Fenner, B. and D. Meyer, "Multicast Source Discovery
Protocol (MSDP)", RFC 3618, October 2003. Protocol (MSDP)", RFC 3618, October 2003.
[RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, [RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
 End of changes. 12 change blocks. 
13 lines changed or deleted 13 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/