Re: [16NG] Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 17 November 2008 22:46 UTC

Return-Path: <16ng-bounces@ietf.org>
X-Original-To: 16ng-archive@optimus.ietf.org
Delivered-To: ietfarch-16ng-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E59A28C15F; Mon, 17 Nov 2008 14:46:24 -0800 (PST)
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D32B28C156 for <16ng@core3.amsl.com>; Mon, 17 Nov 2008 13:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.111
X-Spam-Level:
X-Spam-Status: No, score=-2.111 tagged_above=-999 required=5 tests=[AWL=-0.112, BAYES_00=-2.599, J_CHICKENPOX_32=0.6]
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 XwFeR57dhmVB for <16ng@core3.amsl.com>; Mon, 17 Nov 2008 13:49:04 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224]) by core3.amsl.com (Postfix) with ESMTP id B2D0A3A6907 for <16ng@ietf.org>; Mon, 17 Nov 2008 13:49:04 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id b25so2591241rvf.49 for <16ng@ietf.org>; Mon, 17 Nov 2008 13:49:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=LkILpzScjfROU0vyTXkOXz549ck4MSKXysSxFtKUr6Y=; b=Etg00pMVHq1c2ToZH6aX4YjZ98dmPOJlq4aR3ixmi/TNSGDMDK+jPPiv5Em8TRA/cO UpiLDKwe7km2nhV6Qx7WxCv54ePeqxj9Pohucblrl+Ak8JVphm7hDQPgYJI/lhviAvN8 Iq54UZaJv2+T0V5yCoOv8xaH1YWdsR37WGIjs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Ok4RCW749UTwXj5B6v4/tV2sHAVBwpEZ9UGKkoZKRPDn2DnxJWxrN5Z8HtoWECXIwD /1NuxIz+1GJha2KMkLOno/nc2SYABE0v2DIefKIWVoR5DDoxXa1hbieWf4fNhVpOPaJ2 +UWHGJS6r/HWjC5aE2GCwvYcXFIWUXTmvGCA8=
Received: by 10.141.49.18 with SMTP id b18mr2505595rvk.96.1226958544377; Mon, 17 Nov 2008 13:49:04 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id k2sm10827343rvb.1.2008.11.17.13.49.02 (version=SSLv3 cipher=RC4-MD5); Mon, 17 Nov 2008 13:49:03 -0800 (PST)
Message-ID: <4921E6CF.5070207@gmail.com>
Date: Tue, 18 Nov 2008 10:49:03 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Daniel Park <soohongp@gmail.com>
References: <4BACF58443A3A04688976073775ABB2961B535@daebe102.NOE.Nokia.com> <f7c7d76e0811140119k7ca6a799oeefe0d8dc8111167@mail.gmail.com> <4920E121.5090102@gmail.com> <f7c7d76e0811171203q77763329m21c79469d56f5582@mail.gmail.com> <4921D200.3070506@gmail.com> <f7c7d76e0811171335n66eedc6asa7173c6b749b40d3@mail.gmail.com>
In-Reply-To: <f7c7d76e0811171335n66eedc6asa7173c6b749b40d3@mail.gmail.com>
X-Mailman-Approved-At: Mon, 17 Nov 2008 14:46:21 -0800
Cc: john.loughney@nokia.com, ipv6@ietf.org, "16ng@ietf.org" <16ng@ietf.org>
Subject: Re: [16NG] Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: 16ng-bounces@ietf.org
Errors-To: 16ng-bounces@ietf.org

On 2008-11-18 10:35, Daniel Park wrote:
> Confusing...definitely RFC5121 must be implemented for IPv6 over WiMAX
> network. EthernetCS must be too. No need to decide which CS must be used for
> WiMAX by 6man...?

My understanding is that in the IETF we try to avoid situations where
two ways of doing the same thing MUST be implemented. I hope that 16ng will
produce an applicability statement, but I don't see what we can usefully
say in the node requirements.

    Brian
> 
> Daniel
> 
> On Tue, Nov 18, 2008 at 5:20 AM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>> On 2008-11-18 09:03, Daniel Park wrote:
>>> Brian (ccing 16ng list)
>>>
>>> On Mon, Nov 17, 2008 at 12:12 PM, Brian E Carpenter <
>>> brian.e.carpenter@gmail.com> wrote:
>>>
>>>> Daniel,
>>>>
>>>> On 2008-11-14 22:19, Daniel Park wrote:
>>>>> John,
>>>>>
>>>>> I would make a minor change according to the valuable comments from the
>>>>> WiMAX expert:
>>>>>
>>>>> There are two ways to transfer IPv6 over WiMAX:
>>>>> - IPv6 over WiMAX using IPCS: RFC5121
>>>>> - IPv6 over Ethernet carried over WiMAX: AD Evaluation (ID Status)
>>>> Where does your suggested preference for the IPv6 CS come from?
>>>> Does 16ng have a consensus on this preference?
>>>>
>>>> Since I can't imagine anyone *not* implementing the Ethernet CS,
>>>> doesn't this make extra work for all implementors, compared
>>>> with preferring the Ethernet CS for both IP versions?
>>>
>>> We had long discussion on that before..:-) Yes, IPv6CS (RFC5121) comes
>> from
>>> 16ng WG. And EthernetCS is too. Prebably, the consensus you mentioned
>> above
>>> means which CS is a mandatory or optional for IPv6 implementation or
>>> both. Well, 16ng WG just leaves them to the business choice in WiMAX
>>> networks since that is beyond scope of 16ng. As of today, obviously
>> mobile
>>> biz wants to implement IPv6CS only, and wired biz (looks like DSL) wants
>> to
>>> implemt EthernetCS. But, no one knows what happens tomorrow in WiMAX
>>> networks.
>> Then it seems to me there is no useful statement to be made
>> in the node requirements document. If 16ng has no recommendation,
>> I don't see how 6man can decide.
>>
>> Thanks
>>
>>   Brian
>>
> 
_______________________________________________
16NG mailing list
16NG@ietf.org
https://www.ietf.org/mailman/listinfo/16ng