Re: QUIC - Our schedule and scope

Mark Nottingham <mnot@mnot.net> Fri, 27 October 2017 22:55 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 312C91397F3 for <quic@ietfa.amsl.com>; Fri, 27 Oct 2017 15:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=Jf38bD3N; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=dvFmd75p
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 v8IY70Df2MHo for <quic@ietfa.amsl.com>; Fri, 27 Oct 2017 15:55:32 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D2C8139394 for <quic@ietf.org>; Fri, 27 Oct 2017 15:55:32 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id EA04720CB3; Fri, 27 Oct 2017 18:55:31 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Fri, 27 Oct 2017 18:55:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=vzelNtGkSrIi5DoiJboFNsFGAHK55 AS7uPSbBsPqI/U=; b=Jf38bD3NRlXDInDszXU/I5DJWrGUawVpfSJjm5ZpaqlqZ SbkT2ME9/VbnIirPQuoYp/EbGSZ4w84Sbf62aMuJHVd1FH+Qq7vEP0EBA26V0/Kt jjGrdRrdqlD7gxGe+D/la6o69nR0DA8C9aLsw/9JoAUqnYoBfurBealiLs5Be844 kghzUbJ6dufmAhFb6g3mGeEVl/a3GGs7zyGXwsFNdb5rF7vaG/qZqRQJmUJ6yk50 o3C5OflG4qlUoqI+UfI9EXGBeG9I/ToCM7mLbdlRZ+zUn56ah7CfBJ9jNp8fnaYS FKMBh28zZAR+mTCWoIzmymPufddta+N1YOXEwC6/Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=vzelNt GkSrIi5DoiJboFNsFGAHK55AS7uPSbBsPqI/U=; b=dvFmd75pBSUsG7VyGucuCV 7Wolg9oaWpxcldArlG+NIDizvDIhyd3Oxj953cxWkvXOyEEAypyIS3oZgq/l7dRq 05PIdV7ZLZC5sebzy5vD8amFCQK3d8JokSStLRs7Cr+bvnGIqv+Is7bIBKqk/Ybd Dd8Vij/j9vfRyEavzjD8RLFpoetXWAiCOc+jt509R7uovWt0SfgsVXt5JuNcvoZI j217a2XAIw28UFyTQ8vnszGDWaPd1sW+OTRftv3xrCS5e4YrH4aiNg/8c7WWwMs5 QT2q3T7enZ/mX7YvZ4VQzywcEmbmDdNK3Uu87QGMqyPyn6N4SZtgEzpYM/noPRgw ==
X-ME-Sender: <xms:Y7nzWVQTG2vHhUibbp5eQgy25S0nhLO3ewCDRIWzk8_jVbCZXxbfPA>
Received: from [192.168.1.18] (cpe-124-188-19-231.hdbq1.win.bigpond.net.au [124.188.19.231]) by mail.messagingengine.com (Postfix) with ESMTPA id 882917F96B; Fri, 27 Oct 2017 18:55:30 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\))
Subject: Re: QUIC - Our schedule and scope
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <17E462A6-FC87-47BA-8B31-88D47F8378E9@akamai.com>
Date: Sat, 28 Oct 2017 09:55:29 +1100
Cc: QUIC WG <quic@ietf.org>, Lars Eggert <lars@netapp.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B4934A8-310F-40DE-9F69-0E23AC49C15D@mnot.net>
References: <BCAD8B83-11F7-4D4A-B7B3-FCBF8B45CBB4@mnot.net> <CAOdDvNqdXLXEQff03t_YSLMpUpeT74E6XuAMh_C8GNiMM9f_Uw@mail.gmail.com> <17E462A6-FC87-47BA-8B31-88D47F8378E9@akamai.com>
To: "Salz, Rich" <rsalz@akamai.com>
X-Mailer: Apple Mail (2.3445.1.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/e6Qh7IHzchRB-fLBS13G8JN_OEU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2017 22:55:34 -0000

Hi Rich,

> On 28 Oct 2017, at 3:20 am, Salz, Rich <rsalz@akamai.com> wrote:
> 
> You might also want to consider what TLS 1.3 is going through and allow an escape hatch if you’ve got a good protocol but current Internet conditions prevent it from getting acceptably-wide deployment.  And then, the follow-on question: what *would* be an acceptable level of interference/blockage – 1, 5, 10%?

Doubtless we'll deal with that if and when it comes. 

Cheers,

--
Mark Nottingham   https://www.mnot.net/