1 / 11

Next Generation Network Architectures Summary

Next Generation Network Architectures Summary. John Scudder David Ward. Goal for NGNA Session. The network of 10 years from now won’t be the network of today. Our goal for this session is to consider some ideas which may influence what the Internet of the future will be.

emmet
Download Presentation

Next Generation Network Architectures Summary

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Next Generation Network ArchitecturesSummary John Scudder David Ward

  2. Goal for NGNA Session The network of 10 years from now won’t be the network of today. Our goal for this session is to consider some ideas which may influence what the Internet of the future will be. These ideas include network testbeds, new architectural proposals both incremental and radical, and improvements to existing routing protocols.

  3. Wrap-up Areas of interest from Cisco Input from researchers to Cisco

  4. Problems Cisco would like to see addressed • FRR - can classes of service have different repair domains, is hierarchical recovery possible • Unicast • Multicast • MPLS - LDP • Convergence - what is really seen on the internet, what is impact on traffic matrix • Interdomain • Current route flap analysis does not show us the rate at which the internet converges or what causes impact • Intradomain • Ways to improve leaking across summarization boundaries

  5. Problems Cisco would like to see addressed .2 • Addressing schemes • Locator vs identity for mobility and V6 • Integration of routing and services • Content/application server requiring topology awareness • for client or domain forwarding • Link routing and topology utilization information • Experience w/ metric manipulation (dead end)

  6. Problems Cisco would like to see addressed .3 • Utility of flow based routing • Need quantitative analysis that flow routing gives different routing and service treatment results than per packet • Analysis of optimized exit routing • Does it solve congestion problems? Does it look at correct parameters? • Security • Full attack tree of protocols and routers • What in routing system needs to be secured? Announcements • Src checks at borders for DDOS in interdomain system • Multicast join security, faster channel-change • Infrastructure based routing security with acceptable cost/benefit tradeoff

  7. Problems Cisco would like to see addressed .4 • High availability • Analysis of SSO techniques and failure modes • What is actual recovery time of forwarding plane (given meshiness of internet) that is visible? • Analysis of network design and # of 9’s • topology, traffic matrix, service class - uni & multicast • Traffic oscillation • Do we have other fundamental problems w/ protocols • Interdomain convergence causing oscillation • Assumptions of Hot-potato routing completely wrong? • Given what we have discussed is a better technique to keep packets within a domain as long as possible for guarantees? • Interdomain service signaling • Across borders or end to end?

  8. Problems Cisco would like to see addressed .5 • Ops • Can we infer routing policies of peers? • Can we infer traffic pattern from routing policy modeling? • Cognitive issues in policy languages • Event logs and programmable events?

  9. What do you want from Cisco? • What new data can we generate that you don’t have that would get us results • What new protocol extensions would allow you to tap protocols and/or observe impact of policy? • How can we organize ourselves? • What does the academic/research community need/want in Cisco routers/software? • Do you want to go individual per proposal or as a community?

  10. Opportunities • Future routers will have • More memory • More CPU (cores, GHz, etc) • Line-rate tunneling • Hooks into higher layers • And the kitchen sink • What can this enable? • What do you want added?

More Related