ACM Home Page
Please provide us with feedback. Feedback
Unmanaged Internet Protocol: taming the edge network management crisis
Full text PdfPdf (278 KB)
Source ACM SIGCOMM Computer Communication Review archive
Volume 34 ,  Issue 1  (January 2004) table of contents
COLUMN: Papers from Hotnets-II table of contents
Pages: 93 - 98  
Year of Publication: 2004
ISSN:0146-4833
Author
Bryan Ford  Massachusetts Institute of Technology
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 6,   Downloads (12 Months): 96,   Citation Count: 2
Additional Information:

abstract   references   cited by   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/972374.972391
What is a DOI?

ABSTRACT

Though appropriate for core Internet infrastructure, the Internet Protocol is unsuited to routing within and between emerging ad-hoc edge networks due to its dependence on hierarchical, administratively assigned addresses. Existing ad-hoc routing protocols address the management problem but do not scale to Internet-wide networks. The promise of ubiquitous network computing cannot be fulfilled until we develop an Unmanaged Internet Protocol (UIP), a scalable routing protocol that manages itself automatically. UIP must route within and between constantly changing edge networks potentially containing millions or billions of nodes, and must still function within edge networks disconnected from the main Internet, all without imposing the administrative burden of hierarchical address assignment. Such a protocol appears challenging but feasible. We propose an architecture based on self-certifying, cryptographic node identifies and a routing algorithm adapted from distributed hash tables.


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
J. Abley, B. Black, and V. Gill. Goals for IPv6 site-multihoming architectures, August 2003, RFC 3582.
2
3
4
 
5
B. Carpenter, J. Crowcroft, and Y. Rekhter. IPv4 address behaviour today, February 1997. RFC 2101.
 
6
Microsoft Corporation. Plug and play networking with Microsoft automatic private IP addressing, March 1998.
 
7
R. Droms, Dynamic host configuration protocol, March 1997. RFC 2131.
 
8
Bryan Ford. Peer-to-peer (P2P) communication across middleboxes, October 2003. Internet Draft draft-ford-midcom-p2p-01.txt (Work in Progress).
 
9
Bryan Ford. Scalable Internet routing on topology-independent node identities. Technical Report MIT-LCS-TR-926, MIT Laboratory for Computer Science, 2003. Forthcoming.
 
10
M. Gritter and D. R. Cheriton. An architecture for content routing support in the Internet. In Usenix Symposium on Internet Technologies and Systems, March 2001.
 
11
C. Hedrick. Routing information protocol, June 1988. RFC 1058.
12
 
13
M. Holdrege and P. Srisuresh. Protocol complications with the IP network address translator, January 2001. RFC 3027.
 
14
David B. Johnson. Routing in ad hoc networks of mobile hosts. In IEEE Workshops on Mobile Computing Systems and Applications, pages 158--163, December 1994.
 
15
L. R. Ford Jr. and D. R. Fulkerson. Flows in Networks. Princeton University Press, Princeton N. J., 1962.
 
16
S. Kent and R. Atkinson. Security architecture for the Internet Protocol, November 1998. RFC 2401.
 
17
M. Leech et al. SOCKS protocol version 5, March 1996. RFC 1928.
 
18
J. C. R. Licklider. The computer as a communication device. Science and Technology, April 1968.
 
19
20
 
21
R. Moskowitz and P. Nikander. Host identity protocol architecture, April 2003. Internet-Draft (Work in Progress).
 
22
J. Moy. OSPF version 2, July 1991. RFC 1247.
23
 
24
 
25
C. Perkins. Editor. IP mobility support for IPv4, August 2002. RFC 3344.
 
26
Y. Rekhter and T. Li (editors). An architecture for IP address allocation with CIDR, September 1993. RFC 1518.
 
27
Y. Rekhter and T. Li (editors). A border gateway protocol 4 (BGP-4), March 1995. RFC 1771.
 
28
Lawrence G. Roberts and Barry D. Wessler. Computer network development to achieve resource sharing. In Spring Joint Computer Conference, Atlantic City, New Jersey. May 1970.
 
29
J. Rosenberg, J. Weinberger, C. Huitema, and R. Mahy. STUN - simple traversal of user datagram protocol (UDP) through network address translators (NATs), March 2003. RFC 3489.
30
 
31
 
32
P. Srisuresh and K. Egevang. Traditional IP network address translator (Traditional NAT), January 2001. RFC 3022.
33
34
 
35
UPnP Forum. Internet gateway device (IGD) standardized device control protocol V 1.0, November 2001. http://www.upnp.org/.
 
36
P. Vixie, Editor, S. Thomson, Y. Rekhter, and J. Bound. Dynamic updates in the domain name system (DNS UPDATE), April 1997. RFC 2136.


Peer to Peer - Readers of this Article have also read: