# US 2010/0142543 A1 · Methods and apparatus to analyze autonomous system peering policies

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2010/0142543 A1
- Document ID: US20100142543A1
- Status: Published application
- Kind: A1
- Application number: 12/331,148
- Filed: 2008-12-09
- Published: 2010-06-10
- Earliest claimed: 2008-12-09
- Assignees: AT&T Intellectual Property I, L.P.
- Inventors: Aman Shaikh; Thomas Bradley Scholl; Ashley Flavel
- Web page: https://patentgrep.com/patent/US20100142543A1

## CPC

- H04L 45/04: {Interdomain routing, e.g. hierarchical routing}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods and apparatus to analyze autonomous system (AS) peering policies are disclosed. A disclosed example method comprises obtaining routing information from two or more border routers of a first AS, wherein the routing information identifies two or more routes to a prefix associated with a second AS, and wherein the second AS is a peer of the first AS, identifying one of the two or more routes as an inferior route advertised by the second AS based on the routing information, and determining whether a routing impact is present within the first AS due to the advertised inferior route.

## Claims

### Claim 1

A method comprising:
obtaining routing information from two or more border routers of a first autonomous system (AS), wherein the routing information identifies two or more routes to a prefix associated with a second AS, and wherein the second AS is a peer of the first AS;
identifying one of the two or more routes as an inferior route advertised by the second AS based on the routing information; and
determining whether a routing impact is present within the first AS due to the advertised inferior route.

### Claim 2 (depends on 1)

A method as defined in claim 1, further comprising generating a routing policy impact report that includes a first value representative of the prefix, a second value representative of the advertised inferior route, and an indicator representative of whether the routing impact is present within the first AS.

### Claim 3 (depends on 1)

A method as defined in claim 1, further comprising determining a traffic impact within the first AS due to the identified inferior route when the routing impact is present within the first AS.

### Claim 4 (depends on 3)

A method as defined in claim 3, wherein determining the traffic impact comprises:
identifying an ingress router associated with a traffic flow;
determining whether the ingress router has a second routing impact due to the advertised inferior route;
when the ingress router experienced the second routing impact, computing a route length increase caused by the second routing impact; and
computing a traffic impact metric based on the route length increase and a data rate associated with the traffic flow.

### Claim 5 (depends on 1)

A method as defined in claim 1, further comprising modifying a configuration of one of the two or more border routers to mitigate the routing impact when the routing impact is present in the first AS.

### Claim 6 (depends on 5)

A method as defined in claim 5, wherein modifying the configuration of the one of the two or more border routers comprises at least one of prepending an AS number associated with the second AS, modifying a MED value, modifying an origin value, modifying a prefix length, or modifying an import policy.

### Claim 7 (depends on 1)

A method as defined in claim 1, wherein determining whether the routing impact is present comprises:
determining a best route advertised for the prefix by the second AS;
announcing the advertised best route to one of the two or more border routers;
selecting a route to the prefix at the one of the two or more border routers, wherein the routing impact is present when a propagation of the selected route within the first AS would cause a selection of a different route within the first AS.

### Claim 8 (depends on 1)

A method as defined in claim 1, further comprising identifying a type of non-canonical peering policy associated with the second AS based on the routing information.

### Claim 9 (depends on 1)

A method as defined in claim 1, wherein obtaining the routing information from the two or more border routers of the first AS comprises at least one of collecting routing information base (RIB) incoming route data from the two or more border routers, collecting RIB post-policy route data from the two or more border routers, or receiving updates from the two or more border routers.

### Claim 10 (depends on 1)

A method as defined in claim 1, wherein the inferior route represents a first route to the prefix advertised at the one of the two or more border routers that has at least one of an inferior ASPath value, an inferior Origin value or an inferior MED value compared to a second route to the prefix advertised at a second of the two or more border routers.

### Claim 11 (depends on 1)

A method as defined in claim 1, wherein the routing impact comprises a change in a selected route for the prefix resulting from the advertised inferior route.

### Claim 12

An apparatus comprising:
a data collector to obtain border gateway protocol (BGP) routing information from two or more border routers of a first autonomous system (AS), wherein the BGP routing information identifies two or more routes to a prefix associated with a second AS, and wherein the second AS is a peer of the first AS;
a route classifier to identify one of the two or more routes as an inferior route advertised by the second AS based on the BGP routing information; and
a route analyzer to determine whether a routing impact is present within the first AS due to the inferior route.

### Claim 13 (depends on 12)

An apparatus as defined in claim 12, further comprising a report generator to generate a routing policy impact report that includes a first value representative of the prefix, a second value representative of the advertised inferior route, and an indicator representative of whether the routing impact is present within the first AS.

### Claim 14 (depends on 12)

An apparatus as defined in claim 12, further comprising a traffic analyzer to compute a traffic impact within the first AS due to the identified inferior route when the routing impact is present within the first AS.

### Claim 15 (depends on 12)

An apparatus as defined in claim 12, further comprising a mitigator to modify a configuration of one of the two or more border routers to mitigate the routing impact when the routing impact is present in the first AS.

### Claim 16 (depends on 15)

An apparatus as defined in claim 15, wherein the mitigator is to at least one of prepend an AS number associated with the second AS, modify a multi-exit discriminator value, modify an origin value, modify a prefix length, or modify an import policy.

### Claim 17 (depends on 12)

An apparatus as defined in claim 12, wherein the route analyzer is to determine whether the routing impact is present by:
determining a best route advertised for the prefix by the second AS;
announcing the advertised best route to one of the two or more border routers;
selecting a route to the prefix at the one of the two or more border routers, wherein the routing impact is present when a propagation of the selected route within the first AS would cause a selection of a different route within the first AS.

### Claim 18 (depends on 12)

An apparatus as defined in claim 12, wherein the data collector is to obtain the BGP routing information from the two or more border routers of the first AS by at least one of collecting routing information base (RIB) incoming route data from the two or more border routers, collecting RIB post-policy route data from the two or more border routers, or receiving BGP updates from the two or more border routers.

### Claim 19

An article of manufacture storing machine-accessible instructions that, when executed, cause a machine to:
obtain border gateway protocol (BGP) routing information from two or more border routers of a first autonomous system (AS), wherein the BGP routing information identifies two or more routes to a prefix associated with a second AS, and wherein the second AS is a peer of the first AS;
identify one of the two or more routes as an inferior route advertised by the second AS based on the BGP routing information; and
determine whether a routing impact is present within the first AS due to the advertised inferior route.

### Claim 20 (depends on 19)

An article of manufacture as defined in claim 19, wherein the machine-accessible instructions, when executed, cause the machine to generate a routing policy impact report that includes a first value representative of the prefix, a second value representative of the advertised inferior route, and an indicator representative of whether the routing impact is present within the first AS.

### Claim 21 (depends on 19)

An article of manufacture as defined in claim 19, wherein the machine-accessible instructions, when executed, cause the machine to determine a traffic impact within the first AS due to the identified inferior route when the routing impact is present within the first AS.

### Claim 22 (depends on 21)

An article of manufacture as defined in claim 21, wherein the machine-accessible instructions, when executed, cause the machine to determine the traffic impact by:
identifying an ingress router associated with a traffic flow;
determining whether the ingress router has a second routing impact due to the advertised inferior route;
when the ingress router experienced the second routing impact, computing a route length increase caused by the second routing impact; and
computing a traffic impact metric based on the route length increase and a data rate associated with the traffic flow.

### Claim 23 (depends on 19)

An article of manufacture as defined in claim 19, wherein the machine-accessible instructions, when executed, cause the machine to modify a configuration of one of the two or more border routers to mitigate the routing impact when the routing impact is present in the first AS.

### Claim 24 (depends on 19)

An article of manufacture as defined in claim 19, wherein the machine-accessible instructions, when executed, cause the machine to determine whether the routing impact is present by:
determining a best route advertised for the prefix by the second AS;
announcing the advertised best route to one of the two or more border routers;
selecting a route to the prefix at the one of the two or more border routers, wherein the routing impact is present when a propagation of the selected route within the first AS would cause a selection of a different route within the first AS.

### Claim 25 (depends on 19)

An article of manufacture as defined in claim 19, wherein the machine-accessible instructions, when executed, cause the machine to identify a type of non-canonical peering policy associated with the second AS based on the BGP routing information.

### Claim 26 (depends on 19)

An article of manufacture as defined in claim 19, wherein the machine-accessible instructions, when executed, cause the machine to obtain the BGP routing information from the two or more border routers of the first AS comprises at least one of collecting routing information base (RIB) incoming route data from the two or more border routers, collecting RIB post-policy route data from the two or more border routers, or receiving BGP updates from the two or more border routers.
