As per Relevance of the word practice, we have this rfc below:
Network Working Group S.
Request for Comments: 3184 Merit
BCP: 54 October 2001
Category: Best Current
IETF Guidelines for
Status of this
This document specifies an Internet Best Current Practices for
Internet Community, and requests discussion and suggestions
improvements. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document provides a set of guidelines for personal
in the Internet Engineering Task Force. The Guidelines recognize
diversity of IETF participants, emphasize the value of
respect, and stress the broad applicability of our work
1.
The work of the IETF relies on cooperation among a broad
diversity of peoples, ideas, and communication styles.
Guidelines for Conduct inform our interaction as we work together
develop multiple, interoperable technologies for the Internet.
IETF participants aim to abide by these Guidelines as we
consensus in person, at IETF meetings, and in e-mail. If
arise, we resolve them according to the procedures outlined in
25.[1]
2. Principles of
1. IETF participants extend respect and courtesy to their
at all times
IETF participants come from diverse origins and backgrounds
are equipped with multiple capabilities and ideals. Regardless
these individual differences, participants treat their
with respect as persons--especially when it is difficult to
with them. Seeing from another's point of view is
revealing, even when it fails to be compelling
Harris Best Current Practice [Page 1]
RFC 3184 IETF Guidelines for Conduct October 2001
English is the de facto language of the IETF, but it is not
native language of many IETF participants. Native
speakers attempt to speak clearly and a bit slowly and to
the use of slang in order to accommodate the needs of
listeners
2. IETF participants develop and test ideas impartially,
finding fault with the colleague proposing the idea
We dispute ideas by using reasoned argument, rather than
intimidation or ad hominem attack. Or, said in a somewhat
IETF-like way
"Reduce the heat and increase the light
3. IETF participants think globally, devising solutions that meet
needs of diverse technical and operational environments
The goal of the IETF is to maintain and enhance a working, viable
scalable, global Internet, and the problems we encounter
genuinely very difficult. We understand that "scaling is
ultimate problem" and that many ideas quite workable in the
fail this crucial test. IETF participants use their
engineering judgment to find the best solution for the
Internet, not just the best solution for any particular network
technology, vendor, or user. We follow the intellectual
guidelines outlined in BCP 9.[2]
4. Individuals who attend Working Group meetings are prepared
contribute to the ongoing work of the group
IETF participants who attend Working Group meetings read
relevant Internet-Drafts, RFCs, and e-mail archives beforehand,
order to familiarize themselves with the technology
discussion. This may represent a challenge for newcomers, as e
mail archives can be difficult to locate and search, and it
not be easy to trace the history of longstanding Working
debates. With that in mind, newcomers who attend Working
meetings are encouraged to observe and absorb whatever
they can, but should not interfere with the ongoing process of
group. Working Group meetings run on a very limited
schedule, and are not intended for the education of individuals
The work of the group will continue on the mailing list, and
questions would be better expressed on the list in the months
follow
Harris Best Current Practice [Page 2]
RFC 3184 IETF Guidelines for Conduct October 2001
3. Security
IETF participants review each Internet protocol for
concerns, and these concerns are incorporated in the description
each protocol
4.
Mike O'Dell wrote the first draft of the Guidelines for Conduct,
many of his thoughts, statements, and observations are included
this version. Many useful editorial comments were supplied by
Crocker. Members of the POISSON Working Group provided
significant additions to the text
5.
[1] Bradner, S., "IETF Working Group Guidelines and Procedures",
BCP 25, RFC 2418, September 1998.
[2] Bradner, S., "The Internet Standards Process -- Revision 3",
BCP 9, RFC 2026, October 1996.
6. Author's
Susan
Merit Network, Inc
4251 Plymouth Rd., Suite 2000
Ann Arbor, MI 48105-2785
EMail: srh@merit.
Phone: (734) 936-2100
Harris Best Current Practice [Page 3]
RFC 3184 IETF Guidelines for Conduct October 2001
7. Full Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Harris Best Current Practice [Page 4]
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
