[regext] Re: [Ext] DSYNC in EPP

kowalik@denic.de Tue, 30 July 2024 10:12 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 62A8BC14F6F2 for <regext@ietfa.amsl.com>; Tue, 30 Jul 2024 03:12:19 -0700 (PDT)
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=unavailable 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 H9rmYy9BQPZG for <regext@ietfa.amsl.com>; Tue, 30 Jul 2024 03:12:14 -0700 (PDT)
Received: from mout-b-112.mailbox.org (mout-b-112.mailbox.org [IPv6:2001:67c:2050:102:465::112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF37DC14F6FC for <regext@ietf.org>; Tue, 30 Jul 2024 03:12:12 -0700 (PDT)
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-112.mailbox.org (Postfix) with ESMTPS id 4WY9xz1RjyzDt49; Tue, 30 Jul 2024 12:12:07 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denic.de; s=MBO0001; t=1722334327; 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=nUZKLPM/vYaBF+w+E0Y/MACvLIqzL4KxOtiFluscylw=; b=KSL2Bl4CEuvWDukpIgp/UJDU57ffGDoVhFDV7nLU+/4ToRLthvQE8hy+ISZlKFF0LYIpzS MVvJj9gi1htmLG2BdWzw0QW60dPz4+lMKYXUnJ+zI4o+Ec6fZiRXAMw/XjWwaWg/C1KpVb 03ICAAqytwfdMM+msazPA3sqIdOviNZbrGuI1/m+EEBGDD/E0OnODEcIFdEg93tJz9ghUT Ak4e4cBW0mhVzzLK7EegyQfOKH0Lfh6fVCkvTyKo/r9YFbifcqi0LUm9InkmXreqVvIyqO uLc3YYADTLexUk0RKoaIw+u0e7WK7dup5mq5GuaF3vQ0jrTFD8AsGbcIMqivHg==
Message-ID: <600427ee-05ed-41ee-b1b4-8cf359f4f892@denic.de>
Date: Tue, 30 Jul 2024 12:12:04 +0200
MIME-Version: 1.0
From: kowalik@denic.de
To: Q Misell <q=40as207960.net@dmarc.ietf.org>, Gavin Brown <gavin.brown@icann.org>
References: <CAMEWqGvLueq-s34it58rykyOu0_bf4BXoEqC6k57M+BiMHjFig@mail.gmail.com> <6ED334AC-8211-4F00-887B-F233EBD50BAE@icann.org> <CAMEWqGs5b9vT2-ESZMSNtY0m0LKE4==eEgG8Fi9LNUTu_iRQZw@mail.gmail.com>
Content-Language: en-GB, de-DE
In-Reply-To: <CAMEWqGs5b9vT2-ESZMSNtY0m0LKE4==eEgG8Fi9LNUTu_iRQZw@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms090301020606060203070501"
X-MBO-RS-ID: 58f59d502786c81800f
X-MBO-RS-META: 7fttwf74m4ncd1rz5ch7nsbqxmz7y8js
Message-ID-Hash: DOVWLV3LLKCXAO3U3NTTJMQMC6KQCK3L
X-Message-ID-Hash: DOVWLV3LLKCXAO3U3NTTJMQMC6KQCK3L
X-MailFrom: kowalik@denic.de
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
CC: "regext@ietf.org" <regext@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [regext] Re: [Ext] DSYNC in EPP
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/Ap4hhKZB_26U2KTAfGN9-dPu8zM>
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>

Correct, the resellers would want to use it this way and likely they are 
not reflected in the data model of a registry.

DENIC is using such approach for General Contact/Abuse Contact where 
either registrar default setting applies or a specific one can be 
assigned for the domain through the provisioning protocol.

If an EPP extension is to be drafted I would rather generalise it to 
support more than just DSYNC.

In the DELEG WG discussion there is also a proposal of 
example._deleg.com. 3600 IN SVCB … [1]

The use case of registrar/reseller discovery will be also very 
interesting for Domain Connect. A TXT Record like 
example._domainconnect.com. can potentially be an answer.

I would be happy to work on this draft.

[1] 
https://datatracker.ietf.org/meeting/120/materials/slides-120-deleg-not-at-the-zone-cut

Kind Regards,

Pawel

On 30.07.24 10:09, Q Misell wrote:
> > You would only need an EPP extension in the scenario where different 
> domains under the sponsorship of the same registrar would need 
> different DSYNC information.
>
> This would very much be the case with resellers, or even a registrar 
> using one ICANN accreditation for multiple somewhat operationally 
> distinct brands.