Re: [regext] Implementations of draft-wisser-registrylock?

Erwin Lansing <> Mon, 18 May 2020 12:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2F4433A0B66 for <>; Mon, 18 May 2020 05:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.802
X-Spam-Status: No, score=0.802 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, OBFU_TEXT_ATTACH=1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BKuB8nK-EAEe for <>; Mon, 18 May 2020 05:40:48 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B16F33A0B64 for <>; Mon, 18 May 2020 05:40:47 -0700 (PDT)
Received: from ( [IPv6:2a02:980:2510:ba00:6ca4:9c17:50d8:9848]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by (Postfix) with ESMTPSA id 7CC6940225; Mon, 18 May 2020 12:40:36 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;;; t=1589805636; bh=TeEAP6ennAmAIEChfwuh2lAV96r+zMY+et5hyG/EC2I=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=jnt9onk2GG773UUdgJUJwXRdkgRZZIjok4Z0Wn7BeJLjSC12FL/BsPVcMOKRRyBtq gGqoEfriJILp0YoePxf/6COqFwPH9nY0ZLlCGe8C0yVNu+xC3AY5cwVwYtbSoupX0R TdlSsxlc+xCR2vcwZ66r6DfMgoTIKGBpQKV+vzpH3qD0/NyMneGx5NNlNAI1l8/UBv jRZhgAxAVWiO6DMzza9QhSHj7dmMNTwi53CAy4gy4vfhMTRu/8H526bWGTHmFGPVDs 2Ds4VyLjLbjXgpg+jn8tQE4MxEhdC080El8buvIvveobIg8OWcJbvnnK/+OffL8AIo vrVHrJSjbqQow==
From: Erwin Lansing <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FE912FE0-DF5D-44D6-B641-F6E87EAD7FC6"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Date: Mon, 18 May 2020 14:40:43 +0200
In-Reply-To: <>
Cc: "" <>
To: Ulrich Wisser <>
References: <> <20200327094413.73386d66@nbbrfq.loc> <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [regext] Implementations of draft-wisser-registrylock?
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: Mon, 18 May 2020 12:40:50 -0000

Hi Ulrich,

Thanks for creating this draft.

My impression from reviewing the different registry business models is, that most differences are related to sales channel and out-of-band unlocking methods. As long as locking trough create and update is optional for the server implementation, and since the draft is staying well away from prescribing out-of-band methods, I think it is flexible enough to cover most, if not all, different business models.

Admittedly, I’m not an EPP implementer, and may not be the intended audience, but I had a hard time putting two and two together for some of the features. There are a lot of nuances, that could be brought more clear forward to explain their intention and what they mean to achieve. Two examples that could be highlighted more:
- Front and center: renew - always allowed, transfer and delete - always refused, update - depends on lock status.
- unlockUntil - can only be used at the same time as the initial lock of the domain to delay when the lock becomes active (at least, that’s what I read).

WRT to your question on subordinate hosts, in .dk we agree that they are owned by the domain owner and follow the same procedures as the domain itself.

Finally some nits, I think the last sentence in 2.2 belongs in 2.1, and some typos attached.


> On 7 Apr 2020, at 17.27, Ulrich Wisser <> wrote:
> Hi,
> I have made significant changes to the draft.
> Many thanks to contributions by Michael Bauland and Bernhard Reutner-Fischer.
> Please find the draft at <>
> And please give it a review. 
> If your registry currently offers or will offer registry lock in the future I would be interested to hear how this draft fits or doesn't fit your business model.
> Kind regards from Stockholm
> /Ulrich