[IPsec] ChaCha20/Poly1305 padding (was: I-D Action: draft-ietf-ipsecme-chacha20-poly1305-01.txt)

2015-04-01 Thread Martin Willi
Hi, In Section 2, draft-ietf-ipsecme-chacha20-poly1305-01 has the following text: o Finally, the Poly1305 function is run on the data to be authenticated, which is, as specified in section 2.7 of [chacha_poly] a concatenation of the following in the below order: *

Re: [IPsec] Early code point assignment (was: I-D Action: draft-ietf-ipsecme-chacha20-poly1305-00.txt)

2015-04-01 Thread Yoav Nir
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

Re: [IPsec] Early code point assignment (was: I-D Action: draft-ietf-ipsecme-chacha20-poly1305-00.txt)

2015-04-01 Thread Paul Wouters
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

Re: [IPsec] Early code point assignment

2015-04-01 Thread Yaron Sheffer
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

Re: [IPsec] ChaCha20/Poly1305 padding (was: I-D Action: draft-ietf-ipsecme-chacha20-poly1305-01.txt)

2015-04-01 Thread Yoav Nir
On Apr 1, 2015, at 3:37 PM, Martin Willi mar...@strongswan.org wrote: Hi, In Section 2, draft-ietf-ipsecme-chacha20-poly1305-01 has the following text: o Finally, the Poly1305 function is run on the data to be authenticated, which is, as specified in section 2.7 of

Re: [IPsec] draft-ietf-ipsecme-ikev2-null-auth-05.txt

2015-04-01 Thread Kathleen Moriarty
I went back to the email thread as I wanted to look at the consensus and don't see it the way Paul does. Here is the end of the thread: http://www.ietf.org/mail-archive/web/ipsec/current/msg09668.html It reads as confusion with the term updates and most being ok with going in either direction,

Re: [IPsec] draft-ietf-ipsecme-ikev2-null-auth-05.txt

2015-04-01 Thread Paul Hoffman
On Apr 1, 2015, at 6:57 PM, Kathleen Moriarty kathleen.moriarty.i...@gmail.com wrote: I went back to the email thread as I wanted to look at the consensus and don't see it the way Paul does. Here is the end of the thread: http://www.ietf.org/mail-archive/web/ipsec/current/msg09668.html

Re: [IPsec] Early code point assignment (was: I-D Action: draft-ietf-ipsecme-chacha20-poly1305-00.txt)

2015-04-01 Thread Tero Kivinen
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

Re: [IPsec] draft-ietf-ipsecme-ikev2-null-auth-05.txt

2015-04-01 Thread Kathleen Moriarty
Hi Paul, On Mon, Mar 30, 2015 at 8:51 PM, Paul Hoffman paul.hoff...@vpnc.org wrote: On Mar 30, 2015, at 1:56 PM, Kathleen Moriarty kathleen.moriarty.i...@gmail.com wrote: Thanks for making most of the suggested changes to the draft. I see nothing happened in section 2.4 with the