draft-ietf-madman-email-mib-03.txt   draft-ietf-madman-email-mib-04.txt 
Network Working Group Ned Freed, Innosoft Network Working Group Ned Freed, Innosoft
Internet Draft Steve Kille, ISODE Consortium Internet Draft Steve Kille, ISODE Consortium
Obsoletes: 1566, 2249 <draft-ietf-madman-email-mib-03.txt> Obsoletes: 1566, 2249 <draft-ietf-madman-email-mib-04.txt>
Mail Monitoring MIB Mail Monitoring MIB
December 1999
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC 2026. provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts. may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 2, line ? skipping to change at page 2, line ?
Agents (MTAs). It may also be used to monitor MTA components within Agents (MTAs). It may also be used to monitor MTA components within
gateways. gateways.
2. Table of Contents 2. Table of Contents
1 Introduction .................................................... 1 1 Introduction .................................................... 1
2 Table of Contents ............................................... 2 2 Table of Contents ............................................... 2
3 The SNMPv2 Network Management Framework ......................... 2 3 The SNMPv2 Network Management Framework ......................... 2
4 Message Flow Model .............................................. 3 4 Message Flow Model .............................................. 3
5 MTA Objects ..................................................... 4 5 MTA Objects ..................................................... 4
6 Definitions ..................................................... 4 6 Definitions ..................................................... 5
7 Changes made since RFC 2249 ..................................... 34 7 Changes made since RFC 2249 ..................................... 34
8 Acknowledgements ................................................ 35 8 Acknowledgements ................................................ 35
9 References ...................................................... 35 9 References ...................................................... 35
10 Security Considerations ........................................ 37 10 Security Considerations ........................................ 37
11 Author and Chair Addresses ..................................... 38 11 Author and Chair Addresses ..................................... 38
12 Full Copyright Statement ....................................... 38 12 Full Copyright Statement ....................................... 38
3. The SNMPv2 Network Management Framework 3. The SNMPv2 Network Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
skipping to change at page 4, line 42 skipping to change at page 5, line 12
first two tables must be implemented to conform with this MIB; the last first two tables must be implemented to conform with this MIB; the last
two are optional. two are optional.
6. Definitions 6. Definitions
MTA-MIB DEFINITIONS ::= BEGIN MTA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2 OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
DisplayString, TimeInterval TimeInterval
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
applIndex, URLString applIndex, URLString
FROM NETWORK-SERVICES-MIB; FROM NETWORK-SERVICES-MIB;
mta MODULE-IDENTITY mta MODULE-IDENTITY
LAST-UPDATED "9905120000Z" LAST-UPDATED "9912010000Z"
ORGANIZATION "IETF Mail and Directory Management Working Group" ORGANIZATION "IETF Mail and Directory Management Working Group"
CONTACT-INFO CONTACT-INFO
" Ned Freed " Ned Freed
Postal: Innosoft International, Inc. Postal: Innosoft International, Inc.
1050 Lakes Drive 1050 Lakes Drive
West Covina, CA 91790 West Covina, CA 91790
US US
Tel: +1 626 919 3600 Tel: +1 626 919 3600
Fax: +1 626 919 3614 Fax: +1 626 919 3614
E-Mail: ned.freed@innosoft.com" E-Mail: ned.freed@innosoft.com"
DESCRIPTION DESCRIPTION
"The MIB module describing Message Transfer Agents (MTAs)" "The MIB module describing Message Transfer Agents (MTAs)"
REVISION "9905230000Z" REVISION "9912010000Z"
DESCRIPTION DESCRIPTION
"This revision, published in RFC YYYY, fixes a number of "This revision, published in RFC YYYY, changes a number of
technical problems found in previous versions: The DisplayStrings to SnmpAdminStrings. Note that this change
conformance groups for different versions of this MIB have is not strictly supported by SMIv2. Howevr, the alternative
been corrected, the recommendation that an empty string be of deprecating the old objects and defining new objects
returned if the last operation was successful has been would have a more adverse impact on backward compatibility
removed from mtaGroupInboundRejectionReason and and interoperability, given the particular semantics of
these objects."
REVISION "9905120000Z"
DESCRIPTION
"This revision fixes a number of technical problems found in
previous versions: The conformance groups for different
versions of this MIB have been corrected, the recommendation
that an empty string be returned if the last operation was
successful has been removed from
mtaGroupInboundRejectionReason and
mtaGroupOutboundConnectFailureReason as it conflicts mtaGroupOutboundConnectFailureReason as it conflicts
with the stated purpose of these variables, and the with the stated purpose of these variables, and the
required mtaStatusCode entry has been added to required mtaStatusCode entry has been added to
MtaGroupErrorEntry. It should be noted that this last MtaGroupErrorEntry. It should be noted that this last
change in no way affects the bits on the wire." change in no way affects the bits on the wire."
REVISION "9708170000Z" REVISION "9708170000Z"
DESCRIPTION DESCRIPTION
"This revision, published in RFC 2249, adds the "This revision, published in RFC 2249, adds the
mtaGroupDescription and mtaGroupURL fields, conversion mtaGroupDescription and mtaGroupURL fields, conversion
operation counters, a group hierarchy description mechanism, operation counters, a group hierarchy description mechanism,
skipping to change at page 14, line 30 skipping to change at page 14, line 49
TimeInterval, TimeInterval,
mtaGroupLastOutboundActivity mtaGroupLastOutboundActivity
TimeInterval, TimeInterval,
mtaGroupLastOutboundAssociationAttempt mtaGroupLastOutboundAssociationAttempt
TimeInterval, TimeInterval,
mtaGroupRejectedInboundAssociations mtaGroupRejectedInboundAssociations
Counter32, Counter32,
mtaGroupFailedOutboundAssociations mtaGroupFailedOutboundAssociations
Counter32, Counter32,
mtaGroupInboundRejectionReason mtaGroupInboundRejectionReason
DisplayString, SnmpAdminString,
mtaGroupOutboundConnectFailureReason mtaGroupOutboundConnectFailureReason
DisplayString, SnmpAdminString,
mtaGroupScheduledRetry mtaGroupScheduledRetry
TimeInterval, TimeInterval,
mtaGroupMailProtocol mtaGroupMailProtocol
OBJECT IDENTIFIER, OBJECT IDENTIFIER,
mtaGroupName mtaGroupName
DisplayString, SnmpAdminString,
mtaGroupSuccessfulConvertedMessages mtaGroupSuccessfulConvertedMessages
Counter32, Counter32,
mtaGroupFailedConvertedMessages mtaGroupFailedConvertedMessages
Counter32, Counter32,
mtaGroupDescription mtaGroupDescription
DisplayString, SnmpAdminString,
mtaGroupURL mtaGroupURL
URLString, URLString,
mtaGroupCreationTime mtaGroupCreationTime
TimeInterval, TimeInterval,
mtaGroupHierarchy mtaGroupHierarchy
INTEGER, INTEGER,
mtaGroupOldestMessageId mtaGroupOldestMessageId
DisplayString, SnmpAdminString,
mtaGroupLoopsDetected mtaGroupLoopsDetected
Counter32 Counter32
} }
mtaGroupIndex OBJECT-TYPE mtaGroupIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647) SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index associated with a group for a given MTA." "The index associated with a group for a given MTA."
skipping to change at page 20, line 37 skipping to change at page 20, line 37
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number associations where the group was the "The total number associations where the group was the
initiator and association establishment has failed, initiator and association establishment has failed,
since group creation. Failed associations are since group creation. Failed associations are
not counted in the accumulated association totals." not counted in the accumulated association totals."
::= {mtaGroupEntry 20} ::= {mtaGroupEntry 20}
mtaGroupInboundRejectionReason OBJECT-TYPE mtaGroupInboundRejectionReason OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The failure reason, if any, for the last association this "The failure reason, if any, for the last association this
group refused to respond to. If no association attempt group refused to respond to. If no association attempt
has been made since the MTA was initialized the value has been made since the MTA was initialized the value
should be 'never'." should be 'never'."
::= {mtaGroupEntry 21} ::= {mtaGroupEntry 21}
mtaGroupOutboundConnectFailureReason OBJECT-TYPE mtaGroupOutboundConnectFailureReason OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The failure reason, if any, for the last association attempt "The failure reason, if any, for the last association attempt
this group initiated. If no association attempt has been this group initiated. If no association attempt has been
made since the MTA was initialized the value should be made since the MTA was initialized the value should be
'never'." 'never'."
::= {mtaGroupEntry 22} ::= {mtaGroupEntry 22}
mtaGroupScheduledRetry OBJECT-TYPE mtaGroupScheduledRetry OBJECT-TYPE
skipping to change at page 22, line 6 skipping to change at page 22, line 6
message transfer protocols. If the application protocol is message transfer protocols. If the application protocol is
not listed in the registry, an OID value of the form not listed in the registry, an OID value of the form
{applTCPProtoID port} or {applUDProtoID port} are used for {applTCPProtoID port} or {applUDProtoID port} are used for
TCP-based and UDP-based protocols, respectively. In either TCP-based and UDP-based protocols, respectively. In either
case 'port' corresponds to the primary port number being case 'port' corresponds to the primary port number being
used by the group. applTCPProtoID and applUDPProtoID are used by the group. applTCPProtoID and applUDPProtoID are
defined in the NETWORK-SERVICES-MIB, RFC XXXX." defined in the NETWORK-SERVICES-MIB, RFC XXXX."
::= {mtaGroupEntry 24} ::= {mtaGroupEntry 24}
mtaGroupName OBJECT-TYPE mtaGroupName OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A descriptive name for the group. If this group connects to "A descriptive name for the group. If this group connects to
a single remote MTA this should be the name of that MTA. If a single remote MTA this should be the name of that MTA. If
this in turn is an Internet MTA this should be the domain this in turn is an Internet MTA this should be the domain
name. For an OSI MTA it should be the string encoded name. For an OSI MTA it should be the string encoded
distinguished name of the managed object using the format distinguished name of the managed object using the format
defined in RFC 1779. For X.400(1984) MTAs which do not defined in RFC 1779. For X.400(1984) MTAs which do not
have a Distinguished Name, the RFC 2156 syntax have a Distinguished Name, the RFC 2156 syntax
skipping to change at page 22, line 42 skipping to change at page 22, line 42
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of messages for which an unsuccessful "The number of messages for which an unsuccessful
attempt was made to convert them from one form to attempt was made to convert them from one form to
another in this group since group creation." another in this group since group creation."
::= {mtaGroupEntry 27} ::= {mtaGroupEntry 27}
mtaGroupDescription OBJECT-TYPE mtaGroupDescription OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A description of the group's purpose. This information is "A description of the group's purpose. This information is
intended to identify the group in a status display." intended to identify the group in a status display."
::= {mtaGroupEntry 28} ::= {mtaGroupEntry 28}
mtaGroupURL OBJECT-TYPE mtaGroupURL OBJECT-TYPE
SYNTAX URLString SYNTAX URLString
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 24, line 6 skipping to change at page 24, line 6
those of this group (and usually others). A negative those of this group (and usually others). A negative
value is interpreted as a group collection code: Groups value is interpreted as a group collection code: Groups
with common negative hierarchy values comprise one with common negative hierarchy values comprise one
particular breakdown of MTA activity as a whole. A particular breakdown of MTA activity as a whole. A
zero value means that this MIB implementation doesn't zero value means that this MIB implementation doesn't
implement hierarchy indicators and thus the overall implement hierarchy indicators and thus the overall
group hierarchy cannot be determined." group hierarchy cannot be determined."
::= {mtaGroupEntry 31} ::= {mtaGroupEntry 31}
mtaGroupOldestMessageId OBJECT-TYPE mtaGroupOldestMessageId OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Message ID of the oldest message in the group's queue. "Message ID of the oldest message in the group's queue.
Whenever possible this should be in the form of an Whenever possible this should be in the form of an
RFC 822 msg-id; X.400 may convert X.400 message RFC 822 msg-id; X.400 may convert X.400 message
identifiers to this form by following the rules laid identifiers to this form by following the rules laid
out in RFC2156." out in RFC2156."
::= {mtaGroupEntry 32} ::= {mtaGroupEntry 32}
skipping to change at page 34, line 33 skipping to change at page 34, line 33
for RFC YYYY error monitoring." for RFC YYYY error monitoring."
::= {mtaGroups 9} ::= {mtaGroups 9}
END END
7. Changes made since RFC 2249 7. Changes made since RFC 2249
This revision corrects a number of minor technical errors in the This revision corrects a number of minor technical errors in the
construction of the mail monitoring MIB in RFC 2249 [18]: construction of the mail monitoring MIB in RFC 2249 [18]:
(1) The conformance groups for different versions of this MIB have (1) All DisplayStrings have been changed to SnmpAdminStrings,
(2) the conformance groups for different versions of this MIB have
been corrected, been corrected,
(2) the required mtaStatusCode entry has been added to (3) the required mtaStatusCode entry has been added to
MtaGroupErrorEntry (which does not affect the bits on the wire in MtaGroupErrorEntry (which does not affect the bits on the wire in
any way), and any way), and
(3) the recommendation that an empty string be returned if the last
(4) the recommendation that an empty string be returned if the last
operation was successful has been removed from operation was successful has been removed from
mtaGroupInboundRejectionReason and mtaGroupInboundRejectionReason and
mtaGroupOutboundConnectFailureReason as it conflicts with the mtaGroupOutboundConnectFailureReason as it conflicts with the
stated purpose of these variables. stated purpose of these variables.
8. Acknowledgements 8. Acknowledgements
This document is a work product of the Mail and Directory Management This document is a work product of the Mail and Directory Management
(MADMAN) Working Group of the IETF. It is based on an earlier MIB (MADMAN) Working Group of the IETF. It is based on an earlier MIB
designed by S. Kille, T. Lenggenhager, D. Partain, and W. Yeong. The designed by S. Kille, T. Lenggenhager, D. Partain, and W. Yeong. The
skipping to change at page 38, line 16 skipping to change at page 38, line 16
Ned Freed Ned Freed
Innosoft International, Inc. Innosoft International, Inc.
1050 Lakes Drive 1050 Lakes Drive
West Covina, CA 91790 West Covina, CA 91790
USA USA
tel: +1 626 919 3600 tel: +1 626 919 3600
fax: +1 626 919 3614 fax: +1 626 919 3614
email: ned.freed@innosoft.com email: ned.freed@innosoft.com
Steve Kille, MADMAN WG Chair ISODE Consortium The Dome, The Square Steve Kille, MADMAN WG Chair
Richmond TW9 1DT UK ISODE Consortium
The Dome, The Square
Richmond TW9 1DT
UK
tel: +44 181 332 9091 tel: +44 181 332 9091
email: S.Kille@isode.com email: S.Kille@isode.com
12. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and assist in its implementation may be prepared, copied, published and
 End of changes. 22 change blocks. 
26 lines changed or deleted 46 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/