Re: Invariants draft

Willy Tarreau <w@1wt.eu> Fri, 01 December 2017 06:25 UTC

Return-Path: <w@1wt.eu>
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 783BA12894A for <quic@ietfa.amsl.com>; Thu, 30 Nov 2017 22:25:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 8Foc4QB78wY2 for <quic@ietfa.amsl.com>; Thu, 30 Nov 2017 22:25:47 -0800 (PST)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id B46011243F3 for <quic@ietf.org>; Thu, 30 Nov 2017 22:25:45 -0800 (PST)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id vB16PdNW008303; Fri, 1 Dec 2017 07:25:39 +0100
Date: Fri, 01 Dec 2017 07:25:39 +0100
From: Willy Tarreau <w@1wt.eu>
To: Christian Huitema <huitema@huitema.net>
Cc: quic@ietf.org
Subject: Re: Invariants draft
Message-ID: <20171201062539.GA8275@1wt.eu>
References: <CABkgnnVr7jQ2=fFM+OOgk0-=Fseze8fT3xwWBOj-4CWTOtbq1Q@mail.gmail.com> <440a603c-2924-a260-c477-ecb42a84ec5c@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <440a603c-2924-a260-c477-ecb42a84ec5c@huitema.net>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jHBDSVxYvTbS6FJiOEKBwLx8nqQ>
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, 01 Dec 2017 06:25:48 -0000

On Thu, Nov 30, 2017 at 08:46:49PM -0800, Christian Huitema wrote:
> But at the same time, I am concerned with the tension
> between "focusing on extensibility" and "ensuring interoperability". At
> one end of the spectrum, we could define nothing but extensibility
> mechanisms, and let application developers define an application
> specific transport protocol. At an other end of the spectrum, we could
> rigidly specify a protocol, its formats, and its state machine. I do
> think that the working group has to strike somewhere in the middle, a
> well specified protocol that can be easily extended, but maybe not
> infinitely extensible.

I think this draft clearly leaves a *lot* of room for extensibility,
and defining invariants helps us (and future generations) decide when
a new protocol needs to be specified because it conflicts with the
definition of what was guaranteed to be invariant. It's normal to
reach an end with a protocol when new concerns need to be addressed
that were out of the initial scope. Here in short, as long as we can
use UDP with a few fixed bits and 64-bit connection IDs, we don't
need to define a new protocol.

I personally find it well balanced.

Regards,
Willy