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

Re: Generic CBC-MAC specification

To: ben@Ascend.COM (Ben Rogers)
Subject: Re: Generic CBC-MAC specification
From: "Derrell D. Piper" <ddp@network-alchemy.com>
Date: Wed, 11 Feb 1998 10:17:19 -0800
cc: Daniel Harkins <dharkins@cisco.com>, "Theodore Y. Ts'o" <tytso@MIT.EDU>, ipsec@tis.com
In-reply-to: Your message of "Wed, 11 Feb 1998 09:51:27 EST." <199802111451.JAA08590@carp.morningstar.com>
Sender: owner-ipsec@ex.tis.com

>Does anyone disagree with my rationale for another draft?

Yes, I disagree.  As Ted pointed out, it's relatively well understood how to
generate CBC MAC's.  In addition, introducing another document dependency for
IPSEC is unnecessary and bordering on the absurd.  There's already way too
many documents describing this protocol.

We need these documents to go to RFC, now.  We can always revise the RFC
later.  It's much more dangerous to have folks shipping products that are
written to ID's.  I want to ship a product based on an RFC, not an ID.

Derrell

References:

Re: Generic CBC-MAC specification

From: Ben Rogers <ben@Ascend.COM>

Prev by Date: Re: Generic CBC-MAC specification
Next by Date: Re: PKI(Entrust) & IPsec
Prev by thread: Re: Generic CBC-MAC specification
Next by thread: Re: Generic CBC-MAC specification
Index(es):
- Main
- Thread