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

Dmitry Belyavsky <beldmit@gmail.com> Mon, 12 October 2020 20:39 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 908723A0978 for <regext@ietfa.amsl.com>; Mon, 12 Oct 2020 13:39:24 -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 Y2jQaK8XVgra for <regext@ietfa.amsl.com>; Mon, 12 Oct 2020 13:39:22 -0700 (PDT)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (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 324733A0976 for <regext@ietf.org>; Mon, 12 Oct 2020 13:39:21 -0700 (PDT)
Received: by mail-ed1-x52b.google.com with SMTP id g4so18507795edk.0 for <regext@ietf.org>; Mon, 12 Oct 2020 13:39:21 -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=QkObVF9OFFhWQqbMoWMRvNI6SGsc+zDNo35yejg1ZLM=; b=dOjV1xB2+xq6rSpVzkcyCEfLMrACk0aaI46d/E5LNnQRQNnH5dh7EL3ue1cfPAZy+j dzG8zt3qBo5ptjOUH+2g0XQ9gKIImM3Cwy05cOJlpp8hcmc+/1UclLXZDdbj2NQhfDIN lrqUXcdg4Go1zJ8YlHqeId+v9UeorLoOAANgRwTMP4QRrxEyrbGpfN/apvvFIv94vLxY oolId0o7DeDOpyLyd259KdI6YuXWiBfLfZPkv5mVrt+eiexxToYmiFcqOmb8IZF/e1iP ax3OWJXUqsKCYq6nTzwZDnVsVA/W0nbiuZwW7jsiXifTRNxShWFoRn46up0AWXGGas3Y ja8Q==
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=QkObVF9OFFhWQqbMoWMRvNI6SGsc+zDNo35yejg1ZLM=; b=MMv54kd+QMbusUHrK6D9i8maUoP+Kax25dn2w+2H0eLPqPfD90igsDzb0pT9U8+3G9 NvZLgX42m1hbmBwuA0N1YG9CneBUnU4ROZa/4xGqlx9qzB9YXXfyVwNP4AvE8mz9Xt6I y+S+4/KS9UC1HmImSRoEK9priENI96zIc0N3bF0BfgJopY84/UPLLxWjVtm/3VdMfdTP acg0lpKsoa9BIP1dTQ690vsFpR1VkFq8ZrwoBs+949c99Lsrf61Xow6J1UGMJ05tCx1L 8J90tVqz26AAwxO/+gczg9gOHeuoIMmk7jSqu3hIysPpwyIkqWPV64t8xErQL5xPVine 0elg==
X-Gm-Message-State: AOAM532TT1cSA0luXcdCVhaOxHiJcf6u7XpJa7+7CZSqHu3tCXeGwZfQ YcuTM47B6wRYr6at8ZBZHtFfuecKdaNFOpBgu6M=
X-Google-Smtp-Source: ABdhPJzz7GIjOHgZRegOiwFKmaTat54fTvutwZsJwSU2dgAofBRVml5N5YYuYZVKR4llNTCW5KAPb/c6rd38fq/iqgs=
X-Received: by 2002:aa7:c347:: with SMTP id j7mr16895581edr.353.1602535159660; Mon, 12 Oct 2020 13:39:19 -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> <CADqLbz+PZb_vCNS5wtJk0AizvOUGT6eGKjB0LmVC9mADHXrRmA@mail.gmail.com> <ABF85EEC-68E1-4A58-8D1E-B1CBB1121071@verisign.com>
In-Reply-To: <ABF85EEC-68E1-4A58-8D1E-B1CBB1121071@verisign.com>
From: Dmitry Belyavsky <beldmit@gmail.com>
Date: Mon, 12 Oct 2020 23:39:07 +0300
Message-ID: <CADqLbzKHcw3rr5L6qKEU4up0icYK8nBx7yHAUBvdcVYpn3EOng@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="000000000000eea6d405b17f4a4d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/5qKzPdnXtaZXlX1skjRgqspQW4g>
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 20:39:25 -0000

Dear James,

We have some options that sound reasonable (for me)

1. Treat RFC 6530 as an update to RFC 5322 (not the best idea, really).
2. Indicate accepting EAI via new contact namespace, accept in the
<contact:email> tag
3. Indicate accepting EAI via eppEAI namespace, accept in the
<contact:email> tag
4. Indicate accepting EAI via eppEAI namespace, accept in the
<someext:email> tag

There is also an option "Do nothing, silently accept EAI in the
<contact:email>" which is
implemented in Newstar and TANGO registration systems.

I think we need some consensus to prefer any of these options and I don't
see any options to find out such a consensus than submit a draft and get
some feedback.
Personally, I would prefer either option 2 or option 4.

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

> Dimtry,
>
>
>
> I don’t believe there is the need for a new contact XML namespace, but it would be associated with the new XML namespace (urn:ietf:params:xml:ns:epp:eppEAI-1.0) defined in draft-belyavskiy-epp-eai.
>
>
>
> --
>
>
>
> JG
>
>
>
>
>
> *James Gould *Fellow Engineer
> jgould@Verisign.com
>
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
>
> Verisign.com <http://verisigninc.com/>
>
>
>
> *From: *Dmitry Belyavsky <beldmit@gmail.com>
> *Date: *Monday, October 12, 2020 at 3:59 PM
> *To: *James Gould <jgould@verisign.com>
> *Cc: *"johnl@taugh.com" <johnl@taugh.com>om>, "Hollenbeck, Scott" <
> shollenbeck@verisign.com>gt;, "regext@ietf.org" <regext@ietf.org>
> *Subject: *[EXTERNAL] Re: Re: [regext] Fwd: New Version Notification for
> draft-belyavskiy-epp-eai-01.txt
>
>
>
> 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
> <https://secure-web.cisco.com/1kbbME8WxKH25Af398m-OdqUFjso557LWijQiFXQJ0UKuX4cZCZzvDbYaHCY2_clcdljSgNx33sKFt3KGtedibBS3rd7Wn-tjukLzyRje6FwtvocFZuU1taYezRymzvBZLrldkbICauhkSsHRwazoFoHJepPRC6Q29CN67WEfGRnRBhURM55BobSdxDlos3bzBjeAVgNZ2oo3W_D3k7qndME5v-P8RlGiMBYYOnHXTBW6lDhznLqy1qBTvRiOl1ikEZMFhPPlvc7CdrjXu9iJcjMbQnUP7KNOmkd3ipkG-p0/https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-regext-secure-authinfo-transfer-03%23section-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
> <https://secure-web.cisco.com/1fDC9N8uU6IPT_EF_7uAAVznUD8SeRiQfEspxbZ7K462x3pUcWXANQLl65DhwDm42Tnzst5sWdgJoVVwVaV1nwfEeLIyJ84n7hf0no3KNDmr2FSnfWqoUXwz7CcJKtVHxVeqCPxPrSAtXLVXqMNxyXq43d3XwpQocebl_3CR6r5qfOs6MYXycUvkWQIrUmoVDWKVBZrlAb2X9LGj-xHMMzptz9EHkzj73LblhoBU1TlzhwfEE7NZvB629ZmMF3aDzE-uj8tBvwsCTWyPC2vNVAorS3uKjIAJx0Y5lZgMXKV4/https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-regext-unhandled-namespaces-03%23section-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://secure-web.cisco.com/1Itq6Iu9Ce3lRF7_uiaHCucQVya2sg9-ft8Yg6yP0k3-0H1E8iw8Qqmyc31A7wscCr2uY1m-HhwBC5gY9_wQA6GqtaTqqrdWBFlmQbZhx9-EAmD7vYlV5mMkhJwoXIx70fLtS0dHUPlEdGFEPd9k-L5bRtUyRqdp3eV4jrrKZmQfZ4WjKC2Jy8jEh_kWBRrtR_-uXI1DFtzyn2ZmPQoNRfbEYvr-RfL16Esuwi_20hlASRB2BwJchik4sDeE8emLBSZjWDtN4v-s8j7MFzMbKhg/http%3A%2F%2Fverisigninc.com%2F>
>
>
>
> *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
>


-- 
SY, Dmitry Belyavsky