IETF Logo Mail Archive

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

Kazuho Oku <notifications@github.com> Tue, 25 June 2019 21:55 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 BD116120152 for <quic-issues@ietfa.amsl.com>; Tue, 25 Jun 2019 14:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level:
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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_HELO_NONE=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 9MIT0JPXSVsp for <quic-issues@ietfa.amsl.com>; Tue, 25 Jun 2019 14:55:52 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 986AF120139 for <quic-issues@ietf.org>; Tue, 25 Jun 2019 14:55:52 -0700 (PDT)
Date: Tue, 25 Jun 2019 14:55:51 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1561499751; bh=9MQ8USCnodoxJJlaD0VdSohtDJ6MESCtC5rAcouiSwo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2C9jpmtwoxHxFcZgQqw3x4sjC6fTsOCYQpHfDcIO5cw4M4QrE753od0ZgemYlinqH RlztiB28cTV8+7AgzIWFFrkFYAx1w7rIVpOoWgvECbjDK/PlJmm7AOMuYZsBlaqd2L X+eCDH9oeEx+exHoQ0zrr3mkyMHnBUJAP+zBPSR4=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYRRPGGYUYTAVUTX753D7FOPEVBNHHBWZGHNE@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/505637716@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_5d1298678e607_78e53ff2328cd96c39588d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/KVeFi1LBp3PEEi9hHcOnOl2vvDE>
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, 25 Jun 2019 21:55:55 -0000

@ianswett 
> So the suggestion is: If there's a non-zero length SCID, use that. If SCID is 0 length, use 5-tuple?
> 
> Given you can't share a 5-tuple without using a SCID, that seems like a reasonable approach. If so, it should probably be written down in the QUIC LB draft?

Yes, that's the suggestion, and I think we should write it down somewhere.

I might even advocate for having it clarified in the transport draft, especially if we decide to disallow servers using the client's tuple to distinguish between the connections (#2844).

We have said that long header packets can be identified to which connections they belong, by looking at the 5-tuple. However, for clients to establish multiple QUIC connections in parallel on a single 5-tuple, the server _has_ to identify the connections using `5-tuple || client CID` as the key. It's crucial, but not obvious.

-- 
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-505637716

v2.23.0 | Report a Bug | By Email