URC Scenarios and Requirements
draft-ietf-uri-urc-req-00
| Document | Type |
Expired Internet-Draft
(candidate for uribof WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael H. Mealling , Dr. Ron Daniel | ||
| Last updated | 1995-03-27 (Latest revision 1994-11-23) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | Call For Adoption By WG Issued | |
| 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
This draft describes the place of the Uniform Resource Characteristic (URC) service within the overall context of Uniform Resource Identification on the Internet. It presents several scenarios illustrating how the URC service might be used. From these usage scenarios, we derive a set of requirements that any proposed URC services must meet.
Authors
Michael H. Mealling
Dr. Ron Daniel
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)