Re: [tcmtf] Improved version (v8) of the TCM-TF charter draft

"Jose Saldana" <> Fri, 22 November 2013 09:50 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 5D4F21ACC80; Fri, 22 Nov 2013 01:50:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.726
X-Spam-Status: No, score=-4.726 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id A6HtfFw-LWHk; Fri, 22 Nov 2013 01:50:32 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 894B91ACCDF; Fri, 22 Nov 2013 01:50:32 -0800 (PST)
Received: from usuarioPC ( []) by (8.13.8/8.13.8/Debian-3) with ESMTP id rAM9o2FX003567; Fri, 22 Nov 2013 10:50:11 +0100
From: "Jose Saldana" <>
To: "'Eggert, Lars'" <>
References: <008c01cee5e1$9caa4590$d5fed0b0$> <> <01ee01cee6da$b05eb9a0$111c2ce0$> <>
In-Reply-To: <>
Date: Fri, 22 Nov 2013 10:50:08 +0100
Organization: Universidad de Zaragoza
Message-ID: <01da01cee768$42926af0$c7b740d0$>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI/pFXgt4LgH+pyHEEB6KKfTqM8zAIc4popAgX21NgA+hAoBJkljZTg
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc:,, 'Martin Stiemerling' <>, "'Reinaldo Penno \(repenno\)'" <>, 'Spencer Dawkins' <>
Subject: Re: [tcmtf] Improved version (v8) of the TCM-TF charter draft
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 22 Nov 2013 09:50:35 -0000

Hi, Lars.

During the BoF in Berlin, I got the impression that the problem was not the
idea of TCM-TF itself, but some of the considered options (e.g. TCP). There
were many people who raised their hands when asked about "willing to review
docs or comment on mailing list". However, it seems that there are some
people who are not convinced about the utility of TCM-TF. 

So in order to reach consensus, let us keep on discussing and thinking. This
is very enriching, since it is making us refine the scenarios where TCM-TF
may have a real potential, and discard the ones in which it makes no sense.

I have added two comments inline:

> De: Eggert, Lars []
> Enviado el: jueves, 21 de noviembre de 2013 18:09
> Hi,
> On 2013-11-21, at 11:56, Jose Saldana <> wrote:
> > - in a pair of appliances creating a tunnel between two offices  of a
> > company, there are a number of hops. Interesting for TCM-TF
> there are multiple hops, but are there pressing resource constraints? The
> intranet in all companies I have worked for has worked well enough without
> TCM-TF. If you lease MPLS circuits, you can easily acquire more bandwidth.
> > But what happens if a scenario may involve one, two or more L3 hops?
> > This will  happen in a "community network": you can create a tunnel
> > just to connect a village with the Internet (one hop), or to connect a
> > village with another village, which is the one really connected to the
> > Internet (more than one hop). See a paper about the topology of these
> > networks here
> All of these PEPs really only make sense on the resource-constrained hop.
> In your village example, put them on each side of the congested link. Then
> it's a one-hop scenario. There is little point in going through the
> of compressing, tunneling, etc. when there is ample resource capacity.

This is a very interesting point: we cannot assume that we will have ample
resource capacity everywhere and always. There are situations in which a
traffic rush occurs, and in these situations there are a number of congested
links. I am not only thinking on emerging countries, but also in a traffic
rush anywhere.

What I mean is that we cannot think we have ample resources everywhere and
- Everywhere: The user mobility makes it difficult to predict bandwidth
scarcity problems in some places.
- Always: A traffic rush may appear at a certain moment (e.g. the release of
a new game).

The idea is that TCM-TF is dormant, and it only gets activated when network
capacity becomes scarce. As Dan said in the BoF, TCM-TF provides a degree of
flexibility: you can exchange processing power and bandwidth when required.
In these situations, when a traffic rush occurs, why not activating TCM
optimization, and reducing the amount of pps and the bandwidth requirements
by optimizing the small-packet flows? Network operators have to transport
lots of small-packet flows, and this is not efficient (even in terms of
energy consumption, since header processing accounts for the majority of the
power requirements of a router).

Regarding the village example: community networks are really challenging
scenarios where VoIP and real-time services have a lot of problems to work
properly, so perhaps traffic optimization can be needed frequently (e.g. in
the afternoon when everyone is trying to use skype at home).

> > Perhaps we should take this into account when thinking about the
> > "TCM-TF negotiation". Suppose there are two TCM-optimizers that want
> > to create an optimized tunnel. During the negotiation they SHOULD
> > check if the number of
> > L3 hops between them is 1. In that case, they can avoid the tunnel,
> > and also the multiplexing (and multiplexing delay in turn). This could
> > be seen as a particular case of TCM-TF:
> >
> > - Compression layer: ROHC
> > - Multiplexing layer: send every single packet. No need for PPPMux
> > - Tunneling layer: no tunnel
> >
> > So perhaps we should also consider the "no multiplexing" and "no
> tunneling"
> > options in the protocol stack, in order to cover these cases.
> The point I'm trying to make is that I haven't seen *any* scenario that
> requires a multi-hop solution. And therefore to me what we have with
> ROHC seems to be just fine.
> Lars

Should we then update RFC4170 so as to consider ROHC instead of ECRTP? We
cannot forget that the idea of TCM-TF is to update and to broaden the scope
of RFC4170.

Thanks a lot!