draft-ietf-pim-rfc4601bis-02.txt   draft-ietf-pim-rfc4601bis-03.txt 
Network Working Group B. Fenner Network Working Group B. Fenner
Internet Draft AT&T Labs - Research Internet Draft AT&T Labs - Research
Intended Status: Internet Standard M. Handley Intended Status: Internet Standard M. Handley
Expires: April 20, 2014 UCL Expires: Noveber 7, 2014 UCL
H. Holbrook H. Holbrook
Arastra Arastra
I. Kouvelas I. Kouvelas
R. Parekh R. Parekh
Cisco Systems, Inc. Cisco Systems, Inc.
Z. Zhang Z. Zhang
Juniper Networks Juniper Networks
L. Zheng L. Zheng
Huawei Technologies Huawei Technologies
October 17, 2013 May 7, 2014
Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised) Protocol Specification (Revised)
draft-ietf-pim-rfc4601bis-02 draft-ietf-pim-rfc4601bis-03
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted 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). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
skipping to change at page 116, line 11 skipping to change at page 116, line 11
The group address for which the router wishes to resolve the The group address for which the router wishes to resolve the
forwarding conflict. This is an Encoded-Group address, as forwarding conflict. This is an Encoded-Group address, as
specified in Section 4.9.1. specified in Section 4.9.1.
Source Address Source Address
Source address for which the router wishes to resolve the Source address for which the router wishes to resolve the
forwarding conflict. The source address MAY be set to zero for forwarding conflict. The source address MAY be set to zero for
(*,G) asserts (see below). The format for this address is given (*,G) asserts (see below). The format for this address is given
in Encoded-Unicast-Address in Section 4.9.1. in Encoded-Unicast-Address in Section 4.9.1.
R RPT-bit is a 1-bit value. The RPT-bit is set to 1 for R RPTbit is a 1-bit value. The RPTbit is set to 1 for
Assert(*,G) messages and 0 for Assert(S,G) messages. Assert(*,G) messages and 0 for Assert(S,G) messages.
Metric Preference Metric Preference
Preference value assigned to the unicast routing protocol that Preference value assigned to the unicast routing protocol that
provided the route to the multicast source or Rendezvous-Point. provided the route to the multicast source or Rendezvous-Point.
Metric Metric
The unicast routing table metric associated with the route used The unicast routing table metric associated with the route used
to reach the multicast source or Rendezvous-Point. The metric to reach the multicast source or Rendezvous-Point. The metric
is in units applicable to the unicast routing protocol used. is in units applicable to the unicast routing protocol used.
Assert messages can be sent to resolve a forwarding conflict for all Assert messages can be sent to resolve a forwarding conflict for all
traffic to a given group or for a specific source and group. traffic to a given group or for a specific source and group.
Assert(S,G) Assert(S,G)
Source-specific asserts are sent by routers forwarding a Source-specific asserts are sent by routers forwarding a
specific source on the shortest-path tree (SPTbit is TRUE). specific source on the shortest-path tree (SPTbit is TRUE).
(S,G) Asserts have the Group-Address field set to the group G (S,G) Asserts have the Group-Address field set to the group G
and the Source-Address field set to the source S. The RPT-bit and the Source-Address field set to the source S. The RPTbit
is set to 0, the Metric-Preference is set to MRIB.pref(S) and is set to 0, the Metric-Preference is set to MRIB.pref(S) and
the Metric is set to MRIB.metric(S). the Metric is set to MRIB.metric(S).
Assert(*,G) Assert(*,G)
Group-specific asserts are sent by routers forwarding data for Group-specific asserts are sent by routers forwarding data for
the group and source(s) under contention on the shared tree. the group and source(s) under contention on the shared tree.
(*,G) asserts have the Group-Address field set to the group G. (*,G) asserts have the Group-Address field set to the group G.
For data-triggered Asserts, the Source-Address field MAY be set For data-triggered Asserts, the Source-Address field MAY be set
to the IP source address of the data packet that triggered the to the IP source address of the data packet that triggered the
Assert and is set to zero otherwise. The RPT-bit is set to 1, Assert and is set to zero otherwise. The RPTbit is set to 1,
the Metric-Preference is set to MRIB.pref(RP(G)), and the Metric the Metric-Preference is set to MRIB.pref(RP(G)), and the Metric
is set to MRIB.metric(RP(G)). is set to MRIB.metric(RP(G)).
4.10. PIM Timers 4.10. PIM Timers
PIM-SM maintains the following timers, as discussed in Section 4.1. PIM-SM maintains the following timers, as discussed in Section 4.1.
All timers are countdown timers; they are set to a value and count All timers are countdown timers; they are set to a value and count
down to zero, at which point they typically trigger an action. Of down to zero, at which point they typically trigger an action. Of
course they can just as easily be implemented as count-up timers, course they can just as easily be implemented as count-up timers,
where the absolute expiry time is stored and compared against a real- where the absolute expiry time is stored and compared against a real-
skipping to change at page 131, line 9 skipping to change at page 131, line 9
Address in an IPv6 Multicast Address", RFC 3956, November 2004. Address in an IPv6 Multicast Address", RFC 3956, November 2004.
[18] Zheng, L., Zhang, Z. and R. Parekh, "Survey Report on PIM-SM [18] Zheng, L., Zhang, Z. and R. Parekh, "Survey Report on PIM-SM
Implementations and Deployments", draft-ietf-pim-rfc4601-update- Implementations and Deployments", draft-ietf-pim-rfc4601-update-
survey-report-03.txt, September 2013. survey-report-03.txt, September 2013.
Appendix A. Functionality removed from RFC 4601 Appendix A. Functionality removed from RFC 4601
Based on a survey of PIM implementations and deployments [18], Based on a survey of PIM implementations and deployments [18],
conducted by IETF PIM working group, the following functionality of conducted by IETF PIM working group, the following functionality of
RFC 4601 has been removed due to lack of sufficient implementation RFC 4601 has been removed due to lack of sufficient
and deployment experience. implementation and deployment experience.
o (*,*,RP) State o (*,*,RP) State
o PIM Mulitcast Border Router (PMBR) o PIM Mulitcast Border Router (PMBR)
Authors' Addresses Authors' Addresses
Bill Fenner Bill Fenner
AT&T Labs - Research AT&T Labs - Research
1 River Oaks Place 1 River Oaks Place
San Jose, CA 95134 San Jose, CA 95134
 End of changes. 7 change blocks. 
8 lines changed or deleted 8 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/