Naming Examples UUID (universal unique ID) – 128 bit numbers, locally generated, guaranteed globally unique Uniform Resource Identifier (URI) URL (uniform.

Slides:



Advertisements
Similar presentations
© Antônio M. Alberti 2011 Host Identification and Location Decoupling: A Comparison of Approaches Bruno Magalhães Martins Antônio Marcos Alberti.
Advertisements

P2P data retrieval DHT (Distributed Hash Tables) Partially based on Hellerstein’s presentation at VLDB2004.
Why do current IP semantics cause scaling issues? −Today, “addressing follows topology,” which limits route aggregation compactness −Overloaded IP address.
Peer-to-Peer Systems Chapter 25. What is Peer-to-Peer (P2P)? Napster? Gnutella? Most people think of P2P as music sharing.
Transitioning to IPv6 April 15,2005 Presented By: Richard Moore PBS Enterprise Technology.
Auto Configuration and Mobility Options in IPv6 By: Hitu Malhotra and Sue Scheckermann.
IP Version 6 Next generation IP Prof. P Venkataram ECE Dept. IISc.
1/32 Internet Architecture Lukas Banach Tutors: Holger Karl Christian Dannewitz Monday C. Today I³SI³HIPHI³.
An Overview of Peer-to-Peer Networking CPSC 441 (with thanks to Sami Rollins, UCSB)
1 MAST and Multi6 MAST and Multi6  MAST  Multiple Address Service for Transport  draft-crocker-mast-proposal  A service to maintain locator pools Simultaneous.
 Introduction Originally developed by Open Software Foundation (OSF), which is now called The Open Group ( Provides a set of tools and.
ATP: Autonomous Transport Protocol Tamer Elsayed, Mohamed Hussein, Moustafa Youssef, Tamer Nadeem, Adel Youssef, Liviu Iftode (Poster at SIGCOMM 2003)
1 Improving Web Servers performance Objectives:  Scalable Web server System  Locally distributed architectures  Cluster-based Web systems  Distributed.
Scott Shenker and Ion Stoica Computer Science Division Department of Electrical Engineering and Computer Sciences University of California, Berkeley Berkeley,
Overlay Networks EECS 122: Lecture 18 Department of Electrical Engineering and Computer Sciences University of California Berkeley.
Anycast Jennifer Rexford Advanced Computer Networks Tuesdays/Thursdays 1:30pm-2:50pm.
Object Naming & Content based Object Search 2/3/2003.
1 Reminding - ARP Two machines on a given network can communicate only if they know each other’s physical network address ARP (Address Resolution Protocol)
P2P Over MANET An Introduction to Mobile Resource Sharing.
Vocabulary URL = uniform resource locator: web address protocol –set of rules that networked computers follow in order to share data and coordinate communications.
Peer-to-peer file-sharing over mobile ad hoc networks Gang Ding and Bharat Bhargava Department of Computer Sciences Purdue University Pervasive Computing.
1CS 6401 Peer-to-Peer Networks Outline Overview Gnutella Structured Overlays BitTorrent.
1 TCP/IP architecture A set of protocols allowing communication across diverse networks Out of ARPANET Emphasize on robustness regarding to failure Emphasize.
Towards a New Naming Architectures
Host Identity Protocol
A Layered Naming Architecture for the Internet Hari Balakrishnan, Karthik Lakshminarayanan, Sylvia Ratnasamy, Scott Shenker, Ion Stoica, Michael Walfish.
9.1. The Internet Domain Names and IP addresses. Aims Be able to compare terms such as Domain names and IP addresses URL,URI and URN Internet Registries.
Host Mobility for IP Networks CSCI 6704 Group Presentation presented by Ye Liang, ChongZhi Wang, XueHai Wang March 13, 2004.
Network Layer (3). Node lookup in p2p networks Section in the textbook. In a p2p network, each node may provide some kind of service for other.
Peer-to-Peer Overlay Networks. Outline Overview of P2P overlay networks Applications of overlay networks Classification of overlay networks – Structured.
Naming & Addressing ENUM, EPC, WINC overview JaeYoung Choi
Chapter 1: Introduction to Web Applications. This chapter gives an overview of the Internet, and where the World Wide Web fits in. It then outlines the.
An ID/locator split architecture for future networks Ved P. Kafle, Hideki Otsuki, and Masugi Inoue, National Institute of Information and Communications.
Networks – Network Architecture Network architecture is specification of design principles (including data formats and procedures) for creating a network.
Re-thinking Security in Network Mobility Jukka Ylitalo Ericsson Research NomadicLab NDSS '05 Workshop - February 2.
NUS.SOC.CS2105 Ooi Wei Tsang Application Transport Network Link Physical you are here.
Wireless Networks of Devices (WIND) Hari Balakrishnan and John Guttag MIT Lab for Computer Science NTT-MIT Meeting, January 2000.
The Inter-network is a big network of networks.. The five-layer networking model for the internet.
DNS and Naming Aditya Akella 03/16/2007 Supplemental slides.
A Layered Naming Architecture for the Internet by Hari Balakrishnan, Karthik Lakshminarayanan, Sylvia Ratnasamy, Scott Shenker, Ion Stoica, Michael Walfish.
Peer-to-Peer Name Service (P2PNS) Ingmar Baumgart Institute of Telematics, Universität Karlsruhe IETF 70, Vancouver.
The InetAddress Class Nipat J.. public class InetAddress  This class represents an Internet Protocol (IP) address.  An IP address is either a 32-bit.
IPv4/IPv6, HIP, E.164, URI/URN/URL, DOI Overviews Sep Seungjae Lee
Information-Centric Networks06b-1 Week 6 / Paper 2 A layered naming architecture for the Internet –Hari Balakrishnan, Karthik Lakshminarayanan, Sylvia.
INTERNET AND ADHOC SERVICE DISCOVERY BY: NEHA CHAUDHARY.
LNA and DOA Aditya Akella 3/11/2010. A Layered Naming Architecture for the Internet Hari Balakrishnan, Karthik Lakshminarayanan, Sylvia Ratnasamy, Scott.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
“Secure” migration to host identity based networks Kristian Slavov, Patrik Salmela Ericsson Research, NomadicLab NordicHIP
1 Peer-to-Peer Technologies Seminar by: Kunal Goswami (05IT6006) School of Information Technology Guided by: Prof. C.R.Mandal, School of Information Technology.
1 Naming for Internet MMLAB, Seongil Han
Networking Material taken mainly from HowStuffWorks.com.
Peer to Peer Network Design Discovery and Routing algorithms
Information-Centric Networks Section # 6.2: Evolved Naming & Resolution Instructor: George Xylomenos Department: Informatics.
INTERNET TECHNOLOGIES Week 10 Peer to Peer Paradigm 1.
P2P Search COP6731 Advanced Database Systems. P2P Computing  Powerful personal computer Share computing resources P2P Computing  Advantages: Shared.
1 Objectives Identify the basic components of a network Describe the features of Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6)
A Layered Naming Architecture for the Internet Authors: Balakrishnan et al. Presentation: Vinay Goel 01/14/2005 Authors: Balakrishnan et al. Presentation:
Lecture 9: Name and Directory Servers CDK4: Chapter 9 CDK5: Chapter 13 TVS: Chapter 5.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
TCP/IP Protocol Suite 1 Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Internet Protocol Version4 (IPv4)
Project JXTA By Jude Mercado.
Naming for Mobile Systems
Chapter 5 Network and Transport Layers
MAC Addresses and ARP 32-bit IP address:
A Layered Naming Architecture
Early Measurements of a Cluster-based Architecture for P2P Systems
Distributed Peer-to-peer Name Resolution
CSCI {4,6}900: Ubiquitous Computing
T Research Seminar on Datacommunications Software
Presentation transcript:

Naming Examples UUID (universal unique ID) – 128 bit numbers, locally generated, guaranteed globally unique Uniform Resource Identifier (URI) URL (uniform resource locator) – location dependent E.g., http://www.w3c.org/addressing Name resolution via DNS (Domain Name Service): URI  IP URN (uniform resource names) – location independent E.g., urn:isbn:0-390-343221-1

Naming Principles Network entities (by Saltzer) Naming issues: Services (and data) Hosts (endpoints) Network attachment points Paths (routing paths) Naming issues: Mobility Multi-homing Replication Security Scalability

Host Identity Protocol (HIP) 128-bit host identity tag (HIT) Process Process Transport <IPaddr, port> Transport <HIT, port> IP Layer HIP Layer <IPaddr> <HIT> IP Layer <IPaddr> HIT replaces IP address as a name of a system

How It Works? Client app Client app DNS library DNS Transport HIT DNS request Client app Client app DNS library DNS DNS reply = pubkey (P) send(HIT) HIT=hash(P) IPaddr Transport Transport HIP daemon 4-way authentication HIP daemon HIT HIP Layer IPaddr, P HIP layer send(IPaddr) IPsec IPsec

Layered Naming Architecture (LNA) Process Process SID↔EID <SID> Transport <IPaddr, port> Transport <EID, port> IP Layer EID↔IP <IPaddr> <EID> IP Layer <IPaddr> Should name each individually: Service identifiers (SIDs) name services/data Endpoint identifiers (EIDs) name hosts IP addresses name attachment points Ignore paths (router involvement)

How It Works? “DNS” Client app Client app SID↔EID SID↔EID LNA daemon DNS request “DNS” Client app Client app DNS reply = sid send(sid) SID↔EID eid = get(sid) SID↔EID put(sid, eid) put(eid, IP) LNA daemon DHT send(eid) Transport IP = get(eid) Transport send(eid) EID↔IP EID↔IP Intermediary (IPi) send(IPi) IP IP

Take Away Don’t bind to lower-level IDs prematurely Host mobility and renumbering (HIP) Service and data migration Resolution (binding) of name need not point to object itself, but can point to its delegate Resolution can point to intermediaries who process packets on behalf of the named target Examples HIP: one layer; IDs identify machines LNA: two layers EIDs identify machines SIDs identify everything else

UIA Naming Flat (personal group level) Resolution Routing: User can put “a user friendly” name to each device iPod.Alice, Camera.Bob Each “personal” device has a unique ID (EID) Resolution Mapping (user name  EID via log records) is disseminated whenever connectivity is available Local resolution (assuming full replication) Routing: Routing packets to the EID node?? Source routing using a P2P overlay network

Service Discovery Lots of services dispersed across the network How to find who has what services? Example systems: Jini, JXTA, SLP, UPnP, Bonjour Salutation, INS, Twine, etc..

Directory Information

Directory Architecture

Query Expressiveness

Query Routing Application level routing Network level communication DHT-based Twine, Chord, CAN, Pastry Loosely-consistent DHT JXTA, Freenet Flooding Gnutella Network level communication Unicast communication with a Central server Web-services, Napster, INS, Jini, SLP Multicast communication Jini, SLP, UPnP