Re: [regext] DOODLE: select your documents

"Patrick Mevzek" <pm@dotandco.com> Fri, 11 January 2019 08:04 UTC

Return-Path: <pm@dotandco.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDEED12DD85 for <regext@ietfa.amsl.com>; Fri, 11 Jan 2019 00:04:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dotandco.com header.b=e8SNh6zg; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=aU8ZtxY2
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 GW2expnAj68c for <regext@ietfa.amsl.com>; Fri, 11 Jan 2019 00:04:13 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD40B128D09 for <regext@ietf.org>; Fri, 11 Jan 2019 00:04:12 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A0A3B22037 for <regext@ietf.org>; Fri, 11 Jan 2019 03:04:11 -0500 (EST)
Received: from imap1 ([10.202.2.51]) by compute3.internal (MEProxy); Fri, 11 Jan 2019 03:04:11 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dotandco.com; h= message-id:in-reply-to:references:date:from:to:subject :content-type; s=fm1; bh=uWME7iYQHTRBzJWMr2rO3ya6uEBRC6N05PRsp5U wN/o=; b=e8SNh6zgc7RmVODwbJGJn7osBh2XV7viFjY0iKBiX3K64B3ENVt/WeM X/njDtQ/uEQzOlKdZ8Cci2OFZSaqTordG1NI/R2sip8t9H+IacpxLjODwcaEZkl0 ac4EdSB11prSbZnnqQClSoUYbIcK9sdSXr821VweUDmyZM7gV66dmjXZ34NSJVpC fRbdH3E8h90R74whKDV0FrA9afA3gxJaBk2C4vyTlTqpLB097RjJvyqdhSUNgAUN LfW0T+bGZIOFUgFy+sKWOXXnKxg4sNXHDubKzhIw159lH8mHX2df6EtGWN9MH97z fSGqfU/5l2Nn+DKrAitPl3I3OSb3dIw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:references:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=uWME7iYQHTRBzJWMr 2rO3ya6uEBRC6N05PRsp5UwN/o=; b=aU8ZtxY2iQj98KDt91hyX+0mhorsdXHa1 EysL/1jvODaTc8bXF/G8qNbbXuE0xRPGJHppMmhvms1XmrBffMulMmb00lV/KAT8 OfhrB3sdOjVDYDdssTsCkgBo9TgMRobg3g632ZGC4waoP1DvoiAH2m6CoM8U0Z3W 7kg7cFIaBCNUCBEsE2Y+skvBSe+tsVo4kAsB9eiTaRGDsnTZKMNpxq+kOG8rIIVQ JlPKjQAul1CIi/ANWQdzBfiNCZ+TI9j/N9ujhEnrG5zH8jMqakJ5RQMhrw4LKzn6 Skii63iiqfyQcG1RTpwuffJXf4yaRd4PaKo65eqjqzAbI2SNDfZ/Q==
X-ME-Sender: <xms:-004XH59XOOIC29Y_2J67DrXJJEcfwoCWK2125kCx5ilyyJ3P2ihfon-LEw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrfeeggdduudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecunecujfgurhepofgfkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpe dfrfgrthhrihgtkhcuofgvvhiivghkfdcuoehpmhesughothgrnhgutghordgtohhmqeen ucfrrghrrghmpehmrghilhhfrhhomhepphhmseguohhtrghnuggtohdrtghomhenucevlh hushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:-004XNoAH9ZdLX42sLW3AsHEyCCxz8hKdadOLNm_uq-jEpd1tSmHoQ> <xmx:-004XCR45G5x6mSFjLjSw7lW1HFT7HajEZYlUJOFu1xzC6vnFqIkhQ> <xmx:-004XJstgc4HUdHufbwdCjhjaRKoXxAzQVrwFecoLA3w8VC8behZ3w> <xmx:-004XN0jVgsW5qRSErUAHHjtMTfsGauHiUSWrB5yqfbGG60L6BRisw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3835ED459A; Fri, 11 Jan 2019 03:04:10 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.5-739-g7452a1e-fmstable-20190103v1
X-Me-Personality: 66173168
Message-Id: <93324b73-fcc8-47e1-930d-e85a534735c5@www.fastmail.com>
In-Reply-To: <19F54F2956911544A32543B8A9BDE0759FB9D141@NICS-EXCH2.sbg.nic.at>
References: <C95BDA53-5A54-42E0-A544-B6A061F073FB@elistx.com> <19F54F2956911544A32543B8A9BDE0759FB9D141@NICS-EXCH2.sbg.nic.at>
Date: Fri, 11 Jan 2019 03:04:09 -0500
From: Patrick Mevzek <pm@dotandco.com>
To: regext@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/k7uFXKguKhhff4jA2bfXLJt4vRc>
Subject: Re: [regext] DOODLE: select your documents
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2019 08:04:15 -0000

Hello Alexander,

On Thu, Jan 3, 2019, at 03:25, Alexander Mayrhofer wrote:
> Jim, 
> 
> thanks for posting that - i've made my choices. 
> 
> <rant>

For the record, I share most if not all of your rant Alexander.

1) I am sad to see this working group and the IETF being a rubberstamp for documents discussed elsewhere and coming here explicitely as stated just to get an RFC number.
This is wrong on so many levels and could even be seen as an abuse of IETF.
I do not think the working group should put time and energy on those documents. In most cases they can as well be an individual submission or just stay as a specification added
to the EPP Extension registry.
If people decided to work on them in other venues, then they should just finish "standardization" of them in those other venues, switching to the IETF at the last minute just for an RFC number is certainly not the expected way to work.

The aim of the working group in my mind is to try defining extension that works for
the widest use cases possible accross many registrars and registries. The community is not so big so splitting work in many venues even lowers the chance the results will have enough reviews to make them as generic and globally useful as possible.

Like Alexander stated, the impact of each specification (does it concern one specific case or is it useful for all EPP servers in the world) could or should be taken into account when deciding to work on X instead of Y.

Otherwise we get only a very thin short time frame gain of having RFC for numerous "standardized" extensions where no real consensus will exist on them, some will overlap or even contradict themselves which will in the long term make the current situation regarding deployed extensions on servers even more complex that it is nowadays (and it is complex enough), hence making registrars even more complicated which in turn constrains registries to not be able to easily run new services because registrars will not implement them, etc.

2) I would have much prefered seeing people coming on this exact mailing-list and stating that they will support such and such documents by promising to work on them (reviewing, implementing, etc.) instead of an anonymous poll done on a remote site, whose results are difficult to interpret (is it interest in something being done? willingness to work on it? just showing that is seems to be important without any real interest in it? etc.). That would have shown real community support for some documents and provide a clear proof of interests later on for shepherd reviews and IETF-wide LC.

For all these reasons I voluntarily did not participate in this polling, even if I clearly have my opinion on which documents are most useful to work on than others and which should get the WG attention or not.

That is the end of my rant.

-- 
  Patrick Mevzek
  pm@dotandco.com