AS 4134 does not provide an organisation name · ipverse/feedback · Discussion #11

Sainan
Mar 22, 2024

So, its name is detected as "No.31,Jin-rong Street" which is the address, but it should be "China Telecom" instead.

Cloudflare Radar and PeeringDB do seem to handle this ASN correctly. I'm not sure how exactly, maybe via manual overwrites.

Replies: 1 comment 11 replies

trick77
Mar 24, 2024
Maintainer

Here's what AS4134 publishes as WHOIS descr:

aut-num: AS4134
as-name: CHINANET-BACKBONE
descr: No.31,Jin-rong Street
descr: Beijing
descr: 100032

Unless they change it, it's going to be the street name in ipverse, since it's all automatically processed, no manual overrides or special handling of certain AS for the foreseeable future.

11 replies

@Sainan

Sainan Mar 24, 2024
Author

I'm not asking you to open-source your codebase, just e.g. add an overwrite map, which is populated from a JSON or CSV that's downloaded from a public git repo.

I don't think you have any problems with people using the data you publish for commercial products given that it's published under a licence that seems to basically just dedicate it to the public domain.

Otherwise, if money is an issue, I'd be glad to donate if there were options. I like open data. :)

@Sainan

Sainan Mar 24, 2024
Author

FWIW, we already have manually-curated data to determine if an ASN is a hosting provider (for VPN detection) in a freestanding WASM module, so I've just added a new routine to supply name overwrites (calamity-inc/soup-extra-data@ed61efb), and then apply those on the client (calamity-inc/Soup@d02f622).

I do like WASM as an ISA, but the tooling around it is not great, so this might not work for everyone. I will also need to update clients now before they see any changes, but unless this is implemented directly in ipverse, this is as much as I can do.