[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RFC 3289 on Management Information Base for the Differentiated Services Architecture

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

        RFC 3289

        Title:	    Management Information Base for the Differentiated
                    Services Architecture
        Author(s):  F. Baker, K. Chan, A. Smith
        Status:	    Standards Track
	Date:       May 2002
        Mailbox:    fred@cisco.com, khchan@nortelnetworks.com,
        Pages:      116
        Characters: 239041
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-diffserv-mib-16.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3289.txt

This memo describes an SMIv2 (Structure of Management Information
version 2) MIB for a device implementing the Differentiated Services
Architecture.  It may be used both for monitoring and configuration of
a router or switch capable of Differentiated Services functionality.

This document is a product of the Differentiated Services Working
Group of the IETF.  

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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

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

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.