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

Dmitry Belyavsky <beldmit@gmail.com> Sun, 05 June 2022 10:56 UTC

Return-Path: <beldmit@gmail.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 2C86DC14F733; Sun, 5 Jun 2022 03:56:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 sh983ih7CqmT; Sun, 5 Jun 2022 03:56:31 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 7D63DC14F740; Sun, 5 Jun 2022 03:56:31 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id i10so19311997lfj.0; Sun, 05 Jun 2022 03:56:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=82jMLcV1JcyvI+D6ZcqYgaJg2DyMBdhR1wE+pMk8hvM=; b=pKuL91BOlg105iSLvxeA2Gm0owlbaDDfuKWMcPL1aQ8qTP0iNIYyIbP7FTGsjU/r21 CkcZRX2BL3VEEKkQS1SxFjtvo3NJq9npv5V39hNaLknTV4tcFt12MKVV0lej/xPeXxmY dJeT9IIZh7ciqT87Uxu+qEm4Kvjk8BW702wBiG7FRPe+rgkTEDC9XdF2KnCpN/SFXkvC GtytNtGEK0thrJtuoQCLTHVxQVThhUadA1cdIJMufhUyqGWzElJXJSEcI7QqHYwEGcR6 ZV4uaHscwhUFTlFZ2RTZTWJxCe/NrCsUbR2oDKfSqCLckWAdkkCTpeXEPHKf9dJv03uB vXvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=82jMLcV1JcyvI+D6ZcqYgaJg2DyMBdhR1wE+pMk8hvM=; b=I5o61ZG6BGKA47K4RSZZuT0zHmcmliWx4QkgQGH4Fv+/tYK1tUSBpOUByKVDlJY/mf dhushdf8O0f/0lBTqgAzt2RAHTAdN7kKqeDNvFTRdmVDO9udR/fRWFpNWtzYUe6vtmrO AfWkE4QRpk2vrIB9NeivaWqzJm8AZ4umUM7+7SUqO78ITHdr7v3oydBo1vTFjLJRcops KKmU9ATrFXTWFqU5O0EKBmDLQuxRI0RfPKKO3cBmVlZbndKnqryQlN6YpmnoFKA9jljM PtIZ1ZXE3imLAeMuBmuL72gIa6l4N1oKdAG/QPviHGauHtqSKewrDzIL0BHKD0ZFgsGg f4sQ==
X-Gm-Message-State: AOAM533bJy76wTWT9p6psH3B15YBQbCZlS1CuOsND7RKgbvGZSDqJA4S jr8LJepzVWVWfMH/pErr+L/QV91J1yJDO3GP2Ts/W+QA
X-Google-Smtp-Source: ABdhPJxNEOYu7KalgsuzK22xcOiT2wKrWByxipfHDYk9kTeWz0n9DVaeqo3ECj0vcT9I9eNFBGGRpIx3Go7PKtprTOU=
X-Received: by 2002:a05:6512:3f01:b0:46b:a5ba:3b89 with SMTP id y1-20020a0565123f0100b0046ba5ba3b89mr12243667lfa.28.1654426588666; Sun, 05 Jun 2022 03:56:28 -0700 (PDT)
MIME-Version: 1.0
References: <165413189203.9986.8474357876864107354@ietfa.amsl.com>
In-Reply-To: <165413189203.9986.8474357876864107354@ietfa.amsl.com>
From: Dmitry Belyavsky <beldmit@gmail.com>
Date: Sun, 05 Jun 2022 12:56:16 +0200
Message-ID: <CADqLbz+3J8kJ06X7N9WoKON9M9Bo70roEaZAsHp5SY1QD-_z_w@mail.gmail.com>
To: Yoshiro Yoneya <yoshiro.yoneya@jprs.co.jp>
Cc: i18ndir@ietf.org, draft-ietf-regext-epp-eai.all@ietf.org, regext <regext@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001fdf5705e0b13530"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/gURrrv0LLXWn2pkNHhZO7TJQ7AE>
Subject: Re: [regext] 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: Sun, 05 Jun 2022 10:56:33 -0000

Dear Yoshiro,



On Thu, Jun 2, 2022 at 3:04 AM Yoshiro Yoneya via Datatracker <
noreply@ietf.org> wrote:

> Reviewer: Yoshiro Yoneya
> Review result: Ready with Issues
>
> Summary:
>
>   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:
>
>   None.
>
> 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.
>
> Many thanks for your review!

Yes, transfer becomes impossible in such situations, but the operational
practices are beyond the scope of this document.
It's more a matter of, say, ICANN recommendations.

-- 
SY, Dmitry Belyavsky