IETF Logo Mail Archive

Re: QUIC - Our schedule and scope

Mark Nottingham <mnot@mnot.net> Fri, 27 October 2017 22:57 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 1715E1397F3 for <quic@ietfa.amsl.com>; Fri, 27 Oct 2017 15:57:37 -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=CUxKLPkJ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ACb5WSbT
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 5Qs_zjNAe_bn for <quic@ietfa.amsl.com>; Fri, 27 Oct 2017 15:57:35 -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 82DB1139394 for <quic@ietf.org>; Fri, 27 Oct 2017 15:57:35 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id E068C20B60; Fri, 27 Oct 2017 18:57:34 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Fri, 27 Oct 2017 18:57:34 -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=3ORuFrACHCR3tGRb3i85h8YTWdvxY jOO6A1EABAKyWo=; b=CUxKLPkJdc0l/xinnDXiQFBvHN8l11VSExZyBQdr8UldZ Q7n/bq38utnswe4/EVIzGfTLY2DA/llTmZAgs1j5B3pgEo/TyuuITQjPCFCvbsku 9v1//Y46ODzrjxHPs7AYKQlZHQJ3zMao5St7q+a9LoRPDnUwQAHJT+B09Z1DUMOv 5Y5EMZytG3e2DT5jPapBPGtshnk9cXLCLi06S2EzBbJa+MbdAyFJMWPdw6DmrTQN WuhDzI+NfafRl9G0/maeMXsOx8gJMetVpa096lk+M0AXiOxWIyRhSZFT7ENSV1O6 tQJzgSQf/m4y6LsirNCWRN0Sxv7IxcRjvOntGn5gA==
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=3ORuFr ACHCR3tGRb3i85h8YTWdvxYjOO6A1EABAKyWo=; b=ACb5WSbTX3TyU39/uNNXUD IXgI0B+KiwbInBE0PAhd1OznT4Cvjb1kO4yibv5QiEp7M3U6OIecar0h1v8FzeZl Rrh7WSu3neI3EPflTI/xLIm3npIEzf0YPLU5NbvXfGp5lpSVHYMlSEaV236LlMNp hREScaSqvGBQegUir6J9GUQq1kYxKnZiO0rzEmOODxpoEXV3hNQs27EYdtnj8bR+ MWcpFaAj+lsRkCG4O5A+p0Wk4JzxhhorZoB8CznhMfv3YENiQ5SlVJtbbFTj887f gBH5G3mQyr5/uZrTJiVdeP/MjDuOG8SUW9w3DuV8jeBlzPAXoRvq8khuENq+lMAw ==
X-ME-Sender: <xms:3rnzWdIhU48zI_VD80tzu2XWTBj_av8r8GB05aiFUxUfJs05G5Y1_A>
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 7C71A7E13B; Fri, 27 Oct 2017 18:57:33 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
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: <7CF7F94CB496BF4FAB1676F375F9666A3BA7361D@bgb01xud1012>
Date: Sat, 28 Oct 2017 09:57:30 +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: <49DC61C7-9E31-4049-84E3-112F129CBE50@mnot.net>
References: <BCAD8B83-11F7-4D4A-B7B3-FCBF8B45CBB4@mnot.net> <7CF7F94CB496BF4FAB1676F375F9666A3BA7361D@bgb01xud1012>
To: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
X-Mailer: Apple Mail (2.3445.1.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fEe_xYxg14ODwcphYmGRMzt4_Pc>
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:57:37 -0000

Hi Lucas,


> On 28 Oct 2017, at 3:36 am, Lucas Pardue <Lucas.Pardue@bbc.co.uk> wrote:
> 
> To date, I've tried to avoid mentioning Multipath on list and bring it up now only as it relates to the WG Charter Milestones.
> 
> Can you be more explicit on how your proposals affect the current Multipath extension document dates? I could infer that the proposed changes to the core docs are independent of the extension doc, or more realistically the rescheduling also punts Multipath off another ~6 months (minimum) or until QUIC V2. What is more aligned with your current thinking?

I think multipath would remain a post-V1 activity, which implies that the dates would be pushed out.

Cheers,

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

v2.23.0 | Report a Bug | By Email