From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Headers gain 3 bytes of reserved zeros
Date: Fri, 16 Dec 2016 05:47:33 +0100 [thread overview]
Message-ID: <CAHmME9pWnPunbQdPTKwbmvTSR8Yq4LhRBjEfR0xa7AdXDH669g@mail.gmail.com> (raw)
I did it. White paper updated. Protocol webpage updated.
Benefits:
- Natural 4 byte alignment of ciphertext, which confers significant
speedups on many platforms
- Natural 4 byte alignment of resultant plaintext IP packet; similar speedups.
- Natural integer alignment of index and nonce; similar speedups for
packet lookups.
- Easier to implement in hardware.
- Protocol is more extendable.
Detriments:
- 3 bytes less in the MTU.
This will be part of the next snapshot.
reply other threads:[~2016-12-16 4:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHmME9pWnPunbQdPTKwbmvTSR8Yq4LhRBjEfR0xa7AdXDH669g@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.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).