
From jsaldana@unizar.es  Mon Jul  1 02:35:20 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 7E36621F99AA for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 02:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 SwKy0yGMMD5E for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 02:35:16 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id E310921F95D7 for <tcmtf@ietf.org>; Mon,  1 Jul 2013 02:35:14 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r619Z4Xt005747; Mon, 1 Jul 2013 11:35:04 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Dan Wing'" <dwing@cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>
In-Reply-To: <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>
Date: Mon, 1 Jul 2013 11:35:06 +0200
Organization: Universidad de Zaragoza
Message-ID: <010f01ce763e$47935190$d6b9f4b0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0110_01CE764F.0B1D8120"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHxl5HfJe4XxEPJrqhURPk2/vEH5gJG8kQSAT8jBAWY7RwkkA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 01 Jul 2013 09:35:20 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0110_01CE764F.0B1D8120
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi, Dan.

=20

I have been reading the article "Cisco adds IP multiplexing to mobile
satellite package", and I think there is an idea we should stress in the
BOF:

=20

We are not only saving bandwidth but also reducing the amount of pps. In =
the
satellite scenario a pps reduction can be translated directly to a x20
factor in the number of simultaneous calls to be transmitted.

=20

Thanks,

=20

Jose

=20

De: Dan Wing [mailto:dwing@cisco.com]=20
Enviado el: mi=E9rcoles, 26 de junio de 2013 22:14
Para: jsaldana@unizar.es
CC: tcmtf@ietf.org
Asunto: Re: [tcmtf] Answers to possible questions in the BOF

=20

=20

On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> wrote:





Question 4: Is TCM-TF interesting for the Industry? Should the IETF
standardize this?

=20

Answer:

=20

1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP traffic. =
So if
RFC4170 was interesting, why not updating it?

=20

2) TCM-TF can be useful in order to save bandwidth in many cases:

=20

- Aggregation network of *network operators*: We are saving bandwidth by
optimizing and putting together traffic flows. Is this interesting for a
network operator? What about overprovisioning? The idea is that there =
are
places and moments in which a number of flows based on small packets are =
in
the same place and at the same moment. Then, TCM-TF can be applied in =
order
to provide flexibility. We are not optimizing the overall Internet =
traffic,
we are optimizing specific flows with very tight delay requirements, =
which
network operators have to take care of in a special way.

 <http://www.huawei.com/ilink/en/download/HW_193034>
www.huawei.com/ilink/en/download/HW_193034

=20

- *End to end* optimization: Nowadays, many appliances are used to =
connect
remote offices of the same company (creating a VPN). So if a tunnel =
exists,
why not optimizing this traffic when possible? We would save bandwidth =
in
the access network, where it can be scarce.

=20

- Wireless and satellite scenarios.

=20

"Cisco adds IP multiplexing to mobile satellite package", April 2012,
http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing-258082=
.ht
ml

=20

=20





=20

=20

Any other thoughts? Any other scenarios in mind? Potential =
beneficiaries?

=20

Some networks, today, use cRTP (RFC2508) on their access links.  This =
gives
bandwidth savings on the access link, but consumes considerable CPU
horsepower on the aggregation router (to perform cRTP), but provides no
bandwidth savings across the network core.  If, instead, the bandwidth =
could
be saved on the access link, across the core, and on the far-end access =
link
-- all without the CPU impact on the aggregation router -- it is a
considerable win.

=20

-d

=20

=20





=20

=20

Jose

=20

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de =
Jose
Saldana
Enviado el: lunes, 24 de junio de 2013 13:00
Para: tcmtf@ietf.org
Asunto: [tcmtf] Answers to possible questions in the BOF

=20

I would like to start a thread about possible questions people may ask =
in
the BOF. Obviously, we also need answers, so we should cooperate.

=20

This is different from the =93questions to ask in the BOF=94. This will =
be
discussed separately.

=20

Thanks!

=20

Jose

=20

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

=20


------=_NextPart_000_0110_01CE764F.0B1D8120
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texto de globo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.TextodegloboCar
	{mso-style-name:"Texto de globo Car";
	mso-style-priority:99;
	mso-style-link:"Texto de globo";
	font-family:"Tahoma","sans-serif";}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span =
lang=3DEN-US>Hi, Dan.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>I have been reading the article &quot;Cisco adds IP =
multiplexing to mobile satellite package&quot;, and I think there is an =
idea we should stress in the BOF:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>We are not only saving bandwidth =
but also reducing the amount of pps. In the satellite scenario a pps =
reduction can be translated directly to a x20 factor in the number of =
simultaneous calls to be transmitted.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
language:EN-US'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
language:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
language:EN-US'>Jose<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Dan Wing [mailto:dwing@cisco.com] <br><b>Enviado el:</b> mi=E9rcoles, 26 =
de junio de 2013 22:14<br><b>Para:</b> jsaldana@unizar.es<br><b>CC:</b> =
tcmtf@ietf.org<br><b>Asunto:</b> Re: [tcmtf] Answers to possible =
questions in the BOF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Jun 26, 2013, at 3:49 AM, Jose Saldana &lt;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt; =
wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Question 4: Is TCM-TF interesting for the Industry? Should the IETF =
standardize this?</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Answer:</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP =
traffic. So if RFC4170 was interesting, why not updating it?</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>2) TCM-TF can be useful in order to save bandwidth in many =
cases:</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>- Aggregation network of *<b>network operators</b>*: We are saving =
bandwidth by optimizing and putting together traffic flows. Is this =
interesting for a network operator? What about overprovisioning? The =
idea is that there are places and moments in which a number of flows =
based on small packets are in the same place and at the same moment. =
Then, TCM-TF can be applied in order to provide flexibility. We are not =
optimizing the overall Internet traffic, we are optimizing specific =
flows with very tight delay requirements, which network operators have =
to take care of in a special way.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Arial","sans-serif";color:#009933;=
background:white'><a =
href=3D"http://www.huawei.com/ilink/en/download/HW_193034"><span =
style=3D'color:purple'>www.huawei.com/ilink/en/download/HW_193034</span><=
/a></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>- *<b>End to end</b>* optimization: Nowadays, many appliances are =
used to connect remote offices of the same company (creating a VPN). So =
if a tunnel exists, why not optimizing this traffic when possible? We =
would save bandwidth in the access network, where it can be =
scarce.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>- Wireless and satellite scenarios.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>&quot;Cisco adds IP multiplexing to mobile satellite =
package&quot;, April 2012,&nbsp;<a =
href=3D"http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexin=
g-258082.html">http://www.networkworld.com/news/2012/040912-cisco-ip-mult=
iplexing-258082.html</a><o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Any other thoughts? Any other scenarios in mind? Potential =
beneficiaries?</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Some networks, today, use cRTP (RFC2508) on their =
access links. &nbsp;This gives bandwidth savings on the access link, but =
consumes considerable CPU horsepower on the aggregation router (to =
perform cRTP), but provides no bandwidth savings across the network =
core. &nbsp;If, instead, the bandwidth could be saved on the access =
link, across the core, and on the far-end access link -- all without the =
CPU impact on the aggregation router -- it is a considerable =
win.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>-d<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jose</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div style=3D'border:none;border-left:solid blue =
1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><div><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span class=3Dapple-converted-space><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>&nbsp;</span=
></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><a =
href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> =
[mailto:tcmtf-<a =
href=3D"mailto:bounces@ietf.org">bounces@ietf.org</a>]<span =
class=3Dapple-converted-space>&nbsp;</span><b>En nombre de<span =
class=3Dapple-converted-space>&nbsp;</span></b>Jose =
Saldana<br><b>Envia</b></span><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>do =
el:</span></b><span class=3Dapple-converted-space><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>&nbsp;</span=
></span><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>lunes, 24 =
de junio de 2013 13:00<br><b>Para:</b><span =
class=3Dapple-converted-space>&nbsp;</span><a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><b>Asunto:</b><span =
class=3Dapple-converted-space>&nbsp;</span>[tcmtf] Answers to possible =
questions in the BOF</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div></div></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p>=
</o:p></span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I would =
like to start a thread about possible questions people may ask in the =
BOF. Obviously, we also need answers, so we should =
cooperate.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>This is =
different from the &#8220;questions to ask in the BOF&#8221;. This will =
be discussed separately.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Thanks!</sp=
an><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Jose</span>=
<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div></div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>_________=
______________________________________<br>tcmtf mailing =
list<br></span><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'><a =
href=3D"mailto:tcmtf@ietf.org"><span =
lang=3DEN-US>tcmtf@ietf.org</span></a></span><span lang=3DEN-US =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'><br></spa=
n><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'><a =
href=3D"https://www.ietf.org/mailman/listinfo/tcmtf"><span =
lang=3DEN-US>https://www.ietf.org/mailman/listinfo/tcmtf</span></a></span=
><span lang=3DEN-US =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'><o:p></o:=
p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_0110_01CE764F.0B1D8120--


From jsaldana@unizar.es  Mon Jul  1 02:47:05 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 A619E21F9CE2 for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 02:47:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001,  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 n+fJ3KPNVxDv for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 02:47:01 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 6469E21F9CDC for <tcmtf@ietf.org>; Mon,  1 Jul 2013 02:47:00 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r619kulb020656; Mon, 1 Jul 2013 11:46:57 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <jltornos@unizar.es>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>	<009901ce725a$d1623360$74269a20$@unizar.es>	<2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com> <20130628105725.lmag0xgqsgogggww@webmail.unizar.es>
In-Reply-To: <20130628105725.lmag0xgqsgogggww@webmail.unizar.es>
Date: Mon, 1 Jul 2013 11:46:58 +0200
Organization: Universidad de Zaragoza
Message-ID: <011a01ce763f$eddffde0$c99ff9a0$@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: AQHxl5HfJe4XxEPJrqhURPk2/vEH5gJG8kQSAT8jBAUB238Z4JjePvHA
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 01 Jul 2013 09:47:06 -0000

Hi, Jose Luis.

Regarding security, we can also think about "Unified threat management"
(http://en.wikipedia.org/wiki/Unified_Threat_Management), an appliance =
used
for connecting remote offices, creating VPNs.

If we merge this concept with "WAN optimization"
(http://en.wikipedia.org/wiki/WAN_optimization), we can have a device =
next
to the router, which can use TCM-TF.

Considering that security headers, if a new header has to be added to =
each
packet, then the obtained savings by multiplexing can be even higher.
Perhaps we could do a preliminary study of the expected (asymptotic)
bandwidth savings which could be obtained on each case:

- IPSec
	- transport mode
	- tunnel mode

	- Authentication header
	- Encrypt header

More options?


Perhaps we could consider 20 packets, and calculate:

Number of bytes for a tunnel including 20 packets / Number of bytes for =
a 20
tunnels

Would it be very complicated? I am not a security expert...

Jose

> -----Mensaje original-----
> De: jltornos@unizar.es [mailto:jltornos@unizar.es]
> Enviado el: viernes, 28 de junio de 2013 10:57
> Para: Dan Wing
> CC: jsaldana@unizar.es; tcmtf@ietf.org
> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>=20
> Hi all,
>=20
> Few days ago Julian talked about TCM-TF's security and now I've read =
in
the
> link included by Dan, saying that the gain obtained when multiplexing
Ipsec-
> encrypted packets is 20-to-1. We have been looking for more =
information
> about this issue and thinking about a way to reduce the needed  =
bandwidth
> in IPsec flows.
>=20
> The main idea is to find a way to change the authentication of the
individual
> packets and merge all of them in a unique authentication.
> Thus, instead of using 20 IPsec tunnels, we would have a single tunnel
> including 20 flows. Is this something similar than how Cisco gets the
> improvement?
>=20
> Jos=E9 Luis
>=20
>=20
>=20
> Dan Wing <dwing@cisco.com> ha escrito:
>=20
> >
> > On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> =
wrote:
> >
> >> Question 4: Is TCM-TF interesting for the Industry? Should the IETF
> >> standardize this?
> >>
> >> Answer:
> >>
> >> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP
> >> traffic. So if RFC4170 was interesting, why not updating it?
> >>
> >> 2) TCM-TF can be useful in order to save bandwidth in many cases:
> >>
> >> - Aggregation network of *network operators*: We are saving
> >> bandwidth by optimizing and putting together traffic flows. Is this
> >>  interesting for a network operator? What about overprovisioning?
> >> The idea is that there are places and moments in which a number of
> >> flows based on small packets are in the same place and at the same
> >> moment. Then, TCM-TF can be applied in order to provide
> >> flexibility. We are not optimizing the overall Internet traffic, we
> >>  are optimizing specific flows with very tight delay requirements,
> >> which network operators have to take care of in a special way.
> >> www.huawei.com/ilink/en/download/HW_193034
> >>
> >> - *End to end* optimization: Nowadays, many appliances are used to
> >> connect remote offices of the same company (creating a VPN). So if
> >> a tunnel exists, why not optimizing this traffic when possible? We
> >> would save bandwidth in the access network, where it can be scarce.
> >>
> >> - Wireless and satellite scenarios.
> >
> > "Cisco adds IP multiplexing to mobile satellite package", April
> > 2012,
> > http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing-
> 258
> > 082.html
> >
> >
> >
> >>
> >>
> >> Any other thoughts? Any other scenarios in mind? Potential
beneficiaries?
> >
> > Some networks, today, use cRTP (RFC2508) on their access links.
> > This gives bandwidth savings on the access link, but consumes
> > considerable CPU horsepower on the aggregation router (to perform
> > cRTP), but provides no bandwidth savings across the network core.
> > If, instead, the bandwidth could be saved on the access link, across
> >  the core, and on the far-end access link -- all without the CPU
> > impact on the aggregation router -- it is a considerable win.
> >
> > -d
> >
> >
> >
> >>
> >>
> >> Jose
> >>
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> nombre de Jose Saldana
> >> Enviado el: lunes, 24 de junio de 2013 13:00
> >> Para: tcmtf@ietf.org
> >> Asunto: [tcmtf] Answers to possible questions in the BOF
> >>
> >> I would like to start a thread about possible questions people may
> >> ask in the BOF. Obviously, we also need answers, so we should
> >> cooperate.
> >>
> >> This is different from the "questions to ask in the BOF". This will
> >> be discussed separately.
> >>
> >> Thanks!
> >>
> >> Jose
> >>
> >> _______________________________________________
> >> tcmtf mailing list
> >> tcmtf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >
> >
>=20
>=20



From jsaldana@unizar.es  Mon Jul  1 04:26:48 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 2118621F9E3B for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 04:26:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 H0zX1DHsfyeq for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 04:26:43 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 203C021F9DF7 for <tcmtf@ietf.org>; Mon,  1 Jul 2013 04:26:42 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r61BQWEc008086 for <tcmtf@ietf.org>; Mon, 1 Jul 2013 13:26:37 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Mon, 1 Jul 2013 13:26:36 +0200
Organization: Universidad de Zaragoza
Message-ID: <014b01ce764d$dbdcc0c0$93964240$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_014C_01CE765E.9F6590C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5wrz13IWZxxTaCQH6g7L6OvBjX3A==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] Where to talk about security
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 01 Jul 2013 11:26:48 -0000

This is a multipart message in MIME format.

------=_NextPart_000_014C_01CE765E.9F6590C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all.

 

In the "TCM-TF reference model" (
<https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/>
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/) we say nothing
in the "security" section. I am preparing an updated version.

 

We could perhaps talk about the use of security tunnels (perhaps IPSEC) as
the most straightforward solution for providing end-to-end security to the
optimized tunnel. What do you think?

 

Jose 

 


------=_NextPart_000_014C_01CE765E.9F6590C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>Hi all.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>In the &#8220;TCM-TF reference model&#8221; (</span><a =
href=3D"https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/"><spa=
n =
lang=3DEN-US>https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/<=
/span></a><span lang=3DEN-US>) we say nothing in the =
&#8220;security&#8221; section. I am preparing an updated =
version.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>We could perhaps talk about the use of security tunnels =
(perhaps IPSEC) as the most straightforward solution for providing =
end-to-end security to the optimized tunnel. What do you =
think?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-fareast-language:ES'>Jose =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_014C_01CE765E.9F6590C0--


From fpb@tid.es  Mon Jul  1 06:56:14 2013
Return-Path: <fpb@tid.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 4BF2511E814E for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 06:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 I9r1ILHsId2e for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 06:56:10 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id ECD3B11E8109 for <tcmtf@ietf.org>; Mon,  1 Jul 2013 06:56:07 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MP9003O7G1IKL@tid.hi.inet> for tcmtf@ietf.org; Mon, 01 Jul 2013 15:56:06 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 6D.60.03142.67A81D15; Mon, 01 Jul 2013 15:56:06 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MP9003HIG1IKH@tid.hi.inet> for tcmtf@ietf.org; Mon, 01 Jul 2013 15:56:06 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS6-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Mon, 01 Jul 2013 15:56:05 +0200
Date: Mon, 01 Jul 2013 13:54:57 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <014b01ce764d$dbdcc0c0$93964240$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A29C8B52AD@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_3XuOihf1wSOE0EC/42AKyg)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Where to talk about security
Thread-index: Ac5wrz13IWZxxTaCQH6g7L6OvBjX3AFs3v2A
user-agent: Microsoft-MacOutlook/14.3.5.130515
X-AuditID: 0a5f4068-b7f128e000000c46-c0-51d18a767bdb
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42Lhinfg0i3ruhho0HRA12LX5w2MDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKeNq+iqmgy7Biw4G/LA2M07W7GDk5JARMJDZNmcYEYYtJXLi3 nq2LkYtDSGAjo8TZxtdMEM4PRonlxx+DVQkJTGOUOPRGFMRmEVCV+HdpMSuIzSagJXH67ioW EFtYwFCi9c4fNhCbU8BC4vTXGywQGxQk/px7DGaLCARI7G45AGbzCnhL/L9/kx3CFpT4Mfke WJxZIFfib898JghbXKK59SZYnFFAVuLd/PmsEHOMJGZO2AFnL1i4G6xeVEBP4vCe16wQewUk luw5zwxhi0q8fPyPdQKj6Cwk62YhWTcLyToI20Di/bn5zBC2tsSyha+hbH2JjV/OMkLYZhI7 Fj9lQlazgJFjFaNYcVJRZnpGSW5iZk66gaFeRqZeZl5qySZGSNxl7GBcvlPlEKMAB6MSD2/C qguBQqyJZcWVuYcYJTiYlUR4b3pfDBTiTUmsrEotyo8vKs1JLT7EyMTBKdXAODlokWbAbIsr q77fXnddyCq96s+OXWypMjsrbv3t1ZvS+7woeuPabUqWeXFXUjfsyTF4725eMl2mZ0eht8ST r4E3isvn+3xx1+BZx71naZlqidO+T0bGOfGeE7juF296xvnjRsCGbn+xVXu2HbXQX/zQ+57X nt8dMvkq4gubNa7nKy7sXPP3gRJLcUaioRZzUXEiALDL9daZAgAA
Subject: Re: [tcmtf] Where to talk about security
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, 01 Jul 2013 13:56:14 -0000

--Boundary_(ID_3XuOihf1wSOE0EC/42AKyg)
Content-type: text/plain; charset=Windows-1252
Content-transfer-encoding: quoted-printable

Hi Jose,

Yes, I agree with you. IPSec (in tunnel mode) could be included as another =
tunneling protocol adding the security capability to the whole TCM protocol=
.

Best,

Fernando Pascual Blanco
Telef=F3nica Global Resources
Network Automation and Dynamization
TECHNOLOGY PEOPLE GROUP
F +34913128779
M +34682005168
fpb@tid.es

From: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.es<m=
ailto:jsaldana@unizar.es>>
Organization: Universidad de Zaragoza
Reply-To: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.=
es<mailto:jsaldana@unizar.es>>
Date: lunes, 1 de julio de 2013 13:26
To: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Subject: [tcmtf] Where to talk about security

Hi all.

In the =93TCM-TF reference model=94 (https://datatracker.ietf.org/doc/draft=
-saldana-tsvwg-tcmtf/) we say nothing in the =93security=94 section. I am p=
reparing an updated version.

We could perhaps talk about the use of security tunnels (perhaps IPSEC) as =
the most straightforward solution for providing end-to-end security to the =
optimized tunnel. What do you think?

Jose


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

--Boundary_(ID_3XuOihf1wSOE0EC/42AKyg)
Content-id: <2D4041CE379AFD45B4677B10CC244A07@hi.inet>
Content-type: text/html; charset=Windows-1252
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font=
-family:Calibri,sans-serif">
<div>
<div>
<div>Hi Jose,</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Yes, I=
 agree with you. IPSec (in tunnel mode) could be included as another tunnel=
ing protocol adding the security capability to the whole TCM protocol.</div=
>
<div>
<div><br>
</div>
<div>Best,</div>
<div><br>
</div>
<div>Fernando Pascual Blanco</div>
<div>Telef=F3nica Global Resources</div>
<div>Network Automation and Dynamization</div>
<div>TECHNOLOGY PEOPLE GROUP</div>
<div>F &#43;34913128779</div>
<div>M &#43;34682005168</div>
<div>fpb@tid.es</div>
</div>
</div>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; border-bottom:medium none; border-left:medium none; padding-bottom:0i=
n; padding-left:0in; padding-right:0in; border-top:#b5c4df 1pt solid; borde=
r-right:medium none; padding-top:3pt">
<span style=3D"font-weight:bold">From: </span>&quot;<a href=3D"mailto:jsald=
ana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsaldana@=
unizar.es">jsaldana@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Organization: </span>Universidad de Zarago=
za<br>
<span style=3D"font-weight:bold">Reply-To: </span>&quot;<a href=3D"mailto:j=
saldana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsald=
ana@unizar.es">jsaldana@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>lunes, 1 de julio de 2013 13:=
26<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:tcmtf@i=
etf.org">tcmtf@ietf.org</a>&quot; &lt;<a href=3D"mailto:tcmtf@ietf.org">tcm=
tf@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[tcmtf] Where to talk abou=
t security<br>
</div>
<div><br>
</div>
<div><style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
span.EstiloCorreo17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
.MsoChpDefault
	{font-size:10.0pt;
	font-family:"Calibri","sans-serif"}
@page WordSection1
	{margin:70.85pt 3.0cm 70.85pt 3.0cm}
div.WordSection1
	{}
-->
</style>
<div lang=3D"ES">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi all.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">In the =93TCM-TF reference mode=
l=94 (</span><a href=3D"https://datatracker.ietf.org/doc/draft-saldana-tsvw=
g-tcmtf/"><span lang=3D"EN-US">https://datatracker.ietf.org/doc/draft-salda=
na-tsvwg-tcmtf/</span></a><span lang=3D"EN-US">)
 we say nothing in the =93security=94 section. I am preparing an updated ve=
rsion.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We could perhaps talk about the=
 use of security tunnels (perhaps IPSEC) as the most straightforward soluti=
on for providing end-to-end security to the optimized tunnel. What do you t=
hink?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"">Jose </span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
</div>
</div>
</span><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_3XuOihf1wSOE0EC/42AKyg)--

From jsaldana@unizar.es  Mon Jul  1 07:29:36 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 50B3711E80F6 for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 07:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 wbGxhkAYi6Es for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 07:29:31 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2DFAB11E80E7 for <tcmtf@ietf.org>; Mon,  1 Jul 2013 07:29:30 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r61ETODo005071; Mon, 1 Jul 2013 16:29:24 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>, <tcmtf@ietf.org>, <jltornos@unizar.es>
References: <014b01ce764d$dbdcc0c0$93964240$@unizar.es> <F5EDC35DF914C1428C28E149F10463A29C8B52AD@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A29C8B52AD@EX10-MB2-MAD.hi.inet>
Date: Mon, 1 Jul 2013 16:29:29 +0200
Organization: Universidad de Zaragoza
Message-ID: <01a001ce7667$6577eb70$3067c250$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A1_01CE7678.2901A5D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH2ngCFa/PO3nqUW88IgQ9tCzbLwZj/kl2Q
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Where to talk about security
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 01 Jul 2013 14:29:36 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01A1_01CE7678.2901A5D0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

=20

I am improving the =93TCMTF reference model=94 draft, and I have written =
this
short paragraph to be added to the =93security considerations=94:

=20

The most straightforward option for securing a number of TCM flows

sharing a path is by the use of IPsec [IPsec], when an IP tunnel

scheme is used. Instead of adding a security header to each native

packet, and then compressing and multiplexing, a single IPsec tunnel

can be used in order to secure all the flows together, thus

achieving a better efficiency.

=20

=20

What do you think?

=20

Jose

=20

De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]=20
Enviado el: lunes, 01 de julio de 2013 15:55
Para: jsaldana@unizar.es; tcmtf@ietf.org
Asunto: Re: [tcmtf] Where to talk about security

=20

Hi Jose,

=20

Yes, I agree with you. IPSec (in tunnel mode) could be included as =
another
tunneling protocol adding the security capability to the whole TCM =
protocol.

=20

Best,

=20

Fernando Pascual Blanco

Telef=F3nica Global Resources

Network Automation and Dynamization

TECHNOLOGY PEOPLE GROUP

F +34913128779

M +34682005168

fpb@tid.es

=20

From: "jsaldana@unizar.es" <jsaldana@unizar.es>
Organization: Universidad de Zaragoza
Reply-To: "jsaldana@unizar.es" <jsaldana@unizar.es>
Date: lunes, 1 de julio de 2013 13:26
To: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: [tcmtf] Where to talk about security

=20

Hi all.

=20

In the =93TCM-TF reference model=94 (
<https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/>
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/) we say =
nothing
in the =93security=94 section. I am preparing an updated version.

=20

We could perhaps talk about the use of security tunnels (perhaps IPSEC) =
as
the most straightforward solution for providing end-to-end security to =
the
optimized tunnel. What do you think?

=20

Jose=20

=20

=20

  _____ =20


Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en =
el enlace
situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and
receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx


------=_NextPart_000_01A1_01CE7678.2901A5D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><!--[if =
!mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texto de globo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";}
span.estilocorreo17
	{mso-style-name:estilocorreo17;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.TextodegloboCar
	{mso-style-name:"Texto de globo Car";
	mso-style-priority:99;
	mso-style-link:"Texto de globo";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Hi all,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>I am =
improving the &#8220;TCMTF reference model&#8221; draft, and I have =
written this short paragraph to be added to the &#8220;security =
considerations&#8221;:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>The most =
straightforward option for securing a number of TCM =
flows<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'> sharing a path is by the use of IPsec [IPsec], =
when an IP tunnel<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'> scheme is used. Instead of adding =
a security header to each native<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'> packet, =
and then compressing and multiplexing, a single IPsec =
tunnel<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'> can be used in order to secure all the flows =
together, thus<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'> </span><span =
style=3D'color:#1F497D'>achieving a better =
efficiency.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>What do you =
think?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es] <br><b>Enviado el:</b> =
lunes, 01 de julio de 2013 15:55<br><b>Para:</b> jsaldana@unizar.es; =
tcmtf@ietf.org<br><b>Asunto:</b> Re: [tcmtf] Where to talk about =
security<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><p =
class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'>Hi =
Jose,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>Yes, I agree with you. IPSec (in =
tunnel mode) could be included as another tunneling protocol adding the =
security capability to the whole TCM =
protocol.<o:p></o:p></span></p></div><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>Best,<o:p></o:p></span></p></div><=
div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>Fernando Pascual =
Blanco<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>Telef=F3nica Global =
Resources<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>Network Automation and =
Dynamization<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>TECHNOLOGY PEOPLE =
GROUP<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>F =
+34913128779<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>M =
+34682005168<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><a =
href=3D"mailto:fpb@tid.es">fpb@tid.es</a><o:p></o:p></span></p></div></di=
v></div></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'><p class=3DMsoNormal><b><span style=3D'color:black'>From: =
</span></b><span style=3D'color:black'>&quot;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt;<br><b>Organ=
ization: </b>Universidad de Zaragoza<br><b>Reply-To: </b>&quot;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt;<br><b>Date:=
 </b>lunes, 1 de julio de 2013 13:26<br><b>To: </b>&quot;<a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>&gt;<br><b>Subject: =
</b>[tcmtf] Where to talk about =
security<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>Hi all.</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:black'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:black'>In the &#8220;TCM-TF reference =
model&#8221; (</span><span style=3D'color:black'><a =
href=3D"https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/"><spa=
n =
lang=3DEN-US>https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/<=
/span></a></span><span lang=3DEN-US style=3D'color:black'>) we say =
nothing in the &#8220;security&#8221; section. I am preparing an updated =
version.</span><span style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:black'>We could perhaps talk about the use =
of security tunnels (perhaps IPSEC) as the most straightforward solution =
for providing end-to-end security to the optimized tunnel. What do you =
think?</span><span style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:black'>Jose </span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:black'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p></div></div></div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p><div =
class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span =
style=3D'font-size:10.5pt;color:black'><hr size=3D2 width=3D"100%" =
align=3Dcenter></span></div><p class=3DMsoNormal><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br=
>Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico en el enlace situado m=E1s abajo.<br>This message is =
intended exclusively for its addressee. We only send and receive email =
on the basis of the terms set out at:<br><a =
href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/E=
S/PAGINAS/disclaimer.aspx</a></span><span =
style=3D'font-size:10.5pt;color:black'><o:p></o:p></span></p></div></div>=
</body></html>
------=_NextPart_000_01A1_01CE7678.2901A5D0--


From jsaldana@unizar.es  Mon Jul  1 08:34:47 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 BBAF311E80F7 for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 08:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 w+CfZjOGpSRb for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 08:34:43 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id A2A8A11E80EA for <tcmtf@ietf.org>; Mon,  1 Jul 2013 08:34:42 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r61FYDM1016443 for <tcmtf@ietf.org>; Mon, 1 Jul 2013 17:34:35 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Mon, 1 Jul 2013 17:34:18 +0200
Organization: Universidad de Zaragoza
Message-ID: <01b401ce7670$80a53b10$81efb130$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01B5_01CE7681.442EA750"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5ncCm9MWuGJXdaSTKhNw14s+ChMw==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] A new version of the TCMTF - reference model
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 01 Jul 2013 15:34:47 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01B5_01CE7681.442EA750
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

 

I have built a new version of the first draft, "TCMTF - reference model". We
should update it before the meeting in Berlin. I would like to upload it
next Monday, but I would need you to review it first.

 

You can find this improved version here:
<http://diec.unizar.es/~jsaldana/personal/ietf/draft-saldana-tcmtf_v18.pdf>
http://diec.unizar.es/~jsaldana/personal/ietf/draft-saldana-tcmtf_v18.pdf

 

These are the main changes:

 

- I have used "TCM-TF" instead of "TCMTF"

 

- I have improved abstract and the introduction, re-ordering the sections
and subsections. I have tried to talk a bit more about "small-packet flows",
since it includes real-time and non real-time flows that we are trying to
optimize.

 

- A new section "Terminology", including the names and terms we agreed in
the list, has been added. In addition, I have tried to unify these terms in
the document.

 

- I have improved the classification of the scenarios of application.

 

- I have updates of the ROHC reference to RFC 5795, which obsoleted RFC
4995.

 

- A new paragraph about security in the end (the one I have just sent
before).

 

Comments will be welcome. Next Monday I would upload it with the uploads you
suggest. 

 

Jose 

 


------=_NextPart_000_01B5_01CE7681.442EA750
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>Hi all,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>I have built a new version of the first draft, &#8220;TCMTF =
- reference model&#8221;. We should update it before the meeting in =
Berlin. I would like to upload it next Monday, but I would need you to =
review it first.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>You can find this improved version here: </span><a =
href=3D"http://diec.unizar.es/~jsaldana/personal/ietf/draft-saldana-tcmtf=
_v18.pdf"><span =
lang=3DEN-US>http://diec.unizar.es/~jsaldana/personal/ietf/draft-saldana-=
tcmtf_v18.pdf</span></a><span lang=3DEN-US><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>These are the main =
changes:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- I have used &#8220;TCM-TF&#8221; instead of =
&#8220;TCMTF&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- I have improved abstract and the introduction, =
re-ordering the sections and subsections. I have tried to talk a bit =
more about &#8220;small-packet flows&#8221;, since it includes real-time =
and non real-time flows that we are trying to =
optimize.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- A new section &#8220;Terminology&#8221;, including the =
names and terms we agreed in the list, has been added. In addition, I =
have tried to unify these terms in the document.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- I have improved the =
classification of the scenarios of application.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- I have updates of the ROHC =
reference to RFC 5795, which obsoleted RFC 4995.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- A new paragraph about security in =
the end (the one I have just sent before).<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Comments will be welcome. Next =
Monday I would upload it with the uploads you suggest. =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-fareast-language:ES'>Jose =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_01B5_01CE7681.442EA750--


From navajas@unizar.es  Mon Jul  1 09:11:47 2013
Return-Path: <navajas@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 C422811E81B2 for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 09:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 wsEHKcYmTtKF for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 09:11:43 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id D853F11E8181 for <tcmtf@ietf.org>; Mon,  1 Jul 2013 09:11:34 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r61GBS8m022056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Mon, 1 Jul 2013 18:11:29 +0200
Message-ID: <51D1AA30.5080600@unizar.es>
Date: Mon, 01 Jul 2013 18:11:28 +0200
From: =?ISO-8859-15?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <F5EDC35DF914C1428C28E149F10463A29C8B52AD@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A29C8B52AD@EX10-MB2-MAD.hi.inet>
Content-Type: multipart/alternative; boundary="------------050505040905090003040602"
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Where to talk about security
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, 01 Jul 2013 16:11:47 -0000

This is a multi-part message in MIME format.
--------------050505040905090003040602
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit

Hi all,
I think not only in tunnel mode but also in transport mode.
In transport mode is possible to achieve improved efficiency by using 
TCMTF. In tunnel mode, the aim would be to substitute this by TCMTF and 
achieve improved more efficiency.
Best regards
Julián


El 01/07/2013 15:54, FERNANDO PASCUAL BLANCO escribió:
> Hi Jose,
>
> Yes, I agree with you. IPSec (in tunnel mode) could be included as 
> another tunneling protocol adding the security capability to the whole 
> TCM protocol.
>
> Best,
>
> Fernando Pascual Blanco
> Telefónica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>
> From: "jsaldana@unizar.es <mailto:jsaldana@unizar.es>" 
> <jsaldana@unizar.es <mailto:jsaldana@unizar.es>>
> Organization: Universidad de Zaragoza
> Reply-To: "jsaldana@unizar.es <mailto:jsaldana@unizar.es>" 
> <jsaldana@unizar.es <mailto:jsaldana@unizar.es>>
> Date: lunes, 1 de julio de 2013 13:26
> To: "tcmtf@ietf.org <mailto:tcmtf@ietf.org>" <tcmtf@ietf.org 
> <mailto:tcmtf@ietf.org>>
> Subject: [tcmtf] Where to talk about security
>
> Hi all.
>
> In the "TCM-TF reference model" 
> (https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/) we say 
> nothing in the "security" section. I am preparing an updated version.
>
> We could perhaps talk about the use of security tunnels (perhaps 
> IPSEC) as the most straightforward solution for providing end-to-end 
> security to the optimized tunnel. What do you think?
>
> Jose
>
>
> ------------------------------------------------------------------------
>
> Este mensaje se dirige exclusivamente a su destinatario. Puede 
> consultar nuestra política de envío y recepción de correo electrónico 
> en el enlace situado más abajo.
> This message is intended exclusively for its addressee. We only send 
> and receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


--------------050505040905090003040602
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-15"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi all,<br>
      I think not only in tunnel mode but also in transport mode.<br>
      In transport mode is possible to achieve improved efficiency by
      using TCMTF. In tunnel mode, the aim would be to substitute this
      by TCMTF and achieve improved more efficiency.<br>
      Best regards<br>
      Julián<br>
      <br>
      <br>
      El 01/07/2013 15:54, FERNANDO PASCUAL BLANCO escribió:<br>
    </div>
    <blockquote
      cite="mid:F5EDC35DF914C1428C28E149F10463A29C8B52AD@EX10-MB2-MAD.hi.inet"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-15">
      <div>
        <div>
          <div>Hi Jose,</div>
          <div><br>
          </div>
          <div><span class="Apple-tab-span" style="white-space:pre"></span>Yes,
            I agree with you. IPSec (in tunnel mode) could be included
            as another tunneling protocol adding the security capability
            to the whole TCM protocol.</div>
          <div>
            <div><br>
            </div>
            <div>Best,</div>
            <div><br>
            </div>
            <div>Fernando Pascual Blanco</div>
            <div>Telefónica Global Resources</div>
            <div>Network Automation and Dynamization</div>
            <div>TECHNOLOGY PEOPLE GROUP</div>
            <div>F +34913128779</div>
            <div>M +34682005168</div>
            <div><a class="moz-txt-link-abbreviated" href="mailto:fpb@tid.es">fpb@tid.es</a></div>
          </div>
        </div>
      </div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <div style="font-family:Calibri; font-size:11pt;
          text-align:left; color:black; border-bottom:medium none;
          border-left:medium none; padding-bottom:0in; padding-left:0in;
          padding-right:0in; border-top:#b5c4df 1pt solid;
          border-right:medium none; padding-top:3pt">
          <span style="font-weight:bold">From: </span>"<a
            moz-do-not-send="true" href="mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>"
          &lt;<a moz-do-not-send="true" href="mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt;<br>
          <span style="font-weight:bold">Organization: </span>Universidad
          de Zaragoza<br>
          <span style="font-weight:bold">Reply-To: </span>"<a
            moz-do-not-send="true" href="mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>"
          &lt;<a moz-do-not-send="true" href="mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt;<br>
          <span style="font-weight:bold">Date: </span>lunes, 1 de julio
          de 2013 13:26<br>
          <span style="font-weight:bold">To: </span>"<a
            moz-do-not-send="true" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>"
          &lt;<a moz-do-not-send="true" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>&gt;<br>
          <span style="font-weight:bold">Subject: </span>[tcmtf] Where
          to talk about security<br>
        </div>
        <div><br>
        </div>
        <div>
          <style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
span.EstiloCorreo17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
.MsoChpDefault
	{font-size:10.0pt;
	font-family:"Calibri","sans-serif"}
@page WordSection1
	{margin:70.85pt 3.0cm 70.85pt 3.0cm}
div.WordSection1
	{}
-->
</style>
          <div lang="ES">
            <div class="WordSection1">
              <p class="MsoNormal"><span lang="EN-US">Hi all.</span></p>
              <p class="MsoNormal"><span lang="EN-US"> </span></p>
              <p class="MsoNormal"><span lang="EN-US">In the &#8220;TCM-TF
                  reference model&#8221; (</span><a moz-do-not-send="true"
                  href="https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/"><span
                    lang="EN-US">https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</span></a><span
                  lang="EN-US">) we say nothing in the &#8220;security&#8221;
                  section. I am preparing an updated version.</span></p>
              <p class="MsoNormal"><span lang="EN-US"> </span></p>
              <p class="MsoNormal"><span lang="EN-US">We could perhaps
                  talk about the use of security tunnels (perhaps IPSEC)
                  as the most straightforward solution for providing
                  end-to-end security to the optimized tunnel. What do
                  you think?</span></p>
              <p class="MsoNormal"><span lang="EN-US"> </span></p>
              <p class="MsoNormal"><span style="" lang="EN-US">Jose </span></p>
              <p class="MsoNormal"><span lang="EN-US"> </span></p>
            </div>
          </div>
        </div>
      </span><br>
      <hr>
      <font color="Gray" face="Arial" size="1"><br>
        Este mensaje se dirige exclusivamente a su destinatario. Puede
        consultar nuestra política de envío y recepción de correo
        electrónico en el enlace situado más abajo.<br>
        This message is intended exclusively for its addressee. We only
        send and receive email on the basis of the terms set out at:<br>
        <a class="moz-txt-link-freetext" href="http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/ES/PAGINAS/disclaimer.aspx</a><br>
      </font>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
tcmtf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tcmtf">https://www.ietf.org/mailman/listinfo/tcmtf</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050505040905090003040602--

From dwing@cisco.com  Mon Jul  1 09:49:29 2013
Return-Path: <dwing@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 E871921F9590 for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 09:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.49
X-Spam-Level: 
X-Spam-Status: No, score=-109.49 tagged_above=-999 required=5 tests=[AWL=1.109, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 A8MRNJd6iQjD for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 09:49:26 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id B639421F94D3 for <tcmtf@ietf.org>; Mon,  1 Jul 2013 09:48:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4479; q=dns/txt; s=iport; t=1372697337; x=1373906937; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=gvVHYXVwcbrhRWnF4B2MV8QlwhWlb2ypEmwNUbv+wow=; b=bW433fmkhC61+h+DukRRqALKFQlp7cYoro7CfUdA9LTmw/ZqnAU5Mxp4 l2E7kscjFrnGqWkVFEW9Yz2JskbIDYSz2Fi1iHFV9WVwLSZE76mp8Fhr6 qr8I08L4HX9g6+8GJm3aLCLD5sLJTiUDhR1+ThELKKJeJNNmnzurqOSWF Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFABSx0VGrRDoI/2dsb2JhbABagwkyv2N/FnSCIwEBAQMBAQEBRiULBQsJAhEEAQEBJwcnHwkIGRoEh2sFDY9nrEWNDYEEgRozB4MEYwOJI4pTg1KRRYMxHA
X-IronPort-AV: E=Sophos;i="4.87,975,1363132800"; d="scan'208";a="81842798"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 01 Jul 2013 16:48:55 +0000
Received: from sjc-vpn2-667.cisco.com (sjc-vpn2-667.cisco.com [10.21.114.155]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r61GmseZ031558; Mon, 1 Jul 2013 16:48:54 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <1A39DCC13AF3C14B83CD74124D4DCFC316F8EFAC@DLREXMBX01.intra.dlr.de>
Date: Mon, 1 Jul 2013 09:48:53 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D2029C2A-C04D-4C25-8FAB-D936CAF356F9@cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com> <1A39DCC13AF3C14B83CD74124D4DCFC316F8EFAC@DLREXMBX01.intra.dlr.de>
To: Tomaso.deCola@dlr.de
X-Mailer: Apple Mail (2.1508)
Cc: tcmtf@ietf.org, jsaldana@unizar.es
Subject: Re: [tcmtf] Answers to possible questions in 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: Mon, 01 Jul 2013 16:49:30 -0000

On Jun 27, 2013, at 2:53 AM, Tomaso.deCola@dlr.de wrote:

> Hi Dan,
> =20
> Would it be possible to have more info on this CISCO product?

It just holds onto small packets -- especially TCP ACKs -- until a timer =
fires or the packet is full.  I was not involved with that project, and =
I don't work on satellite, but I am told this reduces the overhead of =
the satellite modem dealing with all the little tiny packets.

> =20
> Actually, nowadays satellite technology already implements =
multiplexing capabilities to better exploit the satellite capacity.
> In this respect it would be interesting to understand the interaction =
of the CISCO multiplexing-enabled router and the functions already =
available in satellite terminals.

I don't have that detail.

-d


> =20
> Thanks in advance
> =20
> Regards,
> =20
> Tomaso
> =20
> =97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=97=
=20
> Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR)=20
> German Aerospace Center=20
> Institute of Communications and Navigation | Satellite Networks | =
Oberpfaffenhofen | 82234 Wessling | Germany
> Tomaso de Cola, Ph.D.=20
> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 | =
tomaso.decola@dlr.de=20
> http://www.dlr.de/kn/institut/abteilungen/san
> =20
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =
Of Dan Wing
> Sent: Wednesday, June 26, 2013 10:14 PM
> To: jsaldana@unizar.es
> Cc: tcmtf@ietf.org
> Subject: Re: [tcmtf] Answers to possible questions in the BOF
> =20
> =20
> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> wrote:
>=20
>=20
> Question 4: Is TCM-TF interesting for the Industry? Should the IETF =
standardize this?
> =20
> Answer:
> =20
> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP traffic. =
So if RFC4170 was interesting, why not updating it?
> =20
> 2) TCM-TF can be useful in order to save bandwidth in many cases:
> =20
> - Aggregation network of *network operators*: We are saving bandwidth =
by optimizing and putting together traffic flows. Is this interesting =
for a network operator? What about overprovisioning? The idea is that =
there are places and moments in which a number of flows based on small =
packets are in the same place and at the same moment. Then, TCM-TF can =
be applied in order to provide flexibility. We are not optimizing the =
overall Internet traffic, we are optimizing specific flows with very =
tight delay requirements, which network operators have to take care of =
in a special way.
> www.huawei.com/ilink/en/download/HW_193034
> =20
> - *End to end* optimization: Nowadays, many appliances are used to =
connect remote offices of the same company (creating a VPN). So if a =
tunnel exists, why not optimizing this traffic when possible? We would =
save bandwidth in the access network, where it can be scarce.
> =20
> - Wireless and satellite scenarios.
> =20
> "Cisco adds IP multiplexing to mobile satellite package", April 2012, =
http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing-258082.=
html
> =20
> =20
>=20
>=20
> =20
> =20
> Any other thoughts? Any other scenarios in mind? Potential =
beneficiaries?
> =20
> Some networks, today, use cRTP (RFC2508) on their access links.  This =
gives bandwidth savings on the access link, but consumes considerable =
CPU horsepower on the aggregation router (to perform cRTP), but provides =
no bandwidth savings across the network core.  If, instead, the =
bandwidth could be saved on the access link, across the core, and on the =
far-end access link -- all without the CPU impact on the aggregation =
router -- it is a considerable win.
> =20
> -d
> =20
> =20
>=20
>=20
> =20
> =20
> Jose
> =20
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de Jose Saldana
> Enviado el: lunes, 24 de junio de 2013 13:00
> Para: tcmtf@ietf.org
> Asunto: [tcmtf] Answers to possible questions in the BOF
> =20
> I would like to start a thread about possible questions people may ask =
in the BOF. Obviously, we also need answers, so we should cooperate.
> =20
> This is different from the =93questions to ask in the BOF=94. This =
will be discussed separately.
> =20
> Thanks!
> =20
> Jose
> =20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From dwing@cisco.com  Mon Jul  1 09:55:34 2013
Return-Path: <dwing@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 49B9F11E81FD for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 09:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.044
X-Spam-Level: 
X-Spam-Status: No, score=-110.044 tagged_above=-999 required=5 tests=[AWL=0.555, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 OEt-V8zquXvn for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 09:55:30 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 34B1211E822A for <tcmtf@ietf.org>; Mon,  1 Jul 2013 09:55:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4405; q=dns/txt; s=iport; t=1372697730; x=1373907330; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=S53Dik4HwoDzRM5mz8DSBGVgBefzE/1hSAjjdAlrx40=; b=LXk/8mCtn7CJjPrirKOKQjYCXi9cdf7SpIyCgZtLrSsq9fgzeERd0v5p jy9NqFIfcz6AqfNYfStbYbIJw5wPVxrg75+uzW7Pr9ORnQUd41rbITMvS rzwMQgS48MW4lPJ29+x1BU0oTPFQFGg83zKMPBNRaej2VpfhOn7AipPpr 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAJSy0VGrRDoI/2dsb2JhbABagwkyv2N/FnSCIwEBAQMBAQEBRiMCCAMFCwsYJwcnHxEZGgSHawUNvDGOEYEaMweDBGMDiSOKU4NSkUWDMRw
X-IronPort-AV: E=Sophos;i="4.87,975,1363132800"; d="scan'208";a="84862097"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 01 Jul 2013 16:55:28 +0000
Received: from sjc-vpn2-667.cisco.com (sjc-vpn2-667.cisco.com [10.21.114.155]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r61GtR0E004609; Mon, 1 Jul 2013 16:55:27 GMT
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <20130628105725.lmag0xgqsgogggww@webmail.unizar.es>
Date: Mon, 1 Jul 2013 09:55:25 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com> <20130628105725.lmag0xgqsgogggww@webmail.unizar.es>
To: jltornos@unizar.es
X-Mailer: Apple Mail (2.1508)
Cc: tcmtf@ietf.org, jsaldana@unizar.es
Subject: Re: [tcmtf] Answers to possible questions in 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: Mon, 01 Jul 2013 16:55:34 -0000

On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:

> Hi all,
>=20
> Few days ago Julian talked about TCM-TF's security and now I've read =
in the link included by Dan, saying that the gain obtained when =
multiplexing Ipsec-encrypted packets is 20-to-1. We have been looking =
for more information about this issue and thinking about a way to reduce =
the needed  bandwidth in IPsec flows.
>=20
> The main idea is to find a way to change the authentication of the =
individual packets and merge all of them in a unique authentication. =
Thus, instead of using 20 IPsec tunnels, we would have a single tunnel =
including 20 flows. Is this something similar than how Cisco gets the =
improvement?

We would not be able to change IPsec any more than we could change TCP, =
so I would not look at how to change IPsec authentication. =20

However, if there are a bunch of IPsec packets sharing a common path, I =
could see them being successfully multiplexed into one larger packet at =
one tunnel endpoint and then de-multiplexed at the other tunnel =
endpoint.  This can provide a packet per second reduction.  I don't =
think there are enough bytes in an IPsec header to bother trying to do =
IPsec header compression (SPI and sequence number are only 64 bits).

-d


>=20
> Jos=E9 Luis
>=20
>=20
>=20
> Dan Wing <dwing@cisco.com> ha escrito:
>=20
>>=20
>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> wrote:
>>=20
>>> Question 4: Is TCM-TF interesting for the Industry? Should the IETF  =
standardize this?
>>>=20
>>> Answer:
>>>=20
>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP  =
traffic. So if RFC4170 was interesting, why not updating it?
>>>=20
>>> 2) TCM-TF can be useful in order to save bandwidth in many cases:
>>>=20
>>> - Aggregation network of *network operators*: We are saving  =
bandwidth by optimizing and putting together traffic flows. Is this  =
interesting for a network operator? What about overprovisioning?  The =
idea is that there are places and moments in which a number of  flows =
based on small packets are in the same place and at the same  moment. =
Then, TCM-TF can be applied in order to provide  flexibility. We are not =
optimizing the overall Internet traffic, we  are optimizing specific =
flows with very tight delay requirements,  which network operators have =
to take care of in a special way.
>>> www.huawei.com/ilink/en/download/HW_193034
>>>=20
>>> - *End to end* optimization: Nowadays, many appliances are used to  =
connect remote offices of the same company (creating a VPN). So if  a =
tunnel exists, why not optimizing this traffic when possible? We  would =
save bandwidth in the access network, where it can be scarce.
>>>=20
>>> - Wireless and satellite scenarios.
>>=20
>> "Cisco adds IP multiplexing to mobile satellite package", April  =
2012,  =
http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing-258082.=
html
>>=20
>>=20
>>=20
>>>=20
>>>=20
>>> Any other thoughts? Any other scenarios in mind? Potential =
beneficiaries?
>>=20
>> Some networks, today, use cRTP (RFC2508) on their access links.   =
This gives bandwidth savings on the access link, but consumes  =
considerable CPU horsepower on the aggregation router (to perform  =
cRTP), but provides no bandwidth savings across the network core.   If, =
instead, the bandwidth could be saved on the access link, across  the =
core, and on the far-end access link -- all without the CPU  impact on =
the aggregation router -- it is a considerable win.
>>=20
>> -d
>>=20
>>=20
>>=20
>>>=20
>>>=20
>>> Jose
>>>=20
>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En  =
nombre de Jose Saldana
>>> Enviado el: lunes, 24 de junio de 2013 13:00
>>> Para: tcmtf@ietf.org
>>> Asunto: [tcmtf] Answers to possible questions in the BOF
>>>=20
>>> I would like to start a thread about possible questions people may  =
ask in the BOF. Obviously, we also need answers, so we should  =
cooperate.
>>>=20
>>> This is different from the "questions to ask in the BOF". This will  =
be discussed separately.
>>>=20
>>> Thanks!
>>>=20
>>> Jose
>>>=20
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>=20
>>=20
>=20
>=20
>=20


From mramalho@cisco.com  Mon Jul  1 11:42:52 2013
Return-Path: <mramalho@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 316EF11E81DC for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 11:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 WXw1fNhT8q0P for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 11:42:47 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 0C05111E80E8 for <tcmtf@ietf.org>; Mon,  1 Jul 2013 11:42:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12138; q=dns/txt; s=iport; t=1372704167; x=1373913767; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=hnWO3/iWlLRDwczlksoBzH8u6UNi00Yj8BP7GQ5yX7M=; b=a7KAPmkWzE8WoJMaqGEdAg+pEKPKURkgH+vM08m+SzYFbti4kGpKu0HC aD+833jFGlkwlaxR2uPrjghUDQz4mS1k4L7hdm6lc8Gory227uKcaj81J JkVzMt5Vo6HnV/FPdHlflxjVNFHSTdL9ubZB74w99jY7HiXNGGn7rxd8o k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFACDM0VGtJXG+/2dsb2JhbABagkVEMkm/LoEAFnSCIwEBAQQtHEACAQgRBAEBCx0HMhQJCAEBBAESCIgHDLwqjy03AYMEYwOTdpUXgxGCKA
X-IronPort-AV: E=Sophos;i="4.87,975,1363132800";  d="scan'208,217";a="229618849"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-3.cisco.com with ESMTP; 01 Jul 2013 18:42:45 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r61IgjGc008273 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 1 Jul 2013 18:42:45 GMT
Received: from xmb-rcd-x12.cisco.com ([169.254.2.54]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Mon, 1 Jul 2013 13:42:45 -0500
From: "Michael Ramalho (mramalho)" <mramalho@cisco.com>
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] Answers to possible questions in the BOF
Thread-Index: Ac5wycGHbApylKz/RhmtAnL3dgONFwBuvVeAAQFOolA=
Date: Mon, 1 Jul 2013 18:42:44 +0000
Message-ID: <D21571530BF9644D9A443D6BD95B91031558CCC1@xmb-rcd-x12.cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es>
In-Reply-To: <009901ce725a$d1623360$74269a20$@unizar.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.125.234]
Content-Type: multipart/alternative; boundary="_000_D21571530BF9644D9A443D6BD95B91031558CCC1xmbrcdx12ciscoc_"
MIME-Version: 1.0
Subject: Re: [tcmtf] Answers to possible questions in 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: Mon, 01 Jul 2013 18:42:52 -0000

--_000_D21571530BF9644D9A443D6BD95B91031558CCC1xmbrcdx12ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

In the space of "more ideas" ...

Internet of Things devices are likely to send a lot of little packets, infr=
equently.  Some of those things will have time-sensitive information - but =
a whole lot of those things will send information that is not very time sen=
sitive. For example, consider the sensor reporting the present temperature =
inside my home  freezer where even 500ms or more delay is acceptable.

With many IoT devices, it can be helpful to aggregate those small not-too-d=
elay-sensitive packets.

Michael Ramalho

From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of J=
ose Saldana
Sent: Wednesday, June 26, 2013 6:49 AM
To: tcmtf@ietf.org
Subject: Re: [tcmtf] Answers to possible questions in the BOF

Question 4: Is TCM-TF interesting for the Industry? Should the IETF standar=
dize this?

Answer:

1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP traffic. So i=
f RFC4170 was interesting, why not updating it?

2) TCM-TF can be useful in order to save bandwidth in many cases:

- Aggregation network of *network operators*: We are saving bandwidth by op=
timizing and putting together traffic flows. Is this interesting for a netw=
ork operator? What about overprovisioning? The idea is that there are place=
s and moments in which a number of flows based on small packets are in the =
same place and at the same moment. Then, TCM-TF can be applied in order to =
provide flexibility. We are not optimizing the overall Internet traffic, we=
 are optimizing specific flows with very tight delay requirements, which ne=
twork operators have to take care of in a special way.
www.huawei.com/ilink/en/download/HW_193034<http://www.huawei.com/ilink/en/d=
ownload/HW_193034>

- *End to end* optimization: Nowadays, many appliances are used to connect =
remote offices of the same company (creating a VPN). So if a tunnel exists,=
 why not optimizing this traffic when possible? We would save bandwidth in =
the access network, where it can be scarce.

- Wireless and satellite scenarios.


Any other thoughts? Any other scenarios in mind? Potential beneficiaries?


Jose

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de Jos=
e Saldana
Enviado el: lunes, 24 de junio de 2013 13:00
Para: tcmtf@ietf.org
Asunto: [tcmtf] Answers to possible questions in the BOF

I would like to start a thread about possible questions people may ask in t=
he BOF. Obviously, we also need answers, so we should cooperate.

This is different from the "questions to ask in the BOF". This will be disc=
ussed separately.

Thanks!

Jose


--_000_D21571530BF9644D9A443D6BD95B91031558CCC1xmbrcdx12ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:70.85pt 85.05pt 70.85pt 85.05pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In the space of &#8220=
;more ideas&#8221; &#8230;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Internet of Things dev=
ices are likely to send a lot of little packets, infrequently.&nbsp; Some o=
f those things will have time-sensitive information &#8211; but a whole lot=
 of those things will send information that is
 not very time sensitive. For example, consider the sensor reporting the pr=
esent temperature inside my home &nbsp;freezer where even 500ms or more del=
ay is acceptable.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">With many IoT devices,=
 it can be helpful to aggregate those small not-too-delay-sensitive packets=
.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Michael Ramalho<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tcmtf-bo=
unces@ietf.org [mailto:tcmtf-bounces@ietf.org]
<b>On Behalf Of </b>Jose Saldana<br>
<b>Sent:</b> Wednesday, June 26, 2013 6:49 AM<br>
<b>To:</b> tcmtf@ietf.org<br>
<b>Subject:</b> Re: [tcmtf] Answers to possible questions in the BOF<o:p></=
o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Question 4: Is TCM-TF =
interesting for the Industry? Should the IETF standardize this?<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Answer:<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">1) TCM-TF intends to u=
pdate RFC4170, which optimizes RTP VoIP traffic. So if RFC4170 was interest=
ing, why not updating it?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">2) TCM-TF can be usefu=
l in order to save bandwidth in many cases:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- Aggregation network =
of *<b>network operators</b>*: We are saving bandwidth by optimizing and pu=
tting together traffic flows. Is this interesting for a network operator? W=
hat about overprovisioning? The idea
 is that there are places and moments in which a number of flows based on s=
mall packets are in the same place and at the same moment. Then, TCM-TF can=
 be applied in order to provide flexibility. We are not optimizing the over=
all Internet traffic, we are optimizing
 specific flows with very tight delay requirements, which network operators=
 have to take care of in a special way.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#009933;background:white"><a href=3D=
"http://www.huawei.com/ilink/en/download/HW_193034">www.huawei.com/ilink/en=
/download/HW_193034</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- *<b>End to end</b>* =
optimization: Nowadays, many appliances are used to connect remote offices =
of the same company (creating a VPN). So if a tunnel exists, why not optimi=
zing this traffic when possible? We
 would save bandwidth in the access network, where it can be scarce.<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- Wireless and satelli=
te scenarios.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Any other thoughts? An=
y other scenarios in mind? Potential beneficiaries?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jose<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ES">De:</span></b=
><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-=
serif&quot;;mso-fareast-language:ES"> tcmtf-bounces@ietf.org [mailto:tcmtf-=
bounces@ietf.org]
<b>En nombre de </b>Jose Saldana<br>
<b>Envia</b></span><b><span lang=3D"ES" style=3D"font-size:10.0pt;font-fami=
ly:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ES">do el=
:</span></b><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;T=
ahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ES"> lunes, 24 de j=
unio
 de 2013 13:00<br>
<b>Para:</b> tcmtf@ietf.org<br>
<b>Asunto:</b> [tcmtf] Answers to possible questions in the BOF<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">I would like to start a thread about possible questi=
ons people may ask in the BOF. Obviously, we also need answers, so we shoul=
d cooperate.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is different from the &#8220;questions to ask i=
n the BOF&#8221;. This will be discussed separately.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks!<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"mso-fareast-language:ES">Jose<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_D21571530BF9644D9A443D6BD95B91031558CCC1xmbrcdx12ciscoc_--

From jsalazar@unizar.es  Mon Jul  1 11:50:27 2013
Return-Path: <jsalazar@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 36FAB11E81B0 for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 11:50:27 -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 TfkWHTt17WuM for <tcmtf@ietfa.amsl.com>; Mon,  1 Jul 2013 11:50:23 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 9CE6C11E8135 for <tcmtf@ietf.org>; Mon,  1 Jul 2013 11:50:22 -0700 (PDT)
Received: from mail.unizar.es (flumen.unizar.es [155.210.11.58]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r61IoI3c025122 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Mon, 1 Jul 2013 20:50:18 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Date: Mon, 01 Jul 2013 20:50:20 +0200
From: jsalazar <jsalazar@unizar.es>
To: tcmtf@ietf.org
In-Reply-To: <EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com> <20130628105725.lmag0xgqsgogggww@webmail.unizar.es> <EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com>
Message-ID: <95d1a818ab88cf76070677949afba188@unizar.es>
X-Sender: jsalazar@unizar.es
User-Agent: Roundcube Webmail/0.8.5
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Answers to possible questions in 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: Mon, 01 Jul 2013 18:50:27 -0000

Hi all:
Mmmmmmm. Since I see tcm-tf as a service, I can design the service with 
added security features that the type of communication is requiring. I 
think we have to be clear what we are expressing when we are talking 
about secure tcm-tf: Ensuring the service tcm-tf or applying the tcm-tf 
service for secure communications.
The first possibility is not a great technological sophistication and 
the second one might consider the first one as a possible additional 
service. Therefore, every time we use the term "secure tcm-tf" should 
think the second option, for generality.
On the other hand, we must also keep in mind that whenever users employ 
secure tcm-tf, they must trust the service fully and consider delegating 
the use of their keys (including private ones) to tcm-tf.

Regards.

JL

"I see them falling out the skies like eagles
All mirrored glass and shattered egos"

Simple Minds.

El 2013-07-01 18:55, Dan Wing escribiÃ³:
> On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
> 
> Hi all,
> 
> Few days ago Julian talked about TCM-TF's security and now I've read in 
> the link included by Dan, saying that the gain obtained when 
> multiplexing Ipsec-encrypted packets is 20-to-1. We have been looking 
> for more information about this issue and thinking about a way to 
> reduce the needed  bandwidth in IPsec flows.
> 
> The main idea is to find a way to change the authentication of the 
> individual packets and merge all of them in a unique authentication. 
> Thus, instead of using 20 IPsec tunnels, we would have a single tunnel 
> including 20 flows. Is this something similar than how Cisco gets the 
> improvement?
> 
> We would not be able to change IPsec any more than we could change
> TCP, so I would not look at how to change IPsec authentication.
> 
> However, if there are a bunch of IPsec packets sharing a common path,
> I could see them being successfully multiplexed into one larger packet
> at one tunnel endpoint and then de-multiplexed at the other tunnel
> endpoint.  This can provide a packet per second reduction.  I don't
> think there are enough bytes in an IPsec header to bother trying to do
> IPsec header compression (SPI and sequence number are only 64 bits).
> 
> -d
> 
> 
> 
> JosÃ© Luis
> 
> 
> 
> Dan Wing <dwing@cisco.com> ha escrito:
> 
> 
> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> wrote:
> 
> Question 4: Is TCM-TF interesting for the Industry? Should the IETF  
> standardize this?
> 
> Answer:
> 
> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP  traffic. 
> So if RFC4170 was interesting, why not updating it?
> 
> 2) TCM-TF can be useful in order to save bandwidth in many cases:
> 
> - Aggregation network of *network operators*: We are saving  bandwidth 
> by optimizing and putting together traffic flows. Is this  interesting 
> for a network operator? What about overprovisioning?  The idea is that 
> there are places and moments in which a number of  flows based on small 
> packets are in the same place and at the same  moment. Then, TCM-TF can 
> be applied in order to provide  flexibility. We are not optimizing the 
> overall Internet traffic, we  are optimizing specific flows with very 
> tight delay requirements,  which network operators have to take care of 
> in a special way.
> www.huawei.com/ilink/en/download/HW_193034
> 
> - *End to end* optimization: Nowadays, many appliances are used to  
> connect remote offices of the same company (creating a VPN). So if  a 
> tunnel exists, why not optimizing this traffic when possible? We  would 
> save bandwidth in the access network, where it can be scarce.
> 
> - Wireless and satellite scenarios.
> 
> "Cisco adds IP multiplexing to mobile satellite package", April  2012,  
> http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing-258082.html
> 
> 
> 
> 
> 
> Any other thoughts? Any other scenarios in mind? Potential 
> beneficiaries?
> 
> Some networks, today, use cRTP (RFC2508) on their access links.   This 
> gives bandwidth savings on the access link, but consumes  considerable 
> CPU horsepower on the aggregation router (to perform  cRTP), but 
> provides no bandwidth savings across the network core.   If, instead, 
> the bandwidth could be saved on the access link, across  the core, and 
> on the far-end access link -- all without the CPU  impact on the 
> aggregation router -- it is a considerable win.
> 
> -d
> 
> 
> 
> 
> 
> Jose
> 
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En  nombre 
> de Jose Saldana
> Enviado el: lunes, 24 de junio de 2013 13:00
> Para: tcmtf@ietf.org
> Asunto: [tcmtf] Answers to possible questions in the BOF
> 
> I would like to start a thread about possible questions people may  ask 
> in the BOF. Obviously, we also need answers, so we should  cooperate.
> 
> This is different from the "questions to ask in the BOF". This will  be 
> discussed separately.
> 
> Thanks!
> 
> Jose
> 
> _______________________________________________
> 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  Wed Jul  3 03:44:37 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 ED32721F9A23 for <tcmtf@ietfa.amsl.com>; Wed,  3 Jul 2013 03:44:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 BODHEXG1qMez for <tcmtf@ietfa.amsl.com>; Wed,  3 Jul 2013 03:44:32 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 22C3021F8C38 for <tcmtf@ietf.org>; Wed,  3 Jul 2013 03:44:31 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r63AiLjW025708 for <tcmtf@ietf.org>; Wed, 3 Jul 2013 12:44:27 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
In-Reply-To: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
Date: Wed, 3 Jul 2013 12:44:25 +0200
Organization: Universidad de Zaragoza
Message-ID: <005301ce77da$4c8da450$e5a8ecf0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0054_01CE77EB.101737A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHxl5HfJe4XxEPJrqhURPk2/vEH5pkBgHlw
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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: Wed, 03 Jul 2013 10:44:38 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0054_01CE77EB.101737A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Question 5: Is there a significant amount of traffic of services based on
small packets? Is it interesting to compress it? Why?

 

Answer (some ideas):

 

Although the vast majority of Internet traffic corresponds to big packets
(file transfers, video downloads), this best-effort traffic does not present
tight delay requirements.

 

However, many of the services using small packets have stringent delay
requirements, so the network has to deliver them faster. And this share of
the traffic is really critical for network operators: if I wait 5 seconds to
watch a video, it is not a problem. However, if my VoIP call or my online
game have a latency of 100ms, it can be a serious problem.

 

In addition, some of these small-packet services are present on certain
network segments where bandwidth may be scarce (residential access,
aggregation networks, satellite links), or a pps limit exists. In the
context of mobile networks:

 

- New VoIP services are using data links instead of establishing traditional
voice calls (e.g., viber)

- Online games are being played with tablets and smartphones:
<http://www.juniperresearch.com/viewpressrelease.php?id=534&pr=364>
http://www.juniperresearch.com/viewpressrelease.php?id=534&pr=364

- Internet of Things: many "things" will send small packets with a certain
frequency

- New traffic patterns: "Major changes in traffic characteristics are the
increases in small packets, short connections, signaling and data traffic,
and abnormal traffic. For Universal Mobile Telecommunications System (UTMS)
networks in idle status, all these changes lead to sharp increases on
signaling and other system resource load. They also bring severe threat on
network performance, and affect application data throughput capability and
network profitability in the long run." (Huawei Smartphone Solutions White
Paper).

 

The mobility of the users has some other implications: The network may
experience a "traffic rush" in certain places or moments (e.g., a sports
event, the World release of a new game), so TCM-TF would provide a certain
degree of flexibility (a tradeoff): I don't have to over-dimension my
network. When a traffic rush is detected, I can get advantage of this
tradeoff, compressing traffic up to 50 or 60%, at the cost of a small added
latency. The service would work a bit more slowly, but it would at least
work.

 

In addition, if I only "awake" TCM-TF optimization when I have a lot of
traffic, then I will add a really tiny latency, since I will have lots of
packets to multiplex, and in 5ms I may be able to create an MTU-sized
multiplexed packet.

 

Any other ideas?

 

Jose

 

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de Jose
Saldana
Enviado el: lunes, 24 de junio de 2013 13:00
Para: tcmtf@ietf.org
Asunto: [tcmtf] Answers to possible questions in the BOF

 

I would like to start a thread about possible questions people may ask in
the BOF. Obviously, we also need answers, so we should cooperate.

 

This is different from the "questions to ask in the BOF". This will be
discussed separately.

 

Thanks!

 

Jose

 


------=_NextPart_000_0054_01CE77EB.101737A0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texto de globo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.EstiloCorreo17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.TextodegloboCar
	{mso-style-name:"Texto de globo Car";
	mso-style-priority:99;
	mso-style-link:"Texto de globo";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Question 5: Is there a significant =
amount of traffic of services based on small packets? Is it interesting =
to compress it? Why?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Answer =
(some ideas):<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Although =
the vast majority of Internet traffic corresponds to big packets (file =
transfers, video downloads), this best-effort traffic does not present =
tight delay requirements.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>However, =
many of the services using small packets have stringent delay =
requirements, so the network has to deliver them faster. And this share =
of the traffic is really critical for network operators: if I wait 5 =
seconds to watch a video, it is not a problem. However, if my VoIP call =
or my online game have a latency of 100ms, it can be a serious =
problem.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>In =
addition, some of these small-packet services are present on certain =
network segments where bandwidth may be scarce (residential access, =
aggregation networks, satellite links), or a pps limit exists. In the =
context of mobile networks:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- New VoIP =
services are using data links instead of establishing traditional voice =
calls (e.g., viber)<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>- Online games are being played =
with tablets and smartphones: </span><a =
href=3D"http://www.juniperresearch.com/viewpressrelease.php?id=3D534&amp;=
pr=3D364"><span =
lang=3DEN-US>http://www.juniperresearch.com/viewpressrelease.php?id=3D534=
&amp;pr=3D364</span></a><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>- Internet of Things: many =
&#8220;things&#8221; will send small packets with a certain =
frequency<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>- New traffic patterns: &#8220;Major changes in =
traffic characteristics are the increases in small packets, short =
connections, signaling and data traffic, and abnormal traffic. For =
Universal Mobile Telecommunications System (UTMS) networks in idle =
status, all these changes lead to sharp increases on signaling and other =
system resource load. They also bring severe threat on network =
performance, and affect application data throughput capability and =
network profitability in the long run.&#8221; (Huawei Smartphone =
Solutions White Paper).<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>The =
mobility of the users has some other implications: The network may =
experience a &#8220;traffic rush&#8221; in certain places or moments =
(e.g., a sports event, the World release of a new game), so TCM-TF would =
provide a certain degree of flexibility (a tradeoff): I don&#8217;t have =
to over-dimension my network. When a traffic rush is detected, I can get =
advantage of this tradeoff, compressing traffic up to 50 or 60%, at the =
cost of a small added latency. The service would work a bit more slowly, =
but it would at least work.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>In =
addition, if I only &#8220;awake&#8221; TCM-TF optimization when I have =
a lot of traffic, then I will add a really tiny latency, since I will =
have lots of packets to multiplex, and in 5ms I may be able to create an =
MTU-sized multiplexed packet.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Any other =
ideas?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'>De:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'> <a =
href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a =
href=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]=
 <b>En nombre de </b>Jose Saldana<br><b>Enviado el:</b> lunes, 24 de =
junio de 2013 13:00<br><b>Para:</b> <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><b>Asunto:</b> =
[tcmtf] Answers to possible questions in the =
BOF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>I would like to start a thread about possible questions =
people may ask in the BOF. Obviously, we also need answers, so we should =
cooperate.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This is different from the &#8220;questions to ask in the =
BOF&#8221;. This will be discussed separately.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Thanks!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:ES'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_0054_01CE77EB.101737A0--


From mramalho@cisco.com  Wed Jul  3 05:41:41 2013
Return-Path: <mramalho@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 0C46B11E819F for <tcmtf@ietfa.amsl.com>; Wed,  3 Jul 2013 05:41:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 a+9z2WIgTJMZ for <tcmtf@ietfa.amsl.com>; Wed,  3 Jul 2013 05:41:35 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id A0F2711E819B for <tcmtf@ietf.org>; Wed,  3 Jul 2013 05:41:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17250; q=dns/txt; s=iport; t=1372855295; x=1374064895; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=+c7t/jud9B9unOfvhCUF7CUWq3/xlEABvN2+3NsAbVw=; b=LXG0NfCOIDf3HwX9wIjdSDPkuVX+SQDflIcILhMGhxKujlVRcUHmMJaX 8tGQa0ihClYl8Z1LUQqIB17l2S5/o1yDPnir06EzLFrJotgUrLEgolvPW 1Cn8xSFBdrNBLCJnm7DdnBUwT+9r5abdpILXxCsHljLM1UxvaEP7Di19S A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMFAAEb1FGtJV2Y/2dsb2JhbABAGoJFRDJJwDKBAhZ0giMBAQEELVwCAQgRBAEBCx0HMhQJCAEBBAEJCQgTh3QMM7o6jjSBBjcBgwRpA6kOgxF6XhE/
X-IronPort-AV: E=Sophos;i="4.87,988,1363132800";  d="scan'208,217";a="230458617"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP; 03 Jul 2013 12:41:34 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r63CfY1P006193 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Jul 2013 12:41:34 GMT
Received: from xmb-rcd-x12.cisco.com ([169.254.2.54]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Wed, 3 Jul 2013 07:41:34 -0500
From: "Michael Ramalho (mramalho)" <mramalho@cisco.com>
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] Answers to possible questions in the BOF
Thread-Index: Ac5wycGHbApylKz/RhmtAnL3dgONFwHOnA2AAAeOkVA=
Date: Wed, 3 Jul 2013 12:41:34 +0000
Message-ID: <D21571530BF9644D9A443D6BD95B91031558E484@xmb-rcd-x12.cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <005301ce77da$4c8da450$e5a8ecf0$@unizar.es>
In-Reply-To: <005301ce77da$4c8da450$e5a8ecf0$@unizar.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.125.234]
Content-Type: multipart/alternative; boundary="_000_D21571530BF9644D9A443D6BD95B91031558E484xmbrcdx12ciscoc_"
MIME-Version: 1.0
Subject: Re: [tcmtf] Answers to possible questions in 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: Wed, 03 Jul 2013 12:41:41 -0000

--_000_D21571530BF9644D9A443D6BD95B91031558E484xmbrcdx12ciscoc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Jose .. you say:

"I don't have to over-dimension my network. When a traffic rush is detected=
, I can get advantage of this tradeoff, compressing traffic up to 50 or 60%=
, at the cost of a small added latency. The service would work a bit more s=
lowly, but it would at least work."

You may have actually over-stated the cost. For such a rush, many of the ht=
tp sessions during "the rush" would stall (go into slow-start). For that su=
bset you may have prevented the stall! Thus while most of the sessions may =
incur the cost of "small added latency" (of ~40ms or less), some of the ses=
sions avoided stalling entirely!

I hate it when a web page tries to fetch 100 things ... and the http get of=
 ONE of those things stalls ... and prevents me from using site as intended=
. Preventing stalls is a good thing.

Also on the "traffic rush" issue ... TCMTF can be used dynamically to lesse=
n bufferbloat (effectively lowering the amount of buffer used on highly buf=
fered links) on a particular egress link. That is, if you see your egress b=
uffer growing, you might try to compress traffic toward it when you can. Th=
at could even lessen the delay for all users at such a sports event (lots o=
f small packets representing updates to game statistics).

Michael Ramalho

From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of J=
ose Saldana
Sent: Wednesday, July 03, 2013 6:44 AM
To: tcmtf@ietf.org
Subject: Re: [tcmtf] Answers to possible questions in the BOF

Question 5: Is there a significant amount of traffic of services based on s=
mall packets? Is it interesting to compress it? Why?

Answer (some ideas):

Although the vast majority of Internet traffic corresponds to big packets (=
file transfers, video downloads), this best-effort traffic does not present=
 tight delay requirements.

However, many of the services using small packets have stringent delay requ=
irements, so the network has to deliver them faster. And this share of the =
traffic is really critical for network operators: if I wait 5 seconds to wa=
tch a video, it is not a problem. However, if my VoIP call or my online gam=
e have a latency of 100ms, it can be a serious problem.

In addition, some of these small-packet services are present on certain net=
work segments where bandwidth may be scarce (residential access, aggregatio=
n networks, satellite links), or a pps limit exists. In the context of mobi=
le networks:

- New VoIP services are using data links instead of establishing traditiona=
l voice calls (e.g., viber)
- Online games are being played with tablets and smartphones: http://www.ju=
niperresearch.com/viewpressrelease.php?id=3D534&pr=3D364
- Internet of Things: many "things" will send small packets with a certain =
frequency
- New traffic patterns: "Major changes in traffic characteristics are the i=
ncreases in small packets, short connections, signaling and data traffic, a=
nd abnormal traffic. For Universal Mobile Telecommunications System (UTMS) =
networks in idle status, all these changes lead to sharp increases on signa=
ling and other system resource load. They also bring severe threat on netwo=
rk performance, and affect application data throughput capability and netwo=
rk profitability in the long run." (Huawei Smartphone Solutions White Paper=
).

The mobility of the users has some other implications: The network may expe=
rience a "traffic rush" in certain places or moments (e.g., a sports event,=
 the World release of a new game), so TCM-TF would provide a certain degree=
 of flexibility (a tradeoff): I don't have to over-dimension my network. Wh=
en a traffic rush is detected, I can get advantage of this tradeoff, compre=
ssing traffic up to 50 or 60%, at the cost of a small added latency. The se=
rvice would work a bit more slowly, but it would at least work.

In addition, if I only "awake" TCM-TF optimization when I have a lot of tra=
ffic, then I will add a really tiny latency, since I will have lots of pack=
ets to multiplex, and in 5ms I may be able to create an MTU-sized multiplex=
ed packet.

Any other ideas?

Jose

De: tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-bou=
nces@ietf.org] En nombre de Jose Saldana
Enviado el: lunes, 24 de junio de 2013 13:00
Para: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: [tcmtf] Answers to possible questions in the BOF

I would like to start a thread about possible questions people may ask in t=
he BOF. Obviously, we also need answers, so we should cooperate.

This is different from the "questions to ask in the BOF". This will be disc=
ussed separately.

Thanks!

Jose


--_000_D21571530BF9644D9A443D6BD95B91031558E484xmbrcdx12ciscoc_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
p.Textodeglobo, li.Textodeglobo, div.Textodeglobo
	{mso-style-name:"Texto de globo";
	mso-style-link:"Texto de globo Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.TextodegloboCar
	{mso-style-name:"Texto de globo Car";
	mso-style-priority:99;
	mso-style-link:"Texto de globo";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:70.85pt 85.05pt 70.85pt 85.05pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jose .. you say: <o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&#8220;</span><span st=
yle=3D"color:#1F497D">I don&#8217;t have to over-dimension my network. When=
 a traffic rush is detected, I can get advantage of this tradeoff, compress=
ing traffic up to 50 or 60%, at the cost of a small
 added latency. The service would work a bit more slowly, but it would at l=
east work.</span><span style=3D"color:#1F497D">&#8221;<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">You may have actually =
over-stated the cost. For such a rush, many of the http sessions during &#8=
220;the rush&#8221; would stall (go into slow-start). For that subset you m=
ay have prevented the stall! Thus while most of
 the sessions may incur the cost of &#8220;small added latency&#8221; (of ~=
40ms or less), some of the sessions avoided stalling entirely!<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I hate it when a web p=
age tries to fetch 100 things &#8230; and the http get of ONE of those thin=
gs stalls &#8230; and prevents me from using site as intended. Preventing s=
talls is a good thing.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Also on the &#8220;tra=
ffic rush&#8221; issue &#8230; TCMTF can be used dynamically to lessen buff=
erbloat (effectively lowering the amount of buffer used on highly buffered =
links) on a particular egress link. That is, if you see
 your egress buffer growing, you might try to compress traffic toward it wh=
en you can. That could even lessen the delay for all users at such a sports=
 event (lots of small packets representing updates to game statistics).<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Michael Ramalho</span>=
<span style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tcmtf-bo=
unces@ietf.org [mailto:tcmtf-bounces@ietf.org]
<b>On Behalf Of </b>Jose Saldana<br>
<b>Sent:</b> Wednesday, July 03, 2013 6:44 AM<br>
<b>To:</b> tcmtf@ietf.org<br>
<b>Subject:</b> Re: [tcmtf] Answers to possible questions in the BOF<o:p></=
o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Question 5: Is there a=
 significant amount of traffic of services based on small packets? Is it in=
teresting to compress it? Why?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Answer (some ideas):<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Although the vast majo=
rity of Internet traffic corresponds to big packets (file transfers, video =
downloads), this best-effort traffic does not present tight delay requireme=
nts.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">However, many of the s=
ervices using small packets have stringent delay requirements, so the netwo=
rk has to deliver them faster. And this share of the traffic is really crit=
ical for network operators: if I wait
 5 seconds to watch a video, it is not a problem. However, if my VoIP call =
or my online game have a latency of 100ms, it can be a serious problem.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In addition, some of t=
hese small-packet services are present on certain network segments where ba=
ndwidth may be scarce (residential access, aggregation networks, satellite =
links), or a pps limit exists. In the
 context of mobile networks:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- New VoIP services ar=
e using data links instead of establishing traditional voice calls (e.g., v=
iber)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- Online games are bei=
ng played with tablets and smartphones:
</span><span lang=3D"ES"><a href=3D"http://www.juniperresearch.com/viewpres=
srelease.php?id=3D534&amp;pr=3D364"><span lang=3D"EN-US">http://www.juniper=
research.com/viewpressrelease.php?id=3D534&amp;pr=3D364</span></a></span><s=
pan style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- Internet of Things: =
many &#8220;things&#8221; will send small packets with a certain frequency<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- New traffic patterns=
: &#8220;Major changes in traffic characteristics are the increases in smal=
l packets, short connections, signaling and data traffic, and abnormal traf=
fic. For Universal Mobile Telecommunications
 System (UTMS) networks in idle status, all these changes lead to sharp inc=
reases on signaling and other system resource load. They also bring severe =
threat on network performance, and affect application data throughput capab=
ility and network profitability
 in the long run.&#8221; (Huawei Smartphone Solutions White Paper).<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The mobility of the us=
ers has some other implications: The network may experience a &#8220;traffi=
c rush&#8221; in certain places or moments (e.g., a sports event, the World=
 release of a new game), so TCM-TF would provide
 a certain degree of flexibility (a tradeoff): I don&#8217;t have to over-d=
imension my network. When a traffic rush is detected, I can get advantage o=
f this tradeoff, compressing traffic up to 50 or 60%, at the cost of a smal=
l added latency. The service would work
 a bit more slowly, but it would at least work.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In addition, if I only=
 &#8220;awake&#8221; TCM-TF optimization when I have a lot of traffic, then=
 I will add a really tiny latency, since I will have lots of packets to mul=
tiplex, and in 5ms I may be able to create an MTU-sized
 multiplexed packet.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Any other ideas?<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jose<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"ES" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ES">D=
e:</span></b><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;=
Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ES">
<a href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a hr=
ef=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]
<b>En nombre de </b>Jose Saldana<br>
<b>Enviado el:</b> lunes, 24 de junio de 2013 13:00<br>
<b>Para:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tcmtf] Answers to possible questions in the BOF<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">I would like to start a thread about possible questi=
ons people may ask in the BOF. Obviously, we also need answers, so we shoul=
d cooperate.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is different from the &#8220;questions to ask i=
n the BOF&#8221;. This will be discussed separately.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks!<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"mso-fareast-language:ES">Jose<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_D21571530BF9644D9A443D6BD95B91031558E484xmbrcdx12ciscoc_--

From jsaldana@unizar.es  Wed Jul  3 07:29:57 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 E8CFC11E81AF for <tcmtf@ietfa.amsl.com>; Wed,  3 Jul 2013 07:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 wI3yiz67AZ5r for <tcmtf@ietfa.amsl.com>; Wed,  3 Jul 2013 07:29:53 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 9569D11E80BA for <tcmtf@ietf.org>; Wed,  3 Jul 2013 07:29:52 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r63ETgVf030708; Wed, 3 Jul 2013 16:29:43 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Michael Ramalho \(mramalho\)'" <mramalho@cisco.com>, <tcmtf@ietf.org>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <005301ce77da$4c8da450$e5a8ecf0$@unizar.es> <D21571530BF9644D9A443D6BD95B91031558E484@xmb-rcd-x12.cisco.com>
In-Reply-To: <D21571530BF9644D9A443D6BD95B91031558E484@xmb-rcd-x12.cisco.com>
Date: Wed, 3 Jul 2013 16:29:47 +0200
Organization: Universidad de Zaragoza
Message-ID: <002701ce77f9$c54d42a0$4fe7c7e0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0028_01CE780A.88D77230"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHxl5HfJe4XxEPJrqhURPk2/vEH5gHqKaBOAZ+pGkuY8HD4gA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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: Wed, 03 Jul 2013 14:29:58 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0028_01CE780A.88D77230
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

You are right, Michael.

=20

Sometimes you can prevent the stall. For example, in the release of a =
new
online game, you can predict that everybody will be waiting in front of =
the
computer at 0:00 AM in order to be the first ones playing: see what =
happened
some months ago when =93Diablo III=94 was released (the =93launch-day =
crash=94):

=20
<http://www.nbcnews.com/technology/blizzard-apologizes-diablo-disaster-77=
807
2>
http://www.nbcnews.com/technology/blizzard-apologizes-diablo-disaster-778=
072

=20

But other times you cannot predict it. For example, think about the =
amount
of whatsapp messages sent whenever a soccer team scores a goal.

=20

So I think we should definitely think about dynamically using TCM-TF,
integrating different ways for detecting congestion and traffic rushes. =
In
fact, this is already included in the draft charter, but only as a
possibility for re-chartering, once TCM-TF is well defined (number 9
<http://www.ietf.org/mail-archive/web/tcmtf/current/msg00286.html>
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00286.html):

=20

=93dynamically applying TCMTF: a higher entity in charge of deciding =
when and
where, applying or not=20

TCMTF, and what kind of TCMTF, and what multiplexing period. Additional
methods for estimating delay=20

would also be required.=94

=20

Thanks!

=20

Jose

=20

De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com]=20
Enviado el: mi=E9rcoles, 03 de julio de 2013 14:42
Para: jsaldana@unizar.es; tcmtf@ietf.org
Asunto: RE: [tcmtf] Answers to possible questions in the BOF

=20

Jose .. you say:=20

=20

=93I don=92t have to over-dimension my network. When a traffic rush is =
detected,
I can get advantage of this tradeoff, compressing traffic up to 50 or =
60%,
at the cost of a small added latency. The service would work a bit more
slowly, but it would at least work.=94

=20

You may have actually over-stated the cost. For such a rush, many of the
http sessions during =93the rush=94 would stall (go into slow-start). =
For that
subset you may have prevented the stall! Thus while most of the sessions =
may
incur the cost of =93small added latency=94 (of ~40ms or less), some of =
the
sessions avoided stalling entirely!

=20

I hate it when a web page tries to fetch 100 things =85 and the http get =
of
ONE of those things stalls =85 and prevents me from using site as =
intended.
Preventing stalls is a good thing.

=20

Also on the =93traffic rush=94 issue =85 TCMTF can be used dynamically =
to lessen
bufferbloat (effectively lowering the amount of buffer used on highly
buffered links) on a particular egress link. That is, if you see your =
egress
buffer growing, you might try to compress traffic toward it when you =
can.
That could even lessen the delay for all users at such a sports event =
(lots
of small packets representing updates to game statistics).

=20

Michael Ramalho

=20

From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =
Of
Jose Saldana
Sent: Wednesday, July 03, 2013 6:44 AM
To: tcmtf@ietf.org
Subject: Re: [tcmtf] Answers to possible questions in the BOF

=20

Question 5: Is there a significant amount of traffic of services based =
on
small packets? Is it interesting to compress it? Why?

=20

Answer (some ideas):

=20

Although the vast majority of Internet traffic corresponds to big =
packets
(file transfers, video downloads), this best-effort traffic does not =
present
tight delay requirements.

=20

However, many of the services using small packets have stringent delay
requirements, so the network has to deliver them faster. And this share =
of
the traffic is really critical for network operators: if I wait 5 =
seconds to
watch a video, it is not a problem. However, if my VoIP call or my =
online
game have a latency of 100ms, it can be a serious problem.

=20

In addition, some of these small-packet services are present on certain
network segments where bandwidth may be scarce (residential access,
aggregation networks, satellite links), or a pps limit exists. In the
context of mobile networks:

=20

- New VoIP services are using data links instead of establishing =
traditional
voice calls (e.g., viber)

- Online games are being played with tablets and smartphones:
<http://www.juniperresearch.com/viewpressrelease.php?id=3D534&pr=3D364>
http://www.juniperresearch.com/viewpressrelease.php?id=3D534&pr=3D364

- Internet of Things: many =93things=94 will send small packets with a =
certain
frequency

- New traffic patterns: =93Major changes in traffic characteristics are =
the
increases in small packets, short connections, signaling and data =
traffic,
and abnormal traffic. For Universal Mobile Telecommunications System =
(UTMS)
networks in idle status, all these changes lead to sharp increases on
signaling and other system resource load. They also bring severe threat =
on
network performance, and affect application data throughput capability =
and
network profitability in the long run.=94 (Huawei Smartphone Solutions =
White
Paper).

=20

The mobility of the users has some other implications: The network may
experience a =93traffic rush=94 in certain places or moments (e.g., a =
sports
event, the World release of a new game), so TCM-TF would provide a =
certain
degree of flexibility (a tradeoff): I don=92t have to over-dimension my
network. When a traffic rush is detected, I can get advantage of this
tradeoff, compressing traffic up to 50 or 60%, at the cost of a small =
added
latency. The service would work a bit more slowly, but it would at least
work.

=20

In addition, if I only =93awake=94 TCM-TF optimization when I have a lot =
of
traffic, then I will add a really tiny latency, since I will have lots =
of
packets to multiplex, and in 5ms I may be able to create an MTU-sized
multiplexed packet.

=20

Any other ideas?

=20

Jose

=20

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de =
Jose
Saldana
Enviado el: lunes, 24 de junio de 2013 13:00
Para: tcmtf@ietf.org
Asunto: [tcmtf] Answers to possible questions in the BOF

=20

I would like to start a thread about possible questions people may ask =
in
the BOF. Obviously, we also need answers, so we should cooperate.

=20

This is different from the =93questions to ask in the BOF=94. This will =
be
discussed separately.

=20

Thanks!

=20

Jose

=20


------=_NextPart_000_0028_01CE780A.88D77230
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texto de globo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.TextodegloboCar
	{mso-style-name:"Texto de globo Car";
	mso-style-priority:99;
	mso-style-link:"Texto de globo";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EstiloCorreo21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EstiloCorreo23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EstiloCorreo24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>You are right, =
Michael.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Sometimes =
you can prevent the stall. For example, in the release of a new online =
game, you can predict that everybody will be waiting in front of the =
computer at 0:00 AM in order to be the first ones playing: see what =
happened some months ago when &#8220;Diablo III&#8221; was released (the =
&#8220;launch-day crash&#8221;):<o:p></o:p></span></p><p =
class=3DMsoNormal><a =
href=3D"http://www.nbcnews.com/technology/blizzard-apologizes-diablo-disa=
ster-778072"><span =
lang=3DEN-US>http://www.nbcnews.com/technology/blizzard-apologizes-diablo=
-disaster-778072</span></a><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>But other =
times you cannot predict it. For example, think about the amount of =
whatsapp messages sent whenever a soccer team scores a =
goal.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>So I think =
we should definitely think about dynamically using TCM-TF, integrating =
different ways for detecting congestion and traffic rushes. In fact, =
this is already included in the draft charter, but only as a possibility =
for re-chartering, once TCM-TF is well defined (number 9 </span><a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00286.html"=
><span lang=3DEN-US =
style=3D'font-size:11.5pt;color:#440088;background:white'>http://www.ietf=
.org/mail-archive/web/tcmtf/current/msg00286.html</span></a><span =
lang=3DEN-US style=3D'color:#1F497D'>):<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>&#8220;dynamically applying TCMTF: a higher =
entity in charge of deciding when and where, applying or not =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>TCMTF, and what kind of TCMTF, and what =
multiplexing period. Additional methods for estimating delay =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>would also be =
required.&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Thanks!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Michael =
Ramalho (mramalho) [mailto:mramalho@cisco.com] =
<br><b>Envia</b></span><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>do =
el:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
mi=E9rcoles, 03 de julio de 2013 14:42<br><b>Para:</b> =
jsaldana@unizar.es; tcmtf@ietf.org<br><b>Asunto:</b> RE: [tcmtf] Answers =
to possible questions in the BOF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Jose .. you say: =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>&#8220;I =
don&#8217;t have to over-dimension my network. When a traffic rush is =
detected, I can get advantage of this tradeoff, compressing traffic up =
to 50 or 60%, at the cost of a small added latency. The service would =
work a bit more slowly, but it would at least =
work.&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>You may =
have actually over-stated the cost. For such a rush, many of the http =
sessions during &#8220;the rush&#8221; would stall (go into slow-start). =
For that subset you may have prevented the stall! Thus while most of the =
sessions may incur the cost of &#8220;small added latency&#8221; (of =
~40ms or less), some of the sessions avoided stalling =
entirely!<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>I hate it =
when a web page tries to fetch 100 things &#8230; and the http get of =
ONE of those things stalls &#8230; and prevents me from using site as =
intended. Preventing stalls is a good thing.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Also on the =
&#8220;traffic rush&#8221; issue &#8230; TCMTF can be used dynamically =
to lessen bufferbloat (effectively lowering the amount of buffer used on =
highly buffered links) on a particular egress link. That is, if you see =
your egress buffer growing, you might try to compress traffic toward it =
when you can. That could even lessen the delay for all users at such a =
sports event (lots of small packets representing updates to game =
statistics).<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Michael =
Ramalho<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a =
href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a =
href=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]=
 <b>On Behalf Of </b>Jose Saldana<br><b>Sent:</b> Wednesday, July 03, =
2013 6:44 AM<br><b>To:</b> <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><b>Subject:</b> Re: =
[tcmtf] Answers to possible questions in the =
BOF<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Question 5: Is there a significant =
amount of traffic of services based on small packets? Is it interesting =
to compress it? Why?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Answer =
(some ideas):<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Although =
the vast majority of Internet traffic corresponds to big packets (file =
transfers, video downloads), this best-effort traffic does not present =
tight delay requirements.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>However, =
many of the services using small packets have stringent delay =
requirements, so the network has to deliver them faster. And this share =
of the traffic is really critical for network operators: if I wait 5 =
seconds to watch a video, it is not a problem. However, if my VoIP call =
or my online game have a latency of 100ms, it can be a serious =
problem.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>In =
addition, some of these small-packet services are present on certain =
network segments where bandwidth may be scarce (residential access, =
aggregation networks, satellite links), or a pps limit exists. In the =
context of mobile networks:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- New VoIP =
services are using data links instead of establishing traditional voice =
calls (e.g., viber)<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>- Online games are being played =
with tablets and smartphones: </span><a =
href=3D"http://www.juniperresearch.com/viewpressrelease.php?id=3D534&amp;=
pr=3D364"><span =
lang=3DEN-US>http://www.juniperresearch.com/viewpressrelease.php?id=3D534=
&amp;pr=3D364</span></a><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>- Internet of Things: many =
&#8220;things&#8221; will send small packets with a certain =
frequency<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>- New traffic patterns: &#8220;Major changes in =
traffic characteristics are the increases in small packets, short =
connections, signaling and data traffic, and abnormal traffic. For =
Universal Mobile Telecommunications System (UTMS) networks in idle =
status, all these changes lead to sharp increases on signaling and other =
system resource load. They also bring severe threat on network =
performance, and affect application data throughput capability and =
network profitability in the long run.&#8221; (Huawei Smartphone =
Solutions White Paper).<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>The =
mobility of the users has some other implications: The network may =
experience a &#8220;traffic rush&#8221; in certain places or moments =
(e.g., a sports event, the World release of a new game), so TCM-TF would =
provide a certain degree of flexibility (a tradeoff): I don&#8217;t have =
to over-dimension my network. When a traffic rush is detected, I can get =
advantage of this tradeoff, compressing traffic up to 50 or 60%, at the =
cost of a small added latency. The service would work a bit more slowly, =
but it would at least work.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>In =
addition, if I only &#8220;awake&#8221; TCM-TF optimization when I have =
a lot of traffic, then I will add a really tiny latency, since I will =
have lots of packets to multiplex, and in 5ms I may be able to create an =
MTU-sized multiplexed packet.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Any other =
ideas?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a =
href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a =
href=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]=
 <b>En nombre de </b>Jose Saldana<br><b>Enviado el:</b> lunes, 24 de =
junio de 2013 13:00<br><b>Para:</b> <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><b>Asunto:</b> =
[tcmtf] Answers to possible questions in the =
BOF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>I would like to start a thread about possible questions =
people may ask in the BOF. Obviously, we also need answers, so we should =
cooperate.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This is different from the &#8220;questions to ask in the =
BOF&#8221;. This will be discussed separately.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Thanks!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></div></div></body></html>
------=_NextPart_000_0028_01CE780A.88D77230--


From jsaldana@unizar.es  Wed Jul  3 08:58: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 2879011E81C8 for <tcmtf@ietfa.amsl.com>; Wed,  3 Jul 2013 08:58:45 -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=[AWL=0.000,  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 aS-vOP30LT5d for <tcmtf@ietfa.amsl.com>; Wed,  3 Jul 2013 08:58:41 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 048C711E81D2 for <tcmtf@ietf.org>; Wed,  3 Jul 2013 08:58:36 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r63FwSrx013950; Wed, 3 Jul 2013 17:58:28 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'jsalazar'" <jsalazar@unizar.es>, <tcmtf@ietf.org>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>	<009901ce725a$d1623360$74269a20$@unizar.es>	<2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>	<20130628105725.lmag0xgqsgogggww@webmail.unizar.es>	<EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com> <95d1a818ab88cf76070677949afba188@unizar.es>
In-Reply-To: <95d1a818ab88cf76070677949afba188@unizar.es>
Date: Wed, 3 Jul 2013 17:58:31 +0200
Organization: Universidad de Zaragoza
Message-ID: <007101ce7806$2d215860$87640920$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHxl5HfJe4XxEPJrqhURPk2/vEH5gJG8kQSAT8jBAUB238Z4AIljoQ2AbET9qCYwxNQwA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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: Wed, 03 Jul 2013 15:58:45 -0000

Hi, Jose Luis. Good point.

Regarding security, we could establish this classification:

1- Adding security to TCM: I have a number of non-secured flows =
traveling through a =E2=80=9Cdangerous=E2=80=9D network segment (perhaps =
a tunnel between appliances connecting remote offices of a company), and =
I want not only traffic optimization but also security. In this case, I =
can simply use IPsec on the tunnel.


2- Using TCM for optimizing already secured communications: I have a =
bunch of already secured flows. Which is the best way for tunneling, =
compressing and multiplexing them?

Two subcases:

2a- I can use TCM normally, but not only compress IP, TCP or UDP =
headers, but also security headers using a header compression method. =
Some possibilities for compressing security headers:

- ROHCoIPsec, RFC5856 (http://tools.ietf.org/html/rfc5856)
- RFC5225 http://tools.ietf.org/html/rfc5225


2b- But I can save more bandwidth if the TCM-ingress optimizer (TCM-IO) =
is able to:
- rebuild the packets to their native form
- TCM-optimize them=20
- put them into a single security tunnel

I have three phases (let's suppose I have 20 communications):

Origin 1
Origin 2     <----20 secured flows --------> TCM-IO <------1 =
tunnel------> TCM-EO <-------- 20 secured flows----> destination 1, 2, =
20
...
Origin 20

I have an advantage: In the shared network path, I use a single tunnel =
instead of 20 different tunnels.

But I have some additional requirements: I need processing capacity in =
the TCM optimizers, and the endpoints should trust them.


Is this classification correct? Any other options? Any other =
requirements? It is time for "security experts".

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> jsalazar
> Enviado el: lunes, 01 de julio de 2013 20:50
> Para: tcmtf@ietf.org
> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>=20
> Hi all:
> Mmmmmmm. Since I see tcm-tf as a service, I can design the service =
with
> added security features that the type of communication is requiring. I =
think
> we have to be clear what we are expressing when we are talking about
> secure tcm-tf: Ensuring the service tcm-tf or applying the tcm-tf =
service for
> secure communications.
> The first possibility is not a great technological sophistication and =
the second
> one might consider the first one as a possible additional service. =
Therefore,
> every time we use the term "secure tcm-tf" should think the second =
option,
> for generality.
> On the other hand, we must also keep in mind that whenever users =
employ
> secure tcm-tf, they must trust the service fully and consider =
delegating the
> use of their keys (including private ones) to tcm-tf.
>=20
> Regards.
>=20
> JL
>=20
> "I see them falling out the skies like eagles
> All mirrored glass and shattered egos"
>=20
> Simple Minds.
>=20
> El 2013-07-01 18:55, Dan Wing escribi=C3=B3:
> > On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
> >
> > Hi all,
> >
> > Few days ago Julian talked about TCM-TF's security and now I've read =
in
> > the link included by Dan, saying that the gain obtained when
> > multiplexing Ipsec-encrypted packets is 20-to-1. We have been =
looking
> > for more information about this issue and thinking about a way to
> > reduce the needed  bandwidth in IPsec flows.
> >
> > The main idea is to find a way to change the authentication of the
> > individual packets and merge all of them in a unique authentication.
> > Thus, instead of using 20 IPsec tunnels, we would have a single =
tunnel
> > including 20 flows. Is this something similar than how Cisco gets =
the
> > improvement?
> >
> > We would not be able to change IPsec any more than we could change
> > TCP, so I would not look at how to change IPsec authentication.
> >
> > However, if there are a bunch of IPsec packets sharing a common =
path,
> > I could see them being successfully multiplexed into one larger =
packet
> > at one tunnel endpoint and then de-multiplexed at the other tunnel
> > endpoint.  This can provide a packet per second reduction.  I don't
> > think there are enough bytes in an IPsec header to bother trying to =
do
> > IPsec header compression (SPI and sequence number are only 64 bits).
> >
> > -d
> >
> >
> >
> > Jos=C3=A9 Luis
> >
> >
> >
> > Dan Wing <dwing@cisco.com> ha escrito:
> >
> >
> > On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> =
wrote:
> >
> > Question 4: Is TCM-TF interesting for the Industry? Should the IETF
> > standardize this?
> >
> > Answer:
> >
> > 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP  =
traffic.
> > So if RFC4170 was interesting, why not updating it?
> >
> > 2) TCM-TF can be useful in order to save bandwidth in many cases:
> >
> > - Aggregation network of *network operators*: We are saving  =
bandwidth
> > by optimizing and putting together traffic flows. Is this  =
interesting
> > for a network operator? What about overprovisioning?  The idea is =
that
> > there are places and moments in which a number of  flows based on =
small
> > packets are in the same place and at the same  moment. Then, TCM-TF =
can
> > be applied in order to provide  flexibility. We are not optimizing =
the
> > overall Internet traffic, we  are optimizing specific flows with =
very
> > tight delay requirements,  which network operators have to take care =
of
> > in a special way.
> > www.huawei.com/ilink/en/download/HW_193034
> >
> > - *End to end* optimization: Nowadays, many appliances are used to
> > connect remote offices of the same company (creating a VPN). So if  =
a
> > tunnel exists, why not optimizing this traffic when possible? We  =
would
> > save bandwidth in the access network, where it can be scarce.
> >
> > - Wireless and satellite scenarios.
> >
> > "Cisco adds IP multiplexing to mobile satellite package", April  =
2012,
> > http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing-
> 258082.html
> >
> >
> >
> >
> >
> > Any other thoughts? Any other scenarios in mind? Potential
> > beneficiaries?
> >
> > Some networks, today, use cRTP (RFC2508) on their access links.   =
This
> > gives bandwidth savings on the access link, but consumes  =
considerable
> > CPU horsepower on the aggregation router (to perform  cRTP), but
> > provides no bandwidth savings across the network core.   If, =
instead,
> > the bandwidth could be saved on the access link, across  the core, =
and
> > on the far-end access link -- all without the CPU  impact on the
> > aggregation router -- it is a considerable win.
> >
> > -d
> >
> >
> >
> >
> >
> > Jose
> >
> > De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En  =
nombre
> > de Jose Saldana
> > Enviado el: lunes, 24 de junio de 2013 13:00
> > Para: tcmtf@ietf.org
> > Asunto: [tcmtf] Answers to possible questions in the BOF
> >
> > I would like to start a thread about possible questions people may  =
ask
> > in the BOF. Obviously, we also need answers, so we should  =
cooperate.
> >
> > This is different from the "questions to ask in the BOF". This will  =
be
> > discussed separately.
> >
> > Thanks!
> >
> > Jose
> >
> > _______________________________________________
> > 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


From mperumal@cisco.com  Wed Jul  3 11:51:31 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 8251311E8200 for <tcmtf@ietfa.amsl.com>; Wed,  3 Jul 2013 11:51:31 -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 5D0bygytM6KG for <tcmtf@ietfa.amsl.com>; Wed,  3 Jul 2013 11:51:27 -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 CCD5111E8212 for <tcmtf@ietf.org>; Wed,  3 Jul 2013 11:51:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5488; q=dns/txt; s=iport; t=1372877483; x=1374087083; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hffOJ/GackoyP31lQTmisXoxleeBG/CBnsiERMlUDoI=; b=Kru9CivGk62I+gNRVJ4f7IiphWiAZm1JFdZgw8lLqHhPfzkwCjJkq17g Vhj55ymNOid7XivOgpHAVaMpNXbVrtz2l5RwWZHe1QbSbFZB/WiNWdjj9 0XaxF1N5lzTzLHtJJZgHxFOHy88wt21ehT1A++GgiwDo2yvNI1euNa9Uw o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMFADJy1FGtJV2a/2dsb2JhbABagwkyScA3gQYWdIIjAQEBBAEBAUYjAggDDAQCAQgRBAEBCx0HJwsUCQgCBAENBQgSBIdxDLojjh6BHDEHBoJ+aQOIa4sMlReDEYIo
X-IronPort-AV: E=Sophos;i="4.87,989,1363132800"; d="scan'208";a="227704080"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-9.cisco.com with ESMTP; 03 Jul 2013 18:51:01 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r63Ip1b5015160 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Jul 2013 18:51:01 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.192]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Wed, 3 Jul 2013 13:51:00 -0500
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: "Dan Wing (dwing)" <dwing@cisco.com>, "jltornos@unizar.es" <jltornos@unizar.es>
Thread-Topic: [tcmtf] Answers to possible questions in the BOF
Thread-Index: AQHOdnvPX00XDi64+EGJAr2DWa8S1ZlTTKXA
Date: Wed, 3 Jul 2013 18:51:00 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE22417E050@xmb-rcd-x02.cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com> <20130628105725.lmag0xgqsgogggww@webmail.unizar.es> <EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com>
In-Reply-To: <EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.78.169]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Subject: Re: [tcmtf] Answers to possible questions in 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: Wed, 03 Jul 2013 18:51:31 -0000

|However, if there are a bunch of IPsec packets sharing a common path,=20
|I could see them being successfully multiplexed into one larger packet=20
|at one tunnel endpoint and then de-multiplexed at the other tunnel endpoin=
t. =20
|This can provide a packet per second reduction.  I don't think there are
|enough bytes in an IPsec header to bother trying to do IPsec header=20
|compression (SPI and sequence number are only 64 bits).

Actually, RFC5856 describes how ROHC can be used over IPSec (ROHCoIPsec). C=
ombining it with multiplexing the entire packets could provide significant =
reduction in the header overhead, especially for IPv6, I think.

Muthu

|-----Original Message-----
|From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of =
Dan Wing (dwing)
|Sent: Monday, July 01, 2013 10:25 PM
|To: jltornos@unizar.es
|Cc: tcmtf@ietf.org; jsaldana@unizar.es
|Subject: Re: [tcmtf] Answers to possible questions in the BOF
|
|
|On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
|
|> Hi all,
|>
|> Few days ago Julian talked about TCM-TF's security and now I've read in =
the link included by Dan,
|saying that the gain obtained when multiplexing Ipsec-encrypted packets is=
 20-to-1. We have been
|looking for more information about this issue and thinking about a way to =
reduce the needed  bandwidth
|in IPsec flows.
|>
|> The main idea is to find a way to change the authentication of the indiv=
idual packets and merge all
|of them in a unique authentication. Thus, instead of using 20 IPsec tunnel=
s, we would have a single
|tunnel including 20 flows. Is this something similar than how Cisco gets t=
he improvement?
|
|We would not be able to change IPsec any more than we could change TCP, so=
 I would not look at how to
|change IPsec authentication.
|
|However, if there are a bunch of IPsec packets sharing a common path, I co=
uld see them being
|successfully multiplexed into one larger packet at one tunnel endpoint and=
 then de-multiplexed at the
|other tunnel endpoint.  This can provide a packet per second reduction.  I=
 don't think there are
|enough bytes in an IPsec header to bother trying to do IPsec header compre=
ssion (SPI and sequence
|number are only 64 bits).
|
|-d
|
|
|>
|> Jos=E9 Luis
|>
|>
|>
|> Dan Wing <dwing@cisco.com> ha escrito:
|>
|>>
|>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> wrote:
|>>
|>>> Question 4: Is TCM-TF interesting for the Industry? Should the IETF  s=
tandardize this?
|>>>
|>>> Answer:
|>>>
|>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP  traffic=
. So if RFC4170 was
|interesting, why not updating it?
|>>>
|>>> 2) TCM-TF can be useful in order to save bandwidth in many cases:
|>>>
|>>> - Aggregation network of *network operators*: We are saving  bandwidth=
 by optimizing and putting
|together traffic flows. Is this  interesting for a network operator? What =
about overprovisioning?  The
|idea is that there are places and moments in which a number of  flows base=
d on small packets are in
|the same place and at the same  moment. Then, TCM-TF can be applied in ord=
er to provide  flexibility.
|We are not optimizing the overall Internet traffic, we  are optimizing spe=
cific flows with very tight
|delay requirements,  which network operators have to take care of in a spe=
cial way.
|>>> www.huawei.com/ilink/en/download/HW_193034
|>>>
|>>> - *End to end* optimization: Nowadays, many appliances are used to  co=
nnect remote offices of the
|same company (creating a VPN). So if  a tunnel exists, why not optimizing =
this traffic when possible?
|We  would save bandwidth in the access network, where it can be scarce.
|>>>
|>>> - Wireless and satellite scenarios.
|>>
|>> "Cisco adds IP multiplexing to mobile satellite package", April  2012,
|http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing-258082.=
html
|>>
|>>
|>>
|>>>
|>>>
|>>> Any other thoughts? Any other scenarios in mind? Potential beneficiari=
es?
|>>
|>> Some networks, today, use cRTP (RFC2508) on their access links.   This =
gives bandwidth savings on
|the access link, but consumes  considerable CPU horsepower on the aggregat=
ion router (to perform
|cRTP), but provides no bandwidth savings across the network core.   If, in=
stead, the bandwidth could
|be saved on the access link, across  the core, and on the far-end access l=
ink -- all without the CPU
|impact on the aggregation router -- it is a considerable win.
|>>
|>> -d
|>>
|>>
|>>
|>>>
|>>>
|>>> Jose
|>>>
|>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En  nombre =
de Jose Saldana
|>>> Enviado el: lunes, 24 de junio de 2013 13:00
|>>> Para: tcmtf@ietf.org
|>>> Asunto: [tcmtf] Answers to possible questions in the BOF
|>>>
|>>> I would like to start a thread about possible questions people may  as=
k in the BOF. Obviously, we
|also need answers, so we should  cooperate.
|>>>
|>>> This is different from the "questions to ask in the BOF". This will  b=
e discussed separately.
|>>>
|>>> Thanks!
|>>>
|>>> Jose
|>>>
|>>> _______________________________________________
|>>> 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 dwing@cisco.com  Wed Jul  3 11:55:59 2013
Return-Path: <dwing@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 19FB821F9BF5 for <tcmtf@ietfa.amsl.com>; Wed,  3 Jul 2013 11:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.46
X-Spam-Level: 
X-Spam-Status: No, score=-110.46 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 X98hFGiZBPFC for <tcmtf@ietfa.amsl.com>; Wed,  3 Jul 2013 11:55:55 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id BF21F11E81F9 for <tcmtf@ietf.org>; Wed,  3 Jul 2013 11:55:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6018; q=dns/txt; s=iport; t=1372877754; x=1374087354; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=q7Nk1zxR9Ditjn8HmtHA4RvxXAvgTVWlM+E5cUioRSI=; b=ctFHnLIuoTxU6Ro/juoOjO5XOgv9fMkLqvQutQdQjaNzTFKRorz+9FLj knAUx2FRUgcIpk/05WkJZycScqrWXfnFa0syKYz8r+UPnfTbDkhOt76de XbAm0HpZvbanfxrog0mSKiZCVvztF+WDvCHy0ZumzDZlHKCF1YLPG8olO Q=;
X-IronPort-AV: E=Sophos;i="4.87,989,1363132800"; d="scan'208";a="82638786"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 03 Jul 2013 18:55:46 +0000
Received: from sjc-vpn2-667.cisco.com (sjc-vpn2-667.cisco.com [10.21.114.155]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r63Ith3Q010750; Wed, 3 Jul 2013 18:55:43 GMT
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <E721D8C6A2E1544DB2DEBC313AF54DE22417E050@xmb-rcd-x02.cisco.com>
Date: Wed, 3 Jul 2013 11:55:43 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <23E6BFC1-4D3C-48A5-A9A2-3BD32863F9A6@cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com> <20130628105725.lmag0xgqsgogggww@webmail.unizar.es> <EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com> <E721D8C6A2E1544DB2DEBC313AF54DE22417E050@xmb-rcd-x02.cisco.com>
To: Muthu Arul Mozhi Perumal (mperumal) <mperumal@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, "jltornos@unizar.es" <jltornos@unizar.es>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Subject: Re: [tcmtf] Answers to possible questions in 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: Wed, 03 Jul 2013 18:55:59 -0000

On Jul 3, 2013, at 11:51 AM, Muthu Arul Mozhi Perumal (mperumal) =
<mperumal@cisco.com> wrote:

> |However, if there are a bunch of IPsec packets sharing a common path,=20=

> |I could see them being successfully multiplexed into one larger =
packet=20
> |at one tunnel endpoint and then de-multiplexed at the other tunnel =
endpoint. =20
> |This can provide a packet per second reduction.  I don't think there =
are
> |enough bytes in an IPsec header to bother trying to do IPsec header=20=

> |compression (SPI and sequence number are only 64 bits).
>=20
> Actually, RFC5856 describes how ROHC can be used over IPSec =
(ROHCoIPsec).

My read of it was:  apply ROHC at the endpoint ("inner headers") and =
then do IPsec.  That is, compress and then encrypt.

-d


> Combining it with multiplexing the entire packets could provide =
significant reduction in the header overhead, especially for IPv6, I =
think.
>=20
> Muthu
>=20
> |-----Original Message-----
> |From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On =
Behalf Of Dan Wing (dwing)
> |Sent: Monday, July 01, 2013 10:25 PM
> |To: jltornos@unizar.es
> |Cc: tcmtf@ietf.org; jsaldana@unizar.es
> |Subject: Re: [tcmtf] Answers to possible questions in the BOF
> |
> |
> |On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
> |
> |> Hi all,
> |>
> |> Few days ago Julian talked about TCM-TF's security and now I've =
read in the link included by Dan,
> |saying that the gain obtained when multiplexing Ipsec-encrypted =
packets is 20-to-1. We have been
> |looking for more information about this issue and thinking about a =
way to reduce the needed  bandwidth
> |in IPsec flows.
> |>
> |> The main idea is to find a way to change the authentication of the =
individual packets and merge all
> |of them in a unique authentication. Thus, instead of using 20 IPsec =
tunnels, we would have a single
> |tunnel including 20 flows. Is this something similar than how Cisco =
gets the improvement?
> |
> |We would not be able to change IPsec any more than we could change =
TCP, so I would not look at how to
> |change IPsec authentication.
> |
> |However, if there are a bunch of IPsec packets sharing a common path, =
I could see them being
> |successfully multiplexed into one larger packet at one tunnel =
endpoint and then de-multiplexed at the
> |other tunnel endpoint.  This can provide a packet per second =
reduction.  I don't think there are
> |enough bytes in an IPsec header to bother trying to do IPsec header =
compression (SPI and sequence
> |number are only 64 bits).
> |
> |-d
> |
> |
> |>
> |> Jos=E9 Luis
> |>
> |>
> |>
> |> Dan Wing <dwing@cisco.com> ha escrito:
> |>
> |>>
> |>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> =
wrote:
> |>>
> |>>> Question 4: Is TCM-TF interesting for the Industry? Should the =
IETF  standardize this?
> |>>>
> |>>> Answer:
> |>>>
> |>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP  =
traffic. So if RFC4170 was
> |interesting, why not updating it?
> |>>>
> |>>> 2) TCM-TF can be useful in order to save bandwidth in many cases:
> |>>>
> |>>> - Aggregation network of *network operators*: We are saving  =
bandwidth by optimizing and putting
> |together traffic flows. Is this  interesting for a network operator? =
What about overprovisioning?  The
> |idea is that there are places and moments in which a number of  flows =
based on small packets are in
> |the same place and at the same  moment. Then, TCM-TF can be applied =
in order to provide  flexibility.
> |We are not optimizing the overall Internet traffic, we  are =
optimizing specific flows with very tight
> |delay requirements,  which network operators have to take care of in =
a special way.
> |>>> www.huawei.com/ilink/en/download/HW_193034
> |>>>
> |>>> - *End to end* optimization: Nowadays, many appliances are used =
to  connect remote offices of the
> |same company (creating a VPN). So if  a tunnel exists, why not =
optimizing this traffic when possible?
> |We  would save bandwidth in the access network, where it can be =
scarce.
> |>>>
> |>>> - Wireless and satellite scenarios.
> |>>
> |>> "Cisco adds IP multiplexing to mobile satellite package", April  =
2012,
> =
|http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing-258082=
.html
> |>>
> |>>
> |>>
> |>>>
> |>>>
> |>>> Any other thoughts? Any other scenarios in mind? Potential =
beneficiaries?
> |>>
> |>> Some networks, today, use cRTP (RFC2508) on their access links.   =
This gives bandwidth savings on
> |the access link, but consumes  considerable CPU horsepower on the =
aggregation router (to perform
> |cRTP), but provides no bandwidth savings across the network core.   =
If, instead, the bandwidth could
> |be saved on the access link, across  the core, and on the far-end =
access link -- all without the CPU
> |impact on the aggregation router -- it is a considerable win.
> |>>
> |>> -d
> |>>
> |>>
> |>>
> |>>>
> |>>>
> |>>> Jose
> |>>>
> |>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En  =
nombre de Jose Saldana
> |>>> Enviado el: lunes, 24 de junio de 2013 13:00
> |>>> Para: tcmtf@ietf.org
> |>>> Asunto: [tcmtf] Answers to possible questions in the BOF
> |>>>
> |>>> I would like to start a thread about possible questions people =
may  ask in the BOF. Obviously, we
> |also need answers, so we should  cooperate.
> |>>>
> |>>> This is different from the "questions to ask in the BOF". This =
will  be discussed separately.
> |>>>
> |>>> Thanks!
> |>>>
> |>>> Jose
> |>>>
> |>>> _______________________________________________
> |>>> 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 fpb@tid.es  Thu Jul  4 01:12:00 2013
Return-Path: <fpb@tid.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 C66BE21F9F5F for <tcmtf@ietfa.amsl.com>; Thu,  4 Jul 2013 01:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.704
X-Spam-Level: 
X-Spam-Status: No, score=-5.704 tagged_above=-999 required=5 tests=[AWL=-0.894, BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 NirNzTJcIohf for <tcmtf@ietfa.amsl.com>; Thu,  4 Jul 2013 01:11:56 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5D98721F9F33 for <tcmtf@ietf.org>; Thu,  4 Jul 2013 01:11:53 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MPE006NDK3F8F@tid.hi.inet> for tcmtf@ietf.org; Thu, 04 Jul 2013 10:11:51 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 76.6C.03142.74E25D15; Thu, 04 Jul 2013 10:11:51 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MPE006OPK3R8F@tid.hi.inet> for tcmtf@ietf.org; Thu, 04 Jul 2013 10:11:51 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Thu, 04 Jul 2013 10:10:39 +0200
Date: Thu, 04 Jul 2013 08:11:48 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <51D1AA30.5080600@unizar.es>
X-Originating-IP: [10.95.64.115]
To: =?Windows-1252?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A29C8B8181@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_RN9pg9+bC5LXA3WNHX+Lng)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Where to talk about security
Thread-index: Ac5wrz13IWZxxTaCQH6g7L6OvBjX3AFs3v2AAACJ1QAAikxqgA==
user-agent: Microsoft-MacOutlook/14.3.5.130515
X-AuditID: 0a5f4068-b7f128e000000c46-90-51d52e47e6aa
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphkeLIzCtJLcpLzFFi42Lhinfg0nXXuxposPutrsWuzxsYHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVMePlZZaCrqCKu9O/MjcwfnXvYuTkkBAwkVix8QYjhC0mceHe erYuRi4OIYGNjBLvzr8ESwgJ/GCU6L7GC5GYxihxe+YmoAQHB4uAqkTXeVWQGjYBLYnTd1ex gNjCAoYSrXf+sIHYnAKaEr/fHINaoCDx59xjsBoRgRyJiVNfgY3hFfCWONabBBLmFRCU+DH5 HlgJs0CuxLP/31ghbHGJ5tabYHFGAVmJd/Pns0KMMZKYOWEHlO0k0fusC8wWFdCTOLznNSvE WgGJJXvOM0PYohIvH/9jncAoOgvJullI1s1Csg7CNpB4f24+M4StLbFs4WsoW19i45ezjBC2 mcTHBUvZkdUsYORYxShWnFSUmZ5RkpuYmZNuYKiXkamXmZdasokREnMZOxiX71Q5xCjAwajE wythdSVQiDWxrLgy9xCjBAezkgivE8fVQCHelMTKqtSi/Pii0pzU4kOMTBycUg2MLp8+PdxR IF7icCtyAteimvAdT1cGdfxO7//kbPzn3fF4gfX7CxxrE1Lfz5RyjLaV3b/t5gKeWBPp/Mod 6QxCLKl/vTYl85x/yDlxUedBm233GlsT1jq/V3wizRonIuO9QnH+7dtni2b6tWgyBC4wtNrs 6Kbmf6BwVXmr+8c1J/f3MLALZ1kpsRRnJBpqMRcVJwIAUiEDWpcCAAA=
Subject: Re: [tcmtf] Where to talk about security
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, 04 Jul 2013 08:12:00 -0000

--Boundary_(ID_RN9pg9+bC5LXA3WNHX+Lng)
Content-type: text/plain; charset=Windows-1252
Content-transfer-encoding: quoted-printable

Hi Juli=E1n,

Absolutely.

Regards,

Fernando Pascual Blanco
Telef=F3nica Global Resources
Network Automation and Dynamization
TECHNOLOGY PEOPLE GROUP
F +34913128779
M +34682005168
fpb@tid.es

From: Juli=E1n Fern=E1ndez Navajas <navajas@unizar.es<mailto:navajas@unizar=
.es>>
Date: lunes, 1 de julio de 2013 18:11
To: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Subject: Re: [tcmtf] Where to talk about security

Hi all,
I think not only in tunnel mode but also in transport mode.
In transport mode is possible to achieve improved efficiency by using TCMTF=
. In tunnel mode, the aim would be to substitute this by TCMTF and achieve =
improved more efficiency.
Best regards
Juli=E1n


El 01/07/2013 15:54, FERNANDO PASCUAL BLANCO escribi=F3:
Hi Jose,

Yes, I agree with you. IPSec (in tunnel mode) could be included as another =
tunneling protocol adding the security capability to the whole TCM protocol=
.

Best,

Fernando Pascual Blanco
Telef=F3nica Global Resources
Network Automation and Dynamization
TECHNOLOGY PEOPLE GROUP
F +34913128779
M +34682005168
fpb@tid.es<mailto:fpb@tid.es>

From: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.es<m=
ailto:jsaldana@unizar.es>>
Organization: Universidad de Zaragoza
Reply-To: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.=
es<mailto:jsaldana@unizar.es>>
Date: lunes, 1 de julio de 2013 13:26
To: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Subject: [tcmtf] Where to talk about security

Hi all.

In the =93TCM-TF reference model=94 (https://datatracker.ietf.org/doc/draft=
-saldana-tsvwg-tcmtf/) we say nothing in the =93security=94 section. I am p=
reparing an updated version.

We could perhaps talk about the use of security tunnels (perhaps IPSEC) as =
the most straightforward solution for providing end-to-end security to the =
optimized tunnel. What do you think?

Jose


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx



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


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

--Boundary_(ID_RN9pg9+bC5LXA3WNHX+Lng)
Content-id: <74E47E095ACDB44C82B539C5D5AF292B@hi.inet>
Content-type: text/html; charset=Windows-1252
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font=
-family:Calibri,sans-serif">
<div>
<div>
<div>Hi Juli=E1n,</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Absolu=
tely.</div>
<div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Fernando Pascual Blanco</div>
<div>Telef=F3nica Global Resources</div>
<div>Network Automation and Dynamization</div>
<div>TECHNOLOGY PEOPLE GROUP</div>
<div>F &#43;34913128779</div>
<div>M &#43;34682005168</div>
<div>fpb@tid.es</div>
</div>
</div>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; border-bottom:medium none; border-left:medium none; padding-bottom:0i=
n; padding-left:0in; padding-right:0in; border-top:#b5c4df 1pt solid; borde=
r-right:medium none; padding-top:3pt">
<span style=3D"font-weight:bold">From: </span>Juli=E1n Fern=E1ndez Navajas =
&lt;<a href=3D"mailto:navajas@unizar.es">navajas@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>lunes, 1 de julio de 2013 18:=
11<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:tcmtf@i=
etf.org">tcmtf@ietf.org</a>&quot; &lt;<a href=3D"mailto:tcmtf@ietf.org">tcm=
tf@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [tcmtf] Where to talk =
about security<br>
</div>
<div><br>
</div>
<div>
<div bgcolor=3D"#FFFFFF">
<div class=3D"moz-cite-prefix">Hi all,<br>
I think not only in tunnel mode but also in transport mode.<br>
In transport mode is possible to achieve improved efficiency by using TCMTF=
. In tunnel mode, the aim would be to substitute this by TCMTF and achieve =
improved more efficiency.<br>
Best regards<br>
Juli=E1n<br>
<br>
<br>
El 01/07/2013 15:54, FERNANDO PASCUAL BLANCO escribi=F3:<br>
</div>
<blockquote type=3D"cite">
<div>
<div>
<div>Hi Jose,</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Yes, I=
 agree with you. IPSec (in tunnel mode) could be included as another tunnel=
ing protocol adding the security capability to the whole TCM protocol.</div=
>
<div>
<div><br>
</div>
<div>Best,</div>
<div><br>
</div>
<div>Fernando Pascual Blanco</div>
<div>Telef=F3nica Global Resources</div>
<div>Network Automation and Dynamization</div>
<div>TECHNOLOGY PEOPLE GROUP</div>
<div>F &#43;34913128779</div>
<div>M &#43;34682005168</div>
<div><a class=3D"moz-txt-link-abbreviated" href=3D"mailto:fpb@tid.es">fpb@t=
id.es</a></div>
</div>
</div>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; border-bottom:medium none; border-left:medium none; padding-bottom:0i=
n; padding-left:0in; padding-right:0in; border-top:#b5c4df 1pt solid; borde=
r-right:medium none; padding-top:3pt">
<span style=3D"font-weight:bold">From: </span>&quot;<a href=3D"mailto:jsald=
ana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsaldana@=
unizar.es">jsaldana@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Organization: </span>Universidad de Zarago=
za<br>
<span style=3D"font-weight:bold">Reply-To: </span>&quot;<a href=3D"mailto:j=
saldana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsald=
ana@unizar.es">jsaldana@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>lunes, 1 de julio de 2013 13:=
26<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:tcmtf@i=
etf.org">tcmtf@ietf.org</a>&quot; &lt;<a href=3D"mailto:tcmtf@ietf.org">tcm=
tf@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[tcmtf] Where to talk abou=
t security<br>
</div>
<div><br>
</div>
<div><style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
span.EstiloCorreo17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
.MsoChpDefault
	{font-size:10.0pt;
	font-family:"Calibri","sans-serif"}
@page WordSection1
	{margin:70.85pt 3.0cm 70.85pt 3.0cm}
-->
</style>
<div lang=3D"ES">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi all.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">In the =93TCM-TF reference mode=
l=94 (</span><a href=3D"https://datatracker.ietf.org/doc/draft-saldana-tsvw=
g-tcmtf/"><span lang=3D"EN-US">https://datatracker.ietf.org/doc/draft-salda=
na-tsvwg-tcmtf/</span></a><span lang=3D"EN-US">)
 we say nothing in the =93security=94 section. I am preparing an updated ve=
rsion.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We could perhaps talk about the=
 use of security tunnels (perhaps IPSEC) as the most straightforward soluti=
on for providing end-to-end security to the optimized tunnel. What do you t=
hink?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"">Jose </span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
</div>
</div>
</span><br>
<hr>
<font color=3D"Gray" face=3D"Arial" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a class=3D"moz-txt-link-freetext" href=3D"http://www.tid.es/ES/PAGINAS/dis=
claimer.aspx">http://www.tid.es/ES/PAGINAS/disclaimer.aspx</a><br>
</font><br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset> <br>
<pre>_______________________________________________
tcmtf mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:tcmtf@ietf.org">tcmtf@=
ietf.org</a><a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org=
/mailman/listinfo/tcmtf">https://www.ietf.org/mailman/listinfo/tcmtf</a></p=
re>
</blockquote>
<br>
</div>
</div>
</span><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_RN9pg9+bC5LXA3WNHX+Lng)--

From mperumal@cisco.com  Thu Jul  4 06:41:55 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 8E73911E80E9 for <tcmtf@ietfa.amsl.com>; Thu,  4 Jul 2013 06:41:55 -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 3zXt9ZF71hex for <tcmtf@ietfa.amsl.com>; Thu,  4 Jul 2013 06:41:51 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 1279B21F9FE7 for <tcmtf@ietf.org>; Thu,  4 Jul 2013 06:41:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7431; q=dns/txt; s=iport; t=1372945311; x=1374154911; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=yKtJNk9qoIlo0FKDYxvq+NtUQMcRVlOSIhoPIk6Ll7o=; b=mIATDWNLnOAfNz0kdW0HJLeKyNaeCRquLJvUhFAIMOuaDmp8JodNcitu QZ2NZ2d9neBhB2/21ERmSHifWgF223In0jKm03bzpbOBZTU5fcGs4W4OZ M1u+fsLwPYYvLbIIn4PVJdl9T/5whhtIoQCkoF7quHHe9xTfA/AAl1niA 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAEp71VGtJXG8/2dsb2JhbABagwkyScA/gQMWdIIjAQEBBAEBASQiIwIIAwwEAgEIEQQBAQsdBycLFAkIAgQOBQgSBIdxDLoLjh6BHDEHBoJ+aQOIa4sMlReDEYIo
X-IronPort-AV: E=Sophos;i="4.87,995,1363132800"; d="scan'208";a="230957920"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-7.cisco.com with ESMTP; 04 Jul 2013 13:41:50 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r64DfoKb000407 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 4 Jul 2013 13:41:50 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.192]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Thu, 4 Jul 2013 08:41:49 -0500
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: "Dan Wing (dwing)" <dwing@cisco.com>
Thread-Topic: [tcmtf] Answers to possible questions in the BOF
Thread-Index: AQHOdnvPX00XDi64+EGJAr2DWa8S1ZlTTKXAgABYC4CAAFOdIA==
Date: Thu, 4 Jul 2013 13:41:49 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE22417FD51@xmb-rcd-x02.cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com> <20130628105725.lmag0xgqsgogggww@webmail.unizar.es> <EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com> <E721D8C6A2E1544DB2DEBC313AF54DE22417E050@xmb-rcd-x02.cisco.com> <23E6BFC1-4D3C-48A5-A9A2-3BD32863F9A6@cisco.com>
In-Reply-To: <23E6BFC1-4D3C-48A5-A9A2-3BD32863F9A6@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.48.23]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, "jltornos@unizar.es" <jltornos@unizar.es>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Subject: Re: [tcmtf] Answers to possible questions in 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: Thu, 04 Jul 2013 13:41:55 -0000

|My read of it was:  apply ROHC at the endpoint ("inner headers") and=20
|then do IPsec.  That is, compress and then encrypt.

Right, Dan. I was thinking the (inner) headers of the packets going over th=
e same IPSec tunnel could first be compressed, multiplex, then encrypted an=
d sent over that tunnel:

--------------------------------------------
|outer IP hdr| ESP | MUX | ROHCoIPsec|Data1|
|            |     | hdr |   hdr1    |     |
--------------------------------------------
                          ----------------------
                          | ROHCoIPsec | Data2 |
                          |    hdr2    |       |
                          ----------------------
                          -------------------------------------
                          | ROHCoIPsec |  Data3  | ESP   | ESP|
                          |    hdr3    |         |Trailer| ICV|
                          -------------------------------------
                    <-----------Encrypted-------->

Muthu

|-----Original Message-----
|From: Dan Wing (dwing)
|Sent: Thursday, July 04, 2013 12:26 AM
|To: Muthu Arul Mozhi Perumal (mperumal)
|Cc: jltornos@unizar.es; tcmtf@ietf.org; jsaldana@unizar.es
|Subject: Re: [tcmtf] Answers to possible questions in the BOF
|
|
|On Jul 3, 2013, at 11:51 AM, Muthu Arul Mozhi Perumal (mperumal) <mperumal=
@cisco.com> wrote:
|
|> |However, if there are a bunch of IPsec packets sharing a common path,
|> |I could see them being successfully multiplexed into one larger packet
|> |at one tunnel endpoint and then de-multiplexed at the other tunnel endp=
oint.
|> |This can provide a packet per second reduction.  I don't think there ar=
e
|> |enough bytes in an IPsec header to bother trying to do IPsec header
|> |compression (SPI and sequence number are only 64 bits).
|>
|> Actually, RFC5856 describes how ROHC can be used over IPSec (ROHCoIPsec)=
.
|
|My read of it was:  apply ROHC at the endpoint ("inner headers") and then =
do IPsec.  That is, compress
|and then encrypt.
|
|-d
|
|
|> Combining it with multiplexing the entire packets could provide signific=
ant reduction in the header
|overhead, especially for IPv6, I think.
|>
|> Muthu
|>
|> |-----Original Message-----
|> |From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =
Of Dan Wing (dwing)
|> |Sent: Monday, July 01, 2013 10:25 PM
|> |To: jltornos@unizar.es
|> |Cc: tcmtf@ietf.org; jsaldana@unizar.es
|> |Subject: Re: [tcmtf] Answers to possible questions in the BOF
|> |
|> |
|> |On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
|> |
|> |> Hi all,
|> |>
|> |> Few days ago Julian talked about TCM-TF's security and now I've read =
in the link included by Dan,
|> |saying that the gain obtained when multiplexing Ipsec-encrypted packets=
 is 20-to-1. We have been
|> |looking for more information about this issue and thinking about a way =
to reduce the needed
|bandwidth
|> |in IPsec flows.
|> |>
|> |> The main idea is to find a way to change the authentication of the in=
dividual packets and merge
|all
|> |of them in a unique authentication. Thus, instead of using 20 IPsec tun=
nels, we would have a single
|> |tunnel including 20 flows. Is this something similar than how Cisco get=
s the improvement?
|> |
|> |We would not be able to change IPsec any more than we could change TCP,=
 so I would not look at how
|to
|> |change IPsec authentication.
|> |
|> |However, if there are a bunch of IPsec packets sharing a common path, I=
 could see them being
|> |successfully multiplexed into one larger packet at one tunnel endpoint =
and then de-multiplexed at
|the
|> |other tunnel endpoint.  This can provide a packet per second reduction.=
  I don't think there are
|> |enough bytes in an IPsec header to bother trying to do IPsec header com=
pression (SPI and sequence
|> |number are only 64 bits).
|> |
|> |-d
|> |
|> |
|> |>
|> |> Jos=E9 Luis
|> |>
|> |>
|> |>
|> |> Dan Wing <dwing@cisco.com> ha escrito:
|> |>
|> |>>
|> |>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> wrote=
:
|> |>>
|> |>>> Question 4: Is TCM-TF interesting for the Industry? Should the IETF=
  standardize this?
|> |>>>
|> |>>> Answer:
|> |>>>
|> |>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP  traf=
fic. So if RFC4170 was
|> |interesting, why not updating it?
|> |>>>
|> |>>> 2) TCM-TF can be useful in order to save bandwidth in many cases:
|> |>>>
|> |>>> - Aggregation network of *network operators*: We are saving  bandwi=
dth by optimizing and
|putting
|> |together traffic flows. Is this  interesting for a network operator? Wh=
at about overprovisioning?
|The
|> |idea is that there are places and moments in which a number of  flows b=
ased on small packets are in
|> |the same place and at the same  moment. Then, TCM-TF can be applied in =
order to provide
|flexibility.
|> |We are not optimizing the overall Internet traffic, we  are optimizing =
specific flows with very
|tight
|> |delay requirements,  which network operators have to take care of in a =
special way.
|> |>>> www.huawei.com/ilink/en/download/HW_193034
|> |>>>
|> |>>> - *End to end* optimization: Nowadays, many appliances are used to =
 connect remote offices of
|the
|> |same company (creating a VPN). So if  a tunnel exists, why not optimizi=
ng this traffic when
|possible?
|> |We  would save bandwidth in the access network, where it can be scarce.
|> |>>>
|> |>>> - Wireless and satellite scenarios.
|> |>>
|> |>> "Cisco adds IP multiplexing to mobile satellite package", April  201=
2,
|> |http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing-2580=
82.html
|> |>>
|> |>>
|> |>>
|> |>>>
|> |>>>
|> |>>> Any other thoughts? Any other scenarios in mind? Potential benefici=
aries?
|> |>>
|> |>> Some networks, today, use cRTP (RFC2508) on their access links.   Th=
is gives bandwidth savings
|on
|> |the access link, but consumes  considerable CPU horsepower on the aggre=
gation router (to perform
|> |cRTP), but provides no bandwidth savings across the network core.   If,=
 instead, the bandwidth
|could
|> |be saved on the access link, across  the core, and on the far-end acces=
s link -- all without the
|CPU
|> |impact on the aggregation router -- it is a considerable win.
|> |>>
|> |>> -d
|> |>>
|> |>>
|> |>>
|> |>>>
|> |>>>
|> |>>> Jose
|> |>>>
|> |>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En  nomb=
re de Jose Saldana
|> |>>> Enviado el: lunes, 24 de junio de 2013 13:00
|> |>>> Para: tcmtf@ietf.org
|> |>>> Asunto: [tcmtf] Answers to possible questions in the BOF
|> |>>>
|> |>>> I would like to start a thread about possible questions people may =
 ask in the BOF. Obviously,
|we
|> |also need answers, so we should  cooperate.
|> |>>>
|> |>>> This is different from the "questions to ask in the BOF". This will=
  be discussed separately.
|> |>>>
|> |>>> Thanks!
|> |>>>
|> |>>> Jose
|> |>>>
|> |>>> _______________________________________________
|> |>>> 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  Thu Jul  4 08:49:40 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 DB98D21F9377 for <tcmtf@ietfa.amsl.com>; Thu,  4 Jul 2013 08:49:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.363
X-Spam-Level: 
X-Spam-Status: No, score=-6.363 tagged_above=-999 required=5 tests=[AWL=0.235,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 wpvc7T+KaF6g for <tcmtf@ietfa.amsl.com>; Thu,  4 Jul 2013 08:49:36 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 40F7821F92E3 for <tcmtf@ietf.org>; Thu,  4 Jul 2013 08:49:28 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r64FnMO1009429; Thu, 4 Jul 2013 17:49:22 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Thu, 4 Jul 2013 17:49:27 +0200
Organization: Universidad de Zaragoza
Message-ID: <001c01ce78ce$10ba6450$322f2cf0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001D_01CE78DE.D443F7A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac54yD46kc6esDuLRW2yf9vSBPgA9g==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: =?iso-8859-1?Q?Jos=E9_Ruiz_Mas?= <jruiz@unizar.es>
Subject: [tcmtf] TCM-TF and mobility
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 04 Jul 2013 15:49:41 -0000

This is a multipart message in MIME format.

------=_NextPart_000_001D_01CE78DE.D443F7A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all.

=20

We are discussing a lot about security and TCM-TF. Why not talking a bit
about TCM-TF and mobility?

=20

A) First question: How can user mobility and TCM-TF affect each other?

=20

1- Residential scenario: I am a network operator, and I am =
TCM-optimizing a
number of real-time (VoIP, online games) flows which are present in my
access network. What happens if one of the users moves to another =
location?
Is there any difference between the case in which the traffic is
TCM-optimized and the non-TCM case?

=20

In a first approach, I don=92t think so. TCM is applied in a network =
segment.
The end hosts may not even notice that TCM is being used. It would be =
seen
as an additional network delay and jitter. Thus, if the user moves and a
flow disappears, nothing happens to the rest of the flows. And regarding =
the
flow of the mobile user, it will be managed by the mobility protocol in =
the
same way.

=20

=20

2-Corporate environment: I am using two network appliances in order to
create a VPN between two offices of my company. There is a TCM session
between the two appliances, optimizing a number of VoIP calls. If a user
gets out of the office and his/her VoIP call moves to a 3G data =
connection,
what happens? Is there any difference with respect to the non-TCM case?

=20

I think the answer is the same as in 1.

=20

=20

3- Machine to machine scenario (sensors, industrial control): Does =
mobility
exist here? Any ideas?

=20

=20

B) Second question: Can any mobility protocol take advantage of TCM-TF?

=20

Just an idea (suggested by Jose Ruiz) regarding *PMIPv6* (RFC5213,
<http://tools.ietf.org/html/rfc5213> =
http://tools.ietf.org/html/rfc5213):

=20

This network-based mobility protocol creates a tunnel between the LMA
(similar to the HA in MIPv6) and the MAG (typically runs on the access
router).

=20

This *tunnel is shared by all the flows* between the LMA and the MAG:=20

=93the bidirectional tunnel between the LMA and MAG is typically a =
shared
tunnel, and can be employed for routing traffic streams for different =
MNs
attached to the same MAG. It extends the 1:1 relation between a tunnel =
and
an MN=92s binding cache entry to a 1:m relation, reflecting the shared =
nature
of the tunnel=94 [1]. The tunnel between LMA and MAG can be based on GRE =
or
IP-in-IP.

=20

So we have a tunnel shared by a number of flows. Why not optimizing that
traffic? Instead of a tunnel including lots of small packets, can we
multiplex them and compress headers? Are these bandwidth and pps =
reductions
interesting?

=20

=20

Thanks,

=20

Jose=20

=20

[1]  Ki-Sik Kong; Wonjun Lee; Youn-Hee Han; Myung-Ki Shin; HeungRyeol =
You,
"Mobility management for all-IP mobile networks: mobile IPv6 vs. proxy
mobile IPv6," Wireless Communications, IEEE , vol.15, no.2, pp.36,45, =
April
2008

http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D
<http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&arnumber=3D4492976&isnu=
mber=3D44
92967> &arnumber=3D4492976&isnumber=3D4492967

 <http://voiplab.niu.edu.tw/ppt/ipv6/R9843011.pdf>
http://voiplab.niu.edu.tw/ppt/ipv6/R9843011.pdf

=20

More info:

 <http://en.wikipedia.org/wiki/Proxy_Mobile_IPv6>
http://en.wikipedia.org/wiki/Proxy_Mobile_IPv6

http://www.cisco.com/en/US/docs/ios-xml/ios/mob_pmipv6/configuration/xe-3=
s/d
eployment/Proxy_Mobile_IPv6_Network-Based_Mobility.html


------=_NextPart_000_001D_01CE78DE.D443F7A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi =
all.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>We are discussing a lot about =
security and TCM-TF. Why not talking a bit about TCM-TF and =
mobility?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>A) First question: How can user mobility and TCM-TF affect =
each other?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>1- Residential scenario: I am a network operator, and I am =
TCM-optimizing a number of real-time (VoIP, online games) flows which =
are present in my access network. What happens if one of the users moves =
to another location? Is there any difference between the case in which =
the traffic is TCM-optimized and the non-TCM =
case?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>In a first approach, I don&#8217;t think so. TCM is applied =
in a network segment. The end hosts may not even notice that TCM is =
being used. It would be seen as an additional network delay and jitter. =
Thus, if the user moves and a flow disappears, nothing happens to the =
rest of the flows. And regarding the flow of the mobile user, it will be =
managed by the mobility protocol in the same =
way.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>2-Corporate environment: I am using two network appliances =
in order to create a VPN between two offices of my company. There is a =
TCM session between the two appliances, optimizing a number of VoIP =
calls. If a user gets out of the office and his/her VoIP call moves to a =
3G data connection, what happens? Is there any difference with respect =
to the non-TCM case?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>I think the answer is the same as in =
1.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>3- Machine to machine scenario (sensors, industrial =
control): Does mobility exist here? Any ideas?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>B) Second question: Can any =
mobility protocol take advantage of TCM-TF?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Just an idea (suggested by Jose =
Ruiz) regarding *<b>PMIPv6</b>* (RFC5213, </span><a =
href=3D"http://tools.ietf.org/html/rfc5213"><span =
lang=3DEN-US>http://tools.ietf.org/html/rfc5213</span></a><span =
lang=3DEN-US>):<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This network-based mobility protocol creates a tunnel =
between the LMA (similar to the HA in MIPv6) and the MAG (typically runs =
on the access router).<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This *<b>tunnel is shared by all the flows</b>* between the =
LMA and the MAG: <o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>&#8220;the bidirectional tunnel between the LMA and MAG is =
typically a shared tunnel, and can be employed for routing traffic =
streams for different MNs attached to the same MAG. It extends the 1:1 =
relation between a tunnel and an MN&#8217;s binding cache entry to a 1:m =
relation, reflecting the shared nature of the tunnel&#8221; [1]. The =
tunnel between LMA and MAG can be based on GRE or =
IP-in-IP.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>So we have a tunnel shared by a number of flows. Why not =
optimizing that traffic? Instead of a tunnel including lots of small =
packets, can we multiplex them and compress headers? Are these bandwidth =
and pps reductions interesting?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:ES'>Jose <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:ES'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:ES'>[1] =A0Ki-Sik Kong; Wonjun Lee; =
Youn-Hee Han; Myung-Ki Shin; HeungRyeol You, &quot;Mobility management =
for all-IP mobile networks: mobile IPv6 vs. proxy mobile IPv6,&quot; =
Wireless Communications, IEEE , vol.15, no.2, pp.36,45, April =
2008<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:ES'><a =
href=3D"http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&amp;arnumber=3D4=
492976&amp;isnumber=3D4492967">http://ieeexplore.ieee.org/stamp/stamp.jsp=
?tp=3D&amp;arnumber=3D4492976&amp;isnumber=3D4492967</a><o:p></o:p></span=
></p><p class=3DMsoNormal><a =
href=3D"http://voiplab.niu.edu.tw/ppt/ipv6/R9843011.pdf"><span =
lang=3DEN-US>http://voiplab.niu.edu.tw/ppt/ipv6/R9843011.pdf</span></a><s=
pan lang=3DEN-US =
style=3D'mso-fareast-language:ES'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>More info:<o:p></o:p></span></p><p =
class=3DMsoNormal><a =
href=3D"http://en.wikipedia.org/wiki/Proxy_Mobile_IPv6"><span =
lang=3DEN-US>http://en.wikipedia.org/wiki/Proxy_Mobile_IPv6</span></a><o:=
p></o:p></p><p class=3DMsoNormal><a =
href=3D"http://www.cisco.com/en/US/docs/ios-xml/ios/mob_pmipv6/configurat=
ion/xe-3s/deployment/Proxy_Mobile_IPv6_Network-Based_Mobility.html">http:=
//www.cisco.com/en/US/docs/ios-xml/ios/mob_pmipv6/configuration/xe-3s/dep=
loyment/Proxy_Mobile_IPv6_Network-Based_Mobility.html</a><o:p></o:p></p><=
/div></body></html>
------=_NextPart_000_001D_01CE78DE.D443F7A0--


From jsalazar@unizar.es  Thu Jul  4 10:58:40 2013
Return-Path: <jsalazar@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 A141121F9F30 for <tcmtf@ietfa.amsl.com>; Thu,  4 Jul 2013 10:58:40 -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 lnRzrTYllXaK for <tcmtf@ietfa.amsl.com>; Thu,  4 Jul 2013 10:58:36 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 0506921F9F37 for <tcmtf@ietf.org>; Thu,  4 Jul 2013 10:58:35 -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 r64HwPmS026483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Thu, 4 Jul 2013 19:58:29 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Date: Thu, 04 Jul 2013 19:58:30 +0200
From: jsalazar <jsalazar@unizar.es>
To: tcmtf@ietf.org
Message-ID: <dcb1afd6eef8ceedb8c7d2c1add3c8cd@unizar.es>
X-Sender: jsalazar@unizar.es
User-Agent: Roundcube Webmail/0.8.5
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] Fwd: RE:  Answers to possible questions in 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: Thu, 04 Jul 2013 17:58:40 -0000

-------- Mensaje original --------
Asunto: RE: [tcmtf] Answers to possible questions in the BOF
Fecha: 2013-07-04 19:35
Remitente: jsalazar <jsalazar@unizar.es>
Destinatario: jsaldana@unizar.es

Hi all.
With your last question, you have just hit the bullseye. I think the 
classification is correct. Cases 1 and 2a are a good way to keep the 
compromise between security and efficency. However, case 2b gives a step 
beyond and the security is compromised in the interest of efficiency.
In that case, users have to trust in tcmtf manager for managing their 
privacy also. Then, we will leave the tipical Public Key Infraestructure 
(PKI) security architecture and use the Identity Based Encryption (IBE) 
one (http://tools.ietf.org/html/rfc5408).
They are three different scenarios and all of them seem to be very 
interesting, but the last one a bit more.
Regards:

JL

"I see them falling out the skies like eagles
All mirrored glass and shattered egos"

Simple Minds.

El 2013-07-03 17:58, Jose Saldana escribiÃ³:
> Hi, Jose Luis. Good point.
> 
> Regarding security, we could establish this classification:
> 
> 1- Adding security to TCM: I have a number of non-secured flows
> traveling through a â€œdangerousâ€� network segment (perhaps a tunnel
> between appliances connecting remote offices of a company), and I want
> not only traffic optimization but also security. In this case, I can
> simply use IPsec on the tunnel.
> 
> 
> 2- Using TCM for optimizing already secured communications: I have a
> bunch of already secured flows. Which is the best way for tunneling,
> compressing and multiplexing them?
> 
> Two subcases:
> 
> 2a- I can use TCM normally, but not only compress IP, TCP or UDP
> headers, but also security headers using a header compression method.
> Some possibilities for compressing security headers:
> 
> - ROHCoIPsec, RFC5856 (http://tools.ietf.org/html/rfc5856)
> - RFC5225 http://tools.ietf.org/html/rfc5225
> 
> 
> 2b- But I can save more bandwidth if the TCM-ingress optimizer
> (TCM-IO) is able to:
> - rebuild the packets to their native form
> - TCM-optimize them
> - put them into a single security tunnel
> 
> I have three phases (let's suppose I have 20 communications):
> 
> Origin 1
> Origin 2     <----20 secured flows --------> TCM-IO <------1
> tunnel------> TCM-EO <-------- 20 secured flows----> destination 1, 2,
> 20
> ...
> Origin 20
> 
> I have an advantage: In the shared network path, I use a single tunnel
> instead of 20 different tunnels.
> 
> But I have some additional requirements: I need processing capacity in
> the TCM optimizers, and the endpoints should trust them.
> 
> 
> Is this classification correct? Any other options? Any other
> requirements? It is time for "security experts".
> 
> Jose
> 
> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
> jsalazar
> Enviado el: lunes, 01 de julio de 2013 20:50
> Para: tcmtf@ietf.org
> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
> 
> Hi all:
> Mmmmmmm. Since I see tcm-tf as a service, I can design the service with
> added security features that the type of communication is requiring. I 
> think
> we have to be clear what we are expressing when we are talking about
> secure tcm-tf: Ensuring the service tcm-tf or applying the tcm-tf 
> service for
> secure communications.
> The first possibility is not a great technological sophistication and 
> the second
> one might consider the first one as a possible additional service. 
> Therefore,
> every time we use the term "secure tcm-tf" should think the second 
> option,
> for generality.
> On the other hand, we must also keep in mind that whenever users employ
> secure tcm-tf, they must trust the service fully and consider 
> delegating the
> use of their keys (including private ones) to tcm-tf.
> 
> Regards.
> 
> JL
> 
> "I see them falling out the skies like eagles
> All mirrored glass and shattered egos"
> 
> Simple Minds.
> 
> El 2013-07-01 18:55, Dan Wing escribiÃ³:
> > On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
> >
> > Hi all,
> >
> > Few days ago Julian talked about TCM-TF's security and now I've read in
> > the link included by Dan, saying that the gain obtained when
> > multiplexing Ipsec-encrypted packets is 20-to-1. We have been looking
> > for more information about this issue and thinking about a way to
> > reduce the needed  bandwidth in IPsec flows.
> >
> > The main idea is to find a way to change the authentication of the
> > individual packets and merge all of them in a unique authentication.
> > Thus, instead of using 20 IPsec tunnels, we would have a single tunnel
> > including 20 flows. Is this something similar than how Cisco gets the
> > improvement?
> >
> > We would not be able to change IPsec any more than we could change
> > TCP, so I would not look at how to change IPsec authentication.
> >
> > However, if there are a bunch of IPsec packets sharing a common path,
> > I could see them being successfully multiplexed into one larger packet
> > at one tunnel endpoint and then de-multiplexed at the other tunnel
> > endpoint.  This can provide a packet per second reduction.  I don't
> > think there are enough bytes in an IPsec header to bother trying to do
> > IPsec header compression (SPI and sequence number are only 64 bits).
> >
> > -d
> >
> >
> >
> > JosÃ© Luis
> >
> >
> >
> > Dan Wing <dwing@cisco.com> ha escrito:
> >
> >
> > On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> wrote:
> >
> > Question 4: Is TCM-TF interesting for the Industry? Should the IETF
> > standardize this?
> >
> > Answer:
> >
> > 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP  traffic.
> > So if RFC4170 was interesting, why not updating it?
> >
> > 2) TCM-TF can be useful in order to save bandwidth in many cases:
> >
> > - Aggregation network of *network operators*: We are saving  bandwidth
> > by optimizing and putting together traffic flows. Is this  interesting
> > for a network operator? What about overprovisioning?  The idea is that
> > there are places and moments in which a number of  flows based on small
> > packets are in the same place and at the same  moment. Then, TCM-TF can
> > be applied in order to provide  flexibility. We are not optimizing the
> > overall Internet traffic, we  are optimizing specific flows with very
> > tight delay requirements,  which network operators have to take care of
> > in a special way.
> > www.huawei.com/ilink/en/download/HW_193034
> >
> > - *End to end* optimization: Nowadays, many appliances are used to
> > connect remote offices of the same company (creating a VPN). So if  a
> > tunnel exists, why not optimizing this traffic when possible? We  would
> > save bandwidth in the access network, where it can be scarce.
> >
> > - Wireless and satellite scenarios.
> >
> > "Cisco adds IP multiplexing to mobile satellite package", April  2012,
> > http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing-
> 258082.html
> >
> >
> >
> >
> >
> > Any other thoughts? Any other scenarios in mind? Potential
> > beneficiaries?
> >
> > Some networks, today, use cRTP (RFC2508) on their access links.   This
> > gives bandwidth savings on the access link, but consumes  considerable
> > CPU horsepower on the aggregation router (to perform  cRTP), but
> > provides no bandwidth savings across the network core.   If, instead,
> > the bandwidth could be saved on the access link, across  the core, and
> > on the far-end access link -- all without the CPU  impact on the
> > aggregation router -- it is a considerable win.
> >
> > -d
> >
> >
> >
> >
> >
> > Jose
> >
> > De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En  nombre
> > de Jose Saldana
> > Enviado el: lunes, 24 de junio de 2013 13:00
> > Para: tcmtf@ietf.org
> > Asunto: [tcmtf] Answers to possible questions in the BOF
> >
> > I would like to start a thread about possible questions people may  ask
> > in the BOF. Obviously, we also need answers, so we should  cooperate.
> >
> > This is different from the "questions to ask in the BOF". This will  be
> > discussed separately.
> >
> > Thanks!
> >
> > Jose
> >
> > _______________________________________________
> > 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  Mon Jul  8 00:28:58 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 601BD11E81A5 for <tcmtf@ietfa.amsl.com>; Mon,  8 Jul 2013 00:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.374
X-Spam-Level: 
X-Spam-Status: No, score=-5.374 tagged_above=-999 required=5 tests=[AWL=-0.634, 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 kvDT8BHlUQjC for <tcmtf@ietfa.amsl.com>; Mon,  8 Jul 2013 00:28:54 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7D76A11E819D for <tcmtf@ietf.org>; Mon,  8 Jul 2013 00:28:53 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r687SgwI023746; Mon, 8 Jul 2013 09:28:42 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'jsalazar'" <jsalazar@unizar.es>, "Muthu Arul Mozhi Perumal \(mperumal\)" <mperumal@cisco.com>, "Dan Wing" <dwing@cisco.com>
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>	<009901ce725a$d1623360$74269a20$@unizar.es>	<2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>" <20130628105725.lmag0xgqsgogggww@webmail.unizar.es>" <EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com> <95d1a818ab88cf76070677949afba188@unizar.es> <007101ce7806$2d215860$87640920$@unizar.es> <bd93363fc447528c4ed5167c0e154198@unizar.es>
In-Reply-To: <bd93363fc447528c4ed5167c0e154198@unizar.es>
Date: Mon, 8 Jul 2013 09:28:44 +0200
Organization: Universidad de Zaragoza
Message-ID: <004601ce7bac$c8fc91b0$5af5b510$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Content-language: es
Thread-index: AQHxl5HfJe4XxEPJrqhURPk2/vEH5gJG8kQSAT8jBAUB238Z4AIljoQ2AbET9qADIMpcjQHjuA3AmKEnG0A=
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 08 Jul 2013 07:28:58 -0000

Hi, Muthu, Dan, Jose Luis.

It seems that we have identified some cases in which different security =
options are possible. The question here is:

Can this be issued in the TCMTF main draft (TCMTF Reference Model)?

Or do you think a TCMTF-security document would be interesting?

Jose

-----Mensaje original-----
De: jsalazar [mailto:jsalazar@unizar.es]=20
Enviado el: jueves, 04 de julio de 2013 19:36
Para: jsaldana@unizar.es
Asunto: RE: [tcmtf] Answers to possible questions in the BOF

Hi all.
With your last question, you have just hit the bullseye. I think the =
classification is correct. Cases 1 and 2a are a good way to keep the =
compromise between security and efficency. However, case 2b gives a step =
beyond and the security is compromised in the interest of efficiency.
In that case, users have to trust in tcmtf manager for managing their =
privacy also. Then, we will leave the tipical Public Key Infraestructure
(PKI) security architecture and use the Identity Based Encryption (IBE) =
one (http://tools.ietf.org/html/rfc5408).
They are three different scenarios and all of them seem to be very =
interesting, but the last one a bit more.
Regards:

JL

"I see them falling out the skies like eagles All mirrored glass and =
shattered egos"

Simple Minds.

El 2013-07-03 17:58, Jose Saldana escribi=C3=B3:
> Hi, Jose Luis. Good point.
>=20
> Regarding security, we could establish this classification:
>=20
> 1- Adding security to TCM: I have a number of non-secured flows=20
> traveling through a =E2=80=9Cdangerous=E2=80=9D network segment =
(perhaps a tunnel=20
> between appliances connecting remote offices of a company), and I want =

> not only traffic optimization but also security. In this case, I can=20
> simply use IPsec on the tunnel.
>=20
>=20
> 2- Using TCM for optimizing already secured communications: I have a=20
> bunch of already secured flows. Which is the best way for tunneling,=20
> compressing and multiplexing them?
>=20
> Two subcases:
>=20
> 2a- I can use TCM normally, but not only compress IP, TCP or UDP=20
> headers, but also security headers using a header compression method.
> Some possibilities for compressing security headers:
>=20
> - ROHCoIPsec, RFC5856 (http://tools.ietf.org/html/rfc5856)
> - RFC5225 http://tools.ietf.org/html/rfc5225
>=20
>=20
> 2b- But I can save more bandwidth if the TCM-ingress optimizer
> (TCM-IO) is able to:
> - rebuild the packets to their native form
> - TCM-optimize them
> - put them into a single security tunnel
>=20
> I have three phases (let's suppose I have 20 communications):
>=20
> Origin 1
> Origin 2     <----20 secured flows --------> TCM-IO <------1
> tunnel------> TCM-EO <-------- 20 secured flows----> destination 1, 2,
> 20
> ...
> Origin 20
>=20
> I have an advantage: In the shared network path, I use a single tunnel =

> instead of 20 different tunnels.
>=20
> But I have some additional requirements: I need processing capacity in =

> the TCM optimizers, and the endpoints should trust them.
>=20
>=20
> Is this classification correct? Any other options? Any other=20
> requirements? It is time for "security experts".
>=20
> Jose
>=20
> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre=20
> de jsalazar Enviado el: lunes, 01 de julio de 2013 20:50
> Para: tcmtf@ietf.org
> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>=20
> Hi all:
> Mmmmmmm. Since I see tcm-tf as a service, I can design the service=20
> with added security features that the type of communication is=20
> requiring. I think we have to be clear what we are expressing when we=20
> are talking about secure tcm-tf: Ensuring the service tcm-tf or=20
> applying the tcm-tf service for secure communications.
> The first possibility is not a great technological sophistication and=20
> the second one might consider the first one as a possible additional=20
> service.
> Therefore,
> every time we use the term "secure tcm-tf" should think the second=20
> option, for generality.
> On the other hand, we must also keep in mind that whenever users=20
> employ secure tcm-tf, they must trust the service fully and consider=20
> delegating the use of their keys (including private ones) to tcm-tf.
>=20
> Regards.
>=20
> JL
>=20
> "I see them falling out the skies like eagles All mirrored glass and=20
> shattered egos"
>=20
> Simple Minds.
>=20
> El 2013-07-01 18:55, Dan Wing escribi=C3=B3:
> > On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
> >
> > Hi all,
> >
> > Few days ago Julian talked about TCM-TF's security and now I've read =

> > in the link included by Dan, saying that the gain obtained when=20
> > multiplexing Ipsec-encrypted packets is 20-to-1. We have been=20
> > looking for more information about this issue and thinking about a=20
> > way to reduce the needed  bandwidth in IPsec flows.
> >
> > The main idea is to find a way to change the authentication of the=20
> > individual packets and merge all of them in a unique authentication.
> > Thus, instead of using 20 IPsec tunnels, we would have a single=20
> > tunnel including 20 flows. Is this something similar than how Cisco=20
> > gets the improvement?
> >
> > We would not be able to change IPsec any more than we could change=20
> > TCP, so I would not look at how to change IPsec authentication.
> >
> > However, if there are a bunch of IPsec packets sharing a common=20
> > path, I could see them being successfully multiplexed into one=20
> > larger packet at one tunnel endpoint and then de-multiplexed at the=20
> > other tunnel endpoint.  This can provide a packet per second=20
> > reduction.  I don't think there are enough bytes in an IPsec header=20
> > to bother trying to do IPsec header compression (SPI and sequence =
number are only 64 bits).
> >
> > -d
> >
> >
> >
> > Jos=C3=A9 Luis
> >
> >
> >
> > Dan Wing <dwing@cisco.com> ha escrito:
> >
> >
> > On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> =
wrote:
> >
> > Question 4: Is TCM-TF interesting for the Industry? Should the IETF=20
> > standardize this?
> >
> > Answer:
> >
> > 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP  =
traffic.
> > So if RFC4170 was interesting, why not updating it?
> >
> > 2) TCM-TF can be useful in order to save bandwidth in many cases:
> >
> > - Aggregation network of *network operators*: We are saving =20
> > bandwidth by optimizing and putting together traffic flows. Is this  =

> > interesting for a network operator? What about overprovisioning? =20
> > The idea is that there are places and moments in which a number of =20
> > flows based on small packets are in the same place and at the same =20
> > moment. Then, TCM-TF can be applied in order to provide =20
> > flexibility. We are not optimizing the overall Internet traffic, we  =

> > are optimizing specific flows with very tight delay requirements, =20
> > which network operators have to take care of in a special way.
> > www.huawei.com/ilink/en/download/HW_193034
> >
> > - *End to end* optimization: Nowadays, many appliances are used to=20
> > connect remote offices of the same company (creating a VPN). So if =20
> > a tunnel exists, why not optimizing this traffic when possible? We =20
> > would save bandwidth in the access network, where it can be scarce.
> >
> > - Wireless and satellite scenarios.
> >
> > "Cisco adds IP multiplexing to mobile satellite package", April =20
> > 2012,
> > http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing-
> 258082.html
> >
> >
> >
> >
> >
> > Any other thoughts? Any other scenarios in mind? Potential=20
> > beneficiaries?
> >
> > Some networks, today, use cRTP (RFC2508) on their access links.   =
This
> > gives bandwidth savings on the access link, but consumes =20
> > considerable CPU horsepower on the aggregation router (to perform  =
cRTP), but
> > provides no bandwidth savings across the network core.   If, =
instead,
> > the bandwidth could be saved on the access link, across  the core,=20
> > and on the far-end access link -- all without the CPU  impact on the =

> > aggregation router -- it is a considerable win.
> >
> > -d
> >
> >
> >
> >
> >
> > Jose
> >
> > De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =20
> > nombre de Jose Saldana Enviado el: lunes, 24 de junio de 2013 13:00
> > Para: tcmtf@ietf.org
> > Asunto: [tcmtf] Answers to possible questions in the BOF
> >
> > I would like to start a thread about possible questions people may =20
> > ask in the BOF. Obviously, we also need answers, so we should  =
cooperate.
> >
> > This is different from the "questions to ask in the BOF". This will  =

> > be discussed separately.
> >
> > Thanks!
> >
> > Jose
> >
> > _______________________________________________
> > 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


From diego@tid.es  Mon Jul  8 02:59:13 2013
Return-Path: <diego@tid.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 217A711E81C5 for <tcmtf@ietfa.amsl.com>; Mon,  8 Jul 2013 02:59:13 -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 kzGhg-mpUM9T for <tcmtf@ietfa.amsl.com>; Mon,  8 Jul 2013 02:59:09 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id DFC9721F9ED3 for <tcmtf@ietf.org>; Mon,  8 Jul 2013 02:59:07 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MPM00IYC3QIC3@tid.hi.inet> for tcmtf@ietf.org; Mon, 08 Jul 2013 11:59:06 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 76.82.03142.A6D8AD15; Mon, 08 Jul 2013 11:59:06 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MPM00IY43QIC3@tid.hi.inet> for tcmtf@ietf.org; Mon, 08 Jul 2013 11:59:06 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Mon, 08 Jul 2013 11:57:51 +0200
Date: Mon, 08 Jul 2013 09:59:06 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <004601ce7bac$c8fc91b0$5af5b510$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "<jsaldana@unizar.es>" <jsaldana@unizar.es>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A049CD0C7F1@EX10-MB2-MAD.hi.inet>
Content-id: <A59662B3AE0E07498A04FB136A601062@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=Windows-1252
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Answers to possible questions in the BOF
Thread-index: Ac5wycGHbApylKz/RhmtAnL3dgONFwJG8kQSAT8jBAUB238Z4AIljoQ2AbET9qADIMpcjQHjuA3AmKEnG0DnAsGfAA==
X-AuditID: 0a5f4068-b7f128e000000c46-0d-51da8d6a3aad
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42Lhinfg0s3qvRVocHKbrMWuzxsYHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVcadrC3PBtpiKjpX3mBsYb3p1MXJwSAiYSLx/VNDFyAlkiklc uLeeDcQWEtjIKHF4vksXIxeQ/YNR4v6qHiYIZxqjxJYlr9hAmlkEVCXm3NcCaWADMh81/2YH sYUFbCX2/L3DCGJzClhI7Jzfxg6xQEHiz7nHLCC2iIC+xI3HIPVcHMwCixgl1r//B7aZV8Bb 4v/iLawgNrOAmcTfztVMEHFBiR+T77FAxPUkPv65zQhhi0s0t96EimtLPHl3AayXUUBW4t38 +awQy+wkpm/bCLU4R+LTuemMEAcJSCzZc54ZwhaVePn4HyvEkw1MEivuv2KZwCgxC8kds5Dc MQvJHbOQ3DELyR0LGFlXMYoVJxVlpmeU5CZm5qQbGOplZOpl5qWWbGKExF3GDsblO1UOMQpw MCrx8D54cjNQiDWxrLgy9xCjBAezkgivOOutQCHelMTKqtSi/Pii0pzU4kOMTBycUg2Mqzb7 OPbaHYn+I3vu2+n5LQp607PZ6nZXlpVOX/raYHd2sYTPbq8V96+E8VpMlYyflzgtyCuwYM9V ed2aVU4TFgtf5Yv7sLKr4q7bvmdeyxbVHvf2Zz3zM+uG6CHJ/7NF5grVmswoVGorn1S597ac smbSt63xzQ4qevunzszfueO8hN/m4nYZJZbijERDLeai4kQAijuunpkCAAA=
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>" <20130628105725.lmag0xgqsgogggww@webmail.unizar.es> <004601ce7bac$c8fc91b0$5af5b510$@unizar.es>
Cc: "<tcmtf@ietf.org>" <tcmtf@ietf.org>, "Muthu Arul Mozhi Perumal \(mperumal\)" <mperumal@cisco.com>, jsalazar <jsalazar@unizar.es>, Dan Wing <dwing@cisco.com>
Subject: Re: [tcmtf] Answers to possible questions in 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: Mon, 08 Jul 2013 09:59:13 -0000

Hi,

When talking about security, we should not forget two different aspects:

1) Applying TCMTF to enhance (or provide a better support to) security netw=
ork services, like IPsec or VPNs

2) Securing the application of TCMTF itself

As far as I can tell, most of the discussion so far has been on the first a=
spect. This could be outlined as an use case, and further discussed in a se=
parate document if required, oriented towards "Applying TCMTF in secure env=
ironments" or the like

Regarding the second issue, I tried to make a few points some time ago:

8<---

> We can consider different security contexts for different tunnels, accord=
ing to some policy agreed by both end-points at a given tunnel. The securit=
y contexts would define encryption, authentication, or both. We'd have to g=
o into more detail to evaluate potential savings, but I have the feeling th=
ey could be worth considering.
>
> The point is that if we go for these different security contexts, we must=
 consider how they can be established by mutual authentication of the tunne=
l end-points, and this opens additional issues regarding configuration and =
crypto material exchange, as well as the possibility of user-initiated auth=
entication by means of protocols like OAuth.
>
> I'd keep this in the list of the "soon-to-open" issues, focusing on the t=
hree main docs we have been discussing so far.

8<---

I had the intention to elaborate them a little more, but other matters pre-=
empted this :-(
My take is that some reflections on this should be included in the "Securit=
y Considerations" section of the framework document, and a further document=
 on this be considered in a further stage.

Be goode,

On 8 Jul 2013, at 09:28 , Jose Saldana wrote:

> Hi, Muthu, Dan, Jose Luis.
>
> It seems that we have identified some cases in which different security o=
ptions are possible. The question here is:
>
> Can this be issued in the TCMTF main draft (TCMTF Reference Model)?
>
> Or do you think a TCMTF-security document would be interesting?
>
> Jose
>
> -----Mensaje original-----
> De: jsalazar [mailto:jsalazar@unizar.es]
> Enviado el: jueves, 04 de julio de 2013 19:36
> Para: jsaldana@unizar.es
> Asunto: RE: [tcmtf] Answers to possible questions in the BOF
>
> Hi all.
> With your last question, you have just hit the bullseye. I think the clas=
sification is correct. Cases 1 and 2a are a good way to keep the compromise=
 between security and efficency. However, case 2b gives a step beyond and t=
he security is compromised in the interest of efficiency.
> In that case, users have to trust in tcmtf manager for managing their pri=
vacy also. Then, we will leave the tipical Public Key Infraestructure
> (PKI) security architecture and use the Identity Based Encryption (IBE) o=
ne (http://tools.ietf.org/html/rfc5408).
> They are three different scenarios and all of them seem to be very intere=
sting, but the last one a bit more.
> Regards:
>
> JL
>
> "I see them falling out the skies like eagles All mirrored glass and shat=
tered egos"
>
> Simple Minds.
>
> El 2013-07-03 17:58, Jose Saldana escribi=F3:
>> Hi, Jose Luis. Good point.
>>
>> Regarding security, we could establish this classification:
>>
>> 1- Adding security to TCM: I have a number of non-secured flows
>> traveling through a =93dangerous=94 network segment (perhaps a tunnel
>> between appliances connecting remote offices of a company), and I want
>> not only traffic optimization but also security. In this case, I can
>> simply use IPsec on the tunnel.
>>
>>
>> 2- Using TCM for optimizing already secured communications: I have a
>> bunch of already secured flows. Which is the best way for tunneling,
>> compressing and multiplexing them?
>>
>> Two subcases:
>>
>> 2a- I can use TCM normally, but not only compress IP, TCP or UDP
>> headers, but also security headers using a header compression method.
>> Some possibilities for compressing security headers:
>>
>> - ROHCoIPsec, RFC5856 (http://tools.ietf.org/html/rfc5856)
>> - RFC5225 http://tools.ietf.org/html/rfc5225
>>
>>
>> 2b- But I can save more bandwidth if the TCM-ingress optimizer
>> (TCM-IO) is able to:
>> - rebuild the packets to their native form
>> - TCM-optimize them
>> - put them into a single security tunnel
>>
>> I have three phases (let's suppose I have 20 communications):
>>
>> Origin 1
>> Origin 2     <----20 secured flows --------> TCM-IO <------1
>> tunnel------> TCM-EO <-------- 20 secured flows----> destination 1, 2,
>> 20
>> ...
>> Origin 20
>>
>> I have an advantage: In the shared network path, I use a single tunnel
>> instead of 20 different tunnels.
>>
>> But I have some additional requirements: I need processing capacity in
>> the TCM optimizers, and the endpoints should trust them.
>>
>>
>> Is this classification correct? Any other options? Any other
>> requirements? It is time for "security experts".
>>
>> Jose
>>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>> de jsalazar Enviado el: lunes, 01 de julio de 2013 20:50
>> Para: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>>
>> Hi all:
>> Mmmmmmm. Since I see tcm-tf as a service, I can design the service
>> with added security features that the type of communication is
>> requiring. I think we have to be clear what we are expressing when we
>> are talking about secure tcm-tf: Ensuring the service tcm-tf or
>> applying the tcm-tf service for secure communications.
>> The first possibility is not a great technological sophistication and
>> the second one might consider the first one as a possible additional
>> service.
>> Therefore,
>> every time we use the term "secure tcm-tf" should think the second
>> option, for generality.
>> On the other hand, we must also keep in mind that whenever users
>> employ secure tcm-tf, they must trust the service fully and consider
>> delegating the use of their keys (including private ones) to tcm-tf.
>>
>> Regards.
>>
>> JL
>>
>> "I see them falling out the skies like eagles All mirrored glass and
>> shattered egos"
>>
>> Simple Minds.
>>
>> El 2013-07-01 18:55, Dan Wing escribi=F3:
>>> On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
>>>
>>> Hi all,
>>>
>>> Few days ago Julian talked about TCM-TF's security and now I've read
>>> in the link included by Dan, saying that the gain obtained when
>>> multiplexing Ipsec-encrypted packets is 20-to-1. We have been
>>> looking for more information about this issue and thinking about a
>>> way to reduce the needed  bandwidth in IPsec flows.
>>>
>>> The main idea is to find a way to change the authentication of the
>>> individual packets and merge all of them in a unique authentication.
>>> Thus, instead of using 20 IPsec tunnels, we would have a single
>>> tunnel including 20 flows. Is this something similar than how Cisco
>>> gets the improvement?
>>>
>>> We would not be able to change IPsec any more than we could change
>>> TCP, so I would not look at how to change IPsec authentication.
>>>
>>> However, if there are a bunch of IPsec packets sharing a common
>>> path, I could see them being successfully multiplexed into one
>>> larger packet at one tunnel endpoint and then de-multiplexed at the
>>> other tunnel endpoint.  This can provide a packet per second
>>> reduction.  I don't think there are enough bytes in an IPsec header
>>> to bother trying to do IPsec header compression (SPI and sequence numbe=
r are only 64 bits).
>>>
>>> -d
>>>
>>>
>>>
>>> Jos=E9 Luis
>>>
>>>
>>>
>>> Dan Wing <dwing@cisco.com> ha escrito:
>>>
>>>
>>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> wrote:
>>>
>>> Question 4: Is TCM-TF interesting for the Industry? Should the IETF
>>> standardize this?
>>>
>>> Answer:
>>>
>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP  traffic.
>>> So if RFC4170 was interesting, why not updating it?
>>>
>>> 2) TCM-TF can be useful in order to save bandwidth in many cases:
>>>
>>> - Aggregation network of *network operators*: We are saving
>>> bandwidth by optimizing and putting together traffic flows. Is this
>>> interesting for a network operator? What about overprovisioning?
>>> The idea is that there are places and moments in which a number of
>>> flows based on small packets are in the same place and at the same
>>> moment. Then, TCM-TF can be applied in order to provide
>>> flexibility. We are not optimizing the overall Internet traffic, we
>>> are optimizing specific flows with very tight delay requirements,
>>> which network operators have to take care of in a special way.
>>> www.huawei.com/ilink/en/download/HW_193034
>>>
>>> - *End to end* optimization: Nowadays, many appliances are used to
>>> connect remote offices of the same company (creating a VPN). So if
>>> a tunnel exists, why not optimizing this traffic when possible? We
>>> would save bandwidth in the access network, where it can be scarce.
>>>
>>> - Wireless and satellite scenarios.
>>>
>>> "Cisco adds IP multiplexing to mobile satellite package", April
>>> 2012,
>>> http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing-
>> 258082.html
>>>
>>>
>>>
>>>
>>>
>>> Any other thoughts? Any other scenarios in mind? Potential
>>> beneficiaries?
>>>
>>> Some networks, today, use cRTP (RFC2508) on their access links.   This
>>> gives bandwidth savings on the access link, but consumes
>>> considerable CPU horsepower on the aggregation router (to perform  cRTP=
), but
>>> provides no bandwidth savings across the network core.   If, instead,
>>> the bandwidth could be saved on the access link, across  the core,
>>> and on the far-end access link -- all without the CPU  impact on the
>>> aggregation router -- it is a considerable win.
>>>
>>> -d
>>>
>>>
>>>
>>>
>>>
>>> Jose
>>>
>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>>> nombre de Jose Saldana Enviado el: lunes, 24 de junio de 2013 13:00
>>> Para: tcmtf@ietf.org
>>> Asunto: [tcmtf] Answers to possible questions in the BOF
>>>
>>> I would like to start a thread about possible questions people may
>>> ask in the BOF. Obviously, we also need answers, so we should  cooperat=
e.
>>>
>>> This is different from the "questions to ask in the BOF". This will
>>> be discussed separately.
>>>
>>> Thanks!
>>>
>>> Jose
>>>
>>> _______________________________________________
>>> 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
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

From jsaldana@unizar.es  Mon Jul  8 07:56:54 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 6E7D721F9D4E for <tcmtf@ietfa.amsl.com>; Mon,  8 Jul 2013 07:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.264
X-Spam-Level: 
X-Spam-Status: No, score=-6.264 tagged_above=-999 required=5 tests=[AWL=0.335,  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 k5PYEvepTXWR for <tcmtf@ietfa.amsl.com>; Mon,  8 Jul 2013 07:56:50 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 73E6421F9D40 for <tcmtf@ietf.org>; Mon,  8 Jul 2013 07:56:48 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r68EucH8027757; Mon, 8 Jul 2013 16:56:38 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Diego R. Lopez'" <diego@tid.es>
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>	<009901ce725a$d1623360$74269a20$@unizar.es>	<2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>"	<20130628105725.lmag0xgqsgogggww@webmail.unizar.es>	<004601ce7bac$c8fc91b0$5af5b510$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CD0C7F1@EX10-MB2-MAD.hi.inet>
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A049CD0C7F1@EX10-MB2-MAD.hi.inet>
Date: Mon, 8 Jul 2013 16:56:42 +0200
Organization: Universidad de Zaragoza
Message-ID: <002301ce7beb$5c198370$144c8a50$@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: AQHxl5HfJe4XxEPJrqhURPk2/vEH5gJG8kQSAT8jBAUB238Z4AI2LB8yAU3srAyYzXlWgA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>, 'jsalazar' <jsalazar@unizar.es>, 'Dan Wing' <dwing@cisco.com>
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 08 Jul 2013 14:56:54 -0000

So it seems that the possibility of a document about Security & TCM-TF =
might
be interesting. What about adding a sentence in the Charter =
(re-chartering
paragraph), talking about that possibility?

....
9. If other interesting features are identified, the group would =
re-charter
and include them, e.g., a=20
mechanism for a multiplexer to discover a de-multiplexer, and vice =
versa; a
mechanism to select an=20
optimal multiplexer and a de-multiplexer when there are more than one
muxer/de-muxer for a flow;=20
dynamically applying TCMTF: a higher entity in charge of deciding when =
and
where, applying or not=20
TCMTF, and what kind of TCMTF, and what multiplexing period. Additional
methods for estimating delay=20
would also be required; *security issues related to TCM-TF, and methods =
for
securing TCM optimized flows.*
....

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Diego R. Lopez
> Enviado el: lunes, 08 de julio de 2013 11:59
> Para: <jsaldana@unizar.es>
> CC: <tcmtf@ietf.org>; Muthu Arul Mozhi Perumal (mperumal); jsalazar; =
Dan
> Wing
> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>=20
> Hi,
>=20
> When talking about security, we should not forget two different =
aspects:
>=20
> 1) Applying TCMTF to enhance (or provide a better support to) security
> network services, like IPsec or VPNs
>=20
> 2) Securing the application of TCMTF itself
>=20
> As far as I can tell, most of the discussion so far has been on the =
first
aspect.
> This could be outlined as an use case, and further discussed in a =
separate
> document if required, oriented towards "Applying TCMTF in secure
> environments" or the like
>=20
> Regarding the second issue, I tried to make a few points some time =
ago:
>=20
> 8<---
>=20
> > We can consider different security contexts for different tunnels,
according
> to some policy agreed by both end-points at a given tunnel. The =
security
> contexts would define encryption, authentication, or both. We'd have =
to go
> into more detail to evaluate potential savings, but I have the feeling
they
> could be worth considering.
> >
> > The point is that if we go for these different security contexts, we
must
> consider how they can be established by mutual authentication of the
tunnel
> end-points, and this opens additional issues regarding configuration =
and
> crypto material exchange, as well as the possibility of user-initiated
> authentication by means of protocols like OAuth.
> >
> > I'd keep this in the list of the "soon-to-open" issues, focusing on =
the
three
> main docs we have been discussing so far.
>=20
> 8<---
>=20
> I had the intention to elaborate them a little more, but other matters
pre-
> empted this :-( My take is that some reflections on this should be
included in
> the "Security Considerations" section of the framework document, and a
> further document on this be considered in a further stage.
>=20
> Be goode,
>=20
> On 8 Jul 2013, at 09:28 , Jose Saldana wrote:
>=20
> > Hi, Muthu, Dan, Jose Luis.
> >
> > It seems that we have identified some cases in which different =
security
> options are possible. The question here is:
> >
> > Can this be issued in the TCMTF main draft (TCMTF Reference Model)?
> >
> > Or do you think a TCMTF-security document would be interesting?
> >
> > Jose
> >
> > -----Mensaje original-----
> > De: jsalazar [mailto:jsalazar@unizar.es] Enviado el: jueves, 04 de
> > julio de 2013 19:36
> > Para: jsaldana@unizar.es
> > Asunto: RE: [tcmtf] Answers to possible questions in the BOF
> >
> > Hi all.
> > With your last question, you have just hit the bullseye. I think the
> classification is correct. Cases 1 and 2a are a good way to keep the
> compromise between security and efficency. However, case 2b gives a =
step
> beyond and the security is compromised in the interest of efficiency.
> > In that case, users have to trust in tcmtf manager for managing =
their
> > privacy also. Then, we will leave the tipical Public Key
> > Infraestructure
> > (PKI) security architecture and use the Identity Based Encryption =
(IBE)
one
> (http://tools.ietf.org/html/rfc5408).
> > They are three different scenarios and all of them seem to be very
> interesting, but the last one a bit more.
> > Regards:
> >
> > JL
> >
> > "I see them falling out the skies like eagles All mirrored glass and
shattered
> egos"
> >
> > Simple Minds.
> >
> > El 2013-07-03 17:58, Jose Saldana escribi=F3:
> >> Hi, Jose Luis. Good point.
> >>
> >> Regarding security, we could establish this classification:
> >>
> >> 1- Adding security to TCM: I have a number of non-secured flows
> >> traveling through a =93dangerous=94 network segment (perhaps a =
tunnel
> >> between appliances connecting remote offices of a company), and I
> >> want not only traffic optimization but also security. In this case, =
I
> >> can simply use IPsec on the tunnel.
> >>
> >>
> >> 2- Using TCM for optimizing already secured communications: I have =
a
> >> bunch of already secured flows. Which is the best way for =
tunneling,
> >> compressing and multiplexing them?
> >>
> >> Two subcases:
> >>
> >> 2a- I can use TCM normally, but not only compress IP, TCP or UDP
> >> headers, but also security headers using a header compression =
method.
> >> Some possibilities for compressing security headers:
> >>
> >> - ROHCoIPsec, RFC5856 (http://tools.ietf.org/html/rfc5856)
> >> - RFC5225 http://tools.ietf.org/html/rfc5225
> >>
> >>
> >> 2b- But I can save more bandwidth if the TCM-ingress optimizer
> >> (TCM-IO) is able to:
> >> - rebuild the packets to their native form
> >> - TCM-optimize them
> >> - put them into a single security tunnel
> >>
> >> I have three phases (let's suppose I have 20 communications):
> >>
> >> Origin 1
> >> Origin 2     <----20 secured flows --------> TCM-IO <------1
> >> tunnel------> TCM-EO <-------- 20 secured flows----> destination 1,
> >> tunnel------> 2,
> >> 20
> >> ...
> >> Origin 20
> >>
> >> I have an advantage: In the shared network path, I use a single
> >> tunnel instead of 20 different tunnels.
> >>
> >> But I have some additional requirements: I need processing capacity
> >> in the TCM optimizers, and the endpoints should trust them.
> >>
> >>
> >> Is this classification correct? Any other options? Any other
> >> requirements? It is time for "security experts".
> >>
> >> Jose
> >>
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> >> de jsalazar Enviado el: lunes, 01 de julio de 2013 20:50
> >> Para: tcmtf@ietf.org
> >> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
> >>
> >> Hi all:
> >> Mmmmmmm. Since I see tcm-tf as a service, I can design the service
> >> with added security features that the type of communication is
> >> requiring. I think we have to be clear what we are expressing when =
we
> >> are talking about secure tcm-tf: Ensuring the service tcm-tf or
> >> applying the tcm-tf service for secure communications.
> >> The first possibility is not a great technological sophistication =
and
> >> the second one might consider the first one as a possible =
additional
> >> service.
> >> Therefore,
> >> every time we use the term "secure tcm-tf" should think the second
> >> option, for generality.
> >> On the other hand, we must also keep in mind that whenever users
> >> employ secure tcm-tf, they must trust the service fully and =
consider
> >> delegating the use of their keys (including private ones) to =
tcm-tf.
> >>
> >> Regards.
> >>
> >> JL
> >>
> >> "I see them falling out the skies like eagles All mirrored glass =
and
> >> shattered egos"
> >>
> >> Simple Minds.
> >>
> >> El 2013-07-01 18:55, Dan Wing escribi=F3:
> >>> On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Few days ago Julian talked about TCM-TF's security and now I've =
read
> >>> in the link included by Dan, saying that the gain obtained when
> >>> multiplexing Ipsec-encrypted packets is 20-to-1. We have been
> >>> looking for more information about this issue and thinking about a
> >>> way to reduce the needed  bandwidth in IPsec flows.
> >>>
> >>> The main idea is to find a way to change the authentication of the
> >>> individual packets and merge all of them in a unique =
authentication.
> >>> Thus, instead of using 20 IPsec tunnels, we would have a single
> >>> tunnel including 20 flows. Is this something similar than how =
Cisco
> >>> gets the improvement?
> >>>
> >>> We would not be able to change IPsec any more than we could change
> >>> TCP, so I would not look at how to change IPsec authentication.
> >>>
> >>> However, if there are a bunch of IPsec packets sharing a common
> >>> path, I could see them being successfully multiplexed into one
> >>> larger packet at one tunnel endpoint and then de-multiplexed at =
the
> >>> other tunnel endpoint.  This can provide a packet per second
> >>> reduction.  I don't think there are enough bytes in an IPsec =
header
> >>> to bother trying to do IPsec header compression (SPI and sequence
> number are only 64 bits).
> >>>
> >>> -d
> >>>
> >>>
> >>>
> >>> Jos=E9 Luis
> >>>
> >>>
> >>>
> >>> Dan Wing <dwing@cisco.com> ha escrito:
> >>>
> >>>
> >>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> =
wrote:
> >>>
> >>> Question 4: Is TCM-TF interesting for the Industry? Should the =
IETF
> >>> standardize this?
> >>>
> >>> Answer:
> >>>
> >>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP
traffic.
> >>> So if RFC4170 was interesting, why not updating it?
> >>>
> >>> 2) TCM-TF can be useful in order to save bandwidth in many cases:
> >>>
> >>> - Aggregation network of *network operators*: We are saving
> >>> bandwidth by optimizing and putting together traffic flows. Is =
this
> >>> interesting for a network operator? What about overprovisioning?
> >>> The idea is that there are places and moments in which a number of
> >>> flows based on small packets are in the same place and at the same
> >>> moment. Then, TCM-TF can be applied in order to provide =
flexibility.
> >>> We are not optimizing the overall Internet traffic, we are
> >>> optimizing specific flows with very tight delay requirements, =
which
> >>> network operators have to take care of in a special way.
> >>> www.huawei.com/ilink/en/download/HW_193034
> >>>
> >>> - *End to end* optimization: Nowadays, many appliances are used to
> >>> connect remote offices of the same company (creating a VPN). So if =
a
> >>> tunnel exists, why not optimizing this traffic when possible? We
> >>> would save bandwidth in the access network, where it can be =
scarce.
> >>>
> >>> - Wireless and satellite scenarios.
> >>>
> >>> "Cisco adds IP multiplexing to mobile satellite package", April
> >>> 2012,
> >>> http://www.networkworld.com/news/2012/040912-cisco-ip-
> multiplexing-
> >> 258082.html
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Any other thoughts? Any other scenarios in mind? Potential
> >>> beneficiaries?
> >>>
> >>> Some networks, today, use cRTP (RFC2508) on their access links.   =
This
> >>> gives bandwidth savings on the access link, but consumes
> >>> considerable CPU horsepower on the aggregation router (to perform
> cRTP), but
> >>> provides no bandwidth savings across the network core.   If, =
instead,
> >>> the bandwidth could be saved on the access link, across  the core,
> >>> and on the far-end access link -- all without the CPU  impact on =
the
> >>> aggregation router -- it is a considerable win.
> >>>
> >>> -d
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Jose
> >>>
> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> nombre
> >>> de Jose Saldana Enviado el: lunes, 24 de junio de 2013 13:00
> >>> Para: tcmtf@ietf.org
> >>> Asunto: [tcmtf] Answers to possible questions in the BOF
> >>>
> >>> I would like to start a thread about possible questions people may
> >>> ask in the BOF. Obviously, we also need answers, so we should
> cooperate.
> >>>
> >>> This is different from the "questions to ask in the BOF". This =
will
> >>> be discussed separately.
> >>>
> >>> Thanks!
> >>>
> >>> Jose
> >>>
> >>> _______________________________________________
> >>> 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
> >
> > _______________________________________________
> > tcmtf mailing list
> > tcmtf@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcmtf
>=20
>=20
> --
> "Esta vez no fallaremos, Doctor Infierno"
>=20
> Dr Diego R. Lopez
> Telefonica I+D
> http://people.tid.es/diego.lopez/
>=20
> e-mail: diego@tid.es
> Tel:    +34 913 129 041
> Mobile: +34 682 051 091
> -----------------------------------------
>=20
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar
> nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en =
el enlace
> situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send =
and
> receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From jsaldana@unizar.es  Tue Jul  9 03:43:28 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 3D42F21F9FE1 for <tcmtf@ietfa.amsl.com>; Tue,  9 Jul 2013 03:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.25
X-Spam-Level: 
X-Spam-Status: No, score=-6.25 tagged_above=-999 required=5 tests=[AWL=0.349,  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 Y2xN5X69ZirC for <tcmtf@ietfa.amsl.com>; Tue,  9 Jul 2013 03:43:24 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 05D0D21F9FE9 for <tcmtf@ietf.org>; Tue,  9 Jul 2013 03:43:20 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r69Ah9Vo028969; Tue, 9 Jul 2013 12:43:10 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Diego R. Lopez'" <diego@tid.es>
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>	<009901ce725a$d1623360$74269a20$@unizar.es>	<2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>"	<20130628105725.lmag0xgqsgogggww@webmail.unizar.es>	<004601ce7bac$c8fc91b0$5af5b510$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CD0C7F1@EX10-MB2-MAD.hi.inet>
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A049CD0C7F1@EX10-MB2-MAD.hi.inet>
Date: Tue, 9 Jul 2013 12:43:11 +0200
Organization: Universidad de Zaragoza
Message-ID: <00b001ce7c91$1dcc6640$596532c0$@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: AQHxl5HfJe4XxEPJrqhURPk2/vEH5gJG8kQSAT8jBAUB238Z4AI2LB8yAU3srAyYzsP/oA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>, 'jsalazar' <jsalazar@unizar.es>, 'Dan Wing' <dwing@cisco.com>
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 09 Jul 2013 10:43:28 -0000

Hi all,

I am finishing the next version of the draft. In the "security
considerations" section in the end. The idea is talking about the two
options (as summarized by Diego):

- Securing the application of TCMTF itself
- Applying TCMTF to enhance (or provide a better support to) security
network services, like IPsec or VPNs

So I would include these two paragraphs, if you agree:


The most straightforward option for securing a number of non-secured =
flows
sharing a path is by the use of IPsec [IPsec], when TCM using an IP =
tunnel
is employed. Instead of adding a security header to the packets of each
native flow, and then compressing and multiplexing, a single IPsec =
tunnel
can be used in order to secure all the flows together, thus achieving a
better efficiency.

When a number of already secured flows including ESP headers is =
optimized by
means of TCM, and the addition of further security is not necessary, =
their
ESP headers can still be compressed using suitable algorithms, in order =
to
improve the efficiency.


Any improvements? Any other ideas?

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Diego R. Lopez
> Enviado el: lunes, 08 de julio de 2013 11:59
> Para: <jsaldana@unizar.es>
> CC: <tcmtf@ietf.org>; Muthu Arul Mozhi Perumal (mperumal); jsalazar; =
Dan
> Wing
> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>=20
> Hi,
>=20
> When talking about security, we should not forget two different =
aspects:
>=20
> 1) Applying TCMTF to enhance (or provide a better support to) security
> network services, like IPsec or VPNs
>=20
> 2) Securing the application of TCMTF itself
>=20
> As far as I can tell, most of the discussion so far has been on the =
first
aspect.
> This could be outlined as an use case, and further discussed in a =
separate
> document if required, oriented towards "Applying TCMTF in secure
> environments" or the like
>=20
> Regarding the second issue, I tried to make a few points some time =
ago:
>=20
> 8<---
>=20
> > We can consider different security contexts for different tunnels,
according
> to some policy agreed by both end-points at a given tunnel. The =
security
> contexts would define encryption, authentication, or both. We'd have =
to go
> into more detail to evaluate potential savings, but I have the feeling
they
> could be worth considering.
> >
> > The point is that if we go for these different security contexts, we
must
> consider how they can be established by mutual authentication of the
tunnel
> end-points, and this opens additional issues regarding configuration =
and
> crypto material exchange, as well as the possibility of user-initiated
> authentication by means of protocols like OAuth.
> >
> > I'd keep this in the list of the "soon-to-open" issues, focusing on =
the
three
> main docs we have been discussing so far.
>=20
> 8<---
>=20
> I had the intention to elaborate them a little more, but other matters
pre-
> empted this :-( My take is that some reflections on this should be
included in
> the "Security Considerations" section of the framework document, and a
> further document on this be considered in a further stage.
>=20
> Be goode,
>=20
> On 8 Jul 2013, at 09:28 , Jose Saldana wrote:
>=20
> > Hi, Muthu, Dan, Jose Luis.
> >
> > It seems that we have identified some cases in which different =
security
> options are possible. The question here is:
> >
> > Can this be issued in the TCMTF main draft (TCMTF Reference Model)?
> >
> > Or do you think a TCMTF-security document would be interesting?
> >
> > Jose
> >
> > -----Mensaje original-----
> > De: jsalazar [mailto:jsalazar@unizar.es] Enviado el: jueves, 04 de
> > julio de 2013 19:36
> > Para: jsaldana@unizar.es
> > Asunto: RE: [tcmtf] Answers to possible questions in the BOF
> >
> > Hi all.
> > With your last question, you have just hit the bullseye. I think the
> classification is correct. Cases 1 and 2a are a good way to keep the
> compromise between security and efficency. However, case 2b gives a =
step
> beyond and the security is compromised in the interest of efficiency.
> > In that case, users have to trust in tcmtf manager for managing =
their
> > privacy also. Then, we will leave the tipical Public Key
> > Infraestructure
> > (PKI) security architecture and use the Identity Based Encryption =
(IBE)
one
> (http://tools.ietf.org/html/rfc5408).
> > They are three different scenarios and all of them seem to be very
> interesting, but the last one a bit more.
> > Regards:
> >
> > JL
> >
> > "I see them falling out the skies like eagles All mirrored glass and
shattered
> egos"
> >
> > Simple Minds.
> >
> > El 2013-07-03 17:58, Jose Saldana escribi=F3:
> >> Hi, Jose Luis. Good point.
> >>
> >> Regarding security, we could establish this classification:
> >>
> >> 1- Adding security to TCM: I have a number of non-secured flows
> >> traveling through a =93dangerous=94 network segment (perhaps a =
tunnel
> >> between appliances connecting remote offices of a company), and I
> >> want not only traffic optimization but also security. In this case, =
I
> >> can simply use IPsec on the tunnel.
> >>
> >>
> >> 2- Using TCM for optimizing already secured communications: I have =
a
> >> bunch of already secured flows. Which is the best way for =
tunneling,
> >> compressing and multiplexing them?
> >>
> >> Two subcases:
> >>
> >> 2a- I can use TCM normally, but not only compress IP, TCP or UDP
> >> headers, but also security headers using a header compression =
method.
> >> Some possibilities for compressing security headers:
> >>
> >> - ROHCoIPsec, RFC5856 (http://tools.ietf.org/html/rfc5856)
> >> - RFC5225 http://tools.ietf.org/html/rfc5225
> >>
> >>
> >> 2b- But I can save more bandwidth if the TCM-ingress optimizer
> >> (TCM-IO) is able to:
> >> - rebuild the packets to their native form
> >> - TCM-optimize them
> >> - put them into a single security tunnel
> >>
> >> I have three phases (let's suppose I have 20 communications):
> >>
> >> Origin 1
> >> Origin 2     <----20 secured flows --------> TCM-IO <------1
> >> tunnel------> TCM-EO <-------- 20 secured flows----> destination 1,
> >> tunnel------> 2,
> >> 20
> >> ...
> >> Origin 20
> >>
> >> I have an advantage: In the shared network path, I use a single
> >> tunnel instead of 20 different tunnels.
> >>
> >> But I have some additional requirements: I need processing capacity
> >> in the TCM optimizers, and the endpoints should trust them.
> >>
> >>
> >> Is this classification correct? Any other options? Any other
> >> requirements? It is time for "security experts".
> >>
> >> Jose
> >>
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> >> de jsalazar Enviado el: lunes, 01 de julio de 2013 20:50
> >> Para: tcmtf@ietf.org
> >> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
> >>
> >> Hi all:
> >> Mmmmmmm. Since I see tcm-tf as a service, I can design the service
> >> with added security features that the type of communication is
> >> requiring. I think we have to be clear what we are expressing when =
we
> >> are talking about secure tcm-tf: Ensuring the service tcm-tf or
> >> applying the tcm-tf service for secure communications.
> >> The first possibility is not a great technological sophistication =
and
> >> the second one might consider the first one as a possible =
additional
> >> service.
> >> Therefore,
> >> every time we use the term "secure tcm-tf" should think the second
> >> option, for generality.
> >> On the other hand, we must also keep in mind that whenever users
> >> employ secure tcm-tf, they must trust the service fully and =
consider
> >> delegating the use of their keys (including private ones) to =
tcm-tf.
> >>
> >> Regards.
> >>
> >> JL
> >>
> >> "I see them falling out the skies like eagles All mirrored glass =
and
> >> shattered egos"
> >>
> >> Simple Minds.
> >>
> >> El 2013-07-01 18:55, Dan Wing escribi=F3:
> >>> On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Few days ago Julian talked about TCM-TF's security and now I've =
read
> >>> in the link included by Dan, saying that the gain obtained when
> >>> multiplexing Ipsec-encrypted packets is 20-to-1. We have been
> >>> looking for more information about this issue and thinking about a
> >>> way to reduce the needed  bandwidth in IPsec flows.
> >>>
> >>> The main idea is to find a way to change the authentication of the
> >>> individual packets and merge all of them in a unique =
authentication.
> >>> Thus, instead of using 20 IPsec tunnels, we would have a single
> >>> tunnel including 20 flows. Is this something similar than how =
Cisco
> >>> gets the improvement?
> >>>
> >>> We would not be able to change IPsec any more than we could change
> >>> TCP, so I would not look at how to change IPsec authentication.
> >>>
> >>> However, if there are a bunch of IPsec packets sharing a common
> >>> path, I could see them being successfully multiplexed into one
> >>> larger packet at one tunnel endpoint and then de-multiplexed at =
the
> >>> other tunnel endpoint.  This can provide a packet per second
> >>> reduction.  I don't think there are enough bytes in an IPsec =
header
> >>> to bother trying to do IPsec header compression (SPI and sequence
> number are only 64 bits).
> >>>
> >>> -d
> >>>
> >>>
> >>>
> >>> Jos=E9 Luis
> >>>
> >>>
> >>>
> >>> Dan Wing <dwing@cisco.com> ha escrito:
> >>>
> >>>
> >>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> =
wrote:
> >>>
> >>> Question 4: Is TCM-TF interesting for the Industry? Should the =
IETF
> >>> standardize this?
> >>>
> >>> Answer:
> >>>
> >>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP
traffic.
> >>> So if RFC4170 was interesting, why not updating it?
> >>>
> >>> 2) TCM-TF can be useful in order to save bandwidth in many cases:
> >>>
> >>> - Aggregation network of *network operators*: We are saving
> >>> bandwidth by optimizing and putting together traffic flows. Is =
this
> >>> interesting for a network operator? What about overprovisioning?
> >>> The idea is that there are places and moments in which a number of
> >>> flows based on small packets are in the same place and at the same
> >>> moment. Then, TCM-TF can be applied in order to provide =
flexibility.
> >>> We are not optimizing the overall Internet traffic, we are
> >>> optimizing specific flows with very tight delay requirements, =
which
> >>> network operators have to take care of in a special way.
> >>> www.huawei.com/ilink/en/download/HW_193034
> >>>
> >>> - *End to end* optimization: Nowadays, many appliances are used to
> >>> connect remote offices of the same company (creating a VPN). So if =
a
> >>> tunnel exists, why not optimizing this traffic when possible? We
> >>> would save bandwidth in the access network, where it can be =
scarce.
> >>>
> >>> - Wireless and satellite scenarios.
> >>>
> >>> "Cisco adds IP multiplexing to mobile satellite package", April
> >>> 2012,
> >>> http://www.networkworld.com/news/2012/040912-cisco-ip-
> multiplexing-
> >> 258082.html
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Any other thoughts? Any other scenarios in mind? Potential
> >>> beneficiaries?
> >>>
> >>> Some networks, today, use cRTP (RFC2508) on their access links.   =
This
> >>> gives bandwidth savings on the access link, but consumes
> >>> considerable CPU horsepower on the aggregation router (to perform
> cRTP), but
> >>> provides no bandwidth savings across the network core.   If, =
instead,
> >>> the bandwidth could be saved on the access link, across  the core,
> >>> and on the far-end access link -- all without the CPU  impact on =
the
> >>> aggregation router -- it is a considerable win.
> >>>
> >>> -d
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Jose
> >>>
> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> nombre
> >>> de Jose Saldana Enviado el: lunes, 24 de junio de 2013 13:00
> >>> Para: tcmtf@ietf.org
> >>> Asunto: [tcmtf] Answers to possible questions in the BOF
> >>>
> >>> I would like to start a thread about possible questions people may
> >>> ask in the BOF. Obviously, we also need answers, so we should
> cooperate.
> >>>
> >>> This is different from the "questions to ask in the BOF". This =
will
> >>> be discussed separately.
> >>>
> >>> Thanks!
> >>>
> >>> Jose
> >>>
> >>> _______________________________________________
> >>> 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
> >
> > _______________________________________________
> > tcmtf mailing list
> > tcmtf@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcmtf
>=20
>=20
> --
> "Esta vez no fallaremos, Doctor Infierno"
>=20
> Dr Diego R. Lopez
> Telefonica I+D
> http://people.tid.es/diego.lopez/
>=20
> e-mail: diego@tid.es
> Tel:    +34 913 129 041
> Mobile: +34 682 051 091
> -----------------------------------------
>=20
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar
> nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en =
el enlace
> situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send =
and
> receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From gorry@erg.abdn.ac.uk  Tue Jul  9 03:55:53 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 B9B4621F9CC2 for <tcmtf@ietfa.amsl.com>; Tue,  9 Jul 2013 03:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 8mQCBWL3KXgw for <tcmtf@ietfa.amsl.com>; Tue,  9 Jul 2013 03:55:49 -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 1F07321F9AAF for <tcmtf@ietf.org>; Tue,  9 Jul 2013 03:55:47 -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 117BA2B4250; Tue,  9 Jul 2013 11:55:46 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Tue, 9 Jul 2013 11:55:46 +0100
Message-ID: <408173bf1a2c57640e76ca5e8808a01b.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <00b001ce7c91$1dcc6640$596532c0$@unizar.es>
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>" <20130628105725.lmag0xgqsgogggww@webmail.unizar.es> <004601ce7bac$c8fc91b0$5af5b510$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CD0C7F1@EX10-MB2-MAD.hi.inet> <00b001ce7c91$1dcc6640$596532c0$@unizar.es>
Date: Tue, 9 Jul 2013 11:55:46 +0100
From: gorry@erg.abdn.ac.uk
To: jsaldana@unizar.es
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
Cc: tcmtf@ietf.org, "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>, "'Diego R. Lopez'" <diego@tid.es>, 'jsalazar' <jsalazar@unizar.es>, 'Dan Wing' <dwing@cisco.com>
Subject: Re: [tcmtf] Answers to possible questions in 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, 09 Jul 2013 10:55:53 -0000

A few comments on the security considerations.

Can you also please add the counter-argument to using IPsec?

- This use of IPsec protects the packets only within the transport network
between tunnel ingress and egress and therefore does not provide
end-to-end authentication or encryption. In some cases , e.g. where the
end points are trusted this model may be appropriate.

- On the second point, please clarify:
-- which headers are compressed?
-- does this change the end-to-end security model (I think not).

I suggest you quote RFCs for the security mechanisms that you discuss.

Finally, you may like to consider DoS attacks against TCMTF. Transport
groups are usually required to consider whether the mechanisms can be
exploited to generate traffic that does not respond to congestion control
or can be used to amplify the attack on network infrastructure. If you can
comment on these that would seem good - I suggest you should note this as
future work in later revisions of the draft.

Gorry


> Hi all,
>
> I am finishing the next version of the draft. In the "security
> considerations" section in the end. The idea is talking about the two
> options (as summarized by Diego):
>
> - Securing the application of TCMTF itself
> - Applying TCMTF to enhance (or provide a better support to) security
> network services, like IPsec or VPNs
>
> So I would include these two paragraphs, if you agree:
>
>
> The most straightforward option for securing a number of non-secured flows
> sharing a path is by the use of IPsec [IPsec], when TCM using an IP tunnel
> is employed. Instead of adding a security header to the packets of each
> native flow, and then compressing and multiplexing, a single IPsec tunnel
> can be used in order to secure all the flows together, thus achieving a
> better efficiency.
>
> When a number of already secured flows including ESP headers is optimized
> by
> means of TCM, and the addition of further security is not necessary, their
> ESP headers can still be compressed using suitable algorithms, in order to
> improve the efficiency.
>
>
> Any improvements? Any other ideas?
>
> Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Diego R. Lopez
>> Enviado el: lunes, 08 de julio de 2013 11:59
>> Para: <jsaldana@unizar.es>
>> CC: <tcmtf@ietf.org>; Muthu Arul Mozhi Perumal (mperumal); jsalazar; Dan
>> Wing
>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>>
>> Hi,
>>
>> When talking about security, we should not forget two different aspects:
>>
>> 1) Applying TCMTF to enhance (or provide a better support to) security
>> network services, like IPsec or VPNs
>>
>> 2) Securing the application of TCMTF itself
>>
>> As far as I can tell, most of the discussion so far has been on the
>> first
> aspect.
>> This could be outlined as an use case, and further discussed in a
>> separate
>> document if required, oriented towards "Applying TCMTF in secure
>> environments" or the like
>>
>> Regarding the second issue, I tried to make a few points some time ago:
>>
>> 8<---
>>
>> > We can consider different security contexts for different tunnels,
> according
>> to some policy agreed by both end-points at a given tunnel. The security
>> contexts would define encryption, authentication, or both. We'd have to
>> go
>> into more detail to evaluate potential savings, but I have the feeling
> they
>> could be worth considering.
>> >
>> > The point is that if we go for these different security contexts, we
> must
>> consider how they can be established by mutual authentication of the
> tunnel
>> end-points, and this opens additional issues regarding configuration and
>> crypto material exchange, as well as the possibility of user-initiated
>> authentication by means of protocols like OAuth.
>> >
>> > I'd keep this in the list of the "soon-to-open" issues, focusing on
>> the
> three
>> main docs we have been discussing so far.
>>
>> 8<---
>>
>> I had the intention to elaborate them a little more, but other matters
> pre-
>> empted this :-( My take is that some reflections on this should be
> included in
>> the "Security Considerations" section of the framework document, and a
>> further document on this be considered in a further stage.
>>
>> Be goode,
>>
>> On 8 Jul 2013, at 09:28 , Jose Saldana wrote:
>>
>> > Hi, Muthu, Dan, Jose Luis.
>> >
>> > It seems that we have identified some cases in which different
>> security
>> options are possible. The question here is:
>> >
>> > Can this be issued in the TCMTF main draft (TCMTF Reference Model)?
>> >
>> > Or do you think a TCMTF-security document would be interesting?
>> >
>> > Jose
>> >
>> > -----Mensaje original-----
>> > De: jsalazar [mailto:jsalazar@unizar.es] Enviado el: jueves, 04 de
>> > julio de 2013 19:36
>> > Para: jsaldana@unizar.es
>> > Asunto: RE: [tcmtf] Answers to possible questions in the BOF
>> >
>> > Hi all.
>> > With your last question, you have just hit the bullseye. I think the
>> classification is correct. Cases 1 and 2a are a good way to keep the
>> compromise between security and efficency. However, case 2b gives a step
>> beyond and the security is compromised in the interest of efficiency.
>> > In that case, users have to trust in tcmtf manager for managing their
>> > privacy also. Then, we will leave the tipical Public Key
>> > Infraestructure
>> > (PKI) security architecture and use the Identity Based Encryption
>> (IBE)
> one
>> (http://tools.ietf.org/html/rfc5408).
>> > They are three different scenarios and all of them seem to be very
>> interesting, but the last one a bit more.
>> > Regards:
>> >
>> > JL
>> >
>> > "I see them falling out the skies like eagles All mirrored glass and
> shattered
>> egos"
>> >
>> > Simple Minds.
>> >
>> > El 2013-07-03 17:58, Jose Saldana escribió:
>> >> Hi, Jose Luis. Good point.
>> >>
>> >> Regarding security, we could establish this classification:
>> >>
>> >> 1- Adding security to TCM: I have a number of non-secured flows
>> >> traveling through a “dangerous” network segment (perhaps a tunnel
>> >> between appliances connecting remote offices of a company), and I
>> >> want not only traffic optimization but also security. In this case, I
>> >> can simply use IPsec on the tunnel.
>> >>
>> >>
>> >> 2- Using TCM for optimizing already secured communications: I have a
>> >> bunch of already secured flows. Which is the best way for tunneling,
>> >> compressing and multiplexing them?
>> >>
>> >> Two subcases:
>> >>
>> >> 2a- I can use TCM normally, but not only compress IP, TCP or UDP
>> >> headers, but also security headers using a header compression method.
>> >> Some possibilities for compressing security headers:
>> >>
>> >> - ROHCoIPsec, RFC5856 (http://tools.ietf.org/html/rfc5856)
>> >> - RFC5225 http://tools.ietf.org/html/rfc5225
>> >>
>> >>
>> >> 2b- But I can save more bandwidth if the TCM-ingress optimizer
>> >> (TCM-IO) is able to:
>> >> - rebuild the packets to their native form
>> >> - TCM-optimize them
>> >> - put them into a single security tunnel
>> >>
>> >> I have three phases (let's suppose I have 20 communications):
>> >>
>> >> Origin 1
>> >> Origin 2     <----20 secured flows --------> TCM-IO <------1
>> >> tunnel------> TCM-EO <-------- 20 secured flows----> destination 1,
>> >> tunnel------> 2,
>> >> 20
>> >> ...
>> >> Origin 20
>> >>
>> >> I have an advantage: In the shared network path, I use a single
>> >> tunnel instead of 20 different tunnels.
>> >>
>> >> But I have some additional requirements: I need processing capacity
>> >> in the TCM optimizers, and the endpoints should trust them.
>> >>
>> >>
>> >> Is this classification correct? Any other options? Any other
>> >> requirements? It is time for "security experts".
>> >>
>> >> Jose
>> >>
>> >> -----Mensaje original-----
>> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>> >> de jsalazar Enviado el: lunes, 01 de julio de 2013 20:50
>> >> Para: tcmtf@ietf.org
>> >> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>> >>
>> >> Hi all:
>> >> Mmmmmmm. Since I see tcm-tf as a service, I can design the service
>> >> with added security features that the type of communication is
>> >> requiring. I think we have to be clear what we are expressing when we
>> >> are talking about secure tcm-tf: Ensuring the service tcm-tf or
>> >> applying the tcm-tf service for secure communications.
>> >> The first possibility is not a great technological sophistication and
>> >> the second one might consider the first one as a possible additional
>> >> service.
>> >> Therefore,
>> >> every time we use the term "secure tcm-tf" should think the second
>> >> option, for generality.
>> >> On the other hand, we must also keep in mind that whenever users
>> >> employ secure tcm-tf, they must trust the service fully and consider
>> >> delegating the use of their keys (including private ones) to tcm-tf.
>> >>
>> >> Regards.
>> >>
>> >> JL
>> >>
>> >> "I see them falling out the skies like eagles All mirrored glass and
>> >> shattered egos"
>> >>
>> >> Simple Minds.
>> >>
>> >> El 2013-07-01 18:55, Dan Wing escribió:
>> >>> On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
>> >>>
>> >>> Hi all,
>> >>>
>> >>> Few days ago Julian talked about TCM-TF's security and now I've read
>> >>> in the link included by Dan, saying that the gain obtained when
>> >>> multiplexing Ipsec-encrypted packets is 20-to-1. We have been
>> >>> looking for more information about this issue and thinking about a
>> >>> way to reduce the needed  bandwidth in IPsec flows.
>> >>>
>> >>> The main idea is to find a way to change the authentication of the
>> >>> individual packets and merge all of them in a unique authentication.
>> >>> Thus, instead of using 20 IPsec tunnels, we would have a single
>> >>> tunnel including 20 flows. Is this something similar than how Cisco
>> >>> gets the improvement?
>> >>>
>> >>> We would not be able to change IPsec any more than we could change
>> >>> TCP, so I would not look at how to change IPsec authentication.
>> >>>
>> >>> However, if there are a bunch of IPsec packets sharing a common
>> >>> path, I could see them being successfully multiplexed into one
>> >>> larger packet at one tunnel endpoint and then de-multiplexed at the
>> >>> other tunnel endpoint.  This can provide a packet per second
>> >>> reduction.  I don't think there are enough bytes in an IPsec header
>> >>> to bother trying to do IPsec header compression (SPI and sequence
>> number are only 64 bits).
>> >>>
>> >>> -d
>> >>>
>> >>>
>> >>>
>> >>> José Luis
>> >>>
>> >>>
>> >>>
>> >>> Dan Wing <dwing@cisco.com> ha escrito:
>> >>>
>> >>>
>> >>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es>
>> wrote:
>> >>>
>> >>> Question 4: Is TCM-TF interesting for the Industry? Should the IETF
>> >>> standardize this?
>> >>>
>> >>> Answer:
>> >>>
>> >>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP
> traffic.
>> >>> So if RFC4170 was interesting, why not updating it?
>> >>>
>> >>> 2) TCM-TF can be useful in order to save bandwidth in many cases:
>> >>>
>> >>> - Aggregation network of *network operators*: We are saving
>> >>> bandwidth by optimizing and putting together traffic flows. Is this
>> >>> interesting for a network operator? What about overprovisioning?
>> >>> The idea is that there are places and moments in which a number of
>> >>> flows based on small packets are in the same place and at the same
>> >>> moment. Then, TCM-TF can be applied in order to provide flexibility.
>> >>> We are not optimizing the overall Internet traffic, we are
>> >>> optimizing specific flows with very tight delay requirements, which
>> >>> network operators have to take care of in a special way.
>> >>> www.huawei.com/ilink/en/download/HW_193034
>> >>>
>> >>> - *End to end* optimization: Nowadays, many appliances are used to
>> >>> connect remote offices of the same company (creating a VPN). So if a
>> >>> tunnel exists, why not optimizing this traffic when possible? We
>> >>> would save bandwidth in the access network, where it can be scarce.
>> >>>
>> >>> - Wireless and satellite scenarios.
>> >>>
>> >>> "Cisco adds IP multiplexing to mobile satellite package", April
>> >>> 2012,
>> >>> http://www.networkworld.com/news/2012/040912-cisco-ip-
>> multiplexing-
>> >> 258082.html
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> Any other thoughts? Any other scenarios in mind? Potential
>> >>> beneficiaries?
>> >>>
>> >>> Some networks, today, use cRTP (RFC2508) on their access links.
>> This
>> >>> gives bandwidth savings on the access link, but consumes
>> >>> considerable CPU horsepower on the aggregation router (to perform
>> cRTP), but
>> >>> provides no bandwidth savings across the network core.   If,
>> instead,
>> >>> the bandwidth could be saved on the access link, across  the core,
>> >>> and on the far-end access link -- all without the CPU  impact on the
>> >>> aggregation router -- it is a considerable win.
>> >>>
>> >>> -d
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> Jose
>> >>>
>> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> nombre
>> >>> de Jose Saldana Enviado el: lunes, 24 de junio de 2013 13:00
>> >>> Para: tcmtf@ietf.org
>> >>> Asunto: [tcmtf] Answers to possible questions in the BOF
>> >>>
>> >>> I would like to start a thread about possible questions people may
>> >>> ask in the BOF. Obviously, we also need answers, so we should
>> cooperate.
>> >>>
>> >>> This is different from the "questions to ask in the BOF". This will
>> >>> be discussed separately.
>> >>>
>> >>> Thanks!
>> >>>
>> >>> Jose
>> >>>
>> >>> _______________________________________________
>> >>> 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
>> >
>> > _______________________________________________
>> > tcmtf mailing list
>> > tcmtf@ietf.org
>> > https://www.ietf.org/mailman/listinfo/tcmtf
>>
>>
>> --
>> "Esta vez no fallaremos, Doctor Infierno"
>>
>> Dr Diego R. Lopez
>> Telefonica I+D
>> http://people.tid.es/diego.lopez/
>>
>> e-mail: diego@tid.es
>> Tel:    +34 913 129 041
>> Mobile: +34 682 051 091
>> -----------------------------------------
>>
>>
>> ________________________________
>>
>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>> nuestra política de envío y recepción de correo electrónico en el enlace
>> situado más abajo.
>> This message is intended exclusively for its addressee. We only send and
>> receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> _______________________________________________
>> 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 Martin.Stiemerling@neclab.eu  Tue Jul  9 03:56:44 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 5532121F9E8B for <tcmtf@ietfa.amsl.com>; Tue,  9 Jul 2013 03:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.354
X-Spam-Level: 
X-Spam-Status: No, score=-103.354 tagged_above=-999 required=5 tests=[AWL=0.245, 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 ejxzY65Wgho0 for <tcmtf@ietfa.amsl.com>; Tue,  9 Jul 2013 03:56:39 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 18B7821F9AAF for <tcmtf@ietf.org>; Tue,  9 Jul 2013 03:56:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 56FCC1048FC; Tue,  9 Jul 2013 12:56:06 +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 vvGNldm5jkvF; Tue,  9 Jul 2013 12:56:06 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 3EAD0104A17; Tue,  9 Jul 2013 12:55:51 +0200 (CEST)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 9 Jul 2013 12:56:23 +0200
Message-ID: <51DBEC56.6030207@neclab.eu>
Date: Tue, 9 Jul 2013 12:56:22 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: "tcmtf@ietf.org" <tcmtf@ietf.org>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>,  Janardhan Iyengar <janardhan.iyengar@fandm.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Subject: [tcmtf] TCMTF BoF co-chairs
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, 09 Jul 2013 10:56:44 -0000

Dear all,

It has been a long wait and here are the two co-chairs for the TCMTF BOF 
(in CC of this email):

Gorry Fairhurst (gorry@erg.abdn.ac.uk) and Janardhan Iyengar 
(janardhan.iyengar@fandm.edu)

Thanks to Gorry and Jana for chairing the BOF

   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 spencerdawkins.ietf@gmail.com  Tue Jul  9 13:48:01 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 D6D8D21F9D8A for <tcmtf@ietfa.amsl.com>; Tue,  9 Jul 2013 13:48:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level: 
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[AWL=0.077,  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 HV1wol8r2e0T for <tcmtf@ietfa.amsl.com>; Tue,  9 Jul 2013 13:48:01 -0700 (PDT)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 6C6A121F9D82 for <tcmtf@ietf.org>; Tue,  9 Jul 2013 13:48:01 -0700 (PDT)
Received: by mail-oa0-f49.google.com with SMTP id n9so8530292oag.36 for <tcmtf@ietf.org>; Tue, 09 Jul 2013 13:48:01 -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=KvmNmn9jmjnkO5QEJfuXum6wxImAohl6kllizZ1CkUk=; b=PbYaBZVkaKjFrXNq8CK2hUrkK3MCdtc+39D1L1JfaC97FDYFdf7p5+a/EgthZP1Lkb kqu25x9s/ASY12L57g8PNXCwQfqj1BUTdHMM/I/kALnqbFpVrj71NQzHMcnoaik0XLHZ qgjzg21UTLbU9QX0pyfY3Y5ZAsbQ2335QauEkFpwapDwQI3nf/VNJMDaCnSnFsFIg2wB KZhuZtheH8mQCdTSintmYLgogjMtfaUKCXCZ5jVsYswK1oSSx5fLl4FN9lKBek74tZmG SwTBNWj4I3BRAM57LXsOcJTLTiNbXn1OS2gdJ55tgiF6h8jQO8oiB7Yo5QhgnS4DJxnf V99Q==
X-Received: by 10.182.112.166 with SMTP id ir6mr15680655obb.25.1373402881027;  Tue, 09 Jul 2013 13:48:01 -0700 (PDT)
Received: from [192.168.1.77] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net. [99.108.174.213]) by mx.google.com with ESMTPSA id i9sm40716757oem.7.2013.07.09.13.47.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Jul 2013 13:48:00 -0700 (PDT)
Message-ID: <51DC76DD.40002@gmail.com>
Date: Tue, 09 Jul 2013 15:47:25 -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: Gorry Fairhurst <gorry@erg.abdn.ac.uk>,  Janardhan Iyengar <janardhan.iyengar@fandm.edu>
References: <51DBEC56.6030207@neclab.eu>
In-Reply-To: <51DBEC56.6030207@neclab.eu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, Martin Stiemerling <martin.stiemerling@neclab.eu>
Subject: Re: [tcmtf] TCMTF BoF co-chairs
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, 09 Jul 2013 20:48:02 -0000

On 7/9/2013 5:56 AM, Martin Stiemerling wrote:
> Dear all,
>
> It has been a long wait and here are the two co-chairs for the TCMTF 
> BOF (in CC of this email):
>
> Gorry Fairhurst (gorry@erg.abdn.ac.uk) and Janardhan Iyengar 
> (janardhan.iyengar@fandm.edu)
>
> Thanks to Gorry and Jana for chairing the BOF

Just to echo Martin's thanks ... thanks!

Spencer

>   Martin
>


From jsaldana@unizar.es  Wed Jul 10 00:50:53 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 AE4EE21F9BCB for <tcmtf@ietfa.amsl.com>; Wed, 10 Jul 2013 00:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.268
X-Spam-Level: 
X-Spam-Status: No, score=-6.268 tagged_above=-999 required=5 tests=[AWL=0.331,  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 m7ua92MocqA5 for <tcmtf@ietfa.amsl.com>; Wed, 10 Jul 2013 00:50:49 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 01DA521F9BA8 for <tcmtf@ietf.org>; Wed, 10 Jul 2013 00:50:48 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r6A7oYM8021190; Wed, 10 Jul 2013 09:50:35 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>, "'Dan Wing \(dwing\)'" <dwing@cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>	<009901ce725a$d1623360$74269a20$@unizar.es>	<2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>	<20130628105725.lmag0xgqsgogggww@webmail.unizar.es>	<EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com>	<E721D8C6A2E1544DB2DEBC313AF54DE22417E050@xmb-rcd-x02.cisco.com>	<23E6BFC1-4D3C-48A5-A9A2-3BD32863F9A6@cisco.com> <E721D8C6A2E1544DB2DEBC313AF54DE22417FD51@xmb-rcd-x02.cisco.com>
In-Reply-To: <E721D8C6A2E1544DB2DEBC313AF54DE22417FD51@xmb-rcd-x02.cisco.com>
Date: Wed, 10 Jul 2013 09:50:37 +0200
Organization: Universidad de Zaragoza
Message-ID: <007901ce7d42$2d49fc20$87ddf460$@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: AQHxl5HfJe4XxEPJrqhURPk2/vEH5gJG8kQSAT8jBAUB238Z4AIljoQ2An0f44UBvevVIgGBEpi6mK06z0A=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, jltornos@unizar.es
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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: Wed, 10 Jul 2013 07:50:53 -0000

Muthu,

But in this case you have two security layers: the original flows use =
IPsec,
and you are adding another IPsec tunnel including all the compressed =
ones.
Am I right? Would this be necessary?

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Muthu Arul Mozhi Perumal (mperumal)
> Enviado el: jueves, 04 de julio de 2013 15:42
> Para: Dan Wing (dwing)
> CC: tcmtf@ietf.org; jltornos@unizar.es; jsaldana@unizar.es
> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>=20
> |My read of it was:  apply ROHC at the endpoint ("inner headers") and
> |then do IPsec.  That is, compress and then encrypt.
>=20
> Right, Dan. I was thinking the (inner) headers of the packets going =
over
the
> same IPSec tunnel could first be compressed, multiplex, then encrypted =
and
> sent over that tunnel:
>=20
> --------------------------------------------
> |outer IP hdr| ESP | MUX | ROHCoIPsec|Data1|
> |            |     | hdr |   hdr1    |     |
> --------------------------------------------
>                           ----------------------
>                           | ROHCoIPsec | Data2 |
>                           |    hdr2    |       |
>                           ----------------------
>                           -------------------------------------
>                           | ROHCoIPsec |  Data3  | ESP   | ESP|
>                           |    hdr3    |         |Trailer| ICV|
>                           -------------------------------------
>                     <-----------Encrypted-------->
>=20
> Muthu
>=20
> |-----Original Message-----
> |From: Dan Wing (dwing)
> |Sent: Thursday, July 04, 2013 12:26 AM
> |To: Muthu Arul Mozhi Perumal (mperumal)
> |Cc: jltornos@unizar.es; tcmtf@ietf.org; jsaldana@unizar.es
> |Subject: Re: [tcmtf] Answers to possible questions in the BOF
> |
> |
> |On Jul 3, 2013, at 11:51 AM, Muthu Arul Mozhi Perumal (mperumal)
> <mperumal@cisco.com> wrote:
> |
> |> |However, if there are a bunch of IPsec packets sharing a common
> |> |path, I could see them being successfully multiplexed into one
> |> |larger packet at one tunnel endpoint and then de-multiplexed at =
the
> other tunnel endpoint.
> |> |This can provide a packet per second reduction.  I don't think =
there
> |> |are enough bytes in an IPsec header to bother trying to do IPsec
> |> |header compression (SPI and sequence number are only 64 bits).
> |>
> |> Actually, RFC5856 describes how ROHC can be used over IPSec
> (ROHCoIPsec).
> |
> |My read of it was:  apply ROHC at the endpoint ("inner headers") and
> |then do IPsec.  That is, compress and then encrypt.
> |
> |-d
> |
> |
> |> Combining it with multiplexing the entire packets could provide
> |> significant reduction in the header
> |overhead, especially for IPv6, I think.
> |>
> |> Muthu
> |>
> |> |-----Original Message-----
> |> |From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
> |> |Behalf Of Dan Wing (dwing)
> |> |Sent: Monday, July 01, 2013 10:25 PM
> |> |To: jltornos@unizar.es
> |> |Cc: tcmtf@ietf.org; jsaldana@unizar.es
> |> |Subject: Re: [tcmtf] Answers to possible questions in the BOF
> |> |
> |> |
> |> |On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
> |> |
> |> |> Hi all,
> |> |>
> |> |> Few days ago Julian talked about TCM-TF's security and now I've
> |> |> read in the link included by Dan,
> |> |saying that the gain obtained when multiplexing Ipsec-encrypted
> |> |packets is 20-to-1. We have been looking for more information =
about
> |> |this issue and thinking about a way to reduce the needed
> |bandwidth
> |> |in IPsec flows.
> |> |>
> |> |> The main idea is to find a way to change the authentication of =
the
> |> |> individual packets and merge
> |all
> |> |of them in a unique authentication. Thus, instead of using 20 =
IPsec
> |> |tunnels, we would have a single tunnel including 20 flows. Is this
> something similar than how Cisco gets the improvement?
> |> |
> |> |We would not be able to change IPsec any more than we could change
> |> |TCP, so I would not look at how
> |to
> |> |change IPsec authentication.
> |> |
> |> |However, if there are a bunch of IPsec packets sharing a common
> |> |path, I could see them being successfully multiplexed into one
> |> |larger packet at one tunnel endpoint and then de-multiplexed at
> |the
> |> |other tunnel endpoint.  This can provide a packet per second
> |> |reduction.  I don't think there are enough bytes in an IPsec =
header
> |> |to bother trying to do IPsec header compression (SPI and sequence
> number are only 64 bits).
> |> |
> |> |-d
> |> |
> |> |
> |> |>
> |> |> Jos=E9 Luis
> |> |>
> |> |>
> |> |>
> |> |> Dan Wing <dwing@cisco.com> ha escrito:
> |> |>
> |> |>>
> |> |>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es>
> wrote:
> |> |>>
> |> |>>> Question 4: Is TCM-TF interesting for the Industry? Should the
IETF
> standardize this?
> |> |>>>
> |> |>>> Answer:
> |> |>>>
> |> |>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP
> |> |>>> traffic. So if RFC4170 was
> |> |interesting, why not updating it?
> |> |>>>
> |> |>>> 2) TCM-TF can be useful in order to save bandwidth in many =
cases:
> |> |>>>
> |> |>>> - Aggregation network of *network operators*: We are saving
> |> |>>> bandwidth by optimizing and
> |putting
> |> |together traffic flows. Is this  interesting for a network =
operator?
What
> about overprovisioning?
> |The
> |> |idea is that there are places and moments in which a number of
> |> |flows based on small packets are in the same place and at the same
> |> |moment. Then, TCM-TF can be applied in order to provide
> |flexibility.
> |> |We are not optimizing the overall Internet traffic, we  are
> |> |optimizing specific flows with very
> |tight
> |> |delay requirements,  which network operators have to take care of =
in a
> special way.
> |> |>>> www.huawei.com/ilink/en/download/HW_193034
> |> |>>>
> |> |>>> - *End to end* optimization: Nowadays, many appliances are =
used
> |> |>>> to  connect remote offices of
> |the
> |> |same company (creating a VPN). So if  a tunnel exists, why not
> |> |optimizing this traffic when
> |possible?
> |> |We  would save bandwidth in the access network, where it can be
> scarce.
> |> |>>>
> |> |>>> - Wireless and satellite scenarios.
> |> |>>
> |> |>> "Cisco adds IP multiplexing to mobile satellite package", April
> |> |>> 2012,
> |> |http://www.networkworld.com/news/2012/040912-cisco-ip-
> multiplexing-2
> |> |58082.html
> |> |>>
> |> |>>
> |> |>>
> |> |>>>
> |> |>>>
> |> |>>> Any other thoughts? Any other scenarios in mind? Potential
> beneficiaries?
> |> |>>
> |> |>> Some networks, today, use cRTP (RFC2508) on their access links.
This
> gives bandwidth savings
> |on
> |> |the access link, but consumes  considerable CPU horsepower on the
> aggregation router (to perform
> |> |cRTP), but provides no bandwidth savings across the network core.
If,
> instead, the bandwidth
> |could
> |> |be saved on the access link, across  the core, and on the far-end
> |> |access link -- all without the
> |CPU
> |> |impact on the aggregation router -- it is a considerable win.
> |> |>>
> |> |>> -d
> |> |>>
> |> |>>
> |> |>>
> |> |>>>
> |> |>>>
> |> |>>> Jose
> |> |>>>
> |> |>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> |> |>>> nombre de Jose Saldana Enviado el: lunes, 24 de junio de 2013
> |> |>>> 13:00
> |> |>>> Para: tcmtf@ietf.org
> |> |>>> Asunto: [tcmtf] Answers to possible questions in the BOF
> |> |>>>
> |> |>>> I would like to start a thread about possible questions people
> |> |>>> may  ask in the BOF. Obviously,
> |we
> |> |also need answers, so we should  cooperate.
> |> |>>>
> |> |>>> This is different from the "questions to ask in the BOF". This
will  be
> discussed separately.
> |> |>>>
> |> |>>> Thanks!
> |> |>>>
> |> |>>> Jose
> |> |>>>
> |> |>>> _______________________________________________
> |> |>>> 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


From jsaldana@unizar.es  Wed Jul 10 00:51: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 2A89121F9C0A for <tcmtf@ietfa.amsl.com>; Wed, 10 Jul 2013 00:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.285
X-Spam-Level: 
X-Spam-Status: No, score=-6.285 tagged_above=-999 required=5 tests=[AWL=0.314,  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 qebYHIYOM1Zz for <tcmtf@ietfa.amsl.com>; Wed, 10 Jul 2013 00:50:56 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 116B721F9BA8 for <tcmtf@ietf.org>; Wed, 10 Jul 2013 00:50:54 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r6A7oYMA021190; Wed, 10 Jul 2013 09:50:47 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <gorry@erg.abdn.ac.uk>
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>" <20130628105725.lmag0xgqsgogggww@webmail.unizar.es> <004601ce7bac$c8fc91b0$5af5b510$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CD0C7F1@EX10-MB2-MAD.hi.inet> <00b001ce7c91$1dcc6640$596532c0$@unizar.es> <408173bf1a2c57640e76ca5e8808a01b.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <408173bf1a2c57640e76ca5e8808a01b.squirrel@www.erg.abdn.ac.uk>
Date: Wed, 10 Jul 2013 09:50:50 +0200
Organization: Universidad de Zaragoza
Message-ID: <007a01ce7d42$3260a0b0$9721e210$@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: AQHxl5HfJe4XxEPJrqhURPk2/vEH5gJG8kQSAT8jBAUB238Z4AI2LB8yAU3srAwCFm+DUgLcQT0qmKiNLEA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>, "'Diego R. Lopez'" <diego@tid.es>, 'jsalazar' <jsalazar@unizar.es>, 'Dan Wing' <dwing@cisco.com>
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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: Wed, 10 Jul 2013 07:51:07 -0000

What about these "security considerations"? (including Gorry's =
suggestions):

------
The most straightforward option for securing a number of non-secured =
flows
sharing a path is by the use of IPsec [IPsec], when TCM using an IP =
tunnel
is employed. Instead of adding a security header to the packets of each
native flow, and then compressing and multiplexing them, a single IPsec
tunnel can be used in order to secure all the flows together, thus =
achieving
a higher efficiency. This use of IPsec protects the packets only within =
the
transport network between tunnel ingress and egress and therefore does =
not
provide end-to-end authentication or encryption. In some cases , e.g., =
where
the end points are trusted, this model may be appropriate.

When a number of already secured flows including ESP [RFC4303] headers =
are
optimized by means of TCM, and the addition of further security is not
necessary, their ESP/IP headers can still be compressed using suitable
algorithms [RFC5225], in order to improve the efficiency. This header
compression does not change the end-to-end security model.

Future versions of this document will consider whether some TCM-TF
mechanisms could be potentially exploited in order to deploy or amplify =
DoS
attacks against network infrastructure.
-----

Do you think the third paragraph should be included in this version? =
Should
we wait before talking about that?

Thanks, Gorry,

Jose

> -----Mensaje original-----
> De: gorry@erg.abdn.ac.uk [mailto:gorry@erg.abdn.ac.uk]
> Enviado el: martes, 09 de julio de 2013 12:56
> Para: jsaldana@unizar.es
> CC: 'Diego R. Lopez'; tcmtf@ietf.org; 'Muthu Arul Mozhi Perumal
> (mperumal)'; 'jsalazar'; 'Dan Wing'
> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>=20
> A few comments on the security considerations.
>=20
> Can you also please add the counter-argument to using IPsec?
>=20
> - This use of IPsec protects the packets only within the transport =
network
> between tunnel ingress and egress and therefore does not provide =
end-to-
> end authentication or encryption. In some cases , e.g. where the end
points
> are trusted this model may be appropriate.
>=20
> - On the second point, please clarify:
> -- which headers are compressed?
> -- does this change the end-to-end security model (I think not).
>=20
> I suggest you quote RFCs for the security mechanisms that you discuss.
>=20
> Finally, you may like to consider DoS attacks against TCMTF. Transport
groups
> are usually required to consider whether the mechanisms can be =
exploited
> to generate traffic that does not respond to congestion control or can =
be
> used to amplify the attack on network infrastructure. If you can =
comment
on
> these that would seem good - I suggest you should note this as future =
work
> in later revisions of the draft.
>=20
> Gorry
>=20
>=20
> > Hi all,
> >
> > I am finishing the next version of the draft. In the "security
> > considerations" section in the end. The idea is talking about the =
two
> > options (as summarized by Diego):
> >
> > - Securing the application of TCMTF itself
> > - Applying TCMTF to enhance (or provide a better support to) =
security
> > network services, like IPsec or VPNs
> >
> > So I would include these two paragraphs, if you agree:
> >
> >
> > The most straightforward option for securing a number of non-secured
> > flows sharing a path is by the use of IPsec [IPsec], when TCM using =
an
> > IP tunnel is employed. Instead of adding a security header to the
> > packets of each native flow, and then compressing and multiplexing, =
a
> > single IPsec tunnel can be used in order to secure all the flows
> > together, thus achieving a better efficiency.
> >
> > When a number of already secured flows including ESP headers is
> > optimized by means of TCM, and the addition of further security is =
not
> > necessary, their ESP headers can still be compressed using suitable
> > algorithms, in order to improve the efficiency.
> >
> >
> > Any improvements? Any other ideas?
> >
> > Jose
> >
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> >> de Diego R. Lopez Enviado el: lunes, 08 de julio de 2013 11:59
> >> Para: <jsaldana@unizar.es>
> >> CC: <tcmtf@ietf.org>; Muthu Arul Mozhi Perumal (mperumal); =
jsalazar;
> >> Dan Wing
> >> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
> >>
> >> Hi,
> >>
> >> When talking about security, we should not forget two different
aspects:
> >>
> >> 1) Applying TCMTF to enhance (or provide a better support to)
> >> security network services, like IPsec or VPNs
> >>
> >> 2) Securing the application of TCMTF itself
> >>
> >> As far as I can tell, most of the discussion so far has been on the
> >> first
> > aspect.
> >> This could be outlined as an use case, and further discussed in a
> >> separate document if required, oriented towards "Applying TCMTF in
> >> secure environments" or the like
> >>
> >> Regarding the second issue, I tried to make a few points some time =
ago:
> >>
> >> 8<---
> >>
> >> > We can consider different security contexts for different =
tunnels,
> > according
> >> to some policy agreed by both end-points at a given tunnel. The
> >> security contexts would define encryption, authentication, or both.
> >> We'd have to go into more detail to evaluate potential savings, but =
I
> >> have the feeling
> > they
> >> could be worth considering.
> >> >
> >> > The point is that if we go for these different security contexts,
> >> > we
> > must
> >> consider how they can be established by mutual authentication of =
the
> > tunnel
> >> end-points, and this opens additional issues regarding =
configuration
> >> and crypto material exchange, as well as the possibility of
> >> user-initiated authentication by means of protocols like OAuth.
> >> >
> >> > I'd keep this in the list of the "soon-to-open" issues, focusing =
on
> >> the
> > three
> >> main docs we have been discussing so far.
> >>
> >> 8<---
> >>
> >> I had the intention to elaborate them a little more, but other
> >> matters
> > pre-
> >> empted this :-( My take is that some reflections on this should be
> > included in
> >> the "Security Considerations" section of the framework document, =
and
> >> a further document on this be considered in a further stage.
> >>
> >> Be goode,
> >>
> >> On 8 Jul 2013, at 09:28 , Jose Saldana wrote:
> >>
> >> > Hi, Muthu, Dan, Jose Luis.
> >> >
> >> > It seems that we have identified some cases in which different
> >> security
> >> options are possible. The question here is:
> >> >
> >> > Can this be issued in the TCMTF main draft (TCMTF Reference =
Model)?
> >> >
> >> > Or do you think a TCMTF-security document would be interesting?
> >> >
> >> > Jose
> >> >
> >> > -----Mensaje original-----
> >> > De: jsalazar [mailto:jsalazar@unizar.es] Enviado el: jueves, 04 =
de
> >> > julio de 2013 19:36
> >> > Para: jsaldana@unizar.es
> >> > Asunto: RE: [tcmtf] Answers to possible questions in the BOF
> >> >
> >> > Hi all.
> >> > With your last question, you have just hit the bullseye. I think
> >> > the
> >> classification is correct. Cases 1 and 2a are a good way to keep =
the
> >> compromise between security and efficency. However, case 2b gives a
> >> step beyond and the security is compromised in the interest of
efficiency.
> >> > In that case, users have to trust in tcmtf manager for managing
> >> > their privacy also. Then, we will leave the tipical Public Key
> >> > Infraestructure
> >> > (PKI) security architecture and use the Identity Based Encryption
> >> (IBE)
> > one
> >> (http://tools.ietf.org/html/rfc5408).
> >> > They are three different scenarios and all of them seem to be =
very
> >> interesting, but the last one a bit more.
> >> > Regards:
> >> >
> >> > JL
> >> >
> >> > "I see them falling out the skies like eagles All mirrored glass
> >> > and
> > shattered
> >> egos"
> >> >
> >> > Simple Minds.
> >> >
> >> > El 2013-07-03 17:58, Jose Saldana escribi=F3:
> >> >> Hi, Jose Luis. Good point.
> >> >>
> >> >> Regarding security, we could establish this classification:
> >> >>
> >> >> 1- Adding security to TCM: I have a number of non-secured flows
> >> >> traveling through a =93dangerous=94 network segment (perhaps a =
tunnel
> >> >> between appliances connecting remote offices of a company), and =
I
> >> >> want not only traffic optimization but also security. In this
> >> >> case, I can simply use IPsec on the tunnel.
> >> >>
> >> >>
> >> >> 2- Using TCM for optimizing already secured communications: I =
have
> >> >> a bunch of already secured flows. Which is the best way for
> >> >> tunneling, compressing and multiplexing them?
> >> >>
> >> >> Two subcases:
> >> >>
> >> >> 2a- I can use TCM normally, but not only compress IP, TCP or UDP
> >> >> headers, but also security headers using a header compression
> method.
> >> >> Some possibilities for compressing security headers:
> >> >>
> >> >> - ROHCoIPsec, RFC5856 (http://tools.ietf.org/html/rfc5856)
> >> >> - RFC5225 http://tools.ietf.org/html/rfc5225
> >> >>
> >> >>
> >> >> 2b- But I can save more bandwidth if the TCM-ingress optimizer
> >> >> (TCM-IO) is able to:
> >> >> - rebuild the packets to their native form
> >> >> - TCM-optimize them
> >> >> - put them into a single security tunnel
> >> >>
> >> >> I have three phases (let's suppose I have 20 communications):
> >> >>
> >> >> Origin 1
> >> >> Origin 2     <----20 secured flows --------> TCM-IO <------1
> >> >> tunnel------> TCM-EO <-------- 20 secured flows----> destination
> >> >> tunnel------> 1, 2,
> >> >> 20
> >> >> ...
> >> >> Origin 20
> >> >>
> >> >> I have an advantage: In the shared network path, I use a single
> >> >> tunnel instead of 20 different tunnels.
> >> >>
> >> >> But I have some additional requirements: I need processing
> >> >> capacity in the TCM optimizers, and the endpoints should trust =
them.
> >> >>
> >> >>
> >> >> Is this classification correct? Any other options? Any other
> >> >> requirements? It is time for "security experts".
> >> >>
> >> >> Jose
> >> >>
> >> >> -----Mensaje original-----
> >> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> >> nombre de jsalazar Enviado el: lunes, 01 de julio de 2013 20:50
> >> >> Para: tcmtf@ietf.org
> >> >> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
> >> >>
> >> >> Hi all:
> >> >> Mmmmmmm. Since I see tcm-tf as a service, I can design the =
service
> >> >> with added security features that the type of communication is
> >> >> requiring. I think we have to be clear what we are expressing =
when
> >> >> we are talking about secure tcm-tf: Ensuring the service tcm-tf =
or
> >> >> applying the tcm-tf service for secure communications.
> >> >> The first possibility is not a great technological =
sophistication
> >> >> and the second one might consider the first one as a possible
> >> >> additional service.
> >> >> Therefore,
> >> >> every time we use the term "secure tcm-tf" should think the =
second
> >> >> option, for generality.
> >> >> On the other hand, we must also keep in mind that whenever users
> >> >> employ secure tcm-tf, they must trust the service fully and
> >> >> consider delegating the use of their keys (including private =
ones)
to
> tcm-tf.
> >> >>
> >> >> Regards.
> >> >>
> >> >> JL
> >> >>
> >> >> "I see them falling out the skies like eagles All mirrored glass
> >> >> and shattered egos"
> >> >>
> >> >> Simple Minds.
> >> >>
> >> >> El 2013-07-01 18:55, Dan Wing escribi=F3:
> >> >>> On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
> >> >>>
> >> >>> Hi all,
> >> >>>
> >> >>> Few days ago Julian talked about TCM-TF's security and now I've
> >> >>> read in the link included by Dan, saying that the gain obtained
> >> >>> when multiplexing Ipsec-encrypted packets is 20-to-1. We have
> >> >>> been looking for more information about this issue and thinking
> >> >>> about a way to reduce the needed  bandwidth in IPsec flows.
> >> >>>
> >> >>> The main idea is to find a way to change the authentication of
> >> >>> the individual packets and merge all of them in a unique
> authentication.
> >> >>> Thus, instead of using 20 IPsec tunnels, we would have a single
> >> >>> tunnel including 20 flows. Is this something similar than how
> >> >>> Cisco gets the improvement?
> >> >>>
> >> >>> We would not be able to change IPsec any more than we could
> >> >>> change TCP, so I would not look at how to change IPsec
> authentication.
> >> >>>
> >> >>> However, if there are a bunch of IPsec packets sharing a common
> >> >>> path, I could see them being successfully multiplexed into one
> >> >>> larger packet at one tunnel endpoint and then de-multiplexed at
> >> >>> the other tunnel endpoint.  This can provide a packet per =
second
> >> >>> reduction.  I don't think there are enough bytes in an IPsec
> >> >>> header to bother trying to do IPsec header compression (SPI and
> >> >>> sequence
> >> number are only 64 bits).
> >> >>>
> >> >>> -d
> >> >>>
> >> >>>
> >> >>>
> >> >>> Jos=E9 Luis
> >> >>>
> >> >>>
> >> >>>
> >> >>> Dan Wing <dwing@cisco.com> ha escrito:
> >> >>>
> >> >>>
> >> >>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es>
> >> wrote:
> >> >>>
> >> >>> Question 4: Is TCM-TF interesting for the Industry? Should the
> >> >>> IETF standardize this?
> >> >>>
> >> >>> Answer:
> >> >>>
> >> >>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP
> > traffic.
> >> >>> So if RFC4170 was interesting, why not updating it?
> >> >>>
> >> >>> 2) TCM-TF can be useful in order to save bandwidth in many =
cases:
> >> >>>
> >> >>> - Aggregation network of *network operators*: We are saving
> >> >>> bandwidth by optimizing and putting together traffic flows. Is
> >> >>> this interesting for a network operator? What about
> overprovisioning?
> >> >>> The idea is that there are places and moments in which a number
> >> >>> of flows based on small packets are in the same place and at =
the
> >> >>> same moment. Then, TCM-TF can be applied in order to provide
> flexibility.
> >> >>> We are not optimizing the overall Internet traffic, we are
> >> >>> optimizing specific flows with very tight delay requirements,
> >> >>> which network operators have to take care of in a special way.
> >> >>> www.huawei.com/ilink/en/download/HW_193034
> >> >>>
> >> >>> - *End to end* optimization: Nowadays, many appliances are used
> >> >>> to connect remote offices of the same company (creating a VPN).
> >> >>> So if a tunnel exists, why not optimizing this traffic when
> >> >>> possible? We would save bandwidth in the access network, where =
it
> can be scarce.
> >> >>>
> >> >>> - Wireless and satellite scenarios.
> >> >>>
> >> >>> "Cisco adds IP multiplexing to mobile satellite package", April
> >> >>> 2012,
> >> >>> http://www.networkworld.com/news/2012/040912-cisco-ip-
> >> multiplexing-
> >> >> 258082.html
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> Any other thoughts? Any other scenarios in mind? Potential
> >> >>> beneficiaries?
> >> >>>
> >> >>> Some networks, today, use cRTP (RFC2508) on their access links.
> >> This
> >> >>> gives bandwidth savings on the access link, but consumes
> >> >>> considerable CPU horsepower on the aggregation router (to =
perform
> >> cRTP), but
> >> >>> provides no bandwidth savings across the network core.   If,
> >> instead,
> >> >>> the bandwidth could be saved on the access link, across  the
> >> >>> core, and on the far-end access link -- all without the CPU
> >> >>> impact on the aggregation router -- it is a considerable win.
> >> >>>
> >> >>> -d
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> Jose
> >> >>>
> >> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> nombre
> >> >>> de Jose Saldana Enviado el: lunes, 24 de junio de 2013 13:00
> >> >>> Para: tcmtf@ietf.org
> >> >>> Asunto: [tcmtf] Answers to possible questions in the BOF
> >> >>>
> >> >>> I would like to start a thread about possible questions people
> >> >>> may ask in the BOF. Obviously, we also need answers, so we =
should
> >> cooperate.
> >> >>>
> >> >>> This is different from the "questions to ask in the BOF". This
> >> >>> will be discussed separately.
> >> >>>
> >> >>> Thanks!
> >> >>>
> >> >>> Jose
> >> >>>
> >> >>> _______________________________________________
> >> >>> 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
> >> >
> >> > _______________________________________________
> >> > tcmtf mailing list
> >> > tcmtf@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/tcmtf
> >>
> >>
> >> --
> >> "Esta vez no fallaremos, Doctor Infierno"
> >>
> >> Dr Diego R. Lopez
> >> Telefonica I+D
> >> http://people.tid.es/diego.lopez/
> >>
> >> e-mail: diego@tid.es
> >> Tel:    +34 913 129 041
> >> Mobile: +34 682 051 091
> >> -----------------------------------------
> >>
> >>
> >> ________________________________
> >>
> >> Este mensaje se dirige exclusivamente a su destinatario. Puede
> >> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico
> >> en el enlace situado m=E1s abajo.
> >> This message is intended exclusively for its addressee. We only =
send
> >> and receive email on the basis of the terms set out at:
> >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >> _______________________________________________
> >> 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 mperumal@cisco.com  Wed Jul 10 03:00:49 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 EB0C121F9E27 for <tcmtf@ietfa.amsl.com>; Wed, 10 Jul 2013 03:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.359
X-Spam-Level: 
X-Spam-Status: No, score=-10.359 tagged_above=-999 required=5 tests=[AWL=0.240, 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 lQKZ3BX3KmBa for <tcmtf@ietfa.amsl.com>; Wed, 10 Jul 2013 03:00:45 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id EA67221F9AC2 for <tcmtf@ietf.org>; Wed, 10 Jul 2013 03:00:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9712; q=dns/txt; s=iport; t=1373450445; x=1374660045; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=XFwC59LPVFANx9jcUPbv8Wh2ePHrGRzKJQ6v89h4Ko4=; b=jQUY5pydFSQasUZbHfT5rsR7kzKvTeE6nhupTmW7VTcWUAhuXL6GjNZp 8H5fJJ3yxt3VbC05Pl/UC5+dR/KXIdSNjPHWxR7Oc9kepZazybbNRngSi PakU/KFZykxE+MKki2j3WFoBdUKnTow8O8uqmwEVctvvpyJKzNnJcdhXC g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFAI4v3VGtJV2b/2dsb2JhbABagwkyTcEQgRAWdIIjAQEBBAEBASQiIwIIAwwEAgEIEQQBAQsdBycLFAkIAgQBDQUIEgSHcQy5MI4WgRwxBwaDA2wDiG2LFJUggxGCKA
X-IronPort-AV: E=Sophos;i="4.87,1035,1363132800"; d="scan'208";a="232959628"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-2.cisco.com with ESMTP; 10 Jul 2013 10:00:29 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6AA0TV4003680 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 10 Jul 2013 10:00:29 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.192]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Wed, 10 Jul 2013 05:00:28 -0500
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "Dan Wing (dwing)" <dwing@cisco.com>
Thread-Topic: [tcmtf] Answers to possible questions in the BOF
Thread-Index: AQHOdnvPX00XDi64+EGJAr2DWa8S1ZlTTKXAgABYC4CAAFOdIIAJ8uGA//+13OA=
Date: Wed, 10 Jul 2013 10:00:27 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE224189F5E@xmb-rcd-x02.cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com> <20130628105725.lmag0xgqsgogggww@webmail.unizar.es> <EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com> <E721D8C6A2E1544DB2DEBC313AF54DE22417E050@xmb-rcd-x02.cisco.com> <23E6BFC1-4D3C-48A5-A9A2-3BD32863F9A6@cisco.com> <E721D8C6A2E1544DB2DEBC313AF54DE22417FD51@xmb-rcd-x02.cisco.com> <007901ce7d42$2d49fc20$87ddf460$@unizar.es>
In-Reply-To: <007901ce7d42$2d49fc20$87ddf460$@unizar.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [72.163.211.93]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, "jltornos@unizar.es" <jltornos@unizar.es>
Subject: Re: [tcmtf] Answers to possible questions in 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: Wed, 10 Jul 2013 10:00:50 -0000

Hi Jose,

|But in this case you have two security layers: the original flows use IPse=
c,
|and you are adding another IPsec tunnel including all the compressed ones.

No, just one IPSec tunnel. The idea is to compress the headers of all packe=
ts that need to go over the same IPSec tunnel, multiplex them and give it t=
o the IPSec layer. The IPSec layer would add the IP/ESP header and send it =
over the IPSec tunnel. The next header field in ESP would tell there is a m=
ux header following it, and the mux header can be used to demux the packet =
after IPSec decryption.

Muthu

|-----Original Message-----
|From: Jose Saldana [mailto:jsaldana@unizar.es]
|Sent: Wednesday, July 10, 2013 1:21 PM
|To: Muthu Arul Mozhi Perumal (mperumal); Dan Wing (dwing)
|Cc: tcmtf@ietf.org; jltornos@unizar.es
|Subject: RE: [tcmtf] Answers to possible questions in the BOF
|
|Muthu,
|
|But in this case you have two security layers: the original flows use IPse=
c,
|and you are adding another IPsec tunnel including all the compressed ones.
|Am I right? Would this be necessary?
|
|Jose
|
|> -----Mensaje original-----
|> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
|> Muthu Arul Mozhi Perumal (mperumal)
|> Enviado el: jueves, 04 de julio de 2013 15:42
|> Para: Dan Wing (dwing)
|> CC: tcmtf@ietf.org; jltornos@unizar.es; jsaldana@unizar.es
|> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
|>
|> |My read of it was:  apply ROHC at the endpoint ("inner headers") and
|> |then do IPsec.  That is, compress and then encrypt.
|>
|> Right, Dan. I was thinking the (inner) headers of the packets going over
|the
|> same IPSec tunnel could first be compressed, multiplex, then encrypted a=
nd
|> sent over that tunnel:
|>
|> --------------------------------------------
|> |outer IP hdr| ESP | MUX | ROHCoIPsec|Data1|
|> |            |     | hdr |   hdr1    |     |
|> --------------------------------------------
|>                           ----------------------
|>                           | ROHCoIPsec | Data2 |
|>                           |    hdr2    |       |
|>                           ----------------------
|>                           -------------------------------------
|>                           | ROHCoIPsec |  Data3  | ESP   | ESP|
|>                           |    hdr3    |         |Trailer| ICV|
|>                           -------------------------------------
|>                     <-----------Encrypted-------->
|>
|> Muthu
|>
|> |-----Original Message-----
|> |From: Dan Wing (dwing)
|> |Sent: Thursday, July 04, 2013 12:26 AM
|> |To: Muthu Arul Mozhi Perumal (mperumal)
|> |Cc: jltornos@unizar.es; tcmtf@ietf.org; jsaldana@unizar.es
|> |Subject: Re: [tcmtf] Answers to possible questions in the BOF
|> |
|> |
|> |On Jul 3, 2013, at 11:51 AM, Muthu Arul Mozhi Perumal (mperumal)
|> <mperumal@cisco.com> wrote:
|> |
|> |> |However, if there are a bunch of IPsec packets sharing a common
|> |> |path, I could see them being successfully multiplexed into one
|> |> |larger packet at one tunnel endpoint and then de-multiplexed at the
|> other tunnel endpoint.
|> |> |This can provide a packet per second reduction.  I don't think there
|> |> |are enough bytes in an IPsec header to bother trying to do IPsec
|> |> |header compression (SPI and sequence number are only 64 bits).
|> |>
|> |> Actually, RFC5856 describes how ROHC can be used over IPSec
|> (ROHCoIPsec).
|> |
|> |My read of it was:  apply ROHC at the endpoint ("inner headers") and
|> |then do IPsec.  That is, compress and then encrypt.
|> |
|> |-d
|> |
|> |
|> |> Combining it with multiplexing the entire packets could provide
|> |> significant reduction in the header
|> |overhead, especially for IPv6, I think.
|> |>
|> |> Muthu
|> |>
|> |> |-----Original Message-----
|> |> |From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
|> |> |Behalf Of Dan Wing (dwing)
|> |> |Sent: Monday, July 01, 2013 10:25 PM
|> |> |To: jltornos@unizar.es
|> |> |Cc: tcmtf@ietf.org; jsaldana@unizar.es
|> |> |Subject: Re: [tcmtf] Answers to possible questions in the BOF
|> |> |
|> |> |
|> |> |On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
|> |> |
|> |> |> Hi all,
|> |> |>
|> |> |> Few days ago Julian talked about TCM-TF's security and now I've
|> |> |> read in the link included by Dan,
|> |> |saying that the gain obtained when multiplexing Ipsec-encrypted
|> |> |packets is 20-to-1. We have been looking for more information about
|> |> |this issue and thinking about a way to reduce the needed
|> |bandwidth
|> |> |in IPsec flows.
|> |> |>
|> |> |> The main idea is to find a way to change the authentication of the
|> |> |> individual packets and merge
|> |all
|> |> |of them in a unique authentication. Thus, instead of using 20 IPsec
|> |> |tunnels, we would have a single tunnel including 20 flows. Is this
|> something similar than how Cisco gets the improvement?
|> |> |
|> |> |We would not be able to change IPsec any more than we could change
|> |> |TCP, so I would not look at how
|> |to
|> |> |change IPsec authentication.
|> |> |
|> |> |However, if there are a bunch of IPsec packets sharing a common
|> |> |path, I could see them being successfully multiplexed into one
|> |> |larger packet at one tunnel endpoint and then de-multiplexed at
|> |the
|> |> |other tunnel endpoint.  This can provide a packet per second
|> |> |reduction.  I don't think there are enough bytes in an IPsec header
|> |> |to bother trying to do IPsec header compression (SPI and sequence
|> number are only 64 bits).
|> |> |
|> |> |-d
|> |> |
|> |> |
|> |> |>
|> |> |> Jos=E9 Luis
|> |> |>
|> |> |>
|> |> |>
|> |> |> Dan Wing <dwing@cisco.com> ha escrito:
|> |> |>
|> |> |>>
|> |> |>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es>
|> wrote:
|> |> |>>
|> |> |>>> Question 4: Is TCM-TF interesting for the Industry? Should the
|IETF
|> standardize this?
|> |> |>>>
|> |> |>>> Answer:
|> |> |>>>
|> |> |>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP
|> |> |>>> traffic. So if RFC4170 was
|> |> |interesting, why not updating it?
|> |> |>>>
|> |> |>>> 2) TCM-TF can be useful in order to save bandwidth in many cases=
:
|> |> |>>>
|> |> |>>> - Aggregation network of *network operators*: We are saving
|> |> |>>> bandwidth by optimizing and
|> |putting
|> |> |together traffic flows. Is this  interesting for a network operator?
|What
|> about overprovisioning?
|> |The
|> |> |idea is that there are places and moments in which a number of
|> |> |flows based on small packets are in the same place and at the same
|> |> |moment. Then, TCM-TF can be applied in order to provide
|> |flexibility.
|> |> |We are not optimizing the overall Internet traffic, we  are
|> |> |optimizing specific flows with very
|> |tight
|> |> |delay requirements,  which network operators have to take care of in=
 a
|> special way.
|> |> |>>> www.huawei.com/ilink/en/download/HW_193034
|> |> |>>>
|> |> |>>> - *End to end* optimization: Nowadays, many appliances are used
|> |> |>>> to  connect remote offices of
|> |the
|> |> |same company (creating a VPN). So if  a tunnel exists, why not
|> |> |optimizing this traffic when
|> |possible?
|> |> |We  would save bandwidth in the access network, where it can be
|> scarce.
|> |> |>>>
|> |> |>>> - Wireless and satellite scenarios.
|> |> |>>
|> |> |>> "Cisco adds IP multiplexing to mobile satellite package", April
|> |> |>> 2012,
|> |> |http://www.networkworld.com/news/2012/040912-cisco-ip-
|> multiplexing-2
|> |> |58082.html
|> |> |>>
|> |> |>>
|> |> |>>
|> |> |>>>
|> |> |>>>
|> |> |>>> Any other thoughts? Any other scenarios in mind? Potential
|> beneficiaries?
|> |> |>>
|> |> |>> Some networks, today, use cRTP (RFC2508) on their access links.
|This
|> gives bandwidth savings
|> |on
|> |> |the access link, but consumes  considerable CPU horsepower on the
|> aggregation router (to perform
|> |> |cRTP), but provides no bandwidth savings across the network core.
|If,
|> instead, the bandwidth
|> |could
|> |> |be saved on the access link, across  the core, and on the far-end
|> |> |access link -- all without the
|> |CPU
|> |> |impact on the aggregation router -- it is a considerable win.
|> |> |>>
|> |> |>> -d
|> |> |>>
|> |> |>>
|> |> |>>
|> |> |>>>
|> |> |>>>
|> |> |>>> Jose
|> |> |>>>
|> |> |>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
|> |> |>>> nombre de Jose Saldana Enviado el: lunes, 24 de junio de 2013
|> |> |>>> 13:00
|> |> |>>> Para: tcmtf@ietf.org
|> |> |>>> Asunto: [tcmtf] Answers to possible questions in the BOF
|> |> |>>>
|> |> |>>> I would like to start a thread about possible questions people
|> |> |>>> may  ask in the BOF. Obviously,
|> |we
|> |> |also need answers, so we should  cooperate.
|> |> |>>>
|> |> |>>> This is different from the "questions to ask in the BOF". This
|will  be
|> discussed separately.
|> |> |>>>
|> |> |>>> Thanks!
|> |> |>>>
|> |> |>>> Jose
|> |> |>>>
|> |> |>>> _______________________________________________
|> |> |>>> 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  Thu Jul 11 01:44: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 6A98121F9DF2 for <tcmtf@ietfa.amsl.com>; Thu, 11 Jul 2013 01:44:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.3
X-Spam-Level: 
X-Spam-Status: No, score=-6.3 tagged_above=-999 required=5 tests=[AWL=0.300, 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 c1HMSGDBDgqn for <tcmtf@ietfa.amsl.com>; Thu, 11 Jul 2013 01:44:15 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id B08B921F9DB0 for <tcmtf@ietf.org>; Thu, 11 Jul 2013 01:44:14 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r6B8i2w0014434; Thu, 11 Jul 2013 10:44:03 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>, "'Dan Wing \(dwing\)'" <dwing@cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>	<009901ce725a$d1623360$74269a20$@unizar.es>	<2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>	<20130628105725.lmag0xgqsgogggww@webmail.unizar.es>	<EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com>	<E721D8C6A2E1544DB2DEBC313AF54DE22417E050@xmb-rcd-x02.cisco.com>	<23E6BFC1-4D3C-48A5-A9A2-3BD32863F9A6@cisco.com> <E721D8C6A2E1544DB2DEBC313AF54DE22417FD51@xmb-rcd-x02.cisco.com> <007901ce7d42$2d49fc20$87ddf460$@unizar.es> <E721D8C6A2E1544DB2DEBC313AF54DE224189F5E@xmb-rcd-x02.cisco.com>
In-Reply-To: <E721D8C6A2E1544DB2DEBC313AF54DE224189F5E@xmb-rcd-x02.cisco.com>
Date: Thu, 11 Jul 2013 10:44:04 +0200
Organization: Universidad de Zaragoza
Message-ID: <003b01ce7e12$cf140570$6d3c1050$@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: AQHxl5HfJe4XxEPJrqhURPk2/vEH5gJG8kQSAT8jBAUB238Z4AIljoQ2An0f44UBvevVIgGBEpi6Ai84Ev4Bgo8iUpiRTJyg
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, jltornos@unizar.es
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 11 Jul 2013 08:44:19 -0000

Muthu,

So you have a "bunch" of IPsec flows, and you
- decrypt each flow
- compress headers
- multiplex packets
- put the multiplexed bundle in an IPsec packet, using a new IPsec =
tunnel

So you would have three phases:
- separate IPsec tunnels for each flows
- a single IPsec tunnel for the TCM flow
- separate IPsec tunnels in the end

Origin 1
Origin 2     <----20 secured flows --------> TCM-IO <------1 =
tunnel------>
TCM-EO <-------- 20 secured flows----> destination 1, 2, 20
...
Origin 20

But I think this raises a question: the TCM ingress optimizer must be =
able
to decrypt all the flows. This implies that it knows the keys and it is
trusted by the communication ends.

This would be the most efficient solution, but you would need some
requirements:

- trust the TCM optimizer
- processing capacity for decrypt-compress-multiplex-encrypt

Is this what you are thinking?

Jose

> -----Mensaje original-----
> De: Muthu Arul Mozhi Perumal (mperumal) [mailto:mperumal@cisco.com]
> Enviado el: mi=E9rcoles, 10 de julio de 2013 12:00
> Para: jsaldana@unizar.es; Dan Wing (dwing)
> CC: tcmtf@ietf.org; jltornos@unizar.es
> Asunto: RE: [tcmtf] Answers to possible questions in the BOF
>=20
> Hi Jose,
>=20
> |But in this case you have two security layers: the original flows use
> |IPsec, and you are adding another IPsec tunnel including all the
compressed
> ones.
>=20
> No, just one IPSec tunnel. The idea is to compress the headers of all
packets
> that need to go over the same IPSec tunnel, multiplex them and give it =
to
the
> IPSec layer. The IPSec layer would add the IP/ESP header and send it =
over
> the IPSec tunnel. The next header field in ESP would tell there is a =
mux
> header following it, and the mux header can be used to demux the =
packet
> after IPSec decryption.
>=20
> Muthu
>=20
> |-----Original Message-----
> |From: Jose Saldana [mailto:jsaldana@unizar.es]
> |Sent: Wednesday, July 10, 2013 1:21 PM
> |To: Muthu Arul Mozhi Perumal (mperumal); Dan Wing (dwing)
> |Cc: tcmtf@ietf.org; jltornos@unizar.es
> |Subject: RE: [tcmtf] Answers to possible questions in the BOF
> |
> |Muthu,
> |
> |But in this case you have two security layers: the original flows use
> |IPsec, and you are adding another IPsec tunnel including all the
compressed
> ones.
> |Am I right? Would this be necessary?
> |
> |Jose
> |
> |> -----Mensaje original-----
> |> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> |> de Muthu Arul Mozhi Perumal (mperumal) Enviado el: jueves, 04 de
> |> julio de 2013 15:42
> |> Para: Dan Wing (dwing)
> |> CC: tcmtf@ietf.org; jltornos@unizar.es; jsaldana@unizar.es
> |> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
> |>
> |> |My read of it was:  apply ROHC at the endpoint ("inner headers") =
and
> |> |then do IPsec.  That is, compress and then encrypt.
> |>
> |> Right, Dan. I was thinking the (inner) headers of the packets going
> |> over
> |the
> |> same IPSec tunnel could first be compressed, multiplex, then
> |> encrypted and sent over that tunnel:
> |>
> |> --------------------------------------------
> |> |outer IP hdr| ESP | MUX | ROHCoIPsec|Data1|
> |> |            |     | hdr |   hdr1    |     |
> |> --------------------------------------------
> |>                           ----------------------
> |>                           | ROHCoIPsec | Data2 |
> |>                           |    hdr2    |       |
> |>                           ----------------------
> |>                           -------------------------------------
> |>                           | ROHCoIPsec |  Data3  | ESP   | ESP|
> |>                           |    hdr3    |         |Trailer| ICV|
> |>                           -------------------------------------
> |>                     <-----------Encrypted-------->
> |>
> |> Muthu
> |>
> |> |-----Original Message-----
> |> |From: Dan Wing (dwing)
> |> |Sent: Thursday, July 04, 2013 12:26 AM
> |> |To: Muthu Arul Mozhi Perumal (mperumal)
> |> |Cc: jltornos@unizar.es; tcmtf@ietf.org; jsaldana@unizar.es
> |> |Subject: Re: [tcmtf] Answers to possible questions in the BOF
> |> |
> |> |
> |> |On Jul 3, 2013, at 11:51 AM, Muthu Arul Mozhi Perumal (mperumal)
> |> <mperumal@cisco.com> wrote:
> |> |
> |> |> |However, if there are a bunch of IPsec packets sharing a common
> |> |> |path, I could see them being successfully multiplexed into one
> |> |> |larger packet at one tunnel endpoint and then de-multiplexed at
> |> |> |the
> |> other tunnel endpoint.
> |> |> |This can provide a packet per second reduction.  I don't think
> |> |> |there are enough bytes in an IPsec header to bother trying to =
do
> |> |> |IPsec header compression (SPI and sequence number are only 64
> bits).
> |> |>
> |> |> Actually, RFC5856 describes how ROHC can be used over IPSec
> |> (ROHCoIPsec).
> |> |
> |> |My read of it was:  apply ROHC at the endpoint ("inner headers") =
and
> |> |then do IPsec.  That is, compress and then encrypt.
> |> |
> |> |-d
> |> |
> |> |
> |> |> Combining it with multiplexing the entire packets could provide
> |> |> significant reduction in the header
> |> |overhead, especially for IPv6, I think.
> |> |>
> |> |> Muthu
> |> |>
> |> |> |-----Original Message-----
> |> |> |From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
> |> |> |Behalf Of Dan Wing (dwing)
> |> |> |Sent: Monday, July 01, 2013 10:25 PM
> |> |> |To: jltornos@unizar.es
> |> |> |Cc: tcmtf@ietf.org; jsaldana@unizar.es
> |> |> |Subject: Re: [tcmtf] Answers to possible questions in the BOF
> |> |> |
> |> |> |
> |> |> |On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
> |> |> |
> |> |> |> Hi all,
> |> |> |>
> |> |> |> Few days ago Julian talked about TCM-TF's security and now =
I've
> |> |> |> read in the link included by Dan,
> |> |> |saying that the gain obtained when multiplexing Ipsec-encrypted
> |> |> |packets is 20-to-1. We have been looking for more information
> |> |> |about this issue and thinking about a way to reduce the needed
> |> |bandwidth
> |> |> |in IPsec flows.
> |> |> |>
> |> |> |> The main idea is to find a way to change the authentication =
of
> |> |> |> the individual packets and merge
> |> |all
> |> |> |of them in a unique authentication. Thus, instead of using 20
> |> |> |IPsec tunnels, we would have a single tunnel including 20 =
flows.
> |> |> |Is this
> |> something similar than how Cisco gets the improvement?
> |> |> |
> |> |> |We would not be able to change IPsec any more than we could
> |> |> |change TCP, so I would not look at how
> |> |to
> |> |> |change IPsec authentication.
> |> |> |
> |> |> |However, if there are a bunch of IPsec packets sharing a common
> |> |> |path, I could see them being successfully multiplexed into one
> |> |> |larger packet at one tunnel endpoint and then de-multiplexed at
> |> |the
> |> |> |other tunnel endpoint.  This can provide a packet per second
> |> |> |reduction.  I don't think there are enough bytes in an IPsec
> |> |> |header to bother trying to do IPsec header compression (SPI and
> |> |> |sequence
> |> number are only 64 bits).
> |> |> |
> |> |> |-d
> |> |> |
> |> |> |
> |> |> |>
> |> |> |> Jos=E9 Luis
> |> |> |>
> |> |> |>
> |> |> |>
> |> |> |> Dan Wing <dwing@cisco.com> ha escrito:
> |> |> |>
> |> |> |>>
> |> |> |>> On Jun 26, 2013, at 3:49 AM, Jose Saldana =
<jsaldana@unizar.es>
> |> wrote:
> |> |> |>>
> |> |> |>>> Question 4: Is TCM-TF interesting for the Industry? Should
> |> |> |>>> the
> |IETF
> |> standardize this?
> |> |> |>>>
> |> |> |>>> Answer:
> |> |> |>>>
> |> |> |>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP =
VoIP
> |> |> |>>> traffic. So if RFC4170 was
> |> |> |interesting, why not updating it?
> |> |> |>>>
> |> |> |>>> 2) TCM-TF can be useful in order to save bandwidth in many
> cases:
> |> |> |>>>
> |> |> |>>> - Aggregation network of *network operators*: We are saving
> |> |> |>>> bandwidth by optimizing and
> |> |putting
> |> |> |together traffic flows. Is this  interesting for a network
operator?
> |What
> |> about overprovisioning?
> |> |The
> |> |> |idea is that there are places and moments in which a number of
> |> |> |flows based on small packets are in the same place and at the
> |> |> |same moment. Then, TCM-TF can be applied in order to provide
> |> |flexibility.
> |> |> |We are not optimizing the overall Internet traffic, we  are
> |> |> |optimizing specific flows with very
> |> |tight
> |> |> |delay requirements,  which network operators have to take care =
of
> |> |> |in a
> |> special way.
> |> |> |>>> www.huawei.com/ilink/en/download/HW_193034
> |> |> |>>>
> |> |> |>>> - *End to end* optimization: Nowadays, many appliances are
> |> |> |>>> used to  connect remote offices of
> |> |the
> |> |> |same company (creating a VPN). So if  a tunnel exists, why not
> |> |> |optimizing this traffic when
> |> |possible?
> |> |> |We  would save bandwidth in the access network, where it can be
> |> scarce.
> |> |> |>>>
> |> |> |>>> - Wireless and satellite scenarios.
> |> |> |>>
> |> |> |>> "Cisco adds IP multiplexing to mobile satellite package",
> |> |> |>> April 2012,
> |> |> |http://www.networkworld.com/news/2012/040912-cisco-ip-
> |> multiplexing-2
> |> |> |58082.html
> |> |> |>>
> |> |> |>>
> |> |> |>>
> |> |> |>>>
> |> |> |>>>
> |> |> |>>> Any other thoughts? Any other scenarios in mind? Potential
> |> beneficiaries?
> |> |> |>>
> |> |> |>> Some networks, today, use cRTP (RFC2508) on their access =
links.
> |This
> |> gives bandwidth savings
> |> |on
> |> |> |the access link, but consumes  considerable CPU horsepower on =
the
> |> aggregation router (to perform
> |> |> |cRTP), but provides no bandwidth savings across the network =
core.
> |If,
> |> instead, the bandwidth
> |> |could
> |> |> |be saved on the access link, across  the core, and on the =
far-end
> |> |> |access link -- all without the
> |> |CPU
> |> |> |impact on the aggregation router -- it is a considerable win.
> |> |> |>>
> |> |> |>> -d
> |> |> |>>
> |> |> |>>
> |> |> |>>
> |> |> |>>>
> |> |> |>>>
> |> |> |>>> Jose
> |> |> |>>>
> |> |> |>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] =
En
> |> |> |>>> nombre de Jose Saldana Enviado el: lunes, 24 de junio de =
2013
> |> |> |>>> 13:00
> |> |> |>>> Para: tcmtf@ietf.org
> |> |> |>>> Asunto: [tcmtf] Answers to possible questions in the BOF
> |> |> |>>>
> |> |> |>>> I would like to start a thread about possible questions
> |> |> |>>> people may  ask in the BOF. Obviously,
> |> |we
> |> |> |also need answers, so we should  cooperate.
> |> |> |>>>
> |> |> |>>> This is different from the "questions to ask in the BOF".
> |> |> |>>> This
> |will  be
> |> discussed separately.
> |> |> |>>>
> |> |> |>>> Thanks!
> |> |> |>>>
> |> |> |>>> Jose
> |> |> |>>>
> |> |> |>>> _______________________________________________
> |> |> |>>> 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  Thu Jul 11 02:19: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 22F6521F9F58; Thu, 11 Jul 2013 02:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.313
X-Spam-Level: 
X-Spam-Status: No, score=-6.313 tagged_above=-999 required=5 tests=[AWL=0.286,  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 pTWdOpxxTf-b; Thu, 11 Jul 2013 02:19:19 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id E758C21F9EFE; Thu, 11 Jul 2013 02:19:18 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r6B9JE4o010082; Thu, 11 Jul 2013 11:19:14 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <i-d-announce@ietf.org>
Date: Thu, 11 Jul 2013 11:19:16 +0200
Organization: Universidad de Zaragoza
Message-ID: <003f01ce7e17$b7c80650$275812f0$@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: Ac5+F6MX4jDUXY/OS0Cr+ea+zD8mig==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, tsv-area@ietf.org, tsvwg@ietf.org
Subject: [tcmtf] I-D Action: draft-saldana-tsvwg-tcmtf-05.txt
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 11 Jul 2013 09:19:24 -0000

A new version of I-D, draft-saldana-tsvwg-tcmtf-05.txt has been successfully
submitted by Jose Saldana and posted to the IETF repository.

Filename:	 draft-saldana-tsvwg-tcmtf
Revision:	 05
Title:		 Tunneling Compressed Multiplexed Traffic Flows (TCM-TF)
Creation date:	 2013-07-11
Group:		 Individual Submission
Number of pages: 21
URL:
http://www.ietf.org/internet-drafts/draft-saldana-tsvwg-tcmtf-05.txt
Status:          http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf
Htmlized:        http://tools.ietf.org/html/draft-saldana-tsvwg-tcmtf-05
Diff:
http://www.ietf.org/rfcdiff?url2=draft-saldana-tsvwg-tcmtf-05

Abstract:
   Tunneling Compressed and Multiplexed Traffic Flows (TCM-TF) is a
   method for improving the bandwidth utilization of network segments
   that carry multiple flows in parallel sharing a common path.  The
   method combines standard protocols for header compression,
   multiplexing, and tunneling over a network path for the purpose of
   reducing the bandwidth used when multiple flows are carried over that
   path.  The amount of packets per second can also be reduced.

   This document describes the TCM-TF framework and the different
   options which can be used for each layer (header compression,
   multiplexing and tunneling).

 



The IETF Secretariat




From jsaldana@unizar.es  Thu Jul 11 02:30:12 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 A2D1B21F9E62 for <tcmtf@ietfa.amsl.com>; Thu, 11 Jul 2013 02:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.325
X-Spam-Level: 
X-Spam-Status: No, score=-6.325 tagged_above=-999 required=5 tests=[AWL=0.273,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 hSsIzHqFiK68 for <tcmtf@ietfa.amsl.com>; Thu, 11 Jul 2013 02:30:06 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7E52921F9E71 for <tcmtf@ietf.org>; Thu, 11 Jul 2013 02:30:06 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r6B9U32x014824 for <tcmtf@ietf.org>; Thu, 11 Jul 2013 11:30:03 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Thu, 11 Jul 2013 11:30:05 +0200
Organization: Universidad de Zaragoza
Message-ID: <004a01ce7e19$39f51bd0$addf5370$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_004B_01CE7E29.FD7E8810"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5+GLYR4+doG1FRRPWbIVTi9Leiug==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] I have just uploaded a new version of the TCM-TF Reference Model draft
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 11 Jul 2013 09:30:12 -0000

This is a multipart message in MIME format.

------=_NextPart_000_004B_01CE7E29.FD7E8810
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

 

I have just uploaded a new version of the "main" TCM-TF draft.

 

It includes some improvements:

 

- The text of the whole document has been revised and improved

- We talk about "small-packet services", thus grouping together real-time
and non-real-time services

- New distribution of 1.2

- New terminology section (1.3)

- the content of 1.4 has been redistributed, and 1.5 has been added

- security considerations have been added, according to what we have
discussed

 

Thanks to everyone! See you in Berlin.

 

Jose

 


------=_NextPart_000_004B_01CE7E29.FD7E8810
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>I have just uploaded a new version of the =
&#8220;main&#8221; TCM-TF draft.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>It includes some =
improvements:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- The text of the whole document has been revised and =
improved<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>- =
We talk about &#8220;small-packet services&#8221;, thus grouping =
together real-time and non-real-time services<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- New distribution of =
1.2<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>- New =
terminology section (1.3)<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- the content of 1.4 has been =
redistributed, and 1.5 has been added<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- security considerations have been =
added, according to what we have discussed<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Thanks to everyone! See you in =
Berlin.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'mso-fareast-language:ES'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_004B_01CE7E29.FD7E8810--


From jltornos@unizar.es  Thu Jul 11 03:42:11 2013
Return-Path: <jltornos@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 149D621F9F98 for <tcmtf@ietfa.amsl.com>; Thu, 11 Jul 2013 03:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.157
X-Spam-Level: 
X-Spam-Status: No, score=-5.157 tagged_above=-999 required=5 tests=[AWL=1.443,  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 Kd-J-J80bdyI for <tcmtf@ietfa.amsl.com>; Thu, 11 Jul 2013 03:42:01 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 71C2021F9AED for <tcmtf@ietf.org>; Thu, 11 Jul 2013 03:42:00 -0700 (PDT)
Received: from mail.unizar.es (arazas.unizar.es [155.210.11.67]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r6BAfn2q003794 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 11 Jul 2013 12:41:50 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Date: Thu, 11 Jul 2013 12:41:51 +0200
From: jltornos <jltornos@unizar.es>
To: jsaldana@unizar.es
In-Reply-To: <003b01ce7e12$cf140570$6d3c1050$@unizar.es>
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>	<009901ce725a$d1623360$74269a20$@unizar.es>	<2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>	<20130628105725.lmag0xgqsgogggww@webmail.unizar.es>	<EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com>" <E721D8C6A2E1544DB2DEBC313AF54DE22417E050@xmb-rcd-x02.cisco.com>" <23E6BFC1-4D3C-48A5-A9A2-3BD32863F9A6@cisco.com> <E721D8C6A2E1544DB2DEBC313AF54DE22417FD51@xmb-rcd-x02.cisco.com> <007901ce7d42$2d49fc20$87ddf460$@unizar.es> <E721D8C6A2E1544DB2DEBC313AF54DE224189F5E@xmb-rcd-x02.cisco.com> <003b01ce7e12$cf140570$6d3c1050$@unizar.es>
Message-ID: <d88f12e6170e741a2efddc7d0e4e2c0e@unizar.es>
X-Sender: jltornos@unizar.es
User-Agent: Roundcube Webmail/0.8.5
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>
Subject: Re: [tcmtf] Answers to possible questions in 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: Thu, 11 Jul 2013 10:42:11 -0000

Hi all,

in the proposed scenario there are two options for establishing a secure 
communication:
- first, a user uses a tunnel from the beginning to the end of the 
communication, one SA (security association).
- second, we use two different tunnels, i.e. two different SAs.

In both scenarios the users have to trust TCM nodes, but in the first 
one the users have to share the security parameters (at least the secret 
key) with the TCM nodes, while in the second scenario the users directly 
establish a secure communication with the TCM nodes.

JosÃ© Luis


El 2013-07-11 10:44, Jose Saldana escribiÃ³:
> Muthu,
> 
> So you have a "bunch" of IPsec flows, and you
> - decrypt each flow
> - compress headers
> - multiplex packets
> - put the multiplexed bundle in an IPsec packet, using a new IPsec 
> tunnel
> 
> So you would have three phases:
> - separate IPsec tunnels for each flows
> - a single IPsec tunnel for the TCM flow
> - separate IPsec tunnels in the end
> 
> Origin 1
> Origin 2     <----20 secured flows --------> TCM-IO <------1 
> tunnel------>
> TCM-EO <-------- 20 secured flows----> destination 1, 2, 20
> ...
> Origin 20
> 
> But I think this raises a question: the TCM ingress optimizer must be 
> able
> to decrypt all the flows. This implies that it knows the keys and it is
> trusted by the communication ends.
> 
> This would be the most efficient solution, but you would need some
> requirements:
> 
> - trust the TCM optimizer
> - processing capacity for decrypt-compress-multiplex-encrypt
> 
> Is this what you are thinking?
> 
> Jose
> 
> -----Mensaje original-----
> De: Muthu Arul Mozhi Perumal (mperumal) [mailto:mperumal@cisco.com]
> Enviado el: miÃ©rcoles, 10 de julio de 2013 12:00
> Para: jsaldana@unizar.es; Dan Wing (dwing)
> CC: tcmtf@ietf.org; jltornos@unizar.es
> Asunto: RE: [tcmtf] Answers to possible questions in the BOF
> 
> Hi Jose,
> 
> |But in this case you have two security layers: the original flows use
> |IPsec, and you are adding another IPsec tunnel including all the
> compressed
> ones.
> 
> No, just one IPSec tunnel. The idea is to compress the headers of all
> packets
> that need to go over the same IPSec tunnel, multiplex them and give it 
> to
> the
> IPSec layer. The IPSec layer would add the IP/ESP header and send it 
> over
> the IPSec tunnel. The next header field in ESP would tell there is a 
> mux
> header following it, and the mux header can be used to demux the packet
> after IPSec decryption.
> 
> Muthu
> 
> |-----Original Message-----
> |From: Jose Saldana [mailto:jsaldana@unizar.es]
> |Sent: Wednesday, July 10, 2013 1:21 PM
> |To: Muthu Arul Mozhi Perumal (mperumal); Dan Wing (dwing)
> |Cc: tcmtf@ietf.org; jltornos@unizar.es
> |Subject: RE: [tcmtf] Answers to possible questions in the BOF
> |
> |Muthu,
> |
> |But in this case you have two security layers: the original flows use
> |IPsec, and you are adding another IPsec tunnel including all the
> compressed
> ones.
> |Am I right? Would this be necessary?
> |
> |Jose
> |
> |> -----Mensaje original-----
> |> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
> |> de Muthu Arul Mozhi Perumal (mperumal) Enviado el: jueves, 04 de
> |> julio de 2013 15:42
> |> Para: Dan Wing (dwing)
> |> CC: tcmtf@ietf.org; jltornos@unizar.es; jsaldana@unizar.es
> |> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
> |>
> |> |My read of it was:  apply ROHC at the endpoint ("inner headers") 
> and
> |> |then do IPsec.  That is, compress and then encrypt.
> |>
> |> Right, Dan. I was thinking the (inner) headers of the packets going
> |> over
> |the
> |> same IPSec tunnel could first be compressed, multiplex, then
> |> encrypted and sent over that tunnel:
> |>
> |> --------------------------------------------
> |> |outer IP hdr| ESP | MUX | ROHCoIPsec|Data1|
> |> |            |     | hdr |   hdr1    |     |
> |> --------------------------------------------
> |>                           ----------------------
> |>                           | ROHCoIPsec | Data2 |
> |>                           |    hdr2    |       |
> |>                           ----------------------
> |>                           -------------------------------------
> |>                           | ROHCoIPsec |  Data3  | ESP   | ESP|
> |>                           |    hdr3    |         |Trailer| ICV|
> |>                           -------------------------------------
> |>                     <-----------Encrypted-------->
> |>
> |> Muthu
> |>
> |> |-----Original Message-----
> |> |From: Dan Wing (dwing)
> |> |Sent: Thursday, July 04, 2013 12:26 AM
> |> |To: Muthu Arul Mozhi Perumal (mperumal)
> |> |Cc: jltornos@unizar.es; tcmtf@ietf.org; jsaldana@unizar.es
> |> |Subject: Re: [tcmtf] Answers to possible questions in the BOF
> |> |
> |> |
> |> |On Jul 3, 2013, at 11:51 AM, Muthu Arul Mozhi Perumal (mperumal)
> |> <mperumal@cisco.com> wrote:
> |> |
> |> |> |However, if there are a bunch of IPsec packets sharing a common
> |> |> |path, I could see them being successfully multiplexed into one
> |> |> |larger packet at one tunnel endpoint and then de-multiplexed at
> |> |> |the
> |> other tunnel endpoint.
> |> |> |This can provide a packet per second reduction.  I don't think
> |> |> |there are enough bytes in an IPsec header to bother trying to do
> |> |> |IPsec header compression (SPI and sequence number are only 64
> bits).
> |> |>
> |> |> Actually, RFC5856 describes how ROHC can be used over IPSec
> |> (ROHCoIPsec).
> |> |
> |> |My read of it was:  apply ROHC at the endpoint ("inner headers") 
> and
> |> |then do IPsec.  That is, compress and then encrypt.
> |> |
> |> |-d
> |> |
> |> |
> |> |> Combining it with multiplexing the entire packets could provide
> |> |> significant reduction in the header
> |> |overhead, especially for IPv6, I think.
> |> |>
> |> |> Muthu
> |> |>
> |> |> |-----Original Message-----
> |> |> |From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
> |> |> |Behalf Of Dan Wing (dwing)
> |> |> |Sent: Monday, July 01, 2013 10:25 PM
> |> |> |To: jltornos@unizar.es
> |> |> |Cc: tcmtf@ietf.org; jsaldana@unizar.es
> |> |> |Subject: Re: [tcmtf] Answers to possible questions in the BOF
> |> |> |
> |> |> |
> |> |> |On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
> |> |> |
> |> |> |> Hi all,
> |> |> |>
> |> |> |> Few days ago Julian talked about TCM-TF's security and now 
> I've
> |> |> |> read in the link included by Dan,
> |> |> |saying that the gain obtained when multiplexing Ipsec-encrypted
> |> |> |packets is 20-to-1. We have been looking for more information
> |> |> |about this issue and thinking about a way to reduce the needed
> |> |bandwidth
> |> |> |in IPsec flows.
> |> |> |>
> |> |> |> The main idea is to find a way to change the authentication of
> |> |> |> the individual packets and merge
> |> |all
> |> |> |of them in a unique authentication. Thus, instead of using 20
> |> |> |IPsec tunnels, we would have a single tunnel including 20 flows.
> |> |> |Is this
> |> something similar than how Cisco gets the improvement?
> |> |> |
> |> |> |We would not be able to change IPsec any more than we could
> |> |> |change TCP, so I would not look at how
> |> |to
> |> |> |change IPsec authentication.
> |> |> |
> |> |> |However, if there are a bunch of IPsec packets sharing a common
> |> |> |path, I could see them being successfully multiplexed into one
> |> |> |larger packet at one tunnel endpoint and then de-multiplexed at
> |> |the
> |> |> |other tunnel endpoint.  This can provide a packet per second
> |> |> |reduction.  I don't think there are enough bytes in an IPsec
> |> |> |header to bother trying to do IPsec header compression (SPI and
> |> |> |sequence
> |> number are only 64 bits).
> |> |> |
> |> |> |-d
> |> |> |
> |> |> |
> |> |> |>
> |> |> |> JosÃ© Luis
> |> |> |>
> |> |> |>
> |> |> |>
> |> |> |> Dan Wing <dwing@cisco.com> ha escrito:
> |> |> |>
> |> |> |>>
> |> |> |>> On Jun 26, 2013, at 3:49 AM, Jose Saldana 
> <jsaldana@unizar.es>
> |> wrote:
> |> |> |>>
> |> |> |>>> Question 4: Is TCM-TF interesting for the Industry? Should
> |> |> |>>> the
> |IETF
> |> standardize this?
> |> |> |>>>
> |> |> |>>> Answer:
> |> |> |>>>
> |> |> |>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP 
> VoIP
> |> |> |>>> traffic. So if RFC4170 was
> |> |> |interesting, why not updating it?
> |> |> |>>>
> |> |> |>>> 2) TCM-TF can be useful in order to save bandwidth in many
> cases:
> |> |> |>>>
> |> |> |>>> - Aggregation network of *network operators*: We are saving
> |> |> |>>> bandwidth by optimizing and
> |> |putting
> |> |> |together traffic flows. Is this  interesting for a network
> operator?
> |What
> |> about overprovisioning?
> |> |The
> |> |> |idea is that there are places and moments in which a number of
> |> |> |flows based on small packets are in the same place and at the
> |> |> |same moment. Then, TCM-TF can be applied in order to provide
> |> |flexibility.
> |> |> |We are not optimizing the overall Internet traffic, we  are
> |> |> |optimizing specific flows with very
> |> |tight
> |> |> |delay requirements,  which network operators have to take care 
> of
> |> |> |in a
> |> special way.
> |> |> |>>> www.huawei.com/ilink/en/download/HW_193034
> |> |> |>>>
> |> |> |>>> - *End to end* optimization: Nowadays, many appliances are
> |> |> |>>> used to  connect remote offices of
> |> |the
> |> |> |same company (creating a VPN). So if  a tunnel exists, why not
> |> |> |optimizing this traffic when
> |> |possible?
> |> |> |We  would save bandwidth in the access network, where it can be
> |> scarce.
> |> |> |>>>
> |> |> |>>> - Wireless and satellite scenarios.
> |> |> |>>
> |> |> |>> "Cisco adds IP multiplexing to mobile satellite package",
> |> |> |>> April 2012,
> |> |> |http://www.networkworld.com/news/2012/040912-cisco-ip-
> |> multiplexing-2
> |> |> |58082.html
> |> |> |>>
> |> |> |>>
> |> |> |>>
> |> |> |>>>
> |> |> |>>>
> |> |> |>>> Any other thoughts? Any other scenarios in mind? Potential
> |> beneficiaries?
> |> |> |>>
> |> |> |>> Some networks, today, use cRTP (RFC2508) on their access 
> links.
> |This
> |> gives bandwidth savings
> |> |on
> |> |> |the access link, but consumes  considerable CPU horsepower on 
> the
> |> aggregation router (to perform
> |> |> |cRTP), but provides no bandwidth savings across the network 
> core.
> |If,
> |> instead, the bandwidth
> |> |could
> |> |> |be saved on the access link, across  the core, and on the 
> far-end
> |> |> |access link -- all without the
> |> |CPU
> |> |> |impact on the aggregation router -- it is a considerable win.
> |> |> |>>
> |> |> |>> -d
> |> |> |>>
> |> |> |>>
> |> |> |>>
> |> |> |>>>
> |> |> |>>>
> |> |> |>>> Jose
> |> |> |>>>
> |> |> |>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] 
> En
> |> |> |>>> nombre de Jose Saldana Enviado el: lunes, 24 de junio de 
> 2013
> |> |> |>>> 13:00
> |> |> |>>> Para: tcmtf@ietf.org
> |> |> |>>> Asunto: [tcmtf] Answers to possible questions in the BOF
> |> |> |>>>
> |> |> |>>> I would like to start a thread about possible questions
> |> |> |>>> people may  ask in the BOF. Obviously,
> |> |we
> |> |> |also need answers, so we should  cooperate.
> |> |> |>>>
> |> |> |>>> This is different from the "questions to ask in the BOF".
> |> |> |>>> This
> |will  be
> |> discussed separately.
> |> |> |>>>
> |> |> |>>> Thanks!
> |> |> |>>>
> |> |> |>>> Jose
> |> |> |>>>
> |> |> |>>> _______________________________________________
> |> |> |>>> 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
> 
> 
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf

From mperumal@cisco.com  Thu Jul 11 06:07:03 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 D580621F9F26 for <tcmtf@ietfa.amsl.com>; Thu, 11 Jul 2013 06:07:03 -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 AetVh-LZOtec for <tcmtf@ietfa.amsl.com>; Thu, 11 Jul 2013 06:06:59 -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 3F63A11E812E for <tcmtf@ietf.org>; Thu, 11 Jul 2013 06:06:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19238; q=dns/txt; s=iport; t=1373548019; x=1374757619; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=qJgjtAElx2EkOZf5mNZcT7FX0kDjYwXOP3J47hkVuLw=; b=fW9qN2DRGxXjgdfCUfUBUx1RKh6lOr1jnJ2DsaW0h5RIYg1o4bY4Hs8z MqnQ8S+50JZmwNxxPo22VAEClSvbqfK7CG1q/Ae95WzAE4mn2F4VdJp3h /fcp7JVihcAUu1dj47wt5TFQ043nI0i9BpAVMA9rC4cP02WR0e8xLfC+R 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAJid3lGtJV2d/2dsb2JhbABagwkyTYMGvkoXbxZ0giMBAQEEAQEBIAQNFSMCCAMMBAIBCBEEAQEDAgYdAwICAiULFAEICAIEAQ0FCBIBA4dxDKV2kT6BJoxugRwWGwcGglAzbAOUA5UhgxGCKA
X-IronPort-AV: E=Sophos;i="4.87,1043,1363132800"; d="scan'208";a="230551321"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-9.cisco.com with ESMTP; 11 Jul 2013 13:06:58 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r6BD6wQD012895 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 11 Jul 2013 13:06:58 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.192]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Thu, 11 Jul 2013 08:06:57 -0500
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: jltornos <jltornos@unizar.es>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Thread-Topic: [tcmtf] Answers to possible questions in the BOF
Thread-Index: AQHOdnvPX00XDi64+EGJAr2DWa8S1ZlTTKXAgABYC4CAAFOdIIAJ8uGA//+13OCAAbiKO4AAGC3g
Date: Thu, 11 Jul 2013 13:06:58 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE22418FD40@xmb-rcd-x02.cisco.com>
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com> <20130628105725.lmag0xgqsgogggww@webmail.unizar.es> <EFFB6AC1-BF9A-47D9-B5B8-3DD34A508FE8@cisco.com>" <E721D8C6A2E1544DB2DEBC313AF54DE22417E050@xmb-rcd-x02.cisco.com>" <23E6BFC1-4D3C-48A5-A9A2-3BD32863F9A6@cisco.com> <E721D8C6A2E1544DB2DEBC313AF54DE22417FD51@xmb-rcd-x02.cisco.com> <007901ce7d42$2d49fc20$87ddf460$@unizar.es> <E721D8C6A2E1544DB2DEBC313AF54DE224189F5E@xmb-rcd-x02.cisco.com> <003b01ce7e12$cf140570$6d3c1050$@unizar.es> <d88f12e6170e741a2efddc7d0e4e2c0e@unizar.es>
In-Reply-To: <d88f12e6170e741a2efddc7d0e4e2c0e@unizar.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.145.75]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Answers to possible questions in 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: Thu, 11 Jul 2013 13:07:03 -0000

fFNvIHlvdSBoYXZlIGEgImJ1bmNoIiBvZiBJUHNlYyBmbG93cywgYW5kIHlvdQ0KfC0gZGVjcnlw
dCBlYWNoIGZsb3cNCnwtIGNvbXByZXNzIGhlYWRlcnMNCnwtIG11bHRpcGxleCBwYWNrZXRzDQp8
LSBwdXQgdGhlIG11bHRpcGxleGVkIGJ1bmRsZSBpbiBhbiBJUHNlYyBwYWNrZXQsIHVzaW5nIGEg
bmV3IElQc2VjDQp8ICB0dW5uZWwNCg0KVGhhdCdzIG9uZSBvZiB0aGUgdXNlIGNhc2VzLCBidXQg
bG9va3MgbGVzcyBpbnRlcmVzdGluZyB0byBtZSBiZWNhdXNlIG9mIGhhdmluZyB0byBwZXJmb3Jt
IElQU2VjIHR3aWNlLg0KDQpJIHdhcyB0aGlua2luZyBvZiB0aGUgY2FzZSB3aGVyZSB0aGVyZSBp
cyBhbiBJUFNlYyB0dW5uZWwgYmV0d2VlbiB0d28gcm91dGVycy4uLmEgdHlwaWNhbCBkZXBsb3lt
ZW50IGZvciBzZWN1cmluZyBjb25uZWN0aW9uIGJldHdlZW4gdHdvIGJyYW5jaGVzIG9mIGFuIG9y
Z2FuaXphdGlvbiBvdmVyIHRoZSBJbnRlcm5ldC4gVGhvc2UgdHdvIHJvdXRlcnMgY2FuIHBlcmZv
cm0gVENNVEYgYW5kIHVzZSB0aGUgSVBTZWMgdHVubmVsIGZvciB0cmFuc3BvcnRpbmcgdGhlIG11
bHRpcGxleGVkICsgY29tcHJlc3NlZCBwYWNrZXRzLiBJbiBlZmZlY3QsIHdlIGhhdmU6DQoNCk4g
cGFja2V0cy0tPltjb21wcmVzc2lvbl0tLT5OIHBhY2tldHMgd2l0aCBoZWFkZXJzIGNvbXByZXNz
ZWQtLSsNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIHwNCjEgZW5jcnlwdGVkIHBhY2tldDwtLVtlbmNyeXB0aW9uXTwtLTEgcGFj
a2V0LS1bbXVsdGlwbGV4aW5nXTwtLSsgICAgICAgICAgICANCnwNCistLT5bdHVubmVsaW5nXS0t
PiAxIHR1bm5lbGVkIGVuY3J5cHRlZCBtdWx0aXBsZXhlZCBjb21wcmVzc2VkIHBhY2tldA0KDQpU
aGlzIGlzIFRDTVRGU2VjIChUQ01URiArIElQU2VjKSAtOikNCg0KQm90aCBUQ01GVCBhbmQgSVBT
ZWMgd291bGQgbmVlZCBzb21lIGNoYW5nZXMuLg0KDQpNdXRodQ0KDQp8LS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCnxGcm9tOiBqbHRvcm5vcyBbbWFpbHRvOmpsdG9ybm9zQHVuaXphci5lc10N
CnxTZW50OiBUaHVyc2RheSwgSnVseSAxMSwgMjAxMyA0OjEyIFBNDQp8VG86IGpzYWxkYW5hQHVu
aXphci5lcw0KfENjOiBNdXRodSBBcnVsIE1vemhpIFBlcnVtYWwgKG1wZXJ1bWFsKTsgdGNtdGZA
aWV0Zi5vcmcNCnxTdWJqZWN0OiBSZTogW3RjbXRmXSBBbnN3ZXJzIHRvIHBvc3NpYmxlIHF1ZXN0
aW9ucyBpbiB0aGUgQk9GDQp8DQp8SGkgYWxsLA0KfA0KfGluIHRoZSBwcm9wb3NlZCBzY2VuYXJp
byB0aGVyZSBhcmUgdHdvIG9wdGlvbnMgZm9yIGVzdGFibGlzaGluZyBhIHNlY3VyZQ0KfGNvbW11
bmljYXRpb246DQp8LSBmaXJzdCwgYSB1c2VyIHVzZXMgYSB0dW5uZWwgZnJvbSB0aGUgYmVnaW5u
aW5nIHRvIHRoZSBlbmQgb2YgdGhlDQp8Y29tbXVuaWNhdGlvbiwgb25lIFNBIChzZWN1cml0eSBh
c3NvY2lhdGlvbikuDQp8LSBzZWNvbmQsIHdlIHVzZSB0d28gZGlmZmVyZW50IHR1bm5lbHMsIGku
ZS4gdHdvIGRpZmZlcmVudCBTQXMuDQp8DQp8SW4gYm90aCBzY2VuYXJpb3MgdGhlIHVzZXJzIGhh
dmUgdG8gdHJ1c3QgVENNIG5vZGVzLCBidXQgaW4gdGhlIGZpcnN0DQp8b25lIHRoZSB1c2VycyBo
YXZlIHRvIHNoYXJlIHRoZSBzZWN1cml0eSBwYXJhbWV0ZXJzIChhdCBsZWFzdCB0aGUgc2VjcmV0
DQp8a2V5KSB3aXRoIHRoZSBUQ00gbm9kZXMsIHdoaWxlIGluIHRoZSBzZWNvbmQgc2NlbmFyaW8g
dGhlIHVzZXJzIGRpcmVjdGx5DQp8ZXN0YWJsaXNoIGEgc2VjdXJlIGNvbW11bmljYXRpb24gd2l0
aCB0aGUgVENNIG5vZGVzLg0KfA0KfEpvc8OpIEx1aXMNCnwNCnwNCnxFbCAyMDEzLTA3LTExIDEw
OjQ0LCBKb3NlIFNhbGRhbmEgZXNjcmliacOzOg0KfD4gTXV0aHUsDQp8Pg0KfD4gU28geW91IGhh
dmUgYSAiYnVuY2giIG9mIElQc2VjIGZsb3dzLCBhbmQgeW91DQp8PiAtIGRlY3J5cHQgZWFjaCBm
bG93DQp8PiAtIGNvbXByZXNzIGhlYWRlcnMNCnw+IC0gbXVsdGlwbGV4IHBhY2tldHMNCnw+IC0g
cHV0IHRoZSBtdWx0aXBsZXhlZCBidW5kbGUgaW4gYW4gSVBzZWMgcGFja2V0LCB1c2luZyBhIG5l
dyBJUHNlYw0KfD4gdHVubmVsDQp8Pg0KfD4gU28geW91IHdvdWxkIGhhdmUgdGhyZWUgcGhhc2Vz
Og0KfD4gLSBzZXBhcmF0ZSBJUHNlYyB0dW5uZWxzIGZvciBlYWNoIGZsb3dzDQp8PiAtIGEgc2lu
Z2xlIElQc2VjIHR1bm5lbCBmb3IgdGhlIFRDTSBmbG93DQp8PiAtIHNlcGFyYXRlIElQc2VjIHR1
bm5lbHMgaW4gdGhlIGVuZA0KfD4NCnw+IE9yaWdpbiAxDQp8PiBPcmlnaW4gMiAgICAgPC0tLS0y
MCBzZWN1cmVkIGZsb3dzIC0tLS0tLS0tPiBUQ00tSU8gPC0tLS0tLTENCnw+IHR1bm5lbC0tLS0t
LT4NCnw+IFRDTS1FTyA8LS0tLS0tLS0gMjAgc2VjdXJlZCBmbG93cy0tLS0+IGRlc3RpbmF0aW9u
IDEsIDIsIDIwDQp8PiAuLi4NCnw+IE9yaWdpbiAyMA0KfD4NCnw+IEJ1dCBJIHRoaW5rIHRoaXMg
cmFpc2VzIGEgcXVlc3Rpb246IHRoZSBUQ00gaW5ncmVzcyBvcHRpbWl6ZXIgbXVzdCBiZQ0KfD4g
YWJsZQ0KfD4gdG8gZGVjcnlwdCBhbGwgdGhlIGZsb3dzLiBUaGlzIGltcGxpZXMgdGhhdCBpdCBr
bm93cyB0aGUga2V5cyBhbmQgaXQgaXMNCnw+IHRydXN0ZWQgYnkgdGhlIGNvbW11bmljYXRpb24g
ZW5kcy4NCnw+DQp8PiBUaGlzIHdvdWxkIGJlIHRoZSBtb3N0IGVmZmljaWVudCBzb2x1dGlvbiwg
YnV0IHlvdSB3b3VsZCBuZWVkIHNvbWUNCnw+IHJlcXVpcmVtZW50czoNCnw+DQp8PiAtIHRydXN0
IHRoZSBUQ00gb3B0aW1pemVyDQp8PiAtIHByb2Nlc3NpbmcgY2FwYWNpdHkgZm9yIGRlY3J5cHQt
Y29tcHJlc3MtbXVsdGlwbGV4LWVuY3J5cHQNCnw+DQp8PiBJcyB0aGlzIHdoYXQgeW91IGFyZSB0
aGlua2luZz8NCnw+DQp8PiBKb3NlDQp8Pg0KfD4gLS0tLS1NZW5zYWplIG9yaWdpbmFsLS0tLS0N
Cnw+IERlOiBNdXRodSBBcnVsIE1vemhpIFBlcnVtYWwgKG1wZXJ1bWFsKSBbbWFpbHRvOm1wZXJ1
bWFsQGNpc2NvLmNvbV0NCnw+IEVudmlhZG8gZWw6IG1pw6lyY29sZXMsIDEwIGRlIGp1bGlvIGRl
IDIwMTMgMTI6MDANCnw+IFBhcmE6IGpzYWxkYW5hQHVuaXphci5lczsgRGFuIFdpbmcgKGR3aW5n
KQ0KfD4gQ0M6IHRjbXRmQGlldGYub3JnOyBqbHRvcm5vc0B1bml6YXIuZXMNCnw+IEFzdW50bzog
UkU6IFt0Y210Zl0gQW5zd2VycyB0byBwb3NzaWJsZSBxdWVzdGlvbnMgaW4gdGhlIEJPRg0KfD4N
Cnw+IEhpIEpvc2UsDQp8Pg0KfD4gfEJ1dCBpbiB0aGlzIGNhc2UgeW91IGhhdmUgdHdvIHNlY3Vy
aXR5IGxheWVyczogdGhlIG9yaWdpbmFsIGZsb3dzIHVzZQ0KfD4gfElQc2VjLCBhbmQgeW91IGFy
ZSBhZGRpbmcgYW5vdGhlciBJUHNlYyB0dW5uZWwgaW5jbHVkaW5nIGFsbCB0aGUNCnw+IGNvbXBy
ZXNzZWQNCnw+IG9uZXMuDQp8Pg0KfD4gTm8sIGp1c3Qgb25lIElQU2VjIHR1bm5lbC4gVGhlIGlk
ZWEgaXMgdG8gY29tcHJlc3MgdGhlIGhlYWRlcnMgb2YgYWxsDQp8PiBwYWNrZXRzDQp8PiB0aGF0
IG5lZWQgdG8gZ28gb3ZlciB0aGUgc2FtZSBJUFNlYyB0dW5uZWwsIG11bHRpcGxleCB0aGVtIGFu
ZCBnaXZlIGl0DQp8PiB0bw0KfD4gdGhlDQp8PiBJUFNlYyBsYXllci4gVGhlIElQU2VjIGxheWVy
IHdvdWxkIGFkZCB0aGUgSVAvRVNQIGhlYWRlciBhbmQgc2VuZCBpdA0KfD4gb3Zlcg0KfD4gdGhl
IElQU2VjIHR1bm5lbC4gVGhlIG5leHQgaGVhZGVyIGZpZWxkIGluIEVTUCB3b3VsZCB0ZWxsIHRo
ZXJlIGlzIGENCnw+IG11eA0KfD4gaGVhZGVyIGZvbGxvd2luZyBpdCwgYW5kIHRoZSBtdXggaGVh
ZGVyIGNhbiBiZSB1c2VkIHRvIGRlbXV4IHRoZSBwYWNrZXQNCnw+IGFmdGVyIElQU2VjIGRlY3J5
cHRpb24uDQp8Pg0KfD4gTXV0aHUNCnw+DQp8PiB8LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
Cnw+IHxGcm9tOiBKb3NlIFNhbGRhbmEgW21haWx0bzpqc2FsZGFuYUB1bml6YXIuZXNdDQp8PiB8
U2VudDogV2VkbmVzZGF5LCBKdWx5IDEwLCAyMDEzIDE6MjEgUE0NCnw+IHxUbzogTXV0aHUgQXJ1
bCBNb3poaSBQZXJ1bWFsIChtcGVydW1hbCk7IERhbiBXaW5nIChkd2luZykNCnw+IHxDYzogdGNt
dGZAaWV0Zi5vcmc7IGpsdG9ybm9zQHVuaXphci5lcw0KfD4gfFN1YmplY3Q6IFJFOiBbdGNtdGZd
IEFuc3dlcnMgdG8gcG9zc2libGUgcXVlc3Rpb25zIGluIHRoZSBCT0YNCnw+IHwNCnw+IHxNdXRo
dSwNCnw+IHwNCnw+IHxCdXQgaW4gdGhpcyBjYXNlIHlvdSBoYXZlIHR3byBzZWN1cml0eSBsYXll
cnM6IHRoZSBvcmlnaW5hbCBmbG93cyB1c2UNCnw+IHxJUHNlYywgYW5kIHlvdSBhcmUgYWRkaW5n
IGFub3RoZXIgSVBzZWMgdHVubmVsIGluY2x1ZGluZyBhbGwgdGhlDQp8PiBjb21wcmVzc2VkDQp8
PiBvbmVzLg0KfD4gfEFtIEkgcmlnaHQ/IFdvdWxkIHRoaXMgYmUgbmVjZXNzYXJ5Pw0KfD4gfA0K
fD4gfEpvc2UNCnw+IHwNCnw+IHw+IC0tLS0tTWVuc2FqZSBvcmlnaW5hbC0tLS0tDQp8PiB8PiBE
ZTogdGNtdGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnRjbXRmLWJvdW5jZXNAaWV0Zi5vcmdd
IEVuIG5vbWJyZQ0KfD4gfD4gZGUgTXV0aHUgQXJ1bCBNb3poaSBQZXJ1bWFsIChtcGVydW1hbCkg
RW52aWFkbyBlbDoganVldmVzLCAwNCBkZQ0KfD4gfD4ganVsaW8gZGUgMjAxMyAxNTo0Mg0KfD4g
fD4gUGFyYTogRGFuIFdpbmcgKGR3aW5nKQ0KfD4gfD4gQ0M6IHRjbXRmQGlldGYub3JnOyBqbHRv
cm5vc0B1bml6YXIuZXM7IGpzYWxkYW5hQHVuaXphci5lcw0KfD4gfD4gQXN1bnRvOiBSZTogW3Rj
bXRmXSBBbnN3ZXJzIHRvIHBvc3NpYmxlIHF1ZXN0aW9ucyBpbiB0aGUgQk9GDQp8PiB8Pg0KfD4g
fD4gfE15IHJlYWQgb2YgaXQgd2FzOiAgYXBwbHkgUk9IQyBhdCB0aGUgZW5kcG9pbnQgKCJpbm5l
ciBoZWFkZXJzIikNCnw+IGFuZA0KfD4gfD4gfHRoZW4gZG8gSVBzZWMuICBUaGF0IGlzLCBjb21w
cmVzcyBhbmQgdGhlbiBlbmNyeXB0Lg0KfD4gfD4NCnw+IHw+IFJpZ2h0LCBEYW4uIEkgd2FzIHRo
aW5raW5nIHRoZSAoaW5uZXIpIGhlYWRlcnMgb2YgdGhlIHBhY2tldHMgZ29pbmcNCnw+IHw+IG92
ZXINCnw+IHx0aGUNCnw+IHw+IHNhbWUgSVBTZWMgdHVubmVsIGNvdWxkIGZpcnN0IGJlIGNvbXBy
ZXNzZWQsIG11bHRpcGxleCwgdGhlbg0KfD4gfD4gZW5jcnlwdGVkIGFuZCBzZW50IG92ZXIgdGhh
dCB0dW5uZWw6DQp8PiB8Pg0KfD4gfD4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0NCnw+IHw+IHxvdXRlciBJUCBoZHJ8IEVTUCB8IE1VWCB8IFJPSENvSVBzZWN8
RGF0YTF8DQp8PiB8PiB8ICAgICAgICAgICAgfCAgICAgfCBoZHIgfCAgIGhkcjEgICAgfCAgICAg
fA0KfD4gfD4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCnw+
IHw+ICAgICAgICAgICAgICAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KfD4g
fD4gICAgICAgICAgICAgICAgICAgICAgICAgICB8IFJPSENvSVBzZWMgfCBEYXRhMiB8DQp8PiB8
PiAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICAgaGRyMiAgICB8ICAgICAgIHwNCnw+IHw+
ICAgICAgICAgICAgICAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KfD4gfD4g
ICAgICAgICAgICAgICAgICAgICAgICAgICAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQp8PiB8PiAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgUk9IQ29JUHNlYyB8ICBE
YXRhMyAgfCBFU1AgICB8IEVTUHwNCnw+IHw+ICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAg
ICBoZHIzICAgIHwgICAgICAgICB8VHJhaWxlcnwgSUNWfA0KfD4gfD4gICAgICAgICAgICAgICAg
ICAgICAgICAgICAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQp8PiB8PiAg
ICAgICAgICAgICAgICAgICAgIDwtLS0tLS0tLS0tLUVuY3J5cHRlZC0tLS0tLS0tPg0KfD4gfD4N
Cnw+IHw+IE11dGh1DQp8PiB8Pg0KfD4gfD4gfC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQp8
PiB8PiB8RnJvbTogRGFuIFdpbmcgKGR3aW5nKQ0KfD4gfD4gfFNlbnQ6IFRodXJzZGF5LCBKdWx5
IDA0LCAyMDEzIDEyOjI2IEFNDQp8PiB8PiB8VG86IE11dGh1IEFydWwgTW96aGkgUGVydW1hbCAo
bXBlcnVtYWwpDQp8PiB8PiB8Q2M6IGpsdG9ybm9zQHVuaXphci5lczsgdGNtdGZAaWV0Zi5vcmc7
IGpzYWxkYW5hQHVuaXphci5lcw0KfD4gfD4gfFN1YmplY3Q6IFJlOiBbdGNtdGZdIEFuc3dlcnMg
dG8gcG9zc2libGUgcXVlc3Rpb25zIGluIHRoZSBCT0YNCnw+IHw+IHwNCnw+IHw+IHwNCnw+IHw+
IHxPbiBKdWwgMywgMjAxMywgYXQgMTE6NTEgQU0sIE11dGh1IEFydWwgTW96aGkgUGVydW1hbCAo
bXBlcnVtYWwpDQp8PiB8PiA8bXBlcnVtYWxAY2lzY28uY29tPiB3cm90ZToNCnw+IHw+IHwNCnw+
IHw+IHw+IHxIb3dldmVyLCBpZiB0aGVyZSBhcmUgYSBidW5jaCBvZiBJUHNlYyBwYWNrZXRzIHNo
YXJpbmcgYSBjb21tb24NCnw+IHw+IHw+IHxwYXRoLCBJIGNvdWxkIHNlZSB0aGVtIGJlaW5nIHN1
Y2Nlc3NmdWxseSBtdWx0aXBsZXhlZCBpbnRvIG9uZQ0KfD4gfD4gfD4gfGxhcmdlciBwYWNrZXQg
YXQgb25lIHR1bm5lbCBlbmRwb2ludCBhbmQgdGhlbiBkZS1tdWx0aXBsZXhlZCBhdA0KfD4gfD4g
fD4gfHRoZQ0KfD4gfD4gb3RoZXIgdHVubmVsIGVuZHBvaW50Lg0KfD4gfD4gfD4gfFRoaXMgY2Fu
IHByb3ZpZGUgYSBwYWNrZXQgcGVyIHNlY29uZCByZWR1Y3Rpb24uICBJIGRvbid0IHRoaW5rDQp8
PiB8PiB8PiB8dGhlcmUgYXJlIGVub3VnaCBieXRlcyBpbiBhbiBJUHNlYyBoZWFkZXIgdG8gYm90
aGVyIHRyeWluZyB0byBkbw0KfD4gfD4gfD4gfElQc2VjIGhlYWRlciBjb21wcmVzc2lvbiAoU1BJ
IGFuZCBzZXF1ZW5jZSBudW1iZXIgYXJlIG9ubHkgNjQNCnw+IGJpdHMpLg0KfD4gfD4gfD4NCnw+
IHw+IHw+IEFjdHVhbGx5LCBSRkM1ODU2IGRlc2NyaWJlcyBob3cgUk9IQyBjYW4gYmUgdXNlZCBv
dmVyIElQU2VjDQp8PiB8PiAoUk9IQ29JUHNlYykuDQp8PiB8PiB8DQp8PiB8PiB8TXkgcmVhZCBv
ZiBpdCB3YXM6ICBhcHBseSBST0hDIGF0IHRoZSBlbmRwb2ludCAoImlubmVyIGhlYWRlcnMiKQ0K
fD4gYW5kDQp8PiB8PiB8dGhlbiBkbyBJUHNlYy4gIFRoYXQgaXMsIGNvbXByZXNzIGFuZCB0aGVu
IGVuY3J5cHQuDQp8PiB8PiB8DQp8PiB8PiB8LWQNCnw+IHw+IHwNCnw+IHw+IHwNCnw+IHw+IHw+
IENvbWJpbmluZyBpdCB3aXRoIG11bHRpcGxleGluZyB0aGUgZW50aXJlIHBhY2tldHMgY291bGQg
cHJvdmlkZQ0KfD4gfD4gfD4gc2lnbmlmaWNhbnQgcmVkdWN0aW9uIGluIHRoZSBoZWFkZXINCnw+
IHw+IHxvdmVyaGVhZCwgZXNwZWNpYWxseSBmb3IgSVB2NiwgSSB0aGluay4NCnw+IHw+IHw+DQp8
PiB8PiB8PiBNdXRodQ0KfD4gfD4gfD4NCnw+IHw+IHw+IHwtLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KfD4gfD4gfD4gfEZyb206IHRjbXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0Y210
Zi1ib3VuY2VzQGlldGYub3JnXSBPbg0KfD4gfD4gfD4gfEJlaGFsZiBPZiBEYW4gV2luZyAoZHdp
bmcpDQp8PiB8PiB8PiB8U2VudDogTW9uZGF5LCBKdWx5IDAxLCAyMDEzIDEwOjI1IFBNDQp8PiB8
PiB8PiB8VG86IGpsdG9ybm9zQHVuaXphci5lcw0KfD4gfD4gfD4gfENjOiB0Y210ZkBpZXRmLm9y
ZzsganNhbGRhbmFAdW5pemFyLmVzDQp8PiB8PiB8PiB8U3ViamVjdDogUmU6IFt0Y210Zl0gQW5z
d2VycyB0byBwb3NzaWJsZSBxdWVzdGlvbnMgaW4gdGhlIEJPRg0KfD4gfD4gfD4gfA0KfD4gfD4g
fD4gfA0KfD4gfD4gfD4gfE9uIEp1biAyOCwgMjAxMywgYXQgMTo1NyBBTSwgamx0b3Jub3NAdW5p
emFyLmVzIHdyb3RlOg0KfD4gfD4gfD4gfA0KfD4gfD4gfD4gfD4gSGkgYWxsLA0KfD4gfD4gfD4g
fD4NCnw+IHw+IHw+IHw+IEZldyBkYXlzIGFnbyBKdWxpYW4gdGFsa2VkIGFib3V0IFRDTS1URidz
IHNlY3VyaXR5IGFuZCBub3cNCnw+IEkndmUNCnw+IHw+IHw+IHw+IHJlYWQgaW4gdGhlIGxpbmsg
aW5jbHVkZWQgYnkgRGFuLA0KfD4gfD4gfD4gfHNheWluZyB0aGF0IHRoZSBnYWluIG9idGFpbmVk
IHdoZW4gbXVsdGlwbGV4aW5nIElwc2VjLWVuY3J5cHRlZA0KfD4gfD4gfD4gfHBhY2tldHMgaXMg
MjAtdG8tMS4gV2UgaGF2ZSBiZWVuIGxvb2tpbmcgZm9yIG1vcmUgaW5mb3JtYXRpb24NCnw+IHw+
IHw+IHxhYm91dCB0aGlzIGlzc3VlIGFuZCB0aGlua2luZyBhYm91dCBhIHdheSB0byByZWR1Y2Ug
dGhlIG5lZWRlZA0KfD4gfD4gfGJhbmR3aWR0aA0KfD4gfD4gfD4gfGluIElQc2VjIGZsb3dzLg0K
fD4gfD4gfD4gfD4NCnw+IHw+IHw+IHw+IFRoZSBtYWluIGlkZWEgaXMgdG8gZmluZCBhIHdheSB0
byBjaGFuZ2UgdGhlIGF1dGhlbnRpY2F0aW9uIG9mDQp8PiB8PiB8PiB8PiB0aGUgaW5kaXZpZHVh
bCBwYWNrZXRzIGFuZCBtZXJnZQ0KfD4gfD4gfGFsbA0KfD4gfD4gfD4gfG9mIHRoZW0gaW4gYSB1
bmlxdWUgYXV0aGVudGljYXRpb24uIFRodXMsIGluc3RlYWQgb2YgdXNpbmcgMjANCnw+IHw+IHw+
IHxJUHNlYyB0dW5uZWxzLCB3ZSB3b3VsZCBoYXZlIGEgc2luZ2xlIHR1bm5lbCBpbmNsdWRpbmcg
MjAgZmxvd3MuDQp8PiB8PiB8PiB8SXMgdGhpcw0KfD4gfD4gc29tZXRoaW5nIHNpbWlsYXIgdGhh
biBob3cgQ2lzY28gZ2V0cyB0aGUgaW1wcm92ZW1lbnQ/DQp8PiB8PiB8PiB8DQp8PiB8PiB8PiB8
V2Ugd291bGQgbm90IGJlIGFibGUgdG8gY2hhbmdlIElQc2VjIGFueSBtb3JlIHRoYW4gd2UgY291
bGQNCnw+IHw+IHw+IHxjaGFuZ2UgVENQLCBzbyBJIHdvdWxkIG5vdCBsb29rIGF0IGhvdw0KfD4g
fD4gfHRvDQp8PiB8PiB8PiB8Y2hhbmdlIElQc2VjIGF1dGhlbnRpY2F0aW9uLg0KfD4gfD4gfD4g
fA0KfD4gfD4gfD4gfEhvd2V2ZXIsIGlmIHRoZXJlIGFyZSBhIGJ1bmNoIG9mIElQc2VjIHBhY2tl
dHMgc2hhcmluZyBhIGNvbW1vbg0KfD4gfD4gfD4gfHBhdGgsIEkgY291bGQgc2VlIHRoZW0gYmVp
bmcgc3VjY2Vzc2Z1bGx5IG11bHRpcGxleGVkIGludG8gb25lDQp8PiB8PiB8PiB8bGFyZ2VyIHBh
Y2tldCBhdCBvbmUgdHVubmVsIGVuZHBvaW50IGFuZCB0aGVuIGRlLW11bHRpcGxleGVkIGF0DQp8
PiB8PiB8dGhlDQp8PiB8PiB8PiB8b3RoZXIgdHVubmVsIGVuZHBvaW50LiAgVGhpcyBjYW4gcHJv
dmlkZSBhIHBhY2tldCBwZXIgc2Vjb25kDQp8PiB8PiB8PiB8cmVkdWN0aW9uLiAgSSBkb24ndCB0
aGluayB0aGVyZSBhcmUgZW5vdWdoIGJ5dGVzIGluIGFuIElQc2VjDQp8PiB8PiB8PiB8aGVhZGVy
IHRvIGJvdGhlciB0cnlpbmcgdG8gZG8gSVBzZWMgaGVhZGVyIGNvbXByZXNzaW9uIChTUEkgYW5k
DQp8PiB8PiB8PiB8c2VxdWVuY2UNCnw+IHw+IG51bWJlciBhcmUgb25seSA2NCBiaXRzKS4NCnw+
IHw+IHw+IHwNCnw+IHw+IHw+IHwtZA0KfD4gfD4gfD4gfA0KfD4gfD4gfD4gfA0KfD4gfD4gfD4g
fD4NCnw+IHw+IHw+IHw+IEpvc8OpIEx1aXMNCnw+IHw+IHw+IHw+DQp8PiB8PiB8PiB8Pg0KfD4g
fD4gfD4gfD4NCnw+IHw+IHw+IHw+IERhbiBXaW5nIDxkd2luZ0BjaXNjby5jb20+IGhhIGVzY3Jp
dG86DQp8PiB8PiB8PiB8Pg0KfD4gfD4gfD4gfD4+DQp8PiB8PiB8PiB8Pj4gT24gSnVuIDI2LCAy
MDEzLCBhdCAzOjQ5IEFNLCBKb3NlIFNhbGRhbmENCnw+IDxqc2FsZGFuYUB1bml6YXIuZXM+DQp8
PiB8PiB3cm90ZToNCnw+IHw+IHw+IHw+Pg0KfD4gfD4gfD4gfD4+PiBRdWVzdGlvbiA0OiBJcyBU
Q00tVEYgaW50ZXJlc3RpbmcgZm9yIHRoZSBJbmR1c3RyeT8gU2hvdWxkDQp8PiB8PiB8PiB8Pj4+
IHRoZQ0KfD4gfElFVEYNCnw+IHw+IHN0YW5kYXJkaXplIHRoaXM/DQp8PiB8PiB8PiB8Pj4+DQp8
PiB8PiB8PiB8Pj4+IEFuc3dlcjoNCnw+IHw+IHw+IHw+Pj4NCnw+IHw+IHw+IHw+Pj4gMSkgVENN
LVRGIGludGVuZHMgdG8gdXBkYXRlIFJGQzQxNzAsIHdoaWNoIG9wdGltaXplcyBSVFANCnw+IFZv
SVANCnw+IHw+IHw+IHw+Pj4gdHJhZmZpYy4gU28gaWYgUkZDNDE3MCB3YXMNCnw+IHw+IHw+IHxp
bnRlcmVzdGluZywgd2h5IG5vdCB1cGRhdGluZyBpdD8NCnw+IHw+IHw+IHw+Pj4NCnw+IHw+IHw+
IHw+Pj4gMikgVENNLVRGIGNhbiBiZSB1c2VmdWwgaW4gb3JkZXIgdG8gc2F2ZSBiYW5kd2lkdGgg
aW4gbWFueQ0KfD4gY2FzZXM6DQp8PiB8PiB8PiB8Pj4+DQp8PiB8PiB8PiB8Pj4+IC0gQWdncmVn
YXRpb24gbmV0d29yayBvZiAqbmV0d29yayBvcGVyYXRvcnMqOiBXZSBhcmUgc2F2aW5nDQp8PiB8
PiB8PiB8Pj4+IGJhbmR3aWR0aCBieSBvcHRpbWl6aW5nIGFuZA0KfD4gfD4gfHB1dHRpbmcNCnw+
IHw+IHw+IHx0b2dldGhlciB0cmFmZmljIGZsb3dzLiBJcyB0aGlzICBpbnRlcmVzdGluZyBmb3Ig
YSBuZXR3b3JrDQp8PiBvcGVyYXRvcj8NCnw+IHxXaGF0DQp8PiB8PiBhYm91dCBvdmVycHJvdmlz
aW9uaW5nPw0KfD4gfD4gfFRoZQ0KfD4gfD4gfD4gfGlkZWEgaXMgdGhhdCB0aGVyZSBhcmUgcGxh
Y2VzIGFuZCBtb21lbnRzIGluIHdoaWNoIGEgbnVtYmVyIG9mDQp8PiB8PiB8PiB8Zmxvd3MgYmFz
ZWQgb24gc21hbGwgcGFja2V0cyBhcmUgaW4gdGhlIHNhbWUgcGxhY2UgYW5kIGF0IHRoZQ0KfD4g
fD4gfD4gfHNhbWUgbW9tZW50LiBUaGVuLCBUQ00tVEYgY2FuIGJlIGFwcGxpZWQgaW4gb3JkZXIg
dG8gcHJvdmlkZQ0KfD4gfD4gfGZsZXhpYmlsaXR5Lg0KfD4gfD4gfD4gfFdlIGFyZSBub3Qgb3B0
aW1pemluZyB0aGUgb3ZlcmFsbCBJbnRlcm5ldCB0cmFmZmljLCB3ZSAgYXJlDQp8PiB8PiB8PiB8
b3B0aW1pemluZyBzcGVjaWZpYyBmbG93cyB3aXRoIHZlcnkNCnw+IHw+IHx0aWdodA0KfD4gfD4g
fD4gfGRlbGF5IHJlcXVpcmVtZW50cywgIHdoaWNoIG5ldHdvcmsgb3BlcmF0b3JzIGhhdmUgdG8g
dGFrZSBjYXJlDQp8PiBvZg0KfD4gfD4gfD4gfGluIGENCnw+IHw+IHNwZWNpYWwgd2F5Lg0KfD4g
fD4gfD4gfD4+PiB3d3cuaHVhd2VpLmNvbS9pbGluay9lbi9kb3dubG9hZC9IV18xOTMwMzQNCnw+
IHw+IHw+IHw+Pj4NCnw+IHw+IHw+IHw+Pj4gLSAqRW5kIHRvIGVuZCogb3B0aW1pemF0aW9uOiBO
b3dhZGF5cywgbWFueSBhcHBsaWFuY2VzIGFyZQ0KfD4gfD4gfD4gfD4+PiB1c2VkIHRvICBjb25u
ZWN0IHJlbW90ZSBvZmZpY2VzIG9mDQp8PiB8PiB8dGhlDQp8PiB8PiB8PiB8c2FtZSBjb21wYW55
IChjcmVhdGluZyBhIFZQTikuIFNvIGlmICBhIHR1bm5lbCBleGlzdHMsIHdoeSBub3QNCnw+IHw+
IHw+IHxvcHRpbWl6aW5nIHRoaXMgdHJhZmZpYyB3aGVuDQp8PiB8PiB8cG9zc2libGU/DQp8PiB8
PiB8PiB8V2UgIHdvdWxkIHNhdmUgYmFuZHdpZHRoIGluIHRoZSBhY2Nlc3MgbmV0d29yaywgd2hl
cmUgaXQgY2FuIGJlDQp8PiB8PiBzY2FyY2UuDQp8PiB8PiB8PiB8Pj4+DQp8PiB8PiB8PiB8Pj4+
IC0gV2lyZWxlc3MgYW5kIHNhdGVsbGl0ZSBzY2VuYXJpb3MuDQp8PiB8PiB8PiB8Pj4NCnw+IHw+
IHw+IHw+PiAiQ2lzY28gYWRkcyBJUCBtdWx0aXBsZXhpbmcgdG8gbW9iaWxlIHNhdGVsbGl0ZSBw
YWNrYWdlIiwNCnw+IHw+IHw+IHw+PiBBcHJpbCAyMDEyLA0KfD4gfD4gfD4gfGh0dHA6Ly93d3cu
bmV0d29ya3dvcmxkLmNvbS9uZXdzLzIwMTIvMDQwOTEyLWNpc2NvLWlwLQ0KfD4gfD4gbXVsdGlw
bGV4aW5nLTINCnw+IHw+IHw+IHw1ODA4Mi5odG1sDQp8PiB8PiB8PiB8Pj4NCnw+IHw+IHw+IHw+
Pg0KfD4gfD4gfD4gfD4+DQp8PiB8PiB8PiB8Pj4+DQp8PiB8PiB8PiB8Pj4+DQp8PiB8PiB8PiB8
Pj4+IEFueSBvdGhlciB0aG91Z2h0cz8gQW55IG90aGVyIHNjZW5hcmlvcyBpbiBtaW5kPyBQb3Rl
bnRpYWwNCnw+IHw+IGJlbmVmaWNpYXJpZXM/DQp8PiB8PiB8PiB8Pj4NCnw+IHw+IHw+IHw+PiBT
b21lIG5ldHdvcmtzLCB0b2RheSwgdXNlIGNSVFAgKFJGQzI1MDgpIG9uIHRoZWlyIGFjY2Vzcw0K
fD4gbGlua3MuDQp8PiB8VGhpcw0KfD4gfD4gZ2l2ZXMgYmFuZHdpZHRoIHNhdmluZ3MNCnw+IHw+
IHxvbg0KfD4gfD4gfD4gfHRoZSBhY2Nlc3MgbGluaywgYnV0IGNvbnN1bWVzICBjb25zaWRlcmFi
bGUgQ1BVIGhvcnNlcG93ZXIgb24NCnw+IHRoZQ0KfD4gfD4gYWdncmVnYXRpb24gcm91dGVyICh0
byBwZXJmb3JtDQp8PiB8PiB8PiB8Y1JUUCksIGJ1dCBwcm92aWRlcyBubyBiYW5kd2lkdGggc2F2
aW5ncyBhY3Jvc3MgdGhlIG5ldHdvcmsNCnw+IGNvcmUuDQp8PiB8SWYsDQp8PiB8PiBpbnN0ZWFk
LCB0aGUgYmFuZHdpZHRoDQp8PiB8PiB8Y291bGQNCnw+IHw+IHw+IHxiZSBzYXZlZCBvbiB0aGUg
YWNjZXNzIGxpbmssIGFjcm9zcyAgdGhlIGNvcmUsIGFuZCBvbiB0aGUNCnw+IGZhci1lbmQNCnw+
IHw+IHw+IHxhY2Nlc3MgbGluayAtLSBhbGwgd2l0aG91dCB0aGUNCnw+IHw+IHxDUFUNCnw+IHw+
IHw+IHxpbXBhY3Qgb24gdGhlIGFnZ3JlZ2F0aW9uIHJvdXRlciAtLSBpdCBpcyBhIGNvbnNpZGVy
YWJsZSB3aW4uDQp8PiB8PiB8PiB8Pj4NCnw+IHw+IHw+IHw+PiAtZA0KfD4gfD4gfD4gfD4+DQp8
PiB8PiB8PiB8Pj4NCnw+IHw+IHw+IHw+Pg0KfD4gfD4gfD4gfD4+Pg0KfD4gfD4gfD4gfD4+Pg0K
fD4gfD4gfD4gfD4+PiBKb3NlDQp8PiB8PiB8PiB8Pj4+DQp8PiB8PiB8PiB8Pj4+IERlOiB0Y210
Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86dGNtdGYtYm91bmNlc0BpZXRmLm9yZ10NCnw+IEVu
DQp8PiB8PiB8PiB8Pj4+IG5vbWJyZSBkZSBKb3NlIFNhbGRhbmEgRW52aWFkbyBlbDogbHVuZXMs
IDI0IGRlIGp1bmlvIGRlDQp8PiAyMDEzDQp8PiB8PiB8PiB8Pj4+IDEzOjAwDQp8PiB8PiB8PiB8
Pj4+IFBhcmE6IHRjbXRmQGlldGYub3JnDQp8PiB8PiB8PiB8Pj4+IEFzdW50bzogW3RjbXRmXSBB
bnN3ZXJzIHRvIHBvc3NpYmxlIHF1ZXN0aW9ucyBpbiB0aGUgQk9GDQp8PiB8PiB8PiB8Pj4+DQp8
PiB8PiB8PiB8Pj4+IEkgd291bGQgbGlrZSB0byBzdGFydCBhIHRocmVhZCBhYm91dCBwb3NzaWJs
ZSBxdWVzdGlvbnMNCnw+IHw+IHw+IHw+Pj4gcGVvcGxlIG1heSAgYXNrIGluIHRoZSBCT0YuIE9i
dmlvdXNseSwNCnw+IHw+IHx3ZQ0KfD4gfD4gfD4gfGFsc28gbmVlZCBhbnN3ZXJzLCBzbyB3ZSBz
aG91bGQgIGNvb3BlcmF0ZS4NCnw+IHw+IHw+IHw+Pj4NCnw+IHw+IHw+IHw+Pj4gVGhpcyBpcyBk
aWZmZXJlbnQgZnJvbSB0aGUgInF1ZXN0aW9ucyB0byBhc2sgaW4gdGhlIEJPRiIuDQp8PiB8PiB8
PiB8Pj4+IFRoaXMNCnw+IHx3aWxsICBiZQ0KfD4gfD4gZGlzY3Vzc2VkIHNlcGFyYXRlbHkuDQp8
PiB8PiB8PiB8Pj4+DQp8PiB8PiB8PiB8Pj4+IFRoYW5rcyENCnw+IHw+IHw+IHw+Pj4NCnw+IHw+
IHw+IHw+Pj4gSm9zZQ0KfD4gfD4gfD4gfD4+Pg0KfD4gfD4gfD4gfD4+PiBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KfD4gfD4gfD4gfD4+PiB0Y210ZiBt
YWlsaW5nIGxpc3QNCnw+IHw+IHw+IHw+Pj4gdGNtdGZAaWV0Zi5vcmcNCnw+IHw+IHw+IHw+Pj4g
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90Y210Zg0KfD4gfD4gfD4gfD4+
DQp8PiB8PiB8PiB8Pj4NCnw+IHw+IHw+IHw+DQp8PiB8PiB8PiB8Pg0KfD4gfD4gfD4gfD4NCnw+
IHw+IHw+IHwNCnw+IHw+IHw+IHxfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KfD4gfD4gfD4gfHRjbXRmIG1haWxpbmcgbGlzdA0KfD4gfD4gfD4gfHRjbXRm
QGlldGYub3JnDQp8PiB8PiB8PiB8aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by90Y210Zg0KfD4gfD4NCnw+IHw+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQp8PiB8PiB0Y210ZiBtYWlsaW5nIGxpc3QNCnw+IHw+IHRjbXRmQGlldGYu
b3JnDQp8PiB8PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQp8
Pg0KfD4NCnw+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQp8PiB0Y210ZiBtYWlsaW5nIGxpc3QNCnw+IHRjbXRmQGlldGYub3JnDQp8PiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQo=

From dwing@cisco.com  Fri Jul 12 08:42:16 2013
Return-Path: <dwing@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 DB0BB21F91BF for <tcmtf@ietfa.amsl.com>; Fri, 12 Jul 2013 08:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.477
X-Spam-Level: 
X-Spam-Status: No, score=-110.477 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 dMWD+qhb1mCo for <tcmtf@ietfa.amsl.com>; Fri, 12 Jul 2013 08:42:12 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 4D90F11E811A for <tcmtf@ietf.org>; Fri, 12 Jul 2013 08:42:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14802; q=dns/txt; s=iport; t=1373643726; x=1374853326; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=Lb8Xu8kewoB51OtB3gBE8HMxYcSGJ07qGPMA/nDlYuo=; b=F9kYDfHfAE9awvWRX7UOQsUrSx+j/RW9ZE0Fvg5OZVVb2b0g6XV8sxoi fN/GUlKxznNIQ78IOeFtvCWiwD1iWfAbKS3GWG0UidzQ/2idCH4ZXFu8E xj2dlfxqCUImfIS+Q0qBkbafftj2UpirVaSTTFVp1GvbG+Zfa7WlP6YNR s=;
X-IronPort-AV: E=Sophos;i="4.89,653,1367971200"; d="scan'208";a="85875031"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 12 Jul 2013 15:42:04 +0000
Received: from sjc-vpn3-1253.cisco.com (sjc-vpn3-1253.cisco.com [10.21.68.229]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r6CFg3Xm022034; Fri, 12 Jul 2013 15:42:03 GMT
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <002301ce7beb$5c198370$144c8a50$@unizar.es>
Date: Fri, 12 Jul 2013 08:42:03 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <341D9E54-28BF-4C85-A15C-EC06E203EE66@cisco.com>
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>	<009901ce725a$d1623360$74269a20$@unizar.es>	<2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>"	<20130628105725.lmag0xgqsgogggww@webmail.unizar.es>	<004601ce7bac$c8fc91b0$5af5b510$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CD0C7F1@EX10-MB2-MAD.hi.inet> <002301ce7beb$5c198370$144c8a50$@unizar.es>
To: <jsaldana@unizar.es>
X-Mailer: Apple Mail (2.1508)
Cc: tcmtf@ietf.org, "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>, "'Diego R. Lopez'" <diego@tid.es>, 'jsalazar' <jsalazar@unizar.es>
Subject: Re: [tcmtf] Answers to possible questions in 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: Fri, 12 Jul 2013 15:42:17 -0000

On Jul 8, 2013, at 7:56 AM, Jose Saldana <jsaldana@unizar.es> wrote:

> So it seems that the possibility of a document about Security & TCM-TF =
might
> be interesting. What about adding a sentence in the Charter =
(re-chartering
> paragraph), talking about that possibility?
>=20
> ....
> 9. If other interesting features are identified, the group would =
re-charter
> and include them, e.g., a=20
> mechanism for a multiplexer to discover a de-multiplexer, and vice =
versa; a
> mechanism to select an=20
> optimal multiplexer and a de-multiplexer when there are more than one
> muxer/de-muxer for a flow;=20
> dynamically applying TCMTF: a higher entity in charge of deciding when =
and
> where, applying or not=20
> TCMTF, and what kind of TCMTF, and what multiplexing period. =
Additional
> methods for estimating delay=20
> would also be required; *security issues related to TCM-TF, and =
methods for
> securing TCM optimized flows.*


This text detracts from the charter, because it lists only one reason we =
might re-charter to broaden the WG's scope.  There are lots of reasons =
we might re-charter to broaden the WG's scope, of course.  So I don't =
think this text is really saying anything that needs to be said.

-d


> ....
>=20
> Jose
>=20
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
>> Diego R. Lopez
>> Enviado el: lunes, 08 de julio de 2013 11:59
>> Para: <jsaldana@unizar.es>
>> CC: <tcmtf@ietf.org>; Muthu Arul Mozhi Perumal (mperumal); jsalazar; =
Dan
>> Wing
>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>>=20
>> Hi,
>>=20
>> When talking about security, we should not forget two different =
aspects:
>>=20
>> 1) Applying TCMTF to enhance (or provide a better support to) =
security
>> network services, like IPsec or VPNs
>>=20
>> 2) Securing the application of TCMTF itself
>>=20
>> As far as I can tell, most of the discussion so far has been on the =
first
> aspect.
>> This could be outlined as an use case, and further discussed in a =
separate
>> document if required, oriented towards "Applying TCMTF in secure
>> environments" or the like
>>=20
>> Regarding the second issue, I tried to make a few points some time =
ago:
>>=20
>> 8<---
>>=20
>>> We can consider different security contexts for different tunnels,
> according
>> to some policy agreed by both end-points at a given tunnel. The =
security
>> contexts would define encryption, authentication, or both. We'd have =
to go
>> into more detail to evaluate potential savings, but I have the =
feeling
> they
>> could be worth considering.
>>>=20
>>> The point is that if we go for these different security contexts, we
> must
>> consider how they can be established by mutual authentication of the
> tunnel
>> end-points, and this opens additional issues regarding configuration =
and
>> crypto material exchange, as well as the possibility of =
user-initiated
>> authentication by means of protocols like OAuth.
>>>=20
>>> I'd keep this in the list of the "soon-to-open" issues, focusing on =
the
> three
>> main docs we have been discussing so far.
>>=20
>> 8<---
>>=20
>> I had the intention to elaborate them a little more, but other =
matters
> pre-
>> empted this :-( My take is that some reflections on this should be
> included in
>> the "Security Considerations" section of the framework document, and =
a
>> further document on this be considered in a further stage.
>>=20
>> Be goode,
>>=20
>> On 8 Jul 2013, at 09:28 , Jose Saldana wrote:
>>=20
>>> Hi, Muthu, Dan, Jose Luis.
>>>=20
>>> It seems that we have identified some cases in which different =
security
>> options are possible. The question here is:
>>>=20
>>> Can this be issued in the TCMTF main draft (TCMTF Reference Model)?
>>>=20
>>> Or do you think a TCMTF-security document would be interesting?
>>>=20
>>> Jose
>>>=20
>>> -----Mensaje original-----
>>> De: jsalazar [mailto:jsalazar@unizar.es] Enviado el: jueves, 04 de
>>> julio de 2013 19:36
>>> Para: jsaldana@unizar.es
>>> Asunto: RE: [tcmtf] Answers to possible questions in the BOF
>>>=20
>>> Hi all.
>>> With your last question, you have just hit the bullseye. I think the
>> classification is correct. Cases 1 and 2a are a good way to keep the
>> compromise between security and efficency. However, case 2b gives a =
step
>> beyond and the security is compromised in the interest of efficiency.
>>> In that case, users have to trust in tcmtf manager for managing =
their
>>> privacy also. Then, we will leave the tipical Public Key
>>> Infraestructure
>>> (PKI) security architecture and use the Identity Based Encryption =
(IBE)
> one
>> (http://tools.ietf.org/html/rfc5408).
>>> They are three different scenarios and all of them seem to be very
>> interesting, but the last one a bit more.
>>> Regards:
>>>=20
>>> JL
>>>=20
>>> "I see them falling out the skies like eagles All mirrored glass and
> shattered
>> egos"
>>>=20
>>> Simple Minds.
>>>=20
>>> El 2013-07-03 17:58, Jose Saldana escribi=F3:
>>>> Hi, Jose Luis. Good point.
>>>>=20
>>>> Regarding security, we could establish this classification:
>>>>=20
>>>> 1- Adding security to TCM: I have a number of non-secured flows
>>>> traveling through a "dangerous" network segment (perhaps a tunnel
>>>> between appliances connecting remote offices of a company), and I
>>>> want not only traffic optimization but also security. In this case, =
I
>>>> can simply use IPsec on the tunnel.
>>>>=20
>>>>=20
>>>> 2- Using TCM for optimizing already secured communications: I have =
a
>>>> bunch of already secured flows. Which is the best way for =
tunneling,
>>>> compressing and multiplexing them?
>>>>=20
>>>> Two subcases:
>>>>=20
>>>> 2a- I can use TCM normally, but not only compress IP, TCP or UDP
>>>> headers, but also security headers using a header compression =
method.
>>>> Some possibilities for compressing security headers:
>>>>=20
>>>> - ROHCoIPsec, RFC5856 (http://tools.ietf.org/html/rfc5856)
>>>> - RFC5225 http://tools.ietf.org/html/rfc5225
>>>>=20
>>>>=20
>>>> 2b- But I can save more bandwidth if the TCM-ingress optimizer
>>>> (TCM-IO) is able to:
>>>> - rebuild the packets to their native form
>>>> - TCM-optimize them
>>>> - put them into a single security tunnel
>>>>=20
>>>> I have three phases (let's suppose I have 20 communications):
>>>>=20
>>>> Origin 1
>>>> Origin 2     <----20 secured flows --------> TCM-IO <------1
>>>> tunnel------> TCM-EO <-------- 20 secured flows----> destination 1,
>>>> tunnel------> 2,
>>>> 20
>>>> ...
>>>> Origin 20
>>>>=20
>>>> I have an advantage: In the shared network path, I use a single
>>>> tunnel instead of 20 different tunnels.
>>>>=20
>>>> But I have some additional requirements: I need processing capacity
>>>> in the TCM optimizers, and the endpoints should trust them.
>>>>=20
>>>>=20
>>>> Is this classification correct? Any other options? Any other
>>>> requirements? It is time for "security experts".
>>>>=20
>>>> Jose
>>>>=20
>>>> -----Mensaje original-----
>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
>>>> de jsalazar Enviado el: lunes, 01 de julio de 2013 20:50
>>>> Para: tcmtf@ietf.org
>>>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>>>>=20
>>>> Hi all:
>>>> Mmmmmmm. Since I see tcm-tf as a service, I can design the service
>>>> with added security features that the type of communication is
>>>> requiring. I think we have to be clear what we are expressing when =
we
>>>> are talking about secure tcm-tf: Ensuring the service tcm-tf or
>>>> applying the tcm-tf service for secure communications.
>>>> The first possibility is not a great technological sophistication =
and
>>>> the second one might consider the first one as a possible =
additional
>>>> service.
>>>> Therefore,
>>>> every time we use the term "secure tcm-tf" should think the second
>>>> option, for generality.
>>>> On the other hand, we must also keep in mind that whenever users
>>>> employ secure tcm-tf, they must trust the service fully and =
consider
>>>> delegating the use of their keys (including private ones) to =
tcm-tf.
>>>>=20
>>>> Regards.
>>>>=20
>>>> JL
>>>>=20
>>>> "I see them falling out the skies like eagles All mirrored glass =
and
>>>> shattered egos"
>>>>=20
>>>> Simple Minds.
>>>>=20
>>>> El 2013-07-01 18:55, Dan Wing escribi=F3:
>>>>> On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
>>>>>=20
>>>>> Hi all,
>>>>>=20
>>>>> Few days ago Julian talked about TCM-TF's security and now I've =
read
>>>>> in the link included by Dan, saying that the gain obtained when
>>>>> multiplexing Ipsec-encrypted packets is 20-to-1. We have been
>>>>> looking for more information about this issue and thinking about a
>>>>> way to reduce the needed  bandwidth in IPsec flows.
>>>>>=20
>>>>> The main idea is to find a way to change the authentication of the
>>>>> individual packets and merge all of them in a unique =
authentication.
>>>>> Thus, instead of using 20 IPsec tunnels, we would have a single
>>>>> tunnel including 20 flows. Is this something similar than how =
Cisco
>>>>> gets the improvement?
>>>>>=20
>>>>> We would not be able to change IPsec any more than we could change
>>>>> TCP, so I would not look at how to change IPsec authentication.
>>>>>=20
>>>>> However, if there are a bunch of IPsec packets sharing a common
>>>>> path, I could see them being successfully multiplexed into one
>>>>> larger packet at one tunnel endpoint and then de-multiplexed at =
the
>>>>> other tunnel endpoint.  This can provide a packet per second
>>>>> reduction.  I don't think there are enough bytes in an IPsec =
header
>>>>> to bother trying to do IPsec header compression (SPI and sequence
>> number are only 64 bits).
>>>>>=20
>>>>> -d
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> Jos=E9 Luis
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> Dan Wing <dwing@cisco.com> ha escrito:
>>>>>=20
>>>>>=20
>>>>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es> =
wrote:
>>>>>=20
>>>>> Question 4: Is TCM-TF interesting for the Industry? Should the =
IETF
>>>>> standardize this?
>>>>>=20
>>>>> Answer:
>>>>>=20
>>>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP
> traffic.
>>>>> So if RFC4170 was interesting, why not updating it?
>>>>>=20
>>>>> 2) TCM-TF can be useful in order to save bandwidth in many cases:
>>>>>=20
>>>>> - Aggregation network of *network operators*: We are saving
>>>>> bandwidth by optimizing and putting together traffic flows. Is =
this
>>>>> interesting for a network operator? What about overprovisioning?
>>>>> The idea is that there are places and moments in which a number of
>>>>> flows based on small packets are in the same place and at the same
>>>>> moment. Then, TCM-TF can be applied in order to provide =
flexibility.
>>>>> We are not optimizing the overall Internet traffic, we are
>>>>> optimizing specific flows with very tight delay requirements, =
which
>>>>> network operators have to take care of in a special way.
>>>>> www.huawei.com/ilink/en/download/HW_193034
>>>>>=20
>>>>> - *End to end* optimization: Nowadays, many appliances are used to
>>>>> connect remote offices of the same company (creating a VPN). So if =
a
>>>>> tunnel exists, why not optimizing this traffic when possible? We
>>>>> would save bandwidth in the access network, where it can be =
scarce.
>>>>>=20
>>>>> - Wireless and satellite scenarios.
>>>>>=20
>>>>> "Cisco adds IP multiplexing to mobile satellite package", April
>>>>> 2012,
>>>>> http://www.networkworld.com/news/2012/040912-cisco-ip-
>> multiplexing-
>>>> 258082.html
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> Any other thoughts? Any other scenarios in mind? Potential
>>>>> beneficiaries?
>>>>>=20
>>>>> Some networks, today, use cRTP (RFC2508) on their access links.   =
This
>>>>> gives bandwidth savings on the access link, but consumes
>>>>> considerable CPU horsepower on the aggregation router (to perform
>> cRTP), but
>>>>> provides no bandwidth savings across the network core.   If, =
instead,
>>>>> the bandwidth could be saved on the access link, across  the core,
>>>>> and on the far-end access link -- all without the CPU  impact on =
the
>>>>> aggregation router -- it is a considerable win.
>>>>>=20
>>>>> -d
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> Jose
>>>>>=20
>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> nombre
>>>>> de Jose Saldana Enviado el: lunes, 24 de junio de 2013 13:00
>>>>> Para: tcmtf@ietf.org
>>>>> Asunto: [tcmtf] Answers to possible questions in the BOF
>>>>>=20
>>>>> I would like to start a thread about possible questions people may
>>>>> ask in the BOF. Obviously, we also need answers, so we should
>> cooperate.
>>>>>=20
>>>>> This is different from the "questions to ask in the BOF". This =
will
>>>>> be discussed separately.
>>>>>=20
>>>>> Thanks!
>>>>>=20
>>>>> Jose
>>>>>=20
>>>>> _______________________________________________
>>>>> tcmtf mailing list
>>>>> tcmtf@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> 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
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>=20
>>=20
>> --
>> "Esta vez no fallaremos, Doctor Infierno"
>>=20
>> Dr Diego R. Lopez
>> Telefonica I+D
>> http://people.tid.es/diego.lopez/
>>=20
>> e-mail: diego@tid.es
>> Tel:    +34 913 129 041
>> Mobile: +34 682 051 091
>> -----------------------------------------
>>=20
>>=20
>> ________________________________
>>=20
>> Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar
>> nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico =
en el enlace
>> situado m=E1s abajo.
>> This message is intended exclusively for its addressee. We only send =
and
>> receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>=20


From dwing@cisco.com  Fri Jul 12 08:53:22 2013
Return-Path: <dwing@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 407BC21F9ECE for <tcmtf@ietfa.amsl.com>; Fri, 12 Jul 2013 08:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.485
X-Spam-Level: 
X-Spam-Status: No, score=-110.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 ZjF5aRY3wetd for <tcmtf@ietfa.amsl.com>; Fri, 12 Jul 2013 08:53:17 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 510F721F9E77 for <tcmtf@ietf.org>; Fri, 12 Jul 2013 08:53:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19784; q=dns/txt; s=iport; t=1373644395; x=1374853995; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=b+dTAaSICdRrSTgBXFdI/QpiiT5ZeMSmg1S6BAGU4e8=; b=Z3bwsZr4EjUCgzY1nZJspOMSvivTlVBsuKm9bn/E+uOsvj+zICkjiqSy hIonVVtW9gCjOcUmLrTOFKtDJgcGDgSbuEMJEx3vp8aOL5C0Cf1NWcLc1 /utvMTf/CrWnNTZjpmmFaBfHGweRXFZffFrX2sDkpUP9VDiFDNwUmugWe g=;
X-IronPort-AV: E=Sophos;i="4.89,654,1367971200"; d="scan'208";a="85810458"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 12 Jul 2013 15:53:12 +0000
Received: from sjc-vpn3-1253.cisco.com (sjc-vpn3-1253.cisco.com [10.21.68.229]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r6CFrBhF027695; Fri, 12 Jul 2013 15:53:11 GMT
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <007a01ce7d42$3260a0b0$9721e210$@unizar.es>
Date: Fri, 12 Jul 2013 08:53:11 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <961D17FB-C262-41A9-88C8-AF1B0CF32BD6@cisco.com>
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>" <20130628105725.lmag0xgqsgogggww@webmail.unizar.es> <004601ce7bac$c8fc91b0$5af5b510$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CD0C7F1@EX10-MB2-MAD.hi.inet> <00b001ce7c91$1dcc6640$596532c0$@unizar.es> <408173bf1a2c57640e76ca5e8808a01b.squirrel@www.erg.abdn.ac.uk> <007a01ce7d42$3260a0b0$9721e210$@unizar.es>
To: <jsaldana@unizar.es>
X-Mailer: Apple Mail (2.1508)
Cc: gorry@erg.abdn.ac.uk, tcmtf@ietf.org, "'Diego R. Lopez'" <diego@tid.es>, 'jsalazar' <jsalazar@unizar.es>, "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>
Subject: Re: [tcmtf] Answers to possible questions in 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: Fri, 12 Jul 2013 15:53:22 -0000

On Jul 10, 2013, at 12:50 AM, Jose Saldana <jsaldana@unizar.es> wrote:

> What about these "security considerations"? (including Gorry's =
suggestions):
>=20
> ------
> The most straightforward option for securing a number of non-secured =
flows
> sharing a path is by the use of IPsec [IPsec], when TCM using an IP =
tunnel
> is employed. Instead of adding a security header to the packets of =
each
> native flow, and then compressing and multiplexing them, a single =
IPsec
> tunnel can be used in order to secure all the flows together, thus =
achieving
> a higher efficiency. This use of IPsec protects the packets only =
within the
> transport network between tunnel ingress and egress and therefore does =
not
> provide end-to-end authentication or encryption. In some cases , e.g., =
where
> the end points are trusted, this model may be appropriate.

I was agreeing with you until the example, which suggests endpoint trust =
is somehow useful/important for using IPsec to protect traffic.  It is =
not relevant if the endpoints are trusted (botnet traffic is perfectly =
okay to get put inside an IPsec tunnel); rather, it is relevant to use =
IPsec if the IPsec-protected path is vulnerable to attack (passive =
attack [sniffing] or active attack [injection]).

I would just drop that last sentence (the sentence starting with "In =
some case, ...").

> When a number of already secured flows including ESP [RFC4303] headers =
are
> optimized by means of TCM, and the addition of further security is not
> necessary, their ESP/IP headers can still be compressed using suitable
> algorithms [RFC5225], in order to improve the efficiency. This header
> compression does not change the end-to-end security model.
>=20
> Future versions of this document will consider whether some TCM-TF
> mechanisms could be potentially exploited in order to deploy or =
amplify DoS
> attacks against network infrastructure.
> -----

Gorry was worried about DoS of TCMTF itself, too.  So change last =
paragraph to also say "will consider DoS vulnerability of TCM-TF itself" =
in addition to what you already have about TCMTF being used to create a =
DoS attack against other stuff.  But, keeping it simpler, how about just =
saying:  "The resilience of TCM-TF to denial of service, and the use of =
TCM-TF to deny service to other parts of the network infrastructure, is =
for future study."

-d


> Do you think the third paragraph should be included in this version? =
Should
> we wait before talking about that?
>=20
> Thanks, Gorry,
>=20
> Jose
>=20
>> -----Mensaje original-----
>> De: gorry@erg.abdn.ac.uk [mailto:gorry@erg.abdn.ac.uk]
>> Enviado el: martes, 09 de julio de 2013 12:56
>> Para: jsaldana@unizar.es
>> CC: 'Diego R. Lopez'; tcmtf@ietf.org; 'Muthu Arul Mozhi Perumal
>> (mperumal)'; 'jsalazar'; 'Dan Wing'
>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>>=20
>> A few comments on the security considerations.
>>=20
>> Can you also please add the counter-argument to using IPsec?
>>=20
>> - This use of IPsec protects the packets only within the transport =
network
>> between tunnel ingress and egress and therefore does not provide =
end-to-
>> end authentication or encryption. In some cases , e.g. where the end
> points
>> are trusted this model may be appropriate.
>>=20
>> - On the second point, please clarify:
>> -- which headers are compressed?
>> -- does this change the end-to-end security model (I think not).
>>=20
>> I suggest you quote RFCs for the security mechanisms that you =
discuss.
>>=20
>> Finally, you may like to consider DoS attacks against TCMTF. =
Transport
> groups
>> are usually required to consider whether the mechanisms can be =
exploited
>> to generate traffic that does not respond to congestion control or =
can be
>> used to amplify the attack on network infrastructure. If you can =
comment
> on
>> these that would seem good - I suggest you should note this as future =
work
>> in later revisions of the draft.
>>=20
>> Gorry
>>=20
>>=20
>>> Hi all,
>>>=20
>>> I am finishing the next version of the draft. In the "security
>>> considerations" section in the end. The idea is talking about the =
two
>>> options (as summarized by Diego):
>>>=20
>>> - Securing the application of TCMTF itself
>>> - Applying TCMTF to enhance (or provide a better support to) =
security
>>> network services, like IPsec or VPNs
>>>=20
>>> So I would include these two paragraphs, if you agree:
>>>=20
>>>=20
>>> The most straightforward option for securing a number of non-secured
>>> flows sharing a path is by the use of IPsec [IPsec], when TCM using =
an
>>> IP tunnel is employed. Instead of adding a security header to the
>>> packets of each native flow, and then compressing and multiplexing, =
a
>>> single IPsec tunnel can be used in order to secure all the flows
>>> together, thus achieving a better efficiency.
>>>=20
>>> When a number of already secured flows including ESP headers is
>>> optimized by means of TCM, and the addition of further security is =
not
>>> necessary, their ESP headers can still be compressed using suitable
>>> algorithms, in order to improve the efficiency.
>>>=20
>>>=20
>>> Any improvements? Any other ideas?
>>>=20
>>> Jose
>>>=20
>>>> -----Mensaje original-----
>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
>>>> de Diego R. Lopez Enviado el: lunes, 08 de julio de 2013 11:59
>>>> Para: <jsaldana@unizar.es>
>>>> CC: <tcmtf@ietf.org>; Muthu Arul Mozhi Perumal (mperumal); =
jsalazar;
>>>> Dan Wing
>>>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>>>>=20
>>>> Hi,
>>>>=20
>>>> When talking about security, we should not forget two different
> aspects:
>>>>=20
>>>> 1) Applying TCMTF to enhance (or provide a better support to)
>>>> security network services, like IPsec or VPNs
>>>>=20
>>>> 2) Securing the application of TCMTF itself
>>>>=20
>>>> As far as I can tell, most of the discussion so far has been on the
>>>> first
>>> aspect.
>>>> This could be outlined as an use case, and further discussed in a
>>>> separate document if required, oriented towards "Applying TCMTF in
>>>> secure environments" or the like
>>>>=20
>>>> Regarding the second issue, I tried to make a few points some time =
ago:
>>>>=20
>>>> 8<---
>>>>=20
>>>>> We can consider different security contexts for different tunnels,
>>> according
>>>> to some policy agreed by both end-points at a given tunnel. The
>>>> security contexts would define encryption, authentication, or both.
>>>> We'd have to go into more detail to evaluate potential savings, but =
I
>>>> have the feeling
>>> they
>>>> could be worth considering.
>>>>>=20
>>>>> The point is that if we go for these different security contexts,
>>>>> we
>>> must
>>>> consider how they can be established by mutual authentication of =
the
>>> tunnel
>>>> end-points, and this opens additional issues regarding =
configuration
>>>> and crypto material exchange, as well as the possibility of
>>>> user-initiated authentication by means of protocols like OAuth.
>>>>>=20
>>>>> I'd keep this in the list of the "soon-to-open" issues, focusing =
on
>>>> the
>>> three
>>>> main docs we have been discussing so far.
>>>>=20
>>>> 8<---
>>>>=20
>>>> I had the intention to elaborate them a little more, but other
>>>> matters
>>> pre-
>>>> empted this :-( My take is that some reflections on this should be
>>> included in
>>>> the "Security Considerations" section of the framework document, =
and
>>>> a further document on this be considered in a further stage.
>>>>=20
>>>> Be goode,
>>>>=20
>>>> On 8 Jul 2013, at 09:28 , Jose Saldana wrote:
>>>>=20
>>>>> Hi, Muthu, Dan, Jose Luis.
>>>>>=20
>>>>> It seems that we have identified some cases in which different
>>>> security
>>>> options are possible. The question here is:
>>>>>=20
>>>>> Can this be issued in the TCMTF main draft (TCMTF Reference =
Model)?
>>>>>=20
>>>>> Or do you think a TCMTF-security document would be interesting?
>>>>>=20
>>>>> Jose
>>>>>=20
>>>>> -----Mensaje original-----
>>>>> De: jsalazar [mailto:jsalazar@unizar.es] Enviado el: jueves, 04 de
>>>>> julio de 2013 19:36
>>>>> Para: jsaldana@unizar.es
>>>>> Asunto: RE: [tcmtf] Answers to possible questions in the BOF
>>>>>=20
>>>>> Hi all.
>>>>> With your last question, you have just hit the bullseye. I think
>>>>> the
>>>> classification is correct. Cases 1 and 2a are a good way to keep =
the
>>>> compromise between security and efficency. However, case 2b gives a
>>>> step beyond and the security is compromised in the interest of
> efficiency.
>>>>> In that case, users have to trust in tcmtf manager for managing
>>>>> their privacy also. Then, we will leave the tipical Public Key
>>>>> Infraestructure
>>>>> (PKI) security architecture and use the Identity Based Encryption
>>>> (IBE)
>>> one
>>>> (http://tools.ietf.org/html/rfc5408).
>>>>> They are three different scenarios and all of them seem to be very
>>>> interesting, but the last one a bit more.
>>>>> Regards:
>>>>>=20
>>>>> JL
>>>>>=20
>>>>> "I see them falling out the skies like eagles All mirrored glass
>>>>> and
>>> shattered
>>>> egos"
>>>>>=20
>>>>> Simple Minds.
>>>>>=20
>>>>> El 2013-07-03 17:58, Jose Saldana escribi=F3:
>>>>>> Hi, Jose Luis. Good point.
>>>>>>=20
>>>>>> Regarding security, we could establish this classification:
>>>>>>=20
>>>>>> 1- Adding security to TCM: I have a number of non-secured flows
>>>>>> traveling through a "dangerous" network segment (perhaps a tunnel
>>>>>> between appliances connecting remote offices of a company), and I
>>>>>> want not only traffic optimization but also security. In this
>>>>>> case, I can simply use IPsec on the tunnel.
>>>>>>=20
>>>>>>=20
>>>>>> 2- Using TCM for optimizing already secured communications: I =
have
>>>>>> a bunch of already secured flows. Which is the best way for
>>>>>> tunneling, compressing and multiplexing them?
>>>>>>=20
>>>>>> Two subcases:
>>>>>>=20
>>>>>> 2a- I can use TCM normally, but not only compress IP, TCP or UDP
>>>>>> headers, but also security headers using a header compression
>> method.
>>>>>> Some possibilities for compressing security headers:
>>>>>>=20
>>>>>> - ROHCoIPsec, RFC5856 (http://tools.ietf.org/html/rfc5856)
>>>>>> - RFC5225 http://tools.ietf.org/html/rfc5225
>>>>>>=20
>>>>>>=20
>>>>>> 2b- But I can save more bandwidth if the TCM-ingress optimizer
>>>>>> (TCM-IO) is able to:
>>>>>> - rebuild the packets to their native form
>>>>>> - TCM-optimize them
>>>>>> - put them into a single security tunnel
>>>>>>=20
>>>>>> I have three phases (let's suppose I have 20 communications):
>>>>>>=20
>>>>>> Origin 1
>>>>>> Origin 2     <----20 secured flows --------> TCM-IO <------1
>>>>>> tunnel------> TCM-EO <-------- 20 secured flows----> destination
>>>>>> tunnel------> 1, 2,
>>>>>> 20
>>>>>> ...
>>>>>> Origin 20
>>>>>>=20
>>>>>> I have an advantage: In the shared network path, I use a single
>>>>>> tunnel instead of 20 different tunnels.
>>>>>>=20
>>>>>> But I have some additional requirements: I need processing
>>>>>> capacity in the TCM optimizers, and the endpoints should trust =
them.
>>>>>>=20
>>>>>>=20
>>>>>> Is this classification correct? Any other options? Any other
>>>>>> requirements? It is time for "security experts".
>>>>>>=20
>>>>>> Jose
>>>>>>=20
>>>>>> -----Mensaje original-----
>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>>>>>> nombre de jsalazar Enviado el: lunes, 01 de julio de 2013 20:50
>>>>>> Para: tcmtf@ietf.org
>>>>>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>>>>>>=20
>>>>>> Hi all:
>>>>>> Mmmmmmm. Since I see tcm-tf as a service, I can design the =
service
>>>>>> with added security features that the type of communication is
>>>>>> requiring. I think we have to be clear what we are expressing =
when
>>>>>> we are talking about secure tcm-tf: Ensuring the service tcm-tf =
or
>>>>>> applying the tcm-tf service for secure communications.
>>>>>> The first possibility is not a great technological sophistication
>>>>>> and the second one might consider the first one as a possible
>>>>>> additional service.
>>>>>> Therefore,
>>>>>> every time we use the term "secure tcm-tf" should think the =
second
>>>>>> option, for generality.
>>>>>> On the other hand, we must also keep in mind that whenever users
>>>>>> employ secure tcm-tf, they must trust the service fully and
>>>>>> consider delegating the use of their keys (including private =
ones)
> to
>> tcm-tf.
>>>>>>=20
>>>>>> Regards.
>>>>>>=20
>>>>>> JL
>>>>>>=20
>>>>>> "I see them falling out the skies like eagles All mirrored glass
>>>>>> and shattered egos"
>>>>>>=20
>>>>>> Simple Minds.
>>>>>>=20
>>>>>> El 2013-07-01 18:55, Dan Wing escribi=F3:
>>>>>>> On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
>>>>>>>=20
>>>>>>> Hi all,
>>>>>>>=20
>>>>>>> Few days ago Julian talked about TCM-TF's security and now I've
>>>>>>> read in the link included by Dan, saying that the gain obtained
>>>>>>> when multiplexing Ipsec-encrypted packets is 20-to-1. We have
>>>>>>> been looking for more information about this issue and thinking
>>>>>>> about a way to reduce the needed  bandwidth in IPsec flows.
>>>>>>>=20
>>>>>>> The main idea is to find a way to change the authentication of
>>>>>>> the individual packets and merge all of them in a unique
>> authentication.
>>>>>>> Thus, instead of using 20 IPsec tunnels, we would have a single
>>>>>>> tunnel including 20 flows. Is this something similar than how
>>>>>>> Cisco gets the improvement?
>>>>>>>=20
>>>>>>> We would not be able to change IPsec any more than we could
>>>>>>> change TCP, so I would not look at how to change IPsec
>> authentication.
>>>>>>>=20
>>>>>>> However, if there are a bunch of IPsec packets sharing a common
>>>>>>> path, I could see them being successfully multiplexed into one
>>>>>>> larger packet at one tunnel endpoint and then de-multiplexed at
>>>>>>> the other tunnel endpoint.  This can provide a packet per second
>>>>>>> reduction.  I don't think there are enough bytes in an IPsec
>>>>>>> header to bother trying to do IPsec header compression (SPI and
>>>>>>> sequence
>>>> number are only 64 bits).
>>>>>>>=20
>>>>>>> -d
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> Jos=E9 Luis
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> Dan Wing <dwing@cisco.com> ha escrito:
>>>>>>>=20
>>>>>>>=20
>>>>>>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es>
>>>> wrote:
>>>>>>>=20
>>>>>>> Question 4: Is TCM-TF interesting for the Industry? Should the
>>>>>>> IETF standardize this?
>>>>>>>=20
>>>>>>> Answer:
>>>>>>>=20
>>>>>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP
>>> traffic.
>>>>>>> So if RFC4170 was interesting, why not updating it?
>>>>>>>=20
>>>>>>> 2) TCM-TF can be useful in order to save bandwidth in many =
cases:
>>>>>>>=20
>>>>>>> - Aggregation network of *network operators*: We are saving
>>>>>>> bandwidth by optimizing and putting together traffic flows. Is
>>>>>>> this interesting for a network operator? What about
>> overprovisioning?
>>>>>>> The idea is that there are places and moments in which a number
>>>>>>> of flows based on small packets are in the same place and at the
>>>>>>> same moment. Then, TCM-TF can be applied in order to provide
>> flexibility.
>>>>>>> We are not optimizing the overall Internet traffic, we are
>>>>>>> optimizing specific flows with very tight delay requirements,
>>>>>>> which network operators have to take care of in a special way.
>>>>>>> www.huawei.com/ilink/en/download/HW_193034
>>>>>>>=20
>>>>>>> - *End to end* optimization: Nowadays, many appliances are used
>>>>>>> to connect remote offices of the same company (creating a VPN).
>>>>>>> So if a tunnel exists, why not optimizing this traffic when
>>>>>>> possible? We would save bandwidth in the access network, where =
it
>> can be scarce.
>>>>>>>=20
>>>>>>> - Wireless and satellite scenarios.
>>>>>>>=20
>>>>>>> "Cisco adds IP multiplexing to mobile satellite package", April
>>>>>>> 2012,
>>>>>>> http://www.networkworld.com/news/2012/040912-cisco-ip-
>>>> multiplexing-
>>>>>> 258082.html
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> Any other thoughts? Any other scenarios in mind? Potential
>>>>>>> beneficiaries?
>>>>>>>=20
>>>>>>> Some networks, today, use cRTP (RFC2508) on their access links.
>>>> This
>>>>>>> gives bandwidth savings on the access link, but consumes
>>>>>>> considerable CPU horsepower on the aggregation router (to =
perform
>>>> cRTP), but
>>>>>>> provides no bandwidth savings across the network core.   If,
>>>> instead,
>>>>>>> the bandwidth could be saved on the access link, across  the
>>>>>>> core, and on the far-end access link -- all without the CPU
>>>>>>> impact on the aggregation router -- it is a considerable win.
>>>>>>>=20
>>>>>>> -d
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> Jose
>>>>>>>=20
>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>>>> nombre
>>>>>>> de Jose Saldana Enviado el: lunes, 24 de junio de 2013 13:00
>>>>>>> Para: tcmtf@ietf.org
>>>>>>> Asunto: [tcmtf] Answers to possible questions in the BOF
>>>>>>>=20
>>>>>>> I would like to start a thread about possible questions people
>>>>>>> may ask in the BOF. Obviously, we also need answers, so we =
should
>>>> cooperate.
>>>>>>>=20
>>>>>>> This is different from the "questions to ask in the BOF". This
>>>>>>> will be discussed separately.
>>>>>>>=20
>>>>>>> Thanks!
>>>>>>>=20
>>>>>>> Jose
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> tcmtf mailing list
>>>>>>> tcmtf@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>> _______________________________________________
>>>>> tcmtf mailing list
>>>>> tcmtf@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>>=20
>>>>=20
>>>> --
>>>> "Esta vez no fallaremos, Doctor Infierno"
>>>>=20
>>>> Dr Diego R. Lopez
>>>> Telefonica I+D
>>>> http://people.tid.es/diego.lopez/
>>>>=20
>>>> e-mail: diego@tid.es
>>>> Tel:    +34 913 129 041
>>>> Mobile: +34 682 051 091
>>>> -----------------------------------------
>>>>=20
>>>>=20
>>>> ________________________________
>>>>=20
>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede
>>>> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico
>>>> en el enlace situado m=E1s abajo.
>>>> This message is intended exclusively for its addressee. We only =
send
>>>> and receive email on the basis of the terms set out at:
>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>>>> _______________________________________________
>>>> 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
>=20


From spencerdawkins.ietf@gmail.com  Fri Jul 12 08:53:23 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 EA32521F9E77 for <tcmtf@ietfa.amsl.com>; Fri, 12 Jul 2013 08:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.559
X-Spam-Level: 
X-Spam-Status: No, score=-2.559 tagged_above=-999 required=5 tests=[AWL=0.040,  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 aXFnr-rrXC+u for <tcmtf@ietfa.amsl.com>; Fri, 12 Jul 2013 08:53:22 -0700 (PDT)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 1213821F9EB8 for <tcmtf@ietf.org>; Fri, 12 Jul 2013 08:53:21 -0700 (PDT)
Received: by mail-ob0-f180.google.com with SMTP id eh20so11296098obb.39 for <tcmtf@ietf.org>; Fri, 12 Jul 2013 08:53:21 -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=15lopoJkgnUwzery2zH5qsn1BYV7OboUZB3xcTEX9eo=; b=UWNcMSfYfBMXMVypuj1HfKLTSlCqt7BOsiG1NGEDn3342XhgM/IAU7qMRfE8U9jldf AY9GFstT+dMQQP/XadkYsnJ8JIe9BJKsgOCuSoq/2m1fzzZzOSUw5ZBVtSUnECVzMF6b QuRDVATal3mPpY1DtMoD06dXEBY4WhBsjRl9/mLmqmznMwU5H/OsrFsubq4rw2jPI+OM apf/qApNKNmakS5PGt3fOVrzpuoz+XvIX1QRSUMznOxj9p5hDOIspMILJMIhUoYMAf0J OCNWeRMI6h9wYwYDgPI1eCDA5CTs5GEyp3TpFaKN2B89iELkENw4MwbG9orqmz/f/fgF 3/Iw==
X-Received: by 10.182.33.4 with SMTP id n4mr35669268obi.19.1373644401653; Fri, 12 Jul 2013 08:53:21 -0700 (PDT)
Received: from [192.168.1.77] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net. [99.108.174.213]) by mx.google.com with ESMTPSA id m11sm56294436oer.4.2013.07.12.08.53.19 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Jul 2013 08:53:20 -0700 (PDT)
Message-ID: <51E02655.3000800@gmail.com>
Date: Fri, 12 Jul 2013 10:52: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: Dan Wing <dwing@cisco.com>
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>	<009901ce725a$d1623360$74269a20$@unizar.es>	<2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>"	<20130628105725.lmag0xgqsgogggww@webmail.unizar.es>	<004601ce7bac$c8fc91b0$5af5b510$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CD0C7F1@EX10-MB2-MAD.hi.inet> <002301ce7beb$5c198370$144c8a50$@unizar.es> <341D9E54-28BF-4C85-A15C-EC06E203EE66@cisco.com>
In-Reply-To: <341D9E54-28BF-4C85-A15C-EC06E203EE66@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: tcmtf@ietf.org, "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>, "'Diego R. Lopez'" <diego@tid.es>, 'jsalazar' <jsalazar@unizar.es>, jsaldana@unizar.es
Subject: Re: [tcmtf] Answers to possible questions in 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: Fri, 12 Jul 2013 15:53:23 -0000

On 7/12/2013 10:42 AM, Dan Wing wrote:
> On Jul 8, 2013, at 7:56 AM, Jose Saldana <jsaldana@unizar.es> wrote:
>
>> So it seems that the possibility of a document about Security & TCM-TF might
>> be interesting. What about adding a sentence in the Charter (re-chartering
>> paragraph), talking about that possibility?
>>
>> ....
>> 9. If other interesting features are identified, the group would re-charter
>> and include them, e.g., a
>> mechanism for a multiplexer to discover a de-multiplexer, and vice versa; a
>> mechanism to select an
>> optimal multiplexer and a de-multiplexer when there are more than one
>> muxer/de-muxer for a flow;
>> dynamically applying TCMTF: a higher entity in charge of deciding when and
>> where, applying or not
>> TCMTF, and what kind of TCMTF, and what multiplexing period. Additional
>> methods for estimating delay
>> would also be required; *security issues related to TCM-TF, and methods for
>> securing TCM optimized flows.*
> This text detracts from the charter, because it lists only one reason we might re-charter to broaden the WG's scope.  There are lots of reasons we might re-charter to broaden the WG's scope, of course.  So I don't think this text is really saying anything that needs to be said.
>
> -d

Dan, I broadly agree that you don't want a list of reasons to re-charter 
before you can do work in the charter. I suggested shorter text to Jose 
privately, seconds ago :-)

Spencer

From jsaldana@unizar.es  Fri Jul 12 11:02:02 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 2B9B521F9CB9 for <tcmtf@ietfa.amsl.com>; Fri, 12 Jul 2013 11:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 PmEyc+THOyHe for <tcmtf@ietfa.amsl.com>; Fri, 12 Jul 2013 11:01:57 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id D74FE21F991E for <tcmtf@ietf.org>; Fri, 12 Jul 2013 11:01:56 -0700 (PDT)
Received: from jsaldanapc (41.Red-88-4-241.dynamicIP.rima-tde.net [88.4.241.41]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r6CI1jq1021378; Fri, 12 Jul 2013 20:01:46 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Fri, 12 Jul 2013 20:01:50 +0200
Message-ID: <000c01ce7f29$e2f9ee20$a8edca60$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01CE7F3A.A6850810"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5/Jx2Wu1M5wcMCQUCVjA377ZvkVQ==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: 'Gorry Fairhurst' <gorry@erg.abdn.ac.uk>, Janardhan Iyengar <janardhan.iyengar@fandm.edu>, 'Spencer Dawkins' <spencerdawkins.ietf@gmail.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [tcmtf] Improved version of the TCM-TF Charter draft (v7)
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, 12 Jul 2013 18:02:02 -0000

This is a multipart message in MIME format.

------=_NextPart_000_000D_01CE7F3A.A6850810
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

According to Spencer=92s advice, I have just re-built the charter draft.
This is the new proposal, in which number 9 and 10 have been improved,=20
with the aim of clearly stating the objectives.
=20
This is the charter that will be discussed in the BOF in IETF87, Berlin.
=20
A formatted version can also be found here:
 <http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf>
http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf
=20
=20
TCM-TF charter draft v7
=20
Description of Working Group
=20
1. In the last years we are witnessing the raise of new real-time =
services
that use the Internet for the delivery of interactive multimedia
applications: VoIP, videoconferencing, telemedicine, video vigilance, =
online
gaming, etc. Due to the need of interactivity, many of these services =
use
small packets (some tens of bytes), since they have to send frequent =
updates
between the extremes of the communication. In addition, some other =
services
also send small packets, but they are not delay-sensitive (e.g., instant
messaging, m2m packets sending collected data in sensor networks using
wireless or satellite scenarios). For both the delay-sensitive and
delay-insensitive applications, their small data payloads incur =
significant
overhead, and it becomes even higher when IPv6 is used, since the basic =
IPv6
header is twice the size of the IPv4 one.
=20
2. The efficiency cannot be increased by the inclusion of a higher =
number of
samples in a single packet, since this would harm the delay requirements =
of
the service. But there exist some scenarios in which a number of flows =
share
the same path. In this case, packets belonging to different flows can be
grouped together, adding a small multiplexing delay as a counterpart of
bandwidth saving. This delay will have to be maintained under some =
threshold
in order to grant the delay requirements. Some examples of the scenarios
where grouping packets is possible are:
=20
- aggregation networks of a network operator;
- an end-to-end tunnel between appliances located in two different =
offices
of the same company;
- the access connection of an Internet Caf=E9 including a high number of
VoIP/gaming flows;
- an agreement between two network operators could allow them to =
compress a
number of flows they are exchanging between a pair of Internet Routers;
- a satellite connection used for collecting the data of a high number =
of
sensors.
=20
3. VoIP using RTP is a clear example of a real-time service using small
packets with high overhead. In order to improve efficiency, RFC4170 =
(TCRTP)
defined a method for grouping packets when a number of flows share a =
path,
considering three different layers: header compression by means of =
ECRTP;
multiplexing by means of PPPMux; tunneling by means of L2TPv3.
=20
4. However, in the last years, emerging real-time services which do not =
use
UDP/RTP have become popular: some of them use UDP or even TCP. In =
addition,
new header compression methods have been defined (ROHC). So there is a =
need
of widening the scope of RFC4170 in order to consider not only UDP/RTP =
but
also other protocols. The same structure of three layers will be =
considered:
=20
- Header compression: Taking into account that real-time applications =
use
different headers (RTP/UDP, UDP or even TCP), different protocols can be
used: no compression, ECRTP, IPHC and ROHC.
- Multiplexing: If a number of flows share a path between an origin and =
a
destination, a multiplexer can build a bigger packet in which a number =
of
payloads share a common header. A demultiplexer is then necessary at the =
end
of the common path, so as to rebuild the packets as they were originally
sent. PPPMux will be the main option. Other ones are not discarded.
- Tunneling will be used to send the multiplexed packets end-to-end. The
options in this layer are L2TP, GRE and MPLS.
=20
5. So the first objective of this group is to specify the protocol stack =
for
tunneling, compressing and multiplexing traffic flows (TCM-TF). Since
standard protocols are being used at each layer, the signaling methods =
of
those protocols will be used. Interactions with the Working Groups and =
Areas
in which these protocols are developed can be expected. However, the
development of new compressing, multiplexing or tunneling protocols is =
not
an objective of this Working Group. In addition, since the current RFC =
4170
would be considered as one of the options, this RFC could be obsoleted.
=20
6. As a first objective, a document (TCM-TF - reference model) will =
define
the different options which can be used at each layer. Specific problems
caused by the interaction between layers will have to be issued, and
suitable extensions may have to be added to the involved protocols.
=20
7. If a pair multiplexer/de-multiplexer want to establish a TCM-TF =
session,
they have first to use a mechanism to negotiate which concrete option =
would
they use in each layer: header compression, multiplexing and tunneling. =
This
will depend on the protocols that each extreme implements at each level, =
and
in the scenario. So another document (TCM-TF - negotiation protocol) =
will
include:
=20
- a mechanism to setup/release a TCM-TF session between a multiplexer =
and a
de-multiplexer, also including:
- a negotiation mechanism to decide the options to use at each layer =
(header
compression, multiplexing and tunneling) between multiplexer and
de-multiplexer,=20
=20
8. As a counterpart of the bandwidth saving, TCM-TF may add some delay =
and
jitter. This is not a problem for the services which are not sensitive =
to
delay. However, regarding delay-sensitive services, the Working Group =
will
also develop a document (TCM-TF - recommendations) with useful
recommendations in order to decide which packet flows can or can not be
multiplexed and how. The document will present a list of available =
traffic
classification methods which can be used for identification of the =
service
or application to which a particular flow belongs, as well as
recommendations of the maximum delay and jitter to be added depending of =
the
identified service or application. The eventual impact of multiplexing =
on
protocol dynamics (e.g., when multiplexing TCP flows) will also have to =
be
addressed.
=20
9. The working group may identify additional deliverables that are=20
necessary/useful, e.g., a mechanism for a multiplexer to discover a=20
de-multiplexer, and vice versa. The working group would re-charter to =
add=20
them before working on them.
=20
10. In addition, specific uses of TCM-TF, such as in wireless and =
satellite=20
scenarios, could be considered, and it might be studied whether
modifications
or extensions are required on the protocol. The working group would=20
re-charter to work on those modifications/extensions.
=20
11. Interactions with other Working Groups can be expected, since TCM-TF
uses
already defined protocols for compression, multiplexing and tunneling =
(ROHC,
PPPMux, MPLS, GRE, L2TP).=20
=20
Goals and Milestones
=20
Specification of TCM-TF  reference model.
=20
Specification of TCM-TF negotiation protocol.
=20
Specification of TCM-TF recommendations of using existing traffic
classification methods, maximum delay and jitter to add, depending on =
the
service.
=20
=20
Current version of Document (TCM-TF - reference model):
 <https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/>
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
=20
Current version of Document (TCM-TF - recommendations):
 <http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/>
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
=20
=20
=20
Best regards,
=20
Jose

=20


------=_NextPart_000_000D_01CE7F3A.A6850810
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML con formato previo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLconformatoprevioCar
	{mso-style-name:"HTML con formato previo Car";
	mso-style-priority:99;
	mso-style-link:"HTML con formato previo";
	font-family:"Courier New";
	mso-fareast-language:ES;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><pre><span lang=3DEN-US =
style=3D'color:black'>According to Spencer&#8217;s advice, I have just =
re-built the charter draft.<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>This is the new proposal, in which =
number 9 and 10 have been improved, <o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>with the aim of clearly stating the =
objectives.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>This is the charter that will be =
discussed in the BOF in IETF87, =
Berlin.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>A formatted version can also be found =
here:<o:p></o:p></span></pre><pre><span style=3D'color:black'><a =
href=3D"http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft=
.pdf"><span =
lang=3DEN-US>http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_=
draft.pdf</span></a></span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>TCM-TF charter draft =
v7<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>Description of Working =
Group<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>1. In the last years we are =
witnessing the raise of new real-time =
services<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>that use the Internet for the delivery of =
interactive multimedia<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>applications: VoIP, videoconferencing, =
telemedicine, video vigilance, online<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>gaming, etc. Due to the need of =
interactivity, many of these services =
use<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>small packets (some tens of bytes), since they =
have to send frequent updates<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>between the extremes of the =
communication. In addition, some other =
services<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>also send small packets, but they are not =
delay-sensitive (e.g., instant<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>messaging, m2m packets sending =
collected data in sensor networks =
using<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>wireless or satellite scenarios). For both the =
delay-sensitive and<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>delay-insensitive applications, their small data =
payloads incur significant<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>overhead, and it becomes even higher =
when IPv6 is used, since the basic =
IPv6<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>header is twice the size of the IPv4 =
one.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>2. The efficiency cannot be increased =
by the inclusion of a higher number of<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>samples in a single packet, since =
this would harm the delay requirements =
of<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>the service. But there exist some scenarios in =
which a number of flows share<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>the same path. In this case, packets =
belonging to different flows can be<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>grouped together, adding a small =
multiplexing delay as a counterpart of<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>bandwidth saving. This delay will =
have to be maintained under some =
threshold<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>in order to grant the delay requirements. Some =
examples of the scenarios<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>where grouping packets is possible =
are:<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>- aggregation networks of a network =
operator;<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>- an end-to-end tunnel between appliances located =
in two different offices<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>of the same =
company;<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>- the access connection of an Internet Caf=E9 =
including a high number of<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>VoIP/gaming =
flows;<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>- an agreement between two network operators could =
allow them to compress a<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>number of flows they are exchanging between a pair =
of Internet Routers;<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>- a satellite connection used for collecting the =
data of a high number of<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>sensors.<o:p></o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>3. VoIP using RTP is a clear example =
of a real-time service using small<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>packets with high overhead. In order =
to improve efficiency, RFC4170 (TCRTP)<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>defined a method for grouping packets =
when a number of flows share a path,<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>considering three different layers: =
header compression by means of ECRTP;<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>multiplexing by means of PPPMux; =
tunneling by means of L2TPv3.<o:p></o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>4. However, in the last years, =
emerging real-time services which do not =
use<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>UDP/RTP have become popular: some of them use UDP =
or even TCP. In addition,<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>new header compression methods have been defined =
(ROHC). So there is a need<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>of widening the scope of RFC4170 in =
order to consider not only UDP/RTP but<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>also other protocols. The same =
structure of three layers will be =
considered:<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>- Header compression: Taking into =
account that real-time applications =
use<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>different headers (RTP/UDP, UDP or even TCP), =
different protocols can be<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>used: no compression, ECRTP, IPHC and =
ROHC.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>- Multiplexing: If a number of flows share a path =
between an origin and a<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>destination, a multiplexer can build a bigger =
packet in which a number of<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>payloads share a common header. A =
demultiplexer is then necessary at the =
end<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>of the common path, so as to rebuild the packets =
as they were originally<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>sent. PPPMux will be the main option. Other ones =
are not discarded.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>- Tunneling will be used to send the multiplexed =
packets end-to-end. The<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>options in this layer are L2TP, GRE and =
MPLS.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>5. So the first objective of this =
group is to specify the protocol stack =
for<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>tunneling, compressing and multiplexing traffic =
flows (TCM-TF). Since<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>standard protocols are being used at each layer, =
the signaling methods of<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>those protocols will be used. Interactions with =
the Working Groups and Areas<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>in which these protocols are =
developed can be expected. However, =
the<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>development of new compressing, multiplexing or =
tunneling protocols is not<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>an objective of this Working Group. =
In addition, since the current RFC =
4170<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>would be considered as one of the options, this =
RFC could be obsoleted.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>6. As a first objective, a document =
(TCM-TF - reference model) will define<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>the different options which can be =
used at each layer. Specific problems<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>caused by the interaction between =
layers will have to be issued, and<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>suitable extensions may have to be =
added to the involved protocols.<o:p></o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>7. If a pair =
multiplexer/de-multiplexer want to establish a TCM-TF =
session,<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>they have first to use a mechanism to negotiate =
which concrete option would<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>they use in each layer: header =
compression, multiplexing and tunneling. =
This<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>will depend on the protocols that each extreme =
implements at each level, and<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>in the scenario. So another document =
(TCM-TF - negotiation protocol) will<o:p></o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'>include:<o:p></o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>- a mechanism to setup/release a =
TCM-TF session between a multiplexer and =
a<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>de-multiplexer, also =
including:<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>- a negotiation mechanism to decide the options to =
use at each layer (header<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>compression, multiplexing and tunneling) between =
multiplexer and<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>de-multiplexer, <o:p></o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>8. As a counterpart of the bandwidth =
saving, TCM-TF may add some delay and<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>jitter. This is not a problem for the =
services which are not sensitive to<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>delay. However, regarding =
delay-sensitive services, the Working Group =
will<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>also develop a document (TCM-TF - recommendations) =
with useful<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>recommendations in order to decide which packet =
flows can or can not be<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>multiplexed and how. The document will present a =
list of available traffic<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>classification methods which can be used for =
identification of the service<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>or application to which a particular =
flow belongs, as well as<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>recommendations of the maximum delay and jitter to =
be added depending of the<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>identified service or application. The eventual =
impact of multiplexing on<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>protocol dynamics (e.g., when multiplexing TCP =
flows) will also have to be<o:p></o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'>addressed.<o:p></o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>9. The working group may identify =
additional deliverables that are <o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>necessary/useful, e.g., a mechanism =
for a multiplexer to discover a <o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>de-multiplexer, and vice versa. The =
working group would re-charter to add <o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>them before working on =
them.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>10. In addition, specific uses of =
TCM-TF, such as in wireless and satellite =
<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>scenarios, could be considered, and it might be =
studied whether modifications<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>or extensions are required on the =
protocol. The working group would <o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>re-charter to work on those =
modifications/extensions.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>11. Interactions with other Working =
Groups can be expected, since TCM-TF =
uses<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>already defined protocols for compression, =
multiplexing and tunneling (ROHC,<o:p></o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>PPPMux, MPLS, GRE, L2TP). =
<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>Goals and =
Milestones<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>Specification of TCM-TF=A0 reference =
model.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>Specification of TCM-TF negotiation =
protocol.<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>Specification of TCM-TF =
recommendations of using existing =
traffic<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>classification methods, maximum delay and jitter =
to add, depending on the<o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'>service.<o:p></o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>Current version of Document (TCM-TF - =
reference model):<o:p></o:p></span></pre><pre><span =
style=3D'color:black'><a =
href=3D"https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/"><spa=
n =
lang=3DEN-US>https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/<=
/span></a></span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US style=3D'color:black'>Current version of Document (TCM-TF - =
recommendations):<o:p></o:p></span></pre><pre><span =
style=3D'color:black'><a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
><span =
lang=3DEN-US>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tc=
mtf/</span></a></span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></pre><pre><span lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
lang=3DEN-US =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
style=3D'color:black'>Best regards,<o:p></o:p></span></pre><pre><span =
style=3D'color:black'><o:p>&nbsp;</o:p></span></pre><pre><span =
style=3D'color:black'>Jose<o:p></o:p></span></pre><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_000D_01CE7F3A.A6850810--


From jsaldana@unizar.es  Mon Jul 15 02:31:02 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 4841C21F9F97 for <tcmtf@ietfa.amsl.com>; Mon, 15 Jul 2013 02:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.337
X-Spam-Level: 
X-Spam-Status: No, score=-6.337 tagged_above=-999 required=5 tests=[AWL=0.262,  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 usu-k8vLYaq6 for <tcmtf@ietfa.amsl.com>; Mon, 15 Jul 2013 02:30:56 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id AC78A21F9F5E for <tcmtf@ietf.org>; Mon, 15 Jul 2013 02:30:51 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r6F9UVk4007376; Mon, 15 Jul 2013 11:30:37 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Dan Wing'" <dwing@cisco.com>
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>" <20130628105725.lmag0xgqsgogggww@webmail.unizar.es> <004601ce7bac$c8fc91b0$5af5b510$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CD0C7F1@EX10-MB2-MAD.hi.inet> <00b001ce7c91$1dcc6640$596532c0$@unizar.es> <408173bf1a2c57640e76ca5e8808a01b.squirrel@www.erg.abdn.ac.uk> <007a01ce7d42$3260a0b0$9721e210$@unizar.es> <961D17FB-C262-41A9-88C8-AF1B0CF32BD6@cisco.com>
In-Reply-To: <961D17FB-C262-41A9-88C8-AF1B0CF32BD6@cisco.com>
Date: Mon, 15 Jul 2013 11:30:37 +0200
Organization: Universidad de Zaragoza
Message-ID: <005501ce813d$fd245d10$f76d1730$@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: AQHxl5HfJe4XxEPJrqhURPk2/vEH5gJG8kQSAT8jBAUB238Z4AI2LB8yAU3srAwCFm+DUgLcQT0qAe+gMNUCTdFhtJiOnYnA
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: gorry@erg.abdn.ac.uk, tcmtf@ietf.org, "'Diego R. Lopez'" <diego@tid.es>, 'jsalazar' <jsalazar@unizar.es>, "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 15 Jul 2013 09:31:03 -0000

Ok, Dan. So the "Security considerations" would be:

    	The most straightforward option for securing a number of =
non-secured
flows sharing a path=20
    	is by the use of IPsec [IPsec] when TCM using an IP tunnel is
employed.=20
    	Instead of adding a security header to the packets of each native
flow, and then compressing=20
    	and multiplexing them, a single IPsec tunnel can be used in order =
to
secure all the flows together,=20
    	thus achieving a higher efficiency. This use of IPsec protects the
packets only within the=20
    	transport network between tunnel ingress and egress and therefore
does not provide end-to-end=20
    	authentication or encryption.
    =09
   	When a number of already secured flows including ESP [ESP] headers=20
    	are optimized by means of TCM, and the addition of further security
is not necessary,=20
    	their ESP/IP headers can still be compressed using suitable
algorithms [RFC5225],=20
    	in order to improve the efficiency. This header compression does =
not
change the end-to-end security model.

  	The resilience of TCM-TF to denial of service, and the use of TCM-TF
to deny service to other parts=20
	of the network infrastructure, is for future study.

Thanks,

Jose

> -----Mensaje original-----
> De: Dan Wing [mailto:dwing@cisco.com]
> Enviado el: viernes, 12 de julio de 2013 17:53
> Para: jsaldana@unizar.es
> CC: gorry@erg.abdn.ac.uk; 'Diego R. Lopez'; tcmtf@ietf.org; 'Muthu =
Arul
> Mozhi Perumal (mperumal)'; 'jsalazar'
> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>=20
>=20
> On Jul 10, 2013, at 12:50 AM, Jose Saldana <jsaldana@unizar.es> wrote:
>=20
> > What about these "security considerations"? (including Gorry's
> suggestions):
> >
> > ------
> > The most straightforward option for securing a number of non-secured
> > flows sharing a path is by the use of IPsec [IPsec], when TCM using =
an
> > IP tunnel is employed. Instead of adding a security header to the
> > packets of each native flow, and then compressing and multiplexing
> > them, a single IPsec tunnel can be used in order to secure all the
> > flows together, thus achieving a higher efficiency. This use of =
IPsec
> > protects the packets only within the transport network between =
tunnel
> > ingress and egress and therefore does not provide end-to-end
> > authentication or encryption. In some cases , e.g., where the end =
points
> are trusted, this model may be appropriate.
>=20
> I was agreeing with you until the example, which suggests endpoint =
trust
is
> somehow useful/important for using IPsec to protect traffic.  It is =
not
> relevant if the endpoints are trusted (botnet traffic is perfectly =
okay to
get
> put inside an IPsec tunnel); rather, it is relevant to use IPsec if =
the
IPsec-
> protected path is vulnerable to attack (passive attack [sniffing] or
active
> attack [injection]).
>=20
> I would just drop that last sentence (the sentence starting with "In =
some
> case, ...").
>=20
> > When a number of already secured flows including ESP [RFC4303] =
headers
> > are optimized by means of TCM, and the addition of further security =
is
> > not necessary, their ESP/IP headers can still be compressed using
> > suitable algorithms [RFC5225], in order to improve the efficiency.
> > This header compression does not change the end-to-end security =
model.
> >
> > Future versions of this document will consider whether some TCM-TF
> > mechanisms could be potentially exploited in order to deploy or
> > amplify DoS attacks against network infrastructure.
> > -----
>=20
> Gorry was worried about DoS of TCMTF itself, too.  So change last
paragraph
> to also say "will consider DoS vulnerability of TCM-TF itself" in =
addition
to
> what you already have about TCMTF being used to create a DoS attack
> against other stuff.  But, keeping it simpler, how about just saying:
"The
> resilience of TCM-TF to denial of service, and the use of TCM-TF to =
deny
> service to other parts of the network infrastructure, is for future
study."
>=20
> -d
>=20
>=20
> > Do you think the third paragraph should be included in this version?
> > Should we wait before talking about that?
> >
> > Thanks, Gorry,
> >
> > Jose
> >
> >> -----Mensaje original-----
> >> De: gorry@erg.abdn.ac.uk [mailto:gorry@erg.abdn.ac.uk] Enviado el:
> >> martes, 09 de julio de 2013 12:56
> >> Para: jsaldana@unizar.es
> >> CC: 'Diego R. Lopez'; tcmtf@ietf.org; 'Muthu Arul Mozhi Perumal
> >> (mperumal)'; 'jsalazar'; 'Dan Wing'
> >> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
> >>
> >> A few comments on the security considerations.
> >>
> >> Can you also please add the counter-argument to using IPsec?
> >>
> >> - This use of IPsec protects the packets only within the transport
> >> network between tunnel ingress and egress and therefore does not
> >> provide end-to- end authentication or encryption. In some cases ,
> >> e.g. where the end
> > points
> >> are trusted this model may be appropriate.
> >>
> >> - On the second point, please clarify:
> >> -- which headers are compressed?
> >> -- does this change the end-to-end security model (I think not).
> >>
> >> I suggest you quote RFCs for the security mechanisms that you =
discuss.
> >>
> >> Finally, you may like to consider DoS attacks against TCMTF.
> >> Transport
> > groups
> >> are usually required to consider whether the mechanisms can be
> >> exploited to generate traffic that does not respond to congestion
> >> control or can be used to amplify the attack on network
> >> infrastructure. If you can comment
> > on
> >> these that would seem good - I suggest you should note this as =
future
> >> work in later revisions of the draft.
> >>
> >> Gorry
> >>
> >>
> >>> Hi all,
> >>>
> >>> I am finishing the next version of the draft. In the "security
> >>> considerations" section in the end. The idea is talking about the
> >>> two options (as summarized by Diego):
> >>>
> >>> - Securing the application of TCMTF itself
> >>> - Applying TCMTF to enhance (or provide a better support to)
> >>> security network services, like IPsec or VPNs
> >>>
> >>> So I would include these two paragraphs, if you agree:
> >>>
> >>>
> >>> The most straightforward option for securing a number of =
non-secured
> >>> flows sharing a path is by the use of IPsec [IPsec], when TCM =
using
> >>> an IP tunnel is employed. Instead of adding a security header to =
the
> >>> packets of each native flow, and then compressing and =
multiplexing,
> >>> a single IPsec tunnel can be used in order to secure all the flows
> >>> together, thus achieving a better efficiency.
> >>>
> >>> When a number of already secured flows including ESP headers is
> >>> optimized by means of TCM, and the addition of further security is
> >>> not necessary, their ESP headers can still be compressed using
> >>> suitable algorithms, in order to improve the efficiency.
> >>>
> >>>
> >>> Any improvements? Any other ideas?
> >>>
> >>> Jose
> >>>
> >>>> -----Mensaje original-----
> >>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >>>> nombre de Diego R. Lopez Enviado el: lunes, 08 de julio de 2013
> >>>> 11:59
> >>>> Para: <jsaldana@unizar.es>
> >>>> CC: <tcmtf@ietf.org>; Muthu Arul Mozhi Perumal (mperumal);
> >>>> jsalazar; Dan Wing
> >>>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
> >>>>
> >>>> Hi,
> >>>>
> >>>> When talking about security, we should not forget two different
> > aspects:
> >>>>
> >>>> 1) Applying TCMTF to enhance (or provide a better support to)
> >>>> security network services, like IPsec or VPNs
> >>>>
> >>>> 2) Securing the application of TCMTF itself
> >>>>
> >>>> As far as I can tell, most of the discussion so far has been on =
the
> >>>> first
> >>> aspect.
> >>>> This could be outlined as an use case, and further discussed in a
> >>>> separate document if required, oriented towards "Applying TCMTF =
in
> >>>> secure environments" or the like
> >>>>
> >>>> Regarding the second issue, I tried to make a few points some =
time
> ago:
> >>>>
> >>>> 8<---
> >>>>
> >>>>> We can consider different security contexts for different =
tunnels,
> >>> according
> >>>> to some policy agreed by both end-points at a given tunnel. The
> >>>> security contexts would define encryption, authentication, or =
both.
> >>>> We'd have to go into more detail to evaluate potential savings, =
but
> >>>> I have the feeling
> >>> they
> >>>> could be worth considering.
> >>>>>
> >>>>> The point is that if we go for these different security =
contexts,
> >>>>> we
> >>> must
> >>>> consider how they can be established by mutual authentication of
> >>>> the
> >>> tunnel
> >>>> end-points, and this opens additional issues regarding
> >>>> configuration and crypto material exchange, as well as the
> >>>> possibility of user-initiated authentication by means of =
protocols
like
> OAuth.
> >>>>>
> >>>>> I'd keep this in the list of the "soon-to-open" issues, focusing
> >>>>> on
> >>>> the
> >>> three
> >>>> main docs we have been discussing so far.
> >>>>
> >>>> 8<---
> >>>>
> >>>> I had the intention to elaborate them a little more, but other
> >>>> matters
> >>> pre-
> >>>> empted this :-( My take is that some reflections on this should =
be
> >>> included in
> >>>> the "Security Considerations" section of the framework document,
> >>>> and a further document on this be considered in a further stage.
> >>>>
> >>>> Be goode,
> >>>>
> >>>> On 8 Jul 2013, at 09:28 , Jose Saldana wrote:
> >>>>
> >>>>> Hi, Muthu, Dan, Jose Luis.
> >>>>>
> >>>>> It seems that we have identified some cases in which different
> >>>> security
> >>>> options are possible. The question here is:
> >>>>>
> >>>>> Can this be issued in the TCMTF main draft (TCMTF Reference
> Model)?
> >>>>>
> >>>>> Or do you think a TCMTF-security document would be interesting?
> >>>>>
> >>>>> Jose
> >>>>>
> >>>>> -----Mensaje original-----
> >>>>> De: jsalazar [mailto:jsalazar@unizar.es] Enviado el: jueves, 04 =
de
> >>>>> julio de 2013 19:36
> >>>>> Para: jsaldana@unizar.es
> >>>>> Asunto: RE: [tcmtf] Answers to possible questions in the BOF
> >>>>>
> >>>>> Hi all.
> >>>>> With your last question, you have just hit the bullseye. I think
> >>>>> the
> >>>> classification is correct. Cases 1 and 2a are a good way to keep
> >>>> the compromise between security and efficency. However, case 2b
> >>>> gives a step beyond and the security is compromised in the =
interest
> >>>> of
> > efficiency.
> >>>>> In that case, users have to trust in tcmtf manager for managing
> >>>>> their privacy also. Then, we will leave the tipical Public Key
> >>>>> Infraestructure
> >>>>> (PKI) security architecture and use the Identity Based =
Encryption
> >>>> (IBE)
> >>> one
> >>>> (http://tools.ietf.org/html/rfc5408).
> >>>>> They are three different scenarios and all of them seem to be =
very
> >>>> interesting, but the last one a bit more.
> >>>>> Regards:
> >>>>>
> >>>>> JL
> >>>>>
> >>>>> "I see them falling out the skies like eagles All mirrored glass
> >>>>> and
> >>> shattered
> >>>> egos"
> >>>>>
> >>>>> Simple Minds.
> >>>>>
> >>>>> El 2013-07-03 17:58, Jose Saldana escribi=F3:
> >>>>>> Hi, Jose Luis. Good point.
> >>>>>>
> >>>>>> Regarding security, we could establish this classification:
> >>>>>>
> >>>>>> 1- Adding security to TCM: I have a number of non-secured flows
> >>>>>> traveling through a "dangerous" network segment (perhaps a =
tunnel
> >>>>>> between appliances connecting remote offices of a company), and =
I
> >>>>>> want not only traffic optimization but also security. In this
> >>>>>> case, I can simply use IPsec on the tunnel.
> >>>>>>
> >>>>>>
> >>>>>> 2- Using TCM for optimizing already secured communications: I
> >>>>>> have a bunch of already secured flows. Which is the best way =
for
> >>>>>> tunneling, compressing and multiplexing them?
> >>>>>>
> >>>>>> Two subcases:
> >>>>>>
> >>>>>> 2a- I can use TCM normally, but not only compress IP, TCP or =
UDP
> >>>>>> headers, but also security headers using a header compression
> >> method.
> >>>>>> Some possibilities for compressing security headers:
> >>>>>>
> >>>>>> - ROHCoIPsec, RFC5856 (http://tools.ietf.org/html/rfc5856)
> >>>>>> - RFC5225 http://tools.ietf.org/html/rfc5225
> >>>>>>
> >>>>>>
> >>>>>> 2b- But I can save more bandwidth if the TCM-ingress optimizer
> >>>>>> (TCM-IO) is able to:
> >>>>>> - rebuild the packets to their native form
> >>>>>> - TCM-optimize them
> >>>>>> - put them into a single security tunnel
> >>>>>>
> >>>>>> I have three phases (let's suppose I have 20 communications):
> >>>>>>
> >>>>>> Origin 1
> >>>>>> Origin 2     <----20 secured flows --------> TCM-IO <------1
> >>>>>> tunnel------> TCM-EO <-------- 20 secured flows----> =
destination
> >>>>>> tunnel------> 1, 2,
> >>>>>> 20
> >>>>>> ...
> >>>>>> Origin 20
> >>>>>>
> >>>>>> I have an advantage: In the shared network path, I use a single
> >>>>>> tunnel instead of 20 different tunnels.
> >>>>>>
> >>>>>> But I have some additional requirements: I need processing
> >>>>>> capacity in the TCM optimizers, and the endpoints should trust
> them.
> >>>>>>
> >>>>>>
> >>>>>> Is this classification correct? Any other options? Any other
> >>>>>> requirements? It is time for "security experts".
> >>>>>>
> >>>>>> Jose
> >>>>>>
> >>>>>> -----Mensaje original-----
> >>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >>>>>> nombre de jsalazar Enviado el: lunes, 01 de julio de 2013 20:50
> >>>>>> Para: tcmtf@ietf.org
> >>>>>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
> >>>>>>
> >>>>>> Hi all:
> >>>>>> Mmmmmmm. Since I see tcm-tf as a service, I can design the
> >>>>>> service with added security features that the type of
> >>>>>> communication is requiring. I think we have to be clear what we
> >>>>>> are expressing when we are talking about secure tcm-tf: =
Ensuring
> >>>>>> the service tcm-tf or applying the tcm-tf service for secure
> communications.
> >>>>>> The first possibility is not a great technological =
sophistication
> >>>>>> and the second one might consider the first one as a possible
> >>>>>> additional service.
> >>>>>> Therefore,
> >>>>>> every time we use the term "secure tcm-tf" should think the
> >>>>>> second option, for generality.
> >>>>>> On the other hand, we must also keep in mind that whenever =
users
> >>>>>> employ secure tcm-tf, they must trust the service fully and
> >>>>>> consider delegating the use of their keys (including private
> >>>>>> ones)
> > to
> >> tcm-tf.
> >>>>>>
> >>>>>> Regards.
> >>>>>>
> >>>>>> JL
> >>>>>>
> >>>>>> "I see them falling out the skies like eagles All mirrored =
glass
> >>>>>> and shattered egos"
> >>>>>>
> >>>>>> Simple Minds.
> >>>>>>
> >>>>>> El 2013-07-01 18:55, Dan Wing escribi=F3:
> >>>>>>> On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
> >>>>>>>
> >>>>>>> Hi all,
> >>>>>>>
> >>>>>>> Few days ago Julian talked about TCM-TF's security and now =
I've
> >>>>>>> read in the link included by Dan, saying that the gain =
obtained
> >>>>>>> when multiplexing Ipsec-encrypted packets is 20-to-1. We have
> >>>>>>> been looking for more information about this issue and =
thinking
> >>>>>>> about a way to reduce the needed  bandwidth in IPsec flows.
> >>>>>>>
> >>>>>>> The main idea is to find a way to change the authentication of
> >>>>>>> the individual packets and merge all of them in a unique
> >> authentication.
> >>>>>>> Thus, instead of using 20 IPsec tunnels, we would have a =
single
> >>>>>>> tunnel including 20 flows. Is this something similar than how
> >>>>>>> Cisco gets the improvement?
> >>>>>>>
> >>>>>>> We would not be able to change IPsec any more than we could
> >>>>>>> change TCP, so I would not look at how to change IPsec
> >> authentication.
> >>>>>>>
> >>>>>>> However, if there are a bunch of IPsec packets sharing a =
common
> >>>>>>> path, I could see them being successfully multiplexed into one
> >>>>>>> larger packet at one tunnel endpoint and then de-multiplexed =
at
> >>>>>>> the other tunnel endpoint.  This can provide a packet per =
second
> >>>>>>> reduction.  I don't think there are enough bytes in an IPsec
> >>>>>>> header to bother trying to do IPsec header compression (SPI =
and
> >>>>>>> sequence
> >>>> number are only 64 bits).
> >>>>>>>
> >>>>>>> -d
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Jos=E9 Luis
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Dan Wing <dwing@cisco.com> ha escrito:
> >>>>>>>
> >>>>>>>
> >>>>>>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es>
> >>>> wrote:
> >>>>>>>
> >>>>>>> Question 4: Is TCM-TF interesting for the Industry? Should the
> >>>>>>> IETF standardize this?
> >>>>>>>
> >>>>>>> Answer:
> >>>>>>>
> >>>>>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP
> >>> traffic.
> >>>>>>> So if RFC4170 was interesting, why not updating it?
> >>>>>>>
> >>>>>>> 2) TCM-TF can be useful in order to save bandwidth in many =
cases:
> >>>>>>>
> >>>>>>> - Aggregation network of *network operators*: We are saving
> >>>>>>> bandwidth by optimizing and putting together traffic flows. Is
> >>>>>>> this interesting for a network operator? What about
> >> overprovisioning?
> >>>>>>> The idea is that there are places and moments in which a =
number
> >>>>>>> of flows based on small packets are in the same place and at =
the
> >>>>>>> same moment. Then, TCM-TF can be applied in order to provide
> >> flexibility.
> >>>>>>> We are not optimizing the overall Internet traffic, we are
> >>>>>>> optimizing specific flows with very tight delay requirements,
> >>>>>>> which network operators have to take care of in a special way.
> >>>>>>> www.huawei.com/ilink/en/download/HW_193034
> >>>>>>>
> >>>>>>> - *End to end* optimization: Nowadays, many appliances are =
used
> >>>>>>> to connect remote offices of the same company (creating a =
VPN).
> >>>>>>> So if a tunnel exists, why not optimizing this traffic when
> >>>>>>> possible? We would save bandwidth in the access network, where
> >>>>>>> it
> >> can be scarce.
> >>>>>>>
> >>>>>>> - Wireless and satellite scenarios.
> >>>>>>>
> >>>>>>> "Cisco adds IP multiplexing to mobile satellite package", =
April
> >>>>>>> 2012,
> >>>>>>> http://www.networkworld.com/news/2012/040912-cisco-ip-
> >>>> multiplexing-
> >>>>>> 258082.html
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Any other thoughts? Any other scenarios in mind? Potential
> >>>>>>> beneficiaries?
> >>>>>>>
> >>>>>>> Some networks, today, use cRTP (RFC2508) on their access =
links.
> >>>> This
> >>>>>>> gives bandwidth savings on the access link, but consumes
> >>>>>>> considerable CPU horsepower on the aggregation router (to
> >>>>>>> perform
> >>>> cRTP), but
> >>>>>>> provides no bandwidth savings across the network core.   If,
> >>>> instead,
> >>>>>>> the bandwidth could be saved on the access link, across  the
> >>>>>>> core, and on the far-end access link -- all without the CPU
> >>>>>>> impact on the aggregation router -- it is a considerable win.
> >>>>>>>
> >>>>>>> -d
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Jose
> >>>>>>>
> >>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >>>> nombre
> >>>>>>> de Jose Saldana Enviado el: lunes, 24 de junio de 2013 13:00
> >>>>>>> Para: tcmtf@ietf.org
> >>>>>>> Asunto: [tcmtf] Answers to possible questions in the BOF
> >>>>>>>
> >>>>>>> I would like to start a thread about possible questions people
> >>>>>>> may ask in the BOF. Obviously, we also need answers, so we
> >>>>>>> should
> >>>> cooperate.
> >>>>>>>
> >>>>>>> This is different from the "questions to ask in the BOF". This
> >>>>>>> will be discussed separately.
> >>>>>>>
> >>>>>>> Thanks!
> >>>>>>>
> >>>>>>> Jose
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> 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
> >>>>>
> >>>>> _______________________________________________
> >>>>> tcmtf mailing list
> >>>>> tcmtf@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>>>
> >>>>
> >>>> --
> >>>> "Esta vez no fallaremos, Doctor Infierno"
> >>>>
> >>>> Dr Diego R. Lopez
> >>>> Telefonica I+D
> >>>> http://people.tid.es/diego.lopez/
> >>>>
> >>>> e-mail: diego@tid.es
> >>>> Tel:    +34 913 129 041
> >>>> Mobile: +34 682 051 091
> >>>> -----------------------------------------
> >>>>
> >>>>
> >>>> ________________________________
> >>>>
> >>>> Este mensaje se dirige exclusivamente a su destinatario. Puede
> >>>> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo
> >>>> electr=F3nico en el enlace situado m=E1s abajo.
> >>>> This message is intended exclusively for its addressee. We only
> >>>> send and receive email on the basis of the terms set out at:
> >>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >>>> _______________________________________________
> >>>> 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 dwing@cisco.com  Mon Jul 15 09:30:44 2013
Return-Path: <dwing@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 DF05A11E8105 for <tcmtf@ietfa.amsl.com>; Mon, 15 Jul 2013 09:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.492
X-Spam-Level: 
X-Spam-Status: No, score=-110.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 qhjTUx+Q4yh8 for <tcmtf@ietfa.amsl.com>; Mon, 15 Jul 2013 09:30:40 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id D8CE621E80C1 for <tcmtf@ietf.org>; Mon, 15 Jul 2013 09:30:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23242; q=dns/txt; s=iport; t=1373905840; x=1375115440; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=CndqkObaqVnTinwbnNPdWpTf9Fzt1AznOY4T+gzEuZ0=; b=cY0hJizLT/528XILWMPJptixKb/XVF0aHOOWXolEVx9XT5rqX1lGP4TN e76qQfWXrBahqI8RsEJVVVhKDo0v2B2UlN4CRbhKadefC93gWUnmzRo90 355iLubtfZ3Rlaj3hY5mFjRYC8T7+haxRlUg1BEd5XPC2CMk8h3fpX7P+ Q=;
X-IronPort-AV: E=Sophos;i="4.89,670,1367971200"; d="scan'208";a="83049271"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 15 Jul 2013 16:30:40 +0000
Received: from sjc-vpn3-945.cisco.com (sjc-vpn3-945.cisco.com [10.21.67.177]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6FGUaFU017192; Mon, 15 Jul 2013 16:30:37 GMT
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <005501ce813d$fd245d10$f76d1730$@unizar.es>
Date: Mon, 15 Jul 2013 09:30:36 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <20FA538D-946A-4A81-B341-FC4A8133529E@cisco.com>
References: "\"<007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>" <20130628105725.lmag0xgqsgogggww@webmail.unizar.es> <004601ce7bac$c8fc91b0$5af5b510$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CD0C7F1@EX10-MB2-MAD.hi.inet> <00b001ce7c91$1dcc6640$596532c0$@unizar.es> <408173bf1a2c57640e76ca5e8808a01b.squirrel@www.erg.abdn.ac.uk> <007a01ce7d42$3260a0b0$9721e210$@unizar.es> <961D17FB-C262-41A9-88C8-AF1B0CF32BD6@cisco.com> <005501ce813d$fd245d10$f76d1730$@unizar.es>
To: <jsaldana@unizar.es>
X-Mailer: Apple Mail (2.1508)
Cc: gorry@erg.abdn.ac.uk, tcmtf@ietf.org, "'Diego R. Lopez'" <diego@tid.es>, 'jsalazar' <jsalazar@unizar.es>, "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>
Subject: Re: [tcmtf] Answers to possible questions in 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: Mon, 15 Jul 2013 16:30:45 -0000

On Jul 15, 2013, at 2:30 AM, Jose Saldana <jsaldana@unizar.es> wrote:

> Ok, Dan. So the "Security considerations" would be:
>=20
>    	The most straightforward option for securing a number of =
non-secured
> flows sharing a path=20
>    	is by the use of IPsec [IPsec] when TCM using an IP tunnel is
> employed.=20
>    	Instead of adding a security header to the packets of each =
native
> flow, and then compressing=20
>    	and multiplexing them, a single IPsec tunnel can be used in =
order to
> secure all the flows together,=20
>    	thus achieving a higher efficiency. This use of IPsec protects =
the
> packets only within the=20
>    	transport network between tunnel ingress and egress and =
therefore
> does not provide end-to-end=20
>    	authentication or encryption.

Splendid.

>   	When a number of already secured flows including ESP [ESP] =
headers=20
>    	are optimized by means of TCM, and the addition of further =
security
> is not necessary,=20

I would remove "and the addition of further security is not necessary" =
phrase, because that phrase implies we are going to detect IPsec ESP =
packets and then not put them into an IPsec-protected tunnel.  Said =
another way, the phrase implies the already-encrypted packets are =
"routed around" (outside) of the IPsec tunnel.  This is risky, and =
deserves its own security analysis and discussion; let's not go there.


>    	their ESP/IP headers can still be compressed using suitable
> algorithms [RFC5225],=20
>    	in order to improve the efficiency. This header compression does =
not
> change the end-to-end security model.
>=20
>  	The resilience of TCM-TF to denial of service, and the use of =
TCM-TF
> to deny service to other parts=20
> 	of the network infrastructure, is for future study.

That text reads nicely.

-d


> Thanks,
>=20
> Jose
>=20
>> -----Mensaje original-----
>> De: Dan Wing [mailto:dwing@cisco.com]
>> Enviado el: viernes, 12 de julio de 2013 17:53
>> Para: jsaldana@unizar.es
>> CC: gorry@erg.abdn.ac.uk; 'Diego R. Lopez'; tcmtf@ietf.org; 'Muthu =
Arul
>> Mozhi Perumal (mperumal)'; 'jsalazar'
>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>>=20
>>=20
>> On Jul 10, 2013, at 12:50 AM, Jose Saldana <jsaldana@unizar.es> =
wrote:
>>=20
>>> What about these "security considerations"? (including Gorry's
>> suggestions):
>>>=20
>>> ------
>>> The most straightforward option for securing a number of non-secured
>>> flows sharing a path is by the use of IPsec [IPsec], when TCM using =
an
>>> IP tunnel is employed. Instead of adding a security header to the
>>> packets of each native flow, and then compressing and multiplexing
>>> them, a single IPsec tunnel can be used in order to secure all the
>>> flows together, thus achieving a higher efficiency. This use of =
IPsec
>>> protects the packets only within the transport network between =
tunnel
>>> ingress and egress and therefore does not provide end-to-end
>>> authentication or encryption. In some cases , e.g., where the end =
points
>> are trusted, this model may be appropriate.
>>=20
>> I was agreeing with you until the example, which suggests endpoint =
trust
> is
>> somehow useful/important for using IPsec to protect traffic.  It is =
not
>> relevant if the endpoints are trusted (botnet traffic is perfectly =
okay to
> get
>> put inside an IPsec tunnel); rather, it is relevant to use IPsec if =
the
> IPsec-
>> protected path is vulnerable to attack (passive attack [sniffing] or
> active
>> attack [injection]).
>>=20
>> I would just drop that last sentence (the sentence starting with "In =
some
>> case, ...").
>>=20
>>> When a number of already secured flows including ESP [RFC4303] =
headers
>>> are optimized by means of TCM, and the addition of further security =
is
>>> not necessary, their ESP/IP headers can still be compressed using
>>> suitable algorithms [RFC5225], in order to improve the efficiency.
>>> This header compression does not change the end-to-end security =
model.
>>>=20
>>> Future versions of this document will consider whether some TCM-TF
>>> mechanisms could be potentially exploited in order to deploy or
>>> amplify DoS attacks against network infrastructure.
>>> -----
>>=20
>> Gorry was worried about DoS of TCMTF itself, too.  So change last
> paragraph
>> to also say "will consider DoS vulnerability of TCM-TF itself" in =
addition
> to
>> what you already have about TCMTF being used to create a DoS attack
>> against other stuff.  But, keeping it simpler, how about just saying:
> "The
>> resilience of TCM-TF to denial of service, and the use of TCM-TF to =
deny
>> service to other parts of the network infrastructure, is for future
> study."
>>=20
>> -d
>>=20
>>=20
>>> Do you think the third paragraph should be included in this version?
>>> Should we wait before talking about that?
>>>=20
>>> Thanks, Gorry,
>>>=20
>>> Jose
>>>=20
>>>> -----Mensaje original-----
>>>> De: gorry@erg.abdn.ac.uk [mailto:gorry@erg.abdn.ac.uk] Enviado el:
>>>> martes, 09 de julio de 2013 12:56
>>>> Para: jsaldana@unizar.es
>>>> CC: 'Diego R. Lopez'; tcmtf@ietf.org; 'Muthu Arul Mozhi Perumal
>>>> (mperumal)'; 'jsalazar'; 'Dan Wing'
>>>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>>>>=20
>>>> A few comments on the security considerations.
>>>>=20
>>>> Can you also please add the counter-argument to using IPsec?
>>>>=20
>>>> - This use of IPsec protects the packets only within the transport
>>>> network between tunnel ingress and egress and therefore does not
>>>> provide end-to- end authentication or encryption. In some cases ,
>>>> e.g. where the end
>>> points
>>>> are trusted this model may be appropriate.
>>>>=20
>>>> - On the second point, please clarify:
>>>> -- which headers are compressed?
>>>> -- does this change the end-to-end security model (I think not).
>>>>=20
>>>> I suggest you quote RFCs for the security mechanisms that you =
discuss.
>>>>=20
>>>> Finally, you may like to consider DoS attacks against TCMTF.
>>>> Transport
>>> groups
>>>> are usually required to consider whether the mechanisms can be
>>>> exploited to generate traffic that does not respond to congestion
>>>> control or can be used to amplify the attack on network
>>>> infrastructure. If you can comment
>>> on
>>>> these that would seem good - I suggest you should note this as =
future
>>>> work in later revisions of the draft.
>>>>=20
>>>> Gorry
>>>>=20
>>>>=20
>>>>> Hi all,
>>>>>=20
>>>>> I am finishing the next version of the draft. In the "security
>>>>> considerations" section in the end. The idea is talking about the
>>>>> two options (as summarized by Diego):
>>>>>=20
>>>>> - Securing the application of TCMTF itself
>>>>> - Applying TCMTF to enhance (or provide a better support to)
>>>>> security network services, like IPsec or VPNs
>>>>>=20
>>>>> So I would include these two paragraphs, if you agree:
>>>>>=20
>>>>>=20
>>>>> The most straightforward option for securing a number of =
non-secured
>>>>> flows sharing a path is by the use of IPsec [IPsec], when TCM =
using
>>>>> an IP tunnel is employed. Instead of adding a security header to =
the
>>>>> packets of each native flow, and then compressing and =
multiplexing,
>>>>> a single IPsec tunnel can be used in order to secure all the flows
>>>>> together, thus achieving a better efficiency.
>>>>>=20
>>>>> When a number of already secured flows including ESP headers is
>>>>> optimized by means of TCM, and the addition of further security is
>>>>> not necessary, their ESP headers can still be compressed using
>>>>> suitable algorithms, in order to improve the efficiency.
>>>>>=20
>>>>>=20
>>>>> Any improvements? Any other ideas?
>>>>>=20
>>>>> Jose
>>>>>=20
>>>>>> -----Mensaje original-----
>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>>>>>> nombre de Diego R. Lopez Enviado el: lunes, 08 de julio de 2013
>>>>>> 11:59
>>>>>> Para: <jsaldana@unizar.es>
>>>>>> CC: <tcmtf@ietf.org>; Muthu Arul Mozhi Perumal (mperumal);
>>>>>> jsalazar; Dan Wing
>>>>>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>>>>>>=20
>>>>>> Hi,
>>>>>>=20
>>>>>> When talking about security, we should not forget two different
>>> aspects:
>>>>>>=20
>>>>>> 1) Applying TCMTF to enhance (or provide a better support to)
>>>>>> security network services, like IPsec or VPNs
>>>>>>=20
>>>>>> 2) Securing the application of TCMTF itself
>>>>>>=20
>>>>>> As far as I can tell, most of the discussion so far has been on =
the
>>>>>> first
>>>>> aspect.
>>>>>> This could be outlined as an use case, and further discussed in a
>>>>>> separate document if required, oriented towards "Applying TCMTF =
in
>>>>>> secure environments" or the like
>>>>>>=20
>>>>>> Regarding the second issue, I tried to make a few points some =
time
>> ago:
>>>>>>=20
>>>>>> 8<---
>>>>>>=20
>>>>>>> We can consider different security contexts for different =
tunnels,
>>>>> according
>>>>>> to some policy agreed by both end-points at a given tunnel. The
>>>>>> security contexts would define encryption, authentication, or =
both.
>>>>>> We'd have to go into more detail to evaluate potential savings, =
but
>>>>>> I have the feeling
>>>>> they
>>>>>> could be worth considering.
>>>>>>>=20
>>>>>>> The point is that if we go for these different security =
contexts,
>>>>>>> we
>>>>> must
>>>>>> consider how they can be established by mutual authentication of
>>>>>> the
>>>>> tunnel
>>>>>> end-points, and this opens additional issues regarding
>>>>>> configuration and crypto material exchange, as well as the
>>>>>> possibility of user-initiated authentication by means of =
protocols
> like
>> OAuth.
>>>>>>>=20
>>>>>>> I'd keep this in the list of the "soon-to-open" issues, focusing
>>>>>>> on
>>>>>> the
>>>>> three
>>>>>> main docs we have been discussing so far.
>>>>>>=20
>>>>>> 8<---
>>>>>>=20
>>>>>> I had the intention to elaborate them a little more, but other
>>>>>> matters
>>>>> pre-
>>>>>> empted this :-( My take is that some reflections on this should =
be
>>>>> included in
>>>>>> the "Security Considerations" section of the framework document,
>>>>>> and a further document on this be considered in a further stage.
>>>>>>=20
>>>>>> Be goode,
>>>>>>=20
>>>>>> On 8 Jul 2013, at 09:28 , Jose Saldana wrote:
>>>>>>=20
>>>>>>> Hi, Muthu, Dan, Jose Luis.
>>>>>>>=20
>>>>>>> It seems that we have identified some cases in which different
>>>>>> security
>>>>>> options are possible. The question here is:
>>>>>>>=20
>>>>>>> Can this be issued in the TCMTF main draft (TCMTF Reference
>> Model)?
>>>>>>>=20
>>>>>>> Or do you think a TCMTF-security document would be interesting?
>>>>>>>=20
>>>>>>> Jose
>>>>>>>=20
>>>>>>> -----Mensaje original-----
>>>>>>> De: jsalazar [mailto:jsalazar@unizar.es] Enviado el: jueves, 04 =
de
>>>>>>> julio de 2013 19:36
>>>>>>> Para: jsaldana@unizar.es
>>>>>>> Asunto: RE: [tcmtf] Answers to possible questions in the BOF
>>>>>>>=20
>>>>>>> Hi all.
>>>>>>> With your last question, you have just hit the bullseye. I think
>>>>>>> the
>>>>>> classification is correct. Cases 1 and 2a are a good way to keep
>>>>>> the compromise between security and efficency. However, case 2b
>>>>>> gives a step beyond and the security is compromised in the =
interest
>>>>>> of
>>> efficiency.
>>>>>>> In that case, users have to trust in tcmtf manager for managing
>>>>>>> their privacy also. Then, we will leave the tipical Public Key
>>>>>>> Infraestructure
>>>>>>> (PKI) security architecture and use the Identity Based =
Encryption
>>>>>> (IBE)
>>>>> one
>>>>>> (http://tools.ietf.org/html/rfc5408).
>>>>>>> They are three different scenarios and all of them seem to be =
very
>>>>>> interesting, but the last one a bit more.
>>>>>>> Regards:
>>>>>>>=20
>>>>>>> JL
>>>>>>>=20
>>>>>>> "I see them falling out the skies like eagles All mirrored glass
>>>>>>> and
>>>>> shattered
>>>>>> egos"
>>>>>>>=20
>>>>>>> Simple Minds.
>>>>>>>=20
>>>>>>> El 2013-07-03 17:58, Jose Saldana escribi=F3:
>>>>>>>> Hi, Jose Luis. Good point.
>>>>>>>>=20
>>>>>>>> Regarding security, we could establish this classification:
>>>>>>>>=20
>>>>>>>> 1- Adding security to TCM: I have a number of non-secured flows
>>>>>>>> traveling through a "dangerous" network segment (perhaps a =
tunnel
>>>>>>>> between appliances connecting remote offices of a company), and =
I
>>>>>>>> want not only traffic optimization but also security. In this
>>>>>>>> case, I can simply use IPsec on the tunnel.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> 2- Using TCM for optimizing already secured communications: I
>>>>>>>> have a bunch of already secured flows. Which is the best way =
for
>>>>>>>> tunneling, compressing and multiplexing them?
>>>>>>>>=20
>>>>>>>> Two subcases:
>>>>>>>>=20
>>>>>>>> 2a- I can use TCM normally, but not only compress IP, TCP or =
UDP
>>>>>>>> headers, but also security headers using a header compression
>>>> method.
>>>>>>>> Some possibilities for compressing security headers:
>>>>>>>>=20
>>>>>>>> - ROHCoIPsec, RFC5856 (http://tools.ietf.org/html/rfc5856)
>>>>>>>> - RFC5225 http://tools.ietf.org/html/rfc5225
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> 2b- But I can save more bandwidth if the TCM-ingress optimizer
>>>>>>>> (TCM-IO) is able to:
>>>>>>>> - rebuild the packets to their native form
>>>>>>>> - TCM-optimize them
>>>>>>>> - put them into a single security tunnel
>>>>>>>>=20
>>>>>>>> I have three phases (let's suppose I have 20 communications):
>>>>>>>>=20
>>>>>>>> Origin 1
>>>>>>>> Origin 2     <----20 secured flows --------> TCM-IO <------1
>>>>>>>> tunnel------> TCM-EO <-------- 20 secured flows----> =
destination
>>>>>>>> tunnel------> 1, 2,
>>>>>>>> 20
>>>>>>>> ...
>>>>>>>> Origin 20
>>>>>>>>=20
>>>>>>>> I have an advantage: In the shared network path, I use a single
>>>>>>>> tunnel instead of 20 different tunnels.
>>>>>>>>=20
>>>>>>>> But I have some additional requirements: I need processing
>>>>>>>> capacity in the TCM optimizers, and the endpoints should trust
>> them.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Is this classification correct? Any other options? Any other
>>>>>>>> requirements? It is time for "security experts".
>>>>>>>>=20
>>>>>>>> Jose
>>>>>>>>=20
>>>>>>>> -----Mensaje original-----
>>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>>>>>>>> nombre de jsalazar Enviado el: lunes, 01 de julio de 2013 20:50
>>>>>>>> Para: tcmtf@ietf.org
>>>>>>>> Asunto: Re: [tcmtf] Answers to possible questions in the BOF
>>>>>>>>=20
>>>>>>>> Hi all:
>>>>>>>> Mmmmmmm. Since I see tcm-tf as a service, I can design the
>>>>>>>> service with added security features that the type of
>>>>>>>> communication is requiring. I think we have to be clear what we
>>>>>>>> are expressing when we are talking about secure tcm-tf: =
Ensuring
>>>>>>>> the service tcm-tf or applying the tcm-tf service for secure
>> communications.
>>>>>>>> The first possibility is not a great technological =
sophistication
>>>>>>>> and the second one might consider the first one as a possible
>>>>>>>> additional service.
>>>>>>>> Therefore,
>>>>>>>> every time we use the term "secure tcm-tf" should think the
>>>>>>>> second option, for generality.
>>>>>>>> On the other hand, we must also keep in mind that whenever =
users
>>>>>>>> employ secure tcm-tf, they must trust the service fully and
>>>>>>>> consider delegating the use of their keys (including private
>>>>>>>> ones)
>>> to
>>>> tcm-tf.
>>>>>>>>=20
>>>>>>>> Regards.
>>>>>>>>=20
>>>>>>>> JL
>>>>>>>>=20
>>>>>>>> "I see them falling out the skies like eagles All mirrored =
glass
>>>>>>>> and shattered egos"
>>>>>>>>=20
>>>>>>>> Simple Minds.
>>>>>>>>=20
>>>>>>>> El 2013-07-01 18:55, Dan Wing escribi=F3:
>>>>>>>>> On Jun 28, 2013, at 1:57 AM, jltornos@unizar.es wrote:
>>>>>>>>>=20
>>>>>>>>> Hi all,
>>>>>>>>>=20
>>>>>>>>> Few days ago Julian talked about TCM-TF's security and now =
I've
>>>>>>>>> read in the link included by Dan, saying that the gain =
obtained
>>>>>>>>> when multiplexing Ipsec-encrypted packets is 20-to-1. We have
>>>>>>>>> been looking for more information about this issue and =
thinking
>>>>>>>>> about a way to reduce the needed  bandwidth in IPsec flows.
>>>>>>>>>=20
>>>>>>>>> The main idea is to find a way to change the authentication of
>>>>>>>>> the individual packets and merge all of them in a unique
>>>> authentication.
>>>>>>>>> Thus, instead of using 20 IPsec tunnels, we would have a =
single
>>>>>>>>> tunnel including 20 flows. Is this something similar than how
>>>>>>>>> Cisco gets the improvement?
>>>>>>>>>=20
>>>>>>>>> We would not be able to change IPsec any more than we could
>>>>>>>>> change TCP, so I would not look at how to change IPsec
>>>> authentication.
>>>>>>>>>=20
>>>>>>>>> However, if there are a bunch of IPsec packets sharing a =
common
>>>>>>>>> path, I could see them being successfully multiplexed into one
>>>>>>>>> larger packet at one tunnel endpoint and then de-multiplexed =
at
>>>>>>>>> the other tunnel endpoint.  This can provide a packet per =
second
>>>>>>>>> reduction.  I don't think there are enough bytes in an IPsec
>>>>>>>>> header to bother trying to do IPsec header compression (SPI =
and
>>>>>>>>> sequence
>>>>>> number are only 64 bits).
>>>>>>>>>=20
>>>>>>>>> -d
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> Jos=E9 Luis
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> Dan Wing <dwing@cisco.com> ha escrito:
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> On Jun 26, 2013, at 3:49 AM, Jose Saldana <jsaldana@unizar.es>
>>>>>> wrote:
>>>>>>>>>=20
>>>>>>>>> Question 4: Is TCM-TF interesting for the Industry? Should the
>>>>>>>>> IETF standardize this?
>>>>>>>>>=20
>>>>>>>>> Answer:
>>>>>>>>>=20
>>>>>>>>> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP
>>>>> traffic.
>>>>>>>>> So if RFC4170 was interesting, why not updating it?
>>>>>>>>>=20
>>>>>>>>> 2) TCM-TF can be useful in order to save bandwidth in many =
cases:
>>>>>>>>>=20
>>>>>>>>> - Aggregation network of *network operators*: We are saving
>>>>>>>>> bandwidth by optimizing and putting together traffic flows. Is
>>>>>>>>> this interesting for a network operator? What about
>>>> overprovisioning?
>>>>>>>>> The idea is that there are places and moments in which a =
number
>>>>>>>>> of flows based on small packets are in the same place and at =
the
>>>>>>>>> same moment. Then, TCM-TF can be applied in order to provide
>>>> flexibility.
>>>>>>>>> We are not optimizing the overall Internet traffic, we are
>>>>>>>>> optimizing specific flows with very tight delay requirements,
>>>>>>>>> which network operators have to take care of in a special way.
>>>>>>>>> www.huawei.com/ilink/en/download/HW_193034
>>>>>>>>>=20
>>>>>>>>> - *End to end* optimization: Nowadays, many appliances are =
used
>>>>>>>>> to connect remote offices of the same company (creating a =
VPN).
>>>>>>>>> So if a tunnel exists, why not optimizing this traffic when
>>>>>>>>> possible? We would save bandwidth in the access network, where
>>>>>>>>> it
>>>> can be scarce.
>>>>>>>>>=20
>>>>>>>>> - Wireless and satellite scenarios.
>>>>>>>>>=20
>>>>>>>>> "Cisco adds IP multiplexing to mobile satellite package", =
April
>>>>>>>>> 2012,
>>>>>>>>> http://www.networkworld.com/news/2012/040912-cisco-ip-
>>>>>> multiplexing-
>>>>>>>> 258082.html
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> Any other thoughts? Any other scenarios in mind? Potential
>>>>>>>>> beneficiaries?
>>>>>>>>>=20
>>>>>>>>> Some networks, today, use cRTP (RFC2508) on their access =
links.
>>>>>> This
>>>>>>>>> gives bandwidth savings on the access link, but consumes
>>>>>>>>> considerable CPU horsepower on the aggregation router (to
>>>>>>>>> perform
>>>>>> cRTP), but
>>>>>>>>> provides no bandwidth savings across the network core.   If,
>>>>>> instead,
>>>>>>>>> the bandwidth could be saved on the access link, across  the
>>>>>>>>> core, and on the far-end access link -- all without the CPU
>>>>>>>>> impact on the aggregation router -- it is a considerable win.
>>>>>>>>>=20
>>>>>>>>> -d
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> Jose
>>>>>>>>>=20
>>>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>>>>>> nombre
>>>>>>>>> de Jose Saldana Enviado el: lunes, 24 de junio de 2013 13:00
>>>>>>>>> Para: tcmtf@ietf.org
>>>>>>>>> Asunto: [tcmtf] Answers to possible questions in the BOF
>>>>>>>>>=20
>>>>>>>>> I would like to start a thread about possible questions people
>>>>>>>>> may ask in the BOF. Obviously, we also need answers, so we
>>>>>>>>> should
>>>>>> cooperate.
>>>>>>>>>=20
>>>>>>>>> This is different from the "questions to ask in the BOF". This
>>>>>>>>> will be discussed separately.
>>>>>>>>>=20
>>>>>>>>> Thanks!
>>>>>>>>>=20
>>>>>>>>> Jose
>>>>>>>>>=20
>>>>>>>>> _______________________________________________
>>>>>>>>> tcmtf mailing list
>>>>>>>>> tcmtf@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>>>> _______________________________________________
>>>>>>> tcmtf mailing list
>>>>>>> tcmtf@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>>>>=20
>>>>>>=20
>>>>>> --
>>>>>> "Esta vez no fallaremos, Doctor Infierno"
>>>>>>=20
>>>>>> Dr Diego R. Lopez
>>>>>> Telefonica I+D
>>>>>> http://people.tid.es/diego.lopez/
>>>>>>=20
>>>>>> e-mail: diego@tid.es
>>>>>> Tel:    +34 913 129 041
>>>>>> Mobile: +34 682 051 091
>>>>>> -----------------------------------------
>>>>>>=20
>>>>>>=20
>>>>>> ________________________________
>>>>>>=20
>>>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede
>>>>>> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo
>>>>>> electr=F3nico en el enlace situado m=E1s abajo.
>>>>>> This message is intended exclusively for its addressee. We only
>>>>>> send and receive email on the basis of the terms set out at:
>>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>>>>>> _______________________________________________
>>>>>> 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
>>>=20
>=20
>=20


From diego@tid.es  Thu Jul 18 02:36:20 2013
Return-Path: <diego@tid.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 A481511E80E7 for <tcmtf@ietfa.amsl.com>; Thu, 18 Jul 2013 02:36:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.804
X-Spam-Level: 
X-Spam-Status: No, score=-5.804 tagged_above=-999 required=5 tests=[AWL=-0.695, BAYES_05=-1.11, HTML_MESSAGE=0.001, 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 zHb59qmiCcuI for <tcmtf@ietfa.amsl.com>; Thu, 18 Jul 2013 02:36:15 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id CAF9C11E8101 for <tcmtf@ietf.org>; Thu, 18 Jul 2013 02:36:13 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MQ400D0SLCCQS@tid.hi.inet> for tcmtf@ietf.org; Thu, 18 Jul 2013 11:36:12 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 20.3D.03142.B07B7E15; Thu, 18 Jul 2013 11:36:12 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MQ400D0OLCBQS@tid.hi.inet> for tcmtf@ietf.org; Thu, 18 Jul 2013 11:36:11 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS8-MAD.hi.inet ([fe80::41c8:e965:8a6:de67%11]) with mapi id 14.02.0328.009; Thu, 18 Jul 2013 11:36:11 +0200
Date: Thu, 18 Jul 2013 09:36:11 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <001c01ce78ce$10ba6450$322f2cf0$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "<jsaldana@unizar.es>" <jsaldana@unizar.es>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A049CD1F357@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_T2YzYNEQyLjsLx2NHJkQ7g)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] TCM-TF and mobility
Thread-index: Ac54yD46kc6esDuLRW2yf9vSBPgA9gKwTlUA
X-AuditID: 0a5f4068-b7f128e000000c46-d4-51e7b70b76d8
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprEIsWRmVeSWpSXmKPExsXCFe/Apcuz/XmgwbW1rBa7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxpXra1gKNs5lrLj+/ixjA+O7LsYuRk4OCQETielXl7FB2GIS F+6tB7K5OIQENjJKPLwxlwXC+cEo8fPZRkYIZwOjRM+zOewgLSwCqhKX3jUwgdhsQPaj5t9g cWEBDYnv916BjeUUsJBouHmSCWKFgsSfc49ZQGwRAX2JG48h6pkF4iVWvHjKCmLzCnhLfF9y lBnCFpT4MfkeUD0HUE2uxMLGcIhycYnm1ptgYxgFZCXezZ/PCjFSU2J10xQ2CNtI4vT071Bf Ckgs2XOeGcIWlXj5+B8ryEghAXOJvRd0JjCKzUKybBbCsllIlkHYBhLvz81nhrC1JZYtfA1l 60ts/HKWEcI2k/hxdjkLspoFjByrGMWKk4oy0zNKchMzc9INDPUyMvUy81JLNjFC4jFjB+Py nSqHGAU4GJV4eG/wPA8UYk0sK67MPcQowcGsJMJbbgYU4k1JrKxKLcqPLyrNSS0+xMjEwSnV wMgxpdJnbvDKyb7Kz9zXli87vYrLUfL1TrOWAvbsh+UvfCZZS4b2rOeLubOfoTpsg4P2U5fr st473VfqrWDWmFf8faa91Qkpj9O3okKaBJ722J02O8IWvnDd3Yktsuc+tq9tmVn27eKXlw/U 2YpKWaf8f3hNpWftu2qW39lebZXVZ+0DHuypyFBiKc5INNRiLipOBACHYXwOpQIAAA==
References: <001c01ce78ce$10ba6450$322f2cf0$@unizar.es>
Cc: "<tcmtf@ietf.org>" <tcmtf@ietf.org>, =?Windows-1252?Q?Jos=E9_Ruiz_Mas?= <jruiz@unizar.es>
Subject: Re: [tcmtf] TCM-TF and mobility
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, 18 Jul 2013 09:36:20 -0000

--Boundary_(ID_T2YzYNEQyLjsLx2NHJkQ7g)
Content-type: text/plain; charset=Windows-1252
Content-transfer-encoding: quoted-printable

Hi,

Getting to this after another discussion on LISP and TCM-TF, let me say tha=
t TCM can benefit mobility-enhancing protocols the same way it can benefit =
security protocols (as we have discussed with the IPsec case) and possibly =
any other tunneling-based techniques. Grouping flows and optimizing their t=
ransport translates into more efficient tunneling. It is true we are not ta=
lking here about fast hand-over mobility, but of the case of roaming users,=
 but anyway it is a relevant portion of mobility use cases.

Be goode,

On 4 Jul 2013, at 17:49 , Jose Saldana wrote:

Hi all.

We are discussing a lot about security and TCM-TF. Why not talking a bit ab=
out TCM-TF and mobility?

A) First question: How can user mobility and TCM-TF affect each other?

1- Residential scenario: I am a network operator, and I am TCM-optimizing a=
 number of real-time (VoIP, online games) flows which are present in my acc=
ess network. What happens if one of the users moves to another location? Is=
 there any difference between the case in which the traffic is TCM-optimize=
d and the non-TCM case?

In a first approach, I don=92t think so. TCM is applied in a network segmen=
t. The end hosts may not even notice that TCM is being used. It would be se=
en as an additional network delay and jitter. Thus, if the user moves and a=
 flow disappears, nothing happens to the rest of the flows. And regarding t=
he flow of the mobile user, it will be managed by the mobility protocol in =
the same way.


2-Corporate environment: I am using two network appliances in order to crea=
te a VPN between two offices of my company. There is a TCM session between =
the two appliances, optimizing a number of VoIP calls. If a user gets out o=
f the office and his/her VoIP call moves to a 3G data connection, what happ=
ens? Is there any difference with respect to the non-TCM case?

I think the answer is the same as in 1.


3- Machine to machine scenario (sensors, industrial control): Does mobility=
 exist here? Any ideas?


B) Second question: Can any mobility protocol take advantage of TCM-TF?

Just an idea (suggested by Jose Ruiz) regarding *PMIPv6* (RFC5213, http://t=
ools.ietf.org/html/rfc5213):

This network-based mobility protocol creates a tunnel between the LMA (simi=
lar to the HA in MIPv6) and the MAG (typically runs on the access router).

This *tunnel is shared by all the flows* between the LMA and the MAG:
=93the bidirectional tunnel between the LMA and MAG is typically a shared t=
unnel, and can be employed for routing traffic streams for different MNs at=
tached to the same MAG. It extends the 1:1 relation between a tunnel and an=
 MN=92s binding cache entry to a 1:m relation, reflecting the shared nature=
 of the tunnel=94 [1]. The tunnel between LMA and MAG can be based on GRE o=
r IP-in-IP.

So we have a tunnel shared by a number of flows. Why not optimizing that tr=
affic? Instead of a tunnel including lots of small packets, can we multiple=
x them and compress headers? Are these bandwidth and pps reductions interes=
ting?


Thanks,

Jose

[1]  Ki-Sik Kong; Wonjun Lee; Youn-Hee Han; Myung-Ki Shin; HeungRyeol You, =
"Mobility management for all-IP mobile networks: mobile IPv6 vs. proxy mobi=
le IPv6," Wireless Communications, IEEE , vol.15, no.2, pp.36,45, April 200=
8
http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&arnumber=3D4492976&isnumbe=
r=3D4492967
http://voiplab.niu.edu.tw/ppt/ipv6/R9843011.pdf

More info:
http://en.wikipedia.org/wiki/Proxy_Mobile_IPv6
http://www.cisco.com/en/US/docs/ios-xml/ios/mob_pmipv6/configuration/xe-3s/=
deployment/Proxy_Mobile_IPv6_Network-Based_Mobility.html
_______________________________________________
tcmtf mailing list
tcmtf@ietf.org<mailto:tcmtf@ietf.org>
https://www.ietf.org/mailman/listinfo/tcmtf


--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

--Boundary_(ID_T2YzYNEQyLjsLx2NHJkQ7g)
Content-id: <5006211E6C1463438C90E7EF4343A705@hi.inet>
Content-type: text/html; charset=Windows-1252
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<base href=3D"">
</head>
<body style=3D"word-wrap:break-word">
Hi,
<div><br>
</div>
<div>Getting to this after another discussion on LISP and TCM-TF, let me sa=
y that TCM can benefit mobility-enhancing protocols the same way it can ben=
efit security protocols (as we have discussed with the IPsec case) and poss=
ibly any other tunneling-based techniques.
 Grouping flows and optimizing their transport translates into more efficie=
nt tunneling. It is true we are not talking here about fast hand-over mobil=
ity, but of the case of roaming users, but anyway it is a relevant portion =
of mobility use cases.</div>
<div><br>
</div>
<div>Be goode,</div>
<div><br>
<div>
<div>On 4 Jul 2013, at 17:49 , Jose Saldana wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse:separate; font-family:Helvetica; font-style:normal; font-variant:n=
ormal; font-weight:normal; letter-spacing:normal; line-height:normal; orpha=
ns:2; text-indent:0px; text-transform:none; white-space:normal; widows:2; w=
ord-spacing:0px; font-size:medium">
<div lang=3D"ES">
<div class=3D"WordSection1" style=3D"">
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
Hi all.</div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
&nbsp;</div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">We are discussing a lot about security and TCM-TF. Why=
 not talking a bit about TCM-TF and mobility?</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">A) First question: How can user mobility and TCM-TF af=
fect each other?</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">1- Residential scenario: I am a network operator, and =
I am TCM-optimizing a number of real-time (VoIP, online games) flows which =
are present in my access network. What happens if one of the users moves to=
 another location? Is there any difference
 between the case in which the traffic is TCM-optimized and the non-TCM cas=
e?</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">In a first approach, I don=92t think so. TCM is applie=
d in a network segment. The end hosts may not even notice that TCM is being=
 used. It would be seen as an additional network delay and jitter. Thus, if=
 the user moves and a flow disappears,
 nothing happens to the rest of the flows. And regarding the flow of the mo=
bile user, it will be managed by the mobility protocol in the same way.</sp=
an></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">2-Corporate environment: I am using two network applia=
nces in order to create a VPN between two offices of my company. There is a=
 TCM session between the two appliances, optimizing a number of VoIP calls.=
 If a user gets out of the office
 and his/her VoIP call moves to a 3G data connection, what happens? Is ther=
e any difference with respect to the non-TCM case?</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">I think the answer is the same as in 1.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">3- Machine to machine scenario (sensors, industrial co=
ntrol): Does mobility exist here? Any ideas?</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">B) Second question: Can any mobility protocol take adv=
antage of TCM-TF?</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">Just an idea (suggested by Jose Ruiz) regarding *<b>PM=
IPv6</b>* (RFC5213,<span class=3D"Apple-converted-space">&nbsp;</span></spa=
n><a href=3D"http://tools.ietf.org/html/rfc5213" style=3D"color:blue; text-=
decoration:underline"><span lang=3D"EN-US">http://tools.ietf.org/html/rfc52=
13</span></a><span lang=3D"EN-US">):</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">This network-based mobility protocol creates a tunnel =
between the LMA (similar to the HA in MIPv6) and the MAG (typically runs on=
 the access router).</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">This *<b>tunnel is shared by all the flows</b>* betwee=
n the LMA and the MAG:</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">=93the bidirectional tunnel between the LMA and MAG is=
 typically a shared tunnel, and can be employed for routing traffic streams=
 for different MNs attached to the same MAG. It extends the 1:1 relation be=
tween a tunnel and an MN=92s binding cache
 entry to a 1:m relation, reflecting the shared nature of the tunnel=94 [1]=
. The tunnel between LMA and MAG can be based on GRE or IP-in-IP.</span></d=
iv>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">So we have a tunnel shared by a number of flows. Why n=
ot optimizing that traffic? Instead of a tunnel including lots of small pac=
kets, can we multiplex them and compress headers? Are these bandwidth and p=
ps reductions interesting?</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">Thanks,</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">Jose</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">[1] &nbsp;Ki-Sik Kong; Wonjun Lee; Youn-Hee Han; Myung=
-Ki Shin; HeungRyeol You, &quot;Mobility management for all-IP mobile netwo=
rks: mobile IPv6 vs. proxy mobile IPv6,&quot; Wireless Communications, IEEE=
 , vol.15, no.2, pp.36,45, April 2008</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US"><a href=3D"http://ieeexplore.ieee.org/stamp/stamp.jsp?=
tp=3D&amp;arnumber=3D4492976&amp;isnumber=3D4492967" style=3D"color:blue; t=
ext-decoration:underline">http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&=
amp;arnumber=3D4492976&amp;isnumber=3D4492967</a></span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<a href=3D"http://voiplab.niu.edu.tw/ppt/ipv6/R9843011.pdf" style=3D"color:=
blue; text-decoration:underline"><span lang=3D"EN-US">http://voiplab.niu.ed=
u.tw/ppt/ipv6/R9843011.pdf</span></a><span lang=3D"EN-US"></span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">More info:</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<a href=3D"http://en.wikipedia.org/wiki/Proxy_Mobile_IPv6" style=3D"color:b=
lue; text-decoration:underline"><span lang=3D"EN-US">http://en.wikipedia.or=
g/wiki/Proxy_Mobile_IPv6</span></a></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<a href=3D"http://www.cisco.com/en/US/docs/ios-xml/ios/mob_pmipv6/configura=
tion/xe-3s/deployment/Proxy_Mobile_IPv6_Network-Based_Mobility.html" style=
=3D"color:blue; text-decoration:underline">http://www.cisco.com/en/US/docs/=
ios-xml/ios/mob_pmipv6/configuration/xe-3s/deployment/Proxy_Mobile_IPv6_Net=
work-Based_Mobility.html</a></div>
</div>
_______________________________________________<br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org" style=3D"color:blue; text-decoration:unde=
rline">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color:blue=
; text-decoration:underline">https://www.ietf.org/mailman/listinfo/tcmtf</a=
><br>
</div>
</span></blockquote>
</div>
<br>
<div><span class=3D"Apple-style-span" style=3D"border-collapse:separate; co=
lor:rgb(0,0,0); font-family:Helvetica; font-style:normal; font-variant:norm=
al; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:=
2; text-indent:0px; text-transform:none; white-space:normal; widows:2; word=
-spacing:0px; font-size:medium"><span class=3D"Apple-style-span" style=3D"b=
order-collapse:separate; color:rgb(0,0,0); font-family:Helvetica; font-styl=
e:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; l=
ine-height:normal; orphans:2; text-indent:0px; text-transform:none; white-s=
pace:normal; widows:2; word-spacing:0px; font-size:medium">
<div style=3D"word-wrap:break-word"><span class=3D"Apple-style-span" style=
=3D"border-collapse:separate; color:rgb(0,0,0); font-family:Helvetica; font=
-style:normal; font-variant:normal; font-weight:normal; letter-spacing:norm=
al; line-height:normal; orphans:2; text-indent:0px; text-transform:none; wh=
ite-space:normal; widows:2; word-spacing:0px; font-size:medium">
<div style=3D"word-wrap:break-word"><br>
--<br>
&quot;Esta vez no fallaremos, Doctor Infierno&quot;<br>
<br>
Dr Diego R. Lopez<br>
Telefonica I&#43;D</div>
<div style=3D"word-wrap:break-word"><a href=3D"http://people.tid.es/diego.l=
opez/">http://people.tid.es/diego.lopez/</a><br>
<br>
e-mail: diego@tid.es<br>
Tel: &nbsp; &nbsp;&#43;34 913 129 041<br>
Mobile: &#43;34 682 051 091<br>
-----------------------------------------</div>
</span></div>
</span></span></div>
<br>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_T2YzYNEQyLjsLx2NHJkQ7g)--

From jsaldana@unizar.es  Tue Jul 23 08:28:12 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 6BAD511E825C for <tcmtf@ietfa.amsl.com>; Tue, 23 Jul 2013 08:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.739
X-Spam-Level: 
X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, 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 rNQuns2k68us for <tcmtf@ietfa.amsl.com>; Tue, 23 Jul 2013 08:28:06 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 6BCEB11E812E for <tcmtf@ietf.org>; Tue, 23 Jul 2013 08:28:00 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r6NFRm0Y021206; Tue, 23 Jul 2013 17:27:49 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
In-Reply-To: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
Date: Tue, 23 Jul 2013 17:27:54 +0200
Organization: Universidad de Zaragoza
Message-ID: <004701ce87b9$36200250$a26006f0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0048_01CE87C9.F9A96E90"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHxl5HfJe4XxEPJrqhURPk2/vEH5pksNmXg
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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, 23 Jul 2013 15:28:12 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0048_01CE87C9.F9A96E90
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Today I have been talking with Bob Briscoe (in cc) and he has asked me =
this
question (more or less). Since it is interesting, I would like to hear =
the
opinion of the list.

=20

Question 7: There exist proprietary products (WAN accelerators and
Performance Enhancing Proxies (PEPs) which are able to optimize traffic.

=20

How will those companies respond to attempts to standardize these =
protocols?
Will it be a problem for them? Will it be interesting?

=20

=20

My answer (more ideas required):

=20

WAN accelerators and PEPs are only part of the involved actors. That is =
the
end-to-end case, in which the end user performs the optimization, and =
the
network does not intervene. I think a standard would be interesting, in
order to permit devices from different companies to interact and =
optimize
traffic.

=20

But there is still another case: optimization within the network. =
Network
operators may be interested because they can find paths in the network
shared by a lot of small-packet flows, so optimization can also be
interesting there. Perhaps the optimizers can be dormant, and be =
activated
only when required (a traffic rush at certain places or moments).

=20

And sometimes the optimization can take place between an end-user device =
and
an operator device. For example, an internet caf=E9 or a rural village =
in a
developing country, with a single connection shared by a number of =
people.
So a standard protocol for doing that can also be interesting.

=20

Or e.g. two network operators may sign an agreement in order to optimize
traffic flows between their aggregation networks. A standard is then
necessary.

=20

Any other ideas? Any other reasons for standardization?

=20

Thanks, Bob and everybody.

=20

Jose

=20

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de =
Jose
Saldana
Enviado el: lunes, 24 de junio de 2013 13:00
Para: tcmtf@ietf.org
Asunto: [tcmtf] Answers to possible questions in the BOF

=20

I would like to start a thread about possible questions people may ask =
in
the BOF. Obviously, we also need answers, so we should cooperate.

=20

This is different from the =93questions to ask in the BOF=94. This will =
be
discussed separately.

=20

Thanks!

=20

Jose

=20


------=_NextPart_000_0048_01CE87C9.F9A96E90
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Today I have been talking with Bob =
Briscoe (in cc) and he has asked me this question (more or less). Since =
it is interesting, I would like to hear the opinion of the =
list.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><b><span lang=3DEN-US style=3D'color:#1F497D'>Question =
7</span></b><span lang=3DEN-US style=3D'color:#1F497D'>: There exist =
proprietary products (WAN accelerators and Performance Enhancing Proxies =
(PEPs) which are able to optimize traffic.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>How will =
those companies respond to attempts to standardize these protocols? Will =
it be a problem for them? Will it be =
interesting?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>My answer =
(more ideas required):<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>WAN =
accelerators and PEPs are only part of the involved actors. That is the =
end-to-end case, in which the end user performs the optimization, and =
the network does not intervene. I think a standard would be interesting, =
in order to permit devices from different companies to interact and =
optimize traffic.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>But there =
is still another case: optimization within the network. Network =
operators may be interested because they can find paths in the network =
shared by a lot of small-packet flows, so optimization can also be =
interesting there. Perhaps the optimizers can be dormant, and be =
activated only when required (a traffic rush at certain places or =
moments).<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>And =
sometimes the optimization can take place between an end-user device and =
an operator device. For example, an internet caf&eacute; or a rural =
village in a developing country, with a single connection shared by a =
number of people. So a standard protocol for doing that can also be =
interesting.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Or e.g. two =
network operators may sign an agreement in order to optimize traffic =
flows between their aggregation networks. A standard is then =
necessary.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Any other =
ideas? Any other reasons for standardization?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Thanks, Bob =
and everybody.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'>De:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'> tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] =
<b>En nombre de </b>Jose Saldana<br><b>Enviado el:</b> lunes, 24 de =
junio de 2013 13:00<br><b>Para:</b> tcmtf@ietf.org<br><b>Asunto:</b> =
[tcmtf] Answers to possible questions in the =
BOF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>I would like to start a thread about possible questions =
people may ask in the BOF. Obviously, we also need answers, so we should =
cooperate.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This is different from the &#8220;questions to ask in the =
BOF&#8221;. This will be discussed separately.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Thanks!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:ES'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_0048_01CE87C9.F9A96E90--


From diego@tid.es  Tue Jul 23 09:18:56 2013
Return-Path: <diego@tid.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 236A911E82C2 for <tcmtf@ietfa.amsl.com>; Tue, 23 Jul 2013 09:18:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 pj4O0jhb3Qw3 for <tcmtf@ietfa.amsl.com>; Tue, 23 Jul 2013 09:18:52 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 7D48211E82D7 for <tcmtf@ietf.org>; Tue, 23 Jul 2013 09:18:45 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MQE00K55DB156@tid.hi.inet> for tcmtf@ietf.org; Tue, 23 Jul 2013 18:18:37 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 05.A0.02911.CDCAEE15; Tue, 23 Jul 2013 18:18:37 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MQE00K4ZDB056@tid.hi.inet> for tcmtf@ietf.org; Tue, 23 Jul 2013 18:18:36 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Tue, 23 Jul 2013 18:17:08 +0200
Date: Tue, 23 Jul 2013 16:18:36 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <004701ce87b9$36200250$a26006f0$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "<jsaldana@unizar.es>" <jsaldana@unizar.es>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A049CD274C4@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_l3ii8SS4NwX4U+7K9Sb5xw)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Answers to possible questions in the BOF
Thread-index: Ac5wycGHbApylKz/RhmtAnL3dgONFwW3q5AAAAHE2YA=
X-AuditID: 0a5f4e69-b7f118e000000b5f-ae-51eeacdc1abc
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIIsWRmVeSWpSXmKPExsXCFe9nqHt3zbtAg8UrhC12fd7A6MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujJ2N9gVP2hkr1nUsZm5gfFzRxcjJISFgIvF4/Vx2CFtM4sK9 9WxdjFwcQgLbGSX+vdvAAuH8ZJSY/XU3M4QzjVFi0511LCAtLAKqEhumLGcFsdmA7EfNv8FG CQvYSuz5e4cRxOYUsJBo27mTEWKFgsSfc4/BekUE9CVuPAap5+BgFvCUuHxCFiTMK+At8aHl IDuELSjxY/I9sHJmgVyJGa2PoGxxiebWm2A2o4CsxLv581khRtpJTN+2EWq8lcSEg4vYINYK SCzZc54ZwhaVePn4H1i9kECqxJXZe5gnMIrNQrJuFpJ1s5Csg7ANJN6fm88MYWtLLFv4GsrW l9j45SzjLLBvzCTaX6ghK1nAyLGKUaw4qSgzPaMkNzEzJ93ASC8jUy8zL7VkEyMkGjN3MC7f qXKIUYCDUYmH98Scd4FCrIllxZW5hxglOJiVRHiXSgGFeFMSK6tSi/Lji0pzUosPMTJxcEo1 MLJFHHD6oLdonsozC++b/HJKf2SqX67oFF94oWR+2nShj39ffyr6t/tw9QOGNh4Bg/IClUyb 7rsurPPz7fbN+Wv1Xm+5st+7RRa9cWqyE3VTl50NX3c9PWyDxxLbjBmys6sjc5O07E9ly2+7 +vlRkSvbllSnInUObs0ljqkSJ6Y9LtjsvmryESWW4oxEQy3mouJEAFmloNOkAgAA
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <004701ce87b9$36200250$a26006f0$@unizar.es>
Cc: "<tcmtf@ietf.org>" <tcmtf@ietf.org>, Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: [tcmtf] Answers to possible questions in 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, 23 Jul 2013 16:18:56 -0000

--Boundary_(ID_l3ii8SS4NwX4U+7K9Sb5xw)
Content-type: text/plain; charset=Windows-1252
Content-transfer-encoding: quoted-printable

Hi,

I think that we could add the possibility of leveraging TCM in the case enc=
apsulation approaches are in use, like mobility (LISP) or security (IPsec)

Be goode,

On 23 Jul 2013, at 17:27 , Jose Saldana wrote:

Today I have been talking with Bob Briscoe (in cc) and he has asked me this=
 question (more or less). Since it is interesting, I would like to hear the=
 opinion of the list.

Question 7: There exist proprietary products (WAN accelerators and Performa=
nce Enhancing Proxies (PEPs) which are able to optimize traffic.

How will those companies respond to attempts to standardize these protocols=
? Will it be a problem for them? Will it be interesting?


My answer (more ideas required):

WAN accelerators and PEPs are only part of the involved actors. That is the=
 end-to-end case, in which the end user performs the optimization, and the =
network does not intervene. I think a standard would be interesting, in ord=
er to permit devices from different companies to interact and optimize traf=
fic.

But there is still another case: optimization within the network. Network o=
perators may be interested because they can find paths in the network share=
d by a lot of small-packet flows, so optimization can also be interesting t=
here. Perhaps the optimizers can be dormant, and be activated only when req=
uired (a traffic rush at certain places or moments).

And sometimes the optimization can take place between an end-user device an=
d an operator device. For example, an internet caf=E9 or a rural village in=
 a developing country, with a single connection shared by a number of peopl=
e. So a standard protocol for doing that can also be interesting.

Or e.g. two network operators may sign an agreement in order to optimize tr=
affic flows between their aggregation networks. A standard is then necessar=
y.

Any other ideas? Any other reasons for standardization?

Thanks, Bob and everybody.

Jose

De: tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-bou=
nces@ietf.org] En nombre de Jose Saldana
Enviado el: lunes, 24 de junio de 2013 13:00
Para: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: [tcmtf] Answers to possible questions in the BOF

I would like to start a thread about possible questions people may ask in t=
he BOF. Obviously, we also need answers, so we should cooperate.

This is different from the =93questions to ask in the BOF=94. This will be =
discussed separately.

Thanks!

Jose

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


--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

--Boundary_(ID_l3ii8SS4NwX4U+7K9Sb5xw)
Content-id: <D7F5DB49838D7345A6EB425ACABA9AD5@hi.inet>
Content-type: text/html; charset=Windows-1252
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<base href=3D"">
</head>
<body style=3D"word-wrap:break-word">
Hi,
<div><br>
</div>
<div>I think that we could add the possibility of leveraging TCM in the cas=
e encapsulation approaches are in use, like mobility (LISP) or security (IP=
sec)</div>
<div><br>
</div>
<div>Be goode,</div>
<div><br>
<div>
<div>On 23 Jul 2013, at 17:27 , Jose Saldana wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse:separate; font-family:Helvetica; font-style:normal; font-variant:n=
ormal; font-weight:normal; letter-spacing:normal; line-height:normal; orpha=
ns:2; text-indent:0px; text-transform:none; white-space:normal; widows:2; w=
ord-spacing:0px; font-size:medium">
<div lang=3D"ES">
<div class=3D"WordSection1" style=3D"">
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">Today I have been talki=
ng with Bob Briscoe (in cc) and he has asked me this question (more or less=
). Since it is interesting, I would like to hear the opinion of the list.</=
span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<b><span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">Question 7</span></b=
><span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">: There exist propriet=
ary products (WAN accelerators and Performance Enhancing Proxies (PEPs) whi=
ch are able to optimize traffic.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">How will those companie=
s respond to attempts to standardize these protocols? Will it be a problem =
for them? Will it be interesting?</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">My answer (more ideas r=
equired):</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">WAN accelerators and PE=
Ps are only part of the involved actors. That is the end-to-end case, in wh=
ich the end user performs the optimization, and the network does not interv=
ene. I think a standard would be interesting,
 in order to permit devices from different companies to interact and optimi=
ze traffic.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">But there is still anot=
her case: optimization within the network. Network operators may be interes=
ted because they can find paths in the network shared by a lot of small-pac=
ket flows, so optimization can also
 be interesting there. Perhaps the optimizers can be dormant, and be activa=
ted only when required (a traffic rush at certain places or moments).</span=
></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">And sometimes the optim=
ization can take place between an end-user device and an operator device. F=
or example, an internet caf=E9 or a rural village in a developing country, =
with a single connection shared by a number
 of people. So a standard protocol for doing that can also be interesting.<=
/span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">Or e.g. two network ope=
rators may sign an agreement in order to optimize traffic flows between the=
ir aggregation networks. A standard is then necessary.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">Any other ideas? Any ot=
her reasons for standardization?</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">Thanks, Bob and everybo=
dy.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">Jose</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></div>
<div style=3D"border-top-style:none; border-right-style:none; border-bottom=
-style:none; border-width:initial; border-color:initial; border-left-style:=
solid; border-left-color:blue; border-left-width:1.5pt; padding-top:0cm; pa=
dding-right:0cm; padding-bottom:0cm; padding-left:4pt">
<div>
<div style=3D"border-right-style:none; border-bottom-style:none; border-lef=
t-style:none; border-width:initial; border-color:initial; border-top-style:=
solid; border-top-color:rgb(181,196,223); border-top-width:1pt; padding-top=
:3pt; padding-right:0cm; padding-bottom:0cm; padding-left:0cm">
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<b><span style=3D"font-size:10pt; font-family:Tahoma,sans-serif">De:</span>=
</b><span style=3D"font-size:10pt; font-family:Tahoma,sans-serif"><span cla=
ss=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto:tcmtf-bounces@i=
etf.org" style=3D"color:blue; text-decoration:underline">tcmtf-bounces@ietf=
.org</a><span class=3D"Apple-converted-space">&nbsp;</span>[mailto:tcmtf-bo=
unces@ietf.org]<span class=3D"Apple-converted-space">&nbsp;</span><b>En
 nombre de<span class=3D"Apple-converted-space">&nbsp;</span></b>Jose Salda=
na<br>
<b>Enviado el:</b><span class=3D"Apple-converted-space">&nbsp;</span>lunes,=
 24 de junio de 2013 13:00<br>
<b>Para:</b><span class=3D"Apple-converted-space">&nbsp;</span><a href=3D"m=
ailto:tcmtf@ietf.org" style=3D"color:blue; text-decoration:underline">tcmtf=
@ietf.org</a><br>
<b>Asunto:</b><span class=3D"Apple-converted-space">&nbsp;</span>[tcmtf] An=
swers to possible questions in the BOF</span></div>
</div>
</div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
&nbsp;</div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">I would like to start a thread about possible question=
s people may ask in the BOF. Obviously, we also need answers, so we should =
cooperate.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">This is different from the =93questions to ask in the =
BOF=94. This will be discussed separately.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">Thanks!</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">Jose</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
</div>
</div>
_______________________________________________<br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org" style=3D"color:blue; text-decoration:unde=
rline">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color:blue=
; text-decoration:underline">https://www.ietf.org/mailman/listinfo/tcmtf</a=
><br>
</div>
</span></blockquote>
</div>
<br>
<div><span class=3D"Apple-style-span" style=3D"border-collapse:separate; co=
lor:rgb(0,0,0); font-family:Helvetica; font-style:normal; font-variant:norm=
al; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:=
2; text-indent:0px; text-transform:none; white-space:normal; widows:2; word=
-spacing:0px; font-size:medium"><span class=3D"Apple-style-span" style=3D"b=
order-collapse:separate; color:rgb(0,0,0); font-family:Helvetica; font-styl=
e:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; l=
ine-height:normal; orphans:2; text-indent:0px; text-transform:none; white-s=
pace:normal; widows:2; word-spacing:0px; font-size:medium">
<div style=3D"word-wrap:break-word"><span class=3D"Apple-style-span" style=
=3D"border-collapse:separate; color:rgb(0,0,0); font-family:Helvetica; font=
-style:normal; font-variant:normal; font-weight:normal; letter-spacing:norm=
al; line-height:normal; orphans:2; text-indent:0px; text-transform:none; wh=
ite-space:normal; widows:2; word-spacing:0px; font-size:medium">
<div style=3D"word-wrap:break-word"><br>
--<br>
&quot;Esta vez no fallaremos, Doctor Infierno&quot;<br>
<br>
Dr Diego R. Lopez<br>
Telefonica I&#43;D</div>
<div style=3D"word-wrap:break-word"><a href=3D"http://people.tid.es/diego.l=
opez/">http://people.tid.es/diego.lopez/</a><br>
<br>
e-mail: diego@tid.es<br>
Tel: &nbsp; &nbsp;&#43;34 913 129 041<br>
Mobile: &#43;34 682 051 091<br>
-----------------------------------------</div>
</span></div>
</span></span></div>
<br>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_l3ii8SS4NwX4U+7K9Sb5xw)--

From jsaldana@unizar.es  Wed Jul 24 04:45:20 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 DB62111E818B for <tcmtf@ietfa.amsl.com>; Wed, 24 Jul 2013 04:45:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.669
X-Spam-Level: 
X-Spam-Status: No, score=-5.669 tagged_above=-999 required=5 tests=[AWL=0.930,  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 Vv8PKSdAg+su for <tcmtf@ietfa.amsl.com>; Wed, 24 Jul 2013 04:45:16 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id E418311E80E0 for <tcmtf@ietf.org>; Wed, 24 Jul 2013 04:45:12 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r6OBj5FO022151 for <tcmtf@ietf.org>; Wed, 24 Jul 2013 13:45:09 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 24 Jul 2013 13:45:09 +0200
Organization: Universidad de Zaragoza
Message-ID: <00bd01ce8863$41e57660$c5b06320$@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: Ac6IYsh8PL27lPowS5yCMVA7xd5a2Q==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] TCM-TF BOF poster in the welcome reception
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
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: Wed, 24 Jul 2013 11:45:21 -0000

Hi all,

During the Welcome Reception next Sunday in Berlin (5pm to 7pm), there =
will
be a poster announcing the TCM-TF BOF in Berlin. At least Diego, Manuel,
Mirko and I will be there (or in the proximity) in order to talk with =
people
interested.

It can be a good opportunity to say "hello" to everyone and to =
coordinate
the efforts for the week.

See you there!

Jose

> -----Mensaje original-----
> De: 87attendees-bounces@ietf.org [mailto:87attendees-bounces@ietf.org]
> En nombre de IETF Chair
> Enviado el: mi=E9rcoles, 24 de julio de 2013 8:22
> Para: ietf-announce@ietf.org
> CC: 87 attendees
> Asunto: [87attendees] BOF posters in the welcome reception
>=20
> I wanted to let you know about an experiment we are trying out in =
Berlin.
>=20
> At this meeting we have quite many BOFs. This is of course great, it =
is
good
> that people are bringing new work to the IETF. I look forward to the
> discussions during the week and hopefully a number of new working =
groups
> will eventually be created.
>=20
> But we want as many people as possible to become involved in these
efforts,
> or at least provide their feedback during the week. So we have given =
an
> opportunity for the BOFs to display a poster in the Welcome Reception
> (Sunday 5pm to 7pm). If you are attending the reception, take a look =
at
the
> posters and look for topics that interest you. Someone running the BOF =
is
> also likely standing by, so you can also get directly involved in
discussions,
> sign up to help, etc. We hope that this helps you all network with =
others
> even more :-)
>=20
> Jari Arkko
> IETF Chair
>=20
> _______________________________________________
> 87attendees mailing list
> 87attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/87attendees


From jsaldana@unizar.es  Tue Jul 30 02:04:55 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 E896821E80BF for <tcmtf@ietfa.amsl.com>; Tue, 30 Jul 2013 02:04:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.761
X-Spam-Level: 
X-Spam-Status: No, score=-5.761 tagged_above=-999 required=5 tests=[AWL=0.837,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 2pZW9opBGP54 for <tcmtf@ietfa.amsl.com>; Tue, 30 Jul 2013 02:04:06 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 9B9BD21E80C8 for <tcmtf@ietf.org>; Tue, 30 Jul 2013 02:02:01 -0700 (PDT)
Received: from jsaldanapc (dhcp-92db.meeting.ietf.org [130.129.10.219]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r6U91m38022552 for <tcmtf@ietf.org>; Tue, 30 Jul 2013 11:01:52 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Tue, 30 Jul 2013 11:01:44 +0200
Message-ID: <002801ce8d03$6f149040$4d3db0c0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0029_01CE8D14.329DFC80"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6NAy7ACvSkcd4ASFSVBKCZdQjznw==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] Deadlines for the different TCM-TF documents
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, 30 Jul 2013 09:04:56 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0029_01CE8D14.329DFC80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

 

Just a question for the BOF. Although in the presentation we are not talking
about the deadlines, we should have something in mind. What about this?

 

TCM-TF Reference Model: 9-12 months from the (eventual) creation of a WG

 

TCM-TF Negotiation protocol: 18 months

 

TCM-TF Recommendations: 12 months

 

I would need your feedback.

 

Thanks a lot!

 

Jose


------=_NextPart_000_0029_01CE8D14.329DFC80
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DES-TRAD>Hi all,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DES-TRAD><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Just a question for the BOF. Although in the presentation =
we are not talking about the deadlines, we should have something in =
mind. What about this?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>TCM-TF Reference Model: 9-12 months from the (eventual) =
creation of a WG<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>TCM-TF Negotiation protocol: 18 =
months<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>TCM-TF Recommendations: 12 months<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>I would need your =
feedback.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Thanks a lot!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US>Jose<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_0029_01CE8D14.329DFC80--


From dwing@cisco.com  Tue Jul 30 04:06:27 2013
Return-Path: <dwing@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 3E93911E81CA for <tcmtf@ietfa.amsl.com>; Tue, 30 Jul 2013 04:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.575
X-Spam-Level: 
X-Spam-Status: No, score=-110.575 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 diWCV5Lq854Z for <tcmtf@ietfa.amsl.com>; Tue, 30 Jul 2013 04:06:22 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 8276B11E810D for <tcmtf@ietf.org>; Tue, 30 Jul 2013 04:06:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4891; q=dns/txt; s=iport; t=1375182364; x=1376391964; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=lodJPeVl5ARzbjriq5kXhFTVmHkvWQ8zEgsfZHPvztE=; b=jdgOhoEc7moQeafWbqc09JX9R0cmA4e7h061NWgWpN3jalSepF/MxRw8 jLfIu3U6ioTllrxSzf7bH+MiUFAw8gq+1xfSoN/GRadfGsZNA2BmArMzg LoJI8XWKxKexvZC2Wj42D4pV8khrJnoitv5Pa5naVG6VD8sSoU2ORPE2s Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAP2c91GrRDoI/2dsb2JhbABbgkJENb5fgR0WdIIkAQEBAwEBAQFrCwULCw44JzAGE4gKBQ24fwSPegQHgxhvA5dfkUyDFjo
X-IronPort-AV: E=Sophos;i="4.89,777,1367971200"; d="scan'208,217";a="84839542"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 30 Jul 2013 11:06:03 +0000
Received: from sjc-vpn3-38.cisco.com (sjc-vpn3-38.cisco.com [10.21.64.38]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6UB62XQ011475; Tue, 30 Jul 2013 11:06:02 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_020967AD-6372-4AD0-ADA5-F034C2B9DA18"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <002801ce8d03$6f149040$4d3db0c0$@unizar.es>
Date: Tue, 30 Jul 2013 13:06:01 +0200
Message-Id: <21C48DB1-66DA-44E0-9A48-A60B5C1FF691@cisco.com>
References: <002801ce8d03$6f149040$4d3db0c0$@unizar.es>
To: Jose Saldana <jsaldana@unizar.es>
X-Mailer: Apple Mail (2.1508)
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Deadlines for the different TCM-TF documents
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, 30 Jul 2013 11:06:27 -0000

--Apple-Mail=_020967AD-6372-4AD0-ADA5-F034C2B9DA18
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Seems reasonable.

-d

On Jul 30, 2013, at 11:01 AM, Jose Saldana <jsaldana@unizar.es> wrote:

> Hi all,
> =20
> Just a question for the BOF. Although in the presentation we are not =
talking about the deadlines, we should have something in mind. What =
about this?
> =20
> TCM-TF Reference Model: 9-12 months from the (eventual) creation of a =
WG
> =20
> TCM-TF Negotiation protocol: 18 months
> =20
> TCM-TF Recommendations: 12 months
> =20
> I would need your feedback.
> =20
> Thanks a lot!
> =20
> Jose
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


--Apple-Mail=_020967AD-6372-4AD0-ADA5-F034C2B9DA18
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Seems =
reasonable.<div><br></div><div>-d</div><div><br><div><div>On Jul 30, =
2013, at 11:01 AM, Jose Saldana &lt;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div lang=3D"ES" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"ES-TRAD">Hi =
all,<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"ES-TRAD">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">Just a question for the BOF. Although in the presentation =
we are not talking about the deadlines, we should have something in =
mind. What about this?<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">TCM-TF Reference Model: 9-12 months from the (eventual) =
creation of a WG<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">TCM-TF Negotiation protocol: 18 =
months<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">TCM-TF Recommendations: 12 =
months<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">I would need your feedback.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">Thanks a =
lot!<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">Jose<o:p></o:p></span></div></div>_________________________=
______________________<br>tcmtf mailing list<br><a =
href=3D"mailto:tcmtf@ietf.org" style=3D"color: purple; text-decoration: =
underline; ">tcmtf@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color: =
purple; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/tcmtf</a><br></div></blockquote></=
div><br></div></body></html>=

--Apple-Mail=_020967AD-6372-4AD0-ADA5-F034C2B9DA18--

From gorry@erg.abdn.ac.uk  Tue Jul 30 04:18:14 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 9788B11E814F for <tcmtf@ietfa.amsl.com>; Tue, 30 Jul 2013 04:18:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.725
X-Spam-Level: 
X-Spam-Status: No, score=-105.725 tagged_above=-999 required=5 tests=[AWL=-0.524, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 SNCvC7FSwTMt for <tcmtf@ietfa.amsl.com>; Tue, 30 Jul 2013 04:18:09 -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 42F1721F9EC2 for <tcmtf@ietf.org>; Tue, 30 Jul 2013 04:18:09 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 9A7492B44D7; Tue, 30 Jul 2013 12:18:08 +0100 (BST)
Received: from [130.129.23.225] (dhcp-17e1.meeting.ietf.org [130.129.23.225]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPA id 256E72B4096; Tue, 30 Jul 2013 12:18:03 +0100 (BST)
References: <002801ce8d03$6f149040$4d3db0c0$@unizar.es> <21C48DB1-66DA-44E0-9A48-A60B5C1FF691@cisco.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <21C48DB1-66DA-44E0-9A48-A60B5C1FF691@cisco.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-64DDA076-1727-44F0-9242-0396F5BC27E4
Content-Transfer-Encoding: 7bit
Message-Id: <269D7A4D-A172-4326-A225-79C83F149A2B@erg.abdn.ac.uk>
X-Mailer: iPad Mail (10B329)
From: Gorry <gorry@erg.abdn.ac.uk>
Date: Tue, 30 Jul 2013 13:18:04 +0200
To: Dan Wing <dwing@cisco.com>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, Jose Saldana <jsaldana@unizar.es>
Subject: Re: [tcmtf] Deadlines for the different TCM-TF documents - off list
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, 30 Jul 2013 11:18:14 -0000

--Apple-Mail-64DDA076-1727-44F0-9242-0396F5BC27E4
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

I think this seems reasonable. Lets see what people say!

Gorry

On 30 Jul 2013, at 01:06 PM, Dan Wing <dwing@cisco.com> wrote:

> Seems reasonable.
>=20
> -d
>=20
> On Jul 30, 2013, at 11:01 AM, Jose Saldana <jsaldana@unizar.es> wrote:
>=20
>> Hi all,
>> =20
>> Just a question for the BOF. Although in the presentation we are not talk=
ing about the deadlines, we should have something in mind. What about this?
>> =20
>> TCM-TF Reference Model: 9-12 months from the (eventual) creation of a WG
>> =20
>> TCM-TF Negotiation protocol: 18 months
>> =20
>> TCM-TF Recommendations: 12 months
>> =20
>> I would need your feedback.
>> =20
>> Thanks a lot!
>> =20
>> Jose
>> _______________________________________________
>> 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

--Apple-Mail-64DDA076-1727-44F0-9242-0396F5BC27E4
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>I think this seems reasonable. Lets se=
e what people say!</div><div><br></div><div>Gorry</div><div><br>On 30 Jul 20=
13, at 01:06 PM, Dan Wing &lt;<a href=3D"mailto:dwing@cisco.com">dwing@cisco=
.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><meta http-e=
quiv=3D"Content-Type" content=3D"text/html charset=3Dus-ascii">Seems reasona=
ble.<div><br></div><div>-d</div><div><br><div><div>On Jul 30, 2013, at 11:01=
 AM, Jose Saldana &lt;<a href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.=
es</a>&gt; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote t=
ype=3D"cite"><div lang=3D"ES" link=3D"blue" vlink=3D"purple" style=3D"font-f=
amily: Helvetica; font-size: medium; font-style: normal; font-variant: norma=
l; font-weight: normal; letter-spacing: normal; line-height: normal; orphans=
: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white=
-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto=
; -webkit-text-stroke-width: 0px; "><div class=3D"WordSection1" style=3D"pag=
e: WordSection1; "><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; f=
ont-family: Calibri, sans-serif; "><span lang=3D"ES-TRAD">Hi all,<o:p></o:p>=
</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-f=
amily: Calibri, sans-serif; "><span lang=3D"ES-TRAD">&nbsp;</span></div><div=
 style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, s=
ans-serif; "><span lang=3D"EN-US">Just a question for the BOF. Although in t=
he presentation we are not talking about the deadlines, we should have somet=
hing in mind. What about this?<o:p></o:p></span></div><div style=3D"margin: 0=
cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span l=
ang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; fon=
t-size: 11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US">TCM-T=
F Reference Model: 9-12 months from the (eventual) creation of a WG<o:p></o:=
p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font=
-family: Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div=
 style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, s=
ans-serif; "><span lang=3D"EN-US">TCM-TF Negotiation protocol: 18 months<o:p=
></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt;=
 font-family: Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div=
><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; "><span lang=3D"EN-US">TCM-TF Recommendations: 12 months<o:p=
></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt;=
 font-family: Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div=
><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif; "><span lang=3D"EN-US">I would need your feedback.<o:p></o:p=
></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-=
family: Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div s=
tyle=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, san=
s-serif; "><span lang=3D"EN-US">Thanks a lot!<o:p></o:p></span></div><div st=
yle=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans=
-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0=
cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span lang=
=3D"EN-US">Jose<o:p></o:p></span></div></div>_______________________________=
________________<br>tcmtf mailing list<br><a href=3D"mailto:tcmtf@ietf.org" s=
tyle=3D"color: purple; text-decoration: underline; ">tcmtf@ietf.org</a><br><=
a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color: purpl=
e; text-decoration: underline; ">https://www.ietf.org/mailman/listinfo/tcmtf=
</a><br></div></blockquote></div><br></div></div></blockquote><blockquote ty=
pe=3D"cite"><div><span>_______________________________________________</span=
><br><span>tcmtf mailing list</span><br><span><a href=3D"mailto:tcmtf@ietf.o=
rg">tcmtf@ietf.org</a></span><br><span><a href=3D"https://www.ietf.org/mailm=
an/listinfo/tcmtf">https://www.ietf.org/mailman/listinfo/tcmtf</a></span><br=
></div></blockquote></body></html>=

--Apple-Mail-64DDA076-1727-44F0-9242-0396F5BC27E4--

From mns@tid.es  Tue Jul 30 04:49:08 2013
Return-Path: <mns@tid.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 9634821E8085 for <tcmtf@ietfa.amsl.com>; Tue, 30 Jul 2013 04:49:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.698
X-Spam-Level: 
X-Spam-Status: No, score=-3.698 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 m9LQrUiKh8OX for <tcmtf@ietfa.amsl.com>; Tue, 30 Jul 2013 04:49:02 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 13AC621E804B for <tcmtf@ietf.org>; Tue, 30 Jul 2013 04:49:00 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MQQ00L47ZHIF9@tid.hi.inet> for tcmtf@ietf.org; Tue, 30 Jul 2013 13:48:54 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 63.81.02911.628A7F15; Tue, 30 Jul 2013 13:48:54 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MQQ00HX7ZHIXM@tid.hi.inet> for tcmtf@ietf.org; Tue, 30 Jul 2013 13:48:54 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.81]) by EX10-HTCAS7-MAD.hi.inet ([::1]) with mapi id 14.03.0123.003; Tue, 30 Jul 2013 13:48:53 +0200
Date: Tue, 30 Jul 2013 11:48:53 +0000
From: =?iso-8859-1?Q?MANUEL_NU=D1EZ_SANZ?= <mns@tid.es>
In-reply-to: <21C48DB1-66DA-44E0-9A48-A60B5C1FF691@cisco.com>
X-Originating-IP: [10.95.64.115]
To: Dan Wing <dwing@cisco.com>, Jose Saldana <jsaldana@unizar.es>
Message-id: <90ED8822CB577741B9A1668A47539312657079AE@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_X8GUVFSGrm743l8OMn+OAw)"
Content-language: es-ES
Accept-Language: es-ES, en-US
Thread-topic: [tcmtf] Deadlines for the different TCM-TF documents
Thread-index: Ac6NAy7ACvSkcd4ASFSVBKCZdQjznwAANQ+AAAWyRJA=
X-AuditID: 0a5f4e69-b7f118e000000b5f-02-51f7a8260233
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpkkeLIzCtJLcpLzFFi42Lhivcz1FVb8T3QYMkeaYtdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoEr41bbVpaCdZ4VT179ZWtg/ODYxcjJISFgIjF/409GCFtM4sK9 9WxdjFwcQgLbGSU+3vzBApIQEvjJKLG9iQPCnsYosetMBIjNIqAqcf5ZD2sXIwcHm4C5RN86 HpCwsICjxIV3V5lAbE4BW4nW249ZIeYrSPw59xhspAhQzcuOwywgrcxAY+Z9UwQJ8wp4S8y/ PZURwhaU+DH5HlRJrsSOR94gYWYBcYk5vyaCTWQUkJVYef40I8REJ4n+hl1Q060k9k3pZoHY KiCxZM95ZghbVOLl43+sEI9kSXQtnM84gVFsFpJtsxC2zUKyDcLWk7gxdQobhK0tsWzha2YI W1dixr9DLMjiCxjZVzGKFScVZaZnlOQmZuakGxjpZWTqZeallmxihERb5g7G5TtVDjEKcDAq 8fBuKPgWKMSaWFZcmXuIUYKDWUmE9/zE74FCvCmJlVWpRfnxRaU5qcWHGJk4OKUaGPnX+Mqq B7RKm25tOetQF95lIHSo4k28iWJ4eN7jG6pip2/8FeifliTaeE/49hqh6N6bm78+TXvI7tb8 0Nth6ez+CzEZpa9f2WzZGePZrMrsJfpR+rzlujYmvm1Oq04K7F9n8TrkRayu8v6TJsarFIuK G8UPWnCKsrdw3uV+KKIfydfQGLlIiaU4I9FQi7moOBEAHIckCpQCAAA=
References: <002801ce8d03$6f149040$4d3db0c0$@unizar.es> <21C48DB1-66DA-44E0-9A48-A60B5C1FF691@cisco.com>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Deadlines for the different TCM-TF documents
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, 30 Jul 2013 11:49:08 -0000

--Boundary_(ID_X8GUVFSGrm743l8OMn+OAw)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable

+1.


De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de Dan=
 Wing
Enviado el: martes, 30 de julio de 2013 13:06
Para: Jose Saldana
CC: tcmtf@ietf.org
Asunto: Re: [tcmtf] Deadlines for the different TCM-TF documents

Seems reasonable.

-d

On Jul 30, 2013, at 11:01 AM, Jose Saldana <jsaldana@unizar.es<mailto:jsald=
ana@unizar.es>> wrote:


Hi all,

Just a question for the BOF. Although in the presentation we are not talkin=
g about the deadlines, we should have something in mind. What about this?

TCM-TF Reference Model: 9-12 months from the (eventual) creation of a WG

TCM-TF Negotiation protocol: 18 months

TCM-TF Recommendations: 12 months

I would need your feedback.

Thanks a lot!

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


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

--Boundary_(ID_X8GUVFSGrm743l8OMn+OAw)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style>
<!--
@font-face
	{font-family:Helvetica}
@font-face
	{font-family:Helvetica}
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
span.EstiloCorreo17
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:70.85pt 3.0cm 70.85pt 3.0cm}
div.WordSection1
	{}
-->
</style>
</head>
<body lang=3D"ES" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&#43;1.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"font-size=
:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F4=
97D">&nbsp;</span></a></p>
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0c=
m 0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt; font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">De:</span></b><span style=3D"font-si=
ze:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tcmtf-bo=
unces@ietf.org [mailto:tcmtf-bounces@ietf.org]
<b>En nombre de </b>Dan Wing<br>
<b>Enviado el:</b> martes, 30 de julio de 2013 13:06<br>
<b>Para:</b> Jose Saldana<br>
<b>CC:</b> tcmtf@ietf.org<br>
<b>Asunto:</b> Re: [tcmtf] Deadlines for the different TCM-TF documents</sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Seems reasonable.</p>
<div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
<div>
<p class=3D"MsoNormal">-d</p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;</p>
<div>
<div>
<p class=3D"MsoNormal">On Jul 30, 2013, at 11:01 AM, Jose Saldana &lt;<a hr=
ef=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt; wrote:</p>
</div>
<p class=3D"MsoNormal"><br>
<br>
</p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"ES-TRAD" style=3D"font-size:11.0pt; fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Hi all,</span><span s=
tyle=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&=
quot;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"ES-TRAD" style=3D"font-size:11.0pt; fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><span st=
yle=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&q=
uot;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Just a question for the=
 BOF. Although in the presentation we are not talking about the deadlines, =
we should have something in mind. What about this?</span><span style=3D"fon=
t-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><span styl=
e=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">TCM-TF Reference Model:=
 9-12 months from the (eventual) creation of a WG</span><span style=3D"font=
-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><span styl=
e=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">TCM-TF Negotiation prot=
ocol: 18 months</span><span style=3D"font-size:11.0pt; font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><span styl=
e=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">TCM-TF Recommendations:=
 12 months</span><span style=3D"font-size:11.0pt; font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><span styl=
e=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">I would need your feedb=
ack.</span><span style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><span styl=
e=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Thanks a lot!</span><sp=
an style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><span styl=
e=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Jose</span><span style=
=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;"></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt; font-family:&quot;H=
elvetica&quot;,&quot;sans-serif&quot;">____________________________________=
___________<br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org"><span style=3D"color:purple">tcmtf@ietf.o=
rg</span></a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf"><span style=3D"colo=
r:purple">https://www.ietf.org/mailman/listinfo/tcmtf</span></a></span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_X8GUVFSGrm743l8OMn+OAw)--
