Re: [eppext] rechartering
Frederico A C Neves <fneves@registro.br> Wed, 29 July 2015 14:09 UTC
Return-Path: <fneves@registro.br>
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 595CE1A1BF3 for <eppext@ietfa.amsl.com>; Wed, 29 Jul 2015 07:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.662
X-Spam-Level:
X-Spam-Status: No, score=-4.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, RCVD_IN_DNSWL_HI=-5, 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 4Qy1zHkA_LnW for <eppext@ietfa.amsl.com>; Wed, 29 Jul 2015 07:09:43 -0700 (PDT)
Received: from clone.registro.br (clone.registro.br [200.160.2.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82D851A1BDD for <eppext@ietf.org>; Wed, 29 Jul 2015 07:09:43 -0700 (PDT)
Received: by clone.registro.br (Postfix, from userid 1000) id 4C79324BED8; Wed, 29 Jul 2015 11:09:41 -0300 (BRT)
Date: Wed, 29 Jul 2015 11:09:41 -0300
From: Frederico A C Neves <fneves@registro.br>
To: Andrew Newton <andy@hxr.us>
Message-ID: <20150729140941.GJ30553@registro.br>
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"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAAQiQRdQ=3rAJFxLDcr25o+qgezGd1ceScuyj7kC5jwkh6G_vg@mail.gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/yFFrbbI9FXHWxSvXRjqGgq6LT34>
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 14:09:45 -0000
On Wed, Jul 29, 2015 at 07:33:14AM -0400, Andrew Newton wrote: > Hi Patrick, > > > On Tue, Jul 28, 2015 at 8:03 PM, Patrick Mevzek <pm@dotandco.com> wrote: > > > - EPP is now an "old" protocol, used by all gTLDs, and many ccTLDs > > registries ; AFAIK it is not used outside of the domain name > > business, and seldom used outside of domain name registries; there is > > no clear indication of any work, outside of technical areas, to try > > improving EPP, for example by reducing the number of extensions, > > forcing registries to implement some of them, etc… I agree that there is very little to no incentive at all to combine/merge old EPP extensions in production but for new work the proposed "combined" charter seems attractive to me. We should leverage as much as we can the history/experience on not spreading enough the word and not exposing proposed extensions enough before they get ossified on agreements and production systems. Focusing the work in a single place is a good way of achieving this. > I believe that both LACNIC and NIC.br, which in addition to being a ccTLD > is also an NIR, use EPP. Yes. NIC.br and NIC.mx, both NIRs, integrates to the LACNIC system since Feb 2013 using the following extensions, ftp://ftp.registro.br/pub/libepp-nicbr/draft-neves-epp-asn-02.txt ftp://ftp.registro.br/pub/libepp-nicbr/draft-neves-epp-ipnetwork-02.txt Besides of the NIR/RIR integration, LACNIC also provides this EPP interface for direct customers. ... > > 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. +1 > -andy Fred
- [eppext] rechartering Andrew Newton
- Re: [eppext] rechartering Marc Blanchet
- Re: [eppext] rechartering Hollenbeck, Scott
- [eppext] Fwd: rechartering Andrew Newton
- Re: [eppext] [weirds] Fwd: rechartering Ulrich Wisser
- Re: [eppext] [weirds] Fwd: rechartering Roger D Carney
- Re: [eppext] [weirds] Fwd: rechartering Andrew Newton
- Re: [eppext] rechartering Patrick Mevzek
- Re: [eppext] rechartering Rik Ribbers
- Re: [eppext] rechartering Andrew Newton
- Re: [eppext] rechartering Andrew Newton
- Re: [eppext] rechartering Rik Ribbers
- Re: [eppext] rechartering Frederico A C Neves
- Re: [eppext] rechartering Marc Blanchet
- Re: [eppext] rechartering Hollenbeck, Scott
- Re: [eppext] rechartering Andrew Newton
- Re: [eppext] rechartering Marc Blanchet
- Re: [eppext] rechartering Patrick Mevzek