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

MobiWac'07 - Proceedings of the 5th ACM International Workshop on Mobility Management and Wireless Access

Volumn , Issue , 2007, Pages 74-83

  Atkinson, R ^a   Bhatti, S ^b   Hailes, S ^c  

^a Extreme Networks   (United States)

^b UNIVERSITY OF ST ANDREWS   (United Kingdom)

^c UNIVERSITY COLLEGE LONDON   (United Kingdom)

Author keywords

Addressing; Identifier; Locator; Naming; Routing

Indexed keywords

ADDRESSING; IDENTIFIER; LOCATOR; NAMING; ROUTING;

INTERNET; TELECOMMUNICATION NETWORKS;

INTERNET PROTOCOLS;

EID: 84860389017     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1298091.1298105     Document Type: Conference Paper

References (25)

1. B. Aboba and W. J. Dixon. IPsec-Network address translation (NAT) compatibility requirements. RFC 3715, IETF, Mar. 2004.
2. R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. DNS Security Introduction and Requirements. RFC 4033, IETF, Mar. 2005.
3. H. Balakrishnan, K. Lakshminarayanan, S. Ratnasamy, S. Shenker, I. Stoica, and M. Walfish. A Layered Naming Architecture for the Internet. ACM Computer Communications Review, 34(4):343-352, 2004. (Pubitemid 40954892)
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 1753, IETF, Dec. 1994.
6. D. Clark, R. Braden, A. Falk, and V. Pingali. FARA: Reorganizing The Addressing Architecture. ACM Computer Communications Review, 33(4):313-321, 2003.
7. D. Cohen. On Names, Addresses, and Routings. Internet Experiment Note (IEN) 23, ARPA Network Working Group, Jan. 1978.
8. J. Crowcroft, S. Hand, R. Mortier, T. Roscoe, and A. Warfield. Plutarch: An Argument for Network Pluralism. In FDNA 2003: Proceedings of the ACM SIGCOMM workshop on Future Directions in Network Architecture, pages 258-266, New York, NY, USA, 2003. ACM Press.
9. D. Eastlake, J. Schiller, and S. Crocker. "randomness requirements for security". RFC 4086, IETF, June 2005.
10. C. E. P. (Ed.). IP mobility support. RFC 2002, IETF, Oct. 1996.
11. K. Egevang and P. Francis. The IP network address translator (NAT). RFC 1631, IETF, May 1994.
12. P. Ferguson and D. Senie. Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing. RFC 2267, IETF, Jan. 1998.
13. P. Francis and R. Gummadi. IPNL: A NAT-extended Internet Architecture. In Proceedings of ACM SIGCOMM 2001, pages 69-80, New York, NY, USA, 2001. ACM Press. (Pubitemid 32981955)
14. M. Holdrege and P. Srisuresh. Protocol Complications with the IP Network Address Translator. RFC 3027, IETF, Jan. 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. H. Saltzer. On the Naming and Binding of Network Destinations. RFC 1498, IETF, Aug. 1993.
21. S. Schmid, L. Eggert, M. Brunner, and J. Quittek. TurfNet: An Architecture for Dynamically Composable Networks. LNCS, 3457/2005:94-114, 2005. (Pubitemid 41274290)
22. J. Shoch. Inter-Network Naming, Addressing, and Routing. Internet Experiment Note 19, ARPA Network Working Group, Jan. 1978.
23. I. Stoica, D. Adkins, S. Zhuang, S. Shenker, and S. Surana. Internet Indirection Infrastructure. ACM Computer Communications Review, 32(4):73-86, 2002. (Pubitemid 43843776)
24. Z. Turanyi, A. Valko, and A. T. Campbell. 4+4: An Architecture for Evolving the Internet Address Space back toward Transparency. ACM Computer Communications Review, 33(5):43-54, 2003.
25. B. Wellington. Secure Domain Name System (DNS) Dynamic Update. RFC 3007, IETF, Nov. 2000.