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 ynir.i...@gmail.com wrote:
One more thing.
I would like to
On Wed, 1 Apr 2015, 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?
Just to confirm, yes please. As I said before, let's not have another
twofish/serpent
Paul Wouters writes:
On Wed, 1 Apr 2015, 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?
Just to confirm, yes please. As I said before, let's not
Seeing as none of the transform names begins with “ESP_” and that we’re
specifying the algorithm for IKE as well as ESP, I’ve changed the identifier to
ENCR_ChaCha20_Poly1305.
Yoav
On Mar 31, 2015, at 12:15 PM, Yoav Nir ynir.i...@gmail.com wrote:
One more thing.
I would like to request
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
On Tue, 31 Mar 2015, Yoav Nir wrote:
Can we make it ENCR_CHACHA20_POLY1305 ?
Currently IANA mostly has no CamelCase and it is kind of a C habbit to
have defines in CAPS :)
I guess, although some of the names don’t quite work as identifiers: AES-GCM with a
8 octet ICV” or ENCR-AES-CCM_12”,
Paul Wouters writes:
On Tue, 31 Mar 2015, Yoav Nir wrote:
Can we make it ENCR_CHACHA20_POLY1305 ?
Currently IANA mostly has no CamelCase and it is kind of a C habbit to
have defines in CAPS :)
I guess, although some of the names don’t quite work as
identifiers: AES-GCM with a 8 octet
Paul Wouters writes:
On Tue, 31 Mar 2015, Tero Kivinen wrote:
How has that happened. Hmmm... looking at the archives that was there
from the beginning. And those assignments which were done at the same
time as RFC4306 was published (i.e. RFC4309 and RFC4106) never went
through the IANA
On Tue, 31 Mar 2015, Yoav Nir wrote:
Seeing as none of the transform names begins with “ESP_” and that we’re
specifying the algorithm for IKE as well as ESP, I’ve changed
the identifier to ENCR_ChaCha20_Poly1305.
Yoav
Can we make it ENCR_CHACHA20_POLY1305 ?
Currently IANA mostly has no
