headers
Gonzalo Camarillo | 4 Apr 2012 14:01
Picon
Favicon

Re: Review of draft-ietf-mmusic-media-loopback-18.txt

Fixing the subject of the email.

Gonzalo

On 04/04/2012 1:26 PM, Miguel Garcia A 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
Permalink | Reply | 0 comments |
headers
Miguel A. Garcia | 4 Apr 2012 12:26
Picon
Favicon

Review of

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
--

-- 
Miguel A. Garcia
+34-91-339-3608
Ericsson Spain
Permalink | Reply | 7 comments |
headers
Martin J. Dürst | 5 Apr 2012 08:19
Picon
Gravatar

Re: Review of

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
Permalink | Reply | 5 comments |
headers
Hadriel Kaplan | 5 Apr 2012 14:03
Favicon

Re: Review of


 13.2.1    audio/encaprtp 

           To: ietf-types <at> 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
(Continue reading)

Permalink | Reply | 4 comments |
headers
Bjoern Hoehrmann | 6 Apr 2012 01:30
Picon

Re: Review of

* Hadriel Kaplan wrote:
> 13.2.1    audio/encaprtp 
>           Encoding considerations: This media type is framed  
>                binary data. 

This should just say "framed".

>           Published specification: This MIME type is described fully 
>                within this document. 

It might be better to use just "this document" or "RFC XXXX". Note the
inconsistency in nomenclature, above you have "media type" and here you
have "MIME type", at least that should be fixed.

>           Person & email address to contact for further information: 
>     
>                Kaynam Hedayat 
>                EMail: kaynam.hedayat <at> exfo.com 

The typical rendering is `Name <example <at> example.example>`.

>           Intended usage: COMMON 

My impression is that RTP-only types typically use LIMITED USE, but I
might be mistaken about that.
--

-- 
Björn Höhrmann · mailto:bjoern <at> 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/
Permalink | Reply | 3 comments |
headers
Miguel Garcia A | 6 Apr 2012 13:38
Picon
Favicon

Re: Review of

Thank you Björn for your review. Please Hadriel, consider Björn 's comments for the next version of the document.

/Miguel
________________________________________
From: Bjoern Hoehrmann [derhoermi <at> gmx.net]
Sent: Friday, April 06, 2012 1:30 AM
To: Hadriel Kaplan
Cc: Martin J. Dürst; ietf-types <at> ietf.org; Miguel Garcia A; Flemming Andreasen; Gonzalo Camarillo;
Robert Sparks
Subject: Re: [ietf-types] Review of

* Hadriel Kaplan wrote:
> 13.2.1    audio/encaprtp
>           Encoding considerations: This media type is framed
>                binary data.

This should just say "framed".

>           Published specification: This MIME type is described fully
>                within this document.

It might be better to use just "this document" or "RFC XXXX". Note the
inconsistency in nomenclature, above you have "media type" and here you
have "MIME type", at least that should be fixed.

>           Person & email address to contact for further information:
>
>                Kaynam Hedayat
>                EMail: kaynam.hedayat <at> exfo.com
(Continue reading)

Permalink | Reply | 1 comment |
headers
Hadriel Kaplan | 6 Apr 2012 14:16
Favicon

Re: Review of


Yup, will do!
Thanks,

-hadriel

On Apr 6, 2012, at 7:38 AM, Miguel Garcia A wrote:

> Thank you Björn for your review. Please Hadriel, consider Björn 's comments for the next version of the document.
> 
> /Miguel
> ________________________________________
> From: Bjoern Hoehrmann [derhoermi <at> gmx.net]
> Sent: Friday, April 06, 2012 1:30 AM
> To: Hadriel Kaplan
> Cc: Martin J. Dürst; ietf-types <at> ietf.org; Miguel Garcia A; Flemming Andreasen; Gonzalo Camarillo;
Robert Sparks
> Subject: Re: [ietf-types] Review of
> 
> * Hadriel Kaplan wrote:
>> 13.2.1    audio/encaprtp
>>          Encoding considerations: This media type is framed
>>               binary data.
> 
> This should just say "framed".
> 
>>          Published specification: This MIME type is described fully
>>               within this document.
> 
> It might be better to use just "this document" or "RFC XXXX". Note the
(Continue reading)

Permalink | Reply | 0 comments |
headers
Magnus Westerlund | 10 Apr 2012 10:07
Picon
Favicon

Re: Review of

On 2012-04-06 01:30, Bjoern Hoehrmann wrote:
> * Hadriel Kaplan wrote:
> 
>>           Intended usage: COMMON 
> 
> My impression is that RTP-only types typically use LIMITED USE, but I
> might be mistaken about that.

I think you are wrong Bjoern, most have been using Common:

I looked at the five RFC published by the Payload WG and the following
RFCs use common and are RTP payload formats:

RFC6190
RFC6262
RFC6295
RFC6416
RFC6469

All of these used common.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
(Continue reading)

Permalink | Reply | 0 comments |
headers
Eric Prud'hommeaux | 18 Apr 2012 17:36
Picon
Favicon

Request for review of N-Triples (an RDF serialization) media type: application/n-triples

Hi all, we're about to publish a last call of an RDF representation called N-Triples.
<http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#sec-mediaReg-n-triples>
(Yes, the contact and the subtype in this email are not in synch with those in the editor's draft -- the email
documents plan A and will be reflected to the editor's draft before publication.)
One question is whether to use "application/ntriples" or "application/n-triples", with a preference
for the latter.
It'd be great to get feedback on the subtype and registration before last call publication.

Contact:
    World Wide Wed Consortium <web-human <at> w3.org>
See also:
    How to Register a Media Type for a W3C Specification
    Internet Media Type registration, consistency of use
    TAG Finding 3 June 2002 (Revised 4 September 2002)

The Internet Media Type / MIME Type for N-Triples is "application/n-triples".

It is recommended that N-Triples files have the extension ".nt" (all lowercase) on all platforms.

It is recommended that N-Triples files stored on Macintosh HFS file systems be given a file type of "TEXT".

This information that follows will be submitted to the IESG for review, approval, and registration with IANA.

Type name:
    application
Subtype name:
    n-triples
Required parameters:
    None
Optional parameters:
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jesús Hernández Gormaz | 23 Apr 2012 00:35
Picon
Gravatar

Request of new MIME type for Python.

Hello I am Jesús Hernández Gormaz, I would like to propose
 that the MIME type text / x-python pass to register with the
 IANA and thus switch to a text / python completelystandard
 and accepted. Also, as I guess will know, Python handles
 files .pyc besides the .py and .pyc are your bytecode, so I
 propose a typoapplication / x-python-bytecode to begin to
 give these files its own MIME type , and encourage as in the
 previous case to formalize an application /bytecode-python
 as it seems important formalziar Python MIME types.

Greetings.

--
JHG.

_______________________________________________
ietf-types mailing list
ietf-types <at> ietf.org
https://www.ietf.org/mailman/listinfo/ietf-types
Permalink | Reply | 1 comment |

Gmane