I am still a bit confused about Sec. 3 (use in IKEv2):
- Where does it say (in this draft or in Sec. 2.7 of the CFRG draft)
that the IV is included explicitly, and where exactly it should go?
- In the bullet that describes the IV, I would add text that the IKE
Message ID is not an option,
Clearly we need to mention that the IV is included, despite the text of
RFC 7296.
You are right about SK_ei/er. The second bullet in Sec. 3 should not
mention KEYMAT, which is unrelated, and maybe should mention SK_ei/er.
Thanks,
Yaron
On 04/27/2015 11:38 AM, Yoav Nir wrote:
On
Thanks. I’ve fixed this in my working draft of -06, which should be published
soon.
Yoav
On Apr 27, 2015, at 1:05 PM, Doyle, Stephen stephen.do...@intel.com wrote:
In the ESP Example in Appendix A, the 'Next Header' field is missing from the
ESP Trailer portion of the plaintext.
OK. Make those changes. I’ll post a new version tomorrow.
Yoav
On Apr 27, 2015, at 12:38 PM, Yaron Sheffer yaronf.i...@gmail.com wrote:
Clearly we need to mention that the IV is included, despite the text of RFC
7296.
You are right about SK_ei/er. The second bullet in Sec. 3 should not
Hi, Martin. See inline.
On Apr 27, 2015, at 2:02 PM, Martin Willi mar...@strongswan.org wrote:
Yoav,
Oh, and one more thing: I’d really appreciate it if somebody checked my
examples. All I can be sure of is that they work in my code.
I've hit two issues when verifying the IKEv2
On Apr 27, 2015, at 10:46 AM, Yaron Sheffer yaronf.i...@gmail.com wrote:
I am still a bit confused about Sec. 3 (use in IKEv2):
- Where does it say (in this draft or in Sec. 2.7 of the CFRG draft) that the
IV is included explicitly, and where exactly it should go?
It says that the IV is
On Apr 27, 2015, at 6:25 PM, Michael Richardson mcr+i...@sandelman.ca wrote:
I read draft-ietf-ipsecme-chacha20-poly1305 on Friday last, and then found
that I needed to further review draft-nir-cfrg-chacha20-poly1305-06 to better
understand the questions in para 2 of the security
On Tue, 28 Apr 2015, Yoav Nir wrote:
This is actually quite unfortunate text. Fields must be aligned to block size
only for CBC. Aligning AES-GCM to 16 bytes and ChaCha20-Poly1305 to 64 bytes
would be totally arbitrary, yet that is what the MUST requirement in the first
bullet seems to be
On Apr 28, 2015, at 2:49 AM, Paul Wouters p...@nohats.ca wrote:
On Tue, 28 Apr 2015, Yoav Nir wrote:
This is actually quite unfortunate text. Fields must be aligned to block
size only for CBC. Aligning AES-GCM to 16 bytes and ChaCha20-Poly1305 to 64
bytes would be totally arbitrary,
Yoav Nir ynir.i...@gmail.com wrote:
Second issue is about UI advice. Some implementations (yes, mine is
included) allow the user to configure encryption algorithm, MAC
algorithm, and D-H group. There is no setting for PRF since such UIs
date back to IKEv1. The PRF is usually
10 matches
Mail list logo
