[apps-discuss] Applications Area Directorate Review of draft-levine-application-gzip-02

Julian Reschke <julian.reschke@gmx.de> Sat, 05 May 2012 08:32 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 1B97921F8546 for <apps-discuss@ietfa.amsl.com>; Sat, 5 May 2012 01:32:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 hCvRnNSjAT2k for <apps-discuss@ietfa.amsl.com>; Sat, 5 May 2012 01:32:21 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 8615B21F8543 for <apps-discuss@ietf.org>; Sat, 5 May 2012 01:32:20 -0700 (PDT)
Received: (qmail invoked by alias); 05 May 2012 08:32:18 -0000
Received: from p54BB3218.dip.t-dialin.net (EHLO [192.168.178.36]) [84.187.50.24] by mail.gmx.net (mp024) with SMTP; 05 May 2012 10:32:18 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19780sBGbB7J+AUVTzPym0yP8tRmOKaazrQVdubpK wRvg6NeX+xr/dZ
Message-ID: <4FA4E58A.2040102@gmx.de>
Date: Sat, 05 May 2012 10:32:10 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: draft-levine-application-gzip@tools.ietf.org, IETF Apps Discuss <apps-discuss@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: standards@taugh.com, The IESG <iesg@ietf.org>
Subject: [apps-discuss] Applications Area Directorate Review of draft-levine-application-gzip-02
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: Sat, 05 May 2012 08:32:22 -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-levine-application-gzip-02
Title: The application/zlib and application/gzip media types
Reviewer: Julian Reschke <julian.reschke@gmx.de>
Review Date: 2012-05-05
IETF Last Call Date: from 2012-05-03 to 2012-05-31
IESG Telechat Date: -

Summary: This document defines media types for gzip and zlib 
compression. It is ready for publication with minor editorial issues.

Major Issues: None.

Minor Issues:

The document needs an IANA Considerations Section. That Section could 
either contain the registration templates, or just reference them.

In the actual templates, I recommend the following changes:

"Published specification:" - I would make these pointers to Sections 2 
and 3 of draft-levine-application-gzip; referencing the base specs 
directly here would mean that draft-levine-application-gzip doesn't get 
referenced in the media types registry at all.

"Encoding considerations": 
<http://tools.ietf.org/html/rfc4288#section-4.8> says this should one of 
"7bit", "8bit", "framed", or "binary". So maybe change to:

"binary - needs base64 or other encoding that allows arbitrary binary 
data when transmitted over non-binary transports"

(or just say "binary").


Best regards, Julian