This is the next-hop IP address this dynamically-signaled co-routed tunnel currently uses, computed by RSVP-TE and, because the tunnel is co-routed, defining the shared next hop for both the outbound signaling and the anchor point of the return path. An admin watches this for unplanned changes after a re-signal, aware that on a co-routed tunnel a next-hop change affects both directions of the bidirectional circuit simultaneously, unlike an associated tunnel where legs move independently. For example, this next hop shifting from 172.16.40.1 to 172.16.40.9 confirms the entire bidirectional circuit re-signaled onto a new shared path, not just one leg.