[regext] EAI in EPP from a registrar point of view
Dmitry Belyavsky <beldmit@gmail.com> Thu, 19 November 2020 09:03 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 017D33A1242 for <regext@ietfa.amsl.com>; Thu, 19 Nov 2020 01:03:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RyFwWt3n4lZS for <regext@ietfa.amsl.com>; Thu, 19 Nov 2020 01:03:25 -0800 (PST)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E8B83A1238 for <regext@ietf.org>; Thu, 19 Nov 2020 01:03:25 -0800 (PST)
Received: by mail-ej1-x62c.google.com with SMTP id lv15so976022ejb.12 for <regext@ietf.org>; Thu, 19 Nov 2020 01:03:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=gCqtFezZ+AW2cVyUErqBxldTulYKbpk2TeUBIo/cTtI=; b=o/WJMwrf7Y+5AJWTMHPNhtYdXu3aa4rR7a28JQ7jkTO8wID2pOQOcajOAb3bnaXLDa XKfSUWUVhqI2wo+zEc9byh1ufOEt95gjDFCFjgaHOw6xUhJdN6+616J7Sr4CKlFtz7pc b0k/wyyMlQF+xjBwCEpWjkAzqc3hJJ+2pSMCLKe9Lm7A7Ir7FJFOQkiQGEuqxWyRP3mm XGABxCUpPQLaxXIdA0yl+OqrUG2F/H2gFIxTKdP2VLDe7Uv9sh6aKDE1O6Do1ptaCIvs 6mrg9jJfAy6QOT1hGiuh442vvXtibbx5vubXZsLLCLXBblKNJBwpJaxWXXdTVo/hBABz QQMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=gCqtFezZ+AW2cVyUErqBxldTulYKbpk2TeUBIo/cTtI=; b=TlFWC0IF7uOsqfhEjOmMPbBachkii5/3LaR04AD6vefuz5xi+/wPELwZQEpuvVDTEo e8zudEmcsmW8USu63ixoFExhTkJOujRCVTyfL4eixrVBg0KsItYp8eAvUXVVnmRZlNlF t8EtAjomJHaspDZe+8y/jtw3BjH3b0gnwhkCY5a8J6paD1asZ5KFlr/K1JasoDwhsowl bdaolsTWCquLycrcFLpQtPZXgIovxRuO79+9W3I3wgi+OqDUGJfuEH+otHE5nrEnlIbb 2ti6Q/p9LKju7pltHCzicMGaS27H53fYFTvNGomE+1uaGsGd3dV6zcigvgwrV7LCZcrs 0YOw==
X-Gm-Message-State: AOAM533PXW2nZDKInm+cMA6ODQdNFnaUBUbnTm7lbaNlqJO77IEWMFa/ W6xE01pAHp1Pkr30Hx0vLHpuhWdoFzoEAYhi7TppUN2/AUQ=
X-Google-Smtp-Source: ABdhPJzCUFy7Q3rH0Nwg2fBwtnBxTaBpMGJqKKG9A9pr+oKWeXko0ayHYkdAbu9E/KeifJkX/UB45D+8dW2BCrk4aGM=
X-Received: by 2002:a17:906:c1c3:: with SMTP id bw3mr26237221ejb.126.1605776603430; Thu, 19 Nov 2020 01:03:23 -0800 (PST)
MIME-Version: 1.0
From: Dmitry Belyavsky <beldmit@gmail.com>
Date: Thu, 19 Nov 2020 12:03:11 +0300
Message-ID: <CADqLbz+VPXYAgrCQY9g-0_vuUxioY7H6GApt4ek2u3gJHXqMPg@mail.gmail.com>
To: regext@ietf.org
Content-Type: multipart/alternative; boundary="00000000000009459705b47200d4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/6ujMla-PfmjYEq_ecuuGNv1eQRI>
Subject: [regext] EAI in EPP from a registrar point of view
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 19 Nov 2020 09:03:27 -0000
Hello, I think it's worth providing some thoughts about the EAI support in EPP from a registrar's perspective. >From a registrar's perspective, when the registry provides some feature, the registrar has to support it in most cases. When a registry supports EAI, the registrar should be ready to at least get an EAI address in the <info> command on transfer. Registrars usually got accreditation for working with more than one registry, and have to write some registry-specific code. In the case of EAI, the changes should require at least accepting EAI addresses from the clients not having the ASCII ones and some mechanism providing the valid ASCII email address in the case when such client wants to register a domain in a registry that does not support EAI. -- SY, Dmitry Belyavsky
- [regext] EAI in EPP from a registrar point of view Dmitry Belyavsky
- Re: [regext] EAI in EPP from a registrar point of… Hollenbeck, Scott
- Re: [regext] EAI in EPP from a registrar point of… Taras Heichenko
- Re: [regext] EAI in EPP from a registrar point of… Hollenbeck, Scott
- Re: [regext] EAI in EPP from a registrar point of… Gould, James
- Re: [regext] EAI in EPP from a registrar point of… Taras Heichenko
- Re: [regext] EAI in EPP from a registrar point of… Hollenbeck, Scott
- Re: [regext] EAI in EPP from a registrar point of… Taras Heichenko
- Re: [regext] EAI in EPP from a registrar point of… Klaus Malorny
- Re: [regext] EAI in EPP from a registrar point of… Taras Heichenko
- Re: [regext] EAI in EPP from a registrar point of… Gould, James