Re: [eppext] revised draft charter - v2
Edward Lewis <edward.lewis@icann.org> Mon, 31 August 2015 13:16 UTC
Return-Path: <edward.lewis@icann.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 573311B473B
for <eppext@ietfa.amsl.com>; Mon, 31 Aug 2015 06:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.431
X-Spam-Level:
X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779,
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 LQy2i4QP95bi for <eppext@ietfa.amsl.com>;
Mon, 31 Aug 2015 06:16:39 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org
[64.78.40.10])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 7B6E31B473C
for <eppext@ietf.org>; Mon, 31 Aug 2015 06:16:39 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by
PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server
(TLS) id 15.0.1044.25; Mon, 31 Aug 2015 06:16:35 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by
PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id
15.00.1044.021; Mon, 31 Aug 2015 06:16:35 -0700
From: Edward Lewis <edward.lewis@icann.org>
To: "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: [eppext] revised draft charter - v2
Thread-Index: AQHQ4dgotzrKbgDz4kiJHJmKV5Edw54mbv0AgAAbuAD//8JkAA==
Date: Mon, 31 Aug 2015 13:16:34 +0000
Message-ID: <D209C95E.E92F%edward.lewis@icann.org>
References: <55E0D247.2020408@elistx.com>
<C80127C588F8F2409E2B535AF968B768BA233E3B@kambx1.SIDN.local>
<5BFD186DCB661E4D951017B0818285AEDE761E65@kambx1.SIDN.local>
In-Reply-To: <5BFD186DCB661E4D951017B0818285AEDE761E65@kambx1.SIDN.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.4.150722
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature";
micalg=sha1; boundary="B_3523857390_16139476"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/AijVmorLjtBUFnJ3CwIJq_MRgcs>
Cc: 'James Galvin' <galvin@elistx.com>
Subject: Re: [eppext] revised draft charter - v2
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: Mon, 31 Aug 2015 13:16:41 -0000
The practices of operating a registry have been evolving over the past 15 years. Getting PROVREG chartered was a challenge back in 2000, as the IETF felt that EPP wasn't a topic for the organization. As soon as EPP's first round of documents were approved, the WG was shutdown and the PROVREG mail list continued in sort of a vacuum as the industry grew around EPP, this was the root (or a root) cause of why EPPEXT came about. I think having a registry-industry focused extensions WG is a good idea. I'd float the request to pull in documents on data escrow of registry data as well as documents related to trademark clearing house. There are documents related to those two functions already in the IETF floating in individual submission space. Two questions that come to mind are: Would creating a registry-as-a-specific-function WG be something new to the IETF? (I.e., precedent-setting?) And would this be better placed in O&M? The former is a question from what I recall was the stumbling block back in 2000. As much as I think there is a need for documenting how registries work - without unifying in any way - so that ideas can be shared, etc., I hope that the IETF is willing to take this on as a WG. I'll add - I don't see registries continually evolving over time, past a point of maturity. So a WG would have a limited lifetime, not an on-going, ever-expanding function. On 8/31/15, 8:57, "EppExt on behalf of Marc Groeneweg" <eppext-bounces@ietf.org on behalf of Marc.Groeneweg@sidn.nl> wrote: >+1 > >I agree to extend the EPPEXT with possible extensions to the RDAP >protocol. And please do forward the eppext, provreg and weirds mail to a >new regext list. > >Regards, >Marc Groeneweg > >-----Original Message----- >From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Rik Ribbers >Sent: maandag 31 augustus 2015 13:18 >To: 'James Galvin'; eppext@ietf.org >Subject: Re: [eppext] revised draft charter - v2 > >+1 for the charter text > >One question. If we are creating aliases for mailingllist should we >consider the provreg mailing list? Then at least all EPP mailing lists I >am aware of are relayed to on place. > >Gr, >Rik > >-----Original Message----- >From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of James Galvin >Sent: vrijdag 28 augustus 2015 23:28 >To: eppext >Cc: Barry Leiba >Subject: [eppext] revised draft charter - v2 > >There were two suggestions on the list for extending the charter. One >seemed to suggest being the home for all protocol extensions. A second >was to focus on just RDAP and EPP extensions. > >I believe the restriction to just RDAP and EPP had more support. There >were a few people who suggested they didn't really want to join the two >protocols but they also said they would not object to joining them. I >counted this as support for the merge. > >Marc Blanchet proposed a new name of REGistration protocols EXTensions >(REGEXT). There were no objections so I adopted it in this revised draft. > >Here is a draft for consideration by the working group. I have not yet >added milestones, which are necessary before submitting this to the IESG >for review. I also have to finish reviewing the discussion for the 3 >documents in WGLC so I can make sure to include them appropriately in >this charter. > >Please comment on this charter and suggest milestones for inclusion by >Friday, 4 September 2015. > >Jim >_______________________________________________ >EppExt mailing list >EppExt@ietf.org >https://www.ietf.org/mailman/listinfo/eppext > >_______________________________________________ >EppExt mailing list >EppExt@ietf.org >https://www.ietf.org/mailman/listinfo/eppext
- [eppext] revised draft charter - v2 James Galvin
- Re: [eppext] revised draft charter - v2 Barry Leiba
- Re: [eppext] revised draft charter - v2 James Galvin
- Re: [eppext] revised draft charter - v2 Andrew Newton
- Re: [eppext] revised draft charter - v2 Hollenbeck, Scott
- Re: [eppext] revised draft charter - v2 Hollenbeck, Scott
- Re: [eppext] revised draft charter - v2 Rik Ribbers
- Re: [eppext] revised draft charter - v2 Roger D Carney
- Re: [eppext] revised draft charter - v2 Rik Ribbers
- Re: [eppext] revised draft charter - v2 Marc Groeneweg
- Re: [eppext] revised draft charter - v2 Edward Lewis
- Re: [eppext] revised draft charter - v2 Linlin Zhou
- Re: [eppext] revised draft charter - v2 Peter Koch
- Re: [eppext] revised draft charter - v2 Edward Lewis