IETF Logo Mail Archive

[regext] Re: WGLC: draft-ietf-regext-rdap-geofeed-05

Mario Loffredo <mario.loffredo@iit.cnr.it> Tue, 16 July 2024 13:56 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 85452C14F61A for <regext@ietfa.amsl.com>; Tue, 16 Jul 2024 06:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.005
X-Spam-Level:
X-Spam-Status: No, score=-7.005 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iit.cnr.it
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 4Tj7zDLNNCKy for <regext@ietfa.amsl.com>; Tue, 16 Jul 2024 06:56:05 -0700 (PDT)
Received: from mx3.iit.cnr.it (mx5.iit.cnr.it [146.48.58.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FDF2C14F5E4 for <regext@ietf.org>; Tue, 16 Jul 2024 06:56:04 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mx3.iit.cnr.it 09E6BC068A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iit.cnr.it; s=mx520231221; t=1721138161; bh=HwTVWhQgg4YnbF67Ygfjy0V0nS7rqaJ0PotapNJw2Wk=; h=Date:Subject:To:References:From:In-Reply-To:From; b=fweGS3bzddWLfi7nOpqfLUzcUyNjQ35J32tx1s9YspSqNkMS6HOSIjJ1FTyctIb7p bY4NUC7S4gV0jvhHsrV31K/pRa6HQYAiiiwnZETw+H4TRbjbGEXzH1DC/uRASnaCai kVnkGsSWUt/1uPXLEKIjjOLfMUQNgggTRNmMoqY/lGRcCQy7g6MDFMqBEqrljehJW6 g9wFqEKSgqAAP0S+IrKVP+TIDzaCt8nZcrxgIqFfIRe7Y3z33z3xjEbqIYCZylWGNj UeAl8+GpBQOoiEd3PImK3qLBui3Cbqpij7prEp5+S+7bylP4pNDhf3QlC5k1upgZju nCbKX9Q0vaGSg==
Received: from localhost (localhost [127.0.0.1]) by mx3.iit.cnr.it (Postfix) with ESMTP id 09E6BC068A for <regext@ietf.org>; Tue, 16 Jul 2024 15:56:01 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mx5.iit.cnr.it
Received: from mx3.iit.cnr.it ([127.0.0.1]) by localhost (mx5.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10028) with ESMTP id Gl6Y40DiQOUH for <regext@ietf.org>; Tue, 16 Jul 2024 15:56:00 +0200 (CEST)
X-Relay-Autenticated: yes
Content-Type: multipart/alternative; boundary="------------AOKacGsSwJwW06UoccPKfR7e"
Message-ID: <95504da0-2733-4ace-9fb4-db3737018136@iit.cnr.it>
Date: Tue, 16 Jul 2024 15:50:43 +0200
Mime-Version: 1.0
Content-Language: it
To: regext@ietf.org
References: <9AE89B13-D3D1-4D15-8EAA-105CCFA0F540@elistx.com>
From: Mario Loffredo <mario.loffredo@iit.cnr.it>
In-Reply-To: <9AE89B13-D3D1-4D15-8EAA-105CCFA0F540@elistx.com>
Message-ID-Hash: XNYLDOMEWSCFTKRK73NMWNXJE4HZIMCV
X-Message-ID-Hash: XNYLDOMEWSCFTKRK73NMWNXJE4HZIMCV
X-MailFrom: mario.loffredo@iit.cnr.it
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-regext.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [regext] Re: WGLC: draft-ietf-regext-rdap-geofeed-05
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/qfvl5XgLWakwBG5Zi1bxVa-tyGs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Owner: <mailto:regext-owner@ietf.org>
List-Post: <mailto:regext@ietf.org>
List-Subscribe: <mailto:regext-join@ietf.org>
List-Unsubscribe: <mailto:regext-leave@ietf.org>

Have reviewed this document.

Per what is stated in section 3, it's not clear to me what servers 
should do whenever the geofeed file exposes the location of an individual.

Neither Section 7 of [I-D.ietf-opsawg-9092-update] seems to clarify this 
point as it contains only a generic warning (see below):

*... In publishing pointers to geofeed files as described in this 
document, the operator should be aware of this exposure in geofeed data 
and be cautious....*


Should RDAP servers omit to present the geo link  or should they remove 
from the linked geofeed file the information related to the location of 
individuals ?

Does it mean that the geo link can be redacted ? If so, which redaction 
method should be used?


Best,

Mario




Il 12/07/2024 23:12, James Galvin ha scritto:
> The document editors have indicated that the following document is ready for submission to the IESG to be considered for publication as a Proposed Standard:
>
> An RDAP Extension for Geofeed Data
> https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-geofeed/
>
> Please indicate your support or no objection for the publication of this document by replying to this message on list (a simple “+1” is sufficient).
>
> If any working group member has questions regarding the publication of this document please respond on the list with your concerns by close of business everywhere, Friday, 2 August 2024.  This WGLC has been extended to 3 weeks because of the IETF120 meeting.
>
> If there are no objections the document will be submitted to the IESG.
>
> The Document Shepherd for this document is Gavin Brown.
>
> Thanks,
>
> Antoin and Jim
> REGEXT WG Co-Chairs
>
> _______________________________________________
> regext mailing list --regext@ietf.org
> To unsubscribe send an email toregext-leave@ietf.org

-- 
Dott. Mario Loffredo
Senior Technologist
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
Address: Via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web:http://www.iit.cnr.it/mario.loffredo

v2.39.1 | Report a Bug | By Email | System Status