Re: [quicwg/base-drafts] ACK rules and packet protection (#34)

ianswett <notifications@github.com> Tue, 29 November 2016 14:37 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 DB890129BE9 for <quic-issues@ietfa.amsl.com>; Tue, 29 Nov 2016 06:37:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.394
X-Spam-Level:
X-Spam-Status: No, score=-4.394 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.497, 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 Zfn3Z3AdTVyh for <quic-issues@ietfa.amsl.com>; Tue, 29 Nov 2016 06:37:27 -0800 (PST)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 52D35129BE8 for <quic-issues@ietf.org>; Tue, 29 Nov 2016 06:37:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=github.com; h=from:reply-to:to:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=ZEgBrQL4+ReuVkOv98xw7NJKzms=; b=UOUYbbVTfW9E3SD5 nWH6SxbzGr8AKH3OKHaaNtHyZI0OKMRzOZr56XY7nJeC2ShT4zsS/Z543qYEin7Z I8QgfXv2yZGY3IZADvHpI+dhg6sNaSXCboYKqfzOUEQGAUlEv7DLHwZHm4KqNkTj bQjKkP0MUK8P8aYxWh7nOtmgN/Q=
Received: by filter0975p1mdw1.sendgrid.net with SMTP id filter0975p1mdw1-26026-583D92A6-5 2016-11-29 14:37:26.045398023 +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 ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id epbJuC0ORBS-KUGrgDgYUA for <quic-issues@ietf.org>; Tue, 29 Nov 2016 14:37:25.952 +0000 (UTC)
Date: Tue, 29 Nov 2016 06:37:25 -0800
From: ianswett <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/34/263586592@github.com>
In-Reply-To: <quicwg/base-drafts/issues/34@github.com>
References: <quicwg/base-drafts/issues/34@github.com>
Subject: Re: [quicwg/base-drafts] ACK rules and packet protection (#34)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_583d92a5bfea7_1f93f912dd0f13049979"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2TuS19ocjKTCAy8KyazXZDtKygfeNf5lHq3K JpdeSLf+ZZyqiPnFgdlhMmt77R6p03yB0fS/SVmugYoRVslvDYpEQ6CnWpHuqiKXoUXaUHrrTtVGBY lV99gIg4qkO0OlFwNRBL0XiRkivOBfDkZwixs+Vru0vv+eKFSIM4VQQhqDC4Y454eB4fpRxMKPEUp0 o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/O52NxNwCudfoUUh_E0dh_X3ap84>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quicwg/base-drafts <reply+0166e4ab898a80ccfe220c59ec52f901f5cebb0e1627116892cf00000001145554a592a169ce0b70894f@reply.github.com>
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: Tue, 29 Nov 2016 14:37:29 -0000

We can prohibit a server from sending a cleartext ACK.  The benefit of a cleartext ACK is an initial RTT sample on the client side in cases when the ClientHello was retransmitted.  As such, I'm slightly against this restriction at this point, unless you think prohibiting it has a value I'm not aware of.

I agree that an ack must be sent with the same or higher protection than the most protected packet it is acknowledging.


-- 
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/34#issuecomment-263586592