Zoltán Turányi
Abstract
We propose 4+4, a simple address extension architecture for Internet that provides an evolutionary approach to extending the existing IPv4 address space in comparison to more complex and disruptive approaches best exemplified by IPv6 deployment. The 4+4 architecture leverages the existence of Network Address Translators (NATs) and private address realms, and importantly, enables the return to end-to-end address transparency as the incremental deployment of 4+4 progresses. During the transition to 4+4, only NATs and end-hosts need to be updated and not the network routers. The 4+4 architecture retains the existing semantics of Internet names and addresses, and only proposes simple changes to the network layer that focus entirely on address extension. Encapsulation is used as the main tool to maintain backward compatibility. We present the design, implementation, and evaluation of the 4+4 architecture and discuss our implementation experiences and results from local and wide-area Internet experimentation. The 4+4 source code is freely available from the Web (comet.columbia.edu/ipv44) for experimentation.
- J. Postel, "Extensible Field Addressing," Internet RFC 730, May 1977.]] Google Scholar
Digital Library
- J. Postel, "Internet Control Message Protocol," Internet RFC 792, September 1981.]] Google ScholarDigital Library
- J. Mogul, S. Deering, "Path MTU discovery," Internet RFC 1191, November 1990.]] Google ScholarDigital Library
- Z. Wang, J. Crowcroft, "A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space Exhaustion," Internet RFC 1335, May 1992.]] Google ScholarDigital Library
- Minutes of the Address Extension by IP Option Usage BOF, proceedings of 29th IETF meeting, Seattle, April 1994.]]Google Scholar
- Minutes of the Address Lifetime Expectations working group, proceedings of 29th IETF meeting, Seattle, April 1994.]]Google Scholar
- P. Francis, "Pip Near-term Architecture," Internet RFC 1621, May 1994.]] Google ScholarDigital Library
- K. Egevang, P. Francis, "The IP Network Address Translator (NAT)", Internet RFC 1631, May 1994.]] Google ScholarDigital Library
- P. Francis "Addressing in Internetwork Protocols," PhD Thesis, University College London, available at www.ingrid.org/francis/thesis.ps.gz, September 1994.]]Google Scholar
- R. Hinden, "Simple Internet Protocol Plus White Paper," Internet RFC 1710, October 1994.]] Google ScholarDigital Library
- Y. Rekhter, B. Moskowitz, D. Karrenberg, G. de Groot, E. Lear, "Address Allocation for Private Internets," Internet RFC 1918, February 1996.]] Google ScholarDigital Library
- R. Hinden, "New Scheme for Internet Routing and Addressing (ENCAPS) for IPNG," Internet RFC 1955, June 1996.]] Google ScholarDigital Library
- I. Castineyra, N. Chiappa, M. Steenstrup, "The Nimrod Routing Architecture," Internet RFC 1992, August 1996.]] Google ScholarDigital Library
- C. Perkins, "Minimal Encapsulation within IP," Internet RFC 2004, October 1996.]] Google ScholarDigital Library
- M. O'Dell, "8+8 -- An Alternate Addressing Architecture for IPv6," Internet Draft, named as draft-odell-8+8-00, Work in progress, November 1996.]]Google Scholar
- S. Deering, R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification," Internet RFC 2460, December 1998.]] Google ScholarDigital Library
- Z. Turányi, A. Valkó, "4+4: Expanding the Internet Address Space without IPv6," Ericsson Internal Report, August 1999.]]Google Scholar
- M. Crawford, A. Mankin, T. Narten, J. Stewart, L. Zhang, "Separating Identifiers and Locators in Addresses: An Analysis of the GSE Proposal for IPv6," Internet Draft, named as draft-ietf-ipngwg-esd-analysis-05, Work in progress, October 1999.]]Google Scholar
- K. Tsuchiya, H. Higuchi, Y. Atarashi, "Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)," Internet RFC 2767, February 2000.]] Google ScholarDigital Library
- A. Gulbrandsen, P. Vixie, L. Esibov, "A DNS RR for specifying the location of services (DNS SRV)," Internet RFC 2782, February 2000.]] Google ScholarDigital Library
- B. Carpenter, "Internet Transparency," Internet RFC 2775, February 2000.]] Google ScholarDigital Library
- M. Crawford, "Router Renumbering for IPv6," Internet RFC 2894, August 2000.]] Google ScholarDigital Library
- T. Hain, "Architectural Implications of NAT," Internet RFC 2993, November 2000.]] Google ScholarDigital Library
- G. Huston, "To NAT or IPv6 -- That is the question," Satellite BroadBand magazine, available at the author's page http://www.telstra.net/gih, December 2000.]]Google Scholar
- M. Holdrege, P. Srisuresh, "Protocol Complications with the IP Network Address Translator," Internet RFC 3027, January 2001.]] Google ScholarDigital Library
- M. Gritter, D. R. Cheriton, "An Architecture for Content Routing Support in the Internet," Usenix Symposium on Internet Technologies and Systems, http://gregorio.stanford.edu/triad, March 2001.]] Google ScholarDigital Library
- P. Francis, R. Gummadi, "IPNL: A NAT-Extended Internet Architecture," SIGCOMM'01, August 2001.]] Google ScholarDigital Library
- M. Borella, J. Lo, D. Grabelsky, G. Montenegro, "Realm Specific IP: Framework," Internet RFC 3102, October 2001.]] Google ScholarDigital Library
- The IETF Next Generation Transition (ngtrans) working group, http://www.ietf.org]]Google Scholar
- Linux 2.4.x Netfilter homepage, http://www.netfilter.org]]Google Scholar
- Z. Turányi, A. Valkó, "4+4," 10th International Conference on Networking Protocols (ICNP 2002), November 2002.]]Google Scholar
- The IP4+4 project webpage at http://comet.columbia.edu/ipv44]]Google Scholar
Recommendations
Internet mobility 4×4
Mobile IP protocols allow mobile hosts to send and receive packets addressed with their home network IP address, regardless of the IP address of their current point of attachment in the Internet.While some recent work in Mobile IP focuses on a couple of ...
IPv4+4
ICNP '02: Proceedings of the 10th IEEE International Conference on Network ProtocolsThe IPv4+4 architecture presented in this paper provides an evolutionary approach to the extension of IPv4 address space. It builds on the existence of Network Address Translators(NATs) and private address realms. During and after the transition from ...
Mobile 4-in-6: A Novel Mechanism for IPv4/v6 Transitioning
IDMS '01: Proceedings of the 8th International Workshop on Interactive Distributed Multimedia SystemsMobility is indisputably one of the major drives promoting IPv6. Making the transition to IPv6 from IPv4, however, is one of the major stumbling blocks. It has recently come to light that Mobile IPv6 (the IETF routing protocol for IPv6 mobile hosts) may ...
Comments