This document is in very good shape, but version 11 introduced a
significant confusion in the first sentence of the Introduction:
"... the DiffServ Code Point (DSCP) [RFC2474] carried in the
DiffServ field [RFC2474] of the IP packet header and the Traffic
Class field of the IPv6 packet header."
The last clause makes the whole sentence unclear. RFC2474 defines
the DiffServ field thus:
"Differentiated Services Field: the IPv4 header TOS octet or the IPv6
Traffic Class octet when interpreted in conformance with the
definition given in this document."
There is no reason to mention the IPv6 Traffic Class if you do not
also mention the IPv4 TOS byte; it just creates confusion. Please
revert to the previous version of the sentence. To avoid all doubt,
we could refer to Section 2 of RFC 2474 ("Terminology Used in This
Document").
(Incidentally, RFC 2474 doesn't use or define the contraction "DiffServ".
It defines and extensively uses DS as the abbreviation for Differentiated
Services. I'm not objecting to "DiffServ", just saying...)
Regards
Brian Carpenter
On 11-Feb-23 07:57, The IESG wrote:
The IESG has received a request from the Transport Area Working Group WG
(tsvwg) to consider the following document: - 'Considerations for Assigning a
new Recommended DiffServ Codepoint
(DSCP)'
<draft-ietf-tsvwg-dscp-considerations-11.txt> as Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@xxxxxxxx mailing lists by 2023-02-24. Exceptionally, comments may
be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.
Abstract
This document discusses considerations for assigning a new
recommended DiffServ Code Point (DSCP) for a new standard Per Hop
Behavior (PHB). It considers the common observed remarking behaviors
that the DiffServ field might be subjected to along an Internet path.
It also notes some implications of using a specific DSCP.
The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-dscp-considerations/
No IPR declarations have been submitted directly on this I-D.
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
