December 2008 - Ietf-types

Registration request for MIME media type tag 3gpp-ims+xml
by John M Meredith 21 May '09

21 May '09

This proposed registration is being distributed to this list (ietf-types(a)iana.org) for preliminary review, in accordance with the instructions given by IANA. It is cc'ed, as suggested by IANA, to Chris Newman. It is also cc'ed to 3GPP delegates to TSG CT WG1 (http://www.3gpp.org/tb/home.htm, http://www.3gpp.org/tb/CT/CT1/CT1.htm) who have a technical interest in the matter. Best regards John M Meredith 3GPP Specifications Manager, ETSI ======================================================================== ======================================== > Name : John M Meredith (3GPP Specifications Manager) > Email : john.meredith&etsi.org > > > MIME media type name: > Application > > MIME subtype name: > 3gpp-ims+xml > > Required parameters: > None > > Optional parameters: > "charset" the parameter has identical semantics to the charset > parameter of the "application/xml" media type as specified in RFC > 3023 [132]. > "sv" or "schemaversion" the parameter's value is used to indicate: > - the versions of the 3GPP IM CN Subsystem XML schema that can be > used to validate the 3GPP IM CN subsystem XML body (if the MIME > type and parameter are present in the Content-Type header) or > - the accepted versions of the 3GPP IM CN Subsystem XML body (if the > MIME type and parameter are present in the Accept header). > > If the "sv" or "schemaversion" parameter is absent, it shall be > assumed that version 1 of the XML Schema for the IM CN subsystem > XML body is supported. > > This registration entry includes ABNF that modifies the m-parameter > definition in RFC 3261 [26]. m-parameter allows for > attribute/value pairs that are applicable to the media range. In > particular, the ABNF below is given for a media range > application/3gpp-ims+xml specific m-parameter. > > m-parameter /= ("sv" / "schemaversion") EQUAL LDQUOT [ sv-value- > list ] RDQUOT > sv-value-list = sv-value-range *( "," sv-value ) sv-value-range = > sv-value [ "-" sv-value ] > sv-value = number / token > number = 1*DIGIT [ "." 1*DIGIT ] > > Encoding considerations: > Same as encoding considerations of application/xml as specified in RFC > 3023 [132] > > Security considerations: > 3GPP has defined mechanisms for ensuring the privacy and integrity > protection of the bodies of SIP messages used in the 3GPP IM CN > Subsystem. > > Interoperability considerations: > This content type provides a format for exchanging information in SIP > Requests and Responses and used within the 3GPP IM CN Subsystem. > > Published specification: > ETSI TS 124 229 version 8.4.1, being a formal transposition of 3GPP TS 24.229 version 8.4.1: > "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session > Description Protocol (SDP); Stage 3" > > Available via http://pda.etsi.org/pda/home.asp?wkr=RTS/TSGC-0124229v841 (http://www.3gpp.org/ftp/Specs/html-info/24229.htm) > > Applications which use this media: > Applications that use the 3GPP IM CN Subsystem as defined by 3GPP. > > Additional information : > > 1. Magic number(s) : none > 2. File extension(s) : none > 3. Macintosh file type code : none > 4. Object Identifiers: none > > Application submitted on behalf of the Organizational Partners of > 3GPP. > > Person to contact for further information : > > 1. Name : John M Meredith, 3GPP Specifications Manager > 2. Email : john.meredith&etsi.org > > > Intended usage: > This content type provides a format for exchanging information in SIP > Requests and Responses as used within the 3GPP IM CN Subsystem. > > Author/Change controller : 3GPP Specifications Manager via > www.3gpp.org > Technical contact: jbakker&rim.com >

3 4

Media Type Registration request for POWDER and POWDER-S
by Phil Archer 22 Jan '09

22 Jan '09

To whom it may concern, This e-mail is sent in line with "How to Register an Internet Media Type for a W3C Spec" [1] and follows an earlier attempt to follow the IANA process (see 2, 3). Having taken advice [4], the W3C POWDER Working Group requests that consideration be given to registering two Media types for POWDER and POWDER-S documents. POWDER: application/powder+xml ============================== POWDER is a constrained dialect of XML that transports RDF properties and objects that can be associated with multiple subjects. The media type details are included in Appendix B of POWDER: Description Resources [5] which has just completed its (second) Last Call period. The version cited here includes changes made in response to last call comments and is not yet published, however, it is the one (or very close to the one) the working group will present as the Proposed Recommendation. It is anticipated that this happen within the next 2 weeks. The relevant section of the Description Resources document is as follows: Appendix B: POWDER Internet Media Type and Macintosh File Type The following Media Type has been submitted to the IESG for review, approval, and registration with IANA contact: Phil Archer or Matt Womer See also: How to Register a Media Type for a W3C Specification Internet Media Type registration, consistency of use TAG Finding 3 June 2002 (Revised 4 September 2002) The Internet Media Type / MIME Type for POWDER is "application/powder+xml". It is recommended that POWDER files use the file extension of .xml (all lowercase) on all platforms. It is recommended that POWDER files stored on Macintosh HFS file systems be given a file type of "TEXT". Type name: application Subtype name: powder+xml Required parameters: None Optional parameters: None Encoding considerations: Identical to those of "application/xml" as specified in [RFC3023], section 3.2. Security considerations: POWDER is used to make assertions, sometimes socially sensitive, about web resources. Consumers of POWDER should be aware of the source and chain of custody of this data. Security considerations for URIs (Section 7 of RFC 3986 [RFC3986]) and IRIs (Section 8 of RFC 3987 [RFC3987]) apply to the extent that describing resources in POWDER may prompt consumers to retrieve those resources. Interoperability considerations: There are no known interoperability issues. Published specification: http://www.w3.org/TR/powder-dr/ Applications which use this media type: No known applications currently use this media type. Additional information: Magic number(s): As specified for "application/xml" in RFC 3023 [RFC3023], section 3.2. File extension(s): .xml Fragment identifiers: Identical to that of "application/xml" as described in RFC 3023 [RFC3023], section 5. Base URI: As specified in RFC 3023 [RFC3023], section 6. Macintosh file type code(s): "TEXT" Person & email address to contact for further information: public-powderwg(a)w3.org Intended usage: COMMON Restrictions on usage: None Author/Change controller: The POWDER specification is a work product of the World Wide Web Consortium's Protocol for Web Description Resources (POWDER) Working Group. The W3C has change control over these specifications. POWDER-S: application/powder-s+xml ================================== Semantic POWDER, or POWDER-S, is typically generated by performing a transformation on a POWDER document. Each POWDER-S document is an OWL ontology from which properties and values can be inferred for a given resource. In order for inferences to be drawn, however, OWL tools must implement a semantic extension (defined separately) and it is for this reason that a new media type is requested, rather than using the existing RDF/OWL media types. A POWDER-S document is valid RDF/OWL but is essentially meaningless without the semantic extension. The media type details are included in Appendix C of POWDER: Description Resources [5] as follows: Appendix C: POWDER-S Internet Media Type and Macintosh File Type The following Media Type has been submitted to the IESG for review, approval, and registration with IANA contact: Phil Archer or Matt Womer See also: How to Register a Media Type for a W3C Specification Internet Media Type registration, consistency of use TAG Finding 3 June 2002 (Revised 4 September 2002) The Internet Media Type / MIME Type for POWDER-S is "application/powder-s+xml". It is recommended that POWDER-S files use the file extension of .rdf (all lowercase) on all platforms. It is recommended that POWDER-S files stored on Macintosh HFS file systems be given a file type of "TEXT". Type name: application Subtype name: powder-s+xml Required parameters: None Optional parameters: None Encoding considerations: Identical to those of "application/xml" as specified in [RFC3023], section 3.2. Security considerations: POWDER-S is used to make assertions, sometimes socially sensitive, about web resources. Consumers of POWDER should-S be aware of the source and chain of custody of this data. Security considerations for URIs (Section 7 of RFC 3986 [RFC3986]) and IRIs (Section 8 of RFC 3987 [RFC3987]) apply to the extent that describing resources in POWDER-S may prompt consumers to retrieve those resources. Interoperability considerations: There are no known interoperability issues. Published specification: http://www.w3.org/TR/powder-dr/ Applications which use this media type: No known applications currently use this media type. Additional information: Magic number(s): As specified for "application/xml" in RFC 3023 [RFC3023], section 3.2. File extension(s): .rdf Fragment identifiers: Identical to that of "application/xml" as described in RFC 3023 [RFC3023], section 5. Base URI: As specified in RFC 3023 [RFC3023], section 6. Macintosh file type code(s): "TEXT" Person & email address to contact for further information: public-powderwg(a)w3.org Intended usage: COMMON Restrictions on usage: None Author/Change controller: The POWDER-S specification is a work product of the World Wide Web Consortium's Protocol for Web Description Resources (POWDER) Working Group. The W3C has change control over these specifications. Please advise if there is any missing or incorrect information in this request. Yours faithfully Phil Archer POWDER WG Chair. [1] http://www.w3.org/2002/06/registering-mediatype [2] http://lists.w3.org/Archives/Public/public-powderwg/2008Dec/0001.html [3] http://lists.w3.org/Archives/Public/public-powderwg/2008Dec/0002.html [4] For example http://lists.w3.org/Archives/Public/public-powderwg/2008Dec/0026.html and http://lists.w3.org/Archives/Public/public-powderwg/2008Dec/0012.html [5] http://www.w3.org/2007/powder/Group/powder-dr/20081205.html -- Phil Archer w. http://philarcher.org/

2 2

Registration of media type image/vnd.radiance
by R Fritz 06 Jan '09

06 Jan '09

Type name: image Subtype name: vnd.radiance Required parameters: None Optional parameters: None Encoding considerations: Binary preferred. This is a binary image type with a text header; "binary" or "base64" are the only reasonable choices. Security considerations: The Radiance HDR file format does not include executable code or scripts; it is a graphics file with an ASCII header. Compression is used, which could crash an image viewer. There is no way to completely rule out the possibility of malicious content, however HDR viewer applications do not usually run with administrator privileges--they seem poor targets for such attacks. Interoperability considerations: byte orders are spelled in the published specification; we expect that Radiance HDR files will be readable on all systems. Published specification: *Radiance File Formats*, available freely at <http://radsite.lbl.gov/radiance/refer/> and also as part of Ch 18 of *Rendering With Radiance* (Booksurge/Amazon, ISBN 0974538108). Applications that use this media type: Adobe Photoshop, AHDRIA, AHDRIC, CinePaint, FDRTools, hdrgen, HDR Shop, PFStools, Photosphere, Qtpfsgui, RadDisplay, Radiance, Web HDR Additional information: Magic number(s): Text "#?RADIANCE\n" (octet sequence 23 3f 52 41 44 49 41 4e 43 45 0a) at the beginning of the file. File extension(s): pic, hdr, rgbe, xyze Macintosh file type code(s): Person & email address to contact for further information: rfritz(a)u.washington.edu Intended usage: COMMON Restrictions on usage: none Author: Randolph Fritz Change controller: Greg Ward (gregoryjward(a)gmail.com) / The Radiance Lighting Simulation Internet Group Notes: 1. The "pic" extension is also used for Macintosh PICT files; it is deprecated. 2. The rgbe and xyze extensions represent information about the content of the files, and may conflict with the actual content of files. Applications should check. 3. Radiance also uses "?RADIANCE\n" as a tag for its octree files; applications should read the file header to confirm that the file is indeed a Radiance HDR file, as described in the specification.

2 5

Registration of media type model/x3d+XXX
by Leonard Daly 05 Jan '09

05 Jan '09

Per the instructions in IETF RFC 4288, the Web3D Consortium (http://web3d.org/) is submitting model/x3d+XXX as a new MIME type. Please contact me if there are clarifications or questions. Thank you, Leonard Daly X3D WG Co-Chair, Web3D Consortium ----------------------------------------------------------- Type name: model Subtype names: x3d+vrml x3d+xml x3d+binary Required parameters: None Optional parameters: None Encoding considerations: This application represents the different MIME types used for three different encodings of the X3D ISO standard (see [1]). The standard defines an abstract information structural representation, for which several file formats are available. These formats are currently defined to be: VRML-Classic: (old-style curly brace format of the VRML97 ISO standard). UTF-8 (8-bit text) is to be supported. The recently introduced UTF-8 BOM cannot be supported by definition of the specification. XML: Encoding requirements as per the XML standards. Binary: (Effectively a binary XML encoding scheme based on the outcome of the W3C binary XML working group process). Still a work in progress and standardisation is not yet complete. Each content type may have an addition Content-Encoding to indicate whether the content has been compressed using GZIP in addition to the basic textual encoding. This is also indicated by modifying each file extension with the character "z". For example, the plaintext VRML-encoded file format would use the extension ".x3dv", and if compressed using GZIP uses the extension ".x3dvz" Security considerations: Scripting is defined as being available for the specification. Two languages are defined: Java and ECMAScript. Each scripting language is controlled by its local security model. As the content may run in many different situations, the X3D specification does not impose specific security policies. For example, some standalone applications will want to directly interact with the local file system, network or database, while others that run in a web browser would use the web-browser's security model. Interoperability considerations: The definition of the file format is maintained by the Web3d Consortium (http://www.web3d.org) and published through the ISO process. Several revisions of the specification have been made and it continues to be made. All revisions use the same MIME type definitions, and are backwards compatible internally and structurally. In addition, each of the file format encodings may be losslessly transformed between each other. Published specification: All revisions of the X3D specification can be found here: http://www.web3d.org/x3d/specifications/ Several revisions of each specification exist. The abstract specification is ISO/IEC 19775:2004. The individual file formats, which also specify the matching MIME types, are parts of the ISO/IEC 19777 specification. Applications that use this media type: There are well over 20 - both browsers, exporters and importers. Additional information: Magic number(s): x3d+vrml: “#X3D” x3d+xml: Use XML’s specification x3d+binary: “#X3D” File extension(s): x3d+vrml: .x3dv, .x3dvz x3d+xml: .x3d, .x3dz x3d+binary: .x3db Macintosh file type code(s): Person & email address to contact for further information: Leonard <mailto:Leonard> Daly (X3D Working Group Co-Chair) Leonard.Daly(a)realism.com Alan Hudson (Web3d Consortium President) giles(a)yumetech.com <mailto:giles@yumetech.com> Intended usage: COMMON Restrictions on usage: None Author: The Web3D Consortium Change controller: The Web3D Consortium The X3D standard is a continuation of the VRML standard that is defined in RFC2077. As part of this work, several large modifications were made to the file format and specification. The basic premise for the specification continues the VRML philosophy. The MIME types and file extensions were changed to indicate this modified standard. -- +-------- | Leonard Daly | Internet Solutions, eBusiness Specialist http://realism.com/ | LA ACM SIGGRAPH, Electronic Services Chair | X3D Book: http://x3dGraphics.com +------------------------------

5 4

Registration of media type for libpcap-format capture files
by Phil Vandry 20 Dec '08

20 Dec '08

Hello, We would like to register a media type (MIME type) for the file format used by the libpcap library ( http://www.tcpdump.org/ ). This file format is widely used by well-known software such as the network packet capturing packages tcpdump and Wireshark but up to now has had no official media-type to designate it. Per section 3 of RFC 4288, we believe the standards tree is the correct place for this new media type. In particular, we do not consider the vendor tree to be appropriate because there is no "vendor" that owns the type (libpcap is open source). We would like to request some clarification concerning the process established by RFC 4288 for regstering new types. Sections 3.1 and 5 state that registrations in the standards tree must either come from the IETF itself (in which case they must be published as RFCs) or from another "recognized standards body". However, the libpcap development community represents neither the IETF nor a recognized standards body, to our knowledge. How do you advise that the registration be made? Can the IETF sponsor an application that we prepare? We are considering "application/pcap-capture" or "application/pcap" for the name of the type but we have not made a decision yet (if you have a suggestion on this point we would be interested to hear it). It will not be a problem to document the file format as well as to meet the other requirements stated in RFC 4288 section 4. Thank you for your consideration. -Phil

3 2

The registration of the "vnd.3gpp.clearmode" RTP payload type at IANA
by John M Meredith 12 Dec '08

12 Dec '08

Dear All It is the intention of 3GPP to request IANA registration of the above code point. The information below is taken from annex D of 3GPP TS 29.007 v8.1.0 which will shortly be available in its entirety on the 3GPP site via http://www.3gpp.org/ftp/Specs/html-info/29007.htm . In accordance with past practice, I am sending the request via the ietf-types exploder for review and comment prior to the formal registration request. Please use the current "to" list which includes the editor of the specification concerned and the chairman and secretary of the responsible working group. Best seasonal wishes John M Meredith 3GPP Specifications Manager ================================================================================ Annex D (informative): IANA registration information for RTP payload types for SCUDIF in SIP-I based CS core network D.1 Introduction This Annex provides information required for the registration of the "vnd.3gpp.clearmode" RTP payload type at IANA. Editor´s note: MCC is requested to perform this registration on behalf of 3GPP at http://www.iana.org/cgi-bin/mediatypes.pl D.2 IANA Registartion information D.2.1 Media Type Name audio D.2.2 Subtype Name vnd.3gpp.clearmode D.2.3 Required parameters none D.2.4 Optional parameters "ptime" gives the length of time in milliseconds represented by the media in a packet, as described in RFC 4566. "maxptime" represents the maximum amount of media, which can be encapsulated in each packet, expressed as time in milliseconds, as described in IETF RFC 4566. "network-initiated-service-change" denotes if a network initiated servive change is supported or applied. It shall be used according to the rules in 3GPP TS 29.007 and 3GPP TS 23.172. No values shall be supplied for this parameter D.2.5 Encoding considerations Framed encoding. D.2.6 Security considerations See Section 6 of RFC 4040 [92] D.2.7 Interoperability considerations none D.2.8 Published specification 3GPP TS 29.007. D.2.9 Applications which use this media type Service change and UDI/RDI Fallback (SCUDIF), as defined in 3GPP TS 23.172 [83] D.2.10 Additional information This type is only defined for transfer via RTP. D.2.10.1 Magic number(s) none D.2.10.2 File extension(s) none D.2.10.3 Macintosh File Type Code(s none D.2.10.2 Object Identifier(s) or OID(s) none D.2.11 Intended usage Limited use. This RTP payload type will only be applied within a 3GPP SIP-I based circuit switched core network, as specified in 3GPP TS 23.231 [y] D.2.12 Other Information/General Comment none D.2.13 Person to contact for further information 3GPP Specifications Manager via 3gppContact(a)etsi.org

1 0

Request for two new media types submitted
by Phil Archer 03 Dec '08

03 Dec '08

To whom it may concern, On behalf of the W3C POWDER Working Group I have have today submitted two registration requests for Media Types. As cited in those requests, the key documentation is section 4 of Protocol for Web Description Resources (POWDER): Description Resources [1]. Although this is formally published as a working draft, we are close to reaching our Candidate Recommendation exit criteria and therefore expect to seek transition to Proposed Recommendation later this month. The reference numbers returned following the submissions were 208572 and 208576. These requests complement the separate request to register 'describedby' as an ATOM relationship type (currently under consideration). If I have missed any important detail or of you have any queries, please contact me, preferably copying in the POWDER WG's public mailing list. Thank you. Phil Archer POWDER WG Chair. [1] http://www.w3.org/TR/powder-dr/#assoc -- Phil Archer w. http://philarcher.org/

3 5