[regext] ROOM CHANGE to TYROLKA - Security/Registry Lock Side Meeting: Wed, 14:00 - 15:00

Alexander Mayrhofer <alexander.mayrhofer@nic.at> Tue, 26 March 2019 17:14 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 416141203E3 for <regext@ietfa.amsl.com>; Tue, 26 Mar 2019 10:14:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.998
X-Spam-Level:
X-Spam-Status: No, score=-6.998 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, URIBL_BLOCKED=0.001] 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 zgYLnk10iwQW for <regext@ietfa.amsl.com>; Tue, 26 Mar 2019 10:14:00 -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 E5869120423 for <regext@ietf.org>; Tue, 26 Mar 2019 10:13:59 -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=BuvqvawcLH5m3G2KAbXymkXfLPYfq4H0VP6CKUr1ggg=; b=PAbys4PIaC8fPnhN2UR8Y7dEabuM4JX1IlPBi6G8+SieVD2glw59Obq6wyq/OKONxXutJMCKVru/d8GjoDR169t2S9/A8KtquswgZ+x6FVkTAtJdz8cjIFIwWNzlC6KR7DqM18q/KT4xj6lo1grl3EjxFviJ7hFxJWc8+qiXHiFo63j04ECftGq3vO9XxzZmX6vmhKHKqxkr0rS+QhL/mNwPC+ahNKs8/B+WLFAK8I946ou6dKM7hZJ/qFUJTzvUGnn3jPvStRcPwDs9njrghfzVmCIA9BV/kJDU/oGCnzwoj4Nq33uU4ap/p8Hzhn9htMpPn/PHluXmudEuMBQ6ZQ==;
Received: from nics-exch2.sbg.nic.at ([10.17.175.6]) by mail.sbg.nic.at with XWall v3.53 ; Tue, 26 Mar 2019 18:13:57 +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 18:13:53 +0100
Thread-Topic: ROOM CHANGE to TYROLKA - Security/Registry Lock Side Meeting: Wed, 14:00 - 15:00
Thread-Index: AdTj9zOikFdln6S+Sn2xzjkEkr5KQA==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.3.59]
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: "regext@ietf.org" <regext@ietf.org>, "dnsop@ietf.org" <dnsop@ietf.org>
Date: Tue, 26 Mar 2019 18:13:52 +0100
X-Assembled-By: XWall v3.53
Message-ID: <19F54F2956911544A32543B8A9BDE0759FC0D8ED@NICS-EXCH2.sbg.nic.at>
X-XWALL-BCKS: auto
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="_NextPart_1_579nlbh2YeizEWjmDStxIPPIwGz"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/RJuWU50PqPwF95_SpzBUVCy1_FQ>
Subject: [regext] ROOM CHANGE to TYROLKA - Security/Registry Lock Side Meeting: Wed, 14:00 - 15:00
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 17:14:02 -0000

Hello everybody,

(sorry for crossposting, but the side meeting was mentioned during today's dnsop session).

I was able to organize a bigger room - the meeting will be held in TYROLKA. Date and Time remain unchanged (Wed, 2019-03-27, 14:00-15:00)

Thanks & enjoy your evening,
Alex


Von: Alexander Mayrhofer
Gesendet: Dienstag, 26. März 2019 11:13
An: regext@ietf.org
Betreff: Security/Registry Lock Side Meeting: Wed, 14:00 - 15:00, Room Paris

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