BGP is a "grass roots", Internet Engineering Task Force (IETF) - Request For Comment (RFC), based protocol.

A BGP solution is desirable under certain circumstances:

• If the network engineer is connecting two or more networks, via one or more, intermediating networks.

• If the networks each have no ab initio knowledge, of the target, or intermediating networks.

• If the networks are organized into globally unique contiguous, numerical node address ranges, of reasonable minimum size.

• If the connection points between networks each have an equivalent version of BGP source code, which have established quasi-static peering sessions.

• If the connection points between networks have transit paths between them which have enough available bandwidth to handle BGP session messages, and also transit traffic simultaneously.

• If an intermediating network has within itself an adequate transit path, between the two connection points.

Notably the path within a network administration domain, from the source, or target end node(s) to the first BGP session supporting transit node encountered is assumed a de facto intrinsic event if no autonomous system number change is in effect.