Re: Drafting mux WG charter

From: spreitze@parc.xerox.com
Date: Mon, Feb 22 1999


From: spreitze@parc.xerox.com
Date: Mon, 22 Feb 1999 11:43:04 PST
To: Ben Laurie <ben@algroup.co.uk>
Cc: ietf-http-ng@w3.org
Message-Id: <99Feb22.114317pst."834550"@idea.parc.xerox.com>
Subject: Re: Drafting mux WG charter


> Firewalls rely on knowing where traffic is
> going. A MUXed protocol is likely to require inspection of every byte to
> do this, or at least, reconstruction of the stream, if it is to be
> noticably different from using multiple connections. This will make
> firewalling almost impossible in hardware, and resource-intensive in all
> circumstances.

My vision of the solution is essentially another layer of packetization.  That is, fixed-length headers that include payload byte counts.  This is the same story as appears at lower layers in the IP stack, and so should be no more difficult for a firewall to handle.