headers
Tom Taylor | 5 Jan 2010 02:23

Media type review for audio/fwdred

The AVT Working Group requests media type review for registration of media type 
audio/fwdred. The documentation is in draft-ietf-avt-forward-shifted-red-03.txt, 
which is in WG Last Call. We would be grateful if any comments could be received 
by January 18.

Tom Taylor
AVT Co-Chair
Permalink | Reply | 0 comments |
headers
Roni Even | 22 Jan 2010 00:11
Favicon

RE: Registration of media type application/iptv_rtsp

Hi,

 

The registration template looks OK.

 I looked at the specification ETSI 183 063 and I am not sure about the usage there

It  has m = application 9 tcp iptv_rtsp

I think it should have been m = application 9 tcp/iptv_rtsp *

 

I also saw an optional parameter "h-session" which in my view should have been in the registration request

 

Roni Even

 

 

From: ietf-types-bounces <at> alvestrand.no [mailto:ietf-types-bounces <at> alvestrand.no] On Behalf Of Miguel Angel Reina Ortega
Sent: Friday, December 04, 2009 12:22 PM
To: ietf-types <at> iana.org; iesg <at> ietf.org
Subject: Registration of media type application/iptv_rtsp

 

 Type name:

     application

 

   Subtype name:

     Standards tree - iptv_rtsp

 

   Required parameters:

     No parameters

 

   Optional parameters:

     No parameters

 

   Encoding considerations:

 

      8 bit text (this media type may require encoding on transports not capable of handling 8 bit text)

     The iptv_rtsp media type is intended to be a media descriptor

     for an RTSP content control channel. The encoding of the RTSP

     protocol is specified in RFC 2326 - Real Time Streaming Protocol

     (RTSP).

 

   Security considerations:

 

     The same security considerations apply as for the RTSP protocol,

     which is specified in RFC 2326 - Real Time Streaming Protocol

     (RTSP).

 

   Interoperability considerations:

 

     Interoperability of the RTSP protocol is specified in RFC 2326 -

     Real Time Streaming Protocol (RTSP).

 

   Published specification:

  

ETSI TS 183 063 v2.4.2 (2009-06). Available at http://pda.etsi.org/pda/queryform.asp

 

   Applications that use this media type:

 

     The iptv_rtsp media type is intended to be a media descriptor

     for an RTSP content control channel. An RTSP content control

     channel is established using SIP and the SDP offer/answer model as

     described in ETSI TS 183 063 Telecommunications and Internet

     Converged Services and Protocols for Advanced Networking (TISPAN);

     IMS-based IPTV Stage 3 Specification", ETSI TS 183 063 v2.4.2

     (2009-06).

 

 

   Additional information:

 

     Magic number(s):

       There is no single string that is always present.

     File extension(s):

       No specific file extension is recommended for this type.

     Macintosh file type code(s):

       No specific Macintosh file type codes are recommended for this

       type.

 

   Person & email address to contact for further information:

 

     MiguelAngel.ReinaOrtega <at> etsi.org on behalf of ETSI

 

   Intended usage:

     COMMON

 

   Restrictions on usage:

     No restrictions apply.

 

   Authors:

 

     the rapporteur (zhouzhipeng <zhouzp <at> HUAWEI.COM>)

      The WG chairman (Raymond.forbes <at> ericsson.com)

     

Change controller:

 

      the ETSI TO (sonia.compans <at> etsi.org)

 

 

 

 

-------------------------------------------

Miguel A. Reina Ortega

Technical Expert

Centre for Testing and Interoperability (CTI)

 

tel:    +33 (0)4 92 94 43 49

mob: +33 (0)6 76 73 60 99

web: http://www.etsi.org

 

Permalink | Reply | 0 comments |
headers
Felix Sasaki | 31 Jan 2010 20:15
Picon
Favicon

Registration of media type application/its+xml

MIME media type name:
    application

MIME subtype name:
    its+xml

Required parameters:
    none

Optional parameters:
    charset
        This parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in IETF RFC 3023.

Encoding considerations:
    Identical to those of "application/xml" as described in IETF RFC 3023, section 3.2, as applied to an ITS document.

Security considerations:
An ITS 1.0 document may cause arbitrary URIs or IRIs to be dereferenced, via the <at> xlink:href attribute at the its:rules element. Therefore, the security issues of [RFC3987] Section 8 should be considered. In addition, the contents of resources identified by file: URIs can in some cases be accessed, processed and returned as results. An implementation of ITS global rules requires the support of XPath 1.0 or its successor. Hence, processing of global rules might encompass dereferencing of URIs or IRIs during computation of XPath expressions. Arbitrary recursion is possible, as is arbitrarily large memory usage, and implementations may place limits on CPU and memory usage, as well as restricting access to system-defined functions.
ITS 1.0 permits extensions. Hence it is possible that application/its+xml may describe content that has security implications beyond those described here.

Interoperability considerations:
    There are no known interoperability issues.

Published specifications:
    http://www.w3.org/TR/2007/REC-its-20070403/

Applications which use this media type:
    This new media type is being registered to allow for deployment of ITS 1.0 on the World Wide Web.

Additional information:
    File extension:
        its
    Fragment identifiers:
        A syntax identical to that of "application/xml" as described in IETF RFC 3023.
    Base URI:
        As specified in IETF RFC 3023, section 6.
    Macintosh File Type code:
        TEXT
    Person and email address to contact for further information:
        World Wide Web Consortium <web-human <at> w3.org>

    Intended usage:
        COMMON
 
    Author/Change controller:
        The Internationalization Tag Set (ITS) 1.0 specification set is a work product of the World Wide Web Consortium's Internationalization Tag Set Working Group. The W3C has change control over this specification.

Permalink | Reply | 6 comments |
headers
Anthony Bryan | 20 Jan 2010 20:25
Picon
Gravatar

Potential media type registration: application/metalink4+xml for Metalink Download Description Format

From http://tools.ietf.org/html/draft-bryan-metalink

application/metalink4+xml MIME type

   A Metalink Document, when serialized as XML 1.0, can be identified
   with the following media type:

   MIME media type name:  application
   MIME subtype name:  metalink4+xml
   Mandatory parameters:  None.
   Optional parameters:
      "charset":  This parameter has semantics identical to the charset
         parameter of the "application/xml" media type as specified in
         [RFC3023].
   Encoding considerations:  Identical to those of "application/xml" as
      described in [RFC3023], Section 3.2.
   Security considerations:  As defined in this specification.
      In addition, as this media type uses the "+xml" convention, it
      shares the same security considerations as described in [RFC3023],
      Section 10.
   Interoperability considerations:  There are no known interoperability
      issues.
   Published specification:  This specification.
   Applications that use this media type:  No known applications
      currently use this media type.

   Additional information:
   Magic number(s):  As specified for "application/xml" in [RFC3023],
      Section 3.2.
   File extension:  .meta4
   Fragment identifiers:  As specified for "application/xml" in
      [RFC3023], Section 5.
   Base URI:  As specified in [RFC3023], Section 6.
   Macintosh File Type code:  TEXT
   Person and email address to contact for further information:  Anthony
      Bryan <anthonybryan <at> gmail.com>
   Intended usage:  COMMON
   Author/Change controller:  IESG

thank you,
--

-- 
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
  )) Easier, More Reliable, Self Healing Downloads
Permalink | Reply | 2 comments |

Gmane