2003
DOI: 10.17487/rfc3650
|View full text |Cite
|
Sign up to set email alerts
|

Handle System Overview

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
66
0

Year Published

2004
2004
2023
2023

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 98 publications
(66 citation statements)
references
References 14 publications
(14 reference statements)
0
66
0
Order By: Relevance
“…In this section we report on part of our experiences with constructing aLP s. The experimental data was collected over the CNRI Handle testbed [13], -an emerging IETF/IRTF standard that provides a global name service for use over WANs. We gathered data from November to December 2002.…”
Section: Methodsmentioning
confidence: 99%
See 1 more Smart Citation
“…In this section we report on part of our experiences with constructing aLP s. The experimental data was collected over the CNRI Handle testbed [13], -an emerging IETF/IRTF standard that provides a global name service for use over WANs. We gathered data from November to December 2002.…”
Section: Methodsmentioning
confidence: 99%
“…It is expected that WAA must scale to millions of client and server pairs. As an example, consider a global name service such as the Handle protocol, an IETF/IRTF standard from CNRI-Corporation for National Research Initiatives [13]. Handle provides a namespace, a name resolution service, and protocols for digital object location and access.…”
Section: Introductionmentioning
confidence: 99%
“…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).…”
Section: Technical Valuementioning
confidence: 99%
“…Security provisions include authentication of clients and servers to prevent unauthorized administrative access, capabilities to encrypt or disable access to confidential values, and options to request a digitally signed response (Sun et al 2003a). The absence of design limits on the number of services within the Handle System, the number of sites within each service, or the number of handle servers within each site facilitates replication, reliability, and scalability (Corporation for National Research Initiatives 2007a).…”
Section: Technical Valuementioning
confidence: 99%
“…Very briefly, the DNS ( [15], [16]) and the World Wide Web built its URL scheme ( [3]) on top of it were designed to be global in reach, hierarchical in assignment, management and resolution, and long-lived, but not persistent. Later, Sollins' Information Mesh project ( [23]) and related work on URNs in the IETF made persistence a primary goal, as did the Handle System ( [26]), based on a global handle registry.…”
mentioning
confidence: 99%