Re: [regext] [Last-Call] [art] Artart last call review of draft-ietf-regext-epp-eai-12

"Gould, James" <jgould@verisign.com> Thu, 18 August 2022 12:31 UTC

Return-Path: <jgould@verisign.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 3E17FC14F733; Thu, 18 Aug 2022 05:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.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 xBKjBulycieg; Thu, 18 Aug 2022 05:31:23 -0700 (PDT)
Received: from mail1.verisign.com (mail1.verisign.com [72.13.63.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF248C14CE38; Thu, 18 Aug 2022 05:31:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=1166; q=dns/txt; s=VRSN; t=1660825883; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=p/qc/NK5q2rc0Hf1c1MgpHeK2l1hc3bQUPaMmVdbwNo=; b=KTjoywmA4B0NpRp+1yGSFJJWTt/y0I9NRnWukUQaPNVN7CVVGmd/kvl8 ZInZWhT0xLglx/mJXhSJkRGj7IwYwFh+WocQka+RfcKqX6jh9LytOEpzI rkor1rjH2DbYXlO1E8I5VeOfnoaL5NSsuc1tf9QxJkYG9M9UnAaf2HEGT TQxVoDA3rVm/PDXHmzUsBoOfYKDkvZZlfqU2rNSjNHA0KSPu/pDUYZID1 bSyPWnfbTudis9v7Dcd8co0xleSdexriQyE3pyZE7iX4zfJyehZlldTGh Bk1rz/1y3oLuNQlc2GUKXq/HwL0uC9McZuA+TkHCUzEqmqOQ2yrXo50vJ A==;
IronPort-Data: A9a23:nAi8qqvggGK/w2sWHL0oyCN9tefnVM9fMUV32f8akzHdYApBsoF/q tZmKTvQMvnbNmH1e4hzaIW3pkgGuJLWmINmTQVs/is0FytG9ZOVVN+UEBz9bniYRiHhoOCLz O1FM4Wdc5pkJpP4jk3wWlQ0hSAkjclkfpKlVKiefHgZqTZMEE8JkQhkl/MynrlmiN24BxLlk d7pqqUzAnf8s9JPGj9SuvnrRC9H5qyo4mtI5wxmP5ingXeF/5UrJMNHTU2OByagKmVkNrbSb /rOyri/4lTY838FYj9yuu+mGqGiaue60Tmm0hK6aYD76vRxjnVaPpIACRYpQRw/ZwOhxIktl YoX5fRcfi9yVkHEsLx1vxBwTXkibfUekFPNCSDXXce7lyUqf5ZwqhnH4Y5f0YAwo45K7W9yG fMwd2g0XgG6vdCN/I2RU7M8qOMvHu/2M9ZK0p1g5Wmx4fcOa6rlGprsyO8AhnEujcdUBbDXa 4wHcyFpKh/HZnWjOH9OUNRnw7zu3ySkNWEJwL6WjfNfD2z7zgN2zbzhGMTYYN2RRMpT2E2fo woq+kygUkpCZIHHmVJp9FqxveHLsS3jd7s+K+WAy9sppmCS/HwqXUh+uVyT5KPRZlSFc8pWJ WQM8yQyoKMyslemJvH3Uhm0pX+YlhEZUttUVeY97WmlyK3U5UOYC3QKZjxKa5ots8pebT4l0 UKNk4a1XSJiqryOSH2bsLyTqBu+PCEPJikDaDMKCwwf7LHLqZsvphPCUtglF7S65vX5Azj+3 3WLoTQwwq8egsMby+C25UiCjjut4JHNSiY06xnZGGW/4WtRYIe+e8mj4FzfxfdNMIjfSUOO1 FAelseT/PwmDJyRmmqKWuplNLDwt/CJMSf0gFNzEd8m7TvF03Gue8VZ+i1WJUp1PIADYzCBX aPIkQlL4sZMOna6NfUyeJyrTcEr1u3qEpLvTPaNKMRUeZ43fwiClM1zWXOtM6nWuBBEuckC1 V2zK65A0V5y5Xxb8QeL
IronPort-HdrOrdr: A9a23:RyaGMqk8DVrK2rBQUhVKOQ2WBvvpDfII3DAbv31ZSRFFG/Fwz/ re/sjy1XfP5Ar4wBkb6Ku90dq7MBbhHPlOkPMs1NaZLXHbUQSTTL2KgbGJ/9SCIVyCygc+79 YCT0EWMrSZZmSS5vyU3ODMKbcdKa68npxA692y854nd3APV0gp1XYfNu7QeHcGIjWuK6BJba ah2g==
X-IronPort-AV: E=Sophos;i="5.93,246,1654560000"; d="scan'208";a="18308508"
Received: from BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) by BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2375.31; Thu, 18 Aug 2022 08:31:15 -0400
Received: from BRN1WNEX01.vcorp.ad.vrsn.com ([10.173.153.48]) by BRN1WNEX01.vcorp.ad.vrsn.com ([10.173.153.48]) with mapi id 15.01.2375.031; Thu, 18 Aug 2022 08:31:15 -0400
From: "Gould, James" <jgould@verisign.com>
To: "paf@paftech.se" <paf@paftech.se>, "beldmit@gmail.com" <beldmit@gmail.com>
CC: "john-ietf@jck.com" <john-ietf@jck.com>, "jgould=40verisign.com@dmarc.ietf.org" <jgould=40verisign.com@dmarc.ietf.org>, "art@ietf.org" <art@ietf.org>, "draft-ietf-regext-epp-eai.all@ietf.org" <draft-ietf-regext-epp-eai.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "regext@ietf.org" <regext@ietf.org>, "i18ndir@ietf.org" <i18ndir@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Re: [Last-Call] [art] Artart last call review of draft-ietf-regext-epp-eai-12
Thread-Index: AQHYsv5oNC9lKCPT9UOqWqv1ocACWg==
Date: Thu, 18 Aug 2022 12:31:15 +0000
Message-ID: <BBBD2D00-31E1-41A2-A1FA-C336D333B0EA@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.62.22061100
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BB016ED05CAC774FA593D23B2612254F@verisign.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/rK4J76qTAMTG-OhGQRqH2wwByfw>
X-Mailman-Approved-At: Fri, 19 Aug 2022 11:38:33 -0700
Subject: Re: [regext] [Last-Call] [art] Artart last call review of draft-ietf-regext-epp-eai-12
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: Thu, 18 Aug 2022 12:31:28 -0000

Partrik,

By creating a standard around draft-ietf-regext-epp-eai it should decrease diversity of proprietary extensions with adding EAI support to EPP.  

-- 
 
JG



James Gould
Fellow Engineer
jgould@Verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgould@Verisign.com>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com <http://verisigninc.com/>

On 8/18/22, 8:24 AM, "Patrik Fältström" <paf@paftech.se> wrote:

    On 18 Aug 2022, at 14:14, Dmitry Belyavsky wrote:

    > If we try to provide uniform requirements, I'm not sure we should do it via preventing/limiting usage of non-ASCII email, speaking about this case.

    I am not saying we should prevent it. I want the specification of how to do it be so well defined that it does not increase the diversity.

       Patrik