idnits 2.17.1 draft-ietf-snmpv2-udp-ds-00.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-24) 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. 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 (November 1994) is 10753 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: 9 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 November 1994 4 SNMPv2 Management Information Base 5 for the User Datagram Protocol 7 1 November 1994 9 Jeffrey D. Case 10 SNMP Research, Inc. 11 case@snmp.com 13 Keith McCloghrie 14 Cisco Systems, Inc. 15 kzm@cisco.com 17 Marshall T. Rose 18 Dover Beach Consulting, Inc. 19 mrose@dbc.mtview.ca.us 21 Steven Waldbusser 22 Carnegie Mellon University 23 waldbusser@cmu.edu 25 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 -- to be assigned as {mib-2 xx} by IANA 99 ::= { experimental xx } 101 -- the UDP group 103 udp OBJECT IDENTIFIER ::= { mib-2 7 } 105 udpInDatagrams OBJECT-TYPE 106 SYNTAX Counter32 107 MAX-ACCESS read-only 108 STATUS current 109 DESCRIPTION 110 "The total number of UDP datagrams delivered to UDP users." 111 ::= { udp 1 } 113 udpNoPorts OBJECT-TYPE 114 SYNTAX Counter32 115 MAX-ACCESS read-only 116 STATUS current 117 DESCRIPTION 118 "The total number of received UDP datagrams for which there 119 was no application at the destination port." 120 ::= { udp 2 } 122 udpInErrors OBJECT-TYPE 123 SYNTAX Counter32 124 MAX-ACCESS read-only 125 STATUS current 126 DESCRIPTION 127 "The number of received UDP datagrams that could not be 128 delivered for reasons other than the lack of an application 129 at the destination port." 130 ::= { udp 3 } 132 udpOutDatagrams OBJECT-TYPE 133 SYNTAX Counter32 134 MAX-ACCESS read-only 135 STATUS current 136 DESCRIPTION 137 "The total number of UDP datagrams sent from this entity." 138 ::= { udp 4 } 140 -- the UDP Listener table 142 -- The UDP listener table contains information about this 143 -- entity's UDP end-points on which a local application is 144 -- currently accepting datagrams. 146 udpTable OBJECT-TYPE 147 SYNTAX SEQUENCE OF UdpEntry 148 MAX-ACCESS not-accessible 149 STATUS current 150 DESCRIPTION 151 "A table containing UDP listener information." 152 ::= { udp 5 } 154 udpEntry OBJECT-TYPE 155 SYNTAX UdpEntry 156 MAX-ACCESS not-accessible 157 STATUS current 158 DESCRIPTION 159 "Information about a particular current UDP listener." 160 INDEX { udpLocalAddress, udpLocalPort } 161 ::= { udpTable 1 } 163 UdpEntry ::= SEQUENCE { 164 udpLocalAddress IpAddress, 165 udpLocalPort INTEGER 166 } 168 udpLocalAddress OBJECT-TYPE 169 SYNTAX IpAddress 170 MAX-ACCESS read-only 171 STATUS current 172 DESCRIPTION 173 "The local IP address for this UDP listener. In the case of 174 a UDP listener which is willing to accept datagrams for any 175 IP interface associated with the node, the value 0.0.0.0 is 176 used." 177 ::= { udpEntry 1 } 179 udpLocalPort OBJECT-TYPE 180 SYNTAX INTEGER (0..65535) 181 MAX-ACCESS read-only 182 STATUS current 183 DESCRIPTION 184 "The local port number for this UDP listener." 185 ::= { udpEntry 2 } 187 -- conformance information 189 udpMIBConformance OBJECT IDENTIFIER ::= { udpMIB 2 } 191 udpMIBCompliances OBJECT IDENTIFIER ::= { udpMIBConformance 1 } 192 udpMIBGroups OBJECT IDENTIFIER ::= { udpMIBConformance 2 } 194 -- compliance statements 196 udpMIBCompliance MODULE-COMPLIANCE 197 STATUS current 198 DESCRIPTION 199 "The compliance statement for SNMPv2 entities which 200 implement UDP." 201 MODULE -- this module 202 MANDATORY-GROUPS { udpGroup 203 } 204 ::= { udpMIBCompliances 1 } 206 -- units of conformance 208 udpGroup OBJECT-GROUP 209 OBJECTS { udpInDatagrams, udpNoPorts, 210 udpInErrors, udpOutDatagrams, 211 udpLocalAddress, udpLocalPort } 212 STATUS current 213 DESCRIPTION 214 "The udp group of objects providing for management of UDP 215 entities." 216 ::= { udpMIBGroups 1 } 218 END 219 3. Acknowledgements 221 This document contains a modified subset of RFC 1213. 223 4. References 225 [1] Information processing systems - Open Systems Interconnection - 226 Specification of Abstract Syntax Notation One (ASN.1), 227 International Organization for Standardization. International 228 Standard 8824, (December, 1987). 230 [2] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Structure 231 of Management Information for version 2 of the Simple Network 232 Management Protocol (SNMPv2)", Internet Draft, SNMP Research, Inc., 233 Cisco Systems, Dover Beach Consulting, Inc., Carnegie Mellon 234 University, November 1994. 236 [3] Postel, J., "User Datagram Protocol", STD 6, RFC 768, USC-ISI, 237 August 1980. 239 [4] McCloghrie, K., and Rose, M., "Management Information Base for 240 Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 241 1213, March 1991. 243 5. Security Considerations 245 Security issues are not discussed in this memo. 247 6. Authors' Addresses 249 Jeffrey D. Case 250 SNMP Research, Inc. 251 3001 Kimberlin Heights Rd. 252 Knoxville, TN 37920-9716 253 US 255 Phone: +1 615 573 1434 256 Email: case@snmp.com 258 Keith McCloghrie 259 Cisco Systems, Inc. 260 170 West Tasman Drive, 261 San Jose CA 95134-1706. 263 Phone: +1 408 526 5260 264 Email: kzm@cisco.com 266 Marshall T. Rose 267 Dover Beach Consulting, Inc. 268 420 Whisman Court 269 Mountain View, CA 94043-2186 270 US 272 Phone: +1 415 968 1052 273 Email: mrose@dbc.mtview.ca.us 275 Steven Waldbusser 276 Carnegie Mellon University 277 5000 Forbes Ave 278 Pittsburgh, PA 15213 279 US 281 Phone: +1 412 268 6628 282 Email: waldbusser@cmu.edu 284 Table of Contents 286 1 Introduction .................................................... 2 287 2 Definitions ..................................................... 3 288 2.1 The UDP Group ................................................. 4 289 2.2 Conformance Information ....................................... 6 290 2.2.1 Compliance Statements ....................................... 6 291 2.2.2 Units of Conformance ........................................ 6 292 3 Acknowledgements ................................................ 7 293 4 References ...................................................... 7 294 5 Security Considerations ......................................... 8 295 6 Authors' Addresses .............................................. 8