Message-ID: <4B2F9930.8070401@cosetrain.com>
Date: Mon, 21 Dec 2009 16:50:08 +0100
From: Florian Sesser <flomaillist@cosetrain.com>
MIME-Version: 1.0
To: linux-wireless@vger.kernel.org
Subject: o11s: Modularize Path Selection Protocol etc.
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-wireless-owner@vger.kernel.org

Hi mesh folks!

For my diploma thesis, I want to add a P2P routing protocoll to the
pre-80211s software in the linux kernel. For details, see my previous
mails. [1],[2]

In struct ieee80211_if_mesh, the current code reads

net/mac80211/ieee80211_i.h
>         u8 mesh_id[IEEE80211_MAX_MESH_ID_LEN];
>         size_t mesh_id_len;
>         /* Active Path Selection Protocol Identifier */
>         u8 mesh_pp_id;
>         /* Active Path Selection Metric Identifier */
>         u8 mesh_pm_id;
>         /* Congestion Control Mode Identifier */
>         u8 mesh_cc_id;
>         /* Synchronization Protocol Identifier */
>         u8 mesh_sp_id;
>         /* Authentication Protocol Identifier */
>         u8 mesh_auth_id;

which is what I at first wanted to work with.

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.

So.. am I erring here?

If yes, I would introduce a new 24 bit value for the OUI, which will be
combined with all the above u8's before going over the wire (into the
air of course)
...if no, I would replace those values by 32 bit ones, possibly even
braking ABI compatibility.

What do you think?
Do you maybe have a better suggestion?

Thank you very much for your input!


Florian

[1] http://marc.info/?l=linux-wireless&m=122600107811517&w=2
[2] http://marc.info/?l=linux-wireless&m=123300309207545&w=2