[Cfrg] Fwd: [saag] possible BCP on public review being needed for standards-track crypto

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 23 March 2016 14:19 UTC

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 9BACC12D526 for <cfrg@ietfa.amsl.com>; Wed, 23 Mar 2016 07:19:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id th8R_OGWu8pD for <cfrg@ietfa.amsl.com>; Wed, 23 Mar 2016 07:19:21 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AFB412DAB3 for <Cfrg@irtf.org>; Wed, 23 Mar 2016 07:06:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 14BB5BE29 for <Cfrg@irtf.org>; Wed, 23 Mar 2016 14:06:18 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BT2S-lI-37em for <Cfrg@irtf.org>; Wed, 23 Mar 2016 14:06:16 +0000 (GMT)
Received: from [192.150.181.133] (unknown [192.150.181.133]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 09978BDD0 for <Cfrg@irtf.org>; Wed, 23 Mar 2016 14:06:16 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1458741976; bh=Ql/Wc2Pnt97v4TkSOCTmIXfVBLttrMnenTMzCxKeTAY=; h=Subject:References:To:From:Date:In-Reply-To:From; b=YW+0Rp4rMAwxz8GSBwcygQ7BNe8q7pW/HDbx0uc+0L14Zod38Xcu2JQASpABPiE5C GF/azTqUikmQ79+wG70YFVcEZ2+KjMaqIYn/gt3vExuQmr/qcbLzcM/tPdlI39fCgm PqFeP5C9lXQsXNSjUvzqPgjDYcC+HujvvWRFT+6w=
References: <56F29DE6.50508@cs.tcd.ie>
To: "cfrg@irtf.org" <Cfrg@irtf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
X-Forwarded-Message-Id: <56F29DE6.50508@cs.tcd.ie>
Message-ID: <56F2A2D7.7020402@cs.tcd.ie>
Date: Wed, 23 Mar 2016 14:06:15 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56F29DE6.50508@cs.tcd.ie>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms070007040009060101020201"
Archived-At: <http://mailarchive.ietf.org/arch/msg/cfrg/ZqLtrKHzOq0737Kc4zwTZchWF7c>
Subject: [Cfrg] Fwd: [saag] possible BCP on public review being needed for standards-track crypto
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2016 14:19:25 -0000

FYI. Please send comments to saag@ietf.org.

If you just want to say "+1" that's as useful here I guess,
but if you think this is a bad idea, please explain why on
the saag list, and of course any detailed comments should
go to the saag list.

Thanks,
S.

-------- Forwarded Message --------
Subject: [saag] possible BCP on public review being needed for
standards-track crypto
Date: Wed, 23 Mar 2016 13:45:10 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: saag@ietf.org <saag@ietf.org>


Hiya,

Rich Salz has put together an initial stab at a draft of a BCP [1]
that says "for IETF standards track, crypto algorithms need to
have had public analysis." (Thanks Rich!)

I think this'd be a good thing to progress but as you'll see the
-00 submitted just at the cutoff needs a good bit of work. (Still
great to have a starting point though, so thanks again Rich:-)

So, please read and comment on saag@ietf.org. As well as getting
detailed comments, I'd also be interested in whether or not
folks think the basic premise is something it'd be good to have
as a BCP, so thumbs-up/down messages are also useful at this
point. (If "thumbs-down" please say why, if "thumbs-up" then
later detailed wrangling over text will be fine.)

We'll have a short 5-min slot for this in the saag session in B-A
just to bring it to folks' attention.  If there are issues that
we don't resolve on the list (e.g. I'd expect that getting a good
enough description of "public review" might be tricky) we can have
a more extended discussion about this at saag in Berlin.

Cheers,
S.

[1] https://tools.ietf.org/html/draft-rsalz-drbg-speck-wap-wep