A proposal for unifying mobility with multi-homing, NAT, & security

ABSTRACT

Internet users seek solutions for mobility, multi-homing, support for localised address management (i.e. via NATs), and end-to-end security. Existing mobility approaches are not well integrated into the rest of the Internet architecture, instead primarily being separate extensions that at present are not widely deployed. Because the current approaches to these issues were developed separately, such approaches often are not harmonious when used together. Meanwhile, the Internet has a number of namespaces, for example the IP address or the Domain Name. In recent years, some have postulated that the Internet's namespaces are not sufficiently rich and that the current concept of an address is too limiting. One proposal, the concept of separating an address into an Identifier and a separate Locator, has been controversial in the Internet community for years. It has been considered within the IETF and IRTF several times, but always was rejected as unworkable. This paper takes the position that evolving the naming in the Internet by splitting the address into separate Identifier and Locator names can provide an elegant integrated solution to the key issues listed above, without changing the core routing architecture, while offering incremental deployability through backwards compatibility with IPv6.

REFERENCES

• 1: B. Aboba , W. Dixon, IPsec-Network Address Translation (NAT) Compatibility Requirements, RFC Editor, 2004
• 2: R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. DNS Security Introduction and Requirements. RFC 4033, IETF, Mar. 2005.
• 3: Hari Balakrishnan , Karthik Lakshminarayanan , Sylvia Ratnasamy , Scott Shenker , Ion Stoica , Michael Walfish, A layered naming architecture for the internet, ACM SIGCOMM Computer Communication Review, v.34 n.4, October 2004
• 4: D. Cheriton and M. Gritter. TRIAD: A new next generation internet architecture. Technical report, Stanford University, Stanford, CA, USA, Mar. 2000.
• 5: N. Chiappa, IPng Technical Requirements Of the Nimrod Routing and Addressing Architecture, RFC Editor, 1994
• 6: David Clark , Robert Braden , Aaron Falk , Venkata Pingali, FARA: reorganizing the addressing architecture, ACM SIGCOMM Computer Communication Review, v.33 n.4, October 2003
• 7: D. Cohen. On Names, Addresses, and Routings. Internet Experiment Note (IEN) 23, ARPA Network Working Group, Jan. 1978.
• 8: Jon Crowcroft , Steven Hand , Richard Mortier , Timothy Roscoe , Andrew Warfield, Plutarch: an argument for network pluralism, Proceedings of the ACM SIGCOMM workshop on Future directions in network architecture, August 25-27, 2003, Karlsruhe, Germany
• 9: D. Eastlake, 3rd , S. Crocker , J. Schiller, Randomness Recommendations for Security, RFC Editor, 1994
• 10: CEP. (Ed.). IP mobility support. RFC 2002, IETF, Oct. 1996.
• 11: K. Egevang , P. Francis, The IP Network Address Translator (NAT), RFC Editor, 1994
• 12: P. Ferguson , D. Senie, Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing, RFC Editor, 1998
• 13: Paul Francis Ramakrishna, IPNL: A NAT-extended internet architecture, Proceedings of the 2001 conference on Applications, technologies, architectures, and protocols for computer communications, p.69-80, August 2001, San Diego, California, United States
• 14: M. Holdrege , P. Srisuresh, Protocol Complications with the IP Network Address Translator, RFC Editor, 2001
• 15: A. Huttunen, B. Swander, V. Volpe, L. DiBurro, and M. Stenberg. UDP encapsulation of IPsec ESP packets. RFC 3948, IETF, Jan. 2005.
• 16: IEEE. Guidelines for 64--bit Global Identifier (EUI-64). Tutorial, IEEE, 2007.
• 17: D. B. Johnson, C. E. Perkins, and J. Arkko. Mobility support in IPv6. RFC 3775, IETF, June 2004.
• 18: A. Jonsson, M. Folke, and B. Ahlgren. The Split Naming/Forwarding Network Architecture. In Proceedings of 1st Swedish National Computer Networking Workshop, Arlandastad, Sweden, Sept. 2003.
• 19: M. O'Dell. 8+8 -- An Alternate Addressing Architecture for IPv6. Internet-Draft draft-odell-8+8-00.txt, IETF, Oct. 1996.
• 20: J. Saltzer, On the Naming and Binding of Network Destinations, RFC Editor, 1993
• 21: S. Schmid, L. Eggert, M. Brunner, and J. Quittek. TurfNet: An Architecture for Dynamically Composable Networks. LNCS, 3457/2005:94--114, 2005.
• 22: J. Shoch. Inter-Network Naming, Addressing, and Routing. Internet Experiment Note~19, ARPA Network Working Group, Jan. 1978.
• 23: Ion Stoica , Daniel Adkins , Shelley Zhuang , Scott Shenker , Sonesh Surana, Internet indirection infrastructure, ACM SIGCOMM Computer Communication Review, v.32 n.4, October 2002
• 24: Zoltán Turányi , András Valkó , Andrew T. Campbell, 4+4: an architecture for evolving the Internet address space back toward transparency, ACM SIGCOMM Computer Communication Review, v.33 n.5, October 2003 [doi>10.1145/963985.963990]
• 25: B. Wellington, Secure Domain Name System (DNS) Dynamic Update, RFC Editor, 2000

INDEX TERMS

Primary Classification:
  C. Computer Systems Organization
  C.2 COMPUTER-COMMUNICATION NETWORKS
      C.2.1 Network Architecture and Design

Additional Classification:
  C. Computer Systems Organization
  C.2 COMPUTER-COMMUNICATION NETWORKS
      C.2.2 Network Protocols

General Terms:
Design

Keywords:
addressing, identifier, locator, maming, routing