In steady state, refreshing is performed hop-by-hop, to allow merging.
-
When the received state differs from the stored state, the stored state is updated.
-
If this update results in modification of state to be forwarded in refresh messages, these refresh messages must be generated and forwarded immediately, so that state changes can be propagated end-to-end without delay.
-
Propagation of a change stops when and if it reaches a point where merging causes no resulting state change.
-
This minimizes RSVP control traffic due to changes and is essential for scaling to large multicast groups.
|
