September 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

RE: Review for media types: application/ibe-pp-data, application/ibe-key-request+xml, and application/ibe-pkg-reply+xml
by Turner, Sean P. 03 Oct '08

03 Oct '08

There was another update: http://www.ietf.org/internet-drafts/draft-ietf-smime-ibearch-08.txt spt >-----Original Message----- >From: stian(a)mygrid.org.uk [mailto:stian@mygrid.org.uk] On >Behalf Of Stian Soiland-Reyes >Sent: Tuesday, September 23, 2008 7:07 AM >To: Turner, Sean P. >Cc: ietf-types(a)iana.org >Subject: Re: Review for media types: application/ibe-pp-data, >application/ibe-key-request+xml, and application/ibe-pkg-reply+xml > >On Mon, Aug 11, 2008 at 21:05, Turner, Sean P. ><turners(a)ieca.com> wrote: >> The Identity-based Encryption Architecture and Supporting Data >> Structures ID, an S/MIME WG item, is seeking to register >three new media types: >> application/ibe-pp-data, application/ibe-key-request+xml, and >> application/ibe-pkg-reply+xml. We're seeking a wider >community review >> of these media types. The ID can be found at: >> >> http://www.ietf.org/internet-drafts/draft-ietf-smime-ibearch-07.txt > >I get a 404 error when trying to follow the above mentioned link. > >-- >Stian Soiland-Reyes, myGrid team >School of Computer Science >The University of Manchester

4 14

review of audio media types for G.719
by Roni Even 01 Oct '08

01 Oct '08

Hi, The AVT working group requests media type review for the g719 media type defined in section 7.1 of http://tools.ietf.org/html/draft-ietf-avt-rtp-g719-02 . This draft is currently in AVT working group last call. We would be grateful if any comments could be made by October 1st. Thanks, Roni Even (AVT co-chair)

3 2

please review "application/rif+xml"
by Sandro Hawke 29 Sep '08

29 Sep '08

The following media type registration is currently published as part of a W3C Last Call Working Draft [1] and will soon be submitted to the IESG for review, approval, and registration with IANA (as per [2]). At this point, we would appreciate comments on this registration information. If you see any problems, please let us know. (It's tempting to say a few words about RIF here, but I suppose I should let the registration stand on its own. It does includes links to the specification and to the Working Group home page.) -- Sandro [1] http://www.w3.org/TR/2008/WD-rif-bld-20080730/#Appendix:_RIF_Media_Type_Reg… [2] http://www.w3.org/2002/06/registering-mediatype ================================================================ Type name: application Subtype name: rif+xml Required parameters: none Optional parameters: charset, as per RFC 3023 (XML Media Types) Encoding considerations: same as RFC 3023 (XML Media Types) Security considerations: Systems which consume RIF documents are potentially vulnerable to attack by malicious producers of RIF documents. The vulnerabilities and forms of attack are similar to those of other Web-based formats with programming or scripting capabilities, such as HTML with embedded Javascript. Excessive Resource Use / Denial of Service Attacks Full and complete processing of a RIF document, even one conforming to the RIF-BLD dialect, may require unlimited CPU and memory resources. Through the use of "import", it may also require arbitrary URI dereferencing, which may consume all available network resources on the consuming system or other systems. RIF consuming systems SHOULD implement reasonable defenses against these attacks. Exploiting Implementation Flaws RIF is a relatively complex format, and rule engines can be extremely sophisticated, so it is likely that some RIF consuming systems will have bugs which allow specially constructed RIF documents to perform inappropriate operations. We urge RIF implementors to make systems which carefully anticipate and handle all possible inputs, including those which present syntactic or semantic errors. External (Application) Functions Because RIF may be extended with local, application defined datatypes and functions, arbitrary vulnerabilities may be introduced. Before being installed on systems which consume untrusted RIF documents, these external functions should be closely reviewed for their own vulnerabilities and for the vulnerabilities that may occur when they are used in unexpected combinations, like "cross-site scripting" attacks. In addition, as this media type uses the "+xml" convention, it shares the same security considerations as other XML formats; see RFC 3023 (XML Media Types). Interoperability considerations: This media type is intended to be shared with other RIF dialects, to be specified in the future. Interoperation between the dialects is governed by the RIF specifications. Published specification: RIF Basic Logic Dialect W3C Working Draft (Recommendation Track) http://www.w3.org/TR/rif-bld/ This media type is intended to be shared with other RIF dialects, to be specified in the future. Applications that use this media type: Unknown at the time of this draft. Multiple applications are expected, however, before the specification reaches W3C Proposed Recommendation status. Additional information: Magic number(s): As with XML in general (See RFC 3023 (XML Media Types)), there is no magic number for this format. However, the XML namespace "http://www.w3.org/2007/rif#" will normally be present in the document. It may theoretically be missing if the document uses XML entities in an obfuscatory manner. The hex form of that namespace will depend on the charset. For utf-8, the hex is: 68 74 74 70 3a 2f 2f 77 77 77 2e 77 33 2e 6f 72. File extension(s): .rif (or .xml) Macintosh file type code(s): "TEXT" (like other XML) Person & email address to contact for further information: Sandro Hawke, sandro(a)w3.org. Please send technical comments and questions about RIF to public-rif-comments(a)w3.org, a mailing list with a public archive at http://lists.w3.org/Archives/Public/public-rif-comments/ Intended usage: COMMON Restrictions on usage: None Author: The editor and contact for this media type registration is Sandro Hawke, sandro(a)w3.org. Change controller: RIF is a product of the Rule Interchange Format (RIF) Working Group of the World Wide Web Consortium (W3C). See http://www.w3.org/2005/rules/wg for information on the group. The W3C (currently acting through this working group) has change control over the RIF specification. (Any other information that the author deems interesting may be added below this line.)

2 1

test to ietf-types@iana.org
by Chris Newman 23 Sep '08

23 Sep '08

Test, please ignore. - Chris

1 0

test to ietf-types@alvestrand.no
by Chris Newman 23 Sep '08

23 Sep '08

Test, please ignore. - Chris

1 0

Request for review of media types on URC framework
by Gottfried Zimmermann 15 Sep '08

15 Sep '08

ISO/IEC 24752:2008 is a new standard on the Universal Remote Console (URC) framework which facilitates pluggable user interfaces for the control of devices and services. It defines various XML-based documents for information exchange within a control network. We (the editor and the corresponding subcommittee SC35 in ISO/IEC JTC1) are seeking feedback on a set of 5 MIME types proposed to be registered with IANA: . application/urc-uisocketdesc+xml: User Interface Socket Description (as defined in ISO/IEC 24752-2:2008) . application/urc-pret+xml: Presentation Template (as defined in ISO/IEC 24752-3:2008) . application/urc-targetdesc+xml: Target Description (as defined in ISO/IEC 24752-4:2008) . application/urc-ressheet+xml: Resource Sheet (as defined in ISO/IEC 24752-5:2008) . application/urc-resdir+xml: Resource Directory (as defined in ISO/IEC 24752-5:2008) Please see the attached files for the proposed registrations. Thanks, Gottfried ___________________________________________________ Gottfried Zimmermann, Ph.D. Phone +49 7121 790806 ICT Systems Architect under contract for: Trace R&D Center, University of Wisconsin-Madison ___________________________________________________

1 0