Re: [apps-discuss] Review of draft-levine-application-gzip-01.txt

John C Klensin <john-ietf@jck.com> Sat, 14 April 2012 16:41 UTC

Return-Path: <john-ietf@jck.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 08E7621F84DA for <apps-discuss@ietfa.amsl.com>; Sat, 14 Apr 2012 09:41:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.472
X-Spam-Level:
X-Spam-Status: No, score=-102.472 tagged_above=-999 required=5 tests=[AWL=0.127, 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 F6-VFrO4nirB for <apps-discuss@ietfa.amsl.com>; Sat, 14 Apr 2012 09:41:41 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 59FCB21F84D2 for <apps-discuss@ietf.org>; Sat, 14 Apr 2012 09:41:41 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SJ5xS-000Hvb-M6; Sat, 14 Apr 2012 12:36:18 -0400
Date: Sat, 14 Apr 2012 12:41:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: "John R. Levine" <johnl@iecc.com>
Message-ID: <867F4054B121B5FC3C414605@PST.JCK.COM>
In-Reply-To: <alpine.BSF.2.00.1204141621250.94187@joyce.lan>
References: <20120414141741.69972.qmail@joyce.lan> <A66F1731667F902A3BE63855@PST.JCK.COM> <alpine.BSF.2.00.1204141621250.94187@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Review of draft-levine-application-gzip-01.txt
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, 14 Apr 2012 16:41:42 -0000

--On Saturday, April 14, 2012 16:33 +0000 "John R. Levine"
<johnl@iecc.com> wrote:

>> Precisely because of the aggregation issue, "application/zip"
>> is a more complex case than "application/gzip" but we see a
>> lot of "application/x-zip" in the wild too.
> 
> But "application/zip" is registered.  See RFC 2912, section
> 4.5 for a suggestion about how one might say what's inside the
> ZIP file in an application/zip MIME part, and RFCs 2007 and
> 6362 for other references. I agree that in a more ideal world,
> the compression type would be in with the encoding, but that
> horse bolted 20 years ago.

Sorry.  Had lost track of application/zip.  Comments/objection
withdrawn -- this spec should not be victimized when we've
already made a worse mistake.   At some stage, we should rethink
the distinction that RFC 2045 tries to make, but I'm not
volunteering and am not going to hold my breath.

> The reason I'm doing application/gzip is that the DMARC
> project is sending reports as application/zip for something
> where gzip would be more suitable, and when I asked why, the
> document author said that application/zip is registered and
> application/gzip isn't.  So I'm levelling the playing field.

Seems reasonable.  
   john