
From mcgrew@cisco.com  Mon Jun 13 07:04:17 2011
Return-Path: <mcgrew@cisco.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1AC9E8009 for <cfrg@ietfa.amsl.com>; Mon, 13 Jun 2011 07:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OzDUQX6V7k18 for <cfrg@ietfa.amsl.com>; Mon, 13 Jun 2011 07:04:16 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by ietfa.amsl.com (Postfix) with ESMTP id 887CD9E800B for <cfrg@irtf.org>; Mon, 13 Jun 2011 07:04:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mcgrew@cisco.com; l=497; q=dns/txt; s=iport; t=1307973856; x=1309183456; h=message-id:from:to:content-transfer-encoding: mime-version:subject:date; bh=1bd9Z9FVrJaKxLakxY7kraCbYp8rSR1kydvsgDOSqL4=; b=KpKxzdEDs8xwVfsnu/bGHqxVe3/TgquEotGwvfOcsS9UgMKktzxMChos PqdfuoZ7PreOa1KWytWYW30q//wksmyg/GCNAa7rlhjJcj1psOU3CxJ7t aOEccbsbo5JG56Y33ZozvdFJleY6Py4Z/aK37RGRHhtWASs/FnniLDE71 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjkHAB4Y9k2rRDoG/2dsb2JhbABSG5d5jiR3qTuBH51BhiQEhw2KJ499
X-IronPort-AV: E=Sophos;i="4.65,358,1304294400"; d="scan'208";a="464454534"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-1.cisco.com with ESMTP; 13 Jun 2011 14:04:15 +0000
Received: from stealth-10-32-254-211.cisco.com (stealth-10-32-254-211.cisco.com [10.32.254.211]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p5DE4EEB022302 for <cfrg@irtf.org>; Mon, 13 Jun 2011 14:04:15 GMT
Message-Id: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: cfrg@irtf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 13 Jun 2011 07:04:14 -0700
X-Mailer: Apple Mail (2.936)
Subject: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2011 14:04:17 -0000

Hi,

I updated the Internet Cryptography pages.  Some new features:

   * new I-Ds (non-expired 00 versions) are listed on a separate page <http://www.mindspring.com/~dmcgrew/ic/new.html 
 >

   * statistics on the number of times each algorithm is referenced <http://www.mindspring.com/~dmcgrew/ic/statistics.html 
 >

That last page can be used to answer the question in the subject  
line.  (Hint: it is not something most of us probably recommend  
anymore.)

regards,

David


From Joachim@Strombergson.com  Mon Jun 13 23:16:17 2011
Return-Path: <Joachim@Strombergson.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BE3811E8120 for <cfrg@ietfa.amsl.com>; Mon, 13 Jun 2011 23:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jXIiRUY5CgIv for <cfrg@ietfa.amsl.com>; Mon, 13 Jun 2011 23:16:16 -0700 (PDT)
Received: from susano.oderland.com (susano.oderland.com [91.201.63.143]) by ietfa.amsl.com (Postfix) with ESMTP id 7F6D211E8088 for <cfrg@irtf.org>; Mon, 13 Jun 2011 23:16:15 -0700 (PDT)
Received: from 2.67.227.87.static.g-sn.siw.siwnet.net ([87.227.67.2] helo=snabbis.local) by susano.oderland.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Joachim@Strombergson.com>) id 1QWMv8-000659-6k for cfrg@irtf.org; Tue, 14 Jun 2011 08:16:14 +0200
Message-ID: <4DF6FCAD.1000704@Strombergson.com>
Date: Tue, 14 Jun 2011 08:16:13 +0200
From: =?UTF-8?B?Sm9hY2hpbSBTdHLDtm1iZXJnc29u?= <Joachim@Strombergson.com>
Organization: Kryptologik
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: cfrg@irtf.org
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com>
In-Reply-To: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - susano.oderland.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - Strombergson.com
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Joachim@Strombergson.com
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 06:16:17 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aloha!

On 2011:06:13 16:04, David McGrew wrote:
> That last page can be used to answer the question in the subject line. 
> (Hint: it is not something most of us probably recommend anymore.)

I was amazed that there were so many of those drafts that are in
standards track. Drafts in informational track describing uses of
insecure algorithms is imho ok, since they document a practice.
Similarly, RFCs are a done deal and if they are a standard RFC must be
replaced by newer RFCs to fix security issues.

But in 2011 writing a draft for standards track that includes known
insecure, broken algorithms?

Would it be fruitful to browse the list try and identify the most
pressing cases and try to convince the authors that they should mend
their ways?

- -- 
Med vänlig hälsning, Yours

Joachim Strömbergson - Alltid i harmonisk svängning.
========================================================================
Kryptoblog - IT-säkerhet på svenska
http://www.strombergson.com/kryptoblog
========================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk32/K0ACgkQZoPr8HT30QF7lACfSUrUM2Ue5RDfK9CZ7379LaSS
mn4AnRgV7Q37ZaUfwm4gzGdODQOMFwOa
=vQLC
-----END PGP SIGNATURE-----

From Joachim@Strombergson.com  Mon Jun 13 23:17:44 2011
Return-Path: <Joachim@Strombergson.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD7E11E81CF for <cfrg@ietfa.amsl.com>; Mon, 13 Jun 2011 23:17:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jn-RlcSVxwWe for <cfrg@ietfa.amsl.com>; Mon, 13 Jun 2011 23:17:43 -0700 (PDT)
Received: from susano.oderland.com (susano.oderland.com [91.201.63.143]) by ietfa.amsl.com (Postfix) with ESMTP id B265711E80DE for <cfrg@irtf.org>; Mon, 13 Jun 2011 23:17:42 -0700 (PDT)
Received: from 2.67.227.87.static.g-sn.siw.siwnet.net ([87.227.67.2] helo=snabbis.local) by susano.oderland.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Joachim@Strombergson.com>) id 1QWMwX-00069G-Cc for cfrg@irtf.org; Tue, 14 Jun 2011 08:17:41 +0200
Message-ID: <4DF6FD05.4000605@Strombergson.com>
Date: Tue, 14 Jun 2011 08:17:41 +0200
From: =?UTF-8?B?Sm9hY2hpbSBTdHLDtm1iZXJnc29u?= <Joachim@Strombergson.com>
Organization: Kryptologik
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: cfrg@irtf.org
References: <op.vuk2vu2epzjggh@ohpato-t61.sec.kddilabs.jp>
In-Reply-To: <op.vuk2vu2epzjggh@ohpato-t61.sec.kddilabs.jp>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - susano.oderland.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - Strombergson.com
Subject: Re: [Cfrg] Ask for comments: draft-kiyomoto-kcipher2-03.txt
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Joachim@Strombergson.com
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 06:17:44 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aloha!

On 2011:04:27 8:27, Wook Shin wrote:
> Joachim asked about the license for KCipher-2. We have patents
> related to KCipher-2 and are trying to make it royalty-free.
> Although the final decision (of my company) hasn't been made yet,
> I believe it is going to be royalty-free soon (within a couple
> of weeks).

This issue was raised about two months ago. Has there been any
clarification on the licensing?

- -- 
Med vänlig hälsning, Yours

Joachim Strömbergson - Alltid i harmonisk svängning.
========================================================================
Kryptoblog - IT-säkerhet på svenska
http://www.strombergson.com/kryptoblog
========================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk32/QQACgkQZoPr8HT30QFYgACg3nGQMINFZ5eCWjiP7FahfLhV
5qwAnAmHyTCujUn/kiEQt5mdD32iKjME
=wCzM
-----END PGP SIGNATURE-----

From turners@ieca.com  Tue Jun 14 15:35:39 2011
Return-Path: <turners@ieca.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8B881F0C7D for <cfrg@ietfa.amsl.com>; Tue, 14 Jun 2011 15:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.148
X-Spam-Level: 
X-Spam-Status: No, score=-102.148 tagged_above=-999 required=5 tests=[AWL=0.449, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXSyGjB3iILA for <cfrg@ietfa.amsl.com>; Tue, 14 Jun 2011 15:35:39 -0700 (PDT)
Received: from nm15.access.bullet.mail.mud.yahoo.com (nm15.access.bullet.mail.mud.yahoo.com [66.94.237.216]) by ietfa.amsl.com (Postfix) with SMTP id E617F1F0C79 for <cfrg@irtf.org>; Tue, 14 Jun 2011 15:35:38 -0700 (PDT)
Received: from [66.94.237.198] by nm15.access.bullet.mail.mud.yahoo.com with NNFMP; 14 Jun 2011 22:35:36 -0000
Received: from [98.139.221.43] by tm9.access.bullet.mail.mud.yahoo.com with NNFMP; 14 Jun 2011 22:35:36 -0000
Received: from [127.0.0.1] by smtp105.biz.mail.bf1.yahoo.com with NNFMP; 14 Jun 2011 22:35:36 -0000
X-Yahoo-Newman-Id: 774493.65267.bm@smtp105.biz.mail.bf1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: gNzt8y8VM1npRQlVxcSwvEKSTGwcA7MCSFcIHc2WD6wGn.l G1TE4frbuCCwFJdAb_TIn5zyeiAh.Uvzfp1whBY5ay9PY9zInXYrROWG4295 P8vkjm7PpXLWflSC0ngt6v1ocqP5zT70QdWVb0Q3fSlMvJeKLMi7oBsPuxy_ ZlRwkkfmg15KOdsSFEnCh1hZHP82R.3lOI1oHeLwI3ejuo.EEVcs9p_MRFn0 GEpK6ESKbDhatfVob3ASySz74W9qEGMypYN5qdrVrR8u3CJt0iicWRMBNMU0 4VRLypvah4y8C0B4rc.3c9PceELwtKVdBovZtJFZd5tzxjfc7ZEPt2yhr03b cZyZqjvwamRurpl6bCUgBsMmN4fLcwSLik_1bqAJHGbJeVnWeGaTspPflttH dA9G0pnp8E7iJ25PQKFXo9LTn7p3Qqckfm7Qub2tNmXdjeWZUl2cu9bnAW3o wVzcEXDdW7FGldELL2N3o2PQsXes54aWigl.kUkiSpridGB0-
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
Received: from thunderfish.local (turners@71.191.15.93 with plain) by smtp105.biz.mail.bf1.yahoo.com with SMTP; 14 Jun 2011 15:35:35 -0700 PDT
Message-ID: <4DF7E236.3060603@ieca.com>
Date: Tue, 14 Jun 2011 18:35:34 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Joachim@Strombergson.com
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com>
In-Reply-To: <4DF6FCAD.1000704@Strombergson.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 22:35:39 -0000

On 6/14/11 2:16 AM, Joachim Strömbergson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Aloha!
>
> On 2011:06:13 16:04, David McGrew wrote:
>> That last page can be used to answer the question in the subject line.
>> (Hint: it is not something most of us probably recommend anymore.)
>
> I was amazed that there were so many of those drafts that are in
> standards track. Drafts in informational track describing uses of
> insecure algorithms is imho ok, since they document a practice.
> Similarly, RFCs are a done deal and if they are a standard RFC must be
> replaced by newer RFCs to fix security issues.
>
> But in 2011 writing a draft for standards track that includes known
> insecure, broken algorithms?

Somebody has asked for draft that says don't use RC4.  I'm really busy 
but would gladly help deprecate RFC cipher suites in TLS. Unless of 
course, I'm totally wrong and we should keep them....

> Would it be fruitful to browse the list try and identify the most
> pressing cases and try to convince the authors that they should mend
> their ways?

Actually, it would.

spt

> - --
> Med vänlig hälsning, Yours
>
> Joachim Strömbergson - Alltid i harmonisk svängning.
> ========================================================================
> Kryptoblog - IT-säkerhet på svenska
> http://www.strombergson.com/kryptoblog
> ========================================================================
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk32/K0ACgkQZoPr8HT30QF7lACfSUrUM2Ue5RDfK9CZ7379LaSS
> mn4AnRgV7Q37ZaUfwm4gzGdODQOMFwOa
> =vQLC
> -----END PGP SIGNATURE-----
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg

From bsmith@mozilla.com  Tue Jun 14 15:42:36 2011
Return-Path: <bsmith@mozilla.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 758C811E8155 for <cfrg@ietfa.amsl.com>; Tue, 14 Jun 2011 15:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cjfvW8eTrTL5 for <cfrg@ietfa.amsl.com>; Tue, 14 Jun 2011 15:42:35 -0700 (PDT)
Received: from mail.mozilla.com (corp01.sj.mozilla.com [63.245.208.141]) by ietfa.amsl.com (Postfix) with ESMTP id C0FC111E8154 for <cfrg@irtf.org>; Tue, 14 Jun 2011 15:42:35 -0700 (PDT)
Received: from mail.mozilla.com (mail.mozilla.com [10.2.72.15]) by mail.mozilla.com (Postfix) with ESMTP id 4F3E6AE646F2; Tue, 14 Jun 2011 15:42:35 -0700 (PDT)
Date: Tue, 14 Jun 2011 15:42:35 -0700 (PDT)
From: Brian Smith <bsmith@mozilla.com>
To: Sean Turner <turners@ieca.com>
Message-ID: <761053052.210562.1308091355160.JavaMail.root@zimbra1.shared.sjc1.mozilla.com>
In-Reply-To: <4DF7E236.3060603@ieca.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [63.245.220.240]
X-Mailer: Zimbra 6.0.8_GA_2661 (ZimbraWebClient - FF3.0 (Win)/6.0.8_GA_2661)
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 22:42:36 -0000

Sean Turner wrote:
> > On 2011:06:13 16:04, David McGrew wrote:
> Somebody has asked for draft that says don't use RC4. I'm really busy
> but would gladly help deprecate RFC cipher suites in TLS. Unless of
> course, I'm totally wrong and we should keep them....

I think you meant to write "deprecate RC4 cipher suites in TLS." 

What would be the justification used? I know of some weaknesses of RC4 but I haven't seen any indication that it is broken in TLS.

Cheers,
Brian

From turners@ieca.com  Tue Jun 14 15:54:29 2011
Return-Path: <turners@ieca.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3F6911E816F for <cfrg@ietfa.amsl.com>; Tue, 14 Jun 2011 15:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.256
X-Spam-Level: 
X-Spam-Status: No, score=-101.256 tagged_above=-999 required=5 tests=[AWL=-0.517, BAYES_20=-0.74, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6bDXnSp2fgM for <cfrg@ietfa.amsl.com>; Tue, 14 Jun 2011 15:54:29 -0700 (PDT)
Received: from nm10.access.bullet.mail.mud.yahoo.com (nm10.access.bullet.mail.mud.yahoo.com [66.94.237.211]) by ietfa.amsl.com (Postfix) with SMTP id 2C20111E811E for <cfrg@irtf.org>; Tue, 14 Jun 2011 15:54:29 -0700 (PDT)
Received: from [66.94.237.192] by nm10.access.bullet.mail.mud.yahoo.com with NNFMP; 14 Jun 2011 22:54:27 -0000
Received: from [98.139.221.60] by tm3.access.bullet.mail.mud.yahoo.com with NNFMP; 14 Jun 2011 22:54:27 -0000
Received: from [127.0.0.1] by smtp101.biz.mail.bf1.yahoo.com with NNFMP; 14 Jun 2011 22:54:27 -0000
X-Yahoo-Newman-Id: 188981.42996.bm@smtp101.biz.mail.bf1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: 8JtEjhUVM1lzuc8kYS_Y866HeViOD8rXLFQ58krSXEZk9VC zLGwZ1dC_iiyPYQwqiBoJCO_VtHNGqGrNX9KV23645fBtpiXhgBPxXTaWncK 2rBi8l9QYxCqU2WIgDIbApKQcSVpduV2Os0aukGw4mRhdzWQ4JbZkWK0KzeW HlLt281EJLiFXtpVSxgYc5V8pRPTPoicK5GdgogIVUtp5xtsDacCQ4SAvOI1 W.lZeF8UvZV0.JHtCwCJFMsMH04TlpDTRO6vI4mgJCF2ni_rIWh3BcTrgeho adVs.AkWFHt2TkqGhfDJNG6rLeDz_OBivYtwK5TCU6U_6UwC1zbfjLVNKBoC JJJHqyB8wYW4PAsPU8PtxHy1b9gWbJ9RzXRQ48g--
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
Received: from thunderfish.local (turners@71.191.15.93 with plain) by smtp101.biz.mail.bf1.yahoo.com with SMTP; 14 Jun 2011 15:54:26 -0700 PDT
Message-ID: <4DF7E6A2.5020305@ieca.com>
Date: Tue, 14 Jun 2011 18:54:26 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Brian Smith <bsmith@mozilla.com>
References: <761053052.210562.1308091355160.JavaMail.root@zimbra1.shared.sjc1.mozilla.com>
In-Reply-To: <761053052.210562.1308091355160.JavaMail.root@zimbra1.shared.sjc1.mozilla.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 22:54:29 -0000

On 6/14/11 6:42 PM, Brian Smith wrote:
> Sean Turner wrote:
>>> On 2011:06:13 16:04, David McGrew wrote:
>> Somebody has asked for draft that says don't use RC4. I'm really busy
>> but would gladly help deprecate RFC cipher suites in TLS. Unless of
>> course, I'm totally wrong and we should keep them....
>
> I think you meant to write "deprecate RC4 cipher suites in TLS."
>
> What would be the justification used? I know of some weaknesses of RC4 but I haven't seen any indication that it is broken in TLS.

I did mean to write "deprecate RC4 cipher suites in TLS."  Honestly, it 
was bait ;)  I got this request and wanted to test the idea that we 
should investigate deprecating RC4.

spt

From jon@callas.org  Tue Jun 14 16:59:31 2011
Return-Path: <jon@callas.org>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C53BC11E8154 for <cfrg@ietfa.amsl.com>; Tue, 14 Jun 2011 16:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDisYaGX9v+d for <cfrg@ietfa.amsl.com>; Tue, 14 Jun 2011 16:59:31 -0700 (PDT)
Received: from merrymeet.com (unknown [173.164.244.100]) by ietfa.amsl.com (Postfix) with ESMTP id 48ACC11E8152 for <cfrg@irtf.org>; Tue, 14 Jun 2011 16:59:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by merrymeet.com (Postfix) with ESMTP id 35E7D2E0B3 for <cfrg@irtf.org>; Tue, 14 Jun 2011 17:02:46 -0700 (PDT)
Received: from merrymeet.com ([127.0.0.1]) by localhost (host.domain.tld [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 93187-09 for <cfrg@irtf.org>; Tue, 14 Jun 2011 17:02:44 -0700 (PDT)
Received: from keys.merrymeet.com (keys.merrymeet.com [173.164.244.97]) (Authenticated sender: jon) by merrymeet.com (Postfix) with ESMTPA id 0CEE12E061 for <cfrg@irtf.org>; Tue, 14 Jun 2011 17:02:44 -0700 (PDT)
Received: from [10.0.23.15] ([173.164.244.98]) by keys.merrymeet.com (PGP Universal service); Tue, 14 Jun 2011 16:59:28 -0700
X-PGP-Universal: processed; by keys.merrymeet.com on Tue, 14 Jun 2011 16:59:28 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
From: Jon Callas <jon@callas.org>
In-Reply-To: <4DF7E236.3060603@ieca.com>
Date: Tue, 14 Jun 2011 16:59:27 -0700
Message-Id: <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org>
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com>
To: cfrg@irtf.org
X-Mailer: Apple Mail (2.1084)
X-PGP-Encoding-Format: Partitioned
X-PGP-Encoding-Version: 2.0.2
X-Content-PGP-Universal-Saved-Content-Transfer-Encoding: quoted-printable
X-Content-PGP-Universal-Saved-Content-Type: text/plain; charset=us-ascii
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Virus-Scanned: Maia Mailguard
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 23:59:31 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>> Would it be fruitful to browse the list try and identify the most
>> pressing cases and try to convince the authors that they should mend
>> their ways?
>=20
> Actually, it would.
>=20

I disagree. What would be helpful would be to identify *implementations* th=
at should mend their ways. The map is not the territory. The RFCs are the m=
aps; the implementations are the territories. If you change the map so that=
 it represents an idealized reality, it's not the same thing as a fixed rea=
lity. I think reality is better than this survey of maps indicates.

Let me channel Jeff Schiller and point out that mandatory-to-implement does=
 not imply mandatory-to-use, as well as that the purpose of a standard is i=
nteroperability. It is the implementations themselves where the rubber meet=
s the road and bits are twiddled.

For example, let's assume a standard that was done in the late '90s, and co=
nsequently has MD5 and 3DES as its MUST algorithms and has since been updat=
ed with MAYs of AES and SHA2.

While it would be nice to update the standard's MUSTs, this is often proble=
matic. On the other hand, as I said above, the purpose of a standard is int=
eroperability. I'd jump down the throat of any implementation that's still =
using MD5 *because* there's no reason to just make the decision that you'll=
 negotiate AES and SHA2 even unto the point of refusing to use MD5 at all. =
It's a reasonable implementer's prerogative.

Now let's look at the flip side of this. Let's wave a magic wand and make a=
ll the standards update themselves to reasonable parameters. I assert that =
the effect of this in the world of implementations will be within epsilon o=
f zero. Any *reasonable* implementation is already using reasonable paramet=
ers, and the ones that haven't updated themselves aren't going to have a fi=
re lit under their butt because RFC 31337 says so. Phrased another way, I d=
on't think there's a single broken implementation that is broken because th=
ere are aged RFCs out there. The implementations are broken for one reason =
only -- the implementers don't care. (I also assert that any implementation=
 that merely is no longer maintained proves me right on the don't-care fron=
t.)

Updating all those aged RFCs is a feel-good exercise that will have no effe=
ct on the real world. Any standard that people are using actively almost ce=
rtainly has migrated away. The exception cases (and I'm sure they exist) ar=
e where the effort should be focused.

If you want to have a positive effect on the world with the minimum windmil=
l-tilting, go find the RFCs that do not have reasonable extensions. Continu=
ing my example, something that is using (e.g.) bare MD5 with no option for =
SHA2. Update that RFC to have SHA2 as a MAY, and then poke the implementers=
 to migrate on their own. I can think of a few things I might pursue (CRAM-=
MD5 springs to mind), but focus your righteous anger on the implementations=
 that are screwing up and then on the implementations that are doing someth=
ing half-assed because the only option they have is to do something half-as=
sed. Write the new RFC for them with something full-assed.

	Jon


-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 2.10.0 (Build 554)
Charset: us-ascii

wj8DBQFN9/XgsTedWZOD3gYRAqYpAJ9vTb/1As0PiH+CMQHXtIEtiiwqmQCeIyKp
vlBNCLgQrMXpAQ+4A9rsfNw=3D
=3DmqjI
-----END PGP SIGNATURE-----

From simon@josefsson.org  Wed Jun 15 00:32:01 2011
Return-Path: <simon@josefsson.org>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97EB711E80C5 for <cfrg@ietfa.amsl.com>; Wed, 15 Jun 2011 00:32:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BkfxZqWYfvmF for <cfrg@ietfa.amsl.com>; Wed, 15 Jun 2011 00:32:01 -0700 (PDT)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [213.115.69.139]) by ietfa.amsl.com (Postfix) with ESMTP id 7455211E8074 for <cfrg@irtf.org>; Wed, 15 Jun 2011 00:31:59 -0700 (PDT)
Received: from latte.josefsson.org (c80-216-4-108.bredband.comhem.se [80.216.4.108]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p5F7VX0c025721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Jun 2011 09:31:36 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Jon Callas <jon@callas.org>
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:110615:jon@callas.org::8gsugpyARiAeJ71m:6pw6
X-Hashcash: 1:22:110615:cfrg@irtf.org::ITfpoXyZ9t2bBZ7X:93vV
Date: Wed, 15 Jun 2011 09:31:33 +0200
In-Reply-To: <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> (Jon Callas's message of "Tue, 14 Jun 2011 16:59:27 -0700")
Message-ID: <87vcw7im96.fsf@latte.josefsson.org>
User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97 at yxa-v
X-Virus-Status: Clean
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 07:32:01 -0000

Jon Callas <jon@callas.org> writes:

> I disagree. What would be helpful would be to identify
> *implementations* that should mend their ways. The map is not the
> territory. The RFCs are the maps; the implementations are the
> territories. If you change the map so that it represents an idealized
> reality, it's not the same thing as a fixed reality. I think reality
> is better than this survey of maps indicates.

+1

Use of DES/RC2/MD4 is still not uncommon.

> If you want to have a positive effect on the world with the minimum
> windmill-tilting, go find the RFCs that do not have reasonable
> extensions. Continuing my example, something that is using (e.g.) bare
> MD5 with no option for SHA2. Update that RFC to have SHA2 as a MAY,
> and then poke the implementers to migrate on their own. I can think of
> a few things I might pursue (CRAM-MD5 springs to mind), but focus your
> righteous anger on the implementations that are screwing up and then
> on the implementations that are doing something half-assed because the
> only option they have is to do something half-assed. Write the new RFC
> for them with something full-assed.

For CRAM-MD5 to fall, I think you need to show that there are practical
attacks on HMAC-MD5.  As far as I recall this hasn't been done yet.

I'm more concerned with DIGEST-MD5.  I'm not sure significant number of
people in the crypto community bothers to study it.  However DIGEST-MD5
is widely implemented and used.

Fortunately, we have SCRAM to replace them both. :-)

/Simon

From Joachim@Strombergson.com  Wed Jun 15 00:42:55 2011
Return-Path: <Joachim@Strombergson.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA3A11E80DD for <cfrg@ietfa.amsl.com>; Wed, 15 Jun 2011 00:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9rgaT0+ZSh3x for <cfrg@ietfa.amsl.com>; Wed, 15 Jun 2011 00:42:54 -0700 (PDT)
Received: from susano.oderland.com (susano.oderland.com [91.201.63.143]) by ietfa.amsl.com (Postfix) with ESMTP id 23BAE11E8074 for <cfrg@irtf.org>; Wed, 15 Jun 2011 00:42:53 -0700 (PDT)
Received: from 2.67.227.87.static.g-sn.siw.siwnet.net ([87.227.67.2] helo=snabbis.local) by susano.oderland.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Joachim@Strombergson.com>) id 1QWkkW-0003nl-Fi for cfrg@irtf.org; Wed, 15 Jun 2011 09:42:52 +0200
Message-ID: <4DF8627B.1030702@Strombergson.com>
Date: Wed, 15 Jun 2011 09:42:51 +0200
From: =?UTF-8?B?Sm9hY2hpbSBTdHLDtm1iZXJnc29u?= <Joachim@Strombergson.com>
Organization: Kryptologik
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: cfrg@irtf.org
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com>	<4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org>
In-Reply-To: <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - susano.oderland.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - Strombergson.com
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Joachim@Strombergson.com
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 07:42:55 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aloha!

On 2011:06:15 1:59, Jon Callas wrote:
>>> Would it be fruitful to browse the list try and identify the
>>> most pressing cases and try to convince the authors that they
>>> should mend their ways?
> 
>> Actually, it would.
> 
> I disagree. What would be helpful would be to identify
> *implementations* that should mend their ways. The map is not the
> territory. The RFCs are the maps; the implementations are the
> territories. If you change the map so that it represents an idealized
> reality, it's not the same thing as a fixed reality. I think reality
> is better than this survey of maps indicates.

Jon, I'm sorry for not being more clear. What I was implicitly referring
to was the lists of active drafts, not RFCs. I agree that for RFCs it is
more important to look at implementations.

But the drafts has not yet become the map. Fixing errors in the map to
be before it is printed isn't that better than waiting until it has been
printed and in use?

We basically have two different problems:
(1) Help implemementations to migrate from algorithms we don't trust
anymore to the algorithms we trust, algorithms specified in updated
versions of the map.

(2) Help map developers avoid specifying use of the bad algorithms so
that new implementations don't end up using bad algorithms in the first
place.

More understandable? And agreeable?

- -- 
Med vänlig hälsning, Yours

Joachim Strömbergson - Alltid i harmonisk svängning.
========================================================================
Kryptoblog - IT-säkerhet på svenska
http://www.strombergson.com/kryptoblog
========================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk34YnsACgkQZoPr8HT30QGNQgCfRC9Nm/5o1FcGfoTB+sdRQ2ch
728AoO2gDDaj9T5uV9VpHiTy2yfentZT
=Uxo/
-----END PGP SIGNATURE-----

From jon@callas.org  Thu Jun 16 10:11:02 2011
Return-Path: <jon@callas.org>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC10111E8190 for <cfrg@ietfa.amsl.com>; Thu, 16 Jun 2011 10:11:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hCOCwLPZ7+l8 for <cfrg@ietfa.amsl.com>; Thu, 16 Jun 2011 10:11:02 -0700 (PDT)
Received: from merrymeet.com (unknown [173.164.244.100]) by ietfa.amsl.com (Postfix) with ESMTP id 0A7C311E814C for <cfrg@irtf.org>; Thu, 16 Jun 2011 10:11:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by merrymeet.com (Postfix) with ESMTP id E04692E0B3 for <cfrg@irtf.org>; Thu, 16 Jun 2011 10:14:08 -0700 (PDT)
Received: from merrymeet.com ([127.0.0.1]) by localhost (host.domain.tld [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 17146-04 for <cfrg@irtf.org>; Thu, 16 Jun 2011 10:14:06 -0700 (PDT)
Received: from keys.merrymeet.com (keys.merrymeet.com [173.164.244.97]) (Authenticated sender: jon) by merrymeet.com (Postfix) with ESMTPA id E7D182E061 for <cfrg@irtf.org>; Thu, 16 Jun 2011 10:14:06 -0700 (PDT)
Received: from [192.168.100.101] ([166.250.33.170]) by keys.merrymeet.com (PGP Universal service); Thu, 16 Jun 2011 10:10:46 -0700
X-PGP-Universal: processed; by keys.merrymeet.com on Thu, 16 Jun 2011 10:10:46 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
From: Jon Callas <jon@callas.org>
In-Reply-To: <4DF8627B.1030702@Strombergson.com>
Date: Thu, 16 Jun 2011 10:10:43 -0700
Message-Id: <B50EC09D-5012-4C12-A340-39E7823149C5@callas.org>
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com>	<4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com>
To: cfrg@irtf.org
X-Mailer: Apple Mail (2.1084)
X-PGP-Encoding-Format: Partitioned
X-PGP-Encoding-Version: 2.0.2
X-Content-PGP-Universal-Saved-Content-Transfer-Encoding: quoted-printable
X-Content-PGP-Universal-Saved-Content-Type: text/plain; charset=us-ascii
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Virus-Scanned: Maia Mailguard
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2011 17:11:02 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>=20
> Jon, I'm sorry for not being more clear. What I was implicitly referring
> to was the lists of active drafts, not RFCs. I agree that for RFCs it is
> more important to look at implementations.
>=20
> But the drafts has not yet become the map. Fixing errors in the map to
> be before it is printed isn't that better than waiting until it has been
> printed and in use?
>=20
> We basically have two different problems:
> (1) Help implemementations to migrate from algorithms we don't trust
> anymore to the algorithms we trust, algorithms specified in updated
> versions of the map.
>=20
> (2) Help map developers avoid specifying use of the bad algorithms so
> that new implementations don't end up using bad algorithms in the first
> place.

Absolutely!

These days it's very easy to pick a good set of building blocks. There are =
also plenty of things that are mostly okay, but you shouldn't use for new p=
rotocols. In the protocol process, it's relatively easy to make sure you're=
 only using the good ones, and for anyone who isn't, we can point out what =
to do.

	Jon


-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 2.10.0 (Build 554)
Charset: us-ascii

wj8DBQFN+jkWsTedWZOD3gYRAhbPAKDIPfun9JMoLcvFpipR7Zr7cQa+AgCgwECs
mx3l7q0yjofbfBkz+0Bx4TE=3D
=3Da+WE
-----END PGP SIGNATURE-----

From pgut001@login01.cs.auckland.ac.nz  Fri Jun 17 02:34:40 2011
Return-Path: <pgut001@login01.cs.auckland.ac.nz>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3F309E8014 for <cfrg@ietfa.amsl.com>; Fri, 17 Jun 2011 02:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.562
X-Spam-Level: 
X-Spam-Status: No, score=-3.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 999yTRVUU+9d for <cfrg@ietfa.amsl.com>; Fri, 17 Jun 2011 02:34:39 -0700 (PDT)
Received: from mx2-int.auckland.ac.nz (mx2-int.auckland.ac.nz [130.216.12.41]) by ietfa.amsl.com (Postfix) with ESMTP id 0C2F19E8007 for <cfrg@irtf.org>; Fri, 17 Jun 2011 02:34:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=pgut001@cs.auckland.ac.nz; q=dns/txt; s=uoa; t=1308303279; x=1339839279; h=from:to:subject:in-reply-to:message-id:date; z=From:=20Peter=20Gutmann=20<pgut001@cs.auckland.ac.nz> |To:=20cfrg@irtf.org,=20jon@callas.org|Subject:=20Re:=20[ Cfrg]=20What=20crypto=20algorithm=20is=20referenced=20mos t=20in=20RFCs?|In-Reply-To:=20<CF0765AF-383F-423F-A8CC-10 AEB4A3E348@callas.org>|Message-Id:=20<E1QXVRh-0001oH-0L@l ogin01.fos.auckland.ac.nz>|Date:=20Fri,=2017=20Jun=202011 =2021:34:33=20+1200; bh=+m5x37PEva4LUgVjnqmeyQPVyEdybcXgzthJrwpdPHo=; b=VmRXvhGlGlRn3IfrPai+7iaRaNjh9gP03A+osu082bJ0FTyCeG8CARVQ sVNaQGvYv1eFyusPMG1TVVjbkjm91YXSLuo9YC2EBW6+JLadize8Xp/1X UXUOJi5ppqrG8FVydg9N1dUnj4nmasWGV61TUSVuQaSxbl5/YBB1oi5qv Q=;
X-IronPort-AV: E=Sophos;i="4.65,380,1304251200"; d="scan'208";a="67849218"
X-Ironport-HAT: APP-SERVERS - $RELAYED
X-Ironport-Source: 130.216.33.150 - Outgoing - Outgoing
Received: from mf1.fos.auckland.ac.nz ([130.216.33.150]) by mx2-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 17 Jun 2011 21:34:33 +1200
Received: from login01.fos.auckland.ac.nz ([130.216.34.40]) by mf1.fos.auckland.ac.nz with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <pgut001@login01.cs.auckland.ac.nz>) id 1QXVRh-0000tT-GH; Fri, 17 Jun 2011 21:34:33 +1200
Received: from pgut001 by login01.fos.auckland.ac.nz with local (Exim 4.69) (envelope-from <pgut001@login01.cs.auckland.ac.nz>) id 1QXVRh-0001oH-0L; Fri, 17 Jun 2011 21:34:33 +1200
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: cfrg@irtf.org, jon@callas.org
In-Reply-To: <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org>
Message-Id: <E1QXVRh-0001oH-0L@login01.fos.auckland.ac.nz>
Date: Fri, 17 Jun 2011 21:34:33 +1200
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 09:34:41 -0000

Jon Callas <jon@callas.org> writes:

>Phrased another way, I don't think there's a single broken implementation
>that is broken because there are aged RFCs out there. The implementations are
>broken for one reason only -- the implementers don't care.

Actually there's a subset of implementations where the implementers do care,
but the decisions-makers don't (I've run into this a number of times).  This
is why in the past I've called for RFCs to spell out otherwise common-sense
"don't do this" requirements, because the implementers may care but without an
official spec saying "if you do this you're being negligent" they can't get
any decision-makers to move on it.

>Updating all those aged RFCs is a feel-good exercise that will have no effect
>on the real world.

It will have an effect in at least some areas.

Peter.

From mcgrew@cisco.com  Fri Jun 17 11:30:09 2011
Return-Path: <mcgrew@cisco.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF4F9E8023 for <cfrg@ietfa.amsl.com>; Fri, 17 Jun 2011 11:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wU-iioqSS3c9 for <cfrg@ietfa.amsl.com>; Fri, 17 Jun 2011 11:30:08 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfa.amsl.com (Postfix) with ESMTP id 6076D9E8017 for <cfrg@irtf.org>; Fri, 17 Jun 2011 11:30:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mcgrew@cisco.com; l=3428; q=dns/txt; s=iport; t=1308335408; x=1309545008; h=cc:message-id:from:to:in-reply-to: content-transfer-encoding:mime-version:subject:date: references; bh=Q9ptxAGx1+Dz8T6a+kOPCjb3LFxDOx3cAaYveK/WHiU=; b=B76ib8SNbOzgbgNpE/uQd4F4brVBm1gNFSCVnUqhjlvc7kpDOoKbwRfP 34gMWdWBk0f3KhsyRojL22un8W2HlXY4SZGxMoLlD5F/Oddu+hoAtwGD4 +c8/latYop3OjE9NvYMp2Ma0Ftc8V2eYRcGVKE+PHvEwI5VtszYbL0/yU g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAAKd+02rRDoI/2dsb2JhbABEDqZQd6lsnXqDGoMNBIcgij6QHQ
X-IronPort-AV: E=Sophos;i="4.65,382,1304294400"; d="scan'208";a="379333799"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-2.cisco.com with ESMTP; 17 Jun 2011 18:29:53 +0000
Received: from stealth-10-32-254-211.cisco.com (stealth-10-32-254-211.cisco.com [10.32.254.211]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p5HITqGY009911; Fri, 17 Jun 2011 18:29:52 GMT
Message-Id: <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: Joachim@Strombergson.com
In-Reply-To: <4DF8627B.1030702@Strombergson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 17 Jun 2011 11:29:51 -0700
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com>	<4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com>
X-Mailer: Apple Mail (2.936)
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 18:30:09 -0000

Hi Joachim,

+1 on the idea of making sure that current I-Ds that mention MD5 are =20
aware   Probably this could be done by crafting a short paragraph =20
saying something like "We noticed that your RFC references MD5; please =20=

be aware that it is not recommended for new protocols (see RFC6151).  =20=

We suggest that your work not make use of MD5.  If it is necessary to =20=

use MD5 for compatibility with existing implementations, we ask that =20
you cite RFC6151."   (Comments and wordsmithing welcome.)

The first of the current drafts that I looked at was draft-zorn-emu-=20
team-02, and it includes TLS_RSA_WITH_RC4_128_MD5 as a SHOULD, and it =20=

doesn't cite 6151.   So I think the message would help.

David

On Jun 15, 2011, at 12:42 AM, Joachim Str=F6mbergson wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Aloha!
>
> On 2011:06:15 1:59, Jon Callas wrote:
>>>> Would it be fruitful to browse the list try and identify the
>>>> most pressing cases and try to convince the authors that they
>>>> should mend their ways?
>>
>>> Actually, it would.
>>
>> I disagree. What would be helpful would be to identify
>> *implementations* that should mend their ways. The map is not the
>> territory. The RFCs are the maps; the implementations are the
>> territories. If you change the map so that it represents an idealized
>> reality, it's not the same thing as a fixed reality. I think reality
>> is better than this survey of maps indicates.
>
> Jon, I'm sorry for not being more clear. What I was implicitly =20
> referring
> to was the lists of active drafts, not RFCs. I agree that for RFCs =20
> it is
> more important to look at implementations.
>
> But the drafts has not yet become the map. Fixing errors in the map to
> be before it is printed isn't that better than waiting until it has =20=

> been
> printed and in use?
>
> We basically have two different problems:
> (1) Help implemementations to migrate from algorithms we don't trust
> anymore to the algorithms we trust, algorithms specified in updated
> versions of the map.
>
> (2) Help map developers avoid specifying use of the bad algorithms so
> that new implementations don't end up using bad algorithms in the =20
> first
> place.
>
> More understandable? And agreeable?
>
> - --
> Med v=E4nlig h=E4lsning, Yours
>
> Joachim Str=F6mbergson - Alltid i harmonisk sv=E4ngning.
> =3D=20
> =3D=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Kryptoblog - IT-s=E4kerhet p=E5 svenska
> http://www.strombergson.com/kryptoblog
> =3D=20
> =3D=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk34YnsACgkQZoPr8HT30QGNQgCfRC9Nm/5o1FcGfoTB+sdRQ2ch
> 728AoO2gDDaj9T5uV9VpHiTy2yfentZT
> =3DUxo/
> -----END PGP SIGNATURE-----
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg


From mcgrew@cisco.com  Fri Jun 17 11:41:05 2011
Return-Path: <mcgrew@cisco.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0E94228004 for <cfrg@ietfa.amsl.com>; Fri, 17 Jun 2011 11:41:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Ctsz34Gdmh7 for <cfrg@ietfa.amsl.com>; Fri, 17 Jun 2011 11:41:05 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id F01BE22800C for <cfrg@irtf.org>; Fri, 17 Jun 2011 11:41:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mcgrew@cisco.com; l=339; q=dns/txt; s=iport; t=1308336065; x=1309545665; h=cc:message-id:from:to:in-reply-to: content-transfer-encoding:mime-version:subject:date: references; bh=ahXn7GdzZzxLmVcy4kHXyUkAuM/PdmXYTZr4emiBcH4=; b=QV7Xy+Q574PvqmUGDNc5YLYH6nm5xk2aVzU0u+AOdX7+nsjWmjzp0qf4 XrC71yc62sjB+0dkz2onRKdctrDXZOOSJoYxs+l0njteXlS89WJ70e//l 1+Jy88nOVELSvRb4Y69xdEB2ICYZeof4ezT68fbT5vKLQ8QTACW3t1ujY s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUIAB6f+01Io8UR/2dsb2JhbABSmAiOSHeIc6B8nXqGJwSHIIo+kB0
X-IronPort-AV: E=Sophos;i="4.65,382,1304294400"; d="scan'208";a="35789754"
Received: from bgl-core-2.cisco.com ([72.163.197.17]) by ams-iport-2.cisco.com with ESMTP; 17 Jun 2011 18:41:02 +0000
Received: from stealth-10-32-254-211.cisco.com (stealth-10-32-254-211.cisco.com [10.32.254.211]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5HIexmE000399; Fri, 17 Jun 2011 18:41:00 GMT
Message-Id: <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: Joachim@Strombergson.com
In-Reply-To: <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 17 Jun 2011 11:40:50 -0700
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com>	<4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com>
X-Mailer: Apple Mail (2.936)
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 18:41:06 -0000

On Jun 17, 2011, at 11:29 AM, David McGrew wrote:

> Hi Joachim,
>
> +1 on the idea of making sure that current I-Ds that mention MD5 are  
> aware   Probably this could be done by crafting a short paragraph  
> saying something like "We noticed that your RFC references MD5;

aargh, I meant "your I-D references MD5".

David

From stephen.farrell@cs.tcd.ie  Fri Jun 17 12:14:45 2011
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B420B9E8031 for <cfrg@ietfa.amsl.com>; Fri, 17 Jun 2011 12:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.402
X-Spam-Level: 
X-Spam-Status: No, score=-105.402 tagged_above=-999 required=5 tests=[AWL=-0.199, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HjZqMsJk3pwl for <cfrg@ietfa.amsl.com>; Fri, 17 Jun 2011 12:14:44 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 0C4B69E803F for <cfrg@irtf.org>; Fri, 17 Jun 2011 12:14:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 07DD6171BFE; Fri, 17 Jun 2011 20:14:39 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h=date :subject:from:x-mailer:message-id:content-type :content-transfer-encoding:mime-version:in-reply-to:references :received:received:x-virus-scanned; s=cs; t=1308338078; bh=MP0aR Xd4U9yF0gHEZkdJ95YUr246gbRi7dbdGZmqkkA=; b=MR2NqtQD6VkLBeKXF+vP8 +38kw89NueQRc8tj3dT8Ijkn7+/Fc/xMwSn0u978mCA4W9BO3xcqFmoAvINDgb/+ EGwzMzjUQ86KNGvmIwWIfo+X5hk9woMlCtPZALqG4h4tNjOZXDXI2kG7K90fOlK5 FmZ2dv2aq6VtK788NXYWxmJ0Gtxyzp7Ips6G76RgIGBuXmoXSE/0Bq8PkdCtXS+O fp/bB4IaCHepVvLFxxpZtZNobnDlbbVQo0kSVtAZoEjdXX3yCh287SagG8nX4LN/ DdCIKGFUnBMOwhpAjuUYcp72h1eg5OP1DGRJS29GsWEa3MXdnINaywIUc5uoZEfA w==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id xOdyIZwbTbGH; Fri, 17 Jun 2011 20:14:38 +0100 (IST)
Received: from [10.87.48.7] (unknown [86.42.188.156]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 764DB171BFA; Fri, 17 Jun 2011 20:14:36 +0100 (IST)
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com>
In-Reply-To: <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com>
Mime-Version: 1.0 (iPhone Mail 8H7)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie>
X-Mailer: iPhone Mail (8H7)
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Fri, 17 Jun 2011 20:14:34 +0100
To: David McGrew <mcgrew@cisco.com>
Cc: "cfrg@irtf.org" <cfrg@irtf.org>
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 19:14:45 -0000

Seems like a reasonable idea but defining the "we" that are noticing/sending=
 this might be tricky. We don't want IETF WGs to start complaining about the=
 IRTF CFRG crypto police. People can be touchy about stuff like that. I'm no=
t sure how best that'd be done to be honest.

S

On 17 Jun 2011, at 19:40, David McGrew <mcgrew@cisco.com> wrote:

>=20
> On Jun 17, 2011, at 11:29 AM, David McGrew wrote:
>=20
>> Hi Joachim,
>>=20
>> +1 on the idea of making sure that current I-Ds that mention MD5 are awar=
e   Probably this could be done by crafting a short paragraph saying somethi=
ng like "We noticed that your RFC references MD5;
>=20
> aargh, I meant "your I-D references MD5".
>=20
> David
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg

From marshall.eubanks@gmail.com  Sat Jun 18 11:33:12 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B146C11E8093 for <cfrg@ietfa.amsl.com>; Sat, 18 Jun 2011 11:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AXseB+yctLnl for <cfrg@ietfa.amsl.com>; Sat, 18 Jun 2011 11:33:12 -0700 (PDT)
Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by ietfa.amsl.com (Postfix) with ESMTP id 24FFF11E8084 for <cfrg@irtf.org>; Sat, 18 Jun 2011 11:33:12 -0700 (PDT)
Received: by ywf7 with SMTP id 7so2415617ywf.13 for <cfrg@irtf.org>; Sat, 18 Jun 2011 11:33:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hXNBlCUvqxH0v8WzCW1IKU7x9/3/EE+ikBDAmDzHCG4=; b=Ha+4XPv+A4TBgtkB92OOZ/vu4MkB8BELwu7jH7rbEgj5wavP/zFrkukdgohUH1TP7G csXDvyxeet6AjBj9YYUi7PaX7k40qWsvAqhaHzrklLo4Te0/dxUOlmXj7DJzukphHpHb 1qQeyb2wPdAu5yi16P1FPqW8lrrdonQ2eghe4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=I783tfijbpi1n98KQwGsw7yicXkgErf4UtXDON2FD+SfQcNDPfp0FEsm83tVu9DhLM IXymZrPNxpPF6LFuIaRhhgDbtjz9epxjS6xBEVaBfbFhKgp9iQhvlVlYhVlxtuLNix1e L8u+5VLP1yNJXiaT5j5yqLK226r+YnbQpg3wE=
MIME-Version: 1.0
Received: by 10.236.182.225 with SMTP id o61mr812003yhm.257.1308421989704; Sat, 18 Jun 2011 11:33:09 -0700 (PDT)
Received: by 10.146.86.10 with HTTP; Sat, 18 Jun 2011 11:33:09 -0700 (PDT)
In-Reply-To: <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie>
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie>
Date: Sat, 18 Jun 2011 14:33:09 -0400
Message-ID: <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=20cf30563961e9a32104a600bbde
Cc: David McGrew <mcgrew@cisco.com>, "cfrg@irtf.org" <cfrg@irtf.org>
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 18:33:12 -0000

--20cf30563961e9a32104a600bbde
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jun 17, 2011 at 3:14 PM, Stephen Farrell
<stephen.farrell@cs.tcd.ie>wrote:

> Seems like a reasonable idea but defining the "we" that are
> noticing/sending this might be tricky. We don't want IETF WGs to start
> complaining about the IRTF CFRG crypto police. People can be touchy about
> stuff like that. I'm not sure how best that'd be done to be honest.
>
>
Write an I-D along the lines of "MD-5 considered dangerous" and get it
published.

Regards
Marshall




> S
>
> On 17 Jun 2011, at 19:40, David McGrew <mcgrew@cisco.com> wrote:
>
> >
> > On Jun 17, 2011, at 11:29 AM, David McGrew wrote:
> >
> >> Hi Joachim,
> >>
> >> +1 on the idea of making sure that current I-Ds that mention MD5 are
> aware   Probably this could be done by crafting a short paragraph saying
> something like "We noticed that your RFC references MD5;
> >
> > aargh, I meant "your I-D references MD5".
> >
> > David
> > _______________________________________________
> > Cfrg mailing list
> > Cfrg@irtf.org
> > http://www.irtf.org/mailman/listinfo/cfrg
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg
>

--20cf30563961e9a32104a600bbde
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Fri, Jun 17, 2011 at 3:14 PM, Stephen=
 Farrell <span dir=3D"ltr">&lt;<a href=3D"mailto:stephen.farrell@cs.tcd.ie"=
>stephen.farrell@cs.tcd.ie</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex;">
Seems like a reasonable idea but defining the &quot;we&quot; that are notic=
ing/sending this might be tricky. We don&#39;t want IETF WGs to start compl=
aining about the IRTF CFRG crypto police. People can be touchy about stuff =
like that. I&#39;m not sure how best that&#39;d be done to be honest.<br>

<font color=3D"#888888"><br></font></blockquote><div><br></div><div>Write a=
n I-D along the lines of &quot;MD-5 considered dangerous&quot; and get it p=
ublished.=A0</div><div><br></div><div>Regards</div><div>Marshall</div><div>
<br></div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><fon=
t color=3D"#888888">
S<br>
</font><div><div></div><div class=3D"h5"><br>
On 17 Jun 2011, at 19:40, David McGrew &lt;<a href=3D"mailto:mcgrew@cisco.c=
om">mcgrew@cisco.com</a>&gt; wrote:<br>
<br>
&gt;<br>
&gt; On Jun 17, 2011, at 11:29 AM, David McGrew wrote:<br>
&gt;<br>
&gt;&gt; Hi Joachim,<br>
&gt;&gt;<br>
&gt;&gt; +1 on the idea of making sure that current I-Ds that mention MD5 a=
re aware =A0 Probably this could be done by crafting a short paragraph sayi=
ng something like &quot;We noticed that your RFC references MD5;<br>
&gt;<br>
&gt; aargh, I meant &quot;your I-D references MD5&quot;.<br>
&gt;<br>
&gt; David<br>
&gt; _______________________________________________<br>
&gt; Cfrg mailing list<br>
&gt; <a href=3D"mailto:Cfrg@irtf.org">Cfrg@irtf.org</a><br>
&gt; <a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" target=3D"_blank=
">http://www.irtf.org/mailman/listinfo/cfrg</a><br>
_______________________________________________<br>
Cfrg mailing list<br>
<a href=3D"mailto:Cfrg@irtf.org">Cfrg@irtf.org</a><br>
<a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" target=3D"_blank">htt=
p://www.irtf.org/mailman/listinfo/cfrg</a><br>
</div></div></blockquote></div><br>

--20cf30563961e9a32104a600bbde--

From stephen.farrell@cs.tcd.ie  Sat Jun 18 11:49:12 2011
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC6211E8112 for <cfrg@ietfa.amsl.com>; Sat, 18 Jun 2011 11:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.477
X-Spam-Level: 
X-Spam-Status: No, score=-105.477 tagged_above=-999 required=5 tests=[AWL=-0.275, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eCI+-OS2RvNM for <cfrg@ietfa.amsl.com>; Sat, 18 Jun 2011 11:49:11 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 39B6411E80E0 for <cfrg@irtf.org>; Sat, 18 Jun 2011 11:49:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id B19B4171C17; Sat, 18 Jun 2011 19:49:03 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h=date :subject:from:x-mailer:message-id:content-type :content-transfer-encoding:mime-version:in-reply-to:references :received:received:x-virus-scanned; s=cs; t=1308422942; bh=68KaK 0g/ZXi+Pw817RzMeTb4FnS3aAebwTynJ7Hqlqc=; b=eK/NABRL1rDZHvMusvdsi 4RlNfKDH5D2L1sinc8PJziuwaSYrk86KPwIWTEleZHW1Jj59JRbtsZZtFvvrZjbW yXdkPLyFCI/4nSq9SuObt0M7Quzeru5DnCT/t4HY/0E7fNJw5AUDyItr6i1gNgy+ pa8rXk0dqQ6WvcWXs1nyPI61FLhVIfNPu5MHPaH4aDwImzUEWsTAu2teKWrlGWfU K03N2bjUimVLF/XanH2VqHJuLHfm3u7297VYeUUhfS4cCwDgEk8Dy83+6w0i/YdK k05ekQ2dIT8569k6J8+UdXBTF9AXJpb83OxzpUpsGbQSxWkNS2npg2FG2Nh9ckNE w==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id JL9+GcaO9qNY; Sat, 18 Jun 2011 19:49:02 +0100 (IST)
Received: from [10.87.48.3] (unknown [86.42.30.134]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 3021D171C02; Sat, 18 Jun 2011 19:48:59 +0100 (IST)
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie> <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com>
In-Reply-To: <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com>
Mime-Version: 1.0 (iPhone Mail 8H7)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary=Apple-Mail-4--596742733
Message-Id: <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie>
X-Mailer: iPhone Mail (8H7)
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Sat, 18 Jun 2011 19:48:57 +0100
To: Marshall Eubanks <marshall.eubanks@gmail.com>
Cc: David McGrew <mcgrew@cisco.com>, "cfrg@irtf.org" <cfrg@irtf.org>
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 18:49:12 -0000

--Apple-Mail-4--596742733
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



On 18 Jun 2011, at 19:33, Marshall Eubanks <marshall.eubanks@gmail.com> wrot=
e:

>=20
>=20
> On Fri, Jun 17, 2011 at 3:14 PM, Stephen Farrell <stephen.farrell@cs.tcd.i=
e> wrote:
> Seems like a reasonable idea but defining the "we" that are noticing/sendi=
ng this might be tricky. We don't want IETF WGs to start complaining about t=
he IRTF CFRG crypto police. People can be touchy about stuff like that. I'm n=
ot sure how best that'd be done to be honest.
>=20
>=20
> Write an I-D along the lines of "MD-5 considered dangerous" and get it pub=
lished.=20

RFC6151?
S

>=20
> Regards
> Marshall
>=20
>=20
> =20
> S
>=20
> On 17 Jun 2011, at 19:40, David McGrew <mcgrew@cisco.com> wrote:
>=20
> >
> > On Jun 17, 2011, at 11:29 AM, David McGrew wrote:
> >
> >> Hi Joachim,
> >>
> >> +1 on the idea of making sure that current I-Ds that mention MD5 are aw=
are   Probably this could be done by crafting a short paragraph saying somet=
hing like "We noticed that your RFC references MD5;
> >
> > aargh, I meant "your I-D references MD5".
> >
> > David
> > _______________________________________________
> > Cfrg mailing list
> > Cfrg@irtf.org
> > http://www.irtf.org/mailman/listinfo/cfrg
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg
>=20

--Apple-Mail-4--596742733
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=utf-8

<html><body bgcolor="#FFFFFF"><div><br><br>On 18 Jun 2011, at 19:33, Marshall Eubanks &lt;<a href="mailto:marshall.eubanks@gmail.com">marshall.eubanks@gmail.com</a>&gt; wrote:<br><br></div><div></div><blockquote type="cite"><div><br><br><div class="gmail_quote">On Fri, Jun 17, 2011 at 3:14 PM, Stephen Farrell <span dir="ltr">&lt;<a href="mailto:stephen.farrell@cs.tcd.ie"><a href="mailto:stephen.farrell@cs.tcd.ie">stephen.farrell@cs.tcd.ie</a></a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Seems like a reasonable idea but defining the "we" that are noticing/sending this might be tricky. We don't want IETF WGs to start complaining about the IRTF CFRG crypto police. People can be touchy about stuff like that. I'm not sure how best that'd be done to be honest.<br>

<font color="#888888"><br></font></blockquote><div><br></div><div>Write an I-D along the lines of "MD-5 considered dangerous" and get it published.&nbsp;</div></div></div></blockquote><div><br></div><div>RFC6151?</div><div>S</div><br><blockquote type="cite"><div><div class="gmail_quote"><div><br></div><div>Regards</div><div>Marshall</div><div>
<br></div><div><br></div><div>&nbsp;</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><font color="#888888">
S<br>
</font><div><div></div><div class="h5"><br>
On 17 Jun 2011, at 19:40, David McGrew &lt;<a href="mailto:mcgrew@cisco.com"><a href="mailto:mcgrew@cisco.com">mcgrew@cisco.com</a></a>&gt; wrote:<br>
<br>
&gt;<br>
&gt; On Jun 17, 2011, at 11:29 AM, David McGrew wrote:<br>
&gt;<br>
&gt;&gt; Hi Joachim,<br>
&gt;&gt;<br>
&gt;&gt; +1 on the idea of making sure that current I-Ds that mention MD5 are aware &nbsp; Probably this could be done by crafting a short paragraph saying something like "We noticed that your RFC references MD5;<br>
&gt;<br>
&gt; aargh, I meant "your I-D references MD5".<br>
&gt;<br>
&gt; David<br>
&gt; _______________________________________________<br>
&gt; Cfrg mailing list<br>
&gt; <a href="mailto:Cfrg@irtf.org"><a href="mailto:Cfrg@irtf.org">Cfrg@irtf.org</a></a><br>
&gt; <a href="http://www.irtf.org/mailman/listinfo/cfrg" target="_blank"><a href="http://www.irtf.org/mailman/listinfo/cfrg">http://www.irtf.org/mailman/listinfo/cfrg</a></a><br>
_______________________________________________<br>
Cfrg mailing list<br>
<a href="mailto:Cfrg@irtf.org"><a href="mailto:Cfrg@irtf.org">Cfrg@irtf.org</a></a><br>
<a href="http://www.irtf.org/mailman/listinfo/cfrg" target="_blank"><a href="http://www.irtf.org/mailman/listinfo/cfrg">http://www.irtf.org/mailman/listinfo/cfrg</a></a><br>
</div></div></blockquote></div><br>
</div></blockquote></body></html>
--Apple-Mail-4--596742733--

From marshall.eubanks@gmail.com  Sat Jun 18 12:09:24 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7823311E820A for <cfrg@ietfa.amsl.com>; Sat, 18 Jun 2011 12:09:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IPt0tUcwtTk2 for <cfrg@ietfa.amsl.com>; Sat, 18 Jun 2011 12:09:23 -0700 (PDT)
Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by ietfa.amsl.com (Postfix) with ESMTP id 856BE11E8208 for <cfrg@irtf.org>; Sat, 18 Jun 2011 12:09:23 -0700 (PDT)
Received: by yic13 with SMTP id 13so2429037yic.13 for <cfrg@irtf.org>; Sat, 18 Jun 2011 12:09:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=qTVMMdRDtfuDkfH9UX+4/tO7byBZF+ghJHpCyALXUy0=; b=xvBk5CUPFGiRGzBR7Eix0Ycsg6OT5AG7+V0bYF5e1GPKjHTYmQVEeTsNQ4hZWc8prL UBvPX91B0piYMdd4cJhb/G2pKuLL1wXGBVIDH3rxpnNQ8V89xFV6Kw6fc6PDaoFz1cmV d6HctW3r7hSC8ox2MxxraBOF+mKtWw+ev76Zs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=e0TzD2v//D9Jjco5Z26BRD+yJSK3C1w2UGdNzfCyg9KHcM5uyo89dL3+Mjamm4O1wc 4TE1htWKGnwVoNMVdp6JQw2LLC8zlyS+bSD0gcSMu9a+zcRW1yLYNTcwRI/+wmkXqS/m rcQ6y6cksfuTLk38cVcWjQHv8IGAk0oQqccw8=
MIME-Version: 1.0
Received: by 10.236.76.69 with SMTP id a45mr5581413yhe.56.1308424161109; Sat, 18 Jun 2011 12:09:21 -0700 (PDT)
Received: by 10.146.86.10 with HTTP; Sat, 18 Jun 2011 12:09:21 -0700 (PDT)
In-Reply-To: <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie>
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie> <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com> <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie>
Date: Sat, 18 Jun 2011 15:09:21 -0400
Message-ID: <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=20cf303b407756a77f04a6013d64
Cc: David McGrew <mcgrew@cisco.com>, "cfrg@irtf.org" <cfrg@irtf.org>
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 19:09:24 -0000

--20cf303b407756a77f04a6013d64
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Jun 18, 2011 at 2:48 PM, Stephen Farrell
<stephen.farrell@cs.tcd.ie>wrote:

>
>
> On 18 Jun 2011, at 19:33, Marshall Eubanks <marshall.eubanks@gmail.com>
> wrote:
>
>
>
> On Fri, Jun 17, 2011 at 3:14 PM, Stephen Farrell <<stephen.farrell@cs.tcd.ie>
> stephen.farrell@cs.tcd.ie> wrote:
>
>> Seems like a reasonable idea but defining the "we" that are
>> noticing/sending this might be tricky. We don't want IETF WGs to start
>> complaining about the IRTF CFRG crypto police. People can be touchy about
>> stuff like that. I'm not sure how best that'd be done to be honest.
>>
>>
> Write an I-D along the lines of "MD-5 considered dangerous" and get it
> published.
>
>
> RFC6151?
>

I thought that there was something like this. Then quote this

   MD5 is no longer acceptable where collision resistance is required
   such as digital signatures.  It is not urgent to stop using MD5 in
   other ways, such as HMAC-MD5; however, since MD5 must not be used for
   digital signatures, new protocol designs should not employ HMAC-MD5.


and point out how the new I-D disagrees with it.

That's not being the Crypto police. After all, the IESG approved this RFC
and new use of MD5 should get pushback when an I-D gets to the IESG.
Pointing this out earlier is just saving people's time, and ADs generally
appreciate having their time saved.

Regards
Marshall


> S
>
>
> Regards
> Marshall
>
>
>
>
>> S
>>
>> On 17 Jun 2011, at 19:40, David McGrew < <mcgrew@cisco.com>
>> mcgrew@cisco.com> wrote:
>>
>> >
>> > On Jun 17, 2011, at 11:29 AM, David McGrew wrote:
>> >
>> >> Hi Joachim,
>> >>
>> >> +1 on the idea of making sure that current I-Ds that mention MD5 are
>> aware   Probably this could be done by crafting a short paragraph saying
>> something like "We noticed that your RFC references MD5;
>> >
>> > aargh, I meant "your I-D references MD5".
>> >
>> > David
>> > _______________________________________________
>> > Cfrg mailing list
>> > <Cfrg@irtf.org>Cfrg@irtf.org
>> > <http://www.irtf.org/mailman/listinfo/cfrg>
>> http://www.irtf.org/mailman/listinfo/cfrg
>> _______________________________________________
>> Cfrg mailing list
>>  <Cfrg@irtf.org>Cfrg@irtf.org
>>  <http://www.irtf.org/mailman/listinfo/cfrg>
>> http://www.irtf.org/mailman/listinfo/cfrg
>>
>
>

--20cf303b407756a77f04a6013d64
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Sat, Jun 18, 2011 at 2:48 PM, Stephen=
 Farrell <span dir=3D"ltr">&lt;<a href=3D"mailto:stephen.farrell@cs.tcd.ie"=
>stephen.farrell@cs.tcd.ie</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex;">
<div bgcolor=3D"#FFFFFF"><div class=3D"im"><div><br><br>On 18 Jun 2011, at =
19:33, Marshall Eubanks &lt;<a href=3D"mailto:marshall.eubanks@gmail.com" t=
arget=3D"_blank">marshall.eubanks@gmail.com</a>&gt; wrote:<br><br></div><di=
v></div>
<blockquote type=3D"cite"><div><br><br><div class=3D"gmail_quote">On Fri, J=
un 17, 2011 at 3:14 PM, Stephen Farrell <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:stephen.farrell@cs.tcd.ie" target=3D"_blank"></a><a href=3D"mailto:ste=
phen.farrell@cs.tcd.ie" target=3D"_blank">stephen.farrell@cs.tcd.ie</a>&gt;=
</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Seems like a reasonable idea but defining the &quot;we&quot; that are notic=
ing/sending this might be tricky. We don&#39;t want IETF WGs to start compl=
aining about the IRTF CFRG crypto police. People can be touchy about stuff =
like that. I&#39;m not sure how best that&#39;d be done to be honest.<br>


<font color=3D"#888888"><br></font></blockquote><div><br></div><div>Write a=
n I-D along the lines of &quot;MD-5 considered dangerous&quot; and get it p=
ublished.=A0</div></div></div></blockquote><div><br></div></div><div>RFC615=
1?</div>
</div></blockquote><div><br></div><div>I thought that there was something l=
ike this. Then quote this</div><div><br></div><div><span class=3D"Apple-sty=
le-span" style=3D"font-family: Times; font-size: 13.3333px; "><pre class=3D=
"newpage" style=3D"font-size: 1em; margin-top: 0px; margin-bottom: 0px; pag=
e-break-before: always; ">
   MD5 is no longer acceptable where collision resistance is required
   such as digital signatures.  It is not urgent to stop using MD5 in
   other ways, such as HMAC-MD5; however, since MD5 must not be used for
   digital signatures, new protocol designs should not employ HMAC-MD5.</pr=
e><pre class=3D"newpage" style=3D"font-size: 1em; margin-top: 0px; margin-b=
ottom: 0px; page-break-before: always; "><br></pre></span></div><div>and po=
int out how the new I-D disagrees with it.</div>
<div><br></div><div>That&#39;s not being the Crypto police. After all, the =
IESG approved this RFC and new use of MD5 should get pushback when an I-D g=
ets to the IESG. Pointing this out earlier is just saving people&#39;s time=
, and ADs generally appreciate having their time saved.</div>
<div><br></div><div>Regards</div><div>Marshall</div><div>=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex;"><div bgcolor=3D"#FFFFFF"><div>S</div><div class=3D"i=
m"><br>
<blockquote type=3D"cite"><div><div class=3D"gmail_quote"><div><br></div><d=
iv>Regards</div><div>Marshall</div><div>
<br></div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font=
 color=3D"#888888">
S<br>
</font><div><div></div><div><br>
On 17 Jun 2011, at 19:40, David McGrew &lt;<a href=3D"mailto:mcgrew@cisco.c=
om" target=3D"_blank"></a><a href=3D"mailto:mcgrew@cisco.com" target=3D"_bl=
ank">mcgrew@cisco.com</a>&gt; wrote:<br>
<br>
&gt;<br>
&gt; On Jun 17, 2011, at 11:29 AM, David McGrew wrote:<br>
&gt;<br>
&gt;&gt; Hi Joachim,<br>
&gt;&gt;<br>
&gt;&gt; +1 on the idea of making sure that current I-Ds that mention MD5 a=
re aware =A0 Probably this could be done by crafting a short paragraph sayi=
ng something like &quot;We noticed that your RFC references MD5;<br>
&gt;<br>
&gt; aargh, I meant &quot;your I-D references MD5&quot;.<br>
&gt;<br>
&gt; David<br>
&gt; _______________________________________________<br>
&gt; Cfrg mailing list<br>
&gt; <a href=3D"mailto:Cfrg@irtf.org" target=3D"_blank"></a><a href=3D"mail=
to:Cfrg@irtf.org" target=3D"_blank">Cfrg@irtf.org</a><br>
&gt; <a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" target=3D"_blank=
"></a><a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" target=3D"_blan=
k">http://www.irtf.org/mailman/listinfo/cfrg</a><br>
_______________________________________________<br>
Cfrg mailing list<br>
<a href=3D"mailto:Cfrg@irtf.org" target=3D"_blank"></a><a href=3D"mailto:Cf=
rg@irtf.org" target=3D"_blank">Cfrg@irtf.org</a><br>
<a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" target=3D"_blank"></a=
><a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" target=3D"_blank">ht=
tp://www.irtf.org/mailman/listinfo/cfrg</a><br>
</div></div></blockquote></div><br>
</div></blockquote></div></div></blockquote></div><br>

--20cf303b407756a77f04a6013d64--

From stephen.farrell@cs.tcd.ie  Sat Jun 18 13:35:48 2011
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3750221F859D for <cfrg@ietfa.amsl.com>; Sat, 18 Jun 2011 13:35:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.12
X-Spam-Level: 
X-Spam-Status: No, score=-106.12 tagged_above=-999 required=5 tests=[AWL=0.479, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z7wtkoC8OcnF for <cfrg@ietfa.amsl.com>; Sat, 18 Jun 2011 13:35:47 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 21B0021F859C for <cfrg@irtf.org>; Sat, 18 Jun 2011 13:35:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id E9577171C17; Sat, 18 Jun 2011 21:35:41 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1308429341; bh=XZs7LxV6iKxBsC O5Lyeajs5fozsLE7aAdYQjBRKyC6E=; b=1qVTuaP5gOto2mBvSrfhn8h4fzBSx8 09ihVhBXOaNZH2H2vGcv0QZ5/VooH05i1yF/kLOn2EYV/N17Rc43VPAgHcY51WIQ cfobsdHeDNDqR4A0d1aDFCMc1NSlV77kKFAEFAtAX+CDOaldNgc0bC7N6m9ripA/ On5AWisNd5TkESy0qXyQen0Kq12cFcZndSH4s2Auk64npgZZMxPPBEQVTCU1pldK jdNplHBK9GgVFKGCj3PHUCkgqFoabESXQmIIFuNuVQ0NOWS8iFn3zY5fGYX/TWGy 5RqWvGVscD8ytli/Y/jFh6jzPUBOGdhIAi3AryCVZqrkVf04RA/Muk5g==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id gzcqLTEjzlC0; Sat, 18 Jun 2011 21:35:41 +0100 (IST)
Received: from [10.87.48.10] (unknown [86.42.30.134]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id EE078171C02; Sat, 18 Jun 2011 21:35:39 +0100 (IST)
Message-ID: <4DFD0C1B.6070909@cs.tcd.ie>
Date: Sat, 18 Jun 2011 21:35:39 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Marshall Eubanks <marshall.eubanks@gmail.com>
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com>	<4DF6FCAD.1000704@Strombergson.com>	<4DF7E236.3060603@ieca.com>	<CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org>	<4DF8627B.1030702@Strombergson.com>	<74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com>	<DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com>	<6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie>	<BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com>	<D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie> <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com>
In-Reply-To: <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: David McGrew <mcgrew@cisco.com>, "cfrg@irtf.org" <cfrg@irtf.org>
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 20:35:48 -0000

On 18/06/11 20:09, Marshall Eubanks wrote:
> On Sat, Jun 18, 2011 at 2:48 PM, Stephen Farrell
> <stephen.farrell@cs.tcd.ie>wrote:
> 
>>
>>
>> On 18 Jun 2011, at 19:33, Marshall Eubanks <marshall.eubanks@gmail.com>
>> wrote:
>>
>>
>>
>> On Fri, Jun 17, 2011 at 3:14 PM, Stephen Farrell <<stephen.farrell@cs.tcd.ie>
>> stephen.farrell@cs.tcd.ie> wrote:
>>
>>> Seems like a reasonable idea but defining the "we" that are
>>> noticing/sending this might be tricky. We don't want IETF WGs to start
>>> complaining about the IRTF CFRG crypto police. People can be touchy about
>>> stuff like that. I'm not sure how best that'd be done to be honest.
>>>
>>>
>> Write an I-D along the lines of "MD-5 considered dangerous" and get it
>> published.
>>
>>
>> RFC6151?
>>
> 
> I thought that there was something like this. Then quote this
> 
>    MD5 is no longer acceptable where collision resistance is required
>    such as digital signatures.  It is not urgent to stop using MD5 in
>    other ways, such as HMAC-MD5; however, since MD5 must not be used for
>    digital signatures, new protocol designs should not employ HMAC-MD5.
> 
> 
> and point out how the new I-D disagrees with it.
> 
> That's not being the Crypto police. After all, the IESG approved this RFC
> and new use of MD5 should get pushback when an I-D gets to the IESG.
> Pointing this out earlier is just saving people's time, and ADs generally
> appreciate having their time saved.

Sure, I'm all for it if its not perceived as adding bureaucracy.
Don't forget we already have up to 6 reviews etc. on stuff at
last-call time.

If someone has a way to generate a report identifying relevant
-00 and -01 drafts maybe, and someone else is willing to ping
authors and explain when they then say "so what" that might
be good.

I'd say a concrete proposal for what and how to do it, sent to
this list (and then probably saag) for sanity checking would
be good. So, who's stepping up to figure out details for such
a proposal?

S.


> 
> Regards
> Marshall
> 
> 
>> S
>>
>>
>> Regards
>> Marshall
>>
>>
>>
>>
>>> S
>>>
>>> On 17 Jun 2011, at 19:40, David McGrew < <mcgrew@cisco.com>
>>> mcgrew@cisco.com> wrote:
>>>
>>>>
>>>> On Jun 17, 2011, at 11:29 AM, David McGrew wrote:
>>>>
>>>>> Hi Joachim,
>>>>>
>>>>> +1 on the idea of making sure that current I-Ds that mention MD5 are
>>> aware   Probably this could be done by crafting a short paragraph saying
>>> something like "We noticed that your RFC references MD5;
>>>>
>>>> aargh, I meant "your I-D references MD5".
>>>>
>>>> David
>>>> _______________________________________________
>>>> Cfrg mailing list
>>>> <Cfrg@irtf.org>Cfrg@irtf.org
>>>> <http://www.irtf.org/mailman/listinfo/cfrg>
>>> http://www.irtf.org/mailman/listinfo/cfrg
>>> _______________________________________________
>>> Cfrg mailing list
>>>  <Cfrg@irtf.org>Cfrg@irtf.org
>>>  <http://www.irtf.org/mailman/listinfo/cfrg>
>>> http://www.irtf.org/mailman/listinfo/cfrg
>>>
>>
>>
> 

From mcgrew@cisco.com  Mon Jun 20 08:25:09 2011
Return-Path: <mcgrew@cisco.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53C2421F8659 for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 08:25:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n623-XiL-xn1 for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 08:25:07 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfa.amsl.com (Postfix) with ESMTP id 8C57C21F8662 for <cfrg@irtf.org>; Mon, 20 Jun 2011 08:24:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mcgrew@cisco.com; l=5375; q=dns/txt; s=iport; t=1308583494; x=1309793094; h=cc:message-id:from:to:in-reply-to: content-transfer-encoding:mime-version:subject:date: references; bh=oQkWnVYHLL0sOhZcx7dzjyift2pbF22Sm5iNk1fW83k=; b=B+AYP4UY5Iia5/M5PRWWxx92Y8Ld9o5EA9zNcK/zhVPZeFnogsQyGbAp efmu6bh6rs93K9/UPxdMq+aZKbkWkVSYzB92VFteRWElaycDZt1DWSdmt ctGzjJhcl51tuE7IgTaYsDgks0aX0vgPdEKu7OUky21HeoISIY7R7hOYs Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAPtk/02rRDoH/2dsb2JhbABTpl93iHOhXp1nhioEhyCKPoklhnw
X-IronPort-AV: E=Sophos;i="4.65,394,1304294400"; d="scan'208";a="380920234"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-2.cisco.com with ESMTP; 20 Jun 2011 15:23:49 +0000
Received: from stealth-10-32-254-213.cisco.com (stealth-10-32-254-213.cisco.com [10.32.254.213]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5KFNltF003583; Mon, 20 Jun 2011 15:23:48 GMT
Message-Id: <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
In-Reply-To: <4DFD0C1B.6070909@cs.tcd.ie>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 20 Jun 2011 08:23:47 -0700
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com>	<4DF6FCAD.1000704@Strombergson.com>	<4DF7E236.3060603@ieca.com>	<CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org>	<4DF8627B.1030702@Strombergson.com>	<74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com>	<DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com>	<6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie>	<BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com>	<D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie> <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com> <4DFD0C1B.6070909@cs.tcd.ie>
X-Mailer: Apple Mail (2.936)
Cc: Sean Turner <turners@ieca.com>, cfrg@irtf.org, Marshall Eubanks <marshall.eubanks@gmail.com>
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 15:25:09 -0000

Hi Stephen,

On Jun 18, 2011, at 1:35 PM, Stephen Farrell wrote:

>
>
> On 18/06/11 20:09, Marshall Eubanks wrote:
>> On Sat, Jun 18, 2011 at 2:48 PM, Stephen Farrell
>> <stephen.farrell@cs.tcd.ie>wrote:
>>
>>>
>>>
>>> On 18 Jun 2011, at 19:33, Marshall Eubanks <marshall.eubanks@gmail.com 
>>> >
>>> wrote:
>>>
>>>
>>>
>>> On Fri, Jun 17, 2011 at 3:14 PM, Stephen Farrell <<stephen.farrell@cs.tcd.ie 
>>> >
>>> stephen.farrell@cs.tcd.ie> wrote:
>>>
>>>> Seems like a reasonable idea but defining the "we" that are
>>>> noticing/sending this might be tricky. We don't want IETF WGs to  
>>>> start
>>>> complaining about the IRTF CFRG crypto police. People can be  
>>>> touchy about
>>>> stuff like that. I'm not sure how best that'd be done to be honest.
>>>>
>>>>
>>> Write an I-D along the lines of "MD-5 considered dangerous" and  
>>> get it
>>> published.
>>>
>>>
>>> RFC6151?
>>>
>>
>> I thought that there was something like this. Then quote this
>>
>>   MD5 is no longer acceptable where collision resistance is required
>>   such as digital signatures.  It is not urgent to stop using MD5 in
>>   other ways, such as HMAC-MD5; however, since MD5 must not be used  
>> for
>>   digital signatures, new protocol designs should not employ HMAC- 
>> MD5.
>>
>>
>> and point out how the new I-D disagrees with it.
>>
>> That's not being the Crypto police. After all, the IESG approved  
>> this RFC
>> and new use of MD5 should get pushback when an I-D gets to the IESG.
>> Pointing this out earlier is just saving people's time, and ADs  
>> generally
>> appreciate having their time saved.
>
> Sure, I'm all for it if its not perceived as adding bureaucracy.
> Don't forget we already have up to 6 reviews etc. on stuff at
> last-call time.
>
> If someone has a way to generate a report identifying relevant
> -00 and -01 drafts maybe, and someone else is willing to ping
> authors and explain when they then say "so what" that might
> be good.
>
> I'd say a concrete proposal for what and how to do it, sent to
> this list (and then probably saag) for sanity checking would
> be good. So, who's stepping up to figure out details for such
> a proposal?

I have a set of scripts for producing the list of relevant drafts  
(containing more AWK programming than I would prefer to admit to ;-)   
It would probably be good to provide more detailed information about  
the 00 I-Ds, such as the crypto algorithm(s) that they reference.  In  
the case of MD5, it would be good to know which I-Ds mention MD5 but  
don't mention RFC6151.  I am happy to contribute this as an "official"  
RG contribution if people feel that is important (I'm not sure why it  
would be, but if it makes process easier I can generate a doc or a  
webpage with the IETF Trust copyright notice).

There are about 120 00-version drafts that reference crypto  
currently.  Most of those are doing the right thing, and won't require  
much if any work from crypto-reviewers.   This suggests that the  
"steady state" workload of having CFRG review the uses of crypto in  
new I-Ds will be manageable, if we can get a couple of volunteers.   
There are also 170 current I-Ds that mention MD5, which suggests that  
the short-term workload will be higher than the steady state  
workload.  If anyone is interested, please send a note either to the  
list, or to Stephen, Sean, and me.

I think the best way to operate would be find some volunteers to go  
through the I-Ds that mention MD5, and send out a notification to  
authors where needed.  If there are cases in which the actual security  
properties are not clear, those should be brought back to the RG for  
discussion.  If this seems fruitful, we can apply the process to -00 I- 
Ds going forward.

Looking ahead a bit, it seems like it would be valuable for the RG to  
produce a document describing the crypto algorithms that are in use  
and providing guidance.  I think it would be healthy to have a  
discussion in CFRG on the guidance, and this document could be  
something that we point to.

David

>
> S.
>
>
>>
>> Regards
>> Marshall
>>
>>
>>> S
>>>
>>>
>>> Regards
>>> Marshall
>>>
>>>
>>>
>>>
>>>> S
>>>>
>>>> On 17 Jun 2011, at 19:40, David McGrew < <mcgrew@cisco.com>
>>>> mcgrew@cisco.com> wrote:
>>>>
>>>>>
>>>>> On Jun 17, 2011, at 11:29 AM, David McGrew wrote:
>>>>>
>>>>>> Hi Joachim,
>>>>>>
>>>>>> +1 on the idea of making sure that current I-Ds that mention  
>>>>>> MD5 are
>>>> aware   Probably this could be done by crafting a short paragraph  
>>>> saying
>>>> something like "We noticed that your RFC references MD5;
>>>>>
>>>>> aargh, I meant "your I-D references MD5".
>>>>>
>>>>> David
>>>>> _______________________________________________
>>>>> Cfrg mailing list
>>>>> <Cfrg@irtf.org>Cfrg@irtf.org
>>>>> <http://www.irtf.org/mailman/listinfo/cfrg>
>>>> http://www.irtf.org/mailman/listinfo/cfrg
>>>> _______________________________________________
>>>> Cfrg mailing list
>>>> <Cfrg@irtf.org>Cfrg@irtf.org
>>>> <http://www.irtf.org/mailman/listinfo/cfrg>
>>>> http://www.irtf.org/mailman/listinfo/cfrg
>>>>
>>>
>>>
>>
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg


From marshall.eubanks@gmail.com  Mon Jun 20 08:33:55 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 612339E8026 for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 08:33:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.765
X-Spam-Level: 
X-Spam-Status: No, score=-102.765 tagged_above=-999 required=5 tests=[AWL=-0.833, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5rwn74dVFkaZ for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 08:33:53 -0700 (PDT)
Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA5D9E801A for <cfrg@irtf.org>; Mon, 20 Jun 2011 08:33:53 -0700 (PDT)
Received: by gyf3 with SMTP id 3so560198gyf.13 for <cfrg@irtf.org>; Mon, 20 Jun 2011 08:33:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=UJL/lheG4m4Aa+eIvn7/YKBJW5uYph9JSeigwaY3RPo=; b=qh9+5kwF9SpFvqmdb0aMOigADZOyUZR9DZ8WO8b6+OX1GTUkebBouWCJ4+J6AxLiGr Ph/wRn7EG5H7J2vNMo0zW2FQRtp8x/yjcleNSgX6CCN1yWQeBcyeaneCzjC874UzogEB AsrbcEE/hQPWl5rr39pqs5cHMZH1lx5ADA2CY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=CmqLVlA5dMpucbcsGGHKtQ9Ov+b8uSrjVEkpsZ1Zjo5KAdB27MQ6i7teoFnpzwbgD8 QYIAXlCrsFlViZsNDbL523QSJNW5moUvbA7nMoMiBp1LEYXSan7xdTbEfWwwaRIrUfRU FcmzvJ/hOsDO7fCKs1v5brngHeNrhq6+Uc2VE=
MIME-Version: 1.0
Received: by 10.236.157.36 with SMTP id n24mr3615028yhk.190.1308584032557; Mon, 20 Jun 2011 08:33:52 -0700 (PDT)
Received: by 10.146.86.10 with HTTP; Mon, 20 Jun 2011 08:33:52 -0700 (PDT)
In-Reply-To: <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com>
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie> <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com> <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie> <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com> <4DFD0C1B.6070909@cs.tcd.ie> <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com>
Date: Mon, 20 Jun 2011 11:33:52 -0400
Message-ID: <BANLkTim8VCPY9NhNbYkOE2u2HMR_r9s7sg@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: David McGrew <mcgrew@cisco.com>
Content-Type: multipart/alternative; boundary=20cf303f64166b596004a626762a
Cc: Sean Turner <turners@ieca.com>, cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 15:33:55 -0000

--20cf303f64166b596004a626762a
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jun 20, 2011 at 11:23 AM, David McGrew <mcgrew@cisco.com> wrote:

> Hi Stephen,
>
>
> On Jun 18, 2011, at 1:35 PM, Stephen Farrell wrote:
>
>
>>
>> On 18/06/11 20:09, Marshall Eubanks wrote:
>>
>>> On Sat, Jun 18, 2011 at 2:48 PM, Stephen Farrell
>>> <stephen.farrell@cs.tcd.ie>**wrote:
>>>
>>>
>>>>
>>>> On 18 Jun 2011, at 19:33, Marshall Eubanks <marshall.eubanks@gmail.com>
>>>> wrote:
>>>>
>>>>
>>>>
>>>> On Fri, Jun 17, 2011 at 3:14 PM, Stephen Farrell <<
>>>> stephen.farrell@cs.tcd.ie>
>>>> stephen.farrell@cs.tcd.ie> wrote:
>>>>
>>>>  Seems like a reasonable idea but defining the "we" that are
>>>>> noticing/sending this might be tricky. We don't want IETF WGs to start
>>>>> complaining about the IRTF CFRG crypto police. People can be touchy
>>>>> about
>>>>> stuff like that. I'm not sure how best that'd be done to be honest.
>>>>>
>>>>>
>>>>>  Write an I-D along the lines of "MD-5 considered dangerous" and get it
>>>> published.
>>>>
>>>>
>>>> RFC6151?
>>>>
>>>>
>>> I thought that there was something like this. Then quote this
>>>
>>>  MD5 is no longer acceptable where collision resistance is required
>>>  such as digital signatures.  It is not urgent to stop using MD5 in
>>>  other ways, such as HMAC-MD5; however, since MD5 must not be used for
>>>  digital signatures, new protocol designs should not employ HMAC-MD5.
>>>
>>>
>>> and point out how the new I-D disagrees with it.
>>>
>>> That's not being the Crypto police. After all, the IESG approved this RFC
>>> and new use of MD5 should get pushback when an I-D gets to the IESG.
>>> Pointing this out earlier is just saving people's time, and ADs generally
>>> appreciate having their time saved.
>>>
>>
>> Sure, I'm all for it if its not perceived as adding bureaucracy.
>> Don't forget we already have up to 6 reviews etc. on stuff at
>> last-call time.
>>
>> If someone has a way to generate a report identifying relevant
>> -00 and -01 drafts maybe, and someone else is willing to ping
>> authors and explain when they then say "so what" that might
>> be good.
>>
>> I'd say a concrete proposal for what and how to do it, sent to
>> this list (and then probably saag) for sanity checking would
>> be good. So, who's stepping up to figure out details for such
>> a proposal?
>>
>
> I have a set of scripts for producing the list of relevant drafts
> (containing more AWK programming than I would prefer to admit to ;-)  It
> would probably be good to provide more detailed information about the 00
> I-Ds, such as the crypto algorithm(s) that they reference.  In the case of
> MD5, it would be good to know which I-Ds mention MD5 but don't mention
> RFC6151.  I am happy to contribute this as an "official" RG contribution if
> people feel that is important (I'm not sure why it would be, but if it makes
> process easier I can generate a doc or a webpage with the IETF Trust
> copyright notice).
>
> There are about 120 00-version drafts that reference crypto currently.
>  Most of those are doing the right thing, and won't require much if any work
> from crypto-reviewers.   This suggests that the "steady state" workload of
> having CFRG review the uses of crypto in new I-Ds will be manageable, if we
> can get a couple of volunteers.  There are also 170 current I-Ds that
> mention MD5, which suggests that the short-term workload will be higher than
> the steady state workload.  If anyone is interested, please send a note
> either to the list, or to Stephen, Sean, and me.
>
> I think the best way to operate would be find some volunteers to go through
> the I-Ds that mention MD5, and send out a notification to authors where
> needed.  If there are cases in which the actual security properties are not
> clear, those should be brought back to the RG for discussion.  If this seems
> fruitful, we can apply the process to -00 I-Ds going forward.
>
>
If you are going to do that, what about DES and rfc4772 ? If you're going to
be looking...

Marshall




> Looking ahead a bit, it seems like it would be valuable for the RG to
> produce a document describing the crypto algorithms that are in use and
> providing guidance.  I think it would be healthy to have a discussion in
> CFRG on the guidance, and this document could be something that we point to.
>
> David
>
>
>
>> S.
>>
>>
>>
>>> Regards
>>> Marshall
>>>
>>>
>>>  S
>>>>
>>>>
>>>> Regards
>>>> Marshall
>>>>
>>>>
>>>>
>>>>
>>>>  S
>>>>>
>>>>> On 17 Jun 2011, at 19:40, David McGrew < <mcgrew@cisco.com>
>>>>> mcgrew@cisco.com> wrote:
>>>>>
>>>>>
>>>>>> On Jun 17, 2011, at 11:29 AM, David McGrew wrote:
>>>>>>
>>>>>>  Hi Joachim,
>>>>>>>
>>>>>>> +1 on the idea of making sure that current I-Ds that mention MD5 are
>>>>>>>
>>>>>> aware   Probably this could be done by crafting a short paragraph
>>>>> saying
>>>>> something like "We noticed that your RFC references MD5;
>>>>>
>>>>>>
>>>>>> aargh, I meant "your I-D references MD5".
>>>>>>
>>>>>> David
>>>>>> ______________________________**_________________
>>>>>> Cfrg mailing list
>>>>>> <Cfrg@irtf.org>Cfrg@irtf.org
>>>>>> <http://www.irtf.org/mailman/**listinfo/cfrg<http://www.irtf.org/mailman/listinfo/cfrg>
>>>>>> >
>>>>>>
>>>>> http://www.irtf.org/mailman/**listinfo/cfrg<http://www.irtf.org/mailman/listinfo/cfrg>
>>>>> ______________________________**_________________
>>>>> Cfrg mailing list
>>>>> <Cfrg@irtf.org>Cfrg@irtf.org
>>>>> <http://www.irtf.org/mailman/**listinfo/cfrg<http://www.irtf.org/mailman/listinfo/cfrg>
>>>>> >
>>>>> http://www.irtf.org/mailman/**listinfo/cfrg<http://www.irtf.org/mailman/listinfo/cfrg>
>>>>>
>>>>>
>>>>
>>>>
>>>  ______________________________**_________________
>> Cfrg mailing list
>> Cfrg@irtf.org
>> http://www.irtf.org/mailman/**listinfo/cfrg<http://www.irtf.org/mailman/listinfo/cfrg>
>>
>
>

--20cf303f64166b596004a626762a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Mon, Jun 20, 2011 at 11:23 AM, David =
McGrew <span dir=3D"ltr">&lt;<a href=3D"mailto:mcgrew@cisco.com">mcgrew@cis=
co.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Stephen,<div><div></div><div class=3D"h5"><br>
<br>
On Jun 18, 2011, at 1:35 PM, Stephen Farrell wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
On 18/06/11 20:09, Marshall Eubanks wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Sat, Jun 18, 2011 at 2:48 PM, Stephen Farrell<br>
&lt;<a href=3D"mailto:stephen.farrell@cs.tcd.ie" target=3D"_blank">stephen.=
farrell@cs.tcd.ie</a>&gt;<u></u>wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
On 18 Jun 2011, at 19:33, Marshall Eubanks &lt;<a href=3D"mailto:marshall.e=
ubanks@gmail.com" target=3D"_blank">marshall.eubanks@gmail.com</a>&gt;<br>
wrote:<br>
<br>
<br>
<br>
On Fri, Jun 17, 2011 at 3:14 PM, Stephen Farrell &lt;&lt;<a href=3D"mailto:=
stephen.farrell@cs.tcd.ie" target=3D"_blank">stephen.farrell@cs.tcd.ie</a>&=
gt;<br>
<a href=3D"mailto:stephen.farrell@cs.tcd.ie" target=3D"_blank">stephen.farr=
ell@cs.tcd.ie</a>&gt; wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Seems like a reasonable idea but defining the &quot;we&quot; that are<br>
noticing/sending this might be tricky. We don&#39;t want IETF WGs to start<=
br>
complaining about the IRTF CFRG crypto police. People can be touchy about<b=
r>
stuff like that. I&#39;m not sure how best that&#39;d be done to be honest.=
<br>
<br>
<br>
</blockquote>
Write an I-D along the lines of &quot;MD-5 considered dangerous&quot; and g=
et it<br>
published.<br>
<br>
<br>
RFC6151?<br>
<br>
</blockquote>
<br>
I thought that there was something like this. Then quote this<br>
<br>
 =A0MD5 is no longer acceptable where collision resistance is required<br>
 =A0such as digital signatures. =A0It is not urgent to stop using MD5 in<br=
>
 =A0other ways, such as HMAC-MD5; however, since MD5 must not be used for<b=
r>
 =A0digital signatures, new protocol designs should not employ HMAC-MD5.<br=
>
<br>
<br>
and point out how the new I-D disagrees with it.<br>
<br>
That&#39;s not being the Crypto police. After all, the IESG approved this R=
FC<br>
and new use of MD5 should get pushback when an I-D gets to the IESG.<br>
Pointing this out earlier is just saving people&#39;s time, and ADs general=
ly<br>
appreciate having their time saved.<br>
</blockquote>
<br>
Sure, I&#39;m all for it if its not perceived as adding bureaucracy.<br>
Don&#39;t forget we already have up to 6 reviews etc. on stuff at<br>
last-call time.<br>
<br>
If someone has a way to generate a report identifying relevant<br>
-00 and -01 drafts maybe, and someone else is willing to ping<br>
authors and explain when they then say &quot;so what&quot; that might<br>
be good.<br>
<br>
I&#39;d say a concrete proposal for what and how to do it, sent to<br>
this list (and then probably saag) for sanity checking would<br>
be good. So, who&#39;s stepping up to figure out details for such<br>
a proposal?<br>
</blockquote>
<br></div></div>
I have a set of scripts for producing the list of relevant drafts (containi=
ng more AWK programming than I would prefer to admit to ;-) =A0It would pro=
bably be good to provide more detailed information about the 00 I-Ds, such =
as the crypto algorithm(s) that they reference. =A0In the case of MD5, it w=
ould be good to know which I-Ds mention MD5 but don&#39;t mention RFC6151. =
=A0I am happy to contribute this as an &quot;official&quot; RG contribution=
 if people feel that is important (I&#39;m not sure why it would be, but if=
 it makes process easier I can generate a doc or a webpage with the IETF Tr=
ust copyright notice).<br>

<br>
There are about 120 00-version drafts that reference crypto currently. =A0M=
ost of those are doing the right thing, and won&#39;t require much if any w=
ork from crypto-reviewers. =A0 This suggests that the &quot;steady state&qu=
ot; workload of having CFRG review the uses of crypto in new I-Ds will be m=
anageable, if we can get a couple of volunteers. =A0There are also 170 curr=
ent I-Ds that mention MD5, which suggests that the short-term workload will=
 be higher than the steady state workload. =A0If anyone is interested, plea=
se send a note either to the list, or to Stephen, Sean, and me.<br>

<br>
I think the best way to operate would be find some volunteers to go through=
 the I-Ds that mention MD5, and send out a notification to authors where ne=
eded. =A0If there are cases in which the actual security properties are not=
 clear, those should be brought back to the RG for discussion. =A0If this s=
eems fruitful, we can apply the process to -00 I-Ds going forward.<br>

<br></blockquote><div><br></div><div>If you are going to do that, what abou=
t DES and=A0rfc4772 ? If you&#39;re going to be looking...</div><div><br></=
div><div>Marshall</div><div><br></div><div><br></div><div>=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex;">

Looking ahead a bit, it seems like it would be valuable for the RG to produ=
ce a document describing the crypto algorithms that are in use and providin=
g guidance. =A0I think it would be healthy to have a discussion in CFRG on =
the guidance, and this document could be something that we point to.<br>
<font color=3D"#888888">
<br>
David</font><div><div></div><div class=3D"h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
S.<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Regards<br>
Marshall<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
S<br>
<br>
<br>
Regards<br>
Marshall<br>
<br>
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
S<br>
<br>
On 17 Jun 2011, at 19:40, David McGrew &lt; &lt;<a href=3D"mailto:mcgrew@ci=
sco.com" target=3D"_blank">mcgrew@cisco.com</a>&gt;<br>
<a href=3D"mailto:mcgrew@cisco.com" target=3D"_blank">mcgrew@cisco.com</a>&=
gt; wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
On Jun 17, 2011, at 11:29 AM, David McGrew wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi Joachim,<br>
<br>
+1 on the idea of making sure that current I-Ds that mention MD5 are<br>
</blockquote></blockquote>
aware =A0 Probably this could be done by crafting a short paragraph saying<=
br>
something like &quot;We noticed that your RFC references MD5;<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
aargh, I meant &quot;your I-D references MD5&quot;.<br>
<br>
David<br>
______________________________<u></u>_________________<br>
Cfrg mailing list<br>
&lt;<a href=3D"mailto:Cfrg@irtf.org" target=3D"_blank">Cfrg@irtf.org</a>&gt=
;<a href=3D"mailto:Cfrg@irtf.org" target=3D"_blank">Cfrg@irtf.org</a><br>
&lt;<a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" target=3D"_blank"=
>http://www.irtf.org/mailman/<u></u>listinfo/cfrg</a>&gt;<br>
</blockquote>
<a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" target=3D"_blank">htt=
p://www.irtf.org/mailman/<u></u>listinfo/cfrg</a><br>
______________________________<u></u>_________________<br>
Cfrg mailing list<br>
&lt;<a href=3D"mailto:Cfrg@irtf.org" target=3D"_blank">Cfrg@irtf.org</a>&gt=
;<a href=3D"mailto:Cfrg@irtf.org" target=3D"_blank">Cfrg@irtf.org</a><br>
&lt;<a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" target=3D"_blank"=
>http://www.irtf.org/mailman/<u></u>listinfo/cfrg</a>&gt;<br>
<a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" target=3D"_blank">htt=
p://www.irtf.org/mailman/<u></u>listinfo/cfrg</a><br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</blockquote>
______________________________<u></u>_________________<br>
Cfrg mailing list<br>
<a href=3D"mailto:Cfrg@irtf.org" target=3D"_blank">Cfrg@irtf.org</a><br>
<a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" target=3D"_blank">htt=
p://www.irtf.org/mailman/<u></u>listinfo/cfrg</a><br>
</blockquote>
<br>
</div></div></blockquote></div><br>

--20cf303f64166b596004a626762a--

From Joachim@Strombergson.com  Mon Jun 20 09:30:24 2011
Return-Path: <Joachim@Strombergson.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 235201F0C70 for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 09:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.391
X-Spam-Level: 
X-Spam-Status: No, score=-1.391 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k1x3pEf5cL8Q for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 09:30:23 -0700 (PDT)
Received: from susano.oderland.com (susano.oderland.com [91.201.63.143]) by ietfa.amsl.com (Postfix) with ESMTP id BAE6A1F0C73 for <cfrg@irtf.org>; Mon, 20 Jun 2011 09:30:16 -0700 (PDT)
Received: from [2.68.105.14] (helo=snabbis.local) by susano.oderland.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Joachim@Strombergson.com>) id 1QYhMc-0000LT-8u for cfrg@irtf.org; Mon, 20 Jun 2011 18:30:14 +0200
Message-ID: <4DFF7590.2060009@Strombergson.com>
Date: Mon, 20 Jun 2011 18:30:08 +0200
From: =?UTF-8?B?Sm9hY2hpbSBTdHLDtm1iZXJnc29u?= <Joachim@Strombergson.com>
Organization: Kryptologik
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: cfrg@irtf.org
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com>	<4DF6FCAD.1000704@Strombergson.com>	<4DF7E236.3060603@ieca.com>	<CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org>	<4DF8627B.1030702@Strombergson.com>	<74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com>	<DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com>	<6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie>	<BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com>	<D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie>	<BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com>	<4DFD0C1B.6070909@cs.tcd.ie> <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com>
In-Reply-To: <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - susano.oderland.com
X-AntiAbuse: Original Domain - irtf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - Strombergson.com
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Joachim@Strombergson.com
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 16:30:24 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aloha!

On 2011:06:20 17:23, David McGrew wrote:
> There are about 120 00-version drafts that reference crypto currently. 
> Most of those are doing the right thing, and won't require much if any
> work from crypto-reviewers.   This suggests that the "steady state"
> workload of having CFRG review the uses of crypto in new I-Ds will be
> manageable, if we can get a couple of volunteers.  There are also 170
> current I-Ds that mention MD5, which suggests that the short-term
> workload will be higher than the steady state workload.  If anyone is
> interested, please send a note either to the list, or to Stephen, Sean,
> and me.

Since I'm the one who brought this up I guess I should also step up to
the plank. ;-) Count me in.

- -- 
Med vänlig hälsning, Yours

Joachim Strömbergson - Alltid i harmonisk svängning.
========================================================================
Kryptoblog - IT-säkerhet på svenska
http://www.strombergson.com/kryptoblog
========================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3/dZAACgkQZoPr8HT30QG3oQCfSj3ndD8lAU5xMnTBZ1QcxfgJ
G5wAmwYUyKck3zZXhy8DdIWathWLJi+u
=pfjM
-----END PGP SIGNATURE-----

From marshall.eubanks@gmail.com  Mon Jun 20 10:18:36 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0719611E816D for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 10:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.479
X-Spam-Level: 
X-Spam-Status: No, score=-103.479 tagged_above=-999 required=5 tests=[AWL=0.119, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ryfzsT3lwpxM for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 10:18:34 -0700 (PDT)
Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by ietfa.amsl.com (Postfix) with ESMTP id 2F00A11E8133 for <cfrg@irtf.org>; Mon, 20 Jun 2011 10:18:34 -0700 (PDT)
Received: by gyf3 with SMTP id 3so615278gyf.13 for <cfrg@irtf.org>; Mon, 20 Jun 2011 10:18:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Wt3a3+gWknWJlQNMJwxJwkKdeKRrHCt9LXeWRiDdVkg=; b=nPWdC/V2M0vIVpKANTwESk6by2So5VpnS2XHs2y3aLdffM5ZNmUJ8GylrYvEh+9oB/ 1xMDubKS7wp1whp2dn0RWvFeMuus6ZAv9aAJURoYsxowrouHTBh88j+eyi37E46YQXQg fOr26gOR73rdc0I+KDnkXudnB7eYBRxf95FGo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Xd8VCzHqDogMRiZF7B9/TCwTF+q+Kk1L4+9bC9hKlnIv36bpKbjVRlPAzuhXb7lzoD mVt5oVzO8ZHhLK2V/S7Od3/QiRfFlRKnvENuuC+9mq860FMpnb11SA17TBMKGPdGIazW uScZzUruu3BVbYTUnNaKRE6CAjgAEnBnXc+Fc=
MIME-Version: 1.0
Received: by 10.236.80.38 with SMTP id j26mr3653882yhe.123.1308590312901; Mon, 20 Jun 2011 10:18:32 -0700 (PDT)
Received: by 10.146.86.10 with HTTP; Mon, 20 Jun 2011 10:18:32 -0700 (PDT)
In-Reply-To: <4DFF7590.2060009@Strombergson.com>
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie> <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com> <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie> <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com> <4DFD0C1B.6070909@cs.tcd.ie> <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com> <4DFF7590.2060009@Strombergson.com>
Date: Mon, 20 Jun 2011 13:18:32 -0400
Message-ID: <BANLkTin+zWUpQPh41hSX0jKoH=QYFJo2XQ@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Joachim@strombergson.com
Content-Type: multipart/alternative; boundary=20cf300fb2b1c1cd6504a627ecec
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 17:18:36 -0000

--20cf300fb2b1c1cd6504a627ecec
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2011/6/20 Joachim Str=F6mbergson <Joachim@strombergson.com>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Aloha!
>
> On 2011:06:20 17:23, David McGrew wrote:
> > There are about 120 00-version drafts that reference crypto currently.
> > Most of those are doing the right thing, and won't require much if any
> > work from crypto-reviewers.   This suggests that the "steady state"
> > workload of having CFRG review the uses of crypto in new I-Ds will be
> > manageable, if we can get a couple of volunteers.  There are also 170
> > current I-Ds that mention MD5, which suggests that the short-term
> > workload will be higher than the steady state workload.  If anyone is
> > interested, please send a note either to the list, or to Stephen, Sean,
> > and me.
>
> Since I'm the one who brought this up I guess I should also step up to
> the plank. ;-) Count me in.
>

I will volunteer too.

Marshall



>
> - --
> Med v=E4nlig h=E4lsning, Yours
>
> Joachim Str=F6mbergson - Alltid i harmonisk sv=E4ngning.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Kryptoblog - IT-s=E4kerhet p=E5 svenska
> http://www.strombergson.com/kryptoblog
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk3/dZAACgkQZoPr8HT30QG3oQCfSj3ndD8lAU5xMnTBZ1QcxfgJ
> G5wAmwYUyKck3zZXhy8DdIWathWLJi+u
> =3DpfjM
> -----END PGP SIGNATURE-----
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg
>

--20cf300fb2b1c1cd6504a627ecec
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">2011/6/20 Joachim Str=F6mbergson <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:Joachim@strombergson.com">Joachim@stromber=
gson.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Aloha!<br>
<br>
</div><div class=3D"im">On 2011:06:20 17:23, David McGrew wrote:<br>
&gt; There are about 120 00-version drafts that reference crypto currently.=
<br>
&gt; Most of those are doing the right thing, and won&#39;t require much if=
 any<br>
&gt; work from crypto-reviewers. =A0 This suggests that the &quot;steady st=
ate&quot;<br>
&gt; workload of having CFRG review the uses of crypto in new I-Ds will be<=
br>
&gt; manageable, if we can get a couple of volunteers. =A0There are also 17=
0<br>
&gt; current I-Ds that mention MD5, which suggests that the short-term<br>
&gt; workload will be higher than the steady state workload. =A0If anyone i=
s<br>
&gt; interested, please send a note either to the list, or to Stephen, Sean=
,<br>
&gt; and me.<br>
<br>
</div>Since I&#39;m the one who brought this up I guess I should also step =
up to<br>
the plank. ;-) Count me in.<br></blockquote><div><br></div><div>I will volu=
nteer too.</div><div><br></div><div>Marshall</div><div><br></div><div>=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex;">

<br>
- --<br>
<div class=3D"im">Med v=E4nlig h=E4lsning, Yours<br>
<br>
Joachim Str=F6mbergson - Alltid i harmonisk sv=E4ngning.<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
Kryptoblog - IT-s=E4kerhet p=E5 svenska<br>
<a href=3D"http://www.strombergson.com/kryptoblog" target=3D"_blank">http:/=
/www.strombergson.com/kryptoblog</a><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.11 (Darwin)<br>
Comment: Using GnuPG with Mozilla - <a href=3D"http://enigmail.mozdev.org/"=
 target=3D"_blank">http://enigmail.mozdev.org/</a><br>
<br>
</div>iEYEARECAAYFAk3/dZAACgkQZoPr8HT30QG3oQCfSj3ndD8lAU5xMnTBZ1QcxfgJ<br>
G5wAmwYUyKck3zZXhy8DdIWathWLJi+u<br>
=3DpfjM<br>
-----END PGP SIGNATURE-----<br>
<div><div></div><div class=3D"h5">_________________________________________=
______<br>
Cfrg mailing list<br>
<a href=3D"mailto:Cfrg@irtf.org">Cfrg@irtf.org</a><br>
<a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" target=3D"_blank">htt=
p://www.irtf.org/mailman/listinfo/cfrg</a><br>
</div></div></blockquote></div><br>

--20cf300fb2b1c1cd6504a627ecec--

From mcgrew@cisco.com  Mon Jun 20 10:35:27 2011
Return-Path: <mcgrew@cisco.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55A7811E8094 for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 10:35:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zDuC3cka7XXM for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 10:35:26 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id 545C911E8072 for <cfrg@irtf.org>; Mon, 20 Jun 2011 10:35:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mcgrew@cisco.com; l=10118; q=dns/txt; s=iport; t=1308591326; x=1309800926; h=cc:message-id:from:to:in-reply-to:mime-version:subject: date:references; bh=acrQ+aah/LnfX2ca/l9YlkUonjBBSf48/24byLFoEDg=; b=Z7rsR0ym2hiCoHG65wi4QTjoZEkfu1uX92YkvkSDoFsc4aXpSMF58k/p snJ0i1RRmhW7EkIyPUoFvB8zySRq0yf5QPE4Ovd2TRLaHh2yl/pQSI3PK 4WaxPrZlnLCRaV5W/I5TCQDvW4Ax+C6WoQxO0VVVmyza2W0DqLXbG5ssI s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EALaD/02rRDoH/2dsb2JhbABTpmJ3iHOhZJ1/hioEhyCKPoRghEWGfA
X-IronPort-AV: E=Sophos;i="4.65,395,1304294400";  d="scan'208,217";a="717530203"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-6.cisco.com with ESMTP; 20 Jun 2011 17:35:24 +0000
Received: from [10.32.254.213] (stealth-10-32-254-213.cisco.com [10.32.254.213]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5KHZF4s009539; Mon, 20 Jun 2011 17:35:23 GMT
Message-Id: <EC9A176E-7C2A-4782-8522-C1656478CBF3@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
In-Reply-To: <BANLkTim8VCPY9NhNbYkOE2u2HMR_r9s7sg@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-273--428373849
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 20 Jun 2011 10:35:07 -0700
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie> <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com> <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie> <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com> <4DFD0C1B.6070909@cs.tcd.ie> <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com> <BANLkTim8VCPY9NhNbYkOE2u2HMR_r9s7sg@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Cc: Sean Turner <turners@ieca.com>, cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 17:35:27 -0000

--Apple-Mail-273--428373849
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On Jun 20, 2011, at 8:33 AM, Marshall Eubanks wrote:

>
>
> On Mon, Jun 20, 2011 at 11:23 AM, David McGrew <mcgrew@cisco.com>  
> wrote:
> Hi Stephen,
>
>
> On Jun 18, 2011, at 1:35 PM, Stephen Farrell wrote:
>
>
>
> On 18/06/11 20:09, Marshall Eubanks wrote:
> On Sat, Jun 18, 2011 at 2:48 PM, Stephen Farrell
> <stephen.farrell@cs.tcd.ie>wrote:
>
>
>
> On 18 Jun 2011, at 19:33, Marshall Eubanks  
> <marshall.eubanks@gmail.com>
> wrote:
>
>
>
> On Fri, Jun 17, 2011 at 3:14 PM, Stephen Farrell <<stephen.farrell@cs.tcd.ie 
> >
> stephen.farrell@cs.tcd.ie> wrote:
>
> Seems like a reasonable idea but defining the "we" that are
> noticing/sending this might be tricky. We don't want IETF WGs to start
> complaining about the IRTF CFRG crypto police. People can be touchy  
> about
> stuff like that. I'm not sure how best that'd be done to be honest.
>
>
> Write an I-D along the lines of "MD-5 considered dangerous" and get it
> published.
>
>
> RFC6151?
>
>
> I thought that there was something like this. Then quote this
>
>  MD5 is no longer acceptable where collision resistance is required
>  such as digital signatures.  It is not urgent to stop using MD5 in
>  other ways, such as HMAC-MD5; however, since MD5 must not be used for
>  digital signatures, new protocol designs should not employ HMAC-MD5.
>
>
> and point out how the new I-D disagrees with it.
>
> That's not being the Crypto police. After all, the IESG approved  
> this RFC
> and new use of MD5 should get pushback when an I-D gets to the IESG.
> Pointing this out earlier is just saving people's time, and ADs  
> generally
> appreciate having their time saved.
>
> Sure, I'm all for it if its not perceived as adding bureaucracy.
> Don't forget we already have up to 6 reviews etc. on stuff at
> last-call time.
>
> If someone has a way to generate a report identifying relevant
> -00 and -01 drafts maybe, and someone else is willing to ping
> authors and explain when they then say "so what" that might
> be good.
>
> I'd say a concrete proposal for what and how to do it, sent to
> this list (and then probably saag) for sanity checking would
> be good. So, who's stepping up to figure out details for such
> a proposal?
>
> I have a set of scripts for producing the list of relevant drafts  
> (containing more AWK programming than I would prefer to admit  
> to ;-)  It would probably be good to provide more detailed  
> information about the 00 I-Ds, such as the crypto algorithm(s) that  
> they reference.  In the case of MD5, it would be good to know which  
> I-Ds mention MD5 but don't mention RFC6151.  I am happy to  
> contribute this as an "official" RG contribution if people feel that  
> is important (I'm not sure why it would be, but if it makes process  
> easier I can generate a doc or a webpage with the IETF Trust  
> copyright notice).
>
> There are about 120 00-version drafts that reference crypto  
> currently.  Most of those are doing the right thing, and won't  
> require much if any work from crypto-reviewers.   This suggests that  
> the "steady state" workload of having CFRG review the uses of crypto  
> in new I-Ds will be manageable, if we can get a couple of  
> volunteers.  There are also 170 current I-Ds that mention MD5, which  
> suggests that the short-term workload will be higher than the steady  
> state workload.  If anyone is interested, please send a note either  
> to the list, or to Stephen, Sean, and me.
>
> I think the best way to operate would be find some volunteers to go  
> through the I-Ds that mention MD5, and send out a notification to  
> authors where needed.  If there are cases in which the actual  
> security properties are not clear, those should be brought back to  
> the RG for discussion.  If this seems fruitful, we can apply the  
> process to -00 I-Ds going forward.
>
>
> If you are going to do that, what about DES and rfc4772 ? If you're  
> going to be looking...
>
> Marshall

good point.

David


--Apple-Mail-273--428373849
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Jun 20, 2011, =
at 8:33 AM, Marshall Eubanks wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><br><br><div=
 class=3D"gmail_quote">On Mon, Jun 20, 2011 at 11:23 AM, David McGrew =
<span dir=3D"ltr">&lt;<a =
href=3D"mailto:mcgrew@cisco.com">mcgrew@cisco.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;"> Hi =
Stephen,<div><div></div><div class=3D"h5"><br> <br> On Jun 18, 2011, at =
1:35 PM, Stephen Farrell wrote:<br> <br> <blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"> <br> <br> On 18/06/11 20:09, Marshall Eubanks =
wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"> On Sat, Jun 18, 2011 =
at 2:48 PM, Stephen Farrell<br> &lt;<a =
href=3D"mailto:stephen.farrell@cs.tcd.ie" =
target=3D"_blank">stephen.farrell@cs.tcd.ie</a>&gt;<u></u>wrote:<br> =
<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> <br> On 18 Jun =
2011, at 19:33, Marshall Eubanks &lt;<a =
href=3D"mailto:marshall.eubanks@gmail.com" =
target=3D"_blank">marshall.eubanks@gmail.com</a>&gt;<br> wrote:<br> <br> =
<br> <br> On Fri, Jun 17, 2011 at 3:14 PM, Stephen Farrell &lt;&lt;<a =
href=3D"mailto:stephen.farrell@cs.tcd.ie" =
target=3D"_blank">stephen.farrell@cs.tcd.ie</a>&gt;<br> <a =
href=3D"mailto:stephen.farrell@cs.tcd.ie" =
target=3D"_blank">stephen.farrell@cs.tcd.ie</a>&gt; wrote:<br> <br> =
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"> Seems like a =
reasonable idea but defining the "we" that are<br> noticing/sending this =
might be tricky. We don't want IETF WGs to start<br> complaining about =
the IRTF CFRG crypto police. People can be touchy about<br> stuff like =
that. I'm not sure how best that'd be done to be honest.<br> <br> <br> =
</blockquote> Write an I-D along the lines of "MD-5 considered =
dangerous" and get it<br> published.<br> <br> <br> RFC6151?<br> <br> =
</blockquote> <br> I thought that there was something like this. Then =
quote this<br> <br> &nbsp;MD5 is no longer acceptable where collision =
resistance is required<br> &nbsp;such as digital signatures. &nbsp;It is =
not urgent to stop using MD5 in<br> &nbsp;other ways, such as HMAC-MD5; =
however, since MD5 must not be used for<br> &nbsp;digital signatures, =
new protocol designs should not employ HMAC-MD5.<br> <br> <br> and point =
out how the new I-D disagrees with it.<br> <br> That's not being the =
Crypto police. After all, the IESG approved this RFC<br> and new use of =
MD5 should get pushback when an I-D gets to the IESG.<br> Pointing this =
out earlier is just saving people's time, and ADs generally<br> =
appreciate having their time saved.<br> </blockquote> <br> Sure, I'm all =
for it if its not perceived as adding bureaucracy.<br> Don't forget we =
already have up to 6 reviews etc. on stuff at<br> last-call time.<br> =
<br> If someone has a way to generate a report identifying relevant<br> =
-00 and -01 drafts maybe, and someone else is willing to ping<br> =
authors and explain when they then say "so what" that might<br> be =
good.<br> <br> I'd say a concrete proposal for what and how to do it, =
sent to<br> this list (and then probably saag) for sanity checking =
would<br> be good. So, who's stepping up to figure out details for =
such<br> a proposal?<br> </blockquote> <br></div></div> I have a set of =
scripts for producing the list of relevant drafts (containing more AWK =
programming than I would prefer to admit to ;-) &nbsp;It would probably =
be good to provide more detailed information about the 00 I-Ds, such as =
the crypto algorithm(s) that they reference. &nbsp;In the case of MD5, =
it would be good to know which I-Ds mention MD5 but don't mention =
RFC6151. &nbsp;I am happy to contribute this as an "official" RG =
contribution if people feel that is important (I'm not sure why it would =
be, but if it makes process easier I can generate a doc or a webpage =
with the IETF Trust copyright notice).<br> <br> There are about 120 =
00-version drafts that reference crypto currently. &nbsp;Most of those =
are doing the right thing, and won't require much if any work from =
crypto-reviewers. &nbsp; This suggests that the "steady state" workload =
of having CFRG review the uses of crypto in new I-Ds will be manageable, =
if we can get a couple of volunteers. &nbsp;There are also 170 current =
I-Ds that mention MD5, which suggests that the short-term workload will =
be higher than the steady state workload. &nbsp;If anyone is interested, =
please send a note either to the list, or to Stephen, Sean, and me.<br> =
<br> I think the best way to operate would be find some volunteers to go =
through the I-Ds that mention MD5, and send out a notification to =
authors where needed. &nbsp;If there are cases in which the actual =
security properties are not clear, those should be brought back to the =
RG for discussion. &nbsp;If this seems fruitful, we can apply the =
process to -00 I-Ds going forward.<br> =
<br></blockquote><div><br></div><div>If you are going to do that, what =
about DES and&nbsp;rfc4772 ? If you're going to be =
looking...</div><div><br></div><div>Marshall</div></div></blockquote><div>=
<br></div><div>good point. =
&nbsp;</div><div><br></div><div>David</div><div><br></div></div></body></h=
tml>=

--Apple-Mail-273--428373849--

From marshall.eubanks@gmail.com  Mon Jun 20 10:38:43 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B98DD11E8178 for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 10:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.515
X-Spam-Level: 
X-Spam-Status: No, score=-103.515 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RIs2WERDwtLB for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 10:38:42 -0700 (PDT)
Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by ietfa.amsl.com (Postfix) with ESMTP id B2E6A228012 for <cfrg@irtf.org>; Mon, 20 Jun 2011 10:38:42 -0700 (PDT)
Received: by yxl31 with SMTP id 31so3416321yxl.13 for <cfrg@irtf.org>; Mon, 20 Jun 2011 10:38:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=9rXjlWkysuvHWK0V2kConFfIKdLw8fTCh7uq/Hzv6ag=; b=LlQEHNwn++IYgxwvaHHgdWJUE1z4KDdGIMCptW5qkpfLYEgfOS9dicqHnrCwlea8KH wrcTxZuRjW9uhlhyanSTIYbe9GqC623bGjHD/pfsDwYXYX8R3I9XZaAUDr5WNaXZksO8 5kufSYlZYcYgdMxduyhLWrPJnz1qE6wMIUPaY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=fnPcQDhUR3eMsGK2HCTGMJu6AnfSwXKRkREDTVWQIs+4lSqbBvOLNI7lg5TmNpGdH7 Kn93qKkgj+dbH/CwIEuI6mAWtPO7ZWbuLlD0PGMpTAKiKLwkWcKqa8iM0Z53P/MSuFCB Wg8eu+6kdBWgXis5zvxEEpk0PqfcTcAvwoExc=
MIME-Version: 1.0
Received: by 10.236.157.36 with SMTP id n24mr3809552yhk.190.1308591522029; Mon, 20 Jun 2011 10:38:42 -0700 (PDT)
Received: by 10.146.86.10 with HTTP; Mon, 20 Jun 2011 10:38:41 -0700 (PDT)
In-Reply-To: <EC9A176E-7C2A-4782-8522-C1656478CBF3@cisco.com>
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie> <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com> <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie> <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com> <4DFD0C1B.6070909@cs.tcd.ie> <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com> <BANLkTim8VCPY9NhNbYkOE2u2HMR_r9s7sg@mail.gmail.com> <EC9A176E-7C2A-4782-8522-C1656478CBF3@cisco.com>
Date: Mon, 20 Jun 2011 13:38:41 -0400
Message-ID: <BANLkTi=fW+wMxkbO_74U8WNiDkrBfpwTvw@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: David McGrew <mcgrew@cisco.com>
Content-Type: multipart/alternative; boundary=20cf303f6416d39f4704a62834f9
Cc: Sean Turner <turners@ieca.com>, cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 17:38:43 -0000

--20cf303f6416d39f4704a62834f9
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jun 20, 2011 at 1:35 PM, David McGrew <mcgrew@cisco.com> wrote:

>
> On Jun 20, 2011, at 8:33 AM, Marshall Eubanks wrote:
>
>
>
> On Mon, Jun 20, 2011 at 11:23 AM, David McGrew <mcgrew@cisco.com> wrote:
>
>> Hi Stephen,
>>
>>
>> On Jun 18, 2011, at 1:35 PM, Stephen Farrell wrote:
>>
>>
>>>
>>> On 18/06/11 20:09, Marshall Eubanks wrote:
>>>
>>>> On Sat, Jun 18, 2011 at 2:48 PM, Stephen Farrell
>>>> <stephen.farrell@cs.tcd.ie>**wrote:
>>>>
>>>>
>>>>>
>>>>> On 18 Jun 2011, at 19:33, Marshall Eubanks <marshall.eubanks@gmail.com
>>>>> >
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Jun 17, 2011 at 3:14 PM, Stephen Farrell <<
>>>>> stephen.farrell@cs.tcd.ie>
>>>>> stephen.farrell@cs.tcd.ie> wrote:
>>>>>
>>>>>  Seems like a reasonable idea but defining the "we" that are
>>>>>> noticing/sending this might be tricky. We don't want IETF WGs to start
>>>>>> complaining about the IRTF CFRG crypto police. People can be touchy
>>>>>> about
>>>>>> stuff like that. I'm not sure how best that'd be done to be honest.
>>>>>>
>>>>>>
>>>>>>  Write an I-D along the lines of "MD-5 considered dangerous" and get
>>>>> it
>>>>> published.
>>>>>
>>>>>
>>>>> RFC6151?
>>>>>
>>>>>
>>>> I thought that there was something like this. Then quote this
>>>>
>>>>  MD5 is no longer acceptable where collision resistance is required
>>>>  such as digital signatures.  It is not urgent to stop using MD5 in
>>>>  other ways, such as HMAC-MD5; however, since MD5 must not be used for
>>>>  digital signatures, new protocol designs should not employ HMAC-MD5.
>>>>
>>>>
>>>> and point out how the new I-D disagrees with it.
>>>>
>>>> That's not being the Crypto police. After all, the IESG approved this
>>>> RFC
>>>> and new use of MD5 should get pushback when an I-D gets to the IESG.
>>>> Pointing this out earlier is just saving people's time, and ADs
>>>> generally
>>>> appreciate having their time saved.
>>>>
>>>
>>> Sure, I'm all for it if its not perceived as adding bureaucracy.
>>> Don't forget we already have up to 6 reviews etc. on stuff at
>>> last-call time.
>>>
>>> If someone has a way to generate a report identifying relevant
>>> -00 and -01 drafts maybe, and someone else is willing to ping
>>> authors and explain when they then say "so what" that might
>>> be good.
>>>
>>> I'd say a concrete proposal for what and how to do it, sent to
>>> this list (and then probably saag) for sanity checking would
>>> be good. So, who's stepping up to figure out details for such
>>> a proposal?
>>>
>>
>> I have a set of scripts for producing the list of relevant drafts
>> (containing more AWK programming than I would prefer to admit to ;-)  It
>> would probably be good to provide more detailed information about the 00
>> I-Ds, such as the crypto algorithm(s) that they reference.  In the case of
>> MD5, it would be good to know which I-Ds mention MD5 but don't mention
>> RFC6151.  I am happy to contribute this as an "official" RG contribution if
>> people feel that is important (I'm not sure why it would be, but if it makes
>> process easier I can generate a doc or a webpage with the IETF Trust
>> copyright notice).
>>
>> There are about 120 00-version drafts that reference crypto currently.
>>  Most of those are doing the right thing, and won't require much if any work
>> from crypto-reviewers.   This suggests that the "steady state" workload of
>> having CFRG review the uses of crypto in new I-Ds will be manageable, if we
>> can get a couple of volunteers.  There are also 170 current I-Ds that
>> mention MD5, which suggests that the short-term workload will be higher than
>> the steady state workload.  If anyone is interested, please send a note
>> either to the list, or to Stephen, Sean, and me.
>>
>> I think the best way to operate would be find some volunteers to go
>> through the I-Ds that mention MD5, and send out a notification to authors
>> where needed.  If there are cases in which the actual security properties
>> are not clear, those should be brought back to the RG for discussion.  If
>> this seems fruitful, we can apply the process to -00 I-Ds going forward.
>>
>>
> If you are going to do that, what about DES and rfc4772 ? If you're going
> to be looking...
>
> Marshall
>
>
> good point.
>
> David
>

On this topic, has triple DES been deprecated yet ? I wouldn't feel
comfortable recommending it for something new, but I don't think it's
been shown the door yet.

Regards
Marshall

--20cf303f6416d39f4704a62834f9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Mon, Jun 20, 2011 at 1:35 PM, David M=
cGrew <span dir=3D"ltr">&lt;<a href=3D"mailto:mcgrew@cisco.com">mcgrew@cisc=
o.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word"><br><div><div><div></div><div class=3D"=
h5"><div>On Jun 20, 2011, at 8:33 AM, Marshall Eubanks wrote:</div><br><blo=
ckquote type=3D"cite"><br><br><div class=3D"gmail_quote">On Mon, Jun 20, 20=
11 at 11:23 AM, David McGrew <span dir=3D"ltr">&lt;<a href=3D"mailto:mcgrew=
@cisco.com" target=3D"_blank">mcgrew@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"> Hi Stephen,<div><div></div><div><br> <br> O=
n Jun 18, 2011, at 1:35 PM, Stephen Farrell wrote:<br> <br> <blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
 <br> <br> On 18/06/11 20:09, Marshall Eubanks wrote:<br> <blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"> On Sat, Jun 18, 2011 at 2:48 PM, Stephen Farrell<br> &lt;<a =
href=3D"mailto:stephen.farrell@cs.tcd.ie" target=3D"_blank">stephen.farrell=
@cs.tcd.ie</a>&gt;<u></u>wrote:<br>
 <br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"> <br> <br> On 18 Jun 2011, at 19:33, M=
arshall Eubanks &lt;<a href=3D"mailto:marshall.eubanks@gmail.com" target=3D=
"_blank">marshall.eubanks@gmail.com</a>&gt;<br>
 wrote:<br> <br> <br> <br> On Fri, Jun 17, 2011 at 3:14 PM, Stephen Farrell=
 &lt;&lt;<a href=3D"mailto:stephen.farrell@cs.tcd.ie" target=3D"_blank">ste=
phen.farrell@cs.tcd.ie</a>&gt;<br> <a href=3D"mailto:stephen.farrell@cs.tcd=
.ie" target=3D"_blank">stephen.farrell@cs.tcd.ie</a>&gt; wrote:<br>
 <br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"> Seems like a reasonable idea but defi=
ning the &quot;we&quot; that are<br> noticing/sending this might be tricky.=
 We don&#39;t want IETF WGs to start<br>
 complaining about the IRTF CFRG crypto police. People can be touchy about<=
br> stuff like that. I&#39;m not sure how best that&#39;d be done to be hon=
est.<br> <br> <br> </blockquote> Write an I-D along the lines of &quot;MD-5=
 considered dangerous&quot; and get it<br>
 published.<br> <br> <br> RFC6151?<br> <br> </blockquote> <br> I thought th=
at there was something like this. Then quote this<br> <br> =A0MD5 is no lon=
ger acceptable where collision resistance is required<br> =A0such as digita=
l signatures. =A0It is not urgent to stop using MD5 in<br>
 =A0other ways, such as HMAC-MD5; however, since MD5 must not be used for<b=
r> =A0digital signatures, new protocol designs should not employ HMAC-MD5.<=
br> <br> <br> and point out how the new I-D disagrees with it.<br> <br> Tha=
t&#39;s not being the Crypto police. After all, the IESG approved this RFC<=
br>
 and new use of MD5 should get pushback when an I-D gets to the IESG.<br> P=
ointing this out earlier is just saving people&#39;s time, and ADs generall=
y<br> appreciate having their time saved.<br> </blockquote> <br> Sure, I&#3=
9;m all for it if its not perceived as adding bureaucracy.<br>
 Don&#39;t forget we already have up to 6 reviews etc. on stuff at<br> last=
-call time.<br> <br> If someone has a way to generate a report identifying =
relevant<br> -00 and -01 drafts maybe, and someone else is willing to ping<=
br>
 authors and explain when they then say &quot;so what&quot; that might<br> =
be good.<br> <br> I&#39;d say a concrete proposal for what and how to do it=
, sent to<br> this list (and then probably saag) for sanity checking would<=
br>
 be good. So, who&#39;s stepping up to figure out details for such<br> a pr=
oposal?<br> </blockquote> <br></div></div> I have a set of scripts for prod=
ucing the list of relevant drafts (containing more AWK programming than I w=
ould prefer to admit to ;-) =A0It would probably be good to provide more de=
tailed information about the 00 I-Ds, such as the crypto algorithm(s) that =
they reference. =A0In the case of MD5, it would be good to know which I-Ds =
mention MD5 but don&#39;t mention RFC6151. =A0I am happy to contribute this=
 as an &quot;official&quot; RG contribution if people feel that is importan=
t (I&#39;m not sure why it would be, but if it makes process easier I can g=
enerate a doc or a webpage with the IETF Trust copyright notice).<br>
 <br> There are about 120 00-version drafts that reference crypto currently=
. =A0Most of those are doing the right thing, and won&#39;t require much if=
 any work from crypto-reviewers. =A0 This suggests that the &quot;steady st=
ate&quot; workload of having CFRG review the uses of crypto in new I-Ds wil=
l be manageable, if we can get a couple of volunteers. =A0There are also 17=
0 current I-Ds that mention MD5, which suggests that the short-term workloa=
d will be higher than the steady state workload. =A0If anyone is interested=
, please send a note either to the list, or to Stephen, Sean, and me.<br>
 <br> I think the best way to operate would be find some volunteers to go t=
hrough the I-Ds that mention MD5, and send out a notification to authors wh=
ere needed. =A0If there are cases in which the actual security properties a=
re not clear, those should be brought back to the RG for discussion. =A0If =
this seems fruitful, we can apply the process to -00 I-Ds going forward.<br=
>
 <br></blockquote><div><br></div><div>If you are going to do that, what abo=
ut DES and=A0rfc4772 ? If you&#39;re going to be looking...</div><div><br><=
/div><div>Marshall</div></div></blockquote><div><br></div></div></div><div>
good point. =A0</div><div><br></div><font color=3D"#888888"><div>David</div=
></font></div></div></blockquote><div><br></div><div>On this topic, has tri=
ple DES been deprecated yet ? I wouldn&#39;t feel comfortable recommending =
it for something new, but I don&#39;t think it&#39;s been=A0shown the door =
yet.</div>
<div><br></div><div>Regards</div><div>Marshall</div><div>=A0</div></div><br=
>

--20cf303f6416d39f4704a62834f9--

From jon@callas.org  Mon Jun 20 10:51:51 2011
Return-Path: <jon@callas.org>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3750E11E808A for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 10:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3xG2UiUn-yTx for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 10:51:50 -0700 (PDT)
Received: from merrymeet.com (unknown [173.164.244.100]) by ietfa.amsl.com (Postfix) with ESMTP id 4893411E8094 for <cfrg@irtf.org>; Mon, 20 Jun 2011 10:51:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by merrymeet.com (Postfix) with ESMTP id 1C48A2E02C for <cfrg@irtf.org>; Mon, 20 Jun 2011 10:51:54 -0700 (PDT)
Received: from merrymeet.com ([127.0.0.1]) by localhost (host.domain.tld [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 34920-01 for <cfrg@irtf.org>; Mon, 20 Jun 2011 10:51:46 -0700 (PDT)
Received: from keys.merrymeet.com (keys.merrymeet.com [173.164.244.97]) (Authenticated sender: jon) by merrymeet.com (Postfix) with ESMTPA id 7FEB02E0C1 for <cfrg@irtf.org>; Mon, 20 Jun 2011 10:51:46 -0700 (PDT)
Received: from ba0301a-dhcp04.apple.com ([17.193.14.132]) by keys.merrymeet.com (PGP Universal service); Mon, 20 Jun 2011 10:51:41 -0700
X-PGP-Universal: processed; by keys.merrymeet.com on Mon, 20 Jun 2011 10:51:41 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
From: Jon Callas <jon@callas.org>
In-Reply-To: <BANLkTi=fW+wMxkbO_74U8WNiDkrBfpwTvw@mail.gmail.com>
Date: Mon, 20 Jun 2011 10:51:40 -0700
Message-Id: <5EE73036-232D-4D10-8C42-3CB7E1155EA0@callas.org>
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie> <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com> <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie> <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com> <4DFD0C1B.6070909@cs.tcd.ie> <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com> <BANLkTim8VCPY9NhNbYkOE2u2HMR_r9s7sg@mail.gmail.com> <EC9A176E-7C2A-4782-8522-C1656478CBF3@cisco.com> <BANLkTi=fW+wMxkbO_74U8WNiDkrBfpwTvw@mail.gmail.com>
To: cfrg@irtf.org
X-Mailer: Apple Mail (2.1084)
X-PGP-Encoding-Format: Partitioned
X-PGP-Encoding-Version: 2.0.2
X-Content-PGP-Universal-Saved-Content-Transfer-Encoding: quoted-printable
X-Content-PGP-Universal-Saved-Content-Type: text/plain; charset=us-ascii
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Virus-Scanned: Maia Mailguard
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 17:51:51 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Jun 20, 2011, at 10:38 AM, Marshall Eubanks wrote:

> On this topic, has triple DES been deprecated yet ? I wouldn't feel comfo=
rtable recommending it for something new, but I don't think it's been shown=
 the door yet.

No. 112-bit crypto of all sorts (another example is 2K RSA keys) is still a=
cceptable.

I agree with you, I wouldn't use 3DES for anything new. But the major reaso=
n to avoid it isn't key size, it's block size. You should avoid anything wi=
th a smaller block than 128 bits.

	Jon



-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 2.10.0 (Build 554)
Charset: us-ascii

wj8DBQFN/4itsTedWZOD3gYRAtDaAKD+P4sz4cpvr7/s/JeWv6rI31+8uACgzrsX
H8E9kdTTiJXQPyMYxhZw3I0=3D
=3D5wHj
-----END PGP SIGNATURE-----

From mcgrew@cisco.com  Mon Jun 20 11:11:25 2011
Return-Path: <mcgrew@cisco.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD7B411E8094 for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 11:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0XEWgG4XWV-u for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 11:11:24 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id C6BBA11E808E for <cfrg@irtf.org>; Mon, 20 Jun 2011 11:11:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mcgrew@cisco.com; l=1523; q=dns/txt; s=iport; t=1308593484; x=1309803084; h=cc:message-id:from:to:in-reply-to: content-transfer-encoding:mime-version:subject:date: references; bh=uGdRJiebhIB/T0H5FqoHGQMIou22w0LnZ9t/kVC1vjw=; b=BMO9SMoOsIi2uPLJyMjAZ1z2swfKeaw3zxA8qbaVOgbib5CRg7K/0yRq rkE4OtuwiUF9QJBxIFHeSjws8BOctRboTO5lf8J/fs1eZuv5Hm1fbORJm XwRL94rI7EEc+Y7eOsUPjjv/BJ4KiYu/5H3EtcSI4TMbsrEAIckkmNiX+ k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EABON/02rRDoJ/2dsb2JhbABTpmJ3iHOhap4IhioEhyCKPpAh
X-IronPort-AV: E=Sophos;i="4.65,395,1304294400"; d="scan'208";a="717569788"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-6.cisco.com with ESMTP; 20 Jun 2011 18:11:09 +0000
Received: from stealth-10-32-254-213.cisco.com (stealth-10-32-254-213.cisco.com [10.32.254.213]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p5KIB8dc004313; Mon, 20 Jun 2011 18:11:09 GMT
Message-Id: <52391DF8-DCD6-4962-92B3-700684F41DB2@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: Jon Callas <jon@callas.org>, Marshall Eubanks <marshall.eubanks@gmail.com>
In-Reply-To: <5EE73036-232D-4D10-8C42-3CB7E1155EA0@callas.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 20 Jun 2011 11:11:07 -0700
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie> <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com> <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie> <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com> <4DFD0C1B.6070909@cs.tcd.ie> <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com> <BANLkTim8VCPY9NhNbYkOE2u2HMR_r9s7sg@mail.gmail.com> <EC9A176E-7C2A-4782-8522-C1656478CBF3@cisco.com> <BANLkTi=fW+wMxkbO_74U8WNiDkrBfpwTvw@mail.gmail.com> <5EE73036-232D-4D10-8C42-3CB7E1155EA0@callas.org>
X-Mailer: Apple Mail (2.936)
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 18:11:25 -0000

Hi Jon,

On Jun 20, 2011, at 10:51 AM, Jon Callas wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Jun 20, 2011, at 10:38 AM, Marshall Eubanks wrote:
>
>> On this topic, has triple DES been deprecated yet ? I wouldn't feel  
>> comfortable recommending it for something new, but I don't think  
>> it's been shown the door yet.
>
> No. 112-bit crypto of all sorts (another example is 2K RSA keys) is  
> still acceptable.
>
> I agree with you, I wouldn't use 3DES for anything new. But the  
> major reason to avoid it isn't key size, it's block size. You should  
> avoid anything with a smaller block than 128 bits.

+1.   This is a highly relevant security factor, especially for higher  
data rates.  This comment applies also to IDEA, CAST-128, GOST  
28147-89, Blowfish, and most uses of RC5.

To quantify this, I believe that a 128-bit block cipher can process  
2^32 times as much data as a 64-bit block cipher, while having the  
same level of security in the indistinguishability model, assuming  
that neither cipher can be distinguished from a random permutation.

David

>
> 	Jon
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP Universal 2.10.0 (Build 554)
> Charset: us-ascii
>
> wj8DBQFN/4itsTedWZOD3gYRAtDaAKD+P4sz4cpvr7/s/JeWv6rI31+8uACgzrsX
> H8E9kdTTiJXQPyMYxhZw3I0=
> =5wHj
> -----END PGP SIGNATURE-----
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg


From pornin@bolet.org  Mon Jun 20 11:19:11 2011
Return-Path: <pornin@bolet.org>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 300F611E81BB for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 11:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l8FsIT89Fn6K for <cfrg@ietfa.amsl.com>; Mon, 20 Jun 2011 11:19:10 -0700 (PDT)
Received: from arges.bolet.org (arges.bolet.org [88.191.65.205]) by ietfa.amsl.com (Postfix) with ESMTP id 768CD11E8094 for <cfrg@irtf.org>; Mon, 20 Jun 2011 11:19:10 -0700 (PDT)
Received: from [10.0.1.101] (modemcable107.127-131-66.mc.videotron.ca [66.131.127.107]) by arges.bolet.org (Postfix) with ESMTPSA id 24CE668C0A6; Mon, 20 Jun 2011 20:19:28 +0200 (CEST)
From: Thomas Pornin <pornin@bolet.org>
To: David McGrew <mcgrew@cisco.com>
In-Reply-To: <52391DF8-DCD6-4962-92B3-700684F41DB2@cisco.com>
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie> <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com> <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie> <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com> <4DFD0C1B.6070909@cs.tcd.ie> <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com> <BANLkTim8VCPY9NhNbYkOE2u2HMR_r9s7sg@mail.gmail.com> <EC9A176E-7C2A-4782-8522-C1656478CBF3@cisco.com> <BANLkTi=fW+wMxkbO_74U8WNiDkrBfpwTvw@mail.gmail.com> <5EE73036-232D-4D10-8C42-3CB7E1155EA0@callas.org> <52391DF8-DCD6-4962-92B3-700684F41DB2@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 20 Jun 2011 14:19:01 -0400
Message-ID: <1308593941.2874.2.camel@nostromo>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
Content-Transfer-Encoding: 7bit
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 18:19:11 -0000

On Mon, 2011-06-20 at 11:11 -0700, David McGrew wrote:
> To quantify this, I believe that a 128-bit block cipher can process  
> 2^32 times as much data as a 64-bit block cipher, while having the  
> same level of security in the indistinguishability model, assuming  
> that neither cipher can be distinguished from a random permutation.

Actually is 2^32 times as many blocks, but since 128-bit blocks are
twice larger than 64-bit blocks, this translates to 2^33 times as much
data.

	--Thomas Pornin



From mcgrew@cisco.com  Tue Jun 21 13:15:05 2011
Return-Path: <mcgrew@cisco.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34EA211E809B for <cfrg@ietfa.amsl.com>; Tue, 21 Jun 2011 13:15:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0iW6lC6BSfjD for <cfrg@ietfa.amsl.com>; Tue, 21 Jun 2011 13:15:04 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by ietfa.amsl.com (Postfix) with ESMTP id C71EE11E807A for <cfrg@irtf.org>; Tue, 21 Jun 2011 13:15:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mcgrew@cisco.com; l=6538; q=dns/txt; s=iport; t=1308687303; x=1309896903; h=cc:message-id:from:to:in-reply-to:mime-version:subject: date:references; bh=A5VBpbsy78zMBva4Jt56vEI9mOX1L1DermHN8lEY1SM=; b=JbcMAzy8KH5yxdzG7D4ggs6VlAMcDtATgdDV2MsaksTrM2RX2Se+9+2R VD5+0wY/COH+uWW8PY34ZTet5g35f/YL8p/Q2wEtGEh9bFS6YIBEYQvhs imCmpaNtekgnLZsHAQZR2uu5xs2CV9s9ORDyPYiBotexiIz6qhW28G7ba s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkFAGP7AE6rRDoG/2dsb2JhbABUnnMBiAZ3iHOhLJ4xhioEhyKKRJAm
X-IronPort-AV: E=Sophos;i="4.65,402,1304294400";  d="scan'208,217";a="466462306"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-1.cisco.com with ESMTP; 21 Jun 2011 20:15:03 +0000
Received: from stealth-10-32-254-213.cisco.com (stealth-10-32-254-213.cisco.com [10.32.254.213]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p5LKF2RG012966; Tue, 21 Jun 2011 20:15:02 GMT
Message-Id: <D4C0F99E-CFA6-4143-A044-33D1DDD359A9@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>, Joachim@strombergson.com
In-Reply-To: <BANLkTin+zWUpQPh41hSX0jKoH=QYFJo2XQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-287--332380100
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 21 Jun 2011 13:15:01 -0700
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie> <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com> <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie> <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com> <4DFD0C1B.6070909@cs.tcd.ie> <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com> <4DFF7590.2060009@Strombergson.com> <BANLkTin+zWUpQPh41hSX0jKoH=QYFJo2XQ@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 20:15:05 -0000

--Apple-Mail-287--332380100
Content-Type: text/plain;
	charset=ISO-8859-1;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: quoted-printable

Joachim, Marshall, many thanks for volunteering.   How about we =20
discuss offline how to divide up the work?  (I'm willing to put in =20
some time too.)

David

On Jun 20, 2011, at 10:18 AM, Marshall Eubanks wrote:

>
>
> 2011/6/20 Joachim Str=F6mbergson <Joachim@strombergson.com>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Aloha!
>
> On 2011:06:20 17:23, David McGrew wrote:
> > There are about 120 00-version drafts that reference crypto =20
> currently.
> > Most of those are doing the right thing, and won't require much if =20=

> any
> > work from crypto-reviewers.   This suggests that the "steady state"
> > workload of having CFRG review the uses of crypto in new I-Ds will =20=

> be
> > manageable, if we can get a couple of volunteers.  There are also =20=

> 170
> > current I-Ds that mention MD5, which suggests that the short-term
> > workload will be higher than the steady state workload.  If anyone =20=

> is
> > interested, please send a note either to the list, or to Stephen, =20=

> Sean,
> > and me.
>
> Since I'm the one who brought this up I guess I should also step up to
> the plank. ;-) Count me in.
>
> I will volunteer too.
>
> Marshall
>
>
>
> - --
> Med v=E4nlig h=E4lsning, Yours
>
> Joachim Str=F6mbergson - Alltid i harmonisk sv=E4ngning.
> =3D=20
> =3D=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Kryptoblog - IT-s=E4kerhet p=E5 svenska
> http://www.strombergson.com/kryptoblog
> =3D=20
> =3D=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk3/dZAACgkQZoPr8HT30QG3oQCfSj3ndD8lAU5xMnTBZ1QcxfgJ
> G5wAmwYUyKck3zZXhy8DdIWathWLJi+u
> =3DpfjM
> -----END PGP SIGNATURE-----
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg
>
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg


--Apple-Mail-287--332380100
Content-Type: text/html;
	charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Joachim, Marshall, many thanks =
for volunteering. &nbsp; How about we discuss offline how to divide up =
the work? &nbsp;(I'm willing to put in some time =
too.)<div><br></div><div>David</div><div><br><div><div>On Jun 20, 2011, =
at 10:18 AM, Marshall Eubanks wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><br><br><div=
 class=3D"gmail_quote">2011/6/20 Joachim Str=F6mbergson <span =
dir=3D"ltr">&lt;<a =
href=3D"mailto:Joachim@strombergson.com">Joachim@strombergson.com</a>&gt;<=
/span><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div =
class=3D"im">-----BEGIN PGP SIGNED MESSAGE-----<br> Hash: SHA1<br> <br> =
Aloha!<br> <br> </div><div class=3D"im">On 2011:06:20 17:23, David =
McGrew wrote:<br> &gt; There are about 120 00-version drafts that =
reference crypto currently.<br> &gt; Most of those are doing the right =
thing, and won't require much if any<br> &gt; work from =
crypto-reviewers. &nbsp; This suggests that the "steady state"<br> &gt; =
workload of having CFRG review the uses of crypto in new I-Ds will =
be<br> &gt; manageable, if we can get a couple of volunteers. =
&nbsp;There are also 170<br> &gt; current I-Ds that mention MD5, which =
suggests that the short-term<br> &gt; workload will be higher than the =
steady state workload. &nbsp;If anyone is<br> &gt; interested, please =
send a note either to the list, or to Stephen, Sean,<br> &gt; and =
me.<br> <br> </div>Since I'm the one who brought this up I guess I =
should also step up to<br> the plank. ;-) Count me =
in.<br></blockquote><div><br></div><div>I will volunteer =
too.</div><div><br></div><div>Marshall</div><div><br></div><div>&nbsp;</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;"> <br> - --<br> <div =
class=3D"im">Med v=E4nlig h=E4lsning, Yours<br> <br> Joachim =
Str=F6mbergson - Alltid i harmonisk sv=E4ngning.<br> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> =
Kryptoblog - IT-s=E4kerhet p=E5 svenska<br> <a =
href=3D"http://www.strombergson.com/kryptoblog" =
target=3D"_blank">http://www.strombergson.com/kryptoblog</a><br> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> =
-----BEGIN PGP SIGNATURE-----<br> Version: GnuPG v1.4.11 (Darwin)<br> =
Comment: Using GnuPG with Mozilla - <a =
href=3D"http://enigmail.mozdev.org/" =
target=3D"_blank">http://enigmail.mozdev.org/</a><br> <br> =
</div>iEYEARECAAYFAk3/dZAACgkQZoPr8HT30QG3oQCfSj3ndD8lAU5xMnTBZ1QcxfgJ<br>=
 G5wAmwYUyKck3zZXhy8DdIWathWLJi+u<br> =3DpfjM<br> -----END PGP =
SIGNATURE-----<br> <div><div></div><div =
class=3D"h5">_______________________________________________<br> Cfrg =
mailing list<br> <a href=3D"mailto:Cfrg@irtf.org">Cfrg@irtf.org</a><br> =
<a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" =
target=3D"_blank">http://www.irtf.org/mailman/listinfo/cfrg</a><br> =
</div></div></blockquote></div><br> =
_______________________________________________<br>Cfrg mailing =
list<br><a href=3D"mailto:Cfrg@irtf.org">Cfrg@irtf.org</a><br><a =
href=3D"http://www.irtf.org/mailman/listinfo/cfrg">http://www.irtf.org/mai=
lman/listinfo/cfrg</a><br></blockquote></div><br></div></body></html>=

--Apple-Mail-287--332380100--

From marshall.eubanks@gmail.com  Tue Jun 21 13:39:00 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6C3D11E807C for <cfrg@ietfa.amsl.com>; Tue, 21 Jun 2011 13:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.608
X-Spam-Level: 
X-Spam-Status: No, score=-103.608 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n-imYezPbVFy for <cfrg@ietfa.amsl.com>; Tue, 21 Jun 2011 13:39:00 -0700 (PDT)
Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by ietfa.amsl.com (Postfix) with ESMTP id 13BEA11E8075 for <cfrg@irtf.org>; Tue, 21 Jun 2011 13:38:59 -0700 (PDT)
Received: by yxl31 with SMTP id 31so92143yxl.13 for <cfrg@irtf.org>; Tue, 21 Jun 2011 13:38:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=nQncAzf6xwH4fPaQCarjaL+ssHLFAC6sVrYTL2wkaHk=; b=TP0SY/2PV+sd3tgWd3Jp4EtSef+pNtSLMnno1Qo7EKCZd3ZQeBxKKAIjwYK6Bvdogg HOj/NEKWFeLjyKG6/KS7lJp3YA091r9QW1er30jvVeBh7hPzGYSRxOQ6ufE5hn8dPXeN 6WEeYrXse4w8Z7G8fTiJks9KBM8Ly0P5Z5038=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=vzs8+mYWHcI+Vtlw92ARxLKNuFCjFEpybwBFs32aYPARfS8kmhqPNk1BR1mtJwEdYd +zuRCebuQW220z9hqtI5YdcUlGHI2hAlDA70VlU/0X9/qZNdTcbEWd6+PSnKBt7rbjzi uEMDf0IbhKROSSLCWg3kGCidva3EVwyvaKgVA=
MIME-Version: 1.0
Received: by 10.146.66.19 with SMTP id o19mr1308140yaa.13.1308688739156; Tue, 21 Jun 2011 13:38:59 -0700 (PDT)
Received: by 10.146.86.10 with HTTP; Tue, 21 Jun 2011 13:38:59 -0700 (PDT)
In-Reply-To: <D4C0F99E-CFA6-4143-A044-33D1DDD359A9@cisco.com>
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie> <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com> <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie> <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com> <4DFD0C1B.6070909@cs.tcd.ie> <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com> <4DFF7590.2060009@Strombergson.com> <BANLkTin+zWUpQPh41hSX0jKoH=QYFJo2XQ@mail.gmail.com> <D4C0F99E-CFA6-4143-A044-33D1DDD359A9@cisco.com>
Date: Tue, 21 Jun 2011 16:38:59 -0400
Message-ID: <BANLkTinwQeBRYuEG0X5iDBdzwtngb_U7+A@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: David McGrew <mcgrew@cisco.com>
Content-Type: multipart/alternative; boundary=000e0cd529766b41c304a63ed79f
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 20:39:01 -0000

--000e0cd529766b41c304a63ed79f
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 21, 2011 at 4:15 PM, David McGrew <mcgrew@cisco.com> wrote:

> Joachim, Marshall, many thanks for volunteering.   How about we discuss
> offline how to divide up the work?  (I'm willing to put in some time too.=
)
>
>
You want set up a webex or skype session?

I am free this Thursday at 10:00 AM EDT.

Marshall



> David
>
> On Jun 20, 2011, at 10:18 AM, Marshall Eubanks wrote:
>
>
>
> 2011/6/20 Joachim Str=F6mbergson <Joachim@strombergson.com>
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Aloha!
>>
>> On 2011:06:20 17:23, David McGrew wrote:
>> > There are about 120 00-version drafts that reference crypto currently.
>> > Most of those are doing the right thing, and won't require much if any
>> > work from crypto-reviewers.   This suggests that the "steady state"
>> > workload of having CFRG review the uses of crypto in new I-Ds will be
>> > manageable, if we can get a couple of volunteers.  There are also 170
>> > current I-Ds that mention MD5, which suggests that the short-term
>> > workload will be higher than the steady state workload.  If anyone is
>> > interested, please send a note either to the list, or to Stephen, Sean=
,
>> > and me.
>>
>> Since I'm the one who brought this up I guess I should also step up to
>> the plank. ;-) Count me in.
>>
>
> I will volunteer too.
>
> Marshall
>
>
>
>>
>> - --
>> Med v=E4nlig h=E4lsning, Yours
>>
>> Joachim Str=F6mbergson - Alltid i harmonisk sv=E4ngning.
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Kryptoblog - IT-s=E4kerhet p=E5 svenska
>> http://www.strombergson.com/kryptoblog
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (Darwin)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAk3/dZAACgkQZoPr8HT30QG3oQCfSj3ndD8lAU5xMnTBZ1QcxfgJ
>> G5wAmwYUyKck3zZXhy8DdIWathWLJi+u
>> =3DpfjM
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> Cfrg mailing list
>> Cfrg@irtf.org
>> http://www.irtf.org/mailman/listinfo/cfrg
>>
>
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg
>
>
>

--000e0cd529766b41c304a63ed79f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Tue, Jun 21, 2011 at 4:15 PM, David M=
cGrew <span dir=3D"ltr">&lt;<a href=3D"mailto:mcgrew@cisco.com">mcgrew@cisc=
o.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word">Joachim, Marshall, many thanks for volu=
nteering. =A0 How about we discuss offline how to divide up the work? =A0(I=
&#39;m willing to put in some time too.)<div><br></div></div></blockquote><=
div>
<br></div><div>You want set up a webex or skype session?</div><div><br></di=
v><div>I am free this Thursday at 10:00 AM EDT.</div><div><br></div><div>Ma=
rshall</div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word"><div></div><font color=3D"#888888"><div=
>David</div></font><div><div></div><div class=3D"h5"><div><br><div><div>On =
Jun 20, 2011, at 10:18 AM, Marshall Eubanks wrote:</div><br><blockquote typ=
e=3D"cite">
<br><br><div class=3D"gmail_quote">2011/6/20 Joachim Str=F6mbergson <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:Joachim@strombergson.com" target=3D"_blank=
">Joachim@strombergson.com</a>&gt;</span><br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
 <div>-----BEGIN PGP SIGNED MESSAGE-----<br> Hash: SHA1<br> <br> Aloha!<br>=
 <br> </div><div>On 2011:06:20 17:23, David McGrew wrote:<br> &gt; There ar=
e about 120 00-version drafts that reference crypto currently.<br> &gt; Mos=
t of those are doing the right thing, and won&#39;t require much if any<br>
 &gt; work from crypto-reviewers. =A0 This suggests that the &quot;steady s=
tate&quot;<br> &gt; workload of having CFRG review the uses of crypto in ne=
w I-Ds will be<br> &gt; manageable, if we can get a couple of volunteers. =
=A0There are also 170<br>
 &gt; current I-Ds that mention MD5, which suggests that the short-term<br>=
 &gt; workload will be higher than the steady state workload. =A0If anyone =
is<br> &gt; interested, please send a note either to the list, or to Stephe=
n, Sean,<br>
 &gt; and me.<br> <br> </div>Since I&#39;m the one who brought this up I gu=
ess I should also step up to<br> the plank. ;-) Count me in.<br></blockquot=
e><div><br></div><div>I will volunteer too.</div><div><br></div><div>Marsha=
ll</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> - --<br> =
<div>Med v=E4nlig h=E4lsning, Yours<br> <br> Joachim Str=F6mbergson - Allti=
d i harmonisk sv=E4ngning.<br>
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> K=
ryptoblog - IT-s=E4kerhet p=E5 svenska<br> <a href=3D"http://www.strombergs=
on.com/kryptoblog" target=3D"_blank">http://www.strombergson.com/kryptoblog=
</a><br>
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> -=
----BEGIN PGP SIGNATURE-----<br> Version: GnuPG v1.4.11 (Darwin)<br> Commen=
t: Using GnuPG with Mozilla - <a href=3D"http://enigmail.mozdev.org/" targe=
t=3D"_blank">http://enigmail.mozdev.org/</a><br>
 <br> </div>iEYEARECAAYFAk3/dZAACgkQZoPr8HT30QG3oQCfSj3ndD8lAU5xMnTBZ1Qcxfg=
J<br> G5wAmwYUyKck3zZXhy8DdIWathWLJi+u<br> =3DpfjM<br> -----END PGP SIGNATU=
RE-----<br> <div><div></div><div>__________________________________________=
_____<br>
 Cfrg mailing list<br> <a href=3D"mailto:Cfrg@irtf.org" target=3D"_blank">C=
frg@irtf.org</a><br> <a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" =
target=3D"_blank">http://www.irtf.org/mailman/listinfo/cfrg</a><br> </div><=
/div>
</blockquote></div><br> _______________________________________________<br>=
Cfrg mailing list<br><a href=3D"mailto:Cfrg@irtf.org" target=3D"_blank">Cfr=
g@irtf.org</a><br><a href=3D"http://www.irtf.org/mailman/listinfo/cfrg" tar=
get=3D"_blank">http://www.irtf.org/mailman/listinfo/cfrg</a><br>
</blockquote></div><br></div></div></div></div></blockquote></div><br>

--000e0cd529766b41c304a63ed79f--

From mcgrew@cisco.com  Tue Jun 21 13:49:44 2011
Return-Path: <mcgrew@cisco.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D983111E8075 for <cfrg@ietfa.amsl.com>; Tue, 21 Jun 2011 13:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3V4DyyuST469 for <cfrg@ietfa.amsl.com>; Tue, 21 Jun 2011 13:49:44 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by ietfa.amsl.com (Postfix) with ESMTP id DEFDB11E8071 for <cfrg@irtf.org>; Tue, 21 Jun 2011 13:49:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mcgrew@cisco.com; l=8702; q=dns/txt; s=iport; t=1308689383; x=1309898983; h=cc:message-id:from:to:in-reply-to:mime-version:subject: date:references; bh=cc4N4WAj2BPhoOf+GokUCPP94912/tRo1XjWaympWUA=; b=LedmHurHsrgX6Xx4nX+5icNGKR+fTZ2BxxrSU6z7IahJxPg/lVZPiyZn ete688fQtmxZw7xAkvufWZK7+7DzDCo68FnXO8vdDZtkWnXi0Qwf7HQlP sHyeRzJqjULvoDZ6+QGWzKkhg9NYZDQmMytJeX1l+NCCOkEbbtCtzFQxc Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqoFAJ8DAU6rRDoG/2dsb2JhbABUhhGYaQGIBneIc6Ezni+GKgSHIopEkCY
X-IronPort-AV: E=Sophos;i="4.65,402,1304294400";  d="scan'208,217";a="466489571"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-1.cisco.com with ESMTP; 21 Jun 2011 20:49:30 +0000
Received: from stealth-10-32-254-213.cisco.com (stealth-10-32-254-213.cisco.com [10.32.254.213]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p5LKnTVw027636; Tue, 21 Jun 2011 20:49:29 GMT
Message-Id: <187F8C9C-302D-49F3-A8E7-1FFDA4C476BD@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>, Joachim@Strombergson.com
In-Reply-To: <BANLkTinwQeBRYuEG0X5iDBdzwtngb_U7+A@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-289--330312822
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 21 Jun 2011 13:49:28 -0700
References: <4A7C9D3B-70C6-4D14-A5D8-F54D84DBBEA9@cisco.com> <4DF6FCAD.1000704@Strombergson.com> <4DF7E236.3060603@ieca.com> <CF0765AF-383F-423F-A8CC-10AEB4A3E348@callas.org> <4DF8627B.1030702@Strombergson.com> <74993A34-C2B3-4FA9-B27B-557AD0E3F7BB@cisco.com> <DD276523-6F9F-466E-BC85-CD9887920E6E@cisco.com> <6679410D-BF1F-4FE4-95DB-90E542CDBBD9@cs.tcd.ie> <BANLkTinJaBzm5wWTcJW1ArF8F-O78HLGKw@mail.gmail.com> <D256DDF2-6E11-4322-91B2-3F052DB52FE3@cs.tcd.ie> <BANLkTimyLVpTNcB8BoMFgjyfa23ikbt_gQ@mail.gmail.com> <4DFD0C1B.6070909@cs.tcd.ie> <BF2B2DDA-08DD-4915-9E69-F7E83BB8D728@cisco.com> <4DFF7590.2060009@Strombergson.com> <BANLkTin+zWUpQPh41hSX0jKoH=QYFJo2XQ@mail.gmail.com> <D4C0F99E-CFA6-4143-A044-33D1DDD359A9@cisco.com> <BANLkTinwQeBRYuEG0X5iDBdzwtngb_U7+A@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Cc: cfrg@irtf.org
Subject: Re: [Cfrg] What crypto algorithm is referenced most in RFCs?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 20:49:45 -0000

--Apple-Mail-289--330312822
Content-Type: text/plain;
	charset=ISO-8859-1;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: quoted-printable


On Jun 21, 2011, at 1:38 PM, Marshall Eubanks wrote:

>
>
> On Tue, Jun 21, 2011 at 4:15 PM, David McGrew <mcgrew@cisco.com> =20
> wrote:
> Joachim, Marshall, many thanks for volunteering.   How about we =20
> discuss offline how to divide up the work?  (I'm willing to put in =20
> some time too.)
>
>
> You want set up a webex or skype session?
>
> I am free this Thursday at 10:00 AM EDT.

that works for me.  How about you, Joachim?

David

>
> Marshall
>
>
> David
>
> On Jun 20, 2011, at 10:18 AM, Marshall Eubanks wrote:
>
>>
>>
>> 2011/6/20 Joachim Str=F6mbergson <Joachim@strombergson.com>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Aloha!
>>
>> On 2011:06:20 17:23, David McGrew wrote:
>> > There are about 120 00-version drafts that reference crypto =20
>> currently.
>> > Most of those are doing the right thing, and won't require much =20
>> if any
>> > work from crypto-reviewers.   This suggests that the "steady state"
>> > workload of having CFRG review the uses of crypto in new I-Ds =20
>> will be
>> > manageable, if we can get a couple of volunteers.  There are also =20=

>> 170
>> > current I-Ds that mention MD5, which suggests that the short-term
>> > workload will be higher than the steady state workload.  If =20
>> anyone is
>> > interested, please send a note either to the list, or to Stephen, =20=

>> Sean,
>> > and me.
>>
>> Since I'm the one who brought this up I guess I should also step up =20=

>> to
>> the plank. ;-) Count me in.
>>
>> I will volunteer too.
>>
>> Marshall
>>
>>
>>
>> - --
>> Med v=E4nlig h=E4lsning, Yours
>>
>> Joachim Str=F6mbergson - Alltid i harmonisk sv=E4ngning.
>> =3D=20
>> =3D=20
>> =3D=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Kryptoblog - IT-s=E4kerhet p=E5 svenska
>> http://www.strombergson.com/kryptoblog
>> =3D=20
>> =3D=20
>> =3D=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (Darwin)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAk3/dZAACgkQZoPr8HT30QG3oQCfSj3ndD8lAU5xMnTBZ1QcxfgJ
>> G5wAmwYUyKck3zZXhy8DdIWathWLJi+u
>> =3DpfjM
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> Cfrg mailing list
>> Cfrg@irtf.org
>> http://www.irtf.org/mailman/listinfo/cfrg
>>
>> _______________________________________________
>> Cfrg mailing list
>> Cfrg@irtf.org
>> http://www.irtf.org/mailman/listinfo/cfrg
>
>
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg


--Apple-Mail-289--330312822
Content-Type: text/html;
	charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><br></div><div>On Jun 21, =
2011, at 1:38 PM, Marshall Eubanks wrote:</div><div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><br><br><div=
 class=3D"gmail_quote">On Tue, Jun 21, 2011 at 4:15 PM, David McGrew =
<span dir=3D"ltr">&lt;<a =
href=3D"mailto:mcgrew@cisco.com">mcgrew@cisco.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex; position: static; z-index: =
auto; "> <div style=3D"word-wrap:break-word">Joachim, Marshall, many =
thanks for volunteering. &nbsp; How about we discuss offline how to =
divide up the work? &nbsp;(I'm willing to put in some time =
too.)<div><br></div></div></blockquote><div> <br></div><div>You want set =
up a webex or skype session?</div><div><br></div><div>I am free this =
Thursday at 10:00 AM =
EDT.</div></div></blockquote><div><br></div><div>that works for me. =
&nbsp;How about you, =
Joachim?</div><div><br></div><div>David</div><br><blockquote =
type=3D"cite"><div =
class=3D"gmail_quote"><div><br></div><div>Marshall</div><div><br></div><di=
v>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div =
style=3D"word-wrap:break-word"><div></div><font =
color=3D"#888888"><div>David</div></font><div><div></div><div =
class=3D"h5"><div><br><div><div>On Jun 20, 2011, at 10:18 AM, Marshall =
Eubanks wrote:</div><br><blockquote type=3D"cite"> <br><br><div =
class=3D"gmail_quote">2011/6/20 Joachim Str=F6mbergson <span =
dir=3D"ltr">&lt;<a href=3D"mailto:Joachim@strombergson.com" =
target=3D"_blank">Joachim@strombergson.com</a>&gt;</span><br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"> <div>-----BEGIN PGP SIGNED MESSAGE-----<br> =
Hash: SHA1<br> <br> Aloha!<br> <br> </div><div>On 2011:06:20 17:23, =
David McGrew wrote:<br> &gt; There are about 120 00-version drafts that =
reference crypto currently.<br> &gt; Most of those are doing the right =
thing, and won't require much if any<br> &gt; work from =
crypto-reviewers. &nbsp; This suggests that the "steady state"<br> &gt; =
workload of having CFRG review the uses of crypto in new I-Ds will =
be<br> &gt; manageable, if we can get a couple of volunteers. =
&nbsp;There are also 170<br> &gt; current I-Ds that mention MD5, which =
suggests that the short-term<br> &gt; workload will be higher than the =
steady state workload. &nbsp;If anyone is<br> &gt; interested, please =
send a note either to the list, or to Stephen, Sean,<br> &gt; and =
me.<br> <br> </div>Since I'm the one who brought this up I guess I =
should also step up to<br> the plank. ;-) Count me =
in.<br></blockquote><div><br></div><div>I will volunteer =
too.</div><div><br></div><div>Marshall</div> =
<div><br></div><div>&nbsp;</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> =
<br> - --<br> <div>Med v=E4nlig h=E4lsning, Yours<br> <br> Joachim =
Str=F6mbergson - Alltid i harmonisk sv=E4ngning.<br> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> =
Kryptoblog - IT-s=E4kerhet p=E5 svenska<br> <a =
href=3D"http://www.strombergson.com/kryptoblog" =
target=3D"_blank">http://www.strombergson.com/kryptoblog</a><br> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> =
-----BEGIN PGP SIGNATURE-----<br> Version: GnuPG v1.4.11 (Darwin)<br> =
Comment: Using GnuPG with Mozilla - <a =
href=3D"http://enigmail.mozdev.org/" =
target=3D"_blank">http://enigmail.mozdev.org/</a><br> <br> =
</div>iEYEARECAAYFAk3/dZAACgkQZoPr8HT30QG3oQCfSj3ndD8lAU5xMnTBZ1QcxfgJ<br>=
 G5wAmwYUyKck3zZXhy8DdIWathWLJi+u<br> =3DpfjM<br> -----END PGP =
SIGNATURE-----<br> =
<div><div></div><div>_______________________________________________<br> =
Cfrg mailing list<br> <a href=3D"mailto:Cfrg@irtf.org" =
target=3D"_blank">Cfrg@irtf.org</a><br> <a =
href=3D"http://www.irtf.org/mailman/listinfo/cfrg" =
target=3D"_blank">http://www.irtf.org/mailman/listinfo/cfrg</a><br> =
</div></div> </blockquote></div><br> =
_______________________________________________<br>Cfrg mailing =
list<br><a href=3D"mailto:Cfrg@irtf.org" =
target=3D"_blank">Cfrg@irtf.org</a><br><a =
href=3D"http://www.irtf.org/mailman/listinfo/cfrg" =
target=3D"_blank">http://www.irtf.org/mailman/listinfo/cfrg</a><br> =
</blockquote></div><br></div></div></div></div></blockquote></div><br> =
_______________________________________________<br>Cfrg mailing =
list<br><a href=3D"mailto:Cfrg@irtf.org">Cfrg@irtf.org</a><br><a =
href=3D"http://www.irtf.org/mailman/listinfo/cfrg">http://www.irtf.org/mai=
lman/listinfo/cfrg</a><br></blockquote></div><br></body></html>=

--Apple-Mail-289--330312822--

From asuganya@rediffmail.com  Thu Jun 30 05:32:39 2011
Return-Path: <asuganya@rediffmail.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2061D9E8012 for <cfrg@ietfa.amsl.com>; Thu, 30 Jun 2011 05:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.457
X-Spam-Level: ****
X-Spam-Status: No, score=4.457 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HTML_MESSAGE=0.001, MSGID_FROM_MTA_HEADER=0.803, SARE_SUB_ENC_UTF8=0.152, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SurENG6c9XmN for <cfrg@ietfa.amsl.com>; Thu, 30 Jun 2011 05:32:35 -0700 (PDT)
Received: from rediffmail.com (f5mail-224-146.rediffmail.com [114.31.224.146]) by ietfa.amsl.com (Postfix) with SMTP id CC8969E800C for <cfrg@irtf.org>; Thu, 30 Jun 2011 05:32:33 -0700 (PDT)
Received: (qmail 20518 invoked by uid 510); 30 Jun 2011 12:32:23 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=redf; d=rediffmail.com; b=dCcA63QJvk+N5JUI4x6VdyfiBx3V58BhDRzCzpc1EwGjfdfLWeo5TJtYeypPVpehPVgc149RD6uksvqRAmNUDRdTwCgKJkE8gz9fbaLNkiFgBMbxX4nrVDK6FUc9mqskL2tpjQ2jgrCwc6qlFxTDJ5UoUCU5banvc87hxLiWFGg= ; 
x-m-msg: asd54ad564ad7aa6sd5as6d5; a6da7d6asas6dasd77; 5dad65ad5sd;
X-CTCH-Spam: Unknown
X-CTCH-VOD: Unknown
X-CTCH-Flags: : 0
X-CTCH-RefID: str=0001.0A150202.4E0C6CD8.007B,ss=1,fgs=0
Date: 30 Jun 2011 12:32:22 -0000
Message-ID: <20110630123222.20508.qmail@f5mail-224-146.rediffmail.com>
MIME-Version: 1.0
To: "cfrg@irtf.org" <cfrg@irtf.org>
Received: from unknown 111.93.96.66 by rediffmail.com via HTTP; 30 Jun 2011 12:32:22 -0000
Sender: asuganya@rediffmail.com
From: "A  SUGANYA" <asuganya@rediffmail.com>
Content-Type: multipart/alternative; boundary="=_01a3a62d182fb079e2b322b04caf0dc2"
Subject: [Cfrg] =?utf-8?q?Mechanism_of_using_block_cipher?=
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: asuganya@rediffmail.com
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 12:32:39 -0000

--=_01a3a62d182fb079e2b322b04caf0dc2
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"



I would like to know about a
mechanism of using AES-128 block cipher (in any secure mode of operation) for frame (Ethernet frame at data link layer) encryption. Please note that the size of frame will not be multiples of block size and frame size will not be constant for all frames. Also, for synchronisation purpose we prefer not to carry-forward the current frame bits to next frame.

Suganya
--=_01a3a62d182fb079e2b322b04caf0dc2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="UTF-8"

<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:DontVertAlignCellWithSp/>
   <w:DontBreakConstrainedForcedTables/>
   <w:DontVertAlignInTxbx/>
   <w:Word11KerningPairs/>
   <w:CachedColBalance/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"--"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"
  DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"267">
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D=
"caption"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph=
 Font"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeho=
lder Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Revisio=
n"/>
  <w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D=
"TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin-top:auto;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:auto;
	mso-para-margin-left:0in;
	text-align:justify;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;}
</style>
<![endif]-->

<p class=3D"MsoNormal">I would like to know about a
mechanism of using AES-128 block cipher (in any secure mode of operation) f=
or frame (Ethernet frame at data link layer) encryption. Please note that t=
he size of frame will not be multiples of block size and frame size will no=
t be constant for all frames. Also, for synchronisation purpose we prefer n=
ot to carry-forward the current frame bits to next frame.<br></p><br>Sugany=
a<br><A HREF=3D"http://sigads.rediff.com/RealMedia/ads/click_nx.ads/www.red=
iffmail.com/signatureline.htm@Middle?" target=3D"_blank"><IMG SRC=3D"http:/=
/sigads.rediff.com/RealMedia/ads/adstream_nx.ads/www.rediffmail.com/signatu=
reline.htm@Middle"></A><br>Treat yourself at a restaurant, spa, resort and =
much more with <b><a href=3D"http://track.rediff.com/click?url=3D___http://=
dealhojaye.rediff.com?sc_cid=3Dmailsignature___&cmp=3Dsignature&lnk=3Dredif=
fmailsignature&newservice=3Ddeals" target =3D"_new">Rediff Deal ho jaye!</a=
></b>
--=_01a3a62d182fb079e2b322b04caf0dc2--

From ggr@qualcomm.com  Thu Jun 30 09:42:46 2011
Return-Path: <ggr@qualcomm.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF4011E8085 for <cfrg@ietfa.amsl.com>; Thu, 30 Jun 2011 09:42:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GmPmT7Lis6oI for <cfrg@ietfa.amsl.com>; Thu, 30 Jun 2011 09:42:45 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id C05E111E8080 for <cfrg@irtf.org>; Thu, 30 Jun 2011 09:42:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=ggr@qualcomm.com; q=dns/txt; s=qcdkim; t=1309452165; x=1340988165; h=from:to:cc:subject:thread-topic:thread-index:date: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: x-originating-ip:content-type:content-id: content-transfer-encoding:mime-version; z=From:=20"Rose,=20Greg"=20<ggr@qualcomm.com>|To:=20"<asug anya@rediffmail.com>"=20<asuganya@rediffmail.com>|CC:=20" Rose,=20Greg"=20<ggr@qualcomm.com>,=20"cfrg@irtf.org"=20< cfrg@irtf.org>|Subject:=20Re:=20[Cfrg]=20Mechanism=20of =20using=20block=20cipher|Thread-Topic:=20[Cfrg]=20Mechan ism=20of=20using=20block=20cipher|Thread-Index:=20AQHMNyH Wrh8LiSqTLE+omBHm4L9Jt5TWkHoA|Date:=20Thu,=2030=20Jun=202 011=2016:42:28=20+0000|Message-ID:=20<F5B7568B-213F-4BB1- 857E-2D6D5170BF2D@qualcomm.com>|References:=20<2011063012 3222.20508.qmail@f5mail-224-146.rediffmail.com> |In-Reply-To:=20<20110630123222.20508.qmail@f5mail-224-14 6.rediffmail.com>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|x-originating-ip:=20[199.106.114.1 30]|Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |Content-ID:=20<D6F8CAFDA48D73429D44A5AF888ADD45@qualcomm .com>|Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0; bh=RRQtuOJ3VJqPMckrDhu3aHmftpUUjpO5yqLigHVmxhs=; b=bA1HRW1jaZLDBQzX0IM1wuOkL00yssrBLBTaVpgSD4iyGhcwPAV+UXCh rB7hGmGgyWhHQaVeQRZjiUUuOdsypuxMafs6G19063hoM9aD+JrjRIDtw rqP4TLtnVLLcOeU0YzMLdXw2j8pHxIhljpid07mO/YLKiZ0RnyTaNFgV3 o=;
X-IronPort-AV: E=McAfee;i="5400,1158,6392"; a="101133257"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 30 Jun 2011 09:42:29 -0700
X-IronPort-AV: E=Sophos;i="4.65,450,1304319600"; d="scan'208";a="40063147"
Received: from nasanexhc09.na.qualcomm.com ([172.30.39.8]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 30 Jun 2011 09:42:29 -0700
Received: from NASANEXD01D.na.qualcomm.com ([fe80::4d64:11bc:743c:6fdb]) by nasanexhc09.na.qualcomm.com ([::1]) with mapi id 14.01.0270.001; Thu, 30 Jun 2011 09:42:28 -0700
From: "Rose, Greg" <ggr@qualcomm.com>
To: "<asuganya@rediffmail.com>" <asuganya@rediffmail.com>
Thread-Topic: [Cfrg] Mechanism of using block cipher
Thread-Index: AQHMNyHWrh8LiSqTLE+omBHm4L9Jt5TWkHoA
Date: Thu, 30 Jun 2011 16:42:28 +0000
Message-ID: <F5B7568B-213F-4BB1-857E-2D6D5170BF2D@qualcomm.com>
References: <20110630123222.20508.qmail@f5mail-224-146.rediffmail.com>
In-Reply-To: <20110630123222.20508.qmail@f5mail-224-146.rediffmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [199.106.114.130]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D6F8CAFDA48D73429D44A5AF888ADD45@qualcomm.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Rose, Greg" <ggr@qualcomm.com>, "cfrg@irtf.org" <cfrg@irtf.org>
Subject: Re: [Cfrg] Mechanism of using block cipher
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 16:42:46 -0000

You could use CCM mode (for compatibility with WiFi) or EAX mode.

Greg.

On 2011 Jun 30, at 5:32 , A SUGANYA wrote:

> I would like to know about a mechanism of using AES-128 block cipher (in =
any secure mode of operation) for frame (Ethernet frame at data link layer)=
 encryption. Please note that the size of frame will not be multiples of bl=
ock size and frame size will not be constant for all frames. Also, for sync=
hronisation purpose we prefer not to carry-forward the current frame bits t=
o next frame.
>=20
>=20
> Suganya
>=20
> Treat yourself at a restaurant, spa, resort and much more with Rediff Dea=
l ho jaye!_______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg


From mcgrew@cisco.com  Thu Jun 30 09:54:03 2011
Return-Path: <mcgrew@cisco.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E59E911E80D4 for <cfrg@ietfa.amsl.com>; Thu, 30 Jun 2011 09:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wKaITmkgk7CX for <cfrg@ietfa.amsl.com>; Thu, 30 Jun 2011 09:53:58 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id A672A11E81A0 for <cfrg@irtf.org>; Thu, 30 Jun 2011 09:53:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mcgrew@cisco.com; l=1335; q=dns/txt; s=iport; t=1309452838; x=1310662438; h=cc:message-id:from:to:in-reply-to: content-transfer-encoding:mime-version:subject:date: references; bh=2N316Q1ObMO+lPE2ETaa+dztzWgylZgSNrAhQTiX9Io=; b=mNJ8ECJVRPKWMD4VvK5GJsiRwK/i26GvMfj8VRebhEnPRIaja2T/mDv4 M+ZbeRB15BPlIvu/F3jgJ4r+2b+8kwDFS2TkodOlR92DGUo5yYV3th7yI by1a0Q5Nao23gUfa8/VT1hGpl7hds31ic2ggdbqTop8iHlQEkzzTMZAKo 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAL+pDE6rRDoI/2dsb2JhbABSp1Z3iHihTJ18hjEEh0CKb5BO
X-IronPort-AV: E=Sophos;i="4.65,451,1304294400"; d="scan'208";a="724890214"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-6.cisco.com with ESMTP; 30 Jun 2011 16:53:58 +0000
Received: from stealth-10-32-254-214.cisco.com (stealth-10-32-254-214.cisco.com [10.32.254.214]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p5UGrvWT021894; Thu, 30 Jun 2011 16:53:57 GMT
Message-Id: <CEFC3182-AC0D-4E8D-8810-DB9199517BE9@cisco.com>
From: David McGrew <mcgrew@cisco.com>
To: A SUGANYA <asuganya@rediffmail.com>
In-Reply-To: <F5B7568B-213F-4BB1-857E-2D6D5170BF2D@qualcomm.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 30 Jun 2011 09:53:56 -0700
References: <20110630123222.20508.qmail@f5mail-224-146.rediffmail.com> <F5B7568B-213F-4BB1-857E-2D6D5170BF2D@qualcomm.com>
X-Mailer: Apple Mail (2.936)
Cc: Greg Rose <ggr@qualcomm.com>, cfrg@irtf.org
Subject: Re: [Cfrg] Mechanism of using block cipher
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 16:54:03 -0000

Hi Suganya,

AES-GCM is what 802.1AE MAC Security uses for frame encryption, see http://www.ieee802.org/1/pages/802.1ae.html 
    If you are looking to protect ethernet frames, it seems like you  
would be interested in that standard.  It is supported in commercially  
available ethernet ASICs and some higher end NIC cards.

David

On Jun 30, 2011, at 9:42 AM, Rose, Greg wrote:

> You could use CCM mode (for compatibility with WiFi) or EAX mode.
>
> Greg.
>
> On 2011 Jun 30, at 5:32 , A SUGANYA wrote:
>
>> I would like to know about a mechanism of using AES-128 block  
>> cipher (in any secure mode of operation) for frame (Ethernet frame  
>> at data link layer) encryption. Please note that the size of frame  
>> will not be multiples of block size and frame size will not be  
>> constant for all frames. Also, for synchronisation purpose we  
>> prefer not to carry-forward the current frame bits to next frame.
>>
>>
>> Suganya
>>
>> Treat yourself at a restaurant, spa, resort and much more with  
>> Rediff Deal ho jaye!_______________________________________________
>> Cfrg mailing list
>> Cfrg@irtf.org
>> http://www.irtf.org/mailman/listinfo/cfrg
>
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg


From Christine.SevernsWilliams@lsi.com  Thu Jun 30 10:40:12 2011
Return-Path: <Christine.SevernsWilliams@lsi.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 580B611E8261 for <cfrg@ietfa.amsl.com>; Thu, 30 Jun 2011 10:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UTyGCq1w8dUG for <cfrg@ietfa.amsl.com>; Thu, 30 Jun 2011 10:40:11 -0700 (PDT)
Received: from na3sys009aog104.obsmtp.com (na3sys009aog104.obsmtp.com [74.125.149.73]) by ietfa.amsl.com (Postfix) with ESMTP id E8D0511E80D9 for <cfrg@irtf.org>; Thu, 30 Jun 2011 10:40:10 -0700 (PDT)
Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob104.postini.com ([74.125.148.12]) with SMTP ID DSNKTgy0+r5Rsk8ks/0RTFx1xuAtYRwxBUiG@postini.com; Thu, 30 Jun 2011 10:40:11 PDT
Received: from PALCAS01.lsi.com (128.94.213.117) by PALEDGE01.lsi.com (192.19.193.42) with Microsoft SMTP Server (TLS) id 8.3.137.0; Thu, 30 Jun 2011 13:41:20 -0400
Received: from palmail02.lsi.com ([128.94.233.45]) by PALCAS01.lsi.com ([128.94.213.117]) with mapi; Thu, 30 Jun 2011 13:40:09 -0400
From: "Severns-Williams, Christine E (Christine)" <Christine.SevernsWilliams@lsi.com>
To: "cfrg@irtf.org" <cfrg@irtf.org>
Date: Thu, 30 Jun 2011 13:40:08 -0400
Thread-Topic: SRTP with SHA2?
Thread-Index: Acw3TME30KqfVTrIQzqmwhaMKqx0xg==
Message-ID: <E04A0D4E9A590848A5B84212DFD59B4B02B035A32C@palmail02.lsi.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_E04A0D4E9A590848A5B84212DFD59B4B02B035A32Cpalmail02lsic_"
MIME-Version: 1.0
Subject: [Cfrg] SRTP with SHA2?
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/cfrg>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 17:40:12 -0000

--_000_E04A0D4E9A590848A5B84212DFD59B4B02B035A32Cpalmail02lsic_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,
  I'm not sure this is really the right mail list for this question.  But I=
 see SHA2 being added to many security protocols (IPsec, TLS, etc) and disc=
ussion of other algorithms fading such as MD5.

I know SRTP supports AES-CM (128, 192, 256), AES-f8, and there is a draft f=
or AES-CCM and AES-GCM (128 and 256).

Has anyone considered or is looking at using/adding SHA2 to the SRTP protoc=
ol?     Just curious.

I know the digest size is larger but it could still be truncated.

Thanks,
Christine
___________________________________________________________________________=
____
Christine Severns                                               Phone: + 1 =
651-675-2987
System, Processor and Security Architecture      Mobile: + 1 612 309-6969
LSI Corporation                                                 Email: Chri=
stine.SevernsWilliams@lsi.com<mailto:Christine.SevernsWilliams@lsi.com>
St. Paul, MN 55120 USA


--_000_E04A0D4E9A590848A5B84212DFD59B4B02B035A32Cpalmail02lsic_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi All,<o:p></o:=
p></p><p class=3DMsoNormal>&nbsp; I&#8217;m not sure this is really the rig=
ht mail list for this question.&nbsp; But I see SHA2 being added to many se=
curity protocols (IPsec, TLS, etc) and discussion of other algorithms fadin=
g such as MD5.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p c=
lass=3DMsoNormal>I know SRTP supports AES-CM (128, 192, 256), AES-f8, and t=
here is a draft for AES-CCM and AES-GCM (128 and 256). <o:p></o:p></p><p cl=
ass=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Has anyone consid=
ered or is looking at using/adding SHA2 to the SRTP protocol?&nbsp; &nbsp;&=
nbsp;&nbsp;Just curious.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:=
p></p><p class=3DMsoNormal>I know the digest size is larger but it could st=
ill be truncated.&nbsp; <o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:=
p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Ari=
al","sans-serif"'>Thanks,</span><o:p></o:p></p><p class=3DMsoNormal><span s=
tyle=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Christine</span>=
<o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fa=
mily:"Arial","sans-serif"'>________________________________________________=
_______________________________</span><o:p></o:p></p><p class=3DMsoNormal><=
span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Christine =
Severns&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Phone: + 1 651-675-2987</s=
pan><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:"Arial","sans-serif"'>System, Processor and Security Architecture&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile: + 1 612 309-6969</span><o:p></o:p></p=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","=
sans-serif"'>LSI Corporation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; Email: <a href=3D"mailto:Christine.SevernsWilliams@lsi.com"><sp=
an style=3D'color:blue'>Christine.SevernsWilliams@lsi.com</span></a></span>=
<o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fa=
mily:"Arial","sans-serif"'>St. Paul, MN 55120 USA</span><o:p></o:p></p><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_000_E04A0D4E9A590848A5B84212DFD59B4B02B035A32Cpalmail02lsic_--
