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

Brian Haberman <brian@innovationslab.net> Mon, 20 September 2010 20:59 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 485EA3A67B6 for <magma@core3.amsl.com>; Mon, 20 Sep 2010 13:59:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level:
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 q3lqcmdusNgw for <magma@core3.amsl.com>; Mon, 20 Sep 2010 13:59:01 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id 8465F3A6876 for <magma@ietf.org>; Mon, 20 Sep 2010 13:59:01 -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 D322E88297 for <magma@ietf.org>; Mon, 20 Sep 2010 13:59:24 -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 22E511369461 for <magma@ietf.org>; Mon, 20 Sep 2010 13:59:24 -0700 (PDT)
Message-ID: <4C97CB2A.6040609@innovationslab.net>
Date: Mon, 20 Sep 2010 16:59:22 -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
References: <4FD1E7CD248BF84F86BD4814EDDDBCC150AFA149AB@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <4FD1E7CD248BF84F86BD4814EDDDBCC150AFA149AB@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: Mon, 20 Sep 2010 20:59:02 -0000

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