IETF Logo Mail Archive

Re: [quicwg/base-drafts] Address validation for connection migration (#732)

Ryan Hamilton <notifications@github.com> Thu, 17 August 2017 19:28 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 0B8ED132640 for <quic-issues@ietfa.amsl.com>; Thu, 17 Aug 2017 12:28:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.595
X-Spam-Level:
X-Spam-Status: No, score=-0.595 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_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 l2GVcCu7I7A1 for <quic-issues@ietfa.amsl.com>; Thu, 17 Aug 2017 12:28:44 -0700 (PDT)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 81934132396 for <quic-issues@ietf.org>; Thu, 17 Aug 2017 12:28:44 -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=Cg4pPai2WlQefgSsbbl/PVzFfEE=; b=b2zWeCG4b7bFaack SDj6RsuxmvgeG2ulQ0Y0bqQYeLOSyImLWGZ/qX1xXJG5azPBvJmcfT2XBr4ydlV6 qyF4G3WMthpJKWCOKsThSvW84x7T/M1XSxXPLJKXlneRoTkF0MLpGZbSaMEe9M8u 5cX93uM/L/IATWgvY/SQ9v5iHgs=
Received: by filter0974p1mdw1.sendgrid.net with SMTP id filter0974p1mdw1-11719-5995EE5A-37 2017-08-17 19:28:26.568024399 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id myEJ-crXRIetC6U1ZiMgew for <quic-issues@ietf.org>; Thu, 17 Aug 2017 19:28:26.540 +0000 (UTC)
Date: Thu, 17 Aug 2017 19:28:26 +0000
From: Ryan Hamilton <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abaedad92b16d7d80ffa4c251a255a038763f5b35b92cf0000000115adb05a92a169ce0ee9dd49@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/732/c323170821@github.com>
In-Reply-To: <quicwg/base-drafts/pull/732@github.com>
References: <quicwg/base-drafts/pull/732@github.com>
Subject: Re: [quicwg/base-drafts] Address validation for connection migration (#732)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5995ee5a6dece_650f3f88e6607c383977f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: RyanAtGoogle
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1+i8FqzdI5ZUbC3YPILGZiyRsHARlRCeL1C3 VibKxLZqHcnOkJR9G87+cFwSHOnfO0en7ld1epdIq7PB/YN8J3q3Z5fBaXx90s5ok5CV3S4Eo9ptlG qKMR4F7Dtnz3KiP+BauEq/pwtjm/L7Lkjf+4Nc/e7SpYxcmtTt4dz4JNqD/iX/ON6rC8zy4/5f/4Ep s=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/EiTbFK9yQ2i6NoMWH6Vv80BVlcA>
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: Thu, 17 Aug 2017 19:28:46 -0000

It seems like sending a PING and waiting for an ACK of that packet would be roughly equivalent to sending a PING with a token and waiting to receive a PONG with that token. Would PING + ACK be sufficient? (I'm probably not thinking it through clearly) If not, can you elaborate what PING + PONG mitigates that PING + ACK does not? 

-- 
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/732#issuecomment-323170821

v2.43.4 | Report a Bug | By Email | System Status