idnits 2.17.1 draft-ietf-snmpv2-udp-ds-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 7 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 1995) is 10628 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' Summary: 10 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft SNMPv2 MIB for UDP March 1995 4 SNMPv2 Management Information Base 5 for the User Datagram Protocol 7 19 March 1995 | 9 draft-ietf-snmpv2-udp-ds-01.txt | 11 Jeffrey D. Case 12 SNMP Research, Inc. 13 case@snmp.com 15 Keith McCloghrie 16 Cisco Systems, Inc. 17 kzm@cisco.com 19 Marshall T. Rose 20 Dover Beach Consulting, Inc. 21 mrose@dbc.mtview.ca.us 23 Steven Waldbusser 24 Carnegie Mellon University 25 waldbusser@cmu.edu 27 Status of this Memo 29 This document is an Internet-Draft. Internet-Drafts are working 30 documents of the Internet Engineering Task Force (IETF), its areas, and 31 its working groups. Note that other groups may also distribute working 32 documents as Internet-Drafts. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet- Drafts as reference material 37 or to cite them other than as ``work in progress.'' 39 To learn the current status of any Internet-Draft, please check the 40 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 41 Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 42 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 44 1. Introduction 46 A management system contains: several (potentially many) nodes, each 47 with a processing entity, termed an agent, which has access to 48 management instrumentation; at least one management station; and, a 49 management protocol, used to convey management information between the 50 agents and management stations. Operations of the protocol are carried 51 out under an administrative framework which defines authentication, 52 authorization, access control, and privacy policies. 54 Management stations execute management applications which monitor and 55 control managed elements. Managed elements are devices such as hosts, 56 routers, terminal servers, etc., which are monitored and controlled via 57 access to their management information. 59 Management information is viewed as a collection of managed objects, 60 residing in a virtual information store, termed the Management 61 Information Base (MIB). Collections of related objects are defined in 62 MIB modules. These modules are written using a subset of OSI's Abstract 63 Syntax Notation One (ASN.1) [1], termed the Structure of Management 64 Information (SMI) [2]. 66 This document is the MIB module which defines managed objects for 67 managing implementations of the User Datagram Protocol (UDP) [3]. 69 The managed objects in this MIB module were originally defined using the 70 SNMPv1 framework as a part of MIB-II [4]. This document defines the 71 same objects for UDP using the SNMPv2 framework. 73 2. Definitions 75 UDP-MIB DEFINITIONS ::= BEGIN 77 IMPORTS 78 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 79 experimental, -- to be removed later 80 IpAddress, mib-2 FROM SNMPv2-SMI 81 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 83 udpMIB MODULE-IDENTITY 84 LAST-UPDATED "9411010000Z" 85 ORGANIZATION "IETF SNMPv2 Working Group" 86 CONTACT-INFO 87 " Keith McCloghrie 89 Postal: Cisco Systems, Inc. 90 170 West Tasman Drive 91 San Jose, CA 95134-1706 92 USA 94 Phone: +1 408 526 5260 95 Email: kzm@cisco.com" 96 DESCRIPTION 97 "The MIB module for managing UDP implementations." 98 REVISION "9103310000Z" + 99 DESCRIPTION + 100 "The initial revision of this MIB module was part of MIB- + 101 II." + 102 -- to be assigned as {mib-2 xx} by IANA 103 ::= { experimental xx } 105 -- the UDP group 107 udp OBJECT IDENTIFIER ::= { mib-2 7 } 109 udpInDatagrams OBJECT-TYPE 110 SYNTAX Counter32 111 MAX-ACCESS read-only 112 STATUS current 113 DESCRIPTION 114 "The total number of UDP datagrams delivered to UDP users." 115 ::= { udp 1 } 117 udpNoPorts OBJECT-TYPE 118 SYNTAX Counter32 119 MAX-ACCESS read-only 120 STATUS current 121 DESCRIPTION 122 "The total number of received UDP datagrams for which there 123 was no application at the destination port." 124 ::= { udp 2 } 126 udpInErrors OBJECT-TYPE 127 SYNTAX Counter32 128 MAX-ACCESS read-only 129 STATUS current 130 DESCRIPTION 131 "The number of received UDP datagrams that could not be 132 delivered for reasons other than the lack of an application 133 at the destination port." 134 ::= { udp 3 } 136 udpOutDatagrams OBJECT-TYPE 137 SYNTAX Counter32 138 MAX-ACCESS read-only 139 STATUS current 140 DESCRIPTION 141 "The total number of UDP datagrams sent from this entity." 142 ::= { udp 4 } 144 -- the UDP Listener table 146 -- The UDP listener table contains information about this 147 -- entity's UDP end-points on which a local application is 148 -- currently accepting datagrams. 150 udpTable OBJECT-TYPE 151 SYNTAX SEQUENCE OF UdpEntry 152 MAX-ACCESS not-accessible 153 STATUS current 154 DESCRIPTION 155 "A table containing UDP listener information." 156 ::= { udp 5 } 158 udpEntry OBJECT-TYPE 159 SYNTAX UdpEntry 160 MAX-ACCESS not-accessible 161 STATUS current 162 DESCRIPTION 163 "Information about a particular current UDP listener." 164 INDEX { udpLocalAddress, udpLocalPort } 165 ::= { udpTable 1 } 167 UdpEntry ::= SEQUENCE { 168 udpLocalAddress IpAddress, 169 udpLocalPort INTEGER 170 } 172 udpLocalAddress OBJECT-TYPE 173 SYNTAX IpAddress 174 MAX-ACCESS read-only 175 STATUS current 176 DESCRIPTION 177 "The local IP address for this UDP listener. In the case of 178 a UDP listener which is willing to accept datagrams for any 179 IP interface associated with the node, the value 0.0.0.0 is 180 used." 181 ::= { udpEntry 1 } 183 udpLocalPort OBJECT-TYPE 184 SYNTAX INTEGER (0..65535) 185 MAX-ACCESS read-only 186 STATUS current 187 DESCRIPTION 188 "The local port number for this UDP listener." 189 ::= { udpEntry 2 } 191 -- conformance information 193 udpMIBConformance OBJECT IDENTIFIER ::= { udpMIB 2 } 195 udpMIBCompliances OBJECT IDENTIFIER ::= { udpMIBConformance 1 } 196 udpMIBGroups OBJECT IDENTIFIER ::= { udpMIBConformance 2 } 198 -- compliance statements 200 udpMIBCompliance MODULE-COMPLIANCE 201 STATUS current 202 DESCRIPTION 203 "The compliance statement for SNMPv2 entities which 204 implement UDP." 205 MODULE -- this module 206 MANDATORY-GROUPS { udpGroup 207 } 208 ::= { udpMIBCompliances 1 } 210 -- units of conformance 212 udpGroup OBJECT-GROUP 213 OBJECTS { udpInDatagrams, udpNoPorts, 214 udpInErrors, udpOutDatagrams, 215 udpLocalAddress, udpLocalPort } 216 STATUS current 217 DESCRIPTION 218 "The udp group of objects providing for management of UDP 219 entities." 220 ::= { udpMIBGroups 1 } 222 END 223 3. Acknowledgements 225 This document contains a modified subset of RFC 1213. 227 4. References 229 [1] Information processing systems - Open Systems Interconnection - 230 Specification of Abstract Syntax Notation One (ASN.1), 231 International Organization for Standardization. International 232 Standard 8824, (December, 1987). 234 [2] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Structure 235 of Management Information for version 2 of the Simple Network 236 Management Protocol (SNMPv2)", Internet Draft, SNMP Research, Inc., 237 Cisco Systems, Dover Beach Consulting, Inc., Carnegie Mellon 238 University, March 1995. | 240 [3] Postel, J., "User Datagram Protocol", STD 6, RFC 768, USC-ISI, 241 August 1980. 243 [4] McCloghrie, K., and Rose, M., "Management Information Base for 244 Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 245 1213, March 1991. 247 5. Security Considerations 249 Security issues are not discussed in this memo. 251 6. Authors' Addresses 253 Jeffrey D. Case 254 SNMP Research, Inc. 255 3001 Kimberlin Heights Rd. 256 Knoxville, TN 37920-9716 257 US 259 Phone: +1 615 573 1434 260 Email: case@snmp.com 262 Keith McCloghrie 263 Cisco Systems, Inc. 264 170 West Tasman Drive, 265 San Jose CA 95134-1706. 267 Phone: +1 408 526 5260 268 Email: kzm@cisco.com 270 Marshall T. Rose 271 Dover Beach Consulting, Inc. 272 420 Whisman Court 273 Mountain View, CA 94043-2186 274 US 276 Phone: +1 415 968 1052 277 Email: mrose@dbc.mtview.ca.us 279 Steven Waldbusser 280 Carnegie Mellon University 281 5000 Forbes Ave 282 Pittsburgh, PA 15213 283 US 285 Phone: +1 412 268 6628 286 Email: waldbusser@cmu.edu 288 Table of Contents 290 1 Introduction .................................................... 3 291 2 Definitions ..................................................... 4 292 2.1 The UDP Group ................................................. 5 293 2.2 Conformance Information ....................................... 7 294 2.2.1 Compliance Statements ....................................... 7 295 2.2.2 Units of Conformance ........................................ 7 296 3 Acknowledgements ................................................ 8 297 4 References ...................................................... 8 298 5 Security Considerations ......................................... 9 299 6 Authors' Addresses .............................................. 9