STD 62, RFC 3411 on An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks

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

 



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


        STD 62
        RFC 3411

        Title:      An Architecture for Describing Simple Network
                    Management Protocol (SNMP) Management Frameworks
        Author(s):  D. Harrington, R. Presuhn, B. Wijnen
        Status:     Standards Track
        Date:       December 2002
        Mailbox:    dbh@enterasys.com, randy_presuhn@bmc.com,
                    bwijnen@lucent.com
        Pages:      64
        Characters: 140096
        Obsoletes:  2571
        See Also:   STD 62

        I-D Tag:    draft-ietf-snmpv3-arch-v2-02.txt

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


This document describes an architecture for describing Simple Network
Management Protocol (SNMP) Management Frameworks.  The architecture is
designed to be modular to allow the evolution of the SNMP protocol
standards over time.  The major portions of the architecture are an
SNMP engine containing a Message Processing Subsystem, a Security
Subsystem and an Access Control Subsystem, and possibly multiple SNMP
applications which provide specific functional processing of
management data.  This document obsoletes RFC 2571.

This document is a product of the SNMPv3 Working Group of the IETF. 

This is now a 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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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.
<ftp://ftp.isi.edu/in-notes/rfc3411.txt>

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux