
From ietf@meetecho.com  Thu Aug  1 18:46:44 2013
Return-Path: <ietf@meetecho.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09A6421E83AA for <tcmtf@ietfa.amsl.com>; Thu,  1 Aug 2013 18:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.358
X-Spam-Level: 
X-Spam-Status: No, score=-0.358 tagged_above=-999 required=5 tests=[AWL=0.361,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 9wJ4QCtVgp2s for <tcmtf@ietfa.amsl.com>; Thu,  1 Aug 2013 18:46:28 -0700 (PDT)
Received: from smtpdg9.aruba.it (smtpdg8.aruba.it [62.149.158.238]) by ietfa.amsl.com (Postfix) with ESMTP id 36CE511E8219 for <tcmtf@ietf.org>; Thu,  1 Aug 2013 17:58:57 -0700 (PDT)
Received: from dell-tcastaldi ([130.129.66.20]) by smtpcmd03.ad.aruba.it with bizsmtp id 7cyw1m0040SDdTW01cywZX; Fri, 02 Aug 2013 02:58:56 +0200
Date: Fri, 2 Aug 2013 02:58:54 +0200 (CEST)
From: Meetecho Team <ietf@meetecho.com>
To: tcmtf@ietf.org
Message-ID: <1469234049.7.1375405134468.JavaMail.tcastaldi@dell-tcastaldi>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_6_915582172.1375405134465"
X-Mailman-Approved-At: Fri, 02 Aug 2013 00:08:56 -0700
Subject: [tcmtf] TCMTF session recording available
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 01:46:45 -0000

------=_Part_6_915582172.1375405134465
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear all,

the full recording (synchronized video, audio, slides and jabber room) of the 
TCMTF WG session at IETF 87 is available at the following URL:
http://ietf87.conf.meetecho.com/index.php/Recorded_Sessions#TCMTF

For the chair(s): please feel free to put the link to the recording in the minutes,
if you think this might be useful.

Cheers,
the Meetecho Team


This email has been automatically generated by The Meetecho Conferencing System


------=_Part_6_915582172.1375405134465--

From info@fap-ntic.org  Thu Aug  1 20:51:39 2013
Return-Path: <info@fap-ntic.org>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B91AB21E8051 for <tcmtf@ietfa.amsl.com>; Thu,  1 Aug 2013 20:51:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.502
X-Spam-Level: 
X-Spam-Status: No, score=0.502 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, URI_NOVOWEL=0.5]
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 MW7L1lI0m0Mx for <tcmtf@ietfa.amsl.com>; Thu,  1 Aug 2013 20:51:34 -0700 (PDT)
Received: from mail2.astralinternet.com (mail2.astralinternet.com [174.142.183.4]) by ietfa.amsl.com (Postfix) with ESMTP id 58F7611E80EF for <tcmtf@ietf.org>; Thu,  1 Aug 2013 20:51:34 -0700 (PDT)
Received: by mail2.astralinternet.com via HTTP; Thu, 1 Aug 2013 23:52:18 -0400
From: "info@fap-ntic.org" <info@fap-ntic.org>
To: <martin.stiemerling@neclab.eu>
Date: Thu, 1 Aug 2013 23:52:18 -0400
Message-ID: <62cc435d$3efd1c1e$5089971$@fap-ntic.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_48CFFA52.340ADB9B"
X-Originating-IP: [41.249.87.158]
X-Mailman-Approved-At: Fri, 02 Aug 2013 00:08:56 -0700
Cc: tcmtf@ietf.org
Subject: [tcmtf] Support to create the working group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: info@fap-ntic.org
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 03:51:39 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0001_48CFFA52.340ADB9B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit


Dear  Martin Stiemerling, 
Transport Area Director,

I have the honor to approach you about the creation of the working group 
TCM-TF which for us is very interesting for developing countries.For your 
information, our organization '' African Forum for the Promotion of New 
Information and Communication Technologies'' AFP-ICT work to our project  : 
''Training and Connecting Rural People'' (WSIS Project Prizes 2013 : 
E-Learning), which  enters its second phase where we think  the Tunneling, 
Compressing and Multiplexing Traffic Flow (TCM-TF) is interesting and 
better  adapt to the rural areas in general and in particular for 
developing  countries because TCMTF, a proposal for Optimizing the traffic 
of  real-time services and other flows based on small packets. It is based 
on grouping and compressing traffic flows, and it is ble to save 50% or 
even 60% of the bandwidth for some services. 
In many of our countries development project, we have a lot of problems 
regarding the provision of services (traffic flow). Especially in rural 
areas (our workplace for the development of ICT) encompassing a large part 
of the African population TCM-TF is a tool that can facilitate the flow of 
information.The creation of a working group TCM-TF can help reflect further 
on this very important issue and may facilitate some parts of the world 
whose needs are urgent and solve many of the problems we face. We have a 
great challenge that is to reduce the digital divide by promoting ICT. In 
Africa, the major urban centers are more developed, however, sustainable 
development that affects a large number of people must be in rural 
communities.

Best Regards

Nzengeli Papie
Coordinator
African Forum for the Promotion of the New Information and Communication 
Technologies 
(Forum Africain pour la Promotion des Nouvelles Technologies de 
l'Information et de la Communication) 
Mail : info@fap-ntic.org 
Web site : www.fap-ntic.org 
Brazzaville/Republic of Congo


------=_NextPart_000_0001_48CFFA52.340ADB9B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<span style=3D"font-family: Tahoma, Geneva, sans-serif; font-size: 10pt"><b=
r>Dear  Martin Stiemerling, <br>Transport Area Director,<br><br><span id=3D=
"result_box" class=3D"" lang=3D"en"><span class=3D"hps">I have the honor</s=
pan> <span class=3D"hps">to approach you</span> <span class=3D"hps">about</=
span> <span class=3D"hps">the creation</span> <span class=3D"hps">of the wo=
rking group</span> <span class=3D"hps atn">TCM-</span><span class=3D"">TF</=
span> <span class=3D"hps">which for us</span> <span class=3D"hps">is very i=
nteresting for</span> <span class=3D"hps">developing countries</span><span =
class=3D"">.</span><br class=3D""><br class=3D""><span class=3D"hps">For yo=
ur information,</span> <span class=3D"hps">our organization </span><span cl=
ass=3D"">''</span> <b><span class=3D"hps">African Forum</span> <span class=
=3D"hps">for the Promotion of</span> <span class=3D"hps">New&nbsp;</span><s=
pan class=3D"hps">Information</span> <span class=3D"hps">and Communication =
</span></b></span><span id=3D"result_box" class=3D"" lang=3D"en"><b><span c=
lass=3D"hps"><span id=3D"result_box" class=3D"" lang=3D"en"><span class=3D"=
hps">Technologies</span></span></span></b><span class=3D"">''</span> <span =
class=3D"hps atn">AFP-</span><span class=3D"">ICT</span> </span><span id=3D=
"result_box" class=3D"" lang=3D"en"><span class=3D"hps">work to our </span>=
</span><span id=3D"result_box" class=3D"" lang=3D"en"><span class=3D"hps">p=
roject&nbsp;</span> : <b>''<span class=3D"hps">Training</span><span class=
=3D""> </span><span class=3D"hps">and</span><span class=3D""> </span><span =
class=3D"hps">Connecting</span> <span class=3D"hps">Rural</span> <span clas=
s=3D"hps">People''</span></b> <span class=3D"hps">(WSIS</span> <span class=
=3D"hps">Project</span> <span class=3D"hps">Prizes</span> <span class=3D"hp=
s">2013 </span><span class=3D"atn">: E-</span><span class=3D"hps">Learning<=
/span><span class=3D"">), </span></span><span id=3D"result_box" class=3D"" =
lang=3D"en"><span class=3D""><span id=3D"result_box" class=3D"long_text"><s=
pan style=3D"background-color: rgb(255, 255, 255);" title=3D"Learning) qui =
entre dans sa deuxi=E8me phase o=F9 nous pensons que TCM-TF est int=E9ressa=
nt et mieux adapter aux milieux rural en particulier et en g=E9n=E9ral pour=
 les pays en d=E9veloppement car le TCMTF, a proposal for optimizing the tr=
affic of real-time services and other">which
 enters its second phase where we think </span></span></span></span><span i=
d=3D"result_box" class=3D"" lang=3D"en"><span class=3D""><span id=3D"result=
_box" class=3D"long_text"><span style=3D"background-color: rgb(255, 255, 25=
5);" title=3D"Learning) qui entre dans sa deuxi=E8me phase o=F9 nous penson=
s que TCM-TF est int=E9ressant et mieux adapter aux milieux rural en partic=
ulier et en g=E9n=E9ral pour les pays en d=E9veloppement car le TCMTF, a pr=
oposal for optimizing the traffic of real-time services and other"><span id=
=3D"result_box" class=3D"" lang=3D"en"> <span class=3D"hps atn">the </span>=
</span><span id=3D"result_box" class=3D"" lang=3D"en"><span class=3D"hps at=
n">Tunneling, Compressing and Multiplexing Traffic Flow (TCM-</span><span c=
lass=3D"">TF)</span></span> is interesting and better
 adapt to the rural areas in general and in particular for developing 
countries because TCMTF, a proposal for Optimizing the traffic of 
real-time services and other </span><span title=3D"flows based on small pac=
kets.">flows based on small packets. </span><span style=3D"background-color=
: rgb(255, 255, 255);" title=3D"It is based on grouping and compressing tra=
ffic flows, and it is able to save 50% or even 60% of the bandwidth for cer=
tain services.">It is based on grouping and compressing traffic flows, and =
it is ble to save 50% or even 60% of the bandwidth for some services.
<br>
</span></span></span></span><span id=3D"result_box" class=3D"" lang=3D"en">=
<span class=3D"hps"></span><br class=3D""><span class=3D"hps">In many of</s=
pan> <span class=3D"hps">our</span> <span class=3D"hps">countries</span> <s=
pan class=3D"hps">development project</span><span class=3D"">,</span> <span=
 class=3D"hps">we have a lot</span> <span class=3D"hps">of</span> <span cla=
ss=3D"hps">problems</span> <span class=3D"hps">regarding</span> <span class=
=3D"hps">the</span> <span class=3D"hps">provision of services</span> <span =
class=3D"hps atn">(</span><span class=3D"">traffic</span> <span class=3D"hp=
s">flow).</span> <span class=3D"hps">Especially</span> <span class=3D"hps">=
in rural areas</span> <span class=3D"hps atn">(</span><span class=3D"">our =
workplace</span> <span class=3D"hps">for the development of</span> <span cl=
ass=3D"hps">ICT)</span> <span class=3D"hps">encompassing</span> <span class=
=3D"hps">a large part of</span> <span class=3D"hps">the African</span> <spa=
n class=3D"hps">population</span> <span class=3D"hps atn">TCM-</span><span =
class=3D"">TF</span> <span class=3D"hps">is a tool that</span> <span class=
=3D"hps">can facilitate</span> <span class=3D"hps">the flow of</span> <span=
 class=3D"hps">information.</span><br class=3D""><br class=3D""><span class=
=3D"hps">The creation of</span> <span class=3D"hps">a working group</span> =
<span class=3D"hps atn">TCM-</span><span class=3D"">TF</span> <span class=
=3D"hps">can</span> <span class=3D"hps">help</span> <span class=3D"hps">ref=
lect further</span> <span class=3D"hps">on</span> <span class=3D"hps">this =
very important issue</span> <span class=3D"hps">and may</span> <span class=
=3D"hps">facilitate some</span> <span class=3D"hps">parts of the world</spa=
n> <span class=3D"hps">whose needs</span> <span class=3D"hps">are</span> <s=
pan class=3D"hps">urgent and</span> <span class=3D"hps">solve</span> <span =
class=3D"hps">many of the</span> <span class=3D"hps">problems</span> <span =
class=3D"hps">we face</span><span class=3D"">.</span> <span class=3D"hps">W=
e have a great</span> <span class=3D"hps">challenge that</span> <span class=
=3D"hps">is to reduce</span> <span class=3D"hps">the digital divide </span>=
</span><span id=3D"result_box" class=3D"" lang=3D"en"><span class=3D"hps"><=
span id=3D"result_box" class=3D"short_text" lang=3D"en"><span class=3D"hps"=
>by promoting</span> <span class=3D"hps">ICT</span></span></span><span clas=
s=3D"">.</span> <span class=3D"hps">In Africa,</span> <span class=3D"hps">t=
he major urban centers</span> <span class=3D"hps">are more developed</span>=
<span class=3D"">, however</span><span class=3D"">, sustainable development=
</span> <span class=3D"hps">that affects a</span> <span class=3D"hps">large=
 number of people</span> <span class=3D"hps">must be</span> <span class=3D"=
hps">in</span> <span class=3D"hps">rural communities.<br><br></span></span>=
Best Regards<br>
<br>
Nzengeli Papie<br>
Coordinator<br>
African Forum for the Promotion of the New Information and Communication Te=
chnologies <br>(Forum Africain pour la Promotion des Nouvelles Technologies=
 de l'Information et de la Communication) <br>Mail : <a href=3D"https://mai=
l.google.com/mail/h/vrv6evnqlyn1/?&amp;v=3Db&amp;cs=3Dwh&amp;to=3Dinfo@fap-=
ntic.org">info@fap-ntic.org</a> <br>Web site :<a href=3D"http://www.google.=
com/url?q=3Dhttp%3A%2F%2Fwww.fap-ntic.org&amp;sa=3DD&amp;sntz=3D1&amp;usg=
=3DAFQjCNGMWp7ho2v7_5WCdRpzeUahCSueEw" target=3D"_blank"> www.fap-ntic.org<=
/a> <br>Brazzaville/Republic of Congo<br><div></div></span>

------=_NextPart_000_0001_48CFFA52.340ADB9B--


From oloo6382@gmail.com  Fri Aug  2 02:45:49 2013
Return-Path: <oloo6382@gmail.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E15D911E812C for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 02:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.994
X-Spam-Level: 
X-Spam-Status: No, score=-0.994 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DEAR_SOMETHING=1.605, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 PLC9GqOb1B6o for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 02:45:49 -0700 (PDT)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 35A3611E8321 for <tcmtf@ietf.org>; Fri,  2 Aug 2013 02:45:49 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id n12so886425oag.39 for <tcmtf@ietf.org>; Fri, 02 Aug 2013 02:45:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=loKBswR9pTjeIpI7MeXHcq3Sb2Xvmyg0JMYagvlE4Bg=; b=pRzgGfhB/+PXvO7ViRR+1uoXXPWOV4f7SnkiDHt7An58LqscddmGDTV6WsDkinvNKw estGWSIHt9C8YbBraQCRSDeUp0tt3/ZGQRYKwWT2hFKx4tJTVWLdj4iRZoD0Hi1+mauL AECn77r9r8LSCWM4j1qkZAXTxeUjnnWQdVPi4cgnZ6cS3zWLOPKaqGz2t0c1s6lSZ4fv LWDWHUrhJSW0yBjvKmcwFVLfCe7tSwWYfrcAUionPgIjVf1OnkrxiZOGB93SEbbvmmFp j2IfmEe5P20fIswgxD7fG3AOli20pnij7wJ0ACGuyOjYZdDFoW2UwV/4ins3ShuDZVjt SrUg==
MIME-Version: 1.0
X-Received: by 10.50.7.1 with SMTP id f1mr199624iga.48.1375436748773; Fri, 02 Aug 2013 02:45:48 -0700 (PDT)
Received: by 10.50.180.231 with HTTP; Fri, 2 Aug 2013 02:45:48 -0700 (PDT)
Date: Fri, 2 Aug 2013 12:45:48 +0300
Message-ID: <CABGLsFjJVHKyGLNCnT3Sc1VhN76LKrtysgviZOez7M=zSPidjw@mail.gmail.com>
From: Charles Oloo <oloo6382@gmail.com>
To: tcmtf@ietf.org
Content-Type: multipart/alternative; boundary=089e0122edb8d282e304e2f3d251
Cc: martin.stiemerling@neclab.eu
Subject: [tcmtf] Working Group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 09:45:50 -0000

--089e0122edb8d282e304e2f3d251
Content-Type: text/plain; charset=ISO-8859-1

Dear Sir,

Am Chales Oloo. I was supposed to attend the IETF87 in Berlin, but could ot
make i due to various reasons. Nonetheless, Ive been following the
deliberations and vey pleased to learn of a plan to creating a WG for
TCMTF, as this technology will be beneficial to delvelpping countries like
Kenya where Bandwidth is very expensive and scarce. The idea is very
welcome and I fully support it.

Regards
Charles Oloo

--089e0122edb8d282e304e2f3d251
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Dear Sir,</div>
<div>=A0</div>
<div>Am Chales Oloo. I was supposed to attend the IETF87 in Berlin, but=A0c=
ould ot make i due to various reasons. Nonetheless, Ive been following the =
deliberations and vey pleased to learn of a plan to creating=A0a WG for TCM=
TF, as this technology will be beneficial to delvelpping countries like Ken=
ya where Bandwidth is very expensive and scarce. The idea is very welcome a=
nd I fully support it.</div>

<div>=A0</div>
<div>Regards=A0<br>Charles Oloo<br></div>

--089e0122edb8d282e304e2f3d251--

From papie_nzengeli@yahoo.fr  Fri Aug  2 01:43:23 2013
Return-Path: <papie_nzengeli@yahoo.fr>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D1F911E8318 for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 01:43:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.121
X-Spam-Level: *
X-Spam-Status: No, score=1.121 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_SORBS_WEB=0.619, URI_NOVOWEL=0.5]
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 ulmaX6HRMKvL for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 01:43:10 -0700 (PDT)
Received: from nm12-vm0.bullet.mail.ird.yahoo.com (nm12-vm0.bullet.mail.ird.yahoo.com [77.238.189.196]) by ietfa.amsl.com (Postfix) with SMTP id 746D121E8329 for <tcmtf@ietf.org>; Fri,  2 Aug 2013 01:40:01 -0700 (PDT)
Received: from [77.238.189.237] by nm12.bullet.mail.ird.yahoo.com with NNFMP; 02 Aug 2013 08:39:25 -0000
Received: from [212.82.98.65] by tm18.bullet.mail.ird.yahoo.com with NNFMP; 02 Aug 2013 08:39:24 -0000
Received: from [127.0.0.1] by omp1002.mail.ir2.yahoo.com with NNFMP; 02 Aug 2013 08:39:24 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 942756.40009.bm@omp1002.mail.ir2.yahoo.com
Received: (qmail 18503 invoked by uid 60001); 2 Aug 2013 08:39:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.fr; s=s1024; t=1375432764; bh=SeZNa8D5X7lpPp3Xy8pb0K5sbZFDkQRc8Q1aACcwUss=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type; b=gG5ZPHllWxSnO28OOmfWrSs3UUGlU/yI4f+Xf/1cwrofj7Kt/8CZ4/D2ujwYk+b2QbaiK63u7o4jrhvRSkdpheA+TtgY/1DU6HAd8sKXFI2GZIM1IgynlRRzEz47ks2zqjvXD1XDyx9EsGZ2oMXa5VrCpl1O3xnqEiHC4NbwvzQ=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type; b=0xb86FgDTOngpWsIiBuI7BH6sTRzP1QnENlT3jRSRwvn1U10Ap5NixesBQercBvlA8jYjn3GyiIxyK3YqxY2iv2pMeUcnuHSP6T4gEQyeEiunc6H9RlXm6Iiqv583VViuxFMuH+da1FODJjcc0BjKPQgrWnqEcGsCw0SfoXoje0=;
X-YMail-OSG: 63imyx0VM1kGyMEIZDwspfnbj2ISkVnhQKzzrTmfE0L8flv qaOfiKKwgFlaji.HCmojOwTGIkg.Uv1Ieimik8.p5MaybLOm4M3egU6may1A t27tZ_5r_dMhCtRdek44rRWEhqgmz1emOkmhYZDt4xbJqNJIqYRXmYAO.U3z o9yuiL6UTpL3q9gJiOLOX0QX3vUvLLcQnyfP5RRoftx92CxCiMOKlpDYgGIq 9HKe4SV36DpOhfuC8HtGqyvPvSU7K69W3GV4oEntLqGPWfsIZwXstQ_CnqHM mvAjRGwxHgYBdmg5QrEgDe7Cixv9wUPbuVymkIEgEbc7yWlq9Tzr7HIytYpq 4ru.l02GAgO.Cvsqtvd9rs7A1.tbDQtiE.sH95bxv5VPPIhIH7zilsPxwZzs Aj4Sl7kQxda1i2OdATnFV223_7peMfYjBKPik0HB1tekqm4x_1aN8RAjMYrU ZqLlkCSUiEsTd_TTeaFQdw8EYaB.xF8Zxk7V244eTATNjLu6eQd5VpChayo0 iBDpVYMDfN2VmF2rQomZPCqLFw1H8F8UQwPLcVx.pM322p48TRCFSvEuBQuT jqrTdot5QvYgLWw9TCRp_Hj7O4v3eLispBIqFwyO.Ghn0DV6TyIDsPB_2ynW W2c67WCY1K_oWsAKQ8_JWbzy1Ceg7bel1l76q0UJsGuRzGFYgrGQYK_ij_M7 XCRj7gSd2Xinz7IOEDAGH13tno3XY7Gfqbid4y3ZVp2z1m4RruFB4E25lxcw PngMUMTQB3.X3vZGHKw2KyxdLIm4l7CCabf7O95uQ2z7QBaeTn6j7Wtu_neQ cOQxz4L_dNJOnJC9FVVDhD1w1wTNjlH5Ne1TnlRM60kifRidB_H3dlrQ7tCh 54vw8NyVpgpeULHGUHUbRke9awjg_aCXnjsbXkRkJokKd3rINW5lD4.xFLCZ AevSZgiRJu0jOQhKivZ1ibrNUXkqhPyNa4FoUKvNrKfOw
Received: from [41.249.33.62] by web171806.mail.ir2.yahoo.com via HTTP; Fri, 02 Aug 2013 09:39:24 BST
X-Rocket-MIMEInfo: 002.001, CgpEZWFyICBNYXJ0aW4gU3RpZW1lcmxpbmcsIApUcmFuc3BvcnQgQXJlYSBEaXJlY3RvciwKCkkgaGF2ZSB0aGUgaG9ub3IgdG8gYXBwcm9hY2ggeW91IGFib3V0IHRoZSBjcmVhdGlvbiBvZiB0aGUgd29ya2luZyBncm91cCBUQ00tVEYgd2hpY2ggZm9yIHVzIGlzIHZlcnkgaW50ZXJlc3RpbmcgZm9yIGRldmVsb3BpbmcgY291bnRyaWVzLgoKRm9yIHlvdXIgaW5mb3JtYXRpb24sIG91ciBvcmdhbml6YXRpb24gJycgQWZyaWNhbiBGb3J1bSBmb3IgdGhlIFByb21vdGlvbiBvZiBOZXfCoEluZm9ybWF0aW9uIGEBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.152.567
Message-ID: <1375432764.16091.YahooMailNeo@web171806.mail.ir2.yahoo.com>
Date: Fri, 2 Aug 2013 09:39:24 +0100 (BST)
From: papie nzengeli <papie_nzengeli@yahoo.fr>
To: "martin.stiemerling@neclab.eu" <martin.stiemerling@neclab.eu>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-970193273-104048855-1375432764=:16091"
X-Mailman-Approved-At: Fri, 02 Aug 2013 02:56:43 -0700
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: [tcmtf] Support to create the working group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: papie nzengeli <papie_nzengeli@yahoo.fr>
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 08:43:23 -0000

---970193273-104048855-1375432764=:16091
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0A=0ADear  Martin Stiemerling, =0ATransport Area Director,=0A=0AI have the=
 honor to approach you about the creation of the working group TCM-TF which=
 for us is very interesting for developing countries.=0A=0AFor your informa=
tion, our organization '' African Forum for the Promotion of New=A0Informat=
ion and Communication Technologies'' AFP-ICT work to our project=A0 : ''Tra=
iningandConnecting Rural People'' (WSIS Project Prizes 2013 : E-Learning), =
which enters its second phase where we think the Tunneling, Compressing and=
 Multiplexing Traffic Flow (TCM-TF) is interesting and better adapt to the =
rural areas in general and in particular for developing=0Acountries because=
 TCMTF, a proposal for Optimizing the traffic of=0Areal-time services and o=
ther flows based on small packets. It is based on grouping and compressing =
traffic flows, and it is ble to save 50% or even 60% of the bandwidth for s=
ome services. =0A=0AIn many of our countries development project, we have a=
 lot of problems regarding the provision of services (traffic flow). Especi=
ally in rural areas (our workplace for the development of ICT) encompassing=
 a large part of the African population TCM-TF is a tool that can facilitat=
e the flow of information.=0A=0AThe creation of a working group TCM-TF can =
help reflect further on this very important issue and may facilitate some p=
arts of the world whose needs are urgent and solve many of the problems we =
face. We have a great challenge that is to reduce the digital divide by pro=
moting ICT. In Africa, the major urban centers are more developed, however,=
 sustainable development that affects a large number of people must be in r=
ural communities.=0A=0ABest Regards=0A=0ANzengeli Papie=0ACoordinator=0AAfr=
ican Forum for the Promotion of the New Information and Communication Techn=
ologies =0A(Forum Africain pour la Promotion des Nouvelles Technologies de =
l'Information et de la Communication) =0AMail : info@fap-ntic.org =0AWeb si=
te :www.fap-ntic.org =0ABrazzaville/Republic of Congo 
---970193273-104048855-1375432764=:16091
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ar=
ial, helvetica, sans-serif;font-size:10pt"><div><span><br></span></div><div=
><span style=3D"font-family:Tahoma, Geneva, sans-serif;font-size:10pt;"><sp=
an style=3D"font-family:Tahoma, Geneva, sans-serif;font-size:10pt;">Dear  M=
artin Stiemerling, <br>Transport Area Director,<br><br><span id=3D"yiv52292=
1999result_box" class=3D"yiv522921999" lang=3D"en"><span class=3D"yiv522921=
999hps">I have the honor</span> <span class=3D"yiv522921999hps">to approach=
 you</span> <span class=3D"yiv522921999hps">about</span> <span class=3D"yiv=
522921999hps">the creation</span> <span class=3D"yiv522921999hps">of the wo=
rking group</span> <span class=3D"yiv522921999hps yiv522921999atn">TCM-</sp=
an><span class=3D"yiv522921999">TF</span> <span class=3D"yiv522921999hps">w=
hich for us</span> <span class=3D"yiv522921999hps">is very interesting for<=
/span> <span class=3D"yiv522921999hps">developing countries</span><span
 class=3D"yiv522921999">.</span><br class=3D"yiv522921999"><br class=3D"yiv=
522921999"><span class=3D"yiv522921999hps">For your information,</span> <sp=
an class=3D"yiv522921999hps">our organization </span><span class=3D"yiv5229=
21999">''</span> <b><span class=3D"yiv522921999hps">African Forum</span> <s=
pan class=3D"yiv522921999hps">for the Promotion of</span> <span class=3D"yi=
v522921999hps">New&nbsp;</span><span class=3D"yiv522921999hps">Information<=
/span> <span class=3D"yiv522921999hps">and Communication </span></b></span>=
<span id=3D"yiv522921999result_box" class=3D"yiv522921999" lang=3D"en"><b><=
span class=3D"yiv522921999hps"><span id=3D"yiv522921999result_box" class=3D=
"yiv522921999" lang=3D"en"><span class=3D"yiv522921999hps">Technologies</sp=
an></span></span></b><span class=3D"yiv522921999">''</span> <span class=3D"=
yiv522921999hps yiv522921999atn">AFP-</span><span class=3D"yiv522921999">IC=
T</span> </span><span id=3D"yiv522921999result_box" class=3D"yiv522921999" =
lang=3D"en"><span
 class=3D"yiv522921999hps">work to our </span></span><span id=3D"yiv5229219=
99result_box" class=3D"yiv522921999" lang=3D"en"><span class=3D"yiv52292199=
9hps">project&nbsp;</span> : <b>''<span class=3D"yiv522921999hps">Training<=
/span><span class=3D"yiv522921999"> </span><span class=3D"yiv522921999hps">=
and</span><span class=3D"yiv522921999"> </span><span class=3D"yiv522921999h=
ps">Connecting</span> <span class=3D"yiv522921999hps">Rural</span> <span cl=
ass=3D"yiv522921999hps">People''</span></b> <span class=3D"yiv522921999hps"=
>(WSIS</span> <span class=3D"yiv522921999hps">Project</span> <span class=3D=
"yiv522921999hps">Prizes</span> <span class=3D"yiv522921999hps">2013 </span=
><span class=3D"yiv522921999atn">: E-</span><span class=3D"yiv522921999hps"=
>Learning</span><span class=3D"yiv522921999">), </span></span><span id=3D"y=
iv522921999result_box" class=3D"yiv522921999" lang=3D"en"><span class=3D"yi=
v522921999"><span id=3D"yiv522921999result_box" class=3D"yiv522921999long_t=
ext"><span style=3D"background-color:rgb(255,
 255, 255);" title=3D"Learning) qui entre dans sa deuxi=E8me phase o=F9 nou=
s pensons que TCM-TF est int=E9ressant et mieux adapter aux milieux rural e=
n particulier et en g=E9n=E9ral pour les pays en d=E9veloppement car le TCM=
TF, a proposal for optimizing the traffic of real-time services and other">=
which=0A enters its second phase where we think </span></span></span></span=
><span id=3D"yiv522921999result_box" class=3D"yiv522921999" lang=3D"en"><sp=
an class=3D"yiv522921999"><span id=3D"yiv522921999result_box" class=3D"yiv5=
22921999long_text"><span style=3D"background-color:rgb(255, 255, 255);" tit=
le=3D"Learning) qui entre dans sa deuxi=E8me phase o=F9 nous pensons que TC=
M-TF est int=E9ressant et mieux adapter aux milieux rural en particulier et=
 en g=E9n=E9ral pour les pays en d=E9veloppement car le TCMTF, a proposal f=
or optimizing the traffic of real-time services and other"><span id=3D"yiv5=
22921999result_box" class=3D"yiv522921999" lang=3D"en"> <span class=3D"yiv5=
22921999hps yiv522921999atn">the </span></span><span id=3D"yiv522921999resu=
lt_box" class=3D"yiv522921999" lang=3D"en"><span class=3D"yiv522921999hps y=
iv522921999atn">Tunneling, Compressing and Multiplexing Traffic Flow (TCM-<=
/span><span class=3D"yiv522921999">TF)</span></span> is interesting and bet=
ter=0A adapt to the rural areas in general and in particular for developing=
=0Acountries because TCMTF, a proposal for Optimizing the traffic of=0Areal=
-time services and other </span><span title=3D"flows based on small packets=
.">flows based on small packets. </span><span style=3D"background-color:rgb=
(255, 255, 255);" title=3D"It is based on grouping and compressing traffic =
flows, and it is able to save 50% or even 60% of the bandwidth for certain =
services.">It is based on grouping and compressing traffic flows, and it is=
 ble to save 50% or even 60% of the bandwidth for some services.=0A<br>=0A<=
/span></span></span></span><span id=3D"yiv522921999result_box" class=3D"yiv=
522921999" lang=3D"en"><span class=3D"yiv522921999hps"></span><br class=3D"=
yiv522921999"><span class=3D"yiv522921999hps">In many of</span> <span class=
=3D"yiv522921999hps">our</span> <span class=3D"yiv522921999hps">countries</=
span> <span class=3D"yiv522921999hps">development project</span><span class=
=3D"yiv522921999">,</span> <span class=3D"yiv522921999hps">we have a lot</s=
pan> <span class=3D"yiv522921999hps">of</span> <span class=3D"yiv522921999h=
ps">problems</span> <span class=3D"yiv522921999hps">regarding</span> <span =
class=3D"yiv522921999hps">the</span> <span class=3D"yiv522921999hps">provis=
ion of services</span> <span class=3D"yiv522921999hps yiv522921999atn">(</s=
pan><span class=3D"yiv522921999">traffic</span> <span class=3D"yiv522921999=
hps">flow).</span> <span class=3D"yiv522921999hps">Especially</span> <span =
class=3D"yiv522921999hps">in rural areas</span> <span class=3D"yiv522921999=
hps yiv522921999atn">(</span><span
 class=3D"yiv522921999">our workplace</span> <span class=3D"yiv522921999hps=
">for the development of</span> <span class=3D"yiv522921999hps">ICT)</span>=
 <span class=3D"yiv522921999hps">encompassing</span> <span class=3D"yiv5229=
21999hps">a large part of</span> <span class=3D"yiv522921999hps">the Africa=
n</span> <span class=3D"yiv522921999hps">population</span> <span class=3D"y=
iv522921999hps yiv522921999atn">TCM-</span><span class=3D"yiv522921999">TF<=
/span> <span class=3D"yiv522921999hps">is a tool that</span> <span class=3D=
"yiv522921999hps">can facilitate</span> <span class=3D"yiv522921999hps">the=
 flow of</span> <span class=3D"yiv522921999hps">information.</span><br clas=
s=3D"yiv522921999"><br class=3D"yiv522921999"><span class=3D"yiv522921999hp=
s">The creation of</span> <span class=3D"yiv522921999hps">a working group</=
span> <span class=3D"yiv522921999hps yiv522921999atn">TCM-</span><span clas=
s=3D"yiv522921999">TF</span> <span class=3D"yiv522921999hps">can</span> <sp=
an
 class=3D"yiv522921999hps">help</span> <span class=3D"yiv522921999hps">refl=
ect further</span> <span class=3D"yiv522921999hps">on</span> <span class=3D=
"yiv522921999hps">this very important issue</span> <span class=3D"yiv522921=
999hps">and may</span> <span class=3D"yiv522921999hps">facilitate some</spa=
n> <span class=3D"yiv522921999hps">parts of the world</span> <span class=3D=
"yiv522921999hps">whose needs</span> <span class=3D"yiv522921999hps">are</s=
pan> <span class=3D"yiv522921999hps">urgent and</span> <span class=3D"yiv52=
2921999hps">solve</span> <span class=3D"yiv522921999hps">many of the</span>=
 <span class=3D"yiv522921999hps">problems</span> <span class=3D"yiv52292199=
9hps">we face</span><span class=3D"yiv522921999">.</span> <span class=3D"yi=
v522921999hps">We have a great</span> <span class=3D"yiv522921999hps">chall=
enge that</span> <span class=3D"yiv522921999hps">is to reduce</span> <span =
class=3D"yiv522921999hps">the digital divide </span></span><span id=3D"yiv5=
22921999result_box"
 class=3D"yiv522921999" lang=3D"en"><span class=3D"yiv522921999hps"><span i=
d=3D"yiv522921999result_box" class=3D"yiv522921999short_text" lang=3D"en"><=
span class=3D"yiv522921999hps">by promoting</span> <span class=3D"yiv522921=
999hps">ICT</span></span></span><span class=3D"yiv522921999">.</span> <span=
 class=3D"yiv522921999hps">In Africa,</span> <span class=3D"yiv522921999hps=
">the major urban centers</span> <span class=3D"yiv522921999hps">are more d=
eveloped</span><span class=3D"yiv522921999">, however</span><span class=3D"=
yiv522921999">, sustainable development</span> <span class=3D"yiv522921999h=
ps">that affects a</span> <span class=3D"yiv522921999hps">large number of p=
eople</span> <span class=3D"yiv522921999hps">must be</span> <span class=3D"=
yiv522921999hps">in</span> <span class=3D"yiv522921999hps">rural communitie=
s.<br><br></span></span>Best Regards<br>=0A<br>=0ANzengeli Papie<br>=0ACoor=
dinator<br>=0AAfrican Forum for the Promotion of the New Information and Co=
mmunication Technologies <br>(Forum Africain pour la Promotion des Nouvelle=
s Technologies de l'Information et de la Communication) <br>Mail : <a rel=
=3D"nofollow" target=3D"_blank" href=3D"https://mail.google.com/mail/h/vrv6=
evnqlyn1/?&amp;v=3Db&amp;cs=3Dwh&amp;to=3Dinfo@fap-ntic.org">info@fap-ntic.=
org</a> <br>Web site :<a rel=3D"nofollow" target=3D"_blank" href=3D"http://=
www.google.com/url?q=3Dhttp%3A%2F%2Fwww.fap-ntic.org&amp;sa=3DD&amp;sntz=3D=
1&amp;usg=3DAFQjCNGMWp7ho2v7_5WCdRpzeUahCSueEw"> www.fap-ntic.org</a> <br>B=
razzaville/Republic of Congo</span></span> </div></div></body></html>
---970193273-104048855-1375432764=:16091--

From ggx@gigix.net  Fri Aug  2 03:35:28 2013
Return-Path: <ggx@gigix.net>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A69511E825F for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 03:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Tteui155CDgk for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 03:35:23 -0700 (PDT)
Received: from mail-pb0-f42.google.com (mail-pb0-f42.google.com [209.85.160.42]) by ietfa.amsl.com (Postfix) with ESMTP id 4DBF411E82B5 for <tcmtf@ietf.org>; Fri,  2 Aug 2013 03:34:58 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un15so538537pbc.15 for <tcmtf@ietf.org>; Fri, 02 Aug 2013 03:34:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version:x-mailer:x-gm-message-state; bh=8WjUEwWi4/o0rE83PLLJkmW8uOdhCJ1P0Nytr+PykJo=; b=FHTNOgyd7GyJey+8KZExCXRmSyPSGXQWPDY4Ku48A0IWQq8PbhP838KNEcAHuAVxKa rjSuG1CcffRtMLWVyMr1aG8/01ZnDOEN7qhJxnUtn2mIoXv/FmLENYTgJ6i1NcbqvLMU SmycFTVFI9YtLHrzbCNfXlq2xTv3I2C8UbLpMR6a7mkyFUtfwdP9k3m2ypuGfkmUWA4A 10ZVBeKBaPE09tgKxykQ7C0gwAcPAgdE1J+HmqwPnLghrSDnR5yLJ0Be4dADR9bVNe5H mVhyOWDSXFu0LXUtzU/0HOvsE5p2vOLytra0biWmQy8CERR0uNiA3yfATndMtw0MC1Tc ddvQ==
X-Received: by 10.66.179.143 with SMTP id dg15mr9690686pac.52.1375439698012; Fri, 02 Aug 2013 03:34:58 -0700 (PDT)
Received: from ?IPv6:2001:df8::32:3058:84d6:8952:17d7? ([2001:df8:0:32:3058:84d6:8952:17d7]) by mx.google.com with ESMTPSA id sx7sm9494199pbc.41.2013.08.02.03.34.56 for <tcmtf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 03:34:57 -0700 (PDT)
From: Luigi Iannone <ggx@gigix.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net>
Date: Fri, 2 Aug 2013 06:34:54 -0400
To: "tcmtf@ietf.org" <tcmtf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQncqMjnCfHyV8eGVQJ77MERuGUQ9jLzZJq9+cE5FH5WmrTK3+6EJKcGB+M5bSY02MYIEbS3
Subject: [tcmtf] BoF feedback
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 10:35:28 -0000

Hi,

I was thinking a little bit about the turn the BoF took yesterday, going =
a bit off topic IMHO.

At a certain point people were going to the mic to explain yet another =
scenario where TCMTF would not work or is not useful.

It is obvious to me that such scenarios exist, but  the goal of TCMTF is =
not to provide something that will be applied to all packets under a =
certain size. =20

It is also obvious to me that scenarios where TCMTF is beneficial exist =
as well. Goal of TCMTF should be to provide the right mechanism for =
those scenarios.

A key point to discuss in TCMTF is how we identify and select the flow =
we want to be multiplexed on a single compressed tunnel.

All of this to say that we should not focus or scenarios where TCMTF =
doesn't help but rather to answer the following question:

Are there scenarios and use cases where TCMTF provides benefits?

The answer IMHO is YES so some work should be done.

Just let me add that,  before thinking how to encapsulate we should =
answer: How do we select the flows we want to encamp?=20

So that we are sure that we do not touch traffic that will suffer =
because of TCMTF.

Just my thoughts after the BoF.

ciao

Luigi

  =20=

From touch@isi.edu  Fri Aug  2 10:58:48 2013
Return-Path: <touch@isi.edu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A37421F9654 for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 10:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.719
X-Spam-Level: 
X-Spam-Status: No, score=-105.719 tagged_above=-999 required=5 tests=[AWL=0.380, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, URI_NOVOWEL=0.5, USER_IN_WHITELIST=-100]
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 yuYUD0ADSW6S for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 10:58:43 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 8FB5721F9655 for <tcmtf@ietf.org>; Fri,  2 Aug 2013 10:58:43 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r72HwMSK020869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Aug 2013 10:58:22 -0700 (PDT)
Message-ID: <51FBF33D.8000401@isi.edu>
Date: Fri, 02 Aug 2013 10:58:21 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: info@fap-ntic.org
References: <62cc435d$3efd1c1e$5089971$@fap-ntic.org>
In-Reply-To: <62cc435d$3efd1c1e$5089971$@fap-ntic.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcmtf@ietf.org, martin.stiemerling@neclab.eu
Subject: Re: [tcmtf] Support to create the working group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 17:58:48 -0000

Hi, all,

FWIW, I don't understand why this is being requested of the TRANSPORT area.

Tunnels such as this ought to be the purview of INTAREA. I admit I 
remain confused as to why so many tunneling protocols are in ROUTING, 
but regardless neither is TRANSPORT.

Joe

On 8/1/2013 8:52 PM, info@fap-ntic.org wrote:
>
> Dear Martin Stiemerling,
> Transport Area Director,
>
> I have the honor to approach you about the creation of the working group
> TCM-TF which for us is very interesting for developing countries.
>
> For your information, our organization '' *African Forum for the
> Promotion of New Information and Communication **Technologies*'' AFP-ICT
> work to our project : *''TrainingandConnecting Rural People''* (WSIS
> Project Prizes 2013 : E-Learning), which enters its second phase where
> we think the Tunneling, Compressing and Multiplexing Traffic Flow
> (TCM-TF) is interesting and better adapt to the rural areas in general
> and in particular for developing countries because TCMTF, a proposal for
> Optimizing the traffic of real-time services and other flows based on
> small packets. It is based on grouping and compressing traffic flows,
> and it is ble to save 50% or even 60% of the bandwidth for some services.
>
> In many of our countries development project, we have a lot of problems
> regarding the provision of services (traffic flow). Especially in rural
> areas (our workplace for the development of ICT) encompassing a large
> part of the African population TCM-TF is a tool that can facilitate the
> flow of information.
>
> The creation of a working group TCM-TF can help reflect further on this
> very important issue and may facilitate some parts of the world whose
> needs are urgent and solve many of the problems we face. We have a great
> challenge that is to reduce the digital divide by promoting ICT. In
> Africa, the major urban centers are more developed, however, sustainable
> development that affects a large number of people must be in rural
> communities.
>
> Best Regards
>
> Nzengeli Papie
> Coordinator
> African Forum for the Promotion of the New Information and Communication
> Technologies
> (Forum Africain pour la Promotion des Nouvelles Technologies de
> l'Information et de la Communication)
> Mail : info@fap-ntic.org
> <https://mail.google.com/mail/h/vrv6evnqlyn1/?&v=b&cs=wh&to=info@fap-ntic.org>
>
> Web site :www.fap-ntic.org
> <http://www.google.com/url?q=http%3A%2F%2Fwww.fap-ntic.org&sa=D&sntz=1&usg=AFQjCNGMWp7ho2v7_5WCdRpzeUahCSueEw>
>
> Brazzaville/Republic of Congo
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>

From touch@isi.edu  Fri Aug  2 11:00:44 2013
Return-Path: <touch@isi.edu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD73D11E8101 for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 11:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.987
X-Spam-Level: 
X-Spam-Status: No, score=-105.987 tagged_above=-999 required=5 tests=[AWL=0.612, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 XPFuH3eojJMb for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 11:00:39 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 0CAE111E80E8 for <tcmtf@ietf.org>; Fri,  2 Aug 2013 11:00:39 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r72I0DjA021101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Aug 2013 11:00:13 -0700 (PDT)
Message-ID: <51FBF3AD.4020301@isi.edu>
Date: Fri, 02 Aug 2013 11:00:13 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Luigi Iannone <ggx@gigix.net>
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net>
In-Reply-To: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] BoF feedback
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 18:00:44 -0000

FWIW, I'd like to see how/whether this can be cast as an extension to SEAL.

It'd be useful not to have to reinvent the many wheel-like parts of this 
that could leverage existing tunneling capabilities.

Joe

On 8/2/2013 3:34 AM, Luigi Iannone wrote:
> Hi,
>
> I was thinking a little bit about the turn the BoF took yesterday, going a bit off topic IMHO.
>
> At a certain point people were going to the mic to explain yet another scenario where TCMTF would not work or is not useful.
>
> It is obvious to me that such scenarios exist, but  the goal of TCMTF is not to provide something that will be applied to all packets under a certain size.
>
> It is also obvious to me that scenarios where TCMTF is beneficial exist as well. Goal of TCMTF should be to provide the right mechanism for those scenarios.
>
> A key point to discuss in TCMTF is how we identify and select the flow we want to be multiplexed on a single compressed tunnel.
>
> All of this to say that we should not focus or scenarios where TCMTF doesn't help but rather to answer the following question:
>
> Are there scenarios and use cases where TCMTF provides benefits?
>
> The answer IMHO is YES so some work should be done.
>
> Just let me add that,  before thinking how to encapsulate we should answer: How do we select the flows we want to encamp?
>
> So that we are sure that we do not touch traffic that will suffer because of TCMTF.
>
> Just my thoughts after the BoF.
>
> ciao
>
> Luigi
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>

From mperumal@cisco.com  Fri Aug  2 13:25:10 2013
Return-Path: <mperumal@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7C1D21E8086 for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 13:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 5mn5Sxio5SJM for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 13:25:06 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 492CA11E8102 for <tcmtf@ietf.org>; Fri,  2 Aug 2013 13:25:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2542; q=dns/txt; s=iport; t=1375475105; x=1376684705; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=9twBa99CTFUL/UrP1jinD9lsgQuZurSFybfUEqSH0Io=; b=RIyzbqPMpOm+Ejpz2KuoawNb1jHIHxB5kIE+s9gHSWHsfM+r9Frlhoir 6J4H5CHNrP55c31J5yr1ZuLyWDgfIpNkwJJT/BizGT7sdyIY+YKCHuVWB dA5nSAMuudDV7QJT+9/ReGRIkL7CyZOGm5ic6YE14MiMpO/34Tou7Lz8/ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwFAD0U/FGtJXG8/2dsb2JhbABQCoMGNVC/DYEeFnSCJAEBAQEDAQEBNzQEEwQCAQgOAwQBAQsUCQcnCxQJCAIEARIIiAgMuQMEjlYEgQ04BoMTdAOpLYMXgWhC
X-IronPort-AV: E=Sophos;i="4.89,803,1367971200"; d="scan'208";a="239917706"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-9.cisco.com with ESMTP; 02 Aug 2013 20:25:04 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r72KP3oN020218 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 Aug 2013 20:25:03 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.27]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Fri, 2 Aug 2013 15:25:03 -0500
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: Luigi Iannone <ggx@gigix.net>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] BoF feedback
Thread-Index: AQHOj2wD5rXoL5C1bkKA8Y3n2L5aYJmCTy4A
Date: Fri, 2 Aug 2013 20:25:02 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE2241CFE0C@xmb-rcd-x02.cisco.com>
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net>
In-Reply-To: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.33.23]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [tcmtf] BoF feedback
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 20:25:11 -0000

TCMTF has clear and demonstrated benefits for VoIP and online gaming. CRTP/=
ECRTP has already enjoyed some success in reducing VoIP bandwidth over poin=
t-to-point WAN links, especially in those regions where access bandwidth is=
 considerably expensive. TCMFT is a natural extension that encompasses bett=
er compression and tunneling technologies to achieve similar goals.=20

The concerns raised during the BoF seemed in relation to generalizing it fo=
r other kinds of traffic and TCP in particular. This generalization though =
important (especially in the context of Internet of Things as echoed by Mic=
hael Ramalho during the BoF) could probably be deferred for future work (TC=
MTF2.0?) and the scope limited to VoIP and online gaming to begin with, IMO=
. As we work through the limited scope, how (and how not) to apply it for o=
ther kinds of traffic should become more clear, I think.

Muthu

|-----Original Message-----
|From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of =
Luigi Iannone
|Sent: Friday, August 02, 2013 4:05 PM
|To: tcmtf@ietf.org
|Subject: [tcmtf] BoF feedback
|
|Hi,
|
|I was thinking a little bit about the turn the BoF took yesterday, going a=
 bit off topic IMHO.
|
|At a certain point people were going to the mic to explain yet another sce=
nario where TCMTF would not
|work or is not useful.
|
|It is obvious to me that such scenarios exist, but  the goal of TCMTF is n=
ot to provide something that
|will be applied to all packets under a certain size.
|
|It is also obvious to me that scenarios where TCMTF is beneficial exist as=
 well. Goal of TCMTF should
|be to provide the right mechanism for those scenarios.
|
|A key point to discuss in TCMTF is how we identify and select the flow we =
want to be multiplexed on a
|single compressed tunnel.
|
|All of this to say that we should not focus or scenarios where TCMTF doesn=
't help but rather to answer
|the following question:
|
|Are there scenarios and use cases where TCMTF provides benefits?
|
|The answer IMHO is YES so some work should be done.
|
|Just let me add that,  before thinking how to encapsulate we should answer=
: How do we select the flows
|we want to encamp?
|
|So that we are sure that we do not touch traffic that will suffer because =
of TCMTF.
|
|Just my thoughts after the BoF.
|
|ciao
|
|Luigi
|
|
|_______________________________________________
|tcmtf mailing list
|tcmtf@ietf.org
|https://www.ietf.org/mailman/listinfo/tcmtf

From wes@mti-systems.com  Fri Aug  2 19:05:28 2013
Return-Path: <wes@mti-systems.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D34311E813F for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 19:05:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 mnwFkoEuV8FF for <tcmtf@ietfa.amsl.com>; Fri,  2 Aug 2013 19:05:22 -0700 (PDT)
Received: from atl4mhob07.myregisteredsite.com (atl4mhob07.myregisteredsite.com [209.17.115.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1F95921E80B8 for <tcmtf@ietf.org>; Fri,  2 Aug 2013 19:05:17 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.206]) by atl4mhob07.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r7325Bf9025395 for <tcmtf@ietf.org>; Fri, 2 Aug 2013 22:05:11 -0400
Received: (qmail 7058 invoked by uid 0); 3 Aug 2013 02:05:11 -0000
X-TCPREMOTEIP: 69.81.143.143
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.122?) (wes@mti-systems.com@69.81.143.143) by 0 with ESMTPA; 3 Aug 2013 02:05:11 -0000
Message-ID: <51FC653A.8050206@mti-systems.com>
Date: Fri, 02 Aug 2013 22:04:42 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
References: <62cc435d$3efd1c1e$5089971$@fap-ntic.org> <51FBF33D.8000401@isi.edu>
In-Reply-To: <51FBF33D.8000401@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: tcmtf@ietf.org, info@fap-ntic.org, martin.stiemerling@neclab.eu
Subject: Re: [tcmtf] Support to create the working group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 02:05:28 -0000

On 8/2/2013 1:58 PM, Joe Touch wrote:
> Hi, all,
> 
> FWIW, I don't understand why this is being requested of the TRANSPORT area.
> 
> Tunnels such as this ought to be the purview of INTAREA. I admit I
> remain confused as to why so many tunneling protocols are in ROUTING,
> but regardless neither is TRANSPORT.
> 


Hi Joe; here are a few reasons I can think of for justifying
transport as the area:

- the intent was not to invent new tunnel protocols, but to use
  existing ones as part of a stack
- all of the possible downsides that people brought up during
  the meeting are impacts to the transport protocol; so there is
  a tight coupling between transport configuration and what the
  recommendation for performing TCMTF on a flow should be
- many of the design considerations are directly related to things
  transport has dealt with in the past like delayed ACKs, ACK
  compression, buffer sizing, etc.
- PILC and PEP documentation were done in the transport area
- RoHC was done in the transport area
- PMTUD was in transport area (since you noted that this is a
  an additional concern)

In my opinion, if this is done, it should be in transport.

-- 
Wes Eddy
MTI Systems

From gorry@erg.abdn.ac.uk  Sat Aug  3 01:36:56 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33CFA11E815F for <tcmtf@ietfa.amsl.com>; Sat,  3 Aug 2013 01:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.349
X-Spam-Level: 
X-Spam-Status: No, score=-106.349 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, URI_NOVOWEL=0.5, USER_IN_WHITELIST=-100]
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 8oa6z5Ay2pH1 for <tcmtf@ietfa.amsl.com>; Sat,  3 Aug 2013 01:36:50 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id E15E911E810C for <tcmtf@ietf.org>; Sat,  3 Aug 2013 01:36:49 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 79D672B44B4; Sat,  3 Aug 2013 09:36:48 +0100 (BST)
Received: from ra-gorry.erg.abdn.ac.uk (ra-gorry.erg.abdn.ac.uk [139.133.204.42]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 0E07C2B439A for <tcmtf@ietf.org>; Sat,  3 Aug 2013 09:36:45 +0100 (BST)
Message-ID: <51FCC11D.704@erg.abdn.ac.uk>
Date: Sat, 03 Aug 2013 10:36:45 +0200
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <62cc435d$3efd1c1e$5089971$@fap-ntic.org> <51FBF33D.8000401@isi.edu>
In-Reply-To: <51FBF33D.8000401@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [tcmtf] Support to create the working group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 08:36:56 -0000

One reason why I think this *COULD* be a transport issue, is that it may 
not primarily require new tunnel encapsulation methods.

The problem space includes how identify how to find/configure the 
compression tunnel endpoints, how to know whether specific transport 
flows should be placed in a compression tunnel, etc. This could well 
include guidance of what not to do from a transport perspective.

Gorry

On 02/08/2013 19:58, Joe Touch wrote:
> Hi, all,
>
> FWIW, I don't understand why this is being requested of the TRANSPORT area.
>
> Tunnels such as this ought to be the purview of INTAREA. I admit I
> remain confused as to why so many tunneling protocols are in ROUTING,
> but regardless neither is TRANSPORT.
>
> Joe
>
> On 8/1/2013 8:52 PM, info@fap-ntic.org wrote:
>>
>> Dear Martin Stiemerling,
>> Transport Area Director,
>>
>> I have the honor to approach you about the creation of the working group
>> TCM-TF which for us is very interesting for developing countries.
>>
>> For your information, our organization '' *African Forum for the
>> Promotion of New Information and Communication **Technologies*'' AFP-ICT
>> work to our project : *''TrainingandConnecting Rural People''* (WSIS
>> Project Prizes 2013 : E-Learning), which enters its second phase where
>> we think the Tunneling, Compressing and Multiplexing Traffic Flow
>> (TCM-TF) is interesting and better adapt to the rural areas in general
>> and in particular for developing countries because TCMTF, a proposal for
>> Optimizing the traffic of real-time services and other flows based on
>> small packets. It is based on grouping and compressing traffic flows,
>> and it is ble to save 50% or even 60% of the bandwidth for some services.
>>
>> In many of our countries development project, we have a lot of problems
>> regarding the provision of services (traffic flow). Especially in rural
>> areas (our workplace for the development of ICT) encompassing a large
>> part of the African population TCM-TF is a tool that can facilitate the
>> flow of information.
>>
>> The creation of a working group TCM-TF can help reflect further on this
>> very important issue and may facilitate some parts of the world whose
>> needs are urgent and solve many of the problems we face. We have a great
>> challenge that is to reduce the digital divide by promoting ICT. In
>> Africa, the major urban centers are more developed, however, sustainable
>> development that affects a large number of people must be in rural
>> communities.
>>
>> Best Regards
>>
>> Nzengeli Papie
>> Coordinator
>> African Forum for the Promotion of the New Information and Communication
>> Technologies
>> (Forum Africain pour la Promotion des Nouvelles Technologies de
>> l'Information et de la Communication)
>> Mail : info@fap-ntic.org
>> <https://mail.google.com/mail/h/vrv6evnqlyn1/?&v=b&cs=wh&to=info@fap-ntic.org>
>>
>>
>> Web site :www.fap-ntic.org
>> <http://www.google.com/url?q=http%3A%2F%2Fwww.fap-ntic.org&sa=D&sntz=1&usg=AFQjCNGMWp7ho2v7_5WCdRpzeUahCSueEw>
>>
>>
>> Brazzaville/Republic of Congo
>>
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>


From jsaldana@unizar.es  Sat Aug  3 01:44:29 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E259921F9951 for <tcmtf@ietfa.amsl.com>; Sat,  3 Aug 2013 01:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Ba7Tj3pPZbm0 for <tcmtf@ietfa.amsl.com>; Sat,  3 Aug 2013 01:44:25 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id CF8D311E80F6 for <tcmtf@ietf.org>; Sat,  3 Aug 2013 01:44:24 -0700 (PDT)
Received: from jsaldanapc (96.Red-88-4-241.dynamicIP.rima-tde.net [88.4.241.96]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r738htoR014227; Sat, 3 Aug 2013 10:44:01 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Wesley Eddy'" <wes@mti-systems.com>, "'Joe Touch'" <touch@isi.edu>
References: <62cc435d$3efd1c1e$5089971$@fap-ntic.org>	<51FBF33D.8000401@isi.edu> <51FC653A.8050206@mti-systems.com>
In-Reply-To: <51FC653A.8050206@mti-systems.com>
Date: Sat, 3 Aug 2013 10:43:55 +0200
Message-ID: <009701ce9025$9d259a40$d770cec0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHglW2h4zKw/INgI/9LI4Fu+hXiagIdhG82An8doGCZOjkr4A==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, info@fap-ntic.org, martin.stiemerling@neclab.eu
Subject: Re: [tcmtf] Support to create the working group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 08:44:30 -0000

I agree with Wes. The question of the area was discussed one year ago =
(see
slides 24-26 of this presentation at IETF83:
http://www.ietf.org/proceedings/83/slides/slides-83-tsvwg-0.pdf). There =
have
been no objections about this point during the last 16 months. The =
drafts
are in tsvwg. The BOF was organized by the Transport Area, and nobody
objected.

So IMHO, this is clear.

Thanks,

Jose=20

-----Mensaje original-----
De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
Wesley Eddy
Enviado el: s=E1bado, 03 de agosto de 2013 4:05
Para: Joe Touch
CC: tcmtf@ietf.org; info@fap-ntic.org; martin.stiemerling@neclab.eu
Asunto: Re: [tcmtf] Support to create the working group for TCM-TF

On 8/2/2013 1:58 PM, Joe Touch wrote:
> Hi, all,
>=20
> FWIW, I don't understand why this is being requested of the TRANSPORT
area.
>=20
> Tunnels such as this ought to be the purview of INTAREA. I admit I=20
> remain confused as to why so many tunneling protocols are in ROUTING,=20
> but regardless neither is TRANSPORT.
>=20


Hi Joe; here are a few reasons I can think of for justifying transport =
as
the area:

- the intent was not to invent new tunnel protocols, but to use
  existing ones as part of a stack
- all of the possible downsides that people brought up during
  the meeting are impacts to the transport protocol; so there is
  a tight coupling between transport configuration and what the
  recommendation for performing TCMTF on a flow should be
- many of the design considerations are directly related to things
  transport has dealt with in the past like delayed ACKs, ACK
  compression, buffer sizing, etc.
- PILC and PEP documentation were done in the transport area
- RoHC was done in the transport area
- PMTUD was in transport area (since you noted that this is a
  an additional concern)

In my opinion, if this is done, it should be in transport.

--
Wes Eddy
MTI Systems
_______________________________________________
tcmtf mailing list
tcmtf@ietf.org
https://www.ietf.org/mailman/listinfo/tcmtf


From jsaldana@unizar.es  Sat Aug  3 01:52:52 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1458211E80F6 for <tcmtf@ietfa.amsl.com>; Sat,  3 Aug 2013 01:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 cRdv9ZrANppj for <tcmtf@ietfa.amsl.com>; Sat,  3 Aug 2013 01:52:47 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id E596111E810C for <tcmtf@ietf.org>; Sat,  3 Aug 2013 01:52:16 -0700 (PDT)
Received: from jsaldanapc (96.Red-88-4-241.dynamicIP.rima-tde.net [88.4.241.96]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r738q5U4017508; Sat, 3 Aug 2013 10:52:06 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>, "'Luigi Iannone'" <ggx@gigix.net>
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net> <E721D8C6A2E1544DB2DEBC313AF54DE2241CFE0C@xmb-rcd-x02.cisco.com>
In-Reply-To: <E721D8C6A2E1544DB2DEBC313AF54DE2241CFE0C@xmb-rcd-x02.cisco.com>
Date: Sat, 3 Aug 2013 10:52:06 +0200
Message-ID: <009801ce9026$bc402340$34c069c0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJA1wKBnfi9hMvXhdZ8GNJVqmA1xwIqY/47mI1KOgA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] BoF feedback
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 08:52:52 -0000

Muthu, Luigi,

Perhaps you are right. The inclusion of the TCP branch of the protocol
raised many objections. But perhaps if we remove that branch (or leave it
for further study), we can carry on with RTP/UDP/IP and UDP/IP flows. In
fact, RTP/UDP/IP is already a standard (RFC4170, 2005) and nobody objected.
At least we should replace ECRTP with ROHC in RFC4170.

Another option would be to create a specific document about the things to
take into account when multiplexing TCP flows. Or perhaps this could be
included in the "TCM-TF recommendations" draft.

Thanks,

Jose

-----Mensaje original-----
De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
Muthu Arul Mozhi Perumal (mperumal)
Enviado el: viernes, 02 de agosto de 2013 22:25
Para: Luigi Iannone; tcmtf@ietf.org
Asunto: Re: [tcmtf] BoF feedback

TCMTF has clear and demonstrated benefits for VoIP and online gaming.
CRTP/ECRTP has already enjoyed some success in reducing VoIP bandwidth over
point-to-point WAN links, especially in those regions where access bandwidth
is considerably expensive. TCMFT is a natural extension that encompasses
better compression and tunneling technologies to achieve similar goals. 

The concerns raised during the BoF seemed in relation to generalizing it for
other kinds of traffic and TCP in particular. This generalization though
important (especially in the context of Internet of Things as echoed by
Michael Ramalho during the BoF) could probably be deferred for future work
(TCMTF2.0?) and the scope limited to VoIP and online gaming to begin with,
IMO. As we work through the limited scope, how (and how not) to apply it for
other kinds of traffic should become more clear, I think.

Muthu

|-----Original Message-----
|From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf 
|Of Luigi Iannone
|Sent: Friday, August 02, 2013 4:05 PM
|To: tcmtf@ietf.org
|Subject: [tcmtf] BoF feedback
|
|Hi,
|
|I was thinking a little bit about the turn the BoF took yesterday, going a
bit off topic IMHO.
|
|At a certain point people were going to the mic to explain yet another 
|scenario where TCMTF would not work or is not useful.
|
|It is obvious to me that such scenarios exist, but  the goal of TCMTF 
|is not to provide something that will be applied to all packets under a
certain size.
|
|It is also obvious to me that scenarios where TCMTF is beneficial exist 
|as well. Goal of TCMTF should be to provide the right mechanism for those
scenarios.
|
|A key point to discuss in TCMTF is how we identify and select the flow 
|we want to be multiplexed on a single compressed tunnel.
|
|All of this to say that we should not focus or scenarios where TCMTF 
|doesn't help but rather to answer the following question:
|
|Are there scenarios and use cases where TCMTF provides benefits?
|
|The answer IMHO is YES so some work should be done.
|
|Just let me add that,  before thinking how to encapsulate we should 
|answer: How do we select the flows we want to encamp?
|
|So that we are sure that we do not touch traffic that will suffer because
of TCMTF.
|
|Just my thoughts after the BoF.
|
|ciao
|
|Luigi
|
|
|_______________________________________________
|tcmtf mailing list
|tcmtf@ietf.org
|https://www.ietf.org/mailman/listinfo/tcmtf
_______________________________________________
tcmtf mailing list
tcmtf@ietf.org
https://www.ietf.org/mailman/listinfo/tcmtf


From jsaldana@unizar.es  Sat Aug  3 02:09:22 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1304321F97C7 for <tcmtf@ietfa.amsl.com>; Sat,  3 Aug 2013 02:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.67
X-Spam-Level: 
X-Spam-Status: No, score=-5.67 tagged_above=-999 required=5 tests=[AWL=-0.929,  BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4]
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 a03Wp6+1Vczo for <tcmtf@ietfa.amsl.com>; Sat,  3 Aug 2013 02:09:16 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 7D16921F995E for <tcmtf@ietf.org>; Sat,  3 Aug 2013 02:09:09 -0700 (PDT)
Received: from jsaldanapc (96.Red-88-4-241.dynamicIP.rima-tde.net [88.4.241.96]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r7398ooP027125; Sat, 3 Aug 2013 11:08:50 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Sat, 3 Aug 2013 11:08:52 +0200
Message-ID: <009901ce9029$15a29b00$40e7d100$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6QJtGZYw9AyQtjQCWMSXvEvd54/Q==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: 'Luigi Iannone' <ggx@gigix.net>, "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>, =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
Subject: Re: [tcmtf] BoF feedback: Application-limited TCP
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 09:09:22 -0000

This is something I tried to explain during the BOF, but perhaps I wasn't
able to set it clear: when we are talking about multiplexing TCP flows, we
are not thinking about normal TCP flows, but about very specific ones, in
which the information is generated during the TCP session itself.

These three papers [1], [2], [3] are about this question: A TCP-based online
game generates TCP packets as the player generates new commands. The PUSH
bit of the TCP header is set to 1 in order to make the TCP stack send it as
soon as possible, and ACKs are piggybacked onto the packets from the server
and vice versa.

But there are some TCP features that do not work properly for these flows,
since they are thought for "network-limited" TCP flows, whereas these games
generate "application-limited" TCP flows (as Mirko explained in the online
games tutorial on Thursday morning):

- Some TCP mechanisms directly deteriorate the experience of the players
(delayed ACK, Nagle algorithm)

- Some other TCP mechanisms do not work efficiently for MMORPGs (cwnd
reduced due to the application having nothing to send)

So which would be the effect of an additional multiplexing delay on a bunch
of "application-limited" TCP flows? I am currently doing NS2 simulations for
a paper I am preparing for IEEE CCNC 2014. I have some preliminary results I
will share here, just if they can shed some light to this (interesting)
debate. I am summarizing them in another e-mail.

Best regards,

Jose


[1]	C-C. Wu K-T. Chen, C-M. Chen, P. Huang, and C-L. Lei, "On the
Challenge and Design of Transport Protocols for MMORPGs," Multimedia Tools
and Applications (special issue on Massively Multiuser Online Gaming Systems
and Applications), Vol. 45, No. 1, pp. 7-32, 2009.
[2]	C. Griwodz and P. Halvorsen. "The fun of using TCP for an MMORPG,"
Proceedings of international workshop on Network and operating systems
support for digital audio and video (NOSSDAV '06). ACM, New York, NY, USA,
2006.
[3]	K-T. Chen, C-Y. Huang, P. Huang and C-L. Lei, "An Empirical
Evaluation of TCP Performance in Online Games", Proceedings of  the 2006 ACM
SIGCHI international conference on Advances in computer entertainment
technology ACE 06, Hollywood, California, USA, 2006.



From gorry@erg.abdn.ac.uk  Sat Aug  3 02:12:05 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A52AE11E8163 for <tcmtf@ietfa.amsl.com>; Sat,  3 Aug 2013 02:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.568
X-Spam-Level: 
X-Spam-Status: No, score=-106.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 EuIckzd0vl-z for <tcmtf@ietfa.amsl.com>; Sat,  3 Aug 2013 02:12:01 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 0C55211E815F for <tcmtf@ietf.org>; Sat,  3 Aug 2013 02:11:55 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 579172B44B4; Sat,  3 Aug 2013 10:11:54 +0100 (BST)
Received: from ra-gorry.erg.abdn.ac.uk (ra-gorry.erg.abdn.ac.uk [139.133.204.42]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 73E852B439A for <tcmtf@ietf.org>; Sat,  3 Aug 2013 10:11:52 +0100 (BST)
Message-ID: <51FCC957.6000100@erg.abdn.ac.uk>
Date: Sat, 03 Aug 2013 11:11:51 +0200
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net> <E721D8C6A2E1544DB2DEBC313AF54DE2241CFE0C@xmb-rcd-x02.cisco.com> <009801ce9026$bc402340$34c069c0$@unizar.es>
In-Reply-To: <009801ce9026$bc402340$34c069c0$@unizar.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [tcmtf] BoF feedback
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 09:12:05 -0000

Indeed, I suspect a separate draft on TCP/SCTP would be helpful. There 
are separate issues that emerge if this is important to consider.

A separate draft could help capture the key issues, present experience 
of using this, results from implementation, etc. RFC 3449 already gives 
some guidance on compression methods for TCP return streams, especially 
the "compaction" approach, and section 5.3.3 hints at the problem of 
forming bursts of TCP segments.

A separate document would also help divide the problem into activities 
where expertise can be focused.

Gorry


On 03/08/2013 10:52, Jose Saldana wrote:
> Muthu, Luigi,
>
> Perhaps you are right. The inclusion of the TCP branch of the protocol
> raised many objections. But perhaps if we remove that branch (or leave it
> for further study), we can carry on with RTP/UDP/IP and UDP/IP flows. In
> fact, RTP/UDP/IP is already a standard (RFC4170, 2005) and nobody objected.
> At least we should replace ECRTP with ROHC in RFC4170.
>
> Another option would be to create a specific document about the things to
> take into account when multiplexing TCP flows. Or perhaps this could be
> included in the "TCM-TF recommendations" draft.
>
> Thanks,
>
> Jose
>
> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
> Muthu Arul Mozhi Perumal (mperumal)
> Enviado el: viernes, 02 de agosto de 2013 22:25
> Para: Luigi Iannone; tcmtf@ietf.org
> Asunto: Re: [tcmtf] BoF feedback
>
> TCMTF has clear and demonstrated benefits for VoIP and online gaming.
> CRTP/ECRTP has already enjoyed some success in reducing VoIP bandwidth over
> point-to-point WAN links, especially in those regions where access bandwidth
> is considerably expensive. TCMFT is a natural extension that encompasses
> better compression and tunneling technologies to achieve similar goals.
>
> The concerns raised during the BoF seemed in relation to generalizing it for
> other kinds of traffic and TCP in particular. This generalization though
> important (especially in the context of Internet of Things as echoed by
> Michael Ramalho during the BoF) could probably be deferred for future work
> (TCMTF2.0?) and the scope limited to VoIP and online gaming to begin with,
> IMO. As we work through the limited scope, how (and how not) to apply it for
> other kinds of traffic should become more clear, I think.
>
> Muthu
>
> |-----Original Message-----
> |From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
> |Of Luigi Iannone
> |Sent: Friday, August 02, 2013 4:05 PM
> |To: tcmtf@ietf.org
> |Subject: [tcmtf] BoF feedback
> |
> |Hi,
> |
> |I was thinking a little bit about the turn the BoF took yesterday, going a
> bit off topic IMHO.
> |
> |At a certain point people were going to the mic to explain yet another
> |scenario where TCMTF would not work or is not useful.
> |
> |It is obvious to me that such scenarios exist, but  the goal of TCMTF
> |is not to provide something that will be applied to all packets under a
> certain size.
> |
> |It is also obvious to me that scenarios where TCMTF is beneficial exist
> |as well. Goal of TCMTF should be to provide the right mechanism for those
> scenarios.
> |
> |A key point to discuss in TCMTF is how we identify and select the flow
> |we want to be multiplexed on a single compressed tunnel.
> |
> |All of this to say that we should not focus or scenarios where TCMTF
> |doesn't help but rather to answer the following question:
> |
> |Are there scenarios and use cases where TCMTF provides benefits?
> |
> |The answer IMHO is YES so some work should be done.
> |
> |Just let me add that,  before thinking how to encapsulate we should
> |answer: How do we select the flows we want to encamp?
> |
> |So that we are sure that we do not touch traffic that will suffer because
> of TCMTF.
> |
> |Just my thoughts after the BoF.
> |
> |ciao
> |
> |Luigi
> |
> |
> |_______________________________________________
> |tcmtf mailing list
> |tcmtf@ietf.org
> |https://www.ietf.org/mailman/listinfo/tcmtf
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>


From jsaldana@unizar.es  Sat Aug  3 03:07:07 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4EA811E816F for <tcmtf@ietfa.amsl.com>; Sat,  3 Aug 2013 03:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.789
X-Spam-Level: 
X-Spam-Status: No, score=-4.789 tagged_above=-999 required=5 tests=[AWL=-1.190, BAYES_00=-2.599, GB_I_LETTER=-2, GB_SUMOF=5, RCVD_IN_DNSWL_MED=-4]
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 XsAy8qHBrf+L for <tcmtf@ietfa.amsl.com>; Sat,  3 Aug 2013 03:07:01 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 2840711E8162 for <tcmtf@ietf.org>; Sat,  3 Aug 2013 03:07:00 -0700 (PDT)
Received: from jsaldanapc (96.Red-88-4-241.dynamicIP.rima-tde.net [88.4.241.96]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r73A6vKe001775 for <tcmtf@ietf.org>; Sat, 3 Aug 2013 12:06:58 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
References: <009901ce9029$15a29b00$40e7d100$@unizar.es>
In-Reply-To: <009901ce9029$15a29b00$40e7d100$@unizar.es>
Date: Sat, 3 Aug 2013 12:06:57 +0200
Message-ID: <00a801ce9031$30dab580$92902080$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKXZVOjUjTZqpVF1wO/T6iO9ZSE35fxiW1A
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] BoF feedback: Application-limited TCP
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 10:07:07 -0000

I am currently deploying NS2 simulations for a paper I am preparing for =
IEEE
CCNC 2014. I have some preliminary results I will share here, just if =
they
can shed some light to this (interesting) debate.

I wasn't able to report these results during the BoF. No time for that =
in a
face-to-face meeting.

I am using an NS2 dumbbell scenario, with two branches. One of them has =
a
"sawteeth" delay and the other doesn't.

(to be seen with Courier letters)
#   node0 o-------o node8                 o node1   =20
#                  \                     /
#            node9  \ node4      node5  /=20
#   node6 o-----o----o-----------------o-----o node7  =20
#                   /                   \
#           node2  o                     o node3
#
# a "number_of_connections_0_1_" of WoW are set from node0 (client) to =
node1
(server)
# a "number_of_connections_6_7_" of WoW are set from node6 (client) to =
node7
(server)
# an additional multiplexing delay is added from node8 to node4, and =
from
node9 to node4
# connection node2-node3 is for background traffic (not used so far)

A "sawteeth" delay is the delay you can expect if you add a =
"multiplexing
period" T: packets arriving at the beginning or the period are delayed T =
ms,
and packets arriving in the end are delayed 0 ms. The average delay is =
T/2.

(to be seen with Courier letters)
|     |     |     |     |     ^
|\    |\    |\    |\    |     |
| \   | \   | \   | \   |     T
|  \  |  \  |  \  |  \  |     |
|   \ |   \ |   \ |   \ |     |
|    \|    \|    \|    \|     v

       <-T->

What I am doing with NS2 is to make a "competition" between:
- A number "N" of TCP-based gaming flows  node0-node1, adding a =
"sawteeth"
delay with period T
- a number "M" of TCP-based gaming flows node6-node7, without that delay

This is something similar to the typical papers in which RTT unfairness =
is
measured for TCP.

Other simulation parameters: NS2 FullTCP is used for the game flows;
bandwidth of each client-server flow: 1.47 kbps (Questing activity of =
World
of Warcraft); bandwidth server-client: 18.13 kbps; OWD of the =
bottleneck: 20
ms; OWD of the rest of links: 10ms; simulation duration: 200 sec; server
population: 100 players on each of the servers.

Some results (no background traffic so far):

A) N=3D50; M=3D50; Bottleneck=3D10Mbps; T=3D50ms

BW node0->node1 =3D 74kbps (aggregate throughput obtained by all the =
flows)
BW node6->node7 =3D 75kbps

B) N=3D100; M=3D100; Bottleneck=3D300kbps; T=3D50ms

BW node0->node1 =3D 144kbps
BW node6->node7 =3D 147kbps

C) N=3D100; M=3D100; Bottleneck=3D250kbps; T=3D25ms

BW node0->node1 =3D 117kbps
BW node6->node7 =3D 131kbps

D) N=3D100; M=3D100; Bottleneck=3D250kbps; T=3D50ms

BW node0->node1 =3D 115kbps
BW node6->node7 =3D 133kbps


Some preliminary conclusions:
- No difference is observed when bandwidth is high enough (A).
- Small differences are observed if bandwidth is a bit higher than the =
sum
of the throughput of all the flows (B)
- The differences become more significant if bandwidth is scarce (C) and =
(D)

So multiplexing may reduce the obtained throughput in some cases, in a
similar way to RTT unfairness. I will also have to compare "sawteeth =
delay"
and a constant additional delay in subsequent tests.

Clearly, this is something that can be further studied, as you can =
guess. I
will write this research paper this month and let you know.

Thanks!

Jose

-----Mensaje original-----
De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de =
Jose
Saldana
Enviado el: s=E1bado, 03 de agosto de 2013 11:09
Para: tcmtf@ietf.org
CC: 'Luigi Iannone'; 'Muthu Arul Mozhi Perumal (mperumal)'; Mirko =
Su=BEnjevi=E6
Asunto: Re: [tcmtf] BoF feedback: Application-limited TCP

This is something I tried to explain during the BOF, but perhaps I =
wasn't
able to set it clear: when we are talking about multiplexing TCP flows, =
we
are not thinking about normal TCP flows, but about very specific ones, =
in
which the information is generated during the TCP session itself.

These three papers [1], [2], [3] are about this question: A TCP-based =
online
game generates TCP packets as the player generates new commands. The =
PUSH
bit of the TCP header is set to 1 in order to make the TCP stack send it =
as
soon as possible, and ACKs are piggybacked onto the packets from the =
server
and vice versa.

But there are some TCP features that do not work properly for these =
flows,
since they are thought for "network-limited" TCP flows, whereas these =
games
generate "application-limited" TCP flows (as Mirko explained in the =
online
games tutorial on Thursday morning):

- Some TCP mechanisms directly deteriorate the experience of the players
(delayed ACK, Nagle algorithm)

- Some other TCP mechanisms do not work efficiently for MMORPGs (cwnd
reduced due to the application having nothing to send)

So which would be the effect of an additional multiplexing delay on a =
bunch
of "application-limited" TCP flows? I am currently doing NS2 simulations =
for
a paper I am preparing for IEEE CCNC 2014. I have some preliminary =
results I
will share here, just if they can shed some light to this (interesting)
debate. I am summarizing them in another e-mail.

Best regards,

Jose


[1]	C-C. Wu K-T. Chen, C-M. Chen, P. Huang, and C-L. Lei, "On the
Challenge and Design of Transport Protocols for MMORPGs," Multimedia =
Tools
and Applications (special issue on Massively Multiuser Online Gaming =
Systems
and Applications), Vol. 45, No. 1, pp. 7-32, 2009.
[2]	C. Griwodz and P. Halvorsen. "The fun of using TCP for an MMORPG,"
Proceedings of international workshop on Network and operating systems
support for digital audio and video (NOSSDAV '06). ACM, New York, NY, =
USA,
2006.
[3]	K-T. Chen, C-Y. Huang, P. Huang and C-L. Lei, "An Empirical
Evaluation of TCP Performance in Online Games", Proceedings of  the 2006 =
ACM
SIGCHI international conference on Advances in computer entertainment
technology ACE 06, Hollywood, California, USA, 2006.


_______________________________________________
tcmtf mailing list
tcmtf@ietf.org
https://www.ietf.org/mailman/listinfo/tcmtf


From ggx@gigix.net  Mon Aug  5 06:28:30 2013
Return-Path: <ggx@gigix.net>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E587521F9DCA for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 06:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 EjwvDkz7kqWR for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 06:28:26 -0700 (PDT)
Received: from mail-we0-f180.google.com (mail-we0-f180.google.com [74.125.82.180]) by ietfa.amsl.com (Postfix) with ESMTP id 9253E21F9DBD for <tcmtf@ietf.org>; Mon,  5 Aug 2013 06:28:25 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id p61so2463300wes.39 for <tcmtf@ietf.org>; Mon, 05 Aug 2013 06:28:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=AHnZ98WHrlNKcRjF6BFmbI8CxMt7g4S5R6ps5LTHnOM=; b=nZQ2zpTjzubcGWPT5y4bUclG0IEraxZH8Mny6pqibsHpYazor5xBo0L1nsh7Ks/WZa SxsQcF0qgxvGJvONKrZhUC4Be2VP7b7cGqjjK888o3hsJSBiOelvrcOXxhrtI/o5W2vG hDuYxSDCxNiXaZ5u1hgaJT3PaZLWRHr9Ly9yz8q09bX1gKqvtlnjOtmtgCpduk0KPKp7 xJYqa93ku5TTNN6g1p/TFNmWd51lapbU0JKnjJdTpfkYpezEWgXS+aYk99Yk377zrh4M xQnyKIUviinPg3ztrZh3iJoJbiDngA5/1WmwuIqkRFppNoiB7C80AUnE1i9PuQnn22AN EvJw==
X-Received: by 10.180.205.236 with SMTP id lj12mr6788199wic.22.1375709304566;  Mon, 05 Aug 2013 06:28:24 -0700 (PDT)
Received: from dhcp164-146.enst.fr (dhcp164-146.enst.fr. [137.194.165.146]) by mx.google.com with ESMTPSA id v9sm21495047wiw.8.2013.08.05.06.28.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 Aug 2013 06:28:23 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <51FCC957.6000100@erg.abdn.ac.uk>
Date: Mon, 5 Aug 2013 15:28:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3152C5BE-50E1-4A70-A655-ADDD56C77725@gigix.net>
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net> <E721D8C6A2E1544DB2DEBC313AF54DE2241CFE0C@xmb-rcd-x02.cisco.com> <009801ce9026$bc402340$34c069c0$@unizar.es> <51FCC957.6000100@erg.abdn.ac.uk>
To: gorry@erg.abdn.ac.uk
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQmnElOqZ0RnfEuWSZQHRSNzoHLBqYANBORHIbZ+Qy7wvCHeyz6oEa0iDJolrNOjyZ7+zMH3
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] BoF feedback
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 13:28:31 -0000

Hi,

I also support the creation of a different document for TCP/SCTP.=20

As Gorry points out, this would help  to separate the issues. I think =
that on this side there is much more work to do in understanding where =
and how TCMTF can be applied.

Work on RTP/UDP/IP can advance faster since there are already clear =
scenarios.

I would also re-iterate my point of view. To be blunt I do not believe =
in a "generalised" use of TCMTF, yet I believe that there are strong =
benefits (already demonstrated) in various scenarios. So, IMHO, TCMTF =
should provide the community with the right set of tools to take =
advantage of those benefits.

ciao

Luigi


On 3 Aug. 2013, at 11:11 , Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:

> Indeed, I suspect a separate draft on TCP/SCTP would be helpful. There =
are separate issues that emerge if this is important to consider.
>=20
> A separate draft could help capture the key issues, present experience =
of using this, results from implementation, etc. RFC 3449 already gives =
some guidance on compression methods for TCP return streams, especially =
the "compaction" approach, and section 5.3.3 hints at the problem of =
forming bursts of TCP segments.
>=20
> A separate document would also help divide the problem into activities =
where expertise can be focused.
>=20
> Gorry
>=20
>=20
> On 03/08/2013 10:52, Jose Saldana wrote:
>> Muthu, Luigi,
>>=20
>> Perhaps you are right. The inclusion of the TCP branch of the =
protocol
>> raised many objections. But perhaps if we remove that branch (or =
leave it
>> for further study), we can carry on with RTP/UDP/IP and UDP/IP flows. =
In
>> fact, RTP/UDP/IP is already a standard (RFC4170, 2005) and nobody =
objected.
>> At least we should replace ECRTP with ROHC in RFC4170.
>>=20
>> Another option would be to create a specific document about the =
things to
>> take into account when multiplexing TCP flows. Or perhaps this could =
be
>> included in the "TCM-TF recommendations" draft.
>>=20
>> Thanks,
>>=20
>> Jose
>>=20
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
>> Muthu Arul Mozhi Perumal (mperumal)
>> Enviado el: viernes, 02 de agosto de 2013 22:25
>> Para: Luigi Iannone; tcmtf@ietf.org
>> Asunto: Re: [tcmtf] BoF feedback
>>=20
>> TCMTF has clear and demonstrated benefits for VoIP and online gaming.
>> CRTP/ECRTP has already enjoyed some success in reducing VoIP =
bandwidth over
>> point-to-point WAN links, especially in those regions where access =
bandwidth
>> is considerably expensive. TCMFT is a natural extension that =
encompasses
>> better compression and tunneling technologies to achieve similar =
goals.
>>=20
>> The concerns raised during the BoF seemed in relation to generalizing =
it for
>> other kinds of traffic and TCP in particular. This generalization =
though
>> important (especially in the context of Internet of Things as echoed =
by
>> Michael Ramalho during the BoF) could probably be deferred for future =
work
>> (TCMTF2.0?) and the scope limited to VoIP and online gaming to begin =
with,
>> IMO. As we work through the limited scope, how (and how not) to apply =
it for
>> other kinds of traffic should become more clear, I think.
>>=20
>> Muthu
>>=20
>> |-----Original Message-----
>> |From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On =
Behalf
>> |Of Luigi Iannone
>> |Sent: Friday, August 02, 2013 4:05 PM
>> |To: tcmtf@ietf.org
>> |Subject: [tcmtf] BoF feedback
>> |
>> |Hi,
>> |
>> |I was thinking a little bit about the turn the BoF took yesterday, =
going a
>> bit off topic IMHO.
>> |
>> |At a certain point people were going to the mic to explain yet =
another
>> |scenario where TCMTF would not work or is not useful.
>> |
>> |It is obvious to me that such scenarios exist, but  the goal of =
TCMTF
>> |is not to provide something that will be applied to all packets =
under a
>> certain size.
>> |
>> |It is also obvious to me that scenarios where TCMTF is beneficial =
exist
>> |as well. Goal of TCMTF should be to provide the right mechanism for =
those
>> scenarios.
>> |
>> |A key point to discuss in TCMTF is how we identify and select the =
flow
>> |we want to be multiplexed on a single compressed tunnel.
>> |
>> |All of this to say that we should not focus or scenarios where TCMTF
>> |doesn't help but rather to answer the following question:
>> |
>> |Are there scenarios and use cases where TCMTF provides benefits?
>> |
>> |The answer IMHO is YES so some work should be done.
>> |
>> |Just let me add that,  before thinking how to encapsulate we should
>> |answer: How do we select the flows we want to encamp?
>> |
>> |So that we are sure that we do not touch traffic that will suffer =
because
>> of TCMTF.
>> |
>> |Just my thoughts after the BoF.
>> |
>> |ciao
>> |
>> |Luigi
>> |
>> |
>> |_______________________________________________
>> |tcmtf mailing list
>> |tcmtf@ietf.org
>> |https://www.ietf.org/mailman/listinfo/tcmtf
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>>=20
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>>=20
>=20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From touch@isi.edu  Mon Aug  5 10:58:12 2013
Return-Path: <touch@isi.edu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61D7D21F9D89 for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 10:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.94
X-Spam-Level: 
X-Spam-Status: No, score=-103.94 tagged_above=-999 required=5 tests=[AWL=-1.341, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 D85mZ4zLWZpr for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 10:58:06 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 0299A21F9D3B for <tcmtf@ietf.org>; Mon,  5 Aug 2013 10:58:05 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r75HvjxS008367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 5 Aug 2013 10:57:45 -0700 (PDT)
Message-ID: <51FFE798.2030509@isi.edu>
Date: Mon, 05 Aug 2013 10:57:44 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Wesley Eddy <wes@mti-systems.com>
References: <62cc435d$3efd1c1e$5089971$@fap-ntic.org> <51FBF33D.8000401@isi.edu> <51FC653A.8050206@mti-systems.com>
In-Reply-To: <51FC653A.8050206@mti-systems.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcmtf@ietf.org, info@fap-ntic.org, martin.stiemerling@neclab.eu
Subject: Re: [tcmtf] Support to create the working group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 17:58:12 -0000

On 8/2/2013 7:04 PM, Wesley Eddy wrote:
> On 8/2/2013 1:58 PM, Joe Touch wrote:
>> Hi, all,
>>
>> FWIW, I don't understand why this is being requested of the TRANSPORT area.
>>
>> Tunnels such as this ought to be the purview of INTAREA. I admit I
>> remain confused as to why so many tunneling protocols are in ROUTING,
>> but regardless neither is TRANSPORT.
>>
>
>
> Hi Joe; here are a few reasons I can think of for justifying
> transport as the area:
>
> - the intent was not to invent new tunnel protocols, but to use
>    existing ones as part of a stack
> - all of the possible downsides that people brought up during
>    the meeting are impacts to the transport protocol; so there is
>    a tight coupling between transport configuration and what the
>    recommendation for performing TCMTF on a flow should be

But that's true of most tunneling protocols. We rarely measure downsides 
to network protocols in isolation.

> - many of the design considerations are directly related to things
>    transport has dealt with in the past like delayed ACKs, ACK
>    compression, buffer sizing, etc.
> - PILC and PEP documentation were done in the transport area

PILC and PEP were intended as *interactions* between the link and 
transport.

> - RoHC was done in the transport area
> - PMTUD was in transport area (since you noted that this is a
>    an additional concern)

Yes, but SEAL was not. And SEAL is a better, more complete tunnel in 
which to develop this sort of mechanism - at which point it's not a 
tunnel mechanism so much as a transport compression.

> In my opinion, if this is done, it should be in transport.

Until the "this" is defined, it's impossible to understand where TCMTF 
belongs.

Joe

From spencerdawkins.ietf@gmail.com  Mon Aug  5 11:03:20 2013
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49F9E21F9DF6 for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 11:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599]
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 KSK3cc1kD8rx for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 11:03:19 -0700 (PDT)
Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5897F21F9DFA for <tcmtf@ietf.org>; Mon,  5 Aug 2013 11:03:19 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id i18so7093235oag.29 for <tcmtf@ietf.org>; Mon, 05 Aug 2013 11:03:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=KZJUXc/AJgA59KztGmKy/xxThvWvwd99Vywa1fWdjFw=; b=EuoESPkC/KHYjamMWQ5DrIthDND/OuKkYBtI0x6V07j254TLTC1VGcrL+8kSIv0y7I bHlgbfDq98sQ8L8nKMDGyd0O33OXtwJqnF9nEORXWs5+lZpBnt832YjWCeEeElPHwj1d HtrliZg/BltbzfMTAHL2mBwglms/nsfQLFKN5qT278eFy5NWXZNHee03buXaITKmDCHo RN8HslZ3TrY7D8zXoapRtaW34LwOX6umhQ4Ocmt80KL/+6KvdGtWj00KVPVVQfSQ+d69 8zj0k37iYKXGYc5jrUGX9wQ5l/uDmpb6llh/bh693xKiAY6+HdYVptXVFJWTZorivDiJ LI1Q==
X-Received: by 10.42.68.75 with SMTP id w11mr865940ici.117.1375725797715; Mon, 05 Aug 2013 11:03:17 -0700 (PDT)
Received: from [192.168.0.23] (173-97-116-174.pools.spcsdns.net. [173.97.116.174]) by mx.google.com with ESMTPSA id r6sm137991igp.8.2013.08.05.11.03.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 Aug 2013 11:03:16 -0700 (PDT)
Message-ID: <51FFE8A8.6000401@gmail.com>
Date: Mon, 05 Aug 2013 13:02:16 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Luigi Iannone <ggx@gigix.net>
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net> <E721D8C6A2E1544DB2DEBC313AF54DE2241CFE0C@xmb-rcd-x02.cisco.com> <009801ce9026$bc402340$34c069c0$@unizar.es> <51FCC957.6000100@erg.abdn.ac.uk> <3152C5BE-50E1-4A70-A655-ADDD56C77725@gigix.net>
In-Reply-To: <3152C5BE-50E1-4A70-A655-ADDD56C77725@gigix.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gorry@erg.abdn.ac.uk, tcmtf@ietf.org
Subject: Re: [tcmtf] BoF feedback
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 18:03:20 -0000

Way down in the thread ...

On 8/5/2013 8:28 AM, Luigi Iannone wrote:
> Hi,
>
> I also support the creation of a different document for TCP/SCTP.
>
> As Gorry points out, this would help  to separate the issues. I think that on this side there is much more work to do in understanding where and how TCMTF can be applied.
>
> Work on RTP/UDP/IP can advance faster since there are already clear scenarios.
>
> I would also re-iterate my point of view. To be blunt I do not believe in a "generalised" use of TCMTF, yet I believe that there are strong benefits (already demonstrated) in various scenarios. So, IMHO, TCMTF should provide the community with the right set of tools to take advantage of those benefits.
>
> ciao
>
> Luigi
>
>
> On 3 Aug. 2013, at 11:11 , Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
>
>> Indeed, I suspect a separate draft on TCP/SCTP would be helpful. There are separate issues that emerge if this is important to consider.
>>
>> A separate draft could help capture the key issues, present experience of using this, results from implementation, etc. RFC 3449 already gives some guidance on compression methods for TCP return streams, especially the "compaction" approach, and section 5.3.3 hints at the problem of forming bursts of TCP segments.
>>
>> A separate document would also help divide the problem into activities where expertise can be focused.
>>
>> Gorry
>>
>>
>> On 03/08/2013 10:52, Jose Saldana wrote:
>>> Muthu, Luigi,
>>>
>>> Perhaps you are right. The inclusion of the TCP branch of the protocol
>>> raised many objections. But perhaps if we remove that branch (or leave it
>>> for further study), we can carry on with RTP/UDP/IP and UDP/IP flows. In
>>> fact, RTP/UDP/IP is already a standard (RFC4170, 2005) and nobody objected.
>>> At least we should replace ECRTP with ROHC in RFC4170.
>>>
>>> Another option would be to create a specific document about the things to
>>> take into account when multiplexing TCP flows. Or perhaps this could be
>>> included in the "TCM-TF recommendations" draft.

So, Martin and I were talking this morning, and a question came up that 
you folks might want to ponder, if you haven't already done so ...

Re: UDP/IP flows, the theory here would be to say that UDP/IP flows are 
more like RTP flows than TCP flows, so the concerns about TCP in TCM-TF 
don't apply, but the nice people in RTCWeb are defining their data 
channel over SCTP/DTLS/UDP, and my guess would be that their data 
channel would behave exactly like TCP for bulk transfers.

Have people already considered that?

Thanks,

Spencer

From wes@mti-systems.com  Mon Aug  5 11:11:46 2013
Return-Path: <wes@mti-systems.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E7B221F996F for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 11:11:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 FktjRd8mYo5t for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 11:11:40 -0700 (PDT)
Received: from atl4mhob05.myregisteredsite.com (atl4mhob05.myregisteredsite.com [209.17.115.43]) by ietfa.amsl.com (Postfix) with ESMTP id AB51221F9EF8 for <tcmtf@ietf.org>; Mon,  5 Aug 2013 11:11:39 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.209]) by atl4mhob05.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r75IBd6E016029 for <tcmtf@ietf.org>; Mon, 5 Aug 2013 14:11:39 -0400
Received: (qmail 31410 invoked by uid 0); 5 Aug 2013 18:11:38 -0000
X-TCPREMOTEIP: 108.99.38.55
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@108.99.38.55) by 0 with ESMTPA; 5 Aug 2013 18:11:38 -0000
Message-ID: <51FFEABD.7080706@mti-systems.com>
Date: Mon, 05 Aug 2013 14:11:09 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
References: <62cc435d$3efd1c1e$5089971$@fap-ntic.org> <51FBF33D.8000401@isi.edu> <51FC653A.8050206@mti-systems.com> <51FFE798.2030509@isi.edu>
In-Reply-To: <51FFE798.2030509@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: tcmtf@ietf.org, info@fap-ntic.org, martin.stiemerling@neclab.eu
Subject: Re: [tcmtf] Support to create the working group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 18:11:46 -0000

Joe - I think we should let the IESG do their job of determining
if a charter is in scope for a particular area or needs to be
shifted.

I trust that no matter what the area is, the same people who are
interested in doing the work will stick around and get the work
done.

-- 
Wes Eddy
MTI Systems

From wes@mti-systems.com  Mon Aug  5 11:16:17 2013
Return-Path: <wes@mti-systems.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A6A121F944C for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 11:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 xVG2fkI0kKKY for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 11:16:11 -0700 (PDT)
Received: from atl4mhob14.myregisteredsite.com (atl4mhob14.myregisteredsite.com [209.17.115.52]) by ietfa.amsl.com (Postfix) with ESMTP id 9B14E21F9EC4 for <tcmtf@ietf.org>; Mon,  5 Aug 2013 11:16:10 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.206]) by atl4mhob14.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r75IG85S020045 for <tcmtf@ietf.org>; Mon, 5 Aug 2013 14:16:08 -0400
Received: (qmail 10111 invoked by uid 0); 5 Aug 2013 18:16:07 -0000
X-TCPREMOTEIP: 108.99.38.55
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@108.99.38.55) by 0 with ESMTPA; 5 Aug 2013 18:16:06 -0000
Message-ID: <51FFEBCB.5020201@mti-systems.com>
Date: Mon, 05 Aug 2013 14:15:39 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net> <E721D8C6A2E1544DB2DEBC313AF54DE2241CFE0C@xmb-rcd-x02.cisco.com> <009801ce9026$bc402340$34c069c0$@unizar.es> <51FCC957.6000100@erg.abdn.ac.uk> <3152C5BE-50E1-4A70-A655-ADDD56C77725@gigix.net> <51FFE8A8.6000401@gmail.com>
In-Reply-To: <51FFE8A8.6000401@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Luigi Iannone <ggx@gigix.net>, gorry@erg.abdn.ac.uk, tcmtf@ietf.org
Subject: Re: [tcmtf] BoF feedback
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 18:16:17 -0000

On 8/5/2013 2:02 PM, Spencer Dawkins wrote:
> 
> So, Martin and I were talking this morning, and a question came up that
> you folks might want to ponder, if you haven't already done so ...
> 
> Re: UDP/IP flows, the theory here would be to say that UDP/IP flows are
> more like RTP flows than TCP flows, so the concerns about TCP in TCM-TF
> don't apply, but the nice people in RTCWeb are defining their data
> channel over SCTP/DTLS/UDP, and my guess would be that their data
> channel would behave exactly like TCP for bulk transfers.
> 
> Have people already considered that?
> 


I think the answer is that instead of searching for particular
protocol layerings that could be harmed, the rules for invoking
TCMTF on a flow would be such that it only operates on things
that it is configured to (e.g. UDP to a game server IP and port),
and that it would "fail off" and not do anything for types of
flows that it isn't sure how to optimize, time release for, or
otherwise not break.

That should be the answer for TCP, UDP, SCTP, DCCP, SCTP over UDP,
etc etc etc.

-- 
Wes Eddy
MTI Systems

From touch@isi.edu  Mon Aug  5 11:19:54 2013
Return-Path: <touch@isi.edu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDBE421F90A7 for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 11:19:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.884
X-Spam-Level: 
X-Spam-Status: No, score=-105.884 tagged_above=-999 required=5 tests=[AWL=0.715, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 q+J+3hPFn3X5 for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 11:19:49 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 2BB1821F8BCE for <tcmtf@ietf.org>; Mon,  5 Aug 2013 11:19:38 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r75IIfrr008933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 5 Aug 2013 11:18:41 -0700 (PDT)
Message-ID: <51FFEC80.3070406@isi.edu>
Date: Mon, 05 Aug 2013 11:18:40 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Jose Saldana <jsaldana@unizar.es>
References: <62cc435d$3efd1c1e$5089971$@fap-ntic.org>	<51FBF33D.8000401@isi.edu> <51FC653A.8050206@mti-systems.com> <009701ce9025$9d259a40$d770cec0$@unizar.es>
In-Reply-To: <009701ce9025$9d259a40$d770cec0$@unizar.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: 'Wesley Eddy' <wes@mti-systems.com>, tcmtf@ietf.org, info@fap-ntic.org, martin.stiemerling@neclab.eu
Subject: Re: [tcmtf] Support to create the working group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 18:19:54 -0000

On 8/3/2013 1:43 AM, Jose Saldana wrote:
> I agree with Wes. The question of the area was discussed one year ago (see
> slides 24-26 of this presentation at IETF83:
> http://www.ietf.org/proceedings/83/slides/slides-83-tsvwg-0.pdf). There have
> been no objections about this point during the last 16 months. The drafts
> are in tsvwg. The BOF was organized by the Transport Area, and nobody
> objected.

One area "on the table" during the time of a BOF is whether the area is 
appropriate. It shouldn't be considered a "done deal" until it's a WG.

Further, there's clearly a lot of continuing confusion about what this 
work constitutes.

I'm a bit surprised that nobody else spoke up a year ago in Paris; the 
logic in slide 26 is deeply flawed. By that logic, all tunnels are E2E 
and thus all tunnels belong in transport. Regardless, the list is where 
these discussions should happen, and I didn't see any such discussion 
raised here.

Finally, you really ought to look at SEAL.

Joe

From touch@isi.edu  Mon Aug  5 11:24:52 2013
Return-Path: <touch@isi.edu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86FB721F8FDC for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 11:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.913
X-Spam-Level: 
X-Spam-Status: No, score=-105.913 tagged_above=-999 required=5 tests=[AWL=0.686, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 kuwCakJ2ZFlE for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 11:24:46 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id C143321F8F2E for <tcmtf@ietf.org>; Mon,  5 Aug 2013 11:24:46 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r75IODJ4010311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 5 Aug 2013 11:24:13 -0700 (PDT)
Message-ID: <51FFEDCC.2090004@isi.edu>
Date: Mon, 05 Aug 2013 11:24:12 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Wesley Eddy <wes@mti-systems.com>
References: <62cc435d$3efd1c1e$5089971$@fap-ntic.org> <51FBF33D.8000401@isi.edu> <51FC653A.8050206@mti-systems.com> <51FFE798.2030509@isi.edu> <51FFEABD.7080706@mti-systems.com>
In-Reply-To: <51FFEABD.7080706@mti-systems.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcmtf@ietf.org, info@fap-ntic.org, martin.stiemerling@neclab.eu
Subject: Re: [tcmtf] Support to create the working group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 18:24:52 -0000

On 8/5/2013 11:11 AM, Wesley Eddy wrote:
> Joe - I think we should let the IESG do their job of determining
> if a charter is in scope for a particular area or needs to be
> shifted.

I don't think that should happen without open discussion.

> I trust that no matter what the area is, the same people who are
> interested in doing the work will stick around and get the work
> done.

Maybe, but historically that's exactly the reason the IESG gives to 
move items to particular areas.

Joe

From spencerdawkins.ietf@gmail.com  Mon Aug  5 13:24:43 2013
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E44AD21F8423 for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 13:24:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.545
X-Spam-Level: 
X-Spam-Status: No, score=-2.545 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599]
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 5VyIZaa+E6iT for <tcmtf@ietfa.amsl.com>; Mon,  5 Aug 2013 13:24:42 -0700 (PDT)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 3DC4B21F9371 for <tcmtf@ietf.org>; Mon,  5 Aug 2013 13:24:42 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id dn14so6662287obc.12 for <tcmtf@ietf.org>; Mon, 05 Aug 2013 13:24:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=U28DlULkX4ogCpgs4Q8Ibywz1QheJp+pJcwZyR1e7zA=; b=kNH1BxcUUQMSLE7H2HfJBeGi4/9Sh71NbjGaICM8NKs6jjTXffIWBOR0rOBtUaiBOk AUUgYKP4mwLagRB4My4Rn+LNm3sU59egQAUK9vzQSxWj6NnNgoSSucYmheIrz5J0vcFH 8MvMNyUTolNk8k3emW2WDh54SXqgAluy6LWvw5d9AHkLC1w2yXDtymKMJhmLryVJ2eDU CG7aYJbYyEr3LVNw2fS4CP09cypeZPAvQJ6W0gbTr9ZDFTaRYUH5wpmBBdPcC1lPBXpE d0CCcdzWMUPGvSl1jareAKQRkUN9n92JudpiqP34ARRZG3w2vXxHxJyWAZ2PljycglW5 Gr0w==
X-Received: by 10.42.224.136 with SMTP id io8mr1838633icb.54.1375734281682; Mon, 05 Aug 2013 13:24:41 -0700 (PDT)
Received: from [192.168.0.23] (173-97-116-174.pools.spcsdns.net. [173.97.116.174]) by mx.google.com with ESMTPSA id q4sm404850igp.6.2013.08.05.13.24.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 Aug 2013 13:24:40 -0700 (PDT)
Message-ID: <520009D9.6010605@gmail.com>
Date: Mon, 05 Aug 2013 15:23:53 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Wesley Eddy <wes@mti-systems.com>
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net> <E721D8C6A2E1544DB2DEBC313AF54DE2241CFE0C@xmb-rcd-x02.cisco.com> <009801ce9026$bc402340$34c069c0$@unizar.es> <51FCC957.6000100@erg.abdn.ac.uk> <3152C5BE-50E1-4A70-A655-ADDD56C77725@gigix.net> <51FFE8A8.6000401@gmail.com> <51FFEBCB.5020201@mti-systems.com>
In-Reply-To: <51FFEBCB.5020201@mti-systems.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Luigi Iannone <ggx@gigix.net>, gorry@erg.abdn.ac.uk, Spencer Dawkins <spencerdawkins.ietf@gmail.com>, tcmtf@ietf.org
Subject: Re: [tcmtf] BoF feedback
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 20:24:43 -0000

On 8/5/2013 1:15 PM, Wesley Eddy wrote:
> On 8/5/2013 2:02 PM, Spencer Dawkins wrote:
>> So, Martin and I were talking this morning, and a question came up that
>> you folks might want to ponder, if you haven't already done so ...
>>
>> Re: UDP/IP flows, the theory here would be to say that UDP/IP flows are
>> more like RTP flows than TCP flows, so the concerns about TCP in TCM-TF
>> don't apply, but the nice people in RTCWeb are defining their data
>> channel over SCTP/DTLS/UDP, and my guess would be that their data
>> channel would behave exactly like TCP for bulk transfers.
>>
>> Have people already considered that?
>>
>
> I think the answer is that instead of searching for particular
> protocol layerings that could be harmed, the rules for invoking
> TCMTF on a flow would be such that it only operates on things
> that it is configured to (e.g. UDP to a game server IP and port),
> and that it would "fail off" and not do anything for types of
> flows that it isn't sure how to optimize, time release for, or
> otherwise not break.

Right. That might not have been clear, but that matches what I was 
thinking - opt-in.

So I think my next question if if people expect the spec to give 
guidance about how to decide what gets configured "in".

Thanks,

Spencer

From jsaldana@unizar.es  Tue Aug  6 00:13:45 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D57821F9A3D for <tcmtf@ietfa.amsl.com>; Tue,  6 Aug 2013 00:13:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.853
X-Spam-Level: 
X-Spam-Status: No, score=-5.853 tagged_above=-999 required=5 tests=[AWL=0.746,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 JAG6jL9dvv0T for <tcmtf@ietfa.amsl.com>; Tue,  6 Aug 2013 00:13:39 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 1AB5F21F9C7A for <tcmtf@ietf.org>; Tue,  6 Aug 2013 00:13:32 -0700 (PDT)
Received: from jsaldanapc (11.Red-88-4-4.dynamicIP.rima-tde.net [88.4.4.11]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r767DC0q004941; Tue, 6 Aug 2013 09:13:13 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Spencer Dawkins'" <spencerdawkins.ietf@gmail.com>, "Dan Wing" <dwing@cisco.com>, "Muthu Arul Mozhi Perumal \(mperumal\)" <mperumal@cisco.com>
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net>	<E721D8C6A2E1544DB2DEBC313AF54DE2241CFE0C@xmb-rcd-x02.cisco.com>	<009801ce9026$bc402340$34c069c0$@unizar.es>	<51FCC957.6000100@erg.abdn.ac.uk>	<3152C5BE-50E1-4A70-A655-ADDD56C77725@gigix.net> <51FFE8A8.6000401@gmail.com>
In-Reply-To: <51FFE8A8.6000401@gmail.com>
Date: Tue, 6 Aug 2013 09:13:12 +0200
Message-ID: <001e01ce9274$6ce80650$46b812f0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJA1wKBnfi9hMvXhdZ8GNJVqmA1xwIqY/47AgQvzBMBXDeRqwIcgtwXAVv1oL+YWx6U4A==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: gorry@erg.abdn.ac.uk, tcmtf@ietf.org, 'Luigi Iannone' <ggx@gigix.net>
Subject: Re: [tcmtf] BoF feedback
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 07:13:45 -0000

My opinion...

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
> Spencer Dawkins
> Enviado el: lunes, 05 de agosto de 2013 20:02
> Para: Luigi Iannone
> CC: gorry@erg.abdn.ac.uk; tcmtf@ietf.org
> Asunto: Re: [tcmtf] BoF feedback
> 
> Way down in the thread ...
> 
> On 8/5/2013 8:28 AM, Luigi Iannone wrote:
> > Hi,
> >
> > I also support the creation of a different document for TCP/SCTP.
> >
> > As Gorry points out, this would help  to separate the issues. I think
that on
> this side there is much more work to do in understanding where and how
> TCMTF can be applied.
> >
> > Work on RTP/UDP/IP can advance faster since there are already clear
> scenarios.
> >
> > I would also re-iterate my point of view. To be blunt I do not believe
in a
> "generalised" use of TCMTF, yet I believe that there are strong benefits
> (already demonstrated) in various scenarios. So, IMHO, TCMTF should
> provide the community with the right set of tools to take advantage of
those
> benefits.
> >
> > ciao
> >
> > Luigi
> >
> >
> > On 3 Aug. 2013, at 11:11 , Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
> >
> >> Indeed, I suspect a separate draft on TCP/SCTP would be helpful. There
> are separate issues that emerge if this is important to consider.
> >>
> >> A separate draft could help capture the key issues, present experience
of
> using this, results from implementation, etc. RFC 3449 already gives some
> guidance on compression methods for TCP return streams, especially the
> "compaction" approach, and section 5.3.3 hints at the problem of forming
> bursts of TCP segments.
> >>
> >> A separate document would also help divide the problem into activities
> where expertise can be focused.
> >>
> >> Gorry
> >>
> >>
> >> On 03/08/2013 10:52, Jose Saldana wrote:
> >>> Muthu, Luigi,
> >>>
> >>> Perhaps you are right. The inclusion of the TCP branch of the
> >>> protocol raised many objections. But perhaps if we remove that
> >>> branch (or leave it for further study), we can carry on with
> >>> RTP/UDP/IP and UDP/IP flows. In fact, RTP/UDP/IP is already a standard
> (RFC4170, 2005) and nobody objected.
> >>> At least we should replace ECRTP with ROHC in RFC4170.
> >>>
> >>> Another option would be to create a specific document about the
> >>> things to take into account when multiplexing TCP flows. Or perhaps
> >>> this could be included in the "TCM-TF recommendations" draft.
> 
> So, Martin and I were talking this morning, and a question came up that
you
> folks might want to ponder, if you haven't already done so ...
> 
> Re: UDP/IP flows, the theory here would be to say that UDP/IP flows are
> more like RTP flows than TCP flows, so the concerns about TCP in TCM-TF
> don't apply, but the nice people in RTCWeb are defining their data channel
> over SCTP/DTLS/UDP, and my guess would be that their data channel would
> behave exactly like TCP for bulk transfers.
> 
> Have people already considered that?
> 
> Thanks,
> 
> Spencer
>

The UDP/IP flows we are considering are not (in general) RTCWeb, since they
do not end in a web browser, but in a specific application (e.g. a game
client, a sample of a M2M metering application). Dan and Muthu are also very
active with RTCWeb, so I would like to hear their opinion about this.

Thanks!

Jose



From jsaldana@unizar.es  Tue Aug  6 00:53:24 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8E021F9D7E for <tcmtf@ietfa.amsl.com>; Tue,  6 Aug 2013 00:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Level: 
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5 tests=[AWL=0.622,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 2wvZsYkHyJEC for <tcmtf@ietfa.amsl.com>; Tue,  6 Aug 2013 00:53:19 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id CDB1121F9B5C for <tcmtf@ietf.org>; Tue,  6 Aug 2013 00:53:18 -0700 (PDT)
Received: from jsaldanapc (11.Red-88-4-4.dynamicIP.rima-tde.net [88.4.4.11]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r767r5r0020239; Tue, 6 Aug 2013 09:53:06 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Joe Touch'" <touch@isi.edu>, <martin.stiemerling@neclab.eu>, "'Spencer Dawkins'" <spencerdawkins.ietf@gmail.com>, "'Wesley Eddy'" <wes@mti-systems.com>
References: <62cc435d$3efd1c1e$5089971$@fap-ntic.org>	<51FBF33D.8000401@isi.edu>	<51FC653A.8050206@mti-systems.com>	<009701ce9025$9d259a40$d770cec0$@unizar.es> <51FFEC80.3070406@isi.edu>
In-Reply-To: <51FFEC80.3070406@isi.edu>
Date: Tue, 6 Aug 2013 09:53:04 +0200
Message-ID: <002201ce9279$fe6d09e0$fb471da0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHglW2h4zKw/INgI/9LI4Fu+hXiagIdhG82An8doGAB8jpq5QEe6BFjmSZRRcA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Support to create the working group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 07:53:24 -0000

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
> Joe Touch
> Enviado el: lunes, 05 de agosto de 2013 20:19
> Para: Jose Saldana
> CC: 'Wesley Eddy'; tcmtf@ietf.org; info@fap-ntic.org;
> martin.stiemerling@neclab.eu
> Asunto: Re: [tcmtf] Support to create the working group for TCM-TF
> 
> 
> 
> On 8/3/2013 1:43 AM, Jose Saldana wrote:
> > I agree with Wes. The question of the area was discussed one year ago
> > (see slides 24-26 of this presentation at IETF83:
> > http://www.ietf.org/proceedings/83/slides/slides-83-tsvwg-0.pdf).
> > There have been no objections about this point during the last 16
> > months. The drafts are in tsvwg. The BOF was organized by the
> > Transport Area, and nobody objected.
> 
> One area "on the table" during the time of a BOF is whether the area is
> appropriate. It shouldn't be considered a "done deal" until it's a WG.
> 
> Further, there's clearly a lot of continuing confusion about what this
work
> constitutes.
> 
> I'm a bit surprised that nobody else spoke up a year ago in Paris; the
logic in
> slide 26 is deeply flawed. By that logic, all tunnels are E2E and thus all
tunnels
> belong in transport. Regardless, the list is where these discussions
should
> happen, and I didn't see any such discussion raised here.
> 
> Finally, you really ought to look at SEAL.
> 
> Joe
>

All,

First of all, thanks for your feedback.

The idea of TCM-TF is to include different options at each layer (header
compression, multiplexing and tunneling). The tunneling layer currently
considers L2TP, GRE and MPLS. In a first approach, I don't see any problem
on considering other tunneling technologies, as SEAL, if we find them
useful.

Regarding the problem of the Area, this is my summary:

- Since TCM includes protocols from different layers, it is really difficult
to assign it to an area. It involves a number of areas, but in fact it must
belong to one of them. The possibilities were RAI, Internet and Transport.
- We first tried with AVTCore (RAI area) and the answer was "I don't think
this proposal really belongs in the WG, most likely not this area even"
(Magnus W).
- So we had two options: Internet and Transport. We thought Transport could
fit, and we tried there and we were accepted.
- We have been for one year and a half in the Transport Area Working Group,
tsvwg (the first version of the draft was submitted Feb 16 2012,
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/history/).
- So the people who have participated in the discussion are mainly in the
Transport Area.
- One year ago (July 8 2012), a specific tcmtf mailing list was created.
This had an advantage: we could specifically discuss about tcmtf. But it
also had a drawback: only people subscribed to the list have participated in
the discussion. As a consequence, in the BoF, people not subscribed to the
list raised many concerns that had not appeared at all in the discussion
before.

And this is my opinion:

- If we try to change to Internet Area now, we would have to start from
scratch after 1.5 years: explaining everything again to people in that area,
looking for a WG in the Internet Area, talking with the ADs, etc.
- So let's be practical and assume that Transport Area can be a good place
for this. We have even organized a BoF in the Transport Area, and no one had
any concern with that. It has been a long way, so we should not rethink
everything again.
- Of course, let's try to get people from other areas involved. We need
them.

Thanks a lot,

Jose


From jsaldana@unizar.es  Tue Aug  6 01:01:19 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 753ED21F9B57 for <tcmtf@ietfa.amsl.com>; Tue,  6 Aug 2013 01:01:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.066
X-Spam-Level: 
X-Spam-Status: No, score=-6.066 tagged_above=-999 required=5 tests=[AWL=0.533,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 aznSxIw1Xgkc for <tcmtf@ietfa.amsl.com>; Tue,  6 Aug 2013 01:01:14 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE5621F9AEF for <tcmtf@ietf.org>; Tue,  6 Aug 2013 01:01:14 -0700 (PDT)
Received: from jsaldanapc (11.Red-88-4-4.dynamicIP.rima-tde.net [88.4.4.11]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r7680xi1007872; Tue, 6 Aug 2013 10:01:00 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Spencer Dawkins'" <spencerdawkins.ietf@gmail.com>, "'Wesley Eddy'" <wes@mti-systems.com>, "Martin Stiemerling" <Martin.Stiemerling@neclab.eu>
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net>	<E721D8C6A2E1544DB2DEBC313AF54DE2241CFE0C@xmb-rcd-x02.cisco.com>	<009801ce9026$bc402340$34c069c0$@unizar.es>	<51FCC957.6000100@erg.abdn.ac.uk>	<3152C5BE-50E1-4A70-A655-ADDD56C77725@gigix.net>	<51FFE8A8.6000401@gmail.com> <51FFEBCB.5020201@mti-systems.com> <520009D9.6010605@gmail.com>
In-Reply-To: <520009D9.6010605@gmail.com>
Date: Tue, 6 Aug 2013 10:00:59 +0200
Message-ID: <002301ce927b$17b73b40$4725b1c0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJA1wKBnfi9hMvXhdZ8GNJVqmA1xwIqY/47AgQvzBMBXDeRqwIcgtwXAVv1oL8CZs8j7gG29ZS9mDo+PNA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: 'Luigi Iannone' <ggx@gigix.net>, gorry@erg.abdn.ac.uk, tcmtf@ietf.org
Subject: Re: [tcmtf] BoF feedback
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 08:01:19 -0000

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
> Spencer Dawkins
> Enviado el: lunes, 05 de agosto de 2013 22:24
> Para: Wesley Eddy
> CC: Luigi Iannone; gorry@erg.abdn.ac.uk; Spencer Dawkins; tcmtf@ietf.org
> Asunto: Re: [tcmtf] BoF feedback
> 
> On 8/5/2013 1:15 PM, Wesley Eddy wrote:
> > On 8/5/2013 2:02 PM, Spencer Dawkins wrote:
> >> So, Martin and I were talking this morning, and a question came up
> >> that you folks might want to ponder, if you haven't already done so ...
> >>
> >> Re: UDP/IP flows, the theory here would be to say that UDP/IP flows
> >> are more like RTP flows than TCP flows, so the concerns about TCP in
> >> TCM-TF don't apply, but the nice people in RTCWeb are defining their
> >> data channel over SCTP/DTLS/UDP, and my guess would be that their
> >> data channel would behave exactly like TCP for bulk transfers.
> >>
> >> Have people already considered that?
> >>
> >
> > I think the answer is that instead of searching for particular
> > protocol layerings that could be harmed, the rules for invoking TCMTF
> > on a flow would be such that it only operates on things that it is
> > configured to (e.g. UDP to a game server IP and port), and that it
> > would "fail off" and not do anything for types of flows that it isn't
> > sure how to optimize, time release for, or otherwise not break.
> 
> Right. That might not have been clear, but that matches what I was
thinking -
> opt-in.
> 
> So I think my next question if if people expect the spec to give guidance
> about how to decide what gets configured "in".
> 
> Thanks,
> 
> Spencer

If you look at the abstract of the "Recommendations draft"
(http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/) , this is
exactly what we intend to do in that document:

   This document contains recommendations to be taken into account when
   using methods which optimize bandwidth utilization through
   compression, multiplexing, and tunneling traffic flows (TCMTF) over a
   network path.  Different multiplexing policies and implementation
   issues which are service and link specific are discussed.
   Additionally, this document describes *policies which can be used for
   detecting, classifying, and choosing the network flows suitable for
   optimization by using TCMTF*.  Finally, recommendations of maximum
   tolerable delays to be added by optimization techniques are reported.
   Recommendations are presented only for network services for which
   such bandwidth optimization techniques are applicable (i.e., services
   with low payload to header size ratio, which will also be denoted as
   "small-packet flows").

Spencer, are you talking about the "policies which can be used for
detecting, classifying, and choosing the network flows suitable for
optimization by using TCMTF"?

Perhaps this was not clear enough in the BoF, but of course this is very
important: you can only use TCM-TF for the TCM-suitable flows, and this spec
must clearly define which flows are TCM-suitable and in what conditions.

Thanks,

Jose

> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From spencerdawkins.ietf@gmail.com  Tue Aug  6 05:26:44 2013
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A85821F9C2D for <tcmtf@ietfa.amsl.com>; Tue,  6 Aug 2013 05:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.545
X-Spam-Level: 
X-Spam-Status: No, score=-2.545 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599]
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 i8NoclkQbp-S for <tcmtf@ietfa.amsl.com>; Tue,  6 Aug 2013 05:26:43 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id AB92921F9DA9 for <tcmtf@ietf.org>; Tue,  6 Aug 2013 05:26:43 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id eh20so649241obb.1 for <tcmtf@ietf.org>; Tue, 06 Aug 2013 05:26:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=djUXLF5L17ikDkY30Pbzj+PSZU8yA65Yf6w+LeJIVY8=; b=kE7wDrffyPABpHhDGHjD5ILQzpwlWt4UGzVcNuqWYPXpctFQhdk8Wclo1jKobqpAzp VQ9/SWp69aliuawR0FhUBOOi1WRiP/ST4L+BSNR7aX+qTeW/X83IqVwlulP3o3vjW0Bn FYT7grAYda1nbpHi2j1Vqc6caoZPbLgqjwercbvQHkY4ofg0LhRK94i7sZzZHfFe60N6 UekhGXOT+5feXfIJqXNEJe5eU8e7OA0MauC0l2ZqNRTdpGpQCom9pJ0OAinDAntOXos8 7lrLuXh1CYgQlzUk01cHInmae4ynvImdYhlR+8VdHt969BRW7ZbPJG5B2fAsmCmEADRD hsTA==
X-Received: by 10.182.226.199 with SMTP id ru7mr847026obc.12.1375792003256; Tue, 06 Aug 2013 05:26:43 -0700 (PDT)
Received: from [192.168.0.30] (173-97-116-174.pools.spcsdns.net. [173.97.116.174]) by mx.google.com with ESMTPSA id hm1sm875803obb.9.2013.08.06.05.26.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Aug 2013 05:26:42 -0700 (PDT)
Message-ID: <5200EB7E.5090105@gmail.com>
Date: Tue, 06 Aug 2013 07:26:38 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Jose Saldana <jsaldana@unizar.es>
References: <A5638BF5-0636-4277-B845-69252B131FD0@gigix.net>	<E721D8C6A2E1544DB2DEBC313AF54DE2241CFE0C@xmb-rcd-x02.cisco.com>	<009801ce9026$bc402340$34c069c0$@unizar.es>	<51FCC957.6000100@erg.abdn.ac.uk>	<3152C5BE-50E1-4A70-A655-ADDD56C77725@gigix.net>	<51FFE8A8.6000401@gmail.com> <51FFEBCB.5020201@mti-systems.com> <520009D9.6010605@gmail.com> <002301ce927b$17b73b40$4725b1c0$@unizar.es>
In-Reply-To: <002301ce927b$17b73b40$4725b1c0$@unizar.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 'Wesley Eddy' <wes@mti-systems.com>, 'Luigi Iannone' <ggx@gigix.net>, tcmtf@ietf.org, gorry@erg.abdn.ac.uk, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] BoF feedback
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 12:26:44 -0000

On 8/6/2013 3:00 AM, Jose Saldana wrote:
> If you look at the abstract of the "Recommendations draft"
> (http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/) , this is
> exactly what we intend to do in that document:
>
>     This document contains recommendations to be taken into account when
>     using methods which optimize bandwidth utilization through
>     compression, multiplexing, and tunneling traffic flows (TCMTF) over a
>     network path.  Different multiplexing policies and implementation
>     issues which are service and link specific are discussed.
>     Additionally, this document describes *policies which can be used for
>     detecting, classifying, and choosing the network flows suitable for
>     optimization by using TCMTF*.  Finally, recommendations of maximum
>     tolerable delays to be added by optimization techniques are reported.
>     Recommendations are presented only for network services for which
>     such bandwidth optimization techniques are applicable (i.e., services
>     with low payload to header size ratio, which will also be denoted as
>     "small-packet flows").
>
> Spencer, are you talking about the "policies which can be used for
> detecting, classifying, and choosing the network flows suitable for
> optimization by using TCMTF"?

I think so. And it's possible that a word choice is confusing me. 
"detecting" sounded pretty on-the-fly/dynamic to me (as in, you might 
detect that any random packet going past would be a packet that TCM-TF 
would process), but my understanding of recent e-mails is that 
"detecting" is much less dynamic ("I want to use TCMTF on WoW, and 
here's how you would know a packet is a WoW packet, and anything I 
didn't say how to recognize as a packet that TCM-TF should process is 
forwarded with no changes").

If my understanding based on these recent e-mails is more in line with 
what you're thinking, that answers my question.

Thanks!

Spencer

> Perhaps this was not clear enough in the BoF, but of course this is very
> important: you can only use TCM-TF for the TCM-suitable flows, and this spec
> must clearly define which flows are TCM-suitable and in what conditions.
>
> Thanks,
>
> Jose


From touch@isi.edu  Tue Aug  6 09:35:11 2013
Return-Path: <touch@isi.edu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B16DD21F991F for <tcmtf@ietfa.amsl.com>; Tue,  6 Aug 2013 09:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.456
X-Spam-Level: 
X-Spam-Status: No, score=-106.456 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 zI1y84Pkgkxz for <tcmtf@ietfa.amsl.com>; Tue,  6 Aug 2013 09:35:07 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 0337221F9957 for <tcmtf@ietf.org>; Tue,  6 Aug 2013 09:35:06 -0700 (PDT)
Received: from [192.168.1.91] (pool-71-105-85-4.lsanca.dsl-w.verizon.net [71.105.85.4]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r76GXiM8022756 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 6 Aug 2013 09:33:55 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=us-ascii
From: Joe Touch <touch@isi.edu>
In-Reply-To: <002201ce9279$fe6d09e0$fb471da0$@unizar.es>
Date: Tue, 6 Aug 2013 09:33:43 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE71280C-CE6B-45D9-908F-AE7E3DF062F3@isi.edu>
References: <62cc435d$3efd1c1e$5089971$@fap-ntic.org>	<51FBF33D.8000401@isi.edu>	<51FC653A.8050206@mti-systems.com>	<009701ce9025$9d259a40$d770cec0$@unizar.es> <51FFEC80.3070406@isi.edu> <002201ce9279$fe6d09e0$fb471da0$@unizar.es>
To: Jose Saldana <jsaldana@unizar.es>
X-Mailer: Apple Mail (2.1508)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: 'Wesley Eddy' <wes@mti-systems.com>, tcmtf@ietf.org, 'Spencer Dawkins' <spencerdawkins.ietf@gmail.com>, martin.stiemerling@neclab.eu
Subject: Re: [tcmtf] Support to create the working group for TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 16:35:11 -0000

Hi, Jose,

First, I encourage you to revisit the logic in your slides presented =
last year regarding your primary rationale (at that time) for being in =
TSV - i.e., that TCM-TF has endpoint state, and E2E belongs in =
transport. That's simply incorrect; there are many protocols with state =
and endpoints, and E2E principles should be applied throughout the IETF.

Second, I encourage you to revise your docs and charter to be more clear =
about the goals of your work in terms of what you intend to create vs. =
use/configure, e.g., a tunnel, stateful compression, etc.

Finally, I encourage you to explore SEAL more carefully as a tunnel =
mechanism. It incorporates most of what we have learned about how NOT to =
do tunnels, much better than any other IETF or de-facto tunnel mechanism =
(*especially* GRE, FWIW).

In the future, I sincerely hope that the scope of a BOF will be an =
active area of discussion at the time new multi-area work is introduced. =
This is NOT the sole purview of the ADs.

Joe

On Aug 6, 2013, at 12:53 AM, Jose Saldana <jsaldana@unizar.es> wrote:

>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
>> Joe Touch
>> Enviado el: lunes, 05 de agosto de 2013 20:19
>> Para: Jose Saldana
>> CC: 'Wesley Eddy'; tcmtf@ietf.org; info@fap-ntic.org;
>> martin.stiemerling@neclab.eu
>> Asunto: Re: [tcmtf] Support to create the working group for TCM-TF
>>=20
>>=20
>>=20
>> On 8/3/2013 1:43 AM, Jose Saldana wrote:
>>> I agree with Wes. The question of the area was discussed one year =
ago
>>> (see slides 24-26 of this presentation at IETF83:
>>> http://www.ietf.org/proceedings/83/slides/slides-83-tsvwg-0.pdf).
>>> There have been no objections about this point during the last 16
>>> months. The drafts are in tsvwg. The BOF was organized by the
>>> Transport Area, and nobody objected.
>>=20
>> One area "on the table" during the time of a BOF is whether the area =
is
>> appropriate. It shouldn't be considered a "done deal" until it's a =
WG.
>>=20
>> Further, there's clearly a lot of continuing confusion about what =
this
> work
>> constitutes.
>>=20
>> I'm a bit surprised that nobody else spoke up a year ago in Paris; =
the
> logic in
>> slide 26 is deeply flawed. By that logic, all tunnels are E2E and =
thus all
> tunnels
>> belong in transport. Regardless, the list is where these discussions
> should
>> happen, and I didn't see any such discussion raised here.
>>=20
>> Finally, you really ought to look at SEAL.
>>=20
>> Joe
>>=20
>=20
> All,
>=20
> First of all, thanks for your feedback.
>=20
> The idea of TCM-TF is to include different options at each layer =
(header
> compression, multiplexing and tunneling). The tunneling layer =
currently
> considers L2TP, GRE and MPLS. In a first approach, I don't see any =
problem
> on considering other tunneling technologies, as SEAL, if we find them
> useful.
>=20
> Regarding the problem of the Area, this is my summary:
>=20
> - Since TCM includes protocols from different layers, it is really =
difficult
> to assign it to an area. It involves a number of areas, but in fact it =
must
> belong to one of them. The possibilities were RAI, Internet and =
Transport.
> - We first tried with AVTCore (RAI area) and the answer was "I don't =
think
> this proposal really belongs in the WG, most likely not this area =
even"
> (Magnus W).
> - So we had two options: Internet and Transport. We thought Transport =
could
> fit, and we tried there and we were accepted.
> - We have been for one year and a half in the Transport Area Working =
Group,
> tsvwg (the first version of the draft was submitted Feb 16 2012,
> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/history/).
> - So the people who have participated in the discussion are mainly in =
the
> Transport Area.
> - One year ago (July 8 2012), a specific tcmtf mailing list was =
created.
> This had an advantage: we could specifically discuss about tcmtf. But =
it
> also had a drawback: only people subscribed to the list have =
participated in
> the discussion. As a consequence, in the BoF, people not subscribed to =
the
> list raised many concerns that had not appeared at all in the =
discussion
> before.
>=20
> And this is my opinion:
>=20
> - If we try to change to Internet Area now, we would have to start =
from
> scratch after 1.5 years: explaining everything again to people in that =
area,
> looking for a WG in the Internet Area, talking with the ADs, etc.
> - So let's be practical and assume that Transport Area can be a good =
place
> for this. We have even organized a BoF in the Transport Area, and no =
one had
> any concern with that. It has been a long way, so we should not =
rethink
> everything again.
> - Of course, let's try to get people from other areas involved. We =
need
> them.
>=20
> Thanks a lot,
>=20
> Jose


From Martin.Stiemerling@neclab.eu  Thu Aug  8 07:34:50 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC7A11E81D1 for <tcmtf@ietfa.amsl.com>; Thu,  8 Aug 2013 07:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.477
X-Spam-Level: 
X-Spam-Status: No, score=-103.477 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 oc+GCSc6gHp2 for <tcmtf@ietfa.amsl.com>; Thu,  8 Aug 2013 07:34:45 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 171AB11E812A for <tcmtf@ietf.org>; Thu,  8 Aug 2013 07:34:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id F1A831052A2 for <tcmtf@ietf.org>; Thu,  8 Aug 2013 16:33:53 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cA899FNCZE0I for <tcmtf@ietf.org>; Thu,  8 Aug 2013 16:33:53 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id DA05D1052A1 for <tcmtf@ietf.org>; Thu,  8 Aug 2013 16:33:48 +0200 (CEST)
Received: from [10.1.99.64] (10.1.99.64) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 8 Aug 2013 16:34:38 +0200
Message-ID: <5203AC7E.1050708@neclab.eu>
Date: Thu, 8 Aug 2013 16:34:38 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: "tcmtf@ietf.org" <tcmtf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.99.64]
Subject: [tcmtf] Your support emails for TCMTF / Status
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 14:34:50 -0000

Dear all,

Just to let you know that your responsible AD (me) has seen the number 
of support emails for creating a TCMTF WG and those will be considered 
for the next steps for TCMTF.

As it stands right now, there will be no TCMTF WG at this point of time, 
as the community in the session was half in favor and half not in favor, 
and a number of technical/scope questions weren't fully solved.

However, I assume that Jose, and co-workers, will keep working with the 
list to address the criticisms.

Thanks,

   Martin


-- 
IETF Transport Area Director

martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From jsaldana@unizar.es  Thu Aug  8 09:39:19 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7423411E81D0 for <tcmtf@ietfa.amsl.com>; Thu,  8 Aug 2013 09:39:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.134
X-Spam-Level: 
X-Spam-Status: No, score=-6.134 tagged_above=-999 required=5 tests=[AWL=0.465,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 SQyzIFbEwT-e for <tcmtf@ietfa.amsl.com>; Thu,  8 Aug 2013 09:39:08 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 3C26721E809A for <tcmtf@ietf.org>; Thu,  8 Aug 2013 09:39:04 -0700 (PDT)
Received: from mail.unizar.es (arazas.unizar.es [155.210.11.67]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r78Gcooh030411 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Thu, 8 Aug 2013 18:38:55 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Date: Thu, 08 Aug 2013 18:38:55 +0200
From: jsaldana <jsaldana@unizar.es>
To: tcmtf@ietf.org
In-Reply-To: <5203AC7E.1050708@neclab.eu>
References: <5203AC7E.1050708@neclab.eu>
Message-ID: <bb0884a818462fdf38216c76b435686d@unizar.es>
X-Sender: jsaldana@unizar.es
User-Agent: Roundcube Webmail/0.8.5
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Your support emails for TCMTF / Status
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 16:39:20 -0000

Thanks, Martin.

I confirm I will keep on working on this, especially with the aim of 
addressing the received criticisms. I think the rest of the people are 
not discouraged at all. This requires more work, so let's do it.

Jose

El 2013-08-08 16:34, Martin Stiemerling escribió:
> Dear all,
> 
> Just to let you know that your responsible AD (me) has seen the number
> of support emails for creating a TCMTF WG and those will be considered
> for the next steps for TCMTF.
> 
> As it stands right now, there will be no TCMTF WG at this point of
> time, as the community in the session was half in favor and half not
> in favor, and a number of technical/scope questions weren't fully
> solved.
> 
> However, I assume that Jose, and co-workers, will keep working with
> the list to address the criticisms.
> 
> Thanks,
> 
> Martin

From spencerdawkins.ietf@gmail.com  Thu Aug  8 10:05:41 2013
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5092F11E8135 for <tcmtf@ietfa.amsl.com>; Thu,  8 Aug 2013 10:05:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Whqwq8PDaQBG for <tcmtf@ietfa.amsl.com>; Thu,  8 Aug 2013 10:05:40 -0700 (PDT)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 4158511E81F2 for <tcmtf@ietf.org>; Thu,  8 Aug 2013 10:05:32 -0700 (PDT)
Received: by mail-oa0-f43.google.com with SMTP id i10so5698805oag.16 for <tcmtf@ietf.org>; Thu, 08 Aug 2013 10:05:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=qIgEIa9YGOR4cc7M/A2czG+0ly92VM4yyXUfe4a9nMc=; b=EwyJWKEbuuWI4Cbkq3HR9/w7fxpd58eHrkGs+nVl5xHHV81JqrTrToqyocbrWgLbtQ B4rUX0ytixu5wNsx11ZOvLFcEIUTdESVFmFFdcmqc8W5n1cRUmcJyjcgPh1qjrkTKRNl /2/ldDmxZuXKVtIjl63mkGyce2msntEgVFmOo5a2EBktzpQe5YhLR8BT09x5p0xWbB/5 zF6PFKC437HK6sAjxSGq6YEOMiw+aFzLlgX55EZ5F+nEs8sdfJOIOBB/GOoAipef9+oM L4JJGqf0Li6A5528psESW1Q1AE3hzzCMoT24Vs3DkEGLatLh7AgznTNAaub24PjOamUZ plzQ==
X-Received: by 10.60.38.199 with SMTP id i7mr5022829oek.36.1375981531733; Thu, 08 Aug 2013 10:05:31 -0700 (PDT)
Received: from [192.168.0.30] (70-2-165-176.pools.spcsdns.net. [70.2.165.176]) by mx.google.com with ESMTPSA id tu4sm14386528obb.5.2013.08.08.10.05.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 08 Aug 2013 10:05:30 -0700 (PDT)
Message-ID: <5203CFDC.2090300@gmail.com>
Date: Thu, 08 Aug 2013 12:05:32 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <5203AC7E.1050708@neclab.eu> <bb0884a818462fdf38216c76b435686d@unizar.es>
In-Reply-To: <bb0884a818462fdf38216c76b435686d@unizar.es>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [tcmtf] Your support emails for TCMTF / Status
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 17:05:41 -0000

On 8/8/2013 11:38 AM, jsaldana wrote:
> Thanks, Martin.
>
> I confirm I will keep on working on this, especially with the aim of 
> addressing the received criticisms. I think the rest of the people are 
> not discouraged at all. This requires more work, so let's do it.
>
> Jose

Hi, Jose,

Just to provide a bit of perspective ... it's not at all unusual for a 
BOF effort to change scope (and that often means "reduce scope") after 
meeting with the broader community. So don't be discouraged - that's a 
good response.

I appreciate your efforts, along with the efforts of other BOF 
proponents, the chairs, and the folk who have provided feedback on this 
mailing list and during the meeting.

Spencer

From gorry@erg.abdn.ac.uk  Tue Aug 13 03:28:42 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E55921E80F4 for <tcmtf@ietfa.amsl.com>; Tue, 13 Aug 2013 03:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.999
X-Spam-Level: 
X-Spam-Status: No, score=-103.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 ZxkOAShWWXTw for <tcmtf@ietfa.amsl.com>; Tue, 13 Aug 2013 03:28:37 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 24CDA21E80E1 for <tcmtf@ietf.org>; Tue, 13 Aug 2013 03:28:36 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 591F62B43C1 for <tcmtf@ietf.org>; Tue, 13 Aug 2013 11:28:33 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Tue, 13 Aug 2013 11:28:33 +0100
Message-ID: <b4f9c4cc2964fc6e6529722aede2b287.squirrel@www.erg.abdn.ac.uk>
Date: Tue, 13 Aug 2013 11:28:33 +0100
From: gorry@erg.abdn.ac.uk
To: tcmtf@ietf.org
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Subject: [tcmtf] Draft notes uploaded from the BoF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 10:28:42 -0000

I have just uploaded copies of the notes from the TCMTF BoF:

http://www.ietf.org/proceedings/87/minutes/minutes-87-tcmtf

Best wishes,

Gorry


