REGEXT is where RDAP is defined, and would be a good place for the RDAP projection of this data to be worked on, thats how they handled geofeed. I think the OPSAWG is a fine place to discuss this proposal right now.
I like this proposal a lot. I think it is the right kind of abstraction for a pointer out of whois/RPSL into the most likely the structural form which we have already coded to from georef: -in the delegate of the address resources hands, signed by their RPKI key. Given the probable increase in a need to determine different qualities of prefix length sub-delegation for distinct purpose (geographic, email, BGP & routing related) which have operational qualities, I think its a good fit to talk about here. What I like is that this proposed mechanism instantiates the sub-type registry so that we can talk about the kinds of context we want a refinement of prefix/len binding, and then add a subtype once it's understood and nailed down in an RFC. Having a generic form to point out means the "outer" parse mechanism which clients reading RPSL will need can be standard, the subsequent processing is extensible defined subsequently. The integrity of the data, delegated down from registry process and out into the RPKI signed assertion, I think is a really nice model. I also like that it's short. I would love this to be adopted and I would be happy to work on it. -G On Fri, Oct 18, 2024 at 9:25 PM Randy Bush <ra...@psg.com> wrote: > not positive this i sthe best wg. but regexr is about epp etc. > > randy > > --- > > A new version of Internet-Draft draft-ymbk-opsawg-rpsl-extref-00.txt has > been > successfully submitted by Randy Bush and posted to the > IETF repository. > > Name: draft-ymbk-opsawg-rpsl-extref > Revision: 00 > Title: Generalized RPSL External Reference > Date: 2024-10-18 > Group: Individual Submission > Pages: 6 > URL: > https://www.ietf.org/archive/id/draft-ymbk-opsawg-rpsl-extref-00.txt > Status: https://datatracker.ietf.org/doc/draft-ymbk-opsawg-rpsl-extref/ > HTMLized: > https://datatracker.ietf.org/doc/html/draft-ymbk-opsawg-rpsl-extref > > > Abstract: > > RPSL, which is not a formal standard, has recently added a geofeed: > attribute to the innet[6]num: class to reference data external to > RPSL. There is now a proposal add another attribute, prefixlen:. > This document describes a more general and extensible mechanism for > external references. > > _______________________________________________ > OPSAWG mailing list -- opsawg@ietf.org > To unsubscribe send an email to opsawg-le...@ietf.org >
_______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
