Re: Git Issues: PING

James M Snell <jasnell@gmail.com> Sat, 20 April 2013 21:58 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 C2FB521F92CB for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 20 Apr 2013 14:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level:
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 k3P2t++Z1BBk for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 20 Apr 2013 14:58:15 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB2B21F92B7 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 20 Apr 2013 14:58:15 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UTfmH-0004de-48 for ietf-http-wg-dist@listhub.w3.org; Sat, 20 Apr 2013 21:57:01 +0000
Resent-Date: Sat, 20 Apr 2013 21:57:01 +0000
Resent-Message-Id: <E1UTfmH-0004de-48@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1UTfmD-0004cu-GZ for ietf-http-wg@listhub.w3.org; Sat, 20 Apr 2013 21:56:57 +0000
Received: from mail-ob0-f170.google.com ([209.85.214.170]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1UTfmC-0001nu-Sf for ietf-http-wg@w3.org; Sat, 20 Apr 2013 21:56:57 +0000
Received: by mail-ob0-f170.google.com with SMTP id eh20so3370328obb.29 for <ietf-http-wg@w3.org>; Sat, 20 Apr 2013 14:56:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=zOaOq6+5l9OtNtct1y6QiLM9gPl6e8gZONdlEBt41ks=; b=qTzwxrA25vk7B/kpB8cWKETWd3gS2aFhFMtD32u+vwmSs/wBqzQaqDWOC0gmVH0e4Z BrO1eLChVuo+8e8DLOCw66A2kYxGIL0qoic4IRGSibhTHxRl8/5TrCy7aAPZpXjHVtDD zVFq4nrSKwmoo6Hkpt5cfyfNaqHjKfm1pPyWB1F0STEd8SSfeA8f98QQvVEqPa+jCu6d sLmh9zFIOWCQCgK/YNoBuhLxNxXwFT0En6+54/j21bQJhAcuweE6PzH5rBwwR6wfqHkn Y5O+lzm+dZfy/gRfSLEAYwWg8Ls7LLwoZ2urm5nX3YWgrzSNUsRa5oykvKye9cr8oePo jBsw==
X-Received: by 10.60.60.227 with SMTP id k3mr12121802oer.97.1366494990715; Sat, 20 Apr 2013 14:56:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.60.3.137 with HTTP; Sat, 20 Apr 2013 14:56:10 -0700 (PDT)
In-Reply-To: <CAA4WUYhpOtHhH8kwHN3aK4=tT4LLdP+p6fTQuogWB9abBAhURw@mail.gmail.com>
References: <CABP7RbeTgHaHVuoJPD=LNgEij4_+k8KQg4ni6oDn=Cuw6qsCWg@mail.gmail.com> <CAA4WUYhpOtHhH8kwHN3aK4=tT4LLdP+p6fTQuogWB9abBAhURw@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Sat, 20 Apr 2013 14:56:10 -0700
Message-ID: <CABP7RbcdGeBKfQke=NocROhow9kSuV4MOQvP4MMJrwzP7ip56Q@mail.gmail.com>
To: =?UTF-8?B?V2lsbGlhbSBDaGFuICjpmYjmmbrmmIwp?= <willchan@chromium.org>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, Jeff Pinner <jpinner@twitter.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=209.85.214.170; envelope-from=jasnell@gmail.com; helo=mail-ob0-f170.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: lisa.w3.org 1UTfmC-0001nu-Sf 66a9079749ea78969e109ad6786ab462
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Git Issues: PING
Archived-At: <http://www.w3.org/mid/CABP7RbcdGeBKfQke=NocROhow9kSuV4MOQvP4MMJrwzP7ip56Q@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17437
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>

The main argument I've seen for allowing a payload is so that the PING
sender can include a stronger correlation token than just the ID (a
timestamp, for instance).

On Sat, Apr 20, 2013 at 1:51 PM, William Chan (陈智昌)
<willchan@chromium.org> wrote:
> +jpinner who filed the issue
>
> Unless anyone comes up with a motivating reason to add arbitrary payloads,
> let's just disallow them. This is what the SPDY/2 spec originally did
> (http://dev.chromium.org/spdy/spdy-protocol/spdy-protocol-draft2#TOC-PING):
> "Length: This frame is always 4 bytes long."
>
> Unless I missed a PING discussion elsewhere, it looks refactoring
> accidentally introduced a semantic change. Let's fix that.
>
>
> On Sat, Apr 20, 2013 at 12:37 PM, James M Snell <jasnell@gmail.com> wrote:
>>
>> 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
>>
>