[gtld-tech] Question about the ICANN RDAP Profile

[Gustavo Lozano]

Thank you Brain for pointing this out,
 
You are correct, the object type values are inverted, and the object type
for the remarks member should be of the form "object truncated .." as
defined in 
https://www.iana.org/assignments/rdap-json-values/rdap-json-values.xhtml.
 
We plan to publish an errata addressing this issue.
 
Regards,
Gustavo

From:  <gtld-tech-bounces at icann.org> on behalf of Brian Mountford via
gtld-tech <gtld-tech at icann.org>
Reply-To:  Brian Mountford <mountford at google.com>
Date:  Thursday, October 6, 2016 at 08:09
To:  "gtld-tech at icann.org" <gtld-tech at icann.org>
Cc:  Nick Felt <nickfelt at google.com>
Subject:  [gtld-tech] Question about the ICANN RDAP Profile

> ICANN folks, 
> 
> I am working on implementing the required remarks and notifications for
> truncate RDAP responses. I see the following in the RDAP Profile document
> 
(https://www.icann.org/resources/pages/rdap-operational-profile-2016-07-26-en)>
:
> 
> 1.4.8. Truncated RDAP responses MUST contain a notices member describing the
> reason of the truncation. The notices object type MUST be of the form
> "Response truncated due to {authorization|load|unexplainable reason}".
> 1.4.9. Truncated RDAP objects MUST contain a remarks member describing the
> reason of the truncation. The remarks object type MUST be of the form "Result
> set truncated due to {authorization|load|unexplainable reason}".
> Something doesn't seem right to me. 1.4.9 requires a remark saying "Result set
> truncated", as if that was used when returning result sets that contain fewer
> results than there actually are because of sizing limits. But then that should
> be a notice, because it happens globally for the response. And yet it refers
> to "truncated RDAP objects" rather than result sets.
> 
> Is it possible that you got the text confused, and that truncated result sets
> have a notice of the form "Result set truncated ...", while truncated objects
> have a remark of the form "Response truncated ..."?
> 
> If that's not what's going on, can you elaborate with a couple examples? I
> can't figure out how it would work. Thanks.
> 
> Brian


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gtld-tech/attachments/20161011/b6ee457b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4701 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gtld-tech/attachments/20161011/b6ee457b/smime-0001.p7s>