[magma] MLDv2 router in the presence of MLDv1 Multicast Address Listeners

"K.Kawaguchi" <kawaguti@ysknet.co.jp> Tue, 28 September 2010 08:28 UTC

Return-Path: <kawaguti@ysknet.co.jp>
X-Original-To: magma@core3.amsl.com
Delivered-To: magma@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D22E23A6C7A for <magma@core3.amsl.com>; Tue, 28 Sep 2010 01:28:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.516
X-Spam-Level: **
X-Spam-Status: No, score=2.516 tagged_above=-999 required=5 tests=[AWL=-0.248, BAYES_20=-0.74, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XV+RhJO5lVOp for <magma@core3.amsl.com>; Tue, 28 Sep 2010 01:28:02 -0700 (PDT)
Received: from tkns.tk.ysknet.co.jp (tkmx.tk.ysknet.co.jp [203.180.172.16]) by core3.amsl.com (Postfix) with SMTP id 93E2A3A6C33 for <magma@ietf.org>; Tue, 28 Sep 2010 01:28:01 -0700 (PDT)
Received: (qmail 28018 invoked from network); 28 Sep 2010 16:29:25 +0900
Received: from (HELO PrecisionM20) (@) by with SMTP; 28 Sep 2010 16:29:25 +0900
To: <magma@ietf.org>
From: "K.Kawaguchi" <kawaguti@ysknet.co.jp>
Message-Id: <201009281628.GIA98953.BBJUHVLX@ysknet.co.jp>
X-Mailer: Winbiff [Version 2.51 PL2]
X-Accept-Language: ja,en,zh
Date: Tue, 28 Sep 2010 16:28:37 +0900
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [magma] MLDv2 router in the presence of MLDv1 Multicast Address Listeners
X-BeenThere: magma@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: kawaguti@ysknet.co.jp
List-Id: Multicast and Anycast Group Membership <magma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/magma>
List-Post: <mailto:magma@ietf.org>
List-Help: <mailto:magma-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 08:28:02 -0000

Hi all,

I have another question.

About a size limit of a Multicast Address Specific Query in MLDv2.

How is a query transmitted when the number of multicast source
addresses of a query message is limited by the MTU?

Is a Query split like a Report type IS_IN?
(It isn't a Query like Report type IS_EX, is it?)


RFC3810
------------------------------------------------------------------------
5.  Message Formats

5.1.  Multicast Listener Query Message

5.1.10.  Number of Sources (N)

   The Number of Sources (N) field specifies how many source addresses
   are present in the Query.  This number is zero in a General Query or
   a Multicast Address Specific Query, and non-zero in a Multicast
   Address and Source Specific Query.  This number is limited by the MTU
   of the link over which the Query is transmitted.  For example, on an
   Ethernet link with an MTU of 1500 octets, the IPv6 header (40 octets)
   together with the Hop-By-Hop Extension Header (8 octets) that
   includes the Router Alert option consume 48 octets; the MLD fields up
   to the Number of Sources (N) field consume 28 octets; thus, there are
   1424 octets left for source addresses, which limits the number of
   source addresses to 89 (1424/16).


5.2.  Version 2 Multicast Listener Report Message

5.2.15.  Multicast Listener Report Size

   If the set of Multicast Address Records required in a Report does not
   fit within the size limit of a single Report message (as determined
   by the MTU of the link on which it will be sent), the Multicast
   Address Records are sent in as many Report messages as needed to
   report the entire set.

   If a single Multicast Address Record contains so many source
   addresses that it does not fit within the size limit of a single
   Report message, then:

   o  if its Type is not IS_EX or TO_EX, it is split into multiple
      Multicast Address Records; each such record contains a different
      subset of the source addresses, and is sent in a separate Report.

   o  if its Type is IS_EX or TO_EX, a single Multicast Address Record
      is sent, with as many source addresses as can fit; the remaining
      source addresses are not reported.  Although the choice of which
      sources to report is arbitrary, it is preferable to report the
      same set of sources in each subsequent report, rather than
      reporting different sources each time.

Best Regards
--
Kiyoaki Kawaguchi