Re: [regext] WG LAST CALL: draft-ietf-regext-rdap-partial-response

Mario Loffredo <mario.loffredo@iit.cnr.it> Mon, 27 April 2020 15:33 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 341713A0CA4 for <regext@ietfa.amsl.com>; Mon, 27 Apr 2020 08:33: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 e_udzLvfV8Fv for <regext@ietfa.amsl.com>; Mon, 27 Apr 2020 08:33:03 -0700 (PDT)
Received: from smtp.iit.cnr.it (mx4.iit.cnr.it [146.48.98.151]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0C973A0D65 for <regext@ietf.org>; Mon, 27 Apr 2020 08:33:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.iit.cnr.it (Postfix) with ESMTP id 5F4EEB801F8; Mon, 27 Apr 2020 17:32:59 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mx4.iit.cnr.it
Received: from smtp.iit.cnr.it ([127.0.0.1]) by localhost (mx4.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bw4pK1pPZX3u; Mon, 27 Apr 2020 17:32:54 +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 C7486B80389; Mon, 27 Apr 2020 17:32:54 +0200 (CEST)
To: Patrick Mevzek <pm@dotandco.com>, regext@ietf.org
References: <CF2EE8CE-DB07-4AFF-84D0-B80BA5E76D39@antoin.nl> <b79a4641-bade-4901-b3f0-bb7decbdb41e@www.fastmail.com>
From: Mario Loffredo <mario.loffredo@iit.cnr.it>
Message-ID: <50276493-87ad-291e-a6cd-ff26fce77868@iit.cnr.it>
Date: Mon, 27 Apr 2020 17:30:34 +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: <b79a4641-bade-4901-b3f0-bb7decbdb41e@www.fastmail.com>
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: it
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/eeBM9W7i7JKprRA4uVH6AObQnJI>
Subject: Re: [regext] WG LAST CALL: draft-ietf-regext-rdap-partial-response
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: Mon, 27 Apr 2020 15:33:05 -0000

Hi Patrick,

your feedback is really welcomed. Better late than never.

My responses to your comments are included below.

Il 27/04/2020 07:45, Patrick Mevzek ha scritto:
>
> On Fri, Feb 28, 2020, at 09:43, Antoin Verschuren wrote:
>> The following working group document is believed to be ready for
>> submission to the IESG for publication as a standards track document:
>>
>> https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-partial-response/
>>
>> This WG last call will end at close of business, Friday, 13 March 2020.
> I am too late, I know.
>
> But anyway I fear that at least the "brief" case will create interoperability
> problems, or at least complexity in clients because there is a risk of each
> RDAP server thinking of it differently.

I published a draft version, namely 
draft-loffredo-regext-rdap-partial-response-03, including a definition 
of the "brief" field set which was based on those WHOIS response fields 
identified in RFC 7485 as mostly supported (i.e. by more than one third 
of contacted services). As you can see from the "Change Log", that 
definition was removed in draft-ietf-regext-rdap-partial-response-01 
because the WG had clearly recommended to separate the technology, 
described in the RFC, from its operational aspects, described in an RDAP 
profile.

The same feedback was recently provided by Karl Heinz Wolf and now I'm 
giving you the same answer as I gave him.

Anyway, if the WG members reconsider their position about this point, I 
will be happy to refine my old proposal or work on a new one.

> The "subsetting_metadata" is only a SHOULD not a MUST, so clients could
> remain completely without real explanations on why "brief" for server A
> is different from "brief" result for server B.

It's not a MUST because the available field sets could be defined in a 
document published elsewhere, for example, in a specific RDAP profile.

Therefore, in my opinion, it would be recommended but not required.

> It would have been nice to provide a template for "brief", at least a SHOULD,
> per objects described in the RDAP RFCs.
See my response above.
> Specially since the document has this text:
> "the
>     name, as well as the list of fields for each field set, should be
>     shared by most of RDAP providers."

Obviously, the field set approach is valuable if there is a wide 
consensus on both the name and the content of a possible field set. It's 
perfectly unuseful to multiply the field sets as well as

to let the same field sets have different contents.

Three possible field set names have been recommended in the document in 
order to ease interoperability. For the field sets representing the two 
extremes, namely "id" and "full", the corresponding content is evident.

For the remaining field set, the WG considered that the document wasn't 
the right place to define its content.

> Written like that, this is not a protocol specification, and does not even
> give tools at the protocol level to enforce that.
>
> Or, and this could be an easy solution, another draft defining rdapConformance
> subsetting_brief_level_0
> should define exactly what is brief and then servers are free to properly
> signal if they adhere to this definition of fields or not.
> There could be multiple drafts in fact for multiple definitions.

This is an interesting solution but I dont' see, at least in the case of 
"brief",  why the WG should approve to define in a separate draft what 
has been considered unsuitable in this draft :-(

> PS: the argument in A.1 about the complexity arising out of jCard can "soon"
> become obsolete if draft-loffredo-regext-rdap-jcard-deprecation goes through,
> so maybe some text should have addressed other non jCard cases (or explaining why
> even if jCard is dropped then problems remain)

Yes, it might become but presently it isn't obsolete. Anyway, the 
reasons why the "field set" approach should be preferred  even when 
jCard will be no more supported are reported before section A.1.

So I don't think section A.1 needs to be changed.


I would like the other WG members to manifest their opinions so that I 
could change the document where appropriate.

Best,

Mario

-- 
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