
From ietf-secretariat@ietf.org  Tue Jul 10 13:33:19 2012
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9087721F85B4; Tue, 10 Jul 2012 13:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LqpUrWCcjTtV; Tue, 10 Jul 2012 13:33:19 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CD2B21F85A8; Tue, 10 Jul 2012 13:33:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.30p3
Message-ID: <20120710203319.20789.4699.idtracker@ietfa.amsl.com>
Date: Tue, 10 Jul 2012 13:33:19 -0700
Cc: tcmtf@ietf.org, jsaldana@unizar.es
Subject: [tcmtf] New Non-WG Mailing List: tcmtf -- Tunneling Compressed Multiplexed	Traffic Flows (TCMTF) discussion 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, 10 Jul 2012 20:33:19 -0000

A new IETF non-working group email list has been created.

List address: tcmtf@ietf.org
Archive: http://www.ietf.org/mail-archive/web/tcmtf/
To subscribe: https://www.ietf.org/mailman/listinfo/tcmtf

Purpose: This list is for discussing TCMTF, and the potential for a working=
 group to focus on the topic. This includes determining the level of intere=
st,
seeing if there is demand, figuring out what should be standardized or
not, organizing potential bar-BoF or BoF meetings, and continuing to
discuss research and test results and architecture/design topics.

For additional information, please contact the list administrator.

From jsaldana@unizar.es  Wed Jul 11 07:38:03 2012
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 DD82721F85C9 for <tcmtf@ietfa.amsl.com>; Wed, 11 Jul 2012 07:38:03 -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 VOCE8cvnPYjL for <tcmtf@ietfa.amsl.com>; Wed, 11 Jul 2012 07:38:02 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 394F121F86A3 for <tcmtf@ietf.org>; Wed, 11 Jul 2012 07:37:50 -0700 (PDT)
Received: from jsaldanapc (n33d97.cs.unibo.it [130.136.33.97]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id q6BEcFWV007436 for <tcmtf@ietf.org>; Wed, 11 Jul 2012 16:38:15 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
References: <004501ccecc2$457fb670$d07f2350$@unizar.es>
In-Reply-To: <004501ccecc2$457fb670$d07f2350$@unizar.es>
Date: Wed, 11 Jul 2012 16:38:16 +0200
Message-ID: <004d01cd5f72$ceff7110$6cfe5330$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_004E_01CD5F83.929894C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQICuFp4c5wICkr62WXkiIWDkH4xMpa5cPfQ
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] Proposal for tunneling, compressing and multiplexing flows
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, 11 Jul 2012 14:38:04 -0000

This is a multipart message in MIME format.

------=_NextPart_000_004E_01CD5F83.929894C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

In order to get an idea of the main aim of the draft, I re-send this =
message
explaining the idea of the draft. I have slightly modified some parts.

=20

Best regards,

=20

Jose

=20

=20

Abstract: This document describes a method to improve the bandwidth
utilization  of network paths that carry multiple streams in parallel
between two endpoints, as in voice trunking.  The method combines =
standard
protocols that provide compression, multiplexing, and tunneling over  a
network path for the purpose of reducing the bandwidth used when =
multiple
streams are carried over that path.

=20

The main idea is to update TCRTP. This is a "Best current practice" RFC =
(
<http://datatracker.ietf.org/doc/rfc4170/>
http://datatracker.ietf.org/doc/rfc4170 ) which was developed in =
Audio/Video
Transport working group in 2005-11. It "describes a method to improve =
the
bandwidth utilization of RTP streams over network paths that carry =
multiple
Real-time Transport Protocol (RTP) streams in parallel between two
endpoints, as in voice trunking. The method combines standard protocols =
that
provide compression, multiplexing, and tunneling over a network path for =
the
purpose of reducing the bandwidth used when multiple RTP streams are =
carried
over that path." (from the introduction of RFC4170).

=20

The scheme of TCRTP is:

=20

RTP/UDP

   |

   |         ----------------------------

   |             =20

 ECRTP             compressing layer

   |                  =20

   |         ----------------------------

   |

PPPMUX            multiplexing layer

   |

   |         ----------------------------

   |

L2TP              tunneling layer

   |

   |         ----------------------------

   |

  IP

=20

However, there exist many real-time flows that do not use RTP:

=20

- Online "First Person Shooter" (FPS) games use UDP datagrams, and they =
are
one of the most "real-time" applications nowadays. Some examples: =
Counter
Strike, Halo, Quake, etc.[1].

=20

- Online "Massively Multiplayer Online Role Playing Games" (MMORPG): =
They
use TCP, but can be considered "real-time", since the actions of the =
players
have to be transmitted very quickly to the server. It should be taken =
into
account that player vs player fights are one of the possible activities =
of
the game. Some examples: World of Warcraft (more than 10 million
subscribers) [2].

=20

- TCP is also getting used for media delivery. For many reasons, such as
avoiding firewalls, the standard IP/ UDP/ RTP protocol stack is =
substituted
in many cases by IP/ TCP/ HTTP/ FLV [3].

=20

- Another interesting scenario is satellite communication links.
Multiplexing small packets into one packet for transmission would =
improve
the efficiency. Satellite links would also find it useful to multiplex =
small
TCP packets into one packet - this could be especially interesting for
compressing TCP ACKs.

=20

In our recent research activities, we have adapted TCRTP scheme for its =
use
when the traffic is not RTP. The idea is to substitute ECRTP by other
compression scheme which can be used for UDP or TCP headers. In 2006, =
the
IETF formed the Robust Header Compression (ROHC) working group which =
created
specifications for header compression over links for RTP, UDP and TCP.
These specifications were extended to compress headers over other =
networks.
For most RTP flows, ROHC is more bandwidth efficient than ECRTP, at the =
cost
of implementation complexity. It has a special care of context
synchronization, defining some states at the compressor and =
decompressor.
Once the effort for designing ROHC has been conducted, it is worth =
including
it in the compressing and multiplexing RFC.

=20

In a recent paper in Nov. issue of IEEE Communications Magazine, it was
shown that 30% of bandwidth saving can be achieved for 8 FPS different =
games
using IPv4. If IPv6 is used, savings can be up to 54% [4]. Another =
recent
study, has estimated 60% bandwidth saving for World of Warcraft
(http://diec.unizar.es/~jsaldana/personal/sergei_SPECTS_2012_in_proc.pdf)=

using IPv4.

=20

The scheme of the proposal is this one:

=20

       TCP    UDP  RTP/UDP

        |      |      |

         \     |     /                    ------------------------------

           \   |   /

Nothing or ROHC or ECRTP or IPHC             header compressing layer

               |

               |                          ------------------------------

               |

   PPPMUX or other mux protocols                multiplexing layer

               |

              / \                         ------------------------------

             /   \

            /     \

   GRE or L2TP     \                              tunneling layer

          |        MPLS

          |                               ------------------------------

          IP

=20

It should be more "open" than TCRTP. I the use of different protocols =
could
be "orthogonal": different header compression algorithms could be used,
depending on the application and the scenario; also different =
multiplexing
and tunneling protocols could be included.

=20

Regarding the scenarios, we have considered some of them:

=20

- A provider of a real-time service (e.g. game or voip) can have an
infrastructure with a number of proxies that can group traffic from
different users and send it to the server.

=20

- An Internet caf=E9, where a number (sometimes big) of players share =
the same
access link. Bandwidth is scarce in that scenario.

=20

- A satellite link, where the bandwidth and the pps have to be saved.

=20

- Desktop or application sharing where the traffic from the server to =
the
client typically consists of the delta of screen updates.  Also, the
standard for remote desktop sharing emerging for WebRTC in the RTCWEB
Working  Group is: {something}/SCTP/UDP (Stream Control Transmission
Protocol [SCTP]).  In this scenario, SCTP/UDP could be used in other =
cases:
chatting, file sharing and applications related to WebRTC peers. There =
could
be hundreds of clients at a site talking to a server located at a =
datacenter
over a WAN.

=20

Thank you very much,

=20

Jose Saldana

=20

PS: We have also written a paper, which was presented in ICC conference, =
in
Ottawa in June. You can read it here:
http://diec.unizar.es/~jsaldana/personal/ottawa_ICC_2012_in_proc.pdf

=20

______________

=20

[1] Ratti, S.; Hariri, B.; Shirmohammadi, S., "A Survey of First-Person
Shooter Gaming Traffic on the Internet," Internet Computing, IEEE , =
vol.14,
no.5, pp.60-69, Sept.-Oct. 2010. URL:
<http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&arnumber=3D5445069&isnu=
mber=3D55
62482>
http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&arnumber=3D5445069&isnum=
ber=3D556
2482

=20

[2] P. Svoboda, W Karner and M. Rupp, "Traffic Analysis and Modeling for
World of Warcraft," ICC '07. IEEE International Conference on
Communications, pp.1612-1617, 24-28, Jun. 2007. URL:
<http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&arnumber=3D4288941&isnu=
mber=3D42
88671>
http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&arnumber=3D4288941&isnum=
ber=3D428
8671

=20

[3] G. Marfia and M. Roccetti, "TCP At Last: Reconsidering TCP's Role =
for
Wireless Entertainment Centers at Home," IEEE Transactions on Consumer
Electronics, Vol. 56, N. 4, Nov. 2010, pp. 2233-2240. URL:
<http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&arnumber=3D5681095&isnu=
mber=3D56
81060>
http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&arnumber=3D5681095&isnum=
ber=3D568
1060

=20

[4] J. Saldana, J. Fern=E1ndez-Navajas, J. Ruiz-Mas, J. I. Aznar, E. =
Viruete
and  L. Casadesus, "First Person Shooters: Can a Smarter Network Save
Bandwidth without Annoying the Players?," IEEE Communications Magazine,
Consumer Communications and Networking Series, vol. 49, no.

11, pp. 190-198, Nov. 2011. URL:
<http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&arnumber=3D6069728&isnu=
mber=3D60
69696>
http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&arnumber=3D6069728&isnum=
ber=3D606
9696

=20

=20


------=_NextPart_000_004E_01CD5F83.929894C0
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;}
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;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:"Calibri","sans-serif";}
span.EstiloCorreo19
	{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'font-family:"Courier New";color:black'>In order to =
get an idea of the main aim of the draft, I re-send this message =
explaining the idea of the draft. I have slightly modified some =
parts.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-family:"Courier New";color:black'>Best =
regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>Jose<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><b><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>Abstract</span></b><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>: This document =
describes a method to improve the bandwidth utilization&nbsp; of network =
paths that carry multiple streams in parallel between two endpoints, as =
in voice trunking.&nbsp; The method combines standard&nbsp; protocols =
that provide compression, multiplexing, and tunneling over&nbsp; a =
network path for the purpose of reducing the bandwidth used when =
multiple streams are carried over that path.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>The main idea is to update TCRTP. This is a &quot;Best =
current practice&quot; RFC (</span><span style=3D'font-family:"Courier =
New";color:black'><a =
href=3D"http://datatracker.ietf.org/doc/rfc4170/"><span lang=3DEN-US =
style=3D'color:black;text-decoration:none'>http://datatracker.ietf.org/do=
c/rfc4170</span></a> </span><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>) which was developed in =
Audio/Video Transport working group in 2005-11. </span><span =
style=3D'font-family:"Courier New";color:black'>It &quot;describes a =
method to improve the bandwidth utilization of RTP streams over network =
paths that carry multiple Real-time Transport Protocol (RTP) streams in =
parallel between two endpoints, as in voice trunking. </span><span =
lang=3DEN-US style=3D'font-family:"Courier New";color:black'>The method =
combines standard protocols that provide compression, multiplexing, and =
tunneling over a network path for the purpose of reducing the bandwidth =
used when multiple RTP streams are carried over that path.&quot; =
</span><span style=3D'font-family:"Courier New";color:black'>(from the =
introduction of RFC4170).<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>The scheme of TCRTP is:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>RTP/UDP<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0=A0 |<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0 =
----------------------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'>=A0ECRTP=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
compressing layer<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier New";color:black'>=A0=A0 =
|=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0|=A0=A0=A0=A0=A0=A0=A0=A0 =
----------------------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0=A0 |<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'> PPPMUX=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 multiplexing =
layer<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>=A0=A0 =
|<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>=A0=A0 =
|=A0=A0=A0=A0=A0=A0=A0=A0 =
----------------------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0=A0 |<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'> L2TP=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 tunneling =
layer<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>=A0=A0 =
|<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>=A0=A0 =
|=A0=A0=A0=A0=A0=A0=A0=A0 =
----------------------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0=A0 |<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0 IP<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>However, there exist many real-time flows that do not =
use RTP:<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'>- Online &quot;First Person Shooter&quot; (FPS) games =
use UDP datagrams, and they are one of the most &quot;real-time&quot; =
applications nowadays. </span><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>Some examples: Counter =
Strike, Halo, Quake, etc.[1].<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>- Online &quot;Massively Multiplayer Online Role =
Playing Games&quot; (MMORPG): They use TCP, but can be considered =
&quot;real-time&quot;, since the actions of the players have to be =
transmitted very quickly to the server. </span><span =
style=3D'font-family:"Courier New";color:black'>It should be taken into =
account that player vs player fights are one of the possible activities =
of the game. Some examples: World of Warcraft (more than 10 million =
subscribers) [2].<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'>- TCP is also getting used for media delivery. For =
many reasons, such as avoiding firewalls, the standard IP/ UDP/ RTP =
protocol stack is substituted in many cases by IP/ TCP/ HTTP/ FLV =
[3].<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>- Another interesting scenario is satellite =
communication links. Multiplexing small packets into one packet for =
transmission would improve the efficiency. </span><span =
style=3D'font-family:"Courier New";color:black'>Satellite links would =
also find it useful to multiplex small TCP packets into one packet - =
this could be especially interesting for compressing TCP =
ACKs.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>In our recent research activities, we have adapted =
TCRTP scheme for its use when the traffic is not RTP. </span><span =
style=3D'font-family:"Courier New";color:black'>The idea is to =
substitute ECRTP by other compression scheme which can be used for UDP =
or TCP headers. In 2006, the IETF formed the Robust Header Compression =
(ROHC) working group which created specifications for header compression =
over links for RTP, UDP and TCP.&nbsp; These specifications were =
extended to compress headers over other networks. For most RTP flows, =
ROHC is more bandwidth efficient than ECRTP, at the cost of =
implementation complexity. It has a special care of context =
synchronization, defining some states at the compressor and =
decompressor. </span><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>Once the effort for designing ROHC has been conducted, =
it is worth including it in the compressing and multiplexing =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>In a recent paper in Nov. issue of IEEE Communications =
Magazine, it was shown that 30% of bandwidth saving can be achieved for =
8 FPS different games using IPv4. </span><span =
style=3D'font-family:"Courier New";color:black'>If IPv6 is used, savings =
can be up to 54% [4]. </span><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>Another recent study, =
has estimated 60% bandwidth saving for World of Warcraft =
(http://diec.unizar.es/~jsaldana/personal/sergei_SPECTS_2012_in_proc.pdf)=
 using IPv4.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>The scheme of the proposal is this =
one:<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0 TCP=A0=A0=A0 UDP=A0 =
RTP/UDP<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>=A0=A0=A0=A0=A0=A0=A0 =
|=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0 |<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0=A0=A0 \=A0=A0=A0=A0 |=A0=A0=A0=A0 =
/=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
------------------------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 \=A0=A0 |=A0=A0 =
/<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>Nothing or ROHC or ECRTP =
or IPHC=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 header compressing =
layer<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
|<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
|=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 ------------------------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
|<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>=A0=A0 PPPMUX or other =
mux protocols=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 multiplexing =
layer<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
|<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 / =
\=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
 ------------------------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /=A0=A0 =
\<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /=A0=A0=A0=A0 =
\<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>=A0=A0 GRE or =
L2TP=A0=A0=A0=A0 =
\=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 tunneling layer<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0=A0 =
MPLS<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
|=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0------------------------------<=
o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'>=A0=A0=A0=A0=A0=A0=A0=A0=A0 IP<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>It should be more &quot;open&quot; than TCRTP. I the =
use of different protocols could be &quot;orthogonal&quot;: different =
header compression algorithms could be used, depending on the =
application and the scenario; also different multiplexing and tunneling =
protocols could be included.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>Regarding the scenarios, we have considered some of =
them:<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'>- A provider of a real-time service (e.g. game or =
voip) can have an infrastructure with a number of proxies that can group =
traffic from different users and send it to the =
server.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>- An Internet caf=E9, where a number (sometimes big) =
of players share the same access link. </span><span =
style=3D'font-family:"Courier New";color:black'>Bandwidth is scarce in =
that scenario.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'>- A satellite link, where the bandwidth and the pps =
have to be saved.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>- Desktop or application sharing where the traffic =
from the server to the client typically consists of the delta of screen =
updates.&nbsp; Also, the standard for remote desktop sharing emerging =
for WebRTC in the RTCWEB Working&nbsp; Group is: {something}/SCTP/UDP =
(Stream Control Transmission Protocol [SCTP]).&nbsp; In this scenario, =
SCTP/UDP could be used in other cases:&nbsp; chatting, file sharing and =
applications related to WebRTC peers. There could be hundreds of clients =
at a site talking to a server located at a datacenter over a =
WAN.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>Thank you very much,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'>Jose Saldana<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>PS: We have also written a paper, which was presented =
in ICC conference, in Ottawa in June. You can read it here: =
http://diec.unizar.es/~jsaldana/personal/ottawa_ICC_2012_in_proc.pdf<o:p>=
</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'>______________<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'>[1] Ratti, S.; Hariri, B.; Shirmohammadi, S., &quot;A =
Survey of First-Person Shooter Gaming Traffic on the Internet,&quot; =
Internet Computing, IEEE , vol.14, no.5, pp.60-69, Sept.-Oct. 2010. =
</span><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>URL: </span><span style=3D'font-family:"Courier =
New";color:black'><a =
href=3D"http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&amp;arnumber=3D5=
445069&amp;isnumber=3D5562482"><span lang=3DEN-US =
style=3D'color:black;text-decoration:none'>http://ieeexplore.ieee.org/sta=
mp/stamp.jsp?tp=3D&amp;arnumber=3D5445069&amp;isnumber=3D5562482</span></=
a></span><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>[2] P. Svoboda, W Karner and M. Rupp, &quot;Traffic =
Analysis and Modeling for World of Warcraft,&quot; ICC '07. </span><span =
style=3D'font-family:"Courier New";color:black'>IEEE International =
Conference on Communications, pp.1612-1617, 24-28, Jun. 2007. =
</span><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>URL: </span><span style=3D'font-family:"Courier =
New";color:black'><a =
href=3D"http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&amp;arnumber=3D4=
288941&amp;isnumber=3D4288671"><span lang=3DEN-US =
style=3D'color:black;text-decoration:none'>http://ieeexplore.ieee.org/sta=
mp/stamp.jsp?tp=3D&amp;arnumber=3D4288941&amp;isnumber=3D4288671</span></=
a></span><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>[3] G. Marfia and M. Roccetti, &quot;TCP At Last: =
Reconsidering TCP's Role for Wireless Entertainment Centers at =
Home,&quot; IEEE Transactions on Consumer Electronics, Vol. 56, N. 4, =
Nov. 2010, pp. 2233-2240. URL: </span><span =
style=3D'font-family:"Courier New";color:black'><a =
href=3D"http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&amp;arnumber=3D5=
681095&amp;isnumber=3D5681060"><span lang=3DEN-US =
style=3D'color:black;text-decoration:none'>http://ieeexplore.ieee.org/sta=
mp/stamp.jsp?tp=3D&amp;arnumber=3D5681095&amp;isnumber=3D5681060</span></=
a></span><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>[4] J. Saldana, J. Fern=E1ndez-Navajas, J. Ruiz-Mas, =
J. I. Aznar, E. Viruete and&nbsp; L. Casadesus, &quot;First Person =
Shooters: Can a Smarter Network Save Bandwidth without Annoying the =
Players?,&quot; IEEE Communications Magazine, Consumer Communications =
and Networking Series, vol. 49, no.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'>11, pp. 190-198, Nov. 2011. </span><span lang=3DEN-US =
style=3D'font-family:"Courier New";color:black'>URL: </span><span =
style=3D'font-family:"Courier New";color:black'><a =
href=3D"http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&amp;arnumber=3D6=
069728&amp;isnumber=3D6069696"><span lang=3DEN-US =
style=3D'color:black;text-decoration:none'>http://ieeexplore.ieee.org/sta=
mp/stamp.jsp?tp=3D&amp;arnumber=3D6069728&amp;isnumber=3D6069696</span></=
a></span><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><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><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_004E_01CD5F83.929894C0--


From jsaldana@unizar.es  Wed Jul 11 07:42:07 2012
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 37C9921F86D0 for <tcmtf@ietfa.amsl.com>; Wed, 11 Jul 2012 07:42:07 -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 OkwOG-nMuFKa for <tcmtf@ietfa.amsl.com>; Wed, 11 Jul 2012 07:42:06 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 3FBFC21F86F3 for <tcmtf@ietf.org>; Wed, 11 Jul 2012 07:42:04 -0700 (PDT)
Received: from jsaldanapc (n33d97.cs.unibo.it [130.136.33.97]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id q6BEgTsb009686 for <tcmtf@ietf.org>; Wed, 11 Jul 2012 16:42:30 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 11 Jul 2012 16:42:30 +0200
Message-ID: <005801cd5f73$669f8320$33de8960$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0059_01CD5F84.2A28C850"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1fcx5B+SREC8/BSc2L96H9eIXnVg==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] The presentation of the draft
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, 11 Jul 2012 14:42:07 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0059_01CD5F84.2A28C850
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The draft can be found here:

 

http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

 

 

And here is the presentation of the draft, which was done in the tsvwg in
IETF83, Paris, March 27th 2012:

 

http://diec.unizar.es/~jsaldana/personal/present-saldana-tsvwg-tcmtf_v2.pdf

 

 

Jose

 


------=_NextPart_000_0059_01CD5F84.2A28C850
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><span =
lang=3DEN-US>The draft can be found here:<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 =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http:=
//datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></spa=
n></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>And here is the presentation of the draft, which was done =
in the tsvwg in IETF83, Paris, March 27<sup>th</sup> =
2012:<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 =
href=3D"http://diec.unizar.es/~jsaldana/personal/present-saldana-tsvwg-tc=
mtf_v2.pdf">http://diec.unizar.es/~jsaldana/personal/present-saldana-tsvw=
g-tcmtf_v2.pdf</a><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 =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage: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_0059_01CD5F84.2A28C850--


From jsaldana@unizar.es  Wed Jul 11 07:45:22 2012
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 7A91921F8532 for <tcmtf@ietfa.amsl.com>; Wed, 11 Jul 2012 07:45:22 -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 Zr7MXuDQR-t3 for <tcmtf@ietfa.amsl.com>; Wed, 11 Jul 2012 07:45:21 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id C3A2D21F8608 for <tcmtf@ietf.org>; Wed, 11 Jul 2012 07:45:20 -0700 (PDT)
Received: from jsaldanapc (n33d97.cs.unibo.it [130.136.33.97]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id q6BEjkIO009552 for <tcmtf@ietf.org>; Wed, 11 Jul 2012 16:45:46 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 11 Jul 2012 16:45:46 +0200
Message-ID: <006301cd5f73$dba6ec80$92f4c580$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0064_01CD5F84.9F30F500"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1fc5g8iivOItdFQrW4wUq6+EwNEg==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] Asking for feedback about including MPLS in draft-saldana-tsvwg-tcmtf
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, 11 Jul 2012 14:45:22 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0064_01CD5F84.9F30F500
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear all,

=20

This is the last idea about improving the draft: the inclusion of MPLS =
as a
possibility for the tunneling part, in addition to L2TP/IP. We have =
thought
to add this subsection to the draft:

=20

----------------

2.4.2 MPLS tunneling

=20

In some scenarios, mainly in operator=B4s core networks, the use of MPLS =
is
widely deployed as data transport method. The adoption of MPLS as =
tunneling
layer in that proposal intends to natively adapt TCMTF to those =
transport
networks.

=20

In the same way that layer 3 tunnels, MPLS paths, identified by MPLS =
labels,
established between Label Edge Routers (LSRs) could be used to transport =
the
compressed payloads within an MPLS network. This way, multiplexing layer
must be placed over MPLS layer. Note that, in this case, layer 3 tunnel
headers should not be used, with the consequent data efficiency =
improvement.

---------------

=20

So the new scheme could be this one:

=20

       TCP    UDP  RTP/UDP

        |      |      |

         \     |     /                    ------------------------------

           \   |   /

Nothing or ROHC or ECRTP or IPHC             header compressing layer

               |

               |                          ------------------------------

               |

   PPPMUX or other mux protocols                multiplexing layer

               |

              / \                         ------------------------------

             /   \

            /     \

   GRE or L2TP     \                              tunneling layer

          |        MPLS

          |                               ------------------------------

          IP

=20

We don=92t think any modification in MPLS would be necessary.

=20

Thank you very much,

=20

Jose Saldana

=20


------=_NextPart_000_0064_01CD5F84.9F30F500
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;}
/* 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.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;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:"Calibri","sans-serif";}
span.EstiloCorreo19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo20
	{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 =
style=3D'font-family:"Courier New";color:black'>Dear =
all,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-family:"Courier New";color:black'>This is the =
last idea about improving the draft: the inclusion of MPLS as a =
possibility for the tunneling part, in addition to L2TP/IP. We have =
thought to add this subsection to the draft:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>----------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>2.4.2 MPLS tunneling<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>In some scenarios, mainly in operator=B4s core =
networks, the use of MPLS is widely deployed as data transport method. =
The adoption of MPLS as tunneling layer in that proposal intends to =
natively adapt TCMTF to those transport =
networks.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>In the same way that layer 3 tunnels, MPLS paths, =
identified by MPLS labels, established between Label Edge Routers (LSRs) =
could be used to transport the compressed payloads within an MPLS =
network. This way, multiplexing layer must be placed over MPLS layer. =
Note that, in this case, layer 3 tunnel headers should not be used, with =
the consequent data efficiency improvement.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>---------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>So the new scheme could be this =
one:<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
TCP&nbsp;&nbsp;&nbsp; UDP&nbsp; RTP/UDP<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
\&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; =
/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
------------------------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; \&nbsp;&nbsp; |&nbsp;&nbsp; /<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>Nothing or ROHC or ECRTP or =
IPHC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; header compressing layer<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|<o:p></o:p><=
/span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; ------------------------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp; PPPMUX or other mux =
protocols&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; multiplexing layer<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; / =
\&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
------------------------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; /&nbsp;&nbsp; \<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; /&nbsp;&nbsp;&nbsp;&nbsp; \<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp; GRE or L2TP&nbsp;&nbsp;&nbsp;&nbsp; =
\&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tunneling layer<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
------------------------------<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
IP<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'>We don&#8217;t think any modification in MPLS would be =
necessary.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-family:"Courier New";color:black'>Thank you =
very much,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black;mso-fareast-language:ES'>Jose =
Saldana<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_0064_01CD5F84.9F30F500--


From jsaldana@unizar.es  Fri Jul 13 02:07:55 2012
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 80F6D21F87AB for <tcmtf@ietfa.amsl.com>; Fri, 13 Jul 2012 02:07:55 -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 64dqxO1ctikC for <tcmtf@ietfa.amsl.com>; Fri, 13 Jul 2012 02:07:54 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id E084021F87AA for <tcmtf@ietf.org>; Fri, 13 Jul 2012 02:07:53 -0700 (PDT)
Received: from jsaldanapc (n33d97.cs.unibo.it [130.136.33.97]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id q6D98PCO012303 for <tcmtf@ietf.org>; Fri, 13 Jul 2012 11:08:25 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
References: <20120713090322.11524.92407.idtracker@ietfa.amsl.com>
In-Reply-To: <20120713090322.11524.92407.idtracker@ietfa.amsl.com>
Date: Fri, 13 Jul 2012 11:08:26 +0200
Message-ID: <004101cd60d7$10106f00$30314d00$@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: AQKMZSr66TAyvfcRpTuj+7SRiQVEbJWo4rnQ
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] RV: New Version Notification for draft-saldana-tsvwg-tcmtf-03.txt
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, 13 Jul 2012 09:07:55 -0000

Hello all,

I have just posted a new version of the draft (03). It includes some =
improvements, and also the possibility of using MPLS instead of other =
tunneling schemes (L2TPv3 or GRE).

https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

Best regards,

Jose

-----Mensaje original-----
De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
Enviado el: viernes, 13 de julio de 2012 11:03
Para: jsaldana@unizar.es
CC: mperumal@cisco.com; navajas@unizar.es; dwing@cisco.com; fpb@tid.es
Asunto: New Version Notification for draft-saldana-tsvwg-tcmtf-03.txt


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

Filename:	 draft-saldana-tsvwg-tcmtf
Revision:	 03
Title:		 Tunneling Compressed Multiplexed Traffic Flows (TCMTF)
Creation date:	 2012-07-13
WG ID:		 Individual Submission
Number of pages: 18
URL:             =
http://www.ietf.org/internet-drafts/draft-saldana-tsvwg-tcmtf-03.txt
Status:          =
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf
Htmlized:        http://tools.ietf.org/html/draft-saldana-tsvwg-tcmtf-03
Diff:            =
http://tools.ietf.org/rfcdiff?url2=3Ddraft-saldana-tsvwg-tcmtf-03

Abstract:
   This document describes a method to improve the bandwidth utilization
   of network paths that carry multiple streams in parallel between two
   endpoints, as in voice trunking.  The method combines standard
   protocols that provide compression, multiplexing, and tunneling over
   a network path for the purpose of reducing the bandwidth used when
   multiple streams are carried over that path.

                                                                         =
        =20


The IETF Secretariat


From fpb@tid.es  Fri Jul 13 02:22:23 2012
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 754A721F852E; Fri, 13 Jul 2012 02:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.654
X-Spam-Level: 
X-Spam-Status: No, score=-4.654 tagged_above=-999 required=5 tests=[AWL=-1.944, BAYES_05=-1.11, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, J_CHICKENPOX_34=0.6, J_CHICKENPOX_64=0.6, J_CHICKENPOX_71=0.6, 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 MEndR2ctAid5; Fri, 13 Jul 2012 02:22:22 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id E29C721F852C; Fri, 13 Jul 2012 02:22:20 -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 <0M730045GE25OK@tid.hi.inet>; Fri, 13 Jul 2012 11:22:55 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id D2.95.02752.FE8EFFF4; Fri, 13 Jul 2012 11:22:55 +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 <0M730045LE26OK@tid.hi.inet>; Fri, 13 Jul 2012 11:22:55 +0200 (MEST)
Received: from EX10-MB1-MAD.hi.inet ([fe80::a473:4f3e:f8db:1855]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0298.004; Fri, 13 Jul 2012 11:22:54 +0200
Date: Fri, 13 Jul 2012 09:22:54 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
X-Originating-IP: [10.95.64.115]
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A211401AA2@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_CtANLI/hoHHxF4pTPP9QBA)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: M2M, WSNs and draft-saldana-tsvwg-tcmtf
Thread-index: Ac1g2RR6RDhC6yzGQMG7kvzNfOCRRg==
X-AuditID: 0a5f4e69-b7f6d6d000000ac0-d4-4fffe8ef23b6
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOKsWRmVeSWpSXmKPExsXCFe9nqPv+xX9/g7d9Aha7Pm9gtDj25i6b A5PHkiU/mQIYo7hsUlJzMstSi/TtErgyvm7fzl7wwaGiY+1b5gbG1VZdjJwcEgImEv/v/2aF sMUkLtxbz9bFyMUhJLCdUeLpvANMEM4zRonW9XtYIZyljBK/J+1nAWlhEVCV2HHlJDOIzSag JXH67iqwuLCAgcS8tb2MEGMVJP6cewwWFxHwkJjTcwMozsHBK+AtcfcUWAmvgKDEj8n3wEqY BdIl9i1exAxhi0s0t94EizMKyEq8mz+fFWKMqUT/hkVQI/Uk3r6ZwAaxSkTi4cXTULaoxMvH /1gnMArPQrJiFpIVs5CsgLDzJa6cPcsGYetILNj9CcrWlli28DUzjH3mwGMmTHE7iVsbF7JD 2AYSh3/+BJrJBWTvYJS4N/kWK0RCUWJK90P2BYw8qxjFipOKMtMzSnITM3PSDYz0MjL1MvNS SzYxQmI2cwfj8p0qhxgFOBiVeHglpn3yF2JNLCuuzD3EKMnBpCTKO//pf38hvqT8lMqMxOKM +KLSnNTiQ4wSHMxKIrwK04ByvCmJlVWpRfkwKRkODiUJXgZgehESLEpNT61Iy8wBJiaYNBMH J0g7D1D7y+cg7cUFibnFmekQ+VOMqhydW+7dYhRiycvPS5US5+UFGSQAUpRRmgc35xWjONDB wrwfQEbwAFMr3IRXQMOZgIbP+vkPZHhJIkJKCpgcSxV/tih2ZS2cUtC94N7knd9Vu5TMZCwb daNn/olbvjJvtRUfxwzm8BcrtPvO9retWpWfZvqdXXXa0b43/25+WDv5wkrOm5uSIp1US5/v /fY79+sFH8/1u2JK+pr3q6fOPXDu3lYbxqeVAfpCrKZTjuvvvPXqzLv1Wudfp1/84CdiEtTa xmStxFKckWioxVxUnAgAhw7UhGoDAAA=
Subject: [tcmtf] M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 13 Jul 2012 09:22:23 -0000

--Boundary_(ID_CtANLI/hoHHxF4pTPP9QBA)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_qOoF9mXdQr7RsxJeaYidDg)"


--Boundary_(ID_qOoF9mXdQr7RsxJeaYidDg)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hello all,

I think that a potential application scenario could be M2M networks, for example, Wireless Sensor Networks (WSNs). WSNs are local wireless networks composed by small devices acquiring environment information and sometimes acting over the environment (fire detection, air pollution monitoring, smart metering, care for gardens, security, structure monitoring, agriculture, ecology, greenhouses...). Sometimes, those devices has a local connectivity using ZigBee or 802.15.4 (there is a IETF WG named 6loWPAN, using IPv6 over that networks) and they have a gateway with fixed (xDSL) or mobile (3G/HSPA) networks towards (for example over the Internet) the servers storing and processing the information.

http://en.wikipedia.org/wiki/Wireless_sensor_network

As you can imagine, in many cases the size of the packets is very small, and in some scenarios you could have a lot of devices sending information over the same gateway, generating a lot of inefficient data packets (with low payload).

The question is: Could that scenario be considered as a candidate to apply TCMTF?

Best Regards,

Fernando


________________________________

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

--Boundary_(ID_qOoF9mXdQr7RsxJeaYidDg)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style>
<!--
@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.EmailStyle17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
.MsoChpDefault
	{font-family:"Calibri","sans-serif"}
@page WordSection1
	{margin:70.85pt 3.0cm 70.85pt 3.0cm}
div.WordSection1
	{}
-->
</style>
</head>
<body lang="ES" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hello all,</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal"><span lang="EN-US">I think that a potential application scenario could be M2M networks, for example, Wireless Sensor Networks (WSNs). WSNs are local wireless networks composed by small devices acquiring environment information and sometimes
 acting over the environment (fire detection, air pollution monitoring, smart metering, care for gardens, security, structure monitoring, agriculture, ecology, greenhouses&#8230;). Sometimes, those devices has a local connectivity using ZigBee or 802.15.4 (there
 is a IETF WG named 6loWPAN, using IPv6 over that networks) and they have a gateway with fixed (xDSL) or mobile (3G/HSPA) networks towards (for example over the Internet) the servers storing and processing the information.
</span></p>
<p class="MsoNormal"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal"><a href="http://en.wikipedia.org/wiki/Wireless_sensor_network"><span lang="EN-US">http://en.wikipedia.org/wiki/Wireless_sensor_network</span></a></p>
<p class="MsoNormal"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal"><span lang="EN-US">As you can imagine, in many cases the size of the packets is very small, and in some scenarios you could have a lot of devices sending information over the same gateway, generating a lot of inefficient data packets (with
 low payload).</span></p>
<p class="MsoNormal"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal"><span lang="EN-US">The question is: Could that scenario be considered as a candidate to apply TCMTF?</span></p>
<p class="MsoNormal"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal"><span lang="EN-US">Best Regards,</span></p>
<p class="MsoNormal"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal"><span lang="EN-US" style="">Fernando</span></p>
<p class="MsoNormal"><span lang="EN-US">&nbsp;</span></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra pol&iacute;tica de env&iacute;o y recepci&oacute;n de correo electr&oacute;nico en el enlace situado m&aacute;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>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_qOoF9mXdQr7RsxJeaYidDg)--

--Boundary_(ID_CtANLI/hoHHxF4pTPP9QBA)
Content-type: text/x-vcard; name="Fernando Pascual Blanco.vcf"
Content-transfer-encoding: base64
Content-disposition: attachment; filename="Fernando Pascual Blanco.vcf";
 size=1782; creation-date="Fri, 13 Jul 2012 09:22:54 GMT";
 modification-date="Fri, 13 Jul 2012 09:22:54 GMT"
Content-description: Fernando Pascual Blanco.vcf

QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpYLU1TLVNJR05BVFVSRTpZRVMNCk47TEFOR1VBR0U9
ZXM6UGFzY3VhbCBCbGFuY287RmVybmFuZG8NCkZOOkZlcm5hbmRvIFBhc2N1YWwgQmxhbmNvDQpP
Ukc7Q0hBUlNFVD1XaW5kb3dzLTEyNTI6VGVsZWbzbmljYSBJK0QNClRJVExFOk5ldHdvcmsgQXV0
b21hdGlvbiBhbmQgRHluYW1pemF0aW9uDQpURUw7V09SSztWT0lDRTozNCA5MTMxMjg3NzkNClRF
TDtDRUxMO1ZPSUNFOjM0IDY4MjAwNTE2OA0KQURSO1dPUks7UFJFRjtDSEFSU0VUPVdpbmRvd3Mt
MTI1Mjo7O0RvbiBSYW3zbiBkZSBsYSBDcnV6IDgyLTg0O01hZHJpZDtNYWRyaWQ7MjgwMDY7U3Bh
aW4NCkxBQkVMO1dPUks7UFJFRjtDSEFSU0VUPVdpbmRvd3MtMTI1MjtFTkNPRElORz1RVU9URUQt
UFJJTlRBQkxFOkRvbiBSYW09RjNuIGRlIGxhIENydXogODItODQ9MEQ9MEE9DQoyODAwNiAgTWFk
cmlkICBNYWRyaWQ9MEQ9MEE9DQpTcGFpbg0KWC1NUy1PTC1ERUZBVUxULVBPU1RBTC1BRERSRVNT
OjINCkVNQUlMO1BSRUY7SU5URVJORVQ6ZnBiQHRpZC5lcw0KWC1NUy1PTC1ERVNJR047Q0hBUlNF
VD11dGYtODo8Y2FyZCB4bWxucz0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9vZmZpY2Uv
b3V0bG9vay8xMi9lbGVjdHJvbmljYnVzaW5lc3NjYXJkcyIgdmVyPSIxLjAiIGxheW91dD0ibGVm
dCIgYmdjb2xvcj0iZmZmZmZmIj48aW1nIHhtbG5zPSIiIGFsaWduPSJmaXQiIGFyZWE9IjE2IiB1
c2U9ImNhcmRwaWN0dXJlIi8+PGZsZCB4bWxucz0iIiBwcm9wPSJuYW1lIiBhbGlnbj0ibGVmdCIg
ZGlyPSJsdHIiIHN0eWxlPSJiIiBjb2xvcj0iMDAwMDAwIiBzaXplPSIxMCIvPjxmbGQgeG1sbnM9
IiIgcHJvcD0ib3JnIiBhbGlnbj0ibGVmdCIgZGlyPSJsdHIiIGNvbG9yPSIwMDAwMDAiIHNpemU9
IjgiLz48ZmxkIHhtbG5zPSIiIHByb3A9InRpdGxlIiBhbGlnbj0ibGVmdCIgZGlyPSJsdHIiIGNv
bG9yPSIwMDAwMDAiIHNpemU9IjgiLz48ZmxkIHhtbG5zPSIiIHByb3A9ImJsYW5rIiBzaXplPSI4
Ii8+PGZsZCB4bWxucz0iIiBwcm9wPSJ0ZWx3b3JrIiBhbGlnbj0ibGVmdCIgZGlyPSJsdHIiIGNv
bG9yPSIwMDAwMDAiIHNpemU9IjgiPjxsYWJlbCBhbGlnbj0icmlnaHQiIGNvbG9yPSI2MjYyNjIi
Pldvcms8L2xhYmVsPjwvZmxkPjxmbGQgeG1sbnM9IiIgcHJvcD0idGVsY2VsbCIgYWxpZ249Imxl
ZnQiIGRpcj0ibHRyIiBjb2xvcj0iMDAwMDAwIiBzaXplPSI4Ij48bGFiZWwgYWxpZ249InJpZ2h0
IiBjb2xvcj0iNjI2MjYyIj5Nb2JpbGU8L2xhYmVsPjwvZmxkPjxmbGQgeG1sbnM9IiIgcHJvcD0i
ZW1haWwiIGFsaWduPSJsZWZ0IiBkaXI9Imx0ciIgY29sb3I9IjAwMDAwMCIgc2l6ZT0iOCIvPjxm
bGQgeG1sbnM9IiIgcHJvcD0iYWRkcndvcmsiIGFsaWduPSJsZWZ0IiBkaXI9Imx0ciIgY29sb3I9
IjAwMDAwMCIgc2l6ZT0iOCIvPjxmbGQgeG1sbnM9IiIgcHJvcD0iYmxhbmsiIHNpemU9IjgiLz48
ZmxkIHhtbG5zPSIiIHByb3A9ImJsYW5rIiBzaXplPSI4Ii8+PGZsZCB4bWxucz0iIiBwcm9wPSJi
bGFuayIgc2l6ZT0iOCIvPjxmbGQgeG1sbnM9IiIgcHJvcD0iYmxhbmsiIHNpemU9IjgiLz48Zmxk
IHhtbG5zPSIiIHByb3A9ImJsYW5rIiBzaXplPSI4Ii8+PGZsZCB4bWxucz0iIiBwcm9wPSJibGFu
ayIgc2l6ZT0iOCIvPjxmbGQgeG1sbnM9IiIgcHJvcD0iYmxhbmsiIHNpemU9IjgiLz48ZmxkIHht
bG5zPSIiIHByb3A9ImJsYW5rIiBzaXplPSI4Ii8+PC9jYXJkPg0KUkVWOjIwMTIwNTA5VDA3NTI1
NFoNCkVORDpWQ0FSRA0K

--Boundary_(ID_CtANLI/hoHHxF4pTPP9QBA)--

From Tomaso.deCola@dlr.de  Tue Jul 17 06:15:58 2012
Return-Path: <Tomaso.deCola@dlr.de>
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 2E9DC21F86FD for <tcmtf@ietfa.amsl.com>; Tue, 17 Jul 2012 06:15:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.249
X-Spam-Level: 
X-Spam-Status: No, score=-8.249 tagged_above=-999 required=5 tests=[AWL=1.999,  BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 RQjFt-FPOFoR for <tcmtf@ietfa.amsl.com>; Tue, 17 Jul 2012 06:15:55 -0700 (PDT)
Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.32]) by ietfa.amsl.com (Postfix) with ESMTP id E943E21F86FA for <tcmtf@ietf.org>; Tue, 17 Jul 2012 06:15:54 -0700 (PDT)
Received: from DLREXHUB02.intra.dlr.de (172.21.152.140) by dlrexedge01.dlr.de (172.21.163.100) with Microsoft SMTP Server (TLS) id 14.2.309.2; Tue, 17 Jul 2012 15:16:17 +0200
Received: from DLREXMBX02.intra.dlr.de ([fe80::8cc6:b83e:ddc1:4e8b]) by dlrexhub02.intra.dlr.de ([::1]) with mapi id 14.02.0309.002; Tue, 17 Jul 2012 15:16:19 +0200
From: <Tomaso.deCola@dlr.de>
To: <tcmtf@ietf.org>
Thread-Topic: [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
Thread-Index: AQJ64L0ugSKGpdB06FnFmfD7UMxzFZXMIFhQgAZYTdA=
Date: Tue, 17 Jul 2012 13:16:18 +0000
Message-ID: <1A39DCC13AF3C14B83CD74124D4DCFC30BE2ADBF@dlrexmbx02.intra.dlr.de>
References: <F5EDC35DF914C1428C28E149F10463A211401AA2@EX10-MB1-MAD.hi.inet> <009201cd60f0$ece8cdf0$c6ba69d0$@unizar.es>
In-Reply-To: <009201cd60f0$ece8cdf0$c6ba69d0$@unizar.es>
Accept-Language: it-IT, de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.247.173.215]
Content-Type: multipart/alternative; boundary="_000_1A39DCC13AF3C14B83CD74124D4DCFC30BE2ADBFdlrexmbx02intra_"
MIME-Version: 1.0
Cc: jsaldana@unizar.es
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 17 Jul 2012 13:15:58 -0000

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

Dear Fernando, dear all,

I also see the case of M2M networks as an appealing scenario where TCMTF co=
uld be used profitably. In addition to Fernando's consideration I would als=
o add the case of WSN connected via satellite to data/monitoring centres. S=
ince satellite capacity is not uniquely assigned to a specific applications=
 or service providers, an efficient multiplexing (e.g., compression and tun=
neling) would be more than welcome to accommodate properly the WSN data flo=
ws. In this context, traffic classification could also play an important ro=
le to perform multiplexing and apply the appropriate compression algorithm =
in the most efficient way.

Best Regards,

Tomaso


------------------------
Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR)
German Aerospace Center
Institute of Communications und Navigation | Satellite Networks | Oberpfaff=
enhofen | 82234 Wessling | Germany
Tomaso de Cola, Ph.D.
Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 | tomaso.decola@dlr.de=
<mailto:sandro.scalise@dlr.de>
http://www.dlr.de/kn/institut/abteilungen/san



De: tsvwg-bounces@ietf.org<mailto:tsvwg-bounces@ietf.org> [mailto:tsvwg-bou=
nces@ietf.org]<mailto:[mailto:tsvwg-bounces@ietf.org]> En nombre de FERNAND=
O PASCUAL BLANCO
Enviado el: viernes, 13 de julio de 2012 11:23
Para: tsvwg@ietf.org<mailto:tsvwg@ietf.org>; tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>
Asunto: [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf

Hello all,

I think that a potential application scenario could be M2M networks, for ex=
ample, Wireless Sensor Networks (WSNs). WSNs are local wireless networks co=
mposed by small devices acquiring environment information and sometimes act=
ing over the environment (fire detection, air pollution monitoring, smart m=
etering, care for gardens, security, structure monitoring, agriculture, eco=
logy, greenhouses...). Sometimes, those devices has a local connectivity us=
ing ZigBee or 802.15.4 (there is a IETF WG named 6loWPAN, using IPv6 over t=
hat networks) and they have a gateway with fixed (xDSL) or mobile (3G/HSPA)=
 networks towards (for example over the Internet) the servers storing and p=
rocessing the information.

http://en.wikipedia.org/wiki/Wireless_sensor_network

As you can imagine, in many cases the size of the packets is very small, an=
d in some scenarios you could have a lot of devices sending information ove=
r the same gateway, generating a lot of inefficient data packets (with low =
payload).

The question is: Could that scenario be considered as a candidate to apply =
TCMTF?

Best Regards,

Fernando


________________________________

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

--_000_1A39DCC13AF3C14B83CD74124D4DCFC30BE2ADBFdlrexmbx02intra_
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-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=3Diso-8859-=
1">
<meta name=3D"Generator" 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: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";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Calibri","sans-serif";}
span.emailstyle17
	{mso-style-name:emailstyle17;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	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";}
span.EmailStyle22
	{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">Dear Fernando, dear al=
l,<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 also see the case of=
 M2M networks as an appealing scenario where TCMTF could be used profitably=
. In addition to Fernando&#8217;s consideration I would also add the case o=
f WSN connected via satellite to data/monitoring
 centres. Since satellite capacity is not uniquely assigned to a specific a=
pplications or service providers, an efficient multiplexing (e.g., compress=
ion and tunneling) would be more than welcome to accommodate properly the W=
SN data flows. In this context,
 traffic classification could also play an important role to perform multip=
lexing and apply the appropriate compression algorithm in the most efficien=
t way.<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">Best Regards,<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">Tomaso<o:p></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"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"DE" style=3D"font-size:10.0pt;font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;color:dimgray">&#8212;&#8212;&#8212;&#8212;&=
#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212=
;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</span><spa=
n lang=3D"DE" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&q=
uot;,&quot;serif&quot;;color:#1F497D">
<br>
</span><b><span lang=3D"DE" style=3D"font-size:10.0pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;;color:dimgray">Deutsches Zentrum f=FCr Luft=
- und Raumfahrt</span></b><span lang=3D"DE" style=3D"font-size:10.0pt;font-=
family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:dimgray"> (DLR)</span=
><span lang=3D"DE" style=3D"font-size:12.0pt;font-family:&quot;Times New Ro=
man&quot;,&quot;serif&quot;;color:#1F497D">
<br>
</span><span lang=3D"DE" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:dimgray">German Aerospace Center</span><=
span lang=3D"DE" style=3D"font-size:12.0pt;font-family:&quot;Times New Roma=
n&quot;,&quot;serif&quot;;color:#1F497D">
<br>
</span><span lang=3D"DE" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:dimgray">Institute of Communications und=
 Navigation | Satellite Networks | Oberpfaffenhofen | 82234 Wessling | Germ=
any</span><span lang=3D"DE" style=3D"font-size:12.0pt;font-family:&quot;Tim=
es New Roman&quot;,&quot;serif&quot;;color:#1F497D">
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:dimgray">Tomaso de Cola, Ph.D.</s=
pan></b><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&q=
uot;,&quot;serif&quot;;color:#1F497D">
<br>
</span><span lang=3D"DE" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:dimgray">Telefon &#43;49 8153 28-2156 | =
Telefax&nbsp; &#43;49 8153 28-2844 |</span><span lang=3D"DE" style=3D"font-=
size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F4=
97D">
</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;;color:#1F497D"><a href=3D"mailto:sandro.scalise@dlr.d=
e"><span lang=3D"DE" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot=
;,&quot;sans-serif&quot;">tomaso.decola@dlr.de</span></a></span><span lang=
=3D"DE" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&=
quot;serif&quot;;color:#1F497D">
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:#1F497D"><a href=3D"http://www.dlr.de/kn/institut/ab=
teilungen/san"><span lang=3D"DE">http://www.dlr.de/kn/institut/abteilungen/=
san</span></a></span><span style=3D"font-size:12.0pt;font-family:&quot;Time=
s New Roman&quot;,&quot;serif&quot;;color:#1F497D">
</span><span lang=3D"DE" style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"DE"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" 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 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;">De:</span></b><span lang=
=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans=
-serif&quot;">
<a href=3D"mailto:tsvwg-bounces@ietf.org">tsvwg-bounces@ietf.org</a> <a hre=
f=3D"mailto:[mailto:tsvwg-bounces@ietf.org]">
[mailto:tsvwg-bounces@ietf.org]</a> <b>En nombre de </b>FERNANDO PASCUAL BL=
ANCO<br>
<b>Enviado el:</b> viernes, 13 de julio de 2012 11:23<br>
<b>Para:</b> <a href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>; <a href=
=3D"mailto:tcmtf@ietf.org">
tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf<o:p></o:p></=
span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"ES">Hello all,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal">I think that a potential application scenario could =
be M2M networks, for example, Wireless Sensor Networks (WSNs). WSNs are loc=
al wireless networks composed by small devices acquiring environment inform=
ation and sometimes acting over the
 environment (fire detection, air pollution monitoring, smart metering, car=
e for gardens, security, structure monitoring, agriculture, ecology, greenh=
ouses&#8230;). Sometimes, those devices has a local connectivity using ZigB=
ee or 802.15.4 (there is a IETF WG named
 6loWPAN, using IPv6 over that networks) and they have a gateway with fixed=
 (xDSL) or mobile (3G/HSPA) networks towards (for example over the Internet=
) the servers storing and processing the information.
<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES"><a href=3D"http://en.wikipedia.org=
/wiki/Wireless_sensor_network"><span lang=3D"EN-US">http://en.wikipedia.org=
/wiki/Wireless_sensor_network</span></a><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">As you can imagine, in many cases the size of the pa=
ckets is very small, and in some scenarios you could have a lot of devices =
sending information over the same gateway, generating a lot of inefficient =
data packets (with low payload).<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">The question is: Could that scenario be considered a=
s a candidate to apply TCMTF?<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">Best Regards,<span lang=3D"ES"><o:p></o:p></span></p=
>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">Fernando<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span>=
</p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"ES" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:7.5pt;font-fami=
ly:&quot;Arial&quot;,&quot;sans-serif&quot;;color:gray"><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 href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span lang=3D"ES" style=3D"font-size:1=
2.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p=
></span></p>
</div>
</body>
</html>

--_000_1A39DCC13AF3C14B83CD74124D4DCFC30BE2ADBFdlrexmbx02intra_--

From fpb@tid.es  Tue Jul 17 23:54:07 2012
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 A9D7211E8147 for <tcmtf@ietfa.amsl.com>; Tue, 17 Jul 2012 23:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.626
X-Spam-Level: 
X-Spam-Status: No, score=-5.626 tagged_above=-999 required=5 tests=[AWL=0.972,  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 C3ugLYxXpJhw for <tcmtf@ietfa.amsl.com>; Tue, 17 Jul 2012 23:54:04 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id CE26F11E80B7 for <tcmtf@ietf.org>; Tue, 17 Jul 2012 23:54:02 -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 <0M7C007QSGJ7KF@tid.hi.inet> for tcmtf@ietf.org; Wed, 18 Jul 2012 08:54:51 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id DF.C6.02752.9BD56005; Wed, 18 Jul 2012 08:54:50 +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 <0M7C007RUGJDKF@tid.hi.inet> for tcmtf@ietf.org; Wed, 18 Jul 2012 08:54:49 +0200 (MEST)
Received: from EX10-MB1-MAD.hi.inet ([fe80::a473:4f3e:f8db:1855]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0298.004; Wed, 18 Jul 2012 08:54:49 +0200
Date: Wed, 18 Jul 2012 06:54:48 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <1A39DCC13AF3C14B83CD74124D4DCFC30BE2ADBF@dlrexmbx02.intra.dlr.de>
X-Originating-IP: [10.95.64.115]
To: "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A2114041C2@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_pVr+NgoPDIi3ad2ggrenJQ)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
Thread-index: Ac1g2RR6RDhC6yzGQMG7kvzNfOCRRpXMIFhQgAZYTdCVysk+EA==
X-AuditID: 0a5f4e69-b7f6d6d000000ac0-11-50065db9dff1
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOKsWRmVeSWpSXmKPExsXCFe9nqLsrli3A4M9sDotdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoEr49CeX+wFVxsYK3a+amVuYLxV2MXIwSEhYCLx/BVzFyMnkCkm ceHeerYuRi4OIYHtjBJnVkxhh3B+MkpMvNLKDOEsBcrce8gC0s0ioCrRvNYHpJtNQEvi9N1V LCC2sICLxLaOb2A2p4C/xNNNf5ggNihI/Dn3GCwuIhAm8e7fLjCbWUBX4vDmNUwgI3kFvCWe rOMFCfMKCEr8mHwPqiRXYva/H6wQtrhEc+tNsDijgKzEu/nzWSFGukqs2doPNkZEwAnonBqI rQISS/ach/pRVOLl439g5UIC+xglvrTGT2AUm4Vk2ywk22Yh2QZh60ncmDqFDcLWlli28DXz LKgHZvw7xIIsvoCRfRWjWHFSUWZ6RkluYmZOuoGRXkamXmZeaskmRkjMZe5gXL5T5RCjAAej Eg+vxLRP/kKsiWXFlbmHGCU5mJREeVfEsAUI8SXlp1RmJBZnxBeV5qQWH2KU4GBWEuEVfM4a IMSbklhZlVqUD5OS4eBQkuB9A9ImWJSanlqRlpkDTCwwaSYOTpB2HqB2L2CaEeItLkjMLc5M h8ifYlTl6Nxy7xajEEtefl6qlDgvG0iRAEhRRmke3JxXjOJABwvzCoJkeYCpEW7CK6DhTEDD LUuYQIaXJCKkpBoYKxNLmo+lcPD8Tavdf9Zf+HkQZ4BC4eyH33a4i8xo9fo079E2/U8dc/3Y Zmvyf9GYcFqneolE5zy/1xYlWTM7N01p6bavb3RoOrjV5//2/ujFaS6GMSuatTZdKZmwTNPg yZU7q9oNjj/JZZc88uPfoZrD04MbsyYcZn7rI7cquGPfw2Dv/qw6JZbijERDLeai4kQAkaJ+ rkoDAAA=
References: <F5EDC35DF914C1428C28E149F10463A211401AA2@EX10-MB1-MAD.hi.inet> <009201cd60f0$ece8cdf0$c6ba69d0$@unizar.es> <1A39DCC13AF3C14B83CD74124D4DCFC30BE2ADBF@dlrexmbx02.intra.dlr.de>
Cc: "jsaldana@unizar.es" <jsaldana@unizar.es>
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 18 Jul 2012 06:54:07 -0000

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

Dear Tomaso,

                Absolutely. M2M networks and satellite networks are very go=
od candidates to apply TCMTF, and rightly in that case.

Regards,

Fernando

From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of T=
omaso.deCola@dlr.de
Sent: martes, 17 de julio de 2012 15:16
To: tcmtf@ietf.org
Cc: jsaldana@unizar.es
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf

Dear Fernando, dear all,

I also see the case of M2M networks as an appealing scenario where TCMTF co=
uld be used profitably. In addition to Fernando's consideration I would als=
o add the case of WSN connected via satellite to data/monitoring centres. S=
ince satellite capacity is not uniquely assigned to a specific applications=
 or service providers, an efficient multiplexing (e.g., compression and tun=
neling) would be more than welcome to accommodate properly the WSN data flo=
ws. In this context, traffic classification could also play an important ro=
le to perform multiplexing and apply the appropriate compression algorithm =
in the most efficient way.

Best Regards,

Tomaso


------------------------
Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR)
German Aerospace Center
Institute of Communications und Navigation | Satellite Networks | Oberpfaff=
enhofen | 82234 Wessling | Germany
Tomaso de Cola, Ph.D.
Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 | tomaso.decola@dlr.de=
<mailto:sandro.scalise@dlr.de>
http://www.dlr.de/kn/institut/abteilungen/san



De: tsvwg-bounces@ietf.org<mailto:tsvwg-bounces@ietf.org> [mailto:tsvwg-bou=
nces@ietf.org]<mailto:[mailto:tsvwg-bounces@ietf.org]> En nombre de FERNAND=
O PASCUAL BLANCO
Enviado el: viernes, 13 de julio de 2012 11:23
Para: tsvwg@ietf.org<mailto:tsvwg@ietf.org>; tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>
Asunto: [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf

Hello all,

I think that a potential application scenario could be M2M networks, for ex=
ample, Wireless Sensor Networks (WSNs). WSNs are local wireless networks co=
mposed by small devices acquiring environment information and sometimes act=
ing over the environment (fire detection, air pollution monitoring, smart m=
etering, care for gardens, security, structure monitoring, agriculture, eco=
logy, greenhouses...). Sometimes, those devices has a local connectivity us=
ing ZigBee or 802.15.4 (there is a IETF WG named 6loWPAN, using IPv6 over t=
hat networks) and they have a gateway with fixed (xDSL) or mobile (3G/HSPA)=
 networks towards (for example over the Internet) the servers storing and p=
rocessing the information.

http://en.wikipedia.org/wiki/Wireless_sensor_network

As you can imagine, in many cases the size of the packets is very small, an=
d in some scenarios you could have a lot of devices sending information ove=
r the same gateway, generating a lot of inefficient data packets (with low =
payload).

The question is: Could that scenario be considered as a candidate to apply =
TCMTF?

Best Regards,

Fernando


________________________________

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

________________________________

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_pVr+NgoPDIi3ad2ggrenJQ)
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:Calibri}
@font-face
	{font-family:Tahoma}
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}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif"}
span.BalloonTextChar
	{font-family:"Tahoma","sans-serif"}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{margin-right:0cm;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Calibri","sans-serif"}
span.emailstyle17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.EmailStyle21
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
span.EmailStyle22
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
span.EmailStyle23
	{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"color:#1F497D">Dear Tomaso,</span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span=
><span lang=3D"EN-US" style=3D"color:#1F497D">Absolutely. M2M networks and =
satellite networks are very good candidates to apply TCMTF, and rightly in =
that case.
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regards=
,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Fernando</span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></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 lang=3D"EN-US" style=3D"font-size:10.0pt; f=
ont-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span=
 lang=3D"EN-US" style=3D"font-size:10.0pt; font-family:&quot;Tahoma&quot;,&=
quot;sans-serif&quot;"> tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.o=
rg]
<b>On Behalf Of </b>Tomaso.deCola@dlr.de<br>
<b>Sent:</b> martes, 17 de julio de 2012 15:16<br>
<b>To:</b> tcmtf@ietf.org<br>
<b>Cc:</b> jsaldana@unizar.es<br>
<b>Subject:</b> Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf=
</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Dear Fe=
rnando, dear all,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I also =
see the case of M2M networks as an appealing scenario where TCMTF could be =
used profitably. In addition to Fernando&#8217;s consideration I would also=
 add the case of WSN connected via satellite
 to data/monitoring centres. Since satellite capacity is not uniquely assig=
ned to a specific applications or service providers, an efficient multiplex=
ing (e.g., compression and tunneling) would be more than welcome to accommo=
date properly the WSN data flows.
 In this context, traffic classification could also play an important role =
to perform multiplexing and apply the appropriate compression algorithm in =
the most efficient way.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Best Re=
gards,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Tomaso<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"DE" style=3D"font-size:10.0=
pt; font-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:dimgray">&#=
8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;=
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#821=
2;&#8212;&#8212;</span><span lang=3D"DE" style=3D"font-size:12.0pt; font-fa=
mily:&quot;Times New Roman&quot;,&quot;serif&quot;; color:#1F497D">
<br>
</span><b><span lang=3D"DE" style=3D"font-size:10.0pt; font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;; color:dimgray">Deutsches Zentrum f=FCr Lu=
ft- und Raumfahrt</span></b><span lang=3D"DE" style=3D"font-size:10.0pt; fo=
nt-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:dimgray"> (DLR)</=
span><span lang=3D"DE" style=3D"font-size:12.0pt; font-family:&quot;Times N=
ew Roman&quot;,&quot;serif&quot;; color:#1F497D">
<br>
</span><span lang=3D"DE" style=3D"font-size:10.0pt; font-family:&quot;Arial=
&quot;,&quot;sans-serif&quot;; color:dimgray">German Aerospace Center</span=
><span lang=3D"DE" style=3D"font-size:12.0pt; font-family:&quot;Times New R=
oman&quot;,&quot;serif&quot;; color:#1F497D">
<br>
</span><span lang=3D"DE" style=3D"font-size:10.0pt; font-family:&quot;Arial=
&quot;,&quot;sans-serif&quot;; color:dimgray">Institute of Communications u=
nd Navigation | Satellite Networks | Oberpfaffenhofen | 82234 Wessling | Ge=
rmany</span><span lang=3D"DE" style=3D"font-size:12.0pt; font-family:&quot;=
Times New Roman&quot;,&quot;serif&quot;; color:#1F497D">
</span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt; f=
ont-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:dimgray">Tomaso =
de Cola, Ph.D.</span></b><span lang=3D"EN-US" style=3D"font-size:12.0pt; fo=
nt-family:&quot;Times New Roman&quot;,&quot;serif&quot;; color:#1F497D">
<br>
</span><span lang=3D"DE" style=3D"font-size:10.0pt; font-family:&quot;Arial=
&quot;,&quot;sans-serif&quot;; color:dimgray">Telefon &#43;49 8153 28-2156 =
| Telefax&nbsp; &#43;49 8153 28-2844 |</span><span lang=3D"DE" style=3D"fon=
t-size:10.0pt; font-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:=
#1F497D">
</span><span lang=3D"EN-US" style=3D"font-size:12.0pt; font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;; color:#1F497D"><a href=3D"mailto:san=
dro.scalise@dlr.de"><span lang=3D"DE" style=3D"font-size:10.0pt; font-famil=
y:&quot;Arial&quot;,&quot;sans-serif&quot;">tomaso.decola@dlr.de</span></a>=
</span><span lang=3D"DE" style=3D"font-size:12.0pt; font-family:&quot;Times=
 New Roman&quot;,&quot;serif&quot;; color:#1F497D">
<br>
</span><span lang=3D"EN-US" style=3D"font-size:10.0pt; font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;; color:#1F497D"><a href=3D"http://www.dlr.=
de/kn/institut/abteilungen/san"><span lang=3D"DE">http://www.dlr.de/kn/inst=
itut/abteilungen/san</span></a></span><span lang=3D"EN-US" style=3D"font-si=
ze:12.0pt; font-family:&quot;Times New Roman&quot;,&quot;serif&quot;; color=
:#1F497D">
</span><span lang=3D"DE" style=3D"color:#1F497D"></span></p>
<p class=3D"MsoNormal"><span lang=3D"DE">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></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;">
<a href=3D"mailto:tsvwg-bounces@ietf.org">tsvwg-bounces@ietf.org</a> <a hre=
f=3D"mailto:[mailto:tsvwg-bounces@ietf.org]">
[mailto:tsvwg-bounces@ietf.org]</a> <b>En nombre de </b>FERNANDO PASCUAL BL=
ANCO<br>
<b>Enviado el:</b> viernes, 13 de julio de 2012 11:23<br>
<b>Para:</b> <a href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>; <a href=
=3D"mailto:tcmtf@ietf.org">
tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<div>
<p class=3D"MsoNormal">Hello all,</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I think that a potential applic=
ation scenario could be M2M networks, for example, Wireless Sensor Networks=
 (WSNs). WSNs are local wireless networks composed by small devices acquiri=
ng environment information and sometimes
 acting over the environment (fire detection, air pollution monitoring, sma=
rt metering, care for gardens, security, structure monitoring, agriculture,=
 ecology, greenhouses&#8230;). Sometimes, those devices has a local connect=
ivity using ZigBee or 802.15.4 (there
 is a IETF WG named 6loWPAN, using IPv6 over that networks) and they have a=
 gateway with fixed (xDSL) or mobile (3G/HSPA) networks towards (for exampl=
e over the Internet) the servers storing and processing the information.
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><a href=3D"http://en.wikipedia.org/wiki/Wireless_sen=
sor_network"><span lang=3D"EN-US">http://en.wikipedia.org/wiki/Wireless_sen=
sor_network</span></a></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">As you can imagine, in many cas=
es the size of the packets is very small, and in some scenarios you could h=
ave a lot of devices sending information over the same gateway, generating =
a lot of inefficient data packets (with
 low payload).</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The question is: Could that sce=
nario be considered as a candidate to apply TCMTF?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Best Regards,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Fernando</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt; font-family:&quot;T=
imes New Roman&quot;,&quot;serif&quot;">&nbsp;</span></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-size:12.0pt; font-family:&quot;Times New Roman&quot;,&quot;s=
erif&quot;">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt; font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;; color:gray"><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 href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span style=3D"font-size:12.0pt; font-=
family:&quot;Times New Roman&quot;,&quot;serif&quot;"></span></p>
</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_pVr+NgoPDIi3ad2ggrenJQ)--

From jsaldana@unizar.es  Thu Jul 19 07:09:34 2012
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 1D98F21F861D for <tcmtf@ietfa.amsl.com>; Thu, 19 Jul 2012 07:09:34 -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 A6vfr8Fwef5N for <tcmtf@ietfa.amsl.com>; Thu, 19 Jul 2012 07:09:29 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id E498021F8732 for <tcmtf@ietf.org>; Thu, 19 Jul 2012 07:09:27 -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 q6JEABee023543; Thu, 19 Jul 2012 16:10:11 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <Tomaso.deCola@dlr.de>, "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>
References: <F5EDC35DF914C1428C28E149F10463A211401AA2@EX10-MB1-MAD.hi.inet> <009201cd60f0$ece8cdf0$c6ba69d0$@unizar.es> <1A39DCC13AF3C14B83CD74124D4DCFC30BE2ADBF@dlrexmbx02.intra.dlr.de>
In-Reply-To: <1A39DCC13AF3C14B83CD74124D4DCFC30BE2ADBF@dlrexmbx02.intra.dlr.de>
Date: Thu, 19 Jul 2012 16:10:19 +0200
Organization: Universidad de Zaragoza
Message-ID: <00a301cd65b8$3b00abe0$b10203a0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A4_01CD65C8.FE8ADB70"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ64L0ugSKGpdB06FnFmfD7UMxzFQGIKrtKAdBf8t+VuueOAA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 19 Jul 2012 14:09:34 -0000

This is a multipart message in MIME format.

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

Dear Tomaso and Fernando,

=20

I think this is a really interesting case where TCMTF can be used. I =
have to
say that we had not thought about it when we first proposed the =
multiplexing
idea. But, as you say, this is a scenario with good characteristics for
multiplexing:

=20

-          A lot of flows sharing a common path: In this case, the =
common
path is from the =93gateway=94 to the place where data is stored or =
analyzed.

-          Small packets, where header compression implies a significant
reduction in the total size.

-          Scarce bandwidth: In satellite links it is clear, but also if =
a
xDSL or 3G connection is used, bandwidth can be scarce depending on the
number of sensors.

-          Perhaps not very tight real-time limits: This is good, since =
we
can multiplex a big number of packets. I mean, in some of these =
scenarios 5
seconds may not be too much time. So perhaps we could wait until we have =
a
MTU-sized packet to send.

=20

Nevertheless, in order to get an idea of the savings, we should deploy =
some
calculations. Our research group has only done simulations for VoIP and
games. In this case, we should know:

=20

-          Number of sensors in a typical scenario.

-          Packet size and used headers. If IPv6 is used, savings can be
really big, since header compression is really good for it.=20

-          Packets per second that a single sensor can generate.

=20

And of course, the gateway should be the place for multiplexing. In this
case, the flows only travel from sensors to data center. Am I right?

=20

Thanks,

=20

Jose

=20

De: Tomaso.deCola@dlr.de [mailto:Tomaso.deCola@dlr.de]=20
Enviado el: martes, 17 de julio de 2012 15:16
Para: tcmtf@ietf.org
CC: jsaldana@unizar.es
Asunto: RE: [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf

=20

Dear Fernando, dear all,

=20

I also see the case of M2M networks as an appealing scenario where TCMTF
could be used profitably. In addition to Fernando=92s consideration I =
would
also add the case of WSN connected via satellite to data/monitoring =
centres.
Since satellite capacity is not uniquely assigned to a specific =
applications
or service providers, an efficient multiplexing (e.g., compression and
tunneling) would be more than welcome to accommodate properly the WSN =
data
flows. In this context, traffic classification could also play an =
important
role to perform multiplexing and apply the appropriate compression =
algorithm
in the most efficient way.

=20

Best Regards,

=20

Tomaso

=20

=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 =

Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR)=20
German Aerospace Center=20
Institute of Communications und Navigation | Satellite Networks |
Oberpfaffenhofen | 82234 Wessling | Germany=20

Tomaso de Cola, Ph.D.=20
Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
<mailto:sandro.scalise@dlr.de> tomaso.decola@dlr.de=20
 <http://www.dlr.de/kn/institut/abteilungen/san>
http://www.dlr.de/kn/institut/abteilungen/san=20

=20

=20

=20

De: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] En nombre de
FERNANDO PASCUAL BLANCO
Enviado el: viernes, 13 de julio de 2012 11:23
Para: tsvwg@ietf.org; tcmtf@ietf.org
Asunto: [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf

=20

Hello all,

=20

I think that a potential application scenario could be M2M networks, for
example, Wireless Sensor Networks (WSNs). WSNs are local wireless =
networks
composed by small devices acquiring environment information and =
sometimes
acting over the environment (fire detection, air pollution monitoring, =
smart
metering, care for gardens, security, structure monitoring, agriculture,
ecology, greenhouses=85). Sometimes, those devices has a local =
connectivity
using ZigBee or 802.15.4 (there is a IETF WG named 6loWPAN, using IPv6 =
over
that networks) and they have a gateway with fixed (xDSL) or mobile =
(3G/HSPA)
networks towards (for example over the Internet) the servers storing and
processing the information.=20

=20

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

=20

As you can imagine, in many cases the size of the packets is very small, =
and
in some scenarios you could have a lot of devices sending information =
over
the same gateway, generating a lot of inefficient data packets (with low
payload).

=20

The question is: Could that scenario be considered as a candidate to =
apply
TCMTF?

=20

Best Regards,

=20

Fernando

=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_00A4_01CD65C8.FE8ADB70
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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	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";}
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:12.0pt;
	font-family:"Calibri","sans-serif";}
span.emailstyle17
	{mso-style-name:emailstyle17;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
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.EstiloCorreo24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EstiloCorreo25
	{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;}
/* List Definitions */
@list l0
	{mso-list-id:442500787;
	mso-list-type:hybrid;
	mso-list-template-ids:-1740457054 -2104612352 201981955 201981957 =
201981953 201981955 201981957 201981953 201981955 201981957;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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 =
style=3D'color:#1F497D'>Dear Tomaso and =
Fernando,<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 lang=3DEN-US style=3D'color:#1F497D'>I think =
this is a really interesting case where TCMTF can be used. I have to say =
that we had not thought about it when we first proposed the multiplexing =
idea. But, as you say, this is a scenario with good characteristics for =
multiplexing:<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=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span lang=3DEN-US =
style=3D'color:#1F497D'><span style=3D'mso-list:Ignore'>-<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'color:#1F497D'>A lot of flows sharing a common path: In this =
case, the common path is from the &#8220;gateway&#8221; to the place =
where data is stored or analyzed.<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span lang=3DEN-US =
style=3D'color:#1F497D'><span style=3D'mso-list:Ignore'>-<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'color:#1F497D'>Small packets, where header compression implies =
a significant reduction in the total size.<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span lang=3DEN-US =
style=3D'color:#1F497D'><span style=3D'mso-list:Ignore'>-<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'color:#1F497D'>Scarce bandwidth: In satellite links it is =
clear, but also if a xDSL or 3G connection is used, bandwidth can be =
scarce depending on the number of sensors.<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span lang=3DEN-US =
style=3D'color:#1F497D'><span style=3D'mso-list:Ignore'>-<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'color:#1F497D'>Perhaps not very tight real-time limits: This is =
good, since we can multiplex a big number of packets. I mean, in some of =
these scenarios 5 seconds may not be too much time. So perhaps we could =
wait until we have a MTU-sized packet to send.<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'>Nevertheless, in order to get an idea of the =
savings, we should deploy some calculations. Our research group has only =
done simulations for VoIP and games. In this case, we should =
know:<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=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span lang=3DEN-US =
style=3D'color:#1F497D'><span style=3D'mso-list:Ignore'>-<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'color:#1F497D'>Number of sensors in a typical =
scenario.<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span lang=3DEN-US style=3D'color:#1F497D'><span =
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'color:#1F497D'>Packet size and used headers. If IPv6 is used, =
savings can be really big, since header compression is really good for =
it. <o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span lang=3DEN-US style=3D'color:#1F497D'><span =
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'color:#1F497D'>Packets per second that a single sensor can =
generate.<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 of =
course, the gateway should be the place for multiplexing. In this case, =
the flows only travel from sensors to data center. Am I =
right?<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><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"'> =
Tomaso.deCola@dlr.de [mailto:Tomaso.deCola@dlr.de] <br><b>Enviado =
el:</b> martes, 17 de julio de 2012 15:16<br><b>Para:</b> =
tcmtf@ietf.org<br><b>CC:</b> jsaldana@unizar.es<br><b>Asunto:</b> RE: =
[tsvwg] M2M, WSNs and =
draft-saldana-tsvwg-tcmtf<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'>Dear Fernando, dear =
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 also see =
the case of M2M networks as an appealing scenario where TCMTF could be =
used profitably. In addition to Fernando&#8217;s consideration I would =
also add the case of WSN connected via satellite to data/monitoring =
centres. Since satellite capacity is not uniquely assigned to a specific =
applications or service providers, an efficient multiplexing (e.g., =
compression and tunneling) would be more than welcome to accommodate =
properly the WSN data flows. In this context, traffic classification =
could also play an important role to perform multiplexing and apply the =
appropriate compression algorithm in the most efficient =
way.<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'>Best =
Regards,<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'>Tomaso<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 =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray'=
>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#=
8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#821=
2;&#8212;&#8212;&#8212;</span><span lang=3DDE =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'> <br></span><b><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray'=
>Deutsches Zentrum f=FCr Luft- und Raumfahrt</span></b><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray'=
> (DLR)</span><span lang=3DDE =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'> <br></span><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray'=
>German Aerospace Center</span><span lang=3DDE =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'> <br></span><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray'=
>Institute of Communications und Navigation | Satellite Networks | =
Oberpfaffenhofen | 82234 Wessling | Germany</span><span lang=3DDE =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'> <o:p></o:p></span></p><p =
class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray'=
>Tomaso de Cola, Ph.D.</span></b><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'> <br></span><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray'=
>Telefon +49 8153 28-2156 | Telefax&nbsp; +49 8153 28-2844 |</span><span =
lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
> </span><span lang=3DEN-US style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif";color:#1F497D'><a =
href=3D"mailto:sandro.scalise@dlr.de"><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>tomaso.decola=
@dlr.de</span></a></span><span lang=3DDE =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'> <br></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'=
><a href=3D"http://www.dlr.de/kn/institut/abteilungen/san"><span =
lang=3DDE>http://www.dlr.de/kn/institut/abteilungen/san</span></a></span>=
<span lang=3DEN-US style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'> </span><span lang=3DDE =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DDE><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'><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'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:tsvwg-bounces@ietf.org">tsvwg-bounces@ietf.org</a> <a =
href=3D"mailto:[mailto:tsvwg-bounces@ietf.org]">[mailto:tsvwg-bounces@iet=
f.org]</a> <b>En nombre de </b>FERNANDO PASCUAL BLANCO<br><b>Enviado =
el:</b> viernes, 13 de julio de 2012 11:23<br><b>Para:</b> <a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>; <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><b>Asunto:</b> =
[tsvwg] M2M, WSNs and =
draft-saldana-tsvwg-tcmtf<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Hello =
all,<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>I think that a potential =
application scenario could be M2M networks, for example, Wireless Sensor =
Networks (WSNs). WSNs are local wireless networks composed by small =
devices acquiring environment information and sometimes acting over the =
environment (fire detection, air pollution monitoring, smart metering, =
care for gardens, security, structure monitoring, agriculture, ecology, =
greenhouses&#8230;). Sometimes, those devices has a local connectivity =
using ZigBee or 802.15.4 (there is a IETF WG named 6loWPAN, using IPv6 =
over that networks) and they have a gateway with fixed (xDSL) or mobile =
(3G/HSPA) networks towards (for example over the Internet) the servers =
storing and processing the information. </span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><a =
href=3D"http://en.wikipedia.org/wiki/Wireless_sensor_network"><span =
lang=3DEN-US>http://en.wikipedia.org/wiki/Wireless_sensor_network</span><=
/a><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>As you can imagine, in many cases the size of the packets =
is very small, and in some scenarios you could have a lot of devices =
sending information over the same gateway, generating a lot of =
inefficient data packets (with low payload).</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>The question is: Could that =
scenario be considered as a candidate to apply =
TCMTF?</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>Best Regards,</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>Fernando</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p></div><p =
class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><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:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p></div></body></html>
------=_NextPart_000_00A4_01CD65C8.FE8ADB70--


From dwing@cisco.com  Tue Jul 24 14:58:08 2012
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 9BE8D11E8080 for <tcmtf@ietfa.amsl.com>; Tue, 24 Jul 2012 14:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.498
X-Spam-Level: 
X-Spam-Status: No, score=-110.498 tagged_above=-999 required=5 tests=[AWL=0.101, 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 1ZpKNPSh7RXD for <tcmtf@ietfa.amsl.com>; Tue, 24 Jul 2012 14:58:08 -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 3216A11E8072 for <tcmtf@ietf.org>; Tue, 24 Jul 2012 14:58:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=814; q=dns/txt; s=iport; t=1343167088; x=1344376688; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=qbiZZYNHvDJHMvn45egUvg+7TS8l7jkm7+izGeL1V9k=; b=NIJkbjp1xCafIFXSCxzqLVIIaIpjc+Obd/WKo08bgZHSTpmI/gxGyDTg eGglZf87JTV7B3ta9pV+HfmUKKA1qOWm5Tk/kHnJeoK7FceHiyx9hMvQ9 0sqJFV7VEDjyW5nzWBiZSVIP/C/MfWOLanL+advdLxi52gGnMIeive+eI I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ak4KAOoZD1CrRDoG/2dsb2JhbABFqhuOQAOBJYEHgicICgEXED8NBQkPUCMcAQQeF4dqmmegPoxegkWDHAOIToUMlhaBZoJ/
X-IronPort-AV: E=Sophos;i="4.77,648,1336348800"; d="scan'208";a="49805360"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 24 Jul 2012 21:58:01 +0000
Received: from dwingWS ([10.21.78.151]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q6OLw0Mc010200; Tue, 24 Jul 2012 21:58:00 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <jsaldana@unizar.es>
Date: Tue, 24 Jul 2012 14:58:00 -0700
Message-ID: <03ee01cd69e7$649942e0$2dcbc8a0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1p52Rdu2gLdKImRwi7JCf7f1SpAQ==
Content-Language: en-us
X-Mailman-Approved-At: Wed, 25 Jul 2012 01:35:19 -0700
Cc: tcmtf@ietf.org, Tomaso.deCola@dlr.de, fpb@tid.es
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 24 Jul 2012 21:58:08 -0000

...
> Nevertheless, in order to get an idea of the savings, we should
> deploy some calculations. Our research group has only done
> simulations for VoIP and games. In this case, we should know:
>
>
>
> -          Number of sensors in a typical scenario.
>
> -          Packet size and used headers. If IPv6 is used, savings
>            can be really big, since header compression is really
>            good for it.
>
> -          Packets per second that a single sensor can generate.
>
>
>
> And of course, the gateway should be the place for multiplexing.
> In this case, the flows only travel from sensors to data center.
> Am I right?

I wonder if there is an easy way for the endpoints to signal that
they are delay tolerant (to allow collecting ~5 seconds of little
packets).

-d



From jsaldana@unizar.es  Thu Jul 26 03:56:11 2012
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 2540821F8700 for <tcmtf@ietfa.amsl.com>; Thu, 26 Jul 2012 03:56:11 -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 Jg5EcysExyeA for <tcmtf@ietfa.amsl.com>; Thu, 26 Jul 2012 03:56:10 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id A3CB921F86E0 for <tcmtf@ietf.org>; Thu, 26 Jul 2012 03:56:09 -0700 (PDT)
Received: from jsaldanapc (53.Red-81-32-18.dynamicIP.rima-tde.net [81.32.18.53]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id q6QAtxiB010769; Thu, 26 Jul 2012 12:56:00 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Dan Wing'" <dwing@cisco.com>
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com>
In-Reply-To: <03ee01cd69e7$649942e0$2dcbc8a0$@com>
Date: Thu, 26 Jul 2012 12:56:02 +0200
Message-ID: <004001cd6b1d$405442e0$c0fcc8a0$@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: AQGF+EuvFpZGZkinmlaOrA3LFBD+CZfKSBgQ
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 26 Jul 2012 10:56:11 -0000

Dan,

I don't know if I have really understood your question. Of course, I assume
that a delay of some seconds is not important for certain sensor networks.
But they don't need to signal that they are delay tolerant. I mean, they are
assumed to be from the moment they are installed.

Well, I think I should gather some information about typical examples of
sensor networks (number of sensors, frequency of samples, packet size of the
samples, etc), in order to calculate in which cases the bandwidth saving
obtained with TCMTF can be interesting, and which "multiplexing period"
should be used. I think that this could be a typical case in which
multiplexing can be done by packet size instead of using a period. I mean,
when you have almost 1500 bytes (or the MTU), you send a packet.

I don't know if I have answered your question,

Jose

-----Mensaje original-----
De: Dan Wing [mailto:dwing@cisco.com] 
Enviado el: martes, 24 de julio de 2012 23:58
Para: jsaldana@unizar.es
CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf

...
> Nevertheless, in order to get an idea of the savings, we should deploy 
> some calculations. Our research group has only done simulations for 
> VoIP and games. In this case, we should know:
>
>
>
> -          Number of sensors in a typical scenario.
>
> -          Packet size and used headers. If IPv6 is used, savings
>            can be really big, since header compression is really
>            good for it.
>
> -          Packets per second that a single sensor can generate.
>
>
>
> And of course, the gateway should be the place for multiplexing.
> In this case, the flows only travel from sensors to data center.
> Am I right?

I wonder if there is an easy way for the endpoints to signal that they are
delay tolerant (to allow collecting ~5 seconds of little packets).

-d



From Tomaso.deCola@dlr.de  Thu Jul 26 04:09:08 2012
Return-Path: <Tomaso.deCola@dlr.de>
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 95DDE21F8734 for <tcmtf@ietfa.amsl.com>; Thu, 26 Jul 2012 04:09:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.249
X-Spam-Level: 
X-Spam-Status: No, score=-9.249 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 8icz3aynSLJB for <tcmtf@ietfa.amsl.com>; Thu, 26 Jul 2012 04:09:07 -0700 (PDT)
Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.32]) by ietfa.amsl.com (Postfix) with ESMTP id 26C6C21F8751 for <tcmtf@ietf.org>; Thu, 26 Jul 2012 04:09:07 -0700 (PDT)
Received: from DLREXHUB02.intra.dlr.de (172.21.152.140) by dlrexedge01.dlr.de (172.21.163.100) with Microsoft SMTP Server (TLS) id 14.2.309.2; Thu, 26 Jul 2012 13:08:56 +0200
Received: from DLREXMBX02.intra.dlr.de ([fe80::8cc6:b83e:ddc1:4e8b]) by dlrexhub02.intra.dlr.de ([::1]) with mapi id 14.02.0309.002; Thu, 26 Jul 2012 13:08:59 +0200
From: <Tomaso.deCola@dlr.de>
To: <jsaldana@unizar.es>, <dwing@cisco.com>
Thread-Topic: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
Thread-Index: Ac1p52Rdu2gLdKImRwi7JCf7f1SpAQBJRcsAAARuVIA=
Date: Thu, 26 Jul 2012 11:08:58 +0000
Message-ID: <1A39DCC13AF3C14B83CD74124D4DCFC30BE31BC3@dlrexmbx02.intra.dlr.de>
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com> <004001cd6b1d$405442e0$c0fcc8a0$@unizar.es>
In-Reply-To: <004001cd6b1d$405442e0$c0fcc8a0$@unizar.es>
Accept-Language: it-IT, de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.247.173.215]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 26 Jul 2012 11:09:08 -0000

I also agree with Jose. It is likely that at installation time, they are co=
nfigured in  a way to collect a number of packets before actually processin=
g them. Of course this very much depends on the specific application, for w=
hich delay tolerance could be critical. Another aspect or question is wheth=
er sensor data are collected through a dedicated network infrastructure or =
not. In the case sensors data are distributed over a network  where other a=
pplication data (still sensors or also other data flows) are multiplexed to=
gether, then delay fluctuation could be experienced. In this scenario, the =
tcmtf idea could also help to keep the delivery delay or the jitter within =
specific time intervals, so to allow the receiving application to work fine=
ly.

Regards,

Tomaso

------------------------
Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR)
German Aerospace Center
Institute of Communications und Navigation | Satellite Networks | Oberpfaff=
enhofen | 82234 Wessling | Germany

Tomaso de Cola, Ph.D.=20
Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 | tomaso.decola@dlr.de
http://www.dlr.de/kn/institut/abteilungen/san

-----Original Message-----
From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of J=
ose Saldana
Sent: Thursday, July 26, 2012 12:56 PM
To: 'Dan Wing'
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf

Dan,

I don't know if I have really understood your question. Of course, I assume=
 that a delay of some seconds is not important for certain sensor networks.
But they don't need to signal that they are delay tolerant. I mean, they ar=
e assumed to be from the moment they are installed.

Well, I think I should gather some information about typical examples of se=
nsor networks (number of sensors, frequency of samples, packet size of the =
samples, etc), in order to calculate in which cases the bandwidth saving ob=
tained with TCMTF can be interesting, and which "multiplexing period"
should be used. I think that this could be a typical case in which multiple=
xing can be done by packet size instead of using a period. I mean, when you=
 have almost 1500 bytes (or the MTU), you send a packet.

I don't know if I have answered your question,

Jose

-----Mensaje original-----
De: Dan Wing [mailto:dwing@cisco.com]
Enviado el: martes, 24 de julio de 2012 23:58
Para: jsaldana@unizar.es
CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf

...
> Nevertheless, in order to get an idea of the savings, we should deploy=20
> some calculations. Our research group has only done simulations for=20
> VoIP and games. In this case, we should know:
>
>
>
> -          Number of sensors in a typical scenario.
>
> -          Packet size and used headers. If IPv6 is used, savings
>            can be really big, since header compression is really
>            good for it.
>
> -          Packets per second that a single sensor can generate.
>
>
>
> And of course, the gateway should be the place for multiplexing.
> In this case, the flows only travel from sensors to data center.
> Am I right?

I wonder if there is an easy way for the endpoints to signal that they are =
delay tolerant (to allow collecting ~5 seconds of little packets).

-d


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

From gorry@erg.abdn.ac.uk  Thu Jul 26 05:21:16 2012
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 457EA21F875D for <tcmtf@ietfa.amsl.com>; Thu, 26 Jul 2012 05:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IkswCyETEZyh for <tcmtf@ietfa.amsl.com>; Thu, 26 Jul 2012 05:21:15 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by ietfa.amsl.com (Postfix) with ESMTP id 065AC21F8760 for <tcmtf@ietf.org>; Thu, 26 Jul 2012 05:21:14 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id q6QCL6D2002158; Thu, 26 Jul 2012 13:21:06 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Thu, 26 Jul 2012 13:21:07 +0100
Message-ID: <001bb7e57832957423b38feafec85f1f.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <1A39DCC13AF3C14B83CD74124D4DCFC30BE31BC3@dlrexmbx02.intra.dlr.de>
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com> <004001cd6b1d$405442e0$c0fcc8a0$@unizar.es> <1A39DCC13AF3C14B83CD74124D4DCFC30BE31BC3@dlrexmbx02.intra.dlr.de>
Date: Thu, 26 Jul 2012 13:21:07 +0100
From: gorry@erg.abdn.ac.uk
To: Tomaso.deCola@dlr.de
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
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
Cc: tcmtf@ietf.org, dwing@cisco.com, jsaldana@unizar.es
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 26 Jul 2012 12:21:16 -0000

Maybe I can try - one of the concerns raised for the tunnel compression
was knowing the parameters that would be acceptable for a particular
operator, application, user or whatever. It seems to me that if you had a
sensor network then the tunnels would need to operate on different time
scales for aggregation of messages, e.g. compared to a on-line game?

So, if we need an Internet spec it needs to be general enough to be
desirable to operators/users to use, but may also need to be flexible
enough that it can reach a wide enough community of interest to
develop/maintain and then operate the new protocol framework.

Gorry

> I also agree with Jose. It is likely that at installation time, they are
> configured in  a way to collect a number of packets before actually
> processing them. Of course this very much depends on the specific
> application, for which delay tolerance could be critical. Another aspect
> or question is whether sensor data are collected through a dedicated
> network infrastructure or not. In the case sensors data are distributed
> over a network  where other application data (still sensors or also other
> data flows) are multiplexed together, then delay fluctuation could be
> experienced. In this scenario, the tcmtf idea could also help to keep the
> delivery delay or the jitter within specific time intervals, so to allow
> the receiving application to work finely.
>
> Regards,
>
> Tomaso
>
> ------------------------
> Deutsches Zentrum für Luft- und Raumfahrt (DLR)
> German Aerospace Center
> Institute of Communications und Navigation | Satellite Networks |
> Oberpfaffenhofen | 82234 Wessling | Germany
>
> Tomaso de Cola, Ph.D.
> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |
> tomaso.decola@dlr.de
> http://www.dlr.de/kn/institut/abteilungen/san
>
> -----Original Message-----
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of
> Jose Saldana
> Sent: Thursday, July 26, 2012 12:56 PM
> To: 'Dan Wing'
> Cc: tcmtf@ietf.org
> Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>
> Dan,
>
> I don't know if I have really understood your question. Of course, I
> assume that a delay of some seconds is not important for certain sensor
> networks.
> But they don't need to signal that they are delay tolerant. I mean, they
> are assumed to be from the moment they are installed.
>
> Well, I think I should gather some information about typical examples of
> sensor networks (number of sensors, frequency of samples, packet size of
> the samples, etc), in order to calculate in which cases the bandwidth
> saving obtained with TCMTF can be interesting, and which "multiplexing
> period"
> should be used. I think that this could be a typical case in which
> multiplexing can be done by packet size instead of using a period. I mean,
> when you have almost 1500 bytes (or the MTU), you send a packet.
>
> I don't know if I have answered your question,
>
> Jose
>
> -----Mensaje original-----
> De: Dan Wing [mailto:dwing@cisco.com]
> Enviado el: martes, 24 de julio de 2012 23:58
> Para: jsaldana@unizar.es
> CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>
> ...
>> Nevertheless, in order to get an idea of the savings, we should deploy
>> some calculations. Our research group has only done simulations for
>> VoIP and games. In this case, we should know:
>>
>>
>>
>> -          Number of sensors in a typical scenario.
>>
>> -          Packet size and used headers. If IPv6 is used, savings
>>            can be really big, since header compression is really
>>            good for it.
>>
>> -          Packets per second that a single sensor can generate.
>>
>>
>>
>> And of course, the gateway should be the place for multiplexing.
>> In this case, the flows only travel from sensors to data center.
>> Am I right?
>
> I wonder if there is an easy way for the endpoints to signal that they are
> delay tolerant (to allow collecting ~5 seconds of little packets).
>
> -d
>
>
> _______________________________________________
> 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  Thu Jul 26 15:53:13 2012
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 B410F21F8499 for <tcmtf@ietfa.amsl.com>; Thu, 26 Jul 2012 15:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.472
X-Spam-Level: 
X-Spam-Status: No, score=-110.472 tagged_above=-999 required=5 tests=[AWL=0.127, 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 gIA8FX3YDR6q for <tcmtf@ietfa.amsl.com>; Thu, 26 Jul 2012 15:53:13 -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 1AEF321F8498 for <tcmtf@ietf.org>; Thu, 26 Jul 2012 15:53:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=3184; q=dns/txt; s=iport; t=1343343193; x=1344552793; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=WhM0Zwtb24ZryJ3AlV/HXof29XVG+CDclQG5tIqR6UU=; b=UPe3tpVRa5yqHiqMi/ZEqcf2PYoV25VLHakKy7oSyfRWQsK5ZbwNcrJ5 YLWqqPgm9J+NHzkdfs7opWF3x4zmcaSh/Fjv8wWtainvpvi2Hyw0ONIW6 r8WyhC4+ZGFABjQJk2UkBRpocWSnBbsNRpiuADIOMNaywUSo4qezClHkv M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjYKABXJEVCrRDoJ/2dsb2JhbABFqgaOIAOBEYEHgiABAQEDAQgKARcQPwUHAQMCCQ4BAgQBASgHGSMKCQgCBBMLF4dlBZsuoFCLT4EThWEDiE2FDJYWgWaCfw
X-IronPort-AV: E=Sophos;i="4.77,662,1336348800"; d="scan'208";a="53055992"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 26 Jul 2012 22:53:12 +0000
Received: from dwingWS ([10.21.78.151]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q6QMrCxS023604; Thu, 26 Jul 2012 22:53:12 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Jose Saldana'" <jsaldana@unizar.es>
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com> <004001cd6b1d$405442e0$c0fcc8a0$@unizar.es>
In-Reply-To: <004001cd6b1d$405442e0$c0fcc8a0$@unizar.es>
Date: Thu, 26 Jul 2012 15:53:12 -0700
Message-ID: <069901cd6b81$6f1bd2a0$4d5377e0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQGF+EuvFpZGZkinmlaOrA3LFBD+CZfKSBgQgADJBbA=
Content-Language: en-us
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 26 Jul 2012 22:53:13 -0000

> -----Original Message-----
> From: Jose Saldana [mailto:jsaldana@unizar.es]
> Sent: Thursday, July 26, 2012 3:56 AM
> To: 'Dan Wing'
> Cc: tcmtf@ietf.org
> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
> 
> Dan,
> 
> I don't know if I have really understood your question. Of course, I
> assume
> that a delay of some seconds is not important for certain sensor
> networks.
> But they don't need to signal that they are delay tolerant. I mean,
> they are
> assumed to be from the moment they are installed.

The device, doing the multiplexing, needs to know if the packets
belong to a delay-tolerant (sensor) endpoint or to a non-delay
tolerant endpoint.

If the device doing the multiplexing is also the gateway communicating
with the delay-tolerant (sensor) network, it certainly knows those
devices are delay-tolerant.   I believe that is your point.

My point is that if the device doing the multiplexing is not directly
connected to that network of delay-tolerant devices, it needs to 
somehow differentiate between the delay-tolerant devices and the non-
delay-tolerant -- by being signaled or by being configured.

In the future, I expect a mix of sensors on various networks that
are not traditional dedicated sensor networks (e.g., WiFi, 3G),
so relying on a gateway to that dedicated network may not always
be the way to know a device is delay tolerant.

-d

> Well, I think I should gather some information about typical examples
> of
> sensor networks (number of sensors, frequency of samples, packet size
> of the
> samples, etc), in order to calculate in which cases the bandwidth
> saving
> obtained with TCMTF can be interesting, and which "multiplexing period"
> should be used. I think that this could be a typical case in which
> multiplexing can be done by packet size instead of using a period. I
> mean,
> when you have almost 1500 bytes (or the MTU), you send a packet.
> 
> I don't know if I have answered your question,
> 
> Jose
> 
> -----Mensaje original-----
> De: Dan Wing [mailto:dwing@cisco.com]
> Enviado el: martes, 24 de julio de 2012 23:58
> Para: jsaldana@unizar.es
> CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
> 
> ...
> > Nevertheless, in order to get an idea of the savings, we should
> deploy
> > some calculations. Our research group has only done simulations for
> > VoIP and games. In this case, we should know:
> >
> >
> >
> > -          Number of sensors in a typical scenario.
> >
> > -          Packet size and used headers. If IPv6 is used, savings
> >            can be really big, since header compression is really
> >            good for it.
> >
> > -          Packets per second that a single sensor can generate.
> >
> >
> >
> > And of course, the gateway should be the place for multiplexing.
> > In this case, the flows only travel from sensors to data center.
> > Am I right?
> 
> I wonder if there is an easy way for the endpoints to signal that they
> are
> delay tolerant (to allow collecting ~5 seconds of little packets).
> 
> -d



From jsaldana@unizar.es  Fri Jul 27 02:44:32 2012
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 79DB221F860F for <tcmtf@ietfa.amsl.com>; Fri, 27 Jul 2012 02:44:32 -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 0sgFlGEHyiCi for <tcmtf@ietfa.amsl.com>; Fri, 27 Jul 2012 02:44:31 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 2FF5121F8602 for <tcmtf@ietf.org>; Fri, 27 Jul 2012 02:44:30 -0700 (PDT)
Received: from jsaldanapc (53.Red-81-32-18.dynamicIP.rima-tde.net [81.32.18.53]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id q6R9iHiG028575; Fri, 27 Jul 2012 11:44:18 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <gorry@erg.abdn.ac.uk>
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com>	<004001cd6b1d$405442e0$c0fcc8a0$@unizar.es>	<1A39DCC13AF3C14B83CD74124D4DCFC30BE31BC3@dlrexmbx02.intra.dlr.de> <001bb7e57832957423b38feafec85f1f.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <001bb7e57832957423b38feafec85f1f.squirrel@www.erg.abdn.ac.uk>
Date: Fri, 27 Jul 2012 11:44:19 +0200
Message-ID: <003601cd6bdc$65bcedb0$3136c910$@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: AQGF+EuvFpZGZkinmlaOrA3LFBD+CQDG7hgjAmcR2ZwBwTEJPpekSeDw
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, Tomaso.deCola@dlr.de, dwing@cisco.com
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 27 Jul 2012 09:44:32 -0000

Thanks, Gorry. Your point is interesting. Of course, an online game has =
a
delay limit of 100-125ms. So you cannot add more than 50ms. In the =
sensor
network you can add bigger delays, in the order of seconds.

In the current Section 1.4. of the draft we have included some scenarios =
of
application. We can add other ones, like the one of the "sensors". And =
yes,
we should take into account that the draft has to be general enough so =
as
not to limit its scope to a particular case.

Perhaps in the beginning of the Section we could say something like =
"This
draft can be useful for different scenarios. The common characteristics =
of
them are: small packets, long-term flows with the same origin and
destination, a number of flows sharing the same path. Some examples are =
the
next ones..."

And yes, we have to keep in mind the flexibility. Otherwise, the RFC =
will
lose a lot of strength.

Thanks for the idea, Gorry.

Jose=20

-----Mensaje original-----
De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
gorry@erg.abdn.ac.uk
Enviado el: jueves, 26 de julio de 2012 14:21
Para: Tomaso.deCola@dlr.de
CC: tcmtf@ietf.org; dwing@cisco.com; jsaldana@unizar.es
Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf


Maybe I can try - one of the concerns raised for the tunnel compression =
was
knowing the parameters that would be acceptable for a particular =
operator,
application, user or whatever. It seems to me that if you had a sensor
network then the tunnels would need to operate on different time scales =
for
aggregation of messages, e.g. compared to a on-line game?

So, if we need an Internet spec it needs to be general enough to be
desirable to operators/users to use, but may also need to be flexible =
enough
that it can reach a wide enough community of interest to =
develop/maintain
and then operate the new protocol framework.

Gorry

> I also agree with Jose. It is likely that at installation time, they=20
> are configured in  a way to collect a number of packets before=20
> actually processing them. Of course this very much depends on the=20
> specific application, for which delay tolerance could be critical.=20
> Another aspect or question is whether sensor data are collected=20
> through a dedicated network infrastructure or not. In the case sensors =

> data are distributed over a network  where other application data=20
> (still sensors or also other data flows) are multiplexed together,=20
> then delay fluctuation could be experienced. In this scenario, the=20
> tcmtf idea could also help to keep the delivery delay or the jitter=20
> within specific time intervals, so to allow the receiving application =
to
work finely.
>
> Regards,
>
> Tomaso
>
> ------------------------
> Deutsches Zentrum f=FCr Luft- und Raumfahrt (DLR) German Aerospace=20
> Center Institute of Communications und Navigation | Satellite Networks =

> | Oberpfaffenhofen | 82234 Wessling | Germany
>
> Tomaso de Cola, Ph.D.
> Telefon +49 8153 28-2156 | Telefax  +49 8153 28-2844 |=20
> tomaso.decola@dlr.de http://www.dlr.de/kn/institut/abteilungen/san
>
> -----Original Message-----
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =

> Of Jose Saldana
> Sent: Thursday, July 26, 2012 12:56 PM
> To: 'Dan Wing'
> Cc: tcmtf@ietf.org
> Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>
> Dan,
>
> I don't know if I have really understood your question. Of course, I=20
> assume that a delay of some seconds is not important for certain=20
> sensor networks.
> But they don't need to signal that they are delay tolerant. I mean,=20
> they are assumed to be from the moment they are installed.
>
> Well, I think I should gather some information about typical examples=20
> of sensor networks (number of sensors, frequency of samples, packet=20
> size of the samples, etc), in order to calculate in which cases the=20
> bandwidth saving obtained with TCMTF can be interesting, and which=20
> "multiplexing period"
> should be used. I think that this could be a typical case in which=20
> multiplexing can be done by packet size instead of using a period. I=20
> mean, when you have almost 1500 bytes (or the MTU), you send a packet.
>
> I don't know if I have answered your question,
>
> Jose
>
> -----Mensaje original-----
> De: Dan Wing [mailto:dwing@cisco.com]
> Enviado el: martes, 24 de julio de 2012 23:58
> Para: jsaldana@unizar.es
> CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>
> ...
>> Nevertheless, in order to get an idea of the savings, we should=20
>> deploy some calculations. Our research group has only done=20
>> simulations for VoIP and games. In this case, we should know:
>>
>>
>>
>> -          Number of sensors in a typical scenario.
>>
>> -          Packet size and used headers. If IPv6 is used, savings
>>            can be really big, since header compression is really
>>            good for it.
>>
>> -          Packets per second that a single sensor can generate.
>>
>>
>>
>> And of course, the gateway should be the place for multiplexing.
>> In this case, the flows only travel from sensors to data center.
>> Am I right?
>
> I wonder if there is an easy way for the endpoints to signal that they =

> are delay tolerant (to allow collecting ~5 seconds of little packets).
>
> -d
>
>
> _______________________________________________
> 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  Fri Jul 27 04:14:33 2012
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 4B40421F8645; Fri, 27 Jul 2012 04:14:33 -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 GWNxk-BulYGX; Fri, 27 Jul 2012 04:14:32 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5394421F84C5; Fri, 27 Jul 2012 04:14:32 -0700 (PDT)
Received: from jsaldanapc (53.Red-81-32-18.dynamicIP.rima-tde.net [81.32.18.53]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id q6RBELUC008674; Fri, 27 Jul 2012 13:14:21 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Dan Wing'" <dwing@cisco.com>
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com>	<004001cd6b1d$405442e0$c0fcc8a0$@unizar.es> <069901cd6b81$6f1bd2a0$4d5377e0$@com>
In-Reply-To: <069901cd6b81$6f1bd2a0$4d5377e0$@com>
Date: Fri, 27 Jul 2012 13:14:20 +0200
Message-ID: <004001cd6be8$f8e1e170$eaa5a450$@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: AQGF+EuvFpZGZkinmlaOrA3LFBD+CQDG7hgjAtHnKE2XrwGWUA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, tsvwg@ietf.org
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 27 Jul 2012 11:14:33 -0000

Well, perhaps a solution is the use of Diffserv bits: in the draft for
updating rfc4594
(https://datatracker.ietf.org/doc/draft-polk-tsvwg-rfc4594-update) there are
classes for real-time services and for best-effort ones. I have always
believed that the update of rfc4594 can be beneficial for TCMTF: you can
build a tunnel with flows belonging to the same traffic category.

But I don't know if the best-effort class means exactly the same as
delay-tolerant.

Dan, what do you think?

Thanks,

Jose

-----Mensaje original-----
De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de Dan
Wing
Enviado el: viernes, 27 de julio de 2012 0:53
Para: 'Jose Saldana'
CC: tcmtf@ietf.org
Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf

> -----Original Message-----
> From: Jose Saldana [mailto:jsaldana@unizar.es]
> Sent: Thursday, July 26, 2012 3:56 AM
> To: 'Dan Wing'
> Cc: tcmtf@ietf.org
> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
> 
> Dan,
> 
> I don't know if I have really understood your question. Of course, I 
> assume that a delay of some seconds is not important for certain 
> sensor networks.
> But they don't need to signal that they are delay tolerant. I mean, 
> they are assumed to be from the moment they are installed.

The device, doing the multiplexing, needs to know if the packets belong to a
delay-tolerant (sensor) endpoint or to a non-delay tolerant endpoint.

If the device doing the multiplexing is also the gateway communicating with
the delay-tolerant (sensor) network, it certainly knows those
devices are delay-tolerant.   I believe that is your point.

My point is that if the device doing the multiplexing is not directly
connected to that network of delay-tolerant devices, it needs to somehow
differentiate between the delay-tolerant devices and the non- delay-tolerant
-- by being signaled or by being configured.

In the future, I expect a mix of sensors on various networks that are not
traditional dedicated sensor networks (e.g., WiFi, 3G), so relying on a
gateway to that dedicated network may not always be the way to know a device
is delay tolerant.

-d

> Well, I think I should gather some information about typical examples 
> of sensor networks (number of sensors, frequency of samples, packet 
> size of the samples, etc), in order to calculate in which cases the 
> bandwidth saving obtained with TCMTF can be interesting, and which 
> "multiplexing period"
> should be used. I think that this could be a typical case in which 
> multiplexing can be done by packet size instead of using a period. I 
> mean, when you have almost 1500 bytes (or the MTU), you send a packet.
> 
> I don't know if I have answered your question,
> 
> Jose
> 
> -----Mensaje original-----
> De: Dan Wing [mailto:dwing@cisco.com]
> Enviado el: martes, 24 de julio de 2012 23:58
> Para: jsaldana@unizar.es
> CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
> 
> ...
> > Nevertheless, in order to get an idea of the savings, we should
> deploy
> > some calculations. Our research group has only done simulations for 
> > VoIP and games. In this case, we should know:
> >
> >
> >
> > -          Number of sensors in a typical scenario.
> >
> > -          Packet size and used headers. If IPv6 is used, savings
> >            can be really big, since header compression is really
> >            good for it.
> >
> > -          Packets per second that a single sensor can generate.
> >
> >
> >
> > And of course, the gateway should be the place for multiplexing.
> > In this case, the flows only travel from sensors to data center.
> > Am I right?
> 
> I wonder if there is an easy way for the endpoints to signal that they 
> are delay tolerant (to allow collecting ~5 seconds of little packets).
> 
> -d


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


From mns@tid.es  Fri Jul 27 04:38:44 2012
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 D84E921F8616; Fri, 27 Jul 2012 04:38:44 -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 ejv39tMsaHba; Fri, 27 Jul 2012 04:38:43 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 29F3421F8577; Fri, 27 Jul 2012 04:38:43 -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 <0M7T00CQVHOHTL@tid.hi.inet>; Fri, 27 Jul 2012 13:38:42 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id E8.D7.02752.1CD72105; Fri, 27 Jul 2012 13:38:41 +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 <0M7T00CQNHOHTL@tid.hi.inet>; Fri, 27 Jul 2012 13:38:41 +0200 (MEST)
Received: from [10.95.162.151] (10.95.64.115) by ex10-htcas3-mad.hi.inet (10.95.73.92) with Microsoft SMTP Server id 14.2.298.4; Fri, 27 Jul 2012 13:38:40 +0200
Date: Fri, 27 Jul 2012 13:40:19 +0200
From: Manuel <mns@tid.es>
In-reply-to: <004001cd6be8$f8e1e170$eaa5a450$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: Jose Saldana <jsaldana@unizar.es>
Message-id: <50127E23.1090509@tid.es>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
X-AuditID: 0a5f4e69-b7f6d6d000000ac0-2c-50127dc13ee0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDIsWRmVeSWpSXmKPExsXCFe9nqHuwVijA4MEJbYtdnzcwWhx7c5fN gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZa5+0shacNax4vv0RewPjOfUuRk4OIQFJiZMHLrGA 2BICJhIvpi9ggrDFJC7cW8/WxcgFVLOdUeLt2znMEM4zRolrO44xQjhLGCUmztjACNLCIqAq 0bHwOVg7G9DYK/fOsoHYwgIuEtcmvgOzOQUsJLpeHGGHWKEg8efcY7DVIkC9S8/+ButlFsiQ aFowixXiPBGJXZsmgdXwAtWsa/jGBGELSvyYfI8Fot5a4tS3lcwQtrbEk3cXwHpFBYIlHj/d A/XCVkaJA992MU5gFJmFpH8Wkv5ZSPoXMDKvYhQrTirKTM8oyU3MzEk3MNLLyNTLzEst2cQI CfrMHYzLd6ocYhTgYFTi4dXYJBggxJpYVlyZe4hRkoNJSZQ3plIoQIgvKT+lMiOxOCO+qDQn tfgQowQHs5II71dboBxvSmJlVWpRPkxKhoNDSYJ3VQ1QSrAoNT21Ii0zBxjbMGkmDk6Qdh6g 9gUgNbzFBYm5xZnpEPlTjJJS4rw7QBICIImM0jy43leM4kBHCvPeA8nyAJMQXNcroIFMQAMt osEGliQipKQaGPMfdlz+OePkVb8Jsk3/fYU5J98Qb4+NaP1of/eq6sONgg0tpyQvqmuace72 vLFDYdL9ySfNhKv4vYtFDh1X9dt1z+rbzLObDyS5ZSTv+399ySP7kx47XzGE732YppMjcdz3 /uNP35iV53WbF9hOvf4vfD1Pnf6O1ZMOv7M7e5klYdmRZWqa3mlKLMUZiYZazEXFiQBH71UZ /wIAAA==
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com> <004001cd6b1d$405442e0$c0fcc8a0$@unizar.es> <069901cd6b81$6f1bd2a0$4d5377e0$@com> <004001cd6be8$f8e1e170$eaa5a450$@unizar.es>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, 'Dan Wing' <dwing@cisco.com>
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mns@tid.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: Fri, 27 Jul 2012 11:38:45 -0000

       Hi,
Jose is too fast typing and I have had to modify my answer.   ;-)

There is an approach to solve that flexibility. If the packet is source
marked (DSCP or MPLS tag for example), the multiplexor could select
different behaviour as a function of that information.A method of
implementation would be to apply different processing queues depending
on the sensitivity of the delay of each flow marked.  If the packet is
not marked the default option is applied.
         A example of implementation is three queues with the following
values to add each packet ( < 10 mseg; 10-100 mseg; > 100 meg). In fact,
I am agreed with Jose and the "draft-polk-tsvwg-rfc4594-update" would be
define these different classes for RT and BE ones.
  The multiplexor introduce the received packet in the right queue in
function of its tag, and the multiplexor waits for the maximum time in
that queue new packets before it process that queue.
         However the multiplexor does not need to know these treatments,
and it only receives always the same type of packets.

         These solution introduce flexibility in any case and the
complexity is not tow much hight.

I hope this helps the discussion.

Manuel N=FA=F1ez

PD.: I have several ideas to refine the treatment and efficiency in the
queues, but I will explain them when they are more matured.

El 27/07/2012 13:14, Jose Saldana escribi=F3:
> Well, perhaps a solution is the use of Diffserv bits: in the draft for
> updating rfc4594
> (https://datatracker.ietf.org/doc/draft-polk-tsvwg-rfc4594-update) there =
are
> classes for real-time services and for best-effort ones. I have always
> believed that the update of rfc4594 can be beneficial for TCMTF: you can
> build a tunnel with flows belonging to the same traffic category.
>
> But I don't know if the best-effort class means exactly the same as
> delay-tolerant.
>
> Dan, what do you think?
>
> Thanks,
>
> Jose
>
> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de D=
an
> Wing
> Enviado el: viernes, 27 de julio de 2012 0:53
> Para: 'Jose Saldana'
> CC: tcmtf@ietf.org
> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>
>> -----Original Message-----
>> From: Jose Saldana [mailto:jsaldana@unizar.es]
>> Sent: Thursday, July 26, 2012 3:56 AM
>> To: 'Dan Wing'
>> Cc: tcmtf@ietf.org
>> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>
>> Dan,
>>
>> I don't know if I have really understood your question. Of course, I
>> assume that a delay of some seconds is not important for certain
>> sensor networks.
>> But they don't need to signal that they are delay tolerant. I mean,
>> they are assumed to be from the moment they are installed.
> The device, doing the multiplexing, needs to know if the packets belong t=
o a
> delay-tolerant (sensor) endpoint or to a non-delay tolerant endpoint.
>
> If the device doing the multiplexing is also the gateway communicating wi=
th
> the delay-tolerant (sensor) network, it certainly knows those
> devices are delay-tolerant.   I believe that is your point.
>
> My point is that if the device doing the multiplexing is not directly
> connected to that network of delay-tolerant devices, it needs to somehow
> differentiate between the delay-tolerant devices and the non- delay-toler=
ant
> -- by being signaled or by being configured.
>
> In the future, I expect a mix of sensors on various networks that are not
> traditional dedicated sensor networks (e.g., WiFi, 3G), so relying on a
> gateway to that dedicated network may not always be the way to know a dev=
ice
> is delay tolerant.
>
> -d
>
>> Well, I think I should gather some information about typical examples
>> of sensor networks (number of sensors, frequency of samples, packet
>> size of the samples, etc), in order to calculate in which cases the
>> bandwidth saving obtained with TCMTF can be interesting, and which
>> "multiplexing period"
>> should be used. I think that this could be a typical case in which
>> multiplexing can be done by packet size instead of using a period. I
>> mean, when you have almost 1500 bytes (or the MTU), you send a packet.
>>
>> I don't know if I have answered your question,
>>
>> Jose
>>
>> -----Mensaje original-----
>> De: Dan Wing [mailto:dwing@cisco.com]
>> Enviado el: martes, 24 de julio de 2012 23:58
>> Para: jsaldana@unizar.es
>> CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
>> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>
>> ...
>>> Nevertheless, in order to get an idea of the savings, we should
>> deploy
>>> some calculations. Our research group has only done simulations for
>>> VoIP and games. In this case, we should know:
>>>
>>>
>>>
>>> -          Number of sensors in a typical scenario.
>>>
>>> -          Packet size and used headers. If IPv6 is used, savings
>>>             can be really big, since header compression is really
>>>             good for it.
>>>
>>> -          Packets per second that a single sensor can generate.
>>>
>>>
>>>
>>> And of course, the gateway should be the place for multiplexing.
>>> In this case, the flows only travel from sensors to data center.
>>> Am I right?
>> I wonder if there is an easy way for the endpoints to signal that they
>> are delay tolerant (to allow collecting ~5 seconds of little packets).
>>
>> -d
>
> _______________________________________________
> 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
> .
>

--
Manuel N=FA=F1ez Sanz
Head of Network Automation & Dynamization
Telef=F3nica Global Resources
Address: C/ Don Ram=F3n de la Cruz 84. Madrid.
Phone: +34 629923641


________________________________

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 dwing@cisco.com  Fri Jul 27 09:26:32 2012
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 1144621F87AB; Fri, 27 Jul 2012 09:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.475
X-Spam-Level: 
X-Spam-Status: No, score=-110.475 tagged_above=-999 required=5 tests=[AWL=0.124, 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 65tdadz-aAls; Fri, 27 Jul 2012 09:26:31 -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 2EE2F21F8790; Fri, 27 Jul 2012 09:26:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=5192; q=dns/txt; s=iport; t=1343406391; x=1344615991; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=vwdKtfokZN7pAyaJfpsOSZBF7ub4chtiv1SMVORz7Dc=; b=bbmbiOYuS14aqfHYtjjyevtpRNNoA7TL2eATwKsjrgZUvuTtVr5Gl/bI cT291p9Pru35LnTf1HnBsk2dQXDxwrkFxVQJHjIocbuFmKTLX6MU1qHEh VGEEWJ3WT7wJfV7Kpp1D71VKKZSbuOjOGbcAMA3eIiNeXfI2mmkFPNFoJ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAMvAElCrRDoJ/2dsb2JhbABFqhKPM4EHgiABAQEDAQEBAQUKARcQNAsFBwEDAgkOAQIEAQEoBxkOFQoJCAIEEwsQB4dlBQyaGaBXBItQhnQDiE2FDJYWgWaCfw
X-IronPort-AV: E=Sophos;i="4.77,668,1336348800"; d="scan'208";a="50660769"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 27 Jul 2012 16:26:30 +0000
Received: from dwingWS (sjc-vpn3-605.cisco.com [10.21.66.93]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q6RGQUwa021272; Fri, 27 Jul 2012 16:26:30 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Jose Saldana'" <jsaldana@unizar.es>
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com>	<004001cd6b1d$405442e0$c0fcc8a0$@unizar.es> <069901cd6b81$6f1bd2a0$4d5377e0$@com> <004001cd6be8$f8e1e170$eaa5a450$@unizar.es>
In-Reply-To: <004001cd6be8$f8e1e170$eaa5a450$@unizar.es>
Date: Fri, 27 Jul 2012 09:26:30 -0700
Message-ID: <090e01cd6c14$943fd750$bcbf85f0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQGF+EuvFpZGZkinmlaOrA3LFBD+CQDG7hgjAtHnKE2XrwGWUIAAbaFA
Content-Language: en-us
Cc: tcmtf@ietf.org, tsvwg@ietf.org
Subject: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 27 Jul 2012 16:26:32 -0000

> -----Original Message-----
> From: Jose Saldana [mailto:jsaldana@unizar.es]
> Sent: Friday, July 27, 2012 4:14 AM
> To: 'Dan Wing'
> Cc: tcmtf@ietf.org; tsvwg@ietf.org
> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
> 
> Well, perhaps a solution is the use of Diffserv bits: in the draft for
> updating rfc4594
> (https://datatracker.ietf.org/doc/draft-polk-tsvwg-rfc4594-update)
> there are	
> classes for real-time services and for best-effort ones. I have always
> believed that the update of rfc4594 can be beneficial for TCMTF: you
> can
> build a tunnel with flows belonging to the same traffic category.
> 
> But I don't know if the best-effort class means exactly the same as
> delay-tolerant.
> 
> Dan, what do you think?

I agree that DSCP is the best tool we have to combine packets
with similar characteristics.  

A recurring problem with DSCP is they are re-written to different 
values because a router was configured to rewrite them all the
time or because a queue of that traffic class had built.  That
rewriting needs to be considered (or ignored) when grouping packets 
that are 'similar'.  IMO, the fact that a packet was in a queue
a few router hops away (and now has a different DSCP than
its friends) doesn't change that it should be grouped with all 
of its friends into a multiplexing tunnel.

-d


> Thanks,
> 
> Jose
> 
> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
> Dan
> Wing
> Enviado el: viernes, 27 de julio de 2012 0:53
> Para: 'Jose Saldana'
> CC: tcmtf@ietf.org
> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
> 
> > -----Original Message-----
> > From: Jose Saldana [mailto:jsaldana@unizar.es]
> > Sent: Thursday, July 26, 2012 3:56 AM
> > To: 'Dan Wing'
> > Cc: tcmtf@ietf.org
> > Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
> >
> > Dan,
> >
> > I don't know if I have really understood your question. Of course, I
> > assume that a delay of some seconds is not important for certain
> > sensor networks.
> > But they don't need to signal that they are delay tolerant. I mean,
> > they are assumed to be from the moment they are installed.
> 
> The device, doing the multiplexing, needs to know if the packets belong
> to a
> delay-tolerant (sensor) endpoint or to a non-delay tolerant endpoint.
> 
> If the device doing the multiplexing is also the gateway communicating
> with
> the delay-tolerant (sensor) network, it certainly knows those
> devices are delay-tolerant.   I believe that is your point.
> 
> My point is that if the device doing the multiplexing is not directly
> connected to that network of delay-tolerant devices, it needs to
> somehow
> differentiate between the delay-tolerant devices and the non- delay-
> tolerant
> -- by being signaled or by being configured.
> 
> In the future, I expect a mix of sensors on various networks that are
> not
> traditional dedicated sensor networks (e.g., WiFi, 3G), so relying on a
> gateway to that dedicated network may not always be the way to know a
> device
> is delay tolerant.
> 
> -d
> 
> > Well, I think I should gather some information about typical examples
> > of sensor networks (number of sensors, frequency of samples, packet
> > size of the samples, etc), in order to calculate in which cases the
> > bandwidth saving obtained with TCMTF can be interesting, and which
> > "multiplexing period"
> > should be used. I think that this could be a typical case in which
> > multiplexing can be done by packet size instead of using a period. I
> > mean, when you have almost 1500 bytes (or the MTU), you send a
> packet.
> >
> > I don't know if I have answered your question,
> >
> > Jose
> >
> > -----Mensaje original-----
> > De: Dan Wing [mailto:dwing@cisco.com]
> > Enviado el: martes, 24 de julio de 2012 23:58
> > Para: jsaldana@unizar.es
> > CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
> > Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
> >
> > ...
> > > Nevertheless, in order to get an idea of the savings, we should
> > deploy
> > > some calculations. Our research group has only done simulations for
> > > VoIP and games. In this case, we should know:
> > >
> > >
> > >
> > > -          Number of sensors in a typical scenario.
> > >
> > > -          Packet size and used headers. If IPv6 is used, savings
> > >            can be really big, since header compression is really
> > >            good for it.
> > >
> > > -          Packets per second that a single sensor can generate.
> > >
> > >
> > >
> > > And of course, the gateway should be the place for multiplexing.
> > > In this case, the flows only travel from sensors to data center.
> > > Am I right?
> >
> > I wonder if there is an easy way for the endpoints to signal that
> they
> > are delay tolerant (to allow collecting ~5 seconds of little
> packets).
> >
> > -d
> 
> 
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From Ruediger.Geib@telekom.de  Sun Jul 29 23:54:08 2012
Return-Path: <Ruediger.Geib@telekom.de>
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 6143C11E8129; Sun, 29 Jul 2012 23:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g3qcN6NaepEx; Sun, 29 Jul 2012 23:54:07 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id BD6C611E8120; Sun, 29 Jul 2012 23:54:03 -0700 (PDT)
Received: from he110890.emea1.cds.t-internal.com ([10.134.92.131]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 30 Jul 2012 08:54:00 +0200
Received: from HE111648.emea1.cds.t-internal.com ([10.134.93.17]) by he110890 ([10.134.92.131]) with mapi; Mon, 30 Jul 2012 08:54:00 +0200
From: <Ruediger.Geib@telekom.de>
To: <dwing@cisco.com>, <jsaldana@unizar.es>
Date: Mon, 30 Jul 2012 08:53:57 +0200
Thread-Topic: [tsvwg] [tcmtf]  M2M, WSNs and draft-saldana-tsvwg-tcmtf
Thread-Index: AQGF+EuvFpZGZkinmlaOrA3LFBD+CQDG7hgjAtHnKE2XrwGWUIAAbaFAgAQRaHA=
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D14DD2452CB@HE111648.emea1.cds.t-internal.com>
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com> <004001cd6b1d$405442e0$c0fcc8a0$@unizar.es> <069901cd6b81$6f1bd2a0$4d5377e0$@com> <004001cd6be8$f8e1e170$eaa5a450$@unizar.es> <090e01cd6c14$943fd750$bcbf85f0$@com>
In-Reply-To: <090e01cd6c14$943fd750$bcbf85f0$@com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 30 Jul 2012 00:35:46 -0700
Cc: tcmtf@ietf.org, tsvwg@ietf.org
Subject: Re: [tcmtf] [tsvwg]   M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 30 Jul 2012 06:54:08 -0000

Folks,

avoiding a DSCP rewrite at domain boundarys is probably
impossible - there are many independent DiffServ
deployments by now.

Al Morton will present some ITU work on the issue. We propose
to apply a small standardised set of domain behaviours (also
called QoS classes) at interconnection interfaces. The benefit
is a domain remarks tranmitted/received traffic to/from the
interdomain DSCPs. Every ISP needs to solve the interworking
issue once only and should expect a reasonable end to end QoS.

The proposal more tries to look at DiffServ router forwarding knobs:
a queuing mechanism and active queue management. My view is, these
can be optimised for an expected transport behaviour:

UDP traffic (streaming or telephony, real time gaming) will most
likely not be retransmitted. A short queue will do, active queue
management by random drops isn't required (unless you'd like
to apply PCN marking or the like).

TCP traffic interacts with router congestion indications, queues
may be a little bit deeper and active queue management may be
deployed. Today it is RED, ECN or the like in future.

If one looks at it from that angle, the number of useful
QoS classes is small.

Take the transport indication (TCP/UDP) as "dominating" in a
class, not a pureness requirement.

Regards

Ruediger



-----Original Message-----
From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of D=
an Wing
Sent: Friday, July 27, 2012 6:27 PM
To: 'Jose Saldana'
Cc: tcmtf@ietf.org; tsvwg@ietf.org
Subject: Re: [tsvwg] [tcmtf] M2M, WSNs and draft-saldana-tsvwg-tcmtf

> -----Original Message-----
> From: Jose Saldana [mailto:jsaldana@unizar.es]
> Sent: Friday, July 27, 2012 4:14 AM
> To: 'Dan Wing'
> Cc: tcmtf@ietf.org; tsvwg@ietf.org
> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>
> Well, perhaps a solution is the use of Diffserv bits: in the draft for
> updating rfc4594
> (https://datatracker.ietf.org/doc/draft-polk-tsvwg-rfc4594-update)
> there are
> classes for real-time services and for best-effort ones. I have always
> believed that the update of rfc4594 can be beneficial for TCMTF: you
> can
> build a tunnel with flows belonging to the same traffic category.
>
> But I don't know if the best-effort class means exactly the same as
> delay-tolerant.
>
> Dan, what do you think?

I agree that DSCP is the best tool we have to combine packets
with similar characteristics.

A recurring problem with DSCP is they are re-written to different
values because a router was configured to rewrite them all the
time or because a queue of that traffic class had built.  That
rewriting needs to be considered (or ignored) when grouping packets
that are 'similar'.  IMO, the fact that a packet was in a queue
a few router hops away (and now has a different DSCP than
its friends) doesn't change that it should be grouped with all
of its friends into a multiplexing tunnel.

-d


> Thanks,
>
> Jose
>
> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
> Dan
> Wing
> Enviado el: viernes, 27 de julio de 2012 0:53
> Para: 'Jose Saldana'
> CC: tcmtf@ietf.org
> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>
> > -----Original Message-----
> > From: Jose Saldana [mailto:jsaldana@unizar.es]
> > Sent: Thursday, July 26, 2012 3:56 AM
> > To: 'Dan Wing'
> > Cc: tcmtf@ietf.org
> > Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
> >
> > Dan,
> >
> > I don't know if I have really understood your question. Of course, I
> > assume that a delay of some seconds is not important for certain
> > sensor networks.
> > But they don't need to signal that they are delay tolerant. I mean,
> > they are assumed to be from the moment they are installed.
>
> The device, doing the multiplexing, needs to know if the packets belong
> to a
> delay-tolerant (sensor) endpoint or to a non-delay tolerant endpoint.
>
> If the device doing the multiplexing is also the gateway communicating
> with
> the delay-tolerant (sensor) network, it certainly knows those
> devices are delay-tolerant.   I believe that is your point.
>
> My point is that if the device doing the multiplexing is not directly
> connected to that network of delay-tolerant devices, it needs to
> somehow
> differentiate between the delay-tolerant devices and the non- delay-
> tolerant
> -- by being signaled or by being configured.
>
> In the future, I expect a mix of sensors on various networks that are
> not
> traditional dedicated sensor networks (e.g., WiFi, 3G), so relying on a
> gateway to that dedicated network may not always be the way to know a
> device
> is delay tolerant.
>
> -d
>
> > Well, I think I should gather some information about typical examples
> > of sensor networks (number of sensors, frequency of samples, packet
> > size of the samples, etc), in order to calculate in which cases the
> > bandwidth saving obtained with TCMTF can be interesting, and which
> > "multiplexing period"
> > should be used. I think that this could be a typical case in which
> > multiplexing can be done by packet size instead of using a period. I
> > mean, when you have almost 1500 bytes (or the MTU), you send a
> packet.
> >
> > I don't know if I have answered your question,
> >
> > Jose
> >
> > -----Mensaje original-----
> > De: Dan Wing [mailto:dwing@cisco.com]
> > Enviado el: martes, 24 de julio de 2012 23:58
> > Para: jsaldana@unizar.es
> > CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
> > Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
> >
> > ...
> > > Nevertheless, in order to get an idea of the savings, we should
> > deploy
> > > some calculations. Our research group has only done simulations for
> > > VoIP and games. In this case, we should know:
> > >
> > >
> > >
> > > -          Number of sensors in a typical scenario.
> > >
> > > -          Packet size and used headers. If IPv6 is used, savings
> > >            can be really big, since header compression is really
> > >            good for it.
> > >
> > > -          Packets per second that a single sensor can generate.
> > >
> > >
> > >
> > > And of course, the gateway should be the place for multiplexing.
> > > In this case, the flows only travel from sensors to data center.
> > > Am I right?
> >
> > I wonder if there is an easy way for the endpoints to signal that
> they
> > are delay tolerant (to allow collecting ~5 seconds of little
> packets).
> >
> > -d
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From brian.e.carpenter@gmail.com  Mon Jul 30 00:19:18 2012
Return-Path: <brian.e.carpenter@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 7958111E80A4; Mon, 30 Jul 2012 00:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.41
X-Spam-Level: 
X-Spam-Status: No, score=-101.41 tagged_above=-999 required=5 tests=[AWL=0.281, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 F4mUMB8+1HOI; Mon, 30 Jul 2012 00:19:17 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 10A5111E808A; Mon, 30 Jul 2012 00:19:16 -0700 (PDT)
Received: by eekb45 with SMTP id b45so1117637eek.31 for <multiple recipients>; Mon, 30 Jul 2012 00:19:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1NKbYac5TrNUq7OEmNFPPPX5cNeH25UiAhTRk8c/hjI=; b=vxQ9oIFu/t36Bbd6WinS10qkWsgb3GqZJU61Qy78rqic82HLMNg+rDEEguZpChEnRy qFlTSFNhMosFqSaE5nAeIc9VMjU0T1Vxd/KRwUclwrBw9mkWtjHIlmhxYUqU9Wgn4JrA aDypELswOXBm2IreUwFaZZnZWZ9aa8Lpu+agzsi6PI3rinU/sAt3HfKhbNbQ2G4go0pP ST6pg+u8r9EdiF0bMZ4AYi9NQkyi0/KdMuINxPNusQgpTdgt3PcQJs13A0kt8y5JQuMW Jjuyxd5u7rQSeKMG9JvM8Ys/3ejbBcJ9Sr6ZC849l5idUFdh9+/6B8aECDwvhyyXd094 k6vQ==
Received: by 10.14.204.72 with SMTP id g48mr4352451eeo.45.1343632756131; Mon, 30 Jul 2012 00:19:16 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-212.as13285.net. [2.102.216.212]) by mx.google.com with ESMTPS id s8sm25685455eeo.8.2012.07.30.00.19.13 (version=SSLv3 cipher=OTHER); Mon, 30 Jul 2012 00:19:15 -0700 (PDT)
Message-ID: <5016356C.6030400@gmail.com>
Date: Mon, 30 Jul 2012 08:19:08 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ruediger.Geib@telekom.de
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com>	<004001cd6b1d$405442e0$c0fcc8a0$@unizar.es>	<069901cd6b81$6f1bd2a0$4d5377e0$@com>	<004001cd6be8$f8e1e170$eaa5a450$@unizar.es>	<090e01cd6c14$943fd750$bcbf85f0$@com> <580BEA5E3B99744AB1F5BFF5E9A3C67D14DD2452CB@HE111648.emea1.cds.t-internal.com>
In-Reply-To: <580BEA5E3B99744AB1F5BFF5E9A3C67D14DD2452CB@HE111648.emea1.cds.t-internal.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 30 Jul 2012 00:35:46 -0700
Cc: tcmtf@ietf.org, tsvwg@ietf.org, dwing@cisco.com, jsaldana@unizar.es
Subject: Re: [tcmtf] [tsvwg]   M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 30 Jul 2012 07:19:18 -0000

On 30/07/2012 07:53, Ruediger.Geib@telekom.de wrote:
> Folks,
> 
> avoiding a DSCP rewrite at domain boundarys is probably
> impossible - there are many independent DiffServ
> deployments by now.
> 
> Al Morton will present some ITU work on the issue. We propose
> to apply a small standardised set of domain behaviours (also
> called QoS classes) at interconnection interfaces. The benefit
> is a domain remarks tranmitted/received traffic to/from the
> interdomain DSCPs. 

That assumes that you trust the diffserv markings applied by your
peer. In the general case, that seems unlikely, which is why there
is always likely to be a classifier as well as a re-marker at the
boundary, and quite possibly a traffic conditioner too.

Agreed, there might be a subset of peering relationships at which
you would be prepared to trust your neighbour's DSCPs. I thought
that was one intent behind RFC 4594 and its possible update.
We surely don't need *another* set of recommended traffic classes.

However, at a peering connection where you don't have that level of
trust, you have to either reclassify all packets or mark everything
as best effort.

Every ISP needs to solve the interworking
> issue once only and should expect a reasonable end to end QoS.
> 
> The proposal more tries to look at DiffServ router forwarding knobs:
> a queuing mechanism and active queue management. My view is, these
> can be optimised for an expected transport behaviour:
> 
> UDP traffic (streaming or telephony, real time gaming) will most
> likely not be retransmitted. A short queue will do, active queue
> management by random drops isn't required (unless you'd like
> to apply PCN marking or the like).
> 
> TCP traffic interacts with router congestion indications, queues
> may be a little bit deeper and active queue management may be
> deployed. Today it is RED, ECN or the like in future.

How do you help the alarming amount of traffic that is streaming over
TCP?

    Brian

> 
> If one looks at it from that angle, the number of useful
> QoS classes is small.
> 
> Take the transport indication (TCP/UDP) as "dominating" in a
> class, not a pureness requirement.
> 
> Regards
> 
> Ruediger
> 
> 
> 
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of Dan Wing
> Sent: Friday, July 27, 2012 6:27 PM
> To: 'Jose Saldana'
> Cc: tcmtf@ietf.org; tsvwg@ietf.org
> Subject: Re: [tsvwg] [tcmtf] M2M, WSNs and draft-saldana-tsvwg-tcmtf
> 
>> -----Original Message-----
>> From: Jose Saldana [mailto:jsaldana@unizar.es]
>> Sent: Friday, July 27, 2012 4:14 AM
>> To: 'Dan Wing'
>> Cc: tcmtf@ietf.org; tsvwg@ietf.org
>> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>
>> Well, perhaps a solution is the use of Diffserv bits: in the draft for
>> updating rfc4594
>> (https://datatracker.ietf.org/doc/draft-polk-tsvwg-rfc4594-update)
>> there are
>> classes for real-time services and for best-effort ones. I have always
>> believed that the update of rfc4594 can be beneficial for TCMTF: you
>> can
>> build a tunnel with flows belonging to the same traffic category.
>>
>> But I don't know if the best-effort class means exactly the same as
>> delay-tolerant.
>>
>> Dan, what do you think?
> 
> I agree that DSCP is the best tool we have to combine packets
> with similar characteristics.
> 
> A recurring problem with DSCP is they are re-written to different
> values because a router was configured to rewrite them all the
> time or because a queue of that traffic class had built.  That
> rewriting needs to be considered (or ignored) when grouping packets
> that are 'similar'.  IMO, the fact that a packet was in a queue
> a few router hops away (and now has a different DSCP than
> its friends) doesn't change that it should be grouped with all
> of its friends into a multiplexing tunnel.
> 
> -d
> 
> 
>> Thanks,
>>
>> Jose
>>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Dan
>> Wing
>> Enviado el: viernes, 27 de julio de 2012 0:53
>> Para: 'Jose Saldana'
>> CC: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>
>>> -----Original Message-----
>>> From: Jose Saldana [mailto:jsaldana@unizar.es]
>>> Sent: Thursday, July 26, 2012 3:56 AM
>>> To: 'Dan Wing'
>>> Cc: tcmtf@ietf.org
>>> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>>
>>> Dan,
>>>
>>> I don't know if I have really understood your question. Of course, I
>>> assume that a delay of some seconds is not important for certain
>>> sensor networks.
>>> But they don't need to signal that they are delay tolerant. I mean,
>>> they are assumed to be from the moment they are installed.
>> The device, doing the multiplexing, needs to know if the packets belong
>> to a
>> delay-tolerant (sensor) endpoint or to a non-delay tolerant endpoint.
>>
>> If the device doing the multiplexing is also the gateway communicating
>> with
>> the delay-tolerant (sensor) network, it certainly knows those
>> devices are delay-tolerant.   I believe that is your point.
>>
>> My point is that if the device doing the multiplexing is not directly
>> connected to that network of delay-tolerant devices, it needs to
>> somehow
>> differentiate between the delay-tolerant devices and the non- delay-
>> tolerant
>> -- by being signaled or by being configured.
>>
>> In the future, I expect a mix of sensors on various networks that are
>> not
>> traditional dedicated sensor networks (e.g., WiFi, 3G), so relying on a
>> gateway to that dedicated network may not always be the way to know a
>> device
>> is delay tolerant.
>>
>> -d
>>
>>> Well, I think I should gather some information about typical examples
>>> of sensor networks (number of sensors, frequency of samples, packet
>>> size of the samples, etc), in order to calculate in which cases the
>>> bandwidth saving obtained with TCMTF can be interesting, and which
>>> "multiplexing period"
>>> should be used. I think that this could be a typical case in which
>>> multiplexing can be done by packet size instead of using a period. I
>>> mean, when you have almost 1500 bytes (or the MTU), you send a
>> packet.
>>> I don't know if I have answered your question,
>>>
>>> Jose
>>>
>>> -----Mensaje original-----
>>> De: Dan Wing [mailto:dwing@cisco.com]
>>> Enviado el: martes, 24 de julio de 2012 23:58
>>> Para: jsaldana@unizar.es
>>> CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
>>> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>>
>>> ...
>>>> Nevertheless, in order to get an idea of the savings, we should
>>> deploy
>>>> some calculations. Our research group has only done simulations for
>>>> VoIP and games. In this case, we should know:
>>>>
>>>>
>>>>
>>>> -          Number of sensors in a typical scenario.
>>>>
>>>> -          Packet size and used headers. If IPv6 is used, savings
>>>>            can be really big, since header compression is really
>>>>            good for it.
>>>>
>>>> -          Packets per second that a single sensor can generate.
>>>>
>>>>
>>>>
>>>> And of course, the gateway should be the place for multiplexing.
>>>> In this case, the flows only travel from sensors to data center.
>>>> Am I right?
>>> I wonder if there is an easy way for the endpoints to signal that
>> they
>>> are delay tolerant (to allow collecting ~5 seconds of little
>> packets).
>>> -d
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
> 
> 

From jsaldana@unizar.es  Mon Jul 30 00:57:34 2012
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 E251021F86A2; Mon, 30 Jul 2012 00:57:34 -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 mrxuHm9GJn-x; Mon, 30 Jul 2012 00:57:33 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 31F8621F86A4; Mon, 30 Jul 2012 00:57:32 -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 q6U7vPXq012784; Mon, 30 Jul 2012 09:57:25 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>, <Ruediger.Geib@telekom.de>
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com>	<004001cd6b1d$405442e0$c0fcc8a0$@unizar.es>	<069901cd6b81$6f1bd2a0$4d5377e0$@com>	<004001cd6be8$f8e1e170$eaa5a450$@unizar.es>	<090e01cd6c14$943fd750$bcbf85f0$@com>	<580BEA5E3B99744AB1F5BFF5E9A3C67D14DD2452CB@HE111648.emea1.cds.t-internal.com> <5016356C.6030400@gmail.com>
In-Reply-To: <5016356C.6030400@gmail.com>
Date: Mon, 30 Jul 2012 09:57:25 +0200
Organization: Universidad de Zaragoza
Message-ID: <005201cd6e28$f68438a0$e38ca9e0$@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: AQGF+EuvFpZGZkinmlaOrA3LFBD+CQDG7hgjAtHnKE0AzSb+eAKtKsUWANcmoK8CBoLfLJeA1leQ
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, tsvwg@ietf.org, dwing@cisco.com
Subject: Re: [tcmtf] [tsvwg]   M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 30 Jul 2012 07:57:35 -0000

Another question: Brian talks about streaming over TCP (e.g. Youtube). This
is non-interactive traffic, since the client can do buffering an wait some
(short) time. But in addition, there are real-time interactive services
using TCP.

For example, World of Warcraft and almost every MMORPG game uses TCP. And
they are real-time interactive services: a player has to fight against other
players or against the "machine", and delay matters (every single player can
confirm this). Our research group has studied this issue, and also the
coexistence of real-time and best-effort TCP flows in a paper that is being
presented today in ICCCN Munchen: "The Effect of TCP Variants on the
Coexistence of MMORPG and Best-Effort Traffic"
(http://diec.unizar.es/~jsaldana/personal/hurry_NIME_2012_in_proc.pdf)

These games are becoming more and more popular. World of Warcraft has 10
million players. And gamers are really difficult clients to delay with. You
can have a look to this presentation (especially slide 5):
http://diec.unizar.es/~jsaldana/personal/sergei_SPECTS_2012_presentation.pdf

The only thing I want to remark with this e-mail is that TCP and best-effort
are not the same. It may sound weird, but real-time interactive TCP services
do exist, and they work every day with a lot of clients. We cannot forget
this when thinking about traffic classification.

Best regards and thank you for your feedback,

Jose

-----Mensaje original-----
De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
Brian E Carpenter
Enviado el: lunes, 30 de julio de 2012 9:19
Para: Ruediger.Geib@telekom.de
CC: tcmtf@ietf.org; tsvwg@ietf.org; dwing@cisco.com; jsaldana@unizar.es
Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf

On 30/07/2012 07:53, Ruediger.Geib@telekom.de wrote:
> Folks,
> 
> avoiding a DSCP rewrite at domain boundarys is probably impossible - 
> there are many independent DiffServ deployments by now.
> 
> Al Morton will present some ITU work on the issue. We propose to apply 
> a small standardised set of domain behaviours (also called QoS 
> classes) at interconnection interfaces. The benefit is a domain 
> remarks tranmitted/received traffic to/from the interdomain DSCPs.

That assumes that you trust the diffserv markings applied by your peer. In
the general case, that seems unlikely, which is why there is always likely
to be a classifier as well as a re-marker at the boundary, and quite
possibly a traffic conditioner too.

Agreed, there might be a subset of peering relationships at which you would
be prepared to trust your neighbour's DSCPs. I thought that was one intent
behind RFC 4594 and its possible update.
We surely don't need *another* set of recommended traffic classes.

However, at a peering connection where you don't have that level of trust,
you have to either reclassify all packets or mark everything as best effort.

Every ISP needs to solve the interworking
> issue once only and should expect a reasonable end to end QoS.
> 
> The proposal more tries to look at DiffServ router forwarding knobs:
> a queuing mechanism and active queue management. My view is, these can 
> be optimised for an expected transport behaviour:
> 
> UDP traffic (streaming or telephony, real time gaming) will most 
> likely not be retransmitted. A short queue will do, active queue 
> management by random drops isn't required (unless you'd like to apply 
> PCN marking or the like).
> 
> TCP traffic interacts with router congestion indications, queues may 
> be a little bit deeper and active queue management may be deployed. 
> Today it is RED, ECN or the like in future.

How do you help the alarming amount of traffic that is streaming over TCP?

    Brian

> 
> If one looks at it from that angle, the number of useful QoS classes 
> is small.
> 
> Take the transport indication (TCP/UDP) as "dominating" in a class, 
> not a pureness requirement.
> 
> Regards
> 
> Ruediger
> 
> 
> 
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf 
> Of Dan Wing
> Sent: Friday, July 27, 2012 6:27 PM
> To: 'Jose Saldana'
> Cc: tcmtf@ietf.org; tsvwg@ietf.org
> Subject: Re: [tsvwg] [tcmtf] M2M, WSNs and draft-saldana-tsvwg-tcmtf
> 
>> -----Original Message-----
>> From: Jose Saldana [mailto:jsaldana@unizar.es]
>> Sent: Friday, July 27, 2012 4:14 AM
>> To: 'Dan Wing'
>> Cc: tcmtf@ietf.org; tsvwg@ietf.org
>> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>
>> Well, perhaps a solution is the use of Diffserv bits: in the draft 
>> for updating rfc4594
>> (https://datatracker.ietf.org/doc/draft-polk-tsvwg-rfc4594-update)
>> there are
>> classes for real-time services and for best-effort ones. I have 
>> always believed that the update of rfc4594 can be beneficial for 
>> TCMTF: you can build a tunnel with flows belonging to the same 
>> traffic category.
>>
>> But I don't know if the best-effort class means exactly the same as 
>> delay-tolerant.
>>
>> Dan, what do you think?
> 
> I agree that DSCP is the best tool we have to combine packets with 
> similar characteristics.
> 
> A recurring problem with DSCP is they are re-written to different 
> values because a router was configured to rewrite them all the time or 
> because a queue of that traffic class had built.  That rewriting needs 
> to be considered (or ignored) when grouping packets that are 
> 'similar'.  IMO, the fact that a packet was in a queue a few router 
> hops away (and now has a different DSCP than its friends) doesn't 
> change that it should be grouped with all of its friends into a 
> multiplexing tunnel.
> 
> -d
> 
> 
>> Thanks,
>>
>> Jose
>>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre 
>> de Dan Wing Enviado el: viernes, 27 de julio de 2012 0:53
>> Para: 'Jose Saldana'
>> CC: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>
>>> -----Original Message-----
>>> From: Jose Saldana [mailto:jsaldana@unizar.es]
>>> Sent: Thursday, July 26, 2012 3:56 AM
>>> To: 'Dan Wing'
>>> Cc: tcmtf@ietf.org
>>> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>>
>>> Dan,
>>>
>>> I don't know if I have really understood your question. Of course, I 
>>> assume that a delay of some seconds is not important for certain 
>>> sensor networks.
>>> But they don't need to signal that they are delay tolerant. I mean, 
>>> they are assumed to be from the moment they are installed.
>> The device, doing the multiplexing, needs to know if the packets 
>> belong to a delay-tolerant (sensor) endpoint or to a non-delay 
>> tolerant endpoint.
>>
>> If the device doing the multiplexing is also the gateway 
>> communicating with the delay-tolerant (sensor) network, it certainly 
>> knows those
>> devices are delay-tolerant.   I believe that is your point.
>>
>> My point is that if the device doing the multiplexing is not directly 
>> connected to that network of delay-tolerant devices, it needs to 
>> somehow differentiate between the delay-tolerant devices and the non- 
>> delay- tolerant
>> -- by being signaled or by being configured.
>>
>> In the future, I expect a mix of sensors on various networks that are 
>> not traditional dedicated sensor networks (e.g., WiFi, 3G), so 
>> relying on a gateway to that dedicated network may not always be the 
>> way to know a device is delay tolerant.
>>
>> -d
>>
>>> Well, I think I should gather some information about typical 
>>> examples of sensor networks (number of sensors, frequency of 
>>> samples, packet size of the samples, etc), in order to calculate in 
>>> which cases the bandwidth saving obtained with TCMTF can be 
>>> interesting, and which "multiplexing period"
>>> should be used. I think that this could be a typical case in which 
>>> multiplexing can be done by packet size instead of using a period. I 
>>> mean, when you have almost 1500 bytes (or the MTU), you send a
>> packet.
>>> I don't know if I have answered your question,
>>>
>>> Jose
>>>
>>> -----Mensaje original-----
>>> De: Dan Wing [mailto:dwing@cisco.com] Enviado el: martes, 24 de 
>>> julio de 2012 23:58
>>> Para: jsaldana@unizar.es
>>> CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
>>> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>>
>>> ...
>>>> Nevertheless, in order to get an idea of the savings, we should
>>> deploy
>>>> some calculations. Our research group has only done simulations for 
>>>> VoIP and games. In this case, we should know:
>>>>
>>>>
>>>>
>>>> -          Number of sensors in a typical scenario.
>>>>
>>>> -          Packet size and used headers. If IPv6 is used, savings
>>>>            can be really big, since header compression is really
>>>>            good for it.
>>>>
>>>> -          Packets per second that a single sensor can generate.
>>>>
>>>>
>>>>
>>>> And of course, the gateway should be the place for multiplexing.
>>>> In this case, the flows only travel from sensors to data center.
>>>> Am I right?
>>> I wonder if there is an easy way for the endpoints to signal that
>> they
>>> are delay tolerant (to allow collecting ~5 seconds of little
>> packets).
>>> -d
>>
>> _______________________________________________
>> 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 30 01:33:58 2012
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 1C4C021F86C6 for <tcmtf@ietfa.amsl.com>; Mon, 30 Jul 2012 01:33:58 -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 jwoQtet+pnWI for <tcmtf@ietfa.amsl.com>; Mon, 30 Jul 2012 01:33:57 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id D1D2521F8732 for <tcmtf@ietf.org>; Mon, 30 Jul 2012 01:33:56 -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 q6U8Xo0K025090 for <tcmtf@ietf.org>; Mon, 30 Jul 2012 10:33:51 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Mon, 30 Jul 2012 10:33:54 +0200
Organization: Universidad de Zaragoza
Message-ID: <008901cd6e2e$0e372b60$2aa58220$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_008A_01CD6E3E.D1C07090"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1uLgBC4hGMTQAtRyizpGuwfSZl8g==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] Article about TCMTF: Shooting around the corner
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, 30 Jul 2012 08:33:58 -0000

This is a multipart message in MIME format.

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

This is to let you know that an article about TCMTF has appeared in the last
number of the IETF Journal, which is being distributed to IETF84 attendees
in Vancouver:

 

 
<http://www.internetsociety.org/sites/default/files/pub-IETFJv8.1-20120702-e
n-.pdf>
http://www.internetsociety.org/sites/default/files/pub-IETFJv8.1-20120702-en
-.pdf, page 20

 
<http://www.internetsociety.org/articles/shooting-around-corner-problem-real
-time-services>
http://www.internetsociety.org/articles/shooting-around-corner-problem-real-
time-services

 

I think this is good news, since I hope this article will attract more
attention (and perhaps more work) to the mailing list and the draft.

 

Best regards,

 

Jose Saldana

 

 


------=_NextPart_000_008A_01CD6E3E.D1C07090
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><span =
lang=3DEN-US>This is to let you know that an article about TCMTF has =
appeared in the last number of the IETF Journal, which is being =
distributed to IETF84 attendees in Vancouver:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><a =
href=3D"http://www.internetsociety.org/sites/default/files/pub-IETFJv8.1-=
20120702-en-.pdf"><span =
lang=3DEN-US>http://www.internetsociety.org/sites/default/files/pub-IETFJ=
v8.1-20120702-en-.pdf</span></a><span lang=3DEN-US>, page =
20<o:p></o:p></span></p><p class=3DMsoNormal><a =
href=3D"http://www.internetsociety.org/articles/shooting-around-corner-pr=
oblem-real-time-services"><span =
lang=3DEN-US>http://www.internetsociety.org/articles/shooting-around-corn=
er-problem-real-time-services</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>I think this is good news, since I hope this article will =
attract more attention (and perhaps more work) to the mailing list and =
the 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>Best regards,<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'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'>Jose Saldana</span><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_008A_01CD6E3E.D1C07090--


From Ruediger.Geib@telekom.de  Mon Jul 30 01:45:00 2012
Return-Path: <Ruediger.Geib@telekom.de>
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 EEDDD21F84C4; Mon, 30 Jul 2012 01:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vr3BfNOt65LZ; Mon, 30 Jul 2012 01:45:00 -0700 (PDT)
Received: from tcmail83.telekom.de (tcmail83.telekom.de [62.225.183.131]) by ietfa.amsl.com (Postfix) with ESMTP id E29F821F843A; Mon, 30 Jul 2012 01:44:58 -0700 (PDT)
Received: from he113472.emea1.cds.t-internal.com ([10.134.93.130]) by tcmail81.telekom.de with ESMTP/TLS/AES128-SHA; 30 Jul 2012 10:44:56 +0200
Received: from HE111648.emea1.cds.t-internal.com ([10.134.93.17]) by HE113472.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 30 Jul 2012 10:44:55 +0200
From: <Ruediger.Geib@telekom.de>
To: <brian.e.carpenter@gmail.com>
Date: Mon, 30 Jul 2012 10:44:54 +0200
Thread-Topic: [tsvwg] [tcmtf]  M2M, WSNs and draft-saldana-tsvwg-tcmtf
Thread-Index: Ac1uI6Fy1+mHQqknT0GP6HB5TMjaowABXzNA
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D14DD245513@HE111648.emea1.cds.t-internal.com>
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com> <004001cd6b1d$405442e0$c0fcc8a0$@unizar.es> <069901cd6b81$6f1bd2a0$4d5377e0$@com> <004001cd6be8$f8e1e170$eaa5a450$@unizar.es> <090e01cd6c14$943fd750$bcbf85f0$@com> <580BEA5E3B99744AB1F5BFF5E9A3C67D14DD2452CB@HE111648.emea1.cds.t-internal.com> <5016356C.6030400@gmail.com>
In-Reply-To: <5016356C.6030400@gmail.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tcmtf@ietf.org, tsvwg@ietf.org
Subject: Re: [tcmtf] [tsvwg]   M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 30 Jul 2012 08:45:01 -0000

Brian,

a two parts response:

QoS interconnection isn't free of charges. The philosphy I am
aware of is "sending party pays". It's a sender incentive
then to ensure the traffic is marked as desired.

Traffic using TCP transport should use a QoS class optimised
for TCP transport, I'd suggest. A recurring issue during
standardisation and interconnection discussion with network
engineers is to avoid to name QoS classes by applications.
The point is to look at the required QoS properties. Transport
seems to be reasonably abstract.

Another issue: QoS means to avoid congestion (this is
not CoS, meaning "survive longer"). Under foreseeable
operational conditions, all QoS classes experience similar
forwarding (no drops and low delay/jitter).

That's why I also don't favour approaches starting from
an application and ending with a new required QoS class.
Where's the experience with the deployed classes
justifying this way of engineering?

The more basic part of your statement:

I agree, we don't need *another* set of classes. You, James and
I just don't agree on which are the ones we don't need. The
set I propopse is rather abstract. I didn't up to now catch a
single line telling me why this set of classes isn't useful.
Instead you say that you prefer a small set as I propose but
then you support James class/codepoint overspecification.
Too many classes, codepoints and standards around them
are part of the problem, they are not part of the solution.

To be precise: Interconnection agreements are simple regarding
the EF and the Best Effort class. They are work intensive
for AF based classes. Do you have an idea what could be
the cause?

No standards body besides IETF works with these many
codepoints and classes. Even if they propose pure IP
interconnections. But (obviously) each standard body
picks another subset and some of them interpret IETF AF
standards rather creative. Yes, DiffServ is flexible enough
to deal with that. Administration, operation and
interconnection negotiation however benefit if there's a
standard behviour, used by a majority of all customers and
by tailored adaptions used by a few.

Regards,

Ruediger


On 30/07/2012 07:53, Ruediger.Geib@telekom.de wrote:
> Folks,
>
> avoiding a DSCP rewrite at domain boundarys is probably
> impossible - there are many independent DiffServ
> deployments by now.
>
> Al Morton will present some ITU work on the issue. We propose
> to apply a small standardised set of domain behaviours (also
> called QoS classes) at interconnection interfaces. The benefit
> is a domain remarks tranmitted/received traffic to/from the
> interdomain DSCPs.

That assumes that you trust the diffserv markings applied by your
peer. In the general case, that seems unlikely, which is why there
is always likely to be a classifier as well as a re-marker at the
boundary, and quite possibly a traffic conditioner too.

Agreed, there might be a subset of peering relationships at which
you would be prepared to trust your neighbour's DSCPs. I thought
that was one intent behind RFC 4594 and its possible update.
We surely don't need *another* set of recommended traffic classes.

However, at a peering connection where you don't have that level of
trust, you have to either reclassify all packets or mark everything
as best effort.

Every ISP needs to solve the interworking
> issue once only and should expect a reasonable end to end QoS.
>
> The proposal more tries to look at DiffServ router forwarding knobs:
> a queuing mechanism and active queue management. My view is, these
> can be optimised for an expected transport behaviour:
>
> UDP traffic (streaming or telephony, real time gaming) will most
> likely not be retransmitted. A short queue will do, active queue
> management by random drops isn't required (unless you'd like
> to apply PCN marking or the like).
>
> TCP traffic interacts with router congestion indications, queues
> may be a little bit deeper and active queue management may be
> deployed. Today it is RED, ECN or the like in future.

How do you help the alarming amount of traffic that is streaming over
TCP?

    Brian

>
> If one looks at it from that angle, the number of useful
> QoS classes is small.
>
> Take the transport indication (TCP/UDP) as "dominating" in a
> class, not a pureness requirement.
>
> Regards
>
> Ruediger
>
>
>
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of=
 Dan Wing
> Sent: Friday, July 27, 2012 6:27 PM
> To: 'Jose Saldana'
> Cc: tcmtf@ietf.org; tsvwg@ietf.org
> Subject: Re: [tsvwg] [tcmtf] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>
>> -----Original Message-----
>> From: Jose Saldana [mailto:jsaldana@unizar.es]
>> Sent: Friday, July 27, 2012 4:14 AM
>> To: 'Dan Wing'
>> Cc: tcmtf@ietf.org; tsvwg@ietf.org
>> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>
>> Well, perhaps a solution is the use of Diffserv bits: in the draft for
>> updating rfc4594
>> (https://datatracker.ietf.org/doc/draft-polk-tsvwg-rfc4594-update)
>> there are
>> classes for real-time services and for best-effort ones. I have always
>> believed that the update of rfc4594 can be beneficial for TCMTF: you
>> can
>> build a tunnel with flows belonging to the same traffic category.
>>
>> But I don't know if the best-effort class means exactly the same as
>> delay-tolerant.
>>
>> Dan, what do you think?
>
> I agree that DSCP is the best tool we have to combine packets
> with similar characteristics.
>
> A recurring problem with DSCP is they are re-written to different
> values because a router was configured to rewrite them all the
> time or because a queue of that traffic class had built.  That
> rewriting needs to be considered (or ignored) when grouping packets
> that are 'similar'.  IMO, the fact that a packet was in a queue
> a few router hops away (and now has a different DSCP than
> its friends) doesn't change that it should be grouped with all
> of its friends into a multiplexing tunnel.
>
> -d
>
>
>> Thanks,
>>
>> Jose
>>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Dan
>> Wing
>> Enviado el: viernes, 27 de julio de 2012 0:53
>> Para: 'Jose Saldana'
>> CC: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>
>>> -----Original Message-----
>>> From: Jose Saldana [mailto:jsaldana@unizar.es]
>>> Sent: Thursday, July 26, 2012 3:56 AM
>>> To: 'Dan Wing'
>>> Cc: tcmtf@ietf.org
>>> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>>
>>> Dan,
>>>
>>> I don't know if I have really understood your question. Of course, I
>>> assume that a delay of some seconds is not important for certain
>>> sensor networks.
>>> But they don't need to signal that they are delay tolerant. I mean,
>>> they are assumed to be from the moment they are installed.
>> The device, doing the multiplexing, needs to know if the packets belong
>> to a
>> delay-tolerant (sensor) endpoint or to a non-delay tolerant endpoint.
>>
>> If the device doing the multiplexing is also the gateway communicating
>> with
>> the delay-tolerant (sensor) network, it certainly knows those
>> devices are delay-tolerant.   I believe that is your point.
>>
>> My point is that if the device doing the multiplexing is not directly
>> connected to that network of delay-tolerant devices, it needs to
>> somehow
>> differentiate between the delay-tolerant devices and the non- delay-
>> tolerant
>> -- by being signaled or by being configured.
>>
>> In the future, I expect a mix of sensors on various networks that are
>> not
>> traditional dedicated sensor networks (e.g., WiFi, 3G), so relying on a
>> gateway to that dedicated network may not always be the way to know a
>> device
>> is delay tolerant.
>>
>> -d
>>
>>> Well, I think I should gather some information about typical examples
>>> of sensor networks (number of sensors, frequency of samples, packet
>>> size of the samples, etc), in order to calculate in which cases the
>>> bandwidth saving obtained with TCMTF can be interesting, and which
>>> "multiplexing period"
>>> should be used. I think that this could be a typical case in which
>>> multiplexing can be done by packet size instead of using a period. I
>>> mean, when you have almost 1500 bytes (or the MTU), you send a
>> packet.
>>> I don't know if I have answered your question,
>>>
>>> Jose
>>>
>>> -----Mensaje original-----
>>> De: Dan Wing [mailto:dwing@cisco.com]
>>> Enviado el: martes, 24 de julio de 2012 23:58
>>> Para: jsaldana@unizar.es
>>> CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
>>> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>>
>>> ...
>>>> Nevertheless, in order to get an idea of the savings, we should
>>> deploy
>>>> some calculations. Our research group has only done simulations for
>>>> VoIP and games. In this case, we should know:
>>>>
>>>>
>>>>
>>>> -          Number of sensors in a typical scenario.
>>>>
>>>> -          Packet size and used headers. If IPv6 is used, savings
>>>>            can be really big, since header compression is really
>>>>            good for it.
>>>>
>>>> -          Packets per second that a single sensor can generate.
>>>>
>>>>
>>>>
>>>> And of course, the gateway should be the place for multiplexing.
>>>> In this case, the flows only travel from sensors to data center.
>>>> Am I right?
>>> I wonder if there is an easy way for the endpoints to signal that
>> they
>>> are delay tolerant (to allow collecting ~5 seconds of little
>> packets).
>>> -d
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>
>

From Ruediger.Geib@telekom.de  Mon Jul 30 03:18:28 2012
Return-Path: <Ruediger.Geib@telekom.de>
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 CC38021F8769; Mon, 30 Jul 2012 03:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0eZV4CrJGKRx; Mon, 30 Jul 2012 03:18:27 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id 9AFC621F876C; Mon, 30 Jul 2012 03:18:26 -0700 (PDT)
Received: from he111631.emea1.cds.t-internal.com ([10.134.93.23]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 30 Jul 2012 12:18:25 +0200
Received: from HE111648.emea1.cds.t-internal.com ([10.134.93.17]) by HE111631.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 30 Jul 2012 12:18:19 +0200
From: <Ruediger.Geib@telekom.de>
To: <jsaldana@unizar.es>
Date: Mon, 30 Jul 2012 12:18:18 +0200
Thread-Topic: [tcmtf] [tsvwg]   M2M, WSNs and draft-saldana-tsvwg-tcmtf
Thread-Index: AQGF+EuvFpZGZkinmlaOrA3LFBD+CQDG7hgjAtHnKE0AzSb+eAKtKsUWANcmoK8CBoLfLJeA1leQgAAVtDA=
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D14DD2456F9@HE111648.emea1.cds.t-internal.com>
References: <03ee01cd69e7$649942e0$2dcbc8a0$@com> <004001cd6b1d$405442e0$c0fcc8a0$@unizar.es> <069901cd6b81$6f1bd2a0$4d5377e0$@com> <004001cd6be8$f8e1e170$eaa5a450$@unizar.es> <090e01cd6c14$943fd750$bcbf85f0$@com> <580BEA5E3B99744AB1F5BFF5E9A3C67D14DD2452CB@HE111648.emea1.cds.t-internal.com> <5016356C.6030400@gmail.com> <005201cd6e28$f68438a0$e38ca9e0$@unizar.es>
In-Reply-To: <005201cd6e28$f68438a0$e38ca9e0$@unizar.es>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tcmtf@ietf.org, tsvwg@ietf.org
Subject: Re: [tcmtf] [tsvwg]   M2M, WSNs and draft-saldana-tsvwg-tcmtf
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, 30 Jul 2012 10:18:28 -0000

Jose,

thanks. Sure, application developers hack around the transport
services they find and it is amazing what they can deliver
withhout QoS. And there are fair arguments why to use TCP
for everything.

By DiffServ alone, one doesn't change the routing path of
a packet. Hence in a congestion free network, the DiffServ
supported packet is at best slightly faster then the
BE packet (that's far less than 1 ms). The RTT remains
the same then.

QoS aware routing could offer more. I'm taking this thread
as a DiffServ thread, not a QoS aware routing thread. No
discussion on QoS routing then.

Under congestion, the player suffers a longer delay and
may experience packet drops. QoS transport of whatever
kind may help to avoid that. But DiffServ doesn't provide
more bandwidth. It defines how the available bandwidth
is shared. If there's a bottleneck in your architecture,
it will remain a bottleneck, also if you deploy DiffServ.
If there's non gaming background traffic which can deal
with congestion, DiffServ could be of use.

Be relaxed on the suitable class. QoS means that under
foreseeable conditions, no congestion should occur.
Queues/classes are optimised for a certain behaviour
in unlikely cases. The SLA QoS descriptions don't tell
you what's your daily experience. A QoS class optimised
for TCP traffic may well do.

Regards,

Ruediger



-----Original Message-----
From: Jose Saldana [mailto:jsaldana@unizar.es]
Sent: Monday, July 30, 2012 9:57 AM
To: 'Brian E Carpenter'; Geib, R=FCdiger
Cc: tcmtf@ietf.org; tsvwg@ietf.org; dwing@cisco.com
Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf

Another question: Brian talks about streaming over TCP (e.g. Youtube). This
is non-interactive traffic, since the client can do buffering an wait some
(short) time. But in addition, there are real-time interactive services
using TCP.

For example, World of Warcraft and almost every MMORPG game uses TCP. And
they are real-time interactive services: a player has to fight against othe=
r
players or against the "machine", and delay matters (every single player ca=
n
confirm this). Our research group has studied this issue, and also the
coexistence of real-time and best-effort TCP flows in a paper that is being
presented today in ICCCN Munchen: "The Effect of TCP Variants on the
Coexistence of MMORPG and Best-Effort Traffic"
(http://diec.unizar.es/~jsaldana/personal/hurry_NIME_2012_in_proc.pdf)

These games are becoming more and more popular. World of Warcraft has 10
million players. And gamers are really difficult clients to delay with. You
can have a look to this presentation (especially slide 5):
http://diec.unizar.es/~jsaldana/personal/sergei_SPECTS_2012_presentation.pd=
f

The only thing I want to remark with this e-mail is that TCP and best-effor=
t
are not the same. It may sound weird, but real-time interactive TCP service=
s
do exist, and they work every day with a lot of clients. We cannot forget
this when thinking about traffic classification.

Best regards and thank you for your feedback,

Jose

-----Mensaje original-----
De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
Brian E Carpenter
Enviado el: lunes, 30 de julio de 2012 9:19
Para: Ruediger.Geib@telekom.de
CC: tcmtf@ietf.org; tsvwg@ietf.org; dwing@cisco.com; jsaldana@unizar.es
Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf

On 30/07/2012 07:53, Ruediger.Geib@telekom.de wrote:
> Folks,
>
> avoiding a DSCP rewrite at domain boundarys is probably impossible -
> there are many independent DiffServ deployments by now.
>
> Al Morton will present some ITU work on the issue. We propose to apply
> a small standardised set of domain behaviours (also called QoS
> classes) at interconnection interfaces. The benefit is a domain
> remarks tranmitted/received traffic to/from the interdomain DSCPs.

That assumes that you trust the diffserv markings applied by your peer. In
the general case, that seems unlikely, which is why there is always likely
to be a classifier as well as a re-marker at the boundary, and quite
possibly a traffic conditioner too.

Agreed, there might be a subset of peering relationships at which you would
be prepared to trust your neighbour's DSCPs. I thought that was one intent
behind RFC 4594 and its possible update.
We surely don't need *another* set of recommended traffic classes.

However, at a peering connection where you don't have that level of trust,
you have to either reclassify all packets or mark everything as best effort=
.

Every ISP needs to solve the interworking
> issue once only and should expect a reasonable end to end QoS.
>
> The proposal more tries to look at DiffServ router forwarding knobs:
> a queuing mechanism and active queue management. My view is, these can
> be optimised for an expected transport behaviour:
>
> UDP traffic (streaming or telephony, real time gaming) will most
> likely not be retransmitted. A short queue will do, active queue
> management by random drops isn't required (unless you'd like to apply
> PCN marking or the like).
>
> TCP traffic interacts with router congestion indications, queues may
> be a little bit deeper and active queue management may be deployed.
> Today it is RED, ECN or the like in future.

How do you help the alarming amount of traffic that is streaming over TCP?

    Brian

>
> If one looks at it from that angle, the number of useful QoS classes
> is small.
>
> Take the transport indication (TCP/UDP) as "dominating" in a class,
> not a pureness requirement.
>
> Regards
>
> Ruediger
>
>
>
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf
> Of Dan Wing
> Sent: Friday, July 27, 2012 6:27 PM
> To: 'Jose Saldana'
> Cc: tcmtf@ietf.org; tsvwg@ietf.org
> Subject: Re: [tsvwg] [tcmtf] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>
>> -----Original Message-----
>> From: Jose Saldana [mailto:jsaldana@unizar.es]
>> Sent: Friday, July 27, 2012 4:14 AM
>> To: 'Dan Wing'
>> Cc: tcmtf@ietf.org; tsvwg@ietf.org
>> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>
>> Well, perhaps a solution is the use of Diffserv bits: in the draft
>> for updating rfc4594
>> (https://datatracker.ietf.org/doc/draft-polk-tsvwg-rfc4594-update)
>> there are
>> classes for real-time services and for best-effort ones. I have
>> always believed that the update of rfc4594 can be beneficial for
>> TCMTF: you can build a tunnel with flows belonging to the same
>> traffic category.
>>
>> But I don't know if the best-effort class means exactly the same as
>> delay-tolerant.
>>
>> Dan, what do you think?
>
> I agree that DSCP is the best tool we have to combine packets with
> similar characteristics.
>
> A recurring problem with DSCP is they are re-written to different
> values because a router was configured to rewrite them all the time or
> because a queue of that traffic class had built.  That rewriting needs
> to be considered (or ignored) when grouping packets that are
> 'similar'.  IMO, the fact that a packet was in a queue a few router
> hops away (and now has a different DSCP than its friends) doesn't
> change that it should be grouped with all of its friends into a
> multiplexing tunnel.
>
> -d
>
>
>> Thanks,
>>
>> Jose
>>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>> de Dan Wing Enviado el: viernes, 27 de julio de 2012 0:53
>> Para: 'Jose Saldana'
>> CC: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>
>>> -----Original Message-----
>>> From: Jose Saldana [mailto:jsaldana@unizar.es]
>>> Sent: Thursday, July 26, 2012 3:56 AM
>>> To: 'Dan Wing'
>>> Cc: tcmtf@ietf.org
>>> Subject: RE: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>>
>>> Dan,
>>>
>>> I don't know if I have really understood your question. Of course, I
>>> assume that a delay of some seconds is not important for certain
>>> sensor networks.
>>> But they don't need to signal that they are delay tolerant. I mean,
>>> they are assumed to be from the moment they are installed.
>> The device, doing the multiplexing, needs to know if the packets
>> belong to a delay-tolerant (sensor) endpoint or to a non-delay
>> tolerant endpoint.
>>
>> If the device doing the multiplexing is also the gateway
>> communicating with the delay-tolerant (sensor) network, it certainly
>> knows those
>> devices are delay-tolerant.   I believe that is your point.
>>
>> My point is that if the device doing the multiplexing is not directly
>> connected to that network of delay-tolerant devices, it needs to
>> somehow differentiate between the delay-tolerant devices and the non-
>> delay- tolerant
>> -- by being signaled or by being configured.
>>
>> In the future, I expect a mix of sensors on various networks that are
>> not traditional dedicated sensor networks (e.g., WiFi, 3G), so
>> relying on a gateway to that dedicated network may not always be the
>> way to know a device is delay tolerant.
>>
>> -d
>>
>>> Well, I think I should gather some information about typical
>>> examples of sensor networks (number of sensors, frequency of
>>> samples, packet size of the samples, etc), in order to calculate in
>>> which cases the bandwidth saving obtained with TCMTF can be
>>> interesting, and which "multiplexing period"
>>> should be used. I think that this could be a typical case in which
>>> multiplexing can be done by packet size instead of using a period. I
>>> mean, when you have almost 1500 bytes (or the MTU), you send a
>> packet.
>>> I don't know if I have answered your question,
>>>
>>> Jose
>>>
>>> -----Mensaje original-----
>>> De: Dan Wing [mailto:dwing@cisco.com] Enviado el: martes, 24 de
>>> julio de 2012 23:58
>>> Para: jsaldana@unizar.es
>>> CC: Tomaso.deCola@dlr.de; fpb@tid.es; tcmtf@ietf.org
>>> Asunto: Re: [tcmtf] [tsvwg] M2M, WSNs and draft-saldana-tsvwg-tcmtf
>>>
>>> ...
>>>> Nevertheless, in order to get an idea of the savings, we should
>>> deploy
>>>> some calculations. Our research group has only done simulations for
>>>> VoIP and games. In this case, we should know:
>>>>
>>>>
>>>>
>>>> -          Number of sensors in a typical scenario.
>>>>
>>>> -          Packet size and used headers. If IPv6 is used, savings
>>>>            can be really big, since header compression is really
>>>>            good for it.
>>>>
>>>> -          Packets per second that a single sensor can generate.
>>>>
>>>>
>>>>
>>>> And of course, the gateway should be the place for multiplexing.
>>>> In this case, the flows only travel from sensors to data center.
>>>> Am I right?
>>> I wonder if there is an easy way for the endpoints to signal that
>> they
>>> are delay tolerant (to allow collecting ~5 seconds of little
>> packets).
>>> -d
>>
>> _______________________________________________
>> 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

