Upgrade to Pro — share decks privately, control downloads, hide ads and more …

RTP Control Protocol (RTCP) Extended Reports (X...

RTP Control Protocol (RTCP) Extended Reports (XR) for Run Length Encoding (RLE) of Discarded Packets

Presented by me at XRBLOCK, IETF87, Berlin

Varun Singh

July 29, 2013
Tweet

More Decks by Varun Singh

Other Decks in Technology

Transcript

  1. RTP Control Protocol (RTCP) Extended Reports (XR) for Run Length

    Encoding (RLE) of Discarded Packets draft-ietf-xrblock-rtcp-xr-discard-rle-metrics 29 July 2013, IETF 87, Berlin Varun Singh, Joerg Ott, Igor Curcio 7/31/13 1
  2. Re-cap •  Discards packets arriving early or late •  Discard

    due to duplication not reported •  Two Report blocks – Run-length encoded •  begin_seq to end_seq! – Bytes discarded •  32 bits unsigned •  Counts payload bytes of discarded packets 7/31/13 2
  3. IESG Review •  Stephen Farrell (and SecDir Review) I don't

    agree with the assertion in section 7 - sometimes more precision is in fact enough to cause a security issue, so the statement is just wrong. Was security really considered? TEXT in -06 version: The security considerations of [RFC3550], [RFC3611], and [RFC4585] apply. Since this document offers only a more precise reporting for an already existing metric, no further security implications are foreseen.! •  RFC3611 defines LOSS RLE 7/31/13 3
  4. Section 7 (Proposal) The Discard RLE block provides per-packet statistics

    so the risk to! confidentiality documented in Section 7, paragraph 3 of [RFC3611]! applies. In some situations, returning very detailed error! information (e.g., over-range measurement or measurement unavailable)! using this report block can provide an attacker with insight into the! security processing. Where this is a concern, the implementation! should apply encryption (authentication?) to this report block. This can be! achieved by using the AVPF profile together with the Secure RTP! profile as defined in [RFC3711]; as a prerequisite, an appropriate! combination of those two profiles (an "SAVPF") is being specified! [RFC5124].! ! Additionally, The security considerations of [RFC3550], [RFC3611],! and [RFC4585] apply.! ! •  Packets are discarded based on timestamp and de-jitter buffer. •  Is any one aware of side channel attacks that may affect XRBLOCKs? 7/31/13 4
  5. PM Directorate Review •  Thank you Alan Clark, –  editorial

    changes + 1 open issue •  OPEN ISSUE: discarded bytes block 1.  Keep with RLE block, update title and add RFC6390 template RTP Control Protocol (RTCP) Extended Reports (XR) for Bytes Discarded and Run Length Encoding (RLE) of Discarded Packets! 2.  Move Discarded bytes to Packet discard draft •  Packet discard draft is in RFC-EDITOR Queue 7/31/13 5
  6. Next Steps •  OPTION 1: impacts only the RLE draft

    – update title and add RFC6390 templates. 7/31/13 6