T Research Seminar on Datacommunications Software

Slides:



Advertisements
Similar presentations
Intra-Carrier Solutions Enabled by the OIF NNI Erning Ye Nortel Networks.
Advertisements

© Antônio M. Alberti 2011 Host Identification and Location Decoupling: A Comparison of Approaches Bruno Magalhães Martins Antônio Marcos Alberti.
Hierarchical Routing Architecture Introduction draft-xu-rrg-hra-00.txt Routing Research Group Xiaohu XU
IPNL: A NAT-Extended Internet Architecture Francis & Gummadi Riku Honkanen.
PROTOCOLS AND ARCHITECTURE Lesson 2 NETS2150/2850.
Protocols and the TCP/IP Suite
Data Communications Architecture Models. What is a Protocol? For two entities to communicate successfully, they must “speak the same language”. What is.
William Stallings Data and Computer Communications 7 th Edition Chapter 2 Protocols and Architecture.
Reliable Distributed Systems Naming (Communication Basics Part II) Slide set based on one by Prof. Paul Francis, Cornell University. Updated by Bina Ramamurthy.
CS335 Networking & Network Administration Tuesday April 27, 2010.
COE 342: Data & Computer Communications (T042) Dr. Marwan Abu-Amara Chapter 2: Protocols and Architecture.
Host Identity Protocol
Protocols and the TCP/IP Suite Chapter 4. Multilayer communication. A series of layers, each built upon the one below it. The purpose of each layer is.
1 A Common API for Transparent Hybrid Multicast (draft-waehlisch-sam-common-api-04) Matthias Wählisch, Thomas C. Schmidt Stig Venaas {waehlisch,
Norbert Niebert, Andreas Schieder, Henrik Abramowicz, Christian Prehofer, Holger Kart Ambient Networks projects, EU’s 6 th Framework Programme
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.1 ISP Services Working at a Small-to-Medium Business or ISP – Chapter 7.
1 Dr. Markus Hillenbrand, ICSY Lab, University of Kaiserslautern, Germany A Generic Database Web Service for the Venice Service Grid Michael Koch, Markus.
Protocols and the TCP/IP Suite
Networks – Network Architecture Network architecture is specification of design principles (including data formats and procedures) for creating a network.
William Stallings Data and Computer Communications 7 th Edition Data Communications and Networks Overview Protocols and Architecture.
Naming Examples UUID (universal unique ID) – 128 bit numbers, locally generated, guaranteed globally unique Uniform Resource Identifier (URI) URL (uniform.
Department of Electronic Engineering City University of Hong Kong EE3900 Computer Networks Introduction Slide 1 A Communications Model Source: generates.
Re-thinking Security in Network Mobility Jukka Ylitalo Ericsson Research NomadicLab NDSS '05 Workshop - February 2.
 Protocols used by network systems are not effective to distributed system  Special requirements are needed here.  They are in cases of: Transparency.
ECE 526 – Network Processing Systems Design Networking: protocols and packet format Chapter 3: D. E. Comer Fall 2008.
Semantic Network as Continuous System Technical University of Košice doc. Ing. Kristína Machová, PhD. Ing. Stanislav Dvorščák WIKT 2010.
Internetworking Concept and Architectural Model
Chapter 17 Internetworking: Concepts, Architecture, and Protocols
1 Mobility Support by the Common API for Transparent Hybrid Multicast draft-irtf-samrg-common-api-03 Project Matthias Wählisch,
William Stallings Data and Computer Communications
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009 ITU-T Kaleidoscope 2009 Innovations for Digital Inclusion Ved P. Kafle, Hideki Otsuki, and Masugi Inoue National.
CHAPTER 4 PROTOCOLS AND THE TCP/IP SUITE Acknowledgement: The Slides Were Provided By Cory Beard, William Stallings For Their Textbook “Wireless Communication.
Chapter 2 Network Models
Slide title In CAPITALS 50 pt Slide subtitle 32 pt Ambient Networks Media Delivery in the 3GPP Framework Author: Outi Koski Supervisor: Heikki Hämmäinen.
Globus and PlanetLab Resource Management Solutions Compared M. Ripeanu, M. Bowman, J. Chase, I. Foster, M. Milenkovic Presented by Dionysis Logothetis.
David Clark, Robert Braden, Aaron Falk, Venkata Pingali ACM SIGCOMM 2003 Workshops August 25&27, Jongsoo Lee
Computer Network Architecture Lecture 6: OSI Model Layers Examples 1 20/12/2012.
Computer Network Lab. 1 3 장 OSI 기본 참조 모델 n OSI : Open System Interconnection n Basic Reference Model : ISO-7498 n Purpose of OSI Model ~ is to open communication.
Uniform Resource Locator URL protocol URL host Path to file Every single website on the Internet has its own unique.
HIP-Based NAT Traversal in P2P-Environments
SDN controllers App Network elements has two components: OpenFlow client, forwarding hardware with flow tables. The SDN controller must implement the network.
The Concept of Universal Service
The OSI Model Prof. Choong Seon HONG.
Chap. 2 Network Models.
Part I. Overview of Data Communications and Networking
Scaling Data Center Networks
EA C451 Vishal Gupta.
ISO/OSI Model and Collision Domain
IoT Diagram Template IBM Cloud Architecture Center
Lecture 6: TCP/IP Networking By: Adal Alashban
Working at a Small-to-Medium Business or ISP – Chapter 7
IOS Network Model 2nd semester
Net 431: ADVANCED COMPUTER NETWORKS
Internetworking & Address Resolution
Working at a Small-to-Medium Business or ISP – Chapter 7
Protocols and the TCP/IP Suite
Data and Computer Communications by William Stallings Eighth Edition
Working at a Small-to-Medium Business or ISP – Chapter 7
IEEE MEDIA INDEPENDENT HANDOVER DCN: MISU
Lecture 6: TCP/IP Networking 1nd semester By: Adal ALashban.
Session 6 Home Network Quality of Service
OSI Model The Seven Layers
Network Layer The network layer is responsible for the source-to-destination delivery of a packet, possibly across multiple networks (links). Whereas the.
Delivering the Data.
Protocols and the TCP/IP Suite
INFORMATION FLOW ACROSS THE INTERNET
Review of Important Networking Concepts
The Internet and Electronic mail
The E.N.a.A. (Ed Needs an A) Network Bridge
Presentation transcript:

T-110.7190 Research Seminar on Datacommunications Software Presentation of the paper “Names, Addresses and Identities in Ambient Networks” (B. Ahlgren, L. Eggert, B. Ohlman, J. Rajahalme, A. Schieder) http://www.sics.se/~bengta/papers/ahlgren-din-2005.pdf Teemu Rinta-aho T-110.7190 Research Seminar on Datacommunications Software 5.10.2005 T-110.7190 Research Seminar on Datacommunications Software 26-Dec-18

Background The main objective of the Ambient Networks project is to enable seamless interoperation between heterogeneous networks The goal is to enable the vision of networking, where services and information are the focus and access and networking are transparent to the user T-110.7190 Research Seminar on Datacommunications Software 26-Dec-18

The Problem Incompatibilities between network functionality limit the usefulness of the available networks Different naming and addressing schemes Routing between heterogeneous networks T-110.7190 Research Seminar on Datacommunications Software 26-Dec-18

A Solution New naming & addressing architecture Network connectivity abstractions Names, addresses and identities Ambient Control Space functions Dynamic bindings between named entities Bridging across different addressing realms T-110.7190 Research Seminar on Datacommunications Software 26-Dec-18

Network Connectivity Abstractions Bearer Combines a sequence of flows into end-to-end connectivity primitives for applications and services Not bound to technology specific locators but higher-level entities in the naming framework Flow Abstracts away the underlying networking technology Provide a uniform view of connectivity for the ACS functions Bound to technology specific locators T-110.7190 Research Seminar on Datacommunications Software 26-Dec-18

Names, Addresses and Identities A layered entity model Focuses on the named entities and not the names used for the entities Use of multiple namespaces per layer Dynamic bindings at different layers enable the basic mobility of nodes, bearers and applications T-110.7190 Research Seminar on Datacommunications Software 26-Dec-18

Entities Application service / data object Host entity SIP services, web pages, … Connect to points of application attachment Comparable to e.g. a BSD socket Application-specific names URLs, URIs, e-mail addresses, … Host entity Connect to points of network attachment A logical entity, but comparable to a physical node attaching to a network, reachable by a network specific locator HIP-like namespace T-110.7190 Research Seminar on Datacommunications Software 26-Dec-18

Dynamic Bindings One purpose of a layered naming architecture is to provide dynamic bindings between entities at different levels With dynamic bindings, names of entities become location independent This enables different types of mobility without any add-on mechanisms Indirection and delegation can additionally support advanced mobility schemes, such as network mobility with reduced signalling T-110.7190 Research Seminar on Datacommunications Software 26-Dec-18

Bridging Across Different Addressing Realms Translation Gateways between addressing domains Common namespace Unique global names Routing between namespaces Source routing Late binding T-110.7190 Research Seminar on Datacommunications Software 26-Dec-18

Summary Presented problems are good & important It’s easy to present an abstract architecture that seems to solve the problem on paper, but how to go further… How to map to existing systems? How much does adding new naming layers affect mobility signalling and space requirements for storing the bindings? Other questions or comments? T-110.7190 Research Seminar on Datacommunications Software 26-Dec-18