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

Mario Loffredo <mario.loffredo@iit.cnr.it> Thu, 07 May 2020 14:17 UTC

Return-Path: <mario.loffredo@iit.cnr.it>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01FA13A04BB for <regext@ietfa.amsl.com>; Thu, 7 May 2020 07:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G43djrt1C-OY for <regext@ietfa.amsl.com>; Thu, 7 May 2020 07:17:01 -0700 (PDT)
Received: from smtp.iit.cnr.it (mx5.iit.cnr.it [146.48.98.152]) by ietfa.amsl.com (Postfix) with ESMTP id EEDED3A041A for <regext@ietf.org>; Thu, 7 May 2020 07:17:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.iit.cnr.it (Postfix) with ESMTP id 177AFC1046; Thu, 7 May 2020 16:16:59 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mx5.iit.cnr.it
Received: from smtp.iit.cnr.it ([127.0.0.1]) by localhost (mx5.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id McFJFJTK98nN; Thu, 7 May 2020 16:16:56 +0200 (CEST)
Received: from [192.12.193.108] (pc-loffredo.nic.it [192.12.193.108]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by smtp.iit.cnr.it (Postfix) with ESMTPSA id 5F8CAC007B; Thu, 7 May 2020 16:16:56 +0200 (CEST)
To: "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org>, "regext@ietf.org" <regext@ietf.org>
References: <1b57b4064efd437588a050adcd7fb502@verisign.com>
From: Mario Loffredo <mario.loffredo@iit.cnr.it>
Message-ID: <2d8c5dae-ade4-ab75-62f8-b211e051cf0c@iit.cnr.it>
Date: Thu, 7 May 2020 16:14:31 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <1b57b4064efd437588a050adcd7fb502@verisign.com>
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: it
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/DOb88WrtRIx6cty-FT2bbmSrksU>
Subject: Re: [regext] RDAP Event Members: REQUIRED or OPTIONAL?
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 May 2020 14:17:06 -0000

Hi Scott,

IMHO, the information required to represent an event are the event type 
and the event date. The one without the other is meaningless. The event 
actor has been already defined as optional on some basis. The "links" 
member is something that could be used to convey additional information.

With regards to the event actor definition, I always wondered what 
"responsible" meant . Is it purposefully left to the interpretation?

Mario

Il 07/05/2020 15:34, Hollenbeck, Scott ha scritto:
> 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
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext

-- 
Dr. Mario Loffredo
Systems and Technological Development Unit
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Mobile: +39.3462122240
Web: http://www.iit.cnr.it/mario.loffredo
#pleasestayathome