Re: [magma] Question about group ID ipv6 multicast addresses

Brian Haberman <brian@innovationslab.net> Tue, 21 September 2010 13:26 UTC

Return-Path: <brian@innovationslab.net>
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 EC2DC28C0E8 for <magma@core3.amsl.com>; Tue, 21 Sep 2010 06:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level:
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Q7rjMOUzkqkn for <magma@core3.amsl.com>; Tue, 21 Sep 2010 06:26:06 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id CFA533A6900 for <magma@ietf.org>; Tue, 21 Sep 2010 06:26:06 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 8992F8821F for <magma@ietf.org>; Tue, 21 Sep 2010 06:26:31 -0700 (PDT)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 231DB13694BC for <magma@ietf.org>; Tue, 21 Sep 2010 06:26:31 -0700 (PDT)
Message-ID: <4C98B285.3030202@innovationslab.net>
Date: Tue, 21 Sep 2010 09:26:29 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: "magma@ietf.org" <magma@ietf.org>
References: <4FD1E7CD248BF84F86BD4814EDDDBCC150AFA149AB@EUSAACMS0703.eamcs.ericsson.se> <4C97CB2A.6040609@innovationslab.net> <4FD1E7CD248BF84F86BD4814EDDDBCC150AFA150CE@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <4FD1E7CD248BF84F86BD4814EDDDBCC150AFA150CE@EUSAACMS0703.eamcs.ericsson.se>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [magma] Question about group ID ipv6 multicast addresses
X-BeenThere: magma@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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, 21 Sep 2010 13:26:11 -0000

On 9/20/10 5:13 PM, Kunal Shah wrote:
> Hi Brian,
> 
> Thaks for your resonse. For group ID range 0x40000000 to 0x7FFFFFFF,
> can these group IDs be ever present in mcast addresses contained in
> MLD reports i.e Can customers have their STBs send out MLD joins for
> mcast addresses containing group IDs in this range??

Yes.  A node should send an MLD Report for all joined multicast
addresses except the All-Hosts address.  That is clearly stated in the
MLD specifications.

> 
> If group ID ranges 0x00000001 to 0x3FFFFFFF and 0x40000000 to
> 0x7FFFFFFF cannot be present in mcast addresses coming in a MLD
> report, does this mean only the range 0x80000000 to 0xFFFFFFFF can be
> used with mcast addresses inside MLD reports??
> 

I think you are confused.  All of the group IDs can occur in multicast
addresses.  What RFC 3307 does is specifies the type of multicast
address that can contain each of the group ID ranges.

Regards,
Brian