[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ietf-tls
Subject:    Re: [TLS] Early code point assignment for draft-ietf-tls-curve25519-01
From:       Simon Josefsson <simon () josefsson ! org>
Date:       2016-01-12 9:24:09
Message-ID: 87mvsbywue.fsf () latte ! josefsson ! org
[Download RAW message or body]


Joseph Salowey <joe@salowey.net> writes:

> Please respond if you have concern about early code point assignment for
> the curves listed in draft-ietf-tls-curve25519-01
> <https://tools.ietf.org/html/draft-ietf-tls-curve25519-01>.

The above draft, and rfc4492bis and tls13-11, has known
issues/inconsistencies related to X25519/X448 that have been discussed
on the list.  When it was decided (offlist..) to move the content of
draft-ietf-tls-curve25519 to other documents, I stopped working on it.

What would the semantics of these code points related to the known
issues be (e.g., code point validation or not)?  Do the code points
refer to what the draft above says, or what people appear to prefer
(don't reject, but ignore set bit) and have been implementing?

I can update the document to fix the known issues.  The content has been
copied to other documents that I have no editor influence of, so
modifying draft-ietf-tls-curve25519 may make the situation even more
confusing.  Please advice if you want anything more to happen with the
document above.

/Simon

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]