[quicwg/base-drafts] Preferred address text is confusing (#2146)

ekr <notifications@github.com> Thu, 13 December 2018 19:03 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A8A1E130E33 for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 11:03:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.459
X-Spam-Status: No, score=-9.459 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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_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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id KCJvs6cOhcDi for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 11:03:53 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CD4A130E2E for <quic-issues@ietf.org>; Thu, 13 Dec 2018 11:03:53 -0800 (PST)
Date: Thu, 13 Dec 2018 11:03:52 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544727832; bh=rHD5AQWjcEO+wpipKDN/J62sD6tuNDRP0/9kB8V23Ts=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=f1kKzio+wmYqpU2STJHRseVO8KZwaSEMyTQqIj/9+sFvHp8RezUQQp83Sud4Y/aBg 1VyGJXoqC3j8PcjmfTUgdE7NEGk7pjsDf8q5NHTQQj6ikouOAJEihneuqmBKXUZbBc xbNwzR8ay4F155cQgQ7vUBt5X09fb2D9trrL58vM=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abdcfed805392fe3549931aa19ddcf5cd2c8daefe592cf00000001182a6f1892a169ce174b625c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2146@github.com>
Subject: [quicwg/base-drafts] Preferred address text is confusing (#2146)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12ad181b6b7_16533fe68aad45c01447f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/ZRjis2P_KH0F8xqVn1ZZhtnzG1c>
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: Thu, 13 Dec 2018 19:04:06 -0000

The following text is kind of hard to track:

```A server might receive a packet addressed to its preferred IP address at any
time after it accepts a connection.  If this packet contains a PATH_CHALLENGE
frame, the server sends a PATH_RESPONSE frame as per {{migrate-validate}}.  The
server MAY send other non-probing frames from its preferred address, but MUST
continue sending all probing packets from its original IP address.

The server SHOULD also initiate path validation of the client using its
preferred address and the address from which it received the client probe.  This
helps to guard against spurious migration initiated by an attacker.

I'm not really following what's going on here. The server knows that it has two addresses and it wants to use its preferred address. Why does it have to probe from its preferred address. Also, I don't understand how these two paragraphs work together. The first one says you have to send probing packets from your original address but the second paragraph tells you to probe from the preferrd address.

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