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

Re: Digest-MD5 to Historic

To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@xxxxxxxxx>
Subject: Re: Digest-MD5 to Historic
From: Alexey Melnikov <alexey.melnikov@xxxxxxxxx>
Date: Wed, 12 Mar 2008 12:09:23 +0000
Cc: ietf-sasl@xxxxxxx
In-reply-to: <fop89f$6m2$1@xxxxxxxxxxxxx>
List-archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-id: <ietf-sasl.imc.org>
List-unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>
References: <ldvfxxzoouv.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx> <476AD3F5.9020400@xxxxxxxxx> <fop89f$6m2$1@xxxxxxxxxxxxx>
Sender: owner-ietf-sasl@xxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915


Frank Ellermann wrote:

Hi,

here is the proposed text explaining the MD5-SESS Digest-MD5
problem.  I could transform it into xml2rfc format if needed.

Hi Frank,

I think the text you've suggested would be good for an interoperabilityreport on an update to DIGEST-MD5 itself.My "DIGEST-MD5 to historic" draft was never intended as a detaileddescription of all things broken in DIGEST-MD5.

Follow-Ups:
- Re: Digest-MD5 to Historic
  - From: Frank Ellermann

References:
- new milestones for charter update
  - From: Tom Yu
- Re: new milestones for charter update
  - From: Alexey Melnikov
- Digest-MD5 to Historic
  - From: Frank Ellermann

Prev by Date: Re: Clarifying the qualities we desire the DIGEST-MD5 replacement to have
Next by Date: Re: Clarifying the qualities we desire the DIGEST-MD5 replacement to have
Previous by thread: Re: Digest-MD5 to Historic
Next by thread: Re: Digest-MD5 to Historic
Index(es):
- Date
- Thread