Re: [rtcweb] Conclusion statement for Recommended Audio Codecs call

Hello,

> We chairs was considering inclusion in draft-ietf-webrtc-audio, but we didn't have any strong opinions on this
> I thus decided that we will start out with an independent document

If the Chairs have still no strong opinion about this, I would request to leave this somewhat editorial issue still open.

It makes more sense that all the relevant information for audio and especially the relevant codecs with their different status be clearly listed in the same "webrtc audio" specification. Especially because we want to address the same interoperability issue.
This will be more consistent and readable.

Then, if more informative text on additional codecs is needed, a separate document can be considered to avoid overloading this webrtc audio document with purely informative text.

Stéphane	

-----Message d'origine-----
De : rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] De la part de Magnus Westerlund
Envoyé : lundi 28 janvier 2013 09:12
À : Romascanu, Dan (Dan)
Cc : Cullen Jennings (fluffy); rtcweb@ietf.org
Objet : Re: [rtcweb] Conclusion statement for Recommended Audio Codecs call

Hi,

We chairs was considering inclusion in draft-ietf-webrtc-audio, but we didn't have any strong opinions on this. Based on that several WG participants thinks this should be an independent document, I thus decided that we will start out with an independent document. If the WG feels differently later we can always fold the text into the audio codec and processing requirements document.

I would recommend that the individuals interested in contributing a codec writes an independent submission with focus on the codec considerations around the codec(s) they are interested in. Then we can merge this into a common WG document.

Cheers

Magnus

On 2013-01-27 10:14, Romascanu, Dan (Dan) wrote:
> Hi WG chairs,
> 
> Clarification question: 
> 
>> In lieu of additional normative text, we believe the WG discussion 
>> supports the inclusion of a new section on "Additional Relevant Codecs".
> 
> Inclusion where? 
> 
> Thanks and Regards,
> 
> Dan
> 
> 
> 
> 
>> -----Original Message-----
>> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On 
>> Behalf Of Cullen Jennings (fluffy)
>> Sent: Thursday, January 24, 2013 6:47 PM
>> To: rtcweb@ietf.org
>> Subject: Re: [rtcweb] Conclusion statement for Recommended Audio 
>> Codecs call
>>
>>
>> We have been running a call for consensus regarding Selecting 
>> Recommended Audio Codecs.
>>
>> At this point the chairs are calling this as "no WG consensus".
>>
>> We can however note a strong interest in a non-normative listing of 
>> potentially important codecs including a description why they should 
>> be considered to be supported in WebRTC implementations.
>>
>> In lieu of additional normative text, we believe the WG discussion 
>> supports the inclusion of a new section on "Additional Relevant Codecs".
>> That can contain a list of codecs which are relevant in specific 
>> contexts, along with a short description of the context for each.
>> Specifically there seems to be interest in understanding the 
>> advantages and costs of G.722, AMR, and AMR-WB. We hope that text 
>> would broaden understanding of the WebRTC use case contexts.
>>
>> The WG chairs
>> Magnus, Ted and Cullen
>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> 

-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.