BACKGROUND

Information Centric Networking (ICN) is an approach to evolve Internet infrastructure away from a host-centric paradigm based on perpetual connectivity and the end-to-end principle to a network architecture in which the focal point is “named information” (i.e., content or data). In ICN, data becomes independent from location, application, storage, and means of transportation, enabling in-network caching and replication. The benefits of ICN include improved efficiency, better scalability with respect to information/bandwidth demand, and better robustness in challenging communication scenarios.

SUMMARY

Embodiments include systems, methods, and apparatuses for providing a failover procedure to one or more alternative Hypertext Transfer Protocol (HTTP) sources in case of an error response in an Information Centric Networking (ICN) network. A first network access point (NAP) may receive a request for a HTTP resource from a requestor. The HTTP resource may include a fully qualified domain name (FQDN). The first NAP may request the HTTP resource from a first server associated with the FQDN. The first NAP may receive an error message that the HTTP resource is not available from the first server. The first NAP may publish a message to a rendezvous point (RVZ). The message may include a list of excluded node identifiers (NIDs) of one or more NAPs that have been previously contacted and have not provided the HTTP resource. The first NAP may receive a forwarding identifier (FID) of a second NAP from a topology manager (TM). The second NAP may be associated with a second server that is associated with the FQDN. A NID of the second NAP may not be on the list of excluded NIDs. The first NAP may request the HTTP resource from the second NAP. Once the HTTP resource is received, the first NAP may send the HTTP resource to the requestor.

