A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated Services
draft-ietf-tsvwg-nqb-01
Transport Area Working Group G. White
Internet-Draft CableLabs
Intended status: Standards Track T. Fossati
Expires: September 10, 2020 ARM
March 9, 2020
A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated
Services
draft-ietf-tsvwg-nqb-01
Abstract
This document specifies properties and characteristics of a Non-
Queue-Building Per-Hop Behavior (NQB PHB). The purpose of this NQB
PHB is to provide a separate queue that enables low latency and, when
possible, low loss for application-limited traffic flows that would
ordinarily share a queue with capacity-seeking traffic. This PHB is
implemented without prioritization and without rate policing, making
it suitable for environments where the use of either these features
may be restricted. The NQB PHB has been developed primarily for use
by access network segments, where queuing delays and queuing loss
caused by Queue-Building protocols are manifested, but its use is not
limited to such segments. In particular, applications to cable
broadband links and mobile network radio and core segments are
discussed. This document defines a standard Differentiated Services
Code Point (DSCP) to identify Non-Queue-Building flows.
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 https://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 September 10, 2020.
White & Fossati Expires September 10, 2020 [Page 1]
Internet-Draft Non-Queue-Building PHB March 2020
Copyright Notice
Copyright (c) 2020 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
(https://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
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. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Overview: Non-Queue-Building Flows . . . . . . . . . . . . . 3
4. DSCP Marking of NQB Traffic . . . . . . . . . . . . . . . . . 4
5. Non-Queue-Building PHB Requirements . . . . . . . . . . . . . 5
6. Relationship to L4S . . . . . . . . . . . . . . . . . . . . . 6
7. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. DOCSIS Access Networks . . . . . . . . . . . . . . . . . 6
7.2. Mobile Networks . . . . . . . . . . . . . . . . . . . . . 6
7.3. WiFi Networks . . . . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
10. Security Considerations . . . . . . . . . . . . . . . . . . . 8
11. Informative References . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
This document defines a Differentiated Services (DS) per-hop behavior
(PHB) called "Non-Queue-Building Per-Hop Behavior" (NQB PHB), which
is intended to enable networks to provide low latency and low loss
for traffic flows that are relatively low data rate and that do not
themselves materially contribute to queueing delay and loss. Such
Non-Queue-Building flows (for example: interactive voice and video,
gaming, machine to machine applications) are application limited
flows that are distinguished from traffic flows managed by an end-to-
end congestion control algorithm.
The vast majority of packets that are carried by broadband access
networks are, in fact, managed by an end-to-end congestion control
algorithm, such as Reno, Cubic or BBR. These congestion control
Show full document text