The first ip-criteria entry maps every packet whose DSCP value is AFxy to FC “H2” and does not change the profile, so those packets are marked in-profile (A).

Queues use the default FC-to-queue map: EF→queue 1, H2→queue 3. Because EF is configured as a strict-priority class, it is always scheduled ahead of H2 (D).

Traffic that fails to match any ip-criteria entry inherits the policy defaults (FC H2, profile in) and is therefore sent to queue 3 (E).

B. Only TCP packets that were not already matched by the earlier AF DSCP rule are sent to FC EF, so not “all” TCP traffic is mapped to EF.

C. UDP matches the H2 rule and goes to queue 3, but the ICMP rule places ICMP in FC L2 (queue 6), not queue 5.

1. Nokia 7750 SR OS Quality of Service Guide, Rel-21.10.R1, Table 67 “Default queue/FC mapping” (p. 211).

2. Same guide, Sec. 6.3.2 “SAP-ingress ip-criteria – first match applies” (pp. 192-193).

3. Same guide, Sec. 6.2 “Profiles; default is in-profile when unspecified” (p. 165).

4. Nokia Service Routing Architect (SRA) Courseware, Module “QoS-1”, slide 34: EF strict-priority over H-classes.

5. K. Salah, “Differentiated Services in Carrier Ethernet,” IEEE Comm. Mag., vol. 52, no. 3, 2014, doi:10.1109/MCOM.2014.6957163 (discussion of EF strict priority).