[quicwg/base-drafts] 27902c: Extract request cancellation from GOAWAY (#1100)

Mike Bishop <mbishop@evequefou.be> Sat, 17 February 2018 17:06 UTC

Return-Path: <bounce+565321.40f-quic-issues=ietf.org@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9FD1127AD4 for <quic-issues@ietfa.amsl.com>; Sat, 17 Feb 2018 09:06:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.25
X-Spam-Level:
X-Spam-Status: No, score=0.25 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 d5fDZoFXwIAF for <quic-issues@ietfa.amsl.com>; Sat, 17 Feb 2018 09:06:22 -0800 (PST)
Received: from m69-169.mailgun.net (m69-169.mailgun.net [166.78.69.169]) (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 A79D9126BF6 for <quic-issues@ietf.org>; Sat, 17 Feb 2018 09:06:22 -0800 (PST)
DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt; s=mailo; t=1518887182; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Subject: Message-ID: To: Reply-To: From: Date: Sender; bh=wccWFWmu3SwChAkwQIiwNIUnYmU9Xt8LJtzHhS6SIco=; b=Ur4VZS0cRvreaH6ysJelHqj6dT04cpLdHGetYTidagrgHT8IVMGDvHPbxoWzEZJY5NCXKxha dlVhGvuxV9gXIFun9UlqumWtQpROeMKA2Ity0+vK45Of1WXzBiPTmpVdtizVsi5iq3qF3iFY 6qA2A1SpG2ZjPirSeXq0nhF5U+U=
X-Mailgun-Sid: WyJhNzYyYiIsICJxdWljLWlzc3Vlc0BpZXRmLm9yZyIsICI0MGYiXQ==
X-Mailgun-Sending-Ip: 166.78.69.169
Sender: mbishop=evequefou.be@github.com
Received: from github.com (Unknown [192.30.252.35]) by mxa.mailgun.org with ESMTP id 5a88610d.7f05d84d2540-smtp-out-n03; Sat, 17 Feb 2018 17:06:21 -0000 (UTC)
Date: Sat, 17 Feb 2018 09:06:20 -0800
From: Mike Bishop <mbishop@evequefou.be>
Reply-To: Mike Bishop <mbishop@evequefou.be>
To: quic-issues@ietf.org
Message-ID: <5a88610cef471_9832b0533843c0416499a@hookshot-fe-d252ca1.cp1-iad.github.net.mail>
Subject: [quicwg/base-drafts] 27902c: Extract request cancellation from GOAWAY (#1100)
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="--==_mimepart_5a88610cef134_9832b0533843c041648a5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/AL_3-ClSvbSsKW0Xy3-nvcHUp0c>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Feb 2018 17:06:24 -0000

  Branch: refs/heads/master
  Home:   https://github.com/quicwg/base-drafts
  Commit: 27902c4be06f15bc643ed5bd7240d107605ad34f
      https://github.com/quicwg/base-drafts/commit/27902c4be06f15bc643ed5bd7240d107605ad34f
  Author: Mike Bishop <mbishop@evequefou.be>
  Date:   2018-02-17 (Sat, 17 Feb 2018)

  Changed paths:
    M draft-ietf-quic-http.md

  Log Message:
  -----------
  Extract request cancellation from GOAWAY (#1100)

Currently, all the discussion about CANCELLED requests is bound up in GOAWAY. While GOAWAY is one way that requests can be CANCELLED, there are others. This lifts out the text about request cancellation to its own section, then shortens the GOAWAY section to reference it.

I don't think there are new normative requirements here, but there are definitely some requirements that are easier to find now.