ITU-T Kaleidoscope 2009
Innovations for Digital Inclusion
An ID/Locator Split Architecture
of Future Networks
Ved P. Kafle, Hideki Otsuki, and Masugi Inoue
National Institute of Information and Communications
Technology (NICT), Japan
kafle_at_nict.go.jp
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
Presentation Layout
Background and Motivation
Related Work
Host Name and Identifier System
Network Architecture Components
Mobility, Scalable Routing Support
Implementation
Conclusion and Future Work
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
2
Background and Motivation
Use IP address as Identifier
Application
Use IP address as Locator
Transport
Application
Transport
Network
Network
Network
Data link
Data link
Data link
Physical
Physical
Physical
Host
Link
IP address functions
as both ID and Locator
Router
Link
Host
Current network demands
ID and Locator split
For mobility and multihoming:
change locators without changing
identifiers
Scalable routing, traffic engineering:
use different scoped locators,
dynamically map them
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
3
Related Work
AKARI Project: (NICT’s initiation to clean-slate design of New
Generation Network)
Includes research on ID/locator split architectures
ITU-T
Study Group 13
Y.2015 (2009): General requirements for ID/locator separation in NGN
Y.FAid-loc-split (Q.5/13), Y.ipv6split (Q.7/13)
IRTF/IETF
Routing Research Group (RRG)
developing a technical framework for ID/locator split-based routing
architectures
Host Identity Protocol (HIP) Research/Working Groups
developed a number of RFCs (5201-5205) on ID/locator split-based
host protocols for secure mobility and multihoming
SHIM6 Working Group
developing protocols to support site multihoming in IPv6
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
4
ID/locator Split Architecture Overview
Use Host ID
Application
Map Host ID to Locator
Application
Transport
Use Locator
Transport
Identity
Identity
Identity
Network
Network
Network
Data link
Data link
Data link
Physical
Physical
Physical
Host
Link
Border Router
Link
Host
Issues to be resolved:
1) Host IDs and mechanisms to generate them. (Locators can be current IP
addresses, using them only in L3 protocols)
2) Mechanisms for host ID to locator binding storage and distribution
3) Functions for host ID to locator mapping in gateways or border routers
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
5
Host Name and Identifier System
(HNIS)
Host name generation
Local hostname
Generated from feature
words
Global hostname
Combination of local
hostname and domain name
e.g. my-host#my-domain.com
Local Hostname # Domain Name
Global Hostname
Host ID formation
Generated by hashing global
hostname
Prefix Scope Version
Hash Value
Host ID
Two-layered name
resolution system
Domain Name Registry
Host Name Registry
Parameter
Hash function
Dynamic mapping
Mobility
Multihoming
Locator 1 Locator 2 …
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
Locators
Locator N
6
Host name, ID to Locator Resolution
host1#domain1.com ->
Host Name Registry
Host1{ID,LOC}
)
R
os t
h
(
r
s te 2
i
g
e
host1#domain1.com ->
Host1{IDs,LOCs}
ery
u
Q
co
ed
y
a
el
omai
Registration/Update
n1.co
Query: host1?
Domain Name
Registry (DNR)
m, H
NR { I
D.LO
1
C}
4
se
:H
os
m
m
un
ic
ter (d
Query:doamin-1.com?
t1
{I
D,
LO
C}
p
oku
at
a
Regis
Lo
me
on
(host1#domain1.com)
5D
R
(HNR)
tna
Hos
Re
sp
Host1
1
C
LO
,
, ID
D
N
3
s
Re
at
io
n
Data communication
ain
m
o
k
oo
L
e
am
po
e
ns
:H
domain1.com ->
HNR{ID,LOC}
up
{ID
R
N
C}
O
,L
Hostname resolution
Host2
(host2#domain2.com)
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
Functional entity
Mapping info
maintained
7
Network Architecture Components
Domain Name Registry (DNR)
domain1.com -> HNR{ID,GLOC}
Logical control network
Host Name Registry (HNR)
hostname -> host{ID,GLOC}
Host2{ID,GLOC,LLOC};
Host1{ID,GLOC}
ID Registry (IDR)
Host1{ID,GLOC,LLOC};
Host2{ID,GLOC}
ID Registry (IDR)
Use GLOC to route packets
Global transit network
LLoc <=> GLoc GW
GW
LLoc <=> GLoc
Edge Network 1
Host1
host1#domain1.com Host1{ID,LLOC};
Host2{ID,LLOC}
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
Edge Network 2
Host2
Host2{ID,LLOC} ;
Host1{ID,LLOC}
host2#domain2.com
8
Network Architecture Components (Cont’d)
Host, GW, Name Registry (HNR +DNR), ID Registry and Routers
are the architectural components
GWs perform L3 protocol/locator translation if
L3 protocols used in each edge network differ
L3 protocols used in edge networks and global transit network differ
Global network {GLOC}
L3 protocol/locator
GW
{LLOC}
Local network
L3 protocol/locator
Host can have in general one hostname, one or more host IDs,
and one and more locators depending the number of interfaces
and available networks
Name Registry (HNR+DNR) used for hostname resolution at the
beginning of a communication
ID Registry used for storing, updating and distributing ID to
locator and other information mappings for supporting mobility,
multihoming, and scalable routing. It can be collocated with GW.
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
9
Mobility Management
IDR_HN
IDR Logical Control Network
IDR_CN
IDR_FN
(2)
MH{ID,LOC}
(4) ID/LOC update
CH{ID,LOC}
Global Transit Network
GW_CN
GW_HN
GW_FN
(1)
(3) New LOC
configuration
Mobile Host
Home Network
Correspondent Host
Correspondent Network
Foreign Network
ID Registry (IDR) control network is used for propagating
ID/LOC mapping updates
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
10
Scalable Routing
Using different locator spaces at global transit and
edge networks
Having ID/locator mapping functions in GW
Using ID Registry to obtain or propagate ID to global
locator (GLOC) mapping records
* Approach is similar to what is
currently being discussed in IRTF RRG.
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
11
Implementation Layout
To verify the basic functions of the architecture, it is
implemented in Linux
Transport layer
Identity sublayer
State Manager
Session Manager
Signaling
Network Manager
Network layer (IPv4)
Network layer (IPv6)
Link layer
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
12
Implementation Layout (cont’d)
ID/locator split functions supporting conventional
protocol stack
Conventional IPv4/v6 applications ID/LOC split functions/applications
TCP/IP socket
IPv4
1
IPv6
2
IPv4
IPv6
TUN/TAP
TUN/TAP
Network Interfaces
TUN/TAP Ether frame exchange between conventional and
ID/LOC split applications through TUN/TAP
1 IPv4 packet sent through raw socket
2 IPv6 packet sent through raw socket
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
13
Architecture Functions Verification
DNR
HNR
RT
Transit Network RT
(IPv6)
IDR multihoming IDR
IDR
GW
GW
GW
HNR
HNR
Edge Network 1
(IPv4)
RT
Host
mobility
Edge Network 2
(IPv6)
Edge Network 3
(IPv6)
Verified basic functions for name resolution, mobility, multihoming, security
Tested mobility: session continuity while moving interface
L3 handover time = 12ms (L2 switching time = several seconds)
Tested multihoming: session continuity while changing interfaces
L3 interface switching time = 12ms
Security: encryption of control signals and data packets
OpenSSL’s RSA library used; could not cipher heavy traffic such as video promptly
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
14
Summary and Future Work
Presented the ID/locator split-based architecture of future
networks
new host name and ID system, two-layered name resolution
system
logical control network for name resolution and ID/locator mapping
updates and distribution
Verified the basic functions in a local scale testbed
As a common platform for mobility, multihoming, scalable routing,
and security
For integrating different L3 protocols (IPv4 & IPv6)
Future work
Extend and evaluate the architecture in larger scale testbed, e.g.,
over PlanetLab
Extend the logical control network functions to support mobile
routers and resource discovery in heterogeneous networks
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
15
Thank you for your attention !
Mar del Plata, Argentina, 31 Aug – 1 Sep 2009
ITU-T Kaleidoscope 2009 – Innovations for Digital Inclusion
16