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

Re: <draft-ietf-ipsec-skipjack-cbc-00.txt>

To: smacgregor@myko.rainbow.com
Subject: Re: <draft-ietf-ipsec-skipjack-cbc-00.txt>
From: Paul Koning <pkoning@xedia.com>
Date: Fri, 11 Jun 1999 13:11:17 -0400
Cc: ipsec@lists.tislabs.com, MFURUSAWA@myko.rainbow.com, SJUDY@myko-md.rainbow.com, cnguyen@rainbow.com
References: <F15F0873C42ED111A27700805F59A4AA91F7B7@exchmyko>
Sender: owner-ipsec@lists.tislabs.com

You should take a look at RFC 2451.  It already covers CBC in
general.  No need to discuss it all over again.  All you should need
is the incremental additions to that RFC to make it cover Skipjack,
which is little more than the table entries covering key size, block
size, etc., along with a reference to the cipher algorithm
specification itself.

Come to think of it -- should this sort of thing be done by the
creation of a standalone document that accompanies RFC 2451, or a new
document that supersedes RFC 2451 (containing all that was there
before plus the new cipher)?  If the latter, perhaps RFC 2405 could be 
folded into it as well, making things slightly less confusing.

	paul

References:

<draft-ietf-ipsec-skipjack-cbc-00.txt>

From: SMACGREG <smacgregor@myko.rainbow.com>

Prev by Date: Re: <draft-ietf-ipsec-skipjack-cbc-00.txt>
Next by Date: Re: What's the attribute value for group generator (MODP) ?
Prev by thread: Re: <draft-ietf-ipsec-skipjack-cbc-00.txt>
Next by thread: NDSS 2000 SUBMISSION DEADLINE EXTENDED TO JUNE 23RD
Index(es):
- Main
- Thread