]> University of Aberdeen

School of Engineering Fraser Noble Building Aberdeen AB24 3UE UK ana@erg.abdn.ac.uk

University of Aberdeen

School of Engineering Fraser Noble Building Aberdeen AB24 3UE UK gorry@erg.abdn.ac.uk

University of Aberdeen

School of Engineering Fraser Noble Building Aberdeen AB24 3UE UK r.secchi@abdn.ac.uk

TSVArea TSVWG DSCP DiffServ Codepoints 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 Differentiated Services (DiffServ) architecture has been deployed in many networks. It provides differentiated traffic forwarding based on the DiffServ Code Point (DSCP) carried in the DiffServ field of the IP packet header. DiffServ associates traffic with a service class and categorises it into Behavior Aggregates . Configuration guidelines for service classes are provided in RFC4594. Behavior aggregates are associated with a DiffServ Code Point (DSCP), which in turn maps to a Per Hop Behavior (PHB). Treatment differentiation can be achieved using a variety of schedulers and queues, and also by algorithms that implement access to the physical media. Within a DiffServ domain, operators can set service level specifications , each of which maps to a particular Per Domain Behavior (PDB) that is based on one or more PHBs. The PDB defines which PHB (or set of PHBs) and hence for a specific operator, which DSCP (or set of DSCPs) will be associated with specific BAs as the packets pass through a DiffServ domain, and whether the packets are remarked as they are forwarded.

Service Traffic Class | Behavior -> DiffServ -> Per Hop Aggregate Codepoint Behavior | Schedule, Queue, Drop ]]> Figure showing the role of DSCPs in classifying IP traffic for differential network treatment by a DiffServ Node.

This document discusses considerations for assigning a new DSCP for a standard PHB. It considers some commonly observed DSCP remarking behaviors that might be experienced along an Internet path. It also describes some packet forwarding treatments that a packet with a specific DSCP can expect to receive when forwarded across a link or subnetwork. The document is motivated by new opportunities to use DiffServ end-to-end across multiple domains, such as , proposals to build mechanisms using DSCPs in other standards-setting organisations, and the desire to use a common set of DSCPs across a range of infrastructure (e.g., ,, ).

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. DSCPs are specified in the IANA registry , where a variety of different formats are described. A DSCP can sometimes be referred to by name, such as "CS1", and sometimes by a decimal, hex, or binary value. Hex values are represented in text using prefix 0x. Binary values use prefix 0b.

This section describes the current usage of DSCPs.

The DiffServ architecture specifies the use of the DiffServ field in the IPv4 and IPv6 packet headers to carry one of 64 distinct DSCP values. Within a given administrative boundary, each DSCP value can be mapped to a distinct PHB . When a new PHB is specified, a recommended DSCP value among those 64 values is normally reserved for that PHB, and is assigned by IANA. An operator is not formally required to use the recommended value; indeed [RFC2474] states that "the mapping of codepoints to PHBs MUST be configurable." However, use of the recommended value is usually convenient and avoids confusion. The DSCP space is divided into three pools for the purpose of assignment and management . A summary of the pools is provided in a table (where 'x' refers to either a bit position with value '0' or '1'). A pool of 32 codepoints with a format 0bxxxxx0, to be assigned by IANA Standards Action . A pool of 16 codepoints with a format of 0bxxxx11, reserved for experimental or local (private) use by network operators (see Sections 4.1 and 4.2 of . A pool of 16 codepoints with a format of 0bxxxx01. This was initially available for experimental or local use, but was originally specified to be "preferentially utilized for standards assignments" if Pool 1 is ever exhausted. had recommended a local use of DSCP values 0x01, 0x03, 0x05 and 0x07 (codepoints with the format of 0b000xx1). Pool 3 codepoints are now "utilized for standards assignments and are no longer available for assignment to experimental or local use" . assigned 0x01 from this pool and consequentially updated . Any future request to assign 0x05 would be expected to similarly update . The DSCP space is shown in the following Figure.

Figure showing the current list of assigned DSCPs and their assigned PHBs.

Figure showing the summary of the DSCP abbreviations used in published RFCs.

The above table summarises the DSCP abbreviations used in currently published RFCs , as described in the IANA registry . BE, also known as CS0, describes the default forwarding treatment. The DiffServ architecture allows forwarding treatments to be associated with each DSCP, and the RFC series describes some of these as PHBs. Although DSCPs are intended to identify specific treatment requirements, multiple DSCPs might also be mapped (aggregated) to the same forwarding treatment. DSCPs can be mapped to treatment aggregates that might result in remarking (e.g., RFC5160 suggests Meta-QoS-Classes to help enable deployment of standard end-to-end QoS classes)

Network Control Traffic is defined as packet flows that are essential for stable operation of the administered network (see , Section 3). The traffic consists of the network control service class and the OAM service class. This traffic is marked with a value from a set of Class Selector (CS) DSCPs. This traffic is often a special case within a provider network, and ingress traffic with these DSCP markings can be remarked. DSCP CS2 is recommended for the OAM (Operations, Administration, and Maintenance) service class (see , Section 3.3). DSCP CS6 is recommended for local network control traffic. This includes routing protocols and OAM traffic that are essential to network operation administration, control and management. Section 3.2 of RFC4594 recommends that "CS6 marked packet flows from untrusted sources (for example, end-user devices) SHOULD be dropped or remarked at ingress to the DiffServ network". DSCP CS7 is reserved for future use by network control traffic. "CS7 marked packets SHOULD NOT be sent across peering points" . RFC2474 recommends PHBs selected by CS6 and CS7 "MUST give packets preferential forwarding treatment by comparison to the PHB selected by codepoint '000000'". At the time of writing, there is evidence to suggest CS6 is actively used by network operators for control traffic. A study of traffic at a large Internet Exchange showed around 40% of ICMP traffic carried this mark . Similarly, another study found many routers remark all traffic except those packets with a DSCP that sets the higher order bits to 0b11 (see Section 4 of this document).

It is a feature of the DiffServ architecture that the DiffServ field of packets can be remarked at the Diffserv domain boundaries (see Section 2.3.4.2 of ). A DSCP can be remarked at the ingress of a domain. This remarking can change the DSCP value used on the remainder of an IP path, or the network can restore the initial DSCP marking at the egress of the domain. The DiffServ field can also be remarked based on common semantics and agreements between providers at an exchange point. Furthermore, states that remarking must occur when there is a possibility of theft/denial-of-service attack. The treatment of packets that are marked with an unknown or an unexpected DSCP at DiffServ domain boundaries is determined by the policy for a DiffServ domain. If packets are received that are marked with an unknown or an unexpected DSCP by a DiffServ domain interior node, recommends forwarding the packet using a default (best effort) treatment, but without changing the DSCP. This seeks to support incremental DiffServ deployment in existing networks as well as preserve DSCP markings by routers that have not been configured to support DiffServ. (See also ). clarifies that this remarking specified by RFC2474 is intended for interior nodes within a DiffServ domain. For DiffServ ingress nodes the traffic conditioning required by RFC 2475 applies first. Reports measuring existing deployments have defined a set of categories for DSCP remarking into the following seven observed remarking behaviors: bleaches all traffic (sets the DSCP to zero); set the first three bits of the DSCP field to 0b000 (reset the 3 bits of the former ToS Precedence field, defined in , and clarified in ); set the first three bits of the DSCP field to 0b000 (reset the 3 bits of the former ToS Precedence field), unless the first two bits of the DSCP field are 0b11; set the first three bits of the DSCP field to any value different than 0b000 (replace the 3 bits of the former ToS Precedence field); set the last three bits of the DSCP field to 0b000; set the last three bits of the DSCP field to 0b000, unless the first two bits of the DSCP field are 0b11; remarks all traffic to one or more particular (non-zero) DSCP values. NOTE: More than one mechanism could result in the same DSCP remarking (see below). The behaviors were measured on Internet paths between 2017 and 2021. The network nodes forming a particular path might or might not have supported DiffServ. It is not generally possible for an external observer to determine which mechanism results in a specific remarking solely from the change in an observed DSCP value.

A specific form of remarking occurs when the DiffServ field is re-assigned to the default treatment, CS0 (0x00). This results in traffic being forwarded using the BE PHB. For example, AF31 (0x1a) would be bleached to CS0. A survey reported that resetting all the bits of the DiffServ field to 0 was seen to be more prevalent at the edge of the network, and rather less common in core networks .

The IETF first defined ToS precedence for IP packets in , and updated it to be part of the ToS Field in . Since 1998, this practice has been deprecated by . RFC 2474 defines DSCPs 0bxxx000 as the Class Selector codepoints, where PHBs selected by these codepoints MUST meet the Class Selector PHB Requirements" described in Sec. 4.2.2.2 of that RFC. However, a recent survey reports practices based on ToS semantics have not yet been eliminated from the Internet, and need to still be considered when making new DSCP assignments .

ToS Precedence Bleaching (/Bleach-ToS-Precedence/) is a practice that resets the first three bits of the DSCP field to zero (the former ToS Precedence field), leaving the last three bits unchanged (see Section 4.2.1 of ). A DiffServ node can be configured in a way that results in this remarking. This remarking can also occur when packets are processed by a router that is not configured with DiffServ (e.g., configured to operate on the former ToS precedence field ). At the time of writing, this is a common manipulation of the DiffServ field. The following Figure depicts this remarking.

Figure showing the ToS Precedence Bleaching (/Bleach-ToS-Precedence/) observed remarking behavior, based on Section 3 of . The bit positions marked "x" are not changed.

As a result of ToS Precedence Bleaching, all the DSCPs in each column are remarked to the smallest DSCP in that column. Therefore, the DSCPs in the bottom row have higher survivability across an end-to-end Internet path.

Data on the observed remarking at the time of writing was presented in .

Figure showing 0b000xxx DSCPs, highlighting any current assignments and whether they are affected by any known remarking behaviors. * DSCP 4 has been historically used by the SSH application..

The above figure summarizes the current assignments for DSCPs of the form 0b000xxx and whether a DSCP is affected by any known remarking behaviors. For example, ToS Precedence Bleaching of popular DSCPs AF11, AF21, AF31, AF41 would result in traffic being remarked with DSCP 2 in the Internet core. The Lower-Effort Per-Hop Behavior PHB (LE) uses a DSCP of 4. This value has been historically used by the SSH application, following semantics that precede DiffServ . If ToS Precedence Bleaching occurs, packets with a DSCP 'x' would be remarked to 'x' & 0x07 and then would be forwarded using the PHB specified for the resulting DSCP in that Diffserv domain. In subsequent networks it will receive treatment as specified by the domain's operator corresponding to the remarked codepoint. A variation of this observed remarking behavior clears the top three bits of a DSCP, unless these have values 0b110 or 0b111 (corresponding to the CS6 and CS7 DSCPs). As a result, a DSCP value greater than 48 decimal (0x30) is less likely to be impacted by ToS Precedence Bleaching.

states "Implementors should note that the DSCP field is six bits wide. DS-compliant nodes MUST select PHBs by matching against the entire 6-bit DSCP field, e.g., by treating the value of the field as a table index which is used to select a particular packet handling mechanism which has been implemented in that device". This replaced remarking according to ToS precedence (/Remark-ToS/) . These practices based on ToS semantics have not yet been eliminated from deployed networks.

Figure showing ToS Precedence Remarking (/Remark-ToS/) observed behavior, based on Section 3 of . The bit positions marked "x" remain unchanged.

A less common remarking, ToS Precedence Remarking sets the first three bits of the DSCP to a non-zero value corresponding to a CS PHB. This remarking occurs when routers are not configured to perform DiffServ remarking. If ToS Precedence Remarking occurs, packets are forwarded using the PHB specified for the resulting DSCP in that domain. For example, the AF31 DSCP (0x1a) could be remarked to either AF11 or AF21. If such a remarked packet further traverses other Diffserv domains, it would receive treatment as specified by each domain's operator corresponding to the remarked codepoint.

A network device might remark the DiffServ field of an IP packet based on a local policy with a specific (set of) DSCPs, /Remark/. Section 3 of recommends: "Packets received with an unrecognized codepoint SHOULD be forwarded as if they were marked for the Default behavior, and their codepoints should not be changed." Some networks might not follow this recommendation and instead remark packets with these codepoints to the default class, CS0 (0x00). This remarking is sometimes performed using a Multi-Field (MF) classifier . If remarking occurs, packets are forwarded using the PHB specified for the resulting DSCP in that domain. As an example, remarking traffic AF31, AF32 and AF33 all to a single DSCP, e.g. AF11, stops any drop probability differentiation, which may have been expressed by these three DSCPs. If such a remarked packet further traverses other domains, it would receive treatment as specified by the domain's operator corresponding to the remarked codepoint. Bleaching (/Bleach/) is a specific example of this observed remarking behavior that remarks to CS0 (0x00) (see ).

Transmission systems and subnetworks can, and do, utilise the DiffServ field in an IP packet to set a QoS-related field or function at the lower layer. A lower layer could also implement a traffic conditioning function that could remark the DSCP used at the IP layer. This function is constrained by designs that utilise fewer than 6 bits to express the service class, and therefore infer a mapping to a smaller L2 QoS field, for example, the 3-bit PCP field in an IEEE Ethernet 802.1Q header, the 3-bit WiFi UP field or the 3-bit Traffic Class field of Multi-Protocol Label Switching (MPLS). A Treatment Aggregate (TA) is an optional intermediary mapping groups of BAs to PHBs.

The IEEE specifies standards that include mappings for DSCPs to lower layer elements.

A 3-bit Priority Code Point (PCP) is specified in the IEEE 802.1Q tag to mark Ethernet frames to one of eight priority values . The value zero indicates the default best effort treatment, and the value one indicates a background traffic class. The remaining values indicate increasing priority. Internet control traffic can be marked as CS6, and network control is marked as CS7. The mapping specified in revises a previous standard , in an effort to align with DiffServ practice: the traffic types are specified to match the first three bits of a suitable DSCP (e.g., the first three bits of the EF DSCP are mapped to a PCP of 5). However, maps both PCP1 (Background) and PCP2 (Spare) to indicate lower priority than PCP0, RFC8622. Therefore, different remarking behaviors are expected depending on the age of deployed devices.

Section 6 of provides a brief overview of IEEE 802.11 QoS. The IEEE 802.11 standards provide MAC functions to support QoS in WLANs using Access Classes (AC). The upstream User Priority (UP) in the 802.11 header has a 3-bit QoS value. A DSCP can be mapped to the UP. Most current WiFi implementations use a default mapping that maps the first three bits of the DSCP to the 802.11 UP value. This is an example of equipment still classifying on ToS Precedence (which could be seen as a simple method to map IP layer DiffServ to layers offering only 3-bit QoS codepoints). Then, in turn, this is mapped to the four WiFi Multimedia (WMM) Access Categories. The Wi-Fi Alliance has also specified a more flexible mapping that follows RFC8325 and provides functions at an AP to remark packets as well as a QoS Map that maps each DSCP to an AC .

Figure showing the DSCP bits commonly mapped to the UP in 802.11. The bit positions marked "x" are mapped to the 3-bit UP value, while the ones marked "." are ignored.

RFC8325 notes inconsistencies that can result from such remarking, and recommends how to perform this remarking. It proposes several recommendations for mapping a DSCP to an IEEE 802.11 UP for wired-to-wireless interconnection. The recommendation includes mapping network control traffic CS6 and CS7, as well unassigned DSCPs, to UP 0. In the upstream direction (wireless-to-wired interconnections, this mapping can result in a specific DSCP remarking behavior. Some Access Points (APs) currently use a default UP-to-DSCP mapping , wherein "DSCP values are derived from the layer 2 UP values by multiplying the UP values by eight (i.e., shifting the three UP bits to the left and adding three additional zeros to generate a 6-bit DSCP value). This derived DSCP value is used for QoS treatment between the wireless AP and the nearest classification and marking policy enforcement point (which may be a central wireless LAN controller, relatively deep within the network). Alternatively, in the case where there is no other classification and marking policy enforcement point, then this derived DSCP value will be used on the remainder of the Internet path." This can result in remarking /Bleach-low/.

Figure showing the observed remarking behavior resulting from deriving from UP-to-DSCP mapping in some 802.11 networks.

An alternative to UP-to-DSCP remapping uses the DSCP value of a downstream IP packet (e.g., the Control And Provisioning of Wireless Access Points (CAPWAP) protocol, RFC5415, maps an IP packet DiffServ field to the DiffServ field of the outer IP header in a CAPWAP tunnel). Some current constraints of WiFi mapping are discussed in Section 2 of . A QoS profile can be used to limit the maximum DSCP value used for the upstream and downstream traffic.

Multi-Protocol Label Switching (MPLS) specified eight MPLS Traffic Classes (TCs), which restrict the number of different treatments . RFC 5127 describes the aggregation of DiffServ TCs and introduces four DiffServ Treatment Aggregates. Traffic marked with multiple DSCPs can be forwarded in a single MPLS TC. There are three Label-Switched Router (LSR) models: the Pipe, the Short Pipe and the Uniform Model . In the Uniform and Pipe models, the egress MPLS router forwards traffic based on the received MPLS TC. The Uniform Model includes an egress DSCP rewrite. With the Short Pipe Model, the egress MPLS router forwards traffic based on the DiffServ DSCP as present at the egress router. If the domain supports IP and MPLS QoS differentiation, controlled behavior requires the DSCP of an (outer) IP header to be assigned or re-written by all domain ingress routers to conform with the domain's internal DiffServ deployment. Note that the Short Pipe Model is prevalent in MPLS domains.

RFC3270 defines a flexible solution for support of DiffServ over MPLS networks. This allows an MPLS network administrator to select how BAs (marked by DSCPs) are mapped onto Label Switched Paths (LSPs) to best match the DiffServ, Traffic Engineering and protection objectives within their particular network. Mappings from the IP DSCP to the MPLS header are defined in Section 4.2 of . The Pipe Model conveys the "LSP Diff-Serv Information" to the LSP Egress so that its forwarding treatment can be based on the IP DSCP. When Penultimate Hop Popping (PHP) is used, the Penultimate LSR needs to be aware of the encapsulation mapping for a PHB to the label corresponding to the exposed header to perform DiffServ Information Encoding (Section 2.5.2 of ).

The Short Pipe Model is an optional variation of the Pipe Model . ITU-T Y.1566 further defined a set of four common QoS classes and four auxiliary classes to which a DSCP can be mapped when interconnecting Ethernet, IP and MPLS networks. proposes four treatment aggregates for interconnection with four defined DSCPs. This was motivated by the requirements of MPLS network operators that use Short-Pipe tunnels, but can be applicable to other networks, both MPLS and non-MPLS. RFC8100 recommends preserving the notion of end-to-end service classes, and recommends a set of standard DSCPs mapped to a small set of standard PHBs at interconnection. The key requirement is that the DSCP at the network ingress is restored at the network egress. The current version of RFC8100 limits the number of DSCPs to 6 and 3 more are suggested for extension. RFC8100 respects the deployment of PHB groups for DS domain internal use, which limits the number of acceptable external DSCPs (and possibilities for their transparent transport or restoration at network boundaries). In this design, packets marked with DSCPs not part of the RFC8100 codepoint scheme are treated as unexpected and will possibly be remarked (a /Remark/ behavior) or dealt with via an additional agreement(s) among the operators of the interconnected networks. RFC8100 can be extended to support up to 32 DSCPs by future standards. RFC8100 is operated by at least one Tier 1 backbone provider. Use of the MPLS Short Pipe Model favours remarking unexpected DSCP values to zero in the absence of an additional agreement(s), as explained in . This can result in bleaching (/Bleach/).

The short-pipe MPLS mapping from RFC 8100.

Mobile LTE and 5G standards have evolved from older UMTS standards, and support DiffServ. LTE (4G) and 5G standards identify traffic classes at the interface between User Equipment (UE) and the mobile Packet Core network by QCI (QoS Class Identifiers) and 5QI (5G QoS Identifier). The 3GPP standards do not define or recommend any specific mapping between each QCI or 5QI and DiffServ (and mobile QCIs are based on several criteria service class definitions). The way packets are mapped at the Packet Gateway (P-GW) boundary is determined by network operators. However, TS 23.107 (version 16.0.0, applies to LTE and below) mandates that Differentiated Services, defined by IETF, shall be used to interoperate with IP backbone networks. The GSM Association (GSMA) has defined four aggregated classes and seven associated PHBs in their guidelines for IPX Provider networks GSMA IR.34. This was previously specified as the Inter-Service Provider IP Backbone Guidelines, and provides a mobile ISP to ISP QoS mapping mechanism, and interconnection with other IP networks in the general Internet. If provided an IP VPN, the operator is free to apply its DS Domain internal codepoint scheme at outer headers and inner IPX DSCPs may be transported transparently. The guidelines also describe a case where the DSCP marking from a Service Provider cannot be trusted (depending on the agreement between the Service Provider and its IPX Provider), in which situation the IPX Provider can remark the DSCP value to a static default value.

Figure showing the PHB mapping recommended in the guidelines proposed in GSMA IR.34.

Metro Ethernet Forum (MEF) provides a mapping of DSCPs at the IP layer to quality of service markings in the Ethernet frame headers MEF 23.1.

This includes any other remarking that does not happen as a result of traffic conditioning, such as policies and L2 procedures that result in remarking traffic as a side-effect of other functions (e.g., in response to Distributed Denial of Service, DDoS).

This section has discussed the various ways in which DSCP remarking behaviors can arise from interactions with lower layers. A provider service path may consist of sections where multiple and changing layers use their own code points to determine differentiated forwarding (e.g., IP - MPLS - IP - Ethernet - WiFi).

This section provides advice for the assignment of a new DSCP value. It is intended to aid the IETF and IESG in considering a request for a new DSCP. The section identifies known issues that might influence the finally assigned DSCP, and provides a summary of considerations for assignment of a new DSCP.

Section 4 describes remarking of the DSCP. New DSCP assignments should consider the impact of bleaching (/Bleach/) or remarking (/Remark/) to a single DSCP, which can limit the ability to provide the expected treatment end-to-end. This is particularly important for cases where the codepoint is intended to result in lower than best effort treatment, as was the case when defining the LE PHB . Forwarding LE using the default PHB is in line with RFC8622, but it is recommended to maintain the distinct LE DSCP codepoint end-to-end to allow for differentiated treatment by domains supporting LE. Rewriting the LE DSCP to the default class (CS0) results in an undesired promotion of the priority for LE traffic in such a domain. Bleaching the lower three bits of the DSCP (/Bleach-low/ and /Bleach-some-low/), as well as remarking to a particular DSCP can result in similar changes of priority relative to traffic that is marked with other DSCPs.

Although the IETF specifications require systems to use DSCP marking semantics in place of methods based on the former ToS field, the current recommendation is that any new assignment where the DSCP is greater than 0x07 should consider the semantics associated with the resulting DSCP when ToS Precedence Bleaching (/Bleach-ToS-Precedence/ and /Bleach-some-ToS/) or ToS Precedence Remarking (/Remark-ToS/) is experienced. For example, it can be desirable to avoid choosing a DSCP that could be remarked to LE, Lower Effort, which could otherwise potentially result in a priority inversion in the treatment.

ToS Precedence Bleaching or ToS Precedence Remarking can unintentionally result in extra traffic aggregated to the same DSCP. For example, after experiencing ToS Precedence Bleaching, all traffic marked AF11, AF21, AF31 and AF41 would be aggregated with traffic marked with DSCP 2 (0x02), increasing the volume of traffic which receives the treatment associated with DSCP 2. New DSCP assignments should consider unexpected consequences arising from this observed remarking behavior.

As a consequence of assigning the LE PHB , the IETF allocated the DSCP 0b000001 from Pool 3. When making assignments where the DSCP has a format: 0bxxx001, the case of ToS Precedence Bleaching (/Bleach-ToS-Precedence/) of a DSCP to a value of 0x01 needs to be considered. ToS Precedence Bleaching will result in demoting the traffic to the lower effort traffic class. Care should be taken to consider the implications of remarking when choosing to assign a DSCP with this format.

Behavior of deployed PHBs and conditioning treatments also needs to be considered when assigning a new DSCP. Network operators have choices when it comes to configuring DiffServ support within their domains, and the observed remarking behaviors described in the previous section can result from different configurations and approaches: A network that either does not implement PHBs, or implements one or more PHBs whilst restoring the DSCP field at network egress with the value at network ingress. Operators in this category pass all DSCPs transparently. A network that implements more than one PHB and enforces Service Level Agreements (SLAs) with its peers. Operators in this category use conditioning to ensure that only traffic that matches a policy is permitted to use a specific DSCP (see ). Operators need to classify the received traffic, assign it to a corresponding PHB, and could remark the DSCP to a value that is appropriate for the domain's deployed DiffServ infrastructure. Networks containing misconfigured devices that do not comply with the relevant RFCs. Networks containing devices that implement an obsolete specification or contain software bugs. Networks containing devices that remark the DSCP as a result of lower layer interactions. The DSCP re-marking corresponding to the ToS Precedence Bleaching (/Bleach-ToS-Precedence/) observed behavior described in Section 4 can arise for various reasons, one of which is old equipment which precedes DiffServ. The same remarking can also arise in some cases when traffic conditioning is provided by DiffServ routers at operator boundaries or as a result of misconfiguration.

A series of questions emerge that need to be answered when considering a proposal to the IETF that requests a new assignment. These questions include: Is the request for local use within a DiffServ domain that does not require interconnection with other DiffServ domains? This request can use DSCPs in Pool 2 for local or experimental use, without any IETF specification for the DSCP or associated PHB. What are the characteristics of the proposed service class?: What are the characteristics of the traffic to be carried? What are the expectations for treatment? Service classes that can utilise existing PHBs should use assigned DSCPs to mark their traffic: Could the request be met by using an existing IETF DSCP? Specification of a new recommended DSCP requires Standards Action. RFC2474 states: "Each standardized PHB MUST have an associated RECOMMENDED codepoint". If approved, new IETF assignments are normally made by IANA in Pool 1, but the IETF can request assignments to be made from Pool 3 . Does the ID contain an appropriate request to IANA? The value selected for a new DSCP can impact the ability of an operator to apply logical functions (e.g., a bitwise mask) to related codepoints when configuring DiffServ. A suitable value can simplify configurations by aggregating classification on a range of DSCPs. This classification based on DSCP ranges can increase the comprehensibility of documenting forwarding differentiation. describes examples of treatment aggregation. What are the effects of treatment aggregation on the proposed DSCP? describes some observed treatments by layers below IP. What are the implications of the treatments and mapping described in on the proposed DSCP? DSCPs are assigned to PHBs and can be used to enable nodes along an end-to-end path to classify the packet for a suitable PHB. describes some observed remarking behavior, and identifies root causes for why this remarking is observed. What is the expected effect of currently-deployed remarking on the service, end-to-end or otherwise?

The authors acknowledge the helpful discussions and analysis by Greg White and Thomas Fossati in a draft concerning NQB. Ruediger Geib and Brian Carpenter contributed comments, along with other members of the TSVWG.

This memo provides information to assist in considering new assignments to the IANA DSCP registry (https://www.iana.org/assignments/dscp-registry/dscp-registry.xhtml). This memo includes no request to IANA, or update to the IANA procedures.

The security considerations are discussed in the security considerations of each cited RFC.

&RFC2119; &RFC2474; &RFC2475; &RFC3260; &RFC3290; &RFC4594; &RFC5129; &RFC8100; &RFC8436; IANA &RFC0791; &RFC1122; &RFC1349; &RFC2597; &RFC3086; &RFC3246; &RFC3270; &RFC5127; &RFC5160; &RFC5865; &RFC8325; &RFC8126; &RFC8174; &RFC8622; &I-D.ietf-tsvwg-nqb; 3GPP GSM Association ITU-T IEEE Wi-Fi Alliance IEEE IEEE University of Aberdeen, UK MEF &I-D.learmonth-rfc1226-bis;

Note to RFC-Editor: please remove this entire section prior to publication. Individual draft -00, initial document. Individual draft -01, address comments from Martin Duke; Brian Carpenter; Ruediger Geib, and revisions to improve language consistency. Individual draft -02, revise to improve language consistency. Working Group -00, replace individual draft. Working Group -01, address feedback in preparation for IETF 113 Vienna. Working Group -02: Consolidate terminology after IETF 113 Vienna. Add clarification to RFC2474 and RFC2475 addressed in RFC3260 (comments from Ruediger Geib). Include figures to show the full list of codepoints, their assigned PHBs & impact of ToS Precedence Bleaching. Add network categories that differentiate between network operator approaches to DiffServ. Add Terminology section to clarify representations of DSCPs. Working Group -03 Add table to explain DSCP abbreviations (comment from Brian Carpenter). Add some refs, improve language consistency (comments from Brian Carpenter). Clarify figure captions. Working Group -04 Reference RFC3086 (comment from Brian Carpenter). Improve references (comments from Ruediger Geib). Clarify intended document audience and scope (comments from Ruediger Geib). Clarify terms and language around re-marking, DiffServ domains and nodes, RFC8100 (comments from Ruediger Geib). More in-depth on mappings specified for mobile networks/MPLS short-pipe (comments from Ruediger Geib). Working Group -05 Clarify meaning of RFC2474 with respect to IP precedence (comments from Ruediger Geib). Add note on understanding the process of remarking (comments from Ruediger Geib). Improve readibility. Working Group -06 Quote RFC2474 with respect to IP precedence (comments from Ruediger Geib). Ensure it is clear that different remarking processes may result in the same observed remarking. Clarify Treatment Aggregates are part of methods such as MPLS (comments from David Black). Clarify implications on the rest of the path by remarking in one domain. Include all observed remarking behaviors in Section 6. Remove mentions of DSCP 5 being provisionally assigned to NQB. Clarify scope of network control traffic in Section 3.2. Improve readibility. Working Group -07 Update Section 4 to clarify both types of paths measured. Revised paragraph 2 in Introduction Working Group -08 Update after Shepherd review with additional comments from R. Geib. D. Black and B. Carpenter provided comments on relationship to RFC 2474. Working Group -09 Updates to document structure to avoid references in artwork legend. Fix DSCP table indentation Update ref to nqb draft to -15 Working Group -10 Document updated after AD review Add clarification on former use of CS1