IETF Logo Mail Archive

Re: [quicwg/base-drafts] Explicit support for on-path calculation of RTT of QUIC flows (#631)

Christian Huitema <notifications@github.com> Mon, 19 June 2017 03:49 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 A45681273E2 for <quic-issues@ietfa.amsl.com>; Sun, 18 Jun 2017 20:49:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.395
X-Spam-Level:
X-Spam-Status: No, score=-8.395 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_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, 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 X8iFctrSpzdK for <quic-issues@ietfa.amsl.com>; Sun, 18 Jun 2017 20:49:03 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 111AC127078 for <quic-issues@ietf.org>; Sun, 18 Jun 2017 20:49:03 -0700 (PDT)
Date: Sun, 18 Jun 2017 20:49:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1497844142; bh=cLGtIzB7Wmpr6t+r/yrLswZJXs4uhzZuIUYLfg7O9C0=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gH04uocRpbQhkKhuhbp2R88CpeicDgfscc+slfitzJ9oK8WGb1qzLNmu7zl7TA2VI A7r4nKc8xmQwmWPfeJ9M6B/kRQOsRNZ5rJq6Y7oz1jLW1Re+FOpN/c4j1SiUmjJBQw Fe8W4anYEQB3RMhNwjS480F1zKc7aVA/VaKRj0ak=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf7abdad88d223327b849c5fe274bbba9878fcfe892cf00000001155f0bae92a169ce0e0f8270@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/631/309332099@github.com>
In-Reply-To: <quicwg/base-drafts/issues/631@github.com>
References: <quicwg/base-drafts/issues/631@github.com>
Subject: Re: [quicwg/base-drafts] Explicit support for on-path calculation of RTT of QUIC flows (#631)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_594749ae2d45a_60e53ff95e293c30510fb"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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/iKvLr6WVl1ArB6JVlejr83HecbI>
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: Mon, 19 Jun 2017 03:49:05 -0000

We could certainly work with packet types instead of dedicated bits. The intermediate nodes would need to observe transitions of the first octet instead of looking at just one bit. But then, we also have a proposal to grease the first octet, for example by doing an XOR with a function of the last byte. That type of greasing would randomize the first octet. So we have a choice: if we want to grease the first octet, we need to dedicate a bit that is exempted from the greasing. If we don't then we can use a packet type.

-- 
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/631#issuecomment-309332099

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