[quicwg/base-drafts] What error kind is caused by multiple GOAWAYS that increase the limit (#3631)

Lucas Pardue <notifications@github.com> Wed, 06 May 2020 21:14 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 62B063A0B5A for <quic-issues@ietfa.amsl.com>; Wed, 6 May 2020 14:14:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.554
X-Spam-Status: No, score=-1.554 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id elw9bcQXijMe for <quic-issues@ietfa.amsl.com>; Wed, 6 May 2020 14:14:27 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E7753A0B59 for <quic-issues@ietf.org>; Wed, 6 May 2020 14:14:27 -0700 (PDT)
Received: from github-lowworker-2300405.va3-iad.github.net (github-lowworker-2300405.va3-iad.github.net []) by smtp.github.com (Postfix) with ESMTP id 3A0462C0B92 for <quic-issues@ietf.org>; Wed, 6 May 2020 14:14:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1588799666; bh=oy7yxLG2oVloQQ0BvHHh7+aqDRLduzTbxveCjNqL3UE=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=dOCo5Ha655XVgGnF2gJ1NhmXznsWX0CGdwTQ91YKjoZhNEzHJj90qBrmG/Fbni0ww yc2Xl94pYNs1TxVQEPJv5JTKje0LcA8WJQEn2W9noXoebUPxCf6msBiFdmN2hLuCK2 NsJaH+EyQfYtX6jkwPUc5SR7CTSOC+Vw1zAsX/mI=
Date: Wed, 06 May 2020 14:14:26 -0700
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZZBD36AZS6J6OUJ754X4E3FEVBNHHCJEYN7M@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3631@github.com>
Subject: [quicwg/base-drafts] What error kind is caused by multiple GOAWAYS that increase the limit (#3631)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5eb328b2288d7_2c3f3feadb4cd9602811d5"; 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/ufikzIVM3XU_IVsPG8LGLLUTwdw>
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, 06 May 2020 21:14:30 -0000

Draft 27 says:

   A server MAY send multiple GOAWAY frames indicating different stream IDs, but MUST NOT
   increase the value they send in the last Stream ID, since clients
   might already have retried unprocessed requests on another

Maybe I'm missing it but I can't see where we say how the GoAway receiver handles an seeing the GoAway ID getting increased. 

We typically state what the receiver should do in such a case. For instance, with MAX_PUSH_ID we say " receipt of a MAX_PUSH_ID that contains a smaller value than previously received MUST be treated as a connection error of type H3_ID_ERROR.".

I suggest that we need text that states receiving a larger GOAWAY ID than previously received MUST be treated as a connection error of type H3_ID_ERROR.

N.B. since draft-27 we landed changes to make the GOAWAY symmetrical. I believe this issue is still applicable to the most recent editors draft

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: