SNMP over OSI

Network Working Group                                           M. Rose
Request for Comments: 1418                 Dover Beach Consulting, Inc.
Obsoletes: <a href="./rfc1161">1161</a>, <a href="./rfc1283">1283</a>                                        March 1993


                             <span class="h1">SNMP over OSI</span>

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

   <a href="#section-1">1</a>. Background .................................................    <a href="#page-1">1</a>
   <a href="#section-2">2</a>. Mapping onto the CLTS ......................................    <a href="#page-2">2</a>
   <a href="#section-2.1">2.1</a> Well-known Addresses ......................................    <a href="#page-2">2</a>
   <a href="#section-2.2">2.2</a> Traps .....................................................    <a href="#page-2">2</a>
   <a href="#section-2.3">2.3</a> Maximum Message Size ......................................    <a href="#page-3">3</a>
   <a href="#section-3">3</a>. Acknowledgements ...........................................    <a href="#page-3">3</a>
   <a href="#section-4">4</a>. References .................................................    <a href="#page-3">3</a>
   <a href="#section-5">5</a>. Security Considerations ....................................    <a href="#page-4">4</a>
   <a href="#section-6">6</a>. Author's Address ...........................................    <a href="#page-4">4</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Background</span>

   The Simple Network Management Protocol (SNMP) as defined in [<a href="#ref-1" title=""Simple Network Management Protocol"">1</a>] 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) [<a href="#ref-2" title=""Structure and Identification of Management Information for TCP/IP-based internets"">2</a>,<a href="#ref-3" title=""Concise MIB Definitions"">3</a>], and
   the Management Information Base (MIB) [<a href="#ref-4" title=""Management Information Base for Network Management of TCP/IP-based Internets"">4</a>], 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 [<a href="#ref-5" title=""SNMP Communications Services"">5</a>], the preferred mapping for SNMP is onto the
   UDP [<a href="#ref-6" title=""User Datagram Protocol"">6</a>].  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



<span class="grey">Rose                                                            [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc1418">RFC 1418</a>                     SNMP over OSI                    March 1993</span>


   heterogeneous transport environment, a managed agent should support
   more than one mapping.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Mapping onto the CLTS</span>

   Mapping the SNMP onto the CLTS [<a href="#ref-7" title="International Organization for Standardization. International Standard 8072/AD 1">7</a>,<a href="#ref-8" title="International Organization for Standardization. International Standard 8602">8</a>] 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 [<a href="#ref-1" title=""Simple Network Management Protocol"">1</a>], 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
   principles, as described in [<a href="#ref-1" title=""Simple Network Management Protocol"">1</a>,<a href="#ref-5" title=""SNMP Communications Services"">5</a>].  However, the CLTS itself can be
   realized using either a connectionless-mode or a connection-oriented
   network service.  The mapping described in this mapping allows for
   either realization.  (When both network services are available, the
   CLNS should be used as the basis of realization.)

<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>.  Well-known Addresses</span>

   Unlike the Internet suite of protocols, OSI does not use well-known
   ports.  Rather,
    demultiplexing occurs on the basis of "selectors", opaque strings of
   octets which have local significance.  In order to foster
   interoperable implementations of the SNMP over the CLTS, it is
   necessary define four selectors for this purpose.

   When the CLTS is used to provide the transport backing for the SNMP,
   and the CLTS uses a connectionless-mode network service, then
   transport selector used shall be "snmp-l" which consists of six ASCII
   characters; and, SNMP traps are, by convention, sent to an SNMP
   manager listening on the transport selector "snmpt-l" which consists
   of seven ASCII characters.

   When the CLTS is used to provide the transport backing for the SNMP,
   and the CLTS uses a connection-oriented network service, then
   transport selector used shall be "snmp-o" which consists of six ASCII
   characters; and, SNMP traps are, by convention, sent to an SNMP
   manager listening on the transport selector "snmpt-o" which consists
   of seven ASCII characters.

<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>.  Traps</span>

   When SNMP traps are sent over the CLTS, the agent-addr field in the
   Trap-PDU contains the IP-address "0.0.0.0" An SNMP manager may
   ascertain the source of the trap based on information provided by the



<span class="grey">Rose                                                            [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc1418">RFC 1418</a>                     SNMP over OSI                    March 1993</span>


   transport service (i.e., from the T-UNIT-DATA.INDICATION primitive).

<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>.  Maximum Message Size</span>

   An entity implementing SNMP over OSI must be prepared to accept
   messages whose size is at least 484 octets.  Implementation of larger
   values is encouraged whenever possible.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Acknowledgements</span>

   This specification was derived from <a href="./rfc1283">RFC 1283</a>, based on discussions in
   the IETF's "SNMP in a Multi-Protocol Internet" working group.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  References</span>

   [<a id="ref-1">1</a>] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
       Network Management Protocol", STD 15, <a href="./rfc1157">RFC 1157</a>, SNMP Research,
       Performance Systems International, Performance Systems
       International, MIT Laboratory for Computer Science, May 1990.

   [<a id="ref-2">2</a>] Rose M., and K. McCloghrie, "Structure and Identification of
       Management Information for TCP/IP-based internets", STD 16, <a href="./rfc1155">RFC</a>
       <a href="./rfc1155">1155</a>, Performance Systems International, Hughes LAN Systems, May
       1990.

   [<a id="ref-3">3</a>] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
       STD 16, <a href="./rfc1212">RFC 1212</a>, Performance Systems International, Hughes LAN
       Systems, March 1991.

   [<a id="ref-4">4</a>] Rose M., and K. McCloghrie, Editors, "Management Information Base
       for Network Management of TCP/IP-based Internets", STD 17, <a href="./rfc1213">RFC</a>
       <a href="./rfc1213">1213</a>, Hughes LAN Systems, Inc., Performance Systems
       International, March 1991.

   [<a id="ref-5">5</a>] Kastenholz, F., "SNMP Communications Services", <a href="./rfc1270">RFC 1270</a>,
       Clearpoint Research Corporation, October 1991.

   [<a id="ref-6">6</a>] Postel J., "User Datagram Protocol", STD 6, <a href="./rfc768">RFC 768</a>,
       USC/Information Sciences Institute, August 1980.

   [<a id="ref-7">7</a>] Information processing systems - Open Systems Interconnection -
       Transport Service Definition - Addendum 1: Connectionless-mode
       Transmission, International Organization for Standardization.
       International Standard 8072/AD 1, June 1986.







<span class="grey">Rose                                                            [Page 3]</span>

<span id="page-4" ></span>
<span class="grey"><a href="./rfc1418">RFC 1418</a>                     SNMP over OSI                    March 1993</span>


   [<a id="ref-8">8</a>] Information processing systems - Open Systems Interconnection -
       Protocol Specification for Providing the Connectionless-mode
       Transport Service, International Organization for
       Standardization.  International Standard 8602, December 1987.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Security Considerations</span>

   Security issues are not discussed in this memo.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Author's Address</span>

   Marshall T. Rose
   Dover Beach Consulting, Inc.
   420 Whisman Court
   Mountain View, CA 94043-2112

   Phone: (415) 968-1052
   EMail: [email protected]

































Rose                                                            [Page 4]