IETF Logo Mail Archive

Re: [quicwg/base-drafts] Server's preferred address (#1251)

Mike Bishop <notifications@github.com> Mon, 02 April 2018 17:55 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 50B4D127010 for <quic-issues@ietfa.amsl.com>; Mon, 2 Apr 2018 10:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 tTGcaqOMjzAK for <quic-issues@ietfa.amsl.com>; Mon, 2 Apr 2018 10:55:08 -0700 (PDT)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 B318B126E64 for <quic-issues@ietf.org>; Mon, 2 Apr 2018 10:55:08 -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=a4e6vHi3Ix3mHJ9069hlZvqoB2U=; b=jWhotLCPM9nnVFPQ GhqhP9r9yQDz+YJDXWoYmcJnWLK8APKvY7sRh7Gi4A3v0FSzeggsWhyknBchKj+l 3CdkAIcsvWv7ceHstrJpTd5tVTbzXaH+kOM6PJIhoU6OJ1W5E/DYpfl6u6MX+z57 eGgXln8PeHCskzvHut20m7fe2KM=
Received: by filter1101p1mdw1.sendgrid.net with SMTP id filter1101p1mdw1-19166-5AC26E7B-23 2018-04-02 17:55:07.637347404 +0000 UTC
Received: from smtp.github.com (out-1.smtp.github.com [192.30.252.192]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id 8DyPrK13Sc2qGKQAndRXQg for <quic-issues@ietf.org>; Mon, 02 Apr 2018 17:55:07.639 +0000 (UTC)
Date: Mon, 02 Apr 2018 17:55:07 +0000
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba44a9f362ee6ae4bf586c0ea18fce066752fc13992cf0000000116da307b92a169ce126c34a9@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1251/c377993550@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1251@github.com>
References: <quicwg/base-drafts/pull/1251@github.com>
Subject: Re: [quicwg/base-drafts] Server's preferred address (#1251)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ac26e7b8c14f_485d3fc6ac43cf301939d6"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0rAgjtveiCwX3j2W5gbmdmFPdVho5eNEx32l 540wJiWjo/PYleQ1NWlUfISvuzGnC9rscuAWw1voKZSn/QxL9e8a5pvrZCMxlFyzbuUQlxduZT+Wy/ bOhOCYrQ3tKc/Jjaf/qsQjNQcCtDT7UnowD7W8Yv1mxe2DhvzVLPKMV4EkCX9XI2WNh4buAgPLKTek M=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/FGBmSHXYPWhCxf7X5IjFjoSCbUo>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 02 Apr 2018 17:55:11 -0000

For simplicity, I'm inclined to say it's the server's job to send a single working IP address to the client.  When we have a more complete server migration story, the server can just try multiple times / send multiple addresses.

Yes, just like in path validation, the server responds on the same address to the same address.

I don't see this as an attack, primarily because it's under the server's control.  The server could use a dedicated IP per cert to do handshakes, then hand off to a shared IP for existing connections.  No certs involved there.

-- 
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/1251#issuecomment-377993550

v2.23.0 | Report a Bug | By Email