Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Niidae Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Differentiated services
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Traffic management mechanisms== DiffServ is a ''coarse-grained'', ''class-based'' mechanism for traffic management. In contrast, IntServ is a ''fine-grained'', ''flow-based'' mechanism. DiffServ relies on a mechanism to ''classify'' and ''mark'' packets as belonging to a specific class. DiffServ-aware routers implement [[per-hop behavior]]s (PHBs), which define the packet-forwarding properties associated with a class of traffic. Different PHBs may be defined to offer, for example, [[Packet loss|low-loss]] or [[Network delay|low-latency]] service. Rather than differentiating network traffic based on the requirements of an individual flow, DiffServ operates on the principle of [[traffic classification]], placing each data packet into one of a limited number of traffic classes. Each router on the network is then configured to differentiate traffic based on its class. Each traffic class can be managed differently, ensuring preferential treatment for higher-priority traffic on the network. The premise of Diffserv is that complicated functions such as packet classification and policing can be carried out at the edge of the network by edge routers. Since no classification and policing is required in the core routers, functionality there can then be kept simple. Core routers simply apply PHB treatment to packets based on their markings. PHB treatment is achieved by core routers using a combination of scheduling policy and queue management policy. A group of routers that implement common, administratively defined DiffServ policies are referred to as a ''DiffServ domain''.<ref>{{citation |url=http://enterprise.huawei.com/ilink/enenterprise/download/HW_134362 |title=S3700HI Ethernet Switches Configuration Guide - QoS |page=7 |publisher=[[Huawei]] |access-date=2016-10-07 |quote=A DiffServ domain is composed of a group of interconnected DiffServ nodes that use the same service policy and PHBs.}}</ref> While DiffServ does recommend a standardized set of traffic classes,{{Ref RFC|4594}} the DiffServ architecture does not incorporate predetermined judgments of what types of traffic should be given priority treatment. DiffServ simply provides a framework to allow classification and differentiated treatment. The standard traffic classes (discussed below) serve to simplify interoperability between different networks and different vendors' equipment.
Summary:
Please note that all contributions to Niidae Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Encyclopedia:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
Differentiated services
(section)
Add topic