Terminology and Use Cases for Interoperability of Identifier Resolution Systems
draft-kahn-dsii-id-res-sys-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Robert E. Kahn , Andrew Maffei | ||
| Last updated | 2013-01-03 (Latest revision 2012-07-02) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Identifier Systems have been in existence for many years and are in widespread use. An opaque identifier conveys essentially nothing about the information identified and must be converted into useful intermediate information, known as state information, before the information being identified can be accessed or used. An identifier that is can be processed by a system in the Internet to provide useful and actionable intermediate state information is said to be resolvable. Although there is ongoing discussion about the value of opaque versus non-opaque identifiers, we assume the existence of a minimal syntax structure for the identifier and also that the resolution mechanisms only knows about the minimal syntax of the identifier. In this document we introduce the notion of interoperability of identifier resolution systems as a key component for enabling interoperability of heterogeneous information systems more broadly, and discuss the role of unique persistent resolvable identifiers. Terminology is proposed to facilitate this discussion and a set of use cases demonstrating the need for interoperability of resolution systems are included.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)