As per Relevance of the word technical, we have this rfc below:
Network Working Group S.
Request for Comments: 3005 Merit
BCP: 45 November 2000
Category: Best Current
IETF Discussion List
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 (2000). All Rights Reserved
The Internet Engineering Task Force (IETF) discussion mailing
furthers the development and specification of Internet
through discussion of technical issues, and hosts discussions of
direction, policy, meetings, and procedures. As this is the
general IETF mailing list, considerable latitude is allowed
Advertising, whether to solicit business or promote
opportunities, falls well outside the range of acceptable topics,
do discussions of a personal nature
Charter for the IETF Discussion
The IETF discussion list, ietf@ietf.org, serves two purposes.
furthers the development and specification of Internet
through discussion of technical issues. It also hosts discussions
IETF direction, policy, meetings, and procedures. As this is
most general IETF mailing list, considerable latitude is allowed
Advertising, whether to solicit business or promote
opportunities, falls well outside the range of acceptable topics,
do discussions of a personal nature
This list is meant for initial discussion only. Discussions
fall within the area of any working group or well established
should be moved to such more specific forum as soon as this
pointed out, unless the issue is one for which the working
needs wider input or direction
Harris Best Current Practice [Page 1]
RFC 3005 IETF Discussion List Charter November 2000
In addition to the topics noted above, appropriate postings include
- Last Call discussions of proposed protocol
- Discussion of technical issues that are candidates for IETF work
but do not yet have an appropriate e-mail
- Discussion of IETF administrative
- Questions and clarifications concerning IETF
- Announcements of conferences, events, or activities that
sponsored or endorsed by the Internet Society or IETF
Inappropriate postings include
- Unsolicited bulk e-
- Discussion of subjects unrelated to IETF policy, meetings
activities, or technical
- Unprofessional commentary, regardless of the general
- Announcements of conferences, events, or activities that are
sponsored or endorsed by the Internet Society or IETF
The IETF Chair, the IETF Executive Director, or a sergeant-at-
appointed by the Chair is empowered to restrict posting by a person
or of a thread, when the content is inappropriate and represents
pattern of abuse. They are encouraged to take into account
overall nature of the postings by an individual and
particular postings are an aberration or typical.
regarding their decisions should be referred to the IAB
Comments by Donald E. Eastlake 3rd and other members of the
POISSON working group are gratefully acknowledged
Author's
Susan R.
Merit Network, Inc
4251 Plymouth Rd., Suite
Ann Arbor, MI 48105-2785
Phone: (734) 936-2100
Fax: (734) 647-3185
EMail: srh@merit.
Harris Best Current Practice [Page 2]
RFC 3005 IETF Discussion List Charter November 2000
Full Copyright
Copyright (C) The Internet Society (2000). 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 3]
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
