3. Management Considerations

This page preserves the original RFC text for the section and adds navigation metadata for the documentation site.

Original RFC Text

3.  Management Considerations

   This section provides several network management guidelines for
   implementations supporting the Diffserv Aware Credit Window
   Extension.

   If this extension is supported, that support MUST be declared using
   the Extensions Supported Data Item (see Section 13.6 of [RFC8175]).
   Diffserv Aware Credit Window Extension Data Items MUST NOT be emitted
   by a DLEP participant unless such support was specified in the
   initialization message received from its peer.  The use of the
   extension defined in this document SHOULD be configurable on both
   modems and routers.  That configuration can be implemented using a
   proprietary Command-Line Interface or by implementing a YANG module.
   The definition of the YANG module is out of scope for this document.

   Modems SHOULD support the configuration of mapping a DSCP to a credit
   window (queue).

   Modems MAY support the configuration of the number of credit windows
   (queues) to advertise to a router.

   Routers may have limits on the number of queues that they can support
   and limits on supported credit window combinations.  Per-destination
   queues might not be supported at all.  When credit window information
   provided by a modem exceeds the capabilities of a router, the router
   SHOULD use a subset of the provided credit windows.  Alternatively, a
   router MAY reset the session and indicate that the extension is not
   supported.  In either case, any mismatch in capabilities SHOULD be
   reported to the user via normal network management mechanisms, such
   as user interface messages or error logging.

   In all cases, if credit windows are in use, traffic for which credits
   are not available MUST NOT be sent to the modem by the router.