Re: [quicwg/base-drafts] Describe PMTU probing that includes source connection ID for routing … (#2402)

MikkelFJ <> Tue, 05 February 2019 07:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B5DF7130E09 for <>; Mon, 4 Feb 2019 23:05:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -12.552
X-Spam-Status: No, score=-12.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 VjPO7_YMTdaD for <>; Mon, 4 Feb 2019 23:05:27 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 41BE7130DEC for <>; Mon, 4 Feb 2019 23:05:27 -0800 (PST)
Date: Mon, 04 Feb 2019 23:05:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1549350325; bh=KVpUg/kLQv+k+FaNaBYs1KC6Sepd8go9wBcGBpzAeW8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=dBvFXSEkPCHsu+Pb3JJQhJcmh7lEOCzoLODxk4dPdjFMr5gXgUx9xFemMbdrT5Ebj F9mCDN1iVS82H6z9eybPn2fQdTXgp5dJHeAb8ZpR18hw2JOR5N3NVs/4/Ifoy+dQwg ++HYkOAoLwSA8pgSN3CO6c1tja19R6CCZVMLbRKg=
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2402/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Describe PMTU probing that includes source connection ID for routing … (#2402)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5935b5b4de1_7e963f86c4cd45bc38766d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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: Tue, 05 Feb 2019 07:05:31 -0000

Another point, which is important at least to me:

The entire idea about not having long headers post 1-RTT, and to make a note of it, is to allow implementations to focus on short packets only for the reminder of the connection, and dropping all context about separate number spaces etc.. If that stops being the case, all the bootrapping mess comes back to haunt you.

I'd switch to different packet processor post handshake so there is no ACK special handling etc.

If you have a dedicated allowance for a probe packet, that is much easier to deal with because you know the context is the same is for the short headers.

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