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

Tim Chown <> Wed, 27 November 2013 14:58 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id BC1951ADBD4; Wed, 27 Nov 2013 06:58:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.222
X-Spam-Status: No, score=-1.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.779] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id S9fizihvDyJ7; Wed, 27 Nov 2013 06:58:34 -0800 (PST)
Received: from ( [IPv6:2001:630:d0:f102::25e]) by (Postfix) with ESMTP id A9BD11AE01A; Wed, 27 Nov 2013 06:58:32 -0800 (PST)
Received: from (localhost []) by (8.13.8/8.13.8) with ESMTP id rAREwSKb017844; Wed, 27 Nov 2013 14:58:28 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 rAREwSKb017844
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple;; s=201304; t=1385564308; bh=YB1gsbK3dushaMpjtAfpQa4lt28=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=fMq9gp/9fENR2HdFYE10LzvQSWvH4POo7ITU7LmIM1m/qfgj2It2KiixvzNByqEwk ycUqwBGLGI5ozWGuclg9zM8lRsmdfgsXlWFxot0geOJjdS9X8IHU7vm/cmARCzfRkv ggwAgeGObwiX6wJXNGsAtdO2GuWbHADYZV+mY43A=
Received: from ([2001:630:d0:f102:250:56ff:fea0:401]) by ( [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <> with ESMTP (valid=N/A) id pAQEwS0959603080Kp ret-id none; Wed, 27 Nov 2013 14:58:28 +0000
Received: from ( [] (may be forged)) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id rAREwQKb006809 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 27 Nov 2013 14:58:26 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Tim Chown <>
In-Reply-To: <00c301cee9ba$90d91de0$b28b59a0$>
Date: Wed, 27 Nov 2013 14:57:52 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|06b2756ee52c882bf688759bbb3e3404pAQEwS03tjc||>
References: <008c01cee5e1$9caa4590$d5fed0b0$> <> <01ee01cee6da$b05eb9a0$111c2ce0$> <> <01da01cee768$42926af0$c7b740d0$> <> <EMEW3|03e3a08ad2910f9d659aa138fccb1644pAM9wB03tjc||> <00c301cee9ba$90d91de0$b28b59a0$> <>
To: <>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=pAQEwS095960308000; tid=pAQEwS0959603080Kp; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: rAREwSKb017844
Cc:, 'Martin Stiemerling' <>,, '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: Wed, 27 Nov 2013 14:58:38 -0000

Hi Jose,

On 25 Nov 2013, at 08:44, Jose Saldana <> wrote:

> Hi, Tim.
> I think it is a good idea and we should definitely explain the scenarios in
> more detail.
> When you talk about a "deliverable which describes scenarios and
> requirements," do you mean another draft? In the current "TCM-TF reference
> model" draft, section 1.4 is about "Scenarios of application". Would it be
> enough if we improve that section according to what we have discussed in the
> last days?
> Regarding the potential effects on other protocols, do you think we should
> include that on the same draft?

I think the text now in the reference model v9 in point 8 covers the comment about scenarios.  It could be a separate draft, it could be the same draft. 

I'm not sure it addresses the issue of the impact on other protocols. This may be an axis on the design space?  And then to at least document the impact on other protocols of adopting the proposed combination of mechanisms at the three layers to be described in the reference model.  Examples of these issues were raised at the IETF87 BoF, and may come up again in a future BoF if the charter doesn't include consideration of them.

Will the reference model summarise the requirements, as distilled from the scenarios that are deemed to be in scope?


> Thanks a lot,
> Jose
>> -----Mensaje original-----
>> De: Tim Chown []
>> Enviado el: sábado, 23 de noviembre de 2013 10:58
>> Para:
>> CC: Eggert, Lars;;; Martin Stiemerling;
>> Reinaldo Penno (repenno); Spencer Dawkins
>> Asunto: Re: [tcmtf] Improved version (v8) of the TCM-TF charter draft
>> Hi,
>> On 22 Nov 2013, at 09:50, Jose Saldana <> wrote:
>>> 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 think it may be useful if the charter includes a deliverable which
> describes
>> scenarios and requirements. At present, the scenarios and existing
>> solutions are presented in points 1-4 of the charter, rather than being
> more
>> formally documented as part of the WG activities. Such a document could
>> explain why, from a requirements perspective, ROHC isn’t sufficient for
> the
>> use cases envisioned. It could also clarify what’s in scope, e.g. point 2
>> mentions satellite while point 10 mentions satellite as possible future
>> work. There’s been some good scenario discussion on the list recently
>> which could all be captured.
>> What’s also missing is analysis of the impact on other protocols of
> deploying
>> soemthing like this; this concern was raised at the previous BoF.
>> Tim