[quicwg/base-drafts] Consistent presenting Connection ID in packet or frame (#1336)
Quoc-Viet Nguyen <notifications@github.com> Thu, 03 May 2018 23:00 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 7F90412DA2B for <quic-issues@ietfa.amsl.com>; Thu, 3 May 2018 16:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.008
X-Spam-Level:
X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_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 r9anx7HJVJgT for <quic-issues@ietfa.amsl.com>; Thu, 3 May 2018 16:00:08 -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 1409F12DA2C for <quic-issues@ietf.org>; Thu, 3 May 2018 16:00:08 -0700 (PDT)
Date: Thu, 03 May 2018 16:00:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1525388407; bh=oSU3aUG2OdLn+69b5JEmCLLCxwcReTS1D9W+lTFwnZ8=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=GRaleqc1onzXjZgMq763CsEQMz7+k2qkp3Wz3QCiqNGeEDnBK5ppdVOKNV08weQJn 6CzaTf7cLnsyYWbI4QaHYX1TK+8c9D9UXXzZ8tL43AJPUEwsiEpuZh4eoYNEM04HLC E2Jt1iAhFjP82t5RIjE1mJgVk3t2uhgo2mBQrgMA=
From: Quoc-Viet Nguyen <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6ba5044ce4240b5537235b6679fab2afcddf7de892cf000000011703567792a169ce131475f5@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@github.com>
Subject: [quicwg/base-drafts] Consistent presenting Connection ID in packet or frame (#1336)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5aeb9477a6aa_17ad2acf0f6a0f50381733"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nqv
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/c1zD6__Dy0183dSCgZ8v841J8Pk>
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: Thu, 03 May 2018 23:00:10 -0000
Currently, there are 4 ways a Connection ID (CID) is presented in a packet or frame: 1. Using DCIL and SCIL (both 4-bit) in Long Header to encode its length. 2. No CID length in Short Header. 3. Fixed size CID in Stateless Reset packet. 4. Using a 8-bit field in NEW_CONNECTION_ID Frame for its length. I am wondering if it is possible to unify the way a CID is presented like Stream ID. I understand that CID is version-independent but what I am concerned the most is CID in Short Header: > Endpoints using a connection-ID based load balancer could agree with the load balancer on a fixed or minimum length and on an encoding for connection IDs. This fixed portion could encode an explicit length, which allows the entire connection ID to vary in length and still be used by the load balancer. I'm trying to implement a QUIC proxy and I don't know how to do with that since I don't control backend applications. Can we specify a Connection ID encoding in the specification, or at least in the first version? -- 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
- [quicwg/base-drafts] Consistent presenting Connec… Quoc-Viet Nguyen
- Re: [quicwg/base-drafts] Consistent presenting Co… Martin Thomson
- Re: [quicwg/base-drafts] Consistent presenting Co… Quoc-Viet Nguyen
- Re: [quicwg/base-drafts] Consistent presenting Co… Patrick McManus
- Re: [quicwg/base-drafts] Consistent presenting Co… ianswett
- Re: [quicwg/base-drafts] Consistent presenting Co… Lars Eggert
- Re: [quicwg/base-drafts] Consistent presenting Co… ianswett
- Re: [quicwg/base-drafts] Consistent presenting Co… Lars Eggert
- Re: [quicwg/base-drafts] Consistent presenting Co… ianswett
- Re: [quicwg/base-drafts] Consistent presenting Co… Lars Eggert
- Re: [quicwg/base-drafts] Consistent presenting Co… MikkelFJ
- Re: [quicwg/base-drafts] Consistent presenting Co… Kazuho Oku
- Re: [quicwg/base-drafts] Consistent presenting Co… MikkelFJ
- Re: [quicwg/base-drafts] Consistent presenting Co… Lars Eggert
- Re: [quicwg/base-drafts] Consistent presenting Co… ianswett
- Re: [quicwg/base-drafts] Consistent presenting Co… janaiyengar
- Re: [quicwg/base-drafts] Consistent presenting Co… janaiyengar