draft-ietf-pim-rpf-vector-06.txt   draft-ietf-pim-rpf-vector-07.txt 
PIM WG IJ. Wijnands PIM WG IJ. Wijnands
Internet-Draft A. Boers Internet-Draft A. Boers
Intended status: Informational E. Rosen Intended status: Standards Track E. Rosen
Expires: August 25, 2008 Cisco Systems, Inc. Expires: July 9, 2009 Cisco Systems, Inc.
February 22, 2008 January 5, 2009
The RPF Vector TLV The RPF Vector TLV
draft-ietf-pim-rpf-vector-06 draft-ietf-pim-rpf-vector-07
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of 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 Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
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.
This Internet-Draft will expire on August 25, 2008. This Internet-Draft will expire on July 9, 2009.
Copyright Notice
Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document describes a use of the PIM Join Attribute as defined in This document describes a use of the PIM Join Attribute as defined in
draft-ietf-pim-join-attributes [I-D.ietf-pim-join-attributes] which draft-ietf-pim-join-attributes [RFC5384] which enables PIM to build
enables PIM to build multicast trees through an MPLS-enabled network, multicast trees through an MPLS-enabled network, even if that
even if that network's IGP does not have a route to the source of the network's IGP does not have a route to the source of the tree.
tree.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Use of the RPF Vector TLV . . . . . . . . . . . . . . . . . . 4 2. Use of the RPF Vector TLV . . . . . . . . . . . . . . . . . . 4
2.1. Attribute and shared tree joins . . . . . . . . . . . . . 4 2.1. Attribute and shared tree joins . . . . . . . . . . . . . 4
2.2. Attribute and Bootstrap messages . . . . . . . . . . . . . 5 2.2. Attribute and Bootstrap messages . . . . . . . . . . . . . 5
2.3. The Vector Attribute . . . . . . . . . . . . . . . . . . . 5 2.3. The Vector Attribute . . . . . . . . . . . . . . . . . . . 5
2.3.1. Inserting a Vector Attribute in a Join . . . . . . . . 5 2.3.1. Inserting a Vector Attribute in a Join . . . . . . . . 5
2.3.2. Processing a Received Vector Attribute . . . . . . . . 5 2.3.2. Processing a Received Vector Attribute . . . . . . . . 5
skipping to change at page 3, line 51 skipping to change at page 3, line 51
In order to allow PIM to work properly in an environment where the In order to allow PIM to work properly in an environment where the
core routers do not maintain external routes, a PIM extension is core routers do not maintain external routes, a PIM extension is
needed. When an edge router sends a PIM Join message into the core, needed. When an edge router sends a PIM Join message into the core,
it must include in that message a "Vector" which specifies the IP it must include in that message a "Vector" which specifies the IP
address of the next edge router along the path to the root of the address of the next edge router along the path to the root of the
multicast distribution tree. The core routers can then process the multicast distribution tree. The core routers can then process the
Join message by sending it towards the specified edge router (i.e., Join message by sending it towards the specified edge router (i.e.,
toward the Vector). In effect, the Vector serves as an attribute, toward the Vector). In effect, the Vector serves as an attribute,
within a particular network, for the root of the tree. within a particular network, for the root of the tree.
This document defines a new TLV in the PIM Join Attribute This document defines a new TLV in the PIM Join Attribute message
message[I-D.ietf-pim-join-attributes]. It consists of a single [RFC5384]. It consists of a single Vector which identifies the exit
Vector which identifies the exit point of the network. point of the network.
2. Use of the RPF Vector TLV 2. Use of the RPF Vector TLV
Before we can start forwarding multicast packets we need to build a Before we can start forwarding multicast packets we need to build a
forwarding tree by sending PIM Joins hop by hop. Each router in the forwarding tree by sending PIM Joins hop by hop. Each router in the
path creates a forwarding state and propagates the Join towards the path creates a forwarding state and propagates the Join towards the
root of the forwarding tree. The building of this tree is receiver root of the forwarding tree. The building of this tree is receiver
driven. See Figure 1. driven. See Figure 1.
------------------ BGP ----------------- ------------------ BGP -----------------
skipping to change at page 7, line 38 skipping to change at page 7, line 38
Length Length
------ ------
Length depending on Address Family of Encoded-Unicast address. Length depending on Address Family of Encoded-Unicast address.
Value Value
----- -----
Encoded-Unicast address. Encoded-Unicast address.
4. IANA Considerations 4. IANA Considerations
An attribute type needs to be assigned. For now we propose the value An new attribute type from the "PIM Join Attribute Types" registry
0. needs to be assigned by IANA for the RPF Vector. The propose value
is 0.
5. Security Considerations 5. Security Considerations
Security of the RPF Vector Attribute is only guaranteed by the Security of the RPF Vector Attribute is only guaranteed by the
security of the PIM packet, so the security considerations for PIM security of the PIM packet, so the security considerations for PIM
join packets as described in PIM-SM [RFC4601] apply here. join packets as described in PIM-SM [RFC4601] apply here.
6. Acknowledgments 6. Acknowledgments
The authors would like to thank Yakov Rekhter and Dino Farinacci for The authors would like to thank Yakov Rekhter and Dino Farinacci for
skipping to change at page 8, line 26 skipping to change at page 8, line 26
"Protocol Independent Multicast - Sparse Mode (PIM-SM): "Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, August 2006. Protocol 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.
[RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, [RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
"Bidirectional Protocol Independent Multicast (BIDIR- "Bidirectional Protocol Independent Multicast (BIDIR-
PIM)", RFC 5015, October 2007. PIM)", RFC 5015, October 2007.
[I-D.ietf-pim-join-attributes] [RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol
Boers, A., "Format for using TLVs in PIM messages", Independent Multicast (PIM) Join Attribute Format",
draft-ietf-pim-join-attributes-03 (work in progress), I-D RFC 5384, November 2008.
Status iesg, IETF Datatracker State Publication Requested,
Intended Status Proposed Standard, Responsible AD David
Ward, May 2007.
7.2. Informative References 7.2. Informative References
Authors' Addresses Authors' Addresses
IJsbrand Wijnands IJsbrand Wijnands
Cisco Systems, Inc. Cisco Systems, Inc.
De kleetlaan 6a De kleetlaan 6a
Diegem 1831 Diegem 1831
Belgium Belgium
skipping to change at page 9, line 4 skipping to change at page 8, line 41
Authors' Addresses Authors' Addresses
IJsbrand Wijnands IJsbrand Wijnands
Cisco Systems, Inc. Cisco Systems, Inc.
De kleetlaan 6a De kleetlaan 6a
Diegem 1831 Diegem 1831
Belgium Belgium
Email: ice@cisco.com Email: ice@cisco.com
Arjen Boers Arjen Boers
Cisco Systems, Inc. Cisco Systems, Inc.
Avda. Diagonal, 682 Avda. Diagonal, 682
Barcelona 08034 Barcelona 08034
Spain Spain
Email: aboers@cisco.com Email: aboers@cisco.com
Eric Rosen Eric Rosen
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, Ma 01719 Boxborough, Ma 01719
Email: erosen@cisco.com Email: erosen@cisco.com
Full Copyright Statement Copyright and License Notice
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
Funding for the RFC Editor function is provided by the IETF This document is subject to BCP 78 and the IETF Trust's Legal
Administrative Support Activity (IASA). Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
 End of changes. 13 change blocks. 
69 lines changed or deleted 23 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/