Re: [regext] RDAP Event Members: REQUIRED or OPTIONAL?

[Roger D Carney <[e-mail]>]

Good Morning,

Thanks Scott, I do believe this suggestion would add clarity and is appropriate.


Thanks
Roger


________________________________
From: regext <[e-mail]> on behalf of Hollenbeck, Scott <shollenbeck=[e-mail]>
Sent: Thursday, May 7, 2020 8:34 AM
To: [e-mail] <[e-mail]>
Subject: [regext] RDAP Event Members: REQUIRED or OPTIONAL?

Notice: This email is from an external sender.



Mario found an interesting issue in RFC 7483. The text in Section 4.5 says this:

"The "events" array consists of objects, each with the following members:

   o  "eventAction" -- a string denoting the reason for the event

   o  "eventActor" -- an optional identifier denoting the actor responsible for the event

   o  "eventDate" -- a string containing the time and date the event occurred.

   o  "links" -- see Section 4.2"

As I read this, an "events" array contains objects, and each object has 4 members. There's nothing here that says that any of the members are REQUIRED or OPTIONAL, but "each with the following members" sounds to me like they MUST be included. There are, however, examples in the document the omit one or more members. The example in Section 4.5 itself omits the "links" member, and an example in Section 5.1 omits both the "eventActor" and "links" members.

The few implementations I've looked at (Verisign, ARIN, APNIC, Afilias, GoDaddy) all omit both the "eventActor" and "links" members. I'm inclined to add text to 7483bis noting that the "eventAction" and "eventDate" members are REQUIRED and the "eventActor" and "links" members are OPTIONAL. Does that cause any concern for anyone?

Scott

_______________________________________________
regext mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/regext