IETF Logo Mail Archive

Re: [quicwg/base-drafts] ACK frame (#644)

MikkelFJ <notifications@github.com> Thu, 22 June 2017 14:46 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 7B2EA129AAD for <quic-issues@ietfa.amsl.com>; Thu, 22 Jun 2017 07:46:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.801
X-Spam-Level:
X-Spam-Status: No, score=-4.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 Jg39yrnPDg7v for <quic-issues@ietfa.amsl.com>; Thu, 22 Jun 2017 07:46:53 -0700 (PDT)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 2FFB2129A9B for <quic-issues@ietf.org>; Thu, 22 Jun 2017 07:46:53 -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=zq//tomXWXIU8CWa7jeJPOh7VQo=; b=OzUHWX049ukZ7ACO Jg5tm+WVFGPRE6ZbLoatX6/+9FtvPOE62ibIpongg4AqXEUFP5wSmyokmvC/WRVK ne/75PAtxPtczHqJ2xpxXRaAN2KPC7H96FFYc4Eoe86ywQIU+ujVeZb2FAY2FOrk caC+CeDuP+tMmgbl5aRcqRHuBsY=
Received: by filter1071p1mdw1.sendgrid.net with SMTP id filter1071p1mdw1-7078-594BD84C-3D 2017-06-22 14:46:36.620213406 +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 ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id 7WP9FNZURfa_4FyFP4P0vg for <quic-issues@ietf.org>; Thu, 22 Jun 2017 14:46:36.541 +0000 (UTC)
Date: Thu, 22 Jun 2017 07:46:36 -0700
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5beb4b0c8086bc1abfb8dbd934cf7aefe143529792cf0000000115639a4c92a169ce0e25e5b6@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/644/310402443@github.com>
In-Reply-To: <quicwg/base-drafts/issues/644@github.com>
References: <quicwg/base-drafts/issues/644@github.com>
Subject: Re: [quicwg/base-drafts] ACK frame (#644)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_594bd84c632a5_5ac93ff8f55c1c2c10397f"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0IO6oBmfoHvCmpOtTtfIGbI0zPm1/DzK2gCD xaPgyQ+fVNjBWSraHf9MW7MAxj7R53OKrRcwNZuyP4/dtiY6N27JUxeh8MjqrnWbt+LiyYHYtYzL2M Ftud1c6gf5mmPadIEI5b40wV1fg5DkqyWSkM82ouLxwfkKHoxUKWQR8C/ImuR65jFwbj/lP32e2tlW g=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/v7x5Q5nZRUKs-8FLtkej0hQTzas>
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, 22 Jun 2017 14:46:55 -0000

#221 references 0RTT ACKs in TLS.
For other cleartext ACKs the text is a bit vague :

>An endpoint SHOULD use data from unprotected or 0-RTT-protected "ACK"
   frames only during the initial handshake and while they have
   insufficient information from 1-RTT-protected "ACK" frames.  Once
   sufficient information has been obtained from protected messages,
   information obtained from less reliable sources can be discarded.

Ignoring 0-RTT:
Does this mean cleartext ACK can remain valid after handshake? Considering constraints on cleartext content (stream 0 + ACK only), I don't think it is relevant anymore, but if it is relevant, would that not follow automatically: if a packet is not acknowledged and not retransmitted, that ack is relevant, otherwise it is not - same as any ACK?

If the text means remains relevant until handshake or sufficient information obtained - that would not be possible before handshake anyway?

-- 
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/644#issuecomment-310402443

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