Dear RIPE DB wg, The RDAP for querying ip and network information on rdap.db.ripe.net is really useful. Currently you support the rdapConformance level "rdap_level_0" and this is missing the CIDR or Prefix Information about the Length/Mask. Other RIR have implemented a rdap conformance level "cidr0" for this: * https://rdap.arin.net/registry/ip/9.9.9.9 * https://rdap.apnic.net/ip/1.1.1.1 with the desired information: "cidr0_cidrs": [ { "v4prefix": "1.1.1.0", "length": 24 } ] Information about the Origin ASN is also available by arin with "arin_originas0", which is also very helpful, but the format seems to be arin specific and not standardized. May I suggest to also implement the cidr0 level, or even additionally the "origin as" for the RIPE DB RDAP? Kind regards, Benjamin
Dear Benjamin, The “origin as” as observed via ARIN RDAP is a difficult-to-use relic from the past. The concept of “Autonomous System Originations” pre-dates IRR and RPKI. It was the best possible solution at that time; but since then superior solutions became available. I submitted a policy proposal to deprecate this functionality in full: https://www.arin.net/participate/policy/drafts/2021_8/ Perhaps a different approach applicable to your objectives is to merge RDAP information with RPKI derived information (both in JSON format). Through this path one can achieve both a more fine-grained granularity (RPKI ROAs can be configured at routing boundaries, rather than assignment boundaries), and have greater assurances the information was produced by the Internet Number Resource holder. A frequently updated JSON formatted view on the RPKI can be found here: https://console.rpki-client.org/vrps.json (this kind of file can also be produced by installing an RPKI validator on your own infrastructure). Kind regards, Job On Wed, 26 Jan 2022 at 12:19, Benjamin Pereto via db-wg <db-wg@ripe.net> wrote:
Dear RIPE DB wg,
The RDAP for querying ip and network information on rdap.db.ripe.net is really useful.
Currently you support the rdapConformance level "rdap_level_0" and this is missing the CIDR or Prefix Information about the Length/Mask.
Other RIR have implemented a rdap conformance level "cidr0" for this: * https://rdap.arin.net/registry/ip/9.9.9.9 * https://rdap.apnic.net/ip/1.1.1.1
with the desired information: "cidr0_cidrs": [ { "v4prefix": "1.1.1.0", "length": 24 } ]
Information about the Origin ASN is also available by arin with "arin_originas0", which is also very helpful, but the format seems to be arin specific and not standardized.
May I suggest to also implement the cidr0 level, or even additionally the "origin as" for the RIPE DB RDAP?
Kind regards, Benjamin --
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
participants (2)
-
Benjamin Pereto -
Job Snijders