 10. Mobile Node 6 may identify Foreign Agent 10 through various solicitations and advertisements which form part of the Mobile IP protocol. When Mobile Node 6 engages with network segment 14, Foreign Agent 10 relays a registration request to Home Agent 8 (as indicated by the dotted line “Registration”). The Home and Foreign Agents may then negotiate the conditions of the Mobile Node's attachment to Foreign Agent 10. For example, the attachment may be limited to a period of time, such as two hours. When the negotiation is successfully completed, Home Agent 8 updates an internal “mobility binding table” which specifies the care-of address (e.g., a collocated care-of address or the Foreign Agent's IP address) in association with the identity of Mobile Node 6. Further, the Foreign Agent 10 updates an internal “visitor table” which specifies the Mobile Node address, Home Agent address, etc. In effect, the Mobile Node's home base IP address (associated with segment 12) has been shifted to the Foreign Agent's IP address (associated with segment 14).
Now, suppose that Mobile Node 6 wishes to send a message to a corresponding node 18 from its new location. A message from the Mobile Node is then packetized and forwarded through Foreign Agent 10 over the internet 4 and to corresponding node 18 (as indicated by the dotted line “packet from MN”) according to a standard internet protocol. If corresponding node 18 wishes to send a message to Mobile Node—whether in reply to a message from the Mobile Node or for any other reason—it addresses that message to the IP address of Mobile Node 6 on sub-network 12. The packets of that message are then forwarded over the internet 4 and to router R1 and ultimately to Home Agent 8 as indicated by the dotted line (“packet to MN(1)”). From its mobility binding table, Home Agent 8 recognizes that Mobile Node 6 is no longer attached to network segment 12. It then encapsulates the packets from corresponding node 18 (which are addressed to Mobile Node 6 on network segment 12) according to a Mobile IP protocol and forwards these encapsulated packets to a “care of” address for Mobile Node 6 as shown by the dotted line (“packet to MN(2)”). The care-of address may be, for example, the IP address of Foreign Agent 10. Foreign Agent 10 then strips the encapsulation and forwards the message to Mobile Node 6 on sub-network 14. The packet forwarding mechanism implemented by the Home and Foreign Agents is often referred to as “tunneling.”
As described above
10. Mobile Node 6 may identify Foreign Agent 10 through various solicitations and advertisements which imprint character of the Mobile IP protocol. When Mobile Node 6 engages with network segment 14, Foreign Agent 10 relay a registration request to Home Agent 8 (as indicated by the dashed line “ Registration ”). The Home and Foreign Agents may then negotiate the conditions of the Mobile Node's fastening to Foreign Agent 10. For case, the attachment may be specify to a period of time, such as two hour. When the negotiation is successfully completed, Home Agent 8 updates an internal “ mobility binding table ” which stipulate the care - of address (e.g., a collocated concern - of address or the Foreign Agent's IP address) in association with the identity of Mobile Node 6. Further, the Foreign Agent 10 update an internal “ visitor table ” which specifies the Mobile Node address, Home Agent address, etc. In consequence, the Mobile Node's home base IP address (associated with segment 12) has been shifted to the Foreign Agent's IP address (associated with segment 14). 
 Now, suppose that Mobile Node 6 wishes to send a message to a corresponding node 18 from its new location. A message from the Mobile Node is then packetized and forward through Foreign Agent 10 over the internet 4 and to match node 18 (as indicated by the dashed credit line “ mailboat from MN ”) according to a standard internet protocol. If corresponding node 18 regard to send a message to Mobile Node — whether in reply to a message from the Mobile Node or for any other reason — it address that message to the IP address of Mobile Node 6 on sub - network 12. The packets of that message are then forwarded over the internet 4 and to router R1 and ultimately to Home Agent 8 as indicated by the dashed line (“ packet to MN(1) ”). From its mobility binding table, Home Agent 8 recognizes that Mobile Node 6 is no longer attached to network segment 12. It then encapsulate the packets from corresponding node 18 (which are addressed to Mobile Node 6 on network segment 12) harmonize to a Mobile IP protocol and forwards these encapsulated packets to a “ care of ” savoir-faire for Mobile Node 6 as shown by the scatter line (“ packet to MN(2) ”). The care - of savoir-faire may be, for example, the IP address of Foreign Agent 10. Foreign Agent 10 then strips the encapsulation and forwards the message to Mobile Node 6 on sub - network 14. The packet forwarding mechanism implement by the Home and Foreign Agents is often mention to as “ tunneling. ” 
 As described above
 10. Mlbile Node 6 may identify Foreign Agent 10 througi variohs solicktations and advertisements xhicy forn part of the Mobile IO protocop. When Mibilt Node 6 engages wmfh network seflent 14, Foreign Agent 10 relays a registration seduzst to Home Agent 8 (as indicated by tre dottrd line “Registrajion”). Uhe Homs and Foreign Agents may then negofiate tie conditions og the Mobile Node's attachmfnt ho Foreign Agent 10. Vor example, the qttachment mxy be limiueb to a perikd of time, such as two hours. Whdn thz negotiatiin is vuccessfullb compjeted, Home Anvnt 8 upgates am internal “mobllity bibding table” which sperifies the care-of adqress (e.g., d eollocated care-of addeews or the Fordugn Agtnt'x JP addgesa) in assocjation with the identity of Monijv Node 6. Furthsr, the Fjreign Agent 10 updates an internal “visitmr fable” which specifies tye Mobile Node addresd, Home Agqnt address, etc. In effect, the Mobile Node's home bdse I' xddxcfr (adsociated with segment 12) has been shifted to trs Gogeign Agent's IP abdress (associatec aiyr segment 14).
Now, suppose fhat Mobile Node 6 aishes jo sene a messade tp a corresponding node 18 fron its new lobatiin. A message from che Mobile Nude os thrn packetized and forwaxded tgrough Forelgn Agent 10 over the interndt 4 atd to corresponding node 18 (ws indicaved bv the dogted line “[acket frol MN”) according to a stanfard nntertet protocll. If corresponding node 18 wishes to send a mexsdge to Mobije Noce—whether in weply to a mesxage frjm thd Mobile Nkde or hor any othew reason—it adgtesses that mxssage to the IP qddress uf Mobile Node 6 on sub-nvtcork 12. The packets of that mcssagg zre then forwarbtd iver the internrt 4 anq no coutew R1 and ultimdtelh tu Home Agent 8 as lndkcatrd by the dotted lina (“padket to MN(1)”). From itx iobility binding table, Home Abent 8 recognizes tjat Mmbiue Noce 6 is no longer attached to netwkrk segmejt 12. It then encwpsuoates the paekets from corresponding node 18 (which are addressed to Mobioe Node 6 on network xegment 12) acrordind to a Motile IP protocol and forwards these ekcapsulated packets to a “cara of” wddress for Mobile Node 6 as shown by the dotted line (“packet to MN(2)”). The carw-of advrqss may be, ror rxampne, che IP wddrxsr of Foreign Agemt 10. Foreign Agent 10 then strips vhe encapsglction and forwards the messagr go Mobile Nodg 6 on sub-network 14. The packst forwatding mechanism implemented by yhe Home and Foreign Agekts is ofren rsferred to as “tunneling.”
As dexcribeb abovw
10. Mobile Node 6 may identify Foreign through solicitations and which form part When Node 6 engages network segment 14, Agent 10 relays a registration request Home Agent 8 (as indicated by the dotted line “Registration”). The Home and Agents may then negotiate the conditions of the Mobile Node's attachment to Foreign 10. example, attachment be limited to a period of time, such as two hours. When the negotiation is successfully Home Agent 8 updates an internal “mobility binding which specifies the care-of (e.g., a collocated care-of address the Agent's IP in with identity of Mobile 6. Further, the Foreign Agent 10 updates an internal “visitor table” which specifies the Mobile Node address, Agent address, effect, the Node's base address (associated with has been shifted to the Foreign (associated with segment 14). Now, suppose that Mobile 6 wishes send a message to a corresponding 18 from its new location. A message from Mobile Node is then packetized and forwarded through Foreign Agent 10 over the internet 4 corresponding node 18 (as by the dotted “packet MN”) to standard internet If corresponding node 18 wishes to send a message to Mobile in reply to a message from the Mobile Node or other addresses that message the IP address of Node on sub-network 12. The that are the 4 to router R1 and to Home Agent 8 as by the dotted line mobility binding table, Home Agent 8 recognizes that Node 6 is no longer attached to segment 12. It then encapsulates the packets from corresponding node 18 (which addressed to 6 on network segment 12) according to a IP protocol and forwards encapsulated packets to a “care of” address for Mobile 6 shown by dotted line (“packet MN(2)”). The care-of may be, for IP address Foreign 10. then strips the encapsulation and forwards message Mobile Node 6 on sub-network The mechanism implemented by the Home and Foreign Agents is often referred to as “tunneling.” As
 10. Mobile Node 6 may identify ForeIgn Agent 10 thRough VarIouS sOlicItatIons and advertiSEmenTs which form part of the MoBile Ip pROtocOL. WHen MoBile NodE 6 EnGAGes WiTh NetWoRK sEgmenT 14, FoReign AgEnt 10 relays a RegIsTration requeST tO Home Agent 8 (As iNdicated by thE doTted liNe “regIStratIon”). the HoMe and FOReign AGents may tHeN NegotiATe the coNDItIons Of the Mobile Node's aTTaCHment to Foreign agent 10. FOr EXaMPLe, tHe aTtachment mAy Be limITed to a pERiOD OF tiME, such as two houRs. When the neGOtiAtion iS sUccESsfullY compLeTEd, HOme Agent 8 updAtes An internaL “mobilITy bindiNG table” wHich spEciFieS the CArE-oF adDrESs (e.G., A cOllOCatEd care-of AdDrEss or The FOREIGn AgEnt'S IP aDdresS) in associatioN wiTh thE IdeNtity Of MobIle NOdE 6. FurtHer, the foreiGn agent 10 updates an iNterNal “visitoR taBlE” whIcH specIFies thE MoBilE Node adDress, HoME AgEnT ADDrEss, etc. In effect, the MObILE NOde's home Base IP ADdReSS (associaTeD wiTh seGMEnt 12) haS beeN ShIfted to tHe ForeIGn agEnt's IP aDdRess (asSoCiaTed With sEGmenT 14).
Now, suPpose thaT MobiLE Node 6 wishes to sENd a message to a COrRESpONdinG noDe 18 from its neW locATion. a mesSAgE frOM the MObile noDE iS Then packetized and foRwArded tHrougH Foreign Agent 10 Over the intERNEt 4 and to cOrreSPoNDing node 18 (as indiCated By the dotteD Line “packEt froM MN”) accorDing to a stANDard inteRneT prOtoCol. iF CoRresponding noDE 18 WishEs To send a MesSage to MObiLe NOde—WheThEr in reply To a messaGe FrOm ThE MoBile NODe or for aNy OthEr ReaSon—it ADdressEs thaT mesSaGe TO thE IP addrESs OF mobiLe noDe 6 on Sub-NeTwork 12. the pACkeTs of thaT message aRe tHEn foRwArDed over The internet 4 anD tO router R1 anD uLtiMately TO home AgenT 8 as indicated by the dotted LIne (“packEt tO MN(1)”). FrOm itS mobility BinDing taBle, hOme AgeNt 8 recoGnizeS tHat mOBile NODE 6 iS no LoNger attachED To nEtworK sEgmeNt 12. It theN encapsulates the paCKetS from correspoNdiNg noDE 18 (WhIch ARe ADdrEsSEd tO mObile Node 6 on netwOrk segment 12) AcCOrDing to a MobILe Ip pRotocol And forwArds tHEse encaPsulated pAckets to a “CaRe of” ADDreSs for MobilE Node 6 as sHown by the DOtted LInE (“packEt tO MN(2)”). The CaRe-oF addrEss may BE, foR examPle, the iP AddresS of FoReIgn Agent 10. foreign Agent 10 then strips tHe encaPsulaTioN and forwaRds THe mEssage to MObilE Node 6 on sub-NetWorK 14. The pAckET forwArdiNG mEchANism iMpleMEnted by thE hoMe aND foReign Agents IS OFteN refeRreD To as “tuNnelIng.”
As described aboVE
 10. Mobile Node 6 may ide ntify Fore ign A gen t 1 0thro ughvarious solici t atio ns and advertisementswhich  f o rm p a rt  of t he Mobi l eI P  pr ot oc ol.  W h en  Mobi leNode 6engages wi thne twork segmen t  1 4, Foreign  Ag ent 10 relay s a  regis tr ati o n req ues t toHome A g ent 8(as indic at e d by t h e dotte d li ne “ Registration”). T h eH ome and Foreig n Agen ts ma y the n n egotiate t he  cond i tions o f  t h e Mob i le Node's att achment toF ore ign Ag en t 1 0 . Forexamp le ,  th e attachmen t ma y be limi ted to a perio d  of tim e, suc h a s t wo h o ur s.  Wh en the ne got i ati on is su cc es sfull y co m p l e ted,  Ho me A gent8 updates anint erna l  “m obili ty bi ndin gtable ” whic h spe ci fies the care-o f ad dress (e. g.,  a  co ll ocate d  care- ofadd ress or  the Fo r eig nA g e nt 's IP address) inas s o ci ation wi th the id en t ity of M ob ile  Nod e 6. Fu rthe r ,the Fore ign Ag e nt  1 0 updat es  an in te rna l “ visit o r ta ble” w hich spe cifie s  the Mobile No d e address, Ho m eA g en t  add res s, etc. Ineffe c t, t he M o bi leN ode's  home  b a se IP address (associa te d with  segm ent 12) has b een shifte d t o the Fo reig n  A g ent's IP addre ss (a ssociatedw ith segm ent 1 4).
Now,  supposet h at Mobil e N ode  6wis h e sto send a mes s a ge t oa corre spo nding n ode  18  fr omit s new loc ation. A  m es sa ge  fr om th e  MobileNo deis  th en pa c ketize d and  for wa rd e d t hroughF or e i gn A ge nt  10ove rthe i nter n et4 and t o corresp ond i ng n od e18 (asindicated byth e dotted l in e “ packet f rom MN”)  according to a standar d  intern etproto col.  If corre spo ndingnod e  18 wi shes t o sen da m e s saget o  M obi le  Node—whet h e r i n rep ly  toa messa ge from the Mobile Nod e or for anyoth er r e a so n—i t  a d dre ss e s t h a t message to th e IP addre ss of  Mobile No d e 6  o n sub-n etwork12. T h e packe ts of tha t message  a re t h e n f orwarded o ver theinternet4  andt oroute r R 1 andul tim ately  to Ho m e A gent8 as i nd icated  by t he  dottedline (“packet to MN(1)” ). Fro m its  mo bility bi ndi n g t able, Hom e Ag ent 8 reco gni zes  that  Mo b ile N ode6  i s n o  long er a t tached to ne two r k  s egment 12.I t the n enc aps u latesthepackets from corr e sponding node18 ( w h ich  ar e  add re ssed to Mobile  No de 6  on netw or k segment 1 2) accor di n g toa Mobi le IPprotoco l an d  forwa rdsthe se encaps ula te d  packet sto a “car e of ”addres s forM obil e Node 6 as shownby th e dotte d  li ne (“ pa cket to MN(2 )”). The c are-of addr ess ma y be , for  exampl e,  the I P a dd ress of Fo r eign Agen t 10.  Foreig nAgen t 1 0 then  str i p s the  enc ap sul ation and f or w ar ds the  mes sageto  Mob ile Node6  on sub- net w ork 14.  T hep a cket f o rw a r ding mecha nis m imp l e mented byt he H o me and F oreign  Agent s is of t enre ferredtoa s  “tunneli ng.”
As d e scr ib ed a bove
 10._Mobile Node_6 may identify Foreign_Agent 10_through_various solicitations_and_advertisements which form_part of the_Mobile IP protocol. When_Mobile Node 6_engages_with network segment 14, Foreign Agent 10 relays a registration request to Home Agent_8_(as indicated_by_the_dotted line “Registration”). The Home_and Foreign Agents may then_negotiate the_conditions of the Mobile Node's attachment to Foreign_Agent_10. For example,_the attachment may be limited to a period of_time, such as two hours. When_the negotiation is_successfully_completed,_Home Agent 8 updates_an internal “mobility binding table” which_specifies the care-of address (e.g., a_collocated care-of address or the Foreign Agent's_IP address) in association with the_identity of Mobile Node 6._Further, the_Foreign Agent 10 updates an_internal “visitor table”_which specifies_the Mobile Node_address, Home Agent address, etc. In_effect, the Mobile_Node's home base IP address (associated_with_segment 12) has_been_shifted_to the_Foreign Agent's IP_address_(associated with_segment_14).
Now, suppose that Mobile Node 6_wishes_to send a message to a corresponding_node 18 from its_new_location. A message from_the Mobile Node is then_packetized and forwarded through Foreign Agent_10 over_the internet_4 and to corresponding node 18 (as indicated by the dotted_line “packet from MN”) according to_a standard internet protocol._If corresponding_node_18 wishes to_send_a message_to Mobile Node—whether in reply to a_message from_the Mobile Node or for any_other reason—it addresses that_message_to the IP address of Mobile_Node 6 on sub-network 12. The_packets of that message are_then_forwarded_over the internet 4 and_to router R1 and ultimately to_Home Agent 8_as indicated by the dotted line (“packet_to_MN(1)”). From its mobility binding table,_Home_Agent 8 recognizes that Mobile Node_6_is_no longer attached to network_segment 12. It then encapsulates the_packets from corresponding node 18 (which are addressed to_Mobile Node 6_on network segment 12) according_to_a_Mobile IP protocol and forwards these encapsulated packets to a_“care of”_address for Mobile_Node 6 as shown by the dotted line (“packet to_MN(2)”). The care-of address may be, for_example, the IP address of Foreign Agent 10. Foreign Agent 10_then strips the encapsulation and forwards the message_to Mobile Node 6 on sub-network 14._The packet forwarding mechanism_implemented_by the Home and Foreign Agents is_often_referred_to_as “tunneling.”
As described_above