Re: [quicwg/base-drafts] Move and consolidate address validation (#1886)

janaiyengar <notifications@github.com> Tue, 23 October 2018 23:25 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 8899E130E97 for <quic-issues@ietfa.amsl.com>; Tue, 23 Oct 2018 16:25:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.47
X-Spam-Level:
X-Spam-Status: No, score=-3.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 PtQM7aq6M4iS for <quic-issues@ietfa.amsl.com>; Tue, 23 Oct 2018 16:25:37 -0700 (PDT)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC3A2130EAE for <quic-issues@ietf.org>; Tue, 23 Oct 2018 16:25:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=bpT7tSCO516m/qy252s71KDafDQ=; b=e+MnxUrUBQU+TYrv xkEKavI6+93XXY8f4uRtGRrMfwcexx/V+a/j3VNAcyheadKDpPioTQniLZtuqGf7 N2pok/ezagRZvJmuG7OayyA/qUemTpLvSW0NU5V1fJroykQ8WaLe+NGTC7SPkd4s 27Xq9Q5W464/JpD/GoThgDrGp1U=
Received: by filter1452p1mdw1.sendgrid.net with SMTP id filter1452p1mdw1-14757-5BCFADEF-5 2018-10-23 23:25:35.583595053 +0000 UTC m=+435716.641989208
Received: from github-lowworker-56a5eb2.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id 8SltBN14RdSqixmew1jPsg for <quic-issues@ietf.org>; Tue, 23 Oct 2018 23:25:35.536 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-56a5eb2.cp1-iad.github.net (Postfix) with ESMTP id 7F2B3C13D1 for <quic-issues@ietf.org>; Tue, 23 Oct 2018 16:25:35 -0700 (PDT)
Date: Tue, 23 Oct 2018 23:25:35 +0000
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbb08f7a1bb5d8859f4dd413edf75034e1f6869ba92cf0000000117e76fef92a169ce1628c016@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1886/review/167678067@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1886@github.com>
References: <quicwg/base-drafts/pull/1886@github.com>
Subject: Re: [quicwg/base-drafts] Move and consolidate address validation (#1886)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bcfadef7bd21_564f3fb9aaed45c45079e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak08YBFirrpNTecSZdPDhSj52OU9M8txRWtqtF jDHBQV2hz64rQQLAIJ2hwWNFC+QiIubGzJj11xrQlrpNl4UFEgAf899GWIuZEGsAA976k1EQaNCyML B+/hfkl5Tdt7ZSEMLa6CFXk9oMFt25365iYqebqzToKC4TD3CgHuVREesBOa2eCaeZxflBquaUo+ok U=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/aMU_MD2MitxU0SVDTG4C0zeAITc>
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, 23 Oct 2018 23:25:51 -0000

janaiyengar commented on this pull request.



> +QUIC uses token-based address validation during connection establishment.  Any
+time the server wishes to validate a client address, it provides the client with
+a token.  As long as it is not possible for an attacker to generate a valid
+token for its address (see {{token-integrity}}) and the client is able to return
+that token, it proves to the server that it received the token.
+
+Upon receiving the client's Initial packet, the server can request address
+validation by sending a Retry packet ({{packet-retry}}) containing a token. This
+token is repeated by the client in an Initial packet after it receives the Retry
+packet.  In response to receiving a token in an Initial packet, a server can
+either abort the connection or permit it to proceed.
+
+
+A server can also use the Retry packet to defer the state and processing costs
+of connection establishment.  By giving the client a different connection ID to
+use, the connection might be routed to a different server instance, which have

```suggestion
use, a server can cause the connection to be routed to a server instance with
more resources available for new connections.
```

-- 
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/1886#pullrequestreview-167678067