Security considerations explained in section 7 of [RFC3686] are
entirely relevant for this draft also. The security considerations
on fresh keys and integrity protection in section 7 of [RFC3686] are
totally applicable on using AES-CTR in IKEv2; see [RFC3686] for
details. Due to
Raj Singh writes:
Section 5. IANA Considerations can be reworded in-line with
ikev2bis.
It would be better align it with ikev2-parameters iana registry.
5. IANA Considerations
IANA has already registered the type and value for AES-CTR.
Name Number Defined In
Paul Hoffman writes:
Based on Pasi's AD review, the authors significantly shortened the
document. It seems prudent to have the WG review the new, shorter
version. In particular, it would be good for developers to look at
the new short document and see if it is complete enough to implement
Raj Singh writes:
Section 5. IANA Considerations can be reworded in-line with
ikev2bis.
It would be better align it with ikev2-parameters iana registry.
5. IANA Considerations
IANA has already registered the type and value for AES-CTR.
Name Number Defined In
: |
|
--|
|[IPsec] Please review draft-ietf-ipsecme-aes-ctr-ikev2-05.txt
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the IP Security Maintenance and Extensions
Working Group of the IETF.
Title : Using Advanced Encryption Standard (AES) Counter Mode
with IKEv2
Author(s) :
: ipsec-boun...@ietf.org [mailto:ipsec-boun...@ietf.org] On Behalf Of Paul
Hoffman
Sent: Wednesday, March 03, 2010 7:52 PM
To: IPsecme WG
Subject: [IPsec] Please review draft-ietf-ipsecme-aes-ctr-ikev2-05.txt
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft
Nir y...@checkpoint.com
Reply-To:
To: 'Paul Hoffman' paul.hoff...@vpnc.org, IPsecme WG ipsec@ietf.org
Subject: Re: [IPsec] Please review draft-ietf-ipsecme-aes-ctr-ikev2-05.txt
Date:Thu, 4 Mar 2010 07:16:55 +0200
Paragraph 5 of section #2:
MUST accept any length that results in proper
