Re: draft-ietf-tsvwg-iana-ports-09: How we have resolved WG last call comments
Eliot Lear <lear@cisco.com> Thu, 02 December 2010 12:51 UTC
Return-Path: <lear@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E572A28C0F5 for <tsvwg@core3.amsl.com>; Thu, 2 Dec 2010 04:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.159
X-Spam-Level:
X-Spam-Status: No, score=-110.159 tagged_above=-999 required=5 tests=[AWL=0.440, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 nllGV6vd1cRH for <tsvwg@core3.amsl.com>; Thu, 2 Dec 2010 04:51:30 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id A854428C0E9 for <tsvwg@ietf.org>; Thu, 2 Dec 2010 04:51:29 -0800 (PST)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArEEAAMl90yQ/khMgWdsb2JhbACDUJ9QFQEBFiIipxGKPZBEgSGDM3MEimY
X-IronPort-AV: E=Sophos;i="4.59,287,1288569600"; d="scan'208";a="14407695"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 02 Dec 2010 12:52:44 +0000
Received: from dhcp-10-61-103-64.cisco.com (dhcp-10-61-103-64.cisco.com [10.61.103.64]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id oB2CqipS017931; Thu, 2 Dec 2010 12:52:44 GMT
Message-ID: <4CF796A9.9070608@cisco.com>
Date: Thu, 02 Dec 2010 13:52:57 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: draft-ietf-tsvwg-iana-ports-09: How we have resolved WG last call comments
References: <4CF79432.8070508@ericsson.com>
In-Reply-To: <4CF79432.8070508@ericsson.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: tsvwg <tsvwg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Dec 2010 12:51:32 -0000
Magnus, On 12/2/10 1:42 PM, Magnus Westerlund wrote: > 1. Proposal to make the system port range equal to the registered range. > > Outcome: No clear consensus on making the change. There was some support > for this change. But also push back on doing the change. The push back > can be summarized as: Agreement that in theory there should be no > differences, however in reality there are a number of implementations, > mostly UNIX dialects that do make a difference. This is a distinction without a difference. Nobody cares anymore about the port range, and the argument is circular, if it was every really stable to begin with. This distinction was made at a time when perhaps the only port in use over 100 (not 1000) was RIP, with the assumption being that services would be registered. That flew out the window largely with X, and then out of the planet with Windows, and out of the solar system with mobile devices. Please. Let's move this distinction into history, where it belongs. Eliot
- draft-ietf-tsvwg-iana-ports-09: How we have resol… Magnus Westerlund
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Eliot Lear
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Lars Eggert
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Magnus Westerlund
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Eliot Lear
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Lars Eggert
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… George Neville-Neil
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Paul Hoffman
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Paul Hoffman
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… George Neville-Neil
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Eliot Lear
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… George Neville-Neil
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Joe Touch
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Joe Touch
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Joe Touch
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… George Neville-Neil
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Eliot Lear
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… t.petch
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Joe Touch
- Re: draft-ietf-tsvwg-iana-ports-09: How we have r… Lars Eggert
- Assigning ports t.petch
- Re: Assigning ports Joe Touch
- Re: Assigning ports t.petch
- Re: Assigning ports Joe Touch