Re: [quicwg/base-drafts] Latency Spin Bit (#609)

mirjak <notifications@github.com> Thu, 08 June 2017 08:03 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 3A0F1128C82 for <quic-issues@ietfa.amsl.com>; Thu, 8 Jun 2017 01:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.183
X-Spam-Level:
X-Spam-Status: No, score=-3.183 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_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, 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 jUr4BjjPen0Y for <quic-issues@ietfa.amsl.com>; Thu, 8 Jun 2017 01:03:02 -0700 (PDT)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 81B231204DA for <quic-issues@ietf.org>; Thu, 8 Jun 2017 01:03:02 -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=a+O3GJ4jHpZTh0fsQkcQGXQjmw0=; b=JjUi7YdeXXipB3NL j1mDYL3V0nJ6ViB7ruuk1QZm3qglbqYAQmIqjQbGPkPKfLZ3p5wSWEN5Hux3Olej lj/50UQOc7x28gA4sTFGzjTvI3tF8IecoeGmr7qADqlcuHO4cRW6iWLJk97eBf+5 cspIFZlh8YlGR7bI5X2ES40HjS8=
Received: by filter1151p1mdw1.sendgrid.net with SMTP id filter1151p1mdw1-12149-593904B5-14 2017-06-08 08:03:01.290288487 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id FfPypBCnS-CY_QFh8KuDJw for <quic-issues@ietf.org>; Thu, 08 Jun 2017 08:03:01.218 +0000 (UTC)
Date: Thu, 08 Jun 2017 01:03:01 -0700
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab0d094094a8dc0521752f6dbf567120f6e9252a8292cf000000011550c6b592a169ce0df938a1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/609/c307029915@github.com>
In-Reply-To: <quicwg/base-drafts/pull/609@github.com>
References: <quicwg/base-drafts/pull/609@github.com>
Subject: Re: [quicwg/base-drafts] Latency Spin Bit (#609)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_593904b513b05_46683fd7a5f51c2c3993c"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2LTGNnvJYcQ3gX1FoJD2f+Jtt+RKey00lPcn kNwEhnxL1RS5UbHV+4DsaX+S3Lq9VfCvXNvj9Cv92U4Fb47Ud3OW41+gQenY99ojG+3pkYYLOQEsQD 3CEdcVYM9J/jAKx+/xu6pJxyDoOqwYjxVv803oVMGKRyvw+SeZEiBS3YeUE20vi9DTgLWDRrvLVNCd c=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/gsrg77aF2FBzLSVGJp1O1thiab8>
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, 08 Jun 2017 08:03:04 -0000

Instead of using a 'whole' bit, you can also have another packet type for protected packets. And if you define a well know patter that is used, you can even measure loss with it.

-- 
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/609#issuecomment-307029915