[16NG] Re: multicast and IPv6 over ETHCS

Alexandru Petrescu <alexandru.petrescu@motorola.com> Tue, 16 January 2007 13:29 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6oNJ-0004CP-50; Tue, 16 Jan 2007 08:29:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6oNI-0004AU-9P for 16ng@ietf.org; Tue, 16 Jan 2007 08:29:16 -0500
Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H6oK9-00075r-Lj for 16ng@ietf.org; Tue, 16 Jan 2007 08:26:02 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-8.tower-119.messagelabs.com!1168953960!8717333!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [144.189.100.101]
Received: (qmail 29547 invoked from network); 16 Jan 2007 13:26:00 -0000
Received: from motgate2.mot.com (HELO motgate2.mot.com) (144.189.100.101) by server-8.tower-119.messagelabs.com with SMTP; 16 Jan 2007 13:26:00 -0000
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate2.mot.com (8.12.11/Motorola) with ESMTP id l0GDQ0MA025445; Tue, 16 Jan 2007 06:26:00 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id l0GDPwZp009138; Tue, 16 Jan 2007 07:25:59 -0600 (CST)
Message-ID: <45ACD265.2080601@motorola.com>
Date: Tue, 16 Jan 2007 14:25:57 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Jihoon Lee <jhlee@mmlab.snu.ac.kr>
References: <20070110194054.28319.qmail@web81914.mail.mud.yahoo.com> <45A54ED7.9020203@motorola.com> <45A67293.6030504@motorola.com> <fa31afde0701111703x9beb44axd1c8d9ff9a537983@mail.gmail.com> <45A76EC4.7070304@motorola.com> <fa31afde0701130744r2e8486b6rd1a291f938a57785@mail.gmail.com> <45AB7268.7020609@motorola.com> <fa31afde0701151611o73352694j69dd2e994b31636e@mail.gmail.com>
In-Reply-To: <fa31afde0701151611o73352694j69dd2e994b31636e@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: 16ng@ietf.org
Subject: [16NG] Re: multicast and IPv6 over ETHCS
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

Jihoon Lee wrote:
> Hi Alex,
> I agree with that.

I also agree, more specifically for IPv6-over-ETHCS document to not 
specify how to implement link-layer multicast behaviour.

If the draft is separated in two separated documents IPv6-over-ETHCS and 
IPv4-over-ETHCS, then I will suggest the following multicast text, for 
the IPv6-over-ETHCS document.

Do you think this text makes sense in the context of this document?  Do 
you agree with the text or portions of it?  Anything wrong with this text?

Thanks,

Alex

> Running IPv6 over an Ethernet link needs the support of link-layer 
> multicast.  In the 802.16 context, the Ethernet Convergence Sublayer 
> (also known as the IEEE Std 802.3/Ethernet-specific part of the IEEE 
> 802.16 Packet Convergence Sublayer) must (1) support multicast 
> link-layer addresses (2) map IPv6 multicast addresses to link-layer 
> addresses and vice-versa, (3) offer the capability of joining and 
> leaving IPv6 link-local multicast groups and (4) send and receive 
> IPv6 link-local multicast packets whose link-layer headers contain 
> link-layer multicast addresses.
> 
> The following link-layer multicast addresses are recommended by 
> RFCXXXX: 33:33:0:0:0:1, 2, 33:33:ff:XX:XX:XX, and others [fill].
> 
> The rules for mapping IPv6 link-local multicast addresses to 
> link-layer multicast addresses are recommended by RFCxxxx and are the
> following:
 >
>     - ff02::1 maps into 33:33:00:00:00:1
>     - and the others.
> 

> The IPv6 stack must join a certain link-local IPv6 multicast group 
> before receiving packets addressed to that group.  For example, 
> before receiving a Router Advertisement the stack MUST join the IPv6 
> link-local multicast address 'all-nodes'.  When the IPv6 stack on the
> Subscriber Station joins a certain IPv6 link-local multicast group it
> MUST receive all packets addressed to that group.  The join operation
> can happen in several ways: sending a MLD REPORT (RFCxxx), setting a
> local filtering rule, etc.
> 
> The IPv6 stack must be able to leave a certain IPv6 link-local 
> multicast group.  When the IPv6 stack leaves a group must no longer 
> receive the IPv6 packets addressed to that group.  Similarly to the 
> joining operation the leaving operation can happen in several ways: 
> sending a MLD REPORT, setting a local filtering rule, etc.
> 
> The following Neighbour Discovery messages are sent by a Subscriber 
> Station to IPv6 link-local multicast addresses: Neighbour 
> Advertisement, Neighbour Solicitation, Router Solicitation (RFCxxxx).
> The following Neighbour Discovery messages are received by a
> Subscriber Station, addressed to IPv6 link-local multicast addresses:
> Router Advertisement, Neighbour Advertisement, Neighbour 
> Solicitation.

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng