Early Review of draft-ietf-tsvwg-rtcweb-qos-02
review-ietf-tsvwg-rtcweb-qos-02-opsdir-early-baker-2015-02-05-00

Request Review of draft-ietf-tsvwg-rtcweb-qos
Requested revision No specific revision (document currently at 18)
Type Early Review
Team Ops Directorate (opsdir)
Deadline 2016-05-17
Requested 2014-07-15
Authors Paul Jones , Subha Dhesikan , Cullen Fluffy Jennings , Dan Druta
I-D last updated 2015-02-05
Completed reviews Genart Last Call review of -15 by Robert Sparks (diff)
Secdir Last Call review of -13 by Paul E. Hoffman (diff)
Opsdir Early review of -02 by Fred Baker (diff)
Assignment Reviewer Fred Baker
State Completed
Request Early review on draft-ietf-tsvwg-rtcweb-qos by Ops Directorate Assigned
Reviewed revision 02 (document currently at 18)
Result Ready
Completed 2015-02-05
review-ietf-tsvwg-rtcweb-qos-02-opsdir-early-baker-2015-02-05-00
In short, I think this is ready to go.

The document identifies a set of DSCP code point values that might be used in
an RTCWEB application. They differ in various ways, depending on their value to
the application. As noted, the network is expected to provide service at least
as good as what the code point requests, but there is no requirement that it
inspect the code point per se; it may simply over-provision.

With respect to the other questions in

http://tools.ietf.org/html/rfc5706#appendix-A.1

, the document does what is needed to my satisfaction.

Attachment:

signature.asc

Description:

 Message signed with OpenPGP using GPGMail