Re: [Cfrg] draft-housley-ccm-mode-00.txt

"Housley, Russ" <rhousley@rsasecurity.com> Fri, 16 August 2002 13:49 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15515 for <cfrg-archive@odin.ietf.org>; Fri, 16 Aug 2002 09:49:02 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA02208 for cfrg-archive@odin.ietf.org; Fri, 16 Aug 2002 09:50:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA02080; Fri, 16 Aug 2002 09:44:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA02057 for <cfrg@optimus.ietf.org>; Fri, 16 Aug 2002 09:44:50 -0400 (EDT)
Received: from vulcan.rsasecurity.com (mail.rsasecurity.com [204.167.114.123]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA15300 for <cfrg@ietf.org>; Fri, 16 Aug 2002 09:43:29 -0400 (EDT)
Received: from no.name.available by vulcan.rsasecurity.com via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 16 Aug 2002 13:44:49 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.80.211.4]) by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id JAA13634 for <cfrg@ietf.org>; Fri, 16 Aug 2002 09:44:18 -0400 (EDT)
Received: from exna00.securitydynamics.com (localhost [127.0.0.1]) by ebola.securitydynamics.com (8.10.2+Sun/8.10.2) with ESMTP id g7GDg7W27238 for <cfrg@ietf.org>; Fri, 16 Aug 2002 09:42:07 -0400 (EDT)
Received: by exna00.securitydynamics.com with Internet Mail Service (5.5.2653.19) id <3TPV2324>; Fri, 16 Aug 2002 09:44:17 -0400
Received: from HOUSLEY-LAP.rsasecurity.com (HOUSLEY-LAP [10.3.9.18]) by exna00.securitydynamics.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 3TPV232Q; Fri, 16 Aug 2002 09:44:10 -0400
From: "Housley, Russ" <rhousley@rsasecurity.com>
To: pgut001@cs.auckland.ac.nz
Cc: cfrg@ietf.org
Message-Id: <5.1.0.14.2.20020816093357.0354b9a0@exna07.securitydynamics.com>
X-Sender: rhousley@exna07.securitydynamics.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 16 Aug 2002 09:39:13 -0400
Subject: Re: [Cfrg] draft-housley-ccm-mode-00.txt
In-Reply-To: <200208160411.QAA18674@ruru.cs.auckland.ac.nz>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: cfrg-admin@ietf.org
Errors-To: cfrg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Crypto Forum Research Group <cfrg.ietf.org>
X-BeenThere: cfrg@ietf.org

Peter:

> >IEEE 802.11 has chosen to make CCM the mandatory to implement AES mode for
> >wireless LAN encryption. IEEE 802.15 has also chosen CCM for use with
> >personal area networks.  In my opinion, this success is due to the lack of
> >a patent (or pending patent from the authors) on CCM.  I suspect that most
> >of the members of this list are aware that other candidate authenticated
> >encryption modes are encumbered.
>
>Is there a chance that it'd be covered by some other patent?  Having
>recently looked at DH+password mechanisms, I'm wary of algorithms in
>fields where multiple overlapping patents already exist.

The authors are unaware of any issued patents that cover CCM.  None of the 
authors have filed patents that cover CCM.  Non of the authors are aware of 
any filed, but not yet issued, patents that cover CCM.

> >It is my intention to publish draft-housley-ccm-mode-00.txt as an
> >Informational RFC.  This looks like the appropriate group to review the
> >document.
>
>If it's truly unencumbered, I'd like to see this as standards-track.  I've
>been working on an single-pass encrypt+MAC process draft for CMS for use
>in areas like EDI, but a combined mode of operation would be much nicer.

Generally, the algorithm specification is published as in Informational 
RFC, then standards-track RFCs reference the Informational RFC.  In this 
way, the algorithm becomes mandatory to implement.

Russ

_______________________________________________
Cfrg mailing list
Cfrg@ietf.org
https://www1.ietf.org/mailman/listinfo/cfrg