
From fpb@tid.es  Mon Oct  1 01:53:56 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 1BD8021F85F0 for <tcmtf@ietfa.amsl.com>; Mon,  1 Oct 2012 01:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.835
X-Spam-Level: 
X-Spam-Status: No, score=-4.835 tagged_above=-999 required=5 tests=[AWL=-0.837, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dZTh0VrVWx2g for <tcmtf@ietfa.amsl.com>; Mon,  1 Oct 2012 01:53:54 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 638CF21F85C7 for <tcmtf@ietf.org>; Mon,  1 Oct 2012 01:53:46 -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 <0MB700BC8I1KIP@tid.hi.inet> for tcmtf@ietf.org; Mon, 01 Oct 2012 10:53:44 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 6D.8F.05494.81A59605; Mon, 01 Oct 2012 10:53:44 +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 <0MB700BC4I1KIP@tid.hi.inet> for tcmtf@ietf.org; Mon, 01 Oct 2012 10:53:44 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.209]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0318.001; Mon, 01 Oct 2012 10:52:39 +0200
Date: Mon, 01 Oct 2012 08:52:38 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <001d01cd9d5d$239aa870$6acff950$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A249D94ACB@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_MtxaqHOsNIyrwlWWGHgm+A)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: [tcmtf] TCMTF: The importance of the layers
Thread-index: Ac2dWmmuh0nyfojQS3ewOn6+GV2BHgCV9zYA
user-agent: Microsoft-MacOutlook/14.2.4.120824
X-AuditID: 0a5f4e69-b7fc06d000001576-63-50695a181d57
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNKsWRmVeSWpSXmKPExsXCFe9nqCsRlRlg8PKiscWuzxsYHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CV8aN9JnvBbJuKbV8PMDYwLjTtYuTkkBAwkbj5eTEjhC0mceHe ejYQW0hgO6PEpmnVXYxcQPZPRonZXT0sEM5MRonbj/+zg1SxCKhKvP08EcxmE9CSOH13FQuI LSxgIfHldTsziM0JZD/4to8VYoOCxJ9zj8FqRAQCJHa3HACzeQW8JY5f3c8EYQtK/Jh8DyzO LJArcWVZDzuELS7R3HoTLM4IdOn3U2uA6jmA5lhK/HjpCDHSSOLY2Vdg5aICehILdh9khlgr ILFkz3koW1Ti5eN/rBMYRWch2TYLybZZSLZB2HoSN6ZOYYOwtSWWLXzNDGHrSsz4dwiohgPI NpN4+6ocWckCRo5VjGLFSUWZ6RkluYmZOekGRnoZmXqZeaklmxghMZe5g3H5TpVDjAIcjEo8 vD8WJgQIsSaWFVfmHmKU5GBSEuV9FZEZIMSXlJ9SmZFYnBFfVJqTWnyIUYKDWUmEl3NGRoAQ b0piZVVqUT5MSoaDQ0mCVzMSqE2wKDU9tSItMweYWGDSTBycIO08QO0ZIDW8xQWJucWZ6RD5 U4ySUuK8gSAJAZBERmkeXO8rRnGgI4V5nUGyPMAUCNf1CmggE9DAqlVpIANLEhFSUg2MUawl jlU1xtNbft+p+avRciAzq3aOQfGpW979c3mKtU9npPL75VZWevU/e1GpU7bup9TW4utZCXMd 3cO8449uK75XHSPmzXj4rlq5RKf0DSHn1BoL1gSrA/ELbKxvzT3LuqVw3Y4t8o+kxN8y9ppr 2kzv1TyVxOQUkfq1Yq+62JIvB80iQ5RYijMSDbWYi4oTAeHLKgw+AwAA
Subject: Re: [tcmtf] TCMTF: The importance of the layers
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2012 08:53:56 -0000

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

Hi Jose,

In that case, tunneling headers (L2TP) should not be maintained. L2TP paylo=
ad (PPPMux and higher layers I guess) should be mounted over MPLS.

Regards,

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

From: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.es<m=
ailto:jsaldana@unizar.es>>
Organization: Universidad de Zaragoza
Reply-To: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.=
es<mailto:jsaldana@unizar.es>>
Date: viernes 28 de septiembre de 2012 11:39
To: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Subject: [tcmtf] TCMTF: The importance of the layers


One question: could this be done, when arriving to a MPLS network? Should t=
he L2TP/IP headers be maintained?:



                    +------+-------+

                    | L2TP |       +

5 flows tunnel -->  +------+ MPLS  + ----------> 5 flows tunnel

                    | IP   |       +

                    +------+-------+





________________________________

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_MtxaqHOsNIyrwlWWGHgm+A)
Content-id: <2CB8DCF8DDCACB41B69320E63036DF5A@hi.inet>
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">
</head>
<body style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font=
-family:Calibri,sans-serif">
<div>
<div>
<div>Hi Jose,</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>In tha=
t case, tunneling headers (L2TP) should not be maintained. L2TP payload (PP=
PMux and higher layers I guess) should be mounted over MPLS.</div>
<div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Fernando Pascual Blanco</div>
<div>Telef=F3nica Global Resources</div>
<div>Network Automation and Dynamization</div>
<div>TECHNOLOGY PEOPLE GROUP</div>
<div>F &#43;34913128779</div>
<div>M &#43;34682005168</div>
<div>fpb@tid.es</div>
</div>
</div>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; border-bottom:medium none; border-left:medium none; padding-bottom:0i=
n; padding-left:0in; padding-right:0in; border-top:#b5c4df 1pt solid; borde=
r-right:medium none; padding-top:3pt">
<span style=3D"font-weight:bold">From: </span>&quot;<a href=3D"mailto:jsald=
ana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsaldana@=
unizar.es">jsaldana@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Organization: </span>Universidad de Zarago=
za<br>
<span style=3D"font-weight:bold">Reply-To: </span>&quot;<a href=3D"mailto:j=
saldana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsald=
ana@unizar.es">jsaldana@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>viernes 28 de septiembre de 2=
012 11:39<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:tcmtf@i=
etf.org">tcmtf@ietf.org</a>&quot; &lt;<a href=3D"mailto:tcmtf@ietf.org">tcm=
tf@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[tcmtf] TCMTF: The importa=
nce of the layers<br>
</div>
<div><br>
</div>
<p class=3D"MsoPlainText" style=3D"margin-top:0cm; margin-right:0cm; margin=
-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-family:Calibri,sans=
-serif">
<span lang=3D"EN-US" style=3D"font-family:'Courier New'">One question: coul=
d this be done, when arriving to a MPLS network? Should the L2TP/IP headers=
 be maintained?:</span></p>
<p class=3D"MsoPlainText" style=3D"margin-top:0cm; margin-right:0cm; margin=
-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-family:Calibri,sans=
-serif">
<span lang=3D"EN-US" style=3D"font-family:'Courier New'">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-top:0cm; margin-right:0cm; margin=
-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-family:Calibri,sans=
-serif">
<span lang=3D"EN-US" style=3D"font-family:'Courier New'">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&#43;------&#43;-------&#43;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-top:0cm; margin-right:0cm; margin=
-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-family:Calibri,sans=
-serif">
<span lang=3D"EN-US" style=3D"font-family:'Courier New'">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;| L2TP |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;</s=
pan></p>
<p class=3D"MsoPlainText" style=3D"margin-top:0cm; margin-right:0cm; margin=
-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-family:Calibri,sans=
-serif">
<span lang=3D"EN-US" style=3D"font-family:'Courier New'">5 flows tunnel --&=
gt;&nbsp; &#43;------&#43; MPLS&nbsp; &#43; ----------</span><span lang=3D"=
EN-US" style=3D"font-size:10pt; font-family:'Courier New'">&gt;<span class=
=3D"Apple-converted-space">&nbsp;</span></span><span lang=3D"EN-US" style=
=3D"font-family:'Courier New'">5
 flows tunnel</span></p>
<p class=3D"MsoPlainText" style=3D"margin-top:0cm; margin-right:0cm; margin=
-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-family:Calibri,sans=
-serif">
<span lang=3D"EN-US" style=3D"font-family:'Courier New'">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;| IP&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; &#43;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-top:0cm; margin-right:0cm; margin=
-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-family:Calibri,sans=
-serif">
<span lang=3D"EN-US" style=3D"font-family:'Courier New'">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&#43;------&#43;-------&#43;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-top:0cm; margin-right:0cm; margin=
-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-family:Calibri,sans=
-serif">
<span lang=3D"EN-US" style=3D"font-family:'Courier New'">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-top:0cm; margin-right:0cm; margin=
-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-family:Calibri,sans=
-serif">
<span lang=3D"EN-US" style=3D"font-family:'Courier New'">&nbsp;</span></p>
</span><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_MtxaqHOsNIyrwlWWGHgm+A)--

From jsaldana@unizar.es  Mon Oct  1 03:15:13 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 CD92721F84EE for <tcmtf@ietfa.amsl.com>; Mon,  1 Oct 2012 03:15:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.08
X-Spam-Level: 
X-Spam-Status: No, score=-6.08 tagged_above=-999 required=5 tests=[AWL=0.519,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WhVYOW5Mh+I3 for <tcmtf@ietfa.amsl.com>; Mon,  1 Oct 2012 03:15:11 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id C631221F845A for <tcmtf@ietf.org>; Mon,  1 Oct 2012 03:15:09 -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 q91AF28d014724; Mon, 1 Oct 2012 12:15:02 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <gorry@erg.abdn.ac.uk>
References: <003101cd9d62$c803f1f0$580bd5d0$@unizar.es> <506592DF.7070508@erg.abdn.ac.uk>
In-Reply-To: <506592DF.7070508@erg.abdn.ac.uk>
Date: Mon, 1 Oct 2012 12:15:05 +0200
Organization: Universidad de Zaragoza
Message-ID: <004701cd9fbd$a0a1b540$e1e51fc0$@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: AQHVprSodD9UYB0w1jP2flEMIsTifgI+jB+cl4I32ZA=
Content-language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] More satellite scenarios
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2012 10:15:13 -0000

Gorry,

The question here is that perhaps the scenario of the sensor network in
http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scenario.pdf =
was
too simplistic, and TCMTF made no sense for it, since the use of IP =
would
not be necessary, as you remarked. There are more interesting =
compressing
options for that scenario. Am I correct?

Thanks for your feedback,

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Gorry Fairhurst
> Enviado el: viernes, 28 de septiembre de 2012 14:07
> Para: tcmtf@ietf.org
> Asunto: Re: [tcmtf] More satellite scenarios
>=20
> I did not dispute the use of VoIP and other "small packet" services =
over
> satellite (I work on this subject). What I wanted to understand was =
why
> ROHC or RFC 3545 (e.g. for VoIP) was not applicable.
>=20
> Gorry
>=20
> On 28/09/2012 11:19, Jose Saldana wrote:
> > We have to continue the discussion about satellite scenarios with
> > sensor
> > networks: if possible, I would like to hear the opinion of people =
from
> > DLR about this.
> >
> >
> > However, I have found more satellite-related scenarios in which a
> > number of small-packet flows can be present:
> >
> > - A cruise: lots of people (3800 people in Queen Mary 2) connected
> > through a satellite link
> >
> >
> http://www.cruisemates.com/articles/onboard/connected.cfm#axzz27l0sEq
> u
> > 3
> > http://en.wikipedia.org/wiki/RMS_Queen_Mary_2
> > http://www.esa.int/esaTE/SEMMAWNFGLE_index_0.html
> >
> >
> > - A plane: similar to the ship, but less people and no satellite, =
but
> > ground antennas communicating with a special antenna on the plane
> > (VoIP is prohibited by now):
> > http://en.wikipedia.org/wiki/Gogo_Inflight_Internet
> >
> >
> > - Satellite access in low-populated regions (e.g. Alaska): Perhaps a
> > number of people, or a village, may share a  connection through an
> antenna:
> > =
http://www.skycasters.com/satellite-internet-coverage/skycasters-cover
> > age-Al
> > aska.html
> >
> >
> > What do you think?
> >
> > Best regards,
> >
> > Jose
> >
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> >> de Gorry Fairhurst Enviado el: viernes, 21 de septiembre de 2012
> >> 10:29
> >> Para: jsaldana@unizar.es
> >> CC: tcmtf@ietf.org; 'FERNANDO PASCUAL BLANCO'
> >> Asunto: Re: [tcmtf] Discussing M2M scenario and savings - =
continuing
> >> the thread
> >>
> >> I think *IF* the satellite link is a DVB 2nd generation RF link, =
e.g.
> >> DVB-S2 for satellite ( a common waveform), then GSE + RFC 5163 is a
> >> reasonable proposal, on which one may benefit if one layers a HC
> >> scheme, such as ROHC, or 6LoWPAN. The profile for the  ROHC schemes
> >> have not been specified for this type of link - but the relevant =
RFCs
> >> exist for the compression itself. RFC 3135 and RFC 3449 also =
describe
> >> TCP/IP techniques
> > to
> >> help improve efficiency on such links.
> >>
> >> As I said, I do not see the *benefit* for the mux and demux in the
> > scenario
> >> as drawn, since this seems more like *link* HC, and it would seem
> >> foolish
> > to
> >> form aggregate traffic over a single link layer in the way that
> >> tunnel compression implements this.
> >>
> >> If the drawing extended the network on one or both sides of the
> >> satellite link, there could be a reason for using tunnel HC, =
although
> >> I am not sure whether this is commercially important, since unlike =
an
> >> access network,
> > the
> >> connectivity to the hub (usually known as the satellite gateway) on
> >> the
> > left of
> >> the figure is not usually a low speed access link and the merits of
> >> HC is
> > less
> >> obvious where bandwidth is high. Also, it would seem desirable to =
use
> >> encapsulation and HC mechanisms on the satellite air interface
> >> anyway, RFC
> >> 3135 part 3 (from the source), possibly combined with RFC 3449
> mechanisms.
> >>
> >> All I am saying is you have to be sure to describe the scenario
> >> carefully
> > and
> >> explain why HC applies in this case and what alternatives exist.
> >>
> >> Gorry
> >>
> >> On 20/09/2012 17:20, Jose Saldana wrote:
> >>> So, do you think the figure should be modified? Perhaps it is
> >>> currently confusing, since it seems that RFC 5163 is the best
> >>> solution. Perhaps a network should be included between the demux
> and
> >>> the data center? Or between the antenna and the demux? Will this =
be
> >>> a real case? I don't know if in the right side it is possible to
> >>> find
> > other
> >> networks.
> >>>
> >>> I am talking about this figure:
> >>>
> >>> =
http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scenario.
> >>> pd
> >>> f
> >>>
> >>> Thanks,
> >>>
> >>> Jose
> >>>
> >>> -----Mensaje original-----
> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> nombre
> >>> de FERNANDO PASCUAL BLANCO Enviado el: mi=E9rcoles, 19 de
> septiembre
> >> de
> >>> 2012 13:02
> >>> Para: gorry@erg.abdn.ac.uk; tcmtf@ietf.org
> >>> Asunto: Re: [tcmtf] Discussing M2M scenario and savings - =
continuing
> >>> the thread
> >>>
> >>> Hi Gorry,
> >>>
> >>>           Absolutely. The tunneling layer would increase that
> >>> benefit in a multi-router hop path, being the satellite-link part =
of
this
> path.
> >>>
> >>> Regards,
> >>>
> >>> Fernando Pascual Blanco
> >>>
> >>> Telef=F3nica Global Resources
> >>>
> >>> Network Automation and Dynamization
> >>>
> >>> TECHNOLOGY PEOPLE GROUP
> >>>
> >>> F +34913128779
> >>>
> >>> M +34682005168
> >>>
> >>> fpb@tid.es <mailto:fpb@tid.es>
> >>>
> >>> On 19/09/12 12:37, "gorry@erg.abdn.ac.uk
> >> <mailto:gorry@erg.abdn.ac.uk>"
> >>> <gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>> wrote:
> >>>
> >>>   >
> >>>
> >>>   >For a point-to-point link carrying traffic destined to a ingle =
L2
> >>>
> >>>   >address, I don't see how this helps above the gains of ROHC or
> >>> some
> >>>
> >>>   >other HC on the link, when possibly combining this with link
> >>> layer
> >>>
> >>>   >transmission options e.g. methods like PDU-CONCAT in RFC 5163.
> >>>
> >>>   >
> >>>
> >>>   >If you're working over a multi-router network hop, the
> >>> considerations
> >>>
> >>>   >may be different.
> >>>
> >>>   >
> >>>
> >>>   >Gorry
> >>>
> >>>   >
> >>>
> >>>   >> Hi Gorry,
> >>>
> >>>   >>
> >>>
> >>>   >>         I don=C2=B4t know a lot about link layer HC, but I =
imagine
that
> >>>
> >>>   >> it compress packet headers (IP-TCP/UDP). If, in addition to
> >>> that, we
> >>>
> >>>   >> group several small packets into a bigger one (using PPP-Mux
> >>> and
> >>>
> >>>   >> RoHC), don=C2=B4t you think more resources could be saved?
> >>>
> >>>   >>
> >>>
> >>>   >> Regards,
> >>>
> >>>   >>
> >>>
> >>>   >> Fernando Pascual Blanco
> >>>
> >>>   >> Telef=C3=B3nica Global Resources
> >>>
> >>>   >> Network Automation and Dynamization
> >>>
> >>>   >> TECHNOLOGY PEOPLE GROUP
> >>>
> >>>   >> F +34913128779
> >>>
> >>>   >> M +34682005168
> >>>
> >>>   >> fpb@tid.es <mailto:fpb@tid.es>
> >>>
> >>>   >>
> >>>
> >>>   >>
> >>>
> >>>   >>
> >>>
> >>>   >>
> >>>
> >>>   >> On 19/09/12 10:56, "gorry@erg.abdn.ac.uk
> >>> <mailto:gorry@erg.abdn.ac.uk>" <gorry@erg.abdn.ac.uk
> >>> <mailto:gorry@erg.abdn.ac.uk>> wrote:
> >>>
> >>>   >>
> >>>
> >>>   >>>I know there are applications for tunnel compression - but =
I'm
> >>> not
> >>>
> >>>   >>>sure  I understand how this can gain further than for =
link-layer
HC?
> >>>
> >>>   >>>
> >>>
> >>>   >>>Gorry
> >>>
> >>>   >>>
> >>>
> >>>   >>>> Hi Gorry,
> >>>
> >>>   >>>>
> >>>
> >>>   >>>>         In addition of HC (header compression), the
multiplexing
> >>>
> >>>   >>>> layer will save even more resources. In that case and
> >>> assuming that
> >>>
> >>>   >>>> all the traffic through the link have the same QoS
> >>> requirements
> >>>
> >>>   >>>> (for example a sensor network), the idea would be to group
> >>> all the
> >>>
> >>>   >>>> flows through the link (the bottleneck).
> >>>
> >>>   >>>>
> >>>
> >>>   >>>> Regards,
> >>>
> >>>   >>>>
> >>>
> >>>   >>>> Fernando Pascual Blanco
> >>>
> >>>   >>>> Telef=C3=B3nica Global Resources
> >>>
> >>>   >>>> Network Automation and Dynamization TECHNOLOGY PEOPLE
> >> GROUP F
> >>>
> >>>   >>>> +34913128779 M +34682005168 fpb@tid.es <mailto:fpb@tid.es>
> >>>
> >>>   >>>>
> >>>
> >>>   >>>>
> >>>
> >>>   >>>>
> >>>
> >>>   >>>>
> >>>
> >>>   >>>> On 18/09/12 20:46, "Gorry Fairhurst" <gorry@erg.abdn.ac.uk
> >>> <mailto:gorry@erg.abdn.ac.uk>> wrote:
> >>>
> >>>   >>>>
> >>>
> >>>   >>>>>A satellite "link" may provide HC, at least some of the =
ones
> >>> I have
> >>>
> >>>   >>>>>seen do. In this case, the flows can easily be grouped by =
mac
> >>>
> >>>   >>>>>address?
> >>>
> >>>   >>>>>
> >>>
> >>>   >>>>>Gorry
> >>>
> >>>   >>>>>
> >>>
> >>>   >>>>>On 13/09/2012 16:20, Jose Saldana wrote:
> >>>
> >>>   >>>>>> Hi, Fernando, sorry for the delay (one week, I=C2=B9m =
afraid).
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> I don=C2=B9t know who is the one interested on using =
TCMTF:
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> -If you are a costumer, and you have to pay for a =
satellite
> >>> link
> >>>
> >>>   >>>>>>or  a  long distance wire, perhaps you are the one
> >>> interested on
> >>>
> >>>   >>>>>>using  end-to-end TCMTF, since you will save bandwidth or
> >>> packets
> >>>
> >>>   >>>>>>per  second  or  money. If you have e.g. two offices, one =
in
> >>>
> >>>   >>>>>>America and other one in  Europe, you may be interested on
> >>> placing
> >>>
> >>>   >>>>>>a device for multiplexing a  number of VoIP calls between
them.
> >>>
> >>>   >>>>>>You have one advantage: the flows  have the same origin =
and
> >>>
> >>>   >>>>>>destination, so header compression is effective.
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> -If you are the operator of the satellite, you have =
another
> >> problem:
> >>>
> >>>   >>>>>> you
> >>>
> >>>   >>>>>> may have to check every flow, and try to group them.
> >>> Perhaps it
> >>>
> >>>   >>>>>> may be easy, but if you want to save headers, you need
> >>> flows with
> >>>
> >>>   >>>>>> the same origin and destination.
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> I think that there are different scenarios, and each
> >>> =C2=B3actor=C2=B2
> >>>
> >>>   >>>>>>may  try to  use TCMTF in the best place: a high number of
> >>> flows,
> >>>
> >>>   >>>>>>with small  packets,  and sharing the same origin and
> > destination.
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> Do you agree?
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> Jose
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> *De:*tcmtf-bounces@ietf.org [mailto:tcmtf-
> bounces@ietf.org]
> >>> <mailto:[mailto:tcmtf-bounces@ietf.org]> *En
> >>>
> >>>   >>>>>> nombre de *FERNANDO PASCUAL BLANCO *Enviado el:*
> martes,
> >> 04 de
> >>>
> >>>   >>>>>> septiembre de 2012 12:27
> >>>
> >>>   >>>>>> *Para:* tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >>>
> >>>   >>>>>> *Asunto:* Re: [tcmtf] Discussing M2M scenario and savings
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> Hi all,
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> Yes, M2M sensor networks are a very good example in order
> >>> to save
> >>>
> >>>   >>>>>> bandwidth in long distance/big latency/low bandwidth =
links,
> >>> links
> >>>
> >>>   >>>>>> were the cost per bit is high. Do you think network
> >>> carriers
> >>>
> >>>   >>>>>> operating this kind of links (satellite links or long
> >>> distance
> >>>
> >>>   >>>>>> wires) would be interested in apply TCMTF?
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> Regards,
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> Fernando
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> *From:*tcmtf-bounces@ietf.org <mailto:tcmtf-
> >> bounces@ietf.org>
> >>>
> >>>   >>>>>> [mailto:tcmtf-bounces@ietf.org]
> >>> <mailto:[mailto:tcmtf-bounces@ietf.org]>
> >>>
> >>>   >>>>>> <mailto:[mailto:tcmtf-bounces@ietf.org]>
> >>>
> >>>   >>>>>> *On Behalf Of *Jose Saldana
> >>>
> >>>   >>>>>> *Sent:* martes, 04 de septiembre de 2012 9:41
> >>>
> >>>   >>>>>> *To:* tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >>> <mailto:tcmtf@ietf.org>
> >>>
> >>>   >>>>>> *Cc:* Matteo.Berioli@dlr.de =
<mailto:Matteo.Berioli@dlr.de>
> >>> <mailto:Matteo.Berioli@dlr.de>;
> >>>
> >>>   >>>>>> Tomaso.deCola@dlr.de <mailto:Tomaso.deCola@dlr.de>
> >>> <mailto:Tomaso.deCola@dlr.de>
> >>>
> >>>   >>>>>> *Subject:* [tcmtf] Discussing M2M scenario and savings
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> Hi again,
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> We already discussed some points about the M2M scenario =
at
> >>> the
> >>>
> >>>   >>>>>>beginning  of August. We are currently studying this, and =
we
> >>> have
> >>>
> >>>   >>>>>>built some  figures, in collaboration with people from DLR
> >>> (Tomaso
> >>>
> >>>   >>>>>>and Matteo).
> >>>
> >>>   >>>>>>You
> >>>
> >>>   >>>>>> can find the figures here:
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>>
> >>>
> >>>
> >>>
> >>>>>>>>
> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_savi
> >>>>>>>> n
> >>> gs
> >>>
> >>>   >>>>>>.pd
> >>>
> >>>   >>>>>>f
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>>
> >>>
> >>>
> >>>
> >>>>>>>>
> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scen
> >>>>>>>> a
> >>> ri
> >>>
> >>>   >>>>>>o.p
> >>>
> >>>   >>>>>>df
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> Perhaps we could comment them, in order to discuss this
> >>> scenario,
> >>>
> >>>   >>>>>> and we may find new ones in which TCMTF can be useful.
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> Thanks,
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> Jose
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>>
> >>>
> >>>
> >>>>>>>>> =
--------------------------------------------------------------
> >>>>>>>>> --
> >>> --
> >>>
> >>>   >>>>>>---
> >>>
> >>>   >>>>>>--
> >>>
> >>>   >>>>>>-
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> Este mensaje se dirige exclusivamente a su destinatario.
> >>> Puede
> >>>
> >>>   >>>>>> consultar nuestra pol=C3=ADtica de env=C3=ADo y =
recepci=C3=B3n de
> >>> correo
> >>>
> >>>   >>>>>> electr=C3=B3nico en el enlace situado m=C3=A1s abajo.
> >>>
> >>>   >>>>>> This message is intended exclusively for its addressee. =
We
> >>> only
> >>>
> >>>   >>>>>> send and receive email on the basis of the terms set out =
at:
> >>>
> >>>   >>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>> _______________________________________________
> >>>
> >>>   >>>>>> tcmtf mailing list
> >>>
> >>>   >>>>>> tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >>>
> >>>   >>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>>
> >>>   >>>>>>
> >>>
> >>>   >>>>>
> >>>
> >>>   >>>>>_______________________________________________
> >>>
> >>>   >>>>>tcmtf mailing list
> >>>
> >>>   >>>>>tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >>>
> >>>   >>>>>https://www.ietf.org/mailman/listinfo/tcmtf
> >>>
> >>>   >>>>
> >>>
> >>>   >>>>
> >>>
> >>>   >>>> ________________________________
> >>>
> >>>   >>>>
> >>>
> >>>   >>>> Este mensaje se dirige exclusivamente a su destinatario.
> >>> Puede
> >>>
> >>>   >>>> consultar nuestra pol=C3=ADtica de env=C3=ADo y =
recepci=C3=B3n de correo
> >>>
> >>>   >>>> electr=C3=B3nico en el enlace situado m=C3=A1s 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
> >>>
> >>>   >>>>
> >>>
> >>>   >>>
> >>>
> >>>   >>>
> >>>
> >>>   >>
> >>>
> >>>   >>
> >>>
> >>>   >> ________________________________
> >>>
> >>>   >>
> >>>
> >>>   >> Este mensaje se dirige exclusivamente a su destinatario. =
Puede
> >>>
> >>>   >> consultar nuestra pol=C3=ADtica de env=C3=ADo y =
recepci=C3=B3n de correo
> >>>
> >>>   >> electr=C3=B3nico en el enlace situado m=C3=A1s abajo.
> >>>
> >>>   >> This message is intended exclusively for its addressee. We =
only
> >>> send
> >>>
> >>>   >> and receive email on the basis of the terms set out at:
> >>>
> >>>   >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >>>
> >>>   >>
> >>>
> >>>   >
> >>>
> >>>   >
> >>>
> >>>   >
> >>>
> >>>   >_______________________________________________
> >>>
> >>>   >tcmtf mailing list
> >>>
> >>>   >tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >>>
> >>>   >https://www.ietf.org/mailman/listinfo/tcmtf
> >>>
> >>> ________________________________
> >>>
> >>> Este mensaje se dirige exclusivamente a su destinatario. Puede
> >>> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo
> >>> electr=F3nico en el enlace situado m=E1s abajo.
> >>>
> >>> This message is intended exclusively for its addressee. We only =
send
> >>> and receive email on the basis of the terms set out at:
> >>>
> >>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >>>
> >>> _______________________________________________
> >>>
> >>> tcmtf mailing list
> >>>
> >>> tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >>>
> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> tcmtf mailing list
> >>> tcmtf@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>>
> >>
> >> _______________________________________________
> >> tcmtf mailing list
> >> tcmtf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >
> > _______________________________________________
> > tcmtf mailing list
> > tcmtf@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcmtf
> >
>=20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From gorry@erg.abdn.ac.uk  Mon Oct  1 03:29:57 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 BD8CA21F8621 for <tcmtf@ietfa.amsl.com>; Mon,  1 Oct 2012 03:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.513
X-Spam-Level: 
X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66R7YyIp926A for <tcmtf@ietfa.amsl.com>; Mon,  1 Oct 2012 03:29:56 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 8D2C021F8589 for <tcmtf@ietf.org>; Mon,  1 Oct 2012 03:29:55 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id CF0FB2B4039; Mon,  1 Oct 2012 11:29:53 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Mon, 1 Oct 2012 11:29:53 +0100
Message-ID: <c898f337fd617ee9fe1a49b9ac8d35e9.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <004701cd9fbd$a0a1b540$e1e51fc0$@unizar.es>
References: <003101cd9d62$c803f1f0$580bd5d0$@unizar.es> <506592DF.7070508@erg.abdn.ac.uk> <004701cd9fbd$a0a1b540$e1e51fc0$@unizar.es>
Date: Mon, 1 Oct 2012 11:29:53 +0100
From: gorry@erg.abdn.ac.uk
To: jsaldana@unizar.es
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: gorry@erg.abdn.ac.uk, tcmtf@ietf.org
Subject: Re: [tcmtf] More satellite scenarios
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2012 10:29:57 -0000

That is what I think - the proposed tunnel method does not seem to have
advantage when used over a single link.

Gorry

> Gorry,
>
> The question here is that perhaps the scenario of the sensor network in
> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scenario.pdf
> was
> too simplistic, and TCMTF made no sense for it, since the use of IP would
> not be necessary, as you remarked. There are more interesting compressing
> options for that scenario. Am I correct?
>
> Thanks for your feedback,
>
> Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Gorry Fairhurst
>> Enviado el: viernes, 28 de septiembre de 2012 14:07
>> Para: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] More satellite scenarios
>>
>> I did not dispute the use of VoIP and other "small packet" services over
>> satellite (I work on this subject). What I wanted to understand was why
>> ROHC or RFC 3545 (e.g. for VoIP) was not applicable.
>>
>> Gorry
>>
>> On 28/09/2012 11:19, Jose Saldana wrote:
>> > We have to continue the discussion about satellite scenarios with
>> > sensor
>> > networks: if possible, I would like to hear the opinion of people from
>> > DLR about this.
>> >
>> >
>> > However, I have found more satellite-related scenarios in which a
>> > number of small-packet flows can be present:
>> >
>> > - A cruise: lots of people (3800 people in Queen Mary 2) connected
>> > through a satellite link
>> >
>> >
>> http://www.cruisemates.com/articles/onboard/connected.cfm#axzz27l0sEq
>> u
>> > 3
>> > http://en.wikipedia.org/wiki/RMS_Queen_Mary_2
>> > http://www.esa.int/esaTE/SEMMAWNFGLE_index_0.html
>> >
>> >
>> > - A plane: similar to the ship, but less people and no satellite, but
>> > ground antennas communicating with a special antenna on the plane
>> > (VoIP is prohibited by now):
>> > http://en.wikipedia.org/wiki/Gogo_Inflight_Internet
>> >
>> >
>> > - Satellite access in low-populated regions (e.g. Alaska): Perhaps a
>> > number of people, or a village, may share a  connection through an
>> antenna:
>> > http://www.skycasters.com/satellite-internet-coverage/skycasters-cover
>> > age-Al
>> > aska.html
>> >
>> >
>> > What do you think?
>> >
>> > Best regards,
>> >
>> > Jose
>> >
>> >> -----Mensaje original-----
>> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>> >> de Gorry Fairhurst Enviado el: viernes, 21 de septiembre de 2012
>> >> 10:29
>> >> Para: jsaldana@unizar.es
>> >> CC: tcmtf@ietf.org; 'FERNANDO PASCUAL BLANCO'
>> >> Asunto: Re: [tcmtf] Discussing M2M scenario and savings - continuing
>> >> the thread
>> >>
>> >> I think *IF* the satellite link is a DVB 2nd generation RF link, e.g.
>> >> DVB-S2 for satellite ( a common waveform), then GSE + RFC 5163 is a
>> >> reasonable proposal, on which one may benefit if one layers a HC
>> >> scheme, such as ROHC, or 6LoWPAN. The profile for the  ROHC schemes
>> >> have not been specified for this type of link - but the relevant RFCs
>> >> exist for the compression itself. RFC 3135 and RFC 3449 also describe
>> >> TCP/IP techniques
>> > to
>> >> help improve efficiency on such links.
>> >>
>> >> As I said, I do not see the *benefit* for the mux and demux in the
>> > scenario
>> >> as drawn, since this seems more like *link* HC, and it would seem
>> >> foolish
>> > to
>> >> form aggregate traffic over a single link layer in the way that
>> >> tunnel compression implements this.
>> >>
>> >> If the drawing extended the network on one or both sides of the
>> >> satellite link, there could be a reason for using tunnel HC, although
>> >> I am not sure whether this is commercially important, since unlike an
>> >> access network,
>> > the
>> >> connectivity to the hub (usually known as the satellite gateway) on
>> >> the
>> > left of
>> >> the figure is not usually a low speed access link and the merits of
>> >> HC is
>> > less
>> >> obvious where bandwidth is high. Also, it would seem desirable to use
>> >> encapsulation and HC mechanisms on the satellite air interface
>> >> anyway, RFC
>> >> 3135 part 3 (from the source), possibly combined with RFC 3449
>> mechanisms.
>> >>
>> >> All I am saying is you have to be sure to describe the scenario
>> >> carefully
>> > and
>> >> explain why HC applies in this case and what alternatives exist.
>> >>
>> >> Gorry
>> >>
>> >> On 20/09/2012 17:20, Jose Saldana wrote:
>> >>> So, do you think the figure should be modified? Perhaps it is
>> >>> currently confusing, since it seems that RFC 5163 is the best
>> >>> solution. Perhaps a network should be included between the demux
>> and
>> >>> the data center? Or between the antenna and the demux? Will this be
>> >>> a real case? I don't know if in the right side it is possible to
>> >>> find
>> > other
>> >> networks.
>> >>>
>> >>> I am talking about this figure:
>> >>>
>> >>> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scenario.
>> >>> pd
>> >>> f
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Jose
>> >>>
>> >>> -----Mensaje original-----
>> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> nombre
>> >>> de FERNANDO PASCUAL BLANCO Enviado el: miércoles, 19 de
>> septiembre
>> >> de
>> >>> 2012 13:02
>> >>> Para: gorry@erg.abdn.ac.uk; tcmtf@ietf.org
>> >>> Asunto: Re: [tcmtf] Discussing M2M scenario and savings - continuing
>> >>> the thread
>> >>>
>> >>> Hi Gorry,
>> >>>
>> >>>           Absolutely. The tunneling layer would increase that
>> >>> benefit in a multi-router hop path, being the satellite-link part of
> this
>> path.
>> >>>
>> >>> Regards,
>> >>>
>> >>> Fernando Pascual Blanco
>> >>>
>> >>> Telefónica Global Resources
>> >>>
>> >>> Network Automation and Dynamization
>> >>>
>> >>> TECHNOLOGY PEOPLE GROUP
>> >>>
>> >>> F +34913128779
>> >>>
>> >>> M +34682005168
>> >>>
>> >>> fpb@tid.es <mailto:fpb@tid.es>
>> >>>
>> >>> On 19/09/12 12:37, "gorry@erg.abdn.ac.uk
>> >> <mailto:gorry@erg.abdn.ac.uk>"
>> >>> <gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>> wrote:
>> >>>
>> >>>   >
>> >>>
>> >>>   >For a point-to-point link carrying traffic destined to a ingle L2
>> >>>
>> >>>   >address, I don't see how this helps above the gains of ROHC or
>> >>> some
>> >>>
>> >>>   >other HC on the link, when possibly combining this with link
>> >>> layer
>> >>>
>> >>>   >transmission options e.g. methods like PDU-CONCAT in RFC 5163.
>> >>>
>> >>>   >
>> >>>
>> >>>   >If you're working over a multi-router network hop, the
>> >>> considerations
>> >>>
>> >>>   >may be different.
>> >>>
>> >>>   >
>> >>>
>> >>>   >Gorry
>> >>>
>> >>>   >
>> >>>
>> >>>   >> Hi Gorry,
>> >>>
>> >>>   >>
>> >>>
>> >>>   >>         I donÂ´t know a lot about link layer HC, but I imagine
> that
>> >>>
>> >>>   >> it compress packet headers (IP-TCP/UDP). If, in addition to
>> >>> that, we
>> >>>
>> >>>   >> group several small packets into a bigger one (using PPP-Mux
>> >>> and
>> >>>
>> >>>   >> RoHC), donÂ´t you think more resources could be saved?
>> >>>
>> >>>   >>
>> >>>
>> >>>   >> Regards,
>> >>>
>> >>>   >>
>> >>>
>> >>>   >> Fernando Pascual Blanco
>> >>>
>> >>>   >> TelefÃ³nica Global Resources
>> >>>
>> >>>   >> Network Automation and Dynamization
>> >>>
>> >>>   >> TECHNOLOGY PEOPLE GROUP
>> >>>
>> >>>   >> F +34913128779
>> >>>
>> >>>   >> M +34682005168
>> >>>
>> >>>   >> fpb@tid.es <mailto:fpb@tid.es>
>> >>>
>> >>>   >>
>> >>>
>> >>>   >>
>> >>>
>> >>>   >>
>> >>>
>> >>>   >>
>> >>>
>> >>>   >> On 19/09/12 10:56, "gorry@erg.abdn.ac.uk
>> >>> <mailto:gorry@erg.abdn.ac.uk>" <gorry@erg.abdn.ac.uk
>> >>> <mailto:gorry@erg.abdn.ac.uk>> wrote:
>> >>>
>> >>>   >>
>> >>>
>> >>>   >>>I know there are applications for tunnel compression - but I'm
>> >>> not
>> >>>
>> >>>   >>>sure  I understand how this can gain further than for
>> link-layer
> HC?
>> >>>
>> >>>   >>>
>> >>>
>> >>>   >>>Gorry
>> >>>
>> >>>   >>>
>> >>>
>> >>>   >>>> Hi Gorry,
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>>         In addition of HC (header compression), the
> multiplexing
>> >>>
>> >>>   >>>> layer will save even more resources. In that case and
>> >>> assuming that
>> >>>
>> >>>   >>>> all the traffic through the link have the same QoS
>> >>> requirements
>> >>>
>> >>>   >>>> (for example a sensor network), the idea would be to group
>> >>> all the
>> >>>
>> >>>   >>>> flows through the link (the bottleneck).
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>> Regards,
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>> Fernando Pascual Blanco
>> >>>
>> >>>   >>>> TelefÃ³nica Global Resources
>> >>>
>> >>>   >>>> Network Automation and Dynamization TECHNOLOGY PEOPLE
>> >> GROUP F
>> >>>
>> >>>   >>>> +34913128779 M +34682005168 fpb@tid.es <mailto:fpb@tid.es>
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>> On 18/09/12 20:46, "Gorry Fairhurst" <gorry@erg.abdn.ac.uk
>> >>> <mailto:gorry@erg.abdn.ac.uk>> wrote:
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>>>A satellite "link" may provide HC, at least some of the ones
>> >>> I have
>> >>>
>> >>>   >>>>>seen do. In this case, the flows can easily be grouped by mac
>> >>>
>> >>>   >>>>>address?
>> >>>
>> >>>   >>>>>
>> >>>
>> >>>   >>>>>Gorry
>> >>>
>> >>>   >>>>>
>> >>>
>> >>>   >>>>>On 13/09/2012 16:20, Jose Saldana wrote:
>> >>>
>> >>>   >>>>>> Hi, Fernando, sorry for the delay (one week, IÂ¹m afraid).
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> I donÂ¹t know who is the one interested on using TCMTF:
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> -If you are a costumer, and you have to pay for a satellite
>> >>> link
>> >>>
>> >>>   >>>>>>or  a  long distance wire, perhaps you are the one
>> >>> interested on
>> >>>
>> >>>   >>>>>>using  end-to-end TCMTF, since you will save bandwidth or
>> >>> packets
>> >>>
>> >>>   >>>>>>per  second  or  money. If you have e.g. two offices, one in
>> >>>
>> >>>   >>>>>>America and other one in  Europe, you may be interested on
>> >>> placing
>> >>>
>> >>>   >>>>>>a device for multiplexing a  number of VoIP calls between
> them.
>> >>>
>> >>>   >>>>>>You have one advantage: the flows  have the same origin and
>> >>>
>> >>>   >>>>>>destination, so header compression is effective.
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> -If you are the operator of the satellite, you have another
>> >> problem:
>> >>>
>> >>>   >>>>>> you
>> >>>
>> >>>   >>>>>> may have to check every flow, and try to group them.
>> >>> Perhaps it
>> >>>
>> >>>   >>>>>> may be easy, but if you want to save headers, you need
>> >>> flows with
>> >>>
>> >>>   >>>>>> the same origin and destination.
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> I think that there are different scenarios, and each
>> >>> Â³actorÂ²
>> >>>
>> >>>   >>>>>>may  try to  use TCMTF in the best place: a high number of
>> >>> flows,
>> >>>
>> >>>   >>>>>>with small  packets,  and sharing the same origin and
>> > destination.
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Do you agree?
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Jose
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> *De:*tcmtf-bounces@ietf.org [mailto:tcmtf-
>> bounces@ietf.org]
>> >>> <mailto:[mailto:tcmtf-bounces@ietf.org]> *En
>> >>>
>> >>>   >>>>>> nombre de *FERNANDO PASCUAL BLANCO *Enviado el:*
>> martes,
>> >> 04 de
>> >>>
>> >>>   >>>>>> septiembre de 2012 12:27
>> >>>
>> >>>   >>>>>> *Para:* tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >>>
>> >>>   >>>>>> *Asunto:* Re: [tcmtf] Discussing M2M scenario and savings
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Hi all,
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Yes, M2M sensor networks are a very good example in order
>> >>> to save
>> >>>
>> >>>   >>>>>> bandwidth in long distance/big latency/low bandwidth links,
>> >>> links
>> >>>
>> >>>   >>>>>> were the cost per bit is high. Do you think network
>> >>> carriers
>> >>>
>> >>>   >>>>>> operating this kind of links (satellite links or long
>> >>> distance
>> >>>
>> >>>   >>>>>> wires) would be interested in apply TCMTF?
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Regards,
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Fernando
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> *From:*tcmtf-bounces@ietf.org <mailto:tcmtf-
>> >> bounces@ietf.org>
>> >>>
>> >>>   >>>>>> [mailto:tcmtf-bounces@ietf.org]
>> >>> <mailto:[mailto:tcmtf-bounces@ietf.org]>
>> >>>
>> >>>   >>>>>> <mailto:[mailto:tcmtf-bounces@ietf.org]>
>> >>>
>> >>>   >>>>>> *On Behalf Of *Jose Saldana
>> >>>
>> >>>   >>>>>> *Sent:* martes, 04 de septiembre de 2012 9:41
>> >>>
>> >>>   >>>>>> *To:* tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >>> <mailto:tcmtf@ietf.org>
>> >>>
>> >>>   >>>>>> *Cc:* Matteo.Berioli@dlr.de <mailto:Matteo.Berioli@dlr.de>
>> >>> <mailto:Matteo.Berioli@dlr.de>;
>> >>>
>> >>>   >>>>>> Tomaso.deCola@dlr.de <mailto:Tomaso.deCola@dlr.de>
>> >>> <mailto:Tomaso.deCola@dlr.de>
>> >>>
>> >>>   >>>>>> *Subject:* [tcmtf] Discussing M2M scenario and savings
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Hi again,
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> We already discussed some points about the M2M scenario at
>> >>> the
>> >>>
>> >>>   >>>>>>beginning  of August. We are currently studying this, and we
>> >>> have
>> >>>
>> >>>   >>>>>>built some  figures, in collaboration with people from DLR
>> >>> (Tomaso
>> >>>
>> >>>   >>>>>>and Matteo).
>> >>>
>> >>>   >>>>>>You
>> >>>
>> >>>   >>>>>> can find the figures here:
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>
>> >>>
>> >>>>>>>>
>> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_savi
>> >>>>>>>> n
>> >>> gs
>> >>>
>> >>>   >>>>>>.pd
>> >>>
>> >>>   >>>>>>f
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>
>> >>>
>> >>>>>>>>
>> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scen
>> >>>>>>>> a
>> >>> ri
>> >>>
>> >>>   >>>>>>o.p
>> >>>
>> >>>   >>>>>>df
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Perhaps we could comment them, in order to discuss this
>> >>> scenario,
>> >>>
>> >>>   >>>>>> and we may find new ones in which TCMTF can be useful.
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Thanks,
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Jose
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>
>> >>>>>>>>> --------------------------------------------------------------
>> >>>>>>>>> --
>> >>> --
>> >>>
>> >>>   >>>>>>---
>> >>>
>> >>>   >>>>>>--
>> >>>
>> >>>   >>>>>>-
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Este mensaje se dirige exclusivamente a su destinatario.
>> >>> Puede
>> >>>
>> >>>   >>>>>> consultar nuestra polÃ­tica de envÃ­o y recepciÃ³n de
>> >>> correo
>> >>>
>> >>>   >>>>>> electrÃ³nico en el enlace situado mÃ¡s abajo.
>> >>>
>> >>>   >>>>>> This message is intended exclusively for its addressee. We
>> >>> only
>> >>>
>> >>>   >>>>>> send and receive email on the basis of the terms set out
>> at:
>> >>>
>> >>>   >>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> _______________________________________________
>> >>>
>> >>>   >>>>>> tcmtf mailing list
>> >>>
>> >>>   >>>>>> tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >>>
>> >>>   >>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>
>> >>>
>> >>>   >>>>>_______________________________________________
>> >>>
>> >>>   >>>>>tcmtf mailing list
>> >>>
>> >>>   >>>>>tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >>>
>> >>>   >>>>>https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>> ________________________________
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>> Este mensaje se dirige exclusivamente a su destinatario.
>> >>> Puede
>> >>>
>> >>>   >>>> consultar 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
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>
>> >>>
>> >>>   >>>
>> >>>
>> >>>   >>
>> >>>
>> >>>   >>
>> >>>
>> >>>   >> ________________________________
>> >>>
>> >>>   >>
>> >>>
>> >>>   >> Este mensaje se dirige exclusivamente a su destinatario. Puede
>> >>>
>> >>>   >> consultar nuestra polÃ­tica de envÃ­o y recepciÃ³n de correo
>> >>>
>> >>>   >> electrÃ³nico en el enlace situado mÃ¡s abajo.
>> >>>
>> >>>   >> This message is intended exclusively for its addressee. We only
>> >>> send
>> >>>
>> >>>   >> and receive email on the basis of the terms set out at:
>> >>>
>> >>>   >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> >>>
>> >>>   >>
>> >>>
>> >>>   >
>> >>>
>> >>>   >
>> >>>
>> >>>   >
>> >>>
>> >>>   >_______________________________________________
>> >>>
>> >>>   >tcmtf mailing list
>> >>>
>> >>>   >tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >>>
>> >>>   >https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>
>> >>> ________________________________
>> >>>
>> >>> Este mensaje se dirige exclusivamente a su destinatario. Puede
>> >>> consultar nuestra política de envío y recepción de correo
>> >>> electrónico en el enlace situado más abajo.
>> >>>
>> >>> This message is intended exclusively for its addressee. We only send
>> >>> and receive email on the basis of the terms set out at:
>> >>>
>> >>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> >>>
>> >>> _______________________________________________
>> >>>
>> >>> tcmtf mailing list
>> >>>
>> >>> tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >>>
>> >>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> tcmtf mailing list
>> >>> tcmtf@ietf.org
>> >>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>
>> >>
>> >> _______________________________________________
>> >> tcmtf mailing list
>> >> tcmtf@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/tcmtf
>> >
>> > _______________________________________________
>> > tcmtf mailing list
>> > tcmtf@ietf.org
>> > https://www.ietf.org/mailman/listinfo/tcmtf
>> >
>>
>> _______________________________________________
>> 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 Oct  1 06:01:02 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 C334311E8121 for <tcmtf@ietfa.amsl.com>; Mon,  1 Oct 2012 06:01:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.117
X-Spam-Level: 
X-Spam-Status: No, score=-6.117 tagged_above=-999 required=5 tests=[AWL=0.482,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xxesAwcKbsqJ for <tcmtf@ietfa.amsl.com>; Mon,  1 Oct 2012 06:01:00 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id DAF7811E8169 for <tcmtf@ietf.org>; Mon,  1 Oct 2012 06:00:59 -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 q91D0lhb021747; Mon, 1 Oct 2012 15:00:47 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <Matteo.Berioli@dlr.de>
References: <003101cd9d62$c803f1f0$580bd5d0$@unizar.es>	<506592DF.7070508@erg.abdn.ac.uk>	<004701cd9fbd$a0a1b540$e1e51fc0$@unizar.es> <c898f337fd617ee9fe1a49b9ac8d35e9.squirrel@www.erg.abdn.ac.uk> <48DB40641BACF54C892EB0A12B4733C10BE7A901@dlrexmbx02.intra.dlr.de>
In-Reply-To: <48DB40641BACF54C892EB0A12B4733C10BE7A901@dlrexmbx02.intra.dlr.de>
Date: Mon, 1 Oct 2012 15:00:53 +0200
Organization: Universidad de Zaragoza
Message-ID: <005b01cd9fd4$c9fb86c0$5df29440$@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: AQHVprSodD9UYB0w1jP2flEMIsTifgI+jB+cAlPREpwA9XgP9wGiKRZwl1sJ5LA=
Content-language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] More satellite scenarios
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2012 13:01:03 -0000

Tomaso,

I think you are correct. TCMTF is interesting when the satellite link is =
not
the only hop.

The question is: are there real sensor networks in which IP is =
necessary?

Some possible examples (please tell me if some of them exist in the real
world):

- Cameras or more complicated sensors generating IP packets
- Different groups of sensors which share the same satellite link to =
deliver
their data to the server, so you need IP in order to distinguish between
them
- Sensors sending data to different destination servers

Thanks,

Jose

> -----Mensaje original-----
> De: Matteo.Berioli@dlr.de [mailto:Matteo.Berioli@dlr.de]
> Enviado el: lunes, 01 de octubre de 2012 14:41
> Para: gorry@erg.abdn.ac.uk; jsaldana@unizar.es
> CC: tcmtf@ietf.org
> Asunto: RE: [tcmtf] More satellite scenarios
>=20
> If I understand it right we have a proposal for tunneling, =
multiplexing,
> (header-)compressing general IP flows, which clearly brings gains for
short
> packets.
> As Gorry said, multiplexing is basically already done below IP in sat
networks,
> and header compression can always be added on top.
> So the only need for doing this above IP and tunnel it (i.e. this
proposal) is
> when the IP links extend beyond the sat link on one or both sides.
> Is this correct?
>=20
>=20
> -----Original Message-----
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
> Of gorry@erg.abdn.ac.uk
> Sent: 01 October 2012 12:30
> To: jsaldana@unizar.es
> Cc: gorry@erg.abdn.ac.uk; tcmtf@ietf.org
> Subject: Re: [tcmtf] More satellite scenarios
>=20
> That is what I think - the proposed tunnel method does not seem to =
have
> advantage when used over a single link.
>=20
> Gorry
>=20
> > Gorry,
> >
> > The question here is that perhaps the scenario of the sensor network
> > in
> > =
http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scenario.pd
> > f
> > was
> > too simplistic, and TCMTF made no sense for it, since the use of IP
> > would not be necessary, as you remarked. There are more interesting
> > compressing options for that scenario. Am I correct?
> >
> > Thanks for your feedback,
> >
> > Jose
> >
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> >> de Gorry Fairhurst Enviado el: viernes, 28 de septiembre de 2012
> >> 14:07
> >> Para: tcmtf@ietf.org
> >> Asunto: Re: [tcmtf] More satellite scenarios
> >>
> >> I did not dispute the use of VoIP and other "small packet" services
> >> over satellite (I work on this subject). What I wanted to =
understand
> >> was why ROHC or RFC 3545 (e.g. for VoIP) was not applicable.
> >>
> >> Gorry
> >>
> >> On 28/09/2012 11:19, Jose Saldana wrote:
> >> > We have to continue the discussion about satellite scenarios with
> >> > sensor
> >> > networks: if possible, I would like to hear the opinion of people
> >> > from DLR about this.
> >> >
> >> >
> >> > However, I have found more satellite-related scenarios in which a
> >> > number of small-packet flows can be present:
> >> >
> >> > - A cruise: lots of people (3800 people in Queen Mary 2) =
connected
> >> > through a satellite link
> >> >
> >> >
> >>
> http://www.cruisemates.com/articles/onboard/connected.cfm#axzz27l0sEq
> >> u
> >> > 3
> >> > http://en.wikipedia.org/wiki/RMS_Queen_Mary_2
> >> > http://www.esa.int/esaTE/SEMMAWNFGLE_index_0.html
> >> >
> >> >
> >> > - A plane: similar to the ship, but less people and no satellite,
> >> > but ground antennas communicating with a special antenna on the
> >> > plane (VoIP is prohibited by now):
> >> > http://en.wikipedia.org/wiki/Gogo_Inflight_Internet
> >> >
> >> >
> >> > - Satellite access in low-populated regions (e.g. Alaska): =
Perhaps
> >> > a number of people, or a village, may share a  connection through
> >> > an
> >> antenna:
> >> > =
http://www.skycasters.com/satellite-internet-coverage/skycasters-co
> >> > ver
> >> > age-Al
> >> > aska.html
> >> >
> >> >
> >> > What do you think?
> >> >
> >> > Best regards,
> >> >
> >> > Jose
> >> >
> >> >> -----Mensaje original-----
> >> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> >> nombre de Gorry Fairhurst Enviado el: viernes, 21 de septiembre =
de
> >> >> 2012
> >> >> 10:29
> >> >> Para: jsaldana@unizar.es
> >> >> CC: tcmtf@ietf.org; 'FERNANDO PASCUAL BLANCO'
> >> >> Asunto: Re: [tcmtf] Discussing M2M scenario and savings -
> >> >> continuing the thread
> >> >>
> >> >> I think *IF* the satellite link is a DVB 2nd generation RF link,
e.g.
> >> >> DVB-S2 for satellite ( a common waveform), then GSE + RFC 5163 =
is
> >> >> a reasonable proposal, on which one may benefit if one layers a =
HC
> >> >> scheme, such as ROHC, or 6LoWPAN. The profile for the  ROHC
> >> >> schemes have not been specified for this type of link - but the
> >> >> relevant RFCs exist for the compression itself. RFC 3135 and RFC
> >> >> 3449 also describe TCP/IP techniques
> >> > to
> >> >> help improve efficiency on such links.
> >> >>
> >> >> As I said, I do not see the *benefit* for the mux and demux in =
the
> >> > scenario
> >> >> as drawn, since this seems more like *link* HC, and it would =
seem
> >> >> foolish
> >> > to
> >> >> form aggregate traffic over a single link layer in the way that
> >> >> tunnel compression implements this.
> >> >>
> >> >> If the drawing extended the network on one or both sides of the
> >> >> satellite link, there could be a reason for using tunnel HC,
> >> >> although I am not sure whether this is commercially important,
> >> >> since unlike an access network,
> >> > the
> >> >> connectivity to the hub (usually known as the satellite gateway)
> >> >> on the
> >> > left of
> >> >> the figure is not usually a low speed access link and the merits
> >> >> of HC is
> >> > less
> >> >> obvious where bandwidth is high. Also, it would seem desirable =
to
> >> >> use encapsulation and HC mechanisms on the satellite air =
interface
> >> >> anyway, RFC
> >> >> 3135 part 3 (from the source), possibly combined with RFC 3449
> >> mechanisms.
> >> >>
> >> >> All I am saying is you have to be sure to describe the scenario
> >> >> carefully
> >> > and
> >> >> explain why HC applies in this case and what alternatives exist.
> >> >>
> >> >> Gorry
> >> >>
> >> >> On 20/09/2012 17:20, Jose Saldana wrote:
> >> >>> So, do you think the figure should be modified? Perhaps it is
> >> >>> currently confusing, since it seems that RFC 5163 is the best
> >> >>> solution. Perhaps a network should be included between the =
demux
> >> and
> >> >>> the data center? Or between the antenna and the demux? Will =
this
> >> >>> be a real case? I don't know if in the right side it is =
possible
> >> >>> to find
> >> > other
> >> >> networks.
> >> >>>
> >> >>> I am talking about this figure:
> >> >>>
> >> >>>
> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scenario.
> >> >>> pd
> >> >>> f
> >> >>>
> >> >>> Thanks,
> >> >>>
> >> >>> Jose
> >> >>>
> >> >>> -----Mensaje original-----
> >> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> nombre
> >> >>> de FERNANDO PASCUAL BLANCO Enviado el: mi=E9rcoles, 19 de
> >> septiembre
> >> >> de
> >> >>> 2012 13:02
> >> >>> Para: gorry@erg.abdn.ac.uk; tcmtf@ietf.org
> >> >>> Asunto: Re: [tcmtf] Discussing M2M scenario and savings -
> >> >>> continuing the thread
> >> >>>
> >> >>> Hi Gorry,
> >> >>>
> >> >>>           Absolutely. The tunneling layer would increase that
> >> >>> benefit in a multi-router hop path, being the satellite-link =
part
> >> >>> of
> > this
> >> path.
> >> >>>
> >> >>> Regards,
> >> >>>
> >> >>> Fernando Pascual Blanco
> >> >>>
> >> >>> Telef=F3nica Global Resources
> >> >>>
> >> >>> Network Automation and Dynamization
> >> >>>
> >> >>> TECHNOLOGY PEOPLE GROUP
> >> >>>
> >> >>> F +34913128779
> >> >>>
> >> >>> M +34682005168
> >> >>>
> >> >>> fpb@tid.es <mailto:fpb@tid.es>
> >> >>>
> >> >>> On 19/09/12 12:37, "gorry@erg.abdn.ac.uk
> >> >> <mailto:gorry@erg.abdn.ac.uk>"
> >> >>> <gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>> wrote:
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >For a point-to-point link carrying traffic destined to a =
ingle
> >> >>> L2
> >> >>>
> >> >>>   >address, I don't see how this helps above the gains of ROHC =
or
> >> >>> some
> >> >>>
> >> >>>   >other HC on the link, when possibly combining this with link
> >> >>> layer
> >> >>>
> >> >>>   >transmission options e.g. methods like PDU-CONCAT in RFC =
5163.
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >If you're working over a multi-router network hop, the
> >> >>> considerations
> >> >>>
> >> >>>   >may be different.
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >Gorry
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >> Hi Gorry,
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >>         I don=C2=B4t know a lot about link layer HC, but I =
imagine
> > that
> >> >>>
> >> >>>   >> it compress packet headers (IP-TCP/UDP). If, in addition =
to
> >> >>> that, we
> >> >>>
> >> >>>   >> group several small packets into a bigger one (using =
PPP-Mux
> >> >>> and
> >> >>>
> >> >>>   >> RoHC), don=C2=B4t you think more resources could be saved?
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >> Regards,
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >> Fernando Pascual Blanco
> >> >>>
> >> >>>   >> Telef=C3=B3nica Global Resources
> >> >>>
> >> >>>   >> Network Automation and Dynamization
> >> >>>
> >> >>>   >> TECHNOLOGY PEOPLE GROUP
> >> >>>
> >> >>>   >> F +34913128779
> >> >>>
> >> >>>   >> M +34682005168
> >> >>>
> >> >>>   >> fpb@tid.es <mailto:fpb@tid.es>
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >> On 19/09/12 10:56, "gorry@erg.abdn.ac.uk
> >> >>> <mailto:gorry@erg.abdn.ac.uk>" <gorry@erg.abdn.ac.uk
> >> >>> <mailto:gorry@erg.abdn.ac.uk>> wrote:
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >>>I know there are applications for tunnel compression - but
> >> >>> I'm not
> >> >>>
> >> >>>   >>>sure  I understand how this can gain further than for
> >> link-layer
> > HC?
> >> >>>
> >> >>>   >>>
> >> >>>
> >> >>>   >>>Gorry
> >> >>>
> >> >>>   >>>
> >> >>>
> >> >>>   >>>> Hi Gorry,
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>>         In addition of HC (header compression), the
> > multiplexing
> >> >>>
> >> >>>   >>>> layer will save even more resources. In that case and
> >> >>> assuming that
> >> >>>
> >> >>>   >>>> all the traffic through the link have the same QoS
> >> >>> requirements
> >> >>>
> >> >>>   >>>> (for example a sensor network), the idea would be to =
group
> >> >>> all the
> >> >>>
> >> >>>   >>>> flows through the link (the bottleneck).
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>> Regards,
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>> Fernando Pascual Blanco
> >> >>>
> >> >>>   >>>> Telef=C3=B3nica Global Resources
> >> >>>
> >> >>>   >>>> Network Automation and Dynamization TECHNOLOGY PEOPLE
> >> >> GROUP F
> >> >>>
> >> >>>   >>>> +34913128779 M +34682005168 fpb@tid.es
> <mailto:fpb@tid.es>
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>> On 18/09/12 20:46, "Gorry Fairhurst" =
<gorry@erg.abdn.ac.uk
> >> >>> <mailto:gorry@erg.abdn.ac.uk>> wrote:
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>>>A satellite "link" may provide HC, at least some of the
> >> >>> ones I have
> >> >>>
> >> >>>   >>>>>seen do. In this case, the flows can easily be grouped =
by
> >> >>> mac
> >> >>>
> >> >>>   >>>>>address?
> >> >>>
> >> >>>   >>>>>
> >> >>>
> >> >>>   >>>>>Gorry
> >> >>>
> >> >>>   >>>>>
> >> >>>
> >> >>>   >>>>>On 13/09/2012 16:20, Jose Saldana wrote:
> >> >>>
> >> >>>   >>>>>> Hi, Fernando, sorry for the delay (one week, I=C2=B9m =
afraid).
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> I don=C2=B9t know who is the one interested on using =
TCMTF:
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> -If you are a costumer, and you have to pay for a
> >> >>> satellite link
> >> >>>
> >> >>>   >>>>>>or  a  long distance wire, perhaps you are the one
> >> >>> interested on
> >> >>>
> >> >>>   >>>>>>using  end-to-end TCMTF, since you will save bandwidth =
or
> >> >>> packets
> >> >>>
> >> >>>   >>>>>>per  second  or  money. If you have e.g. two offices, =
one
> >> >>> in
> >> >>>
> >> >>>   >>>>>>America and other one in  Europe, you may be interested
> >> >>> on placing
> >> >>>
> >> >>>   >>>>>>a device for multiplexing a  number of VoIP calls =
between
> > them.
> >> >>>
> >> >>>   >>>>>>You have one advantage: the flows  have the same origin
> >> >>> and
> >> >>>
> >> >>>   >>>>>>destination, so header compression is effective.
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> -If you are the operator of the satellite, you have
> >> >>> another
> >> >> problem:
> >> >>>
> >> >>>   >>>>>> you
> >> >>>
> >> >>>   >>>>>> may have to check every flow, and try to group them.
> >> >>> Perhaps it
> >> >>>
> >> >>>   >>>>>> may be easy, but if you want to save headers, you need
> >> >>> flows with
> >> >>>
> >> >>>   >>>>>> the same origin and destination.
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> I think that there are different scenarios, and each
> >> >>> =C2=B3actor=C2=B2
> >> >>>
> >> >>>   >>>>>>may  try to  use TCMTF in the best place: a high number
> >> >>> of flows,
> >> >>>
> >> >>>   >>>>>>with small  packets,  and sharing the same origin and
> >> > destination.
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Do you agree?
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Jose
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> *De:*tcmtf-bounces@ietf.org [mailto:tcmtf-
> >> bounces@ietf.org]
> >> >>> <mailto:[mailto:tcmtf-bounces@ietf.org]> *En
> >> >>>
> >> >>>   >>>>>> nombre de *FERNANDO PASCUAL BLANCO *Enviado el:*
> >> martes,
> >> >> 04 de
> >> >>>
> >> >>>   >>>>>> septiembre de 2012 12:27
> >> >>>
> >> >>>   >>>>>> *Para:* tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >> >>>
> >> >>>   >>>>>> *Asunto:* Re: [tcmtf] Discussing M2M scenario and
> >> >>> savings
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Hi all,
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Yes, M2M sensor networks are a very good example in
> >> >>> order to save
> >> >>>
> >> >>>   >>>>>> bandwidth in long distance/big latency/low bandwidth
> >> >>> links, links
> >> >>>
> >> >>>   >>>>>> were the cost per bit is high. Do you think network
> >> >>> carriers
> >> >>>
> >> >>>   >>>>>> operating this kind of links (satellite links or long
> >> >>> distance
> >> >>>
> >> >>>   >>>>>> wires) would be interested in apply TCMTF?
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Regards,
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Fernando
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> *From:*tcmtf-bounces@ietf.org <mailto:tcmtf-
> >> >> bounces@ietf.org>
> >> >>>
> >> >>>   >>>>>> [mailto:tcmtf-bounces@ietf.org]
> >> >>> <mailto:[mailto:tcmtf-bounces@ietf.org]>
> >> >>>
> >> >>>   >>>>>> <mailto:[mailto:tcmtf-bounces@ietf.org]>
> >> >>>
> >> >>>   >>>>>> *On Behalf Of *Jose Saldana
> >> >>>
> >> >>>   >>>>>> *Sent:* martes, 04 de septiembre de 2012 9:41
> >> >>>
> >> >>>   >>>>>> *To:* tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >> >>> <mailto:tcmtf@ietf.org>
> >> >>>
> >> >>>   >>>>>> *Cc:* Matteo.Berioli@dlr.de
> >> >>> <mailto:Matteo.Berioli@dlr.de> <mailto:Matteo.Berioli@dlr.de>;
> >> >>>
> >> >>>   >>>>>> Tomaso.deCola@dlr.de <mailto:Tomaso.deCola@dlr.de>
> >> >>> <mailto:Tomaso.deCola@dlr.de>
> >> >>>
> >> >>>   >>>>>> *Subject:* [tcmtf] Discussing M2M scenario and savings
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Hi again,
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> We already discussed some points about the M2M =
scenario
> >> >>> at the
> >> >>>
> >> >>>   >>>>>>beginning  of August. We are currently studying this, =
and
> >> >>> we have
> >> >>>
> >> >>>   >>>>>>built some  figures, in collaboration with people from
> >> >>> DLR (Tomaso
> >> >>>
> >> >>>   >>>>>>and Matteo).
> >> >>>
> >> >>>   >>>>>>You
> >> >>>
> >> >>>   >>>>>> can find the figures here:
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>>>>>>
> >> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_savi
> >> >>>>>>>> n
> >> >>> gs
> >> >>>
> >> >>>   >>>>>>.pd
> >> >>>
> >> >>>   >>>>>>f
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>>>>>>
> >> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scen
> >> >>>>>>>> a
> >> >>> ri
> >> >>>
> >> >>>   >>>>>>o.p
> >> >>>
> >> >>>   >>>>>>df
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Perhaps we could comment them, in order to discuss =
this
> >> >>> scenario,
> >> >>>
> >> >>>   >>>>>> and we may find new ones in which TCMTF can be useful.
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Thanks,
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Jose
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>
> >> >>>>>>>>> =
-----------------------------------------------------------
> >> >>>>>>>>> ---
> >> >>>>>>>>> --
> >> >>> --
> >> >>>
> >> >>>   >>>>>>---
> >> >>>
> >> >>>   >>>>>>--
> >> >>>
> >> >>>   >>>>>>-
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Este mensaje se dirige exclusivamente a su =
destinatario.
> >> >>> Puede
> >> >>>
> >> >>>   >>>>>> consultar nuestra pol=C3=ADtica de env=C3=ADo y =
recepci=C3=B3n de
> >> >>> correo
> >> >>>
> >> >>>   >>>>>> electr=C3=B3nico en el enlace situado m=C3=A1s abajo.
> >> >>>
> >> >>>   >>>>>> This message is intended exclusively for its =
addressee.
> >> >>> We only
> >> >>>
> >> >>>   >>>>>> send and receive email on the basis of the terms set =
out
> >> at:
> >> >>>
> >> >>>   >>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> _______________________________________________
> >> >>>
> >> >>>   >>>>>> tcmtf mailing list
> >> >>>
> >> >>>   >>>>>> tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >> >>>
> >> >>>   >>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>
> >> >>>
> >> >>>   >>>>>_______________________________________________
> >> >>>
> >> >>>   >>>>>tcmtf mailing list
> >> >>>
> >> >>>   >>>>>tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >> >>>
> >> >>>   >>>>>https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>> ________________________________
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>> Este mensaje se dirige exclusivamente a su destinatario.
> >> >>> Puede
> >> >>>
> >> >>>   >>>> consultar nuestra pol=C3=ADtica de env=C3=ADo y =
recepci=C3=B3n de
> >> >>> correo
> >> >>>
> >> >>>   >>>> electr=C3=B3nico en el enlace situado m=C3=A1s 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
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>
> >> >>>
> >> >>>   >>>
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >> ________________________________
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >> Este mensaje se dirige exclusivamente a su destinatario.
> >> >>> Puede
> >> >>>
> >> >>>   >> consultar nuestra pol=C3=ADtica de env=C3=ADo y =
recepci=C3=B3n de correo
> >> >>>
> >> >>>   >> electr=C3=B3nico en el enlace situado m=C3=A1s abajo.
> >> >>>
> >> >>>   >> This message is intended exclusively for its addressee. We
> >> >>> only send
> >> >>>
> >> >>>   >> and receive email on the basis of the terms set out at:
> >> >>>
> >> >>>   >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >_______________________________________________
> >> >>>
> >> >>>   >tcmtf mailing list
> >> >>>
> >> >>>   >tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >> >>>
> >> >>>   >https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>
> >> >>> ________________________________
> >> >>>
> >> >>> Este mensaje se dirige exclusivamente a su destinatario. Puede
> >> >>> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo
> >> >>> electr=F3nico en el enlace situado m=E1s abajo.
> >> >>>
> >> >>> This message is intended exclusively for its addressee. We only
> >> >>> send and receive email on the basis of the terms set out at:
> >> >>>
> >> >>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >> >>>
> >> >>> _______________________________________________
> >> >>>
> >> >>> tcmtf mailing list
> >> >>>
> >> >>> tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >> >>>
> >> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>
> >> >>>
> >> >>>
> >> >>> _______________________________________________
> >> >>> tcmtf mailing list
> >> >>> tcmtf@ietf.org
> >> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>
> >> >>
> >> >> _______________________________________________
> >> >> tcmtf mailing list
> >> >> tcmtf@ietf.org
> >> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >
> >> > _______________________________________________
> >> > tcmtf mailing list
> >> > tcmtf@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/tcmtf
> >> >
> >>
> >> _______________________________________________
> >> tcmtf mailing list
> >> tcmtf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >
> > _______________________________________________
> > tcmtf mailing list
> > tcmtf@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcmtf
> >
>=20
>=20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From mns@tid.es  Mon Oct  1 07:06:17 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 125501F0E5F for <tcmtf@ietfa.amsl.com>; Mon,  1 Oct 2012 07:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7iQV-BoPrEIn for <tcmtf@ietfa.amsl.com>; Mon,  1 Oct 2012 07:06:14 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id AC81711E8254 for <tcmtf@ietf.org>; Mon,  1 Oct 2012 07:05:04 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MB700389WG9FF@tid.hi.inet> for tcmtf@ietf.org; Mon, 01 Oct 2012 16:05:03 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id D0.7C.03050.F03A9605; Mon, 01 Oct 2012 16:05:03 +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 <0MB70030FWGEE5@tid.hi.inet> for tcmtf@ietf.org; Mon, 01 Oct 2012 16:05:03 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.209]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0318.001; Mon, 01 Oct 2012 16:03:57 +0200
Date: Mon, 01 Oct 2012 14:03:56 +0000
From: =?iso-8859-1?Q?MANUEL_NU=D1EZ_SANZ?= <mns@tid.es>
In-reply-to: <c898f337fd617ee9fe1a49b9ac8d35e9.squirrel@www.erg.abdn.ac.uk>
X-Originating-IP: [10.95.64.115]
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Message-id: <90ED8822CB577741B9A1668A4753931218F47F75@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: es-ES
Content-transfer-encoding: quoted-printable
Accept-Language: es-ES, en-US
Thread-topic: [tcmtf] More satellite scenarios
Thread-index: Ac2dYUy6uVqP4M0WSN+HUIzF9jzvbP///2CAgASXwICAAAQigP//sbcg
X-AuditID: 0a5f4068-b7f176d000000bea-87-5069a30f39ef
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrEJsWRmVeSWpSXmKPExsXCFe/Apcu/ODPAYPJ3XotdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoErY8tUtoLPixgrHra3MDYwXq7rYuTkkBAwkWi5MJkZwhaTuHBv PVsXIxeHkMBGRonenUcZIZyfjBKrJ15lgXBmMkps7JrIAtLCIqAqMXtzN5DNwcEmYC7Rt44H JCwsoCtx+0s/O4jNKeAtcXnPUiaIDQoSf849BmsVEYiTOP37OitIKzPQmHnfFEHCvEDl36ed Z4KwBSV+TL4HVs4soCPR+/0bM4QtLjHn10RWCFtb4sm7C2A2o4CsxMrzpxkhxutJrDs2jwnC dpO4dWo51JMCEkv2nIeyRSVePv7HCvHWCUaJRdsfsU9gFJ+FZPcsJLtnIdk9C8nuBYwsqxjF ipOKMtMzSnITM3PSDQz1MjL1MvNSSzYxQuIoYwfj8p0qhxgFOBiVeHh/LEwIEGJNLCuuzD3E aMnBpCTKu39eZoAQX1J+SmVGYnFGfFFpTmqxkhxvrztQWBwuXFxaXJCZnJlfWhxfWpRziFGC g1lJhNc+B6iINyWxsiq1KB+i9RCjPQeHkgTvqYVAKcGi1PTUirTMHGCygZqsyKu4Oi1ASApZ Bt1wJg7OQ4zmHDxAG3aDjOEtLkjMLc5Mhxohy/sZ5DgxmCiq9lOM7hyzpyx5wCjEkpeflyol zrsdZIYASHVGaR7cJVIKvN9XAV0iiSSBatIrRlNgoAnzLgTp5wGmfYQTZHhPMWYECIlCBdH1 mQNDVoS3CmQ8b3FJYgmy26+ARMVgoqg6pRoYs1S9fU8VX5rzJabUSOqOWbczx3aXvh2zRdi6 c+oFfty/s8zPemVuddy/BdHChk/2Wus33dJ6f5tjGpdPiTOjUbkow8LnKsuS1ZZ5h7ZYP/ta X3NN/w1Tzo2ULVcSzDrnFZ3W3T9nsZqJl2zx01qzm1NuXT3z8ZHrIT+J+7J7T4d3v1I7tGGL EktxRqKhFnNRcSIAAUDHAvUDAAA=
References: <003101cd9d62$c803f1f0$580bd5d0$@unizar.es> <506592DF.7070508@erg.abdn.ac.uk> <004701cd9fbd$a0a1b540$e1e51fc0$@unizar.es> <c898f337fd617ee9fe1a49b9ac8d35e9.squirrel@www.erg.abdn.ac.uk>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] More satellite scenarios
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2012 14:06:17 -0000

Yes, I agree with both and the scenario is raised too simple, and the main =
advantages are obtained when there are several networks after the satellite=
 link and the mux-demux is made end to end.
I am going to describe it with an example. Imagine a group of M2M sensors w=
ith a mux close to gateway (as in the figure), for example sensors in natur=
al parks around Europe to prevent fires. Each group of these sensors send t=
heir data through a satellite link to a next hop, and from there the data a=
re sent to centralized data center in Brussels (for example) to process, to=
 analyze and to take decisions. The demux should be located just across tha=
t data center.

Manuel.


-----Mensaje original-----
De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de gor=
ry@erg.abdn.ac.uk
Enviado el: lunes, 01 de octubre de 2012 12:30
Para: jsaldana@unizar.es
CC: gorry@erg.abdn.ac.uk; tcmtf@ietf.org
Asunto: Re: [tcmtf] More satellite scenarios

That is what I think - the proposed tunnel method does not seem to have adv=
antage when used over a single link.

Gorry

> Gorry,
>
> The question here is that perhaps the scenario of the sensor network
> in
> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scenario.pd
> f
> was
> too simplistic, and TCMTF made no sense for it, since the use of IP
> would not be necessary, as you remarked. There are more interesting
> compressing options for that scenario. Am I correct?
>
> Thanks for your feedback,
>
> Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>> de Gorry Fairhurst Enviado el: viernes, 28 de septiembre de 2012
>> 14:07
>> Para: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] More satellite scenarios
>>
>> I did not dispute the use of VoIP and other "small packet" services
>> over satellite (I work on this subject). What I wanted to understand
>> was why ROHC or RFC 3545 (e.g. for VoIP) was not applicable.
>>
>> Gorry
>>
>> On 28/09/2012 11:19, Jose Saldana wrote:
>> > We have to continue the discussion about satellite scenarios with
>> > sensor
>> > networks: if possible, I would like to hear the opinion of people
>> > from DLR about this.
>> >
>> >
>> > However, I have found more satellite-related scenarios in which a
>> > number of small-packet flows can be present:
>> >
>> > - A cruise: lots of people (3800 people in Queen Mary 2) connected
>> > through a satellite link
>> >
>> >
>> http://www.cruisemates.com/articles/onboard/connected.cfm#axzz27l0sEq
>> u
>> > 3
>> > http://en.wikipedia.org/wiki/RMS_Queen_Mary_2
>> > http://www.esa.int/esaTE/SEMMAWNFGLE_index_0.html
>> >
>> >
>> > - A plane: similar to the ship, but less people and no satellite,
>> > but ground antennas communicating with a special antenna on the
>> > plane (VoIP is prohibited by now):
>> > http://en.wikipedia.org/wiki/Gogo_Inflight_Internet
>> >
>> >
>> > - Satellite access in low-populated regions (e.g. Alaska): Perhaps
>> > a number of people, or a village, may share a  connection through
>> > an
>> antenna:
>> > http://www.skycasters.com/satellite-internet-coverage/skycasters-co
>> > ver
>> > age-Al
>> > aska.html
>> >
>> >
>> > What do you think?
>> >
>> > Best regards,
>> >
>> > Jose
>> >
>> >> -----Mensaje original-----
>> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> >> nombre de Gorry Fairhurst Enviado el: viernes, 21 de septiembre de
>> >> 2012
>> >> 10:29
>> >> Para: jsaldana@unizar.es
>> >> CC: tcmtf@ietf.org; 'FERNANDO PASCUAL BLANCO'
>> >> Asunto: Re: [tcmtf] Discussing M2M scenario and savings -
>> >> continuing the thread
>> >>
>> >> I think *IF* the satellite link is a DVB 2nd generation RF link, e.g.
>> >> DVB-S2 for satellite ( a common waveform), then GSE + RFC 5163 is
>> >> a reasonable proposal, on which one may benefit if one layers a HC
>> >> scheme, such as ROHC, or 6LoWPAN. The profile for the  ROHC
>> >> schemes have not been specified for this type of link - but the
>> >> relevant RFCs exist for the compression itself. RFC 3135 and RFC
>> >> 3449 also describe TCP/IP techniques
>> > to
>> >> help improve efficiency on such links.
>> >>
>> >> As I said, I do not see the *benefit* for the mux and demux in the
>> > scenario
>> >> as drawn, since this seems more like *link* HC, and it would seem
>> >> foolish
>> > to
>> >> form aggregate traffic over a single link layer in the way that
>> >> tunnel compression implements this.
>> >>
>> >> If the drawing extended the network on one or both sides of the
>> >> satellite link, there could be a reason for using tunnel HC,
>> >> although I am not sure whether this is commercially important,
>> >> since unlike an access network,
>> > the
>> >> connectivity to the hub (usually known as the satellite gateway)
>> >> on the
>> > left of
>> >> the figure is not usually a low speed access link and the merits
>> >> of HC is
>> > less
>> >> obvious where bandwidth is high. Also, it would seem desirable to
>> >> use encapsulation and HC mechanisms on the satellite air interface
>> >> anyway, RFC
>> >> 3135 part 3 (from the source), possibly combined with RFC 3449
>> mechanisms.
>> >>
>> >> All I am saying is you have to be sure to describe the scenario
>> >> carefully
>> > and
>> >> explain why HC applies in this case and what alternatives exist.
>> >>
>> >> Gorry
>> >>
>> >> On 20/09/2012 17:20, Jose Saldana wrote:
>> >>> So, do you think the figure should be modified? Perhaps it is
>> >>> currently confusing, since it seems that RFC 5163 is the best
>> >>> solution. Perhaps a network should be included between the demux
>> and
>> >>> the data center? Or between the antenna and the demux? Will this
>> >>> be a real case? I don't know if in the right side it is possible
>> >>> to find
>> > other
>> >> networks.
>> >>>
>> >>> I am talking about this figure:
>> >>>
>> >>> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scenario.
>> >>> pd
>> >>> f
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Jose
>> >>>
>> >>> -----Mensaje original-----
>> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> nombre
>> >>> de FERNANDO PASCUAL BLANCO Enviado el: mi=E9rcoles, 19 de
>> septiembre
>> >> de
>> >>> 2012 13:02
>> >>> Para: gorry@erg.abdn.ac.uk; tcmtf@ietf.org
>> >>> Asunto: Re: [tcmtf] Discussing M2M scenario and savings -
>> >>> continuing the thread
>> >>>
>> >>> Hi Gorry,
>> >>>
>> >>>           Absolutely. The tunneling layer would increase that
>> >>> benefit in a multi-router hop path, being the satellite-link part
>> >>> of
> this
>> path.
>> >>>
>> >>> Regards,
>> >>>
>> >>> Fernando Pascual Blanco
>> >>>
>> >>> Telef=F3nica Global Resources
>> >>>
>> >>> Network Automation and Dynamization
>> >>>
>> >>> TECHNOLOGY PEOPLE GROUP
>> >>>
>> >>> F +34913128779
>> >>>
>> >>> M +34682005168
>> >>>
>> >>> fpb@tid.es <mailto:fpb@tid.es>
>> >>>
>> >>> On 19/09/12 12:37, "gorry@erg.abdn.ac.uk
>> >> <mailto:gorry@erg.abdn.ac.uk>"
>> >>> <gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>> wrote:
>> >>>
>> >>>   >
>> >>>
>> >>>   >For a point-to-point link carrying traffic destined to a ingle
>> >>> L2
>> >>>
>> >>>   >address, I don't see how this helps above the gains of ROHC or
>> >>> some
>> >>>
>> >>>   >other HC on the link, when possibly combining this with link
>> >>> layer
>> >>>
>> >>>   >transmission options e.g. methods like PDU-CONCAT in RFC 5163.
>> >>>
>> >>>   >
>> >>>
>> >>>   >If you're working over a multi-router network hop, the
>> >>> considerations
>> >>>
>> >>>   >may be different.
>> >>>
>> >>>   >
>> >>>
>> >>>   >Gorry
>> >>>
>> >>>   >
>> >>>
>> >>>   >> Hi Gorry,
>> >>>
>> >>>   >>
>> >>>
>> >>>   >>         I don=C2=B4t know a lot about link layer HC, but I imag=
ine
> that
>> >>>
>> >>>   >> it compress packet headers (IP-TCP/UDP). If, in addition to
>> >>> that, we
>> >>>
>> >>>   >> group several small packets into a bigger one (using PPP-Mux
>> >>> and
>> >>>
>> >>>   >> RoHC), don=C2=B4t you think more resources could be saved?
>> >>>
>> >>>   >>
>> >>>
>> >>>   >> Regards,
>> >>>
>> >>>   >>
>> >>>
>> >>>   >> Fernando Pascual Blanco
>> >>>
>> >>>   >> Telef=C3=B3nica Global Resources
>> >>>
>> >>>   >> Network Automation and Dynamization
>> >>>
>> >>>   >> TECHNOLOGY PEOPLE GROUP
>> >>>
>> >>>   >> F +34913128779
>> >>>
>> >>>   >> M +34682005168
>> >>>
>> >>>   >> fpb@tid.es <mailto:fpb@tid.es>
>> >>>
>> >>>   >>
>> >>>
>> >>>   >>
>> >>>
>> >>>   >>
>> >>>
>> >>>   >>
>> >>>
>> >>>   >> On 19/09/12 10:56, "gorry@erg.abdn.ac.uk
>> >>> <mailto:gorry@erg.abdn.ac.uk>" <gorry@erg.abdn.ac.uk
>> >>> <mailto:gorry@erg.abdn.ac.uk>> wrote:
>> >>>
>> >>>   >>
>> >>>
>> >>>   >>>I know there are applications for tunnel compression - but
>> >>> I'm not
>> >>>
>> >>>   >>>sure  I understand how this can gain further than for
>> link-layer
> HC?
>> >>>
>> >>>   >>>
>> >>>
>> >>>   >>>Gorry
>> >>>
>> >>>   >>>
>> >>>
>> >>>   >>>> Hi Gorry,
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>>         In addition of HC (header compression), the
> multiplexing
>> >>>
>> >>>   >>>> layer will save even more resources. In that case and
>> >>> assuming that
>> >>>
>> >>>   >>>> all the traffic through the link have the same QoS
>> >>> requirements
>> >>>
>> >>>   >>>> (for example a sensor network), the idea would be to group
>> >>> all the
>> >>>
>> >>>   >>>> flows through the link (the bottleneck).
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>> Regards,
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>> Fernando Pascual Blanco
>> >>>
>> >>>   >>>> Telef=C3=B3nica Global Resources
>> >>>
>> >>>   >>>> Network Automation and Dynamization TECHNOLOGY PEOPLE
>> >> GROUP F
>> >>>
>> >>>   >>>> +34913128779 M +34682005168 fpb@tid.es <mailto:fpb@tid.es>
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>> On 18/09/12 20:46, "Gorry Fairhurst" <gorry@erg.abdn.ac.uk
>> >>> <mailto:gorry@erg.abdn.ac.uk>> wrote:
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>>>A satellite "link" may provide HC, at least some of the
>> >>> ones I have
>> >>>
>> >>>   >>>>>seen do. In this case, the flows can easily be grouped by
>> >>> mac
>> >>>
>> >>>   >>>>>address?
>> >>>
>> >>>   >>>>>
>> >>>
>> >>>   >>>>>Gorry
>> >>>
>> >>>   >>>>>
>> >>>
>> >>>   >>>>>On 13/09/2012 16:20, Jose Saldana wrote:
>> >>>
>> >>>   >>>>>> Hi, Fernando, sorry for the delay (one week, I=C2=B9m afrai=
d).
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> I don=C2=B9t know who is the one interested on using TCMTF:
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> -If you are a costumer, and you have to pay for a
>> >>> satellite link
>> >>>
>> >>>   >>>>>>or  a  long distance wire, perhaps you are the one
>> >>> interested on
>> >>>
>> >>>   >>>>>>using  end-to-end TCMTF, since you will save bandwidth or
>> >>> packets
>> >>>
>> >>>   >>>>>>per  second  or  money. If you have e.g. two offices, one
>> >>> in
>> >>>
>> >>>   >>>>>>America and other one in  Europe, you may be interested
>> >>> on placing
>> >>>
>> >>>   >>>>>>a device for multiplexing a  number of VoIP calls between
> them.
>> >>>
>> >>>   >>>>>>You have one advantage: the flows  have the same origin
>> >>> and
>> >>>
>> >>>   >>>>>>destination, so header compression is effective.
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> -If you are the operator of the satellite, you have
>> >>> another
>> >> problem:
>> >>>
>> >>>   >>>>>> you
>> >>>
>> >>>   >>>>>> may have to check every flow, and try to group them.
>> >>> Perhaps it
>> >>>
>> >>>   >>>>>> may be easy, but if you want to save headers, you need
>> >>> flows with
>> >>>
>> >>>   >>>>>> the same origin and destination.
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> I think that there are different scenarios, and each
>> >>> =C2=B3actor=C2=B2
>> >>>
>> >>>   >>>>>>may  try to  use TCMTF in the best place: a high number
>> >>> of flows,
>> >>>
>> >>>   >>>>>>with small  packets,  and sharing the same origin and
>> > destination.
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Do you agree?
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Jose
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> *De:*tcmtf-bounces@ietf.org [mailto:tcmtf-
>> bounces@ietf.org]
>> >>> <mailto:[mailto:tcmtf-bounces@ietf.org]> *En
>> >>>
>> >>>   >>>>>> nombre de *FERNANDO PASCUAL BLANCO *Enviado el:*
>> martes,
>> >> 04 de
>> >>>
>> >>>   >>>>>> septiembre de 2012 12:27
>> >>>
>> >>>   >>>>>> *Para:* tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >>>
>> >>>   >>>>>> *Asunto:* Re: [tcmtf] Discussing M2M scenario and
>> >>> savings
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Hi all,
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Yes, M2M sensor networks are a very good example in
>> >>> order to save
>> >>>
>> >>>   >>>>>> bandwidth in long distance/big latency/low bandwidth
>> >>> links, links
>> >>>
>> >>>   >>>>>> were the cost per bit is high. Do you think network
>> >>> carriers
>> >>>
>> >>>   >>>>>> operating this kind of links (satellite links or long
>> >>> distance
>> >>>
>> >>>   >>>>>> wires) would be interested in apply TCMTF?
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Regards,
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Fernando
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> *From:*tcmtf-bounces@ietf.org <mailto:tcmtf-
>> >> bounces@ietf.org>
>> >>>
>> >>>   >>>>>> [mailto:tcmtf-bounces@ietf.org]
>> >>> <mailto:[mailto:tcmtf-bounces@ietf.org]>
>> >>>
>> >>>   >>>>>> <mailto:[mailto:tcmtf-bounces@ietf.org]>
>> >>>
>> >>>   >>>>>> *On Behalf Of *Jose Saldana
>> >>>
>> >>>   >>>>>> *Sent:* martes, 04 de septiembre de 2012 9:41
>> >>>
>> >>>   >>>>>> *To:* tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >>> <mailto:tcmtf@ietf.org>
>> >>>
>> >>>   >>>>>> *Cc:* Matteo.Berioli@dlr.de
>> >>> <mailto:Matteo.Berioli@dlr.de> <mailto:Matteo.Berioli@dlr.de>;
>> >>>
>> >>>   >>>>>> Tomaso.deCola@dlr.de <mailto:Tomaso.deCola@dlr.de>
>> >>> <mailto:Tomaso.deCola@dlr.de>
>> >>>
>> >>>   >>>>>> *Subject:* [tcmtf] Discussing M2M scenario and savings
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Hi again,
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> We already discussed some points about the M2M scenario
>> >>> at the
>> >>>
>> >>>   >>>>>>beginning  of August. We are currently studying this, and
>> >>> we have
>> >>>
>> >>>   >>>>>>built some  figures, in collaboration with people from
>> >>> DLR (Tomaso
>> >>>
>> >>>   >>>>>>and Matteo).
>> >>>
>> >>>   >>>>>>You
>> >>>
>> >>>   >>>>>> can find the figures here:
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>
>> >>>
>> >>>>>>>>
>> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_savi
>> >>>>>>>> n
>> >>> gs
>> >>>
>> >>>   >>>>>>.pd
>> >>>
>> >>>   >>>>>>f
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>
>> >>>
>> >>>>>>>>
>> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scen
>> >>>>>>>> a
>> >>> ri
>> >>>
>> >>>   >>>>>>o.p
>> >>>
>> >>>   >>>>>>df
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Perhaps we could comment them, in order to discuss this
>> >>> scenario,
>> >>>
>> >>>   >>>>>> and we may find new ones in which TCMTF can be useful.
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Thanks,
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Jose
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>
>> >>>>>>>>> -----------------------------------------------------------
>> >>>>>>>>> ---
>> >>>>>>>>> --
>> >>> --
>> >>>
>> >>>   >>>>>>---
>> >>>
>> >>>   >>>>>>--
>> >>>
>> >>>   >>>>>>-
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> Este mensaje se dirige exclusivamente a su destinatario.
>> >>> Puede
>> >>>
>> >>>   >>>>>> consultar nuestra pol=C3=ADtica de env=C3=ADo y recepci=C3=
=B3n de
>> >>> correo
>> >>>
>> >>>   >>>>>> electr=C3=B3nico en el enlace situado m=C3=A1s abajo.
>> >>>
>> >>>   >>>>>> This message is intended exclusively for its addressee.
>> >>> We only
>> >>>
>> >>>   >>>>>> send and receive email on the basis of the terms set out
>> at:
>> >>>
>> >>>   >>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>> _______________________________________________
>> >>>
>> >>>   >>>>>> tcmtf mailing list
>> >>>
>> >>>   >>>>>> tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >>>
>> >>>   >>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>
>> >>>   >>>>>>
>> >>>
>> >>>   >>>>>
>> >>>
>> >>>   >>>>>_______________________________________________
>> >>>
>> >>>   >>>>>tcmtf mailing list
>> >>>
>> >>>   >>>>>tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >>>
>> >>>   >>>>>https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>> ________________________________
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>> Este mensaje se dirige exclusivamente a su destinatario.
>> >>> Puede
>> >>>
>> >>>   >>>> consultar nuestra pol=C3=ADtica de env=C3=ADo y recepci=C3=B3=
n de
>> >>> correo
>> >>>
>> >>>   >>>> electr=C3=B3nico en el enlace situado m=C3=A1s 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
>> >>>
>> >>>   >>>>
>> >>>
>> >>>   >>>
>> >>>
>> >>>   >>>
>> >>>
>> >>>   >>
>> >>>
>> >>>   >>
>> >>>
>> >>>   >> ________________________________
>> >>>
>> >>>   >>
>> >>>
>> >>>   >> Este mensaje se dirige exclusivamente a su destinatario.
>> >>> Puede
>> >>>
>> >>>   >> consultar nuestra pol=C3=ADtica de env=C3=ADo y recepci=C3=B3n =
de correo
>> >>>
>> >>>   >> electr=C3=B3nico en el enlace situado m=C3=A1s abajo.
>> >>>
>> >>>   >> This message is intended exclusively for its addressee. We
>> >>> only send
>> >>>
>> >>>   >> and receive email on the basis of the terms set out at:
>> >>>
>> >>>   >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> >>>
>> >>>   >>
>> >>>
>> >>>   >
>> >>>
>> >>>   >
>> >>>
>> >>>   >
>> >>>
>> >>>   >_______________________________________________
>> >>>
>> >>>   >tcmtf mailing list
>> >>>
>> >>>   >tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >>>
>> >>>   >https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>
>> >>> ________________________________
>> >>>
>> >>> Este mensaje se dirige exclusivamente a su destinatario. Puede
>> >>> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo
>> >>> electr=F3nico en el enlace situado m=E1s abajo.
>> >>>
>> >>> This message is intended exclusively for its addressee. We only
>> >>> send and receive email on the basis of the terms set out at:
>> >>>
>> >>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> >>>
>> >>> _______________________________________________
>> >>>
>> >>> tcmtf mailing list
>> >>>
>> >>> tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >>>
>> >>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> tcmtf mailing list
>> >>> tcmtf@ietf.org
>> >>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>
>> >>
>> >> _______________________________________________
>> >> tcmtf mailing list
>> >> tcmtf@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/tcmtf
>> >
>> > _______________________________________________
>> > tcmtf mailing list
>> > tcmtf@ietf.org
>> > https://www.ietf.org/mailman/listinfo/tcmtf
>> >
>>
>> _______________________________________________
>> 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

________________________________

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 mns@tid.es  Mon Oct  1 07:34:55 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 DB5B21F0C7E for <tcmtf@ietfa.amsl.com>; Mon,  1 Oct 2012 07:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id puKanbEh2iTU for <tcmtf@ietfa.amsl.com>; Mon,  1 Oct 2012 07:34:53 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id CEEEB1F0CD6 for <tcmtf@ietf.org>; Mon,  1 Oct 2012 07:34:52 -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 <0MB700DSRXU3FQ@tid.hi.inet> for tcmtf@ietf.org; Mon, 01 Oct 2012 16:34:51 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 30.49.05494.80AA9605; Mon, 01 Oct 2012 16:34:49 +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 <0MB700DSNXU0FQ@tid.hi.inet> for tcmtf@ietf.org; Mon, 01 Oct 2012 16:34:48 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.209]) by ex10-htcas3-mad.hi.inet ([::1]) with mapi id 14.02.0318.001; Mon, 01 Oct 2012 16:33:43 +0200
Date: Mon, 01 Oct 2012 14:33:42 +0000
From: =?iso-8859-1?Q?MANUEL_NU=D1EZ_SANZ?= <mns@tid.es>
In-reply-to: <001c01cd9d5a$5d104fe0$1730efa0$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, FERNANDO PASCUAL BLANCO <fpb@tid.es>
Message-id: <90ED8822CB577741B9A1668A4753931218F4889D@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: es-ES
Content-transfer-encoding: quoted-printable
Accept-Language: es-ES, en-US
Thread-topic: [tcmtf] Next steps with TCMTF
Thread-index: Ac2cmrry4BaRIpi1Sm27mcZI4g4aKwAJ1PiAACHikIAAnT3mcA==
X-AuditID: 0a5f4e69-b7fc06d000001576-16-5069aa0838d9
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKJsWRmVeSWpSXmKPExsXCFe9nqMu9KjPA4Nt/AYtdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoEr4173TMaC23YVix89Y25gXGPUxcjBISFgIrF8U0oXIyeQKSZx 4d56ti5GLg4hge2MEieeHGKCcH4ySvz/OJ0RwpnJKPHrwx1mkBYWAVWJF8tmsIBMYhMwl+hb xwMSFhbQkvj16Qs7iM0pYCHx6NVsJogNChJ/zj1mAbFFBEIlWlbsZgJpZQYaM++bIkiYV8Bb ovXVZBYIW1Dix+R7YDazgI5E7/dvzBC2uMScXxNZIWxtiSfvLoDZjAKyEivPn2aEGK8t8fPb JzYI20ni2aK5jBAnCEgs2XOeGcIWlXj5+B8rxFvLGSXaZvxkmsAoPgvJ7llIds9CsnsWkt0L GFlWMYoVJxVlpmeU5CZm5qQbGOllZOpl5qWWbGKERFHmDsblO1UOMQpwMCrx8P5YmBAgxJpY VlyZe4jRkoNJSZT347LMACG+pPyUyozE4oz4otKc1GIlOd5ed6CwOFy4uLS4IDM5M7+0OL60 KOcQowQHs5IIr30OUBFvSmJlVWpRPkTrIUZ7Dg4lCd5ZK4BSgkWp6akVaZk5wFQDNVmRV3F1 WoCQFLIMuuFMHJyHGM05eIA2dIOM4S0uSMwtzkyHGiHL+xnkODGYKKr2U4zWUuK8+0D6BEAq Mkrz4LZLKfB+XwW0XRJJAlX3K0ZTYEAJ824C6ecBJneEtTK8pxgzAoREoYLo+syBoSnCWwUy nre4JLEE2b1XQKJiMFFUnVINjPI694TyROTlnFo2vrQqP/kpy865raNsY4XBXpWHj6ZcVnvt plhUE3V4NbfPzficxd39rM6mRoUyW+tXGpdf/aj6JNZ0Ws6OG428l65VNwTYesVevJf2axmL iNGJ3M17f1VE5b/pPRxdKHFlZ5FMVbL3OevvEgeftp87X9bB+HjGtuVrnyW4KbEUZyQaajEX FScCAA4Na+PoAwAA
References: <007801cd9c9b$3b06d5a0$b11480e0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A249D7B626@EX10-MB1-MAD.hi.inet> <001c01cd9d5a$5d104fe0$1730efa0$@unizar.es>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Next steps with 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, 01 Oct 2012 14:34:55 -0000

Hi Jose,
    I am going to try to answer you inline with mark [MNS].

 I hope it has sense.

Manuel.

-----Mensaje original-----
De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de Jos=
e Saldana
Enviado el: viernes, 28 de septiembre de 2012 11:19
Para: FERNANDO PASCUAL BLANCO
CC: tcmtf@ietf.org
Asunto: Re: [tcmtf] Next steps with TCMTF

Fernando,

I have been thinking about it. There are three questions:


A) Should we map packet marks like DiffServ to different tunnels between th=
e same points?

There is a first question: it does not exist (by now) a universally accepte=
d standard about Diffserv mapping for different services. Perhaps an ISP ma=
y have a clear classification, so it can be useful for this, if the tunnel =
is created inside his aggregation network.

Although marking can be useful, perhaps it would not be enough: if you want=
 to group the packets of a certain game, and establish a tunnel finishing a=
t the game server, you need to identify them by the destination IP. So I th=
ink you would need something more than Diffserv.

[MNS] I agree, although marking by ISP o equivalent could be very useful, o=
ther options like "IP sources", "specific ports" could be equally valid.

My proposal: including in the draft b) a sentence like "Different mechanism=
s can be used in order to decide which packets are included into each tunne=
l.
For example, Diffserv can be useful when doing this. In other cases, the pa=
cket flows would have to be identified by their origin and/or destination I=
P addresses."

[MNS] I also agree with that open way.

Fernando (and people from network operators): please think about this. As n=
etwork providers, you should have a clearer idea about this.

B) Could we mix some flows and under what conditions?

If the tunnel is only set inside the ISP network, or between two ISPs, then=
 I think there is no problem on grouping packets from different services, o=
r even transport protocols (UDP and TCP flows in the same tunnel). The ques=
tion is that you have to accomplish the delay requirements of the most dela=
y-sensitive service.

As we have three layers (compressing, multiplexing, tunneling), I think tha=
t tunneling and multiplexing layers do not have to know which kind of packe=
t they are carrying. (I am posting another message about this).

Other question is: if you can set up a tunnel covering the whole route (e.g=
., from the access network to the game server), then you can only group pac=
kets of a single game. On the other hand, if you only group packets in your=
 aggregation network, you can group a big number of flows. When the tunnel =
arrives at the internet router, the packets are rebuilt and sent in their n=
ative form.

So the longer the common route you want to cover, the more specific traffic=
 you can tunnel.

[MNS] I think there no problem on grouping packets from different service a=
s long as each grouped services has the same "delay sensitive" level and th=
e same IP destination (internet router, game data center...). In fact, refi=
ning this idea... if for example the most delay-sensitive flow has not reac=
hed its optimum full it could be complete with the following traffic with s=
hould be less delay-sensitive, and so on. In this way always each flow is s=
ent with its optimum payload.

C) Do you think that would be included in your second draft proposal?

 By now, I think this can be issued in draft b). However, we have to furthe=
r think about it.


Thank you,

Jose

[MNS] Thanks,  Manuel


> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
> de FERNANDO PASCUAL BLANCO Enviado el: jueves, 27 de septiembre de
> 2012 17:08
> Para: jsaldana@unizar.es; tcmtf@ietf.org
> CC: Wesley Eddy; Martin Stiemerling
> Asunto: Re: [tcmtf] Next steps with TCMTF
>
> Hi Jose,
>
>         I absolutely agree with your classification. Nevertheless I
> miss a
draft
> explaining how to deal with different QoS flows passing through a
> TCMTF
> tunnel: Should we map packet marks like DiffServ to different tunnels
> between the same points? Could we mix some flows and under what
> conditions? Do you think that would be included in your second draft
> proposal?
>
> Regards,
>
> Fernando Pascual Blanco
> Telef=F3nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>
>
>
>
> On 27/09/12 12:31, "Jose Saldana" <jsaldana@unizar.es> wrote:
>
> >Hello all,
> >
> >I would like to discuss in this list the possibility of creating a
> >small Working Group for TCMTF, as suggested by Wes. It could have the
> >task of making a RFC from TCMTF, or a wider scope. I think that
> >perhaps more than a draft would be necessary. I mean, I have been
> >thinking about it, and perhaps the work could be divided into the next p=
arts:
> >
> > a) "Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03),
> >including the protocol stack of TCMTF. The current proposal has
> >different options, but the concrete one to use is static: in the
> >set-up moment, you decide that "between these two routers a tunnel is
> >set including all the packets with this IP origin and destination".
> >
> >b) "Recommendations draft": another "informational" one, with
> >recommendations of maximum delays to be added to different kinds of
> >services, different multiplexing policies, implementation issues
> >related to the selection of the best compression algorithm to use, etc.
> >Some hypothetical examples:
> >      -  "if you are multiplexing a First Person Shooter, your
> >multiplexer should not retain packets more than 50 ms"
> >- "if you are multiplexing in a low-end router in a wired scenario,
> >you don't need to use ROHC. A simpler scheme like IPHC can be enough,
> >and it will not require a lot of processing capacity".
> >
> >c) "Dynamic Signaling draft": perhaps another one including a
> >signaling system in order to:
> >       - dynamically "negotiate" the concrete options of TCMTF you
> >are going to use
> >       - if two routers notice that a rush hour is arriving, they
> >could send some packets asking other routers if they have some flows
> >in common with them, which could be multiplexed.
> >
> >
> >The main questions are:
> >
> >Is this enough for creating a working group?
> >
> >Do you think the distribution of the work into three draft makes sense?
> >
> >Is there any other issue which should be studied and standardized?
> >Perhaps other people could imagine more things.
> >
> >So let's start the discussion.
> >
> >Thanks in advance,
> >
> >Jose
> >
> >
> >_______________________________________________
> >tcmtf mailing list
> >tcmtf@ietf.org
> >https://www.ietf.org/mailman/listinfo/tcmtf
>
>
> ________________________________
>
> Este mensaje se dirige exclusivamente a su destinatario. Puede
> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3=
nico
> en el enlace situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send
> and receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf

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

________________________________

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  Tue Oct  2 08:55:28 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 F272821F851A for <tcmtf@ietfa.amsl.com>; Tue,  2 Oct 2012 08:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.449
X-Spam-Level: 
X-Spam-Status: No, score=-110.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ff2Im4U9jMML for <tcmtf@ietfa.amsl.com>; Tue,  2 Oct 2012 08:55:25 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id C613121F8518 for <tcmtf@ietf.org>; Tue,  2 Oct 2012 08:55:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23613; q=dns/txt; s=iport; t=1349193326; x=1350402926; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=acvMg52VBZERolWFEhBdE12ywyOP28fSRceV7jzi+Ys=; b=dKKCkOn05r1UXqttWgmqxZY9N3ADZhpzoEU0woa7PYsxEnctK40E60rW NJHK7OWVATMsicq9NEKERRdH3oezeFH4noq4YMSbcYySEvjE+tb6wmlUa oGSP/Tx4sEZDAWdf0aXb7LiK3Yezf0HZlscnS15F3z0NptSkXf5jwHo0E M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAMIMa1CrRDoI/2dsb2JhbABFDgiuIpAigQiCIAEBAQMBAQEBBQoBBxA9BQIIAwUHAQMCCQ8CBAEBAScHGQ4VCgkIAQEEARILEAeHXQUMmQWPVpBfixoKhkEDiCM1hRGET4RGjS2BaYIsW4FD
X-IronPort-AV: E=Sophos;i="4.80,524,1344211200"; d="scan'208";a="60218896"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 02 Oct 2012 15:55:23 +0000
Received: from dwingWS ([10.32.240.194]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q92FtMn9006924; Tue, 2 Oct 2012 15:55:22 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'MANUEL_NU=D1EZ_SANZ'?=" <mns@tid.es>, <gorry@erg.abdn.ac.uk>, <jsaldana@unizar.es>
References: <003101cd9d62$c803f1f0$580bd5d0$@unizar.es>	<506592DF.7070508@erg.abdn.ac.uk>	<004701cd9fbd$a0a1b540$e1e51fc0$@unizar.es>	<c898f337fd617ee9fe1a49b9ac8d35e9.squirrel@www.erg.abdn.ac.uk> <90ED8822CB577741B9A1668A4753931218F47F75@EX10-MB2-MAD.hi.inet>
In-Reply-To: <90ED8822CB577741B9A1668A4753931218F47F75@EX10-MB2-MAD.hi.inet>
Date: Tue, 2 Oct 2012 08:55:22 -0700
Message-ID: <053201cda0b6$545c2770$fd147650$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac2dYUy6uVqP4M0WSN+HUIzF9jzvbP///2CAgASXwICAAAQigP//sbcg//2kMJA=
Content-Language: en-us
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] More satellite scenarios
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, 02 Oct 2012 15:55:28 -0000

> -----Original Message-----
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
> Of MANUEL NU=D1EZ SANZ
> Sent: Monday, October 01, 2012 7:04 AM
> To: gorry@erg.abdn.ac.uk; jsaldana@unizar.es
> Cc: tcmtf@ietf.org
> Subject: Re: [tcmtf] More satellite scenarios
>=20
> Yes, I agree with both and the scenario is raised too simple, and the
> main advantages are obtained when there are several networks after the
> satellite link and the mux-demux is made end to end.

Also, some implementation experience:  Cisco has long had cRTP and=20
(TCP) VJ header compression in our various devices.  It is CPU =
intensive. =20
Van Jacobson, when he worked at Cisco, did a deep dive into the=20
implementation to improve it, but found no fundamental flaws with
its implementation.

Thus, even if mux/compression seems like a good idea on the
satellite link itself, it consumes CPU horsepower exactly where
it is difficult to handle -- at an aggregation point with lots
of data flowing.  Better to do it once (rather than at every "slow"
link), and do it closer to the producer/consumer so it isn't done
at a large aggregation point.

-d

> I am going to describe it with an example. Imagine a group of M2M
> sensors with a mux close to gateway (as in the figure), for example
> sensors in natural parks around Europe to prevent fires. Each group of
> these sensors send their data through a satellite link to a next hop,
> and from there the data are sent to centralized data center in =
Brussels
> (for example) to process, to analyze and to take decisions. The demux
> should be located just across that data center.
>=20
> Manuel.
>=20
>=20
> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> gorry@erg.abdn.ac.uk
> Enviado el: lunes, 01 de octubre de 2012 12:30
> Para: jsaldana@unizar.es
> CC: gorry@erg.abdn.ac.uk; tcmtf@ietf.org
> Asunto: Re: [tcmtf] More satellite scenarios
>=20
> That is what I think - the proposed tunnel method does not seem to =
have
> advantage when used over a single link.
>=20
> Gorry
>=20
> > Gorry,
> >
> > The question here is that perhaps the scenario of the sensor network
> > in
> >
> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scenario.pd
> > f
> > was
> > too simplistic, and TCMTF made no sense for it, since the use of IP
> > would not be necessary, as you remarked. There are more interesting
> > compressing options for that scenario. Am I correct?
> >
> > Thanks for your feedback,
> >
> > Jose
> >
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> >> de Gorry Fairhurst Enviado el: viernes, 28 de septiembre de 2012
> >> 14:07
> >> Para: tcmtf@ietf.org
> >> Asunto: Re: [tcmtf] More satellite scenarios
> >>
> >> I did not dispute the use of VoIP and other "small packet" services
> >> over satellite (I work on this subject). What I wanted to =
understand
> >> was why ROHC or RFC 3545 (e.g. for VoIP) was not applicable.
> >>
> >> Gorry
> >>
> >> On 28/09/2012 11:19, Jose Saldana wrote:
> >> > We have to continue the discussion about satellite scenarios with
> >> > sensor
> >> > networks: if possible, I would like to hear the opinion of people
> >> > from DLR about this.
> >> >
> >> >
> >> > However, I have found more satellite-related scenarios in which a
> >> > number of small-packet flows can be present:
> >> >
> >> > - A cruise: lots of people (3800 people in Queen Mary 2) =
connected
> >> > through a satellite link
> >> >
> >> >
> >>
> http://www.cruisemates.com/articles/onboard/connected.cfm#axzz27l0sEq
> >> u
> >> > 3
> >> > http://en.wikipedia.org/wiki/RMS_Queen_Mary_2
> >> > http://www.esa.int/esaTE/SEMMAWNFGLE_index_0.html
> >> >
> >> >
> >> > - A plane: similar to the ship, but less people and no satellite,
> >> > but ground antennas communicating with a special antenna on the
> >> > plane (VoIP is prohibited by now):
> >> > http://en.wikipedia.org/wiki/Gogo_Inflight_Internet
> >> >
> >> >
> >> > - Satellite access in low-populated regions (e.g. Alaska): =
Perhaps
> >> > a number of people, or a village, may share a  connection through
> >> > an
> >> antenna:
> >> > http://www.skycasters.com/satellite-internet-coverage/skycasters-
> co
> >> > ver
> >> > age-Al
> >> > aska.html
> >> >
> >> >
> >> > What do you think?
> >> >
> >> > Best regards,
> >> >
> >> > Jose
> >> >
> >> >> -----Mensaje original-----
> >> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> >> nombre de Gorry Fairhurst Enviado el: viernes, 21 de septiembre
> de
> >> >> 2012
> >> >> 10:29
> >> >> Para: jsaldana@unizar.es
> >> >> CC: tcmtf@ietf.org; 'FERNANDO PASCUAL BLANCO'
> >> >> Asunto: Re: [tcmtf] Discussing M2M scenario and savings -
> >> >> continuing the thread
> >> >>
> >> >> I think *IF* the satellite link is a DVB 2nd generation RF link,
> e.g.
> >> >> DVB-S2 for satellite ( a common waveform), then GSE + RFC 5163 =
is
> >> >> a reasonable proposal, on which one may benefit if one layers a
> HC
> >> >> scheme, such as ROHC, or 6LoWPAN. The profile for the  ROHC
> >> >> schemes have not been specified for this type of link - but the
> >> >> relevant RFCs exist for the compression itself. RFC 3135 and RFC
> >> >> 3449 also describe TCP/IP techniques
> >> > to
> >> >> help improve efficiency on such links.
> >> >>
> >> >> As I said, I do not see the *benefit* for the mux and demux in
> the
> >> > scenario
> >> >> as drawn, since this seems more like *link* HC, and it would =
seem
> >> >> foolish
> >> > to
> >> >> form aggregate traffic over a single link layer in the way that
> >> >> tunnel compression implements this.
> >> >>
> >> >> If the drawing extended the network on one or both sides of the
> >> >> satellite link, there could be a reason for using tunnel HC,
> >> >> although I am not sure whether this is commercially important,
> >> >> since unlike an access network,
> >> > the
> >> >> connectivity to the hub (usually known as the satellite gateway)
> >> >> on the
> >> > left of
> >> >> the figure is not usually a low speed access link and the merits
> >> >> of HC is
> >> > less
> >> >> obvious where bandwidth is high. Also, it would seem desirable =
to
> >> >> use encapsulation and HC mechanisms on the satellite air
> interface
> >> >> anyway, RFC
> >> >> 3135 part 3 (from the source), possibly combined with RFC 3449
> >> mechanisms.
> >> >>
> >> >> All I am saying is you have to be sure to describe the scenario
> >> >> carefully
> >> > and
> >> >> explain why HC applies in this case and what alternatives exist.
> >> >>
> >> >> Gorry
> >> >>
> >> >> On 20/09/2012 17:20, Jose Saldana wrote:
> >> >>> So, do you think the figure should be modified? Perhaps it is
> >> >>> currently confusing, since it seems that RFC 5163 is the best
> >> >>> solution. Perhaps a network should be included between the =
demux
> >> and
> >> >>> the data center? Or between the antenna and the demux? Will =
this
> >> >>> be a real case? I don't know if in the right side it is =
possible
> >> >>> to find
> >> > other
> >> >> networks.
> >> >>>
> >> >>> I am talking about this figure:
> >> >>>
> >> >>>
> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scenario.
> >> >>> pd
> >> >>> f
> >> >>>
> >> >>> Thanks,
> >> >>>
> >> >>> Jose
> >> >>>
> >> >>> -----Mensaje original-----
> >> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> nombre
> >> >>> de FERNANDO PASCUAL BLANCO Enviado el: mi=E9rcoles, 19 de
> >> septiembre
> >> >> de
> >> >>> 2012 13:02
> >> >>> Para: gorry@erg.abdn.ac.uk; tcmtf@ietf.org
> >> >>> Asunto: Re: [tcmtf] Discussing M2M scenario and savings -
> >> >>> continuing the thread
> >> >>>
> >> >>> Hi Gorry,
> >> >>>
> >> >>>           Absolutely. The tunneling layer would increase that
> >> >>> benefit in a multi-router hop path, being the satellite-link
> part
> >> >>> of
> > this
> >> path.
> >> >>>
> >> >>> Regards,
> >> >>>
> >> >>> Fernando Pascual Blanco
> >> >>>
> >> >>> Telef=F3nica Global Resources
> >> >>>
> >> >>> Network Automation and Dynamization
> >> >>>
> >> >>> TECHNOLOGY PEOPLE GROUP
> >> >>>
> >> >>> F +34913128779
> >> >>>
> >> >>> M +34682005168
> >> >>>
> >> >>> fpb@tid.es <mailto:fpb@tid.es>
> >> >>>
> >> >>> On 19/09/12 12:37, "gorry@erg.abdn.ac.uk
> >> >> <mailto:gorry@erg.abdn.ac.uk>"
> >> >>> <gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>> wrote:
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >For a point-to-point link carrying traffic destined to a
> ingle
> >> >>> L2
> >> >>>
> >> >>>   >address, I don't see how this helps above the gains of ROHC
> or
> >> >>> some
> >> >>>
> >> >>>   >other HC on the link, when possibly combining this with link
> >> >>> layer
> >> >>>
> >> >>>   >transmission options e.g. methods like PDU-CONCAT in RFC
> 5163.
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >If you're working over a multi-router network hop, the
> >> >>> considerations
> >> >>>
> >> >>>   >may be different.
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >Gorry
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >> Hi Gorry,
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >>         I don=C2=B4t know a lot about link layer HC, but I
> imagine
> > that
> >> >>>
> >> >>>   >> it compress packet headers (IP-TCP/UDP). If, in addition =
to
> >> >>> that, we
> >> >>>
> >> >>>   >> group several small packets into a bigger one (using PPP-
> Mux
> >> >>> and
> >> >>>
> >> >>>   >> RoHC), don=C2=B4t you think more resources could be saved?
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >> Regards,
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >> Fernando Pascual Blanco
> >> >>>
> >> >>>   >> Telef=C3=B3nica Global Resources
> >> >>>
> >> >>>   >> Network Automation and Dynamization
> >> >>>
> >> >>>   >> TECHNOLOGY PEOPLE GROUP
> >> >>>
> >> >>>   >> F +34913128779
> >> >>>
> >> >>>   >> M +34682005168
> >> >>>
> >> >>>   >> fpb@tid.es <mailto:fpb@tid.es>
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >> On 19/09/12 10:56, "gorry@erg.abdn.ac.uk
> >> >>> <mailto:gorry@erg.abdn.ac.uk>" <gorry@erg.abdn.ac.uk
> >> >>> <mailto:gorry@erg.abdn.ac.uk>> wrote:
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >>>I know there are applications for tunnel compression - but
> >> >>> I'm not
> >> >>>
> >> >>>   >>>sure  I understand how this can gain further than for
> >> link-layer
> > HC?
> >> >>>
> >> >>>   >>>
> >> >>>
> >> >>>   >>>Gorry
> >> >>>
> >> >>>   >>>
> >> >>>
> >> >>>   >>>> Hi Gorry,
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>>         In addition of HC (header compression), the
> > multiplexing
> >> >>>
> >> >>>   >>>> layer will save even more resources. In that case and
> >> >>> assuming that
> >> >>>
> >> >>>   >>>> all the traffic through the link have the same QoS
> >> >>> requirements
> >> >>>
> >> >>>   >>>> (for example a sensor network), the idea would be to
> group
> >> >>> all the
> >> >>>
> >> >>>   >>>> flows through the link (the bottleneck).
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>> Regards,
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>> Fernando Pascual Blanco
> >> >>>
> >> >>>   >>>> Telef=C3=B3nica Global Resources
> >> >>>
> >> >>>   >>>> Network Automation and Dynamization TECHNOLOGY PEOPLE
> >> >> GROUP F
> >> >>>
> >> >>>   >>>> +34913128779 M +34682005168 fpb@tid.es
> <mailto:fpb@tid.es>
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>> On 18/09/12 20:46, "Gorry Fairhurst"
> <gorry@erg.abdn.ac.uk
> >> >>> <mailto:gorry@erg.abdn.ac.uk>> wrote:
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>>>A satellite "link" may provide HC, at least some of the
> >> >>> ones I have
> >> >>>
> >> >>>   >>>>>seen do. In this case, the flows can easily be grouped =
by
> >> >>> mac
> >> >>>
> >> >>>   >>>>>address?
> >> >>>
> >> >>>   >>>>>
> >> >>>
> >> >>>   >>>>>Gorry
> >> >>>
> >> >>>   >>>>>
> >> >>>
> >> >>>   >>>>>On 13/09/2012 16:20, Jose Saldana wrote:
> >> >>>
> >> >>>   >>>>>> Hi, Fernando, sorry for the delay (one week, I=C2=B9m
> afraid).
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> I don=C2=B9t know who is the one interested on using =
TCMTF:
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> -If you are a costumer, and you have to pay for a
> >> >>> satellite link
> >> >>>
> >> >>>   >>>>>>or  a  long distance wire, perhaps you are the one
> >> >>> interested on
> >> >>>
> >> >>>   >>>>>>using  end-to-end TCMTF, since you will save bandwidth
> or
> >> >>> packets
> >> >>>
> >> >>>   >>>>>>per  second  or  money. If you have e.g. two offices,
> one
> >> >>> in
> >> >>>
> >> >>>   >>>>>>America and other one in  Europe, you may be interested
> >> >>> on placing
> >> >>>
> >> >>>   >>>>>>a device for multiplexing a  number of VoIP calls
> between
> > them.
> >> >>>
> >> >>>   >>>>>>You have one advantage: the flows  have the same origin
> >> >>> and
> >> >>>
> >> >>>   >>>>>>destination, so header compression is effective.
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> -If you are the operator of the satellite, you have
> >> >>> another
> >> >> problem:
> >> >>>
> >> >>>   >>>>>> you
> >> >>>
> >> >>>   >>>>>> may have to check every flow, and try to group them.
> >> >>> Perhaps it
> >> >>>
> >> >>>   >>>>>> may be easy, but if you want to save headers, you need
> >> >>> flows with
> >> >>>
> >> >>>   >>>>>> the same origin and destination.
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> I think that there are different scenarios, and each
> >> >>> =C2=B3actor=C2=B2
> >> >>>
> >> >>>   >>>>>>may  try to  use TCMTF in the best place: a high number
> >> >>> of flows,
> >> >>>
> >> >>>   >>>>>>with small  packets,  and sharing the same origin and
> >> > destination.
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Do you agree?
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Jose
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> *De:*tcmtf-bounces@ietf.org [mailto:tcmtf-
> >> bounces@ietf.org]
> >> >>> <mailto:[mailto:tcmtf-bounces@ietf.org]> *En
> >> >>>
> >> >>>   >>>>>> nombre de *FERNANDO PASCUAL BLANCO *Enviado el:*
> >> martes,
> >> >> 04 de
> >> >>>
> >> >>>   >>>>>> septiembre de 2012 12:27
> >> >>>
> >> >>>   >>>>>> *Para:* tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >> >>>
> >> >>>   >>>>>> *Asunto:* Re: [tcmtf] Discussing M2M scenario and
> >> >>> savings
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Hi all,
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Yes, M2M sensor networks are a very good example in
> >> >>> order to save
> >> >>>
> >> >>>   >>>>>> bandwidth in long distance/big latency/low bandwidth
> >> >>> links, links
> >> >>>
> >> >>>   >>>>>> were the cost per bit is high. Do you think network
> >> >>> carriers
> >> >>>
> >> >>>   >>>>>> operating this kind of links (satellite links or long
> >> >>> distance
> >> >>>
> >> >>>   >>>>>> wires) would be interested in apply TCMTF?
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Regards,
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Fernando
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> *From:*tcmtf-bounces@ietf.org <mailto:tcmtf-
> >> >> bounces@ietf.org>
> >> >>>
> >> >>>   >>>>>> [mailto:tcmtf-bounces@ietf.org]
> >> >>> <mailto:[mailto:tcmtf-bounces@ietf.org]>
> >> >>>
> >> >>>   >>>>>> <mailto:[mailto:tcmtf-bounces@ietf.org]>
> >> >>>
> >> >>>   >>>>>> *On Behalf Of *Jose Saldana
> >> >>>
> >> >>>   >>>>>> *Sent:* martes, 04 de septiembre de 2012 9:41
> >> >>>
> >> >>>   >>>>>> *To:* tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >> >>> <mailto:tcmtf@ietf.org>
> >> >>>
> >> >>>   >>>>>> *Cc:* Matteo.Berioli@dlr.de
> >> >>> <mailto:Matteo.Berioli@dlr.de> <mailto:Matteo.Berioli@dlr.de>;
> >> >>>
> >> >>>   >>>>>> Tomaso.deCola@dlr.de <mailto:Tomaso.deCola@dlr.de>
> >> >>> <mailto:Tomaso.deCola@dlr.de>
> >> >>>
> >> >>>   >>>>>> *Subject:* [tcmtf] Discussing M2M scenario and savings
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Hi again,
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> We already discussed some points about the M2M =
scenario
> >> >>> at the
> >> >>>
> >> >>>   >>>>>>beginning  of August. We are currently studying this,
> and
> >> >>> we have
> >> >>>
> >> >>>   >>>>>>built some  figures, in collaboration with people from
> >> >>> DLR (Tomaso
> >> >>>
> >> >>>   >>>>>>and Matteo).
> >> >>>
> >> >>>   >>>>>>You
> >> >>>
> >> >>>   >>>>>> can find the figures here:
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>>>>>>
> >> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_savi
> >> >>>>>>>> n
> >> >>> gs
> >> >>>
> >> >>>   >>>>>>.pd
> >> >>>
> >> >>>   >>>>>>f
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>>>>>>
> >> http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/m2m_scen
> >> >>>>>>>> a
> >> >>> ri
> >> >>>
> >> >>>   >>>>>>o.p
> >> >>>
> >> >>>   >>>>>>df
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Perhaps we could comment them, in order to discuss =
this
> >> >>> scenario,
> >> >>>
> >> >>>   >>>>>> and we may find new ones in which TCMTF can be useful.
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Thanks,
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Jose
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>
> >> >>>>>>>>> =
----------------------------------------------------------
> -
> >> >>>>>>>>> ---
> >> >>>>>>>>> --
> >> >>> --
> >> >>>
> >> >>>   >>>>>>---
> >> >>>
> >> >>>   >>>>>>--
> >> >>>
> >> >>>   >>>>>>-
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> Este mensaje se dirige exclusivamente a su
> destinatario.
> >> >>> Puede
> >> >>>
> >> >>>   >>>>>> consultar nuestra pol=C3=ADtica de env=C3=ADo y =
recepci=C3=B3n de
> >> >>> correo
> >> >>>
> >> >>>   >>>>>> electr=C3=B3nico en el enlace situado m=C3=A1s abajo.
> >> >>>
> >> >>>   >>>>>> This message is intended exclusively for its =
addressee.
> >> >>> We only
> >> >>>
> >> >>>   >>>>>> send and receive email on the basis of the terms set
> out
> >> at:
> >> >>>
> >> >>>   >>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>> _______________________________________________
> >> >>>
> >> >>>   >>>>>> tcmtf mailing list
> >> >>>
> >> >>>   >>>>>> tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >> >>>
> >> >>>   >>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>
> >> >>>   >>>>>>
> >> >>>
> >> >>>   >>>>>
> >> >>>
> >> >>>   >>>>>_______________________________________________
> >> >>>
> >> >>>   >>>>>tcmtf mailing list
> >> >>>
> >> >>>   >>>>>tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >> >>>
> >> >>>   >>>>>https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>> ________________________________
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>> Este mensaje se dirige exclusivamente a su destinatario.
> >> >>> Puede
> >> >>>
> >> >>>   >>>> consultar nuestra pol=C3=ADtica de env=C3=ADo y =
recepci=C3=B3n de
> >> >>> correo
> >> >>>
> >> >>>   >>>> electr=C3=B3nico en el enlace situado m=C3=A1s 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
> >> >>>
> >> >>>   >>>>
> >> >>>
> >> >>>   >>>
> >> >>>
> >> >>>   >>>
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >> ________________________________
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >> Este mensaje se dirige exclusivamente a su destinatario.
> >> >>> Puede
> >> >>>
> >> >>>   >> consultar nuestra pol=C3=ADtica de env=C3=ADo y =
recepci=C3=B3n de
> correo
> >> >>>
> >> >>>   >> electr=C3=B3nico en el enlace situado m=C3=A1s abajo.
> >> >>>
> >> >>>   >> This message is intended exclusively for its addressee. We
> >> >>> only send
> >> >>>
> >> >>>   >> and receive email on the basis of the terms set out at:
> >> >>>
> >> >>>   >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >> >>>
> >> >>>   >>
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >
> >> >>>
> >> >>>   >_______________________________________________
> >> >>>
> >> >>>   >tcmtf mailing list
> >> >>>
> >> >>>   >tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >> >>>
> >> >>>   >https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>
> >> >>> ________________________________
> >> >>>
> >> >>> Este mensaje se dirige exclusivamente a su destinatario. Puede
> >> >>> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo
> >> >>> electr=F3nico en el enlace situado m=E1s abajo.
> >> >>>
> >> >>> This message is intended exclusively for its addressee. We only
> >> >>> send and receive email on the basis of the terms set out at:
> >> >>>
> >> >>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >> >>>
> >> >>> _______________________________________________
> >> >>>
> >> >>> tcmtf mailing list
> >> >>>
> >> >>> tcmtf@ietf.org <mailto:tcmtf@ietf.org>
> >> >>>
> >> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>
> >> >>>
> >> >>>
> >> >>> _______________________________________________
> >> >>> tcmtf mailing list
> >> >>> tcmtf@ietf.org
> >> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>
> >> >>
> >> >> _______________________________________________
> >> >> tcmtf mailing list
> >> >> tcmtf@ietf.org
> >> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >
> >> > _______________________________________________
> >> > tcmtf mailing list
> >> > tcmtf@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/tcmtf
> >> >
> >>
> >> _______________________________________________
> >> tcmtf mailing list
> >> tcmtf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >
> > _______________________________________________
> > tcmtf mailing list
> > tcmtf@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcmtf
> >
>=20
>=20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede
> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico
> en el enlace situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send
> and receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From mns@tid.es  Tue Oct  2 09:02:20 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 83FB621F853B for <tcmtf@ietfa.amsl.com>; Tue,  2 Oct 2012 09:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1IbHihrRY+sL for <tcmtf@ietfa.amsl.com>; Tue,  2 Oct 2012 09:02:13 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 8F99521F8533 for <tcmtf@ietf.org>; Tue,  2 Oct 2012 09:02:10 -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 <0MB900DQLWJKE8@tid.hi.inet> for tcmtf@ietf.org; Tue, 02 Oct 2012 18:02:08 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id A1.28.05494.0001B605; Tue, 02 Oct 2012 18:02:08 +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 <0MB900I2KWJKY1@tid.hi.inet> for tcmtf@ietf.org; Tue, 02 Oct 2012 18:02:08 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.209]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0318.001; Tue, 02 Oct 2012 18:02:08 +0200
Date: Tue, 02 Oct 2012 16:02:08 +0000
From: =?utf-8?B?TUFOVUVMIE5Vw5FFWiBTQU5a?= <mns@tid.es>
In-reply-to: <053201cda0b6$545c2770$fd147650$@com>
X-Originating-IP: [10.95.64.115]
To: Dan Wing <dwing@cisco.com>, "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>,  "jsaldana@unizar.es" <jsaldana@unizar.es>
Message-id: <90ED8822CB577741B9A1668A4753931218F4C47C@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: es-ES
Content-transfer-encoding: base64
Accept-Language: es-ES, en-US
Thread-topic: [tcmtf] More satellite scenarios
Thread-index: Ac2dYUy6uVqP4M0WSN+HUIzF9jzvbP///2CAgASXwICAAAQigP//sbcg//2kMJD/+0ZgsA==
X-AuditID: 0a5f4e69-b7fc06d000001576-9d-506b10003999
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrJJsWRmVeSWpSXmKPExsXCFe9nqMsgkB1gsLPF2GLX5w2MDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKeP1sF2PBtWaminM9e9gaGBv+MnYxcnJICJhIrNy2DMoWk7hw bz1bFyMXh5DAdkaJdff+MEI4Pxklzk2axArhzGSUuPJoMVgLi4CqxK6WhcwgNpuAucSFmddZ QWxhAV2J21/62UFsTgEjibVXlrJDrFCQ+HPuMQuILSJQJdE8txsozsHBDDRn3jdFkDCvgLfE 0sdbWCFsQYkfk++xQJSoS0yZkgsSZhYQl5jzayIrhK0oMW1RA9g1jAKyEivPn2aEmK4nse7Y PCYIO0Li/cXZLBAXCEgs2XOeGcIWlXj5+B/UW5uYJN5O2s8+gVF8FpLVsxBWz0KyehaS1QsY WVYxihUnFWWmZ5TkJmbmpBsY6WVk6mXmpZZsYoREUuYOxuU7VQ4xCnAwKvHwKuzOChBiTSwr rsw9xGjJwaQkytvxHSjEl5SfUpmRWJwRX1Sak1qsJMfb654ZICQOFy4uLS7ITM7MLy2OLy3K OcQowcGsJMJrfR+olzclsbIqtSgfovUQoz0Hh5IEbxB/doCQYFFqempFWmYOMN1ATVbkrZwL 1CSFLINuOBMH5yFGcw4eoA2+IGN4iwsSc4sz06FGyPJ+BjlODCaKqv0Uoy/HzhMLHjByzJ6y 5AGjEEtefl6qlDgvC8gkAZCejNI8uHukFHj9Qe6RRJJANe8Voykw6IR5zUH6eYBZAOEQGd5T jBkBQqJQQXR95sDwFeFdoQsKo+KSxBJkHyiDLBWDiaLqlGpgtG41m5zsHxVV1FK3U36xTZ3H n1v/TvzYeGix6E8GrY2n+utnL5683tGrozw+L/fSxy1MGTsPKAkv6eHm6zQ8KTj5U0P6PfXk yPca+yYbvt7nuO+P6vEl5VrTHYQv6jQ+3nf1X9XWn7zZLpcY5yuXnf3uHfa58NUj61eBk8+m BcZ+ed32ObDsgRJLcUaioRZzUXEiAO/+wnf8AwAA
References: <003101cd9d62$c803f1f0$580bd5d0$@unizar.es> <506592DF.7070508@erg.abdn.ac.uk> <004701cd9fbd$a0a1b540$e1e51fc0$@unizar.es> <c898f337fd617ee9fe1a49b9ac8d35e9.squirrel@www.erg.abdn.ac.uk> <90ED8822CB577741B9A1668A4753931218F47F75@EX10-MB2-MAD.hi.inet> <053201cda0b6$545c2770$fd147650$@com>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] More satellite scenarios
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, 02 Oct 2012 16:02:20 -0000

T2ssIHRoZXNlIGV4cGVyaW1lbnRhbCBkYXRhIHJlaW5mb3JjZSB0aGUgaWRlYSBtdXgtZGVtdXgg
IOKAi+KAi2VuZCB0byBlbmQsIGFuZCBpdCBpcyBtb3JlIHVzZWZ1bCB3aGVuIGNyb3NzaW5nIGFy
ZWFzIG5hcnJvd2JhbmQgYW5kIGhpZ2ggZGVsYXkgc3VjaCBhcyBzYXRlbGxpdGUgbGlua3MuDQoN
Ck1hbnVlbC4NCg0KLS0tLS1NZW5zYWplIG9yaWdpbmFsLS0tLS0NCkRlOiBEYW4gV2luZyBbbWFp
bHRvOmR3aW5nQGNpc2NvLmNvbV0NCkVudmlhZG8gZWw6IG1hcnRlcywgMDIgZGUgb2N0dWJyZSBk
ZSAyMDEyIDE3OjU1DQpQYXJhOiBNQU5VRUwgTlXDkUVaIFNBTlo7IGdvcnJ5QGVyZy5hYmRuLmFj
LnVrOyBqc2FsZGFuYUB1bml6YXIuZXMNCkNDOiB0Y210ZkBpZXRmLm9yZw0KQXN1bnRvOiBSRTog
W3RjbXRmXSBNb3JlIHNhdGVsbGl0ZSBzY2VuYXJpb3MNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KPiBGcm9tOiB0Y210Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86dGNtdGYtYm91
bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmDQo+IE9mIE1BTlVFTCBOVcORRVogU0FOWg0KPiBTZW50
OiBNb25kYXksIE9jdG9iZXIgMDEsIDIwMTIgNzowNCBBTQ0KPiBUbzogZ29ycnlAZXJnLmFiZG4u
YWMudWs7IGpzYWxkYW5hQHVuaXphci5lcw0KPiBDYzogdGNtdGZAaWV0Zi5vcmcNCj4gU3ViamVj
dDogUmU6IFt0Y210Zl0gTW9yZSBzYXRlbGxpdGUgc2NlbmFyaW9zDQo+DQo+IFllcywgSSBhZ3Jl
ZSB3aXRoIGJvdGggYW5kIHRoZSBzY2VuYXJpbyBpcyByYWlzZWQgdG9vIHNpbXBsZSwgYW5kIHRo
ZQ0KPiBtYWluIGFkdmFudGFnZXMgYXJlIG9idGFpbmVkIHdoZW4gdGhlcmUgYXJlIHNldmVyYWwg
bmV0d29ya3MgYWZ0ZXIgdGhlDQo+IHNhdGVsbGl0ZSBsaW5rIGFuZCB0aGUgbXV4LWRlbXV4IGlz
IG1hZGUgZW5kIHRvIGVuZC4NCg0KQWxzbywgc29tZSBpbXBsZW1lbnRhdGlvbiBleHBlcmllbmNl
OiAgQ2lzY28gaGFzIGxvbmcgaGFkIGNSVFAgYW5kDQooVENQKSBWSiBoZWFkZXIgY29tcHJlc3Np
b24gaW4gb3VyIHZhcmlvdXMgZGV2aWNlcy4gIEl0IGlzIENQVSBpbnRlbnNpdmUuDQpWYW4gSmFj
b2Jzb24sIHdoZW4gaGUgd29ya2VkIGF0IENpc2NvLCBkaWQgYSBkZWVwIGRpdmUgaW50byB0aGUg
aW1wbGVtZW50YXRpb24gdG8gaW1wcm92ZSBpdCwgYnV0IGZvdW5kIG5vIGZ1bmRhbWVudGFsIGZs
YXdzIHdpdGggaXRzIGltcGxlbWVudGF0aW9uLg0KDQpUaHVzLCBldmVuIGlmIG11eC9jb21wcmVz
c2lvbiBzZWVtcyBsaWtlIGEgZ29vZCBpZGVhIG9uIHRoZSBzYXRlbGxpdGUgbGluayBpdHNlbGYs
IGl0IGNvbnN1bWVzIENQVSBob3JzZXBvd2VyIGV4YWN0bHkgd2hlcmUgaXQgaXMgZGlmZmljdWx0
IHRvIGhhbmRsZSAtLSBhdCBhbiBhZ2dyZWdhdGlvbiBwb2ludCB3aXRoIGxvdHMgb2YgZGF0YSBm
bG93aW5nLiAgQmV0dGVyIHRvIGRvIGl0IG9uY2UgKHJhdGhlciB0aGFuIGF0IGV2ZXJ5ICJzbG93
Ig0KbGluayksIGFuZCBkbyBpdCBjbG9zZXIgdG8gdGhlIHByb2R1Y2VyL2NvbnN1bWVyIHNvIGl0
IGlzbid0IGRvbmUgYXQgYSBsYXJnZSBhZ2dyZWdhdGlvbiBwb2ludC4NCg0KLWQNCg0KPiBJIGFt
IGdvaW5nIHRvIGRlc2NyaWJlIGl0IHdpdGggYW4gZXhhbXBsZS4gSW1hZ2luZSBhIGdyb3VwIG9m
IE0yTQ0KPiBzZW5zb3JzIHdpdGggYSBtdXggY2xvc2UgdG8gZ2F0ZXdheSAoYXMgaW4gdGhlIGZp
Z3VyZSksIGZvciBleGFtcGxlDQo+IHNlbnNvcnMgaW4gbmF0dXJhbCBwYXJrcyBhcm91bmQgRXVy
b3BlIHRvIHByZXZlbnQgZmlyZXMuIEVhY2ggZ3JvdXAgb2YNCj4gdGhlc2Ugc2Vuc29ycyBzZW5k
IHRoZWlyIGRhdGEgdGhyb3VnaCBhIHNhdGVsbGl0ZSBsaW5rIHRvIGEgbmV4dCBob3AsDQo+IGFu
ZCBmcm9tIHRoZXJlIHRoZSBkYXRhIGFyZSBzZW50IHRvIGNlbnRyYWxpemVkIGRhdGEgY2VudGVy
IGluDQo+IEJydXNzZWxzIChmb3IgZXhhbXBsZSkgdG8gcHJvY2VzcywgdG8gYW5hbHl6ZSBhbmQg
dG8gdGFrZSBkZWNpc2lvbnMuDQo+IFRoZSBkZW11eCBzaG91bGQgYmUgbG9jYXRlZCBqdXN0IGFj
cm9zcyB0aGF0IGRhdGEgY2VudGVyLg0KPg0KPiBNYW51ZWwuDQo+DQo+DQo+IC0tLS0tTWVuc2Fq
ZSBvcmlnaW5hbC0tLS0tDQo+IERlOiB0Y210Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86dGNt
dGYtYm91bmNlc0BpZXRmLm9yZ10gRW4gbm9tYnJlDQo+IGRlIGdvcnJ5QGVyZy5hYmRuLmFjLnVr
IEVudmlhZG8gZWw6IGx1bmVzLCAwMSBkZSBvY3R1YnJlIGRlIDIwMTIgMTI6MzANCj4gUGFyYTog
anNhbGRhbmFAdW5pemFyLmVzDQo+IENDOiBnb3JyeUBlcmcuYWJkbi5hYy51azsgdGNtdGZAaWV0
Zi5vcmcNCj4gQXN1bnRvOiBSZTogW3RjbXRmXSBNb3JlIHNhdGVsbGl0ZSBzY2VuYXJpb3MNCj4N
Cj4gVGhhdCBpcyB3aGF0IEkgdGhpbmsgLSB0aGUgcHJvcG9zZWQgdHVubmVsIG1ldGhvZCBkb2Vz
IG5vdCBzZWVtIHRvDQo+IGhhdmUgYWR2YW50YWdlIHdoZW4gdXNlZCBvdmVyIGEgc2luZ2xlIGxp
bmsuDQo+DQo+IEdvcnJ5DQo+DQo+ID4gR29ycnksDQo+ID4NCj4gPiBUaGUgcXVlc3Rpb24gaGVy
ZSBpcyB0aGF0IHBlcmhhcHMgdGhlIHNjZW5hcmlvIG9mIHRoZSBzZW5zb3IgbmV0d29yaw0KPiA+
IGluDQo+ID4NCj4gaHR0cDovL2RpZWMudW5pemFyLmVzL35qc2FsZGFuYS9wZXJzb25hbC90Y210
Zl9maWd1cmVzL20ybV9zY2VuYXJpby5wZA0KPiA+IGYNCj4gPiB3YXMNCj4gPiB0b28gc2ltcGxp
c3RpYywgYW5kIFRDTVRGIG1hZGUgbm8gc2Vuc2UgZm9yIGl0LCBzaW5jZSB0aGUgdXNlIG9mIElQ
DQo+ID4gd291bGQgbm90IGJlIG5lY2Vzc2FyeSwgYXMgeW91IHJlbWFya2VkLiBUaGVyZSBhcmUg
bW9yZSBpbnRlcmVzdGluZw0KPiA+IGNvbXByZXNzaW5nIG9wdGlvbnMgZm9yIHRoYXQgc2NlbmFy
aW8uIEFtIEkgY29ycmVjdD8NCj4gPg0KPiA+IFRoYW5rcyBmb3IgeW91ciBmZWVkYmFjaywNCj4g
Pg0KPiA+IEpvc2UNCj4gPg0KPiA+PiAtLS0tLU1lbnNhamUgb3JpZ2luYWwtLS0tLQ0KPiA+PiBE
ZTogdGNtdGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnRjbXRmLWJvdW5jZXNAaWV0Zi5vcmdd
IEVuDQo+ID4+IG5vbWJyZSBkZSBHb3JyeSBGYWlyaHVyc3QgRW52aWFkbyBlbDogdmllcm5lcywg
MjggZGUgc2VwdGllbWJyZSBkZQ0KPiA+PiAyMDEyDQo+ID4+IDE0OjA3DQo+ID4+IFBhcmE6IHRj
bXRmQGlldGYub3JnDQo+ID4+IEFzdW50bzogUmU6IFt0Y210Zl0gTW9yZSBzYXRlbGxpdGUgc2Nl
bmFyaW9zDQo+ID4+DQo+ID4+IEkgZGlkIG5vdCBkaXNwdXRlIHRoZSB1c2Ugb2YgVm9JUCBhbmQg
b3RoZXIgInNtYWxsIHBhY2tldCIgc2VydmljZXMNCj4gPj4gb3ZlciBzYXRlbGxpdGUgKEkgd29y
ayBvbiB0aGlzIHN1YmplY3QpLiBXaGF0IEkgd2FudGVkIHRvDQo+ID4+IHVuZGVyc3RhbmQgd2Fz
IHdoeSBST0hDIG9yIFJGQyAzNTQ1IChlLmcuIGZvciBWb0lQKSB3YXMgbm90IGFwcGxpY2FibGUu
DQo+ID4+DQo+ID4+IEdvcnJ5DQo+ID4+DQo+ID4+IE9uIDI4LzA5LzIwMTIgMTE6MTksIEpvc2Ug
U2FsZGFuYSB3cm90ZToNCj4gPj4gPiBXZSBoYXZlIHRvIGNvbnRpbnVlIHRoZSBkaXNjdXNzaW9u
IGFib3V0IHNhdGVsbGl0ZSBzY2VuYXJpb3Mgd2l0aA0KPiA+PiA+IHNlbnNvcg0KPiA+PiA+IG5l
dHdvcmtzOiBpZiBwb3NzaWJsZSwgSSB3b3VsZCBsaWtlIHRvIGhlYXIgdGhlIG9waW5pb24gb2Yg
cGVvcGxlDQo+ID4+ID4gZnJvbSBETFIgYWJvdXQgdGhpcy4NCj4gPj4gPg0KPiA+PiA+DQo+ID4+
ID4gSG93ZXZlciwgSSBoYXZlIGZvdW5kIG1vcmUgc2F0ZWxsaXRlLXJlbGF0ZWQgc2NlbmFyaW9z
IGluIHdoaWNoIGENCj4gPj4gPiBudW1iZXIgb2Ygc21hbGwtcGFja2V0IGZsb3dzIGNhbiBiZSBw
cmVzZW50Og0KPiA+PiA+DQo+ID4+ID4gLSBBIGNydWlzZTogbG90cyBvZiBwZW9wbGUgKDM4MDAg
cGVvcGxlIGluIFF1ZWVuIE1hcnkgMikNCj4gPj4gPiBjb25uZWN0ZWQgdGhyb3VnaCBhIHNhdGVs
bGl0ZSBsaW5rDQo+ID4+ID4NCj4gPj4gPg0KPiA+Pg0KPiBodHRwOi8vd3d3LmNydWlzZW1hdGVz
LmNvbS9hcnRpY2xlcy9vbmJvYXJkL2Nvbm5lY3RlZC5jZm0jYXh6ejI3bDBzRXENCj4gPj4gdQ0K
PiA+PiA+IDMNCj4gPj4gPiBodHRwOi8vZW4ud2lraXBlZGlhLm9yZy93aWtpL1JNU19RdWVlbl9N
YXJ5XzINCj4gPj4gPiBodHRwOi8vd3d3LmVzYS5pbnQvZXNhVEUvU0VNTUFXTkZHTEVfaW5kZXhf
MC5odG1sDQo+ID4+ID4NCj4gPj4gPg0KPiA+PiA+IC0gQSBwbGFuZTogc2ltaWxhciB0byB0aGUg
c2hpcCwgYnV0IGxlc3MgcGVvcGxlIGFuZCBubyBzYXRlbGxpdGUsDQo+ID4+ID4gYnV0IGdyb3Vu
ZCBhbnRlbm5hcyBjb21tdW5pY2F0aW5nIHdpdGggYSBzcGVjaWFsIGFudGVubmEgb24gdGhlDQo+
ID4+ID4gcGxhbmUgKFZvSVAgaXMgcHJvaGliaXRlZCBieSBub3cpOg0KPiA+PiA+IGh0dHA6Ly9l
bi53aWtpcGVkaWEub3JnL3dpa2kvR29nb19JbmZsaWdodF9JbnRlcm5ldA0KPiA+PiA+DQo+ID4+
ID4NCj4gPj4gPiAtIFNhdGVsbGl0ZSBhY2Nlc3MgaW4gbG93LXBvcHVsYXRlZCByZWdpb25zIChl
LmcuIEFsYXNrYSk6DQo+ID4+ID4gUGVyaGFwcyBhIG51bWJlciBvZiBwZW9wbGUsIG9yIGEgdmls
bGFnZSwgbWF5IHNoYXJlIGEgIGNvbm5lY3Rpb24NCj4gPj4gPiB0aHJvdWdoIGFuDQo+ID4+IGFu
dGVubmE6DQo+ID4+ID4gaHR0cDovL3d3dy5za3ljYXN0ZXJzLmNvbS9zYXRlbGxpdGUtaW50ZXJu
ZXQtY292ZXJhZ2Uvc2t5Y2FzdGVycy0NCj4gY28NCj4gPj4gPiB2ZXINCj4gPj4gPiBhZ2UtQWwN
Cj4gPj4gPiBhc2thLmh0bWwNCj4gPj4gPg0KPiA+PiA+DQo+ID4+ID4gV2hhdCBkbyB5b3UgdGhp
bms/DQo+ID4+ID4NCj4gPj4gPiBCZXN0IHJlZ2FyZHMsDQo+ID4+ID4NCj4gPj4gPiBKb3NlDQo+
ID4+ID4NCj4gPj4gPj4gLS0tLS1NZW5zYWplIG9yaWdpbmFsLS0tLS0NCj4gPj4gPj4gRGU6IHRj
bXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0Y210Zi1ib3VuY2VzQGlldGYub3JnXSBFbg0K
PiA+PiA+PiBub21icmUgZGUgR29ycnkgRmFpcmh1cnN0IEVudmlhZG8gZWw6IHZpZXJuZXMsIDIx
IGRlIHNlcHRpZW1icmUNCj4gZGUNCj4gPj4gPj4gMjAxMg0KPiA+PiA+PiAxMDoyOQ0KPiA+PiA+
PiBQYXJhOiBqc2FsZGFuYUB1bml6YXIuZXMNCj4gPj4gPj4gQ0M6IHRjbXRmQGlldGYub3JnOyAn
RkVSTkFORE8gUEFTQ1VBTCBCTEFOQ08nDQo+ID4+ID4+IEFzdW50bzogUmU6IFt0Y210Zl0gRGlz
Y3Vzc2luZyBNMk0gc2NlbmFyaW8gYW5kIHNhdmluZ3MgLQ0KPiA+PiA+PiBjb250aW51aW5nIHRo
ZSB0aHJlYWQNCj4gPj4gPj4NCj4gPj4gPj4gSSB0aGluayAqSUYqIHRoZSBzYXRlbGxpdGUgbGlu
ayBpcyBhIERWQiAybmQgZ2VuZXJhdGlvbiBSRiBsaW5rLA0KPiBlLmcuDQo+ID4+ID4+IERWQi1T
MiBmb3Igc2F0ZWxsaXRlICggYSBjb21tb24gd2F2ZWZvcm0pLCB0aGVuIEdTRSArIFJGQyA1MTYz
DQo+ID4+ID4+IGlzIGEgcmVhc29uYWJsZSBwcm9wb3NhbCwgb24gd2hpY2ggb25lIG1heSBiZW5l
Zml0IGlmIG9uZSBsYXllcnMNCj4gPj4gPj4gYQ0KPiBIQw0KPiA+PiA+PiBzY2hlbWUsIHN1Y2gg
YXMgUk9IQywgb3IgNkxvV1BBTi4gVGhlIHByb2ZpbGUgZm9yIHRoZSAgUk9IQw0KPiA+PiA+PiBz
Y2hlbWVzIGhhdmUgbm90IGJlZW4gc3BlY2lmaWVkIGZvciB0aGlzIHR5cGUgb2YgbGluayAtIGJ1
dCB0aGUNCj4gPj4gPj4gcmVsZXZhbnQgUkZDcyBleGlzdCBmb3IgdGhlIGNvbXByZXNzaW9uIGl0
c2VsZi4gUkZDIDMxMzUgYW5kIFJGQw0KPiA+PiA+PiAzNDQ5IGFsc28gZGVzY3JpYmUgVENQL0lQ
IHRlY2huaXF1ZXMNCj4gPj4gPiB0bw0KPiA+PiA+PiBoZWxwIGltcHJvdmUgZWZmaWNpZW5jeSBv
biBzdWNoIGxpbmtzLg0KPiA+PiA+Pg0KPiA+PiA+PiBBcyBJIHNhaWQsIEkgZG8gbm90IHNlZSB0
aGUgKmJlbmVmaXQqIGZvciB0aGUgbXV4IGFuZCBkZW11eCBpbg0KPiB0aGUNCj4gPj4gPiBzY2Vu
YXJpbw0KPiA+PiA+PiBhcyBkcmF3biwgc2luY2UgdGhpcyBzZWVtcyBtb3JlIGxpa2UgKmxpbmsq
IEhDLCBhbmQgaXQgd291bGQNCj4gPj4gPj4gc2VlbSBmb29saXNoDQo+ID4+ID4gdG8NCj4gPj4g
Pj4gZm9ybSBhZ2dyZWdhdGUgdHJhZmZpYyBvdmVyIGEgc2luZ2xlIGxpbmsgbGF5ZXIgaW4gdGhl
IHdheSB0aGF0DQo+ID4+ID4+IHR1bm5lbCBjb21wcmVzc2lvbiBpbXBsZW1lbnRzIHRoaXMuDQo+
ID4+ID4+DQo+ID4+ID4+IElmIHRoZSBkcmF3aW5nIGV4dGVuZGVkIHRoZSBuZXR3b3JrIG9uIG9u
ZSBvciBib3RoIHNpZGVzIG9mIHRoZQ0KPiA+PiA+PiBzYXRlbGxpdGUgbGluaywgdGhlcmUgY291
bGQgYmUgYSByZWFzb24gZm9yIHVzaW5nIHR1bm5lbCBIQywNCj4gPj4gPj4gYWx0aG91Z2ggSSBh
bSBub3Qgc3VyZSB3aGV0aGVyIHRoaXMgaXMgY29tbWVyY2lhbGx5IGltcG9ydGFudCwNCj4gPj4g
Pj4gc2luY2UgdW5saWtlIGFuIGFjY2VzcyBuZXR3b3JrLA0KPiA+PiA+IHRoZQ0KPiA+PiA+PiBj
b25uZWN0aXZpdHkgdG8gdGhlIGh1YiAodXN1YWxseSBrbm93biBhcyB0aGUgc2F0ZWxsaXRlIGdh
dGV3YXkpDQo+ID4+ID4+IG9uIHRoZQ0KPiA+PiA+IGxlZnQgb2YNCj4gPj4gPj4gdGhlIGZpZ3Vy
ZSBpcyBub3QgdXN1YWxseSBhIGxvdyBzcGVlZCBhY2Nlc3MgbGluayBhbmQgdGhlIG1lcml0cw0K
PiA+PiA+PiBvZiBIQyBpcw0KPiA+PiA+IGxlc3MNCj4gPj4gPj4gb2J2aW91cyB3aGVyZSBiYW5k
d2lkdGggaXMgaGlnaC4gQWxzbywgaXQgd291bGQgc2VlbSBkZXNpcmFibGUNCj4gPj4gPj4gdG8g
dXNlIGVuY2Fwc3VsYXRpb24gYW5kIEhDIG1lY2hhbmlzbXMgb24gdGhlIHNhdGVsbGl0ZSBhaXIN
Cj4gaW50ZXJmYWNlDQo+ID4+ID4+IGFueXdheSwgUkZDDQo+ID4+ID4+IDMxMzUgcGFydCAzIChm
cm9tIHRoZSBzb3VyY2UpLCBwb3NzaWJseSBjb21iaW5lZCB3aXRoIFJGQyAzNDQ5DQo+ID4+IG1l
Y2hhbmlzbXMuDQo+ID4+ID4+DQo+ID4+ID4+IEFsbCBJIGFtIHNheWluZyBpcyB5b3UgaGF2ZSB0
byBiZSBzdXJlIHRvIGRlc2NyaWJlIHRoZSBzY2VuYXJpbw0KPiA+PiA+PiBjYXJlZnVsbHkNCj4g
Pj4gPiBhbmQNCj4gPj4gPj4gZXhwbGFpbiB3aHkgSEMgYXBwbGllcyBpbiB0aGlzIGNhc2UgYW5k
IHdoYXQgYWx0ZXJuYXRpdmVzIGV4aXN0Lg0KPiA+PiA+Pg0KPiA+PiA+PiBHb3JyeQ0KPiA+PiA+
Pg0KPiA+PiA+PiBPbiAyMC8wOS8yMDEyIDE3OjIwLCBKb3NlIFNhbGRhbmEgd3JvdGU6DQo+ID4+
ID4+PiBTbywgZG8geW91IHRoaW5rIHRoZSBmaWd1cmUgc2hvdWxkIGJlIG1vZGlmaWVkPyBQZXJo
YXBzIGl0IGlzDQo+ID4+ID4+PiBjdXJyZW50bHkgY29uZnVzaW5nLCBzaW5jZSBpdCBzZWVtcyB0
aGF0IFJGQyA1MTYzIGlzIHRoZSBiZXN0DQo+ID4+ID4+PiBzb2x1dGlvbi4gUGVyaGFwcyBhIG5l
dHdvcmsgc2hvdWxkIGJlIGluY2x1ZGVkIGJldHdlZW4gdGhlDQo+ID4+ID4+PiBkZW11eA0KPiA+
PiBhbmQNCj4gPj4gPj4+IHRoZSBkYXRhIGNlbnRlcj8gT3IgYmV0d2VlbiB0aGUgYW50ZW5uYSBh
bmQgdGhlIGRlbXV4PyBXaWxsDQo+ID4+ID4+PiB0aGlzIGJlIGEgcmVhbCBjYXNlPyBJIGRvbid0
IGtub3cgaWYgaW4gdGhlIHJpZ2h0IHNpZGUgaXQgaXMNCj4gPj4gPj4+IHBvc3NpYmxlIHRvIGZp
bmQNCj4gPj4gPiBvdGhlcg0KPiA+PiA+PiBuZXR3b3Jrcy4NCj4gPj4gPj4+DQo+ID4+ID4+PiBJ
IGFtIHRhbGtpbmcgYWJvdXQgdGhpcyBmaWd1cmU6DQo+ID4+ID4+Pg0KPiA+PiA+Pj4NCj4gaHR0
cDovL2RpZWMudW5pemFyLmVzL35qc2FsZGFuYS9wZXJzb25hbC90Y210Zl9maWd1cmVzL20ybV9z
Y2VuYXJpby4NCj4gPj4gPj4+IHBkDQo+ID4+ID4+PiBmDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gVGhh
bmtzLA0KPiA+PiA+Pj4NCj4gPj4gPj4+IEpvc2UNCj4gPj4gPj4+DQo+ID4+ID4+PiAtLS0tLU1l
bnNhamUgb3JpZ2luYWwtLS0tLQ0KPiA+PiA+Pj4gRGU6IHRjbXRmLWJvdW5jZXNAaWV0Zi5vcmcg
W21haWx0bzp0Y210Zi1ib3VuY2VzQGlldGYub3JnXSBFbg0KPiA+PiBub21icmUNCj4gPj4gPj4+
IGRlIEZFUk5BTkRPIFBBU0NVQUwgQkxBTkNPIEVudmlhZG8gZWw6IG1pw6lyY29sZXMsIDE5IGRl
DQo+ID4+IHNlcHRpZW1icmUNCj4gPj4gPj4gZGUNCj4gPj4gPj4+IDIwMTIgMTM6MDINCj4gPj4g
Pj4+IFBhcmE6IGdvcnJ5QGVyZy5hYmRuLmFjLnVrOyB0Y210ZkBpZXRmLm9yZw0KPiA+PiA+Pj4g
QXN1bnRvOiBSZTogW3RjbXRmXSBEaXNjdXNzaW5nIE0yTSBzY2VuYXJpbyBhbmQgc2F2aW5ncyAt
DQo+ID4+ID4+PiBjb250aW51aW5nIHRoZSB0aHJlYWQNCj4gPj4gPj4+DQo+ID4+ID4+PiBIaSBH
b3JyeSwNCj4gPj4gPj4+DQo+ID4+ID4+PiAgICAgICAgICAgQWJzb2x1dGVseS4gVGhlIHR1bm5l
bGluZyBsYXllciB3b3VsZCBpbmNyZWFzZSB0aGF0DQo+ID4+ID4+PiBiZW5lZml0IGluIGEgbXVs
dGktcm91dGVyIGhvcCBwYXRoLCBiZWluZyB0aGUgc2F0ZWxsaXRlLWxpbmsNCj4gcGFydA0KPiA+
PiA+Pj4gb2YNCj4gPiB0aGlzDQo+ID4+IHBhdGguDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gUmVnYXJk
cywNCj4gPj4gPj4+DQo+ID4+ID4+PiBGZXJuYW5kbyBQYXNjdWFsIEJsYW5jbw0KPiA+PiA+Pj4N
Cj4gPj4gPj4+IFRlbGVmw7NuaWNhIEdsb2JhbCBSZXNvdXJjZXMNCj4gPj4gPj4+DQo+ID4+ID4+
PiBOZXR3b3JrIEF1dG9tYXRpb24gYW5kIER5bmFtaXphdGlvbg0KPiA+PiA+Pj4NCj4gPj4gPj4+
IFRFQ0hOT0xPR1kgUEVPUExFIEdST1VQDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gRiArMzQ5MTMxMjg3
NzkNCj4gPj4gPj4+DQo+ID4+ID4+PiBNICszNDY4MjAwNTE2OA0KPiA+PiA+Pj4NCj4gPj4gPj4+
IGZwYkB0aWQuZXMgPG1haWx0bzpmcGJAdGlkLmVzPg0KPiA+PiA+Pj4NCj4gPj4gPj4+IE9uIDE5
LzA5LzEyIDEyOjM3LCAiZ29ycnlAZXJnLmFiZG4uYWMudWsNCj4gPj4gPj4gPG1haWx0bzpnb3Jy
eUBlcmcuYWJkbi5hYy51az4iDQo+ID4+ID4+PiA8Z29ycnlAZXJnLmFiZG4uYWMudWsgPG1haWx0
bzpnb3JyeUBlcmcuYWJkbi5hYy51az4+IHdyb3RlOg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPg0K
PiA+PiA+Pj4NCj4gPj4gPj4+ICAgPkZvciBhIHBvaW50LXRvLXBvaW50IGxpbmsgY2Fycnlpbmcg
dHJhZmZpYyBkZXN0aW5lZCB0byBhDQo+IGluZ2xlDQo+ID4+ID4+PiBMMg0KPiA+PiA+Pj4NCj4g
Pj4gPj4+ICAgPmFkZHJlc3MsIEkgZG9uJ3Qgc2VlIGhvdyB0aGlzIGhlbHBzIGFib3ZlIHRoZSBn
YWlucyBvZiBST0hDDQo+IG9yDQo+ID4+ID4+PiBzb21lDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+
b3RoZXIgSEMgb24gdGhlIGxpbmssIHdoZW4gcG9zc2libHkgY29tYmluaW5nIHRoaXMgd2l0aCBs
aW5rDQo+ID4+ID4+PiBsYXllcg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPnRyYW5zbWlzc2lvbiBv
cHRpb25zIGUuZy4gbWV0aG9kcyBsaWtlIFBEVS1DT05DQVQgaW4gUkZDDQo+IDUxNjMuDQo+ID4+
ID4+Pg0KPiA+PiA+Pj4gICA+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+SWYgeW91J3JlIHdvcmtp
bmcgb3ZlciBhIG11bHRpLXJvdXRlciBuZXR3b3JrIGhvcCwgdGhlDQo+ID4+ID4+PiBjb25zaWRl
cmF0aW9ucw0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPm1heSBiZSBkaWZmZXJlbnQuDQo+ID4+ID4+
Pg0KPiA+PiA+Pj4gICA+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+R29ycnkNCj4gPj4gPj4+DQo+
ID4+ID4+PiAgID4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+IEhpIEdvcnJ5LA0KPiA+PiA+Pj4N
Cj4gPj4gPj4+ICAgPj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+ICAgICAgICAgSSBkb27DgsK0
dCBrbm93IGEgbG90IGFib3V0IGxpbmsgbGF5ZXIgSEMsIGJ1dCBJDQo+IGltYWdpbmUNCj4gPiB0
aGF0DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+PiBpdCBjb21wcmVzcyBwYWNrZXQgaGVhZGVycyAo
SVAtVENQL1VEUCkuIElmLCBpbiBhZGRpdGlvbg0KPiA+PiA+Pj4gdG8gdGhhdCwgd2UNCj4gPj4g
Pj4+DQo+ID4+ID4+PiAgID4+IGdyb3VwIHNldmVyYWwgc21hbGwgcGFja2V0cyBpbnRvIGEgYmln
Z2VyIG9uZSAodXNpbmcgUFBQLQ0KPiBNdXgNCj4gPj4gPj4+IGFuZA0KPiA+PiA+Pj4NCj4gPj4g
Pj4+ICAgPj4gUm9IQyksIGRvbsOCwrR0IHlvdSB0aGluayBtb3JlIHJlc291cmNlcyBjb3VsZCBi
ZSBzYXZlZD8NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+
PiBSZWdhcmRzLA0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAg
ID4+IEZlcm5hbmRvIFBhc2N1YWwgQmxhbmNvDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+PiBUZWxl
ZsODwrNuaWNhIEdsb2JhbCBSZXNvdXJjZXMNCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+IE5ldHdv
cmsgQXV0b21hdGlvbiBhbmQgRHluYW1pemF0aW9uDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+PiBU
RUNITk9MT0dZIFBFT1BMRSBHUk9VUA0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4gRiArMzQ5MTMx
Mjg3NzkNCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+IE0gKzM0NjgyMDA1MTY4DQo+ID4+ID4+Pg0K
PiA+PiA+Pj4gICA+PiBmcGJAdGlkLmVzIDxtYWlsdG86ZnBiQHRpZC5lcz4NCj4gPj4gPj4+DQo+
ID4+ID4+PiAgID4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+
ICAgPj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+PiBP
biAxOS8wOS8xMiAxMDo1NiwgImdvcnJ5QGVyZy5hYmRuLmFjLnVrDQo+ID4+ID4+PiA8bWFpbHRv
OmdvcnJ5QGVyZy5hYmRuLmFjLnVrPiIgPGdvcnJ5QGVyZy5hYmRuLmFjLnVrDQo+ID4+ID4+PiA8
bWFpbHRvOmdvcnJ5QGVyZy5hYmRuLmFjLnVrPj4gd3JvdGU6DQo+ID4+ID4+Pg0KPiA+PiA+Pj4g
ICA+Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+SSBrbm93IHRoZXJlIGFyZSBhcHBsaWNhdGlv
bnMgZm9yIHR1bm5lbCBjb21wcmVzc2lvbiAtIGJ1dA0KPiA+PiA+Pj4gSSdtIG5vdA0KPiA+PiA+
Pj4NCj4gPj4gPj4+ICAgPj4+c3VyZSAgSSB1bmRlcnN0YW5kIGhvdyB0aGlzIGNhbiBnYWluIGZ1
cnRoZXIgdGhhbiBmb3INCj4gPj4gbGluay1sYXllcg0KPiA+IEhDPw0KPiA+PiA+Pj4NCj4gPj4g
Pj4+ICAgPj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj5Hb3JyeQ0KPiA+PiA+Pj4NCj4gPj4g
Pj4+ICAgPj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+IEhpIEdvcnJ5LA0KPiA+PiA+Pj4N
Cj4gPj4gPj4+ICAgPj4+Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+PiAgICAgICAgIEluIGFk
ZGl0aW9uIG9mIEhDIChoZWFkZXIgY29tcHJlc3Npb24pLCB0aGUNCj4gPiBtdWx0aXBsZXhpbmcN
Cj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4gbGF5ZXIgd2lsbCBzYXZlIGV2ZW4gbW9yZSByZXNv
dXJjZXMuIEluIHRoYXQgY2FzZSBhbmQNCj4gPj4gPj4+IGFzc3VtaW5nIHRoYXQNCj4gPj4gPj4+
DQo+ID4+ID4+PiAgID4+Pj4gYWxsIHRoZSB0cmFmZmljIHRocm91Z2ggdGhlIGxpbmsgaGF2ZSB0
aGUgc2FtZSBRb1MNCj4gPj4gPj4+IHJlcXVpcmVtZW50cw0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAg
Pj4+PiAoZm9yIGV4YW1wbGUgYSBzZW5zb3IgbmV0d29yayksIHRoZSBpZGVhIHdvdWxkIGJlIHRv
DQo+IGdyb3VwDQo+ID4+ID4+PiBhbGwgdGhlDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+IGZs
b3dzIHRocm91Z2ggdGhlIGxpbmsgKHRoZSBib3R0bGVuZWNrKS4NCj4gPj4gPj4+DQo+ID4+ID4+
PiAgID4+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4gUmVnYXJkcywNCj4gPj4gPj4+DQo+
ID4+ID4+PiAgID4+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4gRmVybmFuZG8gUGFzY3Vh
bCBCbGFuY28NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4gVGVsZWbDg8KzbmljYSBHbG9iYWwg
UmVzb3VyY2VzDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+IE5ldHdvcmsgQXV0b21hdGlvbiBh
bmQgRHluYW1pemF0aW9uIFRFQ0hOT0xPR1kgUEVPUExFDQo+ID4+ID4+IEdST1VQIEYNCj4gPj4g
Pj4+DQo+ID4+ID4+PiAgID4+Pj4gKzM0OTEzMTI4Nzc5IE0gKzM0NjgyMDA1MTY4IGZwYkB0aWQu
ZXMNCj4gPG1haWx0bzpmcGJAdGlkLmVzPg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pg0KPiA+
PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pg0KPiA+PiA+
Pj4NCj4gPj4gPj4+ICAgPj4+Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+PiBPbiAxOC8wOS8x
MiAyMDo0NiwgIkdvcnJ5IEZhaXJodXJzdCINCj4gPGdvcnJ5QGVyZy5hYmRuLmFjLnVrDQo+ID4+
ID4+PiA8bWFpbHRvOmdvcnJ5QGVyZy5hYmRuLmFjLnVrPj4gd3JvdGU6DQo+ID4+ID4+Pg0KPiA+
PiA+Pj4gICA+Pj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+PkEgc2F0ZWxsaXRlICJsaW5r
IiBtYXkgcHJvdmlkZSBIQywgYXQgbGVhc3Qgc29tZSBvZiB0aGUNCj4gPj4gPj4+IG9uZXMgSSBo
YXZlDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+PnNlZW4gZG8uIEluIHRoaXMgY2FzZSwgdGhl
IGZsb3dzIGNhbiBlYXNpbHkgYmUgZ3JvdXBlZA0KPiA+PiA+Pj4gYnkgbWFjDQo+ID4+ID4+Pg0K
PiA+PiA+Pj4gICA+Pj4+PmFkZHJlc3M/DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pg0KPiA+
PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj5Hb3JyeQ0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4N
Cj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+T24gMTMvMDkvMjAxMiAxNjoyMCwgSm9zZSBTYWxk
YW5hIHdyb3RlOg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+IEhpLCBGZXJuYW5kbywgc29y
cnkgZm9yIHRoZSBkZWxheSAob25lIHdlZWssIEnDgsK5bQ0KPiBhZnJhaWQpLg0KPiA+PiA+Pj4N
Cj4gPj4gPj4+ICAgPj4+Pj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4gSSBkb27DgsK5
dCBrbm93IHdobyBpcyB0aGUgb25lIGludGVyZXN0ZWQgb24gdXNpbmcgVENNVEY6DQo+ID4+ID4+
Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiAtSWYgeW91
IGFyZSBhIGNvc3R1bWVyLCBhbmQgeW91IGhhdmUgdG8gcGF5IGZvciBhDQo+ID4+ID4+PiBzYXRl
bGxpdGUgbGluaw0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+b3IgIGEgIGxvbmcgZGlzdGFu
Y2Ugd2lyZSwgcGVyaGFwcyB5b3UgYXJlIHRoZSBvbmUNCj4gPj4gPj4+IGludGVyZXN0ZWQgb24N
Cj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PnVzaW5nICBlbmQtdG8tZW5kIFRDTVRGLCBzaW5j
ZSB5b3Ugd2lsbCBzYXZlIGJhbmR3aWR0aA0KPiBvcg0KPiA+PiA+Pj4gcGFja2V0cw0KPiA+PiA+
Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+cGVyICBzZWNvbmQgIG9yICBtb25leS4gSWYgeW91IGhhdmUg
ZS5nLiB0d28gb2ZmaWNlcywNCj4gb25lDQo+ID4+ID4+PiBpbg0KPiA+PiA+Pj4NCj4gPj4gPj4+
ICAgPj4+Pj4+QW1lcmljYSBhbmQgb3RoZXIgb25lIGluICBFdXJvcGUsIHlvdSBtYXkgYmUgaW50
ZXJlc3RlZA0KPiA+PiA+Pj4gb24gcGxhY2luZw0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+
YSBkZXZpY2UgZm9yIG11bHRpcGxleGluZyBhICBudW1iZXIgb2YgVm9JUCBjYWxscw0KPiBiZXR3
ZWVuDQo+ID4gdGhlbS4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PllvdSBoYXZlIG9uZSBh
ZHZhbnRhZ2U6IHRoZSBmbG93cyAgaGF2ZSB0aGUgc2FtZSBvcmlnaW4NCj4gPj4gPj4+IGFuZA0K
PiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+ZGVzdGluYXRpb24sIHNvIGhlYWRlciBjb21wcmVz
c2lvbiBpcyBlZmZlY3RpdmUuDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4NCj4gPj4gPj4+
DQo+ID4+ID4+PiAgID4+Pj4+PiAtSWYgeW91IGFyZSB0aGUgb3BlcmF0b3Igb2YgdGhlIHNhdGVs
bGl0ZSwgeW91IGhhdmUNCj4gPj4gPj4+IGFub3RoZXINCj4gPj4gPj4gcHJvYmxlbToNCj4gPj4g
Pj4+DQo+ID4+ID4+PiAgID4+Pj4+PiB5b3UNCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiBt
YXkgaGF2ZSB0byBjaGVjayBldmVyeSBmbG93LCBhbmQgdHJ5IHRvIGdyb3VwIHRoZW0uDQo+ID4+
ID4+PiBQZXJoYXBzIGl0DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4gbWF5IGJlIGVhc3ks
IGJ1dCBpZiB5b3Ugd2FudCB0byBzYXZlIGhlYWRlcnMsIHlvdSBuZWVkDQo+ID4+ID4+PiBmbG93
cyB3aXRoDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4gdGhlIHNhbWUgb3JpZ2luIGFuZCBk
ZXN0aW5hdGlvbi4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+Pg0KPiA+PiA+Pj4NCj4gPj4g
Pj4+ICAgPj4+Pj4+IEkgdGhpbmsgdGhhdCB0aGVyZSBhcmUgZGlmZmVyZW50IHNjZW5hcmlvcywg
YW5kIGVhY2gNCj4gPj4gPj4+IMOCwrNhY3RvcsOCwrINCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+
Pj4+Pm1heSAgdHJ5IHRvICB1c2UgVENNVEYgaW4gdGhlIGJlc3QgcGxhY2U6IGEgaGlnaCBudW1i
ZXINCj4gPj4gPj4+IG9mIGZsb3dzLA0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+d2l0aCBz
bWFsbCAgcGFja2V0cywgIGFuZCBzaGFyaW5nIHRoZSBzYW1lIG9yaWdpbiBhbmQNCj4gPj4gPiBk
ZXN0aW5hdGlvbi4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+Pg0KPiA+PiA+Pj4NCj4gPj4g
Pj4+ICAgPj4+Pj4+IERvIHlvdSBhZ3JlZT8NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+Pg0K
PiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+IEpvc2UNCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+
Pj4+Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+ICpEZToqdGNtdGYtYm91bmNlc0BpZXRm
Lm9yZyBbbWFpbHRvOnRjbXRmLQ0KPiA+PiBib3VuY2VzQGlldGYub3JnXQ0KPiA+PiA+Pj4gPG1h
aWx0bzpbbWFpbHRvOnRjbXRmLWJvdW5jZXNAaWV0Zi5vcmddPiAqRW4NCj4gPj4gPj4+DQo+ID4+
ID4+PiAgID4+Pj4+PiBub21icmUgZGUgKkZFUk5BTkRPIFBBU0NVQUwgQkxBTkNPICpFbnZpYWRv
IGVsOioNCj4gPj4gbWFydGVzLA0KPiA+PiA+PiAwNCBkZQ0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAg
Pj4+Pj4+IHNlcHRpZW1icmUgZGUgMjAxMiAxMjoyNw0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+
Pj4+ICpQYXJhOiogdGNtdGZAaWV0Zi5vcmcgPG1haWx0bzp0Y210ZkBpZXRmLm9yZz4NCj4gPj4g
Pj4+DQo+ID4+ID4+PiAgID4+Pj4+PiAqQXN1bnRvOiogUmU6IFt0Y210Zl0gRGlzY3Vzc2luZyBN
Mk0gc2NlbmFyaW8gYW5kDQo+ID4+ID4+PiBzYXZpbmdzDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+
Pj4+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiBIaSBhbGwsDQo+ID4+ID4+Pg0KPiA+
PiA+Pj4gICA+Pj4+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiBZZXMsIE0yTSBzZW5z
b3IgbmV0d29ya3MgYXJlIGEgdmVyeSBnb29kIGV4YW1wbGUgaW4NCj4gPj4gPj4+IG9yZGVyIHRv
IHNhdmUNCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiBiYW5kd2lkdGggaW4gbG9uZyBkaXN0
YW5jZS9iaWcgbGF0ZW5jeS9sb3cgYmFuZHdpZHRoDQo+ID4+ID4+PiBsaW5rcywgbGlua3MNCj4g
Pj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiB3ZXJlIHRoZSBjb3N0IHBlciBiaXQgaXMgaGlnaC4g
RG8geW91IHRoaW5rIG5ldHdvcmsNCj4gPj4gPj4+IGNhcnJpZXJzDQo+ID4+ID4+Pg0KPiA+PiA+
Pj4gICA+Pj4+Pj4gb3BlcmF0aW5nIHRoaXMga2luZCBvZiBsaW5rcyAoc2F0ZWxsaXRlIGxpbmtz
IG9yIGxvbmcNCj4gPj4gPj4+IGRpc3RhbmNlDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4g
d2lyZXMpIHdvdWxkIGJlIGludGVyZXN0ZWQgaW4gYXBwbHkgVENNVEY/DQo+ID4+ID4+Pg0KPiA+
PiA+Pj4gICA+Pj4+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiBSZWdhcmRzLA0KPiA+
PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4gRmVy
bmFuZG8NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAg
Pj4+Pj4+ICpGcm9tOip0Y210Zi1ib3VuY2VzQGlldGYub3JnIDxtYWlsdG86dGNtdGYtDQo+ID4+
ID4+IGJvdW5jZXNAaWV0Zi5vcmc+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4gW21haWx0
bzp0Y210Zi1ib3VuY2VzQGlldGYub3JnXQ0KPiA+PiA+Pj4gPG1haWx0bzpbbWFpbHRvOnRjbXRm
LWJvdW5jZXNAaWV0Zi5vcmddPg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+IDxtYWlsdG86
W21haWx0bzp0Y210Zi1ib3VuY2VzQGlldGYub3JnXT4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+
Pj4+PiAqT24gQmVoYWxmIE9mICpKb3NlIFNhbGRhbmENCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+
Pj4+PiAqU2VudDoqIG1hcnRlcywgMDQgZGUgc2VwdGllbWJyZSBkZSAyMDEyIDk6NDENCj4gPj4g
Pj4+DQo+ID4+ID4+PiAgID4+Pj4+PiAqVG86KiB0Y210ZkBpZXRmLm9yZyA8bWFpbHRvOnRjbXRm
QGlldGYub3JnPg0KPiA+PiA+Pj4gPG1haWx0bzp0Y210ZkBpZXRmLm9yZz4NCj4gPj4gPj4+DQo+
ID4+ID4+PiAgID4+Pj4+PiAqQ2M6KiBNYXR0ZW8uQmVyaW9saUBkbHIuZGUNCj4gPj4gPj4+IDxt
YWlsdG86TWF0dGVvLkJlcmlvbGlAZGxyLmRlPiA8bWFpbHRvOk1hdHRlby5CZXJpb2xpQGRsci5k
ZT47DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4gVG9tYXNvLmRlQ29sYUBkbHIuZGUgPG1h
aWx0bzpUb21hc28uZGVDb2xhQGRsci5kZT4NCj4gPj4gPj4+IDxtYWlsdG86VG9tYXNvLmRlQ29s
YUBkbHIuZGU+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4gKlN1YmplY3Q6KiBbdGNtdGZd
IERpc2N1c3NpbmcgTTJNIHNjZW5hcmlvIGFuZCBzYXZpbmdzDQo+ID4+ID4+Pg0KPiA+PiA+Pj4g
ICA+Pj4+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiBIaSBhZ2FpbiwNCj4gPj4gPj4+
DQo+ID4+ID4+PiAgID4+Pj4+Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+IFdlIGFscmVh
ZHkgZGlzY3Vzc2VkIHNvbWUgcG9pbnRzIGFib3V0IHRoZSBNMk0NCj4gPj4gPj4+IHNjZW5hcmlv
IGF0IHRoZQ0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+YmVnaW5uaW5nICBvZiBBdWd1c3Qu
IFdlIGFyZSBjdXJyZW50bHkgc3R1ZHlpbmcgdGhpcywNCj4gYW5kDQo+ID4+ID4+PiB3ZSBoYXZl
DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj5idWlsdCBzb21lICBmaWd1cmVzLCBpbiBjb2xs
YWJvcmF0aW9uIHdpdGggcGVvcGxlIGZyb20NCj4gPj4gPj4+IERMUiAoVG9tYXNvDQo+ID4+ID4+
Pg0KPiA+PiA+Pj4gICA+Pj4+Pj5hbmQgTWF0dGVvKS4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+
Pj4+PllvdQ0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+IGNhbiBmaW5kIHRoZSBmaWd1cmVz
IGhlcmU6DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAg
ID4+Pj4+Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4+Pj4+Pg0KPiA+
PiBodHRwOi8vZGllYy51bml6YXIuZXMvfmpzYWxkYW5hL3BlcnNvbmFsL3RjbXRmX2ZpZ3VyZXMv
bTJtX3NhdmkNCj4gPj4gPj4+Pj4+Pj4gbg0KPiA+PiA+Pj4gZ3MNCj4gPj4gPj4+DQo+ID4+ID4+
PiAgID4+Pj4+Pi5wZA0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+Zg0KPiA+PiA+Pj4NCj4g
Pj4gPj4+ICAgPj4+Pj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4NCj4gPj4gPj4+DQo+
ID4+ID4+Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+Pj4+Pj4NCj4gPj4gaHR0cDovL2RpZWMudW5pemFy
LmVzL35qc2FsZGFuYS9wZXJzb25hbC90Y210Zl9maWd1cmVzL20ybV9zY2VuDQo+ID4+ID4+Pj4+
Pj4+IGENCj4gPj4gPj4+IHJpDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj5vLnANCj4gPj4g
Pj4+DQo+ID4+ID4+PiAgID4+Pj4+PmRmDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4NCj4g
Pj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiBQZXJoYXBzIHdlIGNvdWxkIGNvbW1lbnQgdGhlbSwg
aW4gb3JkZXIgdG8gZGlzY3Vzcw0KPiA+PiA+Pj4gdGhpcyBzY2VuYXJpbywNCj4gPj4gPj4+DQo+
ID4+ID4+PiAgID4+Pj4+PiBhbmQgd2UgbWF5IGZpbmQgbmV3IG9uZXMgaW4gd2hpY2ggVENNVEYg
Y2FuIGJlIHVzZWZ1bC4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+Pg0KPiA+PiA+Pj4NCj4g
Pj4gPj4+ICAgPj4+Pj4+IFRoYW5rcywNCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+Pg0KPiA+
PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+IEpvc2UNCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+
Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4NCj4gPj4g
Pj4+Pj4+Pj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KPiA+PiA+Pj4+Pj4+Pj4gLQ0KPiAtDQo+ID4+ID4+Pj4+Pj4+PiAtLS0NCj4g
Pj4gPj4+Pj4+Pj4+IC0tDQo+ID4+ID4+PiAtLQ0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+
LS0tDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4tLQ0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAg
Pj4+Pj4+LQ0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4g
ICA+Pj4+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiBFc3RlIG1lbnNhamUgc2UgZGly
aWdlIGV4Y2x1c2l2YW1lbnRlIGEgc3UNCj4gZGVzdGluYXRhcmlvLg0KPiA+PiA+Pj4gUHVlZGUN
Cj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiBjb25zdWx0YXIgbnVlc3RyYSBwb2zDg8KtdGlj
YSBkZSBlbnbDg8KtbyB5IHJlY2VwY2nDg8KzbiBkZQ0KPiA+PiA+Pj4gY29ycmVvDQo+ID4+ID4+
Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4gZWxlY3Ryw4PCs25pY28gZW4gZWwgZW5sYWNlIHNpdHVhZG8g
bcODwqFzIGFiYWpvLg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+IFRoaXMgbWVzc2FnZSBp
cyBpbnRlbmRlZCBleGNsdXNpdmVseSBmb3IgaXRzIGFkZHJlc3NlZS4NCj4gPj4gPj4+IFdlIG9u
bHkNCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiBzZW5kIGFuZCByZWNlaXZlIGVtYWlsIG9u
IHRoZSBiYXNpcyBvZiB0aGUgdGVybXMgc2V0DQo+IG91dA0KPiA+PiBhdDoNCj4gPj4gPj4+DQo+
ID4+ID4+PiAgID4+Pj4+PiBodHRwOi8vd3d3LnRpZC5lcy9FUy9QQUdJTkFTL2Rpc2NsYWltZXIu
YXNweA0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+
Pj4+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAg
Pj4+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4gdGNtdGYgbWFpbGluZyBsaXN0DQo+ID4+ID4+Pg0K
PiA+PiA+Pj4gICA+Pj4+Pj4gdGNtdGZAaWV0Zi5vcmcgPG1haWx0bzp0Y210ZkBpZXRmLm9yZz4N
Cj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3RjbXRmDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pj4NCj4gPj4gPj4+DQo+
ID4+ID4+PiAgID4+Pj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+Pl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+
Pj4+PnRjbXRmIG1haWxpbmcgbGlzdA0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+Pj50Y210ZkBp
ZXRmLm9yZyA8bWFpbHRvOnRjbXRmQGlldGYub3JnPg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+
Pj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQo+ID4+ID4+Pg0K
PiA+PiA+Pj4gICA+Pj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+DQo+ID4+ID4+Pg0KPiA+
PiA+Pj4gICA+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+ID4+Pg0K
PiA+PiA+Pj4gICA+Pj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pj4+IEVzdGUgbWVuc2FqZSBz
ZSBkaXJpZ2UgZXhjbHVzaXZhbWVudGUgYSBzdSBkZXN0aW5hdGFyaW8uDQo+ID4+ID4+PiBQdWVk
ZQ0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+PiBjb25zdWx0YXIgbnVlc3RyYSBwb2zDg8KtdGlj
YSBkZSBlbnbDg8KtbyB5IHJlY2VwY2nDg8KzbiBkZQ0KPiA+PiA+Pj4gY29ycmVvDQo+ID4+ID4+
Pg0KPiA+PiA+Pj4gICA+Pj4+IGVsZWN0csODwrNuaWNvIGVuIGVsIGVubGFjZSBzaXR1YWRvIG3D
g8KhcyBhYmFqby4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pj4gVGhpcyBtZXNzYWdlIGlzIGlu
dGVuZGVkIGV4Y2x1c2l2ZWx5IGZvciBpdHMgYWRkcmVzc2VlLg0KPiBXZQ0KPiA+PiA+Pj4gb25s
eQ0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4+PiBzZW5kIGFuZCByZWNlaXZlIGVtYWlsIG9uIHRo
ZSBiYXNpcyBvZiB0aGUgdGVybXMgc2V0IG91dA0KPiBhdDoNCj4gPj4gPj4+DQo+ID4+ID4+PiAg
ID4+Pj4gaHR0cDovL3d3dy50aWQuZXMvRVMvUEFHSU5BUy9kaXNjbGFpbWVyLmFzcHgNCj4gPj4g
Pj4+DQo+ID4+ID4+PiAgID4+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+Pg0KPiA+PiA+Pj4N
Cj4gPj4gPj4+ICAgPj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pg0KPiA+PiA+Pj4NCj4gPj4g
Pj4+ICAgPj4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+IF9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+Pg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAg
Pj4gRXN0ZSBtZW5zYWplIHNlIGRpcmlnZSBleGNsdXNpdmFtZW50ZSBhIHN1IGRlc3RpbmF0YXJp
by4NCj4gPj4gPj4+IFB1ZWRlDQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+PiBjb25zdWx0YXIgbnVl
c3RyYSBwb2zDg8KtdGljYSBkZSBlbnbDg8KtbyB5IHJlY2VwY2nDg8KzbiBkZQ0KPiBjb3JyZW8N
Cj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+IGVsZWN0csODwrNuaWNvIGVuIGVsIGVubGFjZSBzaXR1
YWRvIG3Dg8KhcyBhYmFqby4NCj4gPj4gPj4+DQo+ID4+ID4+PiAgID4+IFRoaXMgbWVzc2FnZSBp
cyBpbnRlbmRlZCBleGNsdXNpdmVseSBmb3IgaXRzIGFkZHJlc3NlZS4gV2UNCj4gPj4gPj4+IG9u
bHkgc2VuZA0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4gYW5kIHJlY2VpdmUgZW1haWwgb24gdGhl
IGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQgb3V0IGF0Og0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPj4g
aHR0cDovL3d3dy50aWQuZXMvRVMvUEFHSU5BUy9kaXNjbGFpbWVyLmFzcHgNCj4gPj4gPj4+DQo+
ID4+ID4+PiAgID4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4g
ICA+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gICA+X19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPj4gPj4+DQo+ID4+
ID4+PiAgID50Y210ZiBtYWlsaW5nIGxpc3QNCj4gPj4gPj4+DQo+ID4+ID4+PiAgID50Y210ZkBp
ZXRmLm9yZyA8bWFpbHRvOnRjbXRmQGlldGYub3JnPg0KPiA+PiA+Pj4NCj4gPj4gPj4+ICAgPmh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCj4gPj4gPj4+DQo+ID4+
ID4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+PiA+Pj4NCj4gPj4gPj4+
IEVzdGUgbWVuc2FqZSBzZSBkaXJpZ2UgZXhjbHVzaXZhbWVudGUgYSBzdSBkZXN0aW5hdGFyaW8u
IFB1ZWRlDQo+ID4+ID4+PiBjb25zdWx0YXIgbnVlc3RyYSBwb2zDrXRpY2EgZGUgZW52w61vIHkg
cmVjZXBjacOzbiBkZSBjb3JyZW8NCj4gPj4gPj4+IGVsZWN0csOzbmljbyBlbiBlbCBlbmxhY2Ug
c2l0dWFkbyBtw6FzIGFiYWpvLg0KPiA+PiA+Pj4NCj4gPj4gPj4+IFRoaXMgbWVzc2FnZSBpcyBp
bnRlbmRlZCBleGNsdXNpdmVseSBmb3IgaXRzIGFkZHJlc3NlZS4gV2Ugb25seQ0KPiA+PiA+Pj4g
c2VuZCBhbmQgcmVjZWl2ZSBlbWFpbCBvbiB0aGUgYmFzaXMgb2YgdGhlIHRlcm1zIHNldCBvdXQg
YXQ6DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gaHR0cDovL3d3dy50aWQuZXMvRVMvUEFHSU5BUy9kaXNj
bGFpbWVyLmFzcHgNCj4gPj4gPj4+DQo+ID4+ID4+PiBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KPiA+PiA+Pj4NCj4gPj4gPj4+IHRjbXRmIG1haWxpbmcg
bGlzdA0KPiA+PiA+Pj4NCj4gPj4gPj4+IHRjbXRmQGlldGYub3JnIDxtYWlsdG86dGNtdGZAaWV0
Zi5vcmc+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby90Y210Zg0KPiA+PiA+Pj4NCj4gPj4gPj4+DQo+ID4+ID4+Pg0KPiA+PiA+Pj4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPj4gPj4+IHRj
bXRmIG1haWxpbmcgbGlzdA0KPiA+PiA+Pj4gdGNtdGZAaWV0Zi5vcmcNCj4gPj4gPj4+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCj4gPj4gPj4+DQo+ID4+ID4+
DQo+ID4+ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQo+ID4+ID4+IHRjbXRmIG1haWxpbmcgbGlzdA0KPiA+PiA+PiB0Y210ZkBpZXRmLm9yZw0KPiA+
PiA+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQo+ID4+ID4N
Cj4gPj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K
PiA+PiA+IHRjbXRmIG1haWxpbmcgbGlzdA0KPiA+PiA+IHRjbXRmQGlldGYub3JnDQo+ID4+ID4g
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90Y210Zg0KPiA+PiA+DQo+ID4+
DQo+ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
ID4+IHRjbXRmIG1haWxpbmcgbGlzdA0KPiA+PiB0Y210ZkBpZXRmLm9yZw0KPiA+PiBodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQo+ID4NCj4gPiBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+IHRjbXRmIG1haWxpbmcg
bGlzdA0KPiA+IHRjbXRmQGlldGYub3JnDQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby90Y210Zg0KPiA+DQo+DQo+DQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQo+IHRjbXRmIG1haWxpbmcgbGlzdA0KPiB0Y210ZkBpZXRm
Lm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQo+DQo+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+DQo+IEVzdGUgbWVuc2FqZSBzZSBk
aXJpZ2UgZXhjbHVzaXZhbWVudGUgYSBzdSBkZXN0aW5hdGFyaW8uIFB1ZWRlDQo+IGNvbnN1bHRh
ciBudWVzdHJhIHBvbMOtdGljYSBkZSBlbnbDrW8geSByZWNlcGNpw7NuIGRlIGNvcnJlbyBlbGVj
dHLDs25pY28NCj4gZW4gZWwgZW5sYWNlIHNpdHVhZG8gbcOhcyBhYmFqby4NCj4gVGhpcyBtZXNz
YWdlIGlzIGludGVuZGVkIGV4Y2x1c2l2ZWx5IGZvciBpdHMgYWRkcmVzc2VlLiBXZSBvbmx5IHNl
bmQNCj4gYW5kIHJlY2VpdmUgZW1haWwgb24gdGhlIGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQgb3V0
IGF0Og0KPiBodHRwOi8vd3d3LnRpZC5lcy9FUy9QQUdJTkFTL2Rpc2NsYWltZXIuYXNweA0KPiBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiB0Y210ZiBt
YWlsaW5nIGxpc3QNCj4gdGNtdGZAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby90Y210Zg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQoNCkVzdGUgbWVuc2FqZSBzZSBkaXJpZ2UgZXhjbHVzaXZhbWVudGUgYSBzdSBkZXN0aW5hdGFy
aW8uIFB1ZWRlIGNvbnN1bHRhciBudWVzdHJhIHBvbMOtdGljYSBkZSBlbnbDrW8geSByZWNlcGNp
w7NuIGRlIGNvcnJlbyBlbGVjdHLDs25pY28gZW4gZWwgZW5sYWNlIHNpdHVhZG8gbcOhcyBhYmFq
by4NClRoaXMgbWVzc2FnZSBpcyBpbnRlbmRlZCBleGNsdXNpdmVseSBmb3IgaXRzIGFkZHJlc3Nl
ZS4gV2Ugb25seSBzZW5kIGFuZCByZWNlaXZlIGVtYWlsIG9uIHRoZSBiYXNpcyBvZiB0aGUgdGVy
bXMgc2V0IG91dCBhdDoNCmh0dHA6Ly93d3cudGlkLmVzL0VTL1BBR0lOQVMvZGlzY2xhaW1lci5h
c3B4DQo=

From jacl@tid.es  Wed Oct  3 07:59:19 2012
Return-Path: <jacl@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 CF7DD21F84C2 for <tcmtf@ietfa.amsl.com>; Wed,  3 Oct 2012 07:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RNU4hX0vdui4 for <tcmtf@ietfa.amsl.com>; Wed,  3 Oct 2012 07:59:18 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4868421F846F for <tcmtf@ietf.org>; Wed,  3 Oct 2012 07:59:16 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MBB004K3OARSM@tid.hi.inet> for tcmtf@ietf.org; Wed, 03 Oct 2012 16:59:15 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id C0.C9.03050.3C25C605; Wed, 03 Oct 2012 16:59:15 +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 <0MBB004JXOARSM@tid.hi.inet> for tcmtf@ietf.org; Wed, 03 Oct 2012 16:59:15 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.209]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0318.001; Wed, 03 Oct 2012 16:59:15 +0200
Date: Wed, 03 Oct 2012 14:59:14 +0000
From: JUAN ANTONIO CASTELL LUCIA <jacl@tid.es>
In-reply-to: <90ED8822CB577741B9A1668A4753931218F4889D@EX10-MB2-MAD.hi.inet>
X-Originating-IP: [10.95.64.115]
To: =?iso-8859-1?Q?MANUEL_NU=D1EZ_SANZ?= <mns@tid.es>, "jsaldana@unizar.es" <jsaldana@unizar.es>, FERNANDO PASCUAL BLANCO <fpb@tid.es>
Message-id: <49F52EC1A431BA4BBA8BA8CFF429B73902ADC3@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_P+QoGh5Za2vMdMklRn1qpA)"
Content-language: es-ES
Accept-Language: es-ES, en-US
Thread-topic: [tcmtf] Next steps with TCMTF
Thread-index: Ac2cmrry4BaRIpi1Sm27mcZI4g4aKwAJ1PiAACHikIAAnT3mcABr3YJw
X-AuditID: 0a5f4068-b7f176d000000bea-47-506c52c3a1e7
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA12TbzAUYRzH53Fn7d1Ys52787giLt4QMSVEpZqohhzJCzVpdet2dY7ZvZNr pkZ/yCBTYSpR3EhRil5FmTFnpheZEUYzxkyMPynyonF1xTRq1x4d7z7P78/3+91nd1GRrMZN hdIGI8kYCL0akYqlmXHSkN5UvSZsZlkV1WVrB3HgSFPToosGZEhjtaSeLiCZHfvOSqlrvaUg 36ItbLbUiYrA57QyIEEhvgva74y4CqyEA2MvkTIgRWV4B4D20mJX4bAIYNfQsONwH8CZoUmE XxHjgfDq44oVRvBQaG39C3j2xIPg0sIPN54leCKct8wCwcIP/umfEvNCcrwUwK/jjdwQioo4 oYd2f34Gw4/C4hELIvAm+LtqTMyzCM+Gd0daRAJ7wbql2yuxAe4DWz70rejL8WC4aF9ABI6H Jb8qxIKvHE4M9iECK+Ds1LLjYWYBbJl/53YLKGud/Gqd/Gqd/AQOhSM11YjAwbC58ZtjJh1a 6z856vHwecUMx1KOBwD8Pt3maPjD6vIJtwYgaQVKNouhdZQxl6D1urDwUIoOpQ2k8RUQXiv1 GjzpDLACHAVqd8zvTY5G5koUsOZcK4hGXdQK7CD31mUeWXlaM0WwVCZj0pOs2he7mUBrZF5r ZdbE5tPn6DwTm2li9FYQwIWYbH82AFRiQ56BVMuxvuOcDqYlzBdJJk+QsYL9KKqG2HgK19rE kDqyMJvWc1+dw8UfM9dzeVTOnY1GLqjECiJRd87Bn0+KsflELkvrHBI+mI0Pqlytrl9/D2JU XpgtmdvD+QnKZFhzV/lhyby7t1Nj/fYciOAuzRML533dud/lv+0WLNF2XiNTOIob9yK5m5Vj T0Ny+LxGwuicdxtvqlytrt9UFYF7McMue08lXDf3le/27Sk4pO0+czh5Yntxc3piiqiyw7v7 QELcR1nJo4Wgxi/WpNj+QONodkqVvbttc+kVz63HqJ4ym9GiT620/0STCkbrq+2diuzTF07E eTKjaXteTI9X6sjBSwnIg/oeZi5DcaMhKert5Qj36R5Zzs7m6JMe0WoxSxHhQSKGJf4B095c GCgEAAA=
References: <007801cd9c9b$3b06d5a0$b11480e0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A249D7B626@EX10-MB1-MAD.hi.inet> <001c01cd9d5a$5d104fe0$1730efa0$@unizar.es> <90ED8822CB577741B9A1668A4753931218F4889D@EX10-MB2-MAD.hi.inet>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Next steps with 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, 03 Oct 2012 14:59:20 -0000

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

Hi all, regarding question A), I would like to comment that I suppose that =
what Fernando wanted to propose is to include an "additional condition" in =
the moment to establish a tunnel between the two peers: some criteria that =
helped to classify the packets in flows with different delay/packet loss re=
quirements in order to have separate tunnels between these two peers, with =
different policies for multiplexing and compressing (e.g. maximum time befo=
re to send a packet, the suggestion of Manuel of completing the payload wit=
h packets with the following kind of flow with lower requirements, etc).

But in all of these cases, the destination IP/Port should be part of the cr=
iteria.

In this sense, I also agree with the proposal of including it in draft b).


Regards.


-----Mensaje original-----
De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de MAN=
UEL NU=D1EZ SANZ
Enviado el: lunes, 01 de octubre de 2012 16:34
Para: jsaldana@unizar.es; FERNANDO PASCUAL BLANCO
CC: tcmtf@ietf.org
Asunto: Re: [tcmtf] Next steps with TCMTF

Hi Jose,
    I am going to try to answer you inline with mark [MNS].

 I hope it has sense.

Manuel.

-----Mensaje original-----
De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de Jos=
e Saldana Enviado el: viernes, 28 de septiembre de 2012 11:19
Para: FERNANDO PASCUAL BLANCO
CC: tcmtf@ietf.org
Asunto: Re: [tcmtf] Next steps with TCMTF

Fernando,

I have been thinking about it. There are three questions:


A) Should we map packet marks like DiffServ to different tunnels between th=
e same points?

There is a first question: it does not exist (by now) a universally accepte=
d standard about Diffserv mapping for different services. Perhaps an ISP ma=
y have a clear classification, so it can be useful for this, if the tunnel =
is created inside his aggregation network.

Although marking can be useful, perhaps it would not be enough: if you want=
 to group the packets of a certain game, and establish a tunnel finishing a=
t the game server, you need to identify them by the destination IP. So I th=
ink you would need something more than Diffserv.


[MNS] I agree, although marking by ISP o equivalent could be very useful, o=
ther options like "IP sources", "specific ports" could be equally valid.

My proposal: including in the draft b) a sentence like "Different mechanism=
s can be used in order to decide which packets are included into each tunne=
l.
For example, Diffserv can be useful when doing this. In other cases, the pa=
cket flows would have to be identified by their origin and/or destination I=
P addresses."

[MNS] I also agree with that open way.

Fernando (and people from network operators): please think about this. As n=
etwork providers, you should have a clearer idea about this.

B) Could we mix some flows and under what conditions?

If the tunnel is only set inside the ISP network, or between two ISPs, then=
 I think there is no problem on grouping packets from different services, o=
r even transport protocols (UDP and TCP flows in the same tunnel). The ques=
tion is that you have to accomplish the delay requirements of the most dela=
y-sensitive service.

As we have three layers (compressing, multiplexing, tunneling), I think tha=
t tunneling and multiplexing layers do not have to know which kind of packe=
t they are carrying. (I am posting another message about this).

Other question is: if you can set up a tunnel covering the whole route (e.g=
., from the access network to the game server), then you can only group pac=
kets of a single game. On the other hand, if you only group packets in your=
 aggregation network, you can group a big number of flows. When the tunnel =
arrives at the internet router, the packets are rebuilt and sent in their n=
ative form.

So the longer the common route you want to cover, the more specific traffic=
 you can tunnel.

[MNS] I think there no problem on grouping packets from different service a=
s long as each grouped services has the same "delay sensitive" level and th=
e same IP destination (internet router, game data center...). In fact, refi=
ning this idea... if for example the most delay-sensitive flow has not reac=
hed its optimum full it could be complete with the following traffic with s=
hould be less delay-sensitive, and so on. In this way always each flow is s=
ent with its optimum payload.

C) Do you think that would be included in your second draft proposal?

 By now, I think this can be issued in draft b). However, we have to furthe=
r think about it.


Thank you,

Jose

[MNS] Thanks,  Manuel


> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
> de FERNANDO PASCUAL BLANCO Enviado el: jueves, 27 de septiembre de
> 2012 17:08
> Para: jsaldana@unizar.es; tcmtf@ietf.org
> CC: Wesley Eddy; Martin Stiemerling
> Asunto: Re: [tcmtf] Next steps with TCMTF
>
> Hi Jose,
>
>         I absolutely agree with your classification. Nevertheless I
> miss a
draft
> explaining how to deal with different QoS flows passing through a
> TCMTF
> tunnel: Should we map packet marks like DiffServ to different tunnels
> between the same points? Could we mix some flows and under what
> conditions? Do you think that would be included in your second draft
> proposal?
>
> Regards,
>
> Fernando Pascual Blanco
> Telef=F3nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>
>
>
>
> On 27/09/12 12:31, "Jose Saldana" <jsaldana@unizar.es> wrote:
>
> >Hello all,
> >
> >I would like to discuss in this list the possibility of creating a
> >small Working Group for TCMTF, as suggested by Wes. It could have the
> >task of making a RFC from TCMTF, or a wider scope. I think that
> >perhaps more than a draft would be necessary. I mean, I have been
> >thinking about it, and perhaps the work could be divided into the next p=
arts:
> >
> > a) "Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03),
> >including the protocol stack of TCMTF. The current proposal has
> >different options, but the concrete one to use is static: in the
> >set-up moment, you decide that "between these two routers a tunnel is
> >set including all the packets with this IP origin and destination".
> >
> >b) "Recommendations draft": another "informational" one, with
> >recommendations of maximum delays to be added to different kinds of
> >services, different multiplexing policies, implementation issues
> >related to the selection of the best compression algorithm to use, etc.
> >Some hypothetical examples:
> >      -  "if you are multiplexing a First Person Shooter, your
> >multiplexer should not retain packets more than 50 ms"
> >- "if you are multiplexing in a low-end router in a wired scenario,
> >you don't need to use ROHC. A simpler scheme like IPHC can be enough,
> >and it will not require a lot of processing capacity".
> >
> >c) "Dynamic Signaling draft": perhaps another one including a
> >signaling system in order to:
> >       - dynamically "negotiate" the concrete options of TCMTF you
> >are going to use
> >       - if two routers notice that a rush hour is arriving, they
> >could send some packets asking other routers if they have some flows
> >in common with them, which could be multiplexed.
> >
> >
> >The main questions are:
> >
> >Is this enough for creating a working group?
> >
> >Do you think the distribution of the work into three draft makes sense?
> >
> >Is there any other issue which should be studied and standardized?
> >Perhaps other people could imagine more things.
> >
> >So let's start the discussion.
> >
> >Thanks in advance,
> >
> >Jose
> >
> >
> >_______________________________________________
> >tcmtf mailing list
> >tcmtf@ietf.org
> >https://www.ietf.org/mailman/listinfo/tcmtf
>
>
> ________________________________
>
> Este mensaje se dirige exclusivamente a su destinatario. Puede
> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3=
nico
> en el enlace situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send
> and receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf

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

________________________________

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

________________________________

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

--Boundary_(ID_P+QoGh5Za2vMdMklRn1qpA)
Content-type: text/x-vcard;
 name="=?iso-8859-1?Q?Juan_Antonio_Castell_Luc=EDa.vcf?="
Content-transfer-encoding: base64
Content-disposition: attachment;
 filename="=?iso-8859-1?Q?Juan_Antonio_Castell_Luc=EDa.vcf?="; size=1816;
 creation-date="Wed, 03 Oct 2012 14:59:14 GMT";
 modification-date="Wed, 03 Oct 2012 14:59:14 GMT"
Content-description: =?iso-8859-1?Q?Juan_Antonio_Castell_Luc=EDa.vcf?=

QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpYLU1TLVNJR05BVFVSRTpZRVMNCk47TEFOR1VBR0U9
ZXM7Q0hBUlNFVD1XaW5kb3dzLTEyNTI6Q2FzdGVsbCBMdWPtYTtKdWFuIEFudG9uaW8NCkZOO0NI
QVJTRVQ9V2luZG93cy0xMjUyOkp1YW4gQW50b25pbyBDYXN0ZWxsIEx1Y+1hDQpPUkc7Q0hBUlNF
VD1XaW5kb3dzLTEyNTI6VGVsZWbzbmljYSBHbG9iYWwgUmVzb3VyY2VzDQpUSVRMRTpBdXRvbWF0
ZWQgYW5kIER5bmFtaWMgTmV0d29ya3MNClRFTDtXT1JLO1ZPSUNFOiszNCA5MTMxMjkxNTcNClRF
TDtDRUxMO1ZPSUNFOjY5MDY0MTQ1Mg0KQURSO1dPUks7UFJFRjtDSEFSU0VUPVdpbmRvd3MtMTI1
Mjo7O2MvRG9uIFJhbfNuIGRlIGxhIENydXo7TWFkcmlkOzgyLTg0OzI4MDA2O0VzcGHxYQ0KTEFC
RUw7V09SSztQUkVGO0NIQVJTRVQ9V2luZG93cy0xMjUyO0VOQ09ESU5HPVFVT1RFRC1QUklOVEFC
TEU6Yy9Eb24gUmFtPUYzbiBkZSBsYSBDcnV6IDgyLTg0PTBEPTBBPQ0KMjgwMDYgIE1hZHJpZA0K
WC1NUy1PTC1ERUZBVUxULVBPU1RBTC1BRERSRVNTOjINCkVNQUlMO1BSRUY7SU5URVJORVQ6amFj
bEB0aWQuZXMNClgtTVMtT0wtREVTSUdOO0NIQVJTRVQ9dXRmLTg6PGNhcmQgeG1sbnM9Imh0dHA6
Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vb2ZmaWNlL291dGxvb2svMTIvZWxlY3Ryb25pY2J1c2lu
ZXNzY2FyZHMiIHZlcj0iMS4wIiBsYXlvdXQ9ImxlZnQiIGJnY29sb3I9ImZmZmZmZiI+PGltZyB4
bWxucz0iIiBhbGlnbj0iZml0IiBhcmVhPSIxNiIgdXNlPSJjYXJkcGljdHVyZSIvPjxmbGQgeG1s
bnM9IiIgcHJvcD0ibmFtZSIgYWxpZ249ImxlZnQiIGRpcj0ibHRyIiBzdHlsZT0iYiIgY29sb3I9
IjAwMDAwMCIgc2l6ZT0iMTAiLz48ZmxkIHhtbG5zPSIiIHByb3A9Im9yZyIgYWxpZ249ImxlZnQi
IGRpcj0ibHRyIiBjb2xvcj0iMDAwMDAwIiBzaXplPSI4Ii8+PGZsZCB4bWxucz0iIiBwcm9wPSJ0
aXRsZSIgYWxpZ249ImxlZnQiIGRpcj0ibHRyIiBjb2xvcj0iMDAwMDAwIiBzaXplPSI4Ii8+PGZs
ZCB4bWxucz0iIiBwcm9wPSJibGFuayIgc2l6ZT0iOCIvPjxmbGQgeG1sbnM9IiIgcHJvcD0idGVs
d29yayIgYWxpZ249ImxlZnQiIGRpcj0ibHRyIiBjb2xvcj0iMDAwMDAwIiBzaXplPSI4Ij48bGFi
ZWwgYWxpZ249InJpZ2h0IiBjb2xvcj0iNjI2MjYyIj5UcmFiYWpvPC9sYWJlbD48L2ZsZD48Zmxk
IHhtbG5zPSIiIHByb3A9InRlbGNlbGwiIGFsaWduPSJsZWZ0IiBkaXI9Imx0ciIgY29sb3I9IjAw
MDAwMCIgc2l6ZT0iOCI+PGxhYmVsIGFsaWduPSJyaWdodCIgY29sb3I9IjYyNjI2MiI+TcOzdmls
PC9sYWJlbD48L2ZsZD48ZmxkIHhtbG5zPSIiIHByb3A9ImVtYWlsIiBhbGlnbj0ibGVmdCIgZGly
PSJsdHIiIGNvbG9yPSIwMDAwMDAiIHNpemU9IjgiLz48ZmxkIHhtbG5zPSIiIHByb3A9ImFkZHJ3
b3JrIiBhbGlnbj0ibGVmdCIgZGlyPSJsdHIiIGNvbG9yPSIwMDAwMDAiIHNpemU9IjgiLz48Zmxk
IHhtbG5zPSIiIHByb3A9ImJsYW5rIiBzaXplPSI4Ii8+PGZsZCB4bWxucz0iIiBwcm9wPSJibGFu
ayIgc2l6ZT0iOCIvPjxmbGQgeG1sbnM9IiIgcHJvcD0iYmxhbmsiIHNpemU9IjgiLz48ZmxkIHht
bG5zPSIiIHByb3A9ImJsYW5rIiBzaXplPSI4Ii8+PGZsZCB4bWxucz0iIiBwcm9wPSJibGFuayIg
c2l6ZT0iOCIvPjxmbGQgeG1sbnM9IiIgcHJvcD0iYmxhbmsiIHNpemU9IjgiLz48ZmxkIHhtbG5z
PSIiIHByb3A9ImJsYW5rIiBzaXplPSI4Ii8+PGZsZCB4bWxucz0iIiBwcm9wPSJibGFuayIgc2l6
ZT0iOCIvPjwvY2FyZD4NClJFVjoyMDEyMDgxM1QxMDQ2MDBaDQpFTkQ6VkNBUkQNCg==

--Boundary_(ID_P+QoGh5Za2vMdMklRn1qpA)--

From fpb@tid.es  Thu Oct  4 00:21:13 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 3E1D01F0C8E for <tcmtf@ietfa.amsl.com>; Thu,  4 Oct 2012 00:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.881
X-Spam-Level: 
X-Spam-Status: No, score=-5.881 tagged_above=-999 required=5 tests=[AWL=0.418,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id giVBD+qD90lc for <tcmtf@ietfa.amsl.com>; Thu,  4 Oct 2012 00:21:11 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4CE081F0C92 for <tcmtf@ietf.org>; Thu,  4 Oct 2012 00:21:10 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MBC00L9VXR7WG@tid.hi.inet> for tcmtf@ietf.org; Thu, 04 Oct 2012 09:21:07 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 9E.68.03050.2E83D605; Thu, 04 Oct 2012 09:21:06 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MBC00L9RXR6WG@tid.hi.inet> for tcmtf@ietf.org; Thu, 04 Oct 2012 09:21:06 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.209]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0318.001; Thu, 04 Oct 2012 09:21:06 +0200
Date: Thu, 04 Oct 2012 07:21:05 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <49F52EC1A431BA4BBA8BA8CFF429B73902ADC3@EX10-MB2-MAD.hi.inet>
X-Originating-IP: [10.95.64.115]
To: JUAN ANTONIO CASTELL LUCIA <jacl@tid.es>, =?iso-8859-1?Q?MANUEL_NU=D1EZ_SANZ?= <mns@tid.es>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Message-id: <F5EDC35DF914C1428C28E149F10463A249D9E91A@EX10-MB2-MAD.hi.inet>
Content-id: <F622A717487C5B488D502E81730C4F98@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [tcmtf] Next steps with TCMTF
Thread-index: Ac2cmrry4BaRIpi1Sm27mcZI4g4aKwAJ1PiAACHikIAAnT3mcABr3YJwACSy0YA=
user-agent: Microsoft-MacOutlook/14.2.4.120824
X-AuditID: 0a5f4068-b7f176d000000bea-0e-506d38e28ca9
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA11TbUgTYRzn2W3zXD5xO3U+rUy3isJ0KWRq5ksiFBq66lNB2ann7mzzZbeZ 60PORALBsgzEkUNItCRQs8KyJBclrCwhCOzFqFmkVIji1LDszps1/fa73/P/vdzzgmPkd7ka Z0sstLmEMmrlCqkiL10R8znRpI/9OpqU+GCmG6SDg21tCxI9OK7YV0gb2QravCv1lIKpnXbK yt7kVs71jkrswJNeB3AcEbvR048FdSCQhyo0MtYlFzBJ9AA06JDVAQWPFwDqangNxI9mgHre PgoQpqTENnSttloiYDkRhZ5/6JQKpsE8fuHdLtCBRBaautQsEwMi0eJLj1TwCSEuAjQ1+w4I 8xjv4/RqhBlIZKPf9m5MwBixB7UvNWIir0TzjWNSkY9G9XNe30wYqqkd9fE70fjPkeUswP/M nPvWcrUQnl/wTstFnIPeO+aX50MJHWrtH8TEbgRqe/jKh0PRhOePrAEgh18Nh18Nh18Nh18N h1+NViDrBCou38waGIuJYo2G2Dgdw+rYEtpyG4gnx/SBjvtbXYDAgTYIRvYX60kZVcHZTC6Q hEu0ofBMvElPrs8vLbQxFMfkma1GmtNuhvUHWD0Z9o/mrFwZW8CWWrk8q9noAgjHtCGwV8Nr YSFlO0ubS0WpC6ThuBZBkr8vpNJMG+jKItbIXyafswbaWvgOav+VteYSPNAFEvAgPiFCsIFc GWXiWIPPIhzOCOVUK+xquRskq8PgpwReRwgTjLXkX7o6EuYK6Rv8FlarJ0E8v1HBEAq5Qfwr +B+7CR6aOa0nQ33kWl0Cv5sh8EZMsdDXQln8+24RQlUr7Gql2g4GYjiPPdNlTb2QrXkybItQ BrdkGYfVJx9HhB+pGhy2uqNHj7Y3ZbZ/a/h12TkeMVRzl9mxP6P8es1NQ/EP3YnJw4ukdkbS G2Bzn7uT8wx2TKdo6I1LxnKlpwlNZBed75NWNfcp3Xt7v1SnFNw7hg1lXJ1NczYHrqsfuNKU XNSolXIMFReFmTnqL/Hr6N7/AwAA
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Next steps with 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, 04 Oct 2012 07:21:13 -0000

Hi all,

        Yes Juan Antonio, that was my point. Even, those different tunnels
between the same two peers could be the same tunnel.

Regards,

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




On 03/10/12 16:59, "JUAN ANTONIO CASTELL LUCIA" <jacl@tid.es> wrote:

>Hi all, regarding question A), I would like to comment that I suppose
>that what Fernando wanted to propose is to include an "additional
>condition" in the moment to establish a tunnel between the two peers:
>some criteria that helped to classify the packets in flows with different
>delay/packet loss requirements in order to have separate tunnels between
>these two peers, with different policies for multiplexing and compressing
>(e.g. maximum time before to send a packet, the suggestion of Manuel of
>completing the payload with packets with the following kind of flow with
>lower requirements, etc).
>
>But in all of these cases, the destination IP/Port should be part of the
>criteria.
>
>In this sense, I also agree with the proposal of including it in draft b).
>
>
>Regards.
>
>
>-----Mensaje original-----
>De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>MANUEL NU=D1EZ SANZ
>Enviado el: lunes, 01 de octubre de 2012 16:34
>Para: jsaldana@unizar.es; FERNANDO PASCUAL BLANCO
>CC: tcmtf@ietf.org
>Asunto: Re: [tcmtf] Next steps with TCMTF
>
>Hi Jose,
>    I am going to try to answer you inline with mark [MNS].
>
> I hope it has sense.
>
>Manuel.
>
>-----Mensaje original-----
>De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>Jose Saldana Enviado el: viernes, 28 de septiembre de 2012 11:19
>Para: FERNANDO PASCUAL BLANCO
>CC: tcmtf@ietf.org
>Asunto: Re: [tcmtf] Next steps with TCMTF
>
>Fernando,
>
>I have been thinking about it. There are three questions:
>
>
>A) Should we map packet marks like DiffServ to different tunnels between
>the same points?
>
>There is a first question: it does not exist (by now) a universally
>accepted standard about Diffserv mapping for different services. Perhaps
>an ISP may have a clear classification, so it can be useful for this, if
>the tunnel is created inside his aggregation network.
>
>Although marking can be useful, perhaps it would not be enough: if you
>want to group the packets of a certain game, and establish a tunnel
>finishing at the game server, you need to identify them by the
>destination IP. So I think you would need something more than Diffserv.
>
>
>[MNS] I agree, although marking by ISP o equivalent could be very useful,
>other options like "IP sources", "specific ports" could be equally valid.
>
>My proposal: including in the draft b) a sentence like "Different
>mechanisms can be used in order to decide which packets are included into
>each tunnel.
>For example, Diffserv can be useful when doing this. In other cases, the
>packet flows would have to be identified by their origin and/or
>destination IP addresses."
>
>[MNS] I also agree with that open way.
>
>Fernando (and people from network operators): please think about this. As
>network providers, you should have a clearer idea about this.
>
>B) Could we mix some flows and under what conditions?
>
>If the tunnel is only set inside the ISP network, or between two ISPs,
>then I think there is no problem on grouping packets from different
>services, or even transport protocols (UDP and TCP flows in the same
>tunnel). The question is that you have to accomplish the delay
>requirements of the most delay-sensitive service.
>
>As we have three layers (compressing, multiplexing, tunneling), I think
>that tunneling and multiplexing layers do not have to know which kind of
>packet they are carrying. (I am posting another message about this).
>
>Other question is: if you can set up a tunnel covering the whole route
>(e.g., from the access network to the game server), then you can only
>group packets of a single game. On the other hand, if you only group
>packets in your aggregation network, you can group a big number of flows.
>When the tunnel arrives at the internet router, the packets are rebuilt
>and sent in their native form.
>
>So the longer the common route you want to cover, the more specific
>traffic you can tunnel.
>
>[MNS] I think there no problem on grouping packets from different service
>as long as each grouped services has the same "delay sensitive" level and
>the same IP destination (internet router, game data center...). In fact,
>refining this idea... if for example the most delay-sensitive flow has
>not reached its optimum full it could be complete with the following
>traffic with should be less delay-sensitive, and so on. In this way
>always each flow is sent with its optimum payload.
>
>C) Do you think that would be included in your second draft proposal?
>
> By now, I think this can be issued in draft b). However, we have to
>further think about it.
>
>
>Thank you,
>
>Jose
>
>[MNS] Thanks,  Manuel
>
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>> de FERNANDO PASCUAL BLANCO Enviado el: jueves, 27 de septiembre de
>> 2012 17:08
>> Para: jsaldana@unizar.es; tcmtf@ietf.org
>> CC: Wesley Eddy; Martin Stiemerling
>> Asunto: Re: [tcmtf] Next steps with TCMTF
>>
>> Hi Jose,
>>
>>         I absolutely agree with your classification. Nevertheless I
>> miss a
>draft
>> explaining how to deal with different QoS flows passing through a
>> TCMTF
>> tunnel: Should we map packet marks like DiffServ to different tunnels
>> between the same points? Could we mix some flows and under what
>> conditions? Do you think that would be included in your second draft
>> proposal?
>>
>> Regards,
>>
>> Fernando Pascual Blanco
>> Telef=F3nica Global Resources
>> Network Automation and Dynamization
>> TECHNOLOGY PEOPLE GROUP
>> F +34913128779
>> M +34682005168
>> fpb@tid.es
>>
>>
>>
>>
>> On 27/09/12 12:31, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>
>> >Hello all,
>> >
>> >I would like to discuss in this list the possibility of creating a
>> >small Working Group for TCMTF, as suggested by Wes. It could have the
>> >task of making a RFC from TCMTF, or a wider scope. I think that
>> >perhaps more than a draft would be necessary. I mean, I have been
>> >thinking about it, and perhaps the work could be divided into the next
>>parts:
>> >
>> > a) "Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03),
>> >including the protocol stack of TCMTF. The current proposal has
>> >different options, but the concrete one to use is static: in the
>> >set-up moment, you decide that "between these two routers a tunnel is
>> >set including all the packets with this IP origin and destination".
>> >
>> >b) "Recommendations draft": another "informational" one, with
>> >recommendations of maximum delays to be added to different kinds of
>> >services, different multiplexing policies, implementation issues
>> >related to the selection of the best compression algorithm to use, etc.
>> >Some hypothetical examples:
>> >      -  "if you are multiplexing a First Person Shooter, your
>> >multiplexer should not retain packets more than 50 ms"
>> >- "if you are multiplexing in a low-end router in a wired scenario,
>> >you don't need to use ROHC. A simpler scheme like IPHC can be enough,
>> >and it will not require a lot of processing capacity".
>> >
>> >c) "Dynamic Signaling draft": perhaps another one including a
>> >signaling system in order to:
>> >       - dynamically "negotiate" the concrete options of TCMTF you
>> >are going to use
>> >       - if two routers notice that a rush hour is arriving, they
>> >could send some packets asking other routers if they have some flows
>> >in common with them, which could be multiplexed.
>> >
>> >
>> >The main questions are:
>> >
>> >Is this enough for creating a working group?
>> >
>> >Do you think the distribution of the work into three draft makes sense?
>> >
>> >Is there any other issue which should be studied and standardized?
>> >Perhaps other people could imagine more things.
>> >
>> >So let's start the discussion.
>> >
>> >Thanks in advance,
>> >
>> >Jose
>> >
>> >
>> >_______________________________________________
>> >tcmtf mailing list
>> >tcmtf@ietf.org
>> >https://www.ietf.org/mailman/listinfo/tcmtf
>>
>>
>> ________________________________
>>
>> Este mensaje se dirige exclusivamente a su destinatario. Puede
>> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=
=F3nico
>> en el enlace situado m=E1s abajo.
>> This message is intended exclusively for its addressee. We only send
>> and receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>
>_______________________________________________
>tcmtf mailing list
>tcmtf@ietf.org
>https://www.ietf.org/mailman/listinfo/tcmtf
>
>________________________________
>
>Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el =
enlace
>situado m=E1s abajo.
>This message is intended exclusively for its addressee. We only send and
>receive email on the basis of the terms set out at:
>http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>_______________________________________________
>tcmtf mailing list
>tcmtf@ietf.org
>https://www.ietf.org/mailman/listinfo/tcmtf


________________________________

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

From jsaldana@unizar.es  Thu Oct  4 05:27:14 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 BC9C621F8658 for <tcmtf@ietfa.amsl.com>; Thu,  4 Oct 2012 05:27:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=0.450,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WiIGKrZukv2I for <tcmtf@ietfa.amsl.com>; Thu,  4 Oct 2012 05:27:13 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 71E7121F8648 for <tcmtf@ietf.org>; Thu,  4 Oct 2012 05:27:13 -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 q94CR6qn008293 for <tcmtf@ietf.org>; Thu, 4 Oct 2012 14:27:07 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Thu, 4 Oct 2012 14:27:12 +0200
Organization: Universidad de Zaragoza
Message-ID: <007301cda22b$95130ec0$bf392c40$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2iHgDnAaLmFjAERgGHYYWERGnbfg==
Content-language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Satellite-sensors scenario: new figure
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2012 12:27:14 -0000

I have been thinking about the satellite-sensors scenario. Taking into =
account all your feedback, I think some statements are clear:

	- If the satellite link is the only one, then there better compression =
schemes exist.
	- TMCTF is only interesting if a number of hops is required, one of =
them being the satellite one.
	- Header compressing requires high processing capacity.
	- Compression should be deployed where enough processing capacity is =
available.

Nother idea: although many sensor networks do not use IP, there are some =
of them using it. Nowadays, "internet of things" is a trending topic. =
"The basic idea of this concept is the pervasive presence around us of a =
variety of things or objects =E2=80=93 such as Radio-Frequency =
IDentification (RFID) tags, sensors, actuators, mobile phones, etc. =
=E2=80=93 which, through unique addressing schemes, are able to interact =
with each other and cooperate with their neighbors to reach common =
goals." =
(http://www.sciencedirect.com/science/article/pii/S1389128610001568).

Another concept is "IP to the Field" paradigm where technologies applied =
in the Internet domain percolate right up to the field devices =
(http://www.kom.tu-darmstadt.de/research-results/projects/siemens-ip-to-t=
he-field/).

=09

Thinking about the IP sensors scenario, I have done three different =
figures:

a) =
http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/satellite_scenario=
_multimux_v2.pdf

	Each WSN multiplexes and compresses its packets. And finally the =
gateway simply sends them. In this case, the processing capacity should =
be in the three multiplexers-compressors


b) =
http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/satellite_scenario=
_v2.pdf

	In this case, there is a single multiplexer-compressor, which is =
located near the antenna, and does all the work for the three WSNs.


c) =
http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/satellite_scenario=
_multimux_separate_v2.pdf

 	A third option could include task distribution: each WSN compresses =
its flows, and the shared gateway does multiplexing and tunneling. =
Perhaps the most CPU intensive task is header compression.


If sensors are not IP, perhaps some of the scenarios would still be =
interesting: you may use IP for distinguishing between different sensor =
networks, or different server destinations.


What do you think? Does this make sense? Which figure would be better?


Thanks for your valuable feedback,

Jose


From jsaldana@unizar.es  Mon Oct  8 07:09: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 1347721F85C3 for <tcmtf@ietfa.amsl.com>; Mon,  8 Oct 2012 07:09:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.877
X-Spam-Level: 
X-Spam-Status: No, score=-4.877 tagged_above=-999 required=5 tests=[AWL=-0.879, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C9wgubAXZlWr for <tcmtf@ietfa.amsl.com>; Mon,  8 Oct 2012 07:09:49 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id ECEA921F84FD for <tcmtf@ietf.org>; Mon,  8 Oct 2012 07:09:48 -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 q98E9bcN009025; Mon, 8 Oct 2012 16:09:43 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A249D8AD4B@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A249D8AD4B@EX10-MB2-MAD.hi.inet>
Date: Mon, 8 Oct 2012 16:09:41 +0200
Organization: Universidad de Zaragoza
Message-ID: <00bd01cda55e$92ae0780$b80a1680$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BE_01CDA56F.56394880"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHZ1736HN49j4JhWKyXddzZc4hwipeXBFAg
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: two kinds of services
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2012 14:09:55 -0000

This is a multipart message in MIME format.

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

Fernando,

=20

So you suggest we should distinguish between two different things (if I
understand well):

=20

1.- dynamically negotiating TCMTF options and/or parameters between
multiplexer and demultiplexer. Some examples:

=20

1.1. Negotiating the options (the different protocol stack options): We =
have
two mux/demux which want to establish a tunnel. If the first one says =
=93I
have implementations of ROHC and ECRTP, PPPMux, GRE=94 and the other one =
says
=93I implement ROHC, PPPMux, L2TP and GRE=94. The only option to use is
ROHC-PPPMux-GRE.

=20

1.2. Negotiating the parameters, if you have an RTT of 60ms, and you are
multiplexing VoIP, you can still add 40ms of multiplexing delay, since =
100ms
is not a problem for VoIP. But if you notice that in a certain moment =
the
RTT grows, you may have to reduce the multiplexing delay. It must be =
taken
into account that the higher the multiplexing delay, the higher the =
number
of packets you can merge, and the higher the bandwidth saving.

=20

2.- dynamically applying TCMTF: that would be a higher entity in charge =
of
deciding when and where, applying or not TCMTF, and what kind of TCMTF, =
and
what multiplexing period (which manly means added delay).

=20

=20

So I have four questions:

=20

Q1) Can TCMTF protocol stack be defined before defining 1.1.? I mean, we
standardize the stack and in a case you use ROHC-PPPMux-L2TP; in another
case you use ECRTP-PPPMux-GRE, etc. But two TCMTF entities would always =
talk
the same way.

=20

Q2) Is 1.1. =93the third draft=94 proposal?

=20

Q3) Is 1.2. a draft proposal? I don=92t think so. If the multiplexer =
modifies
the multiplexing period, the demux does not need to know it. It simply
demultiplexes the packets as they arrive. So no signaling is required: =
the
multiplexer estimates the RTT and modifies the multiplexing period.

=20

Q4) Is 2. a draft proposal? I don=92t clearly see it=85 let=92s keep on =
thinking.

=20

=20

Your =93network operator opinion=94 is interesting here (and also =
others=92
opinions, of course).

=20

Thanks in advance,

=20

Jose

=20

=20

De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]=20
Enviado el: viernes, 28 de septiembre de 2012 13:20
Para: jsaldana@unizar.es; tcmtf@ietf.org
Asunto: Re: [tcmtf] TCMTF: two kinds of services

=20

Hi Jose,

=20

You are talking about dynamically apply TCMTF, and yes, this is a very
interesting aspect. This is different from the third draft you proposed =
in
order to dynamically negotiate TCMTF parameters between multiplexer and
demultiplexer, that would be a higher entity in charge of decide when =
and
where or not to apply TCMTF, and what kind of TCMTF. As operator, we =
have a
lot of knowledge in those kind of policies. I have several colleagues =
that
can talk about that issue.

=20

Regards,

=20

Fernando Pascual Blanco

Telef=F3nica Global Resources

Network Automation and Dynamization

TECHNOLOGY PEOPLE GROUP

F +34913128779

M +34682005168

fpb@tid.es

=20

From: "jsaldana@unizar.es" <jsaldana@unizar.es>
Organization: Universidad de Zaragoza
Reply-To: "jsaldana@unizar.es" <jsaldana@unizar.es>
Date: viernes 28 de septiembre de 2012 11:17
To: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: [tcmtf] TCMTF: two kinds of services

=20

This is another thought to be discussed. We can have two different
situations for multiplexing flows:

=20

- delay-sensitive services (e.g., VoIP, online games). In this case, =
TCMTF
would add some delay, so it should only be used when bandwidth is scarce
(rush hours, new game release, etc.). If your network is working =
properly,
why do you need to save bandwidth and add a small delay to the clients? =
So
in rush hours there must be a counterpart in order to add some priority =
to
the tunneled packets. Otherwise you would penalize them: since they are
small and can be multiplexed, they are delayed.

=20

- services sending small packets but not delay-sensitive (e.g., =
whatsapp,
m2m packets being generated every second). In this case TCMTF saves
bandwidth while adding some delay, but it is not critical.

=20

=20

Jose=20

=20

=20

  _____ =20


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


------=_NextPart_000_00BE_01CDA56F.56394880
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)"><!--[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;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 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";}
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";}
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.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:Consolas;}
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.estilocorreo17
	{mso-style-name:estilocorreo17;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.textosinformatocar0
	{mso-style-name:textosinformatocar;
	font-family:"Calibri","sans-serif";}
span.EstiloCorreo23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.TextodegloboCar
	{mso-style-name:"Texto de globo Car";
	mso-style-priority:99;
	mso-style-link:"Texto de globo";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:544412656;
	mso-list-type:hybrid;
	mso-list-template-ids:1574712800 966415024 201981955 201981957 =
201981953 201981955 201981957 201981953 201981955 201981957;}
@list l0:level1
	{mso-level-number-format:alpha-lower;
	mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@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;}
@list l1
	{mso-list-id:1366326658;
	mso-list-template-ids:1451903152;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:18.0pt;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-text:"%1\.%2\.";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:54.0pt;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-text:"%1\.%2\.%3\.";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-36.0pt;}
@list l1:level4
	{mso-level-text:"%1\.%2\.%3\.%4\.";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-36.0pt;}
@list l1:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:198.0pt;
	text-indent:-54.0pt;}
@list l1:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:234.0pt;
	text-indent:-54.0pt;}
@list l1:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:288.0pt;
	text-indent:-72.0pt;}
@list l1:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:324.0pt;
	text-indent:-72.0pt;}
@list l1:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9\.";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:378.0pt;
	text-indent:-90.0pt;}
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 =
lang=3DEN-US style=3D'color:#1F497D'>Fernando,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>So you =
suggest we should distinguish between two different things (if I =
understand well):<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'>1.- =
dynamically negotiating TCMTF options and/or parameters between =
multiplexer and demultiplexer. Some examples:<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'margin-left:54.0pt;text-indent:-18.0pt;mso-list:l1 level2 =
lfo2'><![if !supportLists]><span lang=3DEN-US =
style=3D'color:#1F497D'><span style=3D'mso-list:Ignore'>1.1.<span =
style=3D'font:7.0pt "Times New Roman"'> =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'color:#1F497D'>Negotiating the options (the different protocol =
stack options): We have two mux/demux which want to establish a tunnel. =
If the first one says &#8220;I have implementations of ROHC and ECRTP, =
PPPMux, GRE&#8221; and the other one says &#8220;I implement ROHC, =
PPPMux, L2TP and GRE&#8221;. The only option to use is =
ROHC-PPPMux-GRE.<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:54.0pt'><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:54.0pt;text-indent:-18.0pt;mso-list:l1 level2 =
lfo2'><![if !supportLists]><span lang=3DEN-US =
style=3D'color:#1F497D'><span style=3D'mso-list:Ignore'>1.2.<span =
style=3D'font:7.0pt "Times New Roman"'> =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'color:#1F497D'>Negotiating the parameters, if you have an RTT =
of 60ms, and you are multiplexing VoIP, you can still add 40ms of =
multiplexing delay, since 100ms is not a problem for VoIP. But if you =
notice that in a certain moment the RTT grows, you may have to reduce =
the multiplexing delay. It must be taken into account that the higher =
the multiplexing delay, the higher the number of packets you can merge, =
and the higher the bandwidth saving.<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'>2.- =
dynamically applying TCMTF: that would be a higher entity in charge of =
deciding when and where, applying or not TCMTF, and what kind of TCMTF, =
and what multiplexing period (which manly means added =
delay).<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>So I have =
four questions:<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'>Q1) Can =
TCMTF protocol stack be defined before defining 1.1.? I mean, we =
standardize the stack and in a case you use ROHC-PPPMux-L2TP; in another =
case you use ECRTP-PPPMux-GRE, etc. But two TCMTF entities would always =
talk the same 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'>Q2) Is 1.1. =
&#8220;the third draft&#8221; proposal?<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'>Q3) Is 1.2. =
a draft proposal? I don&#8217;t think so. If the multiplexer modifies =
the multiplexing period, the demux does not need to know it. It simply =
demultiplexes the packets as they arrive. So no signaling is required: =
the multiplexer estimates the RTT and modifies the multiplexing =
period.<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'>Q4) Is 2. a =
draft proposal? I don&#8217;t clearly see it&#8230; let&#8217;s keep on =
thinking.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Your =
&#8220;network operator opinion&#8221; is interesting here (and also =
others&#8217; opinions, of course).<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 in =
advance,<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><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es] <br><b>Enviado el:</b> =
viernes, 28 de septiembre de 2012 13:20<br><b>Para:</b> =
jsaldana@unizar.es; tcmtf@ietf.org<br><b>Asunto:</b> Re: [tcmtf] TCMTF: =
two kinds of services<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><p =
class=3DMsoNormal><span style=3D'font-size:10.5pt;color:black'>Hi =
Jose,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>You are talking about dynamically =
apply TCMTF, and yes, this is a very interesting aspect. This is =
different from the third draft you proposed in order to dynamically =
negotiate TCMTF parameters between multiplexer and demultiplexer, that =
would be a higher entity in charge of decide when and where or not to =
apply TCMTF, and what kind of TCMTF. As operator, we have a lot of =
knowledge in those kind of policies. I have several colleagues that can =
talk about that issue.<o:p></o:p></span></p></div><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>Regards,<o:p></o:p></span></p></di=
v><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>Fernando Pascual =
Blanco<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>Telef=F3nica Global =
Resources<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>Network Automation and =
Dynamization<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>TECHNOLOGY PEOPLE =
GROUP<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>F =
+34913128779<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'>M =
+34682005168<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><a =
href=3D"mailto:fpb@tid.es">fpb@tid.es</a><o:p></o:p></span></p></div></di=
v></div></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'><p class=3DMsoNormal><b><span style=3D'color:black'>From: =
</span></b><span style=3D'color:black'>&quot;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt;<br><b>Organ=
ization: </b>Universidad de Zaragoza<br><b>Reply-To: </b>&quot;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt;<br><b>Date:=
 </b>viernes 28 de septiembre de 2012 11:17<br><b>To: </b>&quot;<a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>&gt;<br><b>Subject: =
</b>[tcmtf] TCMTF: two kinds of =
services<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><div><div><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>This is another thought to be discussed. We can =
have two different situations for multiplexing flows:</span><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>- =
delay-sensitive services (e.g., VoIP, online games). In this case, TCMTF =
would add some delay, so it should only be used when bandwidth is scarce =
(rush hours, new game release, etc.). If your network is working =
properly, why do you need to save bandwidth and add a small delay to the =
clients? So in rush hours there must be a counterpart in order to add =
some priority to the tunneled packets. Otherwise you would penalize =
them: since they are small and can be multiplexed, they are =
delayed.</span><span style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>- services =
sending small packets but not delay-sensitive (e.g., whatsapp, m2m =
packets being generated every second). In this case TCMTF saves =
bandwidth while adding some delay, but it is not critical.</span><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:black'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>J=
ose </span><span style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p></div></div></div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p><div =
class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span =
style=3D'font-size:10.5pt;color:black'><hr size=3D2 width=3D"100%" =
align=3Dcenter></span></div><p class=3DMsoNormal><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br=
>Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico en el enlace situado m=E1s abajo.<br>This message is =
intended exclusively for its addressee. </span><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'>We =
only send and receive email on the basis of the terms set out =
at:<br></span><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><a =
href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx"><span =
lang=3DEN-US>http://www.tid.es/ES/PAGINAS/disclaimer.aspx</span></a></spa=
n><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p></o:p></span></p></div></div>=
</body></html>
------=_NextPart_000_00BE_01CDA56F.56394880--


From fpb@tid.es  Tue Oct  9 00:17:55 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 27F1421F8514 for <tcmtf@ietfa.amsl.com>; Tue,  9 Oct 2012 00:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.077
X-Spam-Level: 
X-Spam-Status: No, score=-6.077 tagged_above=-999 required=5 tests=[AWL=0.522,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DzxARGHKNbE3 for <tcmtf@ietfa.amsl.com>; Tue,  9 Oct 2012 00:17:54 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 680A021F8505 for <tcmtf@ietf.org>; Tue,  9 Oct 2012 00:17:53 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MBM004086XLV5@tid.hi.inet> for tcmtf@ietf.org; Tue, 09 Oct 2012 09:17:51 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 77.2F.03050.F9FC3705; Tue, 09 Oct 2012 09:17:51 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MBM004646XRV5@tid.hi.inet> for tcmtf@ietf.org; Tue, 09 Oct 2012 09:17:51 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.209]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0318.001; Tue, 09 Oct 2012 09:17:51 +0200
Date: Tue, 09 Oct 2012 07:17:51 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <007301cda22b$95130ec0$bf392c40$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A249DA83B8@EX10-MB2-MAD.hi.inet>
Content-id: <E5B16FEB42123B4B99319A27ECECBB2A@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [tcmtf] Satellite-sensors scenario: new figure
Thread-index: Ac2iHgDnAaLmFjAERgGHYYWERGnbfgD0DugA
user-agent: Microsoft-MacOutlook/14.2.4.120824
X-AuditID: 0a5f4068-b7f176d000000bea-e6-5073cf9f1036
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrEKsWRmVeSWpSXmKPExsXCFe/ApTv/fHGAwbNDuha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRuPrwywFT6QrVu17yN7A+Fisi5GTQ0LARKJn9hoWCFtM4sK9 9WxdjFwcQgIbGSU6Fz5mhXB+Mkr03tnCCOHMZJTYv3M/WAuLgKrEhjdHWUFsNgEtidN3V4HF hQWsJTpuLAezOQUsJA69WcoOsUJB4s+5x2BxEYEAid0tB8BsXgFvib1vvzCC2MwCZhJr/yxj g4gLSvyYfI8FIq4j0fv9GzOELS7R3HoTKq4t8eTdBbAbGIFe+H5qDRPEfBuJzz2boHYZScx+ 9B+sV1RAT2LB7oPMEPcISCzZcx7KFpV4+fgf6wRG8VlIzpiF5IxZSM6YheSMWUjOWMDIuopR rDipKDM9oyQ3MTMn3cBQLyNTLzMvtWQTIyTCMnYwLt+pcohRgINRiYf3wbaiACHWxLLiytxD jJIcTEqivAznigOE+JLyUyozEosz4otKc1KLDzFKcDArifBeTwTK8aYkVlalFuXDpGQ4OJQk eP+fBUoJFqWmp1akZeYA0whMmomDE6SdB6j9FkgNb3FBYm5xZjpE/hSjpJQ473eQhABIIqM0 D673FaM40JHCvG9AsjzAhAfX9QpoIBPQwPtWhSADSxIRUlINjIJbaqem2q5vXJXPtnTW0iiJ fzazsz/z6n9t+ab/krPtPfOBpUmhFfZl/1/m18QL8O5cxLp3QQ+/3qPukGdP555K8GMRsjR7 L5XfPEOj5bjv7CU7zNPskxYXVLDsSEz6/iHu/pk8GYON4WbXVryc9CJtTlbdlg3Ksj3sctxb 0q92z62MeWsQqMRSnJFoqMVcVJwIADQVTP81AwAA
Subject: Re: [tcmtf] Satellite-sensors scenario: new figure
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 07:17:55 -0000

Hi Jose,

        Figures 1 and 2 make more sense for me. I would even include a 4th =
figure
with an only box (TCMTF, gateway and satellite antenna) per WSN.

Regards,

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




On 04/10/12 14:27, "Jose Saldana" <jsaldana@unizar.es> wrote:

>I have been thinking about the satellite-sensors scenario. Taking into
>account all your feedback, I think some statements are clear:
>
>       - If the satellite link is the only one, then there better compress=
ion
>schemes exist.
>       - TMCTF is only interesting if a number of hops is required, one of=
 them
>being the satellite one.
>       - Header compressing requires high processing capacity.
>       - Compression should be deployed where enough processing capacity i=
s
>available.
>
>Nother idea: although many sensor networks do not use IP, there are some
>of them using it. Nowadays, "internet of things" is a trending topic.
>"The basic idea of this concept is the pervasive presence around us of a
>variety of things or objects =AD such as Radio-Frequency IDentification
>(RFID) tags, sensors, actuators, mobile phones, etc. =AD which, through
>unique addressing schemes, are able to interact with each other and
>cooperate with their neighbors to reach common goals."
>(http://www.sciencedirect.com/science/article/pii/S1389128610001568).
>
>Another concept is "IP to the Field" paradigm where technologies applied
>in the Internet domain percolate right up to the field devices
>(http://www.kom.tu-darmstadt.de/research-results/projects/siemens-ip-to-th
>e-field/).
>
>
>
>Thinking about the IP sensors scenario, I have done three different
>figures:
>
>a)
>http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/satellite_scenario_
>multimux_v2.pdf
>
>       Each WSN multiplexes and compresses its packets. And finally the ga=
teway
>simply sends them. In this case, the processing capacity should be in the
>three multiplexers-compressors
>
>
>b)
>http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/satellite_scenario_
>v2.pdf
>
>       In this case, there is a single multiplexer-compressor, which is lo=
cated
>near the antenna, and does all the work for the three WSNs.
>
>
>c)
>http://diec.unizar.es/~jsaldana/personal/tcmtf_figures/satellite_scenario_
>multimux_separate_v2.pdf
>
>       A third option could include task distribution: each WSN compresses=
 its
>flows, and the shared gateway does multiplexing and tunneling. Perhaps
>the most CPU intensive task is header compression.
>
>
>If sensors are not IP, perhaps some of the scenarios would still be
>interesting: you may use IP for distinguishing between different sensor
>networks, or different server destinations.
>
>
>What do you think? Does this make sense? Which figure would be better?
>
>
>Thanks for your valuable feedback,
>
>Jose
>
>_______________________________________________
>tcmtf mailing list
>tcmtf@ietf.org
>https://www.ietf.org/mailman/listinfo/tcmtf


________________________________

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

From fpb@tid.es  Tue Oct  9 00:40:48 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 2F12821F8749 for <tcmtf@ietfa.amsl.com>; Tue,  9 Oct 2012 00:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.129
X-Spam-Level: 
X-Spam-Status: No, score=-6.129 tagged_above=-999 required=5 tests=[AWL=0.469,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zzX1OQOIbLq for <tcmtf@ietfa.amsl.com>; Tue,  9 Oct 2012 00:40:46 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1090D21F8588 for <tcmtf@ietf.org>; Tue,  9 Oct 2012 00:40:44 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MBM004ER7ZUV5@tid.hi.inet> for tcmtf@ietf.org; Tue, 09 Oct 2012 09:40:42 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 62.DF.03050.AF4D3705; Tue, 09 Oct 2012 09:40:42 +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 <0MBM004EN7ZUV5@tid.hi.inet> for tcmtf@ietf.org; Tue, 09 Oct 2012 09:40:42 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.209]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.001; Tue, 09 Oct 2012 09:40:42 +0200
Date: Tue, 09 Oct 2012 07:40:42 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <00bd01cda55e$92ae0780$b80a1680$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>
Message-id: <F5EDC35DF914C1428C28E149F10463A249DA84E3@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_iS7Lsyhr5uxeQn0pvEw8pQ)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] TCMTF: two kinds of services
Thread-index: Ac2dWc3roSS93utvTYC2TKQuzRqQgwAEW7WAAfijtIAAKOhjAA==
user-agent: Microsoft-MacOutlook/14.2.4.120824
X-AuditID: 0a5f4068-b7f176d000000bea-9a-5073d4fa6850
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrDKsWRmVeSWpSXmKPExsXCFe/ApfvrSnGAwayFBha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxseLnAVfXjNWbGg5wNrA2HuOsYuRk0NCwETifetsFghbTOLC vfVsXYxcHEICGxklFt8DKQJxfjJK3O5dDuVsYpRYvXIBWDuLgKrEpVPLwGw2AS2J03dXgY0S FjCUWLOlESzOKWAhsfzhd6h1ChJ/zj0GqxER0JW4svY7excjBwcz0Jx53xRBwrwC3hIrX/5h hbAFJX5MvgdWziyQK3Hy2DUmCFtcorn1JlicUUBW4t38+awQI40kni7/AmU7SbxaDbFWVEBP YsHug8wQJwhILNlzHsoWlXj5+B/rBEaxWUjWzUKybhaSdRC2gcT7c/OZIWxtiWULX0PZ+hIb v5xlhLDNJG683MOOrGYBI8cqRrHipKLM9IyS3MTMnHQDQ72MTL3MvNSSTYyQiMzYwbh8p8oh RgEORiUe3gfbigKEWBPLiitzDzFKcjApifKmXi4OEOJLyk+pzEgszogvKs1JLT7EKMHBrCTC ez0RKMebklhZlVqUD5OS4eBQkuCVAyYPIcGi1PTUirTMHGDagUkzcXCCtPMAte8AGc1bXJCY W5yZDpE/xajN0fRm7kNGjsaeRQ8ZhVjy8vNSpcR5JUHGCYCUZpTmwU17xSgOdLYwLztIlgeY ROHmvAJawQS04r5VIciKkkSElFQDo9n/HJv//zdbqz3teqNXV+F56/vcwuWbdBfPkXb7kOV+ 5OG6KXqCb78e9v7z2n1dyWWj74VzpCtX2V26r/vbtrLmom34hg1O61m/vpxS0ypSMMO4SLbK YSP7G744xleN2Xb9NVyCCjp6EtdnqM396xkxmfX2NuaDSRM5rdmec1xubFxbvkzdQomlOCPR UIu5qDgRAEYj1ZJfAwAA
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] TCMTF: two kinds of services
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 07:40:48 -0000

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

Hi Jose,

Yes, I see distinction between  1 and 2, and I though in something more sim=
ilar to 1.1 than to 1.2. Your questions:

Q1) Can TCMTF protocol stack be defined before defining 1.1.? I mean, we st=
andardize the stack and in a case you use ROHC-PPPMux-L2TP; in another case=
 you use ECRTP-PPPMux-GRE, etc. But two TCMTF entities would always talk th=
e same way.

Yes, of course. You can define a protocol negotiation before define the pos=
sibilities.

Q2) Is 1.1. =93the third draft=94 proposal?

Yes, I think that fits with the concept of "Dynamic Signaling draft".

Q3) Is 1.2. a draft proposal? I don=92t think so. If the multiplexer modifi=
es the multiplexing period, the demux does not need to know it. It simply d=
emultiplexes the packets as they arrive. So no signaling is required: the m=
ultiplexer estimates the RTT and modifies the multiplexing period.

I fully agree: added delay is something that demultiplexer does not need to=
 know.

Q4) Is 2. a draft proposal? I don=92t clearly see it=85 let=92s keep on thi=
nking.

I do not know, but I think it is something that should appear somewhere. Dy=
namic decisions over network is something that operators like to do: a cent=
ral policy manager deciding where and when to apply network optimizations (=
TCMTF) would be very valuable. That functionality could also be added to ex=
isting elements in network operator core networks that are currently making=
 similar things.

Regards,

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

From: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.es<m=
ailto:jsaldana@unizar.es>>
Organization: Universidad de Zaragoza
Reply-To: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.=
es<mailto:jsaldana@unizar.es>>
Date: lunes 8 de octubre de 2012 16:09
To: Fernando Pascual Blanco <fpb@tid.es<mailto:fpb@tid.es>>
Cc: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Subject: RE: [tcmtf] TCMTF: two kinds of services

Fernando,

So you suggest we should distinguish between two different things (if I und=
erstand well):

1.- dynamically negotiating TCMTF options and/or parameters between multipl=
exer and demultiplexer. Some examples:


1.1.Negotiating the options (the different protocol stack options): We have=
 two mux/demux which want to establish a tunnel. If the first one says =93I=
 have implementations of ROHC and ECRTP, PPPMux, GRE=94 and the other one s=
ays =93I implement ROHC, PPPMux, L2TP and GRE=94. The only option to use is=
 ROHC-PPPMux-GRE.



1.2.Negotiating the parameters, if you have an RTT of 60ms, and you are mul=
tiplexing VoIP, you can still add 40ms of multiplexing delay, since 100ms i=
s not a problem for VoIP. But if you notice that in a certain moment the RT=
T grows, you may have to reduce the multiplexing delay. It must be taken in=
to account that the higher the multiplexing delay, the higher the number of=
 packets you can merge, and the higher the bandwidth saving.

2.- dynamically applying TCMTF: that would be a higher entity in charge of =
deciding when and where, applying or not TCMTF, and what kind of TCMTF, and=
 what multiplexing period (which manly means added delay).


So I have four questions:

Q1) Can TCMTF protocol stack be defined before defining 1.1.? I mean, we st=
andardize the stack and in a case you use ROHC-PPPMux-L2TP; in another case=
 you use ECRTP-PPPMux-GRE, etc. But two TCMTF entities would always talk th=
e same way.

Q2) Is 1.1. =93the third draft=94 proposal?

Q3) Is 1.2. a draft proposal? I don=92t think so. If the multiplexer modifi=
es the multiplexing period, the demux does not need to know it. It simply d=
emultiplexes the packets as they arrive. So no signaling is required: the m=
ultiplexer estimates the RTT and modifies the multiplexing period.

Q4) Is 2. a draft proposal? I don=92t clearly see it=85 let=92s keep on thi=
nking.


Your =93network operator opinion=94 is interesting here (and also others=92=
 opinions, of course).

Thanks in advance,

Jose


De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
Enviado el: viernes, 28 de septiembre de 2012 13:20
Para: jsaldana@unizar.es<mailto:jsaldana@unizar.es>; tcmtf@ietf.org<mailto:=
tcmtf@ietf.org>
Asunto: Re: [tcmtf] TCMTF: two kinds of services

Hi Jose,

You are talking about dynamically apply TCMTF, and yes, this is a very inte=
resting aspect. This is different from the third draft you proposed in orde=
r to dynamically negotiate TCMTF parameters between multiplexer and demulti=
plexer, that would be a higher entity in charge of decide when and where or=
 not to apply TCMTF, and what kind of TCMTF. As operator, we have a lot of =
knowledge in those kind of policies. I have several colleagues that can tal=
k about that issue.

Regards,

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

From: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.es<m=
ailto:jsaldana@unizar.es>>
Organization: Universidad de Zaragoza
Reply-To: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.=
es<mailto:jsaldana@unizar.es>>
Date: viernes 28 de septiembre de 2012 11:17
To: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Subject: [tcmtf] TCMTF: two kinds of services


This is another thought to be discussed. We can have two different situatio=
ns for multiplexing flows:



- delay-sensitive services (e.g., VoIP, online games). In this case, TCMTF =
would add some delay, so it should only be used when bandwidth is scarce (r=
ush hours, new game release, etc.). If your network is working properly, wh=
y do you need to save bandwidth and add a small delay to the clients? So in=
 rush hours there must be a counterpart in order to add some priority to th=
e tunneled packets. Otherwise you would penalize them: since they are small=
 and can be multiplexed, they are delayed.



- services sending small packets but not delay-sensitive (e.g., whatsapp, m=
2m packets being generated every second). In this case TCMTF saves bandwidt=
h while adding some delay, but it is not critical.



Jose


________________________________

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

________________________________

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_iS7Lsyhr5uxeQn0pvEw8pQ)
Content-id: <548C3CFF65EF1A41827AC88F89646D71@hi.inet>
Content-type: text/html; charset=Windows-1252
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap:break-word; font-family:Calibri,sans-serif; font-s=
ize:14px">
<div>
<div>
<div style=3D"color:rgb(0,0,0)">Hi Jose,</div>
<div style=3D"color:rgb(0,0,0)"><br>
</div>
<div style=3D"color:rgb(0,0,0)"><span class=3D"Apple-tab-span" style=3D"whi=
te-space:pre"></span>Yes, I see distinction between &nbsp;1 and 2, and I th=
ough in something more similar to 1.1 than to 1.2. Your questions:</div>
<div style=3D"color:rgb(0,0,0)"><br>
</div>
<div>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">Q1) Can TCMTF protocol =
stack be defined before defining 1.1.? I mean, we standardize the stack and=
 in a case you use ROHC-PPPMux-L2TP; in another case you use ECRTP-PPPMux-G=
RE, etc. But two TCMTF entities would
 always talk the same way.</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)"><br>
</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<font class=3D"Apple-style-span" color=3D"#1f497d"><span class=3D"Apple-tab=
-span" style=3D"white-space:pre"></span></font><span class=3D"Apple-style-s=
pan" style=3D"font-size:14px">Yes, of course. You can define a protocol neg=
otiation before define the possibilities.&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">Q2) Is 1.1. =93the thir=
d draft=94 proposal?</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)"><br>
</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)"><span class=3D"Apple-ta=
b-span" style=3D"white-space:pre"></span></span><span class=3D"Apple-style-=
span" style=3D"font-size:14px">Yes, I think that fits with the concept of &=
quot;Dynamic Signaling draft&quot;.</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">Q3) Is 1.2. a draft pro=
posal? I don=92t think so. If the multiplexer modifies the multiplexing per=
iod, the demux does not need to know it. It simply demultiplexes the packet=
s as they arrive. So no signaling is required:
 the multiplexer estimates the RTT and modifies the multiplexing period.</s=
pan></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)"><br>
</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)"><span class=3D"Apple-ta=
b-span" style=3D"white-space:pre"></span></span><span class=3D"Apple-style-=
span" style=3D"font-size:14px">I fully agree: added delay is something that=
 demultiplexer does not need to know.</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">Q4) Is 2. a draft propo=
sal? I don=92t clearly see it=85 let=92s keep on thinking.</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)"><br>
</span></p>
<p class=3D"MsoNormal" style=3D"color:rgb(0,0,0); margin-top:0cm; margin-ri=
ght:0cm; margin-left:0cm; margin-bottom:0.0001pt; font-size:11pt; font-fami=
ly:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)"><span class=3D"Apple-ta=
b-span" style=3D"white-space:pre"></span></span><span class=3D"Apple-style-=
span" style=3D"font-size:14px">I do not know, but I think it is something t=
hat should appear somewhere. Dynamic decisions
 over network is something that operators like to do: a central policy mana=
ger deciding where and when to apply network optimizations (TCMTF) would be=
 very valuable. That functionality could also be added to existing elements=
 in network operator core networks
 that are currently making similar things.</span></p>
</div>
<div style=3D"color:rgb(0,0,0)">
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Fernando Pascual Blanco</div>
<div>Telef=F3nica Global Resources</div>
<div>Network Automation and Dynamization</div>
<div>TECHNOLOGY PEOPLE GROUP</div>
<div>F &#43;34913128779</div>
<div>M &#43;34682005168</div>
<div>fpb@tid.es</div>
</div>
</div>
</div>
<div style=3D"color:rgb(0,0,0)"><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color:rgb(0,0,0)">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; border-bottom:medium none; border-left:medium none; padding-bottom:0i=
n; padding-left:0in; padding-right:0in; border-top:#b5c4df 1pt solid; borde=
r-right:medium none; padding-top:3pt">
<span style=3D"font-weight:bold">From: </span>&quot;<a href=3D"mailto:jsald=
ana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsaldana@=
unizar.es">jsaldana@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Organization: </span>Universidad de Zarago=
za<br>
<span style=3D"font-weight:bold">Reply-To: </span>&quot;<a href=3D"mailto:j=
saldana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsald=
ana@unizar.es">jsaldana@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>lunes 8 de octubre de 2012 16=
:09<br>
<span style=3D"font-weight:bold">To: </span>Fernando Pascual Blanco &lt;<a =
href=3D"mailto:fpb@tid.es">fpb@tid.es</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:tcmtf@i=
etf.org">tcmtf@ietf.org</a>&quot; &lt;<a href=3D"mailto:tcmtf@ietf.org">tcm=
tf@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: [tcmtf] TCMTF: two kin=
ds of services<br>
</div>
<div><br>
</div>
<div><style>
<!--
@font-face
	{font-family:Wingdings}
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Tahoma}
@font-face
	{font-family:Consolas}
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif"}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{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.apple-tab-span
	{}
span.TextosinformatoCar
	{font-family:Consolas}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{margin-right:0cm;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Calibri","sans-serif"}
span.estilocorreo17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.textosinformatocar0
	{font-family:"Calibri","sans-serif"}
span.EstiloCorreo23
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
span.TextodegloboCar
	{font-family:"Tahoma","sans-serif"}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:70.85pt 3.0cm 70.85pt 3.0cm}
div.WordSection1
	{}
ol
	{margin-bottom:0cm}
ul
	{margin-bottom:0cm}
-->
</style>
<div lang=3D"ES">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Fernand=
o,</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">So you =
suggest we should distinguish between two different things (if I understand=
 well):</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">1.- dyn=
amically negotiating TCMTF options and/or parameters between multiplexer an=
d demultiplexer. Some examples:</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:54.0pt; text-indent:-18.=
0pt"><span lang=3D"EN-US" style=3D"color:#1F497D"><span style=3D"">1.1.<spa=
n style=3D"font:7.0pt &quot;Times New Roman&quot;"></span></span></span><sp=
an lang=3D"EN-US" style=3D"color:#1F497D">Negotiating the
 options (the different protocol stack options): We have two mux/demux whic=
h want to establish a tunnel. If the first one says =93I have implementatio=
ns of ROHC and ECRTP, PPPMux, GRE=94 and the other one says =93I implement =
ROHC, PPPMux, L2TP and GRE=94. The only
 option to use is ROHC-PPPMux-GRE.</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:54.0pt"><span lang=3D"EN=
-US" style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:54.0pt; text-indent:-18.=
0pt"><span lang=3D"EN-US" style=3D"color:#1F497D"><span style=3D"">1.2.<spa=
n style=3D"font:7.0pt &quot;Times New Roman&quot;"></span></span></span><sp=
an lang=3D"EN-US" style=3D"color:#1F497D">Negotiating the
 parameters, if you have an RTT of 60ms, and you are multiplexing VoIP, you=
 can still add 40ms of multiplexing delay, since 100ms is not a problem for=
 VoIP. But if you notice that in a certain moment the RTT grows, you may ha=
ve to reduce the multiplexing delay.
 It must be taken into account that the higher the multiplexing delay, the =
higher the number of packets you can merge, and the higher the bandwidth sa=
ving.</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">2.- dyn=
amically applying TCMTF: that would be a higher entity in charge of decidin=
g when and where, applying or not TCMTF, and what kind of TCMTF, and what m=
ultiplexing period (which manly means
 added delay).</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"><span lang=3D"EN-US" style=3D"color:#1F497D">So I ha=
ve four questions:</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">Q1) Can=
 TCMTF protocol stack be defined before defining 1.1.? I mean, we standardi=
ze the stack and in a case you use ROHC-PPPMux-L2TP; in another case you us=
e ECRTP-PPPMux-GRE, etc. But two TCMTF
 entities would always talk the same 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">Q2) Is =
1.1. =93the third draft=94 proposal?</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">Q3) Is =
1.2. a draft proposal? I don=92t think so. If the multiplexer modifies the =
multiplexing period, the demux does not need to know it. It simply demultip=
lexes the packets as they arrive. So no
 signaling is required: the multiplexer estimates the RTT and modifies the =
multiplexing period.</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">Q4) Is =
2. a draft proposal? I don=92t clearly see it=85 let=92s keep on thinking.<=
/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"><span lang=3D"EN-US" style=3D"color:#1F497D">Your =
=93network operator opinion=94 is interesting here (and also others=92 opin=
ions, of course).</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">Thanks =
in advance,</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">Jose</s=
pan></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>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0cm 0cm 0c=
m 4.0pt">
<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:10pt; font-family:Tahoma=
,sans-serif">De:</span></b><span style=3D"font-size:10pt; font-family:Tahom=
a,sans-serif"> FERNANDO PASCUAL BLANCO [<a href=3D"mailto:fpb@tid.es">mailt=
o:fpb@tid.es</a>]
<br>
<b>Enviado el:</b> viernes, 28 de septiembre de 2012 13:20<br>
<b>Para:</b> <a href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>; =
<a href=3D"mailto:tcmtf@ietf.org">
tcmtf@ietf.org</a><br>
<b>Asunto:</b> Re: [tcmtf] TCMTF: two kinds of services</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">Hi Jos=
e,</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">&nbsp;=
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">You ar=
e talking about dynamically apply TCMTF, and yes, this is a very interestin=
g aspect. This is different from the third draft you proposed in order to d=
ynamically negotiate TCMTF parameters
 between multiplexer and demultiplexer, that would be a higher entity in ch=
arge of decide when and where or not to apply TCMTF, and what kind of TCMTF=
. As operator, we have a lot of knowledge in those kind of policies. I have=
 several colleagues that can talk
 about that issue.</span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">&nbsp;=
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">Regard=
s,</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">&nbsp;=
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">Fernan=
do Pascual Blanco</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">Telef=
=F3nica Global Resources</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">Networ=
k Automation and Dynamization</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">TECHNO=
LOGY PEOPLE GROUP</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">F &#43=
;34913128779</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">M &#43=
;34682005168</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black"><a hre=
f=3D"mailto:fpb@tid.es">fpb@tid.es</a></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">&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"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;<a href=3D"mailto:jsaldana@unizar.es">jsaldan=
a@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsaldana@unizar.es">jsaldana@un=
izar.es</a>&gt;<br>
<b>Organization: </b>Universidad de Zaragoza<br>
<b>Reply-To: </b>&quot;<a href=3D"mailto:jsaldana@unizar.es">jsaldana@uniza=
r.es</a>&quot; &lt;<a href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es=
</a>&gt;<br>
<b>Date: </b>viernes 28 de septiembre de 2012 11:17<br>
<b>To: </b>&quot;<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>&gt;<br>
<b>Subject: </b>[tcmtf] TCMTF: two kinds of services</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">&nbsp;=
</span></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:black">This i=
s another thought to be discussed. We can have two different situations for=
 multiplexing flows:</span><span style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:black">&nbsp;=
</span><span style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:black">- dela=
y-sensitive services (e.g., VoIP, online games). In this case, TCMTF would =
add some delay, so it should only be used when bandwidth is scarce (rush ho=
urs, new game release, etc.). If your
 network is working properly, why do you need to save bandwidth and add a s=
mall delay to the clients? So in rush hours there must be a counterpart in =
order to add some priority to the tunneled packets. Otherwise you would pen=
alize them: since they are small
 and can be multiplexed, they are delayed.</span><span style=3D"color:black=
"></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:black">&nbsp;=
</span><span style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:black">- serv=
ices sending small packets but not delay-sensitive (e.g., whatsapp, m2m pac=
kets being generated every second). In this case TCMTF saves bandwidth whil=
e adding some delay, but it is not critical.</span><span style=3D"color:bla=
ck"></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:black">&nbsp;=
</span><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt; color:=
black; font-family:Arial,sans-serif">Jose
</span><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan><span style=3D"color:black"></span></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt; color:black">&nbsp;=
</span></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-size:10.5pt; color:black">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt; color:gray; font-fam=
ily:Arial,sans-serif"><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. </span><span lang=
=3D"EN-US" style=3D"font-size:7.5pt; color:gray; font-family:Arial,sans-ser=
if">We only send and receive email on the basis of the terms set out at:<br=
>
</span><span style=3D"font-size:7.5pt; font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;; color:gray"><a href=3D"http://www.tid.es/ES/PAGINAS/discl=
aimer.aspx"><span lang=3D"EN-US">http://www.tid.es/ES/PAGINAS/disclaimer.as=
px</span></a></span><span lang=3D"EN-US" style=3D"font-size:10.5pt; color:b=
lack"></span></p>
</div>
</div>
</div>
</div>
</span><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_iS7Lsyhr5uxeQn0pvEw8pQ)--

From mirja.kuehlewind@ikr.uni-stuttgart.de  Tue Oct  9 05:24:21 2012
Return-Path: <mirja.kuehlewind@ikr.uni-stuttgart.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 85AD91F0C59 for <tcmtf@ietfa.amsl.com>; Tue,  9 Oct 2012 05:24:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xxmByOOUxnqb for <tcmtf@ietfa.amsl.com>; Tue,  9 Oct 2012 05:24:20 -0700 (PDT)
Received: from mailsrv.ikr.uni-stuttgart.de (mailsrv.ikr.uni-stuttgart.de [129.69.170.2]) by ietfa.amsl.com (Postfix) with ESMTP id 7645F1F0C5F for <tcmtf@ietf.org>; Tue,  9 Oct 2012 05:24:20 -0700 (PDT)
Received: from netsrv1.ikr.uni-stuttgart.de (netsrv1-c [10.11.12.12]) by mailsrv.ikr.uni-stuttgart.de (Postfix) with ESMTP id 110F5633B1; Tue,  9 Oct 2012 14:24:18 +0200 (CEST)
Received: from vpn-2-cl177 (vpn-2-cl177 [10.41.21.177]) by netsrv1.ikr.uni-stuttgart.de (Postfix) with ESMTP id E624B59A8A; Tue,  9 Oct 2012 14:24:17 +0200 (CEST)
From: Mirja Kuehlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
Organization: University of Stuttgart (Germany), IKR
To: tcmtf@ietf.org, jsaldana@unizar.es
Date: Tue, 9 Oct 2012 14:24:17 +0200
User-Agent: KMail/1.9.10 (enterprise35 0.20101217.1207316)
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A249D8AD4B@EX10-MB2-MAD.hi.inet> <00bd01cda55e$92ae0780$b80a1680$@unizar.es>
In-Reply-To: <00bd01cda55e$92ae0780$b80a1680$@unizar.es>
X-KMail-QuotePrefix: > 
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de>
Cc: 'FERNANDO PASCUAL BLANCO' <fpb@tid.es>
Subject: Re: [tcmtf] TCMTF: two kinds of services
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 12:24:21 -0000

Hi Jose,

quick question:

> Q3) Is 1.2. a draft proposal? I don=92t think so. If the multiplexer modi=
fies
> the multiplexing period, the demux does not need to know it. It simply
> demultiplexes the packets as they arrive. So no signaling is required: the
> multiplexer estimates the RTT and modifies the multiplexing period.
>
How does the multiplexer know the RTT?

Mirja



>
> Q4) Is 2. a draft proposal? I don=92t clearly see it=85 let=92s keep on t=
hinking.
>
>
>
>
>
> Your =93network operator opinion=94 is interesting here (and also others=
=92
> opinions, of course).
>
>
>
> Thanks in advance,
>
>
>
> Jose
>
>
>
>
>
> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> Enviado el: viernes, 28 de septiembre de 2012 13:20
> Para: jsaldana@unizar.es; tcmtf@ietf.org
> Asunto: Re: [tcmtf] TCMTF: two kinds of services
>
>
>
> Hi Jose,
>
>
>
> You are talking about dynamically apply TCMTF, and yes, this is a very
> interesting aspect. This is different from the third draft you proposed in
> order to dynamically negotiate TCMTF parameters between multiplexer and
> demultiplexer, that would be a higher entity in charge of decide when and
> where or not to apply TCMTF, and what kind of TCMTF. As operator, we have=
 a
> lot of knowledge in those kind of policies. I have several colleagues that
> can talk about that issue.
>
>
>
> Regards,
>
>
>
> Fernando Pascual Blanco
>
> Telef=F3nica Global Resources
>
> Network Automation and Dynamization
>
> TECHNOLOGY PEOPLE GROUP
>
> F +34913128779
>
> M +34682005168
>
> fpb@tid.es
>
>
>
> From: "jsaldana@unizar.es" <jsaldana@unizar.es>
> Organization: Universidad de Zaragoza
> Reply-To: "jsaldana@unizar.es" <jsaldana@unizar.es>
> Date: viernes 28 de septiembre de 2012 11:17
> To: "tcmtf@ietf.org" <tcmtf@ietf.org>
> Subject: [tcmtf] TCMTF: two kinds of services
>
>
>
> This is another thought to be discussed. We can have two different
> situations for multiplexing flows:
>
>
>
> - delay-sensitive services (e.g., VoIP, online games). In this case, TCMTF
> would add some delay, so it should only be used when bandwidth is scarce
> (rush hours, new game release, etc.). If your network is working properly,
> why do you need to save bandwidth and add a small delay to the clients? So
> in rush hours there must be a counterpart in order to add some priority to
> the tunneled packets. Otherwise you would penalize them: since they are
> small and can be multiplexed, they are delayed.
>
>
>
> - services sending small packets but not delay-sensitive (e.g., whatsapp,
> m2m packets being generated every second). In this case TCMTF saves
> bandwidth while adding some delay, but it is not critical.
>
>
>
>
>
> Jose
>
>
>
>
>
>   _____
>
>
> 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>
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx



=2D-=20
=2D------------------------------------------------------------------
Dipl.-Ing. Mirja K=FChlewind
Institute of Communication Networks and Computer Engineering (IKR)
University of Stuttgart, Germany
Pfaffenwaldring 47, D-70569 Stuttgart

tel: +49(0)711/685-67973
email: mirja.kuehlewind@ikr.uni-stuttgart.de
web: www.ikr.uni-stuttgart.de
=2D------------------------------------------------------------------

From jsaldana@unizar.es  Tue Oct  9 07:40:04 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 923E321F87DA for <tcmtf@ietfa.amsl.com>; Tue,  9 Oct 2012 07:40:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.126
X-Spam-Level: 
X-Spam-Status: No, score=-6.126 tagged_above=-999 required=5 tests=[AWL=0.473,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wM+M0Sby1yD1 for <tcmtf@ietfa.amsl.com>; Tue,  9 Oct 2012 07:40:03 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id CE0B221F87CB for <tcmtf@ietf.org>; Tue,  9 Oct 2012 07:40:02 -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 q99Edvm9000598; Tue, 9 Oct 2012 16:39:57 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Mirja Kuehlewind'" <mirja.kuehlewind@ikr.uni-stuttgart.de>
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A249D8AD4B@EX10-MB2-MAD.hi.inet> <00bd01cda55e$92ae0780$b80a1680$@unizar.es> <201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de>
In-Reply-To: <201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de>
Date: Tue, 9 Oct 2012 16:40:01 +0200
Organization: Universidad de Zaragoza
Message-ID: <002001cda62b$f6e63920$e4b2ab60$@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: AQINPjcn7rEFviyXS5rdNqTB9c1OEQHZ1736AabQPgUCcgz+bJcCQv4Q
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: two kinds of services
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 14:40:04 -0000

Well, it was part of the example. However, your question is interesting,
since we are talking about delay-sensitive services: if you build a =
tunnel
to save bandwidth and, at the same time, you add an unacceptable delay, =
it
makes no sense.

I don't know if you want to suggest the possibility of developing a =
method
for estimating RTT. But do you think it is necessary to develop it? I am
sure something already exists. In fact, online games use "ping" as delay
estimation. Do you know if a standard method for estimating RTT exists?

Thanks, and let us keep on thinking,

Jose

> -----Mensaje original-----
> De: Mirja Kuehlewind [mailto:mirja.kuehlewind@ikr.uni-stuttgart.de]
> Enviado el: martes, 09 de octubre de 2012 14:24
> Para: tcmtf@ietf.org; jsaldana@unizar.es
> CC: 'FERNANDO PASCUAL BLANCO'
> Asunto: Re: [tcmtf] TCMTF: two kinds of services
>=20
> Hi Jose,
>=20
> quick question:
>=20
> > Q3) Is 1.2. a draft proposal? I don=92t think so. If the multiplexer
> > modifies the multiplexing period, the demux does not need to know =
it.
> > It simply demultiplexes the packets as they arrive. So no signaling =
is
> > required: the multiplexer estimates the RTT and modifies the
> multiplexing period.
> >
> How does the multiplexer know the RTT?
>=20
> Mirja
>=20
>=20
>=20
> >
> > Q4) Is 2. a draft proposal? I don=92t clearly see it=85 let=92s keep =
on
thinking.
> >
> >
> >
> >
> >
> > Your =93network operator opinion=94 is interesting here (and also =
others=92
> > opinions, of course).
> >
> >
> >
> > Thanks in advance,
> >
> >
> >
> > Jose
> >
> >
> >
> >
> >
> > De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es] Enviado el: viernes,
> > 28 de septiembre de 2012 13:20
> > Para: jsaldana@unizar.es; tcmtf@ietf.org
> > Asunto: Re: [tcmtf] TCMTF: two kinds of services
> >
> >
> >
> > Hi Jose,
> >
> >
> >
> > You are talking about dynamically apply TCMTF, and yes, this is a =
very
> > interesting aspect. This is different from the third draft you
> > proposed in order to dynamically negotiate TCMTF parameters between
> > multiplexer and demultiplexer, that would be a higher entity in =
charge
> > of decide when and where or not to apply TCMTF, and what kind of
> > TCMTF. As operator, we have a lot of knowledge in those kind of
> > policies. I have several colleagues that can talk about that issue.
> >
> >
> >
> > Regards,
> >
> >
> >
> > Fernando Pascual Blanco
> >
> > Telef=F3nica Global Resources
> >
> > Network Automation and Dynamization
> >
> > TECHNOLOGY PEOPLE GROUP
> >
> > F +34913128779
> >
> > M +34682005168
> >
> > fpb@tid.es
> >
> >
> >
> > From: "jsaldana@unizar.es" <jsaldana@unizar.es>
> > Organization: Universidad de Zaragoza
> > Reply-To: "jsaldana@unizar.es" <jsaldana@unizar.es>
> > Date: viernes 28 de septiembre de 2012 11:17
> > To: "tcmtf@ietf.org" <tcmtf@ietf.org>
> > Subject: [tcmtf] TCMTF: two kinds of services
> >
> >
> >
> > This is another thought to be discussed. We can have two different
> > situations for multiplexing flows:
> >
> >
> >
> > - delay-sensitive services (e.g., VoIP, online games). In this case,
> > TCMTF would add some delay, so it should only be used when bandwidth
> > is scarce (rush hours, new game release, etc.). If your network is
> > working properly, why do you need to save bandwidth and add a small
> > delay to the clients? So in rush hours there must be a counterpart =
in
> > order to add some priority to the tunneled packets. Otherwise you
> > would penalize them: since they are small and can be multiplexed, =
they
> are delayed.
> >
> >
> >
> > - services sending small packets but not delay-sensitive (e.g.,
> > whatsapp, m2m packets being generated every second). In this case
> > TCMTF saves bandwidth while adding some delay, but it is not =
critical.
> >
> >
> >
> >
> >
> > Jose
> >
> >
> >
> >
> >
> >   _____
> >
> >
> > 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>
> > http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>=20
>=20
>=20
> --
> -------------------------------------------------------------------
> Dipl.-Ing. Mirja K=FChlewind
> Institute of Communication Networks and Computer Engineering (IKR)
> University of Stuttgart, Germany Pfaffenwaldring 47, D-70569 Stuttgart
>=20
> tel: +49(0)711/685-67973
> email: mirja.kuehlewind@ikr.uni-stuttgart.de
> web: www.ikr.uni-stuttgart.de
> -------------------------------------------------------------------


From mirja.kuehlewind@ikr.uni-stuttgart.de  Tue Oct  9 09:02:07 2012
Return-Path: <mirja.kuehlewind@ikr.uni-stuttgart.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 89CCC1F0C94 for <tcmtf@ietfa.amsl.com>; Tue,  9 Oct 2012 09:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cngpPlMPf9JM for <tcmtf@ietfa.amsl.com>; Tue,  9 Oct 2012 09:02:06 -0700 (PDT)
Received: from mailsrv.ikr.uni-stuttgart.de (mailsrv.ikr.uni-stuttgart.de [129.69.170.2]) by ietfa.amsl.com (Postfix) with ESMTP id 680AF11E80C5 for <tcmtf@ietf.org>; Tue,  9 Oct 2012 09:02:06 -0700 (PDT)
Received: from netsrv1.ikr.uni-stuttgart.de (netsrv1-c [10.11.12.12]) by mailsrv.ikr.uni-stuttgart.de (Postfix) with ESMTP id 770EE633B1; Tue,  9 Oct 2012 18:02:05 +0200 (CEST)
Received: from vpn-2-cl177 (vpn-2-cl177 [10.41.21.177]) by netsrv1.ikr.uni-stuttgart.de (Postfix) with ESMTP id 506B459A8A; Tue,  9 Oct 2012 18:02:05 +0200 (CEST)
From: Mirja Kuehlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
Organization: University of Stuttgart (Germany), IKR
To: tcmtf@ietf.org, jsaldana@unizar.es
Date: Tue, 9 Oct 2012 18:02:04 +0200
User-Agent: KMail/1.9.10 (enterprise35 0.20101217.1207316)
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es> <201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de> <002001cda62b$f6e63920$e4b2ab60$@unizar.es>
In-Reply-To: <002001cda62b$f6e63920$e4b2ab60$@unizar.es>
X-KMail-QuotePrefix: > 
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de>
Subject: Re: [tcmtf] TCMTF: two kinds of services
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 16:02:07 -0000

Hi Jose,

usually a box somewhere in the network does not know the e2e delay of a sin=
gle=20
transmission. The endsystem might. Moreover, RTT might change during a=20
transmission. Thus making a decision based on RTT somewhere in the network=
=20
isn't that easy.=20

I guess, at least some kind of additional signaling is required which requi=
res=20
further cooperation between the parties or introduces further contrains e.g=
=2E=20
limitation to TCP flows that uses the timestamp option and thus already=20
provide RTT info, but the TCP syntax needs to be interpreted.

I'm following your discussion but I have the feeling that the whole thing i=
s=20
getting more and more complex as this issue about RTT. I guess for a first=
=20
meeting it would make more sense to focus on the more simpler cases first.=
=20
Are you currently writting a charter text?

Mirja


On Tuesday 09 October 2012 16:40:01 Jose Saldana wrote:
> Well, it was part of the example. However, your question is interesting,
> since we are talking about delay-sensitive services: if you build a tunnel
> to save bandwidth and, at the same time, you add an unacceptable delay, it
> makes no sense.
>
> I don't know if you want to suggest the possibility of developing a method
> for estimating RTT. But do you think it is necessary to develop it? I am
> sure something already exists. In fact, online games use "ping" as delay
> estimation. Do you know if a standard method for estimating RTT exists?
>
> Thanks, and let us keep on thinking,
>
> Jose
>
> > -----Mensaje original-----
> > De: Mirja Kuehlewind [mailto:mirja.kuehlewind@ikr.uni-stuttgart.de]
> > Enviado el: martes, 09 de octubre de 2012 14:24
> > Para: tcmtf@ietf.org; jsaldana@unizar.es
> > CC: 'FERNANDO PASCUAL BLANCO'
> > Asunto: Re: [tcmtf] TCMTF: two kinds of services
> >
> > Hi Jose,
> >
> > quick question:
> > > Q3) Is 1.2. a draft proposal? I don=92t think so. If the multiplexer
> > > modifies the multiplexing period, the demux does not need to know it.
> > > It simply demultiplexes the packets as they arrive. So no signaling is
> > > required: the multiplexer estimates the RTT and modifies the
> >
> > multiplexing period.
> >
> > How does the multiplexer know the RTT?
> >
> > Mirja
> >
> > > Q4) Is 2. a draft proposal? I don=92t clearly see it=85 let=92s keep =
on
>
> thinking.
>
> > > Your =93network operator opinion=94 is interesting here (and also oth=
ers=92
> > > opinions, of course).
> > >
> > >
> > >
> > > Thanks in advance,
> > >
> > >
> > >
> > > Jose
> > >
> > >
> > >
> > >
> > >
> > > De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es] Enviado el: viernes,
> > > 28 de septiembre de 2012 13:20
> > > Para: jsaldana@unizar.es; tcmtf@ietf.org
> > > Asunto: Re: [tcmtf] TCMTF: two kinds of services
> > >
> > >
> > >
> > > Hi Jose,
> > >
> > >
> > >
> > > You are talking about dynamically apply TCMTF, and yes, this is a very
> > > interesting aspect. This is different from the third draft you
> > > proposed in order to dynamically negotiate TCMTF parameters between
> > > multiplexer and demultiplexer, that would be a higher entity in charge
> > > of decide when and where or not to apply TCMTF, and what kind of
> > > TCMTF. As operator, we have a lot of knowledge in those kind of
> > > policies. I have several colleagues that can talk about that issue.
> > >
> > >
> > >
> > > Regards,
> > >
> > >
> > >
> > > Fernando Pascual Blanco
> > >
> > > Telef=F3nica Global Resources
> > >
> > > Network Automation and Dynamization
> > >
> > > TECHNOLOGY PEOPLE GROUP
> > >
> > > F +34913128779
> > >
> > > M +34682005168
> > >
> > > fpb@tid.es
> > >
> > >
> > >
> > > From: "jsaldana@unizar.es" <jsaldana@unizar.es>
> > > Organization: Universidad de Zaragoza
> > > Reply-To: "jsaldana@unizar.es" <jsaldana@unizar.es>
> > > Date: viernes 28 de septiembre de 2012 11:17
> > > To: "tcmtf@ietf.org" <tcmtf@ietf.org>
> > > Subject: [tcmtf] TCMTF: two kinds of services
> > >
> > >
> > >
> > > This is another thought to be discussed. We can have two different
> > > situations for multiplexing flows:
> > >
> > >
> > >
> > > - delay-sensitive services (e.g., VoIP, online games). In this case,
> > > TCMTF would add some delay, so it should only be used when bandwidth
> > > is scarce (rush hours, new game release, etc.). If your network is
> > > working properly, why do you need to save bandwidth and add a small
> > > delay to the clients? So in rush hours there must be a counterpart in
> > > order to add some priority to the tunneled packets. Otherwise you
> > > would penalize them: since they are small and can be multiplexed, they
> >
> > are delayed.
> >
> > > - services sending small packets but not delay-sensitive (e.g.,
> > > whatsapp, m2m packets being generated every second). In this case
> > > TCMTF saves bandwidth while adding some delay, but it is not critical.
> > >
> > >
> > >
> > >
> > >
> > > Jose
> > >
> > >
> > >
> > >
> > >
> > >   _____
> > >
> > >
> > > Este mensaje se dirige exclusivamente a su destinatario. Puede
> > > consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo elect=
r=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>
> > > http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >
> > --
> > -------------------------------------------------------------------
> > Dipl.-Ing. Mirja K=FChlewind
> > Institute of Communication Networks and Computer Engineering (IKR)
> > University of Stuttgart, Germany Pfaffenwaldring 47, D-70569 Stuttgart
> >
> > tel: +49(0)711/685-67973
> > email: mirja.kuehlewind@ikr.uni-stuttgart.de
> > web: www.ikr.uni-stuttgart.de
> > -------------------------------------------------------------------
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf



=2D-=20
=2D------------------------------------------------------------------
Dipl.-Ing. Mirja K=FChlewind
Institute of Communication Networks and Computer Engineering (IKR)
University of Stuttgart, Germany
Pfaffenwaldring 47, D-70569 Stuttgart

tel: +49(0)711/685-67973
email: mirja.kuehlewind@ikr.uni-stuttgart.de
web: www.ikr.uni-stuttgart.de
=2D------------------------------------------------------------------

From jsaldana@unizar.es  Tue Oct  9 09:28:00 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 A0BBF11E8137 for <tcmtf@ietfa.amsl.com>; Tue,  9 Oct 2012 09:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.152
X-Spam-Level: 
X-Spam-Status: No, score=-6.152 tagged_above=-999 required=5 tests=[AWL=0.447,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nuyTHG-rfNxe for <tcmtf@ietfa.amsl.com>; Tue,  9 Oct 2012 09:27:59 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 3C68611E8136 for <tcmtf@ietf.org>; Tue,  9 Oct 2012 09:27:58 -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 q99GRoUV008382; Tue, 9 Oct 2012 18:27:50 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Mirja Kuehlewind'" <mirja.kuehlewind@ikr.uni-stuttgart.de>, <tcmtf@ietf.org>
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es> <201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de> <002001cda62b$f6e63920$e4b2ab60$@unizar.es> <201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de>
In-Reply-To: <201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de>
Date: Tue, 9 Oct 2012 18:27:57 +0200
Organization: Universidad de Zaragoza
Message-ID: <000001cda63b$0b3fe330$21bfa990$@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: AQINPjcn7rEFviyXS5rdNqTB9c1OEQJyDP5sAiUuOIoBpXi1CpcAD9Lw
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] TCMTF: two kinds of services
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 16:28:00 -0000

Mirja,

Yes, in fact my plan is sending the charter (first version) tomorrow, =
after
polishing it a bit.

There are two options:

a) Only considering the main draft (protocol stack) and the =
"informational"
draft with recommendations of maximum delays for each service. A final
comment saying "if further needs were identified, the WG would be
rechartered".

b) Considering from the beginning the other options we have talked =
about.
The question is that some of them are not clear by now.

I think the opinions of the Area Directors will be very important here: =
if
they want to start the WG soon, I think option a) would be better =
(according
to my short experience).

But first, we should hear the opinion of everyone in the list. Thanks,

Jose

> -----Mensaje original-----
> De: Mirja Kuehlewind [mailto:mirja.kuehlewind@ikr.uni-stuttgart.de]
> Enviado el: martes, 09 de octubre de 2012 18:02
> Para: tcmtf@ietf.org; jsaldana@unizar.es
> Asunto: Re: [tcmtf] TCMTF: two kinds of services
>=20
> Hi Jose,
>=20
> usually a box somewhere in the network does not know the e2e delay of =
a
> single transmission. The endsystem might. Moreover, RTT might change
> during a transmission. Thus making a decision based on RTT somewhere =
in
> the network isn't that easy.
>=20
> I guess, at least some kind of additional signaling is required which
requires
> further cooperation between the parties or introduces further =
contrains
e.g.
> limitation to TCP flows that uses the timestamp option and thus =
already
> provide RTT info, but the TCP syntax needs to be interpreted.
>=20
> I'm following your discussion but I have the feeling that the whole =
thing
is
> getting more and more complex as this issue about RTT. I guess for a =
first
> meeting it would make more sense to focus on the more simpler cases =
first.
> Are you currently writting a charter text?
>=20
> Mirja
>=20
>=20
> On Tuesday 09 October 2012 16:40:01 Jose Saldana wrote:
> > Well, it was part of the example. However, your question is
> > interesting, since we are talking about delay-sensitive services: if
> > you build a tunnel to save bandwidth and, at the same time, you add =
an
> > unacceptable delay, it makes no sense.
> >
> > I don't know if you want to suggest the possibility of developing a
> > method for estimating RTT. But do you think it is necessary to =
develop
> > it? I am sure something already exists. In fact, online games use
> > "ping" as delay estimation. Do you know if a standard method for
> estimating RTT exists?
> >
> > Thanks, and let us keep on thinking,
> >
> > Jose
> >
> > > -----Mensaje original-----
> > > De: Mirja Kuehlewind =
[mailto:mirja.kuehlewind@ikr.uni-stuttgart.de]
> > > Enviado el: martes, 09 de octubre de 2012 14:24
> > > Para: tcmtf@ietf.org; jsaldana@unizar.es
> > > CC: 'FERNANDO PASCUAL BLANCO'
> > > Asunto: Re: [tcmtf] TCMTF: two kinds of services
> > >
> > > Hi Jose,
> > >
> > > quick question:
> > > > Q3) Is 1.2. a draft proposal? I don=92t think so. If the =
multiplexer
> > > > modifies the multiplexing period, the demux does not need to =
know
it.
> > > > It simply demultiplexes the packets as they arrive. So no
> > > > signaling is
> > > > required: the multiplexer estimates the RTT and modifies the
> > >
> > > multiplexing period.
> > >
> > > How does the multiplexer know the RTT?
> > >
> > > Mirja
> > >
> > > > Q4) Is 2. a draft proposal? I don=92t clearly see it=85 let=92s =
keep on
> >
> > thinking.
> >
> > > > Your =93network operator opinion=94 is interesting here (and =
also
others=92
> > > > opinions, of course).
> > > >
> > > >
> > > >
> > > > Thanks in advance,
> > > >
> > > >
> > > >
> > > > Jose
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es] Enviado el:
> > > > viernes,
> > > > 28 de septiembre de 2012 13:20
> > > > Para: jsaldana@unizar.es; tcmtf@ietf.org
> > > > Asunto: Re: [tcmtf] TCMTF: two kinds of services
> > > >
> > > >
> > > >
> > > > Hi Jose,
> > > >
> > > >
> > > >
> > > > You are talking about dynamically apply TCMTF, and yes, this is =
a
> > > > very interesting aspect. This is different from the third draft
> > > > you proposed in order to dynamically negotiate TCMTF parameters
> > > > between multiplexer and demultiplexer, that would be a higher
> > > > entity in charge of decide when and where or not to apply TCMTF,
> > > > and what kind of TCMTF. As operator, we have a lot of knowledge =
in
> > > > those kind of policies. I have several colleagues that can talk
about that
> issue.
> > > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > >
> > > >
> > > > Fernando Pascual Blanco
> > > >
> > > > Telef=F3nica Global Resources
> > > >
> > > > Network Automation and Dynamization
> > > >
> > > > TECHNOLOGY PEOPLE GROUP
> > > >
> > > > F +34913128779
> > > >
> > > > M +34682005168
> > > >
> > > > fpb@tid.es
> > > >
> > > >
> > > >
> > > > From: "jsaldana@unizar.es" <jsaldana@unizar.es>
> > > > Organization: Universidad de Zaragoza
> > > > Reply-To: "jsaldana@unizar.es" <jsaldana@unizar.es>
> > > > Date: viernes 28 de septiembre de 2012 11:17
> > > > To: "tcmtf@ietf.org" <tcmtf@ietf.org>
> > > > Subject: [tcmtf] TCMTF: two kinds of services
> > > >
> > > >
> > > >
> > > > This is another thought to be discussed. We can have two =
different
> > > > situations for multiplexing flows:
> > > >
> > > >
> > > >
> > > > - delay-sensitive services (e.g., VoIP, online games). In this
> > > > case, TCMTF would add some delay, so it should only be used when
> > > > bandwidth is scarce (rush hours, new game release, etc.). If =
your
> > > > network is working properly, why do you need to save bandwidth =
and
> > > > add a small delay to the clients? So in rush hours there must be =
a
> > > > counterpart in order to add some priority to the tunneled =
packets.
> > > > Otherwise you would penalize them: since they are small and can =
be
> > > > multiplexed, they
> > >
> > > are delayed.
> > >
> > > > - services sending small packets but not delay-sensitive (e.g.,
> > > > whatsapp, m2m packets being generated every second). In this =
case
> > > > TCMTF saves bandwidth while adding some delay, but it is not
critical.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Jose
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >   _____
> > > >
> > > >
> > > > 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>
> > > > http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> > >
> > > --
> > > =
-------------------------------------------------------------------
> > > Dipl.-Ing. Mirja K=FChlewind
> > > Institute of Communication Networks and Computer Engineering (IKR)
> > > University of Stuttgart, Germany Pfaffenwaldring 47, D-70569
> > > Stuttgart
> > >
> > > tel: +49(0)711/685-67973
> > > email: mirja.kuehlewind@ikr.uni-stuttgart.de
> > > web: www.ikr.uni-stuttgart.de
> > > =
-------------------------------------------------------------------
> >
> > _______________________________________________
> > tcmtf mailing list
> > tcmtf@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcmtf
>=20
>=20
>=20
> --
> -------------------------------------------------------------------
> Dipl.-Ing. Mirja K=FChlewind
> Institute of Communication Networks and Computer Engineering (IKR)
> University of Stuttgart, Germany Pfaffenwaldring 47, D-70569 Stuttgart
>=20
> tel: +49(0)711/685-67973
> email: mirja.kuehlewind@ikr.uni-stuttgart.de
> web: www.ikr.uni-stuttgart.de
> -------------------------------------------------------------------


From jsaldana@unizar.es  Wed Oct 10 00:58:31 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 A8E3F21F8448 for <tcmtf@ietfa.amsl.com>; Wed, 10 Oct 2012 00:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.175
X-Spam-Level: 
X-Spam-Status: No, score=-6.175 tagged_above=-999 required=5 tests=[AWL=0.424,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53tTt4ah5jbc for <tcmtf@ietfa.amsl.com>; Wed, 10 Oct 2012 00:58:31 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id B262921F8472 for <tcmtf@ietf.org>; Wed, 10 Oct 2012 00:58:28 -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 q9A7wJ9W021128; Wed, 10 Oct 2012 09:58:19 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es> <201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de> <002001cda62b$f6e63920$e4b2ab60$@unizar.es> <201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de>
In-Reply-To: <201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de>
Date: Wed, 10 Oct 2012 09:58:25 +0200
Organization: Universidad de Zaragoza
Message-ID: <000d01cda6bd$07331370$15993a50$@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: AQINPjcn7rEFviyXS5rdNqTB9c1OEQJyDP5sAiUuOIoBpXi1CpcBEwcQ
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Wesley Eddy <wes@mti-systems.com>, 'Mirja Kuehlewind' <mirja.kuehlewind@ikr.uni-stuttgart.de>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] TCMTF: two kinds of services
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2012 07:58:31 -0000

Dear all,

As Gonzalo and Mirja suggested, I have written a first draft of the Charter
for a (possible) Working Group about TCMTF. In order to make discussion
easier, I have put a number at the beginning of each paragraph, and I have
denoted the three proposed documents as (A), (B) and (C).

There are two options, in my opinion:

a) Only considering the main draft (A) and the "informational" one (B). If
further documents are necessary, the group could be rechartered. In this
case, paragraph 6 would be a part of paragraph 7. This is the option Mirja
suggested, in order to simplify things (I guess).

b) Considering from the beginning the other options we have talked about.
The question is that some of them are not clear by now.

Wes and Martin: I think your opinions as Area Directors are crucial at this
stage: if you want to start the WG soon, I think option a) would be better.

Of course, I hope more people will participate in the improvement of the
Charter. Your feedback will be greatly appreciated.

Well, here it goes. Best regards,

Jose

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

Description of Working Group (version 0)

1. In the last years we are witnessing the raise of new real-time services
that use the Internet for the delivery of interactive multimedia
applications: VoIP, videoconferencing, telemedicine, video vigilance, online
gaming, etc. Due to the need of interactivity, many of these services use
small packets (some tens of bytes), since they have to send frequent updates
to the other extreme of the communication. Therefore, its overhead is
significant, and it becomes even worse when IPv6 is used, as the basic IPv6
header is twice the size of the IPv4 one. In addition, some other services
also send small packets, but they are not delay-sensitive (e.g., instant
messaging, m2m packets being generated every second).

2. In order to mitigate this bad network efficiency, when a number of flows
shares a path, packets can be grouped, considering three different layers:

- Header compression: Taking into account that real-time applications use
different headers (RTP/UDP, UDP or even TCP), different protocols can be
used: no compression, ECRTP, IPHC and ROHC.

- Multiplexing a number of payloads into a single packet. If a number of
flows share a path between an origin and a destination, a multiplexer can
build a bigger packet in which a number of payloads share a common header. A
demultiplexer is necessary at the end of the common path, so as to rebuild
the packets as they were originally sent. PPPMux will be the main option.
Other ones are not discarded.

- Tunneling will be used to send the multiplexed packets end-to-end. The
options in this layer are L2TP, GRE and MPLS.

3. So the first objective of this group is to develop a document (A) that
will specify the protocol stack for compressing, multiplexing and tunneling
traffic flows. Since only standard protocols are being used, each layer will
use its own signaling methods. Thus, the intended status of this document is
"best current practice". In addition, since it "includes" the current RFC
4170, as one of the options, this RFC would be obsoleted.

4. The objective of this first document (A) is to define the different
options which can be used at each layer, not the definition of new protocols
for any of the layers. Only specific problems caused by the interaction
between layers will have to be issued, and suitable extensions may have to
be added to the involved protocols.

5. In addition, TCMTF may save bandwidth but, as a counterpart, some delay
and jitter will be added. This is not a problem for the services which are
not sensitive to delay. However, regarding delay-sensitive services, the
Working Group will also develop a document (B) with recommendations about
the maximum delay and jitter to be added to each kind of service or
application. Empirical research studies with real users will be necessary in
order to establish this set of recommendations.

6. Finally, a document (C) for defining a mechanism for negotiating TCMTF
options between multiplexer and demultiplexer should be developed. If two
mux/demux want to establish a tunnel, they have first to negotiate which
concrete option would they use in each layer: header compression,
multiplexing and tunneling. This will depend on the implementations they
include, and in the scenario.

7. If other interesting features are identified, the group would recharter
and include them (e.g. dynamically applying TCMTF: that would be a higher
entity in charge of deciding when and where, applying or not TCMTF, and what
kind of TCMTF, and what multiplexing period, which manly means added delay.
Additional methods for estimating RTT would also be required).

8. Interactions with other groups can be expected, since TCMTF uses already
defined protocols (ROHC, PPPMux, MPLS, GRE, L2TP).

9. Goals and Milestones
Specification of TCMTF protocol stack (A)
Recommendations of maximum delay depending on the service (B)
Mechanism for negotiating TCMTF options between multiplexer and
demultiplexor (C)


From jsaldana@unizar.es  Wed Oct 10 01:17:30 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 86CCB21F8731 for <tcmtf@ietfa.amsl.com>; Wed, 10 Oct 2012 01:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.196
X-Spam-Level: 
X-Spam-Status: No, score=-6.196 tagged_above=-999 required=5 tests=[AWL=0.402,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 75CljalvQ0g5 for <tcmtf@ietfa.amsl.com>; Wed, 10 Oct 2012 01:17:26 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id E8A4821F84C2 for <tcmtf@ietf.org>; Wed, 10 Oct 2012 01:17:25 -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 q9A8HK9F030481; Wed, 10 Oct 2012 10:17:20 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 10 Oct 2012 10:17:23 +0200
Organization: Universidad de Zaragoza
Message-ID: <000201cda6bf$ad0c4800$0724d800$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0003_01CDA6D0.70951800"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2mv4pYAtzCcnWYTSWHe5kKj0KqPQ==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Wesley Eddy <wes@mti-systems.com>, 'Mirja Kuehlewind' <mirja.kuehlewind@ikr.uni-stuttgart.de>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [tcmtf] [TCMTF]: Charter proposal [Fixing subject]
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2012 08:17:30 -0000

This is a multipart message in MIME format.

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

Dear all,

 

As Gonzalo and Mirja suggested, I have written a first draft of the Charter
for a (possible) Working Group about TCMTF. In order to make discussion
easier, I have put a number at the beginning of each paragraph, and I have
denoted the three proposed documents as (A), (B) and (C).

 

There are two options, in my opinion:

 

a) Only considering the main draft (A) and the "informational" one (B). If
further documents are necessary, the group could be rechartered. In this
case, paragraph 6 would be a part of paragraph 7. This is the option Mirja
suggested, in order to simplify things (I guess).

 

b) Considering from the beginning the other options we have talked about.
The question is that some of them are not clear by now.

 

Wes and Martin: I think your opinions as Area Directors are crucial at this
stage: if you want to start the WG soon, I think option a) would be better.

 

Of course, I hope more people will participate in the improvement of the
Charter. Your feedback will be greatly appreciated.

 

Well, here it goes. Best regards,

 

Jose

 

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

 

Description of Working Group (version 0)

 

1. In the last years we are witnessing the raise of new real-time services
that use the Internet for the delivery of interactive multimedia
applications: VoIP, videoconferencing, telemedicine, video vigilance, online
gaming, etc. Due to the need of interactivity, many of these services use
small packets (some tens of bytes), since they have to send frequent updates
to the other extreme of the communication. Therefore, its overhead is
significant, and it becomes even worse when IPv6 is used, as the basic IPv6
header is twice the size of the IPv4 one. In addition, some other services
also send small packets, but they are not delay-sensitive (e.g., instant
messaging, m2m packets being generated every second).

 

2. In order to mitigate this bad network efficiency, when a number of flows
shares a path, packets can be grouped, considering three different layers:

 

- Header compression: Taking into account that real-time applications use
different headers (RTP/UDP, UDP or even TCP), different protocols can be
used: no compression, ECRTP, IPHC and ROHC.

 

- Multiplexing a number of payloads into a single packet. If a number of
flows share a path between an origin and a destination, a multiplexer can
build a bigger packet in which a number of payloads share a common header. A
demultiplexer is necessary at the end of the common path, so as to rebuild
the packets as they were originally sent. PPPMux will be the main option.
Other ones are not discarded.

 

- Tunneling will be used to send the multiplexed packets end-to-end. The
options in this layer are L2TP, GRE and MPLS.

 

3. So the first objective of this group is to develop a document (A) that
will specify the protocol stack for compressing, multiplexing and tunneling
traffic flows. Since only standard protocols are being used, each layer will
use its own signaling methods. Thus, the intended status of this document is
"best current practice". In addition, since it "includes" the current RFC
4170, as one of the options, this RFC would be obsoleted.

 

4. The objective of this first document (A) is to define the different
options which can be used at each layer, not the definition of new protocols
for any of the layers. Only specific problems caused by the interaction
between layers will have to be issued, and suitable extensions may have to
be added to the involved protocols.

 

5. In addition, TCMTF may save bandwidth but, as a counterpart, some delay
and jitter will be added. This is not a problem for the services which are
not sensitive to delay. However, regarding delay-sensitive services, the
Working Group will also develop a document (B) with recommendations about
the maximum delay and jitter to be added to each kind of service or
application. Empirical research studies with real users will be necessary in
order to establish this set of recommendations.

 

6. Finally, a document (C) for defining a mechanism for negotiating TCMTF
options between multiplexer and demultiplexer should be developed. If two
mux/demux want to establish a tunnel, they have first to negotiate which
concrete option would they use in each layer: header compression,
multiplexing and tunneling. This will depend on the implementations they
include, and in the scenario.

 

7. If other interesting features are identified, the group would recharter
and include them (e.g. dynamically applying TCMTF: that would be a higher
entity in charge of deciding when and where, applying or not TCMTF, and what
kind of TCMTF, and what multiplexing period, which manly means added delay.
Additional methods for estimating RTT would also be required).

 

8. Interactions with other groups can be expected, since TCMTF uses already
defined protocols (ROHC, PPPMux, MPLS, GRE, L2TP).

 

9. Goals and Milestones

Specification of TCMTF protocol stack (A) Recommendations of maximum delay
depending on the service (B) Mechanism for negotiating TCMTF options between
multiplexer and demultiplexor (C)

 


------=_NextPart_000_0003_01CDA6D0.70951800
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;}
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.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:"Calibri","sans-serif";}
.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=3DMsoPlainText><span =
lang=3DEN-US>Dear all,<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>As Gonzalo and Mirja suggested, =
I have written a first draft of the Charter for a (possible) Working =
Group about TCMTF. In order to make discussion easier, I have put a =
number at the beginning of each paragraph, and I have denoted the three =
proposed documents as (A), (B) and (C).<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>There are two options, in my =
opinion:<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>a) Only considering the main draft (A) and the =
&quot;informational&quot; one (B). If further documents are necessary, =
the group could be rechartered. In this case, paragraph 6 would be a =
part of paragraph 7. This is the option Mirja suggested, in order to =
simplify things (I guess).<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>b) Considering from the =
beginning the other options we have talked about. The question is that =
some of them are not clear by now.<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>Wes and Martin: I think your =
opinions as Area Directors are crucial at this stage: if you want to =
start the WG soon, I think option a) would be =
better.<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>Of course, I hope more people will participate in the =
improvement of the Charter. Your feedback will be greatly =
appreciated.<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>Well, here it goes. Best regards,<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>Jose<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></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>Description of Working Group =
(version 0)<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>1. In the last years we are witnessing the raise of new =
real-time services that use the Internet for the delivery of interactive =
multimedia applications: VoIP, videoconferencing, telemedicine, video =
vigilance, online gaming, etc. Due to the need of interactivity, many of =
these services use small packets (some tens of bytes), since they have =
to send frequent updates to the other extreme of the communication. =
Therefore, its overhead is significant, and it becomes even worse when =
IPv6 is used, as the basic IPv6 header is twice the size of the IPv4 =
one. In addition, some other services also send small packets, but they =
are not delay-sensitive (e.g., instant messaging, m2m packets being =
generated every second).<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>2. In order to mitigate this bad =
network efficiency, when a number of flows shares a path, packets can be =
grouped, considering three different layers:<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>- Header compression: Taking =
into account that real-time applications use different headers (RTP/UDP, =
UDP or even TCP), different protocols can be used: no compression, =
ECRTP, IPHC and ROHC.<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>- Multiplexing a number of payloads into a single packet. =
If a number of flows share a path between an origin and a destination, a =
multiplexer can build a bigger packet in which a number of payloads =
share a common header. A demultiplexer is necessary at the end of the =
common path, so as to rebuild the packets as they were originally sent. =
PPPMux will be the main option. Other ones are not =
discarded.<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>- Tunneling will be used to send the multiplexed packets =
end-to-end. The options in this layer are L2TP, GRE and =
MPLS.<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>3. So the first objective of this group is to develop a =
document (A) that will specify the protocol stack for compressing, =
multiplexing and tunneling traffic flows. Since only standard protocols =
are being used, each layer will use its own signaling methods. Thus, the =
intended status of this document is &#8220;best current practice&#8221;. =
In addition, since it &#8220;includes&#8221; the current RFC 4170, as =
one of the options, this RFC would be obsoleted.<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>4. The objective of this first =
document (A) is to define the different options which can be used at =
each layer, not the definition of new protocols for any of the layers. =
Only specific problems caused by the interaction between layers will =
have to be issued, and suitable extensions may have to be added to the =
involved protocols.<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>5. In addition, TCMTF may save bandwidth but, as a =
counterpart, some delay and jitter will be added. This is not a problem =
for the services which are not sensitive to delay. However, regarding =
delay-sensitive services, the Working Group will also develop a document =
(B) with recommendations about the maximum delay and jitter to be added =
to each kind of service or application. Empirical research studies with =
real users will be necessary in order to establish this set of =
recommendations.<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>6. Finally, a document (C) for defining a mechanism for =
negotiating TCMTF options between multiplexer and demultiplexer should =
be developed. If two mux/demux want to establish a tunnel, they have =
first to negotiate which concrete option would they use in each layer: =
header compression, multiplexing and tunneling. This will depend on the =
implementations they include, and in the =
scenario.<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>7. If other interesting features are identified, the group =
would recharter and include them (e.g. dynamically applying TCMTF: that =
would be a higher entity in charge of deciding when and where, applying =
or not TCMTF, and what kind of TCMTF, and what multiplexing period, =
which manly means added delay. Additional methods for estimating RTT =
would also be required).<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>8. Interactions with other =
groups can be expected, since TCMTF uses already defined protocols =
(ROHC, PPPMux, MPLS, GRE, L2TP).<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>9. Goals and =
Milestones<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Specification of TCMTF protocol stack (A) Recommendations =
of maximum delay depending on the service (B) Mechanism for negotiating =
TCMTF options between multiplexer and demultiplexor =
(C)<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_0003_01CDA6D0.70951800--


From ggx@gigix.net  Wed Oct 10 01:20:35 2012
Return-Path: <ggx@gigix.net>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A78721F8771 for <tcmtf@ietfa.amsl.com>; Wed, 10 Oct 2012 01:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BVHlk1jiBsda for <tcmtf@ietfa.amsl.com>; Wed, 10 Oct 2012 01:20:34 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF0B21F8731 for <tcmtf@ietf.org>; Wed, 10 Oct 2012 01:20:33 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hr7so244315wib.13 for <tcmtf@ietf.org>; Wed, 10 Oct 2012 01:20:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=lLH8TA2F6ovD0Co/vQJiTx7Ej41dUXSTYhbERMYdgGo=; b=NtQm7XgTrVseylbZVI7ChQBw0++3hgEe8hiTuyLgbo+ke0m0yBtEVSM1LtJJcU2+kV /H+HYLRszWHBYTIrkVKE4e28zv/gZQf5WVsdy7FQ88mfim5Sf0cuvLNprr+dwpxemO5M Gt8cHDoudhiWpagSfbjgt69z49nbCOtolG0LheH+IrtJuQaj3lFVQH4J6GvXP9tZRLvB aIPHoWfPdxX2leAtCt4ze6+L1hWIPlJZVWDR12sshb0HfS2XXhMWBbCexR0MhdzAavfR zAD/KvwxHHyt84YCk7MHgdqGEVQVVlSnqtS0uHAt6SQec5up+NULKhyARXGCWAwQps2z 0HBA==
Received: by 10.216.210.5 with SMTP id t5mr13423067weo.32.1349857224857; Wed, 10 Oct 2012 01:20:24 -0700 (PDT)
Received: from dhcp164-03.enst.fr (dhcp164-03.enst.fr. [137.194.165.3]) by mx.google.com with ESMTPS id q7sm1513749wiy.11.2012.10.10.01.20.23 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 10 Oct 2012 01:20:24 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <000d01cda6bd$07331370$15993a50$@unizar.es>
Date: Wed, 10 Oct 2012 10:23:27 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <08DEAFED-C1BC-45E3-B2C9-C9879145FC4B@gigix.net>
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es> <201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de> <002001cda62b$f6e63920$e4b2ab60$@unizar.es> <201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de> <000d01cda6bd$07331370$15993a50$@unizar.es>
To: jsaldana@unizar.es
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQnid4JMqD7CyOFfJjp3liTTUP+6iVC+5+cRRZgyDcYja0XiInnJm/UEO2eNtFPiA9MJKi53
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: two kinds of services
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2012 08:20:35 -0000

Hi All,

On 10 Oct. 2012, at 09:58 , Jose Saldana <jsaldana@unizar.es> wrote:

> - Tunneling will be used to send the multiplexed packets end-to-end. =
The
> options in this layer are L2TP, GRE and MPLS.
>=20

I was wondering if the group might be interested in exploring also other =
form of tunnelling, e.g., LISP.

Obviously, since LISP is an experimental effort, it cannot be tagged as =
"best current practice" and included in document (A).

However, the group may have a slightly "larger" scope and include =
alternative forms of tunnelling (and/or multiplexing and/or header =
compression) (may be documented separately).

Thoughts?

ciao

Luigi




From jsaldana@unizar.es  Wed Oct 10 04:48:13 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 EC34521F871A for <tcmtf@ietfa.amsl.com>; Wed, 10 Oct 2012 04:48:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.216
X-Spam-Level: 
X-Spam-Status: No, score=-7.216 tagged_above=-999 required=5 tests=[AWL=1.383,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FqPWjyHL7NRV for <tcmtf@ietfa.amsl.com>; Wed, 10 Oct 2012 04:48:13 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2CCFD21F86FC for <tcmtf@ietf.org>; Wed, 10 Oct 2012 04:48:12 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id q9ABm5Kf003053; Wed, 10 Oct 2012 13:48:06 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Luigi Iannone'" <ggx@gigix.net>
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es>	<201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de>	<002001cda62b$f6e63920$e4b2ab60$@unizar.es>	<201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de>	<000d01cda6bd$07331370$15993a50$@unizar.es> <08DEAFED-C1BC-45E3-B2C9-C9879145FC4B@gigix.net>
In-Reply-To: <08DEAFED-C1BC-45E3-B2C9-C9879145FC4B@gigix.net>
Date: Wed, 10 Oct 2012 13:48:09 +0200
Organization: Universidad de Zaragoza
Message-ID: <002001cda6dd$1f30d690$5d9283b0$@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: AQINPjcn7rEFviyXS5rdNqTB9c1OEQJyDP5sAiUuOIoBpXi1CgF1kAIEAY+uERuW6SvyMA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: two kinds of services
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2012 11:48:14 -0000

Luigi,

Where would you include LISP here? With GRE/L2TP, or with MPLS?

We are also thinking about including other tunneling schemes, as VLAN, =
etc.

(to be seen in Courier letters)

    TCP/IP   UDP/IP  RTP/UDP/IP
         \     |     /
          \    |    /                     ------------------------------
           \   |   /
Nothing or ROHC or ECRTP or IPHC             header compressing layer
               |
               |                          ------------------------------
               |
   PPPMUX or other mux protocols                multiplexing layer
               |
              / \                         ------------------------------
             /   \
            /     \
   GRE or L2TP     \                              tunneling layer
          |        MPLS
          |                               ------------------------------
          IP

Thanks,

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Luigi Iannone
> Enviado el: mi=E9rcoles, 10 de octubre de 2012 10:23
> Para: jsaldana@unizar.es
> CC: tcmtf@ietf.org
> Asunto: Re: [tcmtf] TCMTF: two kinds of services
>=20
> Hi All,
>=20
> On 10 Oct. 2012, at 09:58 , Jose Saldana <jsaldana@unizar.es> wrote:
>=20
> > - Tunneling will be used to send the multiplexed packets end-to-end.
> > The options in this layer are L2TP, GRE and MPLS.
> >
>=20
> I was wondering if the group might be interested in exploring also =
other
form
> of tunnelling, e.g., LISP.
>=20
> Obviously, since LISP is an experimental effort, it cannot be tagged =
as
"best
> current practice" and included in document (A).
>=20
> However, the group may have a slightly "larger" scope and include
> alternative forms of tunnelling (and/or multiplexing and/or header
> compression) (may be documented separately).
>=20
> Thoughts?
>=20
> ciao
>=20
> Luigi
>=20
>=20
>=20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From navajas@unizar.es  Wed Oct 10 05:02:41 2012
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 591E321F8715 for <tcmtf@ietfa.amsl.com>; Wed, 10 Oct 2012 05:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.298
X-Spam-Level: 
X-Spam-Status: No, score=-8.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hLdspiClafmD for <tcmtf@ietfa.amsl.com>; Wed, 10 Oct 2012 05:02:40 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id E7E6621F86C2 for <tcmtf@ietf.org>; Wed, 10 Oct 2012 05:02:39 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id q9AC2ZGq016581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Wed, 10 Oct 2012 14:02:35 +0200
Message-ID: <507563D8.7000207@unizar.es>
Date: Wed, 10 Oct 2012 14:02:32 +0200
From: =?ISO-8859-1?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es>	<201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de>	<002001cda62b$f6e63920$e4b2ab60$@unizar.es>	<201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de>	<000d01cda6bd$07331370$15993a50$@unizar.es> <08DEAFED-C1BC-45E3-B2C9-C9879145FC4B@gigix.net> <002001cda6dd$1f30d690$5d9283b0$@unizar.es>
In-Reply-To: <002001cda6dd$1f30d690$5d9283b0$@unizar.es>
Content-Type: multipart/alternative; boundary="------------060806030500010005050206"
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] TCMTF: two kinds of services
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2012 12:02:41 -0000

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

Perhaps VLAN can not be considered as a tunnelscheme. In fact we are 
thinking about replacing MPLS for Layer 2 transport and then specify 
MPLS tunnels or VLAN technologies and so on.

Julián


El 10/10/2012 13:48, Jose Saldana escribió:
> Luigi,
>
> Where would you include LISP here? With GRE/L2TP, or with MPLS?
>
> We are also thinking about including other tunneling schemes, as VLAN, etc.
>
> (to be seen in Courier letters)
>
>      TCP/IP   UDP/IP  RTP/UDP/IP
>           \     |     /
>            \    |    /                     ------------------------------
>             \   |   /
> Nothing or ROHC or ECRTP or IPHC             header compressing layer
>                 |
>                 |                          ------------------------------
>                 |
>     PPPMUX or other mux protocols                multiplexing layer
>                 |
>                / \                         ------------------------------
>               /   \
>              /     \
>     GRE or L2TP     \                              tunneling layer
>            |        MPLS
>            |                               ------------------------------
>            IP
>
> Thanks,
>
> Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Luigi Iannone
>> Enviado el: miércoles, 10 de octubre de 2012 10:23
>> Para: jsaldana@unizar.es
>> CC: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] TCMTF: two kinds of services
>>
>> Hi All,
>>
>> On 10 Oct. 2012, at 09:58 , Jose Saldana <jsaldana@unizar.es> wrote:
>>
>>> - Tunneling will be used to send the multiplexed packets end-to-end.
>>> The options in this layer are L2TP, GRE and MPLS.
>>>
>> I was wondering if the group might be interested in exploring also other
> form
>> of tunnelling, e.g., LISP.
>>
>> Obviously, since LISP is an experimental effort, it cannot be tagged as
> "best
>> current practice" and included in document (A).
>>
>> However, the group may have a slightly "larger" scope and include
>> alternative forms of tunnelling (and/or multiplexing and/or header
>> compression) (may be documented separately).
>>
>> Thoughts?
>>
>> ciao
>>
>> Luigi
>>
>>
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>
>


--------------060806030500010005050206
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">
      <div id="gt-res-content" class="almost_half_cell"
        closure_uid_y2544f="590">
        <div style="ZOOM: 1" dir="ltr" closure_uid_y2544f="589"><span
            id="result_box" closure_uid_y2544f="123" c="4" a="undefined"
            lang="en"><span class="hps" closure_uid_y2544f="1270">Perhaps</span>
            <span class="hps" closure_uid_y2544f="1271">VLAN</span> <span
              class="hps" closure_uid_y2544f="1272">can not be
              considered</span> <span class="hps"
              closure_uid_y2544f="1273">as</span> <span class="hps"
              closure_uid_y2544f="1274">a tunnel</span><span
              closure_uid_y2544f="1275"> scheme.</span> <span
              class="hps" closure_uid_y2544f="1276">In fact</span> <span
              class="hps" closure_uid_y2544f="1277">we are</span> <span
              class="hps" closure_uid_y2544f="1278">thinking about
              replacing</span> <span class="hps"
              closure_uid_y2544f="1279">MPLS</span> <span class="hps"
              closure_uid_y2544f="1280">for</span> <span class="hps"
              closure_uid_y2544f="1281">Layer 2 transport and then <span
                class="hps" closure_uid_y2544f="2368" oc="null">specify</span>
              <span class="hps" closure_uid_y2544f="2369" oc="null">MPLS
                tunnels or&nbsp;</span><span class="hps"
                closure_uid_y2544f="2371" oc="null">VLAN</span>
              technologies and so on.<br>
              <br>
              Juli&aacute;n<br>
              <br>
              <br>
              <span class="hps" closure_uid_y2544f="2372" oc="null"></span></span></span></div>
      </div>
      El 10/10/2012 13:48, Jose Saldana escribi&oacute;:<br>
    </div>
    <blockquote cite="mid:002001cda6dd$1f30d690$5d9283b0$@unizar.es"
      type="cite">
      <pre wrap="">Luigi,

Where would you include LISP here? With GRE/L2TP, or with MPLS?

We are also thinking about including other tunneling schemes, as VLAN, etc.

(to be seen in Courier letters)

    TCP/IP   UDP/IP  RTP/UDP/IP
         \     |     /
          \    |    /                     ------------------------------
           \   |   /
Nothing or ROHC or ECRTP or IPHC             header compressing layer
               |
               |                          ------------------------------
               |
   PPPMUX or other mux protocols                multiplexing layer
               |
              / \                         ------------------------------
             /   \
            /     \
   GRE or L2TP     \                              tunneling layer
          |        MPLS
          |                               ------------------------------
          IP

Thanks,

Jose

</pre>
      <blockquote type="cite">
        <pre wrap="">-----Mensaje original-----
De: <a class="moz-txt-link-abbreviated" href="mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>] En nombre de
Luigi Iannone
Enviado el: mi&eacute;rcoles, 10 de octubre de 2012 10:23
Para: <a class="moz-txt-link-abbreviated" href="mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>
CC: <a class="moz-txt-link-abbreviated" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>
Asunto: Re: [tcmtf] TCMTF: two kinds of services

Hi All,

On 10 Oct. 2012, at 09:58 , Jose Saldana <a class="moz-txt-link-rfc2396E" href="mailto:jsaldana@unizar.es">&lt;jsaldana@unizar.es&gt;</a> wrote:

</pre>
        <blockquote type="cite">
          <pre wrap="">- Tunneling will be used to send the multiplexed packets end-to-end.
The options in this layer are L2TP, GRE and MPLS.

</pre>
        </blockquote>
        <pre wrap="">
I was wondering if the group might be interested in exploring also other
</pre>
      </blockquote>
      <pre wrap="">form
</pre>
      <blockquote type="cite">
        <pre wrap="">of tunnelling, e.g., LISP.

Obviously, since LISP is an experimental effort, it cannot be tagged as
</pre>
      </blockquote>
      <pre wrap="">"best
</pre>
      <blockquote type="cite">
        <pre wrap="">current practice" and included in document (A).

However, the group may have a slightly "larger" scope and include
alternative forms of tunnelling (and/or multiplexing and/or header
compression) (may be documented separately).

Thoughts?

ciao

Luigi



_______________________________________________
tcmtf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tcmtf">https://www.ietf.org/mailman/listinfo/tcmtf</a>
</pre>
      </blockquote>
      <pre wrap="">
_______________________________________________
tcmtf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tcmtf">https://www.ietf.org/mailman/listinfo/tcmtf</a>


</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------060806030500010005050206--

From ggx@gigix.net  Thu Oct 11 00:08:14 2012
Return-Path: <ggx@gigix.net>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 137DD21F8686 for <tcmtf@ietfa.amsl.com>; Thu, 11 Oct 2012 00:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oRVj4y82fFPc for <tcmtf@ietfa.amsl.com>; Thu, 11 Oct 2012 00:08:13 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id CC37721F86B2 for <tcmtf@ietf.org>; Thu, 11 Oct 2012 00:08:12 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hq12so6585391wib.13 for <tcmtf@ietf.org>; Thu, 11 Oct 2012 00:08:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=ZtXXN+Dw3/wAdVWsoL4VAP2I0WwaxObaPM6pbQiltpk=; b=mEKg0JaXFBKpirx17J0n+7yOcgFOSGzM6o9V/RshZagZmV0Pe98rshSpAEC97l8Ui0 yvZYAnDlZzxHUR2JHckqsUvG+FJCZJi6ICRy//GLnDcoDrLCLltxD25m0Av/Stw93A98 klqXyEFSm1VxXJdAX6hz5iOJuyEyYXK/Q6lrGr8254ruXB03SnZIQUDhl1ibb2imj3GT 0uRUDxOVCDzg/niPgidWK8lGj67hHg2rhq11NxJieFoLbCLVNlVyn12ugB23dMMFumC6 xGRu5/4uA+V89JqGlAjlP3gxb3ABF/KNmb+wmE/RR4X8nP55ZmkGZqGWIzJcOAk9C0Rp uODQ==
Received: by 10.216.195.133 with SMTP id p5mr16346812wen.1.1349939291806; Thu, 11 Oct 2012 00:08:11 -0700 (PDT)
Received: from ?IPv6:2001:660:330f:a4:4d8b:bff:8ccd:32c4? ([2001:660:330f:a4:4d8b:bff:8ccd:32c4]) by mx.google.com with ESMTPS id hv8sm34905944wib.0.2012.10.11.00.08.10 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 11 Oct 2012 00:08:11 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <002001cda6dd$1f30d690$5d9283b0$@unizar.es>
Date: Thu, 11 Oct 2012 09:11:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C62762CA-C668-4758-B72B-20E5CDB634E0@gigix.net>
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es>	<201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de>	<002001cda62b$f6e63920$e4b2ab60$@unizar.es>	<201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de>	<000d01cda6bd$07331370$15993a50$@unizar.es> <08DEAFED-C1BC-45E3-B2C9-C9879145FC4B@gigix.net> <002001cda6dd$1f30d690$5d9283b0$@unizar.es>
To: <jsaldana@unizar.es>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQltQpucq5J7EoXouL98gjhH/8oKuTFWoWyGfvzQP8t++1446PrzHlQfMkdAcAC3bCySlaI+
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: two kinds of services
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 07:08:14 -0000

Hi Jose,

I would put LISP in two different layers.

You can consider LISP as composed of two main parts:=20

1. the encap/decap operations (i.e., the tunnelling)=20

2. the mapping system (basically controlling which traffic is =
tunnelled).

The first can be used  at the tunnelling layer, beside GRE/MPLS/L2TP =
(having multiple options is always a good thing ;-) ), to perform the =
tunnelling. Some parts of the LISP header might be exploited to carry TE =
information (e.g., the Instance ID can be used as QoS tag).

The second can be used at Mux/Demux layer. The LISP mapping system might =
be extended to perform tcmtf negotiation by  leveraging on a particular =
form of mappings. The advantage is that there is already quite a bit of =
signalling machinery out there that can be easily re-used/extended.

Ciao

Luigi


On 10 Oct. 2012, at 13:48 , Jose Saldana <jsaldana@unizar.es> wrote:

> Luigi,
>=20
> Where would you include LISP here? With GRE/L2TP, or with MPLS?
>=20
> We are also thinking about including other tunneling schemes, as VLAN, =
etc.
>=20
> (to be seen in Courier letters)
>=20
>    TCP/IP   UDP/IP  RTP/UDP/IP
>         \     |     /
>          \    |    /                     =
------------------------------
>           \   |   /
> 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
> Thanks,
>=20
> Jose
>=20
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
>> Luigi Iannone
>> Enviado el: mi=E9rcoles, 10 de octubre de 2012 10:23
>> Para: jsaldana@unizar.es
>> CC: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] TCMTF: two kinds of services
>>=20
>> Hi All,
>>=20
>> On 10 Oct. 2012, at 09:58 , Jose Saldana <jsaldana@unizar.es> wrote:
>>=20
>>> - Tunneling will be used to send the multiplexed packets end-to-end.
>>> The options in this layer are L2TP, GRE and MPLS.
>>>=20
>>=20
>> I was wondering if the group might be interested in exploring also =
other
> form
>> of tunnelling, e.g., LISP.
>>=20
>> Obviously, since LISP is an experimental effort, it cannot be tagged =
as
> "best
>> current practice" and included in document (A).
>>=20
>> However, the group may have a slightly "larger" scope and include
>> alternative forms of tunnelling (and/or multiplexing and/or header
>> compression) (may be documented separately).
>>=20
>> Thoughts?
>>=20
>> ciao
>>=20
>> Luigi
>>=20
>>=20
>>=20
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>=20


From fpb@tid.es  Wed Oct 17 07:46:54 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 931A621F85D5 for <tcmtf@ietfa.amsl.com>; Wed, 17 Oct 2012 07:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.172
X-Spam-Level: 
X-Spam-Status: No, score=-7.172 tagged_above=-999 required=5 tests=[AWL=1.427,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8F0axbJ7Fb3M for <tcmtf@ietfa.amsl.com>; Wed, 17 Oct 2012 07:46:53 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1C0F721F875D for <tcmtf@ietf.org>; Wed, 17 Oct 2012 07:46:53 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MC100GWCL21RG@tid.hi.inet> for tcmtf@ietf.org; Wed, 17 Oct 2012 16:46:51 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id E7.BB.03050.BD4CE705; Wed, 17 Oct 2012 16:46:51 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MC100G01L23RG@tid.hi.inet> for tcmtf@ietf.org; Wed, 17 Oct 2012 16:46:51 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.152]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.004; Wed, 17 Oct 2012 16:46:51 +0200
Date: Wed, 17 Oct 2012 14:46:50 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <C62762CA-C668-4758-B72B-20E5CDB634E0@gigix.net>
X-Originating-IP: [10.95.64.115]
To: Luigi Iannone <ggx@gigix.net>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Message-id: <F5EDC35DF914C1428C28E149F10463A249DDFF76@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] TCMTF: two kinds of services
Thread-index: Ac2dWc3roSS93utvTYC2TKQuzRqQgwAEW7WAAfijtIAALpxBgAAEvY2AAALdlgAAIWZvgAAA39GAAAcmKYAAKJ9fAAFAMaAg
X-AuditID: 0a5f4068-b7f176d000000bea-6d-507ec4dbe69c
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrIKsWRmVeSWpSXmKPExsXCFe/ApXv7SF2AwZVuZYtdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoErY+H6NvaCQ0oVy562sDcw7pTsYuTkkBAwkZi1aAMbhC0mceHe eiCbi0NIYCOjxMTOc+wQzk9GieaOtcwgVUICmxglLuwuBbFZBFQl7p24wARiswloSZy+u4oF xBYWMJTY92MmI4jNKWAr0bHmB9QGBYk/5x6D1YgI+EhM+/cWqJeDgxlozrxviiBhXgFviXfb m9kgbEGJH5PvgZUzC+hI9H7/xgxhi0s0t96EimtLPHl3gRXEZhSQlXg3fz4rxHgjiafLv0DZ BRIz5r1mhjhBQGLJnvNQtqjEy8f/WCF+XMgsMfVaP9sERvFZSHbPQrJ7FpLds5DsXsDIsopR rDipKDM9oyQ3MTMn3cBQLyNTLzMvtWQTIySOMnYwLt+pcohRgINRiYd3ZUddgBBrYllxZe4h RkkOJiVR3r6DQCG+pPyUyozE4oz4otKc1OJDjBIczEoivC3LgHK8KYmVValF+TApGQ4OJQle C2DMCwkWpaanVqRl5gCTBUyaiYMTpJ0HqF0GpIa3uCAxtzgzHSJ/ilGVo7Fn0UNGIZa8/LxU KXHe8ENARQIgRRmleXBzXjGKAx0szPv9MFCWB5ju4Ca8AhrOBDS8a3c1yPCSRISUVANj7l3X 3x1BktkbZV43s2zREm3rCl9c61FzgfHPdqaaaLarp7YoLPDeEr1lxqb7U58u+Pkm/biUpBpT 5c7K+f92vTvEJPatlTGqZbnuX4brR8q+rl526UDoqdLAFM6b2ds/+nE36exgTG6YFz2VSzPJ POC9sK62w90Jul7WMloPXzKomzW1cUQqsRRnJBpqMRcVJwIAuvJ+XzQDAAA=
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es> <201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de> <002001cda62b$f6e63920$e4b2ab60$@unizar.es> <201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de> <000d01cda6bd$07331370$15993a50$@unizar.es> <08DEAFED-C1BC-45E3-B2C9-C9879145FC4B@gigix.net> <002001cda6dd$1f30d690$5d9283b0$@unizar.es> <C62762CA-C668-4758-B72B-20E5CDB634E0@gigix.net>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] TCMTF: two kinds of services
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, 17 Oct 2012 14:46:54 -0000

Hi Luigi,

        I understand the use of LISP as a tunnel, and I=B4m not an expert (=
as you are) in LISP. Could you please explain us how do you think LISP mapp=
ing system could help to perform TCMTF negotiation?

        We have two things here: the first one is the negotiation between m=
ultiplexer and demultiplexer on what capabilities are supported in every en=
d. The second one would be to identify what flows should be tunneled, multi=
plexed and or compressed and under what terms.

        Thank you for your interest!

B.R.

Fernando

-----Original Message-----
From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of L=
uigi Iannone
Sent: jueves, 11 de octubre de 2012 9:11
To: jsaldana@unizar.es
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: two kinds of services

Hi Jose,

I would put LISP in two different layers.

You can consider LISP as composed of two main parts:

1. the encap/decap operations (i.e., the tunnelling)

2. the mapping system (basically controlling which traffic is tunnelled).

The first can be used  at the tunnelling layer, beside GRE/MPLS/L2TP (havin=
g multiple options is always a good thing ;-) ), to perform the tunnelling.=
 Some parts of the LISP header might be exploited to carry TE information (=
e.g., the Instance ID can be used as QoS tag).

The second can be used at Mux/Demux layer. The LISP mapping system might be=
 extended to perform tcmtf negotiation by  leveraging on a particular form =
of mappings. The advantage is that there is already quite a bit of signalli=
ng machinery out there that can be easily re-used/extended.

Ciao

Luigi


On 10 Oct. 2012, at 13:48 , Jose Saldana <jsaldana@unizar.es> wrote:

> Luigi,
>
> Where would you include LISP here? With GRE/L2TP, or with MPLS?
>
> We are also thinking about including other tunneling schemes, as VLAN, et=
c.
>
> (to be seen in Courier letters)
>
>    TCP/IP   UDP/IP  RTP/UDP/IP
>         \     |     /
>          \    |    /                     ------------------------------
>           \   |   /
> Nothing or ROHC or ECRTP or IPHC             header compressing layer
>               |
>               |                          ------------------------------
>               |
>   PPPMUX or other mux protocols                multiplexing layer
>               |
>              / \                         ------------------------------
>             /   \
>            /     \
>   GRE or L2TP     \                              tunneling layer
>          |        MPLS
>          |                               ------------------------------
>          IP
>
> Thanks,
>
> Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>> de Luigi Iannone Enviado el: mi=E9rcoles, 10 de octubre de 2012 10:23
>> Para: jsaldana@unizar.es
>> CC: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] TCMTF: two kinds of services
>>
>> Hi All,
>>
>> On 10 Oct. 2012, at 09:58 , Jose Saldana <jsaldana@unizar.es> wrote:
>>
>>> - Tunneling will be used to send the multiplexed packets end-to-end.
>>> The options in this layer are L2TP, GRE and MPLS.
>>>
>>
>> I was wondering if the group might be interested in exploring also
>> other
> form
>> of tunnelling, e.g., LISP.
>>
>> Obviously, since LISP is an experimental effort, it cannot be tagged
>> as
> "best
>> current practice" and included in document (A).
>>
>> However, the group may have a slightly "larger" scope and include
>> alternative forms of tunnelling (and/or multiplexing and/or header
>> compression) (may be documented separately).
>>
>> Thoughts?
>>
>> ciao
>>
>> Luigi
>>
>>
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>

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

________________________________

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

From jsaldana@unizar.es  Fri Oct 19 09:04: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 C4A7721F857A; Fri, 19 Oct 2012 09:04:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.292
X-Spam-Level: 
X-Spam-Status: No, score=-7.292 tagged_above=-999 required=5 tests=[AWL=1.306,  BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PrvLmk2lR+4t; Fri, 19 Oct 2012 09:04:30 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 76EAA21F87A4; Fri, 19 Oct 2012 09:04:29 -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 q9JG4KnY021903; Fri, 19 Oct 2012 18:04:20 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Luigi Iannone'" <ggx@gigix.net>
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es>	<201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de>	<002001cda62b$f6e63920$e4b2ab60$@unizar.es>	<201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de>	<000d01cda6bd$07331370$15993a50$@unizar.es>	<08DEAFED-C1BC-45E3-B2C9-C9879145FC4B@gigix.net>	<002001cda6dd$1f30d690$5d9283b0$@unizar.es> <C62762CA-C668-4758-B72B-20E5CDB634E0@gigix.net>
In-Reply-To: <C62762CA-C668-4758-B72B-20E5CDB634E0@gigix.net>
Date: Fri, 19 Oct 2012 18:04:28 +0200
Organization: Universidad de Zaragoza
Message-ID: <00d701cdae13$6b8b5f00$42a21d00$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D8_01CDAE24.2F1603C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQINPjcn7rEFviyXS5rdNqTB9c1OEQJyDP5sAiUuOIoBpXi1CgF1kAIEAY+uERsBeQryKgLri8P6ltRzMAA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, lisp@ietf.org
Subject: Re: [tcmtf] TCMTF: two kinds of services
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: Fri, 19 Oct 2012 16:04:32 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00D8_01CDAE24.2F1603C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Luigi,

=20

What about this protocol stack for LISP within TCMTF?

(to be seen in Courier letters)

=20

    TCP/IP   UDP/IP  RTP/UDP/IP

         \     |     /

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

           \   |   /

Nothing or ROHC or ECRTP or IPHC             header compressing layer

               |

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

               |

   PPPMUX or other mux protocols                multiplexing layer

           /   |     \

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

         /    LISP     \

        /      |        \

GRE or L2TP   UDP        \                        tunneling layer

       |       |        MPLS

       |       |                           =
------------------------------

       IP      IP

=20

=20

I don=92t know if LISP could be included into TCMTF draft. What do you =
think?
Should it be defined inside the LISP WG?

=20

We have to talk about that LISP signaling which could be used in TCMTF, =
as
you say.

=20

Thanks,

=20

Jose

=20

> -----Mensaje original-----

> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de

> Luigi Iannone

> Enviado el: jueves, 11 de octubre de 2012 9:11

> Para: jsaldana@unizar.es

> CC: tcmtf@ietf.org

> Asunto: Re: [tcmtf] TCMTF: two kinds of services

>=20

> Hi Jose,

>=20

> I would put LISP in two different layers.

>=20

> You can consider LISP as composed of two main parts:

>=20

> 1. the encap/decap operations (i.e., the tunnelling)

>=20

> 2. the mapping system (basically controlling which traffic is =
tunnelled).

>=20

> The first can be used  at the tunnelling layer, beside GRE/MPLS/L2TP
(having

> multiple options is always a good thing ;-) ), to perform the =
tunnelling.
Some

> parts of the LISP header might be exploited to carry TE information =
(e.g.,
the

> Instance ID can be used as QoS tag).

>=20

> The second can be used at Mux/Demux layer. The LISP mapping system

> might be extended to perform tcmtf negotiation by  leveraging on a

> particular form of mappings. The advantage is that there is already =
quite
a bit

> of signalling machinery out there that can be easily re-used/extended.

>=20

> Ciao

>=20

> Luigi

>=20

>=20

> On 10 Oct. 2012, at 13:48 , Jose Saldana < <mailto:jsaldana@unizar.es>
jsaldana@unizar.es> wrote:

>=20

> > Luigi,

> >

> > Where would you include LISP here? With GRE/L2TP, or with MPLS?

> >

> > We are also thinking about including other tunneling schemes, as =
VLAN,

> etc.

> >

> > (to be seen in Courier letters)

> >

> >    TCP/IP   UDP/IP  RTP/UDP/IP

> >         \     |     /

> >          \    |    /                     =
------------------------------

> >           \   |   /

> > Nothing or ROHC or ECRTP or IPHC             header compressing =
layer

> >               |

> >               |                          =
------------------------------

> >               |

> >   PPPMUX or other mux protocols                multiplexing layer

> >               |

> >              / \                         =
------------------------------

> >             /   \

> >            /     \

> >   GRE or L2TP     \                              tunneling layer

> >          |        MPLS

> >          |                               =
------------------------------

> >          IP

> >

> > Thanks,

> >

> > Jose

> >

> >> -----Mensaje original-----

> >> De:  <mailto:tcmtf-bounces@ietf.org> tcmtf-bounces@ietf.org [
<mailto:tcmtf-bounces@ietf.org> mailto:tcmtf-bounces@ietf.org] En nombre

> >> de Luigi Iannone Enviado el: mi=E9rcoles, 10 de octubre de 2012 =
10:23

> >> Para:  <mailto:jsaldana@unizar.es> jsaldana@unizar.es

> >> CC:  <mailto:tcmtf@ietf.org> tcmtf@ietf.org

> >> Asunto: Re: [tcmtf] TCMTF: two kinds of services

> >>

> >> Hi All,

> >>

> >> On 10 Oct. 2012, at 09:58 , Jose Saldana < =
<mailto:jsaldana@unizar.es>
jsaldana@unizar.es> wrote:

> >>

> >>> - Tunneling will be used to send the multiplexed packets =
end-to-end.

> >>> The options in this layer are L2TP, GRE and MPLS.

> >>>

> >>

> >> I was wondering if the group might be interested in exploring also

> >> other

> > form

> >> of tunnelling, e.g., LISP.

> >>

> >> Obviously, since LISP is an experimental effort, it cannot be =
tagged

> >> as

> > "best

> >> current practice" and included in document (A).

> >>

> >> However, the group may have a slightly "larger" scope and include

> >> alternative forms of tunnelling (and/or multiplexing and/or header

> >> compression) (may be documented separately).

> >>

> >> Thoughts?

> >>

> >> ciao

> >>

> >> Luigi

> >>

> >>

> >>

> >> _______________________________________________

> >> tcmtf mailing list

> >>  <mailto:tcmtf@ietf.org> tcmtf@ietf.org

> >>  <https://www.ietf.org/mailman/listinfo/tcmtf>
https://www.ietf.org/mailman/listinfo/tcmtf

> >

>=20

> _______________________________________________

> tcmtf mailing list

>  <mailto:tcmtf@ietf.org> tcmtf@ietf.org

>  <https://www.ietf.org/mailman/listinfo/tcmtf>
https://www.ietf.org/mailman/listinfo/tcmtf


------=_NextPart_000_00D8_01CDAE24.2F1603C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texto de globo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	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";}
.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 129.75pt 70.85pt 129.7pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New"'>Luigi,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier New"'>What about this =
protocol stack for LISP within TCMTF?<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New"'>(to be seen in Courier letters)<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier New"'>=A0=A0=A0 TCP/IP=A0=A0 =
UDP/IP=A0 RTP/UDP/IP<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New"'>=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"'>=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"'>=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"'>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"'>=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"'>=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"'>=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"'>=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"'>=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"'>=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"'>=A0=A0=A0=A0=A0=A0=A0=A0 /=A0 =A0=A0LISP =
=A0=A0=A0=A0\<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier New"'>=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"'>GRE or L2TP=A0=A0 UDP =
=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=A0tunneling layer<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New"'>=A0=A0=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0 | =
=A0=A0=A0=A0=A0=A0=A0MPLS<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New"'>=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"'>=A0=A0=A0=A0=A0=A0 =
IP=A0=A0=A0=A0=A0 IP<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier New"'>I don&#8217;t know if =
LISP could be included into TCMTF draft. What do you think? Should it be =
defined inside the LISP WG?<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier New"'>We have to talk about =
that LISP signaling which could be used in TCMTF, as you =
say.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Courier =
New"'>Thanks,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New"'>Jose<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; </span><span =
style=3D'font-family:"Courier New";mso-fareast-language:ES'>-----Mensaje =
original-----</span><span style=3D'font-family:"Courier =
New"'><o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; </span><span =
style=3D'font-family:"Courier New";mso-fareast-language:ES'>De: =
tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de</span><span style=3D'font-family:"Courier =
New"'><o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; </span><span =
style=3D'font-family:"Courier New";mso-fareast-language:ES'>Luigi =
Iannone</span><span style=3D'font-family:"Courier =
New"'><o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; </span><span =
style=3D'font-family:"Courier New";mso-fareast-language:ES'>Enviado el: =
jueves, 11 de octubre de 2012 9:11</span><span =
style=3D'font-family:"Courier New"'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
</span><span style=3D'font-family:"Courier =
New";mso-fareast-language:ES'>Para: jsaldana@unizar.es</span><span =
style=3D'font-family:"Courier New"'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
</span><span style=3D'font-family:"Courier =
New";mso-fareast-language:ES'>CC: tcmtf@ietf.org</span><span =
style=3D'font-family:"Courier New"'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
</span><span style=3D'font-family:"Courier =
New";mso-fareast-language:ES'>Asunto: Re: [tcmtf] TCMTF: two kinds of =
services</span><span style=3D'font-family:"Courier =
New"'><o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; <o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; Hi =
Jose,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; <o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; I =
would put LISP in two different layers.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; You can consider LISP as =
composed of two main parts:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; 1. the encap/decap operations =
(i.e., the tunnelling)<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; 2. the mapping system =
(basically controlling which traffic is =
tunnelled).<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; <o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; The =
first can be used=A0 at the tunnelling layer, beside GRE/MPLS/L2TP =
(having<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; multiple options is always a =
good thing ;-) ), to perform the tunnelling. =
Some<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; parts of the LISP header might =
be exploited to carry TE information (e.g., the<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
Instance ID can be used as QoS tag).<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; The second can be used at =
Mux/Demux layer. The LISP mapping system<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
might be extended to perform tcmtf negotiation by=A0 leveraging on =
a<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; particular form of mappings. =
The advantage is that there is already quite a =
bit<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; of signalling machinery out =
there that can be easily re-used/extended.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; Ciao<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; Luigi<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; <o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; On =
10 Oct. 2012, at 13:48 , Jose Saldana &lt;<a =
href=3D"mailto:jsaldana@unizar.es"><span =
style=3D'color:windowtext;text-decoration:none'>jsaldana@unizar.es</span>=
</a>&gt; wrote:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; <o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; &gt; =
Luigi,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; &gt; =
Where would you include LISP here? With GRE/L2TP, or with =
MPLS?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; &gt; =
We are also thinking about including other tunneling schemes, as =
VLAN,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; etc.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt; (to be seen in Courier =
letters)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;=A0=A0=A0 TCP/IP=A0=A0 UDP/IP=A0 RTP/UDP/IP<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;=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 =
style=3D'font-family:"Courier New"'>&gt; &gt;=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 style=3D'font-family:"Courier New"'>&gt; =
&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 \=A0=A0 |=A0=A0 =
/<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt; 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 =
style=3D'font-family:"Courier New"'>&gt; =
&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;=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 style=3D'font-family:"Courier New"'>&gt; =
&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;=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 =
style=3D'font-family:"Courier New"'>&gt; =
&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;=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 style=3D'font-family:"Courier New"'>&gt; =
&gt;=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0/=A0=A0 =
\<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; =
&gt;=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 =
style=3D'font-family:"Courier New"'>&gt; &gt;=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 style=3D'font-family:"Courier New"'>&gt; =
&gt;=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 =
style=3D'font-family:"Courier New"'>&gt; &gt;=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 style=3D'font-family:"Courier New"'>&gt; =
&gt;=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"'>&gt; =
&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt; =
Thanks,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; &gt; =
Jose<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt; -----Mensaje original-----<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt; De: <a href=3D"mailto:tcmtf-bounces@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>tcmtf-bounces@ietf.org</s=
pan></a> [<a href=3D"mailto:tcmtf-bounces@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:tcmtf-bounces@ietf=
.org</span></a>] En nombre<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt; de Luigi Iannone Enviado el: mi=E9rcoles, 10 de octubre de 2012 =
10:23<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; Para: <a =
href=3D"mailto:jsaldana@unizar.es"><span =
style=3D'color:windowtext;text-decoration:none'>jsaldana@unizar.es</span>=
</a><o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; CC: <a =
href=3D"mailto:tcmtf@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>tcmtf@ietf.org</span></a>=
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; Asunto: Re: [tcmtf] =
TCMTF: two kinds of services<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; Hi =
All,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; On 10 Oct. 2012, at =
09:58 , Jose Saldana &lt;<a href=3D"mailto:jsaldana@unizar.es"><span =
style=3D'color:windowtext;text-decoration:none'>jsaldana@unizar.es</span>=
</a>&gt; wrote:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt;&gt; - Tunneling will =
be used to send the multiplexed packets =
end-to-end.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt;&gt; The options in =
this layer are L2TP, GRE and MPLS.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; I was wondering if the =
group might be interested in exploring also<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt; other<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt; =
form<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; of tunnelling, e.g., =
LISP.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; Obviously, since LISP =
is an experimental effort, it cannot be tagged<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt; as<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt; =
&quot;best<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; current practice&quot; =
and included in document (A).<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; However, the group may =
have a slightly &quot;larger&quot; scope and =
include<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; alternative forms of =
tunnelling (and/or multiplexing and/or header<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt; compression) (may be documented =
separately).<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; =
Thoughts?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; =
ciao<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; =
Luigi<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; =
_______________________________________________<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt; tcmtf mailing list<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;&gt; <a href=3D"mailto:tcmtf@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>tcmtf@ietf.org</span></a>=
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; &gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/tcmtf"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/tcmtf</span></a><o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
&gt;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; <o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
_______________________________________________<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier New"'>&gt; =
tcmtf mailing list<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; <a =
href=3D"mailto:tcmtf@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>tcmtf@ietf.org</span></a>=
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/tcmtf"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/tcmtf</span></a><o:p></o:p></span></p></div></body></html>
------=_NextPart_000_00D8_01CDAE24.2F1603C0--


From ggx@gigix.net  Sun Oct 21 07:10:04 2012
Return-Path: <ggx@gigix.net>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDF3921F847C for <tcmtf@ietfa.amsl.com>; Sun, 21 Oct 2012 07:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.598
X-Spam-Level: 
X-Spam-Status: No, score=-5.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R-ZI4zWD-En4 for <tcmtf@ietfa.amsl.com>; Sun, 21 Oct 2012 07:10:02 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 1195021F8466 for <tcmtf@ietf.org>; Sun, 21 Oct 2012 07:10:01 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hr7so1371844wib.13 for <tcmtf@ietf.org>; Sun, 21 Oct 2012 07:10:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=D9U4AZDQ7tEhqR05yfN4bgF/MsOIzbVqa//We61TRhw=; b=A2B3UXHnAgHG846X95SH/76hp0JlEmAzb4GnQs01Ovqc9edba77MN9UfrpVirlCzAA uCn+xsHDxbS3hazAozsSDEYX2qs5BB39/1nUHYxofdWgBsuOugzr0VU0h1yBVqD7t5XW O9wnYHs0yIUgUHBWKRI9qsDAcqXkdDNthFttGbLa8/a/fr8m8nm0T9uazn6Mx7vTDcBY h5mbQ10TYR9bwYhk70pUF/7gohzJZlkVdfKHSSDVHeLPLUV2pLorCepYbtJeYNYL9yam 167FWs6MKYOvnViCIN0+tXFB1vbG9M8d0iQiBE6nEKfeaszVA/5HjdovOqH8ic0qPs5U I1lw==
Received: by 10.180.24.4 with SMTP id q4mr30800827wif.19.1350828601152; Sun, 21 Oct 2012 07:10:01 -0700 (PDT)
Received: from [192.168.0.43] (bny92-2-81-56-19-67.fbx.proxad.net. [81.56.19.67]) by mx.google.com with ESMTPS id k20sm46132043wiv.11.2012.10.21.07.09.59 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 21 Oct 2012 07:10:00 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_8FA303AD-9361-4812-BD0C-26583A84ACF8"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <00d701cdae13$6b8b5f00$42a21d00$@unizar.es>
Date: Sun, 21 Oct 2012 16:13:41 +0200
Message-Id: <814C798C-6C32-4378-BA8D-9FA2EA8B8C39@gigix.net>
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es>	<201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de>	<002001cda62b$f6e63920$e4b2ab60$@unizar.es>	<201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de>	<000d01cda6bd$07331370$15993a50$@unizar.es>	<08DEAFED-C1BC-45E3-B2C9-C9879145FC4B@gigix.net>	<002001cda6dd$1f30d690$5d9283b0$@unizar.es> <C62762CA-C668-4758-B72B-20E5CDB634E0@gigix.net> <00d701cdae13$6b8b5f00$42a21d00$@unizar.es>
To: <jsaldana@unizar.es>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQm1lvTe3dJD91QCUsZ/zTZvVyn/Zb9u6k2FelF60MHMvl/SuNbip0NtcctuqbzTJIN7Mu3W
Cc: tcmtf@ietf.org, lisp@ietf.org
Subject: Re: [tcmtf] TCMTF: two kinds of services
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: Sun, 21 Oct 2012 14:10:04 -0000

--Apple-Mail=_8FA303AD-9361-4812-BD0C-26583A84ACF8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi Jose,

comments inline.


On 19 Oct. 2012, at 18:04 , Jose Saldana <jsaldana@unizar.es> wrote:

> Luigi,
> =20
> What about this protocol stack for LISP within TCMTF?
> (to be seen in Courier letters)
> =20
>     TCP/IP   UDP/IP  RTP/UDP/IP
>          \     |     /
>           \    |    /                     =
------------------------------
>            \   |   /
> Nothing or ROHC or ECRTP or IPHC             header compressing layer
>                |
>                |                          =
------------------------------
>                |
>    PPPMUX or other mux protocols                multiplexing layer
>            /   |     \
>           /    |      \                   =
------------------------------
>          /    LISP     \
>         /      |        \
> GRE or L2TP   UDP        \                        tunneling layer
>        |       |        MPLS
>        |       |                           =
------------------------------
>        IP      IP
> =20
> =20
> I don=92t know if LISP could be included into TCMTF draft. What do you =
think?

The graph looks good to me.

Concerning whether or not to include it in the draft, may be it is not =
necessary to include details about LISP just mention that can be used. =
The usage of LISP, because of its experimental nature compare to other =
tunnelling options, can be documented in a different document, which, if =
people are interested, I can (with your help) write.


> Should it be defined inside the LISP WG?
> =20

I`ll let the LISP WG chairs answer on this point.
Nevertheless, IMHO,  the LISP WG is chartered for the main spec. Other =
usages of LISP can be discussed in other, more pertinent, WGs. Obviously =
some form of collaboration will be necessary at least to make the LISP =
WG aware of how other WGs plan to use LISP.

> We have to talk about that LISP signaling which could be used in =
TCMTF, as you say.

As I said before, these details can be documented elsewhere. If LISP is =
mentioned in the main draft, then it can also be stated that the re-use =
of the LISP signalling machinery in the context of TCMTF is explored in =
a different document.

ciao

L.


> =20
> Thanks,
> =20
> Jose
> =20
> > -----Mensaje original-----
> > De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> > Luigi Iannone
> > Enviado el: jueves, 11 de octubre de 2012 9:11
> > Para: jsaldana@unizar.es
> > CC: tcmtf@ietf.org
> > Asunto: Re: [tcmtf] TCMTF: two kinds of services
> >
> > Hi Jose,
> >
> > I would put LISP in two different layers.
> >
> > You can consider LISP as composed of two main parts:
> >
> > 1. the encap/decap operations (i.e., the tunnelling)
> >
> > 2. the mapping system (basically controlling which traffic is =
tunnelled).
> >
> > The first can be used  at the tunnelling layer, beside GRE/MPLS/L2TP =
(having
> > multiple options is always a good thing ;-) ), to perform the =
tunnelling. Some
> > parts of the LISP header might be exploited to carry TE information =
(e.g., the
> > Instance ID can be used as QoS tag).
> >
> > The second can be used at Mux/Demux layer. The LISP mapping system
> > might be extended to perform tcmtf negotiation by  leveraging on a
> > particular form of mappings. The advantage is that there is already =
quite a bit
> > of signalling machinery out there that can be easily =
re-used/extended.
> >
> > Ciao
> >
> > Luigi
> >
> >
> > On 10 Oct. 2012, at 13:48 , Jose Saldana <jsaldana@unizar.es> wrote:
> >
> > > Luigi,
> > >
> > > Where would you include LISP here? With GRE/L2TP, or with MPLS?
> > >
> > > We are also thinking about including other tunneling schemes, as =
VLAN,
> > etc.
> > >
> > > (to be seen in Courier letters)
> > >
> > >    TCP/IP   UDP/IP  RTP/UDP/IP
> > >         \     |     /
> > >          \    |    /                     =
------------------------------
> > >           \   |   /
> > > Nothing or ROHC or ECRTP or IPHC             header compressing =
layer
> > >               |
> > >               |                          =
------------------------------
> > >               |
> > >   PPPMUX or other mux protocols                multiplexing layer
> > >               |
> > >              / \                         =
------------------------------
> > >             /   \
> > >            /     \
> > >   GRE or L2TP     \                              tunneling layer
> > >          |        MPLS
> > >          |                               =
------------------------------
> > >          IP
> > >
> > > Thanks,
> > >
> > > Jose
> > >
> > >> -----Mensaje original-----
> > >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> > >> de Luigi Iannone Enviado el: mi=E9rcoles, 10 de octubre de 2012 =
10:23
> > >> Para: jsaldana@unizar.es
> > >> CC: tcmtf@ietf.org
> > >> Asunto: Re: [tcmtf] TCMTF: two kinds of services
> > >>
> > >> Hi All,
> > >>
> > >> On 10 Oct. 2012, at 09:58 , Jose Saldana <jsaldana@unizar.es> =
wrote:
> > >>
> > >>> - Tunneling will be used to send the multiplexed packets =
end-to-end.
> > >>> The options in this layer are L2TP, GRE and MPLS.
> > >>>
> > >>
> > >> I was wondering if the group might be interested in exploring =
also
> > >> other
> > > form
> > >> of tunnelling, e.g., LISP.
> > >>
> > >> Obviously, since LISP is an experimental effort, it cannot be =
tagged
> > >> as
> > > "best
> > >> current practice" and included in document (A).
> > >>
> > >> However, the group may have a slightly "larger" scope and include
> > >> alternative forms of tunnelling (and/or multiplexing and/or =
header
> > >> compression) (may be documented separately).
> > >>
> > >> Thoughts?
> > >>
> > >> ciao
> > >>
> > >> Luigi
> > >>
> > >>
> > >>
> > >> _______________________________________________
> > >> tcmtf mailing list
> > >> tcmtf@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/tcmtf
> > >
> >
> > _______________________________________________
> > tcmtf mailing list
> > tcmtf@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcmtf


--Apple-Mail=_8FA303AD-9361-4812-BD0C-26583A84ACF8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"><base href=3D"x-msg://1452/"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Hi =
Jose,<div><br></div><div>comments =
inline.</div><div><br></div><div><br><div><div>On 19 Oct. 2012, at 18:04 =
, Jose Saldana &lt;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div lang=3D"ES" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; ">Luigi,<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" style=3D"font-family: 'Courier New'; =
">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-family: 'Courier New'; ">What about this protocol stack =
for LISP within TCMTF?<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" style=3D"font-family: 'Courier New'; ">(to be seen in =
Courier letters)<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" style=3D"font-family: 'Courier New'; =
">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-family: 'Courier New'; ">&nbsp;&nbsp;&nbsp; =
TCP/IP&nbsp;&nbsp; UDP/IP&nbsp; RTP/UDP/IP<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
\&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; =
/<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-family: 'Courier New'; =
">&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></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
\&nbsp;&nbsp; |&nbsp;&nbsp; /<o:p></o:p></span></div><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span lang=3D"EN-US" style=3D"font-family: 'Courier New'; ">Nothing or =
ROHC or ECRTP or =
IPHC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; header compressing layer<o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span lang=3D"EN-US" style=3D"font-family: 'Courier New'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; |<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" style=3D"font-family: 'Courier New'; =
">&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;&nb=
sp; ------------------------------<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; |<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" style=3D"font-family: 'Courier New'; ">&nbsp;&nbsp; =
PPPMUX or other mux =
protocols&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; multiplexing layer<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
/&nbsp;&nbsp; | &nbsp;&nbsp;&nbsp;&nbsp;\<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; ">&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></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
/&nbsp; &nbsp;&nbsp;LISP =
&nbsp;&nbsp;&nbsp;&nbsp;\<o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span lang=3D"EN-US" style=3D"font-family: 'Courier New'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; ">GRE or L2TP&nbsp;&nbsp; UDP =
&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></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-family: 'Courier New'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MPLS<o:p></o:p></span></div><div=
 style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; ">&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;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;----------------------------=
--<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-family: 'Courier New'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
IP<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-family: 'Courier New'; ">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; ">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" style=3D"font-family: 'Courier New'; ">I don=92t know if =
LISP could be included into TCMTF draft. What do you =
think?</span></div></div></div></blockquote><div><br></div><div>The =
graph looks good to me.</div><div><br></div><div>Concerning whether or =
not to include it in the draft, may be it is not necessary to include =
details about LISP just mention that can be used. The usage of LISP, =
because of its experimental nature compare to other tunnelling options, =
can be documented in a different document, which, if people are =
interested, I can (with your help) =
write.</div><div><br></div><br><blockquote type=3D"cite"><div lang=3D"ES" =
link=3D"blue" vlink=3D"purple" style=3D"font-family: Helvetica; =
font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div =
class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; "> Should it be defined inside the LISP =
WG?<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-family: 'Courier New'; =
">&nbsp;</span></div></div></div></blockquote><div><br></div><div>I`ll =
let the LISP WG chairs answer on this point.</div><div>Nevertheless, =
IMHO, &nbsp;the LISP WG is chartered for the main spec. Other usages of =
LISP can be discussed in other, more pertinent, WGs. Obviously some form =
of collaboration will be necessary at least to make the LISP WG aware of =
how other WGs plan to use LISP.</div><div><br></div><blockquote =
type=3D"cite"><div lang=3D"ES" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; ">We have to talk about that LISP signaling which could =
be used in TCMTF, as you =
say.</span></div></div></div></blockquote><div><br></div><div>As I said =
before, these details can be documented elsewhere. If LISP is mentioned =
in the main draft, then it can also be stated that the re-use of the =
LISP signalling machinery in the context of TCMTF is explored in a =
different =
document.</div><div><br></div><div>ciao</div><div><br></div><div>L.</div><=
div><br></div><br><blockquote type=3D"cite"><div lang=3D"ES" link=3D"blue"=
 vlink=3D"purple" style=3D"font-family: Helvetica; font-size: medium; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; "><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-family: 'Courier New'; "><o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; ">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" style=3D"font-family: 'Courier New'; =
">Thanks,<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-family: 'Courier New'; ">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"font-family: =
'Courier New'; ">Jose<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" style=3D"font-family: 'Courier New'; =
">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"font-family: =
'Courier New'; ">&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-family: 'Courier New'; ">-----Mensaje =
original-----</span><span style=3D"font-family: 'Courier New'; =
"><o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-family: 'Courier New'; ">De:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:tcmtf-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline; ">tcmtf-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[mailto:tcmtf-<a =
href=3D"mailto:bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline; ">bounces@ietf.org</a>] En nombre =
de</span><span style=3D"font-family: 'Courier New'; =
"><o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-family: 'Courier New'; ">Luigi Iannone</span><span =
style=3D"font-family: 'Courier New'; "><o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; =
">&gt;<span class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-family: 'Courier New'; ">Enviado el: jueves, 11 de octubre =
de 2012 9:11</span><span style=3D"font-family: 'Courier New'; =
"><o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-family: 'Courier New'; ">Para:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:jsaldana@unizar.es" style=3D"color: purple; =
text-decoration: underline; ">jsaldana@unizar.es</a></span><span =
style=3D"font-family: 'Courier New'; "><o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; =
">&gt;<span class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-family: 'Courier New'; ">CC:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:tcmtf@ietf.org" style=3D"color: purple; text-decoration: =
underline; ">tcmtf@ietf.org</a></span><span style=3D"font-family: =
'Courier New'; "><o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-family: 'Courier New'; ">Asunto: Re: [tcmtf] TCMTF: two =
kinds of services</span><span style=3D"font-family: 'Courier New'; =
"><o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
Hi Jose,<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
I would put LISP in two different layers.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; =
">&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; You can consider LISP as =
composed of two main parts:<o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-family: 'Courier New'; =
">&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; 1. the encap/decap =
operations (i.e., the tunnelling)<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; =
">&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; 2. the mapping system =
(basically controlling which traffic is =
tunnelled).<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
The first can be used&nbsp; at the tunnelling layer, beside =
GRE/MPLS/L2TP (having<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; multiple options is always a =
good thing ;-) ), to perform the tunnelling. =
Some<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; parts of the LISP header =
might be exploited to carry TE information (e.g., =
the<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; Instance ID can be used as =
QoS tag).<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
The second can be used at Mux/Demux layer. The LISP mapping =
system<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; might be extended to perform =
tcmtf negotiation by&nbsp; leveraging on a<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
particular form of mappings. The advantage is that there is already =
quite a bit<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; of signalling machinery out =
there that can be easily re-used/extended.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; =
">&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
Ciao<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
Luigi<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; =
">&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; On 10 Oct. 2012, at 13:48 , =
Jose Saldana &lt;<a href=3D"mailto:jsaldana@unizar.es" style=3D"color: =
purple; text-decoration: underline; "><span style=3D"color: windowtext; =
text-decoration: none; ">jsaldana@unizar.es</span></a>&gt; =
wrote:<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt; Luigi,<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt; Where would you include =
LISP here? With GRE/L2TP, or with MPLS?<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt; We are also thinking =
about including other tunneling schemes, as =
VLAN,<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
etc.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt; (to be seen in Courier =
letters)<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&nbsp;&nbsp;&nbsp; =
TCP/IP&nbsp;&nbsp; UDP/IP&nbsp; RTP/UDP/IP<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
\&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; =
/<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&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></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
\&nbsp;&nbsp; |&nbsp;&nbsp; /<o:p></o:p></span></div><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-family: 'Courier New'; ">&gt; &gt; Nothing or ROHC =
or ECRTP or =
IPHC&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; header compressing layer<o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; |<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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;&nb=
sp; ------------------------------<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; |<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&nbsp;&nbsp; PPPMUX or =
other mux =
protocols&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; multiplexing layer<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; |<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&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></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;/&nbsp;&nbsp; =
\<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
/&nbsp;&nbsp;&nbsp;&nbsp; \<o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-family: 'Courier New'; ">&gt; &gt;&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;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; tunneling layer<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MPLS<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&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;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
------------------------------<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
IP<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt; =
Thanks,<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt; =
Jose<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; -----Mensaje =
original-----<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; De:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:tcmtf-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline; "><span style=3D"color: windowtext; =
text-decoration: none; ">tcmtf-bounces@ietf.org</span></a><span =
class=3D"Apple-converted-space">&nbsp;</span>[<a =
href=3D"mailto:tcmtf-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline; "><span style=3D"color: windowtext; =
text-decoration: none; ">mailto:tcmtf-bounces@ietf.org</span></a>] En =
nombre<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; de Luigi Iannone =
Enviado el: mi=E9rcoles, 10 de octubre de 2012 =
10:23<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; Para:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:jsaldana@unizar.es" style=3D"color: purple; =
text-decoration: underline; "><span style=3D"color: windowtext; =
text-decoration: none; =
">jsaldana@unizar.es</span></a><o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt; CC:<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:tcmtf@ietf.org" style=3D"color: purple; text-decoration: =
underline; "><span style=3D"color: windowtext; text-decoration: none; =
">tcmtf@ietf.org</span></a><o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; Asunto: Re: =
[tcmtf] TCMTF: two kinds of services<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; Hi =
All,<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; On 10 Oct. 2012, at =
09:58 , Jose Saldana &lt;<a href=3D"mailto:jsaldana@unizar.es" =
style=3D"color: purple; text-decoration: underline; "><span =
style=3D"color: windowtext; text-decoration: none; =
">jsaldana@unizar.es</span></a>&gt; wrote:<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt;&gt; - Tunneling =
will be used to send the multiplexed packets =
end-to-end.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt;&gt; The options in =
this layer are L2TP, GRE and MPLS.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; I was wondering if =
the group might be interested in exploring =
also<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; =
other<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt; =
form<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; of tunnelling, =
e.g., LISP.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; Obviously, since =
LISP is an experimental effort, it cannot be =
tagged<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; =
as<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt; =
"best<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; current practice" =
and included in document (A).<o:p></o:p></span></div><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; However, the group =
may have a slightly "larger" scope and =
include<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; alternative forms =
of tunnelling (and/or multiplexing and/or =
header<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; compression) (may =
be documented separately).<o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; =
Thoughts?<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; =
ciao<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; =
Luigi<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt; =
_______________________________________________<o:p></o:p></span></div><di=
v style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
&gt;&gt; tcmtf mailing list<o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:tcmtf@ietf.org" style=3D"color: purple; text-decoration: =
underline; "><span style=3D"color: windowtext; text-decoration: none; =
">tcmtf@ietf.org</span></a><o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-family: 'Courier New'; ">&gt; &gt;&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color: =
purple; text-decoration: underline; "><span style=3D"color: windowtext; =
text-decoration: none; =
">https://www.ietf.org/mailman/listinfo/tcmtf</span></a><o:p></o:p></span>=
</div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; "><span style=3D"font-family: 'Courier =
New'; ">&gt; &gt;<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
_______________________________________________<o:p></o:p></span></div><di=
v style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"font-family: 'Courier New'; ">&gt; =
tcmtf mailing list<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"font-family: 'Courier New'; ">&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:tcmtf@ietf.org" style=3D"color: purple; text-decoration: =
underline; "><span style=3D"color: windowtext; text-decoration: none; =
">tcmtf@ietf.org</span></a><o:p></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"font-family: 'Courier New'; ">&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color: =
purple; text-decoration: underline; "><span style=3D"color: windowtext; =
text-decoration: none; =
">https://www.ietf.org/mailman/listinfo/tcmtf</span></a></span></div></div=
></div></blockquote></div><br></div></body></html>=

--Apple-Mail=_8FA303AD-9361-4812-BD0C-26583A84ACF8--

From jmh@joelhalpern.com  Sun Oct 21 11:56:11 2012
Return-Path: <jmh@joelhalpern.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 DF99F21F8917; Sun, 21 Oct 2012 11:56:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.135
X-Spam-Level: 
X-Spam-Status: No, score=-103.135 tagged_above=-999 required=5 tests=[AWL=1.130, BAYES_00=-2.599, GB_I_LETTER=-2, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M6TlLrwmubA2; Sun, 21 Oct 2012 11:56:11 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 16E5B21F889F; Sun, 21 Oct 2012 11:56:11 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id C6DF5A395C; Sun, 21 Oct 2012 11:56:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 8F6F41BD7EA8; Sun, 21 Oct 2012 11:56:08 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-51-221.clppva.btas.verizon.net [71.161.51.221]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 23C711BD7E58; Sun, 21 Oct 2012 11:56:06 -0700 (PDT)
Message-ID: <50844544.9020200@joelhalpern.com>
Date: Sun, 21 Oct 2012 14:56:04 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Luigi Iannone <ggx@gigix.net>
References: <000e01cd9d5a$0e3f2850$2abd78f0$@unizar.es>	<201210091424.17349.mirja.kuehlewind@ikr.uni-stuttgart.de>	<002001cda62b$f6e63920$e4b2ab60$@unizar.es>	<201210091802.04459.mirja.kuehlewind@ikr.uni-stuttgart.de>	<000d01cda6bd$07331370$15993a50$@unizar.es>	<08DEAFED-C1BC-45E3-B2C9-C9879145FC4B@gigix.net>	<002001cda6dd$1f30d690$5d9283b0$@unizar.es> <C62762CA-C668-4758-B72B-20E5CDB634E0@gigix.net> <00d701cdae13$6b8b5f00$42a21d00$@unizar.es> <814C798C-6C32-4378-BA8D-9FA2EA8B8C39@gigix.net>
In-Reply-To: <814C798C-6C32-4378-BA8D-9FA2EA8B8C39@gigix.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: tcmtf@ietf.org, lisp@ietf.org, jsaldana@unizar.es
Subject: Re: [tcmtf] [lisp]  TCMTF: two kinds of services
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: Sun, 21 Oct 2012 18:56:12 -0000

As a general comment from a chair, a document which references LISP does 
not need to be done in he LISP WG.  (Telling us about it is 
appreciated.)  A document which defines how to use LISP to do something 
needs to be coordinated with the LISP WG.

Yours,
Joel

On 10/21/2012 10:13 AM, Luigi Iannone wrote:
> Hi Jose,
>
> comments inline.
>
>
> On 19 Oct. 2012, at 18:04 , Jose Saldana <jsaldana@unizar.es
> <mailto:jsaldana@unizar.es>> wrote:
>
>> Luigi,
>> What about this protocol stack for LISP within TCMTF?
>> (to be seen in Courier letters)
>>     TCP/IP   UDP/IP  RTP/UDP/IP
>>          \     |     /
>>           \    |    /                     ------------------------------
>>            \   |   /
>> Nothing or ROHC or ECRTP or IPHC             header compressing layer
>>                |
>>                |                          ------------------------------
>>                |
>>    PPPMUX or other mux protocols                multiplexing layer
>>            /   |     \
>>           /    |      \                   ------------------------------
>>          /    LISP     \
>>         /      |        \
>> GRE or L2TP   UDP        \                        tunneling layer
>>        |       |        MPLS
>>        |       |                           ------------------------------
>>        IP      IP
>> I don’t know if LISP could be included into TCMTF draft. What do you
>> think?
>
> The graph looks good to me.
>
> Concerning whether or not to include it in the draft, may be it is not
> necessary to include details about LISP just mention that can be used.
> The usage of LISP, because of its experimental nature compare to other
> tunnelling options, can be documented in a different document, which, if
> people are interested, I can (with your help) write.
>
>
>> Should it be defined inside the LISP WG?
>
> I`ll let the LISP WG chairs answer on this point.
> Nevertheless, IMHO,  the LISP WG is chartered for the main spec. Other
> usages of LISP can be discussed in other, more pertinent, WGs. Obviously
> some form of collaboration will be necessary at least to make the LISP
> WG aware of how other WGs plan to use LISP.
>
>> We have to talk about that LISP signaling which could be used in
>> TCMTF, as you say.
>
> As I said before, these details can be documented elsewhere. If LISP is
> mentioned in the main draft, then it can also be stated that the re-use
> of the LISP signalling machinery in the context of TCMTF is explored in
> a different document.
>
> ciao
>
> L.
>
>
>> Thanks,
>> Jose
>> >-----Mensaje original-----
>> >De:tcmtf-bounces@ietf.org
>> <mailto:tcmtf-bounces@ietf.org>[mailto:tcmtf-bounces@ietf.org
>> <mailto:bounces@ietf.org>] En nombre de
>> >Luigi Iannone
>> >Enviado el: jueves, 11 de octubre de 2012 9:11
>> >Para:jsaldana@unizar.es <mailto:jsaldana@unizar.es>
>> >CC:tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >Asunto: Re: [tcmtf] TCMTF: two kinds of services
>> >
>> > Hi Jose,
>> >
>> > I would put LISP in two different layers.
>> >
>> > You can consider LISP as composed of two main parts:
>> >
>> > 1. the encap/decap operations (i.e., the tunnelling)
>> >
>> > 2. the mapping system (basically controlling which traffic is tunnelled).
>> >
>> > The first can be used  at the tunnelling layer, beside GRE/MPLS/L2TP (having
>> > multiple options is always a good thing ;-) ), to perform the tunnelling. Some
>> > parts of the LISP header might be exploited to carry TE information (e.g., the
>> > Instance ID can be used as QoS tag).
>> >
>> > The second can be used at Mux/Demux layer. The LISP mapping system
>> > might be extended to perform tcmtf negotiation by  leveraging on a
>> > particular form of mappings. The advantage is that there is already quite a bit
>> > of signalling machinery out there that can be easily re-used/extended.
>> >
>> > Ciao
>> >
>> > Luigi
>> >
>> >
>> > On 10 Oct. 2012, at 13:48 , Jose Saldana <jsaldana@unizar.es <mailto:jsaldana@unizar.es>> wrote:
>> >
>> > > Luigi,
>> > >
>> > > Where would you include LISP here? With GRE/L2TP, or with MPLS?
>> > >
>> > > We are also thinking about including other tunneling schemes, as VLAN,
>> > etc.
>> > >
>> > > (to be seen in Courier letters)
>> > >
>> > >    TCP/IP   UDP/IP  RTP/UDP/IP
>> > >         \     |     /
>> > >          \    |    /                     ------------------------------
>> > >           \   |   /
>> > > Nothing or ROHC or ECRTP or IPHC             header compressing layer
>> > >               |
>> > >               |                          ------------------------------
>> > >               |
>> > >   PPPMUX or other mux protocols                multiplexing layer
>> > >               |
>> > >              / \                         ------------------------------
>> > >             /   \
>> > >            /     \
>> > >   GRE or L2TP     \                              tunneling layer
>> > >          |        MPLS
>> > >          |                               ------------------------------
>> > >          IP
>> > >
>> > > Thanks,
>> > >
>> > > Jose
>> > >
>> > >> -----Mensaje original-----
>> > >> De:tcmtf-bounces@ietf.org
>> <mailto:tcmtf-bounces@ietf.org>[mailto:tcmtf-bounces@ietf.org] En nombre
>> > >> de Luigi Iannone Enviado el: miércoles, 10 de octubre de 2012 10:23
>> > >> Para:jsaldana@unizar.es <mailto:jsaldana@unizar.es>
>> > >> CC:tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> > >> Asunto: Re: [tcmtf] TCMTF: two kinds of services
>> > >>
>> > >> Hi All,
>> > >>
>> > >> On 10 Oct. 2012, at 09:58 , Jose Saldana <jsaldana@unizar.es <mailto:jsaldana@unizar.es>> wrote:
>> > >>
>> > >>> - Tunneling will be used to send the multiplexed packets end-to-end.
>> > >>> The options in this layer are L2TP, GRE and MPLS.
>> > >>>
>> > >>
>> > >> I was wondering if the group might be interested in exploring also
>> > >> other
>> > > form
>> > >> of tunnelling, e.g., LISP.
>> > >>
>> > >> Obviously, since LISP is an experimental effort, it cannot be tagged
>> > >> as
>> > > "best
>> > >> current practice" and included in document (A).
>> > >>
>> > >> However, the group may have a slightly "larger" scope and include
>> > >> alternative forms of tunnelling (and/or multiplexing and/or header
>> > >> compression) (may be documented separately).
>> > >>
>> > >> Thoughts?
>> > >>
>> > >> ciao
>> > >>
>> > >> Luigi
>> > >>
>> > >>
>> > >>
>> > >> _______________________________________________
>> > >> tcmtf mailing list
>> > >>tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> > >>https://www.ietf.org/mailman/listinfo/tcmtf
>> > >
>> >
>> > _______________________________________________
>> > tcmtf mailing list
>> >tcmtf@ietf.org <mailto:tcmtf@ietf.org>
>> >https://www.ietf.org/mailman/listinfo/tcmtf
>
>
>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
>

From Mirko.Suznjevic@fer.hr  Tue Oct 23 01:14:25 2012
Return-Path: <Mirko.Suznjevic@fer.hr>
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 8B7C921F8512 for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 01:14:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LgbB9BaRbmjE for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 01:14:25 -0700 (PDT)
Received: from mail.zvne.fer.hr (mail.zvne.fer.hr [161.53.66.5]) by ietfa.amsl.com (Postfix) with ESMTP id 49FCD21F85B2 for <tcmtf@ietf.org>; Tue, 23 Oct 2012 01:14:23 -0700 (PDT)
Received: from munja.zvne.fer.hr (161.53.66.248) by mail.zvne.fer.hr (161.53.66.5) with Microsoft SMTP Server id 14.2.298.4; Tue, 23 Oct 2012 10:14:20 +0200
Received: from sluga.fer.hr ([161.53.66.244]) by munja.zvne.fer.hr with Microsoft SMTPSVC(6.0.3790.4675);	 Tue, 23 Oct 2012 10:14:20 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 23 Oct 2012 10:14:19 +0200
Message-ID: <A3179A2C9AAEE647BE70AC4C7881D5FB0167E5BC@sluga.fer.hr>
In-Reply-To: <007801cd9c9b$3b06d5a0$b11480e0$@unizar.es>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcmtf] Next steps with TCMTF
Thread-Index: Ac2cmrry4BaRIpi1Sm27mcZI4g4aKwUW4ybw
References: <007801cd9c9b$3b06d5a0$b11480e0$@unizar.es>
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: <tcmtf@ietf.org>
X-OriginalArrivalTime: 23 Oct 2012 08:14:20.0404 (UTC) FILETIME=[673BFB40:01CDB0F6]
Subject: Re: [tcmtf] Next steps with 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, 23 Oct 2012 08:14:26 -0000

Hello all,

Regarding the b) "Recommendations draft" I have created a first summary =
of real-time services suitable for multiplexing.

In short I have analyzed the literature regarding:
1) 2-way audio video communications
2) Multiplayer gaming
3) Remote control

I will shortly just summarize the results without listing all sources.
Note: Under term latency one way delay is considered.

For 2-way audio and video communication ITU.T recommendations state that =
150ms latency is needed for completely unimpaired communication. =
Latencies up to 400ms can be tolerated, but their impact is noticeable.

Multiplayer gaming differs significantly on the genre.=20
The most demanding games are First Person Shooter (FPS) games which =
require between 80ms and 100ms delay for unimpaired experience.
Some studies claim that Thrid Person Avatar games from which the most =
common are Role Playing Games (RPGs) and Massively Multiplayer =
Role-Playing Games MMORPGs tolerate latencies up to 500ms, but other =
studies state that a more realistic values for unimpaired MMORPG =
experience is between 120 and 200ms.
As for omnipresent games such as Real Time Strategies (RTS) it is stated =
that latencies up to 500ms and even up to 1000ms do not impair user =
performance on objective metrics, but the evidence from RTS game forums =
suggests that users are quite unsatisfied with latencies above 300ms.

Remote control has different values of latency for different services as =
well. Remote surgery is stated that 330ms latency is acceptable, but for =
controlling a robot in scope of end-to-end tele-echography showed that =
only latencies under 150ms are acceptable.

What do you think is there a possibility to make an extended version of =
such a document and submit it as a draft?

Thanks for any feedback!

Mirko Suznjevic

-----Original Message-----
From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =
Of Jose Saldana
Sent: Thursday, September 27, 2012 12:31 PM
To: tcmtf@ietf.org
Cc: Wesley Eddy; Martin Stiemerling
Subject: [tcmtf] Next steps with TCMTF

Hello all,

I would like to discuss in this list the possibility of creating a small =
Working Group for TCMTF, as suggested by Wes. It could have the task of =
making a RFC from TCMTF, or a wider scope. I think that perhaps more =
than a draft would be necessary. I mean, I have been thinking about it, =
and perhaps the work could be divided into the next parts:

 a) "Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03), =
including the protocol stack of TCMTF. The current proposal has =
different options, but the concrete one to use is static: in the set-up =
moment, you decide that "between these two routers a tunnel is set =
including all the packets with this IP origin and destination".
=20
b) "Recommendations draft": another "informational" one, with =
recommendations of maximum delays to be added to different kinds of =
services, different multiplexing policies, implementation issues related =
to the selection of the best compression algorithm to use, etc. Some =
hypothetical examples:
      -  "if you are multiplexing a First Person Shooter, your =
multiplexer should not retain packets more than 50 ms"
- "if you are multiplexing in a low-end router in a wired scenario, you =
don't need to use ROHC. A simpler scheme like IPHC can be enough, and it =
will not require a lot of processing capacity".
=20
c) "Dynamic Signaling draft": perhaps another one including a signaling =
system in order to:
 	- dynamically "negotiate" the concrete options of TCMTF you are going =
to use
 	- if two routers notice that a rush hour is arriving, they could send =
some packets asking other routers if they have some flows in common with =
them, which could be multiplexed.
=20

The main questions are:

Is this enough for creating a working group?

Do you think the distribution of the work into three draft makes sense?

Is there any other issue which should be studied and standardized? =
Perhaps other people could imagine more things.

So let's start the discussion.

Thanks in advance,

Jose=20


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

From jsaldana@unizar.es  Tue Oct 23 01:25: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 AF37A21F8644 for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 01:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.207
X-Spam-Level: 
X-Spam-Status: No, score=-6.207 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iCpnuYzKI8cg for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 01:25:58 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 7934C21F846B for <tcmtf@ietf.org>; Tue, 23 Oct 2012 01:25:57 -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 q9N8Po6J001665; Tue, 23 Oct 2012 10:25:50 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "=?iso-8859-2?Q?'Mirko_Su=BEnjevi=E6'?=" <Mirko.Suznjevic@fer.hr>
References: <007801cd9c9b$3b06d5a0$b11480e0$@unizar.es> <A3179A2C9AAEE647BE70AC4C7881D5FB0167E5BC@sluga.fer.hr>
In-Reply-To: <A3179A2C9AAEE647BE70AC4C7881D5FB0167E5BC@sluga.fer.hr>
Date: Tue, 23 Oct 2012 10:25:54 +0200
Organization: Universidad de Zaragoza
Message-ID: <003601cdb0f8$04f119a0$0ed34ce0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJpbWemvonwyxHJ/8KeqN5mdLxCRAK1Ml4dlnlpGPA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Next steps with 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: Tue, 23 Oct 2012 08:25:58 -0000

Mirko,

This sounds really good!. This was the idea of "draft b)".

Do you think you have included all the services which can be multiplexed
with TCMTF? I mean: small packets and high overhead. Some ideas: sensor
networks sending a sample, video-surveillance, whatsapp-like =
applications?
Although some of them are not real-time, perhaps they can also be
multiplexed if the number of packets per second is big.

So perhaps a section enumerating non real-time applications with small
packets could also be interesting: for example "instant messaging
applications can tolerate up to 5 seconds of delay" (I have just =
invented
the figure, it's only an example).

I could help you with this, if you agree, of course.

Thanks,

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Mirko Su=BEnjevic
> Enviado el: martes, 23 de octubre de 2012 10:14
> Para: tcmtf@ietf.org
> Asunto: Re: [tcmtf] Next steps with TCMTF
>=20
> Hello all,
>=20
> Regarding the b) "Recommendations draft" I have created a first =
summary of
> real-time services suitable for multiplexing.
>=20
> In short I have analyzed the literature regarding:
> 1) 2-way audio video communications
> 2) Multiplayer gaming
> 3) Remote control
>=20
> I will shortly just summarize the results without listing all sources.
> Note: Under term latency one way delay is considered.
>=20
> For 2-way audio and video communication ITU.T recommendations state =
that
> 150ms latency is needed for completely unimpaired communication.
> Latencies up to 400ms can be tolerated, but their impact is =
noticeable.
>=20
> Multiplayer gaming differs significantly on the genre.
> The most demanding games are First Person Shooter (FPS) games which
> require between 80ms and 100ms delay for unimpaired experience.
> Some studies claim that Thrid Person Avatar games from which the most
> common are Role Playing Games (RPGs) and Massively Multiplayer Role-
> Playing Games MMORPGs tolerate latencies up to 500ms, but other =
studies
> state that a more realistic values for unimpaired MMORPG experience is
> between 120 and 200ms.
> As for omnipresent games such as Real Time Strategies (RTS) it is =
stated
that
> latencies up to 500ms and even up to 1000ms do not impair user
> performance on objective metrics, but the evidence from RTS game =
forums
> suggests that users are quite unsatisfied with latencies above 300ms.
>=20
> Remote control has different values of latency for different services =
as
well.
> Remote surgery is stated that 330ms latency is acceptable, but for
controlling
> a robot in scope of end-to-end tele-echography showed that only =
latencies
> under 150ms are acceptable.
>=20
> What do you think is there a possibility to make an extended version =
of
such
> a document and submit it as a draft?
>=20
> Thanks for any feedback!
>=20
> Mirko Suznjevic
>=20
> -----Original Message-----
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
> Of Jose Saldana
> Sent: Thursday, September 27, 2012 12:31 PM
> To: tcmtf@ietf.org
> Cc: Wesley Eddy; Martin Stiemerling
> Subject: [tcmtf] Next steps with TCMTF
>=20
> Hello all,
>=20
> I would like to discuss in this list the possibility of creating a =
small
Working
> Group for TCMTF, as suggested by Wes. It could have the task of making =
a
> RFC from TCMTF, or a wider scope. I think that perhaps more than a =
draft
> would be necessary. I mean, I have been thinking about it, and perhaps =
the
> work could be divided into the next parts:
>=20
>  a) "Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03),
including
> the protocol stack of TCMTF. The current proposal has different =
options,
but
> the concrete one to use is static: in the set-up moment, you decide =
that
> "between these two routers a tunnel is set including all the packets =
with
this
> IP origin and destination".
>=20
> b) "Recommendations draft": another "informational" one, with
> recommendations of maximum delays to be added to different kinds of
> services, different multiplexing policies, implementation issues =
related
to the
> selection of the best compression algorithm to use, etc. Some =
hypothetical
> examples:
>       -  "if you are multiplexing a First Person Shooter, your =
multiplexer
should
> not retain packets more than 50 ms"
> - "if you are multiplexing in a low-end router in a wired scenario, =
you
don't
> need to use ROHC. A simpler scheme like IPHC can be enough, and it =
will
not
> require a lot of processing capacity".
>=20
> c) "Dynamic Signaling draft": perhaps another one including a =
signaling
> system in order to:
>  	- dynamically "negotiate" the concrete options of TCMTF you are
> going to use
>  	- if two routers notice that a rush hour is arriving, they could
send
> some packets asking other routers if they have some flows in common =
with
> them, which could be multiplexed.
>=20
>=20
> The main questions are:
>=20
> Is this enough for creating a working group?
>=20
> Do you think the distribution of the work into three draft makes =
sense?
>=20
> Is there any other issue which should be studied and standardized? =
Perhaps
> other people could imagine more things.
>=20
> So let's start the discussion.
>=20
> Thanks in advance,
>=20
> Jose
>=20
>=20
> _______________________________________________
> 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 Mirko.Suznjevic@fer.hr  Tue Oct 23 01:40:54 2012
Return-Path: <Mirko.Suznjevic@fer.hr>
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 CE30121F86B4 for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 01:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x8YtTLaFYm3C for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 01:40:54 -0700 (PDT)
Received: from mail.zvne.fer.hr (mail.zvne.fer.hr [161.53.66.5]) by ietfa.amsl.com (Postfix) with ESMTP id 9B68421F86B5 for <tcmtf@ietf.org>; Tue, 23 Oct 2012 01:40:53 -0700 (PDT)
Received: from munja.zvne.fer.hr (161.53.66.248) by mail.zvne.fer.hr (161.53.66.5) with Microsoft SMTP Server id 14.2.298.4; Tue, 23 Oct 2012 10:40:52 +0200
Received: from sluga.fer.hr ([161.53.66.244]) by munja.zvne.fer.hr with Microsoft SMTPSVC(6.0.3790.4675);	 Tue, 23 Oct 2012 10:40:52 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 23 Oct 2012 10:40:52 +0200
Message-ID: <A3179A2C9AAEE647BE70AC4C7881D5FB0167E5C5@sluga.fer.hr>
In-Reply-To: <003601cdb0f8$04f119a0$0ed34ce0$@unizar.es>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcmtf] Next steps with TCMTF
Thread-Index: AQJpbWemvonwyxHJ/8KeqN5mdLxCRAK1Ml4dlnlpGPCAAARlIA==
References: <007801cd9c9b$3b06d5a0$b11480e0$@unizar.es> <A3179A2C9AAEE647BE70AC4C7881D5FB0167E5BC@sluga.fer.hr> <003601cdb0f8$04f119a0$0ed34ce0$@unizar.es>
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: <jsaldana@unizar.es>
X-OriginalArrivalTime: 23 Oct 2012 08:40:52.0297 (UTC) FILETIME=[1C139390:01CDB0FA]
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Next steps with 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, 23 Oct 2012 08:40:54 -0000

Hello,

Well I have not included all the services. Mostly I have focused on the =
real-time ones.
I think that TCMTF can be used to improve other services which do not =
require low latencies, but have required properties of the traffic.
In that case it is just easier, as no hard limits on the latency exists =
and therefore TCMTF usage does not interrupt the QoS or QoE.

Yes I agree with your suggestion, it would also be nice to add the =
section about non-real time services and their tolerated delays (even if =
we talk in time frames of seconds or even minutes). Again if you can =
aggregate on a longer time period the aggregation results will be =
better, so TCMTF could be useful for bandwidth savings in such =
applications for a wide array of  examples.

Cheers!
Mirko Suznjevic

-----Original Message-----
From: Jose Saldana [mailto:jsaldana@unizar.es]=20
Sent: Tuesday, October 23, 2012 10:26 AM
To: Mirko Su=BEnjevi=E6
Cc: tcmtf@ietf.org
Subject: RE: [tcmtf] Next steps with TCMTF

Mirko,

This sounds really good!. This was the idea of "draft b)".

Do you think you have included all the services which can be multiplexed =
with TCMTF? I mean: small packets and high overhead. Some ideas: sensor =
networks sending a sample, video-surveillance, whatsapp-like =
applications?
Although some of them are not real-time, perhaps they can also be =
multiplexed if the number of packets per second is big.

So perhaps a section enumerating non real-time applications with small =
packets could also be interesting: for example "instant messaging =
applications can tolerate up to 5 seconds of delay" (I have just =
invented the figure, it's only an example).

I could help you with this, if you agree, of course.

Thanks,

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre=20
> de Mirko Su=BEnjevic Enviado el: martes, 23 de octubre de 2012 10:14
> Para: tcmtf@ietf.org
> Asunto: Re: [tcmtf] Next steps with TCMTF
>=20
> Hello all,
>=20
> Regarding the b) "Recommendations draft" I have created a first=20
> summary of real-time services suitable for multiplexing.
>=20
> In short I have analyzed the literature regarding:
> 1) 2-way audio video communications
> 2) Multiplayer gaming
> 3) Remote control
>=20
> I will shortly just summarize the results without listing all sources.
> Note: Under term latency one way delay is considered.
>=20
> For 2-way audio and video communication ITU.T recommendations state=20
> that 150ms latency is needed for completely unimpaired communication.
> Latencies up to 400ms can be tolerated, but their impact is =
noticeable.
>=20
> Multiplayer gaming differs significantly on the genre.
> The most demanding games are First Person Shooter (FPS) games which=20
> require between 80ms and 100ms delay for unimpaired experience.
> Some studies claim that Thrid Person Avatar games from which the most=20
> common are Role Playing Games (RPGs) and Massively Multiplayer Role-=20
> Playing Games MMORPGs tolerate latencies up to 500ms, but other=20
> studies state that a more realistic values for unimpaired MMORPG=20
> experience is between 120 and 200ms.
> As for omnipresent games such as Real Time Strategies (RTS) it is=20
> stated
that
> latencies up to 500ms and even up to 1000ms do not impair user=20
> performance on objective metrics, but the evidence from RTS game=20
> forums suggests that users are quite unsatisfied with latencies above =
300ms.
>=20
> Remote control has different values of latency for different services=20
> as
well.
> Remote surgery is stated that 330ms latency is acceptable, but for
controlling
> a robot in scope of end-to-end tele-echography showed that only=20
> latencies under 150ms are acceptable.
>=20
> What do you think is there a possibility to make an extended version=20
> of
such
> a document and submit it as a draft?
>=20
> Thanks for any feedback!
>=20
> Mirko Suznjevic
>=20
> -----Original Message-----
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =

> Of Jose Saldana
> Sent: Thursday, September 27, 2012 12:31 PM
> To: tcmtf@ietf.org
> Cc: Wesley Eddy; Martin Stiemerling
> Subject: [tcmtf] Next steps with TCMTF
>=20
> Hello all,
>=20
> I would like to discuss in this list the possibility of creating a=20
> small
Working
> Group for TCMTF, as suggested by Wes. It could have the task of making =

> a RFC from TCMTF, or a wider scope. I think that perhaps more than a=20
> draft would be necessary. I mean, I have been thinking about it, and=20
> perhaps the work could be divided into the next parts:
>=20
>  a) "Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03),
including
> the protocol stack of TCMTF. The current proposal has different=20
> options,
but
> the concrete one to use is static: in the set-up moment, you decide=20
> that "between these two routers a tunnel is set including all the=20
> packets with
this
> IP origin and destination".
>=20
> b) "Recommendations draft": another "informational" one, with=20
> recommendations of maximum delays to be added to different kinds of=20
> services, different multiplexing policies, implementation issues=20
> related
to the
> selection of the best compression algorithm to use, etc. Some=20
> hypothetical
> examples:
>       -  "if you are multiplexing a First Person Shooter, your=20
> multiplexer
should
> not retain packets more than 50 ms"
> - "if you are multiplexing in a low-end router in a wired scenario,=20
> you
don't
> need to use ROHC. A simpler scheme like IPHC can be enough, and it=20
> will
not
> require a lot of processing capacity".
>=20
> c) "Dynamic Signaling draft": perhaps another one including a=20
> signaling system in order to:
>  	- dynamically "negotiate" the concrete options of TCMTF you are=20
> going to use
>  	- if two routers notice that a rush hour is arriving, they could
send
> some packets asking other routers if they have some flows in common=20
> with them, which could be multiplexed.
>=20
>=20
> The main questions are:
>=20
> Is this enough for creating a working group?
>=20
> Do you think the distribution of the work into three draft makes =
sense?
>=20
> Is there any other issue which should be studied and standardized?=20
> Perhaps other people could imagine more things.
>=20
> So let's start the discussion.
>=20
> Thanks in advance,
>=20
> Jose
>=20
>=20
> _______________________________________________
> 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 ggx@gigix.net  Tue Oct 23 01:41:33 2012
Return-Path: <ggx@gigix.net>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A13921F86B4 for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 01:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Level: 
X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eXCW5IcKwycm for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 01:41:32 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 27FF121F86BE for <tcmtf@ietf.org>; Tue, 23 Oct 2012 01:41:32 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id dr13so2016077wgb.13 for <tcmtf@ietf.org>; Tue, 23 Oct 2012 01:41:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=6cYPQl21p4D7sEEYcmnMNx6XrL9Tfcb9Fi3Hqubqimk=; b=Ribx4LZbcAe2TVuqiDRTc/IT7l+9R2EBO3tOij5NVzJR8mAdtWoInohYsGZ3Qg3HgJ Uz43dJXxPlsxOG2h+5SL26FYBW53ZL4J1/h/kKMUcmYYB5OcRrl5x7IjXyA7xCp7AscP 68RAfoyVThwuGdNCCKbf2McVfAO/Qk55z1W5qkk3tvM5La6HyiScnimR+RrExG5HWuRR u7acUN9Occ5ds2h1srjtyyEPP+H8z6ZhOPerTVO6yyI3DQfttwvsXkpKaUe+ez4aJbWQ 44fOvfeT/02lLzaerstlysiKM2+ijWjS61vn5tAzWoPtWa9ZAFO0ncGU+my5cc8zicro oAsQ==
Received: by 10.216.202.164 with SMTP id d36mr6724442weo.55.1350981691316; Tue, 23 Oct 2012 01:41:31 -0700 (PDT)
Received: from dhcp164-04.enst.fr (dhcp164-04.enst.fr. [137.194.165.4]) by mx.google.com with ESMTPS id w8sm55213490wif.4.2012.10.23.01.41.29 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 23 Oct 2012 01:41:30 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_E01C4C80-EA69-4EE1-A0BE-080A1EACE2B8"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <4F8E71CE-F8DB-41A6-8803-9021C20A2A09@gigix.net>
Date: Tue, 23 Oct 2012 10:45:20 +0200
Message-Id: <A7C5E55A-422D-4E20-8E76-1025EF141F80@gigix.net>
References: <007801cd9c9b$3b06d5a0$b11480e0$@unizar.es> <A3179A2C9AAEE647BE70AC4C7881D5FB0167E5BC@sluga.fer.hr> <4F8E71CE-F8DB-41A6-8803-9021C20A2A09@gigix.net>
To: =?utf-8?Q?Mirko_Su=C5=BEnjevi=C4=87?= <Mirko.Suznjevic@fer.hr>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQnJUQS8oCJN1FfjHsSflAwdmIFxjKHs/iI/ItMgpZH1KqJTf6hA9hGqevcHdjnXJtOjz1Br
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Next steps with 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, 23 Oct 2012 08:41:33 -0000

--Apple-Mail=_E01C4C80-EA69-4EE1-A0BE-080A1EACE2B8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

On 23 Oct. 2012, at 10:14 , Mirko Su=C5=BEnjevi=C4=87 =
<Mirko.Suznjevic@fer.hr> wrote:

> Hello all,
>=20
> Regarding the b) "Recommendations draft" I have created a first =
summary of real-time services suitable for multiplexing.
>=20
> In short I have analyzed the literature regarding:
> 1) 2-way audio video communications
> 2) Multiplayer gaming
> 3) Remote control

May I ask whether or not one way audio video communications should have =
their own category?

May be it falls already in 1), but I was thinking that Internet is the =
more and more used for live events (think about the olympics).
So a broadcaster may have agreements with other ISPs to use TCMTF to =
reduce bandwidth while transmitting these live events (that cannot be =
"downloaded" like other streaming videos, they just need to be =
"constantly" streamed as long as the event goes on).

Could be this something to add?

Luigi



>=20
> I will shortly just summarize the results without listing all sources.
> Note: Under term latency one way delay is considered.
>=20
> For 2-way audio and video communication ITU.T recommendations state =
that 150ms latency is needed for completely unimpaired communication. =
Latencies up to 400ms can be tolerated, but their impact is noticeable.
>=20
> Multiplayer gaming differs significantly on the genre.=20
> The most demanding games are First Person Shooter (FPS) games which =
require between 80ms and 100ms delay for unimpaired experience.
> Some studies claim that Thrid Person Avatar games from which the most =
common are Role Playing Games (RPGs) and Massively Multiplayer =
Role-Playing Games MMORPGs tolerate latencies up to 500ms, but other =
studies state that a more realistic values for unimpaired MMORPG =
experience is between 120 and 200ms.
> As for omnipresent games such as Real Time Strategies (RTS) it is =
stated that latencies up to 500ms and even up to 1000ms do not impair =
user performance on objective metrics, but the evidence from RTS game =
forums suggests that users are quite unsatisfied with latencies above =
300ms.
>=20
> Remote control has different values of latency for different services =
as well. Remote surgery is stated that 330ms latency is acceptable, but =
for controlling a robot in scope of end-to-end tele-echography showed =
that only latencies under 150ms are acceptable.
>=20
> What do you think is there a possibility to make an extended version =
of such a document and submit it as a draft?
>=20
> Thanks for any feedback!
>=20
> Mirko Suznjevic
>=20
> -----Original Message-----
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =
Of Jose Saldana
> Sent: Thursday, September 27, 2012 12:31 PM
> To: tcmtf@ietf.org
> Cc: Wesley Eddy; Martin Stiemerling
> Subject: [tcmtf] Next steps with TCMTF
>=20
> Hello all,
>=20
> I would like to discuss in this list the possibility of creating a =
small Working Group for TCMTF, as suggested by Wes. It could have the =
task of making a RFC from TCMTF, or a wider scope. I think that perhaps =
more than a draft would be necessary. I mean, I have been thinking about =
it, and perhaps the work could be divided into the next parts:
>=20
> a) "Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03), =
including the protocol stack of TCMTF. The current proposal has =
different options, but the concrete one to use is static: in the set-up =
moment, you decide that "between these two routers a tunnel is set =
including all the packets with this IP origin and destination".
>=20
> b) "Recommendations draft": another "informational" one, with =
recommendations of maximum delays to be added to different kinds of =
services, different multiplexing policies, implementation issues related =
to the selection of the best compression algorithm to use, etc. Some =
hypothetical examples:
>     -  "if you are multiplexing a First Person Shooter, your =
multiplexer should not retain packets more than 50 ms"
> - "if you are multiplexing in a low-end router in a wired scenario, =
you don't need to use ROHC. A simpler scheme like IPHC can be enough, =
and it will not require a lot of processing capacity".
>=20
> c) "Dynamic Signaling draft": perhaps another one including a =
signaling system in order to:
> 	- dynamically "negotiate" the concrete options of TCMTF you are =
going to use
> 	- if two routers notice that a rush hour is arriving, they could =
send some packets asking other routers if they have some flows in common =
with them, which could be multiplexed.
>=20
>=20
> The main questions are:
>=20
> Is this enough for creating a working group?
>=20
> Do you think the distribution of the work into three draft makes =
sense?
>=20
> Is there any other issue which should be studied and standardized? =
Perhaps other people could imagine more things.
>=20
> So let's start the discussion.
>=20
> Thanks in advance,
>=20
> Jose=20
>=20
>=20
> _______________________________________________
> 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



--Apple-Mail=_E01C4C80-EA69-4EE1-A0BE-080A1EACE2B8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Hi,</div><div><br><div><div>On 23 Oct. 2012, at 10:14 , Mirko =
Su=C5=BEnjevi=C4=87 &lt;<a =
href=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt; =
wrote:</div><blockquote type=3D"cite"></blockquote><font =
color=3D"#0f61c8"><br></font><blockquote type=3D"cite"><blockquote =
type=3D"cite"></blockquote>Hello all,<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>Regarding the b) "Recommendations draft" I =
have created a first summary of real-time services suitable for =
multiplexing.<br><blockquote type=3D"cite"></blockquote><font =
color=3D"#007316"><br></font><blockquote type=3D"cite"></blockquote>In =
short I have analyzed the literature regarding:<br><blockquote =
type=3D"cite"></blockquote>1) 2-way audio video =
communications<br><blockquote type=3D"cite"></blockquote>2) Multiplayer =
gaming<br>3) Remote control<br></blockquote><blockquote =
type=3D"cite"></blockquote><font color=3D"#0f61c8"><br></font><blockquote =
type=3D"cite"></blockquote>May I ask whether or not one way audio video =
communications should have their own category?<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#0f61c8"><br></font><blockquote =
type=3D"cite"></blockquote>May be it falls already in 1), but I was =
thinking that Internet is the more and more used for live events (think =
about the olympics).<br><blockquote type=3D"cite"></blockquote>So a =
broadcaster may have agreements with other ISPs to use TCMTF to reduce =
bandwidth while transmitting these live events (that cannot be =
"downloaded" like other streaming videos, they just need to be =
"constantly" streamed as long as the event goes on).<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#0f61c8"><br></font><blockquote =
type=3D"cite"></blockquote>Could be this something to =
add?<br><blockquote type=3D"cite"></blockquote><font =
color=3D"#0f61c8"><br></font><blockquote =
type=3D"cite"></blockquote>Luigi<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#0f61c8"><br></font><blockquote =
type=3D"cite"></blockquote><font color=3D"#0f61c8"><br></font><blockquote =
type=3D"cite"></blockquote><font color=3D"#0f61c8"><br></font><blockquote =
type=3D"cite"><blockquote type=3D"cite"></blockquote><font =
color=3D"#007316"><br></font><blockquote type=3D"cite"></blockquote>I =
will shortly just summarize the results without listing all =
sources.<br><blockquote type=3D"cite"></blockquote>Note: Under term =
latency one way delay is considered.<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>For 2-way audio and video communication ITU.T =
recommendations state that 150ms latency is needed for completely =
unimpaired communication. Latencies up to 400ms can be tolerated, but =
their impact is noticeable.<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>Multiplayer gaming differs significantly on =
the genre.&nbsp;<br><blockquote type=3D"cite"></blockquote>The most =
demanding games are First Person Shooter (FPS) games which require =
between 80ms and 100ms delay for unimpaired experience.<br><blockquote =
type=3D"cite"></blockquote>Some studies claim that Thrid Person Avatar =
games from which the most common are Role Playing Games (RPGs) and =
Massively Multiplayer Role-Playing Games MMORPGs tolerate latencies up =
to 500ms, but other studies state that a more realistic values for =
unimpaired MMORPG experience is between 120 and 200ms.<br><blockquote =
type=3D"cite"></blockquote>As for omnipresent games such as Real Time =
Strategies (RTS) it is stated that latencies up to 500ms and even up to =
1000ms do not impair user performance on objective metrics, but the =
evidence from RTS game forums suggests that users are quite unsatisfied =
with latencies above 300ms.<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>Remote control has different values of =
latency for different services as well. Remote surgery is stated that =
330ms latency is acceptable, but for controlling a robot in scope of =
end-to-end tele-echography showed that only latencies under 150ms are =
acceptable.<br><blockquote type=3D"cite"></blockquote><font =
color=3D"#007316"><br></font><blockquote type=3D"cite"></blockquote>What =
do you think is there a possibility to make an extended version of such =
a document and submit it as a draft?<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>Thanks for any feedback!<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>Mirko Suznjevic<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>-----Original Message-----<br><blockquote =
type=3D"cite"></blockquote>From: <a =
href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> =
[mailto:tcmtf-<a href=3D"mailto:bounces@ietf.org">bounces@ietf.org</a>] =
On Behalf Of Jose Saldana<br><blockquote type=3D"cite"></blockquote>Sent: =
Thursday, September 27, 2012 12:31 PM<br><blockquote =
type=3D"cite"></blockquote>To: <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><blockquote =
type=3D"cite"></blockquote>Cc: Wesley Eddy; Martin =
Stiemerling<br><blockquote type=3D"cite"></blockquote>Subject: [tcmtf] =
Next steps with TCMTF<br><blockquote type=3D"cite"></blockquote><font =
color=3D"#007316"><br></font><blockquote type=3D"cite"></blockquote>Hello =
all,<br><blockquote type=3D"cite"></blockquote><font =
color=3D"#007316"><br></font><blockquote type=3D"cite"></blockquote>I =
would like to discuss in this list the possibility of creating a small =
Working Group for TCMTF, as suggested by Wes. It could have the task of =
making a RFC from TCMTF, or a wider scope. I think that perhaps more =
than a draft would be necessary. I mean, I have been thinking about it, =
and perhaps the work could be divided into the next =
parts:<br><blockquote type=3D"cite"></blockquote><font =
color=3D"#007316"><br></font><blockquote type=3D"cite"></blockquote>a) =
"Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03), =
including the protocol stack of TCMTF. The current proposal has =
different options, but the concrete one to use is static: in the set-up =
moment, you decide that "between these two routers a tunnel is set =
including all the packets with this IP origin and =
destination".<br><blockquote type=3D"cite"></blockquote><font =
color=3D"#007316"><br></font><blockquote type=3D"cite"></blockquote>b) =
"Recommendations draft": another "informational" one, with =
recommendations of maximum delays to be added to different kinds of =
services, different multiplexing policies, implementation issues related =
to the selection of the best compression algorithm to use, etc. Some =
hypothetical examples:<br><blockquote type=3D"cite"></blockquote>&nbsp; =
&nbsp; - &nbsp;"if you are multiplexing a First Person Shooter, your =
multiplexer should not retain packets more than 50 ms"<br><blockquote =
type=3D"cite"></blockquote>- "if you are multiplexing in a low-end =
router in a wired scenario, you don't need to use ROHC. A simpler scheme =
like IPHC can be enough, and it will not require a lot of processing =
capacity".<br><blockquote type=3D"cite"></blockquote><font =
color=3D"#007316"><br></font><blockquote type=3D"cite"></blockquote>c) =
"Dynamic Signaling draft": perhaps another one including a signaling =
system in order to:<br><blockquote type=3D"cite"></blockquote><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- =
dynamically "negotiate" the concrete options of TCMTF you are going to =
use<br><blockquote type=3D"cite"></blockquote><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- if two =
routers notice that a rush hour is arriving, they could send some =
packets asking other routers if they have some flows in common with =
them, which could be multiplexed.<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>The main questions are:<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>Is this enough for creating a working =
group?<br><blockquote type=3D"cite"></blockquote><font =
color=3D"#007316"><br></font><blockquote type=3D"cite"></blockquote>Do =
you think the distribution of the work into three draft makes =
sense?<br><blockquote type=3D"cite"></blockquote><font =
color=3D"#007316"><br></font><blockquote type=3D"cite"></blockquote>Is =
there any other issue which should be studied and standardized? Perhaps =
other people could imagine more things.<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>So let's start the discussion.<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>Thanks in advance,<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>Jose&nbsp;<br><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote><font color=3D"#007316"><br></font><blockquote =
type=3D"cite"></blockquote>_______________________________________________=
<br><blockquote type=3D"cite"></blockquote>tcmtf mailing =
list<br><blockquote type=3D"cite"></blockquote><a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><blockquote =
type=3D"cite"></blockquote>https://www.ietf.org/mailman/listinfo/tcmtf<br>=
<blockquote =
type=3D"cite"></blockquote>_______________________________________________=
<br><blockquote type=3D"cite"></blockquote>tcmtf mailing =
list<br><blockquote =
type=3D"cite"></blockquote>tcmtf@ietf.org<br>https://www.ietf.org/mailman/=
listinfo/tcmtf<br></blockquote><br></div></div><br></body></html>=

--Apple-Mail=_E01C4C80-EA69-4EE1-A0BE-080A1EACE2B8--

From Mirko.Suznjevic@fer.hr  Tue Oct 23 01:45:42 2012
Return-Path: <Mirko.Suznjevic@fer.hr>
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 BA00E21F8662 for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 01:45:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l59SH7ClKQjB for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 01:45:41 -0700 (PDT)
Received: from mail.zvne.fer.hr (mail.zvne.fer.hr [161.53.66.5]) by ietfa.amsl.com (Postfix) with ESMTP id 1302121F85A3 for <tcmtf@ietf.org>; Tue, 23 Oct 2012 01:45:41 -0700 (PDT)
Received: from munja.zvne.fer.hr (161.53.66.248) by mail.zvne.fer.hr (161.53.66.5) with Microsoft SMTP Server id 14.2.298.4; Tue, 23 Oct 2012 10:45:40 +0200
Received: from sluga.fer.hr ([161.53.66.244]) by munja.zvne.fer.hr with Microsoft SMTPSVC(6.0.3790.4675);	 Tue, 23 Oct 2012 10:45:40 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Tue, 23 Oct 2012 10:45:38 +0200
Message-ID: <A3179A2C9AAEE647BE70AC4C7881D5FB0167E5C7@sluga.fer.hr>
In-Reply-To: <4F8E71CE-F8DB-41A6-8803-9021C20A2A09@gigix.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcmtf] Next steps with TCMTF
Thread-Index: Ac2w+hhwp+FFV9e3RquoqIywsMJXswAABkVw
References: <007801cd9c9b$3b06d5a0$b11480e0$@unizar.es> <A3179A2C9AAEE647BE70AC4C7881D5FB0167E5BC@sluga.fer.hr> <4F8E71CE-F8DB-41A6-8803-9021C20A2A09@gigix.net>
From: =?utf-8?B?TWlya28gU3XFvm5qZXZpxIc=?= <Mirko.Suznjevic@fer.hr>
To: Luigi Iannone <ggx@openlisp.org>
X-OriginalArrivalTime: 23 Oct 2012 08:45:40.0096 (UTC) FILETIME=[C79E3800:01CDB0FA]
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Next steps with 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, 23 Oct 2012 08:45:42 -0000

SSBjb25jdXIgd2l0aCB0aGlzLiBCYW5kd2lkdGggbGltaXRhdGlvbnMgYXJlIGEgaHVnZSBpc3N1
ZSBpbiBhbnkgdHlwZSBvZiBsYXJnZSBzY2FsZSBzdHJlYW1pbmcgZXZlbnRzLCBhbHRob3VnaCBw
cm9wZXJ0aWVzIG9mIHRoZSBzdHJlYW1pbmcgdHJhZmZpYyBzaG91bGQgYmUgdGFrZW4gaW50byBh
Y2NvdW50IChub3QgdGhhdCBtYW55IHNtYWxsIHBhY2tldHMpLg0KDQpJIG1pZ2h0IGhhdmUgc2Fp
ZCB0aGlzIGVhcmxpZXIgYnV0IHRoZSB3b3JsZCByZWNvcmQgb24gdGhlIGZhc3Rlc3QgSW50ZXJu
ZXQgY29ubmVjdGlvbiBmb3IgYSBjZXJ0YWluIGV2ZW50IHdhcyBzZXQgYnkgRHJlYW1oYWNrIDIw
MTEgYSBsYXJnZSBMQU4gcGFydHkgd2l0aCBhIGxvdCBvZiBzdHJlYW1pbmcgYW5kIGEgbG90IG9m
IHBsYXllcnMgcGxheWluZyBkaWZmZXJlbnQgZ2FtZXMgKHRob3VnaCB0aGUgaW5mbyBtYXkgYmUg
YSBiaXQgb3V0ZGF0ZWQpLg0KaHR0cDovL3d3dy5kcmVhbWhhY2suc2UvZGh3MTEvMjAxMS8xMS8y
Mi8xMjAtZ2lnYWJpdC1hdC1kaHcxMS8NCg0KQ2hlZXJzIQ0KTWlya28NCg0KDQotLS0tLU9yaWdp
bmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogTHVpZ2kgSWFubm9uZSBbbWFpbHRvOmdneEBvcGVubGlz
cC5vcmddIA0KU2VudDogVHVlc2RheSwgT2N0b2JlciAyMywgMjAxMiAxMDo0NCBBTQ0KVG86IE1p
cmtvIFN1xb5uamV2acSHDQpDYzogdGNtdGZAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbdGNtdGZd
IE5leHQgc3RlcHMgd2l0aCBUQ01URg0KDQoNCk9uIDIzIE9jdC4gMjAxMiwgYXQgMTA6MTQgLCBN
aXJrbyBTdcW+bmpldmnEhyA8TWlya28uU3V6bmpldmljQGZlci5ocj4gd3JvdGU6DQoNCj4gSGVs
bG8gYWxsLA0KPiANCj4gUmVnYXJkaW5nIHRoZSBiKSAiUmVjb21tZW5kYXRpb25zIGRyYWZ0IiBJ
IGhhdmUgY3JlYXRlZCBhIGZpcnN0IHN1bW1hcnkgb2YgcmVhbC10aW1lIHNlcnZpY2VzIHN1aXRh
YmxlIGZvciBtdWx0aXBsZXhpbmcuDQo+IA0KPiBJbiBzaG9ydCBJIGhhdmUgYW5hbHl6ZWQgdGhl
IGxpdGVyYXR1cmUgcmVnYXJkaW5nOg0KPiAxKSAyLXdheSBhdWRpbyB2aWRlbyBjb21tdW5pY2F0
aW9ucw0KPiAyKSBNdWx0aXBsYXllciBnYW1pbmcNCj4gMykgUmVtb3RlIGNvbnRyb2wNCg0KTWF5
IEkgYXNrIHdoZXRoZXIgb3Igbm90IG9uZSB3YXkgYXVkaW8gdmlkZW8gY29tbXVuaWNhdGlvbnMg
c2hvdWxkIGhhdmUgdGhlaXIgb3duIGNhdGVnb3J5Pw0KDQpNYXkgYmUgaXQgZmFsbHMgYWxyZWFk
eSBpbiAxKSwgYnV0IEkgd2FzIHRoaW5raW5nIHRoYXQgSW50ZXJuZXQgaXMgdGhlIG1vcmUgYW5k
IG1vcmUgdXNlZCBmb3IgbGl2ZSBldmVudHMgKHRoaW5rIGFib3V0IHRoZSBvbHltcGljcykuDQpT
byBhIGJyb2FkY2FzdGVyIG1heSBoYXZlIGFncmVlbWVudHMgd2l0aCBvdGhlciBJU1BzIHRvIHVz
ZSBUQ01URiB0byByZWR1Y2UgYmFuZHdpZHRoIHdoaWxlIHRyYW5zbWl0dGluZyB0aGVzZSBsaXZl
IGV2ZW50cyAodGhhdCBjYW5ub3QgYmUgImRvd25sb2FkZWQiIGxpa2Ugb3RoZXIgc3RyZWFtaW5n
IHZpZGVvcywgdGhleSBqdXN0IG5lZWQgdG8gYmUgImNvbnN0YW50bHkiIHN0cmVhbWVkIGFzIGxv
bmcgYXMgdGhlIGV2ZW50IGdvZXMgb24pLg0KDQpDb3VsZCBiZSB0aGlzIHNvbWV0aGluZyB0byBh
ZGQ/DQoNCkx1aWdpDQoNCg0KDQo+IA0KPiBJIHdpbGwgc2hvcnRseSBqdXN0IHN1bW1hcml6ZSB0
aGUgcmVzdWx0cyB3aXRob3V0IGxpc3RpbmcgYWxsIHNvdXJjZXMuDQo+IE5vdGU6IFVuZGVyIHRl
cm0gbGF0ZW5jeSBvbmUgd2F5IGRlbGF5IGlzIGNvbnNpZGVyZWQuDQo+IA0KPiBGb3IgMi13YXkg
YXVkaW8gYW5kIHZpZGVvIGNvbW11bmljYXRpb24gSVRVLlQgcmVjb21tZW5kYXRpb25zIHN0YXRl
IHRoYXQgMTUwbXMgbGF0ZW5jeSBpcyBuZWVkZWQgZm9yIGNvbXBsZXRlbHkgdW5pbXBhaXJlZCBj
b21tdW5pY2F0aW9uLiBMYXRlbmNpZXMgdXAgdG8gNDAwbXMgY2FuIGJlIHRvbGVyYXRlZCwgYnV0
IHRoZWlyIGltcGFjdCBpcyBub3RpY2VhYmxlLg0KPiANCj4gTXVsdGlwbGF5ZXIgZ2FtaW5nIGRp
ZmZlcnMgc2lnbmlmaWNhbnRseSBvbiB0aGUgZ2VucmUuIA0KPiBUaGUgbW9zdCBkZW1hbmRpbmcg
Z2FtZXMgYXJlIEZpcnN0IFBlcnNvbiBTaG9vdGVyIChGUFMpIGdhbWVzIHdoaWNoIHJlcXVpcmUg
YmV0d2VlbiA4MG1zIGFuZCAxMDBtcyBkZWxheSBmb3IgdW5pbXBhaXJlZCBleHBlcmllbmNlLg0K
PiBTb21lIHN0dWRpZXMgY2xhaW0gdGhhdCBUaHJpZCBQZXJzb24gQXZhdGFyIGdhbWVzIGZyb20g
d2hpY2ggdGhlIG1vc3QgY29tbW9uIGFyZSBSb2xlIFBsYXlpbmcgR2FtZXMgKFJQR3MpIGFuZCBN
YXNzaXZlbHkgTXVsdGlwbGF5ZXIgUm9sZS1QbGF5aW5nIEdhbWVzIE1NT1JQR3MgdG9sZXJhdGUg
bGF0ZW5jaWVzIHVwIHRvIDUwMG1zLCBidXQgb3RoZXIgc3R1ZGllcyBzdGF0ZSB0aGF0IGEgbW9y
ZSByZWFsaXN0aWMgdmFsdWVzIGZvciB1bmltcGFpcmVkIE1NT1JQRyBleHBlcmllbmNlIGlzIGJl
dHdlZW4gMTIwIGFuZCAyMDBtcy4NCj4gQXMgZm9yIG9tbmlwcmVzZW50IGdhbWVzIHN1Y2ggYXMg
UmVhbCBUaW1lIFN0cmF0ZWdpZXMgKFJUUykgaXQgaXMgc3RhdGVkIHRoYXQgbGF0ZW5jaWVzIHVw
IHRvIDUwMG1zIGFuZCBldmVuIHVwIHRvIDEwMDBtcyBkbyBub3QgaW1wYWlyIHVzZXIgcGVyZm9y
bWFuY2Ugb24gb2JqZWN0aXZlIG1ldHJpY3MsIGJ1dCB0aGUgZXZpZGVuY2UgZnJvbSBSVFMgZ2Ft
ZSBmb3J1bXMgc3VnZ2VzdHMgdGhhdCB1c2VycyBhcmUgcXVpdGUgdW5zYXRpc2ZpZWQgd2l0aCBs
YXRlbmNpZXMgYWJvdmUgMzAwbXMuDQo+IA0KPiBSZW1vdGUgY29udHJvbCBoYXMgZGlmZmVyZW50
IHZhbHVlcyBvZiBsYXRlbmN5IGZvciBkaWZmZXJlbnQgc2VydmljZXMgYXMgd2VsbC4gUmVtb3Rl
IHN1cmdlcnkgaXMgc3RhdGVkIHRoYXQgMzMwbXMgbGF0ZW5jeSBpcyBhY2NlcHRhYmxlLCBidXQg
Zm9yIGNvbnRyb2xsaW5nIGEgcm9ib3QgaW4gc2NvcGUgb2YgZW5kLXRvLWVuZCB0ZWxlLWVjaG9n
cmFwaHkgc2hvd2VkIHRoYXQgb25seSBsYXRlbmNpZXMgdW5kZXIgMTUwbXMgYXJlIGFjY2VwdGFi
bGUuDQo+IA0KPiBXaGF0IGRvIHlvdSB0aGluayBpcyB0aGVyZSBhIHBvc3NpYmlsaXR5IHRvIG1h
a2UgYW4gZXh0ZW5kZWQgdmVyc2lvbiBvZiBzdWNoIGEgZG9jdW1lbnQgYW5kIHN1Ym1pdCBpdCBh
cyBhIGRyYWZ0Pw0KPiANCj4gVGhhbmtzIGZvciBhbnkgZmVlZGJhY2shDQo+IA0KPiBNaXJrbyBT
dXpuamV2aWMNCj4gDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IHRjbXRm
LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0Y210Zi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhh
bGYgT2YgSm9zZSBTYWxkYW5hDQo+IFNlbnQ6IFRodXJzZGF5LCBTZXB0ZW1iZXIgMjcsIDIwMTIg
MTI6MzEgUE0NCj4gVG86IHRjbXRmQGlldGYub3JnDQo+IENjOiBXZXNsZXkgRWRkeTsgTWFydGlu
IFN0aWVtZXJsaW5nDQo+IFN1YmplY3Q6IFt0Y210Zl0gTmV4dCBzdGVwcyB3aXRoIFRDTVRGDQo+
IA0KPiBIZWxsbyBhbGwsDQo+IA0KPiBJIHdvdWxkIGxpa2UgdG8gZGlzY3VzcyBpbiB0aGlzIGxp
c3QgdGhlIHBvc3NpYmlsaXR5IG9mIGNyZWF0aW5nIGEgc21hbGwgV29ya2luZyBHcm91cCBmb3Ig
VENNVEYsIGFzIHN1Z2dlc3RlZCBieSBXZXMuIEl0IGNvdWxkIGhhdmUgdGhlIHRhc2sgb2YgbWFr
aW5nIGEgUkZDIGZyb20gVENNVEYsIG9yIGEgd2lkZXIgc2NvcGUuIEkgdGhpbmsgdGhhdCBwZXJo
YXBzIG1vcmUgdGhhbiBhIGRyYWZ0IHdvdWxkIGJlIG5lY2Vzc2FyeS4gSSBtZWFuLCBJIGhhdmUg
YmVlbiB0aGlua2luZyBhYm91dCBpdCwgYW5kIHBlcmhhcHMgdGhlIHdvcmsgY291bGQgYmUgZGl2
aWRlZCBpbnRvIHRoZSBuZXh0IHBhcnRzOg0KPiANCj4gYSkgIkN1cnJlbnQgZHJhZnQiOiB0aGUg
bWFpbiBkcmFmdCAoZHJhZnQtc2FsZGFuYS10c3Z3Zy10Y210Zi0wMyksIGluY2x1ZGluZyB0aGUg
cHJvdG9jb2wgc3RhY2sgb2YgVENNVEYuIFRoZSBjdXJyZW50IHByb3Bvc2FsIGhhcyBkaWZmZXJl
bnQgb3B0aW9ucywgYnV0IHRoZSBjb25jcmV0ZSBvbmUgdG8gdXNlIGlzIHN0YXRpYzogaW4gdGhl
IHNldC11cCBtb21lbnQsIHlvdSBkZWNpZGUgdGhhdCAiYmV0d2VlbiB0aGVzZSB0d28gcm91dGVy
cyBhIHR1bm5lbCBpcyBzZXQgaW5jbHVkaW5nIGFsbCB0aGUgcGFja2V0cyB3aXRoIHRoaXMgSVAg
b3JpZ2luIGFuZCBkZXN0aW5hdGlvbiIuDQo+IA0KPiBiKSAiUmVjb21tZW5kYXRpb25zIGRyYWZ0
IjogYW5vdGhlciAiaW5mb3JtYXRpb25hbCIgb25lLCB3aXRoIHJlY29tbWVuZGF0aW9ucyBvZiBt
YXhpbXVtIGRlbGF5cyB0byBiZSBhZGRlZCB0byBkaWZmZXJlbnQga2luZHMgb2Ygc2VydmljZXMs
IGRpZmZlcmVudCBtdWx0aXBsZXhpbmcgcG9saWNpZXMsIGltcGxlbWVudGF0aW9uIGlzc3VlcyBy
ZWxhdGVkIHRvIHRoZSBzZWxlY3Rpb24gb2YgdGhlIGJlc3QgY29tcHJlc3Npb24gYWxnb3JpdGht
IHRvIHVzZSwgZXRjLiBTb21lIGh5cG90aGV0aWNhbCBleGFtcGxlczoNCj4gICAgICAtICAiaWYg
eW91IGFyZSBtdWx0aXBsZXhpbmcgYSBGaXJzdCBQZXJzb24gU2hvb3RlciwgeW91ciBtdWx0aXBs
ZXhlciBzaG91bGQgbm90IHJldGFpbiBwYWNrZXRzIG1vcmUgdGhhbiA1MCBtcyINCj4gLSAiaWYg
eW91IGFyZSBtdWx0aXBsZXhpbmcgaW4gYSBsb3ctZW5kIHJvdXRlciBpbiBhIHdpcmVkIHNjZW5h
cmlvLCB5b3UgZG9uJ3QgbmVlZCB0byB1c2UgUk9IQy4gQSBzaW1wbGVyIHNjaGVtZSBsaWtlIElQ
SEMgY2FuIGJlIGVub3VnaCwgYW5kIGl0IHdpbGwgbm90IHJlcXVpcmUgYSBsb3Qgb2YgcHJvY2Vz
c2luZyBjYXBhY2l0eSIuDQo+IA0KPiBjKSAiRHluYW1pYyBTaWduYWxpbmcgZHJhZnQiOiBwZXJo
YXBzIGFub3RoZXIgb25lIGluY2x1ZGluZyBhIHNpZ25hbGluZyBzeXN0ZW0gaW4gb3JkZXIgdG86
DQo+IAktIGR5bmFtaWNhbGx5ICJuZWdvdGlhdGUiIHRoZSBjb25jcmV0ZSBvcHRpb25zIG9mIFRD
TVRGIHlvdSBhcmUgZ29pbmcgdG8gdXNlDQo+IAktIGlmIHR3byByb3V0ZXJzIG5vdGljZSB0aGF0
IGEgcnVzaCBob3VyIGlzIGFycml2aW5nLCB0aGV5IGNvdWxkIHNlbmQgc29tZSBwYWNrZXRzIGFz
a2luZyBvdGhlciByb3V0ZXJzIGlmIHRoZXkgaGF2ZSBzb21lIGZsb3dzIGluIGNvbW1vbiB3aXRo
IHRoZW0sIHdoaWNoIGNvdWxkIGJlIG11bHRpcGxleGVkLg0KPiANCj4gDQo+IFRoZSBtYWluIHF1
ZXN0aW9ucyBhcmU6DQo+IA0KPiBJcyB0aGlzIGVub3VnaCBmb3IgY3JlYXRpbmcgYSB3b3JraW5n
IGdyb3VwPw0KPiANCj4gRG8geW91IHRoaW5rIHRoZSBkaXN0cmlidXRpb24gb2YgdGhlIHdvcmsg
aW50byB0aHJlZSBkcmFmdCBtYWtlcyBzZW5zZT8NCj4gDQo+IElzIHRoZXJlIGFueSBvdGhlciBp
c3N1ZSB3aGljaCBzaG91bGQgYmUgc3R1ZGllZCBhbmQgc3RhbmRhcmRpemVkPyBQZXJoYXBzIG90
aGVyIHBlb3BsZSBjb3VsZCBpbWFnaW5lIG1vcmUgdGhpbmdzLg0KPiANCj4gU28gbGV0J3Mgc3Rh
cnQgdGhlIGRpc2N1c3Npb24uDQo+IA0KPiBUaGFua3MgaW4gYWR2YW5jZSwNCj4gDQo+IEpvc2Ug
DQo+IA0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCj4gdGNtdGYgbWFpbGluZyBsaXN0DQo+IHRjbXRmQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCj4gX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gdGNtdGYgbWFpbGluZyBsaXN0DQo+IHRjbXRm
QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYN
Cg0K

From jsaldana@unizar.es  Tue Oct 23 02:12:38 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 8545D21F8654 for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 02:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.21
X-Spam-Level: 
X-Spam-Status: No, score=-6.21 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m8RoCcnIKwzI for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 02:12:37 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 3B7B221F85A6 for <tcmtf@ietf.org>; Tue, 23 Oct 2012 02:12:36 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id q9N9CP34000776; Tue, 23 Oct 2012 11:12:26 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Luigi Iannone'" <ggx@gigix.net>, "=?UTF-8?Q?'Mirko_Su=C5=BEnjevi=C4=87'?=" <Mirko.Suznjevic@fer.hr>
References: <007801cd9c9b$3b06d5a0$b11480e0$@unizar.es>	<A3179A2C9AAEE647BE70AC4C7881D5FB0167E5BC@sluga.fer.hr>	<4F8E71CE-F8DB-41A6-8803-9021C20A2A09@gigix.net> <A7C5E55A-422D-4E20-8E76-1025EF141F80@gigix.net>
In-Reply-To: <A7C5E55A-422D-4E20-8E76-1025EF141F80@gigix.net>
Date: Tue, 23 Oct 2012 11:12:27 +0200
Organization: Universidad de Zaragoza
Message-ID: <004e01cdb0fe$869b2a30$93d17e90$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_004F_01CDB10F.4A25A7E0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJpbWemvonwyxHJ/8KeqN5mdLxCRAK1Ml4dAx+7T7oBg6h8LJZUWz0w
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Next steps with 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: Tue, 23 Oct 2012 09:12:38 -0000

This is a multipart message in MIME format.

------=_NextPart_000_004F_01CDB10F.4A25A7E0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Luigi,

=20

I think the question is that only small packets can be multiplexed. =
Video broadcast uses 1500 bytes packets (just checked with Youtube and =
Wireshark)

=20

Radio broadcast may use 250bytes packets, so perhaps you could multiplex =
4 o 5 packets, but the saving is not very significant (just checked in =
http://www.cope.es/player/id=3D2011122307520001 =
<http://www.cope.es/player/id=3D2011122307520001&activo=3D5> =
&activo=3D5)

=20

In one-way broadcasts, 5 seconds are not critical, I think. But only =
small packets are interesting for TCMTF.

=20

Thanks,

=20

Jose

=20

=20

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de =
Luigi Iannone
Enviado el: martes, 23 de octubre de 2012 10:45
Para: Mirko Su=C5=BEnjevi=C4=87
CC: tcmtf@ietf.org
Asunto: Re: [tcmtf] Next steps with TCMTF

=20

Hi,

=20

On 23 Oct. 2012, at 10:14 , Mirko Su=C5=BEnjevi=C4=87 =
<Mirko.Suznjevic@fer.hr> wrote:





Hello all,







Regarding the b) "Recommendations draft" I have created a first summary =
of real-time services suitable for multiplexing.







In short I have analyzed the literature regarding:



1) 2-way audio video communications



2) Multiplayer gaming
3) Remote control





May I ask whether or not one way audio video communications should have =
their own category?







May be it falls already in 1), but I was thinking that Internet is the =
more and more used for live events (think about the olympics).



So a broadcaster may have agreements with other ISPs to use TCMTF to =
reduce bandwidth while transmitting these live events (that cannot be =
"downloaded" like other streaming videos, they just need to be =
"constantly" streamed as long as the event goes on).







Could be this something to add?







Luigi



















I will shortly just summarize the results without listing all sources.



Note: Under term latency one way delay is considered.







For 2-way audio and video communication ITU.T recommendations state that =
150ms latency is needed for completely unimpaired communication. =
Latencies up to 400ms can be tolerated, but their impact is noticeable.







Multiplayer gaming differs significantly on the genre.=20



The most demanding games are First Person Shooter (FPS) games which =
require between 80ms and 100ms delay for unimpaired experience.



Some studies claim that Thrid Person Avatar games from which the most =
common are Role Playing Games (RPGs) and Massively Multiplayer =
Role-Playing Games MMORPGs tolerate latencies up to 500ms, but other =
studies state that a more realistic values for unimpaired MMORPG =
experience is between 120 and 200ms.



As for omnipresent games such as Real Time Strategies (RTS) it is stated =
that latencies up to 500ms and even up to 1000ms do not impair user =
performance on objective metrics, but the evidence from RTS game forums =
suggests that users are quite unsatisfied with latencies above 300ms.







Remote control has different values of latency for different services as =
well. Remote surgery is stated that 330ms latency is acceptable, but for =
controlling a robot in scope of end-to-end tele-echography showed that =
only latencies under 150ms are acceptable.







What do you think is there a possibility to make an extended version of =
such a document and submit it as a draft?







Thanks for any feedback!







Mirko Suznjevic







-----Original Message-----



From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =
Of Jose Saldana



Sent: Thursday, September 27, 2012 12:31 PM



To: tcmtf@ietf.org



Cc: Wesley Eddy; Martin Stiemerling



Subject: [tcmtf] Next steps with TCMTF







Hello all,







I would like to discuss in this list the possibility of creating a small =
Working Group for TCMTF, as suggested by Wes. It could have the task of =
making a RFC from TCMTF, or a wider scope. I think that perhaps more =
than a draft would be necessary. I mean, I have been thinking about it, =
and perhaps the work could be divided into the next parts:







a) "Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03), =
including the protocol stack of TCMTF. The current proposal has =
different options, but the concrete one to use is static: in the set-up =
moment, you decide that "between these two routers a tunnel is set =
including all the packets with this IP origin and destination".







b) "Recommendations draft": another "informational" one, with =
recommendations of maximum delays to be added to different kinds of =
services, different multiplexing policies, implementation issues related =
to the selection of the best compression algorithm to use, etc. Some =
hypothetical examples:



    -  "if you are multiplexing a First Person Shooter, your multiplexer =
should not retain packets more than 50 ms"



- "if you are multiplexing in a low-end router in a wired scenario, you =
don't need to use ROHC. A simpler scheme like IPHC can be enough, and it =
will not require a lot of processing capacity".







c) "Dynamic Signaling draft": perhaps another one including a signaling =
system in order to:



          - dynamically "negotiate" the concrete options of TCMTF you =
are going to use



          - if two routers notice that a rush hour is arriving, they =
could send some packets asking other routers if they have some flows in =
common with them, which could be multiplexed.











The main questions are:







Is this enough for creating a working group?







Do you think the distribution of the work into three draft makes sense?







Is there any other issue which should be studied and standardized? =
Perhaps other people could imagine more things.







So let's start the discussion.







Thanks in advance,







Jose=20











_______________________________________________



tcmtf mailing list



tcmtf@ietf.org



https://www.ietf.org/mailman/listinfo/tcmtf



_______________________________________________



tcmtf mailing list



tcmtf@ietf.org
https://www.ietf.org/mailman/listinfo/tcmtf

=20

=20


------=_NextPart_000_004F_01CDB10F.4A25A7E0
Content-Type: text/html;
	charset="UTF-8"
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=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Luigi,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I think the question is that only small packets can be multiplexed. =
Video broadcast uses 1500 bytes packets (just checked with Youtube and =
Wireshark)<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Radio broadcast may use 250bytes packets, so perhaps you could =
multiplex 4 o 5 packets, but the saving is not very significant (just =
checked in <a =
href=3D"http://www.cope.es/player/id=3D2011122307520001&amp;activo=3D5">h=
ttp://www.cope.es/player/id=3D2011122307520001&amp;activo=3D5</a>)<o:p></=
o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>In one-way broadcasts, 5 seconds are not critical, I think. But only =
small packets are interesting for TCMTF.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jose<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] <b>En =
nom</b></span><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>bre de =
</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Luigi =
Iannone<br><b>Enviado el:</b> martes, 23 de octubre de 2012 =
10:45<br><b>Para:</b> Mirko Su=C5=BEnjevi=C4=87<br><b>CC:</b> =
tcmtf@ietf.org<br><b>Asunto:</b> Re: [tcmtf] Next steps with =
TCMTF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>Hi,<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
23 Oct. 2012, at 10:14 , Mirko Su=C5=BEnjevi=C4=87 &lt;<a =
href=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt; =
wrote:<o:p></o:p></p></div><p class=3DMsoNormal><span =
style=3D'color:#0F61C8'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Hello all,<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Regarding the b) &quot;Recommendations draft&quot; I =
have created a first summary of real-time services suitable for =
multiplexing.<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>In short I have analyzed the literature =
regarding:<br><br><o:p></o:p></p><p class=3DMsoNormal>1) 2-way audio =
video communications<br><br><o:p></o:p></p><p class=3DMsoNormal>2) =
Multiplayer gaming<br>3) Remote control<o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#0F61C8'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>May I ask whether or not one way audio video =
communications should have their own category?<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#0F61C8'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>May be it falls already in 1), but I was thinking that =
Internet is the more and more used for live events (think about the =
olympics).<br><br><o:p></o:p></p><p class=3DMsoNormal>So a broadcaster =
may have agreements with other ISPs to use TCMTF to reduce bandwidth =
while transmitting these live events (that cannot be =
&quot;downloaded&quot; like other streaming videos, they just need to be =
&quot;constantly&quot; streamed as long as the event goes =
on).<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#0F61C8'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Could be this something to =
add?<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#0F61C8'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Luigi<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#0F61C8'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#0F61C8'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#0F61C8'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>I will shortly just summarize the results without =
listing all sources.<br><br><o:p></o:p></p><p class=3DMsoNormal>Note: =
Under term latency one way delay is considered.<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>For 2-way audio and video communication ITU.T =
recommendations state that 150ms latency is needed for completely =
unimpaired communication. Latencies up to 400ms can be tolerated, but =
their impact is noticeable.<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Multiplayer gaming differs significantly on the =
genre.&nbsp;<br><br><o:p></o:p></p><p class=3DMsoNormal>The most =
demanding games are First Person Shooter (FPS) games which require =
between 80ms and 100ms delay for unimpaired =
experience.<br><br><o:p></o:p></p><p class=3DMsoNormal>Some studies =
claim that Thrid Person Avatar games from which the most common are Role =
Playing Games (RPGs) and Massively Multiplayer Role-Playing Games =
MMORPGs tolerate latencies up to 500ms, but other studies state that a =
more realistic values for unimpaired MMORPG experience is between 120 =
and 200ms.<br><br><o:p></o:p></p><p class=3DMsoNormal>As for omnipresent =
games such as Real Time Strategies (RTS) it is stated that latencies up =
to 500ms and even up to 1000ms do not impair user performance on =
objective metrics, but the evidence from RTS game forums suggests that =
users are quite unsatisfied with latencies above =
300ms.<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Remote control has different values of latency for =
different services as well. Remote surgery is stated that 330ms latency =
is acceptable, but for controlling a robot in scope of end-to-end =
tele-echography showed that only latencies under 150ms are =
acceptable.<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>What do you think is there a possibility to make an =
extended version of such a document and submit it as a =
draft?<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Thanks for any feedback!<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Mirko Suznjevic<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>-----Original Message-----<br><br><o:p></o:p></p><p =
class=3DMsoNormal>From: <a =
href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> =
[mailto:tcmtf-<a href=3D"mailto:bounces@ietf.org">bounces@ietf.org</a>] =
On Behalf Of Jose Saldana<br><br><o:p></o:p></p><p =
class=3DMsoNormal>Sent: Thursday, September 27, 2012 12:31 =
PM<br><br><o:p></o:p></p><p class=3DMsoNormal>To: <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><br><o:p></o:p></p><=
p class=3DMsoNormal>Cc: Wesley Eddy; Martin =
Stiemerling<br><br><o:p></o:p></p><p class=3DMsoNormal>Subject: [tcmtf] =
Next steps with TCMTF<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Hello all,<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>I would like to discuss in this list the possibility =
of creating a small Working Group for TCMTF, as suggested by Wes. It =
could have the task of making a RFC from TCMTF, or a wider scope. I =
think that perhaps more than a draft would be necessary. I mean, I have =
been thinking about it, and perhaps the work could be divided into the =
next parts:<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>a) &quot;Current draft&quot;: the main draft =
(draft-saldana-tsvwg-tcmtf-03), including the protocol stack of TCMTF. =
The current proposal has different options, but the concrete one to use =
is static: in the set-up moment, you decide that &quot;between these two =
routers a tunnel is set including all the packets with this IP origin =
and destination&quot;.<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>b) &quot;Recommendations draft&quot;: another =
&quot;informational&quot; one, with recommendations of maximum delays to =
be added to different kinds of services, different multiplexing =
policies, implementation issues related to the selection of the best =
compression algorithm to use, etc. Some hypothetical =
examples:<br><br><o:p></o:p></p><p class=3DMsoNormal>&nbsp; &nbsp; - =
&nbsp;&quot;if you are multiplexing a First Person Shooter, your =
multiplexer should not retain packets more than 50 =
ms&quot;<br><br><o:p></o:p></p><p class=3DMsoNormal>- &quot;if you are =
multiplexing in a low-end router in a wired scenario, you don't need to =
use ROHC. A simpler scheme like IPHC can be enough, and it will not =
require a lot of processing capacity&quot;.<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>c) &quot;Dynamic Signaling draft&quot;: perhaps =
another one including a signaling system in order =
to:<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
class=3Dapple-tab-span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 </span>- dynamically &quot;negotiate&quot; the concrete options of =
TCMTF you are going to use<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
class=3Dapple-tab-span>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 </span>- if two routers notice that a rush hour is arriving, they =
could send some packets asking other routers if they have some flows in =
common with them, which could be multiplexed.<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>The main questions are:<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Is this enough for creating a working =
group?<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Do you think the distribution of the work into three =
draft makes sense?<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Is there any other issue which should be studied and =
standardized? Perhaps other people could imagine more =
things.<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>So let's start the =
discussion.<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Thanks in advance,<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>Jose&nbsp;<br><br><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#007316'><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>_______________________________________________<br><br>=
<o:p></o:p></p><p class=3DMsoNormal>tcmtf mailing =
list<br><br><o:p></o:p></p><p class=3DMsoNormal><a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><br><o:p></o:p></p><=
p =
class=3DMsoNormal>https://www.ietf.org/mailman/listinfo/tcmtf<br><br><o:p=
></o:p></p><p =
class=3DMsoNormal>_______________________________________________<br><br>=
<o:p></o:p></p><p class=3DMsoNormal>tcmtf mailing =
list<br><br><o:p></o:p></p><p =
class=3DMsoNormal>tcmtf@ietf.org<br>https://www.ietf.org/mailman/listinfo=
/tcmtf<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_004F_01CDB10F.4A25A7E0--


From fpb@tid.es  Tue Oct 23 07:29:34 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 94DF21F0C54 for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 07:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.14
X-Spam-Level: 
X-Spam-Status: No, score=-6.14 tagged_above=-999 required=5 tests=[AWL=0.158,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i5deWU6bRjzc for <tcmtf@ietfa.amsl.com>; Tue, 23 Oct 2012 07:29:32 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 84BB11F0C49 for <tcmtf@ietf.org>; Tue, 23 Oct 2012 07:29:29 -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 <0MCC008NWO93QC@tid.hi.inet> for tcmtf@ietf.org; Tue, 23 Oct 2012 16:29:28 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id A5.1A.05494.5C9A6805; Tue, 23 Oct 2012 16:29:25 +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 <0MCC008NLO91QC@tid.hi.inet> for tcmtf@ietf.org; Tue, 23 Oct 2012 16:29:25 +0200 (MEST)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.178]) by ex10-htcas3-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Tue, 23 Oct 2012 16:29:25 +0200
Date: Tue, 23 Oct 2012 14:29:24 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <004e01cdb0fe$869b2a30$93d17e90$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, 'Luigi Iannone' <ggx@gigix.net>, =?iso-8859-2?Q?=27Mirko_Su=BEnjevi=E6=27?= <Mirko.Suznjevic@fer.hr>
Message-id: <F5EDC35DF914C1428C28E149F10463A24C746627@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_QevidpK+ObcJ0rXg8s8JVA)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: [tcmtf] Next steps with TCMTF
Thread-index: Ac2cmrry4BaRIpi1Sm27mcZI4g4aKwUW4ybwAAEEIav//+bTgIAAeeoA
user-agent: Microsoft-MacOutlook/14.2.4.120824
X-AuditID: 0a5f4e69-b7fc06d000001576-fd-5086a9c5975d
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrFKsWRmVeSWpSXmKPExsXCFe9nqHtsZVuAwf7N0ha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxsfuqYwFT08wVjxef4a5gfHSasYuRk4OCQETiZ17FjJB2GIS F+6tZ+ti5OIQEtjOKLH2yxlmCOcno8TTi/sYIZyZjBLbbi5iAWlhEVCVWDL7CyuIzSagJXH6 7iqgOAeHMJB95ps6SJhTwELi+IQuqG0KEn/OPQZrFRGYyiixYGsJSDkz0Jh53xRBwrwC3hLb lu1ng7AFJX5MvgdWziyQKzF7zRFmCFtcorn1JlicEejo76fWMEGM1Jb4+e0TG4TtJnH2/COw GlEBPYkFuw8yQ5wgILFkz3koW1Ti5eN/rBMYxWYhWTcLybpZSNZB2HoSz07NgrK1JZYtfA1V oytx6eE6VgjbTGLqq/PMyGoWMHKsYhQrTirKTM8oyU3MzEk3MNLLyNTLzEst2cQIicjMHYzL d6ocYhTgYFTi4X1xojVAiDWxrLgy9xCjJAeTkihv+oq2ACG+pPyUyozE4oz4otKc1OJDjBIc zEoivKb2QDnelMTKqtSifJiUDAeHkgTvyeVAKcGi1PTUirTMHGDagUkzcXCCtPMAtVeAjOYt LkjMLc5Mh8ifYpSUEuc9AtIsAJLIKM2D633FKA50pDDvdZAsDzBBwnW9AhrIBDTQnKcVZGBJ IkJKqoGx/umh/+vVf/zg0losIZ7x8d/upfJdPt1tBVNCL3TO3Te9mWtSyYSdK38l/L6gIHyp Z0pRtFZW2Ql/9YiSnUmsYZdit4ezO0tlTs3zlN0ydYVr446Lx72Yv76NeMp5Kv/tk80bGhvb r1tu6RRe82keC4NTgt0/qa07Fj3x6D3q7895f3H2T6+3SizFGYmGWsxFxYkAt6sCyk0DAAA=
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Next steps with 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, 23 Oct 2012 14:29:34 -0000

--Boundary_(ID_QevidpK+ObcJ0rXg8s8JVA)
Content-type: text/plain; charset=iso-8859-2
Content-transfer-encoding: quoted-printable

Hi all,

Maybe in the 2-way audio-video case video is also out of scope: packets are=
 not very small. They usually use different RTP flows, 4 flows in total for=
 a 2-way audio video communications (2 flows in every direction). So, shoul=
d be focused in audio?

Regards from Darmstadt,

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

From: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.es<m=
ailto:jsaldana@unizar.es>>
Organization: Universidad de Zaragoza
Reply-To: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.=
es<mailto:jsaldana@unizar.es>>
Date: martes, 23 de octubre de 2012 11:12
To: Luigi Iannone <ggx@gigix.net<mailto:ggx@gigix.net>>, 'Mirko Su=BEnjevi=
=E6' <Mirko.Suznjevic@fer.hr<mailto:Mirko.Suznjevic@fer.hr>>
Cc: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Subject: Re: [tcmtf] Next steps with TCMTF

Luigi,

I think the question is that only small packets can be multiplexed. Video b=
roadcast uses 1500 bytes packets (just checked with Youtube and Wireshark)

Radio broadcast may use 250bytes packets, so perhaps you could multiplex 4 =
o 5 packets, but the saving is not very significant (just checked in http:/=
/www.cope.es/player/id=3D2011122307520001&activo=3D5)

In one-way broadcasts, 5 seconds are not critical, I think. But only small =
packets are interesting for TCMTF.

Thanks,

Jose


De: tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-bou=
nces@ietf.org] En nombre de Luigi Iannone
Enviado el: martes, 23 de octubre de 2012 10:45
Para: Mirko Su=BEnjevi=E6
CC: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: Re: [tcmtf] Next steps with TCMTF

Hi,

On 23 Oct. 2012, at 10:14 , Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr<mai=
lto:Mirko.Suznjevic@fer.hr>> wrote:


Hello all,



Regarding the b) "Recommendations draft" I have created a first summary of =
real-time services suitable for multiplexing.



In short I have analyzed the literature regarding:

1) 2-way audio video communications

2) Multiplayer gaming
3) Remote control


May I ask whether or not one way audio video communications should have the=
ir own category?



May be it falls already in 1), but I was thinking that Internet is the more=
 and more used for live events (think about the olympics).

So a broadcaster may have agreements with other ISPs to use TCMTF to reduce=
 bandwidth while transmitting these live events (that cannot be "downloaded=
" like other streaming videos, they just need to be "constantly" streamed a=
s long as the event goes on).



Could be this something to add?



Luigi









I will shortly just summarize the results without listing all sources.

Note: Under term latency one way delay is considered.



For 2-way audio and video communication ITU.T recommendations state that 15=
0ms latency is needed for completely unimpaired communication. Latencies up=
 to 400ms can be tolerated, but their impact is noticeable.



Multiplayer gaming differs significantly on the genre.

The most demanding games are First Person Shooter (FPS) games which require=
 between 80ms and 100ms delay for unimpaired experience.

Some studies claim that Thrid Person Avatar games from which the most commo=
n are Role Playing Games (RPGs) and Massively Multiplayer Role-Playing Game=
s MMORPGs tolerate latencies up to 500ms, but other studies state that a mo=
re realistic values for unimpaired MMORPG experience is between 120 and 200=
ms.

As for omnipresent games such as Real Time Strategies (RTS) it is stated th=
at latencies up to 500ms and even up to 1000ms do not impair user performan=
ce on objective metrics, but the evidence from RTS game forums suggests tha=
t users are quite unsatisfied with latencies above 300ms.



Remote control has different values of latency for different services as we=
ll. Remote surgery is stated that 330ms latency is acceptable, but for cont=
rolling a robot in scope of end-to-end tele-echography showed that only lat=
encies under 150ms are acceptable.



What do you think is there a possibility to make an extended version of suc=
h a document and submit it as a draft?



Thanks for any feedback!



Mirko Suznjevic



-----Original Message-----

From: tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-b=
ounces@ietf.org<mailto:bounces@ietf.org>] On Behalf Of Jose Saldana

Sent: Thursday, September 27, 2012 12:31 PM

To: tcmtf@ietf.org<mailto:tcmtf@ietf.org>

Cc: Wesley Eddy; Martin Stiemerling

Subject: [tcmtf] Next steps with TCMTF



Hello all,



I would like to discuss in this list the possibility of creating a small Wo=
rking Group for TCMTF, as suggested by Wes. It could have the task of makin=
g a RFC from TCMTF, or a wider scope. I think that perhaps more than a draf=
t would be necessary. I mean, I have been thinking about it, and perhaps th=
e work could be divided into the next parts:



a) "Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03), includin=
g the protocol stack of TCMTF. The current proposal has different options, =
but the concrete one to use is static: in the set-up moment, you decide tha=
t "between these two routers a tunnel is set including all the packets with=
 this IP origin and destination".



b) "Recommendations draft": another "informational" one, with recommendatio=
ns of maximum delays to be added to different kinds of services, different =
multiplexing policies, implementation issues related to the selection of th=
e best compression algorithm to use, etc. Some hypothetical examples:

    -  "if you are multiplexing a First Person Shooter, your multiplexer sh=
ould not retain packets more than 50 ms"

- "if you are multiplexing in a low-end router in a wired scenario, you don=
't need to use ROHC. A simpler scheme like IPHC can be enough, and it will =
not require a lot of processing capacity".



c) "Dynamic Signaling draft": perhaps another one including a signaling sys=
tem in order to:

          - dynamically "negotiate" the concrete options of TCMTF you are g=
oing to use

          - if two routers notice that a rush hour is arriving, they could =
send some packets asking other routers if they have some flows in common wi=
th them, which could be multiplexed.





The main questions are:



Is this enough for creating a working group?



Do you think the distribution of the work into three draft makes sense?



Is there any other issue which should be studied and standardized? Perhaps =
other people could imagine more things.



So let's start the discussion.



Thanks in advance,



Jose





_______________________________________________

tcmtf mailing list

tcmtf@ietf.org<mailto:tcmtf@ietf.org>

https://www.ietf.org/mailman/listinfo/tcmtf

_______________________________________________

tcmtf mailing list

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



________________________________

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

--Boundary_(ID_QevidpK+ObcJ0rXg8s8JVA)
Content-id: <E1B0110DBF7C3B47A593A58861F6CD9F@hi.inet>
Content-type: text/html; charset=iso-8859-2
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
2">
</head>
<body style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font=
-family:Calibri,sans-serif">
<div>
<div>
<div>Hi all,</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Maybe =
in the 2-way audio-video case video is also out of scope: packets are not v=
ery small. They usually use different RTP flows, 4 flows in total for a 2-w=
ay audio video communications (2 flows
 in every direction). So, should be focused in audio?</div>
<div>
<div><br>
</div>
<div>Regards from Darmstadt,</div>
<div><br>
</div>
<div>Fernando Pascual Blanco</div>
<div>Telef=F3nica Global Resources</div>
<div>Network Automation and Dynamization</div>
<div>TECHNOLOGY PEOPLE GROUP</div>
<div>F &#43;34913128779</div>
<div>M &#43;34682005168</div>
<div>fpb@tid.es</div>
</div>
</div>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; border-bottom:medium none; border-left:medium none; padding-bottom:0i=
n; padding-left:0in; padding-right:0in; border-top:#b5c4df 1pt solid; borde=
r-right:medium none; padding-top:3pt">
<span style=3D"font-weight:bold">From: </span>&quot;<a href=3D"mailto:jsald=
ana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsaldana@=
unizar.es">jsaldana@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Organization: </span>Universidad de Zarago=
za<br>
<span style=3D"font-weight:bold">Reply-To: </span>&quot;<a href=3D"mailto:j=
saldana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsald=
ana@unizar.es">jsaldana@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>martes, 23 de octubre de 2012=
 11:12<br>
<span style=3D"font-weight:bold">To: </span>Luigi Iannone &lt;<a href=3D"ma=
ilto:ggx@gigix.net">ggx@gigix.net</a>&gt;, 'Mirko Su=BEnjevi=E6' &lt;<a hre=
f=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:tcmtf@i=
etf.org">tcmtf@ietf.org</a>&quot; &lt;<a href=3D"mailto:tcmtf@ietf.org">tcm=
tf@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [tcmtf] Next steps wit=
h TCMTF<br>
</div>
<div><br>
</div>
<div><style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
span.apple-tab-span
	{}
span.EstiloCorreo18
	{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>
<div lang=3D"ES">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">Luigi,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">I think the question is tha=
t only small packets can be multiplexed. Video broadcast uses 1500 bytes pa=
ckets (just checked with Youtube and Wireshark)</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">Radio broadcast may use 250=
bytes packets, so perhaps you could multiplex 4 o 5 packets, but the saving=
 is not very significant (just checked
 in <a href=3D"http://www.cope.es/player/id=3D2011122307520001&amp;activo=
=3D5">http://www.cope.es/player/id=3D2011122307520001&amp;activo=3D5</a>)</=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">In one-way broadcasts, 5 se=
conds are not critical, I think. But only small packets are interesting for=
 TCMTF.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">Thanks,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">Jose</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11pt; font-f=
amily:Calibri,sans-serif; color:rgb(31,73,125)">&nbsp;</span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0cm 0cm 0c=
m 4.0pt">
<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:10pt; fon=
t-family:Tahoma,sans-serif">De:</span></b><span lang=3D"EN-US" style=3D"fon=
t-size:10pt; font-family:Tahoma,sans-serif">
<a href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a hr=
ef=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]
<b>En nom</b></span><b><span style=3D"font-size:10pt; font-family:Tahoma,sa=
ns-serif">bre de
</span></b><span style=3D"font-size:10pt; font-family:Tahoma,sans-serif">Lu=
igi Iannone<br>
<b>Enviado el:</b> martes, 23 de octubre de 2012 10:45<br>
<b>Para:</b> Mirko Su=BEnjevi=E6<br>
<b>CC:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> Re: [tcmtf] Next steps with TCMTF</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<div>
<p class=3D"MsoNormal">Hi,</p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;</p>
<div>
<div>
<p class=3D"MsoNormal">On 23 Oct. 2012, at 10:14 , Mirko Su=BEnjevi=E6 &lt;=
<a href=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt; wr=
ote:</p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#0F61C8"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Hello all,<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Regarding the b) &quot;Recommendations draft&quot; I=
 have created a first summary of real-time services suitable for multiplexi=
ng.<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">In short I have analyzed the literature regarding:<b=
r>
<br>
</p>
<p class=3D"MsoNormal">1) 2-way audio video communications<br>
<br>
</p>
<p class=3D"MsoNormal">2) Multiplayer gaming<br>
3) Remote control</p>
<p class=3D"MsoNormal"><span style=3D"color:#0F61C8"><br>
<br>
</span></p>
<p class=3D"MsoNormal">May I ask whether or not one way audio video communi=
cations should have their own category?<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#0F61C8"><br>
<br>
</span></p>
<p class=3D"MsoNormal">May be it falls already in 1), but I was thinking th=
at Internet is the more and more used for live events (think about the olym=
pics).<br>
<br>
</p>
<p class=3D"MsoNormal">So a broadcaster may have agreements with other ISPs=
 to use TCMTF to reduce bandwidth while transmitting these live events (tha=
t cannot be &quot;downloaded&quot; like other streaming videos, they just n=
eed to be &quot;constantly&quot; streamed as long as the
 event goes on).<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#0F61C8"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Could be this something to add?<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#0F61C8"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Luigi<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#0F61C8"><br>
<br>
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#0F61C8"><br>
<br>
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#0F61C8"><br>
<br>
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">I will shortly just summarize the results without li=
sting all sources.<br>
<br>
</p>
<p class=3D"MsoNormal">Note: Under term latency one way delay is considered=
.<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">For 2-way audio and video communication ITU.T recomm=
endations state that 150ms latency is needed for completely unimpaired comm=
unication. Latencies up to 400ms can be tolerated, but their impact is noti=
ceable.<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Multiplayer gaming differs significantly on the genr=
e.&nbsp;<br>
<br>
</p>
<p class=3D"MsoNormal">The most demanding games are First Person Shooter (F=
PS) games which require between 80ms and 100ms delay for unimpaired experie=
nce.<br>
<br>
</p>
<p class=3D"MsoNormal">Some studies claim that Thrid Person Avatar games fr=
om which the most common are Role Playing Games (RPGs) and Massively Multip=
layer Role-Playing Games MMORPGs tolerate latencies up to 500ms, but other =
studies state that a more realistic
 values for unimpaired MMORPG experience is between 120 and 200ms.<br>
<br>
</p>
<p class=3D"MsoNormal">As for omnipresent games such as Real Time Strategie=
s (RTS) it is stated that latencies up to 500ms and even up to 1000ms do no=
t impair user performance on objective metrics, but the evidence from RTS g=
ame forums suggests that users are
 quite unsatisfied with latencies above 300ms.<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Remote control has different values of latency for d=
ifferent services as well. Remote surgery is stated that 330ms latency is a=
cceptable, but for controlling a robot in scope of end-to-end tele-echograp=
hy showed that only latencies under
 150ms are acceptable.<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">What do you think is there a possibility to make an =
extended version of such a document and submit it as a draft?<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Thanks for any feedback!<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Mirko Suznjevic<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">-----Original Message-----<br>
<br>
</p>
<p class=3D"MsoNormal">From: <a href=3D"mailto:tcmtf-bounces@ietf.org">tcmt=
f-bounces@ietf.org</a> [<a href=3D"mailto:tcmtf-">mailto:tcmtf-</a><a href=
=3D"mailto:bounces@ietf.org">bounces@ietf.org</a>] On Behalf Of Jose Saldan=
a<br>
<br>
</p>
<p class=3D"MsoNormal">Sent: Thursday, September 27, 2012 12:31 PM<br>
<br>
</p>
<p class=3D"MsoNormal">To: <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org=
</a><br>
<br>
</p>
<p class=3D"MsoNormal">Cc: Wesley Eddy; Martin Stiemerling<br>
<br>
</p>
<p class=3D"MsoNormal">Subject: [tcmtf] Next steps with TCMTF<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Hello all,<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">I would like to discuss in this list the possibility=
 of creating a small Working Group for TCMTF, as suggested by Wes. It could=
 have the task of making a RFC from TCMTF, or a wider scope. I think that p=
erhaps more than a draft would be
 necessary. I mean, I have been thinking about it, and perhaps the work cou=
ld be divided into the next parts:<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">a) &quot;Current draft&quot;: the main draft (draft-=
saldana-tsvwg-tcmtf-03), including the protocol stack of TCMTF. The current=
 proposal has different options, but the concrete one to use is static: in =
the set-up moment, you decide that &quot;between
 these two routers a tunnel is set including all the packets with this IP o=
rigin and destination&quot;.<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">b) &quot;Recommendations draft&quot;: another &quot;=
informational&quot; one, with recommendations of maximum delays to be added=
 to different kinds of services, different multiplexing policies, implement=
ation issues related to the selection of the best compression
 algorithm to use, etc. Some hypothetical examples:<br>
<br>
</p>
<p class=3D"MsoNormal">&nbsp; &nbsp; - &nbsp;&quot;if you are multiplexing =
a First Person Shooter, your multiplexer should not retain packets more tha=
n 50 ms&quot;<br>
<br>
</p>
<p class=3D"MsoNormal">- &quot;if you are multiplexing in a low-end router =
in a wired scenario, you don't need to use ROHC. A simpler scheme like IPHC=
 can be enough, and it will not require a lot of processing capacity&quot;.=
<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">c) &quot;Dynamic Signaling draft&quot;: perhaps anot=
her one including a signaling system in order to:<br>
<br>
</p>
<p class=3D"MsoNormal"><span class=3D"apple-tab-span">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>- dynamically &quot;negotiate&quot=
; the concrete options of TCMTF you are going to use<br>
<br>
</p>
<p class=3D"MsoNormal"><span class=3D"apple-tab-span">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>- if two routers notice that a rus=
h hour is arriving, they could send some packets asking other routers if th=
ey have some flows in common with them, which could be multiplexed.<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">The main questions are:<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Is this enough for creating a working group?<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Do you think the distribution of the work into three=
 draft makes sense?<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Is there any other issue which should be studied and=
 standardized? Perhaps other people could imagine more things.<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">So let's start the discussion.<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Thanks in advance,<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">Jose&nbsp;<br>
<br>
</p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#007316"><br>
<br>
</span></p>
<p class=3D"MsoNormal">_______________________________________________<br>
<br>
</p>
<p class=3D"MsoNormal">tcmtf mailing list<br>
<br>
</p>
<p class=3D"MsoNormal"><a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>=
<br>
<br>
</p>
<p class=3D"MsoNormal"><a href=3D"https://www.ietf.org/mailman/listinfo/tcm=
tf">https://www.ietf.org/mailman/listinfo/tcmtf</a><br>
<br>
</p>
<p class=3D"MsoNormal">_______________________________________________<br>
<br>
</p>
<p class=3D"MsoNormal">tcmtf mailing list<br>
<br>
</p>
<p class=3D"MsoNormal"><a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>=
<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf">https://www.ietf.or=
g/mailman/listinfo/tcmtf</a></p>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
</div>
</div>
</div>
</span><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_QevidpK+ObcJ0rXg8s8JVA)--

From navajas@unizar.es  Wed Oct 24 02:00:37 2012
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B373B21F8A2F for <tcmtf@ietfa.amsl.com>; Wed, 24 Oct 2012 02:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.299
X-Spam-Level: 
X-Spam-Status: No, score=-7.299 tagged_above=-999 required=5 tests=[AWL=-0.999, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bIqTwgvtDQBf for <tcmtf@ietfa.amsl.com>; Wed, 24 Oct 2012 02:00:37 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 92B8621F8A2A for <tcmtf@ietf.org>; Wed, 24 Oct 2012 02:00:36 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id q9O90Vb6008153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Wed, 24 Oct 2012 11:00:32 +0200
Message-ID: <5087AE2E.3040303@unizar.es>
Date: Wed, 24 Oct 2012 11:00:30 +0200
From: =?ISO-8859-15?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <007801cd9c9b$3b06d5a0$b11480e0$@unizar.es> <A3179A2C9AAEE647BE70AC4C7881D5FB0167E5BC@sluga.fer.hr> <003601cdb0f8$04f119a0$0ed34ce0$@unizar.es>
In-Reply-To: <003601cdb0f8$04f119a0$0ed34ce0$@unizar.es>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Next steps with 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, 24 Oct 2012 09:00:37 -0000

hello all,
Regarding the real-time services suitable for multiplexing, i have a 
question about the third of them, remote control. I can't think a use 
case that transmits little packets in order to be multiplexed. Mirko 
suggests tele-echography but it no seems a use case that traffic needs 
multiplexion because there are not a lot of users simultaneusly.
Let us thinking about remote control and the possible use cases that can 
be presented here.

Julián




El 23/10/2012 10:25, Jose Saldana escribió:
> Mirko,
>
> This sounds really good!. This was the idea of "draft b)".
>
> Do you think you have included all the services which can be multiplexed
> with TCMTF? I mean: small packets and high overhead. Some ideas: sensor
> networks sending a sample, video-surveillance, whatsapp-like applications?
> Although some of them are not real-time, perhaps they can also be
> multiplexed if the number of packets per second is big.
>
> So perhaps a section enumerating non real-time applications with small
> packets could also be interesting: for example "instant messaging
> applications can tolerate up to 5 seconds of delay" (I have just invented
> the figure, it's only an example).
>
> I could help you with this, if you agree, of course.
>
> Thanks,
>
> Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Mirko Su¸njevic
>> Enviado el: martes, 23 de octubre de 2012 10:14
>> Para: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] Next steps with TCMTF
>>
>> Hello all,
>>
>> Regarding the b) "Recommendations draft" I have created a first summary of
>> real-time services suitable for multiplexing.
>>
>> In short I have analyzed the literature regarding:
>> 1) 2-way audio video communications
>> 2) Multiplayer gaming
>> 3) Remote control
>>
>> I will shortly just summarize the results without listing all sources.
>> Note: Under term latency one way delay is considered.
>>
>> For 2-way audio and video communication ITU.T recommendations state that
>> 150ms latency is needed for completely unimpaired communication.
>> Latencies up to 400ms can be tolerated, but their impact is noticeable.
>>
>> Multiplayer gaming differs significantly on the genre.
>> The most demanding games are First Person Shooter (FPS) games which
>> require between 80ms and 100ms delay for unimpaired experience.
>> Some studies claim that Thrid Person Avatar games from which the most
>> common are Role Playing Games (RPGs) and Massively Multiplayer Role-
>> Playing Games MMORPGs tolerate latencies up to 500ms, but other studies
>> state that a more realistic values for unimpaired MMORPG experience is
>> between 120 and 200ms.
>> As for omnipresent games such as Real Time Strategies (RTS) it is stated
> that
>> latencies up to 500ms and even up to 1000ms do not impair user
>> performance on objective metrics, but the evidence from RTS game forums
>> suggests that users are quite unsatisfied with latencies above 300ms.
>>
>> Remote control has different values of latency for different services as
> well.
>> Remote surgery is stated that 330ms latency is acceptable, but for
> controlling
>> a robot in scope of end-to-end tele-echography showed that only latencies
>> under 150ms are acceptable.
>>
>> What do you think is there a possibility to make an extended version of
> such
>> a document and submit it as a draft?
>>
>> Thanks for any feedback!
>>
>> Mirko Suznjevic
>>
>> -----Original Message-----
>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
>> Of Jose Saldana
>> Sent: Thursday, September 27, 2012 12:31 PM
>> To: tcmtf@ietf.org
>> Cc: Wesley Eddy; Martin Stiemerling
>> Subject: [tcmtf] Next steps with TCMTF
>>
>> Hello all,
>>
>> I would like to discuss in this list the possibility of creating a small
> Working
>> Group for TCMTF, as suggested by Wes. It could have the task of making a
>> RFC from TCMTF, or a wider scope. I think that perhaps more than a draft
>> would be necessary. I mean, I have been thinking about it, and perhaps the
>> work could be divided into the next parts:
>>
>>   a) "Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03),
> including
>> the protocol stack of TCMTF. The current proposal has different options,
> but
>> the concrete one to use is static: in the set-up moment, you decide that
>> "between these two routers a tunnel is set including all the packets with
> this
>> IP origin and destination".
>>
>> b) "Recommendations draft": another "informational" one, with
>> recommendations of maximum delays to be added to different kinds of
>> services, different multiplexing policies, implementation issues related
> to the
>> selection of the best compression algorithm to use, etc. Some hypothetical
>> examples:
>>        -  "if you are multiplexing a First Person Shooter, your multiplexer
> should
>> not retain packets more than 50 ms"
>> - "if you are multiplexing in a low-end router in a wired scenario, you
> don't
>> need to use ROHC. A simpler scheme like IPHC can be enough, and it will
> not
>> require a lot of processing capacity".
>>
>> c) "Dynamic Signaling draft": perhaps another one including a signaling
>> system in order to:
>>   	- dynamically "negotiate" the concrete options of TCMTF you are
>> going to use
>>   	- if two routers notice that a rush hour is arriving, they could
> send
>> some packets asking other routers if they have some flows in common with
>> them, which could be multiplexed.
>>
>>
>> The main questions are:
>>
>> Is this enough for creating a working group?
>>
>> Do you think the distribution of the work into three draft makes sense?
>>
>> Is there any other issue which should be studied and standardized? Perhaps
>> other people could imagine more things.
>>
>> So let's start the discussion.
>>
>> Thanks in advance,
>>
>> Jose
>>
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>
>


From fpb@tid.es  Wed Oct 24 02:37:38 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 0FCBD21F8A07 for <tcmtf@ietfa.amsl.com>; Wed, 24 Oct 2012 02:37:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.153
X-Spam-Level: 
X-Spam-Status: No, score=-6.153 tagged_above=-999 required=5 tests=[AWL=0.146,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cqf-mTlVyEM6 for <tcmtf@ietfa.amsl.com>; Wed, 24 Oct 2012 02:37:36 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 8030621F89F4 for <tcmtf@ietf.org>; Wed, 24 Oct 2012 02:37:35 -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 <0MCE00KB85EI9U@tid.hi.inet> for tcmtf@ietf.org; Wed, 24 Oct 2012 11:37:34 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 68.60.05494.DD6B7805; Wed, 24 Oct 2012 11:37:33 +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 <0MCE00KBI5EL9U@tid.hi.inet> for tcmtf@ietf.org; Wed, 24 Oct 2012 11:37:33 +0200 (MEST)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.178]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0318.004; Wed, 24 Oct 2012 11:37:32 +0200
Date: Wed, 24 Oct 2012 09:37:32 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <5087AE2E.3040303@unizar.es>
X-Originating-IP: [10.95.64.115]
To: =?utf-8?B?SnVsacOhbiBGZXJuw6FuZGV6LU5hdmFqYXM=?= <navajas@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A24C74AB4F@EX10-MB1-MAD.hi.inet>
Content-id: <90C41BF3B3AC654C89C0B9B7FAF9118F@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Next steps with TCMTF
Thread-index: Ac2cmrry4BaRIpi1Sm27mcZI4g4aKwUW4ybw///h8wCAAZv/AIAAK92A
user-agent: Microsoft-MacOutlook/14.2.4.120824
X-AuditID: 0a5f4e69-b7fc06d000001576-b1-5087b6dda8f1
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprPKsWRmVeSWpSXmKPExsXCFe9nqHt3W3uAwdG7Zha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxtPzPewFH4Iqtq19x97A+CCgi5GTQ0LARGLxkzesELaYxIV7 69m6GLk4hAS2M0o0nnvPCuH8ZJS4PvkpO4Qzk1FiZ888sBYWAVWJ3scrmEBsNgEtidN3V7F0 MXJwCAPZZ76pg4Q5BTQlGt4fZ4fYoCDx59xjFhBbRCBX4tbpZrA4r4C3xLaXN5hBbGYBM4n9 D06wQcQFJX5Mvgc2kllAXWLKlFyIEnGJ5tabLBC2osS0RQ2MIDajgKzEu/nzWSHGa0v8/PaJ DcJ2k3ja3A22SlRAT2LB7oPMEOcISCzZcx7KFpV4+fgf6wRG8VlIrpiF5IpZCFfMQnLFLCRX LGBkXcUoVpxUlJmeUZKbmJmTbmCkl5Gpl5mXWrKJERJbmTsYl+9UOcQowMGoxMN74GJbgBBr YllxZe4hRkkOJiVRXsWt7QFCfEn5KZUZicUZ8UWlOanFhxglOJiVRHifrALK8aYkVlalFuXD pGQ4OJQkeKeDtAkWpaanVqRl5gATCEyaiYMTpJ0HqH0FSA1vcUFibnFmOkT+FKOklDhvF0hC ACSRUZoH1/uKURzoSGHePpAsDzDVwXW9AhrIBDTQnKcVZGBJIkJKqoFx3Q5DRxN99+Xlc84f vsH3ll92Ud7M6t/MEeYH6m/7dRmIGRw6evufu9/3oBVZh65YOOWXvj+kbCsSY31g/90Fov6Z JqXXV1gF3Oa+ra9myzFlgpBEa3aKnGKNQvOkmoWllyzn8x7mUHBj/WrRKq7/cxbPCybtbSs0 7ZWSUzqPHPBeumK7Yp0SS3FGoqEWc1FxIgABl6oVMgMAAA==
Subject: Re: [tcmtf] Next steps with 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, 24 Oct 2012 09:37:38 -0000

SGkgYWxsLA0KDQogICAgICAgIEFzIGEgZmlyc3QgdGhpbmtpbmcsIFJUU1AgcHJvdG9jb2wgaGF2
ZSBhIGNvbm5lY3Rpb24gY29udHJvbCBsYXllciB0aGF0DQpsZXQgY2xpZW50cyB0byByZW1vdGVs
eSBjb250cm9sIHN0cmVhbWluZyBzZXJ2ZXJzOiB0aGV5IGNhbiByZW1vdGVseSBwbGF5DQpvciBw
YXVzZSB0aGUgbWVkaWHigKYgSSBkb27CtHQga25vdyBpZiB0aGF0IHdvdWxkIGJlIGFuIGludGVy
ZXN0aW5nIHVzZSBjYXNlDQp3aGVuIG11bHRpcGxleGluZyB1c2VycyBjb25zdW1pbmcgbWVkaWEg
dW5kZXIgZGVtYW5kLg0KDQpSZWdhcmRzLA0KDQpGZXJuYW5kbyBQYXNjdWFsIEJsYW5jbw0KVGVs
ZWbDs25pY2EgR2xvYmFsIFJlc291cmNlcw0KTmV0d29yayBBdXRvbWF0aW9uIGFuZCBEeW5hbWl6
YXRpb24NClRFQ0hOT0xPR1kgUEVPUExFIEdST1VQDQpGICszNDkxMzEyODc3OQ0KTSArMzQ2ODIw
MDUxNjgNCmZwYkB0aWQuZXMNCg0KDQoNCg0KT24gMjQvMTAvMTIgMTE6MDAsICJKdWxpw6FuIEZl
cm7DoW5kZXotTmF2YWphcyIgPG5hdmFqYXNAdW5pemFyLmVzPiB3cm90ZToNCg0KPmhlbGxvIGFs
bCwNCj5SZWdhcmRpbmcgdGhlIHJlYWwtdGltZSBzZXJ2aWNlcyBzdWl0YWJsZSBmb3IgbXVsdGlw
bGV4aW5nLCBpIGhhdmUgYQ0KPnF1ZXN0aW9uIGFib3V0IHRoZSB0aGlyZCBvZiB0aGVtLCByZW1v
dGUgY29udHJvbC4gSSBjYW4ndCB0aGluayBhIHVzZQ0KPmNhc2UgdGhhdCB0cmFuc21pdHMgbGl0
dGxlIHBhY2tldHMgaW4gb3JkZXIgdG8gYmUgbXVsdGlwbGV4ZWQuIE1pcmtvDQo+c3VnZ2VzdHMg
dGVsZS1lY2hvZ3JhcGh5IGJ1dCBpdCBubyBzZWVtcyBhIHVzZSBjYXNlIHRoYXQgdHJhZmZpYyBu
ZWVkcw0KPm11bHRpcGxleGlvbiBiZWNhdXNlIHRoZXJlIGFyZSBub3QgYSBsb3Qgb2YgdXNlcnMg
c2ltdWx0YW5ldXNseS4NCj5MZXQgdXMgdGhpbmtpbmcgYWJvdXQgcmVtb3RlIGNvbnRyb2wgYW5k
IHRoZSBwb3NzaWJsZSB1c2UgY2FzZXMgdGhhdCBjYW4NCj5iZSBwcmVzZW50ZWQgaGVyZS4NCj4N
Cj5KdWxpw6FuDQo+DQo+DQo+DQo+DQo+RWwgMjMvMTAvMjAxMiAxMDoyNSwgSm9zZSBTYWxkYW5h
IGVzY3JpYmnDszoNCj4+IE1pcmtvLA0KPj4NCj4+IFRoaXMgc291bmRzIHJlYWxseSBnb29kIS4g
VGhpcyB3YXMgdGhlIGlkZWEgb2YgImRyYWZ0IGIpIi4NCj4+DQo+PiBEbyB5b3UgdGhpbmsgeW91
IGhhdmUgaW5jbHVkZWQgYWxsIHRoZSBzZXJ2aWNlcyB3aGljaCBjYW4gYmUgbXVsdGlwbGV4ZWQN
Cj4+IHdpdGggVENNVEY/IEkgbWVhbjogc21hbGwgcGFja2V0cyBhbmQgaGlnaCBvdmVyaGVhZC4g
U29tZSBpZGVhczogc2Vuc29yDQo+PiBuZXR3b3JrcyBzZW5kaW5nIGEgc2FtcGxlLCB2aWRlby1z
dXJ2ZWlsbGFuY2UsIHdoYXRzYXBwLWxpa2UNCj4+YXBwbGljYXRpb25zPw0KPj4gQWx0aG91Z2gg
c29tZSBvZiB0aGVtIGFyZSBub3QgcmVhbC10aW1lLCBwZXJoYXBzIHRoZXkgY2FuIGFsc28gYmUN
Cj4+IG11bHRpcGxleGVkIGlmIHRoZSBudW1iZXIgb2YgcGFja2V0cyBwZXIgc2Vjb25kIGlzIGJp
Zy4NCj4+DQo+PiBTbyBwZXJoYXBzIGEgc2VjdGlvbiBlbnVtZXJhdGluZyBub24gcmVhbC10aW1l
IGFwcGxpY2F0aW9ucyB3aXRoIHNtYWxsDQo+PiBwYWNrZXRzIGNvdWxkIGFsc28gYmUgaW50ZXJl
c3Rpbmc6IGZvciBleGFtcGxlICJpbnN0YW50IG1lc3NhZ2luZw0KPj4gYXBwbGljYXRpb25zIGNh
biB0b2xlcmF0ZSB1cCB0byA1IHNlY29uZHMgb2YgZGVsYXkiIChJIGhhdmUganVzdA0KPj5pbnZl
bnRlZA0KPj4gdGhlIGZpZ3VyZSwgaXQncyBvbmx5IGFuIGV4YW1wbGUpLg0KPj4NCj4+IEkgY291
bGQgaGVscCB5b3Ugd2l0aCB0aGlzLCBpZiB5b3UgYWdyZWUsIG9mIGNvdXJzZS4NCj4+DQo+PiBU
aGFua3MsDQo+Pg0KPj4gSm9zZQ0KPj4NCj4+PiAtLS0tLU1lbnNhamUgb3JpZ2luYWwtLS0tLQ0K
Pj4+IERlOiB0Y210Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86dGNtdGYtYm91bmNlc0BpZXRm
Lm9yZ10gRW4gbm9tYnJlIGRlDQo+Pj4gTWlya28gU3XFvm5qZXZpYw0KPj4+IEVudmlhZG8gZWw6
IG1hcnRlcywgMjMgZGUgb2N0dWJyZSBkZSAyMDEyIDEwOjE0DQo+Pj4gUGFyYTogdGNtdGZAaWV0
Zi5vcmcNCj4+PiBBc3VudG86IFJlOiBbdGNtdGZdIE5leHQgc3RlcHMgd2l0aCBUQ01URg0KPj4+
DQo+Pj4gSGVsbG8gYWxsLA0KPj4+DQo+Pj4gUmVnYXJkaW5nIHRoZSBiKSAiUmVjb21tZW5kYXRp
b25zIGRyYWZ0IiBJIGhhdmUgY3JlYXRlZCBhIGZpcnN0DQo+Pj5zdW1tYXJ5IG9mDQo+Pj4gcmVh
bC10aW1lIHNlcnZpY2VzIHN1aXRhYmxlIGZvciBtdWx0aXBsZXhpbmcuDQo+Pj4NCj4+PiBJbiBz
aG9ydCBJIGhhdmUgYW5hbHl6ZWQgdGhlIGxpdGVyYXR1cmUgcmVnYXJkaW5nOg0KPj4+IDEpIDIt
d2F5IGF1ZGlvIHZpZGVvIGNvbW11bmljYXRpb25zDQo+Pj4gMikgTXVsdGlwbGF5ZXIgZ2FtaW5n
DQo+Pj4gMykgUmVtb3RlIGNvbnRyb2wNCj4+Pg0KPj4+IEkgd2lsbCBzaG9ydGx5IGp1c3Qgc3Vt
bWFyaXplIHRoZSByZXN1bHRzIHdpdGhvdXQgbGlzdGluZyBhbGwgc291cmNlcy4NCj4+PiBOb3Rl
OiBVbmRlciB0ZXJtIGxhdGVuY3kgb25lIHdheSBkZWxheSBpcyBjb25zaWRlcmVkLg0KPj4+DQo+
Pj4gRm9yIDItd2F5IGF1ZGlvIGFuZCB2aWRlbyBjb21tdW5pY2F0aW9uIElUVS5UIHJlY29tbWVu
ZGF0aW9ucyBzdGF0ZQ0KPj4+dGhhdA0KPj4+IDE1MG1zIGxhdGVuY3kgaXMgbmVlZGVkIGZvciBj
b21wbGV0ZWx5IHVuaW1wYWlyZWQgY29tbXVuaWNhdGlvbi4NCj4+PiBMYXRlbmNpZXMgdXAgdG8g
NDAwbXMgY2FuIGJlIHRvbGVyYXRlZCwgYnV0IHRoZWlyIGltcGFjdCBpcyBub3RpY2VhYmxlLg0K
Pj4+DQo+Pj4gTXVsdGlwbGF5ZXIgZ2FtaW5nIGRpZmZlcnMgc2lnbmlmaWNhbnRseSBvbiB0aGUg
Z2VucmUuDQo+Pj4gVGhlIG1vc3QgZGVtYW5kaW5nIGdhbWVzIGFyZSBGaXJzdCBQZXJzb24gU2hv
b3RlciAoRlBTKSBnYW1lcyB3aGljaA0KPj4+IHJlcXVpcmUgYmV0d2VlbiA4MG1zIGFuZCAxMDBt
cyBkZWxheSBmb3IgdW5pbXBhaXJlZCBleHBlcmllbmNlLg0KPj4+IFNvbWUgc3R1ZGllcyBjbGFp
bSB0aGF0IFRocmlkIFBlcnNvbiBBdmF0YXIgZ2FtZXMgZnJvbSB3aGljaCB0aGUgbW9zdA0KPj4+
IGNvbW1vbiBhcmUgUm9sZSBQbGF5aW5nIEdhbWVzIChSUEdzKSBhbmQgTWFzc2l2ZWx5IE11bHRp
cGxheWVyIFJvbGUtDQo+Pj4gUGxheWluZyBHYW1lcyBNTU9SUEdzIHRvbGVyYXRlIGxhdGVuY2ll
cyB1cCB0byA1MDBtcywgYnV0IG90aGVyIHN0dWRpZXMNCj4+PiBzdGF0ZSB0aGF0IGEgbW9yZSBy
ZWFsaXN0aWMgdmFsdWVzIGZvciB1bmltcGFpcmVkIE1NT1JQRyBleHBlcmllbmNlIGlzDQo+Pj4g
YmV0d2VlbiAxMjAgYW5kIDIwMG1zLg0KPj4+IEFzIGZvciBvbW5pcHJlc2VudCBnYW1lcyBzdWNo
IGFzIFJlYWwgVGltZSBTdHJhdGVnaWVzIChSVFMpIGl0IGlzDQo+Pj5zdGF0ZWQNCj4+IHRoYXQN
Cj4+PiBsYXRlbmNpZXMgdXAgdG8gNTAwbXMgYW5kIGV2ZW4gdXAgdG8gMTAwMG1zIGRvIG5vdCBp
bXBhaXIgdXNlcg0KPj4+IHBlcmZvcm1hbmNlIG9uIG9iamVjdGl2ZSBtZXRyaWNzLCBidXQgdGhl
IGV2aWRlbmNlIGZyb20gUlRTIGdhbWUgZm9ydW1zDQo+Pj4gc3VnZ2VzdHMgdGhhdCB1c2VycyBh
cmUgcXVpdGUgdW5zYXRpc2ZpZWQgd2l0aCBsYXRlbmNpZXMgYWJvdmUgMzAwbXMuDQo+Pj4NCj4+
PiBSZW1vdGUgY29udHJvbCBoYXMgZGlmZmVyZW50IHZhbHVlcyBvZiBsYXRlbmN5IGZvciBkaWZm
ZXJlbnQgc2VydmljZXMNCj4+PmFzDQo+PiB3ZWxsLg0KPj4+IFJlbW90ZSBzdXJnZXJ5IGlzIHN0
YXRlZCB0aGF0IDMzMG1zIGxhdGVuY3kgaXMgYWNjZXB0YWJsZSwgYnV0IGZvcg0KPj4gY29udHJv
bGxpbmcNCj4+PiBhIHJvYm90IGluIHNjb3BlIG9mIGVuZC10by1lbmQgdGVsZS1lY2hvZ3JhcGh5
IHNob3dlZCB0aGF0IG9ubHkNCj4+PmxhdGVuY2llcw0KPj4+IHVuZGVyIDE1MG1zIGFyZSBhY2Nl
cHRhYmxlLg0KPj4+DQo+Pj4gV2hhdCBkbyB5b3UgdGhpbmsgaXMgdGhlcmUgYSBwb3NzaWJpbGl0
eSB0byBtYWtlIGFuIGV4dGVuZGVkIHZlcnNpb24gb2YNCj4+IHN1Y2gNCj4+PiBhIGRvY3VtZW50
IGFuZCBzdWJtaXQgaXQgYXMgYSBkcmFmdD8NCj4+Pg0KPj4+IFRoYW5rcyBmb3IgYW55IGZlZWRi
YWNrIQ0KPj4+DQo+Pj4gTWlya28gU3V6bmpldmljDQo+Pj4NCj4+PiAtLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KPj4+IEZyb206IHRjbXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0Y210
Zi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYNCj4+PiBPZiBKb3NlIFNhbGRhbmENCj4+PiBT
ZW50OiBUaHVyc2RheSwgU2VwdGVtYmVyIDI3LCAyMDEyIDEyOjMxIFBNDQo+Pj4gVG86IHRjbXRm
QGlldGYub3JnDQo+Pj4gQ2M6IFdlc2xleSBFZGR5OyBNYXJ0aW4gU3RpZW1lcmxpbmcNCj4+PiBT
dWJqZWN0OiBbdGNtdGZdIE5leHQgc3RlcHMgd2l0aCBUQ01URg0KPj4+DQo+Pj4gSGVsbG8gYWxs
LA0KPj4+DQo+Pj4gSSB3b3VsZCBsaWtlIHRvIGRpc2N1c3MgaW4gdGhpcyBsaXN0IHRoZSBwb3Nz
aWJpbGl0eSBvZiBjcmVhdGluZyBhDQo+Pj5zbWFsbA0KPj4gV29ya2luZw0KPj4+IEdyb3VwIGZv
ciBUQ01URiwgYXMgc3VnZ2VzdGVkIGJ5IFdlcy4gSXQgY291bGQgaGF2ZSB0aGUgdGFzayBvZiBt
YWtpbmcNCj4+PmENCj4+PiBSRkMgZnJvbSBUQ01URiwgb3IgYSB3aWRlciBzY29wZS4gSSB0aGlu
ayB0aGF0IHBlcmhhcHMgbW9yZSB0aGFuIGENCj4+PmRyYWZ0DQo+Pj4gd291bGQgYmUgbmVjZXNz
YXJ5LiBJIG1lYW4sIEkgaGF2ZSBiZWVuIHRoaW5raW5nIGFib3V0IGl0LCBhbmQgcGVyaGFwcw0K
Pj4+dGhlDQo+Pj4gd29yayBjb3VsZCBiZSBkaXZpZGVkIGludG8gdGhlIG5leHQgcGFydHM6DQo+
Pj4NCj4+PiAgIGEpICJDdXJyZW50IGRyYWZ0IjogdGhlIG1haW4gZHJhZnQgKGRyYWZ0LXNhbGRh
bmEtdHN2d2ctdGNtdGYtMDMpLA0KPj4gaW5jbHVkaW5nDQo+Pj4gdGhlIHByb3RvY29sIHN0YWNr
IG9mIFRDTVRGLiBUaGUgY3VycmVudCBwcm9wb3NhbCBoYXMgZGlmZmVyZW50DQo+Pj5vcHRpb25z
LA0KPj4gYnV0DQo+Pj4gdGhlIGNvbmNyZXRlIG9uZSB0byB1c2UgaXMgc3RhdGljOiBpbiB0aGUg
c2V0LXVwIG1vbWVudCwgeW91IGRlY2lkZQ0KPj4+dGhhdA0KPj4+ICJiZXR3ZWVuIHRoZXNlIHR3
byByb3V0ZXJzIGEgdHVubmVsIGlzIHNldCBpbmNsdWRpbmcgYWxsIHRoZSBwYWNrZXRzDQo+Pj53
aXRoDQo+PiB0aGlzDQo+Pj4gSVAgb3JpZ2luIGFuZCBkZXN0aW5hdGlvbiIuDQo+Pj4NCj4+PiBi
KSAiUmVjb21tZW5kYXRpb25zIGRyYWZ0IjogYW5vdGhlciAiaW5mb3JtYXRpb25hbCIgb25lLCB3
aXRoDQo+Pj4gcmVjb21tZW5kYXRpb25zIG9mIG1heGltdW0gZGVsYXlzIHRvIGJlIGFkZGVkIHRv
IGRpZmZlcmVudCBraW5kcyBvZg0KPj4+IHNlcnZpY2VzLCBkaWZmZXJlbnQgbXVsdGlwbGV4aW5n
IHBvbGljaWVzLCBpbXBsZW1lbnRhdGlvbiBpc3N1ZXMNCj4+PnJlbGF0ZWQNCj4+IHRvIHRoZQ0K
Pj4+IHNlbGVjdGlvbiBvZiB0aGUgYmVzdCBjb21wcmVzc2lvbiBhbGdvcml0aG0gdG8gdXNlLCBl
dGMuIFNvbWUNCj4+Pmh5cG90aGV0aWNhbA0KPj4+IGV4YW1wbGVzOg0KPj4+ICAgICAgICAtICAi
aWYgeW91IGFyZSBtdWx0aXBsZXhpbmcgYSBGaXJzdCBQZXJzb24gU2hvb3RlciwgeW91cg0KPj4+
bXVsdGlwbGV4ZXINCj4+IHNob3VsZA0KPj4+IG5vdCByZXRhaW4gcGFja2V0cyBtb3JlIHRoYW4g
NTAgbXMiDQo+Pj4gLSAiaWYgeW91IGFyZSBtdWx0aXBsZXhpbmcgaW4gYSBsb3ctZW5kIHJvdXRl
ciBpbiBhIHdpcmVkIHNjZW5hcmlvLCB5b3UNCj4+IGRvbid0DQo+Pj4gbmVlZCB0byB1c2UgUk9I
Qy4gQSBzaW1wbGVyIHNjaGVtZSBsaWtlIElQSEMgY2FuIGJlIGVub3VnaCwgYW5kIGl0IHdpbGwN
Cj4+IG5vdA0KPj4+IHJlcXVpcmUgYSBsb3Qgb2YgcHJvY2Vzc2luZyBjYXBhY2l0eSIuDQo+Pj4N
Cj4+PiBjKSAiRHluYW1pYyBTaWduYWxpbmcgZHJhZnQiOiBwZXJoYXBzIGFub3RoZXIgb25lIGlu
Y2x1ZGluZyBhIHNpZ25hbGluZw0KPj4+IHN5c3RlbSBpbiBvcmRlciB0bzoNCj4+PiAgICAgLSBk
eW5hbWljYWxseSAibmVnb3RpYXRlIiB0aGUgY29uY3JldGUgb3B0aW9ucyBvZiBUQ01URiB5b3Ug
YXJlDQo+Pj4gZ29pbmcgdG8gdXNlDQo+Pj4gICAgIC0gaWYgdHdvIHJvdXRlcnMgbm90aWNlIHRo
YXQgYSBydXNoIGhvdXIgaXMgYXJyaXZpbmcsIHRoZXkgY291bGQNCj4+IHNlbmQNCj4+PiBzb21l
IHBhY2tldHMgYXNraW5nIG90aGVyIHJvdXRlcnMgaWYgdGhleSBoYXZlIHNvbWUgZmxvd3MgaW4g
Y29tbW9uDQo+Pj53aXRoDQo+Pj4gdGhlbSwgd2hpY2ggY291bGQgYmUgbXVsdGlwbGV4ZWQuDQo+
Pj4NCj4+Pg0KPj4+IFRoZSBtYWluIHF1ZXN0aW9ucyBhcmU6DQo+Pj4NCj4+PiBJcyB0aGlzIGVu
b3VnaCBmb3IgY3JlYXRpbmcgYSB3b3JraW5nIGdyb3VwPw0KPj4+DQo+Pj4gRG8geW91IHRoaW5r
IHRoZSBkaXN0cmlidXRpb24gb2YgdGhlIHdvcmsgaW50byB0aHJlZSBkcmFmdCBtYWtlcyBzZW5z
ZT8NCj4+Pg0KPj4+IElzIHRoZXJlIGFueSBvdGhlciBpc3N1ZSB3aGljaCBzaG91bGQgYmUgc3R1
ZGllZCBhbmQgc3RhbmRhcmRpemVkPw0KPj4+UGVyaGFwcw0KPj4+IG90aGVyIHBlb3BsZSBjb3Vs
ZCBpbWFnaW5lIG1vcmUgdGhpbmdzLg0KPj4+DQo+Pj4gU28gbGV0J3Mgc3RhcnQgdGhlIGRpc2N1
c3Npb24uDQo+Pj4NCj4+PiBUaGFua3MgaW4gYWR2YW5jZSwNCj4+Pg0KPj4+IEpvc2UNCj4+Pg0K
Pj4+DQo+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cj4+PiB0Y210ZiBtYWlsaW5nIGxpc3QNCj4+PiB0Y210ZkBpZXRmLm9yZw0KPj4+IGh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCj4+PiBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+IHRjbXRmIG1haWxpbmcgbGlzdA0K
Pj4+IHRjbXRmQGlldGYub3JnDQo+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby90Y210Zg0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4+IHRjbXRmIG1haWxpbmcgbGlzdA0KPj4gdGNtdGZAaWV0Zi5vcmcNCj4+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCj4+DQo+Pg0KPg0KPl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+dGNtdGYgbWFpbGlu
ZyBsaXN0DQo+dGNtdGZAaWV0Zi5vcmcNCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3RjbXRmDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCg0KRXN0
ZSBtZW5zYWplIHNlIGRpcmlnZSBleGNsdXNpdmFtZW50ZSBhIHN1IGRlc3RpbmF0YXJpby4gUHVl
ZGUgY29uc3VsdGFyIG51ZXN0cmEgcG9sw610aWNhIGRlIGVudsOtbyB5IHJlY2VwY2nDs24gZGUg
Y29ycmVvIGVsZWN0csOzbmljbyBlbiBlbCBlbmxhY2Ugc2l0dWFkbyBtw6FzIGFiYWpvLg0KVGhp
cyBtZXNzYWdlIGlzIGludGVuZGVkIGV4Y2x1c2l2ZWx5IGZvciBpdHMgYWRkcmVzc2VlLiBXZSBv
bmx5IHNlbmQgYW5kIHJlY2VpdmUgZW1haWwgb24gdGhlIGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQg
b3V0IGF0Og0KaHR0cDovL3d3dy50aWQuZXMvRVMvUEFHSU5BUy9kaXNjbGFpbWVyLmFzcHgNCg==

From jacl@tid.es  Wed Oct 24 03:02:11 2012
Return-Path: <jacl@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 CB7D421F8AC0 for <tcmtf@ietfa.amsl.com>; Wed, 24 Oct 2012 03:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dCLVFLSixrvM for <tcmtf@ietfa.amsl.com>; Wed, 24 Oct 2012 03:02:09 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id DEA2E21F8A6B for <tcmtf@ietf.org>; Wed, 24 Oct 2012 03:02:07 -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 <0MCE00KYP6JI9U@tid.hi.inet> for tcmtf@ietf.org; Wed, 24 Oct 2012 12:02:06 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 9A.21.05494.D9CB7805; Wed, 24 Oct 2012 12:02:06 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MCE00KYK6JH9U@tid.hi.inet> for tcmtf@ietf.org; Wed, 24 Oct 2012 12:02:05 +0200 (MEST)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.178]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Wed, 24 Oct 2012 12:02:05 +0200
Date: Wed, 24 Oct 2012 10:02:04 +0000
From: JUAN ANTONIO CASTELL LUCIA <jacl@tid.es>
In-reply-to: <F5EDC35DF914C1428C28E149F10463A24C74AB4F@EX10-MB1-MAD.hi.inet>
X-Originating-IP: [10.95.64.115]
To: FERNANDO PASCUAL BLANCO <fpb@tid.es>, =?utf-8?B?SnVsacOhbiBGZXJuw6FuZGV6LU5hdmFqYXM=?= <navajas@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <49F52EC1A431BA4BBA8BA8CFF429B739029A360C@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_PiS1s6y3eRw97RGucokD1Q)"
Content-language: es-ES
Accept-Language: es-ES, en-US
Thread-topic: [tcmtf] Next steps with TCMTF
Thread-index: Ac2cmrry4BaRIpi1Sm27mcZI4g4aKwUW4ybw///h8wCAAZv/AIAAK92A///+BNA=
X-AuditID: 0a5f4e69-b7fc06d000001576-bf-5087bc9daff2
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGKsWRmVeSWpSXmKPExsXCFe9nqDtvT3uAwfJ2VotdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoErY/+SRewFzysrdt/9wNrAuLGsi5GTQ0LAROL1gktMELaYxIV7 69m6GLk4hAS2M0osnraNHcL5ySix++UhFghnJlDm9V42kBYWAVWJKx8amUFsNgE9iUOr/jOC 2MICWhK/Pn1hB7E5BXwkfp5qY4ZYoSDx59xjsEEiAlMZJRq+zQdr4BXwlpjx5BgrhC0o8WPy PRYQm1kgXeLvwjOMELa4xJxfE8FqGAVkJVaePw0WFxHQlvj57RMbhO0ncXH+ExaIZSISDy+e ZoOwRSVePv4H1iskkCXx6uE2lgmMorOQrJuFZN0sJOtmMXIA2ZoS63fpQ4QVJaZ0P2SHsGMl Nrxpg2r1ldh5+w8rhH2dUeLS9ARk9QsYOVcxihUnFWWmZ5TkJmbmpBsY6WVk6mXmpZZsYoRE ZOYOxuU7VQ4xCnAwKvHwHrjYFiDEmlhWXJl7iFGSg0lJlHf9jvYAIb6k/JTKjMTijPii0pzU 4kOMKkBLHm1YfYFRiiUvPy9VSYT3ySqgOt6UxMqq1KJ8mDIZDg4lCV7L3UApwaLU9NSKtMwc YDqCSTNxcB5ilODgAWr3BKnhLS5IzC3OTIfIn2KUlBLnTQNJCIAkMkrz4HpfMYoDHSzMqw2S 5QEmTriuV0ADmYAGmvO0ggwsSURISTUwhh/X6WNI1l/VqarUva/GJXa7zkGvvQubN179ozBH pd8gP2VNnkbRr7sKqsZax37uaJ774fTUfhnzcqP/t/6Ghi7QcK7Vqa9cVP09ZnOVEvf0Jerq 6/sXdexfYnbDPiIo+c3mT/sXpm4v69Dfp9b3nkkyztJrzsETnze/+Tnt/IRJP88kd504qcRS nJFoqMVcVJwIAKxd3FxZAwAA
References: <5087AE2E.3040303@unizar.es> <F5EDC35DF914C1428C28E149F10463A24C74AB4F@EX10-MB1-MAD.hi.inet>
Subject: Re: [tcmtf] Next steps with 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, 24 Oct 2012 10:02:11 -0000

--Boundary_(ID_PiS1s6y3eRw97RGucokD1Q)
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: base64

SGkgYWxsLCBhbHRob3VnaCBpcyBub3QgYSBzdHJpY3RseSByZW1vdGUgY29udHJvbCB0b3BpYywg
cmVnYXJkaW5nIG1lZGlhIGNvbnN1bXB0aW9uLCBhIHBvc3NpYmxlIHVzZSBjYXNlIG9mIFRDTVRG
IGFwcGxpY2F0aW9uIHdpdGggbXVsdGlwbGV4aW5nIElNSE8gY291bGQgYmUgaW50ZXJhY3RpdmUg
dGVsZXZpc2lvbiBwcm9ncmFtcy4gRm9yIGV4YW1wbGUsIHByb2dyYW1zIHdpdGggYSB2b3Rpbmcg
c2NoZW1lIChsZXQncyBkbyBhIG1vcmUgZmFpciBFdXJvdmlzaW9uIHNvbmcgY29udGVzdCA7bykp
LiBUaGF0IHN1cHBvc2VzIHRoYXQgZHVyaW5nIGNlcnRhaW4gY29uY3JldGUgcGVyaW9kIG9mIHRp
bWUgcHJvZ3JhbSB3YXRjaGVycyB3b3VsZCBiZSBzaW11bHRhbmVvdXNseSBzZW5kaW5nIHNtYWxs
IChJIGd1ZXNzKSBwYWNrZXRzLiBUaGUgbGF0ZW5jeSByZXF1aXJlbWVudHMgd291bGRuJ3QgYmUg
dmVyeSBoaWdoLg0KDQpTbWFydCBUVnMgYXJlIGNvbWluZy4uLg0KDQpXaGF0IGRvIHlvdSB0aGlu
az8NCg0KUmVnYXJkcywNCkp1YW4gQW50b25pbw0KDQoNCg0KLS0tLS1NZW5zYWplIG9yaWdpbmFs
LS0tLS0NCkRlOiB0Y210Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86dGNtdGYtYm91bmNlc0Bp
ZXRmLm9yZ10gRW4gbm9tYnJlIGRlIEZFUk5BTkRPIFBBU0NVQUwgQkxBTkNPDQpFbnZpYWRvIGVs
OiBtacOpcmNvbGVzLCAyNCBkZSBvY3R1YnJlIGRlIDIwMTIgMTE6MzgNClBhcmE6IEp1bGnDoW4g
RmVybsOhbmRlei1OYXZhamFzOyB0Y210ZkBpZXRmLm9yZw0KQXN1bnRvOiBSZTogW3RjbXRmXSBO
ZXh0IHN0ZXBzIHdpdGggVENNVEYNCg0KSGkgYWxsLA0KDQogICAgICAgIEFzIGEgZmlyc3QgdGhp
bmtpbmcsIFJUU1AgcHJvdG9jb2wgaGF2ZSBhIGNvbm5lY3Rpb24gY29udHJvbCBsYXllciB0aGF0
IGxldCBjbGllbnRzIHRvIHJlbW90ZWx5IGNvbnRyb2wgc3RyZWFtaW5nIHNlcnZlcnM6IHRoZXkg
Y2FuIHJlbW90ZWx5IHBsYXkgb3IgcGF1c2UgdGhlIG1lZGlh4oCmIEkgZG9uwrR0IGtub3cgaWYg
dGhhdCB3b3VsZCBiZSBhbiBpbnRlcmVzdGluZyB1c2UgY2FzZSB3aGVuIG11bHRpcGxleGluZyB1
c2VycyBjb25zdW1pbmcgbWVkaWEgdW5kZXIgZGVtYW5kLg0KDQpSZWdhcmRzLA0KDQpGZXJuYW5k
byBQYXNjdWFsIEJsYW5jbw0KVGVsZWbDs25pY2EgR2xvYmFsIFJlc291cmNlcw0KTmV0d29yayBB
dXRvbWF0aW9uIGFuZCBEeW5hbWl6YXRpb24NClRFQ0hOT0xPR1kgUEVPUExFIEdST1VQDQpGICsz
NDkxMzEyODc3OQ0KTSArMzQ2ODIwMDUxNjgNCmZwYkB0aWQuZXMNCg0KDQoNCg0KT24gMjQvMTAv
MTIgMTE6MDAsICJKdWxpw6FuIEZlcm7DoW5kZXotTmF2YWphcyIgPG5hdmFqYXNAdW5pemFyLmVz
PiB3cm90ZToNCg0KPmhlbGxvIGFsbCwNCj5SZWdhcmRpbmcgdGhlIHJlYWwtdGltZSBzZXJ2aWNl
cyBzdWl0YWJsZSBmb3IgbXVsdGlwbGV4aW5nLCBpIGhhdmUgYQ0KPnF1ZXN0aW9uIGFib3V0IHRo
ZSB0aGlyZCBvZiB0aGVtLCByZW1vdGUgY29udHJvbC4gSSBjYW4ndCB0aGluayBhIHVzZQ0KPmNh
c2UgdGhhdCB0cmFuc21pdHMgbGl0dGxlIHBhY2tldHMgaW4gb3JkZXIgdG8gYmUgbXVsdGlwbGV4
ZWQuIE1pcmtvDQo+c3VnZ2VzdHMgdGVsZS1lY2hvZ3JhcGh5IGJ1dCBpdCBubyBzZWVtcyBhIHVz
ZSBjYXNlIHRoYXQgdHJhZmZpYyBuZWVkcw0KPm11bHRpcGxleGlvbiBiZWNhdXNlIHRoZXJlIGFy
ZSBub3QgYSBsb3Qgb2YgdXNlcnMgc2ltdWx0YW5ldXNseS4NCj5MZXQgdXMgdGhpbmtpbmcgYWJv
dXQgcmVtb3RlIGNvbnRyb2wgYW5kIHRoZSBwb3NzaWJsZSB1c2UgY2FzZXMgdGhhdA0KPmNhbiBi
ZSBwcmVzZW50ZWQgaGVyZS4NCj4NCj5KdWxpw6FuDQo+DQo+DQo+DQo+DQo+RWwgMjMvMTAvMjAx
MiAxMDoyNSwgSm9zZSBTYWxkYW5hIGVzY3JpYmnDszoNCj4+IE1pcmtvLA0KPj4NCj4+IFRoaXMg
c291bmRzIHJlYWxseSBnb29kIS4gVGhpcyB3YXMgdGhlIGlkZWEgb2YgImRyYWZ0IGIpIi4NCj4+
DQo+PiBEbyB5b3UgdGhpbmsgeW91IGhhdmUgaW5jbHVkZWQgYWxsIHRoZSBzZXJ2aWNlcyB3aGlj
aCBjYW4gYmUNCj4+bXVsdGlwbGV4ZWQgIHdpdGggVENNVEY/IEkgbWVhbjogc21hbGwgcGFja2V0
cyBhbmQgaGlnaCBvdmVyaGVhZC4gU29tZQ0KPj5pZGVhczogc2Vuc29yICBuZXR3b3JrcyBzZW5k
aW5nIGEgc2FtcGxlLCB2aWRlby1zdXJ2ZWlsbGFuY2UsDQo+PndoYXRzYXBwLWxpa2UgYXBwbGlj
YXRpb25zPw0KPj4gQWx0aG91Z2ggc29tZSBvZiB0aGVtIGFyZSBub3QgcmVhbC10aW1lLCBwZXJo
YXBzIHRoZXkgY2FuIGFsc28gYmUNCj4+bXVsdGlwbGV4ZWQgaWYgdGhlIG51bWJlciBvZiBwYWNr
ZXRzIHBlciBzZWNvbmQgaXMgYmlnLg0KPj4NCj4+IFNvIHBlcmhhcHMgYSBzZWN0aW9uIGVudW1l
cmF0aW5nIG5vbiByZWFsLXRpbWUgYXBwbGljYXRpb25zIHdpdGgNCj4+c21hbGwgIHBhY2tldHMg
Y291bGQgYWxzbyBiZSBpbnRlcmVzdGluZzogZm9yIGV4YW1wbGUgImluc3RhbnQNCj4+bWVzc2Fn
aW5nICBhcHBsaWNhdGlvbnMgY2FuIHRvbGVyYXRlIHVwIHRvIDUgc2Vjb25kcyBvZiBkZWxheSIg
KEkgaGF2ZQ0KPj5qdXN0IGludmVudGVkICB0aGUgZmlndXJlLCBpdCdzIG9ubHkgYW4gZXhhbXBs
ZSkuDQo+Pg0KPj4gSSBjb3VsZCBoZWxwIHlvdSB3aXRoIHRoaXMsIGlmIHlvdSBhZ3JlZSwgb2Yg
Y291cnNlLg0KPj4NCj4+IFRoYW5rcywNCj4+DQo+PiBKb3NlDQo+Pg0KPj4+IC0tLS0tTWVuc2Fq
ZSBvcmlnaW5hbC0tLS0tDQo+Pj4gRGU6IHRjbXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0
Y210Zi1ib3VuY2VzQGlldGYub3JnXSBFbiBub21icmUNCj4+PiBkZSBNaXJrbyBTdcW+bmpldmlj
IEVudmlhZG8gZWw6IG1hcnRlcywgMjMgZGUgb2N0dWJyZSBkZSAyMDEyIDEwOjE0DQo+Pj4gUGFy
YTogdGNtdGZAaWV0Zi5vcmcNCj4+PiBBc3VudG86IFJlOiBbdGNtdGZdIE5leHQgc3RlcHMgd2l0
aCBUQ01URg0KPj4+DQo+Pj4gSGVsbG8gYWxsLA0KPj4+DQo+Pj4gUmVnYXJkaW5nIHRoZSBiKSAi
UmVjb21tZW5kYXRpb25zIGRyYWZ0IiBJIGhhdmUgY3JlYXRlZCBhIGZpcnN0DQo+Pj5zdW1tYXJ5
IG9mICByZWFsLXRpbWUgc2VydmljZXMgc3VpdGFibGUgZm9yIG11bHRpcGxleGluZy4NCj4+Pg0K
Pj4+IEluIHNob3J0IEkgaGF2ZSBhbmFseXplZCB0aGUgbGl0ZXJhdHVyZSByZWdhcmRpbmc6DQo+
Pj4gMSkgMi13YXkgYXVkaW8gdmlkZW8gY29tbXVuaWNhdGlvbnMNCj4+PiAyKSBNdWx0aXBsYXll
ciBnYW1pbmcNCj4+PiAzKSBSZW1vdGUgY29udHJvbA0KPj4+DQo+Pj4gSSB3aWxsIHNob3J0bHkg
anVzdCBzdW1tYXJpemUgdGhlIHJlc3VsdHMgd2l0aG91dCBsaXN0aW5nIGFsbCBzb3VyY2VzLg0K
Pj4+IE5vdGU6IFVuZGVyIHRlcm0gbGF0ZW5jeSBvbmUgd2F5IGRlbGF5IGlzIGNvbnNpZGVyZWQu
DQo+Pj4NCj4+PiBGb3IgMi13YXkgYXVkaW8gYW5kIHZpZGVvIGNvbW11bmljYXRpb24gSVRVLlQg
cmVjb21tZW5kYXRpb25zIHN0YXRlDQo+Pj50aGF0ICAxNTBtcyBsYXRlbmN5IGlzIG5lZWRlZCBm
b3IgY29tcGxldGVseSB1bmltcGFpcmVkDQo+Pj5jb21tdW5pY2F0aW9uLg0KPj4+IExhdGVuY2ll
cyB1cCB0byA0MDBtcyBjYW4gYmUgdG9sZXJhdGVkLCBidXQgdGhlaXIgaW1wYWN0IGlzIG5vdGlj
ZWFibGUuDQo+Pj4NCj4+PiBNdWx0aXBsYXllciBnYW1pbmcgZGlmZmVycyBzaWduaWZpY2FudGx5
IG9uIHRoZSBnZW5yZS4NCj4+PiBUaGUgbW9zdCBkZW1hbmRpbmcgZ2FtZXMgYXJlIEZpcnN0IFBl
cnNvbiBTaG9vdGVyIChGUFMpIGdhbWVzIHdoaWNoDQo+Pj5yZXF1aXJlIGJldHdlZW4gODBtcyBh
bmQgMTAwbXMgZGVsYXkgZm9yIHVuaW1wYWlyZWQgZXhwZXJpZW5jZS4NCj4+PiBTb21lIHN0dWRp
ZXMgY2xhaW0gdGhhdCBUaHJpZCBQZXJzb24gQXZhdGFyIGdhbWVzIGZyb20gd2hpY2ggdGhlDQo+
Pj5tb3N0ICBjb21tb24gYXJlIFJvbGUgUGxheWluZyBHYW1lcyAoUlBHcykgYW5kIE1hc3NpdmVs
eSBNdWx0aXBsYXllcg0KPj4+Um9sZS0gIFBsYXlpbmcgR2FtZXMgTU1PUlBHcyB0b2xlcmF0ZSBs
YXRlbmNpZXMgdXAgdG8gNTAwbXMsIGJ1dA0KPj4+b3RoZXIgc3R1ZGllcyAgc3RhdGUgdGhhdCBh
IG1vcmUgcmVhbGlzdGljIHZhbHVlcyBmb3IgdW5pbXBhaXJlZA0KPj4+TU1PUlBHIGV4cGVyaWVu
Y2UgaXMgIGJldHdlZW4gMTIwIGFuZCAyMDBtcy4NCj4+PiBBcyBmb3Igb21uaXByZXNlbnQgZ2Ft
ZXMgc3VjaCBhcyBSZWFsIFRpbWUgU3RyYXRlZ2llcyAoUlRTKSBpdCBpcw0KPj4+c3RhdGVkDQo+
PiB0aGF0DQo+Pj4gbGF0ZW5jaWVzIHVwIHRvIDUwMG1zIGFuZCBldmVuIHVwIHRvIDEwMDBtcyBk
byBub3QgaW1wYWlyIHVzZXINCj4+PiBwZXJmb3JtYW5jZSBvbiBvYmplY3RpdmUgbWV0cmljcywg
YnV0IHRoZSBldmlkZW5jZSBmcm9tIFJUUyBnYW1lDQo+Pj4gZm9ydW1zIHN1Z2dlc3RzIHRoYXQg
dXNlcnMgYXJlIHF1aXRlIHVuc2F0aXNmaWVkIHdpdGggbGF0ZW5jaWVzIGFib3ZlIDMwMG1zLg0K
Pj4+DQo+Pj4gUmVtb3RlIGNvbnRyb2wgaGFzIGRpZmZlcmVudCB2YWx1ZXMgb2YgbGF0ZW5jeSBm
b3IgZGlmZmVyZW50DQo+Pj5zZXJ2aWNlcyBhcw0KPj4gd2VsbC4NCj4+PiBSZW1vdGUgc3VyZ2Vy
eSBpcyBzdGF0ZWQgdGhhdCAzMzBtcyBsYXRlbmN5IGlzIGFjY2VwdGFibGUsIGJ1dCBmb3INCj4+
IGNvbnRyb2xsaW5nDQo+Pj4gYSByb2JvdCBpbiBzY29wZSBvZiBlbmQtdG8tZW5kIHRlbGUtZWNo
b2dyYXBoeSBzaG93ZWQgdGhhdCBvbmx5DQo+Pj5sYXRlbmNpZXMgIHVuZGVyIDE1MG1zIGFyZSBh
Y2NlcHRhYmxlLg0KPj4+DQo+Pj4gV2hhdCBkbyB5b3UgdGhpbmsgaXMgdGhlcmUgYSBwb3NzaWJp
bGl0eSB0byBtYWtlIGFuIGV4dGVuZGVkIHZlcnNpb24NCj4+PiBvZg0KPj4gc3VjaA0KPj4+IGEg
ZG9jdW1lbnQgYW5kIHN1Ym1pdCBpdCBhcyBhIGRyYWZ0Pw0KPj4+DQo+Pj4gVGhhbmtzIGZvciBh
bnkgZmVlZGJhY2shDQo+Pj4NCj4+PiBNaXJrbyBTdXpuamV2aWMNCj4+Pg0KPj4+IC0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4gRnJvbTogdGNtdGYtYm91bmNlc0BpZXRmLm9yZyBbbWFp
bHRvOnRjbXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uDQo+Pj4gQmVoYWxmIE9mIEpvc2UgU2FsZGFu
YQ0KPj4+IFNlbnQ6IFRodXJzZGF5LCBTZXB0ZW1iZXIgMjcsIDIwMTIgMTI6MzEgUE0NCj4+PiBU
bzogdGNtdGZAaWV0Zi5vcmcNCj4+PiBDYzogV2VzbGV5IEVkZHk7IE1hcnRpbiBTdGllbWVybGlu
Zw0KPj4+IFN1YmplY3Q6IFt0Y210Zl0gTmV4dCBzdGVwcyB3aXRoIFRDTVRGDQo+Pj4NCj4+PiBI
ZWxsbyBhbGwsDQo+Pj4NCj4+PiBJIHdvdWxkIGxpa2UgdG8gZGlzY3VzcyBpbiB0aGlzIGxpc3Qg
dGhlIHBvc3NpYmlsaXR5IG9mIGNyZWF0aW5nIGENCj4+PnNtYWxsDQo+PiBXb3JraW5nDQo+Pj4g
R3JvdXAgZm9yIFRDTVRGLCBhcyBzdWdnZXN0ZWQgYnkgV2VzLiBJdCBjb3VsZCBoYXZlIHRoZSB0
YXNrIG9mDQo+Pj5tYWtpbmcgYSAgUkZDIGZyb20gVENNVEYsIG9yIGEgd2lkZXIgc2NvcGUuIEkg
dGhpbmsgdGhhdCBwZXJoYXBzIG1vcmUNCj4+PnRoYW4gYSBkcmFmdCAgd291bGQgYmUgbmVjZXNz
YXJ5LiBJIG1lYW4sIEkgaGF2ZSBiZWVuIHRoaW5raW5nIGFib3V0DQo+Pj5pdCwgYW5kIHBlcmhh
cHMgdGhlICB3b3JrIGNvdWxkIGJlIGRpdmlkZWQgaW50byB0aGUgbmV4dCBwYXJ0czoNCj4+Pg0K
Pj4+ICAgYSkgIkN1cnJlbnQgZHJhZnQiOiB0aGUgbWFpbiBkcmFmdCAoZHJhZnQtc2FsZGFuYS10
c3Z3Zy10Y210Zi0wMyksDQo+PiBpbmNsdWRpbmcNCj4+PiB0aGUgcHJvdG9jb2wgc3RhY2sgb2Yg
VENNVEYuIFRoZSBjdXJyZW50IHByb3Bvc2FsIGhhcyBkaWZmZXJlbnQNCj4+Pm9wdGlvbnMsDQo+
PiBidXQNCj4+PiB0aGUgY29uY3JldGUgb25lIHRvIHVzZSBpcyBzdGF0aWM6IGluIHRoZSBzZXQt
dXAgbW9tZW50LCB5b3UgZGVjaWRlDQo+Pj50aGF0ICAiYmV0d2VlbiB0aGVzZSB0d28gcm91dGVy
cyBhIHR1bm5lbCBpcyBzZXQgaW5jbHVkaW5nIGFsbCB0aGUNCj4+PnBhY2tldHMgd2l0aA0KPj4g
dGhpcw0KPj4+IElQIG9yaWdpbiBhbmQgZGVzdGluYXRpb24iLg0KPj4+DQo+Pj4gYikgIlJlY29t
bWVuZGF0aW9ucyBkcmFmdCI6IGFub3RoZXIgImluZm9ybWF0aW9uYWwiIG9uZSwgd2l0aA0KPj4+
cmVjb21tZW5kYXRpb25zIG9mIG1heGltdW0gZGVsYXlzIHRvIGJlIGFkZGVkIHRvIGRpZmZlcmVu
dCBraW5kcyBvZg0KPj4+c2VydmljZXMsIGRpZmZlcmVudCBtdWx0aXBsZXhpbmcgcG9saWNpZXMs
IGltcGxlbWVudGF0aW9uIGlzc3Vlcw0KPj4+cmVsYXRlZA0KPj4gdG8gdGhlDQo+Pj4gc2VsZWN0
aW9uIG9mIHRoZSBiZXN0IGNvbXByZXNzaW9uIGFsZ29yaXRobSB0byB1c2UsIGV0Yy4gU29tZQ0K
Pj4+aHlwb3RoZXRpY2FsDQo+Pj4gZXhhbXBsZXM6DQo+Pj4gICAgICAgIC0gICJpZiB5b3UgYXJl
IG11bHRpcGxleGluZyBhIEZpcnN0IFBlcnNvbiBTaG9vdGVyLCB5b3VyDQo+Pj5tdWx0aXBsZXhl
cg0KPj4gc2hvdWxkDQo+Pj4gbm90IHJldGFpbiBwYWNrZXRzIG1vcmUgdGhhbiA1MCBtcyINCj4+
PiAtICJpZiB5b3UgYXJlIG11bHRpcGxleGluZyBpbiBhIGxvdy1lbmQgcm91dGVyIGluIGEgd2ly
ZWQgc2NlbmFyaW8sDQo+Pj4geW91DQo+PiBkb24ndA0KPj4+IG5lZWQgdG8gdXNlIFJPSEMuIEEg
c2ltcGxlciBzY2hlbWUgbGlrZSBJUEhDIGNhbiBiZSBlbm91Z2gsIGFuZCBpdA0KPj4+IHdpbGwN
Cj4+IG5vdA0KPj4+IHJlcXVpcmUgYSBsb3Qgb2YgcHJvY2Vzc2luZyBjYXBhY2l0eSIuDQo+Pj4N
Cj4+PiBjKSAiRHluYW1pYyBTaWduYWxpbmcgZHJhZnQiOiBwZXJoYXBzIGFub3RoZXIgb25lIGlu
Y2x1ZGluZyBhDQo+Pj4gc2lnbmFsaW5nIHN5c3RlbSBpbiBvcmRlciB0bzoNCj4+PiAgICAgLSBk
eW5hbWljYWxseSAibmVnb3RpYXRlIiB0aGUgY29uY3JldGUgb3B0aW9ucyBvZiBUQ01URiB5b3Ug
YXJlDQo+Pj4gZ29pbmcgdG8gdXNlDQo+Pj4gICAgIC0gaWYgdHdvIHJvdXRlcnMgbm90aWNlIHRo
YXQgYSBydXNoIGhvdXIgaXMgYXJyaXZpbmcsIHRoZXkgY291bGQNCj4+IHNlbmQNCj4+PiBzb21l
IHBhY2tldHMgYXNraW5nIG90aGVyIHJvdXRlcnMgaWYgdGhleSBoYXZlIHNvbWUgZmxvd3MgaW4g
Y29tbW9uDQo+Pj53aXRoICB0aGVtLCB3aGljaCBjb3VsZCBiZSBtdWx0aXBsZXhlZC4NCj4+Pg0K
Pj4+DQo+Pj4gVGhlIG1haW4gcXVlc3Rpb25zIGFyZToNCj4+Pg0KPj4+IElzIHRoaXMgZW5vdWdo
IGZvciBjcmVhdGluZyBhIHdvcmtpbmcgZ3JvdXA/DQo+Pj4NCj4+PiBEbyB5b3UgdGhpbmsgdGhl
IGRpc3RyaWJ1dGlvbiBvZiB0aGUgd29yayBpbnRvIHRocmVlIGRyYWZ0IG1ha2VzIHNlbnNlPw0K
Pj4+DQo+Pj4gSXMgdGhlcmUgYW55IG90aGVyIGlzc3VlIHdoaWNoIHNob3VsZCBiZSBzdHVkaWVk
IGFuZCBzdGFuZGFyZGl6ZWQ/DQo+Pj5QZXJoYXBzDQo+Pj4gb3RoZXIgcGVvcGxlIGNvdWxkIGlt
YWdpbmUgbW9yZSB0aGluZ3MuDQo+Pj4NCj4+PiBTbyBsZXQncyBzdGFydCB0aGUgZGlzY3Vzc2lv
bi4NCj4+Pg0KPj4+IFRoYW5rcyBpbiBhZHZhbmNlLA0KPj4+DQo+Pj4gSm9zZQ0KPj4+DQo+Pj4N
Cj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+
IHRjbXRmIG1haWxpbmcgbGlzdA0KPj4+IHRjbXRmQGlldGYub3JnDQo+Pj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90Y210Zg0KPj4+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4gdGNtdGYgbWFpbGluZyBsaXN0DQo+Pj4g
dGNtdGZAaWV0Zi5vcmcNCj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L3RjbXRmDQo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPj4gdGNtdGYgbWFpbGluZyBsaXN0DQo+PiB0Y210ZkBpZXRmLm9yZw0KPj4gaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90Y210Zg0KPj4NCj4+DQo+DQo+X19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj50Y210ZiBtYWlsaW5nIGxp
c3QNCj50Y210ZkBpZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vdGNtdGYNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQpFc3RlIG1l
bnNhamUgc2UgZGlyaWdlIGV4Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRhcmlvLiBQdWVkZSBj
b25zdWx0YXIgbnVlc3RyYSBwb2zDrXRpY2EgZGUgZW52w61vIHkgcmVjZXBjacOzbiBkZSBjb3Jy
ZW8gZWxlY3Ryw7NuaWNvIGVuIGVsIGVubGFjZSBzaXR1YWRvIG3DoXMgYWJham8uDQpUaGlzIG1l
c3NhZ2UgaXMgaW50ZW5kZWQgZXhjbHVzaXZlbHkgZm9yIGl0cyBhZGRyZXNzZWUuIFdlIG9ubHkg
c2VuZCBhbmQgcmVjZWl2ZSBlbWFpbCBvbiB0aGUgYmFzaXMgb2YgdGhlIHRlcm1zIHNldCBvdXQg
YXQ6DQpodHRwOi8vd3d3LnRpZC5lcy9FUy9QQUdJTkFTL2Rpc2NsYWltZXIuYXNweA0KX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnRjbXRmIG1haWxpbmcg
bGlzdA0KdGNtdGZAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vdGNtdGYNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCg0KRXN0ZSBtZW5z
YWplIHNlIGRpcmlnZSBleGNsdXNpdmFtZW50ZSBhIHN1IGRlc3RpbmF0YXJpby4gUHVlZGUgY29u
c3VsdGFyIG51ZXN0cmEgcG9sw610aWNhIGRlIGVudsOtbyB5IHJlY2VwY2nDs24gZGUgY29ycmVv
IGVsZWN0csOzbmljbyBlbiBlbCBlbmxhY2Ugc2l0dWFkbyBtw6FzIGFiYWpvLg0KVGhpcyBtZXNz
YWdlIGlzIGludGVuZGVkIGV4Y2x1c2l2ZWx5IGZvciBpdHMgYWRkcmVzc2VlLiBXZSBvbmx5IHNl
bmQgYW5kIHJlY2VpdmUgZW1haWwgb24gdGhlIGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQgb3V0IGF0
Og0KaHR0cDovL3d3dy50aWQuZXMvRVMvUEFHSU5BUy9kaXNjbGFpbWVyLmFzcHgNCg==

--Boundary_(ID_PiS1s6y3eRw97RGucokD1Q)
Content-type: text/x-vcard;
 name="=?utf-8?B?SnVhbiBBbnRvbmlvIENhc3RlbGwgTHVjw61hLnZjZg==?="
Content-transfer-encoding: base64
Content-disposition: attachment;
 filename="=?utf-8?B?SnVhbiBBbnRvbmlvIENhc3RlbGwgTHVjw61hLnZjZg==?=";
 size=1816; creation-date="Wed, 24 Oct 2012 10:02:04 GMT";
 modification-date="Wed, 24 Oct 2012 10:02:04 GMT"
Content-description: =?utf-8?B?SnVhbiBBbnRvbmlvIENhc3RlbGwgTHVjw61hLnZjZg==?=

QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpYLU1TLVNJR05BVFVSRTpZRVMNCk47TEFOR1VBR0U9
ZXM7Q0hBUlNFVD1XaW5kb3dzLTEyNTI6Q2FzdGVsbCBMdWPtYTtKdWFuIEFudG9uaW8NCkZOO0NI
QVJTRVQ9V2luZG93cy0xMjUyOkp1YW4gQW50b25pbyBDYXN0ZWxsIEx1Y+1hDQpPUkc7Q0hBUlNF
VD1XaW5kb3dzLTEyNTI6VGVsZWbzbmljYSBHbG9iYWwgUmVzb3VyY2VzDQpUSVRMRTpBdXRvbWF0
ZWQgYW5kIER5bmFtaWMgTmV0d29ya3MNClRFTDtXT1JLO1ZPSUNFOiszNCA5MTMxMjkxNTcNClRF
TDtDRUxMO1ZPSUNFOjY5MDY0MTQ1Mg0KQURSO1dPUks7UFJFRjtDSEFSU0VUPVdpbmRvd3MtMTI1
Mjo7O2MvRG9uIFJhbfNuIGRlIGxhIENydXo7TWFkcmlkOzgyLTg0OzI4MDA2O0VzcGHxYQ0KTEFC
RUw7V09SSztQUkVGO0NIQVJTRVQ9V2luZG93cy0xMjUyO0VOQ09ESU5HPVFVT1RFRC1QUklOVEFC
TEU6Yy9Eb24gUmFtPUYzbiBkZSBsYSBDcnV6IDgyLTg0PTBEPTBBPQ0KMjgwMDYgIE1hZHJpZA0K
WC1NUy1PTC1ERUZBVUxULVBPU1RBTC1BRERSRVNTOjINCkVNQUlMO1BSRUY7SU5URVJORVQ6amFj
bEB0aWQuZXMNClgtTVMtT0wtREVTSUdOO0NIQVJTRVQ9dXRmLTg6PGNhcmQgeG1sbnM9Imh0dHA6
Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vb2ZmaWNlL291dGxvb2svMTIvZWxlY3Ryb25pY2J1c2lu
ZXNzY2FyZHMiIHZlcj0iMS4wIiBsYXlvdXQ9ImxlZnQiIGJnY29sb3I9ImZmZmZmZiI+PGltZyB4
bWxucz0iIiBhbGlnbj0iZml0IiBhcmVhPSIxNiIgdXNlPSJjYXJkcGljdHVyZSIvPjxmbGQgeG1s
bnM9IiIgcHJvcD0ibmFtZSIgYWxpZ249ImxlZnQiIGRpcj0ibHRyIiBzdHlsZT0iYiIgY29sb3I9
IjAwMDAwMCIgc2l6ZT0iMTAiLz48ZmxkIHhtbG5zPSIiIHByb3A9Im9yZyIgYWxpZ249ImxlZnQi
IGRpcj0ibHRyIiBjb2xvcj0iMDAwMDAwIiBzaXplPSI4Ii8+PGZsZCB4bWxucz0iIiBwcm9wPSJ0
aXRsZSIgYWxpZ249ImxlZnQiIGRpcj0ibHRyIiBjb2xvcj0iMDAwMDAwIiBzaXplPSI4Ii8+PGZs
ZCB4bWxucz0iIiBwcm9wPSJibGFuayIgc2l6ZT0iOCIvPjxmbGQgeG1sbnM9IiIgcHJvcD0idGVs
d29yayIgYWxpZ249ImxlZnQiIGRpcj0ibHRyIiBjb2xvcj0iMDAwMDAwIiBzaXplPSI4Ij48bGFi
ZWwgYWxpZ249InJpZ2h0IiBjb2xvcj0iNjI2MjYyIj5UcmFiYWpvPC9sYWJlbD48L2ZsZD48Zmxk
IHhtbG5zPSIiIHByb3A9InRlbGNlbGwiIGFsaWduPSJsZWZ0IiBkaXI9Imx0ciIgY29sb3I9IjAw
MDAwMCIgc2l6ZT0iOCI+PGxhYmVsIGFsaWduPSJyaWdodCIgY29sb3I9IjYyNjI2MiI+TcOzdmls
PC9sYWJlbD48L2ZsZD48ZmxkIHhtbG5zPSIiIHByb3A9ImVtYWlsIiBhbGlnbj0ibGVmdCIgZGly
PSJsdHIiIGNvbG9yPSIwMDAwMDAiIHNpemU9IjgiLz48ZmxkIHhtbG5zPSIiIHByb3A9ImFkZHJ3
b3JrIiBhbGlnbj0ibGVmdCIgZGlyPSJsdHIiIGNvbG9yPSIwMDAwMDAiIHNpemU9IjgiLz48Zmxk
IHhtbG5zPSIiIHByb3A9ImJsYW5rIiBzaXplPSI4Ii8+PGZsZCB4bWxucz0iIiBwcm9wPSJibGFu
ayIgc2l6ZT0iOCIvPjxmbGQgeG1sbnM9IiIgcHJvcD0iYmxhbmsiIHNpemU9IjgiLz48ZmxkIHht
bG5zPSIiIHByb3A9ImJsYW5rIiBzaXplPSI4Ii8+PGZsZCB4bWxucz0iIiBwcm9wPSJibGFuayIg
c2l6ZT0iOCIvPjxmbGQgeG1sbnM9IiIgcHJvcD0iYmxhbmsiIHNpemU9IjgiLz48ZmxkIHhtbG5z
PSIiIHByb3A9ImJsYW5rIiBzaXplPSI4Ii8+PGZsZCB4bWxucz0iIiBwcm9wPSJibGFuayIgc2l6
ZT0iOCIvPjwvY2FyZD4NClJFVjoyMDEyMDgxM1QxMDQ2MDBaDQpFTkQ6VkNBUkQNCg==

--Boundary_(ID_PiS1s6y3eRw97RGucokD1Q)--

From jsaldana@unizar.es  Wed Oct 24 03:18: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 3966121F8B88 for <tcmtf@ietfa.amsl.com>; Wed, 24 Oct 2012 03:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.056
X-Spam-Level: 
X-Spam-Status: No, score=-6.056 tagged_above=-999 required=5 tests=[AWL=-0.072, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W9Y40U12a0hP for <tcmtf@ietfa.amsl.com>; Wed, 24 Oct 2012 03:18:53 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 267CE21F8941 for <tcmtf@ietf.org>; Wed, 24 Oct 2012 03:18:52 -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 q9OAIgFf000720; Wed, 24 Oct 2012 12:18:46 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'JUAN ANTONIO CASTELL LUCIA'" <jacl@tid.es>, "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>, "=?UTF-8?Q?'Juli=C3=A1n_Fern=C3=A1ndez-Navajas'?=" <navajas@unizar.es>
References: <5087AE2E.3040303@unizar.es>	<F5EDC35DF914C1428C28E149F10463A24C74AB4F@EX10-MB1-MAD.hi.inet> <49F52EC1A431BA4BBA8BA8CFF429B739029A360C@EX10-MB1-MAD.hi.inet>
In-Reply-To: <49F52EC1A431BA4BBA8BA8CFF429B739029A360C@EX10-MB1-MAD.hi.inet>
Date: Wed, 24 Oct 2012 12:18:48 +0200
Organization: Universidad de Zaragoza
Message-ID: <005c01cdb1d0$f71ab910$e5502b30$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGTmWR5AQilMS4nEd6SNju/j1p3wQJ9MU5qAb3IQIWYGpOV8A==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Next steps with 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: Wed, 24 Oct 2012 10:18:55 -0000

We are thinking a lot, and this is good.

My opinion: the optimization is only interesting for services with:

- small packets
- a place where a number of flows can be multiplexed
- the multiplexing saving is interesting. One example is a service with =
sudden and huge traffic bursts.

In this sense, I think that the voting scheme for a TV program can be =
interesting. Your network is dimensioned for a normal performance, and =
in 10 seconds you have millions of people sending messages: just when =
the program host says: "who is the one you want to ban from the program? =
Send your votes just now"

And a whatsapp-like application has the same problem:
- after a football match, you may like to pester the one whose team has =
lost, or to congratulate the winner (less frequent).
- in the minutes around 0:00 of New Year's day, there are lots of people =
sending short messages.

Regarding RTSP, I don't clearly see a place where a big number of =
messages can be grouped. Some help?

And regarding tele-ecography, I think that the number of ecography =
devices in a place will always be small. In addition, doctors always =
have money to spare, so they don't need to save bandwidth.

Thanks,

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> JUAN ANTONIO CASTELL LUCIA
> Enviado el: mi=C3=A9rcoles, 24 de octubre de 2012 12:02
> Para: FERNANDO PASCUAL BLANCO; Juli=C3=A1n Fern=C3=A1ndez-Navajas;
> tcmtf@ietf.org
> Asunto: Re: [tcmtf] Next steps with TCMTF
>=20
> Hi all, although is not a strictly remote control topic, regarding =
media
> consumption, a possible use case of TCMTF application with =
multiplexing
> IMHO could be interactive television programs. For example, programs =
with a
> voting scheme (let's do a more fair Eurovision song contest ;o)). That
> supposes that during certain concrete period of time program watchers
> would be simultaneously sending small (I guess) packets. The latency
> requirements wouldn't be very high.
>=20
> Smart TVs are coming...
>=20
> What do you think?
>=20
> Regards,
> Juan Antonio
>=20
>=20
>=20
> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> FERNANDO PASCUAL BLANCO Enviado el: mi=C3=A9rcoles, 24 de octubre de =
2012
> 11:38
> Para: Juli=C3=A1n Fern=C3=A1ndez-Navajas; tcmtf@ietf.org
> Asunto: Re: [tcmtf] Next steps with TCMTF
>=20
> Hi all,
>=20
>         As a first thinking, RTSP protocol have a connection control =
layer that let
> clients to remotely control streaming servers: they can remotely play =
or
> pause the media=E2=80=A6 I don=C2=B4t know if that would be an =
interesting use case
> when multiplexing users consuming media under demand.
>=20
> Regards,
>=20
> Fernando Pascual Blanco
> Telef=C3=B3nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>=20
>=20
>=20
>=20
> On 24/10/12 11:00, "Juli=C3=A1n Fern=C3=A1ndez-Navajas" =
<navajas@unizar.es> wrote:
>=20
> >hello all,
> >Regarding the real-time services suitable for multiplexing, i have a
> >question about the third of them, remote control. I can't think a use
> >case that transmits little packets in order to be multiplexed. Mirko
> >suggests tele-echography but it no seems a use case that traffic =
needs
> >multiplexion because there are not a lot of users simultaneusly.
> >Let us thinking about remote control and the possible use cases that
> >can be presented here.
> >
> >Juli=C3=A1n
> >
> >
> >
> >
> >El 23/10/2012 10:25, Jose Saldana escribi=C3=B3:
> >> Mirko,
> >>
> >> This sounds really good!. This was the idea of "draft b)".
> >>
> >> Do you think you have included all the services which can be
> >>multiplexed  with TCMTF? I mean: small packets and high overhead. =
Some
> >>ideas: sensor  networks sending a sample, video-surveillance,
> >>whatsapp-like applications?
> >> Although some of them are not real-time, perhaps they can also be
> >>multiplexed if the number of packets per second is big.
> >>
> >> So perhaps a section enumerating non real-time applications with
> >>small  packets could also be interesting: for example "instant
> >>messaging  applications can tolerate up to 5 seconds of delay" (I =
have
> >>just invented  the figure, it's only an example).
> >>
> >> I could help you with this, if you agree, of course.
> >>
> >> Thanks,
> >>
> >> Jose
> >>
> >>> -----Mensaje original-----
> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> nombre
> >>> de Mirko Su=C5=BEnjevic Enviado el: martes, 23 de octubre de 2012 =
10:14
> >>> Para: tcmtf@ietf.org
> >>> Asunto: Re: [tcmtf] Next steps with TCMTF
> >>>
> >>> Hello all,
> >>>
> >>> Regarding the b) "Recommendations draft" I have created a first
> >>>summary of  real-time services suitable for multiplexing.
> >>>
> >>> In short I have analyzed the literature regarding:
> >>> 1) 2-way audio video communications
> >>> 2) Multiplayer gaming
> >>> 3) Remote control
> >>>
> >>> I will shortly just summarize the results without listing all =
sources.
> >>> Note: Under term latency one way delay is considered.
> >>>
> >>> For 2-way audio and video communication ITU.T recommendations =
state
> >>>that  150ms latency is needed for completely unimpaired
> >>>communication.
> >>> Latencies up to 400ms can be tolerated, but their impact is =
noticeable.
> >>>
> >>> Multiplayer gaming differs significantly on the genre.
> >>> The most demanding games are First Person Shooter (FPS) games =
which
> >>>require between 80ms and 100ms delay for unimpaired experience.
> >>> Some studies claim that Thrid Person Avatar games from which the
> >>>most  common are Role Playing Games (RPGs) and Massively =
Multiplayer
> >>>Role-  Playing Games MMORPGs tolerate latencies up to 500ms, but
> >>>other studies  state that a more realistic values for unimpaired
> >>>MMORPG experience is  between 120 and 200ms.
> >>> As for omnipresent games such as Real Time Strategies (RTS) it is
> >>>stated
> >> that
> >>> latencies up to 500ms and even up to 1000ms do not impair user
> >>> performance on objective metrics, but the evidence from RTS game
> >>> forums suggests that users are quite unsatisfied with latencies =
above
> 300ms.
> >>>
> >>> Remote control has different values of latency for different
> >>>services as
> >> well.
> >>> Remote surgery is stated that 330ms latency is acceptable, but for
> >> controlling
> >>> a robot in scope of end-to-end tele-echography showed that only
> >>>latencies  under 150ms are acceptable.
> >>>
> >>> What do you think is there a possibility to make an extended =
version
> >>> of
> >> such
> >>> a document and submit it as a draft?
> >>>
> >>> Thanks for any feedback!
> >>>
> >>> Mirko Suznjevic
> >>>
> >>> -----Original Message-----
> >>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
> >>> Behalf Of Jose Saldana
> >>> Sent: Thursday, September 27, 2012 12:31 PM
> >>> To: tcmtf@ietf.org
> >>> Cc: Wesley Eddy; Martin Stiemerling
> >>> Subject: [tcmtf] Next steps with TCMTF
> >>>
> >>> Hello all,
> >>>
> >>> I would like to discuss in this list the possibility of creating a
> >>>small
> >> Working
> >>> Group for TCMTF, as suggested by Wes. It could have the task of
> >>>making a  RFC from TCMTF, or a wider scope. I think that perhaps =
more
> >>>than a draft  would be necessary. I mean, I have been thinking =
about
> >>>it, and perhaps the  work could be divided into the next parts:
> >>>
> >>>   a) "Current draft": the main draft =
(draft-saldana-tsvwg-tcmtf-03),
> >> including
> >>> the protocol stack of TCMTF. The current proposal has different
> >>>options,
> >> but
> >>> the concrete one to use is static: in the set-up moment, you =
decide
> >>>that  "between these two routers a tunnel is set including all the
> >>>packets with
> >> this
> >>> IP origin and destination".
> >>>
> >>> b) "Recommendations draft": another "informational" one, with
> >>>recommendations of maximum delays to be added to different kinds of
> >>>services, different multiplexing policies, implementation issues
> >>>related
> >> to the
> >>> selection of the best compression algorithm to use, etc. Some
> >>>hypothetical
> >>> examples:
> >>>        -  "if you are multiplexing a First Person Shooter, your
> >>>multiplexer
> >> should
> >>> not retain packets more than 50 ms"
> >>> - "if you are multiplexing in a low-end router in a wired =
scenario,
> >>> you
> >> don't
> >>> need to use ROHC. A simpler scheme like IPHC can be enough, and it
> >>> will
> >> not
> >>> require a lot of processing capacity".
> >>>
> >>> c) "Dynamic Signaling draft": perhaps another one including a
> >>> signaling system in order to:
> >>>     - dynamically "negotiate" the concrete options of TCMTF you =
are
> >>> going to use
> >>>     - if two routers notice that a rush hour is arriving, they =
could
> >> send
> >>> some packets asking other routers if they have some flows in =
common
> >>>with  them, which could be multiplexed.
> >>>
> >>>
> >>> The main questions are:
> >>>
> >>> Is this enough for creating a working group?
> >>>
> >>> Do you think the distribution of the work into three draft makes =
sense?
> >>>
> >>> Is there any other issue which should be studied and standardized?
> >>>Perhaps
> >>> other people could imagine more things.
> >>>
> >>> So let's start the discussion.
> >>>
> >>> Thanks in advance,
> >>>
> >>> Jose
> >>>
> >>>
> >>> _______________________________________________
> >>> tcmtf mailing list
> >>> tcmtf@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>> _______________________________________________
> >>> tcmtf mailing list
> >>> tcmtf@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> _______________________________________________
> >> tcmtf mailing list
> >> tcmtf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >>
> >>
> >
> >_______________________________________________
> >tcmtf mailing list
> >tcmtf@ietf.org
> >https://www.ietf.org/mailman/listinfo/tcmtf
>=20
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar
> nuestra pol=C3=ADtica de env=C3=ADo y recepci=C3=B3n de correo =
electr=C3=B3nico en el enlace
> situado m=C3=A1s abajo.
> This message is intended exclusively for its addressee. We only send =
and
> receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar
> nuestra pol=C3=ADtica de env=C3=ADo y recepci=C3=B3n de correo =
electr=C3=B3nico en el enlace
> situado m=C3=A1s 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


From mns@tid.es  Wed Oct 24 03:48:21 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 E339E21F8BCB for <tcmtf@ietfa.amsl.com>; Wed, 24 Oct 2012 03:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.142
X-Spam-Level: 
X-Spam-Status: No, score=-6.142 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jrxrLn1D-bCX for <tcmtf@ietfa.amsl.com>; Wed, 24 Oct 2012 03:48:20 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6F35B21F8BD2 for <tcmtf@ietf.org>; Wed, 24 Oct 2012 03:48:18 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MCE00K7Q8OA4G@tid.hi.inet> for tcmtf@ietf.org; Wed, 24 Oct 2012 12:48:17 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 37.9D.03050.177C7805; Wed, 24 Oct 2012 12:48:17 +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 <0MCE00KA88OH4G@tid.hi.inet> for tcmtf@ietf.org; Wed, 24 Oct 2012 12:48:17 +0200 (MEST)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.178]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.004; Wed, 24 Oct 2012 12:48:16 +0200
Date: Wed, 24 Oct 2012 10:48:16 +0000
From: =?utf-8?B?TUFOVUVMIE5Vw5FFWiBTQU5a?= <mns@tid.es>
In-reply-to: <005c01cdb1d0$f71ab910$e5502b30$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, JUAN ANTONIO CASTELL LUCIA <jacl@tid.es>, FERNANDO PASCUAL BLANCO <fpb@tid.es>, =?utf-8?B?J0p1bGnDoW4gRmVybsOhbmRlei1OYXZhamFzJw==?= <navajas@unizar.es>
Message-id: <90ED8822CB577741B9A1668A475393121B8FD629@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: es-ES
Content-transfer-encoding: base64
Accept-Language: es-ES, en-US
Thread-topic: [tcmtf] Next steps with TCMTF
Thread-index: Ac2cmrry4BaRIpi1Sm27mcZI4g4aKwUW4ybw///h8wCAAZv/AIAAK92A///+BND//+wAAP//2FGg
X-AuditID: 0a5f4068-b7f176d000000bea-6e-5087c771d798
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrAKsWRmVeSWpSXmKPExsXCFe/ApVt4vD3AoLVR1GLX5w2MDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKuLT/D1PBkmbGih9r17I0MH6p72Lk5JAQMJE4/+M8M4QtJnHh 3nq2LkYuDiGBjYwSS7/cY4dwfjJK9E7ZyQLhbGKU2PxmGjtIC4uAqsS9Z1dYQGw2AXOJCzOv s4LYwgJaEr8+fQGr4RSwkDi65TgbxAoFiT/nHoPViwicZZRY+S25i5GDgxlozrxviiAmr4C3 xI+75SAVvAKCEj8m32OBqFCXmDIlFyTMLCAuMefXRFYIW1Fi2qIGRhCbUUBWYuX504wQw7Ul fn77xAZhx0h0Ns9lgjhAQGLJHph/RSVePv7HCvHVLaBjen6zTGAUn4Vk9SyE1bOQrJ6FZPUC RpZVjGLFSUWZ6RkluYmZOekGhnoZmXqZeaklmxghUZSxg3H5TpVDjAIcjEo8vAcutgUIsSaW FVfmHmKU5GBSEuVtONYeIMSXlJ9SmZFYnBFfVJqTWnyIUYKDWUmE98kqoBxvSmJlVWpRPkxK hoNDSYL3EEibYFFqempFWmYOMFXApJk4OEHaeYDaj4PU8BYXJOYWZ6ZD5E8xqnI09ix6yCjE kpeflyolzrsKpEgApCijNA9uzitGcaCDhXnfgGR5gMkObsIroOFMQMPNeVpBhpckIqSkGhgz J1Uersnwn6O4bYnNujCXhmap7oiT6nMDpfaukuJKmHr5Upgs3w6FSPf6zLVT5uWsnTOrZfH6 /At/V9bVWwb+2tIouu7YuUyT+yKxUz4npf3pCD//lv/aPv9Mu1M7NkTxel70T8jLu/GC0VEo 5WIF90SzBeVSX7ctuDaH7Wqt+ynlSN6FSjpKLMUZiYZazEXFiQBTvJJ9MwMAAA==
References: <5087AE2E.3040303@unizar.es> <F5EDC35DF914C1428C28E149F10463A24C74AB4F@EX10-MB1-MAD.hi.inet> <49F52EC1A431BA4BBA8BA8CFF429B739029A360C@EX10-MB1-MAD.hi.inet> <005c01cdb1d0$f71ab910$e5502b30$@unizar.es>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Next steps with 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, 24 Oct 2012 10:48:22 -0000

SGksDQoNCk9ubHkgdG8gYWRkIG15IHR3byBjZW50cy4gSW4gUlRTUCBjYXNlIHlvdSBhbHNvIGNv
dWxkIGhhdmUgYSBuZXcgZmxvdyBmcm9tIHNlcnZlciB0byAgdXNlcnMsIGlmIHRoZSBUViBuZWVk
cyAgYWRkIHBlcnNvbmFsaXplZCB0ZXh0IHVuZGVyIHlvdXIgc2hvdyAgcHJvZ3JhbS4gRm9yIGV4
YW1wbGU6IFJTUyBuZXdzLCBSU1MgcGVyc29uYWxpemVkIGFkdmVydGlzaW5nLi4uLiBJbiB0aGlz
IGNhc2UsIGFnYWluIHRoZSBudW1iZXIgb2Ygc21hbGwgcGFja2V0IHNlZW1zIGhpZ2guDQoNClJl
Z2FyZHMsDQogICAgIE1hbnVlbA0KDQoNCi0tLS0tTWVuc2FqZSBvcmlnaW5hbC0tLS0tDQpEZTog
dGNtdGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnRjbXRmLWJvdW5jZXNAaWV0Zi5vcmddIEVu
IG5vbWJyZSBkZSBKb3NlIFNhbGRhbmENCkVudmlhZG8gZWw6IG1pw6lyY29sZXMsIDI0IGRlIG9j
dHVicmUgZGUgMjAxMiAxMjoxOQ0KUGFyYTogSlVBTiBBTlRPTklPIENBU1RFTEwgTFVDSUE7IEZF
Uk5BTkRPIFBBU0NVQUwgQkxBTkNPOyAnSnVsacOhbiBGZXJuw6FuZGV6LU5hdmFqYXMnDQpDQzog
dGNtdGZAaWV0Zi5vcmcNCkFzdW50bzogUmU6IFt0Y210Zl0gTmV4dCBzdGVwcyB3aXRoIFRDTVRG
DQoNCldlIGFyZSB0aGlua2luZyBhIGxvdCwgYW5kIHRoaXMgaXMgZ29vZC4NCg0KTXkgb3Bpbmlv
bjogdGhlIG9wdGltaXphdGlvbiBpcyBvbmx5IGludGVyZXN0aW5nIGZvciBzZXJ2aWNlcyB3aXRo
Og0KDQotIHNtYWxsIHBhY2tldHMNCi0gYSBwbGFjZSB3aGVyZSBhIG51bWJlciBvZiBmbG93cyBj
YW4gYmUgbXVsdGlwbGV4ZWQNCi0gdGhlIG11bHRpcGxleGluZyBzYXZpbmcgaXMgaW50ZXJlc3Rp
bmcuIE9uZSBleGFtcGxlIGlzIGEgc2VydmljZSB3aXRoIHN1ZGRlbiBhbmQgaHVnZSB0cmFmZmlj
IGJ1cnN0cy4NCg0KSW4gdGhpcyBzZW5zZSwgSSB0aGluayB0aGF0IHRoZSB2b3Rpbmcgc2NoZW1l
IGZvciBhIFRWIHByb2dyYW0gY2FuIGJlIGludGVyZXN0aW5nLiBZb3VyIG5ldHdvcmsgaXMgZGlt
ZW5zaW9uZWQgZm9yIGEgbm9ybWFsIHBlcmZvcm1hbmNlLCBhbmQgaW4gMTAgc2Vjb25kcyB5b3Ug
aGF2ZSBtaWxsaW9ucyBvZiBwZW9wbGUgc2VuZGluZyBtZXNzYWdlczoganVzdCB3aGVuIHRoZSBw
cm9ncmFtIGhvc3Qgc2F5czogIndobyBpcyB0aGUgb25lIHlvdSB3YW50IHRvIGJhbiBmcm9tIHRo
ZSBwcm9ncmFtPyBTZW5kIHlvdXIgdm90ZXMganVzdCBub3ciDQoNCkFuZCBhIHdoYXRzYXBwLWxp
a2UgYXBwbGljYXRpb24gaGFzIHRoZSBzYW1lIHByb2JsZW06DQotIGFmdGVyIGEgZm9vdGJhbGwg
bWF0Y2gsIHlvdSBtYXkgbGlrZSB0byBwZXN0ZXIgdGhlIG9uZSB3aG9zZSB0ZWFtIGhhcyBsb3N0
LCBvciB0byBjb25ncmF0dWxhdGUgdGhlIHdpbm5lciAobGVzcyBmcmVxdWVudCkuDQotIGluIHRo
ZSBtaW51dGVzIGFyb3VuZCAwOjAwIG9mIE5ldyBZZWFyJ3MgZGF5LCB0aGVyZSBhcmUgbG90cyBv
ZiBwZW9wbGUgc2VuZGluZyBzaG9ydCBtZXNzYWdlcy4NCg0KUmVnYXJkaW5nIFJUU1AsIEkgZG9u
J3QgY2xlYXJseSBzZWUgYSBwbGFjZSB3aGVyZSBhIGJpZyBudW1iZXIgb2YgbWVzc2FnZXMgY2Fu
IGJlIGdyb3VwZWQuIFNvbWUgaGVscD8NCg0KQW5kIHJlZ2FyZGluZyB0ZWxlLWVjb2dyYXBoeSwg
SSB0aGluayB0aGF0IHRoZSBudW1iZXIgb2YgZWNvZ3JhcGh5IGRldmljZXMgaW4gYSBwbGFjZSB3
aWxsIGFsd2F5cyBiZSBzbWFsbC4gSW4gYWRkaXRpb24sIGRvY3RvcnMgYWx3YXlzIGhhdmUgbW9u
ZXkgdG8gc3BhcmUsIHNvIHRoZXkgZG9uJ3QgbmVlZCB0byBzYXZlIGJhbmR3aWR0aC4NCg0KVGhh
bmtzLA0KDQpKb3NlDQoNCj4gLS0tLS1NZW5zYWplIG9yaWdpbmFsLS0tLS0NCj4gRGU6IHRjbXRm
LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0Y210Zi1ib3VuY2VzQGlldGYub3JnXSBFbiBub21i
cmUNCj4gZGUgSlVBTiBBTlRPTklPIENBU1RFTEwgTFVDSUEgRW52aWFkbyBlbDogbWnDqXJjb2xl
cywgMjQgZGUgb2N0dWJyZSBkZQ0KPiAyMDEyIDEyOjAyDQo+IFBhcmE6IEZFUk5BTkRPIFBBU0NV
QUwgQkxBTkNPOyBKdWxpw6FuIEZlcm7DoW5kZXotTmF2YWphczsNCj4gdGNtdGZAaWV0Zi5vcmcN
Cj4gQXN1bnRvOiBSZTogW3RjbXRmXSBOZXh0IHN0ZXBzIHdpdGggVENNVEYNCj4NCj4gSGkgYWxs
LCBhbHRob3VnaCBpcyBub3QgYSBzdHJpY3RseSByZW1vdGUgY29udHJvbCB0b3BpYywgcmVnYXJk
aW5nDQo+IG1lZGlhIGNvbnN1bXB0aW9uLCBhIHBvc3NpYmxlIHVzZSBjYXNlIG9mIFRDTVRGIGFw
cGxpY2F0aW9uIHdpdGgNCj4gbXVsdGlwbGV4aW5nIElNSE8gY291bGQgYmUgaW50ZXJhY3RpdmUg
dGVsZXZpc2lvbiBwcm9ncmFtcy4gRm9yDQo+IGV4YW1wbGUsIHByb2dyYW1zIHdpdGggYSB2b3Rp
bmcgc2NoZW1lIChsZXQncyBkbyBhIG1vcmUgZmFpcg0KPiBFdXJvdmlzaW9uIHNvbmcgY29udGVz
dCA7bykpLiBUaGF0IHN1cHBvc2VzIHRoYXQgZHVyaW5nIGNlcnRhaW4NCj4gY29uY3JldGUgcGVy
aW9kIG9mIHRpbWUgcHJvZ3JhbSB3YXRjaGVycyB3b3VsZCBiZSBzaW11bHRhbmVvdXNseQ0KPiBz
ZW5kaW5nIHNtYWxsIChJIGd1ZXNzKSBwYWNrZXRzLiBUaGUgbGF0ZW5jeSByZXF1aXJlbWVudHMg
d291bGRuJ3QgYmUgdmVyeSBoaWdoLg0KPg0KPiBTbWFydCBUVnMgYXJlIGNvbWluZy4uLg0KPg0K
PiBXaGF0IGRvIHlvdSB0aGluaz8NCj4NCj4gUmVnYXJkcywNCj4gSnVhbiBBbnRvbmlvDQo+DQo+
DQo+DQo+IC0tLS0tTWVuc2FqZSBvcmlnaW5hbC0tLS0tDQo+IERlOiB0Y210Zi1ib3VuY2VzQGll
dGYub3JnIFttYWlsdG86dGNtdGYtYm91bmNlc0BpZXRmLm9yZ10gRW4gbm9tYnJlDQo+IGRlIEZF
Uk5BTkRPIFBBU0NVQUwgQkxBTkNPIEVudmlhZG8gZWw6IG1pw6lyY29sZXMsIDI0IGRlIG9jdHVi
cmUgZGUNCj4gMjAxMg0KPiAxMTozOA0KPiBQYXJhOiBKdWxpw6FuIEZlcm7DoW5kZXotTmF2YWph
czsgdGNtdGZAaWV0Zi5vcmcNCj4gQXN1bnRvOiBSZTogW3RjbXRmXSBOZXh0IHN0ZXBzIHdpdGgg
VENNVEYNCj4NCj4gSGkgYWxsLA0KPg0KPiAgICAgICAgIEFzIGEgZmlyc3QgdGhpbmtpbmcsIFJU
U1AgcHJvdG9jb2wgaGF2ZSBhIGNvbm5lY3Rpb24gY29udHJvbA0KPiBsYXllciB0aGF0IGxldCBj
bGllbnRzIHRvIHJlbW90ZWx5IGNvbnRyb2wgc3RyZWFtaW5nIHNlcnZlcnM6IHRoZXkgY2FuDQo+
IHJlbW90ZWx5IHBsYXkgb3IgcGF1c2UgdGhlIG1lZGlh4oCmIEkgZG9uwrR0IGtub3cgaWYgdGhh
dCB3b3VsZCBiZSBhbg0KPiBpbnRlcmVzdGluZyB1c2UgY2FzZSB3aGVuIG11bHRpcGxleGluZyB1
c2VycyBjb25zdW1pbmcgbWVkaWEgdW5kZXIgZGVtYW5kLg0KPg0KPiBSZWdhcmRzLA0KPg0KPiBG
ZXJuYW5kbyBQYXNjdWFsIEJsYW5jbw0KPiBUZWxlZsOzbmljYSBHbG9iYWwgUmVzb3VyY2VzDQo+
IE5ldHdvcmsgQXV0b21hdGlvbiBhbmQgRHluYW1pemF0aW9uDQo+IFRFQ0hOT0xPR1kgUEVPUExF
IEdST1VQDQo+IEYgKzM0OTEzMTI4Nzc5DQo+IE0gKzM0NjgyMDA1MTY4DQo+IGZwYkB0aWQuZXMN
Cj4NCj4NCj4NCj4NCj4gT24gMjQvMTAvMTIgMTE6MDAsICJKdWxpw6FuIEZlcm7DoW5kZXotTmF2
YWphcyIgPG5hdmFqYXNAdW5pemFyLmVzPiB3cm90ZToNCj4NCj4gPmhlbGxvIGFsbCwNCj4gPlJl
Z2FyZGluZyB0aGUgcmVhbC10aW1lIHNlcnZpY2VzIHN1aXRhYmxlIGZvciBtdWx0aXBsZXhpbmcs
IGkgaGF2ZSBhDQo+ID5xdWVzdGlvbiBhYm91dCB0aGUgdGhpcmQgb2YgdGhlbSwgcmVtb3RlIGNv
bnRyb2wuIEkgY2FuJ3QgdGhpbmsgYSB1c2UNCj4gPmNhc2UgdGhhdCB0cmFuc21pdHMgbGl0dGxl
IHBhY2tldHMgaW4gb3JkZXIgdG8gYmUgbXVsdGlwbGV4ZWQuIE1pcmtvDQo+ID5zdWdnZXN0cyB0
ZWxlLWVjaG9ncmFwaHkgYnV0IGl0IG5vIHNlZW1zIGEgdXNlIGNhc2UgdGhhdCB0cmFmZmljDQo+
ID5uZWVkcyBtdWx0aXBsZXhpb24gYmVjYXVzZSB0aGVyZSBhcmUgbm90IGEgbG90IG9mIHVzZXJz
IHNpbXVsdGFuZXVzbHkuDQo+ID5MZXQgdXMgdGhpbmtpbmcgYWJvdXQgcmVtb3RlIGNvbnRyb2wg
YW5kIHRoZSBwb3NzaWJsZSB1c2UgY2FzZXMgdGhhdA0KPiA+Y2FuIGJlIHByZXNlbnRlZCBoZXJl
Lg0KPiA+DQo+ID5KdWxpw6FuDQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPkVsIDIzLzEwLzIwMTIg
MTA6MjUsIEpvc2UgU2FsZGFuYSBlc2NyaWJpw7M6DQo+ID4+IE1pcmtvLA0KPiA+Pg0KPiA+PiBU
aGlzIHNvdW5kcyByZWFsbHkgZ29vZCEuIFRoaXMgd2FzIHRoZSBpZGVhIG9mICJkcmFmdCBiKSIu
DQo+ID4+DQo+ID4+IERvIHlvdSB0aGluayB5b3UgaGF2ZSBpbmNsdWRlZCBhbGwgdGhlIHNlcnZp
Y2VzIHdoaWNoIGNhbiBiZQ0KPiA+Pm11bHRpcGxleGVkICB3aXRoIFRDTVRGPyBJIG1lYW46IHNt
YWxsIHBhY2tldHMgYW5kIGhpZ2ggb3ZlcmhlYWQuDQo+ID4+U29tZQ0KPiA+PmlkZWFzOiBzZW5z
b3IgIG5ldHdvcmtzIHNlbmRpbmcgYSBzYW1wbGUsIHZpZGVvLXN1cnZlaWxsYW5jZSwNCj4gPj53
aGF0c2FwcC1saWtlIGFwcGxpY2F0aW9ucz8NCj4gPj4gQWx0aG91Z2ggc29tZSBvZiB0aGVtIGFy
ZSBub3QgcmVhbC10aW1lLCBwZXJoYXBzIHRoZXkgY2FuIGFsc28gYmUNCj4gPj5tdWx0aXBsZXhl
ZCBpZiB0aGUgbnVtYmVyIG9mIHBhY2tldHMgcGVyIHNlY29uZCBpcyBiaWcuDQo+ID4+DQo+ID4+
IFNvIHBlcmhhcHMgYSBzZWN0aW9uIGVudW1lcmF0aW5nIG5vbiByZWFsLXRpbWUgYXBwbGljYXRp
b25zIHdpdGgNCj4gPj5zbWFsbCAgcGFja2V0cyBjb3VsZCBhbHNvIGJlIGludGVyZXN0aW5nOiBm
b3IgZXhhbXBsZSAiaW5zdGFudA0KPiA+Pm1lc3NhZ2luZyAgYXBwbGljYXRpb25zIGNhbiB0b2xl
cmF0ZSB1cCB0byA1IHNlY29uZHMgb2YgZGVsYXkiIChJDQo+ID4+aGF2ZSBqdXN0IGludmVudGVk
ICB0aGUgZmlndXJlLCBpdCdzIG9ubHkgYW4gZXhhbXBsZSkuDQo+ID4+DQo+ID4+IEkgY291bGQg
aGVscCB5b3Ugd2l0aCB0aGlzLCBpZiB5b3UgYWdyZWUsIG9mIGNvdXJzZS4NCj4gPj4NCj4gPj4g
VGhhbmtzLA0KPiA+Pg0KPiA+PiBKb3NlDQo+ID4+DQo+ID4+PiAtLS0tLU1lbnNhamUgb3JpZ2lu
YWwtLS0tLQ0KPiA+Pj4gRGU6IHRjbXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0Y210Zi1i
b3VuY2VzQGlldGYub3JnXSBFbg0KPiBub21icmUNCj4gPj4+IGRlIE1pcmtvIFN1xb5uamV2aWMg
RW52aWFkbyBlbDogbWFydGVzLCAyMyBkZSBvY3R1YnJlIGRlIDIwMTIgMTA6MTQNCj4gPj4+IFBh
cmE6IHRjbXRmQGlldGYub3JnDQo+ID4+PiBBc3VudG86IFJlOiBbdGNtdGZdIE5leHQgc3RlcHMg
d2l0aCBUQ01URg0KPiA+Pj4NCj4gPj4+IEhlbGxvIGFsbCwNCj4gPj4+DQo+ID4+PiBSZWdhcmRp
bmcgdGhlIGIpICJSZWNvbW1lbmRhdGlvbnMgZHJhZnQiIEkgaGF2ZSBjcmVhdGVkIGEgZmlyc3QN
Cj4gPj4+c3VtbWFyeSBvZiAgcmVhbC10aW1lIHNlcnZpY2VzIHN1aXRhYmxlIGZvciBtdWx0aXBs
ZXhpbmcuDQo+ID4+Pg0KPiA+Pj4gSW4gc2hvcnQgSSBoYXZlIGFuYWx5emVkIHRoZSBsaXRlcmF0
dXJlIHJlZ2FyZGluZzoNCj4gPj4+IDEpIDItd2F5IGF1ZGlvIHZpZGVvIGNvbW11bmljYXRpb25z
DQo+ID4+PiAyKSBNdWx0aXBsYXllciBnYW1pbmcNCj4gPj4+IDMpIFJlbW90ZSBjb250cm9sDQo+
ID4+Pg0KPiA+Pj4gSSB3aWxsIHNob3J0bHkganVzdCBzdW1tYXJpemUgdGhlIHJlc3VsdHMgd2l0
aG91dCBsaXN0aW5nIGFsbCBzb3VyY2VzLg0KPiA+Pj4gTm90ZTogVW5kZXIgdGVybSBsYXRlbmN5
IG9uZSB3YXkgZGVsYXkgaXMgY29uc2lkZXJlZC4NCj4gPj4+DQo+ID4+PiBGb3IgMi13YXkgYXVk
aW8gYW5kIHZpZGVvIGNvbW11bmljYXRpb24gSVRVLlQgcmVjb21tZW5kYXRpb25zDQo+ID4+PnN0
YXRlIHRoYXQgIDE1MG1zIGxhdGVuY3kgaXMgbmVlZGVkIGZvciBjb21wbGV0ZWx5IHVuaW1wYWly
ZWQNCj4gPj4+Y29tbXVuaWNhdGlvbi4NCj4gPj4+IExhdGVuY2llcyB1cCB0byA0MDBtcyBjYW4g
YmUgdG9sZXJhdGVkLCBidXQgdGhlaXIgaW1wYWN0IGlzIG5vdGljZWFibGUuDQo+ID4+Pg0KPiA+
Pj4gTXVsdGlwbGF5ZXIgZ2FtaW5nIGRpZmZlcnMgc2lnbmlmaWNhbnRseSBvbiB0aGUgZ2VucmUu
DQo+ID4+PiBUaGUgbW9zdCBkZW1hbmRpbmcgZ2FtZXMgYXJlIEZpcnN0IFBlcnNvbiBTaG9vdGVy
IChGUFMpIGdhbWVzDQo+ID4+PndoaWNoIHJlcXVpcmUgYmV0d2VlbiA4MG1zIGFuZCAxMDBtcyBk
ZWxheSBmb3IgdW5pbXBhaXJlZCBleHBlcmllbmNlLg0KPiA+Pj4gU29tZSBzdHVkaWVzIGNsYWlt
IHRoYXQgVGhyaWQgUGVyc29uIEF2YXRhciBnYW1lcyBmcm9tIHdoaWNoIHRoZQ0KPiA+Pj5tb3N0
ICBjb21tb24gYXJlIFJvbGUgUGxheWluZyBHYW1lcyAoUlBHcykgYW5kIE1hc3NpdmVseQ0KPiA+
Pj5NdWx0aXBsYXllcg0KPiA+Pj5Sb2xlLSAgUGxheWluZyBHYW1lcyBNTU9SUEdzIHRvbGVyYXRl
IGxhdGVuY2llcyB1cCB0byA1MDBtcywgYnV0DQo+ID4+Pm90aGVyIHN0dWRpZXMgIHN0YXRlIHRo
YXQgYSBtb3JlIHJlYWxpc3RpYyB2YWx1ZXMgZm9yIHVuaW1wYWlyZWQNCj4gPj4+TU1PUlBHIGV4
cGVyaWVuY2UgaXMgIGJldHdlZW4gMTIwIGFuZCAyMDBtcy4NCj4gPj4+IEFzIGZvciBvbW5pcHJl
c2VudCBnYW1lcyBzdWNoIGFzIFJlYWwgVGltZSBTdHJhdGVnaWVzIChSVFMpIGl0IGlzDQo+ID4+
PnN0YXRlZA0KPiA+PiB0aGF0DQo+ID4+PiBsYXRlbmNpZXMgdXAgdG8gNTAwbXMgYW5kIGV2ZW4g
dXAgdG8gMTAwMG1zIGRvIG5vdCBpbXBhaXIgdXNlcg0KPiA+Pj4gcGVyZm9ybWFuY2Ugb24gb2Jq
ZWN0aXZlIG1ldHJpY3MsIGJ1dCB0aGUgZXZpZGVuY2UgZnJvbSBSVFMgZ2FtZQ0KPiA+Pj4gZm9y
dW1zIHN1Z2dlc3RzIHRoYXQgdXNlcnMgYXJlIHF1aXRlIHVuc2F0aXNmaWVkIHdpdGggbGF0ZW5j
aWVzDQo+ID4+PiBhYm92ZQ0KPiAzMDBtcy4NCj4gPj4+DQo+ID4+PiBSZW1vdGUgY29udHJvbCBo
YXMgZGlmZmVyZW50IHZhbHVlcyBvZiBsYXRlbmN5IGZvciBkaWZmZXJlbnQNCj4gPj4+c2Vydmlj
ZXMgYXMNCj4gPj4gd2VsbC4NCj4gPj4+IFJlbW90ZSBzdXJnZXJ5IGlzIHN0YXRlZCB0aGF0IDMz
MG1zIGxhdGVuY3kgaXMgYWNjZXB0YWJsZSwgYnV0IGZvcg0KPiA+PiBjb250cm9sbGluZw0KPiA+
Pj4gYSByb2JvdCBpbiBzY29wZSBvZiBlbmQtdG8tZW5kIHRlbGUtZWNob2dyYXBoeSBzaG93ZWQg
dGhhdCBvbmx5DQo+ID4+PmxhdGVuY2llcyAgdW5kZXIgMTUwbXMgYXJlIGFjY2VwdGFibGUuDQo+
ID4+Pg0KPiA+Pj4gV2hhdCBkbyB5b3UgdGhpbmsgaXMgdGhlcmUgYSBwb3NzaWJpbGl0eSB0byBt
YWtlIGFuIGV4dGVuZGVkDQo+ID4+PiB2ZXJzaW9uIG9mDQo+ID4+IHN1Y2gNCj4gPj4+IGEgZG9j
dW1lbnQgYW5kIHN1Ym1pdCBpdCBhcyBhIGRyYWZ0Pw0KPiA+Pj4NCj4gPj4+IFRoYW5rcyBmb3Ig
YW55IGZlZWRiYWNrIQ0KPiA+Pj4NCj4gPj4+IE1pcmtvIFN1em5qZXZpYw0KPiA+Pj4NCj4gPj4+
IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+PiBGcm9tOiB0Y210Zi1ib3VuY2VzQGll
dGYub3JnIFttYWlsdG86dGNtdGYtYm91bmNlc0BpZXRmLm9yZ10gT24NCj4gPj4+IEJlaGFsZiBP
ZiBKb3NlIFNhbGRhbmENCj4gPj4+IFNlbnQ6IFRodXJzZGF5LCBTZXB0ZW1iZXIgMjcsIDIwMTIg
MTI6MzEgUE0NCj4gPj4+IFRvOiB0Y210ZkBpZXRmLm9yZw0KPiA+Pj4gQ2M6IFdlc2xleSBFZGR5
OyBNYXJ0aW4gU3RpZW1lcmxpbmcNCj4gPj4+IFN1YmplY3Q6IFt0Y210Zl0gTmV4dCBzdGVwcyB3
aXRoIFRDTVRGDQo+ID4+Pg0KPiA+Pj4gSGVsbG8gYWxsLA0KPiA+Pj4NCj4gPj4+IEkgd291bGQg
bGlrZSB0byBkaXNjdXNzIGluIHRoaXMgbGlzdCB0aGUgcG9zc2liaWxpdHkgb2YgY3JlYXRpbmcg
YQ0KPiA+Pj5zbWFsbA0KPiA+PiBXb3JraW5nDQo+ID4+PiBHcm91cCBmb3IgVENNVEYsIGFzIHN1
Z2dlc3RlZCBieSBXZXMuIEl0IGNvdWxkIGhhdmUgdGhlIHRhc2sgb2YNCj4gPj4+bWFraW5nIGEg
IFJGQyBmcm9tIFRDTVRGLCBvciBhIHdpZGVyIHNjb3BlLiBJIHRoaW5rIHRoYXQgcGVyaGFwcw0K
PiA+Pj5tb3JlIHRoYW4gYSBkcmFmdCAgd291bGQgYmUgbmVjZXNzYXJ5LiBJIG1lYW4sIEkgaGF2
ZSBiZWVuIHRoaW5raW5nDQo+ID4+PmFib3V0IGl0LCBhbmQgcGVyaGFwcyB0aGUgIHdvcmsgY291
bGQgYmUgZGl2aWRlZCBpbnRvIHRoZSBuZXh0IHBhcnRzOg0KPiA+Pj4NCj4gPj4+ICAgYSkgIkN1
cnJlbnQgZHJhZnQiOiB0aGUgbWFpbiBkcmFmdA0KPiA+Pj4gKGRyYWZ0LXNhbGRhbmEtdHN2d2ct
dGNtdGYtMDMpLA0KPiA+PiBpbmNsdWRpbmcNCj4gPj4+IHRoZSBwcm90b2NvbCBzdGFjayBvZiBU
Q01URi4gVGhlIGN1cnJlbnQgcHJvcG9zYWwgaGFzIGRpZmZlcmVudA0KPiA+Pj5vcHRpb25zLA0K
PiA+PiBidXQNCj4gPj4+IHRoZSBjb25jcmV0ZSBvbmUgdG8gdXNlIGlzIHN0YXRpYzogaW4gdGhl
IHNldC11cCBtb21lbnQsIHlvdQ0KPiA+Pj5kZWNpZGUgdGhhdCAgImJldHdlZW4gdGhlc2UgdHdv
IHJvdXRlcnMgYSB0dW5uZWwgaXMgc2V0IGluY2x1ZGluZw0KPiA+Pj5hbGwgdGhlIHBhY2tldHMg
d2l0aA0KPiA+PiB0aGlzDQo+ID4+PiBJUCBvcmlnaW4gYW5kIGRlc3RpbmF0aW9uIi4NCj4gPj4+
DQo+ID4+PiBiKSAiUmVjb21tZW5kYXRpb25zIGRyYWZ0IjogYW5vdGhlciAiaW5mb3JtYXRpb25h
bCIgb25lLCB3aXRoDQo+ID4+PnJlY29tbWVuZGF0aW9ucyBvZiBtYXhpbXVtIGRlbGF5cyB0byBi
ZSBhZGRlZCB0byBkaWZmZXJlbnQga2luZHMgb2YNCj4gPj4+c2VydmljZXMsIGRpZmZlcmVudCBt
dWx0aXBsZXhpbmcgcG9saWNpZXMsIGltcGxlbWVudGF0aW9uIGlzc3Vlcw0KPiA+Pj5yZWxhdGVk
DQo+ID4+IHRvIHRoZQ0KPiA+Pj4gc2VsZWN0aW9uIG9mIHRoZSBiZXN0IGNvbXByZXNzaW9uIGFs
Z29yaXRobSB0byB1c2UsIGV0Yy4gU29tZQ0KPiA+Pj5oeXBvdGhldGljYWwNCj4gPj4+IGV4YW1w
bGVzOg0KPiA+Pj4gICAgICAgIC0gICJpZiB5b3UgYXJlIG11bHRpcGxleGluZyBhIEZpcnN0IFBl
cnNvbiBTaG9vdGVyLCB5b3VyDQo+ID4+Pm11bHRpcGxleGVyDQo+ID4+IHNob3VsZA0KPiA+Pj4g
bm90IHJldGFpbiBwYWNrZXRzIG1vcmUgdGhhbiA1MCBtcyINCj4gPj4+IC0gImlmIHlvdSBhcmUg
bXVsdGlwbGV4aW5nIGluIGEgbG93LWVuZCByb3V0ZXIgaW4gYSB3aXJlZA0KPiA+Pj4gc2NlbmFy
aW8sIHlvdQ0KPiA+PiBkb24ndA0KPiA+Pj4gbmVlZCB0byB1c2UgUk9IQy4gQSBzaW1wbGVyIHNj
aGVtZSBsaWtlIElQSEMgY2FuIGJlIGVub3VnaCwgYW5kIGl0DQo+ID4+PiB3aWxsDQo+ID4+IG5v
dA0KPiA+Pj4gcmVxdWlyZSBhIGxvdCBvZiBwcm9jZXNzaW5nIGNhcGFjaXR5Ii4NCj4gPj4+DQo+
ID4+PiBjKSAiRHluYW1pYyBTaWduYWxpbmcgZHJhZnQiOiBwZXJoYXBzIGFub3RoZXIgb25lIGlu
Y2x1ZGluZyBhDQo+ID4+PiBzaWduYWxpbmcgc3lzdGVtIGluIG9yZGVyIHRvOg0KPiA+Pj4gICAg
IC0gZHluYW1pY2FsbHkgIm5lZ290aWF0ZSIgdGhlIGNvbmNyZXRlIG9wdGlvbnMgb2YgVENNVEYg
eW91DQo+ID4+PiBhcmUgZ29pbmcgdG8gdXNlDQo+ID4+PiAgICAgLSBpZiB0d28gcm91dGVycyBu
b3RpY2UgdGhhdCBhIHJ1c2ggaG91ciBpcyBhcnJpdmluZywgdGhleQ0KPiA+Pj4gY291bGQNCj4g
Pj4gc2VuZA0KPiA+Pj4gc29tZSBwYWNrZXRzIGFza2luZyBvdGhlciByb3V0ZXJzIGlmIHRoZXkg
aGF2ZSBzb21lIGZsb3dzIGluDQo+ID4+PmNvbW1vbiB3aXRoICB0aGVtLCB3aGljaCBjb3VsZCBi
ZSBtdWx0aXBsZXhlZC4NCj4gPj4+DQo+ID4+Pg0KPiA+Pj4gVGhlIG1haW4gcXVlc3Rpb25zIGFy
ZToNCj4gPj4+DQo+ID4+PiBJcyB0aGlzIGVub3VnaCBmb3IgY3JlYXRpbmcgYSB3b3JraW5nIGdy
b3VwPw0KPiA+Pj4NCj4gPj4+IERvIHlvdSB0aGluayB0aGUgZGlzdHJpYnV0aW9uIG9mIHRoZSB3
b3JrIGludG8gdGhyZWUgZHJhZnQgbWFrZXMgc2Vuc2U/DQo+ID4+Pg0KPiA+Pj4gSXMgdGhlcmUg
YW55IG90aGVyIGlzc3VlIHdoaWNoIHNob3VsZCBiZSBzdHVkaWVkIGFuZCBzdGFuZGFyZGl6ZWQ/
DQo+ID4+PlBlcmhhcHMNCj4gPj4+IG90aGVyIHBlb3BsZSBjb3VsZCBpbWFnaW5lIG1vcmUgdGhp
bmdzLg0KPiA+Pj4NCj4gPj4+IFNvIGxldCdzIHN0YXJ0IHRoZSBkaXNjdXNzaW9uLg0KPiA+Pj4N
Cj4gPj4+IFRoYW5rcyBpbiBhZHZhbmNlLA0KPiA+Pj4NCj4gPj4+IEpvc2UNCj4gPj4+DQo+ID4+
Pg0KPiA+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cj4gPj4+IHRjbXRmIG1haWxpbmcgbGlzdA0KPiA+Pj4gdGNtdGZAaWV0Zi5vcmcNCj4gPj4+IGh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCj4gPj4+IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+PiB0Y210ZiBtYWls
aW5nIGxpc3QNCj4gPj4+IHRjbXRmQGlldGYub3JnDQo+ID4+PiBodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQo+ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQo+ID4+IHRjbXRmIG1haWxpbmcgbGlzdA0KPiA+PiB0Y210
ZkBpZXRmLm9yZw0KPiA+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Rj
bXRmDQo+ID4+DQo+ID4+DQo+ID4NCj4gPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fDQo+ID50Y210ZiBtYWlsaW5nIGxpc3QNCj4gPnRjbXRmQGlldGYub3Jn
DQo+ID5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQo+DQo+DQo+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+DQo+IEVzdGUgbWVuc2FqZSBzZSBk
aXJpZ2UgZXhjbHVzaXZhbWVudGUgYSBzdSBkZXN0aW5hdGFyaW8uIFB1ZWRlDQo+IGNvbnN1bHRh
ciBudWVzdHJhIHBvbMOtdGljYSBkZSBlbnbDrW8geSByZWNlcGNpw7NuIGRlIGNvcnJlbyBlbGVj
dHLDs25pY28NCj4gZW4gZWwgZW5sYWNlIHNpdHVhZG8gbcOhcyBhYmFqby4NCj4gVGhpcyBtZXNz
YWdlIGlzIGludGVuZGVkIGV4Y2x1c2l2ZWx5IGZvciBpdHMgYWRkcmVzc2VlLiBXZSBvbmx5IHNl
bmQNCj4gYW5kIHJlY2VpdmUgZW1haWwgb24gdGhlIGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQgb3V0
IGF0Og0KPiBodHRwOi8vd3d3LnRpZC5lcy9FUy9QQUdJTkFTL2Rpc2NsYWltZXIuYXNweA0KPiBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiB0Y210ZiBt
YWlsaW5nIGxpc3QNCj4gdGNtdGZAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby90Y210Zg0KPg0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPg0KPiBFc3RlIG1lbnNhamUgc2UgZGlyaWdlIGV4Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGlu
YXRhcmlvLiBQdWVkZQ0KPiBjb25zdWx0YXIgbnVlc3RyYSBwb2zDrXRpY2EgZGUgZW52w61vIHkg
cmVjZXBjacOzbiBkZSBjb3JyZW8gZWxlY3Ryw7NuaWNvDQo+IGVuIGVsIGVubGFjZSBzaXR1YWRv
IG3DoXMgYWJham8uDQo+IFRoaXMgbWVzc2FnZSBpcyBpbnRlbmRlZCBleGNsdXNpdmVseSBmb3Ig
aXRzIGFkZHJlc3NlZS4gV2Ugb25seSBzZW5kDQo+IGFuZCByZWNlaXZlIGVtYWlsIG9uIHRoZSBi
YXNpcyBvZiB0aGUgdGVybXMgc2V0IG91dCBhdDoNCj4gaHR0cDovL3d3dy50aWQuZXMvRVMvUEFH
SU5BUy9kaXNjbGFpbWVyLmFzcHgNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCnRjbXRmIG1haWxpbmcgbGlzdA0KdGNtdGZAaWV0Zi5vcmcNCmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCg0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCg0KRXN0ZSBtZW5zYWplIHNlIGRpcmlnZSBleGNsdXNpdmFtZW50
ZSBhIHN1IGRlc3RpbmF0YXJpby4gUHVlZGUgY29uc3VsdGFyIG51ZXN0cmEgcG9sw610aWNhIGRl
IGVudsOtbyB5IHJlY2VwY2nDs24gZGUgY29ycmVvIGVsZWN0csOzbmljbyBlbiBlbCBlbmxhY2Ug
c2l0dWFkbyBtw6FzIGFiYWpvLg0KVGhpcyBtZXNzYWdlIGlzIGludGVuZGVkIGV4Y2x1c2l2ZWx5
IGZvciBpdHMgYWRkcmVzc2VlLiBXZSBvbmx5IHNlbmQgYW5kIHJlY2VpdmUgZW1haWwgb24gdGhl
IGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQgb3V0IGF0Og0KaHR0cDovL3d3dy50aWQuZXMvRVMvUEFH
SU5BUy9kaXNjbGFpbWVyLmFzcHgNCg==

From Mirko.Suznjevic@fer.hr  Fri Oct 26 02:17:11 2012
Return-Path: <Mirko.Suznjevic@fer.hr>
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 2174B21F84F8 for <tcmtf@ietfa.amsl.com>; Fri, 26 Oct 2012 02:17:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8H9M76GEfkgk for <tcmtf@ietfa.amsl.com>; Fri, 26 Oct 2012 02:17:10 -0700 (PDT)
Received: from mail.zvne.fer.hr (mail.zvne.fer.hr [161.53.66.5]) by ietfa.amsl.com (Postfix) with ESMTP id A316621F84F3 for <tcmtf@ietf.org>; Fri, 26 Oct 2012 02:17:08 -0700 (PDT)
Received: from munja.zvne.fer.hr (161.53.66.248) by mail.zvne.fer.hr (161.53.66.5) with Microsoft SMTP Server id 14.2.298.4; Fri, 26 Oct 2012 11:17:04 +0200
Received: from sluga.fer.hr ([161.53.66.244]) by munja.zvne.fer.hr with Microsoft SMTPSVC(6.0.3790.4675);	 Fri, 26 Oct 2012 11:17:04 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 26 Oct 2012 11:17:05 +0200
Message-ID: <A3179A2C9AAEE647BE70AC4C7881D5FB0167E732@sluga.fer.hr>
In-Reply-To: <5087AE2E.3040303@unizar.es>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcmtf] Next steps with TCMTF
Thread-Index: Ac2xxg7NNbFA3uVbQ72RSEsYnvB4nwBlHgsw
References: <007801cd9c9b$3b06d5a0$b11480e0$@unizar.es><A3179A2C9AAEE647BE70AC4C7881D5FB0167E5BC@sluga.fer.hr><003601cdb0f8$04f119a0$0ed34ce0$@unizar.es> <5087AE2E.3040303@unizar.es>
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: =?iso-8859-2?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>, <tcmtf@ietf.org>
X-OriginalArrivalTime: 26 Oct 2012 09:17:04.0491 (UTC) FILETIME=[AA0B53B0:01CDB35A]
Subject: Re: [tcmtf] Next steps with 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, 26 Oct 2012 09:17:11 -0000

Hello all,

Yes this is true,
This was just an example of remote control services for which I found =
data regarding latency values in the literature.
I think that the most used remote control real time services would be =
remote desktop. If a whole company accesses one server on which the =
virtualized PCs are hosted shared network path is very long (especially =
if you take into consideration clouds). And remote desktop packets are =
quite small in terms of packet size and therefore good for TCMTF.

Sadly, I have not yet found any data regarding QoS or QoE for those =
services, but I am sure that there exist somewhere in the literature.

Cheers!
Mirko

-----Original Message-----
From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =
Of Juli=E1n Fern=E1ndez-Navajas
Sent: Wednesday, October 24, 2012 11:01 AM
To: tcmtf@ietf.org
Subject: Re: [tcmtf] Next steps with TCMTF

hello all,
Regarding the real-time services suitable for multiplexing, i have a =
question about the third of them, remote control. I can't think a use =
case that transmits little packets in order to be multiplexed. Mirko =
suggests tele-echography but it no seems a use case that traffic needs =
multiplexion because there are not a lot of users simultaneusly.
Let us thinking about remote control and the possible use cases that can =
be presented here.

Juli=E1n




El 23/10/2012 10:25, Jose Saldana escribi=F3:
> Mirko,
>
> This sounds really good!. This was the idea of "draft b)".
>
> Do you think you have included all the services which can be=20
> multiplexed with TCMTF? I mean: small packets and high overhead. Some=20
> ideas: sensor networks sending a sample, video-surveillance, =
whatsapp-like applications?
> Although some of them are not real-time, perhaps they can also be=20
> multiplexed if the number of packets per second is big.
>
> So perhaps a section enumerating non real-time applications with small =

> packets could also be interesting: for example "instant messaging=20
> applications can tolerate up to 5 seconds of delay" (I have just=20
> invented the figure, it's only an example).
>
> I could help you with this, if you agree, of course.
>
> Thanks,
>
> Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre=20
>> de Mirko Su=BEnjevic Enviado el: martes, 23 de octubre de 2012 10:14
>> Para: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] Next steps with TCMTF
>>
>> Hello all,
>>
>> Regarding the b) "Recommendations draft" I have created a first=20
>> summary of real-time services suitable for multiplexing.
>>
>> In short I have analyzed the literature regarding:
>> 1) 2-way audio video communications
>> 2) Multiplayer gaming
>> 3) Remote control
>>
>> I will shortly just summarize the results without listing all =
sources.
>> Note: Under term latency one way delay is considered.
>>
>> For 2-way audio and video communication ITU.T recommendations state=20
>> that 150ms latency is needed for completely unimpaired communication.
>> Latencies up to 400ms can be tolerated, but their impact is =
noticeable.
>>
>> Multiplayer gaming differs significantly on the genre.
>> The most demanding games are First Person Shooter (FPS) games which=20
>> require between 80ms and 100ms delay for unimpaired experience.
>> Some studies claim that Thrid Person Avatar games from which the most =

>> common are Role Playing Games (RPGs) and Massively Multiplayer Role-=20
>> Playing Games MMORPGs tolerate latencies up to 500ms, but other=20
>> studies state that a more realistic values for unimpaired MMORPG=20
>> experience is between 120 and 200ms.
>> As for omnipresent games such as Real Time Strategies (RTS) it is=20
>> stated
> that
>> latencies up to 500ms and even up to 1000ms do not impair user=20
>> performance on objective metrics, but the evidence from RTS game=20
>> forums suggests that users are quite unsatisfied with latencies above =
300ms.
>>
>> Remote control has different values of latency for different services =

>> as
> well.
>> Remote surgery is stated that 330ms latency is acceptable, but for
> controlling
>> a robot in scope of end-to-end tele-echography showed that only=20
>> latencies under 150ms are acceptable.
>>
>> What do you think is there a possibility to make an extended version=20
>> of
> such
>> a document and submit it as a draft?
>>
>> Thanks for any feedback!
>>
>> Mirko Suznjevic
>>
>> -----Original Message-----
>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On=20
>> Behalf Of Jose Saldana
>> Sent: Thursday, September 27, 2012 12:31 PM
>> To: tcmtf@ietf.org
>> Cc: Wesley Eddy; Martin Stiemerling
>> Subject: [tcmtf] Next steps with TCMTF
>>
>> Hello all,
>>
>> I would like to discuss in this list the possibility of creating a=20
>> small
> Working
>> Group for TCMTF, as suggested by Wes. It could have the task of=20
>> making a RFC from TCMTF, or a wider scope. I think that perhaps more=20
>> than a draft would be necessary. I mean, I have been thinking about=20
>> it, and perhaps the work could be divided into the next parts:
>>
>>   a) "Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03),
> including
>> the protocol stack of TCMTF. The current proposal has different=20
>> options,
> but
>> the concrete one to use is static: in the set-up moment, you decide=20
>> that "between these two routers a tunnel is set including all the=20
>> packets with
> this
>> IP origin and destination".
>>
>> b) "Recommendations draft": another "informational" one, with=20
>> recommendations of maximum delays to be added to different kinds of=20
>> services, different multiplexing policies, implementation issues=20
>> related
> to the
>> selection of the best compression algorithm to use, etc. Some=20
>> hypothetical
>> examples:
>>        -  "if you are multiplexing a First Person Shooter, your=20
>> multiplexer
> should
>> not retain packets more than 50 ms"
>> - "if you are multiplexing in a low-end router in a wired scenario,=20
>> you
> don't
>> need to use ROHC. A simpler scheme like IPHC can be enough, and it=20
>> will
> not
>> require a lot of processing capacity".
>>
>> c) "Dynamic Signaling draft": perhaps another one including a=20
>> signaling system in order to:
>>   	- dynamically "negotiate" the concrete options of TCMTF you are=20
>> going to use
>>   	- if two routers notice that a rush hour is arriving, they could
> send
>> some packets asking other routers if they have some flows in common=20
>> with them, which could be multiplexed.
>>
>>
>> The main questions are:
>>
>> Is this enough for creating a working group?
>>
>> Do you think the distribution of the work into three draft makes =
sense?
>>
>> Is there any other issue which should be studied and standardized?=20
>> Perhaps other people could imagine more things.
>>
>> So let's start the discussion.
>>
>> Thanks in advance,
>>
>> Jose
>>
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>
>

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

From diego@tid.es  Sat Oct 27 01:38:06 2012
Return-Path: <diego@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC24A21F84DF for <tcmtf@ietfa.amsl.com>; Sat, 27 Oct 2012 01:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.149
X-Spam-Level: 
X-Spam-Status: No, score=-5.149 tagged_above=-999 required=5 tests=[AWL=1.150,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NqrEyYi8dEAa for <tcmtf@ietfa.amsl.com>; Sat, 27 Oct 2012 01:38:05 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 527EF21F84D7 for <tcmtf@ietf.org>; Sat, 27 Oct 2012 01:38:04 -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 <0MCJ003I8MNE0D@tid.hi.inet> for tcmtf@ietf.org; Sat, 27 Oct 2012 10:38:02 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id DE.33.05494.A6D9B805; Sat, 27 Oct 2012 10:38:02 +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 <0MCJ003I2MNE0D@tid.hi.inet> for tcmtf@ietf.org; Sat, 27 Oct 2012 10:38:02 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.242]) by ex10-htcas3-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Sat, 27 Oct 2012 10:38:01 +0200
Date: Sat, 27 Oct 2012 08:38:00 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <A3179A2C9AAEE647BE70AC4C7881D5FB0167E732@sluga.fer.hr>
X-Originating-IP: [10.95.64.115]
To: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A044F557A9D@EX10-MB2-MAD.hi.inet>
Content-id: <3DDCA9478F235A4F8E88E0288C1F0DD1@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-2
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [tcmtf] Next steps with TCMTF
Thread-index: Ac2cmrry4BaRIpi1Sm27mcZI4g4aKwUW4ybw///h8wCAAZv/AIADKUyAgAGHY4A=
X-AuditID: 0a5f4e69-b7fc06d000001576-7a-508b9d6a0a7d
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFKsWRmVeSWpSXmKPExsXCFe9nqJs1tzvA4PY/BYtdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoErY++Vy0wFi9wrHnZtYWtgbLLqYuTkkBAwkbh3fSszhC0mceHe erYuRi4OIYHtjBLnXvxlgnB+Mkq8u3SAEcKZyShxdNEHFpAWFgFViZ4TbUwgNhuQ/aj5N3sX IweHsICWxJlv6iBhTgEXiS+z9kFtUJD4c+4xWKuIgKPEmifzWUFsZoEciX83L7KCtPIKeEuc ueUJETaT2PxnE1gJr4CgxI/J91hASpgFdCS+ToqAKBGXaG69yQJha0s8eXcBrJwR6Jfvp9Yw QWzSlvj57RMbSKuIgJ/E9g/GEMcISCzZcx7qMFGJl4//sUI8+I1RYtKbBtYJjBKzkFwxC8kV sxCumIXkillIrljAyLqKUaw4qSgzPaMkNzEzJ93ASC8jUy8zL7VkEyMk4jJ3MC7fqXKIUYCD UYmH9+SnrgAh1sSy4srcQ4ySHExKorwcM7oDhPiS8lMqMxKLM+KLSnNSiw8xSnAwK4nwuqkA 5XhTEiurUovyYVIyHBxKErzr5wClBItS01Mr0jJzgGkFJs3EwQnSzgPUrg1Sw1tckJhbnJkO kT/FKCklzrsXJCEAksgozYPrfcUoDnSkMG8uSJYHmADhul4BDWQCGijG2gkysCQRISXVwLju h95OrZyEWQEuD//NEk1ISLtv/7svPv/65xML+NlUf+sXB/KpLuTplfsd6VX/eHlZgX4P25GP C0/O9AjZkfzx+B7lWUm96vNWhP37+0XD1XBirdoXWyfdMBar+ojf4i4HY6MWn51/03+V6uZV H3LX1JQkbGNV//h5hfnvt+0bF1U/FnygbKXEUpyRaKjFXFScCAC3kUccPQMAAA==
References: <007801cd9c9b$3b06d5a0$b11480e0$@unizar.es> <A3179A2C9AAEE647BE70AC4C7881D5FB0167E5BC@sluga.fer.hr> <003601cdb0f8$04f119a0$0ed34ce0$@unizar.es> <5087AE2E.3040303@unizar.es> <A3179A2C9AAEE647BE70AC4C7881D5FB0167E732@sluga.fer.hr>
Cc: "<tcmtf@ietf.org>" <tcmtf@ietf.org>, =?iso-8859-2?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
Subject: Re: [tcmtf] Next steps with 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: Sat, 27 Oct 2012 08:38:06 -0000

Hi,

Indeed, remote desktop is one of the use cases we have been discussing
internally. We can think of a couple of scenarios in addition to a
pure cloud one. Irrespectively of were the RD server is located, workers
in remote branches could benefit form TCMTF, especially when we think about
heavily distributed organizations (banks, insurance companies, government
agencies, to name a few). Another one could any off-site gathering, request=
ing
a many temporary simultaneous connection from an otherwise unusual location=
.

Be goode,

On 26 Oct 2012, at 11:17 , Mirko Su=BEnjevi=E6 wrote:
> Yes this is true,
> This was just an example of remote control services for which I found dat=
a regarding latency values in the literature.
> I think that the most used remote control real time services would be rem=
ote desktop. If a whole company accesses one server on which the virtualize=
d PCs are hosted shared network path is very long (especially if you take i=
nto consideration clouds). And remote desktop packets are quite small in te=
rms of packet size and therefore good for TCMTF.
>
> Sadly, I have not yet found any data regarding QoS or QoE for those servi=
ces, but I am sure that there exist somewhere in the literature.
>
> Cheers!
> Mirko
>
> -----Original Message-----
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of=
 Juli=E1n Fern=E1ndez-Navajas
> Sent: Wednesday, October 24, 2012 11:01 AM
> To: tcmtf@ietf.org
> Subject: Re: [tcmtf] Next steps with TCMTF
>
> hello all,
> Regarding the real-time services suitable for multiplexing, i have a ques=
tion about the third of them, remote control. I can't think a use case that=
 transmits little packets in order to be multiplexed. Mirko suggests tele-e=
chography but it no seems a use case that traffic needs multiplexion becaus=
e there are not a lot of users simultaneusly.
> Let us thinking about remote control and the possible use cases that can =
be presented here.
>
> Juli=E1n
>
>
>
>
> El 23/10/2012 10:25, Jose Saldana escribi=F3:
>> Mirko,
>>
>> This sounds really good!. This was the idea of "draft b)".
>>
>> Do you think you have included all the services which can be
>> multiplexed with TCMTF? I mean: small packets and high overhead. Some
>> ideas: sensor networks sending a sample, video-surveillance, whatsapp-li=
ke applications?
>> Although some of them are not real-time, perhaps they can also be
>> multiplexed if the number of packets per second is big.
>>
>> So perhaps a section enumerating non real-time applications with small
>> packets could also be interesting: for example "instant messaging
>> applications can tolerate up to 5 seconds of delay" (I have just
>> invented the figure, it's only an example).
>>
>> I could help you with this, if you agree, of course.
>>
>> Thanks,
>>
>> Jose
>>
>>> -----Mensaje original-----
>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>>> de Mirko Su=BEnjevic Enviado el: martes, 23 de octubre de 2012 10:14
>>> Para: tcmtf@ietf.org
>>> Asunto: Re: [tcmtf] Next steps with TCMTF
>>>
>>> Hello all,
>>>
>>> Regarding the b) "Recommendations draft" I have created a first
>>> summary of real-time services suitable for multiplexing.
>>>
>>> In short I have analyzed the literature regarding:
>>> 1) 2-way audio video communications
>>> 2) Multiplayer gaming
>>> 3) Remote control
>>>
>>> I will shortly just summarize the results without listing all sources.
>>> Note: Under term latency one way delay is considered.
>>>
>>> For 2-way audio and video communication ITU.T recommendations state
>>> that 150ms latency is needed for completely unimpaired communication.
>>> Latencies up to 400ms can be tolerated, but their impact is noticeable.
>>>
>>> Multiplayer gaming differs significantly on the genre.
>>> The most demanding games are First Person Shooter (FPS) games which
>>> require between 80ms and 100ms delay for unimpaired experience.
>>> Some studies claim that Thrid Person Avatar games from which the most
>>> common are Role Playing Games (RPGs) and Massively Multiplayer Role-
>>> Playing Games MMORPGs tolerate latencies up to 500ms, but other
>>> studies state that a more realistic values for unimpaired MMORPG
>>> experience is between 120 and 200ms.
>>> As for omnipresent games such as Real Time Strategies (RTS) it is
>>> stated
>> that
>>> latencies up to 500ms and even up to 1000ms do not impair user
>>> performance on objective metrics, but the evidence from RTS game
>>> forums suggests that users are quite unsatisfied with latencies above 3=
00ms.
>>>
>>> Remote control has different values of latency for different services
>>> as
>> well.
>>> Remote surgery is stated that 330ms latency is acceptable, but for
>> controlling
>>> a robot in scope of end-to-end tele-echography showed that only
>>> latencies under 150ms are acceptable.
>>>
>>> What do you think is there a possibility to make an extended version
>>> of
>> such
>>> a document and submit it as a draft?
>>>
>>> Thanks for any feedback!
>>>
>>> Mirko Suznjevic
>>>
>>> -----Original Message-----
>>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
>>> Behalf Of Jose Saldana
>>> Sent: Thursday, September 27, 2012 12:31 PM
>>> To: tcmtf@ietf.org
>>> Cc: Wesley Eddy; Martin Stiemerling
>>> Subject: [tcmtf] Next steps with TCMTF
>>>
>>> Hello all,
>>>
>>> I would like to discuss in this list the possibility of creating a
>>> small
>> Working
>>> Group for TCMTF, as suggested by Wes. It could have the task of
>>> making a RFC from TCMTF, or a wider scope. I think that perhaps more
>>> than a draft would be necessary. I mean, I have been thinking about
>>> it, and perhaps the work could be divided into the next parts:
>>>
>>>  a) "Current draft": the main draft (draft-saldana-tsvwg-tcmtf-03),
>> including
>>> the protocol stack of TCMTF. The current proposal has different
>>> options,
>> but
>>> the concrete one to use is static: in the set-up moment, you decide
>>> that "between these two routers a tunnel is set including all the
>>> packets with
>> this
>>> IP origin and destination".
>>>
>>> b) "Recommendations draft": another "informational" one, with
>>> recommendations of maximum delays to be added to different kinds of
>>> services, different multiplexing policies, implementation issues
>>> related
>> to the
>>> selection of the best compression algorithm to use, etc. Some
>>> hypothetical
>>> examples:
>>>       -  "if you are multiplexing a First Person Shooter, your
>>> multiplexer
>> should
>>> not retain packets more than 50 ms"
>>> - "if you are multiplexing in a low-end router in a wired scenario,
>>> you
>> don't
>>> need to use ROHC. A simpler scheme like IPHC can be enough, and it
>>> will
>> not
>>> require a lot of processing capacity".
>>>
>>> c) "Dynamic Signaling draft": perhaps another one including a
>>> signaling system in order to:
>>>     - dynamically "negotiate" the concrete options of TCMTF you are
>>> going to use
>>>     - if two routers notice that a rush hour is arriving, they could
>> send
>>> some packets asking other routers if they have some flows in common
>>> with them, which could be multiplexed.
>>>
>>>
>>> The main questions are:
>>>
>>> Is this enough for creating a working group?
>>>
>>> Do you think the distribution of the work into three draft makes sense?
>>>
>>> Is there any other issue which should be studied and standardized?
>>> Perhaps other people could imagine more things.
>>>
>>> So let's start the discussion.
>>>
>>> Thanks in advance,
>>>
>>> Jose
>>>
>>>
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>>
>>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


--
"Esta vez no fallaremos, Doctor Infierno"

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

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


________________________________

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