draft-ietf-ipv6-rfc2013-update-03.txt   draft-ietf-ipv6-rfc2013-update-04.txt 
IPv6 MIB Revision Design Team Bill Fenner IPv6 MIB Revision Design Team B. Fenner
INTERNET-DRAFT AT&T Research Internet-Draft AT&T Labs -- Research
Expires: October 2004 John Flick Expires: April 18, 2005 J. Flick
Hewlett-Packard Company Hewlett-Packard Company
April 2004 October 18, 2004
Management Information Base Management Information Base for the User Datagram Protocol (UDP)
for the User Datagram Protocol (UDP) draft-ietf-ipv6-rfc2013-update-04
draft-ietf-ipv6-rfc2013-update-03.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is subject to all provisions
all provisions of Section 10 of RFC2026. of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as
Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This document is a product of the IPv6 MIB Revision Design Team. This Internet-Draft will expire on April 18, 2005.
Comments should be addressed to the authors, or to the mailing list
at ipv6@ietf.org.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects used for implementations In particular, it describes managed objects used for implementations
of the User Datagram Protocol (UDP) in an IP version independent of the User Datagram Protocol (UDP) in an IP version independent
manner. This memo obsoletes RFCs 2013 and 2454. manner. This memo obsoletes RFCs 2013 and 2454.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework ................. 5 1. Revision History . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview ................................................... 6 2. The Internet-Standard Management Framework . . . . . . . . . . 7
2.1. Relationship to Other MIBs ............................... 6 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1.1. Relationship to RFC1213-MIB ............................ 6 3.1 Relationship to Other MIBs . . . . . . . . . . . . . . . . 8
2.1.2. Relationship to the IPV6-UDP-MIB ....................... 7 3.1.1 Relationship to RFC1213-MIB . . . . . . . . . . . . . 8
2.1.3. Relationship to HOST-RESOURCES-MIB and SYSAPPL-MIB ..... 7 3.1.2 Relationship to the IPV6-UDP-MIB . . . . . . . . . . . 8
3. Definitions ................................................ 7 3.1.3 Relationship to HOST-RESOURCES-MIB and SYSAPPL-MIB . . 8
4. Intellectual Property ...................................... 18 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
5. Acknowledgements ........................................... 18 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20
6. Contributers ............................................... 18 6. Contributers . . . . . . . . . . . . . . . . . . . . . . . . . 20
7. Normative References ....................................... 19 7. Security Considerations . . . . . . . . . . . . . . . . . . . 21
8. Informative References ..................................... 19 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
9. Security Considerations .................................... 20 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
10. Editors Addresses ......................................... 21 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 22
11. Full Copyright Statement .................................. 21 9.2 Informative References . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . . . 25
Revision History 1. Revision History
[Note to RFC Editor: Please remove prior to publication] [Note to RFC Editor: Please remove prior to publication]
Changes from draft-ietf-ipv6-rfc2013-update-02.txt Changes from draft-ietf-ipv6-rfc2013-update-02.txt
18 October 2004 - IETF Last Call comments
Updated reference to RFC3291 to refer to 3291bis internet-draft.
Updated DESCRIPTION clause of the most recent REVISION clause to
reflect the changes that have been made since RFC 2013.
Updated DESCRIPTION clause of least recent REVISION clause to
reflect that MIB-II was published as RFC 1213.
Added pseudo OBJECT clauses to the description of
udpMIBCompliance2 for udpEndpointLocalAddress and
udpEndpointRemoteAddress.
Updated Overview section so that all references are cited.
Moved references to RFC 2287 and RFC 2790 from Normative
References to Informative References, since they are not actually
required for implementation, and we don't want advancement of this
document to be blocked.
Removed use of zero-length addresses to represent wildcard
listeners when the version is specified. Instead, use zero valued
addresses of the appropriate length. Updated udpEndpointTable and
udpEndpointLocalAddress DESCRIPTION clauses to reflect this.
Added IANA Considerations section.
Updated IPR boilerplate.
Changes from draft-ietf-ipv6-rfc2013-update-02.txt
27 April 2004 27 April 2004
Added text to section 2.1.2 to clarify why an equivalent to RFC Added text to section 2.1.2 to clarify why an equivalent to RFC
2454's ipv6UdpIfIndex is not required. 2454's ipv6UdpIfIndex is not required.
Changed the text of the Security Considerations so that it no Changed the text of the Security Considerations so that it no
longer implies that udpEndpointLocalPort is readable, but is longer implies that udpEndpointLocalPort is readable, but is
instead only returned as part of an index. instead only returned as part of an index.
Added an explicit reference to sysUpTime as a discontinuity Added an explicit reference to sysUpTime as a discontinuity
indicator to the counter objects in the mib. indicator to the counter objects in the mib.
Reworded the description of udpEndpointLocalAddress to indicate Reworded the description of udpEndpointLocalAddress to indicate
that it can be used to represent any address that the local that it can be used to represent any address that the local system
system is listening to, not just addresses assigned to the is listening to, not just addresses assigned to the system.
system.
Updated the description of InetAddress objects used as index Updated the description of InetAddress objects used as index
elements to indicate the 128 octet limit. elements to indicate the 128 octet limit.
Added a note to the description of udpEndpointRemoteAddressType Added a note to the description of udpEndpointRemoteAddressType to
to indicate that some combinations of indicate that some combinations of udpEndpointLocalAddressType and
udpEndpointLocalAddressType and udpEndpointRemoteAddressType are udpEndpointRemoteAddressType are not legal.
not legal.
Reverted udpEndpointInstance to not-accessible, since Reverted udpEndpointInstance to not-accessible, since
udpEndpointProcess is now a mandatory to implement object (to udpEndpointProcess is now a mandatory to implement object (to
align with the TCP-MIB). align with the TCP-MIB).
Added text to the udpEndpointInstance description to describe Added text to the udpEndpointInstance description to describe why
why it is needed. it is needed.
Added pseudo OBJECT clauses to the description of Added pseudo OBJECT clauses to the description of
udpMIBCompliance2 for udpEndpointLocalAddressType and udpMIBCompliance2 for udpEndpointLocalAddressType and
udpEndpointRemoteAddressType. udpEndpointRemoteAddressType.
Removed udpEndpointInstance from the udpEndpointGroup, since it Removed udpEndpointInstance from the udpEndpointGroup, since it is
is now not-accessible, and added udpEndpointProcess to the now not-accessible, and added udpEndpointProcess to the
udpEndpointGroup, since it is now mandatory. Removed the udpEndpointGroup, since it is now mandatory. Removed the
udpEndpointProcessGroup. udpEndpointProcessGroup.
Changes from draft-ietf-ipv6-rfc2013-update-00.txt Changes from draft-ietf-ipv6-rfc2013-update-00.txt
24 October 2003 24 October 2003
Dropped udpEndpointInDatagrams, udpEndpointHCInDatagrams, Dropped udpEndpointInDatagrams, udpEndpointHCInDatagrams,
udpEndpointOutDatagrams, udpEndpointHCOutDatagrams, udpEndpointOutDatagrams, udpEndpointHCOutDatagrams,
udpEndpointInOctets, udpEndpointHCInOctets, udpEndpointInOctets, udpEndpointHCInOctets, udpEndpointOutOctets,
udpEndpointOutOctets, udpEndpointHCOutOctets, and udpEndpointHCOutOctets, and udpEndpointStartTime.
udpEndpointStartTime.
Removed udpEndpointStatsGroup, udpEndpointHCDatagramStatsGroup Removed udpEndpointStatsGroup, udpEndpointHCDatagramStatsGroup and
and udpEndpointHCOctetStatsGroup. udpEndpointHCOctetStatsGroup.
Changed udpEndpointInstance back to read-only, since there is no Changed udpEndpointInstance back to read-only, since there is no
longer a mandatory non-auxiliary column in the udpEndpointTable. longer a mandatory non-auxiliary column in the udpEndpointTable.
Removed Open Issues section. Removed Open Issues section.
Moved Revision History section to beginning of document and Moved Revision History section to beginning of document and
removed its section number, to allow for easier removal at RFC removed its section number, to allow for easier removal at RFC
publication. publication.
skipping to change at page 4, line 9 skipping to change at page 5, line 21
udpEndpointRemoteAddress, and updated the DESCRIPTION clause of udpEndpointRemoteAddress, and updated the DESCRIPTION clause of
udpEndpointEntry. udpEndpointEntry.
Removed "Use of IP Addresses" section, since this information is Removed "Use of IP Addresses" section, since this information is
already documented in the relevant MIB DESCRIPTIONs. already documented in the relevant MIB DESCRIPTIONs.
Changes from draft-ietf-ipngwg-rfc2013-update-01.txt Changes from draft-ietf-ipngwg-rfc2013-update-01.txt
28 May 2002 28 May 2002
Removed udpConnectionTable Removed udpConnectionTable.
Renamed ListenerTable to EndpointTable, since with a remote Renamed ListenerTable to EndpointTable, since with a remote
address Listener is not quite correct. address Listener is not quite correct.
Use ''h consistently for 'any IP address', instead of sometimes Use ''h consistently for 'any IP address', instead of sometimes
''h and sometimes all-zeroes of the right address family. ''h and sometimes all-zeroes of the right address family.
Use "Datagram" instead of "Packet" to talk about UDP datagrams. Use "Datagram" instead of "Packet" to talk about UDP datagrams.
Added mandatory udpEndpointStartTime, this also fixes the Added mandatory udpEndpointStartTime, this also fixes the
udpEndpointInstance needing to be read-only and mandatory. udpEndpointInstance needing to be read-only and mandatory.
Make udpEndpointProcess mandatory on systems that have process Make udpEndpointProcess mandatory on systems that have process
IDs. IDs.
Make a note of { udp 6 } in a comment for clarity on why it's Make a note of { udp 6 } in a comment for clarity on why it's
skipped. skipped.
Fleshed out section 3. Fleshed out section 3.
Changed the deprecated udpLocalPort SYNTAX to Integer32. Since Changed the deprecated udpLocalPort SYNTAX to Integer32. Since it
it was already restricted to (0..65536) this is not a semantic was already restricted to (0..65536) this is not a semantic
change. change.
Changes from draft-ietf-ipngwg-rfc2013-update-00.txt Changes from draft-ietf-ipngwg-rfc2013-update-00.txt
14 November 2001 14 November 2001
Added udpConnectionTable Added udpConnectionTable.
Added udpListenerRemoteAddressType, to distinguish e.g. Added udpListenerRemoteAddressType, to distinguish e.g.
IPV6_V6ONLY IPV6_V6ONLY.
Added counters to udpListenerTable and udpConnectionTable Added counters to udpListenerTable and udpConnectionTable.
Changes from draft-ops-rfc2013-update-00.txt Changes from draft-ops-rfc2013-update-00.txt
12 Jul 2001 12 Jul 2001
Turned into IPNG WG document Turned into IPNG WG document
Changes from first draft posted to v6mib mailing list: Changes from first draft posted to v6mib mailing list:
23 Feb 2001 23 Feb 2001
skipping to change at page 5, line 21 skipping to change at page 6, line 34
21 Feb 2001 -- Juergen's changes 21 Feb 2001 -- Juergen's changes
Renamed udpInetTable to udpListenerTable Renamed udpInetTable to udpListenerTable
Updated Conformance info Updated Conformance info
6 Feb 2001 6 Feb 2001
Removed v6-only objects. Removed v6-only objects.
Removed remote and instance objects, turning the table back into Removed remote and instance objects, turning the table back into a
a listener-only table. listener-only table.
Renamed inetUdp* to udpInet* Renamed inetUdp* to udpInet*
Added HC in and out datagram counters Added HC in and out datagram counters
Added SIZE restriction to udpListenerLocalAddress. (36 = 32- Added SIZE restriction to udpListenerLocalAddress. (36 = 32-byte
byte addresses plus 4-byte scope, but it's just a strawman) addresses plus 4-byte scope, but it's just a strawman)
Used InetPortNumber TC from updated INET-ADDRESS-MIB Used InetPortNumber TC from updated INET-ADDRESS-MIB
Updated compliance statements. Updated compliance statements.
Added Keith to authors Added Keith to authors
Added open issues section. Added open issues section.
1. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
2. Overview 3. Overview
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects used for implementations
of the User Datagram Protocol (UDP), as defined in RFC 768 [RFC0768],
in an IP version independent manner.
The current UDP-MIB defined in this memo consists of one table and a The current UDP-MIB defined in this memo consists of one table and a
group of scalars: group of scalars:
- The udp group of scalars reports parameters and statistics of a o The udp group of scalars reports parameters and statistics of a
UDP protocol engine. Two scalars udpHCInDatagrams and UDP protocol engine. Two scalars udpHCInDatagrams and
udpHCOutDatagrams have been added to this group since the udpHCOutDatagrams have been added to this group since the
publication of RFC 2013 in order to provide high-capacity publication of RFC 2013 [RFC2013] in order to provide
counters for fast networks. high-capacity counters for fast networks. Discontinuities in the
values of the counters in this group are indicated by
discontinuities in the value of the sysUpTime object, which is
defined in RFC 3418 [RFC3418].
- The udpEndpointTable provides access to status information for o The udpEndpointTable provides access to status information for all
all UDP endpoints handled by a UDP protocol engine. The table UDP endpoints handled by a UDP protocol engine. The table
provides for strictly listening endpoints, as with the provides for strictly listening endpoints, as with the historical
historical udpTable, and also for "connected" UDP endpoints, udpTable, and also for "connected" UDP endpoints, which only
which only accept packets from a given remote system. It also accept packets from a given remote system. It also reports
reports identification of the operating system level processes identification of the operating system level processes which
which handle UDP connections. handle UDP connections. Addresses and ports of UDP endpoints in
this table are represented using the InetAddressType, InetAddress,
and InetPortNumber textual conventions defined in RFC 3291bis
[I-D.ietf-ops-rfc3291bis].
2.1. Relationship to Other MIBs 3.1 Relationship to Other MIBs
This section discusses the relationship of this UDP-MIB module to This section discusses the relationship of this UDP-MIB module to
other MIB modules. other MIB modules.
2.1.1. Relationship to RFC1213-MIB 3.1.1 Relationship to RFC1213-MIB
UDP related MIB objects were originally defined as part of the UDP related MIB objects were originally defined as part of the
RFC1213-MIB defined in RFC 1213 [RFC1213]. The UDP related objects of RFC1213-MIB defined in RFC 1213 [RFC1213]. The UDP related objects
the RFC1213-MIB were later copied into a separate MIB module and of the RFC1213-MIB were later copied into a separate MIB module and
published in RFC 2013 [RFC2013] in SMIv2 format. published in RFC 2013 [RFC2013] in SMIv2 format.
The previous versions of the UDP-MIB both defined the udpTable, which The previous versions of the UDP-MIB both defined the udpTable, which
has been deprecated for basically two reasons: has been deprecated for basically two reasons:
(1) The udpTable only supports IPv4. (1) The udpTable only supports IPv4.
The current approach in the IETF is to write IP version neutral The current approach in the IETF is to write IP version neutral
MIBs rather than having different definitions for various version MIBs rather than having different definitions for various version
of IP. This reduces the amount of overhead when new objects are of IP. This reduces the amount of overhead when new objects are
skipping to change at page 7, line 8 skipping to change at page 8, line 38
(2) The udpTable does not permit describing "connected" UDP (2) The udpTable does not permit describing "connected" UDP
endpoints. endpoints.
It turns out that "connected" endpoints tend to have a different It turns out that "connected" endpoints tend to have a different
behaviour and management access pattern compared to listening behaviour and management access pattern compared to listening
endpoints. Adding remote endpoint information to the endpoints. Adding remote endpoint information to the
udpEndpointTable thus allows for the addition of specific status udpEndpointTable thus allows for the addition of specific status
and statistic objects for "connected" endpoints and connections. and statistic objects for "connected" endpoints and connections.
2.1.2. Relationship to the IPV6-UDP-MIB 3.1.2 Relationship to the IPV6-UDP-MIB
The IPV6-UDP-MIB defined in RFC 2454 has been moved to Historic since The IPV6-UDP-MIB defined in RFC 2454 [RFC2454] has been moved to
the approach of having separate IP version specific tables is not Historic since the approach of having separate IP version specific
followed anymore. Implementation of RFC 2454 is thus not suggested tables is not followed anymore. Implementation of RFC 2454 is thus
anymore. not suggested anymore.
Note that since scoped addresses are now represented using the ipv4z Note that since scoped addresses are now represented using the ipv4z
and ipv6z address types, there is no longer a need to explicitly and ipv6z address types, there is no longer a need to explicitly
include the ifIndex in the index clause of the udpEndpointTable. include the ifIndex in the index clause of the udpEndpointTable.
This is a change from the use of ipv6UdpIfIndex in RFC 2454. This is a change from the use of ipv6UdpIfIndex in RFC 2454.
2.1.3. Relationship to HOST-RESOURCES-MIB and SYSAPPL-MIB 3.1.3 Relationship to HOST-RESOURCES-MIB and SYSAPPL-MIB
The udpEndpointTable reports the identification of the operating The udpEndpointTable reports the identification of the operating
system level process which handles a connection or a listening system level process which handles a connection or a listening
endpoint. The value is reported as an Unsigned32 which is expected to endpoint. The value is reported as an Unsigned32 which is expected
be the same as the hrSWRunIndex of the HOST-RESOURCES-MIB [RFC2790] to be the same as the hrSWRunIndex of the HOST-RESOURCES-MIB
(if the value is smaller than 2147483647) or the sysApplElmtRunIndex [RFC2790] (if the value is smaller than 2147483647) or the
of the SYSAPPL-MIB [RFC2287]. This allows managment applications to sysApplElmtRunIndex of the SYSAPPL-MIB [RFC2287]. This allows
identify the UDP connections that belong to an operating system level managment applications to identify the UDP connections that belong to
process, which has proven to be valuable in operational environments. an operating system level process, which has proven to be valuable in
operational environments.
3. Definitions 4. Definitions
UDP-MIB DEFINITIONS ::= BEGIN UDP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, Counter64, MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, Counter64,
Unsigned32, IpAddress, mib-2 FROM SNMPv2-SMI Unsigned32, IpAddress, mib-2 FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
InetAddress, InetAddressType, InetAddress, InetAddressType,
InetPortNumber FROM INET-ADDRESS-MIB; InetPortNumber FROM INET-ADDRESS-MIB;
udpMIB MODULE-IDENTITY udpMIB MODULE-IDENTITY
LAST-UPDATED "200404270000Z" -- April 27, 2004 LAST-UPDATED "200410180000Z" -- October 18, 2004
ORGANIZATION ORGANIZATION
"IETF IPv6 Working Group "IETF IPv6 Working Group
http://www.ietf.org/htmp.lharters/ipv6-charter.html" http://www.ietf.org/html.charters/ipv6-charter.html"
CONTACT-INFO CONTACT-INFO
"Bill Fenner (editor) "Bill Fenner (editor)
AT&T Labs -- Research AT&T Labs -- Research
75 Willow Rd. 75 Willow Rd.
Menlo Park, CA 94025 Menlo Park, CA 94025
Phone: +1 650 330-7893 Phone: +1 650 330-7893
Email: <fenner@research.att.com> Email: <fenner@research.att.com>
John Flick (editor) John Flick (editor)
Hewlett-Packard Company Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557 8000 Foothills Blvd. M/S 5557
Roseville, CA 95747 Roseville, CA 95747
Phone: +1 916 785 4018 Phone: +1 916 785 4018
Email: <johnf@rose.hp.com> Email: <john.flick@hp.com>
Send comments to <ipv6@ietf.org>" Send comments to <ipv6@ietf.org>"
DESCRIPTION DESCRIPTION
"The MIB module for managing UDP implementations. "The MIB module for managing UDP implementations.
Copyright (C) The Internet Society (2004). This Copyright (C) The Internet Society (2004). This
version of this MIB module is part of RFC XXXX; version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
-- RFC Ed.: Replace XXXX with actual RFC number & remove note -- RFC Ed.: Replace XXXX with actual RFC number & remove note
REVISION "200404270000Z" -- April 27, 2004 REVISION "200410180000Z" -- October 18, 2004
DESCRIPTION DESCRIPTION
"IP version neutral revision, published as RFC XXXX." "IP version neutral revision, incorporating the
following revisions:
- Added udpHCInDatagrams and udpHCOutDatagrams in order
to provide high-capacity counters for fast networks.
- Added text to the descriptions of all counter objects
to indicate how discontinuities are detected.
- Deprecated the IPv4-specific udpTable and replaced it
with the version neutral udpEndpointTable. This
table includes support for connected UDP endpoints
and support for identification of the operating
system process associated with a UDP endpoint.
- Deprecated the udpGroup, and replaced it with object
groups representing the current set of objects.
- Deprecated udpMIBCompliance, and replaced it with
udpMIBCompliance2, which includes the compliance
information for the new object groups.
This version published as RFC XXXX."
-- RFC Ed.: Replace XXXX with actual RFC number & remove note -- RFC Ed.: Replace XXXX with actual RFC number & remove note
REVISION "199411010000Z" -- November 1, 1994 REVISION "199411010000Z" -- November 1, 1994
DESCRIPTION DESCRIPTION
"Initial SMIv2 version, published as RFC 2013." "Initial SMIv2 version, published as RFC 2013."
REVISION "199103310000Z" -- March 31, 1991 REVISION "199103310000Z" -- March 31, 1991
DESCRIPTION DESCRIPTION
"The initial revision of this MIB module was part of "The initial revision of this MIB module was part of
MIB-II." MIB-II, published as RFC 1213."
::= { mib-2 50 } ::= { mib-2 50 }
-- the UDP group -- the UDP group
udp OBJECT IDENTIFIER ::= { mib-2 7 } udp OBJECT IDENTIFIER ::= { mib-2 7 }
udpInDatagrams OBJECT-TYPE udpInDatagrams OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 11, line 25 skipping to change at page 13, line 25
1) an application which is willing to accept both IPv4 1) an application which is willing to accept both IPv4
and IPv6 datagrams is represented by a and IPv6 datagrams is represented by a
udpEndpointLocalAddressType of unknown(0) and udpEndpointLocalAddressType of unknown(0) and
udpEndpointLocalAddress of ''h (a zero-length udpEndpointLocalAddress of ''h (a zero-length
octet-string). octet-string).
2) an application which is willing to accept only IPv4 2) an application which is willing to accept only IPv4
or only IPv6 datagrams is represented by a or only IPv6 datagrams is represented by a
udpEndpointLocalAddressType of the appropriate udpEndpointLocalAddressType of the appropriate
address type, and udpEndpointLocalAddress of ''h (a address type, and udpEndpointLocalAddress of
zero-length octet-string). '0.0.0.0' or '::' respectively.
3) an application which is listening for datagrams only 3) an application which is listening for datagrams only
for a specific IP address, but from any remote for a specific IP address, but from any remote
system, is repesented by a system, is repesented by a
udpEndpointLocalAddressType of the appropriate udpEndpointLocalAddressType of the appropriate
address type, udpEndpointLocalAddress specifying the address type, udpEndpointLocalAddress specifying the
local address. local address.
In all cases where the remote is a wildcard, the In all cases where the remote is a wildcard, the
udpEndpointRemoteAddressType is unknown(0), the udpEndpointRemoteAddressType is unknown(0), the
skipping to change at page 12, line 48 skipping to change at page 14, line 48
IPv4, IPv4z, IPv6 and IPv6z addresses are expected, or IPv4, IPv4z, IPv6 and IPv6z addresses are expected, or
unknown(0) if datagrams for all local IP addresses are unknown(0) if datagrams for all local IP addresses are
accepted." accepted."
::= { udpEndpointEntry 1 } ::= { udpEndpointEntry 1 }
udpEndpointLocalAddress OBJECT-TYPE udpEndpointLocalAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local IP address for this UDP endpoint. This is "The local IP address for this UDP endpoint.
either one of the IP addresses for which this node is
receiving packets, or a null octet-string (''h) to The value of this object can be represented in three
represent that datagrams destined to any address to possible ways, depending on the characteristics of the
which the system is listening of an IP version listening application:
consistent with udpEndpointLocalAddressType (or any IP
version, if udpEndpointLocalAddressType is unknown(0)) 1. For an application that is willing to accept both
will be accepted. IPv4 and IPv6 datagrams, the value of this object
must be ''h (a zero-length octet-string), with
the value of the corresponding instance of the
udpEndpointLocalAddressType object being unknown(0).
2. For an application which is willing to accept only
IPv4 or IPv6 datagrams, the value of this object
must be '0.0.0.0' or '::' respectively, while the
corresponding instatnce of the
udpEndpointLocalAddressType object represents the
appropriate address type.
3. For an application which is listening for data
destined only to a specific IP address, the value
of this object is the specific IP address for which
this node is receiving packets, with the
corresponding instance of the
udpEndpointLocalAddressType object representing the
appropriate address type.
As this object is used in the index for the As this object is used in the index for the
udpEndpointTable, implementors of this table should be udpEndpointTable, implementors of this table should be
careful not to create entries that would result in OIDs careful not to create entries that would result in OIDs
with more than 128 subidentifiers; else the information with more than 128 subidentifiers; else the information
cannot be accessed using SNMPv1, SNMPv2c or SNMPv3." cannot be accessed using SNMPv1, SNMPv2c or SNMPv3."
::= { udpEndpointEntry 2 } ::= { udpEndpointEntry 2 }
udpEndpointLocalPort OBJECT-TYPE udpEndpointLocalPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
skipping to change at page 16, line 31 skipping to change at page 18, line 50
for which we have the following compliance for which we have the following compliance
requirements, expressed in OBJECT clause form in this requirements, expressed in OBJECT clause form in this
description clause: description clause:
-- OBJECT udpEndpointLocalAddressType -- OBJECT udpEndpointLocalAddressType
-- SYNTAX InetAddressType { unknown(0), ipv4(1), -- SYNTAX InetAddressType { unknown(0), ipv4(1),
-- ipv6(2), ipv4z(3), -- ipv6(2), ipv4z(3),
-- ipv6z(4) } -- ipv6z(4) }
-- DESCRIPTION -- DESCRIPTION
-- Support for dns(5) is not required. -- Support for dns(5) is not required.
-- OBJECT udpEndpointLocalAddress
-- SYNTAX InetAddress (SIZE(0|4|8|16|20))
-- DESCRIPTION
-- Support is only required for zero-length
-- octet-strings, and for scoped and unscoped
-- IPv4 and IPv6 addresses.
-- OBJECT udpEndpointRemoteAddressType -- OBJECT udpEndpointRemoteAddressType
-- SYNTAX InetAddressType { unknown(0), ipv4(1), -- SYNTAX InetAddressType { unknown(0), ipv4(1),
-- ipv6(2), ipv4z(3), -- ipv6(2), ipv4z(3),
-- ipv6z(4) } -- ipv6z(4) }
-- DESCRIPTION -- DESCRIPTION
-- Support for dns(5) is not required. -- Support for dns(5) is not required.
-- OBJECT udpEndpointRemoteAddress
-- SYNTAX InetAddress (SIZE(0|4|8|16|20))
-- DESCRIPTION
-- Support is only required for zero-length
-- octet-strings, and for scoped and unscoped
-- IPv4 and IPv6 addresses.
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { udpBaseGroup, udpEndpointGroup } MANDATORY-GROUPS { udpBaseGroup, udpEndpointGroup }
GROUP udpHCGroup GROUP udpHCGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for those systems which "This group is mandatory for those systems which
are capable of receiving or transmitting more than are capable of receiving or transmitting more than
1 million UDP datagrams per second. 1 million 1 million UDP datagrams per second. 1 million
datagrams per second will cause a Counter32 to datagrams per second will cause a Counter32 to
wrap in just over an hour." wrap in just over an hour."
skipping to change at page 18, line 5 skipping to change at page 20, line 36
udpEndpointGroup OBJECT-GROUP udpEndpointGroup OBJECT-GROUP
OBJECTS { udpEndpointProcess } OBJECTS { udpEndpointProcess }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group of objects providing for the IP version "The group of objects providing for the IP version
independent management of UDP 'endpoints'." independent management of UDP 'endpoints'."
::= { udpMIBGroups 4 } ::= { udpMIBGroups 4 }
END END
4. Intellectual Property
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
5. Acknowledgements 5. Acknowledgements
This document contains a modified subset of RFC 1213 and updates RFC This document contains a modified subset of RFC 1213 and updates RFC
2013 and RFC 2454. Acknowledments are therefore due to the authors 2013 and RFC 2454. Acknowledments are therefore due to the authors
and editors of these documents for their excellent work. and editors of these documents for their excellent work.
6. Contributers 6. Contributers
This document is an output of the IPv6 MIB revision team, and This document is an output of the IPv6 MIB revision team, and
contributors to earlier versions of this document include: contributors to earlier versions of this document include:
skipping to change at page 19, line 13 skipping to change at page 21, line 23
Dave Thaler, Microsoft Dave Thaler, Microsoft
Email: dthaler@windows.microsoft.com Email: dthaler@windows.microsoft.com
Much of Keith McCloghrie's text from RFC1213/RFC2013 remains in this Much of Keith McCloghrie's text from RFC1213/RFC2013 remains in this
document, and the structure of the MIB is due to him. document, and the structure of the MIB is due to him.
Mike Daniele wrote the original IPv6 UDP MIB in RFC2454. Mike Daniele wrote the original IPv6 UDP MIB in RFC2454.
Juergen Schoenwalder provided much of the text for section 2. Juergen Schoenwalder provided much of the text for section 2.
7. Normative References 7. Security Considerations
[RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980.
[RFC2287] Krupczak, C., and J. Saperia, "Definitions of
System-Level Managed Objects for Applications", RFC 2287,
February 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Conformance Statements
for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB", RFC
2790, March 2000.
[RFC3291] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 3291, May 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", RFC 3418,
December 2002.
8. Informative References
[RFC1213] McCloghrie, K. and M. Rose, Editors, "Management
Information Base for Network Management of TCP/IP-based
internets: MIB-II", STD 17, RFC 1213, March 1991.
[RFC2013] McCloghrie, K., "Management Information Base for the
User Datagram Protocol using SMIv2", RFC 2013, November
1996.
[RFC2454] Daniele, M., "IP Version 6 Management Information Base
for the User Datagram Protocol", RFC 2454, December
1998.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
9. Security Considerations
There are no management objects defined in this MIB that have a MAX- There are no management objects defined in this MIB that have a
ACCESS clause of read-write and/or read-create. So, if this MIB is MAX-ACCESS clause of read-write and/or read-create. So, if this MIB
implemented correctly, then there is no risk that an intruder can is implemented correctly, then there is no risk that an intruder can
alter or create any management objects of this MIB module via direct alter or create any management objects of this MIB module via direct
SNMP SET operations. SNMP SET operations.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
skipping to change at page 21, line 10 skipping to change at page 22, line 20
(for authentication and privacy). (for authentication and privacy).
Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
10. Editors Addresses 8. IANA Considerations
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
+------------+-------------------------+
| Descriptor | OBJECT IDENTIFIER value |
+------------+-------------------------+
| udp | { mib-2 7} |
| udpMIB | { mib-2 50 } |
+------------+-------------------------+
Editor's Note (to be removed prior to publication): this draft makes
no additional requests of the IANA.
9. References
9.1 Normative References
[I-D.ietf-ops-rfc3291bis]
Daniele, M., "Textual Conventions for Internet Network
Addresses", draft-ietf-ops-rfc3291bis-06 (work in
progress), August 2004.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, RFC
3418, December 2002.
9.2 Informative References
[RFC1213] McCloghrie, K. and M. Rose, "Management Information Base
for Network Management of TCP/IP-based internets:MIB-II",
STD 17, RFC 1213, March 1991.
[RFC2013] McCloghrie, K., "SNMPv2 Management Information Base for
the User Datagram Protocol using SMIv2", RFC 2013,
November 1996.
[RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level
Managed Objects for Applications", RFC 2287, February
1998.
[RFC2454] Daniele, M., "IP Version 6 Management Information Base for
the User Datagram Protocol", RFC 2454, December 1998.
[RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB", RFC
2790, March 2000.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
Authors' Addresses
Bill Fenner Bill Fenner
AT&T Labs -- Research AT&T Labs -- Research
75 Willow Rd 75 Willow Rd
Menlo Park, CA 94025 Menlo Park, CA 94025
USA USA
Email: fenner@research.att.com EMail: fenner@research.att.com
John Flick John Flick
Hewlett-Packard Company Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557 8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557 Roseville, CA 95747-5557
USA USA
Email: johnf@rose.hp.com EMail: john.flick@hp.com
11. Full Copyright Statement Intellectual Property Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
This document and translations of it may be copied and furnished to Copies of IPR disclosures made to the IETF Secretariat and any
others, and derivative works that comment on or otherwise explain it assurances of licenses to be made available, or the result of an
or assist in its implementation may be prepared, copied, published attempt made to obtain a general license or permission for the use of
and distributed, in whole or in part, without restriction of any such proprietary rights by implementers or users of this
kind, provided that the above copyright notice and this paragraph are specification can be obtained from the IETF on-line IPR repository at
included on all such copies and derivative works. However, this http://www.ietf.org/ipr.
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be The IETF invites any interested party to bring to its attention any
revoked by the Internet Society or its successors or assigns. copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
This document and the information contained herein is provided on an Disclaimer of Validity
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING This document and the information contained herein are provided on an
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/