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

Igor Lubashev <> Thu, 28 February 2019 18:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7A5911271FF for <>; Thu, 28 Feb 2019 10:38:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Status: No, score=-6.597 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_28=1.404, 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 b2a-yBkozJwj for <>; Thu, 28 Feb 2019 10:38:01 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B7B481200ED for <>; Thu, 28 Feb 2019 10:38:01 -0800 (PST)
Date: Thu, 28 Feb 2019 10:38:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1551379080; bh=bR5U+ttszX4Pnlt5n9qBHLPJ7ib05x83+GZX2um1blI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=F7is2Cao+FqCz7WkxSVteAreVUgvDD6AGdUSMHKlUai3KnYafeCzJrKxTheg8/N4y z4FLwQNe4VTztRlZx3KvGnZPtwznrRSHtOikdU4Q/JoTdK0e6qOieafKLdj1NhQHT+ cywBg/YACPYCwX44Y9kwLXn5WX9d/xdW7VN1sy7A=
From: Igor Lubashev <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2402/review/>
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_5c782a88977af_5cbd3fa6346d45c4446667"; 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: Thu, 28 Feb 2019 18:38:03 -0000

igorlord commented on this pull request.

> @@ -2670,9 +2670,10 @@ complete.  Though the values of some fields in the packet header might be
 redundant, no fields are omitted.  The receiver of coalesced QUIC packets MUST
 individually process each QUIC packet and separately acknowledge them, as if
 they were received as the payload of different UDP datagrams.  For example, if
-decryption fails (because the keys are not available or any other reason), the
-the receiver MAY either discard or buffer the packet for later processing and
-MUST attempt to process the remaining packets.
+decryption fails (because the keys are not available, the UDP datagram is a PMTU
+probe (see {{pmtu-probes-src-cid}}), or any other reason), the the receiver MAY

The new commit updates the text as requested / discussed.  Resolving this.

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