IETF Logo Mail Archive

Re: Call for Adoption: Invariants

Jana Iyengar <jri@google.com> Mon, 05 February 2018 20:15 UTC

Return-Path: <jri@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 539D5128954 for <quic@ietfa.amsl.com>; Mon, 5 Feb 2018 12:15:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 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, T_RP_MATCHES_RCVD=-0.01] 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 mhrS3a7k4l_6 for <quic@ietfa.amsl.com>; Mon, 5 Feb 2018 12:15:54 -0800 (PST)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (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 D566B127698 for <quic@ietf.org>; Mon, 5 Feb 2018 12:15:53 -0800 (PST)
Received: by mail-yw0-x231.google.com with SMTP id v139so19313663ywg.4 for <quic@ietf.org>; Mon, 05 Feb 2018 12:15:53 -0800 (PST)
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=BAy5MlnQSAOVFyAehuzyAWgLDuhaPjrWlcwMqNdP/fk=; b=hAn1fHV0Pn9PrtnIqkbi0/zkrlmgUKU+JDKZC9ie/AcUCZw6a1Q0nzwobNDZSuMq/L qXGu4oUafDGCDq5zYACig3yRhKZTW+B3asF0uaLZ8bw/GcdsaUncZhXgOXSJqVCvy/5a mFsiNpyVrOe2k8oLuHh6oUDh4hiUUznanZTUnXDhCXBeRDF2WpdjX/f6uJRepP2RMoDg DQ49Mn5wKll+/cEZ8w6xqOuC/O6+k5XNdyqtv/IdE1UPHsLaIHLhkjx7PJkVP6tFol5/ yZk709BKiaKmLDI5T3e3p0Eg1S/iyH7nU1nHTjB5Z0t84H7TC96nsrs0TF+xjuueyYfA pjww==
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=BAy5MlnQSAOVFyAehuzyAWgLDuhaPjrWlcwMqNdP/fk=; b=ujfTKiBB8w9AIVz4c1Iv3glanzaqV/benomYbLiSpaqdLI5zts+isk1nhl0He/5Gj1 I9dxSrKDn54+/d/J00BqfGpfvcR4RYu+EZcrhlL0XnxQdIan3uOd1rqz9GiepdRukeHz 1QgP360f+3tSNvW99Afyym49e9CVklsxkVX2tf3V1EF8G8tcw7slq58p3WPmGzOEltei vqI9Vx5QucmJzzPdHqP8vd3WKyELz2i6y7BjHLiuJ7r3BHj8WkcmBN8E+Fs9JghnOmAu HsnDz/8Y/LqTYzXHr2mqCkajy1HOwSdiNzBjkubaHyloSQvKv7/FR5Tv8IPZ9S17q8Z+ /V3w==
X-Gm-Message-State: APf1xPBHJABT4JPSQqxFpqWy0u6Wfe4Cce2+iacQnKMe7HZXgV/Nai8Q KUni7us9QV+efJXUOKZlEpuk4vsVWLkHzmIkDDYXYw==
X-Google-Smtp-Source: AH8x224aN5L4WX37rcUKhukonBtpIxlVV8cWqzXVp04oO4+9pEMYX6oWsQegYKwzAki8QeFxV+6LKUSOW6FioKvyAjw=
X-Received: by 10.37.74.68 with SMTP id x65mr8312yba.91.1517861752601; Mon, 05 Feb 2018 12:15:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.135.77 with HTTP; Mon, 5 Feb 2018 12:15:52 -0800 (PST)
In-Reply-To: <DB6PR10MB176682C4EC84D225E08C5A6BACFE0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
References: <C35C3AB6-F0FC-4D83-9C97-DD0B605A863F@mnot.net> <DB6PR10MB17667AAB19D4A9288FD5BAF3ACFE0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <FDFA0988-1FB4-4AFC-8958-1A6B16068FE5@trammell.ch> <MWHPR08MB2432F1CB1FBAFACD611D3913DAFE0@MWHPR08MB2432.namprd08.prod.outlook.com> <DB6PR10MB176682C4EC84D225E08C5A6BACFE0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
From: Jana Iyengar <jri@google.com>
Date: Mon, 05 Feb 2018 12:15:52 -0800
Message-ID: <CAGD1bZZ=QB8Jf2aQQ+M1Hg58rJ7ewSPgwOVAU+_k1pLhRMu5fw@mail.gmail.com>
Subject: Re: Call for Adoption: Invariants
To: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
Cc: Mike Bishop <mbishop@evequefou.be>, "Brian Trammell (IETF)" <ietf@trammell.ch>, Lars Eggert <lars@eggert.org>, Mark Nottingham <mnot@mnot.net>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="001a113e67bc95b78e05647cba5f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/durOg3b_2s4X2XNWgM6dugkmOsw>
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: Mon, 05 Feb 2018 20:15:56 -0000

+1 for adoption.

As Ian pointed out, once published, any changes to the invariants will be a
significant uphill task for active deployments. That's the entire point of
having these invariants. I would very much like to publish the invariants
ahead of the rest of the documents, so that active deployment of IETF-QUIC
can start, but that's a matter for a different thread, not this one.

On Mon, Feb 5, 2018 at 11:05 AM, Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com
> wrote:

> It could be called QUID ...
>
> ------------------------------
> *From:* Mike Bishop <mbishop@evequefou.be>
> *Sent:* Monday, February 5, 2018 8:00:53 PM
> *To:* Brian Trammell (IETF); Mikkel Fahnøe Jørgensen
> *Cc:* Lars Eggert; Mark Nottingham; QUIC WG
> *Subject:* RE: Call for Adoption: Invariants
>
> I support adoption.  The way to change the invariants will be to mint a
> new protocol, and not claim that your new protocol is a version of QUIC.
> If it happens to be startlingly similar, all well and good.
>
> -----Original Message-----
> From: QUIC [mailto:quic-bounces@ietf.org <quic-bounces@ietf.org>] On
> Behalf Of Brian Trammell (IETF)
> Sent: Monday, February 5, 2018 12:34 AM
> To: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
> Cc: Lars Eggert <lars@eggert.org>; Mark Nottingham <mnot@mnot.net>; QUIC
> WG <quic@ietf.org>
> Subject: Re: Call for Adoption: Invariants
>
> Hi, all,
>
> I support adoption of the invariants draft.
>
> > On 5 Feb 2018, at 08:51, Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
> wrote:
> >
> > Only concern is when it takes effect since it likely needs adjustments.
>
> I'd presume that invariants is published simultaneously with the version 1
> spec.
>
> > And perhaps a procedure to handle invariant changes since everything
> changes.
>
> Noted, though the point of declaring something an invariant is to say "the
> meaning of this part of the wire image, expressed as a bit offset, will
> never change". You can add constraints to the invariants, but if you think
> you might remove a constraint, then it's not an invariant by definition.
>
> Cheers,
>
> Brian
>
> > From: QUIC <quic-bounces@ietf.org> on behalf of Mark Nottingham <
> mnot@mnot.net>
> > Sent: Monday, February 5, 2018 7:07:45 AM
> > To: QUIC WG
> > Cc: Lars Eggert
> > Subject: Call for Adoption: Invariants
> >
> > At the Melbourne meeting, there was strong support for adopting Martin's
> invariants draft:
> >
> > https://tools.ietf.org/html/draft-thomson-quic-invariants-00
> >
> > Any objections / concerns about doing so? Unless we hear otherwise,
> we'll adopt at the end of the week.
> >
> > Cheers,
> >
> > --
> > Mark Nottingham   https://www.mnot.net/
>
>

v2.23.0 | Report a Bug | By Email