IETF Logo Mail Archive

Re: Rationalise HTTP_WRONG_STREAM and HTTP_UNEXPECTED_FRAME

Lucas Pardue <lucaspardue.24.7@gmail.com> Wed, 07 August 2019 00:47 UTC

Return-Path: <lucaspardue.24.7@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 F06321200B2 for <quic@ietfa.amsl.com>; Tue, 6 Aug 2019 17:47:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level:
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 6FHwtYMxTXsG for <quic@ietfa.amsl.com>; Tue, 6 Aug 2019 17:47:31 -0700 (PDT)
Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (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 6426A12009C for <quic@ietf.org>; Tue, 6 Aug 2019 17:47:31 -0700 (PDT)
Received: by mail-vs1-xe2f.google.com with SMTP id m23so59586399vso.1 for <quic@ietf.org>; Tue, 06 Aug 2019 17:47:31 -0700 (PDT)
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=8NNivtKVmhtVVriViSNwhZvpFWbtQyaqdk4wmqqNC8A=; b=YJfKjHByv8XhgJ7qk82Ol2jgnzR7LjhdgHk4QGIZm04cF88UiS3EVZHzhPdN7hZiOv Zqmh0D9Eg6bZO0XN4Phw6YS22KEf5Hpnstq2b9mhFjNRa29OAMzkXWN9Mzex+tECcE8p ThCfw92G7pI/qzwqwugHoM33NHlfrygL62Kxzdz+6thsl0P3qUuc/1tNdATqqAiiRZiW 0KsN5b9f+gp4+nHFV0/f/0k1D6CvJMhVFqcu0ALxo9F0MQimUrmfbcMqbJ+NHQ8uyrJ5 5nXfMv6Sue5yQiuoFbQrhA5lRjQ8PKlvUhXqLdW0AhZ1NbT3eUgWW9dFcKc10ywLaKEd Wqjg==
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=8NNivtKVmhtVVriViSNwhZvpFWbtQyaqdk4wmqqNC8A=; b=GT4llgg0UvuFueUDpZ8FE14zViLqwRYnFr5b7r0V/ITGbXdkSiJmfSC9YTD0ZH+hUB cZ2pjj1t8hkr+T8kydT2ReF5lSLkReaJfbl9SSEpcxWQwa9jtuT/i/2eqPj2gYxQFcbc pXz8YKZUWCUtydsObDGZeyxuCE62TeIClmLImsyJdWm0zH8RjsIOVfouRTQKFeHIJAjf aMv3wG7mr2FTwJ3y/fnsFaeyAmqPy/0kP/LWM5txGyBvWyZIgdcipFfA/uWcERS3xfdW pmYiOyyg2XWZ5MGpznKG5SrMdSgDCm5cjgpBos+aoE21h62cEVMIZ6xQEVS0O0hkdw7W k/Sg==
X-Gm-Message-State: APjAAAV8PL2B2LZ2N4w5GBBMG66WKPmYTkoJNKazbBj23wmRKBQ6RQRT nt0/n1DLKetfV+9fRSICfqU/r0GUCM6222lqkGvHKw==
X-Google-Smtp-Source: APXvYqyTTbCV8EbP0G7PJYfNpWMPH9/DniL1OYrbxn0miWVF3Oeov0dOnGdcdPaOsF3wfDY+g454mh1GP0GQqsfakNo=
X-Received: by 2002:a67:d00d:: with SMTP id r13mr4390164vsi.100.1565138850466; Tue, 06 Aug 2019 17:47:30 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9ob7=MzO5qt987dpBAxBqnsMRvkrgYz7svktKsMNNhjAdw@mail.gmail.com> <608f1832-2ac3-4459-875e-bdc9a86ad8b8@www.fastmail.com>
In-Reply-To: <608f1832-2ac3-4459-875e-bdc9a86ad8b8@www.fastmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 07 Aug 2019 01:47:26 +0100
Message-ID: <CALGR9oYaKt3wD=ctrS+9PPnf3Er4Ggg9JtQkc-EHPvBbGpW_=Q@mail.gmail.com>
Subject: Re: Rationalise HTTP_WRONG_STREAM and HTTP_UNEXPECTED_FRAME
To: Martin Thomson <mt@lowentropy.net>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000034d42b058f7c49aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/TUYKbpTCethaQI5TDE4T_D7r2Is>
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 00:47:33 -0000

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