Internet2 QBone

1
Internet2QBone

• Ben Teitelbaumltben_at_internet2.edugtJoint NLANR
  Internet2 Techs Meeting
• November 3rd 1998

2
The QBone - What is It?

• QBone ? testbed for interdomain DiffServ
  intradomain solutions group
• Goals
• Grow a snowball of interoperable DiffServ clouds
• Grow a community of participants
• Foster pre-standards interoperability
• Collaborate to solve problems and share
  experiences
• Initial participants have been identified

3
QoS WG Membership

• Osama Aboul-Magd (Nortel/Bay)
• Andy Adamson (Michigan)
• Grenville Armitage (Lucent)
• Steve Blake (Torrent)
• Scott Bradner (Harvard)
• Scott Brim (Newbridge)
• Larry Conrad (Florida State)
• John Coulter (CAnet2)
• Chuck Song / Laura Cunningham (MCI/vBNS)
• Fred Baker / Larry Dunn (Cisco)

• Cliff Frost (UC Berkeley)
• Rüdiger Geib (Deutsche Telekom)
• Terry Gray (U Washington)
• Jim Grisham (NYSERNet)
• Roch Guerin (Penn)
• Susan Hares (Merit)
• Joseph Lappa (CMU
• Jay Kistler (FORE)
• Kathleen Nichols (IETF Liaison)
• Ken Pierce (3com)
• John Sikora (ATT Labs)

4
Milestones

• November 1997, First meeting (Ann Arbor)
• Lots of initial head scratching and brainstorming
• February 1998, Second meeting (Chicago)
• Agreement on requirements
• Agreement on general approach
• Action plan for proposal début
• April 1998, Third meeting (Los Angeles)
• Increased understanding of rollout phasing
• Refinement of pre-workshop papers
• May 1998, I2QoS98 (Santa Clara)
• September 1998, QBone CFP

5
I2QoS98 Recommendations

• DiffServ appears to solve a lot of problems
• Scaling
• Interoperability
• Focus initially on non-relative services
• Other services later (i.e. predictive services,
  CoS, ...)
• Begin immediate testbed trials
• Take an iterative approach
• QoS will not be a slam dunk!

• Administrative flexibility
• Strong services for advanced apps

6
Differentiated Services

• Exploits edge/core distinction for scalability
• Applications contract for specific QoS profiles
• Policing at network periphery
• A few simple, differentiated per-hop forwarding
  behaviors (PHBs)
• Indicated in packet header
• Applied to PHB traffic aggregates
• PHBs policing rules range of services
• Clouds contract for aggregate QoS traffic
  profiles
• Policing at cloud-cloud boundary
• Supports simple, bilateral business agreements

7
DiffServ Architecture
Bandwidth Brokers (perform admissions control,
manage network resources, configure leaf and
edge devices)
Destination
Source
BB
BB
Core routers
Core routers
Ingress Edge Router (classify, police, mark
aggregates)
Egress Edge Router(shape aggregates)
Leaf Router (police, mark flows)
8
Example Diff-Serv Flavors

• Premium Service
• Emulates a leased line
• Hard bandwidth / jitter guarantee
• Assured Service
• Emulates a lightly-loaded network
• Soft bandwidth guarantee
• Olympic Service
• Gold, silver, bronze CoS
• Relative link-share assurances
• Required functional components very similar

9
Premium Service

• Emulates a leased line
• Contract peak rate profile
• PHB forward me first (e.g. priority queuing,
  WFQ)
• Policing rule drop out-of-profile packets
• On egress, clouds need to shape Premium
  aggregates to mask induced burstiness

10
Assured Service

• Emulates a lightly-loaded network
• Contract rate and burst profile
• PHB drop me last (e.g. WRED, RIO)
• Policing rule mark out-of-profile packets
• Assured traffic shares queue with BE
• Drop out-of-profile and BE packets before
  in-profile
• On cloud egress, clouds may need to shape Assured
  aggregates to mask induced burstiness

11
IETF Differential Services (DIFFSERV) Working
Group

• Current focus is narrow
• Define a small number of PHBs
• Standardize code-points in the DS-Byte (for IPv4,
  the TOS byte for IPv6, the Traffic Class octet)
• Co-chairs
• Brian Carpenter ltbrian_at_hursley.ibm.comgt
• Kathleen Nichols ltknichols_at_baynetworks.comgt
• Mailing list
• diff-serv_at_baynetworks.com

12
QBone Structure

• QBone Interoperability Group (QIG)
• Actively building pre-production interdomain
  DiffServ infrastructure
• Works on nuts-and-bolts interoperability issues
• Specific phased demonstrations of interdomain QoS
• Participation staged to keep group focused
• QBone Solutions Group (QSG)
• Broader discussion of engineering and deployment
  issues
• Includes teams that plan to join the QIG
• Focus on intradomain engineering issues
• Participation open to the Internet2 community
• I2 QoS Working Group
• Architectural guardians
• Nurture QIG and QSG

13
QBone Call for Participation

• CFP issued September 25th, 1998
• Proposals due October 16th
• Review complete October 30th
• Participant Types
• Networks
• Network Engineering / Advanced Development
• Applications and Middleware Developers
• Corporate Partners

14
QBone Networks
- Internet2 or affiliated advanced research and
education networks that agree to accelerate
deployment of key DiffServ architectural
components

• Goals
• Technical diversity Topological diversity
  Contiguity
• Proposal discussion points
• Current architecture and topology
• Future architecture and topology
• Network map identifying what will/will not be
  DiffServ-enabled
• Supported DiffServ features their placement and
  implementation

15
QBone Engineering / Advanced Development
- network engineering groups to develop tools,
techniques, architectural components AND/OR to
serve as centers of expertise and technical
support

• Technical support for developers / plumbers
• Example tools
• Bandwidth broker prototypes
• Measurement and analysis
• Admissions control algorithms
• Intradomain resource management.
• Proposal discussion points
• Tools or architectural components to be developed
• Strengths and expertise of engineering support
  team

16
QBone Applications / Middleware Development
- advanced application and QoS middleware
developers to develop or port applications or
enabling middleware that exploits new QBone
services

• Proposal discussion points
• Application's raw bandwidth requirements
• Application's QoS requirements (e.g. latency
  intolerance)
• Development platform(s)
• Relevant protocols, codecs, and middleware
  requirements (i.e. directory services,
  inter-realm authentication services)
• Testing plan

17
QBone Corporate Partners
- equipment vendors and solutions providers that
commit to assist the QBone through donations of
equipment, software, technical support, or
personnel

• Proposal discussion points
• Nature of contribution (e.g. consulting,
  hardware, software)
• Conditions (i.e. is contribution to the QBone
  project at large or to individual participants or
  participant types)

18
Review Process

• QBone Facilitation Committee (QFC)
• 13 members of the Internet2 QoS Working Group
• First, reviewed proposals individually
• Then, met in Armonk to finalize
• Principles and Guidelines
• Emphasis on forming productive partnerships/groupi
  ngs, rather than selecting/rejecting
• Small is beautiful w.r.t Phase 0 QIG
• Objective and subjective evaluations of proposals

19
Review Process (cont.)

• First, proposals evaluated against objective
  criteria
• Emphasis on time line, relevance, technical
  merit, and sincerity (committed resources)
• Then, grouped/staged in a highly subjective way
• Emphasis on staging QIG participation to meet
  stated project goals
• Diversity of DiffServ implementations
• Manageable growth rate
• Physical contiguity of network participants
• Attempted to identify other opportunities for
  collaboration

20
Submitted QBone Proposals

• 36 submitted proposals from 73 organizations
• Many excellent proposals!
• Breakdown of network proposals

International (8)
21
Phase 0 Recommendations

• 13 Proposals recommended for initial QIG
• Mostly networks teamed with applications groups
• 10 Campus
• 6 GigaPoP
• Starting two parallel groups
• Bandwidth Broker
• Assess likely timeline and direction for IETF BB
  standardization
• Possibly recommend an interim solution for QIG
• Recommend operational practices for manual BB
  instantiations
• Measurement
• Work with I2 Measurement WG to recommend a
  unified measurement infrastructure for the QBone

• 2 Backbone
• 4 International

22
Further Down the Road...
Latency assurances
Stronger services...
Crankback Route-pinning QoS Routing
More users...
More clouds...
Real
Signaling through API
BB interoperability
Scheduling
Inter-domain interoperability
23
Internet2 QoS Resources

• QoS Working Group
• Home Pagehttp//www.internet2.edu/qos/wg
• Interest Mailing Listwg-qos-interest_at_internet2.e
  du
• QBone
• Home pagehttp//www.internet2.edu/qos/qbone