Last Call Review of draft-ietf-xrblock-rtcp-xr-jb-11
review-ietf-xrblock-rtcp-xr-jb-11-secdir-lc-emery-2013-06-27-00

Request Review of draft-ietf-xrblock-rtcp-xr-jb
Requested revision No specific revision (document currently at 14)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2013-06-25
Requested 2013-06-13
Authors Alan Clark , Varun Singh , Qin Wu
I-D last updated 2013-06-27
Completed reviews Genart Last Call review of -11 by Meral Shirazipour (diff)
Genart Telechat review of -12 by Meral Shirazipour (diff)
Secdir Last Call review of -11 by Shawn M Emery (diff)
Assignment Reviewer Shawn M Emery
State Completed
Request Last Call review on draft-ietf-xrblock-rtcp-xr-jb by Security Area Directorate Assigned
Reviewed revision 11 (document currently at 14)
Result Has nits
Completed 2013-06-27
review-ietf-xrblock-rtcp-xr-jb-11-secdir-lc-emery-2013-06-27-00
I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the IESG.
These comments were written primarily for the benefit of the security
area directors. Document editors and WG chairs should treat these
comments just like any other last call comments.

This internet-draft specifies a RTP Control Protocol (RTCP) Extended Report
(XR) Block for data on jitter buffer configuration and performance.

The security considerations section does exist and states that the new block
data does not introduce any additional security concerns than those stated
in the base XR spec, RFC 3611.  I believe this to be an accurate assertion.

General comments:

I found the draft slightly hard to read, as the terminology and abbreviations
used are not expanded.  For example, the abstract has "RTP", but never expands
the abbreviation.

Editorial comments:

s/[RFC6390]and/[RFC6390] and/

Shawn.
--