Git Issues: PING

James M Snell <jasnell@gmail.com> Sat, 20 April 2013 19:38 UTC

Resent-Date: Sat, 20 Apr 2013 19:38:17 +0000
Resent-Message-Id: <E1UTdc1-0003jU-37@frink.w3.org>
MIME-Version: 1.0
From: James M Snell <jasnell@gmail.com>
Date: Sat, 20 Apr 2013 12:37:26 -0700
Message-ID: <CABP7RbeTgHaHVuoJPD=LNgEij4_+k8KQg4ni6oDn=Cuw6qsCWg@mail.gmail.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.214.177; envelope-from=jasnell@gmail.com; helo=mail-ob0-f177.google.com
Subject: Git Issues: PING
Archived-At: <http://www.w3.org/mid/CABP7RbeTgHaHVuoJPD=LNgEij4_+k8KQg4ni6oDn=Cuw6qsCWg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

Per https://github.com/http2/http2-spec/issues/68 ...

The question is: "In the current draft, the PING frame requires the
server to resend an arbitrarily large payload.... Perhaps restrict the
length of the PING frame to 0, allow any stream identifier in the
header require the server to echo the identifier? ... I'm not sure
what benefit being able to echo arbitrary contents provides."

Placing a cap on the size of the Ping payload makes sense. Whether
that cap should be strictly mandated by the spec or established via
SETTINGS is an open question, however. Perhaps the spec ought to place
a strict upper limit and allow recipients to optionally specify a more
restrictive value via SETTINGS?

- James

Git Issues: PING James M Snell
Re: Git Issues: PING William Chan (陈智昌)
Re: Git Issues: PING James M Snell
Re: Git Issues: PING Jeff Pinner
Re: Git Issues: PING James M Snell