IETF Logo Mail Archive

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

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6qBK-0007uK-A0; Tue, 16 Jan 2007 10:25:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6qBI-0007mo-Qj for 16ng@ietf.org; Tue, 16 Jan 2007 10:25:00 -0500
Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1H6qBH-0000fM-Jm for 16ng@ietf.org; Tue, 16 Jan 2007 10:25:00 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-15.tower-119.messagelabs.com!1168961098!8348701!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 4091 invoked from network); 16 Jan 2007 15:24:58 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-15.tower-119.messagelabs.com with SMTP; 16 Jan 2007 15:24:58 -0000
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l0GFOwLu029573; Tue, 16 Jan 2007 08:24:58 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id l0GFOve6011405; Tue, 16 Jan 2007 09:24:58 -0600 (CST)
Message-ID: <45ACEE48.6050504@motorola.com>
Date: Tue, 16 Jan 2007 16:24:56 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Daniel Park <soohongp@gmail.com>
Subject: Re: [16NG] Re: multicast and IPv6 over ETHCS
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> <45ACD265.2080601@motorola.com> <f7c7d76e0701160557pbfb25aclad1cbdb04699cf02@mail.gmail.com>
In-Reply-To: <f7c7d76e0701160557pbfb25aclad1cbdb04699cf02@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: b19722fc8d3865b147c75ae2495625f2
Cc: 16ng@ietf.org
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

Daniel Park wrote:
> Folks,
> 
>> 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.
> 
> [chair hat-on]
> 
> The thread is digressing from the point at issue. Following the 16ng 
> charter, we will definitely work on a single EthernetCS document to
> be ready for publication. While chartering, we (chairs, IAB, IESG and
>  several experts on this field) had many discussion and ended up to 
> this conclusion. Thus, please focus on the technical aspect itself
> not inputing to separate it.

Dear Chair, I was not aware of the decision.

> [chair hat-off]
> 
> Alex, your contribution on the current EthernetCS document would be 
> valuable and acceptable to me. So, please do this...:-)

Thanks, I can only submit contribution about IPv6-over-ETHCS (maybe 
section in the full IPv6-IPv4 document).  I can not write text about
IPv4-over-ETHCS for several reasons.  I have implemented IPv6 not IPv4.
  IPv4 does not have stringent requirements with respect to the
link-layer supporting multicast.  IPv4 requires link-layer to be
broadcast capable, not multicast.

I will agree with the group's decisions.

Alex

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

v2.8.7 | Report a Bug | By Email