The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] [mpls] draft-weilian-mpls-fast-reroute-ext-00
On reading the introduction of this draft, I am unclear about the motivation and problem that it is trying to solve. The draft says: "However, for N:1 backup, after the protected tunnel switches to the backup tunnel, the protocol state should still be refreshed through sending protocol messages of the protected tunnel along the path of backup tunnel. Once FRR switchover occurs, abundant Refresh messages of the protected tunnel are transmitted along the path of backup tunnel, intermediate and tail nodes of the backup tunnel will allocate abundant useless labels." As I understand the bypass tunnel mechanism, the Refresh messages for the protected tunnels are sent to the merge node via the backup tunnel; this means that the Refresh messages are encapsulated and not seen by the intermediate nodes of the backup tunnel. When the refresh message is seen by the tail node of the backup tunnel (which is the MP), the MP will look-up the state and label assigned to the associated protected LSP and refresh the state and provide the label back. I don't see that there is any allocation of useless labels. Could you clarify an example where this happens? In particular, could you pull the problem from RFC4090? Thanks, Alia _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls
|
|