IETF Logo Mail Archive

Re: [regext] EPP evolution and the REGEXT charter

"Gould, James" <jgould@verisign.com> Fri, 22 March 2024 18:16 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 B6DDAC14F6F4 for <regext@ietfa.amsl.com>; Fri, 22 Mar 2024 11:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, 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 ZmSmfxQ2nCjt for <regext@ietfa.amsl.com>; Fri, 22 Mar 2024 11:16:18 -0700 (PDT)
Received: from mail2.verisign.com (mail2.verisign.com [72.13.63.31]) (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 2EF08C14F5FF for <regext@ietf.org>; Fri, 22 Mar 2024 11:16:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=18118; q=dns/txt; s=VRSN; t=1711131378; h=from:to:cc:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version:subject; bh=KbIbgjQabydot67l+nMOpTH4glwHkS50N4YY+e0AWWs=; b=KZypTuqi+fEvovJLEhz9X/WeVRp6VZsljdq5zNXMneYWMhZmZqOy2aVA TbzMQi96tnTVpx1ELx5VlV17ZyqdVafQwpgyMAC4aArstZG3XrfaPS/cz W1iiVRT4SPh/diSurSM/01/pckXV3KawcoXtU+dfKs3kkUjJ6zKr+/obG AX4HlHcEJHX9Us82xeXH2sA4BNW+lmhby7qzbRhBdPIBtbNp/3+1kIgqs zVLY9GCFTX3oNStxa9TphIjB4FZtgrL4nbtqmqLMP17ChgUETz6SwzAEy A7Rm0iJEwHxdIvvXiyyeb+DvGR0SWcyRLNYNcrYPxUq173huEYSWRqclZ g==;
X-CSE-ConnectionGUID: A3XsSXb7RTu9te+3Kh+gbQ==
X-CSE-MsgGUID: numMf/ncQaOMDtY/r75xJw==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:lHLAtqzOw3qut/2ZxMl6t+cbxyrEfRIJ4+MujC+fZmUNrF6WrkVWy jRMCDqPbP3YY2Dwfot+aIy39k5X6sXQmtI1GwppqS00HyNBpPSeCIXCJC8cHc8wwu7rFxs7s ppEOrEsCOhuExcwcz/0auCJQUFUjPzOHvykTrecZkidfCc8IA85kxVvhuUltYBhhNm9Emult Mj7yyHlEAbNNwVcbCRMtMpvlDs15K6u4GhC5ARkDRx2lAS2e0c9Xcp3yZ6ZciOQrrl8RoaSW +vFxbelyWLVlz9F5gSNy+uTnuUiG9Y+DCDW4pZkc/HKbitq/0Te5p0G2M80Mi+7vR3Sxowsl 48d3XCHYVxB0qXkwIzxWjEGS30uZfUuFLXveRBTuuTLp6HKnueFL1yDwyjaMKVBktubD12i+ tQxcwAWVSCJ2NiK3eOnR6o3pcRgI8PSadZ3VnFIlVk1DN4Me7aafIPn1YcBmik7gdpWW//SI dQDcjwpZxPFC/FNEg5PTsthx6Hx2yK5L20wRFG9/MLb50DRwwts1LTFLtfPe8eLSsMTlUGdz o7D1z+gW0lCb4zGodaD2nSxg8rB2iXwYYs1MZGkx7lw3wCD5HNGXXX6UnP++5FVkHWWUtRTO mQU6jBosLNa3EmiVNj6GRm/rnCesxIbc9tRD6sx7hvLy7a8ywSQHWQFViVpYcYnsokwSCBC/ lqAlsn1CDopr6CRTXOb9Z+PrD+0fy4RRUcYaCAJXRct4tT/rsc0lB2nczp4OKSviITqHzzgm 2nPtzYkwbASlosB0OOx51aexSy2vZ6PRQkwjunKYl+YAspCTNbNT+SVBZLztJ6s8K7xooG9g UU5
IronPort-HdrOrdr: A9a23:aHBNiar3X9dkbWArlp78ZG8aV5r2eYIsimQD101hICG9Ffbo8v xG/c5rtyMc5wxwZJhNo7690cq7Lk80nKQdibX5Vo3SPzUO1lHIEKhSqaXvxDH6EzDz+6p3xc 5bH5RWOZnVAUJhhcj3pCu1A78bquWvweSNif3Fx3lgCTt2bbpthj0VNi+AHlZoSBJ9CZ01KZ qZ6qN8zAadRQ==
X-Talos-CUID: 9a23:tcbDPWvBHxPFXu4hcBAedTcg6IsMKU3G90fafHWEFDd1Rf7Oal/T96ldxp8=
X-Talos-MUID: 9a23:di4BswS0P1ndtyFPRXTqmTRHOoBu6J2nL2UhjaRBoZbZJQ5vbmI=
X-IronPort-AV: E=Sophos;i="6.07,146,1708387200"; d="scan'208";a="31100381"
Received: from BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) 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; Fri, 22 Mar 2024 14:16:11 -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; Fri, 22 Mar 2024 14:16:11 -0400
From: "Gould, James" <jgould@verisign.com>
To: "andy@hxr.us" <andy@hxr.us>
CC: "mario.loffredo@iit.cnr.it" <mario.loffredo@iit.cnr.it>, "jasdips@arin.net" <jasdips@arin.net>, "Hollenbeck, Scott" <shollenbeck@verisign.com>, "maarten.wullink@sidn.nl" <maarten.wullink@sidn.nl>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] Re: Re: [regext] EPP evolution and the REGEXT charter
Thread-Index: AQHafFzGePKdkQQH3kC6BKa3pnDaU7FEEU4A
Date: Fri, 22 Mar 2024 18:16:11 +0000
Message-ID: <62742B79-3DA6-41CE-9F1B-0825686A5359@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>
In-Reply-To: <CAAQiQRcpMFkcqWHCGn1LrAuRAGipWr3+7WiEUgqqnhtvhK2VsA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.82.24021116
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E10667E67415D842A61844304388E09D@verisign.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/PQVa3c-wxAbc-XzKpnLeEVP1lfw>
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: Fri, 22 Mar 2024 18:16:22 -0000

Andy,

I'm not comparing EoH with REPP in any way since they're not competitive.  I view the EoH and EoQ drafts as a fully complaint transports with the extensibility defined in EPP RFC 5730, and therefore they're covered by the existing REGEXT charter.  REPP is a competitive draft to EPP itself since it replaces EPP RFC 5730.  REPP may reuse some aspects of EPP, but it is a replacement protocol.  Can you find language in the REGEXT charter that supports working on a replacement protocol to EPP?  

Thanks,

-- 

JG 



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




On 3/22/24, 9:28 AM, "Andrew Newton (andy)" <andy@hxr.us <mailto:andy@hxr.us>> wrote:


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. 


James,


If you wish to persist this line of reasoning whereby your drafts are
in charter but REPP is not due to an unorthodox definition of what is
and what is not an EPP extension, be aware that there is plenty of
text in the current RFCs that define more strictly the nature of an
EPP extension.


I also take a more inclusive view that REPP could be covered under the
latter section of the regext charter, specifically in that it defines
XML and/or JSON files, exchanged over HTTP, between registration
entities that need insertion in or extraction from EPP or RDAP.


-andy


On Fri, Mar 22, 2024 at 8:01 AM Gould, James <jgould@verisign.com <mailto:jgould@verisign.com>> wrote:
>
> Andy,
>
> It's not a question of fairness, but a question of what is defined in EPP RFC 5730 as it comes to extensibility of EPP. EPP RFC 5730 includes extensibility of transport, as reflected in Section 2.1.
>
> --
>
> JG
>
>
>
> James Gould
> Fellow Engineer
> jgould@Verisign.com <mailto:jgould@Verisign.com> <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgould@Verisign.com <mailto:jgould@Verisign.com>>
>
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
>
> Verisign.com <http://secure-web.cisco.com/1EhcGow1atX1jq2duBAhzSxt2PHDpLVZkGSj3d6FbCQz_EkI6jfEcLHAGIwfS9-36yDWM-kXX7w3IufIkmPPMH99L9ueNM8-wGSS60JT8YxeehBi4dgNuz1ZfCCxvkv6kzU7cqkY_eKPV-J8BJX--Ov8gYOEvL0COzw9U3jOx3pxZtgH2kQEUq2DFfHjuVDiZTGNhWsZXpkWv2WwZWon9yRy5WlpfP4xICVgMy3MJ8YXQVaTNwWtruiLj_gjlj7RvnnoZ8vCS7yLz79uktZKVUbgMbCNBhPcnrDDgZq-qhDQ/http%3A%2F%2Fverisigninc.com%2F> <http://secure-web.cisco.com/1EhcGow1atX1jq2duBAhzSxt2PHDpLVZkGSj3d6FbCQz_EkI6jfEcLHAGIwfS9-36yDWM-kXX7w3IufIkmPPMH99L9ueNM8-wGSS60JT8YxeehBi4dgNuz1ZfCCxvkv6kzU7cqkY_eKPV-J8BJX--Ov8gYOEvL0COzw9U3jOx3pxZtgH2kQEUq2DFfHjuVDiZTGNhWsZXpkWv2WwZWon9yRy5WlpfP4xICVgMy3MJ8YXQVaTNwWtruiLj_gjlj7RvnnoZ8vCS7yLz79uktZKVUbgMbCNBhPcnrDDgZq-qhDQ/http%3A%2F%2Fverisigninc.com%2F&gt;>
>
>
>
>
> On 3/22/24, 7:40 AM, "Andrew Newton (andy)" <andy@hxr.us <mailto:andy@hxr.us> <mailto:andy@hxr.us <mailto:andy@hxr.us>>> wrote:
>
>
> 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.
>
>
> I am against any logic that creates different gating factors for the
> different, competing solutions. Any contortion of the concept of an
> EPP "extension" that results in the favor of one set of drafts over
> the other is obviously unfair.
>
>
> -andy
>
>
> On Fri, Mar 22, 2024 at 5:33 AM Mario Loffredo
> <mario.loffredo=40iit.cnr.it@dmarc.ietf.org <mailto:40iit.cnr.it@dmarc.ietf.org> <mailto:40iit.cnr.it@dmarc.ietf.org <mailto:40iit.cnr.it@dmarc.ietf.org>>> wrote:
> >
> > Hi Jasdip,
> >
> >
> > IMO, REPP is not an "EPP extension" as defined by RFC5730. It provides neither just a switch of transport (like EoH and EoQ) nor an extension to EPP comands and responses.
> >
> > Instead, it presents a full revision of EPP that maps some EPP features onto HTTP features.
> >
> > Moreover, the current proposal is incompatible with some existing or future documents including extensions to EPP query commands (see Jody's question at last meeting about REPP compatibility with the Fee Extension).
> >
> > On the contrary, in the spirit of achieving a full compliance with RFC5730, .it is going to update its EPP implementation that has been working since 2009.
> >
> >
> > With regard to a possible RegExt rechartering, I also don't think we need it.
> >
> > RFC5730 already allows for implementing EPP over multiple transports. But it does even more, it makes some examples of possible alternatives to TCP.
> >
> > Therefore, leaving aside for the moment the debate about considering a new transport as an extension or not, it would be paradoxical if the protocol itself admitted other transports than TCP but it wouldn't be allowed to standardize them just like it has been done for TCP :-(
> >
> >
> > Best,
> >
> > Mario
> >
> >
> > Il 22/03/2024 01:12, Jasdip Singh ha scritto:
> >
> > Hi.
> >
> >
> >
> > Curious if the newly proposed “RESTful EPP” is considered a new protocol that is different from EPP, or is it an “extension” of EPP? (AFAICT, the former seems outside the current regext charter.)
> >
> >
> >
> > Thanks,
> >
> > Jasdip
> >
> >
> >
> > From: regext <regext-bounces@ietf.org <mailto:regext-bounces@ietf.org> <mailto:regext-bounces@ietf.org <mailto:regext-bounces@ietf.org>>> on behalf of Hollenbeck, Scott <shollenbeck=40verisign.com@dmarc.ietf.org <mailto:40verisign.com@dmarc.ietf.org> <mailto:40verisign.com@dmarc.ietf.org <mailto:40verisign.com@dmarc.ietf.org>>>
> > Date: Friday, March 22, 2024 at 9:56 AM
> > To: jgould=40verisign.com@dmarc.ietf.org <mailto:40verisign.com@dmarc.ietf.org> <mailto:40verisign.com@dmarc.ietf.org <mailto:40verisign.com@dmarc.ietf.org>> <jgould=40verisign.com@dmarc.ietf.org <mailto:40verisign.com@dmarc.ietf.org> <mailto:40verisign.com@dmarc.ietf.org <mailto:40verisign.com@dmarc.ietf.org>>>, maarten.wullink=40sidn.nl@dmarc.ietf.org <mailto:40sidn.nl@dmarc.ietf.org> <mailto:40sidn.nl@dmarc.ietf.org <mailto:40sidn.nl@dmarc.ietf.org>> <maarten.wullink=40sidn.nl@dmarc.ietf.org <mailto:40sidn.nl@dmarc.ietf.org> <mailto:40sidn.nl@dmarc.ietf.org <mailto:40sidn.nl@dmarc.ietf.org>>>, regext@ietf.org <mailto:regext@ietf.org> <mailto:regext@ietf.org <mailto:regext@ietf.org>> <regext@ietf.org <mailto:regext@ietf.org> <mailto:regext@ietf.org <mailto:regext@ietf.org>>>
> > Subject: Re: [regext] EPP evolution and the REGEXT charter
> >
> > From: regext <regext-bounces@ietf.org <mailto:regext-bounces@ietf.org> <mailto:regext-bounces@ietf.org <mailto: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 <mailto:40sidn.nl@dmarc.ietf.org> <mailto:40sidn.nl@dmarc.ietf.org <mailto:40sidn.nl@dmarc.ietf.org>>; regext@ietf.org <mailto:regext@ietf.org> <mailto:regext@ietf.org <mailto: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
> >
> >
> > _______________________________________________
> > regext mailing list
> > regext@ietf.org <mailto:regext@ietf.org> <mailto:regext@ietf.org <mailto:regext@ietf.org>>
> > https://secure-web.cisco.com/1AHUQzQat70wECC1RRIdlvWm6a3oTnGW5Afh7sXu_lR2HyyVuRXrR0lmpM5vRDM9NZ1Dn_mgZ408bGse4rFP87Bzb_P4WSnP4y1V8JWalFxOD1vLEeuJ1Y3bLE2YucTsVDuZy7fNqIxydwos1PgoTBfEpc1LUI_JJ6cqYs-K6QC5PxEtE56EclyqxE1FTVbAjx31gXz0BQ9ovBAu8ui6gxxeIfeA-2HvCvVZGFnGGezsTKMZjt7k8BQpo5Bt3pGIGKPdjpgyKoSOAsdqzefvxKMyiMYnOklpSHqLUv-A6U5E/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext <https://secure-web.cisco.com/1AHUQzQat70wECC1RRIdlvWm6a3oTnGW5Afh7sXu_lR2HyyVuRXrR0lmpM5vRDM9NZ1Dn_mgZ408bGse4rFP87Bzb_P4WSnP4y1V8JWalFxOD1vLEeuJ1Y3bLE2YucTsVDuZy7fNqIxydwos1PgoTBfEpc1LUI_JJ6cqYs-K6QC5PxEtE56EclyqxE1FTVbAjx31gXz0BQ9ovBAu8ui6gxxeIfeA-2HvCvVZGFnGGezsTKMZjt7k8BQpo5Bt3pGIGKPdjpgyKoSOAsdqzefvxKMyiMYnOklpSHqLUv-A6U5E/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext> <https://secure-web.cisco.com/1AHUQzQat70wECC1RRIdlvWm6a3oTnGW5Afh7sXu_lR2HyyVuRXrR0lmpM5vRDM9NZ1Dn_mgZ408bGse4rFP87Bzb_P4WSnP4y1V8JWalFxOD1vLEeuJ1Y3bLE2YucTsVDuZy7fNqIxydwos1PgoTBfEpc1LUI_JJ6cqYs-K6QC5PxEtE56EclyqxE1FTVbAjx31gXz0BQ9ovBAu8ui6gxxeIfeA-2HvCvVZGFnGGezsTKMZjt7k8BQpo5Bt3pGIGKPdjpgyKoSOAsdqzefvxKMyiMYnOklpSHqLUv-A6U5E/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext> <https://secure-web.cisco.com/1AHUQzQat70wECC1RRIdlvWm6a3oTnGW5Afh7sXu_lR2HyyVuRXrR0lmpM5vRDM9NZ1Dn_mgZ408bGse4rFP87Bzb_P4WSnP4y1V8JWalFxOD1vLEeuJ1Y3bLE2YucTsVDuZy7fNqIxydwos1PgoTBfEpc1LUI_JJ6cqYs-K6QC5PxEtE56EclyqxE1FTVbAjx31gXz0BQ9ovBAu8ui6gxxeIfeA-2HvCvVZGFnGGezsTKMZjt7k8BQpo5Bt3pGIGKPdjpgyKoSOAsdqzefvxKMyiMYnOklpSHqLUv-A6U5E/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext&gt;>
> >
> > --
> > Dott. Mario Loffredo
> > Senior Technologist
> > Technological Unit “Digital Innovation”
> > Institute of Informatics and Telematics (IIT)
> > National Research Council (CNR)
> > via G. Moruzzi 1, I-56124 PISA, Italy
> > Phone: +39.0503153497
> > Web: http://secure-web.cisco.com/18ZjMbqiWAB8oMpQC_ad8NBmCklQJicNAwYJBNem9hqNp-hnYYx8W-IsDgAj5YYIoPjNXKYbLHoHbLQOnuO1D-0pGn5efNkoPhRLt_PjSQXNKJ9YPI2SoqpNV8LDbUNZClA2VpmWyPUIdW_nuvzx27LwKDerZzNlwEI5hkIELgWMK7ygkBCN27fX6PEj5kXXpIVavRO8hg-l-9Z_37pAF4D9eHgyJrJQOePP7E_gUINDrBkBOiQqVcTBCovA44sUJbDOaqmIDAZ0QF7g5pHhMwd5gGlIZ1SThSB64HZfLxIs/http%3A%2F%2Fwww.iit.cnr.it%2Fmario.loffredo <http://secure-web.cisco.com/18ZjMbqiWAB8oMpQC_ad8NBmCklQJicNAwYJBNem9hqNp-hnYYx8W-IsDgAj5YYIoPjNXKYbLHoHbLQOnuO1D-0pGn5efNkoPhRLt_PjSQXNKJ9YPI2SoqpNV8LDbUNZClA2VpmWyPUIdW_nuvzx27LwKDerZzNlwEI5hkIELgWMK7ygkBCN27fX6PEj5kXXpIVavRO8hg-l-9Z_37pAF4D9eHgyJrJQOePP7E_gUINDrBkBOiQqVcTBCovA44sUJbDOaqmIDAZ0QF7g5pHhMwd5gGlIZ1SThSB64HZfLxIs/http%3A%2F%2Fwww.iit.cnr.it%2Fmario.loffredo> <http://secure-web.cisco.com/18ZjMbqiWAB8oMpQC_ad8NBmCklQJicNAwYJBNem9hqNp-hnYYx8W-IsDgAj5YYIoPjNXKYbLHoHbLQOnuO1D-0pGn5efNkoPhRLt_PjSQXNKJ9YPI2SoqpNV8LDbUNZClA2VpmWyPUIdW_nuvzx27LwKDerZzNlwEI5hkIELgWMK7ygkBCN27fX6PEj5kXXpIVavRO8hg-l-9Z_37pAF4D9eHgyJrJQOePP7E_gUINDrBkBOiQqVcTBCovA44sUJbDOaqmIDAZ0QF7g5pHhMwd5gGlIZ1SThSB64HZfLxIs/http%3A%2F%2Fwww.iit.cnr.it%2Fmario.loffredo> <http://secure-web.cisco.com/18ZjMbqiWAB8oMpQC_ad8NBmCklQJicNAwYJBNem9hqNp-hnYYx8W-IsDgAj5YYIoPjNXKYbLHoHbLQOnuO1D-0pGn5efNkoPhRLt_PjSQXNKJ9YPI2SoqpNV8LDbUNZClA2VpmWyPUIdW_nuvzx27LwKDerZzNlwEI5hkIELgWMK7ygkBCN27fX6PEj5kXXpIVavRO8hg-l-9Z_37pAF4D9eHgyJrJQOePP7E_gUINDrBkBOiQqVcTBCovA44sUJbDOaqmIDAZ0QF7g5pHhMwd5gGlIZ1SThSB64HZfLxIs/http%3A%2F%2Fwww.iit.cnr.it%2Fmario.loffredo&gt;>
> >
> > _______________________________________________
> > regext mailing list
> > regext@ietf.org <mailto:regext@ietf.org> <mailto:regext@ietf.org <mailto:regext@ietf.org>>
> > https://secure-web.cisco.com/1AHUQzQat70wECC1RRIdlvWm6a3oTnGW5Afh7sXu_lR2HyyVuRXrR0lmpM5vRDM9NZ1Dn_mgZ408bGse4rFP87Bzb_P4WSnP4y1V8JWalFxOD1vLEeuJ1Y3bLE2YucTsVDuZy7fNqIxydwos1PgoTBfEpc1LUI_JJ6cqYs-K6QC5PxEtE56EclyqxE1FTVbAjx31gXz0BQ9ovBAu8ui6gxxeIfeA-2HvCvVZGFnGGezsTKMZjt7k8BQpo5Bt3pGIGKPdjpgyKoSOAsdqzefvxKMyiMYnOklpSHqLUv-A6U5E/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext <https://secure-web.cisco.com/1AHUQzQat70wECC1RRIdlvWm6a3oTnGW5Afh7sXu_lR2HyyVuRXrR0lmpM5vRDM9NZ1Dn_mgZ408bGse4rFP87Bzb_P4WSnP4y1V8JWalFxOD1vLEeuJ1Y3bLE2YucTsVDuZy7fNqIxydwos1PgoTBfEpc1LUI_JJ6cqYs-K6QC5PxEtE56EclyqxE1FTVbAjx31gXz0BQ9ovBAu8ui6gxxeIfeA-2HvCvVZGFnGGezsTKMZjt7k8BQpo5Bt3pGIGKPdjpgyKoSOAsdqzefvxKMyiMYnOklpSHqLUv-A6U5E/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext> <https://secure-web.cisco.com/1AHUQzQat70wECC1RRIdlvWm6a3oTnGW5Afh7sXu_lR2HyyVuRXrR0lmpM5vRDM9NZ1Dn_mgZ408bGse4rFP87Bzb_P4WSnP4y1V8JWalFxOD1vLEeuJ1Y3bLE2YucTsVDuZy7fNqIxydwos1PgoTBfEpc1LUI_JJ6cqYs-K6QC5PxEtE56EclyqxE1FTVbAjx31gXz0BQ9ovBAu8ui6gxxeIfeA-2HvCvVZGFnGGezsTKMZjt7k8BQpo5Bt3pGIGKPdjpgyKoSOAsdqzefvxKMyiMYnOklpSHqLUv-A6U5E/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext> <https://secure-web.cisco.com/1AHUQzQat70wECC1RRIdlvWm6a3oTnGW5Afh7sXu_lR2HyyVuRXrR0lmpM5vRDM9NZ1Dn_mgZ408bGse4rFP87Bzb_P4WSnP4y1V8JWalFxOD1vLEeuJ1Y3bLE2YucTsVDuZy7fNqIxydwos1PgoTBfEpc1LUI_JJ6cqYs-K6QC5PxEtE56EclyqxE1FTVbAjx31gXz0BQ9ovBAu8ui6gxxeIfeA-2HvCvVZGFnGGezsTKMZjt7k8BQpo5Bt3pGIGKPdjpgyKoSOAsdqzefvxKMyiMYnOklpSHqLUv-A6U5E/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext&gt;>
>
>
>

v2.23.0 | Report a Bug | By Email