Issue169

Title What to do with QoS tags exceeding maximum
Priority bug Status resolved
Superseder Nosy List pcalhoun
Assigned To pcalhoun Topics

Created on 2008-07-30.23:27:15 by pcalhoun, last changed 2008-08-20.13:31:44 by pcalhoun.

Messages
msg503 (view) Author: pcalhoun Date: 2008-08-20.13:31:44
Fixed in draft-ietf-capwap-protocol-specification-12.txt
msg493 (view) Author: pcalhoun Date: 2008-08-13.21:53:58
I will make a recommendation that we simply down-tag. I think dropping the 
packet will cause nothing but a communication outage, which can lead to a very 
difficult troubleshooting session. So the new text is:

<new text>
6.14.  IEEE 802.11 Station QoS Profile

   The IEEE 802.11 Station QoS Profile message element contains the
   maximum IEEE 802.11e priority tag that may be used by the station.
   Any packet received that exceeds the value encoded in this message
   element MUST be tagged using the maximum value permitted by to the
   user.  The priority tag MUST be between zero (0) and seven (7).  This
   message element MUST NOT be present without the IEEE 802.11 Station
   (see Section 6.13) message element
</new text>
msg451 (view) Author: pcalhoun Date: 2008-07-30.23:27:15
> Section 6.14 says that packets exceeding this priority are either dropped 
or "down-tagged" -- but it seems which of 
> these is done depends on WTP (and the AC can't even know what the WTP 
does).  
> Isn't this problematic for interoperability?
History
Date User Action Args
2008-08-20 13:31:44pcalhounsetstatus: chatting -> resolved
messages: + msg503
2008-08-13 21:53:58pcalhounsetstatus: unread -> chatting
messages: + msg493
2008-07-30 23:27:15pcalhouncreate