summaryrefslogtreecommitdiff
path: root/doc/rfc/rfc3232.txt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/rfc/rfc3232.txt')
-rw-r--r--doc/rfc/rfc3232.txt171
1 files changed, 171 insertions, 0 deletions
diff --git a/doc/rfc/rfc3232.txt b/doc/rfc/rfc3232.txt
new file mode 100644
index 0000000..e1bf878
--- /dev/null
+++ b/doc/rfc/rfc3232.txt
@@ -0,0 +1,171 @@
+
+
+
+
+
+
+Network Working Group J. Reynolds, Editor
+Request for Comments: 3232 RFC Editor
+Obsoletes: 1700 January 2002
+Category: Informational
+
+
+ Assigned Numbers: RFC 1700 is Replaced by an On-line Database
+
+Status of this Memo
+
+ This memo provides information for the Internet community. It does
+ not specify an Internet standard of any kind. Distribution of this
+ memo is unlimited.
+
+Copyright Notice
+
+ Copyright (C) The Internet Society (2002). All Rights Reserved.
+
+Abstract
+
+ This memo obsoletes RFC 1700 (STD 2) "Assigned Numbers", which
+ contained an October 1994 snapshot of assigned Internet protocol
+ parameters.
+
+Description
+
+ From November 1977 through October 1994, the Internet Assigned
+ Numbers Authority (IANA) periodically published tables of the
+ Internet protocol parameter assignments in RFCs entitled, "Assigned
+ Numbers". The most current of these Assigned Numbers RFCs had
+ Standard status and carried the designation: STD 2. At this time,
+ the latest STD 2 is RFC 1700.
+
+ Since 1994, this sequence of RFCs have been replaced by an online
+ database accessible through a web page (currently, www.iana.org).
+ The purpose of the present RFC is to note this fact and to officially
+ obsolete RFC 1700, whose status changes to Historic. RFC 1700 is
+ obsolete, and its values are incomplete and in some cases may be
+ wrong.
+
+ We expect this series to be revived in the future by the new IANA
+ organization.
+
+Security Considerations
+
+ This memo does not affect the technical security of the Internet.
+
+
+
+
+
+Reynolds Informational [Page 1]
+
+RFC 3232 RFC 1700 Replaced by On-line Database January 2002
+
+
+Author's Address
+
+ Joyce K. Reynolds
+ RFC Editor
+ 4676 Admiralty Way
+ Marina del Rey, CA 90292
+ USA
+
+ EMail: rfc-editor@rfc-editor.org
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Reynolds Informational [Page 2]
+
+RFC 3232 RFC 1700 Replaced by On-line Database January 2002
+
+
+Full Copyright Statement
+
+ Copyright (C) The Internet Society (2002). All Rights Reserved.
+
+ This document and translations of it may be copied and furnished to
+ others, and derivative works that comment on or otherwise explain it
+ or assist in its implementation may be prepared, copied, published
+ and distributed, in whole or in part, without restriction of any
+ kind, provided that the above copyright notice and this paragraph are
+ included on all such copies and derivative works. However, this
+ document itself may not be modified in any way, such as by removing
+ the copyright notice or references to the Internet Society or other
+ Internet organizations, except as needed for the purpose of
+ developing Internet standards in which case the procedures for
+ copyrights defined in the Internet Standards process must be
+ followed, or as required to translate it into languages other than
+ English.
+
+ The limited permissions granted above are perpetual and will not be
+ revoked by the Internet Society or its successors or assigns.
+
+ This document and the information contained herein is provided on an
+ "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
+ TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
+ BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
+ HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
+ MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
+
+Acknowledgement
+
+ Funding for the RFC Editor function is currently provided by the
+ Internet Society.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Reynolds Informational [Page 3]
+