Re: [regext] Fwd: New Version Notification for draft-belyavskiy-epp-eai-01.txt

Dmitry Belyavsky <beldmit@gmail.com> Mon, 12 October 2020 19:59 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 1A8143A08AD for <regext@ietfa.amsl.com>; Mon, 12 Oct 2020 12:59:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 HmeB0_Eoigpw for <regext@ietfa.amsl.com>; Mon, 12 Oct 2020 12:59:51 -0700 (PDT)
Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (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 AB3C33A010A for <regext@ietf.org>; Mon, 12 Oct 2020 12:59:49 -0700 (PDT)
Received: by mail-ej1-x629.google.com with SMTP id u21so24938234eja.2 for <regext@ietf.org>; Mon, 12 Oct 2020 12:59:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mu9O3wiR2U9S1GfvjXsWcvqYdXMerHnrcFNu9ar7ST8=; b=gJhfYfzzn3XQACtQ71T4Kte0sANyuX5JBO9Et6rNqeopPB7rkSxvW5/vmQYyHonGtR dTDt24MAChFYuOmtMcVT58/FCRIb+OZKtGysDruWS3MXtt439k0mV7fSvox4NxiHbQaa n9r64qeTCAMVLySDO8ZS20+GyH6F8iYyngq+HuBzetohT2AUof3dSUXHuV0sZeslJnNz UYgIvUWPLrkHOcT9Lb2/oHjLx/pdn7Pqax9tqdhKFw+WAJICdBuSbucItqMmRUZgESfd ozRv4Eye9MZ3l7g4vmEARmpxlOImbMfGdB5AvEfx0aPcMuE39e9qsHtjAB3x4jBPMCI8 3Wnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mu9O3wiR2U9S1GfvjXsWcvqYdXMerHnrcFNu9ar7ST8=; b=b/put0t7yFIMndJ+mlyJ/zaAkwuRcvJzmAWXd8Nzb2wgZYJjg9YGQNGjgss4FmQl2T btsIjRDsscTI4w4AWNTjdi+uJyDIwVSdQEBsHTXgml5mX3LVq9HVbICakA3Cjf9wBcat ehI9eo70mpH58oN2c5hbA08EIzBKNC/R1IXityv5YSmQT8CpfnScPAy3AnGhkdJnD4le hY4ewa63dQ/2eKymsb53FGyUFzYShuGuCD0SKqw/K6yJFZUosMrdbxZFkHEKEIz5oz8w uFRjc6y6wompsVuaYzEGfi8HCNpSCbUCQuhRwhUK0eSKl6p2/7XW+2zW5aRFMqk/1Y4V jw4g==
X-Gm-Message-State: AOAM531q5daFTeCvaHQC2ZsFU/t4tCgf4f25qskE1z5GQ4wonwK7VX2y 6UC7AOw8pmXQCyrfzXA3rvEas9wKEdiW//eUUIk=
X-Google-Smtp-Source: ABdhPJwIUW833UpWr/PIEwll3VR5qBMIe43WNQl9qvy2pr9P5v8jq41+upFfGLfnXc+xaSjJwZHa3Kpv9MSivAUn4d8=
X-Received: by 2002:a17:906:3397:: with SMTP id v23mr29111569eja.212.1602532788108; Mon, 12 Oct 2020 12:59:48 -0700 (PDT)
MIME-Version: 1.0
References: <542572b0e6284550a9bee035bea2d6bf@verisign.com> <20201012155145.DB742234E06D@ary.qy> <CADqLbzJ4Qj=2MYp6L4kqVqrj4im+P-ouC+-qgLuwV5zgT3YHeg@mail.gmail.com> <C2AE5F0D-812A-4E50-B1EB-5DCF480AE2ED@verisign.com>
In-Reply-To: <C2AE5F0D-812A-4E50-B1EB-5DCF480AE2ED@verisign.com>
From: Dmitry Belyavsky <beldmit@gmail.com>
Date: Mon, 12 Oct 2020 22:59:36 +0300
Message-ID: <CADqLbz+PZb_vCNS5wtJk0AizvOUGT6eGKjB0LmVC9mADHXrRmA@mail.gmail.com>
To: "Gould, James" <jgould@verisign.com>
Cc: "johnl@taugh.com" <johnl@taugh.com>, "Hollenbeck, Scott" <shollenbeck@verisign.com>, "regext@ietf.org" <regext@ietf.org>
Content-Type: multipart/related; boundary="00000000000093b5d405b17ebdc6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/VMujVTS6gRs_J3Aa7Lx_vpBABRI>
Subject: Re: [regext] Fwd: New Version Notification for draft-belyavskiy-epp-eai-01.txt
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: Mon, 12 Oct 2020 19:59:53 -0000

Dear James,

If we indicate in the EPP greeting/Login support
of urn:ietf:params:xml:ns:contact-1.0
for old contact scheme without EAI and urn:ietf:params:xml:ns:contact-1.1
for a new scheme with EAI, will it be enough?

On Mon, Oct 12, 2020 at 10:53 PM Gould, James <jgould@verisign.com> wrote:

> Dmitry,
>
>
>
> The mechanism that we’ve used in the past is signaling support in the EPP
> greeting and login services.  Support for an EPP extension is signaled per
> RFC in the EPP greeting and login services.  We signal support for an
> operation practice via defining an XML namespace that is included in the
> EPP greeting and login services.  See
> https://tools.ietf.org/html/draft-ietf-regext-secure-authinfo-transfer-03#section-3
> for signaling support for draft-ietf-regext-secure-authinfo-transfer, and
> see
> https://tools.ietf.org/html/draft-ietf-regext-unhandled-namespaces-03#section-4
> for signaling support for draft-ietf-regext-unhandled-namespaces.
>
>
>
> --
>
>
>
> JG
>
>
>
>
>
> *James Gould *Fellow Engineer
> jgould@Verisign.com
>
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
>
> Verisign.com <http://verisigninc.com/>
>
>
>
> *From: *regext <regext-bounces@ietf.org> on behalf of Dmitry Belyavsky <
> beldmit@gmail.com>
> *Date: *Monday, October 12, 2020 at 3:16 PM
> *To: *John Levine <johnl@taugh.com>
> *Cc: *"Hollenbeck, Scott" <shollenbeck@verisign.com>om>, "regext@ietf.org" <
> regext@ietf.org>
> *Subject: *[EXTERNAL] Re: [regext] Fwd: New Version Notification for
> draft-belyavskiy-epp-eai-01.txt
>
>
>
> We could update the contact scheme version to indicate the EAI support as
> it is relevant for the contract mapping only.
>
>
>
> On Mon, 12 Oct 2020, 18:51 John Levine, <johnl@taugh.com> wrote:
>
> In article <542572b0e6284550a9bee035bea2d6bf@verisign.com> you write:
> >   [SAH] Perhaps there’s a case to be made for RFC 6530 being an update
> to RFC 5322. I’m going to see if I can run some tests to
> >confirm it, but I, too, suspect that EPP as-is won’t have any issues with
> internationalized email addresses.
>
> Urrgh.  RFC 6530 is not an update to 5322.  Don't go there.  I agree there
> is no
> great technical problem sending UTF-8 address strings through EPP.
>
> I'm getting the impression that what we need is a way for the client
> to ask the registry whether it can handle EAI addresses so it knows
> what to accept registrants.  I can imagine a variety of ways to do that.
>
> R's,
> John
>
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext
> <https://secure-web.cisco.com/1E2O9BAxjfPFRfBkfkdxxMTw4FeUHvpkoq0D8pXADkch3J8zQcnJFteI9-DnviuVEI5t6W5sTnonl8zXd9JKRrx-gGoGyQXdMImvWtBZf9dYNpujyBnEMqxC1Ly9rBkcppwn1Q8waImJkzHzgPSR5W076Bq_Qj1fvERIlfLyfP1t5QgoTwZ2gpmuX85-A2Z_DzpzUdNJ-F5_W-JNHhs7NJcXcs3bEciqsCWn8Pogs9sG9e5TijoAKpJc7gqcV6DlHoJghQ11jLtbMvnQ48zpr3_uROAOzByjqHEoLAyKKmWY/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext>
>
>

-- 
SY, Dmitry Belyavsky