This is a working group last call announcement for draft-ietf-tls-tls13-19, to
run through March 27. Please send your reviews to the list as soon as possible
so we can prepare for any discussion of open issues at IETF 98 in Chicago.
Thanks,
J&S
___
Note to Ilari: I have already taken your email as WGLC comments, so no need
to
re-send.
-Ekr
On Mon, Mar 13, 2017 at 10:30 AM, Sean Turner wrote:
> This is a working group last call announcement for
> draft-ietf-tls-tls13-19, to run through March 27. Please send your reviews
> to the list as
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 : Elliptic Curve Cryptography (ECC) Cipher Suites for
Transport Layer Security (TLS) Versions 1.2 and Earlier
Aut
I have just posted a new version of the DTLS 1.3 draft, updated for
draft-19.
It's still very rough with a lot of open issues (some of which are even
noted
in the draft), and no doubt contains egregious errors.
https://tools.ietf.org/html/draft-rescorla-tls-dtls13-01
As usual, comments welcome.
All,
I have updated the draft in preparation for the IETF 98:
https://tools.ietf.org/html/draft-sullivan-tls-exported-authenticator-01
The details of the protocol haven't changed, but I've included some
security considerations after speaking with Karthikeyan Bhargavan and
others about the cryptog
Can you help me understand what this means?
servers that are authoritative for multiple domains the same
connection but do not have a certificate that is simultaneously
authoritative for all of them
I'm sure there's a word or two missing between "domains" and "the" in
the first
When we added padding to TLS 1.3, we created an ambiguity with the
max_fragment_length extension.
Does the limit apply to len(TLSInnerPlaintext) or does it apply to
len(TLSInnerPlaintext.content) (i.e., TLSPlaintext.length)? That is,
does is include the padding and content type, or not?
Includin
