draft-ietf-madman-email-mib-00.txt   draft-ietf-madman-email-mib-01.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-00.txt> Obsoletes: 1566, 2249 <draft-ietf-madman-email-mib-01.txt>
Mail Monitoring MIB Mail Monitoring MIB
November 1998 February 1999
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft and is in full conformance with all
documents of the Internet Engineering Task Force (IETF), its areas, and provisions of Section 10 of RFC 2026.
its working groups. Note that other groups may also distribute working
documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months. Internet-Drafts are working documents of the Internet Engineering Task
Internet-Drafts may be updated, replaced, or obsoleted by other Force (IETF), its areas, and its working groups. Note that other groups
documents at any time. It is not appropriate to use Internet-Drafts as may also distribute working documents as Internet-Drafts.
reference material or to cite them other than as a ``working draft'' or
``work in progress.''
To view the entire list of current Internet-Drafts, please check the Internet-Drafts are draft documents valid for a maximum of six months
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow and may be updated, replaced, or obsoleted by other documents at any
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern Europe), time. It is inappropriate to use Internet- Drafts as reference material
ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific Rim), or to cite them other than as "work in progress."
ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
Copyright (C) The Internet Society (1998). All Rights Reserved. The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved.
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. use with network management protocols in the Internet community.
Specifically, this memo extends the basic Network Services Monitoring Specifically, this memo extends the basic Network Services Monitoring
MIB defined in RFC XXXX [8] to allow monitoring of Message Transfer MIB defined in RFC XXXX [16] to allow monitoring of Message Transfer
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 SNMP Network Management Framework ........................... 2
3.1 Object Definitions ............................................ 3 3.1 Object Definitions ............................................ 3
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 ................................................ 34 8 Acknowledgements ................................................ 34
9 References ...................................................... 34 9 References ...................................................... 34
10 Security Considerations ........................................ 35 10 Security Considerations ........................................ 37
11 Author and Chair Addresses ..................................... 36 11 Author and Chair Addresses ..................................... 37
12 Full Copyright Statement ....................................... 36 12 Full Copyright Statement ....................................... 38
3. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of seven major 3. The SNMP Network Management Framework
components. They are:
o RFC 1902 [1] which defines the SMI, the mechanisms used for The SNMP Management Framework presently consists of five major
describing and naming objects for the purpose of management. components:
o RFC 1903 [2] defines textual conventions for SNMPv2. o An overall architecture, described in RFC 2271 [1].
o RFC 1904 [3] defines conformance statements for SNMPv2. o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version,
called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC
1904 [7].
o RFC 1905 [4] defines transport mappings for SNMPv2. o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].
o RFC 1906 [5] defines the protocol operations used for network o Protocol operations for accessing management information. The
access to managed objects. first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations
and associated PDU formats is described in RFC 1905 [13].
o RFC 1907 [6] defines the Management Information Base for SNMPv2. o A set of fundamental applications described in RFC 2273 [14] and
the view-based access control mechanism described in RFC 2275
[15].
o RFC 1908 [7] specifies coexistance between SNMP and SNMPv2. Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined
using the mechanisms defined in the SMI.
The Framework permits new objects to be defined for the purpose of This memo specifies a MIB module that is compliant to the SMIv2. A MIB
experimentation and evaluation. conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
3.1. Object Definitions 3.1. Object Definitions
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined using Management Information Base or MIB. Objects in the MIB are defined using
the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI.
In particular, each object type is named by an OBJECT IDENTIFIER, an In particular, each object type is named by an OBJECT IDENTIFIER, an
administratively assigned name. The object type together with an object administratively assigned name. The object type together with an object
instance serves to uniquely identify a specific instantiation of the instance serves to uniquely identify a specific instantiation of the
object. For human convenience, we often use a textual string, termed object. For human convenience, we often use a textual string, termed
skipping to change at page 5, line 22 skipping to change at page 5, line 36
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 "9311280000Z"
DESCRIPTION
"The original version of this MIB was published in RFC 1566"
REVISION "9708170000Z"
DESCRIPTION
""
REVISION "9811130000Z" REVISION "9811130000Z"
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. No changes technical problems found in previous versions. No changes
have been made to the objects this MIB defines." have been made to the objects this MIB defines."
REVISION "9708170000Z"
DESCRIPTION
"This revision, published in RFC 2249, adds the
mtaGroupDescription and mtaGroupURL fields, conversion
operation counters, a group hierarchy description mechanism,
counters for specific errors, oldest message IDs, per-MTA
and per-group loop counters, and a new table for tracking
any errors an MTA encounters."
REVISION "9311280000Z"
DESCRIPTION
"The original version of this MIB was published in RFC 1566"
::= {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}
skipping to change at page 34, line 21 skipping to change at page 34, line 21
"A collection of objects providing monitoring of "A collection of objects providing monitoring of
detailed MTA errors. This is the appropriate group detailed MTA errors. This is the appropriate group
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 [10]. There are no construction of the mail monitoring MIB in RFC 2249 [18]. There are no
substantive changes to any of the objects the MIB defines. substantive changes to any of the objects the MIB defines.
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
Electronic Mail Association's TSC committee was instrumental in Electronic Mail Association's TSC committee was instrumental in
providing feedback on and suggesting enhancements to RFC 1566 [11] that providing feedback on and suggesting enhancements to RFC 1566 [19] that
have led to the present document. have led to the present document.
9. References 9. References
[1] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Structure [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998.
[2] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990.
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212,
Performance Systems International, Hughes LAN Systems, March 1991.
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP",
RFC 1215, Performance Systems International, March 1991.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
of Management Information for Version 2 of the Simple Network of Management Information for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1902, January 1996. Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco
Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996.
[2] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Textual [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for Version 2 of the Simple Network Management Protocol Conventions for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1903, January 1996. (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[3] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Conformance [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance
Statements for Version 2 of the Simple Network Management Protocol Statements for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1904, January 1996. (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network
Operations for Version 2 of the Simple Network Management Protocol Management Protocol", RFC 1157, SNMP Research, Performance Systems
(SNMPv2)", RFC 1905, January 1996. International, Performance Systems International, MIT Laboratory
for Computer Science, May 1990.
[5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, SNMP Research,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport
Mappings for Version 2 of the Simple Network Management Protocol Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, January 1996. (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Management [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Information Base for Version 2 of the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMPv2)", RFC 1907, January 1996. Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems,
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[7] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for
"Coexistence between Version 1 and Version 2 of the Internet- version 3 of the Simple Network Management Protocol (SNMPv3)", RFC
standard Network Management Framework", RFC 1908, January 1996. 2274, IBM T. J. Watson Research, January 1998.
[8] Freed, N., Kille, S., "The Network Services Monitoring MIB", [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco
Systems, January 1998.
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc.,
Cisco Systems, Inc., January 1998.
[16] Freed, N., Kille, S., "The Network Services Monitoring MIB",
Internet Draft, November 1998. Internet Draft, November 1998.
[9] Kille, S., "A String Representation of Distinguished Names", RFC [17] Kille, S., "A String Representation of Distinguished Names", RFC
1779, March 1995. 1779, March 1995.
[10] Freed, N., Kille, S., "Mail Monitoring MIB", RFC 2249, January [18] Freed, N., Kille, S., "Mail Monitoring MIB", RFC 2249, January
1998. 1998.
[11] Freed, N., Kille, S., "Mail Monitoring MIB", RFC 1566, January [19] Freed, N., Kille, S., "Mail Monitoring MIB", RFC 1566, January
1994. 1994.
[12] Kille, S., "Mapping between X.400(1988) and RFC 822/MIME", RFC [20] Kille, S., "Mapping between X.400(1988) and RFC 822/MIME", RFC
2156, January 1998. 2156, January 1998.
[13] Crocker, D., "Standard for the Format of ARPA Internet Text [21] Crocker, D., "Standard for the Format of ARPA Internet Text
Message", STD 11, RFC 822, August 1982. Message", STD 11, RFC 822, August 1982.
[14] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893, [22] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893,
January 1996. January 1996.
10. Security Considerations 10. Security Considerations
This MIB does not offer write access, and as such cannot be used to This MIB does not offer write access, and as such cannot be used to
actively attack a system. However, this MIB does provide passive actively attack a system. However, this MIB does provide passive
information about the existance, type, and configuration of applications information about the existance, type, and configuration of applications
on a given host that could potentially indicate some sort of on a given host that could potentially indicate some sort of
vulnerability. Finally, the information MIB provides about network usage vulnerability. Finally, the information MIB provides about network usage
could be used to analyze network traffic patterns. could be used to analyze network traffic patterns.
SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the
User-based Security Model RFC 2274 [12] and the View-based Access
Control Model RFC 2275 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity
giving access to an instance of this MIB, is properly configured to give
access to the objects only to those principals (users) that have
legitimate rights to indeed GET or SET (change/create/delete) them.
11. Author and Chair Addresses 11. Author and Chair Addresses
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
skipping to change at page 36, line 28 skipping to change at page 38, line 14
Steve Kille, MADMAN WG Chair Steve Kille, MADMAN WG Chair
ISODE Consortium ISODE Consortium
The Dome, The Square The Dome, The Square
Richmond TW9 1DT Richmond TW9 1DT
UK 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 (1998). 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
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing the document itself may not be modified in any way, such as by removing the
copyright notice or references to the Internet Society or other copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of developing Internet organizations, except as needed for the purpose of developing
 End of changes. 44 change blocks. 
72 lines changed or deleted 160 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/