As per Relevance of the word copyright, we have this rfc below:
Network Working Group P.
Request for Comments: 3233 Internet Mail
BCP: 58 S.
Category: Best Current Practice Harvard
February 2002
Defining the
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 (2002). All Rights Reserved
This document gives a more concrete definition of "the IETF" as
understood today. Many RFCs refer to "the IETF". Many
IETF documents speak of the IETF as if it were an already-
entity. However, no IETF document correctly defines what the
is
1.
Many RFCs refer to "the IETF". Many important IETF documents
of the IETF as if it were an already-defined entity. However,
IETF document correctly defines what the IETF is. This
gives a more concrete definition of "the IETF" as it
today
2. Defining the
BCP 9 ("The Internet Standards Process -- Revision 3") [BCP 9],
primary document that describes the Internet standards process,
defines the IETF. As described in BCP 11 ("The
Involved in the IETF Standards Process") [BCP 11], the
Engineering Task Force (IETF) is an open global community of
designers, operators, vendors, and researchers producing
specifications for the evolution of the Internet architecture and
smooth operation of the Internet
Hoffman & Bradner Best Current Practice [Page 1]
RFC 3233 Defining the IETF February 2002
It is important to note that the IETF is not a corporation: it is
unincorporated, freestanding organization. The IETF is
supported by the Internet Society (ISOC). ISOC is an
non-profit organization incorporated in the US with thousands
individual and corporate members throughout the world who
membership fees to join. The Internet Society provides many
to the IETF, including insurance and some financial and
support
As described in BCP 11, Internet standardization is an
activity of the ISOC, with the ISOC Board of Trustees
responsible for ratifying the procedures and rules of the
standards process. However, the IETF is not a formal subset of ISOC
for example, one does not have to join ISOC to be a member of
IETF
There is no board of directors for the IETF, no formally
bylaws, no treasurer, and so on. The structure of the IETF (
leadership, its working groups, the definition of IETF membership
and so on) are described in detail in BCP 11. Procedures
choosing leadership are described in detail in BCP 10.
Thus, when RFCs say "the IETF", they are describing the group
acts in accordance with BCP 9, BCP 10, and BCP 11.
3. Security
All IETF protocols must describe the security aspects of
environment in which they will be used. Also, the IETF has
Security Area which discusses the security aspects of IETF protocols
However, descriptive documents such as this one do not affect
security of the Internet
Hoffman & Bradner Best Current Practice [Page 2]
RFC 3233 Defining the IETF February 2002
A.
[BCP 9] Bradner, S., "The Internet Standards Process -- Revision 3",
BCP 9, RFC 2026, October 1996.
[BCP 10] Galvin, J., "IAB and IESG Selection, Confirmation,
Recall Process: Operation of the Nominating and
Committees", BCP 10, RFC 2727, February 2000.
[BCP 11] Hovey, R. and S. Bradner, "The Organizations Involved in
IETF Standards Process", BCP 11, RFC 2028, October 1996.
B. Editors'
Paul
Internet Mail
127 Segre
Santa Cruz, CA 95060
EMail: phoffman@imc.
Scott
Harvard
29 Oxford
Cambridge MA 02138
EMail: sob@harvard.
Hoffman & Bradner Best Current Practice [Page 3]
RFC 3233 Defining the IETF February 2002
Full Copyright
Copyright (C) The Internet Society (2002). 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
Hoffman & Bradner 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
