Ticket #153 (new task)

Opened 5 years ago

Last modified 4 years ago

More flexible DiffServ support

Reported by: pjf Assigned to: pjf
Priority: normal Milestone: 3.0
Component: Traffic control Version:
Severity: normal Keywords:
Cc:

Description

We should be able to assign a lower/higher priority to the traffic of a network client using DiffServ?. I think it should be feasible to replace old ToS policies and use this part of DSCP to introduce our "client class tags".

Thus, we will have possibility to:

  • mark content type - 3 most significant bits (7 possibilities) - bulk, office, media, txt, sys, localmedia
  • mark client SLA - 3 bits after content type - being the relative probability of a single packet to be queued/dropped, ie.
    • 1 - highest priority (lowest probability to be dropped in case of link congestion)
    • (...)
    • 7 - lowest priority (highest probability to be dropped in case of link congestion)

Change History

02/09/07 00:55:50 changed by pjf

  • milestone changed from 2.1 to 3.0.

02/27/07 21:31:11 changed by pjf

  • severity changed from normal to major.
  • milestone changed from 3.0 to 2.1.

Shouldn't be that hard.

  • assign DSCP to PPPoE clients (incoming traffic)
  • replace standard pfifo queues with DiffServ?-aware

02/27/07 21:38:05 changed by pjf

  • type changed from idea to task.
  • severity changed from major to normal.

03/15/08 15:49:29 changed by pjf

  • milestone changed from 2.1rc1 to 3.0.

Milestone 2.1rc1 deleted