idnits 2.17.1 draft-ietf-snmpv2-udp-ds-02.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 document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** 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. 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.) -- Couldn't find a document date in the document -- date freshness check skipped. 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. -------------------------------------------------------------------------------- 1 SNMPv2 Management Information Base 2 for the User Datagram Protocol 4 Fri Jun 30 23:59:59 1995 6 draft-ietf-snmpv2-udp-ds-02.txt 8 Jeffrey D. Case 9 SNMP Research, Inc. 10 case@snmp.com 12 Keith McCloghrie 13 Cisco Systems, Inc. 14 kzm@cisco.com 16 Marshall T. Rose 17 Dover Beach Consulting, Inc. 18 mrose@dbc.mtview.ca.us 20 Steven Waldbusser 21 Carnegie Mellon University 22 waldbusser@cmu.edu 24 Status of this Memo 26 This document is an Internet-Draft. Internet-Drafts are working 27 documents of the Internet Engineering Task Force (IETF), its areas, and 28 its working groups. Note that other groups may also distribute working 29 documents as Internet-Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet- Drafts as reference material 34 or to cite them other than as ``work in progress.'' 36 To learn the current status of any Internet-Draft, please check the 37 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 38 Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 39 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 41 1. Introduction 43 A management system contains: several (potentially many) nodes, each 44 with a processing entity, termed an agent, which has access to 45 management instrumentation; at least one management station; and, a 46 management protocol, used to convey management information between the 47 agents and management stations. Operations of the protocol are carried 48 out under an administrative framework which defines authentication, 49 authorization, access control, and privacy policies. 51 Management stations execute management applications which monitor and 52 control managed elements. Managed elements are devices such as hosts, 53 routers, terminal servers, etc., which are monitored and controlled via 54 access to their management information. 56 Management information is viewed as a collection of managed objects, 57 residing in a virtual information store, termed the Management 58 Information Base (MIB). Collections of related objects are defined in 59 MIB modules. These modules are written using a subset of OSI's Abstract 60 Syntax Notation One (ASN.1) [1], termed the Structure of Management 61 Information (SMI) [2]. 63 This document is the MIB module which defines managed objects for 64 managing implementations of the User Datagram Protocol (UDP) [3]. 66 The managed objects in this MIB module were originally defined using the 67 SNMPv1 framework as a part of MIB-II [4]. This document defines the 68 same objects for UDP using the SNMPv2 framework. 70 2. Definitions 72 UDP-MIB DEFINITIONS ::= BEGIN 74 IMPORTS 75 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 76 experimental, -- to be removed later 77 IpAddress, mib-2 FROM SNMPv2-SMI 78 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 80 udpMIB MODULE-IDENTITY 81 LAST-UPDATED "9411010000Z" 82 ORGANIZATION "IETF SNMPv2 Working Group" 83 CONTACT-INFO 84 " Keith McCloghrie 86 Postal: Cisco Systems, Inc. 87 170 West Tasman Drive 88 San Jose, CA 95134-1706 89 US 91 Phone: +1 408 526 5260 92 Email: kzm@cisco.com" 93 DESCRIPTION 94 "The MIB module for managing UDP implementations." 95 REVISION "9103310000Z" 96 DESCRIPTION 97 "The initial revision of this MIB module was part of MIB- 98 II." 99 -- to be assigned as {mib-2 xx} by IANA 100 ::= { experimental xx } 102 -- the UDP group 104 udp OBJECT IDENTIFIER ::= { mib-2 7 } 106 udpInDatagrams OBJECT-TYPE 107 SYNTAX Counter32 108 MAX-ACCESS read-only 109 STATUS current 110 DESCRIPTION 111 "The total number of UDP datagrams delivered to UDP users." 112 ::= { udp 1 } 114 udpNoPorts OBJECT-TYPE 115 SYNTAX Counter32 116 MAX-ACCESS read-only 117 STATUS current 118 DESCRIPTION 119 "The total number of received UDP datagrams for which there 120 was no application at the destination port." 121 ::= { udp 2 } 123 udpInErrors OBJECT-TYPE 124 SYNTAX Counter32 125 MAX-ACCESS read-only 126 STATUS current 127 DESCRIPTION 128 "The number of received UDP datagrams that could not be 129 delivered for reasons other than the lack of an application 130 at the destination port." 131 ::= { udp 3 } 133 udpOutDatagrams OBJECT-TYPE 134 SYNTAX Counter32 135 MAX-ACCESS read-only 136 STATUS current 137 DESCRIPTION 138 "The total number of UDP datagrams sent from this entity." 139 ::= { udp 4 } 141 -- the UDP Listener table 143 -- The UDP listener table contains information about this 144 -- entity's UDP end-points on which a local application is 145 -- currently accepting datagrams. 147 udpTable OBJECT-TYPE 148 SYNTAX SEQUENCE OF UdpEntry 149 MAX-ACCESS not-accessible 150 STATUS current 151 DESCRIPTION 152 "A table containing UDP listener information." 153 ::= { udp 5 } 155 udpEntry OBJECT-TYPE 156 SYNTAX UdpEntry 157 MAX-ACCESS not-accessible 158 STATUS current 159 DESCRIPTION 160 "Information about a particular current UDP listener." 161 INDEX { udpLocalAddress, udpLocalPort } 162 ::= { udpTable 1 } 164 UdpEntry ::= SEQUENCE { 165 udpLocalAddress IpAddress, 166 udpLocalPort INTEGER 167 } 169 udpLocalAddress OBJECT-TYPE 170 SYNTAX IpAddress 171 MAX-ACCESS read-only 172 STATUS current 173 DESCRIPTION 174 "The local IP address for this UDP listener. In the case of 175 a UDP listener which is willing to accept datagrams for any 176 IP interface associated with the node, the value 0.0.0.0 is 177 used." 178 ::= { udpEntry 1 } 180 udpLocalPort OBJECT-TYPE 181 SYNTAX INTEGER (0..65535) 182 MAX-ACCESS read-only 183 STATUS current 184 DESCRIPTION 185 "The local port number for this UDP listener." 186 ::= { udpEntry 2 } 188 -- conformance information 190 udpMIBConformance OBJECT IDENTIFIER ::= { udpMIB 2 } 192 udpMIBCompliances OBJECT IDENTIFIER ::= { udpMIBConformance 1 } 193 udpMIBGroups OBJECT IDENTIFIER ::= { udpMIBConformance 2 } 195 -- compliance statements 197 udpMIBCompliance MODULE-COMPLIANCE 198 STATUS current 199 DESCRIPTION 200 "The compliance statement for SNMPv2 entities which 201 implement UDP." 202 MODULE -- this module 203 MANDATORY-GROUPS { udpGroup 204 } 205 ::= { udpMIBCompliances 1 } 207 -- units of conformance 209 udpGroup OBJECT-GROUP 210 OBJECTS { udpInDatagrams, udpNoPorts, 211 udpInErrors, udpOutDatagrams, 212 udpLocalAddress, udpLocalPort } 213 STATUS current 214 DESCRIPTION 215 "The udp group of objects providing for management of UDP 216 entities." 217 ::= { udpMIBGroups 1 } 219 END 220 3. Acknowledgements 222 This document contains a modified subset of RFC 1213. 224 4. References 226 [1] Information processing systems - Open Systems Interconnection - 227 Specification of Abstract Syntax Notation One (ASN.1), 228 International Organization for Standardization. International 229 Standard 8824, (December, 1987). 231 [2] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Structure 232 of Management Information for version 2 of the Simple Network 233 Management Protocol (SNMPv2)", Internet Draft, SNMP Research, Inc., 234 Cisco Systems, Dover Beach Consulting, Inc., Carnegie Mellon 235 University, March 1995. 237 [3] Postel, J., "User Datagram Protocol", STD 6, RFC 768, USC-ISI, 238 August 1980. 240 [4] McCloghrie, K., and Rose, M., "Management Information Base for 241 Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 242 1213, March 1991. 244 5. Security Considerations 246 Security issues are not discussed in this memo. 248 6. Authors' Addresses 250 Jeffrey D. Case 251 SNMP Research, Inc. 252 3001 Kimberlin Heights Rd. 253 Knoxville, TN 37920-9716 254 US 256 Phone: +1 615 573 1434 257 Email: case@snmp.com 259 Keith McCloghrie 260 Cisco Systems, Inc. 261 170 West Tasman Drive 262 San Jose, CA 95134-1706 263 US 265 Phone: +1 408 526 5260 266 Email: kzm@cisco.com 268 Marshall T. Rose 269 Dover Beach Consulting, Inc. 270 420 Whisman Court 271 Mountain View, CA 94043-2186 272 US 274 Phone: +1 415 968 1052 275 Email: mrose@dbc.mtview.ca.us 277 Steven Waldbusser 278 Carnegie Mellon University 279 5000 Forbes Ave 280 Pittsburgh, PA 15213 281 US 283 Phone: +1 412 268 6628 284 Email: waldbusser@cmu.edu 286 Table of Contents 288 1 Introduction .................................................... 3 289 2 Definitions ..................................................... 4 290 2.1 The UDP Group ................................................. 5 291 2.2 Conformance Information ....................................... 7 292 2.2.1 Compliance Statements ....................................... 7 293 2.2.2 Units of Conformance ........................................ 7 294 3 Acknowledgements ................................................ 8 295 4 References ...................................................... 8 296 5 Security Considerations ......................................... 9 297 6 Authors' Addresses .............................................. 9