ACM Home Page
Please provide us with feedback. Feedback
Addressing reality: an architectural response to real-world demands on the evolving Internet
Full text PdfPdf (361 KB)
Source Applications, Technologies, Architectures, and Protocols for Computer Communication archive
Proceedings of the ACM SIGCOMM workshop on Future directions in network architecture table of contents
Karlsruhe, Germany
SESSION: Motivations table of contents
Pages: 247 - 257  
Year of Publication: 2003
ISBN:1-58113-748-0
Also published in ...
Authors
David D. Clark  MIT LCS
Karen Sollins  MIT LCS
John Wroclawski  MIT LCS
Ted Faber  USC ISI
Sponsor
SIGCOMM: ACM Special Interest Group on Data Communication
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 12,   Downloads (12 Months): 85,   Citation Count: 9
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/944759.944761
What is a DOI?

ABSTRACT

A system as complex as the Internet can only be designed effectively if it is based on a core set of design principles, or tenets, that identify points in the architecture where there must be common understanding and agreement. The tenets of the original Internet architecture [6] arose as a response to the technical, governmental, and societal environment of internetworking's earliest days, but have remained central to the Internet as it has evolved. In light of the increasing integration of the Internet into the social, economic, and political aspects of our lives, it is worth revisiting the underlying tenets of what is becoming a central element of the world's infrastructure.This paper examines three key tenets that we believe should guide the evolution of the Internet in its next generation and beyond. They are: design for change, controlled transparency, and the centrality of the tussle space. [8] Our purpose is not to present these ideas as new, but rather to propose that they should be elevated to central tenets of the evolving architecture of the Internet, and explore the ramifications of doing so. The paper first examines the tenets somewhat abstractly, and then in more detail by studying their relation to several design choices needed for a complete architecture. We conclude with a discussion of the relationship between the network architecture and the applications it serves.


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
 
2
Y. Bernet, The Complementary Roles of RSVP and Differentiated Services in the Full-Service QOS Network, IEEE Communications Magazine, Vol. 38, No. 2, February, 2000.
3
 
4
B. Carpenter, Internet Transparency, RFC 2775, February 2000.
 
5
 
6
D. D. Clark, Design Principles of the Internet Architecture, Proc. ACM SIGCOMM 1988, Stanford, CA, USA, August 1988.
7
8
 
9
 
10
L. Daigle, D. van Gulik, R. Iannela, P. Faltstrom, URN Namespace Definition Mechanisms, RFC 2611, June, 1999.
11
 
12
Dept. of Defense, Trusted Computer Systems Evaluation CriteriaDoD 5200.28-STD, August 15, 1983. (Also known as the "Orange Book".)
 
13
FidoNet Web Site, http://www.fidonet.org
 
14
M. Handley, C. Kreibich and V. Paxson, Network Intrusion Detection, Evasion, Traffic Normalization and End-to-End Protocol Semantics, Proc. USENIX Security Symposium 2001.
 
15
S. Kent, C. Lynn, K. Seo, Secure Border Gateway Protocol (S-BGP), IEEE JSAC, Vol. 18 No. 4, April 2000, pp. 582--592.
 
16
P. V. Mockapetris, Domain names - concepts and facilities, RFC 1034, Nov. 1, 1987.
 
17
P. V. Mockapetris, Domain names - implementation and specification, RFC 1035, Nov. 1, 1987.
 
18
R. Moskowitz, unpublished documents on the Host Identity Payload Architecture, 2001. Currently the work only exists as Internet Drafts.
 
19
National Research Council, Committee on Information Systems Trustworthiness, Trust in Cyberspace, National Academy Press, 1999.
 
20
J. Postel, ed., Internet Protocol, RFC 791, Std 5, September 1981.
21
 
22
23
 
24
K. Sollins, Architectural Principles of Uniform Resource Name Resolution, RFC 2276, January, 1998.
 
25
K. Sollins and L. Massinter, Functional Requirements for Uniform Resource Names, RFC 1737, December, 1994.
 
26
 
27
28

CITED BY  9

Collaborative Colleagues:
David D. Clark: colleagues
Karen Sollins: colleagues
John Wroclawski: colleagues
Ted Faber: colleagues