Re: [eppext] Agenda items for Yokohama?

Antoin Verschuren <ietf@antoin.nl> Tue, 22 September 2015 09:58 UTC

Return-Path: <ietf@antoin.nl>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 952681A1B4B for <eppext@ietfa.amsl.com>; Tue, 22 Sep 2015 02:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.083
X-Spam-Level:
X-Spam-Status: No, score=0.083 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 leYp8U3SGBUu for <eppext@ietfa.amsl.com>; Tue, 22 Sep 2015 02:58:08 -0700 (PDT)
Received: from walhalla.antoin.nl (walhalla.antoin.nl [88.159.164.218]) by ietfa.amsl.com (Postfix) with ESMTP id 7F0E21A1B44 for <eppext@ietf.org>; Tue, 22 Sep 2015 02:58:08 -0700 (PDT)
Received: from [192.168.0.114] (unknown [192.168.0.1]) by walhalla.antoin.nl (Postfix) with ESMTPSA id 9012C280186 for <eppext@ietf.org>; Tue, 22 Sep 2015 11:58:07 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antoin.nl; s=walhalla; t=1442915887; bh=OzM+YH2QQIGp8GW2rDFH0DzLI+gYElj5qxNsQj+jxo4=; h=Subject:From:In-Reply-To:Date:References:To:From; b=fMcPo0p1568KNqz0kIlOF1RLeL6mfYKmDwSXG1bz8h/j1uYvkPFrg/oCy0KxWc5is YW7bGhqk4aKy52pFoR/uFzvNa67u4MfbX99u5HJgxcVnpr1KYjNeMwtkrd9uMnwtVn 2oPyzNhWGh4hrb1qM3aUep+7pZ1lGggGfjPWvtzs=
Content-Type: multipart/signed; boundary="Apple-Mail=_69CC98C2-3E77-4AD6-A93A-2CA2BE470D72"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Pgp-Agent: GPGMail 2.5.1
From: Antoin Verschuren <ietf@antoin.nl>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4A09B08A@BRN1WNEXMBX02.vcorp.ad.vrsn.com>
Date: Tue, 22 Sep 2015 11:57:57 +0200
Message-Id: <FB0DF608-2762-41AB-9CE7-DBB99A25C4FE@antoin.nl>
References: <831693C2CDA2E849A7D7A712B24E257F4A084A1A@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <C11E5411-FB92-44E1-9D1F-19DDE978F31E@cnnic.cn> <CAJ9-zoVYe3ZmKXx1aAf4rQVXyFbm-9M488=QuqENjFtdqwPVPQ@mail.gmail.com> <C80127C588F8F2409E2B535AF968B768BA25A0FC@kambx2.SIDN.local> <F246B83F-0F86-44A4-8184-A670A305C26A@antoin.nl> <831693C2CDA2E849A7D7A712B24E257F4A09B08A@BRN1WNEXMBX02.vcorp.ad.vrsn.com>
To: "eppext@ietf.org" <eppext@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/ZNgC3bJO6VPwi8Nk2rZ95TxYv0A>
Subject: Re: [eppext] Agenda items for Yokohama?
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2015 09:58:11 -0000

Op 21 sep. 2015, om 13:09 heeft Hollenbeck, Scott <shollenbeck@verisign.com> het volgende geschreven:

> Antoin, I'd very much like to know what's happening with our re-charter discussion and the documents that have been WG-last-called with no further progression (draft-ietf-eppext-tmch-smd, draft-ietf-eppext-launchphase, draft-ietf-eppext-keyrelay). These might not be agenda items, but if not they should be clearly addressed before we meet.

Hi Scott, all,

So a small update from our action items.

Jim and I have requested a 2 hour slot for Yokohama.
Please send in agenda items so I can send out a proposed agenda later this week.

The recharter discussion will certainly be on our agenda.
Jim has sent a revised charter text for REGEXT that most of the WG seemed to agree with.
The only thing left to do there is a list of milestones. I have provided Jim with a list of documents that potentially fall into our charter, and Jim will send out the revised charter including the milestones later this week. The list of milestones is more or less the list of proposed candidate documents discussed in Prague (https://tools.ietf.org/wg/eppext/minutes?item=minutes-93-eppext.html), so if you want to talk about one of them, please send an agenda item.

As for the documents in our current charter:
We have document shepherds for 2 documents:

-draft-ietf-eppext-tmch-smd
The document shepherd for this document is Ning Kong.
There were 2 minor nits in Ning’s proposed writeup that he has corrected after I had some issues with my mail. That delay was completely my fault.
Ning has submitted his shepherd writeup to the data tracker earlier this week, and I will send the document to the IESG later this week.

-draft-ietf-eppext-keyrelay
The document shepherd for this document is Ulrich Wisser.
Ulrich has provided us with a writeup already some weeks ago.
Since I have double hats on this document, I will stay neutral in the approval process, and Jim will give feedback to Ulrich and the authors.
There are 2 minor nits still here, where Jim needs to coordinate with Ulrich and the authors:
-One minor nit in the writeup (Jim will correct/contact Ulrich)
-One minor nit in the document itself with regards to an error of the initials of the authors caused by pandoc2rfc.
I have contacted Rik: Please correct the initials and provide a 09 version of the document.

-draft-ietf-eppext-launchphase
This document does not have document shepherd yet because we felt in Prague that this one is not ready yet.
We will move this one to our revised new charter.

So in summary:
All but one document from EPPEXT will be sent to the IESG before Yokohama which means most of our work there is done.
One document will be carried along to our new REGEXT charter to be finished there.

- --
Antoin Verschuren

Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
xmpp:antoinverschuren@gmail.com