Re: [TLS] WGLC for draft-ietf-tls-ticketrequests

"Christopher Wood" <caw@heapingbits.net> Thu, 14 November 2019 16:06 UTC

Return-Path: <caw@heapingbits.net>
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 23272120113 for <tls@ietfa.amsl.com>; Thu, 14 Nov 2019 08:06:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=heapingbits.net header.b=TBIL9Ohx; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Jubu1dTF
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 TCsvqjtBcMJ2 for <tls@ietfa.amsl.com>; Thu, 14 Nov 2019 08:05:58 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85E53120033 for <tls@ietf.org>; Thu, 14 Nov 2019 08:05:57 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id BFAA121B2C for <tls@ietf.org>; Thu, 14 Nov 2019 11:05:55 -0500 (EST)
Received: from imap4 ([10.202.2.54]) by compute6.internal (MEProxy); Thu, 14 Nov 2019 11:05:55 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=AUUMo5ewrv9WsXNgSu+we936igj90n1 ZFThVLl4Hudo=; b=TBIL9OhxTernvulEjP3WTwUH/aYouuiulnSA05QnVG5WqcJ kjmk1j7OxwCw+CcVcIO6yt4e04JKZeXXBtz9Dcp3DNZWxLoSn3cHe8wZkqvY9v7s hU2J8dSxRdrIQSiz/Wg96HP/Qr9CwOey07/en1hUHaQyit2LTi3MJmCnfOfcrL05 NAX98yw0SVdVuHJVpd1yuW/BJPs/A3mGyLSS856Te/ztKoTURgH3eq7fP5OXV75y ryTc5Tx1jGBE04M3IV8OWjwk08/Z08XSsFg4jn9Sn0rPHF/+w92QzkWRcSbOVlBX 3BGDFiswSEyUdKCxsn0lBsNJoMRj7RmDUzt3KZg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=AUUMo5 ewrv9WsXNgSu+we936igj90n1ZFThVLl4Hudo=; b=Jubu1dTFyIO8M2OynN9c5C rbROh/AsbOqqIfE1YGYDkssN/Q2MBr39ZzqxBp4qWAuiC2fMiVkLCSmgjKtwVz66 pywPlurIcaRbFe4U3irWZiCO3unnErP6uXGVmuFVw4h4zER+6Vz8nAACoVxbjPae x6WHyqIgfZFowA9ZpeXonhmgx2y9oqoT0Ux6D8ijwINeoTwgTiBuXsKyb7VZ1DSK hQyuz3V1bmomrMmHOwDy2EC9ktbTeWqCss6s5Vfpf7qSxxTotXiFdlU8YP44cPbt qYje+c78Wp2UAs3/MtmK0sqNfKx9Hvi23nBecVvgu+dNeHyvedKz7gt9i6oXqZmw ==
X-ME-Sender: <xms:Y3vNXXEx793rx5-kzQDeRB011GMNohZazatleMRJzHeIO-3OQYBCgA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeffedgkeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfvehhrhhishhtohhphhgvrhcuhghoohgufdcuoegtrgif sehhvggrphhinhhgsghithhsrdhnvghtqeenucffohhmrghinhepghhithhhuhgsrdgtoh hmpdhivghtfhdrohhrghenucfrrghrrghmpehmrghilhhfrhhomheptggrfieshhgvrghp ihhnghgsihhtshdrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:Y3vNXUTU0PailKikQ9AEOcxzDKHLu8IGyO3bjEIrDj-kB6rYgfmkkA> <xmx:Y3vNXUuXUGwveoe3Kv8bhBVtQyJDGk1OQNS1HzTi0C2xVW6MR8btuA> <xmx:Y3vNXaAhKmYvUb5tzZLpxoaJLr-NTGvBAaTERXtU6in3RyeJDwj0BQ> <xmx:Y3vNXc6M8EEbGkd_smYJ4m4mdJLQdgdBKSjFySKPmDCSVIer6k9w0w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 43A173C00A1; Thu, 14 Nov 2019 11:05:55 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-562-gfd0633a-fmstable-20191114v1
Mime-Version: 1.0
Message-Id: <caa6f6b4-537c-46bb-a04b-28d2b59f8ecd@www.fastmail.com>
In-Reply-To: <0469b84c-3009-427a-99ca-e7f6817f0b6c@www.fastmail.com>
References: <2FB1D8AD-2C22-4A09-B7AF-0EFD6F0DBACA@sn3rd.com> <0469b84c-3009-427a-99ca-e7f6817f0b6c@www.fastmail.com>
Date: Thu, 14 Nov 2019 08:05:34 -0800
From: "Christopher Wood" <caw@heapingbits.net>
To: "TLS@ietf.org" <tls@ietf.org>
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/GWGcZb8U3wn3agsjPU8p_59oFhg>
Subject: Re: [TLS] WGLC for draft-ietf-tls-ticketrequests
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 14 Nov 2019 16:06:00 -0000

On Tue, Nov 5, 2019, at 5:32 PM, Martin Thomson wrote:
> There was a lengthy discussion after the last time this was discussed.  
> Can I request that an editor (or a chair) summarize that discussion and 
> the resulting actions (if any)?  I was involved in that discussion, but 
> I don't see any changes from that.  I'm totally OK with publication 
> as-is, but I want to make sure that nothing got dropped.

The only comment that was not integrated was the desire to use the hint to express not only a count, but also a bit indicating whether or not clients will accept a ticket if the server needs to send one (e.g., if its STEK is about to rotate and any old tickets would expire). The authors did not incorporate that into the document since it added complexity and there didn't seem to be much support for it. 

> p.s., it might make sense to include some advisory text on 
> prioritization of tickets vs. application data.  I can see a naive 
> implementation of this seriously degrading application performance.  
> For instance, it doesn't take that many tickets to fill an early TCP 
> congestion window.

Sure, we can add that: https://github.com/tlswg/draft-ietf-tls-ticketrequest/issues/9

> p.p.s., yes, if you keep issuing last calls, I will keep finding new things.

:-)

Thanks,
Chris

> 
> On Wed, Nov 6, 2019, at 03:05, Sean Turner wrote:
> > All,
> > 
> > This is the working group last call for the "TLS Ticket Requests" draft 
> > available at 
> > https://datatracker.ietf.org/doc/draft-ietf-tls-ticketrequests/.  
> > Please review the document and send your comments to the list by 2359 
> > UTC on 19 November 2019.
> > 
> > Note the the GH repo for this draft can be found at:
> > https://github.com/tlswg/draft-ietf-tls-ticketrequest
> > 
> > Thanks - J&S
> > _______________________________________________
> > TLS mailing list
> > TLS@ietf.org
> > https://www.ietf.org/mailman/listinfo/tls
> >
> 
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>