The rescap Resolution Protocol
draft-ietf-rescap-proto-main-01
| Document | Type | Expired Internet-Draft (rescap WG) | |
|---|---|---|---|
| Author | Paul E. Hoffman | ||
| Last updated | 2000-08-09 | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | WG state | WG Document | |
| 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 can be found at:
https://www.ietf.org/archive/id/draft-ietf-rescap-proto-main-01.txt
https://www.ietf.org/archive/id/draft-ietf-rescap-proto-main-01.txt
Abstract
The rescap protocol is a general client-server resolution protocol that translates resource identifiers to a list of attributes. For instance, a rescap client can ask a rescap server for the attributes of a particular mail user. rescap is very light-weight and acts only as a resolution protocol, not a directory service. This document describes the main features of the protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)