[regext] Security/Registry Lock Side Meeting: Wed, 14:00 - 15:00, Room Paris

Alexander Mayrhofer <alexander.mayrhofer@nic.at> Tue, 26 March 2019 10:13 UTC

Return-Path: <alexander.mayrhofer@nic.at>
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 C4977120282 for <regext@ietfa.amsl.com>; Tue, 26 Mar 2019 03:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.999
X-Spam-Level:
X-Spam-Status: No, score=-6.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nic.at
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 CJYGYBCNVzT2 for <regext@ietfa.amsl.com>; Tue, 26 Mar 2019 03:13:34 -0700 (PDT)
Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) (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 3FA111202A1 for <regext@ietf.org>; Tue, 26 Mar 2019 03:13:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nic.at; s=it2019; h=From:From:To:CC:Subject:Date:Message-Id:Content-Type:Received:Received; bh=+45wdYyvbMHnLrA3ca5arAXOyHcJtRg9vx4cAyLugzc=; b=vbdh6nn63KusLMey+U681zAEoYCGrw4bDAaSdzV7FNsXwpN0VFRCZyyGJSBYMjmhM8rMevEmvfs0lMwkBZwrGWiSKFP6V5m9SaWxCcxu/xY4YXLNIpicM306Sa744mfvka9FMTgU+13foHwvIQZsna4nZM6zR0B51wwEzB+MBYgWlKv3FHQy+Ny+r4w0ETXQsw1Mizxq4NjleGcWXD+2ua50TC7AY6PyDBl0e0IVl1FVssjoR0WLwY//6XjC2rHLIK+KL6S1jvabB6/D/a4uqBYx0hQIXgHRSSmAgJrST7gDTfA1BLm5mXD0PNThZS50/ck+zGSRrBAjudq5r2HRSQ==;
Received: from nics-exch2.sbg.nic.at ([10.17.175.6]) by mail.sbg.nic.at with XWall v3.53 ; Tue, 26 Mar 2019 11:13:30 +0100
Received: from NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57]) by NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57%12]) with mapi id 14.03.0439.000; Tue, 26 Mar 2019 11:13:25 +0100
Thread-Topic: Security/Registry Lock Side Meeting: Wed, 14:00 - 15:00, Room Paris
Thread-Index: AdTju5Upt9I6hsDIThahso9FFTrKRg==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.3.53]
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: "regext@ietf.org" <regext@ietf.org>
Date: Tue, 26 Mar 2019 11:13:25 +0100
X-Assembled-By: XWall v3.53
Message-ID: <19F54F2956911544A32543B8A9BDE0759FC0D703@NICS-EXCH2.sbg.nic.at>
X-XWALL-BCKS: auto
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="_NextPart_1_579nlaroPJAvxWADvANdcFdIegh"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/4PNUX-OYGbYTz1bpNJC0BUC-GaY>
Subject: [regext] Security/Registry Lock Side Meeting: Wed, 14:00 - 15:00, Room Paris
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 Mar 2019 10:13:36 -0000

Hello everyone,

as mentioned during the regext WG session, i've organized a "SecurityLock / RegistryLock" side meeting. Meeting details are as follows:


-          Date: Wed, 2019-03-27

-          Time: 14:00 - 15:00

-          Location: Room "Paris" at the IETF venue

Unfortunately, remote participation won't be possible. I do understand that a beamer is available, though.

My plan for the Agenda would be as follows:


-          Security Lock / Registry Lock "problem space" introduction (Alex, 10m)

-          Tour de Table of current/planned "Security Lock" features, brief description (2m each), eg:

o   How does the locking work (Who locks, how?)

o   How does the "approval" of changes work (Who approves, what happens to transactions?)

o   How does the "unlocking" work (Who unlocks, and how?)

o   Forms of authentication

-          Which areas could benefit from standardization? Discussion (20m)

-          Wrapup and next steps (10m)

I'm looking forward!

Best,
Alex