draft-ietf-pim-rpf-vector-05.txt   draft-ietf-pim-rpf-vector-06.txt 
PIM WG IJ. Wijnands PIM WG IJ. Wijnands
Internet-Draft A. Boers Internet-Draft A. Boers
Intended status: Informational E. Rosen Intended status: Informational E. Rosen
Expires: May 21, 2008 Cisco Systems, Inc. Expires: August 25, 2008 Cisco Systems, Inc.
November 18, 2007 February 22, 2008
The RPF Vector TLV The RPF Vector TLV
draft-ietf-pim-rpf-vector-05 draft-ietf-pim-rpf-vector-06
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes 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. 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
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 May 21, 2008. This Internet-Draft will expire on August 25, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). 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 [I-D.ietf-pim-join-attributes] which
enables PIM to build multicast trees through an MPLS-enabled network, enables PIM to build multicast trees through an MPLS-enabled network,
even if that network's IGP does not have a route to the source of the even if that network's IGP does not have a route to the source of the
tree. tree.
Table of Contents Table of Contents
skipping to change at page 6, line 12 skipping to change at page 6, line 12
the source of the tree. This information is used in the selection of the source of the tree. This information is used in the selection of
the assert winner. If a PIM Join is being sent towards a Vector, the assert winner. If a PIM Join is being sent towards a Vector,
rather than towards the source, the Assert message must have the rather than towards the source, the Assert message must have the
metric to the Vector instead of the metric to the source. The Assert metric to the Vector instead of the metric to the source. The Assert
message however does not have an attribute field and does not mention message however does not have an attribute field and does not mention
the Vector. the Vector.
A router may change its upstream neighbor on a particular multicast A router may change its upstream neighbor on a particular multicast
tree as the result of receiving Assert messages. However a Vector tree as the result of receiving Assert messages. However a Vector
Attribute should not be sent in a PIM Join to an upstream neighbor Attribute should not be sent in a PIM Join to an upstream neighbor
which is chosen as the result of processing the Assert messages. which is chosen as the result of an assert winner and different from
Reachability of the Vector is only guaranteed by the router that the original upstream neighbor (the upstream neighbor for the
advertises reachability to the Vector in its IGP. If the assert multicast route not influenced by the assert). Reachability of the
winner upstream is not our real preferred next-hop, we can't be sure Vector is only guaranteed by the router that advertises reachability
this router knows the path to the Vector. In the worst case the to the Vector in its IGP. If the assert winner upstream is not our
assert winner has a route to the Vector that is on the same interface real preferred next-hop, we can't be sure this router knows the path
where the assert was won. That will point the RPF interface to that to the Vector. In the worst case the assert winner has a route to
interface and will result in the O-list being NULL. The Vector the Vector that is on the same interface where the assert was won.
attribute is not inserted if the RPF neighbor was chosen via an That will point the RPF interface to that interface and will result
assert process and the RPF neighbor is different from the RPF in the O-list being NULL. The Vector attribute is not inserted if
neighbor that would have been selected via the local routing table. the RPF neighbor was chosen via an assert process and the RPF
In all other cases the Vector has to be included in the Join message. neighbor is different from the RPF neighbor that would have been
selected via the local routing table. In all other cases the Vector
has to be included in the Join message.
2.3.4. Vector Attribute and Join suppression 2.3.4. Vector Attribute and Join suppression
If a router receives a PIM join on the upstream LAN interface for a If a router receives a PIM join on the upstream LAN interface for a
particular multicast state, join suppression may be applied if that particular multicast state, join suppression may be applied if that
PIM join is targeted to the same upstream neighbor. Which router(s) PIM join is targeted to the same upstream neighbor. Which router(s)
will suppress their PIM join is depending on timing and is will suppress their PIM join is depending on timing and is
unpredictable. Downstream routers on a LAN may include different RPF unpredictable. Downstream routers on a LAN may include different RPF
vectors in the PIM joins. Therefore an upstream router on that LAN vectors in the PIM joins. Therefore an upstream router on that LAN
may receive and use different RPF vectors over time to reach the may receive and use different RPF vectors over time to reach the
skipping to change at page 8, line 28 skipping to change at page 8, line 28
[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] [I-D.ietf-pim-join-attributes]
Boers, A., "Format for using TLVs in PIM messages", Boers, A., "Format for using TLVs in PIM messages",
draft-ietf-pim-join-attributes-03 (work in progress), draft-ietf-pim-join-attributes-03 (work in progress), I-D
May 2007. 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 10, line 7 skipping to change at page 10, line 7
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 Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 7 change blocks. 
20 lines changed or deleted 24 lines changed or added

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