Re: [16NG] I-D Action:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-07.txt

<Basavaraj.Patil@nokia.com> Thu, 03 June 2010 21:06 UTC

Return-Path: <Basavaraj.Patil@nokia.com>
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 9572F3A6A03 for <16ng@core3.amsl.com>; Thu, 3 Jun 2010 14:06:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_MED=-4]
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 spv5roWQHN9W for <16ng@core3.amsl.com>; Thu, 3 Jun 2010 14:06:55 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 3DBF13A688C for <16ng@ietf.org>; Thu, 3 Jun 2010 14:06:55 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx09.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o53L6eX0009158 for <16ng@ietf.org>; Thu, 3 Jun 2010 16:06:41 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 4 Jun 2010 00:06:39 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 4 Jun 2010 00:06:39 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 4 Jun 2010 00:06:34 +0300
Received: from NOK-EUMSG-03.mgdnok.nokia.com ([65.54.30.108]) by nok-am1mhub-02.mgdnok.nokia.com ([65.54.30.6]) with mapi; Thu, 3 Jun 2010 23:06:34 +0200
From: <Basavaraj.Patil@nokia.com>
To: <maximilian.riegel@nsn.com>, <16ng@ietf.org>
Date: Thu, 3 Jun 2010 23:06:31 +0200
Thread-Topic: [16NG] I-D Action:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-07.txt
Thread-Index: AcsCyP3ZBHNAbCjOQayyAgLl5L5ETwAk2FIgAABFdyEAAHpTUAAAUWCa
Message-ID: <C82D8387.9556%basavaraj.patil@nokia.com>
In-Reply-To: <BC27158B99D3064A955ADE084783900C03817889@DEMUEXC014.nsn-intra.net>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 03 Jun 2010 21:06:34.0835 (UTC) FILETIME=[A6155230:01CB0360]
X-Nokia-AV: Clean
Subject: Re: [16NG] I-D Action:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-07.txt
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/mail-archive/web/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>
X-List-Received-Date: Thu, 03 Jun 2010 21:06:56 -0000

Thanks for the update.


On 6/3/10 4:01 PM, "Riegel, Maximilian" <maximilian.riegel@nsn.com>; wrote:

> Raj,
> 
> The new IP-CS is not based on GP-CS, but is a special version of the
> IP-CS introduced in the IEEE802.16-2009 specification.

So this enhanced IP-CS is different in some ways from the legacy IPv4CS and
IPv6CS? 

It may be useful to specify IPv4/v6 over this revised IP-CS rather than just
merging the previous documents into a new I-D. You could reuse quite a lot
of the text but you need to consider the changes that have been made to this
.16-2009 IP-CS version.

-Raj

> There is still
> quite some legacy thinking but meanwhile a common sense is established,
> that this 'common' IP-CS is the way forward for 802.16m.
> 
> Bye
> Max
> 
> -----Original Message-----
> From: ext Patil Basavaraj (Nokia-D/Dallas)
> [mailto:Basavaraj.Patil@nokia.com]
> Sent: Thursday, June 03, 2010 10:44 PM
> To: Riegel, Maximilian (NSN - DE/Munich); 16ng@ietf.org
> Subject: Re: [16NG] I-D
> Action:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-07.txt
> 
> 
> Max,
> 
> Is the new IP-CS based on GPCS? If so, I believe it is better to write a
> separate I-D which specifies v4 and v6 transport over such a convergence
> sublayer.
> 
> -Raj
> 
> 
> On 6/3/10 3:40 PM, "Riegel, Maximilian" <maximilian.riegel@nsn.com>;
> wrote:
> 
>> Is it really reasonable to progress this I-D towards RFC? Meanwhile
>> IEEE802.16 as well as WiMAX Forum are moving towards an combined
> IP-CS,
>> which is capable to transfer IPv4 packets as well as IPv6 packets over
>> the same service flows.
>> 
>> IMHO, it would make much more sense to merge the IPv6-CS and the
> IPv4-CS
>> specification text into a common IP-CS text.
>> 
>> Bye
>> Max
>> 
>> -----Original Message-----
>> From: 16ng-bounces@ietf.org [mailto:16ng-bounces@ietf.org] On Behalf
> Of
>> ext Internet-Drafts@ietf.org
>> Sent: Thursday, June 03, 2010 5:00 AM
>> To: i-d-announce@ietf.org
>> Cc: 16ng@ietf.org
>> Subject: [16NG] I-D
>> Action:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-07.txt
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the IP over IEEE 802.16 Networks Working
>> Group of the IETF.
>> 
>> 
>>         Title           : Transmission of IPv4 packets over IEEE
>> 802.16's IP Convergence Sublayer
>>         Author(s)       : S. Madanapalli, et al.
>>         Filename        :
>> draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-07.txt
>>         Pages           : 13
>>         Date            : 2010-06-02
>> 
>> IEEE 802.16 is an air interface specification for wireless broadband
>> access.  IEEE 802.16 has specified multiple service specific
>> Convergence Sublayers for transmitting upper layer protocols.  The
>> packet CS (Packet Convergence Sublayer) is used for the transport of
>> all packet-based protocols such as Internet Protocol (IP) and IEEE
>> 802.3 (Ethernet).  The IP-specific part of the Packet CS enables the
>> transport of IPv4 packets directly over the IEEE 802.16 Media Access
>> Control (MAC).
>> 
>> This document specifies the frame format, the Maximum Transmission
>> Unit (MTU) and address assignment procedures for transmitting IPv4
>> packets over the IP-specific part of the Packet Convergence Sublayer
>> of IEEE 802.16.
>> 
>> A URL for this Internet-Draft is:
>> 
> http://www.ietf.org/internet-drafts/draft-ietf-16ng-ipv4-over-802-dot-16
>> -ipcs-07.txt
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>> _______________________________________________
>> 16NG mailing list
>> 16NG@ietf.org
>> https://www.ietf.org/mailman/listinfo/16ng
> 
> 
> _______________________________________________
> 16NG mailing list
> 16NG@ietf.org
> https://www.ietf.org/mailman/listinfo/16ng