RFC 1449
Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2)
Part 1 of 4 🎀 more parts are coming, bestie!
RFC 1449: Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2) 💖
Okay so this is RFC 1449, dated April 1993 🌸. It was written by J. Case (SNMP Research, Inc.), K. McCloghrie (Hughes LAN Systems), M. Rose (Dover Beach Consulting, Inc.), and S. Waldbusser (Carnegie Mellon University) 🧚, all from the Network Working Group. Its category is an IAB standards track protocol ✨. The title block doesn't list either Obsoletes or Updates, so it doesn't change any other RFCs 🙈.
Status of This Memo 📜
This one specifies an IAB standards track protocol for the Internet community, and it asks for discussion and suggestions for improvements 💅. For the standardization state and status of this protocol, check the current edition of the "IAB Official Protocol Standards" 🔍. Distribution of this memo is unlimited 🦋.
Table of Contents 🌸
1 Introduction .......................................... 2
1.1 A Note on Terminology ............................... 2
2 Definitions ........................................... 3
3 SNMPv2 over UDP ....................................... 7
3.1 Serialization ....................................... 7
3.2 Well-known Values ................................... 7
4 SNMPv2 over OSI ....................................... 8
4.1 Serialization ....................................... 8
4.2 Well-known Values ................................... 8
5 SNMPv2 over DDP ....................................... 9
5.1 Serialization ....................................... 9
5.2 Well-known Values ................................... 9
5.3 Discussion of AppleTalk Addressing .................. 9
5.3.1 How to Acquire NBP names .......................... 10
5.3.2 When to Turn NBP names into DDP addresses ......... 11
5.3.3 How to Turn NBP names into DDP addresses .......... 11
5.3.4 What if NBP is broken ............................. 12
6 SNMPv2 over IPX ....................................... 13
6.1 Serialization ....................................... 13
6.2 Well-known Values ................................... 13
7 Proxy to SNMPv1 ....................................... 14
7.1 Transport Domain: rfc1157Domain ..................... 14
7.2 Authentication Algorithm: rfc1157noAuth ............. 14
8 Serialization using the Basic Encoding Rules .......... 16
8.1 Usage Example ....................................... 17
9 Acknowledgements ...................................... 18
10 References ........................................... 22
11 Security Considerations .............................. 24
12 Authors' Addresses ................................... 24
13 Security Considerations .............................. 25
14 Authors' Addresses ................................... 251. Introduction 🦋
A network management system is made up of several (potentially many) nodes, each with a processing entity called an agent that can reach management instrumentation 🫶. It also has at least one management station 👑, plus a management protocol that carries management information between the agents and the stations 💌. The protocol runs under an administrative framework that defines both authentication and authorization policies 🔐.
Network management stations run management applications that monitor and control network elements ✨. Network elements are things like hosts, routers, terminal servers, etc., and they get monitored and controlled through access to their management information 💻.
The management protocol, version 2 of the Simple Network Management Protocol [1], may be used over a variety of protocol suites 🌈. This document defines how SNMPv2 maps onto an initial set of transport domains 🧚. Other mappings may be defined in the future 🔮.
Although several mappings are defined, the mapping onto UDP is the preferred one 💖. For the greatest interoperability, systems that choose to deploy other mappings SHOULD also provide proxy service to the UDP mapping 🫶.
1.1. A Note on Terminology 📖
For the purpose of exposition, the original Internet-standard Network Management Framework, described in RFCs 1155, 1157, and 1212, is called the SNMP version 1 framework (SNMPv1) 🕰️. The current framework is called the SNMP version 2 framework (SNMPv2) 🆕.
2. Definitions ✨
Here's the whole SNMPv2-TM module, straight from the source 💅:
SNMPv2-TM DEFINITIONS ::= BEGIN
IMPORTS
snmpDomains, snmpProxys
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
-- SNMPv2 over UDP
snmpUDPDomain OBJECT IDENTIFIER ::= { snmpDomains 1 }
-- for a SnmpUDPAddress of length 6:
--
-- octets contents encoding
-- 1-4 IP-address network-byte order
-- 5-6 UDP-port network-byte order
--
SnmpUDPAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d/2d"
STATUS current
DESCRIPTION
"Represents a UDP address."
SYNTAX OCTET STRING (SIZE (6))
-- SNMPv2 over OSI
snmpCLNSDomain OBJECT IDENTIFIER ::= { snmpDomains 2 }
snmpCONSDomain OBJECT IDENTIFIER ::= { snmpDomains 3 }
-- for a SnmpOSIAddress of length m:
--
-- octets contents encoding
-- 1 length of NSAP "n" as an unsigned-integer
-- (either 0 or from 3 to 20)
-- 2..(n+1) NSAP concrete binary representation
-- (n+2)..m TSEL string of (up to 64) octets
--
SnmpOSIAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "*1x:/1x:"
STATUS current
DESCRIPTION
"Represents an OSI transport-address."
SYNTAX OCTET STRING (SIZE (1 | 4..85))
-- SNMPv2 over DDP
snmpDDPDomain OBJECT IDENTIFIER ::= { snmpDomains 4 }
-- for a SnmpNBPAddress of length m:
--
-- octets contents encoding
-- 1 length of object "n" as an unsigned integer
-- 2..(n+1) object string of (up to 32) octets
-- n+2 length of type "p" as an unsigned integer
-- (n+3)..(n+2+p) type string of (up to 32) octets
-- n+3+p length of zone "q" as an unsigned integer
-- (n+4+p)..m zone string of (up to 32) octets
--
-- for comparison purposes, strings are case-insensitive
--
-- all strings may contain any octet other than 255 (hex ff)
--
SnmpNBPAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents an NBP name."
SYNTAX OCTET STRING (SIZE (3..99))
-- SNMPv2 over IPX
snmpIPXDomain OBJECT IDENTIFIER ::= { snmpDomains 5 }
-- for a SnmpIPXAddress of length 12:
--
-- octets contents encoding
-- 1-4 network-number network-byte order
-- 5-10 physical-address network-byte order
-- 11-12 socket-number network-byte order
--
SnmpIPXAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "4x.1x:1x:1x:1x:1x:1x.2d"
STATUS current
DESCRIPTION
"Represents an IPX address."
SYNTAX OCTET STRING (SIZE (12))
-- for proxy to community-based SNMPv1 (RFC 1157)
rfc1157Proxy OBJECT IDENTIFIER ::= { snmpProxys 1 }
-- uses SnmpUDPAddress
rfc1157Domain OBJECT IDENTIFIER ::= { rfc1157Proxy 1 }
-- the community-based noAuth
rfc1157noAuth OBJECT IDENTIFIER ::= { rfc1157Proxy 2 }
END3. SNMPv2 over UDP 💌
This is the preferred transport mapping 👑.
3.1. Serialization 📦
Each instance of a message gets serialized onto a single UDP[2] datagram, using the algorithm specified in Section 8 🧩.
3.2. Well-known Values 🍓
The partyTable gives transport addressing info for an SNMPv2 party, but it's suggested that admins configure their SNMPv2 entities acting in an agent role to listen on UDP port 161 🎯. It's also suggested that notification sinks get configured to listen on UDP port 162 🔔.
The partyTable also lists the maximum message size that an SNMPv2 party is willing to accept. This value MUST be at least 484 octets 🚨. Implementing larger values is encouraged whenever possible 🌟.
5. SNMPv2 over DDP 🦋
okay so this one is an optional transport mapping, which means you don't have to build it 💅
5.1. Serialization
every instance of a message gets serialized onto one single DDP datagram [5], using the algorithm from Section 8 ✨
5.2. Well-known Values
SNMPv2 messages get sent using DDP protocol type 8 💖. SNMPv2 entities acting in an agent role listen on DDP socket number 8, while notification sinks listen on DDP socket number 9 🌸.
so the partyTable does give transport addressing info for an SNMPv2 party, but administrators still have to configure their agent-role entities to use the NBP type "SNMP Agent" (that's ten ASCII characters, bestie 🔢). notification sinks must be configured to use the NBP type "SNMP Trap Handler" (seventeen ASCII characters 🧚).
the NBP name for agents and notification sinks should be stable. NBP names should not change any more often than the IP address of a typical TCP/IP node 🫶. it is suggested that the NBP name be stored in some form of stable storage 💜.
the partyTable also lists the maximum message size that an SNMPv2 party is willing to accept. this value must be at least 484 octets. implementing larger values is encouraged whenever possible 🎀.
5.3. Discussion of AppleTalk Addressing
the AppleTalk protocol suite has some features that just don't show up in TCP/IP 🍓. AppleTalk's naming strategy and its dynamic address assignment can cause problems for SNMPv2 entities that want to manage AppleTalk networks 😭. TCP/IP nodes each have an IP address that tells them apart from one another. AppleTalk nodes usually don't have anything like that. the network-level address might be pretty stable, but it can change at every reboot (or even more often) 🙈.
so when SNMPv2 gets mapped over DDP, nodes are identified by a "name" instead of an "address" 🦋. that means all AppleTalk nodes that implement this mapping are required to respond to NBP lookups and confirms (e.g., implement the NBP protocol stub). that's what guarantees a mapping from NBP name to DDP address will be possible 👑.
when figuring out the SNMP identity to register for an SNMPv2 entity, it is suggested that the SNMP identity be a name that's associated with other network services the machine offers ✨.
NBP lookups, which map NBP names into DDP addresses, can cause a lot of network traffic and eat up CPU resources 💀. they're also sensitive to certain network disruptions (like zone table inconsistencies) that wouldn't stop two SNMPv2 entities from talking directly over AppleTalk 🔥.
so it is recommended that NBP lookups be used infrequently, mainly to build a cache of name-to-address mappings. those cached mappings should then be used for any further SNMP traffic 🌈. it is recommended that SNMPv2 entities acting in a manager role maintain this cache between reboots. this caching can help cut down on network traffic, lighten the CPU load on the network, and allow for (some amount of) trouble shooting when the basic name-to-address translation mechanism is broken 🫶.
5.3.1. How to Acquire NBP names
an SNMPv2 entity acting in a manager role might have a pre-configured list of names of "known" SNMPv2 entities acting in an agent role 📝. it might also interact with an operator 🧑💻. and finally, it might communicate with all SNMPv2 entities acting in an agent role across a set of zones or networks 🌸.
5.3.2. When to Turn NBP names into DDP addresses
when an SNMPv2 entity uses a cache entry to address an SNMP packet, it should try to confirm the mapping is still valid, if the mapping hasn't been confirmed within the last T1 seconds ⏰. this cache entry lifetime, T1, has a minimum default value of 60 seconds, and it should be configurable 💅.
an SNMPv2 entity acting in a manager role may decide to prime its cache of names before it actually talks to another SNMPv2 entity 🎀. generally, that entity might want to keep certain mappings "more current" than others. for example, nodes that represent the network infrastructure (like routers) might be deemed "more important" 👑.
heads up, though: an SNMPv2 entity acting in a manager role should not prime its entire cache upon initialization 🙅♀️. instead, it should attempt resolutions over an extended period of time (maybe in some pre-determined or configured priority order). each of these resolutions might actually be a wildcard lookup in a given zone 🦋.
an SNMPv2 entity acting in an agent role must never prime its cache 🚫. it should only do NBP lookups (or confirms) when it needs to send an SNMP trap 🔔. when generating a response, it does not need to confirm a cache entry ✨.
5.3.3. How to Turn NBP names into DDP addresses
if the only info available is the NBP name, then an NBP lookup should be performed to turn that name into a DDP address 🔍. but if there's a piece of stale information, it can be used as a hint for an NBP confirm. that sends a unicast to the network address that's presumed to be the target of the name lookup, to see whether the stale information is still valid 💖.
an NBP name to DDP address mapping can also be confirmed implicitly, using only SNMP transactions 🧚. for example, an SNMPv2 entity acting in a manager role that's issuing a retrieval operation could also retrieve the relevant objects from the NBP group [6] for the SNMPv2 entity acting in an agent role 🌸.
that information can then be correlated with the source DDP address of the response 🫶.
5.3.4. What if NBP is broken
sometimes there's connectivity between two SNMPv2 entities, but the NBP mapping machinery is broken anyway 😭. for example:
- the NBP
FwdReq(forward NBP lookup onto local attached network) mechanism might be broken at a router on the other entity's network; or, - the NBP
BrRq(NBP broadcast request) mechanism might be broken at a router on the entity's own network; or, - NBP might be broken on the other entity's node.
an SNMPv2 entity acting in a manager role that's dedicated to AppleTalk management might choose to work around some of these failures by directly implementing the router portion of NBP 🛠️. for example, that entity might already know all the zones on the AppleTalk internet, and the networks on which each zone appears 🗺️. given an NBP lookup that fails, the entity could send an NBP FwdReq to the network where the agent was last located. if that fails too, the station could send an NBP LkUp (NBP lookup packet) as a directed (DDP) multicast to each network number on that network 👑. of the single failures above, this combined approach solves the case where either the local router's BrRq-to-FwdReq mechanism is broken, or the remote router's FwdReq-to-LkUp mechanism is broken 🎀.
6. SNMPv2 over IPX 🌈
this is an optional transport mapping too, so no pressure 🫶.
6.1. Serialization
each instance of a message gets serialized onto a single IPX datagram [7], using the algorithm from Section 8 ✨.
6.2. Well-known Values
SNMPv2 messages get sent using IPX packet type 4 (i.e., Packet Exchange Packet) 💅.
even though the partyTable gives transport addressing info for an SNMPv2 party, it is suggested that administrators configure their agent-role entities to listen on IPX socket 36879 (900f hexadecimal) 🦋. it is further suggested that notification sinks be configured to listen on IPX socket 36880 (9010 hexadecimal).
the partyTable also lists the maximum message size that an SNMPv2 party is willing to accept. this value must be at least 546 octets. implementing larger values is encouraged whenever possible 🍓.
7. Proxy to SNMPv1 🧚
so to provide proxy to community-based SNMP [8], we need some definitions for both transport domains and authentication protocols 👑.
7.1. Transport Domain: rfc1157Domain
the transport domain rfc1157Domain tells you the transport mapping for community-based SNMP messages defined in RFC 1157 💖. when a party's transport domain (partyTDomain) is rfc1157Domain:
- the party's transport address (
partyTAddress) shall be 6 octets long. the first 4 octets hold the IP-address in network-byte order, and the last two octets hold the UDP port in network-byte order; and, - the party's authentication protocol (
partyAuthProtocol) shall berfc1157noAuth.
when a proxy relationship identifies a proxy destination party that has rfc1157Domain as its transport domain:
- the proxy source party (
contextSrcPartyIndex) and proxy context (contextProxyContext) components of the proxy relationship are irrelevant; and, - Section 3.1 of [9] specifies the behavior of the proxy agent 🌸.
7.2. Authentication Algorithm: rfc1157noAuth
a party's authentication protocol (partyAuthProtocol) says which protocol and mechanism the party uses to authenticate the integrity and origin of the SNMPv1 or SNMPv2 PDUs it generates 🔐. when a party's authentication protocol is rfc1157noAuth:
- the party's public authentication key (
partyAuthPublic), clock (partyAuthClock), and lifetime (partyAuthLifetime) are irrelevant; and, - the party's private authentication key (
partySecretsAuthPrivate) shall be used as the 1157 community for the proxy destination, and shall be at least one octet in length. (no maximum length is specified.) 🫶
note that when setting the party's private authentication key, the exclusive-OR semantics specified in [10] still apply ✨.
8. Serialization using the Basic Encoding Rules ✨
okay bestie, when you serialize with the Basic Encoding Rules [11] 💅 there are three big rules you need to know:
(1) When encoding the length field, only the definite form is used; use of the indefinite form encoding is prohibited. Note that when using the definite-long form, it is permissible to use more than the minimum number of length octets necessary to encode the length field. 🎀
(2) When encoding the value field, the primitive form SHALL be used for all simple types, i.e., INTEGER, OCTET STRING, OBJECT IDENTIFIER, and BIT STRING (either IMPLICIT or explicit). The constructed form of encoding SHALL be used only for structured types, i.e., a SEQUENCE or an IMPLICIT SEQUENCE. 🧚
(3) When a BIT STRING is serialized, all named-bits are transferred regardless of their truth-value. Further, if the number of named-bits is not an integral multiple of eight, then the fewest number of additional zero-valued bits are transferred so that an integral multiple of eight bits is transferred. 🍓
These restrictions apply to all aspects of ASN.1 encoding, including the message wrappers, protocol data units, and the data objects they contain. So literally everything in the message gets the same treatment 👑
8.1. Usage Example 🦋
okay, let's see this in action! Suppose one wanted to encode an instance of the GetBulkRequest-PDU [1]:
[5] IMPLICIT SEQUENCE {
request-id 1414684022,
non-repeaters 1,
max-repetitions 2,
variable-bindings {
{ name sysUpTime,
value { unspecified NULL } },
{ name ipNetToMediaPhysAddress,
value { unspecified NULL } },
{ name ipNetToMediaType,
value { unspecified NULL } }
}
}Applying the BER, this would be encoded (in hexadecimal) as:
[5] IMPLICIT SEQUENCE a5 82 00 39
INTEGER 02 04 52 54 5d 76
INTEGER 02 01 01
INTEGER 02 01 02
SEQUENCE 30 2b
SEQUENCE 30 0b
OBJECT IDENTIFIER 06 07 2b 06 01 02 01 01 03
NULL 05 00
SEQUENCE 30 0d
OBJECT IDENTIFIER 06 09 2b 06 01 02 01 04 16 01 02
NULL 05 00
SEQUENCE 30 0d
OBJECT IDENTIFIER 06 09 2b 06 01 02 01 04 16 01 04
NULL 05 00Note that the initial SEQUENCE is not encoded using the minimum number of length octets. (The first octet of the length, 82, indicates that the length of the content is encoded in the next two octets.) 🙈
9. Acknowledgements 🫶
The UDP-based mapping is based, in part, on RFC 1157.
The OSI-based mapping is based, in part, on RFC 1283.
The DDP-based mapping is based, in part, on earlier work by Greg Minshall of Novell, Inc., and Mike Ritter of Apple Computer, Inc.
The IPX-based mapping is based, in part, on RFC 1298.
The section on proxy to community-based SNMP is based on earlier work that was based in part on a suggestion by Jonathan Biggar of Netlabs, Inc.
Finally, the comments of the SNMP version 2 working group are gratefully acknowledged, and the whole crew deserves a huge shoutout 🌈💜
Beth Adams, Network Management Forum
Steve Alexander, INTERACTIVE Systems Corporation
David Arneson, Cabletron Systems
Toshiya Asaba
Fred Baker, ACC
Jim Barnes, Xylogics, Inc.
Brian Bataille
Andy Bierman, SynOptics Communications, Inc.
Uri Blumenthal, IBM Corporation
Fred Bohle, Interlink
Jack Brown
Theodore Brunner, Bellcore
Stephen F. Bush, GE Information Services
Jeffrey D. Case, University of Tennessee, Knoxville
John Chang, IBM Corporation
Szusin Chen, Sun Microsystems
Robert Ching
Chris Chiotasso, Ungermann-Bass
Bobby A. Clay, NASA/Boeing
John Cooke, Chipcom
Tracy Cox, Bellcore
Juan Cruz, Datability, Inc.
David Cullerot, Cabletron Systems
Cathy Cunningham, Microcom
James R. (Chuck) Davin, Bellcore
Michael Davis, Clearpoint
Mike Davison, FiberCom
Cynthia DellaTorre, MITRE
Taso N. Devetzis, Bellcore
Manual Diaz, DAVID Systems, Inc.
Jon Dreyer, Sun Microsystems
David Engel, Optical Data Systems
Mike Erlinger, Lexcel
Roger Fajman, NIH
Daniel Fauvarque, Sun Microsystems
Karen Frisa, CMU
Shari Galitzer, MITRE
Shawn Gallagher, Digital Equipment Corporation
Richard Graveman, Bellcore
Maria Greene, Xyplex, Inc.
Michel Guittet, Apple
Robert Gutierrez, NASA
Bill Hagerty, Cabletron Systems
Gary W. Haney, Martin Marietta Energy Systems
Patrick Hanil, Nokia Telecommunications
Matt Hecht, SNMP Research, Inc.
Edward A. Heiner, Jr., Synernetics Inc.
Susan E. Hicks, Martin Marietta Energy Systems
Geral Holzhauer, Apple
John Hopprich, DAVID Systems, Inc.
Jeff Hughes, Hewlett-Packard
Robin Iddon, Axon Networks, Inc.
David Itusak
Kevin M. Jackson, Concord Communications, Inc.
Ole J. Jacobsen, Interop Company
Ronald Jacoby, Silicon Graphics, Inc.
Satish Joshi, SynOptics Communications, Inc.
Frank Kastenholz, FTP Software
Mark Kepke, Hewlett-Packard
Ken Key, SNMP Research, Inc.
Zbiginew Kielczewski, Eicon
Jongyeoi Kim
Andrew Knutsen, The Santa Cruz Operation
Michael L. Kornegay, VisiSoft
Deirdre C. Kostik, Bellcore
Cheryl Krupczak, Georgia Tech
Mark S. Lewis, Telebit
David Lin
David Lindemulder, AT&T/NCR
Ben Lisowski, Sprint
David Liu, Bell-Northern Research
John Lunny, The Wollongong Group
Robert C. Lushbaugh Martin, Marietta Energy Systems
Michael Luufer, BBN
Carl Madison, Star-Tek, Inc.
Keith McCloghrie, Hughes LAN Systems
Evan McGinnis, 3Com Corporation
Bill McKenzie, IBM Corporation
Donna McMaster, SynOptics Communications, Inc.
John Medicke, IBM Corporation
Doug Miller, Telebit
Dave Minnich, FiberCom
Mohammad Mirhakkak, MITRE
Rohit Mital, Protools
George Mouradian, AT&T Bell Labs
Patrick Mullaney, Cabletron Systems
Dan Myers, 3Com Corporation
Rina Nathaniel, Rad Network Devices Ltd.
Hien V. Nguyen, Sprint
Mo Nikain
Tom Nisbet
William B. Norton, MERIT
Steve Onishi, Wellfleet Communications, Inc.
David T. Perkins, SynOptics Communications, Inc.
Carl Powell, BBN
Ilan Raab, SynOptics Communications, Inc.
Richard Ramons, AT&T
Venkat D. Rangan, Metric Network Systems, Inc.
Louise Reingold, Sprint
Sam Roberts, Farallon Computing, Inc.
Kary Robertson, Concord Communications, Inc.
Dan Romascanu, Lannet Data Communications Ltd.
Marshall T. Rose, Dover Beach Consulting, Inc.
Shawn A. Routhier, Epilogue Technology Corporation
Chris Rozman
Asaf Rubissa, Fibronics
Jon Saperia, Digital Equipment Corporation
Michael Sapich
Mike Scanlon, Interlan
Sam Schaen, MITRE
John Seligson, Ultra Network Technologies
Paul A. Serice, Corporation for Open Systems
Chris Shaw, Banyan Systems
Timon Sloane
Robert Snyder, Cisco Systems
Joo Young Song
Roy Spitier, Sprint
Einar Stefferud, Network Management Associates
John Stephens, Cayman Systems, Inc.
Robert L. Stewart, Xyplex, Inc. (chair)
Kaj Tesink, Bellcore
Dean Throop, Data General
Ahmet Tuncay, France Telecom-CNET
Maurice Turcotte, Racal Datacom
Warren Vik, INTERACTIVE Systems Corporation
Yannis Viniotis
Steven L. Waldbusser, Carnegie Mellon Universitty
Timothy M. Walden, ACC
Alice Wang, Sun Microsystems
James Watt, Newbridge
Luanne Waul, Timeplex
Donald E. Westlake III, Digital Equipment Corporation
Gerry White
Bert Wijnen, IBM Corporation
Peter Wilson, 3Com Corporation
Steven Wong, Digital Equipment Corporation
Randy Worzella, IBM Corporation
Daniel Woycke, MITRE
Honda Wu
Jeff Yarnell, Protools
Chris Young, Cabletron
Kiho Yum, 3Com Corporation10. References 📚
okay bestie, this is the reading list 🤓 every source the spec leans on is here, so you can go check anything that feels sus. the wild part is how old some of these are. the oldest is from 1980 🦕
[1] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1448, SNMP Research, Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon University, April 1993. 💖
[2] Postel, J., "User Datagram Protocol", STD 6, RFC 768, USC/Information Sciences Institute, August 1980. 🌸
[3] Information processing systems - Open Systems Interconnection - Transport Service Definition, International Organization for Standardization. International Standard 8072, (June, 1986). ✨
[4] Information processing systems - Open Systems Interconnection - Transport Service Definition - Addendum 1: Connectionless-mode Transmission, International Organization for Standardization. International Standard 8072/AD 1, (December, 1986). 🦋
[5] G. Sidhu, R. Andrews, A. Oppenheimer, Inside AppleTalk (second edition). Addison-Wesley, 1990. 🍎
[6] Waldbusser, S., "AppleTalk Management Information Base", RFC 1243, Carnegie Mellon University, July 1991. 🧚
[7] Network System Technical Interface Overview. Novell, Inc, (June, 1989). 💜
[8] 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. 🔥
[9] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework", RFC 1452, SNMP Research, Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon University, April 1993. 🫶
[10] McCloghrie, K., and Galvin, J., "Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1447, Hughes LAN Systems, Trusted Information Systems, April 1993. 🎀
[11] Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1), International Organization for Standardization. International Standard 8825, (December, 1987). 👑
11. Security Considerations 🔒
okay this one is short but it is serious, bestie 💀 the memo just says: security issues are not discussed in this memo. so the spec itself doesn't cover security at all. 🙈 don't go assuming anything extra is handled here, because it literally isn't.
12. Authors' Addresses 🎀
these are the four people who wrote the thing, plus where to reach them. the girlies behind SNMPv2 framing, no cap 💅
Jeffrey D. Case
SNMP Research, Inc.
3001 Kimberlin Heights Rd.
Knoxville, TN 37920-9716
US
Phone: +1 615 573 1434
Email: case@snmp.com
Keith McCloghrie
Hughes LAN Systems
1225 Charleston Road
Mountain View, CA 94043
US
Phone: +1 415 966 7934
Email: kzm@hls.com
Marshall T. Rose
Dover Beach Consulting, Inc.
420 Whisman Court
Mountain View, CA 94043-2186
US
Phone: +1 415 968 1052
Email: mrose@dbc.mtview.ca.us
Steven Waldbusser
Carnegie Mellon University
4910 Forbes Ave
Pittsburgh, PA 15213
US
Phone: +1 412 268 6628
Email: waldbusser@cmu.eduthat's the whole doc, bestie! 🌈✨ you made it through all four parts 🫶💖
📦 where this page comes from
- ietf: rfc1449 1993-04
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms