1 / 10

An Analysis of BGP Multiple Origin AS (MOAS) Conflicts

An Analysis of BGP Multiple Origin AS (MOAS) Conflicts. Xiaoliang Zhao, et al. Overview. Motivation Classifications of MOAS conflicts. Results Possible explanations for MOAS. Motivation. The last AS in an AS path should be the origin of the BGP routes.

vida
Download Presentation

An Analysis of BGP Multiple Origin AS (MOAS) Conflicts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An Analysis of BGP Multiple Origin AS (MOAS) Conflicts Xiaoliang Zhao, et al. Dongkee LEE (dklee@an.kaist.ac.kr)

  2. Overview. • Motivation • Classifications of MOAS conflicts. • Results • Possible explanations for MOAS. Dongkee LEE (dklee@an.kaist.ac.kr)

  3. Motivation • The last AS in an AS path should be the origin of the BGP routes. Suppose prefix ‘d’ is associated with AS paths, asp1 = (p1, p2, … pn), asp2 = (p1, p2, … pm) If pn != qm : MOAS conflict occurs. • MOAS could be the result of a ‘fault’ or an ‘attack’. • What are the reason for MOAS conflicts and What are the impacts ?” Dongkee LEE (dklee@an.kaist.ac.kr)

  4. Classification of MOAS • prefix ‘d’, asp1 = (p1, p2, … pn), asp2 = (p1, p2, … pm) • OrigTranAS: pn =qj (j < m) AS Pn announces itself as the origin AS and as a transit AS. • SplitView: pi =qj (i < n, j < m) AS Pi announces different routes to different neighbors. • DistinctPaths: pn =qj (for all i in [1..n], j in [1..m] ) There are two totally different routes for the prefix ‘d’. Dongkee LEE (dklee@an.kaist.ac.kr)

  5. Results • Oregon RouteViews data. • Total Number of MOAS Conflicts. Overall 38225 conflicts were observed over 1279 days. • Duration of MOAS Conflicts. 10177 conflicts Dongkee LEE (dklee@an.kaist.ac.kr)

  6. Results • Distribution of MOAS Conflicts Dongkee LEE (dklee@an.kaist.ac.kr)

  7. Results • Distribution of MOAS classes Dongkee LEE (dklee@an.kaist.ac.kr)

  8. Causes of MOAS conflicts – (1) • Exchange Point Addresses. • Prefix associated with an exchange point is directly reachable from all the ASes, at the exchange point. • 30 out of 38225 prefixes. • Multi-homing without BGP. Dongkee LEE (dklee@an.kaist.ac.kr)

  9. Causes of MOAS conflicts – (2) • Multi-homing with Private AS Numbers. • AS number Substitution on Egress (ASE). • Anycast addresses. • Anycast address is intended to originate from multiple ASes. • Faulty or Malicious Configurations. Dongkee LEE (dklee@an.kaist.ac.kr)

  10. The END Dongkee LEE (dklee@an.kaist.ac.kr)

More Related