1 / 18

Sho Kanemaru (Keio University, Japan) Kazuma Yonemura (Keio University, Japan)

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). Outline. Background Z Network Protocol (ZNP )

chun
Download Presentation

Sho Kanemaru (Keio University, Japan) Kazuma Yonemura (Keio University, Japan)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Design and Implementation of Mapping Systems for an ID/Locator Split Protocol for New Generation Network Sho Kanemaru (Keio University, Japan) KazumaYonemura (Keio University, Japan) Fumio Teraoka (Keio University, Japan) AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  2. 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 AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  3. 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 Protocol (ZNP) • Network layer protocol of ZNA • Designed to satisfy requirements for practical operation Z Network Architecture[Teraoka:2009] L4 Identifier ID sublayer L3 mapping Forwarding sublayer Locator Locator L2 ID/Locator Split Architecture AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  4. 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 alsodesignedZ 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 AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  5. 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 ZNPLoc other GU-Nets (edge networks) L-Nets (edge networks) PU-Nets (edge networks) L3 protocol heterogeneity (Req. (1)) GU-Net: Global Universal Network PU-Net: Private Universal Network L-Net: Local Network Universal Locator Space Local Locator Space Assumed Network in the future Internet AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  6. Mappings in ZNP 4 bytes 10 bytes 2 bytes Organization Identifier Node Identifier Registry Identifier • Name • FQDN style • Hierarchical structure • 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)) Name Node_X.unet.jp. name-to-ID mapping ID 101:100:1::1 • Regional Internet Registry number • National Internet Registry number • etc. ID-to-Locator mapping 2001:db8:1::1 192.168.0.1 Locator ID format AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  7. Hierarchical Mapping Systems 4 bytes 10 bytes 2 bytes Organization Identifier Node Identifier Registry Identifier • 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 • 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 root NMA APNIC IMA jp. . . . NMA JPNIC IMA • Regional Internet Registry number • National Internet Registry number • etc. pnet.jp.(PU-Net) unet.jp(GU-Net) global space IMA NMA IMA NMA local/ private space . . . . . . L-IMA L-NMA . . . . . . ID format AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  8. 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)) Identifier mapping Locator (ZNP) Locator (IPv4) Locator (IPv6) L3 protocol heterogeneity (Req.(1)) <GU-Net> <L-Net (IPv4)> L-IMA IMA IPv4 address of server locator of gateway request server’s locator request server’s locator server gateway avoidance of locator leakage (Req.(4)) nodeA nodeB AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  9. Data Structure of Mappings • The mapping information is expressed as the Resource Records • Composed of the Label, the Record Type, and the Resource Data AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  10. Zone File Examples • Resource Records are described in the zone file • Configuration file of Mapping Agents unet.jp ID - 101:100:: LOC - 2001:db8::/48 IMA (unet.jp) NMA (unet.jp) Zone file of NMA (unet.jp) sub.unet.jp ID - 101:100:1:: LOC - 2001:db8:1::/64 <Label> <Record Type> <Resource Data> Node_ArID 101:100::3 Node_BrID 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::5LOC 2001:db8:1::5 Node_A.unet.jp Node_B.unet.jp ④ ③ NMA (sub.unet.jp) IMA (sub.unet.jp) 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 AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  11. 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) (2) (1) GU-Nets (edge networks) L-Nets (edge networks) PU-Nets (edge networks) Universal Locator Space Local Locator Space AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  12. Signaling Example: Intra GU-Net 11 3 10 4 2 9 Node_Y.unet2.jp Node_X.unet1.jp NMA (unet2.jp) IMA (APNIC) IMA (JPNIC) NMA (jp) resolves Node_X’s locator from Node_X’s ID (to make sure ID-to-Locator mapping of Node_X) resolves Node_Y’s ID andIMA’s locator from Node_Y’s name 12 Root NMA IMA (unet2.jp) NMA (unet1.jp) IMA (unet1.jp) 0 1 8, 13 0 5 6 ZCMP Messages 7 resolves Node_Y’s locator from Node_Y’s ID ID Request/Reply Loc Request/Reply Data Communication Loc Reg Request/Reply 14 AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  13. Signaling Example: GU-Net -> L-Net <IPv4 L-Net (lnet.jp)> <GU-Net (unet.jp)> requests Node_Y’s locator from Node_Y’s ID → resolvesGU-Loc-gw 4 resolves IPv4_Node_Y from Node_Y’s ID 2 5 mapping_cache (lnet.jp) 3 protocol conversion gateway 1 Node_Y.lnet.jp Node_X.unet.jp IMA (lnet.jp) NMA (unet.jp) L-IMA (lnet.jp) ZCMP Message resolves Node_Y’s IDfrom Node_Y’s name IPv4 header ID Request/Reply Loc Request/Reply Data Communication AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  14. 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 nmad imad PF_LOCALsocket PF_INET socket pznpd znpd znpd gateway / mapping_cache NMA / IMA AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  15. Future Work • Implement the functions of ZNP into Linux kernel • UseLinux-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 IPv6 IPv4 ZNP IEEE802.xx Ethernet Protocol stack in the kernel AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  16. Implementing functions (normal node) udp_rcv() Transport Layer (UDP) udp_sendmsg() znp_output() znp_convert() only gw Network Layer znp_forward() znp_input() znp_l3_output() dev_queue_xmit() DatalinkLayer ZNP node in the ZNP network udp_rcv() udp_sendmsg() Transport Layer (UDP) znp_input2() znp_output() Network Layer ip_proto->handler() ip_queue_xmit() DatalinkLayer ZNP node in the Legacy Network (IPv4 network in this example) AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  17. Implementing functions (gateway between ZNP network and IPv4 network) Transport Layer (UDP) udp_rcv() udp_rcv() udp_sendmsg() udp_sendmsg() znp_output() znp_convert() znp_input2() znp_output() Network Layer ip_proto->handler() ip_queue_xmit() znp_l3_output() znp_input() Datalink Layer AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

  18. 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 AsiaFI Future Internet Architecture Workshop @ Daejeon Korea

More Related