RDAP jCard Profile
draft-rdap-jcard-profile-00

Document Type Replaced Internet-Draft (individual)
Last updated 2019-07-07
Replaced by draft-harrison-regext-rdap-jcard-profile
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-harrison-regext-rdap-jcard-profile
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-rdap-jcard-profile-00.txt

Abstract

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.

Authors

Tom Harrison (tomh@apnic.net)
George Michaelson (ggm@apnic.net)

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