Re: [quicwg/base-drafts] Consistent presenting Connection ID in packet or frame (#1336)

MikkelFJ <notifications@github.com> Sat, 05 May 2018 10:07 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 909041242EA for <quic-issues@ietfa.amsl.com>; Sat, 5 May 2018 03:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Level:
X-Spam-Status: No, score=-3.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, 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 yt-O4N1J7ZR6 for <quic-issues@ietfa.amsl.com>; Sat, 5 May 2018 03:06:59 -0700 (PDT)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE9071241FC for <quic-issues@ietf.org>; Sat, 5 May 2018 03:06:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=LKGhTQ6fHhgGUApAVSdz+ePhcUQ=; b=S3NfyGUTiudCodTE dnDkc0HyPeXWJWEORPqZ3+n6fEwZBPUah5pJwHYo18NCPxJbiBVPMNK5hGzkxadO uJ/jkMjVRqIXJrPq3JL30Cwa7gSzULHP8qp+HSRwqtPWXIcvzfGLsexxgVUJahfo FJuLCCGtWzHfIrUldcnGlrHZqXY=
Received: by filter0561p1iad2.sendgrid.net with SMTP id filter0561p1iad2-16320-5AED8241-D 2018-05-05 10:06:57.568375874 +0000 UTC
Received: from github-lowworker-1f7e42f.cp1-iad.github.net (unknown [192.30.252.46]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id kxoTsUo1Q6Ky8mWGby5blA for <quic-issues@ietf.org>; Sat, 05 May 2018 10:06:57.487 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-1f7e42f.cp1-iad.github.net (Postfix) with ESMTP id 74EFCC00AF for <quic-issues@ietf.org>; Sat, 5 May 2018 03:06:57 -0700 (PDT)
Date: Sat, 05 May 2018 10:06:57 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1d26a7dbd2de29533b39df1563533159c7004a9092cf000000011705444192a169ce131475f5@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1336/386794629@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1336@github.com>
References: <quicwg/base-drafts/issues/1336@github.com>
Subject: Re: [quicwg/base-drafts] Consistent presenting Connection ID in packet or frame (#1336)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5aed8241730ea_7a692acc56c20f543090b2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
categories: subscribed
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3crLXm2mn1l0PfUu2lrsYeNesVL/cgwVQRnz 1at5EvvpIOE90p+iLaKxXns0HnkXXQuPPuA6WFGLceWNMJSR02cyV2nrKY0ib/pGbHTaYBLewAqWGw YMV6Lt/o1vp9cBp5kYpNRFdd+RRmf1Uz8KUiaLHgQCwi2+5hlbjUX0qkYg==
X-SG-ID: A4fhEY3diXC81rW45KdZlyZUeIsAZbh4s7lWAZfiJNE=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/mEKVJG_hCNtr0aLP9-4b69Wnim8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 05 May 2018 10:07:00 -0000

I was thinking a bit about using a single port also for the client case:

In this case the number connections is likely small, but a CID cannot be zero length. Using a full byte to encode CID length is a bit much if you only need to distinguish between 8 different CIDs.

At the same time, if CID's are tied to key rotation, 0 length CID's won't work but a single bit CID would work similar to a key phase, iff CID's can be reused in this case.

If the minimal CID length, including length prefix, is a single byte, there isn't much space left for longer, but it can be handled:

Two bits code for length. 00, 01, 02, 03

00: keyphase, zero length CID, but a single keyphase bit.
01: 6 bit bit CID
02: 14 bit CID
03:  CID length is encoded in the following 6 bits.

-- 
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/1336#issuecomment-386794629