Re: [eppext] rechartering

"Hollenbeck, Scott" <shollenbeck@verisign.com> Wed, 29 July 2015 15:42 UTC

Return-Path: <shollenbeck@verisign.com>
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 47C911A8829 for <eppext@ietfa.amsl.com>; Wed, 29 Jul 2015 08:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_LOW=-0.7] 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 QjsCXW2LuTy0 for <eppext@ietfa.amsl.com>; Wed, 29 Jul 2015 08:42:16 -0700 (PDT)
Received: from mail-oi0-f98.google.com (mail-oi0-f98.google.com [209.85.218.98]) (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 5A59F1A8825 for <eppext@ietf.org>; Wed, 29 Jul 2015 08:42:16 -0700 (PDT)
Received: by oiho132 with SMTP id o132so641883oih.2 for <eppext@ietf.org>; Wed, 29 Jul 2015 08:42:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:content-transfer-encoding :mime-version; bh=Garz8UhZ2NGdbW30v4x/KOB88mVauUHI1HNvxDnyBPA=; b=Ho8HG2oQo6LCWdathPPyHqUGVLUo+BcdbjJd5Uod25oj2cwKV5U7Rev7o6a/5SXnaT GCMVR94PRnSWnN3X96AjX3C8uUp2NFZhATdYLjk8uXycfMkJUL9x+c75r9mSe0lJGqqb n+LgYovHH1sFv41mjGkxeE2H0bSBJwOkGEu49kFuFdrAhRICFtNifhMg5fUD+l/NidPa mDtQYQaYEaPGwM6nfSzlcFNNZTAKfGIaL7A8ncZAefmR0CV51o0joMpd152mqh7xau/Y t803BvGloLI2zBb8NS89gvVdMPEGmY5HbsDL9r0B0qS4YagzTX9R2KPb6frX6UrvtQY0 eaIg==
X-Gm-Message-State: ALoCoQkvVQG7yvIosGRuAWv22BbSgsQAv/SQ1R5VD6NN7PQrDvMQodcoJuGof3c1ws90zOBU2hlGqBn2Ca5SUBoCU4sfbsrsog==
X-Received: by 10.55.24.219 with SMTP id 88mr63304150qky.54.1438184535786; Wed, 29 Jul 2015 08:42:15 -0700 (PDT)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id p9sm7956236qkh.2.2015.07.29.08.42.15 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 29 Jul 2015 08:42:15 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id t6TFgEd3026332 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Jul 2015 11:42:14 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Wed, 29 Jul 2015 11:42:14 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Marc Blanchet <marc.blanchet@viagenie.ca>, Andrew Newton <andy@hxr.us>
Thread-Topic: [eppext] rechartering
Thread-Index: AQHQyJkPFHZ2BhIbnkKLXgSzziciwp3yk1sngAAFltA=
Date: Wed, 29 Jul 2015 15:42:13 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A04277E@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <CAAQiQRdBDKb8NF+d2COxTVCbx7MMtV4dsTRDSqBotq6XroHxBQ@mail.gmail.com> <20150729000315.GA30829@home.patoche.org> <CAAQiQRdQ=3rAJFxLDcr25o+qgezGd1ceScuyj7kC5jwkh6G_vg@mail.gmail.com> <A73C7C2E-2DA2-42C1-94A8-4C8C2DB46B8C@viagenie.ca>
In-Reply-To: <A73C7C2E-2DA2-42C1-94A8-4C8C2DB46B8C@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/CPk7jDl7jKuIzFvMJCMjJoXXRy4>
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:42:18 -0000

> -----Original Message-----
> From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Marc
> Blanchet
> Sent: Wednesday, July 29, 2015 11:02 AM
> To: Andrew Newton
> Cc: Patrick Mevzek; eppext
> Subject: Re: [eppext] rechartering
> 
> 
> 
> 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)

I like that...

Scott