ACM Home Page
Please provide us with feedback. Feedback
IPNL: A NAT-extended internet architecture
Full text PdfPdf (242 KB)
Source Applications, Technologies, Architectures, and Protocols for Computer Communication archive
Proceedings of the 2001 conference on Applications, technologies, architectures, and protocols for computer communications table of contents
San Diego, California, United States
Pages: 69 - 80  
Year of Publication: 2001
ISBN:1-58113-411-8
Also published in ...
Authors
Paul Francis  Tahoe Networks
Ramakrishna Gummadi  UC Berkeley
Sponsor
SIGCOMM: ACM Special Interest Group on Data Communication
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 15,   Downloads (12 Months): 88,   Citation Count: 26
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/383059.383065
What is a DOI?

ABSTRACT

This paper presents and analyzes IPNL (for IP Next Layer), a NAT-extended Internet protocol architecture designed to scalably solve the address depletion problem of IPv4. A NAT-extended architecture is one where only hosts and NAT boxes are modified. IPv4 routers and support protocols remain untouched. IPNL attempts to maintain all of the original characteristics of IPv4, most notably address prefix location independence. IPNL provides true site isolation (no renumbering), and allows sites to be multi-homed without polluting the default-free routing zone with per-site prefixes. We discuss IPNL's architectural benefits and drawbacks, and show that it comes acceptably close to achieving its goals.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
S. Bradner, A. Mankin, J. Schiller, " A Framework for Purpose Built Keys (PBK)", Internet Draft, draft-bradner-pbk-frame-00.txt, February 2001.
 
2
B. Carpenter, K. Moore, "Connection of IPv6 Domains via IPv4 Clouds", RFC3056, February 2001.
 
3
I. Castineyra, N. Chiappa, M. Steenstrup, "The Nimrod Routing Architecture", RFC1992, August 1996.
 
4
D. R. Cheriton, M. Gritter, "TRIAD: A Scalable Deployable NAT-based Internet Architecture", Stanford Computer Science Technical Report, January 2000.
 
5
M. Crawford, "Router Renumbering for IPv6", RFC2894, August 2000.
 
6
S. Deering, R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC2460, December 1998.
 
7
Mike O'Dell, "GSE-an alternate addressing architecture for IPv6", Internet Draft, draft-ietf-ipngwg-gseaddr-00.txt, February 1997.
 
8
R. Droms, "Dynamic Host Configuration Protocol", RFC1541, March 1997.
 
9
K. Egevang, P. Francis, "The IP Network Address Translator (NAT)", RFC1631, May 1994.
 
10
P. Francis, "Pip Near-term Architecture", RFC1621, May 1994.
 
11
P. Francis, R. Gummadi, "IPNL Protocol Specification"; available from http://www.ipnl.net/spec/
 
12
P. Gross, P. Almquist, "IESG Deliberations on Routing and Addressing", RFC1380, November 1992.
 
13
M. Handley, H. Schulzrinne, E. Schooler, J. Rosenberg, "SIP: Session Initiation Protocol", RFC2543, March 1999.
 
14
R. Hinden, S. Deering, "IP Version 6 Addressing Architecture", RFC2373, July 1998.
 
15
S. Kent, R. Atkinson, "IP Encapsulating Security Payload (ESP)", RFC2406, November 1998.
16
 
17
R. Moskowitz, "Host Identity Payload Architecture", Internet Draft, draft-moskowitz-hip-arch-02.txt, February 2001.
 
18
 
19
C. Perkins, Editor, "IP Mobility Support", RFC2002, October 1996.
 
20
C. Rigney, A. Rubens, W. Simpson, S. Willens, "Remote Authentication Dial In User Service (RADIUS)", RFC2138, April 1997.
 
21
J. Saltzer, "On the Naming and Binding of Network Destinations", RFC1498, August 1993.
 
22
Site Multihoming in IPv6 (multi6), http://www.ietf.org/html.charters/multi6-charter.html
23
 
24
F. Templin, "Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)", Internet Draft, draft-ietf-ngtrans-isatap-00.txt, March 2001.

CITED BY  26

Collaborative Colleagues:
Paul Francis: colleagues
Ramakrishna Gummadi: colleagues