draft-ietf-snmpv2-udp-ds-02.txt   rfc2013.txt 
SNMPv2 Management Information Base
for the User Datagram Protocol
Fri Jun 30 23:59:59 1995
draft-ietf-snmpv2-udp-ds-02.txt Network Working Group K. McCloghrie, Editor
Request for Comments: 2013 Cisco Systems
Jeffrey D. Case Updates: 1213 November 1996
SNMP Research, Inc. Category: Standards Track
case@snmp.com
Keith McCloghrie SNMPv2 Management Information Base
Cisco Systems, Inc. for the User Datagram Protocol using SMIv2
kzm@cisco.com
Marshall T. Rose Status of this Memo
Dover Beach Consulting, Inc.
mrose@dbc.mtview.ca.us
Steven Waldbusser This document specifies an Internet standards track protocol for the
Carnegie Mellon University Internet community, and requests discussion and suggestions for
waldbusser@cmu.edu 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.
Status of this Memo IESG Note:
This document is an Internet-Draft. Internet-Drafts are working The IP, UDP, and TCP MIB modules currently support only IPv4. These
documents of the Internet Engineering Task Force (IETF), its areas, and three modules use the IpAddress type defined as an OCTET STRING of
its working groups. Note that other groups may also distribute working length 4 to represent the IPv4 32-bit internet addresses. (See RFC
documents as Internet-Drafts. 1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6
internet addresses.
Internet-Drafts are draft documents valid for a maximum of six months Table of Contents
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the 1. Introduction ................................................. 1
``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 2. Definitions .................................................. 2
Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 2.1 The UDP Group ............................................... 3
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 2.2 Conformance Information ..................................... 5
2.2.1 Compliance Statements ..................................... 5
2.2.2 Units of Conformance ...................................... 5
3. Acknowledgements ............................................. 6
4. References ................................................... 6
5. Security Considerations ...................................... 6
6. Editor's Address ............................................. 6
1. Introduction 1. Introduction
A management system contains: several (potentially many) nodes, each A management system contains: several (potentially many) nodes, each
with a processing entity, termed an agent, which has access to with a processing entity, termed an agent, which has access to
management instrumentation; at least one management station; and, a management instrumentation; at least one management station; and, a
management protocol, used to convey management information between the management protocol, used to convey management information between
agents and management stations. Operations of the protocol are carried the agents and management stations. Operations of the protocol are
out under an administrative framework which defines authentication, carried out under an administrative framework which defines
authorization, access control, and privacy policies. authentication, authorization, access control, and privacy policies.
Management stations execute management applications which monitor and Management stations execute management applications which monitor and
control managed elements. Managed elements are devices such as hosts, control managed elements. Managed elements are devices such as
routers, terminal servers, etc., which are monitored and controlled via hosts, routers, terminal servers, etc., which are monitored and
access to their management information. controlled via access to their management information.
Management information is viewed as a collection of managed objects, Management information is viewed as a collection of managed objects,
residing in a virtual information store, termed the Management residing in a virtual information store, termed the Management
Information Base (MIB). Collections of related objects are defined in Information Base (MIB). Collections of related objects are defined
MIB modules. These modules are written using a subset of OSI's Abstract in MIB modules. These modules are written using a subset of OSI's
Syntax Notation One (ASN.1) [1], termed the Structure of Management Abstract Syntax Notation One (ASN.1) [1], termed the Structure of
Information (SMI) [2]. Management Information (SMI) [2].
This document is the MIB module which defines managed objects for This document is the MIB module which defines managed objects for
managing implementations of the User Datagram Protocol (UDP) [3]. managing implementations of the User Datagram Protocol (UDP) [3].
The managed objects in this MIB module were originally defined using the The managed objects in this MIB module were originally defined using
SNMPv1 framework as a part of MIB-II [4]. This document defines the the SNMPv1 framework as a part of MIB-II [4]. This document defines
same objects for UDP using the SNMPv2 framework. the same objects for UDP using the SNMPv2 framework.
2. Definitions 2. Definitions
UDP-MIB DEFINITIONS ::= BEGIN UDP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32, MODULE-IDENTITY, OBJECT-TYPE, Counter32,
experimental, -- to be removed later
IpAddress, mib-2 FROM SNMPv2-SMI IpAddress, mib-2 FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
udpMIB MODULE-IDENTITY udpMIB MODULE-IDENTITY
LAST-UPDATED "9411010000Z" LAST-UPDATED "9411010000Z"
ORGANIZATION "IETF SNMPv2 Working Group" ORGANIZATION "IETF SNMPv2 Working Group"
CONTACT-INFO CONTACT-INFO
" Keith McCloghrie " Keith McCloghrie
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
skipping to change at page 4, line 28 skipping to change at page 3, line 4
CONTACT-INFO CONTACT-INFO
" Keith McCloghrie " Keith McCloghrie
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
US US
Phone: +1 408 526 5260 Phone: +1 408 526 5260
Email: kzm@cisco.com" Email: kzm@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module for managing UDP implementations." "The MIB module for managing UDP implementations."
REVISION "9103310000Z" REVISION "9103310000Z"
DESCRIPTION DESCRIPTION
"The initial revision of this MIB module was part of MIB- "The initial revision of this MIB module was part of MIB-
II." II."
-- to be assigned as {mib-2 xx} by IANA ::= { mib-2 50 }
::= { experimental xx }
-- the UDP group -- the UDP group
udp OBJECT IDENTIFIER ::= { mib-2 7 } udp OBJECT IDENTIFIER ::= { mib-2 7 }
udpInDatagrams OBJECT-TYPE udpInDatagrams OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 8, line 6 skipping to change at page 6, line 6
udpLocalAddress, udpLocalPort } udpLocalAddress, udpLocalPort }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The udp group of objects providing for management of UDP "The udp group of objects providing for management of UDP
entities." entities."
::= { udpMIBGroups 1 } ::= { udpMIBGroups 1 }
END END
3. Acknowledgements 3. Acknowledgements
This document contains a modified subset of RFC 1213. This document contains a modified subset of RFC 1213.
4. References 4. References
[1] Information processing systems - Open Systems Interconnection - [1] Information processing systems - Open Systems Interconnection
Specification of Abstract Syntax Notation One (ASN.1), Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization. International International Organization for Standardization. International
Standard 8824, (December, 1987). Standard 8824, (December, 1987).
[2] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Structure [2] McCloghrie, K., Editor, "Structure of Management Information
of Management Information for version 2 of the Simple Network for version 2 of the Simple Network Management Protocol
Management Protocol (SNMPv2)", Internet Draft, SNMP Research, Inc., (SNMPv2)", RFC 1902, Cisco Systems, January 1996.
Cisco Systems, Dover Beach Consulting, Inc., Carnegie Mellon
University, March 1995.
[3] Postel, J., "User Datagram Protocol", STD 6, RFC 768, USC-ISI, [3] Postel, J., "User Datagram Protocol", STD 6, RFC 768, USC-ISI,
August 1980. August 1980.
[4] McCloghrie, K., and Rose, M., "Management Information Base for [4] McCloghrie, K., and Rose, M., "Management Information Base for
Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC Network Management of TCP/IP-based internets: MIB-II", STD 17,
1213, March 1991. RFC 1213, March 1991.
5. Security Considerations 5. Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
6. Authors' Addresses
Jeffrey D. Case
SNMP Research, Inc.
3001 Kimberlin Heights Rd.
Knoxville, TN 37920-9716
US
Phone: +1 615 573 1434
Email: case@snmp.com
Keith McCloghrie
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
US
Phone: +1 408 526 5260
Email: kzm@cisco.com
Marshall T. Rose
Dover Beach Consulting, Inc.
420 Whisman Court
Mountain View, CA 94043-2186
US
Phone: +1 415 968 1052
Email: mrose@dbc.mtview.ca.us
Steven Waldbusser
Carnegie Mellon University
5000 Forbes Ave
Pittsburgh, PA 15213
US
Phone: +1 412 268 6628 6. Editor's Address
Email: waldbusser@cmu.edu
Table of Contents Keith McCloghrie
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
US
1 Introduction .................................................... 3 Phone: +1 408 526 5260
2 Definitions ..................................................... 4 EMail: kzm@cisco.com
2.1 The UDP Group ................................................. 5
2.2 Conformance Information ....................................... 7
2.2.1 Compliance Statements ....................................... 7
2.2.2 Units of Conformance ........................................ 7
3 Acknowledgements ................................................ 8
4 References ...................................................... 8
5 Security Considerations ......................................... 9
6 Authors' Addresses .............................................. 9
 End of changes. 26 change blocks. 
110 lines changed or deleted 73 lines changed or added

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