Re: [eppext] rechartering

"Marc Blanchet" <marc.blanchet@viagenie.ca> Wed, 29 July 2015 15:21 UTC

Return-Path: <marc.blanchet@viagenie.ca>
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 780A61A89B3 for <eppext@ietfa.amsl.com>; Wed, 29 Jul 2015 08:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.311
X-Spam-Level:
X-Spam-Status: No, score=-1.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_52=0.6, 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 9E06gU_9hdur for <eppext@ietfa.amsl.com>; Wed, 29 Jul 2015 08:21:36 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE9D1A8843 for <eppext@ietf.org>; Wed, 29 Jul 2015 08:01:49 -0700 (PDT)
Received: from [206.123.31.98] (kuwa.viagenie.ca [206.123.31.98]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 7D07340221; Wed, 29 Jul 2015 11:01:51 -0400 (EDT)
From: "Marc Blanchet" <marc.blanchet@viagenie.ca>
To: "Andrew Newton" <andy@hxr.us>
Date: Wed, 29 Jul 2015 11:01:38 -0400
Message-ID: <A73C7C2E-2DA2-42C1-94A8-4C8C2DB46B8C@viagenie.ca>
In-Reply-To: <CAAQiQRdQ=3rAJFxLDcr25o+qgezGd1ceScuyj7kC5jwkh6G_vg@mail.gmail.com>
References: <CAAQiQRdBDKb8NF+d2COxTVCbx7MMtV4dsTRDSqBotq6XroHxBQ@mail.gmail.com> <20150729000315.GA30829@home.patoche.org> <CAAQiQRdQ=3rAJFxLDcr25o+qgezGd1ceScuyj7kC5jwkh6G_vg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.1r5084)
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/9SkctBFM3uMZEHrZ6mTCXaSJtNg>
Cc: Patrick Mevzek <pm@dotandco.com>, eppext <eppext@ietf.org>
Subject: Re: [eppext] rechartering
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: Wed, 29 Jul 2015 15:21:37 -0000


On 29 Jul 2015, at 7:33, Andrew Newton wrote:

> Hi Patrick,
>
…

>> At the end of the day, I think what could be used as a criteria is:
>> will this kind of merge in topics foster more work and feedback, and
>> hence going forward faster, or will it make no change?
>>
>
> I agree, that's an important question to ask. If the additional topic 
> is
> too large for this working group, that would be a bad thing. But to 
> date,
> EPPEXT has not exactly been high volume. That being said, we also 
> wouldn't
> want to derail the backlog of EPP extension work with new RDAP work 
> items.
> Therefore the proposed charter text states that the initial focus will 
> be
> EPP work.

I disagree with putting a priority in the (new) charter. I think this is 
just a triage function that can be done by the chairs, depending on 
which topic needs more priority. We may end up having epp-ext-1 and 
rdap-ext-4 be higher priorities than epp-ext-2.  Again, just a chair+wg 
triage function to me.

I also think that the level of work is not too heavy and can easily be 
handled in a single working group.

Here is a proposal for the working group name: regext  (REGistration 
protocols EXTensions)

Regards, Marc.

>
> -andy
> _______________________________________________
> EppExt mailing list
> EppExt@ietf.org
> https://www.ietf.org/mailman/listinfo/eppext