From: David Young <dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: Radiotap <radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>
Subject: Re: [RFA] namespaces and vendor extensions
Date: Tue, 1 Dec 2009 11:31:23 -0600 [thread overview]
Message-ID: <20091201173122.GD6179@ojctech.com> (raw)
In-Reply-To: <1259687018.32171.96.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
On Tue, Dec 01, 2009 at 06:03:38PM +0100, Johannes Berg wrote:
> On Tue, 2009-12-01 at 08:43 -0800, Luis R. Rodriguez wrote:
> > 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.
I'm not keen on adding a special case to the length field, either.
Implementing the namespace-reset bit is simple.
I foresee using namespace reset a lot in the same header [1]. Using a
vendor extension field of 5-plus bytes each time, instead, will use a
lot of bytes fast!
I think that getting an OUI for Radiotap would be expensive.
Dave
[1] I'm thinking of using namespace-reset in re-transmission histories/strategies.
--
David Young OJC Technologies
dyoung-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org Urbana, IL * (217) 278-3933
next prev parent reply other threads:[~2009-12-01 17:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 17:55 [RFA] namespaces and vendor extensions Johannes Berg
[not found] ` <1259258152.32372.90.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-11-30 22:41 ` Joshua (Shiwei) Zhao
[not found] ` <d521a2310911301441l3c5503b5hf43d31a47e83fe4b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-12-01 9:16 ` Johannes Berg
[not found] ` <1259659011.32171.45.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-12-01 16:32 ` Joshua (Shiwei) Zhao
2009-12-01 16:43 ` Luis R. Rodriguez
[not found] ` <43e72e890912010843y208201aawb2ad95cbec98c814-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-12-01 17:03 ` Johannes Berg
[not found] ` <1259687018.32171.96.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-12-01 17:31 ` David Young [this message]
2009-12-01 17:46 ` Luis R. Rodriguez
2009-12-01 17:05 ` Gerald Combs
[not found] ` <4B154CD4.8020700-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
2009-12-01 21:37 ` Luis R. Rodriguez
[not found] ` <43e72e890912011337l704c68ebscea8fd23160f7a8b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-12-01 23:11 ` Johannes Berg
2009-12-01 23:08 ` Johannes Berg
[not found] ` <1259708896.32171.132.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2010-01-06 17:22 ` Johannes Berg
[not found] ` <1262798525.30225.15.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2010-01-09 0:18 ` Gerald Combs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091201173122.GD6179@ojctech.com \
--to=dyoung-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox