Re: [regext] DOODLE: select your documents

Alexander Mayrhofer <alexander.mayrhofer@nic.at> Thu, 03 January 2019 08:25 UTC

Return-Path: <alexander.mayrhofer@nic.at>
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 F0F72126C7E for <regext@ietfa.amsl.com>; Thu, 3 Jan 2019 00:25:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 I_M-T58z8I30 for <regext@ietfa.amsl.com>; Thu, 3 Jan 2019 00:25:27 -0800 (PST)
Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) (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 EB23C128D52 for <regext@ietf.org>; Thu, 3 Jan 2019 00:25:26 -0800 (PST)
Received: from nics-exch2.sbg.nic.at ([10.17.175.6]) by mail.sbg.nic.at with XWall v3.53 ; Thu, 3 Jan 2019 09:25:21 +0100
Received: from NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57]) by NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57%12]) with mapi id 14.03.0415.000; Thu, 3 Jan 2019 09:25:18 +0100
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: James Galvin <galvin@elistx.com>, Registration Protocols Extensions <regext@ietf.org>
Thread-Topic: [regext] DOODLE: select your documents
Thread-Index: AQHUmUgpkh9yytrCLkqYAKEagX/Al6WdQQ0g
Date: Thu, 03 Jan 2019 08:25:17 +0000
Message-ID: <19F54F2956911544A32543B8A9BDE0759FB9D141@NICS-EXCH2.sbg.nic.at>
References: <C95BDA53-5A54-42E0-A544-B6A061F073FB@elistx.com>
In-Reply-To: <C95BDA53-5A54-42E0-A544-B6A061F073FB@elistx.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.10.0.110]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-XWALL-BCKS: auto
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/Ym6mwobtkrLo9xC-s3M7aOyrrm0>
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: Thu, 03 Jan 2019 08:25:29 -0000

Jim, 

thanks for posting that - i've made my choices. 

<rant>

Sigh.

As i have voiced in the past, I see greatest value when the IETF standardizes widely used protocols, *OR* important extensions to standards track protocols. Those are the documents that directly or indirectly affect billions of internet internet users, and that's where the IETF should focus their energy on. I do believe the standardization of industry-specific file formats with a very narrow (temporal and spatial) application window, affecting only 1k-2k organizations (and ~10k individual, at most - about 6 magnitudes less!) is an extremely inefficient use of the scarce resources of the IETF, and should pursued somewhere else. Particularly since most of the regext regulars congregate at various other venues anyways.

Slapping an RFC number onto a document just so that an ecstatic crowd can commence their chant "it's an RFC!! An RFC! Arrr Efff Zeee!! You MUST implement!!" doesn't make it a "better" or  "more important" specification. 

I do believe in the value of standardization, but we should carefully select the right venues.

</rant>

Best,
Alex

> -----Ursprüngliche Nachricht-----
> Von: regext <regext-bounces@ietf.org> Im Auftrag von James Galvin
> Gesendet: Freitag, 21. Dezember 2018 17:13
> An: Registration Protocols Extensions <regext@ietf.org>
> Betreff: [regext] DOODLE: select your documents
> 
> Please take the time to select the documents you support for advancement in
> this working group.
> 
> https://doodle.com/poll/6nyguby3yr8dx9cp
> 
> Please select from 1-5 documents.
> 
> If you click once in the box a green check mark will appear.  Use this to
> indicate support for a document.  If you click twice in the box a yellow check
> mark in parentheses will appear.  You may use the yellow check mark to
> indicate support that is a lower priority than a green check mark.
> 
> For your convenience I have included the list of documents and their links
> below.
> 
> This selection process will remain open for 3 weeks, until 11 January 2019.
> 
> Enjoy your holiday season!  See you all next year!
> 
> Jim
> 
> 
> DOCUMENTS TO CONSIDER
> 
> Registry Reporting Repository
> https://datatracker.ietf.org/doc/draft-mcpherson-sattler-registry-reporting-
> repo/
> 
> Registry Reporting Structure
> https://datatracker.ietf.org/doc/draft-mcpherson-sattler-registry-report-
> structure/
> 
> Domain Fee Report
> https://datatracker.ietf.org/doc/draft-sattler-registry-domain-fee-report/
> 
> Registry Transaction Report
> https://datatracker.ietf.org/doc/draft-mcpherson-sattler-ry-transaction-
> report/
> 
> Registry Domain Inventory Report
> https://datatracker.ietf.org/doc/draft-sattler-registry-domain-inventory-
> report/
> 
> Registry Domain Drop Report
> https://datatracker.ietf.org/doc/draft-sattler-registry-domain-drop-report
> 
> Registry Unavailable Domain Report
> https://datatracker.ietf.org/doc/draft-sattler-registry-unavailable-domain-
> report/
> 
> Registry Maintenance Notifications
> https://datatracker.ietf.org/doc/draft-sattler-epp-registry-maintenance/
> 
> Unhandled Namespaces
> https://tools.ietf.org/html/draft-gould-casanova-regext-unhandled-
> namespaces
> 
> Data Set File Format
> https://datatracker.ietf.org/doc/draft-gould-regext-dataset/
> 
> Login Security
> https://datatracker.ietf.org/doc/draft-gould-regext-login-security/
> 
> Federated Authentication for RDAP
> https://datatracker.ietf.org/doc/draft-hollenbeck-regext-rdap-openid/
> 
> RDAP Partial Response
> https://datatracker.ietf.org/doc/draft-loffredo-regext-rdap-partial-response/
> 
> RDAP Search
> https://datatracker.ietf.org/doc/draft-fregly-regext-rdap-search-regex/
> 
> RDAP Reverse Search
> https://datatracker.ietf.org/doc/draft-loffredo-regext-rdap-reverse-search/
> 
> RDAP Sorting and Paging
> https://datatracker.ietf.org/doc/draft-loffredo-regext-rdap-sorting-and-
> paging/
> 
> Registry Data Escrow Specification
> https://datatracker.ietf.org/doc/draft-arias-noguchi-registry-data-escrow/
> 
> Domain Name Registration Data (DNRD) Objects Mapping
> https://datatracker.ietf.org/doc/draft-arias-noguchi-dnrd-objects-mapping/
> 
> Third Party DNS Operator to Registrar/Registry
> https://datatracker.ietf.org/doc/draft-ietf-regext-dnsoperator-to-rrr-
> protocol/
> 
> Validate
> https://datatracker.ietf.org/doc/draft-ietf-regext-validate/
> 
> Verification Code
> https://datatracker.ietf.org/doc/draft-ietf-regext-verificationcode/
> 
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext