IETF Logo Mail Archive

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

"Daniel Park" <soohongp@gmail.com> Tue, 16 January 2007 15:35 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6qL6-00016A-Rj; Tue, 16 Jan 2007 10:35:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6qL1-00015f-It for 16ng@ietf.org; Tue, 16 Jan 2007 10:35:03 -0500
Received: from an-out-0708.google.com ([209.85.132.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6qKz-0002H4-H0 for 16ng@ietf.org; Tue, 16 Jan 2007 10:35:02 -0500
Received: by an-out-0708.google.com with SMTP id d30so608309and for <16ng@ietf.org>; Tue, 16 Jan 2007 07:35:01 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PegW2iCBc6HscbPd0PFQPpQc3LqjaHWZtTfKnAtvzpcSnVMxaB59wGFYa6nVFmh1TmnPy03C0oleWjU48c/1LnWOsuASMDboaQAgvz6Iu8PIU1PknI002DCu9dKhhI4ti4c8YxgZQZrl5TmIxd5quu22zVwoP2R2ZN4OMkLoOSQ=
Received: by 10.65.154.4 with SMTP id g4mr8035067qbo.1168961698289; Tue, 16 Jan 2007 07:34:58 -0800 (PST)
Received: by 10.64.204.5 with HTTP; Tue, 16 Jan 2007 07:34:58 -0800 (PST)
Message-ID: <f7c7d76e0701160734j7b405553x9d00c91379aa4bf@mail.gmail.com>
Date: Wed, 17 Jan 2007 00:34:58 +0900
From: "Daniel Park" <soohongp@gmail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
Subject: Re: [16NG] Re: multicast and IPv6 over ETHCS
In-Reply-To: <45ACEE48.6050504@motorola.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20070110194054.28319.qmail@web81914.mail.mud.yahoo.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> <45ACEE48.6050504@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
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

Thanks much Alex for your prompt and kind understanding.

I'd recommend authors of EthernetCS document to devide technical
sections into IPv4 and IPv6. Then, you who are willing to contribution
IPv6 only will be able to do your work more efficient than now. Also,
who are interesting in IPv4 only will be able to contribute their
efforts to IPv4 section as well...

Author of EthernetCS document, please take care of Alex' concern...:-)

Thanks in advance,

Daniel

On 1/17/07, Alexandru Petrescu <alexandru.petrescu@motorola.com> wrote:
> 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
>


-- 


Daniel (Soohong Daniel Park)
Mobile Convergence Laboratory, SAMSUNG Electronics.

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

v2.8.7 | Report a Bug | By Email