New Request for Comments are now available from the DDN Network Information Center in the online library at FTP.NISC.SRI.COM. RFC 1233: Title: Definitions of Managed Objects for the DS3 Interface Type Author: T. Cox & K. Tesink, Editors Mailbox: tacox@sabre.bellcore.com, kaj@nvuxr.cc.bellcore.com Pages: 23 Characters: 48,269 Obsoletes/Updates: none pathname: rfc/rfc1233.txt This memo defines objects for managing DS3 Interface objects for use with the SNMP protocol. This memo is a product of the SNMP and Transmission MIB Working Group of the Internet Engineering Task Force (IETF). 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.Z (where "nnnn" refers to the number of the RFC and "v" refers to the version number of the RFC). Login with FTP username "anonymous" and your e-mail address as your password. JvNCnet also provides a mail service for those sites which cannot use FTP. Address the request to NISC@JVNC.NET and in the subject field of the message indicate the RFC number, as in "Subject: RFC nnnn". 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