IETF Logo Mail Archive

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

"Daniel Park" <soohongp@gmail.com> Fri, 14 November 2008 09:14 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 47C373A6996; Fri, 14 Nov 2008 01:14:30 -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 81F333A6996 for <16ng@core3.amsl.com>; Fri, 14 Nov 2008 01:14:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 liTHFyUG9Tz3 for <16ng@core3.amsl.com>; Fri, 14 Nov 2008 01:14:28 -0800 (PST)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by core3.amsl.com (Postfix) with ESMTP id EFB613A6898 for <16ng@ietf.org>; Fri, 14 Nov 2008 01:14:27 -0800 (PST)
Received: by fg-out-1718.google.com with SMTP id d23so1025613fga.41 for <16ng@ietf.org>; Fri, 14 Nov 2008 01:14:26 -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:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=veyMeOQh+53S9oOIZcTyWb0Rhi56jobGDLYxVopLEcE=; b=hlmEJByEG6GrxuUM4jUoPVxXrchdqfM/wACKaotusJAUrYvtHrXwrBLx9j0liITvHQ 93Z+Bz6VOe0l83/XdoBXEhRWvxL3UMBcGD6WPQGmxG4S0CXGnbOhIf/AjxLhAsf9XBR+ R2ZN0PfHAFjc8zVl9Huo+hQGpUbKV9JJElubg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=QOgz1ASElubxfvEeJLaO38TlPhUwq+ryqnwZ1tTXFMLOw7OV1fb3cG8ohx6bI3IpZ5 lllPHUK1Zu/OD28L3loZ6dwuQeNF/2RfVmZ9IjJ0CrCu0Zj5Rr5kXk/SJ3m7FrNz+1oT KIgmBKAjVKbTUcQrpTVNW8RJ98F8+IKLT0XJg=
Received: by 10.181.231.19 with SMTP id i19mr182756bkr.205.1226654066628; Fri, 14 Nov 2008 01:14:26 -0800 (PST)
Received: by 10.181.47.2 with HTTP; Fri, 14 Nov 2008 01:14:26 -0800 (PST)
Message-ID: <f7c7d76e0811140114r29aaa4c7v2ce362fa2bb8aa55@mail.gmail.com>
Date: Fri, 14 Nov 2008 18:14:26 +0900
From: Daniel Park <soohongp@gmail.com>
To: "Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com>
In-Reply-To: <BC27158B99D3064A955ADE084783900C01666CE6@DEMUEXC014.nsn-intra.net>
MIME-Version: 1.0
References: <4BACF58443A3A04688976073775ABB2961B535@daebe102.NOE.Nokia.com> <f7c7d76e0811132212x427ef06aub634e857705bfaed@mail.gmail.com> <BC27158B99D3064A955ADE084783900C01666CE6@DEMUEXC014.nsn-intra.net>
Cc: 16ng@ietf.org
Subject: Re: [16NG] Fwd: Node Req: Issue 6: Support for RFC 5121: IP version 6over 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: multipart/mixed; boundary="===============2061335470=="
Sender: 16ng-bounces@ietf.org
Errors-To: 16ng-bounces@ietf.org

Max,

It looks good. Also, I think we can input EthCS to the IPv6 Node
Requirements after RFC publication.

Daniel


On Fri, Nov 14, 2008 at 5:36 PM, Riegel, Maximilian (NSN - DE/Munich) <
maximilian.riegel@nsn.com> wrote:

>  Daniel,
>
> There are two ways to transfer IPv6 over WiMAX:
> - IPv6 over WiMAX using IP-CS: RFC5121
> - IPv6 over Ethernet carried over WiMAX.
>
> It would be more clear to state the requirement:
>
> Nodes supporting IPv6 via IP-CS over WiMAX networks MUST implement
>
> "Transmission of IPv6 via the IPv6 Convergence Sublayer
> over IEEE 802.16 Networks" [RFC 5121].
> Thanks
> Max
>  ------------------------------
> *From:* 16ng-bounces@ietf.org [mailto:16ng-bounces@ietf.org] *On Behalf Of
> *ext Daniel Park
> *Sent:* Friday, November 14, 2008 7:13 AM
> *To:* 16ng@ietf.org
> *Subject:* [16NG] Fwd: Node Req: Issue 6: Support for RFC 5121: IP version
> 6over WiMAX
>
> FYI, in case you do not follow up IPv6 mailing list.
>
>
> Daniel
>
>
> ---------- Forwarded message ----------
> From: <john.loughney@nokia.com>
> Date: Fri, Nov 14, 2008 at 6:34 AM
> Subject: Node Req: Issue 6: Support for RFC 5121: IP version 6 over WiMAX
> To: ipv6@ietf.org
>
>
> Daniel Park sent this issue in:
>
> I'd request one more requirement for this bis. It is about 16ng
> deliverable for IPv6 transmission over IPv6CS networks as RFC 5121. Due
> to Convergence Sublayer characteristics of WiMAX networks, the below
> requirement must be included in the Node Requirement. (For example:
> globally unique prefix must be assigned to the WiMAX node, DAD
> considerations, ND features, and etc described in RFC 5121)
>
> 4.X IP version 6 over WiMAX - RFC 5121
>
> Nodes supporting IPv6 over WiMAX networks MUST implement
>
> "Transmission of IPv6 via the IPv6 Convergence Sublayer
> over IEEE 802.16 Networks" [RFC 5121].
>
> --> I think this seems like a reasonable thing to add.
>
> John
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



-- 
Daniel Park [at] Samsung Electronics
Standard Architect, blog.naver.com/natpt

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

v2.27.6 | Report a Bug | By Email | System Status