Re: [16NG] Re: traffic classification

"yw_chen" <ywchen@ee.ncu.edu.tw> Wed, 31 January 2007 16:41 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCIWa-0003rA-Gu; Wed, 31 Jan 2007 11:41:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCHyb-0000Em-Fz for 16ng@ietf.org; Wed, 31 Jan 2007 11:06:25 -0500
Received: from webmail.ee.ncu.edu.tw ([140.115.70.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCHyS-0004av-3F for 16ng@ietf.org; Wed, 31 Jan 2007 11:06:25 -0500
Received: from ee.ncu.edu.tw (localhost [127.0.0.1]) by webmail.ee.ncu.edu.tw (8.13.4/8.13.1) with ESMTP id l0VGLCER036303; Thu, 1 Feb 2007 00:21:13 +0800 (CST) (envelope-from ywchen@ee.ncu.edu.tw)
From: "yw_chen" <ywchen@ee.ncu.edu.tw>
To: "JinHyeock Choi" <jinchoe@gmail.com>, "Jari Arkko" <jari.arkko@piuha.net>
Subject: Re: [16NG] Re: traffic classification
Date: Thu, 1 Feb 2007 00:21:12 +0800
Message-Id: <20070131161106.M971@ee.ncu.edu.tw>
In-Reply-To: <92e919fb0701310737m45cbb6f8ud1dab68aa75f380d@mail.gmail.com>
References: <45BDFD58.8060202@piuha.net> <45C099CD.8010506@piuha.net> <45C0A227.1040303@motorola.com> <45C0A4D1.9010602@piuha.net> <92e919fb0701310737m45cbb6f8ud1dab68aa75f380d@mail.gmail.com>
X-Mailer: Open WebMail 2.51 20050228
X-OriginatingIP: 220.139.159.79 (ywchen)
MIME-Version: 1.0
Content-Type: text/plain; charset=big5
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
X-Mailman-Approved-At: Wed, 31 Jan 2007 11:41:29 -0500
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

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

Yen-Wen






On Thu, 1 Feb 2007 00:37:21 +0900, JinHyeock Choi wrote
> > > I think it _may_ be relevant here.  IPv6 has a Traffic Class field with
> > > defined values (see rfc2474 for 6bit DSCP, and rfc2597 for AF Assured
> > > Forwarding values).  802.16 has Service Class service flow encodings
> > > (11.13.4 in 802.16-1004).  The mapping between the two should be
> > > specified here I believe.
> > >
> > > Basically one would need to define mappings between DSCPs and 802.16
> > > Service Flow encodings.  Remark the mapping is not straightforward
> > > because DSCP uses 6bit while service field is on 4bit.  But not all
> > > values from 6bit need to be encoded either.
> > >
> > > I think 802.16 spec doesn't define these mappings.  Although they do
> > > define filter in the CS that interprets the IPv6 Traffic Class field.
> >
> > Anyone who understands in detail what 802.16 classification
> > does, feel free to jump in here... DJ?
> >
> > My assumption was that 802.16 defines a classification mechanism
> > that can look at certain fields from IP packets and determine what
> > service flow should be used, including all parameters used in the
> > service flow. If this is not the case then you are right.
> 
> Classification is the process by which a MAC SDU (IPv6 packet in our
> case) is mapped onto a particular transport connection for
> transmission between MAC peers (BS and MS in our case). The mapping
> process associates an IPv6 packet with a transport connection and its
> CID (Connection Identifier).
> 
> Classifiers are matching criteria applied to each packet and consist
> of some protocol-specific packet matching criteria such as 
> destination IP address. If a packet matches the specified packet 
> matching criteria
> (i.e. classifier(s)), it is then delivered to the SAP for delivery 
> on the connection defined by the CID (Connection Identifier).
> 
> You may find more detail in 5.2.2 of 802.16. I also put a figure in
> 
> http://www.diffeo.com/16ng/fig.gif
> 
> Thanks for your kind consideration.
> 
> Best Regards
> 
> JinHyeock
> 
> _______________________________________________
> 16NG mailing list
> 16NG@ietf.org
> https://www1.ietf.org/mailman/listinfo/16ng


--
Open WebMail Project (http://openwebmail.org)


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