irrd causes a large amount of disk churn.
For IRR imports this can be mitigated by using NRTM to insert deltas instead of performing a full re-import every time.
Right now nothing similar exists for the RPKI importer. It looks like by default all >400k rows are re-imported every 3600s.
Routinator3000 supports the json-delta endpoint that allows to request a delta of the ROA changes since the last request using the session and serial identifier.
Is it possible to implement support for the json-delta endpoint in irrd?
Appendix:
Example json-delta output
# curl "http://127.0.0.1:8323/json-delta?session=1683714697&serial=2698"
{
"reset": false,
"session": "1683714697",
"serial": 2699,
"fromSerial": 2698,
"announced": [
{
"type": "routeOrigin",
"asn": "AS210058",
"prefix": "45.91.192.0/24",
"maxLength": 24
},
{
"type": "routeOrigin",
"asn": "AS0",
"prefix": "138.185.229.0/24",
"maxLength": 24
},
{
"type": "routeOrigin",
"asn": "AS134932",
"prefix": "2400:7e60::/32",
"maxLength": 32
}
],
"withdrawn": [
{
"type": "routeOrigin",
"asn": "AS47065",
"prefix": "138.185.229.0/24",
"maxLength": 24
}
]
}
irrd causes a large amount of disk churn.
For IRR imports this can be mitigated by using NRTM to insert deltas instead of performing a full re-import every time.
Right now nothing similar exists for the RPKI importer. It looks like by default all >400k rows are re-imported every 3600s.
Routinator3000 supports the
json-deltaendpoint that allows to request a delta of the ROA changes since the last request using the session and serial identifier.Is it possible to implement support for the
json-deltaendpoint in irrd?Appendix:
Example json-delta output