RESET_STREAM or STOP_SENDING to terminate a push?
Ryan Hamilton <rch@google.com> Tue, 03 September 2019 17:33 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 480531208D8 for <quic@ietfa.amsl.com>; Tue, 3 Sep 2019 10:33:41 -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 kBIeu4Qrodpt for <quic@ietfa.amsl.com>; Tue, 3 Sep 2019 10:33:39 -0700 (PDT)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 CFE49120867 for <quic@ietf.org>; Tue, 3 Sep 2019 10:33:38 -0700 (PDT)
Received: by mail-wm1-x334.google.com with SMTP id y135so550565wmc.1 for <quic@ietf.org>; Tue, 03 Sep 2019 10:33:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=eYDn3vwg7jI+AMovVqHfHgvK23BwTcQYMtyUQ/BGDHQ=; b=ZwryNKx/lAocqCdUY5cKrQebc5hEe3n39k99e/FOz92xsdshpB96hxZsHY2Py4T0aQ +62baluj/qY77OAAjzCqn7eqAiZeqtwnxOEBds3MQGDnOxYQDPz53QH2pys1swYJ3+3Z MKEeYU+DcGhs/xbhp8z4uUWSduwhNUr8M9/bLaPKjzbb3+sZzsdGxRLYD1ZmvZGEcoZW kK0/DTo9A/9xndys7XWMUfcSUOMbPIxCZGfo04eq6Z6ewAktjz2TRQkM8tNZi6rQkjzt K4DKuQvJkwzusqH2MZbtk8Wk8g4Wn9JOaaakN96PbaTxwXw7YUFH7jfudq5GIu1OqK4T n2Ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=eYDn3vwg7jI+AMovVqHfHgvK23BwTcQYMtyUQ/BGDHQ=; b=mtalz8kt1Ofl0u6pa5N/zcTQdqi0Cmehl9ajdwipcia2XsJh4HMXJbHpreuoYnL8Kj N31VnyGMoHvnUkkd0cFSBjEtNwbF5WHUzUVd+FpWU86BD53BqCpMvsu6sJl0UC/pc6He tFzJb0+ufjvQPx8IuPltrX/7IfYDOwY5c6fY4yUI02FgYZ0P0FFESo4xtQNCeN44hm1C 12ms5v7eo02iZt2mDDTQCqgbiCN6P0TVL1XYKa0ZMSTTmkJKg9LrabEIOEae9CmcXBl4 eo+r/Z2SCmxfV7IWDLKoCiKlzBRUM94bsNR3Ov3Agy8Tke/X4b5N2RB9H4KKCs2QBdC/ jVvg==
X-Gm-Message-State: APjAAAXol94ipm/jQ3Vc7Z12o6o6ViXAj2Ig0X+QedmhLBLct7Qr9PXY ogvotwbTIcEv7WWs3Xh168TfCCnGnujlYMP9YSgnkws2mhbevA==
X-Google-Smtp-Source: APXvYqzRVN4/qF+5IUAMfj2PnV+bTQt9BlPRmeS/+6JNmz8xETCFhPUfTzrx6cpNlAieVT0c/YJhIRqsfkStnCn5WZc=
X-Received: by 2002:a7b:c352:: with SMTP id l18mr593648wmj.44.1567532016244; Tue, 03 Sep 2019 10:33:36 -0700 (PDT)
MIME-Version: 1.0
From: Ryan Hamilton <rch@google.com>
Date: Tue, 03 Sep 2019 10:33:24 -0700
Message-ID: <CAJ_4DfS_wtUwSju9HHT52YQePU-SrWp4JVJVQd4+qjOeKS+i3w@mail.gmail.com>
Subject: RESET_STREAM or STOP_SENDING to terminate a push?
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000001179e0591a97d59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ODAlBmb8Ray9JEaPRyjr1aJXKI8>
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 17:33:51 -0000
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? Cheers, Ryan
- 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