Hi George, It's really hard to find the summary information specially lme (+ others, like me) who have limited technical skill to analyze the summary data .
*is it possible to share any URL which present infographic information about NIR allocated dada ? * Regards, Jahangir On Thu, Feb 20, 2020 at 4:08 AM George Michaelson <[email protected]> wrote: > Having spoken to Anurag off-list, the problem he was facing has been > resolved, but to keep the community informed, here is a summary. > > 1) delegated file records about AS numbers are *blocks* of AS Numbers. > > As noted by Jamie, the entry for many of the AS numbers in the delegated > and delegated-extended reports is not a single line per AS, but a block: > Part of the file includes a count of AS, which combined with the value of > the AS represents the “size” of the range. Single AS lines have a “size” of > 1. > > So (for example): (as used by Jamie) > > apnic|IN|asn|58897|10|20130417|allocated|A918EDB2 > > Is a block of 10 AS starting with AS58897. Its AS58897 to AS58906. > > If you try to “grep” in the file for any ASN in the range 58898 to 58907, > there is no match. You need to “parse” the file with code, and construct > the list of actual ASN or use interval arithmetic to find the range > containing the value. (See attached Python3 code) > > > 2) Blocks of AS are mainly in the NIR > > Most AS block records are in the NIR. They are recorded as “in use” at the > point of delegation into the NIR, but unfortunately due to some process > issues we do not currently have the more specific holder information in > APNIC registry records. We are working to correct this, and have started a > process with all the NIR to get details on the NIR Sub-accountm (NIR > member) which holds the ASN. > > When this data is collected we will be updating centrally managed registry > records, and these AS block records in the delegated and delegated-extended > reports will be replaced by individual records about each AS, showing > economy and the unique custodian code of that resource holder. > > > 3) More information about AS holders are in the NIR managed Whois and RDAP > sources. > > If you want to use an online query, the sources which we collate and serve > about each NIR’s Whois data are available at whois.apnic.net and in > rdap.apnic.net, for all APNIC holdings including the NIR. > > > APNIC’s Whois service is a federation over all Whois sources we collate, > each shown as a distinct “source:” tagged record in the response. > > Some NIR are operating inside APNIC Whois, and do not currently share data > back into our service from their in-economy Whois service and therefore we > dont have a "source: <NIR>" for every NIR. We always serve information > about the resource, It may still return an “as-block:" record if no more > specific Whois "aut-num:" record exists. > > RDAP is a machine parsable format which is also part of a global > fully-connected service, and is by far the best mechanism to see the > registration details about all internet number resources for machine > processing. The “nicinfo” command from ARIN ( > https://github.com/arineng/nicinfo) is a great example of a service which > can find any Internet Number Resource worldwide (in any RIR) from the > command line. -It has a human friendly default display but can also show > the raw JSON format RDAP data. > > > -George > > _______________________________________________ > apnic-talk mailing list > [email protected] > https://mailman.apnic.net/mailman/listinfo/apnic-talk
_______________________________________________ apnic-talk mailing list [email protected] https://mailman.apnic.net/mailman/listinfo/apnic-talk
