Re: [ietf-types] Review of
Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 05 April 2012 12:04 UTC
Return-Path: <HKaplan@acmepacket.com>
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 6831321F8822 for <ietf-types@ietfa.amsl.com>; Thu, 5 Apr 2012 05:04:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level:
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=-0.450, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, MIME_8BIT_HEADER=0.3]
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 IddLHLL-U0Vq for <ietf-types@ietfa.amsl.com>; Thu, 5 Apr 2012 05:04:04 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 21B3521F87AB for <ietf-types@ietf.org>; Thu, 5 Apr 2012 05:04:03 -0700 (PDT)
Received: from MAIL1.acmepacket.com (10.0.0.21) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 5 Apr 2012 08:03:59 -0400
Received: from MAIL2.acmepacket.com ([169.254.2.74]) by Mail1.acmepacket.com ([169.254.1.130]) with mapi id 14.02.0283.003; Thu, 5 Apr 2012 08:03:57 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, "ietf-types@ietf.org" <ietf-types@ietf.org>
Thread-Topic: [ietf-types] Review of
Thread-Index: AQHNEk2AXbRsLGUU40Co+nnEkMXldpaMBoSAgABgSQA=
Date: Thu, 05 Apr 2012 12:03:57 +0000
Message-ID: <6F178BA1-04CD-4629-A0C9-C3B829213CC4@acmepacket.com>
References: <4F7C21F0.6020908@ericsson.com> <4F7D3967.20809@it.aoyama.ac.jp>
In-Reply-To: <4F7D3967.20809@it.aoyama.ac.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.0.0.30]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E7396DACE0B3D341AD026B549AF28A65@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
X-Mailman-Approved-At: Thu, 05 Apr 2012 05:50:00 -0700
Cc: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>, Flemming Andreasen <fandreas@cisco.com>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [ietf-types] Review of
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Apr 2012 12:04:05 -0000
13.2.1 audio/encaprtp
To: ietf-types@iana.org
Subject: Registration of media type audio/encaprtp
Type name: audio
Subtype name: encaprtp
Required parameters:
rate:RTP timestamp clock rate, which is equal to the
sampling rate. The typical rate is 8000; other rates
may be specified.
Optional parameters: none
Encoding considerations: This media type is framed
binary data.
Security considerations: See Section 12 of this document.
Interoperability considerations: none
Published specification: This MIME type is described fully
within this document.
Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP
Service.
Additional information: none
Person & email address to contact for further information:
Kaynam Hedayat
EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON
Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not
defined at this time.
Author:
Kaynam Hedayat.
Change controller: IETF Audio/Video Transport working
group delegated from the IESG.
13.2.2 video/encaprtp
To: ietf-types@iana.org
Subject: Registration of media type video/encaprtp
Type name: video
Subtype name: encaprtp
Required parameters:
rate:RTP timestamp clock rate, which is equal to the
sampling rate. The typical rate is 8000; other rates
may be specified.
Optional parameters: none
Encoding considerations: This media type is framed
binary data.
Security considerations: See Section 12 of this document.
Interoperability considerations: none
Published specification: This MIME type is described fully
within this document.
Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP
Service.
Additional information: none
Person & email address to contact for further information:
Kaynam Hedayat
EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON
Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not
defined at this time.
Author:
Kaynam Hedayat.
Change controller: IETF Audio/Video Transport working
group delegated from the IESG.
13.2.3 text/encaprtp
To: ietf-types@iana.org
Subject: Registration of media type text/encaprtp
Type name: text
Subtype name: encaprtp
Required parameters:
rate:RTP timestamp clock rate, which is equal to the
sampling rate. The typical rate is 8000; other rates
may be specified.
Optional parameters: none
Encoding considerations: This media type is framed
binary data.
Security considerations: See Section 12 of this document.
Interoperability considerations: none
Published specification: This MIME type is described fully
within this document.
Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP
Service.
Additional information: none
Person & email address to contact for further information:
Kaynam Hedayat
EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON
Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not
defined at this time.
Author:
Kaynam Hedayat.
Change controller: IETF Audio/Video Transport working
group delegated from the IESG.
13.2.4 application/encaprtp
To: ietf-types@iana.org
Subject: Registration of media type
application/encaprtp
Type name: application
Subtype name: encaprtp
Required parameters:
rate:RTP timestamp clock rate, which is equal to the
sampling rate. The typical rate is 8000; other rates
may be specified.
Optional parameters: none
Encoding considerations: This media type is framed
binary data.
Security considerations: See Section 12 of this document.
Interoperability considerations: none
Published specification: This MIME type is described fully
within this document.
Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP
Service.
Additional information: none
Person & email address to contact for further information:
Kaynam Hedayat
EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON
Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not
defined at this time.
Author:
Kaynam Hedayat.
Change controller: IETF Audio/Video Transport working
group delegated from the IESG.
13.2.5 audio/rtploopback
To: ietf-types@iana.org
Subject: Registration of media type audio/rtploopback
Type name: audio
Subtype name: rtploopback
Required parameters:
rate:RTP timestamp clock rate, which is equal to the
sampling rate. The typical rate is 8000; other rates
may be specified.
Optional parameters: none
Encoding considerations: This media type is framed
binary data.
Security considerations: See Section 12 of this document.
Interoperability considerations: none
Published specification: This MIME type is described fully
within this document.
Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP
Service.
Additional information: none
Person & email address to contact for further information:
Kaynam Hedayat
EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON
Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not
defined at this time.
Author:
Kaynam Hedayat.
Change controller: IETF Audio/Video Transport working
group delegated from the IESG.
13.2.6 video/rtploopback
To: ietf-types@iana.org
Subject: Registration of media type video/rtploopback
Type name: video
Subtype name: rtploopback
Required parameters:
rate:RTP timestamp clock rate, which is equal to the
sampling rate. The typical rate is 8000; other rates
may be specified.
Optional parameters: none
Encoding considerations: This media type is framed
binary data.
Security considerations: See Section 12 of this document.
Interoperability considerations: none
Published specification: This MIME type is described fully
within this document.
Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP
Service.
Additional information: none
Person & email address to contact for further information:
Kaynam Hedayat
EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON
Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not
defined at this time.
Author:
Kaynam Hedayat.
Change controller: IETF Audio/Video Transport working
group delegated from the IESG.
13.2.7 text/rtploopback
To: ietf-types@iana.org
Subject: Registration of media type text/rtploopback
Type name: text
Subtype name: rtploopback
Required parameters:
rate:RTP timestamp clock rate, which is equal to the
sampling rate. The typical rate is 8000; other rates
may be specified.
Optional parameters: none
Encoding considerations: This media type is framed
binary data.
Security considerations: See Section 12 of this document.
Interoperability considerations: none
Published specification: This MIME type is described fully
within this document.
Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP
Service.
Additional information: none
Person & email address to contact for further information:
Kaynam Hedayat
EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON
Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not
defined at this time.
Author:
Kaynam Hedayat.
Change controller: IETF Audio/Video Transport working
group delegated from the IESG.
13.2.8 application/rtploopback
To: ietf-types@iana.org
Subject: Registration of media type
application/rtploopback
Type name: application
Subtype name: rtploopback
Required parameters:
rate:RTP timestamp clock rate, which is equal to the
sampling rate. The typical rate is 8000; other rates
may be specified.
Optional parameters: none
Encoding considerations: This media type is framed
binary data.
Security considerations: See Section 12 of this document.
Interoperability considerations: none
Published specification: This MIME type is described fully
within this document.
Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP
Service.
Additional information: none
Person & email address to contact for further information:
Kaynam Hedayat
EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON
Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not
defined at this time.
Author:
Kaynam Hedayat.
Change controller: IETF Audio/Video Transport working
group delegated from the IESG.
On Apr 5, 2012, at 2:19 AM, Martin J. Dürst wrote:
> Hello Miguel,
>
> Please post the registration templates here. This gives you a *much* higher chance of getting good comments.
>
> Regards, Martin.
>
> On 2012/04/04 19:26, Miguel A. Garcia wrote:
>> Hi,
>>
>> The MMUSIC working group is running the WGLC of
>> draft-ietf-mmusic-media-loopback-18.txt, available at:
>>
>> http://datatracker.ietf.org/doc/draft-ietf-mmusic-media-loopback/
>>
>> The draft registers 8 new media types. Please refer to Section 13.2 in
>> the draft:
>>
>> http://tools.ietf.org/html/draft-ietf-mmusic-media-loopback-18#section-13.2
>>
>> We will appreciate if you can review the registration and provide us
>> with comments.
>>
>> Thanks,
>>
>> Miguel
- Re: [ietf-types] Review of draft-ietf-mmusic-medi… Gonzalo Camarillo
- [ietf-types] Review of Miguel A. Garcia
- Re: [ietf-types] Review of Martin J. Dürst
- Re: [ietf-types] Review of Hadriel Kaplan
- Re: [ietf-types] Review of Bjoern Hoehrmann
- Re: [ietf-types] Review of Miguel Garcia A
- Re: [ietf-types] Review of Hadriel Kaplan
- Re: [ietf-types] Review of Magnus Westerlund