Re: TCPMUX (RFC 1078) status

Martin Sustrik <sustrik@250bpm.com> Wed, 21 August 2013 15:31 UTC

Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91AC511E821E for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 08:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level:
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xw+nYo4K4dcZ for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 08:31:34 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7027011E8112 for <ietf@ietf.org>; Wed, 21 Aug 2013 08:31:34 -0700 (PDT)
Received: from [192.168.0.100] (ip66.bbxnet.sk [91.219.133.66]) by mail.moloch.sk (Postfix) with ESMTPSA id 3A43D1803548; Wed, 21 Aug 2013 17:31:33 +0200 (CEST)
Message-ID: <5214DD54.60009@250bpm.com>
Date: Wed, 21 Aug 2013 17:31:32 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com> <520DBABA.2000506@250bpm.com> <520E6A55.6010802@isi.edu> <52136288.6090408@250bpm.com> <521384B8.9020505@isi.edu> <52147135.9060705@250bpm.com> <5214D8E7.50002@isi.edu>
In-Reply-To: <5214D8E7.50002@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 21 Aug 2013 15:31:43 -0000

On 21/08/13 17:12, Joe Touch wrote:

>> The real problem here IMO is how to distinguish between "adding a
>> completely new application" -- which should require approval process --
>> and "adding a new component within an existing distributed application"
>> -- which should be managed by devs themselves.
>
> IMO it's easy - any group of services you want others to be able to use
> independently could justify a new port, but you can always mux them all
> together if you want to avoid additional firewall configuration issues.

So what would you use for muxing, if TCPMUX is not a good idea?

> I.e., this is your call. But it doesn't appear to have anything to do
> with the notion of a single port to access any *existing* service, which
> is what TCPMUX and its descendants does.

Martin