2 name: Layer 3 cross connect
3 maintainer: Neale Ranns <nranns@cisco.com>
5 - cross connect all ingress traffic on an L3 interface to an output FIB path.
6 - the path can describe any output (with the exception of MPLS labels)
7 - The same functions can be achieved by using a dedicated VRF for the table
8 and adding a default route with the same path. However, the L3XC is more
9 efficient in memory and CPU
13 properties: [API, CLI, MULTITHREAD]