On Tue, 2009-12-01 at 08:43 -0800, Luis R. Rodriguez wrote:

> Wanted to clarify, on the vendor it_present bitmap, does it always
> have to also respect the bit for vendor extension bit 30? The current
> proposal seems to have language which would indicates so:
> 
> "This field is reserved in all namespaces and every it_present word,
> the standard radiotap namespace as well as all vendor namespaces. "

Yes, we have already reserved bit 31 in all it_present words, and now we
also reserve bits 29 and 30, so that vendor extensions can only use
numbers 0-28, 32-60, 64-92, ...

> If so what is the point of the reset bit? What I mean is that if we
> give radiotap its own OUI technically we could just reset ourselves to
> the radiotap namespace by specifying the radiotap OUI with what I'd
> think would be optional radiotap subnamespace material (length could
> be 0 I take it).

Well I personally would rather reserve a bit than try to come up with a
radiotap OUI (how would it get that?) and then special-casing the length
field etc. That just means _more_ special cases in the parser, rather
than less.

johannes