Another thought that crossed my mind is how to handle off-channel TDLS. I'm sure it'll become a requirement fairly soon, and I think we'll want to design it into the stack. I wish I could gather a few people into a room and sit there for a few days brainstorming how it should look like (and how to implement backward compatibility!) .... :-) Anyway so my thought about off-channel TDLS was -- should we maybe assign a channel to each station? Obviously each station associated to an AP would have the same channel. That might make channel switching (CSA) a little interesting, but hey ... In our device we'll probably not handle it this way, but it seems like the best abstraction? Also I think we should probably have some explicit channel handling. I'm not thinking about scanning/off-channel operations but about actual use of the channel. There could be some weight requests for the different channels depending on airtime needs, but ultimately the driver will probably have to make the timing decisions and will communicate that up to make negotiation between devices possible for this. NoA might be handled in the driver right now, but I think TDLS negotiation for channels would not be, and there you need timings... johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
