Handle System Protocol (ver 2.1) Specification

Abstract

Several groups within the IETF and IRTF have discussed the Handle System and its relationship to existing systems of identifiers. The IESG wishes to point out that these discussions have not resulted in IETF consensus on the described Handle System, nor on how it might fit into the IETF architecture for identifiers. Though there has been discussion of handles as a form of URI, specifically as a URN, these documents describe an alternate view of how namespaces and identifiers might work on the Internet and include characterizations of existing systems which may not match the IETF consensus view. AbstractThe Handle System is a general-purpose global name service that allows secured name resolution and administration over the public Internet. This document describes the protocol used for client software to access the Handle System for both handle resolution and administration. The protocol specifies the procedure for a client software to locate the responsible handle server of any given handle. It also defines the messages exchanged between the client and server for any handle operation.

Assigning Digital Object Identifiers to RFCs

“…DOIs are an application of the Handle System defined by RFCs [RFC3650], [RFC3651], and [RFC3652]. For example, a DOI for an RFC might be as follows:…”

On the utility of identification schemes for digital earth science data: an assessment and recommendations

“…The Handle System is specified in Request for Comments (RFC) 3560 (Sun et al 2003a), 3651 (Sun et al 2003b), and 3652 (Sun et al 2003c), published by the IETF for review by the Internet community. The Handle System also has been designated as the standard required for uniquely identifying repositories and learning content distributed by the United States military (Department of Defense 2006).…”

The cache-and-forward network architecture for efficient mobile content delivery services in the future internet

“…The CNF architecture is independent of the style of naming an endpoint in that an endpoint might be identified by using a handle [44], url (sanjoy@winlab.rutgers.edu), a role (fireman, police officer etc. ), or by using names of local relevance (Jim's laptop, Sue's cellphone).…”

“…A possible implementation of FNRS would be the handle system [44]. Attributes corresponding to a CID would consist of a variety of information pertinent to the content, such as, Content Hash, Content Creator, Content Access Rights, etc.…”