Re: [port-srv-reg] final updates - ports doc
Joe Touch <touch@ISI.EDU> Thu, 08 April 2010 13:34 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 6DFCF3A688A for <port-srv-reg@core3.amsl.com>;
Thu, 8 Apr 2010 06:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level:
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,
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 x--+kuQtp5uX for
<port-srv-reg@core3.amsl.com>; Thu, 8 Apr 2010 06:34:48 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com
(Postfix) with ESMTP id E90B43A6837 for <port-srv-reg@ietf.org>;
Thu, 8 Apr 2010 06:34:47 -0700 (PDT)
Received: from [192.168.1.92] (pool-71-106-88-10.lsanca.dsl-w.verizon.net
[71.106.88.10]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with
ESMTP id o38DX6kF004956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA
bits=256 verify=NOT); Thu, 8 Apr 2010 06:33:07 -0700 (PDT)
Message-ID: <4BBDDB12.7020604@isi.edu>
Date: Thu, 08 Apr 2010 06:33:06 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
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> <4BBDBA1C.2020303@isode.com>
In-Reply-To: <4BBDBA1C.2020303@isode.com>
X-Enigmail-Version: 0.96.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="------------enig9A29B2639D7BF24746C39438"
X-MailScanner-ID: o38DX6kF004956
X-ISI-4-69-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] 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 13:34:49 -0000
Alexey Melnikov wrote: > 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? There's already a references section for that purpose, AFAICT. Joe >> 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. >
- Re: [port-srv-reg] [tsvwg] "assigned" ( vs. "regi… Alfred Hönes
- Re: [port-srv-reg] [tsvwg] "assigned" ( vs. "regi… Magnus Westerlund
- Re: [port-srv-reg] [tsvwg] "assigned" ( vs. "regi… Olafur Gudmundsson
- Re: [port-srv-reg] [tsvwg] "assigned" ( vs. "regi… Joe Touch
- Re: [port-srv-reg] [tsvwg] "assigned" (vs. "regis… Alfred Hönes
- Re: [port-srv-reg] [tsvwg] "assigned" (vs. "regis… Joe Touch
- Re: [port-srv-reg] [tsvwg] "assigned" (vs. "regis… Alfred Hönes
- Re: [port-srv-reg] [tsvwg] "assigned" (vs. "regis… Joe Touch
- [port-srv-reg] final updates - ports doc Joe Touch
- Re: [port-srv-reg] final updates - ports doc Joe Touch
- Re: [port-srv-reg] final updates - ports doc Alexey Melnikov
- Re: [port-srv-reg] final updates - ports doc Alexey Melnikov
- Re: [port-srv-reg] final updates - ports doc Joe Touch
- Re: [port-srv-reg] final updates - ports doc Joe Touch
- [port-srv-reg] status check Lars Eggert
- Re: [port-srv-reg] status check Mark Mcfadden
- Re: [port-srv-reg] status check Pearl Liang
- Re: [port-srv-reg] status check Lars Eggert
- Re: [port-srv-reg] status check Michelle Cotton
- Re: [port-srv-reg] status check Lars Eggert
- [port-srv-reg] ACTION ITEMS - final updates - por… Joe Touch
- Re: [port-srv-reg] final updates - ports doc Lars Eggert
- Re: [port-srv-reg] final updates - ports doc Gorry Fairhurst
- Re: [port-srv-reg] final updates - ports doc Lars Eggert
- Re: [port-srv-reg] ACTION ITEMS - final updates -… Lars Eggert
- Re: [port-srv-reg] ACTION ITEMS - final updates -… Joe Touch
- Re: [port-srv-reg] ACTION ITEMS - final updates -… Lars Eggert
- Re: [port-srv-reg] ACTION ITEMS - final updates -… Alexey Melnikov
- Re: [port-srv-reg] ACTION ITEMS - final updates -… Joe Touch
- Re: [port-srv-reg] ACTION ITEMS - final updates -… David Harrington
- Re: [port-srv-reg] ACTION ITEMS - final updates -… Joe Touch
- Re: [port-srv-reg] ACTION ITEMS - final updates -… Lars Eggert
- Re: [port-srv-reg] ACTION ITEMS - final updates -… Lars Eggert
- Re: [port-srv-reg] ACTION ITEMS - final updates -… Gorry Fairhurst
- Re: [port-srv-reg] ACTION ITEMS - final updates -… Lars Eggert
- Re: [port-srv-reg] ACTION ITEMS - final updates -… Joe Touch
- Re: [port-srv-reg] ACTION ITEMS - final updates -… Lars Eggert
- Re: [port-srv-reg] status check Joe Touch
- Re: [port-srv-reg] status check Lars Eggert
- Re: [port-srv-reg] status check Gorry Fairhurst