A routing structure is defined for provider edge (PE) routers that will create the ability to recompute best paths based on application criteria. The routing structure may include the use of a network controller which is connected with the internet to receive requests from applications to trigger path re-computation. The controller will peer with PEs to send re-computation information used by the PE to construct an application-aware BGP table and forwarding instance. The PE also defines a new BGP and packet filter to replicate specific BGP paths into the application-aware table. The application-aware BGP and forwarding instance is unique to the requesting application. Thus, each request with a different source/destination combination obtains a discrete table providing separation. When a packet enters the PE from customer edge (CE) or core interface the packet traverses a packet filter that when matched against source/destination is redirected to the appropriate application-aware forwarding table. Once in the application-aware table the packet is then forwarded along the application-aware path achieving the objective. The instantiation of the application-aware BGP and forwarding table is be done based on BGP updates learned from the controller.