Re: [quicwg/base-drafts] Connection ID lengths 1, 2 and 3 bytes can't be encoded (#1570)

ekr <notifications@github.com> Tue, 07 August 2018 20:05 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 B011B130EF9 for <quic-issues@ietfa.amsl.com>; Tue, 7 Aug 2018 13:05:07 -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 djYuRzmvJkh1 for <quic-issues@ietfa.amsl.com>; Tue, 7 Aug 2018 13:05:06 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F06D1310BD for <quic-issues@ietf.org>; Tue, 7 Aug 2018 13:05:06 -0700 (PDT)
Date: Tue, 07 Aug 2018 13:05:05 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1533672305; bh=NaAgnI+e9HCGUbmrHrUKrz5+OX1OpH511zoneMtaLxk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RBZ1co6k2SqY6LOUV4lR8VKU8r73fAT57sH8WJR0p4tmV1+f/DywrZoyxPW3DI/0x F2cQWT0jQeC0ouGmHUSuoWmz+L1bUbA/M0e7rW76Y5cR/sRN9RLxtbFgsz7Hq+9agQ Ur4J2RhkExuUCKEFNj/axBxMm+UM2y9JtVuE7jmU=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc0e8e770f5e7959fc32053cf0f8eb6d52d4c3aa192cf000000011781bd7192a169ce14587666@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1570/411184260@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1570@github.com>
References: <quicwg/base-drafts/issues/1570@github.com>
Subject: Re: [quicwg/base-drafts] Connection ID lengths 1, 2 and 3 bytes can't be encoded (#1570)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b69fb71505f9_51353fcf0d6d45b819383f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/XKxxtFYUivcB7H480rxInR122f0>
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 20:05:08 -0000

@janaiyengar: I'm not sure I disagree, but I feel uncomfortable going
against what I thought was consensus. Regrettably, I think a topic for NYC.

On Tue, Aug 7, 2018 at 12:40 PM, janaiyengar <notifications@github.com>
wrote:

> @ekr <https://github.com/ekr> @martinthomson
> <https://github.com/martinthomson> : I think it's useful to have this
> degree of freedom for uses, for instance, where there's no migration, but
> only demultiplexing among a few connections. I understand the concern that
> having connection ID that's too small can lead to linkability, but I think
> there's a natural pushback here -- servers that use connection ID for
> demuxing will want to use a large CID because small ones are not enough, or
> they'll use no CID. The only place a small one becomes interesting is when
> (i) there are only a few connections being demuxed and (ii) where the bit
> cost matters. This is true in the p2p case, where I would argue that
> linkability is quite easy with just timing of packets.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/1570#issuecomment-411177124>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABD1oaQcNqm140O3BhvaRU19r3qq1c5hks5uOe0pgaJpZM4VQV65>
> .
>


-- 
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/1570#issuecomment-411184260