As per Relevance of the word copyright, we have this rfc below:
Network Working Group D.
Request for Comments: 3166
Category: Informational J.
Cisco
August 2001
Request to Move RFC 1403 to Historic
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
RFC 1403, "BGP OSPF Interaction", describes technology which is
longer used. This document requests that RFC 1403 be moved
Historic status
1.
During a review of internet standards relating to BGP, it
apparent that BGP OSPF interaction, as described in RFC 1403, is
common usage (if at all), and requires significant
complexity. Since this mechanism has not been in use in the
internet for many years (if ever), it is proposed to reclassify it
Historic
2. Security
Moving RFC 1403 to Historic has no known effect on the security
the internet
3.
[RFC1403] Varadhan, K., "BGP OSPF Interaction", RFC 1403,
January 1993.
Meyer & Scudder Informational [Page 1]
RFC 3166 Request to Move RFC 1403 to Historic Status August 2001
4. Authors'
David
12502 Sunrise Valley
Reston VA, 20191
MS VARESA-0105
EMail: dmm@sprint.
John
Cisco Systems, Inc
170 Tasman
San Jose, CA, 95134
EMail: jgs@cisco.
Meyer & Scudder Informational [Page 2]
RFC 3166 Request to Move RFC 1403 to Historic Status August 2001
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
Meyer & Scudder Informational [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