Browse Prior Art Database

Architectural Principles of Uniform Resource Name Resolution (RFC2276)

IP.com Disclosure Number: IPCOM000002837D
Original Publication Date: 1998-Jan-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 19 page(s) / 61K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. Sollins: AUTHOR

Abstract

This document addresses the issues of the discovery of URN (Uniform Resource Name) resolver services that in turn will directly translate URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource Characteristics). The document falls into three major parts, the assumptions underlying the work, the guidelines in order to be a viable Resolver Discovery Service or RDS, and a framework for designing RDSs. The guidelines fall into three principle areas: evolvability, usability, and security and privacy. An RDS that is compliant with the framework will not necessarily be compliant with the guidelines. Compliance with the guidelines will need to be validated separately.

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

Network Working Group K. Sollins

Request for Comments: 2276 MIT/LCS

Category: Informational January 1998

Architectural Principles of Uniform Resource Name Resolution

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

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

Abstract

This document addresses the issues of the discovery of URN (Uniform

Resource Name) resolver services that in turn will directly translate

URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource

Characteristics). The document falls into three major parts, the

assumptions underlying the work, the guidelines in order to be a

viable Resolver Discovery Service or RDS, and a framework for

designing RDSs. The guidelines fall into three principle areas:

evolvability, usability, and security and privacy. An RDS that is

compliant with the framework will not necessarily be compliant with

the guidelines. Compliance with the guidelines will need to be

validated separately.

Table of Contents

1. Introduction..................................................2

2. Assumptions...................................................5

3. Guidelines....................................................7

3.1 Evolution.....................................................7

3.2 Usability....................................................10

3.2.1 The Publisher................................................11

3.2.2 The Client...................................................12

3.2.3 The Management...............................................13

3.3 Security and Privacy.........................................14

4. The Framework................................................18

5. Acknowledgements.............................................23

6. References...................................................23

7. Author's Address.............................................23

8. Full Copyright Statement.....................................24

1. Introduction

The purpose of this document is to lay out the engineering criteria

for what we will call here a Resolver Discovery Service (RDS), a

service to help in the learning about URN (Uniform Resource Name)

resolvers. The term "resolver" is used in this document to indicate

a service that translates URNs to URLs (Uniform Resource Locators) or

URCs (...