IETF Logo Mail Archive

Re: [quicwg/base-drafts] NEW_CONNECTION_ID: use sequence number for one CID only (#2096)

MikkelFJ <notifications@github.com> Tue, 04 December 2018 16:04 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 67763130E06 for <quic-issues@ietfa.amsl.com>; Tue, 4 Dec 2018 08:04:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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] 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 xXo8Ectbo8p3 for <quic-issues@ietfa.amsl.com>; Tue, 4 Dec 2018 08:03:59 -0800 (PST)
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 9DE0912870E for <quic-issues@ietf.org>; Tue, 4 Dec 2018 08:03:59 -0800 (PST)
Date: Tue, 04 Dec 2018 08:03:58 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543939438; bh=zAongr9EFCcFFj8N+bpZ15tpU6UVNUBFsAWX8QPyM+A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=heUc7NwmZx1ehePAIEhI4leJyeFZZjg9xXCcNyqsTbCDHwEc7zV2EGnm0td9Z6qDV UIt90DOYVNojoWiAr6Tc2R4h3XIJNVZzZN1+T5jGD33WM39fGfYpSvtyn0MSk82HPK e+ZWnD6gkpDvdsXjHAbLfUjXq5g6WxPGXJaAgcLs=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab13622cfc79e340f88117b8289673549df303c3b892cf00000001181e676e92a169ce171693ce@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2096/c444154036@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2096@github.com>
References: <quicwg/base-drafts/pull/2096@github.com>
Subject: Re: [quicwg/base-drafts] NEW_CONNECTION_ID: use sequence number for one CID only (#2096)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c06a56e9e257_5f9e3f88b7cd45b816436e"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/gR1_YqVOlU8Ho4Yt2uBLaqZWGoE>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Dec 2018 16:04:02 -0000

How would know that the sequence number is from a different CID? If you have this concern, wouldn't it be better to advice not to send a sequence number for different CID, and keep a range check receiver side on the assumption that the sequence number is specific to the given CID domain?

-- 
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/2096#issuecomment-444154036

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