There are a couple EPP Extension RFCs that may be of use with the Organization 
Mapping in RFC 8543 and Organization Extension in RFC 8544 that do support the 
definition and linkage of multiple organization types to registry objects, such 
as Resellers and DNS Providers.  The Organization Mapping could also be used to 
provision registrar information and since it’s an EPP object, it can be 
extended with a command response extension for attributes like DSYNC.  If DSYNC 
is an attribute of the registrars and resellers, then that could be a use case 
for the Organization EPP RFCs.

--

JG

[cid87442*image001.png@01D960C5.C631DA40]

James Gould
Fellow Engineer
jgo...@verisign.com<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com<http://verisigninc.com/>

From: "kowa...@denic.de" <kowa...@denic.de>
Date: Tuesday, July 30, 2024 at 6:12 AM
To: Q Misell <q=40as207960....@dmarc.ietf.org>, Gavin Brown 
<gavin.br...@icann.org>
Cc: "regext@ietf.org" <regext@ietf.org>
Subject: [EXTERNAL] [regext] Re: [Ext] DSYNC in EPP


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<https://secure-web.cisco.com/15FbRe5fpRvlrkkAq0HkR-BPdonBYPdJ1OdxjUMtXaldWy9CK6PKxzuPBfeK_iwa3DkCNRFim9k2m8hxPU3a_SfTjNu4bRyTTyHmfoZMa_T_a5PLaHngENA44Sj6naTkbL90wAdN_BnHNGdSBhg40tz9azdIZgVCk0rI0JisrzXsG0sUOhqN5cHVfx__QTi3V91E3rigZuY7qnd1P-ALesfY8T9z2CUcwOukdMl2bEa0J1LOIqeq5vacoe7xTDuHG-vLScKO2TiJg3k5ekgBq3Q5rToH8MQsfZKsTNohYhZA/https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2F120%2Fmaterials%2Fslides-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.
_______________________________________________
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org

Reply via email to