RFC 3747 on The Differentiated Services Configuration MIB

--NextPart


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


        RFC 3747

        Title:      The Differentiated Services Configuration MIB
        Author(s):  H. Hazewinkel, Ed., D. Partain, Ed.
        Status:     Standards Track
        Date:       April 2004
        Mailbox:    [email protected], [email protected]
        Pages:      24
        Characters: 51659
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-snmpconf-diffpolicy-09.txt

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


This memo describes a MIB module that provides a conceptual layer
between high-level "network-wide" policy definitions that effect
configuration of the Differentiated Services (diffserv) subsystem and
the instance-specific information that would include such details as
the parameters for all the queues associated with each interface in a
system.  This essentially provides an interface for configuring
differentiated services at a conceptually higher layer than that of
the Differentiated Services MIB.

This document is a product of the Configuration Management with SNMP
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 [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[email protected].  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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="[email protected]"

Content-Type: text/plain
Content-ID: <[email protected]>

RETRIEVE: rfc
DOC-ID: rfc3747

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc3747.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <[email protected]>

--OtherAccess--
--NextPart--

_______________________________________________
IETF-Announce mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ietf-announce