1. 미래인터넷의 이동 네트워크 구조 연구 동향 한국기술교육대학교 한연희 (Youn-Hee Han) http://link.kut.ac.kr 2010.05.06

2. Contents Why FI What FI FI Research & Standardization Activities Why FI Mobility Architecture Design Principles of FI Mobility Architecture ID/Locator Separation FI Mobility Architecture Example AKARI MOFI 2/30

3. Why FI? Motivation of Future Internet (FI) The Limits and Flaws of Current Internet The Advent of New Technologies 3/30 New Technologies 1.Optical Technology - Packet Switching - Dynamic Circuit Switching 2. Cognitive Radio & Network 3. ID/Locator Split 3. Delay-Tolerant Networking 4. etc… Source: http://www.itconference.or.kr

4. Why FI? Motivation of Future Internet (FI) New Requirements to Internet  Hundred billions or more of Internet nodes Quite many sensor nodes to be connected to Internet Internet of Things (IoT)  Disruptive technologies: sensors, mobile wireless, photonics…  Dynamic network composition (or configuration) for dynamic applications (or services)  Many business models  Intelligent services  Robust, reliable, and secure service 4/30

5. Why FI? Limits and Flaws of Current Internet Scalability Problem  Bandwidth scalability From few bps to few Tbytes/sec  Distance scalability From few centimeters to millions of Kilometers  Number of nodes  Huge number of (backbone) routing table entries From few nodes to billions of nodes Manageability Problem  Troubleshooting packet loss, delay, disconnected nodes, attacks etc.  Operation vulnerable to human errors  Measurement complex 5/30

6. Why FI? Limits of Current Internet Context-awareness Problem  Contexts Location, past history, user preferences etc.  Context-aware (service, network) architecture : not supported by the current Internet Mobility Problem  Mobility was not a design criterion of Internet So many candidate technologies: Mobile IP/Proxy MIP, mSCTP, mSIP,… No Complete Mobility Transparency  Does not well support the heterogeneous networks Several physical layers  Does not support the sensor devices (and group of them) mobility  No Scalability & No Efficient Routing 6/30

7. What FI? Future Internet To design a new network beyond the current Internet Clean-slate approach would be REQURIED  Not the future (evolution) of the current Internet  But the network of the future Revolution/Innovation  The backward compatibility may or may not be required FIND (Future INternet Design)  an NSF project  49 projects (2006) / 15 projects (2007)  $15 million/year  2009 (Phase 2) ~ 7/30

8. FI Research Activities 8/30

9. FI Research Activities 9/30 FIF (Future Internet Forum - Korea) Established in 2006 to promote R&D collaborations in Future networking 5 WGs - Architecture, Wireless, Service, Testbed, Policy http://fif.kr Workshops, seminars, publications Mailing List  member@fif.kr: 포럼 전체 메일링 리스트. 공지사항 등 게시  discuss@fif.kr: 전체 토론방. 제한없는 토론 허용 미래 인터넷 캠프 (FISC, FIWC) 미래 인터넷 표준 워크숍 (FISW) 국제 컨퍼런스 (CFI - International Conference on Future Internet)

10. FI Standardization Activities 10/30 ISO/IEC JTC1 SC6 SC6 1 월 회의 : January 18–22, 2010, Barcelona, Spain SC6 10 월 회의 : October, 2010, London, UK ITU-T FG-FN Third Meeting: January 26–28, 2010, Geneva, Switzerland Fourth Meeting: March 29–April 2, 2010, Tokyo, Japan GENI GEC7: March 16-18, 2010 RENCI, Chapel Hill, NC GEC8: July 20-22, 2010 UCSD, San Diego, CA GEC9: November 9-11, 2010 NSF, Arlington, VA IETF/IRTF 77th IETF: March 21-26, 2010, Anaheim, CA, USA 78th IETF: July 25-30, 2010, Maastricht, Netherlands 79th IETF: November 7-12, 2010, Beijing, China

11. FI Standardization Activities 11/30 ISO/IEC JTC1 SC6 (Chair: Dae Young KIM) WG7 - Network and Transport Layer  Future Network (aka Future Internet)  History Initiative taken, Xian, Apr. 2007 Ad-hoc meeting on FN, Paris, Sept. 2007 NP ballot authorized, Geneva, Apr. 2008 1st meeting, Montreux, Nov. 2008 2nd meeting, Tokyo, June 2009 On-going work  ISO/IEC TR 29181 Technical Report (Editor: Myung-Ki SHIN, ETRI) Future Network: Problem Statement and Requirements Scalability, Security, Mobility, QoS, Naming & Addressing, IDs, Switching/Routing/Transport mechanisms, Heterogeneity, Virtualization, Content-centric, Context-aware, Economic…

12. FI Standardization Activities 12/30 ITU-T FG-FN (Chair: Takashi Egawa - NEC) 1st mtg, 6/29-7/3, Lulea, Sweden, /w FIRE FG-FN (Focus Group-Future Networks)  Co-Chairs: Myung-Ki SHIN (ETRI), Takashi Egawa (NEC)  Draft Documents Future Networks: Vision, Concept, and Requirements Daisuke Matsubara (Hitachi), Myung-Ki SHIN (ETRI) Framework of Network Virtualization Sangjin Jeong (ETRI), Hideki Otsuki (NICT) Identifiers and Identification processes in Future Networks Heeyoung Jung (ETRI), Takashi Egawa (NEC)

13. Why FI Mobility Architecture? 13/30 Selected Projects for FI Mobility Arch.  Japan: AKARI  Europe: 4WARD, Trilogy  U.S.: FIND, GENI

14. Why FI Mobility Architecture? 14/30 Problems of Internet (in mobile environments) Static characteristic of IP address Assumptions on link and host Host-based protocols Mobility control in the form of patch-on Integration of data and control paths User location privacy Others Source: http://www.trilogy-project.org

15. Design Principles of FI Mobility Architecture 15/30 Design Principles Mobile-oriented and Static-allowed ID-based Communication with LOC-based Routing  Separation of Identifier and Locator  Address-free User Host  Location Privacy Separation of Access Network and Backbone Network  Network-based Mobility Control  Intrinsic Route Optimization for Data Delivery  Separation of Mobility Control from Data Transport Accommodation of New Services (or Networks)  Delay Tolerant Networks (Opportunistic Networks)

16. ID/Locator Separation 16/30 Why ID/Locator Separation? Today IP addresses used for  Identifying purposes (“who”; in TCP connections)  Locating purposes (“where”; lookup routes) Intentionally designed such a overloading  To avoid a system that maps between them But, Internet has been quite complex because of the overloading feature  Complexity in Mobility Support  Complexity in (Host and Site) Multihoming Support

17. ID/Locator Separation 17/30 Name, ID, and Locator Name Identifier Locators - Human-readable (e.g., alphanumeric) - To uniquely identify a corresponding (communicating) object in the network : an object may be human, device, data, service, etc. - Cannot be memorized by humans (may be “bitstring”) - End object should be identified by ID in a secure manner - Used as control information and packet headers - Represent the location of an object in the network. - Contain the information about topological info. of an object - For efficient support of mobility and multihoming : Multiple locators per object Mapping

18. ID/Locator Separation 18/30 Possible Approach to Separation New shim-layer on hosts map between IDs and locators Use of locator is transparent to (most) applications and transport Need a new protocol to setup mapping on hosts Application Transport ID  Locator Mapping Shim Network Name Identifier Locator

19. A FI Mobility Architecture AKARI Project (2006 ~ Current) “A small light in the dark pointing to the future”  "AKARI" means "a small light" in Japanese. Goal is to build technologies for new generation network by 2015, developing a network architecture and creating a network design based on that architecture.. NWGN (New Generation Network)  Network architectures and service conditions are different from IP networks, and it may be a new paradigm. 19/30

20. AKARI - FI Mobile Architecture HNIS (HostName and Identifier System) Hostname  Examples Identifier  Self-allocating ID  fixed-length bit strings Host ID & Locators mapping  The host ID is dynamically mapped to different locators Global Locator (GLOC), Local Locator (LLOC)  For mobility Host ID is mapped to two different locators at different instances.  For multihoming Host ID is simultaneously mapped to two or more locators. 20/30 my-pc-20090915#mydomain.com sensor-temp-room-5-202#my-domain.com

21. AKARI - FI Mobile Architecture Identity Sublayer in Protocol Stack Transport and upper layers  Host ID are used for host or session identification Network layer  locators are used for finding host location and forwarding packets 21/30 Physical Data link Network Identity Physical Data link Network Host Gateway Host Link Use Locator Use Host ID Transport Application Identity Map Host ID to Locator Physical Data link Network Identity Transport Application

22. AKARI - FI Mobile Architecture Architecture Components 1) Edge networks 2) Global transit network 3) Unified logical control network  HNRs Hostname Registry  DNRs Domain Name Registry  IDRs ID Registry 4) Gateways  Two main tasks 1) translating network layer protocols or locators, 2) updating the ID/locator mapping records of IDRs 22/30 GW Local network L3 protocol/locator {LLOC} {GLOC} Global network L3 protocol/locator

23. AKARI - FI Mobile Architecture Hostname resolution process 23/30 Host2 (host2#domain2.com) Register (domain1.com, HNR{ID.LOC} Domain Name Lookup Host1 (host1#domain1.com) Register (host1, ID, LOC) 3 1 2 Query Relayed Data communication Hostname Lookup 5 domain1.com -> HNR{ID,LOC} Query: host1? Query:doamin1.com? Domain Name Registry (DNR) Host Name Registry (HNR) (HNR_MH) host1#domain1.com -> Host1{ID,LOC} - host1#domain1.com - IDs - LOCs Response: HNR_MH{ID,LOC} 4 Response: host1{ID,LOC}

24. AKARI - FI Mobile Architecture Data packet delivery 24/30 GW Host1{ID,LLOC} Host2{ID,LLOC} GW Host1 Host2{ID,LLOC} Host1{ID,LLOC} Host2 host1#domain1.com host2#domain2.com Use GLOC to route packets ID Registry (IDR) Host2{ID,GLOC,LLOC}; Host1{ID,GLOC} Host1{ID,GLOC,LLOC}; Host2{ID,GLOC} Global transit network Edge Network 1 Edge Network 2 LLOC  GLOC Host1{ID,LLOC, GLOC} Host2{ID,GLOC, GW{ID,GLOC}} Host2{ID,LLOC, GLOC} Host1{ID,GLOC, GW{ID,GLOC}}

25. AKARI - FI Mobile Architecture Procedures of Mobility Management 25/30 Correspondent Host GW_CN GW_FN Mobile Host (3) New LOC configuration (2) MH{ID,LOC} CH{ID,LOC} IDR Logical Control Network IDR_HNIDR_CN IDR_FN (1) (4) ID/LOC update Global Transit Network Foreign Network Correspondent Network Home Network GW_HN HNR_HN HNR_CH (5) (6)(7) (8)

26. A FI Mobility Architecture in Korea A New Domestic Project (2010 ~ ) 미래인터넷에서의 이동환경 및 네트워크 다양성 지원구조 연 산업원천기술개발사업 주관 및 참여 기관  ETRI & 경북대  서울대  경희대  충남대  충북대  한국기술교대  한국산업기술대 Pre-research result  MOFI (Mobile-Oriented Future Internet) – White paper  http://protocol.knu.ac.kr/MOFI/ 26/30

27. MOFI - FI Mobile Architecture Name, ID, and Locator Separation Name (e.g., NAI (Network Access Identifier)) End Host ID (EID)  128-bit fixed length Locator (LOC) 27/30

28. MOFI - FI Mobile Architecture Functional Architecture 28/30

29. MOFI - FI Mobile Architecture Data Transport Operations Mobility Control Protocol (MCP) 29/30

30. Future Research Direction DTN Support FI Mobility Architecture should incorporate DTN architecture Per-Flow Mobility Host-based vs. Network-based End Host Intelligence vs. Network Intelligence IETF Proxy MIP - fully network-based Semi-network-based? Scalability Issue 30/30