idnits 2.17.1 draft-ietf-ipngwg-ipv6-udp-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. 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 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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 358 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 is 1 instance of too long lines in the document, the longest one being 2 characters in excess of 72. ** There are 43 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 309 has weird spacing: '...defined in t...' == Line 312 has weird spacing: '...ication of r...' -- 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 (January 1998) is 9598 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) == Unused Reference: 'IPV6' is defined on line 302, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '1' ** Obsolete normative reference: RFC 1902 (ref. '2') (Obsoleted by RFC 2578) -- Possible downref: Non-RFC (?) normative reference: ref. 'UDP MIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'IPV6' Summary: 10 errors (**), 0 flaws (~~), 5 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft UDP MIB for IPv6 January 1998 3 Expires July, 1998 5 IP Version 6 Management Information Base 6 for the User Datagram Protocol 8 10 Mike Daniele 11 Digital Equipment Corporation 13 Status of this Memo 15 This document is an Internet-Draft. Internet-Drafts are working 16 documents of the Internet Engineering Task Force (IETF), its 17 areas, and its working groups. Note that other groups may also 18 distribute working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six 21 months and may be updated, replaced, or obsoleted by other 22 documents at any time. It is inappropriate to use Internet- 23 Drafts as reference material or to cite them other than as 24 "work in progress." 26 To view the entire list of current Internet-Drafts, please check 27 the "1id-abstracts.txt" listing contained in the Internet-Drafts 28 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 29 (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East 30 Coast), or ftp.isi.edu (US West Coast). 32 Abstract 34 This document is one in the series of documents that define 35 various MIB objects for IPv6. Specifically, this document 36 is the MIB module which defines managed objects for 37 implementations of the User Datagram Protocol (UDP) 38 over IP Version 6 (IPv6). 40 This document also recommends a specific policy with respect to 41 the applicability of RFC 2013 for implementations of IPv6. 42 Namely, that most of managed objects defined in RFC 2013 are 43 independent of which IP versions underlie UDP, and only the 44 UDP listener information is IP version-specific. 46 This memo defines an experimental portion of the Management 47 Information Base (MIB) for use with network management 48 protocols in IPv6-based internets. 50 1. Introduction 52 A management system contains: several (potentially many) nodes, each 53 with a processing entity, termed an agent, which has access to 54 management instrumentation; at least one management station; and, a 55 management protocol, used to convey management information between 56 the agents and management stations. Operations of the protocol are 57 carried out under an administrative framework which defines 58 authentication, authorization, access control, and privacy policies. 60 Management stations execute management applications which monitor and 61 control managed elements. Managed elements are devices such as 62 hosts, routers, terminal servers, etc., which are monitored and 63 controlled via access to their management information. 65 Management information is viewed as a collection of managed objects, 66 residing in a virtual information store, termed the Management 67 Information Base (MIB). Collections of related objects are defined 68 in MIB modules. These modules are written using a subset of OSI's 69 Abstract Syntax Notation One (ASN.1) [1], termed the Structure of 70 Management Information (SMI) [2]. 72 2. Overview 74 This document is one in the series of documents that define various 75 MIB objects, and statements of conformance, for IPv6. This document 76 defines the required instrumentation for implementations of UDP over 77 IPv6. 79 3. Transparency of IP versions to UDP 81 The fact that UDP is carried over IPv6 as opposed to IPv4, 82 is largely invisible to a UDP implementation. A "UDPng" did 83 not need to be defined, implementations simply need to support 84 IPv6 addresses. 86 As such, the managed objects already defined in [UDP MIB] are 87 sufficient for managing UDP in the presence of IPv6. These objects 88 are equally applicable whether the managed node supports IPv4 only, 89 IPv6 only, or both IPv4 and IPv6. 91 For example, udpInDatagrams counts "The total number of UDP datagrams 92 delivered to UDP users", regardless of which version of IP is used 93 to deliver any of those datagrams. 95 Stated differently, UDP implementations don't need separate counters 96 for IPv4 and for IPv6. 98 4. Representing UDP Listeners 100 The exception to the statements in section 3 is the udpTable. 101 Since IPv6 addresses cannot be represented with the IpAddress syntax, 102 not all UDP endpoints can be represented in the udpTable 103 defined in [UDP MIB]. 105 This memo defines a new, separate table to represent only those 106 UDP endpoints that utilize an IPv6 address. UDP endpoints on 107 IPv4 addresses continue to be represented in udpTable [UDP MIB]. 109 A different approach would have been to define a new table to 110 represent all UDP endpoints regardless of IP version. This would 111 require changes to [UDP MIB] and hence to existing (IPv4-only) 112 UDP implementations. The approach suggested in this memo has the 113 advantage of leaving IPv4-only implementations intact. 115 It is assumed that the objects defined in this memo will eventually 116 be defined in an update to [UDP MIB]. For this reason, the module 117 identity is assigned under the experimental portion of the MIB. 119 5. Conformance 121 This memo contains conformance statements to define conformance 122 to this MIB for UDP over IPv6 implementations. 124 6. Definitions 126 IPV6-UDP-MIB DEFINITIONS ::= BEGIN 128 IMPORTS 129 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 130 MODULE-IDENTITY, OBJECT-TYPE, 131 mib-2, experimental FROM SNMPv2-SMI 132 Ipv6Address, Ipv6IfIndexOrZero FROM IPV6-TC; 134 ipv6UdpMIB MODULE-IDENTITY 135 LAST-UPDATED "9801290000Z" 136 ORGANIZATION "IETF IPv6 MIB Working Group" 137 CONTACT-INFO 138 " Mike Daniele 140 Postal: Digital Equipment Corporation 141 110 Spitbrook Rd 142 Nashua, NH 03062. 143 US 145 Phone: +1 603 884 1423 146 Email: daniele@zk3.dec.com" 147 DESCRIPTION 148 "The MIB module for entities implementing UDP over IPv6." 149 ::= { experimental XXX } 151 -- objects specific to UDP for IPv6 153 udp OBJECT IDENTIFIER ::= { mib-2 7 } 155 -- the UDP over IPv6 Listener table 157 -- This table contains information about this entity's 158 -- UDP/IPv6 endpoints. Only endpoints utilizing IPv6 addresses 159 -- are contained in this table. This entity's UDP/IPv4 endpoints 160 -- are contained in udpTable. 162 ipv6UdpTable OBJECT-TYPE 163 SYNTAX SEQUENCE OF Ipv6UdpEntry 164 MAX-ACCESS not-accessible 165 STATUS current 166 DESCRIPTION 167 "A table containing UDP listener information for 168 UDP/IPv6 endpoints." 169 ::= { udp 6 } 171 ipv6UdpEntry OBJECT-TYPE 172 SYNTAX Ipv6UdpEntry 173 MAX-ACCESS not-accessible 174 STATUS current 175 DESCRIPTION 176 "Information about a particular current UDP listener. 178 Note that conceptual rows in this table require an 179 additional index object compared to udpTable, since 180 IPv6 addresses are not guaranteed to be unique on the 181 managed node." 182 INDEX { ipv6UdpLocalAddress, 183 ipv6UdpLocalPort, 184 ipv6UdpIfIndex } 185 ::= { ipv6UdpTable 1 } 187 Ipv6UdpEntry ::= SEQUENCE { 188 ipv6UdpLocalAddress Ipv6Address, 189 ipv6UdpLocalPort INTEGER (0..65535), 190 ipv6UdpIfIndex Ipv6IfIndexOrZero } 192 ipv6UdpLocalAddress OBJECT-TYPE 193 SYNTAX Ipv6Address 194 MAX-ACCESS not-accessible 195 STATUS current 196 DESCRIPTION 197 "The local IPv6 address for this UDP listener. 198 In the case of a UDP listener which is willing 199 to accept datagrams for any IPv6 address 200 associated with the managed node, the value ::0 201 is used." 202 ::= { ipv6UdpEntry 1 } 204 ipv6UdpLocalPort OBJECT-TYPE 205 SYNTAX INTEGER (0..65535) 206 MAX-ACCESS not-accessible 207 STATUS current 208 DESCRIPTION 209 "The local port number for this UDP listener." 210 ::= { ipv6UdpEntry 2 } 212 ipv6UdpIfIndex OBJECT-TYPE 213 SYNTAX Ipv6IfIndexOrZero 214 MAX-ACCESS read-only 215 STATUS current 216 DESCRIPTION 217 "An index object used to disambiguate conceptual rows in 218 the table, since the ipv6UdpLocalAddress/ipv6UdpLocalPort 219 pair may not be unique. 221 This object identifies the local interface that is 222 associated with ipv6UdpLocalAddress for this UDP listener. 223 If such a local interface cannot be determined, this object 224 should take on the value 0. (A possible example of this 225 would be if the value of ipv6UdpLocalAddress is ::0.) 227 The interface identified by a particular non-0 value of 228 this index is the same interface as identified by the same 229 value of ipv6IfIndex. 231 The value of this object must remain constant during 232 the life of this UDP endpoint." 233 ::= { ipv6UdpEntry 3 } 235 -- 236 -- conformance information 237 -- 239 ipv6UdpConformance OBJECT IDENTIFIER ::= { ipv6UdpMIB 2 } 241 ipv6UdpCompliances OBJECT IDENTIFIER ::= { ipv6UdpConformance 1 } 242 ipv6UdpGroups OBJECT IDENTIFIER ::= { ipv6UdpConformance 2 } 244 -- compliance statements 246 ipv6UdpCompliance MODULE-COMPLIANCE 247 STATUS current 248 DESCRIPTION 249 "The compliance statement for SNMPv2 entities which 250 implement UDP over IPv6." 251 MODULE -- this module 252 MANDATORY-GROUPS { ipv6UdpGroup } 253 ::= { ipv6UdpCompliances 1 } 255 ipv6UdpGroup OBJECT-GROUP 256 OBJECTS { -- these are defined in this module 257 -- ipv6UdpLocalAddress (not-accessible) 258 -- ipv6UdpLocalPort (not-accessible) 259 ipv6UdpIfIndex } 260 STATUS current 261 DESCRIPTION 262 "The group of objects providing management of 263 UDP over IPv6." 264 ::= { ipv6UdpGroups 1 } 266 END 268 7. Acknowledgments 270 This memo is a product of the IPng work group, and benefited especially 271 from the contributions of the following working group members: 273 Dimitry Haskin Bay Networks 274 Margaret Forsythe Epilogue 275 Tim Hartrick Mentat 276 Frank Solensky FTP 277 Jack McCann DEC 279 8. References 281 [1] Information processing systems - Open Systems Interconnection - 282 Specification of Abstract Syntax Notation One (ASN.1), 283 International Organization for Standardization. International 284 Standard 8824, (December, 1987). 286 [2] McCloghrie, K., Editor, "Structure of Management Information 287 for version 2 of the Simple Network Management Protocol 288 (SNMPv2)", RFC 1902, Cisco Systems, January 1996. 290 [UDP MIB] 292 SNMPv2 Working Group, McCloghrie, K., Editor, 293 "SNMPv2 Management Information Base for the User 294 Datagram Protocol using SMIv2", RFC 2013, November 1996. 296 [IPV6 MIB TC] 298 Haskin, D., and S. Onishi, "Management Information Base 299 for IP Version 6: Textual Conventions and General Group", 300 Work in progress. 302 [IPV6] 304 Deering, S., and R. Hinden, "Internet Protocol, Version 6 305 (IPv6) Specification", RFC 1883, December 1995. 307 9. Security Considerations 309 Certain management information defined in this MIB may be 310 considered sensitive in some network environments. 312 Therefore, authentication of received SNMP requests and 313 controlled access to management information should be employed 314 in such environments. 316 10. Author's Address 318 Mike Daniele 319 Digital Equipment Corporation 320 110 Spit Brook Rd 321 Nashua, NH 03062 323 Phone: +1-603-884-1423 324 EMail: daniele@zk3.dec.com 326 11. Full Copyright Statement 328 Copyright (C) The Internet Society (1998). All Rights Reserved. 330 This document and translations of it may be copied and furnished to 331 others, and derivative works that comment on or otherwise explain it 332 or assist in its implementation may be prepared, copied, published 333 and distributed, in whole or in part, without restriction of any 334 kind, provided that the above copyright notice and this paragraph are 335 included on all such copies and derivative works. However, this 336 document itself may not be modified in any way, such as by removing 337 the copyright notice or references to the Internet Society or other 338 Internet organizations, except as needed for the purpose of 339 developing Internet standards in which case the procedures for 340 copyrights defined in the Internet Standards process must be 341 followed, or as required to translate it into languages other than 342 English. 344 The limited permissions granted above are perpetual and will not be 345 revoked by the Internet Society or its successors or assigns. 347 This document and the information contained herein is provided on an 348 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 349 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 350 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 351 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 352 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 354 Expires July, 1998