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

Lars Eggert <lars.eggert@nokia.com> Fri, 05 February 2010 12:23 UTC

From: Lars Eggert <lars.eggert@nokia.com>
Content-Type: multipart/signed; boundary=Apple-Mail-50--697401326; protocol="application/pkcs7-signature"; micalg=sha1
Date: Fri, 5 Feb 2010 14:23:27 +0200
References: <004201caa654$6f5e5fc0$0601a8c0@allison>
To: port-srv-reg@ietf.org
Message-Id: <781C9E2F-F351-4627-994B-E1FCB6B4CDFC@nokia.com>
Mime-Version: 1.0 (Apple Message framework v1077)
Subject: [port-srv-reg] Fwd: [tsvwg] [Fwd: Re: AD review: draft-ietf-tsvwg-port-randomization-05]
Precedence: list


Begin forwarded message:

> From: tom.petch <cfinss@dial.pipex.com>
> Date: February 5, 2010 10:28:44 GMT+02:00
> To: Michelle Cotton <michelle.cotton@icann.org>rg>, "Eggert Lars (Nokia-NRC/Espoo)" <lars.eggert@nokia.com>
> Cc: tsvwg <tsvwg@ietf.org>rg>, apps-discuss <apps-discuss@ietf.org>
> Subject: Re: [tsvwg] [Fwd: Re: AD review: draft-ietf-tsvwg-port-randomization-05]
> Reply-To: tom.petch <cfinss@dial.pipex.com>
> 
> ----- Original Message -----
> From: "Michelle Cotton" <michelle.cotton@icann.org>
> To: "Fernando Gont" <fernando@gont.com.ar>ar>; "Lars Eggert"
> <lars.eggert@nokia.com>
> Cc: "tsvwg" <tsvwg@ietf.org>
> Sent: Monday, February 01, 2010 11:39 PM
> 
> 
> Fernando/Lars,
> 
> Following-up on the thread below.
> 
> Port Number requests are rejected for many reasons.  Here are three of the most
> common reasons:
> 
> 1 - Duplicates a function or protocol already in existence
> 2 - Is the secure version of a port already applied for or already in existence
> 3 - Port applied for is of local use only and traffic does not flow over the
> public Internet
> 
> In general, a port number request is granted when an applicant can show a
> well-defined, public Internet protocol.  The port must identify a named service
> that allows sessions to be created over the public Internet.  The protocol, in a
> successful application, will be sufficiently documented to ensure that it is not
> local or a version of another service already in use.
> 
> I hope this information helps.  Please let me know if there is anything I can
> clarify.
> 
> <tp>
> 
> Michelle
> 
> How straightforward and clear the above paragraphs are.  Honest.  Brilliant.
> 
> I need to say this because recently I was critical of
> draft-ietf-tsvwg-iana-ports-04
> for the lack of just this information, for describing the bureaucracy of port
> assignment/allocation/registration/reservation/request/grant........
> without
> a) explaining what if anything is the difference between these terms
> b) describing what the point of the bureaucracy is.
> 
> Your paragraphs above do more good than the whole of section 7, so please ditch
> section 7, include something along the lines above, and place it right at the
> front of the I-D, section 2.  I would place reasons for granting before reasons
> for rejecting but otherwise I would change little.
> 
> Tom Petch
> 
> </tp>
> 
> 
> Michelle
> IANA
> 
> On 1/27/10 11:20 AM, "Fernando Gont" <fernando@gont.com.ar> wrote:
> 
>>> 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.
>

Attachment: smime.p7s

[port-srv-reg] Fwd: [tsvwg] [Fwd: Re: AD review: … Lars Eggert
Re: [port-srv-reg] Fwd: [tsvwg] [Fwd: Re: AD revi… Joe Touch

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

Attachment: smime.p7s