The MPLS WG Archive

[Apratim Mukherjee <apratim.mukherjee@metro-optix.com>]

hi harish,

normally , you would store the incoming and outgoing object separately in
the Path State since you need the incoming object to check for changes in
the incoming refresh message while you need the outgoing object while
buiding the Path Refresh message. Sometimes , the outgoing object can be
calculated every time you send a refresh , but this is implementation
dependant .
e.g OutAdspec could be stored as a separate field or recalculated every time
u send a refresh . 
OutIntegrity could be stored as a separate field which is recalculated evry
time an outgoing object changes or it could be recalculated while sending
each refresh message. 


-----Original Message-----
From: Harish Kumtakar [mailto:harishk3@rediffmail.com]
Sent: Wednesday, September 04, 2002 11:28 AM
To: rsvp@isi.edu
Cc: schultz@io.iol.unh.edu; mpls@UU.NET
Subject: help


hi,

    what i understood after reading RFC 2205 and 2209 is that, 
when a node receives a PATH message it will store or update the 
info. contained in the message into corresponding PATH state and 
then forwards the PATH message (the message may be modified) to 
the next hop.

   my question is will that node stores the info that is modified 
by it(in case the PATH message is modified) somewhere (i mean, in 
some state?).