IETF Logo Mail Archive

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

Alexander Mayrhofer <alex.mayrhofer.ietf@gmail.com> Mon, 04 March 2019 09:14 UTC

Return-Path: <alex.mayrhofer.ietf@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 1364612941A for <regext@ietfa.amsl.com>; Mon, 4 Mar 2019 01:14:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 74HVzqB0qhNF for <regext@ietfa.amsl.com>; Mon, 4 Mar 2019 01:14:26 -0800 (PST)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 2310E1293B1 for <regext@ietf.org>; Mon, 4 Mar 2019 01:14:26 -0800 (PST)
Received: by mail-lf1-x131.google.com with SMTP id m73so2971834lfa.2 for <regext@ietf.org>; Mon, 04 Mar 2019 01:14:26 -0800 (PST)
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=ceW/2xwCw6yhagTuScjlwPv5HERUS7N+5JsMf6CqyC0=; b=CCeiIYbmVijF2SplInlwovPH/UABVaJLbcHe4qa6OCzpq2Y9eLlQK0NhVxlzM9NQd7 FPPPeTuJHvlp+K0ibhp0MJa0+YLU5N2oIhifAw2HEy1vXcRHx3YekOT4wukoKkF+zO8c wEhDxOWolqcFKYb19pGX1NOG+23ynImqmf+0VTiuNaNkZzTLDmfoaqvhGtdJEXAUGmAo +O6AfdXpeRW047k9Oaog/zUG5/lUPPtQdYOvS0q/9y47UPr1t09wuZciE24sDeLUBRCg 5iuQHl5Q2zGbsgLlVBr3CrPhQ/p3HX94tjhESG8X+6wcOzpCYwj+78RT5Ls+npmyoCvM boXg==
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=ceW/2xwCw6yhagTuScjlwPv5HERUS7N+5JsMf6CqyC0=; b=TCwsXiZngOQWFPHtc6Fde/JX/XHKD8zI+YqmbguIzIkrADIHn9crnq1LYirWqXrqeE x+cWJ70rMYIXodaVzf9HtTgtlYdgo+KXK24p8YbCGo8m9Rnei9lf64t6b1BDPntHgwmJ +tWZSK0TxZ45Y7CYsQza7OHr2kKRLTXwnuYB/il6E9mh4YNadsTkA5U2VYlZcxV7iX4g iiP6PHMMwccHQw3QgGNJUn46vCvJ3Zz561z3omNlPqOqZifQC86JN8FyuCciv1hgDn+T En5Ad6+PW0GkXmm23vOickmcN9z8ILazZ8SQ5Rr5E9xuBpnoggTpWgMBIEySFzL5JNrE Dbng==
X-Gm-Message-State: APjAAAVyYQtvAG6asmFw4s1ZcaQ3J2tBWqPG2yOXk81E022yUe66w4MY rPx/oC2GC7HE2Hg2PYAKrK5zF7XBCnUWJaSmAu2rMQ==
X-Google-Smtp-Source: APXvYqx+IDYY1S86HaftB2ERPoiEu3CXmhgJRUzRneOcWQmS4wMTC+IZr35X58KRwQokIuUWvYS927UTge+6trtjRoA=
X-Received: by 2002:a19:6454:: with SMTP id b20mr10143936lfj.150.1551690864304; Mon, 04 Mar 2019 01:14:24 -0800 (PST)
MIME-Version: 1.0
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> <2BE5D16A-F8A6-4609-9420-19BA1CE89185@nic.br> <alpine.DEB.2.20.1902261744450.19193@grey.csi.cam.ac.uk>
In-Reply-To: <alpine.DEB.2.20.1902261744450.19193@grey.csi.cam.ac.uk>
From: Alexander Mayrhofer <alex.mayrhofer.ietf@gmail.com>
Date: Mon, 04 Mar 2019 10:14:13 +0100
Message-ID: <CAHXf=0rcJD_CQQ5WhLPhC_AtqXqMkZDdxpZAMjBfx1KRsSErGQ@mail.gmail.com>
To: Tony Finch <dot@dotat.at>
Cc: Rubens Kuhl <rubensk@nic.br>, "regext@ietf.org" <regext@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/KG27u6TqyJA5Zawm9ed1K7b9dyo>
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: Mon, 04 Mar 2019 09:14:28 -0000

I've reserved room PARIS on wednesday, 2pm for that discussion. I hope
that everyone can make it - this is the "unstructured time" slot on
Wed afternoon, and so far it does not collide with any BoFs.. If
there's a more convenient time, please let me know in private mail...
i thought a doodle would be overkill for now..

best,
Alex

On Tue, Feb 26, 2019 at 6:46 PM Tony Finch <dot@dotat.at> wrote:
>
> Rubens Kuhl <rubensk@nic.br> wrote:
> >
> > 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.
>
> There is RFC 7477 CSYNC, but I don't know of any implementations.
>
> Tony.
> --
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
> safeguard the balance of nature and the environment
>
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext

v2.23.0 | Report a Bug | By Email