Re: [quicwg/base-drafts] Can Initial/0-RTT CIDs safely be used for routing? (#2026)

Mike Bishop <notifications@github.com> Tue, 20 November 2018 20:58 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 0E516130DC6 for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 12:58:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.471
X-Spam-Level:
X-Spam-Status: No, score=-3.471 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, RCVD_IN_MSPIKE_H2=-0.001, 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 Qx-MTvDUI_c6 for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 12:58:19 -0800 (PST)
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 56C8D12785F for <quic-issues@ietf.org>; Tue, 20 Nov 2018 12:58:19 -0800 (PST)
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=tSCOA+e4iX/0H5UmzWldodFIM7Q=; b=M9jVYCPvd/EekHY/ 0UcGcUuFO/shgMOCDDCIDLuCl5PXfrteq4R/V956V/dVOy4l4gIeejA0BGmpHV1o 1lViJbvkVRNyw+GHAlj1T1hFD9fi1xyTkVkOF1JKm5H+uH7dCmOtYKDDpsH4rpS5 0K1Bf21vuICMoVsKC2QM5/0orlU=
Received: by filter0786p1las1.sendgrid.net with SMTP id filter0786p1las1-30956-5BF47569-F 2018-11-20 20:58:17.382274806 +0000 UTC m=+426979.794627970
Received: from github-lowworker-89d05ac.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0009p1iad2.sendgrid.net (SG) with ESMTP id mb6XpecmQdK6UOSX3_jUsg for <quic-issues@ietf.org>; Tue, 20 Nov 2018 20:58:17.314 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-89d05ac.cp1-iad.github.net (Postfix) with ESMTP id 3D94EAE0243 for <quic-issues@ietf.org>; Tue, 20 Nov 2018 12:58:17 -0800 (PST)
Date: Tue, 20 Nov 2018 20:58:17 +0000
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab0260c61dfbd01f672070fc7a4db98b1ac1a054b792cf00000001180c376992a169ce16d12586@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2026/440427008@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2026@github.com>
References: <quicwg/base-drafts/issues/2026@github.com>
Subject: Re: [quicwg/base-drafts] Can Initial/0-RTT CIDs safely be used for routing? (#2026)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bf475693c474_67283fefa28d45c41618a4"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2pefYZBgkXwieSyosemBfsWAHIQBbQOVIQHv RbXnW+UraLs21HM7fDCtEa8lS5YuDRuC9k984UFqQzpeDRmPLLB5ClYaC1OI6EI+Yo8MCJyNGpIHPj S7MEpIZ3L6UW/hKj4CKKnF4g9yP8Pc7WwGRzbAHJuf3vU2cY60rmzPgGLrqdtsRlRh++gNNTsEULWg A=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/rhWuDoZ8jLd9AfHWw7Fm3rpdLhg>
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, 20 Nov 2018 20:58:21 -0000

@mikkelfj, I presume you mean Retry.  The server can specify any CID in the Retry, but I'd expect the routing to be achieved by IP:port consistency throughout the handshake.

-- 
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/2026#issuecomment-440427008