IETF Logo Mail Archive

Re: Splitting transport and application error code spaces

Martin Thomson <martin.thomson@gmail.com> Thu, 17 August 2017 01:46 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 69C39132407 for <quic@ietfa.amsl.com>; Wed, 16 Aug 2017 18:46:03 -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 4ghNMKe9n9CC for <quic@ietfa.amsl.com>; Wed, 16 Aug 2017 18:46:01 -0700 (PDT)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (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 8CC2F13226B for <quic@ietf.org>; Wed, 16 Aug 2017 18:46:01 -0700 (PDT)
Received: by mail-io0-x22a.google.com with SMTP id g71so18789852ioe.5 for <quic@ietf.org>; Wed, 16 Aug 2017 18:46:01 -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=Tb1AGSV2mU3BYlQElV7ylzqCjU5EK3UrEES3nyA++/I=; b=kCV/sf+qOjE/OCJcYbqcPKmGbbwfKKvptXA5sAcN4Vlzxnwpl73P7mHNwTYGhxqjIr r76TrF1RDGwKP226BuzVrT+pUQYgiKCz2qFOIGWpxSfz+8wJranrDoNhEy2yvbAESVjY 9+qPzkcGXmPCTD5WndaGSJca2iaYt4MmimKa3E6hMQwzKycNmyCwbO8sefCyLoemh4GF /JzYnuwEaVqKrh/9h3D0Qos/u+J53QePOsUdL8uhF+9OMA7hy1MYJcTrFTAU3MZOef5Q kAM2P0KN4CnsRA8aVEzOHbFxp4QAUCrV6vpFydVfx7sScsec1JVEi7P+Y6jJZBAOyTpS WRFg==
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=Tb1AGSV2mU3BYlQElV7ylzqCjU5EK3UrEES3nyA++/I=; b=UAX6kW5vc4OuTgtmZcWwx5kLguEjpuBhNMSxHGoqgh9WvvLA0SyZ3lX5b5rNh6IPC6 Q8NYDVqH/+uDFzBLcq00r8EOcGv8NELGnhmCZzQkD4O50D+4PuKmyX6jDv/suBWGNtHX gFik5FenndzyXy2UN/KXbSAoKFsJt2Bt6BfFO7DkqiycmwGfsROTSVhYZR3dE3goi35z GnSKzMvdb757pjblPxfm0ELgrEbiuX7aQlZJ5YURBoXCq54mWBDxAMwsTD0m3OoioiI8 TrjH6Ju7MsEuT7jCxV9+3FheIDymEpPRu1Qz7GHMsytJqjXWVCv9N09JZtPmOSHGo4E0 Bw+Q==
X-Gm-Message-State: AHYfb5j23IlwKhMxUO/bI05YGg4QZDNhVfGuRSmTg/mN+emA7hnUIoLr hMpbIbcT1bz/QDOhap+PdBzrv9aPAkXl
X-Received: by 10.107.201.65 with SMTP id z62mr3688413iof.74.1502934360954; Wed, 16 Aug 2017 18:46:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.164.42 with HTTP; Wed, 16 Aug 2017 18:46:00 -0700 (PDT)
In-Reply-To: <CAN1APdfDOCahTpyzTOn7m5pL41LubUMVe_Di5oGQ0rg-TbszPQ@mail.gmail.com>
References: <CABkgnnXcjaqXeRLq=+W98HnubFSEy_DWB7PbaK8GEDUK+Wvetg@mail.gmail.com> <CY4PR21MB0136EE9B4C91C296860A38F687890@CY4PR21MB0136.namprd21.prod.outlook.com> <CABkgnnU6gP++XeByfz3ML75VCuowrDA94DvjijZxL=sRCBiOSA@mail.gmail.com> <CAGD1bZYv8LDuyOH=tP1wDk+Ja+=Yy1MYAGLUxtyB2DpBLXdqwQ@mail.gmail.com> <CABkgnnXDc8Fzh0Y6yB9BUWxtXi2kcfKTS+=znPPvuppHRdA3ZQ@mail.gmail.com> <MWHPR21MB0141C504874E7704D62BF388878D0@MWHPR21MB0141.namprd21.prod.outlook.com> <CAGD1bZbUu63JH7EvJWHdOFuNG+qivkvx_dMv=H4Vjnu1rz5tUQ@mail.gmail.com> <CAN1APdfDOCahTpyzTOn7m5pL41LubUMVe_Di5oGQ0rg-TbszPQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 17 Aug 2017 11:46:00 +1000
Message-ID: <CABkgnnXDQxuznEv2+OztOUke2FM4Ni00FAeCvErXOugDFp=68Q@mail.gmail.com>
Subject: Re: Splitting transport and application error code spaces
To: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
Cc: Jana Iyengar <jri@google.com>, Mike Bishop <michael.bishop@microsoft.com>, QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5e5SSKjDQifE2tJO6zuJxvL7huM>
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: Thu, 17 Aug 2017 01:46:03 -0000

On 16 August 2017 at 17:32, Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> wrote:
> If STOP_SENDING is moved a basic application will no longer have a language
> to communicate intent.
> This is perhaps a broader issue - but the question is: what are the minimum
> primitives a basic application with no advanced higher level protocol needs
> in order to move data on multiple streams? It relates to adding bidi streams
> on top of uni streams.

The assertion here is that STOP_SENDING isn't a necessary primitive.
And it isn't generated or consumed by the transport, even if the
effects (RST_STREAM) are.

It is useful in HTTP, so HTTP can define it.  We might see something
like that if someone ported (for example) websockets to QUIC.  I can't
see it being used for DNS.  I might speculate and say the same about
RTP, but that's so nebulous I'd likely be wrong.

v2.23.0 | Report a Bug | By Email