1. 5 December 2000 Campus Problems & Roadblocks Group 7 Breakout Results Gang of 10 Recorded by Matt Zekauskas

2. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 2 Gang of 10 Matt Zekauskas Guy Almes Steve Corbato Joe Perches, Spirent Erik Plesset, Spirent John Streck, NC State Kevin Walsh, SDSC Ronn Ritke, NLANR Joe St Sauver, Oregon Claudia de Luna, JPL

3. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 3 Caveats Campus folks in this group were pretty happy with current campus infrastructure (all switched 10/100) => Configuration rather than bandwidth Bounced between problems & tools to solve the problems Errors/omissions/… are mine

4. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 4 Miscellaneous Problems Are not aware of advanced applications Applications developers/users not aware of application requirements (e.g., know average, not burst performance) Apps req’d to know performance of routes, but may not even monitor; No one knows performance of routes in advance

5. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 5 Problem No way to definitively find device causing loss, or duplicating frames, or… Must resort to divide & conquer

6. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 6 Problem Finding partners to do bandwidth testing or troubleshooting to perform divide & conquer Or, lack of automated, interactive, sites

7. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 7 Problem Finding topology of intermediate or remote clouds

8. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 8 Problem Disconnect between applications designers expectations and real network behavior “Network performs convolutions” Hence, belief that if works locally it must be a network problem Ignorance of platform/network specifics

9. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 9 Problem End host configuration End host CPU/bus/interface limitations “People happy to download huge software packages, but not willing to change defaults”

10. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 10 Problem Can’t get stats out of boxes we need Need correlation of performance at every level to debug problems

11. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 11 Problem ? Need separate network for control/debugging

12. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 12 Problem Need to know when tools are NOT approprate

13. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 13 Problems / QoS Easy to use, decent, bandwidth brokering scheme People too cheap to buy premium service

14. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 14 Problem Shared access links Expensive local loops (upgrading connections to BB nets and GigaPoPs)

15. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 15 Problem Lack of centralization (uniformity) Apps support folks talking to networking folks Single/Limited types of routers/switches If boxes on campus owned by many different organizations, hard to do debugging & troubleshooting

16. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 16 Problem If “five nines” reliability is a goal, hard to quickly install code to enable advanced services, it’s usually experimental and unstable

17. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 17 Problem Retention of Networking talent Hard to compete with offers that double salary and give options/equity Turnover delays ability to support advanced services & applications Causes lots of “reinventing wheel”

18. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 18 Problem Money For equipment For upgrades For people! … way network groups are funded …don’t want to always be in crisis management …must have development money

19. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 19 Problem Need CIO support, commitment

20. Group 7 Breakout: Campus Problems and Roadblocks12/5/00 20 Miscellaneous Problems IP Telephony: reliability needs too high Multicasting classes might be done better (scheduled versus on-demand) If get to rebroadcasting HDTV, lambda not enough, so will require rethinking entire infrastructure

21. www.internet2.edu