[regext] Re: [Ext] DSYNC in EPP
"Gould, James" <jgould@verisign.com> Tue, 30 July 2024 15:41 UTC
Return-Path: <jgould@verisign.com>
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 C0DE0C14F6E2 for <regext@ietfa.amsl.com>; Tue, 30 Jul 2024 08:41:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.006
X-Spam-Level:
X-Spam-Status: No, score=-7.006 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, HTTPS_HTTP_MISMATCH=0.1, 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_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=verisign.com
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 ZutPgNTBXdfR for <regext@ietfa.amsl.com>; Tue, 30 Jul 2024 08:41:43 -0700 (PDT)
Received: from mail1.verisign.com (mail1.verisign.com [72.13.63.30]) by ietfa.amsl.com (Postfix) with ESMTP id 045ECC14F6BA for <regext@ietf.org>; Tue, 30 Jul 2024 08:41:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=19482; q=dns/txt; s=VRSN; t=1722354103; h=from:to:cc:date:message-id:references:in-reply-to: mime-version:subject; bh=n0i7a/gBqMzJIUp12G1D7D/Y/+NHEArwSyQxXgUaf2s=; b=U4PKdykkmCYBMtBKKjF59QpvjYXBwRifZNZqnmaXz4/bK5zHLl9isR0m v1B/B2rSWjhRq/iIKZIWgPC/50dPV5LaniWMlzJ3NJrPzqWWlL+DBEvqp spbju53HELMiGlRCrdRZeGacW99bHY7CoqXr7PSiuYE67bUYBbcpYgn5Y Te59Rp1WUiBokZi89zvCO8m1zuE0TPSGtTjPtjr8coMfPVRWZejtDk1Cp H5o+5ehVN1sf7EWiW7vj7Tx8a1Ui9kggWUj7T6stzIMlxa/ckDAO4Ryws Lw6UFnq/1FlhRdUif1/XJVRVMRZQkNLTtFJYBSyqxuR1lUXSwbLWvTNBQ w==;
X-CSE-ConnectionGUID: HD0SOGZOSIuzikh/3Qu9iQ==
X-CSE-MsgGUID: Ainm9lcdQMeN7wgFuGRiTQ==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:ecN+2q1MPzXP+QGyfPbD5XRwkn2cJEfYwER7XKvMYbSIYAOW5UVek zNIDGmGO+HKPDXFz+oGPt+xoBgAvcXRyN9iSVRk/ihnQy5BopaZW43GJEr6Y32Zd8adHRM64 pkVMdOQJZ1oF3WC+Bn2b+Xv83Mn3vnXS9IQZAKl1gVZHGeIHw990Es98wJAvrNVvDSZP++sk dqi/JODMwb+imUuPmsZ4Pzd8Esw5q+i5WtH5QFnbPtH4AaOxnIYMskSdPq7R5fariu4PcbhH rqek+vplo/9101wYj9wuu+jKiXmepaLYE7TzCMQA/X/6vR7jnRa+r4hM/YBYltghTyMntRgo P1ArpXYpT0BZ8Ugo8xDFUEJe81CFfceouOffiPn6Zb7I3DuKBMA/d0/VCnaAqVFoo6bMUkWn dQEJTYEaAy0hu7e6NqTVul2i80/G9LgNYUZt2sI5Wmx4SEOGM2rrw3ivLe07R9o7ix8Na+2i /kxMFKDWC/9jyhnYT/7Prplxbv12SOvG9FvgAn9SaIfuwA/xSQviOS9aIK9ltaiHa25lW7Az o7KEviQ7rj3+7VzxBLcmk9AiNMjkgvbdNopM5KK0cVLnU+SxWxUUyQLBFqC9KzRZk6WA7qzK mQ+wAx3ko4fxBTxCMf2WAeg5neI+AAGQNwWGOo/gO2P4vOMpV/GXS5dE2UHNI1OWMweHFTG0 neLkNT0ATBHrrCPSGmc+bHSpjS3UcQQBTRSO3JfFlZeizXliKgyiBeeSt1vKYu4qILqFh/t7 AqLkBFr0t3/iuZOjc1X52vvgDWzr5zITSY56wPWVSSp42tRfdv5P4WzswCEvKgYaoCUUnGNu XEekI6f4fwAS5aXm0SlT+wTHbfv7eyCLzv0gFVmGZ9n8C6ik1a5cI9d8C1WJUp1PIADYzCBX aPIkQlL4sZMOna6NfUyeJyrTcEr1u3qEpLvTPaNKMRUeZ43fwiClM1zWXOtM6nWuBBEuckC1 V2zLa5A0V5y5Xxb8QeL
IronPort-HdrOrdr: A9a23:GXOjIqN4/AYcs8BcTuKjsMiBIKoaSvp037By7TEUdfRUGvb1qy ncpoV96faUskdqZJhOo7C90cW7K080sKQFhLX5Xo3SITUO2lHYT72KhLGKq1bd8m/Fh4xgPM xbHJSWfeeQMbEMt6jHCWeDfurIi+P3lpxAzd2utkuEB2tRGtldBilCe32mLnE=
X-Talos-CUID: 9a23:6Jb7QWrgAS1t5ZkjBHchj2LmUeAJKkb640X3GG6lG2dqSPrOcELB+Zoxxg==
X-Talos-MUID: 9a23:EGnWWwru+nQ00VEhrc8ezxhjMsI556+iMWUAt8oZtOeZGhZxBw7I2Q==
X-IronPort-AV: E=Sophos;i="6.09,248,1716249600"; d="png'150?scan'150,208,217,150";a="38653353"
Received: from BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) by BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.37; Tue, 30 Jul 2024 11:38:28 -0400
Received: from BRN1WNEX01.vcorp.ad.vrsn.com ([10.173.153.48]) by BRN1WNEX01.vcorp.ad.vrsn.com ([10.173.153.48]) with mapi id 15.01.2507.037; Tue, 30 Jul 2024 11:38:28 -0400
From: "Gould, James" <jgould@verisign.com>
To: "kowalik@denic.de" <kowalik@denic.de>, "q=40as207960.net@dmarc.ietf.org" <q=40as207960.net@dmarc.ietf.org>, "gavin.brown@icann.org" <gavin.brown@icann.org>
Thread-Topic: [EXTERNAL] [regext] Re: [Ext] DSYNC in EPP
Thread-Index: AQHa4laFRQ1SpYLGL0qxyQaoqn6VrbIPLeqAgAAiUACAABgjgA==
Date: Tue, 30 Jul 2024 15:38:28 +0000
Message-ID: <E212D7A2-739D-44CC-B093-DF319C930D79@verisign.com>
References: <CAMEWqGvLueq-s34it58rykyOu0_bf4BXoEqC6k57M+BiMHjFig@mail.gmail.com> <6ED334AC-8211-4F00-887B-F233EBD50BAE@icann.org> <CAMEWqGs5b9vT2-ESZMSNtY0m0LKE4==eEgG8Fi9LNUTu_iRQZw@mail.gmail.com> <600427ee-05ed-41ee-b1b4-8cf359f4f892@denic.de>
In-Reply-To: <600427ee-05ed-41ee-b1b4-8cf359f4f892@denic.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.82.24021116
x-originating-ip: [10.170.148.18]
Content-Type: multipart/related; boundary="_004_E212D7A2739D44CCB093DF319C930D79verisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Message-ID-Hash: GQGDY5HFAD7U76QQCXXR6UZBL3KBMEUL
X-Message-ID-Hash: GQGDY5HFAD7U76QQCXXR6UZBL3KBMEUL
X-MailFrom: jgould@verisign.com
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/SySmg7_W1U8Q0XsruFzOcdRP01g>
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>
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 jgould@Verisign.com<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgould@Verisign.com> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://verisigninc.com/> From: "kowalik@denic.de" <kowalik@denic.de> Date: Tuesday, July 30, 2024 at 6:12 AM To: Q Misell <q=40as207960.net@dmarc.ietf.org>, Gavin Brown <gavin.brown@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] DSYNC in EPP Q Misell
- [regext] Re: [Ext] DSYNC in EPP Gavin Brown
- [regext] Re: [Ext] DSYNC in EPP Q Misell
- [regext] Re: [Ext] DSYNC in EPP kowalik
- [regext] Re: [Ext] DSYNC in EPP Gould, James
- [regext] Re: [Ext] DSYNC in EPP John Levine
- [regext] Re: [Ext] DSYNC in EPP Q Misell
- [regext] Re: [Ext] DSYNC in EPP John Levine