[quicwg/base-drafts] 8a1cc1: No normative language for connection/stream operat...
Martin Thomson <noreply@github.com> Tue, 21 July 2020 23:34 UTC
Return-Path: <noreply@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 57FA53A080A for <quic-issues@ietfa.amsl.com>; Tue, 21 Jul 2020 16:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 hdn7j7cAhzUk for <quic-issues@ietfa.amsl.com>; Tue, 21 Jul 2020 16:34:27 -0700 (PDT)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CFFE3A0809 for <quic-issues@ietf.org>; Tue, 21 Jul 2020 16:34:27 -0700 (PDT)
Received: from github-lowworker-a27607f.ash1-iad.github.net (github-lowworker-a27607f.ash1-iad.github.net [10.56.18.61]) by smtp.github.com (Postfix) with ESMTP id 822E2A0061 for <quic-issues@ietf.org>; Tue, 21 Jul 2020 16:34:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1595374466; bh=bfs0XbmJJ2RWzwvC6wFZcTF6oz7ug/hAgE4BrVz06o8=; h=Date:From:To:Subject:From; b=BN6cWb0B1n4h+fHh/gKYJK5iLbxSm+i4L18P0wYc0vveNERzyUaLoe7JX8/9sJP6f /wz0jkNwB03qWzTcOiAr4rH39C0BHyuaqU5SBdcdWlMm7TnkvupbLLY91PZM1OmkGO +u6xytDRWn9M0mj7m3L9n1RpXcADdXGlxE8yzl3s=
Date: Tue, 21 Jul 2020 16:34:26 -0700
From: Martin Thomson <noreply@github.com>
To: quic-issues@ietf.org
Message-ID: <quicwg/base-drafts/push/refs/heads/general-purpose-operations/000000-8a1cc1@github.com>
Subject: [quicwg/base-drafts] 8a1cc1: No normative language for connection/stream operat...
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-Auto-Response-Suppress: All
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/yvI3TsbF3KEtnpNCdc7U5zSkj6o>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 21 Jul 2020 23:34:28 -0000
Branch: refs/heads/general-purpose-operations Home: https://github.com/quicwg/base-drafts Commit: 8a1cc17e9b0f20fc50d9186de073df1a66d7c526 https://github.com/quicwg/base-drafts/commit/8a1cc17e9b0f20fc50d9186de073df1a66d7c526 Author: Martin Thomson <mt@lowentropy.net> Date: 2020-07-22 (Wed, 22 Jul 2020) Changed paths: M draft-ietf-quic-transport.md Log Message: ----------- No normative language for connection/stream operations The strong requirements here were wrong. What is necessary from these sections is defining operations in QUIC that application protocols can depend on being present. Levying the requirement on implementations was incorrect. As some application protocols don't use certain QUIC features, it is not necessary to require implementations to support features if they are not general purpose. This rephrases these requirements without normative language, instead concentrating on what services the application protocol can depend on. This translates into requirements on implementations, but only via the application protocols they intend to support. Closes #3838.
- [quicwg/base-drafts] 8a1cc1: No normative languag… Martin Thomson