| Re: capwap transport analysis: QoS vs multiport | <– Date –> <– Thread –> |
|
From: Bob O'Hara (boohara) (boohara |
|
| Date: Wed, 14 Jun 2006 10:42:32 -0700 (PDT) | |
Scott, Your reformulation of premise (4) is closer to my intent, but still off the mark. This is what I would prefer to see from premise (4): (4) many of these elements only classify traffic based on 5-tuples, due to administrative or policy constraints; they will not use AC/WTP-provided VLAN tags or DSCP/802.1q/802.1d markings for QoS purposes -Bob -----Original Message----- From: Scott G. Kelly [mailto:s.kelly [at] ix.netcom.com] Sent: Tuesday, June 13, 2006 10:42 AM To: Bob O'Hara (boohara); capwap Subject: Re: [Capwap] capwap transport analysis: QoS vs multiport Hi Bob, boohara wrote: > >Scott wrote: > >>So if the AC and WTP were to mark control packets >>so as to make them distinguishable from data packets >>(using one of the marking methods suggested above, >>and without relying on client truthfulness), what >>problems remain? > >As Pat points out in a separate email, the problem of controlling how >the WTP marks those packets remains to be solved. But, that discussion >can continue in Pat's thread. > >Another problem is that the WTP, itself, is not trusted by the network >to which it is attached. A widespread example is a network of WLAN >hotspots. The WTPs at the hotspot are connected to the AC over a third >party's network. > >In some of those hotspots, the WTP will be local-MAC. A hotspot user's >packets from a local-MAC WTP will be able to be inspected at ingress to >the third party's network, since the 5-tuple is clearly available in >those packets. QoS can be applied to those user data packets, without >requiring any changes to the third party's network equipment. > >However, if those same packets are sent to the AC by a split-MAC WTP, >the third party network will not be able to distinguish control packets >from data packets, unless they are sent on separate ports. In the >CAPWAP packet, the 5-tuple is the same for both control and data. Keeping in mind that what we are trying to do is ascertain whether premise (4) was correctly formulated, let me re-state that in its original form: (4) many of these elements can only classify traffic based on 5-tuples; they apparently cannot use VLAN tags or 1:1 mappings of DSCP/802.1q/802.1d mappings Apparently, what is at issue is the phrase "1:1 mappings of" - if I apply what you've said above to this premise, it seems that this would be an acceptable re-formulation: (4) many of these elements can only classify traffic based on 5-tuples; they apparently cannot use AC/WTP-provided VLAN tags or DSCP/802.1q/802.1d markings for QoS purposes Does this reflect your intent? Thanks, Scott
- Re: capwap transport analysis: QoS vs multiport, (continued)
- Re: capwap transport analysis: QoS vs multiport Scott G Kelly, June 13 2006
- Re: capwap transport analysis: QoS vs multiport Bob O'Hara (boohara), June 13 2006
-
Re: capwap transport analysis: QoS vs multiport Scott G. Kelly, June 13 2006
- Re: capwap transport analysis: QoS vs multiport Michael.G.Williams, June 13 2006
- Re: capwap transport analysis: QoS vs multiport Bob O'Hara (boohara), June 14 2006
Results generated by Tiger Technologies using MHonArc.