Re: [eppext] final draft charter
pm@dotandco.com Sun, 26 July 2015 18:30 UTC
Return-Path: <patrick@shaktot.patoche.org>
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 0F4951ACD32 for <eppext@ietfa.amsl.com>; Sun, 26 Jul 2015 11:30:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 aRsghLOVBoD0 for <eppext@ietfa.amsl.com>; Sun, 26 Jul 2015 11:30:30 -0700 (PDT)
Received: from shaktot.patoche.org (shaktot.patoche.org [212.85.152.86]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 692311ACD2F for <eppext@ietf.org>; Sun, 26 Jul 2015 11:30:29 -0700 (PDT)
Received: from shaktot.patoche.org (localhost.localdomain [127.0.0.1]) by shaktot.patoche.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id t6QIUJt2005256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 26 Jul 2015 20:30:19 +0200
Received: (from patrick@localhost) by shaktot.patoche.org (8.14.3/8.14.3/Submit) id t6QIUJxS005255; Sun, 26 Jul 2015 20:30:19 +0200
Date: Sun, 26 Jul 2015 20:30:17 +0200
From: pm@dotandco.com
To: eppext <eppext@ietf.org>
Message-ID: <20150726183017.GA7334@home.patoche.org>
References: <55B0DBED.3070100@elistx.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <55B0DBED.3070100@elistx.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Scanned-By: shaktot_dot_patoche_dot_org on 212.85.152.86
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/MZ7XkkIbV2C0j_t3Bm3xZ4QTDyI>
Subject: Re: [eppext] final draft charter
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: Sun, 26 Jul 2015 18:30:32 -0000
James Galvin <galvin@elistx.com> 2015-07-23 14:22 > A charter can not be submitted for formal approval until we have a > set of milestones. Based on the discussion in the working group > meeting we have quite a set of documents to consider for working > group documents. > > The co-chairs will review this list and, for the purposes of > discussion, we will assume that all documents interested in being a > standards track specification will be included. We will create a > draft set of milestones for the working group based on including all > documents. Sorry in advance for this newbie question: as I offered some time ago, I still wish to work on some extensions that would factor out, especially for contacts, what are most often seen currently at various registries, and then hope that this would seem useful to the working group, and maybe then target standards track. With this hypothesis, should I either - hurry to publish some -00 version in order to be able to catch the first milestone list, even if the document will be far from finished - or, just work on it as I can, and ask later for inclusion to milestones, if this list can change then? Thanks in advance for your guidance, and support. -- Patrick Mevzek
- [eppext] final draft charter James Galvin
- Re: [eppext] final draft charter pm