draft-ietf-weirds-json-response-13.txt   draft-ietf-weirds-json-response-14.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: June 5, 2015 Verisign Labs Expires: July 4, 2015 Verisign Labs
December 2, 2014 December 31, 2014
JSON Responses for the Registration Data Access Protocol (RDAP) JSON Responses for the Registration Data Access Protocol (RDAP)
draft-ietf-weirds-json-response-13 draft-ietf-weirds-json-response-14
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 June 5, 2015. This Internet-Draft will expire on July 4, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 20, line 42 skipping to change at page 20, line 42
"asEventActor":[ "asEventActor":[
{ {
"eventAction":"last changed", "eventAction":"last changed",
"eventDate":"1991-12-31T23:59:59Z" "eventDate":"1991-12-31T23:59:59Z"
} }
] ]
} }
Figure 15 Figure 15
This object has the following members: The entity object class can contain the following members:
o objectClassName -- the string "entity" o objectClassName -- the string "entity"
o handle -- a string representing an registry unique identifier of o handle -- a string representing an registry unique identifier of
the entity the entity
o vcardArray -- a jCard with the entity's contact information o vcardArray -- a jCard with the entity's contact information
o roles -- an array of strings, each signifying the relationship an o roles -- an array of strings, each signifying the relationship an
object would have with its closest containing object (see object would have with its closest containing object (see
Section 10.2.4 for a list of values) Section 10.2.4 for a list of values)
skipping to change at page 27, line 22 skipping to change at page 27, line 22
... ...
"entities" : "entities" :
[ [
... ...
], ],
... ...
} }
Figure 21 Figure 21
The nameserver object class has the following members: The nameserver object class can contain the following members:
o objectClassName - the string "nameserver" o objectClassName - the string "nameserver"
o handle -- a string representing an registry unique identifier of o handle -- a string representing an registry unique identifier of
the nameserver the nameserver
o ldhName -- a string containing the LDH name of the nameserver (see o ldhName -- a string containing the LDH name of the nameserver (see
Section 3) Section 3)
o unicodeName -- a string containing a DNS Unicode name of the o unicodeName -- a string containing a DNS Unicode name of the
skipping to change at page 28, line 41 skipping to change at page 28, line 41
], ],
... ...
"entities" : "entities" :
[ [
... ...
] ]
} }
Figure 22 Figure 22
The following is a description of the members of this object: The domain object class can contain the following members:
o objectClassName -- the string "domain" o objectClassName -- the string "domain"
o handle -- a string representing a registry unique identifier of o handle -- a string representing a registry unique identifier of
the domain object instance the domain object instance
o ldhName -- a string describing a domain name in LDH form as o ldhName -- a string describing a domain name in LDH form as
described in Section 3 described in Section 3
o unicodeName -- a string containing a domain name with U-labels as o unicodeName -- a string containing a domain name with U-labels as
skipping to change at page 40, line 7 skipping to change at page 40, line 7
} }
] ]
} }
] ]
} }
Figure 24 Figure 24
5.4. The IP Network Object Class 5.4. The IP Network Object Class
The IP Network object class models IP network registrations found in The IP network object class models IP network registrations found in
RIRs and is the expected response for the "/ip" query as defined by RIRs and is the expected response for the "/ip" query as defined by
[I-D.ietf-weirds-rdap-query]. There is no equivalent object class [I-D.ietf-weirds-rdap-query]. There is no equivalent object class
for DNRs. The high level structure of the IP network object class for DNRs. The high level structure of the IP network object class
consists of information about the network registration and entities consists of information about the network registration and entities
related to the IP network (e.g. registrant information, contacts, related to the IP network (e.g. registrant information, contacts,
etc...). etc...).
The following is an elided example of the IP network object type The following is an elided example of the IP network object type
showing the high level structure: showing the high level structure:
skipping to change at page 43, line 21 skipping to change at page 43, line 21
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z" "eventDate" : "1991-12-31T23:59:59Z"
} }
] ]
} }
] ]
} }
Figure 26 Figure 26
The following is a description of the members of this object: The IP network object class can contain the following members:
o objectClassName -- the string "ip network" o objectClassName -- the string "ip network"
o handle -- a string representing an RIR unique identifier of the o handle -- a string representing an RIR unique identifier of the
network registration network registration
o startAddress -- the starting IP address of the network, either o startAddress -- the starting IP address of the network, either
IPv4 or IPv6 IPv4 or IPv6
o endAddress -- the ending IP address of the network, either IPv4 or o endAddress -- the ending IP address of the network, either IPv4 or
skipping to change at page 44, line 17 skipping to change at page 44, line 17
o remarks - see Section 4.3 o remarks - see Section 4.3
o links - see Section 4.2 o links - see Section 4.2
o port43 - see Section 4.7 o port43 - see Section 4.7
o events - see Section 4.5 o events - see Section 4.5
5.5. Autonomous System Number Entity Object Class 5.5. Autonomous System Number Entity Object Class
The Autonomous System Number (autnum) object class models Autonomous The autonomous system number (autnum) object class models Autonomous
System Number registrations found in RIRs and represents the expected System Number registrations found in RIRs and represents the expected
response to an "/autnum" query as defined by response to an "/autnum" query as defined by
[I-D.ietf-weirds-rdap-query]. There is no equivalent object class [I-D.ietf-weirds-rdap-query]. There is no equivalent object class
for DNRs. The high level structure of the autnum object class for DNRs. The high level structure of the autnum object class
consists of information about the network registration and entities consists of information about the network registration and entities
related to the autnum registration (e.g. registrant information, related to the autnum registration (e.g. registrant information,
contacts, etc.), and is similar to the IP Network entity object contacts, etc.), and is similar to the IP Network entity object
class. class.
The following is an example of a JSON object representing an autnum. The following is an example of a JSON object representing an autnum.
skipping to change at page 47, line 6 skipping to change at page 47, line 6
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z" "eventDate" : "1991-12-31T23:59:59Z"
} }
] ]
} }
] ]
} }
Figure 27 Figure 27
The following is a description of the members of this object: The autonomous system number object class can contain the following
members:
o objectClassName -- the string "autnum" o objectClassName -- the string "autnum"
o handle -- a string representing an RIR-unique identifier of the o handle -- a string representing an RIR-unique identifier of the
autnum registration autnum registration
o startAutnum -- a number representing the starting number [RFC5396] o startAutnum -- a number representing the starting number [RFC5396]
in the block of autonomous system numbers in the block of autonomous system numbers
o endAutnum -- a number representing the ending number [RFC5396] in o endAutnum -- a number representing the ending number [RFC5396] in
skipping to change at page 91, line 23 skipping to change at page 91, line 23
-12 -12
Changes to address IESG comments. Changes to address IESG comments.
-13 -13
Changes to address Alyssa's DISCUSS. Changes to address Alyssa's DISCUSS.
'redacted' status changed to 'removed' 'redacted' status changed to 'removed'
-14
Text changes regarding can contain vs has members of for object
classes.
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. 11 change blocks. 
11 lines changed or deleted 17 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/