| < draft-ietf-pim-3810bis-00.txt | draft-ietf-pim-3810bis-01.txt > | |||
|---|---|---|---|---|
| Network Working Group B. Haberman, Ed. | Network Working Group B. Haberman, Ed. | |||
| Internet-Draft JHU APL | Internet-Draft JHU APL | |||
| Obsoletes: 3810 (if approved) September 2021 | Obsoletes: 3810 (if approved) October 2021 | |||
| Intended status: Standards Track | Intended status: Standards Track | |||
| Expires: 1 April 2022 | Expires: 28 April 2022 | |||
| Multicast Listener Discovery Version 2 (MLDv2) for IPv6 | Multicast Listener Discovery Version 2 (MLDv2) for IPv6 | |||
| draft-ietf-pim-3810bis-00 | draft-ietf-pim-3810bis-01 | |||
| Abstract | Abstract | |||
| This document updates RFC 2710, and it specifies Version 2 of the | This document updates RFC 2710, and it specifies Version 2 of the | |||
| Multicast Listener Discovery Protocol (MLDv2). MLD is used by an | Multicast Listener Discovery Protocol (MLDv2). MLD is used by an | |||
| IPv6 router to discover the presence of multicast listeners on | IPv6 router to discover the presence of multicast listeners on | |||
| directly attached links, and to discover which multicast addresses | directly attached links, and to discover which multicast addresses | |||
| are of interest to those neighboring nodes. MLDv2 is designed to be | are of interest to those neighboring nodes. MLDv2 is designed to be | |||
| interoperable with MLDv1. MLDv2 adds the ability for a node to | interoperable with MLDv1. MLDv2 adds the ability for a node to | |||
| report interest in listening to packets with a particular multicast | report interest in listening to packets with a particular multicast | |||
| skipping to change at page 1, line 41 ¶ | skipping to change at page 1, line 41 ¶ | |||
| 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 https://datatracker.ietf.org/drafts/current/. | Drafts is at https://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 5 March 2022. | This Internet-Draft will expire on 4 April 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2021 IETF Trust and the persons identified as the | Copyright (c) 2021 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 (https://trustee.ietf.org/ | Provisions Relating to IETF Documents (https://trustee.ietf.org/ | |||
| license-info) in effect on the date of publication of this document. | license-info) in effect on the date of publication of this document. | |||
| Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
| skipping to change at page 4, line 26 ¶ | skipping to change at page 4, line 26 ¶ | |||
| 10.3. State Change Report messages . . . . . . . . . . . . . . 60 | 10.3. State Change Report messages . . . . . . . . . . . . . . 60 | |||
| 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60 | 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60 | |||
| 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 61 | 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 61 | |||
| 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 61 | 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 61 | |||
| 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 61 | 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 61 | |||
| 14.1. Normative References . . . . . . . . . . . . . . . . . . 61 | 14.1. Normative References . . . . . . . . . . . . . . . . . . 61 | |||
| 14.2. Informative References . . . . . . . . . . . . . . . . . 62 | 14.2. Informative References . . . . . . . . . . . . . . . . . 62 | |||
| Appendix A. Design Rationale . . . . . . . . . . . . . . . . . . 62 | Appendix A. Design Rationale . . . . . . . . . . . . . . . . . . 62 | |||
| A.1. The Need for State Change Messages . . . . . . . . . . . 62 | A.1. The Need for State Change Messages . . . . . . . . . . . 62 | |||
| A.2. Host Suppression . . . . . . . . . . . . . . . . . . . . 63 | A.2. Host Suppression . . . . . . . . . . . . . . . . . . . . 63 | |||
| A.3. Switching router filter modes from EXCLUDE to INCLUDE . . 63 | A.3. Switching router filter modes from EXCLUDE to INCLUDE . . 64 | |||
| Appendix B. Summary of Changes . . . . . . . . . . . . . . . . . 64 | Appendix B. Summary of Changes . . . . . . . . . . . . . . . . . 64 | |||
| B.1. MLDv1 . . . . . . . . . . . . . . . . . . . . . . . . . . 64 | B.1. MLDv1 . . . . . . . . . . . . . . . . . . . . . . . . . . 64 | |||
| B.2. MLDv2 . . . . . . . . . . . . . . . . . . . . . . . . . . 65 | B.2. MLDv2 . . . . . . . . . . . . . . . . . . . . . . . . . . 65 | |||
| Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 65 | Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 66 | |||
| 1. Introduction | 1. Introduction | |||
| The Multicast Listener Discovery Protocol (MLD) is used by IPv6 | The Multicast Listener Discovery Protocol (MLD) is used by IPv6 | |||
| routers to discover the presence of multicast listeners (i.e., nodes | routers to discover the presence of multicast listeners (i.e., nodes | |||
| that wish to receive multicast packets) on their directly attached | that wish to receive multicast packets) on their directly attached | |||
| links, and to discover specifically which multicast addresses are of | links, and to discover specifically which multicast addresses are of | |||
| interest to those neighboring nodes. Note that a multicast router | interest to those neighboring nodes. Note that a multicast router | |||
| may itself be a listener of one or more multicast addresses; in this | may itself be a listener of one or more multicast addresses; in this | |||
| case it performs both the "multicast router part" and the "multicast | case it performs both the "multicast router part" and the "multicast | |||
| skipping to change at page 61, line 11 ¶ | skipping to change at page 61, line 11 ¶ | |||
| In addition, IANA has assigned the ICMPv6 message type value of 143 | In addition, IANA has assigned the ICMPv6 message type value of 143 | |||
| for Version 2 Multicast Listener Report messages, as specified in | for Version 2 Multicast Listener Report messages, as specified in | |||
| Section 4. | Section 4. | |||
| 12. Contributors | 12. Contributors | |||
| Roland Vida, Luis Henrique Maciel Kosmalski Costa, Serge Fdida, Steve | Roland Vida, Luis Henrique Maciel Kosmalski Costa, Serge Fdida, Steve | |||
| Deering, Bill Fenner, and Isidor Kouvelas are the authors of RFC | Deering, Bill Fenner, and Isidor Kouvelas are the authors of RFC | |||
| 3810, which makes up the majority of the content in this document. | 3810, which makes up the majority of the content in this document. | |||
| Anuj Budhiraja, Toerless Eckert, Olufemi Komolafe and Tim Winters | ||||
| have contributed valuable content to this version of the | ||||
| specification. | ||||
| 13. Acknowledgments | 13. Acknowledgments | |||
| We would like to thank Hitoshi Asaeda, Randy Bush, Francis Dupont, | We would like to thank Hitoshi Asaeda, Randy Bush, Francis Dupont, | |||
| Ted Hardie, Russ Housley, Konstantin Kabassanov, Erik Nordmark, | Ted Hardie, Russ Housley, Konstantin Kabassanov, Erik Nordmark, | |||
| Shinsuke Suzuki, Margaret Wasserman, Bert Wijnen, and Remi Zara for | Shinsuke Suzuki, Margaret Wasserman, Bert Wijnen, and Remi Zara for | |||
| their valuable comments and suggestions on this document. | their valuable comments and suggestions on this document. | |||
| Stig Venaas, Hitoshi Asaeda, and Mike McBride have provided valuable | ||||
| feedback on this version of the specification and we thank them for | ||||
| their input. | ||||
| 14. References | 14. References | |||
| 14.1. Normative References | 14.1. Normative References | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
| <https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 | [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 | |||
| End of changes. 8 change blocks. | ||||
| 6 lines changed or deleted | 14 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||