Re: [tsvwg] [Fwd: Re: AD review: draft-ietf-tsvwg-port-randomization-05]

Lars Eggert <lars.eggert@nokia.com> Fri, 29 January 2010 09:24 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 0A3C73A67FA for <tsvwg@core3.amsl.com>; Fri, 29 Jan 2010 01:24:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.602
X-Spam-Level:
X-Spam-Status: No, score=-6.602 tagged_above=-999 required=5 tests=[AWL=-0.003, BAYES_00=-2.599, 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 2Bsb5rrTTFBv for <tsvwg@core3.amsl.com>; Fri, 29 Jan 2010 01:24:49 -0800 (PST)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 58EB73A6784 for <tsvwg@ietf.org>; Fri, 29 Jan 2010 01:24:49 -0800 (PST)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx06.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o0T9LHTf013211; Fri, 29 Jan 2010 11:21:25 +0200
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 29 Jan 2010 11:21:19 +0200
Received: from mgw-sa01.ext.nokia.com ([147.243.1.47]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Fri, 29 Jan 2010 11:21:19 +0200
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-sa01.ext.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o0T9LGev025468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jan 2010 11:21:17 +0200
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.95.3 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: multipart/signed; boundary="Apple-Mail-7-834339880"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <4B608FEC.2090203@gont.com.ar>
Date: Fri, 29 Jan 2010 11:21:04 +0200
Message-Id: <ED5B4FDE-8D4C-46B4-91D6-8F5EA4544C4F@nokia.com>
References: <C77B4C32.1F9A5%michelle.cotton@icann.org> <4B608FEC.2090203@gont.com.ar>
To: Fernando Gont <fernando@gont.com.ar>
X-Mailer: Apple Mail (2.1077)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (mail.fit.nokia.com [0.0.0.0]); Fri, 29 Jan 2010 11:21:11 +0200 (EET)
X-OriginalArrivalTime: 29 Jan 2010 09:21:19.0222 (UTC) FILETIME=[6A607160:01CAA0C4]
X-Nokia-AV: Clean
Cc: Michelle Cotton <michelle.cotton@icann.org>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] [Fwd: Re: AD review: draft-ietf-tsvwg-port-randomization-05]
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: Fri, 29 Jan 2010 09:24:51 -0000

Hi,

is this an issue that needs to be resolved before a revision of port-randomization can be posted? (I'm trying to get as many drafts as possible moving before the next IETF...)

Thanks,
Lars

On 2010-1-27, at 21:11, Fernando Gont wrote:

> Michelle Cotton wrote:
> 
>> IANA assigns a requested port number if that port number is available.
>> However there are many instances where folks come to IANA and request a
>> certain port number because they have been using it  and it is already
>> assigned to someone else.
>> 
>> We encourage coming to IANA first before “using” a port number.
> 
> Agreed, but, if IANA actually "assigns" rather than just "register" port
> numbers in the "registered" port range, I guess some requests are
> approved, and others are rejected... so I wonder what's the criteria for
> that... in partcular when port numbers are used by "closed" protocols.
> 
> e.g., what has been the criteria for "assigning" say, these port numbers:
> 
> 
> shockwave	1626/tcp  Shockwave
> lofr-lm         1752/tcp    Leap of Faith Research License Manager
> yo-main         4040/tcp   Yo.net main service
> turbonote-1     39681/tcp   TurboNote Default Port
> 
> Have there any cases in which use of a port has been rejected? If so,
> what has been that reason?
> 
> Thanks!
> 
> Kind regards,
> -- 
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@acm.org
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
> 
> 
> 
>