Re: [16NG] Re: traffic classification

Jari Arkko wrote:
> There are a couple of issues. The main technical question is whether 
> host and base station need to be synchronized with respect to the CID
> etc that they use. For instance, if the host puts something in CID =
> X and the base station drops it because it felt that it should have
> travelled in CID = Y. If they need to be synchronized, then we can
> talk about whether that's something that should be left to policy or
> mandated in the standards.

I think SS and BS need to be sync'ed about what traffic class they
choose for what CIDs.

Currently I think it should be mandated in standards that certain IPv6
Traffic Class DSCPs match to certain 802.16 Traffic Priority _or_
Service Class Name.

> I think it is pretty obvious that we're not mandating what port 
> numbers or address ranges should be treated in what way;

I agree.

> that's a standard policy/qos filtering function. If you agree, then 
> its not clear to me why DSCP is any different.

I think DSCP is a means to do exactly what 802.16MAC does, but at IP layer.

An implementation that is written such to run over any link-layer but
having the same QoS reservation behaviour can _only_ use DSCP.
802.16MAC could help such an implementation by following mapping rules
recommendations.

> The non-technical issue is whether the topic belongs to the IEEE or 
> IETF standard. My thinking is that it should be an IETF function if 
> and only if IP needs to do something for which there is no 
> corresponding link layer functionality. For instance, we map 
> multicast IP addresses to multicast L2 addresses because there is no 
> L2 multicast address resolution function. In our 16ng case there 
> appears to be a link layer function for mapping IP packets to CIDs. I
>  don't know if that function is perfect or not, but it does seem to 
> be an IEEE issue.

For QoS, there exist no resolution function like ND or DNS that would
resolve a DSCP into a 802.16 Traffic Priority.

Remark I'm not talking about mapping an IPv6 Traffic Class DSCP into a
CID but into a 802.16 Traffic Priority or a 802.16 Service Name.

Alex

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