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