From: Florian Sesser <flomaillist@cosetrain.com>
To: Rui Paulo <rpaulo@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: o11s: Modularize Path Selection Protocol etc.
Date: Tue, 22 Dec 2009 12:55:47 +0100 [thread overview]
Message-ID: <4B30B3C3.7040602@cosetrain.com> (raw)
In-Reply-To: <7057634E-E560-413E-9FB2-163F5311E054@gmail.com>
Hi Rui!
Thanks for your prompt reply. I will dig into the new draft ASAP.
(It is propably rude to ask for an up to date draft on this list? I
would, of course, discreetly profit from having it handy shortly...)
Greetings!
Florian
Me:
>> [...]
>> In my last patch [2], I introduced some new 32 bit struct
>> members, because, if I am not mistaken, these IDs should include a
>> vendor specific OUI, which enables a user to combine a path
>> selection protocol of vendor A with a path selection metric of
>> vendor B.
Rui:
> This has changed quite a bit on the latest 802.11s draft standards.
> If you want to use your own routing protocol and to be 802.11s
> compliant, you need to set the path selection protocol ID to 255 and
> append a vendor specific information element to the management frame.
> [...]
> Rui Paulo
prev parent reply other threads:[~2009-12-22 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 15:50 o11s: Modularize Path Selection Protocol etc Florian Sesser
2009-12-21 16:17 ` Rui Paulo
2009-12-22 8:33 ` Simon Raffeiner
2009-12-22 11:55 ` Florian Sesser [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=4B30B3C3.7040602@cosetrain.com \
--to=flomaillist@cosetrain.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rpaulo@gmail.com \
/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).