Re: [regext] IETF 101 agenda and POSSIBLE RESCEDULING
"James Galvin" <galvin@elistx.com> Sun, 18 March 2018 20:16 UTC
Return-Path: <galvin@elistx.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 73B4712AF84 for <regext@ietfa.amsl.com>; Sun, 18 Mar 2018 13:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=elistx-com.20150623.gappssmtp.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 6Mt4CiUuTdJL for <regext@ietfa.amsl.com>; Sun, 18 Mar 2018 13:16:49 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 A8E3F12711D for <regext@ietf.org>; Sun, 18 Mar 2018 13:16:48 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id l9so2544280wmh.2 for <regext@ietf.org>; Sun, 18 Mar 2018 13:16:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=elistx-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:date:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=Tgw923JH5RLFmHEcERRGh8DADFqovkbYrDHb9vsacbs=; b=clETH++J+R2plsFpTvfaBhfTHR9+My8LKXBH9jM9nzjoE7ZiuMTQHLjP1dnvyd+Ydt cRmpf3R0xmenoG0a4Qp+FIzfgq9m5OJG0Z3sibChdtkPFdgGgsvMxwfH617M/F/hyiDO 3y5adezw/DKfj6MsUIuUyCbVyMHoAkWHZ1PICXktOREbgBL8FRTtzjRVLlEmZIIv2kHV HJUVuntq+Cs5VdrgC7+mB0rE0b7vll+zupMJzwlsnY5v5kjhveA1jjhAR5IsgitZBBg2 IitksC91q6B4/vyv9HQHpPbR0GFCQtH7TeUqNu98As2T+HyV6HMYYuFfF0sQfXxJADz3 fLzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Tgw923JH5RLFmHEcERRGh8DADFqovkbYrDHb9vsacbs=; b=EVOqJaoUSOq4jCWwldraEvuSQHYCUbmfxvF5G17jpcU3WIG0tzaNnSbMXtNjiG2f9e CCiDEBJQN4A2jQYwbls7U07H+Sdd2S6aipAW99GLh/iXBVS5DjWT+g4g8uUoO7W2g4FV rYA062YbyS47LSQKbJZ4nkED663k9+3QxHeVPlNrWj4kcIdjHNELyQgqJHoMXHuvb0pR UVL/VDVQMQmAgwerKaUTh9qPoZHpAcOu1B7NNW8q5duqhO8MMmfLFGzUf9C+8+yaurBd MxdQ4pODd+YOWE84jHYoHlv/oBRNRBpup2JlYWfJ9lSz2cwtlgSon3filHjzftk75jIo bZkA==
X-Gm-Message-State: AElRT7E4kCfP1bLr/IkmlrGZQ0dGcLROPcvhjz/luLSIvf4UhuEEaNGT dxNXhqMFkTxXvHKyjETJsZ9d4IkV/E4=
X-Google-Smtp-Source: AG47ELvzReakmMy01KbL4DmuQpi9qzal7uD2z0vUcYsN+kB8DQwb7tCwbjeFbQjeV6C6N2B5kUeBPg==
X-Received: by 10.28.191.70 with SMTP id p67mr7455471wmf.17.1521404206473; Sun, 18 Mar 2018 13:16:46 -0700 (PDT)
Received: from [31.133.145.117] ([2001:67c:1232:144:1477:179:3ba8:5e67]) by smtp.googlemail.com with ESMTPSA id 14sm12348089wml.41.2018.03.18.13.16.45 for <regext@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Mar 2018 13:16:45 -0700 (PDT)
From: James Galvin <galvin@elistx.com>
To: Registration Protocols Extensions <regext@ietf.org>
Date: Sun, 18 Mar 2018 20:16:42 +0000
X-Mailer: MailMate (1.11r5462)
Message-ID: <5375DD14-6BA5-4001-AD2E-B1F395CF63E4@elistx.com>
In-Reply-To: <847C6439-9D32-4D6B-ABAB-A4E682273F7C@antoin.nl>
References: <847C6439-9D32-4D6B-ABAB-A4E682273F7C@antoin.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/SNuTwPWpUZ8Gsu1TJQLAGabRyxk>
Subject: Re: [regext] IETF 101 agenda and POSSIBLE RESCEDULING
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 18 Mar 2018 20:16:51 -0000
I have just confirmed this evening that they have NOT moved our meeting. The published final agenda is correct. The REGEXT will meet as follows at IETF101. Monday, 1740-1840, Park Suite (east wing first floor) Wednesday, 1520-1650, Richmond/Chelsea/Tower (east wing first floor) Sorry for the confusion. Jim On 10 Mar 2018, at 15:26, Antoin Verschuren wrote: > Hi All, > > Below is our preliminary agenda for our REGEXT IETF 101 meeting that I > posted since the agenda was due. > As you can see, we only received extra items from Roger, and we still > have space left on our agenda. > > If you have any more items you wish to discuss, please let the chairs > know asap! > > Also be AWARE of the following: > We have received a request to reschedule our Wednesday 1520 regular > meeting session due to a conflict of another WG. > The workable options for rescheduling we were presented are Tuesday > 0930 or Friday 1150. > The problem of the Tuesday option is that both Adam our AD, and myself > as co-chair have a conflict on Tuesday, but Jim our other co-chair > hasn’t. > However, we feel that the Friday might be a conflict for the WG, as > the work meeting on Monday and a regular session on Friday may be too > far apart. > So we opted our first choice to reschedule to Tuesday, and I will > sacrifice my remote presence for the benefit of the WG and I will try > to follow the meeting over a low bandwidth link. > We have yet to hear which of the 2 options works best for the IETF, so > be aware we may still reschedule to Friday if that’s the only option > left. > > Preliminary agenda: > > Registration Protocols Extensions (REGEXT) > IETF 101, London, UK, Agenda > > Co-chairs: Jim Galvin, Antoin Verschuren > Mailinglist: regext@ietf.org > > ***************************************** > > Session I, Work session. > Monday 2018-03-19 17:40 - 18:40 > > Introduce the Registry Mapping concepts (Roger Carney) > This will be a discussion/work session on a new Registry mapping > proposal, > a new Policy document that describes all of the variable paths > that an > extension creates (SHOULD(s), MAY(s), lists, etc). > > ***************************************** > > ***************************************** > > Session II, Regular WG meeting session. > Wednesday 2018-03-21 15:20 - 16:50 > > > 1. Welcome and Introductions (5 minutes) > > i. Jabber scribe > ii. Notes scribe > iii. NOTE WELL > > > 2. Existing Document Status > > > 2.a. Published (2 minutes) > > i. Launch Phase Mapping for the Extensible Provisioning Protocol > RFC 8334 (was draft-ietf-regext-launchphase ) > > > 2.b. Working group (past) last call documents (15 minutes) > > i. https://datatracker.ietf.org/doc/draft-ietf-regext-epp-fees/ > (Roger Carney 10 minutes) > > ii. > https://datatracker.ietf.org/doc/draft-ietf-regext-change-poll/ > > iii. > https://datatracker.ietf.org/doc/draft-ietf-regext-allocation-token/ > > > 3. https://datatracker.ietf.org/doc/draft-ietf-regext-validate/ > (Roger Carney 10 minutes) > > > 4. Working session summary (10 minutes) > > i. Introduce the Registry Mapping concepts (Roger Carney) > > > 5. Milestone status review (Adoption requests, Renaming, Milestones) > (20 minutes) > > There are some items that can be closed on our milestone list, and > some recently > adopted documents that need to be added but we need to discuss the > priority and > maturity for them. We also want to discuss new documents to adopt. > (milestone list / adopted documents overview to be added) > > > 6. AOB > > ***************************************** > > Regards, > > Jim and Antoin > > - -- > Antoin Verschuren > > Tweevoren 6, 5672 SB Nuenen, NL > M: +31 6 37682392 > > > > > > > _______________________________________________ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext
- [regext] IETF 101 agenda and POSSIBLE RESCEDULING Antoin Verschuren
- Re: [regext] IETF 101 agenda and POSSIBLE RESCEDU… James Galvin
- Re: [regext] IETF 101 agenda Stephane Bortzmeyer