Re: Assigning ports

Joe Touch <touch@isi.edu> Thu, 15 September 2011 21:38 UTC

Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D6DA11E80B3 for <tsvwg@ietfa.amsl.com>; Thu, 15 Sep 2011 14:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.885
X-Spam-Level:
X-Spam-Status: No, score=-104.885 tagged_above=-999 required=5 tests=[AWL=1.114, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WICm7P8SgHPg for <tsvwg@ietfa.amsl.com>; Thu, 15 Sep 2011 14:38:42 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id CEBFF11E80A6 for <tsvwg@ietf.org>; Thu, 15 Sep 2011 14:38:42 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p8FLeWgO019614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 15 Sep 2011 14:40:32 -0700 (PDT)
Message-ID: <4E7270D0.5070609@isi.edu>
Date: Thu, 15 Sep 2011 14:40:32 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: Assigning ports
References: <4CF79432.8070508@ericsson.com> <008501cb92fa$dc1c1ba0$4001a8c0@gateway.2wire.net> <7B685540-D448-43D1-98D9-5CCBD4A98692@nokia.com> <00de01cc7381$1059d580$4001a8c0@gateway.2wire.net>
In-Reply-To: <00de01cc7381$1059d580$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, tsvwg <tsvwg@ietf.org>, Lars Eggert <lars.eggert@nokia.com>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 15 Sep 2011 21:38:43 -0000

Hi, Tom,

On 9/15/2011 1:25 AM, t.petch wrote:
> Now that RFC6335 has been published, the IANA page on how to get a port assigned
> has been updated (take a good book if you want to access it:-( but the text
> there leaves me confused.
>
> It says
> "System Ports are assigned by IETF process for standards-track protocols, as per
> [RFC1340]"
> which, RFC1340 being ' Assigned Numbers. J. Reynolds, J. Postel. July 1992'
> confuses me.

It's a reference to the original definition of System Ports.

> Should this instead refer to RFC6335 or RFC5226? (I suspect that
> the former is the better reference even if to make sense of it you must access
> the latter).

It might be useful to cite all three.

> It also says
> "Service names are assigned on a first-come, first-served process, as
> documented in [RFC952]"
> which, RFC952 being ' DoD Internet host table specification. K. Harrenstien,
> M.K.
>       Stahl, E.J. Feinler. October 1985. '
> also confuses me.   Should this instead refer to RFC6335 or RFC5226?

Yes - probably both there as well.

I'll forward this to IANA for update.

Joe