[ietf-types] Request for review of standards tree registration request for OpenXPS

Brian Clubb <bclubb@microsoft.com> Wed, 12 January 2011 18:55 UTC

Return-Path: <bclubb@microsoft.com>
X-Original-To: ietf-types@core3.amsl.com
Delivered-To: ietf-types@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 8FCAD3A6B48 for <ietf-types@core3.amsl.com>; Wed, 12 Jan 2011 10:55:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.576
X-Spam-Status: No, score=-10.576 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id v6-jmeDiaEIl for <ietf-types@core3.amsl.com>; Wed, 12 Jan 2011 10:55:01 -0800 (PST)
Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:1::39]) by core3.amsl.com (Postfix) with ESMTP id 5BD3A3A6B07 for <ietf-types@ietf.org>; Wed, 12 Jan 2011 10:54:59 -0800 (PST)
Received: from smtp.microsoft.com (mailb.microsoft.com []) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id p0CIuwe1008715 for <ietf-types@iana.org>; Wed, 12 Jan 2011 10:57:18 -0800
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com ( by TK5-EXGWY-E802.partners.extranet.microsoft.com ( with Microsoft SMTP Server (TLS) id; Wed, 12 Jan 2011 10:40:18 -0800
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ( by TK5EX14MLTC104.redmond.corp.microsoft.com ( with Microsoft SMTP Server (TLS) id; Wed, 12 Jan 2011 10:40:18 -0800
Received: from TK5EX14MBXW652.wingroup.windeploy.ntdev.microsoft.com ([]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([]) with mapi; Wed, 12 Jan 2011 10:40:16 -0800
From: Brian Clubb <bclubb@microsoft.com>
To: "ietf-types@iana.org" <ietf-types@iana.org>
Thread-Topic: Request for review of standards tree registration request for OpenXPS
Thread-Index: AcuyiB+gKtQ7++B2Q1KvnCMNPqoWlA==
Date: Wed, 12 Jan 2011 18:40:17 +0000
Message-ID: <FE6603D65048F44AB8F8955AE89A09B90A400D@TK5EX14MBXW652.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_FE6603D65048F44AB8F8955AE89A09B90A400DTK5EX14MBXW652win_"
MIME-Version: 1.0
X-Greylist: Delayed for 00:15:51 by milter-greylist-4.0 (pechora4.lax.icann.org []); Wed, 12 Jan 2011 10:57:18 -0800 (PST)
X-Mailman-Approved-At: Thu, 13 Jan 2011 11:30:38 -0800
Subject: [ietf-types] Request for review of standards tree registration request for OpenXPS
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 12 Jan 2011 18:55:12 -0000

To whom it may concern:

Pursuant to RFC 4288 section 5.1, I am submitting the following registration template describing the OpenXPS format for community review with the goal of adding this registration to the standards tree.  The two-week comment period will conclude on  27 January 2011.

Thank you in advance for your review and consideration!

Brian Clubb
Chairman - Ecma TC46  (Ecma 388: Open XML Paper Specification)
Microsoft Corporation

Name : Brian Clubb

Email : bclubb@microsoft.com

MIME media type name : Application

MIME subtype name : Standards Tree - OpenXPS

Required parameters : N/A

Optional parameters :

Encoding considerations : 8-bit

Security considerations :
OpenXPS uses ZIP compression as specified in .ZIP File Format Specification from PKWARE, Inc., version 6.2.0 (2004).  ZIP compressed XML requires parsing untrusted XML data and untrusted ZIP data.  consumer is responsible for validating the .zip archive, the XML structure, and the resource content.  Per spec, there should be no active content provided as part of the OpenXPS format.  The consumer must ensure that no malicious active content is erroneously provided in the OpenXPS document.  Valid content is described in the EMCA-388 specification (http://www.ecma-international.org/publications/standards/Ecma-388.htm)

Also see section E.3 of ECMA-388 specification (http://www.ecma-international.org/publications/standards/Ecma-388.htm):
OpenXPS Documents follow requirements set out in this Standard, as well as other normative references including the Open Packaging Conventions. Implementations may use the following steps to identify an unknown file or stream as an OpenXPS Document within an Open Packaging Conventions payload.
1. Test that the file or stream is a ZIP file
a. As required by §9.2 of the Open Packaging Conventions
b. First four bytes correspond to the local file header signature defined in the .ZIP File Format Specification from PKWARE, Inc., version 6.2.0 (2004)
2. Test that a valid Package Relationships zip item exists
a. As required by §8.3.4 of the Open Packaging Conventions
b. Check that the content type for the package relationships zip item is correctly defined in the Content Types stream (see OPC §8.1.2) as a relationships part
3. Test that the Package Relationships Part contains a relationship (see OPC §8.3) whose target attribute points to a valid FixedDocumentSequence Part
a. As required by §10.2 of this Standard
b. Check that the content type for the FixedDocumentSequence part is correctly defined in the Content Types stream as a FixedDocumentSequence part

Interoperability considerations :
application/OpenXPS documents are specified by the XML schemas standardized in ECMA-388.
Applications and drivers currently producing/consuming Microsoft XPS content cannot directly produce/consume OpenXPS.  Changes are required to address differences in the two specifications, such as namespace, print ticket usage, use of JPEG XR, etc.

Published specification :
The published Standard ECMA-388 is available at:

Applications which use this media :
The application/oxps MIME type can be used to identify CSTA XML (ECMA-388) instance documents.  No published applications or print drivers currently use OpenXPS.  The intent is for any application or driver that can currently produce/consume Microsoft XPS to also adopt OpenXPS.  Examples of such applications would include but are not limited to:  Microsoft XPS Viewer, Microsoft XPS Document Writer, Microsoft Internet Explorer 9.

Additional information :

1. Magic number(s) : ZIP archive CRC-32: 0xdebb20e3 per http://www.pkware.com/documents/APPNOTE/APPNOTE-6.2.0.txt
2. File extension(s) : .oxps
3. Macintosh file type code : N/A
4. Object Identifiers: N/A

Person & email address to contact for further information:
Ecma International Helpdesk
Rue du Rhone114
CH-1204 Geneva

Person to contact for further information :

1. Name : Ecma International Helpdesk
2. Email : helpdesk@ecma-international.org

Intended usage : Common
This type will be used for all documents conforming to the Open XML
   Paper Specifcation's (ECMA-388) Open XPS Document format, published
   by ECMA.

Author/Change controller : The ECMA-388 Standard is developed and
   maintained by the Ecma TC46 Working Group.