Re: Composability of extensions (was: Re: Preparing for discussion on what to do about the multipath extension milestone)

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Thu, 01 October 2020 13:33 UTC

Return-Path: <dtikhonov@litespeedtech.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 2861B3A1059 for <quic@ietfa.amsl.com>; Thu, 1 Oct 2020 06:33:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 gY7yzdSx9fZk for <quic@ietfa.amsl.com>; Thu, 1 Oct 2020 06:33:12 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 C0DEF3A103D for <quic@ietf.org>; Thu, 1 Oct 2020 06:33:12 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id n10so4334626qtv.3 for <quic@ietf.org>; Thu, 01 Oct 2020 06:33:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=F31AINxIRJhi6Sl9T9UNL/Q5dvaEocJ1qMVhvJhpvWA=; b=KsbeGkHlhDIjf8kM+iN+IQo9ddFfksWR+q1bLjVywuThkg1AWd/67pcOBCUtq7WKTD BOjSRHN/0ZbBci/qkYi2A5iG/Mf4kr4bvzXU//o4U36gGVIOoqvvW1aEG8yMoL5a8wHD Aoybe9japnL6KjwZ3ZydyvYnaqLrVoida00kYZjVgQMAhmga/m8N11MS3zDWgYNQiG/H J0qGMlo7yacbbI/D3LYdR1YWRv6ha/9ApL8yhlIBmB6T1KSi91OSm6z0OfaJzK6Ffn0d Y6uG89d7ytUUmXsgsXXmgoEV3R+9ilWV35W9g/Kks6R54jhNLKjR6Bl1viy6u/rfVdww 7VJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to; bh=F31AINxIRJhi6Sl9T9UNL/Q5dvaEocJ1qMVhvJhpvWA=; b=tnS4rX+VNyYcjeD1kOhHQuvNSaT5fZYuskOj1CHNQx1tADrtfB8X17bfmR5exEH7Mr gwShQDG9lpvbaGQDt9MEglllQxkM7SMaVVD1U1YwRX0t9OCUcltMvI6xskANGWXcHcTv hty2mcuNnhrpiY9uhN9mKmjbiQ7wYrTA0DOjLkVLv5Q7GGz6jlJnzd1zKqhQsNhy1Gtl 5PCd8XAqDpp4pEFTpbF/lCK5p45YwByop2eI7SI6ExCeKf8ldUvgA8XAvMZT2ChcXSyb wjpQ5Oz0lgJLLtfT2BvgOdVBfhfUa5SGDgNOItHRxZcvJYwVQq87mMmzIq4OMt6iLuP5 W9Qw==
X-Gm-Message-State: AOAM533ScUVDjN/SyK5tTOCWVPUpS3xnld6TXeb9oHDIKOgQteH2z/br Mo2mPgT5jJv61K3WsV6uf7nNClPPUnBUWA==
X-Google-Smtp-Source: ABdhPJx+mgU62zjo+BHcUAWfCru+ZD5PkAoTkZ7aBn7kL8DlthuCuvlw0MjFCTRhdVFT+XHRX9OXEA==
X-Received: by 2002:ac8:4e3c:: with SMTP id d28mr7816867qtw.40.1601559191330; Thu, 01 Oct 2020 06:33:11 -0700 (PDT)
Received: from okhta (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id d10sm5823517qko.32.2020.10.01.06.33.10 for <quic@ietf.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 01 Oct 2020 06:33:10 -0700 (PDT)
Date: Thu, 01 Oct 2020 09:33:08 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: quic@ietf.org
Subject: Re: Composability of extensions (was: Re: Preparing for discussion on what to do about the multipath extension milestone)
Message-ID: <20201001133308.GC192198@okhta>
Mail-Followup-To: quic@ietf.org
References: <F0A5E38D-4117-4729-BFF8-72D97CAA9908@eggert.org> <CAKKJt-e=+XLZhNWqaG9YSLTRqyQRvDc-dagUSkFwHOByFwZ++Q@mail.gmail.com> <78651438-2fce-ba67-4f44-4228bbc79a75@uclouvain.be> <CADdTf+hOACZ1x=d8SV-aX0f3vc+_fyqTziRqi5gi+nJgppaz8A@mail.gmail.com> <CAKcm_gNF=0gwrPt=Mr1P=dF_-wmXfz-OJkavFSDe1qrXFeMa4A@mail.gmail.com> <CALGR9oZF-m5fYxRjCfvQbqgSBv7djDgT3wU+MkBj+-gF4oVc6A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CALGR9oZF-m5fYxRjCfvQbqgSBv7djDgT3wU+MkBj+-gF4oVc6A@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fAvM6kOONLiA0oxRcfhoGnct0Uk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 01 Oct 2020 13:33:14 -0000

On Thu, Oct 01, 2020 at 02:07:34PM +0100, Lucas Pardue wrote:
> This reminded me of the comment I made on the mailing list in January [1]
> about how QUIC extensions would play together. There was some further
> discussion on GitHub [2] and in Zurich we decided to do nothing.
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

That's not quite accurate.  We decided to do nothing with the
understanding that figuring out extension composability and interplay
is the responsibility of newer extensions; they'd have to "watch out
for the dragons" [1].

  - Dmitri.

1. https://blog.litespeedtech.com/2020/02/11/quic-working-group-interim-zurich-recap/#extension-dragons