draft-ietf-regext-rfc7483bis-03.txt   draft-ietf-regext-rfc7483bis-04.txt 
REGEXT Working Group S. Hollenbeck REGEXT Working Group S. Hollenbeck
Internet-Draft Verisign Labs Internet-Draft Verisign Labs
Intended status: Standards Track A. Newton Intended status: Standards Track A. Newton
Expires: 15 April 2021 AWS Expires: 24 April 2021 AWS
12 October 2020 21 October 2020
JSON Responses for the Registration Data Access Protocol (RDAP) JSON Responses for the Registration Data Access Protocol (RDAP)
draft-ietf-regext-rfc7483bis-03 draft-ietf-regext-rfc7483bis-04
Abstract Abstract
This document describes JSON data structures representing This document describes JSON data structures representing
registration information maintained by Regional Internet Registries registration information maintained by Regional Internet Registries
(RIRs) and Domain Name Registries (DNRs). These data structures are (RIRs) and Domain Name Registries (DNRs). These data structures are
used to form Registration Data Access Protocol (RDAP) query used to form Registration Data Access Protocol (RDAP) query
responses. responses.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 15 April 2021. This Internet-Draft will expire on 24 April 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 8, line 41 skipping to change at page 8, line 41
4. Common Data Structures 4. Common Data Structures
This section defines common data structures used in responses and This section defines common data structures used in responses and
object classes. object classes.
4.1. RDAP Conformance 4.1. RDAP Conformance
The data structure named "rdapConformance" is an array of strings, The data structure named "rdapConformance" is an array of strings,
each providing a hint as to the specifications used in the each providing a hint as to the specifications used in the
construction of the response. This data structure MUST appear in the construction of the response. This data structure MUST appear in the
topmost JSON object of a response. topmost JSON object of a response. A response to a "help" request
will include identifiers for all of the specifications supported by
the server. A response to any other request will include only
identifiers for the specifications used in the construction of the
response. The set of returned identifiers MAY vary depending on the
authorization level of the client.
An example rdapConformance data structure: An example rdapConformance data structure:
"rdapConformance" : "rdapConformance" :
[ [
"rdap_level_0" "rdap_level_0"
] ]
Figure 3 Figure 3
skipping to change at page 85, line 13 skipping to change at page 85, line 13
02: Changed "registrant" to "registrar" in the description of the 02: Changed "registrant" to "registrar" in the description of the
"transfer" event action to address erratum 6158. Added IANA "transfer" event action to address erratum 6158. Added IANA
instructions to correct the description of the value in the instructions to correct the description of the value in the
registry. Added text to Section 4.2 to note that "self" and registry. Added text to Section 4.2 to note that "self" and
"related" "href" URIs MUST NOT be the same. Added text to "related" "href" URIs MUST NOT be the same. Added text to
Section 4.2 to describe return of IDNs in LDH name format. Section 4.2 to describe return of IDNs in LDH name format.
03: Added text to note that the "fn" member of a contact object MAY 03: Added text to note that the "fn" member of a contact object MAY
be empty in Section 3. be empty in Section 3.
04: Added text to clarify rdapConformance requirements in
Section 4.1.
Authors' Addresses Authors' Addresses
Scott Hollenbeck Scott Hollenbeck
Verisign Labs Verisign Labs
12061 Bluemont Way 12061 Bluemont Way
Reston, VA 20190 Reston, VA 20190
United States United States
Email: shollenbeck@verisign.com Email: shollenbeck@verisign.com
URI: https://www.verisignlabs.com/ URI: https://www.verisignlabs.com/
 End of changes. 5 change blocks. 
5 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/