HS_SERV is described in the RFCs, although the description has some outdated details. An HS_SERV value's data is intended to be a handle, the handle record for which has HS_SITE values. Thus it describes a handle service. When an HS_SERV value is in a prefix handle record, the service described by the HS_SERV value can be used to access handles under that prefix. In particular, HS_SERV values in the 0.NA/0.NA record can be used to access prefix handles; thus, the sites indirectly listed via those HS_SERV values are part of the GHR.
What has changed since the publication of the RFCs is (1) a prefix handle can have more than one HS_SERV value, or a mix of HS_SITE and HS_SERV values; and (2) the GHR's servers can also be described by HS_SERV values on 0.NA/0.NA.
Organizationally, each MPA which administers global handle servers has its own HS_SERV value on 0.NA/0.NA. A selection of HS_SITE values remain on the record as well, to enable use by legacy clients which do not understand HS_SERV values on 0.NA/0.NA.
Robert
Hi Robert,
in the file:bootstrap_handles, has the follow information, eg:
{
"index": 20,
"type": "HS_SERV",
"data": {
"format": "string",
"value": "0.GHR/20"
},
"ttl": 86400,
"timestamp": "2015-12-09T17:49:42Z"
},
There is no definition in the rfc3651/rfc3652, what use is it?
Peter Li
_______________________________________________Handle-Info mailing listHandle-Info@cnri.reston.va.ushttp://www.handle.net/mailman/listinfo/handle-info