[regext] Re: [Ext] DSYNC in EPP

Gavin Brown <gavin.brown@icann.org> Tue, 30 July 2024 08:00 UTC

Return-Path: <gavin.brown@icann.org>
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 8DFD9C14F6F3; Tue, 30 Jul 2024 01:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
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 YbP-dQFfiCFh; Tue, 30 Jul 2024 01:00:03 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) by ietfa.amsl.com (Postfix) with ESMTP id 5257DC14F6F0; Tue, 30 Jul 2024 01:00:03 -0700 (PDT)
Received: from MBX112-W2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.5]) by ppa2.lax.icann.org (8.18.1.2/8.18.1.2) with ESMTPS id 46U802ZJ014031 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 30 Jul 2024 08:00:02 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Tue, 30 Jul 2024 01:00:01 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) by MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) with mapi id 15.02.1544.011; Tue, 30 Jul 2024 01:00:01 -0700
From: Gavin Brown <gavin.brown@icann.org>
To: Q Misell <q=40as207960.net@dmarc.ietf.org>
Thread-Topic: [Ext] [regext] DSYNC in EPP
Thread-Index: AQHa4lAy6b5dTGy4tEKhNdgjibCPprIPXawA
Date: Tue, 30 Jul 2024 08:00:01 +0000
Message-ID: <6ED334AC-8211-4F00-887B-F233EBD50BAE@icann.org>
References: <CAMEWqGvLueq-s34it58rykyOu0_bf4BXoEqC6k57M+BiMHjFig@mail.gmail.com>
In-Reply-To: <CAMEWqGvLueq-s34it58rykyOu0_bf4BXoEqC6k57M+BiMHjFig@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.47.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B0C40CC4DF14F94DBC3C427E118747F8@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.28.16 definitions=2024-07-30_08,2024-07-26_01,2024-05-17_01
Message-ID-Hash: BDFM6YLHE3CJHAXKSQWOS7Z3E4LGYCLM
X-Message-ID-Hash: BDFM6YLHE3CJHAXKSQWOS7Z3E4LGYCLM
X-MailFrom: gavin.brown@icann.org
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/mVH5KyCsFBoQDtpZTl4GdeUuNYY>
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>


> On 30 Jul 2024, at 08:13, Q Misell <q=40as207960.net@dmarc.ietf.org> wrote:
> 
> Moin,
> 
> There has been work recently in DNSOP on Generalised DNS Notifications (https://www.ietf.org/archive/id/draft-ietf-dnsop-generalized-notify-02.html [ietf.org]
> This draft is mostly targeted at CDS/CDNSKEY, but is general to other notifications.
> 
> As the draft currently stands this requires a record at example._dsync.com [dsync.com] to direct notifications for example.com [example.com] In some cases the target for these notifications would usefully be the registry, however in others the notifications would be better routed to the registrar (e.g. in the case of a registrar implementing CDS themselves).
> 
> Adding these records to the parent's DNS would require an extension to EPP; is there an appetite in the WG for an EPP extension to manage these DSYNC records?

This is not necessarily true. It may be the case that each registrar would have a single DSYNC configuration for all its domains under management, in which case it is information that can be collected once at onboarding (or when the registry begins supporting DSYNC).

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.

It would be worth validating this assumption before going to the effort of developing an extension.

G.

--
Gavin Brown
Principal Engineer, Global Domains & Strategy
Internet Corporation for Assigned Names and Numbers (ICANN)

https://www.icann.org