Skip to main content

Multicast Listener Discovery Version 2 (MLDv2) for IPv6
draft-ietf-pim-3810bis-12

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pim-3810bis@ietf.org, gunter@vandevelde.cc, pim-chairs@ietf.org, pim@ietf.org, rfc-editor@rfc-editor.org, stig@venaas.com
Subject: Protocol Action: 'Multicast Listener Discovery Version 2 (MLDv2) for IPv6' to Internet Standard (draft-ietf-pim-3810bis-12.txt)

The IESG has approved the following document:
- 'Multicast Listener Discovery Version 2 (MLDv2) for IPv6'
  (draft-ietf-pim-3810bis-12.txt) as Internet Standard

This document is the product of the Protocols for IP Multicast Working Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and John
Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-3810bis/


Ballot Text

Technical Summary

   This document updates RFC 2710, and it specifies Version 2 of the
   Multicast Listener Discovery Protocol (MLDv2).  MLD is used by an
   IPv6 router to discover the presence of multicast listeners on
   directly attached links, and to discover which multicast addresses
   are of interest to those neighboring nodes.  MLDv2 is designed to be
   interoperable with MLDv1.  MLDv2 adds the ability for a node to
   report interest in listening to packets with a particular multicast
   address only from specific source addresses or from all sources
   except for specific source addresses.

   This document obsoletes RFC 3810.

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

Several people, some of the more active participants, have voiced their support.
Some concerns were raised during WGLC related to fallback to older versions and
SSM. This has been resolved after a longer discussion. No other issues raised.

There were some differences of opinion on whether it was necessary to add text
on fallback to older versions and SSM, after some discussion this was added. It
looks like the PIM WG found a good compromise.

The working group would like to make MLDv2 originally specified by rfc3810 in 2004 an Internet Standard and includes implementation and operator experience.

Document Quality

   Are there existing implementations of the protocol?  Have a 
   significant number of vendors indicated their plan to
   implement the specification?  Are there any reviewers that
   merit special mention as having done a thorough review,
   e.g., one that resulted in important changes or a
   conclusion that the document had no substantive issues?  If
   there was a MIB Doctor, Media Type, or other Expert Review,
   what was its course (briefly)?  In the case of a Media Type
   Review, on what date was the request posted?

There are many implementations of MLDv2. This document is updating that based on errata
and implementation/deployment experiences. The WG did a survey to get input on these aspects.

In general the document is in good shape and only minor changes from RFC3810. This document will obsolete RFC 3810 and update 2710.

The rtgdir review has been addressed by the document author
There is an open secdir item answered by the document, however the finite resolution may be found with architectural observations together with security ADs

Personnel

   The Document Shepherd for this document is Stig Venaas. The Responsible
   Area Director is Gunter Van de Velde.

IANA Note

   IANA has assigned the IPv6 link-local multicast address ff02::16,
   called "all MLDv2-capable routers", as described in Section 5.2.15.
   Version 2 Multicast Listener Reports will be sent to this special
   address.  The reference for this assignment should be changed to this
   document upon publication as an RFC.

   In addition, IANA has assigned the ICMPv6 message type value of 143
   for Version 2 Multicast Listener Report messages, as specified in
   Section 4.  The reference for this assignment should be changed to
   this document upon publication as an RFC.

RFC Editor Note