Host-Reported QoS Needs

A.

IntServ follows the signaled-QoS model, where the end-hosts signal their QoS needs to the network.

The QoS model that allows hosts to report their QoS needs to the network is called the Integrated Services (IntServ) QoS model.

IntServ is a QoS architecture that provides a fine-grained, flow-based QoS mechanism, which enables hosts to request and receive specific levels of service from the network. In IntServ, hosts use the Resource Reservation Protocol (RSVP) to signal their QoS requirements to the network. RSVP is a signaling protocol that enables hosts to request specific QoS parameters, such as bandwidth, delay, jitter, and packet loss, for their flows.

The IntServ QoS model operates by setting up a reserved bandwidth for a flow from end to end, which ensures that the required QoS parameters are maintained along the path of the flow. This is achieved by configuring routers and switches in the network to reserve the necessary resources and prioritize traffic according to the QoS requirements of the flows.

In contrast to IntServ, the other QoS models listed in the question do not allow hosts to directly report their QoS needs to the network. Here is a brief overview of these models:

• Class-Based Weighted Fair Queuing (CB-WFQ): This QoS model uses traffic classification based on criteria such as protocol, source and destination IP addresses, and port numbers to prioritize traffic. It does not allow hosts to directly request QoS parameters.
• Differentiated Services (DiffServ): This QoS model uses a simplified, scalable approach to QoS by classifying traffic into a small number of service classes and applying QoS policies to those classes. It does not allow hosts to directly request QoS parameters.
• Modular QoS CLI (MQC): This is a configuration framework that enables the application of QoS policies to specific traffic flows based on various criteria. It does not allow hosts to directly request QoS parameters.