OMP advertises the following types of routes:

OMP routes $($also called vRoutes$)$Prefixes that establish reachability between end points that use the OMP$-$orchestrated transport network. OMP routes can represent services in a central data center, services at a branch office, or collections of hosts and other end points in any location of the overlay network. OMP routes require and resolve into TLOCs for functional forwarding. In comparison with BGP$,$ an OMP route is the equivalent of a prefix carried in any of the BGP AFI$/$SAFI NLRI fields $($Address Family Indicator $($AFI$),$ Subsequent Address Family Identifiers $($SAFI$),$ Network Layer Reachability Information $($NLRI$))$ fields$).$

Transport locations $($TLOCs$)$Identifiers that tie an OMP route to a physical location. The TLOC is the only entity of the OMP routing domain that is visible to the underlying network, and it must be reachable via routing in the underlying network. A TLOC can be directly reachable via an entry in the routing table of the physical network, or it can be represented by a prefix residing on the outside of a NAT device and must be included in the routing table. In comparison with BGP$,$ the TLOC acts as the next hop for OMP routes.