Re: [quicwg/base-drafts] Implicitly Acknowledging CRYTPO Data (#1741)

Martin Thomson <notifications@github.com> Thu, 13 September 2018 00:03 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 D71C5130DFA for <quic-issues@ietfa.amsl.com>; Wed, 12 Sep 2018 17:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 abAash9ut6tv for <quic-issues@ietfa.amsl.com>; Wed, 12 Sep 2018 17:03:54 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D748F127AC2 for <quic-issues@ietf.org>; Wed, 12 Sep 2018 17:03:53 -0700 (PDT)
Date: Wed, 12 Sep 2018 17:03:52 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1536797032; bh=povw2cdI95obfE2IdSl7JNEWKenUxnsFMTQlXO6acH0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BxXTnKmdXx8rkqlh//ymZ7ok5Gr7UQK6FZDxaclj444ScM3OMeQfUmJVu9yHC6eRd WRSOeu5LiEjS14NPemwMCM7c3EFYFfqIDvIj3uCB1KKA8Tebee/afKdawoNQ++aTf6 8OSb8ENxLvncpZxzagGyJcOnlT9PhRO7uc9P8WKk=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab63e49ff048770929a31f72d4545c0aa368c7155292cf0000000117b16b6892a169ce156f81ba@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1741/420838259@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1741@github.com>
References: <quicwg/base-drafts/issues/1741@github.com>
Subject: Re: [quicwg/base-drafts] Implicitly Acknowledging CRYTPO Data (#1741)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b99a968b9e98_3c483fb555ed45b419938e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/8UMMic1k3xVTuQylF81YcKTQpxc>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Sep 2018 00:03:57 -0000

This is precisely the subject of discussion at the last IETF meeting.  It might help to review that.   What the implementation is doing here is valid: it operates loss detection on Initial packets independent of other packets.  To some extent, that's necessary.

That the handshake has proceeded and that activity at the next epoch indicates successful receipt of the necessary packets is extra information you aren't required to assimilate, but as @rpaulo says, you are free to do so.  We explicitly decided not to prohibit the optimization suggested, but nor do we require that anyone implement the optimization.  All THAT means is that you can't assume that the other side is going to stop sending you Initial+CRYPTO if you don't acknowledge it.

The exchange @nibanks describes is entirely valid as implemented, if suboptimal.  That's all.

-- 
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/1741#issuecomment-420838259