IETF Logo Mail Archive

Re: [regext] Comments to the feedback about epp-over-http

"Hollenbeck, Scott" <shollenbeck@verisign.com> Thu, 31 March 2022 20:11 UTC

Return-Path: <shollenbeck@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 9D84B3A067A for <regext@ietfa.amsl.com>; Thu, 31 Mar 2022 13:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.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 JDW912YshtVE for <regext@ietfa.amsl.com>; Thu, 31 Mar 2022 13:11:03 -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 AD4D63A073D for <regext@ietf.org>; Thu, 31 Mar 2022 13:11:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=7078; q=dns/txt; s=VRSN; t=1648757465; h=from:to:cc:date:message-id:references:in-reply-to: mime-version:subject; bh=47WVeflaJXOZ2a+zX+NzEb6RgF04VXsGGQIlNoIWZh8=; b=Zk2HOkVBEOmygdM89hQbBB5odSro4zg1HYL76CTX7Pw7I4JBV2liPNxK xed1ZyXqlVIa23iHSYOQ+PDCu7TMFrJV9AGQ+/DxjT0rfS8BwjI06/13j Eoa/DkexcWX6ZrCZdgQKFDdj0K1m11jIq/xzRX4r8R3Dp23hodE6xKn+2 Qiuz4+9IodDqy/J7a+Ui9kubVD8PXXZBQv3shq1jDJzkj3tO0iLWViQEc 3/QLbuHEo8axdBc4HQYCmvSdn1tBDjr3UoCpVeKWDeSkRxNw+uQvAhg3P I3dTydir49VKaVb0zCF2DrbU5XFuM4tWTlAVfhlZiLfhEiWvej1aqeJJs Q==;
IronPort-Data: A9a23:5v2cj620ct9G5VmEQvbD5YZwkn2cJEfYwER7XKvMYLTBsI5bp2BSz mAaWjjVM/mKNjD0edlzatix8x4FvMXdmoUwSFY+qSg9HnlHl5HIVI+TRqvS04N+DSFioGZPt Zh2hgzodZhsJpPkS5PE3oHJ9RGQ74nRLlbHILOCa3gZqTNMEn9700o4wLdh2OaEvPDia++zk YKqyyHgEAL9s9JEGjp8B3Wr8U4HUFza4Vv0j3RmDRx5lAa2e0o9VfrzEZqMw07QGeG4KAIaq 9Hrl9lV9kuBl/skIo39zuajKiXmSJaKVeSFoiI+t6RPHnGuD8H9u0o2HKN0VKtZt9mGt/xTx vpNiISpcgQoIvychPw0TT1oShgraMWq+JefSZS+meap6RT5VVbcm68oEkoxJ5Ve8+oxH3tV8 7oTLzVlghKr3rrwme3gDLAx3YJ/faEHP6tG0p1k5SrZCvIiTJbJTq7JzcFVxjYrh89IW/3ZY qL1bBI2MEWaPUUXZz/7Dro83/+nvD7lLwcf61yfgKQV5jmJ1yZ+he2F3N39P4biqd9utkORv GPBuWD+DB8AOdCY4TuE7jSngPWJnD+TcIwIHbuz9+Vhh3WOwHZVAxoTPXOhrPa0mlKWWt9DJ QoT4CVGkEQp3EaxSIDiWRCo+CTBpQAGHd9RCKgw70eH0KyNpRiDHW5CRTlEADA7iPILqfUR/ gfht7vU6fZH6dV5lVr1Gm+okA6P
IronPort-HdrOrdr: A9a23:/UbNYqnBTIezWouZ7YiwG7VNVFPpDfIA3DAbv31ZSRFFG/Fwz/ re+Mjy1XfP5Ar5K0tQ/uxoWZPwOk80mqQU3WB8B92ftUzdyQ6VxeJZnPHfKl/bak7DH4dmvM 8KT0E9MqyTMbEQt6nHCXyDcurIt+PozEnHv4rjJjxWPGdXgulbnn5E4yigYzVLeDU=
X-IronPort-AV: E=Sophos; i="5.90,225,1643673600"; d="scan'208,217"; a="14926005"
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) 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.24; Thu, 31 Mar 2022 16:11:01 -0400
Received: from BRN1WNEX02.vcorp.ad.vrsn.com ([10.173.153.49]) by BRN1WNEX02.vcorp.ad.vrsn.com ([10.173.153.49]) with mapi id 15.01.2375.024; Thu, 31 Mar 2022 16:11:01 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "mario.loffredo@iit.cnr.it" <mario.loffredo@iit.cnr.it>, "francisco@unr.com" <francisco@unr.com>
CC: "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] Re: [regext] Comments to the feedback about epp-over-http
Thread-Index: AQHYRPYWlKlXjhloxEaCk5yYnLJ6tqzZsQsAgAAyKQCAAAUXgIAAET4AgAALVACAAAqcgIAAAeCAgAAchQD//76FEA==
Date: Thu, 31 Mar 2022 20:11:01 +0000
Message-ID: <82cb73a31c284345804c5db72738c298@verisign.com>
References: <0843A6FD-79B8-45B9-BE58-0BCED21C19B0@verisign.com> <1b87995b-700b-0d16-1241-c69cf142c3f7@iit.cnr.it> <8346151e-acc1-8e9a-f8ce-ac4d2f6a8dac@knipp.de> <759658bd-4781-a9cb-b7dd-88ba596fe2b0@iit.cnr.it> <58f622e5-1548-4894-a14c-c21125972a74@www.fastmail.com> <de81a129-68a4-8759-ee00-09ef2091ec22@iit.cnr.it> <6E923AA5-4027-4188-8DA3-6A93F39A3173@unr.com> <20457027-440b-02a5-82b8-3bef4e95819a@iit.cnr.it> <25E251B5-32D0-4E11-8383-F6CFFFD72CB8@unr.com> <c2bbe76c-4efd-4e92-3098-028291298001@iit.cnr.it>
In-Reply-To: <c2bbe76c-4efd-4e92-3098-028291298001@iit.cnr.it>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.170.148.18]
Content-Type: multipart/alternative; boundary="_000_82cb73a31c284345804c5db72738c298verisigncom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/W6GUSdS3o2GWQUI4B8DgzHqW2lQ>
Subject: Re: [regext] Comments to the feedback about epp-over-http
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, 31 Mar 2022 20:11:09 -0000


From: regext <regext-bounces@ietf.org> On Behalf Of Mario Loffredo
Sent: Thursday, March 31, 2022 4:03 PM
To: Francisco Obispo <francisco@unr.com>
Cc: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Comments to the feedback about epp-over-http



Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi Francisco,

appreciated but:

1) The ssl variables in NGINX are different.

2) Even supposing to extract CN or SAN, as it seems one should do in NGINX via a regular expression, it doesn't necessarily correspond to the registrar username to access the EPP server.

3) I repeat: why should I complicate a solution to come to another that I consider less efficient?

[SAH] For ease of interoperability with clients (registrars) who have to work with other servers (registries) that follow the specifications more closely.

Scott

v2.8.7 | Report a Bug | By Email