IETF Logo Mail Archive

Re: [TLS] Fwd: New Version Notification for draft-whyte-qsh-tls13-01.txt

Peter Gutmann <pgut001@cs.auckland.ac.nz> Mon, 21 September 2015 04:52 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
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 A84E51A8785 for <tls@ietfa.amsl.com>; Sun, 20 Sep 2015 21:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 ofc1o9bS9DwN for <tls@ietfa.amsl.com>; Sun, 20 Sep 2015 21:52:08 -0700 (PDT)
Received: from mx4.auckland.ac.nz (mx4.auckland.ac.nz [130.216.125.248]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B7A21A8782 for <tls@ietf.org>; Sun, 20 Sep 2015 21:52:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1442811128; x=1474347128; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=aW1utlU/yI0LL7w8KAAtQm56SMAh3iTbUY+yDyJf8oo=; b=rYQ8vfMG+F4Wp5Qqs/jJdzoxuZXjwSO9WTw0rxXzvaIq/cRna20FaPoX 08sAUlXYENK0nLeLQGlh0Cp5BPQQVPkSOu6hD4N2i0B2NtwI6c44p+W2+ WWshdJkmEb7Gb3t0Zz+csESaP0Dxn+EwGMl3PsEhGam74q6zxWmrBIgER Rq7JEECfH5qB9rCwD52t6/b39RaRpptqropIcRp8c4QVqk4tE8CrF4oVy pX1yPs3UYYPcD4ENiK45e0TvCErfWXoc6iV9b0VKqzfL+S/uM1WpeKjVQ HFO9AFeP5Uovr+rBMy+QxR/fAM5wC9iCjsVWI5MvRqWQAAcsbXQ8ztFr3 g==;
X-IronPort-AV: E=Sophos;i="5.17,565,1437393600"; d="scan'208";a="43092665"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 130.216.4.106 - Outgoing - Outgoing
Received: from uxchange10-fe2.uoa.auckland.ac.nz ([130.216.4.106]) by mx4-int.auckland.ac.nz with ESMTP/TLS/AES128-SHA; 21 Sep 2015 16:52:05 +1200
Received: from UXCN10-5.UoA.auckland.ac.nz ([169.254.5.51]) by uxchange10-fe2.UoA.auckland.ac.nz ([130.216.4.106]) with mapi id 14.03.0174.001; Mon, 21 Sep 2015 16:52:05 +1200
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Geoffrey Keating <geoffk@geoffk.org>, William Whyte <wwhyte@securityinnovation.com>
Thread-Topic: [TLS] Fwd: New Version Notification for draft-whyte-qsh-tls13-01.txt
Thread-Index: AQHQ9CBX9PQg16Tx50axem0ddgumQp5GaipW
Date: Mon, 21 Sep 2015 04:52:04 +0000
Message-ID: <9A043F3CF02CD34C8E74AC1594475C73F4B184CC@uxcn10-5.UoA.auckland.ac.nz>
References: <20150921023216.17159.38513.idtracker@ietfa.amsl.com> <CACz1E9orLfuemj+gdJOW3=37WBHJxrYkxLidGkhY4+jo3G=p8w@mail.gmail.com>, <m2k2rk8mbz.fsf@localhost.localdomain>
In-Reply-To: <m2k2rk8mbz.fsf@localhost.localdomain>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/uxQ8Skftvld5DlQ-9YzU9y0JnaE>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Fwd: New Version Notification for draft-whyte-qsh-tls13-01.txt
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: Mon, 21 Sep 2015 04:52:13 -0000

Geoffrey Keating <geoffk@geoffk.org> writes:

>That would affect the initial client hello, which I think we're trying to
>keep backwards compatible.  It might be better to just define a rule like "if
>multiple extensions with the same number are present, their values are
>concatenated".

A better one would be "if you're planning on introducing some new crypto
mechanism, make it one that will fit into the TLS framework".

Peter.

v2.23.0 | Report a Bug | By Email