Dear Colleagues,
On 13 May 2025, at 17:03, Randy Bush <randy@psg.com> wrote:
i received a suggestion to mention this on the ripe wg list. similar to geofeed, it allows one to document the prefix length one is using.
Publishing End-Site Prefix Lengths https://datatracker.ietf.org/doc/draft-ietf-opsawg-prefix-lengths/
This document specifies how to augment the Routing Policy Specification Language (RPSL) inetnum: class to refer specifically to prefixlen comma-separated values (CSV) data files and describes an optional scheme that uses the Resource Public Key Infrastructure (RPKI) to authenticate the prefixlen data files.
randy
There was some discussion on the End-Site Prefix Lengths proposal at the RIPE90 DB-WG session, and no objections have been raised. Accordingly the RIPE NCC DB team now plan to implement the prefixlen: attribute according to the draft RFC: https://datatracker.ietf.org/doc/draft-ietf-opsawg-prefix-lengths/ And with the following implementation details: * We will add an optional, single "prefixlen:" attribute to the inetnum and inet6num object templates. * The attribute value will be validated to require a HTTPS URL * We will not otherwise validate the URL location or content * Either prefixlen: or remarks: prefixlen will be allowed but not both in the same object (same as for geofeed). * The prefixlen: attribute will not be filtered by default and will be included in the nightly dump, split files and NRTM. Please reply with any comments or questions. Regards Ed Shryane RIPE NCC