draft-ietf-mpls-seamless-mcast-02.txt   draft-ietf-mpls-seamless-mcast-03.txt 
Network Working Group Y. Rekhter Network Working Group Y. Rekhter
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: May 2012 Expiration Date: June 2012
R. Aggarwal R. Aggarwal
T. Morin T. Morin
France Telecom France Telecom
I. Grosclaude I. Grosclaude
France Telecom France Telecom
N. Leymann N. Leymann
Deutsche Telekom AG Deutsche Telekom AG
S. Saad S. Saad
AT&T AT&T
November 16, 2011 December 7 2011
Inter-Area P2MP Segmented LSPs Inter-Area P2MP Segmented LSPs
draft-ietf-mpls-seamless-mcast-02.txt draft-ietf-mpls-seamless-mcast-03.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 4, line 17 skipping to change at page 4, line 17
12.3 Data Plane Procedures on an Ingress PE ................ 30 12.3 Data Plane Procedures on an Ingress PE ................ 30
12.4 Data Plane Procedures on Transit Routers .............. 30 12.4 Data Plane Procedures on Transit Routers .............. 30
13 Support for Inter-Area Transport LSPs ................. 30 13 Support for Inter-Area Transport LSPs ................. 30
13.1 Transport Tunnel Tunnel Type .......................... 31 13.1 Transport Tunnel Tunnel Type .......................... 31
13.2 Discovering Leaves of the Inter-Area P2MP Service LSP . 31 13.2 Discovering Leaves of the Inter-Area P2MP Service LSP . 31
13.3 Discovering the P2MP FEC of the Inter-Area P2MP Transport LSP 31 13.3 Discovering the P2MP FEC of the Inter-Area P2MP Transport LSP 31
13.4 Egress PE Procedures for Inter-Area P2MP Transport LSP ....32 13.4 Egress PE Procedures for Inter-Area P2MP Transport LSP ....32
13.5 Egress ABR, Ingress ABR, Ingress PE procedures for Inter-Area 33 13.5 Egress ABR, Ingress ABR, Ingress PE procedures for Inter-Area 33
13.6 Discussion ............................................ 33 13.6 Discussion ............................................ 33
14 IANA Considerations ................................... 35 14 IANA Considerations ................................... 35
15 Security Considerations ............................... 36 15 Security Considerations ............................... 35
16 Acknowledgements ...................................... 36 16 Acknowledgements ...................................... 36
17 References ............................................ 36 17 References ............................................ 36
17.1 Normative References .................................. 36 17.1 Normative References .................................. 36
17.2 Informative References ................................ 37 17.2 Informative References ................................ 36
18 Author's Address ...................................... 37 18 Author's Address ...................................... 37
seamless-mcast.nroff:1820: warning: macro `.' not defined seamless-mcast.nroff:1820: warning: macro `.' not defined
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
skipping to change at page 13, line 23 skipping to change at page 13, line 23
The Ingress PE's IP address is determined as described in the section The Ingress PE's IP address is determined as described in the section
"Determining the Upstream ABR/PE/ASBR". "Determining the Upstream ABR/PE/ASBR".
The Originating Router's IP address field of MCAST-VPN NLRI is set to The Originating Router's IP address field of MCAST-VPN NLRI is set to
the address of the local PE (PE that originates the route). the address of the local PE (PE that originates the route).
Thus the entire MCAST-VPN NLRI of the route has the following format: Thus the entire MCAST-VPN NLRI of the route has the following format:
+-----------------------------------+ +-----------------------------------+
| Route Type = 5 (1 octet) | | Route Type = 4 (1 octet) |
+-----------------------------------+ +-----------------------------------+
| Length (1 octet) | | Length (1 octet) |
+-----------------------------------+ +-----------------------------------+
| RD (8 octets) | | RD (8 octets) |
+-----------------------------------+ +-----------------------------------+
| Multicast Source Length (1 octet) | | Multicast Source Length (1 octet) |
+-----------------------------------+ +-----------------------------------+
| Multicast Source (Variable) | | Multicast Source (Variable) |
+-----------------------------------+ +-----------------------------------+
| Multicast Group Length (1 octet) | | Multicast Group Length (1 octet) |
 End of changes. 6 change blocks. 
6 lines changed or deleted 6 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/