Re: [quicwg/base-drafts] Section 4.2.17 references HTTP_UNEXPECTED_GOAWAY which doesn't exist (#1918)

Luca Niccolini <notifications@github.com> Sat, 27 October 2018 19:22 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 5AC8E130E3B for <quic-issues@ietfa.amsl.com>; Sat, 27 Oct 2018 12:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 iBYPf1cUHFC5 for <quic-issues@ietfa.amsl.com>; Sat, 27 Oct 2018 12:22:28 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C87C12D4E7 for <quic-issues@ietf.org>; Sat, 27 Oct 2018 12:22:28 -0700 (PDT)
Date: Sat, 27 Oct 2018 12:22:26 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1540668146; bh=lV0OUxgmWlCdTaBOja2XTZ6lDaEfwMGmq5m26cOsKS0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zBd8LBRMlcZeWUzOc3MSp1U5NQyKaDc+z1nGh13z/iNdll5IpLRXxA4B9XcwE3eNC Bhn1pwAzpL85j/TTDvfdJ/bHyP410heISFu9HmItxvMBZegxqO2I7V3Nj2wUMQ2dmV uW75TmUBfJv7IsCyjaHH3cx54Rdcp19i0LHAqQdQ=
From: Luca Niccolini <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc5c3bc6c0d7c72dd60af6f978e40edfea398d11492cf0000000117ec7cf292a169ce164cfa34@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1918/433648181@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1918@github.com>
References: <quicwg/base-drafts/issues/1918@github.com>
Subject: Re: [quicwg/base-drafts] Section 4.2.17 references HTTP_UNEXPECTED_GOAWAY which doesn't exist (#1918)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bd4baf2bb7fb_13fb3ff0a66d45bc2421966"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: lnicco
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/nbt7wyy-PJxokqWKtlgThCXFZH4>
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: Sat, 27 Oct 2018 19:22:30 -0000

similar to how GOAWAY is not allowed from client to server, MAX_PUSH_ID is not allowed from server to client. 
should we use and define UNEXPECTED_MAX_PUSH_ID in the same way ? 

current text:
> A client MUST treat the receipt of a MAX_PUSH_ID frame as a connection error of type HTTP_MALFORMED_FRAME

-- 
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/issues/1918#issuecomment-433648181