[16NG] Re: traffic classification

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

Jari

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