draft-ietf-tsvwg-rtcweb-qos-09.txt   draft-ietf-tsvwg-rtcweb-qos-10.txt 
Network Working Group S. Dhesikan Network Working Group S. Dhesikan
Internet-Draft C. Jennings Internet-Draft C. Jennings
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: July 26, 2016 D. Druta, Ed. Expires: July 27, 2016 D. Druta, Ed.
AT&T AT&T
P. Jones P. Jones
Cisco Systems Cisco Systems
January 23, 2016 January 24, 2016
DSCP and other packet markings for WebRTC QoS DSCP and other packet markings for WebRTC QoS
draft-ietf-tsvwg-rtcweb-qos-09 draft-ietf-tsvwg-rtcweb-qos-10
Abstract Abstract
Many networks, such as service provider and enterprise networks, can Many networks, such as service provider and enterprise networks, can
provide treatment for individual packets based on Differentiated provide treatment for individual packets based on Differentiated
Services Code Point (DSCP) values on a per-hop basis. This document Services Code Point (DSCP) values on a per-hop basis. This document
provides the recommended DSCP values for web browsers to use for provides the recommended DSCP values for web browsers to use for
various classes of WebRTC traffic. various classes of WebRTC traffic.
Status of This Memo Status of This Memo
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 26, 2016. This Internet-Draft will expire on July 27, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 22 skipping to change at page 4, line 22
benefits the first few hops. benefits the first few hops.
3. Terminology 3. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
4. Inputs 4. Inputs
WebRTC entities transmit and receive two types of media of WebRTC entities transmit and receive two types of flows of
significance to this document: significance to this document:
o media flows which are RTP streams [I-D.ietf-rtcweb-rtp-usage] o media flows which are RTP streams [I-D.ietf-rtcweb-rtp-usage]
o data flows which are data channels [I-D.ietf-rtcweb-data-channel] o data flows which are data channels [I-D.ietf-rtcweb-data-channel]
Each of the RTP streams and distinct data channels consists of all of Each of the RTP streams and distinct data channels consists of all of
the packets associated with an independent media entity and are not the packets associated with an independent media entity and are not
always equivalent to a transport-layer flow defined by a 5-tuple always equivalent to a transport-layer flow defined by a 5-tuple
(source address, destination address, source port, destination port, (source address, destination address, source port, destination port,
and protocol). There may be multiple RTP streams and data channels and protocol). There may be multiple RTP streams and data channels
 End of changes. 5 change blocks. 
5 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/