draft-ietf-pim-rfc4601bis-01.txt   draft-ietf-pim-rfc4601bis-02.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: Draft Standard M. Handley Intended Status: Internet Standard M. Handley
Expires: April 29, 2012 UCL Expires: April 20, 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 27, 2011 October 17, 2013
Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised) Protocol Specification (Revised)
draft-ietf-pim-rfc4601bis-01 draft-ietf-pim-rfc4601bis-02
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 2, line 9 skipping to change at page 2, line 9
capable routing information base. It builds unidirectional shared capable routing information base. It builds unidirectional shared
trees rooted at a Rendezvous Point (RP) per group, and optionally trees rooted at a Rendezvous Point (RP) per group, and optionally
creates shortest-path trees per source. creates shortest-path trees per source.
This document addresses errata filed against RFC 4601, and removes This document addresses errata filed against RFC 4601, and removes
the optional (*,*,RP) feature that lacks sufficient deployment the optional (*,*,RP) feature that lacks sufficient deployment
experience. experience.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2013 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 36 skipping to change at page 4, line 36
6.2. Non-Cryptographic Authentication Mechanisms . . . . . . .125 6.2. Non-Cryptographic Authentication Mechanisms . . . . . . .125
6.3. Authentication Using IPsec . . . . . . . . . . . . . . . .126 6.3. Authentication Using IPsec . . . . . . . . . . . . . . . .126
6.3.1. Protecting Link-Local Multicast Messages . . . . . . .126 6.3.1. Protecting Link-Local Multicast Messages . . . . . . .126
6.3.2. Protecting Unicast Messages . . . . . . . . . . . . .127 6.3.2. Protecting Unicast Messages . . . . . . . . . . . . .127
6.3.2.1. Register Messages . . . . . . . . . . . . . . . .127 6.3.2.1. Register Messages . . . . . . . . . . . . . . . .127
6.3.2.2. Register-Stop Messages . . . . . . . . . . . . . .127 6.3.2.2. Register-Stop Messages . . . . . . . . . . . . . .127
6.4. Denial-of-Service Attacks . . . . . . . . . . . . . . . .128 6.4. Denial-of-Service Attacks . . . . . . . . . . . . . . . .128
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .128 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .128
8. Normative References . . . . . . . . . . . . . . . . . . . . .129 8. Normative References . . . . . . . . . . . . . . . . . . . . .129
9. Informative References . . . . . . . . . . . . . . . . . . . .129 9. Informative References . . . . . . . . . . . . . . . . . . . .129
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .131 Appendix A. Functionality removed from RFC 4601 . . . . . . . . .131
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .132
List of Figures List of Figures
Figure 1. Per-(S,G) register state machine at a DR ................38 Figure 1. Per-(S,G) register state machine at a DR ................38
Figure 2. Downstream per-interface (*,G) state machine ............45 Figure 2. Downstream per-interface (*,G) state machine ............45
Figure 3. Downstream per-interface (S,G) state machine ............49 Figure 3. Downstream per-interface (S,G) state machine ............49
Figure 4. Downstream per-interface (S,G,rpt) state machine ........53 Figure 4. Downstream per-interface (S,G,rpt) state machine ........53
Figure 5. Upstream (*,G) state machine ............................58 Figure 5. Upstream (*,G) state machine ............................58
Figure 6. Upstream (S,G) state machine ............................62 Figure 6. Upstream (S,G) state machine ............................62
Figure 7. Upstream (S,G,rpt) state machine for triggered Figure 7. Upstream (S,G,rpt) state machine for triggered
skipping to change at page 131, line 5 skipping to change at page 130, line 15
[15] Savola, P., Lehtonen, R., and D. Meyer, "Protocol Independent [15] Savola, P., Lehtonen, R., and D. Meyer, "Protocol Independent
Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Multicast - Sparse Mode (PIM-SM) Multicast Routing Security
Issues and Enhancements", RFC 4609, August 2006. Issues and Enhancements", RFC 4609, August 2006.
[16] Savola, P. and J. Lingard, "Host Threats to Protocol Independent [16] Savola, P. and J. Lingard, "Host Threats to Protocol Independent
Multicast (PIM)", RFC 5294, August 2008. Multicast (PIM)", RFC 5294, August 2008.
[17] Savola, P. and B. Haberman, "Embedding the Rendezvous Point (RP) [17] Savola, P. and B. Haberman, "Embedding the Rendezvous Point (RP)
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
Implementations and Deployments", draft-ietf-pim-rfc4601-update-
survey-report-03.txt, September 2013.
Appendix A. Functionality removed from RFC 4601
Based on a survey of PIM implementations and deployments [18],
conducted by IETF PIM working group, the following functionality of
RFC 4601 has been removed due to lack of sufficient implementation
and deployment experience.
o (*,*,RP) State
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
EMail: fenner@research.att.com EMail: fenner@research.att.com
Mark Handley Mark Handley
 End of changes. 6 change blocks. 
6 lines changed or deleted 21 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/