Using JSContact in Registration Data Access Protocol (RDAP) JSON Responses
draft-loffredo-regext-rdap-jcard-deprecation-04
| Document | Type |
Replaced Internet-Draft
(regext WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mario Loffredo , Gavin Brown | ||
| Last updated | 2021-03-15 (Latest revision 2021-01-24) | ||
| Replaced by | draft-ietf-regext-rdap-jscontact | ||
| 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 | Replaced by draft-ietf-regext-rdap-jscontact | |
| 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 which represents entity contact information in JSON responses using JSContact.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)