RFC 1901

Introduction to Community-based SNMPv2

📅 published January 1996, from ietf

RFC 1901 · Part 1 of 2 💖

Okay bestie, let's start with the receipts 🧾 This is RFC 1901, titled Introduction to Community-based SNMPv2. It came from the SNMPv2 Working Group (part of the Network Working Group 🎀) in January 1996. It's an Experimental doc, so the category is Experimental. The authors are J. Case (SNMP Research, Inc.), K. McCloghrie (Cisco Systems, Inc.), M. Rose (Dover Beach Consulting, Inc.), and S. Waldbusser (International Network Services). The header doesn't list anything this one obsoletes or updates, so that spot is empty 🤷‍♀️.

Status of this Memo 📜

Okay so this is an Experimental protocol for the Internet community 🧪. It is not an Internet standard of any kind 🙅‍♀️. They're literally asking for discussion and suggestions for improvement, and distribution is unlimited 💌.

Table of Contents 🗂️

   1. Introduction ................................................    1
   2. Components of the SNMPv2 Framework ..........................    2
   2.1 Structure of Management Information ........................    2
   2.2 Textual Conventions ........................................    3
   2.3 Conformance Statements .....................................    3
   2.4 Protocol Operations ........................................    3
   2.5 Transport Mappings .........................................    4
   2.6 Protocol Instrumentation ...................................    4
   3. The Community-based Administrative Framework ................    4
   4. Security Considerations .....................................    5
   5. Editor's Address ............................................    6
   6. Acknowledgements ............................................    6
   7. References ..................................................    7

1. Introduction 🦋

The whole point of this doc is to define the Community-based Administrative Framework for the SNMP version 2 framework (SNMPv2). The SNMPv2 framework is fully described in [1-6]. It's derived from the original Internet-standard Network Management Framework (SNMPv1), which is made of these three documents:

STD 16, RFC 1155 [7] defines the Structure of Management Information (SMI), the mechanisms used for describing and naming objects for the purpose of management. 📐
STD 16, RFC 1212 [8] defines a more concise description mechanism, which is wholly consistent with the SMI. ✂️
STD 15, RFC 1157 [9] defines the Simple Network Management Protocol (SNMP), the protocol used for network access to managed objects. 🌐

For coexistence between SNMPv1 and SNMPv2, go check out [10] 👀.

2. Components of the SNMPv2 Framework 🧩

Okay so a management system has a bunch of pieces 💅. There are several (potentially many) nodes, and each one has a processing entity called an agent that can access management instrumentation. There's also at least one management station, plus a management protocol that carries management information between the agents and the stations. The protocol's operations run under an administrative framework that defines authentication, authorization, access control, and privacy policies 🔐.

Management stations run management applications that monitor and control managed elements. Managed elements are devices like hosts, routers, terminal servers, etc., and they get monitored and controlled through access to their management information 🖥️.

2.1. Structure of Management Information 🏗️

Management information is seen as a collection of managed objects, living in a virtual information store called the Management Information Base (MIB). Related objects get grouped into MIB modules, and those modules are written using a subset of OSI's Abstract Syntax Notation One (ASN.1) [11]. The Structure of Management Information for SNMPv2 document [1] is the one that defines that subset 📖.

The SMI has three parts: module definitions, object definitions, and trap definitions 🧱.

(1) Module definitions are used when describing information modules. An ASN.1 macro, MODULE-IDENTITY, is used to concisely convey the semantics of an information module.
(2) Object definitions are used when describing managed objects. An ASN.1 macro, OBJECT-TYPE, is used to concisely convey the syntax and semantics of a managed object.
(3) Notification definitions are used when describing unsolicited transmissions of management information. An ASN.1 macro, NOTIFICATION-TYPE, is used to concisely convey the syntax and semantics of a notification. 🔔

2.2. Textual Conventions 🎨

When you're designing a MIB module, it's super useful to define new types that look like the ones in the SMI. Compared to an SMI type, each new type has a different name and a similar syntax, but a more precise semantics 💜. These new types are called textual conventions, and they're there for the convenience of humans reading the MIB module. The Textual Conventions for SNMPv2 document [2] is where the initial set of textual conventions for all MIB modules is defined.

Objects defined with a textual convention are always encoded using the rules for their primitive type. But textual conventions often come with special semantics attached, so an ASN.1 macro, TEXTUAL-CONVENTION, is used to concisely convey the syntax and semantics of a textual convention ✨.

2.3. Conformance Statements 📏

It can be useful to define the acceptable lower bounds of an implementation, along with the level actually achieved. The Conformance Statements for SNMPv2 document [3] defines the notation for all of that. There are two kinds of notation:

(1) Compliance statements are used when describing requirements for agents with respect to object definitions. An ASN.1 macro, MODULE-COMPLIANCE, is used to concisely convey such requirements.
(2) Capability statements are used when describing capabilities of agents with respect to object definitions. An ASN.1 macro, AGENT-CAPABILITIES, is used to concisely convey such capabilities.

Last but not least, related objects get grouped into a unit of conformance. An ASN.1 macro, OBJECT-GROUP, is used to concisely convey the syntax and semantics of a group 🫶.

2.4. Protocol Operations 📬

The management protocol handles the exchange of messages that carry management information between the agents and the management stations. These messages are wrapped up in a message "wrapper" that encapsulates a Protocol Data Unit (PDU) 🎁.

The Protocol Operations for SNMPv2 document [4] defines the operations of the protocol, covering how PDUs are sent and received 📤📥.

2.5. Transport Mappings 🚚

The management protocol, version 2 of the Simple Network Management Protocol, can run over a bunch of different protocol suites 🌈. The Transport Mappings for SNMPv2 document [5] defines how SNMPv2 maps onto an initial set of transport domains, and other mappings may be defined in the future.

Even though several mappings are defined, the mapping onto UDP is the preferred mapping 💖. To get the greatest level of interoperability, systems that choose to deploy other mappings should also provide proxy service to the UDP mapping 🤝.

2.6. Protocol Instrumentation 🔧

The Management Information Base for SNMPv2 document [6] defines the managed objects that describe the behavior of an SNMPv2 entity. Those are the instruments that tell you how the entity is actually doing 📊.

⏭️ Part 2 picks up with Section 3 🦋✨

6. Acknowledgements ✨

okay so this doc is literally the result of so much work from four major contributors, and I need you to see their names 🫶

Jeffrey D. Case (SNMP Research, case@snmp.com)
Keith McCloghrie (Cisco Systems, kzm@cisco.com)
Marshall T. Rose (Dover Beach Consulting, mrose@dbc.mtview.ca.us)
Steven Waldbusser (International Network Services, stevew@uni.ins.com)

and the SNMPv2 Working Group gets a shoutout too 💜 the contributions of the group are acknowledged, and a really special thanks goes to these people:

Alexander I. Alten (Novell)
Dave Arneson (Cabletron)
Uri Blumenthal (IBM)
Doug Book (Chipcom)
Kim Curran (Bell-Northern Research)
Jim Galvin (Trusted Information Systems)
Maria Greene (Ascom Timeplex)
Iain Hanson (Digital)
Dave Harrington (Cabletron)
Nguyen Hien (IBM)
Jeff Johnson (Cisco Systems)
Michael Kornegay (Object Quest)
Deirdre Kostick (AT&T Bell Labs)
David Levi (SNMP Research)
Daniel Mahoney (Cabletron)
Bob Natale (ACE*COMM)
Brian O'Keefe (Hewlett Packard)
Andrew Pearson (SNMP Research)
Dave Perkins (Peer Networks)
Randy Presuhn (Peer Networks)
Aleksey Romanov (Quality Quorum)
Shawn Routhier (Epilogue)
Jon Saperia (BGS Systems)
Bob Stewart (Cisco Systems, bstewart@cisco.com), chair
Kaj Tesink (Bellcore)
Glenn Waters (Bell-Northern Research)
Bert Wijnen (IBM)

7. References 📚

the full reference list, bestie. every single one is here 🦋

[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996.
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1907, January 1996.
[7] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based internets", STD 16, RFC 1155, May 1990.
[8] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[9] Case, J., Fedor, M., Schoffstall, M., Davin, J., "Simple Network Management Protocol", STD 15, RFC 1157, SNMP Research, Performance Systems International, MIT Laboratory for Computer Science, May 1990.
[10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework", RFC 1908, January 1996.
[11] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization. International Standard 8824, (December, 1987).

that's the whole list, and every single one of these is what makes the SNMPv2 stack hold together 🌸✨

📦 where this page comes from

ietf: rfc1901 1996-01
💖 girlified by claude-haiku-5-5 on 2026-10-15: a language model's rewrite of the original, under its terms