| 1 |
<pre>Network Working Group G. Malkin |
| 2 |
Request for Comments: 1539 Xylogics, Inc. |
| 3 |
Obsoletes: <a href="./rfc1391">1391</a> October 1993 |
| 4 |
FYI: 17 |
| 5 |
Category: Informational |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">The Tao of IETF</span> |
| 9 |
<span class="h1">A Guide for New Attendees of the Internet Engineering Task Force</span> |
| 10 |
|
| 11 |
|
| 12 |
Status of this Memo |
| 13 |
|
| 14 |
This memo provides information for the Internet community. It does |
| 15 |
not specify an Internet standard. Distribution of this memo is |
| 16 |
unlimited. |
| 17 |
|
| 18 |
|
| 19 |
Abstract |
| 20 |
|
| 21 |
Over the last two years, the attendance at Internet Engineering Task |
| 22 |
Force (IETF) Plenary meetings has grown phenomenally. Approximately |
| 23 |
38% of the attendees are new to the IETF at each meeting. About 33% |
| 24 |
of those go on to become regular attendees. When the meetings were |
| 25 |
smaller, it wasn't very difficult for a newcomer to get to know |
| 26 |
people and get into the swing of things. Today, however, a newcomer |
| 27 |
meets many more new people, some previously known only as the authors |
| 28 |
of Request For Comments (RFC) documents or thought provoking email |
| 29 |
messages. |
| 30 |
|
| 31 |
The purpose of this For Your Information (FYI) RFC is to explain to |
| 32 |
the newcomers how the IETF works. This will give them a warm, fuzzy |
| 33 |
feeling and enable them to make the meeting more productive for |
| 34 |
everyone. This FYI will also provide the mundane bits of information |
| 35 |
which everyone who attends an IETF meeting should know. |
| 36 |
|
| 37 |
|
| 38 |
Acknowledgments |
| 39 |
|
| 40 |
The IETF Secretariat is made up of the following people: Steve Coya |
| 41 |
(Executive Director of the IETF), Cynthia Clark, Lois Keiper, Debra |
| 42 |
Legare, John Stewart, and Megan Davies Walnut. These are the people |
| 43 |
behind the Registration Table, and the success, of the IETF meetings. |
| 44 |
I thank them for their hard work, and for their input and review of |
| 45 |
this document. Thanks also to Vinton Cerf, Christian Huitema, and |
| 46 |
Jon Postel for their review and comments. And, as always, special |
| 47 |
thanks to April Marine and Joyce Reynolds. |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Internet Engineering Task Force [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">Section 1</a> - The "Fun" Stuff |
| 60 |
What is the IETF? . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 61 |
Humble Beginnings . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 62 |
The Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 63 |
IETF Mailing Lists . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 64 |
Registration . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 65 |
Newcomers' Orientation . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 66 |
Dress Code . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 67 |
Seeing Spots Before Your Eyes . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 68 |
Terminal Room . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 69 |
Social Event . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 70 |
Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 71 |
Other General Things . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 72 |
|
| 73 |
<a href="#section-2">Section 2</a> - The "You've got to know it" Stuff |
| 74 |
Registration Bullets . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 75 |
Mailing Lists and Archives . . . . . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 76 |
Important Email Addresses . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a> |
| 77 |
IETF Proceedings . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 78 |
InterNIC Archives . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a> |
| 79 |
Be Prepared . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a> |
| 80 |
RFCs and Internet-Drafts . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a> |
| 81 |
Frequently Asked Questions (and Their Answers) . . . . . . . <a href="#page-16">16</a> |
| 82 |
Pointers to Useful Documents and Files . . . . . . . . . . . <a href="#page-17">17</a> |
| 83 |
|
| 84 |
<a href="#section-3">Section 3</a> - The "Reference" Stuff |
| 85 |
Tao . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a> |
| 86 |
IETF Area Abbreviations . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a> |
| 87 |
Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a> |
| 88 |
References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a> |
| 89 |
Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a> |
| 90 |
Author's Address . . . . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a> |
| 91 |
|
| 92 |
|
| 93 |
What is the IETF? |
| 94 |
|
| 95 |
The Internet Engineering Task Force is a loosely self-organized group |
| 96 |
of people who make technical and other contributions to the |
| 97 |
engineering and evolution of the Internet and its technologies. It |
| 98 |
is the principal body engaged in the development of new Internet |
| 99 |
Standard specifications. Its mission includes: |
| 100 |
|
| 101 |
o Identifying, and proposing solutions to, pressing operational and |
| 102 |
technical problems in the Internet; |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Internet Engineering Task Force [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 111 |
|
| 112 |
|
| 113 |
o Specifying the development or usage of protocols and the near-term |
| 114 |
architecture to solve such technical problems for the Internet; |
| 115 |
|
| 116 |
o Making recommendations to the Internet Engineering Steering Group |
| 117 |
(IESG) regarding the standardization of protocols and protocol |
| 118 |
usage in the Internet; |
| 119 |
|
| 120 |
o Facilitating technology transfer from the Internet Research Task |
| 121 |
Force (IRTF) to the wider Internet community; and |
| 122 |
|
| 123 |
o Providing a forum for the exchange of information within the |
| 124 |
Internet community between vendors, users, researchers, agency |
| 125 |
contractors, and network managers. |
| 126 |
|
| 127 |
The IETF Plenary meeting is not a conference, although there are |
| 128 |
technical presentations. The IETF is not a traditional standards |
| 129 |
organization, although many standards are produced. The IETF is the |
| 130 |
volunteers who meet three times a year to fulfill the IETF mission. |
| 131 |
|
| 132 |
There is no membership in the IETF. Anyone may register for and |
| 133 |
attend any meeting. The closest thing there is to being an IETF |
| 134 |
member is being on the IETF or Working Group mailing lists (see the |
| 135 |
IETF Mailing Lists section). This is where the best information |
| 136 |
about current IETF activities and focus can be found. |
| 137 |
|
| 138 |
|
| 139 |
Humble Beginnings |
| 140 |
|
| 141 |
The first IETF meeting was held in January, 1986 at Linkabit in San |
| 142 |
Diego with 15 attendees. The 4th IETF, held at SRI in Menlo Park in |
| 143 |
October, 1986, was the first at which non-government vendors |
| 144 |
attended. The concept of Working Groups (WG) was introduced at the |
| 145 |
5th IETF meeting at the NASA Ames Research Center in California in |
| 146 |
February, 1987. The 7th IETF, held at MITRE in McLean, Virginia in |
| 147 |
July, 1987, was the first meeting with over 100 attendees. |
| 148 |
|
| 149 |
The 14th IETF meeting was held at Stanford University in July, 1989. |
| 150 |
It marked a major change in the structure of the IETF universe. The |
| 151 |
IAB (then Internet Activities Board, now Internet Architecture |
| 152 |
Board), which until that time oversaw many Task Forces, changed its |
| 153 |
structure to leave only two: the IETF and the IRTF. The IRTF is |
| 154 |
tasked to consider the long-term research problems in the Internet. |
| 155 |
The IETF also changed at that time. |
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Internet Engineering Task Force [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 167 |
|
| 168 |
|
| 169 |
After the Internet Society (ISOC) was formed in January 1992, the IAB |
| 170 |
proposed to ISOC that the IAB's activities should take place under |
| 171 |
the auspices of the Internet Society. During INET92, in Kobe, Japan, |
| 172 |
the ISOC Trustees approved a new charter for the IAB to reflect the |
| 173 |
proposed relationship. |
| 174 |
|
| 175 |
A recent first for the IETF was its first European meeting. In July, |
| 176 |
1993, the IETF met in Amsterdam, The Netherlands. The U.S./non-U.S. |
| 177 |
attendees split was nearly 50/50. |
| 178 |
|
| 179 |
|
| 180 |
The Hierarchy |
| 181 |
|
| 182 |
To completely understand the structure of the IETF, it is useful to |
| 183 |
understand the overall structure in which the IETF resides. There |
| 184 |
are four groups in the structure: the ISOC and its Board of Trustees |
| 185 |
(BOT), the IAB, the IESG, and the IETF itself. |
| 186 |
|
| 187 |
Internet standardization is an organized activity of the ISOC. The |
| 188 |
ISOC is a professional society that is concerned with the growth and |
| 189 |
evolution of the worldwide Internet, with the way in which the |
| 190 |
Internet is and can be used, and with the social, political, and |
| 191 |
technical issues which arise as a result. The BOT is responsible for |
| 192 |
approving appointments to the IAB from among the nominees submitted |
| 193 |
by the IETF nominating committee. |
| 194 |
|
| 195 |
The IAB is a technical advisory group of the ISOC. It is chartered |
| 196 |
to provide oversight of the architecture of the Internet and its |
| 197 |
protocols, and to serve, in the context of the Internet Standards |
| 198 |
process, as a body to which the decisions of the IESG may be |
| 199 |
appealed. The IAB is responsible for approving appointments to the |
| 200 |
IESG from among the nominees submitted by the IETF nominations |
| 201 |
committee. |
| 202 |
|
| 203 |
The IESG is responsible for technical management of IETF activities |
| 204 |
and the Internet Standards process. As part of the ISOC, it |
| 205 |
administers the process according to the rules and procedures which |
| 206 |
have been ratified by the ISOC BOT. The IESG is directly responsible |
| 207 |
for the actions associated with entry into and movement along the |
| 208 |
IETF "standards track", including final approval of specifications as |
| 209 |
Internet Standards. |
| 210 |
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Internet Engineering Task Force [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 223 |
|
| 224 |
|
| 225 |
The IETF is divided into nine functional Areas. They are: |
| 226 |
Applications, Internet Services, Network Management, Operational |
| 227 |
Requirements, Routing, Security, Service Applications, Transport, and |
| 228 |
User Services. Each Area has at least one Area Director. There is |
| 229 |
also an Area Director who oversees Standards Management. The Area |
| 230 |
Directors, along with the IETF Chair, form the IESG. Phillip Gross |
| 231 |
has been the IETF Chair since the IETF's 7th meeting. He founded the |
| 232 |
IESG and serves as its Chair as well. |
| 233 |
|
| 234 |
Each Area has several Working Groups. A Working Group is a group of |
| 235 |
people who work under a charter to achieve a certain goal. That goal |
| 236 |
may be the creation of an informational document, the creation of a |
| 237 |
protocol standard, or the resolution of problems in the Internet. |
| 238 |
Most Working Groups have a finite lifetime. That is, once a Working |
| 239 |
Group has achieved its goal, it disbands. As in the IETF, there is |
| 240 |
no official membership for a Working Group. Unofficially, a Working |
| 241 |
Group member is somebody who's on that Working Group's mailing list; |
| 242 |
however, anyone may attend a Working Group meeting (see the Be |
| 243 |
Prepared section below). |
| 244 |
|
| 245 |
Areas may also have Birds of a Feather (BOF) groups. They generally |
| 246 |
have the same goals as Working Groups, except that they have no |
| 247 |
charter and usually only meet once or twice. BOFs are often held to |
| 248 |
determine if there is enough interest to form a Working Group. |
| 249 |
|
| 250 |
|
| 251 |
IETF Mailing Lists |
| 252 |
|
| 253 |
Anyone who plans to attend an IETF meeting should join the IETF |
| 254 |
announcements mailing list. This is where all of the meeting |
| 255 |
information, new and revised Internet-Draft and RFC announcements, |
| 256 |
IESG Recommendations, and Last Calls are posted. People who'd like |
| 257 |
to "get technical" may also join the IETF discussion list, |
| 258 |
"[email protected]". This was the only list before the |
| 259 |
announcement list was created and is where discussions of cosmic |
| 260 |
significance are held (most Working Groups have their own mailing |
| 261 |
lists for discussions relating to their work). To join the IETF |
| 262 |
announcement list, send a request to: |
| 263 |
|
| 264 |
[email protected] |
| 265 |
|
| 266 |
To join the IETF discussion list, send a request to: |
| 267 |
|
| 268 |
[email protected] |
| 269 |
|
| 270 |
To join both of the lists, simply send a single message, to either |
| 271 |
"-request" address, and indicate that you'd like to join both lists. |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Internet Engineering Task Force [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 279 |
|
| 280 |
|
| 281 |
Do not, ever, under any circumstances, for any reason, send a request |
| 282 |
to join a list to the list itself! The thousands of people on the |
| 283 |
list don't need, or want, to know when a new person joins. |
| 284 |
Similarly, when changing email addresses or leaving a list, send your |
| 285 |
request only to the "-request" address, not to the main list. This |
| 286 |
means you!! |
| 287 |
|
| 288 |
The IETF discussion list is unmoderated. This means that anyone can |
| 289 |
express their opinions about issues affecting the Internet. However, |
| 290 |
it is not a place for companies or individuals to solicit or |
| 291 |
advertise. Only the Secretariat can send a message to the |
| 292 |
announcement list. |
| 293 |
|
| 294 |
Even though the IETF mailing lists "represent" the IETF membership at |
| 295 |
large, it is important to note that attending an IETF meeting does |
| 296 |
not automatically include addition to either mailing list. |
| 297 |
|
| 298 |
|
| 299 |
Registration |
| 300 |
|
| 301 |
As previously mentioned, all meeting announcements are sent to the |
| 302 |
IETF announcement list. Within the IETF meeting announcement is a |
| 303 |
Registration Form and complete instructions for registering, |
| 304 |
including, of course, the cost. The Secretariat highly recommends |
| 305 |
that attendees preregister. Early registration, which ends about one |
| 306 |
month before the meeting, carries a lower registration fee. As the |
| 307 |
size of the meetings has grown, so has the length of the lines at the |
| 308 |
registration desk. Fortunately, there are three lines: |
| 309 |
"preregistered and prepaid" (which moves very quickly), |
| 310 |
"preregistered and on-site payment" (which moves a little more |
| 311 |
slowly), and "registration and on-site payment" (take a guess). |
| 312 |
|
| 313 |
Registration is open all week. However, the Secretariat highly |
| 314 |
recommends that attendees arrive for early registration, beginning at |
| 315 |
6:00 P.M. (meeting local time), on the Sunday before the opening |
| 316 |
plenary. Not only will there be fewer people, but there will also be |
| 317 |
a reception at which people can get a byte to eat. If the |
| 318 |
registration lines are long, one can eat first and try again when the |
| 319 |
lines are shorter. |
| 320 |
|
| 321 |
Registered attendees (and there isn't any other kind) receive a |
| 322 |
Registration Packet. It contains a general orientation sheet, the |
| 323 |
At-A-Glance sheet, a list of Working Group acronyms, the most recent |
| 324 |
Agenda, and a name tag. The At-A-Glance is a very important |
| 325 |
reference and is used throughout the week. It contains Working |
| 326 |
Group/BOF room assignments and a map of room locations. Attendees |
| 327 |
who prepaid will also find their receipt in their packet. |
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Internet Engineering Task Force [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 335 |
|
| 336 |
|
| 337 |
Newcomers' Orientation |
| 338 |
|
| 339 |
Newcomers are encouraged to attend the IETF Newcomers' Orientation. |
| 340 |
As the name implies, it is an orientation for first time attendees to |
| 341 |
IETF meetings. The orientation is organized and conducted by the |
| 342 |
IETF Secretariat and is intended to provide useful introductory |
| 343 |
information. The Secretariat tries to keep the orientation session |
| 344 |
informal, and is usually successful at it. |
| 345 |
|
| 346 |
The orientation is typically 30-45 minutes long and covers a number |
| 347 |
of topics: what's in the attendee packets, what all the dots on name |
| 348 |
tags mean, and how to read the At-A-Glance. There is also discussion |
| 349 |
about the organization of the IETF: Working Groups and their Areas, |
| 350 |
and the IESG. There is ample time at the end for questions. The |
| 351 |
Secretariat also provides handouts which include the text from the |
| 352 |
IETF Overview and a list of important files maintained on the IETF |
| 353 |
Shadow directories. |
| 354 |
|
| 355 |
The orientation is held on Sunday afternoon and ends about 30 mintues |
| 356 |
before the Registration Reception. However, attending the |
| 357 |
orientation does NOT mean you can go to the reception early! |
| 358 |
|
| 359 |
|
| 360 |
Dress Code |
| 361 |
|
| 362 |
Since attendees must wear their name tags, they must also wear shirts |
| 363 |
or blouses. Pants or skirts are also highly recommended. Seriously |
| 364 |
though, many newcomers are often embarrassed when they show up Monday |
| 365 |
morning in suits, to discover that everybody else is wearing T- |
| 366 |
shirts, jeans (shorts, if weather permits) and sandals. There are |
| 367 |
those in the IETF who refuse to wear anything other than suits. |
| 368 |
Fortunately, they are well known (for other reasons) so they are |
| 369 |
forgiven this particular idiosyncrasy. The general rule is "dress |
| 370 |
for the weather" (unless you plan to work so hard that you won't go |
| 371 |
outside, in which case, "dress for comfort" is the rule!). |
| 372 |
|
| 373 |
|
| 374 |
Seeing Spots Before Your Eyes |
| 375 |
|
| 376 |
Some of the people at the IETF will have a little colored dot on |
| 377 |
their name tag. A few people have more than one. These dots |
| 378 |
identify people who are silly enough to volunteer to do a lot of |
| 379 |
extra work. The colors have the following meanings: |
| 380 |
|
| 381 |
red - IAB member |
| 382 |
yellow - IESG member |
| 383 |
blue - Working Group/BOF chair |
| 384 |
green - Local host |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Internet Engineering Task Force [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 391 |
|
| 392 |
|
| 393 |
Local hosts are the people who can answer questions about the |
| 394 |
terminal room, restaurants, and points of interest in the area. |
| 395 |
|
| 396 |
Some people have Gold Stars on their name tags. The stars indicate |
| 397 |
that those people chaired Working Groups or BOFs in the IETF Area |
| 398 |
which submitted all of its Working Group/BOF Minutes and Area Report |
| 399 |
from the previous meeting first. The stars are the Secretariat's way |
| 400 |
of saying "Thank You" for providing the necessary information |
| 401 |
quickly. |
| 402 |
|
| 403 |
It is important that newcomers to the IETF not be afraid to strike up |
| 404 |
conversations with people who wear these dots. If the IAB and IESG |
| 405 |
members, and Working Group and BOF chairs, didn't want to talk to |
| 406 |
anybody, they wouldn't be wearing the dots in the first place. |
| 407 |
|
| 408 |
To make life simpler for the Secretariat, Registration Packets are |
| 409 |
also coded with little colored dots. These are only for Secretariat |
| 410 |
use, so nobody else needs to worry about them. Please, don't peel |
| 411 |
them off your packet and put them on your name tag. |
| 412 |
|
| 413 |
|
| 414 |
Terminal Room |
| 415 |
|
| 416 |
One of the most important (depending on your point of view) things |
| 417 |
the local host does is provide Internet access to the meeting |
| 418 |
attendees. In general, the connectivity is excellent. This is |
| 419 |
entirely due to the Olympian efforts of the local hosts, and their |
| 420 |
ability to beg, borrow and steal. The people and companies who |
| 421 |
donate their equipment, services, and time are to be heartily |
| 422 |
congratulated and thanked. |
| 423 |
|
| 424 |
While preparation far in advance of the meeting is encouraged, there |
| 425 |
may be some unavoidable "last minute" things which can be |
| 426 |
accomplished in the terminal room. It may also be useful to people |
| 427 |
who need to make trip reports or status reports while things are |
| 428 |
still fresh in their minds. |
| 429 |
|
| 430 |
|
| 431 |
Social Event |
| 432 |
|
| 433 |
Another of the most important things organized and managed by the |
| 434 |
local hosts is the IETF social event. The social event has become |
| 435 |
something of a tradition at the IETF meetings. It has been |
| 436 |
immortalized by Marshal Rose with his reference to "many fine lunches |
| 437 |
and dinners" [ROSE], and by Claudio and Julia Topolcic with their |
| 438 |
rendition of "Nerds in Paradise" on a pink T-shirt. |
| 439 |
|
| 440 |
Newcomers to the IETF are encouraged to attend the social event. |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Internet Engineering Task Force [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 447 |
|
| 448 |
|
| 449 |
Everyone is encouraged to wear their name tags. The social event is |
| 450 |
designed to give people a chance to meet on a social, rather than |
| 451 |
technical, level. |
| 452 |
|
| 453 |
Sometimes, the social event is a computer or high-tech related event. |
| 454 |
At the Boston IETF, for example, the social was dinner at the |
| 455 |
Computer Museum. Other times, the social might be a dinner cruise or |
| 456 |
a trip to an art gallery. |
| 457 |
|
| 458 |
|
| 459 |
Agenda |
| 460 |
|
| 461 |
The Agenda for the IETF meetings is a very fluid thing. It is sent, |
| 462 |
in various forms, to the IETF announcement list three times prior to |
| 463 |
the meeting. The final Agenda is included in the Registration |
| 464 |
Packets. Of course, "final" in the IETF doesn't mean the same thing |
| 465 |
as it does elsewhere in the world. The final Agenda is simply the |
| 466 |
version that went to the printers. |
| 467 |
|
| 468 |
The Secretariat will announce Agenda changes during the morning |
| 469 |
plenary sessions. Changes will also be posted on the bulletin board |
| 470 |
near the IETF Registration Table (not the hotel registration desk). |
| 471 |
|
| 472 |
Assignments for breakout rooms (that's where the Working Groups and |
| 473 |
BOFs meet) and a map showing the room locations make up the At-A- |
| 474 |
Glance sheet (included in the Registration Packets). Room |
| 475 |
assignments are as flexible as the Agenda. Some Working Groups meet |
| 476 |
multiple times during a meeting and every attempt is made to have a |
| 477 |
Working Group meet in the same room each session. Room assignment |
| 478 |
changes are not necessarily permanent for the week. Always check the |
| 479 |
At-A-Glance first, then the bulletin board. When in doubt, check |
| 480 |
with a member of the Secretariat at the Registration Table. |
| 481 |
|
| 482 |
|
| 483 |
Other General Things |
| 484 |
|
| 485 |
The opening Plenary on Monday morning is the most heavily attended |
| 486 |
session. It is where important introductory remarks are made, so |
| 487 |
people are encouraged to attend. |
| 488 |
|
| 489 |
The IETF Secretariat, and IETFers in general, are very approachable. |
| 490 |
Never be afraid to approach someone and introduce yourself. Also, |
| 491 |
don't be afraid to ask questions, especially when it comes to jargon |
| 492 |
and acronyms! |
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Internet Engineering Task Force [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 503 |
|
| 504 |
|
| 505 |
Hallway conversations are very important. A lot of very good work |
| 506 |
gets done by people who talk together between meetings and over |
| 507 |
lunches and dinners. Every minute of the IETF can be considered work |
| 508 |
time (much to some people's dismay). |
| 509 |
|
| 510 |
A "Bar BOF" is an unofficial get-together, usually in the late |
| 511 |
evening, during which a lot of work gets done over drinks. |
| 512 |
|
| 513 |
It's unwise to get between a hungry IETFer (and there isn't any other |
| 514 |
kind) and coffee break brownies and cookies, no matter how |
| 515 |
interesting a hallway conversation is. |
| 516 |
|
| 517 |
IETFers are fiercely independent. It's safe to question opinions and |
| 518 |
offer alternatives, but don't expect an IETFer to follow orders. |
| 519 |
|
| 520 |
The IETF, and the plenary sessions in particular, are not places for |
| 521 |
vendors to try to sell their wares. People can certainly answer |
| 522 |
questions about their company and its products, but bear in mind that |
| 523 |
the IETF is not a trade show. This does not preclude people from |
| 524 |
recouping costs for IETF related T-shirts, buttons and pocket |
| 525 |
protectors. |
| 526 |
|
| 527 |
|
| 528 |
Registration Bullets |
| 529 |
|
| 530 |
Registration is such an important topic, that it's in this RFC twice! |
| 531 |
This is the "very important registration bullets" section. |
| 532 |
|
| 533 |
o To attend an IETF meeting: you have to register and you have to |
| 534 |
pay the registration fee. |
| 535 |
|
| 536 |
o All you need to do to be registered is to send in a completed |
| 537 |
Registration Form. |
| 538 |
|
| 539 |
o You may register by mail, email or fax. Generally, email and fax |
| 540 |
registration forms will be accepted until 1:00 P.M. ET on the |
| 541 |
Friday before the meeting. |
| 542 |
|
| 543 |
o You may preregister and pay, preregister and pay later, |
| 544 |
preregister and pay on-site, or register and pay on-site. |
| 545 |
|
| 546 |
o To get the lower registration fee, you must register by the early |
| 547 |
registration deadline (about one month before the meeting). You |
| 548 |
can still pay later or on-site. |
| 549 |
|
| 550 |
o If you don't register by the early registration deadline, a late |
| 551 |
fee is added. |
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Internet Engineering Task Force [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 559 |
|
| 560 |
|
| 561 |
o Everyone pays the same fees. There are no educational or group |
| 562 |
discounts. There are no discounts for attending only part of the |
| 563 |
week. |
| 564 |
|
| 565 |
o Register only ONE person per registration form. Substitutions are |
| 566 |
NOT allowed. |
| 567 |
|
| 568 |
o You may register then pay later, but you may not pay then register |
| 569 |
later. Payment MUST be accompanied by a completed registration |
| 570 |
form. |
| 571 |
|
| 572 |
o Purchase orders are NOT accepted. DD Form 1556 is accepted. |
| 573 |
Invoice for payment cannot be accepted. |
| 574 |
|
| 575 |
o Refunds are subject to a $20 service charge. Late fees will not |
| 576 |
be refunded. |
| 577 |
|
| 578 |
o The registration fee covers a copy of the meeting's Proceedings, |
| 579 |
Sunday evening reception (cash bar), a daily continental |
| 580 |
breakfast, and daily coffee breaks. |
| 581 |
|
| 582 |
|
| 583 |
Mailing Lists and Archives |
| 584 |
|
| 585 |
As previously mentioned, the IETF announcement and discussion mailing |
| 586 |
lists are the central mailing lists for IETF activities. However, |
| 587 |
there are many other mailing lists related to IETF work. For |
| 588 |
example, every Working Group has its own discussion list. In |
| 589 |
addition, there are some long-term technical debates which have been |
| 590 |
moved off of the IETF list onto lists created specifically for those |
| 591 |
topics. It is highly recommended that everybody follow the |
| 592 |
discussions on the mailing lists of the Working Groups which they |
| 593 |
wish to attend. The more work that is done on the mailing lists, the |
| 594 |
less work that will need to be done at the meeting, leaving time for |
| 595 |
cross pollination (i.e., attending Working Groups outside one's |
| 596 |
primary area of interest in order to broaden one's perspective). |
| 597 |
|
| 598 |
The mailing lists also provide a forum for those who wish to follow, |
| 599 |
or contribute to, the Working Groups' efforts, but cannot attend the |
| 600 |
IETF meetings. |
| 601 |
|
| 602 |
All IETF discussion lists have a "-request" address which handles the |
| 603 |
administrative details of joining and leaving the list. It is |
| 604 |
generally frowned upon when such administrivia appears on the |
| 605 |
discussion mailing list. |
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Internet Engineering Task Force [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 615 |
|
| 616 |
|
| 617 |
Most IETF discussion lists are archived. That is, all of the |
| 618 |
messages sent to the list are automatically stored on a host for |
| 619 |
anonymous FTP access. To find out where a particular list is |
| 620 |
archived, send a message to the list's "-request" address, NOT to the |
| 621 |
list itself. |
| 622 |
|
| 623 |
|
| 624 |
Important Email Addresses |
| 625 |
|
| 626 |
There are some important IETF email addresses with which everyone |
| 627 |
should be familiar. They are all located at "cnri.reston.va.us" |
| 628 |
(e.g., "[email protected]"). To personalize things, the |
| 629 |
names of the Secretariat staff who respond to the messages are given |
| 630 |
for each address. |
| 631 |
|
| 632 |
o ietf-info general queries about the IETF - |
| 633 |
Cynthia Clark, Debra Legare, John Stewart, |
| 634 |
and Megan Davies Walnut |
| 635 |
|
| 636 |
o ietf-rsvp queries about meeting locations and fees, |
| 637 |
emailed Registration Forms - |
| 638 |
Debra Legare |
| 639 |
|
| 640 |
o proceedings queries about previous Proceedings availability, |
| 641 |
orders for copies of the Proceedings - |
| 642 |
Debra Legare |
| 643 |
|
| 644 |
o ietf-announce-request |
| 645 |
requests to join/leave IETF announcement list - |
| 646 |
Cynthia Clark |
| 647 |
|
| 648 |
o ietf-request requests to join/leave IETF discussion list - |
| 649 |
Cynthia Clark |
| 650 |
|
| 651 |
o internet-drafts Internet-Draft submissions and queries - |
| 652 |
Cynthia Clark |
| 653 |
|
| 654 |
o iesg-secretary John Stewart |
| 655 |
|
| 656 |
o ietf-secretariat Steve Coya |
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Internet Engineering Task Force [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 671 |
|
| 672 |
|
| 673 |
IETF Proceedings |
| 674 |
|
| 675 |
The IETF Proceedings are compiled in the two months following each |
| 676 |
IETF meeting. The Proceedings usually start with a message from |
| 677 |
Steve Coya, the Executive Director of the IETF. Each contains the |
| 678 |
final (hindsight) Agenda, an IETF overview, a report from the IESG, |
| 679 |
Area and Working Group reports, network status briefings, slides from |
| 680 |
the protocol and technical presentations, and the attendees list. |
| 681 |
The attendees list includes an attendee's name, affiliation, work |
| 682 |
phone number, work fax number, and email address, as provided on the |
| 683 |
Registration Form. |
| 684 |
|
| 685 |
A copy of the Proceedings will be sent to everyone who registered for |
| 686 |
the IETF. The cost is included in the registration fee. The |
| 687 |
Proceedings are sent to the mailing addresses provided on the |
| 688 |
Registration Forms. |
| 689 |
|
| 690 |
For those who could not attend a meeting but would like a copy of the |
| 691 |
Proceedings send a check for $35 (made payable to CNRI) to: |
| 692 |
|
| 693 |
Corporation for National Research Initiatives |
| 694 |
Attn: Accounting Department - IETF Proceedings |
| 695 |
1895 Preston White Drive, Suite 100 |
| 696 |
Reston, VA 22091 |
| 697 |
|
| 698 |
Please indicate which meeting Proceedings you would like to receive |
| 699 |
by specifying the meeting date (e.g., July 1993) or meeting number |
| 700 |
and location (e.g., 27th meeting in Amsterdam). Availability of |
| 701 |
previous meetings' Proceedings is limited, so ask BEFORE sending |
| 702 |
payment. |
| 703 |
|
| 704 |
|
| 705 |
InterNIC Archives |
| 706 |
|
| 707 |
There is a tremendous amount of material available for those who |
| 708 |
follow the work of the IETF. To make it easier to know what to read |
| 709 |
to prepare for a meeting, the InterNIC has established a document |
| 710 |
archive. Beginning about one month prior to an IETF meeting, Working |
| 711 |
Group/BOF Chairs and Area Directors put documents relevent to the |
| 712 |
discussions to be held into the archives. Those people who plan to |
| 713 |
attend a Working Group/BOF session should check the archives for |
| 714 |
documents which need to be read. The documents are left in the |
| 715 |
archives for about two months after the end of the IETF meeting. |
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Internet Engineering Task Force [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 727 |
|
| 728 |
|
| 729 |
On the host "ds.internic.net", documents are stored in the directory |
| 730 |
"/pub/current-ietf-docs" under subdirectories named for each Area and |
| 731 |
then for each Working Group. For example, a document for the NISI |
| 732 |
Working Group, which is in the User Services Area, would be stored as |
| 733 |
"current-ietf-docs/usv/nisi/nisi-doc1.txt". Each Area will also have |
| 734 |
a subdirectory called "bof", where documents to be discussed in BOF |
| 735 |
sessions will be placed. A directory called "plenary" will also be |
| 736 |
created under "/pub/current-ietf-docs" to put documents or viewgraphs |
| 737 |
related to a plenary session. Any filename conflicts will be |
| 738 |
resolved by the archive administrator working with the submitter of |
| 739 |
the document via email. |
| 740 |
|
| 741 |
It is important to note that the service is provided by the InterNIC |
| 742 |
and that the documents are submitted by the people who work on them. |
| 743 |
The IETF Secretariat does not manage or monitor the archive service. |
| 744 |
|
| 745 |
Access via anonymous FTP: |
| 746 |
|
| 747 |
Anonymous FTP to ds.internic.net |
| 748 |
Change directory to /pub/current-ietf-docs |
| 749 |
Browse and get the document of interest |
| 750 |
|
| 751 |
Access via GOPHER (from a Gopher client): |
| 752 |
|
| 753 |
Point to gopher.internic.net |
| 754 |
Select menu item 4, InterNIC Directory and Database Services ... |
| 755 |
Then menu item named "Internet Documentation (RFC's FYI's, etc.)/" |
| 756 |
Lastly menu item named "Current IETF Conference Documents (...)/" |
| 757 |
|
| 758 |
If you do not have a Gopher client, use the InterNIC's public-access |
| 759 |
Gopher client. Simply telnet to "gopher.internic.net" and login as |
| 760 |
"gopher" (no password required). |
| 761 |
|
| 762 |
|
| 763 |
Be Prepared |
| 764 |
|
| 765 |
This topic cannot be stressed enough. As the IETF grows, it becomes |
| 766 |
more and more important for attendees to arrive prepared for the |
| 767 |
Working Group meetings they plan to attend. This doesn't apply only |
| 768 |
to newcomers; everybody should come prepared. |
| 769 |
|
| 770 |
Being prepared means having read the documents which the Working |
| 771 |
Group or BOF Chair has distributed. It means having followed the |
| 772 |
discussions on the Working Group's mailing list or having reviewed |
| 773 |
the archives. For the Working Group/BOF Chairs, it means getting all |
| 774 |
of the documents out early (i.e., several weeks) to give everybody |
| 775 |
time to read them and announcing an agenda and sticking to it. |
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Internet Engineering Task Force [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 783 |
|
| 784 |
|
| 785 |
At the Chair's discretion, some time may be devoted to bringing new |
| 786 |
Working Group attendees up to speed. In fact, long lived Working |
| 787 |
Groups have occasionally held entire sessions which were introductory |
| 788 |
in nature. As a rule, however, a Working Group is not the place to |
| 789 |
go for training. Observers are always welcome, but they must realize |
| 790 |
that the work effort cannot be delayed for education. Anyone wishing |
| 791 |
to attend a Working Group for the first time might seek out the Chair |
| 792 |
prior to the meeting and ask for some introduction. |
| 793 |
|
| 794 |
Another thing, for everybody, to consider is that Working Groups go |
| 795 |
through phases. In the initial phase (say, the first two meetings), |
| 796 |
all ideas are welcome. The idea is to gather all the possible |
| 797 |
solutions together for consideration. In the development phase, a |
| 798 |
solution is chosen and developed. Trying to reopen issues which were |
| 799 |
decided more than a couple of meetings back is considered bad form. |
| 800 |
The final phase (the last two meetings) is where the "spit and |
| 801 |
polish" are applied to the architected solution. This is not the |
| 802 |
time to suggest architectural changes or open design issues already |
| 803 |
resolved. It's a bad idea to wait until the last minute to speak out |
| 804 |
if a problem is discovered. This is especially true for people whose |
| 805 |
excuse is that they hadn't read the documents until the day before a |
| 806 |
comments period ended. |
| 807 |
|
| 808 |
Time at the IETF meetings is a precious thing. Working Groups are |
| 809 |
encouraged to meet between IETF meetings, either in person or by |
| 810 |
video or telephone conference. Doing as much work as possible over |
| 811 |
the mailing lists would also reduce the amount of work which must be |
| 812 |
done at the meeting. |
| 813 |
|
| 814 |
RFCs and Internet-Drafts |
| 815 |
|
| 816 |
Originally, RFCs were just what the name implies; they were requests |
| 817 |
for comments. The early RFCs were messages between the ARPANET |
| 818 |
architects about how to resolve certain problems. Over the years, |
| 819 |
RFCs became more formal. It reached the point that they were being |
| 820 |
cited as standards, even when they weren't. |
| 821 |
|
| 822 |
To help clear up some confusion, there are now two special sub-series |
| 823 |
within the RFCs: FYIs and STDs. The For Your Information RFC sub- |
| 824 |
series was created to document overviews and topics which are |
| 825 |
introductory. Frequently, FYIs are created by groups within the IETF |
| 826 |
User Services Area. The STD RFC sub-series was created to identify |
| 827 |
those RFCs which do in fact specify Internet Standards. |
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Internet Engineering Task Force [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 839 |
|
| 840 |
|
| 841 |
Every RFC, including FYIs and STDs, have an RFC number by which they |
| 842 |
are indexed and by which they can be retrieved. FYIs and STDs have |
| 843 |
FYI numbers and STD numbers, respectively, in addition to RFC |
| 844 |
numbers. This makes it easier for a new Internet user, for example, |
| 845 |
to find all of the helpful, informational documents by looking for |
| 846 |
the FYIs amongst all the RFCs. If an FYI or STD is revised, its RFC |
| 847 |
number will change, but its FYI or STD number will remain contant for |
| 848 |
ease of reference. |
| 849 |
|
| 850 |
There is also an RTR subseries of RFCs for Reseaux Associes pour la |
| 851 |
Recherche Europeenne (RARE) Technical Reports. These are technical |
| 852 |
reports developed in the RARE community that are published as RFCs to |
| 853 |
provide easy access to the general Internet community. |
| 854 |
|
| 855 |
Internet-Drafts (I-D) are working documents of the IETF. Any group |
| 856 |
(e.g., Working Group, BOF) or individual may submit a document for |
| 857 |
distribution as an I-D. An I-D is valid for six months. Guidelines |
| 858 |
require that an expiration date appear on every page of an I-D. An |
| 859 |
I-D may be updated, replaced or obsoleted at any time. It is not |
| 860 |
appropriate to use I-Ds as reference material or to cite them, other |
| 861 |
than as a "working draft" or "work in progress". |
| 862 |
|
| 863 |
For additional information, read the following documents: |
| 864 |
|
| 865 |
o Request for Comments on Request for Comments [<a href="./rfc1111">RFC1111</a>] |
| 866 |
o F.Y.I. on F.Y.I: Introduction to the F.Y.I notes [FYI1] |
| 867 |
o Introduction to the STD Notes [<a href="./rfc1311">RFC1311</a>] |
| 868 |
o Guidelines to Authors of Internet Drafts [GAID] |
| 869 |
o The Internet Activities Board [<a href="./rfc1160">RFC1160</a>] |
| 870 |
o The Internet Standards Process [<a href="./rfc1310">RFC1310</a>] |
| 871 |
o Internet Official Protocol Standards [STD1] |
| 872 |
|
| 873 |
|
| 874 |
Frequently Asked Questions (and Their Answers) |
| 875 |
|
| 876 |
Q: My Working Group moved this morning. Where is it now? |
| 877 |
A: Not all room assignment changes are permanent. Check the At-A- |
| 878 |
Glance sheet and the message board for announcements. |
| 879 |
|
| 880 |
Q: Where is Room A? |
| 881 |
A: Check the map on the At-A-Glance sheet. An enlarged version is on |
| 882 |
the bulletin board. |
| 883 |
|
| 884 |
Q: Where can I get a copy of the Proceedings? |
| 885 |
A: The Proceedings are automatically sent to each attendee about two |
| 886 |
months after the meeting. |
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Internet Engineering Task Force [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 895 |
|
| 896 |
|
| 897 |
Q: When is on-site registration? |
| 898 |
A: The IETF registration table is set up Sunday night from 6:00 p.m. |
| 899 |
- 8:00 p.m. and Monday - Thursday from about 8:30 a.m. - 6:00 p.m. |
| 900 |
Starting time in the mornings and Friday's hours may vary |
| 901 |
depending on the meeting schedule. |
| 902 |
|
| 903 |
Q: Where is lunch served? |
| 904 |
A: The meeting does not include lunch or dinner. Ask a local host |
| 905 |
(somebody with a green dotted badge) for a recommendation. |
| 906 |
|
| 907 |
Q: Where are the receipts for the social event? |
| 908 |
A: The social is not managed by the IETF Secretariat. Ask a local |
| 909 |
host. |
| 910 |
|
| 911 |
|
| 912 |
Pointers to Useful Documents and Files |
| 913 |
|
| 914 |
This is a list of documents and files that provide useful information |
| 915 |
about the IETF meetings, Working Groups, and documentation. These |
| 916 |
files reside in the "ietf" directory on the Anonymous FTP sites |
| 917 |
listed below. Files with names beginning with "0" (zero) pertain to |
| 918 |
IETF meetings. These may refer to a recently held meeting if the |
| 919 |
first announcement of the next meeting has not yet been sent to the |
| 920 |
IETF mailing list. Files with names beginning with "1" (one) contain |
| 921 |
general IETF information. This is only a partial list of the |
| 922 |
available files. |
| 923 |
|
| 924 |
o 0mtg-agenda.txt Agenda for the meeting |
| 925 |
o 0mtg-at-a-glance.txt Logistics information for the meeting |
| 926 |
o 0mtg-rsvp.txt Meeting registration form |
| 927 |
o 0mtg-sites.txt Future meeting sites and dates |
| 928 |
o 0mtg-traveldirections.txt Directions to the meeting site |
| 929 |
o 0tao.txt This document |
| 930 |
|
| 931 |
o 1directories.txt The IETF Shadow directory locations and |
| 932 |
contents. |
| 933 |
o 1id-guidelines.txt Guidelines to Authors of Internet-Drafts |
| 934 |
Contains information on writing and |
| 935 |
submitting I-Ds. |
| 936 |
o 1ietf-description.txt Short description of the IETF and IESG, |
| 937 |
including a list of Area Directors. |
| 938 |
o 1nonwg-discuss.txt A list of mailing lists created to |
| 939 |
discuss specific IETF issues. |
| 940 |
o 1proceedings-request.txt A Proceedings order form for the |
| 941 |
current and previous meetings. |
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Internet Engineering Task Force [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 951 |
|
| 952 |
|
| 953 |
o 1wg-summary.txt List of all Working Groups, by Area, |
| 954 |
including the name and address of the |
| 955 |
chairperson, and the mailing list |
| 956 |
address. |
| 957 |
o 1wg-summary-by-acronym Same as above, but sorted by the |
| 958 |
Working Groups' acronyms. |
| 959 |
o 1wg-charter.txt Abbreviated versions of all current |
| 960 |
Working Group charters. |
| 961 |
o 1wg-charters-by-acronym Same as above, but sorted by the |
| 962 |
Working Groups' acronyms. |
| 963 |
|
| 964 |
Additionally, the full charters and minutes of the Working Groups and |
| 965 |
BOFs are archived in the "ietf" directory. |
| 966 |
|
| 967 |
All of these documents are available by anonymous FTP from the |
| 968 |
following primary sites (there may be closer shadow sites, so check |
| 969 |
with your network administrator): |
| 970 |
|
| 971 |
o North America Address: ds.internic.net (198.49.45.10) |
| 972 |
o Pacific Rim Address: munnari.oz.au (128.250.1.21) |
| 973 |
o Europe Address: nic.nordu.net (192.36.148.17) |
| 974 |
|
| 975 |
These files are also available through the Internet Gopher at |
| 976 |
"ietf.cnri.reston.va.us". |
| 977 |
|
| 978 |
Residing on the same archive sites are the RFCs and Internet-Drafts. |
| 979 |
They are in the "rfc" and "internet-drafts" directories, |
| 980 |
respectively. The file "rfc-index.txt" contains the latest |
| 981 |
information about the RFCs (e.g., which have been obsoleted by |
| 982 |
which). In general, only the newest version of an Internet-Draft is |
| 983 |
available. |
| 984 |
|
| 985 |
All of the files, RFCs and Internet-Drafts are also available via |
| 986 |
email from various mail servers. To to get the IETF agenda, |
| 987 |
Internet-Draft abstracts and <a href="./rfc1150">RFC 1150</a> from the mail server at the |
| 988 |
InterNIC, for example, you would send the following message: |
| 989 |
|
| 990 |
To: [email protected] Message header |
| 991 |
Subject: anything you want |
| 992 |
|
| 993 |
FILE /ietf/0mtg-agenda.txt Body of the message |
| 994 |
FILE /internet-drafts/1id-abstracts.txt |
| 995 |
FILE /rfc/rfc1150.txt |
| 996 |
PATH [email protected] |
| 997 |
|
| 998 |
Where: FILE specifies the name of a file to be returned and PATH |
| 999 |
specifies the email address to which the file(s) should be sent. |
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Internet Engineering Task Force [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
RFCs may also be retrieved, using email, from ISI's RFC-Info server |
| 1010 |
at "[email protected]". To get a specific RFC, include the following |
| 1011 |
in the body of the message: |
| 1012 |
|
| 1013 |
Retrieve: RFC |
| 1014 |
Doc-ID: <a href="./rfc0951">RFC0951</a> |
| 1015 |
|
| 1016 |
This example would cause a copy of <a href="./rfc951">RFC 951</a> (the leading zero in the |
| 1017 |
Doc-ID is required) to be emailed to the requestor. To get a list of |
| 1018 |
available RFCs which match certain criteria, include the following in |
| 1019 |
the body of the message: |
| 1020 |
|
| 1021 |
LIST: RFC |
| 1022 |
Keywords: Gateway |
| 1023 |
|
| 1024 |
This example would email a list of all RFCs with "Gateway" in the |
| 1025 |
title, or as an assigned keyword, to the requestor. To get |
| 1026 |
information on other ways to get RFCs: |
| 1027 |
|
| 1028 |
HELP: ways_to_get_rfcs |
| 1029 |
|
| 1030 |
Tao |
| 1031 |
|
| 1032 |
Pronounced "Dow", Tao means "the Way." It is the basic principle |
| 1033 |
behind the teachings of Lao-tse, a Chinese master. Its familiar |
| 1034 |
symbol is the black and white Yin-Yang circle. |
| 1035 |
|
| 1036 |
|
| 1037 |
IETF Area Abbreviations |
| 1038 |
|
| 1039 |
APP Applications |
| 1040 |
INT Internet Services |
| 1041 |
MGT Network Management |
| 1042 |
OPS Operational Requirements |
| 1043 |
RTG Routing |
| 1044 |
SAP Service Applications |
| 1045 |
SEC Security |
| 1046 |
TSV Transport |
| 1047 |
USV User Services |
| 1048 |
|
| 1049 |
|
| 1050 |
|
| 1051 |
|
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Internet Engineering Task Force [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
Acronyms |
| 1066 |
|
| 1067 |
:-) Smiley face |
| 1068 |
ANSI American National Standards Institute |
| 1069 |
ARPA Advanced Research Projects Agency |
| 1070 |
ARPANET Advanced Research Projects Agency Network |
| 1071 |
AS Autonomous System |
| 1072 |
ATM Asynchronous Transfer Mode |
| 1073 |
BGP Border Gateway Protocol |
| 1074 |
BOF Birds Of a Feather |
| 1075 |
BSD Berkeley Software Distribution |
| 1076 |
BTW By The Way |
| 1077 |
CCIRN Coordinating Committee for Intercontinental Research Networks |
| 1078 |
CCITT International Telegraph and Telephone Consultative Comittee |
| 1079 |
CIDR Classless Inter-Domain Routing |
| 1080 |
CIX Commercial Information Exchange |
| 1081 |
CNI Coalition for Networked Information |
| 1082 |
CREN The Corporation for Research and Educational Networking |
| 1083 |
DARPA U.S. Defense Advanced Research Projects Agency (now ARPA) |
| 1084 |
DDN U.S. Defense Data Network |
| 1085 |
DISA U.S. Defense Information Systems Agency |
| 1086 |
EGP Exterior Gateway Protocol |
| 1087 |
FAQ Frequently Asked Question |
| 1088 |
FARNET Federation of American Research NETworks |
| 1089 |
FIX U.S. Federal Information Exchange |
| 1090 |
FNC U.S. Federal Networking Council |
| 1091 |
FQDN Fully Qualified Domain Name |
| 1092 |
FYI For Your Information (RFC) |
| 1093 |
GOSIP U.S. Government OSI Profile |
| 1094 |
IAB Internet Architecture Board |
| 1095 |
IANA Internet Assigned Numbers Authority |
| 1096 |
I-D Internet-Draft |
| 1097 |
IEN Internet Experiment Note |
| 1098 |
IESG Internet Engineering Steering Group |
| 1099 |
IETF Internet Engineering Task Force |
| 1100 |
IGP Interior Gateway Protocol |
| 1101 |
IMHO In My Humble Opinion |
| 1102 |
IMR Internet Monthly Report |
| 1103 |
InterNIC Internet Network Information Center |
| 1104 |
IR Internet Registry |
| 1105 |
IRSG Internet Research Steering Group |
| 1106 |
IRTF Internet Research Task Force |
| 1107 |
ISO International Organization for Standardization |
| 1108 |
ISOC Internet Society |
| 1109 |
ISODE ISO Development Environment |
| 1110 |
ITU International Telecommunication Union |
| 1111 |
MIB Management Information Base |
| 1112 |
MIME Multipurpose Internet Mail Extensions |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Internet Engineering Task Force [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
NIC Network Information Center |
| 1122 |
NIS Network Information Services |
| 1123 |
NIST National Institute of Standards and Technology |
| 1124 |
NOC Network Operations Center |
| 1125 |
NREN National Research and Education Network |
| 1126 |
NSF National Science Foundation |
| 1127 |
OSI Open Systems Interconnection |
| 1128 |
PEM Privacy Enhanced Mail |
| 1129 |
PTT Postal, Telegraph and Telephone |
| 1130 |
RARE Reseaux Associes pour la Recherche Europeenne |
| 1131 |
RFC Request For Comments |
| 1132 |
RIPE Reseaux IP Europeenne |
| 1133 |
SIG Special Interest Group |
| 1134 |
STD Standard (RFC) |
| 1135 |
TLA Three Letter Acronym |
| 1136 |
TTFN Ta-Ta For Now |
| 1137 |
UTC Universal Time Coordinated |
| 1138 |
WG Working Group |
| 1139 |
WRT With Respect To |
| 1140 |
WYSIWYG What You See is What You Get |
| 1141 |
|
| 1142 |
References |
| 1143 |
|
| 1144 |
FYI1 Malkin, G., and J. Reynolds, "F.Y.I. on F.Y.I.", FYI 1, <a href="./rfc1150">RFC</a> |
| 1145 |
<a href="./rfc1150">1150</a>, Proteon, USC/Information Sciences Institute, March |
| 1146 |
1990. |
| 1147 |
|
| 1148 |
GAID "Guidelines to Authors of Internet Drafts", |
| 1149 |
1id-guidelines.txt. |
| 1150 |
|
| 1151 |
ROSE Rose, M., "The Open Book: A Practical Perspective on OSI", |
| 1152 |
Prentice Hall, Englewood Cliffs, NJ, 1989. |
| 1153 |
|
| 1154 |
<a href="./rfc1111">RFC1111</a> Postel, J., "Request for Comments on Request for Comments", |
| 1155 |
<a href="./rfc1111">RFC 1111</a>, USC/Information Sciences Institute, August 1989. |
| 1156 |
|
| 1157 |
<a href="./rfc1160">RFC1160</a> Cerf, V., "The Internet Activities Board", <a href="./rfc1160">RFC 1160</a>, NRI, May |
| 1158 |
1990. |
| 1159 |
|
| 1160 |
<a href="./rfc1310">RFC1310</a> Chapin, L., Chair, "The Internet Standards Process", <a href="./rfc1310">RFC</a> |
| 1161 |
<a href="./rfc1310">1310</a>, Internet Activities Board, March 1992. |
| 1162 |
|
| 1163 |
<a href="./rfc1311">RFC1311</a> Postel, J., Editor, "Introduction to the STD Notes", <a href="./rfc1311">RFC</a> |
| 1164 |
<a href="./rfc1311">1311</a>, USC/Information Sciences Institute, March 1992. |
| 1165 |
|
| 1166 |
STD1 Postel, J., Editor, "Internet Official Protocol Standards", |
| 1167 |
STD 1, <a href="./rfc1500">RFC 1500</a>, Internet Architecture Board, August 1993. |
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Internet Engineering Task Force [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc1539">RFC 1539</a> The Tao of IETF October 1993</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
Security Considerations |
| 1178 |
|
| 1179 |
Security issues are not discussed in this memo. |
| 1180 |
|
| 1181 |
|
| 1182 |
Author's Address |
| 1183 |
|
| 1184 |
Gary Scott Malkin |
| 1185 |
Xylogics, Inc. |
| 1186 |
53 Third Avenue |
| 1187 |
Burlington, MA 01803 |
| 1188 |
|
| 1189 |
Phone: (617) 272-8140 |
| 1190 |
EMail: [email protected] |
| 1191 |
|
| 1192 |
|
| 1193 |
|
| 1194 |
|
| 1195 |
|
| 1196 |
|
| 1197 |
|
| 1198 |
|
| 1199 |
|
| 1200 |
|
| 1201 |
|
| 1202 |
|
| 1203 |
|
| 1204 |
|
| 1205 |
|
| 1206 |
|
| 1207 |
|
| 1208 |
|
| 1209 |
|
| 1210 |
|
| 1211 |
|
| 1212 |
|
| 1213 |
|
| 1214 |
|
| 1215 |
|
| 1216 |
|
| 1217 |
|
| 1218 |
|
| 1219 |
|
| 1220 |
|
| 1221 |
|
| 1222 |
|
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
Internet Engineering Task Force [Page 22] |
| 1229 |
</pre> |