[quicwg/base-drafts] No normative language for connection/stream operations (#3935)
Martin Thomson <notifications@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 A2ED53A080A for <quic-issues@ietfa.amsl.com>; Tue, 21 Jul 2020 16:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level:
X-Spam-Status: No, score=-3.099 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, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-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 2OI5iMmTKgoG for <quic-issues@ietfa.amsl.com>; Tue, 21 Jul 2020 16:34:55 -0700 (PDT)
Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61E363A080E for <quic-issues@ietf.org>; Tue, 21 Jul 2020 16:34:55 -0700 (PDT)
Received: from github-lowworker-a6a2749.va3-iad.github.net (github-lowworker-a6a2749.va3-iad.github.net [10.48.16.62]) by smtp.github.com (Postfix) with ESMTP id 13B59261857 for <quic-issues@ietf.org>; Tue, 21 Jul 2020 16:34:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1595374495; bh=M87f2VGU1G7BRRNRkC5mmFJbWILAjBB2T9ak2JAdGWE=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ehmP7Hnh41t12PW9V1SPh9G4QVeVZf3EQgAA4vvgAYgreMVlpVpbfS+DaTIXpHY/I 2On5EMK21lwIEYqftTV8EuKK6XVNXYV8IsL71HQ6OpFV3wqFlSJNMi8ndHajvlPp2/ BfHV2euR0lsC6JpdpP439BxIcSJGcRejAjc5GXyA=
Date: Tue, 21 Jul 2020 16:34:54 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK75MOTVUSFGEMF3BBN5ENOJ5EVBNHHCPCSANM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3935@github.com>
Subject: [quicwg/base-drafts] No normative language for connection/stream operations (#3935)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f177b9ec1e00_1e3d3fd73a0cd96496766"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/1svEAK5OSLoBoFGMY16i0kj-RrQ>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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:57 -0000
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. You can view, comment on, or merge this pull request online at: https://github.com/quicwg/base-drafts/pull/3935 -- Commit Summary -- * No normative language for connection/stream operations -- File Changes -- M draft-ietf-quic-transport.md (43) -- Patch Links -- https://github.com/quicwg/base-drafts/pull/3935.patch https://github.com/quicwg/base-drafts/pull/3935.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/pull/3935
- [quicwg/base-drafts] No normative language for co… Martin Thomson
- Re: [quicwg/base-drafts] No normative language fo… Jana Iyengar
- Re: [quicwg/base-drafts] No normative language fo… ianswett
- Re: [quicwg/base-drafts] No normative language fo… Martin Thomson
- Re: [quicwg/base-drafts] No normative language fo… Martin Thomson
- Re: [quicwg/base-drafts] No normative language fo… Martin Thomson
- Re: [quicwg/base-drafts] No normative language fo… Marten Seemann
- Re: [quicwg/base-drafts] No normative language fo… Mike Bishop
- Re: [quicwg/base-drafts] No normative language fo… Jana Iyengar
- Re: [quicwg/base-drafts] No normative language fo… Kazuho Oku
- Re: [quicwg/base-drafts] No normative language fo… Christian Huitema
- Re: [quicwg/base-drafts] No normative language fo… Jana Iyengar