IETF Logo Mail Archive

Re: QUIC - Our schedule and scope

Ian Swett <ianswett@google.com> Tue, 31 October 2017 22:38 UTC

Return-Path: <ianswett@google.com>
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 E3ED513F788 for <quic@ietfa.amsl.com>; Tue, 31 Oct 2017 15:38:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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=google.com
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 F25_tUYEpvyA for <quic@ietfa.amsl.com>; Tue, 31 Oct 2017 15:38:35 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EB8613F769 for <quic@ietf.org>; Tue, 31 Oct 2017 15:38:35 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id 189so2231996iow.10 for <quic@ietf.org>; Tue, 31 Oct 2017 15:38:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kE4wq4tbh7ewgwx8oLqE3LDHVqv6222MDCcpsHNybNg=; b=RLe4SKuDpAEmu4rhmmGmw9NMQ6g9Kpd1FeEtcSMc92nPTgjpJrdLChs1VRHPg8jCbL DqmOEpSJ0QVO0PiSiuztsP+hug/VZNwKAakeu0odGf8vOoW4loQ7EIuAtGCnp9IsGE3W xHMvhTPApPClapErftF5+Cgw3553/E4gHDb8VVXkWu6mZVYGgoE1D7olFCGhULps0wSQ HRALHS5blD23+jUYZlL1ge7zyyEVrCjcZDlIK9PMAQaxkYi0zqczYqnrR5A4gOmobgev mYS/SJ30suTd+0d/dCyig/qYTdJ3+n/jvqnVqcTRvfFhCjl/SKriTTaZpN+hM6jGXLYZ MXvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kE4wq4tbh7ewgwx8oLqE3LDHVqv6222MDCcpsHNybNg=; b=Qmn0F31H1bEgg4BEpkoyEESLCpI8n/fTdhXTrjOUwf1KtieOaNPccGXUiMJFd/aVs3 i/P+sDSZuUwiFh1Ysfu2MdYUgw6wr/8dC4dH4Rg3jYPVxgZJlPNa5NJH7oVzjhJAqizt YhHFTQ0DT8rRD1vSQMQ+keUUJ2JaFvlt9kg74gkIoG1RappXZF76WyruC57kAz2I2YNN HiEs6MRvZs1QlHZH3oTDrMp4apjq1l1SAqZ8FScnS7P1hdnTVpoBMt0Kvavtvhezv7cn iHMvZ3A4jJWlqB/8xR3Dv0MKsIWlgv+0lQDCXNbFSjs29uGKFC5ypC8/rD8woLgCTRWu bXrg==
X-Gm-Message-State: AMCzsaXmM5CBIJy57BSQ/b6tWE8iYi79Q8znGcc2Ro6ZarHPtu62BvZ/ tmuQo6kvzs0ZYMl28FpvuoWqr0pMrN+6N+GzpDzEIg==
X-Google-Smtp-Source: ABhQp+S9gK8awTHiMG8InkScFCVvJRibW7IwJaRrNRa6GkgLjagcjA6E9qtG4ymguQ3fUkpDSzPVVCIhCXQMG7rTCdM=
X-Received: by 10.36.105.65 with SMTP id e62mr5249946itc.16.1509489514065; Tue, 31 Oct 2017 15:38:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.130.221 with HTTP; Tue, 31 Oct 2017 15:38:13 -0700 (PDT)
In-Reply-To: <CAKcm_gN7hNAgLf8kU5WLeLAeE-oOrE_do4VupmN5pnR1x=+FLw@mail.gmail.com>
References: <BCAD8B83-11F7-4D4A-B7B3-FCBF8B45CBB4@mnot.net> <6E58094ECC8D8344914996DAD28F1CCD828A1A@DGGEMM506-MBS.china.huawei.com> <D6EF62BE-F105-48DF-8BC6-EA55460C8252@netapp.com> <76E33E22-AFEC-481F-AF0A-99EBE92E645E@in-panik.de> <6E58094ECC8D8344914996DAD28F1CCD829F41@DGGEMM506-MBS.china.huawei.com> <CAM4esxQ18BOVbTC4qyg63+Y4LuUCtuC5V=a7+aLJzLVtfmjtdQ@mail.gmail.com> <9500F7AE-D042-43B6-A663-2307D8983A8C@netapp.com> <CAKcm_gN7hNAgLf8kU5WLeLAeE-oOrE_do4VupmN5pnR1x=+FLw@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Tue, 31 Oct 2017 18:38:13 -0400
Message-ID: <CAKcm_gOnK=FUnwrMixCKHRoUXG5pjMUsE8v_ZQGD9cPfKq-T9w@mail.gmail.com>
Subject: Re: QUIC - Our schedule and scope
To: "Eggert, Lars" <lars@netapp.com>
Cc: Martin Duke <martin.h.duke@gmail.com>, "Philipp S. Tiesel" <phils@in-panik.de>, Roni Even <roni.even@huawei.com>, QUIC WG <quic@ietf.org>, Mark Nottingham <mnot@mnot.net>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a1144528447de4c055cdf6a93"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/mYrMlme3_62zciFFLmLw1y49_gs>
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: Tue, 31 Oct 2017 22:38:37 -0000

I have created a new quicv2 label.  Anyone who created issues that are not
critical to resolve before QUIC v1 should tag the issue with the new QUICv2
tag.  Editors will also tag some issues as quicv2, but it'd be better if
the issue creators did so themselves.

As an example, my Message frame issue:
https://github.com/quicwg/base-drafts/issues/814

Thanks, Ian

On Tue, Oct 31, 2017 at 10:17 AM, Ian Swett <ianswett@google.com> wrote:

> Excellent suggestion Martin.
>
> Lars, what is the name of the new label?  I have at least one issue I'd
> like to tag as nonblocking(or ponies, or deferred...).
>
> On Mon, Oct 30, 2017 at 12:40 PM, Eggert, Lars <lars@netapp.com> wrote:
>
>> Hi
>>
>> On 2017-10-30, at 17:12, Martin Duke <martin.h.duke@gmail.com> wrote:
>>
>> One practical suggestion: can we create an issue category for "deferred"
>> stuff? There are probably a dozen or issues that are good ideas floating
>> around (a couple of mine) that we may not have time to address in 2018, but
>> shouldn't be lost. I would feel a lot better about my stuff being punted if
>> I knew the WG would formally consider it in v2.
>>
>>
>> that is a good suggestion, and I will add that tag in GitHub shortly.
>>
>> I would like to request that the proposers of such deferred issues bring
>> them back at an appropriate time, rather than putting this load on the
>> editors, who are already spread to thinly.
>>
>> Lars
>>
>
>

v2.23.0 | Report a Bug | By Email