draft-ietf-pim-mtid-00.txt   draft-ietf-pim-mtid-01.txt 
PIM WG Yiqun Cai PIM WG Yiqun Cai
Internet Draft Heidi Ou Internet Draft Heidi Ou
Intended Status: Proposed Standard Intended Status: Proposed Standard
Expires: July 7, 2009 Cisco Systems, Inc. Expires: January 2, 2010 Cisco Systems, Inc.
January 7, 2009 July 2, 2009
PIM Multi-Topology ID (MT-ID) Join-Attribute PIM Multi-Topology ID (MT-ID) Join-Attribute
draft-ietf-pim-mtid-00.txt draft-ietf-pim-mtid-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 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.
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 July 7, 2009. This Internet-Draft will expire on January 2, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
Abstract Abstract
This document introduces a new type of PIM Join Attribute that This document introduces a new type of PIM Join Attribute that
extends PIM signaling to identify a topology that should be used when extends PIM signaling to identify a topology that should be used when
constructing a particular multicast distribution tree. constructing a particular multicast distribution tree.
Table of Contents Table of Contents
1 Specification of Requirements ...................... 2 1 Specification of Requirements ...................... 2
skipping to change at page 4, line 45 skipping to change at page 4, line 45
3.3. Applicability 3.3. Applicability
The PIM MT-ID join attribute described in this draft applies to PIM The PIM MT-ID join attribute described in this draft applies to PIM
Join/Assert packets used by PIM SM/SSM/Bidir. It is not used in any Join/Assert packets used by PIM SM/SSM/Bidir. It is not used in any
other PIM packets, such as Prune, Register, Register-Stop, Graft, other PIM packets, such as Prune, Register, Register-Stop, Graft,
Graft-ack, DF Election, Candidate-RP, and Bootstrap. As such, it can Graft-ack, DF Election, Candidate-RP, and Bootstrap. As such, it can
only be used to build shared or source trees for PIM SM/SSM and PIM- only be used to build shared or source trees for PIM SM/SSM and PIM-
bidir downstream. bidir downstream.
When this attribute is used in combination with RPF vectors defined When this attribute is used in combination with RPF vectors defined
in [ID.ietf-pim-rpf-vector] [ID.ietf-l3vpn-2547bis-mcast], they are in [RFC5496] [ID.ietf-l3vpn-2547bis-mcast], they are processed
processed against the topology identified by the PIM MT-ID attribute. against the topology identified by the PIM MT-ID attribute.
4. Protocol Specification of PIM MT-ID 4. Protocol Specification of PIM MT-ID
4.1. Sending PIM MT-ID Join Attribute 4.1. Sending PIM MT-ID Join Attribute
When a PIM router originates a PIM Join/Assert packet, it may choose When a PIM router originates a PIM Join/Assert packet, it may choose
to encode PIM MT-ID of the topology in which RPF lookup takes place to encode PIM MT-ID of the topology in which RPF lookup takes place
for the corresponding (*,G) or (S,G) entry. The chosen PIM MT-ID MUST for the corresponding (*,G) or (S,G) entry. The chosen PIM MT-ID MUST
be the one decided by local topology selection configuration if it be the one decided by local topology selection configuration if it
exists, or the one received from downstream routers after conflict exists, or the one received from downstream routers after conflict
skipping to change at page 6, line 15 skipping to change at page 6, line 15
4.3. Validating PIM MT-ID Join Attribute 4.3. Validating PIM MT-ID Join Attribute
An encoded PIM MT-ID join attribute is valid if all of the following An encoded PIM MT-ID join attribute is valid if all of the following
conditions are satisfied, conditions are satisfied,
- there is at most 1 PIM MT-ID attribute encoded. - there is at most 1 PIM MT-ID attribute encoded.
- the length field must be 2 and the value must not be 0. - the length field must be 2 and the value must not be 0.
If an encoded PIM MT-ID join attribute is deemed invalid, it is If an encoded PIM MT-ID join attribute is deemed invalid, it is
ignored and not forwarded further. The packet is processed as if the silently ignored. The packet is processed as if the attribute were
attribute were not present. not present.
It is important to note that, if the sender is not a PIM neighbor It is important to note that, if the sender is not a PIM neighbor
that has included "PIM Join Attribute" option in its Hello packets, that has included "PIM Join Attribute" option in its Hello packets,
or if the "F" bit in the encoding is reset, the encoding may still be the encoding may still be considered valid by an implementation.
considered valid by an implementation and is allowed to be forwarded.
4.4. Conflict Resolution 4.4. Conflict Resolution
Depending on whether a PIM router is an upstream or a downstream Depending on whether a PIM router is an upstream or a downstream
router, the action it takes to resolve conflicting PIM MT-ID router, the action it takes to resolve conflicting PIM MT-ID
attributes differs. The detail is described below. attributes differs. The detail is described below.
4.4.1. Upstream Routers 4.4.1. Upstream Routers
If an upstream router has a local configuration that specifies a If an upstream router has a local configuration that specifies a
skipping to change at page 7, line 33 skipping to change at page 7, line 33
in the ASSERT process, and the ASSERT winner uses a different PIM in the ASSERT process, and the ASSERT winner uses a different PIM
MT-ID, the downstream router SHOULD still choose the ASSERT MT-ID, the downstream router SHOULD still choose the ASSERT
winner as the RPF neighbour but it MUST NOT encode PIM MT-ID when winner as the RPF neighbour but it MUST NOT encode PIM MT-ID when
sending Join packets to it. sending Join packets to it.
5. PIM MT-ID Join Attribute TLV Format 5. PIM MT-ID Join Attribute TLV Format
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|F|E| Attr Type | Length | Value | |F|E| Attr Type | Length |R R R R| Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- F bit: 1 Transitive Attribute. - F bit: 0 Non-transitive Attribute.
- E bit: As specified by [RFC5384] - E bit: As specified by [RFC5384]
- Attr Type: 3. - Attr Type: 3.
- Length: 2. - Length: 2.
- Value: PIM MT-ID, 1 to 65535. - R: Reserved bits, 4 in total.
- Value: PIM MT-ID, 1 to 4095.
6. IANA Considerations 6. IANA Considerations
A new PIM Join Attribute type needs to be assigned. 3 is proposed for A new PIM Join Attribute type needs to be assigned. 3 is proposed for
now. now.
7. Security Considerations 7. Security Considerations
As a type of PIM Join Attribute, the security considerations As a type of PIM Join Attribute, the security considerations
described in [RFC5384] apply here. Specifically, malicious alteration described in [RFC5384] apply here. Specifically, malicious alteration
skipping to change at page 9, line 26 skipping to change at page 9, line 26
11. Informative References 11. Informative References
[RFC4915] P. Psenak, S. Mirtorabi, A. Roy, L. Nguyen, P. Pillay- [RFC4915] P. Psenak, S. Mirtorabi, A. Roy, L. Nguyen, P. Pillay-
Esnault, "Multi-Topology (MT) Routing in OSPF", RFC 4915, June 2007. Esnault, "Multi-Topology (MT) Routing in OSPF", RFC 4915, June 2007.
[RFC5120] T. Przygienda, N. Shen, N. Sheth, "M-ISIS: Multi Topology [RFC5120] T. Przygienda, N. Shen, N. Sheth, "M-ISIS: Multi Topology
(MT) Routing in Intermediate System to Intermediate Systems (IS- (MT) Routing in Intermediate System to Intermediate Systems (IS-
ISs)", RFC 5120, February 2008. ISs)", RFC 5120, February 2008.
[ID.ietf-pim-rpf-vector] I. Wijnands, A. Boers, E. Rosen, "The RPF [RFC5496] I. Wijnands, A. Boers, E. Rosen, "The Reverse Path
Vector TLV", draft-ietf-pim-rpf-vector. Forwarding (RPF) Vector TLV", RFC 5496, March 2009.
[ID.ietf-l3vpn-2547bis-mcast] E. Rosen,R Aggarwal, "Multicast in [ID.ietf-l3vpn-2547bis-mcast] E. Rosen,R Aggarwal, "Multicast in
MPLS/BGP IP VPNs", draft-ietf-l3vpn-2547bis-mcast
 End of changes. 13 change blocks. 
20 lines changed or deleted 20 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/