Hi Andy,
I list three other possible errors. I don't know if they are real
errors, most probably I misunderstood some statements of the protocol:
- in RFC7480 (section "5.3") it is written "If a server wishes to
respond that it has an empty result set (that is, no data appropriately
satisfying the query), it returns a 404 (Not Found) response code."
According to this statement, it seems that search response arrays
should have at least one element so for example the rule
$domainSearchResult = "domainSearchResult" : [ $domain_oc * ] should be
replaced by the rule $domainSearchResult = "domainSearchResult" : [
$domain_oc + ]
- Is it possible to have RDAP responses without any value (at least
"rdap_level_*" seems to be required) in the rdapConformance array? If
no, the rule about rdapConformance should be $rdapConformance =
"rdapConformance" : [ string + ]
- Handle seems to be required for an entity. If so, the handle defintion
in common_mixin should be overrided by an identical definition without
'?' in entity_mixin. The same occurs if rdapConformance is required for
all the reponses except the error response.
Regards,
Mario
Il 11/10/2017 16:08, Andrew Newton ha scritto:
Mario,
Thanks for reviewing this. My replies are in-line.
------ Original Message ------
From: "Mario Loffredo" <[email protected]>
To: "Andrew Newton" <[email protected]>
Cc: "Registration Protocols Extensions" <[email protected]>
Sent: 10/9/2017 11:41:21 AM
Subject: Re: [regext] Preparing for IETF 100
Hi Andy,
it seems to me that some corrections should be made:
- the last three properties of "secureDNS" definition should
be moved inside the "domain_mixin" definition;
Good catch! Thanks.
- the "autnum_mixin" definition should contain the
"country" property;
Another good catch. Thanks.
- the "event" definition should be splitted in two like the
following:
$noActorEvent = {
"eventAction" : string,
"eventDate" : datetime,
$links,
$lang
}
$event = {
$noActorEvent,
"eventActor" : string,
}
The noActorEvent type should be used in the definition of
"asEventActor" property
because RFC7483 states that each object in the array must not
have an "eventActor" member.
Yes, I agree. I'll also add some comments to explain it. Thanks.
In addition, there is a case of redundancy but I don't know if
it is an error or it is allowed by JCR overriding rules.
The presence of the "lang" property in a lookup response can
be derived by following two paths. For example, in a domain
lookup response lang can be derived both by
domain_response->response_mixin->lang
and domain_response->domain_mixin->common_mixin->lang
Since lang is optional, there is no harm. However, I see no reason why
it should be in both places. Thanks for point this out.
I'll make these corrections on the next version of the draft.
-andy
_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext
--
Dr. Mario Loffredo
Servizi Internet e Sviluppo Tecnologico
CNR - Istituto di Informatica e Telematica
via G. Moruzzi 1, I-56124 PISA, Italy
E-Mail: [email protected]
Phone: +39 050 3153497
Web: http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext
