Re: [TLS] Status of Cha-Cha/Poly Cipher Suites?

[Nikos Mavrogiannopoulos <[e-mail]>]

On Sun, 2015-05-17 at 08:42 +0300, Ilari Liusvaara wrote:
> On Sun, May 17, 2015 at 01:02:23AM +0300, Yoav Nir wrote:
> > Hi, Jeffrey
> > What remains for the TLS working group to do is to adopt a draft for
> > ChaCha20-Poly1305 in TLS. There already is a candidate:
> > https://tools.ietf.org/html/draft-mavrogiannopoulos-chacha-tls-05
> 
> The only comment I have regarding that draft is that it doesn't specify
> what to stick to record payload. Ciphertext (|P| bytes) || Tag (16 bytes),
> right?

Hi,
 I believed that the output format was explicit in rfc7539, but I was
wrong. I've clarified that point and hopefully that will be included in
the next draft update.

> > Once that’s done, the document can both progress and if needed, people
> > can request early assignment of identifiers. The ciphersuite registry
> > has a “specification required” policy. Strictly speaking, the private
> > draft could be enough - we don’t have to have an RFC, but practically
> > speaking, this document will only get assignment after it is adopted
> > by the WG.
> As note, GnuTLS 3.4.x implements (disabled by default) the abovementioned
> draft, using CSID CCA0-CCA7 (which are noted in the draft).

Indeed, we've added new code points to allow interoperability testing.

regards,
Nikos