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

Fernando Gont <fernando@gont.com.ar> Wed, 27 January 2010 19:20 UTC

Return-Path: <fernando.gont.netbook.win@gmail.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 17FEE3A68DB for <tsvwg@core3.amsl.com>; Wed, 27 Jan 2010 11:20:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.956
X-Spam-Level:
X-Spam-Status: No, score=-0.956 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_NJABL_PROXY=1.643]
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 yDoCUcnTMbJ6 for <tsvwg@core3.amsl.com>; Wed, 27 Jan 2010 11:20:35 -0800 (PST)
Received: from mail-yw0-f109.google.com (mail-yw0-f109.google.com [209.85.211.109]) by core3.amsl.com (Postfix) with ESMTP id 3A2043A6892 for <tsvwg@ietf.org>; Wed, 27 Jan 2010 11:20:35 -0800 (PST)
Received: by ywh7 with SMTP id 7so1826062ywh.18 for <tsvwg@ietf.org>; Wed, 27 Jan 2010 11:20:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=qaevlDJ3dUCFKxeirTjqPtiyBfwaIvhj3DclshQPOGw=; b=cuqJQmWX73SY8PHF2STDy1WRr3bqXKtjrZwHUtcxcRc9j8P+SmgwbNZPvLC0dv7L2N NuWmZQ1wsAHMabpq1WQQ8yvo/fDLxWTuz7L6WLksG4cIpiddT7bKtGYo5y6WcQkkJ77J cl1Es0LwQoe6WQzQAsf9lPehKcjfeDrbgl/gU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=LsMfwC8/GlJjELw8zuo1wQKVHfDSNh2hsI02iuz/2UCIbrbx6sJY6KOa2wDDH48rrc vb0m0OODAsBzLTl0eXrT9vOcS9rrOl0Mn48pz9IVOHeYASocKrOR6k7bZ7dUwXrBB+Be vyCfUFB7yOqwftigQE9saKIbtjnqZ/W2JfRHI=
Received: by 10.101.147.24 with SMTP id z24mr8455660ann.150.1264620047352; Wed, 27 Jan 2010 11:20:47 -0800 (PST)
Received: from ?190.48.227.28? ([190.48.227.28]) by mx.google.com with ESMTPS id 4sm58335ywd.59.2010.01.27.11.20.44 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 27 Jan 2010 11:20:46 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4B609203.6010100@gont.com.ar>
Date: Wed, 27 Jan 2010 16:20:35 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
References: <4B4ABB1E.7010809@gont.com.ar> <D7ADE4E4-5876-4ADC-AE8C-C7C894A53649@nokia.com> <4B4BA948.3080302@gont.com.ar> <A8E1ACBA-9F4B-451A-A526-256DD81E8052@nokia.com> <4B4E1110.3020901@gont.com.ar> <EB6229CF-9670-4751-9F46-EB11DC721C4F@nokia.com> <4B55EA7D.3060705@gont.com.ar> <22EDB9D5-4C7C-40A8-9D98-396FE2AD3969@nokia.com> <4B578A7F.7030908@gont.com.ar> <F03E6942-74B1-407F-BCCA-4BB339080835@nokia.com>
In-Reply-To: <F03E6942-74B1-407F-BCCA-4BB339080835@nokia.com>
X-Enigmail-Version: 0.96.0
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: Wed, 27 Jan 2010 19:20:36 -0000

Lars Eggert wrote:

>> What has been the criteria for assigning port numbers for e.g.
>> closed protocols? (other than just registering their use)
> 
> this is going a bit offtopic, but I believe that IANA has been using
> the Expert Review procedure we're describing in iana-ports for many
> years. (One of the reasons for iana-ports is to document the existing
> procedures.)

I have not read your I-D (other than some specific parts). But I believe
that the question I asked is key to the "assigned" vs. "registered"
discussion. If it's not clear what's the criteria for assigning or
rejecting port numbers in a specific range, particularly when an app has
already been using it, I don't think one can go further than saying that
 IANA has "registered" the port.

I recall reading some piece of text at IANA's web site that for the most
part the list of registered for was kinda a "best effort" service to the
community.


>> Have there any cases in which use of a port has been rejected?
> 
> Yes.
>
>> If so, what has been that reason?
> 
> Depends :-) Maybe IANA can give some examples.
> 
>> And what has been the criteria for actually "granting" the use of
>> ports (as the above)?
> 
> Satisfying the Expert Reviewer.

Hope Michelle (or somebody else from IANA) can help with these ones.

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