Summary

  • RFC 9895 is an IETF Standards Track extension, Extension Type 5, for IEEE 802.1Q-aware DLEP credit windows.
  • Its use is declared through Extensions Supported. An advertising implementation must support the related RFC 9892 and RFC 9893 messages, Data Items, Ethernet classification, and processing: this is a mandatory dependency closure, not a pick-and-mix feature claim.
  • When Diffserv and Ethernet classifiers both match a flow, Ethernet wins. That precedence is an allocation decision: the selected VLAN/PCP classification determines the credit window.

RFC 9895 combines RFC 9892 traffic classification with RFC 9893 credit control and associates logical windows with DLEP destinations, VLAN identifiers, and IEEE 802.1Q priority code points. Windows can be shared or destination-specific. A deployment therefore needs to distinguish a common window from a window attached to a particular destination; the RFC does not establish one universal window design.

The practical configuration starts with PCP-to-window mapping. Per-VLAN PCP mapping may also be supported. If VLANs are supported without PCP, VLAN-to-window mapping should be configurable. VID semantics matter: VID 0 means that the VID is ignored; VID 0xFFFF is reserved; 0x0001 through 0xFFFE are usable for classification. A wildcard PCP or VID can expand the match to unexpected or newly appearing traffic. RFC 9895 recommends wildcards only when clearly needed.

A router that sees more advertised windows than it supports should use a supported subset or may reset the session, while reporting the mismatch through ordinary management mechanisms. When windows are in use, it must not send traffic without sufficient credits. Injected window resizing is a denial-of-service risk because an attacker or untrusted peer could alter the available sending budget.

Verification fixtures

  1. Send a tagged frame whose DSCP maps to window D, while its VID and PCP map to window E. Verify that Ethernet classification selects E and that accounting uses E, not D.
  2. Test VID 0, VID 0xFFFF, VID 1, and VID 0xFFFE separately. Confirm that zero ignores VID, 0xFFFF is rejected as reserved, and the other two are classifiable boundary values.
  3. Advertise the extension and exercise every dependent RFC 9892/9893 message and Data Item. Then advertise more windows than the router supports and verify supported-subset behavior or session reset plus ordinary management reporting.
  4. Exhaust a window, attempt a send, and confirm that no packet leaves without sufficient credit. Apply a controlled resize and verify authorization, audit visibility, and denial of unauthorized changes.

The sources do not establish deployment prevalence, measured performance improvement, a queue count, a telemetry threshold, a rollback timer, a CLI, a YANG module, or one universal VLAN/PCP-to-window design. The trust boundary for VLAN and PCP markings across administrative domains remains an operator decision.

Sources