Re: [regext] RegistryLock draft (as promised)
Karl Heinz Wolf <khwolf1@gmail.com> Thu, 29 August 2019 12:03 UTC
Return-Path: <khwolf1@gmail.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 DFBC81200F1 for <regext@ietfa.amsl.com>; Thu, 29 Aug 2019 05:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I1cU1v6KFBzm for <regext@ietfa.amsl.com>; Thu, 29 Aug 2019 05:03:37 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 081021200D5 for <regext@ietf.org>; Thu, 29 Aug 2019 05:03:37 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id n7so3320317qtb.6 for <regext@ietf.org>; Thu, 29 Aug 2019 05:03:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=t8G1/m6h9QWbTu7sCXEoh31JMWMwxg2XiIWbjvZF+Q8=; b=h3IHBxYuRkRuD50eMU4MNbQvO9YBDrsuXUwj8ZNCHOmLGql4h9uW9hUM6mKLTcw907 VZLOaiobRxi4koAstaD8MQxOYQP68lQpD7FBEppCYFpeaqfwGtUJA2SUglzwfQdho72R WDwSvKDfePQJFSHhBn0yuZtM8+YHkoFOE1p10kORG8rf1bZP+3/8stb3Tis4F7MrF0Sw VfIgol+F/2BtTrWUzTDs/vtYxaMFjU+h6dxFA6GmE1sqYFzOyOHTKDYLcPLRnbnRcWYn dtI4brB8gqyQLEmeTnGUV1lPxFoJnBk4y4DirXPBPbqZrLaiSSAud+QL0MjjzKR/cBUM W2ZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=t8G1/m6h9QWbTu7sCXEoh31JMWMwxg2XiIWbjvZF+Q8=; b=kMhS45gnEyQb+SUrHtyy6jtQvfUG5KGNP/Y/cvvIv4vWYVQlB1nk4QHnv26GWsCEA3 mM+z8EA2ZP9T9//tmV7GNBkWhiDwK8AuJBESFVEjgf8va90oz95X++8epzPhIk9rJwxn H+qBDvJis0JZMejcEXJURFQZyO3mipXzofj7mzBXo+SH2ZlC6b64QhtnDNoxmiFmb2Tg UZHIxluWkSTuQzRp34atBDjvOhaVvCMctKde/e8/W3lXQrXKAB6AAdiLbdRAZasUyDGd ltgymX0kxZqafkIa8kGTOGww0N6JigiCv+bt3f9FnnO4MkmPrhOWRVdDkXmthe0aQhaz kZ7Q==
X-Gm-Message-State: APjAAAVvgkCcDo+WYZih8QErVypEwH41Ei1WlxlAP89XLOKpi3ExsLb7 pHFC55tyVdd4BLsj3LC/05IlTThdebwnhEwbMXMfrWZpCkw=
X-Google-Smtp-Source: APXvYqzKoxEQ57cP5Zz50q0INSHmZdoa/Jw8KmHXFRMz75h1sOGVXyK/PmQnIW80yuJCU6F9V2/KG+v9fUFZl1LfQ4w=
X-Received: by 2002:aed:3787:: with SMTP id j7mr3874448qtb.56.1567080215359; Thu, 29 Aug 2019 05:03:35 -0700 (PDT)
MIME-Version: 1.0
References: <CAJ9-zoU=FF8FLYGsGyvzeM041ZRQ3ytvznWbje9pMfQ_inH=qg@mail.gmail.com>
In-Reply-To: <CAJ9-zoU=FF8FLYGsGyvzeM041ZRQ3ytvznWbje9pMfQ_inH=qg@mail.gmail.com>
From: Karl Heinz Wolf <khwolf1@gmail.com>
Date: Thu, 29 Aug 2019 14:03:23 +0200
Message-ID: <CAL=Qo5gFA96icx2Fz_4bD=qjJ26KqGDkWj0DO7UYGp46EPWJoQ@mail.gmail.com>
To: Ulrich Wisser <ulrich@wisser.se>
Cc: regext@ietf.org
Content-Type: multipart/alternative; boundary="000000000000923d570591404b41"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/2PSeYIUIK2a_0n_H8Cu_OGOqPBk>
Subject: Re: [regext] RegistryLock draft (as promised)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 29 Aug 2019 12:03:39 -0000
Ulrich, thank you for writing this up. I think it is a good idea to have a document with a definition of what a registry lock actually means (e.g. status values to be set as listed in Section 2.3). However, some parts of your EPP extension seem underspecified, here are a few comments and questions that came to my mind while reading: how does the create work? Is the example in Section 4.2.1 a domain create that additionally adds a registry lock, or does the domain already exist and only the registry lock is added? It looks to me as the former, but it also says "If the object is locked, the EPP <create> command MUST be rejected" – so this might refer to already existing domains? Having said that, also the update section should clearly state what can be done (lock and unlock existing domains?). I do not find any information on the restriction type "password", it only shows up in the schema. I wonder if registrars would also like to receive information about out of band unlocks via the EPP message queue. It would also be interesting to know more about the out of band processes (even though out of scope for the draft) you have in place for your registry lock implementation, if you want to share that. Thanks Karl On Fri, Mar 29, 2019 at 1:51 PM Ulrich Wisser <ulrich@wisser.se> wrote: > Hi, > > as promised at the Registry Lock side meeting and by Alex in the minutes > from the meeting, > here comes the link to my "secret" draft. > > https://tools.ietf.org/html/draft-wisser-registrylock-00 > > Comments and improvements are of course welcome. > > /Ulrich > _______________________________________________ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext >
- [regext] RegistryLock draft (as promised) Ulrich Wisser
- Re: [regext] RegistryLock draft (as promised) Karl Heinz Wolf