It appears that Randy Bush <ra...@psg.com> said: >not positive this i sthe best wg. but regexr is about epp etc.
I agree that this is worth thinking about, but this draft feels like it either says too much or too little. >From the too little angle, what do the URLs point to? Will they all be CSV files with a prefix in the first field? Are they defined one RFC at a time or is there some sort of schema that clients can look up to see what the fields are? R's, John PS: If we move this ahead we definitel need to talk to regext about how this would be reconciled with RDAP queries. >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
