jkrey@ISI.EDU (Joyce K. Reynolds) (06/26/91)
A new Request for Comments is now available from the DDN Network
Information Center in the online library at FTP.NISC.SRI.COM.
RFC 1239:
Title: Reassignment of Experimental MIBs to Standard MIBs
Author: J. Reynolds
Mailbox: jkrey@isi.edu
Pages: 2
Characters: 3,542
Updates: RFCs 1229, 1230, 1231, 1232, 1233
pathname: rfc/rfc1239.txt
In the past, MIBs have been assigned arcs in the experimental MIB
namespace early in their development and then were not assigned arcs
in the standard MIB namespace until they reached Full Standard status.
This practice required vendors to revise their implementations when a
MIB went from Draft to Full Standard status, even though there was
probably no substantive technical change in the definitions. This
practice could also engender operational problems in the field at an
undesirably late stage of the standardization process. It was also
observed that this practice could discourage implementation until the
Full Standard stage and that this, too, would be undesirable. So, a
preferable practice is to assign arcs in the standard MIB namespace at
the earliest phase of standardization and to preserve these
assignments as the standard progresses.
This RFC specifies a Proposed Standard Protocol for the Internet
community, and requests discussion and suggestions for improvements.
Please refer to the current edition of the "IAB Official Protocol
Standards" for the standardization state and status of this protocol.
Distribution of this memo is unlimited.
RFCs can be obtained via FTP from FTP.NISC.SRI.COM, NIS.NSF.NET, or
NISC.JVNC.NET.
RFCs can be obtained via FTP from FTP.NISC.SRI.COM, with the pathname
rfc/rfcNNNN.txt (where "NNNN" refers to the number of the RFC). Login
with FTP username "anonymous" and password "guest".
SRI also provides an automatic mail service for those sites which
cannot use FTP. Address the request to MAIL-SERVER@NISC.SRI.COM and
in the body of the message indicate the RFC to be sent: "send rfcNNNN"
where NNNN is the RFC number. Multiple requests may be included in
the same message.
To obtain RFCs from NIS.NSF.NET via FTP, login with username
"anonymous" and password "guest"; then connect to the RFC directory
("cd RFC"). The file name is of the form RFCnnnn.TXT-1 (where "nnnn"
refers to the number of the RFC).
The NIS also provides an automatic mail service for those sites which
cannot use FTP. Address the request to NIS-INFO@NIS.NSF.NET and leave
the subject field of the message blank. The first line of the text of
the message must be "SEND RFCnnnn.TXT-1", where nnnn is replaced by
the RFC number.
RFCs can also be obtained via FTP from NISC.JVNC.NET, with the
pathname rfc/RFCnnnn.TXT.v (where "nnnn" refers to the number of the
RFC and "v" refers to the version number of the RFC).
JvNCnet also provides a mail service for those sites which cannot use
FTP. Address the request to SENDRFC@JVNC.NET and in the subject field
of the message indicate the RFC number, as in "Subject: RFCnnnn" where
nnnn is the RFC number. Please note that RFCs whose number are less
than 1000 need not place a "0". (For example, RFC932 is fine.) No
text in the body of the message is needed.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
POSTEL@ISI.EDU. Please consult RFC 1111, "Instructions to RFC
Authors", for further information.
Requests to be added to or deleted from this distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.
Joyce K. Reynolds
USC/Information Sciences Institute