IETF Logo Mail Archive

Re: RST_STREAM for send-only stream

Ian Swett <ianswett@google.com> Tue, 09 January 2018 19:11 UTC

Return-Path: <ianswett@google.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 24B5C129C56 for <quic@ietfa.amsl.com>; Tue, 9 Jan 2018 11:11:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level:
X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 8Pl9WKkexkPf for <quic@ietfa.amsl.com>; Tue, 9 Jan 2018 11:11:34 -0800 (PST)
Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 9B9ED120725 for <quic@ietf.org>; Tue, 9 Jan 2018 11:11:34 -0800 (PST)
Received: by mail-it0-x234.google.com with SMTP id m11so14201088iti.1 for <quic@ietf.org>; Tue, 09 Jan 2018 11:11:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=E0ZwAPKZ2Kyxm4XfM1Fp4Cv+pcSCtFVxDvErHF8quqo=; b=dG1G7wSpLrecMFk1/fm+RQ+7mpSNdQmwx2zyZO6JoU/+aL3UoYuGPV8e3/o6l7UC1c mt19gH8pi7s80iNPFaJLh7TNkhmsJoCMLYjLk/5dcbg4WeBaIW9Nwxl66muiz7b/ZB7s uy8PkEUNPJF1zMQeKkYuhmHIGlLAxATA/Pko14NOcTmQ1ZoZZ/WEcKLz9Wlj+08xzSLs 9VXfvgJNp+RoCYINsGo+r1CZz/stOfmE9AVu5L2tNS7UAD2q/ZfeKp2gL/4VFSmXSr2F cspFJ1cho8/SGYLtXFldHajEV3XROA+DP3HIZ/1rVvYlLH5LJaSzsBKcejGQrv88jWPk EMQg==
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=E0ZwAPKZ2Kyxm4XfM1Fp4Cv+pcSCtFVxDvErHF8quqo=; b=ZQY/1nQxJP7u62+CpoFI8Sz02dK25r9IllDcwcHuUzYRmfZCb2quhpHmskNfElLWYq 59/yM858Keo/hRz/JPgPAKTEx5Q2mzFTlBe/EO4vhq3WfS/7yLZpjj+Lgb9lXS+o0Klz wPfNXMA1TFw7Bhmp1A3ZEvmUoPN2KCHW32MOonuAaD9HRjkdZ9nSDh9R2yaKlGjbWFi+ HVVnWnfxr1uSqzSlxr4ylgsVY0c/uiTu7lvERR8mazVcDeDQIx9j+tSkUOkfTntQOYPl jnpshDL77opcthmStdLrX6BxK8PEL9va9JeMK8Oh1DW/Ox1CPnKLRhh65GzFxvGN3p1x 5j3g==
X-Gm-Message-State: AKGB3mIMwe+3tKTr0S3IVCI5wvpZIKlhWIO/yRJBa3yYcil296H4aL/Q QK2ZZ75K1RWzGy7bcl8C6fSTWo5kBX4jHkrDMEsXQQ==
X-Google-Smtp-Source: ACJfBovrPS21yexoWi789tMh9XryuNz7kyohnerH8Ra8j7DDovu7Fy9YLg4X6ZRv9Ke65dRIwstzJdWbPeTQL7SwJt0=
X-Received: by 10.36.73.102 with SMTP id z99mr17419638ita.72.1515525093739; Tue, 09 Jan 2018 11:11:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.82.17 with HTTP; Tue, 9 Jan 2018 11:11:12 -0800 (PST)
In-Reply-To: <MWHPR08MB2432D80D2167110601413BFEDA100@MWHPR08MB2432.namprd08.prod.outlook.com>
References: <CAM4esxRdrumkRrPueUgz1zJUVB6Y=JX2PxZfvPn+fNHGjdUDgQ@mail.gmail.com> <MWHPR08MB2432D80D2167110601413BFEDA100@MWHPR08MB2432.namprd08.prod.outlook.com>
From: Ian Swett <ianswett@google.com>
Date: Tue, 09 Jan 2018 14:11:12 -0500
Message-ID: <CAKcm_gPBiR2QHeHVoMR-UGFaqictBXFsxZYJBdT0MZ8dAo1ygQ@mail.gmail.com>
Subject: Re: RST_STREAM for send-only stream
To: Mike Bishop <mbishop@evequefou.be>
Cc: Martin Duke <martin.h.duke@gmail.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c14e5edd084b05625cae1e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/GCbdCPHhNt32QV-2JUUbg47uHss>
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: Tue, 09 Jan 2018 19:11:36 -0000

I would think it's a fatal error, but if we allow it, 0 would be the only
valid offset, correct?

Agreed, it should be documented.

On Tue, Jan 9, 2018 at 1:59 PM, Mike Bishop <mbishop@evequefou.be> wrote:

> I could reasonably see it going either way.  If you conceive of
> unidirectional streams as starting with one direction already closed,
> re-closing the closed side is a no-op.  If you conceive of the reverse
> direction simply not existing, then the frame is invalid.
>
>
>
> Either way, we should decide and write it down.  I have no strong
> preference.
>
>
>
> *From:* QUIC [mailto:quic-bounces@ietf.org] *On Behalf Of *Martin Duke
> *Sent:* Tuesday, January 9, 2018 8:59 AM
> *To:* IETF QUIC WG <quic@ietf.org>
> *Subject:* RST_STREAM for send-only stream
>
>
>
> Is it a fatal error if I receive a RST_STREAM for my send-only stream? Is
> it PROTOCOL_VIOLATION or STREAM_STATE_ERROR? connection-level or
> stream-level? or should I drop the packet? drop the frame?
>

v2.23.0 | Report a Bug | By Email