Re: [quicwg/base-drafts] Long Header Packets and Routing Connection IDs (#2834)

Nick Banks <notifications@github.com> Sun, 23 June 2019 16:23 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04C17120018 for <quic-issues@ietfa.amsl.com>; Sun, 23 Jun 2019 09:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.605
X-Spam-Level:
X-Spam-Status: No, score=-6.605 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-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 Uxhc7Y6awJNS for <quic-issues@ietfa.amsl.com>; Sun, 23 Jun 2019 09:23:02 -0700 (PDT)
Received: from out-21.smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51DDB1200D8 for <quic-issues@ietf.org>; Sun, 23 Jun 2019 09:23:02 -0700 (PDT)
Date: Sun, 23 Jun 2019 09:23:01 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1561306981; bh=lDjkyL4rPq6BcUYkfN4iGu/XTUmHUI3NVg+/JmDFjas=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mm85tBoTvI31W0q0wtvPc5jSjB5avMvIV/2LeB7UoWL37lgCI60FbKL1Jj7rrii3O H02k6aSnzFFq29dVO/76KRL/L3Cg+Jwu7oks1xHMUD6NJbY32TImRa4PBF9QaLUpKG /4MPxqglu0js2fcCI3qscLtTLJYSR1tj68+V76SQ=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2O5UURUPE2NWNXPX53DTM6LEVBNHHBWZGHNE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2834/504766651@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2834@github.com>
References: <quicwg/base-drafts/issues/2834@github.com>
Subject: Re: [quicwg/base-drafts] Long Header Packets and Routing Connection IDs (#2834)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d0fa765588b_1f423fe0352cd968577137"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/3yumUd6jicBhVHJ5iYg1cE4tBWo>
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: Sun, 23 Jun 2019 16:23:05 -0000

@mikkelfj currently, when processing a LH Initial packet, from just the packet header, the LB cannot determine how to route the packet, if it has two different sets of logic: one for client chosen CIDs and one for server chosen CIDs.

Instead of waiting until short header packets to change the CID, you could wait until Handshake packets, but I don't see how this makes things better. I don't understand your statement:

> It would also allow a client to decide where state is managed during a handshake, to a degree, which opens to an attack.

The whole point here is that you want to route all long header packets to the same place. Why would you route the initial packets one place, and then handshake packets somewhere else? If you didn't like where they went in the first place, don't route them 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/issues/2834#issuecomment-504766651