From each@isc.org  Mon Nov 30 21:05:21 2015
CC: 
MIME-Version: 1.0
In-Reply-To: <rt-4.2.8-15470-1448915040-790.41202-4-0@isc.org>
Content-Disposition: inline
X-RT-Interface: API
References: <RT-Ticket-41202@isc.org> <20151130190536.GA28613@mycre.ws> <rt-4.2.8-15470-1448910416-485.41202-3-0@isc.org> <20151130202356.14C3A3DC5BEF@rock.dv.isc.org> <rt-4.2.8-15470-1448915040-790.41202-4-0@isc.org>
Message-ID: <20151130210521.GA34449@isc.org>
content-type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) by bugs.isc.org (Postfix) with ESMTP id DF36A71B586 for <bind9-bugs@bugs.isc.org>; Mon, 30 Nov 2015 21:05:21 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id BCDB9216C1E; Mon, 30 Nov 2015 21:05:21 +0000 (UTC)
Delivered-To: bind9-bugs@bugs.isc.org
Subject: Re: [ISC-Bugs #41202] No IANA registration for port 953
User-Agent: Mutt/1.5.23 (2014-03-12)
Return-Path: <each@isc.org>
X-Original-To: bind9-bugs@bugs.isc.org
Date: Mon, 30 Nov 2015 21:05:21 +0000
To: "Mark Andrews via RT" <bind9-bugs@isc.org>
From: "Evan Hunt" <each@isc.org>
RT-Message-ID: <rt-4.2.8-1384-1448917522-1295.41202-0-0@isc.org>
Content-Length: 380

> This is deliberate.  There is no need for a port to be registered
> for this as it is entirely private use.  rndc.conf provides a
> adequate way to remember the port between invocations.

However, our use of 953 as a default could be problematic if some other
service came along which wanted to reserve that port.  It wouldn't hurt
to ask IANA to recognize the existing usage.