IETF Logo Mail Archive

Re: [regext] [I18ndir] I18ndir early review of draft-ietf-regext-epp-eai-10

John Levine <johnl@taugh.com> Wed, 08 June 2022 20:59 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 1E26EC157B47 for <regext@ietfa.amsl.com>; Wed, 8 Jun 2022 13:59:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.86
X-Spam-Level:
X-Spam-Status: No, score=-6.86 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_DNSWL_HI=-5, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=d62qS3dm; dkim=pass (2048-bit key) header.d=taugh.com header.b=PWmzc+wn
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 tnAWGyEQfw-7 for <regext@ietfa.amsl.com>; Wed, 8 Jun 2022 13:59:18 -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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99B7FC15948F for <regext@ietf.org>; Wed, 8 Jun 2022 13:59:18 -0700 (PDT)
Received: (qmail 20348 invoked from network); 8 Jun 2022 20:59:16 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=4f76.62a10da4.k2206; bh=P5PT55DYe3qeHl7tg875J4VfbRlSzHsOn2RFxX5ydA4=; b=d62qS3dmf/mDbKVRM8TA7v+Pnpzwx+G11NOwPiyAHBHR5p5heIrw2O6VU9LIFc8SrVyIGYCaTaTZuJ/3KyUuEbWl42a2of6ci0QSvRnnuj7PJJ8wrV/DOjfYhHsbia6H/l+9XASbdiqpcyv6ZAsPb9rFtalmX3XCqz3oZG5eE9NYlP2KHJFpizhaKvzvngqtVpKprQj7z/euHaFPA3q2+gM2xC1pLSsNV86bxBVeab86PAj3x804dAWUlmVhR+eB5NLoGIwfwNV6R3j8OO+D/VH9pyNHMB6XVx/584Pe2E5o49tJ80csniEk5/9FtYzZtxt7f4V4zdCXcqv5CqR1qw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=4f76.62a10da4.k2206; bh=P5PT55DYe3qeHl7tg875J4VfbRlSzHsOn2RFxX5ydA4=; b=PWmzc+wn+ieOz0gFM784KPz8vVDrkcw/VBkHS4dr7kTupnW99H49Yu7YiI10QI4+MjXYhWAUCvFtv2mGcLjhzfKYs9CKH4EB3bmFYx81wad3aNSBEBvt49fxoHaP0T2lCVbYwIMjVdIafJwHBJbfqoVuJF8cxxWLtQANeAti35HLTuj1uc1+X4EMOkOLsgj/MehiTua3Hog5jh97UwKs02W1ElWEYS3WxLqFkHSHpHfIHbeiy91kLfEfbza1Y2i3LAIvz+XjtxNBD8+h6D96znrUAHRMnT+9hiTEtS6KVK5KOzZ8VxKARRFCr2rmHhUn7KumqmmMAglSbn0LItOoJA==
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 AES-256-GCM AEAD) via TCP6; 08 Jun 2022 20:59:16 -0000
Received: by ary.qy (Postfix, from userid 501) id DB4764341BC2; Wed, 8 Jun 2022 16:59:15 -0400 (EDT)
Date: Wed, 08 Jun 2022 16:59:15 -0400
Message-Id: <20220608205915.DB4764341BC2@ary.qy>
From: John Levine <johnl@taugh.com>
To: i18ndir@ietf.org, regext@ietf.org
Cc: jgould@verisign.com
In-Reply-To: <8E7CE5FC-3A1D-419A-9DD2-3444A2E91C4B@verisign.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/k5AYpOql8sZJ29wJgrTaT3zOUUw>
Subject: Re: [regext] [I18ndir] I18ndir early review of draft-ietf-regext-epp-eai-10
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2022 20:59:24 -0000

It appears that Gould, James <jgould@verisign.com> said:
>Technically a transfer of the domain name doesn't include a transfer of the contact information, where the gaining registrar
>can create a new contact to link to the domain name once the domain name transfer completes.  Transfers of a contact in EPP
>is rarely done, but it is supported in EPP RFC 5733. ...

I agree that most of the time when people transfer domains, they enter new contact info at the new registrar.

A more practical issue is that the new registrar generally sends
e-mail to the old owner to notify them or in some cases to ask for
confirmation. If the old registrar handles EAI addresses and the new
one doesn't, that's likely to fail, but I also don't think it's our
problem to solve here.

R's,
John

v2.23.0 | Report a Bug | By Email