Abstract
Network address translation model (NAT) has been viewed as clear transgression of end-to-end connectivity principle of internet. Since local area network (LAN) based internal addresses are all disguised behind one publicly accessible NATenabled router, it is virtually impossible for public hosts to initiate a connection to a specific private host. This in turn adversely affects the NAT enabled network’s ability to support VOIP, Video conferencing and other peer-to-peer applications. The situation is acutely compounded when we have multiple levels and nesting of Static and Dynamic NATs. The situation is tempting when we hope to retain the benefits of NAT but may still aspire to achieve the principle of end-to-end connectivity. This manuscript tends to realize the above situation by proposing a three dimensional network address translation scheme with a tentative capability to support end-to-end connectivity based applications and at the same time retaining the benefits of conventional NAT model.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Baker, F.: Requirements for IP Version 4 routers. RFC 1812, Internet Engineering Task Force (June 1995)
Cisco Systems. Cisco IOS Network Address Translation (NAT). Technical report, as of (December 2000)
Cohen, A., Rangarajan, S.: A programming interface for supporting IP traffic processing. In: Proc. Of IWAN 1999 (1999)
Hain, T.: Architectural implications of NAT. RFC 2993, Internet Engineering Task Force (November 2000)
Hasenstein, M.: IP network address translation. Diplomarbeit, Technische Universite at Chemnitz, Chemnitz, Germany, as of (December 1, 2000)
Srisuresh, P., Gan, D.: Load sharing using IP Network Address Translation (LSNAT). RFC 2391, Internet Engineering Task Force (August 1998)
Srisuresh, P., Holdrege, M.: IP Network Address Translator (NAT) terminology and considerations. RFC 2663, Internet Engineering Task Force (August. 1999)
Srisuresh, P., Tsirtsis, G., Akkiraju, P., Hefferman, A.: DNS extensions to Network Address Translators (DNS ALG). RFC 2694, Internet Engineering Task Force (September 1999)
Tsirtsis, G., Srisuresh, P.: Network Address Translation| Protocol Translation (NAT-PT). RFC 2766, Internet Engineering Task Force (February 2000)
Braden, R.: RFC 1122: Requirements for Internet Hosts — Communication Layers (October 1989)
Eppinger, J. L.: TCP Connections for P2P Apps: A Software Approach to Solving the NAT Problem. Tech. Rep. CMU-ISRI-05-104, Carnegie Mellon University, Pittsburgh, PA (January 2005)
Ford, B., Srisuresh, P., Kegel, D.: Peer-to-peer communication across network address translators. In: Proceedings of the 2005 USENIX Annual Technical Conference, Anaheim, CA (April 2005)
Audet, F., Jennings, C.: (text). RFC 4787 Network Address Translation (NAT) Behavioral Requirements for Unicast UDP (January 2007)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2011 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Johal, H.S., Singh, B., Nagpal, A., Krishan, K. (2011). 3D NAT Scheme for Realizing Seamless End-to-End Connectivity and Addressing Multilevel Nested Network Address Translation Issues. In: Lee, R. (eds) Computer and Information Science 2011. Studies in Computational Intelligence, vol 364. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-21378-6_10
Download citation
DOI: https://doi.org/10.1007/978-3-642-21378-6_10
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-21377-9
Online ISBN: 978-3-642-21378-6
eBook Packages: EngineeringEngineering (R0)