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

Dmitry Belyavsky <beldmit@gmail.com> Thu, 08 October 2020 14:45 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 CC60C3A0E01 for <regext@ietfa.amsl.com>; Thu, 8 Oct 2020 07:45: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 J-JqUwwxWW7r for <regext@ietfa.amsl.com>; Thu, 8 Oct 2020 07:45:22 -0700 (PDT)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (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 593003A09EC for <regext@ietf.org>; Thu, 8 Oct 2020 07:45:22 -0700 (PDT)
Received: by mail-ed1-x535.google.com with SMTP id b12so6083366edz.11 for <regext@ietf.org>; Thu, 08 Oct 2020 07:45:22 -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=vggZKpRvdmSSKWQO/pzw/6pMw552TRt9pHSHBIn9wbM=; b=eFx/7DZV1KXJrifuJZ3H9wD+ON2x5a2MnjcuKEUTCUhe4JAHO8lSGG59KEck5VRPwF 0mz3sfAqcXzkgOnDapsDncnbC48g4P7imDj1pcqgkpeB630qzaU5geuPSzOcGMOjoqju hCVIfRvhPldY1TeeiUboVKYBOFCJIhiwQXaDyAQDkrg08CdB8I7LuuZ6xVrXiD1d8Ylj jV5TbtUe1DE0AdJ28PhZXe6Pw44nFx2d6ug1AKg3GOJInX2Aw4N8vp8weuEUg7hSDNgY hg1Uv2p6lID8GtWAA1lGTfJ2j76cm1ub0RYPnebl/84H7EQK1Zsxd5P4SLWMX+eLj07E 79Kw==
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=vggZKpRvdmSSKWQO/pzw/6pMw552TRt9pHSHBIn9wbM=; b=WFoO0kpcHCR3GVc+fsn+XruiClBX2IJf1M4KuqoTbzFGD1UdwdrWSnxkYHKuQvP++b soQIug4BFKENXp1VKhb4k+g3vxVmdLJxwoqezFfUvXUBKr/SFZe29N1xDWimJp3uruHF AOvOgakzOM8vlUAXSnDYA4+TcR8dAy9Auvb97clNzqP+ZRXUhkYQUn1aFGiPrRgrpL6i 3I1PgK+1XQwnFe5uqk83VnDrjLifDI1r3Tn4rPFw/9/G+updhiRApT9SEqradQ/LSP1s nWlMdVBuzdimi6KoaEe999Nu+pjN+dDZFrBwmWbntWLCzp8U2v48PQmuI7Qh5aIC4msC 0JmQ==
X-Gm-Message-State: AOAM532Ch3omyapDUY7TzpcHMxUY97n2DSudhSJCr3G6Aw6BQfh+Ynr9 vAC+d1BOJPFDBHa4G6F4/fSDbp4ODCxbWlYBwDxafCSdlAM=
X-Google-Smtp-Source: ABdhPJyEshC8/Akrnp+ehDNbCArnJ6Lsi1ylXZdMJ6f7tduRENHxfh0qA7J8eeZH+jfshiiJ4bOJkeQ4a+scQP7K0kg=
X-Received: by 2002:aa7:d783:: with SMTP id s3mr9597207edq.214.1602168320541; Thu, 08 Oct 2020 07:45:20 -0700 (PDT)
MIME-Version: 1.0
References: <160207715398.14301.11809257569714930902@ietfa.amsl.com> <CADqLbzJP0igLXu1ZOt2ShNsoVz5RQ-a6Vyrt4hp9tJAmoKHE+g@mail.gmail.com> <5f28bdeb6cbe4d3fa9bf9b969b17025d@verisign.com> <CADqLbzJFN634Gs7mH2=Ukygw7CXbuaCWKn8d4fyWdh+CyEh93w@mail.gmail.com> <F49F50D1-BF92-433C-9958-0B975455F7C6@verisign.com>
In-Reply-To: <F49F50D1-BF92-433C-9958-0B975455F7C6@verisign.com>
From: Dmitry Belyavsky <beldmit@gmail.com>
Date: Thu, 8 Oct 2020 17:45:08 +0300
Message-ID: <CADqLbzJn+RLtbA-F=LZdWxNBZhz00D99gK4CN3LzOO8NyhDUdw@mail.gmail.com>
To: "Gould, James" <jgould@verisign.com>
Cc: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "masha@cctld.ru" <masha@cctld.ru>, "regext@ietf.org" <regext@ietf.org>
Content-Type: multipart/related; boundary="0000000000009e570405b129e191"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/Qza-QUUrazrMiD-JTKK8EvIF9O4>
Subject: Re: [regext] Fwd: New Version Notification for draft-belyavskiy-epp-eai-00.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: Thu, 08 Oct 2020 14:45:25 -0000

Dear James and Scott,

Many thanks for your clarifications and example!
Will soon return with an updated draft!

On Thu, Oct 8, 2020 at 5:37 PM Gould, James <jgould@verisign.com> wrote:

> An extension was used to override the type of the RFC 5730 password and
> new password element in the Login Security Extension (
> https://tools.ietf.org/html/rfc8807).  In the case of the Login Security
> Extension, a pre-defined placeholder value is used in the RFC 5730 password
> or new password elements to point to the use of the corresponding elements
> in the extension.
>
>
>
> What is the issue with the eppcom:minTokenType for an internationalized
> email address, which defines a minimum length of one and uses the XML
> schema “token” type, and which extends from the XML schema
> “normalizedString”?  The only difference between the “token” and the
> proposed “normalizedString” is the collapsing of whitespace.  Is the
> collapsing of whitespace (#x20 (space), #x9 (tab), #xA (linefeed),
> or #xD(carriage return)) an issue for internationalized email addresses?
>
>
>
> --
>
>
>
> 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: *Thursday, October 8, 2020 at 10:21 AM
> *To: *"Hollenbeck, Scott" <shollenbeck@verisign.com>
> *Cc: *"masha@cctld.ru" <masha@cctld.ru>ru>, "regext@ietf.org" <
> regext@ietf.org>
> *Subject: *[EXTERNAL] Re: [regext] Fwd: New Version Notification for
> draft-belyavskiy-epp-eai-00.txt
>
>
>
> Dear Scott,
>
>
>
> Many thanks for your response!
>
>
>
> I'm sorry, I don't feel the difference between this case and a similar
> update of X.509 profile by RFC 8399.
>
>
>
> And, as the email field is mandatory on creating the contact, I don't
> think that the extension is the best way.
>
>
>
> On Thu, Oct 8, 2020 at 5:13 PM Hollenbeck, Scott <shollenbeck@verisign.com>
> wrote:
>
> Thanks for the note, Dmitry. I get what you’re trying to do, but I don’t
> think we can update Standard 69 (the set of EPP RFCs) this way. I’m not
> aware of any RFCs that expressly prohibit such things, but it’s a topic
> that the IESG has debated multiple times over the years and there might not
> be support for doing it his way now. A safer path would be to develop an
> extension using one of the techniques described in RFC 3735, “Guidelines
> for Extending the Extensible Provisioning Protocol”.
>
>
>
> Scott
>
>
>
> *From:* regext <regext-bounces@ietf.org> *On Behalf Of *Dmitry Belyavsky
> *Sent:* Wednesday, October 7, 2020 9:28 AM
> *To:* regext@ietf.org
> *Cc:* marabox <masha@cctld.ru>
> *Subject:* [EXTERNAL] [regext] Fwd: New Version Notification for
> draft-belyavskiy-epp-eai-00.txt
>
>
>
> Dear colleagues,
>
> This is an initial version of the IETF draft allowing usage of
> Internationalized Email Addresses in the EPP protocol.
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Wed, Oct 7, 2020 at 4:25 PM
> Subject: New Version Notification for draft-belyavskiy-epp-eai-00.txt
> To: Dmitry Belyavskiy <beldmit@gmail.com>
>
>
>
>
> A new version of I-D, draft-belyavskiy-epp-eai-00.txt
> has been successfully submitted by Dmitry Belyavskiy and posted to the
> IETF repository.
>
> Name:           draft-belyavskiy-epp-eai
> Revision:       00
> Title:          Use of Internationalized Email Addresses in EPP protocol
> Document date:  2020-10-07
> Group:          Individual Submission
> Pages:          4
> URL:            https://www.ietf.org/id/draft-belyavskiy-epp-eai-00.txt
> <https://secure-web.cisco.com/1LkyicX_gPmVOFcqhopUmVBWNTNu8kNZjDBEJQvuOubNy547f4jeqX_rzGbyYv6ETENBk4XhC6Pf1HYfuQdaDUGDzadgReCVZHuAE3qDlDJ-ztd4b8LLqBg3K_QCXVYdim6g241oyclQbCWdzjcjdB0qsqZhAj7W3T-uShNPnveo9pis0PgzAehHj4M_Pa1E2SJthPbd5fydZFjMvT1MZ7uJOuf11g-OM7uxR0y4HKXBBcQmHQeYPly9f0fMNpUmxbzdghKVzx472b1k082jKppl8gS440Z2FgZc1DYcPwzw/https%3A%2F%2Fwww.ietf.org%2Fid%2Fdraft-belyavskiy-epp-eai-00.txt>
> Status:         https://datatracker.ietf.org/doc/draft-belyavskiy-epp-eai/
> <https://secure-web.cisco.com/1iH-jWELClftnGP8aH6xLx2NYPu3jsbvha_VBM_4gIYI_a8gCvX2XYik-58d-Us1TIPSkJ-7MhuKX4fkdG4KZTg6OnUZ-zO05p4r4nD5I65TQfgse3foF4wNxX8RmIRAC7QJJZfmvtRF40KsstlpsRnvYB6kI9UZHGMck8TJxG4ie2i_kJkLDrxEG4bX4IwyU_uaYJ6NcQKwea85dIKFVXK7crG9xK8yBLnaj7wswNB70e2H_7SYNN1Iye6vp1u3iq54v8LaLW08h06WUNV5rxQ/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-belyavskiy-epp-eai%2F>
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-belyavskiy-epp-eai
> <https://secure-web.cisco.com/1R1veyqLSTSFJHBa1BOcXLht2lZlaD_b-6Bcn_diis5-1NVr8a1BzS7TR8Hx0DncgMGnCAxrF7tXkKyNq8gqWnEUxjk2pAF9gfoOnpD39Aa3C81DT4CHwuBnuZx9GisUlHkmqsxp2MkhJKm-1oyTZGF9pTmhivYFGZdBjn9pRiTMFYfCDrvh6aE1Q1_ZBmI3o6O5Y68lqVSGq23CffeKWDO6wXDh-43gZ9Uri_2xEmQbOzBdfrrvfdLy7dRo0XEaaG_Ixs6XMLnC9OQSoppMSbw/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-belyavskiy-epp-eai>
> Htmlized:       https://tools.ietf.org/html/draft-belyavskiy-epp-eai-00
> <https://secure-web.cisco.com/1aPLpPIJlvKOGrv9LEQTzgEaIIt-akmzF6wRR_zggj-AfW5Y1tzou50A5DCNMH-Fdh2GPXgvVE2JvtV-6esKg-9tT0f-1iQykAZFrmwEYBLzRgmzI7XbCUcbjoMuV7BsJlwNBzH4j50M5pdZJa0HXNlXozZxgd9oeWyq-yPwoq-mg4mGEDYXJ_aS8sTyd0VPYw1_jJV0RlvffC9RLZ1t6WSpFIlP1IW3dEqhkFF0Lj3CEhPPJAYe47DoLsUCcnbcz-Gc-1tv63IN6ljQrXIXITIYo_HnS9RwKFZQ8lcQ9XDc/https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-belyavskiy-epp-eai-00>
>
>
> Abstract:
>    This document permits usage of Internationalized Email Addresses in
>    the EPP protocol.
>
>    TO BE REMOVED on turning to RFC: The document is edited in the
>    dedicated github repo [1].  Please send your submissions via GitHub.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org
> <http://secure-web.cisco.com/1Uf4zmBFe46PVm16LpIWeYo6zFDeCMc2krmNCh3enAUGvptve1fyz-b7Ajy5sgY3pxCRTvrr8PSkB8TxBU26-mOuzr751etNgYOdmrmv7bGGtkDxLWyYJufulJaqZILFmfGSMMkAWh07W_JGwcxgQ-FwE5tyXQ_H3Ka6VoeG8BUjpzT77mFSpvxlgcu4il6bYriCZWRrgvLZTH87sUfS2zQ2qIuM-6BHE6xtTxk0J7nbjI8KZUUu9vTJAvq6YnoTNsdf8qPm9KHQ3I-MktA3ikpnptxlzHINmJAIJJPD5L2E/http%3A%2F%2Ftools.ietf.org>
> .
>
> The IETF Secretariat
>
>
>
>
> --
>
> SY, Dmitry Belyavsky
>
>
>
>
> --
>
> SY, Dmitry Belyavsky
>


-- 
SY, Dmitry Belyavsky