DRIP Registry HTTP Interface
draft-wiethuechter-drip-registry-http-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Adam Wiethuechter , Stuart W. Card , Robert Moskowitz | ||
| Last updated | 2023-03-31 (Latest revision 2022-09-27) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 document defines an HTTP based interface using either JSON or CBOR for object encodings for the DRIP Registry from a DRIP Provisioning Agent (DPA) to support DRIP Entity Tag (DET) and its additional information registration into a DRIP Identity Management Entity (DIME). The Registry is a logically required component of a DIME that handles the various DNS functions for DRIP registration and lookup using DETs.
Authors
Adam Wiethuechter
Stuart W. Card
Robert Moskowitz
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)