draft-ietf-tsvwg-udplite-mib-02.txt   draft-ietf-tsvwg-udplite-mib-03.txt 
Transport Area Working Group G. Renker Transport Area Working Group G. Renker
Internet-Draft G. Fairhurst Internet-Draft G. Fairhurst
Intended status: Standards Track University of Aberdeen Intended status: Standards Track University of Aberdeen
Expires: March 30, 2008 October 11, 2007 Expires: May 1, 2008 October 29, 2007
MIB for the UDP-Lite protocol MIB for the UDP-Lite protocol
draft-ietf-tsvwg-udplite-mib-02 draft-ietf-tsvwg-udplite-mib-03
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 Internet-Draft will expire on March 30, 2008. This Internet-Draft will expire on May 1, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document specifies a Management Information Base (MIB) module This document specifies a Management Information Base (MIB) module
for the Lightweight User Datagram Protocol, RFC 3828. It defines a for the Lightweight User Datagram Protocol. It defines a set of new
set of new MIB entities to characterise the behaviour and performance MIB objects to characterise the behaviour and performance of
of transport layer endpoints deploying UDP-Lite. UDP-Lite resembles transport layer endpoints deploying UDP-Lite. UDP-Lite resembles
UDP, but differs from the semantics of UDP by the addition of a UDP, but differs from the semantics of UDP by the addition of a
single option. This adds the capability for variable-length data single option. This adds the capability for variable-length data
checksum coverage, which can benefit a class of applications that checksum coverage, which can benefit a class of applications that
prefer delivery of (partially) corrupted datagram payload data in prefer delivery of (partially) corrupted datagram payload data in
preference to discarding the datagram. preference to discarding the datagram.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Relationship to the UDP-MIB . . . . . . . . . . . . . . . 3 1.1. Relationship to the UDP-MIB . . . . . . . . . . . . . . . 3
1.2. Relationship to HOST-RESOURCES-MIB and SYSAPPL-MIB . . . . 4 1.2. Relationship to HOST-RESOURCES-MIB and SYSAPPL-MIB . . . . 5
1.3. Interpretation of the MIB Variables . . . . . . . . . . . 5 1.3. Interpretation of the MIB Variables . . . . . . . . . . . 5
1.4. Conventions . . . . . . . . . . . . . . . . . . . . . . . 7 1.4. Conventions . . . . . . . . . . . . . . . . . . . . . . . 8
2. The Internet-Standard Management Framework . . . . . . . . . . 8 2. The Internet-Standard Management Framework . . . . . . . . . . 9
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10
4. Security Considerations . . . . . . . . . . . . . . . . . . . 21 4. Security Considerations . . . . . . . . . . . . . . . . . . . 23
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.1. Normative References . . . . . . . . . . . . . . . . . . . 30 7.1. Normative References . . . . . . . . . . . . . . . . . . . 32
7.2. Informative References . . . . . . . . . . . . . . . . . . 30 7.2. Informative References . . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34
Intellectual Property and Copyright Statements . . . . . . . . . . 33 Intellectual Property and Copyright Statements . . . . . . . . . . 35
1. Introduction 1. Introduction
The Lightweight User Datagram Protocol (UDP-Lite) [RFC3828] (also The Lightweight User Datagram Protocol (UDP-Lite) [RFC3828] (also
known as UDPLite) is an IETF standards-track transport protocol. The known as UDPLite) is an IETF standards-track transport protocol. The
operation of UDP-Lite is similar to the User Datagram Protocol (UDP) operation of UDP-Lite is similar to the User Datagram Protocol (UDP)
[RFC0768], but can also serve applications in error-prone network [RFC0768], but can also serve applications in error-prone network
environments that prefer to have partially damaged payloads delivered environments that prefer to have partially damaged payloads delivered
rather than discarded. This is achieved by changing the semantics of rather than discarded. This is achieved by changing the semantics of
the UDP Length field to that of a Checksum Coverage field. If this the UDP Length field to that of a Checksum Coverage field. If this
skipping to change at page 3, line 38 skipping to change at page 3, line 38
facilitate both network management/monitoring as well as unified facilitate both network management/monitoring as well as unified
comparisons between different protocol implementations and operating comparisons between different protocol implementations and operating
environments. To provide a common interface for users and environments. To provide a common interface for users and
implementors of UDP-Lite modules, the definitions of these runtime implementors of UDP-Lite modules, the definitions of these runtime
statistics are provided as a MIB module using the SMIv2 format statistics are provided as a MIB module using the SMIv2 format
[RFC2578]. [RFC2578].
1.1. Relationship to the UDP-MIB 1.1. Relationship to the UDP-MIB
The similarities between UDP and UDP-Lite suggest that the MIB module The similarities between UDP and UDP-Lite suggest that the MIB module
for UDP-Lite should resemble the that of UDP [RFC4113], with for UDP-Lite should resemble that of UDP [RFC4113], with extensions
extensions corresponding to the additional capabilities of UDP-Lite. corresponding to the additional capabilities of UDP-Lite. The UDP-
The UDP-Lite MIB module is placed beneath the mib-2 subtree, adhering Lite MIB module is placed beneath the mib-2 subtree, adhering to the
to the familiar structure of the UDP-MIB module [RFC4113] to ease familiar structure of the UDP-MIB module to ease integration.
integration.
In particular, these well-known basic counters are supported: In particular, these well-known basic counters are supported:
o InDatagrams o InDatagrams
o NoPorts o NoPorts
o InErrors o InErrors
o OutDatagrams
o OutDatagrams
The following read-only variables have been added to the basic The following read-only variables have been added to the basic
structure used in the UDP-MIB module: structure used in the UDP-MIB module:
InPartialCov: The number of received datagrams, with a valid InPartialCov: The number of received datagrams, with a valid
format and checksum, whose checksum coverage is strictly less than format and checksum, whose checksum coverage is strictly less than
the datagram length. the datagram length.
InBadChecksum: The number of received datagrams with an invalid InBadChecksum: The number of received datagrams with an invalid
checksum (i.e. where the receiver-recalculated UDP-Lite checksum checksum (i.e. where the receiver-recalculated UDP-Lite checksum
does not match that in the Checksum field). Unlike NoPorts, this does not match that in the Checksum field). Unlike NoPorts, this
skipping to change at page 4, line 28 skipping to change at page 4, line 26
OutPartialCov: The number of sent datagrams with a valid format OutPartialCov: The number of sent datagrams with a valid format
and checksum whose checksum coverage is strictly less than the and checksum whose checksum coverage is strictly less than the
datagram length. datagram length.
All non-error counters used in this document are 64-bit counters. All non-error counters used in this document are 64-bit counters.
This is a departure from UDP, which traditionally used 32-bit This is a departure from UDP, which traditionally used 32-bit
counters and mandates 64-bit counters only on fast networks counters and mandates 64-bit counters only on fast networks
[RFC4113]. This choice is justified by the fact that UDP-Lite is a [RFC4113]. This choice is justified by the fact that UDP-Lite is a
more recent protocol, and that network speeds continue to grow. more recent protocol, and that network speeds continue to grow.
Another contrast to UDP is that the UDP-Lite MIB module does not Another difference from the UDP MIB module is that the UDP-Lite MIB
support an IPv4-only listener table. This feature was present only module does not support an IPv4-only listener table. This feature
for compatibility reasons and is superseded by the more informative was present only for compatibility reasons and is superseded by the
endpoint table. Two columnar objects have been added to this table: more informative endpoint table. Two columnar objects have been
added to this table:
udpliteEndpointMinCoverage: The minimum acceptable receiver udpliteEndpointMinCoverage: The minimum acceptable receiver
checksum coverage length [RFC3828]. This value may be manipulated checksum coverage length [RFC3828]. This value may be manipulated
by the application attached to the receiving endpoint. by the application attached to the receiving endpoint.
udpliteEndpointViolCoverage: This object is optional and counts udpliteEndpointViolCoverage: This object is optional and counts
the number of valid datagrams with a checksum coverage value less the number of valid datagrams with a checksum coverage value less
than the corresponding value of udpliteEndpointMinCoverage. than the corresponding value of udpliteEndpointMinCoverage.
Although being otherwise valid, such datagrams are discarded Although being otherwise valid, such datagrams are discarded
rather than passed to the application. This object thus serves to rather than passed to the application. This object thus serves to
separate cases of violated coverage from other InErrors. separate cases of violated coverage from other InErrors.
The second entry is not required to manage the transport protocol and The second entry is not required to manage the transport protocol and
hence is not mandatory. It may be implemented to assist in debugging hence is not mandatory. It may be implemented to assist in debugging
application design and configuration. application design and configuration.
The UDP-Lite MIB module also provides a discontinuity object to help
determine whether one or more of its counters experienced a
discontinuity event. This is an event, other than re-initialising
the management system, which invalidates the management entity's
understanding of the counter values.
For example, if UDP-Lite is implemented as a loadable operating
system module, a module load or unload would produce a discontinuity.
By querying the value of udpliteStatsDiscontinuityTime, a management
entity can determine whether or not a discontinuity event has
occurred.
1.2. Relationship to HOST-RESOURCES-MIB and SYSAPPL-MIB 1.2. Relationship to HOST-RESOURCES-MIB and SYSAPPL-MIB
The endpoint table of [RFC4113] contains one columnar object, also The UDP-Lite endpoint table contains one columnar object,
used in this MIB module, which reports the identification of the udpliteEndpointProcess, reporting a unique value which identifies a
piece of software handling a connection or a listening endpoint. The distinct piece of software associated with this endpoint. (When more
value is reported as an Unsigned32, which is expected to be the same than one piece of software is associated with this endpoint, a
as the hrSWRunIndex of the HOST-RESOURCES-MIB [RFC2790] (if the value representative is chosen; so that consecutive queries consistently
is smaller than 2147483647) or the sysApplElmtRunIndex of the refer to the same identifier, as long as the representative piece of
SYSAPPL-MIB [RFC2287]. software is running and still associated with the endpoint.)
The value of udpliteEndpointProcess is reported as an Unsigned32; and
it shares with the hrSWRunIndex of the HOST-RESOURCES-MIB [RFC2790]
and the sysApplElmtRunIndex of the SYSAPPL-MIB [RFC2287] the
requirement that, wherever possible, this should be the native and
unique identification number employed by the system.
If the SYSAPPL-MIB module is available, the value of
udpliteEndpointProcess should correspond to the appropriate value of
sysApplElmtRunIndex. If not available, an alternative should be used
(e.g. the hrSWRunIndex of the HOST-RESOURCES-MIB module).
1.3. Interpretation of the MIB Variables 1.3. Interpretation of the MIB Variables
Figure 1 shows an informal survey of the packet processing path, with Figure 1 shows an informal survey of the packet processing path, with
reference to counter names in brackets. reference to counter names in brackets.
Received UDP-Lite Datagrams Received UDP-Lite Datagrams
| |
| +- Full Coverage ---------------------+-> Deliver | +- Full Coverage ---------------------+-> Deliver
| | | | | |
skipping to change at page 9, line 15 skipping to change at page 10, line 15
3. Definitions 3. Definitions
UDPLITE-MIB DEFINITIONS ::= BEGIN UDPLITE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
mib-2, Unsigned32, mib-2, Unsigned32,
Counter32, Counter64 FROM SNMPv2-SMI -- [RFC2578] Counter32, Counter64 FROM SNMPv2-SMI -- [RFC2578]
TimeStamp FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
InetAddress, InetAddress,
InetAddressType, InetAddressType,
InetPortNumber FROM INET-ADDRESS-MIB; -- [RFC4001] InetPortNumber FROM INET-ADDRESS-MIB; -- [RFC4001]
udpliteMIB MODULE-IDENTITY udpliteMIB MODULE-IDENTITY
ORGANIZATION "IETF TSV Working Group (TSVWG)" ORGANIZATION "IETF TSV Working Group (TSVWG)"
CONTACT-INFO CONTACT-INFO
"IETF TSV Working Group "IETF TSV Working Group
http://www.ietf.org/html.charters/tsvwg-charter.html http://www.ietf.org/html.charters/tsvwg-charter.html
Mailing List: tsvwg@ietf.org Mailing List: tsvwg@ietf.org
Gerrit Renker, Godred Fairhurst Gerrit Renker, Godred Fairhurst
Electronics Research Group Electronics Research Group
Department of Engineering, University of Abderdeen School of Engineering, University of Aberdeen
Fraser Noble Building, Aberdeen AB24 3UE, UK" Fraser Noble Building, Aberdeen AB24 3UE, UK"
DESCRIPTION DESCRIPTION
"The MIB module for managing UDP-Lite implementations. "The MIB module for managing UDP-Lite implementations.
Copyright (C) The IETF Trust (2007). This version of Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC ZZZ; see the RFC this MIB module is part of RFC ZZZ; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed.: replace ZZZ with actual RFC number & remove this note -- RFC Ed.: replace ZZZ with actual RFC number & remove this note
DESCRIPTION DESCRIPTION
"Initial SMIv2 revision, based on the format of the UDP "Initial SMIv2 revision, based on the format of the UDP
skipping to change at page 10, line 14 skipping to change at page 11, line 42
udplite OBJECT IDENTIFIER ::= { udpliteMIB 1 } udplite OBJECT IDENTIFIER ::= { udpliteMIB 1 }
udpliteInDatagrams OBJECT-TYPE -- as in UDP-MIB udpliteInDatagrams OBJECT-TYPE -- as in UDP-MIB
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of UDP-Lite datagrams that were "The total number of UDP-Lite datagrams that were
delivered to UDP-Lite users. delivered to UDP-Lite users.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialisation of the management system, and at
other times as indicated by discontinuities in the other times as indicated by the value of
value of sysUpTime." udpliteStatsDiscontinuityTime."
::= { udplite 1 } ::= { udplite 1 }
udpliteInPartialCov OBJECT-TYPE -- new in UDP-Lite udpliteInPartialCov OBJECT-TYPE -- new in UDP-Lite
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of UDP-Lite datagrams that were "The total number of UDP-Lite datagrams that were
delivered to UDP-Lite users (applications) and whose delivered to UDP-Lite users (applications) and whose
checksum coverage was strictly less than the datagram checksum coverage was strictly less than the datagram
length. length.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
skipping to change at page 10, line 29 skipping to change at page 12, line 14
udpliteInPartialCov OBJECT-TYPE -- new in UDP-Lite udpliteInPartialCov OBJECT-TYPE -- new in UDP-Lite
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of UDP-Lite datagrams that were "The total number of UDP-Lite datagrams that were
delivered to UDP-Lite users (applications) and whose delivered to UDP-Lite users (applications) and whose
checksum coverage was strictly less than the datagram checksum coverage was strictly less than the datagram
length. length.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialisation of the management system, and at
other times as indicated by discontinuities in the other times as indicated by the value of
value of sysUpTime." udpliteStatsDiscontinuityTime."
::= { udplite 2 } ::= { udplite 2 }
udpliteNoPorts OBJECT-TYPE -- as in UDP-MIB udpliteNoPorts OBJECT-TYPE -- as in UDP-MIB
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of received UDP-Lite datagrams for "The total number of received UDP-Lite datagrams for
which there was no listener at the destination port. which there was no listener at the destination port.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialisation of the management system, and at
other times as indicated by discontinuities in the other times as indicated by the value of
value of sysUpTime." udpliteStatsDiscontinuityTime."
::= { udplite 3 } ::= { udplite 3 }
udpliteInErrors OBJECT-TYPE -- as in UDP-MIB udpliteInErrors OBJECT-TYPE -- as in UDP-MIB
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of received UDP-Lite datagrams that could not "The number of received UDP-Lite datagrams that could not
be delivered for reasons other than the lack of an be delivered for reasons other than the lack of an
application at the destination port. application at the destination port.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialisation of the management system, and at
other times as indicated by discontinuities in the other times as indicated by the value of
value of sysUpTime." udpliteStatsDiscontinuityTime."
::= { udplite 4 } ::= { udplite 4 }
udpliteInBadChecksum OBJECT-TYPE -- new in UDP-Lite udpliteInBadChecksum OBJECT-TYPE -- new in UDP-Lite
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of received UDP-Lite datagrams whose checksum "The number of received UDP-Lite datagrams whose checksum
could not be validated. This includes illegal checksum could not be validated. This includes illegal checksum
coverage values, as their use would lead to incorrect coverage values, as their use would lead to incorrect
checksums. checksums.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
skipping to change at page 11, line 28 skipping to change at page 13, line 14
udpliteInBadChecksum OBJECT-TYPE -- new in UDP-Lite udpliteInBadChecksum OBJECT-TYPE -- new in UDP-Lite
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of received UDP-Lite datagrams whose checksum "The number of received UDP-Lite datagrams whose checksum
could not be validated. This includes illegal checksum could not be validated. This includes illegal checksum
coverage values, as their use would lead to incorrect coverage values, as their use would lead to incorrect
checksums. checksums.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialisation of the management system, and at
other times as indicated by discontinuities in the other times as indicated by the value of
value of sysUpTime." udpliteStatsDiscontinuityTime."
REFERENCE "RFC 3828, section 3.1" REFERENCE "RFC 3828, section 3.1"
::= { udplite 5 } ::= { udplite 5 }
udpliteOutDatagrams OBJECT-TYPE -- as in UDP-MIB udpliteOutDatagrams OBJECT-TYPE -- as in UDP-MIB
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of UDP-Lite datagrams sent from this "The total number of UDP-Lite datagrams sent from this
entity. entity.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialisation of the management system, and at
other times as indicated by discontinuities in the other times as indicated by the value of
value of sysUpTime." udpliteStatsDiscontinuityTime."
::= { udplite 6 } ::= { udplite 6 }
udpliteOutPartialCov OBJECT-TYPE -- new in UDP-Lite udpliteOutPartialCov OBJECT-TYPE -- new in UDP-Lite
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of udpliteOutDatagrams whose "The total number of udpliteOutDatagrams whose
checksum coverage was strictly less than the checksum coverage was strictly less than the
datagram length. datagram length.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at at re-initialisation of the management system, and at
other times as indicated by discontinuities in the other times as indicated by the value of
value of sysUpTime." udpliteStatsDiscontinuityTime."
::= { udplite 7 } ::= { udplite 7 }
udpliteEndpointTable OBJECT-TYPE udpliteEndpointTable OBJECT-TYPE
SYNTAX SEQUENCE OF UdpLiteEndpointEntry SYNTAX SEQUENCE OF UdpLiteEndpointEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing information about this entity's "A table containing information about this entity's
UDP-Lite endpoints on which a local application is UDP-Lite endpoints on which a local application is
currently accepting or sending datagrams. currently accepting or sending datagrams.
skipping to change at page 13, line 12 skipping to change at page 14, line 43
address type and a udpliteEndpointLocalAddress of address type and a udpliteEndpointLocalAddress of
'0.0.0.0' or '::' respectively. '0.0.0.0' or '::' respectively.
3) An application that is listening for datagrams only 3) An application that 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 represented by a system is represented by a
udpliteEndpointLocalAddressType of the appropriate udpliteEndpointLocalAddressType of the appropriate
address type, with udpliteEndpointLocalAddress address type, with udpliteEndpointLocalAddress
specifying the local address. specifying the local address.
In all cases where the remote is a wildcard address, In all cases where the remote address is a wildcard,
the udpliteEndpointRemoteAddressType is unknown(0), the udpliteEndpointRemoteAddressType is unknown(0),
the udpliteEndpointRemoteAddress is ''h (a zero-length the udpliteEndpointRemoteAddress is ''h (a zero-length
octet-string), and the udpliteEndpointRemotePort is 0. octet-string), and the udpliteEndpointRemotePort is 0.
If the operating system is demultiplexing UDP-Lite If the operating system is demultiplexing UDP-Lite
packets by remote address/port, or if the application packets by remote address/port, or if the application
has 'connected' the socket specifying a default remote has 'connected' the socket specifying a default remote
address/port, the udpliteEndpointRemote* values should address/port, the udpliteEndpointRemote* values should
be used to reflect this." be used to reflect this."
::= { udplite 8 } ::= { udplite 8 }
skipping to change at page 15, line 39 skipping to change at page 17, line 39
destined only to a specific IP address, the value destined only to a specific IP address, the value
of this object is the specific IP address for of this object is the specific IP address for
which this node is receiving packets, with the which this node is receiving packets, with the
corresponding instance of the corresponding instance of the
EndpointLocalAddressType object representing the EndpointLocalAddressType object representing the
appropriate address type. appropriate address type.
As this object is used in the index for the As this object is used in the index for the
udpliteEndpointTable, implementors should be careful udpliteEndpointTable, implementors should be careful
not to create entries that would result in OIDs with not to create entries that would result in OIDs with
more than 128 subidentifiers; else the information more than 128 sub-identifiers; this is because of SNMP
cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3." and SMI limitations."
::= { udpliteEndpointEntry 2 } ::= { udpliteEndpointEntry 2 }
udpliteEndpointLocalPort OBJECT-TYPE udpliteEndpointLocalPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local port number for this UDP-Lite endpoint." "The local port number for this UDP-Lite endpoint."
::= { udpliteEndpointEntry 3 } ::= { udpliteEndpointEntry 3 }
udpliteEndpointRemoteAddressType OBJECT-TYPE udpliteEndpointRemoteAddressType OBJECT-TYPE
skipping to change at page 16, line 36 skipping to change at page 18, line 36
datagrams from any remote system are to be accepted, datagrams from any remote system are to be accepted,
this value is ''h (a zero-length octet-string). this value is ''h (a zero-length octet-string).
Otherwise, it has the type described by Otherwise, it has the type described by
udpliteEndpointRemoteAddressType and is the address of udpliteEndpointRemoteAddressType and is the address of
the remote system from which datagrams are to be the remote system from which datagrams are to be
accepted (or to which all datagrams will be sent). accepted (or to which all datagrams will be sent).
As this object is used in the index for the As this object is used in the index for the
udpliteEndpointTable, implementors should be careful udpliteEndpointTable, implementors should be careful
not to create entries that would result in OIDs with not to create entries that would result in OIDs with
more than 128 subidentifiers; else the information more than 128 sub-identifiers; this is because of SNMP
cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3." and SMI limitations."
::= { udpliteEndpointEntry 5 } ::= { udpliteEndpointEntry 5 }
udpliteEndpointRemotePort OBJECT-TYPE udpliteEndpointRemotePort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote port number for this UDP-Lite endpoint. If "The remote port number for this UDP-Lite endpoint. If
datagrams from any remote system are to be accepted, datagrams from any remote system are to be accepted,
this value is zero." this value is zero."
skipping to change at page 17, line 23 skipping to change at page 19, line 23
used to support the SO_REUSEADDR and SO_REUSEPORT used to support the SO_REUSEADDR and SO_REUSEPORT
socket options." socket options."
::= { udpliteEndpointEntry 7 } ::= { udpliteEndpointEntry 7 }
udpliteEndpointProcess OBJECT-TYPE udpliteEndpointProcess OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique value corresponding to a piece of software "A unique value corresponding to a piece of software
running on this endpoint. Where possible, this should running on this endpoint.
be the system's native, unique identification number.
This identifier is platform-specific. It may correspond If this endpoint is associated with more than one piece
to a process ID or application instance number. It is of software, the agent should choose one of these; such
expected to be the same as HOST-RESOURCES-MIB:: that subsequent reads will consistently return the same
hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for value, as long as the representative piece of software
some row in the appropriate tables. is running and still associated with the endpoint. The
implementation may use any algorithm satisfying these
constraints (e.g. choosing the entity with the oldest
start time).
A value of zero indicates that the application This identifier is platform-specific. Wherever possible,
instance(s) cannot be identified." it should use the system's native, unique identification
::= { udpliteEndpointEntry 8 } number as value.
If the SYSAPPL-MIB module is available, the value should
be the same as sysApplElmtRunIndex. If not available, an
alternative should be used (e.g. the hrSWRunIndex of the
HOST-RESOURCES-MIB module).
If it is not possible to uniquely identify the pieces of
software associated with this endpoint, then the value
zero should be used. (Note that zero is otherwise a
valid value for sysApplElmtRunIndex.)"
::= { udpliteEndpointEntry 8 }
udpliteEndpointMinCoverage OBJECT-TYPE -- new in UDP-Lite udpliteEndpointMinCoverage OBJECT-TYPE -- new in UDP-Lite
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum checksum coverage expected by this endpoint. "The minimum checksum coverage expected by this endpoint.
If set to 0, only fully covered datagrams are accepted." A value of 0 indicates that only fully covered datagrams
are accepted."
REFERENCE "RFC 3828, section 3.1" REFERENCE "RFC 3828, section 3.1"
::= { udpliteEndpointEntry 9 } ::= { udpliteEndpointEntry 9 }
udpliteEndpointViolCoverage OBJECT-TYPE -- new / optional in UDP-Lite udpliteEndpointViolCoverage OBJECT-TYPE -- new / optional in UDP-Lite
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of datagrams received by this endpoint whose "The number of datagrams received by this endpoint whose
checksum coverage violated the minimum coverage threshold checksum coverage violated the minimum coverage threshold
set for this connection (i.e. all valid datagrams whose set for this connection (i.e. all valid datagrams whose
checksum coverage was strictly smaller than the minimum, checksum coverage was strictly smaller than the minimum,
as defined in RFC 3828)." as defined in RFC 3828).
Discontinuities in the value of this counter can occur
at re-initialisation of the management system, and at
other times as indicated by the value of
udpliteStatsDiscontinuityTime."
::= { udpliteEndpointEntry 10 } ::= { udpliteEndpointEntry 10 }
udpliteStatsDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the most recent occasion at
which one or more of the UDP-Lite counters suffered a
discontinuity.
A value of zero indicates no such discontinuity has
occurred since the last re-initialisation of the local
management subsystem."
::= { udplite 9 }
-- Conformance Information
udpliteMIBConformance OBJECT IDENTIFIER ::= { udpliteMIB 2 } udpliteMIBConformance OBJECT IDENTIFIER ::= { udpliteMIB 2 }
udpliteMIBCompliance MODULE-COMPLIANCE udpliteMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for systems that implement "The compliance statement for systems that implement
UDP-Lite. UDP-Lite.
There are a number of INDEX objects that cannot be There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2, represented in the form of OBJECT clauses in SMIv2,
skipping to change at page 19, line 19 skipping to change at page 21, line 48
-- octet-strings, and for scoped and unscoped -- octet-strings, and for scoped and unscoped
-- IPv4 and IPv6 addresses. -- IPv4 and IPv6 addresses.
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { udpliteBaseGroup, MANDATORY-GROUPS { udpliteBaseGroup,
udplitePartialCsumGroup, udplitePartialCsumGroup,
udpliteEndpointGroup } udpliteEndpointGroup }
GROUP udpliteAppGroup GROUP udpliteAppGroup
DESCRIPTION DESCRIPTION
"This group is optional and provides supplementary "This group is optional and provides supplementary
information about the effectivity of using minimum information about the effectiveness of using minimum
checksum coverage thresholds on endpoints." checksum coverage thresholds on endpoints."
::= { udpliteMIBConformance 1 } ::= { udpliteMIBConformance 1 }
udpliteMIBGroups OBJECT IDENTIFIER ::= { udpliteMIBConformance 2 } udpliteMIBGroups OBJECT IDENTIFIER ::= { udpliteMIBConformance 2 }
udpliteBaseGroup OBJECT-GROUP -- as in UDP udpliteBaseGroup OBJECT-GROUP -- as in UDP
OBJECTS { udpliteInDatagrams, udpliteNoPorts, udpliteInErrors, OBJECTS { udpliteInDatagrams, udpliteNoPorts, udpliteInErrors,
udpliteOutDatagrams } udpliteOutDatagrams, udpliteStatsDiscontinuityTime }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group of objects providing for counters of "The group of objects providing for counters of
basic UDP-like statistics." basic UDP-like statistics."
::= { udpliteMIBGroups 1 } ::= { udpliteMIBGroups 1 }
udplitePartialCsumGroup OBJECT-GROUP -- specific to UDP-Lite udplitePartialCsumGroup OBJECT-GROUP -- specific to UDP-Lite
OBJECTS { udpliteInPartialCov, OBJECTS { udpliteInPartialCov,
udpliteInBadChecksum, udpliteInBadChecksum,
udpliteOutPartialCov } udpliteOutPartialCov }
skipping to change at page 21, line 22 skipping to change at page 23, line 22
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:
Since UDP-Lite permits the delivery of (partially) corrupted data to Since UDP-Lite permits the delivery of (partially) corrupted data to
an end host, the counters defined in this MIB module ay be used to an end host, the counters defined in this MIB module may be used to
imply information about the characteristics of the end-to-end path infer information about the characteristics of the end-to-end path
over which the datagrams are communicated. over which the datagrams are communicated.
The indices of the udpliteEndpointTable contain information about the The indices of the udpliteEndpointTable contain information about the
listeners on an entity. In particular, the udpliteEndpointLocalPort listeners on an entity. In particular, the udpliteEndpointLocalPort
and udpliteLocalPort objects in the indices can be used to identify and udpliteLocalPort objects in the indices can be used to identify
what ports are open on the machine and which attacks are likely to what ports are open on the machine and which attacks are likely to
succeed, without the attacker having to run a port scanner. The succeed, without the attacker having to run a port scanner. The
table also identifies the currently listening UDP-Lite ports. This table also identifies the currently listening UDP-Lite ports. This
could be used to infer the type of application associated with the could be used to infer the type of application associated with the
port at the receiver. The udpliteEndpointMinCoverage provides port at the receiver. The udpliteEndpointMinCoverage provides
skipping to change at page 26, line 31 skipping to change at page 28, line 31
o General: o General:
- incremented revision number to 01 - incremented revision number to 01
- updated date to November - updated date to November
- rephrased abstract - rephrased abstract
o Section 1: o Section 1:
- rephrased the begining of the second paragraph - rephrased the beginning of the second paragraph
o Section 1.1: o Section 1.1:
- rephrased some items - rephrased some items
- added missing InBadChecksum heading - added missing InBadChecksum heading
- updated text to refer to 64bit counters - updated text to refer to 64bit counters
o Section 1.3: o Section 1.3:
- removed 'x' in 'datagrams' - removed 'x' in 'datagrams'
- rephrased for clarity - rephrased for clarity
- Figure 1: missing bracked text should be InErrors - Figure 1: missing bracketed text should be InErrors
- Figure 1: correction - NoPorts are not counted as InDatagrams - Figure 1: correction - NoPorts are not counted as InDatagrams
o Section 2: o Section 2:
- made the "Editor's Note" stand out more - made the "Editor's Note" stand out more
o Section 3 / MIB: o Section 3 / MIB:
- upgraded 11 32bit counters to 64bit - upgraded 11 32bit counters to 64bit
skipping to change at page 32, line 9 skipping to change at page 34, line 9
[RFC4113] Fenner, B. and J. Flick, "Management Information Base for [RFC4113] Fenner, B. and J. Flick, "Management Information Base for
the User Datagram Protocol (UDP)", RFC 4113, June 2005. the User Datagram Protocol (UDP)", RFC 4113, June 2005.
[RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram
Congestion Control Protocol (DCCP)", RFC 4340, March 2006. Congestion Control Protocol (DCCP)", RFC 4340, March 2006.
Authors' Addresses Authors' Addresses
Gerrit Renker Gerrit Renker
University of Aberdeen University of Aberdeen
Department of Engineering School of Engineering
Fraser Noble Building Fraser Noble Building
Aberdeen AB24 3UE Aberdeen AB24 3UE
Scotland Scotland
Email: gerrit@erg.abdn.ac.uk Email: gerrit@erg.abdn.ac.uk
URI: http://www.erg.abdn.ac.uk URI: http://www.erg.abdn.ac.uk
Godred Fairhurst Godred Fairhurst
University of Aberdeen University of Aberdeen
Department of Engineering School of Engineering
Fraser Noble Building Fraser Noble Building
Aberdeen AB24 3UE Aberdeen AB24 3UE
Scotland Scotland
Email: gorry@erg.abdn.ac.uk Email: gorry@erg.abdn.ac.uk
URI: http://www.erg.abdn.ac.uk URI: http://www.erg.abdn.ac.uk
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
 End of changes. 45 change blocks. 
85 lines changed or deleted 143 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/