Say in README why RouteWatch exists (closes #204) #209

Merged
clawbot merged 1 commits from issue-204-rationale into next 2026-10-27 21:34:09 +01:00
Collaborator

Rewrites the README's Rationale section from the owner's words on #204.

What it now says, in order:

  • RouteWatch exists to serve our other services as an internal API for information about IP addresses.
  • It follows routing table updates from RIPE RIS Live and keeps the table itself. From that table it sees which AS each address is routed to, and which announced prefix holds it and how big that prefix is.
  • WHOIS details of each AS add to that. They are kept in the database and fetched again once 30 days old, so an IP lookup never waits for WHOIS.
  • So our own services can ask RouteWatch instead of each working it out.

The old section's sentences on what RIS Live does and does not give stay, shortened, after the main point. Its sentence on prefix pages is dropped.

Disclosures:

  • Judgement call: the geojs lookups the owner mentions are left out. They are not built, and the README describes only what is built (rules on #157). They are proposed on #203.
  • Judgement call: "our" is kept from the owner's words ("our other services", "our own services").

Model: opus-5-5

Rewrites the README's Rationale section from the owner's words on https://git.eeqj.de/sneak/routewatch/issues/204. What it now says, in order: - RouteWatch exists to serve our other services as an internal API for information about IP addresses. - It follows routing table updates from RIPE RIS Live and keeps the table itself. From that table it sees which AS each address is routed to, and which announced prefix holds it and how big that prefix is. - WHOIS details of each AS add to that. They are kept in the database and fetched again once 30 days old, so an IP lookup never waits for WHOIS. - So our own services can ask RouteWatch instead of each working it out. The old section's sentences on what RIS Live does and does not give stay, shortened, after the main point. Its sentence on prefix pages is dropped. Disclosures: - Judgement call: the geojs lookups the owner mentions are left out. They are not built, and the README describes only what is built (rules on https://git.eeqj.de/sneak/routewatch/issues/157). They are proposed on https://git.eeqj.de/sneak/routewatch/issues/203. - Judgement call: "our" is kept from the owner's words ("our other services", "our own services"). Model: opus-5-5
clawbot added the needs-review label 2026-10-27 21:25:20 +01:00
clawbot self-assigned this 2026-10-27 21:25:20 +01:00
clawbot added 1 commit 2026-10-27 21:25:20 +01:00
The Rationale section now gives the owner's reason for the program: it
is an internal API that our other services ask about IP addresses. It
sees which AS routes each address and which announced prefix holds it
from its own routing table. WHOIS details of each AS, kept in its
database, add to that.

What RIS Live does and does not give stays, shortened. Planned geojs
lookups are left out, because the README describes only what is built.

Model: opus-5-5
Author
Collaborator

PASS: the Rationale section keeps the owner's meaning from #204 and is ready to squash-merge into next.

  • Judgement call: the unchanged opening line "It keeps the whole routing table in memory" is read as all of RouteWatch's own table being in memory, so it does not contradict the Rationale's "holds only the routes announced since RouteWatch first started".
  • Judgement call: "looks them up again once they are 30 days old" is read as accurate, although the fetcher takes stale ASes one at a time, so some wait longer than 30 days.

Model: opus-5-5

PASS: the Rationale section keeps the owner's meaning from https://git.eeqj.de/sneak/routewatch/issues/204 and is ready to squash-merge into `next`. - Judgement call: the unchanged opening line "It keeps the whole routing table in memory" is read as all of RouteWatch's own table being in memory, so it does not contradict the Rationale's "holds only the routes announced since RouteWatch first started". - Judgement call: "looks them up again once they are 30 days old" is read as accurate, although the fetcher takes stale ASes one at a time, so some wait longer than 30 days. Model: opus-5-5
clawbot merged commit 6d4f3e3419 into next 2026-10-27 21:34:09 +01:00
clawbot deleted branch issue-204-rationale 2026-10-27 21:34:09 +01:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/routewatch#209