Skip to main content

RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG-2 Transport Stream (TS) Program Specific Information (PSI) Independent Decodability Statistics Metrics Reporting
draft-ietf-xrblock-rtcp-xr-decodability-12

Yes

(Gonzalo Camarillo)
(Richard Barnes)

No Objection

(Adrian Farrel)
(Barry Leiba)
(Benoît Claise)
(Brian Haberman)
(Jari Arkko)
(Joel Jaeggli)
(Martin Stiemerling)
(Pete Resnick)
(Sean Turner)
(Stephen Farrell)
(Ted Lemon)

Note: This ballot was opened for revision 11 and is now closed.

Gonzalo Camarillo Former IESG member
Yes
Yes (for -11) Unknown

                            
Richard Barnes Former IESG member
Yes
Yes (for -11) Unknown

                            
Spencer Dawkins Former IESG member
Yes
Yes (2013-05-28 for -11) Unknown
Very clear and crisp. Nice work.
Adrian Farrel Former IESG member
No Objection
No Objection (for -11) Unknown

                            
Barry Leiba Former IESG member
No Objection
No Objection (for -11) Unknown

                            
Benoît Claise Former IESG member
No Objection
No Objection (for -11) Unknown

                            
Brian Haberman Former IESG member
No Objection
No Objection (for -11) Unknown

                            
Jari Arkko Former IESG member
No Objection
No Objection (for -11) Unknown

                            
Joel Jaeggli Former IESG member
No Objection
No Objection (for -11) Unknown

                            
Martin Stiemerling Former IESG member
No Objection
No Objection (for -11) Unknown

                            
Pete Resnick Former IESG member
No Objection
No Objection (for -11) Unknown

                            
Sean Turner Former IESG member
No Objection
No Objection (for -11) Unknown

                            
Stephen Farrell Former IESG member
No Objection
No Objection (for -11) Unknown

                            
Stewart Bryant Former IESG member
No Objection
No Objection (2013-05-29 for -11) Unknown
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 IESG member
No Objection
No Objection (for -11) Unknown