One document matched: draft-rfc-editor-rfc1700bis-00.txt-4446.txt
INTERNET-DRAFT J.Reynolds
draft-rfc-editor-rfc1700bis-00.txt 15 August 2001
STD: 2
Obsoletes: 1700
Category: Standards Track
Expires: 15 February 2002
Assigned Numbers: RFC 1700 is Obsolete
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract
This memo obsoletes RFC 1700 (STD 2) "Assigned Numbers", which
contained an October 1994 snapshot of assigned Internet protocol
parameters.
RFC Editor Standards Track [Page 1]
Internet-Draft Assigned Numbers: RFC 1700 is Obsolete 31 July 2001
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.
Author's Address
RFC Editor
4676 Admiralty Way
Marina del Rey, CA 90292
USA
EMail: rfc-editor@rfc-editor.org
RFC Editor Standards Track [Page 2]
Internet-Draft Assigned Numbers: RFC 1700 is Obsolete 31 July 2001
Full Copyright Statement
Copyright (C) The Internet Society (2001). 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.
RFC Editor Standards Track [Page 3]
| PAFTECH AB 2003-2026 | 2026-04-24 01:48:21 |