IETF Logo Mail Archive

Re: [quicwg/base-drafts] Spin bit should be applied per each 5-tuple rather than per connection (#1828)

mirjak <notifications@github.com> Wed, 28 November 2018 17:35 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 786E9130E8B for <quic-issues@ietfa.amsl.com>; Wed, 28 Nov 2018 09:35:43 -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 0mAzw79_pgU3 for <quic-issues@ietfa.amsl.com>; Wed, 28 Nov 2018 09:35:42 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DECEE1277BB for <quic-issues@ietf.org>; Wed, 28 Nov 2018 09:35:41 -0800 (PST)
Date: Wed, 28 Nov 2018 09:35:39 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543426539; bh=BUzU5C5Ezx8YSz+DZkVIJunvEl3Rs+jE/V2fg1Ol9Gw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=B1iueTmc5mCVctoQ4HJhuAbzayzCkwOSj/a4CaBjBm7t5tAsLBDv4gm0VDJGH7PY5 cKYnAEsU10Nma3JiST1AFBzzbZaE53rnJxoloykW4G+1pn6tAJT02SyHoF8mpFcEfC 2HwfF2YcmMUhsgLnzBwvZS65jrEqPXAKM40N37Gk=
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb573989669de2ea4fbab3cc60bb1bdc85730aa9d92cf00000001181693eb92a169ce15d27d33@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1828/442535987@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1828@github.com>
References: <quicwg/base-drafts/issues/1828@github.com>
Subject: Re: [quicwg/base-drafts] Spin bit should be applied per each 5-tuple rather than per connection (#1828)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bfed1ebdcb06_6e4b3fca654d45bc17743"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
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/MeEBOIx4wz02y2Lnps91SXPRT7o>
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: Wed, 28 Nov 2018 17:35:44 -0000

Is the assumption of the current discussion that the connection ID is present/non-zero? I guess if no connection ID would be present a per-CID spin signal would look quite random from the network, no? 

-- 
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/1828#issuecomment-442535987

v2.23.0 | Report a Bug | By Email