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

Re: (IMPORTANT) Call for AH-MD5 and ESP-DES to move forward

To: "PALAMBER.US.ORACLE.COM" <PALAMBER@us.oracle.com>
Subject: Re: (IMPORTANT) Call for AH-MD5 and ESP-DES to move forward
From: "Perry E. Metzger" <perry@piermont.com>
Date: Thu, 29 Feb 1996 20:58:20 -0500
Cc: ipsec@ans.net
In-Reply-To: Your message of "29 Feb 1996 13:36:29 PST." <199602292154.NAA18059@mailsun2.us.oracle.com>
Reply-To: perry@piermont.com
Sender: ipsec-request@neptune.tis.com


"PALAMBER.US.ORACLE.COM" writes:
> >but I disagree with the words "replace". As Paul's survey 
> >reveals, many implementations currently implement 1828. 
>  
> There has been very strong support for the use of HMAC as the "standard" 
> transform for AH.  A "change" of this mechanism sooner, rather than later, 
> would limit the impact on implementors. 

Fine, but that doesn't necessarily mean "replace".

Perry

References:

Re: (IMPORTANT) Call for AH-MD5 and ESP-DES to move forward

From: "PALAMBER.US.ORACLE.COM" <PALAMBER@us.oracle.com>

Prev by Date: Re: (IMPORTANT) Call for AH-MD5 and ESP-DES to move forward
Next by Date: Re: technical clarification request to RFC-1828.
Prev by thread: Re: (IMPORTANT) Call for AH-MD5 and ESP-DES to move forward
Next by thread: Re: (IMPORTANT) Call for AH-MD5 and ESP-DES to move forward
Index(es):
- Main
- Thread