IETF Logo Mail Archive

Re: [regext] EPP evolution and the REGEXT charter

"Hollenbeck, Scott" <shollenbeck@verisign.com> Mon, 25 March 2024 12:32 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 79B9CC14F698 for <regext@ietfa.amsl.com>; Mon, 25 Mar 2024 05:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_BLOCKED=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_BLOCKED=0.001, 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 6ic8okgW_Z-G for <regext@ietfa.amsl.com>; Mon, 25 Mar 2024 05:32:19 -0700 (PDT)
Received: from mail3.verisign.com (mail3.verisign.com [72.13.63.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 68F34C14F685 for <regext@ietf.org>; Mon, 25 Mar 2024 05:32:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=2284; q=dns/txt; s=VRSN; t=1711369939; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=guke6OvZ3j7Eu9izsT1/GqFRwIfjg6V9skZNXIvzWIQ=; b=QuJEaxt1tIaZLvOVxIlPlSevMRIxdReqg57fYg8WRWTukgdSzEH6T7QL UF4LXI6Je6LBB2c1WkFT4bBg+4wcJmYhFffJ6cTzYT7YSS1lRZvgzVp8V BzQaCm/Zp+ogz/mpopESChOcnWGimLN+hgh9ChLNBwwnoNNcSvN5omf9M xS/xehhf7FK42VbAU/xBnskWiFnuzxTSZnySygtOfQ4x6kxx2wNX8dF2w OBjxTGkrWwygg3eETIDLH5QEAPoVDkG9BziXoY2B0A6dnmD4MQsn4VhiB 8eCdqA8mnEOvN524qZgyRaxN1rr+NutA+cRmw+JSkQsgx94qNtpDsz5A8 g==;
X-CSE-ConnectionGUID: KIAJ5GOlQ/SG0JYZBTgQzg==
X-CSE-MsgGUID: koGVAkNhRaytmbMibyzvOQ==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:m3Yd7KskQpb8bqSbIK4H6XMRfOfnVH1fMUV32f8akzHdYApBsoF/q tZmKTuFO/uDNzHyf9lwaoux908Pu57VydEwHFFtqXtjRS4X9ZOVVN+UEBz9bniYRiHhoOCLz O1FM4Wdc5pkJpP4jk3wWlQ0hSAkjclkfpKlVaicfHg3HFc4IMsYoUoLs/YjhYJ1isSODQqIu Nfjy+XSI1bNNwRcawr40Ird7ksw1BjOkGlA5ABmPqoW5Aa2e0Q9V/rzG4ngdxMUfaEJRoZWd 86bpJml82XQ+QsaC9/Nut4XpWVTH9Y+lSDX4pZnc/DKbipq/0Te4Y5iXBYoUnq7vh3S9zxH4 I4U6cHvE1dB0prkw4zxWzEAe813FfMepO+feRBTu+TLp6HNWyOEL/mDkCjalGDXkwp6KTgmy BAWFNwCRjOirsDr75W/c65XqZwBHfvBAIwmqH41mFk1Dd5+KXzCa4/ww4Zn+hoA3poIA/3Zf dJfYDYpcg7bZVtEPVJ/5JAWxb/u3yakNWQF8xTJ9MLb4ECKpOB1+KPtN97Rd9qASM5WtliVv GPd/mv/RBodMbRzzBLeqCn837eTxEsXXqoRE5KG3/1MgGea13AWAjgXX0qpv96A3xvWt9V3b hZ8FjAVha07/Va3Q9+7QAC8pH+CvTYHWtZWVes+gCmEzKbFywaJHC4ZVVZpbdU8tchwQTsk2 EWEk9TBBD1z9raTUzSc6t+8rzqpNSkNNkcLfy4CCw0I/7HLuow8gwLTZtduDKDzicf6cQwc2 BiAti5nmLMenZZRkr6l5xbCginprJ+PRBQzv0PJRHmjqAh+YeZJerCV1LQS1t4YRK7xc7VLl CFsdxS2hAzWMaywqQ==
IronPort-HdrOrdr: A9a23:kYb+EahBql8jhSfjbXihB1xPynBQXgcji2hC6mlwRA09TyX+rb HKoB17726XtN9/YhEdcLy7VpVoIkmyyXcd2+B4AV7IZniEhILHFuBfxLqn7THmFzb36+JRkY xxGpITNPTASXx3l9zz7gX9MdoxqePszImYwcPT1W1kQw0vUbxn9AsRMGumO1d7XxZLHqA0E5 eg5s5KzgDKRUgq
X-Talos-CUID: 9a23:oevGSW1Owno+WRI1JMpBMLxfOeEMUCDy63PpZHSXUURYepepRmaC9/Yx
X-Talos-MUID: 9a23:Htx00Ao1RUjjnb+RXhwezzJlG/lB4IKuMkkcjZAMnsiOJD5uHA7I2Q==
X-IronPort-AV: E=Sophos;i="6.07,153,1708387200"; d="scan'208";a="32381041"
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.2507.37; Mon, 25 Mar 2024 08:32:17 -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; Mon, 25 Mar 2024 08:32:17 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "maarten.wullink@sidn.nl" <maarten.wullink@sidn.nl>, "Gould, James" <jgould@verisign.com>
CC: "andy@hxr.us" <andy@hxr.us>, "mario.loffredo@iit.cnr.it" <mario.loffredo@iit.cnr.it>, "jasdips@arin.net" <jasdips@arin.net>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [regext] EPP evolution and the REGEXT charter
Thread-Index: AQHafPeDN5kO3vxG4E+7MlHcmEpsiLFIZV0Q
Date: Mon, 25 Mar 2024 12:32:17 +0000
Message-ID: <b4c2f43f31e64126b462c2a3be569a3e@verisign.com>
References: <8CA69CC0-D08D-420C-83C7-4A5B03D698B8@verisign.com> <a7b73d2bb3ec49b586230d8709424170@verisign.com> <LV3PR15MB6453A840D9C678809D94BB0EC9312@LV3PR15MB6453.namprd15.prod.outlook.com> <1f54547d-8fb1-4686-8a95-e9dcbe021d55@iit.cnr.it> <CAAQiQReqVY91FF2_r=0KfWKUzc5Nt4nBRvzaZO5ZxjWp4Oux4g@mail.gmail.com> <A7C9335D-F0E1-4F89-8C02-3D67359297EA@verisign.com> <CAAQiQRcpMFkcqWHCGn1LrAuRAGipWr3+7WiEUgqqnhtvhK2VsA@mail.gmail.com> <62742B79-3DA6-41CE-9F1B-0825686A5359@verisign.com> <3A9AA491-1CD1-45EA-B21B-4CF39D6F2E64@sidn.nl>
In-Reply-To: <3A9AA491-1CD1-45EA-B21B-4CF39D6F2E64@sidn.nl>
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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/Df5s3M6rwhQ8x5DvaHsU6jZ_bxk>
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: Mon, 25 Mar 2024 12:32:23 -0000

> -----Original Message-----
> From: Maarten Wullink <maarten.wullink@sidn.nl>
> Sent: Saturday, March 23, 2024 3:56 AM
> To: Gould, James <jgould@verisign.com>
> Cc: andy@hxr.us; mario.loffredo@iit.cnr.it; jasdips@arin.net; Hollenbeck,
> Scott <shollenbeck@verisign.com>; 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.
> 
> REPP is not meant to be a replacement for RFC5730. Version 01 uses a custom
> schema based on the RFC5730 schema, because that looked to be a cleaner
> way to do it.
> But we could change it so REPP uses the RFC5730 schema as in Version 00. In
> that case we can describe which XML elements and types are not reused by
> REPP.

[SAH] Modification of the schema is where we cross into "this isn't an extension" territory. Using the 5730 schema would eliminate that concern.

> I don’t see REPP therefore as a new protocol. it reuses almost all EPP
> datastructures and protocol commands. Commands are mapped to URLs and
> all extensions should still work
> 
> I believe the closest match for REPP is a transport mapping. A transport
> mapping doest have to use a obvious transport protocol such as tcp/quic it
> can also be an L7 layer protocol. Section 2.1 for instance gives the SMTP
> protocol as an example for a possible transport mapping.

[SAH] Here's a thought: could REPP build on the newly proposed HTTPS transport mapping and focus instead on the mapping of commands to URLs?

Scott

v2.23.0 | Report a Bug | By Email