Re: [quicwg/base-drafts] Does a timestamp for a packet implicity ACK it (#698)
janaiyengar <notifications@github.com> Wed, 06 September 2017 21:06 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 2468A1329C5 for <quic-issues@ietfa.amsl.com>; Wed, 6 Sep 2017 14:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.999
X-Spam-Level:
X-Spam-Status: No, score=-6.999 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_32=0.001, HTML_MESSAGE=0.001, 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 069LDFdyatZI for <quic-issues@ietfa.amsl.com>; Wed, 6 Sep 2017 14:06:53 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext7.iad.github.net [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB983132026 for <quic-issues@ietf.org>; Wed, 6 Sep 2017 14:06:52 -0700 (PDT)
Date: Wed, 06 Sep 2017 14:06:52 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1504732012; bh=uTXtzJH+kKXL5vbXGct8XPykvOEQ9FEqkjHWJ44peiw=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JUR0f0u+AbaHNtTeqbXzPHD2sc3rYa1Cwx7VhNRaMkDV6IsM89hAx1DCD/UBSB2G+ xRrYFJ0avXrXcyJiwfgeNBShAIwOcuMlP4zFjZB53Xkb/ASY+GrRlURP08WRwu+o0R JZ0bGU4fSwF4dyzjmJ3I75RG7EKmWI9N3I8tHBPk=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5057ec32c29a3f1a8489cf8b738aa7f21146e35492cf0000000115c8256c92a169ce0ea843fe@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/698/327612919@github.com>
In-Reply-To: <quicwg/base-drafts/issues/698@github.com>
References: <quicwg/base-drafts/issues/698@github.com>
Subject: Re: [quicwg/base-drafts] Does a timestamp for a packet implicity ACK it (#698)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59b0636c42d84_12683fab243b1c3024440"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/VLqiFJb3k4Hkk9oDTzcURkkCvJk>
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: Wed, 06 Sep 2017 21:06:54 -0000
@martinduke: I agree with you in theory that a timestamp semantically is an ack. That said, I can't see why a receiver would send a timestamp but not an ack for it -- that seems backwards. Timestamps are advisory in that they may or may not be received, and they tend to be sent just once. Acks are the "primary" information here. It is much simpler to write out all the ack blocks and then fit all the timestamps you can within a frame, than to have rules that mix and match both. Making the receiver never send timestamps for packets that are not being acked in the frame makes it clear what the expected behavior is, and simplifies parsing the ack frame. -- 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/698#issuecomment-327612919
- [quicwg/base-drafts] Does a timestamp for a packe… Subodh Iyengar
- Re: [quicwg/base-drafts] Does a timestamp for a p… ianswett
- Re: [quicwg/base-drafts] Does a timestamp for a p… Subodh Iyengar
- Re: [quicwg/base-drafts] Does a timestamp for a p… ianswett
- Re: [quicwg/base-drafts] Does a timestamp for a p… MikkelFJ
- Re: [quicwg/base-drafts] Does a timestamp for a p… ianswett
- Re: [quicwg/base-drafts] Does a timestamp for a p… martinduke
- Re: [quicwg/base-drafts] Does a timestamp for a p… martinduke
- Re: [quicwg/base-drafts] Does a timestamp for a p… janaiyengar
- Re: [quicwg/base-drafts] Does a timestamp for a p… martinduke
- Re: [quicwg/base-drafts] Does a timestamp for a p… ekr
- Re: [quicwg/base-drafts] Does a timestamp for a p… Martin Thomson