Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 7AFF03A0844
 for <quic-issues@ietfa.amsl.com>; Mon,  8 Jun 2020 17:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Level: 
X-Spam-Status: No, score=-1.483 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, DKIM_VALID_EF=-0.1,
 HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1,
 RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
 header.d=github.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 tn2PHRWJQTEr for <quic-issues@ietfa.amsl.com>;
 Mon,  8 Jun 2020 17:43:22 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 35B453A0841
 for <quic-issues@ietf.org>; Mon,  8 Jun 2020 17:43:22 -0700 (PDT)
Received: from github-lowworker-c53a806.ac4-iad.github.net
 (github-lowworker-c53a806.ac4-iad.github.net [10.52.23.45])
 by smtp.github.com (Postfix) with ESMTP id E659A1C08EC
 for <quic-issues@ietf.org>; Mon,  8 Jun 2020 17:43:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1591663400;
 bh=iNMOP4YRRbTxaiLLybWPM7EmIhRDc706tP+CgsYAxQU=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=La4WrqCo7Rr/9LqIrUTnMCSB5zXpbSDZT2fVEv5/gpmUnpUNGmZBB2cVxdBBROJeD
 fTIMmdOQtZ8znPhLuqB63lhzkxWB9RwIwmWCs7WGpIGFFTvG3xHuItSzf01xt4OXt5
 miG31iXAaLDtY6p31i7UJ34b7NgPtAR+DlGf3YYI=
Date: Mon, 08 Jun 2020 17:43:20 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJKY53ZJJTZBGIXTEYWN45K6CREVBNHHCLIOW54@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3730/review/426713541@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3730@github.com>
References: <quicwg/base-drafts/pull/3730@github.com>
Subject: Re: [quicwg/base-drafts] Gorrys invariant nits (#3730)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5ededb28d7d4f_54aa3fc4838cd96c8067";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/uoCznlF9DhHTzo7c_8QnSqx-g_0>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG
 <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>,
 <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>,
 <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2020 00:43:24 -0000


----==_mimepart_5ededb28d7d4f_54aa3fc4838cd96c8067
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

@ianswett commented on this pull request.

Thanks for changing SCID/DCID to "Source Connection ID" and "Destination Connection ID", that seems like a good change.

> @@ -235,11 +240,11 @@ A connection ID is an opaque field of arbitrary length.
 
 The primary function of a connection ID is to ensure that changes in addressing
 at lower protocol layers (UDP, IP, and below) don't cause packets for a QUIC
-connection to be delivered to the wrong endpoint.  The connection ID is used by
-endpoints and the intermediaries that support them to ensure that each QUIC
-packet can be delivered to the correct instance of an endpoint.  At the
-endpoint, the connection ID is used to identify which QUIC connection the packet
-is intended for.
+connection to be delivered to the wrong transport endpoint.  The connection ID

What's a transport endpoint?  I don't recall us using that term elsewhere, so endpoint seems sufficient to me.  Or maybe we need another term for this case?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3730#pullrequestreview-426713541
----==_mimepart_5ededb28d7d4f_54aa3fc4838cd96c8067
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p></p>
<p><b>@ianswett</b> commented on this pull request.</p>

<p>Thanks for changing SCID/DCID to "Source Connection ID" and "Destination Connection ID", that seems like a good change.</p><hr>

<p>In <a href="https://github.com/quicwg/base-drafts/pull/3730#discussion_r437074788">draft-ietf-quic-invariants.md</a>:</p>
<pre style='color:#555'>&gt; @@ -235,11 +240,11 @@ A connection ID is an opaque field of arbitrary length.
 
 The primary function of a connection ID is to ensure that changes in addressing
 at lower protocol layers (UDP, IP, and below) don&#39;t cause packets for a QUIC
-connection to be delivered to the wrong endpoint.  The connection ID is used by
-endpoints and the intermediaries that support them to ensure that each QUIC
-packet can be delivered to the correct instance of an endpoint.  At the
-endpoint, the connection ID is used to identify which QUIC connection the packet
-is intended for.
+connection to be delivered to the wrong transport endpoint.  The connection ID
</pre>
<p>What's a transport endpoint?  I don't recall us using that term elsewhere, so endpoint seems sufficient to me.  Or maybe we need another term for this case?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/pull/3730#pullrequestreview-426713541">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK3ZQRMO74JHO7I3MX3RVWASRANCNFSM4NTJBL2A">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK6IE6M4DQIWO2QI2VDRVWASRA5CNFSM4NTJBL2KYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGODFXSDRI.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/pull/3730#pullrequestreview-426713541",
"url": "https://github.com/quicwg/base-drafts/pull/3730#pullrequestreview-426713541",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5ededb28d7d4f_54aa3fc4838cd96c8067--

