The following errata report has been submitted for RFC5246,
"The Transport Layer Security (TLS) Protocol Version 1.2".
--
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5246&eid=4912
-
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Layer Security of the IETF.
Title : Applying GREASE to TLS Extensibility
Author : David Benjamin
Filename: draft-ietf-tls-g
Done. Let me know if I did any of that incorrectly.
(Sorry about the delay. I've been some combination of suffering from a
cold, on vacation, or at conferences for the past month---usually more than
one at a time!)
On Tue, Jan 3, 2017 at 8:59 AM Sean Turner wrote:
I appears that we’ve got enoug
So, having uploaded draft-ietf-tls-grease-00, I would now like to rewrite
large chunks of it. The draft is currently defined for TLS 1.2, but it
probably makes sense to order it after TLS 1.3.
TLS 1.3 also adds a many new extension points, and we can expect new TLS
1.3 implementations popping up i
Hi David,
> I was thinking of making the following changes:
>
> - Cite TLS 1.3 instead of TLS 1.2.
>
> - Add some text to use the same code point pattern for TLS 1.3
> signature_algorithms.
>
> - Add some text to suggest advertising GREASE values in key_shares if
> advertised in supported_group
On 19 January 2017 at 14:04, Kazu Yamamoto wrote:
> Should we also add grease values for key_share?
supported_groups code points should cover that, but if you are asking
if we should spend bytes on sending shares for bogus groups, that's a
question I don't have an opinion on. I guess that you *c
On Wed, Jan 18, 2017 at 8:15 PM Martin Thomson
wrote:
On 19 January 2017 at 14:04, Kazu Yamamoto wrote:
> Should we also add grease values for key_share?
supported_groups code points should cover that, but if you are asking
if we should spend bytes on sending shares for bogus groups, that's a
q
> That's what we do in Chrome/BoringSSL. We send one fake NamedGroup at the
> front of supported_groups and then put it in key_shares with a one-byte
> fake KeyShareEntry.
>
> It costs five bytes total and, having already caught a bug with it, seems
> valuable. It ensures that servers are capable
