Re: [regext] Security Lock anyone? (Was: Preliminary agenda for Prague, and call for agenda items)

Rubens Kuhl <rubensk@nic.br> Tue, 26 February 2019 03:15 UTC

Return-Path: <rubensk@nic.br>
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 832BD130E6B for <regext@ietfa.amsl.com>; Mon, 25 Feb 2019 19:15:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.br
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 Y_vO_y_-xQLU for <regext@ietfa.amsl.com>; Mon, 25 Feb 2019 19:15:28 -0800 (PST)
Received: from mail.nic.br (mail.nic.br [IPv6:2001:12ff:0:4::5]) (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 6D0FB130E68 for <regext@ietf.org>; Mon, 25 Feb 2019 19:15:27 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.nic.br (Postfix) with ESMTP id E6A1C1498CF for <regext@ietf.org>; Tue, 26 Feb 2019 00:15:23 -0300 (-03)
X-Virus-Scanned: Debian amavisd-new at mail.nic.br
Authentication-Results: mail.nic.br (amavisd-new); dkim=pass (1024-bit key) header.d=nic.br
Received: from mail.nic.br ([127.0.0.1]) by localhost (mail.nic.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTe3_ojWRt_6 for <regext@ietf.org>; Tue, 26 Feb 2019 00:15:21 -0300 (-03)
Received: from [IPv6:2804:431:9701:f94c:8040:d8bd:febd:de1c] (unknown [IPv6:2804:431:9701:f94c:8040:d8bd:febd:de1c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: rubensk@nic.br) by mail.nic.br (Postfix) with ESMTPSA id 626471498CE for <regext@ietf.org>; Tue, 26 Feb 2019 00:15:20 -0300 (-03)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.br; s=dkim; t=1551150920; bh=WS/5L1eavDbEacNeta2sqaPAQUhxCqoaUG4L53v4LHg=; h=From:Subject:Date:References:To:In-Reply-To:From; b=LjnbkHsOfBe7oEuwxEVuMzRl5u2nysK6hiqKzJLwnsuYA6qd6RmOeLc03DWSQt790 EpDsag/s2dg5gEgNSbwhsCJxk76wEx/2gKh8+gsIjcCW0uV2ChoGxfNkjiAEzdFSLV /rOucrwhvo00gSrheU0qwsP/7YMiMv6C5U5NcS3c=
From: Rubens Kuhl <rubensk@nic.br>
Content-Type: multipart/signed; boundary="Apple-Mail=_9234921D-F060-4078-ACAB-BAA662240154"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Tue, 26 Feb 2019 00:15:18 -0300
References: <19F54F2956911544A32543B8A9BDE0759FBF8765@NICS-EXCH2.sbg.nic.at> <8175501f-3365-c8d1-7a76-a4584e76734e@centralnic.com> <C4A68CA3-1ADE-4959-A51E-A73F4A4914DC@sidn.nl> <395DD26B-B2D1-4144-87BD-8DBCD772A8A5@lansing.dk> <34c35e4c575a4e338215b919c102cdfc@cira.ca>
To: "regext@ietf.org" <regext@ietf.org>
In-Reply-To: <34c35e4c575a4e338215b919c102cdfc@cira.ca>
Message-Id: <2BE5D16A-F8A6-4609-9420-19BA1CE89185@nic.br>
X-Mailer: Apple Mail (2.3445.102.3)
DMARC-Filter: OpenDMARC Filter v1.3.1 mail.nic.br 626471498CE
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/ah8CqsKh6Z90vs9uZJwsu8W_fFQ>
Subject: Re: [regext] Security Lock anyone? (Was: Preliminary agenda for Prague, and call for agenda items)
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: Tue, 26 Feb 2019 03:15:30 -0000

I imagine that DNS as a communication channel to assure registrant willingness to change something, similar to CDNS/CDNSKEY, could be quite useful. For instance, if the name servers that are delegated on the registry are now pointing to new name servers, and this response is signed by the current DS/DNSKEY on the delegation, changing the DNS servers for that domain is pretty safe.

If registrant's adversary already has control of the domain DNS servers, preventing the change of name servers gives very little to the registrant.



Rubens


> On 25 Feb 2019, at 14:46, Tongfeng Zhang <tongfeng.zhang@cira.ca> wrote:
> 
> At .ca and all the TLDs CIRA operates,  we have a similar feature of registry lock.
> We are interested in standardization for sure.
> 
> There is a regiOps workshop coming up in May in Bangkok. I see a fit there if regext is not the right place.
> 
> Cheers,
> Tongfeng
> 
> 
> -----Original Message-----
> From: regext <regext-bounces@ietf.org> On Behalf Of Erwin Lansing
> Sent: Monday, February 25, 2019 11:25 AM
> To: regext@ietf.org
> Subject: Re: [regext] Security Lock anyone? (Was: Preliminary agenda for Prague, and call for agenda items)
> 
> Folks,
> 
> At .dk we also offer a form form of registry lock, called VID, which I’d like to redesign at some point.  Having a standardised, or at least similar “enough” product offering across different registries and TLDs would make it much more attractive for registrants.  Even though I won’t be in Prague, I’m certainly interested in following any standardisation effort.
> 
> Best,
> Erwin
> 
> 
> 
>> On 25 Feb 2019, at 17.11, Marc Groeneweg <Marc.Groeneweg@sidn.nl> wrote:
>> 
>> All,
>> 
>> At SIDN (for .nl) we have our own form of registry lock called .nl control (https://www.sidn.nl/en/nl-control?language_id=2). Perhaps this can be used as input for a joined effort in increasing security around registry/registrar operations.
>> 
>> Regards,
>> Marc Groeneweg
>> 
>> On 25/02/2019, 14:57, "regext on behalf of Gavin Brown" <regext-bounces@ietf.org on behalf of gavin.brown@centralnic.com> wrote:
>> 
>>   If a BoF happens in Prague I will certainly attend.
>> 
>>   On 25/02/2019 07:26, Alexander Mayrhofer wrote:
>>> Antoin, all,
>>> 
>>> 
>>> 
>>> for now this is more a question / request to the group, rather than a
>>> specific agenda slot request – but:
>>> 
>>> 
>>> 
>>> In the light of the recent attacks on registration interfaces, do we
>>> want to take a fresh look at standardization of “Registry Lock” /
>>> “Security Lock”. There’s some previous work on this topic (see
>>> https://tools.ietf.org/html/draft-wallstrom-epp-registrant-problem-statement-00).
>>> As Patrick pointed out, there’s also some IPR considerations in this
>>> area (See his blog post at
>>> http://www.circleid.com/posts/20150603_registry_lock_or_epp_with_two_factor_authentication/).
>>> 
>>> 
>>> 
>>> I constantly hear from registrars that “Security Lock” (our product
>>> name) would be much more attractive if there wasn’t a myriad of
>>> different processes at each registry – so my take is that there’s
>>> room for standardization (which probably goes beyond the pure EPP extension).
>>> I’m also hearing some fellow ccTLD colleages are interesting in a
>>> common “profile”.
>>> 
>>> Would regext be the right spot for such a discussion? If yes, would
>>> it be interesting to hold a 20 minutes slot in Prague? Or even a
>>> Bar-BoF before we “report back” to the working group?
>>> 
>>> 
>>> 
>>> Best,
>>> 
>>> Alex
>>> 
>>> 
>>> 
>>> 
>>> 
>>> *Von:*regext <regext-bounces@ietf.org> *Im Auftrag von *Antoin
>>> Verschuren
>>> *Gesendet:* Sonntag, 24. Februar 2019 14:43
>>> *An:* Registration Protocols Extensions <regext@ietf.org>
>>> *Betreff:* [regext] Preliminary agenda for Prague, and call for
>>> agenda items
>>> 
>>> 
>>> 
>>> Hi all,
>>> 
>>> Please find the preliminary agenda for Prague attached.
>>> I hope I captured everyone that has requested time to speak. If not,
>>> let the chairs know.
>>> We still have a little bit of time left on the agenda, so if you have
>>> urgent agenda items, let us know as well.
>>> If you are on the agenda, start preparing ;-)
>>> 
>>> 
>>> 
>>> 
>>> Regards, Jim and Antoin
>>> 
>>> - --
>>> Antoin Verschuren
>>> 
>>> Tweevoren 6, 5672 SB Nuenen, NL
>>> M: +31 6 37682392
>>> 
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> regext mailing list
>>> regext@ietf.org <mailto:regext@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/regext
>>> 
>>> 
>>> _______________________________________________
>>> regext mailing list
>>> regext@ietf.org
>>> https://www.ietf.org/mailman/listinfo/regext
>>> 
>> 
>>   --
>>   Gavin Brown
>>   Chief Technology Officer
>>   CentralNic Group plc (LSE:CNIC)
>>   Innovative, Reliable and Flexible Registry Services
>>   for ccTLD, gTLD and private domain name registries
>>   https://www.centralnic.com/
>>   +44.7548243029
>> 
>>   CentralNic Group plc is a company registered in England and Wales with
>>   company number 8576358. Registered Offices: 35-39 Moorgate, London,
>>   EC2R 6AR.
>> 
>> 
>> _______________________________________________
>> regext mailing list
>> regext@ietf.org
>> https://www.ietf.org/mailman/listinfo/regext
> 
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext