Re: [quicwg/base-drafts] Define stateless CONNECTION_CLOSE (#3292)

Martin Thomson <> Wed, 11 December 2019 23:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 38D9A1200F4 for <>; Wed, 11 Dec 2019 15:44:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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_32=0.001, 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 X4B9CyzEu04Y for <>; Wed, 11 Dec 2019 15:44:55 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8FA781200B3 for <>; Wed, 11 Dec 2019 15:44:55 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id ACF8E1C0C4B for <>; Wed, 11 Dec 2019 15:44:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1576107894; bh=VdDZN+UEg/dlxDDGIcFEa8mBdyP4B9ZFl/poCMy3HeA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Fvzx3xaRAZx1CHclj8NF5v6+By7oG+YpnBuGYNJs8F7E+BONEhGslFRC1k9URA2Do DrUxeZJzCpO0SZidFkPtItVgA++kns94jVHOTVr4UB4Pua9LhBwZT3+pkrWIFwAHVA cX6IEfsUi3LjK79UslQxAP6I0HJiqu5BAKc2m5UQ=
Date: Wed, 11 Dec 2019 15:44:54 -0800
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3292/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Define stateless CONNECTION_CLOSE (#3292)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5df17f769d466_2a083fa0d26cd95c1233ba"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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: Wed, 11 Dec 2019 23:44:57 -0000

martinthomson commented on this pull request.

> @@ -5759,11 +5778,15 @@ During the creation of a connection, QUIC only provides protection against
 attack from off the network path.  All QUIC packets contain proof that the
 recipient saw a preceding packet from its peer.
-The first mechanism used is the source and destination connection IDs, which are
-required to match those set by a peer.  Except for an Initial and stateless
-reset packets, an endpoint only accepts packets that include a destination
-connection that matches a connection ID the endpoint previously chose.  This is
-the only protection offered for Version Negotiation packets.
+Addresses cannot change during the handshake, so endpoints can discard packets
+that are received on a different network path.
+The source and destination connection IDs are the primary means of protection

Yup.  I don't think that we have the concept of a "destination connection ID" separate from the field though, so I am now referring to the fields directly.

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