Hoffman paul.hoff...@vpnc.org
To:
Scott C Moonen/Raleigh/i...@ibmus
Cc:
IPsecme WG ipsec@ietf.org, ipsec-boun...@ietf.org, Tero Kivinen
kivi...@iki.fi
Date:
11/25/2009 12:29 PM
Subject:
Re: [IPsec] #122: Integrity proposals with combined algorithms
At 11:34 AM -0500 11/25/09, Scott C Moonen wrote
Paul Hoffman writes:
The 4th paragraph of section 3.3 says If an algorithm that combines
encryption and integrity protection is proposed, it MUST be proposed
as an encryption algorithm and an integrity protection algorithm
MUST NOT be proposed. This means that an integrity protection
At 4:08 PM +0200 11/24/09, Tero Kivinen wrote:
Paul Hoffman writes:
The 4th paragraph of section 3.3 says If an algorithm that combines
encryption and integrity protection is proposed, it MUST be proposed
as an encryption algorithm and an integrity protection algorithm
MUST NOT be proposed.
The 4th paragraph of section 3.3 says If an algorithm that combines encryption
and integrity protection is proposed, it MUST be proposed as an encryption
algorithm and an integrity protection algorithm MUST NOT be proposed. This
means that an integrity protection algorithm can only be proposed
On Mon, Nov 23, 2009 at 04:32:43PM -0800, Paul Hoffman wrote:
The second sentence seems wrong. Proposed rewording:
For example,
[AEAD] specifies additional formats based on authenticated
encryption, in which the integrity algorithm is an inherent
part of the combined algorithm; in
