File: qnetworkegg.html

package info (click to toggle)
qt-embedded 2.3.2-3
  • links: PTS
  • area: main
  • in suites: woody
  • size: 68,608 kB
  • ctags: 45,998
  • sloc: cpp: 276,654; ansic: 71,987; makefile: 29,074; sh: 12,305; yacc: 2,465; python: 1,863; perl: 481; lex: 480; xml: 68; lisp: 15
file content (130 lines) | stat: -rw-r--r-- 5,036 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Food-for-thought Easter Egg</title></head><body bgcolor="#ffffff">
<p>
<h1 align="center">The Twelve Networking Truths</h1>
<p>This is <a href="http://info.internet.isi.edu/1/in-notes/rfc">RFC
1925</a> - copied in here since its truths are even less limited than
the author says.  5, 6, 6a and 7 in particular can often be quoted
during software development discussions.
<p>
<hr>
<p>
<table cellspacing="0" cellpadding="0" width="100%"><tr>
<td align="left" valign="top">
Network Working Group<br>
Request for Comments: 1925<br>
Category: Informational<br>
</td><td align=right valign=top>
R. Callon, Editor<br>
IOOF<br>
1 April 1996
</td>
</tr></table>
<p>
<h3>Status of this Memo</h3>
<p>
   This memo provides information for the Internet community.  This memo
   does not specify an Internet standard of any kind.  Distribution of
   this memo is unlimited.
<p>
<h3>Abstract</h3>
<p>
   This memo documents the fundamental truths of networking for the
   Internet community. This memo does not specify a standard, except in
   the sense that all standards must implicitly follow the fundamental
   truths.
<p>
<h3>Acknowledgements</h3>
<p>
   The truths described in this memo result from extensive study over an
   extended period of time by many people, some of whom did not intend
   to contribute to this work. The editor merely has collected these
   truths, and would like to thank the networking community for
   originally illuminating these truths.
<p>
<h3>1. Introduction</h3>
<p>
   This Request for Comments (RFC) provides information about the
   fundamental truths underlying all networking. These truths apply to
   networking in general, and are not limited to TCP/IP, the Internet,
   or any other subset of the networking community.
<p>
<h3>2. The Fundamental Truths</h3>
<p>
   <ol>
   <li> It Has To Work.
<li> No matter how hard you push and no matter what the priority,
        you can't increase the speed of light.
<p>
        <ol type="a"> <li> (corollary). No matter how hard you try, you
        can't make a baby in much less than 9 months. Trying to speed
        this up <em>might</em> make it slower, but it won't make it
        happen any quicker. </ol>
<li> With sufficient thrust, pigs fly just fine. However, this is
        not necessarily a good idea. It is hard to be sure where they
        are going to land, and it could be dangerous sitting under them
        as they fly overhead.
<li> Some things in life can never be fully appreciated nor
        understood unless experienced firsthand. Some things in
        networking can never be fully understood by someone who neither
        builds commercial networking equipment nor runs an operational
        network.
<li> It is always possible to agglutinate multiple separate problems
        into a single complex interdependent solution. In most cases
        this is a bad idea.
<li> It is easier to move a problem around (for example, by moving
        the problem to a different part of the overall network
        architecture) than it is to solve it.
<p>
        <ol type="a"> <li> (corollary). It is always possible to add
        another level of indirection. </ol>
<li> It is always something.
<p>
        <ol type="a"> <li> (corollary). Good, Fast, Cheap: Pick any two
        (you can't have all three). </ol>
<li> It is more complicated than you think.
<li> For all resources, whatever it is, you need more.
<p>
       <ol type="a"> <li> (corollary) Every networking problem always
       takes longer to solve than it seems like it should.</ol>
<li> One size never fits all.
<li> Every old idea will be proposed again with a different name and
        a different presentation, regardless of whether it works.
<p>
        <ol type="a"> <li> (corollary). See rule 6a. </ol>
<li> In protocol design, perfection has been reached not when there
        is nothing left to add, but when there is nothing left to take
        away.
<p>
   </ol>
<p>
<h3>Security Considerations</h3>
<p>
   This RFC raises no security issues. However, security protocols are
   subject to the fundamental networking truths.
<p>
<h3>References</h3>
<p>
   The references have been deleted in order to protect the guilty and
   avoid enriching the lawyers.
<p>
<h3>Author's Address</h3>
<p>
   Ross Callon<br>
   Internet Order of Old Farts<br>
   c/o Bay Networks<br>
   3 Federal Street<br>
   Billerica, MA  01821<br>
   <br>
   Phone: 508-436-3936<br>
   EMail: rcallon@baynetworks.com<br>
<p>
<hr>
<p>
(Note that the RFC is covered by its own copyright notice; the one
below just covers this HTML page.)

<p><address><hr><div align="center">
<table width="100%" cellspacing="0" border="0"><tr>
<td>Copyright  2001 Trolltech<td><a href="http://www.trolltech.com/trademarks.html">Trademarks</a>
<td align="right"><div align="right">Qt version 2.3.2</div>
</table></div></address></body></html>