IETF Logo Mail Archive

Re: [regext] EPP evolution and the REGEXT charter

"Hollenbeck, Scott" <shollenbeck@verisign.com> Thu, 21 March 2024 23:56 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 C549EC14F6F0 for <regext@ietfa.amsl.com>; Thu, 21 Mar 2024 16:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.406
X-Spam-Level:
X-Spam-Status: No, score=-4.406 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_MED=-2.3, 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 gqvETp5y_doS for <regext@ietfa.amsl.com>; Thu, 21 Mar 2024 16:56:00 -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 B596FC14F698 for <regext@ietf.org>; Thu, 21 Mar 2024 16:56:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=7116; q=dns/txt; s=VRSN; t=1711065360; h=from:to:date:message-id:references:in-reply-to: mime-version:subject; bh=Yg5Hrk6Tf4vvCMmiEl2lb9zj3Vz6eMiql7v9devinNo=; b=d1hQaC5VfEmb7yZzbqg7F//ttgj5MNjMlNwmC6QBzihkklIy/ymVDa2Z quweoVK3s+jm88wHlMQZ//wYkylwsxaLh6ZswftxzwHPMFd+hZ1iVQj5m b6jQ4PhXIa4tPvno4gzd2NdCYX3da+7DCl/ExiK7JPTLABJ666ZAYMXQv Y5cVlNA+CCtpn+IWGHFgdXBuA859BH9JOFSU3GwmNM3mrGGmbqvRl7mhn ejHIC5JMIHYv7U766/iNYmEyq8A3/1RC03KzasEq4VTEPqXuVVrdbHPKM aoevyaU35jhtVon7stL+bMfZKDzqOvozBCi/1IsNlgjf1l1SNsY6RGF8m Q==;
X-CSE-ConnectionGUID: v2tsjAGiTyirUNaglO0fxw==
X-CSE-MsgGUID: 6rcQB7bIQ7uUGyp5cSjzQw==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:YetGKK9lEDMB44f4CE8rDrUDrn+TJUtcMsCJ2f8bNWPcYEJGY0x3z 2scCGiHO/+NYWSme4oka962p04DsMfcy9VnG1c6q3sxFiIbosf7XtnIdU2Y0wF+jCHgZBk+s 5hBMImowOQcFCK0SsKFa+C5xZVE/fjVAOK6UKidYnwZqTZMEE8JkQhkl/MynrlmiN24BxLlk d7pqqUzAnf8s9JPGjxSs/3rRC9H5qyo5GtD5AVmPpingXeF/5UrJMNHTU2OByagKmVkNrbSb /rOyri/4lTY838FYj9yuu+mGqGiaue60Tmm0hK6aYD76vRxjnVaPpIACRYpQRw/ZwOhxIktl YoX5fRcfi9yVkHEsLx1vxBwTXkibfUekFPNCSDXXce7lyUqf5ZwqhnH4Y5f0YAwo45K7W9yG fMwNmoRdRKqqOOK0bOhd89licAEdMf7I9ZK0p1g5Wmx4fcOa6rlGprsyO8AhXEujcdUBbDXa 4wHcyFpKh/HZnWjOH9OUNRnw7zu3ySkNWEIwL6WjfNfD2z71wx21LzgNtDYcd+iW8hPn12Zq WSA9GP8av0fHIfCl2ffqiL17gPJtX3hU7s4S7eZz6F3vXKC3jEYMx8EbETu9JFVjWb7AbqzM Xc8+CUpsKw+oRDzUNTnXga5r3jCtRkZc9ZVGvcxrgCA1qSS5ByWbkABRzdbdNEg8tArQTgr0 Fzcw4vyBDBp9ruRYX6Y/62f6zK/JSZTKnUNDQceQAQI88XLoYwvgFTIVNkLLUKuptfvH2jvx T2a9HF7nKsJy8sKzOCx+hbNmTT14IbTVQhz7QLSNo640j5EiEeeT9TAwTDmATxode51knHpU KA4pvWj
IronPort-HdrOrdr: A9a23:uYF3pKjydcLW9HQJpkxcVQDRHnBQXu8ji2hC6mlwRA09TyXBrb HKoB1p726RtN9xYgBZpTnuAsi9qB/nn6KdpLNhX4tKPzOWw1dATrsD0WKK+VSJcBEWtNQttp uIGJITNDSENzZHZLHBjzVQfexM/DDNytHOuQ6X9QYKcehFUdAY0ztE
X-Talos-CUID: 9a23:ImHF5GBLlYyqaBv6Ezc96FUWM+8kTmzc1kr2KkC8Lj5nWKLAHA==
X-Talos-MUID: 9a23:LH2eDQrkj+8yFiMoTHcez294P/5CvK6PMR8QrLoXo5SPDi5iAijI2Q==
X-IronPort-AV: E=Sophos;i="6.07,144,1708387200"; d="scan'208,217";a="35652081"
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) 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:55:58 -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.2507.037; Thu, 21 Mar 2024 19:55:58 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "jgould=40verisign.com@dmarc.ietf.org" <jgould=40verisign.com@dmarc.ietf.org>, "maarten.wullink=40sidn.nl@dmarc.ietf.org" <maarten.wullink=40sidn.nl@dmarc.ietf.org>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] Re: [regext] EPP evolution and the REGEXT charter
Thread-Index: AQHae+pkvE9/OUMhCECT40eBRj2oYLFC3j7w
Date: Thu, 21 Mar 2024 23:55:58 +0000
Message-ID: <a7b73d2bb3ec49b586230d8709424170@verisign.com>
References: <8CA69CC0-D08D-420C-83C7-4A5B03D698B8@verisign.com>
In-Reply-To: <8CA69CC0-D08D-420C-83C7-4A5B03D698B8@verisign.com>
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_a7b73d2bb3ec49b586230d8709424170verisigncom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/vPw9nTrkAZLLzsVlmYTHG_U5mb4>
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:56:04 -0000

From: regext <regext-bounces@ietf.org> On Behalf Of Gould, James
Sent: Thursday, March 21, 2024 7:49 PM
To: maarten.wullink=40sidn.nl@dmarc.ietf.org; regext@ietf.org
Subject: [EXTERNAL] Re: [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.

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.

[SAH] Agreed. New transport mappings are just another type of extension as long as they preserve the data model described in RFC 5730.



Scott

v2.23.0 | Report a Bug | By Email