Last Call Review of draft-ietf-sipbrandy-rtpsec-07
review-ietf-sipbrandy-rtpsec-07-genart-lc-resnick-2019-03-04-00

Request Review of draft-ietf-sipbrandy-rtpsec
Requested revision No specific revision (document currently at 08)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2019-02-21
Requested 2019-02-07
Authors Jon Peterson , Richard Barnes , Russ Housley
I-D last updated 2019-03-04
Completed reviews Genart Last Call review of -07 by Pete Resnick (diff)
Opsdir Last Call review of -07 by Dan Romascanu (diff)
Secdir Last Call review of -07 by Liang Xia (diff)
Assignment Reviewer Pete Resnick
State Completed
Request Last Call review on draft-ietf-sipbrandy-rtpsec by General Area Review Team (Gen-ART) Assigned
Reviewed revision 07 (document currently at 08)
Result Ready w/issues
Completed 2019-03-04
review-ietf-sipbrandy-rtpsec-07-genart-lc-resnick-2019-03-04-00
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-sipbrandy-rtpsec-07
Reviewer: Pete Resnick
Review Date: 2019-03-04
IETF LC End Date: 2019-02-21
IESG Telechat date: 2019-03-07

Summary:

No concerns about the content of the document; looks like reasonable security
recommendations.

I'm not clear on why it's BCP (which usually implies "one and done") instead of
proposed standard; this thing looks like it could evolve with implementation
experience in the future. By no means a showstopper, but worth considering.
(Note that it doesn't require a new Last Call if you decide to change the
status.)