From: Eric Curtin <ericcurtin17@gmail.com>
To: vfedorenko@novek.ru
Cc: aahringo@redhat.com, linux-cifs@vger.kernel.org,
linux-nfs@vger.kernel.org, lsahlber@redhat.com,
netdev@vger.kernel.org, smfrench@gmail.com, swhiteho@redhat.com
Subject: Re: quic in-kernel implementation?
Date: Sun, 5 Sep 2021 15:09:31 +0100 [thread overview]
Message-ID: <20210905140931.345774-1-ericcurtin17@gmail.com> (raw)
In-Reply-To: <9ce530f5-cfe7-b1d4-ede6-d88801a769ba@novek.ru>
Hi Guys,
Great idea, something I have been hoping to see in the kernel for a
while. How has your implementation been going @Vadim? I'd be interested
in a non-encrypted version of QUIC also in the kernel (may not be
supported in the spec but possible and I think worth having), would be
useful for cases where you don't care about network ossification
protection or data-in-transit encryption, say a trusted local network
where you would prefer the performance and reliability advantages of
going plaintext and you don't want to figure out how to deploy
certififcates. Something that could be used as a straight swap for a
TCP socket.
next prev parent reply other threads:[~2021-09-05 14:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 15:25 quic in-kernel implementation? Alexander Ahring Oder Aring
2021-06-07 16:45 ` Aurélien Aptel
2021-06-08 3:04 ` Steve French
2021-06-08 7:36 ` Stefan Metzmacher
2021-06-08 21:03 ` Alexander Aring
2021-06-08 22:33 ` Stephen Hemminger
2021-06-09 16:48 ` Jakub Kicinski
2021-06-09 18:44 ` Alexander Aring
2021-06-13 12:17 ` David Laight
2021-06-13 18:08 ` Alexander Aring
2021-06-08 21:26 ` Chuck Lever III
2021-06-07 17:29 ` Chuck Lever III
2021-06-08 20:51 ` Vadim Fedorenko
2021-06-08 21:06 ` Alexander Aring
2021-06-09 0:27 ` Vadim Fedorenko
2021-09-05 14:09 ` Eric Curtin [this message]
2021-09-05 23:38 ` Steve French
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=20210905140931.345774-1-ericcurtin17@gmail.com \
--to=ericcurtin17@gmail.com \
--cc=aahringo@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=swhiteho@redhat.com \
--cc=vfedorenko@novek.ru \
/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).