Re: [regext] I-D draft-latour-pre-registration

kowalik@denic.de Thu, 16 November 2023 08:26 UTC

Return-Path: <kowalik@denic.de>
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 AC3DEC151066 for <regext@ietfa.amsl.com>; Thu, 16 Nov 2023 00:26:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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=denic.de
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 QCQYSPDcZniF for <regext@ietfa.amsl.com>; Thu, 16 Nov 2023 00:26:46 -0800 (PST)
Received: from mout-b-210.mailbox.org (mout-b-210.mailbox.org [195.10.208.40]) (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 DDC25C14CF01 for <regext@ietf.org>; Thu, 16 Nov 2023 00:26:44 -0800 (PST)
Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:b231:465::202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-210.mailbox.org (Postfix) with ESMTPS id 4SWCmt6cVzzDtYm; Thu, 16 Nov 2023 09:26:38 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denic.de; s=MBO0001; t=1700123198; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=AqFIZZYCCxpfP8W3wPDDpWqR9gv3ZaE4HT+1fG4fqzE=; b=MM2yQMhKZ2Ly6x9/OzrC2sPlefhSSBSqsgwDxwftB5Bwi8/1KAoGUS4SL9X07VUSZay3Vo 4Ua7CA1pWwPhuGypRF0N5h8i70TaFcNQOsS2KuBwzVFM8JOHQXSI69qa7dhiLmMph1oiiP Uvx0s+IaCsBYflGJzbO3AaBOsPta7NEwWK6Riph7Ww0Ix5wxSa06q0PlErYZcUc5JV0ZPr lKj05DDVZx9uaxN1k7JBKdBrToedH//+X2FjYyAWROMoTL3cOMSsx9J4KoaO6L+wkF4NXp a+Sh36l/T9bRjrA2USjQF8crEbSWCSfEha1M2co3+OwBMxtgViymfO6INpHXmw==
Message-ID: <259686d7-48c4-4e0d-af1e-8999d657a89f@denic.de>
Date: Thu, 16 Nov 2023 09:26:36 +0100
MIME-Version: 1.0
From: kowalik@denic.de
Content-Language: en-GB
To: Jacques Latour <Jacques.Latour=40cira.ca@dmarc.ietf.org>, "regext@ietf.org" <regext@ietf.org>
Cc: Don Slaunwhite <Don.Slaunwhite@cira.ca>, "timj@internetnz.net.nz" <timj@internetnz.net.nz>
References: <YT2P288MB0252F7B68F98EBF28747C7FA8AB1A@YT2P288MB0252.CANP288.PROD.OUTLOOK.COM>
In-Reply-To: <YT2P288MB0252F7B68F98EBF28747C7FA8AB1A@YT2P288MB0252.CANP288.PROD.OUTLOOK.COM>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms070103050501060302030400"
X-MBO-RS-ID: 7947a7ef1318555c7d8
X-MBO-RS-META: zzruorzxusfy4s4tshdpgatzffbqe3zr
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/f2smZOa6m1G80_9vYBhnTc4tCzw>
Subject: Re: [regext] I-D draft-latour-pre-registration
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: Thu, 16 Nov 2023 08:26:50 -0000

Hi Jack,

Skimming through the document I have 3 questions / observations:

1) why you decided to break the flow into 2 commands with create and 
validate? What shall happen afterwards to the object(s) created in the 
first step? In this context the approach in draft-ietf-regext-validate 
to have temporary objects created implicitly with check:validate 
command, even if the process is asynchronous, seems more plausible to me.

2) The draft tells a lot about ML/AI, while actually it can be any type 
of validation. It can be static, rule based or even manual if you wish. 
I would not narrow down the use-case just to ML/AI.

3) Section 8 is for me too deep into policy setting/suggesting and not 
in the area of technical protocol. The protocol shall define whether the 
result is discrete value (with maybe IANA repository) or continuos score 
and the number format, but not going beyond that. Note that the same 
protocol could be also used for other purposes other than abuse, like 
eligibility check based on other criteria.

Kind regards,

Pawel

Am 15.11.23 um 16:56 schrieb Jacques Latour:
>
> Hi all,
>
> At the ICANN78 meeting and other venues, there were quite a lot of 
> discussion on AI/ML abuse detection related discussions and presentations.
>
>   * Example:
>     https://static.sched.com/hosted_files/icann78/de/4%20%2020231023-TechDay-AI%20at%20EURid.pdf
>
> But this is after the fact, after a registration is completed, so we 
> thought of a new extension to allow the registrar to ask the registry 
> that have this real time capabilities to analyse the pre-registration 
> information and return a quality score to better inform the process.
>
> draft-latour-pre-registration-00 - EPP Pre-Registration Verification 
> (ietf.org) 
> <https://datatracker.ietf.org/doc/draft-latour-pre-registration/>
>
> Have a read,
>
> Jack
>
>
> CLASSIFICATION:CONFIDENTIAL
>
>
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext