IPv6网络中应用HIP和ILNP解决Multi-homing和移动IP研究与实验
摘要
随着科技日新月异的发展,人们对于网络的需求也与日俱增。从单纯的对网络速度的需求到对网络健壮性的需求,以及要求随时随地的能够接入互联网。这也就是现在非常热门的研究方向,多ISP接入网络(Multi-homing组网)和移动IP。但是创立于上个世纪80年代的TCP/IP协议并没有考虑到如此复杂环境下的通信,因此在下一代以IPv6位基础的网络中,需要进行一些额外的新增的协议来解决这些问题。
讨论产生上诉两个问题的根源,其实质是一样的。即由于IP地址身兼路由寻址和传输层标示等两大功能,因此,一旦在传输过程中IP地址发生变化将导致了传输层不能识别当前连接。针对上诉问题,互联网工程任务组(IETF)设计了主机标示协议(HIP)和标示位置网络协议(ILNP)来尝试断开传输层和网络层之间的耦合,进而从根本上解决这些问题。本文根据RFC草案[1]的建议,搭建了相应的实验环境,首次应用HIP和简化后ILNP于移动和Multi-homing环境中,设计了相关试验,验证尚在完善中的两个协议。最后,向IETF提交实验报告并发表两篇相关EI检索论文。
With the rapid changes in technology, it is also growing demand for network. Peoples'requirement grows from to the network speed to the network robustness, and requires accessing the Internet anytime and anywhere. This is now very popular research direction, multi-ISP access network (Multi-homing) and mobile IP. However, TCP/IP protocol founded in the last century does not take into account such a complex environment of communication. Therefore, in the next generation IPv6 based network, some additional new protocols are needed to address these issues.
As to the main cause of these problems, the essence is the same. That is, because IP address has two main functions such as routing and transport layer marking, changing IP addresses will lead to the transport layer does riot recognize the current connection. On solving this problem, the Internet Engineering Task Force (IETF) has designed Host Identity Protocol (HIP) and the Identifier-Locator Network Protocol (ILNP) to try to disconnect the combination between transport layer and network layer. So that Multi-homing and mobile IP problems can be solved. We built the corresponding experimental environment in our labs based on the RFC draft[1].This paper is first to implement HIP and simplified ILNP in mobile and multi-homed environment, and design relevant test to verify whether these protocals can solve problems. At last, submit reports to the IETF and published two El-searched papers.
讨论产生上诉两个问题的根源,其实质是一样的。即由于IP地址身兼路由寻址和传输层标示等两大功能,因此,一旦在传输过程中IP地址发生变化将导致了传输层不能识别当前连接。针对上诉问题,互联网工程任务组(IETF)设计了主机标示协议(HIP)和标示位置网络协议(ILNP)来尝试断开传输层和网络层之间的耦合,进而从根本上解决这些问题。本文根据RFC草案[1]的建议,搭建了相应的实验环境,首次应用HIP和简化后ILNP于移动和Multi-homing环境中,设计了相关试验,验证尚在完善中的两个协议。最后,向IETF提交实验报告并发表两篇相关EI检索论文。
With the rapid changes in technology, it is also growing demand for network. Peoples'requirement grows from to the network speed to the network robustness, and requires accessing the Internet anytime and anywhere. This is now very popular research direction, multi-ISP access network (Multi-homing) and mobile IP. However, TCP/IP protocol founded in the last century does not take into account such a complex environment of communication. Therefore, in the next generation IPv6 based network, some additional new protocols are needed to address these issues.
As to the main cause of these problems, the essence is the same. That is, because IP address has two main functions such as routing and transport layer marking, changing IP addresses will lead to the transport layer does riot recognize the current connection. On solving this problem, the Internet Engineering Task Force (IETF) has designed Host Identity Protocol (HIP) and the Identifier-Locator Network Protocol (ILNP) to try to disconnect the combination between transport layer and network layer. So that Multi-homing and mobile IP problems can be solved. We built the corresponding experimental environment in our labs based on the RFC draft[1].This paper is first to implement HIP and simplified ILNP in mobile and multi-homed environment, and design relevant test to verify whether these protocals can solve problems. At last, submit reports to the IETF and published two El-searched papers.
引文
[1]F. Baker:Implementing GSE using IPv6/IPv6 Network Address Translation, IETF draft-baker-nat66-gse-00,2008.
[2]M. Wasserman,F. Baker:IPv6-to-IPv6 Network Address Translation (NAT66),IETF draft-mrw-behave-nat66-02,2008.
[3]O'Dell, M.:GSE-An Alternate Addressing Architecture for IPv6,IETF RFC 1884, February 1997.
[4]T. Hain:Architectural Implications of NAT, IETF RFC 2993,2000.
[5]O'Dell, M.:GSE-An Alternate Addressing Architecture for IPv6,IETF RFC 1884, February 1997.
[6]Hinden, R.,Deering, S.,and E. Nordmark,"IPv6 Global Unicast Address Format",RFC 3587, August 2003.
[7]Hinden, R. and B.Haberman, "Unique Local IPv6 Unicast Addresses",RFC 4193, October 2005.
[8]Hinden, R. and S.Deering,"IP Version 6 Addressing Architecture",RFC 4291, February 2006.
[9]Van de Velde, G.,Hain, T.,Droms, R.,Carpenter, B.,and E.Klein,"Local Network Protection for IPv6", RFC 4864, May 2007.
[10]V. Fuller and T. Li. Classless Inter-domain Routing (CIDR):The Internet Address Assignment and Aggregation Plan, RFC4632.August 2006
[11]Moskowitz, R.,Nikander, P.,Jokela, P.,and T. Henderson:Host Identity Protocol, IETF RFC 5201,April 2008.
[12]Moskowitz, R. and P. Nikander:Host Identity Protocol (HIP) Architecture, IETF RFC 4423, May 2006.
[13]Nikander, P.,Henderson, T.,Vogt, C.,and J.Arkko:End-Host Mobility and Multihoming with the Host Identity Protocol,IETF RFC 5206, April 2008..
[14]Draves, R.:Default Address Selection for Internet Protocol version 6 (IPv6), IETF RFC 3484, February 2003.
[15]M. Stiemerling, J. Quittek, L. Eggert:NAT and Firewall Traversal Issues of Host Identity Protocol (HIP) Communication, IETF RFC 5207, April 2008..
[16]Draves, R.:Default Address Selection for Internet Protocol version 6 (IPv6), IETF RFC 3484, February 2003.
[17]R. Atkinson:ILNP Concept of Operations, IETF draft-rja-ilnp-intro-01 (work in progress), June 2008.
[18]R. Atkinson:Additional DNS Resource Records, IETF draft-rja-ilnp-dns-01 (work in progress), December 2008.
[19]R. Atkinson:ICMP Locator Update message, IETF draft-rja-ilnp-icmp-00 (work in progress), December 2008.
[20]R. Atkinson:Nonce Destination Option, IETF draft-rja-ilnp-nonce-01 (work in progress), December 2008.
[21]Qi Liang, Xiongyan Tang, Fred Baker,Yan Ma. Implementing HIP in IPv6/ipv6 network on solving Multi-homing, IC-BNMT2009,2009.10
[22]Zhangyi Yuan, Yan Ma, Fred Baker, Xiaohong Huang, Xiaodong Zhang. The implementation of NAT66 and the solutions of Multi-homing in NAT66 environment. IC-BNMT2009,2009.10
[23]Thomas F.Herbert and Charles River Media. The Linux TCP/IP Stack: Networking for Embedded Systems.2004
[24]Robert Love著,陈莉君、康华、张波等译,Linux内核设计与实现,机械工业出版社,2006年1月
[25]Douglas E.Comer著,林瑶、蒋慧、杜蔚轩等译,谢希仁审校《用TCP/IP进行网际互连第一卷：原理、协议与结构》,第四版,2003年1月
[2]M. Wasserman,F. Baker:IPv6-to-IPv6 Network Address Translation (NAT66),IETF draft-mrw-behave-nat66-02,2008.
[3]O'Dell, M.:GSE-An Alternate Addressing Architecture for IPv6,IETF RFC 1884, February 1997.
[4]T. Hain:Architectural Implications of NAT, IETF RFC 2993,2000.
[5]O'Dell, M.:GSE-An Alternate Addressing Architecture for IPv6,IETF RFC 1884, February 1997.
[6]Hinden, R.,Deering, S.,and E. Nordmark,"IPv6 Global Unicast Address Format",RFC 3587, August 2003.
[7]Hinden, R. and B.Haberman, "Unique Local IPv6 Unicast Addresses",RFC 4193, October 2005.
[8]Hinden, R. and S.Deering,"IP Version 6 Addressing Architecture",RFC 4291, February 2006.
[9]Van de Velde, G.,Hain, T.,Droms, R.,Carpenter, B.,and E.Klein,"Local Network Protection for IPv6", RFC 4864, May 2007.
[10]V. Fuller and T. Li. Classless Inter-domain Routing (CIDR):The Internet Address Assignment and Aggregation Plan, RFC4632.August 2006
[11]Moskowitz, R.,Nikander, P.,Jokela, P.,and T. Henderson:Host Identity Protocol, IETF RFC 5201,April 2008.
[12]Moskowitz, R. and P. Nikander:Host Identity Protocol (HIP) Architecture, IETF RFC 4423, May 2006.
[13]Nikander, P.,Henderson, T.,Vogt, C.,and J.Arkko:End-Host Mobility and Multihoming with the Host Identity Protocol,IETF RFC 5206, April 2008..
[14]Draves, R.:Default Address Selection for Internet Protocol version 6 (IPv6), IETF RFC 3484, February 2003.
[15]M. Stiemerling, J. Quittek, L. Eggert:NAT and Firewall Traversal Issues of Host Identity Protocol (HIP) Communication, IETF RFC 5207, April 2008..
[16]Draves, R.:Default Address Selection for Internet Protocol version 6 (IPv6), IETF RFC 3484, February 2003.
[17]R. Atkinson:ILNP Concept of Operations, IETF draft-rja-ilnp-intro-01 (work in progress), June 2008.
[18]R. Atkinson:Additional DNS Resource Records, IETF draft-rja-ilnp-dns-01 (work in progress), December 2008.
[19]R. Atkinson:ICMP Locator Update message, IETF draft-rja-ilnp-icmp-00 (work in progress), December 2008.
[20]R. Atkinson:Nonce Destination Option, IETF draft-rja-ilnp-nonce-01 (work in progress), December 2008.
[21]Qi Liang, Xiongyan Tang, Fred Baker,Yan Ma. Implementing HIP in IPv6/ipv6 network on solving Multi-homing, IC-BNMT2009,2009.10
[22]Zhangyi Yuan, Yan Ma, Fred Baker, Xiaohong Huang, Xiaodong Zhang. The implementation of NAT66 and the solutions of Multi-homing in NAT66 environment. IC-BNMT2009,2009.10
[23]Thomas F.Herbert and Charles River Media. The Linux TCP/IP Stack: Networking for Embedded Systems.2004
[24]Robert Love著,陈莉君、康华、张波等译,Linux内核设计与实现,机械工业出版社,2006年1月
[25]Douglas E.Comer著,林瑶、蒋慧、杜蔚轩等译,谢希仁审校《用TCP/IP进行网际互连第一卷：原理、协议与结构》,第四版,2003年1月