Not while the latest revision still has two TBDs, while we're still
debating two interop-critical issues (padding, salt) and another major
security issue (IV).
I don't want private use numbers any more than PaulW, but I also don't
want errata like we had for TLS EtM.
We can iron out these issues within a week or two and then I'd be all in
favor of a code point assignment.
Thanks,
Yaron
On 04/01/2015 04:26 AM, Yoav Nir wrote:
OK, so this thread kind of got side-tracked about the name of the
algorithm. I think ENCR_CHACHA20_POLY1305 works for everybody.
What about early code point assignment?
Thanks
Yoav
On Mar 31, 2015, at 12:15 PM, Yoav Nir <[email protected]
<mailto:[email protected]>> wrote:
One more thing.
I would like to request early code point assignment for
ESP_ChaCha20-Poly1305.
I know that it is the goal of the chairs to bring this to LC sooner
rather than later, but I would like to get started on implementation
sooner rather than later, and the IETF process takes three months at
best, and six months in the more common case.
Thanks
Yoav
_______________________________________________
IPsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipsec
_______________________________________________
IPsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipsec
