home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_j_p
/
draft-ietf-madman-mtamib-08.txt
< prev
next >
Wrap
Text File
|
1994-01-13
|
2KB
|
59 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1566:
Title: Mail Monitoring MIB
Author: S. Kille & N. Freed
Mailbox: S.Kille@isode.com, ned@innosoft.com
Pages: 20
Characters: 33,136
Updates/Obsoletes: none
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, this memo extends the basic Network Services Monitoring
MIB (RFC 1565) to allow monitoring of Message Transfer Agents (MTAs).
It may also be used to monitor MTA components within gateways. This
RFC is a product of the Mail and Directory Management Working Group of
the IETF.
This is now a Proposed Standard Protocol.
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds
USC/Information Sciences Institute