From: Jouni Malinen <j@w1.fi>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: "Ледовских Николай Валерьевич" <nledovskih@mail.ru>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: fix ieee80211_meshconf_ie::meshconf_cap type to be u16
Date: Mon, 5 Apr 2010 10:38:01 +0300 [thread overview]
Message-ID: <20100405073801.GA28792@jm.kir.nu> (raw)
In-Reply-To: <201004042359.52494.jcmvbkbc@gmail.com>
On Sun, Apr 04, 2010 at 11:59:52PM +0400, Max Filippov wrote:
> > On Sun, 4 Apr 2010 14:12:44 +0400
> > Max Filippov <jcmvbkbc@gmail.com> wrote:
> >
> > > According to the current 802.11s draft mesh capability field
> > > is 16 bits wide.
This does not match with the latest 802.11s draft. Please also specify
the draft version in the commit message to make this easier to notice.
802.11s is still a moving target and unless we have a clearly specified
older version of the draft that we try to follow, I don't see much point
in updating this field based on some older version (D4.0) when the field
has already changed since then (D5.0).
> > > - u8 meshconf_cap;
> > > + u16 meshconf_cap;
> My reference is 802.11s-D4.01, it says (7.3.2.95.1):
That is not the latest draft. IEEE P802.11s/D5.0 7.3.2.96.1 shows the
Mesh Capability to be a one octet field.
> Element id: 1 octet,
> Length: 1 octet,
> Active path selection protocol identifier: 1 octet,
> Active path selection metric identifier: 1 octet,
> Congestion control mode identifier: 1 octet,
> Synchronization protocol identifier: 1 octet,
> Authentication protocol identifier: 1 octet,
> Mesh formation info: 1 octet,
> Mesh capability: 2 octets.
>
> The length field is set to 8.
Length is still 8, but there is a new field (Mesh Peering Protocol
Identifier) before Mesh Formation Info (and Mesh capability is 1 octet).
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2010-04-05 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 10:12 [PATCH] mac80211: fix ieee80211_meshconf_ie::meshconf_cap type to be u16 Max Filippov
2010-04-04 18:07 ` Felix Fietkau
2010-04-04 19:39 ` Max Filippov
2010-04-04 19:50 ` [PATCH] mac80211: fix ieee80211_meshconf_ie::meshconf_cap type to be __le16 Max Filippov
2010-04-04 19:45 ` [PATCH] mac80211: fix ieee80211_meshconf_ie::meshconf_cap type to be u16 Ледовских Николай Валерьевич
2010-04-04 19:59 ` Max Filippov
2010-04-05 7:38 ` Jouni Malinen [this message]
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=20100405073801.GA28792@jm.kir.nu \
--to=j@w1.fi \
--cc=jcmvbkbc@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nledovskih@mail.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.