Engineering Discussion

J Bouramond, S Bradner, S Brim, S Corbato, T Gray, R Hobby, G Jackson, R Khanna, K Klingenstein, D Wasley

Burlingame CA
22 January 1997

(This presentation parallels and draws heavily on the I2 Engineering Working Group's much more detailed Preliminary Report)

---

Figure 1

---

Elements

• Applications
• Campus & Related Facilities
• Campus Networks
• Campus-to-Gigapop Connections
• Gigapops
• Inter-Gigapop Connections
• Protocols

---

Principles

• Buy rather than build.
• Open rather than closed.
• Redundancy rather than reliance.
• Basics before complexity.
• Production not experimentation.
• Services to end users, not among commercial providers.

---

Timelines

July 1997:	Initial campuses and gigapops connected Campus locations perhaps limited vBNS cloud (if pricing permits) Some QoS within gigapop communities
July 1998:	Most campuses and gigapops connected Campus accessibility widespread Cloud expanding beyond vBNS Limited QoS support
July 1999:	Most campuses and gigapops connected Campus accessibility widespread Cloud expanding beyond vBNS Limited QoS support

---

Campus Networks

• 10Mbps unshared available from desktop
• >500Mbps backbone
• (native ATM?)
• NOC instrumentation, reporting, monitoring, trouble-ticket sharing, &c.
• QoS management

---

Campus-to-Gigapop Connections

• Bandwidth rising to >150Mbps
• NOC-NOC trust & communications
• Campus responsibility

---

Figure 2

---

Gigapops

• 5-12 members
• Other networks as useful to members
• Other facilities & application-specific functionality as proves useful
• Routing and switching
• Boundaries and sorting
• NOC instrumentation, reporting, monitoring, trouble-ticket sharing, &c.
• QoS management

---

Gigapop Requirements

• Protocols
• Routing
• Speed
• Linkage
• Measurement
• Aggregation
• Technology transfer
• Eligibility
• Services
• Performance

• Network management
• Service-level monitoring
• Security
• Support for accounting experiments

---

Figure 3

---

Inter-Gigapop Connections

• Multipath, multivendor
• Transit only among I2 members
• >500Mbps
• Virtual connections
• Collective acquisition & management?

---

Cloud Requirements

• Reliability
• Capacity
• Selectable quality-of-service
• Management tools

---

Protocols

• IPv4 routing: BGP, IDRP, OSPF, I-PNNI
• IPv6 routing: I-PNNI, IDRP, BGP4+, OSPF, RIPng
• ATM routing: PNNI
• QoS signalling: RSVP

---

Quality of Service Dimensions

• Transmission speed
• Bounded delay and delay variance
• Throughput
• Schedule
• Loss rate

---

To Do

• Finish defining functional standards
• Resolve conundrums
• Upgrade campus networks
• Make gigapops
• Acquire connectivity
• Manage & monitor

---

Campus Action Items

• Plan and implement the necessary upgrades to campus network backbones and tail circuits
• Collaborate with other nearby campuses to design, fund, and implement a common gigapop
• Arrange for connectivity between the campus and the gigapop
• Provide support for users whose applications require I2 connectivity

---

Gigapop Action Items

• Organize and staff
• Identify and secure a location
• Develop a design in coordination other operators
• Acquire, install, test equipment and routing design
• Connect and test local pipes
• Connect and test pipes to other gigapops
• Establish working relationships

---

Cloud Action Items

• Organize and staff the Collective Entity
• Agree on what data and control should be available to Collective Entity network managers
• Negotiate network connectivity for the I2 cloud, beginning with vBNS but looking forward to other providers as well

---

© 1997 University of Chicago (for Internet 2)
last modified 1/22/97 GJackson