Hi all, Ahead of Vienna I want to surface a small piece of input to the referrals work.
On the 6th I posted draft-ranjbar-regext-rdap-subordinate-referrals-00, describing an optional, holder-designated RDAP referral from a registry's response to the holder's own RDAP service for the more-specifics below a registered domain or an allocation: https://datatracker.ietf.org/doc/draft-ranjbar-regext-rdap-subordinate-referrals/ In review, Jasdip made a suggestion that I think improves it and widens its use: name the link relation for what it targets, the base URL of a downstream RDAP service, rather than for the resource-holder role. So the -00 placeholder "rdap-resource-holder" becomes "rdap-base", and the holder-designated subordinate referral becomes one application of a general relation. That generalisation lines up with at least three cases the group already cares about: - Delegated and hybrid RPKI: draft-ietf-regext-rdap-rpki addresses the same base-URL discovery need with an "rdap-help" relation. A single general "rdap-base" could serve both, and I would rather converge than mint two near-identical relations. I would value input on whether that reconciliation makes sense. - RIR-to-NIR referrals. - Replacing holder-side RWhois/SWIP with an RDAP pointer. -01 also (a) carries the relation in both lookup and search responses, for names and number resources, (b) spells out how a holder-designated server discovers the registry's base URL for the reverse "up"/"rdap-up" link, via the RFC 9224 bootstrap registries, and (c) registers "rdap-base" with IANA. The submission tool is closed for the pre-meeting cut-off, so I will upload -01 as soon as it reopens after the 18th. In the meantime I wanted the rdap-base framing, and especially the rdap-base/rdap-help question, in front of the list rather than sitting in private mail. My preference remains for this to be folded into draft-ietf-regext-rdap-referrals rather than progressing on its own. Thanks, Kaveh
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
