Git Issues: PING

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

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F3B421F9104 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 20 Apr 2013 12:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0DOxVqd3OyMF for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 20 Apr 2013 12:38:51 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 0573D21F8E36 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 20 Apr 2013 12:38:51 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UTdc1-0003jU-37 for ietf-http-wg-dist@listhub.w3.org; Sat, 20 Apr 2013 19:38:17 +0000
Resent-Date: Sat, 20 Apr 2013 19:38:17 +0000
Resent-Message-Id: <E1UTdc1-0003jU-37@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1UTdbx-0003ik-Sk for ietf-http-wg@listhub.w3.org; Sat, 20 Apr 2013 19:38:13 +0000
Received: from mail-ob0-f177.google.com ([209.85.214.177]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1UTdbx-0002Kr-4A for ietf-http-wg@w3.org; Sat, 20 Apr 2013 19:38:13 +0000
Received: by mail-ob0-f177.google.com with SMTP id ef5so3928943obb.36 for <ietf-http-wg@w3.org>; Sat, 20 Apr 2013 12:37:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=wI+TwuwhAdGpY/9tV2wml8Vt3tLjTYzlkCAp2I3O5oY=; b=JgDOgIvdvHmRKyXH9EhvxZUjIiB8u0XA9z/lGng4ofmX3SHaNk0Qc7v5CLcLnZs3Nu w7XWAXAVHsilX6qt6HB7nZEm+dSm+3/bby6JTpJn/dMVQ6fpuYmwvUs7rGKn4olB6Ruv UybgvrVYAmnO2frryHt96zI75FtB4oHjuZtTg39GszHIWpGSWo8B8NV3GnJxjT9Gda8L Rgl7WQGNk37TPEiKvzynSZXhR0AqtmYGhbsZiK/nTJt18kZCOA/pc3CPWV188UGrhAIf DwGorjSEB889yV14OqSIGfx94pEmK7jIymNY+75t7dh+nw9tcG2QRql/bOOSXV14FTxB 1jDA==
X-Received: by 10.60.3.71 with SMTP id a7mr7057868oea.35.1366486667018; Sat, 20 Apr 2013 12:37:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.60.3.137 with HTTP; Sat, 20 Apr 2013 12:37:26 -0700 (PDT)
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
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.679, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1UTdbx-0002Kr-4A 808fd3ad8e3b688a041c5c2062f25648
X-Original-To: ietf-http-wg@w3.org
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
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17430
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

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