[regext] Re: [Ext] DSYNC in EPP
John Levine <johnl@taugh.com> Tue, 30 July 2024 16:36 UTC
Return-Path: <johnl@iecc.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 1811CC14F699 for <regext@ietfa.amsl.com>; Tue, 30 Jul 2024 09:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.857
X-Spam-Level:
X-Spam-Status: No, score=-1.857 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="B0e7P9UV"; dkim=pass (2048-bit key) header.d=taugh.com header.b="w0XBw6HU"
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 fsA9mMJV5PDb for <regext@ietfa.amsl.com>; Tue, 30 Jul 2024 09:36:50 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 1BFD2C14F605 for <regext@ietf.org>; Tue, 30 Jul 2024 09:36:49 -0700 (PDT)
Received: (qmail 73970 invoked from network); 30 Jul 2024 16:36:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=120ef66a9169f.k2407; bh=zf3cTTbEw1B6KIaARy6gk48nv1cUziDIRvYEMa6BxcM=; b=B0e7P9UVkndtEz4naQur6vdB+s2xEsfp5Y5vaKa/2nF1ODlxF3pR32lotyVXpjZjum5N12CE4GwcW5cGxnGHZTEjP1VJD9HTyBmptfs4xF+N7X4c7y/3yjM1nIVoOM7tVVWdKtxO+4VaVIN/TcUiIzNRIGgTUhjzq80lQTZF0pdxRwlmc2mk9r8XZ7QuyLGIrwxS5+MYHYhuZ4Wv07rXRvaQfBr8yCYLGQkf+FLW444Pwq+IcJgWi3X7JY7X5vX/P2ZFoLkNgjPkV5n4/7PZ8q4q0qIM8t5gADph/QMIDAlgK1ahLwkyRC4eyP+Cv0gIERV6ihBUtEQbgbuG+zR5nA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=120ef66a9169f.k2407; bh=zf3cTTbEw1B6KIaARy6gk48nv1cUziDIRvYEMa6BxcM=; b=w0XBw6HUfNcN90iTBqTdUhWUWg+kFktV/Nt6KctNJaW47CwsTUdneLa77+Cy9Fz1E5Rf9zDBaVyiARhzlyo2N1ncN2e5D+5aZXk8l4jNuam/etNaMO4fFwOb+E5uYL356WBy4GXOWkLL0JgS8rUb/ERf/yXaXoF9kbz5RdrC+oDuilTOGhUZFMWLCwyMijyDPOVaPgwR+Vvv6Ih38u6ryn/jemVljWZeR9g7oAJm4eXEoF39d0oEVRmZjQC3WN14vbj8taFS3KA0c6WYa72oDEPwQiISfgkGLrWF0488FiaAqmt7H20PVQgx0zU7xR1qVE32VNKg0finFAL/X05RJg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 30 Jul 2024 16:36:47 -0000
Received: by ary.qy (Postfix, from userid 501) id 043F390801A7; Tue, 30 Jul 2024 12:36:46 -0400 (EDT)
Date: Tue, 30 Jul 2024 12:36:46 -0400
Message-Id: <20240730163647.043F390801A7@ary.qy>
From: John Levine <johnl@taugh.com>
To: regext@ietf.org
In-Reply-To: <CAMEWqGs5b9vT2-ESZMSNtY0m0LKE4==eEgG8Fi9LNUTu_iRQZw@mail.gmail.com>
Organization: Taughannock Networks
References: <CAMEWqGvLueq-s34it58rykyOu0_bf4BXoEqC6k57M+BiMHjFig@mail.gmail.com> <6ED334AC-8211-4F00-887B-F233EBD50BAE@icann.org> <CAMEWqGs5b9vT2-ESZMSNtY0m0LKE4==eEgG8Fi9LNUTu_iRQZw@mail.gmail.com>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: AR3HKL5SOGTKCJVRIKIJ2KOXS2IX6AIB
X-Message-ID-Hash: AR3HKL5SOGTKCJVRIKIJ2KOXS2IX6AIB
X-MailFrom: johnl@iecc.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: q@as207960.net
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/XhNlnxO8hysvZCpIuVaW2FzCgQI>
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>
It appears that Q Misell <q@as207960.net> said: >-=-=-=-=-=- > >> 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. It depends. I resell Tucows and all my updates are routed through the registry via their API. That could certainly work the other way, the registrar gets the signal and forwards it to the reseller. Also, a registrar could handle the provisioning update stuff itself and then tell the reseller about it rather than expecting each reseller to create its own DNSSEC update logic. R's, John
- [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