90 likes | 198 Views
Meta Architecture : A New Narrow Waist for Future Internet Hourglass. Myung-Ki Shin , mkshin@etri.re.kr Eun Kyoung Paik, euna@kt.com JinHyeock Choi, jinchoe@samsung.com May 30 2008. Problem Statement (1/2). Basic Problems Routing failures and scalability Insecurity Mobility
E N D
Meta Architecture :A New Narrow Waist for Future Internet Hourglass Myung-Ki Shin, mkshin@etri.re.kr Eun Kyoung Paik, euna@kt.com JinHyeock Choi, jinchoe@samsung.com May 30 2008
Problem Statement (1/2) • Basic Problems • Routing failures and scalability • Insecurity • Mobility • Quality of service • Heterogeneous physical layers, applications, and architecture • IP = Narrow Waist of Hourglass • Network management • Congestive collapse • Opportunistic and fast long-distance communications • Economy and policy
Problem Statement (2/2) • Problems with Original Design Principles • Packet switching • End-to-end argument • Layering
Solution - Building Blocks • Meta architecture (diverse architecture) • Architecture • Mechanism • Service/ applications
Internet versus Future Internet TCP/IP – single architecture Multiple, heterogeneous architectures Applications Application #1 Application #2 Application #N TCP/UDP Transport & Network #1 Transport & Network #2 Transport & Network #N ….. IP Link & Physical #1 Link & Physical #2 Link & Physical #N Link Physical • Today’s Internet : • Architecture – TCP/IP • Mechanism – SNMP, IPsec … • Application – Web, E-mail … • Future Internet : • Architecture 1– Internet (TCP/IP), 2- Sensor (Intermittent X), …. • Mechanism – SNMP, IPsec, Cognitive, Cooperative, • Application – Web, E-mail, Sensor, Vehicle/aircraft, Satellite
Today’s Internet Narrow Waist for Internet Hourglass (Common Layer = IP)
Future Internet Heterogeneous Architecture & User Services Virtualization Cross-layer Comm. Diverse E2E A New Narrow Waist for Future Internet Hourglass (Common Layer = Meta Architecture) Meta Architecture Heterogeneous Infrastructure & Physical Layer
Principles for Meta Architecture • Network virtualization • Cross-layer communications • Diverse end-to-end (IP or non-IP) arguments
Requirements • Multiple architecture support • Network (router/host) virtualization, server clustering • Identity, Resource specification (Rspec) • Programmability • Architecture federation • Control and (distributed) management plane