Re: Last Call: <draft-ietf-tcpm-undeployed-03.txt> (Moving Outdated TCP Extensions and TCP-related Documents to Historic and Informational Status) to Informational RFC

Philip Homburg <pch-ietf-4@u-1.phicoh.com> Tue, 05 January 2016 12:40 UTC

Return-Path: <pch-bBB316E3E@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08A891B2D4E; Tue, 5 Jan 2016 04:40:58 -0800 (PST)
X-Quarantine-ID: <gTxEvjRrW7gY>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
X-Spam-Flag: NO
X-Spam-Score: -4.6
X-Spam-Level:
X-Spam-Status: No, score=-4.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gTxEvjRrW7gY; Tue, 5 Jan 2016 04:40:55 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE8E1B2D47; Tue, 5 Jan 2016 04:40:53 -0800 (PST)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1aGQuv-0000CuC; Tue, 5 Jan 2016 13:40:49 +0100
Message-Id: <m1aGQuv-0000CuC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-tcpm-undeployed-03.txt> (Moving Outdated TCP Extensions and TCP-related Documents to Historic and Informational Status) to Informational RFC
From: Philip Homburg <pch-ietf-4@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
In-reply-to: Your message of "Mon, 04 Jan 2016 15:53:50 -0500 ." <95406.1451940830@turing-police.cc.vt.edu>
Date: Tue, 05 Jan 2016 13:40:38 +0100
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/dxvQadrFdlWgwMdSBFtHM0Erb4Y>
Cc: tcpm@ietf.org, Valdis.Kletnieks@vt.edu, draft-ietf-tcpm-undeployed@ietf.org, mls.ietf@gmail.com, draft-ietf-tcpm-undeployed@tools.ietf.org, IETF-Announce <ietf-announce@ietf.org>, tcpm-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2016 12:40:58 -0000

In your letter dated Mon, 04 Jan 2016 15:53:50 -0500 you wrote:
>The draft says in section 2.1:
>
>   o  [RFC1078] U, "TCP Port Service Multiplexer (TCPMUX)" should be
>      deprecated, because:
>....
>      *  There are no known client-side deployments.

Just for reference. I use TCPMUX for a private protocol. It is nice for
prototyping because it is easier pick a unique string for a protocol than
to pick un unused port.

(Obviously, when DNS is used, SRV can also be used for this)

The second argument is a weird. 
      *  It requires all new connections to be received on a single
          port, which limits the number of connections between two
	  machines."

There are many systems that receive essentially all of their traffic over 
one port. So those system already have this problem. It also is very rare
that a single host connects to a remote host more than 16000 times
in parallel. So I wonder if this is a practical limitation.