Re: Tracking IANA protocol registry changes

Julian Reschke <julian.reschke@gmx.de> Wed, 09 November 2016 16:57 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AB1012946E for <ietf@ietfa.amsl.com>; Wed, 9 Nov 2016 08:57:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-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 SjQ3SDQSWw7P for <ietf@ietfa.amsl.com>; Wed, 9 Nov 2016 08:57:53 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04720129417 for <ietf@ietf.org>; Wed, 9 Nov 2016 08:57:52 -0800 (PST)
Received: from [192.168.178.20] ([93.217.118.38]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MC4VE-1bvkkQ01fk-008nle; Wed, 09 Nov 2016 17:57:34 +0100
Subject: Re: Tracking IANA protocol registry changes
To: ned+ietf@mauve.mrochek.com, John C Klensin <john-ietf@jck.com>
References: <877f8eusek.fsf@mid.deneb.enyo.de> <2F8640D5-0CF1-4DFB-906A-B951665ABACE@sinodun.com> <E32F9074F35CE01B441F5D46@JcK-HP8200> <01Q73VC2AP74011H9Q@mauve.mrochek.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <adb54fae-5ff3-86f4-dc98-37351123106c@gmx.de>
Date: Wed, 9 Nov 2016 17:57:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <01Q73VC2AP74011H9Q@mauve.mrochek.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:fvDMyU2ctXbf6eNGVS3KbnaBCkJ6YD9RzG9Xne0jaYd4oPhP86o +cndJMMEuZsZyV/bq9bpDOefR6gMHrAfKJzQBPZOoDniw1zTi8Lp/VoJpnmCsMMQvEh9QGt gN+o14Cf79IhM/OaNUwfbdL/kIsD8EdwdpRb13u6xYyajtA3Yti7Ub8ej6u/KGYhsE/c5C+ gYuxnQnTsSDpRkHY8N+zw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:SG8GOx9tSzI=:qUTllc27/vpZQgT6rTA1mK IPU4qN/3IxhRF/xCvlDP74jWUAIvSaIvDx2S8Jj16GM5l7gsXQO4DGfXxOdpqy5muPMmx9jxD N1cEFXujvfL1wQgdNOcO3FxQjgyvPXSLv3RC+bVztS/cwLo3TDv1nwUKwSNCFuU3ZL7lffUAu 8/9Fh75x6XDMHuL3OQsBEG4+lsocb4pcwTzyVeuorC280a3EoAAFbs0U2zqJ5Q6SVwCQZGWZY P3Ua+kECjNEa/BUehwODJZpD+lpTnxV39vBz3jvyPSE1MNYK4Z4vCXlw0B2XFwQuoSw1Hfwv0 hvlgZQ4v0GA8r4WrDbvzEkamZoNP5TA9kf2qlksGppZn62fYcK+NQdW03TqZCPDr3/K0jzOE6 hkab0iIZGobQidvBqNoO5Nu27TarYM+qrRRbIqkwTFtu39mhExvmQK37uHfiAvL/eWgGYz1lr O9yIohAQt11aFKiF9wru7u70fIPp7dHpBTYboaE3lXsep//oPQqOCIzduByJn0sGeSz32dMGX tb0pGBtXFOh7QF7bEzWkaEUNkAir45uEwHj6ZEg2SKcbV8Jl9tpaEmzasAv+PbGHC8zGqGqLb c0MJdqiNfTNe5bcswWn1YJ417l1H0/7fBiTsFDh+/Cjo7SigTbfYeHQXJv+0oGROS069UuwXP kzQ3jWepVb9NVBI3NQeZTy6qFQx3qpiQA5oPhKpqbk/Su4PIWlUKcvxyNRzmX51hUb5QWtk/j gm/Zixg/Z/WRwG16rBhcXm0va/TBZXsieBHtnppb8H8j4pwTcBEhl6ZUYzOVZcUMJKh6zMczn rPjZOBC
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8oly3vYBFC0u4HR_Fo8tRIoV8UU>
Cc: Florian Weimer <fw@deneb.enyo.de>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2016 16:57:55 -0000

On 2016-11-09 17:30, ned+ietf@mauve.mrochek.com wrote:
>
>
>> --On Tuesday, November 08, 2016 11:34 +0000 John Dickinson
>> <jad@sinodun.com>; wrote:
>
>>> ...
>>> I would also like to see some visibility into the registries
>>> and things like new TLD's (grouped by type and sorted by
>>> date of entry).
>
> Given that ICANN regularly updates a single file list of TLDs, this
> isn't too hard to automate. (Not that this should be necessary, mind you.)
>
> Of course this doesn't extend to registries. There are too many of them
> and too much complexity as to their structure to make remote automation
> viable.
>
>>> I would like a query mechanism as well as a
>>> subscription.
>
>> Take this up with ICANN -- not an IETF problem.
>
> I'm afraid I'm going to have to disagree here. The IETF, as a user/consumer of
> the registry services IANA/ICANN provides, most definitely should have a say in
> the capabilites of the interface to those services. (In fact I believe the IETF
> was involved in if not the instigator of the push to make registry data
> available in structured form.)
>
> As such, I think it's perfectly legitimate to ask why the IETF isn't
> collectively asking IANA to provide registry creation and update notifications.
>
> And I have to say it's a bit embarassing that there's no way to get, say,
> an RSS feed out of IANA. Something I get for free from most content
> management software these days - in fact in many cases it's on by default.

+1

> Of course it's possible that there's no consensus in the IETF that this
> is an issue worth worrying about. But determining that requires discussion.

+1

Best regards, Julian