Configuration Guidelines for Diffserv Service Classes draft-baker-diffserv-basic-classes-02.txt

1
Configuration Guidelines for Diffserv Service
Classesdraft-baker-diffserv-basic-classes-02.txt

• Fred Baker, fred_at_cisco.com
• Jozef Babiarz, babiarz_at_nortelnetworks.com
• Kwok Ho Chan, khchan_at_nortelnetworks.com
• 59th IETF, March 1, 2004

2
Major Points

• Draft provides guidelines on how to configure QoS
  mechanisms to achieve service differentiation
• Service class indicates network treatments needed
  for service differentiation
• Service classes simplify usage of Diffserv for
  applications
• Applications use DSCP to indicate the required
  service class (network treatment)
• Service classes are End to End
• DSCP marking needs to be used consistently end to
  end
• Service classes utilize the 4 PHBs
• Default Forwarding, Class Selector, AF, and EF

3
Value of Service Classes

• Allows grouping of applications that have
  similar
• Traffic characteristics
• Network performance requirements
• Allows new applications to use existing
  configurations
• Provides differentiation for handling traffic end
  to end
• Each service class has a defined traffic
  characteristics and performance requirements
• Many applications may use the same service class

4
Packet cube
IP-phone (classic) Skype (IP-phone) HTTP File
sharing
300
Customer-provided Slide
600
Variation of packet size (Byte)
900
1200
Average packet size (Byte)
0
300
600
900
1200
1500
Maybe packet rate (not bandwidth) should be a
fourth dimension?
5
Conclusions

• Service classes allow easy expression of
  application requirements
• Service classes allow consistent and simpler
  network deployment
• Having a BCP accelerates the offering of new
  services
• Network administrators are asking for guidelines

6
Next Steps

• Would like to request this draft be a TSVWG work
  item in the form of a BCP