summaryrefslogtreecommitdiff
path: root/doc/rfc/rfc1089.txt
blob: 5c7624bc02b63983eb22c3c13358cfb3356796e7 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
Network Working Group                                  M. Schoffstall
Request for Comments: 1089           Rensselaer Polytechnic Institute
                                                             C. Davin
                                  MIT Laboratory for Computer Science
                                                             M. Fedor
                                                       NYSERNet, Inc.
                                                              J. Case
                                 University of Tennessee at Knoxville
                                                        February 1989


                           SNMP over Ethernet

Status of This Memo

   This memo describes an experimental method by which the Simple
   Network Management Protocol (SNMP) as specified in [1] can be used
   over Ethernet MAC layer framing [2] instead of the Internet UDP/IP
   protocol stack.  This specification is useful for LAN based network
   elements that support no higher layer protocols beyond the MAC sub-
   layer.  Distribution of this memo is unlimited.

Overview and Rational

   SNMP has been successful in managing Internet capable network
   elements which support the protocol stack at least through UDP the
   connectionless Internet transport layer protocol.  As originally
   designed, SNMP is capable of running over any reasonable transport
   mechanism (not necessarily a transport protocol) that supports bi-
   directional flow and addressability.

   Many non-Internet capable network elements are present in local
   networks; for example, repeaters and wiring concentrators.  They
   include both addressability, and programmable intelligence.  These
   devices are widely used and increasingly important yet, for the most
   part, invisible except through proprietary mechanisms.

Specification

   Almost all Internet capable network elements use the same mechanism
   for encapsulation of the Internet protocol stack regardless of
   conformity with the physical characteristics of Ethernet or 802.3,
   this mechanism is specified in [3] and [4].  This specification
   continues that style with the assignment (by XEROX) of 33100
   (hexadecimal 814C) to the Ethernet Type field for SNMP.  The data
   portion of the Ethernet frame would then be a standard SNMP message
   as specified in [1].




Schoffstall, Davin, Fedor & Case                                [Page 1]
^L
RFC 1089                   SNMP over Ethernet              February 1989


References

     [1]  Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A Simple
          Network Management Protocol", RFC-1067, University of
          Tennessee at Knoxville, NYSERNet, Inc., Rensselaer Polytechnic
          Institute, and Proteon, Inc., August 1988.

     [2]  DEC, "The Ethernet - A Local Area Network", Version 2.0,
          Digital Equipment Corporation, Intel Corporation, Xerox
          Corporation.

     [3]  Hornig, C., "A Standard for the Transmission of IP Datagrams
          over Ethernet Networks", RFC-894, Symbolics, April 1984.

     [4]  Postel, J., and J. Reynolds, "A Standard for the Transmission
          of IP Datagrams over IEEE 802 Networks", RFC-1042, USC
          Information Sciences Institute, February 1988.

Authors' Addresses

   Marty Schoffstall
   NYSERNET Inc.
   Rensselaer Technology Park
   165 Jordan Road
   Troy, NY 12180

   Phone: (518) 276-2654

   EMail: schoff@stonewall.nyser.net


   Chuck Davin
   MIT Laboratory for Computer Science, NE43-507
   545 Technology Square
   Cambridge, MA 02139

   Phone: (617) 253-6020

   EMail: jrd@ptt.lcs.mit.edu












Schoffstall, Davin, Fedor & Case                                [Page 2]
^L
RFC 1089                   SNMP over Ethernet              February 1989


   Mark Fedor
   Nysernet, Inc.
   Rensselaer Technology Park
   125 Jordan Road
   Troy, NY 12180
   (518) 283-8860

   Phone: (518) 283-8860

   EMail: fedor@patton.NYSER.NET


   Jeff Case
   University of Tennessee Computing Center
   Associate Director
   200 Stokely Management Center
   Knoxville, TN 37996-0520

   Phone: (615) 974-6721

   EMail: case@UTKUX1.UTK.EDU






























Schoffstall, Davin, Fedor & Case                                [Page 3]
^L