Re: [port-srv-reg] Fwd: Re: [DNSOP] New version of document for review

Joe Touch <touch@isi.edu> Thu, 02 December 2010 18:13 UTC

Return-Path: <touch@isi.edu>
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 CC6B928C14C for <port-srv-reg@core3.amsl.com>; Thu, 2 Dec 2010 10:13:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level:
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 HUhn2+S8DR3y for <port-srv-reg@core3.amsl.com>; Thu, 2 Dec 2010 10:13:00 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id AE42C28C0EE for <port-srv-reg@ietf.org>; Thu, 2 Dec 2010 10:13:00 -0800 (PST)
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 oB2ICwJa022384 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 2 Dec 2010 10:13:01 -0800 (PST)
Message-ID: <4CF7E1AA.4050907@isi.edu>
Date: Thu, 02 Dec 2010 10:12:58 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
References: <4CC971F7.1000504@ericsson.com> <4CF71688.4050404@isi.edu> <4CF7D183.3040704@ericsson.com> <B9C2EAA2-78D7-4CB2-B584-5F1BE48E17FB@nokia.com>
In-Reply-To: <B9C2EAA2-78D7-4CB2-B584-5F1BE48E17FB@nokia.com>
Content-Type: multipart/mixed; boundary="------------030005030901070607030104"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "port-srv-reg@ietf.org" <port-srv-reg@ietf.org>
Subject: Re: [port-srv-reg] Fwd: Re: [DNSOP] New version of document for review
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, 02 Dec 2010 18:13:02 -0000

Hi, Lars,

Some comments below...

On 12/2/2010 9:59 AM, Lars Eggert wrote:
...
>>>> * In Section 8.1 (and/or perhaps elsewhere?) I think it would be useful
>>>> to suggest (perhaps at the SHOULD level?) that when appropriate the
>>>> administrative contact e-mail address should be a role account, and the
>>>> problem this is designed to mitigate (individuals sometimes leave the
>>>> company/organization that is responsible for the assignment resulting in
>>>> a dead e-mail address).
>>
>> Not discussed currently, but something that IANA themselves can make
>> clear in any form.
>
> Or we add a sentence into the current working version now, to be included whenever we issue one.

This is a doc about IANA procedure, not about best practices for those 
filling out requests. That sort of nit seems OK for IANA to include as a 
reminder, but unnecessary for this document.

>>>> * In Section 6 (and elsewhere) there does not appear to be a normative
>>>> reference for the division of port numbers into the Well Known,
>>>> Registered, and Dynamic categories.
>>
>> Still not present in that section.
>
> *Is* there even such a reference? I thought it was a historic artifact.

RFC1340

(I have a complete history of this in the other doc I've been drafting, 
if I ever get cycles to get to it...) See attached drafty draft. The 
history part is fairly complete.

--

On a separate note, the ref to the ID on portnames got dropped with the 
claim that others had proposed it. I have a history in the portnames 
doc, and the idea was never proposed AFAICT. If anyone knows of such 
other proposals along those lines, please let me know (and if claiming 
such exist is the only reason for dropping that text, in the absence of 
a specific pointer I'll ask to restore that sentence).

Joe