Re: draft-ietf-tsvwg-iana-ports-09: How we have resolved WG last call comments

Lars Eggert <lars.eggert@nokia.com> Thu, 02 December 2010 13:57 UTC

Return-Path: <lars.eggert@nokia.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1773928C0D0 for <tsvwg@core3.amsl.com>; Thu, 2 Dec 2010 05:57:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level:
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oJQAGwSsfBov for <tsvwg@core3.amsl.com>; Thu, 2 Dec 2010 05:57:01 -0800 (PST)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by core3.amsl.com (Postfix) with ESMTP id 485EF28C0CE for <tsvwg@ietf.org>; Thu, 2 Dec 2010 05:57:01 -0800 (PST)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da02.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id oB2DwAI5020560 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2010 15:58:11 +0200
Subject: Re: draft-ietf-tsvwg-iana-ports-09: How we have resolved WG last call comments
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96.4 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary="Apple-Mail-14--541529970"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <4CF796A9.9070608@cisco.com>
Date: Thu, 02 Dec 2010 15:58:02 +0200
Message-Id: <7A4B44A1-8A53-4819-82A2-5583D52218B4@nokia.com>
References: <4CF79432.8070508@ericsson.com> <4CF796A9.9070608@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Thu, 02 Dec 2010 15:58:07 +0200 (EET)
X-Nokia-AV: Clean
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, tsvwg <tsvwg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Dec 2010 13:57:02 -0000

Hi,

On 2010-12-2, at 14:52, Eliot Lear wrote:
> This is a distinction without a difference.  Nobody cares anymore about
> the port range, and the argument is circular, if it was every really
> stable to begin with.  This distinction was made at a time when perhaps
> the only port in use over 100 (not 1000) was RIP, with the assumption
> being that services would be registered.  That flew out the window
> largely with X, and then out of the planet with Windows, and out of the
> solar system with mobile devices.  Please.  Let's move this distinction
> into history, where it belongs.

Assume we got rid of the distinction between ports larger and smaller than 1024 like you're asking us to. IANA just treats them the same, i.e., FCFS with Expert Review.

Assume that someone asks for a port number. IANA rolls the dice and gives them 842.

They put that in their code and all of a sudden realize that on many platforms, they need to ask the user for admin rights in order to bind to that port.

They won't be happy.

Right?

Because in practice, on many systems, it DOES matter if you have a low port or not.

(So instead what we do is we limit the FCFS range to 1024-49151 and make people who think they want a low port go via the IETF.)

Lars