Dismiss
There will be a system update on Friday, May 5th, 6 PM ET. You may experience a brief service interruption.
Browse Prior Art Database

URI Resolution Services Necessary for URN Resolution (RFC2483)

IP.com Disclosure Number: IPCOM000003063D
Original Publication Date: 1999-Jan-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 12 page(s) / 28K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Mealling: AUTHOR [+2]

Abstract

Retrieving the resource identified by a Uniform Resource Identifier (URI) [1] is only one of the operations that can be performed on a URI. One might also ask for and get a list of other identifiers that are aliases for the original URI or a bibliographic description of the resource the URI denotes, for example. This applies to both Uniform Resource Names (URNs) and Uniform Resource Locators (URLs). Uniform Resource Characteristics (URCs) are discussed in this document but only as descriptions of resources rather than identifiers.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 11% of the total text.

Network Working Group M. Mealling

Request for Comments: 2483 Network Solutions, Inc.

Category: Experimental R. Daniel, Jr.

Los Alamos National Laboratory

January 1999

URI Resolution Services

Necessary for URN Resolution

Status of this Memo

This memo defines an Experimental Protocol for the Internet

community. It does not specify an Internet standard of any kind.

Discussion and suggestions for improvement are requested.

Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

Retrieving the resource identified by a Uniform Resource Identifier

(URI) [1] is only one of the operations that can be performed on a

URI. One might also ask for and get a list of other identifiers that

are aliases for the original URI or a bibliographic description of

the resource the URI denotes, for example. This applies to both

Uniform Resource Names (URNs) and Uniform Resource Locators (URLs).

Uniform Resource Characteristics (URCs) are discussed in this

document but only as descriptions of resources rather than

identifiers.

A service in the network providing access to a resource may provide

one or some of these options, but it need not provide all of them.

This memo specifies an initial set of these operations that can be

used to describe the interactions provided by a given access service.

It also suggests guidelines that should be adhered to when those

operations are encoded in a protocol.

1. Introduction

In the course of formulating current proposals [2] regarding URNs

[3], it became apparent that requiring servers to manage all of the

desired functions or requiring clients to process varied information

returned by a server was unrealistic and a barrier to adoption. There

needed to be some way for a client to be able to identify a server

that specialized in the complex and another that specialized in the

simple (but fast). Also, in subsequent conversations it became

obvious that, in most cases, some of the operations were

inappropriate or difficult for certain identifiers.

The Problem

In the process of learning about a resource in the Internet, there

are a variety of possible functions that may be important and/or

useful, such as discovery of locators, names, descriptions, and

accessing the resource itself. A given service may support only a

subset of these; hence, it is important to describe such an access

service by the types of functions supported and the resources of

which it has some knowledge. For example, in the framework for an RDS

described in [5] the RDS itself may provide URLs [6][7], while the

resolvers may provide descriptions, URLs, or even the resources

themselves. The design of...