Re: traffic class (was: [16NG] Review of draft-ietf-16ng-ipv6-over-ipv6cs-07.txt)

[Alexandru Petrescu <alexandru.petrescu at motorola.com>]

Jari Arkko wrote:
> Margaret, Basavaraj,
>
> First, thank you Margaret for your review! I talked to the chairs and
>  Basavaraj, and they will revise the document according to your and 
> Pekka's comments.
>
> Please find some observations inline wrt to the biggest substantial 
> comments.
[...]
> > For transmission of IPv6 packets via the IP specific part of the 
> > Packet CS of 802.16, the IPv6 layer interfaces with the 802.16 MAC 
> > directly.  The IPv6 layer delivers the IPv6 packet to the Packet CS
> > of the 802.16.  The packet CS defines a set of classifiers that are
> > used to determine how to handle the packet.  The IP classifiers 
> > that are used at the MAC operate on the fields of the IP header and
> > the transport protocol and these include the IP Traffic class, Next
> >
> >
> >
> > SUBS:  Why include the traffic class and not the entire IPv6 Flow 
> > Label field?
>
> The 802.16 specification determines how the classifers work. We 
> cannot change that (but we are setting up a review with IEEE that 
> would detect differences, if any.)

I _think_ the 802.16 classifiers just list what are the fields in the
IPv6 header that they understand.  I _think_ the 802.16 CS classifiers
don't know how to map the contained values, eg DSCP AF11 '001010'
(rfc2597) into a 802.16 service field.  I _think_ this mapping isn't
specified in 802.16 spec.

I think it should be specified here.

I could formulate that as a question: how does the 802.16 MAC
implementation map the DSCP AF11 into a service flow, what is the mapping?

Alex


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