DSCP and other packet markings for RTCWeb QoS
draft-jennings-rtcweb-qos-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Subha Dhesikan , Dan Druta , Cullen Fluffy Jennings , Paul Jones , James Polk | ||
Last updated | 2013-03-11 (Latest revision 2012-07-09) | ||
Replaced by | draft-ietf-rtcweb-qos | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-rtcweb-qos | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Many networks, such as Service Provider and Enterprise networks, can provide per packet treatments based on Differentiated Services Code Points (DSCP) on a per hop basis. This document defines the recommended DSCP values for browsers to use for various classes of traffic. This draft is a very early and far from done. It is meant to provide the structure for the idea of how to do this but much discussion is needed about the details.
Authors
Subha Dhesikan
Dan Druta
Cullen Fluffy Jennings
Paul Jones
James Polk
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)