Re: [16NG] Re: traffic classification
Alexandru Petrescu <alexandru.petrescu@motorola.com> Wed, 31 January 2007 17:25 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1HCJCk-0006We-QT; Wed, 31 Jan 2007 12:25:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1HCJCi-0006TJ-1D
for 16ng@ietf.org; Wed, 31 Jan 2007 12:25:04 -0500
Received: from mail153.messagelabs.com ([216.82.253.51])
by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HCJAv-00059F-55
for 16ng@ietf.org; Wed, 31 Jan 2007 12:23:15 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-5.tower-153.messagelabs.com!1170264191!370254!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 14484 invoked from network); 31 Jan 2007 17:23:11 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
by server-5.tower-153.messagelabs.com with SMTP;
31 Jan 2007 17:23:11 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l0VHN2IX027487;
Wed, 31 Jan 2007 10:23:02 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id l0VHN10w027981;
Wed, 31 Jan 2007 11:23:01 -0600 (CST)
Message-ID: <45C0D074.5080000@motorola.com>
Date: Wed, 31 Jan 2007 18:23:00 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: yw_chen <ywchen@ee.ncu.edu.tw>
Subject: Re: [16NG] Re: traffic classification
References: <45BDFD58.8060202@piuha.net>
<45C099CD.8010506@piuha.net> <45C0A227.1040303@motorola.com>
<45C0A4D1.9010602@piuha.net> <92e919fb0701310737m45cbb6f8ud1dab68aa75f380d@mail.gmail.com>
<20070131161106.M971@ee.ncu.edu.tw>
In-Reply-To: <20070131161106.M971@ee.ncu.edu.tw>
Content-Type: text/plain; charset=Big5
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: 16ng@ietf.org, Pekka Savola <pekkas@netcore.fi>
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
Hi yw_chen,
yw_chen wrote:
> Dear All,
>
> I am Yen-Wen Chen from Dept. of Communication Engineering, National
> Central University, Taiwan. As I know that the classifier in 802.16
> is applied to match the network layer traffic (e.g. IP packets or
> IPv6 packets) into MAC flows of 802.16. Each MAC flow has a
> connection ID (CID) and is associated with a specific forwarding
> class (e.g. UGS, rtPS, nrtPS, ertPS, or best effort) and QoS-related
> parameters (e.g. delay time, loss rate, etc.). The mapping rules does
> not specify in the spec. and is decided in accordance with different
> applications.
I believe when 802.16 spec says 'in accordance with different
applications' it means IP is one of those applications.
I think both the 802.16MAC implementation _and_ the IPv6 stack should
respect the same - unwritten - mapping rules. Otherwise my IPv6 stack
on a vendor's 802.16MAC won't work on another vendor's.
> Packets with different IP Headers may be mapped to the same CID if
> those packets are with the same treatment in the link layer of
> 802.16.
I'm fine with that.
But does IPv6 DSCP AF11 '001010' (rfc2597) map into 'UGS' or into 'Best
Effort' forwarding class (802.16)? Which one do you like more? Which
one is implemented?
Alex
PS: 802.16 terms: UGS - Unsolicited Grant Service
rtPS - real-time Polling Services
nrtPS - non-real-time Polling Services
ertPS - ??
_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng
- [16NG] FW: Review of the ipv6-over-ipv6cs draft Jari Arkko
- Re: [16NG] FW: Review of the ipv6-over-ipv6cs dra… Jari Arkko
- Re: traffic classification (was: [16NG] FW: Revie… Alexandru Petrescu
- [16NG] Re: traffic classification Jari Arkko
- Re: [16NG] Re: traffic classification JinHyeock Choi
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: traffic classification yw_chen
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- [16NG] Re: Review of the ipv6-over-ipv6cs draft Basavaraj Patil
- [16NG] Re: Review of the ipv6-over-ipv6cs draft Pekka Savola
- Re: [16NG] Re: traffic classification JinHyeock Choi
- [16NG] Re: Review of the ipv6-over-ipv6cs draft Basavaraj Patil
- [16NG] Re: Review of the ipv6-over-ipv6cs draft Pekka Savola
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: Review of the ipv6-over-ipv6cs dra… JinHyeock Choi
- DNA and using 3*MaxRtrAdvInterval [Re: [16NG] Re:… Pekka Savola
- [16NG] Re: Review of the ipv6-over-ipv6cs draft Basavaraj Patil
- Re: [16NG] Re: traffic classification JinHyeock Choi
- Re: DNA and using 3*MaxRtrAdvInterval [Re: [16NG]… JinHyeock Choi
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: traffic classification Jari Arkko
- RE: [16NG] Re: traffic classification Riegel, Maximilian
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: traffic classification Basavaraj Patil
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: traffic classification Jari Arkko
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: traffic classification Basavaraj Patil
- Re: [16NG] Re: traffic classification Basavaraj Patil