draft-ietf-mpls-pim-sm-over-mldp-00.txt   draft-ietf-mpls-pim-sm-over-mldp-01.txt 
Network Working Group Yakov Rekhter Network Working Group Yakov Rekhter
Internet Draft Juniper Networks Internet Draft Juniper Networks
Intended status: Standards Track Intended status: Standards Track
Expires: September 2014 Rahul Aggarwal Expires: March 2015 Rahul Aggarwal
Arktan Arktan
Nicolai Leymann Nicolai Leymann
Deutsche Telekom Deutsche Telekom
Wim Henderickx Wim Henderickx
Alcatel-Lucent Alcatel-Lucent
Quintin Zhao Quintin Zhao
Huawei Huawei
Richard Li Richard Li
Huawei Huawei
March 4 2014 September 8 2014
Carrying PIM-SM in ASM mode Trees over P2MP mLDP LSPs Carrying PIM-SM in ASM mode Trees over P2MP mLDP LSPs
draft-ietf-mpls-pim-sm-over-mldp-00.txt draft-ietf-mpls-pim-sm-over-mldp-01.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 2, line 7 skipping to change at page 2, line 7
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2015 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
skipping to change at page 3, line 7 skipping to change at page 3, line 7
Abstract Abstract
When IP multicast trees created by PIM-SM in Any Source Multicast When IP multicast trees created by PIM-SM in Any Source Multicast
(ASM) mode need to pass through an MPLS domain, it may be desirable (ASM) mode need to pass through an MPLS domain, it may be desirable
to map such trees to Point-to-Multipoint Label Switched Paths. This to map such trees to Point-to-Multipoint Label Switched Paths. This
document describes how to accomplish this in the case where such document describes how to accomplish this in the case where such
Point-to-Multipoint Label Switched Paths are established using mLDP. Point-to-Multipoint Label Switched Paths are established using mLDP.
Table of Contents Table of Contents
1 Specification of Requirements ......................... 3 1 Specification of Requirements ......................... 3
2 Introduction .......................................... 3 2 Introduction .......................................... 3
3 Option 1 - Non-transitive mapping of IP multicast shared tree 5 3 Option 1 - Non-transitive mapping of IP multicast shared tree 5
3.1 Originating Source Active auto-discovery routes (Option 1) 5 3.1 Originating Source Active auto-discovery routes (Option 1) 5
3.2 Receiving BGP Source Active auto-discovery route by LSR ...6 3.2 Receiving BGP Source Active auto-discovery route by LSR ...6
3.3 Handling (S, G, RPT-bit) state ........................ 6 3.3 Handling (S, G, RPT-bit) state ........................ 6
4 Option 2 - Transitive mapping of IP multicast shared tree .6 4 Option 2 - Transitive mapping of IP multicast shared tree .6
4.1 In-band signaling for IP Multicast Shared Tree ........ 7 4.1 In-band signaling for IP Multicast Shared Tree ........ 7
4.2 Originating Source Active auto-discovery routes (Option 2) 8 4.2 Originating Source Active auto-discovery routes (Option 2) 8
4.3 Receiving BGP Source Active auto-discovery route ...... 9 4.3 Receiving BGP Source Active auto-discovery route ...... 9
4.4 Pruning Sources off the Shared Tree ................... 9 4.4 Pruning Sources off the Shared Tree ................... 9
4.5 More on handling (S,G,RPT-bit) state .................. 10 4.5 More on handling (S,G,RPT-bit) state .................. 10
5 IANA Considerations ................................... 10 5 IANA Considerations ................................... 10
6 Security Considerations ............................... 10 6 Security Considerations ............................... 10
7 Acknowledgements ...................................... 10 7 Acknowledgements ...................................... 10
8 Normative References .................................. 11 8 Normative References .................................. 11
9 Informative References ................................ 11 9 Informative References ................................ 11
10 Authors' Addresses .................................... 11 10 Authors' Addresses .................................... 11
1. Specification of Requirements 1. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Introduction 2. Introduction
[RFC6826] describes how to map Point-to-Multipoint Label Switched [RFC6826] describes how to map Point-to-Multipoint Label Switched
skipping to change at page 7, line 16 skipping to change at page 7, line 16
To provide support for in-band mLDP signaling of IP multicast shared To provide support for in-band mLDP signaling of IP multicast shared
trees this document defines two new mLDP TLVs: Transit IPv4 Shared trees this document defines two new mLDP TLVs: Transit IPv4 Shared
Tree TLV, and Transit IPv6 Shared Tree TLV. Tree TLV, and Transit IPv6 Shared Tree TLV.
These two TLVs have exactly the same encoding/format as the IPv4/IPv6 These two TLVs have exactly the same encoding/format as the IPv4/IPv6
Source Tree TLVs defined in [RFC6826], except that instead of the Source Tree TLVs defined in [RFC6826], except that instead of the
Source field they have the RP field, and this field carries the Source field they have the RP field, and this field carries the
address of the RP, as follows: address of the RP, as follows:
Transit IPv4 Shared Tree TLV: Transit IPv4 Shared Tree TLV:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | RP | Type | Length | RP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Group | Group
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: TBD (to be assigned by IANA). Type: TBD (to be assigned by IANA).
Length: 8 Length: 8
RP: IPv4 RP address, 4 octets. RP: IPv4 RP address, 4 octets.
Group: IPv4 multicast group address, 4 octets. Group: IPv4 multicast group address, 4 octets.
Transit IPv6 Shared Tree TLV: Transit IPv6 Shared Tree TLV:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | RP ~ | Type | Length | RP ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ | Group ~ ~ | Group ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ | ~ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: TBD (to be assigned by IANA). Type: TBD (to be assigned by IANA).
Length: 32 Length: 32
RP: IPv6 RP address, 16 octets. RP: IPv6 RP address, 16 octets.
Group: IPv6 multicast group address, 16 octets. Group: IPv6 multicast group address, 16 octets.
Procedures for in-band signaling for IP multicast shared trees with Procedures for in-band signaling for IP multicast shared trees with
mLDP follow the same procedures as for in-band signaling for IP mLDP follow the same procedures as for in-band signaling for IP
multicast source trees specified in [RFC6826], except that while the multicast source trees specified in [RFC6826], except that while the
latter signals (S,G) state using Transit IPv4/IPv6 Source TLVs, the latter signals (S,G) state using Transit IPv4/IPv6 Source TLVs, the
former signals (*,G) state using Transit IPv4/IPv6 Shared Tree TLVs. former signals (*,G) state using Transit IPv4/IPv6 Shared Tree TLVs.
4.2. Originating Source Active auto-discovery routes (Option 2) 4.2. Originating Source Active auto-discovery routes (Option 2)
Consider an LSR that has some of its interfaces capable of IP Consider an LSR that has some of its interfaces capable of IP
skipping to change at page 11, line 34 skipping to change at page 11, line 34
9. Informative References 9. Informative References
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol
Specification (Revised)", RFC 4601, August 2006. Specification (Revised)", RFC 4601, August 2006.
[RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for [RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for
IP", RFC 4607, August 2006. IP", RFC 4607, August 2006.
[draft-wijnands] Wijnands IJ, et. al., "mLDP In-Band Signaling with [draft-wijnands] Wijnands IJ, et. al., "mLDP In-Band Signaling with
Wildcards", draft-wijnands-mpls-mldp-in-band-wildcard-encoding, work Wildcards", draft-ietf-mpls-mldp-in-band-wildcard-encoding, work in
in progress progress
10. Authors' Addresses 10. Authors' Addresses
Yakov Rekhter Yakov Rekhter
Juniper Networks, Inc. Juniper Networks, Inc.
e-mail: yakov@juniper.net e-mail: yakov@juniper.net
Rahul Aggarwal Rahul Aggarwal
e-mail: raggarwa_1@yahoo.com e-mail: raggarwa_1@yahoo.com
 End of changes. 18 change blocks. 
52 lines changed or deleted 52 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/