IP QoS Management

1
IP QoS Management

• Fundamental changes in the service paradigm for
  IP networks (QoS) will necessitate fundamental
  changes in how IP networks are controlled and
  managed.
• The current incremental evolutionary approach
  used by the internet community will not lead to
  QoS in the internet.
• The magnitude of this change has not been
  calculated by most participants in defining IP
  QoS, and the monetary and societal cost will be
  such that it will have major influence on the
  future of the internet.

2
Origins of the Internet

• Four ground rules were critical to early
  architecture
• Communications would be on a best effort basis.
  If a packet didn't make it to the final
  destination, it would shortly be retransmitted
  from the source.
• There would be no global control at the
  operations level.
• Black boxes would be used to connect the
  networks. There would be no information retained
  by the gateways about the individual flows of
  packets passing through them, thereby keeping
  them simple and avoiding complicated adaptation
  and recovery from various failure modes.
• Each distinct network would have to stand on its
  own and no internal changes could be required to
  any such network to connect it to the Internet.

3
Unfolding Internet Paradigm

• Universal ubiquitous communications
  infrastructure
• Distinguishable levels of service
• End-to-end services
• Global control structure
• Formalized agreements between domains
• Global control for communications
• Metering of traffic
• Route selection
• Inter-domain signaling
• Recovery and redundancy of data paths
• Dedicated Control Network
• Non-repudiation and billing functions
• Service level specifications and agreements
• AAA functions

4
IP QoS Issues
Routing QoS community assumption is best effort
path will be used Distinguished flows will
necessitate traffic engineering Service
Delivery Strong requirement for network
management that provides coherent view of the
network not just element management view Strong
requirement for usage based accounting and
billing QoS Inter-Domain signaling Need
accounting, management, and traffic engineering
across autonomous systems?
5
Manage the Access
Identify a flow to get QoS
6
Manage the Access
Verify and control the flow to insure it is
within agreed parameters
7
Manage the intradomain ISs
Configure a each hop for QoS flows
8
Manage the routing domain / AS
Select a path through the network that will give
the quality needed
9
Manage the routing domain / AS
Perform traffic engineering to assure efficient
use of resources
10
Manage the inter-domain gateway
Manage relations between Autonomous Systems to
provide end-to-end QoS
11
Manage the inter-domain gateway
Provide network management and accounting,
especially between Autonomous Systems
12
Edge Information Model

• Differentiated Services (diffserv WG)
• Policy framework (policy WG)

13
Intradomain IS Model

• Differentiated Services (diffserv WG)
• Policy framework (policy WG)

14
Architecture

• Resource Allocation Protocol (rap WG)
• Policy framework (policy WG)

15
Architecture

• Internet2 (Qbone)

Bandwidth Broker
Bandwidth Broker
16
Architecture
Piecemeal approach that needs a comprehensive one
Bandwidth Broker
PDP
PEP
Intra-domain routing
Inter-domain routing
17
IP Service Management in the QoS Network
Building on the work in IRTF Services Management
Research Group Service Management Architectures
Issues and Review (RFC 3052) by Michael Eder and
Sid Nag New IRTF RG Draft IP Service Management
in the QoS Network Centralized management
functionality (distributed implementations)
18
Architecture

• Ground rules critical to architecture
• Operations support for QoS. (Admission control,
  Metering, Route Selection, Inter-domain
  signaling)
• Network operates even in event of catastrophic
  failure of operations system. Black boxes rule
  remains
• Compatible with existing Intermediate Systems
  (ISs) fundamental switching capabilities
• Provides consistent control for all
  communications services

19
Issues Cont.

• Scalability
• Most important for access network
• Edge routers have minimal routing info
• Access core does not have a scaling issue
• Core may not need to participate (just transport)

20
Considerations

• What is going to be the cost of these new systems
  and who is going to take the forefront in
  standardizing and developing them?
• 1/3 vs. 2/3 rule in Telecommunications
• Leave high level management functions to industry
• Will only the large players survive?
• If the communications are proprietary what could
  that mean to the market
• What happens to best effort service in these
  scenarios
• Is the direction of the internet more towards a
  luxury service or a necessity service?
• Traditionally necessity services have been highly
  regulated
• What organization is equipped to address QoS
  control needs?

21
Questions
?
22
Terminology
Network devices without the capability to forward
packets between subnetworks are called end
systems (ESs) Network devices with the capability
to forward packets between subnetworks are called
intermediate systems (ISs) ISs are further
divided into those that can communicate within
routing domains (intradomain ISs) Those that
communicate both within and between routing
domains (interdomain ISs) Routing domains are
also called autonomous systems (AS) AS is usually
under a common administrative authority that is
regulated by a particular set of administrative
guidelines