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

Re: change in isakmp/oakley

To: pau@watson.ibm.com
Subject: Re: change in isakmp/oakley
From: Daniel Harkins <dharkins@cisco.com>
Date: Tue, 30 Sep 1997 18:15:08 -0700
Cc: ipsec@tis.com, lmccarth@cs.umass.edu, hugo@ee.technion.ac.il, ho@earth.hpc.org
In-Reply-To: Your message of "Tue, 30 Sep 1997 18:54:39 EDT." <9709302254.AA17780@secpwr.watson.ibm.com>
Sender: owner-ipsec@ex.tis.com

  It hasn't been addressed yet. Ben Rogers brought up the exact point.
If no body can come up with a legitimate reference then are there any
complaints about me removing it? I have no qualms with Schneier (as some
of you do) but he doesn't address padding. Any other ones out there?

  I could cook something up but I don't think ISAKMP/Oakley should be
defining prf's. I'd rather refer to a (non Internet-Draft) document.

  Dan.

> I don't know if this has been addressed or not.
> But for a prf using block cipher such as 3DES-CBC-MAC,
> the input data must also be padded to block boundary.
> 
> How should the padding be done ?

References:

Re: change in isakmp/oakley

From: pau@watson.ibm.com

Prev by Date: ISAKMP Notification with an SA for Lifetimes
Next by Date: Re: ISAKMP Notification with an SA for Lifetimes
Prev by thread: Re: change in isakmp/oakley
Next by thread: [Survey] request for input -- October 1997 Survey
Index(es):
- Main
- Thread