Found 1 record.

Status: Verified (1)

RFC 4594, "Configuration Guidelines for DiffServ Service Classes", August 2006

Note: This RFC has been updated by RFC 5865, RFC 8622

Errata ID: 4910
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: David Black
Date Reported: 2017-01-18
Verifier Name: Mirja Kühlewind
Date Verified: 2017-01-20

Section 4.8 says:

It can be assumed that this class will consume any available
bandwidth and that packets traversing congested links may
experience higher queuing delays or packet loss.

It should say:

This class is expected to consist of TCP traffic and
other traffic with a TCP-like response to available bandwidth
and network bottlenecks; therefore, it can be assumed that this traffic
will consume any bandwidth available to the class and that packets
traversing congested links may experience higher queuing
delays and/or packet loss.

Notes:

This errata adds some explanation to a sentence in the description of the High-Throughput Data Service Class. The original sentence was misread to imply less than best effort service as part of work on WiFi mapping of Diffserv. That implication is incorrect, e.g., as indicated by the AF1x DSCP marking recommendation. The added explanation was agreed to with the WiFi Diffserv draft authors as sufficient to avoid any implication that less than best effort service is appropriate for this traffic service class.

Report New Errata