Re: [port-srv-reg] ACTION ITEMS - final updates - ports doc

Lars Eggert <lars.eggert@nokia.com> Thu, 20 May 2010 06:47 UTC

Return-Path: <lars.eggert@nokia.com>
X-Original-To: port-srv-reg@core3.amsl.com
Delivered-To: port-srv-reg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A52383A6CE7 for <port-srv-reg@core3.amsl.com>; Wed, 19 May 2010 23:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.958
X-Spam-Level:
X-Spam-Status: No, score=-4.958 tagged_above=-999 required=5 tests=[AWL=-0.960, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 UyDySKOCvWMA for <port-srv-reg@core3.amsl.com>; Wed, 19 May 2010 23:47:28 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 3334B3A67EC for <port-srv-reg@ietf.org>; Wed, 19 May 2010 23:47:24 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx03.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o4K6kl1t022080; Thu, 20 May 2010 09:47:14 +0300
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 20 May 2010 09:46:28 +0300
Received: from mgw-sa02.ext.nokia.com ([147.243.1.48]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Thu, 20 May 2010 09:46:28 +0300
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-sa02.ext.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o4K6kQBq024627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 May 2010 09:46:26 +0300
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: multipart/signed; boundary=Apple-Mail-8--321978720; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <4BF3F313.40805@isi.edu>
Date: Thu, 20 May 2010 09:46:04 +0300
Message-Id: <118EACD9-782A-4F79-8201-FFB09EBF8841@nokia.com>
References: <201002190143.CAA21850@TR-Sys.de> <4B7F0FF4.5050904@isi.edu> <4B98AE6D.4040704@erg.abdn.ac.uk> <4B9AB98F.5080802@isi.edu> <4B9B6F07.7090105@erg.abdn.ac.uk> <4B9B9F8C.6080900@isi.edu> <4BABC04D.206@isi.edu> <4BBBB3C8.9060402@isi.edu> <4BE1B8C6.6010706@isi.edu> <7ECE5396-364E-4365-8E1B-F782E25727B0@nokia.com> <4BF33873.8010309@isi.edu> <4D0497EE-FD49-445E-942D-1388C66A2701@nokia.com> <4BF3F313.40805@isi.edu>
To: Joe Touch <touch@ISI.EDU>
X-Mailer: Apple Mail (2.1078)
X-OriginalArrivalTime: 20 May 2010 06:46:28.0087 (UTC) FILETIME=[2C480070:01CAF7E8]
X-Nokia-AV: Clean
Cc: "port-srv-reg@ietf.org" <port-srv-reg@ietf.org>
Subject: Re: [port-srv-reg] ACTION ITEMS - final updates - ports doc
X-BeenThere: port-srv-reg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of updates to service name and transport protocol port registry <port-srv-reg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/port-srv-reg>, <mailto:port-srv-reg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/port-srv-reg>
List-Post: <mailto:port-srv-reg@ietf.org>
List-Help: <mailto:port-srv-reg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/port-srv-reg>, <mailto:port-srv-reg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2010 06:47:34 -0000

Hi,

On 2010-5-19, at 17:17, Joe Touch wrote:
> I.e., here are the specific changes:
> 
> <orig>
> 	Transport Protocol(s) (REQUIRED if port number requested)
> <new>
> 	Transport Protocol(s) (REQUIRED)
> 
> <orig>
>   o  Transport Protocol(s): If assignment of a port number is desired,
>      the transport protocol(s) for which the allocation is requested
>      MUST be provided.  This field is currently limited to one or more
>      of TCP, UDP, SCTP, and DCCP.
> <new>
>   o  Transport Protocol(s): The transport protocol(s) for which the
>      allocation is requested MUST be provided.  This field is currently
>      limited to one or more of TCP, UDP, SCTP, and DCCP. This field is
>      required even for services with no port number.

applied.

> <new - insert after Reference (REQUIRED)>
> 	Known Unauthorized Uses (OPTIONAL)
> 	Assignment Notes (OPTIONAL)
> 
> <new - insert after full description of Reference>
> 
> o Known Unauthorized Uses: A list of uses by applications or
> organizations who are not the assignee. This list may be augmented by
> IANA after assignment when unauthorized uses are reported.
> 
> o Assignment Notes: Indications of owner/name change, or any other
> assignment process issue. This list may be updated by IANA after
> assignment to help track changes to an assignment, e.g.,
> de-registration, owner/name changes, etc.

Also applied, for now, so we know what we are discussing.

Lars

PS: Diff to -04: