Re: [quicwg/base-drafts] Fix: a connection is not identified by a *collection* (#1632)
Mike Bishop <notifications@github.com> Tue, 07 August 2018 17:15 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 33BC512D7F8 for <quic-issues@ietfa.amsl.com>; Tue, 7 Aug 2018 10:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 Aa9ImIYgjE8s for <quic-issues@ietfa.amsl.com>; Tue, 7 Aug 2018 10:15:41 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0B7C1277BB for <quic-issues@ietf.org>; Tue, 7 Aug 2018 10:15:40 -0700 (PDT)
Date: Tue, 07 Aug 2018 10:15:40 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1533662140; bh=xjJWaDVvWDRlaigf6GA8UdMUen87BRwk4qxA5s+e3XY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=P+CUSsxYQhugvoROiF6Oyzay2xEDOil1Qss4InvsfecYfXb7yvF5804KPLB60aQ6T zn8McFfH4nfLC363UYbTbQXllQ8vL1kY/YvzK4O/oA3Gpyk5a+slHBduz1DqSN/5v8 T1EyW0+5dPXzQrABOg77EZMEphhMTc4Iy3ow5Fck=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4e2b3ac482a6a549e90d916a2e4b7a816b07cde892cf00000001178195bc92a169ce14a9b803@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1632/c411133382@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1632@github.com>
References: <quicwg/base-drafts/pull/1632@github.com>
Subject: Re: [quicwg/base-drafts] Fix: a connection is not identified by a *collection* (#1632)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b69d3bcf3e6_77013fb6b66be6247806b"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/q7gVAU5CUWeBwcbEjS1g2hLptHg>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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, 07 Aug 2018 17:15:42 -0000
I think we need to assume that CIDs are unique without regard to the client address, because otherwise you won't survive NAT rebinding. The same will be true for server addresses if we allow server migration in a future version, so I'd like to lay the conceptual groundwork here. I agree that a server could hypothetically reuse CIDs across its own addresses, but to me that seems more conceptually akin to multiple independent servers running on different ports. I'm inclined to leave the uniqueness comments in, as @dtikhonov has done here. I originally said "unlikely to be" unique, since IIRC we have at least one implementation that used zero-length addresses until there was a tuple overlap. Zero-length can be unique if it's the only one. :-) -- 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/1632#issuecomment-411133382
- [quicwg/base-drafts] Fix: a connection is not ide… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Fix: a connection is not… Martin Thomson
- Re: [quicwg/base-drafts] Fix: a connection is not… MikkelFJ
- Re: [quicwg/base-drafts] Fix: a connection is not… Mike Bishop