($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [RFC 0/5] Initial prep/skeleton for isolating core DPP protocol
Date: Wed, 13 Mar 2024 10:13:06 -0700	[thread overview]
Message-ID: <20240313171311.695830-1-prestwoj@gmail.com> (raw)

Patches 1-4 can be applied any time, they are needed for the refactoring in
further patches but are still a nice improvement on their own.

Patch 5 is the skeleton module for the common DPP code. Don't merge this now
(even if it looks fine), I'd like to at least get the TCP side started before
I lock in the dpp_sm APIs in case there are changes required.

The reason this is being done is to eventually support DPP-over-TCP as well as
add the ability to implement a DPP controller within the IWD source repo which
can use the same state machine as IWD. Doing this requires the TX/RX of DPP
frames be offloaded to the encapsulating protocol (802.11 or TCP). This leaves
the DPP state details within the SM, which can be shared between either
protocol.

James Prestwood (5):
  dpp: prep for moving AAD within dpp_append_wrapped_data
  dpp-util: move AAD logic within dpp_append_wrapped_attributes
  dpp-util: add dpp_append_point
  dpp: use dpp_append_point
  dpp-common: Skeleton for common DPP module

 src/dpp-common.c | 517 +++++++++++++++++++++++++++++++++++++++++++++++
 src/dpp-common.h | 109 ++++++++++
 src/dpp-util.c   | 180 ++++++++++++++++-
 src/dpp-util.h   |   7 +-
 src/dpp.c        | 308 ++++++++++++++--------------
 5 files changed, 948 insertions(+), 173 deletions(-)
 create mode 100644 src/dpp-common.c
 create mode 100644 src/dpp-common.h

--
2.34.1


             reply	other threads:[~2024-03-13 17:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 17:13 James Prestwood [this message]
2024-03-13 17:13 ` [RFC 1/5] dpp: prep for moving AAD within dpp_append_wrapped_data James Prestwood
2024-03-13 17:13 ` [RFC 2/5] dpp-util: move AAD logic within dpp_append_wrapped_attributes James Prestwood
2024-03-13 17:13 ` [RFC 3/5] dpp-util: add dpp_append_point James Prestwood
2024-03-13 17:13 ` [RFC 4/5] dpp: use dpp_append_point James Prestwood
2024-03-13 17:13 ` [RFC 5/5] dpp-common: Skeleton for common DPP module James Prestwood

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=20240313171311.695830-1-prestwoj@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=iwd@lists.linux.dev \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).