1
2
3ADDRESS RESOLUTION PROTOCOL PARAMETERS
4
5The Address Resolution Protocol (ARP) specified in [RFC826] has
6several parameters.  The assigned values for these parameters are
7listed here.
8
9REVERSE ADDRESS RESOLUTION PROTOCOL OPERATION CODES
10
11The Reverse Address Resolution Protocol (RARP) specified in [RFC903]
12uses the "Reverse" codes below.
13
14DYNAMIC REVERSE ARP
15
16The Dynamic Reverse Address Resolution Protocol (DRARP) uses the
17"DRARP" codes below.  For further information, contact: David Brownell
18(suneast!helium!db@Sun.COM).
19
20INVERSE ADDRESS RESOULUTION PROTOCOL
21
22The Inverse Address Resolution Protocol (IARP) specified in [RFC1293]
23uses the "InARP" codes below.
24
25Assignments:
26
27Number Operation Code (op)                           References
28------ --------------------------                    ----------
29     1  REQUEST                                        [RFC826]
30     2  REPLY                                          [RFC826]
31     3  request Reverse                                [RFC903]
32     4  reply Reverse                                  [RFC903]
33     5  DRARP-Request                          [David Brownell]
34     6  DRARP-Reply                            [David Brownell]
35     7  DRARP-Error                            [David Brownell]
36     8  InARP-Request                                 [RFC1293]
37     9  InARP-Reply                                   [RFC1293]
38    10  ARP-NAK                                       [RFC1577]
39    11  MARS-Request                                 [Armitage]
40    12  MARS-Multi                                   [Armitage]
41    13  MARS-MServ                                   [Armitage]
42    14  MARS-Join                                    [Armitage]
43    15  MARS-Leave                                   [Armitage]
44    16  MARS-NAK                                     [Armitage]
45    17  MARS-Unserv                                  [Armitage]
46    18  MARS-SJoin                                   [Armitage]
47    19  MARS-SLeave                                  [Armitage]
48    20  MARS-Grouplist-Request                       [Armitage]
49    21  MARS-Grouplist-Reply                         [Armitage]
50    22  MARS-Redirect-Map                            [Armitage]
51    23  MAPOS-UNARP				     [Maruyama]
52
53
54Number Hardware Type (hrd)                           References
55------ -----------------------------------           ----------
56     1 Ethernet (10Mb)                                    [JBP]
57     2 Experimental Ethernet (3Mb)                        [JBP]
58     3 Amateur Radio AX.25                                [PXK]
59     4 Proteon ProNET Token Ring                        [Doria]
60     5 Chaos                                              [GXP]
61     6 IEEE 802 Networks                                  [JBP]
62     7 ARCNET                                             [JBP]
63     8 Hyperchannel                                       [JBP]
64     9 Lanstar                                             [TU]
65    10 Autonet Short Address                             [MXB1]
66    11 LocalTalk                                         [JKR1]
67    12 LocalNet (IBM PCNet or SYTEK LocalNET)             [JXM]
68    13 Ultra link                                        [RXD2]
69    14 SMDS                                              [GXC1]
70    15 Frame Relay                                        [AGM]
71    16 Asynchronous Transmission Mode (ATM)              [JXB2]
72    17 HDLC                                               [JBP]
73    18 Fibre Channel                            [Yakov Rekhter]
74    19 Asynchronous Transmission Mode (ATM)           [RFC1577]
75    20 Serial Line                                        [JBP]
76    21 Asynchronous Transmission Mode (ATM)              [MXB1]
77    22 MIL-STD-188-220                                 [Jensen]
78    23 Metricom                                         [Stone]
79    24 IEEE 1394.1995                                  [Hattig]
80    25 MAPOS					     [Maruyama]
81
82Protocol Type (pro)
83
84Use the same codes as listed in the section called "Ethernet Numbers
85of Interest" (all hardware types use this code set for the protocol
86type).
87
88
89REFERENCES
90
91[RFC826] Plummer, D., "An Ethernet Address Resolution Protocol or
92         Converting Network Protocol Addresses to 48-bit Ethernet
93         Addresses for Transmission on Ethernet Hardware", STD 37, RFC
94         826, MIT-LCS, November 1982.
95
96[RFC903] Finlayson, R., Mann, T., Mogul, J., and M. Theimer, "A
97         Reverse Address Resolution Protocol", STD 38, RFC 903,
98         Stanford University, June 1984.
99
100[RFC1293] Bradley, T., and C. Brown, "Inverse Address Resolution
101          Protocol", RFC 1293, Wellfleet Communications, Inc.,
102          January 1992.
103
104
105PEOPLE
106
107[Armitage] Grenville Armitage, <gja@thumper.belcore.com>, April 1995.
108
109[AGM] Andy Malis <malis_a@timeplex.com>
110
111[GXC1] George Clapp <meritec!clapp@bellcore.bellcore.com>
112
113[Doria] Avri Doria <avri@peoteon.com> December 1994.
114
115[GXP] Gill Pratt <gill%mit-ccc@MC.LCS.MIT.EDU>
116
117[Jensen] Herb Jensen, <hwjensen@itt.com>, February 1995.
118
119[JBP] Jon Postel <postel@isi.edu>
120
121[JKR1] Joyce K. Reynolds <jkrey@isi.edu>
122
123[JXM] Joseph Murdock <---none--->
124
125[Hattig] Myron Hattig, <Myron_Hattig@ccm.jf.intel.com>, February 1997.
126
127[Maruyama] Mitsuru Maruyama, <mitsuru@ntt-20.ecl.net>, March 1997.
128
129[MXB1] Mike Burrows <burrows@SRC.DEC.COM>
130
131[PXK] Philip Koch <Philip.Koch@DARTMOUTH.EDU>
132
133[RXD2] Rajiv Dhingra <rajiv@ULTRA.COM>
134
135[Stone] Jonathan Stone, <jonathan@DSG.Stanford.edu>, May 1996.
136
137[TU] Tom Unger <tom@CITI.UMICH>
138
139[David Brownell]
140
141[Mark Laubach]
142
143[Yakov Rekhter] <Yakov@IBM.COM>
144
145[]
146