References Used

  1. An Architecture for Differentiated Services (S. Blake, D. Black, M. Carlson, E. Davies, Z.Wang, W. Weiss)

    2. This document (RFC 2475) describes the architecture for implementing scaleable service differentiation in the Internet. Traffic classification is done based on the DS field in the IP header. Aggregation of flows with the same DS field value is done. Service differentiation is achieved by defining per-hop behaviours along the path. Classification, marking, policing and shaping operations are done at network boundaries and hosts to prepare the packet for service differentiation. Network resources are allocated by service provisioning policies which govern the entry into a DS enabled network and also the forwarding behaviour within it.
     
  2. Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 headers  (K. Nichols, S. Blake, F. Baker, D. Black)

    3. This document (RFC 2474) defines the IP header field, the DS field. In IPv4 it defines the layout of the TOS octet. In IPv6 it defines layout of the Traffic Class octet.  A base set of forwarding behaviours also called per-hop behaviours (PHBs) are also defined. While the DS field is the basis for classifying packets for service differentiation, PHBs are the mechasims to provide service differentiation within a DS enabled domain. There is a direct mapping of the DS field to the PHBs. While some DS fields (and hence PHBs) are made standard and thus have global significance, others can have local significance in a particular DS domain.
     
  3. A Framework for Differentiated Services  (Yoram Bernet, James Binder, Steven Blake, Mark Carlson, Brian E. Carpenter, Srinivasan Keshav, Elwyn Davies, Borje Ohlman, Dinesh Verma, Zheng Wang, Walter Weiss)

    4. This document (Internet Draft) provides a general description of the issues related to the definition, configuration and management of services enabled by the differentiated services architecture. A key idea is that traffic is conditioned at the boundary of a DS domain while the interior nodes merely do the forwarding process.
     
  4. Security Issues for Differentiated Service Framework (Zhi Fu, S Felix Wu, T.S. Wu, He Huang)

    5. This document (Internet Draft) provides a sercurity analysis for the differentiated services framework. A threat model is specified and a study of the kind of attacks possible, and the impact of the attacks on the network services is made. The authors voice the need for intrusion detection and response systems to address the security concerns in a network providing QoS through DiffServ.
     
  5. Assured Forwarding PHB group (J. Heinanen, F. Baker, W. Weiss, J. Wroclawski)

    6. This document (RFC 2597) defines the use of the DS PHB (Differentiated Services Per-Hop-Behaviour) group called Assured Forwarding (AF). Four classes are defined and IP packets are classified into one of the four classes based on the DS field. Within each class, there are three levels of drop precedence. Reordering of packets of the same microflow within an AF class is not done.
     
  6. An Expedited Forwarding PHB (V. Jacobson, K. Nichols, K. Poduri)

    7. This document (RFC 2598) describes a PHB called Expedited Forwarding. The generality of the PHB is shown by observing that it can be produced by many mechanism. The authors give an example of its use to produce a Virtual Leased Line. A recommended codepoint for this PHB is also given.
     
  7. A Network Simulator Differentiated Services Implementation - Open IP, Nortel Networks (Peter Pieda, Jeremy Ethridge, Mandeep Baines, Farhan Shallwani)

    8. This report provides the implementation details of the Differentiated Services architecture in the ns network simulator. Brief descriptions of ns and DiffServ and complete details of the modules added to create an ns DiffServ implementation are provided.
     
  8. Differentiated Services on Linux (Werner Almesberger, Jamal Hadi Salim, Alexey Kuznetsov)

    9. This document describes the support for differentiated services in the Linux kernel. The authors have maintained the traffic control elements of Linux and added new components where appropriate. A description of all such components are provided.