Subject: Re: [rtcweb] AD evaluation: draft-ietf-rtcweb-audio-codecs-for-interop-04

From: <[email-masked]>
Date: Wed, 10 Feb 2016 08:18:44 +0000

Thanks Alissa for you review
I've just submitted a 05 version capturing all your comments (no other changes except the one you suggest)

Kind regards

Stéphane 

-----Message d'origine-----
De : rtcweb [mailto:[email-masked]] De la part de Alissa Cooper
Envoyé : jeudi 28 janvier 2016 00:55
À : [email-masked]
Objet : [rtcweb] AD evaluation: draft-ietf-rtcweb-audio-codecs-for-interop-04

I have reviewed this document in preparation for IETF LC. I have a few substantive comments that need to be resolved for IETF LC. I’ve also included some nits below that should be resolved together with LC comments.

Substantive comments:

(1) Typically when a long author list gets shifted to the Acknowledgments section the remaining name at the top get marked as an editor. That seems appropriate in this case.

(2) The document uses the term “WebRTC client” in a few places. I would suggest referencing the terminology defined in draft-ietf-rtcweb-overview regarding endpoints/devices/browsers and consistently using the terminology defined there (or, if not, explain why not).

(3) The claims throughout Section 4 about the number of terminals affected sound like marketing. Wanted to check if the WG is confident that these claims need to be in the document.

(4) Section 4.4 seems superfluous and should be deleted.

Nits:

= Section 1 =

s/to include in the offer other suitable audio codecs/to include in the offer other suitable audio codecs beyond those that are mandatory to implement/

= Section 5 =

s/to also report more specifically/to also refer more specifically/

_______________________________________________
rtcweb mailing list
[email-masked]
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,
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, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.