Q. In open-loop congestion control, policies are applied to

View solution

Q. In Congestion Control, the warning message goes directly to the

View solution

Q. Two classes of services have been defined for

View solution

Q. A leaky bucket algorithm shapes bursty traffic into fixed-rate traffic by averaging the

View solution

Q. ADR stands for

View solution

Q. In Forwarded Signaling, a bit can warn the destination about the

View solution

Q. In QoS techniques, packets wait in a buffer (queue) until the node is ready to process them in

View solution

Q. In Congestion, the maximum burst size normally refers to the maximum length of time the traffic is generated at the

View solution

Q. In the slow-start algorithm, the size of the congestion window increases exponentially until it reaches

View solution

Q. In Congestion, to define the maximum data rate of the traffic we use

View solution

Q. The token bucket can easily be implemented with a counter, initialized by

View solution

Q. Integrated Services is based on flow based Quality OF Service model designed for

View solution

Q. In Congestion Control, the packet is put at the end of the input queue while waiting to be

View solution

Q. ABR stands for

View solution

Q. Integrated Services in which the receivers and not the sender makes the reservation is

View solution

Q. The main focus point in Congestion Control and Quality of Services is

View solution

Q. In Congestion Control, a bit can be set in a packet moving in the direction of the

View solution

Q. In Integrated Services, when a source makes a reservation, it needs to define a

View solution

Q. A flow of data needs resources such as a buffer, bandwidth and

View solution

Q. In Congestion, traffic descriptors are qualitative values that represent a

View solution