Implicit and Explicit Null Label in MPLS networks
The MPLS Label Stack Encoding (RFC 3032) specifies two reserved values (among others) that are useful in the last hop of a Label Switched Path (LSP):
- 0: explicit NULL. Can be used in signaling protocols as well as label headers.
- 3: implicit NULL. Used in signaling protocols only. It should never appear in the label stack. Its use in a signaling protocol indicates that the upstream router should perform penultimate hop popping (PHP; remove the top label on the stack).
The implicit NULL should be used whenever possible, as the PHP reduces the amount of lookup required on the last hop of an LSP (sometimes that could mean the difference between hardware and software lookup).
With implicit NULL, the penultimate router performs a simple label lookup, pops the label, and sends an IP packet to the egress router. The egress router performs a simple IP lookup.
When using the implicit NULL, there is no label on the last link in the MPLS network. QoS actions on that link are thus based on the IP packet DSCP value.
With explicit NULL, the penultimate router swaps an MPLS label with a NULL label, and sends a labeled packet to the egress router. The egress router performs an MPLS label lookup and finds a NULL label which triggers another lookup in IP routing table.
Explicit NULL could be used in environments where you want to use MPLS QoS values that are different from IP DSCP/IP Precedence values.
When the egress router signals an explicit NULL, a packet traversing the last link in the MPLS network carries a NULL label, the EXP bits in the label stack are preserved throughout the MPLS network, and the QoS actions performed by the penultimate router can be based on MPLS EXP bits.
By default, Cisco IOS routers advertise implicit NULL with LDP. To change this behavior, use the mpls ldp explicit-null global configuration command.