From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: "Joshua (Shiwei) Zhao" <swzhao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Radiotap <radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>,
Gerald Combs <gerald-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
Subject: Re: [RFA] namespaces and vendor extensions
Date: Tue, 01 Dec 2009 10:16:51 +0100 [thread overview]
Message-ID: <1259659011.32171.45.camel@johannes.local> (raw)
In-Reply-To: <d521a2310911301441l3c5503b5hf43d31a47e83fe4b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
Joshua,
> For the structure of the vendor space, you extend 'skip_length' from 8
> bits to 16 bits.
> > Structure
> > u8 OUI[3], u8 sub_namespace, __le16 skip_length
> I'm neutral on that. My question is why not extend 'sub_namespace' to
> 16 bits too?
I don't see much point in having more than 255 sub-namespaces per OUI,
do you?
> I hardly see that a vendor extension part can go over 255
> bytes. But if that happens, it's quite likely that the extension may
> contain more than 8 fields.
Where are you taking 8 fields from? After the vendor extensions bit, the
vendor extension puts vendor-defined presence bits into the it_present
bitmap. Therefore, you have an unlimited number of fields per vendor
sub-namespace, as such I see little reason to support more than 255
sub-namespaces.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-12-01 9:16 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 [this message]
[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
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=1259659011.32171.45.camel@johannes.local \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=gerald-IZ8446WsY0/dtAWm4Da02A@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org \
--cc=swzhao-Re5JQEeQqe8AvxtiuMwx3w@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;
as well as URLs for NNTP newsgroup(s).