Re: RESET_STREAM or STOP_SENDING to terminate a push?
Ryan Hamilton <rch@google.com> Tue, 03 September 2019 19:55 UTC
Return-Path: <rch@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 5D85B120077 for <quic@ietfa.amsl.com>; Tue, 3 Sep 2019 12:55:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Level:
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] 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 W5e7zkigTolk for <quic@ietfa.amsl.com>; Tue, 3 Sep 2019 12:55:16 -0700 (PDT)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (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 BEBCE120043 for <quic@ietf.org>; Tue, 3 Sep 2019 12:55:15 -0700 (PDT)
Received: by mail-wm1-x32e.google.com with SMTP id r17so815464wme.0 for <quic@ietf.org>; Tue, 03 Sep 2019 12:55:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EX+u90lvzmHoIrLavtvoz9seGPrJzriFTHQSqlfCI3w=; b=gcBjbDg0Vl1hOM+adAL12xjxIXzcCj5OOzGZPoYoa4g3PF/kxFWyg0+bCs8UK0q1s4 9NAyuBW4/svEVxFTnHRlFVhMNo/lff3vStNm4OD/kdMTyAC5XarzeFxKwYro8XuOIF4W w722AiLv2ZLQkA1KDkrx9FTnYpKwVqv8qAX2Lj5vPYT3P3qqEK2PWsqX9rvd2b8AYmRU lRODS0cJJU3bO4EjZ81WLli5C/p3jSc2s9FmIcRfFQ3TnGC969OTBp4mCrkPEbWP+5+m 7Ex7Gz3+ONBwjJE74njUh54/Asa6PLswGOE3iXcGHK/RVJE1W1AltcM4g8ZdCRgo0yLL I6DQ==
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=EX+u90lvzmHoIrLavtvoz9seGPrJzriFTHQSqlfCI3w=; b=ZZiVKJOvcMIksBLaLpTrl6q1ZuTVOi+LLq5+9hDgA7Ou45rGFejbjaeIDefOFcVd9l zJyXImCsj64ioD9n5iy4hqHoGVJT4qb2oqYoZ0Q5wuBoH1/fvwb5pqtP/bqndgVbqNIL ofC1lHoCYu865uTE/RQLwE/9AB8cIHKftAM28dEqsT8cnoBZ6pdabNCyT68tWO7T1wWE mO9bjMCJQd/W5qI5t/MtlPe8+90AIt3ec71XkKvS7je8zNoHqWTWwLL3LKYEnZXmybA7 afpj7D3vABgofJl9F58nc2mlWhCUvq+Yb9Qp0o97X4WwcgLa8kptvFJoFyw7azlhlYxl qacw==
X-Gm-Message-State: APjAAAWJlGTmG6quHcHsXGL3E9iJo5xpl88/a9lgBvaqRWFh2QmqopPq RyiR5ibAukWEBr9YjyjH8C2DByXrwyQZKHfcryVE+w==
X-Google-Smtp-Source: APXvYqygqZIBdkI2c+lsd04T+rA1w1YrgG2ipf0mZhEgXhhyAk1Rfvm2RO2ntsH4G8uIX/glIT68EJARxFIYPJjjVZ4=
X-Received: by 2002:a1c:a383:: with SMTP id m125mr1284330wme.57.1567540513769; Tue, 03 Sep 2019 12:55:13 -0700 (PDT)
MIME-Version: 1.0
References: <CAJ_4DfS_wtUwSju9HHT52YQePU-SrWp4JVJVQd4+qjOeKS+i3w@mail.gmail.com> <CALGR9oZ-==nUOpPzVE3Dkb4DOb61xPOUOJcYzWYNBSWM3Af87w@mail.gmail.com>
In-Reply-To: <CALGR9oZ-==nUOpPzVE3Dkb4DOb61xPOUOJcYzWYNBSWM3Af87w@mail.gmail.com>
From: Ryan Hamilton <rch@google.com>
Date: Tue, 03 Sep 2019 12:55:01 -0700
Message-ID: <CAJ_4DfRLhCwzRFEAAEGaJhun0FL1RVG4q+wOaBpU11NCo626zQ@mail.gmail.com>
Subject: Re: RESET_STREAM or STOP_SENDING to terminate a push?
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007f0ed80591ab77cc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/pVMGwAx6n0likpmTqbzedkClUL4>
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 19:55:19 -0000
On Tue, Sep 3, 2019 at 11:00 AM Lucas Pardue <lucaspardue.24.7@gmail.com> wrote: > 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. > Ah! Yes of course. Thanks.
- RESET_STREAM or STOP_SENDING to terminate a push? Ryan Hamilton
- Re: RESET_STREAM or STOP_SENDING to terminate a p… Lucas Pardue
- Re: RESET_STREAM or STOP_SENDING to terminate a p… Ryan Hamilton
- RE: RESET_STREAM or STOP_SENDING to terminate a p… Mike Bishop