A method comprising: receiving, at a network node within a network, a packet from another network node (504, 206, 502) within the network; identifying, within the packet, a label stack that includes a plurality of labels that collectively represent at least a portion of a label-switched path within the network; popping, from the label stack, a label that corresponds to a next hop of the network node included in the label-switched path; assigning, by the network node, the label to the next hop such that any packet whose label stack includes the label assigned to the next hop is forwarded to the next hop unless the next hop has failed; receiving, at the network node, a reservation message that includes labels assigned to network nodes included in the label-switched path; creating, at the network node, a context table in connection with the next hop; recording, within the context table, the labels assigned to the network nodes included in the label-switched path; determining, based at least in part on the label, that the next hop has experienced a failure that prevents the packet from reaching a destination via the next hop; and in response to determining that the next hop has experienced the failure, identifying a backup path that: merges with the label-switched path at a next-to-next hop included in the label-switched path; and enables the packet to bypass the failed next hop and reach the destination, wherein identifying the backup path comprises searching the context table for at least one bypass label assigned to at least one bypass network node included in the backup path by: identifying, within the label stack, a subsequent label that: resides subsequent to the label popped from the label stack; and corresponds to the next-to-next hop included in the label-switched path, and locating, within the context table, the bypass label assigned to the bypass network node included in the backup path based at least in part on the subsequent label, and applying the bypass label to the packet at the network node prior to forwarding the packet via the backup path; and upon identifying the backup path, forwarding the packet to the next-to-next hop via the backup path. receiving, at a network node within a network, a packet from another network node (504, 206, 502) within the network; identifying, within the packet, a label stack that includes a plurality of labels that collectively represent at least a portion of a label-switched path within the network; popping, from the label stack, a label that corresponds to a next hop of the network node included in the label-switched path; assigning, by the network node, the label to the next hop such that any packet whose label stack includes the label assigned to the next hop is forwarded to the next hop unless the next hop has failed; receiving, at the network node, a reservation message that includes labels assigned to network nodes included in the label-switched path; creating, at the network node, a context table in connection with the next hop; recording, within the context table, the labels assigned to the network nodes included in the label-switched path; determining, based at least in part on the label, that the next hop has experienced a failure that prevents the packet from reaching a destination via the next hop; and in response to determining that the next hop has experienced the failure, identifying a backup path that: merges with the label-switched path at a next-to-next hop included in the label-switched path; and enables the packet to bypass the failed next hop and reach the destination, merges with the label-switched path at a next-to-next hop included in the label-switched path; and enables the packet to bypass the failed next hop and reach the destination, wherein identifying the backup path comprises searching the context table for at least one bypass label assigned to at least one bypass network node included in the backup path by: identifying, within the label stack, a subsequent label that: resides subsequent to the label popped from the label stack; and corresponds to the next-to-next hop included in the label-switched path, and locating, within the context table, the bypass label assigned to the bypass network node included in the backup path based at least in part on the subsequent label, and identifying, within the label stack, a subsequent label that: resides subsequent to the label popped from the label stack; and corresponds to the next-to-next hop included in the label-switched path, and resides subsequent to the label popped from the label stack; and corresponds to the next-to-next hop included in the label-switched path, and locating, within the context table, the bypass label assigned to the bypass network node included in the backup path based at least in part on the subsequent label, and applying the bypass label to the packet at the network node prior to forwarding the packet via the backup path; and upon identifying the backup path, forwarding the packet to the next-to-next hop via the backup path.