[ietf-types] Registration of media type application/fdt+xml
Vincent Roca <vincent.roca@inria.fr> Tue, 22 May 2012 14:14 UTC
Return-Path: <vincent.roca@inria.fr>
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 ABD4121F85AC for <ietf-types@ietfa.amsl.com>; Tue, 22 May 2012 07:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.02
X-Spam-Level:
X-Spam-Status: No, score=-109.02 tagged_above=-999 required=5 tests=[AWL=-1.230, BAYES_20=-0.74, HELO_EQ_FR=0.35, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8, 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 eKFshmJbcPuu for <ietf-types@ietfa.amsl.com>; Tue, 22 May 2012 07:14:26 -0700 (PDT)
Received: from pechora2.lax.icann.org (pechora2.icann.org [IPv6:2620:0:2d0:201::1:72]) by ietfa.amsl.com (Postfix) with ESMTP id C74AE21F85D8 for <ietf-types@ietf.org>; Tue, 22 May 2012 07:14:25 -0700 (PDT)
Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by pechora2.lax.icann.org (8.13.8/8.13.8) with ESMTP id q4MEE4x0026440 for <ietf-types@iana.org>; Tue, 22 May 2012 14:14:25 GMT
X-IronPort-AV: E=Sophos;i="4.75,637,1330902000"; d="scan'208";a="144654047"
Received: from geve.inrialpes.fr ([194.199.24.116]) by mail4-relais-sop.national.inria.fr with ESMTP/TLS/AES128-SHA; 22 May 2012 16:14:02 +0200
From: Vincent Roca <vincent.roca@inria.fr>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Tue, 22 May 2012 16:14:02 +0200
Message-Id: <E1B907DE-95AD-4A43-9023-CDEF2D4BD064@inria.fr>
To: ietf-types@iana.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora2.lax.icann.org [192.0.33.72]); Tue, 22 May 2012 14:14:25 +0000 (UTC)
X-Mailman-Approved-At: Tue, 22 May 2012 07:52:08 -0700
Cc: rmt-chairs@tools.ietf.org, draft-ietf-rmt-flute-revised@tools.ietf.org, Vincent Roca <vincent.roca@inria.fr>
Subject: [ietf-types] Registration of media type application/fdt+xml
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, 22 May 2012 14:14:26 -0000
Hello, The FLUTE-revised I-D (http://tools.ietf.org/html/ietf-rmt-flute-revised-14), currently under IESG review, defines in section 8.2 the application/fdt+xml Media-Type. Comments on this registration would be greatly appreciated. Thanks! Cheers, Vincent --- Type name: application Subtype name: fdt+xml Required parameters: none Optional parameters: none Encoding considerations: The fdt+xml type consists of UTF-8 ASCII characters [RFC3629] and must be well-formed XML. Additional content and transfer encodings may be used with fdt+xml files, with the appropriate encoding for any specific file being entirely dependent upon the deployed application. Restrictions on usage: Only for usage with FDT Instances which are valid according to the XML schema of section 3.4.2. Security considerations: fdt+xml data is passive, and does not generally represent a unique or new security threat. However, there is some risk in sharing any kind of data, in that unintentional information may be exposed, and that risk applies to fdt+xml data as well. Interoperability considerations: None Published specification: The present document including section 3.4.2. The specified FDT Instance functions as an actual media format of use to the general Internet community and thus media type registration under the Standards Tree is appropriate to maximize interoperability. Applications which use this media type: Not restricted to any particular application. Any application, FLUTE included, that sends an object that consists of an FDT Instance can use this media type. Additional information: Magic number(s): none File extension(s): An FDT Instance may use the extension ".fdt" but this is not required. Macintosh File Type Code(s): none Person and email address to contact for further information: Toni Paila (toni.paila (at) nokia.com) Intended usage: Common Author/Change controller: IETF
- [ietf-types] Registration of media type applicati… Vincent Roca
- Re: [ietf-types] Registration of media type appli… Bjoern Hoehrmann
- Re: [ietf-types] Registration of media type appli… Vincent Roca