IETF Logo Mail Archive

Re: Split error codes in two

Martin Thomson <martin.thomson@gmail.com> Wed, 06 September 2017 09:55 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 AAE4D1320D9 for <quic@ietfa.amsl.com>; Wed, 6 Sep 2017 02:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, 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 fkW9vlTlk90F for <quic@ietfa.amsl.com>; Wed, 6 Sep 2017 02:55:43 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 5AA471270AB for <quic@ietf.org>; Wed, 6 Sep 2017 02:55:43 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id x190so23141912oix.3 for <quic@ietf.org>; Wed, 06 Sep 2017 02:55:43 -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:content-transfer-encoding; bh=s4xqM1AB0nOiUFVr2g8x63srC1q4KMuJ2qPm+5NIwX4=; b=eqfygaSZjnmv3xG4AM622uLxCMalQNqwcR6S6grt9kn9oUWGtEkWIBsmdyGtzOxVqb B7ttAZtOkMxp8hMFa5LsLl2ZFeghzYE2iV1GIRaDeMSXZo0RK7gA9sPLTO3e23W6/RZu PaUZAvZqdBnCzr/Xege54m246KJIDs2H3FmpUzO4gQ6DuA3sECRqmQjImtIao1NvCacr 1EtblgR9Es76q6V0WOcJsYFfBUHN5uq8qmWdZ9aYzDjB4XEA/KoELOHwgEv+5ZEaq5PQ JtP5k0e/ZM6DWRLnLZWLRn1k3YNKWvWqdblaspF94YIMLyUGO/28Q+bYZZHvzZH4wNqQ jdqw==
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:content-transfer-encoding; bh=s4xqM1AB0nOiUFVr2g8x63srC1q4KMuJ2qPm+5NIwX4=; b=FvK/QsONowTWnwjV3qs2o1aJV1nhHQTUhVwJiPikFcceuxTwV3Be/KbXcB4fuTSE2R qHWRWnjUvlTHos50V5l6pBsCM7ShxnYYynzULZWgpgp2rLh6t9wdoUEEDvcN+/ZRwT2X YnUBAR7Y5TsvH+ahAUJ7B4EmuJ/cHH4oOSL6g7LXoqCEVLwlVkg3IZvNEjKMj8qm0adO G49SaRYwJ1kg6Gp7KFKRxnQ0qLnrCTQ2oJ/Gyf2er8R5bApx44ofpEpKrT7OMuYrgYjM cd27Hrz9I5w6K2Ev3D9lDQgI42EHnPaF3I2qb/72MRoNwnJjXt3iVcQo/w97DR7RRjZb RgYw==
X-Gm-Message-State: AHPjjUhjJHQ/HNJWZCnNt5epBQBXNMhAMZ9WbVA9ifyhpTIHDy8y5g6/ 57a8kPt3hggPzF3wOIkGKT1ppw3FDg==
X-Google-Smtp-Source: ADKCNb4Kwhmdsgw75coiUTVCn8GbHoHItc8uCmR9f/6ZyGqOzGOZL7XGIlnbB/Iwr/fm3BZJXyl20nb2dqLX7AdNl8s=
X-Received: by 10.202.93.136 with SMTP id r130mr539480oib.5.1504691742757; Wed, 06 Sep 2017 02:55:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.14.77 with HTTP; Wed, 6 Sep 2017 02:55:42 -0700 (PDT)
In-Reply-To: <05505C10-8737-4C58-BC91-E401D2659AF0@in-panik.de>
References: <CABkgnnWwGAyHzkST9o9ueVmBw3_TpJun=dv2X+HL2snXSZJgew@mail.gmail.com> <CAAZdMafBWFWtC7A60P1CMm_6nUnbW+_Tx_7re1bAo7Vx2kLdcA@mail.gmail.com> <CABkgnnWphw3k=f3==2y3AhexQCj9Py50SLSEH06nN3MN0SCerQ@mail.gmail.com> <CAAZdMacHC1HKhXMR4G9CKUOmYyQMsQBab+tampP-PG6n_jJZoA@mail.gmail.com> <CACdeXiLS7W8cJbnT=orHkcd9reH=8QqhOzxWnUEpWZmfcdvd2g@mail.gmail.com> <CAGD1bZa-h0ZVh7kUYQtG3r93eH6TqRXnQ6YXAcscCrCQHk8LeA@mail.gmail.com> <CABkgnnXMFUP_c+2r6YeJouJXanHd8tFcqDKgU=C9UF0stPcXOw@mail.gmail.com> <CAGD1bZZZG9L0_d7Tmo8vfdAx+=LU+yi97N42vKFGo82K16Zycw@mail.gmail.com> <05505C10-8737-4C58-BC91-E401D2659AF0@in-panik.de>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 06 Sep 2017 19:55:42 +1000
Message-ID: <CABkgnnUC0sGy7tTuuWFgV8599PhXzOQrWAEVat1ss2CA_FO4EQ@mail.gmail.com>
Subject: Re: Split error codes in two
To: "Philipp S. Tiesel" <phils@in-panik.de>
Cc: Jana Iyengar <jri@google.com>, Victor Vasiliev <vasilvv@google.com>, QUIC WG <quic@ietf.org>, Nick Harper <nharper@google.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/uLcSNe5DI5cdmAulreGsbk3LNCc>
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: Wed, 06 Sep 2017 09:55:45 -0000

On Wed, Sep 6, 2017 at 7:16 PM, Philipp S. Tiesel <phils@in-panik.de> wrote:
> RST_STREAM is also referenced in the "Stream Errors” section and still makes sense for transport errors only effecting a single stream

The problem here is that a stream reset at the transport layer causes
loss of application layer state.  There might be some application data
that is critical (the opposite of your partially reliability use
case).  The transport dropping it would leave the application in an
indeterminate state.

v2.23.0 | Report a Bug | By Email