IETF Logo Mail Archive

Re: [quicwg/base-drafts] Negative Connection ID Sequence Number (#1484)

Kazuho Oku <notifications@github.com> Thu, 28 June 2018 00:26 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 9636E130E54 for <quic-issues@ietfa.amsl.com>; Wed, 27 Jun 2018 17:26:06 -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 EmX5oEe0qi1r for <quic-issues@ietfa.amsl.com>; Wed, 27 Jun 2018 17:26:04 -0700 (PDT)
Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD8EE130E53 for <quic-issues@ietf.org>; Wed, 27 Jun 2018 17:26:04 -0700 (PDT)
Date: Wed, 27 Jun 2018 17:26:04 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530145564; bh=rk1EGzunXOtiZbTqQKMB4nxHtZ87SMzSMr0RkPrY4pA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rJmytPOOZSKWtBUtjmZ83HpiVoArJsQji9ZGSJTmHIYQRYrNu88D1yWo4Y/IViqPJ pWl41zd12bYSq1Nmi/ckC5nE2l2dfg6arMqncwTr2+b4sdUp4w4RyI7VaFEO4CSUai zqGHeCJutCLvnbP5tvviAipvJ3Ee1g9zVD038v8E=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab88d6bb791c8561b94573b9af52898f568292ea8492cf00000001174bed1c92a169ce140758e9@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1484/400871736@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1484@github.com>
References: <quicwg/base-drafts/issues/1484@github.com>
Subject: Re: [quicwg/base-drafts] Negative Connection ID Sequence Number (#1484)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b342b1c4ea97_76b73f8cccbd2f8417164"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/-TZdrJJj3-k7cyz-n33yGcKpOsk>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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, 28 Jun 2018 00:26:07 -0000

My preference goes to numbering each Connection ID *the endpoint provides* contiguously, starting from zero.

To be precise:
* SCID of the Initial packet is "zero"
* CID of SPA is "one", if exists
* CID being exchanged using NEW_CONNECTION_ID frames will start from "one" (if a CID is not provided by the endpoint using SPA), or "two" (if SPA was used)

I believe that the definition is clear, and that it is also easy to implement.

An implementation is required to have a structure that drops duplicate NEW_CONNECTION_ID frames. Having non-negative sequence numbers for SCID of the Initial packet and CID in SPA is only a matter of how we setup the structure.

-- 
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/1484#issuecomment-400871736

v2.27.6 | Report a Bug | By Email | System Status