Browse Prior Art Database

SNMP over OSI (RFC1418)

IP.com Disclosure Number: IPCOM000002244D
Original Publication Date: 1993-Mar-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 3 page(s) / 7K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Rose: AUTHOR

Abstract

The Simple Network Management Protocol (SNMP) as defined in [1] is now used as an integral part of the network management framework for TCP/IP-based internets. Together with its companions standards, which define the Structure of Management Information (SMI) [2,3], and the Management Information Base (MIB) [4], the SNMP has received widespread deployment in many operational networks running the Internet suite of protocols.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 41% of the total text.

Network Working Group M. Rose

Request for Comments: 1418 Dover Beach Consulting, Inc.

Obsoletes: 1161, 1283 March 1993

SNMP over OSI

Status of this Memo

This RFC specifies an IAB standards track protocol for the Internet

community, and requests discussion and suggestions for improvements.

Please refer to the current edition of the "IAB Official Protocol

Standards" for the standardization state and status of this protocol.

Distribution of this memo is unlimited.

Table of Contents

1. Background ................................................. 1

2. Mapping onto the CLTS ...................................... 2

2.1 Well-known Addresses ...................................... 2

2.2 Traps ..................................................... 2

2.3 Maximum Message Size ...................................... 3

3. Acknowledgements ........................................... 3

4. References ................................................. 3

5. Security Considerations .................................... 4

6. Author's Address ........................................... 4

1. Background

The Simple Network Management Protocol (SNMP) as defined in [1] is

now used as an integral part of the network management framework for

TCP/IP-based internets. Together with its companions standards,

which define the Structure of Management Information (SMI) [2,3], and

the Management Information Base (MIB) [4], the SNMP has received

widespread deployment in many operational networks running the

Internet suite of protocols.

It should not be surprising that many of these sites might acquire

OSI capabilities and may wish to leverage their investment in SNMP

technology towards managing those OSI components. This memo

addresses these concerns by defining a framework for running the SNMP

in an environment which supports the OSI connectionless-mode

transport service.

However, as noted in [5], the preferred mapping for SNMP is onto the

UDP [6]. This specification is intended for use in environments

where UDP transport is not available. No aspect of this

specification should be construed as a suggestion that, in a

heterogeneous transport environment, a managed agent should support

more than one mapping.

2. Mapping onto the CLTS

Mapping the SNMP onto the CLTS [7,8] is straight-forward. The

elements of procedure are identical to that of using the UDP. Note

that the CLTS and the service offered by the UDP both transmit

packets of information which contain full addressing information.

Thus, mapping the SNMP onto the CLTS, a "transport address" in the

context of [1], is simply a transport-selector and network address.

It should be noted that the mapping of SNMP onto a connectionless-

mode transport service is wholly consistent with SNMP's architectural

pri...