On 1/22/26 9:01 AM, Gavin Brown wrote: >> The path-based approach works where target of the initial redirect is the >> organization that can answer for the desired object, but not if there is an >> intermediate organization. This may be outside the design goals, but a >> hypothetical TLD -> 2LD -> Registrar relationship would see the intent lost >> on the first redirect, unless the first redirecting server knew the >> capabilities of the intermediate.
Yes, there is a limitation if an intermediate does not understand the extension and the draft should probably note the issue. I am not making the connection about the path-based approach though. Can you elaborate for those of us with fewer brain cells? >> Getting outside my knowledge here, there may be such relationships in the >> number space when considering transfers between RIRs then referrals to LIRs. >> Repeatedly following some relations would not make sense, e.g. rdap-up. >> Again, may be outside the goals of this draft. Yes, there is value in following rdap-up more than once because the allocation hierarchy in many instances contains an org allocating to itself and being able to find the org boundary is useful in some situations. -andy, no hats _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
