Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)
RFC 1906
Document | Type |
RFC - Draft Standard
(January 1996; No errata)
Obsoleted by RFC 3417
Obsoletes RFC 1449
|
|
---|---|---|---|
Authors | Jeff Case , Keith McCloghrie , Marshall Rose , Steven Waldbusser | ||
Last updated | 2013-03-02 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 1906 (Draft Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group SNMPv2 Working Group Request for Comments: 1906 J. Case Obsoletes: 1449 SNMP Research, Inc. Category: Standards Track K. McCloghrie Cisco Systems, Inc. M. Rose Dover Beach Consulting, Inc. S. Waldbusser International Network Services January 1996 Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2) 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. Table of Contents 1. Introduction ................................................ 2 1.1 A Note on Terminology ...................................... 2 2. Definitions ................................................. 3 3. SNMPv2 over UDP ............................................. 5 3.1 Serialization .............................................. 5 3.2 Well-known Values .......................................... 5 4. SNMPv2 over OSI ............................................. 6 4.1 Serialization .............................................. 6 4.2 Well-known Values .......................................... 6 5. SNMPv2 over DDP ............................................. 6 5.1 Serialization .............................................. 6 5.2 Well-known Values .......................................... 6 5.3 Discussion of AppleTalk Addressing ......................... 7 5.3.1 How to Acquire NBP names ................................. 8 5.3.2 When to Turn NBP names into DDP addresses ................ 8 5.3.3 How to Turn NBP names into DDP addresses ................. 8 5.3.4 What if NBP is broken .................................... 9 6. SNMPv2 over IPX ............................................. 9 6.1 Serialization .............................................. 9 6.2 Well-known Values .......................................... 9 7. Proxy to SNMPv1 ............................................. 10 8. Serialization using the Basic Encoding Rules ................ 10 8.1 Usage Example .............................................. 11 SNMPv2 Working Group Standards Track [Page 1] RFC 1906 Transport Mappings for SNMPv2 January 1996 9. Security Considerations ..................................... 11 10. Editor's Address ........................................... 12 11. Acknowledgements ........................................... 12 12. References ................................................. 13 1. Introduction A management system contains: several (potentially many) nodes, each with a processing entity, termed an agent, which has access to management instrumentation; at least one management station; and, a management protocol, used to convey management information between the agents and management stations. Operations of the protocol are carried out under an administrative framework which defines authentication, authorization, access control, and privacy policies. Management stations execute management applications which monitor and control managed elements. Managed elements are devices such as hosts, routers, terminal servers, etc., which are monitored and controlled via 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. It is the purpose of this document to define how the 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 mapping. As such, to provide for the greatest level of interoperability, systems which choose to deploy other mappings should also provide for proxy service to the UDP mapping. 1.1. A Note on Terminology For the purpose of exposition, the original Internet-standard Network Management Framework, as described in RFCs 1155 (STD 16), 1157 (STD 15), and 1212 (STD 16), is termed the SNMP version 1 framework (SNMPv1). The current framework is termed the SNMP version 2Show full document text