Re: [Cfrg] I-D Action: draft-irtf-cfrg-randomness-improvements-08.txt

"Christopher Wood" <caw@heapingbits.net> Tue, 03 December 2019 21:18 UTC

Return-Path: <caw@heapingbits.net>
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 E0E5512003E for <cfrg@ietfa.amsl.com>; Tue, 3 Dec 2019 13:18:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=heapingbits.net header.b=Wqt27Qd9; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=NK/Gglcw
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 uYXozTXspd7l for <cfrg@ietfa.amsl.com>; Tue, 3 Dec 2019 13:18:09 -0800 (PST)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2A2012002F for <cfrg@irtf.org>; Tue, 3 Dec 2019 13:18:09 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id BC0068E5; Tue, 3 Dec 2019 16:18:07 -0500 (EST)
Received: from imap4 ([10.202.2.54]) by compute6.internal (MEProxy); Tue, 03 Dec 2019 16:18:08 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm3; bh=4+sWD6eruPkP/Iyjy6z3/RKLF04i fGsKvHF80bTnId4=; b=Wqt27Qd9hhKKubPbJT/6CmHeOd2iNP11vlUmiUmo+O7I 9mL5KJmT8SJ8xKpQ4OC6GJzflZ5IGLTgIRwyLZDt6wqXN75zEQzifkrRqipW50gC iyst/AFuCl57/EebOHyT9dHOb0fpceAtRF1XnMxClgKUx06eOGcYniuRT+ewCM/+ J1iRKxnerEAwHhFWy3NzI20SpGHd1ztHYFtUHijl0Ov6HhbFFyKSQ8fFGtAf4EVc kkJYf4dD2PPeJXtgUqBoH0oCxMooustqUHIqqKAFk8RDkn9mJQNW78KzEtUquEn7 gjrp0yG1xg43C9In2YOvQrwu+9Cv3oPagXcsq6AclQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=4+sWD6 eruPkP/Iyjy6z3/RKLF04ifGsKvHF80bTnId4=; b=NK/GglcwWyDI7Cu5kv77Wb V3C2vEhBT4rIA+OmCTUGoezeFRKw5EDz8LPkkKTLu5dMIKKteW3ql7dkG3SXFffx xlTvFAD+/aCV72P1RntMdV/Ewd4f34IRqygg3TNA9g73Ns93x+Am+UFDUxYgoYUM 8uKf5SRug1PRq25JhvjK9f5Nu/Nq5buc6PZcCR66CuRjmbF7v9I+zaDaqfiYqlPv 9Ww0ddpDr+U2tg+ZsFrb9Xtu02dUzU5SWgEXAu8mJNX4I7CFhWYG0zz0Cl/seWW2 gcd+mgBSDLl8R7oN0UjBN5B9cGDPwdKjQAw1sFP1u8+JpRWPwU0E7CyBQk8RnV1w ==
X-ME-Sender: <xms:D9HmXRnDSFg1L29zgk5XR84MErVwHad5D43-F4sTkjOT5t3IjWLLTw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudejjedgudegjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedfvehh rhhishhtohhphhgvrhcuhghoohgufdcuoegtrgifsehhvggrphhinhhgsghithhsrdhnvg htqeenucfrrghrrghmpehmrghilhhfrhhomheptggrfieshhgvrghpihhnghgsihhtshdr nhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:D9HmXfRBmLMirx1_IdgJtk4hz5rSC4yI78cUWRb1mjMgS5QuMWvjQw> <xmx:D9HmXX0Sqse2pMwBqdSJx4M4pEvPs2pz_s4Yl7MdYw4fH9neUlaF6g> <xmx:D9HmXZHeeNA7NOw_7NfibHiZyq-uFiL8m9Oi7Abo_L9VRqKkhELg3g> <xmx:D9HmXXZ6DLF4Kb8nsZE626p_5Lq0v_KKvMqpBeDSsmXLI9pHACQrkA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 0B5403C00A1; Tue, 3 Dec 2019 16:18:07 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-612-g13027cc-fmstable-20191203v1
Mime-Version: 1.0
Message-Id: <d6cd6002-8984-4940-a06e-9c46d2f789eb@www.fastmail.com>
In-Reply-To: <CAMr0u6mEW=orEF6YtbTfdQy5EuQHDqdo=2_R243PUkqGD2Vgqg@mail.gmail.com>
References: <157273808364.6043.6715638492611593951@ietfa.amsl.com> <77AD232C-094D-4FC1-A966-DA56EC44A27F@ericsson.com> <CAMr0u6=7r2wAD_3Yn1hBjJW-y=8FE27jeYQW8wk3wJ-Xh2g2hg@mail.gmail.com> <20191122162758.kzx3vl4ibayykyqu@positron.jfet.org> <CAMr0u6=94uCjUybJ89Nf-qNvyKFPkX_KWM6k5u1kPUZMOCLNRw@mail.gmail.com> <20191124213717.o5gjtyv55lmlcy4s@positron.jfet.org> <CAMr0u6mEW=orEF6YtbTfdQy5EuQHDqdo=2_R243PUkqGD2Vgqg@mail.gmail.com>
Date: Tue, 03 Dec 2019 13:17:45 -0800
From: Christopher Wood <caw@heapingbits.net>
To: "Stanislav V. Smyshlyaev" <smyshsv@gmail.com>, "Riad S. Wahby" <rsw@jfet.org>, Christopher Wood <christopherwood07@gmail.com>, Nick Sullivan <nick@cloudflare.com>
Cc: "cfrg@irtf.org" <cfrg@irtf.org>
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/910Xw1XenMm_1f7v0lg4M9id_WI>
Subject: Re: [Cfrg] I-D Action: draft-irtf-cfrg-randomness-improvements-08.txt
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.29
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: Tue, 03 Dec 2019 21:18:11 -0000


On Wed, Nov 27, 2019, at 1:56 AM, Stanislav V. Smyshlyaev wrote:
> >> In this case, it seems like a separate document for other constructions
> is definitely more appropriate---no sense introducing serious delay for
> this document
> 
> Many thanks, Riad!
> 
> I'll definitely think about this - maybe it will be reasonable to 
> arrange a discussion of this (with slides, at CFRG) at IETF 107 and 
> initiate a document on this.
> If you don't mind, I'll get in touch with you off-list in the beginning 
> of 2020 - to discuss, what should be included in such a document. Would 
> you like to participate in this?..
> 
> >> But: would it be possible to clarify, maybe just in the intro, that 
> this document is primarily geared toward the HSM case?
> I think that mentioning HSMs as one of most important cases when the 
> construction is needed, can be helpful. 
> Chris, Nick, what do you think?

+1 -- this makes sense to me!

Best,
Chris