From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: atul.gupta@chelsio.com, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, netdev@vger.kernel.org,
dt@chelsio.com
Subject: Re: [crypto 0/4] Inline TLS client and v6 support
Date: Thu, 11 Apr 2019 11:52:28 -0700 (PDT) [thread overview]
Message-ID: <20190411.115228.894374097382770159.davem@davemloft.net> (raw)
In-Reply-To: <20190411114506.10d19a40@cakuba.netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Thu, 11 Apr 2019 11:45:06 -0700
> I think the "netdev community" feels pretty strongly about preventing
> protocol ossification and bypassing crucial parts of the infrastructure.
Correct.
next prev parent reply other threads:[~2019-04-11 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 15:22 [crypto 0/4] Inline TLS client and v6 support Atul Gupta
2019-04-09 18:01 ` Jakub Kicinski
2019-04-10 5:26 ` Atul Gupta
2019-04-10 15:58 ` Jakub Kicinski
2019-04-11 4:17 ` Atul Gupta
2019-04-11 16:40 ` Jakub Kicinski
[not found] ` <ae56c100-d072-bf6b-465a-5136d29b84be@chelsio.com>
2019-04-11 18:45 ` Jakub Kicinski
2019-04-11 18:52 ` David Miller [this message]
2019-04-15 9:10 ` Atul Gupta
2019-04-15 9:36 ` Herbert Xu
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=20190411.115228.894374097382770159.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=atul.gupta@chelsio.com \
--cc=dt@chelsio.com \
--cc=herbert@gondor.apana.org.au \
--cc=jakub.kicinski@netronome.com \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).