RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG-2 Transport Stream (TS) Program Specific Information (PSI) Independent Decodability Statistics Metrics Reporting
RFC 6990
Yes
No Objection
Note: This ballot was opened for revision 11 and is now closed.
(Gonzalo Camarillo; former steering group member) Yes
(Richard Barnes; former steering group member) Yes
(Spencer Dawkins; former steering group member) Yes
Very clear and crisp. Nice work.
(Adrian Farrel; former steering group member) No Objection
(Barry Leiba; former steering group member) No Objection
(Benoît Claise; former steering group member) No Objection
(Brian Haberman; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Joel Jaeggli; former steering group member) No Objection
(Martin Stiemerling; former steering group member) No Objection
(Pete Resnick; former steering group member) No Objection
(Sean Turner; former steering group member) No Objection
(Stephen Farrell; former steering group member) No Objection
(Stewart Bryant; former steering group member) No Objection
I notice that the security section says: "This proposed RTCP XR report block introduces no new security considerations beyond those described in RFC 3611." Doesn't that depend on what the reported error counters are used for? I can imagine that there might some relationship between reported errors and contractual SLAs and hence an attack on these error fields may have implications for the network operator.
(Ted Lemon; former steering group member) No Objection