[regext] Re: Fwd: New Version Notification for draft-loffredo-regext-rdap-verified-contacts-01.txt

Andy Newton <andy@hxr.us> Thu, 24 July 2025 15:28 UTC

Return-Path: <andy@hxr.us>
X-Original-To: regext@mail2.ietf.org
Delivered-To: regext@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 1D6AA4A747A6 for <regext@mail2.ietf.org>; Thu, 24 Jul 2025 08:28:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=hxr-us.20230601.gappssmtp.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FoGlKqGJIo0n for <regext@mail2.ietf.org>; Thu, 24 Jul 2025 08:28:52 -0700 (PDT)
Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 512D84A74759 for <regext@ietf.org>; Thu, 24 Jul 2025 08:28:48 -0700 (PDT)
Received: by mail-qk1-x730.google.com with SMTP id af79cd13be357-7e372c8a9a4so86056785a.2 for <regext@ietf.org>; Thu, 24 Jul 2025 08:28:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20230601.gappssmtp.com; s=20230601; t=1753370928; x=1753975728; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=aJRZt4EnS/EJzmyHNLPFSVllGGNXOLUGDLRvFvXx5Fc=; b=XVzHebgRw5uVUyHxMVeTNEPOKLuEvTGOBPynPvq3On6l/9PZs/bQliWb6dDNYf1TTB muPBNRjKkFZB4zCRPd+X+e0dH6ZNITBt06HcIxxmubj5s9GMvuYeEBVEeI+TTQQBWJVN 8xmkc3Tf4fWgZA4YFENt17KsBYIhuqchMGSrg4XaEaEMGA8qFdhUc093VydUdnstCjr4 HUsHY4/s3W4qIgX+74d5TQGO4bUHVNWpARAiiDTlCB/ms1/pT2/vQB4yZs3Lv8IJl58o takJAbrBtfYKVH0JpNN7+UKxtCG6sDYQ31TLTwcJDjv7k6BH8zaoeEvkm/uozYGy+7FJ CA2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753370928; x=1753975728; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=aJRZt4EnS/EJzmyHNLPFSVllGGNXOLUGDLRvFvXx5Fc=; b=RpKwH9vXFUqch6/dnkI2z283NQehqPusAXVcxDOb92IHp/+/uhpXn1GiLjGEmEHVdF w5CAc4fgxK/p9YsFkdOqLnqExvkmFEA5kj8eiJG9xToZNC6b0Jw95Jq5uQM60b6H/eoZ WaITTbQ1bg/RL7O0UnDSluk3UEDLid35KC9hV3DFFxcHRAnCaJeO6v/Ajj2YUgi/kLqm RTNPmzeIyJK3RRwrpFt3zcM134FZRRlm+vYNjocxF3BjgGpE0I/S89fMDjMvM7kyi+nL 2piN0LSsHj5MGFe5ITnfZVZveCkjKsU8Z6EGXnSTbOtjyCoBDLVoDVsiQecap81J2d6T Z/Ug==
X-Forwarded-Encrypted: i=1; AJvYcCXRu7QjSantyU35Q6n7Ff4vkvX2fDlHGg6f93l61JB8p+jOO/Jah8USj19VjjPfuRRXmmfZAo8=@ietf.org
X-Gm-Message-State: AOJu0Yx3kxqkKqzjUra81lRqetZugXkokr1ae14GKZ3b7T+tooa28fIL yJoMuFNbp/PbIhfOhDvDZgy5huTYuyjoklqPtiek9jlKgs/vZ2V6d2UpLtojzaURxn7gX8vTRph cbAio3gzvgw==
X-Gm-Gg: ASbGncv40t2rufheMZBu9B/xplGZn0Uf2ifo8pK78onVVwNU78GfJVy87b6uLgKGYae 0jotC1+TyvPMLuqO+gsiS6gAWb+zU9Qt3iz9niZrH9xFciwHaPWdXWrVsz0k3N2/5bfI3fsiN9j cZhDoSM/Wj45PxBRqk66TiSMQhcnXf3CnMQRyU7Okfyxi5+CwH/1nKD8lLpunloD7s3/3UbFOGb vJVZxaDGkC1XpRGVZMmdfgS41ndJYPDih1cxa20GT0sB7QZKlxqn/TzCqgvJmWPsnjpLyvenFtt P4Xh72G7xoRD59qmbSgR94DC6ZuBixKMyI5LxfuQxDXIO3CJZiv7ux+5tzJwjrq8Hp1osOWXq88 yVaB8d4+tyKEm4VhVvE6aGpKdendjUaonbId/eRw25ZeaP9O50ZjqtFAI3ssMANK3ykCOX4Q=
X-Google-Smtp-Source: AGHT+IEcJrLp0Yl1JKKdmEfTVAgq0n8+vE/6hVjdrti+Qc+95ViexCBonn8RBdNhCBxEGOez3M0Txw==
X-Received: by 2002:a05:620a:6a0b:b0:7d5:e4a2:2374 with SMTP id af79cd13be357-7e62a139b10mr613487085a.8.1753370927392; Thu, 24 Jul 2025 08:28:47 -0700 (PDT)
Received: from ?IPV6:2001:67c:370:1998:e0be:2b2:838d:1294? ([2001:67c:370:1998:e0be:2b2:838d:1294]) by smtp.gmail.com with ESMTPSA id af79cd13be357-7e632e4e3c5sm134287985a.93.2025.07.24.08.28.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 24 Jul 2025 08:28:46 -0700 (PDT)
Message-ID: <55bed8e1-d71f-4d8f-8f23-e2dc290bf4f8@hxr.us>
Date: Thu, 24 Jul 2025 17:28:45 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Mario Loffredo <mario.loffredo=40iit.cnr.it@dmarc.ietf.org>, "regext@ietf.org" <regext@ietf.org>
References: <175308442343.1698295.955769774131702283@dt-datatracker-7ff4b97469-cdtd8> <ccd6e5c7-c1fd-48b3-85e4-630bee869e2d@iit.cnr.it>
Content-Language: en-US
From: Andy Newton <andy@hxr.us>
In-Reply-To: <ccd6e5c7-c1fd-48b3-85e4-630bee869e2d@iit.cnr.it>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: MIE6FCYNWXUMFEGOJM35COUG5PHNV4S7
X-Message-ID-Hash: MIE6FCYNWXUMFEGOJM35COUG5PHNV4S7
X-MailFrom: andy@hxr.us
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.9rc6
Precedence: list
Subject: [regext] Re: Fwd: New Version Notification for draft-loffredo-regext-rdap-verified-contacts-01.txt
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/pVnsS-d_v6DILwNn8b_3GUsWUg4>
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>

Hi Mario,

Have you considered putting the extension inside of the current RDAP event structure?
The advantage here is that clients that may not understand the extension can still pass
through some information to the end-user.

Something like:

{
     "eventAction" : "email verified",
     "eventDate" : "1990-12-31T23:59:59Z",
     "verifiedContact_method" : "smsToken"
}

If the client doesn't understand the verifiedContact extension, the end user will still know the date/time
of the email verification. And for clients that do understand the extension, the method can be given to
the user.

-andy

On 21-07-2025 10:00 AM, Mario Loffredo wrote:
> Hi,
> 
> I have slightly modified the initial version to align it with tomorrow's presentation.
> 
> I further specified the verification methods and made the verifiedContacts_data keys consistent with those defined in draft-ietf-regext-rdap-jscontact.
> 
> See you tomorrow.
> 
> Best,
> 
> Mario
> 
> 
> 
> -------- Messaggio Inoltrato --------
> Oggetto: 	New Version Notification for draft-loffredo-regext-rdap-verified-contacts-01.txt
> Data: 	Mon, 21 Jul 2025 00:53:43 -0700
> Mittente: 	internet-drafts@ietf.org
> A: 	James Gould <jgould@verisign.com>, Mario Loffredo <mario.loffredo@iit.cnr.it>, Maurizio Martinelli <maurizio.martinelli@iit.cnr.it>
> 
> 
> 
> A new version of Internet-Draft
> draft-loffredo-regext-rdap-verified-contacts-01.txt has been successfully
> submitted by Mario Loffredo and posted to the
> IETF repository.
> 
> Name: draft-loffredo-regext-rdap-verified-contacts
> Revision: 01
> Title: Registration Data Access Protocol (RDAP) Extension for Verified Contact Information
> Date: 2025-07-21
> Group: Individual Submission
> Pages: 6
> URL: https://www.ietf.org/archive/id/draft-loffredo-regext-rdap-verified-contacts-01.txt
> Status: https://datatracker.ietf.org/doc/draft-loffredo-regext-rdap-verified-contacts/
> HTML: https://www.ietf.org/archive/id/draft-loffredo-regext-rdap-verified-contacts-01.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-loffredo-regext-rdap-verified-contacts
> Diff: https://author-tools.ietf.org/iddiff?url2=draft-loffredo-regext-rdap-verified-contacts-01
> 
> Abstract:
> 
> This document describes an extension to the Registration Data Access
> Protocol (RDAP) that allows the inclusion of verification status
> information for contact fields such as email addresses and phone
> numbers. The goal is to improve data quality and trustworthiness of
> RDAP responses by indicating which pieces of contact data have been
> verified and how.
> 
> 
> 
> The IETF Secretariat
> 
> 
> 
> _______________________________________________
> regext mailing list -- regext@ietf.org
> To unsubscribe send an email to regext-leave@ietf.org