Date: Mon, 31 Dec 2018 01:25:07 -0800
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab9c1eb4f504e05446045084248a0da3303f29ffb392cf000000011841a27392a169ce177f0208@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2259/450624307@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2259@github.com>
References: <quicwg/base-drafts/issues/2259@github.com>
Subject: Re: [quicwg/base-drafts] amplification attack using Retry and VN
 triggered by coalesced Initial packets (#2259)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c29e073141e4_40383fd72d8d45c0118533f";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/5X9O9Rol1pT_Xgdk8IUY0vTA1Fo>


----==_mimepart_5c29e073141e4_40383fd72d8d45c0118533f
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

@kazuho We already have a MUST requirement for coalesced packets:
> Senders MUST NOT coalesce QUIC packets for different connections into a single UDP datagram. Receivers SHOULD ignore any subsequent packets with a different Destination Connection ID than the first packet in the datagram.

Both requirements cannot be enforced in the sense that the connection is closed. However, they are enforced in the sense that the incorrect packets are dropped, so there's no motivation whatsoever for an endpoint to misbehave.

-- 
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/issues/2259#issuecomment-450624307
----==_mimepart_5c29e073141e4_40383fd72d8d45c0118533f
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p><a class=3D"user-mention" data-hovercard-type=3D"user" data-hovercard-=
url=3D"/hovercards?user_id=3D41567" data-octo-click=3D"hovercard-link-cli=
ck" data-octo-dimensions=3D"link_type:self" href=3D"https://github.com/ka=
zuho">@kazuho</a> We already have a MUST requirement for coalesced packet=
s:</p>
<blockquote>
<p>Senders MUST NOT coalesce QUIC packets for different connections into =
a single UDP datagram. Receivers SHOULD ignore any subsequent packets wit=
h a different Destination Connection ID than the first packet in the data=
gram.</p>
</blockquote>
<p>Both requirements cannot be enforced in the sense that the connection =
is closed. However, they are enforced in the sense that the incorrect pac=
kets are dropped, so there's no motivation whatsoever for an endpoint to =
misbehave.</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/issues/2259#issuecomment-450624307">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkqyXA=
escXyFIufamyt9ElQoggYyQ1ks5u-dfzgaJpZM4Zh5Ox">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq4lsUhR3NkhsXAjfxrIO3wRP=
dYjiks5u-dfzgaJpZM4Zh5Ox.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://github.githubassets.com/images/email/message_cards/header.png","avata=
r_image_url":"https://github.githubassets.com/images/email/message_cards/=
avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/q=
uicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@=
marten-seemann in #2259: @kazuho We already have a MUST requirement for c=
oalesced packets:\r\n\u003e Senders MUST NOT coalesce QUIC packets for di=
fferent connections into a single UDP datagram. Receivers SHOULD ignore a=
ny subsequent packets with a different Destination Connection ID than the=
 first packet in the datagram.\r\n\r\nBoth requirements cannot be enforce=
d in the sense that the connection is closed. However, they are enforced =
in the sense that the incorrect packets are dropped, so there's no motiva=
tion whatsoever for an endpoint to misbehave."}],"action":{"name":"View I=
ssue","url":"https://github.com/quicwg/base-drafts/issues/2259#issuecomme=
nt-450624307"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2259#issuecomment=
-450624307",
"url": "https://github.com/quicwg/base-drafts/issues/2259#issuecomment-45=
0624307",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c29e073141e4_40383fd72d8d45c0118533f--