[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Revised suggestion for ESP 3DES MD5 document
Naganand,
Given that Steve Kent is modularizing the IPSec documents, let me
retract my suggestion since it is likely to cause delays. It is more
important to me to have a strong ESP quickly, than a modular
specification.
--Bob
>----------
>From: Ran Atkinson[SMTP:rja@cisco.com]
>Sent: Wednesday, October 23, 1996 2:03 PM
>To: Bob Baldwin
>Cc: ipsec@TIS.COM
>Subject: Re: Suggestion for ESP 3DES MD5 document
>
>Bob Baldwin wrote:
>
>> I would like to suggest that when you write-up the triple DES
>>transform that you modularize the document so it is easy to
>>substitute other ciphers and hash functions. My goal is to be able
>>to briefly specify other ESPs by referencing your document.
>
> Modularity is the primary goal of the editorial changes proposed in
>Montreal
>by and being made by Steve Kent. More documents specifying more transforms
>is
>(IMHO) not part of the solution here, as Steve Kent so clearly pointed out in
>Montreal.
>
> With a modest amount of luck, we'll eliminate the "transform" concept
>-- all together -- and replace it with some magic number/algorithm pairs
>in the IAB Assigned Numbers document (of which only one set each for AH/ESP
>would be mandatory to implement).
>
> At some level, it would be more logical to wait on all new transform
>specifications until after the modularised base specifications are
>published. However, the group seems to prefer to proceed forward for
>now and retrofit those specs back into the new document model later.
>By basing the 3DES transform draft on the Jim Hughes' Combined ESP
>draft, these later editorial changes can be done without adversely
>impacting code.
>
>All IMHO.
>
>Ran
>rja@cisco.com
>
>
>
>
>
>
>