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

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 08 April 2010 11:12 UTC

Return-Path: <alexey.melnikov@isode.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 E57A03A69A3 for <port-srv-reg@core3.amsl.com>; Thu, 8 Apr 2010 04:12:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 vyTus2XzHsmH for <port-srv-reg@core3.amsl.com>; Thu, 8 Apr 2010 04:12:40 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id E4D513A6A1B for <port-srv-reg@ietf.org>; Thu, 8 Apr 2010 04:12:39 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <S726JABHTibK@rufus.isode.com>; Thu, 8 Apr 2010 12:12:36 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4BBDBA1C.2020303@isode.com>
Date: Thu, 08 Apr 2010 12:12:28 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Joe Touch <touch@ISI.EDU>
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> <4BBDB9B8.2070601@isode.com>
In-Reply-To: <4BBDB9B8.2070601@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "port-srv-reg@ietf.org" <port-srv-reg@ietf.org>
Subject: Re: [port-srv-reg] 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, 08 Apr 2010 11:12:41 -0000

Alexey Melnikov wrote:

> Hi Joe,
>
> Joe Touch wrote:
> [...]
>
>> All the items above except for "Comments" are described in the doc, and
>> constitute the registration information. The comments field should, IMO,
>> be broken down into a few separate fields; I'm not sure any of these
>> need to be listed in the doc, however, since the information it presents
>> is administrative 'out-of-band' context.
>
> Do we need to be that strict about what can go into Comments?

For example, can the reference to a document defining use of DNS SRV be 
listed here?

> I am fine with your proposal as well, but I don't think limiting scope 
> of comments would be helpful to IANA. Michelle?
>
>> Here's what I would break it into two fields:
>>
>>     Known Unauthorized Uses
>>     Assignment comments (de-registration, owner change, name change)
>>
>> I'm not sure it's appropriate to list the known unauthorized uses in the
>> same table as the authorized ones; I would prefer de-valuing that list
>> to a separate table on a separate page.
>
> Works for me. Documenting unauthorized uses might be of value and I 
> agree that keeping it separate is sensible.