Re: use of radiotap bit 14?
Johannes Berg <[email protected]>
| Newsgroups | org.netbsd.radiotap |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 2008-06-19 at 14:13 -0400, Pavel Roskin wrote: > On Thu, 2008-06-19 at 19:44 +0200, Johannes Berg wrote: > > Ok, I tried collecting all the information, and here's what I found so > > far: > > > > http://www.radiotap.org/suggested-fields > > > > Bits 14, 15 and 16 are defined twice. > > If we call those fields "suggested", we deceive ourselves. Suggested > fields should not come with bit numbers. There bit numbers should be > assigned only when the suggestion is accepted. Well, yes, but it seemed prudent to not introduce a third "used-but-not-standardised" category and these bit numbers reflect the fact that they are indeed used with those bit numbers in varying OSes. I hope the audience of this website is smart enough to realise that. > Perhaps you could add your proposal without a bit number and then ask > for the numbers to be assigned? If 19 is the lowest uncontested number, > then it would be assigned. > > There is no need to wait with your proposals until the contested fields > controversy is resolved. Well, I don't have a proposal yet, those fields that are there are sufficient if we also accept the vendor-namespaces idea that I'm just trying to put into understandable words. johannes
signature.asc
(application/pgp-signature, 836 B)
-----BEGIN PGP SIGNATURE----- Comment: Johannes Berg (powerbook) iQIcBAABAgAGBQJIWqMGAAoJEKVg1VMiehFYfxUQAKG2CBhZxVLt8s8rDF+Sc4bb yktHcuL0FXsRj2CnGl2ZhfYvwVb8XuZLSYMVNdEYFsk2pKK6xMwSl0q5lERkGIVn rix2qSoa4PZE0TSZiIl+mjYWH9Sk1Ix7VMiwyvzFSLiwtWje+973sm5SOJeWeF/a QM4IRfW9AUvBsLo2Y3mXeJ45jxJjSPTxI4GMamxgDj5nrmSdcSuZcx+hIYah9pi0 XOkk+DB4Ugx6oveZNbZnj0mNFTFkg4GnRvOgLecIXQ7DlUDsdp6+g9xSKPyDWVj/ bQgFmxA6drRrysO/yC/ii0wOp4UzKoUDOZl69T0P5l2soDMaJxC0JaU40/2w7mU2 YeJOvDuVGVWANppbfc6ibqPhReG4c3YQP3tVZgvgSuopcvH08z9B6l7CjAejj5fQ Stglqvpm0hNFJvx+Y8ukcNuSJ40s5cCK6nGwoFBkMuMyJKMcrINJEQe4KCT6Njqv 0Yk5sd/zU0jOiJ1qsFtxOPtDMFp6Qnoh8by0mNIS9u7R9lVdPAW4pnzUJEMNNuAt NVK5+l9OmkqC7YyOF35WKcJvNyXnsVavJSt+94JJIzn8gWRQODTB4M1ZigPYfMtJ H2t01nuHmzv1NMvLpYuHHtN76EZwaBDMLd+xne9u2ZSkSbHaQj0au6zk22iHNlF1 uUGhEHniLGgovYDRFYFl =V0Xg -----END PGP SIGNATURE-----