As currently implemented, if a client wanted to resolve 10.100.1000/abc, it would send a resolution request for 0.NA/10.100.1000 to the GHR. If there was no such record at the GHR, but there was a record for 0.NA/10.100 with an HS_SITE.PREFIX value, the GHR would respond with a "prefix referral" response (a handle response with response code 303), indicating that the prefix may be resolvable at the site given by the HS_SITE.PREFIX value. This is another handle service which is not the GHR but an LHS service that happens to be responsible for some prefixes. (It does correspond to what you had labeled GHR2.) The client will now send the send resolution request for 0.NA/10.100.1000 to this handle service, and may receive a normal handle resolution response with an HS_SITE value, indicating where the client may send a request for 10.100.1000/abc. Current clients do support the behavior I have outlined. If you are interested in minting your own two-dot prefixes and running a server where those prefixes can be resolved, you should reach out to CNRI (or other MPAs) about possible contractual arrangements. Robert
|
_______________________________________________ Handle-Info mailing list Handle-Info@cnri.reston.va.us http://www.handle.net/mailman/listinfo/handle-info