The Use of Registries
draft-wilde-registries-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Erik Wilde | ||
| Last updated | 2020-01-31 (Latest revision 2019-07-30) | ||
| 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
Registries for Internet and Web protocols fulfill a wide range of tasks, ranging from low-level networking aspects such as packet type identifiers, all the way up to application-level protocols and standards. This document summarizes some of the reasons of why, when, and how to use registries. It serves as an informative reference for specification writers considering whether to create and manage a registry, allowing them to better understand some of the issues associated with certain design and operational decisions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)