Transcript ppt - MMLab

Naming for Internet
2005. 9. 12.
MMLAB, Seongil Han
[email protected]
1
Contents


Overview
A layered Naming Architecture for the
Internet

Intentional Naming System (INS)

Problems

Conclusion
-2-
Overview

What is naming??

Name


For what?


<noun> a word or words by which an
individual person, place or thing is identified
and referred to
Data, object, service, and so on
In Internet

DNS, IP
-3-
Contents


Overview
A layered Naming Architecture for the
Internet

Intentional Naming System (INS)

Problems

Conclusion
-4-
Current naming (DNS)
www.goolgle.co.kr
66.249.89.99
DNS
www.google.co.kr

I want to use the
search engine of
google
Application
2 reference

Transport
Network
Data link
Physical

You should
communicate that
host with
66.249.89.99 among
several service
providing hosts
And in 66.249.*.*
network
-5-
New Architecture

Design principle #1


Names should bind protocols only to the
relevant aspects of the underlying
structure; binding protocols to irrelevant
details unnecessarily limits flexibility and
functionality
DNS system is violated
-6-
New Architecture

Decouple I



The name of data or service
The endpoint hosting the data or service
Decouple II


The endpoint that I communicate with
Its network location (IP address)
-7-
New Architecture

Service identifier

Application
SID
Transport

Endpoint identifier
Network
EID

Data link
Physical

Only represents the service
or data (not host / endpoint)
Only represents the host (or
endpoint) (not its location)
Two resolution


SID → (EID,transport,port)
EID → IP addresses
-8-
The Naming Layers
User-level descriptors
(e.g., search)
App-specific search/lookup
returns SID
Use SID as handle
App session
Application
App session
Resolves SID to EID
Opens transport conns
Bind to EID
Transport
Transport
Resolves EID to IP
IP
IP hdr EID TCP SID …
IP
New Namespace

Design principle #2

Names, if they are to be persistent,
should not impose arbitrary restrictions
on the elements to which they refer

DNS, IP are violated

2 approaches


Genre (e.g. URN)
Flat namespace
-10-
Flat namespace

How implement??

DHT



O(log n) resolution time → problem
Various solutions
The disadvantage



Not pay-for-your-own model
Why trust
cf) RSP
-11-
Contents


Overview
A layered Naming Architecture for the
Internet

Intentional Naming System (INS)

Problems

Conclusion
-12-
INS is ..

Intentional Naming System


Resource discovery and service location
system for dynamic and mobile networks
of devices and computers
Key features




Focus on ‘what’, not ‘where’
Early, late binding
Application-controlled metric support
Easy deployment on current internet
-13-
New Architecture
Early binding
client
DATA INR networks
(Intentional Naming Router)
service
network location
Intentional name
INR
service
service
-14-
New Architecture
service
data
INR
Intentional name + data
service
client
Intentional anycast
service
-15-
New Architecture
service
INR
Intentional name + data
service
Intentional multicast
client
service
-16-
New Architecture
service
Announcing
an
intentional name
INR
query
service
client
names
Discovering
Intentional name
service
-17-
New naming

Intentional name

Name-specifiers : attribute-value pair



Wild-card (*)
Range matching
Example


[city=washington [building=whitehouse
[wing=west]]]
[service=camera [data-type=picture
[format=jpg]] [resolution=640x480]]
-18-
Name tree
root
Orthogonal attributes
city
service
accessibility
washington
camera
public
building
data-type
resolution
whitehouse
picture
640X480
wing
west
Name-record
-19-
Problems

New architecture



Development and deployment is too
difficult
Scalability and transition should be
significantly considered
New namespace

Flat namespace


Ultimate destination, but serious and many
challenges
Security
-20-
Conclusion


New paradigm is prepared and
appeared by many humans or
organizations nowadays
In internet, the change and challenge
about naming are needed


Ubiquitous computing, mobility support,
security, and so on
We need to consider this sufficiently
-21-