draft-ietf-weirds-json-response-05.txt   draft-ietf-weirds-json-response-06.txt 
Network Working Group A. Newton Network Working Group A. Newton
Internet-Draft ARIN Internet-Draft ARIN
Intended status: Standards Track S. Hollenbeck Intended status: Standards Track S. Hollenbeck
Expires: February 16, 2014 Verisign Labs Expires: April 06, 2014 Verisign Labs
August 15, 2013 October 03, 2013
JSON Responses for the Registration Data Access Protocol (RDAP) JSON Responses for the Registration Data Access Protocol (RDAP)
draft-ietf-weirds-json-response-05 draft-ietf-weirds-json-response-06
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 February 16, 2014. This Internet-Draft will expire on April 06, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 47, line 44 skipping to change at page 47, line 44
[I-D.ietf-weirds-rdap-query] specifies three types of searches: [I-D.ietf-weirds-rdap-query] specifies three types of searches:
domains, nameservers, and entities. Responses to these searches take domains, nameservers, and entities. Responses to these searches take
the form of an array of object instances where each instance is an the form of an array of object instances where each instance is an
appropriate object class for the search (i.e. a search for /domains appropriate object class for the search (i.e. a search for /domains
yields an array of domain object instances). These arrays are yields an array of domain object instances). These arrays are
contained within the response object. contained within the response object.
The names of the arrays are as follows: The names of the arrays are as follows:
o for /domains searches, the array is "domains" o for /domains searches, the array is "domainSearchResults"
o for /nameservers searches, the array is "nameservers" o for /nameservers searches, the array is "nameserverSearchResults"
o for /entities searches, the array is "entities" o for /entities searches, the array is "entitySearchResults"
The following is an elided example of a response to a /domains The following is an elided example of a response to a /domains
search. search.
{ {
"rdapConformance" : "rdapConformance" :
[ [
"rdap_level_0" "rdap_level_0"
], ],
... ...
"domains" : "domainSearchResults" :
[ [
{ {
"handle" : "1-XXXX", "handle" : "1-XXXX",
"name" : "1.example.com", "ldhName" : "1.example.com",
... ...
}, },
{ {
"handle" : "2-XXXX", "handle" : "2-XXXX",
"name" : "2.example.com", "ldhName" : "2.example.com",
... ...
} }
] ]
} }
search_response_example search_response_example
In addition to the arrays, the response object may contain a member In addition to the arrays, the response object may contain a member
named "searchResultsTruncated" which is a boolean. When this value named "searchResultsTruncated" which is a boolean. When this value
is set to true, it indicates the accompanying array did not contain is set to true, it indicates the accompanying array did not contain
skipping to change at page 49, line 30 skipping to change at page 49, line 30
{ {
"value" : "http://example.net/help", "value" : "http://example.net/help",
"rel" : "alternate", "rel" : "alternate",
"type" : "text/html", "type" : "text/html",
"href" : "http://www.example.com/search_policy.html" "href" : "http://www.example.com/search_policy.html"
} }
] ]
} }
], ],
"searchResultsTruncated" : true "searchResultsTruncated" : true
"domains" : "domainSearchResults" :
[ [
... ...
] ]
} }
search_response_truncated_example search_response_truncated_example
10. IANA Considerations 10. IANA Considerations
10.1. RDAP JSON Media Type Registration 10.1. RDAP JSON Media Type Registration
skipping to change at page 67, line 12 skipping to change at page 67, line 12
Applications (IDNA): Definitions and Document Framework", Applications (IDNA): Definitions and Document Framework",
RFC 5890, August 2010. RFC 5890, August 2010.
[RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 [RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
Address Text Representation", RFC 5952, August 2010. Address Text Representation", RFC 5952, August 2010.
[RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010. [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010.
[I-D.ietf-jcardcal-jcard] [I-D.ietf-jcardcal-jcard]
Kewisch, P., "jCard: The JSON format for vCard", draft- Kewisch, P., "jCard: The JSON format for vCard", draft-
ietf-jcardcal-jcard-05 (work in progress), July 2013. ietf-jcardcal-jcard-06 (work in progress), September 2013.
[I-D.ietf-weirds-using-http] [I-D.ietf-weirds-using-http]
Newton, A., Ellacott, B., and N. Kong, "HTTP usage in the Newton, A., Ellacott, B., and N. Kong, "HTTP usage in the
Registration Data Access Protocol (RDAP)", draft-ietf- Registration Data Access Protocol (RDAP)", draft-ietf-
weirds-using-http-07 (work in progress), July 2013. weirds-using-http-07 (work in progress), July 2013.
[I-D.ietf-weirds-rdap-query] [I-D.ietf-weirds-rdap-query]
Newton, A. and S. Hollenbeck, "Registration Data Access Newton, A. and S. Hollenbeck, "Registration Data Access
Protocol Lookup Format", draft-ietf-weirds-rdap-query-05 Protocol Query Format", draft-ietf-weirds-rdap-query-07
(work in progress), June 2013. (work in progress), October 2013.
[ISO.3166.1988] [ISO.3166.1988]
International Organization for Standardization, "Codes for International Organization for Standardization, "Codes for
the representation of names of countries, 3rd edition", the representation of names of countries, 3rd edition",
ISO Standard 3166, August 1988. ISO Standard 3166, August 1988.
15.2. Informative References 15.2. Informative References
[RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912,
September 2004. September 2004.
skipping to change at page 82, line 5 skipping to change at page 81, line 52
Changed flags and protocols to integers in keyData. Changed flags and protocols to integers in keyData.
Added 'entities' to the specified list for autnum. Added 'entities' to the specified list for autnum.
Added SHOULD/SHOULD NOT language about using "type": Added SHOULD/SHOULD NOT language about using "type":
"application/rdap+json" for self links. "application/rdap+json" for self links.
Added 'port43' to ip networks and autnum. Added 'port43' to ip networks and autnum.
-06
Fix search response example.
Change the returned search arrays to 'domainSearchResults',
'entitySearchResults', and 'nameserverSearchResults'.
Authors' Addresses Authors' Addresses
Andrew Lee Newton Andrew Lee Newton
American Registry for Internet Numbers American Registry for Internet Numbers
3635 Concorde Parkway 3635 Concorde Parkway
Chantilly, VA 20151 Chantilly, VA 20151
US US
Email: andy@arin.net Email: andy@arin.net
URI: http://www.arin.net URI: http://www.arin.net
 End of changes. 13 change blocks. 
14 lines changed or deleted 20 lines changed or added

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