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

"Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com> Thu, 03 June 2010 21:01 UTC

Return-Path: <maximilian.riegel@nsn.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 115273A6A35 for <16ng@core3.amsl.com>; Thu, 3 Jun 2010 14:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level:
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=0.745, BAYES_00=-2.599]
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 xvf6NmCHIH-Z for <16ng@core3.amsl.com>; Thu, 3 Jun 2010 14:01:35 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id BD5B63A6A2D for <16ng@ietf.org>; Thu, 3 Jun 2010 14:01:34 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o53L1JsX022241 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <16ng@ietf.org>; Thu, 3 Jun 2010 23:01:19 +0200
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o53L1GQU008902 for <16ng@ietf.org>; Thu, 3 Jun 2010 23:01:19 +0200
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Thu, 3 Jun 2010 23:01:13 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 3 Jun 2010 23:01:11 +0200
Message-ID: <BC27158B99D3064A955ADE084783900C03817889@DEMUEXC014.nsn-intra.net>
In-Reply-To: <C82D7E30.954D%basavaraj.patil@nokia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [16NG] I-D Action:draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-07.txt
thread-index: AcsCyP3ZBHNAbCjOQayyAgLl5L5ETwAk2FIgAABFdyEAAHpTUA==
References: <BC27158B99D3064A955ADE084783900C03817880@DEMUEXC014.nsn-intra.net> <C82D7E30.954D%basavaraj.patil@nokia.com>
From: "Riegel, Maximilian (NSN - DE/Munich)" <maximilian.riegel@nsn.com>
To: "ext Patil Basavaraj (Nokia-D/Dallas)" <Basavaraj.Patil@nokia.com>, <16ng@ietf.org>
X-OriginalArrivalTime: 03 Jun 2010 21:01:13.0419 (UTC) FILETIME=[E68121B0:01CB035F]
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:01:36 -0000

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. 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