idnits 2.17.1 draft-ietf-v6ops-ipv4survey-ops-02.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: ---------------------------------------------------------------------------- == 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 2577 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.) ** There are 2 instances of lines with control characters in the document. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 1432: '...TAX of NetworkAddress, the SYNTAX MUST...' RFC 2119 keyword, line 1448: '... object SHOULD contain the val...' RFC 2119 keyword, line 1479: '...TAX of NetworkAddress, the SYNTAX MUST...' RFC 2119 keyword, line 1495: '... object SHOULD contain the val...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The "Author's Address" (or "Authors' Addresses") section title is misspelled. == Line 82 has weird spacing: '...vacuum and pr...' == Line 83 has weird spacing: '...the problems ...' == Line 133 has weird spacing: '...ub tree is ri...' == Line 185 has weird spacing: '... octets cont...' == Line 1119 has weird spacing: '... octets cont...' == (4 more instances...) -- 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 2004) is 7406 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) -- Looks like a reference, but probably isn't: 'RFC1906' on line 1739 == Outdated reference: A later version (-06) exists of draft-ietf-v6ops-ipv4survey-intro-02 ** Downref: Normative reference to an Informational draft: draft-ietf-v6ops-ipv4survey-intro (ref. '1') Summary: 5 errors (**), 0 flaws (~~), 11 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Philip J. Nesser II 2 draft-ietf-v6ops-ipv4survey-ops-02.txt Nesser & Nesser Consulting 3 Internet Draft Andreas Bergstrom 4 Ostfold University College 5 August 2003 6 Expires January 2004 8 Survey of IPv4 Addresses in Currently Deployed 9 IETF Operations & Management Area Standards 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. 14 Status of this Memo 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that other 18 groups may also 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 documents at 22 any time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 Abstract 33 This document seeks to document all usage of IPv4 addresses in currently 34 deployed IETF Operations & Management Area documented standards. In 35 order to successfully transition from an all IPv4 Internet to an all 36 IPv6 Internet, many interim steps will be taken. One of these steps is 37 the evolution of current protocols that have IPv4 dependencies. It is 38 hoped that these protocols (and their implementations) will be 39 redesigned to be network address independent, but failing that will at 40 least dually support IPv4 and IPv6. To this end, all Standards (Full, 41 Draft, and Proposed) as well as Experimental RFCs will be surveyed and 42 any dependencies will be documented. 44 Table of Contents 46 1. Introduction 47 2. Document Organisation 48 3. Full Standards 49 4. Draft Standards 50 5. Proposed Standards 51 6. Experimental RFCs 52 7. Summary of Results 53 7.1 Standards 54 7.2 Draft Standards 55 7.3 Proposed Standards 56 7.4 Experimental RFCs 57 8. Security Consideration 58 9. Acknowledgements 59 10. References 60 11. Authors Address 61 12. Intellectual Property Statement 62 13. Full Copyright Statement 64 1.0 Introduction 66 This document is part of a document set aiming to document all usage of 67 IPv4 addresses in IETF stanadards. In an effort to have the information 68 in a manageable form, it has been broken into 7 documents conforming 69 to the current IETF areas (Application, Internet, Manangement & 70 Operations, Routing, Security, Sub-IP and Transport). 72 For a full introduction, please see the intro[1] draft. 74 2.0 Document Organization 76 The document is organized as described below: 78 Sections 3, 4, 5, and 6 each describe the raw analysis of Full, Draft, 79 and Proposed Standards, and Experimental RFCs. Each RFC is discussed in 80 its turn starting with RFC 1 and ending with RFC 3247. The comments for 81 each RFC is "raw" in nature. That is, each RFC is discussed in a 82 vacuum and problems or issues discussed do not "look ahead" to see if 83 the problems have already been fixed. 85 Section 7 is an analysis of the data presented in Sections 3, 4, 5, and 86 6. It is here that all of the results are considered as a whole and the 87 problems that have been resolved in later RFCs are correlated. 89 3.0 Full Standards 91 Full Internet Standards (most commonly simply referred to as 92 "Standards") are fully mature protocol specification that are widely 93 implemented and used throughout the Internet. 95 3.1 RFC 1157 Simple Network Management Protocol 97 Beginning in Section 3.2.6.3.2 atTable Object Type Names thru the rest 98 of Section 3 there are numerous references to the use of IPv4 addresses 99 as part of OIDs. 101 Section 4. Protocol Specification specifies the format of an SNMP 102 packet which uses the overall format of: 104 RFC1157-SNMP DEFINITIONS ::= BEGIN 105 IMPORTS 106 ObjectName, ObjectSyntax, NetworkAddress, IpAddress, TimeTicks 107 FROM RFC1155-SMI; 109 Section 4.1.3.1. Example of Table Traversal has many uses of IPv4 110 addresses in its example of table transversal. 112 Section 5. Definitions reiterates the use of IPv4 addresses. 114 RFC1157-SNMP DEFINITIONS ::= BEGIN 116 IMPORTS 117 ObjectName, ObjectSyntax, NetworkAddress, IpAddress, TimeTicks 118 FROM RFC1155-SMI; 120 3.2 RFC 1155 Structure of Management Information 122 Section 3.2.3.2. IpAddress defines the following: 124 This application-wide type represents a 32-bit internet address. It 125 is represented as an OCTET STRING of length 4, in network byte-order. 127 There are several instances of the use of this definition in the rest of 128 the document. 130 3.3 RFC 1213 Management Information Base 132 There are far too many instances of IPv4 addresses is this document 133 to enumerate here. Clearly the entire IP OID sub tree is rife with 134 IPv4 dependencies. A new sub tree needs to be defined to deal with 135 IPv6 addresses leaving the current sub tree intact for IPv4 address 136 information. 138 3.4 RFC 1643 Definitions of Managed Objects for the Ethernet-like 139 Interface Types 141 There are no IPv4 dependencies in this specification. 143 3.5 RFC 2578 Structure of Management Information Version 2 (SMIv2) 145 Section 7.1.5. IpAddress defines: 147 The IpAddress type represents a 32-bit internet address. It is 148 represented as an OCTET STRING of length 4, in network byte-order. 150 Note that the IpAddress type is a tagged type for historical reasons. 151 Network addresses should be represented using an invocation of the 152 TEXTUAL-CONVENTION macro. 154 Note the deprecated status of this type; see RFC 3291 for details on 155 TEXTUAL-CONVENTION macro. 157 3.6 RFC 2579 Textual Conventions for SMIv2 159 There are no IPv4 dependencies in this specification. 161 3.7 RFC 2819 Remote Network Monitoring Management Information Base 162 (RMON-MIB) 164 There are no IPv4 dependencies in this specification. 166 3.8 RFC 3416 Protocol Operations for Version 2 of the Simple Network 167 Management Protocol (SNMPv2) (OPS-MIB) 169 Section 4.2.2.1. Example of Table Traversal and Section 4.2.3.1. 170 Another Example of Table Traversal both use OID's from MIB2 whose 171 data contains IPv4 addresses. Other than their use in these example 172 sections there are no IPv4 dependencies in this specification. 174 3.9 RFC 3417 Transport Mappings for Version 2 of the Simple Network 175 Management Protocol (SNMPv2) (TRANS-MIB) 177 Section 2 Definitions contains the following OID definition: 179 SnmpUDPAddress ::= TEXTUAL-CONVENTION 180 DISPLAY-HINT "1d.1d.1d.1d/2d" 181 STATUS current 182 DESCRIPTION 183 "Represents a UDP address: 185 octets contents encoding 186 1-4 IP-address network-byte order 187 5-6 UDP-port network-byte order 188 " 189 SYNTAX OCTET STRING (SIZE (6)) 191 Section 8.1. Usage Example also contains examples which use IPv4 192 address, but it has no significance in the operation of the 193 specification. 195 3.10 RFC 3418 Management Information Base for Version 2 of the Simple 196 Network Management Protocol (SNMPv2) (SNMPv2-MIB) 198 There are no IPv4 dependencies in this specification. 200 4.0 Draft Standards 202 Draft Standards represent the penultimate standard level in the IETF. 203 A protocol can only achieve draft standard when there are multiple, 204 independent, interoperable implementations. Draft Standards are usually 205 quite mature and widely used. 207 4.01 RFC 1493 Definitions of Managed Objects for Bridges (BRIDGE-MIB) 209 There are no IPv4 dependencies in this specification. 211 4.02 RFC 1559 DECnet Phase IV MIB Extensions (DECNET-MIB) 213 There are no IPv4 dependencies in this specification. 215 4.03 RFC 1657 Definitions of Managed Objects for the Fourth 216 Version of the Border Gateway Protocol (BGP-4) using SMIv2 (BGP-4-MIB) 218 The MIB defined in this RFC deals with objects in a BGP4 based routing 219 system and therefore contain many objects that are limited by the 220 IpAddress 32-bit value defined in MIB2. Clearly the values of this MIB 221 are limited to IPv4 addresses. No update is needed, although a new MIB 222 should be defined for BGP++ to allow management of IPv6 addresses and 223 routes. 225 4.04 RFC 1658 Definitions of Managed Objects for Character Stream 226 Devices using SMIv2 228 There are no IPv4 dependencies in this specification. 230 4.05 RFC 1659 Definitions of Managed Objects for RS-232-like Hardware 231 Devices using SMIv2 233 There are no IPv4 dependencies in this protocol. 235 4.06 RFC 1660 Definitions of Managed Objects for Parallel-printer-like 236 Hardware Devices using SMIv2 238 There are no IPv4 dependencies in this protocol. 240 4.07 RFC 1694 Definitions of Managed Objects for SMDS Interfaces using 241 SMIv2 (SIP-MIB) 243 This MIB definition defines the following subtree: 245 ipOverSMDS OBJECT IDENTIFIER ::= { smdsApplications 1 } 247 -- Although the objects in this group are read-only, at the 248 -- agent's discretion they may be made read-write so that the 249 -- management station, when appropriately authorized, may 250 -- change the addressing information related to the 251 -- configuration of a logical IP subnetwork implemented on 252 -- top of SMDS. 254 -- This table is necessary to support RFC1209 (IP-over-SMDS) 255 -- and gives information on the Group Addresses and ARP 256 -- Addresses used in the Logical IP subnetwork. 257 -- One SMDS address may be associated with multiple IP 258 -- addresses. One SNI may be associated with multiple LISs. 260 ipOverSMDSTable OBJECT-TYPE 261 SYNTAX SEQUENCE OF IpOverSMDSEntry 262 MAX-ACCESS not-accessible 263 STATUS current 264 DESCRIPTION 265 "The table of addressing information relevant to 266 this entity's IP addresses." 267 ::= { ipOverSMDS 1 } 269 ipOverSMDSEntry OBJECT-TYPE 270 SYNTAX IpOverSMDSEntry 271 MAX-ACCESS not-accessible 272 STATUS current 273 DESCRIPTION 274 "The addressing information for one of this 275 entity's IP addresses." 276 INDEX { ipOverSMDSIndex, ipOverSMDSAddress } 277 ::= { ipOverSMDSTable 1 } 279 IpOverSMDSEntry ::= 280 SEQUENCE { 281 ipOverSMDSIndex IfIndex, 282 ipOverSMDSAddress IpAddress, 283 ipOverSMDSHA SMDSAddress, 284 ipOverSMDSLISGA SMDSAddress, 285 ipOverSMDSARPReq SMDSAddress 286 } 288 ipOverSMDSIndex OBJECT-TYPE 289 SYNTAX IfIndex 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "The value of this object identifies the 294 interface for which this entry contains management 295 information. " 296 ::= { ipOverSMDSEntry 1 } 298 ipOverSMDSAddress OBJECT-TYPE 299 SYNTAX IpAddress 300 MAX-ACCESS read-only 301 STATUS current 302 DESCRIPTION 303 "The IP address to which this entry's addressing 304 information pertains." 305 ::= { ipOverSMDSEntry 2 } 307 ipOverSMDSHA OBJECT-TYPE 308 SYNTAX SMDSAddress 309 MAX-ACCESS read-only 310 STATUS current 311 DESCRIPTION 312 "The SMDS Individual address of the IP station." 313 ::= { ipOverSMDSEntry 3 } 315 ipOverSMDSLISGA OBJECT-TYPE 316 SYNTAX SMDSAddress 317 MAX-ACCESS read-only 318 STATUS current 319 DESCRIPTION 320 "The SMDS Group Address that has been configured 321 to identify the SMDS Subscriber-Network Interfaces 322 (SNIs) of all members of the Logical IP Subnetwork 323 (LIS) connected to the network supporting SMDS." 324 ::= { ipOverSMDSEntry 4 } 326 ipOverSMDSARPReq OBJECT-TYPE 327 SYNTAX SMDSAddress 328 MAX-ACCESS read-only 329 STATUS current 330 DESCRIPTION 331 "The SMDS address (individual or group) to which 332 ARP Requests are to be sent." 333 ::= { ipOverSMDSEntry 5 } 335 Although these OIDs are intended for IPv4 addresses, a similar MIB 336 can be defined for IPv6 addressing. 338 4.08 RFC 1724 RIP Version 2 MIB Extension (RIP2-MIB) 340 As might be expected, this RFC is filled with IPv4 dependencies since 341 it defines a MIB for an IPv4 only routing protocol. A new MIB for RIPng 342 is required. 344 4.09 RFC 1748 IEEE 802.5 MIB using SMIv2 (802.5-MIB) 346 There are no IPv4 dependencies in this specification. 348 4.10 RFC 1850 OSPF Version 2 Management Information Base (OSPF-MIB) 350 This MIB defines managed objects for OSPFv2 which is a protocol used 351 to exchange IPv4 routing information. Since OSPFv2 is limited to IPv4 352 addresses a new MIB is required to support a new version of OSPF that 353 is IPv6 aware. 355 4.11 RFC 2115 Management Information Base for Frame Relay DTEs 356 Using SMIv2 (FRAME-MIB) 358 This MIB has several examples of mapping IPv4 addresses to multiple 359 Frame Relay DLCI's and monitoring their connections. A new set of OID's 360 needs to be defined to allow this functionality for IPv6. 362 4.12 RFC 2571 An Architecture for Describing SNMP Management Frameworks 363 (ARCH-SNMP) 365 There are no IPv4 dependencies in this specification. 367 4.13 RFC 2572 Message Processing and Dispatching for the Simple Network 368 Management Protocol (SNMP) (MPD-SNMP) 370 There are no IPv4 dependencies in this specification. 372 4.14 RFC 2573 SNMP Applications (SNMP-APP) 374 There are no IPv4 dependencies in this protocol. 376 4.15 RFC 2574 User-based Security Model (USM) for version 3 of the 377 Simple Network Management Protocol (SNMPv3) (USM-SNMPV3) 379 There are no IPv4 dependencies in this protocol. 381 4.16 RFC 2575 View-based Access Control Model (VACM) for the Simple 382 Network Management Protocol (SNMP) (VACM-SNMP) 384 There are no IPv4 dependencies in this protocol. 386 4.17 RFC 2790 Host Resources MIB 388 There are no IPv4 dependencies in this specification. 390 4.18 RFC 2863 The Interfaces Group MIB (INTERGRMIB) 392 There are no IPv4 dependencies in this specification. There is some 393 discussion in one OID about an interface performing a self test, but it 394 is IP version independent. 396 5.0 Proposed Standards 398 Proposed Standards are introductory level documents. There are no 399 requirements for even a single implementation. In many cases Proposed 400 are never implemented or advanced in the IETF standards process. They 401 therefore are often just proposed ideas that are presented to the 402 Internet community. Sometimes flaws are exposed or they are one of 403 many competing solutions to problems. In these later cases, no 404 discussion is presented as it would not serve the purpose of this 405 discussion. 407 5.001 RFC 1239 Reassignment of experimental MIBs to standard MIBs 408 (STD-MIBs) 410 There are no IPv4 dependencies in this specification. 412 5.002 RFC 1269 Definitions of Managed Objects for the Border Gateway 413 Protocol: Version 3 (BGP-MIB) 415 The use of BGP3 has been deprecated and is not discussed. 417 5.003 RFC 1285 FDDI Management Information Base (FDDI-MIB) 419 There are no IPv4 dependencies in this specification. 421 5.004 RFC 1381 SNMP MIB Extension for X.25 LAPB (SNMP-LAPB) 423 There are no IPv4 dependencies in this specification. 425 5.005 RFC 1382 SNMP MIB Extension for the X.25 Packet Layer (SNMP-X.25) 427 There are no IPv4 dependencies in this specification. 429 5.006 RFC 1414 Identification MIB (IDENT-MIB) 431 There are no IPv4 dependencies in this specification. 433 5.007 RFC 1418 SNMP over OSI (SNMP-OSI) 435 There are no IPv4 dependencies in this protocol. 437 5.008 RFC 1419 SNMP over AppleTalk (SNMP-AT) 439 There are no IPv4 dependencies in this protocol. 441 5.009 RFC 1420 SNMP over IPX (SNMP-IPX) 443 There are no IPv4 dependencies in this protocol. 445 5.010 RFC 1441 Introduction to version 2 of the Internet-standard 446 Network Management Framework (SNMPv2) 448 There are no IPv4 dependencies in this protocol. 450 5.011 RFC 1461 SNMP MIB extension for Multiprotocol Interconnect 451 over X.25 (X25-MIB) 453 The following OIDs are defined in Section 4 "Definitions": 455 mioxPleLastFailedEnAddr OBJECT-TYPE 456 SYNTAX OCTET STRING (SIZE(2..128)) 457 ACCESS read-only 458 STATUS mandatory 459 DESCRIPTION 460 "The last Encapsulated address that failed 461 to find a corresponding X.121 address and 462 caused mioxPleEnAddrToX121LkupFlrs to be 463 incremented. The first octet of this object 464 contains the encapsulation type, the 465 remaining octets contain the address of that 466 type that failed. Thus for an IP address, 467 the length will be five octets, the first 468 octet will contain 204 (hex CC), and the 469 last four octets will contain the IP 470 address. For a snap encapsulation, the 471 first byte would be 128 (hex 80) and the 472 rest of the octet string would have the snap 473 header." 474 ::= { mioxPleEntry 4 } 476 mioxPeerEnAddr OBJECT-TYPE 477 SYNTAX OCTET STRING (SIZE (0..128)) 478 ACCESS read-write 479 STATUS mandatory 480 DESCRIPTION 481 "The Encapsulation address of the remote 482 host mapped by this table entry. A length 483 of zero indicates the remote IP address is 484 unknown or unspecified for use as a PLE 485 default. 487 The first octet of this object contains the 488 encapsulation type, the remaining octets 489 contain an address of that type. Thus for 490 an IP address, the length will be five 491 octets, the first octet will contain 204 492 (hex CC), and the last four octets will 493 contain the IP address. For a snap 494 encapsulation, the first byte would be 128 495 (hex 80) and the rest of the octet string 496 would have the snap header." 497 DEFVAL { ''h } 498 ::= { mioxPeerEntry 7 } 500 mioxPeerEncType OBJECT-TYPE 501 SYNTAX INTEGER (0..256) 502 ACCESS read-write 503 STATUS mandatory 504 DESCRIPTION 505 "The value of the encapsulation type. For 506 IP encapsulation this will have a value of 507 204 (hex CC). For SNAP encapsulated 508 packets, this will have a value of 128 (hex 509 80). For CLNP, ISO 8473, this will have a 510 value of 129 (hex 81). For ES-ES, ISO 9542, 511 this will have a value of 130 (hex 82). A 512 value of 197 (hex C5) identifies the Blacker 513 X.25 encapsulation. A value of 0, 514 identifies the Null encapsulation. 516 This value can only be written when the 517 mioxPeerStatus object with the same 518 mioxPeerIndex has a value of underCreation. 519 Setting this object to a value of 256 520 deletes the entry. When deleting an entry, 521 all other entries in the mioxPeerEncTable 522 with the same mioxPeerIndex and with an 523 mioxPeerEncIndex higher then the deleted 524 entry, will all have their mioxPeerEncIndex 525 values decremented by one." 526 ::= { mioxPeerEncEntry 2 } 528 Updated values of the first byte of these OID's can be defined to 529 support IPv6 addresses. 531 5.012 RFC 1471 The Definitions of Managed Objects for the Link 532 Control Protocol of the Point-to-Point Protocol (PPP/LCPMIB) 534 There are no IPv4 dependencies in this specification. 536 5.013 RFC 1472 The Definitions of Managed Objects for the Security 537 Protocols of the Point-to-Point Protocol (PPP/SECMIB) 539 There are no IPv4 dependencies in this specification. 541 5.014 RFC 1473 The Definitions of Managed Objects for the IP Network 542 Control Protocol of the Point-to-Point Protocol (PPP/IPMIB) 544 Every OID in the MIB contain IPv4 addresses. A new MIB must be defined 545 for OIDs for similar IPv6 addresses. 547 5.015 RFC 1474 The Definitions of Managed Objects for the Bridge 548 Network Control Protocol of the Point-to-Point Protocol 549 (PPP/Bridge) 551 There are no IPv4 dependencies in this specification. 553 5.016 RFC 1512 FDDI Management Information Base (FDDI-MIB) 555 There are no IPv4 dependencies in this specification. 557 5.017 RFC 1513 Token Ring Extensions to the Remote Network 558 Monitoring MIB 560 There are no IPv4 dependencies in this specification. 562 5.018 RFC 1515 Definitions of Managed Objects for IEEE 802.3 563 Medium Attachment Units (MAUs) 565 There are no IPv4 dependencies in this protocol. 567 5.019 RFC 1525 Definitions of Managed Objects for Source Routing 568 Bridges (SRB-MIB) 570 There are no IPv4 dependencies in this specification. 572 5.020 RFC 1611 DNS Server MIB Extensions (DNS-S-MIB) 574 The following OID is defined: 576 DnsServZoneEntry ::= 577 SEQUENCE { 578 dnsServZoneName 579 DnsNameAsIndex, 580 dnsServZoneClass 581 DnsClass, 582 dnsServZoneLastReloadSuccess 583 DnsTime, 584 dnsServZoneLastReloadAttempt 585 DnsTime, 586 dnsServZoneLastSourceAttempt 587 IpAddress, 588 dnsServZoneStatus 589 RowStatus, 590 dnsServZoneSerial 591 Counter32, 592 dnsServZoneCurrent 593 TruthValue, 594 dnsServZoneLastSourceSuccess 595 IpAddress 596 } 598 There are two instances of IPv4 assumptions. New OIDs can be 599 defined for IPv6 addressing. 601 Similarly: 603 -- DNS Zone Source Table 605 dnsServZoneSrcTable OBJECT-TYPE 606 SYNTAX SEQUENCE OF DnsServZoneSrcEntry 607 MAX-ACCESS not-accessible 608 STATUS current 609 DESCRIPTION 610 "This table is a list of IP addresses from which the 611 server will attempt to load zone information using DNS 612 zone transfer operations. A reload may occur due to SNMP 613 operations that create a row in dnsServZoneTable or a 614 SET to object dnsServZoneReload. This table is only 615 used when the zone is loaded via zone transfer." 616 ::= { dnsServZone 2 } 618 dnsServZoneSrcEntry OBJECT-TYPE 619 SYNTAX DnsServZoneSrcEntry 620 MAX-ACCESS not-accessible 621 STATUS current 622 DESCRIPTION 623 "An entry in the name server zone source table." 624 INDEX { dnsServZoneSrcName, 625 dnsServZoneSrcClass, 626 dnsServZoneSrcAddr } 627 ::= { dnsServZoneSrcTable 1 } 629 DnsServZoneSrcEntry ::= 630 SEQUENCE { 631 dnsServZoneSrcName 632 DnsNameAsIndex, 633 dnsServZoneSrcClass 634 DnsClass, 635 dnsServZoneSrcAddr 636 IpAddress, 637 dnsServZoneSrcStatus 638 RowStatus 639 } 641 dnsServZoneSrcName OBJECT-TYPE 642 SYNTAX DnsNameAsIndex 643 MAX-ACCESS not-accessible 644 STATUS current 645 DESCRIPTION 646 "DNS name of the zone to which this entry applies." 647 ::= { dnsServZoneSrcEntry 1 } 649 dnsServZoneSrcClass OBJECT-TYPE 650 SYNTAX DnsClass 651 MAX-ACCESS not-accessible 652 STATUS current 653 DESCRIPTION 654 "DNS class of zone to which this entry applies." 655 ::= { dnsServZoneSrcEntry 2 } 657 dnsServZoneSrcAddr OBJECT-TYPE 658 SYNTAX IpAddress 659 MAX-ACCESS not-accessible 660 STATUS current 661 DESCRIPTION 662 "IP address of name server host from which this zone 663 might be obtainable." 664 ::= { dnsServZoneSrcEntry 3 } 666 5.021 RFC 1612 DNS Resolver MIB Extensions (DNS-R-MIB) 668 As in the previous section the following IPv4 dependent OIDs are 669 defined: 671 DnsResConfigSbeltEntry ::= 672 SEQUENCE { 673 dnsResConfigSbeltAddr 674 IpAddress, 675 dnsResConfigSbeltName 676 DnsName, 677 dnsResConfigSbeltRecursion 678 INTEGER, 679 dnsResConfigSbeltPref 680 INTEGER, 681 dnsResConfigSbeltSubTree 682 DnsNameAsIndex, 683 dnsResConfigSbeltClass 684 DnsClass, 685 dnsResConfigSbeltStatus 686 RowStatus 687 } 689 dnsResConfigSbeltAddr OBJECT-TYPE 690 SYNTAX IpAddress 691 MAX-ACCESS not-accessible 692 STATUS current 693 DESCRIPTION 694 "The IP address of the Sbelt name server identified by 695 this row of the table." 696 ::= { dnsResConfigSbeltEntry 1 } 698 and 700 DnsResLameDelegationEntry ::= 701 SEQUENCE { 702 dnsResLameDelegationSource 703 IpAddress, 704 dnsResLameDelegationName 705 DnsNameAsIndex, 706 dnsResLameDelegationClass 707 DnsClass, 708 dnsResLameDelegationCounts 709 Counter32, 710 dnsResLameDelegationStatus 711 RowStatus 712 } 714 dnsResLameDelegationSource OBJECT-TYPE 715 SYNTAX IpAddress 716 MAX-ACCESS not-accessible 717 STATUS current 718 DESCRIPTION 719 "Source of lame delegation." 720 ::= { dnsResLameDelegationEntry 1 } 722 and 724 DnsResCacheRREntry ::= 725 SEQUENCE { 726 dnsResCacheRRName 727 DnsNameAsIndex, 728 dnsResCacheRRClass 729 DnsClass, 730 dnsResCacheRRType 731 DnsType, 732 dnsResCacheRRTTL 733 DnsTime, 734 dnsResCacheRRElapsedTTL 735 DnsTime, 736 dnsResCacheRRSource 737 IpAddress, 738 dnsResCacheRRData 739 OCTET STRING, 740 dnsResCacheRRStatus 741 RowStatus, 742 dnsResCacheRRIndex 743 Integer32, 744 dnsResCacheRRPrettyName 745 DnsName 746 } 748 dnsResCacheRRSource OBJECT-TYPE 749 SYNTAX IpAddress 750 MAX-ACCESS read-only 751 STATUS current 752 DESCRIPTION 753 "Host from which RR was received, 0.0.0.0 if unknown." 754 ::= { dnsResCacheRREntry 6 } 756 and 758 DnsResNCacheErrEntry ::= 759 SEQUENCE { 760 dnsResNCacheErrQName 761 DnsNameAsIndex, 762 dnsResNCacheErrQClass 763 DnsQClass, 764 dnsResNCacheErrQType 765 DnsQType, 766 dnsResNCacheErrTTL 767 DnsTime, 768 dnsResNCacheErrElapsedTTL 769 DnsTime, 770 dnsResNCacheErrSource 771 IpAddress, 772 dnsResNCacheErrCode 773 INTEGER, 774 dnsResNCacheErrStatus 775 RowStatus, 776 dnsResNCacheErrIndex 777 Integer32, 778 dnsResNCacheErrPrettyName 779 DnsName 780 } 782 dnsResNCacheErrSource OBJECT-TYPE 783 SYNTAX IpAddress 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "Host which sent the authoritative error, 0.0.0.0 if 788 unknown." 789 ::= { dnsResNCacheErrEntry 6 } 791 5.022 RFC 1628 UPS Management Information Base (UPS-MIB) 793 There are no IPv4 dependencies in this specification. 795 5.023 RFC 1666 Definitions of Managed Objects for SNA NAUs 796 using SMIv2 SNANAU-MIB 798 There are no IPv4 dependencies in this specification. 800 5.024 RFC 1696 Modem Management Information Base (MIB) using SMIv2 801 MODEM-MIB 803 There are no IPv4 dependencies in this specification. 805 5.025 RFC 1697 Relational Database Management System (RDBMS) 806 Management Information Base (MIB) using SMIv2 RDBMS-MIB 808 There are no IPv4 dependencies in this specification. 810 5.026 RFC 1742 AppleTalk Management Information Base II (AT-MIB) 812 The following OIDs are defined: 814 KipEntry ::= SEQUENCE { 815 kipNetStart ATNetworkNumber, 816 kipNetEnd ATNetworkNumber, 817 kipNextHop IpAddress, 818 kipHopCount INTEGER, 819 kipBCastAddr IpAddress, 820 kipCore INTEGER, 821 kipType INTEGER, 822 kipState INTEGER, 823 kipShare INTEGER, 824 kipFrom IpAddress 825 } 827 kipNextHop OBJECT-TYPE 828 SYNTAX IpAddress 829 ACCESS read-write 830 STATUS mandatory 831 DESCRIPTION 832 "The IP address of the next hop in the route to this 833 entry's destination network." 834 ::= { kipEntry 3 } 836 kipBCastAddr OBJECT-TYPE 837 SYNTAX IpAddress 838 ACCESS read-write 839 STATUS mandatory 840 DESCRIPTION 841 "The form of the IP address used to broadcast on this 842 network." 843 ::= { kipEntry 5 } 845 kipFrom OBJECT-TYPE 846 SYNTAX IpAddress 847 ACCESS read-only 848 STATUS mandatory 849 DESCRIPTION 850 "The IP address from which the routing entry was 851 learned via the AA protocol. If this entry was not 852 created via the AA protocol, it should contain IP 853 address 0.0.0.0." 854 ::= { kipEntry 10 } 856 5.027 RFC 1747 Definitions of Managed Objects for SNA Data Link 857 Control (SDLC) using SMIv2 SDLCSMIv2 859 There are no IPv4 dependencies in this protocol. 861 5.028 RFC 1749 IEEE 802.5 Station Source Routing MIB using SMIv2 862 802.5-SSR 864 There are no IPv4 dependencies in this specification. 866 5.029 RFC 1759 Printer MIB (Print-MIB) 868 There are no IPv4 dependencies in this specification. 870 5.030 RFC 2006 The Definitions of Managed Objects for IP Mobility 871 Support using SMIv2 (MOBILEIPMI) 873 This document defines a MIB for the Mobile IPv4 documents described 874 immediately above. Without enumeration, let it be stated that a new 875 MIB for IPv6 Mobility is required. 877 5.031 RFC 2011 SNMPv2 Management Information Base for the Internet 878 Protocol using SMIv2 (MIB-IP) 880 Approximately 1/3 of the OIDs defined in this document are clearly 881 IPv4 dependent. A new MIB for IPv6 OIDs is required. 883 5.032 RFC 2012 SNMPv2 Management Information Base for the 884 Transmission Control Protocol using SMIv2 (MIB-TCP) 886 A number of OIDs in this MIB assumes IPv4 addresses, as is noted in 887 the note reproduced below: 889 IESG Note: 891 The IP, UDP, and TCP MIB modules currently support only IPv4. These 892 three modules use the IpAddress type defined as an OCTET STRING of 893 length 4 to represent the IPv4 32-bit internet addresses. (See RFC 894 1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6 895 internet addresses. 897 5.033 RFC 2013 SNMPv2 Management Information Base for the User 898 Datagram Protocol using SMIv2 (MIB-UDP) 900 A number of OIDs in this MIB assumes IPv4 addresses, as is noted in 901 the note reproduced below: 903 IESG Note: 905 The IP, UDP, and TCP MIB modules currently support only IPv4. These 906 three modules use the IpAddress type defined as an OCTET STRING of 907 length 4 to represent the IPv4 32-bit internet addresses. (See RFC 908 1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6 909 internet addresses. 911 5.034 RFC 2020 IEEE 802.12 Interface MIB (802.12-MIB) 913 There are no IPv4 dependencies in this specification. 915 5.035 RFC 2021 Remote Network Monitoring Management Information Base 916 Version 2 using SMIv2 (RMON-MIB) 918 The following OIDs are defined: 920 addressMapNetworkAddress OBJECT-TYPE 921 SYNTAX OCTET STRING 922 MAX-ACCESS not-accessible 923 STATUS current 924 DESCRIPTION 925 "The network address for this relation. 927 This is represented as an octet string with 928 specific semantics and length as identified 929 by the protocolDirLocalIndex component of the 930 index. 932 For example, if the protocolDirLocalIndex indicates an 933 encapsulation of ip, this object is encoded as a length 934 octet of 4, followed by the 4 octets of the ip address, 935 in network byte order." 936 ::= { addressMapEntry 2 } 938 nlHostAddress OBJECT-TYPE 939 SYNTAX OCTET STRING 940 MAX-ACCESS not-accessible 941 STATUS current 942 DESCRIPTION 943 "The network address for this nlHostEntry. 945 This is represented as an octet string with 946 specific semantics and length as identified 947 by the protocolDirLocalIndex component of the index. 949 For example, if the protocolDirLocalIndex indicates an 950 encapsulation of ip, this object is encoded as a length 951 octet of 4, followed by the 4 octets of the ip address, 952 in network byte order." 953 ::= { nlHostEntry 2 } 955 nlMatrixSDSourceAddress OBJECT-TYPE 956 SYNTAX OCTET STRING 957 MAX-ACCESS not-accessible 958 STATUS current 959 DESCRIPTION 960 "The network source address for this nlMatrixSDEntry. 962 This is represented as an octet string with 963 specific semantics and length as identified 964 by the protocolDirLocalIndex component of the index. 966 For example, if the protocolDirLocalIndex indicates an 967 encapsulation of ip, this object is encoded as a length 968 octet of 4, followed by the 4 octets of the ip address, 969 in network byte order." 970 ::= { nlMatrixSDEntry 2 } 972 nlMatrixSDDestAddress OBJECT-TYPE 973 SYNTAX OCTET STRING 974 MAX-ACCESS not-accessible 975 STATUS current 976 DESCRIPTION 977 "The network destination address for this 978 nlMatrixSDEntry. 980 This is represented as an octet string with 981 specific semantics and length as identified 982 by the protocolDirLocalIndex component of the index. 984 For example, if the protocolDirLocalIndex indicates an 985 encapsulation of ip, this object is encoded as a length 986 octet of 4, followed by the 4 octets of the ip address, 987 in network byte order." 988 ::= { nlMatrixSDEntry 3 } 990 nlMatrixDSSourceAddress OBJECT-TYPE 991 SYNTAX OCTET STRING 992 MAX-ACCESS not-accessible 993 STATUS current 994 DESCRIPTION 995 "The network source address for this nlMatrixDSEntry. 997 This is represented as an octet string with 998 specific semantics and length as identified 999 by the protocolDirLocalIndex component of the index. 1001 For example, if the protocolDirLocalIndex indicates an 1002 encapsulation of ip, this object is encoded as a length 1003 octet of 4, followed by the 4 octets of the ip address, 1004 in network byte order." 1005 ::= { nlMatrixDSEntry 2 } 1007 nlMatrixDSDestAddress OBJECT-TYPE 1008 SYNTAX OCTET STRING 1009 MAX-ACCESS not-accessible 1010 STATUS current 1011 DESCRIPTION 1012 "The network destination address for this 1013 nlMatrixDSEntry. 1015 This is represented as an octet string with 1016 specific semantics and length as identified 1017 by the protocolDirLocalIndex component of the index. 1019 For example, if the protocolDirLocalIndex indicates an 1020 encapsulation of ip, this object is encoded as a length 1021 octet of 4, followed by the 4 octets of the ip address, 1022 in network byte order." 1023 ::= { nlMatrixDSEntry 3 } 1025 nlMatrixTopNSourceAddress OBJECT-TYPE 1026 SYNTAX OCTET STRING 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "The network layer address of the source host in this 1031 conversation. 1033 This is represented as an octet string with 1034 specific semantics and length as identified 1035 by the associated nlMatrixTopNProtocolDirLocalIndex. 1037 For example, if the protocolDirLocalIndex indicates an 1038 encapsulation of ip, this object is encoded as a length 1039 octet of 4, followed by the 4 octets of the ip address, 1040 in network byte order." 1041 ::= { nlMatrixTopNEntry 3 } 1043 nlMatrixTopNDestAddress OBJECT-TYPE 1044 SYNTAX OCTET STRING 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION 1048 "The network layer address of the destination host in this 1049 conversation. 1051 This is represented as an octet string with 1052 specific semantics and length as identified 1053 by the associated nlMatrixTopNProtocolDirLocalIndex. 1055 For example, if the nlMatrixTopNProtocolDirLocalIndex 1056 indicates an encapsulation of ip, this object is encoded as a 1057 length octet of 4, followed by the 4 octets of the ip address, 1058 in network byte order." 1059 ::= { nlMatrixTopNEntry 4 } 1061 alMatrixTopNSourceAddress OBJECT-TYPE 1062 SYNTAX OCTET STRING 1063 MAX-ACCESS read-only 1064 STATUS current 1065 DESCRIPTION 1066 "The network layer address of the source host in this 1067 conversation. 1068 This is represented as an octet string with 1069 specific semantics and length as identified 1070 by the associated alMatrixTopNProtocolDirLocalIndex. 1072 For example, if the alMatrixTopNProtocolDirLocalIndex 1073 indicates an encapsulation of ip, this object is encoded as a 1074 length octet of 4, followed by the 4 octets of the ip address, 1075 in network byte order." 1076 ::= { alMatrixTopNEntry 3 } 1078 alMatrixTopNDestAddress OBJECT-TYPE 1079 SYNTAX OCTET STRING 1080 MAX-ACCESS read-only 1081 STATUS current 1082 DESCRIPTION 1083 "The network layer address of the destination host in this 1084 conversation. 1086 This is represented as an octet string with 1087 specific semantics and length as identified 1088 by the associated alMatrixTopNProtocolDirLocalIndex. 1090 For example, if the alMatrixTopNProtocolDirLocalIndex 1091 indicates an encapsulation of ip, this object is encoded as a 1092 length octet of 4, followed by the 4 octets of the ip address, 1093 in network byte order." 1094 ::= { alMatrixTopNEntry 4 } 1096 trapDestProtocol OBJECT-TYPE 1097 SYNTAX INTEGER { 1098 ip(1), 1099 ipx(2) 1100 } 1101 MAX-ACCESS read-create 1102 STATUS current 1103 DESCRIPTION 1104 "The protocol with which to send this trap." 1105 ::= { trapDestEntry 3 } 1107 trapDestAddress OBJECT-TYPE 1108 SYNTAX OCTET STRING 1109 MAX-ACCESS read-create 1110 STATUS current 1111 DESCRIPTION 1112 "The address to send traps on behalf of this entry. 1114 If the associated trapDestProtocol object is equal to ip(1), 1115 the encoding of this object is the same as the snmpUDPAddress 1116 textual convention in [RFC1906]: 1117 -- for a SnmpUDPAddress of length 6: 1118 -- 1119 -- octets contents encoding 1120 -- 1-4 IP-address network-byte order 1121 -- 5-6 UDP-port network-byte order 1123 If the associated trapDestProtocol object is equal to ipx(2), 1124 the encoding of this object is the same as the snmpIPXAddress 1125 textual convention in [RFC1906]: 1126 -- for a SnmpIPXAddress of length 12: 1127 -- 1128 -- octets contents encoding 1129 -- 1-4 network-number network-byte order 1130 -- 5-10 physical-address network-byte order 1131 -- 11-12 socket-number network-byte order 1133 This object may not be modified if the associated 1134 trapDestStatus object is equal to active(1)." 1135 ::= { trapDestEntry 4 } 1137 All of the OIDs above (except trapDestProtocol) imply IPv4 addresses 1138 but since they use a SYNTAX of OCTET STRING, they should work fine 1139 for IPv6 addresses. A new legitimate value of trapDestProtocol (i.e. 1140 SYNTAX addition of ipv6(3) should make this specification IPv6 1141 functional. 1143 5.036 RFC 2024 Definitions of Managed Objects for Data Link Switching 1144 using SMIv2 (DLSW-MIB) 1146 The following OIDs are defined: 1148 TAddress ::= TEXTUAL-CONVENTION 1149 STATUS current 1150 DESCRIPTION 1151 "Denotes a transport service address. 1152 For dlswTCPDomain, a TAddress is 4 octets long, 1153 containing the IP-address in network-byte order." 1154 SYNTAX OCTET STRING (SIZE (0..255)) 1156 -- DLSw over TCP 1157 dlswTCPDomain OBJECT IDENTIFIER ::= { dlswDomains 1 } 1158 -- for an IP address of length 4: 1159 -- 1160 -- octets contents encoding 1161 -- 1-4 IP-address network-byte order 1162 -- 1163 DlswTCPAddress ::= TEXTUAL-CONVENTION 1164 DISPLAY-HINT "1d.1d.1d.1d" 1165 STATUS current 1166 DESCRIPTION 1167 "Represents the IP address of a DLSw which uses 1168 TCP as a transport protocol." 1169 SYNTAX OCTET STRING (SIZE (4)) 1171 Additionally there are many OIDs that use a SYNTAX of TAddress within 1172 the document. Interestingly the SYNTAX for TAddress is an OCTET 1173 string of up to 256 characters. It could easily accommodate a similar 1174 hybrid format for IPv6 addresses. 1176 A new OID to enhance functionality for DlswTCPAddress can be added 1177 to support IPv6 addresses. 1179 5.037 RFC 2051 Definitions of Managed Objects for APPC using SMIv2 1180 (SNANAU-APP) 1182 There are no IPv4 dependencies in this protocol. 1184 5.038 RFC 2096 IP Forwarding Table MIB (TABLE-MIB) 1186 This MIB defines many OIDs that are IPv4 dependent. It is expected 1187 that another MIB for similar IPv6 addresses will be developed. 1189 5.039 RFC 2108 Definitions of Managed Objects for IEEE 802.3 Repeater 1190 Devices using SMIv2 802 (3-MIB) 1192 There are no IPv4 dependencies in this specification. 1194 5.040 RFC 2127 ISDN Management Information Base using SMIv2 1195 (ISDN-MIB) 1197 There are no IPv4 dependencies in this protocol. 1199 5.041 RFC 2128 Dial Control Management Information Base using 1200 SMIv2 (DC-MIB) 1202 There are no IPv4 dependencies in this specification. 1204 5.042 RFC 2206 RSVP Management Information Base using SMIv2 1205 (RSVP-MIB) 1207 All OIDs in this MIB have options for both IPv4 and IPv6. There 1208 are no IPv4 dependencies in this specification. 1210 5.043 RFC 2213 Integrated Services Management Information 1211 Base using SMIv2 1213 This MIB is IPv6 aware and therefore there are no IPv4 1214 dependencies in this specification. 1216 5.044 RFC 2214 Integrated Services Management Information 1217 Base Guaranteed Service Extensions using SMIv2 1219 There are no IPv4 dependencies in this protocol. 1221 5.045 RFC 2232 Definitions of Managed Objects for DLUR using 1222 SMIv2 (DLUR-MIB) 1224 There are no IPv4 dependencies in this specification. 1226 5.046 RFC 2238 Definitions of Managed Objects for HPR using 1227 SMIv2 (HPR-MIB) 1229 There are no IPv4 dependencies in this specification. 1231 5.047 RFC 2266 Definitions of Managed Objects for IEEE 802.12 1232 Repeater Devices 1234 There are no IPv4 dependencies in this protocol. 1236 5.048 RFC 2287 Definitions of System-Level Managed Objects for 1237 Applications (SLM-APP) 1239 There are no IPv4 dependencies in this protocol. 1241 5.049 RFC 2320 Definitions of Managed Objects for Classical IP 1242 and ARP Over ATM Using SMIv2 (IPOA-MIB) (IPOA-MIB) 1244 This MIB is wholly dependent of IPv4. A new MIB for IPv6 is 1245 required to provide the same functionality 1247 5.050 RFC 2417 Definitions of Managed Objects for Multicast 1248 over UNI 3.0/3.1 based ATM Networks 1250 There are many OIDs defined in this MIB which are IPv4 only. A 1251 similar MIB for IPv6 OIDs should be created. 1253 5.051 RFC 2452 IP Version 6 Management Information Base for the 1254 Transmission Control Protocol 1256 This RFC documents an IPv6 MIB and is not considered in this 1257 discussion. 1259 5.052 RFC 2454 IP Version 6 Management Information Base for 1260 the User Datagram Protocol 1262 This RFC documents an IPv6 MIB and is not considered in this 1263 discussion. 1265 5.053 RFC 2455 Definitions of Managed Objects for APPN 1266 (APPN-MIB) 1268 There are no IPv4 dependencies in this specification. 1270 5.054 RFC 2456 Definitions of Managed Objects for APPN TRAPS 1272 There are no IPv4 dependencies in this protocol. 1274 5.055 RFC 2457 Definitions of Managed Objects for Extended Border 1275 Node (EBN-MIB) 1277 There are no IPv4 dependencies in this specification. 1279 5.056 RFC 2465 Management Information Base for IP Version 6: 1280 Textual Conventions and General Group 1282 This RFC documents an IPv6 MIB and is not considered in this 1283 discussion. 1285 5.057 RFC 2466 Management Information Base for IP Version 6: 1286 ICMPv6 Group (ICMPv6-MIB) 1288 This RFC documents an IPv6 MIB and is not considered in this 1289 discussion. 1291 5.058 RFC 2493 Textual Conventions for MIB Modules Using 1292 Performance History Based on 15 Minute Intervals 1294 There are no IPv4 dependencies in this specification. 1296 5.059 RFC 2494 Definitions of Managed Objects for the DS0 1297 and DS0 Bundle Interface Type 1299 There are no IPv4 dependencies in this protocol. 1301 5.060 RFC 2495 Definitions of Managed Objects for the DS1 E1 1302 DS2 and E2 Interface Types 1304 There are no IPv4 dependencies in this protocol. 1306 5.061 RFC 2496 Definitions of Managed Object for the DS3/E3 1307 Interface Type (DS3-E3-MIB) 1309 There are no IPv4 dependencies in this specification. 1311 5.062 RFC 2512 Accounting Information for ATM Networks 1313 There are no IPv4 dependencies in this protocol. 1315 5.063 RFC 2513 Managed Objects for Controlling the Collection 1316 and Storage of Accounting Information for Connection- 1317 Oriented Networks 1319 There are no IPv4 dependencies in this protocol. 1321 5.064 RFC 2514 Definitions of Textual Conventions and 1322 OBJECT-IDENTITIES for ATM Management (ATM-TC-OID) 1324 There are no IPv4 dependencies in this protocol. 1326 5.065 RFC 2515 Definitions of Managed Objects for ATM 1327 Management (ATM-MIBMAN) 1329 This MIB defines the following OIDs: 1331 AtmInterfaceConfEntry ::= SEQUENCE { 1332 atmInterfaceMaxVpcs INTEGER, 1333 atmInterfaceMaxVccs INTEGER, 1334 atmInterfaceConfVpcs INTEGER, 1335 atmInterfaceConfVccs INTEGER, 1336 atmInterfaceMaxActiveVpiBits INTEGER, 1337 atmInterfaceMaxActiveVciBits INTEGER, 1338 atmInterfaceIlmiVpi AtmVpIdentifier, 1339 atmInterfaceIlmiVci AtmVcIdentifier, 1340 atmInterfaceAddressType INTEGER, 1341 atmInterfaceAdminAddress AtmAddr, 1342 atmInterfaceMyNeighborIpAddress IpAddress, 1343 atmInterfaceMyNeighborIfName DisplayString, 1344 atmInterfaceCurrentMaxVpiBits INTEGER, 1345 atmInterfaceCurrentMaxVciBits INTEGER, 1346 atmInterfaceSubscrAddress AtmAddr 1347 } 1349 atmInterfaceMyNeighborIpAddress OBJECT-TYPE 1350 SYNTAX IpAddress 1351 MAX-ACCESS read-write 1352 STATUS current 1353 DESCRIPTION 1354 "The IP address of the neighbor system connected to 1355 the far end of this interface, to which a Network 1356 Management Station can send SNMP messages, as IP 1357 datagrams sent to UDP port 161, in order to access 1358 network management information concerning the 1359 operation of that system. Note that the value 1360 of this object may be obtained in different ways, 1361 e.g., by manual configuration, or through ILMI 1362 interaction with the neighbor system." 1363 ::= { atmInterfaceConfEntry 11 } 1365 atmInterfaceConfGroup2 OBJECT-GROUP 1366 OBJECTS { 1367 atmInterfaceMaxVpcs, atmInterfaceMaxVccs, 1368 atmInterfaceConfVpcs, atmInterfaceConfVccs, 1369 atmInterfaceMaxActiveVpiBits, 1370 atmInterfaceMaxActiveVciBits, 1371 atmInterfaceIlmiVpi, 1372 atmInterfaceIlmiVci, 1373 atmInterfaceMyNeighborIpAddress, 1374 atmInterfaceMyNeighborIfName, 1375 atmInterfaceCurrentMaxVpiBits, 1376 atmInterfaceCurrentMaxVciBits, 1377 atmInterfaceSubscrAddress } 1378 STATUS current 1379 DESCRIPTION 1380 "A collection of objects providing configuration 1381 information about an ATM interface." 1382 ::= { atmMIBGroups 10 } 1384 Clearly a subsequent MIB must define equivalent IPv6 OIDs. 1386 5.066 RFC 2558 Definitions of Managed Objects for the SONET/SDH 1387 Interface Type 1389 There are no IPv4 dependencies in this protocol. 1391 5.067 RFC 2561 Base Definitions of Managed Objects for TN3270E 1392 Using SMIv2 1394 The document states: 1396 The MIB defined by this memo supports use of both IPv4 and IPv6 1397 addressing. 1399 This specification is both IPv4 and IPv6 aware. 1401 5.068 RFC 2562 Definitions of Protocol and Managed Objects for 1402 TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB) 1403 (TN2370E-RT) 1405 Several OIDs rely on imports from RFC 2561 and therefore the 1406 protocol is both IPv4 and IPv6 aware. 1408 5.069 RFC 2564 Application Management MIB (APP-MIB) 1410 The following OID is defined: 1412 ApplTAddress ::= TEXTUAL-CONVENTION 1413 STATUS current 1414 DESCRIPTION 1415 "Denotes a transport service address. 1417 For snmpUDPDomain, an ApplTAddress is 6 octets long, 1418 the initial 4 octets containing the IP-address in 1419 network-byte order and the last 2 containing the UDP 1420 port in network-byte order. Consult 'Transport Mappings 1421 for Version 2 of the Simple Network Management Protocol 1422 (SNMPv2)' for further information on snmpUDPDomain." 1423 SYNTAX OCTET STRING (SIZE (0..255)) 1425 A new OID should be defined to handle IPv6 addresses. 1427 5.070 RFC 2576 Coexistence between Version 1 Version 2 and Version 1428 3 of the Internet-standard Network Management Framework (SNMP) 1430 This document states: 1432 (11) For any object with a SYNTAX of NetworkAddress, the SYNTAX MUST 1433 be changed to IpAddress. Note that the use of NetworkAddress in 1434 new MIB documents is strongly discouraged (in fact, new MIB 1435 documents should be written using SMIv2, which does not define 1436 NetworkAddress). 1438 and defines the OID: 1440 snmpTrapAddress OBJECT-TYPE 1441 SYNTAX IpAddress 1442 MAX-ACCESS accessible-for-notify 1443 STATUS current 1444 DESCRIPTION 1445 "The value of the agent-addr field of a Trap PDU which 1446 is forwarded by a proxy forwarder application using 1447 an SNMP version other than SNMPv1. The value of this 1448 object SHOULD contain the value of the agent-addr field 1449 from the original Trap PDU as generated by an SNMPv1 1450 agent." 1451 ::= { snmpCommunityMIBObjects 3 } 1453 This clearly points out a lack of IPv6 awareness in this specification. 1455 5.071 RFC 2564 Application Management MIB (APP-MIB) 1457 The following OID is defined: 1459 ApplTAddress ::= TEXTUAL-CONVENTION 1460 STATUS current 1461 DESCRIPTION 1462 "Denotes a transport service address. 1464 For snmpUDPDomain, an ApplTAddress is 6 octets long, 1465 the initial 4 octets containing the IP-address in 1466 network-byte order and the last 2 containing the UDP 1467 port in network-byte order. Consult 'Transport Mappings 1468 for Version 2 of the Simple Network Management Protocol 1469 (SNMPv2)' for further information on snmpUDPDomain." 1470 SYNTAX OCTET STRING (SIZE (0..255)) 1472 A new OID should be defined to handle IPv6 addresses. 1474 5.072 RFC 2576 Coexistence between Version 1 Version 2 and Version 1475 3 of the Internet-standard Network Management Framework (SNMP) 1477 This document states: 1479 (11) For any object with a SYNTAX of NetworkAddress, the SYNTAX MUST 1480 be changed to IpAddress. Note that the use of NetworkAddress in 1481 new MIB documents is strongly discouraged (in fact, new MIB 1482 documents should be written using SMIv2, which does not define 1483 NetworkAddress). 1485 and defines the OID: 1487 snmpTrapAddress OBJECT-TYPE 1488 SYNTAX IpAddress 1489 MAX-ACCESS accessible-for-notify 1490 STATUS current 1491 DESCRIPTION 1492 "The value of the agent-addr field of a Trap PDU which 1493 is forwarded by a proxy forwarder application using 1494 an SNMP version other than SNMPv1. The value of this 1495 object SHOULD contain the value of the agent-addr field 1496 from the original Trap PDU as generated by an SNMPv1 1497 agent." 1498 ::= { snmpCommunityMIBObjects 3 } 1500 This clearly points out a lack of IPv6 awareness in this specification. 1502 5.073 RFC 2584 Definitions of Managed Objects for APPN/HPR in 1503 IP Networks 1505 Many of the OIDs described in this document assume the use of the 1506 IPv4 only TOS header bits. It is therefore IPv4 only in nature and 1507 will not support IPv6 interfaces. An updated MIB should be created. 1509 5.074 RFC 2591 Definitions of Managed Objects for Scheduling 1510 Management Operations 1512 There are no IPv4 dependencies in this protocol. 1514 5.075 RFC 2592 Definitions of Managed Objects for the Delegation 1515 of Management Script 1517 There are no IPv4 dependencies in this protocol. 1519 5.076 RFC 2594 Definitions of Managed Objects for WWW Services 1521 There are no IPv4 dependencies in this protocol. 1523 5.077 RFC 2605 Directory Server Monitoring MIB 1525 There are no IPv4 dependencies in this specification. 1527 5.078 RFC 2613 Remote Network Monitoring MIB Extensions for 1528 Switched Networks Version 1.0 1530 There are no IPv4 dependencies in this specification. 1532 5.079 RFC 2618 RADIUS Authentication Client MIB 1534 This RFC defines the following OIDs: 1536 RadiusAuthServerEntry ::= SEQUENCE { 1537 radiusAuthServerIndex Integer32, 1538 radiusAuthServerAddress IpAddress, 1539 radiusAuthClientServerPortNumber Integer32, 1540 radiusAuthClientRoundTripTime TimeTicks, 1541 radiusAuthClientAccessRequests Counter32, 1542 radiusAuthClientAccessRetransmissions Counter32, 1543 radiusAuthClientAccessAccepts Counter32, 1544 radiusAuthClientAccessRejects Counter32, 1545 radiusAuthClientAccessChallenges Counter32, 1546 radiusAuthClientMalformedAccessResponses Counter32, 1547 radiusAuthClientBadAuthenticators Counter32, 1548 radiusAuthClientPendingRequests Gauge32, 1549 radiusAuthClientTimeouts Counter32, 1550 radiusAuthClientUnknownTypes Counter32, 1551 radiusAuthClientPacketsDropped Counter32 1552 } 1554 radiusAuthServerAddress OBJECT-TYPE 1555 SYNTAX IpAddress 1556 MAX-ACCESS read-only 1557 STATUS current 1558 DESCRIPTION 1559 "The IP address of the RADIUS authentication server 1560 referred to in this table entry." 1561 ::= { radiusAuthServerEntry 2 } 1563 There needs to be an update to allow an IPv6 based OID for this 1564 value. 1566 5.080 RFC 2619 RADIUS Authentication Server MIB 1568 This MIB defines the followings OIDs: 1570 RadiusAuthClientEntry ::= SEQUENCE { 1571 radiusAuthClientIndex Integer32, 1572 radiusAuthClientAddress IpAddress, 1573 radiusAuthClientID SnmpAdminString, 1574 radiusAuthServAccessRequests Counter32, 1575 radiusAuthServDupAccessRequests Counter32, 1576 radiusAuthServAccessAccepts Counter32, 1577 radiusAuthServAccessRejects Counter32, 1578 radiusAuthServAccessChallenges Counter32, 1579 radiusAuthServMalformedAccessRequests Counter32, 1580 radiusAuthServBadAuthenticators Counter32, 1581 radiusAuthServPacketsDropped Counter32, 1582 radiusAuthServUnknownTypes Counter32 1583 } 1585 radiusAuthClientAddress OBJECT-TYPE 1586 SYNTAX IpAddress 1587 MAX-ACCESS read-only 1588 STATUS current 1589 DESCRIPTION 1590 "The NAS-IP-Address of the RADIUS authentication client 1591 referred to in this table entry." 1592 ::= { radiusAuthClientEntry 2 } 1594 There needs to be an update to allow an IPv6 based OID for this 1595 value. 1597 5.081 RFC 2622 Routing Policy Specification Language (RPSL) 1598 (RPSL) 1600 The only objects in the version of RPSL that deal with IP addresses 1601 are defined as: 1603 An IPv4 address is represented as a sequence of four 1604 integers in the range from 0 to 255 separated by the character dot 1605 ".". For example, 128.9.128.5 represents a valid IPv4 address. 1606 In the rest of this document, we may refer to IPv4 addresses as IP 1607 addresses. 1609 An address prefix is represented as an IPv4 address 1610 followed by the character slash "/" followed by an integer in the 1611 range from 0 to 32. The following are valid address prefixes: 1612 128.9.128.5/32, 128.9.0.0/16, 0.0.0.0/0; and the following address 1613 prefixes are invalid: 0/0, 128.9/16 since 0 or 128.9 are not 1614 strings containing four integers. 1616 There seems to be an awareness of IPv6 because of the terminology but 1617 it is not specifically defined. Therefore additional objects for IPv6 1618 addresses and masks need to be defined. 1620 5.082 RFC 2662 Definitions of Managed Objects for the ADSL 1621 Lines (MIB) 1623 There are no IPv4 dependencies in this specification. 1625 5.083 RFC 2665 Definitions of Managed Objects for the 1626 Ethernet-like Interface Types (MIB) 1628 There are no IPv4 dependencies in this specification. 1630 5.084 RFC 2667 IP Tunnel MIB 1632 The Abstract of this document says: 1634 This memo defines a Management Information Base (MIB) for use with 1635 network management protocols in the Internet community. In 1636 particular, it describes managed objects used for managing tunnels of 1637 any type over IPv4 networks. Extension MIBs may be designed for 1638 managing protocol-specific objects. Likewise, extension MIBs may be 1639 designed for managing security-specific objects. This MIB does not 1640 support tunnels over non-IPv4 networks (including IPv6 networks). 1641 Management of such tunnels may be supported by other MIBs. 1643 A similar MIB for tunneling over IPv6 should be defined. 1645 5.085 RFC 2668 Definitions of Managed Objects for IEEE 802.3 Medium 1646 Attachment Units (MAUs) (MAU-MIB) 1648 There are no IPv4 dependencies in this specification. 1650 5.086 RFC 2669 DOCSIS Cable Device MIB Cable Device Management 1651 Information Base for DOCSIS compliant Cable Modems and 1652 Cable Modem Termination Systems 1654 This document states: 1656 Please note that the DOCSIS 1.0 standard only requires Cable 1657 Modems to implement SNMPv1 and to process IPv4 customer traffic. 1658 Design choices in this MIB reflect those requirements. Future 1659 versions of the DOCSIS standard are expected to require support 1660 for SNMPv3 and IPv6 as well. 1662 5.087 RFC 2670 Radio Frequency (RF) Interface Management Information 1663 Base for MCNS/DOCSIS compliant RF interfaces (MIB) 1665 This MIB defines the following OIDs: 1667 DocsIfCmtsCmStatusEntry ::= SEQUENCE { 1668 docsIfCmtsCmStatusIndex Integer32, 1669 docsIfCmtsCmStatusMacAddress MacAddress, 1670 docsIfCmtsCmStatusIpAddress IpAddress, 1671 docsIfCmtsCmStatusDownChannelIfIndex InterfaceIndexOrZero, 1672 docsIfCmtsCmStatusUpChannelIfIndex InterfaceIndexOrZero, 1673 docsIfCmtsCmStatusRxPower TenthdBmV, 1674 docsIfCmtsCmStatusTimingOffset Unsigned32, 1675 docsIfCmtsCmStatusEqualizationData OCTET STRING, 1676 docsIfCmtsCmStatusValue INTEGER, 1677 docsIfCmtsCmStatusUnerroreds Counter32, 1678 docsIfCmtsCmStatusCorrecteds Counter32, 1679 docsIfCmtsCmStatusUncorrectables Counter32, 1680 docsIfCmtsCmStatusSignalNoise TenthdB, 1681 docsIfCmtsCmStatusMicroreflections Integer32 1682 } 1684 docsIfCmtsCmStatusIpAddress OBJECT-TYPE 1685 SYNTAX IpAddress 1686 MAX-ACCESS read-only 1687 STATUS current 1688 DESCRIPTION 1689 "IP address of this Cable Modem. If the Cable Modem has no 1690 IP address assigned, or the IP address is unknown, this 1691 object returns a value of 0.0.0.0. If the Cable Modem has 1692 multiple IP addresses, this object returns the IP address 1693 associated with the Cable interface." 1694 ::= { docsIfCmtsCmStatusEntry 3 } 1696 IPv6 OIDs should be defined. 1698 5.088 RFC 2674 Definitions of Managed Objects for Bridges with 1699 Traffic Classes, Multicast Filtering and Virtual LAN 1700 Extensions (MIB) 1702 There are no IPv4 dependencies in this specification. 1704 5.089 RFC 2677 Definitions of Managed Objects for the NBMA Next 1705 Hop Resolution Protocol (NHRP) (NHRP-MIB) 1707 There are no IPv4 dependencies in this specification. 1709 5.90 RFC 2720 Traffic Flow Measurement: Meter MIB 1711 This protocol is both IPv4 and IPv6 aware and needs no changes. 1713 5.091 RFC 2725 Routing Policy System Security 1715 There are no IPv4 dependencies in this protocol. 1717 5.092 RFC 2726 PGP Authentication for RIPE Database Updates 1719 There are no IPv4 dependencies in this protocol. 1721 5.093 RFC 2737 Entity MIB (Version 2) 1723 The TAddress Syntax is used in this MIB which contains IPv4 1724 assumptions and need to be updated. 1726 entLogicalTAddress OBJECT-TYPE 1727 SYNTAX TAddress 1728 MAX-ACCESS read-only 1729 STATUS current 1730 DESCRIPTION 1731 "The transport service address by which the logical entity 1732 receives network management traffic, formatted according to 1733 the corresponding value of entLogicalTDomain. 1735 For snmpUDPDomain, a TAddress is 6 octets long, the initial 1736 4 octets containing the IP-address in network-byte order and 1737 the last 2 containing the UDP port in network-byte order. 1738 Consult 'Transport Mappings for Version 2 of the Simple 1739 Network Management Protocol' (RFC 1906 [RFC1906]) for 1740 further information on snmpUDPDomain." 1742 5.094 RFC 2741 Agent Extensibility (AgentX) Protocol Version 1743 1 (SNMP) 1745 This protocol contains definitions for IPv4 only objects, by reference 1746 and all examples use only IPv4 addressing. However, there does not 1747 seem to be any reason that it could not easily be modified to support 1748 IPv6 addresses. 1750 5.095 RFC 2742 Definitions of Managed Objects for Extensible SNMP 1751 Agents 1753 There are no IPv4 dependencies in this protocol. 1755 5.096 RFC 2748 The COPS (Common Open Policy Service) Protocol 1756 (COPS) 1758 This protocol is both IPv4 and IPv6 aware and needs no changes. 1760 5.097 RFC 2749 COPS usage for RSVP 1762 There are no IPv4 dependencies in this protocol. 1764 5.098 RFC 2769 Routing Policy System Replication (RPSL) 1766 There are no IPv4 dependencies in this protocol. 1768 5.099 RFC 2787 Definitions of Managed Objects for the Virtual 1769 Router Redundancy Protocol 1771 As stated in the Overview section: 1773 Since the VRRP protocol is intended for use with IPv4 routers only, 1774 this MIB uses the SYNTAX for IP addresses which is specific to IPv4. 1775 Thus, changes will be required for this MIB to interoperate in an 1776 IPv6 environment. 1778 5.100 RFC 2788 Network Services Monitoring MIB 1780 There are no IPv4 dependencies in this specification. 1782 5.101 RFC 2789 Mail Monitoring MIB 1784 There are no IPv4 dependencies in this specification. 1786 5.102 RFC 2837 Definitions of Managed Objects for the Fabric Element 1787 in Fibre Channel Standard 1789 There are no IPv4 dependencies in this protocol. 1791 5.103 RFC 2851 Textual Conventions for Internet Network Addresses 1793 This MIB defines a new set of OIDs for that allow new MIB's to 1794 use multiple versions of IP. Currently IPv4 and IPv6 addressing 1795 is defined. Update of the many MIBs previously identified as 1796 having IPv4 dependencies could easily be updated using this new 1797 set of IP address abstractions. 1799 5.104 RFC 2856 Textual Conventions for Additional High Capacity 1800 Data Types (SNMP) 1802 There are no IPv4 dependencies in this protocol. 1804 5.105 RFC 2864 The Inverted Stack Table Extension to the Interfaces 1805 Group MIB 1807 There are no IPv4 dependencies in this specification. 1809 5.106 RFC 2895 Remote Network Monitoring MIB Protocol Identifier 1810 Reference (RMON-MIB) 1812 This MIB is both IPv4 and IPv6 aware and needs no changes. 1814 5.107 RFC 2925 Definitions of Managed Objects for Remote 1815 Ping, Traceroute, and Lookup Operations 1817 This MIB mostly is IPv4 and IPv6 aware. There are a few 1818 assumptions that are problems thought. In the following OIDs: 1820 pingCtlDataSize OBJECT-TYPE 1821 SYNTAX Unsigned32 (0..65507) 1822 UNITS "octets" 1823 MAX-ACCESS read-create 1824 STATUS current 1825 DESCRIPTION 1826 "Specifies the size of the data portion to be 1827 transmitted in a ping operation in octets. A ping 1828 request is usually an ICMP message encoded 1829 into an IP packet. An IP packet has a maximum size 1830 of 65535 octets. Subtracting the size of the ICMP 1831 or UDP header (both 8 octets) and the size of the IP 1832 header (20 octets) yields a maximum size of 65507 1833 octets." 1834 DEFVAL { 0 } 1835 ::= { pingCtlEntry 5 } 1837 traceRouteCtlDataSize OBJECT-TYPE 1838 SYNTAX Unsigned32 (0..65507) 1839 UNITS "octets" 1840 MAX-ACCESS read-create 1841 STATUS current 1842 DESCRIPTION 1843 "Specifies the size of the data portion of a traceroute 1844 request in octets. A traceroute request is essentially 1845 transmitted by encoding a UDP datagram into a 1846 IP packet. So subtracting the size of a UDP header 1847 (8 octets) and the size of a IP header (20 octets) 1848 yields a maximum of 65507 octets." 1849 DEFVAL { 0 } 1850 ::= { traceRouteCtlEntry 6 } 1852 There is clearly an assumption of IPv4 header sizes. 1854 5.108 RFC 2932 IPv4 Multicast Routing MIB 1856 This specification is only defined for IPv4 and a similar MIB 1857 must be defined for IPv6. 1859 5.109 RFC 2933 Internet Group Management Protocol MIB 1861 As stated in this document: 1863 Since IGMP is specific to IPv4, this MIB does not support management 1864 of equivalent functionality for other address families, such as IPv6. 1866 5.110 RFC 2940 Definitions of Managed Objects for Common 1867 Open Policy Service (COPS) Protocol Clients 1869 This MIB is both IPv4 and IPv6 aware and needs no changes. 1871 5.111 RFC 2954 Definitions of Managed Objects for Frame 1872 Relay Service (FR-MIB) 1874 There are no IPv4 dependencies in this specification. 1876 5.112 RFC 2955 Definitions of Managed Objects for Monitoring 1877 and Controlling the Frame Relay/ATM PVC Service 1878 Interworking Function 1880 There are no IPv4 dependencies in this protocol. 1882 5.113 RFC 2959 Real-Time Transport Protocol Management 1883 Information Base 1885 There are numerous uses of the included TAddress Syntax which is 1886 IPv4 dependent as noted above. 1888 For example: 1890 rtpSessionRemAddr OBJECT-TYPE 1891 SYNTAX TAddress 1892 MAX-ACCESS read-create 1893 STATUS current 1894 DESCRIPTION 1895 "The address to which RTP packets are sent by the RTP system. 1896 In an IP multicast RTP session, this is the single address used 1897 by all senders and receivers of RTP session data. In a unicast 1898 RTP session this is the unicast address of the remote RTP system. 1899 'The destination address pair may be common for all participants, 1900 as in the case of IP multicast, or may be different for each, as 1901 in the case of individual unicast network address pairs.' See 1902 RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' 1903 sec. 3. The transport service is identified by rtpSessionDomain. 1904 For snmpUDPDomain, this is an IP address and even-numbered UDP 1905 Port with the RTCP being sent on the next higher odd-numbered 1906 port, see RFC 1889, sec. 5." 1907 ::= { rtpSessionEntry 3 } 1909 There are a total of 8 instances of this. 1911 5.114 RFC 2981 Event MIB 1913 There are no IPv4 dependencies in this specification. 1915 5.115 RFC 2982 Distributed Management Expression MIB 1917 There are no IPv4 dependencies in this specification. 1919 5.116 RFC 3014 Notification Log MIB 1921 This document contains OIDs that are IPv4 specific: 1923 nlmLogVariableIpAddressVal OBJECT-TYPE 1924 SYNTAX IpAddress 1925 MAX-ACCESS read-only 1926 STATUS current 1927 DESCRIPTION 1928 "The value when nlmLogVariableType is 'ipAddress'. 1929 Although this seems to be unfriendly for IPv6, we 1930 have to recognize that there are a number of older 1931 MIBs that do contain an IPv4 format address, known 1932 as IpAddress. 1934 IPv6 addresses are represented using TAddress or 1935 InetAddress, and so the underlying datatype is 1936 OCTET STRING, and their value would be stored in 1937 the nlmLogVariableOctetStringVal column." 1938 ::= { nlmLogVariableEntry 9 } 1940 Not withstanding the note in the DESCRIPTION. 1942 5.117 RFC 3019 IP Version 6 Management Information Base for 1943 The Multicast Listener Discovery Protocol 1945 This is an IPv6 related document and is not discussed in this 1946 document. 1948 5.118 RFC 3020 Definitions of Managed Objects for Monitoring 1949 and Controlling the UNI/NNI Multilink Frame Relay Function 1951 There are no IPv4 dependencies in this protocol. 1953 5.119 RFC 3055 Management Information Base for the PINT Services 1954 Architecture 1956 There are no IPv4 dependencies in this protocol. 1958 5.120 RFC 3060 Policy Core Information Model -- Version 1 1959 Specification (CIM) 1961 There are no IPv4 dependencies in this protocol. 1963 5.121 RFC 3084 COPS Usage for Policy Provisioning (COPS-PR) 1964 (COPS-PR) 1966 This is an IPv4 only protocol. A version for IPv6 must be defined. 1968 6.0 Experimental RFCs 1970 Experimental RFCs typically define protocols that do not have widescale 1971 implementation or usage on the Internet. They are often propriety in 1972 nature or used in limited arenas. They are documented to the Internet 1973 community in order to allow potential interoperability or some other 1974 potential useful scenario. In a few cases they are presented as 1975 alternatives to the mainstream solution to an acknowledged problem. 1977 6.01 RFC 1187 Bulk Table Retrieval with the SNMP (SNMP-BULK) 1979 There are no IPv4 dependencies in this protocol. 1981 6.02 RFC 1224 Techniques for managing asynchronously generated 1982 alerts (ALERTS) 1984 There are no IPv4 dependencies in this protocol. 1986 6.03 RFC 1238 CLNS MIB for use with Connectionless Network Protocol 1987 (ISO 8473) and End System to Intermediate System (ISO 9542) 1988 (CLNS-MIB) 1990 There are no IPv4 dependencies in this specification. 1992 6.04 RFC 1592 Simple Network Management Protocol Distributed Protocol 1993 Interface Version 2.0 (SNMP-DPI) 1995 There are no IPv4 dependencies in this protocol. 1997 6.05 RFC 1792 TCP/IPX Connection Mib Specification (TCP/IPXMIB) 1999 There are no IPv4 dependencies in this specification. 2001 6.06 RFC 1901 Introduction to Community-based SNMPv2 (SNMPV2CB) 2003 There are no IPv4 dependencies in this protocol. 2005 6.07 RFC 1909 An Administrative Infrastructure for SNMPv2 2006 (SNMPV2AI) 2008 There are no IPv4 dependencies in this protocol. 2010 6.08 RFC 1910 User-based Security Model for SNMPv2 (SNMPV2SM) 2012 There are no IPv4 dependencies in this protocol. 2014 6.09 RFC 2593 Script MIB Extensibility Protocol Version 1.0 2016 There are no IPv4 dependencies in this specification. 2018 6.10 RFC 2724 RTFM: New Attributes for Traffic Flow Measurement 2020 There are no IPv4 dependencies in this protocol. 2022 6.11 RFC 2758 Definitions of Managed Objects for Service Level 2023 Agreements Performance Monitoring 2025 This protocol is both IPv4 and IPv6 aware and needs no changes. 2027 6.12 RFC 2786 Diffie-Helman USM Key Management Information Base and 2028 Textual Convention 2030 There are no IPv4 dependencies in this protocol. 2032 6.13 RFC 2903 Generic AAA Architecture 2034 There are no IPv4 dependencies in this protocol. 2036 6.14 RFC 2934 Protocol Independent Multicast MIB for IPv4 2038 This document is specific to IPv4. 2040 7.0 Summary of Results 2042 In the initial survey of RFCs 41 positives were identified out of a 2043 total of 163, broken down as follows: 2045 Standards 6 of 10 or 60.00% 2046 Draft Standards 3 of 18 or 16.67% 2047 Proposed Standards 31 of 121 or 25.62% 2048 Experimental RFCs 1 of 14 or 7.14% 2050 Of those identified many require no action because they document 2051 outdated and unused protocols, while others are document protocols 2052 that are actively being updated by the appropriate working groups. 2053 Additionally there are many instances of standards that should be 2054 updated but do not cause any operational impact if they are not 2055 updated. The remaining instances are documented below. 2057 7.1 Standards 2059 7.1.1 STD 15 Simple Network Management Protocol (RFCs 1157, 1155, 1213) 2061 The limitations identified have been addressed; RFC 1157 is HISTORIC, 2062 RFC1155 is obsoleted by RFC 2578-2580, and RFC1213 has been split to 2063 multiple modules which have been seen to. 2065 7.2 Draft Standards 2067 7.2.1 BGP4 MIB (RFC 1657) 2069 This problem is currently being addressed by the Inter Domain Routing 2070 (IDR) WG and an ID exists (draft-ietf-idr-bgp4-mib-09.txt). 2072 7.2.2 SMDS MIB (RFC 1694) 2074 See Section 7.1.22. Once a specification for IPv6 over SMDS is 2075 created a new MIB must be defined. 2077 7.2.3 RIPv2 MIB (RFC 1724) 2079 See Section 7.1.24. This problem is currently being addressed by the 2080 RIP WG and an ID exists (draft-ietf-rip-mib-01.txt). 2082 7.2.4 OSPFv2 MIB (RFC 1850) 2084 This problem is currently being addressed by the OSPF WG and an ID 2085 exists (draft-ietf-ospf-ospfv3-mib-04.txt). 2087 7.2.5 Transport MIB (RFC 1906) 2089 The problem has been fixed in RFC 2454, IPv6 Management Information 2090 Base for the User Datagram Protocol. 2092 7.2.6 Frame Relay MIB (RFC 2115) 2094 The problem has been fixed in RFC 2954, Definitions of Managed Objects 2095 for Frame Relay Service. 2097 7.3 Proposed Standards 2099 7.3.01 MIB for Multiprotocol Interconnect over X.25 (RFC 1461) 2101 This problem has not been addressed. A new specification should 2102 be created. 2104 7.3.02 PPP IPCP MIB (RFC 1473) 2106 There is no updated MIB to cover the problems outlined. A new MIB 2107 must be defined. 2109 7.3.03 DNS Server MIB (RFC 1611) 2111 This document is HISTORIC and no action is required. 2113 7.3.04 DNS Resolver MIB (RFC 1612) 2115 This document is HISTORIC and no action is required. 2117 7.3.05 Appletalk MIB (RFC 1742) 2119 The problems have not been addressed and a new MIB should be defined. 2121 7.3.06 The Definitions of Managed Objects for IP Mobility 2122 Support using SMIv2 (RFC 2006) 2124 The problems are being resolved by the Mobile IP WG and there is 2125 an ID (draft-ietf-mobileip-rfc2006bis-00.txt) 2127 7.3.07 SMIv2 MIB IP (RFC 2011) 2129 The problems have been addressed in RFC 2851, Textual Conventions 2130 for Internet Network Addresses, and RFC 2465, Management Information 2131 Base for IP Version 6: Textual Conventions and General Group. 2133 7.3.08 SNMPv2 MIB TCP (RFC 2012) 2135 The problems have been addressed in RFC 2452, IPv6 Management 2136 Information Base for the Transmission Control Protocol. 2138 7.3.09 SNMPv2 MIB UDP (RFC 2013) 2140 The problems have been addressed in RFC 2454, IPv6 Management 2141 Information Base for the User Datagram Protocol. 2143 7.3.10 RMON MIB (RFC 2021) 2145 The problems have been addressed in RFC 2819, Remote Network 2146 Monitoring Management Information Base. 2148 7.3.11 DataLink Switching using SMIv2 MIB (RFC 2022) 2150 The problems have not been addressed and a new MIB should be 2151 defined. 2153 7.3.12 IP Forwarding Table MIB (RFC 2096) 2155 This issue is being worked on by the IPv6 WG and an ID exists to 2156 address this (draft-ietf-ipngwg-rfc2096-update-00.txt) 2158 7.3.13 Classical IP & ARP over ATM MIB (RFC 2320) 2160 The problems identified are not addressed and a new MIB must be 2161 defined. 2163 7.3.14 Multicast over UNI 3.0/3.1 ATM MIB (RFC 2417) 2165 The problems identified are not addressed and a new MIB must be 2166 defined. 2168 7.3.15 ATM MIB (RFC 2515) 2170 The problems identified are not addressed and a new MIB must be 2171 defined. 2173 7.3.16 TN3270 MIB (RFC 2562) 2175 The problems identified are not addressed and a new MIB may be 2176 defined. 2178 7.3.17 Application MIB (RFC 2564) 2180 The problems identified are not addressed and a new MIB may be 2181 defined. 2182 One possible solution is to use RFC 3419 TCs. 2184 7.3.18 Coexistence of SNMP v1, v2, & v3 (RFC 2576) 2186 There are no real issues that can be resolved. 2188 7.3.19 Definitions of Managed Objects for APPN/HPR in IP Networks 2189 (RFC 2584) 2191 The problems identified are not addressed and a new MIB may be 2192 defined. 2194 7.3.20 RADIUS MIB (RFC 2618) 2196 The problems have not been addressed and a new MIB should be defined. 2198 7.3.21 RADIUS Authentication Server MIB (RFC 2619) 2200 The problems have not been addressed and a new MIB should be defined. 2202 7.3.22 IPv4 Tunnel MIB (RFC 2667) 2204 The problems have not been addressed and a new MIB should be defined. 2206 7.3.23 DOCSIS MIB (RFC 2669) 2208 This problem is currently being addressed by the IPCDN WG and an ID 2209 is available (draft-ietf-ipcdn-device-mibv2-01.txt). 2211 7.3.24 RF MIB For DOCSIS (RFC 2670) 2213 This problem is currently being addressed by the IPCDN WG and an ID 2214 is available (draft-ietf-ipcdn-docs-rfmibv2-01.txt). 2216 7.3.25 Entity MIB Version 2 (RFC 2737) 2218 The problems have not been addressed and a new MIB should be defined. 2220 7.3.26 AgentX Protocol V1 (RFC 2741) 2222 The problems have not been addressed and a new protocol may be 2223 defined. 2225 7.3.27 VRRP MIB (RFC 2787) 2227 The problems have not been addressed and a new MIB should be defined. 2229 7.3.28 MIB For Traceroute, Pings and Lookups (RFC 2925) 2231 The problems have not been addressed and a new MIB may be defined. 2233 7.3.29 IPv4 Multicast Routing MIB (RFC 2932) 2235 This problem is currently being addressed by the IDR WG and several 2236 IDs exist. 2238 7.3.30 IGMP MIB (RFC 2933) 2240 This problem is currently being addressed by the IDR WG. 2242 7.3.31 RPSL (RFC 2622) 2244 Additional objects must be defined for IPv6 addresses and prefixes. 2246 7.4 Experimental RFCs 2248 7.4.1 Protocol Independent Multicast MIB for IPv4 (RFC 2934) 2250 The problems have not been addressed and a new MIB should be defined. 2252 8.0 Security Consideration 2254 This memo examines the IPv6-readiness of specifications; this does not 2255 have security considerations in itself. 2257 9.0 Acknowledgements 2259 The authors would like to acknowledge the support of the Internet 2260 Society in the research and production of this document. 2261 Additionally the author, Philip J. Nesser II, would like to thanks 2262 his partner in all ways, Wendy M. Nesser. 2264 The editor, Andreas Bergstrom, would like to thank Pekka Savola 2265 for guidance and collection of comments for the editing of this 2266 document. 2267 He would further like to thank Juergen Schoenwaelder, Brian Carpenter 2268 and C. M. Heard for feedback on many points of this document. 2270 10.0 References 2272 10.1 Normative 2274 [1] Philip J. Nesser II, Andreas Bergstrom. "Introduction to the Survey 2275 of IPv4 Addresses in Currently Deployed IETF Standards", 2276 draft-ietf-v6ops-ipv4survey-intro-02.txt IETF work in progress, 2277 August 2003 2279 11.0 Authors Address 2281 Please contact the author with any questions, comments or suggestions 2282 at: 2284 Philip J. Nesser II 2285 Principal 2286 Nesser & Nesser Consulting 2287 13501 100th Ave NE, #5202 2288 Kirkland, WA 98034 2290 Email: phil@nesser.com 2291 Phone: +1 425 481 4303 2292 Fax: +1 425 48 2294 Andreas Bergstrom 2295 Ostfold University College 2296 Email: andreas.bergstrom@hiof.no 2297 Address: Rute 503 Buer 2298 N-1766 Halden 2299 Norway 2301 12.0 Intellectual Property Statement 2303 The IETF takes no position regarding the validity or scope of any 2304 intellectual property or other rights that might be claimed to 2305 pertain to the implementation or use of the technology described in 2306 this document or the extent to which any license under such rights 2307 might or might not be available; neither does it represent that it 2308 has made any effort to identify any such rights. Information on the 2309 IETF's procedures with respect to rights in standards-track and 2310 standards-related documentation can be found in BCP-11. Copies of 2311 claims of rights made available for publication and any assurances of 2312 licenses to be made available, or the result of an attempt made to 2313 obtain a general license or permission for the use of such 2314 proprietary rights by implementors or users of this specification can 2315 be obtained from the IETF Secretariat. 2316 The IETF invites any interested party to bring to its attention any 2317 copyrights, patents or patent applications, or other proprietary 2318 rights which may cover technology that may be required to practice 2319 this standard. Please address the information to the IETF Executive 2320 Director. 2322 13.0 Full Copyright Statement 2324 Copyright (C) The Internet Society (2000). All Rights Reserved. 2326 This document and translations of it may be copied and furnished to 2327 others, and derivative works that comment on or otherwise explain it 2328 or assist in its implementation may be prepared, copied, published 2329 and distributed, in whole or in part, without restriction of any 2330 kind, provided that the above copyright notice and this paragraph are 2331 included on all such copies and derivative works. However, this docu- 2332 ment itself may not be modified in any way, such as by removing the 2333 copyright notice or references to the Internet Society or other 2334 Internet organizations, except as needed for the purpose of develop- 2335 ing Internet standards in which case the procedures for copyrights 2336 defined in the Internet Standards process must be followed, or as 2337 required to translate it into languages other than English. The lim- 2338 ited permissions granted above are perpetual and will not be revoked 2339 by the Internet Society or its successors or assigns. This document 2340 and the information contained herein is provided on an "AS IS" basis 2341 and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DIS- 2342 CLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED 2343 TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 2344 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 2345 FITNESS FOR A PARTICULAR PURPOSE.