Re: CRYPTO_ERROR (0x1XX) conflict with HTTP/3 Error Codes
Matt Joras <matt.joras@gmail.com> Sat, 30 November 2019 00:33 UTC
Return-Path: <matt.joras@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 12F7A1200D6 for <quic@ietfa.amsl.com>; Fri, 29 Nov 2019 16:33:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 pvTL2pkImRbQ for <quic@ietfa.amsl.com>; Fri, 29 Nov 2019 16:33:24 -0800 (PST)
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 3BBDC120033 for <quic@ietf.org>; Fri, 29 Nov 2019 16:33:24 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id y195so6772690vsy.5 for <quic@ietf.org>; Fri, 29 Nov 2019 16:33:24 -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=plrksV4ijFGKXnvXAcOD2YKFIWQcUvuWyGnokipry/Y=; b=Ul9kgFfFUKf56i8l0y0azNxB0ITK7BseliwbQmB2ebvg8pplpo6NIuF9qguBBwDQ9J hNPOTh3I35XnikgAmqJcZRQ/TfxCSuYlKuhj6xoVgTytEH3bCZfDyrfq3EnjcXf8t5L4 ITTP/xJhIsT5AvuLOe0Vd4pHPKO1ADFIoBRzm4rdz9r+lKeVGk8lFwvSG3n4p64QblqF byEAcdpKIvpmZC/r8KPmkzKCIDvACDX7co7AAauPvBYK9O4aTfhcoa750oD4dPxMJ7cF 6kD9mwA2oTZKKv1U0BammpAr/qKV53/iir7PqABU4VOZkfI/n22FfLboaVHD8wxZwDT/ kSNw==
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=plrksV4ijFGKXnvXAcOD2YKFIWQcUvuWyGnokipry/Y=; b=o38wAHAH+IRbRLT89YKgsd7RS0lH3QSGtO0pZyjsp27XIqWCagIe0UVE3CcIgRM8PP kabgPJMyRYmEGC0OqP+f/xuzyyDmJoVIV3DMdrWx1f036PWRkg6aOvKG+i/+6v/HWZjr ZqFhGPnVFdd1v1CjsAFTsSDW0etMp5FvbV8x6ES5ive1M5gaVwPSb/LbhLwDZyAx3Zlq cSJ3LdfV6pno5+2BZDxlNraqtNb01gJY1IoT5KA3wrH+n+HOmfC9L8xXntuPpnvB0TgS dtRh5dgqwWHuAdshconbqP+1HLws3Qb7B2Ydilucsgd/ZwCTkHVDqPjQWKOJbBNsuJ4V ilZQ==
X-Gm-Message-State: APjAAAXV9WOsXkpSMp2kZCT6j1E0vr4sM0sMof7WnUiCQLOJ9M1RWu8i sbE9SjIVw96GwQanS5deQZToYkn+n4NLXDlL/8Q=
X-Google-Smtp-Source: APXvYqzD4vdVzhtU2bYyx/ZrjI2AF4e6ldwJlJbqBgk1cJXycGR9KmK0JFlGdhY0PCP5tIePAYyTk8ltteEi0KIsFkg=
X-Received: by 2002:a67:ee49:: with SMTP id g9mr34481979vsp.105.1575074002860; Fri, 29 Nov 2019 16:33:22 -0800 (PST)
MIME-Version: 1.0
References: <CAG9+TpaFDpoPCXkLVBRMYUF4sCcFqzEeuNSFX4n2VY3A0LN09A@mail.gmail.com>
In-Reply-To: <CAG9+TpaFDpoPCXkLVBRMYUF4sCcFqzEeuNSFX4n2VY3A0LN09A@mail.gmail.com>
From: Matt Joras <matt.joras@gmail.com>
Date: Fri, 29 Nov 2019 16:33:11 -0800
Message-ID: <CADdTf+jOgQK-A5kX+ubiY+XdW9n26KLyzxicW-9iLEDMLoF1jA@mail.gmail.com>
Subject: Re: CRYPTO_ERROR (0x1XX) conflict with HTTP/3 Error Codes
To: Jiuhai Zhang <jiuhai.zhang@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/eOt6crVxNs9c6IJtgxc0NtxYCBw>
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: Sat, 30 Nov 2019 00:33:26 -0000
On Fri, Nov 29, 2019 at 5:04 AM Jiuhai Zhang <jiuhai.zhang@gmail.com> wrote: > > Transport error CRYPTO_ERROR (0x1XX) > HTTP/3 error range 0x100 from 0x110 They're different spaces, in the case of a close they are distinguished by which variant of the CONNECTION_CLOSE frame carries the error. See: https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#connection-errors https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#frame-connection-close https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#error-codes https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#app-error-codes
- CRYPTO_ERROR (0x1XX) conflict with HTTP/3 Error C… Jiuhai Zhang
- Re: CRYPTO_ERROR (0x1XX) conflict with HTTP/3 Err… Matt Joras