Efficient RDAP Referrals
draft-brown-rdap-referrals-02
| Document | Type |
Replaced Internet-Draft
(regext WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Gavin Brown , Andy Newton | ||
| Last updated | 2025-09-01 (Latest revision 2025-05-19) | ||
| Replaced by | draft-ietf-regext-rdap-referrals | ||
| 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 | Paweł Kowalik | ||
| IESG | IESG state | Replaced by draft-ietf-regext-rdap-referrals | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | kowalik@denic.de |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes how RDAP servers can provide HTTP "Link" header fields in RDAP responses to allow RDAP clients to efficiently determine the URL of related RDAP records for a resource.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)