draft-ietf-mboned-lightweight-igmpv3-mldv2-04.txt   draft-ietf-mboned-lightweight-igmpv3-mldv2-05.txt 
MBONED Working Group H. Liu MBONED Working Group H. Liu
Internet-Draft W. Cao Internet-Draft W. Cao
Intended status: BCP Huawei Technologies Co., Ltd. Intended status: BCP Huawei Technologies Co., Ltd.
Expires: March 10, 2009 H. Asaeda Expires: November 23, 2009 H. Asaeda
Keio University Keio University
September 6, 2008 May 22, 2009
Lightweight IGMPv3 and MLDv2 Protocols Lightweight IGMPv3 and MLDv2 Protocols
draft-ietf-mboned-lightweight-igmpv3-mldv2-04 draft-ietf-mboned-lightweight-igmpv3-mldv2-05
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79. This document may contain material
have been or will be disclosed, and any of which he or she becomes from IETF Documents or IETF Contributions published or made publicly
aware will be disclosed, in accordance with Section 6 of BCP 79. available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
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.
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."
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 March 10, 2009. This Internet-Draft will expire on November 23, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract Abstract
This document describes lightweight IGMPv3 and MLDv2 protocols (LW- This document describes lightweight IGMPv3 and MLDv2 protocols (LW-
IGMPv3 and LW-MLDv2), which simplify the standard (full) versions of IGMPv3 and LW-MLDv2), which simplify the standard (full) versions of
IGMPv3 and MLDv2. The interoperability with the full versions and IGMPv3 and MLDv2. The interoperability with the full versions and
the previous versions of IGMP and MLD is also taken into account. the previous versions of IGMP and MLD is also taken into account.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT","SHOULD", "SHOULD NOT", "RECOMMENDED","MAY", and "OPTIONAL" in NOT","SHOULD", "SHOULD NOT", "RECOMMENDED","MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC 2119 [1]. this document are to be interpreted as described in RFC 2119 [1].
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Simplification Method Overview . . . . . . . . . . . . . . . . 7 3. Simplification Method Overview . . . . . . . . . . . . . . . . 8
3.1. Behavior of Group Members . . . . . . . . . . . . . . . . 7 3.1. Behavior of Group Members . . . . . . . . . . . . . . . . 8
3.2. Behavior of Multicast Routers . . . . . . . . . . . . . . 7 3.2. Behavior of Multicast Routers . . . . . . . . . . . . . . 8
4. LW-IGMPv3 Protocol for Group Members . . . . . . . . . . . . . 9 4. LW-IGMPv3 Protocol for Group Members . . . . . . . . . . . . . 10
4.1. Query and Report Messages . . . . . . . . . . . . . . . . 9 4.1. Query and Report Messages . . . . . . . . . . . . . . . . 10
4.2. Action on Change of Interface State . . . . . . . . . . . 9 4.2. Action on Change of Interface State . . . . . . . . . . . 10
4.3. Action on Reception of a Query . . . . . . . . . . . . . . 10 4.3. Action on Reception of a Query . . . . . . . . . . . . . . 11
4.4. LW-IGMPv3 Group Record Types . . . . . . . . . . . . . . . 10 4.4. LW-IGMPv3 Group Record Types . . . . . . . . . . . . . . . 11
5. LW-IGMPv3 Protocol for Multicast Routers . . . . . . . . . . . 12 5. LW-IGMPv3 Protocol for Multicast Routers . . . . . . . . . . . 13
5.1. Group Timers and Source Timers in the Lightweight 5.1. Group Timers and Source Timers in the Lightweight
Version . . . . . . . . . . . . . . . . . . . . . . . . . 12 Version . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.2. Source-Specific Forwarding Rules . . . . . . . . . . . . . 13 5.2. Source-Specific Forwarding Rules . . . . . . . . . . . . . 14
5.3. Reception of Current-State Records . . . . . . . . . . . . 13 5.3. Reception of Current-State Records . . . . . . . . . . . . 14
5.4. Reception of Source-List-Change and Filter-Mode-Change 5.4. Reception of Source-List-Change and Filter-Mode-Change
Records . . . . . . . . . . . . . . . . . . . . . . . . . 14 Records . . . . . . . . . . . . . . . . . . . . . . . . . 15
6. Interoperability . . . . . . . . . . . . . . . . . . . . . . . 16 6. Interoperability . . . . . . . . . . . . . . . . . . . . . . . 17
6.1. Interoperation with the Full Version of IGMPv3/MLDv2 . . . 16 6.1. Interoperation with the Full Version of IGMPv3/MLDv2 . . . 17
6.1.1. Behavior of Group Members . . . . . . . . . . . . . . 16 6.1.1. Behavior of Group Members . . . . . . . . . . . . . . 17
6.1.2. Behavior of Multicast Routers . . . . . . . . . . . . 16 6.1.2. Behavior of Multicast Routers . . . . . . . . . . . . 17
6.2. Interoperation with IGMPv1/IGMPv2 . . . . . . . . . . . . 16 6.2. Interoperation with IGMPv1/IGMPv2 . . . . . . . . . . . . 17
6.2.1. Behavior of Group Members . . . . . . . . . . . . . . 16 6.2.1. Behavior of Group Members . . . . . . . . . . . . . . 17
6.2.2. Behavior of Multicast Routers . . . . . . . . . . . . 17 6.2.2. Behavior of Multicast Routers . . . . . . . . . . . . 18
6.3. Interoperation with MLDv1 . . . . . . . . . . . . . . . . 17 6.3. Interoperation with MLDv1 . . . . . . . . . . . . . . . . 18
7. Implementation Considerations . . . . . . . . . . . . . . . . 19 7. Implementation Considerations . . . . . . . . . . . . . . . . 20
7.1. Implementation of Source-Specific Multicast . . . . . . . 19 7.1. Implementation of Source-Specific Multicast . . . . . . . 20
7.2. Implementation of Multicast Source Filter (MSF) APIs . . . 19 7.2. Implementation of Multicast Source Filter (MSF) APIs . . . 20
8. Security Considerations . . . . . . . . . . . . . . . . . . . 20 8. Security Considerations . . . . . . . . . . . . . . . . . . . 21
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22
9.1. Normative References . . . . . . . . . . . . . . . . . . . 21 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.2. Informative References . . . . . . . . . . . . . . . . . . 21 10.1. Normative References . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 10.2. Informative References . . . . . . . . . . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
IGMP version 3 [2] and MLD version 2 [3] implement source filtering IGMP version 3 [2] and MLD version 2 [3] implement source filtering
capabilities that are not supported by their earlier versions, IGMPv1 capabilities that are not supported by their earlier versions, IGMPv1
[4], IGMPv2 [5] and MLDv1 [6]. An IGMPv3 or MLDv2 capable host can [4], IGMPv2 [5] and MLDv1 [6]. An IGMPv3 or MLDv2 capable host can
tell its upstream router which group it would like to join by tell its upstream router which group it would like to join by
specifying which sources it does or does not intend to receive specifying which sources it does or does not intend to receive
multicast traffic from. IGMPv3 and MLDv2 add the capability for a multicast traffic from. IGMPv3 and MLDv2 add the capability for a
multicast router to learn sources which are of interest or which are multicast router to learn sources which are of interest or which are
skipping to change at page 13, line 42 skipping to change at page 14, line 42
G_Timer > 0 S_TIMER >= 0 Suggest forwarding G_Timer > 0 S_TIMER >= 0 Suggest forwarding
traffic from source traffic from source
G_Timer > 0 No Source Elements Suggest forwarding G_Timer > 0 No Source Elements Suggest forwarding
traffic from source traffic from source
5.3. Reception of Current-State Records 5.3. Reception of Current-State Records
When receiving Current-State Records, the LW-IGMPv3 router resets its When receiving Current-State Records, the LW-IGMPv3 router resets its
group or source timers and updates its source list within the group. group or source timers and updates its source list within the group.
For source-specific group reception state (when G_Timer==0), the For source-specific group reception state (when G_Timer==0 and
source list contains sources whose traffic will be forwarded by the S_Timer > 0), the source list contains sources whose traffic will be
router, while in non-source-specific group reception (when forwarded by the router, while in non-source-specific group reception
G_Timer>0), the source list remembers the valid sources to receive (when G_Timer>0), the source list remembers the valid sources to
traffic from after toggling to source-specific reception state. receive traffic from after toggling to source-specific reception
state.
Although the LW-IGMPv3 host only sends a subset of the message of Although the LW-IGMPv3 host only sends a subset of the message of
that of the full version, the LW-IGMPv3 router should be able to that of the full version, the LW-IGMPv3 router should be able to
process as much messages as possible to be compatible with the full process as much messages as possible to be compatible with the full
version host. Note that if the report type is IS_EX(x) with non- version host. Note that if the report type is IS_EX(x) with non-
empty source-list, the router will treat it as the same type of empty source-list, the router will treat it as the same type of
report with empty source list. The following table describes the report with empty source list. The following table describes the
action taken by a multicast router after receiving Current-State action taken by a multicast router after receiving Current-State
Records. The notations have the same meaning as that in the full Records. The notations have the same meaning as that in the full
IGMPv3 protocol. IGMPv3 protocol.
skipping to change at page 17, line 28 skipping to change at page 18, line 28
A full IGMPv3 router uses Group Compatibility Mode (whose value is A full IGMPv3 router uses Group Compatibility Mode (whose value is
either of IGMPv1, IGMPv2, or IGMPv3) per group record to indicate either of IGMPv1, IGMPv2, or IGMPv3) per group record to indicate
which version of IGMP protocol it behaves for the group. This value which version of IGMP protocol it behaves for the group. This value
is set according to the version of the received IGMP report. When is set according to the version of the received IGMP report. When
Group Compatibility Mode is IGMPv3, the lightweight router acts with Group Compatibility Mode is IGMPv3, the lightweight router acts with
LW-IGMPv3 protocol for that group. LW-IGMPv3 protocol for that group.
When Group Compatibility mode is IGMPv2, a LW-IGMPv3 router inherits When Group Compatibility mode is IGMPv2, a LW-IGMPv3 router inherits
this compatibility mechanism with the following rules: this compatibility mechanism with the following rules:
IGMPv2 Message LW-IGMPv3 Equivalent IGMP Message LW-IGMPv3 Equivalent
-------------- -------------------- -------------- --------------------
v2 Report TO_EX({}) v2 Report TO_EX({})
v2 Leave TO_IN({}) v2 Leave TO_IN({})
When Group Compatibility mode is IGMPv1, a LW-IGMPv3 router When Group Compatibility mode is IGMPv1, a LW-IGMPv3 router
internally translates the following IGMPv1 and IGMPv2 messages for internally translates the following IGMPv1 and IGMPv2 messages for
that group to their IGMPv3 equivalents: that group to their LW-IGMPv3 equivalents:
IGMPv1 Message LW-IGMPv3 Equivalent IGMP Message LW-IGMPv3 Equivalent
-------------- -------------------- -------------- --------------------
v1 Report TO_EX({}) v1 Report TO_EX({})
v2 Report TO_EX({}) v2 Report TO_EX({})
6.3. Interoperation with MLDv1 6.3. Interoperation with MLDv1
The MLDv2 hosts and routers MUST interoperate with the hosts and LW-MLDv2 hosts and routers MUST interoperate with the hosts and
routers running MLDv1. The method is the same as described in routers running MLDv1. The method is the same as described in
Section 6.2. The difference is that when a MLDv2 router has a MLDv1 Section 6.2. The difference is that when a LW-MLDv2 router has a
listener on its network, it translates the following MLDv1 messages MLDv1 listener on its network, it translates the following MLDv1
to their MLDv2 equivalents: messages to their LW-MLDv2 equivalents:
MLDv1 Message LW-MLDv2 Equivalent MLDv1 Message LW-MLDv2 Equivalent
------------- ------------------- ------------- -------------------
Report TO_EX({}) Report TO_EX({})
Done TO_IN({}) Done TO_IN({})
7. Implementation Considerations 7. Implementation Considerations
skipping to change at page 19, line 21 skipping to change at page 20, line 21
running IGMPv3/MLDv2 (snooping) and multicast routing protocols may running IGMPv3/MLDv2 (snooping) and multicast routing protocols may
be greatly decreased. be greatly decreased.
In the following sections, the implementation related aspects are In the following sections, the implementation related aspects are
described for the lightweight version protocols. described for the lightweight version protocols.
7.1. Implementation of Source-Specific Multicast 7.1. Implementation of Source-Specific Multicast
[8] illustrates the requirements of implementation of Source-Specific [8] illustrates the requirements of implementation of Source-Specific
Multicast (SSM) on IGMPv3/MLDv2 hosts and routers. The lightweight Multicast (SSM) on IGMPv3/MLDv2 hosts and routers. The lightweight
protocol does not impose any bad influences on an SSM application. protocol follows the same rule given in [8] except the changing of
The requirements of LW-IGMPv3/LW-MLDv2 for supporting SSM are the message types due to the simplification.
illustrated below.
A LW-IGMPv3/LW-MLDv2 host should not invoke (*,G) join (i.e., A LW-IGMPv3/LW-MLDv2 host should not invoke (*,G) join (i.e.,
TO_EX({})) and IGMPv2 Leave and MLDv1 Done messages (i.e., TO_IN({})) TO_EX({})) and (*,G) leave (i.e., TO_IN({})) for the application
for the application whose multicast address is in the SSM address whose multicast address is in the SSM address range. The upstream
range. The reception of a (*,G) join with an SSM group address LW-IGMPv3/LW-MLDv2 router will ignore the these messages and may log
should indicate an error to the application. The SSM-aware router an error on reception of them. Other types of messages should be
will ignore TO_EX({}) reports with SSM addresses. Other types of processed as [8] describes.
Reports should be processed normally.
7.2. Implementation of Multicast Source Filter (MSF) APIs 7.2. Implementation of Multicast Source Filter (MSF) APIs
Multicast Source Filter (MSF) APIs [9] defines (1) IPv4 Basic MSF Multicast Source Filter (MSF) APIs [9] defines (1) IPv4 Basic MSF
API, (2) IPv4 Advanced MSF API, (3) Protocol-Independent Basic MSF API, (2) IPv4 Advanced MSF API, (3) Protocol-Independent Basic MSF
API, and (4) Protocol-Independent Advanced MSF API. API, and (4) Protocol-Independent Advanced MSF API.
According to the MSF APIs definition, a LW-IGMPv3 host should According to the MSF APIs definition, a LW-IGMPv3 host should
implement either IPv4 Basic MSF API or Protocol-Independent Basic MSF implement either IPv4 Basic MSF API or Protocol-Independent Basic MSF
API, and a LW-MLDv2 host should implement Protocol-Independent Basic API, and a LW-MLDv2 host should implement Protocol-Independent Basic
MSF API. Other APIs, IPv4 Advanced MSF API and Protocol-Independent MSF API. Other APIs, IPv4 Advanced MSF API and Protocol-Independent
Advanced MSF API, are optional to implement in a LW-IGMPv3/LW-MLDv2 Advanced MSF API, are optional to implement in a LW-IGMPv3/LW-MLDv2
host. host.
8. Security Considerations 8. Security Considerations
The security considerations are the same as that of the full version The security considerations are the same as that of the full version
of IGMPv3/MLDv2. of IGMPv3/MLDv2.
9. References 9. Acknowledgements
9.1. Normative References The authors would like to appreciate MBONED and MAGMA working group
members. Special thanks is given to Marshall Eubanks, Guo Feng, Mark
Fine, Prashant Jhingran, Bharat Joshi, Guo Tao, Wang Wendong, and
Gong Xiangyang for their valuable comments and suggestions on this
document.
10. References
10.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to indicate requirement [1] Bradner, S., "Key words for use in RFCs to indicate requirement
levels", RFC 2119, March 1997. levels", RFC 2119, March 1997.
[2] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. [2] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A.
Thyagarajan, "Internet Group Management Protocol, Version 3", Thyagarajan, "Internet Group Management Protocol, Version 3",
RFC 3376, October 2002. RFC 3376, October 2002.
[3] Vida, R. and L. Costa, "Multicast Listener Discovery Version 2 [3] Vida, R. and L. Costa, "Multicast Listener Discovery Version 2
(MLDv2) for IPv6", RFC 3810, June 2004. (MLDv2) for IPv6", RFC 3810, June 2004.
skipping to change at page 21, line 36 skipping to change at page 23, line 36
Discovery (MLD) for IPv6", RFC 2710, October 1999. Discovery (MLD) for IPv6", RFC 2710, October 1999.
[7] Holbrook, H. and B. Cain, "Source-Specific Multicast for IP", [7] Holbrook, H. and B. Cain, "Source-Specific Multicast for IP",
RFC 4607, August 2006. RFC 4607, August 2006.
[8] Holbrook, H., Cain, B., and B. Haberman, "Using Internet Group [8] Holbrook, H., Cain, B., and B. Haberman, "Using Internet Group
Management Protocol Version 3 (IGMPv3) and Multicast Listener Management Protocol Version 3 (IGMPv3) and Multicast Listener
Discovery Protocol Version 2 (MLDv2) for Source-Specific Discovery Protocol Version 2 (MLDv2) for Source-Specific
Multicast", RFC 4604, August 2006. Multicast", RFC 4604, August 2006.
9.2. Informative References 10.2. Informative References
[9] Thaler, D., Fenner, B., and B. Quinn, "Socket Interface [9] Thaler, D., Fenner, B., and B. Quinn, "Socket Interface
Extensions for Multicast Source Filters", RFC 3678, Extensions for Multicast Source Filters", RFC 3678,
January 2004. January 2004.
Authors' Addresses Authors' Addresses
Hui Liu Hui Liu
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
Huawei Bld., No.3 Xinxi Rd. Huawei Bld., No.3 Xinxi Rd.
skipping to change at page 23, line 4 skipping to change at line 790
Email: caowayne@huawei.com Email: caowayne@huawei.com
Hitoshi Asaeda Hitoshi Asaeda
Keio University Keio University
Graduate School of Media and Governance Graduate School of Media and Governance
5322 Endo 5322 Endo
Fujisawa, Kanagawa 252-8520 Fujisawa, Kanagawa 252-8520
Japan Japan
Email: asaeda@wide.ad.jp Email: asaeda@wide.ad.jp
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 20 change blocks. 
64 lines changed or deleted 90 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/