Skip to main content

A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated Services
draft-ietf-tsvwg-nqb-33

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-tsvwg-nqb@ietf.org, gorry@erg.abdn.ac.uk, rfc-editor@rfc-editor.org, tsvwg-chairs@ietf.org, tsvwg@ietf.org, zahed.sarker.ietf@gmail.com
Subject: Protocol Action: 'A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated Services' to Proposed Standard (draft-ietf-tsvwg-nqb-33.txt)

The IESG has approved the following document:
- 'A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated
   Services'
  (draft-ietf-tsvwg-nqb-33.txt) as Proposed Standard

This document is the product of the Transport and Services Working Group.

The IESG contact persons are Gorry Fairhurst and Mike Bishop.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-nqb/


Ballot Text

Technical Summary

   This document specifies characteristics of a Non-Queue-Building Per-
   Hop Behavior (NQB PHB).  The NQB PHB provides a shallow-buffered,
   best-effort service as a complement to a Default deep-buffered best-
   effort service for Internet services.  The purpose of this NQB PHB is
   to provide a separate queue that enables smooth (i.e. non-bursty),
   low-data-rate, application-limited traffic microflows, which would
   ordinarily share a queue with bursty and capacity-seeking traffic, to
   avoid the latency, latency variation and loss caused by such traffic.
   This PHB is implemented without prioritization and can be implemented
   without rate policing, making it suitable for environments where the
   use of these features is 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, Wi-Fi links, and mobile
   network radio and core segments are discussed.  This document
   recommends a specific Differentiated Services Code Point (DSCP) to
   identify Non-Queue-Building microflows, and updates the RFC8325
   guidance on mapping Diffserv to IEEE 802.11 for this codepoint.

Working Group Summary

   There was broad agreement on developing this work within the TSVWG 
   working group. This document defines a new PHB and allocates a 
   recommended DSCP for this PHB. The choice of allocated DSCP was 
   considered by the WG over many meetings and there was rough 
   consensus on  the use of the chosen DS codepoint.
   
   A consensus call on the final text was issued in 2024-10-22 
   with only one remaining objection to the DSCP chosen. 

Document Quality

  To complete this work, the WG evaluated candidate DSCPs and 
  agreed to allocate a DSCP, as well as detailed analysis to 
  determine the conditioning required and assess the expected 
  path to deployment. The document has been reviewed in several
  rounds by the WG, and multiple WGLCs for publication on the
  Standards Track. The document received detailed shepherd
  reviews after the second and final call.

Personnel

   The Document Shepherd for this document is Zaheduzzaman Sarker. The 
   Responsible Area Director is Gorry Fairhurst.

RFC Editor Note