Versioning in the Registration Data Access Protocol (RDAP)
draft-gould-regext-rdap-versioning-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | James Gould , Dan Keathley , Mario Loffredo | ||
| Last updated | 2023-11-13 (Latest revision 2023-05-12) | ||
| RFC stream | (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 describes an RDAP extension for identifying RDAP extension versions supported by the server, RDAP extension versions included in an RDAP response, and enabling a client to specify the desired RDAP extension versions to include in an RDAP response using machine-parseable identifiers.
Authors
James Gould
Dan Keathley
Mario Loffredo
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)