WebRTC Video Processing and Codec Requirements
draft-ietf-rtcweb-video-06
Yes
No Objection
Note: This ballot was opened for revision 05 and is now closed.
Alvaro Retana No Objection
(Alissa Cooper; former steering group member) Yes
(Ben Campbell; former steering group member) Yes
Thanks for this, it is well written and easy to read. (It easily hides all the gnashing-of-teeth that went into it.) I've got just a couple of minor comments: -- section 3: "the video scan pattern for video codecs is Y’CbCr 4:2:0." At the risk of stepping way outside my expertise, I've generally heard that referred to as a (sub)sampling ratio. Is this talking about something different? -- 6.2, "max-mbps,..." Odd vertical spacing.
(Spencer Dawkins; former steering group member) Yes
Thank you for producing this document. I'm only mildly familiar with this level of detail, and the document was clear, with pointers when I needed them. I'm honored to ballot Yes. I did have one question. In this text: Implementations MAY send and act upon "User data registered by Rec. ITU-T T.35" and "User data unregistered" messages. Even if they do not act on them, implementations MUST be prepared to receive such messages without any ill effects. Is that a usual thing to say? Perhaps it is, but I thought that might be understood.
(Terry Manderson; former steering group member) Yes
(Alia Atlas; former steering group member) No Objection
(Barry Leiba; former steering group member) No Objection
I do wonder that the Abstract and Introduction are both short, and, yet, give such different descriptions of the document as to make it look like two different documents. Given how short they are, perhaps it really is best to make them the same, no? Abstract: This specification provides the requirements and considerations for WebRTC applications to send and receive video across a network. It specifies the video processing that is required, as well as video codecs and their parameters. Introduction: This specification defines how the video is used and discusses special considerations for processing the video. It also covers the video- related algorithms WebRTC devices need to support.
(Benoît Claise; former steering group member) No Objection
(Brian Haberman; former steering group member) No Objection
(Deborah Brungard; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Joel Jaeggli; former steering group member) No Objection
(Kathleen Moriarty; former steering group member) No Objection
(Martin Stiemerling; former steering group member) No Objection