[eppext] Recharter Milestones discussion

Antoin Verschuren <ietf@antoin.nl> Fri, 04 December 2015 11:09 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 290291B300F for <eppext@ietfa.amsl.com>; Fri, 4 Dec 2015 03:09:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.982
X-Spam-Level: *
X-Spam-Status: No, score=1.982 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id QphwbaQwIwFe for <eppext@ietfa.amsl.com>; Fri, 4 Dec 2015 03:09:36 -0800 (PST)
Received: from walhalla.antoin.nl (walhalla.antoin.nl [IPv6:2a01:670:6aa4:da00::6]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC3A1B3019 for <eppext@ietf.org>; Fri, 4 Dec 2015 03:09:16 -0800 (PST)
Received: from [] (unknown []) by walhalla.antoin.nl (Postfix) with ESMTPSA id A697F280318 for <eppext@ietf.org>; Fri, 4 Dec 2015 12:09:15 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antoin.nl; s=walhalla; t=1449227355; bh=KiMkVkblXZfPmXxGlOPvvD/dqsurADdOr1TZybELyBU=; h=From:Subject:Date:To:From; b=Bwqx2P5WXzrKrgEvVnnXPHXKYwWoH2IKxqPJw0RurEWAAE+DBTxvrDhaBm9nY+iYs XXVCfwhpNZF+d8vT9a2gdbdHlS4mlNO7XmW2gJ1HlveOLSDAFV+0B4A5ZbEXFscoB5 BPnSzMz7P6QqsJLuApiPyIGdXNNOr0vD+4s+7wtU=
From: Antoin Verschuren <ietf@antoin.nl>
X-Pgp-Agent: GPGMail 2.5.2
Content-Type: multipart/signed; boundary="Apple-Mail=_C36D93AE-26D9-4565-90A1-A37F30E96B38"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Date: Fri, 04 Dec 2015 12:09:07 +0100
Message-Id: <F8238C95-4212-419A-BDE3-913E5CA6F99F@antoin.nl>
To: eppext <eppext@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/0ssXWxHjr3jWt5cMsrl9_JuX5w4>
Subject: [eppext] Recharter Milestones discussion
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: Fri, 04 Dec 2015 11:09:38 -0000

Dear Working Group,

Apologies for this late starting of this discussion.
I had intended to start this discussion some weeks ago, but I was waiting for Jim to edit the draft charter text so we could be in agreement on the draft charter text and the milestones at the same time. Jim is very busy and didn’t get around to that yet, so as sugested by Linlin, let’s start the discussion on the proposed milestones and have that item concluded on.

Below you will find the list of proposed milestones.
I have reordered them based on our discussion in Yokohama.

What we would like to hear from the WG is if this list of milestones is accepted.
To order the discussion, comments can be made:
-Either on a specific document not to be in the milestones list so it will not become a WG item.
-Discussion on priority or grouping, but then there needs to be consensus on which documents to exchange in the priority because we cannot work on all documents at the same time.

To be clear:
-All of the documents on this list will become WG documents.
-As discussed in Yokohama, this WG focusses on Standards track documents, but at the WG request, we can review Informational documents, and the nv mapping draft in one such example where the authors have requested WG review.
-The order and priority can be changed in the future, but this is the initial order in which we think work can be done.
-There is room for new evolving documents to be added later.


The proposal is to create a set of groups of our documents, order
those groups, and then create milestones for each group.

As a starting point for discussion there is a set of documents already
active and the rest have been distributed into 4 sets.

Here is the proposed set of milestones.  It is based on the model of 3
months per group.

Active Now

- WGLC completed by December 2015
- Submit for publication January 2016

Group 1

- WGLC completed by February 2016
- Submit for publication March 2016

Group 2

- WGLC completed by May 2016
- Submit for publication June 2016

Group 3

- WGLC completed by September 2016
- Submit for publication October 2016

Group 4

- WGLC completed by January 2017
- Submit for publication February 2017

Here is the proposed groupings of the documents.

Active now



Group 1

-epp-rdap mapping (draft-gould-epp-rdap-status-mapping)
-verification code (draft-gould-eppext-verificationcode)
-nv mapping (draft-xie-eppext-nv-mapping)(Remains as Informational, but reviewed by WG)

Group 2

-reseller (draft-zhou-eppext-reseller and draft-zhou-eppext-reseller-mapping)
-allocation token (draft-gould-allocation-token)
-change poll (draft-gould-change-poll)

Group 3

-fees (draft-brown-epp-fees-05)
-bundling (draft-kong-eppext-bundling-registration)

Group 4

-IDN Table Mapping (draft-ietf-eppext-idnmap and draft-gould-idn-table
 and draft-wilcox-cira-idn-eppext)
-Relay (no draft yet, split from keyrelay)

Please send feedback to the list on these proposed milestones before December 25, so we can conclude our new charter and milestones before the end of this year.


Jim and Antoin

- --
Antoin Verschuren

Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392