Re: [port-srv-reg] Fwd: Reminder: WGLC Announcement for draft-ietf-tsvwg-iana-ports-08 - 26th November 2010
Joe Touch <touch@isi.edu> Tue, 23 November 2010 17:15 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 455FB3A6942 for <port-srv-reg@core3.amsl.com>;
Tue, 23 Nov 2010 09:15:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.565
X-Spam-Level:
X-Spam-Status: No, score=-102.565 tagged_above=-999 required=5 tests=[AWL=0.034,
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 u6X8oTdE38fS for
<port-srv-reg@core3.amsl.com>; Tue, 23 Nov 2010 09:15:23 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com
(Postfix) with ESMTP id 260DB3A690F for <port-srv-reg@ietf.org>;
Tue, 23 Nov 2010 09:15:23 -0800 (PST)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated
bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id oANHG7dO011619
(version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);
Tue, 23 Nov 2010 09:16:07 -0800 (PST)
Message-ID: <4CEBF6D7.2050902@isi.edu>
Date: Tue, 23 Nov 2010 09:16:07 -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: <p06240827c9108fb7d7f0@[10.20.30.150]>
<BF2AAA6C-23C5-4F0B-A27E-D4A2AE930983@nokia.com>
In-Reply-To: <BF2AAA6C-23C5-4F0B-A27E-D4A2AE930983@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: oANHG7dO011619
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: port-srv-reg@ietf.org
Subject: Re: [port-srv-reg] Fwd: Reminder: WGLC Announcement
for draft-ietf-tsvwg-iana-ports-08 - 26th November 2010
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: Tue, 23 Nov 2010 17:15:24 -0000
Hi, all, I agree with the URL references. We can probably just cite them as being available on the IANA web pages at www.iana.org W.r.t. the system/user port issue, this document is about unifying the registries. It does NOT change how the ports are used. That issue is not appropriate for this document, IMO. The text in sec 6 should explain what system ports are, which is actually discussed peripherally at the end of sec 6: ...Such confirmation of intended use is especially important when these ports are associated with privileged (e.g., system or administrator) processes. So maybe we can update 6 to explain that system ports are associated with privileged (e.g., system or administrator) processes. That text should be repeated where needed, e.g., in sec 8. I don't see a need to address this in sec 7; none of the principles there affect how system/user ports are evaluated. Thoughts? Joe On 11/22/2010 11:29 PM, Lars Eggert wrote: > > > Begin forwarded message: > >> From: Paul Hoffman<paul.hoffman@vpnc.org> >> Date: November 23, 2010 0:14:26 GMT+02:00 >> To: tsvwg WG<tsvwg@ietf.org> >> Subject: Re: Reminder: WGLC Announcement for draft-ietf-tsvwg-iana-ports-08 - 26th November 2010 >> >> In general, this document seems fairly worthwhile. I have a two reservations, however: >> >> - There is no justification for retaining the differentiation >> between System Ports and User Ports. Given the wide disparity in >> assignment rates, I would have thought that this would be a good >> time to say "there is no longer a difference". The text in 8.1 >> doesn't explain the difference in a way I could discern. At a >> minimum, this needs to be covered in much more detail in sections >> 7.1 and 7.2. >> >> - Two of the references seem ill-advised for a long-lived RFC: >> [SYSFORM] Internet Assigned Numbers Authority (IANA), "Application >> for System (Well Known) Port Number", >> http://www.iana.org/cgi-bin/sys-port-number.pl. >> >> [USRFORM] Internet Assigned Numbers Authority (IANA), "Application >> for User (Registered) Port Number", >> http://www.iana.org/cgi-bin/usr-port-number.pl. >> For years, URI-aware IETF participants have been trying to get IANA to not instantiate URIs that hard-code the source and type of content in public URLs. The above two URLs force IANA to keep using an Apache-based directory structure, and to keep using Perl scripts, for the life of this RFC. It would be far better if IANA would start following Web best practices before this document is published as an RFC and use more universal local parts in these URLs. >> >> On a process note, am I really the only person doing a WG LC review of this document? I'm not really even a WG member... >> >> --Paul Hoffman, Director >> --VPN Consortium > > > > _______________________________________________ > Port-srv-reg mailing list > Port-srv-reg@ietf.org > https://www.ietf.org/mailman/listinfo/port-srv-reg