Re: [quicwg/base-drafts] Replay protection is the responsibility of application protocols (9400c2f)
MikkelFJ <notifications@github.com> Wed, 06 February 2019 09:02 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 90A05130DD8 for <quic-issues@ietfa.amsl.com>; Wed, 6 Feb 2019 01:02:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.552
X-Spam-Level:
X-Spam-Status: No, score=-12.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 VFvBUbVHdezX for <quic-issues@ietfa.amsl.com>; Wed, 6 Feb 2019 01:02:41 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA78D130934 for <quic-issues@ietf.org>; Wed, 6 Feb 2019 01:02:41 -0800 (PST)
Date: Wed, 06 Feb 2019 01:02:39 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549443759; bh=MptHm/IzQ5CNPDZRcg1q8UpShVFQrfN0oaM26PBRY7Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=q1GUILmDqLXSK49JoWEyqYZ8Wg3u/biJKRs6q0Pk6nTAABgOmIgJhTM/Yjzm5frg9 zzSwLg08vdhQlr7WyqVFtCYVKlSw0bKENZB1ldGiuazGmzsNqch5/tdvN8wg1/D5rK ots7ISBqspfZYtotWQPPUBldHJrAegHcT1Spcq8c=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5dea30171063ac3054a7d679d0a0e11b88275e5992cf00000001187264af92a163ce01eb7be6@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/commit/9400c2f9b2c5a235ce15377538bc8dc354467f39/32209894@github.com>
In-Reply-To: <quicwg/base-drafts/commit/9400c2f9b2c5a235ce15377538bc8dc354467f39@github.com>
References: <quicwg/base-drafts/commit/9400c2f9b2c5a235ce15377538bc8dc354467f39@github.com>
Subject: Re: [quicwg/base-drafts] Replay protection is the responsibility of application protocols (9400c2f)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5aa2afe073d_191f3fa14b4d45b410191d"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/eyPFgs2FlgA2yCqdacTGfHTBbOg>
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: Wed, 06 Feb 2019 09:03:02 -0000
I think the application has a lot more useful information, but the application has no control over network configuration: it cannot see what lands on other endpoints, at least not without a heavy cost. So therefore, if we can truly enforce replay rejection at transport level, that would be a much saner approach, even if it places more restrictions on 0-RTT usage. While being safer against accidental mistakes, it also makes 0-RTT more useful, as you can do more things in 0-RTT. -- 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/commit/9400c2f9b2c5a235ce15377538bc8dc354467f39#commitcomment-32209894