[ietf-types] Request for registration of application/gzip and application/zlib

"John R Levine" <johnl@taugh.com> Tue, 21 February 2012 18:54 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BC3921F88A6 for <ietf-types@ietfa.amsl.com>; Tue, 21 Feb 2012 10:54:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 5CfQzD8TwrxP for <ietf-types@ietfa.amsl.com>; Tue, 21 Feb 2012 10:54:15 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 7D32421F87F7 for <ietf-types@ietf.org>; Tue, 21 Feb 2012 10:54:10 -0800 (PST)
Received: (qmail 54378 invoked from network); 21 Feb 2012 18:54:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:vbr-info:user-agent:cleverness; s=d466.4f43e850.k1202; bh=y2hdfGlOG3x0wwXwGtHp6b7Cu/41quJEoq+jpjARWCU=; b=H29d4SMAF4xgiQFvxluS8WLBT2BRkJE+BnaVPKxcYJGyeDXtKyapVoMIguhbww+Cn2QzzJajcFycxFkaRuK2cOKKgLq8j2sU2zo12jG+qulyp/5udg5AjBdKtdkeFTivDS2x/8A8p4GsO/1QbiiRi2i9tiunuudDbUjnXXfti4I=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:vbr-info:user-agent:cleverness; s=d466.4f43e850.k1202; bh=y2hdfGlOG3x0wwXwGtHp6b7Cu/41quJEoq+jpjARWCU=; b=fWYG/UHOhr8Tg6gjVWakPpOhfDiEcKIyUVUGvI3MEI5ny+WdRpJqNpjPaYwIQkF/sQG8Nc1JmX1Brzj/USJ1zANsXDAcHdgc4gnTbfqm8P7VjbFUWH5VsIPT5UzUYR6JA2CFCU/PsNES11NNo1WzqF17u7mrGAkOEqKRUpZ8VPI=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 21 Feb 2012 18:53:45 -0000
Date: Tue, 21 Feb 2012 10:54:05 -0800
Message-ID: <alpine.BSF.2.00.1202211047280.29127@joyce.lan>
From: John R Levine <johnl@taugh.com>
To: ietf-types@ietf.org
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Subject: [ietf-types] Request for registration of application/gzip and application/zlib
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2012 18:54:27 -0000

The draft is here:

https://datatracker.ietf.org/doc/draft-levine-application-gzip/

The zlib and gzip formats are defined in RFCs 1950 and 1952. This
defines MIME types for them.

2.  The Application/Zlib Media Type

    Type name: application

    Subtype name: zlib

    Required parameters: none

    Optional parameters: none

    Encoding considerations: needs base64 or other encoding that allows
    arbitrary binary data

    Security considerations: See section [security] below

    Interoperability considerations: none

    Published specification: [RFC1950]

    Applications that use this media type: anywhere data size is an issue

    Additional information:

       Magic number(s): first byte is usually 0x78 but can also be 0x08,
       0x18, 0x28, 0x38, 0x48, 0x58, or 0x68.
       File extension(s): none
       Macintosh file type code(s): none

    Person and email address to contact for further information: see
    http://www.zlib.net/

    Intended usage: COMMON

    Restrictions on usage: none

    Author: John Levine

    Change controller: IETF

3.  The Application/Gzip Media Type

    Type name: application

    Subtype name: gzip

    Required parameters: none

    Optional parameters: none

    Encoding considerations: needs base64 or other encoding that allows
    arbitrary binary data

    Security considerations: See section [security] below

    Interoperability considerations: none

    Published specification: [RFC1952]

    Applications that use this media type: anywhere data size is an issue

    Additional information:

       Magic number(s): first two bytes are 0x1f, 0x8b.
       File extension(s): gz
       Macintosh file type code(s): none

    Person and email address to contact for further information: see
    http://www.gzip.net/

    Intended usage: COMMON

    Restrictions on usage: none

    Author: John Levine

    Change controller: IETF


4.  Security Considerations

    Zlib and gzip compression can be used to compress arbitrary binary
    data such as hostile executable code.  Also, data that purports to be
    in zlib or gzip format may not be, and fields that are supposed to be
    flags, lengths, or pointers, could contain anything.  Applications
    should treat any data with due scepticism.


Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.