(16)
`
`??§§¥Z6 -6 2 0 2 0
`
`[10]
`
`m__m.mo.anauoaa=-am
`
`.:J§$mn
`
`~H.~.m_nLcum
`
`mo.awunuam=
`
`32%
`
`mom11]|«om<\.Vx.u_
`
`
`
`IIIIIIIIII.|I.|Il..lnIIIl.IuII.lII'IIulsIulul¢Iull.L
`
`unum.#o.=uaum=m=:am
`
`Lmu.Ho.=cmum=m=uqm
`
`m~.~.m_uhnvm
`
`_o.:umnmsmc
`
`,_AmwmL
`....:38
`
`
`
`
`
`IIII|IIIIIIIuIu.lIIIIIlulnulllunllull-.lIuI.II.l.lJ
`
`l||l[lIIIIIIl!lllII|‘|l‘!"|I]l'llIE
`
`e.:m.=unuwam::am
`
`pcum.xu.sunn¢eu=:am
`
`89
`
`L_c.xu.sunumeu=:mm
`
`~83
`
`xw.Eun.osm:
`
`u.w.mHu.uum
`
`Mm.EU£u®=M=
`
`m.w.m_uguua
`
`J»a
`
`mofifiNo__
`
`~cH_
`
`
`
`82E_em_8_co:8_m_O:_
`
`mm?.6E3mama
`
`
`
`
`
`
`
`

`
`Ufl
`
`%fi¥6—62020
`
`[E112]
`
`{E112}
`
`r502—1—
`
`7PUxfi~N
`
`ap-nane=adm .01 .a.ddr
`
`1002-1-———,
`E
`
`7Fvxfi~N
`
`ap-name=bdm . ax . addr-
`
`
`
`1 — E3£13’/'1?
`
`J — Fifi
`name-bdm.sx
`namen
`
`fifl7 F Ixz
`addr=13.8.6
`EQE7 F 1/ X addr=
`
`
`RUFEWJHF-5
`time=9999
`
`1202b
`
`1203b
`
`1204b
`
`time=
`
`
`
`Efiilfiifbififi
`
`
`
`
`
`[1 4]
`
`(E91 4]
`
`/
`
`1401
`
`9
`E
`I
`I
`E
`E
`I
`E
`E
`E
`E
`E
`E
`E
`E
`E
`I
`
`bdm 1403
`
`u """"""""""""""""""""""" '7
`I
`I
`I
`I
`E
`E
`E
`E
`I
`I
`E
`E
`E
`E
`E
`E
`E
`E
`I
`I
`E
`E
`E
`E
`E
`E
`E
`E
`I
`I
`
`1405
`
`ax
`
`sx
`
`..,
`
`addr
`
`1407
`
`dir
`
`mail
`
`adm 1402
`
`E"""""""""""""""" "
`I
`I
`I
`E
`E
`I
`E1404
`E
`E
`I
`I
`E
`E
`E
`E
`I
`
`01
`
`02
`
`addt‘
`
`mail
`
`dir
`1406
`
`03
`
`file
`
`Fx+yA5m
`
`%x4>B1m1
`
`Page 1502 of 1928
`
`

`
`%%¥6—62020
`
`(18)
`
`[12113]
`
`I@1N
`
`T1002-2——:——,
`-5-’! [/0 l~ U")-—1\’
`
`ap-nane=bdu.ax.dir
`
`
`
`¥¥U0%Ufifi
`
`02-2
`
`?4v7bU#—N
`
`ap—name-adm.01.dir
`
`?¥D?IUfifi
`
`I
`
`
`
`IIIIIIIIIII1IIIIIIIIIIIIIIIII
`
`1306b
`
`1307b
`
`1308b
`
`1309b
`
`
`
`name'&dm.02.mail
`
`addr=
`
`ap—addr=
`
`Iyhufifi
`
`name=bdm.sx.nai1
`
`fifi $fl7Fvz
`
`addr=13.8.8
`
`AA F’7’ Fl/:1
`
`ap~addr=5
`
`aIias=
`
`Page 1503 of 1928
`
` 13086
`Wfi
`
`

`
`Electronic Acknowledgement Receipt
`
`International Application Number:
`
`Title of Invention:
`
`Point-to-Point Internet Protocol
`
`First Named Inventor/Applicant Name:
`
`6108704
`
`Customer Number:
`
`42624
`
`Michael R. Casey
`
`Attorney Docket Number:
`
`2655-0188
`
`Payment information:
`
`File Listing:
`
`Document
`
`.
`
`.
`
`File Size(Bytes)/
`
`Multi
`
`Pages
`
`° 1504 of 1928
`
`NPL Documents
`
`F0057_|SR_US9615504.pdf
`
`e27eccddcd4afd0e46cS4746 l 8b0320ce80
`4ee73
`
`

`
`
`
`.
`.
`F0058_gItma n_economIc_ana|
`ysis.pdf
`
`1874599
`
`ee53 I 3be03ddc627 I d4 881 65e869732cba
`dd8dfS
`
`NPL Documents
`
`Information:
`
`
`
`F0059_hue|amo_end_user_pre
`.
`mIses.pdf
`
`6bafdfc0Z5(d5fI a9069bdc68730628aae79
`dc6a
`
`712273
`
`NPL Documents
`
`Information:
`
`
`
`102320
`
`2 I 230c20d I 270e7$6 I5 I 634 3079c6e0e80
`fi40I
`
`NPL Documents
`
`F0060_RFC978.pdf
`
`Information:
`
`
`
`202556
`
`4200eae0048397a08bb I 5b27455eee776I =
`a I a37
`
`NPL Documents
`
`F0061_RFC1055.pdf
`
`Information:
`
`
`
`NPL Documents
`
`F0062_james_mi||s_data_voice
`pdf
`
`99ef‘2 3fe5bI7c3074fe2a3c50b94bc2a9f6dc
`87c
`
`223076
`
`Information:
`
`
`
`F0063_james_forgie_speech.
`pdf
`
`da96c67c7acc4ba388869f0654b9727f973 3
`0cb3
`
`527034
`
`NPL Documents
`
`Information:
`
`
`
`F0064_james_forgie_voice_co
`nferencingpdf
`
`a64 I 74568406C29dfe7866ab66ec3a5fa4ba
`écda
`
`500690
`
`NPL Documents
`
`Information:
`
`
`
`154076
`
`9aed6ddfad82f64 d8ec6a9 I94 a I 5c938e7b
`b(e7f
`
`NPL Documents
`
`FO065_Janes_1979_80.pdf
`
`Information:
`
`7b9504
`
`NPL Documents
`
`F0066_Janes_1985.pdf
`
`e446be3eb5d4585d956eb700228(]3adf40
`
`421297
`
`Warnings:
`
`lnformgfigfl 1505 Of 1928
`
`

`
`
`
`617418
`
`b I57dfi49070abeda57d8c608I7 I4d66886
`8297
`
`NPL Documents
`
`F0067_Janes_1989.pdf
`
`Information:
`
`
`
`2431238
`
`42a92bed6d 324 6 I2d6393dcb84cb77220d
`5c5Iec
`
`NPL Documents
`
`F0068_Janes_1990_91.pdf
`
`Information:
`
`
`
`628193
`
`2 Id4 e5f3edaf3a02e9eIb3aca Ic85067ddcb
`ac48
`
`NPL Documents
`
`F0069_Janes_1992_93.pdf
`
`Information:
`
`
`
`F0070_Jim_stevens_Much_mo
`repdf
`
`50b7eI I9 Iccb 1056! C05 I099e673685Ia77
`1189b
`
`262071
`
`NPL Documents
`
`Information:
`
`428289
`
`
`
`NPL Documents
`
`F0071_John_be||amy_Digita |_
`elephonypdf
`
`d4 I
`
`I 8e2dd0b29ce876e90 I d342c49202_S7
`12356!
`
`Information:
`
`
`
`183914
`
`C361 3862827391 II 9076358057492 I c36bc
`e9cee
`
`Foreign Reference
`
`F0072_JP-63-131637.pdf
`
`Information:
`
`
`
`2765194
`
`4 I4eIcc6I974IcI2d}db57735fId3be644d
`83841
`
`Foreign Reference
`
`F0073_JP_6-62020.pdf
`
`Information:
`
`
`
`FOO74_JP2008163825_Office_A
`ction_Trans|ation.pdf
`
`edbec99254 efe8b8f883d933acI 3ebd 36e6
`c0010
`
`487599
`
`NPL Documents
`
`Information:
`
`a54 ba
`
`1272933
`
`cb52899aaa2I 2045567I9Z5588a887a55 I
`
`I
`
`NPL Documents
`
`F0075_JP-59-44140.pdf
`
`Warnings:
`
`lnformgfigfl 1506 Of 1928
`
`

`
`
`
`F0076_k_sohra by_|SDN_Prima
`y.pdf
`
`55f333f30db6a34d6(b4023d0eI0f62a972
`Iad0
`
`507873
`
`NPL Documents
`
`Information:
`
`
`
`NPL Documents
`
`F0077_ken_sherman_data_co
`.
`.
`mmunIcatIons.pdf
`
`752769
`
`a0804 5a I 9608085c077e9ce8d9e66888398
`Ib75 I
`
`Information:
`
`
`
`F0078_kevin_jefay_kerne|_sup
`portpdf
`
`7nd5cc4aC2748ca37Ie3c4c370396da382f6
`abbc
`
`803713
`
`NPL Documents
`
`Information:
`
`
`
`NPL Documents
`
`F0079_kyuta_saito_voice_pack
`etcommpdf
`
`d249d6607b524 I2523bbb Id75c95d3d I 9
`9f8485
`
`300668
`
`Information:
`
`NPL Documents
`
`F0080_|awrence_roberts_evo|u
`tion_of_packet.pdf
`
`5322acI07dc3I64a74af2da29ceIbIb946I
`I0e2I
`
`543758
`
`
`
`Information:
`
`NPL Documents
`
`F0O81_|in_hwa-
`chun_dynamic_|oad_ba|ancing
`
`837781
`
`3ad7
`75b8I9860‘)e325fc9I3a2Ic40059c640dd3‘
`
`Information:
`
`
`
`378989
`
`7877637c3d098 I 5a3C55b75IcI 87620d82b
`3 Iaf5
`
`NPL Documents
`
`F0082_m_e_u|ug_Statistica|_M
`u|tip|exing.pdf
`
`Information:
`
`748795
`
` F0083_m_gopa|akrishnan_inte
`
`NPL Documents
`
`grating_voice_and_data.pdf
`
`ae2aId3b0II6a57fi40‘)cd4b6e9a3e58384 "
`d0d
`
`Information:
`
`e338
`
`F0084_m_J_ross_a|ternatIves_f
`or_integrating.pdf
`
`77a8d73e3decc48d7585 3a92ccfcf4eee I08
`
`NPL Documents
`
`Warnings:
`
`lnformgfigfl 1507 Of 1928
`
`

`
`
`
`1075971
`
`d4 I4c99a5 Ibdee8c7e6535564b720d53db
`79d492
`
`NPL Documents
`
`F0085_natesa_JanakIraman_ov
`erview_of_recent.pdf
`
`Information:
`
` F0086_p_borgnis-desbordes.
`
`pdf
`
`61 Ibd0eI747e84778c4dI934932595Ia064
`844c0
`
`NPL Documents
`
`Information:
`
`
`
`NPL Documents
`
`F0087_p_venkat_rangan_soft
`are_architecture.pdf
`
`817899
`
`0777202a3b6656b76 I 727a4 b664 8135 Ibdf
`9d4 3bI
`
`Information:
`
`
`
`2166322
`
`e0eebbd5ade457f82f85be64dfi45d634d '
`a645
`
`‘
`
`NPL Documents
`
`FO088_francis94inet.pdf
`
`Information:
`
`
`
`NPL Documents
`
`F0089_|nternet_NavIgator_w|t
`h_SOR.pdf
`
`204 996$ IacI7d622I 6fi7dabeebb8f6bb6 I
`
`1454997
`
`Information:
`
`F0090_Extending_the_|P_|nter NPL Documents
`
`net_Through_Address_Reuse.
`
`3846
`dea6I7364 cb744 32a6 I b08c7a74983Iba46
`
`Information:
`
`NPL Documents
`
`F0091_phi|ip_h_regan_is_it_th
`e_PBX.pdf
`
`83870 3bd I I687 I 64w6903828f9c2e364e I
`
`468795
`
`
`
`Information:
`
`NPL Documents
`
`F0092_po||e_t_ze||weger_An_
`overview_of_the_etherphone.
`
`972784
`
`I387
`efda62ad5ca7dd I I6f(d9d7c22bfe879e0d
`
`Information:
`
`0c If
`
`F0093_r_braudes_Requiremen
`s_for_Mu|ticast.pdf
`
`75a9dfd4 92a76d67 I8eI808d7eId4 581437
`
`NPL Documents
`
`Warnings:
`
`lnformgfigfl 1508 Of 1928
`
`

`
`Information:
`
`Information:
`
`Information:
`
`Information:
`
`NPL Documents
`
`.
`F0094_r_w_meba_ExperIments
`_in_Wideband.pdf
`
`233947
`
`d37bd24c9482b32ddIacI IcIe9ZSb45a56
`30Ic9d
`
`NPL Documents
`
`F0095_r_p_mcNa ma ra_some_
`considerations.pdf
`
`5a0807f2 35f0a2a9d5b567dd8774603dda7
`9 HQ
`
`292918
`
`NPL Documents
`
`.
`F0096_ra ndy_co|e_packet_voI -
`e_when.pdf
`
`662089
`
`2ef3af38d393b0l 3e58d9dbb l aa297 l 560l
`a7a07
`
`NPL Documents
`
`_
`_
`_
`F0O97_scott_f|Inn_coordInatIn
`g_heterogeneous.pdf
`
`1104908
`
`I 60e963fe6320d I 24 7d97276dfd8cZS5 I29
`7bIb8
`
`NPL Documents
`
`_
`_
`_
`_
`F0098_shImmI_hattorI_Integra
`ted_digita|_switching.pdf
`
`656025
`
`570Iee25e3 Id8c636Ic49a8e3I8ed6Ibf46
`
`Total Files Size (in bytes)
`
`30535989
`
`This Acknowledgement Receipt evidences receipt on the noted date by the USPTO ofthe indicated documents,
`characterized by the applicant, and including page counts, where applicable. It serves as evidence of receipt similar to a
`Post Card, as described in MPEP 503.
`
`New Applications Under 35 U.S.C. 111
`lfa new application is being filed and the application includes the necessary components for a filing date (see 37 CFR
`1.53(b)-(d) and MPEP 506), a Filing Receipt (37 CFR 1.54) will be issued in due course and the date shown on this
`Acknowledgement Receipt will establish the filing date of the application.
`
`National Stage of an International Application under 35 U.S.C. 371
`lfa timely submission to enter the national stage ofan international application is compliant with the conditions of 35
`U.S.C. 371 and other applicable requirements a Form PCT/DO/E0/903 indicating acceptance of the application as a
`national stage submission under 35 U.S.C. 371 will be issued in addition to the Filing Receipt, in due course.
`
`New International Application Filed with the USPTO as a Receiving Office
`lfa new international application is being filed and the international application includes the necessary components for
`an international filing date (see PCT Article 11 and MPEP 1810), a Notification of the International Application Number
`and ofthe International Filing Date (Form PCT/R0/105) will be issued in due course, subject to prescriptions concerning
`national security, and the date shown on this Acknowledgement Receipt will establish the international filing date of
`the application.
`
`Page 1509 of 1928
`
`

`
`wonw IN1EI.uzcIUAI._ meg ORGANIZATION
`PCT _
`INTERNATIONAL APPLICATION PUBLISHED UNDER THEIPATENT COOPERATION TREATY (PCT)
`(51) Int-national Patent Clasificafion 5 =
`(11) International Publication Number:
`WO 94/22087
`G06F‘ 13/00
`'
`
`
`
`(43) Ina-nouonnl Publication Door:
`
`29 Septernber I994 (299994)
`
`3
`
`(21) International Application Number:
`
`PCT/US94/00(D4
`
`(22) International Filing Date:
`
`3 January I994 (0331.94)
`
`(81) Designated Shtes: AU, CA. JP. KR, European patent (AT,
`BE.C-H.DE.DK.E3.FR.GB.GR.IB.lT.LU.MC.NL.
`PI‘, 33).
`
`(30) Priority Data:
`08/033,914
`
`19 March 1993 (l9.03.93)
`
`vs
`
`A
`Published
`Mr). intemarional search report.
`
`(71) Applicant: 3COM CORPORATION [US/US]: 5400 Bayfront
`Plaza, PO. Box 58145. Santa Clara, CA 95052-8145 (US).
`
`(72) Inventors: NILAKANTAN. Chandrasekharan; 3774 Woodbart
`Court, San Jose, CA 95ll7 (US). IDI. Ly; 34852 Winches-
`ter Placa. Fremont, CA 94555 (US). ARUNKUMAR, Na-
`Emji 3041 Cedar Ridge Court, San Jose. CA 95148 (US).
`SEAMAN, Michael, John; 350 Elan Village Lane, #206,
`San Jose. CA 95134 (US).
`
`(74) Agent: HAYNES. Mark, A.: Haynes & Davis. Suite 170. 2180
`-
`Sand Hill Road, Menlo Park, CA 94025-6935 (US).
`
`(54) 'I1tle: SYSTEM FOR REVERSE ADDRESS RESOLUTION FOR REMOTE NETWORK DEVICE
`
`MEDIA AD ‘‘
`IF ADDRE
`DATA BASE
`GIANNEL ND!
`[P ADIIISS
`DAM BASE
`
`REQUEST
`GENERAHDN
`PROCESS
`(FIG.-4)
`
`ACCEPTANCE
`PROCESS
`
`PACKET EXCHANE OVER VIM MEDIA
`
`.5
`
`(51) Abstract
`
`Areverse addressresolution protocol foruse in a oornmuniwion network which allows resolution logic to provide a higher level
`protocol information (such asanIPaddress)tonsourceofaIeqnest (127) for such information (l22),independentofthephysical network
`addrossofsnchsourco. Theprotocolisusedinaproecswrhavingapltnnlityofpcrmatleastoneofsuchpcruconnecwdbyapoint-to
`point channelto arcxnote network device. Revcrseaddressrcsolution protocol is responsive (129) uonrcsolution Iequestfromthe remote
`networkdcvioeaaossdIepoim4o-pointchanneluasupplythehigberlcvel protooolinforumionbascdupontheportthroughwhich the
`resolmionrequestis received (125). rather lhanthe physical netwakaddressofdre requcsdngdevioe. Thm,aremotedevioeInay be
`coupled Ina network. and connected tnaeentral nannagunentsin: acrosupoim-to-pointeommunicalion link. in a "plug and play" mode.
`'I'hepe:sonwnnec1ingfl1edevicetotlIeIemotenetwoI'kdoesnotneednodeterInined:ephysicalnetworkaddrusofthodeviceorconfignre
`thedeviccwithnhighcrleveladdresspromcol.
`
`Page 1510 of 1928
`
`

`
`Codes used to identify States party to the PC!‘ on the from pages of pamphlets publishing international
`applications under the PCT.
`AT
`Austria
`Auslnlh
`AU
`B3
`B3
`BF
`BG
`31
`BR
`BY
`CA
`Cl’
`CG
`
`FOR THE PURPOSES OF INFORMATION ONLY
`
`Pun
`
`
`
`§§§§§:EE=§:§S:==fi2$§2S
`
`gsaeqaaaaafiaszsafifisfifiga
`
`30C
`
`M
`CN
`(3
`
`aD
`
`E
`DK
`ES
`
`HF
`
`R
`(M
`
`Page1511of1928
`
`

`
`W0 94l'2.2087
`
`PCT/US94I00004
`
`SYSTEM FOR REVERSE ADDRESS RESOLUTION
`
`FOR REMOTE NETWORK DEVICE
`
`FIELD QE IHE INVENIIQN
`
`The present invention relates to start up protocols for devices in I
`
`communication networks; and more particularly to systems which allow a
`
`machine without a configured higher level protocol address to obtain such '
`
`5
`
`address without a unique machine identifier.
`
`SCRI
`
`INOF E
`
`A
`
`A widely accepted series of intematlonal standards describing network
`
`architectures is known as the OSI
`
`reference model.
`
`See, generally,
`
`10
`
`Tannenbaum, , 2nd Ed., 1988, Prentice-Hall. According
`
`to this model, network communications are divided into a plurality of
`
`protocols within layers of the model. Local Area Networks (LANs) operate
`
`using medium access protocols within the lower layers, |ayers1 and 2, oi the
`
`OSI model, such as the carrier sense multiple access with collision detection
`
`15
`
`CSMA/CD, IEEE Standard 802.3, also known as ETHERNET, and the token
`
`ring access ring method of IEEE Standard 802.5. These two lower layers
`
`are typically broken down into the physical layer and the data link layer, with
`
`the data link layer being further broken down into a media access control
`
`(MAC) layer, and a logical link layer.
`
`20
`
`Systems, such as personal computers, workstations, and mainframe
`
`computers, attached to the LANs each have a distinct lower level protocol
`
`identifier known as the physical network address or MAC address. LAN
`frames forwarded to a destination system on the network under these lower
`
`L
`
`level protocols contain the destination system MAC address, or other
`
`25
`
`physical network address, as a destination. LAN frames forwarded from a
`
`source system on the network contain the source system MAC address, or
`
`other physical network address, as
`
`a source address.
`
`Systems
`
`-1-
`
`Page 1512 of 1928
`
`

`
`W0 94/22087
`
`PCT/US94/00004
`
`communicate by encapsulating additional protocols (OSI layers 3-7) within
`
`the lower layer LAN frames. These higher level protocols are grouped into
`
`suites such as the TCP/IP protocol suite and the XNS protocol suite. Many
`
`LANs contain groups of end systems that use different higher level protocol
`
`5
`
`suites. These higher level protocol suites also assign unique higher level
`
`.
`
`protocol
`
`identifiers to systems which transmit or receive frames in the
`
`network.
`
`For instance, an internet protocol IP address is assigned to each
`
`system operating within an intemet protocol network. The intemet protocol
`
`10
`
`address includes a network address portion and a host address portion. The
`
`network address portion identifies a network within which the system resides,
`
`and the host address portion uniquely identifies the system in that network.
`
`Processors routing packets in an intemet protocol network rely on the
`
`network address portion of the IP address in a frame to find -the local area
`
`15
`
`network of the destination machine. Once the local area network of the
`
`destination is located, the frame is forwarded to that network where the host
`
`address portion is relied upon to assign a MAC address for the destination
`
`machine to the packet. Thus, higher level protocol address places the
`
`device in a particular network orsubnetwork, so that the higher level protocol
`
`20
`
`can effectively manage the routing of packets among the networks, without
`
`maintaining a table of the unique physical access layer identifiers for all of
`
`the terminals in the network.
`
`In order to communicate in such a network, the machine must first
`
`obtain its higher level protocol address. This address is typically assigned
`
`25
`
`by a central authority, such as the intemet Activities Board, or by a network
`
`manager. Normally, a particular machine learns its IP address by a
`
`configure operation, in which a technician uses a local terminal to configure
`
`the machine.
`
`In a centrally managed network, this could be a cumbersome
`
`task, involving travel of skilled personnel away from the central management
`
`30
`
`location. However, a reverse address resolution protocol RARP has been
`
`-2-
`
`Page 1513 of 1928
`
`

`
`W0 94/22087
`
`PCT/US94/00004
`
`developed for networks such as TCP/IP or SNMP protocols. The HARP
`
`allows a machine without a configured IP address to obtain an IP address
`
`from a remote sewer. The machine broadcasts a request and waits until an
`
`RARP server responds.
`
`In the request, the requesting machine must provide
`
`5
`
`its physical network address (MAC address) to uniquely identify itself,
`
`allowing the sewer to map it into an IP address.
`
`This RARP protocol works fine, so long as the central management
`
`site is aware of the physical network address of the devices being added to
`
`the network.
`
`in order to find out the physical network address, all of the
`
`.
`
`4
`
`10
`
`system being added to the network must be passed through the central
`
`management site so that the address can be read from these machines, or
`
`a local technician must read the physical network address from the machine
`
`and telephone the central site. This process makes connecting a new device
`
`to a network difficult. Further, this process of physically reading the physical
`
`15
`
`network address from the box is prone to human errors. Such addresses
`
`are typically very long (MAC addresses are 48 bits long), and can be
`
`misread or typed in erroneously.
`
`It
`
`is desirable to have so-called ‘plug and play‘ network devices.
`
`Such devices can be plugged in and turned on by unskilled personnel.
`
`20
`
`However, the need to find out the physical network address of the box
`
`detracts from this ability.
`
`Accordingly, it is desirable to provide a technique for resolving higher
`
`level protocol addresses, without reliance on the lower level protocol
`
`addresses.
`
`25
`
`§L1MMAB! QE ] HE INMENTIQN
`
`.
`
`The present invention provides a reverse address resolution protocol
`
`for use in a communication network which allows resolution logic to provide
`
`a higher level protocol address, or other information, to a source of a request
`
`30
`
`for such address, independent of the physical network address of such
`
`-3-
`
`Page 1514 of 1928
`
`

`
`W0 94/2087
`
`PCTIUS94/00004
`
`source. The protocol according to the present invention is used in a
`
`processor having a plurality oi ports, at least one of such ports connected by
`
`a point-to-point channel to a remote network device. The reverse address
`
`resolution protocol is responsive to a resolution request from the remote
`
`network device across the point-to—point channel to supply the higher level
`
`.
`
`protocol address based upon the port through which the resolution request
`
`is received, rather than the physical network address of the requesting
`
`device. Thus, a remote device may be coupled to a network, and connected
`
`to a central management site across a point-to—point communication link in
`
`a “plug and play" mode. The person connecting the device to the remote
`
`network does not need to determine the physical network address of the
`
`device or configure the device with a higher level address protocol. All this
`
`can be handled automatically.
`
`Thus, the present invention can be characterized as an apparatus for
`
`resolving higher level protocol addresses in response to resolution requests
`from a source oi resolution ‘requests in a communication network. The
`
`apparatus comprises a central processor having a plurality of ports for
`
`connection to the communication network, and resolution logic which is
`
`coupled to the communication network and in communication with the central
`
`processor. The resolution logic provides a higher level protocol identifier in
`
`response to a particular port in the plurality of ports through which the
`
`resolution request is received by the central processor, independent of the
`
`lower level protocol Identifier of the source of the resolution request. The
`resolution logic may be a routine executed by the central processor, or a
`
`routine executed by a network management processor coupled to the
`
`communication network, and in communication with the central processor.
`
`The resolution logic, according to one aspect, includes a resolution
`
`table that is configurable independent of the lower level protocol identiflers,
`
`which assigns higher level protocol identifiers to particular ports of the central
`
`10
`
`15
`
`20
`
`25
`
`30
`
`processor through which the resolution requests may be received.
`
`.4-
`
`Page 1515 of 1928
`
`

`
`W0 94I22087
`
`PCT/US94I00004
`
`The higher level protocol identifier may comprise an intemet protocol
`
`IP address, which includes a network address for the source of the resolution
`
`request, and a host address for the source of the resolution request.
`
`Further, the higher level protocol may be utilized by a network management
`
`5
`
`system, which communicates network-wide, while the lower level protocol
`
`.
`
`comprises a medium access protocol.
`
`The resolution logic, according to the present invention, relies on the ‘
`
`source of the resolution request being coupled across a point-to-point
`
`communication channel to the particular port of the processor receiving the
`
`10
`
`request.
`
`in this way, the port serves as a virtual identifier for the source of
`
`the request.
`
`Thus, the present invention can also be characterized as an apparatus
`
`for connecting a first network and a second network. This apparatus
`
`includes a communication link, a first processor, and a second processor.
`
`15
`
`The first processor has a first interface coupled to the first network and a
`
`second interface coupled to the communication link. The second processor
`
`has a lower level protocol identifier and is coupled to the second network
`
`and to the communication link. Resolution logic is coupled to the first
`
`network to provide a higher level protocol identifier to the second processor
`
`20
`
`in response to a resolution request through the second interface of the first
`
`processor, independent of the lower level "protocol identifier of the second
`
`processor.
`
`in this manner, the first processor can configure the higher level
`
`protocol addresses for devices in the system, independent of the lower level
`
`protocol addresses.
`
`25
`
`According to another aspect of the invention, the first processor
`
`includes resources to provide network services to frames of data In the first
`
`.
`
`and second networks through the first and second interfaces, and the second
`
`processor includes resources to extend the second interface of the first
`
`processor transparently to the second network.
`
`Page 1516 of 1928
`
`

`
`wo 94/2087
`
`PCT/US94I00004
`
`The resolution logic may comprise a routine executed by the first
`
`processor, or a routine executed by a network management processor
`
`located in the first network.
`
`Accordingly, a techniquevwhich greatly improves the “plug and play‘
`
`capability of a network-device has been provided. Fiemote networks may be .
`
`set up using this system, without requiring error prone and cumbersome
`
`techniques to acquire the physical network address of each device being
`
`added to the network.
`
`Other aspects and advantages of the present invention can be seen
`
`upon review of the figures, the detailed description, and the claims which
`
`follow.
`
`F D
`
`C
`
`ON OF
`
`E
`
`I
`
`Fig. 1
`
`is a schematic diagram of a system including the reverse
`
`address resolution logic according to the present invention.
`
`Fig. 2 illustrates a prior art packet exchange sequence for reverse
`
`address resolution over LAN media.
`
`Fig. 3 illustrates a packet exchange sequence over a WAN medium
`
`as extended according to the present invention.
`
`Fig. 4 illustrates the resolution request generation process used in the
`
`sequence of Fig. 3.
`
`Fig. 5 illustrates the resolution request response generation process
`
`used in the sequence of Fig. 3.
`
`Fig. 6 illustrates the resolution request response acceptance process
`
`used in the sequence of Fig. 3, which results in a request for a subnet mask
`
`in IP networks.
`
`Fig. 7 is a diagram of the subnet mask response generation process
`
`used in the sequence of Fig. 3.
`
`10
`
`15
`
`20
`
`25
`
`Fig. 8'is a diagram of the subnet mask response acceptance process
`used in the sequence of Fig. 3.
`.
`
`30
`
`Page 1517 of 1928
`
`

`
`W0 94/2208‘!
`
`PCTIUS94/00004
`
`Fig. 9 is a schematic diagram illustrating one network environment in
`
`which the present invention may be used.
`
`OOFE F
`
`E
`
`N
`
`A detailed description oi preferred embodiments of the present '
`
`invention is provided with respect to Figs. 1-9. Fig. 1 illustrates application
`
`oi the present invention in a preferred embodiment. Figs. 2-8 illustrate the -
`
`extended protocol for reverse address resolution used in a preferred
`
`embodiment of the present invention. Fig. 9 provides an overview of a
`
`network in which the present invention may be applied.
`
`Fig. 1 provides a schematic diagram of an apparatus for connecting
`
`a first network 10 to a second network 11 using address resolution logic 25
`
`according to the present invention. The first network 10 includes a first LAN
`
`9 which includes a plurality of end systems and a server, and may be
`
`interconnected to other LANs using intermediate systems (not shown) known
`
`in the art. Coupled to the LAN 9 is a boundary router 12. The boundary
`
`router 12 is an intermediate system in the network which provides network
`
`resources serving higher
`
`level protocol suites which,
`
`in one unique
`
`embodiment, constitute routing resources. As such, the boundary router 12
`
`maintains end system directories 13 for the local LAN 9 and global routing
`
`information 14 to serve the routing functions according to the higher level
`
`protocol suites. Thus, the end system directories will include DEC end
`
`system tables, IPX end system tables, IP and system tables, and others to
`
`serve other protocol suites that are operating in the network 10. The
`
`boundary router 12 may also be coupled to other portions of the corporate
`
`data network as schematically illustrated at arrow 15.
`
`The boundary router 12 includes a local interface 16 which serves the
`
`local LAN 9 providing access to the network resources within the boundary
`
`router to end systems on LAN 9. The boundary router could also have
`
`interfaces to other local LANs as well.
`
`in addition, the boundary router 12
`
`.-7-
`
`10
`
`15
`
`20
`
`25
`
`30
`
`Page 1518 of 1928
`
`

`
`WO 94/22087
`
`PCT/US94i00004
`
`includes a remote routing interface 17, which provides an interface to the
`
`network resources for and systems in the remote network 11.
`
`In support of
`
`the remote interface 17,
`
`the boundary router maintains and system
`
`directories 18 serving the higher level protocol suites in the remote network
`
`11.
`
`As illustrated schematically by the hatched symbol 19, the remote
`
`network 11 appears to the end systems in the local LAN 9 as if it were a -
`
`LAN connected locally to the boundary router 12. This appearance is
`
`maintained across a communication link 20, which may use telephone or
`
`other dial up lines,
`
`leased lines, satellites. wireless systems, or other
`
`communication media configured as a point-to-point channel, to a routing
`
`adapter21, which is coupled to the remote network 11. The remote network
`
`11 includes a remote LAN 22 to which a plurality of end systems and servers
`
`may be connected as known in the art.
`
`in addition, the LAN 22 may be
`
`coupled to other LANs in the remote network 11 through Intermediate
`
`systems (not shown) as known in the art. The routing adapter 21 provides
`
`resources for extending the remote routing interface 17 transparently to the
`
`remote network 11 across the communication link 20. From the perspective
`
`of the remote network 11.
`
`the routing adapter 21 provides the same
`
`functionality as a router, while the routing adapter itself operates independent
`
`of the higher level protocol suites.
`
`The system thus provides efficient communication between remote
`
`networks, and a corporate network, through a boundary router (e.g.. net 11,
`
`routing adaptor 21, link 20, boundary router 12, net 9).
`
`The routing adapter 21 includes hardware perlonning physical network
`
`access protocols for connection to the network 22. Also, such hardware is
`
`assigned a physical network address, or MAC address, to uniquely identify
`
`the system for the lower level protocol suites. However,
`
`in order to
`
`participate in the higher level protocol suites managed by the boundary
`
`router 12 or elsewhere in the central network 10, an identifier which serves
`
`-3-
`
`10
`
`15
`
`20
`
`25
`
`30
`
`Page 1519 of 1928
`
`

`
`W0 94/22087
`
`PCTIUS94/00004
`
`such higher level protocols is needed for the routing adapter 21. Thus, the
`
`boundary router 12 includes resolution logic 25 to provide such identifier in
`
`response to the interface 17 across which a request for such identifier is
`
`received.
`
`5
`
`Figs. 2-8 illustrate the reverse address resolution protocol executed .
`
`by the resolution logic 25 in the boundary router of Fig.
`
`1 according to a
`
`preferred embodiment, in which the higher level protocol address comprises ’
`
`an internet protocol IP address, such as used by SNMP (Simple Network
`
`Management Protocol) standard network management servers.
`
`10
`
`Fig. 2 illustrates the prior art mechanism which is utilized in the
`
`preferred system on ports of the routing adaptor coupled to LAN media. The
`
`structure of Fig. 2 includes a first interface 100 corresponding to the HAHP
`
`client port of
`
`the routing adapter 21, and a second interface 101
`
`corresponding to an HARP server in the local network 11. The routing
`
`15
`
`adapter includes HARP request generation process 102, an RAHP response
`
`acceptance process 103, and an ICMP subnet mask response acceptance
`
`process 104. The resolution logic 25 in the RAHP server includes an RAHP
`
`response generation process 105, and an ICMP subnet mask response
`generation process 106.
`I
`
`20
`
`Using the industry standard HAHP request generation process, as
`
`specified in RFC 903 dated June, 1984, the RAHP request generation
`
`process 102 in the client generates an RAHP HFC 903 request 107, which
`
`includes the client's MAC address. This request 107 is received at the
`
`server interface 101 and the HARP response generation process 105
`
`25
`
`generates a response 108 by accessing a database or other logic which
`
`assigns an IP address based upon the MAC address in the request 107.
`
`The HAHP response acceptance process 103 in the client receives the iP
`
`address from the response 108, stores it as appropriate in the client, and
`
`generates an ICMP subnet mask request 109. The server 101 receives the
`
`30
`
`request 109 and the ICMP subnet mask response generation process 106
`
`-9-
`
`Page 1520 of 1928
`
`

`
`W0 94/12,087
`
`PCT/US94I00004
`
`supplies a subnet mask response 110 to the client 100. The ICMP subnet
`
`mask response acceptance process 104 then configures the client with the
`
`IP address and the subnet mask, and assigns the address of the server 101
`
`as the default gateway address.
`
`5
`
`Fig. 3 illustrates this process as extended according to the present
`
`invention for reverse address resolution independent of the physical network
`
`address of the client.
`
`In this aspect, the interface 120 corresponds to the
`
`routing adapter 21 operating as an HARP client. The interface 121
`
`corresponds to the interface 17 of the boundary router 12 operating as an
`
`10
`
`HARP server. The HAHP sewer 121 need not be located in the boundary
`
`router 12. Rather, it can be located in any in system or intermediate system
`
`coupled to the networks served by the boundary router 12.
`
`In the extended sequence, as illustrated in Fig. 3, the routing adapter
`
`also includes an HAHP request generation process 122 (Fig. 4), an HAHP
`
`15
`
`response acceptance process 123 (Fig. 6), and an ICMP subnet mask
`
`response acceptance process 124 (Fig. 8). The HARP server in the
`
`boundary router includes an HARP response generation process 125 (Fig.
`
`5) and an ICMP subnet mask response generation process 126 (Fig. 7).
`
`As in the prior art system, the HARP request generation process 122
`
`20
`
`in the client 120 generates an HAHP RFC 903 request 127. Also, the
`
`process 122 generates an extended request 128, which indicates to the
`
`receiver that the address resolution must be conducted independent oi the
`
`MAC address.
`
`The HAHP response generation process 125 receives both the RFC
`
`25
`
`903 request 127 and the MAC independent request 128.
`
`If the response can
`
`be served with the RFC 903 request, then the response generation process
`
`125 proceeds that way. However, if the MAC address of the client 120 has
`
`not been previously communicated to the response generation process 125,
`
`then the MAC independent request 128 must be utilized.
`
`-10-
`
`Page 1521 of 1928
`
`

`
`W0 94/22087
`
`PC!‘/USMI00004
`
`The RARP response generation process 125 is coupled to a media
`
`address/IP address database 135 and to a channel number/lP address
`
`database 136. These databases are configured by the network managerto
`
`assign IP addresses throughout the network. The channel number/lP
`
`5
`
`address database is relied upon when the media address (MAC address) of
`
`_
`
`the client 120 is not available at the time the IP address is configured.
`
`’
`
`in either event, the RARP response generation process 125 generates
`
`an RARP RFC 903 response 129 which includes an IP address. The RARP
`‘response acceptance process 123 in the client 120 accepts t