Re: [16NG] Re: multicast and IPv6 over ETHCS

Pars Mutaf <pars.mutaf@int-evry.fr> Fri, 12 January 2007 14:25 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H5NLC-0000HR-O6; Fri, 12 Jan 2007 09:25:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H5NLB-0000HJ-Gz for 16ng@ietf.org; Fri, 12 Jan 2007 09:25:09 -0500
Received: from smtp2.int-evry.fr ([157.159.10.45]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5NLA-0006RR-3t for 16ng@ietf.org; Fri, 12 Jan 2007 09:25:09 -0500
Received: from lor-maknavic3.int-evry.fr (lor-maknavic3.int-evry.fr [157.159.103.217]) by smtp2.int-evry.fr (Postfix) with ESMTP id 0FA6B2FFD4; Fri, 12 Jan 2007 15:24:56 +0100 (CET)
Subject: Re: [16NG] Re: multicast and IPv6 over ETHCS
From: Pars Mutaf <pars.mutaf@int-evry.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
In-Reply-To: <45A76EC4.7070304@motorola.com>
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>
Content-Type: text/plain
Organization: INT Evry
Date: Fri, 12 Jan 2007 15:25:00 +0100
Message-Id: <1168611900.3013.9.camel@lor-maknavic3.int-evry.fr>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1
Content-Transfer-Encoding: 7bit
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck:
X-INT-MailScanner-SpamCheck:
X-INT-MailScanner-From: pars.mutaf@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: v6ops@ops.ietf.org, 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: pars.mutaf@int-evry.fr
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

Hi, sorry for popping up,

On Fri, 2007-01-12 at 12:19 +0100, Alexandru Petrescu wrote:
> Hi Jihoon, thanks for reply,
> 
> Jihoon Lee wrote:
> > Hi Alex,
> > 
> > Let me jump into discussion. 1) 802.16/16e MAC has no capability to 
> > do uplink multicast. In DL, 802.16 provides multicast CIDs which is 
> > initiated by DSA messages. In UL, however, there is no way for an MS 
> > to access others' UL data fundamentally, in 802.16 PHY/MAC.

Do you think this is an accidental design choice (i.e. no uplink
multicast)? Or 802.16/16e MAC designers had very good fundamental
reasons? 

(I'm sorry. This question looks out-of IETF scope. But I think we may 
learn something more general i.e. useful to IP perhaps?)

Thank you.
pars


> Ok.  For one, if the 802.16MAC is not capable to do bidirectional (or
> normal) multicast then that is a big issue for IPv6-over-IPv6CS. (and
> surprisingly, apparently the document IPv6-over-IPv6CS doesn't seem to
> mention the word 'multicast'.)




> 
> The issue is that a SS running IPv6 needs to multicast a NA, from time
> to time.  For DAD it needs to send a NS to a multicast address too.
> 
> > In case of ETH over 802.16, the ETH(bridge) may cover this (an MS 
> > sends multicast data in UL, and then a bridge forwards it back). But,
> >  there is still a difficulty in multicasting data back except for the
> >  source MS.
> 
> You mean the bridge in BS?  I was thinking ETHCS in SS may offer a
> multicast interface to the IP stack.
> 
> In both cases (bridge in BS or bridge in SS), I think it is not up to
> this document to specify how the ETHCS transforms a asymmetric ul/dl
> multicast feature into a symmetric one.  But it should be a goal for
> ETHCS to offer such an interface to the IPv6 stack, otherwise the IPv6
> stack won't work.  What do you think?
> 
> Alex
> 
> _______________________________________________
> 16NG mailing list
> 16NG@ietf.org
> https://www1.ietf.org/mailman/listinfo/16ng


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