A new Request for Comments is now available in online RFC libraries.


        RFC 2013:

        Title:      SNMPv2 Management Information Base
                    for the User Datagram Protocol using SMIv2
        Author:     K. McCloghrie, Editor
        Date:       November 1996
        Mailbox:    kzm@cisco.com
        Pages:      6
        Characters: 9,333
        Updates/Obsoletes:  1213

        URL:        ftp://ds.internic.net/rfc/rfc2013.txt


This document is the MIB module which defines managed objects for
managing implementations of the User Datagram Protocol (UDP). This RFC
is a product of the SNMP Version 2 Working Group of the IETF.

IESG Note: The IP, UDP, and TCP MIB modules currently support only
IPv4.  These three modules use the IpAddress type defined as an OCTET
STRING of length 4 to represent the IPv4 32-bit internet addresses.
(See RFC 1902, SMI for SNMPv2.)  They do not support the new 128-bit
IPv6 internet addresses.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should be sent
to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute