IETF Logo Mail Archive

Re: RESET_STREAM or STOP_SENDING to terminate a push?

Lucas Pardue <lucaspardue.24.7@gmail.com> Tue, 03 September 2019 17:59 UTC

Return-Path: <lucaspardue.24.7@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 1B43F1208F4 for <quic@ietfa.amsl.com>; Tue, 3 Sep 2019 10:59:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level:
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 fjictE75hpmG for <quic@ietfa.amsl.com>; Tue, 3 Sep 2019 10:59:51 -0700 (PDT)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (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 4DE38120854 for <quic@ietf.org>; Tue, 3 Sep 2019 10:59:51 -0700 (PDT)
Received: by mail-vs1-xe34.google.com with SMTP id m22so3368335vsl.9 for <quic@ietf.org>; Tue, 03 Sep 2019 10:59:51 -0700 (PDT)
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=4VPnFy1Z6lRmT8z6edXAD1RdZFxuidI0//cQZ++xUVI=; b=K6a0aAku8rQjfEUjSL1hkUgXXgyQEar2VM5/7QnXMfoGErxxJs4boQhJBVTZYU9icK S6WV8y9m3emmywXVrHSHXauRs5jF4NWPdOARNogi+bzHZHozmwyy2wEZaOh0bxPKvl/Z JqdxEzOFzSo0JPOf9KP7/IGLUl1PYC/gZd3A/zXPhlml/OMy3zHEPkmL/xE0PObp/pQm M9vM1p9UPFvS6Hyju54w2iaQvWHIpQzDKk/0Z3WPlW7AjvXWJ9tJIGBczVbZi5JO7+rD iBUWaAo7vw/IW46dOEqdDAO2rgx3RmWnxZbYBiABHrRTMU+BsmWNqTFeQX30FB0syl3R zmKA==
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=4VPnFy1Z6lRmT8z6edXAD1RdZFxuidI0//cQZ++xUVI=; b=Bu49lB81zLGJElj6472bhfHvM3asSr9xhgc50VWxgq9S+iFxiGsDAMlDfutkLrcp1Q vlTy2PzV/M3jESatHsKEylkANdFDjaE06En/jBalEtz/6D52DAxRFy6i7XypXESHzOL6 TusGwE/IYrFAGOlWkXzULsIOKOQQsnxy9TKAG9IDNU6jZ21RouEmRwhxtpHQz41k0ZUQ nuSWsxsAltELQanq/AWkqpTlbGhlRaLWsNGsixquu4PmKcnP+iBidn6/Fo0wvR2NmWlv gLAiGSSi40HfIPJBpxfQISGhZT52C+49iLDweSwghS22AwyVnSfKI7SyQV70sozkI6sy MPrQ==
X-Gm-Message-State: APjAAAVjLHgBUYlVw05xNphe0mSzdvHNUoiJgBRrvQDqRJKRy+RaQEYn 7al+bcks0xrLXBFLo+lKZI35CYapuZOGmZK4i1SWqw==
X-Google-Smtp-Source: APXvYqyXftd4wR+tOYMm7Dya7kaI15DJVxvH874tt4TNQTQQ7FQ5gTW2k6I1A4SPjY760dOo3brX0tj9mughaeFWliU=
X-Received: by 2002:a67:dc04:: with SMTP id x4mr6204862vsj.15.1567533590287; Tue, 03 Sep 2019 10:59:50 -0700 (PDT)
MIME-Version: 1.0
References: <CAJ_4DfS_wtUwSju9HHT52YQePU-SrWp4JVJVQd4+qjOeKS+i3w@mail.gmail.com>
In-Reply-To: <CAJ_4DfS_wtUwSju9HHT52YQePU-SrWp4JVJVQd4+qjOeKS+i3w@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Tue, 03 Sep 2019 18:59:39 +0100
Message-ID: <CALGR9oZ-==nUOpPzVE3Dkb4DOb61xPOUOJcYzWYNBSWM3Af87w@mail.gmail.com>
Subject: Re: RESET_STREAM or STOP_SENDING to terminate a push?
To: Ryan Hamilton <rch=40google.com@dmarc.ietf.org>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d299f20591a9da63"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/f_64tUJZv0l-OXiT_vuAT9FkDKw>
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: Tue, 03 Sep 2019 18:00:05 -0000

Hi Ryan,

On Tue, Sep 3, 2019 at 6:35 PM Ryan Hamilton <rch=
40google.com@dmarc.ietf.org> wrote:

> Howdy Folks,
>
> 7.2.4 of the http/3 spec  says
> <https://tools.ietf.org/html/draft-ietf-quic-http-22#section-7.2.4>:
>
>    Once the
>    push stream has been created, sending CANCEL_PUSH has no effect on
>    the state of the push stream.  A QUIC RESET_STREAM frame SHOULD be
>    used instead to abort transmission of the server push response.
>
>
> Since CANCEL_PUSH is sent by a client, it would seem like the frame we should recommend sending after a push stream has been created should be a frame the client can send. In this case, I think that would be STOP_SENDING. Do I have that right?
>
>
So CANCEL_PUSH is a little counterintuitive because it an be sent by either
client or server. The sentence you highlight is in the paragraph that talks
about the server's perspective - at this stage it cannot send a
STOP_SENDING because it is the sender.

Cheers
Lucas

v2.23.0 | Report a Bug | By Email