draft-ietf-tsvwg-udplite-mib-01.txt   draft-ietf-tsvwg-udplite-mib-02.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 14, 2008 September 11, 2007 Expires: March 30, 2008 October 11, 2007
MIB for the UDP-Lite protocol MIB for the UDP-Lite protocol
draft-ietf-tsvwg-udplite-mib-01 draft-ietf-tsvwg-udplite-mib-02
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 14, 2008. This Internet-Draft will expire on March 30, 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) for the This document specifies a Management Information Base (MIB) module
Lightweight User Datagram Protocol (UDP-Lite, RFC 3828). It defines for the Lightweight User Datagram Protocol, RFC 3828. It defines a
a set of new MIB entities to characterise the behaviour and set of new MIB entities to characterise the behaviour and performance
performance of transport layer endpoints deploying UDP-Lite. UDP- of transport layer endpoints deploying UDP-Lite. UDP-Lite resembles
Lite resembles UDP (RFC 768), but differs from the semantics of UDP UDP, but differs from the semantics of UDP by the addition of a
by the addition of a single (socket) option. This adds the single option. This adds the capability for variable-length data
capability for variable-length data checksum coverage, which can checksum coverage, which can benefit a class of applications that
benefit a class of applications that prefer delivery of (partially) prefer delivery of (partially) corrupted datagram payload data in
corrupted datagram payload data in preference to discarding the preference to discarding the datagram.
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 . . . . 4
1.3. Interpretation of the MIB Variables . . . . . . . . . . . 5 1.3. Interpretation of the MIB Variables . . . . . . . . . . . 5
2. The Internet-Standard Management Framework . . . . . . . . . . 7 1.4. Conventions . . . . . . . . . . . . . . . . . . . . . . . 7
2. The Internet-Standard Management Framework . . . . . . . . . . 8
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 21 4. Security Considerations . . . . . . . . . . . . . . . . . . . 21
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.1. Normative References . . . . . . . . . . . . . . . . . . . 30 7.1. Normative References . . . . . . . . . . . . . . . . . . . 30
7.2. Informative References . . . . . . . . . . . . . . . . . . 30 7.2. Informative References . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32
Intellectual Property and Copyright Statements . . . . . . . . . . 32 Intellectual Property and Copyright Statements . . . . . . . . . . 33
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
feature is not used, UDP-Lite is semantically identical to UDP. feature is not used, UDP-Lite is semantically identical to UDP.
The interface of UDP-Lite differs from that of UDP by the addition of The interface of UDP-Lite differs from that of UDP by the addition of
a single (socket) option, which communicates a length value. At the a single option, which communicates a length value. At the sender
sender this specifies the intended datagram checksum coverage; at the this specifies the intended datagram checksum coverage; at the
receiver it signifies a minimum coverage threshold for incoming receiver it signifies a minimum coverage threshold for incoming
datagrams. This length value may also be modified during the datagrams. This length value may also be modified during the
lifetime of a connection. UDP-Lite does not provide mechanisms to lifetime of a connection. UDP-Lite does not provide mechanisms to
negotiate the checksum coverage between the sender and receiver. negotiate the checksum coverage between the sender and receiver.
Where required, this needs to be communicated by another protocol. Where required, this needs to be communicated by another protocol.
DCCP [RFC4340] for instance includes a capability to negotiate DCCP [RFC4340] for instance includes a capability to negotiate
checksum coverage values. checksum coverage values.
This document defines a set of runtime statistics (variables) that This document defines a set of runtime statistics (variables) that
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 using the SMIv2 format [RFC2578]. statistics are provided as a MIB module using the SMIv2 format
[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 for The similarities between UDP and UDP-Lite suggest that the MIB module
UDP-Lite should resemble the MIB for UDP [RFC4113], with extensions for UDP-Lite should resemble the that of UDP [RFC4113], with
corresponding to the additional capabilities of UDP-Lite. The UDP- extensions corresponding to the additional capabilities of UDP-Lite.
Lite MIB is placed beneath the mib-2 subtree, adhering to the The UDP-Lite MIB module is placed beneath the mib-2 subtree, adhering
familiar structure of the UDP MIB [RFC4113] to ease integration. to the familiar structure of the UDP-MIB module [RFC4113] to ease
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: 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
error type also counts as InErrors. error type also counts as InErrors.
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 does not support an Another contrast to UDP is that the UDP-Lite MIB module does not
IPv4-only listener table. This feature was present only for support an IPv4-only listener table. This feature was present only
compatibility reasons and is superseded by the more informative for compatibility reasons and is superseded by the more informative
endpoint table. Two columnar objects have been added to this table: 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.
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 endpoint table of [RFC4113] contains one columnar object, also
used in this MIB, which reports the identification of the operating- used in this MIB module, which reports the identification of the
system-level process handling a connection or a listening endpoint. piece of software handling a connection or a listening endpoint. The
The value is reported as an Unsigned32, which is expected to be the value is reported as an Unsigned32, which is expected to be the same
same as the hrSWRunIndex of the HOST-RESOURCES-MIB [RFC2790] (if the as the hrSWRunIndex of the HOST-RESOURCES-MIB [RFC2790] (if the value
value is smaller than 2147483647) or the sysApplElmtRunIndex of the is smaller than 2147483647) or the sysApplElmtRunIndex of the
SYSAPPL-MIB [RFC2287]. SYSAPPL-MIB [RFC2287].
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
reference to counter names in brackets.
Received UDP-Lite Datagrams
|
| +- Full Coverage ---------------------+-> Deliver
| | |
+- Valid Header--+ +- >= Rec. Coverage --+
| (InDatagrams) | |
| +- Partial -----+
| (InPartialCov) |
| +- < Rec. Coverage --+
| (EndpointViolCoverage) |
| |
| |
+- Header Error ---+ |
| | |
+- Checksum Error -+-----------------------------------+-> Discard
| (InBadChecksum) (InErrors)
|
+- Port Error -------------------------------------------> Discard
(NoPorts)
Figure 1: UDP-Lite Input Processing Path
A platform-independent test of the UDP-Lite implementations in two A platform-independent test of the UDP-Lite implementations in two
connected end hosts may be performed as follows. connected end hosts may be performed as follows.
On the sending side, OutDatagrams and OutPartialCov are observed. If On the sending side, OutDatagrams and OutPartialCov are observed.
both values are equal, no partial coverage is employed. On the The ratio OutPartialCov/OutDatagrams describes the fraction (between
receiving side, InDatagrams, InPartialCov, and InErrors are 0 and 1) of datagrams using partial checksum coverage.
On the receiving side, InDatagrams, InPartialCov, and InErrors are
monitored. If datagrams are received from the given sender, InErrors monitored. If datagrams are received from the given sender, InErrors
is close to zero, and InPartialCov is zero, no partial coverage is is close to zero, and InPartialCov is zero, no partial coverage is
employed. If no datagrams are received and InErrors increases employed. If no datagrams are received and InErrors increases
proportionally with the sending rate, a configuration error is likely proportionally with the sending rate, a configuration error is likely
(a wrong value of receiver minimum checksum coverage). (a wrong value of receiver minimum checksum coverage).
The InBadChecksum counter reflects errors that may persist following The InBadChecksum counter reflects errors that may persist following
end-host processing, router processing, or link processing (this end-host processing, router processing, or link processing (this
includes illegal coverage values as defined in [RFC3828], since includes illegal coverage values as defined in [RFC3828], since
checksum and checksum coverage are mutually inter-dependent). In checksum and checksum coverage are mutually inter-dependent). In
skipping to change at page 5, line 51 skipping to change at page 6, line 33
o The number of InErrors that were discarded due to problems other o The number of InErrors that were discarded due to problems other
than bad checksum is InErrors - InBadChecksum than bad checksum is InErrors - InBadChecksum
o The number of InDatagrams that have full coverage is InDatagrams - o The number of InDatagrams that have full coverage is InDatagrams -
InPartialCov. InPartialCov.
o The number of OutDatagrams that have full coverage is OutDatagrams o The number of OutDatagrams that have full coverage is OutDatagrams
- OutPartialCov. - OutPartialCov.
The following Case diagram [CASE] summarises the relationships
between the counters on the input processing path.
Transport Layer Interface
-------------------------------------------------------------
/\
||
----------------------------- InDatagrams
|| ^
|| |
|| |
||----------------------> InPartialCov
|| |
|| |
|| v
|| EndpointViolCoverage
|| |
NoPorts <--------|| |
|| |
||------> InBadChecksum ------>|
|| |
|| |
|| v
||------------------------> InErrors
||
||
-------------------------------------------------------------
Network Layer Interface
Figure 2: Counters for received UDP-Lite Datagrams
A configuration error may occur when a sender chooses a coverage A configuration error may occur when a sender chooses a coverage
value for the datagrams that it sends that is less than the minimum value for the datagrams that it sends that is less than the minimum
coverage configured by the intended recipient. The minimum coverage coverage configured by the intended recipient. The minimum coverage
is set on a per-session basis by the application associated with the is set on a per-session basis by the application associated with the
listening endpoint, and its current value is recorded in the listening endpoint, and its current value is recorded in the
udpliteEndpointTable. Reception of valid datagrams with a checksum udpliteEndpointTable. Reception of valid datagrams with a checksum
coverage value less than this threshold results in dropping the coverage value less than this threshold results in dropping the
datagram [RFC3828] and incrementing InErrors. To improve debugging datagram [RFC3828] and incrementing InErrors. To improve debugging
of such (misconfigured) cases, an implementer may choose to support of such (misconfigured) cases, an implementer may choose to support
the optional udpliteEndpointViolCoverage entry in the endpoint table the optional udpliteEndpointViolCoverage entry in the endpoint table
(Section 1.1.) that specifically counts datagrams falling in this (Section 1.1.) that specifically counts datagrams falling in this
category. Without this feature, failure due to misconfiguration can category. Without this feature, failure due to misconfiguration can
not be distinguished from datagram processing failure. not be distinguished from datagram processing failure.
Figure 1 summarises the roles of the various receiver counters. 1.4. Conventions
Received Datagrams
|
| +-Full Coverage ----------------------+---> Deliver
| | |
+ InDatagrams -+ +-- >= Rec Coverage ---+
| | |
| +-InPartialCov-+
| |
| +-- < Rec Coverage ---+
| (EndpointViolCoverage) |
| |
| |
+ InBadChecksum -------------------------------------+---> Discard
| (InErrors)
|
+ NoPorts -----------------------------------------------> Discard
Figure 1: Counters for received UDP-Lite Datagrams The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, [RFC2119].
2. 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].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119].
==> RFC Editor's Note (please replace XXX with IANA value):
The MIB module in this document uses the following IANA-assigned
value, to be recorded in the SMI Numbers registry:
+------------+-------------------------+
| Descriptor | OBJECT IDENTIFIER value |
+------------+-------------------------+
| udpliteMIB | { mib-2 XXX } |
+------------+-------------------------+
Table 1: UDP-Lite Object Identifier
3. Definitions 3. Definitions
UDPLITE-MIB DEFINITIONS ::= BEGIN UDPLITE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2, MODULE-IDENTITY,
Unsigned32, Counter32, Counter64 FROM SNMPv2-SMI OBJECT-TYPE,
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF mib-2, Unsigned32,
InetAddress, InetAddressType, Counter32, Counter64 FROM SNMPv2-SMI -- [RFC2578]
InetPortNumber FROM INET-ADDRESS-MIB;
MODULE-COMPLIANCE,
OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
InetAddress,
InetAddressType,
InetPortNumber FROM INET-ADDRESS-MIB; -- [RFC4001]
udpliteMIB MODULE-IDENTITY udpliteMIB MODULE-IDENTITY
ORGANIZATION ORGANIZATION "IETF TSV Working Group (TSVWG)"
"Electronics Research Group at the University of
Aberdeen, UK"
CONTACT-INFO CONTACT-INFO
"Electronics Research Group "IETF TSV Working Group
Department of Engineering, University of Abderdeen http://www.ietf.org/html.charters/tsvwg-charter.html
Fraser Noble Building, Aberdeen AB24 3UE, UK Mailing List: tsvwg@ietf.org
Phone: +44 1224 27 2813 Gerrit Renker, Godred Fairhurst
Email: gerrit@erg.abdn.ac.uk" Electronics Research Group
Department of Engineering, University of Abderdeen
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 Internet Society (2007). This Copyright (C) The IETF Trust (2007). This version of
version of this MIB module is part of RFC ZZZ; this MIB module is part of RFC ZZZ; see the RFC
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 "Initial SMIv2 revision, based on the format of the UDP
the UDP MIB (RFC 4113) and published as RFC ZZZ." MIB module (RFC 4113) and published as RFC ZZZ."
-- RFC Ed.: replace ZZZ with actual RFC number & remove this note -- RFC Ed.: replace ZZZ with actual RFC number & remove this note
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: replace XXX with OBJECT-IDENTIFIER & remove this note -- RFC Ed.: replace XXX with OBJECT-IDENTIFIER & remove this note
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-initialization of the management system, and at
other times as indicated by discontinuities in the other times as indicated by discontinuities in the
skipping to change at page 11, line 25 skipping to change at page 11, line 25
value of sysUpTime." value of sysUpTime."
::= { 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 defined in RFC 3828), as their use coverage values, as their use would lead to incorrect
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-initialization of the management system, and at
other times as indicated by discontinuities in the other times as indicated by discontinuities in the
value of sysUpTime." value of sysUpTime."
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-initialization of the management system, and at
other times as indicated by discontinuities in the other times as indicated by discontinuities in the
value of sysUpTime." value of sysUpTime."
::= { 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-initialization of the management system, and at
other times as indicated by discontinuities in the other times as indicated by discontinuities in the
value of sysUpTime." value of sysUpTime."
::= { udplite 7 } ::= { udplite 7 }
udpliteEndpointTable OBJECT-TYPE udpliteEndpointTable OBJECT-TYPE
SYNTAX SEQUENCE OF UdpLiteEndpointEntry SYNTAX SEQUENCE OF UdpLiteEndpointEntry
skipping to change at page 13, line 12 skipping to change at page 13, line 12
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, the In all cases where the remote is a wildcard address,
udpliteEndpointRemoteAddressType is unknown(0), the the udpliteEndpointRemoteAddressType is unknown(0),
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 }
udpliteEndpointEntry OBJECT-TYPE udpliteEndpointEntry OBJECT-TYPE
skipping to change at page 17, line 14 skipping to change at page 17, line 14
udpliteEndpointInstance OBJECT-TYPE udpliteEndpointInstance OBJECT-TYPE
SYNTAX Unsigned32 (1..'ffffffff'h) SYNTAX Unsigned32 (1..'ffffffff'h)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The instance of this tuple. This object is used to "The instance of this tuple. This object is used to
distinguish among multiple processes 'connected' to distinguish among multiple processes 'connected' to
the same UDP-Lite endpoint. For example, on a system the same UDP-Lite endpoint. For example, on a system
implementing the BSD sockets interface, this would be implementing the BSD sockets interface, this would be
used to support the SO_REUSEADDR and SO_REUSEPORT used to support the SO_REUSEADDR and SO_REUSEPORT
socket options. socket options."
The object value should be obtained from a counter that
increments each time a new UDP-Lite endpoint is created.
Once the counter wraps around, care must be taken to
ensure that newly created indices are unique."
::= { 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
"The system's process ID for the process associated with "A unique value corresponding to a piece of software
this endpoint, or zero if there is no such process. running on this endpoint. Where possible, this should
This value is expected to be the same as be the system's native, unique identification number.
HOST-RESOURCES-MIB::hrSWRunIndex or SYSAPPL-MIB::
sysApplElmtRunIndex for some row in the appropriate This identifier is platform-specific. It may correspond
tables." to a process ID or application instance number. It is
expected to be the same as HOST-RESOURCES-MIB::
hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for
some row in the appropriate tables.
A value of zero indicates that the application
instance(s) cannot be identified."
::= { udpliteEndpointEntry 8 } ::= { 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.
(as defined in RFC 3828). If set to 0, only fully If set to 0, only fully covered datagrams are accepted."
covered datagrams are accepted." 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,
skipping to change at page 21, line 22 skipping to change at page 21, 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 may be used to imply an end host, the counters defined in this MIB module ay be used to
information about the characteristics of the end-to-end path over imply information about the characteristics of the end-to-end path
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
information about the requirements of the transport service information about the requirements of the transport service
skipping to change at page 23, line 7 skipping to change at page 23, line 7
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, 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.
5. IANA Considerations 5. IANA Considerations
This document requires IANA action to assign the UDP-Lite OBJECT The MIB module in this document uses the following IANA-assigned
IDENTIFIER value, defined in sections 2 and 3, under the 'mib-2' OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
subtree and to record the assignment in the SMI Numbers registry.
+------------+-------------------------+
| Descriptor | OBJECT IDENTIFIER value |
+------------+-------------------------+
| udpliteMIB | { mib-2 XXX } |
+------------+-------------------------+
==> Note to the RFC Editor (to be removed prior to publication): ==> Note to the RFC Editor (to be removed prior to publication):
The IANA is requested to assign a value for "XXX" under the 'mib-2' The IANA is requested to assign a value for "XXX" under the 'mib-2'
subtree and to record the assignment in the SMI Numbers registry. subtree and to record the assignment in the SMI Numbers registry.
When the assignment has been made, the RFC Editor is asked to replace When the assignment has been made, the RFC Editor is asked to replace
"XXX" (here and in the MIB module) with the assigned value and to "XXX" (here and in the MIB module) with the assigned value and to
remove this note. remove this note.
6. Acknowledgments 6. Acknowledgments
The design of the MIB presented owes much to the format of the MIB The design of the MIB module presented in this document owes much to
presented in [RFC4113]. the format of the module presented in [RFC4113].
==> NOTE TO THE RFC EDITOR: PLEASE REMOVE THIS LOG PRIOR TO PUBLICATION ==> NOTE TO THE RFC EDITOR: PLEASE REMOVE THIS LOG PRIOR TO PUBLICATION
Revision 00 of draft-ietf-tsvwg-udplite-mib was obsoleted by revision Revision 00 of draft-ietf-tsvwg-udplite-mib was obsoleted by revision
01 due to a syntax error (quote transposed with full-stop) in the 01 due to a syntax error (quote transposed with full-stop) in the MIB
MIB, which is corrected in rev-01. Thanks to Magnus Westerlund for module, which is corrected in rev-01. Thanks to Magnus Westerlund
identifying this. for identifying this.
Draft draft-ietf-tsvwg-udplite-mib-00 was published as a work item of Draft draft-ietf-tsvwg-udplite-mib-00 was published as a work item of
tsvwg, June 2007. tsvwg, June 2007.
The following changelog lists the changes up to revision 02 (which The following changelog lists the changes up to revision 02 (which
became rev-00/01 of this document) of the preceding individual draft became rev-00/01 of this document) of the preceding individual draft
submission draft-renker-tsvwg-udplite-mib. submission draft-renker-tsvwg-udplite-mib.
Changes introduced in rev-01: Changes introduced in rev-01:
skipping to change at page 27, line 35 skipping to change at page 27, line 35
Changes introduced in rev-02: Changes introduced in rev-02:
o General: o General:
- updated month, date, and revision - updated month, date, and revision
- changed `transport layer entities' to `endpoints' in abstract - changed `transport layer entities' to `endpoints' in abstract
o Section 1: o Section 1:
- added missing comma after `(socket) option' - added missing comma after `option'
- split explanatory clause after colon into standalone clause - split explanatory clause after colon into standalone clause
o Section 1.1: o Section 1.1:
- added a bullet list of standard counters known from the UDP - added a bullet list of standard counters known from the UDP
MIB MIB
- added a note that NoPorts does not increment InErrors - added a note that NoPorts does not increment InErrors
skipping to change at page 30, line 12 skipping to change at page 30, line 12
====> END OF NOTE TO THE RFC EDITOR <==== ====> END OF NOTE TO THE RFC EDITOR <====
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Schoenwaelder, Ed., "Structure of Management Information Rose, M., and S. Waldbusser, "Structure of Management
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Rose, M., and S. Waldbusser, "Textual Conventions for
STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
"Conformance Statements for SMIv2", STD 58, RFC 2580, Rose, M., and S. Waldbusser, "Conformance Statements for
April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC3828] Larzon, L-A., Degermark, M., Pink, S., Jonsson, L-E., and [RFC3828] Larzon, L-A., Degermark, M., Pink, S., Jonsson, L-E., and
G. Fairhurst, "The Lightweight User Datagram Protocol G. Fairhurst, "The Lightweight User Datagram Protocol
(UDP-Lite)", RFC 3828, July 2004. (UDP-Lite)", RFC 3828, July 2004.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
7.2. Informative References 7.2. Informative References
[CASE] Case, J. and C. Partridge, "Case Diagrams: A First Step to
Diagrammed Management Information Bases", ACM Computer
Communications Review, 19(1):13-16, January 1989.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980. August 1980.
[RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level [RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level
Managed Objects for Applications", RFC 2287, Managed Objects for Applications", RFC 2287,
February 1998. February 1998.
[RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB", [RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB",
RFC 2790, March 2000. RFC 2790, March 2000.
 End of changes. 45 change blocks. 
133 lines changed or deleted 183 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/