Re: TCPMUX (RFC 1078) status

Martin Sustrik <sustrik@250bpm.com> Thu, 22 August 2013 07:44 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 D72C211E80F3 for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 00:44:36 -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 M3kBrH5eZC-F for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 00:44:30 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3B3D121F9425 for <ietf@ietf.org>; Thu, 22 Aug 2013 00:44:30 -0700 (PDT)
Received: from [192.168.0.100] (ip66.bbxnet.sk [91.219.133.66]) by mail.moloch.sk (Postfix) with ESMTPSA id EB3FA1803555; Thu, 22 Aug 2013 09:44:27 +0200 (CEST)
Message-ID: <5215C15B.3000008@250bpm.com>
Date: Thu, 22 Aug 2013 09:44:27 +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> <5214DD54.60009@250bpm.com> <5214F219.6000506@isi.edu>
In-Reply-To: <5214F219.6000506@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: Thu, 22 Aug 2013 07:44:37 -0000

On 21/08/13 19:00, Joe Touch wrote:

>> So what would you use for muxing, if TCPMUX is not a good idea?
>
> You need to roll your own. The requirements of systems vary widely, as
> do the costs/benefits of different approaches.
>
> I listed a few before, but here's a more comprehensive list:
>      - service per message
>          demux based on message ID
>          use IPC (interprocess comm) to handoff internal
>          to your system
>
>      - service per connection
>          demux based on the first message in an
>          association (TCP or UDP), and either continue to
>          forward messages to a different process or handoff
>          the connection

So, if I proceed with this option why not use RFC1078 to implement it? 
Why write a new RFC if there's an old one that fits the bill?

>
>      - subservice on different ports
>          determine what subservice you want to initiate,
>          start it on an ephemeral port, and indicate the
>          port number in-band (e.g., as with FTP and others)

Martin