IETF Logo Mail Archive

Re: [regext] EPP Transport Service Discovery

"Hollenbeck, Scott" <shollenbeck@verisign.com> Wed, 20 March 2024 04:57 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 B8BCAC1654FE for <regext@ietfa.amsl.com>; Tue, 19 Mar 2024 21:57:00 -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, 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 OHLfZtFXX4Lq for <regext@ietfa.amsl.com>; Tue, 19 Mar 2024 21:56:56 -0700 (PDT)
Received: from mail4.verisign.com (mail4.verisign.com [69.58.187.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 9A3A9C151707 for <regext@ietf.org>; Tue, 19 Mar 2024 21:56:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=1216; q=dns/txt; s=VRSN; t=1710910616; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=pByJlW6W5B78sBS+i66WiL3YXVvf7Jo+eDtttmOzkUk=; b=JueShoKqHLwUCcqbFwG/e/k2ISfchq+0i9KeTMTe9lOu2m6M+ZrI6QKB gydZ/dVBMiSy1g8gJLcNDs1Q+gRxPrEB6+AEqNuiYH7xDvEi/FOoTKili 5ObRXkPyO/VDH8WWq9Wnn+KqqENn4PWzrEudNYBwIM9+4bmisWf+XVLik B+3eEbDswi5KeUnulbeOZ1MKzxnEy5FqJ7lMBpYxwSxMbKPiPP0wcLtGq rHr9MDKtYLI0Yo3qmIlA1ClhewB6l9TDVtxIsZcwGldCEKBW2/HQz7nlH BRmMKyGU2eTjUpQBHp0hRk7w/1TVCCpWr9gY2CEZbg3PbsBai4ziHZWh6 w==;
X-CSE-ConnectionGUID: Zb9I3d4KTmaowToOr+q8JA==
X-CSE-MsgGUID: ca72GSyXQSanwsdiw3kn/A==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:ibjwu6r5pO/Mr0csEbZ+XpwpHjBeBmJyZBIvgKrLsJaIsI4StFCzt garIBmAa6uNZ2enfo9+adnnp09V6pHVxtVqTgU4ry81RXka95acVYWSI3mrMnLJJKUvbq7FA +Y2MYCccZ9uHhcwgj/3b9ANeFEljfngqoLUUbOCYmYpA1Y8FE/NsDo788YhmIlknNOlNA2Ev NL2sqX3NUSss9JOGjt8B5mr9lU345wehBtC5gZiPasR5AeH/5UoJMl3yZ+ZfiOQrrZ8Q7bSq 9brlNmR4m7f9hExPdKp+p6TnpoiG+O60aCm0xK6aoD66vRwjnVaPpUTbZLwXXxqZwChxLid/ v0W7MDtFl15VkH7sL91vxFwS0mSNIUYoOOXeSDXXca7lyUqeFO0qxli4d1f0ST1NY+bDEkXn cH0JgzhYTixjbOXm77nadVpj8M8EM7MJsAG6lNJmGSx4fYOGfgvQo3g3/kB4xEdtpgXW+jVY NABLzNjKgraeBsJMVASYH48tL7wwCCgKHsB9QnT+fpfD2v7lWSd1JD2MN3RftGMT8henW6Gq 3jH5GX2BFcRM9n3JT+tqSr3176QwXOTtIQ6H7TnrNFRkW2q/WUVFwYaVETgov/+oxvrMz5YA wlOksY0loA880aqVcH6dwGlq3mbpVgXXN84O/c35wyd1oLV7hqXQG8eQVZ8hMcOvtUwHCMs2 0/RxpbyGyYptbyODHiasL2Oq2r0JzIOKykJYipsoRY53uQPabob1nrnJuuP2obs5jEpMVkcG wy3kRU=
IronPort-HdrOrdr: A9a23:QPYLYathOvBan0J1OS3rvGbc7skDq9V00zEX/kB9WHVpm6uj5q WTdZUgpH3JYVkqOE3I9ervBEDiexzhHPdOiOEs1NyZLWrbUQWTTb1K3M/NzzrtACXi+uMY/r cIScRDIey1KVRhl8717E2bH8ZI+rO62ZHtoevF1X9iQUVRdqd6425CZzqzCEFsWwVcP5Y/Ga ed4sYvnVGdRUg=
X-Talos-CUID: 9a23:fW8Zymu6rn2Q+c7EDp/d3uSU6IsXeCz8l3uMAHO9AGF2dLqyUxyJqIFNxp8=
X-Talos-MUID: 9a23:8D3y4w3bn0R8LWLVO4I/CIDiRjUj6K3xUm82gKU/gMCCKjd8OijGjzLwa9py
X-IronPort-AV: E=Sophos;i="6.07,139,1708387200"; d="scan'208";a="30399748"
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.35; Wed, 20 Mar 2024 00:56:54 -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.035; Wed, 20 Mar 2024 00:56:54 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "fobispo@tucows.com" <fobispo@tucows.com>
CC: "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] Re: [regext] EPP Transport Service Discovery
Thread-Index: Adp6ali/WjYcMp1BRDifguzfI9i3tgANsuoAAAeyHoA=
Date: Wed, 20 Mar 2024 04:56:54 +0000
Message-ID: <4529b20872b84c9580e0da43dcd493d6@verisign.com>
References: <c9fd4e5780f740dc9129e42a28a21813@verisign.com> <33DE0A17-6481-462D-A856-18890E3583E6@tucows.com>
In-Reply-To: <33DE0A17-6481-462D-A856-18890E3583E6@tucows.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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/jxlGDQtyDMbHgM028TEgRbEsVVM>
Subject: Re: [regext] EPP Transport Service Discovery
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: Wed, 20 Mar 2024 04:57:00 -0000

> -----Original Message-----
> From: Francisco Obispo <fobispo@tucows.com>
> Sent: Wednesday, March 20, 2024 12:32 AM
> To: Hollenbeck, Scott <shollenbeck@verisign.com>
> Cc: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] EPP Transport Service Discovery
> 
> 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.
> 
> This is a neat idea,
> 
> Is there a reasoning or use case for such need?
[SAH] [snip]

During today's WG meeting we discussed three proposals for non-TCP EPP transport. If any of them become standards and are implemented and deployed, a client will not be able to assume that tcp/700 is the only available transport. It will need to discover which transport is supported by every server it communicates with. That's the need.

Scott

v2.23.0 | Report a Bug | By Email