Abstract: Techniques and architecture are described for service and/or application specific underlay path selection in fabric access networks. An egress tunnel router (ETR) registers service requirements of a connected application server, e.g., an end point known by host/device detection, config, or CDC type protocols, to a fabric control plane, e.g., a map server/map resolver (MSMR). The fabric control plane, while replying to a map request from an ingress tunnel router (ITR), sends service parameters in the map reply. While installing a tunnel forwarding path in hardware, i.e., map cache, the ITR may utilize a probing mechanism to ensure that the ITR chooses the right underlay adjacency, e.g., routing locator(s) (RLOC(s)), that can satisfy the service requirements provided by the fabric control plane. Only RLOC(s) that comply with the service requirements are installed in the map cache along with the required service parameters.

Abstract: A traffic flow based map cache refresh may be provided. A computing device may receive a dropped packet message when a packet associated with a flow having a destination and a source was dropped before it reached the destination. Next, in response to receiving the dropped packet message, a map request message may be sent to a Map Server (MS). In response to sending the map request message, a map response message may be received indicating an updated destination for the flow. A map cache may then be refreshed for the source of the flow based on the updated destination from the received map response message.

Abstract: A traffic flow based map cache refresh may be provided. A computing device may receive a dropped packet message when a packet associated with a flow having a destination and a source was dropped before it reached the destination. Next, in response to receiving the dropped packet message, a map request message may be sent to a Map Server (MS). In response to sending the map request message, a map response message may be received indicating an updated destination for the flow. A map cache may then be refreshed for the source of the flow based on the updated destination from the received map response message.