IETF Logo Mail Archive

Re: [regext] EPP evolution and the REGEXT charter

Jim Reid <jim@rfc1035.com> Thu, 21 March 2024 23:52 UTC

Return-Path: <jim@rfc1035.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 8F5DEC14F710 for <regext@ietfa.amsl.com>; Thu, 21 Mar 2024 16:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
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 3I_jYj-1IKvq for <regext@ietfa.amsl.com>; Thu, 21 Mar 2024 16:52:29 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F2C6C14F5EC for <regext@ietf.org>; Thu, 21 Mar 2024 16:51:55 -0700 (PDT)
Received: from smtpclient.apple (dhcp-9b38.meeting.ietf.org [31.133.155.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 541AF2420E4A; Thu, 21 Mar 2024 23:51:52 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <8CA69CC0-D08D-420C-83C7-4A5B03D698B8@verisign.com>
Date: Thu, 21 Mar 2024 23:51:47 +0000
Cc: "regext@ietf.org" <regext@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2400A7CD-5DAE-4571-93F2-BA2072B35BB0@rfc1035.com>
References: <8CA69CC0-D08D-420C-83C7-4A5B03D698B8@verisign.com>
To: "Gould, James" <jgould=40verisign.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/9PqULE7s-vH-gPEMO9q2rdKwBNw>
Subject: Re: [regext] EPP evolution and the REGEXT charter
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, 21 Mar 2024 23:52:33 -0000


> On 21 Mar 2024, at 23:49, Gould, James <jgould=40verisign.com@dmarc.ietf.org> wrote:
> 
> I don’t believe that there is a need to revise the REGEXT charter to support the additional of new EPP transports. 

+1

v2.23.0 | Report a Bug | By Email