DSCP Packet Markings for WebRTC QoS
draft-ietf-tsvwg-rtcweb-qos-18
|
| Document |
Type |
|
Active Internet-Draft (tsvwg WG)
|
|
Last updated |
|
2016-08-22
(latest revision 2016-08-19)
|
|
Replaces |
|
draft-dhesikan-tsvwg-rtcweb-qos
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
(wg milestone:
Feb 2016 - Submit 'DSCP packet ...
)
|
|
Document shepherd |
|
David Black
|
|
Shepherd write-up |
|
Show
(last changed 2016-05-11)
|
| IESG |
IESG state |
|
RFC Ed Queue
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Spencer Dawkins
|
|
Send notices to |
|
"David L. Black" <david.black@emc.com>
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
No IC
|
| RFC Editor |
RFC Editor state |
|
MISSREF |
Network Working Group P. Jones
Internet-Draft S. Dhesikan
Intended status: Standards Track C. Jennings
Expires: February 20, 2017 Cisco Systems
D. Druta
AT&T
August 19, 2016
DSCP Packet Markings for WebRTC QoS
draft-ietf-tsvwg-rtcweb-qos-18
Abstract
Many networks, such as service provider and enterprise networks, can
provide different forwarding treatments for individual packets based
on Differentiated Services Code Point (DSCP) values on a per-hop
basis. This document provides the recommended DSCP values for web
browsers to use for various classes of WebRTC traffic.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 20, 2017.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Jones, et al. Expires February 20, 2017 [Page 1]
Internet-Draft WebRTC QoS August 2016
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Relation to Other Specifications . . . . . . . . . . . . . . 3
4. Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. DSCP Mappings . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8. Downward References . . . . . . . . . . . . . . . . . . . . . 9
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
10. Dedication . . . . . . . . . . . . . . . . . . . . . . . . . 9
11. Document History . . . . . . . . . . . . . . . . . . . . . . 9
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
12.1. Normative References . . . . . . . . . . . . . . . . . . 9
12.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
Differentiated Services Code Point (DSCP) [RFC2474] packet marking
can help provide QoS in some environments. This specification
provides default packet marking for browsers that support WebRTC
applications, but does not change any advice or requirements in other
IETF RFCs. The contents of this specification are intended to be a
simple set of implementation recommendations based on the previous
RFCs.
Networks where these DSCP markings are beneficial (likely to improve
QoS for WebRTC traffic) include:
1. Private, wide-area networks. Network administrators have control
over remarking packets and treatment of packets.
2. Residential Networks. If the congested link is the broadband
uplink in a cable or DSL scenario, often residential routers/NAT
support preferential treatment based on DSCP.
3. Wireless Networks. If the congested link is a local wireless
network, marking may help.
There are cases where these DSCP markings do not help, but, aside
from possible priority inversion for "less than best effort traffic"
Jones, et al. Expires February 20, 2017 [Page 2]
Show full document text