Return-Path: 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 38C7921F8B21 for ; Wed, 30 Nov 2011 02:40:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.287 X-Spam-Level: X-Spam-Status: No, score=0.287 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396] 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 tbOyG5pDftXd for ; Wed, 30 Nov 2011 02:40:04 -0800 (PST) Received: from pechora2.lax.icann.org (pechora2.icann.org [IPv6:2620:0:2d0:201::1:72]) by ietfa.amsl.com (Postfix) with ESMTP id 2C60421F8B06 for ; Wed, 30 Nov 2011 02:40:03 -0800 (PST) Received: from mo-p00-ob6.rzone.de (mo-p00-ob6.rzone.de [IPv6:2a01:238:20a:202:53f0::1]) by pechora2.lax.icann.org (8.13.8/8.13.8) with ESMTP id pAUAdfF3003674 for ; Wed, 30 Nov 2011 10:40:01 GMT DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1322649580; l=70622; s=domk; d=nomor.de; h=Mime-Version:To:Cc:Date:Subject:Content-Type:From:X-RZG-CLASS-ID: X-RZG-AUTH; bh=3oq2gQzpsujIMsiIdiiDtwqnj5E=; b=SGZ7QTr7W+0HW0r1zG4BgvYmjE4Cof2/J+AQIwaSt9frXhzLvG6ogMIc0YDerwT9zJl PuweknqqZndA4OQKPkUFhMZm4nS4wvywssc6QV/VkIGtqX8ri4x1BYTkJifSsKkVFsEM/ syToa9MP6Ylw2lasxbuUSdGW/2xvbhKfD7o= X-RZG-AUTH: :P3gLdkugevKirJkjH/RoTtk5THWq6nlFgKpnuMPeiu1/81cZd+MVACG0+zKN+A== X-RZG-CLASS-ID: mo00 Received: from [192.168.16.215] ([195.94.37.227]) by post.strato.de (mrclete mo31) (RZmta 26.10 AUTH) with ESMTPA id e022fdnAU91JYw ; Wed, 30 Nov 2011 11:39:33 +0100 (MET) From: Thomas Stockhammer Content-Type: multipart/alternative; boundary="Apple-Mail=_BE05AC36-F49F-49CD-8CDE-9BAD82D26C00" Date: Wed, 30 Nov 2011 11:39:35 +0100 Message-Id: To: ietf-types@iana.org Mime-Version: 1.0 (Apple Message framework v1251.1) X-Mailer: Apple Mail (2.1251.1) X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora2.lax.icann.org [IPv6:2620:0:2d0:201::1:72]); Wed, 30 Nov 2011 10:40:02 +0000 (UTC) Cc: gen-sys@lists.uni-klu.ac.at, Narasimhan Mandayam , List DASH Subject: [ietf-types] MIME type for MPEG-2 transport streams X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Nov 2011 10:40:05 -0000 --Apple-Mail=_BE05AC36-F49F-49CD-8CDE-9BAD82D26C00 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Dear experts,=20 MPEG is working in defining a generic RTP-independent MIME type for = MPEG-2 transport streams to be included as an Annex in ISO/IEC 13818-1. Please review media type registration of the MPEG-2 TS as provided = below. Please provide any comments asap, latest by December 9th. Thanks! Thomas =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 MIME type for MPEG-2 transport streams T.1 Introduction This Annex provides the formal MIME type registration for MPEG-2 = transport streams. It is referenced from the registry at = http://www.iana.org/. T.2 MIME type and subtype MIME media type name: video=20 MIME subtype name: mp2t Required parameters: none Optional parameters: The =91profiles=92 parameter as documented in Annex T.2.1 The 'codecs' parameter as document in Annex T.2.2 Encoding considerations: This type is defined for general use; for transfer via RTP = see [RFC 3550]. Security considerations: see Annex T.3 Interoperability considerations: The specification defines a platform-independent expression = of a presentation, and it is intended that wide = interoperability can be achieved. Published specification: ISO/IEC 13818-1, Information technology =97 Generic coding = of moving pictures and associated audio information: Systems Applications that use this media type: various, including video streaming and video broadcasting = applications Additional information: File extension(s): =20 .ts Intended usage: =20 COMMON Other Information/General Comment: none Person to contact for further information: Name:=20 Mandayam Narasimhan e-mail: =20 Snarasimhan@motorola.com Change controller: ISO/IEC JTC1/SC29 (MPEG) =20 T.3 Security Considerations It is possible to inject non-compliant streams (Audio, Video, and = Systems) in the transport stream to overload the receiver/decoder's = buffers. This might compromise the functionality of the receiver or = even crash it. An MPEG-2 Transport Stream is an extensible container format, and hence = might carry streams that have active aspects (e.g. contain script = snippets). If those subsystems are not properly defined or implemented, = it may be possible to crash the receiver or temporarily make it = unavailable. T.4 Parameters T.4.1 The profiles parameter =20 Parameter Name: profiles =20 Parameter Value: =20 The 'profiles' parameter is an optional parameter that indicates one or = more profiles to which the stream claims conformance. The contents of = this attribute shall conform to either the pro-simple or pro-fancy = productions of RFC6381, Section 4.5. The profile identifiers reported in = the MIME type parameter takes as value the transport_profile, coded as a = decimal integer, e.g. profiles=3D"1" for streams conforming to the = 'strict' profile. =20 Example: video/mp2t;profiles=3D"1" =20 T.4.2 The codecs parameter =20 Parameter Name: codecs =20 Parameter Value: =20 =20 The 'codecs' parameter is an optional parameter that indicates one or = more codecs which are used for the elementary streams in the MPEG-2 TS. = The contents of this attribute shall conform to either the pro-simple or = pro-fancy productions of RFC6381, Section 3.2. RFC 6381 defines =91codecs=92= parameter as a single value, or a comma-separated list of values = identifying the codec(s), where each value consists of one or more = dot-separated elements. The first element of such a value can be = derived from the value of stream_type in the program_map_section. If = the stream_type value appears in Table T-1, the value in the first = element column shall be used as the first element. If the stream_type = value is between 0x80 and 0xFF, the first element may be derived in ways = not specified by this Annex (e.g. by examining the contents of = registration_descriptor, if used). Table T-1 =96=91codecs=92 parameter values stream_type first element 0x01 mp1v 0x02 mp2v 0x03 mp1a 0x04 mp2a 0x0F mp2a 0x10 mp4v 0x11 mp4a 0x1B avc1 0x1C mp4a 0x1D tx3g 0x1F svc1 0x20 mvc1 0x21 mjp2 =20 Wherever a definition for additional elements exists in RFC 6381 for a = given first element, the definition in RFC 6381 shall be followed. When the first element of a value is =91mp2a=92 or =91mp2v=92, the = second element of the codecs parameter value is the hexadecimal = representation of the MP4 Registration Authority ObjectTypeIndication = (OTI) for the appropriate specification and profile. =20 Examples: =20 ISO/IEC 13818-2 Main Profile video/mp2ts;codecs=3D"mp2v.61" ISO/IEC 13818-3 is represented video/mp2ts;codecs=3D"mp2a.69" ISO/IEC 13818-7 Low Complexity Profile video/mp2ts;codecs=3D"mp2a.67" Dolby AC-3 audio (per ATSC A/52, AC-3 audio has = stream_type 0x81 and = format_identifier =93AC-3=94 in the registration_descriptor ) = video/mp2ts;codecs=3D"ac-3" ISO/IEC 13818-2 Main Profile Video together with ISO/IEC 13818-7 audio video/mp2ts;codecs=3D"mp2v.61,mp2a.67"= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- Dr. Thomas Stockhammer (CEO) || stockhammer@nomor.de || phone +49 89 = 978980 02 || cell +491725702667 || http://www.nomor-research.com Nomor Research GmbH - Sitz der Gesellschaft: M=FCnchen - = Registergericht: M=FCnchen, HRB 165856 =96 Umsatzsteuer-ID: DE238047637 = - Gesch=E4ftsf=FChrer: Dr. Thomas Stockhammer, Dr. Ingo Viering. --Apple-Mail=_BE05AC36-F49F-49CD-8CDE-9BAD82D26C00 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
Dear = experts, 

MPEG is working in defining a = generic RTP-independent MIME type for MPEG-2 transport streams to = be included as an Annex in ISO/IEC = 13818-1.

Please review media type registration = of the MPEG-2 TS as provided below.

Please provide any = comments asap, latest by December = 9th.

Thanks!

Thomas


=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D

 

MIME type for MPEG-2 transport streams

T.1     = Introduction

This = Annex provides the formal MIME type registration for MPEG-2 transport streams. It is referenced from the registry at http://www.iana.org/.<= /p>

T.2     MIME type and = subtype

MIME= media type name:
        =     video  =

MIME= subtype name:
        =     mp2t

Required parameters:
        =     none

Optional parameters:
        =     The =91profiles=92 = parameter as documented in Annex T.2.1

        =     The 'codecs' = parameter as document in Annex T.2.2

Encoding = considerations:

        =     This type is defined for general use; for transfer via RTP see [RFC = 3550].

Security considerations:
        =     see Annex T.3

Interoperability = considerations:

        =     The specification defines a platform-independent expression of a = presentation, and it is intended that         =    wide interoperability can be achieved.

Published specification:
        =     ISO/IEC 13818-1, Information technology =97 Generic coding of moving pictures and associated         = audio information: Systems

Applications that use this media type:
        =     various, including video streaming and video broadcasting = applications

Additional information:
        =     File extension(s):         =

        =             &n= bsp;   .ts

        =     Intended usage:         =    

        =             &n= bsp;   COMMON

Other Information/General = Comment:

        =     none

Person to contact for further = information:

        =     Name:  =

        =             &n= bsp;   Mandayam Narasimhan

        =     e-mail:         =    

        =             &n= bsp;   Snarasimhan@motorola.com=

Change controller: =

        =     ISO/IEC JTC1/SC29 (MPEG)

 

T.3    Security = Considerations

It = is possible to inject non-compliant streams (Audio, Video, and Systems) in the transport stream to overload the = receiver/decoder's buffers.  This might = compromise the functionality of the receiver or even crash = it.

An = MPEG-2 Transport Stream is an extensible container format, and hence might carry streams that have active aspects (e.g. = contain script snippets). If those subsystems are not properly defined or = implemented, it may be possible to crash the receiver or temporarily make it = unavailable.

T.4   = Parameters

T.4.1 The profiles parameter

 

Parameter = Name:        = profiles

 

Parameter = Value:        =  

The 'profiles' parameter is an optional parameter that indicates one or more profiles to which the = stream claims conformance. The contents of this attribute shall conform to either the pro-simple or = pro-fancy= productions of RFC6381, Section 4.5. The profile identifiers reported in the MIME type parameter takes as value = the transport_profile, = coded as a decimal integer, e.g. profiles=3D"1" for = streams conforming to the 'strict' profile.

 

Example:        =              = video/mp2t;profiles=3D"1"

 

T.4.2 The codecs = parameter

 

Parameter = Name:        = codecs

 

Parameter = Value:        =  

 

The 'codecs' = parameter is an optional parameter that indicates one or more codecs which are used for = the elementary streams in the MPEG-2 TS.  The contents of this attribute shall conform to either the pro-simple or = pro-fancy= productions of RFC6381, Section 3.2. RFC 6381 defines =91codecs=92 parameter as a single value, or a comma-separated list of values identifying the = codec(s), where each value consists of one or more dot-separated elements. =  The first element of such a value can be derived from the value of stream_type in the = program_map_section.  If the = stream_type value = appears in Table T-1, the value in the first = element column shall be used as = the first element. If the stream_type value is = between 0x80 and 0xFF, the first = element may be derived in ways not specified by this Annex (e.g. by examining the contents of registration_descriptor, if used).

Table T-1 =96=91codecs=92 parameter values

stream_type

first element

0x01

mp1v

0x02

mp2v

0x03

mp1a

0x04

mp2a

0x0F

mp2a

0x10

mp4v

0x11

mp4a

0x1B

avc1

0x1C

mp4a

0x1D

tx3g

0x1F

svc1

0x20

mvc1

0x21

mjp2

 

Wherever a = definition for additional elements exists in RFC 6381 for a given first element, the definition in = RFC 6381 shall be followed.

When the first = element of a value is =91mp2a=92 or =91mp2v=92, the second element of the codecs parameter = value is the hexadecimal representation of the MP4 Registration Authority ObjectTypeIndication (OTI) for the appropriate specification and = profile.

 

Examples:        =             =

            = ;            = ISO/IEC 13818-2 Main Profile

        =        = video/mp2ts;codecs=3D"mp2v.61"

            = ;            = ISO/IEC 13818-3 is represented

        =             &n= bsp;           &nbs= p;   video/mp2ts;codecs=3D"mp2a.= 69"

        =             &n= bsp;   ISO/IEC 13818-7 Low Complexity Profile

        =             &n= bsp;           &nbs= p;   video/mp2ts;codecs=3D"mp2a.= 67"

            = ;            = Dolby AC-3 audio (per ATSC A/52, AC-3 audio has stream_type 0x81 and             = ;            &= nbsp;           =     format_identifier =93AC-3=94 in the registration_descriptor )

        =             &n= bsp;           &nbs= p;            =          video/mp2ts;codecs=3D"ac-3"=

ISO/IEC 13818-2 Main Profile Video together with ISO/IEC 13818-7 = audio

        =             &n= bsp;           &nbs= p;   video/mp2ts;codecs=3D"mp2v.= 61,mp2a.67"


stockhammer@nomor.de || = phone +49 89 978980 02 || cell +491725702667 || http://www.nomor-research.com
Nomor Research GmbH  -  Sitz = der Gesellschaft: M=FCnchen - Registergericht: M=FCnchen, HRB 165856 =96 = Umsatzsteuer-ID: DE238047637 - Gesch=E4ftsf=FChrer: Dr. Thomas = Stockhammer, Dr. Ingo Viering.






= --Apple-Mail=_BE05AC36-F49F-49CD-8CDE-9BAD82D26C00-- Return-Path: 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 9156C1F0C36 for ; Tue, 29 Nov 2011 10:54:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.999 X-Spam-Level: X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, J_CHICKENPOX_45=0.6] 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 xXXOHXF6Th06 for ; Tue, 29 Nov 2011 10:54:16 -0800 (PST) Received: from pechora1.lax.icann.org (unknown [IPv6:2620:0:2d0:201::1:71]) by ietfa.amsl.com (Postfix) with ESMTP id 6980F21F8A71 for ; Tue, 29 Nov 2011 10:54:16 -0800 (PST) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by pechora1.lax.icann.org (8.13.8/8.13.8) with SMTP id pATIrtxH030027 for ; Tue, 29 Nov 2011 10:54:15 -0800 Received: (qmail invoked by alias); 29 Nov 2011 18:53:53 -0000 Received: from dslb-094-222-134-043.pools.arcor-ip.net (EHLO HIVE) [94.222.134.43] by mail.gmx.net (mp023) with SMTP; 29 Nov 2011 19:53:53 +0100 X-Authenticated: #723575 X-Provags-ID: V01U2FsdGVkX19/XI8u1MN/EG9oOM+mpsKXnwphdPekTFFNuxBuYJ diSaHiv4Uuf4MR From: Bjoern Hoehrmann To: ietf-types@iana.org Date: Tue, 29 Nov 2011 19:53:59 +0100 Message-ID: <8eaad7hpkdmbon03ialjs2heegum5uh4t8@hive.bjoern.hoehrmann.de> X-Mailer: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora1.lax.icann.org [192.0.33.71]); Tue, 29 Nov 2011 18:54:16 +0000 (UTC) Subject: [ietf-types] Media Type overview with IANA, Apache, Wikipedia data X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2011 18:54:16 -0000 Hi, http://lists.w3.org/Archives/Public/www-archive/2011Nov/0079.html has some information on currently registered media types, media types in Wikipedia, and in Apache's mime.types configuration file. regards, -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ Return-Path: 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 7FDBB21F87D6 for ; Mon, 28 Nov 2011 01:08:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.002 X-Spam-Level: X-Spam-Status: No, score=-102.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, 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 bsW2gzxzI0Id for ; Mon, 28 Nov 2011 01:08:15 -0800 (PST) Received: from pechora2.lax.icann.org (pechora2.icann.org [IPv6:2620:0:2d0:201::1:72]) by ietfa.amsl.com (Postfix) with ESMTP id 9313E21F8AEC for ; Mon, 28 Nov 2011 01:08:14 -0800 (PST) Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by pechora2.lax.icann.org (8.13.8/8.13.8) with ESMTP id pAS97se3031681 for ; Mon, 28 Nov 2011 09:08:14 GMT MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_EYhqLWBmdadHoTjgvWRlxA)" Received: from relay15.apple.com ([17.128.113.54]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LVD000PG2IAPCN1@mail-out.apple.com> for ietf-types@iana.org; Mon, 28 Nov 2011 00:06:22 -0800 (PST) X-AuditID: 11807136-b7c19ae0000072b0-f5-4ed340fa1315 Received: from [17.73.146.234] (Unknown_Domain [17.73.146.234]) by relay15.apple.com (Apple SCV relay) with SMTP id CE.53.29360.CF043DE4; Mon, 28 Nov 2011 00:06:21 -0800 (PST) From: David Singer In-reply-to: <78353E30EDF34348B3E8C3EAA016C9510F6FA1@TK5EX14MBXC281.redmond.corp.microsoft.com> Date: Mon, 28 Nov 2011 09:06:17 +0100 Message-id: <56028828-94F9-424F-A17A-8879CF985800@apple.com> References: <203C8BD8-69F9-4AD9-B1A7-23D83D6F72D8@nomor.de> <78353E30EDF34348B3E8C3EAA016C9510F6FA1@TK5EX14MBXC281.redmond.corp.microsoft.com> To: Harry Pyle X-Mailer: Apple Mail (2.1251.1) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrPLMWRmVeSWpSXmKPExsUi6Dnple5fh8t+BldOmVvsPrmC3eLrzJ9M FuuunWKyWLTzLJsDi0ePvMfb2fkerTv+sntce/aIPYAlissmJTUnsyy1SN8ugSvj3+Ju1oI7 U5gqOpbuYmlgvPqFsYuRg0NCwESiqyO1i5ETyBSTuHBvPVsXIxeHkMBGRonGG6fZQBLCAuYS b2/cYgSxeQWMJdbcescCYjMLJEj8PruJCcRmE1CVeDDnGFgNp0C8xL9NS8F6WYDiE7f8YwYZ yizQwihxsO0/1CAbiU9/dzNCbOtjlJh3YTPYRSICmhLrrxVBXCQv0fL1DtsERr5ZSHbPQrIb wtaWWLbwNTOErSmxv3s5C6a4hkTnt4msCxjZVjEKFqXmJFYamuolFhTkpOol5+duYgQFc0Oh 2Q7GHX/lDjEKcDAq8fBuvHzJT4g1say4MvcQowQHs5IIb89RoBBvSmJlVWpRfnxRaU5q8SFG aQ4WJXHeT5qn/YQE0hNLUrNTUwtSi2CyTBycUg2MJl2aMQWBrq80/gleVIzorQoUudL7++nz gHOyj1Oqdkpv5jCpqr99WDlE8u/tgx79sX2rjtxQ6ojl0+YL/dTEeLKPZ0VXZU7Nk3I1kZdn pvZrxk89IuJ0f5lS+dqJ2Y1xSsJ6u+/cDM6S6T/KIvPJP6evo/T4RDOTiN+bJY9+LOVew9wz 7YQSS3FGoqEWc1FxIgC70Z1DYgIAAA== X-Greylist: Delayed for 01:01:32 by milter-greylist-4.0 (pechora2.lax.icann.org [192.0.33.72]); Mon, 28 Nov 2011 09:08:14 +0000 (UTC) X-Mailman-Approved-At: Tue, 29 Nov 2011 06:37:18 -0800 Cc: "ietf-types@iana.org" , List DASH Subject: Re: [ietf-types] [DASH] Media type registration of DASH MPD X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2011 09:08:16 -0000 --Boundary_(ID_EYhqLWBmdadHoTjgvWRlxA) Content-type: text/plain; charset=utf-8 Content-transfer-encoding: quoted-printable maybe that would imply that only official ones should be used? On Nov 28, 2011, at 0:15 , Harry Pyle wrote: > My only minor question is why not use a couple of the official DASH = profile URN values in the example instead of the mythical/fictional = ones? > =20 > =E2=80=A6Harry > =20 > From: dash-bounces@lists.uni-klu.ac.at = [mailto:dash-bounces@lists.uni-klu.ac.at] On Behalf Of Thomas = Stockhammer > Sent: Friday, November 25, 2011 6:19 AM > To: ietf-types@iana.org > Cc: List DASH > Subject: [DASH] Media type registration of DASH MPD > =20 > Dear experts,=20 > =20 > MPEG-DASH in ISO/IEC 23009-1 has passed DIS ballot and is in the final = editing stages:=20 > =20 > Please review media type registration of the MPD as provided below: > =20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =20 > Annex C: MIME type registration for MPD > =20 > C.1 Introduction > This Annex provides the formal MIME type registration for the MPD. It = is referenced from the registry at http://www.iana.org/. > =20 > C.2 MIME type and subtype > The MIME Type and Subtype are defined as follows: > =E2=8E=AF MIME media type name: application > =E2=8E=AF MIME subtype name: dash+xml > =E2=8E=AF Required parameters: none > =E2=8E=AF Optional parameters: The =E2=80=98profiles=E2=80=99= parameter as documented in Annex C.3.1 in this part of ISO/IEC 23009 > =E2=8E=AF Encoding considerations: the same media = type encoding considerations specified in section 3.2 of RFC 3023 > =E2=8E=AF Security considerations: The MPD is a = Media Presentation Description and contains references to other = resources. It is coded in XML, and there are risks that deliberately = malformed XML could cause security issues. In addition, an MPD could be = authored that causes receiving clients to access other resources; if = widely distributed, this could be used to cause a denial-of-service = attack. > =E2=8E=AF Interoperability considerations:=20 > The specification defines a platform-independent expression of a = presentation, and it is intended that wide interoperability can be = achieved. > =E2=8E=AF Published specification: ISO/IEC = 23009-1: Information technology =E2=80=94 Dynamic adaptive streaming = over HTTP (DASH) =E2=80=94 Part 1: Dynamic adaptive streaming over HTTP = (DASH) > =E2=8E=AF Applications which use this media type: = various > =E2=8E=AF Additional information: > =E2=8E=AF File extension(s): = mpd > =E2=8E=AF Intended usage: = common > =E2=8E=AF Other Information/General Comment: none > =E2=8E=AF Person to contact for further information: > =E2=8E=AF Name: Thomas Stockhammer > =E2=8E=AF Email: stockhammer@nomor.de > =E2=8E=AF Author/Change controller: ISO/IEC JTC1/SC29 = (MPEG) > =20 > C.3 Parameters > C.3.1 The profiles parameter > Parameter name: profiles > Parameter value: The 'profiles' parameter is an optional = parameter that indicates one or more profiles to which the file claims = conformance. The contents of this attribute shall conform to either the = pro-simp or pro-fancy productions of RFC6381, Section 4.5. The profile = identifiers reported in the MIME type parameter should match identically = the profiles reported in the profiles attribute in the MPD itself (see = Clause 8). > =20 > example: > = application/dash+xml;profiles=3D"urn:mpeg:dash:profiles:mythical,urn:3gpp:= dash:profiles:fictional" > =20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > =20 > Please provide any comments asap, latest by December 6th. > =20 > Thanks! > =20 > Thomas > =20 > --- > Dr. Thomas Stockhammer (CEO) || stockhammer@nomor.de || phone +49 89 = 978980 02 || cell +491725702667 || http://www.nomor-research.com > Nomor Research GmbH - Sitz der Gesellschaft: M=C3=BCnchen - = Registergericht: M=C3=BCnchen, HRB 165856 =E2=80=93 Umsatzsteuer-ID: = DE238047637 - Gesch=C3=A4ftsf=C3=BChrer: Dr. Thomas Stockhammer, Dr. = Ingo Viering. > =20 > =20 > =20 > =20 > =20 >=20 David Singer Multimedia and Software Standards, Apple Inc. --Boundary_(ID_EYhqLWBmdadHoTjgvWRlxA) Content-type: text/html; charset=utf-8 Content-transfer-encoding: quoted-printable maybe = that would imply that only official ones should be = used?

On Nov 28, 2011, at 0:15 , Harry Pyle = wrote:

My = only minor question is why not use a couple of the official DASH profile = URN values in the example instead of the mythical/fictional = ones?
From: dash-bounces@lists.uni-kl= u.ac.at [mailto:dash-bounces@lists.uni-klu.ac.at] On Behalf Of Thomas = Stockhammer
Sent: Friday, November 25, 2011 = 6:19 AM
To: ietf-types@iana.org
Cc:<= span class=3D"Apple-converted-space"> List = DASH
Subject: [DASH] Media type = registration of DASH MPD
 
Dear = experts, 
MPEG-DASH in ISO/IEC = 23009-1 has passed DIS ballot and is in the final editing = stages: 
Please review media type = registration of the MPD as provided = below:
 
Annex C: MIME type registration for = MPD
C.1        &= nbsp;           Introduction
 This Annex provides = the formal MIME type registration for the MPD. It is referenced from the = registry at  
= --Boundary_(ID_EYhqLWBmdadHoTjgvWRlxA)-- Return-Path: 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 AB8B121F8BDB for ; Mon, 28 Nov 2011 00:27:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.167 X-Spam-Level: *** X-Spam-Status: No, score=3.167 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, MIME_QP_LONG_LINE=1.396] 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 oZRJVdLeRqzJ for ; Mon, 28 Nov 2011 00:27:36 -0800 (PST) Received: from pechora8.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:74]) by ietfa.amsl.com (Postfix) with ESMTP id C214521F8BBC for ; Mon, 28 Nov 2011 00:27:34 -0800 (PST) Received: from mailsrv.uni-klu.ac.at (mailsrv.uni-klu.ac.at [143.205.180.44]) by pechora8.dc.icann.org (8.13.8/8.13.8) with ESMTP id pAS8RB4D023543 for ; Mon, 28 Nov 2011 03:27:33 -0500 Received: from mailsrv.uni-klu.ac.at (localhost [127.0.0.1]) by mailsrv.uni-klu.ac.at (Postfix) with ESMTP id 1F66885169; Mon, 28 Nov 2011 09:04:00 +0100 (CET) Received: from mailsrv.itec.uni-klu.ac.at (mailsrv-itec.uni-klu.ac.at [143.205.176.139]) by mailsrv.uni-klu.ac.at (Postfix) with ESMTP id F168A842AC; Mon, 28 Nov 2011 09:03:59 +0100 (CET) Received: from mailsrv.itec.uni-klu.ac.at (localhost [127.0.0.1]) by mailsrv.itec.uni-klu.ac.at (Postfix) with ESMTP id D8ACC138032C; Mon, 28 Nov 2011 09:03:59 +0100 (CET) Received: from [192.168.16.100] (unknown [195.94.37.227]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailsrv.itec.uni-klu.ac.at (Postfix) with ESMTPSA id 6F89E138026D; Mon, 28 Nov 2011 09:03:59 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: multipart/alternative; boundary="Apple-Mail=_30D3B617-1A86-4BC5-933C-CC0EC94913C6" From: "Christian Timmerer (ITEC)" In-Reply-To: <78353E30EDF34348B3E8C3EAA016C9510F6FA1@TK5EX14MBXC281.redmond.corp.microsoft.com> Date: Mon, 28 Nov 2011 09:03:59 +0100 Message-Id: <57C0EFD2-AB72-4880-BDA5-532663822E0E@itec.uni-klu.ac.at> References: <203C8BD8-69F9-4AD9-B1A7-23D83D6F72D8@nomor.de> <78353E30EDF34348B3E8C3EAA016C9510F6FA1@TK5EX14MBXC281.redmond.corp.microsoft.com> To: Harry Pyle X-Mailer: Apple Mail (2.1251.1) X-AV-Checked: ClamAV at mailsrv.itec.uni-klu.ac.at X-Virus-Scanned: ClamAV using ClamSMTP X-Greylist: Delayed for 00:23:12 by milter-greylist-4.2.3 (pechora8.dc.icann.org [192.0.46.74]); Mon, 28 Nov 2011 03:27:33 -0500 (EST) X-Mailman-Approved-At: Tue, 29 Nov 2011 06:37:18 -0800 Cc: "ietf-types@iana.org" , List DASH Subject: Re: [ietf-types] [DASH] Media type registration of DASH MPD X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2011 08:27:37 -0000 --Apple-Mail=_30D3B617-1A86-4BC5-933C-CC0EC94913C6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 +1 On Nov 28, 2011, at 12:15 AM, Harry Pyle wrote: > My only minor question is why not use a couple of the official DASH = profile URN values in the example instead of the mythical/fictional = ones? > =20 > =E2=80=A6Harry > =20 > From: dash-bounces@lists.uni-klu.ac.at = [mailto:dash-bounces@lists.uni-klu.ac.at] On Behalf Of Thomas = Stockhammer > Sent: Friday, November 25, 2011 6:19 AM > To: ietf-types@iana.org > Cc: List DASH > Subject: [DASH] Media type registration of DASH MPD > =20 > Dear experts,=20 > =20 > MPEG-DASH in ISO/IEC 23009-1 has passed DIS ballot and is in the final = editing stages:=20 > =20 > Please review media type registration of the MPD as provided below: > =20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =20 > Annex C: MIME type registration for MPD > =20 > C.1 Introduction > This Annex provides the formal MIME type registration for the MPD. It = is referenced from the registry at http://www.iana.org/. > =20 > C.2 MIME type and subtype > The MIME Type and Subtype are defined as follows: > =E2=8E=AF MIME media type name: application > =E2=8E=AF MIME subtype name: dash+xml > =E2=8E=AF Required parameters: none > =E2=8E=AF Optional parameters: The =E2=80=98profiles=E2=80=99= parameter as documented in Annex C.3.1 in this part of ISO/IEC 23009 > =E2=8E=AF Encoding considerations: the same media = type encoding considerations specified in section 3.2 of RFC 3023 > =E2=8E=AF Security considerations: The MPD is a = Media Presentation Description and contains references to other = resources. It is coded in XML, and there are risks that deliberately = malformed XML could cause security issues. In addition, an MPD could be = authored that causes receiving clients to access other resources; if = widely distributed, this could be used to cause a denial-of-service = attack. > =E2=8E=AF Interoperability considerations:=20 > The specification defines a platform-independent expression of a = presentation, and it is intended that wide interoperability can be = achieved. > =E2=8E=AF Published specification: ISO/IEC = 23009-1: Information technology =E2=80=94 Dynamic adaptive streaming = over HTTP (DASH) =E2=80=94 Part 1: Dynamic adaptive streaming over HTTP = (DASH) > =E2=8E=AF Applications which use this media type: = various > =E2=8E=AF Additional information: > =E2=8E=AF File extension(s): = mpd > =E2=8E=AF Intended usage: = common > =E2=8E=AF Other Information/General Comment: none > =E2=8E=AF Person to contact for further information: > =E2=8E=AF Name: Thomas Stockhammer > =E2=8E=AF Email: stockhammer@nomor.de > =E2=8E=AF Author/Change controller: ISO/IEC JTC1/SC29 = (MPEG) > =20 > C.3 Parameters > C.3.1 The profiles parameter > Parameter name: profiles > Parameter value: The 'profiles' parameter is an optional = parameter that indicates one or more profiles to which the file claims = conformance. The contents of this attribute shall conform to either the = pro-simp or pro-fancy productions of RFC6381, Section 4.5. The profile = identifiers reported in the MIME type parameter should match identically = the profiles reported in the profiles attribute in the MPD itself (see = Clause 8). > =20 > example: > = application/dash+xml;profiles=3D"urn:mpeg:dash:profiles:mythical,urn:3gpp:= dash:profiles:fictional" > =20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > =20 > Please provide any comments asap, latest by December 6th. > =20 > Thanks! > =20 > Thomas > =20 > --- > Dr. Thomas Stockhammer (CEO) || stockhammer@nomor.de || phone +49 89 = 978980 02 || cell +491725702667 || http://www.nomor-research.com > Nomor Research GmbH - Sitz der Gesellschaft: M=C3=BCnchen - = Registergericht: M=C3=BCnchen, HRB 165856 =E2=80=93 Umsatzsteuer-ID: = DE238047637 - Gesch=C3=A4ftsf=C3=BChrer: Dr. Thomas Stockhammer, Dr. = Ingo Viering. > =20 > =20 > =20 > =20 > =20 >=20 > =20 --Apple-Mail=_30D3B617-1A86-4BC5-933C-CC0EC94913C6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

+1

On Nov 28, 2011, at 12:15 AM, Harry Pyle wrote:

My = only minor question is why not use a couple of the official DASH profile = URN values in the example instead of the mythical/fictional = ones?
From: dash-bounces@lists.uni-klu.ac.at [mailto:dash-bounces@lists.un= i-klu.ac.at] On = Behalf Of Thomas = Stockhammer
Sent: Friday, November 25, 2011 = 6:19 AM
To: ietf-types@iana.org
Cc: List = DASH
Subject: [DASH] Media type = registration of DASH MPD
 
Dear = experts, 
MPEG-DASH in ISO/IEC = 23009-1 has passed DIS ballot and is in the final editing = stages: 
Please review media type = registration of the MPD as provided = below:
 
Annex C: MIME type registration for = MPD
C.1        &= nbsp;           Introduction
 This Annex provides = the formal MIME type registration for the MPD. It is referenced from the = registry at  
Dr. Thomas Stockhammer (CEO) || stockhammer@nomor.de || phone +49 = 89 978980 02 || cell +491725702667 ||  
To: ietf-types@iana.org References: <1A2E179F-088C-4C70-8C3E-DC1507BED7E6@nomor.de> Message-Id: <48154DB7-133F-4DB1-A37F-6F866AB94462@nomor.de> X-Mailer: Apple Mail (2.1251.1) X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (pechora7.dc.icann.org [IPv6:2620:0:2830:201::1:73]); Fri, 25 Nov 2011 10:02:25 -0500 (EST) Subject: [ietf-types] Media Types in draft-ietf-fecframe-rtp-raptor-06 (update) X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2011 15:02:30 -0000 --Apple-Mail=_480A64FD-67C0-4E09-B39E-809F3CB46242 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Dear experts,=20 based on some immediate feedback, please consider this small update=20 draft-ietf-fecframe-rtp-raptor-06 is currently in IESG review.=20 Please review its media type registration as provided below: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 6. Media Types 6.1. Registration of the application/raptorfec media type This RTP payload format is identified using the application/raptorfec media type which is registered in accordance with [RFC4855] and using the template of [RFC4288]. 6.1.1. Media Type Definition Type name: application Subtype name: raptorfec Required parameters: o rate: The RTP timestamp (clock) rate. The RTP timestamp (clock) rate is specified in Hz and the format is unsigned integer. o raptor-scheme-id: The value of this parameter is the FEC Scheme Id for the specific Raptor FEC Scheme that will be used as defined in [I-D.ietf-fecframe-raptor]. o Kmax: The value of this parameter is the FEC Framework Configuration Information element "Maximum Source Block Length" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o T: The value of this parameter is the FEC Framework Configuration Information element "Encoding Symbol Size" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o repair-window: The maximum time that spans the source packets and the corresponding repair packets. The size of the repair window is specified in microseconds and the format is unsigned integer. Optional parameters: o P: The value of this parameter is the FEC Framework Configuration Information element "Payload ID Format" as defined in [I-D.ietf-fecframe-raptor]. If this parameter is missing the value "A" SHALL be assumed. Encoding considerations: This media type is framed and binary, see section 4.8 in [RFC4288] Security considerations: Please see security consideration in [RFC6363] Interoperability considerations: Published specification: [I-D.ietf-fecframe-raptor] Applications that use this media type: Real-time multimedia applications like video streaming, audio streaming, and video conferencing. Additional information: Magic number(s): File extension(s): Macintosh file type code(s): Person & email address to contact for further information: Thomas Stockhammer, stockhammer@nomor.de Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP [[RFC3550]]. Transport within other framing protocols is not defined at this time. Author: Thomas Stockhammer, Nomor Research Change controller: IETF Audio/Video Transport working group delegated from the IESG. 6.2. Registration of the video/raptorfec media type This RTP payload format is identified using the video/raptorfec media type which is registered in accordance with [RFC4855] and using the template of [RFC4288]. 6.2.1. Media Type Definition Type name: video Subtype name: raptorfec Required parameters: o rate: The RTP timestamp (clock) rate. The RTP timestamp (clock) rate is specified in Hz and the format is unsigned integer. o raptor-scheme-id: The value of this parameter is the FEC Scheme Id for the specific Raptor FEC Scheme that will be used as defined in [I-D.ietf-fecframe-raptor]. o Kmax: The value of this parameter is the FEC Framework Configuration Information element "Maximum Source Block Length" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o T: The value of this parameter is the FEC Framework Configuration Information element "Encoding Symbol Size" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o repair-window: The maximum time that spans the source packets and the corresponding repair packets. The size of the repair window is specified in microseconds and the format is unsigned integer. Optional parameters: o P: The value of this parameter is the FEC Framework Configuration Information element "Payload ID Format" as defined in [I-D.ietf-fecframe-raptor]. If this parameter is missing the value "A" SHALL be assumed. Encoding considerations: This media type is framed and binary, see section 4.8 in [RFC4288] Security considerations: Please see security consideration in [RFC6363] Interoperability considerations: Published specification: [I-D.ietf-fecframe-raptor] Applications that use this media type: Real-time multimedia applications like video streaming, audio streaming, and video conferencing. Additional information: Magic number(s): File extension(s): Macintosh file type code(s): Person & email address to contact for further information: Thomas Stockhammer, stockhammer@nomor.de Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP [[RFC3550]]. Transport within other framing protocols is not defined at this time. Author: Thomas Stockhammer, Nomor Research. Change controller: IETF Audio/Video Transport working group delegated from the IESG. 6.3. Registration of the audio/raptorfec media type This RTP payload format is identified using the audio/raptorfec media type which is registered in accordance with [RFC4855] and using the template of [RFC4288]. 6.3.1. Media Type Definition Type name: audio Subtype name: raptorfec Required parameters: o rate: The RTP timestamp (clock) rate. The RTP timestamp (clock) rate is specified in Hz and the format is unsigned integer. o raptor-scheme-id: The value of this parameter is the FEC Scheme Id for the specific Raptor FEC Scheme that will be used as defined in [I-D.ietf-fecframe-raptor]. o Kmax: The value of this parameter is the FEC Framework Configuration Information element "Maximum Source Block Length" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o T: The value of this parameter is the FEC Framework Configuration Information element "Encoding Symbol Size" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o repair-window: The maximum time that spans the source packets and the corresponding repair packets. The size of the repair window is specified in microseconds and the format is unsigned integer. Optional parameters: o P: The value of this parameter is the FEC Framework Configuration Information element "Payload ID Format" as defined in [I-D.ietf-fecframe-raptor]. If this parameter is missing the value "A" SHALL be assumed. Encoding considerations: This media type is framed and binary, see section 4.8 in [RFC4288] Security considerations: Please see security consideration in [RFC6363] Interoperability considerations: Published specification: [I-D.ietf-fecframe-raptor] Applications that use this media type: Real-time multimedia applications like video streaming, audio streaming, and video conferencing. Additional information: Magic number(s): File extension(s): Macintosh file type code(s): Person & email address to contact for further information: Thomas Stockhammer, stockhammer@nomor.de Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP [[RFC3550]]. Transport within other framing protocols is not defined at this time. Author: Thomas Stockhammer, Nomor Research. Change controller: IETF Audio/Video Transport working group delegated from the IESG. 6.4. Registration of the text/raptorfec media type This RTP payload format is identified using the text/raptorfec media type which is registered in accordance with [RFC4855] and using the template of [RFC4288]. 6.4.1. Media Type Definition Type name: text Subtype name: raptorfec Required parameters: o rate: The RTP timestamp (clock) rate. The RTP timestamp (clock) rate is specified in Hz and the format is unsigned integer. o raptor-scheme-id: The value of this parameter is the FEC Scheme Id for the specific Raptor FEC Scheme that will be used as defined in [I-D.ietf-fecframe-raptor]. o Kmax: The value of this parameter is the FEC Framework Configuration Information element "Maximum Source Block Length" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o T: The value of this parameter is the FEC Framework Configuration Information element "Encoding Symbol Size" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o repair-window: The maximum time that spans the source packets and the corresponding repair packets. The size of the repair window is specified in microseconds and the format is unsigned integer. Optional parameters: o P: The value of this parameter is the FEC Framework Configuration Information element "Payload ID Format" as defined in [I-D.ietf-fecframe-raptor]. If this parameter is missing the value "A" SHALL be assumed. Encoding considerations: This media type is framed and binary, see section 4.8 in [RFC4288] Security considerations: Please see security consideration in [RFC6363] Interoperability considerations: Published specification: [I-D.ietf-fecframe-raptor] Applications that use this media type: Real-time multimedia applications like video streaming, audio streaming, and video conferencing. Additional information: Magic number(s): File extension(s): Macintosh file type code(s): Person & email address to contact for further information: Thomas Stockhammer, stockhammer@nomor.de Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP [[RFC3550]]. Transport within other framing protocols is not defined at this time. Author: Thomas Stockhammer, Nomor Research. Change controller: IETF Audio/Video Transport working group delegated from the IESG. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Please provide any comments asap, latest by December 9th. Thanks! Thomas On Nov 25, 2011, at 3:00 PM, Thomas Stockhammer wrote: > Dear experts,=20 >=20 > draft-ietf-fecframe-rtp-raptor-06 is currently in IESG review.=20 > Please review its media type registration as provided below: >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > 6. Media Types >=20 > 6.1. Registration of the application/raptorfec media type >=20 > This RTP payload format is identified using the = application/raptorfec > media type which is registered in accordance with [RFC4855] and = using > the template of [RFC4288]. >=20 > 6.1.1. Media Type Definition >=20 > Type name: application >=20 > Subtype name: raptorfec >=20 > Required parameters: >=20 > o rate: The RTP timestamp (clock) rate. The operator SHALL select = a > rate larger than 1000 Hz to provide sufficient resolution to = RTCP > operations and the operator SHOULD select the rate that matches > the rate of the protected source RTP stream. The RTP timestamp > (clock) rate is specified in Hz and the format is unsigned > integer. >=20 > o raptor-scheme-id: The value of this parameter is the FEC Scheme = Id > for the specific Raptor FEC Scheme that will be used as defined = in > [I-D.ietf-fecframe-raptor]. >=20 > o Kmax: The value of this parameter is the FEC Framework > Configuration Information element "Maximum Source Block Length" = as > defined in [I-D.ietf-fecframe-raptor] encoded as a decimal > integer. For specific requirements for this value refer to > [I-D.ietf-fecframe-raptor]. >=20 > o T: The value of this parameter is the FEC Framework = Configuration > Information element "Encoding Symbol Size" as defined in > [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For > specific requirements for this value refer to > [I-D.ietf-fecframe-raptor]. >=20 > o repair-window: The maximum time that spans the source packets = and > the corresponding repair packets. The size of the repair window > is specified in microseconds and the format is unsigned integer. >=20 > Optional parameters: >=20 > o P: The value of this parameter is the FEC Framework = Configuration > Information element "Payload ID Format" as defined in > [I-D.ietf-fecframe-raptor]. If this parameter is missing the > value "A" SHALL be assumed. >=20 > Encoding considerations: This media type is framed and binary, see > section 4.8 in [RFC4288] >=20 > Security considerations: Please see security consideration in > [RFC6363] >=20 > Interoperability considerations: >=20 > Published specification: [I-D.ietf-fecframe-raptor] >=20 > Applications that use this media type: Real-time multimedia > applications like video streaming, audio streaming, and video > conferencing. >=20 > Additional information: >=20 > Magic number(s): >=20 > File extension(s): >=20 > Macintosh file type code(s): >=20 > Person & email address to contact for further information: Thomas > Stockhammer, stockhammer@nomor.de >=20 > Intended usage: COMMON >=20 > Restrictions on usage: This media type depends on RTP framing, and > hence is only defined for transfer via RTP [[RFC3550]]. Transport > within other framing protocols is not defined at this time. >=20 > Author: Thomas Stockhammer, Nomor Research >=20 > Change controller: IETF Audio/Video Transport working group = delegated > from the IESG. >=20 > 6.2. Registration of the video/raptorfec media type >=20 > This RTP payload format is identified using the video/raptorfec = media > type which is registered in accordance with [RFC4855] and using the > template of [RFC4288]. >=20 > 6.2.1. Media Type Definition >=20 > Type name: video >=20 > Subtype name: raptorfec >=20 > Required parameters: >=20 > o rate: The RTP timestamp (clock) rate. The operator SHALL select = a > rate larger than 1000 Hz to provide sufficient resolution to = RTCP > operations and the operator SHOULD select the rate that matches > the rate of the protected source RTP stream. The RTP timestamp > (clock) rate is specified in Hz and the format is unsigned > integer. >=20 > o raptor-scheme-id: The value of this parameter is the FEC Scheme = Id > for the specific Raptor FEC Scheme that will be used as defined = in > [I-D.ietf-fecframe-raptor]. >=20 > o Kmax: The value of this parameter is the FEC Framework > Configuration Information element "Maximum Source Block Length" = as > defined in [I-D.ietf-fecframe-raptor] encoded as a decimal > integer. For specific requirements for this value refer to > [I-D.ietf-fecframe-raptor]. >=20 > o T: The value of this parameter is the FEC Framework = Configuration > Information element "Encoding Symbol Size" as defined in > [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For > specific requirements for this value refer to > [I-D.ietf-fecframe-raptor]. >=20 > o repair-window: The maximum time that spans the source packets = and > the corresponding repair packets. The size of the repair window > is specified in microseconds and the format is unsigned integer. >=20 > Optional parameters: >=20 > o P: The value of this parameter is the FEC Framework = Configuration > Information element "Payload ID Format" as defined in > [I-D.ietf-fecframe-raptor]. If this parameter is missing the > value "A" SHALL be assumed. >=20 > Encoding considerations: This media type is framed and binary, see > section 4.8 in [RFC4288] >=20 > Security considerations: Please see security consideration in > [RFC6363] >=20 > Interoperability considerations: >=20 > Published specification: [I-D.ietf-fecframe-raptor] >=20 > Applications that use this media type: Real-time multimedia > applications like video streaming, audio streaming, and video > conferencing. >=20 > Additional information: >=20 > Magic number(s): >=20 > File extension(s): >=20 > Macintosh file type code(s): >=20 > Person & email address to contact for further information: Thomas > Stockhammer, stockhammer@nomor.de >=20 > Intended usage: COMMON >=20 > Restrictions on usage: This media type depends on RTP framing, and > hence is only defined for transfer via RTP [[RFC3550]]. Transport > within other framing protocols is not defined at this time. >=20 > Author: Thomas Stockhammer, Nomor Research. >=20 > Change controller: IETF Audio/Video Transport working group = delegated > from the IESG. >=20 > 6.3. Registration of the audio/raptorfec media type >=20 > This RTP payload format is identified using the audio/raptorfec = media > type which is registered in accordance with [RFC4855] and using the > template of [RFC4288]. >=20 > 6.3.1. Media Type Definition >=20 > Type name: audio >=20 > Subtype name: raptorfec >=20 > Required parameters: >=20 > o rate: The RTP timestamp (clock) rate. The operator SHALL select = a > rate larger than 1000 Hz to provide sufficient resolution to = RTCP > operations and the operator SHOULD select the rate that matches > the rate of the protected source RTP stream. The RTP timestamp > (clock) rate is specified in Hz and the format is unsigned > integer. >=20 > o raptor-scheme-id: The value of this parameter is the FEC Scheme = Id > for the specific Raptor FEC Scheme that will be used as defined = in > [I-D.ietf-fecframe-raptor]. >=20 > o Kmax: The value of this parameter is the FEC Framework > Configuration Information element "Maximum Source Block Length" = as > defined in [I-D.ietf-fecframe-raptor] encoded as a decimal > integer. For specific requirements for this value refer to > [I-D.ietf-fecframe-raptor]. >=20 > o T: The value of this parameter is the FEC Framework = Configuration > Information element "Encoding Symbol Size" as defined in > [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For > specific requirements for this value refer to > [I-D.ietf-fecframe-raptor]. >=20 > o repair-window: The maximum time that spans the source packets = and > the corresponding repair packets. The size of the repair window > is specified in microseconds and the format is unsigned integer. >=20 > Optional parameters: >=20 > o P: The value of this parameter is the FEC Framework = Configuration > Information element "Payload ID Format" as defined in > [I-D.ietf-fecframe-raptor]. If this parameter is missing the > value "A" SHALL be assumed. >=20 > Encoding considerations: This media type is framed and binary, see > section 4.8 in [RFC4288] >=20 > Security considerations: Please see security consideration in > [RFC6363] >=20 > Interoperability considerations: >=20 > Published specification: [I-D.ietf-fecframe-raptor] >=20 > Applications that use this media type: Real-time multimedia > applications like video streaming, audio streaming, and video > conferencing. >=20 > Additional information: >=20 > Magic number(s): >=20 > File extension(s): >=20 > Macintosh file type code(s): >=20 > Person & email address to contact for further information: Thomas > Stockhammer, stockhammer@nomor.de >=20 > Intended usage: COMMON >=20 > Restrictions on usage: This media type depends on RTP framing, and > hence is only defined for transfer via RTP [[RFC3550]]. Transport > within other framing protocols is not defined at this time. >=20 > Author: Thomas Stockhammer, Nomor Research. >=20 > Change controller: IETF Audio/Video Transport working group = delegated > from the IESG. >=20 > 6.4. Registration of the text/raptorfec media type >=20 > This RTP payload format is identified using the text/raptorfec = media > type which is registered in accordance with [RFC4855] and using the > template of [RFC4288]. >=20 > 6.4.1. Media Type Definition >=20 > Type name: text >=20 > Subtype name: raptorfec >=20 > Required parameters: >=20 > o rate: The RTP timestamp (clock) rate. The operator SHALL select = a > rate larger than 1000 Hz to provide sufficient resolution to = RTCP > operations and the operator SHOULD select the rate that matches > the rate of the protected source RTP stream. The RTP timestamp > (clock) rate is specified in Hz and the format is unsigned > integer. >=20 > o raptor-scheme-id: The value of this parameter is the FEC Scheme = Id > for the specific Raptor FEC Scheme that will be used as defined = in > [I-D.ietf-fecframe-raptor]. >=20 > o Kmax: The value of this parameter is the FEC Framework > Configuration Information element "Maximum Source Block Length" = as > defined in [I-D.ietf-fecframe-raptor] encoded as a decimal > integer. For specific requirements for this value refer to > [I-D.ietf-fecframe-raptor]. >=20 > o T: The value of this parameter is the FEC Framework = Configuration > Information element "Encoding Symbol Size" as defined in > [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For > specific requirements for this value refer to > [I-D.ietf-fecframe-raptor]. >=20 > o repair-window: The maximum time that spans the source packets = and > the corresponding repair packets. The size of the repair window > is specified in microseconds and the format is unsigned integer. >=20 > Optional parameters: >=20 > o P: The value of this parameter is the FEC Framework = Configuration > Information element "Payload ID Format" as defined in > [I-D.ietf-fecframe-raptor]. If this parameter is missing the > value "A" SHALL be assumed. >=20 > Encoding considerations: This media type is framed and binary, see > section 4.8 in [RFC4288] >=20 > Security considerations: Please see security consideration in > [RFC6363] >=20 > Interoperability considerations: >=20 > Published specification: [I-D.ietf-fecframe-raptor] >=20 > Applications that use this media type: Real-time multimedia > applications like video streaming, audio streaming, and video > conferencing. >=20 > Additional information: >=20 > Magic number(s): >=20 > File extension(s): >=20 > Macintosh file type code(s): >=20 > Person & email address to contact for further information: Thomas > Stockhammer, stockhammer@nomor.de >=20 > Intended usage: COMMON >=20 > Restrictions on usage: This media type depends on RTP framing, and > hence is only defined for transfer via RTP [[RFC3550]]. Transport > within other framing protocols is not defined at this time. >=20 > Author: Thomas Stockhammer, Nomor Research. >=20 > Change controller: IETF Audio/Video Transport working group = delegated > from the IESG. >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Please provide any comments asap, latest by December 9th. >=20 > Thanks! >=20 > Thomas --- Dr. Thomas Stockhammer (CEO) || stockhammer@nomor.de || phone +49 89 = 978980 02 || cell +491725702667 || http://www.nomor-research.com Nomor Research GmbH - Sitz der Gesellschaft: M=FCnchen - = Registergericht: M=FCnchen, HRB 165856 =96 Umsatzsteuer-ID: DE238047637 = - Gesch=E4ftsf=FChrer: Dr. Thomas Stockhammer, Dr. Ingo Viering. --Apple-Mail=_480A64FD-67C0-4E09-B39E-809F3CB46242 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
6. =  Media Types

6.1. =  Registration of the application/raptorfec media = type

   This = RTP payload format is identified using the = application/raptorfec
   media type which = is registered in accordance with [RFC4855] and = using
   the template of = [RFC4288].

6.1.1. =  Media Type = Definition

  =  Type name: = application

  =  Subtype name: = raptorfec

  =  Required = parameters:

  =  o  rate: The RTP timestamp (clock) rate.  The RTP = timestamp (clock)
      rate is = specified in Hz and the format is unsigned = integer.

   o =  raptor-scheme-id: The value of this parameter is the FEC Scheme = Id
      for the specific Raptor FEC = Scheme that will be used as defined in
  =     = [I-D.ietf-fecframe-raptor].

   o  Kmax: The value of this parameter is the FEC = Framework














<= div>

   Intended usage: = COMMON

  =  Restrictions on usage: This media type depends on RTP framing, = and
   hence is only defined for transfer = via RTP [[RFC3550]].  Transport
  =  within other framing protocols is not defined at this = time.

  =  Author: Thomas Stockhammer, Nomor = Research

  =  Change controller: IETF Audio/Video Transport working group = delegated
   from the = IESG.

6.2. =  Registration of the video/raptorfec media = type

   This = RTP payload format is identified using the video/raptorfec = media
   type which is registered in = accordance with [RFC4855] and using the
  =  template of = [RFC4288].

6.2.1. =  Media Type = Definition

  =  Type name: = video

  =  Subtype name: = raptorfec

  =  Required = parameters:

  =  o  rate: The RTP timestamp (clock) rate.  The RTP = timestamp (clock)
      rate is = specified in Hz and the format is unsigned = integer.

   o =  raptor-scheme-id: The value of this parameter is the FEC Scheme = Id
      for the specific Raptor FEC = Scheme that will be used as defined in
  =     = [I-D.ietf-fecframe-raptor].

   o  Kmax: The value of this parameter is the FEC = Framework
      Configuration = Information element "Maximum Source Block Length" = as
      defined in = [I-D.ietf-fecframe-raptor] encoded as a = decimal
      integer.  For = specific requirements for this value refer = to
      = [I-D.ietf-fecframe-raptor].

   o  T: The value of this parameter is the FEC = Framework Configuration
      = Information element "Encoding Symbol Size" as defined = in
      [I-D.ietf-fecframe-raptor] = encoded as a decimal integer.  For
  =     specific requirements for this value refer = to
      = [I-D.ietf-fecframe-raptor].

   o  repair-window: The maximum time that spans the = source packets and
      the = corresponding repair packets.  The size of the repair = window
      is specified in = microseconds and the format is unsigned = integer.

  =  Optional = parameters:

  =  o  P: The value of this parameter is the FEC Framework = Configuration
      Information = element "Payload ID Format" as defined in
  =     [I-D.ietf-fecframe-raptor].  If this parameter is = missing the
      value "A" SHALL be = assumed.

  =  Encoding considerations: This media type is framed and binary, = see
   section 4.8 in = [RFC4288]

  =  Security considerations: Please see security consideration = in
  =  [RFC6363]

  =  Interoperability = considerations:

  =  Published specification: = [I-D.ietf-fecframe-raptor]

=    Applications that use this media type: Real-time = multimedia
   applications like video = streaming, audio streaming, and video
  =  conferencing.

  =  Additional = information:

  =  Magic number(s): <none = defined>

  =  File extension(s): <none = defined>

  =  Macintosh file type code(s): <none = defined>

  =  Person & email address to contact for further information: = Thomas
   Stockhammer, stockhammer@nomor.de
<= div>

   Intended usage: = COMMON

  =  Restrictions on usage: This media type depends on RTP framing, = and
   hence is only defined for transfer = via RTP [[RFC3550]].  Transport
  =  within other framing protocols is not defined at this = time.

  =  Author: Thomas Stockhammer, Nomor = Research.

  =  Change controller: IETF Audio/Video Transport working group = delegated
   from the = IESG.

6.3. =  Registration of the audio/raptorfec media = type

   This = RTP payload format is identified using the audio/raptorfec = media
   type which is registered in = accordance with [RFC4855] and using the
  =  template of = [RFC4288].

6.3.1. =  Media Type = Definition

  =  Type name: = audio

  =  Subtype name: = raptorfec

  =  Required = parameters:

  =  o  rate: The RTP timestamp (clock) rate.  The RTP = timestamp (clock)
      rate is = specified in Hz and the format is unsigned = integer.

   o =  raptor-scheme-id: The value of this parameter is the FEC Scheme = Id
      for the specific Raptor FEC = Scheme that will be used as defined in
  =     = [I-D.ietf-fecframe-raptor].

   o  Kmax: The value of this parameter is the FEC = Framework
      Configuration = Information element "Maximum Source Block Length" = as
      defined in = [I-D.ietf-fecframe-raptor] encoded as a = decimal
      integer.  For = specific requirements for this value refer = to
      = [I-D.ietf-fecframe-raptor].

   o  T: The value of this parameter is the FEC = Framework Configuration
      = Information element "Encoding Symbol Size" as defined = in
      [I-D.ietf-fecframe-raptor] = encoded as a decimal integer.  For
  =     specific requirements for this value refer = to
      = [I-D.ietf-fecframe-raptor].

   o  repair-window: The maximum time that spans the = source packets and
      the = corresponding repair packets.  The size of the repair = window
      is specified in = microseconds and the format is unsigned = integer.

  =  Optional = parameters:

  =  o  P: The value of this parameter is the FEC Framework = Configuration
      Information = element "Payload ID Format" as defined in
  =     [I-D.ietf-fecframe-raptor].  If this parameter is = missing the
      value "A" SHALL be = assumed.

  =  Encoding considerations: This media type is framed and binary, = see
   section 4.8 in = [RFC4288]

  =  Security considerations: Please see security consideration = in
  =  [RFC6363]

  =  Interoperability = considerations:

  =  Published specification: = [I-D.ietf-fecframe-raptor]

=    Applications that use this media type: Real-time = multimedia
   applications like video = streaming, audio streaming, and video
  =  conferencing.

  =  Additional = information:

  =  Magic number(s): <none = defined>

  =  File extension(s): <none = defined>

  =  Macintosh file type code(s): <none = defined>

  =  Person & email address to contact for further information: = Thomas
   Stockhammer, stockhammer@nomor.de
<= div>

   Intended usage: = COMMON

  =  Restrictions on usage: This media type depends on RTP framing, = and
   hence is only defined for transfer = via RTP [[RFC3550]].  Transport
  =  within other framing protocols is not defined at this = time.

  =  Author: Thomas Stockhammer, Nomor = Research.

  =  Change controller: IETF Audio/Video Transport working group = delegated
   from the = IESG.

6.4. =  Registration of the text/raptorfec media = type

   This = RTP payload format is identified using the text/raptorfec = media
   type which is registered in = accordance with [RFC4855] and using the
  =  template of = [RFC4288].

6.4.1. =  Media Type = Definition

  =  Type name: = text

   Subtype = name: raptorfec

  =  Required = parameters:

  =  o  rate: The RTP timestamp (clock) rate.  The RTP = timestamp (clock)
      rate is = specified in Hz and the format is unsigned = integer.

   o =  raptor-scheme-id: The value of this parameter is the FEC Scheme = Id
      for the specific Raptor FEC = Scheme that will be used as defined in
  =     = [I-D.ietf-fecframe-raptor].

   o  Kmax: The value of this parameter is the FEC = Framework
      Configuration = Information element "Maximum Source Block Length" = as
      defined in = [I-D.ietf-fecframe-raptor] encoded as a = decimal
      integer.  For = specific requirements for this value refer = to
      = [I-D.ietf-fecframe-raptor].

   o  T: The value of this parameter is the FEC = Framework Configuration
      = Information element "Encoding Symbol Size" as defined = in
      [I-D.ietf-fecframe-raptor] = encoded as a decimal integer.  For
  =     specific requirements for this value refer = to
      = [I-D.ietf-fecframe-raptor].

   o  repair-window: The maximum time that spans the = source packets and
      the = corresponding repair packets.  The size of the repair = window
      is specified in = microseconds and the format is unsigned = integer.

  =  Optional = parameters:

  =  o  P: The value of this parameter is the FEC Framework = Configuration
      Information = element "Payload ID Format" as defined in
  =     [I-D.ietf-fecframe-raptor].  If this parameter is = missing the
      value "A" SHALL be = assumed.

  =  Encoding considerations: This media type is framed and binary, = see
   section 4.8 in = [RFC4288]

  =  Security considerations: Please see security consideration = in
  =  [RFC6363]

  =  Interoperability = considerations:

  =  Published specification: = [I-D.ietf-fecframe-raptor]

=    Applications that use this media type: Real-time = multimedia
   applications like video = streaming, audio streaming, and video
  =  conferencing.

  =  Additional = information:

  =  Magic number(s): <none = defined>

  =  File extension(s): <none = defined>

  =  Macintosh file type code(s): <none = defined>

  =  Person & email address to contact for further information: = Thomas
   Stockhammer, stockhammer@nomor.de
<= div>

   Intended usage: = COMMON

  =  Restrictions on usage: This media type depends on RTP framing, = and
   hence is only defined for transfer = via RTP [[RFC3550]].  Transport
  =  within other framing protocols is not defined at this = time.

  =  Author: Thomas Stockhammer, Nomor = Research.

  =  Change controller: IETF Audio/Video Transport working group = delegated
   from the = IESG.

=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D

Please provide any comments asap, = latest by December = 9th.

Thanks!

Thomas


O= n Nov 25, 2011, at 3:00 PM, Thomas Stockhammer wrote:

Dear = experts, 

draft-ietf-fecframe-rtp-raptor-06 = is currently in IESG review. 
Please review its media = type registration as provided = below:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D

6.  Media = Types

6.1.  Registration of the = application/raptorfec media type

  =  This RTP payload format is identified using the = application/raptorfec
   media type which is = registered in accordance with [RFC4855] and using
  =  the template of [RFC4288].

6.1.1. =  Media Type Definition

   Type = name: application

   Subtype name: = raptorfec

   Required = parameters:

   o  rate: The RTP = timestamp (clock) rate.  The operator SHALL select = a
      rate larger than 1000 Hz to provide = sufficient resolution to RTCP
      operations = and the operator SHOULD select the rate that matches
  =     the rate of the protected source RTP stream.  The RTP = timestamp
      (clock) rate is specified in Hz = and the format is unsigned
      = integer.

   o  raptor-scheme-id: = The value of this parameter is the FEC Scheme Id
    =   for the specific Raptor FEC Scheme that will be used as defined = in
      = [I-D.ietf-fecframe-raptor].

   o =  Kmax: The value of this parameter is the FEC = Framework
      Configuration Information = element "Maximum Source Block Length" as
      = defined in [I-D.ietf-fecframe-raptor] encoded as a = decimal
      integer.  For specific = requirements for this value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  T: The value of this parameter is the FEC Framework = Configuration
      Information element = "Encoding Symbol Size" as defined in
      = [I-D.ietf-fecframe-raptor] encoded as a decimal integer. =  For
      specific requirements for this = value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  repair-window: The maximum time that spans the source packets = and
      the corresponding repair packets. =  The size of the repair window
      is = specified in microseconds and the format is unsigned = integer.

   Optional = parameters:

   o  P: The value = of this parameter is the FEC Framework Configuration
  =     Information element "Payload ID Format" as defined = in
      [I-D.ietf-fecframe-raptor].  If = this parameter is missing the
      value "A" = SHALL be assumed.

   Encoding = considerations: This media type is framed and binary, = see
   section 4.8 in = [RFC4288]

   Security considerations: = Please see security consideration in
  =  [RFC6363]

   Interoperability = considerations:

   Published = specification: = [I-D.ietf-fecframe-raptor]

  =  Applications that use this media type: Real-time = multimedia
   applications like video streaming, = audio streaming, and video
  =  conferencing.

   Additional = information:

   Magic number(s): = <none defined>

   File = extension(s): <none defined>

  =  Macintosh file type code(s): <none = defined>

   Person & email = address to contact for further information: Thomas
  =  Stockhammer, stockhammer@nomor.de
   Intended usage: = COMMON

   Restrictions on usage: This = media type depends on RTP framing, and
   hence is = only defined for transfer via RTP [[RFC3550]]. =  Transport
   within other framing protocols is = not defined at this time.

   Author: = Thomas Stockhammer, Nomor Research

  =  Change controller: IETF Audio/Video Transport working group = delegated
   from the = IESG.

6.2.  Registration of the = video/raptorfec media type

   This = RTP payload format is identified using the video/raptorfec = media
   type which is registered in accordance with = [RFC4855] and using the
   template of = [RFC4288].

6.2.1.  Media Type = Definition

   Type name: = video

   Subtype name: = raptorfec

   Required = parameters:

   o  rate: The RTP = timestamp (clock) rate.  The operator SHALL select = a
      rate larger than 1000 Hz to provide = sufficient resolution to RTCP
      operations = and the operator SHOULD select the rate that matches
  =     the rate of the protected source RTP stream.  The RTP = timestamp
      (clock) rate is specified in Hz = and the format is unsigned
      = integer.

   o  raptor-scheme-id: = The value of this parameter is the FEC Scheme Id
    =   for the specific Raptor FEC Scheme that will be used as defined = in
      = [I-D.ietf-fecframe-raptor].

   o =  Kmax: The value of this parameter is the FEC = Framework
      Configuration Information = element "Maximum Source Block Length" as
      = defined in [I-D.ietf-fecframe-raptor] encoded as a = decimal
      integer.  For specific = requirements for this value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  T: The value of this parameter is the FEC Framework = Configuration
      Information element = "Encoding Symbol Size" as defined in
      = [I-D.ietf-fecframe-raptor] encoded as a decimal integer. =  For
      specific requirements for this = value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  repair-window: The maximum time that spans the source packets = and
      the corresponding repair packets. =  The size of the repair window
      is = specified in microseconds and the format is unsigned = integer.

   Optional = parameters:

   o  P: The value = of this parameter is the FEC Framework Configuration
  =     Information element "Payload ID Format" as defined = in
      [I-D.ietf-fecframe-raptor].  If = this parameter is missing the
      value "A" = SHALL be assumed.

   Encoding = considerations: This media type is framed and binary, = see
   section 4.8 in = [RFC4288]

   Security considerations: = Please see security consideration in
  =  [RFC6363]

   Interoperability = considerations:

   Published = specification: = [I-D.ietf-fecframe-raptor]

  =  Applications that use this media type: Real-time = multimedia
   applications like video streaming, = audio streaming, and video
  =  conferencing.

   Additional = information:

   Magic number(s): = <none defined>

   File = extension(s): <none defined>

  =  Macintosh file type code(s): <none = defined>

   Person & email = address to contact for further information: Thomas
  =  Stockhammer, stockhammer@nomor.de
   Intended usage: = COMMON

   Restrictions on usage: This = media type depends on RTP framing, and
   hence is = only defined for transfer via RTP [[RFC3550]]. =  Transport
   within other framing protocols is = not defined at this time.

   Author: = Thomas Stockhammer, Nomor Research.

  =  Change controller: IETF Audio/Video Transport working group = delegated
   from the = IESG.

6.3.  Registration of the = audio/raptorfec media type

   This = RTP payload format is identified using the audio/raptorfec = media
   type which is registered in accordance with = [RFC4855] and using the
   template of = [RFC4288].

6.3.1.  Media Type = Definition

   Type name: = audio

   Subtype name: = raptorfec

   Required = parameters:

   o  rate: The RTP = timestamp (clock) rate.  The operator SHALL select = a
      rate larger than 1000 Hz to provide = sufficient resolution to RTCP
      operations = and the operator SHOULD select the rate that matches
  =     the rate of the protected source RTP stream.  The RTP = timestamp
      (clock) rate is specified in Hz = and the format is unsigned
      = integer.

   o  raptor-scheme-id: = The value of this parameter is the FEC Scheme Id
    =   for the specific Raptor FEC Scheme that will be used as defined = in
      = [I-D.ietf-fecframe-raptor].

   o =  Kmax: The value of this parameter is the FEC = Framework
      Configuration Information = element "Maximum Source Block Length" as
      = defined in [I-D.ietf-fecframe-raptor] encoded as a = decimal
      integer.  For specific = requirements for this value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  T: The value of this parameter is the FEC Framework = Configuration
      Information element = "Encoding Symbol Size" as defined in
      = [I-D.ietf-fecframe-raptor] encoded as a decimal integer. =  For
      specific requirements for this = value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  repair-window: The maximum time that spans the source packets = and
      the corresponding repair packets. =  The size of the repair window
      is = specified in microseconds and the format is unsigned = integer.

   Optional = parameters:

   o  P: The value = of this parameter is the FEC Framework Configuration
  =     Information element "Payload ID Format" as defined = in
      [I-D.ietf-fecframe-raptor].  If = this parameter is missing the
      value "A" = SHALL be assumed.

   Encoding = considerations: This media type is framed and binary, = see
   section 4.8 in = [RFC4288]

   Security considerations: = Please see security consideration in
  =  [RFC6363]

   Interoperability = considerations:

   Published = specification: = [I-D.ietf-fecframe-raptor]

  =  Applications that use this media type: Real-time = multimedia
   applications like video streaming, = audio streaming, and video
  =  conferencing.

   Additional = information:

   Magic number(s): = <none defined>

   File = extension(s): <none defined>

  =  Macintosh file type code(s): <none = defined>

   Person & email = address to contact for further information: Thomas
  =  Stockhammer, stockhammer@nomor.de
   Intended usage: = COMMON

   Restrictions on usage: This = media type depends on RTP framing, and
   hence is = only defined for transfer via RTP [[RFC3550]]. =  Transport
   within other framing protocols is = not defined at this time.

   Author: = Thomas Stockhammer, Nomor Research.

  =  Change controller: IETF Audio/Video Transport working group = delegated
   from the = IESG.

6.4.  Registration of the = text/raptorfec media type

   This RTP = payload format is identified using the text/raptorfec = media
   type which is registered in accordance with = [RFC4855] and using the
   template of = [RFC4288].

6.4.1.  Media Type = Definition

   Type name: = text

   Subtype name: = raptorfec

   Required = parameters:

   o  rate: The RTP = timestamp (clock) rate.  The operator SHALL select = a
      rate larger than 1000 Hz to provide = sufficient resolution to RTCP
      operations = and the operator SHOULD select the rate that matches
  =     the rate of the protected source RTP stream.  The RTP = timestamp
      (clock) rate is specified in Hz = and the format is unsigned
      = integer.

   o  raptor-scheme-id: = The value of this parameter is the FEC Scheme Id
    =   for the specific Raptor FEC Scheme that will be used as defined = in
      = [I-D.ietf-fecframe-raptor].

   o =  Kmax: The value of this parameter is the FEC = Framework
      Configuration Information = element "Maximum Source Block Length" as
      = defined in [I-D.ietf-fecframe-raptor] encoded as a = decimal
      integer.  For specific = requirements for this value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  T: The value of this parameter is the FEC Framework = Configuration
      Information element = "Encoding Symbol Size" as defined in
      = [I-D.ietf-fecframe-raptor] encoded as a decimal integer. =  For
      specific requirements for this = value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  repair-window: The maximum time that spans the source packets = and
      the corresponding repair packets. =  The size of the repair window
      is = specified in microseconds and the format is unsigned = integer.

   Optional = parameters:

   o  P: The value = of this parameter is the FEC Framework Configuration
  =     Information element "Payload ID Format" as defined = in
      [I-D.ietf-fecframe-raptor].  If = this parameter is missing the
      value "A" = SHALL be assumed.

   Encoding = considerations: This media type is framed and binary, = see
   section 4.8 in = [RFC4288]

   Security considerations: = Please see security consideration in
  =  [RFC6363]

   Interoperability = considerations:

   Published = specification: = [I-D.ietf-fecframe-raptor]

  =  Applications that use this media type: Real-time = multimedia
   applications like video streaming, = audio streaming, and video
  =  conferencing.

   Additional = information:

   Magic number(s): = <none defined>

   File = extension(s): <none defined>

  =  Macintosh file type code(s): <none = defined>

   Person & email = address to contact for further information: Thomas
  =  Stockhammer, stockhammer@nomor.de
   Intended usage: = COMMON

   Restrictions on usage: This = media type depends on RTP framing, and
   hence is = only defined for transfer via RTP [[RFC3550]]. =  Transport
   within other framing protocols is = not defined at this time.

   Author: = Thomas Stockhammer, Nomor Research.

  =  Change controller: IETF Audio/Video Transport working group = delegated
   from the = IESG.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D

Please provide any comments asap, = latest by December = 9th.

Thanks!

Thomas

stockhammer@nomor.de || = phone +49 89 978980 02 || cell +491725702667 || http://www.nomor-research.com
Nomor Research GmbH  -  Sitz = der Gesellschaft: M=FCnchen - Registergericht: M=FCnchen, HRB 165856 =96 = Umsatzsteuer-ID: DE238047637 - Gesch=E4ftsf=FChrer: Dr. Thomas = Stockhammer, Dr. Ingo Viering.






= --Apple-Mail=_480A64FD-67C0-4E09-B39E-809F3CB46242-- Return-Path: 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 2370621F8C1A for ; Fri, 25 Nov 2011 06:21:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.449 X-Spam-Level: X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 KZA0L9tKPmAB for ; Fri, 25 Nov 2011 06:21:03 -0800 (PST) Received: from pechora2.lax.icann.org (pechora2.icann.org [IPv6:2620:0:2d0:201::1:72]) by ietfa.amsl.com (Postfix) with ESMTP id 5BF5B21F8C17 for ; Fri, 25 Nov 2011 06:21:03 -0800 (PST) Received: from mo-p00-ob6.rzone.de (mo-p00-ob6.rzone.de [IPv6:2a01:238:20a:202:53f0::1]) by pechora2.lax.icann.org (8.13.8/8.13.8) with ESMTP id pAPEKfT1004709 for ; Fri, 25 Nov 2011 14:21:02 GMT DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1322230841; l=37149; s=domk; d=nomor.de; h=Mime-Version:To:Date:Subject:Content-Type:From:X-RZG-CLASS-ID: X-RZG-AUTH; bh=KE9qVxRRtt5zp8V+nNfO6KsriFY=; b=wP5z124t/oSu1c01SZDCy3k2B/tAVkc8yKTHVvQTPNgs6TD02/JgYRzeW/QbazGI+mC 8LVjGWI52GAi7HK//zYs5Wvif1BwWezlr26fqiRILdZjZ/AnvZXVDEiICiqe/W8SDpxVl PKcIhSiHqHhR8iu5BVqmp1LSa20HKy7Hqn4= X-RZG-AUTH: :P3gLdkugevKirJkjH/RoTtk5THWq6nlFgKpnuMPeiu13+UwGfuMVAY1fXI1g9SU= X-RZG-CLASS-ID: mo00 Received: from [192.168.0.170] ([93.104.202.244]) by smtp.strato.de (cohen mo1) (RZmta 26.10 AUTH) with ESMTPA id e03c27nAPDF25g for ; Fri, 25 Nov 2011 15:00:40 +0100 (MET) From: Thomas Stockhammer Content-Type: multipart/alternative; boundary="Apple-Mail=_10A6E04A-5DE8-494E-A98F-6DB5A0000185" Date: Fri, 25 Nov 2011 15:00:40 +0100 Message-Id: <1A2E179F-088C-4C70-8C3E-DC1507BED7E6@nomor.de> To: ietf-types@iana.org Mime-Version: 1.0 (Apple Message framework v1251.1) X-Mailer: Apple Mail (2.1251.1) X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora2.lax.icann.org [IPv6:2620:0:2d0:201::1:72]); Fri, 25 Nov 2011 14:21:03 +0000 (UTC) Subject: [ietf-types] Media Types in draft-ietf-fecframe-rtp-raptor-06 X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2011 14:21:05 -0000 --Apple-Mail=_10A6E04A-5DE8-494E-A98F-6DB5A0000185 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Dear experts,=20 draft-ietf-fecframe-rtp-raptor-06 is currently in IESG review.=20 Please review its media type registration as provided below: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 6. Media Types 6.1. Registration of the application/raptorfec media type This RTP payload format is identified using the application/raptorfec media type which is registered in accordance with [RFC4855] and using the template of [RFC4288]. 6.1.1. Media Type Definition Type name: application Subtype name: raptorfec Required parameters: o rate: The RTP timestamp (clock) rate. The operator SHALL select a rate larger than 1000 Hz to provide sufficient resolution to RTCP operations and the operator SHOULD select the rate that matches the rate of the protected source RTP stream. The RTP timestamp (clock) rate is specified in Hz and the format is unsigned integer. o raptor-scheme-id: The value of this parameter is the FEC Scheme Id for the specific Raptor FEC Scheme that will be used as defined in [I-D.ietf-fecframe-raptor]. o Kmax: The value of this parameter is the FEC Framework Configuration Information element "Maximum Source Block Length" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o T: The value of this parameter is the FEC Framework Configuration Information element "Encoding Symbol Size" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o repair-window: The maximum time that spans the source packets and the corresponding repair packets. The size of the repair window is specified in microseconds and the format is unsigned integer. Optional parameters: o P: The value of this parameter is the FEC Framework Configuration Information element "Payload ID Format" as defined in [I-D.ietf-fecframe-raptor]. If this parameter is missing the value "A" SHALL be assumed. Encoding considerations: This media type is framed and binary, see section 4.8 in [RFC4288] Security considerations: Please see security consideration in [RFC6363] Interoperability considerations: Published specification: [I-D.ietf-fecframe-raptor] Applications that use this media type: Real-time multimedia applications like video streaming, audio streaming, and video conferencing. Additional information: Magic number(s): File extension(s): Macintosh file type code(s): Person & email address to contact for further information: Thomas Stockhammer, stockhammer@nomor.de Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP [[RFC3550]]. Transport within other framing protocols is not defined at this time. Author: Thomas Stockhammer, Nomor Research Change controller: IETF Audio/Video Transport working group delegated from the IESG. 6.2. Registration of the video/raptorfec media type This RTP payload format is identified using the video/raptorfec media type which is registered in accordance with [RFC4855] and using the template of [RFC4288]. 6.2.1. Media Type Definition Type name: video Subtype name: raptorfec Required parameters: o rate: The RTP timestamp (clock) rate. The operator SHALL select a rate larger than 1000 Hz to provide sufficient resolution to RTCP operations and the operator SHOULD select the rate that matches the rate of the protected source RTP stream. The RTP timestamp (clock) rate is specified in Hz and the format is unsigned integer. o raptor-scheme-id: The value of this parameter is the FEC Scheme Id for the specific Raptor FEC Scheme that will be used as defined in [I-D.ietf-fecframe-raptor]. o Kmax: The value of this parameter is the FEC Framework Configuration Information element "Maximum Source Block Length" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o T: The value of this parameter is the FEC Framework Configuration Information element "Encoding Symbol Size" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o repair-window: The maximum time that spans the source packets and the corresponding repair packets. The size of the repair window is specified in microseconds and the format is unsigned integer. Optional parameters: o P: The value of this parameter is the FEC Framework Configuration Information element "Payload ID Format" as defined in [I-D.ietf-fecframe-raptor]. If this parameter is missing the value "A" SHALL be assumed. Encoding considerations: This media type is framed and binary, see section 4.8 in [RFC4288] Security considerations: Please see security consideration in [RFC6363] Interoperability considerations: Published specification: [I-D.ietf-fecframe-raptor] Applications that use this media type: Real-time multimedia applications like video streaming, audio streaming, and video conferencing. Additional information: Magic number(s): File extension(s): Macintosh file type code(s): Person & email address to contact for further information: Thomas Stockhammer, stockhammer@nomor.de Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP [[RFC3550]]. Transport within other framing protocols is not defined at this time. Author: Thomas Stockhammer, Nomor Research. Change controller: IETF Audio/Video Transport working group delegated from the IESG. 6.3. Registration of the audio/raptorfec media type This RTP payload format is identified using the audio/raptorfec media type which is registered in accordance with [RFC4855] and using the template of [RFC4288]. 6.3.1. Media Type Definition Type name: audio Subtype name: raptorfec Required parameters: o rate: The RTP timestamp (clock) rate. The operator SHALL select a rate larger than 1000 Hz to provide sufficient resolution to RTCP operations and the operator SHOULD select the rate that matches the rate of the protected source RTP stream. The RTP timestamp (clock) rate is specified in Hz and the format is unsigned integer. o raptor-scheme-id: The value of this parameter is the FEC Scheme Id for the specific Raptor FEC Scheme that will be used as defined in [I-D.ietf-fecframe-raptor]. o Kmax: The value of this parameter is the FEC Framework Configuration Information element "Maximum Source Block Length" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o T: The value of this parameter is the FEC Framework Configuration Information element "Encoding Symbol Size" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o repair-window: The maximum time that spans the source packets and the corresponding repair packets. The size of the repair window is specified in microseconds and the format is unsigned integer. Optional parameters: o P: The value of this parameter is the FEC Framework Configuration Information element "Payload ID Format" as defined in [I-D.ietf-fecframe-raptor]. If this parameter is missing the value "A" SHALL be assumed. Encoding considerations: This media type is framed and binary, see section 4.8 in [RFC4288] Security considerations: Please see security consideration in [RFC6363] Interoperability considerations: Published specification: [I-D.ietf-fecframe-raptor] Applications that use this media type: Real-time multimedia applications like video streaming, audio streaming, and video conferencing. Additional information: Magic number(s): File extension(s): Macintosh file type code(s): Person & email address to contact for further information: Thomas Stockhammer, stockhammer@nomor.de Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP [[RFC3550]]. Transport within other framing protocols is not defined at this time. Author: Thomas Stockhammer, Nomor Research. Change controller: IETF Audio/Video Transport working group delegated from the IESG. 6.4. Registration of the text/raptorfec media type This RTP payload format is identified using the text/raptorfec media type which is registered in accordance with [RFC4855] and using the template of [RFC4288]. 6.4.1. Media Type Definition Type name: text Subtype name: raptorfec Required parameters: o rate: The RTP timestamp (clock) rate. The operator SHALL select a rate larger than 1000 Hz to provide sufficient resolution to RTCP operations and the operator SHOULD select the rate that matches the rate of the protected source RTP stream. The RTP timestamp (clock) rate is specified in Hz and the format is unsigned integer. o raptor-scheme-id: The value of this parameter is the FEC Scheme Id for the specific Raptor FEC Scheme that will be used as defined in [I-D.ietf-fecframe-raptor]. o Kmax: The value of this parameter is the FEC Framework Configuration Information element "Maximum Source Block Length" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o T: The value of this parameter is the FEC Framework Configuration Information element "Encoding Symbol Size" as defined in [I-D.ietf-fecframe-raptor] encoded as a decimal integer. For specific requirements for this value refer to [I-D.ietf-fecframe-raptor]. o repair-window: The maximum time that spans the source packets and the corresponding repair packets. The size of the repair window is specified in microseconds and the format is unsigned integer. Optional parameters: o P: The value of this parameter is the FEC Framework Configuration Information element "Payload ID Format" as defined in [I-D.ietf-fecframe-raptor]. If this parameter is missing the value "A" SHALL be assumed. Encoding considerations: This media type is framed and binary, see section 4.8 in [RFC4288] Security considerations: Please see security consideration in [RFC6363] Interoperability considerations: Published specification: [I-D.ietf-fecframe-raptor] Applications that use this media type: Real-time multimedia applications like video streaming, audio streaming, and video conferencing. Additional information: Magic number(s): File extension(s): Macintosh file type code(s): Person & email address to contact for further information: Thomas Stockhammer, stockhammer@nomor.de Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP [[RFC3550]]. Transport within other framing protocols is not defined at this time. Author: Thomas Stockhammer, Nomor Research. Change controller: IETF Audio/Video Transport working group delegated from the IESG. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Please provide any comments asap, latest by December 9th. Thanks! Thomas --- Dr. Thomas Stockhammer (CEO) || stockhammer@nomor.de || phone +49 89 = 978980 02 || cell +491725702667 || http://www.nomor-research.com Nomor Research GmbH - Sitz der Gesellschaft: M=FCnchen - = Registergericht: M=FCnchen, HRB 165856 =96 Umsatzsteuer-ID: DE238047637 = - Gesch=E4ftsf=FChrer: Dr. Thomas Stockhammer, Dr. Ingo Viering. --Apple-Mail=_10A6E04A-5DE8-494E-A98F-6DB5A0000185 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
6.  Media = Types

6.1.  Registration of the = application/raptorfec media type

  =  This RTP payload format is identified using the = application/raptorfec
   media type which is = registered in accordance with [RFC4855] and using
  =  the template of [RFC4288].

6.1.1. =  Media Type Definition

   Type = name: application

   Subtype name: = raptorfec

   Required = parameters:

   o  rate: The RTP = timestamp (clock) rate.  The operator SHALL select = a
      rate larger than 1000 Hz to provide = sufficient resolution to RTCP
      operations = and the operator SHOULD select the rate that matches
  =     the rate of the protected source RTP stream.  The RTP = timestamp
      (clock) rate is specified in Hz = and the format is unsigned
      = integer.

   o  raptor-scheme-id: = The value of this parameter is the FEC Scheme Id
    =   for the specific Raptor FEC Scheme that will be used as defined = in
      = [I-D.ietf-fecframe-raptor].

   o =  Kmax: The value of this parameter is the FEC = Framework
      Configuration Information = element "Maximum Source Block Length" as
      = defined in [I-D.ietf-fecframe-raptor] encoded as a = decimal
      integer.  For specific = requirements for this value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  T: The value of this parameter is the FEC Framework = Configuration
      Information element = "Encoding Symbol Size" as defined in
      = [I-D.ietf-fecframe-raptor] encoded as a decimal integer. =  For
      specific requirements for this = value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  repair-window: The maximum time that spans the source packets = and
      the corresponding repair packets. =  The size of the repair window
      is = specified in microseconds and the format is unsigned = integer.

   Optional = parameters:

   o  P: The value = of this parameter is the FEC Framework Configuration
  =     Information element "Payload ID Format" as defined = in
      [I-D.ietf-fecframe-raptor].  If = this parameter is missing the
      value "A" = SHALL be assumed.

   Encoding = considerations: This media type is framed and binary, = see
   section 4.8 in = [RFC4288]

   Security considerations: = Please see security consideration in
  =  [RFC6363]

   Interoperability = considerations:

   Published = specification: = [I-D.ietf-fecframe-raptor]

  =  Applications that use this media type: Real-time = multimedia
   applications like video streaming, = audio streaming, and video
  =  conferencing.

   Additional = information:

   Magic number(s): = <none defined>

   File = extension(s): <none defined>

  =  Macintosh file type code(s): <none = defined>

   Person & email = address to contact for further information: Thomas
  =  Stockhammer, stockhammer@nomor.de
   Intended usage: = COMMON

   Restrictions on usage: This = media type depends on RTP framing, and
   hence is = only defined for transfer via RTP [[RFC3550]]. =  Transport
   within other framing protocols is = not defined at this time.

   Author: = Thomas Stockhammer, Nomor Research

  =  Change controller: IETF Audio/Video Transport working group = delegated
   from the = IESG.

6.2.  Registration of the = video/raptorfec media type

   This = RTP payload format is identified using the video/raptorfec = media
   type which is registered in accordance with = [RFC4855] and using the
   template of = [RFC4288].

6.2.1.  Media Type = Definition

   Type name: = video

   Subtype name: = raptorfec

   Required = parameters:

   o  rate: The RTP = timestamp (clock) rate.  The operator SHALL select = a
      rate larger than 1000 Hz to provide = sufficient resolution to RTCP
      operations = and the operator SHOULD select the rate that matches
  =     the rate of the protected source RTP stream.  The RTP = timestamp
      (clock) rate is specified in Hz = and the format is unsigned
      = integer.

   o  raptor-scheme-id: = The value of this parameter is the FEC Scheme Id
    =   for the specific Raptor FEC Scheme that will be used as defined = in
      = [I-D.ietf-fecframe-raptor].

   o =  Kmax: The value of this parameter is the FEC = Framework
      Configuration Information = element "Maximum Source Block Length" as
      = defined in [I-D.ietf-fecframe-raptor] encoded as a = decimal
      integer.  For specific = requirements for this value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  T: The value of this parameter is the FEC Framework = Configuration
      Information element = "Encoding Symbol Size" as defined in
      = [I-D.ietf-fecframe-raptor] encoded as a decimal integer. =  For
      specific requirements for this = value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  repair-window: The maximum time that spans the source packets = and
      the corresponding repair packets. =  The size of the repair window
      is = specified in microseconds and the format is unsigned = integer.

   Optional = parameters:

   o  P: The value = of this parameter is the FEC Framework Configuration
  =     Information element "Payload ID Format" as defined = in
      [I-D.ietf-fecframe-raptor].  If = this parameter is missing the
      value "A" = SHALL be assumed.

   Encoding = considerations: This media type is framed and binary, = see
   section 4.8 in = [RFC4288]

   Security considerations: = Please see security consideration in
  =  [RFC6363]

   Interoperability = considerations:

   Published = specification: = [I-D.ietf-fecframe-raptor]

  =  Applications that use this media type: Real-time = multimedia
   applications like video streaming, = audio streaming, and video
  =  conferencing.

   Additional = information:

   Magic number(s): = <none defined>

   File = extension(s): <none defined>

  =  Macintosh file type code(s): <none = defined>

   Person & email = address to contact for further information: Thomas
  =  Stockhammer, stockhammer@nomor.de
   Intended usage: = COMMON

   Restrictions on usage: This = media type depends on RTP framing, and
   hence is = only defined for transfer via RTP [[RFC3550]]. =  Transport
   within other framing protocols is = not defined at this time.

   Author: = Thomas Stockhammer, Nomor Research.

  =  Change controller: IETF Audio/Video Transport working group = delegated
   from the = IESG.

6.3.  Registration of the = audio/raptorfec media type

   This = RTP payload format is identified using the audio/raptorfec = media
   type which is registered in accordance with = [RFC4855] and using the
   template of = [RFC4288].

6.3.1.  Media Type = Definition

   Type name: = audio

   Subtype name: = raptorfec

   Required = parameters:

   o  rate: The RTP = timestamp (clock) rate.  The operator SHALL select = a
      rate larger than 1000 Hz to provide = sufficient resolution to RTCP
      operations = and the operator SHOULD select the rate that matches
  =     the rate of the protected source RTP stream.  The RTP = timestamp
      (clock) rate is specified in Hz = and the format is unsigned
      = integer.

   o  raptor-scheme-id: = The value of this parameter is the FEC Scheme Id
    =   for the specific Raptor FEC Scheme that will be used as defined = in
      = [I-D.ietf-fecframe-raptor].

   o =  Kmax: The value of this parameter is the FEC = Framework
      Configuration Information = element "Maximum Source Block Length" as
      = defined in [I-D.ietf-fecframe-raptor] encoded as a = decimal
      integer.  For specific = requirements for this value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  T: The value of this parameter is the FEC Framework = Configuration
      Information element = "Encoding Symbol Size" as defined in
      = [I-D.ietf-fecframe-raptor] encoded as a decimal integer. =  For
      specific requirements for this = value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  repair-window: The maximum time that spans the source packets = and
      the corresponding repair packets. =  The size of the repair window
      is = specified in microseconds and the format is unsigned = integer.

   Optional = parameters:

   o  P: The value = of this parameter is the FEC Framework Configuration
  =     Information element "Payload ID Format" as defined = in
      [I-D.ietf-fecframe-raptor].  If = this parameter is missing the
      value "A" = SHALL be assumed.

   Encoding = considerations: This media type is framed and binary, = see
   section 4.8 in = [RFC4288]

   Security considerations: = Please see security consideration in
  =  [RFC6363]

   Interoperability = considerations:

   Published = specification: = [I-D.ietf-fecframe-raptor]

  =  Applications that use this media type: Real-time = multimedia
   applications like video streaming, = audio streaming, and video
  =  conferencing.

   Additional = information:

   Magic number(s): = <none defined>

   File = extension(s): <none defined>

  =  Macintosh file type code(s): <none = defined>

   Person & email = address to contact for further information: Thomas
  =  Stockhammer, stockhammer@nomor.de
   Intended usage: = COMMON

   Restrictions on usage: This = media type depends on RTP framing, and
   hence is = only defined for transfer via RTP [[RFC3550]]. =  Transport
   within other framing protocols is = not defined at this time.

   Author: = Thomas Stockhammer, Nomor Research.

  =  Change controller: IETF Audio/Video Transport working group = delegated
   from the = IESG.

6.4.  Registration of the = text/raptorfec media type

   This RTP = payload format is identified using the text/raptorfec = media
   type which is registered in accordance with = [RFC4855] and using the
   template of = [RFC4288].

6.4.1.  Media Type = Definition

   Type name: = text

   Subtype name: = raptorfec

   Required = parameters:

   o  rate: The RTP = timestamp (clock) rate.  The operator SHALL select = a
      rate larger than 1000 Hz to provide = sufficient resolution to RTCP
      operations = and the operator SHOULD select the rate that matches
  =     the rate of the protected source RTP stream.  The RTP = timestamp
      (clock) rate is specified in Hz = and the format is unsigned
      = integer.

   o  raptor-scheme-id: = The value of this parameter is the FEC Scheme Id
    =   for the specific Raptor FEC Scheme that will be used as defined = in
      = [I-D.ietf-fecframe-raptor].

   o =  Kmax: The value of this parameter is the FEC = Framework
      Configuration Information = element "Maximum Source Block Length" as
      = defined in [I-D.ietf-fecframe-raptor] encoded as a = decimal
      integer.  For specific = requirements for this value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  T: The value of this parameter is the FEC Framework = Configuration
      Information element = "Encoding Symbol Size" as defined in
      = [I-D.ietf-fecframe-raptor] encoded as a decimal integer. =  For
      specific requirements for this = value refer to
      = [I-D.ietf-fecframe-raptor].

   o =  repair-window: The maximum time that spans the source packets = and
      the corresponding repair packets. =  The size of the repair window
      is = specified in microseconds and the format is unsigned = integer.

   Optional = parameters:

   o  P: The value = of this parameter is the FEC Framework Configuration
  =     Information element "Payload ID Format" as defined = in
      [I-D.ietf-fecframe-raptor].  If = this parameter is missing the
      value "A" = SHALL be assumed.

   Encoding = considerations: This media type is framed and binary, = see
   section 4.8 in = [RFC4288]

   Security considerations: = Please see security consideration in
  =  [RFC6363]

   Interoperability = considerations:

   Published = specification: = [I-D.ietf-fecframe-raptor]

  =  Applications that use this media type: Real-time = multimedia
   applications like video streaming, = audio streaming, and video
  =  conferencing.

   Additional = information:

   Magic number(s): = <none defined>

   File = extension(s): <none defined>

  =  Macintosh file type code(s): <none = defined>

   Person & email = address to contact for further information: Thomas
  =  Stockhammer, stockhammer@nomor.de
   Intended usage: = COMMON

   Restrictions on usage: This = media type depends on RTP framing, and
   hence is = only defined for transfer via RTP [[RFC3550]]. =  Transport
   within other framing protocols is = not defined at this time.

   Author: = Thomas Stockhammer, Nomor Research.

  =  Change controller: IETF Audio/Video Transport working group = delegated
   from the = IESG.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D

Please provide any comments asap, = latest by December = 9th.

Thanks!

Thomas
stockhammer@nomor.de || = phone +49 89 978980 02 || cell +491725702667 || http://www.nomor-research.com
Nomor Research GmbH  -  Sitz = der Gesellschaft: M=FCnchen - Registergericht: M=FCnchen, HRB 165856 =96 = Umsatzsteuer-ID: DE238047637 - Gesch=E4ftsf=FChrer: Dr. Thomas = Stockhammer, Dr. Ingo Viering.






= --Apple-Mail=_10A6E04A-5DE8-494E-A98F-6DB5A0000185-- Return-Path: 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 145CE21F8BF3 for ; Fri, 25 Nov 2011 06:19:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.545 X-Spam-Level: X-Spam-Status: No, score=-1.545 tagged_above=-999 required=5 tests=[AWL=-0.943, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, MIME_QP_LONG_LINE=1.396] 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 vJyi9OtoWZPp for ; Fri, 25 Nov 2011 06:19:43 -0800 (PST) Received: from pechora7.dc.icann.org (pechora7.icann.org [IPv6:2620:0:2830:201::1:73]) by ietfa.amsl.com (Postfix) with ESMTP id CB45321F8BF0 for ; Fri, 25 Nov 2011 06:19:41 -0800 (PST) Received: from mo-p00-ob6.rzone.de (mo-p00-ob6.rzone.de [IPv6:2a01:238:20a:202:53f0::1]) by pechora7.dc.icann.org (8.13.8/8.13.8) with ESMTP id pAPEJKGh005494 for ; Fri, 25 Nov 2011 09:19:40 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1322230759; l=35497; s=domk; d=nomor.de; h=Mime-Version:To:Cc:Date:Subject:Content-Type:From:X-RZG-CLASS-ID: X-RZG-AUTH; bh=pNwahoHym3Zee4v3/r3rdIHzH8E=; b=BPOZFFJX2BItKQ+xji135NubBEOeFdEpnvSpqTDZkivf3CgSzqozjOeasyvmh49GS+8 RFEXwbCCxbWgRk0O3w2kxvFVvEB8o7Is21N7FrU+qK6X69ETcGZL+xZHQsl4mvjc79RV/ nx+bCPBEz1x9Dg97KF9eDPjnTghDIw+eT20= X-RZG-AUTH: :P3gLdkugevKirJkjH/RoTtk5THWq6nlFgKpnuMPeiu13+UwGfuMVAY1fXI1g9SU= X-RZG-CLASS-ID: mo00 Received: from [192.168.0.170] ([93.104.202.244]) by post.strato.de (mrclete mo63) (RZmta 26.10 AUTH) with ESMTPA id 2035f9nAPCpe0s ; Fri, 25 Nov 2011 15:19:04 +0100 (MET) From: Thomas Stockhammer Content-Type: multipart/alternative; boundary="Apple-Mail=_2461D033-7323-43E6-B855-66E2793E3B8E" Date: Fri, 25 Nov 2011 15:19:04 +0100 Message-Id: <203C8BD8-69F9-4AD9-B1A7-23D83D6F72D8@nomor.de> To: ietf-types@iana.org Mime-Version: 1.0 (Apple Message framework v1251.1) X-Mailer: Apple Mail (2.1251.1) X-Greylist: Delayed for 00:18:32 by milter-greylist-4.2.3 (pechora7.dc.icann.org [IPv6:2620:0:2830:201::1:73]); Fri, 25 Nov 2011 09:19:41 -0500 (EST) Cc: List DASH Subject: [ietf-types] Media type registration of DASH MPD X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2011 14:19:44 -0000 --Apple-Mail=_2461D033-7323-43E6-B855-66E2793E3B8E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Dear experts,=20 MPEG-DASH in ISO/IEC 23009-1 has passed DIS ballot and is in the final = editing stages:=20 Please review media type registration of the MPD as provided below: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Annex C: MIME type registration for MPD C.1 Introduction This Annex provides the formal MIME type registration for the MPD. It = is referenced from the registry at http://www.iana.org/. C.2 MIME type and subtype The MIME Type and Subtype are defined as follows: =E2=8E=AF MIME media type name: application =E2=8E=AF MIME subtype name: dash+xml =E2=8E=AF Required parameters: none =E2=8E=AF Optional parameters: The =E2=80=98profiles=E2=80=99 = parameter as documented in Annex C.3.1 in this part of ISO/IEC 23009 =E2=8E=AF Encoding considerations: the same media type = encoding considerations specified in section 3.2 of RFC 3023 =E2=8E=AF Security considerations: The MPD is a Media = Presentation Description and contains references to other resources. It = is coded in XML, and there are risks that deliberately malformed XML = could cause security issues. In addition, an MPD could be authored that = causes receiving clients to access other resources; if widely = distributed, this could be used to cause a denial-of-service attack. =E2=8E=AF Interoperability considerations:=20 The specification defines a platform-independent expression of a = presentation, and it is intended that wide interoperability can be = achieved. =E2=8E=AF Published specification: ISO/IEC 23009-1: = Information technology =E2=80=94 Dynamic adaptive streaming over HTTP = (DASH) =E2=80=94 Part 1: Dynamic adaptive streaming over HTTP (DASH) =E2=8E=AF Applications which use this media type: various =E2=8E=AF Additional information: =E2=8E=AF File extension(s): = mpd =E2=8E=AF Intended usage: = common =E2=8E=AF Other Information/General Comment: none =E2=8E=AF Person to contact for further information: =E2=8E=AF Name: Thomas Stockhammer =E2=8E=AF Email: stockhammer@nomor.de =E2=8E=AF Author/Change controller: ISO/IEC JTC1/SC29 (MPEG) C.3 Parameters C.3.1 The profiles parameter Parameter name: profiles Parameter value: The 'profiles' parameter is an optional = parameter that indicates one or more profiles to which the file claims = conformance. The contents of this attribute shall conform to either the = pro-simp or pro-fancy productions of RFC6381, Section 4.5. The profile = identifiers reported in the MIME type parameter should match identically = the profiles reported in the profiles attribute in the MPD itself (see = Clause 8). example: = application/dash+xml;profiles=3D"urn:mpeg:dash:profiles:mythical,urn:3gpp:= dash:profiles:fictional" =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Please provide any comments asap, latest by December 6th. Thanks! Thomas --- Dr. Thomas Stockhammer (CEO) || stockhammer@nomor.de || phone +49 89 = 978980 02 || cell +491725702667 || http://www.nomor-research.com Nomor Research GmbH - Sitz der Gesellschaft: M=C3=BCnchen - = Registergericht: M=C3=BCnchen, HRB 165856 =E2=80=93 Umsatzsteuer-ID: = DE238047637 - Gesch=C3=A4ftsf=C3=BChrer: Dr. Thomas Stockhammer, Dr. = Ingo Viering. --Apple-Mail=_2461D033-7323-43E6-B855-66E2793E3B8E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Annex C: 

C.1 = Introduction
 This Annex provides the = formal MIME type registration for the MPD. It is referenced from the = registry at http://www.iana.org/.

C.2 MIME type and = subtype
 The MIME Type and Subtype are defined = as follows:
 =E2=8E=AF MIME = media type name: = application
 =E2=8E=AF MIME = subtype name: = dash+xml
 =E2=8E=AF Required = parameters: = none
 =E2=8E=AF Optional = parameters: = The =E2=80=98profiles=E2=80=99 parameter as documented in Annex = C.3.1 in this part of ISO/IEC 23009
 =E2=8E=AF Encoding = considerations: = the same media type encoding considerations specified in section = 3.2 of RFC 3023
 =E2=8E=AF Security = considerations: = The MPD is a Media Presentation Description and contains = references to other resources. It is coded in XML, and there are = risks that deliberately malformed XML could cause security issues. = In addition, an MPD could be authored that causes receiving clients = to access other resources; if widely distributed, this could be = used to cause a denial-of-service = attack.
 =E2=8E=AF Interoperability = considerations: 
The specification defines a = platform-independent expression of a presentation, and it is intended = that wide interoperability can be = achieved.
 =E2=8E=AF Published = specification: = ISO/IEC 23009-1: Information technology =E2=80=94 Dynamic = adaptive streaming over HTTP (DASH) =E2=80=94 Part 1: Dynamic = adaptive streaming over HTTP (DASH)
 =E2=8E=AF = Applications which use this media type:  = various
 =E2=8E=AF = Additional information:
  =E2=8E=AF File = extension(s): = mpd
=  =E2=8E=AF Intended usage: = common
 =E2=8E=AF Other = Information/General Comment: = none
 =E2=8E=AF Person to = contact for further information:
  =E2=8E=AF = Name: = Thomas Stockhammer
  =E2=8E=AF = Email: = stockhammer@nomor.de
<= div>
 =E2=8E=AF Author/Change controller: ISO/IEC = JTC1/SC29 (MPEG)

C.3 = Parameters
 C.3.1 The = profiles parameter
 Parameter name: = profiles
 Parameter value: The = 'profiles' parameter is an optional parameter that indicates one or more = profiles to which the file claims conformance. The contents of this = attribute shall conform to either the pro-simp or pro-fancy productions = of RFC6381, Section 4.5. The profile identifiers reported in the = MIME type parameter should match identically the profiles reported = in the profiles attribute in the MPD itself (see Clause = 8).

 example:
  = application/dash+xml;profiles=3D"urn:mpeg:dash:profiles:mythical,ur= n:3gpp:dash:profiles:fictional"

=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Please provide any = comments asap, latest by December = 6th.

Thanks!

Thomas
stockhammer@nomor.de || = phone +49 89 978980 02 || cell +491725702667 || http://www.nomor-research.com
Nomor Research GmbH  -  Sitz = der Gesellschaft: M=C3=BCnchen - Registergericht: M=C3=BCnchen, HRB = 165856 =E2=80=93 Umsatzsteuer-ID: DE238047637 - Gesch=C3=A4ftsf=C3=BChrer:= Dr. Thomas Stockhammer, Dr. Ingo Viering.






= --Apple-Mail=_2461D033-7323-43E6-B855-66E2793E3B8E-- Return-Path: 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 09EB711E8205 for ; Sun, 13 Nov 2011 22:29:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.882 X-Spam-Level: X-Spam-Status: No, score=-102.882 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_LOW=-1, 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 0BsDYWW0Fi7a for ; Sun, 13 Nov 2011 22:29:43 -0800 (PST) Received: from pechora2.lax.icann.org (pechora2.icann.org [IPv6:2620:0:2d0:201::1:72]) by ietfa.amsl.com (Postfix) with ESMTP id 1312D11E81F1 for ; Sun, 13 Nov 2011 22:29:37 -0800 (PST) Received: from mail-wy0-f169.google.com (mail-wy0-f169.google.com [74.125.82.169]) by pechora2.lax.icann.org (8.13.8/8.13.8) with ESMTP id pAE6TFbS000409 for ; Mon, 14 Nov 2011 06:29:36 GMT Received: by wyg24 with SMTP id 24so6008203wyg.28 for ; Sun, 13 Nov 2011 22:29:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=WHsTmTEPVJQSBOF2s/XLlcmqOhnAKevhgvSqSaI5bIo=; b=HVR+8VQ4HRSxt21gyVw6I3vL+jW7YDZC7TYHmNb5YmAdSuRpglAFYv1c6Yp9UIKwqS s70rSfE69dNWbqp+O5IjQkxoVZtKVBxye7OMK37fC/NMYjy1om5gdjwck8hDGBDmpiQT WruORIfF7I2geBjAi8Y/XJNIhwPwSXOK1q2rA= Received: by 10.216.52.16 with SMTP id d16mr3793562wec.88.1321252153080; Sun, 13 Nov 2011 22:29:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.184.147 with HTTP; Sun, 13 Nov 2011 22:28:32 -0800 (PST) In-Reply-To: References: From: Frank Ellermann Date: Mon, 14 Nov 2011 07:28:32 +0100 Message-ID: To: The IESG Content-Type: text/plain; charset=ISO-8859-1 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora2.lax.icann.org [192.0.33.72]); Mon, 14 Nov 2011 06:29:36 +0000 (UTC) Cc: IANA MIME types Subject: [ietf-types] Registration of media type application/opensearchdescription+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2011 06:29:44 -0000 Hi, the unregistered application/opensearchdescription+xml MIME type is commonly used in "search" link relations: The "popular" web browsers (IE7 or later, Firefox, and others) support OpenSearch descriptions for years. The specification is stable. Two changes in 2011 consist of an updated reference s/RFC 3066/RFC 5646/ and the addition of the MIME type registration template as required by RFC 4288 section 4.10: Please register this MIME type following the procedure in RFC 4288 section 5. To simplify the evaluation I've posted the registration request template also as I-D: Regards, Frank Return-Path: 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 0938C11E810F for ; Thu, 3 Nov 2011 05:39:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.784 X-Spam-Level: X-Spam-Status: No, score=-2.784 tagged_above=-999 required=5 tests=[AWL=1.465, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_DE=0.35] 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 bGJtaF9IWgg0 for ; Thu, 3 Nov 2011 05:39:20 -0700 (PDT) Received: from pechora8.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:74]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB6E11E810D for ; Thu, 3 Nov 2011 05:39:20 -0700 (PDT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by pechora8.dc.icann.org (8.13.8/8.13.8) with ESMTP id pA3Ccxm1017755 for ; Thu, 3 Nov 2011 08:39:19 -0400 Received: from [192.168.178.27] (p5DDECB0F.dip0.t-ipconnect.de [93.222.203.15]) by mrelayeu.kundenserver.de (node=mrbap3) with ESMTP (Nemesis) id 0M580s-1R2dZf0yvW-00zGVc; Thu, 03 Nov 2011 13:38:57 +0100 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=iso-8859-1 From: Paul Libbrecht In-Reply-To: Date: Thu, 3 Nov 2011 13:38:56 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <7F0BC7E1-877C-414F-8FB8-62C8D4A892F9@hoplahup.net> References: To: Frank Ellermann X-Mailer: Apple Mail (2.1084) X-Provags-ID: V02:K0:9l6zGdM+29TlXcUuPdffqFSZVv9xHFNSlSxKJz5WMu7 hUB0J40XfF+mLScpJ80MHbRvIBDv7DLjXPzdw+IqgtYe0TDTXx US+VjOj02dj1gCHh0EBHZvVFBegCCcBiGX0YY1di7qWEqKkakG d5tQ4EMQz5MAyq+My74Py5UqoNFm1hqiTFijWt8ZlPu8zF5F6A 5sBm2E9EfTykk3qN77SEcINzxUJb9q0VJPFEg8RgdE/C0xxxUZ EsvMaSlLC9E2BjTxQaGZw63JJT7jWJr54ue3fWFSsGJrzw/b3v eomC6fFxyJYXGbF/hcM+X06fiX1ifBnQAnIEx6Epi6ygRdECZL J7+s39juK7tm+SgwUf+kdFSWsMAXGga4N1rF6BMaegn4BZqMUf BQbxTtTwlGd6g== X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (pechora8.dc.icann.org [192.0.46.74]); Thu, 03 Nov 2011 08:39:19 -0400 (EDT) Cc: IANA Media types Subject: Re: [ietf-types] Registration of media type application/opensearchdescription+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 12:39:21 -0000 The same kind of reasoning was made for TeX and Maple media-types, it = was deemed not necessary. The result being... there's about twenty such out there. Hence I believe it is useful to make some choice beforehand for even the = clipboard names so that a reference is used in any case it appears = useful. I believe this is the right place to discuss clipboard names but surely = you could try to rewake Apple's four-letter directory. It looks like you do not see this related, I will not be able to = convince you more. paul Le 3 nov. 2011 =E0 13:09, Frank Ellermann a =E9crit : > On 3 November 2011 12:24, Paul Libbrecht wrote: >=20 >>> is there any problem with XML and clipboards? >> None, except showing its source to users is ugly. >=20 > Okay, that is apparently unrelated to the business > at hand, i.e., registering a media type for "OSDs". >=20 >>> If you have any "official" public source that >>> this is a well-known Mac id. >=20 >> about OSDs? I do not think so. >=20 > No problem, Apple or somebody knowing the details > can add it later if desired. The reference in RFC > 4288 is Apple KB 55381 vintage 1993, and I've read > the 2008 update (TA25699) about Mac OS9. >=20 >> I do not think there's a lot of danger involved. >=20 > RFC 4288 states that even using the word "none" is > already dangerous. AFAIK media type registrations > are not supposed to "invent" file extensions (or > file type codes for a historic OS) out of thin air. >=20 > -Frank Return-Path: 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 E5A161F0C81 for ; Thu, 3 Nov 2011 05:10:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.82 X-Spam-Level: X-Spam-Status: No, score=-102.82 tagged_above=-999 required=5 tests=[AWL=0.279, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_LOW=-1, 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 lJfYr6Y4dz6z for ; Thu, 3 Nov 2011 05:10:45 -0700 (PDT) Received: from pechora5.dc.icann.org (pechora5.icann.org [IPv6:2620:0:2830:201::1:71]) by ietfa.amsl.com (Postfix) with ESMTP id 7E53D1F0C70 for ; Thu, 3 Nov 2011 05:10:45 -0700 (PDT) Received: from mail-ww0-f47.google.com (mail-ww0-f47.google.com [74.125.82.47]) by pechora5.dc.icann.org (8.13.8/8.13.8) with ESMTP id pA3CANHi003759 for ; Thu, 3 Nov 2011 12:10:43 GMT Received: by wwf22 with SMTP id 22so1192070wwf.16 for ; Thu, 03 Nov 2011 05:10:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=0NkREd3beZixU7/S6pCaj4+fP51SW0vVUTKVFHJXxxk=; b=qLKPLLSA8esvqfZquJT/9oGWUVwbAIssAesbz9JvPbuN9TBbeh2PV1L8Spe7p2DSFy CVOK6AF58Uk82BFHKtW8stDSCtt0Df11x/8L2f+Gdj56RBrZjlbEp3tt9bMARSsCJ4Gy BohPtPAOGLyJfMX1rsTsacxdTDhDIZLeOQxAI= Received: by 10.227.60.131 with SMTP id p3mr13112881wbh.4.1320322223108; Thu, 03 Nov 2011 05:10:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.80.134 with HTTP; Thu, 3 Nov 2011 05:09:42 -0700 (PDT) In-Reply-To: References: From: Frank Ellermann Date: Thu, 3 Nov 2011 13:09:42 +0100 Message-ID: To: Paul Libbrecht Content-Type: text/plain; charset=ISO-8859-1 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora5.dc.icann.org [192.0.46.71]); Thu, 03 Nov 2011 12:10:43 +0000 (UTC) Cc: IANA MIME types Subject: Re: [ietf-types] Registration of media type application/opensearchdescription+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 12:10:57 -0000 On 3 November 2011 12:24, Paul Libbrecht wrote: >> is there any problem with XML and clipboards? > None, except showing its source to users is ugly. Okay, that is apparently unrelated to the business at hand, i.e., registering a media type for "OSDs". >> If you have any "official" public source that >> this is a well-known Mac id. > about OSDs? I do not think so. No problem, Apple or somebody knowing the details can add it later if desired. The reference in RFC 4288 is Apple KB 55381 vintage 1993, and I've read the 2008 update (TA25699) about Mac OS9. > I do not think there's a lot of danger involved. RFC 4288 states that even using the word "none" is already dangerous. AFAIK media type registrations are not supposed to "invent" file extensions (or file type codes for a historic OS) out of thin air. -Frank Return-Path: 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 CCCB911E80CF for ; Thu, 3 Nov 2011 04:24:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.319 X-Spam-Level: X-Spam-Status: No, score=-1.319 tagged_above=-999 required=5 tests=[AWL=0.929, BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001] 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 oL1dpiG-tPPr for ; Thu, 3 Nov 2011 04:24:59 -0700 (PDT) Received: from pechora1.lax.icann.org (unknown [IPv6:2620:0:2d0:201::1:71]) by ietfa.amsl.com (Postfix) with ESMTP id 4D52A11E8088 for ; Thu, 3 Nov 2011 04:24:59 -0700 (PDT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by pechora1.lax.icann.org (8.13.8/8.13.8) with ESMTP id pA3BOcNI017014 for ; Thu, 3 Nov 2011 04:24:58 -0700 Received: from [192.168.178.27] (p5DDECB0F.dip0.t-ipconnect.de [93.222.203.15]) by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis) id 0LgGuK-1QaiXo0tee-00o09X; Thu, 03 Nov 2011 12:24:36 +0100 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-52-562375675 From: Paul Libbrecht In-Reply-To: Date: Thu, 3 Nov 2011 12:24:35 +0100 Message-Id: References: To: Frank Ellermann X-Mailer: Apple Mail (2.1084) X-Provags-ID: V02:K0:YQpop3Hw5gXwSrMDvMHCI6yGpZJz3g8qKYbsss0Tw34 q7vhn5Ex/O5RrtYuTLkamc/A6xtA7Tm1GTQfsBXuYjjTvmpcIF xBnch0Dv59MCk41kD/M0gZRFwHHDZkg+RUAtnp4zHWWxif6iwV OFaNkrQ2/9UKcwo2FD1RpO7vUn5SBW0fc7XehU5vDjgfGh9RLi 0c0u+bLHB2xqNMwc8kwUvVotMHLdnJAnFGMvyNi2l5UFC6s4P9 ++QLt7jDRw+npDXX3dqX+VJbQiubLPXIV9s4NdC5R6jrGy16jG qU0+KLfQohpXiiJ+dZ3gJDsXji/0yqUtxTjDp9eWfId24Y5r5i KGOZHZ/4G60gKo7ZEqP/vjBoTqrsQxRgX/h2GEm2E60h54H+di /DAIlPbHreDhA== X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora1.lax.icann.org [192.0.33.71]); Thu, 03 Nov 2011 11:24:58 +0000 (UTC) Cc: IANA MIME types Subject: Re: [ietf-types] Registration of media type application/opensearchdescription+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 11:24:59 -0000 --Apple-Mail-52-562375675 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Le 25 oct. 2011 =E0 17:10, Frank Ellermann a =E9crit : >> My usual suggestion is: what about clipboards? >=20 > Dunno, is there any problem with XML and clipboards? None, except showing its source to users is ugly. >> OpenSearch Description Documents sound to be a natural >> candidate to be exchanged in clipboards (be copied-and >> -pasted, be drag-and-dropped, ...). Do I mistake? >=20 > All I ever wish to do with OSDs is (1) edit some details, > or wrt the security considerations inspect their source, > (2) adopt an OSD when the auto-detect link rel=3D"search" > worked as it should, (3) click on an AddSearchProvider() > EcmaScript link for cases where link rel=3D"search" is no > option. Where do clipboards enter this picture for you, Does it make sense to exchange them between two browsers? The clipboard is a prime place for this. > and is it relevant for the IANA media type registration? This is the right place I believe. >=20 >> - Macintosh Uniform Type Identifier: >> org.opensearch.description conforms to public.xml >=20 > Sadly I've no idea how Mac Uniform type identifiers work, > and the info published in RFC 4288 convinced me that it's > not something to worry about. If you have any "official" > public source that this is a well-known Mac id. about OSDs? I do not think so. About UTIs... start at wikipedia. > I add it, otherwise I prefer to stick to what I could defend in an = IETF Last Call. I do not think there's a lot of danger involved. >> - Similarly http://www.opensearch.org/ is rather a >> volatile change controller. >=20 > This actually is the "change controller" for some years, > but IANAL and certainly not speaking for A9. But that is owned by A9... paul --Apple-Mail-52-562375675 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
My usual suggestion is: what about = clipboards?

Dunno, is there any problem with XML and = clipboards?

None, = except showing its source to users is ugly.

OpenSearch Description Documents sound = to be a natural
candidate to = be exchanged in clipboards (be copied-and
-pasted, be drag-and-dropped, ...). Do I = mistake?

All I ever wish to do with OSDs is (1) edit = some details,
or wrt the security considerations inspect their = source,
(2) adopt an OSD when the auto-detect link = rel=3D"search"
worked as it should, (3) click on an = AddSearchProvider()
EcmaScript link for cases where link rel=3D"search"= is no
option.  Where do clipboards enter this picture for = you,

Does it make sense = to exchange them between two browsers?
The clipboard is a = prime place for this.

and is = it relevant for the IANA media type = registration?

This is = the right place I believe.

- Macintosh Uniform Type = Identifier:
org.opensearch.description conforms to = public.xml

Sadly I've no idea how Mac Uniform type = identifiers work,
and the info published in RFC 4288 convinced me = that it's
not something to worry about.  If you have any = "official"
public source that this is a well-known Mac id. =

about OSDs? I do not think = so.
About UTIs... start at wikipedia.

I add = it, otherwise I prefer to stick to what I could defend in = an IETF Last = Call.

I do not think = there's a lot of danger involved.

- Similarly http://www.opensearch.org/ is= rather a
volatile change = controller.

This actually is the "change controller" = for some years,
but IANAL and certainly not speaking for = A9.

But that is owned by = A9...

paul

= --Apple-Mail-52-562375675-- Return-Path: 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 4259E1F0CA6 for ; Thu, 3 Nov 2011 04:10:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.634 X-Spam-Level: X-Spam-Status: No, score=-101.634 tagged_above=-999 required=5 tests=[AWL=-0.949, BAYES_40=-0.185, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_LOW=-1, 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 WXJDtb-JPdaC for ; Thu, 3 Nov 2011 04:10:40 -0700 (PDT) Received: from pechora3.lax.icann.org (unknown [IPv6:2620:0:2d0:201::1:73]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA501F0CA5 for ; Thu, 3 Nov 2011 04:10:40 -0700 (PDT) Received: from mail-ww0-f47.google.com (mail-ww0-f47.google.com [74.125.82.47]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id pA3BAIBg027880 for ; Thu, 3 Nov 2011 11:10:39 GMT Received: by wwf22 with SMTP id 22so1137312wwf.16 for ; Thu, 03 Nov 2011 04:10:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=MOEvglC59SXYqIRn2CXu/tWxeAhjVsiWAv1vI4oUGok=; b=UoCYm3TltBu36yGVesnOwrfvDyJ/TrZmuIWDwQ7UofyAKq81pCeRSLV9qx9Q2uvrKx hHeST9af6KlqSpUesfWRoT+YfyErLydLpaLEWBrPXB2iERepwQrcGkDIImaNk4CITTuv ciSWi75NgMsC0sodfF8lEdd5yF0DRGExw2KVk= Received: by 10.216.221.157 with SMTP id r29mr7731133wep.66.1320318618116; Thu, 03 Nov 2011 04:10:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.80.134 with HTTP; Thu, 3 Nov 2011 04:09:37 -0700 (PDT) In-Reply-To: References: From: Frank Ellermann Date: Thu, 3 Nov 2011 12:09:37 +0100 Message-ID: To: Paul Libbrecht Content-Type: text/plain; charset=ISO-8859-1 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [192.0.33.73]); Thu, 03 Nov 2011 11:10:39 +0000 (UTC) Cc: IANA MIME types Subject: Re: [ietf-types] Registration of media type application/opensearchdescription+xml X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2011 11:10:41 -0000 On 25 October 2011 17:10 wrote: > I've tried to submit an updated "not for RFC" > Internet Draft Meanwhile that worked to some degree, I'll fix the misleading "not for RFC" boilerplate later: -Frank