draft-ietf-pim-explicit-tracking-04.txt   draft-ietf-pim-explicit-tracking-05.txt 
PIM Working Group H. Asaeda PIM Working Group H. Asaeda
Internet-Draft NICT Internet-Draft NICT
Intended status: Standards Track January 29, 2013 Intended status: Standards Track February 25, 2013
Expires: August 2, 2013 Expires: August 29, 2013
IGMP/MLD-Based Explicit Membership Tracking Function for Multicast IGMP/MLD-Based Explicit Membership Tracking Function for Multicast
Routers Routers
draft-ietf-pim-explicit-tracking-04 draft-ietf-pim-explicit-tracking-05
Abstract Abstract
This document describes the IGMP/MLD-based explicit membership This document describes the IGMP/MLD-based explicit membership
tracking function for multicast routers supporting IGMPv3/MLDv2. The tracking function for multicast routers supporting IGMPv3/MLDv2. The
explicit tracking function contributes to saving network resources explicit tracking function contributes to saving network resources
and fast leaves (i.e. shortening leave latency). and fast leaves (i.e. shortening leave latency).
Status of this Memo Status of this Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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/.
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."
This Internet-Draft will expire on August 2, 2013. This Internet-Draft will expire on August 29, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
skipping to change at page 9, line 11 skipping to change at page 9, line 11
information is outdated. This provides "smooth state transition" information is outdated. This provides "smooth state transition"
that does not initiate the membership state information from scratch that does not initiate the membership state information from scratch
and synchronizes the actual membership state smoothly. and synchronizes the actual membership state smoothly.
7. IANA Considerations 7. IANA Considerations
This document has no actions for IANA. This document has no actions for IANA.
8. Security Considerations 8. Security Considerations
There is no additional security consideration for [1][2][3] provided. The explicit tracking function potentially requires a large amount of
memory so that routers keep all membership states. Especially when
malicious hosts send a large number of invalid IGMP/MLD report
messages, some serious threats may be induced. In order to prevent
abuse, a router enabling the explicit tracking function MAY need to
rate-limit a total amount of membership information the router can
store and an amount of membership information the router can store
per host. The rate limit is left to the router's implementation.
9. Acknowledgements 9. Acknowledgements
Toerless Eckert, Sergio Figueiredo, Nicolai Leymann, Stig Venaas, and Toerless Eckert, Sergio Figueiredo, Nicolai Leymann, Stig Venaas, and
others provided many constructive and insightful comments. others provided many constructive and insightful comments.
10. References 10. References
10.1. Normative References 10.1. Normative References
 End of changes. 4 change blocks. 
5 lines changed or deleted 12 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/