Versioning in the Registration Data Access Protocol (RDAP)
draft-gould-regext-rdap-versioning-02
Document | Type |
Expired Internet-Draft
(regext WG)
Expired & archived
|
|
---|---|---|---|
Authors | James Gould , Dan Keathley , Mario Loffredo | ||
Last updated | 2024-06-10 (Latest revision 2023-12-08) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
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 is available in these formats:
Abstract
This document describes an RDAP extension for an extensible set of versioning types with the features of identifying the RDAP extension versions supported by the server, the RDAP extension versions included in an RDAP response, and enabling a client to specify the desired RDAP extension versions to include in the RDAP query and RDAP response.
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.)