Re: Tracking IANA protocol registry changes Wed, 09 November 2016 16:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4AF871294AE for <>; Wed, 9 Nov 2016 08:41:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.399
X-Spam-Status: No, score=-3.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BLaHVU-JzC6k for <>; Wed, 9 Nov 2016 08:41:34 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6723D129491 for <>; Wed, 9 Nov 2016 08:41:34 -0800 (PST)
Received: from by (PMDF V6.1-1 #35243) id <> for; Wed, 9 Nov 2016 08:40:46 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Received: from by (PMDF V6.1-1 #35243) id <> (original mail from for; Wed, 09 Nov 2016 08:40:40 -0800 (PST)
Message-id: <>
Date: Wed, 09 Nov 2016 08:30:37 -0800
Subject: Re: Tracking IANA protocol registry changes
In-reply-to: "Your message dated Tue, 08 Nov 2016 08:34:52 -0500" <E32F9074F35CE01B441F5D46@JcK-HP8200>
References: <> <> <E32F9074F35CE01B441F5D46@JcK-HP8200>
To: John C Klensin <>
Archived-At: <>
Cc: Florian Weimer <>,
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 09 Nov 2016 16:41:36 -0000

> --On Tuesday, November 08, 2016 11:34 +0000 John Dickinson
> <> 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

> > 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.

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.