As per Relevance of the word engineering, we have this rfc below:
Network Working Group G.
Request for Comments: 1391 Xylogics, Inc
FYI: 17 January 1993
The Tao of
A Guide for New Attendees of the Internet Engineering Task
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard. Distribution of this memo
unlimited
Over the last two years, the attendance at Internet Engineering
Force (IETF) Plenary meetings has grown phenomenally.
38% of the attendees are new to the IETF at each meeting. About 33%
of those go on to become regular attendees. When the meetings
smaller, it wasn't very difficult for a newcomer to get to
people and get into the swing of things. Today, however, a
meets many more new people, some previously known only as the
of Request For Comments (RFC) documents or thought provoking
messages
The purpose of this For Your Information (FYI) RFC is to explain
the newcomers how the IETF works. This will give them a warm,
feeling and enable them to make the meeting more productive
everyone. This FYI will also provide the mundane bits of
which everyone who attends an IETF meeting should know
The IETF Secretariat is made up of the following people: Steve
(Executive Director of the IETF), Cynthia Clark, Megan Davies,
Legare, and Greg Vaudreuil. These are the people behind
Registration Table, and the success, of the IETF meetings. I
them for their hard work, and for their input and review of
document. Thanks also to Vinton Cerf, Phillip Gross, and
Partridge for their review and comments. And, as always,
thanks to April Marine and Skippy
I would also like to thank the management of Xylogics for
strong, continuing support of my IETF activities
Internet Engineering Task Force [Page 1]
RFC 1391 The Tao of IETF January 1993
Table of
Section 1 - The "Fun"
What is the IETF? . . . . . . . . . . . . . . . . . . . . . . 2
Humble Beginnings . . . . . . . . . . . . . . . . . . . . . . 3
The Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . 3
IETF Mailing Lists . . . . . . . . . . . . . . . . . . . . . 4
Registration . . . . . . . . . . . . . . . . . . . . . . . . 5
Dress Code . . . . . . . . . . . . . . . . . . . . . . . . . 6
Seeing Spots Before Your Eyes . . . . . . . . . . . . . . . . 6
Terminal Room . . . . . . . . . . . . . . . . . . . . . . . . 7
Social Event . . . . . . . . . . . . . . . . . . . . . . . . 7
Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Other General Things . . . . . . . . . . . . . . . . . . . . 8
Section 2 - The "You've got to know it"
Registration Bullets . . . . . . . . . . . . . . . . . . . . 9
Mailing Lists and Archives . . . . . . . . . . . . . . . . . 10
Important Email Addresses . . . . . . . . . . . . . . . . . . 10
IETF Proceedings . . . . . . . . . . . . . . . . . . . . . . 11
Be Prepared . . . . . . . . . . . . . . . . . . . . . . . . . 12
RFCs and Internet-Drafts . . . . . . . . . . . . . . . . . . 12
Frequently Asked Questions (and Their Answers) . . . . . . . 13
Pointers to Useful Documents and Files . . . . . . . . . . . 14
Section 3 - The "Reference"
Tao . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
IETF Area Abbreviations . . . . . . . . . . . . . . . . . . . 17
Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 17
References . . . . . . . . . . . . . . . . . . . . . . . . . 19
Security Considerations . . . . . . . . . . . . . . . . . . . 19
Author's Address . . . . . . . . . . . . . . . . . . . . . . 19
What is the IETF
The IETF is the protocol engineering, development,
standardization arm of the Internet Architecture Board (IAB).
mission includes
o Identifying, and proposing solutions to, pressing operational
technical problems in the Internet
o Specifying the development or usage of protocols and the near-
architecture to solve such technical problems for the Internet
o Making recommendations to the IAB regarding standardization
protocols and protocol usage in the Internet
Internet Engineering Task Force [Page 2]
RFC 1391 The Tao of IETF January 1993
o Facilitating technology transfer from the Internet Research
Force (IRTF) to the wider Internet community;
o Providing a forum for the exchange of information within
Internet community between vendors, users, researchers,
contractors, and network managers
The IETF Plenary meeting is not a conference, although there
technical presentations. The IETF is not a traditional
organization, although many standards are produced. The IETF is
volunteers who meet three times a year to fulfill the IETF mission
There is no membership in the IETF. Anyone may register for
attend any meeting. The closest thing there is to being an
member is being on the IETF mailing lists (see the IETF Mailing
section). This is where the best information about current
activities and focus can be found
Humble
The first IETF meeting was held in January, 1986 at Linkabit in
Diego with 15 attendees. The 4th IETF, held at SRI in Menlo Park
October, 1986, was the first at which non-government
attended. The concept of Working Groups (WG) was introduced at
5th IETF meeting at the NASA Ames Research Center in California
February, 1987. The 7th IETF, held at MITRE in McLean, Virginia
July, 1987, was the first meeting with over 100 attendees
The 14th IETF meeting was held at Stanford University in July, 1989.
It marked a major change in the structure of the IETF universe.
IAB (then, Internet Activities Board), which until that time
many Task Forces, changed its structure to leave only two: the
and the IRTF. The IRTF is tasked to consider the long-term
problems in the Internet. The IETF also changed. Those changes
visible in today's hierarchy
The
To completely understand the structure of the IETF, it is useful
understand the overall structure in which the IETF resides.
Internet Society (ISOC), formed in January 1992, provides
official parent organization for the IETF. The ISOC Board
Trustees appoints the members of the IAB. The IETF and IRTF
are also IAB members. The IAB provides the final technical review
Internet standards. They also provide leadership in the IETF,
virtue of their skills and years of experience
Internet Engineering Task Force [Page 3]
RFC 1391 The Tao of IETF January 1993
The IETF is divided into nine functional Areas. They are
Applications, Internet Services, Network Management,
Requirements, OSI Integration, Routing, Security, Transport
Services, and User Services. Each Area has at least one
Director. There is also an Area Director who oversees
Management. The Area Directors, along with the IETF Chair, form
Internet Engineering Steering Group (IESG). Phillip Gross has
the IETF Chair since the IETF's 7th meeting. He founded the IESG
serves as its Chair as well. The IESG provides the first
review of Internet standards. They are also responsible for
day-to-day "management" of the IETF
Each Area has several Working Groups. A Working Group is a group
people who work under a charter to achieve a certain goal. That
may be the creation of an informational document, the creation of
protocol standard, or the resolution of problems in the Internet
Most Working Groups have a finite lifetime. That is, once a
Group has achieved its goal, it disbands. As in the IETF, there
no official membership for a Working Group. Unofficially, a
Group member is somebody who's on that Working Group's mailing list
Anyone may attend a Working Group meeting (see the Be
section below).
Areas may also have Birds of a Feather (BOF) groups. They
have the same goals as Working Groups, except that they have
charter and usually only meet once or twice. BOFs are often held
determine if there is enough interest to form a Working Group
IETF Mailing
Anyone who plans to attend an IETF meeting should join the
announcements mailing list. This is where all of the
information, new and revised Internet-Draft and RFC announcements
IESG Recommendations, and Last Calls are posted. People who'd
to "get technical" may also join the IETF discussion list
"ietf@cnri.reston.va.us". This was the only list before
announcement list was created and is where discussions of
significance are held (most Working Groups have their own
lists for discussions relating to their work). To join the
announcement list, send a request to
ietf-announce-request@cnri.reston.va.
To join the IETF discussion list, send a request to
ietf-request@cnri.reston.va.
Internet Engineering Task Force [Page 4]
RFC 1391 The Tao of IETF January 1993
To join both of the lists, simply send a single message, to
"-request" address, and indicate that you'd like to join both
lists
Do not, ever, under any circumstances, for any reason, send a
to join a list to the list itself! The thousands of people on
list don't need, or want, to know when a new person joins
Similarly, when changing email addresses or leaving a list, send
request only to the "-request" address, not to the main list.
means you!!
The IETF discussion list is unmoderated. This means that anyone
express their opinions about issues affecting the Internet. However
it is not a place for companies or individuals to solicit
advertise. Only the Secretariat can send a message to
announcement list
Even though the IETF mailing lists "represent" the IETF membership
large, it is important to note that attending an IETF meeting
not automatically include addition to either mailing list
As previously mentioned, all meeting announcements are sent to
IETF announcement list. Within the IETF meeting announcement is
Registration Form and complete instructions for registering
including, of course, the cost. The Secretariat highly
that attendees preregister. Early registration, which ends about
month before the meeting, carries a lower registration fee. As
size of the meetings has grown, so has the length of the lines at
registration desk. Fortunately, there are three lines:
"preregistered and prepaid" line (which moves very quickly);
"preregistered and on-site payment" line (which moves a little
slowly); and the "registration and on-site payment" line (take
guess).
Registration is open all week. However, the Secretariat
recommends that attendees arrive for early registration, beginning
6:00 P.M. (meeting local time), on the Sunday before the
plenary. Not only will there be fewer people, but there will also
a reception at which people can get a byte to eat. If
registration lines are long, one can eat first and try again when
lines are shorter. Newcomers are encouraged to attend the
Orientation on Sunday at 4:30 P.M
Registered attendees (and there isn't any other kind) receive
Registration Packet. It contains a general orientation sheet,
Internet Engineering Task Force [Page 5]
RFC 1391 The Tao of IETF January 1993
At-A-Glance sheet, a list of Working Group acronyms, the most
Agenda, and a name tag. The At-A-Glance is a very
reference and is used throughout the week. It contains
Group/BOF room assignments and a map of room locations.
who prepaid will also find their receipt in their packet
Dress
Since attendees must wear their name tags, they must also wear
or blouses. Pants or skirts are also highly recommended.
though, many newcomers are often embarrassed when they show up
morning in suits, to discover that everybody else is wearing T
shirts, jeans (shorts, if weather permits) and sandals. There
those in the IETF who refuse to wear anything other than suits
Fortunately, they are well known (for other reasons) so they
forgiven this particular idiosyncrasy
The general rule is: "dress for the weather."
Seeing Spots Before Your
Some of the people at the IETF will have a little colored dot
their name tags. A few people have more than one. These
identify people who are silly enough to volunteer to do a lot
extra work. The colors have the following meanings
red - IAB
yellow - IESG
blue - Working Group/BOF
green - Local
Local hosts are the people who can answer questions about
terminal room, and restaurants and points of interest in the area
It is important that newcomers to the IETF not be afraid to strike
conversations with people who wear these dots. If the IAB and
members, and Working Group and BOF chairs, didn't want to talk
anybody, they wouldn't be wearing the dots in the first place
To make life simpler for the Secretariat, Registration Packets
also coded with little colored dots. These are only for
use, so the nobody else needs to worry about them
Internet Engineering Task Force [Page 6]
RFC 1391 The Tao of IETF January 1993
Terminal
One of the most important (depending on your point of view)
the local host does is provide Internet access to the
attendees. In general, the connectivity is excellent. This
entirely due to the Olympian efforts of the local hosts, and
ability to beg, borrow and steal. The people and companies
donate their equipment, services, and time are to be
congratulated and thanked
While preparation far in advance of the meeting is encouraged,
may be some unavoidable "last minute" things which can
accomplished in the terminal room. It may also be useful to
who need to make trip reports or status reports while things
still fresh in their minds
Social
Another of the most important things organized and managed by
local hosts is the IETF social event. The social event has
something of a tradition at the IETF meetings. It has
immortalized by Marshal Rose with his reference to "many fine
and dinners" [ROSE], and by Claudio and Julia Topolcic with
rendition of "Nerds in Paradise" on a pink T-shirt
Newcomers to the IETF are encouraged to attend the social event
Everyone is encouraged to wear their name tags. The social event
designed to give people a chance to meet on a social, rather
technical, level
Sometimes, the social event is a computer or high-tech related event
At the Boston IETF, for example, the social was dinner at
Computer Museum. Other times, the social might be a dinner cruise
a trip to an art gallery
The Agenda for the IETF meetings is a very fluid thing. It is sent
in various forms, to the IETF announcement list three times prior
the meeting. The final Agenda is included in the
Packets. Of course, "final" in the IETF doesn't mean the same
as it does elsewhere in the world. The final Agenda is simply
version that went to the printers
The Secretariat will announce Agenda changes during the
plenary sessions. Changes will also be posted on the bulletin
Internet Engineering Task Force [Page 7]
RFC 1391 The Tao of IETF January 1993
near the IETF Registration Table (not the hotel registration desk).
Assignments for breakout rooms (that's where the Working Groups
BOFs meet) and a map showing the room locations make up the At-A
Glance sheet (included in the Registration Packets).
assignments are as flexible as the Agenda. Some Working Groups
multiple times during a meeting and every attempt is made to have
Working Group meet in the same room each session. Room
changes are not necessarily permanent for the week. Always check
At-A-Glance first, then the bulletin board. When in doubt,
with a member of the Secretariat at the Registration Table
Other General
The opening Plenary on Monday morning is the most heavily
session. It is where important introductory remarks are made,
people are encouraged to attend
The guy wearing the suit is probably Vint Cerf, the President of
Internet Society and an IAB member. If you see a guy doing a
tease out of a suit, it's definitely Vint (but don't come just to
him do it again; he's only done it once in the Internet's 20
history).
The IETF Secretariat, and IETFers in general, are very approachable
Never be afraid to approach someone and introduce yourself. Also
don't be afraid to ask questions, especially when it comes to
and acronyms
Hallway conversations are very important. A lot of very good
gets done by people who talk together between meetings and
lunches and dinners. Every minute of the IETF can be considered
time (much to some people's dismay).
"Bar BOFs" are unofficial get-togethers, usually in the late evening
during which a lot of work gets done over drinks
It's unwise to get between a hungry IETFer (and there isn't any
kind) and coffee break brownies and cookies, no matter
interesting a hallway conversation is
IETFers are fiercely independent. It's always safe to question
opinion and offer alternatives, but don't expect an IETFer to
an order
The IETF, and the plenary sessions in particular, are not places
vendors to try to sell their wares. People can certainly
Internet Engineering Task Force [Page 8]
RFC 1391 The Tao of IETF January 1993
questions about their company and its products, but bear in mind
the IETF is not a trade show. This does not preclude people
recouping costs for IETF related T-shirts, buttons and
protectors
Registration
Registration is such an important topic, that it's in this RFC twice
This is the "very important registration bullets" section
o To attend an IETF meeting: you have to register and you have
pay the registration fee
o All you need to do to be registered is to send in a
Registration Form
o You may register by mail, email or fax. Email and
registration forms will be accepted until 1:00 P.M. ET on
Friday before the meeting
o You may preregister and pay, preregister and pay later
preregister and pay on-site, or register and pay on-site
o To get the lower registration fee, you must register by the
registration deadline (about one month before the meeting).
can still pay later or on-site
o If you don't register by the early registration deadline, a
fee is added
o Everyone pays the same fees. There are no education or
discounts. There are no discounts for attending only part of
week
o Register only ONE person per registration form. Substitutions
NOT allowed
o You may register then pay later, but you may not pay then
later. Payment MUST be accompanied by a completed
form
o Purchase orders are NOT accepted. DD Form 1556 IS accepted
o Refunds are subject to a $20 service charge. Late fees will
be refunded
o The registration fee covers a copy of the meeting's Proceedings
Internet Engineering Task Force [Page 9]
RFC 1391 The Tao of IETF January 1993
Sunday evening reception (cash bar), a daily
breakfast, and two daily coffee breaks
Mailing Lists and
As previously mentioned, the IETF announcement and discussion
lists are the central mailing lists for IETF activities. However
there are many other mailing lists related to IETF work.
example, every Working Group has its own discussion list.
addition, there are some long-term technical debates which have
moved off of the IETF list onto lists created specifically for
topics. It is highly recommended that everybody follow
discussions on the mailing lists of the Working Groups which
wish to attend. The more work that is done on the mailing lists,
less work that will need to be done at the meeting, leaving time
cross pollination (i.e., attending Working Groups outside one'
primary area of interest in order to broaden one's perspective).
The mailing lists also provide a forum for those who wish to follow
or contribute to, the Working Groups' efforts, but cannot attend
IETF meetings
All IETF discussion lists have a "-request" address which handles
administrative details of joining and leaving the list. It
generally frowned upon when such administrivia appears on
discussion mailing list
Most IETF discussion lists are archived. That is, all of
messages sent to the list are automatically stored on a host
anonymous FTP access. To find out where a particular list
archived, send a message to the list's "-request" address, NOT to
list itself
Important Email
There are some important IETF email addresses with which
should be familiar. They are all located at "cnri.reston.va.us
(e.g., "ietf-info@cnri.reston.va.us"). To personalize things,
names of the Secretariat staff who handle the lists are given
o ietf-info general queries about the IETF
Greg Vaudreuil, Megan Davies and Cynthia
o ietf-rsvp queries about meeting locations and fees
emailed Registration Forms
Debra
Internet Engineering Task Force [Page 10]
RFC 1391 The Tao of IETF January 1993
o proceedings queries about previous Proceedings availability
orders for copies of the Proceedings
Debra
o ietf-announce-
requests to join/leave IETF announcement list
Cynthia
o ietf-request requests to join/leave IETF discussion list
Cynthia
o internet-drafts Internet-Draft submissions
Cynthia
o iesg-secretary Greg
IETF
The IETF Proceedings are compiled in the two months following
IETF meeting. The Proceedings usually start with a message
Phill Gross, the Chair of the IETF. Each contains the
(hindsight) Agenda, an IETF overview, a report from the IESG,
and Working Group reports, network status briefings, slides from
protocol and technical presentations, and the attendees list.
attendees list includes an attendee's name, affiliation, work
number, work fax number, and email address, as provided on
Registration Form
A copy of the Proceedings will be sent to everyone who registered
the IETF. The cost is included in the registration fee.
Proceedings are sent to the mailing addresses provided on
Registration Forms
For those who could not attend a meeting but would like a copy of
Proceedings send a check for $35 (made payable to CNRI) to
Corporation for National Research
Attn: Accounting Department - IETF
1895 Preston White Drive, Suite 100
Reston, VA 22091
Please indicate which meeting Proceedings you would like to
by specifying the meeting date (e.g., July 1992) or meeting
and location (e.g., 24th meeting in Boston). Availability
previous meeting Proceedings is limited, so check BEFORE
payment
Internet Engineering Task Force [Page 11]
RFC 1391 The Tao of IETF January 1993
Be
This topic cannot be stressed enough. As the IETF grows, it
more and more important for attendees to arrive prepared for
Working Groups meetings they plan to attend. This doesn't apply
to newcomers; everybody should come prepared
Being prepared means having read the documents which the
Group or BOF Chair has distributed. It means having followed
discussions on the Working Group's mailing list or having
the archives. For the Working Group/BOF Chairs, it means getting
of the documents out early enough (i.e., several weeks) to
everybody time to read them. It also means announcing an agenda
sticking with it
At the Chair's discretion, some time may be devoted to bringing
Working Group attendees up to speed. In fact, long lived
Groups have occasionally held entire sessions which were
in nature. As a rule, however, a Working Group is not the place
go for training. Observers are always welcome, but they must
that the work effort cannot be delayed for education. Anyone
to attend a Working Group for the first time might seek out the
prior to the meeting and ask for some introduction
Another thing, for everybody, to consider is that Working Groups
through phases. In the initial phase (say, the first two meetings),
all ideas are welcome. The idea is to gather all the
solutions together for consideration. In the development phase,
solution is chosen and developed. Trying to reopen issues which
decided more than a couple of meetings back is considered bad form
The final phase (the last two meetings) is where the "spit
polish" are applied to the architected solution. This is not
time to suggest architectural changes or open design issues
resolved. It's a bad idea to wait until the last minute to speak
if a problem is discovered. This is especially true for people
excuse is that they hadn't read the documents until the day before
comments period ended
Time at the IETF meetings is a precious thing. Working Groups
encouraged to meet between IETF meetings, either in person or
video or telephone conference. Doing as much work as possible
the mailing lists would also reduce the amount of work which must
done at the meeting
RFCs and Internet-
Originally, RFCs were just what the name implies; they were
for comments. The early RFCs were messages between the
Internet Engineering Task Force [Page 12]
RFC 1391 The Tao of IETF January 1993
architects about how to resolve certain problems. Over the years
RFCs became more formal. It reached the point that they were
cited as standards, even when they weren't
Internet Experiment Notes (IEN) were created to become a new
document series about the early experimental work on TCP and IP.
was thought that having "Notes" as part of the name would
them from being cited as standards. As the work matured,
documentation was done as RFCs
RFCs continue to be the important documents about the Internet;
are now two special sub-series within the RFCs: FYIs and STDs.
For Your Information RFC sub-series was created to document
and things which are introductory. Frequently, FYIs are created
the IETF User Services Area. The STD RFC sub-series is new. It
created to identify those RFCs which do specify full
Standards. RFCs of every type have an RFC number by which they
indexed and by which they can be retrieved. FYIs and STDs have
numbers and STD numbers, respectively, in addition to RFC numbers
This makes it easier for a new Internet user, for example, to
all of the helpful, informational documents, by looking in the
index. In addition, FYI and STD numbers never change across
document revision, while the RFC number does
Internet-Drafts (I-D) are working documents of the IETF. Any
(e.g., Working Group, BOF) or individual may submit a document
distribution as an I-D. An I-D is valid for six months.
guidelines require that an expiration date appear on every page of
I-D. An I-D may be updated, replaced or obsoleted at any time.
is not appropriate to use I-Ds as reference material or to cite them
other than as a "working draft" or "work in progress".
For additional information, read the following documents
o Request for Comments on Request for Comments [RFC1111]
o F.Y.I. on F.Y.I: Introduction to the F.Y.I notes [RFC1150]
o Introduction to the STD Notes [RFC1311]
o Guidelines to Authors of Internet Drafts [GAID
o The Internet Activities Board [RFC1160]
o The Internet Standards Process [RFC1310]
o IAB Official Protocol Standards [STD1]
Frequently Asked Questions (and Their Answers
Q: My Working Group moved this morning. Where is it now
A: Not all room assignment changes are permanent. Check the At-A
Glance sheet and the message board for announcements
Internet Engineering Task Force [Page 13]
RFC 1391 The Tao of IETF January 1993
Q: Where is Room A
A: Check the map on the At-A-Glance sheet. An enlarged version is
the bulletin board
Q: Where can I get a copy of the Proceedings
A: The Proceedings are automatically sent to each attendee about
months after the meeting
Q: When is on-site registration
A: The IETF registration table is set up Sunday night from 6:00 p.m
- 8:00 p.m. and Monday - Thursday from about 8:30 a.m. - 6:00 p.m
Starting time in the mornings and Friday's hours may
depending on the meeting schedule
Q: Where is lunch served
A: The meeting does not include lunch or dinner. Ask a local
(somebody with a green dotted badge) for a recommendation
Q: Where are the receipts for the social event
A: The social is not managed by the IETF Secretariat. Ask a
host
Pointers to Useful Documents and
This is a list of documents and files that provide useful
about the IETF meetings, Working Groups, and documentation.
files reside in the "ietf" directory on the Anonymous FTP
listed below. Files with names beginning with "0" (zero) pertain
IETF meetings. These may refer to a recently held meeting if
first announcement of the next meeting has not yet been sent to
IETF mailing list. Files with names beginning with "1" (one)
general IETF information. This is only a partial list of
available files
o 0mtg-agenda.txt Agenda for the
o 0mtg-at-a-glance.txt Logistics information for the
o 0mtg-rsvp.txt Meeting registration
o 0mtg-sites.txt Future meeting sites and
o 0mtg-traveldirections.txt Directions to the meeting
o 1directories.txt The IETF Shadow directory locations
contents
o 1id-guidelines.txt Guidelines to Authors of Internet-
Contains information on writing
submitting I-Ds
o 1ietf-description.txt Short description of the IETF and IESG
including a list of Area Directors
Internet Engineering Task Force [Page 14]
RFC 1391 The Tao of IETF January 1993
o 1nonwg-discuss.txt A list of mailing lists created
discuss specific IETF issues
o 1proceedings-request.txt A Proceedings order form for
current and previous
o 1wg-summary.txt List of all Working Groups, by Area
including the name and address of
chairperson, and the mailing
address
Additionally, the charters and minutes of the Working Groups and
are archived in the "ietf" directory
All of these documents are available by anonymous FTP from
following sites
o DDN NIC Address: nic.ddn.mil (192.112.36.5)
o East Coast (US) Address: nnsc.nsf.net (128.89.1.178)
o West Coast (US) Address: ftp.nisc.sri.com (192.33.33.22)
o Pacific Rim Address: munnari.oz.au (128.250.1.21)
o Europe Address: nic.nordu.net (192.36.148.17)
The files are also available via email from various mail servers.
to get the agenda and meeting summary from the mail server at
International, for example, you would send the following message
To: mail-server@nisc.sri.com Message
Subject: anything you
send 0mtg-agenda.txt Body of the
send 0mtg-at-a-glance.
Residing on the same archive sites are the RFCs and Internet-Drafts
They are in the "rfc" and "internet-drafts" directories
respectively. The file "rfc-index.txt" contains the
information about the RFCs (e.g., which have been obsoleted
which). In general, only the newest version of an Internet-Draft
available
Mail servers can also be used to retrieve RFCs and I-Ds. To
SRI's mail server to get an RFC, simply include a "send command"
the body of the message for the desired RFC. For example
send rfc1150
or use a special RFC shorthand
rfc 1150
Internet Engineering Task Force [Page 15]
RFC 1391 The Tao of IETF January 1993
For Internet-Drafts, include the name (yes, they are very long) in
"send" command line. For example
send draft-ietf-ripv2-mibext-03.
RFCs may also be retrieved, using email, from ISI's RFC-Info
at "rfc-info@isi.edu". To get a specific RFC, include the
in the body of the message
Retrieve:
Doc-ID: RFC0951
This example would cause a copy of RFC 951 (the leading zero in
Doc-ID is required) to be emailed to the requestor
To get a list of available RFCs which match certain criteria,
the following in the body of the message
LIST:
Keywords:
This example would email a list of all RFCs with "Gateway" in
title, or as an assigned keyword, to the requestor
To get a copy of the RFC-Info manual
HELP:
To get information on other ways to get RFCs
HELP: ways_to_get_
Internet Engineering Task Force [Page 16]
RFC 1391 The Tao of IETF January 1993
Pronounced "Dow", Tao means "the Way." It is the basic
behind the teachings of Lao-tse, a Chinese master. Its
symbol is the black and white Yin-Yang circle
IETF Area
APP
INT Internet
MGT Network
OPS Operational
OSI OSI
RTG
SEC
TSV Transport and
USV User
:-) Smiley
ANSI American National Standards
ARPANET Advanced Research Projects Agency
AS Autonomous
ATM Asynchronous Transfer
BGP Border Gateway
BOF Birds Of a
BSD Berkeley Software
BTW By The
CCIRN Coordinating Committee for Intercontinental Research
CCITT International Telegraph and Telephone Consultative
CNI Coalition for Networked
CREN The Corporation for Research and Educational
DARPA U.S. Defense Advanced Research Projects
DDN U.S. Defense Data
DISA U.S. Defense Information Systems
EGP Exterior Gateway
FAQ Frequently Asked
FARNET Federation of American Research
FIX U.S. Federal Information
FNC U.S. Federal Networking
FQDN Fully Qualified Domain
FYI For Your Information (RFC
GOSIP U.S. Government OSI
IAB Internet Architecture
IANA Internet Assigned Numbers
I-D Internet-
Internet Engineering Task Force [Page 17]
RFC 1391 The Tao of IETF January 1993
IEN Internet Experiment
IESG Internet Engineering Steering
IETF Internet Engineering Task
IGP Interior Gateway
IMHO In My Humble
IMR Internet Monthly
IR Internet
IRSG Internet Research Steering
IRTF Internet Research Task
ISO International Organization for
ISOC Internet
ISODE ISO Development
ITU International Telecommunication
MIB Management Information
MIME Multipurpose Internet Mail
NIC Network Information
NIS Network Information
NIST National Institute of Standards and
NOC Network Operations
NREN National Research and Education
NSF National Science
OSI Open Systems
PEM Privacy Enhanced
PTT Postal, Telegraph and
RARE Reseaux Associes pour la Recherche
RFC Request For
RIPE Reseaux IP
SIG Special Interest
STD Standard (RFC
TLA Three Letter
TTFN Ta-Ta For
UTC Universal Time
WG Working
WRT With Respect
WYSIWYG What You See is What You
Internet Engineering Task Force [Page 18]
RFC 1391 The Tao of IETF January 1993
GAID "Guidelines to Authors of Internet Drafts",
1id-guidelines.txt
ROSE Rose, M., "The Open Book: A Practical Perspective on OSI",
Prentice Hall, Englewood Cliffs, NJ, 1989.
RFC1111 Postel, J., "Request for Comments on Request for Comments",
RFC 1111, USC/Information Sciences Institute, August 1989.
RFC1150 Malkin, G., and J. Reynolds, "F.Y.I. on F.Y.I.", FYI 1,
1150, Proteon, USC/Information Sciences Institute,
1990.
RFC1160 Cerf, V., "The Internet Activities Board", RFC 1160, NRI,
1990.
RFC1310 Chapin, L., Chair, "The Internet Standards Process",
1310, Internet Activities Board, March 1992.
RFC1311 Postel, J., Editor, "Introduction to the STD Notes",
1311, USC/Information Sciences Institute, March 1992.
STD1 Postel, J., Editor, "IAB Official Protocol Standards", STD 1,
RFC1360, Internet Architecture Board, September 1992.
Security
Security issues are not discussed in this memo
Author's
Gary Scott
Xylogics, Inc
53 Third
Burlington, MA 01803
Phone: (617) 272-8140
EMail: gmalkin@Xylogics.
Internet Engineering Task Force [Page 19]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
