Return-Path: 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 9034812F299 for ; Tue, 18 Jul 2017 11:37:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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=gmail.com 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 Sv0bLX6Ml5xX for ; Tue, 18 Jul 2017 11:37:31 -0700 (PDT) Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D54B129B35 for ; Tue, 18 Jul 2017 11:37:31 -0700 (PDT) Received: by mail-yw0-x235.google.com with SMTP id y186so9761096ywc.1 for ; Tue, 18 Jul 2017 11:37:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fIs9mRoCp8OXtZODjnmYDZSNZw3pca2UN+mVwQpCZGA=; b=a/T3qJvSYyoSNS5TSNvnGQBU/NJtknaSzHs6RDaoZ7tDDhKv9YQ5YzW+ph2bKxxkmq 0LKwDI9DMWa+a4O0N8cfGl4gDGfej43m9Si17BNc7A7b9DIOzD6/erm430XkL+i2P8B4 MAGbXyiNXWxrnMuVsbzK9iO/zuNIoUvkfGFnNHF+owWRF+A26nF+om33FRCHxHK+xdCd 4eNKxErnm/sLcWHT3Rb6fA0qg0akuGvf5tTdQro/GdAakuy8vknvmEmxN9vicO0M1Iqy ygLlay4CD54It9ShYMy2uGJt8axjgmuT/QZpPrN/N02/pHScRsQjMs/mH3dh8B2u9E+A UMuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fIs9mRoCp8OXtZODjnmYDZSNZw3pca2UN+mVwQpCZGA=; b=sEvOSIU4gWqhDIwPtOtDBV/rJ5EW9fp2ZvKNvjXFprnvy9C//8DpCDCLecsvn4hb2n Iw8E4ahpe0oQ1wwGGq415daK5qXYvpnmlqioHfJOsqa19+UhssFSwdR//OrJOk+xVAOv 2GIc5Y0UVKXUT8tROQRLv431PAfuvWe7m+NqvnPJKCoAoJgzirV7YPQmsNRny/JLnS3D SE5BGQz/kARyy9fwjvkIEbyHRs2PzVdjuqmUEpxKCdZiCND+8yqQ48JsQAwgh57DClem B9qqoowRHkYvRvQ5qgk/wGKYqL0a9uhXy1ju6WFfV6AJlxYGqxPiEXUoGJgvlRnfjdk8 XXwA== X-Gm-Message-State: AIVw113P35aJEJ8sxrAIAH4IG4Y37Zuibv0vrCsMfbRpjW3DEchDCEgX WT6l8CjxCGB+Urx4zLaucavILEJRjg== X-Received: by 10.129.53.205 with SMTP id c196mr2311279ywa.38.1500403050190; Tue, 18 Jul 2017 11:37:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.170.132 with HTTP; Tue, 18 Jul 2017 11:37:09 -0700 (PDT) In-Reply-To: References: From: Tony Arcieri Date: Tue, 18 Jul 2017 11:37:09 -0700 Message-ID: To: Sharon Goldberg Cc: "cfrg@irtf.org" , jan@ns1.com, Dimitrios Papadopoulos , Leonid Reyzin Content-Type: multipart/alternative; boundary="001a114224c6d3b48005549bce86" Archived-At: Subject: Re: [Cfrg] draft-goldbe-vrf: Verifiable Random Functions X-BeenThere: cfrg@irtf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Crypto Forum Research Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jul 2017 18:37:32 -0000 --001a114224c6d3b48005549bce86 Content-Type: text/plain; charset="UTF-8" Just a quick note on section 5.4.1, and perhaps a question to the chairs: Would it be worth it for the CFRG to specify standard schemes for hashing to elliptic curve points? This draft talks about both the "hash and pray" method (5.4.1.1) then also the Icart method as well as Elligator (5.4.1.2). This seems like a common enough problem it'd be nice to have off-the-shelf solutions for it, rather than every higher level protocol having to specify their own. -- Tony Arcieri --001a114224c6d3b48005549bce86 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Just a quick note on section 5.4.1, and perhaps a question= to the chairs:

Would it be worth it for the CFRG to specify = standard schemes for hashing to elliptic curve points? This draft talks abo= ut both the "hash and pray" method (5.4.1.1) then also the Icart = method as well as Elligator (5.4.1.2).

This seems like a= common enough problem it'd be nice to have off-the-shelf solutions for= it, rather than every higher level protocol having to specify their own.
--
Tony Arcieri
--001a114224c6d3b48005549bce86--