RFC 4789
Simple Network Management Protocol (SNMP) over IEEE 802 Networks
RFC 4789: Simple Network Management Protocol (SNMP) over IEEE 802 Networks ✨
Okay bestie, this is RFC 4789 💖 It's from the Network Working Group and was written by J. Schoenwaelder (International University Bremen) and T. Jeffree (Consultant). It's on the Standards Track and dates from November 2006 🎀 It obsoletes RFC 1089 and updates RFC 3417 🔥 So it replaces the old SNMP-over-Ethernet spec and adds to the standard SNMP transport mappings. Main character energy 👑
Status of This Memo
This document is an Internet standards track protocol for the Internet community, and it's asking for discussion and suggestions for improvements 🦋 For the standardization state and status of this protocol, check the current edition of the "Internet Official Protocol Standards" (STD 1). Distribution of this memo is unlimited 💅
Copyright Notice
Copyright (C) The IETF Trust (2006). 🌸
Abstract ✨
This document explains how Simple Network Management Protocol (SNMP) messages can be sent directly over IEEE 802 networks, no detour needed 🧚
This document obsoletes RFC 1089.
Table of Contents
1. Introduction ....................................................2
1.1. Key Words ..................................................2
2. Definitions .....................................................3
3. SNMP over IEEE 802 Networks .....................................4
3.1. Serialization ..............................................4
3.2. Well-known Values ..........................................4
3.3. IEEE 802.3 Frame Format ....................................5
4. Relationship to Other MIB Modules ...............................5
5. IANA Considerations .............................................6
6. Security Considerations .........................................6
7. Acknowledgments .................................................7
8. References ......................................................7
8.1. Normative References .......................................7
8.2. Informative References .....................................71. Introduction 🌈
So this doc is all about sending SNMP messages straight over IEEE 802 networks, and it's giving simple and direct ✨ If you want the big-picture tour of the Internet-Standard management framework, go read section 7 of RFC 3410 [RFC3410] 📚 This document adds to the standard SNMP transport mappings from RFC 3417 [RFC3417] 💜
Also, this obsoletes RFC 1089 🫶
Managed objects live in a virtual information store called the Management Information Base, or MIB 🗂️ MIB objects are usually reached through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined with the rules of the Structure of Management Information (SMI). This memo specifies a MIB module that works with SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580] 🍓
1.1. Key Words 🔑
Okay so the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document should be read as described in RFC 2119 [RFC2119] 🫶
2. Definitions 📜
Here's the MIB module, verbatim, because implementers need every character 🙈
SNMP-IEEE802-TM-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, snmpModules, snmpDomains
FROM SNMPv2-SMI;
snmpIeee802TmMib MODULE-IDENTITY
LAST-UPDATED "200611210000Z"
ORGANIZATION "IETF Operations and Management Area"
CONTACT-INFO
"Juergen Schoenwaelder (Editor)
International University Bremen
P.O. Box 750 561
28725 Bremen, Germany
Phone: +49 421 200-3587
EMail: j.schoenwaelder@iu-bremen.de
Send comments to <ietfmibs@ops.ietf.org>."
DESCRIPTION
"This MIB module defines the SNMP over IEEE 802
transport mapping.
Copyright (C) The IETF Trust (2006). This version
of this MIB module is part of RFC 4789; see the RFC
itself for full legal notices."
REVISION "200611210000Z"
DESCRIPTION
"The initial version, published as RFC 4789."
::= { snmpModules 21 }
snmpIeee802Domain OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The SNMP over IEEE 802 networks transport domain. The
corresponding transport address is of type MacAddress
as defined in the SNMPv2-TC module (RFC 2579)."
REFERENCE "RFC 2579"
::= { snmpDomains 6 }
END3. SNMP over IEEE 802 Networks 🚀
This transport mapping is optional, so use it if it fits your setup 🌸 The need to carry SNMP directly over an 802 LAN, so that simple devices can be managed, came up in things like the Two-Port Media Access Control (MAC) Relay, which IEEE 802.1 is building under project P802.1aj [802.1aj] 🧚
SNMP over IEEE 802 networks has some built-in limits, so read this part carefully 👀 Using this transport mapping keeps messages inside a single logical IEEE 802 LAN, bridged LAN or VLAN. On top of that, only one SNMP engine can be addressed on a given IEEE 802 network interface. Command generators and notification receivers, plus command responders and notification originators, all have to share one transport endpoint 🫶
3.1. Serialization 🧩
SNMP messages get serialized the way Section 8 of RFC 3417 [RFC3417] describes 💖 The serialized message then rides in the data portion of an IEEE LAN MAC frame 🎀
3.2. Well-known Values 💜
Serialized SNMP messages are sent in IEEE 802.3 frames with an Ethernet type field of 33100 (hexadecimal 814C) 🔥
When serialized SNMP messages go out in IEEE 802.3 frames (and in other IEEE 802 MAC frame types that can natively carry Ethernet type values), the Ethernet type field value MUST be 33100 (hexadecimal 814C) as the link layer protocol identifier. For IEEE 802 LANs that identify the link layer protocol with LLC, like IEEE 802.11 Wireless LANs, the SNAP encapsulation method from subclause 10.5 "Encapsulation of Ethernet frames over LLC" in [IEEE802] MUST be used. ⭐
When an SNMP entity uses this transport mapping, it MUST be able to accept SNMP messages up to and including 484 octets in size. It is RECOMMENDED that implementations can accept messages up to 1472 octets in size. Going bigger is encouraged whenever possible 🌈
3.3. IEEE 802.3 Frame Format 🖼️
Here's the frame layout. Each tic mark is one bit 🍓
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination |
+- -+
| Ethernet |
+- -+
| Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source |
+- -+
| Ethernet |
+- -+
| Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1 0 0 0 0 0 0 1 0 1 0 0 1 1 0 0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SNMP |
+- -+
/ message ... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
(Each tic mark represents one bit.)4. Relationship to Other MIB Modules 🔗
Several core SNMP MIB modules use TDomain/TAddress pairs to identify SNMP transport endpoints. The SNMP-TARGET-MIB [RFC3413] uses them to identify targets that can receive notifications. The NOTIFICATION-LOG-MIB [RFC3014] uses TDomain/TAddress pairs to record where a notification came from. The ENTITY-MIB [RFC4133] uses them to give the transport endpoint of logical entities 💅
The MIB module in this document introduces the object identifier constant snmpIeee802Domain. You can assign this constant to an object of type TDomain to mark an SNMP over IEEE 802 endpoint. In that case, the matching TAddress has a value that follows the MacAddress textual convention. Because of this, the generic MIB modules can refer to SNMP over IEEE 802 endpoints too 🦋
5. IANA Considerations 📋
IANA made a MIB OID assignment under the snmpModules branch for the SNMP-IEEE802-TM-MIB module 🌸
IANA also assigned an OID value below snmpDomains for the transport domain. Getting there first required setting up a registry for OIDs under snmpDomains. At the time of writing, these assignments already exist:
Prefix: iso.org.dod.internet.snmpv2.snmpDomains (1.3.6.1.6.1)
Decimal Name Description References
------- ---- ----------- ----------
1 snmpUDPDomain SNMP over UDP [RFC3417]
2 snmpCLNSDomain SNMP over CLNS [RFC3417]
3 snmpCONSDomain SNMP over CONS [RFC3417]
4 snmpDDPDomain SNMP over DDP [RFC3417]
5 snmpIPXDomain SNMP over IPX [RFC3417]The following assignment has been made:
Decimal Name Description References
------- ---- ----------- ----------
6 snmpIeee802Domain SNMP over IEEE 802 RFC 4789For new assignments, a specification is required as per [RFC2434] 🔥
6. Security Considerations 🔐
⚠️ Security is serious business, so read this section fully, bestie 💀
This module doesn't define any management objects. Instead, it defines an OBJECT-IDENTIFIER that other MIB modules can use to identify an SNMP transport mapping. Meaningful security considerations can only be written in the MIB modules that define management objects. So the MIB module in this document has no impact on the security of the Internet 🛡️
SNMPv1 and SNMPv2c messages are not considered secure 😭 It is recommended that implementors consider using SNMPv3 messages and the security features of the SNMPv3 framework. Specifically, the User-based Security Model STD 62, RFC 3414 [RFC3414] and the View-based Access Control Model STD 62, RFC 3415 [RFC3415] are recommended 🔒
It's then the customer or user's responsibility to make sure the SNMP entity that gives access to a MIB is configured properly. Access to the objects should only go to the principals (users) who really have the legitimate right to GET or SET (change) them. No unauthorized vibes allowed 🙅♀️
7. Acknowledgments 🫶
The original SNMP over Ethernet definition was written by Marty Schoffstall, Chuck Davin, Mark Fedor, and Jeff Case, and published as RFC 1089 [RFC1089] 🌟
Bert Wijnen and Dan Romascanu gave guidance on many parts of this revised specification. David Harrington left useful comments that made the presentation better 💜
8. References 📚
The reference list continues in part 2 🧚
8.1. Normative References 📚
okay so these are the docs this spec literally can't function without, bestie 💅
- [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
- [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
- [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
- [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
- [RFC3417] Presuhn, R., Ed., "Transport Mappings for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3417, December 2002.
- [IEEE802] "IEEE Standard for Local Area Networks: Overview and Architecture", IEEE Std. 802-2001.
- [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
8.2. Informative References 🌸
these ones are the extra reading. helpful, not required, but lowkey a must-read if you're curious 🧚
- [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
- [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network Management Protocol (SNMP) Applications", STD 62, RFC 3413, December 2002.
- [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
- [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3415, December 2002.
- [RFC3014] Kavasseri, R., "Notification Log MIB", RFC 3014, November 2000.
- [RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3)", RFC 4133, August 2005.
- [RFC1089] Schoffstall, M., Davin, C., Fedor, M., and J. Case, "SNMP over Ethernet", RFC 1089, February 1989.
- [802.1aj] P802.1aj/D1.4 Draft Standard for Local and Metropolitan Area Networks - Virtual Bridged Local Area Networks - Amendment 08: Two-Port Media Access Control (MAC) Relay, IEEE 802.1 Working Group, June 2006, Work in Progress.
Authors' Addresses 🎀
meet the people who wrote this, the OG squad 🫶
Juergen Schoenwaelder
International University Bremen
Campus Ring 1
28725 Bremen
Germany
Phone: +49 421 200-3587
EMail: j.schoenwaelder@iu-bremen.de
Tony Jeffree
Consultant
11a Poplar Grove
Sale, Cheshire, M33 3AX
United Kingdom
Phone: +44-161-973-4278
EMail: tony@jeffree.co.ukFull Copyright Statement ⚖️
Copyright (C) The IETF Trust (2006).
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST, AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
Intellectual Property 🔐
the IETF doesn't pick a side on whether any IP rights apply to the tech in here, or whether you can get a license for it. it also doesn't claim it went hunting for those rights itself. the rules for rights in RFC docs live in BCP 78 and BCP 79, so go check those if you need the tea ☕
copies of IPR disclosures sent to the IETF Secretariat, and any assurances of licenses, or the result of an attempt to get a general license or permission for implementers or users, can be found in the IETF's online IPR repository at http://www.ietf.org/ipr.
the IETF also invites anyone to flag any copyrights, patents, patent applications, or other proprietary rights that might cover technology needed to implement this standard. send that info to the IETF at ietf-ipr@ietf.org 📬
Acknowledgement 🌈
funding for the RFC Editor function is currently provided by the Internet Society. thank you, Internet Society 🫶✨
📦 where this page comes from
- ietf: rfc4789 2006-11
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms