From: Hannes Reinecke <hare@suse.de>
To: Chuck Lever III <chuck.lever@oracle.com>,
kernel-tls-handshake <kernel-tls-handshake@lists.linux.dev>
Subject: Re: NVMe standards for TLS
Date: Sat, 7 Oct 2023 10:10:01 +0200 [thread overview]
Message-ID: <fa244391-805c-4595-9038-e6dff725e1c0@suse.de> (raw)
In-Reply-To: <6CC80C5D-CB9F-412D-BF93-B1F5C391707A@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
On 10/6/23 19:33, Chuck Lever III wrote:
> Hi-
>
> I'm finishing up some slides for NetDev 0x17 describing the in-kernel
> TLS handshake facility. For use cases, I have listed RPC-with-TLS,
> QUICv1, and NVMe. Does someone have a reference to the NVMe
> specification for using TLS that I can cite?
>
That's in the NVMe-of TCP Transport Specification. PDF is attached.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Ivo Totev, Andrew
Myers, Andrew McDonald, Martje Boudien Moerman
[-- Attachment #2: NVM Express TCP Transport Specification 1.0c 2022.10.03 Ratified.pdf --]
[-- Type: application/pdf, Size: 754067 bytes --]
prev parent reply other threads:[~2023-10-07 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 17:33 NVMe standards for TLS Chuck Lever III
2023-10-07 8:10 ` Hannes Reinecke [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=fa244391-805c-4595-9038-e6dff725e1c0@suse.de \
--to=hare@suse.de \
--cc=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@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).