Date: Wed, 22 May 2019 07:24:59 -0700
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK22GCKDX4K7BIV5O4N26KHDXEVBNHHBVJKNCE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2743/c494825756@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2743@github.com>
References: <quicwg/base-drafts/pull/2743@github.com>
Subject: Re: [quicwg/base-drafts] Better articulate principles for
 ciphersuites (#2743)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5ce55bbb88042_d653ff3a10cd96814579bc";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/4yeIA2vQnh109BagyWlU_2Iq2NQ>


----==_mimepart_5ce55bbb88042_d653ff3a10cd96814579bc
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

I think I must be entirely missing the point, but I don't understand this:

> An endpoint MUST NOT reject a ClientHello that offers a ciphersuite that ...

Can you please explain how this works? For the sake of argument, TLS_AES_128_CCM_8_SHA256 is not supported, but the peer chooses to use it, and the TLS engine behind it all decides to support it via some configuration that the endpoint is directly aware of.

How does the endpoint now deal with header protection. Is it assumed that this is a TLS black box so it just magically works if the TLS engine has accepted the cipher via some useful API call.

If it is a TLS blackbox API call, how would that work with HW offloading?





-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2743#issuecomment-494825756
----==_mimepart_5ce55bbb88042_d653ff3a10cd96814579bc
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>I think I must be entirely missing the point, but I don't understand this:</p>
<blockquote>
<p>An endpoint MUST NOT reject a ClientHello that offers a ciphersuite that ...</p>
</blockquote>
<p>Can you please explain how this works? For the sake of argument, TLS_AES_128_CCM_8_SHA256 is not supported, but the peer chooses to use it, and the TLS engine behind it all decides to support it via some configuration that the endpoint is directly aware of.</p>
<p>How does the endpoint now deal with header protection. Is it assumed that this is a TLS black box so it just magically works if the TLS engine has accepted the cipher via some useful API call.</p>
<p>If it is a TLS blackbox API call, how would that work with HW offloading?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/pull/2743?email_source=notifications&amp;email_token=AFTOJK7CM4DPU6ZYNFFP7GDPWVJTXA5CNFSM4HOSTCBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7HCHA#issuecomment-494825756">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK3HW6YX5UKUDPJRRFLPWVJTXANCNFSM4HOSTCBA">mute the thread</a>.<img src="https://github.com/notifications/beacon/AFTOJK7VHQOPIKCP2YGO65LPWVJTXA5CNFSM4HOSTCBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7HCHA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/pull/2743?email_source=notifications\u0026email_token=AFTOJK7CM4DPU6ZYNFFP7GDPWVJTXA5CNFSM4HOSTCBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7HCHA#issuecomment-494825756",
"url": "https://github.com/quicwg/base-drafts/pull/2743?email_source=notifications\u0026email_token=AFTOJK7CM4DPU6ZYNFFP7GDPWVJTXA5CNFSM4HOSTCBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7HCHA#issuecomment-494825756",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5ce55bbb88042_d653ff3a10cd96814579bc--