IETF Logo Mail Archive

Re: [TLS] Extensions "supported_groups" and "key_share" in TLS 1.3

Xuelei Fan <xuelei.fan@vimino.com> Fri, 27 November 2015 02:12 UTC

Return-Path: <xuelei.fan@vimino.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E8AA1B30A9 for <tls@ietfa.amsl.com>; Thu, 26 Nov 2015 18:12:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 rAEB6gLrLgOh for <tls@ietfa.amsl.com>; Thu, 26 Nov 2015 18:12:15 -0800 (PST)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (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 5E1F71B30A6 for <tls@ietf.org>; Thu, 26 Nov 2015 18:12:15 -0800 (PST)
Received: by obbnk6 with SMTP id nk6so73021805obb.2 for <tls@ietf.org>; Thu, 26 Nov 2015 18:12:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vimino-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TfHegkR0Wd/spg8aTbHd8G6+L4MBK8CYXLAw/Y9T71A=; b=EXLrkGk5UI/jWSi0bIfmx00ECaLvj7HLM6zZjScqwnGQ6ttjLt33lFYIwgxope2PBc T8g2lhsIq7wukpUXh/knFuXtkXkJqM22IbMWcaIPs6FAHF4q+0oB2/TiBGsjpSbn6pvf swKT0NHSYBC/j0QH0Pf2nhdEveL4v4qd+TXYGGnpRfOnePlItiWGsusxS3EO2xiTMk/T whPHrMLLkXGOH7vhmnlhP7xq04CIgWaTFfvNs2yhMDdrltFt/oZywZP4Bq4QULnY9Kxi BjKAPh5fcFfc3FFpugAwF5rfE8YJRoQ0EBAWJpQdxmD5t1nGQKWQUocDvpo/IqV/+96l j6Fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=TfHegkR0Wd/spg8aTbHd8G6+L4MBK8CYXLAw/Y9T71A=; b=Q1QieUK0nqhh0CZWDL1/VJxSrd8Wrt4s9O/cUEqAs0aLOzjj0GUy6+MRwsh4cDP+xZ 300dZZ1GSUPMnp7eiS3xjfYrxyoEqyj0W0bfnVww97Y/HWHZahuzimnVmB/PXQnNqVCQ uYpgblLohr2FD3HNIrAzVQEIqrZz8FlClvynFbh6sBHWKB/Mouv/ocSZBQox3ROM3Tjl Dd44e2HBDNzrPdIqHA9RtgQiU1D9WWGNWUz3vQkw3bhqdRHxmR+UpDhIoiyx02N+m42R OdxiaHPvhYXky+ASsqLlAIcss/SYXhxpOvhHoMhnh5me7NXGbJzgXxXMwbrW0mPBTHg/ gV4A==
X-Gm-Message-State: ALoCoQnv6MnJ1kYOQdnHyrU2p1cvFkI+vi41KCte/iWRb+BO068zIe7uyQTrmfY2BtuTrVsIVCKp
MIME-Version: 1.0
X-Received: by 10.60.65.170 with SMTP id y10mr15774877oes.36.1448590334768; Thu, 26 Nov 2015 18:12:14 -0800 (PST)
Received: by 10.76.171.103 with HTTP; Thu, 26 Nov 2015 18:12:14 -0800 (PST)
X-Originating-IP: [148.87.19.218]
In-Reply-To: <CAAgBOht9egOhCKWb6LKeOraH-Dd8-bfNYf4kgMiK_unwZPASkg@mail.gmail.com>
References: <CAAgBOhuOPB=jxO=WWHmy_y7ARY5qfdK2x4xC9t-Z-vn0UU5Paw@mail.gmail.com> <20151126191525.GB3728@LK-Perkele-V2.elisa-laajakaista.fi> <CAAgBOhvRY+TPKb-Bwtpm_uGKJwJyaY7pDZfd38MrucOhSC_oEg@mail.gmail.com> <201511262039.01452.davemgarrett@gmail.com> <CAAgBOht9egOhCKWb6LKeOraH-Dd8-bfNYf4kgMiK_unwZPASkg@mail.gmail.com>
Date: Fri, 27 Nov 2015 10:12:14 +0800
Message-ID: <CAAgBOhus3fr5wwPYVFT4iid53KQPcruS+jcQks_chstUtA3sWA@mail.gmail.com>
From: Xuelei Fan <xuelei.fan@vimino.com>
To: Dave Garrett <davemgarrett@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c21194544db405257c38a8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/DxrUVETdO437xVduhA3Fms5FUuE>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Extensions "supported_groups" and "key_share" in TLS 1.3
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Nov 2015 02:12:16 -0000

On Fri, Nov 27, 2015 at 9:48 AM, Xuelei Fan <xuelei.fan@vimino.com> wrote:

>
>
> > I think, key_share is ordered too.  If considering both key_share and
>> > supported_groups together, looks like there are two options
>> [...]
>>
>> Yes, I addressed the conflict of priorities in one of my PRs, but it's on
>> my todo list to rewrite it as ekr noted a few parts that needed changing.
>> We agreed on simply making the two orders be required to be the same,
>> though at "SHOULD"-level requirement. Those that have them differ will be
>> dealt with at the implementations' discretion.
>>
>> Requiring the two order the same would triage order checking.  It may be
> easier that the key_share does not define the order.
>
I may miss something.  Can key_share offers two shares for the same group?
For example, two DH public values (dh_Y) for the ffdhe2048?  If yes, the
key_share order is necessary.  Otherwise, I think it is more simple to
remove the order requirement of shares.

Thanks,
Xuelei

v2.23.0 | Report a Bug | By Email