IETF Logo Mail Archive

Re: [regext] EPP evolution and the REGEXT charter

"Gould, James" <jgould@verisign.com> Thu, 21 March 2024 23:49 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 46B6FC18DB87 for <regext@ietfa.amsl.com>; Thu, 21 Mar 2024 16:49:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LL3Y29CFuv54 for <regext@ietfa.amsl.com>; Thu, 21 Mar 2024 16:49:21 -0700 (PDT)
Received: from mail6.verisign.com (mail6.verisign.com [69.58.187.32]) (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 71621C18DB9B for <regext@ietf.org>; Thu, 21 Mar 2024 16:49:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=17754; q=dns/txt; s=VRSN; t=1711064961; h=from:to:date:message-id:mime-version:subject; bh=iBNbmfo/a0sJQmLcQrXrheACisynQmTMnF18F0PJetE=; b=BMxAqAiRvlWaGibBg0yxDEAnJ01QhQX8L0f6GpsgLA1qZXXPADd1wwga +vXM0mRlLmhXP1D/lOivdBoVJFX7+fyRy1PVvyPqPZWgBURgATpkftJFG bmofCE4X2fMJ8WhlGiJGkpBiXZvvVvcZiwvrRMf3gpKEHq1kMChihnAFP G1cMwi2FfVehmqTV0CaYbmSjUhGKeeqTF7Nv8+X+7vQ0VhKSCrIjNd3A7 HR9t4ZVkSuw68YHt8zSy2V6vnkOeRTxHhUh16YYfBi8vztrSXZnrbfGjf wS0XF2KcSiwhLFyVq4yCN01i85x15WWey9IfwkrbnxaYSji7MCmMuQHIw Q==;
X-CSE-ConnectionGUID: PgLJ4k8lT628NXi+K6HTgw==
X-CSE-MsgGUID: mwrLcyzyQvu+fJr8wjMv7Q==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:QSZNqqsTjuulIGPtRh4DLV2T9+fnVLxfMUV32f8akzHdYApBs4E2e luraxnfZ67dN2L1esc2NtqGQXl278TSm4RlTFFoqyA0FnwaopPPCYiSJRusYXrNJMDJEBxst s5AO4idIZw/FXWMr0rxa7K/83cniPyGGLCnA7abN0idKeMFpAIJ0HqPzMZl29c26TTAPz6wh D/SnyH+EAL/0jN4Pz0dsqnY9kti5a2s5G9B5wZiOqARslGPm3BFUMtPdKq8ESD1E9JedgKYq 0Qv75nipz+EoE19Yj+BuuymGqHfaueKZWBislIPBu76xEAE/3RuukoCHKJ0QV9NjDmUlMxGx txItJihIS8kJaSkdN41CnG0KAkge/UZkFP7CSLn65DLlBefKyCEL8hGVynaA6VJoo6bPkkTr ZT0GBhVBjifiuS/xq6MS+UErqzP++GyYevzElk5pd3oJa5OraLrGs0m1vcBtNsEvf2iKN6FD yYvQWE2MEmfOU0n1mA/U/rSlM/w7pX2W2MA9ALN/cLb6UCLpOB6+OCF3NY45rVm7Cia96qVj juuwoj3Pv0VHOSQ7RjZ8SKourGVzQXLWcExSp2E+eE/1TV/xkRLYPEXfXGBh6CGrGOOA4gZN UcT4DJopKR06lawSJ/2WBjQTHys50ZaAoULVbRns0fRm8I44C7AboQAZjxOb8EiuOcoSCYrz V6GmZXiAjkHXLi9EyPMq+7M8mPa1S49KHAYQSQVXxo8/cSgrqMp3g3Na8g8Kfvg5jHyMXSqq 9yQlwA7jrwJkcMNkbqm+VTGhTH5+sDSTwIzoAPTdm6g5xlyIo+oe4Lu7kLUhd5aIYmUXkWpv XUYlY6Z9u9mMH2WvCaXRrwSGry5v6zAKyPGx1tuBNwr8HKn4Xj6O55K+zc4L0BsWioZRQLUj IbokVs5zPdu0LGCNMebv6rZ5xwW8JXd
IronPort-HdrOrdr: A9a23:tEdDLaH6yZ3yyr2lpLqE2MeALOsnbusQ8zAXPhhKOH9om7+j5q KTdZUgpGbJYVkqOU3I9errBEDiewKlyXcW2+ks1N6ZNWGMhILCFu1fBP7ZrQEIbBeQygcy78 pdmuNFebjN5BBB/KLHCEPTKadG/DCoytHPudvj
X-Talos-CUID: 9a23:vByvg2yWraQ/Hz7RCdTLBgUsFeQHLn6NyEuOeR+eOWcqa+O1dVCPrfY=
X-Talos-MUID: 9a23:ICFH/Ah6DQE02hkvgBk0wcMpMdhyx6+/GlE0j4hFteueZTNyHinCtWHi
X-IronPort-AV: E=Sophos;i="6.07,144,1708387200"; d="png'150?scan'150,208,217,150";a="29951078"
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.2507.37; Thu, 21 Mar 2024 19:49:19 -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.2507.037; Thu, 21 Mar 2024 19:49:19 -0400
From: "Gould, James" <jgould@verisign.com>
To: "maarten.wullink=40sidn.nl@dmarc.ietf.org" <maarten.wullink=40sidn.nl@dmarc.ietf.org>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] [regext] EPP evolution and the REGEXT charter
Thread-Index: AQHae+pkvE9/OUMhCECT40eBRj2oYA==
Date: Thu, 21 Mar 2024 23:49:19 +0000
Message-ID: <8CA69CC0-D08D-420C-83C7-4A5B03D698B8@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.82.24021116
x-originating-ip: [10.170.148.18]
Content-Type: multipart/related; boundary="_004_8CA69CC0D08D420C83C74A5B03D698B8verisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/repoY1Y1QzUBf41OKimcOV38WSc>
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:49:27 -0000

Maarten,

The charter refers to EPP extensions, which transports is a form of an EPP extension.  RFC 5730 defines the extension points for EPP and includes support for extending the transports based on Section 2.1 “Transport Mapping Considerations”.  I don’t believe that there is a need to revise the REGEXT charter to support the additional of new EPP transports.

Thanks,

--

JG

[cid87442*image001.png@01D960C5.C631DA40]

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/>

From: regext <regext-bounces@ietf.org> on behalf of Maarten Wullink <maarten.wullink=40sidn.nl@dmarc.ietf.org>
Date: Thursday, March 21, 2024 at 7:37 PM
To: "regext@ietf.org" <regext@ietf.org>
Subject: [EXTERNAL] [regext] EPP evolution and the REGEXT charter


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 all,

Is the charter for the REGEXT WG limited to working on EPP XML extensions only?

If so, what is then required for allowing the different new transport proposals to continue? A new transport is clearly something different.

Do we need to expand the current charter and maybe change the WG name, if possible?

Or do we need to create a new WG for work related to EPP evolution such as new transport protocols?

Best,
Maarten

v2.23.0 | Report a Bug | By Email