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

Kunal Shah <kunal.shah@ericsson.com> Mon, 20 September 2010 21:14 UTC

Return-Path: <kunal.shah@ericsson.com>
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 32CEA3A6972 for <magma@core3.amsl.com>; Mon, 20 Sep 2010 14:14:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.999
X-Spam-Level:
X-Spam-Status: No, score=-4.999 tagged_above=-999 required=5 tests=[AWL=-2.400, BAYES_00=-2.599]
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 VTej-MCiB-nO for <magma@core3.amsl.com>; Mon, 20 Sep 2010 14:13:59 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 5E0A53A69D1 for <magma@ietf.org>; Mon, 20 Sep 2010 14:13:56 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id o8KLPuWe020720; Mon, 20 Sep 2010 16:26:13 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.10]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Mon, 20 Sep 2010 17:13:59 -0400
From: Kunal Shah <kunal.shah@ericsson.com>
To: Brian Haberman <brian@innovationslab.net>, "magma@ietf.org" <magma@ietf.org>
Date: Mon, 20 Sep 2010 17:13:58 -0400
Thread-Topic: [magma] Question about group ID ipv6 multicast addresses
Thread-Index: ActZBt5gp1/xuDMyRay8W+I9eg4nNgAAKi4A
Message-ID: <4FD1E7CD248BF84F86BD4814EDDDBCC150AFA150CE@EUSAACMS0703.eamcs.ericsson.se>
References: <4FD1E7CD248BF84F86BD4814EDDDBCC150AFA149AB@EUSAACMS0703.eamcs.ericsson.se> <4C97CB2A.6040609@innovationslab.net>
In-Reply-To: <4C97CB2A.6040609@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 21 Sep 2010 06:03:42 -0700
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: Mon, 20 Sep 2010 21:14:07 -0000

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??

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??

Thanks
Kunal

-----Original Message-----
From: magma-bounces@ietf.org [mailto:magma-bounces@ietf.org] On Behalf Of Brian Haberman
Sent: Monday, September 20, 2010 1:59 PM
To: magma@ietf.org
Subject: Re: [magma] Question about group ID ipv6 multicast addresses

On 9/17/10 5:14 PM, Kunal Shah wrote:
> Hi all,
> 
> I was looking at the RFC 3307 and after reading section 4, I had the 
> following questions:
> 
> 1. Permanent mcast addresses use Group Ids 0x00000001 to 0x3FFFFFFF .
> Does this mean this range of group IDS is reserved and cannot be used 
> with non permanent addresses??

Yes.

> 
> 2. Also can the group ID range 0x40000000 to 0x7FFFFFFF be used by 
> customers for their content channels??

That range is intended for use with IPv6 multicast addresses derived using RFC 3306.  You should note that the IANA considerations state that group IDs in this range are allocated based on Expert Review.  So, if the customer is sourcing well-known application data, then it may make sense to use this range.

Regards,
Brian
_______________________________________________
magma mailing list
magma@ietf.org
https://www.ietf.org/mailman/listinfo/magma