draft-ietf-mpls-seamless-mcast-03.txt   draft-ietf-mpls-seamless-mcast-04.txt 
Network Working Group Y. Rekhter Network Working Group Y. Rekhter
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: June 2012 Expiration Date: November 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
December 7 2011 May 30 2012
Inter-Area P2MP Segmented LSPs Inter-Area P2MP Segmented LSPs
draft-ietf-mpls-seamless-mcast-03.txt draft-ietf-mpls-seamless-mcast-04.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 23 skipping to change at page 4, line 23
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 ............................... 35 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 ................................ 36 17.2 Informative References ................................ 36
18 Author's Address ...................................... 37 18 Author's Address ...................................... 37
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
This document describes procedures for building inter-area point-to- This document describes procedures for building inter-area point-to-
skipping to change at page 19, line 40 skipping to change at page 19, line 40
last Leaf auto-discovery route for the Route Prefix then the last Leaf auto-discovery route for the Route Prefix then the
following procedures will be executed. following procedures will be executed.
While generating a Leaf auto-discovery route update, the egress ABR While generating a Leaf auto-discovery route update, the egress ABR
originates a Leaf auto-discovery route, whose MCAST-VPN NLRI is originates a Leaf auto-discovery route, whose MCAST-VPN NLRI is
constructed as follows. constructed as follows.
The Route Key field of MCAST-VPN NLRI is the same as the Route Key The Route Key field of MCAST-VPN NLRI is the same as the Route Key
field of MCAST-VPN NLRI of the received Leaf auto-discovery route. field of MCAST-VPN NLRI of the received Leaf auto-discovery route.
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 ABR (the ABR that originates the route). In the address of the local ABR (the ABR that originates the route).
The Next Hop field of the MP_REACH_NLRI attribute of the route SHOULD The Next Hop field of the MP_REACH_NLRI attribute of the route SHOULD
be set to the same IP address as the one carried in the Originating be set to the same IP address as the one carried in the Originating
Router's IP Address field of the route. Router's IP Address field of the route.
To constrain distribution of this route the originating egress ABR To constrain distribution of this route the originating egress ABR
constructs an IP-based Route Target community by placing the IP constructs an IP-based Route Target community by placing the IP
address of the upstream node in the Global Administrator field of the address of the upstream node in the Global Administrator field of the
community, with the Local Administrator field of this community set community, with the Local Administrator field of this community set
to 0, and sets the Extended Communities attribute of this Leaf auto- to 0, and sets the Extended Communities attribute of this Leaf auto-
skipping to change at page 32, line 41 skipping to change at page 32, line 41
RD (8 octets) - set to 0 RD (8 octets) - set to 0
Multicast Source Length, Multicast Source - constructed from Multicast Source Length, Multicast Source - constructed from
the Source PE address part of the Tunnel Identifier carried the Source PE address part of the Tunnel Identifier carried
in the received S-PMSI auto-discovery route. in the received S-PMSI auto-discovery route.
Multicast Group Length, Multicast Group - constructed from Multicast Group Length, Multicast Group - constructed from
Local Number part of the Tunnel Identifier carried in the Local Number part of the Tunnel Identifier carried in the
received S-PMSI auto-discovery route. received S-PMSI auto-discovery route.
Ingress PE IP Address is constructed from the Source PE Ingress PE IP Address is set to the Source PE address part
address part of the Tunnel Identifier carried in the of the Tunnel Identifier carried in the received S-PMSI
received S-PMSI auto-discovery route. auto-discovery route.
The egress PE, when determining the upstream ABR, follows the The egress PE, when determining the upstream ABR, follows the
procedures specified in Section 6.1 for global table multicast. procedures specified in Section 6.1 for global table multicast.
From that point on we follow the procedures used for the Leaf auto- From that point on we follow the procedures used for the Leaf auto-
discovery routes for global table multicast, as outlined below. discovery routes for global table multicast, as outlined below.
13.5. Egress ABR, Ingress ABR, Ingress PE procedures for Inter-Area 13.5. Egress ABR, Ingress ABR, Ingress PE procedures for Inter-Area
Transport LSP" Transport LSP"
 End of changes. 6 change blocks. 
8 lines changed or deleted 7 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/