Re: [apps-discuss] Appsdir review of draft-reschke-http-status-308-05

Julian Reschke <julian.reschke@gmx.de> Wed, 29 February 2012 19:40 UTC

Return-Path: <julian.reschke@gmx.de>
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 7B45821F8684 for <apps-discuss@ietfa.amsl.com>; Wed, 29 Feb 2012 11:40:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.251
X-Spam-Level:
X-Spam-Status: No, score=-104.251 tagged_above=-999 required=5 tests=[AWL=-1.652, 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 GBsu3YiHkRJ6 for <apps-discuss@ietfa.amsl.com>; Wed, 29 Feb 2012 11:40:52 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 51DF121F86F0 for <apps-discuss@ietf.org>; Wed, 29 Feb 2012 11:40:52 -0800 (PST)
Received: (qmail invoked by alias); 29 Feb 2012 19:40:50 -0000
Received: from p3EE26EBB.dip.t-dialin.net (EHLO [192.168.178.36]) [62.226.110.187] by mail.gmx.net (mp071) with SMTP; 29 Feb 2012 20:40:50 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18yfu1jiZkygvgD55A/3Jo9HCJrYJx74+CcCbGakP 0jhnwW9KkPBpEx
Message-ID: <4F4E7F3F.6030107@gmx.de>
Date: Wed, 29 Feb 2012 20:40:47 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Eran Hammer <eran@hueniverse.com>
References: <90C41DD21FB7C64BB94121FBBC2E723453AFCD387F@P3PW5EX1MB01.EX1.SECURESERVER.NET>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723453AFCD387F@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [apps-discuss] Appsdir review of draft-reschke-http-status-308-05
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: Wed, 29 Feb 2012 19:40:53 -0000

On 2012-02-29 20:12, Eran Hammer wrote:
> 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-reschke-http-status-308-05
>
> Title: The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)
>
> Reviewer: Eran Hammer
>
> Review Date: 2012-02-29
>
> IETF Last Call Date: 2012-03-16
>
> Summary: This draft is ready for publication as Experimental
>
> Major Issues:
>
> None.
>
> Minor Issues:
>
> None.
>
> Nits:

Thanks!

> Section 3: I was expecting the section to read as if it was part of draft-ietf-httpbis-p2-semantics (e.g. the "missing" section 7.3.9). While all the technical information can be found in the document, it might be easier for readers to have section 3 written the same way 7.3.9 is written in draft-ietf-httpbis-p2-semantics

That's because we just did cleanup work in Part 2, and that draft hasn't 
been published yet. See 
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-latest.html#status.307>.

> Section 4: Add informative reference to current HTML specification.

OK, I can do that.

Best regards, Julian