A waypoint service approach to connect heterogeneous internet address spaces

Proceedings of the 2001 USENIX Annual Technical Conference

Volumn , Issue , 2001, Pages

  Eugene Ng, T S ^a   Stoica, Ion ^a   Zhang, Hui ^a  

^a CARNEGIE MELLON UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

BIRDS; NETWORK LAYERS; ROUTERS;

ADDRESS SPACE; BI-DIRECTIONAL; CONNECTIVITY PROPERTIES; HIGH CONNECTIVITY; IPV6 ADDRESS; PROTOTYPE SYSTEM; RAPID GROWTH; SCARCE RESOURCES;

INTERNET PROTOCOLS;

EID: 85084160260     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (27)

1. S. Bellovin. Firewall friendly FTP, February 1994. RFC-1579.
2. M. Borella, J. Lo, D. Grabelsky, and G. Montenegro. Realm Specific IP: A framework, July 2000. Internet Draft, draft-ietf-nat-rsipframework-05.txt.
3. D. R. Cheriton and M. Gritter. TRIAD: A new next generation Internet architecture, March 2000. http://www-dsg.stanford.edu/triad/triad.ps.gz.
4. S. Deering and R. Hinden. Internet Protocol, version 6 (IPv6) specification, December 1998. RFC-2460.
5. P. Ferguson and D. Senie. Network ingress filtering: Defeating denial of service attacks which employ IP source address spoofing, May 2000. RFC-2827.
6. P. Francis. IPNL architecture and protocol description, May 2000. Available from the author.
7. J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, and T. Berners-Lee. Hypertext Transfer Protocol - HTTP/1.1, June 1999. RFC-2616.
8. R. Gilligan and E. Nordmark. Transition mechanisms for IPv6 hosts and routers, April 1996. RFC-2893.
9. A. Gulbrandsen, P. Vixie, and L. Esibov. A DNS RR for specifying the location of services (DNS SRV), February 2000. RFC-2782.
10. M. Holdrege and P. Srisuresh. Protocol complications with the IP network address translator, January 2001. RFC-3027.
11. Internet Software Consortium. Berkeley Internet Name Domain (BIND) version 8.2.3. http://www.isc.org/products/BIND/.
12. D. Kegel. NAT and peer-to-peer networking. http://www.alumni.caltech.edu/~dank/peer-nat.html.
13. S. Kent and R. Atkinson. Security architecture for the Internet Protocol, November 1998. RFC-2401.
14. H. Kitamura. A SOCKS-based IPv6/IPv4 gateway mechanism, March 2001. Internet Draft, draft-ietf-ngtrans-socks-gateway-06.txt.
15. P. Mockapetris. Domain names - concepts and facilities, November 1987. RFC-1034.
16. J. Mogul and S. Deering. Path MTU discovery, November 1990. RFC-1191.
17. R. Moskowitz. Host Identity Payload, February 2001. Internet Draft, draft-moskowitz-hip-arch-02.txt.
18. E. Nordmark. Stateless IP/ICMP translation algorithm (SIIT), February 2000. RFC-2765.
19. J. Postel. Internet Control Message Protocol, September 1981. RFC-792.
20. J. Postel. Internet Protocol, September 1981. RFC-791.
21. Y. Rekhter, B. Moskowitz, D. Karrenberg, G. J. de Groot, and E. Lear. Address allocation for private internets, February 1996. RFC-1918.
22. R. Rivest. The MD5 message-digest algorithm, April 1992. RFC-1321.
23. S. Savage, D. Wetherall, A. Karlin, and T. Anderson. Practical network support for IP traceback. In Proceedings of ACM SIG-COMM'00, Stockholm, Sweden, Aug. 2000.
24. D. Senie. NAT friendly application design guidelines, March 2001. Internet Draft, draft-ietf-nat-app-guide-05.txt.
25. P. Srisuresh and K. Egevang. Traditional IP network address translator (Traditional NAT), January 2001. RFC-3022.
26. P. Srisuresh, G. Tsirtsis, P. Akkiraju, and A. Heffernan. DNS extensions to network address translators (DNS-ALG), September 1999. RFC-2694.
27. G. Tsirtsis and P. Srisuresh. Network address translation - protocol translation (NAT-PT), February 2000. RFC-2766.