Re: [regext] Questions about RDAP extensions and registration at IANA, role of prefix and version

"Patrick Mevzek" <> Thu, 23 January 2020 16:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6E7EE1208E0 for <>; Thu, 23 Jan 2020 08:32:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=sPD9HZR0; dkim=pass (2048-bit key) header.b=XQTfSLgx
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id a1hluJ5ge97N for <>; Thu, 23 Jan 2020 08:32:27 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F03581208E5 for <>; Thu, 23 Jan 2020 08:32:26 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal []) by mailout.west.internal (Postfix) with ESMTP id 7FF955C2 for <>; Thu, 23 Jan 2020 11:32:26 -0500 (EST)
Received: from imap1 ([]) by compute3.internal (MEProxy); Thu, 23 Jan 2020 11:32:26 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=StWPOLepujCqG3IodW+tWftcAzziQ/x CN6ZzCfIoMdI=; b=sPD9HZR0CI3fe1F75UTOjuN91A6GnAyFM/7AOngTVRpPW0m uz4sP4G8Ir/V28KU1ps0bduSDmBnhqfV7M4ktE1PGS8eC47o0imLJj6Oj0kqJYhJ eSm4MIoQJlMvgCtqCciMQofp95Qf5vhEr26u7Ru2cKdX7HgeSj9gwX7K9Kny9NAT 2FEpDjoJCYxp/oNW2t7SSXdjDA6IO6ia3rdtcWadiqigV7Jiydo0Ja586+vqxfxL MfUpwN2LmPc/PGp8Qs3uQ2JGukbZluVBhEpzcBTtlSbxRYdrPxFBfTnSh3p7UP8o B2hR3SL2DiF+aQWZY9gekcvTAgpoumd7BiUIN+w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=StWPOL epujCqG3IodW+tWftcAzziQ/xCN6ZzCfIoMdI=; b=XQTfSLgxr1P+Rrdkher/IS 2W27VpE4753PL3cBvGp5zrs2ckNXwXhDRqSysojj4Fhll61INRvA4LHrOVv8vmpH fsKO8zchK8inn70HzXfOuC5026o4QG19go4dyTMxUkNOWKUPh/FsyyjP/zSH05Dh vD/rwk4flRnuWOydGweg/LyBCRPTrbrP333Hah6sYebKOFOClPzrn2JgSleQoIUG NU0j9zT+GN9uIU53eKUIxm2HbNWnNSiv5j/ECP8HN+kNCxPjvwil3MXPETAELEmg vb8vQn4TqUgUitYw52Y2FebHInK//85jONXogAFSTLKJ6qt/zqSL5AOxvNpCVn2g ==
X-ME-Sender: <xms:mcopXkIxp4hLVL5dV1kMcBiNV8FVQZ68Ha-qoAIkb5qrOfqoAk3kW3uMOrY>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrvddvgdehkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreerjeenucfhrhhomhepfdfrrghtrhhitghkucfovghviigvkhdfuceophhmseguohht rghnuggtohdrtghomheqnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepphhmseguohhtrghnuggtohdrtghomh
X-ME-Proxy: <xmx:mcopXk5JEY0FCAHwtkT88RMC5ti9UdBJ-xpNM-WHadOVZ4cgoNtZsg> <xmx:mcopXkVbkSJ-OB5Bx0POQlfA7HUs8CtdPwegfUbtXtspIkR0woVCCg> <xmx:mcopXqlh7EgZLs2spDGhOiGnWZKv2R6xUQr1WngcUK7y8e2_3POqvw> <xmx:msopXj-5tuGQniWuBG_QOUlHRpdXcC7dIdPhDJ2x4kmrq9FlCxfTEg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id D3EEAC200A4; Thu, 23 Jan 2020 11:32:25 -0500 (EST)
X-Mailer: Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-775-g74f2d12-fmstable-20200121v1
Mime-Version: 1.0
Message-Id: <>
In-Reply-To: <>
References: <> <> <> <>
Date: Thu, 23 Jan 2020 11:32:04 -0500
From: "Patrick Mevzek" <>
Content-Type: text/plain
Archived-At: <>
Subject: Re: [regext] =?utf-8?q?Questions_about_RDAP_extensions_and_registrat?= =?utf-8?q?ion_at_IANA=2C_role_of_prefix_and_version?=
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 Jan 2020 16:32:28 -0000

On Thu, Jan 23, 2020, at 11:09, Hollenbeck, Scott wrote:
> The URNs that appear in a greeting should exactly match those that 
> appear in a specification, are registered with IANA, should be used 
> during login, etc. I hope that registrars can work with that server 
> operator to make appropriate corrections.

I agree, but FWIW it is an old ccTLD (so not like a new server/TLD
just having appeared), and I just stumbled on that by chance recently
and was keen to share with the community, but since I guess this exists for a long
time, no one was feeling it should be corrected, so I guess it will persist
for a long time. Unfortunately.

But it happens, often (maybe?) it is simpler for registrars to work around
(with local "patches") what they think is a problem from responses they got,
than trying to make the registry act on them. It is just a matter of finding
out where your time is better spent, since "being 100% standard compliant"
is not exactly a big selling point for customers, just accepting orders
may be preferred, business-wise, than taking time to put pressure on registries
to fix things.

There is no worldwide EPP police indeed.

Or fortunately :-)

  Patrick Mevzek