ResCap Requirements
draft-ietf-rescap-req-01
| Document | Type | Expired Internet-Draft (rescap WG) | |
|---|---|---|---|
| Last updated | 2015-10-14 (latest revision 2002-06-24) | ||
| Stream | IETF | ||
| Intended RFC status | Informational | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Scott Hollenbeck | ||
| IESG note | Open issues not resolved after 18 months. WG concluded. Marking dead. | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-rescap-req-01.txt
Abstract
A variety of resource identifiers have been widely deployed on the Internet as a means of identifying various resources, services, and destinations. However, a means of attaching a set of attributes or characteristics to a given resource identifier and subsequently assessing those attributes or characteristics has not been specified and deployed. Two tasks are envisioned. The first task will be to define a general resolution protocol that will translate resource identifiers to a list of attributes. The second task will be to define an administrative model and update protocol that can be used to set up and maintain the information the resolution protocol accesses.
Authors
John Beck (john.beck+rescap@sun.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)