Re: [regext] Roman Danyliw's No Objection on draft-ietf-regext-rdap-reverse-search-25: (with COMMENT)
Mario Loffredo <mario.loffredo@iit.cnr.it> Tue, 26 September 2023 06:46 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 31FD6C151089; Mon, 25 Sep 2023 23:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HRgz-DpeLpB5; Mon, 25 Sep 2023 23:46:34 -0700 (PDT)
Received: from mx5.iit.cnr.it (mx5.iit.cnr.it [146.48.58.12]) by ietfa.amsl.com (Postfix) with ESMTP id 4EBAEC14CF13; Mon, 25 Sep 2023 23:46:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx5.iit.cnr.it (Postfix) with ESMTP id 1BCFFC0860; Tue, 26 Sep 2023 08:46:30 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mx5.iit.cnr.it
Received: from mx5.iit.cnr.it ([127.0.0.1]) by localhost (mx5.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id itiYa5BsulJv; Tue, 26 Sep 2023 08:46:26 +0200 (CEST)
X-Relay-Autenticated: yes
Content-Type: multipart/alternative; boundary="------------0oS0TBO0I6Oa0wIwG3GQbffn"
Message-ID: <69a79ae1-a376-4c23-a071-c1f243a8949c@iit.cnr.it>
Date: Tue, 26 Sep 2023 08:41:55 +0200
Mime-Version: 1.0
Content-Language: it
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
Cc: "draft-ietf-regext-rdap-reverse-search@ietf.org" <draft-ietf-regext-rdap-reverse-search@ietf.org>, "regext-chairs@ietf.org" <regext-chairs@ietf.org>, "regext@ietf.org" <regext@ietf.org>, "tomh@apnic.net" <tomh@apnic.net>
References: <169339781569.36762.10311804866233525273@ietfa.amsl.com> <f8493b40-2bbc-d75e-6d5e-dc7c3da8ad32@iit.cnr.it> <BN2P110MB110727B1AB2EC14463185C47DCFCA@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
From: Mario Loffredo <mario.loffredo@iit.cnr.it>
In-Reply-To: <BN2P110MB110727B1AB2EC14463185C47DCFCA@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/C4XbbgF4onHgegLTfmeoLZyrox4>
Subject: Re: [regext] Roman Danyliw's No Objection on draft-ietf-regext-rdap-reverse-search-25: (with COMMENT)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 26 Sep 2023 06:46:38 -0000
Hi Roman, again my reponses below. Il 25/09/2023 22:55, Roman Danyliw ha scritto: > > Hi Mario! > > Thanks for the response. Response inline … > > *From:* Mario Loffredo <mario.loffredo@iit.cnr.it> > *Sent:* Friday, September 1, 2023 6:50 AM > *To:* Roman Danyliw <rdd@cert.org>; The IESG <iesg@ietf.org> > *Cc:* draft-ietf-regext-rdap-reverse-search@ietf.org; > regext-chairs@ietf.org; regext@ietf.org; tomh@apnic.net > *Subject:* Re: Roman Danyliw's No Objection on > draft-ietf-regext-rdap-reverse-search-25: (with COMMENT) > > Hi Roman, > > please find my comments below. > > Il 30/08/2023 14:16, Roman Danyliw via Datatracker ha scritto: > > Roman Danyliw has entered the following ballot position for > > draft-ietf-regext-rdap-reverse-search-25: No Objection > > > > When responding, please keep the subject line intact and reply to all > > email addresses included in the To and CC lines. (Feel free to cut this > > introductory paragraph, however.) > > > > > > Please refer tohttps://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ > > for more information about how to handle DISCUSS and COMMENT positions. > > > > > > The document, along with other ballot positions, can be found here: > > https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-reverse-search/ > > > > > > > > ---------------------------------------------------------------------- > > COMMENT: > > ---------------------------------------------------------------------- > > > > Thank you to Tero Kivinen for the SECDIR review. > > > > Thanks for address my DISCUSS feedback. > > > > I support Lars Eggert's DISCUSS position. > > > > == > > > > ** Section 1. > > The first objection concerns the potential risks of privacy > > violation. > > > > Where are these privacy concerns summarized? Could a reference be provided? > > > > > > [ML] Guess you think your remark hasn't yet been addressed by the new > version. > > Considering that the implications on privacy are presented in more > detail in the "Privacy Considerations" section, could it be enough to > rewrite that sentence as in the following ? > > (*) The first objection concerns the potential risks of privacy violations resulting from the use ofpersonal data and the detection of facts about an individual when the > requestor is not supported by lawful basis. > > I'm not aware of any document describing those concerns. When I wrote > the "Privacy Considerations" section, I started from the threats > listed in RFC6973 and I tried to identify those which could fit in > with the reverse search. > > Afterwards, RegExt considered that section exhaustive enough to > conclude the discussion about the privacy concerns. > > [Roman] The Privacy Considerations and the inline text make the issue > clear. I was reacting to the following text: > > its > > availability as a standardized Whois [RFC3912] capability has been > > objected to for two main reasons, which now don't seem to conflict > > with an RDAP implementation. > > [Roman] My recommendation was that if there was a way to cite the > objections to whois, it would be helpful (instead of asserting there > were objections without a reference). If this is not easy to do, then > please ignore the feedback. > [ML] Have repeatedly searched the web for some documents (preferably by ICANN or CENTR or some other forum of registries) about privacy concerns connected with Reverse Whois but all of those I found talk generally about "privacy concerns". This is the reason why I tried to summarize them in the sentence above (*). Anyway, if there is someone in RegExt who knows a suitable reference, I would be happy to include it in the document. Best, Mario > Thanks, > > Roman > > > _______________________________________________ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext -- Dott. Mario Loffredo Senior Technologist Technological Unit “Digital Innovation” Institute of Informatics and Telematics (IIT) National Research Council (CNR) via G. Moruzzi 1, I-56124 PISA, Italy Phone: +39.0503153497 Web:http://www.iit.cnr.it/mario.loffredo
- [regext] Roman Danyliw's No Objection on draft-ie… Roman Danyliw via Datatracker
- Re: [regext] Roman Danyliw's No Objection on draf… Mario Loffredo
- Re: [regext] Roman Danyliw's No Objection on draf… Roman Danyliw
- Re: [regext] Roman Danyliw's No Objection on draf… Mario Loffredo
- Re: [regext] Roman Danyliw's No Objection on draf… Roman Danyliw