draft-ietf-madman-email-mib-02.txt   draft-ietf-madman-email-mib-03.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-02.txt> Obsoletes: 1566, 2249 <draft-ietf-madman-email-mib-03.txt>
Mail Monitoring MIB Mail Monitoring MIB
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.
skipping to change at page 2, line ? skipping to change at page 2, line ?
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 ..................................................... 4
7 Changes made since RFC 2249 ..................................... 33 7 Changes made since RFC 2249 ..................................... 34
8 Acknowledgements ................................................ 34 8 Acknowledgements ................................................ 35
9 References ...................................................... 34 9 References ...................................................... 35
10 Security Considerations ........................................ 36 10 Security Considerations ........................................ 37
11 Author and Chair Addresses ..................................... 37 11 Author and Chair Addresses ..................................... 38
12 Full Copyright Statement ....................................... 37 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
components: components:
o An overall architecture, described in RFC 2571 [1]. o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
skipping to change at page 5, line 22 skipping to change at page 5, line 22
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 "9905120000Z" REVISION "9905230000Z"
DESCRIPTION DESCRIPTION
"This revision, published in RFC YYYY, fixes a number of "This revision, published in RFC YYYY, fixes a number of
technical problems found in previous versions: The technical problems found in previous versions: The
conformance groups for different versions of this MIB have conformance groups for different versions of this MIB have
been corrected, the recommendation that an empty string be been corrected, the recommendation that an empty string be
returned if the last operation was successful has been returned if the last operation was successful has been
removed from mtaGroupInboundRejectionReason and 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." MtaGroupErrorEntry. It should be noted that this last
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,
counters for specific errors, oldest message IDs, per-MTA counters for specific errors, oldest message IDs, per-MTA
and per-group loop counters, and a new table for tracking and per-group loop counters, and a new table for tracking
any errors an MTA encounters." any errors an MTA encounters."
REVISION "9311280000Z" REVISION "9311280000Z"
DESCRIPTION DESCRIPTION
skipping to change at page 6, line 13 skipping to change at page 6, line 13
::= {mib-2 28} ::= {mib-2 28}
mtaTable OBJECT-TYPE mtaTable OBJECT-TYPE
SYNTAX SEQUENCE OF MtaEntry SYNTAX SEQUENCE OF MtaEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table holding information specific to an MTA." "The table holding information specific to an MTA."
::= {mta 1} ::= {mta 1}
mtaStatusCode OBJECT-TYPE
SYNTAX INTEGER (4000000..5999999)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index capable of representing an Enhanced Mail System
Status Code. Enhanced Mail System Status Codes are
defined in RFC 1893. These codes have the form
class.subject.detail
Here 'class' is either 2, 4, or 5 and both 'subject' and
'detail' are integers in the range 0..999. Given a status
code the corresponding index value is defined to be
((class * 1000) + subject) * 1000 + detail. Both SMTP
error response codes and X.400 reason and diagnostic codes
can be mapped into these codes, resulting in a namespace
capable of describing most error conditions a mail system
encounters in a generic yet detailed way."
::= {mta 6}
mtaEntry OBJECT-TYPE mtaEntry OBJECT-TYPE
SYNTAX MtaEntry SYNTAX MtaEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entry associated with each MTA." "The entry associated with each MTA."
INDEX {applIndex} INDEX {applIndex}
::= {mtaTable 1} ::= {mtaTable 1}
MtaEntry ::= SEQUENCE { MtaEntry ::= SEQUENCE {
skipping to change at page 27, line 30 skipping to change at page 27, line 30
"Count of the number of errors of a given type that have "Count of the number of errors of a given type that have
been accumulated in association with a particular group's been accumulated in association with a particular group's
outbound connection activities. In the case of an SMTP outbound connection activities. In the case of an SMTP
client these will typically be errors reported while client these will typically be errors reported while
attempting to contact or while communicating with the attempting to contact or while communicating with the
remote SMTP server. In the case of X.400 these will remote SMTP server. In the case of X.400 these will
typically be errors encountered while constructing typically be errors encountered while constructing
or attempting to deliver an outgoing message." or attempting to deliver an outgoing message."
::= {mtaGroupErrorEntry 3} ::= {mtaGroupErrorEntry 3}
mtaStatusCode OBJECT-TYPE
SYNTAX INTEGER (4000000..5999999)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index capable of representing an Enhanced Mail System
Status Code. Enhanced Mail System Status Codes are
defined in RFC 1893. These codes have the form
class.subject.detail
Here 'class' is either 2, 4, or 5 and both 'subject' and
'detail' are integers in the range 0..999. Given a status
code the corresponding index value is defined to be
((class * 1000) + subject) * 1000 + detail. Both SMTP
error response codes and X.400 reason and diagnostic codes
can be mapped into these codes, resulting in a namespace
capable of describing most error conditions a mail system
encounters in a generic yet detailed way."
::= {mtaGroupErrorEntry 4}
-- Conformance information -- Conformance information
mtaConformance OBJECT IDENTIFIER ::= {mta 4} mtaConformance OBJECT IDENTIFIER ::= {mta 4}
mtaGroups OBJECT IDENTIFIER ::= {mtaConformance 1} mtaGroups OBJECT IDENTIFIER ::= {mtaConformance 1}
mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2} mtaCompliances OBJECT IDENTIFIER ::= {mtaConformance 2}
-- Compliance statements -- Compliance statements
mtaCompliance MODULE-COMPLIANCE mtaCompliance MODULE-COMPLIANCE
skipping to change at page 33, line 45 skipping to change at page 34, line 37
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) The conformance groups for different versions of this MIB have
been corrected, been corrected,
(2) the required mtaStatusCode entry has been added to (2) the required mtaStatusCode entry has been added to
MtaGroupErrorEntry, and MtaGroupErrorEntry (which does not affect the bits on the wire in
any way), and
(3) the recommendation that an empty string be returned if the last (3) 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
skipping to change at page 37, 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 Steve Kille, MADMAN WG Chair ISODE Consortium The Dome, The Square
ISODE Consortium Richmond TW9 1DT UK
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. 8 change blocks. 
36 lines changed or deleted 35 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/