Re: [port-srv-reg] draft-ietf-tsvwg-iana-ports: status of draft-touch-tsvwg-port-use
Joe Touch <touch@isi.edu> Thu, 17 February 2011 15:04 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 23B5A3A6F0A for <port-srv-reg@core3.amsl.com>; Thu, 17 Feb 2011 07:04:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.72
X-Spam-Level:
X-Spam-Status: No, score=-104.72 tagged_above=-999 required=5 tests=[AWL=1.879, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 UwW1GOZEqxw1 for <port-srv-reg@core3.amsl.com>; Thu, 17 Feb 2011 07:04:29 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 403A03A6CBF for <port-srv-reg@ietf.org>; Thu, 17 Feb 2011 07:04:29 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-81-169.lsanca.dsl-w.verizon.net [71.105.81.169]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p1HF4IvJ023329 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 17 Feb 2011 07:04:27 -0800 (PST)
Message-ID: <4D5D38F3.7040106@isi.edu>
Date: Thu, 17 Feb 2011 07:04:19 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <4D5D28CB.8080604@isode.com>
In-Reply-To: <4D5D28CB.8080604@isode.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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] draft-ietf-tsvwg-iana-ports: status of draft-touch-tsvwg-port-use
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, 17 Feb 2011 15:04:30 -0000
Hi, all, I had tried, apparently in vain, to update section 7 to address the LC concerns. I don't think that the path below provides a way forward. Perhaps it would be more productive to remove section 7 in its entirety. Let me know if you agree. Joe On 2/17/2011 5:55 AM, Alexey Melnikov wrote: > Hi group, > The following comment was made by Cullen: > > Cullen Jennings wrote: > [...] > >> I find the the following text a bit outrageous. >> >> Applicants >> should be aware that IANA decisions are not required to be bound to >> these principles. These principles and general advice to users on >> port use are expected to change over time and are therefore >> documented separately, please see [I-D.touch-tsvwg-port-use]. >> >> The basic complaints about this draft can mostly be summarized as a >> view that everything that the authors of this draft could not get >> agreement on in the WG, they just made the draft silent on and Joe is >> asserting that the expert reviews can do whatever they think was best >> regardless of any IETF consensus and then people can appeal it. So >> this text would have this BCP assert that the place to find out what >> was OK and not OK was in documented in an individual draft written by >> Joe. This is not OK. Consider if I asked that instead, it pointed at >> I-D.fluffy-port-use. I'm sure many people would think that was totally >> unacceptable. I don't see how this is any more acceptable. It seems >> like an inappropriate change to make without a new LC. I don't think >> that it is OK for a BCP on how to register ports to point people at a >> spec without consensus approval that says what is OK to register and >> what is not. >> > Ignoring the emotional part of the argument, I think I share his concern > about pointing to an individual draft (which is clearly quite raw at > this point) and not a WG document. I would personally feel more > comfortable if [I-D.touch-tsvwg-port-use] was resubmitted as a TSVWG > document. Any objections to this (especially from Joe)? > > Thanks, > Alexey > > > _______________________________________________ > Port-srv-reg mailing list > Port-srv-reg@ietf.org > https://www.ietf.org/mailman/listinfo/port-srv-reg
- [port-srv-reg] draft-ietf-tsvwg-iana-ports: statu… Alexey Melnikov
- Re: [port-srv-reg] draft-ietf-tsvwg-iana-ports: s… Joe Touch
- Re: [port-srv-reg] draft-ietf-tsvwg-iana-ports: s… Lars Eggert
- Re: [port-srv-reg] draft-ietf-tsvwg-iana-ports: s… Michelle Cotton
- Re: [port-srv-reg] draft-ietf-tsvwg-iana-ports: s… Joe Touch
- Re: [port-srv-reg] draft-ietf-tsvwg-iana-ports: s… Alexey Melnikov
- Re: [port-srv-reg] draft-ietf-tsvwg-iana-ports: s… Joe Touch