Re: [rtcweb] Call for Consensus Regarding Selecting Recommended Audio Codecs

[Cameron Byrne <[e-mail]>]

Sent from ipv6-only Android
On Jan 17, 2013 6:54 AM, <[e-mail]> wrote:
>
> Please consider that the AMR-WB codec is the mandatory codec for HD Voice
VoLTE terminals and that first VoLTE deployments in the world from Korean
Telcos (SKT and LGU) are HD Voice with AMR-WB (And with respect to your
past/future categories, I think we can say that VoLTE is more on future
side that "past")
>
> But AMR-WB is also already deployed in the 2G and 3G networks of more
than 50 Mobile Network Operators
>
> So I agree that interop. with legacy are two objectives distinct and
fortunately, supporting AMR-WB is sufficient to reach both in the same time
!
>
>

Please accept that the ipr terms of amr-wb pose a huge barrier for the
ietf. I really believe you are wasting your time. Please focus your efforts
on ensuring your offer/answer supports the codec you want you want in your
implementation.

Your efforts would be better spent getting the 3gpp to accept Opus as their
default,  it is royalty free and mti for all web browsers.

Br,

CB

> De : Bernard Aboba [mailto:[e-mail]]
> Envoyé : lundi 14 janvier 2013 15:35
> À : PROUST Stephane OLNC/OLPS
> Cc : [e-mail]
> Objet : RE: [rtcweb] Call for Consensus Regarding Selecting Recommended
Audio Codecs
>
> Stephane said:
>
> "In addition to G.711, these 3 codecs cover almost all legacy devices
dedicated to voice services. They are consequently needed and sufficient to
be supported by WebRTC to make it an attractive and future proof technology"
>
> [BA] The use of the terms "legacy" and "future proof" here is puzzling.
"Future proof" would seem to imply the ability to adapt to future
developments, whereas "legacy" relates to compatibility with what has gone
before.   Unless the "past" is the same as the "future" (which implies no
progress at all), those two objectives are distinct (and possibly
conflicting).
>
>
>
>
>
_________________________________________________________________________________________________________________________
>
> 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.
>
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb