Re: [quicwg/base-drafts] Composability of QUIC Extensions (#3332)

Igor Lubashev <> Mon, 13 January 2020 00:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 686DF120026 for <>; Sun, 12 Jan 2020 16:45:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id v_BIX4vgn9bE for <>; Sun, 12 Jan 2020 16:45:32 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B0BB8120013 for <>; Sun, 12 Jan 2020 16:45:32 -0800 (PST)
Date: Sun, 12 Jan 2020 16:45:31 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1578876331; bh=R12Ysb9YlEyk5BpbhhYVteNejsBA3NYreXN/KLth4DQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Sb8wTvI0ZtQ50CwbvHdkJFq7Ap8918GyYQP4X9pyfdfUKrCuox5fWLs+B7d0245l9 JbB5YFTTS+5O6OqFXeUKJveaBMQZ+KCaIQApw8cY+gi2PiCpHycnwmIg7rpzOL98I8 Y9BETEtT3FCybJ6aHqQROS9/ETir5M4jeqoxr9UE=
From: Igor Lubashev <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3332/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Composability of QUIC Extensions (#3332)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e1bbdabc4fdd_dc03fab238cd968110834"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 13 Jan 2020 00:45:34 -0000

I think there are two types of extensions we are discussing: extensions that add new fields and extensions that replace fields.

Extensions that add new fields can coexist easily by all extensions agreeing on a disambiguation principle.  For example, new fields associated with an extension with a smaller Transport Parameter come first.  It would be useful to agree on this and have all such extensions include a statement to this effect.

Extension that replace fields can be logically split into removing an existing field and adding new fields.  They can co-exist by removing existing fields and shifting the rest of the frame to the left, and adding new fields using the above-mentioned principle (in TP number order).

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: