Please view the following table.
| | CR LSP | LDP LSP | SR TE |
| Label allocation | Label distribution and diffusion through MPLS extension protocol. Each LSP is assigned a label. When there are multiple LSPs, multiple labels need to be allocated on the same link. The label resources are used more and the label forwarding table has a large maintenance workload. | LDP nodes can share labels with different LSPs, and save label resources compare to RSVP. If load balance, LDP FRR, or REMOTE LFA is configured, the label occupation specification will be N*3. | Label allocation: Label distribution and diffusion through the IGP extension protocol. Only one label is assigned to each link. All LSPs share this label, which reduces the occupation of label resources and reduces the maintenance workload of the label forwarding table. Control plane: The signaling control protocol is an extension of the IGP protocol, no need for MPLS control protocol and reducing the number of protocols. Scalability: The transit device does not perceive the tunnel. The tunnel information is carried in each packet. It does not need to maintain the tunnel status information. High Scalability. Path adjustment and control: The transit device does not perceive the tunnel. The service path can be controlled by labeling the packets of the ingress node. When a node in the path fails, the controller recalculates the path and updates the label stack of the ingress node to complete the path adjustment. |
| Algorithm | CSPF(Constraint Shortest Path First) | SPF（Shortest Path First） |
| ECMP | no support | support |
| Control diversity | Support bandwidth reservation, bandwidth constraints, link colors, and explicit paths | Label forwarding, no traffic control |
| Configuration&Maintenance | Complicated | Simple |
| Rollback time | Fast（TE FRR, TE HSB） | Slow（based on IGP Convergence time, OSPF FRR configured now） |
