Skip to content

Latest commit

 

History

History
26 lines (14 loc) · 2.72 KB

File metadata and controls

26 lines (14 loc) · 2.72 KB

Data Sources

ASNForge v0.1 uses public-safe source classes by default.

RIR delegated stats provide registry allocation information, including ASN ranges, allocation status, allocation date, RIR, and registration_country. This is registry data, not geolocation.

BGP prefix-origin snapshots provide observed routing state. v0.1 implements normalized CSV/TSV input with prefix,origin_asn,collector,observed_at and the bgp.tools bulk table export at https://bgp.tools/table.jsonl. The bgp.tools export provides JSON Lines records with CIDR, ASN, and Hits; ASNForge maps these to prefix-origin observations with collector bgp.tools.

ASN catalog enrichment uses https://bgp.tools/asns.csv, which provides ASN, name, and coarse class fields. ASNForge uses it for asn_name, asn_org, conservative asn_type, tags, and confidence. Manual overrides still take precedence.

ASN signal enrichment uses static raw CSV outputs from IP-Knowledge-Layer and ASN-Signal-Graph. These feeds add controlled ASN tags such as cloud, cdn, crawler, vpn-adjacent, tor-adjacent, privacy-service, security, and suspicious. They are infrastructure context signals, not enforcement verdicts or risk scores.

GeoFeed-Harvester is intentionally not merged into ASNForge v0.1 outputs. Geofeed data describes prefix geolocation assertions, while ASNForge uses registration_country for RIR allocation country and avoids mixing allocation country with geolocation. Geofeed ingestion belongs in a separate GeoIP/geofeed artifact family unless a future schema adds explicit geofeed fields.

The research-caida profile supports CAIDA ASRank, AS2Org, and AS relationships bulk files from local paths or explicitly configured URLs. The default research config uses:

  • https://publicdata.caida.org/datasets/as-organizations/latest.as-org2info.txt.gz
  • the latest *.as-rel2.txt.bz2 file resolved from https://publicdata.caida.org/datasets/as-relationships/serial-2/

ASNForge does not crawl ASRank APIs. If ASRank is needed, provide an operator-managed CSV file through asrank_paths or asrank_urls. CAIDA-derived fields are optional ASN-table enrichment fields and are not included in MMDB records.

The deterministic normalized fixture is scoped to config/local-dev.yaml. The public-safe profile uses the bgp.tools bulk table and ASN catalog exports, plus static ipanalytics signal CSVs, and sets an identifying HTTP User-Agent.

Manual overrides provide curated corrections for ASN name, organization, type, tags, confidence, and field sources. Overrides take precedence over inferred fields.

Future optional source profiles may include PeeringDB, RPKI VRPs, and CAIDA AS Rank / AS relationships / AS2Org. CAIDA is not included in the default v0.1 public-safe release.