Feature Request:

Generic OID - Generic RDAP info

Use case:

• I have an object tree 1.2.3
• No I have a service e.g. registring an OID to an user, e.g. 1.2.3.2999 let it be a website for example
• so 1.2.3 is a "factory/generator" RA for delegatting/handing out 1.2.3.? OIDs

Idea:

• 1.2.3 is a service managed by an external website service managing the OIDs for the subtree
• So to look up an OID by RDAP the client queries the RDAP Server for 1.2.3 example.com/rdap/oid/1.2.3.2999
• example.com looks up 1.2.3.2999 at website-serice.example.net which would be the RDAP server for 1.2.3**.** <--- The dot indicates it is for suboids while 1.2.3 stay managed by example.com how we did it with the OIDplus System OIDs in the RDAP bootstrap file

To run a complete RDAP OIDplus solution on website-serice.example.net is to much overhead and NOT what I want, as it just has to manage sub-trees/local ids like e.g. website (2999).
Instead it should provide an API for it type of objects (websites), as like 1.2.3.?.x

Instead to delegate the whole RDAP request to website-serice.example.net, the
RDAP server on example.com/rdap/oid/1.2.3.2999 should use INTF_OID_1_3_6_1_4_1_37553_8_1_8_8_53354196964_1276945 public function rdapExtensions() or equivalent in wtf-plugins add_filter( 'oidplus_rdapExtensions',... );
to resolve the RDAP request by just a 1.2.3.?.x template ... e.g.

It runs the template which is setup for 1.2.3 and adds extra info for 1.2.3.? by hooking the external API.

This CAN be done right now by the plugins and the wtf plugins, but it must be done by a developer per instance.

What do you think?

Ich notiere das mal als Idee damit es nicht verloren geht und setze mich bald mal selber dran, ich möchte nicht den Rahmen sprengen und noch mehr Baustellen eröffnen.