[apps-discuss] APPSDIR review of draft-ietf-httpbis-method-registrations-13

S Moonesamy <sm+ietf@elandsys.com> Sun, 03 November 2013 15:06 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE8321E8096; Sun, 3 Nov 2013 07:06:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.533
X-Spam-Level:
X-Spam-Status: No, score=-103.533 tagged_above=-999 required=5 tests=[AWL=-0.934, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 JV-A+k3cYkiP; Sun, 3 Nov 2013 07:06:52 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E77A21E80AA; Sun, 3 Nov 2013 07:06:48 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.135.62]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id rA3F6TkU020305 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 3 Nov 2013 07:06:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383491201; bh=pPOa4jALFBTeN5M53rZC/w6zk1VicoewdOczN283kBg=; h=Date:To:From:Subject:Cc; b=eyNLukKLUB+hoXZGzRlhWULTh4mcBI5XSSwjjluPOvOjjpOSmBzNXv5yjWFKx1U70 OMlYbk13lUo7RDqtoGu41MvGIEe7DylZ36Rl4TJxVGcR9LvO2Y2y8HKmwTM1jCASjG Jw6Vz1w16wI43yRlFbFfkWjz2zGFITABuBGmKnG4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383491201; i=@elandsys.com; bh=pPOa4jALFBTeN5M53rZC/w6zk1VicoewdOczN283kBg=; h=Date:To:From:Subject:Cc; b=NS3+vSAAVO24U6Bl5mcuMYQQyW99PLmBoZKy1p6PJhJudyhWhBJpFdDp/l/vIZ49c XPzuARR9rAJZeRtF/FRZpcC2ivIWbSjVbkPUQpwMsuzurezCXwitbcUoeiLLIn894/ J9DeYYcv58TO+sCIvjSQIoEz6lkP70lGR9VFS2Uw=
Message-Id: <6.2.5.6.2.20131103061113.0db92cb8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 03 Nov 2013 07:01:22 -0800
To: apps-discuss@ietf.org, draft-ietf-httpbis-method-registrations.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: ietf-http-wg@w3.org, iesg@ietf.org
Subject: [apps-discuss] APPSDIR review of draft-ietf-httpbis-method-registrations-13
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Nov 2013 15:06:54 -0000

I have been selected as the Applications Area Directorate reviewer 
for this draft (for background on APPSDIR, please see 
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).

Please resolve these comments along with any other Last Call comments 
you may receive. Please wait for direction from your document 
shepherd or AD before posting a new version of the draft.

Document: draft-ietf-httpbis-method-registrations-13
Title: Initial Hypertext Transfer Protocol (HTTP) Method Registrations
Reviewer: S. Moonesamy
Review Date: November 3, 2013
IETF Last Call Date: October 21, 2013

Summary: This draft is nearly reading for publication as an Informational RFC.

The document registers those Hypertext Transfer Protocol (HTTP) 
methods which have been defined in standards-track RFCs before the 
IANA HTTP Method Registry was established.  The methods listed in the 
document is generally used for WebDAV.

Some of the HTTP methods are extensions to HTTP.  The (new) registry 
does not provide any information to distinguish between a method 
which is part of basic HTTP features and a method which is part of an 
extension to HTTP.

Major Issues: None

Minor Issues:

I suggest having the HTTP method names being registered in Section 3 
instead of Appendix A as the document is not of much use with that 
main information.

Nits:

The LINK and UNLINK HTTP methods are defined in RFC 2068 which was 
obsoleted by RFC 2616.    I gather that they are listed so that the 
method name is not reused.

Editorial nits are not included in this review.

Regards,
S. Moonesamy