IETF Logo Mail Archive

Re: Rationalise HTTP_WRONG_STREAM and HTTP_UNEXPECTED_FRAME

Ian Swett <ianswett@google.com> Wed, 07 August 2019 13:26 UTC

Return-Path: <ianswett@google.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 BE6E412004E for <quic@ietfa.amsl.com>; Wed, 7 Aug 2019 06:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Level:
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 YIAG3EsMf4AF for <quic@ietfa.amsl.com>; Wed, 7 Aug 2019 06:26:50 -0700 (PDT)
Received: from mail-ua1-x92b.google.com (mail-ua1-x92b.google.com [IPv6:2607:f8b0:4864:20::92b]) (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 E50C8120086 for <quic@ietf.org>; Wed, 7 Aug 2019 06:26:49 -0700 (PDT)
Received: by mail-ua1-x92b.google.com with SMTP id v20so35020982uao.3 for <quic@ietf.org>; Wed, 07 Aug 2019 06:26:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=E1OTUHDONeh5x8eI4B/aUBKObWsnOL2WozzvMCMtnzw=; b=VMcMVSn4F4mK2F+630HRkL/HAy1N/eIWOu9wIOFPIA70AgPLHrHiwIJpBENGIRCow5 HqnCsjk5IovPxAklvtuvUH3R6viIBCpEjDKr6JfwtNNHbTdXRR6jfcbCPnOidDg0MaZ5 SB3n7wfZcd/dNcLxa5sWV0ApzR1Gr1X3K6CuWU44quKMKfXeqX2+9DPF7gKxPuAj9bGz fSLJSECHFhflfEaWQ856okxfwA7qLYOggguom06A+OELf9zHCjFvO0XkMFsa6AXchC2M rO8u47mpRfFq6bpnRz24VJL5uCbzx9io7HnI6POA752zmTc8kxODjHVK2LvVZaqzqQwO OPew==
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=E1OTUHDONeh5x8eI4B/aUBKObWsnOL2WozzvMCMtnzw=; b=RUuALOHWLkiZ8ADGfn1cisgICyrkqakE8ESp/d9/eWvyDNILawn1jOzfVK++UNYHKR wqPm3iiYdg2JKKkvshjnb84k7WFchqzmn9hKa5oZHpdVnTPyrTVzYKoNFp5YcpdC+fMv KzWvmEkshhWHxq4riaR8ahdrTv6Rd3Uxhvhd2vvX2/+QBEjvO2MS/zEFu/g7Q1J5WCXP X6Q5+j9ZXMErsXnEPcLkzn/jW7UPwnt4Wc83Zs5BmD8o1o+uNzDdhlPb8FBeiT+Gkanj RaM8fRcCLwNUDX0JAmcr4EBv/BLxJyBlE1cmJ9J6d5h3ui9FQEdLPY3prafUJYUXH4nJ vjng==
X-Gm-Message-State: APjAAAVftWwyGwzWNyZ7D/OHhgXERYY40+7rbA6jlEnyuN3QGKbVHRa9 G3zzbMRTDg8WAwxYOmqpEWmkpll17x8diPUuaTvQ7w==
X-Google-Smtp-Source: APXvYqy2Ox4k3PVsN6CBRH6J/zGR3mq0hHlAaGsehYrkJ6/O++k44uEeFrH9wBFh1lGc/sFQl/x3HIN7Sycf6mT7gdE=
X-Received: by 2002:ab0:2b7:: with SMTP id 52mr6044048uah.23.1565184408593; Wed, 07 Aug 2019 06:26:48 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9ob7=MzO5qt987dpBAxBqnsMRvkrgYz7svktKsMNNhjAdw@mail.gmail.com> <608f1832-2ac3-4459-875e-bdc9a86ad8b8@www.fastmail.com> <CALGR9oYaKt3wD=ctrS+9PPnf3Er4Ggg9JtQkc-EHPvBbGpW_=Q@mail.gmail.com>
In-Reply-To: <CALGR9oYaKt3wD=ctrS+9PPnf3Er4Ggg9JtQkc-EHPvBbGpW_=Q@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Wed, 07 Aug 2019 09:26:36 -0400
Message-ID: <CAKcm_gMA0LaCi5xjXXTC5H7Qcgu4Mipy5qtgQ+o=c11yQaoFjw@mail.gmail.com>
Subject: Re: Rationalise HTTP_WRONG_STREAM and HTTP_UNEXPECTED_FRAME
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Martin Thomson <mt@lowentropy.net>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000aeffdd058f86e4d7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8YpgFKCb0w1fel7EsbboT4I3leU>
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: Wed, 07 Aug 2019 13:26:52 -0000

The distinction seems fairly clear to me and I'm happy keeping the draft as
is.

On Tue, Aug 6, 2019 at 8:47 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

>
>
> On Wed, Aug 7, 2019 at 1:29 AM Martin Thomson <mt@lowentropy.net> wrote:
>
>>
>> However, I'm also concerned that this is going to get wrapped up in the
>> usual compliance test mess.  If I hook up different parsers on different
>> streams and my request stream parser doesn't know about SETTINGS at all, so
>> ignores it when it suddenly appears on a request stream, is the test case
>> going to fail when I don't generate HTTP_FRAME_IN_THE_WRONG_PLACE?
>>
>
> My intention would be to keep the exisiting error rules and behaviour.
> Each stream type has a set of allowed Frames, as outlined in Section 7 /
> Table 1. If your request stream parser totally ignores a mandatory HTTP/3
> frame like SETTINGS, it is presently non-conformant (for whatever you
> choose that to mean).
>
>
>

v2.23.0 | Report a Bug | By Email