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

Yoshiro Yoneya via Datatracker <noreply@ietf.org> Thu, 02 June 2022 01:04 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: regext@ietf.org
Delivered-To: regext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A86FC15AACB; Wed, 1 Jun 2022 18:04:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Yoshiro Yoneya via Datatracker <noreply@ietf.org>
To: i18ndir@ietf.org
Cc: draft-ietf-regext-epp-eai.all@ietf.org, regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.3.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <165413189203.9986.8474357876864107354@ietfa.amsl.com>
Reply-To: Yoshiro Yoneya <yoshiro.yoneya@jprs.co.jp>
Date: Wed, 01 Jun 2022 18:04:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/FHS8pycbux2J7MtKtTtmAfamrq4>
Subject: [regext] I18ndir early review of draft-ietf-regext-epp-eai-10
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 02 Jun 2022 01:04:52 -0000

Reviewer: Yoshiro Yoneya
Review result: Ready with Issues


  This draft is in good shape regarding protocol.  Regarding to operation,
  having an additional guidance for registrar transfer from EAI supporting
  registrar to non EAI supporting registrar would be better.

Major issues:


Minor issues:

  When a registrant who has only EAI contact addresses attempts to transfer a
  domain from EAI supporting registrar to another non EAI supporting registrar,
  then transfer of contact information will cause failure.  If there were
  additional operational guidance addressing this issue in this draft will be
  helpful for registrar operators.  For example, when loosing registrar who is
  supporting EAI received a transfer request, it should check whether the
  registrant has only EAI contact addresses, and if it was true, the registrar
  should advice the registrant to provide alternative ASCII contact addresses
  in advance for the successful transfer.