IETF Logo Mail Archive

Re: QUIC - Our schedule and scope

Simon Pietro Romano <spromano@unina.it> Sun, 29 October 2017 07:01 UTC

Return-Path: <spromano@unina.it>
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 A0BB513F5E6 for <quic@ietfa.amsl.com>; Sun, 29 Oct 2017 00:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level:
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 AuppuSP0N25Z for <quic@ietfa.amsl.com>; Sun, 29 Oct 2017 00:01:38 -0700 (PDT)
Received: from unina.it (fmvip.unina.it [IPv6:2001:760:3403:ffff::7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6230D13F6CC for <quic@ietf.org>; Sun, 29 Oct 2017 00:01:38 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by leas1.unina.it with ESMTP id v9T71XBI002482-v9T71XBK002482 (version=TLSv1.0 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Oct 2017 08:01:33 +0100
Received: from [192.168.1.69] (93-44-59-94.ip95.fastwebnet.it [93.44.59.94]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id v9T71XrG015459 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Oct 2017 08:01:33 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
Subject: Re: QUIC - Our schedule and scope
From: Simon Pietro Romano <spromano@unina.it>
X-Mailer: iPhone Mail (15A432)
In-Reply-To: <49DC61C7-9E31-4049-84E3-112F129CBE50@mnot.net>
Date: Sun, 29 Oct 2017 08:01:32 +0100
Cc: Lucas Pardue <Lucas.Pardue@bbc.co.uk>, 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: <FAE9A7F7-C642-4AC5-B469-91BE7189F2F0@unina.it>
References: <BCAD8B83-11F7-4D4A-B7B3-FCBF8B45CBB4@mnot.net> <7CF7F94CB496BF4FAB1676F375F9666A3BA7361D@bgb01xud1012> <49DC61C7-9E31-4049-84E3-112F129CBE50@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/hTyqoaKLl6Ake1cZeTkqjU5TmEo>
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: Sun, 29 Oct 2017 07:01:41 -0000

The sad thing about multipath is that there have been people who have worked, more than one year ago, on implementing it in a v1-compliant way. Though, the group has never wanted to give multipath a real chance to survive and has always treated it as a “potential future extension”. This has been made so clear in the mailing list that we have stopped trying to push for it.

Simon


Inviato da iPhone

> Il giorno 28 ott 2017, alle ore 00:57, Mark Nottingham <mnot@mnot.net> ha scritto:
> 
> 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