Service Delivery to Campus

1
Service Delivery to Campus

• Patrick Christian
• University of Wisconsin
• October 12, 2006

2
Outline

• What is OmniPoP?
• OmniPoP services
• (some) WAN to RON/GigaPoP Issues
• (some) RON/GigaPoP to Campus Issues

3
What is OmniPoP? (RONs)
BOREAS-Net
WiscWaves BOREAS-Net
MiLR
BOREAS-Net
PSU-Net
I-WIRE ICCN
TFN
I-Light
4
What is OmniPoP? (Participants)

• University of Chicago
• University of Illinois (UIUC UIC)
• Indiana University
• University of Iowa
• University of Michigan
• Michigan State University
• University of Minnesota
• Northwestern University
• Ohio State University
• Purdue University
• University of Wisconsin - Madison

5
What is OmniPoP?
6
What is OmniPoP?

• High-level description/goals
• GigaPoP of GigaPoPs (at StarLight)
• Sharing of common infrastructure in Chicago
  (reduced control vs. performance/cost value)
• Production service/support only
• Aggregation of participants to various networks
  (e.g. NLR, Internet2-NewNet)

7
OmniPoP Services

• Services
• Layer 2 Ethernet switch (F10) in production today
• Considering Layer 3 (perhaps) Layer 1
  (partnership?)
• Layer 2 service
• Private p2p 1/10GE services for members (ports
  for private purposes)
• (today) Production 10GE trunks to various
  networks
• Individual member 802.1q VLANs terminate on
  member L2/L3 equipment at campus with various
  network provider
• Best effort service (statistical multiplexing) w/
  no rate limits on VLANs

8
(some) WAN to RON/GigaPoP Issues

• VLAN coordination/duplication
• Campus duplication of VLAN RON/GigaPoP VLANs
• OmniPoP developed VLAN plan (attempting to avoid
  MREN/StarLight, NLR utilized VLAN blocks)
• P2P VLAN assignments for member interconnects in
  2500 range
• (802.1ad, registry?)
• Oversubscription of 10GE trunks
• Broadcast storms
• Actual traffic flows (e.g. NewNet routed service
  peering)
• Proliferation of port utilization for different
  service types
• Dedication of unutilized capacity for different
  service types (value proposition)
• Service definitions how RON/GigaPoP needs to
  (not?) be engaged
• change our service model (gatekeeper/gateway?)
• Deterministic vs. best effort
• Manual/managed/dynamic provisioning

9
RON/GigaPoP to Campus Issues

• Campus handoff
• Economics, technology politics tend to
  determine how RON/GigaPoP connection gets to
  campus lab
• Fiber extension of DWDM system
• Scalability, redundancy, manual intervention,
  support
• Interconnect to campus infrastructure
• Sufficient (excess?) capacity, support,
  automation
• (some) Software provisioning options
  (interop/selection?)
• (dynamic) DRAGON GMPLS L1-L3 provisioning
• (managed) UCLP software L1 provisioning
• (managed) U-Wisc (AANTS) campus (or others?) L2
  provisioning
• (managed) OSCARS L2.5/3 control plane
  provisioning
• (ultimately) Understand process then automate
  it particularly if we extend concepts from WAN
  to RON/GigaPoP and ultimately into campus network

10
Thank You