IETF Logo Mail Archive

Re: Splitting transport and application error code spaces

Martin Thomson <martin.thomson@gmail.com> Sat, 12 August 2017 10:04 UTC

Return-Path: <martin.thomson@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 A9F441324D5 for <quic@ietfa.amsl.com>; Sat, 12 Aug 2017 03:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-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 R3jCuLuoiQjq for <quic@ietfa.amsl.com>; Sat, 12 Aug 2017 03:04:15 -0700 (PDT)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 178251324CF for <quic@ietf.org>; Sat, 12 Aug 2017 03:04:15 -0700 (PDT)
Received: by mail-it0-x22b.google.com with SMTP id 77so4689443itj.1 for <quic@ietf.org>; Sat, 12 Aug 2017 03:04:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=q+ex6CMl2iWO0T4jIj6Ml8x5UPm+pVwHONC2mOMN5xo=; b=KsTKyDHD/obAKgpMsr680JdSwkVAZUlLCPL7xtz92x3KLzRTSb7QawCHl+Iqi89Url H8eb5bwFaG/l//yv0ieNeADcb+MbTV1y/B5fpU9MZdg4+WnAzBmiy1iTr2AOAsDZQr/H UeOfHZrqjiTJdEMptSx3bIZltJmfmf1PkAPVQHbgTT+riUDB3HwqEPjYgE0X6speNCDe ePCT7iC5lvIC8ZjCjDRRnNp4QBoq1jvws1qpaNsAK5M07pEt64JeTsZdRTjp85l16DYo k29Oz0vtVKxWnYLgddhkZ7XMnExxdIiMFua84+zixdas+xKe2jJsn4MGj1RLuIPDlT3E ERyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=q+ex6CMl2iWO0T4jIj6Ml8x5UPm+pVwHONC2mOMN5xo=; b=H7Z9NVVV/UvG++JXqh6gHqXlCmsEMpj2sQ1st9vqqGtS7icMPw/YlWZ3rBoNojEnoe LmJaUKMX+K+xIqw9jjqRTf1raGfD5Um5Delh3KMlCs4lYRgiMmFlyGut79n96sZrjqWe 4azgydQLtkAcaQW1X1t7UCKyCyGrC1ls0GU4J+UWIoW7uiQo1Jm4hOKuVAzJpyu2ZAIJ GHYCuX4Hwbh4YVOdDm18HHm4ZHQjJ+gNIMme8zyNS2hNh1OeppmM8RPHOWHu4nO7Ey/Y x4/2GmeQTAa2FmuEAwiabfSa4hpnfqkd+LwSE/39DKeHUwNaviiDQw1Ij0EdJA5KTgV8 DGHQ==
X-Gm-Message-State: AHYfb5gmu9sg2GV3rksGLLTW9sQ15+0Tq82aKRVKPIzDW37GacbGwm3y 6t6L1dIEjlgROUelijW8vtfeoQ/m4g==
X-Received: by 10.36.107.68 with SMTP id v65mr1390572itc.129.1502532254470; Sat, 12 Aug 2017 03:04:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.164.42 with HTTP; Sat, 12 Aug 2017 03:04:13 -0700 (PDT)
In-Reply-To: <CY4PR21MB0136EE9B4C91C296860A38F687890@CY4PR21MB0136.namprd21.prod.outlook.com>
References: <CABkgnnXcjaqXeRLq=+W98HnubFSEy_DWB7PbaK8GEDUK+Wvetg@mail.gmail.com> <CY4PR21MB0136EE9B4C91C296860A38F687890@CY4PR21MB0136.namprd21.prod.outlook.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Sat, 12 Aug 2017 20:04:13 +1000
Message-ID: <CABkgnnU6gP++XeByfz3ML75VCuowrDA94DvjijZxL=sRCBiOSA@mail.gmail.com>
Subject: Re: Splitting transport and application error code spaces
To: Mike Bishop <Michael.Bishop@microsoft.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/CaiV81sO2w89hBWn7VZ88fbFk6c>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
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, 12 Aug 2017 10:04:16 -0000

On 12 August 2017 at 00:42, Mike Bishop <Michael.Bishop@microsoft.com> wrote:
> Given that the assigned 0x2 and 0x3 differ by one bit, might it be clearer
> to have an embedded flag in CONNECTION_CLOSE indicating the source?  That
> avoids having two frames with identical semantics except the registry in
> which you look up the value of a field.

It all amounts to the same thing, and I think that separate types is a
better trend generally.  I'm not a huge fan of the mix of discrete
types and bit patterns, preferring the former for the sake of clarity.

v2.23.0 | Report a Bug | By Email