Re: Questions about draft-lear-iana-no-more-well-known-ports-00.txt

John C Klensin <john-ietf@jck.com> Thu, 25 May 2006 01:16 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fj4T4-0003EN-4w; Wed, 24 May 2006 21:16:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fj4T3-0003EG-9e for ietf@ietf.org; Wed, 24 May 2006 21:16:49 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fj4T1-0008OE-V4 for ietf@ietf.org; Wed, 24 May 2006 21:16:49 -0400
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1Fj4T0-000MSv-6j; Wed, 24 May 2006 21:16:46 -0400
Date: Wed, 24 May 2006 21:16:45 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jeffrey Hutzelman <jhutz@cmu.edu>, Eliot Lear <lear@cisco.com>
Message-ID: <664A83A74B8EC25F2B007B2E@p3.JCK.COM>
In-Reply-To: <7DFCB2920E3DCE504E503EBD@sirius.fac.cs.cmu.edu>
References: <883F4A921E26D32C08E569F0@p3.JCK.COM> <44745B81.8000508@cisco.com> <7DFCB2920E3DCE504E503EBD@sirius.fac.cs.cmu.edu>
X-Mailer: Mulberry/4.0.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: ietf@ietf.org
Subject: Re: Questions about draft-lear-iana-no-more-well-known-ports-00.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org


--On Wednesday, 24 May, 2006 19:06 -0400 Jeffrey Hutzelman
<jhutz@cmu.edu> wrote:

> Disclaimer - I wasn't even aware of this document before
> reading this thread.  However, I have now read it, so feel
> prepared to comment.
>...
 
> (2) As I understand it, for ports above 1024, the IANA does
> _not_ assign
>     values - it just registers uses claimed by others.
> Eliminating
>     well-known ports eliminates any assignment role, and
> leaves us with
>     just a registry of what people have claimed.  Note that
> this means
>     there is no mechanism which prevents the same number from
> being
>     registered by more than one registry.

This is not correct.  They do, indeed, assign values.  They also
apply some minimal rules in doing so.  Squatting on unassigned
values, while it does happen, is considered to be in bad taste.

> Second, I believe that having a complete, accurate registry of
> port numbers is highly valuable.  If there is a charge to
> register a port, and a recurring charge to maintain a
> registration, then no one will register their ports for
> private or vendor-specific use and/or minor protocols. That
> means that they won't be known to network administrators or
> network traffic analysis tools, and people looking for an
> unused port - even if they intend to register and pay for it -
> will have a difficult time finding one that is actually free.
> It also means that registrations will tend to disappear over
> time, such that valuable historical information is lost.
>...

FWIW, I tend to agree.

     john


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf