IETF Logo Mail Archive

Re: 0-RTT usage rules are wrong

David Schinazi <dschinazi.ietf@gmail.com> Thu, 19 November 2020 20:23 UTC

Return-Path: <dschinazi.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 271603A117D for <quic@ietfa.amsl.com>; Thu, 19 Nov 2020 12:23:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 JkOg73wP8zpc for <quic@ietfa.amsl.com>; Thu, 19 Nov 2020 12:23:33 -0800 (PST)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 72F223A117A for <quic@ietf.org>; Thu, 19 Nov 2020 12:23:33 -0800 (PST)
Received: by mail-pf1-x42f.google.com with SMTP id w6so5601794pfu.1 for <quic@ietf.org>; Thu, 19 Nov 2020 12:23:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JIGKFpR4T/qNmEKyjyBII6QA467BLi6LOcWxTCwDlik=; b=RqYMHFOnFSjGI0LjhS8nBDkFRAJUKto9M9gGN9HOlTw1VMLmAsEv0LPuFUA+gSoHac eHCFZg54ouUFdB2/EnyTTrx2MqlFlaas+WtozsMSvEk6J5mIOMzdpAl2OJWNTnbX4oGq tRdLaAuf2OhTtupbvcQcmsv8yvwvA4AYFrkM4Vif8kz26121pqBeB0TKDag6M7nDruh7 814XR4/jRHv6jhb8thtTTj5HTyQihtHg/BuPFbrFZd6sHUXzRHYqr6KPVG9Us2JbNt6W eQUujtweXON+C8XtCloAj4r9Vh0s7AW560+cILhgwvV+4Klu89k2j04rIMU8GXkhVG71 fkCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JIGKFpR4T/qNmEKyjyBII6QA467BLi6LOcWxTCwDlik=; b=DhB+FDh74OtCOf04raLIxpWwPOPVC25odGwnR6W2xeJ+60Ki2/8oFmYI6/bmtliHZq JctZuZhYyp0TYRFvkb3kv45Ph7j+gch2CmXoo/c6Si2Z19ys5ejXleaN7vvyS5A+4pQ3 xKeIwrJAJLXDR3VWEHPhwHoxcuZ6KBOjQXTuJBZKC/0mhlPwDIyNRf4fJXYrsMV5hmnk Y9pOfkIIFonQF4QbdZ0w/hxFJUoMDl/oyTgTdGYEfkWwOIgUtt+pEVqqKCvwSX7Z8nFb 0lmMDpggWnOrWIqFZVcM3v2HkdHOP/hyOjz+RdufLfPZ0sLUoFwSLg20iiRimfeuyWtd lBuw==
X-Gm-Message-State: AOAM533MVpWacgfDupQgu5cljm5+skq+nDfBxNeyBmyj40Dr06W8CSCw eqrnbKYAKmRyBMQ1d2+wTeN9hxKoX0928x3H9+U8quAkXEQ=
X-Google-Smtp-Source: ABdhPJzbMLxSiLfCWT7pp1eaMoATrakSX0Kt+n6PYvXvpJztYw1NgL2XRc26J9QV3aWNbWa+KvNHSyzGZxdph5X6in4=
X-Received: by 2002:a05:6a00:158b:b029:18b:fd84:956d with SMTP id u11-20020a056a00158bb029018bfd84956dmr10960504pfk.22.1605817412870; Thu, 19 Nov 2020 12:23:32 -0800 (PST)
MIME-Version: 1.0
References: <326752af-6c6d-4fc8-ad76-0b00c7b46cbd@www.fastmail.com> <68743cd28c6588b5ce2eb18eeb15126a8b6d7988.camel@ericsson.com>
In-Reply-To: <68743cd28c6588b5ce2eb18eeb15126a8b6d7988.camel@ericsson.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Thu, 19 Nov 2020 12:23:21 -0800
Message-ID: <CAPDSy+654OTx7wHh1xUrMvrA3ZOw80mQ9HTWVEhApgxy=Mwd-A@mail.gmail.com>
Subject: Re: 0-RTT usage rules are wrong
To: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>
Cc: "mt@lowentropy.net" <mt@lowentropy.net>, "quic@ietf.org" <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000077e7de05b47b80e7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/GVKypHdKPTUrz7_PLWYtxKil7iU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2020 20:23:35 -0000

Thanks for finding this, Martin. Your fix looks good, and while it does
change the text, I think it states what we meant all along ;-)

David

On Thu, Nov 19, 2020 at 2:29 AM Magnus Westerlund <magnus.westerlund=
40ericsson.com@dmarc.ietf.org> wrote:

> Hi,
>
> From my AD perspective I think it is good to fix this. Otherwise I am
> convinced
> that Ben or Roman (Sec ADs) anyway will react on it.
>
> WG, please review the text proposal!
>
> Cheers
>
> Magnus
>
> On Thu, 2020-11-19 at 17:00 +1100, Martin Thomson wrote:
> > I was just reviewing the applicability draft (Brian, Mirja, expect a PR
> > soon).  I was surprised to see such a strong assertion regarding
> idempotence
> > in there.  I followed the link to the TLS draft and found that the text
> there
> > was just wrong.  Not badly wrong, but wrong in a way that conflicts with
> RFC
> > 8470.
> >
> > Now, I wrote both, so there is no excuse.  But I'd like to be given a
> chance
> > to fix this.
> >
> > Issue:
> >
> https://protect2.fireeye.com/v1/url?k=98a27635-c7394f04-98a236ae-86e2237f51fb-afbf76956a17f6b0&q=1&e=a4325166-9081-4878-a243-c3db587fb5e3&u=https%3A%2F%2Fgithub.com%2Fquicwg%2Fbase-drafts%2Fissues%2F4393
> > Pull Request:
> >
> https://protect2.fireeye.com/v1/url?k=d4333fd5-8ba806e4-d4337f4e-86e2237f51fb-56fc156292f3b52d&q=1&e=a4325166-9081-4878-a243-c3db587fb5e3&u=https%3A%2F%2Fgithub.com%2Fquicwg%2Fbase-drafts%2Fpull%2F4394
> >
> > This is a substantive change that better aligns the rules here with
> existing
> > work.
> >
> > Cheers,
> > Martin
> >
>

v2.23.0 | Report a Bug | By Email