Skip to content

Latest commit

 

History

History
68 lines (40 loc) · 1.66 KB

File metadata and controls

68 lines (40 loc) · 1.66 KB
layout page
title Analysis
permalink /analysis

Unexpected cases

Definitions:

Target network: AS that peers either directly with PEERING or with the falcon routeserver, and receives our prefix advertisements.

Case 1.1:

Announcement via: Falcon routeserver

Target network: is falcon peer, is monitor

Prefix visibility: None or partial

alt text

Case 1.2:

Announcement via: direct peering with target network

Target network: is direct peer, is monitor

Prefix visibility: None or partial

alt text


Case 2.1:

Announcement via: Falcon routeserver

Target network: is monitor, is customer of a falcon peer

Prefix visibility: None or partial

alt text

Case 2.2:

Announcement via: direct peering

Target network: is monitor, is customer of the direct peer

Prefix visibility: None or partial

alt text


Case 3.1:

Announcement via: Falcon routeserver

Target networks: A is falcon peer, B is customer of A, both are monitors, (??B is not falcon peer??)

Prefix visibility: Mismatch in prefix visibility between A and B

alt text

Case 3.2:

Announcement via: direct peering

Target networks: A is direct peer, B is customer of A, both are monitors, (??B is not direct peer??)

Prefix visibility: Mismatch in prefix visibility between A and B

alt text