[Cfrg] Nomination of OPAQUE

Hugo Krawczyk <hugokraw@gmail.com> Wed, 29 May 2019 03:28 UTC

Return-Path: <hugokraw@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 2EC161200F6 for <cfrg@ietfa.amsl.com>; Tue, 28 May 2019 20:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 Th9FUZqZ6-DE for <cfrg@ietfa.amsl.com>; Tue, 28 May 2019 20:28:49 -0700 (PDT)
Received: from mail-it1-x12d.google.com (mail-it1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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 9A1DB120074 for <cfrg@irtf.org>; Tue, 28 May 2019 20:28:49 -0700 (PDT)
Received: by mail-it1-x12d.google.com with SMTP id g23so4324085iti.1 for <cfrg@irtf.org>; Tue, 28 May 2019 20:28:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=40k5M+kx3RpJ6cDadah4c0CHE6Lb5tn6XwWdMt7Obpo=; b=Ma2kYtEdvWF55m1822iL4oxBMN5J8lWaGXBs5uEq22NmTt5iD9AIeN7vPa2kWDdPKb 5y03pya9MPoGLPmBhzwRjheASqOAJRQxnf36JQ9CqIxLbcKnkeXPBLV9XUzrqEte6lFA LV6zGyD8b6uvMSsnNEbEECo/NgymlGzKrw3gwXa8IAI4/ozowieWf4Sz+5FiwTz3Rf4K cEQzIn3bdrAYuE6cmIxVlg1wZvthnIfYS1Oq4tbzyCgL6XTh1if6q0pRp+EICN1i5ea9 aBss02cB+qJ/hY0SkFVxfyk9j4ahhujW+nlVn83TtY7+tW0jdYSFBdnzgisFSie41pKD 8JXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=40k5M+kx3RpJ6cDadah4c0CHE6Lb5tn6XwWdMt7Obpo=; b=EXq080AONcp+BCI29tjhbio30bee+8Sdd0s2Xx1gpg1yqj7y4T+Po3rCQ3EUSJ8p10 NTMmhkfh92UCefkrlHGYcIn9baYikKzMhk7oHni5wNUhlKSVSIcolhBVLzLpnFU7h+sf MNO0YItmoDuZBTkDOdpD2PQhGreYYEzENJD/qkUxH51gyGkN8fYbGU2dfvYOav1Up6jv KhzDLNE+lvXdAQZHEtAFjS2d5mozuVACSOcK1sz7+QRyROs+70P/U2Bha/h7oFQhofQ/ urMwdMZLqCF/AFQ6tQZOergSzV6r4U0FkkUYEnAuT88FKOdFn71HrT8DA3BLAwMiOr7X jZDg==
X-Gm-Message-State: APjAAAW/8yQhDZzoBvahDxXkHdfojEQDh00MbifEB0SdMzwYSIZ1gxKt YYOHb6TjB++aSgIcFNTXUeEHQ9mnFzFjyUPShfe4EJFKh94=
X-Google-Smtp-Source: APXvYqzRi2GvhD+W/uSfBXK6wOPyRt8loYFHzXMaBT+UM3ing5SUmeVvazZJH02y43eoj9OdH+tdv5WJR0gHxfUH9Ho=
X-Received: by 2002:a24:27c6:: with SMTP id g189mr5584437ita.114.1559100528661; Tue, 28 May 2019 20:28:48 -0700 (PDT)
MIME-Version: 1.0
From: Hugo Krawczyk <hugokraw@gmail.com>
Date: Tue, 28 May 2019 23:28:24 -0400
Message-ID: <CADi0yUOqxvohNHeyDKMxJSDcceruobeeiNK=Eunu0=3pQiMrTQ@mail.gmail.com>
To: CFRG <cfrg@irtf.org>
Content-Type: multipart/alternative; boundary="0000000000002e1b210589fe61bf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/XZetYYkt8te3aYv0ztRNQHMzzHc>
Subject: [Cfrg] Nomination of OPAQUE
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: Wed, 29 May 2019 03:28:51 -0000

Following Watson's example, I want to nominate OPAQUE as candidate for an
*augmented* PAKE in the CFRG selection process.

The protocol is defined in quite high level in
https://datatracker.ietf.org/doc/draft-krawczyk-cfrg-opaque/

A benefit of OPAQUE is its modular design that allows to more easily
integrate it with different protocols, such as TLS and IKE. In particular,
the draft  includes a discussion of how to integrate it with TLS. A more
detailed treatment of such integration appears in
https://tools.ietf.org/html/draft-sullivan-tls-opaque-00

A  more detailed and precise specification, including a standalone
specification, will be developed in future versions taking into account
CFRG feedback.

Hugo