Editorial Issues: Section 4.2.2

James M Snell <jasnell@gmail.com> Wed, 24 April 2013 17:13 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 58A3921F962F for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 24 Apr 2013 10:13:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.541
X-Spam-Level:
X-Spam-Status: No, score=-10.541 tagged_above=-999 required=5 tests=[AWL=0.058, 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 IjGEAshiYrOG for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 24 Apr 2013 10:13:11 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id B36B621F961E for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 24 Apr 2013 10:13:11 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UV3F7-0006mM-Kv for ietf-http-wg-dist@listhub.w3.org; Wed, 24 Apr 2013 17:12:29 +0000
Resent-Date: Wed, 24 Apr 2013 17:12:29 +0000
Resent-Message-Id: <E1UV3F7-0006mM-Kv@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 1UV3F3-0006ks-6B for ietf-http-wg@listhub.w3.org; Wed, 24 Apr 2013 17:12:25 +0000
Received: from mail-oa0-f42.google.com ([209.85.219.42]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1UV3F1-0007GH-TL for ietf-http-wg@w3.org; Wed, 24 Apr 2013 17:12:25 +0000
Received: by mail-oa0-f42.google.com with SMTP id i10so1969819oag.1 for <ietf-http-wg@w3.org>; Wed, 24 Apr 2013 10:11:58 -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=7U4NDoMP+dZJdDQU9CvlBto6cKj1m5Y2sPv7kLpOm1E=; b=0C0z+yJjHx409Y64E4oIKwdt6gnhmT6DMysQJH3MF+MF8mF82pz1lMIpVnfWbQCynt pUJGDqo8CuyBVBbmtNnukJ+rAy0G9o4CL3mBi+1Jgpbo1x0inJajlkPIYfWO+zp1zxQY dlz2J0d07U/JR+T8md23MqimoiKYOpDUPotbfV6WK0yA8l2Dpm+FHJUjtbNwkdqE89DU 7dBsz9nhV04A+xm/7+7xch86kJlzY2yj0rnwW3s+pOwmHDcc/09CWedTByhoCeFde9XY P50egC/+iPvvH1tghufeXUiGq2pEF1J43w/RHN+6rF3FL73oHOlpcRxJ8KYmIknu0+iq ix/Q==
X-Received: by 10.182.129.7 with SMTP id ns7mr13632187obb.77.1366823517985; Wed, 24 Apr 2013 10:11:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.60.3.137 with HTTP; Wed, 24 Apr 2013 10:11:37 -0700 (PDT)
From: James M Snell <jasnell@gmail.com>
Date: Wed, 24 Apr 2013 10:11:37 -0700
Message-ID: <CABP7Rbfh_V0GVameQzF-5RC+GQa7=XTQoZ3E4vZ5Uu+PL_1w8g@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.219.42; envelope-from=jasnell@gmail.com; helo=mail-oa0-f42.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.665, 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 1UV3F1-0007GH-TL d4f0d1d0bc7331c5ef71913627fa7b2b
X-Original-To: ietf-http-wg@w3.org
Subject: Editorial Issues: Section 4.2.2
Archived-At: <http://www.w3.org/mid/CABP7Rbfh_V0GVameQzF-5RC+GQa7=XTQoZ3E4vZ5Uu+PL_1w8g@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17544
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>

Current:

  ":method":  the HTTP method for this request (e.g.
  "GET", "POST", "HEAD", etc) ([HTTP-p2], Section 4)

  ":path":  ":path" - the request-target for this URI with "/"
  prefixed (see [HTTP-p1], Section 3.1.1).  For example, for
  "http://www.google.com/search?q=dogs" the path would be
  "/search?q=dogs". [[anchor26: what forms of the HTTPbis
  request-target are allowed here?]]

  These header fields MUST be present in HTTP requests.

  In addition, the following two name-value pairs MUST be present in
  every request:

  ":host":  the host and optional port portions (see [RFC3986],
  Section 3.2) of the URI for this request (e.g. "www.google.com:
  1234").  This header field is the same as the HTTP 'Host'
  header field ([HTTP-p1], Section 5.4).

  ":scheme":  the scheme portion of the URI for this request (e.g.
  "https")

Note the double ":path": ":path" : in the second paragraph.

Also, why are these split into two sections? "These... MUST be
present... In addition, the following two... MUST be present..." ..
Recommend reworking this to:

  The following fields MUST be present in all HTTP requests:

  ":method":  the HTTP method for this request (e.g.  "GET", "POST",
  "HEAD", etc) ([HTTP-p2], Section 4)

  ":path":  the request-target for this URI with "/"
  prefixed (see [HTTP-p1], Section 3.1.1).  For example, for
  "http://www.google.com/search?q=dogs" the path would be
  "/search?q=dogs". [[anchor26: what forms of the HTTPbis
  request-target are allowed here?]]

  ":host":  the host and optional port portions (see [RFC3986],
  Section 3.2) of the URI for this request (e.g. "www.google.com:
  1234").  This header field is the same as the HTTP 'Host'
  header field ([HTTP-p1], Section 5.4).

  ":scheme":  the scheme portion of the URI for this request (e.g.
  "https")

Also, I recommend removing the additional requirement given in the
paragraph that follows:

  All header field names starting with ":" (whether defined in this
  document or future extensions to this document) MUST appear before
  any other header fields.

The challenge with this is that if we go with any of the proposed
Delta-based header encoding schemes currently on the table, it is
difficult to ensure that : prefixed headers are encoded first in the
header block. It may even be counter productive to the task of
producing an optimized serialization.

- James