Transcript pptx - AsiaFI

Design and Implementation of Mapping
Systems for an ID/Locator Split Protocol
for New Generation Network
Sho Kanemaru (Keio University, Japan)
Kazuma Yonemura (Keio University, Japan)
Fumio Teraoka (Keio University, Japan)
2011/08/12
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
1
Outline
• Background
• Z Network Protocol (ZNP)
– Internetworking with a Common ID Space
– Name, ID, Locator
• Mapping Systems of ZNP
–
–
–
–
–
–
–
Mappings in ZNP
Hierarchical Mapping Systems
Features of Mapping Systems
Data Structure of Mappings
Zone File Examples
ZCMP Messages
Signaling Examples
• Implementation
• Future Work
• Conclusion
2011/08/12
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
2
Background
• “Clean Slate” approach
– Aims at redesign of the Internet
– AKARI Project proposes a new
network architecture called Z
Network Architecture (ZNA)
• One of the features of ZNA is
ID/Locator Split
– Features
• Layer 3 protocol heterogeneity
• mobility
• multihoming
Z Network Architecture[Teraoka:2009]
L4
• Z Network Protocol (ZNP)
– Network layer protocol of ZNA
– Designed to satisfy
requirements for practical
operation
2011/08/12
Identifier
L3
mapping
Locator
L2
Locator
ID sublayer
Forwarding
sublayer
ID/Locator Split Architecture
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
3
Z Network Protocol (ZNP)[Kanemaru:ICC2011]
• Designed to satisfy the four requirements in terms of practical
operation
–
–
–
–
Req.(1) Heterogeneity of network layer protocols
Req.(2) Scalability of ID/Locator mapping systems
Req.(3) Independence of mapping information management
Req.(4) Avoidance of locator leakage beyond the administrative
boundary
• We also designed Z Control Message Protocol (ZCMP) to manipulate
the mapping systems.
– Designed as an application layer protocol.
• Features of ZNP
– Internetworking with a Common ID Space
– Hierarchical mapping systems: NMS and IMS
S. Kanemaru and F. Teraoka, “ZNP: A Network Layer Protocol Based on ID/Locator Split
Considering Practical Operation”, In Proc. of IEEE International Conference on Communications
(ICC2011), 6 pages, Jun. 2011
2011/08/12
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
4
Internetworking with a Common ID Space
• Various networks connect to ZNP Network
– Assume NAT-like environment (PU-Net)
– Legacy Networks connect via the protocol conversion gateway (L-Net)
• Node can communicate as long as it knows the ID of the target
node
– Each node is assigned the locator of the network to which it connects
– Difference of locator types are transparent to upper layers
upper layer
Global Universal Network
(backbone network)
Common ID space
IPv4
IPv6
ZNP Loc
GU-Nets
(edge
networks)
PU-Nets
(edge
networks)
Universal Locator Space
L-Nets
(edge
networks)
Local Locator Space
Assumed Network in the future Internet
2011/08/12
other
L3 protocol heterogeneity (Req. (1))
GU-Net: Global Universal Network
PU-Net: Private Universal Network
L-Net: Local Network
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
5
Mappings in ZNP
• Name
Name
– FQDN style
– Hierarchical structure
name-to-ID mapping
ID
• ID
– 128 bits
– Hierarchical structure
• Locator
– Various types
• ZNP Locator, IPv4, IPv6…
• We propose the mapping
systems of ZNP
– Designed to satisfy “the four
requirements” (Req.(1)-(4))
2011/08/12
Node_X.unet.jp.
101:100:1::1
ID-to-Locator mapping
2001:db8:1::1
Locator
192.168.0.1
2 bytes
4 bytes
10 bytes
Registry Organization
Node Identifier
Identifier
Identifier
- Regional Internet Registry number
- National Internet Registry number
- etc.
ID format
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
6
Hierarchical Mapping Systems
• Name Mapping System
(NMS)
– Manages the name-to-ID
mappings
– Consists of Name Mapping
Agents (NMAs)
– Hierarchy of the NMS is
based on the structure of the
name
root NMA
IMA APNIC
...
jp. NMA
IMA
unet.jp(GU-Net)
NMA
...
pnet.jp.(PU-Net)
IMA
...
NMA
L-NMA
...
• ID Mapping System (IMS)
– Manages the ID-to-Locator
mappings
– Consists of ID Mapping
Agents (IMAs)
– Hierarchy of the IMS is based
on the structure of the ID
2011/08/12
JPNIC
2 bytes
4 bytes
global
space
IMA
L-IMA local/
private
...
space
10 bytes
Registry Organization
Node Identifier
Identifier
Identifier
- Regional Internet Registry number
- National Internet Registry number
- etc.
ID format
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
7
Features of Mapping Systems
• IMS can manage mappings of
ID to various types of locators
– Satisfies L3 protocol
heterogeneity (Req.(1))
• Introduce the tree structure
– Satisfies scalability (Req.(2))
– Satisfies independence of
mapping information
management (Req.(3))
• Introduce the Local NMA/Local
IMA in PU-Net and L-Net
– Satisfies avoidance of locator
leakage (Req.(4))
2011/08/12
mapping
Identifier
Locator
Locator
Locator
(ZNP)
(IPv4)
(IPv6)
L3 protocol heterogeneity (Req.(1))
<GU-Net>
<L-Net (IPv4)>
L-IMA IMA
locator of
IPv4 address
gateway
of server
request
request
server’s server’s
locator
locator
nodeB
nodeA
gateway
server
avoidance of locator leakage (Req.(4))
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
8
Data Structure of Mappings
• The mapping information is expressed as the
Resource Records
– Composed of the Label, the Record Type, and the
Resource Data
2011/08/12
Record Type
Label
Resource Data
rID
host name
rID
pID
host name
pID
NMA
domain name
rID of NMA
IMA
ID
rID of IMA
LOC
ID
Locator
PTR
ID
host name
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
9
Zone File Examples
• Resource Records are described in the zone file
– Configuration file of Mapping Agents
Zone file of NMA (unet.jp)
<Label> <Record Type> <Resource Data>
Node_A
rID
101:100::3
Node_B
rID
101:100::4
sub
NMA
101:100:1::5
101:100::
IMA
101:100::2
101:100::2 LOC
2001:db8::2
101:100:1::5 LOC
2001:db8:1::5
Zone file of IMA (unet.jp)
<Label> <Record Type> <Resource Data>
101:100::3 LOC
2001:db8::3
101:100::4 LOC
2001:db8::4
101:100:1:: IMA
101:100:1::6
101:100:1::6 LOC
2001:db8:1::6
2011/08/12
IMA
NMA
(unet.jp) (unet.jp)
unet.jp
ID - 101:100::
LOC - 2001:db8::/48
④
③
Node_A.unet.jp Node_B.unet.jp
sub.unet.jp
ID - 101:100:1::
LOC - 2001:db8:1::/64
IMA
NMA
(sub.unet.jp) (sub.unet.jp)
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
10
Signaling Examples
• 2 examples
(1) Intra GU-Net
(2) GU-Net to L-Net
GU-Net: Global Universal Network
PU-Net: Private Universal Network
L-Net: Local Network
Global Universal Network
(backbone network)
(1)
GU-Nets
(edge
networks)
PU-Nets
(edge
networks)
Universal Locator Space
2011/08/12
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
(2)
L-Nets
(edge
networks)
Local Locator Space
11
Signaling Example: Intra GU-Net
NMA NMA
IMA
IMA
(JPNIC) (APNIC) Root NMA (jp) (unet2.jp)
IMA
(unet2.jp)
11 10 9
12
2
3
IMA
(unet1.jp)
4
NMA
(unet1.jp)
0
resolves
1 5
8, 13 0
resolves Node_Y’s
6
Node_X’s locator
ID and IMA’s locator
7
from Node_X’s ID
from Node_Y’s name
14
(to make sure Node_Y.unet2.jp
Node_X.unet1.jp
ID-to-Locator
ZCMP Messages
resolves
mapping of
ID Request/Reply
Node_Y’s locator
Node_X)
Loc Request/Reply
from Node_Y’s ID
Data Communication
Loc Reg Request/Reply
2011/08/12
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
12
Signaling Example: GU-Net -> L-Net
<IPv4 L-Net (lnet.jp)>
<GU-Net (unet.jp)>
IMA
requests Node_Y’s locator
(lnet.jp)
mapping_cache
from Node_Y’s ID
(lnet.jp)
4
→ resolves GU-Loc-gw
resolves
NMA
IPv4_Node_Y
(unet.jp)
2
5
3
from Node_Y’s ID
protocol
1
conversion
Node_Y.lnet.jp
ZCMP Message
gateway
Node_X.unet.jp
ID Request/Reply
resolves Node_Y’s ID
Loc Request/Reply
from Node_Y’s name
L-IMA
(lnet.jp)
Data Communication
ZNP Header (proc.5)
IPv4
header
2011/08/12
ZNP Header (proc.3)
Src Loc : IPv4_gw
Src Loc : GU-Loc_Node_X
Dst Loc : IPv4_Node_Y
Dst Loc : GU-Loc_gw
Src ID : ID_Node_X
Src ID : ID_Node_X
Dst ID : ID_Node_Y
Dst ID : ID_Node_Y
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
13
Implementation
• Finished Implementing ZNP and ZCMP in the user
space
– NMA and IMA are implemented as nmad and imad.
• These modules exchange packets with znpd which is an
implementation of ZNP in user space
PU-Net (L-Net)
GU-Net
mapping_cache
pznpd
znpd
gateway / mapping_cache
2011/08/12
nmad
imad
znpd
NMA / IMA
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
PF_LOCAL socket
PF_INET socket
14
Future Work
• Implement the functions of ZNP into Linux kernel
– Use Linux-2.6.18
– Add the new protocol family called PF_ZNET into Linux
kernel
• Modify the implementation of mapping systems
– Interfaces between mapping systems and ZNP-kernel
UDP
TCP
IPv4
IPv6
ZNP
Ethernet IEEE802.xx
Protocol stack in the kernel
2011/08/12
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
15
Implementing functions (normal node)
Transport Layer (UDP) udp_rcv()
udp_sendmsg()
znp_output()
only gw znp_convert()
Network
Layer
znp_input()
znp_forward()
znp_l3_output()
dev_queue_xmit()
Datalink Layer
ZNP node in the ZNP network
Transport Layer (UDP)
Network
Layer
udp_rcv()
udp_sendmsg()
znp_input2()
znp_output()
ip_proto->handler()
ip_queue_xmit()
Datalink Layer
ZNP node in the Legacy Network (IPv4 network in this example)
2011/08/12
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
16
Implementing functions (gateway between
ZNP network and IPv4 network)
Transport
Layer (UDP)
udp_rcv()
udp_sendmsg()
znp_output() znp_convert()
udp_sendmsg()
udp_rcv()
znp_output()
znp_input2()
Network
Layer
znp_input()
znp_l3_output()
ip_queue_xmit() ip_proto->handler()
Datalink
Layer
2011/08/12
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
17
Conclusion
• We are proposing Z Network Protocol (ZNP)
– Designed to satisfy “the four requirements” considering practical
operation
•
•
•
•
Req.(1) Heterogeneity of network layer protocols
Req.(2) Scalability of ID/Locator mapping systems
Req.(3) Independence of mapping information management
Req.(4) Avoidance of locator leakage beyond the administrative boundary
• Mapping Systems of ZNP is also designed to satisfy “the four
requirements”
– IMS can manage mappings of ID to various types of locators (for
Req.(1))
– Introducing the tree structure (for Req.(2), (3))
– Introducing the Local NMA/Local IMA in PU-Net and L-Net (for Req.(4))
• Future Work
– Implementing the function of ZNP in Linux kernel
– Confirm the basic function of ZNP kernel
2011/08/12
AsiaFI Future Internet Architecture Workshop @ Daejeon Korea
18