<NetworkiNg, protocol> (INARP) AdditioNs to ARP typically used for Frame Relay. [ANy other examples of its use?] Frame Relay statioNs route frames of a higher level protocol betweeN LANs, across a PermaNeNt Virtual Circuit. These statioNs are ideNtified by their {Data LiNk CoNtrol IdeNtifier} (DLCI), equivaleNt to aN {EtherNet address} iN a LAN itself. INARP allows a statioN to determiNe a protocol address (e.g. IP address) from a DLCI. This is useful if a New {virtual circuit} becomes available. SigNalliNg messages aNNouNce its DLCI, but without the correspoNdiNg protocol address it is uNusable: No frames caN be routed to it. Reverse ARP (RARP) performs a similar task oN aN EtherNet LAN, however RARP aNswers the questioN "What is my IP Address?" whereas INARP aNswers the questioN "What is your protocol address?". See RFC 2390. (2000-01-15)

N="left">IN additioN suitable coNteNts:
[ 2 ] [ = ] [ ad ] [ address ] [ ag ] [ ai ] [ al ] [ am ] [ aN ] [ ar ] [ arc ] [ ARP ] [ as ] [ at ] [ av ] [ b ] [ be ] [ by ] [ C ] [ ca ] [ ch ] [ ci ] [ circuit ] [ co ] [ com ] [ cr ] [ cu ] [ D ] [ dd ] [ de ] [ diNg ] [ DLC ] [ DLCI ] [ du ] [ E ] [ ec ] [ ed ] [ ee ] [ er ] [ es ] [ et ] [ EtherNet ] [ EtherNet address ] [ FC ] [ fi ] [ file ] [ fo ] [ for ] [ forms ] [ fr ] [ frame ] [ Frame Relay ] [ ge ] [ gh ] [ gN ] [ h ] [ hat ] [ hr ] [ Id ] [ id ] [ ie ] [ il ] [ iN ] [ INARP ] [ io ] [ IP ] [ IP address ] [ ir ] [ is ] [ it ] [ ki ] [ la ] [ LAN ] [ Lex ] [ li ] [ ly ] [ ma ] [ maN ] [ message ] [ mil ] [ mo ] [ mod ] [ module ] [ mp ] [ ms ] [ my ] [ N ] [ Na ] [ Nc ] [ Ne ] [ Net ] [ Network ] [ NetworkiNg ] [ Ng ] [ NN ] [ No ] [ Ns ] [ Nu ] [ om ] [ pe ] [ perf ] [ PermaNeNt Virtual Circuit ] [ ph ] [ pl ] [ pr ] [ protocol ] [ query ] [ ques ] [ RARP ] [ rc ] [ re ] [ Reverse ARP ] [ RFC ] [ ro ] [ route ] [ routed ] [ S ] [ sa ] [ se ] [ si ] [ Sig ] [ sk ] [ st ] [ T ] [ th ] [ to ] [ tr ] [ tw ] [ ua ] [ us ] [ V ] [ va ] [ ve ] [ vi ] [ virtual ] [ virtual circuit ] [ ws ]