Skip to main content

RDAP jCard Profile

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Tom Harrison , George G. Michaelson
Last updated 2020-01-08 (Latest revision 2019-07-07)
Replaces draft-rdap-jcard-profile
RFC stream (None)
Intended RFC status (None)
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:


The Registration Data Access Protocol (RDAP) is used by Regional Internet Registries (RIRs) and Domain Name Registries (DNRs) to provide access to their resource registration information. RDAP uses jCard to convey information about individuals and other entities: for example, for the technical contact for a domain name. In practice, server operators are only using a small subset of jCard's functionality, so in an effort to simplify the requirements on the client side, this document defines a jCard profile for use with RDAP.


Tom Harrison
George G. Michaelson

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)