rfc9894v1.txt   rfc9894.txt 
skipping to change at line 117 skipping to change at line 117
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. Extension Usage and Identification 2. Extension Usage and Identification
The extension defined in this document is composed of the mechanisms The extension defined in this document is composed of the mechanisms
and processing defined in [RFC9892] and [RFC9893]. To indicate that and processing defined in [RFC9892] and [RFC9893]. To indicate that
the Diffserv Aware Credit Window Extension is to be used, an the Diffserv Aware Credit Window Extension is to be used, an
implementation MUST include the Diffserv Aware Credit Window Type implementation MUST include the Diffserv Aware Credit Window
Value in the Extensions Supported Data Item (see Section 13.6 of Extension Type Value in the Extensions Supported Data Item (see
[RFC8175]). The Extensions Supported Data Item is sent and processed Section 13.6 of [RFC8175]). The Extensions Supported Data Item is
according to [RFC8175]. Any implementation that indicates the use of sent and processed according to [RFC8175]. Any implementation that
the Diffserv Aware Credit Window Extension MUST support all message indicates the use of the Diffserv Aware Credit Window Extension MUST
types, Data Items, the Diffserv Traffic Classification Sub-Data Item, support all message types, Data Items, the Diffserv Traffic
and all related processing defined in [RFC9892] and [RFC9893]. Classification Sub-Data Item, and all related processing defined in
[RFC9892] and [RFC9893].
The Diffserv Aware Credit Window Extension Type Value is 6. See The Diffserv Aware Credit Window Extension Type Value is 6. See
Section 5. Section 5.
3. Management Considerations 3. Management Considerations
This section provides several network management guidelines for This section provides several network management guidelines for
implementations supporting the Diffserv Aware Credit Window implementations supporting the Diffserv Aware Credit Window
Extension. Extension.
If this extension is supported, that support MUST be declared using If this extension is supported, that support MUST be declared using
the Extensions Supported Data Item (see Section 13.6 of [RFC8175]). the Extensions Supported Data Item (see Section 13.6 of [RFC8175]).
Diffserv Aware Credit Window Extension Data Items MUST NOT be emitted Diffserv Aware Credit Window Extension Data Items MUST NOT be emitted
by a DLEP participant unless such support was specified in the by a DLEP participant unless such support was specified in the
initialization message received from its peer. The use of the initialization message received from its peer. The use of the
extension defined in this document SHOULD be configurable on both extension defined in this document SHOULD be configurable on both
modems and routers. That configuration can be implemented using a modems and routers. That configuration can be implemented using a
proprietary Command-Line Interface (CLI) or by implementing a YANG proprietary Command-Line Interface or by implementing a YANG module.
module. The definition of the YANG module is out of scope for this The definition of the YANG module is out of scope for this document.
document.
Modems SHOULD support the configuration of mapping a DSCP to a credit Modems SHOULD support the configuration of mapping a DSCP to a credit
window (queue). window (queue).
Modems MAY support the configuration of the number of credit windows Modems MAY support the configuration of the number of credit windows
(queues) to advertise to a router. (queues) to advertise to a router.
Routers may have limits on the number of queues that they can support Routers may have limits on the number of queues that they can support
and limits on supported credit window combinations. Per-destination and limits on supported credit window combinations. Per-destination
queues might not be supported at all. When credit window information queues might not be supported at all. When credit window information
 End of changes. 2 change blocks. 
10 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.48.