RFC 3411 - An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks

Network Working Group
Request for Comments: 3411
STD: 62
Obsoletes: 2571
Category: Standards Track

Authors:

• D. Harrington, Enterasys Networks
• R. Presuhn, BMC Software, Inc.
• B. Wijnen, Lucent Technologies

Date: December 2002

Status of this Memo

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.

Copyright Notice

Copyright (C) The Internet Society (2002). All Rights Reserved.

Abstract

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.

Contents

• 1. Introduction
  • 1.1. Overview
  • 1.2. SNMP
  • 1.3. Goals of this Architecture
  • 1.4. Security Requirements of this Architecture
  • 1.5. Design Decisions
• 2. Documentation Overview
  • 2.1. Document Roadmap
  • 2.2. Applicability Statement
  • 2.3. Coexistence and Transition
  • 2.4. Transport Mappings
  • 2.5. Message Processing
  • 2.6. Security
  • 2.7. Access Control
  • 2.8. Protocol Operations
  • 2.9. Applications
  • 2.10. Structure of Management Information
  • 2.11. Textual Conventions
  • 2.12. Conformance Statements
  • 2.13. Management Information Base Modules
  • 2.14. SNMP Framework Documents
• 3. Elements of the Architecture
  • 3.1. The Naming of Entities
  • 3.2. The Naming of Identities
  • 3.3. The Naming of Management Information
  • 3.4. Other Constructs
• 4. Abstract Service Interfaces
  • 4.1. Dispatcher Primitives
  • 4.2. Message Processing Subsystem Primitives
  • 4.3. Access Control Subsystem Primitives
  • 4.4. Security Subsystem Primitives
  • 4.5. Common Primitives
  • 4.6. Scenario Diagrams
• 5. Managed Object Definitions for SNMP Management Frameworks
• 6. IANA Considerations
  • 6.1. Security Models
  • 6.2. Message Processing Models
  • 6.3. SnmpEngineID Formats
• 7. Intellectual Property
• 8. Acknowledgements
• 9. Security Considerations
• 10. References
  • 10.1. Normative References
  • 10.2. Informative References
• Appendix A. Guidelines for Model Designers
  • A.1. Security Model Design Requirements
  • A.2. Message Processing Model Design Requirements
  • A.3. Application Design Requirements
  • A.4. Access Control Model Design Requirements

Editors' Addresses

Bert Wijnen
Lucent Technologies
Schagen 33
3461 GL Linschoten
Netherlands
Phone: +31 348-680-485
EMail: [email protected]

David Harrington
Enterasys Networks
Post Office Box 5005
35 Industrial Way
Rochester, New Hampshire 03866-5005
USA
Phone: +1 603-337-2614
EMail: [email protected]

Randy Presuhn
BMC Software, Inc.
2141 North First Street
San Jose, California 95131
USA
Phone: +1 408-546-1006
Fax: +1 408-965-0359
EMail: [email protected]

Full Copyright Statement

Copyright (C) The Internet Society (2002). All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

Funding for the RFC Editor function is currently provided by the Internet Society.