IETF Logo Mail Archive

Re: [quicwg/base-drafts] Client connection IDs are broken (#2844)

Martin Thomson <notifications@github.com> Tue, 23 July 2019 15:27 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 2C16F1203D1 for <quic-issues@ietfa.amsl.com>; Tue, 23 Jul 2019 08:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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_24=1.618, 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 8dLa08LGMIk5 for <quic-issues@ietfa.amsl.com>; Tue, 23 Jul 2019 08:27:32 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FB2C120426 for <quic-issues@ietf.org>; Tue, 23 Jul 2019 08:27:32 -0700 (PDT)
Date: Tue, 23 Jul 2019 08:27:31 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1563895651; bh=gfBQibY0N0O8xjyi0fFwZDxfkvhD4xUy6XWArKXeoVw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mKeXIBhqiHYaxEHVdUzEIqOK2Ds97Rh8KtG5QbhZc84x4Jb5HZEwkRSjdl/VrIsYB PKN8bfTheBwVsB6uvBFH+h3EDUl0TQ3I9aKjS/0ZuXkLmE3pRUyRyDvyvkUWmpeMcW yKU2jLSQE1vMz4XI0nHgD+sxoqTAdq2QhtohmOJo=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7COSJNQWR667MI5PN3IRM6HEVBNHHBW5BWIY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2844/514260400@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2844@github.com>
References: <quicwg/base-drafts/issues/2844@github.com>
Subject: Re: [quicwg/base-drafts] Client connection IDs are broken (#2844)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d3727635ecc0_8b33fc75a6cd96c2001c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/_psFLbPzu8J0ztzlXCFcRMRh6Wg>
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, 23 Jul 2019 15:27:41 -0000

Discussed in Montreal.  Some concern about enabling a TCP-like usage for QUIC, but concerns about the effect that a choice of an endpoint could have on its peer.

Options are:

1. MUST use only local information (local host, port, cid) to route packets.

2. SHOULD, with qualification, but leaving this open to people to shoot each other in the feet.

3. MUST unless you know something about what your peers (as you identify them) are doing.  This precludes peers that attempt to use connection IDs if you intend to use source-address-based routing.

I think that we might want to end up in the third bucket.  Which acknowledges and endorses the use case, but properly defines the conditions under which this is acceptable.

-- 
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/2844#issuecomment-514260400

v2.23.0 | Report a Bug | By Email