RE: QUIC - Our schedule and scope

Lucas Pardue <Lucas.Pardue@bbc.co.uk> Fri, 27 October 2017 16:37 UTC

Return-Path: <Lucas.Pardue@bbc.co.uk>
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 91AFC13F3FF for <quic@ietfa.amsl.com>; Fri, 27 Oct 2017 09:37:03 -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, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 YF8IRUDZFTy9 for <quic@ietfa.amsl.com>; Fri, 27 Oct 2017 09:36:55 -0700 (PDT)
Received: from mailout1.telhc.bbc.co.uk (mailout1.telhc.bbc.co.uk [132.185.161.180]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3C2F133047 for <quic@ietf.org>; Fri, 27 Oct 2017 09:36:54 -0700 (PDT)
Received: from BGB01XI1005.national.core.bbc.co.uk ([10.184.50.55]) by mailout1.telhc.bbc.co.uk (8.15.2/8.15.2) with ESMTP id v9RGaqMu025601; Fri, 27 Oct 2017 17:36:52 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1005.national.core.bbc.co.uk ([10.184.50.55]) with mapi id 14.03.0361.001; Fri, 27 Oct 2017 17:36:52 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Mark Nottingham <mnot@mnot.net>, QUIC WG <quic@ietf.org>
CC: Lars Eggert <lars@netapp.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Subject: RE: QUIC - Our schedule and scope
Thread-Topic: QUIC - Our schedule and scope
Thread-Index: AQHTTuygoRyfQK5nH0aqrxlKAhFp4aL34mwg
Date: Fri, 27 Oct 2017 16:36:51 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BA7361D@bgb01xud1012>
References: <BCAD8B83-11F7-4D4A-B7B3-FCBF8B45CBB4@mnot.net>
In-Reply-To: <BCAD8B83-11F7-4D4A-B7B3-FCBF8B45CBB4@mnot.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.161.212]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-11.0.0.4255-8.100.1062-23422.000
x-tm-as-result: No--19.238400-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Leivqc-Ju21f4BcryWzWXspeFqM>
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 16:37:03 -0000

Hi Mark,

> Our charter instructs us to deliver the "core" four documents in March 2018,
> five months away.
<snip>
> To address this, we think two things are necessary:
>
> 1) Our Milestone for delivering the "core" QUIC documents (plus applicability
> and manageability statements) to the IESG should be moved to December
> 2018, with the understanding that this is a deadline we intend to meet.
>
> 2) V1 of QUIC should *only* address the use case of HTTP.
>
> This has a few implications:
>
> * Proposals for changes that are not realistically achievable in the timeline of
> #1 will be rejected on that basis, because the WG has consensus that the
> schedule is important.
>
> * V1 will need to document the "invariants" of QUIC -- i.e., the parts on the
> wire that will not change -- to allow other use cases to be addressed by V2
> and beyond.
>
> * Discussion of anything else (including issues, drafts, proposals) that doesn't
> address the needs of HTTP-over-QUIC will be postponed until after V1 has
> shipped.
>

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?

Kind regards
Lucas


-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------