Re: [TLS] TLS 1.2 Long-term Support Profile draft posted

Peter Gutmann <pgut001@cs.auckland.ac.nz> Fri, 18 March 2016 09:06 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B5D412D538 for <tls@ietfa.amsl.com>; Fri, 18 Mar 2016 02:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=auckland.ac.nz
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 eXWtkCVaUp8Q for <tls@ietfa.amsl.com>; Fri, 18 Mar 2016 02:06:04 -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 142E612D7A4 for <tls@ietf.org>; Fri, 18 Mar 2016 02:06:03 -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=1458291964; x=1489827964; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=zmxHfO98Zryva6wNHjp8TUO+yyQeYEhQIapk0CucxTM=; b=3dY1zyLxTsy8ePiRGODHk9uS8ftmImSTrhrQLoD6c7EomyFhvagftG3s kMX3RgSdHXdZ5CrfvAoiS6E3z8yAJ8+gVPC2pKB5CbB/WpJASISbjejMb l1HTx2qy8zwVo/2YsvOiKPhEug07VcT0SOCdMaGDaSMVRgUDC9hmATV/O qK6AouoFcb6rDtaLfZyAJAo7/9JITWgPp0ZmyTBPxR6fQ5oeuiwCg3JzO ViBMmV7gjbYw9SIxmtlemZzfHgMnY3bzPlyJfUvA30Nc+rp41gkfNPcAo 9SAcx3FZiu/qtA0hZCmuO79VbUPIZ2fvHCudUYVqJj6yguIKxeqXXIcax w==;
X-IronPort-AV: E=Sophos;i="5.24,354,1454929200"; d="scan'208";a="75065518"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 130.216.4.125 - Outgoing - Outgoing
Received: from uxchange10-fe3.uoa.auckland.ac.nz ([130.216.4.125]) by mx4-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 18 Mar 2016 22:05:50 +1300
Received: from UXCN10-TDC05.UoA.auckland.ac.nz ([169.254.9.241]) by uxchange10-fe3.UoA.auckland.ac.nz ([169.254.143.234]) with mapi id 14.03.0266.001; Fri, 18 Mar 2016 22:05:50 +1300
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Dave Garrett <davemgarrett@gmail.com>, "tls@ietf.org" <tls@ietf.org>
Thread-Topic: [TLS] TLS 1.2 Long-term Support Profile draft posted
Thread-Index: AdF/gGiJXC2ZI/lER3iVToFYg5p2egANbZiAAE/Mgtw=
Date: Fri, 18 Mar 2016 09:05:50 +0000
Message-ID: <9A043F3CF02CD34C8E74AC1594475C73F4C25EAB@uxcn10-tdc05.UoA.auckland.ac.nz>
References: <9A043F3CF02CD34C8E74AC1594475C73F4C2374E@uxcn10-tdc05.UoA.auckland.ac.nz>, <201603170400.36176.davemgarrett@gmail.com>
In-Reply-To: <201603170400.36176.davemgarrett@gmail.com>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.6.2.2]
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/Z19wJ3gNuYYDLSkjqEqvaWnjNWA>
Subject: Re: [TLS] TLS 1.2 Long-term Support Profile draft posted
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.17
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, 18 Mar 2016 09:06:05 -0000

Dave Garrett <davemgarrett@gmail.com>; writes:

I've already replied to the other parts in an earlier reply, leaving:

>The big glaring problem, however, in multiple places, are the statements that
>something is "implicit in TLS-LTS, there is no need to signal it" via its
>designated extension. No! These features MUST be implemented in full,
>according to their specifications, such that they will work fully with
>servers that support them but not this new LTS proposal. Skimping on this
>just makes this messy situation even messier, which is the opposite of what
>you're trying to do here.

Good point, I've changed the text to say that for TLS-LTS purposes you don't
need it, but you do if you need to interop with non-LTS servers/clients.

Peter.