[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Cfrg] Re: Changing the key deriveration

To: cfrg@ietf.org, <ipsec@lists.tislabs.com>, Charlie Kaufman <ckaufman@microsoft.com>
Subject: Re: [Cfrg] Re: Changing the key deriveration
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Date: Fri, 20 Feb 2004 18:09:58 -0800
Cc: Hugo Krawczyk <hugo@ee.technion.ac.il>, "The Purple Streak, Hilarie Orman" <ho@alum.mit.edu>
In-reply-to: <Pine.GSO.4.44_heb2.09.0402170435310.18015-100000@ee.technion.ac.il>
References: <Pine.GSO.4.44_heb2.09.0402170435310.18015-100000@ee.technion.ac.il>
Sender: owner-ipsec@lists.tislabs.com

At 9:57 PM +0200 2/17/04, Hugo Krawczyk wrote:
>Anyway, replacing SK_ai and SK_ar in the above text (as well as in 2.15,
>first paragraph) with SK_d does resolve the problem of using two
>algorithms (prf and integrity) with the same key, and it is much better
>than what is done now.

There have been no more comments on this, and the ADs are still 
waiting for a final draft of this document so they can move all three 
IKEv2 documents to IETF last call.

Charlie: are you OK with this solution? If so, can you get the new 
draft out soon, such as when the Internet Drafts window opens?

--Paul Hoffman, Director
--VPN Consortium

Follow-Ups:
- Re: [Cfrg] Re: Changing the key deriveration
  - From: canetti <canetti@watson.ibm.com>
- Re: [Cfrg] Re: Changing the key deriveration
  - From: "Theodore Ts'o" <tytso@mit.edu>

References:
- Re: [Cfrg] Re: Changing the key deriveration
  - From: Hugo Krawczyk <hugo@ee.technion.ac.il>

Prev by Date: Re: Traffic selectors in IKEv2
Next by Date: RE: Traffic Selectors (was SA fragments)
Previous by thread: Re: [Cfrg] Re: Changing the key deriveration
Next by thread: Re: [Cfrg] Re: Changing the key deriveration
Index(es):
- Date
- Thread