Re: [16NG] Re: traffic classification

JinHyeock Choi wrote:
> Alex
> 
>>>> More specifically, what is the priority assigned to this
>>>> service flow? ("traffic priority": sec 11.13.5 of 802.16-2004).
>>>> This encoding has values from 0 to 7 with higher numbers
>>>> indicating higher priority.  If not the "traffic priority"
>>>> value then what are the other service flow-specific constants
>>>> that this IPv6 DSCP (diffserv codepoint) converts into.
>>> 
>>> As of my knowledge, there is no rule to convert IPv6 DSCP
>>> (diffserv codepoint) into 802.16 QoS parameter in a deterministic
>>> way. I understand its up to the implementation & policy.
>> 
>> Isn't this an interoperability issue? (between one's phone to one 
>> other's base station).
> 
> I can't think of any but which, I admit, doesn't guarantee there 
> exists none. :-)

JinHyeock, do you think there could have been an interoperability issue
if rfc2464 didn't specify that ff02::1 was mapped into 33:33::1 (IP
multicast address mapped into MAC multicast address)?

Do you think that if my phone puts Traffic Class 001010 (Class 1 Low
Drop Prec rfc2597) into 802.16 Unsolicited Grant Class forwarding class,
but the AP expects Traffic Class 001010 to be on a 802.16 Best Effort
forwarding class - there's no interoperability issue?

I think there may be big interoperability issues.  I agree though that
these issues may be made much more relevant when they arise in
deployments.  Then we can try to document the issues, maybe as an
upgrade to existing documents.  Until then I'll continue putting
whatever I want in my Traffic Class, ie what you call 'implementation
and policy'.  In this way we can agree :-)

Alex

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