IETF Logo Mail Archive

Re: [quicwg/base-drafts] Trigger unhappy (#2677)

Lucas Pardue <notifications@github.com> Wed, 08 May 2019 17:47 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 C17F6120178 for <quic-issues@ietfa.amsl.com>; Wed, 8 May 2019 10:47:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level:
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 P36_-Jwrj0AM for <quic-issues@ietfa.amsl.com>; Wed, 8 May 2019 10:47:08 -0700 (PDT)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1721F1200FC for <quic-issues@ietf.org>; Wed, 8 May 2019 10:47:08 -0700 (PDT)
Date: Wed, 08 May 2019 10:47:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557337627; bh=J2kmNA06sWInJ1B92olgR26V0fUrLyXxJFC+56uh0eI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=U6JICTvSjJjUekxGng89F0qeUQlfHXXU+MG8XN3AKspAa7dn8jQsnBeXjmXDlcs1Q ArccO7ybrkZMxxwcglKebs8jf3fq+kYOtNZyLS+zjU+PxfI4Ph+ohdxJxutuRwNdle /2GSwMA1YhH2aPRE4nTy3qmwvcwVly/T52rycJn8=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4QBWGWR5PRF4CKGHN24BEJXEVBNHHBUVH3D4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2677/c490583673@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2677@github.com>
References: <quicwg/base-drafts/pull/2677@github.com>
Subject: Re: [quicwg/base-drafts] Trigger unhappy (#2677)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd3161bbd9d_724a3fdf5b8cd960207684"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/RGGCegSMOLKZL6GTaS-sJ_okPlg>
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: Wed, 08 May 2019 17:47:10 -0000

> The reason for this language is because an HTTP implementation cannot send a QUIC frame

This rule is not applied universally in the document, probably because I didn't know about it :)

Examples:
* > If the push stream has been opened by the server, the server SHOULD send a QUIC RESET_STREAM
* > When a client sends a STOP_SENDING with HTTP_REQUEST_CANCELLED, a
   server MAY send the error code HTTP_REQUEST_REJECTED in the
   corresponding RESET_STREAM if no processing was performed.
* > an HTTP/3 client SHOULD send non-zero values for the QUIC transport
   parameters "initial_max_stream_data_bidi_local".  An HTTP/3 server
   SHOULD send non-zero values for the QUIC transport parameters
   "initial_max_stream_data_bidi_remote" and "initial_max_bidi_streams".

Suggestion welcome on how to address this consistently.

-- 
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/2677#issuecomment-490583673

v2.23.0 | Report a Bug | By Email