Skip to content
This repository has been archived by the owner on Jul 15, 2021. It is now read-only.

provide clear reachability information ("Is this entire prefix reachable?") on the "BGP Preview" page / API #47

Open
nusenu opened this issue Sep 19, 2018 · 2 comments
Milestone

Comments

@nusenu
Copy link

nusenu commented Sep 19, 2018

Instead of expecting that people look at all the lines that a bgp preview lookup may return and have them check in their head or via scripts if all the VALIDs compensate for the same IP space as the INVALID, lets add a simple red/green icon/flag to clearly show the reachability of a prefix:

red: not (completely) reachable (completely or partially invalid)
or
green: completely reachable (because it is VALID, UNKNOWN or has alternative routes in an ROV environment)

Since green is already used for "VALID" (not "reachable") you might want to clearly show what is what, maybe use "reachable" and "unreachable" in addition to the colors.

https://rpki-validator.ripe.net/bgp-preview
example prefix:
209.99.224.0/20 (red)

@lolepezy
Copy link
Contributor

Hi,

We do not use the terminology such as 'reachable', so I am not sure if I understand correctly what you mean.

Basically,

  • green VALID for a prefix means that there exists at least one ROA that covers the prefix.
  • yellow (or orange)
    • INVALID ASN means we see a ROA for the same (or larger) prefix but ASN from the ROA is different.
    • INVALID LENGTH means we see the ROA with the correct ASN and prefix but the ROAs maximal length field doesn't allow for the prefix to be that small.
  • grey UNKNOWN means there are no ROAs with the same of covering prefix

These are the only statuses RPKI uses. What is the definition of 'reachable' you suggest and how to relate 'reachable' with the aforementioned statuses?

@nusenu
Copy link
Author

nusenu commented Jan 23, 2019

thanks for picking this up.

Your question should be answered here:
https://nusenu.github.io/RPKI-Observatory/unreachable-networks.html#what-is-a-rpki-unreachable-network

@dacruz dacruz added this to the Phase 2 milestone Jan 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants