Re: Tracking IANA protocol registry changes
John C Klensin <john-ietf@jck.com> Tue, 08 November 2016 13:35 UTC
Return-Path: <john-ietf@jck.com>
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 31754129BC0 for <ietf@ietfa.amsl.com>; Tue, 8 Nov 2016 05:35:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.397
X-Spam-Level:
X-Spam-Status: No, score=-3.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497] 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 O4hhMKc6ULsF for <ietf@ietfa.amsl.com>; Tue, 8 Nov 2016 05:34:59 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2BF71296E8 for <ietf@ietf.org>; Tue, 8 Nov 2016 05:34:59 -0800 (PST)
Received: from [198.252.137.10] (helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1c46YE-000LuF-0A; Tue, 08 Nov 2016 08:34:58 -0500
Date: Tue, 08 Nov 2016 08:34:52 -0500
From: John C Klensin <john-ietf@jck.com>
To: John Dickinson <jad@sinodun.com>
Subject: Re: Tracking IANA protocol registry changes
Message-ID: <E32F9074F35CE01B441F5D46@JcK-HP8200>
In-Reply-To: <2F8640D5-0CF1-4DFB-906A-B951665ABACE@sinodun.com>
References: <877f8eusek.fsf@mid.deneb.enyo.de> <2F8640D5-0CF1-4DFB-906A-B951665ABACE@sinodun.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_ZUEvh6WET8sOxZ4NAZsXAYufMc>
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: Tue, 08 Nov 2016 13:35:01 -0000
--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). I would like a query mechanism as well as a > subscription. Take this up with ICANN -- not an IETF problem. Rhetorical question, please do not clutter up this list with an answer: Out of curiosity, what would you be prepared to pay for such services, which would involve both development and ongoing costs, however small? Or are you somehow entitled to free lunches? Note, too, that IANA staff, especially staff associated with the TLD registry, do not work for the IETF and may not carefully follow this list. If you want to contact them, try iana@iana.org. john
- Tracking IANA protocol registry changes Florian Weimer
- Re: Tracking IANA protocol registry changes John Dickinson
- Re: Tracking IANA protocol registry changes John C Klensin
- Re: Tracking IANA protocol registry changes S Moonesamy
- Re: Tracking IANA protocol registry changes Michelle Cotton
- Re: Tracking IANA protocol registry changes Marco Davids (Private)
- Re: Tracking IANA protocol registry changes Eggert, Lars
- Re: Tracking IANA protocol registry changes Julian Reschke
- Re: Tracking IANA protocol registry changes Emily Shepherd
- Re: Tracking IANA protocol registry changes Eggert, Lars
- Re: Tracking IANA protocol registry changes ned+ietf
- Re: Tracking IANA protocol registry changes Julian Reschke