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

David Conrad <drc@virtualized.org> Thu, 25 May 2006 03:52 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fj6tb-0006DO-Gn; Wed, 24 May 2006 23:52:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fj6ta-0006DJ-Ia for ietf@ietf.org; Wed, 24 May 2006 23:52:22 -0400
Received: from ns.virtualized.org ([204.152.189.134] helo=mail.virtualized.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fj6tY-0000Rz-4r for ietf@ietf.org; Wed, 24 May 2006 23:52:22 -0400
Received: from terminus.local (ns.virtualized.org [204.152.189.134]) by mail.virtualized.org (8.12.9p1/8.12.9) with ESMTP id k4P2Yddm046944; Wed, 24 May 2006 19:34:48 -0700 (PDT) (envelope-from drc@virtualized.org)
Received: from [127.0.0.1] by terminus.local (PGP Universal service); Wed, 24 May 2006 20:52:10 -0700
X-PGP-Universal: processed; by terminus.local on Wed, 24 May 2006 20:52:10 -0700
In-Reply-To: <7DFCB2920E3DCE504E503EBD@sirius.fac.cs.cmu.edu>
References: <883F4A921E26D32C08E569F0@p3.JCK.COM> <44745B81.8000508@cisco.com> <7DFCB2920E3DCE504E503EBD@sirius.fac.cs.cmu.edu>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <1FA82A97-E336-4995-AAE1-AFE664631419@virtualized.org>
Content-Transfer-Encoding: 7bit
From: David Conrad <drc@virtualized.org>
Date: Wed, 24 May 2006 20:51:57 -0700
To: Jeffrey Hutzelman <jhutz@cmu.edu>
X-Mailer: Apple Mail (2.750)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org, Eliot Lear <lear@cisco.com>
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

Hi,

On May 24, 2006, at 4:06 PM, Jeffrey Hutzelman wrote:
> On Wednesday, May 24, 2006 03:11:29 PM +0200 Eliot Lear  
> <lear@cisco.com> wrote:
>> Yes, the distinction between well known ports and just assigned  
>> ports is
>> outdated.  The overarching theme of the document is that the IANA  
>> should
>> be treated as a group of adults

Heh.  :-)

>> and that they should use some discretion
>> with oversight only where needed.
>
> Careful here...
>
> (1) The IANA is a group of adults, but it is no longer a group of
>    protocol subject matter experts.  IMHO there is probably no need
>    for IESG oversight of port number allocation, especially if we are
>    eliminating the (artificial) scarcity of so-called well-known  
> ports.

The scarcity of ports is not artificial.  There are only 16 bits of  
port space and changing the number of bits in ports will be ...  
interesting.

> (2) As I understand it, for ports above 1024, the IANA does _not_  
> assign
>    values - it just registers uses claimed by others.

This is not accurate.  The IESG has been explicit in that IANA  
assigns port numbers (both well known and user), it does not register  
use.

> Second, I believe that having a complete, accurate registry of port  
> numbers is highly valuable.

As do I.  It does not currently exist.

> That means that they won't be known to network administrators or  
> network traffic analysis tools,

Of course, the port registry does nothing to stop any protocol using  
any port.

It might be useful to figure out what function folks expect the IANA  
port registry to perform.

Rgds,
-drc


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