
From jsaldana@unizar.es  Wed Jan  9 01:29:09 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D221221F8574 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 01:29:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iyGSJScAcHYD for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 01:29:09 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 0576D21F8438 for <tcmtf@ietf.org>; Wed,  9 Jan 2013 01:29:08 -0800 (PST)
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 r099T3mP006433 for <tcmtf@ietf.org>; Wed, 9 Jan 2013 10:29:03 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
References: <20130109092515.21441.34780.idtracker@ietfa.amsl.com>
In-Reply-To: <20130109092515.21441.34780.idtracker@ietfa.amsl.com>
Date: Wed, 9 Jan 2013 10:29:08 +0100
Organization: Universidad de Zaragoza
Message-ID: <006601cdee4b$c6942d50$53bc87f0$@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: AQJSNkqco8tyZOR+9daRtbKaKT7hHZc4Krlw
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] RV: New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 09:29:10 -0000

I have just uploaded a new version of the tcmtf draft.

Jose

> -----Mensaje original-----
> De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Enviado el: mi=C3=A9rcoles, 09 de enero de 2013 10:25
> Para: jsaldana@unizar.es
> CC: mperumal@cisco.com; navajas@unizar.es; dwing@cisco.com; fpb@tid.es
> Asunto: New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
>=20
>=20
> A new version of I-D, draft-saldana-tsvwg-tcmtf-04.txt has been =
successfully
> submitted by Jose Saldana and posted to the IETF repository.
>=20
> Filename:	 draft-saldana-tsvwg-tcmtf
> Revision:	 04
> Title:		 Tunneling Compressed Multiplexed Traffic Flows (TCMTF)
> Creation date:	 2013-01-09
> WG ID:		 Individual Submission
> Number of pages: 19
> URL:             =
http://www.ietf.org/internet-drafts/draft-saldana-tsvwg-tcmtf-
> 04.txt
> Status:          =
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf
> Htmlized:        =
http://tools.ietf.org/html/draft-saldana-tsvwg-tcmtf-04
> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-saldana-tsvwg-tcmtf-04
>=20
> Abstract:
>    This document describes a method to improve the bandwidth =
utilization
>    of network paths that carry multiple streams in parallel sharing a
>    common path.  The method combines standard protocols that provide
>    compression, multiplexing, and tunneling over a network path for =
the
>    purpose of reducing the bandwidth used when multiple streams are
>    carried over that path.
>=20
>=20
>=20
>=20
> The IETF Secretariat



From jsaldana@unizar.es  Wed Jan  9 01:46:54 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A89F21F842E for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 01:46:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, 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 vdML14syQVF8 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 01:46:51 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id D36C921F8526 for <tcmtf@ietf.org>; Wed,  9 Jan 2013 01:46:50 -0800 (PST)
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 r099khFo022705; Wed, 9 Jan 2013 10:46:43 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 9 Jan 2013 10:46:48 +0100
Organization: Universidad de Zaragoza
Message-ID: <006701cdee4e$3ecaf2c0$bc60d840$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0068_01CDEE56.A091A4B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3uRDTQiMDFtmLvSzeI1OoMKlMgFw==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Wesley Eddy <wes@mti-systems.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [tcmtf] Charter proposal for a possible Working Group about 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, 09 Jan 2013 09:46:54 -0000

This is a multipart message in MIME format.

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

Hi all,

 

Since we are considering the possibility of creating a WG for TCMTF, I have
written this Charter. It is only a first version to discuss. In other
messages I will suggest some related questions. So your opinion will now be
really valuable.

 

Document (A) refers to
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

Document (B) refers to
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/

 

Thanks,

 

Jose

 

 

*Description of Working Group*

 

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 sending collected data in sensor networks).

 

2. In order to mitigate this bad network efficiency, when a number of flows
share 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. If two mux/demux want to establish a tunnel, they have first to use a
mechanism to negotiate which concrete option would they use in each layer:
header compression, multiplexing and tunneling. This will depend on the
implementations they include, and in the scenario.

 

6. 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.

 

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).

 

 

*Goals and Milestones*

 

Specification of TCMTF protocol stack (A)

 

Recommendations of maximum delay depending on the service (B)


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi =
all,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>Since we are considering the =
possibility of creating a WG for TCMTF, I have written this Charter. It =
is only a first version to discuss. In other messages I will suggest =
some related questions. So your opinion will now be really =
valuable.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Document (A) refers to <a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http:=
//datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></spa=
n></p><p class=3DMsoNormal><span lang=3DEN-US>Document (B) refers to <a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a><o:p=
></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jose<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>*Description of Working Group*<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>1. 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 sending collected data in sensor =
networks).<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>2. In order to mitigate this bad network efficiency, when a =
number of flows share a path, packets can be grouped, considering three =
different layers:<o:p></o:p></span></p><p class=3DMsoNormal><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=3DMsoNormal><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=3DMsoNormal><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=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><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=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><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=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>5. If two mux/demux want to establish a tunnel, they have =
first to use a mechanism to negotiate which concrete option would they =
use in each layer: header compression, multiplexing and tunneling. This =
will depend on the implementations they include, and in the =
scenario.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>6. 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=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><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=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><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=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>*<b>Goals and Milestones</b>*<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Specification of TCMTF protocol =
stack (A)<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Recommendations of maximum delay depending on the service =
(B)<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_0068_01CDEE56.A091A4B0--


From jsaldana@unizar.es  Wed Jan  9 01:47:58 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A099B21F8556 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 01:47:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z9ChNQcyQFco for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 01:47:58 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id A01DE21F852C for <tcmtf@ietf.org>; Wed,  9 Jan 2013 01:47:57 -0800 (PST)
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 r099khFq022705 for <tcmtf@ietf.org>; Wed, 9 Jan 2013 10:47:43 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 9 Jan 2013 10:47:47 +0100
Organization: Universidad de Zaragoza
Message-ID: <007201cdee4e$61e4d960$25ae8c20$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0073_01CDEE56.C3A94160"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3uTJFFLbx+z32QTGuvtXZ79XI24Q==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
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, 09 Jan 2013 09:47:58 -0000

This is a multipart message in MIME format.

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

One question is if we should consider the creation of a specific draft about
signaling issues. In paragraph 5, I have written the idea, but I don't
currently know if it is necessary at this stage: "a mechanism to negotiate
which concrete option would they use in each layer".

 

My opinion: We could first focus on drafts (A) and (B), and later re-charter
the WG if necessary in order to consider this other document.

 

What do you think?

 

Jose 

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>One question is if we should consider the creation of a =
specific draft about signaling issues. In paragraph 5, I have written =
the idea, but I don&#8217;t currently know if it is necessary at this =
stage: &#8220;a mechanism to negotiate which concrete option would they =
use in each layer&#8221;.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>My opinion: We could first focus on =
drafts (A) and (B), and later re-charter the WG if necessary in order to =
consider this other document.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>What do you =
think?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'>Jose <o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_0073_01CDEE56.C3A94160--


From jsaldana@unizar.es  Wed Jan  9 01:48:27 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8530721F8556 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 01:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qr9wa8tkt47f for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 01:48:27 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id C9EB121F852C for <tcmtf@ietf.org>; Wed,  9 Jan 2013 01:48:26 -0800 (PST)
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 r099khFu022705; Wed, 9 Jan 2013 10:48:15 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 9 Jan 2013 10:47:47 +0100
Organization: Universidad de Zaragoza
Message-ID: <008101cdee4e$7881e190$6985a4b0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0082_01CDEE56.DA464990"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3uTZdwrJXW2tf+Tx+3CKyrnihymQ==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Luigi Iannone <ggx@gigix.net>, "'Joel M. Halpern'" <jmh@joelhalpern.com>
Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 3
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, 09 Jan 2013 09:48:27 -0000

This is a multipart message in MIME format.

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

Another question: Luigi proposed the possibility of including LISP as
another possibility in the Tunneling layer
(http://www.ietf.org/mail-archive/web/tcmtf/current/msg00073.html).

 

Should this be also somewhat included in the Charter?

 

Thanks,

 

Jose 

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>Another question: Luigi proposed the possibility of =
including LISP as another possibility in the Tunneling layer (<a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00073.html"=
>http://www.ietf.org/mail-archive/web/tcmtf/current/msg00073.html</a>).<o=
:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Should this be also somewhat included in the =
Charter?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'>Jose <o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_0082_01CDEE56.DA464990--


From jsaldana@unizar.es  Wed Jan  9 01:48:34 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F40721F8556 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 01:48:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AfqDgnQzX3Dw for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 01:48:34 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id DF3A521F857A for <tcmtf@ietf.org>; Wed,  9 Jan 2013 01:48:33 -0800 (PST)
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 r099khFv022705; Wed, 9 Jan 2013 10:48:27 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 9 Jan 2013 10:48:32 +0100
Organization: Universidad de Zaragoza
Message-ID: <008601cdee4e$7c69a310$753ce930$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0087_01CDEE56.DE2E0B10"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3uTNeTbO+aCk7ITXS7wkpgZ6Gw0g==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Tomaso.deCola@dlr.de, Matteo.Berioli@dlr.de, Fernando Pascual Blanco <fpb@tid.es>
Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2
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, 09 Jan 2013 09:48:34 -0000

This is a multipart message in MIME format.

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

There is another question: Tomaso, from DLR, proposed another draft for a
specific satellite scenario
(http://www.ietf.org/mail-archive/web/tcmtf/current/msg00095.html). Should
we include this in the charter?

 

My opinion is that, at this stage, we could begin the WG without considering
this, and at the same time a draft could be written and discussed. According
to the ideas and feedback after that, including it in a new version of the
Charter could be considered.

 

Jose 

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>There is another question: Tomaso, from DLR, proposed =
another draft for a specific satellite scenario (<a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00095.html"=
>http://www.ietf.org/mail-archive/web/tcmtf/current/msg00095.html</a>). =
Should we include this in the charter?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>My opinion is that, at this stage, =
we could begin the WG without considering this, and at the same time a =
draft could be written and discussed. According to the ideas and =
feedback after that, including it in a new version of the Charter could =
be considered.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'>Jose <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_0087_01CDEE56.DE2E0B10--


From Mirko.Suznjevic@fer.hr  Wed Jan  9 02:21:34 2013
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 A4CCF21F8644 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 02:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 xVOaCHvO5cor for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 02:21:34 -0800 (PST)
Received: from mail.zvne.fer.hr (mail.zvne.fer.hr [161.53.66.5]) by ietfa.amsl.com (Postfix) with ESMTP id 99FF121F8630 for <tcmtf@ietf.org>; Wed,  9 Jan 2013 02:21:33 -0800 (PST)
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.318.4; Wed, 9 Jan 2013 11:21:31 +0100
Received: from sluga.fer.hr ([161.53.66.244]) by munja.zvne.fer.hr with Microsoft SMTPSVC(6.0.3790.4675);	 Wed, 9 Jan 2013 11:21:19 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CDEE53.106B205B"
Date: Wed, 9 Jan 2013 11:21:16 +0100
Message-ID: <A3179A2C9AAEE647BE70AC4C7881D5FB01775E6A@sluga.fer.hr>
In-Reply-To: <008601cdee4e$7c69a310$753ce930$@unizar.es>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2
Thread-Index: Ac3uTNeTbO+aCk7ITXS7wkpgZ6Gw0gABangw
References: <008601cdee4e$7c69a310$753ce930$@unizar.es>
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: <jsaldana@unizar.es>, <tcmtf@ietf.org>
X-OriginalArrivalTime: 09 Jan 2013 10:21:19.0123 (UTC) FILETIME=[1090BE30:01CDEE53]
Cc: Tomaso.deCola@dlr.de, Matteo.Berioli@dlr.de, Fernando Pascual Blanco <fpb@tid.es>
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2
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, 09 Jan 2013 10:21:34 -0000

------_=_NextPart_001_01CDEE53.106B205B
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

Well the satelite scenario is very interesting application of TCMTF, but =
I think that at this point we should focus our efforts on the current =
documents. Once we have the draft of the satellite scenario written and =
discussed we can include it in the new version of the Charter.=20

I think that the same applies to your first question regarding the =
specific draft about signaling issues. I think that the WG can be =
re-chartered later on.

=20

Mirko Suznjevic

=20

From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =
Of Jose Saldana
Sent: Wednesday, January 9, 2013 10:49 AM
To: tcmtf@ietf.org
Cc: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de; Fernando Pascual Blanco
Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2

=20

There is another question: Tomaso, from DLR, proposed another draft for =
a specific satellite scenario =
(http://www.ietf.org/mail-archive/web/tcmtf/current/msg00095.html). =
Should we include this in the charter?

=20

My opinion is that, at this stage, we could begin the WG without =
considering this, and at the same time a draft could be written and =
discussed. According to the ideas and feedback after that, including it =
in a new version of the Charter could be considered.

=20

Jose=20

=20


------_=_NextPart_001_01CDEE53.106B205B
Content-Type: text/html; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-2">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{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=3DHR link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Well the satelite scenario is very =
interesting application of TCMTF, but I think that at this point we =
should focus our efforts on the current documents. Once we have the =
draft of the satellite scenario written and discussed we can include it =
in the new version of the Charter. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>I think =
that the same applies to your first question regarding the specific =
draft about signaling issues. I think that the WG can be re-chartered =
later on.<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'>Mirko =
Suznjevic<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] <b>On Behalf Of =
</b>Jose Saldana<br><b>Sent:</b> Wednesday, January 9, 2013 10:49 =
AM<br><b>To:</b> tcmtf@ietf.org<br><b>Cc:</b> Tomaso.deCola@dlr.de; =
Matteo.Berioli@dlr.de; Fernando Pascual Blanco<br><b>Subject:</b> =
[tcmtf] Questions regarding the TCMTF WG Chart proposal. =
2<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>There is another question: Tomaso, from DLR, proposed =
another draft for a specific satellite scenario (<a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00095.html"=
>http://www.ietf.org/mail-archive/web/tcmtf/current/msg00095.html</a>). =
Should we include this in the charter?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>My opinion is that, at this stage, =
we could begin the WG without considering this, and at the same time a =
draft could be written and discussed. According to the ideas and =
feedback after that, including it in a new version of the Charter could =
be considered.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Jose =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------_=_NextPart_001_01CDEE53.106B205B--

From ggx@gigix.net  Wed Jan  9 03:44:40 2013
Return-Path: <ggx@gigix.net>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36F3921F86C1 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 03:44:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.832
X-Spam-Level: 
X-Spam-Status: No, score=-2.832 tagged_above=-999 required=5 tests=[AWL=0.416,  BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 VI-Cai+qhJju for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 03:44:39 -0800 (PST)
Received: from mail-we0-f177.google.com (mail-we0-f177.google.com [74.125.82.177]) by ietfa.amsl.com (Postfix) with ESMTP id CBB2921F869A for <tcmtf@ietf.org>; Wed,  9 Jan 2013 03:44:38 -0800 (PST)
Received: by mail-we0-f177.google.com with SMTP id x48so1008671wey.22 for <tcmtf@ietf.org>; Wed, 09 Jan 2013 03:44:37 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:message-id:references:to:x-mailer:x-gm-message-state; bh=o69ceU4eQwBLbJYRaI0OPzW/r+Ony2B7qqUo3leqJag=; b=YdcwGoUeru+MonanMD8t6TcYxOgZ40b7ZptYlzi5gxZ1E9ItGHorPND7Nf+ZMDa4eO 9BAQ+WqvMX+SgsqyLtt9AN6pojImv/7AEdIVMCorZnnleeCZul3pCqjVcNfc0sb/miwv BJDeBIbRi/4KtnHfHGiD63YDTYju49EyDgw1Jcw9hQdTdfO0RPHzTQdBxD11XvXf7xkb 2NtPi0zi+QOsLL5nXz4ynnaB5wLeZjSNlznSRVRDouzSmjkYxZ103FyQ6byb0RiiA8m4 sbVNLcbEEBPWKLp72JHCsaKYucfrlO89dGiR3rL5HYq3Jwsg+N36tFi33em1CKaR4iGB YSqg==
X-Received: by 10.180.77.35 with SMTP id p3mr2765170wiw.18.1357731877737; Wed, 09 Jan 2013 03:44:37 -0800 (PST)
Received: from dhcp164-04.enst.fr (dhcp164-04.enst.fr. [137.194.165.4]) by mx.google.com with ESMTPS id dm3sm3525220wib.9.2013.01.09.03.44.36 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Jan 2013 03:44:36 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_F62F26A8-6B0B-4CF6-AC9A-7BBFBE1AD4A5"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <008101cdee4e$7881e190$6985a4b0$@unizar.es>
Date: Wed, 9 Jan 2013 12:44:39 +0100
Message-Id: <3FE9B877-78C2-4C0C-B8CB-2C75A84CEBC2@gigix.net>
References: <008101cdee4e$7881e190$6985a4b0$@unizar.es>
To: <jsaldana@unizar.es>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQk3VLVgACSaZbiPV9SQi54tjI4/ldc43B97UZSv+2qL5CoxvP8SP0Z+kgg+1MMhyQQp2xQf
Cc: tcmtf@ietf.org, "'Joel M. Halpern'" <jmh@joelhalpern.com>
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 3
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, 09 Jan 2013 11:44:40 -0000

--Apple-Mail=_F62F26A8-6B0B-4CF6-AC9A-7BBFBE1AD4A5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

obviously I am in favour of this ;-)
I think there are benefits is such solution.

Yet, if the WG is interested in this may be a different kind of document =
should be added to the charter.=20

Point 3 of the charter refers to "only standard protocols are being =
used" and aims at a "best current practice" document.=20
LISP is still considered "experimental", hence, I am not sure it can be =
included in a BCP document.=20

ciao

Luigi

On 9 Jan. 2013, at 10:47 , Jose Saldana <jsaldana@unizar.es> wrote:

> Another question: Luigi proposed the possibility of including LISP as =
another possibility in the Tunneling layer =
(http://www.ietf.org/mail-archive/web/tcmtf/current/msg00073.html).
> =20
> Should this be also somewhat included in the Charter?
> =20
> Thanks,
> =20
> Jose
> =20


--Apple-Mail=_F62F26A8-6B0B-4CF6-AC9A-7BBFBE1AD4A5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"><base href=3D"x-msg://6912/"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
">Hi,<div><br></div><div>obviously I am in favour of this =
;-)</div><div>I think there are benefits is such =
solution.</div><div><br></div><div>Yet, if the WG is interested in this =
may be a different kind of document should be added to the =
charter.&nbsp;</div><div><br></div><div>Point 3 of the charter refers to =
"only standard protocols are being used" and aims at a "best current =
practice" document.&nbsp;</div><div>LISP is still considered =
"experimental", hence, I am not sure it can be included in a BCP =
document.&nbsp;</div><div><br></div><div>ciao</div><div><br></div><div>Lui=
gi</div><div><br><div><div>On 9 Jan. 2013, at 10:47 , 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">Another question: Luigi =
proposed the possibility of including LISP as another possibility in the =
Tunneling layer (<a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00073.html" =
style=3D"color: purple; text-decoration: underline; =
">http://www.ietf.org/mail-archive/web/tcmtf/current/msg00073.html</a>).<o=
:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">Should this be also somewhat included in the =
Charter?<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">Thanks,<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial, sans-serif; =
">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">&nbsp;</span></div></div></div></blockquote></div><br></div=
></body></html>=

--Apple-Mail=_F62F26A8-6B0B-4CF6-AC9A-7BBFBE1AD4A5--

From dwing@cisco.com  Wed Jan  9 07:37:41 2013
Return-Path: <dwing@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66A1121F8831 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 07:37:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 C++BRtY+yz8s for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 07:37:40 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id C770621F8830 for <tcmtf@ietf.org>; Wed,  9 Jan 2013 07:37:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1036; q=dns/txt; s=iport; t=1357745860; x=1358955460; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=fPIrfEd36gQS3EgWxcGx9ZVsdMeF4rK9bkRvy83SCTA=; b=UN1GhuKHVpj1JCij0duVt9twZUKD9whRPrAsFatpXGq5aNMVV7s3/o58 YZPhxDHkk/NBY9zkm9ut8s39vFtTrdkfqAuy1hHJPl4q3m4PA1gt1szJz 1FVMGQBmfbI6eO/0jFnyaqhufklM6riuYqavKkx4z7b8EILaXGD22mZPN M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlsIAP2N7VCrRDoJ/2dsb2JhbABEg0e6CxZzgh4BAQEDAQgCMDoKBwEDAgkRBAEBKAcZLQkIAgQBEgsFiAEFthyREAOIYYUdhFuDM5BJgxU
X-IronPort-AV: E=Sophos;i="4.84,438,1355097600"; d="scan'208";a="68351808"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 09 Jan 2013 15:37:40 +0000
Received: from DWINGWS01 ([10.32.240.196]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r09FbegF001296; Wed, 9 Jan 2013 15:37:40 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <jsaldana@unizar.es>, <tcmtf@ietf.org>
References: <007201cdee4e$61e4d960$25ae8c20$@unizar.es>
In-Reply-To: <007201cdee4e$61e4d960$25ae8c20$@unizar.es>
Date: Wed, 9 Jan 2013 07:37:40 -0800
Message-ID: <0b5901cdee7f$425a64d0$c70f2e70$@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDH7LepDP3BMXzcqEq1eyAG5/2DDJpNJL2A
Content-Language: en-us
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
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, 09 Jan 2013 15:37:41 -0000

> -----Original Message-----
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
> Of Jose Saldana
> Sent: Wednesday, January 09, 2013 1:48 AM
> To: tcmtf@ietf.org
> Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
> 
> One question is if we should consider the creation of a specific draft
> about signaling issues.

So, this is a 'problem statement', describing the problem we're trying
to solve (e.g., the application's tolerance for TCMTF-induced jitter)?  
Or, this is a document analyzing how we signal TCMTF capabilities to the 
other end?


> In paragraph 5, I have written the idea, but I
> don't currently know if it is necessary at this stage: "a mechanism to
> negotiate which concrete option would they use in each layer".
> 
> 
> 
> My opinion: We could first focus on drafts (A) and (B), and later re-
> charter the WG if necessary in order to consider this other document.

Agreed.

-d


> 
> 
> 
> What do you think?
> 
> 
> 
> Jose
> 
> 



From jsaldana@unizar.es  Wed Jan  9 08:07:40 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4820C21F86C1 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 08:07:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MkGI5Wu+3Ybe for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 08:07:39 -0800 (PST)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7B1AC21F866D for <tcmtf@ietf.org>; Wed,  9 Jan 2013 08:07:39 -0800 (PST)
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 r09G7Wn4020141; Wed, 9 Jan 2013 17:07:32 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Dan Wing'" <dwing@cisco.com>, <tcmtf@ietf.org>
References: <007201cdee4e$61e4d960$25ae8c20$@unizar.es> <0b5901cdee7f$425a64d0$c70f2e70$@cisco.com>
In-Reply-To: <0b5901cdee7f$425a64d0$c70f2e70$@cisco.com>
Date: Wed, 9 Jan 2013 17:07:36 +0100
Organization: Universidad de Zaragoza
Message-ID: <00fa01cdee83$70e73720$52b5a560$@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: AQDH7LepDP3BMXzcqEq1eyAG5/2DDAJ+smNjmjk2epA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
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, 09 Jan 2013 16:07:40 -0000

Dan,

The question is if we should include in the charter this objective: =
writing
a document about two things which have somewhat appeared during the
discussion:

- Negotiation mechanisms to decide the options at each layer =
(compression,
multiplexing and tunneling) between mux and demux. Perhaps the mux has =
ROHC,
ECRTP and IPHC, and the demux only has ECRTP and IPHC, so the two =
machines
will have to negotiate in order to decide which compression protocol =
use.

- dynamically establishing, modifying and releasing tunnels

Best regards,

Jose

> -----Mensaje original-----
> De: Dan Wing [mailto:dwing@cisco.com]
> Enviado el: mi=E9rcoles, 09 de enero de 2013 16:38
> Para: jsaldana@unizar.es; tcmtf@ietf.org
> Asunto: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
>=20
> > -----Original Message-----
> > From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On =
Behalf
> > Of Jose Saldana
> > Sent: Wednesday, January 09, 2013 1:48 AM
> > To: tcmtf@ietf.org
> > Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
> >
> > One question is if we should consider the creation of a specific =
draft
> > about signaling issues.
>=20
> So, this is a 'problem statement', describing the problem we're trying =
to
solve
> (e.g., the application's tolerance for TCMTF-induced jitter)?
> Or, this is a document analyzing how we signal TCMTF capabilities to =
the
> other end?
>=20
>=20
> > In paragraph 5, I have written the idea, but I
> > don't currently know if it is necessary at this stage: "a mechanism =
to
> > negotiate which concrete option would they use in each layer".
> >
> >
> >
> > My opinion: We could first focus on drafts (A) and (B), and later =
re-
> > charter the WG if necessary in order to consider this other =
document.
>=20
> Agreed.
>=20
> -d
>=20
>=20
> >
> >
> >
> > What do you think?
> >
> >
> >
> > Jose
> >
> >



From dwing@cisco.com  Wed Jan  9 08:23:43 2013
Return-Path: <dwing@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4749C21F87E7 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 08:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 i0COGh3-T-bJ for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 08:23:42 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id A448E21F84BB for <tcmtf@ietf.org>; Wed,  9 Jan 2013 08:23:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2688; q=dns/txt; s=iport; t=1357748622; x=1358958222; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=CMvXisKNH4M3uxeGR3/werh/vURu4BCZc4GolibG70Q=; b=NvF9gEziQOiURD7URb032Fd4SV1jlqllg9W18AxcbetglL2L3PajOvh0 CAB4zLGi60BAjp4zLcKrUGi/LrV1lRlmP0BC4mJWpmJpw3YTG9QbfzwKD xLo40jdUzHoo19sRsfAjLOJ4v3uW1l+qLZtOx8cMi+plDjZSG8c6LbILY 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwIANuY7VCrRDoH/2dsb2JhbABEg0e6ExZzgh4BAQEDAQgCagoHAQMCCREEAQEoBxktCQgCBAESCwWIAwW2JJEaA4gtNYUchFuDM5BJgxU
X-IronPort-AV: E=Sophos;i="4.84,438,1355097600"; d="scan'208";a="65778002"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 09 Jan 2013 16:23:42 +0000
Received: from DWINGWS01 ([10.32.240.196]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r09GNgqY018231; Wed, 9 Jan 2013 16:23:42 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <jsaldana@unizar.es>, <tcmtf@ietf.org>
References: <007201cdee4e$61e4d960$25ae8c20$@unizar.es> <0b5901cdee7f$425a64d0$c70f2e70$@cisco.com> <00fa01cdee83$70e73720$52b5a560$@unizar.es>
In-Reply-To: <00fa01cdee83$70e73720$52b5a560$@unizar.es>
Date: Wed, 9 Jan 2013 08:23:42 -0800
Message-ID: <0b9701cdee85$b09358c0$11ba0a40$@cisco.com>
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: AQDH7LepDP3BMXzcqEq1eyAG5/2DDAJ+smNjAc3crh+aKsursA==
Content-Language: en-us
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
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, 09 Jan 2013 16:23:43 -0000

> -----Original Message-----
> From: Jose Saldana [mailto:jsaldana@unizar.es]
> Sent: Wednesday, January 09, 2013 8:08 AM
> To: 'Dan Wing'; tcmtf@ietf.org
> Subject: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal. =
1
>=20
> Dan,
>=20
> The question is if we should include in the charter this objective:
> writing a document about two things which have somewhat appeared =
during
> the
> discussion:
>=20
> - Negotiation mechanisms to decide the options at each layer
> (compression, multiplexing and tunneling) between mux and demux. =
Perhaps
> the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP and =
IPHC,
> so the two machines will have to negotiate in order to decide which
> compression protocol use.

We need that -- it is capabilities negotiation.  It is needed because
the protocol will fail if one side mistakenly thinks the other side
has certain functionality, and because we will want to add some fancy
new compression in the year 2020 and will need to negotiate it.

I don't think it needs to be a separate milestone or a separate=20
document, though.

> - dynamically establishing, modifying and releasing tunnels

-d

> Best regards,
>=20
> Jose
>=20
> > -----Mensaje original-----
> > De: Dan Wing [mailto:dwing@cisco.com]
> > Enviado el: mi=E9rcoles, 09 de enero de 2013 16:38
> > Para: jsaldana@unizar.es; tcmtf@ietf.org
> > Asunto: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal. =
1
> >
> > > -----Original Message-----
> > > From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
> > > Behalf Of Jose Saldana
> > > Sent: Wednesday, January 09, 2013 1:48 AM
> > > To: tcmtf@ietf.org
> > > Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal. =
1
> > >
> > > One question is if we should consider the creation of a specific
> > > draft about signaling issues.
> >
> > So, this is a 'problem statement', describing the problem we're =
trying
> > to
> solve
> > (e.g., the application's tolerance for TCMTF-induced jitter)?
> > Or, this is a document analyzing how we signal TCMTF capabilities to
> > the other end?
> >
> >
> > > In paragraph 5, I have written the idea, but I don't currently =
know
> > > if it is necessary at this stage: "a mechanism to negotiate which
> > > concrete option would they use in each layer".
> > >
> > >
> > >
> > > My opinion: We could first focus on drafts (A) and (B), and later
> > > re- charter the WG if necessary in order to consider this other
> document.
> >
> > Agreed.
> >
> > -d
> >
> >
> > >
> > >
> > >
> > > What do you think?
> > >
> > >
> > >
> > > Jose
> > >
> > >



From mramalho@cisco.com  Wed Jan  9 09:05:20 2013
Return-Path: <mramalho@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B973421F85FC for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 09:05:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BEO9dVnQGO95 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 09:05:20 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id EFDD421F85BC for <tcmtf@ietf.org>; Wed,  9 Jan 2013 09:05:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4066; q=dns/txt; s=iport; t=1357751120; x=1358960720; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=BVODZQ53CJwtP4L/EV2KEfcECNZwxdOHC1W5tRXjk5w=; b=iz2H/uaCAlELIkOsrp0JvTCj43GbGRgAxpaEuqte0AwWuSlIwBRwpiPo yfsekVmEtcjGBF9Svz2xx6X1mghEd+paIk0GMi6+GD8ZhdscbFr+XfJ+u q4LrvDBm/4rnU1WOH7g20BwJodWn3BaUS5QpgTxIRZF8CoYHuOYCJeoBG 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFANii7VCtJV2Z/2dsb2JhbAA6CoNsgk22L3IWc4IeAQEBBAEBASARMwcJDgYBCBEEAQEDAgYdAwIEJQsUAQgJAQQBEggBiBAHBaZLj0+BIotGgx8yYQOXKI8tgnSCJA
X-IronPort-AV: E=Sophos;i="4.84,439,1355097600"; d="scan'208";a="157577794"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 09 Jan 2013 17:05:19 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r09H5JAh012968 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 9 Jan 2013 17:05:19 GMT
Received: from xmb-rcd-x12.cisco.com ([169.254.2.163]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.02.0318.004; Wed, 9 Jan 2013 11:05:19 -0600
From: "Michael Ramalho (mramalho)" <mramalho@cisco.com>
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
Thread-Index: Ac3ui7/19m7iJp6vTHSMflxr4Puotg==
Date: Wed, 9 Jan 2013 17:05:18 +0000
Message-ID: <D21571530BF9644D9A443D6BD95B9103154BC379@xmb-rcd-x12.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.168.118]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 17:05:20 -0000

Sm9zZSwgZXQuIGFsLiwNCg0KU29ycnkgZm9yIGJlaW5nIHNvIHF1aWV0IHJlY2VudGx5IG9uIHRo
aXMgbGlzdCAuLi4gSSBhbSBqdXN0IGJlZ2lubmluZyB0byBiZWNvbWUgdW5idXJpZWQgZnJvbSB3
b3JrIGxhdGUgbGFzdCB5ZWFyIQ0KDQpZb3UgbWVudGlvbiBGUFMgYW5kIE1NT1JQR3MgaW4gdGhl
IGRyYWZ0IC4uLiBidXQgaGFzIGFueSBkZXRhaWxlZCB0aG91Z2h0IGFib3V0IGhvdyBUQ01URiBt
aWdodCBpZGVudGlmeSB3aGljaCBmbG93cyBpdCBzaG91bGQgTk9UIGF0dGVtcHQgdG8gY29tcHJl
c3M/DQoNCkNvbnNpZGVyaW5nICJ0aGUgSW50ZXJuZXQgb2YgdGhpbmdzIiAod2hlcmUgdmlydHVh
bGx5IGV2ZXJ5IGRldmljZSBpcyBjb25uZWN0ZWQgdmlhIElQKSAuLi4gd2UgY2FuIGV4cGVjdCBh
IGxvdCBvZiBzbWFsbCBwYWNrZXRzIC4uLiBidXQgbm90IG5lY2Vzc2FyaWx5IGtub3cgaWYgd2Ug
c2hvdWxkIGNvbXByZXNzIHRoZW0gb3Igbm90IChlLmcuLCBGUFMgcGFja2V0cykgLi4uIG9yIHdo
YXQgdGhlIGRlbGF5IGJvdW5kcyBvbiB0aGUgY29tcHJlc3Npb24gc2hvdWxkIGJlLg0KDQpTaG91
bGQgd2UgbWVudGlvbiB0aGF0IGZsb3dzIHRoYXQgc2lnbmFsIHRoZWlyIG93biB0cmFmZmljIGNs
YXNzIChlLmcuLCB1c2luZyAiTWV0YWRhdGEiIGRlc2NyaWJpbmcgdGhlIGZsb3cpIGlzIGEgZ29v
ZCB0aGluZyB0byBkaWZmZXJlbnRpYXRlIG9uPyBTaG91bGQgd2Ugc3VnZ2VzdCBzaWduYXR1cmUg
YW5hbHlzaXMgKGEgcHJvYmFiaWxpc3RpYyBndWVzcyBmb3IgdGhlIGFwcGxpY2F0aW9uIGJhc2Vk
IG9uIGl0cyB0aW1lLWRvbWFpbiBzaWduYXR1cmUgY2hhcmFjdGVyaXN0aWNzKSBtaWdodCBhbHNv
IGJlIG9mIHV0aWxpdHk/DQoNCkJlaW5nIHNpbGVudCBvbiB0aGlzIHBvaW50IG1heSBsZXNzZW4g
dGhlIGF0dHJhY3RpdmVuZXNzIHRvIGRlc2lnbiB1c2luZyBpdC4NCg0KU29ycnkgaWYgdGhpcyBw
b2ludCBoYXMgYmVlbiByYWlzZWQgYmVmb3JlLg0KDQpCZXN0LA0KDQpNaWNoYWVsIFJhbWFsaG8N
Cg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IHRjbXRmLWJvdW5jZXNAaWV0Zi5v
cmcgW21haWx0bzp0Y210Zi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgSm9zZSBTYWxk
YW5hDQpTZW50OiBXZWRuZXNkYXksIEphbnVhcnkgMDksIDIwMTMgNDoyOSBBTQ0KVG86IHRjbXRm
QGlldGYub3JnDQpTdWJqZWN0OiBbdGNtdGZdIFJWOiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24g
Zm9yIGRyYWZ0LXNhbGRhbmEtdHN2d2ctdGNtdGYtMDQudHh0DQoNCkkgaGF2ZSBqdXN0IHVwbG9h
ZGVkIGEgbmV3IHZlcnNpb24gb2YgdGhlIHRjbXRmIGRyYWZ0Lg0KDQpKb3NlDQoNCj4gLS0tLS1N
ZW5zYWplIG9yaWdpbmFsLS0tLS0NCj4gRGU6IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFp
bHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10gRW52aWFkbyANCj4gZWw6IG1pw6lyY29sZXMs
IDA5IGRlIGVuZXJvIGRlIDIwMTMgMTA6MjUNCj4gUGFyYToganNhbGRhbmFAdW5pemFyLmVzDQo+
IENDOiBtcGVydW1hbEBjaXNjby5jb207IG5hdmFqYXNAdW5pemFyLmVzOyBkd2luZ0BjaXNjby5j
b207IGZwYkB0aWQuZXMNCj4gQXN1bnRvOiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRy
YWZ0LXNhbGRhbmEtdHN2d2ctdGNtdGYtMDQudHh0DQo+IA0KPiANCj4gQSBuZXcgdmVyc2lvbiBv
ZiBJLUQsIGRyYWZ0LXNhbGRhbmEtdHN2d2ctdGNtdGYtMDQudHh0IGhhcyBiZWVuIA0KPiBzdWNj
ZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEpvc2UgU2FsZGFuYSBhbmQgcG9zdGVkIHRvIHRoZSBJRVRG
IHJlcG9zaXRvcnkuDQo+IA0KPiBGaWxlbmFtZToJIGRyYWZ0LXNhbGRhbmEtdHN2d2ctdGNtdGYN
Cj4gUmV2aXNpb246CSAwNA0KPiBUaXRsZToJCSBUdW5uZWxpbmcgQ29tcHJlc3NlZCBNdWx0aXBs
ZXhlZCBUcmFmZmljIEZsb3dzIChUQ01URikNCj4gQ3JlYXRpb24gZGF0ZToJIDIwMTMtMDEtMDkN
Cj4gV0cgSUQ6CQkgSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQo+IE51bWJlciBvZiBwYWdlczogMTkN
Cj4gVVJMOiAgICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9k
cmFmdC1zYWxkYW5hLXRzdndnLXRjbXRmLQ0KPiAwNC50eHQNCj4gU3RhdHVzOiAgICAgICAgICBo
dHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXNhbGRhbmEtdHN2d2ctdGNtdGYN
Cj4gSHRtbGl6ZWQ6ICAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1zYWxk
YW5hLXRzdndnLXRjbXRmLTA0DQo+IERpZmY6ICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9y
Zy9yZmNkaWZmP3VybDI9ZHJhZnQtc2FsZGFuYS10c3Z3Zy10Y210Zi0wNA0KPiANCj4gQWJzdHJh
Y3Q6DQo+ICAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGEgbWV0aG9kIHRvIGltcHJvdmUgdGhl
IGJhbmR3aWR0aCB1dGlsaXphdGlvbg0KPiAgICBvZiBuZXR3b3JrIHBhdGhzIHRoYXQgY2Fycnkg
bXVsdGlwbGUgc3RyZWFtcyBpbiBwYXJhbGxlbCBzaGFyaW5nIGENCj4gICAgY29tbW9uIHBhdGgu
ICBUaGUgbWV0aG9kIGNvbWJpbmVzIHN0YW5kYXJkIHByb3RvY29scyB0aGF0IHByb3ZpZGUNCj4g
ICAgY29tcHJlc3Npb24sIG11bHRpcGxleGluZywgYW5kIHR1bm5lbGluZyBvdmVyIGEgbmV0d29y
ayBwYXRoIGZvciB0aGUNCj4gICAgcHVycG9zZSBvZiByZWR1Y2luZyB0aGUgYmFuZHdpZHRoIHVz
ZWQgd2hlbiBtdWx0aXBsZSBzdHJlYW1zIGFyZQ0KPiAgICBjYXJyaWVkIG92ZXIgdGhhdCBwYXRo
Lg0KPiANCj4gDQo+IA0KPiANCj4gVGhlIElFVEYgU2VjcmV0YXJpYXQNCg0KDQpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KdGNtdGYgbWFpbGluZyBsaXN0
DQp0Y210ZkBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90
Y210Zg0K

From jacl@tid.es  Wed Jan  9 13:16:17 2013
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 B71FD21F86F7 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 13:16:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qbu-p1TMlwj9 for <tcmtf@ietfa.amsl.com>; Wed,  9 Jan 2013 13:16:16 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id D848821F86F6 for <tcmtf@ietf.org>; Wed,  9 Jan 2013 13:16:15 -0800 (PST)
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 <0MGD00D12N30KE@tid.hi.inet> for tcmtf@ietf.org; Wed, 09 Jan 2013 22:16:13 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id F6.D9.02896.C1EDDE05; Wed, 09 Jan 2013 22:16:12 +0100 (CET)
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 <0MGD00D0WN30KE@tid.hi.inet> for tcmtf@ietf.org; Wed, 09 Jan 2013 22:16:12 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.223]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Wed, 09 Jan 2013 22:16:12 +0100
Date: Wed, 09 Jan 2013 21:16:11 +0000
From: JUAN ANTONIO CASTELL LUCIA <jacl@tid.es>
In-reply-to: <0b9701cdee85$b09358c0$11ba0a40$@cisco.com>
X-Originating-IP: [10.95.64.115]
To: Dan Wing <dwing@cisco.com>, "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <49F52EC1A431BA4BBA8BA8CFF429B73905F44EBE@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] Questions regarding the TCMTF WG Chart proposal. 1
Thread-index: Ac3uTJFFLbx+z32QTGuvtXZ79XI24QAKk8AAAAELoAAAAI/yAAAL56zw
X-AuditID: 0a5f4e69-b7f636d000000b50-8b-50edde1cc62c
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGKsWRmVeSWpSXmKPExsXCFe9nqCtz722AwdRXpha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxocDv1gKOhUq1j2fwd7AuF+yi5GTQ0LAROL9oY3sELaYxIV7 69m6GLk4hAS2MUrc23qeEcL5wSjx9O4PKGcmo8T2OUuZuhg5OFgEVCXeH9YB6WYT0JM4tOo/ I4gtLOAu0bzrAyuIzSlgITFr32QWiA0KEn/OPQazRQTyJN7tPwlWzyvgLdH46h0ThC0o8WPy PbAaZgEdid7v35ghbHGJOb8mskLY2hJP3l0AsxkFZCVWnj/NCDHTQ+LajMfsELabxI+Vm9kg 9gpILNlznhnCFpV4+fgfK8QvBxklpr0+zTyBUWwWkt2zkOyehWT3LCS7FzCyrGIUK04qykzP KMlNzMxJNzDSy8jUy8xLLdnECImYzB2My3eqHGIU4GBU4uH94fg2QIg1say4MvcQoyQHk5Io b/9toBBfUn5KZUZicUZ8UWlOavEhRgkOZiUR3pDtQDnelMTKqtSifJiUDAeHkgSv5V2glGBR anpqRVpmDjAtwKSZODhB2nmA2nfdAWkvLkjMLc5Mh8ifYlTlOHXwzlNGIZa8/LxUKXFeYZBB AiBFGaV5cHNeMYoDHSzMawCS5QEmNrgJr4CGMwENnzP1DcjwkkSElFQDo/fp+eovG31Klnq4 uVqWJdY8cb63lcNnJ++igzsN//0SnnNXrlfmw4kTE8Tnbf+3d91V4Q2sHbM+pay5Y7lgRfYL 1eT6ohyBD/fWmehGzFKIsv9p/UbmTkZpbKi8cA5L070HZXwlR0z6PSNuHOi7EOprqj5t58eV 73pj5fcV3vV/FOxtdTHMW4mlOCPRUIu5qDgRAAdlVAkpAwAA
References: <007201cdee4e$61e4d960$25ae8c20$@unizar.es> <0b5901cdee7f$425a64d0$c70f2e70$@cisco.com> <00fa01cdee83$70e73720$52b5a560$@unizar.es> <0b9701cdee85$b09358c0$11ba0a40$@cisco.com>
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
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, 09 Jan 2013 21:16:17 -0000

Hi all, I agree with Dan. The first kind of signaling ("auto-negotiation") =
is needed from the beginning if we don't want an extremely static protocol =
and therefore possibly difficult to get it working, especially when in most=
 of cases the peers belong to different entities/companies.

I think the second kind of signaling (dynamic (de)activation) is very usefu=
l in many scenarios (e.g. unexpected congestion in a segment of the network=
, or in the service provider that would accept that extra delay or jitter i=
n those circumstances), but it could be an extension that can be added late=
r.

Regards

-----Mensaje original-----
De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de Dan=
 Wing
Enviado el: mi=E9rcoles, 09 de enero de 2013 17:24
Para: jsaldana@unizar.es; tcmtf@ietf.org
Asunto: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1

> -----Original Message-----
> From: Jose Saldana [mailto:jsaldana@unizar.es]
> Sent: Wednesday, January 09, 2013 8:08 AM
> To: 'Dan Wing'; tcmtf@ietf.org
> Subject: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
> 1
>
> Dan,
>
> The question is if we should include in the charter this objective:
> writing a document about two things which have somewhat appeared
> during the
> discussion:
>
> - Negotiation mechanisms to decide the options at each layer
> (compression, multiplexing and tunneling) between mux and demux.
> Perhaps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP
> and IPHC, so the two machines will have to negotiate in order to
> decide which compression protocol use.

We need that -- it is capabilities negotiation.  It is needed because the p=
rotocol will fail if one side mistakenly thinks the other side has certain =
functionality, and because we will want to add some fancy new compression i=
n the year 2020 and will need to negotiate it.

I don't think it needs to be a separate milestone or a separate document, t=
hough.

> - dynamically establishing, modifying and releasing tunnels

-d

> Best regards,
>
> Jose
>
> > -----Mensaje original-----
> > De: Dan Wing [mailto:dwing@cisco.com] Enviado el: mi=E9rcoles, 09 de
> > enero de 2013 16:38
> > Para: jsaldana@unizar.es; tcmtf@ietf.org
> > Asunto: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
> > 1
> >
> > > -----Original Message-----
> > > From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
> > > Behalf Of Jose Saldana
> > > Sent: Wednesday, January 09, 2013 1:48 AM
> > > To: tcmtf@ietf.org
> > > Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
> > > 1
> > >
> > > One question is if we should consider the creation of a specific
> > > draft about signaling issues.
> >
> > So, this is a 'problem statement', describing the problem we're
> > trying to
> solve
> > (e.g., the application's tolerance for TCMTF-induced jitter)?
> > Or, this is a document analyzing how we signal TCMTF capabilities to
> > the other end?
> >
> >
> > > In paragraph 5, I have written the idea, but I don't currently
> > > know if it is necessary at this stage: "a mechanism to negotiate
> > > which concrete option would they use in each layer".
> > >
> > >
> > >
> > > My opinion: We could first focus on drafts (A) and (B), and later
> > > re- charter the WG if necessary in order to consider this other
> document.
> >
> > Agreed.
> >
> > -d
> >
> >
> > >
> > >
> > >
> > > What do you think?
> > >
> > >
> > >
> > > 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 mperumal@cisco.com  Thu Jan 10 01:27:00 2013
Return-Path: <mperumal@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA0DD21F84C9 for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 01:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YhSAzwr3Ac6a for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 01:26:51 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id D890F21F84FC for <tcmtf@ietf.org>; Thu, 10 Jan 2013 01:26:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5235; q=dns/txt; s=iport; t=1357810010; x=1359019610; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=GiTUktwmdJ9KJgPducwcfLImrGqDsXicd4GM7YK8YRQ=; b=QtAjrF911+aDbiA1S1NevfGzQW1kEC6E9/FBK+qTy2UNqsRXF/pUyaDU pFRgaly7O3BZYyDlSe2TANHRefWeLspcmLNwRIulfk9kzDqWVVj+YRDYO r1VJlTMiIknEXur9aKZpGwjpH/bahxIXX+iRNa3m1xdNrGoUUvjrJHDeR U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAKuI7lCtJXG+/2dsb2JhbABEvWwWc4IeAQEBBAEBAWsGEQQCAQgRBAEBCx0HJwsUCQgBAQQBEgiIEQy0coxig1dhA4gtiiyTfIJ0gW81
X-IronPort-AV: E=Sophos;i="4.84,443,1355097600"; d="scan'208";a="160648418"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-1.cisco.com with ESMTP; 10 Jan 2013 09:26:48 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r0A9QmBL004963 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 10 Jan 2013 09:26:48 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.7]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Thu, 10 Jan 2013 03:26:48 -0600
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: JUAN ANTONIO CASTELL LUCIA <jacl@tid.es>, "Dan Wing (dwing)" <dwing@cisco.com>, "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
Thread-Index: Ac3uTJFFLbx+z32QTGuvtXZ79XI24QAKk8AAAAELoAAAAI/yAAAL56zwABlBWnA=
Date: Thu, 10 Jan 2013 09:26:48 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE223FBCBC7@xmb-rcd-x02.cisco.com>
References: <007201cdee4e$61e4d960$25ae8c20$@unizar.es> <0b5901cdee7f$425a64d0$c70f2e70$@cisco.com> <00fa01cdee83$70e73720$52b5a560$@unizar.es> <0b9701cdee85$b09358c0$11ba0a40$@cisco.com> <49F52EC1A431BA4BBA8BA8CFF429B73905F44EBE@EX10-MB2-MAD.hi.inet>
In-Reply-To: <49F52EC1A431BA4BBA8BA8CFF429B73905F44EBE@EX10-MB2-MAD.hi.inet>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.142.108.114]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
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, 10 Jan 2013 09:27:02 -0000

Along with it I think we also need a way for the muxer and de-muxer to disc=
over each other. In a way it is a generalization of:
> dynamically establishing, modifying and releasing tunnels

Once we have that the muxer and de-muxer can setup a tunnel on-demand and d=
on't have to assume that there is always a muxer/de-muxer at the other end =
of an existing tunnel.

When a muxer/de-muxer discovers more than one de-muxer/muxer, we may also n=
eed a mechanism to elect a muxer and a de-muxer for a flow -- but, I think =
it can be added later.

Muthu

|-----Original Message-----
|From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of =
JUAN ANTONIO CASTELL LUCIA
|Sent: Thursday, January 10, 2013 2:46 AM
|To: Dan Wing (dwing); jsaldana@unizar.es; tcmtf@ietf.org
|Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
|
|Hi all, I agree with Dan. The first kind of signaling ("auto-negotiation")=
 is needed from the
|beginning if we don't want an extremely static protocol and therefore poss=
ibly difficult to get it
|working, especially when in most of cases the peers belong to different en=
tities/companies.
|
|I think the second kind of signaling (dynamic (de)activation) is very usef=
ul in many scenarios (e.g.
|unexpected congestion in a segment of the network, or in the service provi=
der that would accept that
|extra delay or jitter in those circumstances), but it could be an extensio=
n that can be added later.
|
|Regards
|
|-----Mensaje original-----
|De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de Da=
n Wing
|Enviado el: mi=E9rcoles, 09 de enero de 2013 17:24
|Para: jsaldana@unizar.es; tcmtf@ietf.org
|Asunto: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
|
|> -----Original Message-----
|> From: Jose Saldana [mailto:jsaldana@unizar.es]
|> Sent: Wednesday, January 09, 2013 8:08 AM
|> To: 'Dan Wing'; tcmtf@ietf.org
|> Subject: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
|> 1
|>
|> Dan,
|>
|> The question is if we should include in the charter this objective:
|> writing a document about two things which have somewhat appeared
|> during the
|> discussion:
|>
|> - Negotiation mechanisms to decide the options at each layer
|> (compression, multiplexing and tunneling) between mux and demux.
|> Perhaps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP
|> and IPHC, so the two machines will have to negotiate in order to
|> decide which compression protocol use.
|
|We need that -- it is capabilities negotiation.  It is needed because the =
protocol will fail if one
|side mistakenly thinks the other side has certain functionality, and becau=
se we will want to add some
|fancy new compression in the year 2020 and will need to negotiate it.
|
|I don't think it needs to be a separate milestone or a separate document, =
though.
|
|> - dynamically establishing, modifying and releasing tunnels
|
|-d
|
|> Best regards,
|>
|> Jose
|>
|> > -----Mensaje original-----
|> > De: Dan Wing [mailto:dwing@cisco.com] Enviado el: mi=E9rcoles, 09 de
|> > enero de 2013 16:38
|> > Para: jsaldana@unizar.es; tcmtf@ietf.org
|> > Asunto: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
|> > 1
|> >
|> > > -----Original Message-----
|> > > From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
|> > > Behalf Of Jose Saldana
|> > > Sent: Wednesday, January 09, 2013 1:48 AM
|> > > To: tcmtf@ietf.org
|> > > Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
|> > > 1
|> > >
|> > > One question is if we should consider the creation of a specific
|> > > draft about signaling issues.
|> >
|> > So, this is a 'problem statement', describing the problem we're
|> > trying to
|> solve
|> > (e.g., the application's tolerance for TCMTF-induced jitter)?
|> > Or, this is a document analyzing how we signal TCMTF capabilities to
|> > the other end?
|> >
|> >
|> > > In paragraph 5, I have written the idea, but I don't currently
|> > > know if it is necessary at this stage: "a mechanism to negotiate
|> > > which concrete option would they use in each layer".
|> > >
|> > >
|> > >
|> > > My opinion: We could first focus on drafts (A) and (B), and later
|> > > re- charter the WG if necessary in order to consider this other
|> document.
|> >
|> > Agreed.
|> >
|> > -d
|> >
|> >
|> > >
|> > >
|> > >
|> > > What do you think?
|> > >
|> > >
|> > >
|> > > Jose
|> > >
|> > >
|
|
|_______________________________________________
|tcmtf mailing list
|tcmtf@ietf.org
|https://www.ietf.org/mailman/listinfo/tcmtf
|
|________________________________
|
|Este mensaje se dirige exclusivamente a su destinatario. Puede consultar n=
uestra 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 r=
eceive 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 fpb@tid.es  Thu Jan 10 01:51:29 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E4D021F88CC for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 01:51:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300,  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 bNjen+jCFXd0 for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 01:51:23 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 09D5521F863A for <tcmtf@ietf.org>; Thu, 10 Jan 2013 01:51:21 -0800 (PST)
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 <0MGE00B8CM1F27@tid.hi.inet> for tcmtf@ietf.org; Thu, 10 Jan 2013 10:51:20 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 4B.31.02896.71F8EE05; Thu, 10 Jan 2013 10:51:19 +0100 (CET)
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 <0MGE00B8UM1J27@tid.hi.inet> for tcmtf@ietf.org; Thu, 10 Jan 2013 10:51:19 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.223]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.004; Thu, 10 Jan 2013 10:48:28 +0100
Date: Thu, 10 Jan 2013 09:51:18 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <E721D8C6A2E1544DB2DEBC313AF54DE223FBCBC7@xmb-rcd-x02.cisco.com>
X-Originating-IP: [10.95.64.115]
To: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>, JUAN ANTONIO CASTELL LUCIA <jacl@tid.es>, "Dan Wing (dwing)" <dwing@cisco.com>, "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A2528952B2@EX10-MB2-MAD.hi.inet>
Content-id: <FF4076D7AF1FC3419866B204A5FA8172@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] Questions regarding the TCMTF WG Chart proposal. 1
Thread-index: Ac3uTJFFLbx+z32QTGuvtXZ79XI24QAKk8AAAAELoAAAAI/yAAAL56zwABlBWnAAAYehgA==
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4e69-b7f636d000000b50-68-50ee8f172d90
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKKsWRmVeSWpSXmKPExsXCFe9nqCve/y7A4N9HU4tdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoEr48GxmywFq8wrLq3/xtTA+Eeni5GTQ0LARKLt/xsWCFtM4sK9 9WxdjFwcQgLbGCVmXHjECuH8YJT42nYNKrOJUeLw4uVMIC0sAqoSVxa/ArPZBLQkTt9dBTZK WMBd4uLpm2wgNqeAr8SsvycYIVYoSPw595gFZJCIwCNGiVnv3oM18wp4S/xqa2EFsZkFzCSu nZ7HBhEXlPgx+R4LRFxHovf7N2YIW1yiufUmVFxb4sm7C2C9jAKyEu/mzwezRQQ8JK7NeMwO YUdILDh/BKxeVEBPou3YGXaIgwQkluw5zwxhi0q8fPyPdQKj+CwkZ8xCcsYsJGfMQnLGLCRn LGBkXcUoVpxUlJmeUZKbmJmTbmCkl5Gpl5mXWrKJERJjmTsYl+9UOcQowMGoxMObUPcuQIg1 say4MvcQoyQHk5Iob1EPUIgvKT+lMiOxOCO+qDQntfgQowQHs5IIb8j2twFCvCmJlVWpRfkw KRkODiUJXsk+oDbBotT01Iq0zBxgIoFJM3FwgrTzALWngtTwFhck5hZnpkPkTzFqc7Qc6H7O yDFjYs9zRiGWvPy8VClx3hm9QKUCIKUZpXlw014xigOdLcx7HCTLA0yLcHNeAa1gAloxZ+ob kBUliQgpqQZG9WsL/OtuOm25P6uef5fO1f69emanGTUr7CUKTbN9pIwfftdJzNoi6XYnU7FR 2yUqRnB5kN6XB9ce8SWoZ5XEbVXd1Z4trOChonHy8P2irRlrIjuiuRU/5yfetRfKXm3Xayun KXd3n2nFAqMLn/dP73Hd2ORSzOB65vmxxDoxmS+7mBtvf1RiKc5INNRiLipOBACkSY9CSAMA	AA==
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
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, 10 Jan 2013 09:51:31 -0000

Hi all,

        I also agree with the idea of including the mux-demux signaling wit=
hin
the draft A (as Dan said, they are capabilities negotiation). This draft
should be able to get two boxes with TCMTF fully working between them.
Under my point of view this includes the definition of the capabilities in
each node and the negotiation of that capabilities.
        On the other hand,  the selection of flows to be potentially TCMTFe=
d
could be something undefined at the beginning (it may be statically
configured for example), but it is something that will NEED to be defined
to be dynamically enforced at the mux from a higher entity (policy
manager). That functionality would be addressed to a different draft in
the future, re-chartering the WG.
        Regarding the "dynamically establishing, modifying and releasing tu=
nnels"
I also agree with Muthu that it is something that can be added later.

Regards,

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




On 10/01/13 10:26, "Muthu Arul Mozhi Perumal (mperumal)"
<mperumal@cisco.com> wrote:

>Along with it I think we also need a way for the muxer and de-muxer to
>discover each other. In a way it is a generalization of:
>> dynamically establishing, modifying and releasing tunnels
>
>Once we have that the muxer and de-muxer can setup a tunnel on-demand and
>don't have to assume that there is always a muxer/de-muxer at the other
>end of an existing tunnel.
>
>When a muxer/de-muxer discovers more than one de-muxer/muxer, we may also
>need a mechanism to elect a muxer and a de-muxer for a flow -- but, I
>think it can be added later.
>
>Muthu
>
>|-----Original Message-----
>|From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
>Of JUAN ANTONIO CASTELL LUCIA
>|Sent: Thursday, January 10, 2013 2:46 AM
>|To: Dan Wing (dwing); jsaldana@unizar.es; tcmtf@ietf.org
>|Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
>|
>|Hi all, I agree with Dan. The first kind of signaling
>("auto-negotiation") is needed from the
>|beginning if we don't want an extremely static protocol and therefore
>possibly difficult to get it
>|working, especially when in most of cases the peers belong to different
>entities/companies.
>|
>|I think the second kind of signaling (dynamic (de)activation) is very
>useful in many scenarios (e.g.
>|unexpected congestion in a segment of the network, or in the service
>provider that would accept that
>|extra delay or jitter in those circumstances), but it could be an
>extension that can be added later.
>|
>|Regards
>|
>|-----Mensaje original-----
>|De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>Dan Wing
>|Enviado el: mi=E9rcoles, 09 de enero de 2013 17:24
>|Para: jsaldana@unizar.es; tcmtf@ietf.org
>|Asunto: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
>|
>|> -----Original Message-----
>|> From: Jose Saldana [mailto:jsaldana@unizar.es]
>|> Sent: Wednesday, January 09, 2013 8:08 AM
>|> To: 'Dan Wing'; tcmtf@ietf.org
>|> Subject: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
>|> 1
>|>
>|> Dan,
>|>
>|> The question is if we should include in the charter this objective:
>|> writing a document about two things which have somewhat appeared
>|> during the
>|> discussion:
>|>
>|> - Negotiation mechanisms to decide the options at each layer
>|> (compression, multiplexing and tunneling) between mux and demux.
>|> Perhaps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP
>|> and IPHC, so the two machines will have to negotiate in order to
>|> decide which compression protocol use.
>|
>|We need that -- it is capabilities negotiation.  It is needed because
>the protocol will fail if one
>|side mistakenly thinks the other side has certain functionality, and
>because we will want to add some
>|fancy new compression in the year 2020 and will need to negotiate it.
>|
>|I don't think it needs to be a separate milestone or a separate
>document, though.
>|
>|> - dynamically establishing, modifying and releasing tunnels
>|
>|-d
>|
>|> Best regards,
>|>
>|> Jose
>|>
>|> > -----Mensaje original-----
>|> > De: Dan Wing [mailto:dwing@cisco.com] Enviado el: mi=E9rcoles, 09 de
>|> > enero de 2013 16:38
>|> > Para: jsaldana@unizar.es; tcmtf@ietf.org
>|> > Asunto: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
>|> > 1
>|> >
>|> > > -----Original Message-----
>|> > > From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
>|> > > Behalf Of Jose Saldana
>|> > > Sent: Wednesday, January 09, 2013 1:48 AM
>|> > > To: tcmtf@ietf.org
>|> > > Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
>|> > > 1
>|> > >
>|> > > One question is if we should consider the creation of a specific
>|> > > draft about signaling issues.
>|> >
>|> > So, this is a 'problem statement', describing the problem we're
>|> > trying to
>|> solve
>|> > (e.g., the application's tolerance for TCMTF-induced jitter)?
>|> > Or, this is a document analyzing how we signal TCMTF capabilities to
>|> > the other end?
>|> >
>|> >
>|> > > In paragraph 5, I have written the idea, but I don't currently
>|> > > know if it is necessary at this stage: "a mechanism to negotiate
>|> > > which concrete option would they use in each layer".
>|> > >
>|> > >
>|> > >
>|> > > My opinion: We could first focus on drafts (A) and (B), and later
>|> > > re- charter the WG if necessary in order to consider this other
>|> document.
>|> >
>|> > Agreed.
>|> >
>|> > -d
>|> >
>|> >
>|> > >
>|> > >
>|> > >
>|> > > What do you think?
>|> > >
>|> > >
>|> > >
>|> > > 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 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  Thu Jan 10 02:10:58 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13F3921F849A for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 02:10:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.798
X-Spam-Level: 
X-Spam-Status: No, score=-5.798 tagged_above=-999 required=5 tests=[AWL=0.500,  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 OkXfjZvCap9D for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 02:10:55 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id CA38921F8472 for <tcmtf@ietf.org>; Thu, 10 Jan 2013 02:10:53 -0800 (PST)
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 <0MGE00BB5MY427@tid.hi.inet> for tcmtf@ietf.org; Thu, 10 Jan 2013 11:10:52 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 6D.B1.02896.BA39EE05; Thu, 10 Jan 2013 11:10:51 +0100 (CET)
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 <0MGE00B7KMXP27@tid.hi.inet> for tcmtf@ietf.org; Thu, 10 Jan 2013 11:10:51 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.223]) by ex10-htcas3-mad.hi.inet ([::1]) with mapi id 14.02.0328.009; Thu, 10 Jan 2013 10:58:35 +0100
Date: Thu, 10 Jan 2013 10:01:24 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <A3179A2C9AAEE647BE70AC4C7881D5FB01775E6A@sluga.fer.hr>
X-Originating-IP: [10.95.64.115]
To: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>, "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A252895425@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_1N4WKeIuUnwSqT0JGSK2cg)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2
Thread-index: Ac3uTNeTbO+aCk7ITXS7wkpgZ6Gw0gABangwADG+O4A=
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4e69-b7f636d000000b50-ce-50ee93ab5352
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrJKsWRmVeSWpSXmKPExsXCFe9nqLtm8rsAgwdfWCx2fd7A6MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujJNfr7MVnPat2Pz7NHsDY69LFyMnh4SAicSXpkNsELaYxIV7 64FsLg4hgW2MEoc//mcCSQgJ/GCUWHTNFiIxk1Hi+4LTLCAJFgFViTl737GC2GwCWhKn764C iwsLuEs0fG1jBLE5BVwkWqecY4HYoCDx59xjFpBBIgITGSV2dC8B28AskCLxdeEGsAZeAW+J W/u6mCBsQYkfk++xQNTkSkx9sB2qXlyiufUmWJwR6Ozvp9aAxUUEPCRa3s1j72LkALKtJNYc FgUJiwroSbQdO8MOcYOAxJI955khbFGJl4//sU5gFJuFZNssJNtmIdkGYetJPDs1C8rWlli2 8DUzhK0rcenhOlYI20zizf+JbMhqFjByrGIUK04qykzPKMlNzMxJNzDSy8jUy8xLLdnECInH zB2My3eqHGIU4GBU4uFNqHsXIMSaWFZcmXuIUZKDSUmU90A/UIgvKT+lMiOxOCO+qDQntfgQ owQHs5IIb8j2twFCvCmJlVWpRfkwKRkODiUJ3luTgNoEi1LTUyvSMnOASQcmzcTBCdLOA9S+ BKSGt7ggMbc4Mx0if4pRUkqctxEkIQCSyCjNg+t9xSgOdKQwrxVIlgeYHuG6XgENZAIaOGfq G5CBJYkIKakGxkPLXmXwqdqLMO/JXr+p5xr/ro0NF5oMj+dXZ22adbrdPnTPvEnLJp0+UHx4 U8X2UysTBCfy/V3uYfC8aD4H47etUYd1S/omBB+6uFfHa7FDnV2bg5lYUFTiqzKhhXarPR+z +V3S8vbobl0pPZ/RdKJZ6p/bsmrsBYq3bcK2fFoztXLCrfff5ymxFGckGmoxFxUnAgD4MekM TAMAAA==
Cc: "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>, "Matteo.Berioli@dlr.de" <Matteo.Berioli@dlr.de>
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2
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, 10 Jan 2013 10:10:58 -0000

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

Hi Mirko, Jose,

I also think that satellite specific scenario can wait to be discussed, foc=
using our efforts in the complete definition of the TCMTF itself. Regarding=
 the discussion about the signaling for capabilities negotiation, it is bei=
ng discussed in a different thread.

Regards,

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

From: Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr<mailto:Mirko.Suznjevic@fe=
r.hr>>
Date: mi=E9rcoles, 9 de enero de 2013 11:21
To: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.es<mai=
lto:jsaldana@unizar.es>>, "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ie=
tf.org<mailto:tcmtf@ietf.org>>
Cc: "Tomaso.deCola@dlr.de<mailto:Tomaso.deCola@dlr.de>" <Tomaso.deCola@dlr.=
de<mailto:Tomaso.deCola@dlr.de>>, "Matteo.Berioli@dlr.de<mailto:Matteo.Beri=
oli@dlr.de>" <Matteo.Berioli@dlr.de<mailto:Matteo.Berioli@dlr.de>>, Fernand=
o Pascual Blanco <fpb@tid.es<mailto:fpb@tid.es>>
Subject: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2

Well the satelite scenario is very interesting application of TCMTF, but I =
think that at this point we should focus our efforts on the current documen=
ts. Once we have the draft of the satellite scenario written and discussed =
we can include it in the new version of the Charter.
I think that the same applies to your first question regarding the specific=
 draft about signaling issues. I think that the WG can be re-chartered late=
r on.

Mirko Suznjevic

From: tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-b=
ounces@ietf.org] On Behalf Of Jose Saldana
Sent: Wednesday, January 9, 2013 10:49 AM
To: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Cc: Tomaso.deCola@dlr.de<mailto:Tomaso.deCola@dlr.de>; Matteo.Berioli@dlr.d=
e<mailto:Matteo.Berioli@dlr.de>; Fernando Pascual Blanco
Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2

There is another question: Tomaso, from DLR, proposed another draft for a s=
pecific satellite scenario (http://www.ietf.org/mail-archive/web/tcmtf/curr=
ent/msg00095.html). Should we include this in the charter?

My opinion is that, at this stage, we could begin the WG without considerin=
g this, and at the same time a draft could be written and discussed. Accord=
ing to the ideas and feedback after that, including it in a new version of =
the Charter could be considered.

Jose


________________________________

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

--Boundary_(ID_1N4WKeIuUnwSqT0JGSK2cg)
Content-id: <0408EB481AB01145AAA8A2196E28C87E@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>Hi Mirko, Jose,</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>I also=
 think that satellite specific scenario can wait to be discussed, focusing =
our efforts in the complete definition of the TCMTF itself. Regarding the d=
iscussion about the signaling for capabilities
 negotiation, it is being discussed in a different thread.&nbsp;</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><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>Mirko Su=BEnjevi=E6 &lt;<a hr=
ef=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>mi=E9rcoles, 9 de enero de 20=
13 11:21<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:jsaldan=
a@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsaldana@un=
izar.es">jsaldana@unizar.es</a>&gt;, &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>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:Tomaso.=
deCola@dlr.de">Tomaso.deCola@dlr.de</a>&quot; &lt;<a href=3D"mailto:Tomaso.=
deCola@dlr.de">Tomaso.deCola@dlr.de</a>&gt;, &quot;<a href=3D"mailto:Matteo=
.Berioli@dlr.de">Matteo.Berioli@dlr.de</a>&quot; &lt;<a href=3D"mailto:Matt=
eo.Berioli@dlr.de">Matteo.Berioli@dlr.de</a>&gt;,
 Fernando Pascual Blanco &lt;<a href=3D"mailto:fpb@tid.es">fpb@tid.es</a>&g=
t;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: [tcmtf] Questions rega=
rding the TCMTF WG Chart proposal. 2<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:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
span.EmailStyle17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.EmailStyle18
	{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"HR">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Well th=
e satelite scenario is very interesting application of TCMTF, but I think t=
hat at this point we should focus our efforts on the current documents. Onc=
e we have the draft of the satellite scenario
 written and discussed we can include it in the new version of the Charter.=
 </span>
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I think=
 that the same applies to your first question regarding the specific draft =
about signaling issues. I think that the WG can be re-chartered later on.</=
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">Mirko S=
uznjevic</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0c=
m 0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10pt; fon=
t-family:Tahoma,sans-serif">From:</span></b><span lang=3D"EN-US" style=3D"f=
ont-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>On Behalf Of </b>Jose Saldana<br>
<b>Sent:</b> Wednesday, January 9, 2013 10:49 AM<br>
<b>To:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>=
; <a href=3D"mailto:Matteo.Berioli@dlr.de">
Matteo.Berioli@dlr.de</a>; Fernando Pascual Blanco<br>
<b>Subject:</b> [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2<=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">There is another question: Toma=
so, from DLR, proposed another draft for a specific satellite scenario (<a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00095.html">h=
ttp://www.ietf.org/mail-archive/web/tcmtf/current/msg00095.html</a>).
 Should we include this in the charter?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">My opinion is that, at this sta=
ge, we could begin the WG without considering this, and at the same time a =
draft could be written and discussed. According to the ideas and feedback a=
fter that, including it in a new version
 of the Charter could be considered.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt; font-f=
amily:Arial,sans-serif">Jose
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
</div>
</div>
</span><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_1N4WKeIuUnwSqT0JGSK2cg)--

From jsaldana@unizar.es  Thu Jan 10 02:35:26 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 717EF21F8910 for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 02:35:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QOa5Zr+0qhWp for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 02:35:25 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id F3ACF21F890E for <tcmtf@ietf.org>; Thu, 10 Jan 2013 02:35:24 -0800 (PST)
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 r0AAZIqa000598; Thu, 10 Jan 2013 11:35:18 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Michael Ramalho \(mramalho\)'" <mramalho@cisco.com>, <tcmtf@ietf.org>
References: <D21571530BF9644D9A443D6BD95B9103154BC379@xmb-rcd-x12.cisco.com>
In-Reply-To: <D21571530BF9644D9A443D6BD95B9103154BC379@xmb-rcd-x12.cisco.com>
Date: Thu, 10 Jan 2013 11:35:21 +0100
Organization: Universidad de Zaragoza
Message-ID: <002901cdef1e$31a1b130$94e51390$@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: AQMEzTQAZ53iu0VmwDVV1/HiijQI+pXUnnvg
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jan 2013 10:35:26 -0000

Hi, Michael.

I have been thinking about your mail. The question is how to identify =
the flows. We can use two examples:

Case 1: You are a network operator and you have an agreement with a =
networked gaming company. So you are trying to merge flows belonging to =
the same game, and send them multiplexed to the demux located at the =
game company. So your network has to be able to identify those flows and =
send them to the mux. So you would need a sort of "Deep Packet =
Inspection", I think. One solution: all the packets with a certain =
destination IP go to the mux. The servers of the game are clearly =
identified by their IPs.

Case 2: But what happens if you only want to save bandwidth inside your =
network?: you have to compress traffic before traversing a certain path =
with scarce bandwidth. So you will have to identify "flows" of packets =
with a cadence, and some common characteristics. In this case, you may =
need to use "signature analysis" or something, in order to know the game =
genre, etc, and thus being able to set a maximum multiplexing period, =
for example.

But I don't know if the question of identifying the flows has to be =
solved by TCMTF. There should be other machine that sends to the mux =
only the packets that have to be multiplexed.... or not?

Jose

> -----Mensaje original-----
> De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com]
> Enviado el: mi=C3=A9rcoles, 09 de enero de 2013 18:05
> Para: jsaldana@unizar.es; tcmtf@ietf.org
> Asunto: RE: [tcmtf] : New Version Notification for =
draft-saldana-tsvwg-tcmtf-
> 04.txt
>=20
> Jose, et. al.,
>=20
> Sorry for being so quiet recently on this list ... I am just beginning =
to become
> unburied from work late last year!
>=20
> You mention FPS and MMORPGs in the draft ... but has any detailed =
thought
> about how TCMTF might identify which flows it should NOT attempt to
> compress?
>=20
> Considering "the Internet of things" (where virtually every device is
> connected via IP) ... we can expect a lot of small packets ... but not
> necessarily know if we should compress them or not (e.g., FPS packets) =
... or
> what the delay bounds on the compression should be.
>=20
> Should we mention that flows that signal their own traffic class =
(e.g., using
> "Metadata" describing the flow) is a good thing to differentiate on? =
Should
> we suggest signature analysis (a probabilistic guess for the =
application based
> on its time-domain signature characteristics) might also be of =
utility?
>=20
> Being silent on this point may lessen the attractiveness to design =
using it.
>=20
> Sorry if this point has been raised before.
>=20
> Best,
>=20
> Michael Ramalho
>=20
> -----Original Message-----
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
> Of Jose Saldana
> Sent: Wednesday, January 09, 2013 4:29 AM
> To: tcmtf@ietf.org
> Subject: [tcmtf] RV: New Version Notification for =
draft-saldana-tsvwg-tcmtf-
> 04.txt
>=20
> I have just uploaded a new version of the tcmtf draft.
>=20
> Jose
>=20
> > -----Mensaje original-----
> > De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] =
Enviado
> > el: mi=C3=A9rcoles, 09 de enero de 2013 10:25
> > Para: jsaldana@unizar.es
> > CC: mperumal@cisco.com; navajas@unizar.es; dwing@cisco.com;
> fpb@tid.es
> > Asunto: New Version Notification for =
draft-saldana-tsvwg-tcmtf-04.txt
> >
> >
> > A new version of I-D, draft-saldana-tsvwg-tcmtf-04.txt has been
> > successfully submitted by Jose Saldana and posted to the IETF =
repository.
> >
> > Filename:	 draft-saldana-tsvwg-tcmtf
> > Revision:	 04
> > Title:		 Tunneling Compressed Multiplexed Traffic Flows (TCMTF)
> > Creation date:	 2013-01-09
> > WG ID:		 Individual Submission
> > Number of pages: 19
> > URL:             =
http://www.ietf.org/internet-drafts/draft-saldana-tsvwg-tcmtf-
> > 04.txt
> > Status:          =
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf
> > Htmlized:        =
http://tools.ietf.org/html/draft-saldana-tsvwg-tcmtf-04
> > Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-saldana-tsvwg-tcmtf-04
> >
> > Abstract:
> >    This document describes a method to improve the bandwidth =
utilization
> >    of network paths that carry multiple streams in parallel sharing =
a
> >    common path.  The method combines standard protocols that provide
> >    compression, multiplexing, and tunneling over a network path for =
the
> >    purpose of reducing the bandwidth used when multiple streams are
> >    carried over that path.
> >
> >
> >
> >
> > The IETF Secretariat
>=20
>=20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From jsaldana@unizar.es  Thu Jan 10 02:55:31 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88F4721F868E for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 02:55:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bC6p3avVqn22 for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 02:55:30 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2C00721F867D for <tcmtf@ietf.org>; Thu, 10 Jan 2013 02:55:21 -0800 (PST)
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 r0AAtG3Q019347; Thu, 10 Jan 2013 11:55:16 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Luigi Iannone'" <ggx@gigix.net>
References: <008101cdee4e$7881e190$6985a4b0$@unizar.es> <3FE9B877-78C2-4C0C-B8CB-2C75A84CEBC2@gigix.net>
In-Reply-To: <3FE9B877-78C2-4C0C-B8CB-2C75A84CEBC2@gigix.net>
Date: Thu, 10 Jan 2013 11:55:20 +0100
Organization: Universidad de Zaragoza
Message-ID: <002d01cdef20$fc49a850$f4dcf8f0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_002E_01CDEF29.5E0EFAB0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQD4FIBEU76HOMj4I0aNPQ9ph/L/FwIIyL3kmd3PIXA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, "'Joel M. Halpern'" <jmh@joelhalpern.com>
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 3
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, 10 Jan 2013 10:55:31 -0000

This is a multipart message in MIME format.

------=_NextPart_000_002E_01CDEF29.5E0EFAB0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi, Luigi.

=20

I get your point: perhaps we cannot mix LISP and TCMTF in draft (A).

=20

However, since it seems that they can work together, and present some
synergies, we could think about a specific =93experimental=94 draft. It =
could be
done within the LISP WG or within the TCMTF WG (if created). Perhaps it
would make more sense in the LISP WG.

=20

However, I think this would have to wait a little. Before, we would need =
to:

=20

- Better explore the synergies between LISP and TCMTF

- Have a clearer idea of TCMTF, I mean, move some steps towards the
standardization. By now, the =93ugly truth=94 is that TCMTF is still a =
=93personal
submission=94

=20

What do you think?

=20

Jose

=20

De: Luigi Iannone [mailto:ggx@gigix.net]=20
Enviado el: mi=E9rcoles, 09 de enero de 2013 12:45
Para: jsaldana@unizar.es
CC: tcmtf@ietf.org; 'Joel M. Halpern'
Asunto: Re: Questions regarding the TCMTF WG Chart proposal. 3

=20

Hi,

=20

obviously I am in favour of this ;-)

I think there are benefits is such solution.

=20

Yet, if the WG is interested in this may be a different kind of document
should be added to the charter.=20

=20

Point 3 of the charter refers to "only standard protocols are being =
used"
and aims at a "best current practice" document.=20

LISP is still considered "experimental", hence, I am not sure it can be
included in a BCP document.=20

=20

ciao

=20

Luigi

=20

On 9 Jan. 2013, at 10:47 , Jose Saldana <jsaldana@unizar.es> wrote:





Another question: Luigi proposed the possibility of including LISP as
another possibility in the Tunneling layer (
<http://www.ietf.org/mail-archive/web/tcmtf/current/msg00073.html>
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00073.html).

=20

Should this be also somewhat included in the Charter?

=20

Thanks,

=20

Jose

=20

=20


------=_NextPart_000_002E_01CDEF29.5E0EFAB0
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)"><base href=3D"x-msg://6912/"><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi, Luigi.<o:p></o:p></span></p><p class=3DMsoNormal><span =
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 get your point: perhaps we cannot mix LISP and TCMTF in draft =
(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'>However, since it seems that they can work together, and present some =
synergies, we could think about a specific &#8220;experimental&#8221; =
draft. It could be done within the LISP WG or within the TCMTF WG (if =
created). Perhaps it would make more sense in the LISP =
WG.<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'>However, I think this would have to wait a little. Before, we would =
need to:<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'>- Better explore the synergies between LISP and =
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'>- Have a clearer idea of TCMTF, I mean, move some steps towards the =
standardization. By now, the &#8220;ugly truth&#8221; is that TCMTF is =
still a &#8220;personal=A0 submission&#8221;<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'>What do you think?<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><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"'> =
Luigi Iannone [mailto:ggx@gigix.net] <br><b>Enviado el:</b> mi=E9rcoles, =
09 de enero de 2013 12:45<br><b>Para:</b> =
jsaldana@unizar.es<br><b>CC:</b> tcmtf@ietf.org; 'Joel M. =
Halpern'<br><b>Asunto:</b> Re: Questions regarding the TCMTF WG Chart =
proposal. 3<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>obviously I am in favour of this =
;-)<o:p></o:p></p></div><div><p class=3DMsoNormal>I think there are =
benefits is such solution.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Yet, if the WG is interested in this may be a =
different kind of document should be added to the =
charter.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Point 3 of the charter refers to &quot;only standard =
protocols are being used&quot; and aims at a &quot;best current =
practice&quot; document.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>LISP is still considered &quot;experimental&quot;, =
hence, I am not sure it can be included in a BCP =
document.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>ciao<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Luigi<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
9 Jan. 2013, at 10:47 , Jose Saldana &lt;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt; =
wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Another =
question: Luigi proposed the possibility of including LISP as another =
possibility in the Tunneling layer (<a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00073.html"=
><span =
style=3D'color:purple'>http://www.ietf.org/mail-archive/web/tcmtf/current=
/msg00073.html</span></a>).</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Should =
this be also somewhat included in the Charter?</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Thanks,</sp=
an><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Jose</span><s=
pan =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_002E_01CDEF29.5E0EFAB0--


From fpb@tid.es  Thu Jan 10 03:16:03 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B82921F8910 for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 03:16:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.115
X-Spam-Level: 
X-Spam-Status: No, score=-6.115 tagged_above=-999 required=5 tests=[AWL=0.484,  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 0c+km95z9MHe for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 03:16:02 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id B4CC521F88F7 for <tcmtf@ietf.org>; Thu, 10 Jan 2013 03:16:01 -0800 (PST)
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 <0MGE00DV7PYODM@tid.hi.inet> for tcmtf@ietf.org; Thu, 10 Jan 2013 12:16:00 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 4C.93.02896.0F2AEE05; Thu, 10 Jan 2013 12:16:00 +0100 (CET)
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 <0MGE00DV1PYNDM@tid.hi.inet> for tcmtf@ietf.org; Thu, 10 Jan 2013 12:16:00 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.223]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Thu, 10 Jan 2013 12:15:58 +0100
Date: Thu, 10 Jan 2013 11:15:58 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <002901cdef1e$31a1b130$94e51390$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "'Michael Ramalho (mramalho)'" <mramalho@cisco.com>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A2528959F6@EX10-MB2-MAD.hi.inet>
Content-id: <562B1AB53896774BBF2FF776C5F3D187@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] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
Thread-index: AQHN7yN34/OsZiyFmESN4kptW9pM3Q==
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4e69-b7f636d000000b50-57-50eea2f0b51b
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrEKsWRmVeSWpSXmKPExsXCFe9nqPth0bsAg9uPpCx2fd7A6MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujIMTG9kK7uhVtL9+y9bA+Ea1i5GTQ0LARGLqko9MELaYxIV7 69m6GLk4hAS2MUocm3iYEcL5wShx6MtcFghnJqPE2s3LmUFaWARUJXZv3sYCYrMJaEmcvrsK zBYWCJM4dOgGmM0pYCGx5v9tqBUKEn/OPQaLiwh0MkpcPBMBYvMKeEtceLyZHcRmFjCTWH3k FzNEXFDix+R7LBBxHYne79+YIWxxiebWm1BxbYkn7y6wgtiMQC98P7WGCWJ+uMTx9gWMELae xNWbp8BqRIHstmNn2CHuEZBYsuc8M4QtKvHy8T/WCYzis5CcMQvJGbOQnDELyRmzkJyxgJF1 FaNYcVJRZnpGSW5iZk66gZFeRqZeZl5qySZGSIRl7mBcvlPlEKMAB6MSD29C3bsAIdbEsuLK 3EOMkhxMSqK8hguAQnxJ+SmVGYnFGfFFpTmpxYcYJTiYlUR4W0ByvCmJlVWpRfkwKRkODiUJ 3kcLgVKCRanpqRVpmTnANAKTZuLgBGnnAWpPB6nhLS5IzC3OTIfIn2KUlBLnvQSSEABJZJTm wfW+YhQHOlKYtxUkywNMeHBdr4AGMgENnDP1DcjAkkSElFQD46qr97Yp7plR5KTpmHV6+nrG X6efh24x9Gv7+Kr0dV3BnvQnJh2smd5nb9hKL/YxfrJPbPsEsXPZf3fPbG4Kfhx+rC5r6SvG 4zrf7t3ZX9d8bXlV74e14aurWZh6XVj3nIhi+MZpuiRt6/F5Cl/+pq+1lj/54o/PJWnPz4Lb lGKfuBpdOHFBvlKJpTgj0VCLuag4EQDTw1Q3NQMAAA==
Subject: Re: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jan 2013 11:16:03 -0000

Hi Jose,

        I fully agree with you. TCMTF module could be embedded within a rou=
ter or
not, and the decision to apply TCMTF to a flow (and the way to signal
that) or not is something that under my point of view is out of the scope
of drafts A and B. Once defined the core TCMTF functionality we can build
things around it.

Regards,

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




On 10/01/13 11:35, "Jose Saldana" <jsaldana@unizar.es> wrote:

>Hi, Michael.
>
>I have been thinking about your mail. The question is how to identify the
>flows. We can use two examples:
>
>Case 1: You are a network operator and you have an agreement with a
>networked gaming company. So you are trying to merge flows belonging to
>the same game, and send them multiplexed to the demux located at the game
>company. So your network has to be able to identify those flows and send
>them to the mux. So you would need a sort of "Deep Packet Inspection", I
>think. One solution: all the packets with a certain destination IP go to
>the mux. The servers of the game are clearly identified by their IPs.
>
>Case 2: But what happens if you only want to save bandwidth inside your
>network?: you have to compress traffic before traversing a certain path
>with scarce bandwidth. So you will have to identify "flows" of packets
>with a cadence, and some common characteristics. In this case, you may
>need to use "signature analysis" or something, in order to know the game
>genre, etc, and thus being able to set a maximum multiplexing period, for
>example.
>
>But I don't know if the question of identifying the flows has to be
>solved by TCMTF. There should be other machine that sends to the mux only
>the packets that have to be multiplexed.... or not?
>
>Jose
>
>> -----Mensaje original-----
>> De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com]
>> Enviado el: mi=E9rcoles, 09 de enero de 2013 18:05
>> Para: jsaldana@unizar.es; tcmtf@ietf.org
>> Asunto: RE: [tcmtf] : New Version Notification for
>>draft-saldana-tsvwg-tcmtf-
>> 04.txt
>>
>> Jose, et. al.,
>>
>> Sorry for being so quiet recently on this list ... I am just beginning
>>to become
>> unburied from work late last year!
>>
>> You mention FPS and MMORPGs in the draft ... but has any detailed
>>thought
>> about how TCMTF might identify which flows it should NOT attempt to
>> compress?
>>
>> Considering "the Internet of things" (where virtually every device is
>> connected via IP) ... we can expect a lot of small packets ... but not
>> necessarily know if we should compress them or not (e.g., FPS packets)
>>... or
>> what the delay bounds on the compression should be.
>>
>> Should we mention that flows that signal their own traffic class (e.g.,
>>using
>> "Metadata" describing the flow) is a good thing to differentiate on?
>>Should
>> we suggest signature analysis (a probabilistic guess for the
>>application based
>> on its time-domain signature characteristics) might also be of utility?
>>
>> Being silent on this point may lessen the attractiveness to design
>>using it.
>>
>> Sorry if this point has been raised before.
>>
>> Best,
>>
>> Michael Ramalho
>>
>> -----Original Message-----
>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
>> Of Jose Saldana
>> Sent: Wednesday, January 09, 2013 4:29 AM
>> To: tcmtf@ietf.org
>> Subject: [tcmtf] RV: New Version Notification for
>>draft-saldana-tsvwg-tcmtf-
>> 04.txt
>>
>> I have just uploaded a new version of the tcmtf draft.
>>
>> Jose
>>
>> > -----Mensaje original-----
>> > De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] Enviado
>> > el: mi=E9rcoles, 09 de enero de 2013 10:25
>> > Para: jsaldana@unizar.es
>> > CC: mperumal@cisco.com; navajas@unizar.es; dwing@cisco.com;
>> fpb@tid.es
>> > Asunto: New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
>> >
>> >
>> > A new version of I-D, draft-saldana-tsvwg-tcmtf-04.txt has been
>> > successfully submitted by Jose Saldana and posted to the IETF
>>repository.
>> >
>> > Filename:   draft-saldana-tsvwg-tcmtf
>> > Revision:   04
>> > Title:              Tunneling Compressed Multiplexed Traffic Flows (TC=
MTF)
>> > Creation date:      2013-01-09
>> > WG ID:              Individual Submission
>> > Number of pages: 19
>> > URL:
>>http://www.ietf.org/internet-drafts/draft-saldana-tsvwg-tcmtf-
>> > 04.txt
>> > Status:
>>http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf
>> > Htmlized:
>>http://tools.ietf.org/html/draft-saldana-tsvwg-tcmtf-04
>> > Diff:
>>http://www.ietf.org/rfcdiff?url2=3Ddraft-saldana-tsvwg-tcmtf-04
>> >
>> > Abstract:
>> >    This document describes a method to improve the bandwidth
>>utilization
>> >    of network paths that carry multiple streams in parallel sharing a
>> >    common path.  The method combines standard protocols that provide
>> >    compression, multiplexing, and tunneling over a network path for
>>the
>> >    purpose of reducing the bandwidth used when multiple streams are
>> >    carried over that path.
>> >
>> >
>> >
>> >
>> > The IETF Secretariat
>>
>>
>> _______________________________________________
>> 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 mperumal@cisco.com  Thu Jan 10 03:52:35 2013
Return-Path: <mperumal@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9455321F88BC for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 03:52:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DUORu-RTfLIj for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 03:52:27 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id F000F21F88AE for <tcmtf@ietf.org>; Thu, 10 Jan 2013 03:52:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8080; q=dns/txt; s=iport; t=1357818747; x=1359028347; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=T/fY0rR/W4MSFgwfKWOMbqYN9s5t2RO3KNZ2K8zKtH4=; b=V+Ta7JTIsssrwZwAzsZ6CIYPvllhOF+r8czWFsZxAm94ajTaF6dEwhan UwkG1ykgJ+DAzvgYL+bWzL7ro2ypWFcpSLEGlI5SUO/RVK+kl2NuNoA23 AcLhH3DnldTuPTwTAOh9pqhcwqm9ESpATMYzWUqrXL6X9UqG10YZ1zwtM w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAFqq7lCtJXG//2dsb2JhbABEvWwWc4IeAQEBBAEBAWsGEQQCAQgRBAEBCx0HJwsUCQgCBAESCIgRDLROjGeDV2EDiC2KLJN8gnWBbzU
X-IronPort-AV: E=Sophos;i="4.84,443,1355097600"; d="scan'208";a="160937641"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-3.cisco.com with ESMTP; 10 Jan 2013 11:52:26 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r0ABqQ6U020035 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 10 Jan 2013 11:52:26 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.7]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0318.004; Thu, 10 Jan 2013 05:52:24 -0600
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: FERNANDO PASCUAL BLANCO <fpb@tid.es>, JUAN ANTONIO CASTELL LUCIA <jacl@tid.es>, "Dan Wing (dwing)" <dwing@cisco.com>, "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
Thread-Index: Ac3uTJFFLbx+z32QTGuvtXZ79XI24QAKk8AAAAELoAAAAI/yAAAL56zwABlBWnAAAYehgAAAP+pQ
Date: Thu, 10 Jan 2013 11:52:24 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE223FBD086@xmb-rcd-x02.cisco.com>
References: <E721D8C6A2E1544DB2DEBC313AF54DE223FBCBC7@xmb-rcd-x02.cisco.com> <F5EDC35DF914C1428C28E149F10463A2528952B2@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A2528952B2@EX10-MB2-MAD.hi.inet>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [173.39.67.39]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
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, 10 Jan 2013 11:52:35 -0000

Hi Fernando,

I think there are 3 parts to:
dynamically establishing, modifying and releasing tunnels

1. A mechanism for a muxer to discover a de-muxer (and vice versa).
2. A mechanism to elect an optimal muxer and a de-muxer when there=20
   are more than one muxer/de-muxer for a flow.
3. A mechanism to setup/release a tunnel b/w a muxer and a de-muxer.

#1 needs to be specified.
#2 can be added later.
#3 many not require much specification.

Muthu

|-----Original Message-----
|From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
|Sent: Thursday, January 10, 2013 3:21 PM
|To: Muthu Arul Mozhi Perumal (mperumal); JUAN ANTONIO CASTELL LUCIA; Dan W=
ing (dwing);
|jsaldana@unizar.es; tcmtf@ietf.org
|Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
|
|Hi all,
|
|        I also agree with the idea of including the mux-demux signaling wi=
thin
|the draft A (as Dan said, they are capabilities negotiation). This draft
|should be able to get two boxes with TCMTF fully working between them.
|Under my point of view this includes the definition of the capabilities in
|each node and the negotiation of that capabilities.
|        On the other hand,  the selection of flows to be potentially TCMTF=
ed
|could be something undefined at the beginning (it may be statically
|configured for example), but it is something that will NEED to be defined
|to be dynamically enforced at the mux from a higher entity (policy
|manager). That functionality would be addressed to a different draft in
|the future, re-chartering the WG.
|        Regarding the "dynamically establishing, modifying and releasing t=
unnels"
|I also agree with Muthu that it is something that can be added later.
|
|Regards,
|
|Fernando Pascual Blanco
|Telef=F3nica Global Resources
|Network Automation and Dynamization
|TECHNOLOGY PEOPLE GROUP
|F +34913128779
|M +34682005168
|fpb@tid.es
|
|
|
|
|On 10/01/13 10:26, "Muthu Arul Mozhi Perumal (mperumal)"
|<mperumal@cisco.com> wrote:
|
|>Along with it I think we also need a way for the muxer and de-muxer to
|>discover each other. In a way it is a generalization of:
|>> dynamically establishing, modifying and releasing tunnels
|>
|>Once we have that the muxer and de-muxer can setup a tunnel on-demand and
|>don't have to assume that there is always a muxer/de-muxer at the other
|>end of an existing tunnel.
|>
|>When a muxer/de-muxer discovers more than one de-muxer/muxer, we may also
|>need a mechanism to elect a muxer and a de-muxer for a flow -- but, I
|>think it can be added later.
|>
|>Muthu
|>
|>|-----Original Message-----
|>|From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
|>Of JUAN ANTONIO CASTELL LUCIA
|>|Sent: Thursday, January 10, 2013 2:46 AM
|>|To: Dan Wing (dwing); jsaldana@unizar.es; tcmtf@ietf.org
|>|Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
|>|
|>|Hi all, I agree with Dan. The first kind of signaling
|>("auto-negotiation") is needed from the
|>|beginning if we don't want an extremely static protocol and therefore
|>possibly difficult to get it
|>|working, especially when in most of cases the peers belong to different
|>entities/companies.
|>|
|>|I think the second kind of signaling (dynamic (de)activation) is very
|>useful in many scenarios (e.g.
|>|unexpected congestion in a segment of the network, or in the service
|>provider that would accept that
|>|extra delay or jitter in those circumstances), but it could be an
|>extension that can be added later.
|>|
|>|Regards
|>|
|>|-----Mensaje original-----
|>|De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
|>Dan Wing
|>|Enviado el: mi=E9rcoles, 09 de enero de 2013 17:24
|>|Para: jsaldana@unizar.es; tcmtf@ietf.org
|>|Asunto: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
|>|
|>|> -----Original Message-----
|>|> From: Jose Saldana [mailto:jsaldana@unizar.es]
|>|> Sent: Wednesday, January 09, 2013 8:08 AM
|>|> To: 'Dan Wing'; tcmtf@ietf.org
|>|> Subject: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
|>|> 1
|>|>
|>|> Dan,
|>|>
|>|> The question is if we should include in the charter this objective:
|>|> writing a document about two things which have somewhat appeared
|>|> during the
|>|> discussion:
|>|>
|>|> - Negotiation mechanisms to decide the options at each layer
|>|> (compression, multiplexing and tunneling) between mux and demux.
|>|> Perhaps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP
|>|> and IPHC, so the two machines will have to negotiate in order to
|>|> decide which compression protocol use.
|>|
|>|We need that -- it is capabilities negotiation.  It is needed because
|>the protocol will fail if one
|>|side mistakenly thinks the other side has certain functionality, and
|>because we will want to add some
|>|fancy new compression in the year 2020 and will need to negotiate it.
|>|
|>|I don't think it needs to be a separate milestone or a separate
|>document, though.
|>|
|>|> - dynamically establishing, modifying and releasing tunnels
|>|
|>|-d
|>|
|>|> Best regards,
|>|>
|>|> Jose
|>|>
|>|> > -----Mensaje original-----
|>|> > De: Dan Wing [mailto:dwing@cisco.com] Enviado el: mi=E9rcoles, 09 de
|>|> > enero de 2013 16:38
|>|> > Para: jsaldana@unizar.es; tcmtf@ietf.org
|>|> > Asunto: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
|>|> > 1
|>|> >
|>|> > > -----Original Message-----
|>|> > > From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
|>|> > > Behalf Of Jose Saldana
|>|> > > Sent: Wednesday, January 09, 2013 1:48 AM
|>|> > > To: tcmtf@ietf.org
|>|> > > Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
|>|> > > 1
|>|> > >
|>|> > > One question is if we should consider the creation of a specific
|>|> > > draft about signaling issues.
|>|> >
|>|> > So, this is a 'problem statement', describing the problem we're
|>|> > trying to
|>|> solve
|>|> > (e.g., the application's tolerance for TCMTF-induced jitter)?
|>|> > Or, this is a document analyzing how we signal TCMTF capabilities to
|>|> > the other end?
|>|> >
|>|> >
|>|> > > In paragraph 5, I have written the idea, but I don't currently
|>|> > > know if it is necessary at this stage: "a mechanism to negotiate
|>|> > > which concrete option would they use in each layer".
|>|> > >
|>|> > >
|>|> > >
|>|> > > My opinion: We could first focus on drafts (A) and (B), and later
|>|> > > re- charter the WG if necessary in order to consider this other
|>|> document.
|>|> >
|>|> > Agreed.
|>|> >
|>|> > -d
|>|> >
|>|> >
|>|> > >
|>|> > >
|>|> > >
|>|> > > What do you think?
|>|> > >
|>|> > >
|>|> > >
|>|> > > 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 n=
uestra 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 r=
eceive email on the basis of
|the terms set out at:
|http://www.tid.es/ES/PAGINAS/disclaimer.aspx

From fpb@tid.es  Thu Jan 10 04:33:43 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A7AE21F885C for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 04:33:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.236
X-Spam-Level: 
X-Spam-Status: No, score=-6.236 tagged_above=-999 required=5 tests=[AWL=0.363,  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 P4kyTzm4Sgor for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 04:33:42 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id CF8E521F8859 for <tcmtf@ietf.org>; Thu, 10 Jan 2013 04:33:40 -0800 (PST)
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 <0MGE00AGXTK38N@tid.hi.inet> for tcmtf@ietf.org; Thu, 10 Jan 2013 13:33:39 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 87.40.03184.325BEE05; Thu, 10 Jan 2013 13:33:39 +0100 (CET)
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 <0MGE00AGPTK28N@tid.hi.inet> for tcmtf@ietf.org; Thu, 10 Jan 2013 13:33:39 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.223]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.004; Thu, 10 Jan 2013 13:30:48 +0100
Date: Thu, 10 Jan 2013 12:33:38 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <E721D8C6A2E1544DB2DEBC313AF54DE223FBD086@xmb-rcd-x02.cisco.com>
X-Originating-IP: [10.95.64.115]
To: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>, JUAN ANTONIO CASTELL LUCIA <jacl@tid.es>, "Dan Wing (dwing)" <dwing@cisco.com>, "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A252895F08@EX10-MB2-MAD.hi.inet>
Content-id: <4E5915CDD27B8A46BCFF11EF5F29C9A2@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] Questions regarding the TCMTF WG Chart proposal. 1
Thread-index: Ac3uTJFFLbx+z32QTGuvtXZ79XI24QAKk8AAAAELoAAAAI/yAAAL56zwABlBWnAAAYehgAAAP+pQAAVrnAA=
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4068-b7fc06d000000c70-d5-50eeb5232455
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMKsWRmVeSWpSXmKPExsXCFe/Apau89V2Awcp3gha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxq0LngXrvSsWLrrO3MB4xLaLkZNDQsBEYurEO0wQtpjEhXvr 2UBsIYENjBJPdll0MXIB2T8YJRr/XWaGcDYxSkw5vY8RpIpFQFVi6qwGdhCbTUBL4vTdVSwg trCAu8TF0zfBJnEK+EocPXqTGWKDgsSfc49ZQAaJCDxilJj17j3Yal4Bb4lTu9vBmpkFzCR2 79rADhEXlPgx+R5UXEei9/s3ZghbXKK59SZUXFviybsLrCA2o4CsxLv588FsEQEPiWszHrND 2CkSsyasBztaVEBPou3YGXaIgwQkluw5D3WcqMTLx/9YJzCKz0JyxiwkZ8xCcsYsJGfMQnLG AkbWVYxixUlFmekZJbmJmTnpBoZ6GZl6mXmpJZsYIfGVsYNx+U6VQ4wCHIxKPLwJde8ChFgT y4orcw8xSnIwKYnyGq4BCvEl5adUZiQWZ8QXleakFh9ilOBgVhLhbVkAlONNSaysSi3Kh0nJ cHAoSfCabAFKCRalpqdWpGXmAJMITJqJgxOknQeo3QCkhre4IDG3ODMdIn+KUZuj5UD3c0aO GRN7njMKseTl56VKifMqgpQKgJRmlObBTXvFKA50tjAvH0iWB5gS4ea8AlrBBLRiztQ3ICtK EhFSUg2MPnt/FL83ScnkbSzQSNpXabYqaEpp8MYZP958lLszr33vUtbOxfl9IXo+Lz+dX/LZ W4PN/MkyFZsV0guelztO22Rw5Hb6jMJAE8f+qAXhP/YaXC3R6VdfeNx3w+nyBcrcdY8PiC1a Wda46mDCU02Wid8Epp0V3vjc5Y5DZEZ/leaL3P7+Z2VTlViKMxINtZiLihMBZxZkekYDAAA=
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
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, 10 Jan 2013 12:33:43 -0000

Hi Muthu,

        Regarding #1, to be honest, I am not completely sure of the need to
specify a mechanism to discover muxes and demuxes between them. I think
those kind of mechanisms have more sense in local environments but I=B4m no=
t
sure if it applies here. At least at the beginning this associations can
be done manually.
        #2 is more related to the higher entity that has to decide whether =
a flow
should be TCMTFed or not, and under my point of view it can be addressed
in a different draft.
        #3 I think should be included in the draft A, since it is a mechani=
sm
within the TFMTF protocol itself.

        What do you think?

Regards,

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




On 10/01/13 12:52, "Muthu Arul Mozhi Perumal (mperumal)"
<mperumal@cisco.com> wrote:

>Hi Fernando,
>
>I think there are 3 parts to:
>dynamically establishing, modifying and releasing tunnels
>
>1. A mechanism for a muxer to discover a de-muxer (and vice versa).
>2. A mechanism to elect an optimal muxer and a de-muxer when there
>   are more than one muxer/de-muxer for a flow.
>3. A mechanism to setup/release a tunnel b/w a muxer and a de-muxer.
>
>#1 needs to be specified.
>#2 can be added later.
>#3 many not require much specification.
>
>Muthu
>
>|-----Original Message-----
>|From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>|Sent: Thursday, January 10, 2013 3:21 PM
>|To: Muthu Arul Mozhi Perumal (mperumal); JUAN ANTONIO CASTELL LUCIA; Dan
>Wing (dwing);
>|jsaldana@unizar.es; tcmtf@ietf.org
>|Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
>|
>|Hi all,
>|
>|        I also agree with the idea of including the mux-demux signaling
>within
>|the draft A (as Dan said, they are capabilities negotiation). This draft
>|should be able to get two boxes with TCMTF fully working between them.
>|Under my point of view this includes the definition of the capabilities
>in
>|each node and the negotiation of that capabilities.
>|        On the other hand,  the selection of flows to be potentially
>TCMTFed
>|could be something undefined at the beginning (it may be statically
>|configured for example), but it is something that will NEED to be defined
>|to be dynamically enforced at the mux from a higher entity (policy
>|manager). That functionality would be addressed to a different draft in
>|the future, re-chartering the WG.
>|        Regarding the "dynamically establishing, modifying and releasing
>tunnels"
>|I also agree with Muthu that it is something that can be added later.
>|
>|Regards,
>|
>|Fernando Pascual Blanco
>|Telef=F3nica Global Resources
>|Network Automation and Dynamization
>|TECHNOLOGY PEOPLE GROUP
>|F +34913128779
>|M +34682005168
>|fpb@tid.es
>|
>|
>|
>|
>|On 10/01/13 10:26, "Muthu Arul Mozhi Perumal (mperumal)"
>|<mperumal@cisco.com> wrote:
>|
>|>Along with it I think we also need a way for the muxer and de-muxer to
>|>discover each other. In a way it is a generalization of:
>|>> dynamically establishing, modifying and releasing tunnels
>|>
>|>Once we have that the muxer and de-muxer can setup a tunnel on-demand
>and
>|>don't have to assume that there is always a muxer/de-muxer at the other
>|>end of an existing tunnel.
>|>
>|>When a muxer/de-muxer discovers more than one de-muxer/muxer, we may
>also
>|>need a mechanism to elect a muxer and a de-muxer for a flow -- but, I
>|>think it can be added later.
>|>
>|>Muthu
>|>
>|>|-----Original Message-----
>|>|From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
>|>Of JUAN ANTONIO CASTELL LUCIA
>|>|Sent: Thursday, January 10, 2013 2:46 AM
>|>|To: Dan Wing (dwing); jsaldana@unizar.es; tcmtf@ietf.org
>|>|Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
>|>|
>|>|Hi all, I agree with Dan. The first kind of signaling
>|>("auto-negotiation") is needed from the
>|>|beginning if we don't want an extremely static protocol and therefore
>|>possibly difficult to get it
>|>|working, especially when in most of cases the peers belong to different
>|>entities/companies.
>|>|
>|>|I think the second kind of signaling (dynamic (de)activation) is very
>|>useful in many scenarios (e.g.
>|>|unexpected congestion in a segment of the network, or in the service
>|>provider that would accept that
>|>|extra delay or jitter in those circumstances), but it could be an
>|>extension that can be added later.
>|>|
>|>|Regards
>|>|
>|>|-----Mensaje original-----
>|>|De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>|>Dan Wing
>|>|Enviado el: mi=E9rcoles, 09 de enero de 2013 17:24
>|>|Para: jsaldana@unizar.es; tcmtf@ietf.org
>|>|Asunto: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
>|>|
>|>|> -----Original Message-----
>|>|> From: Jose Saldana [mailto:jsaldana@unizar.es]
>|>|> Sent: Wednesday, January 09, 2013 8:08 AM
>|>|> To: 'Dan Wing'; tcmtf@ietf.org
>|>|> Subject: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
>|>|> 1
>|>|>
>|>|> Dan,
>|>|>
>|>|> The question is if we should include in the charter this objective:
>|>|> writing a document about two things which have somewhat appeared
>|>|> during the
>|>|> discussion:
>|>|>
>|>|> - Negotiation mechanisms to decide the options at each layer
>|>|> (compression, multiplexing and tunneling) between mux and demux.
>|>|> Perhaps the mux has ROHC, ECRTP and IPHC, and the demux only has
>ECRTP
>|>|> and IPHC, so the two machines will have to negotiate in order to
>|>|> decide which compression protocol use.
>|>|
>|>|We need that -- it is capabilities negotiation.  It is needed because
>|>the protocol will fail if one
>|>|side mistakenly thinks the other side has certain functionality, and
>|>because we will want to add some
>|>|fancy new compression in the year 2020 and will need to negotiate it.
>|>|
>|>|I don't think it needs to be a separate milestone or a separate
>|>document, though.
>|>|
>|>|> - dynamically establishing, modifying and releasing tunnels
>|>|
>|>|-d
>|>|
>|>|> Best regards,
>|>|>
>|>|> Jose
>|>|>
>|>|> > -----Mensaje original-----
>|>|> > De: Dan Wing [mailto:dwing@cisco.com] Enviado el: mi=E9rcoles, 09 d=
e
>|>|> > enero de 2013 16:38
>|>|> > Para: jsaldana@unizar.es; tcmtf@ietf.org
>|>|> > Asunto: RE: [tcmtf] Questions regarding the TCMTF WG Chart
>proposal.
>|>|> > 1
>|>|> >
>|>|> > > -----Original Message-----
>|>|> > > From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
>|>|> > > Behalf Of Jose Saldana
>|>|> > > Sent: Wednesday, January 09, 2013 1:48 AM
>|>|> > > To: tcmtf@ietf.org
>|>|> > > Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal.
>|>|> > > 1
>|>|> > >
>|>|> > > One question is if we should consider the creation of a specific
>|>|> > > draft about signaling issues.
>|>|> >
>|>|> > So, this is a 'problem statement', describing the problem we're
>|>|> > trying to
>|>|> solve
>|>|> > (e.g., the application's tolerance for TCMTF-induced jitter)?
>|>|> > Or, this is a document analyzing how we signal TCMTF capabilities
>to
>|>|> > the other end?
>|>|> >
>|>|> >
>|>|> > > In paragraph 5, I have written the idea, but I don't currently
>|>|> > > know if it is necessary at this stage: "a mechanism to negotiate
>|>|> > > which concrete option would they use in each layer".
>|>|> > >
>|>|> > >
>|>|> > >
>|>|> > > My opinion: We could first focus on drafts (A) and (B), and later
>|>|> > > re- charter the WG if necessary in order to consider this other
>|>|> document.
>|>|> >
>|>|> > Agreed.
>|>|> >
>|>|> > -d
>|>|> >
>|>|> >
>|>|> > >
>|>|> > >
>|>|> > >
>|>|> > > What do you think?
>|>|> > >
>|>|> > >
>|>|> > >
>|>|> > > 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


________________________________

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 mramalho@cisco.com  Thu Jan 10 06:48:31 2013
Return-Path: <mramalho@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A296221F87AD for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 06:48:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FDS47yMcrPxN for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 06:48:30 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id A3E3921F8206 for <tcmtf@ietf.org>; Thu, 10 Jan 2013 06:48:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11067; q=dns/txt; s=iport; t=1357829304; x=1359038904; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=TX+MTxO/9xpNGZ/zLmNcrNZJgb/IT+hUPuimIdhoGqk=; b=Uzhk2GVPYl6zTFl9Dhr3Sf9Nu6DXaxbeSyYBNHearHHliJING2ib8xUj brtKnIrTpSzSHVti1xwlGZhyu+XTBYBdY0YnuivCuYLOadB2MEY83oB4B qK58tWlgozcZh+QOlWamcfssdFR/ULzXXC5W1kCn9M6yE1RYqeDT5rPuY k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAGfU7lCtJXHA/2dsb2JhbAA6CoNsuX4Wc4IeAQEBAgIBAQFkBwYDDgQCAQgRBAEBCx0HJwsUCQgBAQQBEggBEod+BwW0ToxnBgqDR2EDiC2KLIRPjy2CdYFvNQ
X-IronPort-AV: E=Sophos;i="4.84,444,1355097600"; d="scan'208";a="160998444"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-3.cisco.com with ESMTP; 10 Jan 2013 14:48:24 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r0AEmNkT015943 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 10 Jan 2013 14:48:23 GMT
Received: from xmb-rcd-x12.cisco.com ([169.254.2.163]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Thu, 10 Jan 2013 08:48:23 -0600
From: "Michael Ramalho (mramalho)" <mramalho@cisco.com>
To: FERNANDO PASCUAL BLANCO <fpb@tid.es>, "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
Thread-Index: Ac3ui7/19m7iJp6vTHSMflxr4PuotgAxLtuAAAFrJAAABsArwA==
Date: Thu, 10 Jan 2013 14:48:23 +0000
Message-ID: <D21571530BF9644D9A443D6BD95B9103154BC655@xmb-rcd-x12.cisco.com>
References: <002901cdef1e$31a1b130$94e51390$@unizar.es> <F5EDC35DF914C1428C28E149F10463A2528959F6@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A2528959F6@EX10-MB2-MAD.hi.inet>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.168.118]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jan 2013 14:48:31 -0000

All,

I'll answer Fernando and Jose at the same time, with "MAR:" below.

Michael Ramalho

-----Original Message-----
From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]=20
Sent: Thursday, January 10, 2013 6:16 AM
To: jsaldana@unizar.es; Michael Ramalho (mramalho); tcmtf@ietf.org
Subject: Re: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcm=
tf-04.txt

Hi Jose,

        I fully agree with you. TCMTF module could be embedded within a rou=
ter or not, and the decision to apply TCMTF to a flow (and the way to signa=
l
that) or not is something that under my point of view is out of the scope o=
f drafts A and B.

MAR: First of all, "we" defined drafts A and B ... we can define other draf=
ts or other working group charters/proposals. However ...

MAR: I disagree ... I think this happens to be partially addressed in draft=
 B (http://www.ietf.org/id/draft-suznjevic-tsvwg-mtd-tcmtf-00.pdf ).

<MAR:>
Consider the following ... a potential TCMTF endpoint sees two small UDP pa=
ckets ... and lets further assume that it cannot tell by inspection the app=
lications the small packets belong to.

One of the packets belong to a First Person Shooter (FPS) game (very low la=
tency desired) and the other from my home thermostat (reporting my nominal =
house temperature to a service in the cloud).

My home thermostat also previously sent metadata (a traffic class flow iden=
tifier) telling all hops on the path that my packet is relatively delay ins=
ensitive (maybe via a STUN packet) ... and it doesn't mind if any particula=
r hop adds even 200 ms of per-hop delay.

Wouldn't it make sense that TCMTF assumes my thermostat flow is a strong ca=
ndidate and the FPS isn't a candidate unless it arrived "just/immediately b=
efore" a TCMTF packet creation?

The bottom line is that (deep) packet inspection will only get you so far. =
Indeed some VXI protocol designs are being modified so that they can be "mo=
re easily" identified by routers (by headers early in the packet payloads) =
- until this point there was no effort to do so and it is very, very diffic=
ult (in general) to determine a "delay tolerance" by simply looking at a pa=
rticular packet. Even more so with packet encryption ;-).

When the "internet of things" is here ... we will have lots of small packet=
s ... the exact application where TCMTF has its strongest use case. And mos=
t of these small packets will have very loose delay bounds (long nominal re=
porting intervals or periodic keep-alives for firewalls/NATs/etc.).
</MAR:>

Once defined the core TCMTF functionality we can build things around it.

MAR: True. But equally true is that if you DON'T specify useful criteria on=
 how you classify candidate TCMTF flows ... it may not be seriously conside=
red.

MAR: A good example is the "voice communications" item in Table 1 of draft =
B. If the RTP voice flow was a push-to-talk flow ... then I could agree to =
up to a 80ms mux delay. For a normal voice call, 80ms is WAY, WAY too much =
delay (most VoIP calls use ptime of 20ms for a reason!). If you knew a pack=
et was a voice packet (via RTP inspection) ... but additionally knew it bel=
onged for a push-to-talk service ... you could TCMTF it. So you really need=
 to have more knowledge than just "it is a packet of G.722.2 voice" to make=
 a decision. As an aside, the reference for Table 1 (of draft B) is not rig=
orous enough for the use claimed (you can find hundreds of references that =
would disagree with the 80 ms maximum recommendation).

Regards,

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




On 10/01/13 11:35, "Jose Saldana" <jsaldana@unizar.es> wrote:

>Hi, Michael.
>
>I have been thinking about your mail. The question is how to identify=20
>the flows. We can use two examples:
>
>Case 1: You are a network operator and you have an agreement with a=20
>networked gaming company. So you are trying to merge flows belonging to=20
>the same game, and send them multiplexed to the demux located at the=20
>game company. So your network has to be able to identify those flows=20
>and send them to the mux. So you would need a sort of "Deep Packet=20
>Inspection", I think.

MAR: As per my reply to Fernando above, DPI will only get you so far. There=
 are a lot of applications using UDP in which you cannot make a definitive =
association between the packet and a particular service.

MAR: However, when TCMTF is used on a "high-enough" speed link, the delay c=
an be arbitrarily small. Thus I think some TCMTF guidance is primarily need=
ed for low-speed links (i.e., links where the mux delay could be in excess =
of some reasonable bound, like 5 ms maximum).

>One solution: all the packets with a certain=20
>destination IP go to the mux. The servers of the game are clearly identifi=
ed by their IPs.

MAR: As an aside, if the network operator had such an agreement ... they wo=
uld know a priori something about the aggregate flows to the networked game=
 company. They could also determine this from metadata without any "special=
 arrangement".

MAR: However, even this is not general enough. We already have applications=
 that for a particular source and destination IP address/port have differen=
t QoS treatment (e.g., SVC video - different packets have different QoS req=
uirements for the same flow).

MAR: I think capabilities negotiation (another thread) should include a not=
ion of "what types of flows" to consider TCMTFing. Without it, I think TCMT=
F could make some poor decisions (not on efficiency, the dimension upon whi=
ch it always wins - but on delay) which may, in turn, create impedance for =
its acceptance.

>
>Case 2: But what happens if you only want to save bandwidth inside your
>network?: you have to compress traffic before traversing a certain path=20
>with scarce bandwidth. So you will have to identify "flows" of packets=20
>with a cadence, and some common characteristics. In this case, you may=20
>need to use "signature analysis" or something, in order to know the=20
>game genre, etc, and thus being able to set a maximum multiplexing=20
>period, for example.
>
>But I don't know if the question of identifying the flows has to be=20
>solved by TCMTF.

MAR: I was not arguing for "solving" the flow identification problem at thi=
s stage ... just mentioning it now would make sense ... and that techniques=
 such as exploiting any metadata information for the flow and/or signature =
analysis could be used for the TCMTF determination. Eventually, I think we =
need to mention how capabilities negotiation can include flow types too.

>There should be other machine that sends to the mux=20
>only the packets that have to be multiplexed.... or not?
>
>Jose
>
>> -----Mensaje original-----
>> De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com]  Enviado=20
>>el: mi=E9rcoles, 09 de enero de 2013 18:05
>> Para: jsaldana@unizar.es; tcmtf@ietf.org
>> Asunto: RE: [tcmtf] : New Version Notification for
>>draft-saldana-tsvwg-tcmtf-
>> 04.txt
>>
>> Jose, et. al.,
>>
>> Sorry for being so quiet recently on this list ... I am just=20
>>beginning to become  unburied from work late last year!
>>
>> You mention FPS and MMORPGs in the draft ... but has any detailed=20
>>thought  about how TCMTF might identify which flows it should NOT=20
>>attempt to  compress?
>>
>> Considering "the Internet of things" (where virtually every device is =20
>>connected via IP) ... we can expect a lot of small packets ... but not =20
>>necessarily know if we should compress them or not (e.g., FPS packets)=20
>>... or  what the delay bounds on the compression should be.
>>
>> Should we mention that flows that signal their own traffic class=20
>>(e.g., using  "Metadata" describing the flow) is a good thing to=20
>>differentiate on?
>>Should
>> we suggest signature analysis (a probabilistic guess for the=20
>>application based  on its time-domain signature characteristics) might=20
>>also be of utility?
>>
>> Being silent on this point may lessen the attractiveness to design=20
>>using it.
>>
>> Sorry if this point has been raised before.
>>
>> Best,
>>
>> Michael Ramalho
>>
>> -----Original Message-----
>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On=20
>>Behalf  Of Jose Saldana
>> Sent: Wednesday, January 09, 2013 4:29 AM
>> To: tcmtf@ietf.org
>> Subject: [tcmtf] RV: New Version Notification for
>>draft-saldana-tsvwg-tcmtf-
>> 04.txt
>>
>> I have just uploaded a new version of the tcmtf draft.
>>
>> Jose
>>
>> > -----Mensaje original-----
>> > De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
>> > Enviado
>> > el: mi=E9rcoles, 09 de enero de 2013 10:25
>> > Para: jsaldana@unizar.es
>> > CC: mperumal@cisco.com; navajas@unizar.es; dwing@cisco.com;
>> fpb@tid.es
>> > Asunto: New Version Notification for=20
>> > draft-saldana-tsvwg-tcmtf-04.txt
>> >
>> >
>> > A new version of I-D, draft-saldana-tsvwg-tcmtf-04.txt has been=20
>> > successfully submitted by Jose Saldana and posted to the IETF
>>repository.
>> >
>> > Filename:   draft-saldana-tsvwg-tcmtf
>> > Revision:   04
>> > Title:              Tunneling Compressed Multiplexed Traffic Flows (TC=
MTF)
>> > Creation date:      2013-01-09
>> > WG ID:              Individual Submission
>> > Number of pages: 19
>> > URL:
>>http://www.ietf.org/internet-drafts/draft-saldana-tsvwg-tcmtf-
>> > 04.txt
>> > Status:
>>http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf
>> > Htmlized:
>>http://tools.ietf.org/html/draft-saldana-tsvwg-tcmtf-04
>> > Diff:
>>http://www.ietf.org/rfcdiff?url2=3Ddraft-saldana-tsvwg-tcmtf-04
>> >
>> > Abstract:
>> >    This document describes a method to improve the bandwidth
>>utilization
>> >    of network paths that carry multiple streams in parallel sharing a
>> >    common path.  The method combines standard protocols that provide
>> >    compression, multiplexing, and tunneling over a network path for
>>the
>> >    purpose of reducing the bandwidth used when multiple streams are
>> >    carried over that path.
>> >
>> >
>> >
>> >
>> > The IETF Secretariat
>>
>>
>> _______________________________________________
>> 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 ggx@gigix.net  Thu Jan 10 06:53:40 2013
Return-Path: <ggx@gigix.net>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E62921F86D9 for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 06:53:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.04
X-Spam-Level: 
X-Spam-Status: No, score=-3.04 tagged_above=-999 required=5 tests=[AWL=0.208,  BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 b8mT0FECVKhv for <tcmtf@ietfa.amsl.com>; Thu, 10 Jan 2013 06:53:37 -0800 (PST)
Received: from mail-we0-f175.google.com (mail-we0-f175.google.com [74.125.82.175]) by ietfa.amsl.com (Postfix) with ESMTP id D946821F86AC for <tcmtf@ietf.org>; Thu, 10 Jan 2013 06:53:36 -0800 (PST)
Received: by mail-we0-f175.google.com with SMTP id z53so311720wey.34 for <tcmtf@ietf.org>; Thu, 10 Jan 2013 06:53:34 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:message-id:references:to:x-mailer:x-gm-message-state; bh=fGogHQjuHa9v3Oi7tFiGvfNC8ghz+B54OmGRDNhTAU0=; b=kPx1aeX+B2DP2MCw9Pkd4djSxcRJ3fQ8E41FJyI2sJHOC9ZyqLN3WHRXBttMd/FEB7 sAoJLtavZYbAe0QRw/ZStcEiY4gVEPEuZTGHCZ7i4M5jjyQq3rgzAbK7dd2M8sAb68cd kQ9NdSNvMTefE25z/bW08/rTFC83JMvchaGn3osQ7meWxi0GdTytKrNXwanyP1H0409B jEcMHbe5/VZuZR4CYOVdQZkq6rdKxMFF/ERdXLK7kN/UYtjKPr9IXc/Aw5trrnGlMKK8 gQF0gKBRwkz39KuP/duv1BLt4Qihy8XZ7gdF7rx4VOS3RoIdVW+tS+LGr9gaxvX2u+Uy 3RLQ==
X-Received: by 10.194.235.100 with SMTP id ul4mr115596414wjc.7.1357829614528;  Thu, 10 Jan 2013 06:53:34 -0800 (PST)
Received: from dhcp164-04.enst.fr (dhcp164-04.enst.fr. [137.194.165.4]) by mx.google.com with ESMTPS id hg17sm8699150wib.1.2013.01.10.06.53.31 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Jan 2013 06:53:32 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_B790F738-528C-43B8-AD5C-45F362C38558"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <002d01cdef20$fc49a850$f4dcf8f0$@unizar.es>
Date: Thu, 10 Jan 2013 15:53:30 +0100
Message-Id: <052A3926-115B-4941-A5D7-2DEB368C046A@gigix.net>
References: <008101cdee4e$7881e190$6985a4b0$@unizar.es> <3FE9B877-78C2-4C0C-B8CB-2C75A84CEBC2@gigix.net> <002d01cdef20$fc49a850$f4dcf8f0$@unizar.es>
To: <jsaldana@unizar.es>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQm/Ei4KThJLG7RTydgB6xla5cv56Yy4VvHWiTcrM7dyp8gWlU2Rov/s/p4EhoWyr9DuTDPZ
Cc: tcmtf@ietf.org, "'Joel M. Halpern'" <jmh@joelhalpern.com>
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 3
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, 10 Jan 2013 14:53:40 -0000

--Apple-Mail=_B790F738-528C-43B8-AD5C-45F362C38558
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi Jose,


On 10 Jan. 2013, at 11:55 , Jose Saldana <jsaldana@unizar.es> wrote:

> Hi, Luigi.
> =20
> I get your point: perhaps we cannot mix LISP and TCMTF in draft (A).
> =20
> However, since it seems that they can work together, and present some =
synergies, we could think about a specific =93experimental=94 draft. It =
could be done within the LISP WG or within the TCMTF WG (if created). =
Perhaps it would make more sense in the LISP WG.
> =20

Well, it really depends on how the TCMTF evolves. However, you are right =
that there is no space for LISP in (A) and is worth to wait a little bit =
before going forward on this path.

> However, I think this would have to wait a little. Before, we would =
need to:
> =20
> - Better explore the synergies between LISP and TCMTF

Agreed.

> - Have a clearer idea of TCMTF, I mean, move some steps towards the =
standardization. By now, the =93ugly truth=94 is that TCMTF is still a =
=93personal  submission=94
> =20

Yes, but things are moving ;-)

ciao

Luigi


> What do you think?
> =20
> Jose
> =20
> De: Luigi Iannone [mailto:ggx@gigix.net]=20
> Enviado el: mi=E9rcoles, 09 de enero de 2013 12:45
> Para: jsaldana@unizar.es
> CC: tcmtf@ietf.org; 'Joel M. Halpern'
> Asunto: Re: Questions regarding the TCMTF WG Chart proposal. 3
> =20
> Hi,
> =20
> obviously I am in favour of this ;-)
> I think there are benefits is such solution.
> =20
> Yet, if the WG is interested in this may be a different kind of =
document should be added to the charter.=20
> =20
> Point 3 of the charter refers to "only standard protocols are being =
used" and aims at a "best current practice" document.=20
> LISP is still considered "experimental", hence, I am not sure it can =
be included in a BCP document.=20
> =20
> ciao
> =20
> Luigi
> =20
> On 9 Jan. 2013, at 10:47 , Jose Saldana <jsaldana@unizar.es> wrote:
>=20
>=20
> Another question: Luigi proposed the possibility of including LISP as =
another possibility in the Tunneling layer =
(http://www.ietf.org/mail-archive/web/tcmtf/current/msg00073.html).
> =20
> Should this be also somewhat included in the Charter?
> =20
> Thanks,
> =20
> Jose
> =20


--Apple-Mail=_B790F738-528C-43B8-AD5C-45F362C38558
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://6912/"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Hi =
Jose,<div><br></div><div><br></div><div><div><div>On 10 Jan. 2013, at =
11:55 , 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: 12pt; font-family: 'Times =
New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); ">Hi, =
Luigi.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); ">I get your point: perhaps we =
cannot mix LISP and TCMTF in draft (A).<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><span lang=3D"EN-US" style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">&nbsp;</span></div><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span lang=3D"EN-US" =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">However, since it seems that they can work together, =
and present some synergies, we could think about a specific =
=93experimental=94 draft. It could be done within the LISP WG or within =
the TCMTF WG (if created). Perhaps it would make more sense in the LISP =
WG.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); =
">&nbsp;</span></div></div></div></blockquote><div><br></div><div>Well, =
it really depends on how the TCMTF evolves. However, you are right that =
there is no space for LISP in (A) and is worth to wait a little bit =
before going forward on this path.</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: 12pt; font-family: 'Times =
New Roman', serif; "><span lang=3D"EN-US" style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">However, I =
think this would have to wait a little. Before, we would need =
to:<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); ">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><span lang=3D"EN-US" style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">- Better =
explore the synergies between LISP and =
TCMTF</span></div></div></div></blockquote><div><br></div><div>Agreed.</di=
v><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: 12pt; font-family: 'Times New Roman', serif; "><span =
lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); "><o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><span lang=3D"EN-US" style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">- Have a =
clearer idea of TCMTF, I mean, move some steps towards the =
standardization. By now, the =93ugly truth=94 is that TCMTF is still a =
=93personal&nbsp; submission=94<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><span lang=3D"EN-US" style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">&nbsp;</span></div></div></div></blockquote><div><br></div><div>Yes, =
but things are moving =
;-)</div><div><br></div><div>ciao</div><div><br></div><div>Luigi</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: 12pt; font-family: 'Times New Roman', serif; "><span =
lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); ">What do you =
think?<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); ">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><span lang=3D"EN-US" style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">Jose<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); ">&nbsp;</span></div><div =
style=3D"border-style: none none none solid; border-left-width: 1.5pt; =
border-left-color: blue; padding: 0cm 0cm 0cm 4pt; "><div><div =
style=3D"border-style: solid none none; border-top-width: 1pt; =
border-top-color: rgb(181, 196, 223); padding: 3pt 0cm 0cm; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><b><span style=3D"font-size: 10pt; font-family: =
Tahoma, sans-serif; ">De:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span>Luigi Iannone =
[mailto:ggx@<a href=3D"http://gigix.net">gigix.net</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><br><b>Enviado el:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>mi=E9rcoles, 09 de enero de =
2013 12:45<br><b>Para:</b><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a><br><b>CC:</b><sp=
an class=3D"Apple-converted-space">&nbsp;</span>tcmtf@ietf.org; 'Joel M. =
Halpern'<br><b>Asunto:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: Questions regarding the =
TCMTF WG Chart proposal. 3<o:p></o:p></span></div></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
">Hi,<o:p></o:p></div><div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
">obviously I am in favour of this ;-)<o:p></o:p></div></div><div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; ">I think there are benefits is such =
solution.<o:p></o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">Yet, =
if the WG is interested in this may be a different kind of document =
should be added to the charter.&nbsp;<o:p></o:p></div></div><div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><o:p>&nbsp;</o:p></div></div><div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; ">Point 3 of the charter refers to "only standard =
protocols are being used" and aims at a "best current practice" =
document.&nbsp;<o:p></o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">LISP =
is still considered "experimental", hence, I am not sure it can be =
included in a BCP document.&nbsp;<o:p></o:p></div></div><div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><o:p>&nbsp;</o:p></div></div><div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; ">ciao<o:p></o:p></div></div><div><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
">Luigi<o:p></o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">On 9 =
Jan. 2013, at 10:47 , Jose Saldana &lt;<a =
href=3D"mailto:jsaldana@unizar.es" style=3D"color: purple; =
text-decoration: underline; ">jsaldana@unizar.es</a>&gt; =
wrote:<o:p></o:p></div></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">Another question: Luigi proposed the possibility of =
including LISP as another possibility in the Tunneling layer (<a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00073.html" =
style=3D"color: purple; text-decoration: underline; "><span =
style=3D"color: purple; =
">http://www.ietf.org/mail-archive/web/tcmtf/current/msg00073.html</span><=
/a>).</span><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; "><o:p></o:p></span></div></div><div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span lang=3D"EN-US" style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; ">&nbsp;</span><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; =
"><o:p></o:p></span></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">Should this be also somewhat included in the =
Charter?</span><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; "><o:p></o:p></span></div></div><div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span lang=3D"EN-US" style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; ">&nbsp;</span><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; =
"><o:p></o:p></span></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span lang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">Thanks,</span><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p></o:p></span></div></div><div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><span lang=3D"EN-US" style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">&nbsp;</span><span style=3D"font-size:=
 11pt; font-family: Calibri, sans-serif; =
"><o:p></o:p></span></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial, =
sans-serif; ">Jose</span><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p></o:p></span></div></div><div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><span lang=3D"EN-US" style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">&nbsp;</span><span style=3D"font-size:=
 11pt; font-family: Calibri, sans-serif; =
"><o:p></o:p></span></div></div></div></div><p class=3D"MsoNormal" =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; =
"></p></div></div></div></div></blockquote></div><br></div></body></html>=

--Apple-Mail=_B790F738-528C-43B8-AD5C-45F362C38558--

From mperumal@cisco.com  Fri Jan 11 00:34:59 2013
Return-Path: <mperumal@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D618221F86C9 for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 00:34:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xzJRY42KC-xF for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 00:34:58 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id E771921F869B for <tcmtf@ietf.org>; Fri, 11 Jan 2013 00:34:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11352; q=dns/txt; s=iport; t=1357893298; x=1359102898; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=+yHa+wZU+otc7xCg2+hsapK9n92w5JnQ2ASvhiFKxpI=; b=Akw43yGjXtXPilNefg9DcGp/l89zlBSUOe7xuZctNuriB1oQdOtSOLiJ eQVAr5XwrdsGayYoAZkz2a8qJN1JxjB1IunwJK3SkzlA3IhYkJnHuB+6b 0Epl5hM/BsAYfd6aRfbN+SBS4JExj33EefV8yIWERMdUJpLEaBy0Wtqxm 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFALrN71CtJXG9/2dsb2JhbABEvXoWc4IeAQEBBAEBAWsGEQQCAQgRBAEBCx0HJwsUCQgCBAESCIgRDLUTjGeDV2EDiCuKLJN8gnWBbzU
X-IronPort-AV: E=Sophos;i="4.84,451,1355097600"; d="scan'208";a="161078160"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-1.cisco.com with ESMTP; 11 Jan 2013 08:34:55 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r0B8YtkT030387 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 11 Jan 2013 08:34:55 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.7]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Fri, 11 Jan 2013 02:34:55 -0600
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: FERNANDO PASCUAL BLANCO <fpb@tid.es>, JUAN ANTONIO CASTELL LUCIA <jacl@tid.es>, "Dan Wing (dwing)" <dwing@cisco.com>, "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
Thread-Index: Ac3uTJFFLbx+z32QTGuvtXZ79XI24QAKk8AAAAELoAAAAI/yAAAL56zwABlBWnAAAYehgAAAP+pQAAVrnAAAKV/bgA==
Date: Fri, 11 Jan 2013 08:34:54 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE223FBF829@xmb-rcd-x02.cisco.com>
References: <E721D8C6A2E1544DB2DEBC313AF54DE223FBD086@xmb-rcd-x02.cisco.com> <F5EDC35DF914C1428C28E149F10463A252895F08@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A252895F08@EX10-MB2-MAD.hi.inet>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [173.39.67.39]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
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, 11 Jan 2013 08:35:00 -0000

Hi Fernando,

|        Regarding #1, to be honest, I am not completely sure of the=20
|need to specify a mechanism to discover muxes and demuxes between them.=20
|I think those kind of mechanisms have more sense in local environments=20
|but I=B4m not sure if it applies here. At least at the beginning this=20
|associations can be done manually.

I think it is the opposite -- in local environments you can provision/assoc=
iate them manually. However, in a multi-vendor environment over the Interne=
t this should happen automatically.

|        #2 is more related to the higher entity that has to decide whether=
=20
|a flow  should be TCMTFed or not, and under my point of view it can be=20
|addressed in a different draft.

Agree.

|        #3 I think should be included in the draft A, since it is a
|mechanism within the TFMTF protocol itself.

Agree.

Muthu

|-----Original Message-----
|From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of =
FERNANDO PASCUAL BLANCO
|Sent: Thursday, January 10, 2013 6:04 PM
|To: Muthu Arul Mozhi Perumal (mperumal); JUAN ANTONIO CASTELL LUCIA; Dan W=
ing (dwing);
|jsaldana@unizar.es; tcmtf@ietf.org
|Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
|
|Hi Muthu,
|
|        Regarding #1, to be honest, I am not completely sure of the need t=
o
|specify a mechanism to discover muxes and demuxes between them. I think
|those kind of mechanisms have more sense in local environments but I=B4m n=
ot
|sure if it applies here. At least at the beginning this associations can
|be done manually.
|        #2 is more related to the higher entity that has to decide whether=
 a flow
|should be TCMTFed or not, and under my point of view it can be addressed
|in a different draft.
|        #3 I think should be included in the draft A, since it is a mechan=
ism
|within the TFMTF protocol itself.
|
|        What do you think?
|
|Regards,
|
|Fernando Pascual Blanco
|Telef=F3nica Global Resources
|Network Automation and Dynamization
|TECHNOLOGY PEOPLE GROUP
|F +34913128779
|M +34682005168
|fpb@tid.es
|
|
|
|
|On 10/01/13 12:52, "Muthu Arul Mozhi Perumal (mperumal)"
|<mperumal@cisco.com> wrote:
|
|>Hi Fernando,
|>
|>I think there are 3 parts to:
|>dynamically establishing, modifying and releasing tunnels
|>
|>1. A mechanism for a muxer to discover a de-muxer (and vice versa).
|>2. A mechanism to elect an optimal muxer and a de-muxer when there
|>   are more than one muxer/de-muxer for a flow.
|>3. A mechanism to setup/release a tunnel b/w a muxer and a de-muxer.
|>
|>#1 needs to be specified.
|>#2 can be added later.
|>#3 many not require much specification.
|>
|>Muthu
|>
|>|-----Original Message-----
|>|From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
|>|Sent: Thursday, January 10, 2013 3:21 PM
|>|To: Muthu Arul Mozhi Perumal (mperumal); JUAN ANTONIO CASTELL LUCIA; Dan
|>Wing (dwing);
|>|jsaldana@unizar.es; tcmtf@ietf.org
|>|Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
|>|
|>|Hi all,
|>|
|>|        I also agree with the idea of including the mux-demux signaling
|>within
|>|the draft A (as Dan said, they are capabilities negotiation). This draft
|>|should be able to get two boxes with TCMTF fully working between them.
|>|Under my point of view this includes the definition of the capabilities
|>in
|>|each node and the negotiation of that capabilities.
|>|        On the other hand,  the selection of flows to be potentially
|>TCMTFed
|>|could be something undefined at the beginning (it may be statically
|>|configured for example), but it is something that will NEED to be define=
d
|>|to be dynamically enforced at the mux from a higher entity (policy
|>|manager). That functionality would be addressed to a different draft in
|>|the future, re-chartering the WG.
|>|        Regarding the "dynamically establishing, modifying and releasing
|>tunnels"
|>|I also agree with Muthu that it is something that can be added later.
|>|
|>|Regards,
|>|
|>|Fernando Pascual Blanco
|>|Telef=F3nica Global Resources
|>|Network Automation and Dynamization
|>|TECHNOLOGY PEOPLE GROUP
|>|F +34913128779
|>|M +34682005168
|>|fpb@tid.es
|>|
|>|
|>|
|>|
|>|On 10/01/13 10:26, "Muthu Arul Mozhi Perumal (mperumal)"
|>|<mperumal@cisco.com> wrote:
|>|
|>|>Along with it I think we also need a way for the muxer and de-muxer to
|>|>discover each other. In a way it is a generalization of:
|>|>> dynamically establishing, modifying and releasing tunnels
|>|>
|>|>Once we have that the muxer and de-muxer can setup a tunnel on-demand
|>and
|>|>don't have to assume that there is always a muxer/de-muxer at the other
|>|>end of an existing tunnel.
|>|>
|>|>When a muxer/de-muxer discovers more than one de-muxer/muxer, we may
|>also
|>|>need a mechanism to elect a muxer and a de-muxer for a flow -- but, I
|>|>think it can be added later.
|>|>
|>|>Muthu
|>|>
|>|>|-----Original Message-----
|>|>|From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
|>|>Of JUAN ANTONIO CASTELL LUCIA
|>|>|Sent: Thursday, January 10, 2013 2:46 AM
|>|>|To: Dan Wing (dwing); jsaldana@unizar.es; tcmtf@ietf.org
|>|>|Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. =
1
|>|>|
|>|>|Hi all, I agree with Dan. The first kind of signaling
|>|>("auto-negotiation") is needed from the
|>|>|beginning if we don't want an extremely static protocol and therefore
|>|>possibly difficult to get it
|>|>|working, especially when in most of cases the peers belong to differen=
t
|>|>entities/companies.
|>|>|
|>|>|I think the second kind of signaling (dynamic (de)activation) is very
|>|>useful in many scenarios (e.g.
|>|>|unexpected congestion in a segment of the network, or in the service
|>|>provider that would accept that
|>|>|extra delay or jitter in those circumstances), but it could be an
|>|>extension that can be added later.
|>|>|
|>|>|Regards
|>|>|
|>|>|-----Mensaje original-----
|>|>|De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre d=
e
|>|>Dan Wing
|>|>|Enviado el: mi=E9rcoles, 09 de enero de 2013 17:24
|>|>|Para: jsaldana@unizar.es; tcmtf@ietf.org
|>|>|Asunto: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 1
|>|>|
|>|>|> -----Original Message-----
|>|>|> From: Jose Saldana [mailto:jsaldana@unizar.es]
|>|>|> Sent: Wednesday, January 09, 2013 8:08 AM
|>|>|> To: 'Dan Wing'; tcmtf@ietf.org
|>|>|> Subject: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal=
.
|>|>|> 1
|>|>|>
|>|>|> Dan,
|>|>|>
|>|>|> The question is if we should include in the charter this objective:
|>|>|> writing a document about two things which have somewhat appeared
|>|>|> during the
|>|>|> discussion:
|>|>|>
|>|>|> - Negotiation mechanisms to decide the options at each layer
|>|>|> (compression, multiplexing and tunneling) between mux and demux.
|>|>|> Perhaps the mux has ROHC, ECRTP and IPHC, and the demux only has
|>ECRTP
|>|>|> and IPHC, so the two machines will have to negotiate in order to
|>|>|> decide which compression protocol use.
|>|>|
|>|>|We need that -- it is capabilities negotiation.  It is needed because
|>|>the protocol will fail if one
|>|>|side mistakenly thinks the other side has certain functionality, and
|>|>because we will want to add some
|>|>|fancy new compression in the year 2020 and will need to negotiate it.
|>|>|
|>|>|I don't think it needs to be a separate milestone or a separate
|>|>document, though.
|>|>|
|>|>|> - dynamically establishing, modifying and releasing tunnels
|>|>|
|>|>|-d
|>|>|
|>|>|> Best regards,
|>|>|>
|>|>|> Jose
|>|>|>
|>|>|> > -----Mensaje original-----
|>|>|> > De: Dan Wing [mailto:dwing@cisco.com] Enviado el: mi=E9rcoles, 09 =
de
|>|>|> > enero de 2013 16:38
|>|>|> > Para: jsaldana@unizar.es; tcmtf@ietf.org
|>|>|> > Asunto: RE: [tcmtf] Questions regarding the TCMTF WG Chart
|>proposal.
|>|>|> > 1
|>|>|> >
|>|>|> > > -----Original Message-----
|>|>|> > > From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
|>|>|> > > Behalf Of Jose Saldana
|>|>|> > > Sent: Wednesday, January 09, 2013 1:48 AM
|>|>|> > > To: tcmtf@ietf.org
|>|>|> > > Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal=
.
|>|>|> > > 1
|>|>|> > >
|>|>|> > > One question is if we should consider the creation of a specific
|>|>|> > > draft about signaling issues.
|>|>|> >
|>|>|> > So, this is a 'problem statement', describing the problem we're
|>|>|> > trying to
|>|>|> solve
|>|>|> > (e.g., the application's tolerance for TCMTF-induced jitter)?
|>|>|> > Or, this is a document analyzing how we signal TCMTF capabilities
|>to
|>|>|> > the other end?
|>|>|> >
|>|>|> >
|>|>|> > > In paragraph 5, I have written the idea, but I don't currently
|>|>|> > > know if it is necessary at this stage: "a mechanism to negotiate
|>|>|> > > which concrete option would they use in each layer".
|>|>|> > >
|>|>|> > >
|>|>|> > >
|>|>|> > > My opinion: We could first focus on drafts (A) and (B), and late=
r
|>|>|> > > re- charter the WG if necessary in order to consider this other
|>|>|> document.
|>|>|> >
|>|>|> > Agreed.
|>|>|> >
|>|>|> > -d
|>|>|> >
|>|>|> >
|>|>|> > >
|>|>|> > >
|>|>|> > >
|>|>|> > > What do you think?
|>|>|> > >
|>|>|> > >
|>|>|> > >
|>|>|> > > 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
|
|
|________________________________
|
|Este mensaje se dirige exclusivamente a su destinatario. Puede consultar n=
uestra 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 r=
eceive email on the basis of
|the terms set out at:
|http://www.tid.es/ES/PAGINAS/disclaimer.aspx
|_______________________________________________
|tcmtf mailing list
|tcmtf@ietf.org
|https://www.ietf.org/mailman/listinfo/tcmtf

From jsaldana@unizar.es  Fri Jan 11 00:50:31 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E9E221F877B for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 00:50:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DoLYhr2-ZqYK for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 00:50:29 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 78D2321F8795 for <tcmtf@ietf.org>; Fri, 11 Jan 2013 00:50:28 -0800 (PST)
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 r0B8oKtI005887; Fri, 11 Jan 2013 09:50:20 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Michael Ramalho \(mramalho\)'" <mramalho@cisco.com>, "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>, <tcmtf@ietf.org>
References: <002901cdef1e$31a1b130$94e51390$@unizar.es> <F5EDC35DF914C1428C28E149F10463A2528959F6@EX10-MB2-MAD.hi.inet> <D21571530BF9644D9A443D6BD95B9103154BC655@xmb-rcd-x12.cisco.com>
In-Reply-To: <D21571530BF9644D9A443D6BD95B9103154BC655@xmb-rcd-x12.cisco.com>
Date: Fri, 11 Jan 2013 09:50:24 +0100
Organization: Universidad de Zaragoza
Message-ID: <003a01cdefd8$b2d06a70$18713f50$@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: AQHJXHPKpPlPIwpdtqJtXFRe3b1sDwILUyuWAoE+HQaYKJDQEA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
Subject: Re: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 08:50:31 -0000

Michael,

I think this discussion is getting more and more interesting. Thanks.

You talk about methods for identifying the different packets, and it is
interesting, since it would make things work really better: the =
multiplexer
would know which packets can and which ones can not be multiplexed.

One question here is that perhaps the developer of the application to be
multiplexed wouldn't want to add anything to its protocol. I mean, if I =
am
the network provider and I want to save bandwidth in my network, I only =
have
the packets as they have been sent by the final application.

So the question is: are you proposing that we should develop something
within TCMTF WG in order to classify packets? Perhaps this is too much,
since there will be other people thinking about traffic classification =
with
other objectives.

Perhaps a "natural" way could be widening the scope of draft (B), =
including
not only delay limits, but also currently existing traffic =
classification
methods which could be useful for selecting the packets to multiplex. =
Does
this sound well?

Jose

> -----Mensaje original-----
> De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com]
> Enviado el: jueves, 10 de enero de 2013 15:48
> Para: FERNANDO PASCUAL BLANCO; jsaldana@unizar.es; tcmtf@ietf.org
> Asunto: RE: [tcmtf] : New Version Notification for
draft-saldana-tsvwg-tcmtf-
> 04.txt
>=20
> All,
>=20
> I'll answer Fernando and Jose at the same time, with "MAR:" below.
>=20
> Michael Ramalho
>=20
> -----Original Message-----
> From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> Sent: Thursday, January 10, 2013 6:16 AM
> To: jsaldana@unizar.es; Michael Ramalho (mramalho); tcmtf@ietf.org
> Subject: Re: [tcmtf] : New Version Notification for =
draft-saldana-tsvwg-
> tcmtf-04.txt
>=20
> Hi Jose,
>=20
>         I fully agree with you. TCMTF module could be embedded within =
a
router
> or not, and the decision to apply TCMTF to a flow (and the way to =
signal
> that) or not is something that under my point of view is out of the =
scope
of
> drafts A and B.
>=20
> MAR: First of all, "we" defined drafts A and B ... we can define other
drafts or
> other working group charters/proposals. However ...
>=20
> MAR: I disagree ... I think this happens to be partially addressed in
draft B
> (http://www.ietf.org/id/draft-suznjevic-tsvwg-mtd-tcmtf-00.pdf ).
>=20
> <MAR:>
> Consider the following ... a potential TCMTF endpoint sees two small =
UDP
> packets ... and lets further assume that it cannot tell by inspection =
the
> applications the small packets belong to.
>=20
> One of the packets belong to a First Person Shooter (FPS) game (very =
low
> latency desired) and the other from my home thermostat (reporting my
> nominal house temperature to a service in the cloud).
>=20
> My home thermostat also previously sent metadata (a traffic class flow
> identifier) telling all hops on the path that my packet is relatively
delay
> insensitive (maybe via a STUN packet) ... and it doesn't mind if any
particular
> hop adds even 200 ms of per-hop delay.
>=20
> Wouldn't it make sense that TCMTF assumes my thermostat flow is a =
strong
> candidate and the FPS isn't a candidate unless it arrived
"just/immediately
> before" a TCMTF packet creation?
>=20
> The bottom line is that (deep) packet inspection will only get you so =
far.
> Indeed some VXI protocol designs are being modified so that they can =
be
> "more easily" identified by routers (by headers early in the packet
payloads)
> - until this point there was no effort to do so and it is very, very
difficult (in
> general) to determine a "delay tolerance" by simply looking at a
particular
> packet. Even more so with packet encryption ;-).
>=20
> When the "internet of things" is here ... we will have lots of small
packets ...
> the exact application where TCMTF has its strongest use case. And most =
of
> these small packets will have very loose delay bounds (long nominal
> reporting intervals or periodic keep-alives for firewalls/NATs/etc.).
> </MAR:>
>=20
> Once defined the core TCMTF functionality we can build things around =
it.
>=20
> MAR: True. But equally true is that if you DON'T specify useful =
criteria
on how
> you classify candidate TCMTF flows ... it may not be seriously =
considered.
>=20
> MAR: A good example is the "voice communications" item in Table 1 of =
draft
> B. If the RTP voice flow was a push-to-talk flow ... then I could =
agree to
up to
> a 80ms mux delay. For a normal voice call, 80ms is WAY, WAY too much =
delay
> (most VoIP calls use ptime of 20ms for a reason!). If you knew a =
packet
was a
> voice packet (via RTP inspection) ... but additionally knew it =
belonged
for a
> push-to-talk service ... you could TCMTF it. So you really need to =
have
more
> knowledge than just "it is a packet of G.722.2 voice" to make a =
decision.
As an
> aside, the reference for Table 1 (of draft B) is not rigorous enough =
for
the use
> claimed (you can find hundreds of references that would disagree with =
the
> 80 ms maximum recommendation).
>=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
>=20
>=20
>=20
> On 10/01/13 11:35, "Jose Saldana" <jsaldana@unizar.es> wrote:
>=20
> >Hi, Michael.
> >
> >I have been thinking about your mail. The question is how to identify
> >the flows. We can use two examples:
> >
> >Case 1: You are a network operator and you have an agreement with a
> >networked gaming company. So you are trying to merge flows belonging =
to
> >the same game, and send them multiplexed to the demux located at the
> >game company. So your network has to be able to identify those flows
> >and send them to the mux. So you would need a sort of "Deep Packet
> >Inspection", I think.
>=20
> MAR: As per my reply to Fernando above, DPI will only get you so far.
There
> are a lot of applications using UDP in which you cannot make a =
definitive
> association between the packet and a particular service.
>=20
> MAR: However, when TCMTF is used on a "high-enough" speed link, the
> delay can be arbitrarily small. Thus I think some TCMTF guidance is
primarily
> needed for low-speed links (i.e., links where the mux delay could be =
in
> excess of some reasonable bound, like 5 ms maximum).
>=20
> >One solution: all the packets with a certain destination IP go to the
> >mux. The servers of the game are clearly identified by their IPs.
>=20
> MAR: As an aside, if the network operator had such an agreement ... =
they
> would know a priori something about the aggregate flows to the =
networked
> game company. They could also determine this from metadata without any
> "special arrangement".
>=20
> MAR: However, even this is not general enough. We already have
> applications that for a particular source and destination IP =
address/port
have
> different QoS treatment (e.g., SVC video - different packets have
different
> QoS requirements for the same flow).
>=20
> MAR: I think capabilities negotiation (another thread) should include =
a
notion
> of "what types of flows" to consider TCMTFing. Without it, I think =
TCMTF
> could make some poor decisions (not on efficiency, the dimension upon
> which it always wins - but on delay) which may, in turn, create =
impedance
for
> its acceptance.
>=20
> >
> >Case 2: But what happens if you only want to save bandwidth inside =
your
> >network?: you have to compress traffic before traversing a certain =
path
> >with scarce bandwidth. So you will have to identify "flows" of =
packets
> >with a cadence, and some common characteristics. In this case, you =
may
> >need to use "signature analysis" or something, in order to know the
> >game genre, etc, and thus being able to set a maximum multiplexing
> >period, for example.
> >
> >But I don't know if the question of identifying the flows has to be
> >solved by TCMTF.
>=20
> MAR: I was not arguing for "solving" the flow identification problem =
at
this
> stage ... just mentioning it now would make sense ... and that =
techniques
> such as exploiting any metadata information for the flow and/or =
signature
> analysis could be used for the TCMTF determination. Eventually, I =
think we
> need to mention how capabilities negotiation can include flow types =
too.
>=20
> >There should be other machine that sends to the mux only the packets
> >that have to be multiplexed.... or not?
> >
> >Jose
> >
> >> -----Mensaje original-----
> >> De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com]  Enviado
> >>el: mi=E9rcoles, 09 de enero de 2013 18:05
> >> Para: jsaldana@unizar.es; tcmtf@ietf.org
> >> Asunto: RE: [tcmtf] : New Version Notification for
> >>draft-saldana-tsvwg-tcmtf-
> >> 04.txt
> >>
> >> Jose, et. al.,
> >>
> >> Sorry for being so quiet recently on this list ... I am just
> >>beginning to become  unburied from work late last year!
> >>
> >> You mention FPS and MMORPGs in the draft ... but has any detailed
> >>thought  about how TCMTF might identify which flows it should NOT
> >>attempt to  compress?
> >>
> >> Considering "the Internet of things" (where virtually every device =
is
> >>connected via IP) ... we can expect a lot of small packets ... but =
not
> >>necessarily know if we should compress them or not (e.g., FPS =
packets)
> >>... or  what the delay bounds on the compression should be.
> >>
> >> Should we mention that flows that signal their own traffic class
> >>(e.g., using  "Metadata" describing the flow) is a good thing to
> >>differentiate on?
> >>Should
> >> we suggest signature analysis (a probabilistic guess for the
> >>application based  on its time-domain signature characteristics) =
might
> >>also be of utility?
> >>
> >> Being silent on this point may lessen the attractiveness to design
> >>using it.
> >>
> >> Sorry if this point has been raised before.
> >>
> >> Best,
> >>
> >> Michael Ramalho
> >>
> >> -----Original Message-----
> >> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
> >>Behalf  Of Jose Saldana
> >> Sent: Wednesday, January 09, 2013 4:29 AM
> >> To: tcmtf@ietf.org
> >> Subject: [tcmtf] RV: New Version Notification for
> >>draft-saldana-tsvwg-tcmtf-
> >> 04.txt
> >>
> >> I have just uploaded a new version of the tcmtf draft.
> >>
> >> Jose
> >>
> >> > -----Mensaje original-----
> >> > De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> >> > Enviado
> >> > el: mi=E9rcoles, 09 de enero de 2013 10:25
> >> > Para: jsaldana@unizar.es
> >> > CC: mperumal@cisco.com; navajas@unizar.es; dwing@cisco.com;
> >> fpb@tid.es
> >> > Asunto: New Version Notification for
> >> > draft-saldana-tsvwg-tcmtf-04.txt
> >> >
> >> >
> >> > A new version of I-D, draft-saldana-tsvwg-tcmtf-04.txt has been
> >> > successfully submitted by Jose Saldana and posted to the IETF
> >>repository.
> >> >
> >> > Filename:   draft-saldana-tsvwg-tcmtf
> >> > Revision:   04
> >> > Title:              Tunneling Compressed Multiplexed Traffic =
Flows
(TCMTF)
> >> > Creation date:      2013-01-09
> >> > WG ID:              Individual Submission
> >> > Number of pages: 19
> >> > URL:
> >>http://www.ietf.org/internet-drafts/draft-saldana-tsvwg-tcmtf-
> >> > 04.txt
> >> > Status:
> >>http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf
> >> > Htmlized:
> >>http://tools.ietf.org/html/draft-saldana-tsvwg-tcmtf-04
> >> > Diff:
> >>http://www.ietf.org/rfcdiff?url2=3Ddraft-saldana-tsvwg-tcmtf-04
> >> >
> >> > Abstract:
> >> >    This document describes a method to improve the bandwidth
> >>utilization
> >> >    of network paths that carry multiple streams in parallel =
sharing a
> >> >    common path.  The method combines standard protocols that =
provide
> >> >    compression, multiplexing, and tunneling over a network path =
for
> >>the
> >> >    purpose of reducing the bandwidth used when multiple streams =
are
> >> >    carried over that path.
> >> >
> >> >
> >> >
> >> >
> >> > The IETF Secretariat
> >>
> >>
> >> _______________________________________________
> >> 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=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


From Mirko.Suznjevic@fer.hr  Fri Jan 11 02:07:25 2013
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 7A66021F8793 for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 02:07:25 -0800 (PST)
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 wwq5InVR7mdw for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 02:07:24 -0800 (PST)
Received: from mail.zvne.fer.hr (mail.zvne.fer.hr [161.53.66.5]) by ietfa.amsl.com (Postfix) with ESMTP id 992F221F8610 for <tcmtf@ietf.org>; Fri, 11 Jan 2013 02:07:22 -0800 (PST)
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.318.4; Fri, 11 Jan 2013 11:07:19 +0100
Received: from sluga.fer.hr ([161.53.66.244]) by munja.zvne.fer.hr with Microsoft SMTPSVC(6.0.3790.4675);	 Fri, 11 Jan 2013 11:06:45 +0100
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, 11 Jan 2013 11:06:42 +0100
Message-ID: <A3179A2C9AAEE647BE70AC4C7881D5FB01775F0F@sluga.fer.hr>
In-Reply-To: <003a01cdefd8$b2d06a70$18713f50$@unizar.es>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
Thread-Index: AQHJXHPKpPlPIwpdtqJtXFRe3b1sDwILUyuWAoE+HQaYKJDQEIAAFLeA
References: <002901cdef1e$31a1b130$94e51390$@unizar.es> <F5EDC35DF914C1428C28E149F10463A2528959F6@EX10-MB2-MAD.hi.inet> <D21571530BF9644D9A443D6BD95B9103154BC655@xmb-rcd-x12.cisco.com> <003a01cdefd8$b2d06a70$18713f50$@unizar.es>
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: <jsaldana@unizar.es>, "Michael Ramalho (mramalho)" <mramalho@cisco.com>, FERNANDO PASCUAL BLANCO <fpb@tid.es>, <tcmtf@ietf.org>
X-OriginalArrivalTime: 11 Jan 2013 10:06:45.0408 (UTC) FILETIME=[5C9DEA00:01CDEFE3]
Subject: Re: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 10:07:25 -0000

Hello all,
I think there is no need to develop something for traffic classification =
in the scope of TCMTF WG. There is a large research community doing =
traffic classification and some of the already developed techniques can =
be applied for our need. It may be feasible to present an overview of =
techniques which could be used by TCMTF in draft B.
Mirko

-----Original Message-----
From: Jose Saldana [mailto:jsaldana@unizar.es]=20
Sent: Friday, January 11, 2013 9:50 AM
To: 'Michael Ramalho (mramalho)'; 'FERNANDO PASCUAL BLANCO'; =
tcmtf@ietf.org
Cc: Mirko Su=BEnjevi=E6
Subject: RE: [tcmtf] : New Version Notification for =
draft-saldana-tsvwg-tcmtf-04.txt

Michael,

I think this discussion is getting more and more interesting. Thanks.

You talk about methods for identifying the different packets, and it is =
interesting, since it would make things work really better: the =
multiplexer would know which packets can and which ones can not be =
multiplexed.

One question here is that perhaps the developer of the application to be =
multiplexed wouldn't want to add anything to its protocol. I mean, if I =
am the network provider and I want to save bandwidth in my network, I =
only have the packets as they have been sent by the final application.

So the question is: are you proposing that we should develop something =
within TCMTF WG in order to classify packets? Perhaps this is too much, =
since there will be other people thinking about traffic classification =
with other objectives.

Perhaps a "natural" way could be widening the scope of draft (B), =
including not only delay limits, but also currently existing traffic =
classification methods which could be useful for selecting the packets =
to multiplex. Does this sound well?

Jose

> -----Mensaje original-----
> De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com] Enviado el: =

> jueves, 10 de enero de 2013 15:48
> Para: FERNANDO PASCUAL BLANCO; jsaldana@unizar.es; tcmtf@ietf.org
> Asunto: RE: [tcmtf] : New Version Notification for
draft-saldana-tsvwg-tcmtf-
> 04.txt
>=20
> All,
>=20
> I'll answer Fernando and Jose at the same time, with "MAR:" below.
>=20
> Michael Ramalho
>=20
> -----Original Message-----
> From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> Sent: Thursday, January 10, 2013 6:16 AM
> To: jsaldana@unizar.es; Michael Ramalho (mramalho); tcmtf@ietf.org
> Subject: Re: [tcmtf] : New Version Notification for=20
> draft-saldana-tsvwg- tcmtf-04.txt
>=20
> Hi Jose,
>=20
>         I fully agree with you. TCMTF module could be embedded within=20
> a
router
> or not, and the decision to apply TCMTF to a flow (and the way to=20
> signal
> that) or not is something that under my point of view is out of the=20
> scope
of
> drafts A and B.
>=20
> MAR: First of all, "we" defined drafts A and B ... we can define other
drafts or
> other working group charters/proposals. However ...
>=20
> MAR: I disagree ... I think this happens to be partially addressed in
draft B
> (http://www.ietf.org/id/draft-suznjevic-tsvwg-mtd-tcmtf-00.pdf ).
>=20
> <MAR:>
> Consider the following ... a potential TCMTF endpoint sees two small=20
> UDP packets ... and lets further assume that it cannot tell by=20
> inspection the applications the small packets belong to.
>=20
> One of the packets belong to a First Person Shooter (FPS) game (very=20
> low latency desired) and the other from my home thermostat (reporting=20
> my nominal house temperature to a service in the cloud).
>=20
> My home thermostat also previously sent metadata (a traffic class flow
> identifier) telling all hops on the path that my packet is relatively
delay
> insensitive (maybe via a STUN packet) ... and it doesn't mind if any
particular
> hop adds even 200 ms of per-hop delay.
>=20
> Wouldn't it make sense that TCMTF assumes my thermostat flow is a=20
> strong candidate and the FPS isn't a candidate unless it arrived
"just/immediately
> before" a TCMTF packet creation?
>=20
> The bottom line is that (deep) packet inspection will only get you so =
far.
> Indeed some VXI protocol designs are being modified so that they can=20
> be "more easily" identified by routers (by headers early in the packet
payloads)
> - until this point there was no effort to do so and it is very, very
difficult (in
> general) to determine a "delay tolerance" by simply looking at a
particular
> packet. Even more so with packet encryption ;-).
>=20
> When the "internet of things" is here ... we will have lots of small
packets ...
> the exact application where TCMTF has its strongest use case. And most =

> of these small packets will have very loose delay bounds (long nominal =

> reporting intervals or periodic keep-alives for firewalls/NATs/etc.).
> </MAR:>
>=20
> Once defined the core TCMTF functionality we can build things around =
it.
>=20
> MAR: True. But equally true is that if you DON'T specify useful=20
> criteria
on how
> you classify candidate TCMTF flows ... it may not be seriously =
considered.
>=20
> MAR: A good example is the "voice communications" item in Table 1 of=20
> draft B. If the RTP voice flow was a push-to-talk flow ... then I=20
> could agree to
up to
> a 80ms mux delay. For a normal voice call, 80ms is WAY, WAY too much=20
> delay (most VoIP calls use ptime of 20ms for a reason!). If you knew a =

> packet
was a
> voice packet (via RTP inspection) ... but additionally knew it=20
> belonged
for a
> push-to-talk service ... you could TCMTF it. So you really need to=20
> have
more
> knowledge than just "it is a packet of G.722.2 voice" to make a =
decision.
As an
> aside, the reference for Table 1 (of draft B) is not rigorous enough=20
> for
the use
> claimed (you can find hundreds of references that would disagree with=20
> the
> 80 ms maximum recommendation).
>=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
>=20
>=20
>=20
> On 10/01/13 11:35, "Jose Saldana" <jsaldana@unizar.es> wrote:
>=20
> >Hi, Michael.
> >
> >I have been thinking about your mail. The question is how to identify =

> >the flows. We can use two examples:
> >
> >Case 1: You are a network operator and you have an agreement with a=20
> >networked gaming company. So you are trying to merge flows belonging=20
> >to the same game, and send them multiplexed to the demux located at=20
> >the game company. So your network has to be able to identify those=20
> >flows and send them to the mux. So you would need a sort of "Deep=20
> >Packet Inspection", I think.
>=20
> MAR: As per my reply to Fernando above, DPI will only get you so far.
There
> are a lot of applications using UDP in which you cannot make a=20
> definitive association between the packet and a particular service.
>=20
> MAR: However, when TCMTF is used on a "high-enough" speed link, the=20
> delay can be arbitrarily small. Thus I think some TCMTF guidance is
primarily
> needed for low-speed links (i.e., links where the mux delay could be=20
> in excess of some reasonable bound, like 5 ms maximum).
>=20
> >One solution: all the packets with a certain destination IP go to the =

> >mux. The servers of the game are clearly identified by their IPs.
>=20
> MAR: As an aside, if the network operator had such an agreement ...=20
> they would know a priori something about the aggregate flows to the=20
> networked game company. They could also determine this from metadata=20
> without any "special arrangement".
>=20
> MAR: However, even this is not general enough. We already have=20
> applications that for a particular source and destination IP=20
> address/port
have
> different QoS treatment (e.g., SVC video - different packets have
different
> QoS requirements for the same flow).
>=20
> MAR: I think capabilities negotiation (another thread) should include=20
> a
notion
> of "what types of flows" to consider TCMTFing. Without it, I think=20
> TCMTF could make some poor decisions (not on efficiency, the dimension =

> upon which it always wins - but on delay) which may, in turn, create=20
> impedance
for
> its acceptance.
>=20
> >
> >Case 2: But what happens if you only want to save bandwidth inside=20
> >your
> >network?: you have to compress traffic before traversing a certain=20
> >path with scarce bandwidth. So you will have to identify "flows" of=20
> >packets with a cadence, and some common characteristics. In this=20
> >case, you may need to use "signature analysis" or something, in order =

> >to know the game genre, etc, and thus being able to set a maximum=20
> >multiplexing period, for example.
> >
> >But I don't know if the question of identifying the flows has to be=20
> >solved by TCMTF.
>=20
> MAR: I was not arguing for "solving" the flow identification problem=20
> at
this
> stage ... just mentioning it now would make sense ... and that=20
> techniques such as exploiting any metadata information for the flow=20
> and/or signature analysis could be used for the TCMTF determination.=20
> Eventually, I think we need to mention how capabilities negotiation =
can include flow types too.
>=20
> >There should be other machine that sends to the mux only the packets=20
> >that have to be multiplexed.... or not?
> >
> >Jose
> >
> >> -----Mensaje original-----
> >> De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com]  Enviado
> >>el: mi=E9rcoles, 09 de enero de 2013 18:05
> >> Para: jsaldana@unizar.es; tcmtf@ietf.org
> >> Asunto: RE: [tcmtf] : New Version Notification for
> >>draft-saldana-tsvwg-tcmtf-
> >> 04.txt
> >>
> >> Jose, et. al.,
> >>
> >> Sorry for being so quiet recently on this list ... I am just=20
> >>beginning to become  unburied from work late last year!
> >>
> >> You mention FPS and MMORPGs in the draft ... but has any detailed=20
> >>thought  about how TCMTF might identify which flows it should NOT=20
> >>attempt to  compress?
> >>
> >> Considering "the Internet of things" (where virtually every device=20
> >>is connected via IP) ... we can expect a lot of small packets ...=20
> >>but not necessarily know if we should compress them or not (e.g.,=20
> >>FPS packets) ... or  what the delay bounds on the compression should =
be.
> >>
> >> Should we mention that flows that signal their own traffic class=20
> >>(e.g., using  "Metadata" describing the flow) is a good thing to=20
> >>differentiate on?
> >>Should
> >> we suggest signature analysis (a probabilistic guess for the=20
> >>application based  on its time-domain signature characteristics)=20
> >>might also be of utility?
> >>
> >> Being silent on this point may lessen the attractiveness to design=20
> >>using it.
> >>
> >> Sorry if this point has been raised before.
> >>
> >> Best,
> >>
> >> Michael Ramalho
> >>
> >> -----Original Message-----
> >> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On=20
> >>Behalf  Of Jose Saldana
> >> Sent: Wednesday, January 09, 2013 4:29 AM
> >> To: tcmtf@ietf.org
> >> Subject: [tcmtf] RV: New Version Notification for
> >>draft-saldana-tsvwg-tcmtf-
> >> 04.txt
> >>
> >> I have just uploaded a new version of the tcmtf draft.
> >>
> >> Jose
> >>
> >> > -----Mensaje original-----
> >> > De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
> >> > Enviado
> >> > el: mi=E9rcoles, 09 de enero de 2013 10:25
> >> > Para: jsaldana@unizar.es
> >> > CC: mperumal@cisco.com; navajas@unizar.es; dwing@cisco.com;
> >> fpb@tid.es
> >> > Asunto: New Version Notification for=20
> >> > draft-saldana-tsvwg-tcmtf-04.txt
> >> >
> >> >
> >> > A new version of I-D, draft-saldana-tsvwg-tcmtf-04.txt has been=20
> >> > successfully submitted by Jose Saldana and posted to the IETF
> >>repository.
> >> >
> >> > Filename:   draft-saldana-tsvwg-tcmtf
> >> > Revision:   04
> >> > Title:              Tunneling Compressed Multiplexed Traffic =
Flows
(TCMTF)
> >> > Creation date:      2013-01-09
> >> > WG ID:              Individual Submission
> >> > Number of pages: 19
> >> > URL:
> >>http://www.ietf.org/internet-drafts/draft-saldana-tsvwg-tcmtf-
> >> > 04.txt
> >> > Status:
> >>http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf
> >> > Htmlized:
> >>http://tools.ietf.org/html/draft-saldana-tsvwg-tcmtf-04
> >> > Diff:
> >>http://www.ietf.org/rfcdiff?url2=3Ddraft-saldana-tsvwg-tcmtf-04
> >> >
> >> > Abstract:
> >> >    This document describes a method to improve the bandwidth
> >>utilization
> >> >    of network paths that carry multiple streams in parallel =
sharing a
> >> >    common path.  The method combines standard protocols that =
provide
> >> >    compression, multiplexing, and tunneling over a network path=20
> >> > for
> >>the
> >> >    purpose of reducing the bandwidth used when multiple streams =
are
> >> >    carried over that path.
> >> >
> >> >
> >> >
> >> >
> >> > The IETF Secretariat
> >>
> >>
> >> _______________________________________________
> >> 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=20
> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico=20
> en el enlace situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send=20
> and receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx


From ggx@gigix.net  Fri Jan 11 02:45:53 2013
Return-Path: <ggx@gigix.net>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A40B21F88E6 for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 02:45:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.711
X-Spam-Level: 
X-Spam-Status: No, score=-1.711 tagged_above=-999 required=5 tests=[AWL=-1.260, BAYES_00=-2.599, HELO_DYNAMIC_DHCP=1.398, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, RDNS_DYNAMIC=0.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 ZIYxNZXgY1vm for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 02:45:52 -0800 (PST)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id CEF1A21F88E1 for <tcmtf@ietf.org>; Fri, 11 Jan 2013 02:45:51 -0800 (PST)
Received: by mail-wi0-f170.google.com with SMTP id hq7so1885523wib.3 for <tcmtf@ietf.org>; Fri, 11 Jan 2013 02:45:51 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received: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=nGZaLmc3ay8ZXNbXk4s2nj3MH3EzPHPAT1KqtJp2Tkc=; b=QgL2r2xsIy9bGIIOSUpibeNlLbghRSsBJszJ4IiYgm2d2C2ZFdq0lw+LPaNsA0ipQA pAhcYL8lSE+LJ4ynQJF3OUihuHuCgM7oizRvygW7SJKIl0XEMSLo3DM5OopNNfje37Wt QK2xLj4qF7iAiPrxfZ4eN06O21zAdWW7Z3QSOhzt9U7bXOJKAN69s/8v0883WBgCNN4i OpOrgDus3iCmUg5jrBCXZYxqzR9WnfcX5BHgD/mA8nqg/d7yVwyUDfx4+VOE9ydxGkJF hnbaDC8Xo7fvdU7cNUOlh4mjipuAf9Iv7mz3QgiuvLuM9h5FgA2mbZBpXRP2of+RpIo+ IMtQ==
X-Received: by 10.180.33.202 with SMTP id t10mr14662588wii.3.1357901150921; Fri, 11 Jan 2013 02:45:50 -0800 (PST)
Received: from dhcp164-04.enst.fr (dhcp164-04.enst.fr. [137.194.165.4]) by mx.google.com with ESMTPS id e6sm6631551wiz.1.2013.01.11.02.45.49 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Jan 2013 02:45:50 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-2
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <A3179A2C9AAEE647BE70AC4C7881D5FB01775F0F@sluga.fer.hr>
Date: Fri, 11 Jan 2013 11:45:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4734F2B7-003C-4BB5-B69A-E089DE6085C7@gigix.net>
References: <002901cdef1e$31a1b130$94e51390$@unizar.es> <F5EDC35DF914C1428C28E149F10463A2528959F6@EX10-MB2-MAD.hi.inet> <D21571530BF9644D9A443D6BD95B9103154BC655@xmb-rcd-x12.cisco.com> <003a01cdefd8$b2d06a70$18713f50$@unizar.es> <A3179A2C9AAEE647BE70AC4C7881D5FB01775F0F@sluga.fer.hr>
To: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQnxqib93KIepEgQyR3hs6ymXfHaYRp6rSq7KAw5qSAdbsi3vJ4kg6JPYu8y5a8Pl16jTSdL
Cc: tcmtf@ietf.org, FERNANDO PASCUAL BLANCO <fpb@tid.es>, "Michael Ramalho \(mramalho\)" <mramalho@cisco.com>, jsaldana@unizar.es
Subject: Re: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 10:45:53 -0000

On 11 Jan. 2013, at 11:06 , Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr> =
wrote:

> Hello all,
> I think there is no need to develop something for traffic =
classification in the scope of TCMTF WG. There is a large research =
community doing traffic classification and some of the already developed =
techniques can be applied for our need. It may be feasible to present an =
overview of techniques which could be used by TCMTF in draft B.

+1

There are tons of classification methods out there, developing a new one =
does not look very useful to me.

Luigi


> Mirko
>=20
> -----Original Message-----
> From: Jose Saldana [mailto:jsaldana@unizar.es]=20
> Sent: Friday, January 11, 2013 9:50 AM
> To: 'Michael Ramalho (mramalho)'; 'FERNANDO PASCUAL BLANCO'; =
tcmtf@ietf.org
> Cc: Mirko Su=BEnjevi=E6
> Subject: RE: [tcmtf] : New Version Notification for =
draft-saldana-tsvwg-tcmtf-04.txt
>=20
> Michael,
>=20
> I think this discussion is getting more and more interesting. Thanks.
>=20
> You talk about methods for identifying the different packets, and it =
is interesting, since it would make things work really better: the =
multiplexer would know which packets can and which ones can not be =
multiplexed.
>=20
> One question here is that perhaps the developer of the application to =
be multiplexed wouldn't want to add anything to its protocol. I mean, if =
I am the network provider and I want to save bandwidth in my network, I =
only have the packets as they have been sent by the final application.
>=20
> So the question is: are you proposing that we should develop something =
within TCMTF WG in order to classify packets? Perhaps this is too much, =
since there will be other people thinking about traffic classification =
with other objectives.
>=20
> Perhaps a "natural" way could be widening the scope of draft (B), =
including not only delay limits, but also currently existing traffic =
classification methods which could be useful for selecting the packets =
to multiplex. Does this sound well?
>=20
> Jose
>=20
>> -----Mensaje original-----
>> De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com] Enviado =
el:=20
>> jueves, 10 de enero de 2013 15:48
>> Para: FERNANDO PASCUAL BLANCO; jsaldana@unizar.es; tcmtf@ietf.org
>> Asunto: RE: [tcmtf] : New Version Notification for
> draft-saldana-tsvwg-tcmtf-
>> 04.txt
>>=20
>> All,
>>=20
>> I'll answer Fernando and Jose at the same time, with "MAR:" below.
>>=20
>> Michael Ramalho
>>=20
>> -----Original Message-----
>> From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>> Sent: Thursday, January 10, 2013 6:16 AM
>> To: jsaldana@unizar.es; Michael Ramalho (mramalho); tcmtf@ietf.org
>> Subject: Re: [tcmtf] : New Version Notification for=20
>> draft-saldana-tsvwg- tcmtf-04.txt
>>=20
>> Hi Jose,
>>=20
>>        I fully agree with you. TCMTF module could be embedded within=20=

>> a
> router
>> or not, and the decision to apply TCMTF to a flow (and the way to=20
>> signal
>> that) or not is something that under my point of view is out of the=20=

>> scope
> of
>> drafts A and B.
>>=20
>> MAR: First of all, "we" defined drafts A and B ... we can define =
other
> drafts or
>> other working group charters/proposals. However ...
>>=20
>> MAR: I disagree ... I think this happens to be partially addressed in
> draft B
>> (http://www.ietf.org/id/draft-suznjevic-tsvwg-mtd-tcmtf-00.pdf ).
>>=20
>> <MAR:>
>> Consider the following ... a potential TCMTF endpoint sees two small=20=

>> UDP packets ... and lets further assume that it cannot tell by=20
>> inspection the applications the small packets belong to.
>>=20
>> One of the packets belong to a First Person Shooter (FPS) game (very=20=

>> low latency desired) and the other from my home thermostat (reporting=20=

>> my nominal house temperature to a service in the cloud).
>>=20
>> My home thermostat also previously sent metadata (a traffic class =
flow
>> identifier) telling all hops on the path that my packet is relatively
> delay
>> insensitive (maybe via a STUN packet) ... and it doesn't mind if any
> particular
>> hop adds even 200 ms of per-hop delay.
>>=20
>> Wouldn't it make sense that TCMTF assumes my thermostat flow is a=20
>> strong candidate and the FPS isn't a candidate unless it arrived
> "just/immediately
>> before" a TCMTF packet creation?
>>=20
>> The bottom line is that (deep) packet inspection will only get you so =
far.
>> Indeed some VXI protocol designs are being modified so that they can=20=

>> be "more easily" identified by routers (by headers early in the =
packet
> payloads)
>> - until this point there was no effort to do so and it is very, very
> difficult (in
>> general) to determine a "delay tolerance" by simply looking at a
> particular
>> packet. Even more so with packet encryption ;-).
>>=20
>> When the "internet of things" is here ... we will have lots of small
> packets ...
>> the exact application where TCMTF has its strongest use case. And =
most=20
>> of these small packets will have very loose delay bounds (long =
nominal=20
>> reporting intervals or periodic keep-alives for firewalls/NATs/etc.).
>> </MAR:>
>>=20
>> Once defined the core TCMTF functionality we can build things around =
it.
>>=20
>> MAR: True. But equally true is that if you DON'T specify useful=20
>> criteria
> on how
>> you classify candidate TCMTF flows ... it may not be seriously =
considered.
>>=20
>> MAR: A good example is the "voice communications" item in Table 1 of=20=

>> draft B. If the RTP voice flow was a push-to-talk flow ... then I=20
>> could agree to
> up to
>> a 80ms mux delay. For a normal voice call, 80ms is WAY, WAY too much=20=

>> delay (most VoIP calls use ptime of 20ms for a reason!). If you knew =
a=20
>> packet
> was a
>> voice packet (via RTP inspection) ... but additionally knew it=20
>> belonged
> for a
>> push-to-talk service ... you could TCMTF it. So you really need to=20
>> have
> more
>> knowledge than just "it is a packet of G.722.2 voice" to make a =
decision.
> As an
>> aside, the reference for Table 1 (of draft B) is not rigorous enough=20=

>> for
> the use
>> claimed (you can find hundreds of references that would disagree with=20=

>> the
>> 80 ms maximum recommendation).
>>=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
>>=20
>>=20
>>=20
>> On 10/01/13 11:35, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>=20
>>> Hi, Michael.
>>>=20
>>> I have been thinking about your mail. The question is how to =
identify=20
>>> the flows. We can use two examples:
>>>=20
>>> Case 1: You are a network operator and you have an agreement with a=20=

>>> networked gaming company. So you are trying to merge flows belonging=20=

>>> to the same game, and send them multiplexed to the demux located at=20=

>>> the game company. So your network has to be able to identify those=20=

>>> flows and send them to the mux. So you would need a sort of "Deep=20
>>> Packet Inspection", I think.
>>=20
>> MAR: As per my reply to Fernando above, DPI will only get you so far.
> There
>> are a lot of applications using UDP in which you cannot make a=20
>> definitive association between the packet and a particular service.
>>=20
>> MAR: However, when TCMTF is used on a "high-enough" speed link, the=20=

>> delay can be arbitrarily small. Thus I think some TCMTF guidance is
> primarily
>> needed for low-speed links (i.e., links where the mux delay could be=20=

>> in excess of some reasonable bound, like 5 ms maximum).
>>=20
>>> One solution: all the packets with a certain destination IP go to =
the=20
>>> mux. The servers of the game are clearly identified by their IPs.
>>=20
>> MAR: As an aside, if the network operator had such an agreement ...=20=

>> they would know a priori something about the aggregate flows to the=20=

>> networked game company. They could also determine this from metadata=20=

>> without any "special arrangement".
>>=20
>> MAR: However, even this is not general enough. We already have=20
>> applications that for a particular source and destination IP=20
>> address/port
> have
>> different QoS treatment (e.g., SVC video - different packets have
> different
>> QoS requirements for the same flow).
>>=20
>> MAR: I think capabilities negotiation (another thread) should include=20=

>> a
> notion
>> of "what types of flows" to consider TCMTFing. Without it, I think=20
>> TCMTF could make some poor decisions (not on efficiency, the =
dimension=20
>> upon which it always wins - but on delay) which may, in turn, create=20=

>> impedance
> for
>> its acceptance.
>>=20
>>>=20
>>> Case 2: But what happens if you only want to save bandwidth inside=20=

>>> your
>>> network?: you have to compress traffic before traversing a certain=20=

>>> path with scarce bandwidth. So you will have to identify "flows" of=20=

>>> packets with a cadence, and some common characteristics. In this=20
>>> case, you may need to use "signature analysis" or something, in =
order=20
>>> to know the game genre, etc, and thus being able to set a maximum=20
>>> multiplexing period, for example.
>>>=20
>>> But I don't know if the question of identifying the flows has to be=20=

>>> solved by TCMTF.
>>=20
>> MAR: I was not arguing for "solving" the flow identification problem=20=

>> at
> this
>> stage ... just mentioning it now would make sense ... and that=20
>> techniques such as exploiting any metadata information for the flow=20=

>> and/or signature analysis could be used for the TCMTF determination.=20=

>> Eventually, I think we need to mention how capabilities negotiation =
can include flow types too.
>>=20
>>> There should be other machine that sends to the mux only the packets=20=

>>> that have to be multiplexed.... or not?
>>>=20
>>> Jose
>>>=20
>>>> -----Mensaje original-----
>>>> De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com]  Enviado
>>>> el: mi=E9rcoles, 09 de enero de 2013 18:05
>>>> Para: jsaldana@unizar.es; tcmtf@ietf.org
>>>> Asunto: RE: [tcmtf] : New Version Notification for
>>>> draft-saldana-tsvwg-tcmtf-
>>>> 04.txt
>>>>=20
>>>> Jose, et. al.,
>>>>=20
>>>> Sorry for being so quiet recently on this list ... I am just=20
>>>> beginning to become  unburied from work late last year!
>>>>=20
>>>> You mention FPS and MMORPGs in the draft ... but has any detailed=20=

>>>> thought  about how TCMTF might identify which flows it should NOT=20=

>>>> attempt to  compress?
>>>>=20
>>>> Considering "the Internet of things" (where virtually every device=20=

>>>> is connected via IP) ... we can expect a lot of small packets ...=20=

>>>> but not necessarily know if we should compress them or not (e.g.,=20=

>>>> FPS packets) ... or  what the delay bounds on the compression =
should be.
>>>>=20
>>>> Should we mention that flows that signal their own traffic class=20
>>>> (e.g., using  "Metadata" describing the flow) is a good thing to=20
>>>> differentiate on?
>>>> Should
>>>> we suggest signature analysis (a probabilistic guess for the=20
>>>> application based  on its time-domain signature characteristics)=20
>>>> might also be of utility?
>>>>=20
>>>> Being silent on this point may lessen the attractiveness to design=20=

>>>> using it.
>>>>=20
>>>> Sorry if this point has been raised before.
>>>>=20
>>>> Best,
>>>>=20
>>>> Michael Ramalho
>>>>=20
>>>> -----Original Message-----
>>>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On=20
>>>> Behalf  Of Jose Saldana
>>>> Sent: Wednesday, January 09, 2013 4:29 AM
>>>> To: tcmtf@ietf.org
>>>> Subject: [tcmtf] RV: New Version Notification for
>>>> draft-saldana-tsvwg-tcmtf-
>>>> 04.txt
>>>>=20
>>>> I have just uploaded a new version of the tcmtf draft.
>>>>=20
>>>> Jose
>>>>=20
>>>>> -----Mensaje original-----
>>>>> De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
>>>>> Enviado
>>>>> el: mi=E9rcoles, 09 de enero de 2013 10:25
>>>>> Para: jsaldana@unizar.es
>>>>> CC: mperumal@cisco.com; navajas@unizar.es; dwing@cisco.com;
>>>> fpb@tid.es
>>>>> Asunto: New Version Notification for=20
>>>>> draft-saldana-tsvwg-tcmtf-04.txt
>>>>>=20
>>>>>=20
>>>>> A new version of I-D, draft-saldana-tsvwg-tcmtf-04.txt has been=20
>>>>> successfully submitted by Jose Saldana and posted to the IETF
>>>> repository.
>>>>>=20
>>>>> Filename:   draft-saldana-tsvwg-tcmtf
>>>>> Revision:   04
>>>>> Title:              Tunneling Compressed Multiplexed Traffic Flows
> (TCMTF)
>>>>> Creation date:      2013-01-09
>>>>> WG ID:              Individual Submission
>>>>> Number of pages: 19
>>>>> URL:
>>>> http://www.ietf.org/internet-drafts/draft-saldana-tsvwg-tcmtf-
>>>>> 04.txt
>>>>> Status:
>>>> http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf
>>>>> Htmlized:
>>>> http://tools.ietf.org/html/draft-saldana-tsvwg-tcmtf-04
>>>>> Diff:
>>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-saldana-tsvwg-tcmtf-04
>>>>>=20
>>>>> Abstract:
>>>>>   This document describes a method to improve the bandwidth
>>>> utilization
>>>>>   of network paths that carry multiple streams in parallel sharing =
a
>>>>>   common path.  The method combines standard protocols that =
provide
>>>>>   compression, multiplexing, and tunneling over a network path=20
>>>>> for
>>>> the
>>>>>   purpose of reducing the bandwidth used when multiple streams are
>>>>>   carried over that path.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> The IETF Secretariat
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> tcmtf mailing list
>>>> tcmtf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>=20
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>=20
>>=20
>> ________________________________
>>=20
>> Este mensaje se dirige exclusivamente a su destinatario. Puede=20
>> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico=20
>> en el enlace situado m=E1s abajo.
>> This message is intended exclusively for its addressee. We only send=20=

>> and receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>=20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From mramalho@cisco.com  Fri Jan 11 05:34:41 2013
Return-Path: <mramalho@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7EE021F890F for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 05:34:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
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 olUQ+RPm5iPp for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 05:34:40 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id C7B9521F88AE for <tcmtf@ietf.org>; Fri, 11 Jan 2013 05:34:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16580; q=dns/txt; s=iport; t=1357911279; x=1359120879; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=AvCfeR0j6dwBhzgH7sVPJac71FxK9LyhsUPofW6k2ak=; b=FnrbswjfxTbiARD4or5jsN0/wE6WfL2vCe+01sPDROXzHdeBQ+vQ+aK0 yf+NCALbl4JveO8WGoyc4CSGM+uDHefsUvH8TSBmV2stbJwcH7PmBSe2I 2oYlFGGUfNkZh7/RUm9OzwRviJ6W+TWfVSgTolNcJ5OrTLyKhFY8MyCat c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAHUU8FCtJV2a/2dsb2JhbAA6CoNsug0Wc4IeAQEBAgEBAQEBZAcGAwIFBwQCAQgOAwQBAQEKHQcnCxQJCAIEAQ0FCAELB4d4BgcFtFuMZwYKg0dhA5JXhE+PLYJ1gWYJFwQa
X-IronPort-AV: E=Sophos;i="4.84,451,1355097600"; d="scan'208";a="161365014"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-5.cisco.com with ESMTP; 11 Jan 2013 13:34:38 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r0BDYcwv003868 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 11 Jan 2013 13:34:38 GMT
Received: from xmb-rcd-x12.cisco.com ([169.254.2.163]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.02.0318.004; Fri, 11 Jan 2013 07:34:38 -0600
From: "Michael Ramalho (mramalho)" <mramalho@cisco.com>
To: Luigi Iannone <ggx@gigix.net>, =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
Thread-Topic: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
Thread-Index: Ac3ui7/19m7iJp6vTHSMflxr4PuotgAxLtuAAAFrJAAABsArwAAmdPcAAAKqLQAAAV2VAAAHQgCw
Date: Fri, 11 Jan 2013 13:34:37 +0000
Message-ID: <D21571530BF9644D9A443D6BD95B9103154BCBB6@xmb-rcd-x12.cisco.com>
References: <002901cdef1e$31a1b130$94e51390$@unizar.es> <F5EDC35DF914C1428C28E149F10463A2528959F6@EX10-MB2-MAD.hi.inet> <D21571530BF9644D9A443D6BD95B9103154BC655@xmb-rcd-x12.cisco.com> <003a01cdefd8$b2d06a70$18713f50$@unizar.es> <A3179A2C9AAEE647BE70AC4C7881D5FB01775F0F@sluga.fer.hr> <4734F2B7-003C-4BB5-B69A-E089DE6085C7@gigix.net>
In-Reply-To: <4734F2B7-003C-4BB5-B69A-E089DE6085C7@gigix.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.168.118]
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, FERNANDO PASCUAL BLANCO <fpb@tid.es>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Subject: Re: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcmtf-04.txt
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 13:34:41 -0000

All,

Regarding Jose's comment: " So the question is: are you proposing that we s=
hould develop something within TCMTF WG in order to classify packets? "

I agree with Luigi and Mirko ... there are more than enough people working =
on traffic flow descriptions ... and how to signal/inform networks of their=
 requirements (e.g., per-hop behaviors and the like).

My point below is that you SHOULD NOT decide whether or not to TCMTF packet=
s from a flow simply by looking at the individual packets themselves (e.g.,=
 the G.722.2 "voice" example I provided).

In my opinion, "non-secure" flows with less stringent transport characteris=
tics SHOULD tell the network - so that the network can optimize itself for =
temporary peaks in load, efficiency and so on.

There will always be corner cases (e.g., secure communications) where a flo=
w will not want to signal that type of information to the network - so appl=
ying TCMTF techniques to such flows is a difficult decision.

Service providers are often measured as to the transport performance of the=
ir network. Excepting the cases where TCMTF saves enough bandwidth to lower=
 packet drop percentages, TCMTF will (in general) cause added delay in the =
backbone portion of the flows. I desire TCMTF to be of interest to these se=
rvice providers, so I believe it is wise to address their concern "up-front=
" while defining TCMTF.

For now, I would recommend a placeholder in the draft that addresses the co=
ncern and that TCMTF SHOULD consider the traffic class of the flows when su=
ch information is available.

Michael Ramalho

-----Original Message-----
From: Luigi Iannone [mailto:ggx@gigix.net]=20
Sent: Friday, January 11, 2013 5:46 AM
To: Mirko Su=BEnjevi=E6
Cc: jsaldana@unizar.es; Michael Ramalho (mramalho); FERNANDO PASCUAL BLANCO=
; tcmtf@ietf.org
Subject: Re: [tcmtf] : New Version Notification for draft-saldana-tsvwg-tcm=
tf-04.txt


On 11 Jan. 2013, at 11:06 , Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr> wr=
ote:

> Hello all,
> I think there is no need to develop something for traffic classification =
in the scope of TCMTF WG. There is a large research community doing traffic=
 classification and some of the already developed techniques can be applied=
 for our need. It may be feasible to present an overview of techniques whic=
h could be used by TCMTF in draft B.

+1

There are tons of classification methods out there, developing a new one do=
es not look very useful to me.

Luigi


> Mirko
>=20
> -----Original Message-----
> From: Jose Saldana [mailto:jsaldana@unizar.es]
> Sent: Friday, January 11, 2013 9:50 AM
> To: 'Michael Ramalho (mramalho)'; 'FERNANDO PASCUAL BLANCO';=20
> tcmtf@ietf.org
> Cc: Mirko Su=BEnjevi=E6
> Subject: RE: [tcmtf] : New Version Notification for=20
> draft-saldana-tsvwg-tcmtf-04.txt
>=20
> Michael,
>=20
> I think this discussion is getting more and more interesting. Thanks.
>=20
> You talk about methods for identifying the different packets, and it is i=
nteresting, since it would make things work really better: the multiplexer =
would know which packets can and which ones can not be multiplexed.
>=20
> One question here is that perhaps the developer of the application to be =
multiplexed wouldn't want to add anything to its protocol. I mean, if I am =
the network provider and I want to save bandwidth in my network, I only hav=
e the packets as they have been sent by the final application.
>=20
> So the question is: are you proposing that we should develop something wi=
thin TCMTF WG in order to classify packets? Perhaps this is too much, since=
 there will be other people thinking about traffic classification with othe=
r objectives.
>=20
> Perhaps a "natural" way could be widening the scope of draft (B), includi=
ng not only delay limits, but also currently existing traffic classificatio=
n methods which could be useful for selecting the packets to multiplex. Doe=
s this sound well?
>=20
> Jose
>=20
>> -----Mensaje original-----
>> De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com] Enviado el:=20
>> jueves, 10 de enero de 2013 15:48
>> Para: FERNANDO PASCUAL BLANCO; jsaldana@unizar.es; tcmtf@ietf.org
>> Asunto: RE: [tcmtf] : New Version Notification for
> draft-saldana-tsvwg-tcmtf-
>> 04.txt
>>=20
>> All,
>>=20
>> I'll answer Fernando and Jose at the same time, with "MAR:" below.
>>=20
>> Michael Ramalho
>>=20
>> -----Original Message-----
>> From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>> Sent: Thursday, January 10, 2013 6:16 AM
>> To: jsaldana@unizar.es; Michael Ramalho (mramalho); tcmtf@ietf.org
>> Subject: Re: [tcmtf] : New Version Notification for
>> draft-saldana-tsvwg- tcmtf-04.txt
>>=20
>> Hi Jose,
>>=20
>>        I fully agree with you. TCMTF module could be embedded within=20
>> a
> router
>> or not, and the decision to apply TCMTF to a flow (and the way to=20
>> signal
>> that) or not is something that under my point of view is out of the=20
>> scope
> of
>> drafts A and B.
>>=20
>> MAR: First of all, "we" defined drafts A and B ... we can define=20
>> other
> drafts or
>> other working group charters/proposals. However ...
>>=20
>> MAR: I disagree ... I think this happens to be partially addressed in
> draft B
>> (http://www.ietf.org/id/draft-suznjevic-tsvwg-mtd-tcmtf-00.pdf ).
>>=20
>> <MAR:>
>> Consider the following ... a potential TCMTF endpoint sees two small=20
>> UDP packets ... and lets further assume that it cannot tell by=20
>> inspection the applications the small packets belong to.
>>=20
>> One of the packets belong to a First Person Shooter (FPS) game (very=20
>> low latency desired) and the other from my home thermostat (reporting=20
>> my nominal house temperature to a service in the cloud).
>>=20
>> My home thermostat also previously sent metadata (a traffic class=20
>> flow
>> identifier) telling all hops on the path that my packet is relatively
> delay
>> insensitive (maybe via a STUN packet) ... and it doesn't mind if any
> particular
>> hop adds even 200 ms of per-hop delay.
>>=20
>> Wouldn't it make sense that TCMTF assumes my thermostat flow is a=20
>> strong candidate and the FPS isn't a candidate unless it arrived
> "just/immediately
>> before" a TCMTF packet creation?
>>=20
>> The bottom line is that (deep) packet inspection will only get you so fa=
r.
>> Indeed some VXI protocol designs are being modified so that they can=20
>> be "more easily" identified by routers (by headers early in the=20
>> packet
> payloads)
>> - until this point there was no effort to do so and it is very, very
> difficult (in
>> general) to determine a "delay tolerance" by simply looking at a
> particular
>> packet. Even more so with packet encryption ;-).
>>=20
>> When the "internet of things" is here ... we will have lots of small
> packets ...
>> the exact application where TCMTF has its strongest use case. And=20
>> most of these small packets will have very loose delay bounds (long=20
>> nominal reporting intervals or periodic keep-alives for firewalls/NATs/e=
tc.).
>> </MAR:>
>>=20
>> Once defined the core TCMTF functionality we can build things around it.
>>=20
>> MAR: True. But equally true is that if you DON'T specify useful=20
>> criteria
> on how
>> you classify candidate TCMTF flows ... it may not be seriously considere=
d.
>>=20
>> MAR: A good example is the "voice communications" item in Table 1 of=20
>> draft B. If the RTP voice flow was a push-to-talk flow ... then I=20
>> could agree to
> up to
>> a 80ms mux delay. For a normal voice call, 80ms is WAY, WAY too much=20
>> delay (most VoIP calls use ptime of 20ms for a reason!). If you knew=20
>> a packet
> was a
>> voice packet (via RTP inspection) ... but additionally knew it=20
>> belonged
> for a
>> push-to-talk service ... you could TCMTF it. So you really need to=20
>> have
> more
>> knowledge than just "it is a packet of G.722.2 voice" to make a decision=
.
> As an
>> aside, the reference for Table 1 (of draft B) is not rigorous enough=20
>> for
> the use
>> claimed (you can find hundreds of references that would disagree with=20
>> the
>> 80 ms maximum recommendation).
>>=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
>>=20
>>=20
>>=20
>> On 10/01/13 11:35, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>=20
>>> Hi, Michael.
>>>=20
>>> I have been thinking about your mail. The question is how to=20
>>> identify the flows. We can use two examples:
>>>=20
>>> Case 1: You are a network operator and you have an agreement with a=20
>>> networked gaming company. So you are trying to merge flows belonging=20
>>> to the same game, and send them multiplexed to the demux located at=20
>>> the game company. So your network has to be able to identify those=20
>>> flows and send them to the mux. So you would need a sort of "Deep=20
>>> Packet Inspection", I think.
>>=20
>> MAR: As per my reply to Fernando above, DPI will only get you so far.
> There
>> are a lot of applications using UDP in which you cannot make a=20
>> definitive association between the packet and a particular service.
>>=20
>> MAR: However, when TCMTF is used on a "high-enough" speed link, the=20
>> delay can be arbitrarily small. Thus I think some TCMTF guidance is
> primarily
>> needed for low-speed links (i.e., links where the mux delay could be=20
>> in excess of some reasonable bound, like 5 ms maximum).
>>=20
>>> One solution: all the packets with a certain destination IP go to=20
>>> the mux. The servers of the game are clearly identified by their IPs.
>>=20
>> MAR: As an aside, if the network operator had such an agreement ...=20
>> they would know a priori something about the aggregate flows to the=20
>> networked game company. They could also determine this from metadata=20
>> without any "special arrangement".
>>=20
>> MAR: However, even this is not general enough. We already have=20
>> applications that for a particular source and destination IP=20
>> address/port
> have
>> different QoS treatment (e.g., SVC video - different packets have
> different
>> QoS requirements for the same flow).
>>=20
>> MAR: I think capabilities negotiation (another thread) should include=20
>> a
> notion
>> of "what types of flows" to consider TCMTFing. Without it, I think=20
>> TCMTF could make some poor decisions (not on efficiency, the=20
>> dimension upon which it always wins - but on delay) which may, in=20
>> turn, create impedance
> for
>> its acceptance.
>>=20
>>>=20
>>> Case 2: But what happens if you only want to save bandwidth inside=20
>>> your
>>> network?: you have to compress traffic before traversing a certain=20
>>> path with scarce bandwidth. So you will have to identify "flows" of=20
>>> packets with a cadence, and some common characteristics. In this=20
>>> case, you may need to use "signature analysis" or something, in=20
>>> order to know the game genre, etc, and thus being able to set a=20
>>> maximum multiplexing period, for example.
>>>=20
>>> But I don't know if the question of identifying the flows has to be=20
>>> solved by TCMTF.
>>=20
>> MAR: I was not arguing for "solving" the flow identification problem=20
>> at
> this
>> stage ... just mentioning it now would make sense ... and that=20
>> techniques such as exploiting any metadata information for the flow=20
>> and/or signature analysis could be used for the TCMTF determination.
>> Eventually, I think we need to mention how capabilities negotiation can =
include flow types too.
>>=20
>>> There should be other machine that sends to the mux only the packets=20
>>> that have to be multiplexed.... or not?
>>>=20
>>> Jose
>>>=20
>>>> -----Mensaje original-----
>>>> De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com]  Enviado
>>>> el: mi=E9rcoles, 09 de enero de 2013 18:05
>>>> Para: jsaldana@unizar.es; tcmtf@ietf.org
>>>> Asunto: RE: [tcmtf] : New Version Notification for
>>>> draft-saldana-tsvwg-tcmtf-
>>>> 04.txt
>>>>=20
>>>> Jose, et. al.,
>>>>=20
>>>> Sorry for being so quiet recently on this list ... I am just=20
>>>> beginning to become  unburied from work late last year!
>>>>=20
>>>> You mention FPS and MMORPGs in the draft ... but has any detailed=20
>>>> thought  about how TCMTF might identify which flows it should NOT=20
>>>> attempt to  compress?
>>>>=20
>>>> Considering "the Internet of things" (where virtually every device=20
>>>> is connected via IP) ... we can expect a lot of small packets ...
>>>> but not necessarily know if we should compress them or not (e.g.,=20
>>>> FPS packets) ... or  what the delay bounds on the compression should b=
e.
>>>>=20
>>>> Should we mention that flows that signal their own traffic class=20
>>>> (e.g., using  "Metadata" describing the flow) is a good thing to=20
>>>> differentiate on?
>>>> Should
>>>> we suggest signature analysis (a probabilistic guess for the=20
>>>> application based  on its time-domain signature characteristics)=20
>>>> might also be of utility?
>>>>=20
>>>> Being silent on this point may lessen the attractiveness to design=20
>>>> using it.
>>>>=20
>>>> Sorry if this point has been raised before.
>>>>=20
>>>> Best,
>>>>=20
>>>> Michael Ramalho
>>>>=20
>>>> -----Original Message-----
>>>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On=20
>>>> Behalf  Of Jose Saldana
>>>> Sent: Wednesday, January 09, 2013 4:29 AM
>>>> To: tcmtf@ietf.org
>>>> Subject: [tcmtf] RV: New Version Notification for
>>>> draft-saldana-tsvwg-tcmtf-
>>>> 04.txt
>>>>=20
>>>> I have just uploaded a new version of the tcmtf draft.
>>>>=20
>>>> Jose
>>>>=20
>>>>> -----Mensaje original-----
>>>>> De: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
>>>>> Enviado
>>>>> el: mi=E9rcoles, 09 de enero de 2013 10:25
>>>>> Para: jsaldana@unizar.es
>>>>> CC: mperumal@cisco.com; navajas@unizar.es; dwing@cisco.com;
>>>> fpb@tid.es
>>>>> Asunto: New Version Notification for=20
>>>>> draft-saldana-tsvwg-tcmtf-04.txt
>>>>>=20
>>>>>=20
>>>>> A new version of I-D, draft-saldana-tsvwg-tcmtf-04.txt has been=20
>>>>> successfully submitted by Jose Saldana and posted to the IETF
>>>> repository.
>>>>>=20
>>>>> Filename:   draft-saldana-tsvwg-tcmtf
>>>>> Revision:   04
>>>>> Title:              Tunneling Compressed Multiplexed Traffic Flows
> (TCMTF)
>>>>> Creation date:      2013-01-09
>>>>> WG ID:              Individual Submission
>>>>> Number of pages: 19
>>>>> URL:
>>>> http://www.ietf.org/internet-drafts/draft-saldana-tsvwg-tcmtf-
>>>>> 04.txt
>>>>> Status:
>>>> http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf
>>>>> Htmlized:
>>>> http://tools.ietf.org/html/draft-saldana-tsvwg-tcmtf-04
>>>>> Diff:
>>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-saldana-tsvwg-tcmtf-04
>>>>>=20
>>>>> Abstract:
>>>>>   This document describes a method to improve the bandwidth
>>>> utilization
>>>>>   of network paths that carry multiple streams in parallel sharing a
>>>>>   common path.  The method combines standard protocols that provide
>>>>>   compression, multiplexing, and tunneling over a network path for
>>>> the
>>>>>   purpose of reducing the bandwidth used when multiple streams are
>>>>>   carried over that path.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> The IETF Secretariat
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> tcmtf mailing list
>>>> tcmtf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>=20
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>=20
>>=20
>> ________________________________
>>=20
>> Este mensaje se dirige exclusivamente a su destinatario. Puede=20
>> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=
=F3nico=20
>> en el enlace situado m=E1s abajo.
>> This message is intended exclusively for its addressee. We only send=20
>> and receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>=20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From diego@tid.es  Fri Jan 11 08:08:49 2013
Return-Path: <diego@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D249D21F88B1 for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 08:08:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KsfovB4j4d6l for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 08:08:48 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 13F8321F88AE for <tcmtf@ietf.org>; Fri, 11 Jan 2013 08:08:47 -0800 (PST)
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 <0MGG008GFY6KWT@tid.hi.inet> for tcmtf@ietf.org; Fri, 11 Jan 2013 17:08:45 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id BA.11.02896.D0930F05; Fri, 11 Jan 2013 17:08:45 +0100 (CET)
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 <0MGG008GIY6LWT@tid.hi.inet> for tcmtf@ietf.org; Fri, 11 Jan 2013 17:08:45 +0100 (MET)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.151]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0318.004; Fri, 11 Jan 2013 17:08:44 +0100
Date: Fri, 11 Jan 2013 16:05:51 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <F5EDC35DF914C1428C28E149F10463A252895425@EX10-MB2-MAD.hi.inet>
X-Originating-IP: [10.95.64.115]
To: FERNANDO PASCUAL BLANCO <fpb@tid.es>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A046533FEC1@EX10-MB1-MAD.hi.inet>
Content-id: <64D196DC483B5B43820B31C0CA474E41@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, es-ES
Thread-topic: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2
Thread-index: Ac3uTNeTbO+aCk7ITXS7wkpgZ6Gw0gABangwADG+O4AANqC9gA==
X-AuditID: 0a5f4e69-b7f636d000000b50-1c-50f0390defb4
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNKsWRmVeSWpSXmKPExsXCFe9nqMtr+SHAoOujkcWuzxsYHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVsW5lTsEFmYrG31eYGhgPi3cxcnJICJhItHxuYYOwxSQu3FsP ZHNxCAlsY5Q4+vswO4Tzg1Fi8ervLBDOTEaJX+9/sIC0sAioShy82cYKYrMB2Y+af7OD2MIC 7hINX9sYQWxOAR+JU8uPs0CsUJD4c+4xmC0ioCGx/e5fZpChzAJfGSWefpsENohXwFti3ozF YDazgJnEqz+7WSDighI/Jt8DsjmA4joSXydFQJSISzS33mSBsLUlnry7ANbKKCAr8W7+fFaI XR4SLe/msUPYThJTrt5gh7hHQGLJnvPMELaoxMvH/1hBxgsBnXDzWskERolZSI6YheSIWQhH zEJyxCwkRyxgZF3FKFacVJSZnlGSm5iZk25gpJeRqZeZl1qyiRESc5k7GJfvVDnEKMDBqMTD q1H5PkCINbGsuDL3EKMkB5OSKO868w8BQnxJ+SmVGYnFGfFFpTmpxYcYJTiYlUR4vRiBcrwp iZVVqUX5MCkZDg4lCd6vIG2CRanpqRVpmTnAxAKTZuLgBGnnAWr/AFLDW1yQmFucmQ6RP8Uo KSXO+wUkIQCSyCjNg+t9xSgOdKQwL4sFUJYHmALhul4BDWQCGnj2wnuQgSWJCCmpBkb+S0+q 7qa5XroRtTj9/xSv20+X+dUe19U+f+LCt18686XT+/8nn5r4V8iV8/kpP7HJMXnH/barSH3j NxdnetTb82LH9BvFprErpmqUGi3m1hXTuJX170JE58n3u+cz9bRUPVHQNYveZvs1l/H8zocn JpxyPaVeolf4IlB5g0DMU+N3RfHmBneVWIozEg21mIuKEwFQincRPgMAAA==
References: <F5EDC35DF914C1428C28E149F10463A252895425@EX10-MB2-MAD.hi.inet>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, "Matteo.Berioli@dlr.de" <Matteo.Berioli@dlr.de>, =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>, "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2
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, 11 Jan 2013 16:08:50 -0000

Hi,

While I agree with Fernando when it comes to the formal procedure, I don't
see any harm in the DLR guys progressing with the satellite scenario. As Mi=
rko
says, we can include in the charter the scenario once we have a mature
draft...

Be goode,

On 10 Jan 2013, at 11:01 , FERNANDO PASCUAL BLANCO wrote:

> Hi Mirko, Jose,
>
> I also think that satellite specific scenario can wait to be discussed, f=
ocusing our efforts in the complete definition of the TCMTF itself. Regardi=
ng the discussion about the signaling for capabilities negotiation, it is b=
eing discussed in a different thread.
>
> Regards,
>
> Fernando Pascual Blanco
> Telef=F3nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>
> From: Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr>
> Date: mi=E9rcoles, 9 de enero de 2013 11:21
> To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ie=
tf.org>
> Cc: "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>, "Matteo.Berioli@dlr.de=
" <Matteo.Berioli@dlr.de>, Fernando Pascual Blanco <fpb@tid.es>
> Subject: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2
>
> Well the satelite scenario is very interesting application of TCMTF, but =
I think that at this point we should focus our efforts on the current docum=
ents. Once we have the draft of the satellite scenario written and discusse=
d we can include it in the new version of the Charter.
> I think that the same applies to your first question regarding the specif=
ic draft about signaling issues. I think that the WG can be re-chartered la=
ter on.
>
> Mirko Suznjevic
>
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of=
 Jose Saldana
> Sent: Wednesday, January 9, 2013 10:49 AM
> To: tcmtf@ietf.org
> Cc: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de; Fernando Pascual Blanco
> Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2
>
> There is another question: Tomaso, from DLR, proposed another draft for a=
 specific satellite scenario (http://www.ietf.org/mail-archive/web/tcmtf/cu=
rrent/msg00095.html). Should we include this in the charter?
>
> My opinion is that, at this stage, we could begin the WG without consider=
ing this, and at the same time a draft could be written and discussed. Acco=
rding to the ideas and feedback after that, including it in a new version o=
f the Charter could be considered.
>
> 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 e=
nlace 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


--
"Esta vez no fallaremos, Doctor Infierno"

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

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


________________________________

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

From Matteo.Berioli@dlr.de  Fri Jan 11 09:48:46 2013
Return-Path: <Matteo.Berioli@dlr.de>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8424721F8994 for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 09:48:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 2ktTQ6Ck80vE for <tcmtf@ietfa.amsl.com>; Fri, 11 Jan 2013 09:48:45 -0800 (PST)
Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.32]) by ietfa.amsl.com (Postfix) with ESMTP id AFE2921F88EA for <tcmtf@ietf.org>; Fri, 11 Jan 2013 09:48:43 -0800 (PST)
Received: from DLREXHUB01.intra.dlr.de (172.21.152.130) by dlrexedge01.dlr.de (172.21.163.100) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 11 Jan 2013 18:48:14 +0100
Received: from DLREXMBX02.intra.dlr.de ([fe80::8cc6:b83e:ddc1:4e8b]) by dlrexhub01.intra.dlr.de ([::1]) with mapi id 14.02.0318.004; Fri, 11 Jan 2013 18:48:20 +0100
From: <Matteo.Berioli@dlr.de>
To: <diego@tid.es>, <fpb@tid.es>
Thread-Topic: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2
Thread-Index: Ac3uTNeTbO+aCk7ITXS7wkpgZ6Gw0gABangwADG+O4AANqC9gAALzvKg
Date: Fri, 11 Jan 2013 17:48:20 +0000
Message-ID: <48DB40641BACF54C892EB0A12B4733C10BEDC84A@dlrexmbx02.intra.dlr.de>
References: <F5EDC35DF914C1428C28E149F10463A252895425@EX10-MB2-MAD.hi.inet> <E6D8B95470ED0845B3376F61DCAB1A046533FEC1@EX10-MB1-MAD.hi.inet>
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A046533FEC1@EX10-MB1-MAD.hi.inet>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.247.173.107]
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tcmtf@ietf.org, Mirko.Suznjevic@fer.hr, Tomaso.deCola@dlr.de, jsaldana@unizar.es
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2
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, 11 Jan 2013 17:48:46 -0000

Hi all,

Just a small clarification: the "DLR" idea is not just constrained to satel=
lites, it applies to all wireless access mediums in general.
Since on these wireless access mediums, header compression is desirable but=
 it has to be terminated at the access point, the idea is to extend it to t=
he backbone by exploiting a modification of TCMTF.

Regards,
Matteo


-----Original Message-----
From: Diego R. Lopez [mailto:diego@tid.es]=20
Sent: 11 January 2013 17:06
To: FERNANDO PASCUAL BLANCO
Cc: Mirko Su=BEnjevic; jsaldana@unizar.es; tcmtf@ietf.org; Cola, Tomaso de;=
 Berioli, Matteo
Subject: Re: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2

Hi,

While I agree with Fernando when it comes to the formal procedure, I don't =
see any harm in the DLR guys progressing with the satellite scenario. As Mi=
rko says, we can include in the charter the scenario once we have a mature =
draft...

Be goode,

On 10 Jan 2013, at 11:01 , FERNANDO PASCUAL BLANCO wrote:

> Hi Mirko, Jose,
>
> I also think that satellite specific scenario can wait to be discussed, f=
ocusing our efforts in the complete definition of the TCMTF itself. Regardi=
ng the discussion about the signaling for capabilities negotiation, it is b=
eing discussed in a different thread.
>
> Regards,
>
> Fernando Pascual Blanco
> Telef=F3nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>
> From: Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr>
> Date: mi=E9rcoles, 9 de enero de 2013 11:21
> To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org"=20
> <tcmtf@ietf.org>
> Cc: "Tomaso.deCola@dlr.de" <Tomaso.deCola@dlr.de>,=20
> "Matteo.Berioli@dlr.de" <Matteo.Berioli@dlr.de>, Fernando Pascual=20
> Blanco <fpb@tid.es>
> Subject: RE: [tcmtf] Questions regarding the TCMTF WG Chart proposal.=20
> 2
>
> Well the satelite scenario is very interesting application of TCMTF, but =
I think that at this point we should focus our efforts on the current docum=
ents. Once we have the draft of the satellite scenario written and discusse=
d we can include it in the new version of the Charter.
> I think that the same applies to your first question regarding the specif=
ic draft about signaling issues. I think that the WG can be re-chartered la=
ter on.
>
> Mirko Suznjevic
>
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf=20
> Of Jose Saldana
> Sent: Wednesday, January 9, 2013 10:49 AM
> To: tcmtf@ietf.org
> Cc: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de; Fernando Pascual=20
> Blanco
> Subject: [tcmtf] Questions regarding the TCMTF WG Chart proposal. 2
>
> There is another question: Tomaso, from DLR, proposed another draft for a=
 specific satellite scenario (http://www.ietf.org/mail-archive/web/tcmtf/cu=
rrent/msg00095.html). Should we include this in the charter?
>
> My opinion is that, at this stage, we could begin the WG without consider=
ing this, and at the same time a draft could be written and discussed. Acco=
rding to the ideas and feedback after that, including it in a new version o=
f the Charter could be considered.
>
> 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 e=
nlace 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


--
"Esta vez no fallaremos, Doctor Infierno"

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

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


________________________________

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

From jsaldana@unizar.es  Tue Jan 15 02:55:39 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C359E21F860A for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:55:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bPnZB1DGK-V7 for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:55:38 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 4494021F85E8 for <tcmtf@ietf.org>; Tue, 15 Jan 2013 02:55:37 -0800 (PST)
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 r0FAtTK4000661; Tue, 15 Jan 2013 11:55:29 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Tue, 15 Jan 2013 11:55:34 +0100
Organization: Universidad de Zaragoza
Message-ID: <006501cdf30e$d890ea80$89b2bf80$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0066_01CDF317.3A555280"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3y/UFqIyjasnoeRoy+0n+IH96/pA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Wesley Eddy <wes@mti-systems.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [tcmtf] TCMTF: Summary of the discussion about the Charter for a possible Working Group
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, 15 Jan 2013 10:55:39 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0066_01CDF317.3A555280
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all.

 

Last week we discussed about the charter and the drafts to include in a
possible Working Group about TCMTF. In this mail, I will try to summarize
the discussion in order to reach consensus about what to include and what to
leave for future work (possible re-charter of the WG). I have used some
quotations of people's mails. If someone thinks I have not understood his
point, or I have simplified the problem, feel free to report it.

 

- We are talking about 5 possible documents:

 

- Document (A) refers to the main TCMTF draft, currently in
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

- Document (B) refers to the informational draft about maximum tolerable
delays, currently in
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/

- Document (C) may refer to a new document about signaling

- Document (D) may refer to the proposal of Matteo and Tomasso (the "DLR"
draft)

- Document (E) may refer to a document about LISP and TCMTF

 

So I am sending 5 different mails in order to know if there is consensus
about:

 

- The content of each Document

- If the Document has to be:

- included in the current charter

- announced as future work after re-chartering

- not cited at all

 

 

Best regards,

 

Jose


------=_NextPart_000_0066_01CDF317.3A555280
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>Hi all.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Last week we discussed about the charter and the drafts to =
include in a possible Working Group about TCMTF. In this mail, I will =
try to summarize the discussion in order to reach consensus about what =
to include and what to leave for future work (possible re-charter of the =
WG). I have used some quotations of people&#8217;s mails. If someone =
thinks I have not understood his point, or I have simplified the =
problem, feel free to report it.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- We are talking about 5 possible =
documents:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- Document (A) refers to the main TCMTF draft, currently in =
<a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http:=
//datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></spa=
n></p><p class=3DMsoNormal><span lang=3DEN-US>- Document (B) refers to =
the informational draft about maximum tolerable delays, currently in <a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a><o:p=
></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>- Document (C) =
may refer to a new document about signaling<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- Document (D) may refer to the =
proposal of Matteo and Tomasso (the &#8220;DLR&#8221; =
draft)<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>- =
Document (E) may refer to a document about LISP and =
TCMTF<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>So I am sending 5 different mails in order to know if there =
is consensus about:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- The content of each Document<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- If the Document has to =
be:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-indent:35.4pt'><span lang=3DEN-US>- included in the =
current charter<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-indent:35.4pt'><span lang=3DEN-US>- announced as future =
work after re-chartering<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-indent:35.4pt'><span lang=3DEN-US>- not cited at =
all<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Best regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US>Jose<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_0066_01CDF317.3A555280--


From jsaldana@unizar.es  Tue Jan 15 02:55:58 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B6EE21F85E8 for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lU-Rx+MYtKST for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:55:56 -0800 (PST)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8E62721F8835 for <tcmtf@ietf.org>; Tue, 15 Jan 2013 02:55:55 -0800 (PST)
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 r0FAtq82000980 for <tcmtf@ietf.org>; Tue, 15 Jan 2013 11:55:52 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Tue, 15 Jan 2013 11:55:55 +0100
Organization: Universidad de Zaragoza
Message-ID: <006a01cdf30e$e477ca80$ad675f80$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_006B_01CDF317.463C3280"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3zAeLy1yQgwmr3SQqrjWQn55Okzg==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] TCMTF: Document A discussion: content and charter
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, 15 Jan 2013 10:55:58 -0000

This is a multipart message in MIME format.

------=_NextPart_000_006B_01CDF317.463C3280
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Document (A) refers to the main TCMTF draft, currently in
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

=20

1.- Content of the Document

=20

Currently it contains the description of the question and the protocols
which could be used on each layer (tunneling, compressing, =
multiplexing). It
says that the signaling issues would be that of each protocol.

=20

There is consensus (I think) about this: we should include some =
signaling
issues. The question is: What should we include in Draft A and what in =
Draft
C?

=20

- *Auto-negotiation* Negotiation mechanisms to decide the options at =
each
layer (compression, multiplexing and tunneling) between mux and demux.
Perhaps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP =
and
IPHC, so the two machines will have to negotiate in order to decide =
which
compression protocol use.

=20

This should be included in (A). I think there is consensus about this:

Juan Antonio: =93The first kind of signaling ("auto-negotiation") is =
needed
from the beginning if we don't want an extremely static protocol and
therefore possibly difficult to get it working, especially when in most =
of
cases the peers belong to different entities/companies.=94

=20

Dan: =93We need that -- it is capabilities negotiation.  It is needed =
because
the protocol will fail if one side mistakenly thinks the other side has
certain functionality, and because we will want to add some fancy new
compression in the year 2020 and will need to negotiate it.=94

=20

Fernando: =93I also agree with the idea of including the mux-demux =
signaling
within the draft A (as Dan said, they are capabilities negotiation). =
This
draft should be able to get two boxes with TCMTF fully working between =
them.
Under my point of view this includes the definition of the capabilities =
in
each node and the negotiation of that capabilities.=94

=20

Does this mean that Document (A) will no longer be a Best Current =
Practice?
I think so.

=20

=20

- *dynamically establishing, modifying and releasing tunnels*

=20

#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.

=20

There is still no consensus here:

=20

Fernando: =93Regarding #1, to be honest, I am not completely sure of the =
need
to specify a mechanism to discover muxes and demuxes between them. I =
think
those kind of mechanisms have more sense in local environments but I=B4m =
not
sure if it applies here. At least at the beginning this associations can =
be
done manually.=94

=20

Muthu: =93I think it is the opposite -- in local environments you can
provision/associate them manually. However, in a multi-vendor =
environment
over the Internet this should happen automatically.=94=20

=93#1 needs to be specified.=94

=20

=20

=20

#2. A mechanism to *elect an optimal muxer and a de-muxer when there are
more than one muxer/de-muxer for a flow*.

=20

We agree: This can wait for Document (C).

=20

                Fernando: =93#2 is more related to the higher entity =
that has
to decide whether a flow should be TCMTFed or not, and under my point of
view it can be addressed in a different draft.=94

                Muthu: =93#2 can be added later.=94

=20

=20

3. A mechanism to *setup/release a tunnel b/w a muxer and a de-muxer*.

=20

We agree: This has to be included in (A).

=20

                Fernando =93#3 I think should be included in the draft =
A,
since it is a mechanism within the TFMTF protocol itself.=94

                Muthu: =93#3 many not require much specification.=94

=20

=20

=20

2.- Should we include it in the Charter now?

=20

Of course, Document (A) should be in the charter.

=20

=20

Best regards,

=20

Jose

=20


------=_NextPart_000_006B_01CDF317.463C3280
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.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=3DMsoNormal><span =
lang=3DEN-US>Document (A) refers to the main TCMTF draft, currently in =
<a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http:=
//datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></spa=
n></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>1.- Content of the Document<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Currently it contains the =
description of the question and the protocols which could be used on =
each layer (tunneling, compressing, multiplexing). It says that the =
signaling issues would be that of each protocol.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>There is consensus (I think) about =
this: we should include some signaling issues. The question is: What =
should we include in Draft A and what in Draft =
C?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- *<b>Auto-negotiation</b>* Negotiation mechanisms to =
decide the options at each layer (compression, multiplexing and =
tunneling) between mux and demux. Perhaps the mux has ROHC, ECRTP and =
IPHC, and the demux only has ECRTP and IPHC, so the two machines will =
have to negotiate in order to decide which compression protocol =
use.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This should be included in (A). I think there is consensus =
about this:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:35.4pt'><span lang=3DEN-US>Juan Antonio: &#8220;The =
first kind of signaling (&quot;auto-negotiation&quot;) is needed from =
the beginning if we don't want an extremely static protocol and =
therefore possibly difficult to get it working, especially when in most =
of cases the peers belong to different =
entities/companies.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US>Dan: &#8220;We need that -- it is capabilities =
negotiation.=A0 It is needed because the protocol will fail if one side =
mistakenly thinks the other side has certain functionality, and because =
we will want to add some fancy new compression in the year 2020 and will =
need to negotiate it.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Fernando: &#8220;I also =
agree with the idea of including the mux-demux signaling within the =
draft A (as Dan said, they are capabilities negotiation). This draft =
should be able to get two boxes with TCMTF fully working between them. =
Under my point of view this includes the definition of the capabilities =
in each node and the negotiation of that =
capabilities.&#8221;<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>Does this mean that Document (A) will no longer be a Best =
Current Practice? I think so.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>- *<b>dynamically establishing, =
modifying and releasing tunnels</b>*<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. A *<b>mechanism for a muxer =
to discover a de-muxer (and vice versa)</b>*.<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 is still no consensus =
here:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.4pt'><span lang=3DEN-US>Fernando: =
&#8220;Regarding #1, to be honest, I am not completely sure of the need =
to specify a mechanism to discover muxes and demuxes between them. I =
think those kind of mechanisms have more sense in local environments but =
I=B4m not sure if it applies here. At least at the beginning this =
associations can be done manually.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.4pt'><span =
lang=3DEN-US>Muthu: &#8220;I think it is the opposite -- in local =
environments you can provision/associate them manually. However, in a =
multi-vendor environment over the Internet this should happen =
automatically.&#8221; <o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.4pt;text-indent:35.4pt'><span =
lang=3DEN-US>&#8220;#1 needs to be =
specified.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>#2. A mechanism to *<b>elect an optimal muxer and a =
de-muxer when there are more than one muxer/de-muxer for a =
flow</b>*.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>We agree: This can wait for Document =
(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>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Fernando: =
&#8220;#2 is more related to the higher entity that has to decide =
whether a flow should be TCMTFed or not, and under my point of view it =
can be addressed in a different draft.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Muthu: =
&#8220;#2 can be added later.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>3. A mechanism to =
*<b>setup/release a tunnel b/w a muxer and a =
de-muxer</b>*.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>We agree: This has to be included in =
(A).<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>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Fernando =
&#8220;#3 I think should be included in the draft A, since it is a =
mechanism within the TFMTF protocol =
itself.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Muthu: =
&#8220;#3 many not require much =
specification.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>2.- Should we include it in the Charter =
now?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Of course, Document (A) should be in the =
charter.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Best regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_006B_01CDF317.463C3280--


From jsaldana@unizar.es  Tue Jan 15 02:56:31 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F291821F85E8 for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:56:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jGWkPtaMleiD for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:56:28 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id F12F721F859D for <tcmtf@ietf.org>; Tue, 15 Jan 2013 02:56:27 -0800 (PST)
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 r0FAuN1o028315 for <tcmtf@ietf.org>; Tue, 15 Jan 2013 11:56:24 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Tue, 15 Jan 2013 11:56:27 +0100
Organization: Universidad de Zaragoza
Message-ID: <007b01cdf30e$f7d3b170$e77b1450$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_007C_01CDF317.599A8A70"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3zAd2uYPABnQrZRziFoMS7yxCKNw==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] TCMTF: Document B discussion: content and charter
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, 15 Jan 2013 10:56:31 -0000

This is a multipart message in MIME format.

------=_NextPart_000_007C_01CDF317.599A8A70
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Document (B) refers to the informational draft about maximum tolerable
delays, currently in
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/

=20

1.- Content of the Document

=20

Currently, the Document specifies the maximum added delays for different
services.

=20

However, the discussion has set clear that other things should be added,
mainly methods for identifying the flows:

=20

Michael: =93has any detailed thought about how TCMTF might identify =
which
flows it should NOT attempt to compress?

Considering "the Internet of things" (where virtually every device is
connected via IP) ... we can expect a lot of small packets ... but not
necessarily know if we should compress them or not (e.g., FPS packets) =
...
or what the delay bounds on the compression should be.

Should we mention that flows that signal their own traffic class (e.g.,
using "Metadata" describing the flow) is a good thing to differentiate =
on?
Should we suggest signature analysis (a probabilistic guess for the
application based on its time-domain signature characteristics) might =
also
be of utility?=94

=20

Fernando had another opinion: =93On the other hand,  the selection of =
flows to
be potentially TCMTFed could be something undefined at the beginning (it =
may
be statically configured for example), but it is something that will =
NEED to
be defined to be dynamically enforced at the mux from a higher entity
(policy manager). That functionality would be addressed to a different =
draft
in the future, re-chartering the WG.=94

=20

Jose: =93Perhaps a "natural" way could be widening the scope of draft =
(B),
including not only delay limits, but also currently existing traffic
classification methods which could be useful for selecting the packets =
to
multiplex. Does this sound well?=94

=20

Mirko: =93I think there is no need to develop something for traffic
classification in the scope of TCMTF WG. There is a large research =
community
doing traffic classification and some of the already developed =
techniques
can be applied for our need. It may be feasible to present an overview =
of
techniques which could be used by TCMTF in draft B.=94

=20

Luigi: =93There are tons of classification methods out there, developing =
a new
one does not look very useful to me.=94

=20

Michael: =93I agree with Luigi and Mirko ... there are more than enough =
people
working on traffic flow descriptions ... and how to signal/inform =
networks
of their requirements (e.g., per-hop behaviors and the like). (=85) For =
now, I
would recommend a placeholder in the draft that addresses the concern =
and
that TCMTF SHOULD consider the traffic class of the flows when such
information is available.=94

=20

So perhaps the solution could be widening the scope of the Document (B) =
in
order to also include:

                - TCMTF SHOULD consider the traffic class of the flows =
when
such information is available

                - Suggesting traffic classification methods which could =
be
useful in order to do this=20

=20

What do you think? Is everyone ok with this?

=20

=20

=20

2.- Should we include it in the Charter now?

=20

Of course, Document (B) should be included in the Charter.

=20

=20

Best regards,

=20

Jose

=20

=20

Jose Saldana, PhD

Communications Technologies Group (GTC)
Dpt. Electrical Engineering and Communications
EINA, University of Zaragoza.
C/ Mar=EDa de Luna 1, Edif. Ada Byron, D. 2.05
50018 Zaragoza, Spain

Tel: +34 976 76 2698

Ext: 2698

E-mail:  <mailto:jsaldana@unizar.es> jsaldana@unizar.es

 <http://diec.unizar.es/~jsaldana/personal/index.htm>
http://diec.unizar.es/~jsaldana/personal/index.htm

=20


------=_NextPart_000_007C_01CDF317.599A8A70
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.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=3DMsoNormal><span =
lang=3DEN-US>Document (B) refers to the informational draft about =
maximum tolerable delays, currently in <a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a><o:p=
></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>1.- Content of the Document<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Currently, the Document specifies =
the maximum added delays for different services.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>However, the discussion has set =
clear that other things should be added, mainly methods for identifying =
the flows:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'text-indent:35.4pt'><span lang=3DEN-US>Michael: &#8220;has any =
detailed thought about how TCMTF might identify which flows it should =
NOT attempt to compress?<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.4pt'><span lang=3DEN-US>Considering &quot;the =
Internet of things&quot; (where virtually every device is connected via =
IP) ... we can expect a lot of small packets ... but not necessarily =
know if we should compress them or not (e.g., FPS packets) ... or what =
the delay bounds on the compression should be.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:35.4pt'><span lang=3DEN-US>Should =
we mention that flows that signal their own traffic class (e.g., using =
&quot;Metadata&quot; describing the flow) is a good thing to =
differentiate on? Should we suggest signature analysis (a probabilistic =
guess for the application based on its time-domain signature =
characteristics) might also be of =
utility?&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Fernando had another =
opinion: &#8220;On the other hand,=A0 the selection of flows to be =
potentially TCMTFed could be something undefined at the beginning (it =
may be statically configured for example), but it is something that will =
NEED to be defined to be dynamically enforced at the mux from a higher =
entity (policy manager). That functionality would be addressed to a =
different draft in the future, re-chartering the =
WG.&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Jose: &#8220;Perhaps a =
&quot;natural&quot; way could be widening the scope of draft (B), =
including not only delay limits, but also currently existing traffic =
classification methods which could be useful for selecting the packets =
to multiplex. Does this sound well?&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Mirko: &#8220;I think =
there is no need to develop something for traffic classification in the =
scope of TCMTF WG. There is a large research community doing traffic =
classification and some of the already developed techniques can be =
applied for our need. It may be feasible to present an overview of =
techniques which could be used by TCMTF in draft =
B.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Luigi: &#8220;There are =
tons of classification methods out there, developing a new one does not =
look very useful to me.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Michael: &#8220;I agree =
with Luigi and Mirko ... there are more than enough people working on =
traffic flow descriptions ... and how to signal/inform networks of their =
requirements (e.g., per-hop behaviors and the like). (&#8230;) For now, =
I would recommend a placeholder in the draft that addresses the concern =
and that TCMTF SHOULD consider the traffic class of the flows when such =
information is available.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>So perhaps the solution could be widening the scope of the =
Document (B) in order to also include:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - TCMTF =
SHOULD consider the traffic class of the flows when such information is =
available<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 - Suggesting =
traffic classification methods which could be useful in order to do this =
<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>What do you think? Is everyone ok with =
this?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>2.- Should we include it in the Charter =
now?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Of course, Document (B) should be included in the =
Charter.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Best regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'>Jose Saldana, PhD</span><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:ES'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'>Communications Technologies Group (GTC)<br>Dpt. Electrical =
Engineering and Communications<br>EINA, University of =
Zaragoza.<br></span><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'>C/ Mar=EDa de Luna 1, Edif. Ada Byron, D. 2.05<br>50018 =
Zaragoza, Spain</span><span =
style=3D'mso-fareast-language:ES'><o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'>Tel: +34 976 76 2698</span><span =
style=3D'mso-fareast-language:ES'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'>Ext: 2698</span><span lang=3DEN-US =
style=3D'mso-fareast-language:ES'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'>E-mail: </span><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'><a href=3D"mailto:jsaldana@unizar.es"><span lang=3DEN-US =
style=3D'color:blue'>jsaldana@unizar.es</span></a></span><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'><a =
href=3D"http://diec.unizar.es/~jsaldana/personal/index.htm"><span =
lang=3DEN-US =
style=3D'color:blue'>http://diec.unizar.es/~jsaldana/personal/index.htm</=
span></a></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_007C_01CDF317.599A8A70--


From jsaldana@unizar.es  Tue Jan 15 02:56:44 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2850421F85E8 for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:56:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XumskUnJuUWZ for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:56:43 -0800 (PST)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0AF5421F8578 for <tcmtf@ietf.org>; Tue, 15 Jan 2013 02:56:42 -0800 (PST)
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 r0FAuerI001885 for <tcmtf@ietf.org>; Tue, 15 Jan 2013 11:56:40 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Tue, 15 Jan 2013 11:56:42 +0100
Organization: Universidad de Zaragoza
Message-ID: <008601cdf30f$0105f8c0$0311ea40$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0087_01CDF317.62CA60C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3zAaWdu17ID/aOR5mMJnwF9rLUGQ==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] TCMTF: Document C discussion: content and charter
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, 15 Jan 2013 10:56:44 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0087_01CDF317.62CA60C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Document (C) may refer to a new document about signaling

 

1.- Content of the Document

 

#2. A mechanism to *elect an optimal muxer and a de-muxer when there are
more than one muxer/de-muxer for a flow*.

 

We agree: This can wait for Document C.

 

                Fernando: "#2 is more related to the higher entity that has
to decide whether a flow should be TCMTFed or not, and under my point of
view it can be addressed in a different draft."

                Muthu: "#2 can be added later."

 

 

2.- Should we include it in the Charter now?

 

I think we shouldn't include this in the charter as an objective. It can be
included in one of the last paragraphs.

 

Best regards,

 

Jose

 


------=_NextPart_000_0087_01CDF317.62CA60C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
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=3DMsoNormal><span =
lang=3DEN-US>Document (C) may refer to a new document about =
signaling<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>1.- Content of the Document<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>#2. A mechanism to *<b>elect an =
optimal muxer and a de-muxer when there are more than one muxer/de-muxer =
for a flow</b>*.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>We agree: This can wait for Document =
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>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fernando: &#8220;#2 is more related to =
the higher entity that has to decide whether a flow should be TCMTFed or =
not, and under my point of view it can be addressed in a different =
draft.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu: &#8220;#2 can be added =
later.&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>2.- Should we include it in the Charter =
now?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>I think we shouldn&#8217;t include this in the charter as =
an objective. It can be included in one of the last =
paragraphs.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Best regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_0087_01CDF317.62CA60C0--


From jsaldana@unizar.es  Tue Jan 15 02:57:12 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FFA421F860A for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:57:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXuUFn3WpsWd for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:57:11 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id E66F921F85E8 for <tcmtf@ietf.org>; Tue, 15 Jan 2013 02:57:10 -0800 (PST)
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 r0FAv5A0002477 for <tcmtf@ietf.org>; Tue, 15 Jan 2013 11:57:05 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Tue, 15 Jan 2013 11:57:10 +0100
Organization: Universidad de Zaragoza
Message-ID: <009101cdf30f$11a3aa10$34eafe30$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0092_01CDF317.73681210"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3zAInvJKT5v2C/Rt6kO+6MBryW0w==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] TCMTF: Document D discussion: content and charter
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, 15 Jan 2013 10:57:12 -0000

This is a multipart message in MIME format.

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

Document (D) refers to the proposal of Matteo and Tomasso (the "DLR" draft)

 

1.- Content of the Document

 

As Matteo says, it "is not just constrained to satellites, it applies to all
wireless access mediums in general. Since on these wireless access mediums,
header compression is desirable but it has to be terminated at the access
point, the idea is to extend it to the backbone by exploiting a modification
of TCMTF."

 

2.- Should we include it in the Charter now?

 

I think we agree on not including it in the Charter now. Since we are
talking about a "modification of TCMTF" or a very specific application, we
should wait until TCMTF is mature enough before this.

 

And my proposal is to cite the problem in this paragraph of the Charter:

 

7. If other interesting features are identified, the group would recharter
and include them (.). *In addition, specific uses of TCMTF, such as wireless
and satellite scenarios could be addressed if some modifications are
required on the protocol.*

 

 

Of course, as Diego says: "I don't see any harm in the DLR guys progressing
with the satellite scenario. As Mirko says, we can include in the charter
the scenario once we have a mature draft." So a first version of the draft,
with a description of the scenarios and the problem could be really
interesting in order to get a better idea of it."

 

 

Best regards,

 

Jose

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:"Calibri","sans-serif";}
span.EstiloCorreo19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>Document (D) refers to the proposal of Matteo and Tomasso =
(the &#8220;DLR&#8221; draft)<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>1.- Content of the =
Document<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>As Matteo says, it &#8220;is not just constrained to =
satellites, it applies to all wireless access mediums in general. Since =
on these wireless access mediums, header compression is desirable but it =
has to be terminated at the access point, the idea is to extend it to =
the backbone by exploiting a modification of =
TCMTF.&#8221;<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.- Should we include it in the Charter =
now?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>I think we agree on not including it in the Charter now. =
Since we are talking about a &#8220;modification of TCMTF&#8221; or a =
very specific application, we should wait until TCMTF is mature enough =
before this.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>And my proposal is to cite the problem in this paragraph of =
the Charter:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>7. If other interesting features are identified, the group =
would recharter and include them (&#8230;). *<b>In addition, specific =
uses of TCMTF, such as wireless and satellite scenarios could be =
addressed if some modifications are required on the =
protocol.</b>*<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Of course, as Diego says: &#8220;I don't see any harm in =
the DLR guys progressing with the satellite scenario. As Mirko says, we =
can include in the charter the scenario once we have a mature =
draft.&#8221; So a first version of the draft, with a description of the =
scenarios and the problem could be really interesting in order to get a =
better idea of it.&#8221;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Best =
regards,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0092_01CDF317.73681210--


From jsaldana@unizar.es  Tue Jan 15 02:57:29 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E2EC21F860A for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:57:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2R1w1Sdgpj4K for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:57:28 -0800 (PST)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0124121F85BC for <tcmtf@ietf.org>; Tue, 15 Jan 2013 02:57:27 -0800 (PST)
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 r0FAvOfP002591 for <tcmtf@ietf.org>; Tue, 15 Jan 2013 11:57:24 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Tue, 15 Jan 2013 11:57:27 +0100
Organization: Universidad de Zaragoza
Message-ID: <009c01cdf30f$1b991a50$52cb4ef0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_009D_01CDF317.7D5D8250"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3zAJryV5Ji6TcZRyiQIkx7FlKoAA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] TCMTF: Document E discussion: content and charter
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, 15 Jan 2013 10:57:29 -0000

This is a multipart message in MIME format.

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

Document (E) may refer to a document about LISP and TCMTF

 

1.- Content of the Document

 

It seems that LISP and TCMTF can work together, and present some synergies,
we could think about a specific "experimental" draft. It could be done
within the LISP WG or within the TCMTF WG (if created). Perhaps it would
make more sense in the LISP WG.

 

Luigi: "Well, it really depends on how the TCMTF evolves. However, you are
right that there is no space for LISP in (A) and is worth to wait a little
bit before going forward on this path."

 

 

2.- Should we include it in the Charter now?

 

Clearly, we should not include it now. The problem is that LISP is
experimental.

 

I think this would have to wait a little. Before, we would need to:

 

- Better explore the synergies between LISP and TCMTF

 

- Have a clearer idea of TCMTF, I mean, move some steps towards the
standardization. 

 

 

Best regards,

 

Jose

 


------=_NextPart_000_009D_01CDF317.7D5D8250
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:"Calibri","sans-serif";}
span.EstiloCorreo19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>Document (E) may refer to a document about LISP and =
TCMTF<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>1.- Content of the Document<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>It seems that LISP and TCMTF can =
work together, and present some synergies, we could think about a =
specific &#8220;experimental&#8221; draft. It could be done within the =
LISP WG or within the TCMTF WG (if created). Perhaps it would make more =
sense in the LISP WG.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Luigi: &#8220;Well, it really depends on how the TCMTF =
evolves. However, you are right that there is no space for LISP in (A) =
and is worth to wait a little bit before going forward on this =
path.&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>2.- Should we include it in the Charter =
now?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Clearly, we should not include it now. The problem is that =
LISP is experimental.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>I think this would have to wait a little. Before, we would =
need to:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- Better explore the synergies between LISP and =
TCMTF<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- Have a clearer idea of TCMTF, I mean, move some steps =
towards the standardization. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Best =
regards,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jose<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_009D_01CDF317.7D5D8250--


From mns@tid.es  Tue Jan 15 04:15:46 2013
Return-Path: <mns@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9919521F87CE for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 04:15:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XAuVANZh8Rzg for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 04:15:43 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 394D821F873C for <tcmtf@ietf.org>; Tue, 15 Jan 2013 04:15:41 -0800 (PST)
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 <0MGO0026122112@tid.hi.inet> for tcmtf@ietf.org; Tue, 15 Jan 2013 13:15:39 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id D7.81.03184.B6845F05; Tue, 15 Jan 2013 13:15:39 +0100 (CET)
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 <0MGO0026D22312@tid.hi.inet> for tcmtf@ietf.org; Tue, 15 Jan 2013 13:15:39 +0100 (MET)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.151]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0318.004; Tue, 15 Jan 2013 13:15:38 +0100
Date: Tue, 15 Jan 2013 12:15:38 +0000
From: =?iso-8859-1?Q?MANUEL_NU=D1EZ_SANZ?= <mns@tid.es>
In-reply-to: <007b01cdf30e$f7d3b170$e77b1450$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <90ED8822CB577741B9A1668A47539312316DD456@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_ch3j3hNolZJIJtOkQ/ojuA)"
Content-language: es-ES
Accept-Language: es-ES, en-US
Thread-topic: [tcmtf] TCMTF: Document B discussion: content and charter
Thread-index: Ac3zAd2uYPABnQrZRziFoMS7yxCKNwAEJgsA
X-AuditID: 0a5f4068-b7fc06d000000c70-2a-50f5486b23ab
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDKsWRmVeSWpSXmKPExsXCFe/ApZvt8TXAoP2loMWuzxsYHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVcfvYQqaC7nmMFe0vulkbGHs6GbsYOTkkBEwknh9tZoGwxSQu 3FvP1sXIxSEksIFRYu2eo4wQzg9Gif+nVzJBODMZJa5/ms8O0sIioCrxfM0doAQHB5uAuUTf Oh4QU1jATWJjjyBIBaeAhcTa/nvMEAsUJP6cewy2TEQgQGJ3ywEwm1fAW+LnuR5GCFtQ4sfk eywgY5gFciWefRAFCTMLiEvM+TWRFcRmFJCVWHn+NCPEGHeJ27svQY00krj88RAbxCoBiSV7 zkOtFZV4+fgfWK8Q0JGnL79lncAoOgvJtlkI22Yh2QZh60ncmDqFDcLWlli28DUzhK0rMePf IRZk8QWM7KsYxYqTijLTM0pyEzNz0g0M9TIy9TLzUks2MUKiK2MH4/KdKocYBTgYlXh4D5z9 HCDEmlhWXJl7iFGSg0lJlLfK/WuAEF9SfkplRmJxRnxRaU5q8SFGCQ5mJRFeDSOgHG9KYmVV alE+TEqGg0NJgrcMpE2wKDU9tSItMweYQmDSTBycIO08QO1HQWp4iwsSc4sz0yHypxhVOVoO dD9nFGLJy89LlRLnvQBSJABSlFGaBzfnFaM40MHCvI9AsjzAJAg34RXQcCag4Zv2fgYZXpKI kJJqYHTkrJq2un5W7lYXK58dJ47X/LP7YFJioty5YW32ovieo+F/WbdVaedvuS/o/3DKhIwD s1/5i9Z2Lr7VuO2tSzbT920Kvw57XXstcsO/tDDTLvn22Uvm9jZd6yLier5s0hOvuBQw5aY5 06K934J2rnknwTN7+mcVZ00XiR3Sl7yPC9gEvNKO2K3EUpyRaKjFXFScCACsg1xEPwMAAA==
References: <007b01cdf30e$f7d3b170$e77b1450$@unizar.es>
Subject: Re: [tcmtf] TCMTF: Document B discussion: content and charter
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, 15 Jan 2013 12:15:46 -0000

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

Hi,
  I am going to do one=B4s bit.

It is true there are tons of classification methods, however the issue is t=
hat:

1.       It is not common its use, and therefore it is reasonable to suppos=
e a lot of packets/flows will not be classified.

2.       And even when a flow is classified, it is possible than that class=
ification does not identify the delays for that flow.


Therefore under my opinion (quite similar to Fernando) is that it is necess=
ary the MUX "obtain" the configuration to know than flow are TCMTFed. In th=
at line, there are three different approaches:

1.       A static configuration (as an initial state)

2.       A policy manager dynamically enforces the option for each new flow

3.       The MUX asks for instruction for each "new" flow to an "policy man=
ager" or "controller". This last options is fully compatible with the 2 opt=
ion.

And answering the question about open the scope of document B. I agree.

Regards,
  Manuel N=FA=F1ez


De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de Jos=
e Saldana
Enviado el: martes, 15 de enero de 2013 11:56
Para: tcmtf@ietf.org
Asunto: [tcmtf] TCMTF: Document B discussion: content and charter

Document (B) refers to the informational draft about maximum tolerable dela=
ys, currently in http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-=
tcmtf/

1.- Content of the Document

Currently, the Document specifies the maximum added delays for different se=
rvices.

However, the discussion has set clear that other things should be added, ma=
inly methods for identifying the flows:


Michael: "has any detailed thought about how TCMTF might identify which flo=
ws it should NOT attempt to compress?

Considering "the Internet of things" (where virtually every device is conne=
cted via IP) ... we can expect a lot of small packets ... but not necessari=
ly know if we should compress them or not (e.g., FPS packets) ... or what t=
he delay bounds on the compression should be.
Should we mention that flows that signal their own traffic class (e.g., usi=
ng "Metadata" describing the flow) is a good thing to differentiate on? Sho=
uld we suggest signature analysis (a probabilistic guess for the applicatio=
n based on its time-domain signature characteristics) might also be of util=
ity?"

Fernando had another opinion: "On the other hand,  the selection of flows t=
o be potentially TCMTFed could be something undefined at the beginning (it =
may be statically configured for example), but it is something that will NE=
ED to be defined to be dynamically enforced at the mux from a higher entity=
 (policy manager). That functionality would be addressed to a different dra=
ft in the future, re-chartering the WG."


Jose: "Perhaps a "natural" way could be widening the scope of draft (B), in=
cluding not only delay limits, but also currently existing traffic classifi=
cation methods which could be useful for selecting the packets to multiplex=
. Does this sound well?"



Mirko: "I think there is no need to develop something for traffic classific=
ation in the scope of TCMTF WG. There is a large research community doing t=
raffic classification and some of the already developed techniques can be a=
pplied for our need. It may be feasible to present an overview of technique=
s which could be used by TCMTF in draft B."



Luigi: "There are tons of classification methods out there, developing a ne=
w one does not look very useful to me."



Michael: "I agree with Luigi and Mirko ... there are more than enough peopl=
e working on traffic flow descriptions ... and how to signal/inform network=
s of their requirements (e.g., per-hop behaviors and the like). (...) For n=
ow, I would recommend a placeholder in the draft that addresses the concern=
 and that TCMTF SHOULD consider the traffic class of the flows when such in=
formation is available."



So perhaps the solution could be widening the scope of the Document (B) in =
order to also include:

                - TCMTF SHOULD consider the traffic class of the flows when=
 such information is available

                - Suggesting traffic classification methods which could be =
useful in order to do this



What do you think? Is everyone ok with this?






2.- Should we include it in the Charter now?

Of course, Document (B) should be included in the Charter.


Best regards,

Jose


Jose Saldana, PhD
Communications Technologies Group (GTC)
Dpt. Electrical Engineering and Communications
EINA, University of Zaragoza.
C/ Mar=EDa de Luna 1, Edif. Ada Byron, D. 2.05
50018 Zaragoza, Spain
Tel: +34 976 76 2698
Ext: 2698
E-mail: jsaldana@unizar.es<mailto:jsaldana@unizar.es>
http://diec.unizar.es/~jsaldana/personal/index.htm


________________________________

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_ch3j3hNolZJIJtOkQ/ojuA)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style>
<!--
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","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.TextosinformatoCar
	{font-family:"Calibri","sans-serif"}
span.EstiloCorreo19
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.EstiloCorreo20
	{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
	{}
ol
	{margin-bottom:0cm}
ul
	{margin-bottom:0cm}
-->
</style>
</head>
<body lang=3D"ES" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi, </s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;I am going to do one=B4s bit.
</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">It is t=
rue there are tons of classification methods, however the issue is that:</s=
pan></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt"><span lang=3D"E=
N-US" style=3D"color:#1F497D"><span style=3D"">1.<span style=3D"font:7.0pt =
&quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN-US" style=3D"color:#1F497D">It is not=
 common its use, and therefore it is reasonable to suppose a lot of packets=
/flows will not be classified.</span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt"><span lang=3D"E=
N-US" style=3D"color:#1F497D"><span style=3D"">2.<span style=3D"font:7.0pt =
&quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN-US" style=3D"color:#1F497D">And even =
when a flow is classified, it is possible than that classification does not=
 identify the delays for that flow.</span></p>
<p class=3D"MsoListParagraph"><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">Therefo=
re under my opinion (quite similar to Fernando) is that it is necessary the=
 MUX &#8220;obtain&#8221; the configuration to know than flow are TCMTFed. =
In that line, there are three different approaches:</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:38.25pt; text-indent:-18=
.0pt"><span lang=3D"EN-US" style=3D"color:#1F497D"><span style=3D"">1.<span=
 style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
</span></span></span><span lang=3D"EN-US" style=3D"color:#1F497D">A static =
configuration (as an initial state)</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:38.25pt; text-indent:-18=
.0pt"><span lang=3D"EN-US" style=3D"color:#1F497D"><span style=3D"">2.<span=
 style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
</span></span></span><span lang=3D"EN-US" style=3D"color:#1F497D">A policy =
manager dynamically enforces the option for each new flow</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:38.25pt; text-indent:-18=
.0pt"><span lang=3D"EN-US" style=3D"color:#1F497D"><span style=3D"">3.<span=
 style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
</span></span></span><span lang=3D"EN-US" style=3D"color:#1F497D">The MUX a=
sks for instruction for each &#8220;new&#8221; flow to an &#8220;policy man=
ager&#8221; or &#8220;controller&#8221;. This last options is fully compati=
ble with the 2 option.</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">And ans=
wering the question about open the scope of document B. I agree.
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regards=
, </span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;Manuel N=FA=F1ez</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>
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0c=
m 0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt; font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">De:</span></b><span style=3D"font-si=
ze:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tcmtf-bo=
unces@ietf.org [mailto:tcmtf-bounces@ietf.org]
<b>En nombre de </b>Jose Saldana<br>
<b>Enviado el:</b> martes, 15 de enero de 2013 11:56<br>
<b>Para:</b> tcmtf@ietf.org<br>
<b>Asunto:</b> [tcmtf] TCMTF: Document B discussion: content and charter</s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Document (B) refers to the info=
rmational draft about maximum tolerable delays, currently in
<a href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/=
">http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">1.- Content of the Document</sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Currently, the Document specifi=
es the maximum added delays for different services.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">However, the discussion has set=
 clear that other things should be added, mainly methods for identifying th=
e flows:</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"text-indent:35.4pt"><span lang=3D"EN-US"=
>Michael: &#8220;has any detailed thought about how TCMTF might identify wh=
ich flows it should NOT attempt to compress?</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span lang=3D"EN-US"=
>Considering &quot;the Internet of things&quot; (where virtually every devi=
ce is connected via IP) ... we can expect a lot of small packets ... but no=
t necessarily know if we should compress them or
 not (e.g., FPS packets) ... or what the delay bounds on the compression sh=
ould be.</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lang=3D"EN-US">Sh=
ould we mention that flows that signal their own traffic class (e.g., using=
 &quot;Metadata&quot; describing the flow) is a good thing to differentiate=
 on? Should we suggest signature analysis (a probabilistic
 guess for the application based on its time-domain signature characteristi=
cs) might also be of utility?&#8221;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.25pt"><span lang=3D"EN-US">F=
ernando had another opinion: &#8220;On the other hand,&nbsp; the selection =
of flows to be potentially TCMTFed could be something undefined at the begi=
nning (it may be statically configured for example),
 but it is something that will NEED to be defined to be dynamically enforce=
d at the mux from a higher entity (policy manager). That functionality woul=
d be addressed to a different draft in the future, re-chartering the WG.&#8=
221;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Jose: &#8220;Perhaps a &quot;natural&quot; way could be widening the scop=
e of draft (B), including not only delay limits, but also currently existin=
g traffic classification methods which could be useful
 for selecting the packets to multiplex. Does this sound well?&#8221;</span=
></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Mirko: &#8220;I think there is no need to develop something for traffic c=
lassification in the scope of TCMTF WG. There is a large research community=
 doing traffic classification and some of the
 already developed techniques can be applied for our need. It may be feasib=
le to present an overview of techniques which could be used by TCMTF in dra=
ft B.&#8221;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Luigi: &#8220;There are tons of classification methods out there, develop=
ing a new one does not look very useful to me.&#8221;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Michael: &#8220;I agree with Luigi and Mirko ... there are more than enou=
gh people working on traffic flow descriptions ... and how to signal/inform=
 networks of their requirements (e.g., per-hop
 behaviors and the like). (&#8230;) For now, I would recommend a placeholde=
r in the draft that addresses the concern and that TCMTF SHOULD consider th=
e traffic class of the flows when such information is available.&#8221;</sp=
an></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">So perhaps the solution coul=
d be widening the scope of the Document (B) in order to also include:</span=
></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - TCMTF SHOU=
LD consider the traffic class of the flows when such information is availab=
le</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Suggesting=
 traffic classification methods which could be useful in order to do this
</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">What do you think? Is everyo=
ne ok with this?</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">2.- Should we include it in =
the Charter now?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Of course, Document (B) should =
be included in the Charter.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Best regards,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jose</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Jose Saldana, PhD</span><=
span lang=3D"EN-US" style=3D"font-size:12.0pt; font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Communications Technologi=
es Group (GTC)<br>
Dpt. Electrical Engineering and Communications<br>
EINA, University of Zaragoza.<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;">C/ Mar=EDa de Luna 1, Edif. Ada Byron, D. 2.05<br>
50018 Zaragoza, Spain</span><span style=3D""></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;A=
rial&quot;,&quot;sans-serif&quot;">Tel: &#43;34 976 76 2698</span><span sty=
le=3D""></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Ext: 2698</span><span lan=
g=3D"EN-US" style=3D""></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;">E-mail:
</span><span style=3D"font-size:10.0pt; font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;"><a href=3D"mailto:jsaldana@unizar.es"><span lang=3D"EN-U=
S">jsaldana@unizar.es</span></a></span><span lang=3D"EN-US" style=3D"font-s=
ize:10.0pt; font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;A=
rial&quot;,&quot;sans-serif&quot;"><a href=3D"http://diec.unizar.es/~jsalda=
na/personal/index.htm"><span lang=3D"EN-US">http://diec.unizar.es/~jsaldana=
/personal/index.htm</span></a></span><span lang=3D"EN-US" style=3D"font-siz=
e:10.0pt; font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_ch3j3hNolZJIJtOkQ/ojuA)--

From fpb@tid.es  Tue Jan 15 06:05:56 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AC3821F88F5 for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 06:05:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.158
X-Spam-Level: 
X-Spam-Status: No, score=-6.158 tagged_above=-999 required=5 tests=[AWL=0.140,  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 sU6xPAfMsUAN for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 06:05:55 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 8F42F21F889C for <tcmtf@ietf.org>; Tue, 15 Jan 2013 06:05:52 -0800 (PST)
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 <0MGO0067975RNY@tid.hi.inet> for tcmtf@ietf.org; Tue, 15 Jan 2013 15:05:51 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id CA.D4.02896.E3265F05; Tue, 15 Jan 2013 15:05:50 +0100 (CET)
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 <0MGO0067575QNY@tid.hi.inet> for tcmtf@ietf.org; Tue, 15 Jan 2013 15:05:50 +0100 (MET)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.151]) by ex10-htcas3-mad.hi.inet ([::1]) with mapi id 14.02.0328.009; Tue, 15 Jan 2013 15:02:46 +0100
Date: Tue, 15 Jan 2013 14:05:49 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <90ED8822CB577741B9A1668A47539312316DD456@EX10-MB1-MAD.hi.inet>
X-Originating-IP: [10.95.64.115]
To: =?Windows-1252?Q?MANUEL_NU=D1EZ_SANZ?= <mns@tid.es>, "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A265041303@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_l2cezDmdXVpO8FJ5nH6mwA)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: [tcmtf] TCMTF: Document B discussion: content and charter
Thread-index: Ac3zAd2uYPABnQrZRziFoMS7yxCKNwAEJgsAAAW9d4A=
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4e69-b7f636d000000b50-1e-50f5623ed60b
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrJKsWRmVeSWpSXmKPExsXCFe9nqGuX9DXA4PAXK4tdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoErY8rjZUwFd/czViy7qtHAuH8ZYxcjB4eEgInEtDXWXYycQKaY xIV769m6GLk4hAS2MUq82LmHBcL5wSjx6sFKdghnJqPEh7O9YN0sAqoSffdVQbrZBLQkTt9d xQJiCwu4Sazd0c0MYnMK+Ei0rd3CCLFBQeLPucdgQ0UE2oHmdN9nBZnDK+At8eSbIUgNr4Cg xI/J98DmMAvkSmya850VwhaXaG69CRZnBLr0+6k1TCC2iIC7xO3dl1ggbCuJWycesYPYogJ6 Em3HzrBD7BWQWLLnPDOELSrx8vE/1gmMorOQrJuFZN0sJOsgbAOJ9+fmM0PY2hLLFr6GsvUl Nn45ywhhm0mcaFzPgqxmASPHKkax4qSizPSMktzEzJx0AyO9jEy9zLzUkk2MkLjL3MG4fKfK IUYBDkYlHt4DZz8HCLEmlhVX5h5ilORgUhLljYz8GiDEl5SfUpmRWJwRX1Sak1p8iFGCg1lJ hFfDCCjHm5JYWZValA+TkuHgUJLglUkESgkWpaanVqRl5gCTC0yaiYMTpJ0HqF0JpIa3uCAx tzgzHSJ/ilGVo+VA93NGIZa8/LxUKXHePwlARQIgRRmleXBzXjGKAx0szOsGMoIHmB7hJrwC Gs4ENHzT3s8gw0sSEVJSDYzpf61UVpQk5sltUeVef+9pZKlj82tztxsKh8tbd7/ovRlSZJp4 Ks2V0+6ExPazO96sqnm2qZTtg8Os67rnMlT/tL86zP+79V1q0Nevxd/a2+3NXsptOX98a29p ySzRzniZb/Enws2un++4sDRX3Vf2094dbVcPH3rpIvv5qNgMsel3v39tvhamxFKckWioxVxU nAgAo+bAx0wDAAA=
Subject: Re: [tcmtf] TCMTF: Document B discussion: content and charter
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, 15 Jan 2013 14:05:56 -0000

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

Hi all,

What if we define both?

  1.  What Manuel explained in points 2 and 3 (dynamic enforcement of the T=
CMTF optimization): a northbound interface to do that
  2.  To apply TCMTF optimization based on inline signaling (signaling with=
in the data, as Traffic Class or metadata)

Could both things be defined, and give preference to one of them?

Regards,

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

From: "mns@tid.es<mailto:mns@tid.es>" <mns@tid.es<mailto:mns@tid.es>>
Date: martes, 15 de enero de 2013 13:15
To: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.es<mai=
lto:jsaldana@unizar.es>>, "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ie=
tf.org<mailto:tcmtf@ietf.org>>
Subject: Re: [tcmtf] TCMTF: Document B discussion: content and charter

Hi,
  I am going to do one=B4s bit.

It is true there are tons of classification methods, however the issue is t=
hat:

1.       It is not common its use, and therefore it is reasonable to suppos=
e a lot of packets/flows will not be classified.

2.       And even when a flow is classified, it is possible than that class=
ification does not identify the delays for that flow.


Therefore under my opinion (quite similar to Fernando) is that it is necess=
ary the MUX =93obtain=94 the configuration to know than flow are TCMTFed. I=
n that line, there are three different approaches:

1.       A static configuration (as an initial state)

2.       A policy manager dynamically enforces the option for each new flow

3.       The MUX asks for instruction for each =93new=94 flow to an =93poli=
cy manager=94 or =93controller=94. This last options is fully compatible wi=
th the 2 option.

And answering the question about open the scope of document B. I agree.

Regards,
  Manuel N=FA=F1ez


De: tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-bou=
nces@ietf.org] En nombre de Jose Saldana
Enviado el: martes, 15 de enero de 2013 11:56
Para: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: [tcmtf] TCMTF: Document B discussion: content and charter

Document (B) refers to the informational draft about maximum tolerable dela=
ys, currently in http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-=
tcmtf/

1.- Content of the Document

Currently, the Document specifies the maximum added delays for different se=
rvices.

However, the discussion has set clear that other things should be added, ma=
inly methods for identifying the flows:


Michael: =93has any detailed thought about how TCMTF might identify which f=
lows it should NOT attempt to compress?

Considering "the Internet of things" (where virtually every device is conne=
cted via IP) ... we can expect a lot of small packets ... but not necessari=
ly know if we should compress them or not (e.g., FPS packets) ... or what t=
he delay bounds on the compression should be.
Should we mention that flows that signal their own traffic class (e.g., usi=
ng "Metadata" describing the flow) is a good thing to differentiate on? Sho=
uld we suggest signature analysis (a probabilistic guess for the applicatio=
n based on its time-domain signature characteristics) might also be of util=
ity?=94

Fernando had another opinion: =93On the other hand,  the selection of flows=
 to be potentially TCMTFed could be something undefined at the beginning (i=
t may be statically configured for example), but it is something that will =
NEED to be defined to be dynamically enforced at the mux from a higher enti=
ty (policy manager). That functionality would be addressed to a different d=
raft in the future, re-chartering the WG.=94


Jose: =93Perhaps a "natural" way could be widening the scope of draft (B), =
including not only delay limits, but also currently existing traffic classi=
fication methods which could be useful for selecting the packets to multipl=
ex. Does this sound well?=94



Mirko: =93I think there is no need to develop something for traffic classif=
ication in the scope of TCMTF WG. There is a large research community doing=
 traffic classification and some of the already developed techniques can be=
 applied for our need. It may be feasible to present an overview of techniq=
ues which could be used by TCMTF in draft B.=94



Luigi: =93There are tons of classification methods out there, developing a =
new one does not look very useful to me.=94



Michael: =93I agree with Luigi and Mirko ... there are more than enough peo=
ple working on traffic flow descriptions ... and how to signal/inform netwo=
rks of their requirements (e.g., per-hop behaviors and the like). (=85) For=
 now, I would recommend a placeholder in the draft that addresses the conce=
rn and that TCMTF SHOULD consider the traffic class of the flows when such =
information is available.=94



So perhaps the solution could be widening the scope of the Document (B) in =
order to also include:

                - TCMTF SHOULD consider the traffic class of the flows when=
 such information is available

                - Suggesting traffic classification methods which could be =
useful in order to do this



What do you think? Is everyone ok with this?






2.- Should we include it in the Charter now?

Of course, Document (B) should be included in the Charter.


Best regards,

Jose


Jose Saldana, PhD
Communications Technologies Group (GTC)
Dpt. Electrical Engineering and Communications
EINA, University of Zaragoza.
C/ Mar=EDa de Luna 1, Edif. Ada Byron, D. 2.05
50018 Zaragoza, Spain
Tel: +34 976 76 2698
Ext: 2698
E-mail: jsaldana@unizar.es<mailto:jsaldana@unizar.es>
http://diec.unizar.es/~jsaldana/personal/index.htm


________________________________

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font=
-family:Calibri,sans-serif">
<div>
<div>
<div>Hi all,</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>What i=
f we define both?</div>
<ol>
<li>What Manuel explained in points 2 and 3 (dynamic enforcement of the TCM=
TF optimization): a
<b>northbound interface </b>to do that</li><li>To apply TCMTF optimization =
based on inline signaling (signaling within the data, as Traffic Class or m=
etadata)</li></ol>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span></div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Could =
both things be defined, and give preference to one of them?</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:mns@t=
id.es">mns@tid.es</a>&quot; &lt;<a href=3D"mailto:mns@tid.es">mns@tid.es</a=
>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>martes, 15 de enero de 2013 1=
3:15<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:jsaldan=
a@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsaldana@un=
izar.es">jsaldana@unizar.es</a>&gt;, &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>
<span style=3D"font-weight:bold">Subject: </span>Re: [tcmtf] TCMTF: Documen=
t B discussion: content and charter<br>
</div>
<div><br>
</div>
<div><style>
<!--
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","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.TextosinformatoCar
	{font-family:"Calibri","sans-serif"}
span.EstiloCorreo19
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.EstiloCorreo20
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:70.85pt 3.0cm 70.85pt 3.0cm}
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">Hi, </s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;I am going to do one=B4s bit.
</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">It is t=
rue there are tons of classification methods, however the issue is that:</s=
pan></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt"><span lang=3D"E=
N-US" style=3D"color:#1F497D"><span style=3D"">1.<span style=3D"font-style:=
normal; font-variant:normal; font-weight:normal; font-size:7pt; line-height=
:normal; font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
</span></span></span><span lang=3D"EN-US" style=3D"color:#1F497D">It is not=
 common its use, and therefore it is reasonable to suppose a lot of packets=
/flows will not be classified.</span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt"><span lang=3D"E=
N-US" style=3D"color:#1F497D"><span style=3D"">2.<span style=3D"font-style:=
normal; font-variant:normal; font-weight:normal; font-size:7pt; line-height=
:normal; font-family:'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
</span></span></span><span lang=3D"EN-US" style=3D"color:#1F497D">And even =
when a flow is classified, it is possible than that classification does not=
 identify the delays for that flow.</span></p>
<p class=3D"MsoListParagraph"><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">Therefo=
re under my opinion (quite similar to Fernando) is that it is necessary the=
 MUX =93obtain=94 the configuration to know than flow are TCMTFed. In that =
line, there are three different approaches:</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:38.25pt; text-indent:-18=
.0pt"><span lang=3D"EN-US" style=3D"color:#1F497D"><span style=3D"">1.<span=
 style=3D"font-style:normal; font-variant:normal; font-weight:normal; font-=
size:7pt; line-height:normal; font-family:'Times New Roman'">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN-US" style=3D"color:#1F497D">A static =
configuration (as an initial state)</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:38.25pt; text-indent:-18=
.0pt"><span lang=3D"EN-US" style=3D"color:#1F497D"><span style=3D"">2.<span=
 style=3D"font-style:normal; font-variant:normal; font-weight:normal; font-=
size:7pt; line-height:normal; font-family:'Times New Roman'">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN-US" style=3D"color:#1F497D">A policy =
manager dynamically enforces the option for each new flow</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:38.25pt; text-indent:-18=
.0pt"><span lang=3D"EN-US" style=3D"color:#1F497D"><span style=3D"">3.<span=
 style=3D"font-style:normal; font-variant:normal; font-weight:normal; font-=
size:7pt; line-height:normal; font-family:'Times New Roman'">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;
</span></span></span><span lang=3D"EN-US" style=3D"color:#1F497D">The MUX a=
sks for instruction for each =93new=94 flow to an =93policy manager=94 or =
=93controller=94. This last options is fully compatible with the 2 option.<=
/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">And ans=
wering the question about open the scope of document B. I agree.
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regards=
, </span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;Manuel N=FA=F1ez</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>
<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">
<a href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a hr=
ef=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]
<b>En nombre de </b>Jose Saldana<br>
<b>Enviado el:</b> martes, 15 de enero de 2013 11:56<br>
<b>Para:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tcmtf] TCMTF: Document B discussion: content and charter</s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Document (B) refers to the info=
rmational draft about maximum tolerable delays, currently in
<a href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/=
">http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">1.- Content of the Document</sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Currently, the Document specifi=
es the maximum added delays for different services.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">However, the discussion has set=
 clear that other things should be added, mainly methods for identifying th=
e flows:</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"text-indent:35.4pt"><span lang=3D"EN-US"=
>Michael: =93has any detailed thought about how TCMTF might identify which =
flows it should NOT attempt to compress?</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span lang=3D"EN-US"=
>Considering &quot;the Internet of things&quot; (where virtually every devi=
ce is connected via IP) ... we can expect a lot of small packets ... but no=
t necessarily know if we should compress them or
 not (e.g., FPS packets) ... or what the delay bounds on the compression sh=
ould be.</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lang=3D"EN-US">Sh=
ould we mention that flows that signal their own traffic class (e.g., using=
 &quot;Metadata&quot; describing the flow) is a good thing to differentiate=
 on? Should we suggest signature analysis (a probabilistic
 guess for the application based on its time-domain signature characteristi=
cs) might also be of utility?=94</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.25pt"><span lang=3D"EN-US">F=
ernando had another opinion: =93On the other hand,&nbsp; the selection of f=
lows to be potentially TCMTFed could be something undefined at the beginnin=
g (it may be statically configured for example),
 but it is something that will NEED to be defined to be dynamically enforce=
d at the mux from a higher entity (policy manager). That functionality woul=
d be addressed to a different draft in the future, re-chartering the WG.=94=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Jose: =93Perhaps a &quot;natural&quot; way could be widening the scope of=
 draft (B), including not only delay limits, but also currently existing tr=
affic classification methods which could be useful
 for selecting the packets to multiplex. Does this sound well?=94</span></p=
>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Mirko: =93I think there is no need to develop something for traffic class=
ification in the scope of TCMTF WG. There is a large research community doi=
ng traffic classification and some of the
 already developed techniques can be applied for our need. It may be feasib=
le to present an overview of techniques which could be used by TCMTF in dra=
ft B.=94</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Luigi: =93There are tons of classification methods out there, developing =
a new one does not look very useful to me.=94</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Michael: =93I agree with Luigi and Mirko ... there are more than enough p=
eople working on traffic flow descriptions ... and how to signal/inform net=
works of their requirements (e.g., per-hop
 behaviors and the like). (=85) For now, I would recommend a placeholder in=
 the draft that addresses the concern and that TCMTF SHOULD consider the tr=
affic class of the flows when such information is available.=94</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">So perhaps the solution coul=
d be widening the scope of the Document (B) in order to also include:</span=
></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - TCMTF SHOU=
LD consider the traffic class of the flows when such information is availab=
le</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Suggesting=
 traffic classification methods which could be useful in order to do this
</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">What do you think? Is everyo=
ne ok with this?</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">2.- Should we include it in =
the Charter now?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Of course, Document (B) should =
be included in the Charter.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Best regards,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jose</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt; font-f=
amily:Arial,sans-serif">Jose Saldana, PhD</span><span lang=3D"EN-US" style=
=3D"font-size:12pt; font-family:'Times New Roman',serif"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt; font-f=
amily:Arial,sans-serif">Communications Technologies Group (GTC)<br>
Dpt. Electrical Engineering and Communications<br>
EINA, University of Zaragoza.<br>
</span><span style=3D"font-size:10pt; font-family:Arial,sans-serif">C/ Mar=
=EDa de Luna 1, Edif. Ada Byron, D. 2.05<br>
50018 Zaragoza, Spain</span><span style=3D""></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:Arial,san=
s-serif">Tel: &#43;34 976 76 2698</span><span style=3D""></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt; font-f=
amily:Arial,sans-serif">Ext: 2698</span><span lang=3D"EN-US" style=3D""></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt; font-f=
amily:Arial,sans-serif">E-mail:
</span><span style=3D"font-size:10.0pt; font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;"><a href=3D"mailto:jsaldana@unizar.es"><span lang=3D"EN-U=
S">jsaldana@unizar.es</span></a></span><span lang=3D"EN-US" style=3D"font-s=
ize:10pt; font-family:Arial,sans-serif"></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;A=
rial&quot;,&quot;sans-serif&quot;"><a href=3D"http://diec.unizar.es/~jsalda=
na/personal/index.htm"><span lang=3D"EN-US">http://diec.unizar.es/~jsaldana=
/personal/index.htm</span></a></span><span lang=3D"EN-US" style=3D"font-siz=
e:10pt; font-family:Arial,sans-serif"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a><br>
</font></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_l2cezDmdXVpO8FJ5nH6mwA)--

From fpb@tid.es  Tue Jan 15 06:07:04 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B816E21F8903 for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 06:07:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.332
X-Spam-Level: 
X-Spam-Status: No, score=-6.332 tagged_above=-999 required=5 tests=[AWL=0.266,  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 tGn8wVv4cSp3 for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 06:07:04 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id E894D21F889C for <tcmtf@ietf.org>; Tue, 15 Jan 2013 06:07:02 -0800 (PST)
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 <0MGO0027D77Q12@tid.hi.inet> for tcmtf@ietf.org; Tue, 15 Jan 2013 15:07:02 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id D9.14.03184.68265F05; Tue, 15 Jan 2013 15:07:02 +0100 (CET)
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 <0MGO0027977P12@tid.hi.inet> for tcmtf@ietf.org; Tue, 15 Jan 2013 15:07:01 +0100 (MET)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.151]) by ex10-htcas3-mad.hi.inet ([::1]) with mapi id 14.02.0328.009; Tue, 15 Jan 2013 15:03:58 +0100
Date: Tue, 15 Jan 2013 14:07:01 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <008601cdf30f$0105f8c0$0311ea40$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A265041332@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_w3jKI68WqPnPpd8yKgYYhw)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: [tcmtf] TCMTF: Document C discussion: content and charter
Thread-index: Ac3zAaWdu17ID/aOR5mMJnwF9rLUGQAJ/EGA
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4068-b7fc06d000000c70-b3-50f56286d132
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOKsWRmVeSWpSXmKPExsXCFe/ApduW9DXA4GMnh8WuzxsYHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVsWryfZaCs1YVbxYtYmxg7DfuYuTkkBAwkVj78i4jhC0mceHe ejYQW0hgA6PE2RNMEPYPRokbN1kh7JmMErO+ioHYLAKqEg2PDzOD2GwCWhKn765iAbGFBdwk Pj37ChbnFLCQOPBxDhPEfAWJP+ceg9WICARI7G45AGbzCnhLbDm0mQ3CFpT4MfkeWJxZIFei bfZdNghbXKK59SZYnBHozu+n1jBBzHGX+HbtISOEbSSx5tIudhBbVEBPou3YGXaIvQISS/ac Z4awRSVePv7HOoFRdBaSdbOQrJuFZB2EbSDx/tx8ZghbW2LZwtdQtr7Exi9nGSFsM4knh28y IatZwMixilGsOKkoMz2jJDcxMyfdwFAvI1MvMy+1ZBMjJOYydjAu36lyiFGAg1GJh/fA2c8B QqyJZcWVuYcYJTmYlER5JyV+DRDiS8pPqcxILM6ILyrNSS0+xCjBwawkwqthBJTjTUmsrEot yodJyXBwKEnwzgRpEyxKTU+tSMvMASYWmDQTBydIOw9QuxJIDW9xQWJucWY6RP4UoypHy4Hu 54xCLHn5ealS4rxtIEUCIEUZpXlwc14xigMdLMzbBJLlAaZGuAmvgIYzAQ3ftPczyPCSRISU VAMwQXK/NpTKfXvn0ze5WMmcn39MPslHl08N+t/aFpvOKnGlRmaHec2xg4s3HmrY7xETdnLP NO7am4nM/5YmvOF/0yn3qZUvZOKLjGWipTd0bVotTVao2JttO2i3fOc9w+dzEh0d/Wulsm5u bHxyjVs4p040R0h3xZpHKaGBvGdnBRz3veL3KFaJpTgj0VCLuag4EQAIqDSgSgMAAA==
Subject: Re: [tcmtf] TCMTF: Document C discussion: content and charter
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, 15 Jan 2013 14:07:04 -0000

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

I agree.

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: martes, 15 de enero de 2013 11:56
To: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Subject: [tcmtf] TCMTF: Document C discussion: content and charter

Document (C) may refer to a new document about signaling

1.- Content of the Document


#2. A mechanism to *elect an optimal muxer and a de-muxer when there are mo=
re than one muxer/de-muxer for a flow*.



We agree: This can wait for Document C.



                Fernando: =93#2 is more related to the higher entity that h=
as to decide whether a flow should be TCMTFed or not, and under my point of=
 view it can be addressed in a different draft.=94

                Muthu: =93#2 can be added later.=94



2.- Should we include it in the Charter now?

I think we shouldn=92t include this in the charter as an objective. It can =
be included in one of the last paragraphs.

Best regards,

Jose


________________________________

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

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font=
-family:Calibri,sans-serif">
<div>
<div>
<div>I agree.</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>martes, 15 de enero de 2013 1=
1:56<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: Document C =
discussion: content and charter<br>
</div>
<div><br>
</div>
<div><style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
span.EstiloCorreo17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.TextosinformatoCar
	{font-family:"Calibri","sans-serif"}
.MsoChpDefault
	{font-family:"Calibri","sans-serif"}
@page WordSection1
	{margin:70.85pt 3.0cm 70.85pt 3.0cm}
div.WordSection1
	{}
-->
</style>
<div lang=3D"ES">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Document (C) may refer to a new=
 document about signaling</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">1.- Content of the Document</sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">#2. A mechanism to *<b>elect=
 an optimal muxer and a de-muxer when there are more than one muxer/de-muxe=
r for a flow</b>*.</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">We agree: This can wait for =
Document C.</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fernando: =
=93#2 is more related to the higher entity that has to decide whether a flo=
w should be TCMTFed or not, and under my point of view it can be addressed =
in a different draft.=94</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu: =93#2=
 can be added later.=94</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">2.- Should we include it in =
the Charter now?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I think we shouldn=92t include =
this in the charter as an objective. It can be included in one of the last =
paragraphs.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Best regards,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jose</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
</div>
</div>
</span><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_w3jKI68WqPnPpd8yKgYYhw)--

From fpb@tid.es  Tue Jan 15 06:42:02 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1E921F86E3; Tue, 15 Jan 2013 06:42:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.22
X-Spam-Level: 
X-Spam-Status: No, score=-6.22 tagged_above=-999 required=5 tests=[AWL=0.078,  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 axytVbLmpdZa; Tue, 15 Jan 2013 06:42:01 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 8DF8321F86D8; Tue, 15 Jan 2013 06:41:59 -0800 (PST)
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 <0MGO006K18TYNY@tid.hi.inet>; Tue, 15 Jan 2013 15:41:58 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id F1.C5.02896.6BA65F05; Tue, 15 Jan 2013 15:41:58 +0100 (CET)
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 <0MGO006JV8TXNY@tid.hi.inet>; Tue, 15 Jan 2013 15:41:58 +0100 (MET)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.151]) by ex10-htcas3-mad.hi.inet ([::1]) with mapi id 14.02.0328.009; Tue, 15 Jan 2013 15:38:54 +0100
Date: Tue, 15 Jan 2013 14:41:56 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <A3179A2C9AAEE647BE70AC4C7881D5FB017759C4@sluga.fer.hr>
X-Originating-IP: [10.95.64.115]
To: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>, "tcmtf@ietf.org" <tcmtf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A265041584@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_zg+EiJe6cIWzHJQOTkKQag)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
Thread-index: AQHN8y4KB8ofXnBXW0Oy0IIeip1rIA==
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4e69-b7f636d000000b50-31-50f56ab64727
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHKsWRmVeSWpSXmKPExsXCFe9nqLst62uAwZs/aha7Pm9gtDj25i6b A5PHkiU/mQIYo7hsUlJzMstSi/TtErgypvSZF3xOqZixsJe1gfF9eBcjJ4eEgInEnp1vWSBs MYkL99azdTFycQgJbGOUuNq3jx3CecooMatjBSuEM5NRYtX696wgLSwCqhK3Wt8wgthsAloS p++uAhslLFAg0fnhC1gNp4CLROvuT8wQKxQk/px7zAIySESgk1GiYdJZsGZeAW+JKb/6oGxB iR+T74ENYhbIlbh3ZS8zhC0u0dx6EyzOCHTr91NrmEBsEYFCifstc4Hu5gCy9SSenI8BCYsC mW3HzrBD7BWQWLLnPNQNohIvH/9jncAoOgvJtllIts1Csg3C1pN4dmoWlK0tsWzha6gaXYlL D9exQthmEm9+TGNHVrOAkWMVo1hxUlFmekZJbmJmTrqBkV5Gpl5mXmrJJkZIBGbuYFy+U+UQ owAHoxIP74GznwOEWBPLiitzDzFKcjApifIWpn8NEOJLyk+pzEgszogvKs1JLT7EKMHBrCTC q2EElONNSaysSi3Kh0nJcHAoSfAKAJOFkGBRanpqRVpmDjDNwKSZODhB2nmA2kVAaniLCxJz izPTIfKnGFU59j9pf84oxJKXn5cqJc67OhOoSACkKKM0D27OK0ZxoIOFea1BRvAAEyXchFdA w5mAhm/a+xlkeEkiQkqqgXF7+9aPn6fXlTjIR76QW6WfEPdSoDHrauCvFFPm7jAZtl/f215d 8eDMeDyvqdwxKfzjYcbFz4+vF5vCln82KSA2jGE2V8MCv5BJksUvswV49Xry5u2oeNn4SH3R dW2vJ42X+SY/3SZgvkz0+6vk56qNga+MmbxVgpq9z+4r0d2ReKe42vzaFCWW4oxEQy3mouJE AEnK+cpRAwAA
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 14:42:02 -0000

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

Hi Mirko,

Some comments to the draft:

  *   In the introduction it says "TCTMF", it is "TCMTF".
  *   I do not understand the sentence "Therefore, we neither take into acc=
ount services using an approach in which all the calculations are deployed =
in the server, which sends a real-time video stream to the client." in sect=
ion 3.
  *   In section 3 (Considered Services), I think it could be also interest=
ing to consider non-real time services candidates to be TCMTF optimized. Fo=
r example services like instant messaging, where the bandwidth saving is th=
e main benefit of the TCMTF optimization, should be somehow mentioned, esta=
blishing a kind of delay upper threshold. Related to that, in section 3, wh=
en talking about web browsing, the sentence "there is no need for policy li=
mitations in TCMTF" could be disappointed, because actually there are limit=
ations (ITU-T_G.1010, 10 seconds for web browsing, as in section 4.1 10 sec=
onds are considered for streaming audio).
  *   In section 4, I would change the sentence "A number of flows are mult=
iplexed together before being sent through the Internet." for "A number of =
flows are multiplexed together before being sent through the network.", bec=
ause the network could not be necessary the Internet, I would also adapt Fi=
gure 2.
  *   Maybe the creation of a section 4.4 talking about non real time servi=
ces could be considered including last comments (acceptable with the recomm=
endation appearing in the last sentence of the section 4.3 "It should be no=
ted that multiplexing periods of about 1 second can be considered as enough=
 for non real time services (e.g., web browsing and streaming audio).")
  *   Table 1 could be included in a separate section (i.e. Section 4.5) as=
 a summary

Hope to help!

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: Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr<mailto:Mirko.Suznjevic@fe=
r.hr>>
Date: jueves, 13 de diciembre de 2012 10:06
To: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>, "tsvwg@ietf.org<mailto:tsvwg@ietf.org>" <tsvwg@ietf.org<mailto:ts=
vwg@ietf.org>>
Subject: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compr=
essed Multiplexed Traffic Flows

Hello,

We have just submitted the draft named Maximum Tolerable Delays when using =
Tunneling Compressed Multiplexed Traffic Flows: http://datatracker.ietf.org=
/doc/draft-suznjevic-tsvwg-mtd-tcmtf/

It is an extension of tcmtf http://datatracker.ietf.org/doc/draft-saldana-t=
svwg-tcmtf/. Since a specific list for tcmtf exists (tcmtf@ietf.org<mailto:=
tcmtf@ietf.org>), the idea is to discuss it there.

The draft contains recommendations for TCMTF multiplexing period for differ=
ent real-time services. In order to prevent QoE degradation of real-time se=
rvices using TCMTF, a policy defining  a multiplexing period can be employe=
d. Values of maximum tolerable delays presented in the draft form the base =
of such policy.    The recommendations are presented for real-time network =
services in which TCTMF bandwidth optimization is applicable (i.e., service=
s  which have low payload to header size ratio which results in high protoc=
ol overhead).

Your feedback will be welcome. Thank you.

Sincerely,
Mirko Suznjevic

________________________________

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_zg+EiJe6cIWzHJQOTkKQag)
Content-id: <9DD849C7D95A9040B5FC477442A7E6E2@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">
<div>
<div style=3D"color:rgb(0,0,0); font-family:Calibri,sans-serif; font-size:1=
4px">Hi Mirko,</div>
<div style=3D"color:rgb(0,0,0); font-family:Calibri,sans-serif; font-size:1=
4px"><br>
</div>
<div style=3D"color:rgb(0,0,0); font-family:Calibri,sans-serif; font-size:1=
4px"><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Some c=
omments to the draft:</div>
<ul>
<li style=3D"color:rgb(0,0,0); font-family:Calibri,sans-serif; font-size:14=
px">In the introduction it says &quot;TCTMF&quot;, it is &quot;TCMTF&quot;.=
</li><li style=3D"color:rgb(0,0,0); font-family:Calibri,sans-serif; font-si=
ze:14px"><font face=3D"Calibri,sans-serif">I do not understand the sentence=
 &quot;</font><font face=3D"Calibri,sans-serif">Therefore, we&nbsp;</font><=
font face=3D"Calibri,sans-serif">neither take into account
 services using an approach in which all the&nbsp;</font><font face=3D"Cali=
bri,sans-serif">calculations are deployed in the server, which sends a real=
-time&nbsp;</font><span style=3D"font-family:Calibri,sans-serif">video stre=
am to the client.&quot; in section 3.</span></li><li style=3D"color:rgb(0,0=
,0); font-family:Calibri,sans-serif; font-size:14px">In section 3 (Consider=
ed Services), I think it could be also interesting to consider non-real tim=
e services candidates to be TCMTF optimized. For example services like inst=
ant messaging,
 where the bandwidth saving is the main benefit of the TCMTF optimization, =
should be somehow mentioned, establishing a kind of delay upper threshold. =
Related to that, i<font face=3D"Calibri,sans-serif">n section 3, when talki=
ng about web browsing, the sentence
 &quot;<font face=3D"Calibri,sans-serif">there is no need for policy&nbsp;<=
/font>limitations in TCMTF</font><font face=3D"Calibri,sans-serif">&quot; c=
ould be&nbsp;disappointed, because actually there are limitations (ITU-T_G.=
1010,&nbsp;10 seconds for web browsing, as in section 4.1 10
 seconds are considered for streaming audio).</font></li><li style=3D"color=
:rgb(0,0,0); font-family:Calibri,sans-serif; font-size:14px"><font face=3D"=
Calibri,sans-serif">In section 4, I would change the sentence &quot;</font>=
<font face=3D"Calibri,sans-serif">A number of flows are multiplexed&nbsp;</=
font><span style=3D"font-family:Calibri,sans-serif">together
 before being sent through the Internet.&quot; for &quot;</span><font face=
=3D"Calibri,sans-serif">A number of flows are multiplexed&nbsp;</font><span=
 style=3D"font-family:Calibri,sans-serif">together before being sent throug=
h the network.&quot;, because the network could not be necessary
 the Internet, I would also adapt Figure 2.</span></li><li><span style=3D"c=
olor:rgb(0,0,0); font-family:Calibri,sans-serif; font-size:14px; font-style=
:normal; font-weight:normal; text-decoration:none">Maybe the creation of a =
section 4.4 talking about non real time services could be considered includ=
ing last comments
 (acceptable with the recommendation appearing in the last sentence of the =
section 4.3 &quot;</span><font face=3D"Calibri,sans-serif">It should be not=
ed&nbsp;</font><font face=3D"Calibri,sans-serif">that multiplexing periods =
of about 1 second can be considered as&nbsp;</font><font face=3D"Calibri,sa=
ns-serif">enough
 for non real time services (e.g., web browsing and streaming&nbsp;</font><=
span style=3D"font-family:Calibri,sans-serif">audio).&quot;)</span></li><li=
><font face=3D"Calibri,sans-serif">Table 1 could be included in a separate =
section (i.e.&nbsp;Section 4.5) as a summary</font></li></ul>
<div><font face=3D"Calibri,sans-serif"><span class=3D"Apple-tab-span" style=
=3D"white-space:pre"></span>Hope to help!</font></div>
<div style=3D"color:rgb(0,0,0); font-family:Calibri,sans-serif; font-size:1=
4px">
<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><a href=3D"mailto:fpb@tid.es">fpb@tid.es</a></div>
</div>
</div>
<div style=3D"color:rgb(0,0,0); font-family:Calibri,sans-serif; font-size:1=
4px"><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color:rgb(0,0,0); font-family:Ca=
libri,sans-serif; font-size:14px">
<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>Mirko Su=BEnjevi=E6 &lt;<a hr=
ef=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>jueves, 13 de diciembre de 20=
12 10:06<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;, &quot;<a href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org=
</a>&quot; &lt;<a href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[tcmtf] Draft: Maximum Tol=
erable Delays when using Tunneling Compressed Multiplexed Traffic Flows<br>
</div>
<div><br>
</div>
<div><style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
span.EmailStyle17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
.MsoChpDefault
	{}
@page WordSection1
	{margin:70.85pt 70.85pt 70.85pt 70.85pt}
div.WordSection1
	{}
-->
</style>
<div lang=3D"HR">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hello,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We have just submitted the draf=
t named Maximum Tolerable Delays when using Tunneling Compressed Multiplexe=
d Traffic Flows:
<a href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/=
">http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">It is an extension of tcmtf <a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a>. Since a spe=
cific list for tcmtf exists (<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.o=
rg</a>), the idea is to discuss it there.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The draft contains recommendati=
ons for TCMTF multiplexing period for different real-time services. In orde=
r to prevent QoE degradation of real-time services using TCMTF, a policy de=
fining&nbsp; a multiplexing period can be
 employed. Values of maximum tolerable delays presented in the draft form t=
he base of such policy.&nbsp;&nbsp;&nbsp; The recommendations are presented=
 for real-time network services in which TCTMF bandwidth optimization is ap=
plicable (i.e., services&nbsp; which have low payload
 to header size ratio which results in high protocol overhead).</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Your feedback will be welcome. =
Thank you.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
Sincerely,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Mirko Suznjevic</span></p>
</div>
</div>
</div>
</span><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_zg+EiJe6cIWzHJQOTkKQag)--

From Mirko.Suznjevic@fer.hr  Tue Jan 15 07:49:23 2013
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 7E6D121F871C; Tue, 15 Jan 2013 07:49:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 EJvU1JyYj4cl; Tue, 15 Jan 2013 07:49:19 -0800 (PST)
Received: from mail.zvne.fer.hr (mail.zvne.fer.hr [161.53.66.5]) by ietfa.amsl.com (Postfix) with ESMTP id 7E6A421F8510; Tue, 15 Jan 2013 07:49:17 -0800 (PST)
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.318.4; Tue, 15 Jan 2013 16:49:15 +0100
Received: from sluga.fer.hr ([161.53.66.244]) by munja.zvne.fer.hr with Microsoft SMTPSVC(6.0.3790.4675);	 Tue, 15 Jan 2013 16:49:00 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CDF337.D5BC6F98"
Date: Tue, 15 Jan 2013 16:48:59 +0100
Message-ID: <A3179A2C9AAEE647BE70AC4C7881D5FB0177608D@sluga.fer.hr>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A265041584@EX10-MB1-MAD.hi.inet>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
Thread-Index: AQHN8y4KB8ofXnBXW0Oy0IIeip1rIJhKgzjA
References: <A3179A2C9AAEE647BE70AC4C7881D5FB017759C4@sluga.fer.hr> <F5EDC35DF914C1428C28E149F10463A265041584@EX10-MB1-MAD.hi.inet>
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: FERNANDO PASCUAL BLANCO <fpb@tid.es>, <tcmtf@ietf.org>, <tsvwg@ietf.org>
X-OriginalArrivalTime: 15 Jan 2013 15:49:00.0134 (UTC) FILETIME=[D5EB7060:01CDF337]
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 15:49:23 -0000

------_=_NextPart_001_01CDF337.D5BC6F98
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

Hello,

Thanks for all the comments, I will briefly respond to them, and include =
your (as well as previous) corrections in a new version of the draft:

*	I do not understand the sentence "Therefore, we neither take into =
account services using an approach in which all the calculations are =
deployed in the server, which sends a real-time video stream to the =
client." in section 3.

The meaning of this sentence is that we will not be looking at the cloud =
based gaming services such as OnLive or Gaiki as they are focused on =
performing all needed calculations of the gamestate on the server, and =
sending a very "fat" video stream to the client which only renders the =
video. Therefore they are not suitable for tcmtf. I will change that in =
order to be more clear.

*	In section 3 (Considered Services), I think it could be also =
interesting to consider non-real time services candidates to be TCMTF =
optimized. For example services like instant messaging, where the =
bandwidth saving is the main benefit of the TCMTF optimization, should =
be somehow mentioned, establishing a kind of delay upper threshold. =
Related to that, in section 3, when talking about web browsing, the =
sentence "there is no need for policy limitations in TCMTF" could be =
disappointed, because actually there are limitations (ITU-T_G.1010, 10 =
seconds for web browsing, as in section 4.1 10 seconds are considered =
for streaming audio).

At first when we were discussing we decided that it will be focused on =
real-time services, but this can be broadened to others non-real-time. I =
think giving such upper limits has a point, although would we even =
employ tcmtf in cases  in which we will not have enough data to send a =
packet in 5 or more seconds? Is that feasible? Maybe in some sensor =
networks? Maybe I am just looking it the wrong way, maybe we would have =
a lot of traffic that needs to be packed ASAP!

*	In section 4, I would change the sentence "A number of flows are =
multiplexed together before being sent through the Internet." for "A =
number of flows are multiplexed together before being sent through the =
network.", because the network could not be necessary the Internet, I =
would also adapt Figure 2.

Ok will be done.

*	Maybe the creation of a section 4.4 talking about non real time =
services could be considered including last comments (acceptable with =
the recommendation appearing in the last sentence of the section 4.3 "It =
should be noted that multiplexing periods of about 1 second can be =
considered as enough for non real time services (e.g., web browsing and =
streaming audio).")

Ok, seems sound enough. I will write it and see which format looks =
better.

*	Table 1 could be included in a separate section (i.e. Section 4.5) as =
a summary

Ok.

=20

Thanks again for the feedback!

Cheers!
Mirko

=20

From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]=20
Sent: Tuesday, January 15, 2013 3:42 PM
To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org; tsvwg@ietf.org
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using =
Tunneling Compressed Multiplexed Traffic Flows

=20

Hi Mirko,

=20

Some comments to the draft:

*	In the introduction it says "TCTMF", it is "TCMTF".
*	I do not understand the sentence "Therefore, we neither take into =
account services using an approach in which all the calculations are =
deployed in the server, which sends a real-time video stream to the =
client." in section 3.
*	In section 3 (Considered Services), I think it could be also =
interesting to consider non-real time services candidates to be TCMTF =
optimized. For example services like instant messaging, where the =
bandwidth saving is the main benefit of the TCMTF optimization, should =
be somehow mentioned, establishing a kind of delay upper threshold. =
Related to that, in section 3, when talking about web browsing, the =
sentence "there is no need for policy limitations in TCMTF" could be =
disappointed, because actually there are limitations (ITU-T_G.1010, 10 =
seconds for web browsing, as in section 4.1 10 seconds are considered =
for streaming audio).
*	In section 4, I would change the sentence "A number of flows are =
multiplexed together before being sent through the Internet." for "A =
number of flows are multiplexed together before being sent through the =
network.", because the network could not be necessary the Internet, I =
would also adapt Figure 2.
*	Maybe the creation of a section 4.4 talking about non real time =
services could be considered including last comments (acceptable with =
the recommendation appearing in the last sentence of the section 4.3 "It =
should be noted that multiplexing periods of about 1 second can be =
considered as enough for non real time services (e.g., web browsing and =
streaming audio).")
*	Table 1 could be included in a separate section (i.e. Section 4.5) as =
a summary

Hope to help!

=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: Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr>
Date: jueves, 13 de diciembre de 2012 10:06
To: "tcmtf@ietf.org" <tcmtf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling =
Compressed Multiplexed Traffic Flows

=20

Hello,

=20

We have just submitted the draft named Maximum Tolerable Delays when =
using Tunneling Compressed Multiplexed Traffic Flows: =
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/

=20

It is an extension of tcmtf =
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/. Since a =
specific list for tcmtf exists (tcmtf@ietf.org), the idea is to discuss =
it there.

=20

The draft contains recommendations for TCMTF multiplexing period for =
different real-time services. In order to prevent QoE degradation of =
real-time services using TCMTF, a policy defining  a multiplexing period =
can be employed. Values of maximum tolerable delays presented in the =
draft form the base of such policy.    The recommendations are presented =
for real-time network services in which TCTMF bandwidth optimization is =
applicable (i.e., services  which have low payload to header size ratio =
which results in high protocol overhead).

=20

Your feedback will be welcome. Thank you.


Sincerely,

Mirko Suznjevic

=20

________________________________


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


------_=_NextPart_001_01CDF337.D5BC6F98
Content-Type: text/html; charset="iso-8859-2"
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-2"><meta name=3DGenerator content=3D"Microsoft Word =
12 (filtered medium)"><!--[if !mso]><style>v\:* =
{behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	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.emailstyle17
	{mso-style-name:emailstyle17;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:549346588;
	mso-list-type:hybrid;
	mso-list-template-ids:-590298032 68812817 68812825 68812827 68812815 =
68812825 68812827 68812815 68812825 68812827;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:1165701985;
	mso-list-template-ids:1998326026;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
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=3DHR link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Hello,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Thanks for =
all the comments, I will briefly respond to them, and include your (as =
well as previous) corrections in a new version of the =
draft:<o:p></o:p></span></p><ul type=3Ddisc><li class=3DMsoNormal =
style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l1 level1 lfo1'><span lang=3DEN-US style=3D'font-size:10.5pt'>I =
do not understand the sentence &quot;Therefore, we&nbsp;neither take =
into account services using an approach in which all =
the&nbsp;calculations are deployed in the server, which sends a =
real-time&nbsp;video stream to the client.&quot; in section =
3.<o:p></o:p></span></li></ul><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US style=3D'color:#1F497D'>The meaning of this sentence is =
that we will not be looking at the cloud based gaming services such as =
OnLive or Gaiki as they are focused on performing all needed =
calculations of the gamestate on the server, and sending a very =
&#8220;fat&#8221; video stream to the client which only renders the =
video. Therefore they are not suitable for tcmtf. I will change that in =
order to be more clear.</span><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p></o:p></span></p><ul =
type=3Ddisc><li class=3DMsoNormal =
style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l1 level1 lfo1'><span lang=3DEN-US style=3D'font-size:10.5pt'>In =
section 3 (Considered Services), I think it could be also interesting to =
consider non-real time services candidates to be TCMTF optimized. For =
example services like instant messaging, where the bandwidth saving is =
the main benefit of the TCMTF optimization, should be somehow mentioned, =
establishing a kind of delay upper threshold. Related to that, in =
section 3, when talking about web browsing, the sentence &quot;there is =
no need for policy&nbsp;limitations in TCMTF&quot; could =
be&nbsp;disappointed, because actually there are limitations =
(ITU-T_G.1010,&nbsp;10 seconds for web browsing, as in section 4.1 10 =
seconds are considered for streaming =
audio).<o:p></o:p></span></li></ul><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US style=3D'color:#1F497D'>At first when we were discussing we =
decided that it will be focused on real-time services, but this can be =
broadened to others non-real-time. I think giving such upper limits has =
a point, although would we even employ tcmtf in cases =A0in which we =
will not have enough data to send a packet in 5 or more seconds? Is that =
feasible? Maybe in some sensor networks? Maybe I am just looking it the =
wrong way, maybe we would have a lot of traffic that needs to be packed =
ASAP!</span><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p></o:p></span></p><ul =
type=3Ddisc><li class=3DMsoNormal =
style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l1 level1 lfo1'><span lang=3DEN-US style=3D'font-size:10.5pt'>In =
section 4, I would change the sentence &quot;A number of flows are =
multiplexed&nbsp;together before being sent through the Internet.&quot; =
for &quot;A number of flows are multiplexed&nbsp;together before being =
sent through the network.&quot;, because the network could not be =
necessary the Internet, I would also adapt Figure =
2.<o:p></o:p></span></li></ul><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US style=3D'color:#1F497D'>Ok will be done.</span><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p></o:p></span></p><ul =
type=3Ddisc><li class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 =
level1 lfo1'><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Maybe the creation of a section =
4.4 talking about non real time services could be considered including =
last comments (acceptable with the recommendation appearing in the last =
sentence of the section 4.3 &quot;</span><span lang=3DEN-US>It should be =
noted&nbsp;that multiplexing periods of about 1 second can be considered =
as&nbsp;enough for non real time services (e.g., web browsing and =
streaming&nbsp;audio).&quot;)</span><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></li></ul><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US style=3D'color:#1F497D'>Ok, seems sound enough. I will =
write it and see which format looks better.</span><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p><ul type=3Ddisc><li =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 =
level1 lfo1'><span lang=3DEN-US>Table 1 could be included in a separate =
section (i.e.&nbsp;Section 4.5) as a =
summary<o:p></o:p></span></li></ul><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Ok.<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 =
again for the feedback!<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'color:#1F497D'>Cheers!<br>Mirko<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> FERNANDO =
PASCUAL BLANCO [mailto:fpb@tid.es] <br><b>Sent:</b> Tuesday, January 15, =
2013 3:42 PM<br><b>To:</b> Mirko Su=BEnjevi=E6; tcmtf@ietf.org; =
tsvwg@ietf.org<br><b>Subject:</b> Re: [tcmtf] Draft: Maximum Tolerable =
Delays when using Tunneling Compressed Multiplexed Traffic =
Flows<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Hi =
Mirko,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Some comments to the =
draft:<o:p></o:p></span></p></div><ul type=3Ddisc><li class=3DMsoNormal =
style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l1 level1 lfo1'><span lang=3DEN-US style=3D'font-size:10.5pt'>In =
the introduction it says &quot;TCTMF&quot;, it is =
&quot;TCMTF&quot;.<o:p></o:p></span></li><li class=3DMsoNormal =
style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l1 level1 lfo1'><span lang=3DEN-US style=3D'font-size:10.5pt'>I =
do not understand the sentence &quot;Therefore, we&nbsp;neither take =
into account services using an approach in which all =
the&nbsp;calculations are deployed in the server, which sends a =
real-time&nbsp;video stream to the client.&quot; in section =
3.<o:p></o:p></span></li><li class=3DMsoNormal =
style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l1 level1 lfo1'><span lang=3DEN-US style=3D'font-size:10.5pt'>In =
section 3 (Considered Services), I think it could be also interesting to =
consider non-real time services candidates to be TCMTF optimized. For =
example services like instant messaging, where the bandwidth saving is =
the main benefit of the TCMTF optimization, should be somehow mentioned, =
establishing a kind of delay upper threshold. Related to that, in =
section 3, when talking about web browsing, the sentence &quot;there is =
no need for policy&nbsp;limitations in TCMTF&quot; could =
be&nbsp;disappointed, because actually there are limitations =
(ITU-T_G.1010,&nbsp;10 seconds for web browsing, as in section 4.1 10 =
seconds are considered for streaming audio).<o:p></o:p></span></li><li =
class=3DMsoNormal =
style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l1 level1 lfo1'><span lang=3DEN-US style=3D'font-size:10.5pt'>In =
section 4, I would change the sentence &quot;A number of flows are =
multiplexed&nbsp;together before being sent through the Internet.&quot; =
for &quot;A number of flows are multiplexed&nbsp;together before being =
sent through the network.&quot;, because the network could not be =
necessary the Internet, I would also adapt Figure =
2.<o:p></o:p></span></li><li class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 =
level1 lfo1'><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Maybe the creation of a section =
4.4 talking about non real time services could be considered including =
last comments (acceptable with the recommendation appearing in the last =
sentence of the section 4.3 &quot;</span><span lang=3DEN-US>It should be =
noted&nbsp;that multiplexing periods of about 1 second can be considered =
as&nbsp;enough for non real time services (e.g., web browsing and =
streaming&nbsp;audio).&quot;)</span><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></li><li class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 =
level1 lfo1'><span lang=3DEN-US>Table 1 could be included in a separate =
section (i.e.&nbsp;Section 4.5) as a =
summary<o:p></o:p></span></li></ul><div><p class=3DMsoNormal><span =
lang=3DEN-US>Hope to help!<o:p></o:p></span></p></div><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Regards,<o:p></o:p></span></p></di=
v><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Fernando Pascual =
Blanco<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>Telef=F3nica Global =
Resources<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>Network Automation =
and Dynamization<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>TECHNOLOGY PEOPLE =
GROUP<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>F =
+34913128779<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>M =
+34682005168<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US 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><p class=3DMsoNormal><span lang=3DEN-US =
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 lang=3DEN-US =
style=3D'color:black'>From: </span></b><span lang=3DEN-US =
style=3D'color:black'>Mirko Su=BEnjevi=E6 &lt;<a =
href=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt;<br>=
<b>Date: </b>jueves, 13 de diciembre de 2012 10:06<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;, &quot;<a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&gt;<br><b>Subject: =
</b>[tcmtf] Draft: Maximum Tolerable Delays when using Tunneling =
Compressed Multiplexed Traffic Flows<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>Hello,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>We have just =
submitted the draft named Maximum Tolerable Delays when using Tunneling =
Compressed Multiplexed Traffic Flows: <a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a><o:p=
></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>It is an =
extension of tcmtf <a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http:=
//datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a>. Since a =
specific list for tcmtf exists (<a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>), the idea is to =
discuss it there.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>The draft =
contains recommendations for TCMTF multiplexing period for different =
real-time services. In order to prevent QoE degradation of real-time =
services using TCMTF, a policy defining&nbsp; a multiplexing period can =
be employed. Values of maximum tolerable delays presented in the draft =
form the base of such policy.&nbsp;&nbsp;&nbsp; The recommendations are =
presented for real-time network services in which TCTMF bandwidth =
optimization is applicable (i.e., services&nbsp; which have low payload =
to header size ratio which results in high protocol =
overhead).<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>Your feedback =
will be welcome. Thank you.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'><br>Sincerely,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>Mirko =
Suznjevic<o:p></o:p></span></p></div></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><hr =
size=3D2 width=3D"100%" align=3Dcenter></span></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br=
>Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico en el enlace situado m=E1s abajo.<br>This message is =
intended exclusively for its addressee. We only send and receive email =
on the basis of the terms set out at:<br><a =
href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/E=
S/PAGINAS/disclaimer.aspx</a></span><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p></div></body></html>
------_=_NextPart_001_01CDF337.D5BC6F98--

From fpb@tid.es  Tue Jan 15 09:03:47 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DF3C21F8588 for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 09:03:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.23
X-Spam-Level: 
X-Spam-Status: No, score=-6.23 tagged_above=-999 required=5 tests=[AWL=0.069,  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 EV+XBYRoopJo for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 09:03:45 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id A894221F85E8 for <tcmtf@ietf.org>; Tue, 15 Jan 2013 09:03:43 -0800 (PST)
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 <0MGO005CXFDZZ5@tid.hi.inet> for tcmtf@ietf.org; Tue, 15 Jan 2013 18:03:36 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id B4.B9.02896.7EB85F05; Tue, 15 Jan 2013 18:03:35 +0100 (CET)
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 <0MGO005CQFDZZ5@tid.hi.inet> for tcmtf@ietf.org; Tue, 15 Jan 2013 18:03:35 +0100 (MET)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.151]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.004; Tue, 15 Jan 2013 18:00:31 +0100
Date: Tue, 15 Jan 2013 17:03:34 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <004c01cddc49$3e7264a0$bb572de0$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, 'Dan Wing' <dwing@cisco.com>, =?utf-8?B?J01pcmtvIFN1xb5uamV2acSHJw==?= <Mirko.Suznjevic@fer.hr>, =?utf-8?B?SnVsacOhbiBGZXJuw6FuZGV6IE5hdmFqYXM=?= <navajas@unizar.es>
Message-id: <F5EDC35DF914C1428C28E149F10463A265041D90@EX10-MB1-MAD.hi.inet>
Content-id: <37A733BAB19FAB49BFCE68B75C206D11@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] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
Thread-index: AQHN80HTGfNkhpo19UGvY8fOW/24Bg==
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4e69-b7f636d000000b50-41-50f58be70fd9
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrDKsWRmVeSWpSXmKPExsXCFe9nqPu8+2uAwaInBha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRvfaZvaCZVkVD483sDcwnkjvYuTkkBAwkZgw9xobhC0mceHe ejBbSGAbo8SbK9JdjFxA9g9GiYvt7awQiU2MEn3rw0FsFgFViXMb1zGB2GwCWhKn765iAbGF BQokOj98AavnFLCQWNW4mR1igYLEn3OPWUCGigjcYJT4834ykMPBwQw0aN43RZAaXgFvien9 k5hBbGYBM4lb14+xQsQFJX5MvgdVri4xZUouRIm4RHPrTRYIW1Fi2qIGRhCbUUBW4t38+WCt IgKFEvdb5rJB2HoSa1dsBTtHFMhuO3YG6jQBiSV7zjND2KISLx//Y53AKDELyRWzkFwxC+GK WUiumIXkigWMrKsYxYqTijLTM0pyEzNz0g2M9DIy9TLzUks2MUIiLnMH4/KdKocYBTgYlXh4 D5z9HCDEmlhWXJl7iFGSg0lJlHddw9cAIb6k/JTKjMTijPii0pzU4kOMEhzMSiK8YeVAOd6U xMqq1KJ8mJQMB4eSBO+5LqCUYFFqempFWmYOMK3ApJk4OEHaeYDaa0BqeIsLEnOLM9Mh8qcY tTn2P2l/zsgxY2LPc0Yhlrz8vFQpcd4NIKUCIKUZpXlw014xigOdLcy7DSTLA0yScHNeAa1g Alqxae9nkBUliQgpqQZGw5Ablgt/b5Z8GeHaZCpycMWpnIxtU3S37tZcev32szVKezQYWgwk vt7/5Xs884rxfp/9n9XZb5av3/VMRXLJPFHzqvMfD+dev9e33yDmcOkblffby8TCbpYZX5yR d7i1SlF995pN097PiRFkNji0yeXFlTqG5xMrjyu26klwfv00aV7T01l7GZVYijMSDbWYi4oT AT7YcBNPAwAA
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 17:03:47 -0000

SGkgYWxsLA0KDQogICAgICAgIFRvIHJlLW9wZW4gdGhhdCBpc3N1ZSwgSSB3b3VsZCBzdWdnZXN0
IHRoYXQgZ2l2ZW4gdGhhdCB0aGUgZGVsYXkgaXMgc28NCnNlbnNpdGl2ZSBpbiByZWFsIHRpbWUg
c2VydmljZXMsIHdlIG5lZWQgdG8gZmluZCBhIGNvbnNlbnN1cyBoZXJlLg0KDQogICAgICAgIE15
IG9waW5pb24gaXMgdGhhdCB0byBhcHBseSB0aGUgZmlyc3QgcG9zc2liaWxpdHkgKHRoZSBzdGF0
aWMNCm11bHRpcGxleGluZyBwZXJpb2QpIHdlIG5lZWQgdG8gc3VwcG9zZSB0aGF0IHRoZSBuZXR3
b3JrIGNvbmRpdGlvbnMgYXJlDQpyZWFsbHkgYmFkLCB0byBiZSBwcm90ZWN0ZWQgd2hlbiB0aGUg
bmV0d29yayBjb25nZXN0aW9uIGFyaXNlcy4gSW4gdGhhdA0KY2FzZSwgdGhlIGFwcGxpY2F0aW9u
IG9mIHRoZSBUQ01URiBvcHRpbWl6YXRpb24gd2lsbCBub3QgYmUgb3B0aW1hbCwgc28NCnRoYXQg
d291bGQgYmUgdGhlIGxlc3MgcHJlZmVycmVkIG9wdGlvbiwgYnV0IGVhc2llciB0byBpbXBsZW1l
bnQgYW5kDQptYWludGFpbiBvdmVyIHRoZSB0aW1lLg0KDQogICAgICAgIE9uIHRoZSBvdGhlciBo
YW5kLCB0aGUgc2Vjb25kIHBvc3NpYmlsaXR5IHdvdWxkIGJlIHRoZSBwcmVmZXJyZWQuIEl0IGlz
DQplYXN5IHRvIGtub3cgdGhlIGRlbGF5IGJldHdlZW4gdGhlIG11eCBhbmQgdGhlIGRlbXV4IGJ1
dCBtb3N0IG9mIHRoZSB0aW1lcw0Kd2lsbCBub3QgYmUgZW5vdWdoIHVubGVzcyBtdXggYW5kIGRl
bXV4IHdlcmUgcmVhbGx5IG5lYXIgZnJvbSB0aGUgY2xpZW50DQphbmQgdGhlIHNlcnZlciByZXNw
ZWN0aXZlbHkuIEkgYWdyZWUgd2l0aCBKb3NlIGluIHRoZSBwb3NzaWJpbGl0eSBvZiBzbm9vcA0K
UlRDUCBwYWNrZXRzIGluIG9yZGVyIHRvIGFkYXB0IHRoZSBtdWx0aXBsZXhpbmcgcGVyaW9kIHdo
ZW4gbXVsdGlwbGV4aW5nDQpSVFAgcGFja2V0cyAoYW5kIFJUQ1AgaXMgYXZhaWxhYmxlKS4gVGFs
a2luZyBhYm91dCBSVFQsIEnCtG0gbm90IHN1cmUgaWYNClJUVCB3b3VsZCBiZSB1c2VmdWwgZ2l2
ZW4gdGhhdCB0aGUgbXVsdGlwbGV4aW5nIHBlcmlvZCBvbmx5IGFmZmVjdCB0aGUgb25lDQp3YXkg
ZGVsYXkgKE9XRCkuIEltYWdpbmUgdGhlIGZvbGxvd2luZyBzY2VuYXJpbzoNCiAgICAgICAgLSBD
bGllbnQgLSBNdXgvRGVtdXggLSBEZW11eC9NdXggLSBTZXJ2ZXIgKHR3byB3YXlzIFRDTVRGLCBU
V1RDTVRGIDpQKQ0KICAgICAgICAtIFRoZSBPV0QgZnJvbSBzZXJ2ZXIgdG8gY2xpZW50IGdldCBp
bmNyZWFzZWQNCiAgICAgICAgLSBUaGUgT1dEIGZyb20gY2xpZW50IHRvIHNlcnZlciByZW1haW5z
IGVxdWFsDQogICAgICAgIC0gU2hvdWxkIHdlIHVzZSBhIGxvd2VyIG11bHRpcGxleGluZyBwZXJp
b2QgaW4gdGhlIGNsaWVudCB0byBzZXJ2ZXINCmRpcmVjdGlvbj8gSSBkb27CtHQgdGhpbmsgc2/i
gKYgYmVjYXVzZSB3ZSBzaG91bGQgdXNlIGEgbG93ZXIgbXVsdGlwbGV4aW5nDQpwZXJpb2QgaW4g
dGhlIG90aGVyIGRpcmVjdGlvbi4NCg0KICAgICAgICBNeSBwb2ludCBpcyB0aGF0IHRoZSBtdWx0
aXBsZXhpbmcgcGVyaW9kIHNob3VsZCBvbmx5IGJlIGFmZmVjdGVkIGJ5IHRoZQ0KT1dEIGFuZCBu
b3QgYnkgdGhlIFJUVCAob3IgaXQgbWF5IGJlIGFwcGxpY2F0aW9uIGRlcGVuZGVudCkuIEhvdyB0
bw0KY2FsY3VsYXRlIHRoZSBPV0Q/IEnCtHZlIGJlZW4gcmVhZGluZyBzb21ldGhpbmcgYWJvdXQg
T1dBTVAgYW5kIGl0IHNlZW1zDQp0aGF0IGFuIHNwZWNpZmljIHNvZnR3YXJlIGhhcyB0byBiZSBp
bXBsZW1lbnRlZCBpbiB0aGUgY2xpZW50L3NlcnZlciBzaWRlLg0KQ2FuIHdlIGFzc3VtZSB0aGF0
PyBVbmZvcnR1bmF0ZWx5IEkgY2Fubm90IGNvbnRyaWJ1dGUgc28gbXVjaCBoZXJl4oCmDQogICAg
ICAgIEl0IGlzIHBvc3NpYmxlIHRoYXQgZm9yIGNlcnRhaW4gc2VydmljZXMgdGhlIHN0YXRpYyAo
YW5kIHdvcnN0IGNhc2UpDQptdWx0aXBsZXhpbmcgcGVyaW9kIHdvdWxkIGJlIHRoZSBiZXR0ZXIg
c29sdXRpb24uDQoNCiAgICAgICAgV2hhdCBkbyB5b3UgdGhpbms/DQoNClJlZ2FyZHMsDQoNCkZl
cm5hbmRvIFBhc2N1YWwgQmxhbmNvDQpUZWxlZsOzbmljYSBHbG9iYWwgUmVzb3VyY2VzDQpOZXR3
b3JrIEF1dG9tYXRpb24gYW5kIER5bmFtaXphdGlvbg0KVEVDSE5PTE9HWSBQRU9QTEUgR1JPVVAN
CkYgKzM0OTEzMTI4Nzc5DQpNICszNDY4MjAwNTE2OA0KZnBiQHRpZC5lcw0KDQoNCg0KDQpPbiAx
Ny8xMi8xMiAxMjoyNSwgIkpvc2UgU2FsZGFuYSIgPGpzYWxkYW5hQHVuaXphci5lcz4gd3JvdGU6
DQoNCj5IaSBhbGwsDQo+DQo+SnVsaWFuIGFuZCBJIGhhdmUgYmVlbiBkaXNjdXNzaW5nIGFib3V0
IHRoaXMuIFNvbWUgaWRlYXMgaGF2ZSBhcmlzZW4uIFRoaXMNCj5pcyB0aGUgc3VtbWFyeS4NCj4N
Cj5UaGlzIHdvdWxkIGJlIHRoZSBzY2hlbWUgb2YgdGhlIHN5c3RlbSwgaW5jbHVkaW5nIG11eCBh
bmQgZGVtdXg6DQo+DQo+UmVhbC10aW1lIGFwcGxpY2F0aW9uIC0tLS0tLS0gbXV4IC0tLS0tLS0t
IGludGVybmV0IC0tLS0tLS0tLSBkZW11eA0KPi0tLS0tLS0NCj5zZXJ2ZXINCj4NCj4NCj5JIHRo
aW5rIHBlcmhhcHMgdGhlIGRyYWZ0IGNvdWxkIHNheSBzb21ldGhpbmcgbGlrZToNCj4NCj5XaGVu
IHNldHRpbmcgdGhlIG11bHRpcGxleGluZyBwZXJpb2QsIHRoZXJlIGFyZSB0d28gcG9zc2liaWxp
dGllczoNCj4NCj4xLi0gU3RhdGljIC8gcGVybWFuZW50OiBBdCBzeXN0ZW0gc2V0dXAgdGltZSwg
bmV0d29yayBkZWxheXMgYXJlIG1lYXN1cmVkLA0KPmFuZCBhIG11bHRpcGxleGluZyBwZXJpb2Qg
aXMgc2VsZWN0ZWQgYW5kIHNldCBpbiB0aGUgbXVsdGlwbGV4ZXIuDQo+DQo+Mi4tIER5bmFtaWM6
IEEgbWVjaGFuaXNtIGlzIHVzZWQgc28gYXMgdG8gYWRhcHQgdG8gdGhlIGV2b2x1dGlvbiBvZg0K
Pm5ldHdvcmsNCj5kZWxheXMuIEluIHRoaXMgY2FzZSwgZGlmZmVyZW50IG1lY2hhbmlzbXMgY2Fu
IGJlIHVzZWQgaW4gb3JkZXIgdG8gb2J0YWluDQo+cGVyaW9kaWNhbCBlbmQtdG8tZW5kIG5ldHdv
cmsgZGVsYXkgZXN0aW1hdGlvbnMsIHdoaWNoIHdvdWxkIGJlIHVzZWZ1bCBpbg0KPm9yZGVyIHRv
IHNldCB0aGUgbXVsdGlwbGV4aW5nIHBlcmlvZDoNCj4NCj4tIElmIHRoZSB0cmFmZmljIGlzIFJU
UCwgdGhlbiBSVENQIHBhY2tldHMgY29udGFpbmluZyB0aGUgZXN0aW1hdGlvbiBjb3VsZA0KPmJl
IGFuYWx5emVkIGluIG9yZGVyIHRvIGV4dHJhY3QgdGhlc2UgdmFsdWVzLCBhcyBEYW4gc3VnZ2Vz
dHMuIFRoZQ0KPnF1ZXN0aW9uDQo+aXM6IHdvdWxkIHRoYXQgcGFja2V0cyB0cmF2ZWwgdGhyb3Vn
aCB0aGUgbXVsdGlwbGV4ZXI/DQo+LSBJZiB0aGUgdHJhZmZpYyBpcyBUQ1AsIHBlcmhhcHMgc29t
ZXRoaW5nIHNpbWlsYXIgdG8gdGhlIFJUVCBlc3RpbWF0aW9uDQo+b2YNCj5UQ1AgY291bGQgYmUg
dXNlZnVsLg0KPi0gSWYgdGhlIHRyYWZmaWMgaXMgVURQLCBzaG91bGQgdGhlIG11eCB1c2Ugc29t
ZXRoaW5nIGxpa2UgT1dBTVANCj4oaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNDY1Nikg
aW4gb3JkZXIgdG8gY2FsY3VsYXRlIHR3byBkZWxheXMNCj4oYXBwbGljYXRpb24gdG8gbXV4LCBh
bmQgbXV4IHRvIHNlcnZlcikgYW5kIGNhbGN1bGF0ZSB0aGUgc3VtPw0KPg0KPg0KPkkgdGhpbmsg
dGhlIGRyYWZ0IGlzIG9ubHkgc3VwcG9zZWQgdG8gcmVwb3J0IHRoZSBtYXhpbXVtIGRlbGF5cyBu
b3JtYWxseQ0KPmNvbnNpZGVyZWQgYWNjZXB0YWJsZS4gUGVyaGFwcyB0aGUgYWRkaXRpb25hbCBt
ZWNoYW5pc21zIGZvciBjYWxjdWxhdGluZw0KPnRoZQ0KPlJUVCBjb3VsZCBqdXN0IGJlIHN1Z2dl
c3RlZC4NCj4NCj5XaGF0IGRvIHlvdSB0aGluaz8NCj4NCj5Kb3NlDQo+DQo+PiAtLS0tLU1lbnNh
amUgb3JpZ2luYWwtLS0tLQ0KPj4gRGU6IHRjbXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0
Y210Zi1ib3VuY2VzQGlldGYub3JnXSBFbiBub21icmUgZGUNCj4+IERhbiBXaW5nDQo+PiBFbnZp
YWRvIGVsOiB2aWVybmVzLCAxNCBkZSBkaWNpZW1icmUgZGUgMjAxMiAxODozMw0KPj4gUGFyYTog
anNhbGRhbmFAdW5pemFyLmVzOyAnTWlya28gU3XFvm5qZXZpxIcnDQo+PiBDQzogdGNtdGZAaWV0
Zi5vcmcNCj4+IEFzdW50bzogUmU6IFt0Y210Zl0gRHJhZnQ6IE1heGltdW0gVG9sZXJhYmxlIERl
bGF5cyB3aGVuIHVzaW5nIFR1bm5lbGluZw0KPj4gQ29tcHJlc3NlZCBNdWx0aXBsZXhlZCBUcmFm
ZmljIEZsb3dzDQo+Pg0KPj4gPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4gPiBGcm9t
OiBKb3NlIFNhbGRhbmEgW21haWx0bzpqc2FsZGFuYUB1bml6YXIuZXNdDQo+PiA+IFNlbnQ6IEZy
aWRheSwgRGVjZW1iZXIgMTQsIDIwMTIgMjo1OCBBTQ0KPj4gPiBUbzogJ0RhbiBXaW5nJzsgJ01p
cmtvIFN1xb5uamV2acSHJw0KPj4gPiBDYzogdGNtdGZAaWV0Zi5vcmcNCj4+ID4gU3ViamVjdDog
UkU6IFt0Y210Zl0gRHJhZnQ6IE1heGltdW0gVG9sZXJhYmxlIERlbGF5cyB3aGVuIHVzaW5nDQo+
PiA+IFR1bm5lbGluZyBDb21wcmVzc2VkIE11bHRpcGxleGVkIFRyYWZmaWMgRmxvd3MNCj4+ID4N
Cj4+ID4gRGFuLA0KPj4gPg0KPj4gPiBSZWdhcmRpbmcgdGhlIHVzZSBvZiB0aGUgbWF4aW11bSBk
ZWxheSwgc29tZSBkYXlzIGFnbyB3ZSBkaXNjdXNzZWQNCj4+ID4gYWJvdXQNCj4+ID4gaXQ6DQo+
PiA+IHRoZSBhY3R1YWwgT1dEIG9mIHRoZSBuZXR3b3JrIHNob3VsZCBiZSBtZWFzdXJlZCAob3Ig
ZXN0aW1hdGVkKSBpbg0KPj4gPiBvcmRlciB0byBrbm93IHRoZSBtYXhpbXVtIG11bHRpcGxleGlu
ZyBwZXJpb2Qgd2UgY2FuIHNldC4NCj4+ID4NCj4+ID4gV2UgbWF5IGhhdmUgdGhpcyBmb3JtdWxh
LCBpZiB0aGlua2luZyBvbmUtd2F5Og0KPj4gPg0KPj4gPiBPV0QgICsgTXV4IHBlcmlvZC8yICA8
IHRvbGVyYWJsZV9PV0QNCj4+ID4NCj4+ID4gSWYgd2UgdGhpbmsgUlRUOg0KPj4gPg0KPj4gPiBP
V0QgKyBNdXggcGVyaW9kLzIgKyBPV0QgYmFjayA8IDIqdG9sZXJhYmxlX09XRA0KPj4gPg0KPj4g
PiBJIGRvbid0IGtub3cgaWYgd2Ugc2hvdWxkIGluY2x1ZGUgYSBtZWNoYW5pc20gZm9yIGVzdGlt
YXRpbmcgT1dEIGluDQo+PiA+IHRjbXRmLiBJIHRoaW5rIHRoaXMgaXMgbW9yZSBhbiBpbXBsZW1l
bnRhdGlvbiBwcm9ibGVtLCB3aGljaCBtYXkgYmUNCj4+ID4gYWxyZWFkeSBzb2x2ZWQuDQo+Pg0K
Pj4gWWVzLCBpdCdzIGFscmVhZHkgc29sdmVkIGVuZC10by1lbmQ6ICBSVFAgd2l0aCBSVENQIGZl
ZWRiYWNrIGFsbG93cw0KPj4gZGV0ZXJtaW5pbmcgb25lIHdheSBkZWxheS4NCj4+DQo+PiBCdXQg
aWYgc29tZXRoaW5nIGluIHRoZSBtaWRkbGUgaXMgbXVsdGlwbGV4aW5nIHNldmVyYWwgcGFja2V0
cyB0b2dldGhlciwNCj53ZQ0KPj4gZG9uJ3Qgd2FudCBpdCB0byBhZGQgdG9vIG11Y2ggZGVsYXku
ICBUaGF0IHRoaW5nIGluIHRoZSBtaWRkbGUgd29uJ3QNCj4+IG5lY2Vzc2FyaWx5IGtub3cgdGhl
IG9uZSB3YXkgZGVsYXkgc2VlbiBieSB0aGUgZW5kcG9pbnRzLCB1bmxlc3MgaXQNCj4+IGFuYWx5
emVzIHRoZSBSVFAgYW5kIFJUQ1AuICBUaGVyZSBhcmUgZGV2aWNlcyB0aGF0IGRvIHRoYXQgb24g
dGhlDQo+Pm1hcmtldCwNCj4+IG1vc3RseSB0byBkaWFnbm9zZSB3aGVyZSBuZXR3b3JrcyBhcmUg
Y2F1c2luZyBsb3NzL2RlbGF5IHdpdGggUlRQIGZsb3dzLg0KPj4NCj4+DQo+PiA+IEFub3RoZXIg
b3B0aW9uIGlzIHVzaW5nIHNvbWUgdHlwaWNhbCB2YWx1ZXMsIGUuZy4gZnJvbQ0KPj4gPiBodHRw
Oi8vaXBuZXR3b3JrLmJndG1vLmlwLmF0dC5uZXQvcHdzL2dsb2JhbF9uZXR3b3JrX2F2Z3MuaHRt
bA0KPj4gPg0KPj4gPiBUaGUgZHJhZnQgaW5jbHVkZXMgc29tZSBwcmVsaW1pbmFyeS9yZWNvbW1l
bmRlZCB2YWx1ZXMgZm9yIHRoZQ0KPj4gPiBNdWx0aXBsZXhpbmcgUGVyaW9kLiBJcyB0aGlzIGlu
dGVyZXN0aW5nPyBTaG91bGQgd2UgcHV0IHRoZSBmb3JtdWxhDQo+PiA+IGluc3RlYWQ/DQo+Pg0K
Pj4gSXQncyBwcm9iYWJseSBzdWZmaWNpZW50IGFzLWlzLg0KPj4NCj4+IC1kDQo+Pg0KPj4gPiBN
aXJrbywgYW5vdGhlciBxdWVzdGlvbjogaW4gb25saW5lIGdhbWVzLCBwbGF5ZXJzIHVzdWFsbHkg
dGFsayBhYm91dA0KPj4gPiB0aGUgInBpbmciLCBhbmQgSSB0aGluayBpdCBtZWFucyBSVFQuIERv
bid0IHlvdSB0aGluayBpdCB3b3VsZCBiZQ0KPj4gPiBiZXR0ZXIgdG8gZGVmaW5lIGEgUlRUIGxp
bWl0IGluc3RlYWQgb2YgYSBPV0Qgb25lIGluIHRoYXQgY2FzZT8NCj4+ID4NCj4+ID4gV2hhdCBk
byB5b3UgdGhpbms/DQo+PiA+DQo+PiA+IEpvc2UNCj4+ID4NCj4+ID4gPiAtLS0tLU1lbnNhamUg
b3JpZ2luYWwtLS0tLQ0KPj4gPiA+IERlOiB0Y210Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86
dGNtdGYtYm91bmNlc0BpZXRmLm9yZ10gRW4gbm9tYnJlDQo+PiA+ID4gZGUgRGFuIFdpbmcgRW52
aWFkbyBlbDoganVldmVzLCAxMyBkZSBkaWNpZW1icmUgZGUgMjAxMiAxNzowNw0KPj4gPiA+IFBh
cmE6ICdNaXJrbyBTdcW+bmpldmnEhyc7IHRjbXRmQGlldGYub3JnDQo+PiA+ID4gQXN1bnRvOiBS
ZTogW3RjbXRmXSBEcmFmdDogTWF4aW11bSBUb2xlcmFibGUgRGVsYXlzIHdoZW4gdXNpbmcNCj4+
ID4gPiBUdW5uZWxpbmcgQ29tcHJlc3NlZCBNdWx0aXBsZXhlZCBUcmFmZmljIEZsb3dzDQo+PiA+
ID4NCj4+ID4gPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiA+ID4gPiBGcm9tOiB0
Y210Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86dGNtdGYtYm91bmNlc0BpZXRmLm9yZ10gT24N
Cj4+ID4gPiA+IEJlaGFsZiBPZiBNaXJrbyBTdcW+bmpldmljDQo+PiA+ID4gPiBTZW50OiBUaHVy
c2RheSwgRGVjZW1iZXIgMTMsIDIwMTIgMTowNyBBTQ0KPj4gPiA+ID4gVG86IHRjbXRmQGlldGYu
b3JnOyB0c3Z3Z0BpZXRmLm9yZw0KPj4gPiA+ID4gU3ViamVjdDogW3RjbXRmXSBEcmFmdDogTWF4
aW11bSBUb2xlcmFibGUgRGVsYXlzIHdoZW4gdXNpbmcNCj4+ID4gPiA+IFR1bm5lbGluZyBDb21w
cmVzc2VkIE11bHRpcGxleGVkIFRyYWZmaWMgRmxvd3MNCj4+ID4gPiA+DQo+PiA+ID4gPiBIZWxs
bywNCj4+ID4gPiA+DQo+PiA+ID4gPg0KPj4gPiA+ID4NCj4+ID4gPiA+IFdlIGhhdmUganVzdCBz
dWJtaXR0ZWQgdGhlIGRyYWZ0IG5hbWVkIE1heGltdW0gVG9sZXJhYmxlIERlbGF5cw0KPj4gPiA+
ID4gd2hlbiB1c2luZyBUdW5uZWxpbmcgQ29tcHJlc3NlZCBNdWx0aXBsZXhlZCBUcmFmZmljIEZs
b3dzOg0KPj4gPiA+ID4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1zdXpu
amV2aWMtdHN2d2ctbXRkLXRjbXRmLw0KPj4gPiA+DQo+PiA+ID4gVGhlIHN1Z2dlc3RlZCA0MDBt
cyBmb3IgaW50ZXJhY3RpdmUgdm9pY2UgaXMgYXQgbGVhc3QgMnggdG9vIGhpZ2guDQo+PiA+ID4g
SQ0KPj4gPiBleHBlY3QNCj4+ID4gPiB0aGF0IG51bWJlciBkb2VzIG5vdCBpbmNsdWRlIHRoZSBw
bGF5b3V0IGppdHRlciBidWZmZXIgKHdoaWNoIGlzDQo+PiA+ID4gdmFyaWFibGUsDQo+PiA+IGJ1
dA0KPj4gPiA+IHVzdWFsbHkgYSBmZXcgc2FtcGxlcywgc28gNDAtODBtcykuICAyMDBtcyBlbmQt
dG8tZW5kIGlzIHRoZSBoaWdoZXINCj4+ID4gPiBlbmQsDQo+PiA+IGFuZA0KPj4gPiA+IHRoYXQg
aW5jbHVkZXMgaml0dGVyIGJ1ZmZlciwgY29kZWMgcHJvY2Vzc2luZywgYW5kIHNvIG9uLg0KPj4g
PiA+DQo+PiA+ID4gQnV0LCBtb3JlIGltcG9ydGFudGx5OiAgaXQgc2VlbXMgdmFsdWFibGUgZm9y
IGVuZHBvaW50cyB0byBzaWduYWwNCj4+ID4gPiB0aGVpciBtYXhpbXVtIGRlbGF5IHNvbWVob3cu
ICBPciB3b3VsZCB0aGUgVENNVEYgZnVuY3Rpb24NCj4+IGRldGVybWluZQ0KPj4gPiA+IHRoZSBt
YXhpbXVtIGRlbGF5LCB1c2luZyBzb21lIGhldXJpc3RpYz8NCj4+ID4gPg0KPj4gPiA+IEhvdyBk
b2VzIHRoZSBUQ01URiBmdW5jdGlvbiBkZXRlcm1pbmUgaG93IG11Y2ggb2YgdGhhdCAndG9sZXJh
YmxlDQo+PiA+ID4gbGF0ZW5jeScgYnVkZ2V0IGl0IGNhbiBjb25zdW1lPw0KPj4gPiA+DQo+PiA+
ID4gLWQNCj4+ID4gPg0KPj4gPiA+DQo+PiA+ID4gPiBJdCBpcyBhbiBleHRlbnNpb24gb2YgdGNt
dGYgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC0NCj4+ID4gPiA+IHNhbGRh
bmEtdHN2d2ctdGNtdGYvLiBTaW5jZSBhIHNwZWNpZmljIGxpc3QgZm9yIHRjbXRmIGV4aXN0cw0K
Pj4gPiA+ID4gKHRjbXRmQGlldGYub3JnKSwgdGhlIGlkZWEgaXMgdG8gZGlzY3VzcyBpdCB0aGVy
ZS4NCj4+ID4gPiA+DQo+PiA+ID4gPg0KPj4gPiA+ID4NCj4+ID4gPiA+IFRoZSBkcmFmdCBjb250
YWlucyByZWNvbW1lbmRhdGlvbnMgZm9yIFRDTVRGIG11bHRpcGxleGluZyBwZXJpb2QNCj4+ID4g
PiA+IGZvciBkaWZmZXJlbnQgcmVhbC10aW1lIHNlcnZpY2VzLiBJbiBvcmRlciB0byBwcmV2ZW50
IFFvRQ0KPj4gPiA+ID4gZGVncmFkYXRpb24gb2YgcmVhbC10aW1lIHNlcnZpY2VzIHVzaW5nIFRD
TVRGLCBhIHBvbGljeSBkZWZpbmluZw0KPj4gPiA+ID4gYSBtdWx0aXBsZXhpbmcgcGVyaW9kIGNh
biBiZSBlbXBsb3llZC4gVmFsdWVzIG9mIG1heGltdW0gdG9sZXJhYmxlDQo+PiA+ID4gPiBkZWxh
eXMgcHJlc2VudGVkIGluDQo+PiA+ID4gdGhlDQo+PiA+ID4gPiBkcmFmdCBmb3JtIHRoZSBiYXNl
IG9mIHN1Y2ggcG9saWN5LiAgICBUaGUgcmVjb21tZW5kYXRpb25zIGFyZQ0KPj4gPiBwcmVzZW50
ZWQNCj4+ID4gPiA+IGZvciByZWFsLXRpbWUgbmV0d29yayBzZXJ2aWNlcyBpbiB3aGljaCBUQ1RN
RiBiYW5kd2lkdGgNCj4+ID4gPiA+IG9wdGltaXphdGlvbiBpcyBhcHBsaWNhYmxlIChpLmUuLCBz
ZXJ2aWNlcyAgd2hpY2ggaGF2ZSBsb3cgcGF5bG9hZA0KPj4gPiA+ID4gdG8gaGVhZGVyIHNpemUg
cmF0aW8gd2hpY2ggcmVzdWx0cyBpbiBoaWdoIHByb3RvY29sIG92ZXJoZWFkKS4NCj4+ID4gPiA+
DQo+PiA+ID4gPg0KPj4gPiA+ID4NCj4+ID4gPiA+IFlvdXIgZmVlZGJhY2sgd2lsbCBiZSB3ZWxj
b21lLiBUaGFuayB5b3UuDQo+PiA+ID4gPg0KPj4gPiA+ID4NCj4+ID4gPiA+IFNpbmNlcmVseSwN
Cj4+ID4gPiA+DQo+PiA+ID4gPiBNaXJrbyBTdXpuamV2aWMNCj4+ID4gPg0KPj4gPiA+DQo+PiA+
ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+ID4g
PiB0Y210ZiBtYWlsaW5nIGxpc3QNCj4+ID4gPiB0Y210ZkBpZXRmLm9yZw0KPj4gPiA+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCj4+DQo+PiBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gdGNtdGYgbWFpbGluZyBs
aXN0DQo+PiB0Y210ZkBpZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby90Y210Zg0KPg0KPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+dGNtdGYgbWFpbGluZyBsaXN0DQo+dGNtdGZAaWV0Zi5vcmcNCj5odHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQoNCg0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCg0KRXN0ZSBtZW5zYWplIHNlIGRpcmlnZSBleGNsdXNpdmFtZW50
ZSBhIHN1IGRlc3RpbmF0YXJpby4gUHVlZGUgY29uc3VsdGFyIG51ZXN0cmEgcG9sw610aWNhIGRl
IGVudsOtbyB5IHJlY2VwY2nDs24gZGUgY29ycmVvIGVsZWN0csOzbmljbyBlbiBlbCBlbmxhY2Ug
c2l0dWFkbyBtw6FzIGFiYWpvLg0KVGhpcyBtZXNzYWdlIGlzIGludGVuZGVkIGV4Y2x1c2l2ZWx5
IGZvciBpdHMgYWRkcmVzc2VlLiBXZSBvbmx5IHNlbmQgYW5kIHJlY2VpdmUgZW1haWwgb24gdGhl
IGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQgb3V0IGF0Og0KaHR0cDovL3d3dy50aWQuZXMvRVMvUEFH
SU5BUy9kaXNjbGFpbWVyLmFzcHgNCg==

From mramalho@cisco.com  Tue Jan 15 10:38:52 2013
Return-Path: <mramalho@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F004711E809C for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 10:38:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.298
X-Spam-Level: 
X-Spam-Status: No, score=-10.298 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
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 bWFeBAgfmXGq for <tcmtf@ietfa.amsl.com>; Tue, 15 Jan 2013 10:38:48 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id EDB6211E809A for <tcmtf@ietf.org>; Tue, 15 Jan 2013 10:38:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=30694; q=dns/txt; s=iport; t=1358275128; x=1359484728; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=T08P9OzU+XgX+PbrGrIeEcJF+jbiKlEfLoi1RWydWL4=; b=MhYNRocEPdimnXPi0nWAs6DMDRQ5kifITrBSbuD6OrpNAaUSiSoGZOxC 13bPgPfWax85Mm/jJI77AnmHcwJrYOo1KkYwFcqCBq9Jah4m2IjnBYAZs n3mzOHqFMpEgLbqcPSuqxZTMqsTTxXVnMutyXpum+UJE7+n7AbNF+O+tg 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwGAICh9VCtJXHA/2dsb2JhbAA7ChaCMqh+iQwBhWqDSRZzgh4BAQEELVwCAQgRBAEBCxYBBgcyFAkIAQEEARIIDAeHfgyoS45KjQAGBQWDR2EDiCyKLYRPjy2CdYFnCBce
X-IronPort-AV: E=Sophos;i="4.84,475,1355097600";  d="scan'208,217";a="162757343"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-4.cisco.com with ESMTP; 15 Jan 2013 18:38:46 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r0FIckVJ031738 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 15 Jan 2013 18:38:46 GMT
Received: from xmb-rcd-x12.cisco.com ([169.254.2.163]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Tue, 15 Jan 2013 12:38:46 -0600
From: "Michael Ramalho (mramalho)" <mramalho@cisco.com>
To: =?iso-8859-1?Q?MANUEL_NU=D1EZ_SANZ?= <mns@tid.es>, "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] TCMTF: Document B discussion: content and charter
Thread-Index: Ac3zAd2uYPABnQrZRziFoMS7yxCKNwAEJgsAAA5lTzA=
Date: Tue, 15 Jan 2013 18:38:45 +0000
Message-ID: <D21571530BF9644D9A443D6BD95B9103154C2B3A@xmb-rcd-x12.cisco.com>
References: <007b01cdf30e$f7d3b170$e77b1450$@unizar.es> <90ED8822CB577741B9A1668A47539312316DD456@EX10-MB1-MAD.hi.inet>
In-Reply-To: <90ED8822CB577741B9A1668A47539312316DD456@EX10-MB1-MAD.hi.inet>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.168.119]
Content-Type: multipart/alternative; boundary="_000_D21571530BF9644D9A443D6BD95B9103154C2B3Axmbrcdx12ciscoc_"
MIME-Version: 1.0
Subject: Re: [tcmtf] TCMTF: Document B discussion: content and charter
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, 15 Jan 2013 18:38:53 -0000

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

All,

My comments are in-line below (with "MAR:").

Michael Ramalho

From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of M=
ANUEL NU=D1EZ SANZ
Sent: Tuesday, January 15, 2013 7:16 AM
To: jsaldana@unizar.es; tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: Document B discussion: content and charter

Hi,
  I am going to do one=B4s bit.

It is true there are tons of classification methods, however the issue is t=
hat:

1.       It is not common its use, and therefore it is reasonable to suppos=
e a lot of packets/flows will not be classified.



MAR: True. But, given the move to the "Internet of [Things|Everything]" as =
I mentioned previously, the industry will soon send some type of "traffic c=
lass indication" to the network to help the network optimize itself. Until =
that day occurs, if you know: 1) NOTHING about the flow, AND 2) but believe=
 it may be a "real-time flow" AND 3) to TCMTF a packet from that flow would=
 add more than a few milliseconds of delay ... you probably should not TCMT=
F it.



MAR: "Real-time" is defined here as a packet relating to some human respons=
e time type of application (e.g., remote desktop virtualization sent over T=
CP might be considered "real-time").



2.       And even when a flow is classified, it is possible than that class=
ification does not identify the delays for that flow.



MAR: Most real-time traffic classifiers DO NOT specify a hard limit on the =
"per-hop" added delay. But would you delay a TCP flow that said it was a "V=
oice packet" by 1000 milliseconds by TCMTFing it? Before you think that wou=
ldn't ever  happen, there a lot of real time packets sent over TCP to get t=
hrough firewals after all attempts to send such a packet over UDP fails. As=
 an aside, signature analysis could help in these cases.



MAR: Note that most of my concern is moot when TCMTF is operating on high r=
ate output links - as most compressions will result in TCMTF delays of less=
 than a few milliseconds.


Therefore under my opinion (quite similar to Fernando) is that it is necess=
ary the MUX "obtain" the configuration to know than flow are TCMTFed. In th=
at line, there are three different approaches:

1.       A static configuration (as an initial state)

2.       A policy manager dynamically enforces the option for each new flow

3.       The MUX asks for instruction for each "new" flow to an "policy man=
ager" or "controller". This last options is fully compatible with the 2 opt=
ion.



MAR: A "good TCMTF tunneling function" should make an intelligent decision =
regarding what flows it thinks is acceptable to TCMTF and which it should n=
ot. We need to allow room for products to differentiate themselves. Thus, I=
 think we ought to provide some guidance without being overly prescriptive.=
 I think we should error on the side of acknowledging the issue and providi=
ng guidance to implementers via a "SHOULD strength" requirement in the draf=
t.

And answering the question about open the scope of document B. I agree.

Regards,
  Manuel N=FA=F1ez

[MAR: Does anyone know how I tell MSFT Outlook that I don't want to reply i=
n Spanish ... it keeps "correcting" my American English reply with incorrec=
t Spanish words!]

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de Jos=
e Saldana
Enviado el: martes, 15 de enero de 2013 11:56
Para: tcmtf@ietf.org
Asunto: [tcmtf] TCMTF: Document B discussion: content and charter

Document (B) refers to the informational draft about maximum tolerable dela=
ys, currently in http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-=
tcmtf/

1.- Content of the Document

Currently, the Document specifies the maximum added delays for different se=
rvices.

However, the discussion has set clear that other things should be added, ma=
inly methods for identifying the flows:


Michael: "has any detailed thought about how TCMTF might identify which flo=
ws it should NOT attempt to compress?

Considering "the Internet of things" (where virtually every device is conne=
cted via IP) ... we can expect a lot of small packets ... but not necessari=
ly know if we should compress them or not (e.g., FPS packets) ... or what t=
he delay bounds on the compression should be.
Should we mention that flows that signal their own traffic class (e.g., usi=
ng "Metadata" describing the flow) is a good thing to differentiate on? Sho=
uld we suggest signature analysis (a probabilistic guess for the applicatio=
n based on its time-domain signature characteristics) might also be of util=
ity?"

Fernando had another opinion: "On the other hand,  the selection of flows t=
o be potentially TCMTFed could be something undefined at the beginning (it =
may be statically configured for example), but it is something that will NE=
ED to be defined to be dynamically enforced at the mux from a higher entity=
 (policy manager). That functionality would be addressed to a different dra=
ft in the future, re-chartering the WG."


Jose: "Perhaps a "natural" way could be widening the scope of draft (B), in=
cluding not only delay limits, but also currently existing traffic classifi=
cation methods which could be useful for selecting the packets to multiplex=
. Does this sound well?"



Mirko: "I think there is no need to develop something for traffic classific=
ation in the scope of TCMTF WG. There is a large research community doing t=
raffic classification and some of the already developed techniques can be a=
pplied for our need. It may be feasible to present an overview of technique=
s which could be used by TCMTF in draft B."



Luigi: "There are tons of classification methods out there, developing a ne=
w one does not look very useful to me."



Michael: "I agree with Luigi and Mirko ... there are more than enough peopl=
e working on traffic flow descriptions ... and how to signal/inform network=
s of their requirements (e.g., per-hop behaviors and the like). (...) For n=
ow, I would recommend a placeholder in the draft that addresses the concern=
 and that TCMTF SHOULD consider the traffic class of the flows when such in=
formation is available."



So perhaps the solution could be widening the scope of the Document (B) in =
order to also include:

                - TCMTF SHOULD consider the traffic class of the flows when=
 such information is available

                - Suggesting traffic classification methods which could be =
useful in order to do this



What do you think? Is everyone ok with this?






2.- Should we include it in the Charter now?

Of course, Document (B) should be included in the Charter.


Best regards,

Jose


Jose Saldana, PhD
Communications Technologies Group (GTC)
Dpt. Electrical Engineering and Communications
EINA, University of Zaragoza.
C/ Mar=EDa de Luna 1, Edif. Ada Byron, D. 2.05
50018 Zaragoza, Spain
Tel: +34 976 76 2698
Ext: 2698
E-mail: jsaldana@unizar.es<mailto:jsaldana@unizar.es>
http://diec.unizar.es/~jsaldana/personal/index.htm


________________________________

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

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	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:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
span.textosinformatocar
	{mso-style-name:textosinformatocar;
	font-family:"Calibri","sans-serif";}
span.estilocorreo19
	{mso-style-name:estilocorreo19;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.estilocorreo20
	{mso-style-name:estilocorreo20;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">All,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">My comments are in-lin=
e below (with &#8220;MAR:&#8220;).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Michael Ramalho<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tcmtf-bo=
unces@ietf.org [mailto:tcmtf-bounces@ietf.org]
<b>On Behalf Of </b>MANUEL NU=D1EZ SANZ<br>
<b>Sent:</b> Tuesday, January 15, 2013 7:16 AM<br>
<b>To:</b> jsaldana@unizar.es; tcmtf@ietf.org<br>
<b>Subject:</b> Re: [tcmtf] TCMTF: Document B discussion: content and chart=
er<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi, </span><span lang=
=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;I am going=
 to do one=B4s bit. </span>
<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">It is true there are t=
ons of classification methods, however the issue is that:</span><span lang=
=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"c=
olor:#1F497D">1.</span><span style=3D"font-size:7.0pt;font-family:&quot;Tim=
es New Roman&quot;,&quot;serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span><span style=3D"color:#1F497D">It is not common its use, and therefor=
e it is reasonable to suppose a lot of packets/flows will not be classified=
.</span><o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"c=
olor:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span style=3D"colo=
r:#1F497D">MAR: True. But, given the move to the &#8220;Internet of [Things=
|Everything]&#8221; as I mentioned previously, the industry will soon send =
some type of &#8220;traffic class indication&#8221; to the network
 to help the network optimize itself. Until that day occurs, if you know: 1=
) NOTHING about the flow, AND 2) but believe it may be a &#8220;real-time f=
low&#8221; AND 3) to TCMTF a packet from that flow would add more than a fe=
w milliseconds of delay &#8230; you probably should
 not TCMTF it.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span style=3D"colo=
r:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span style=3D"colo=
r:#1F497D">MAR: &#8220;Real-time&#8221; is defined here as a packet relatin=
g to some human response time type of application (e.g., remote desktop vir=
tualization sent over TCP might be considered &#8220;real-time&#8221;).<o:p=
></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span lang=3D"ES" s=
tyle=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><span style=3D"c=
olor:#1F497D">2.</span><span style=3D"font-size:7.0pt;font-family:&quot;Tim=
es New Roman&quot;,&quot;serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span><span style=3D"color:#1F497D">And even when a flow is classified, it=
 is possible than that classification does not identify the delays for that=
 flow.</span><o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span lang=3D"ES" s=
tyle=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span lang=3D"ES" s=
tyle=3D"color:#1F497D">MAR: Most real-time traffic classifiers DO NOT speci=
fy a hard limit on the &#8220;per-hop&#8221; added delay. But would you del=
ay a TCP flow that said it was a &#8220;Voice packet&#8221; by 1000
 milliseconds by TCMTFing it? Before you think that wouldn&#8217;t ever &nb=
sp;happen, there a lot of real time packets sent over TCP to get through fi=
rewals after all attempts to send such a packet over UDP fails. As an aside=
, signature analysis could help in these cases.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span lang=3D"ES" s=
tyle=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span lang=3D"ES" s=
tyle=3D"color:#1F497D">MAR: Note that most of my concern is moot when TCMTF=
 is operating on high rate output links &#8211; as most compressions will r=
esult in TCMTF delays of less than a few milliseconds.<o:p></o:p></span></p=
>
<p class=3D"MsoListParagraph"><span style=3D"color:#1F497D">&nbsp;</span><s=
pan lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Therefore under my opi=
nion (quite similar to Fernando) is that it is necessary the MUX &#8220;obt=
ain&#8221; the configuration to know than flow are TCMTFed. In that line, t=
here are three different approaches:</span><span lang=3D"ES"><o:p></o:p></s=
pan></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:38.25pt;text-indent:-.25=
in"><span style=3D"color:#1F497D">1.</span><span style=3D"font-size:7.0pt;f=
ont-family:&quot;Times New Roman&quot;,&quot;serif&quot;;color:#1F497D">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"color:#1F497D">A static configuration (as an initial =
state)</span><span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:38.25pt;text-indent:-.25=
in"><span style=3D"color:#1F497D">2.</span><span style=3D"font-size:7.0pt;f=
ont-family:&quot;Times New Roman&quot;,&quot;serif&quot;;color:#1F497D">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"color:#1F497D">A policy manager dynamically enforces =
the option for each new flow</span><span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:38.25pt;text-indent:-.25=
in"><span style=3D"color:#1F497D">3.</span><span style=3D"font-size:7.0pt;f=
ont-family:&quot;Times New Roman&quot;,&quot;serif&quot;;color:#1F497D">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span style=3D"color:#1F497D">The MUX asks for instruction for each =
&#8220;new&#8221; flow to an &#8220;policy manager&#8221; or &#8220;control=
ler&#8221;. This last options is fully compatible with the 2 option.</span>=
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span lang=3D"ES" s=
tyle=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span lang=3D"ES" s=
tyle=3D"color:#1F497D">MAR: A &#8220;good TCMTF tunneling function&#8221; s=
hould make an intelligent decision regarding what flows it thinks is accept=
able to TCMTF and which it should not. We need to allow
 room for products to differentiate themselves. Thus, I think we ought to p=
rovide some guidance without being overly prescriptive. I think we should e=
rror on the side of acknowledging the issue and providing guidance to imple=
menters via a &#8220;SHOULD strength&#8221;
 requirement in the draft.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">And answering the ques=
tion about open the scope of document B. I agree.
</span><span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards, </span><span =
lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;Manuel N=
=FA=F1ez</span><span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[MAR: Does anyone know=
 how I tell MSFT Outlook that I don&#8217;t want to reply in Spanish &#8230=
; it keeps &#8220;correcting&#8221; my American English reply with incorrec=
t Spanish words!]</span><span style=3D"color:#1F497D">&nbsp;</span><span st=
yle=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span lan=
g=3D"ES"><o:p></o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"ES" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">De:</span></b><span lang=
=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans=
-serif&quot;"> tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org]
<b>En nombre de </b>Jose Saldana<br>
<b>Enviado el:</b> martes, 15 de enero de 2013 11:56<br>
<b>Para:</b> tcmtf@ietf.org<br>
<b>Asunto:</b> [tcmtf] TCMTF: Document B discussion: content and charter</s=
pan><span lang=3D"ES"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal">Document (B) refers to the informational draft about=
 maximum tolerable delays, currently in
<a href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/=
">http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a><span=
 lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">1.- Content of the Document<span lang=3D"ES"><o:p></=
o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">Currently, the Document specifies the maximum added =
delays for different services.<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">However, the discussion has set clear that other thi=
ngs should be added, mainly methods for identifying the flows:<span lang=3D=
"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"text-indent:35.4pt">Michael: &#8220;has =
any detailed thought about how TCMTF might identify which flows it should N=
OT attempt to compress?<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt">Considering &quot;th=
e Internet of things&quot; (where virtually every device is connected via I=
P) ... we can expect a lot of small packets ... but not necessarily know if=
 we should compress them or not (e.g., FPS packets)
 ... or what the delay bounds on the compression should be.<span lang=3D"ES=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt">Should we mention that =
flows that signal their own traffic class (e.g., using &quot;Metadata&quot;=
 describing the flow) is a good thing to differentiate on? Should we sugges=
t signature analysis (a probabilistic guess for
 the application based on its time-domain signature characteristics) might =
also be of utility?&#8221;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.25pt">Fernando had another o=
pinion: &#8220;On the other hand,&nbsp; the selection of flows to be potent=
ially TCMTFed could be something undefined at the beginning (it may be stat=
ically configured for example), but it is something
 that will NEED to be defined to be dynamically enforced at the mux from a =
higher entity (policy manager). That functionality would be addressed to a =
different draft in the future, re-chartering the WG.&#8221;<span lang=3D"ES=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt">Jose: &#8220;Perhap=
s a &quot;natural&quot; way could be widening the scope of draft (B), inclu=
ding not only delay limits, but also currently existing traffic classificat=
ion methods which could be useful for selecting the
 packets to multiplex. Does this sound well?&#8221;<span lang=3D"ES"><o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt">&nbsp;<span lang=3D=
"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt">Mirko: &#8220;I thi=
nk there is no need to develop something for traffic classification in the =
scope of TCMTF WG. There is a large research community doing traffic classi=
fication and some of the already developed
 techniques can be applied for our need. It may be feasible to present an o=
verview of techniques which could be used by TCMTF in draft B.&#8221;<span =
lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt">&nbsp;<span lang=3D=
"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt">Luigi: &#8220;There=
 are tons of classification methods out there, developing a new one does no=
t look very useful to me.&#8221;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt">&nbsp;<span lang=3D=
"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt">Michael: &#8220;I a=
gree with Luigi and Mirko ... there are more than enough people working on =
traffic flow descriptions ... and how to signal/inform networks of their re=
quirements (e.g., per-hop behaviors and the
 like). (&#8230;) For now, I would recommend a placeholder in the draft tha=
t addresses the concern and that TCMTF SHOULD consider the traffic class of=
 the flows when such information is available.&#8221;<span lang=3D"ES"><o:p=
></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt">&nbsp;<span lang=3D=
"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText">So perhaps the solution could be widening the sco=
pe of the Document (B) in order to also include:<span lang=3D"ES"><o:p></o:=
p></span></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - TCMTF SHOULD consider the traff=
ic class of the flows when such information is available<span lang=3D"ES"><=
o:p></o:p></span></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Suggesting traffic classificati=
on methods which could be useful in order to do this
<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText">What do you think? Is everyone ok with this?<span=
 lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoPlainText">2.- Should we include it in the Charter now?<span=
 lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">Of course, Document (B) should be included in the Ch=
arter.<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">Best regards,<span lang=3D"ES"><o:p></o:p></span></p=
>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">Jose<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Jose Saldana, PhD</span><span lang=3D"ES"=
><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Communications Technologies Group (GTC)<b=
r>
Dpt. Electrical Engineering and Communications<br>
EINA, University of Zaragoza.<br>
</span><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;">C/ Mar=EDa de Luna 1, Edif. Ada Byron, D. 2.0=
5<br>
50018 Zaragoza, Spain</span><span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;">Tel: &#43;34 976 76 2698</spa=
n><span lang=3D"ES"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Ext: 2698</span><span lang=3D"ES"><o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">E-mail:
</span><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;"><a href=3D"mailto:jsaldana@unizar.es"><span l=
ang=3D"EN-US">jsaldana@unizar.es</span></a></span><span lang=3D"ES"><o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:10.0pt;font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;"><a href=3D"http://diec.unizar=
.es/~jsaldana/personal/index.htm"><span lang=3D"EN-US">http://diec.unizar.e=
s/~jsaldana/personal/index.htm</span></a></span><span lang=3D"ES"><o:p></o:=
p></span></p>
<p class=3D"MsoNormal">&nbsp;<span lang=3D"ES"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:12.0pt;font-fam=
ily:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span>=
</p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"ES" style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&qu=
ot;,&quot;serif&quot;">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:7.5pt;font-fami=
ly:&quot;Arial&quot;,&quot;sans-serif&quot;;color:gray"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span lang=3D"ES" style=3D"font-size:1=
2.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p=
></span></p>
</div>
</body>
</html>

--_000_D21571530BF9644D9A443D6BD95B9103154C2B3Axmbrcdx12ciscoc_--

From jsaldana@unizar.es  Wed Jan 16 02:15:15 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0397821F8D17 for <tcmtf@ietfa.amsl.com>; Wed, 16 Jan 2013 02:15:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.429
X-Spam-Level: 
X-Spam-Status: No, score=-6.429 tagged_above=-999 required=5 tests=[AWL=-0.131, 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 wQSie4fMBLhD for <tcmtf@ietfa.amsl.com>; Wed, 16 Jan 2013 02:15:09 -0800 (PST)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 73F0521F8633 for <tcmtf@ietf.org>; Wed, 16 Jan 2013 02:15:08 -0800 (PST)
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 r0GAF0lJ023441; Wed, 16 Jan 2013 11:15:00 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Michael Ramalho \(mramalho\)'" <mramalho@cisco.com>, "=?iso-8859-1?Q?'MANUEL_NU=D1EZ_SANZ'?=" <mns@tid.es>, "Fernando Pascual Blanco" <fpb@tid.es>
References: <007b01cdf30e$f7d3b170$e77b1450$@unizar.es> <90ED8822CB577741B9A1668A47539312316DD456@EX10-MB1-MAD.hi.inet> <D21571530BF9644D9A443D6BD95B9103154C2B3A@xmb-rcd-x12.cisco.com>
In-Reply-To: <D21571530BF9644D9A443D6BD95B9103154C2B3A@xmb-rcd-x12.cisco.com>
Date: Wed, 16 Jan 2013 11:15:04 +0100
Organization: Universidad de Zaragoza
Message-ID: <003b01cdf3d2$5a1304d0$0e390e70$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_003C_01CDF3DA.BBD9DDD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFd2vPfb5lHZQBTAaBp969CvrTxqQJtUSMoAWqVZZGZDSDs8A==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: Document B discussion: content and charter
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, 16 Jan 2013 10:15:15 -0000

This is a multipart message in MIME format.

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

Hi all,

=20

I think we agree on this (if not, please report it):

=20

#1 Document B has to be in the Charter

#2 Document B has to specify maximum delays for different services

#3 Document B has to include some recommendations about the use of =
traffic
classification methods

=20

=20

So the question is now related to #3:

=20

How to include that recommendations about traffic classification =
methods:
putting a SHOULD or not, etc.

=20

=20

But my question:

=20

Do we need to decide this now? Is this decision necessary in order to =
write
the Charter? Perhaps it is not, and we can go ahead with it. My proposal =
for
the paragraph about Document (B) in the Charter:=20

=20

6. 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 =
which
can be useful in order to decide which packet flows can or can not be
multiplexed: recommendations about the use of available traffic
classification methods; the maximum delay and jitter to be added to each
kind of service or application; other recommendations can be included if
necessary. Empirical research studies with real users will be necessary =
in
order to establish this set of recommendations.

=20

What do you think? Do you like this paragraph for the Charter? =
Improvement
suggestions will be welcome.

=20

Best reards,

=20

Jose

=20

De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com]=20
Enviado el: martes, 15 de enero de 2013 19:39
Para: MANUEL NU=D1EZ SANZ; jsaldana@unizar.es; tcmtf@ietf.org
Asunto: RE: [tcmtf] TCMTF: Document B discussion: content and charter

=20

All,

=20

My comments are in-line below (with =93MAR:=93).

=20

Michael Ramalho

=20

From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =
Of
MANUEL NU=D1EZ SANZ
Sent: Tuesday, January 15, 2013 7:16 AM
To: jsaldana@unizar.es; tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: Document B discussion: content and charter

=20

Hi,=20

  I am going to do one=B4s bit.=20

=20

It is true there are tons of classification methods, however the issue =
is
that:

1.       It is not common its use, and therefore it is reasonable to =
suppose
a lot of packets/flows will not be classified.

=20

MAR: True. But, given the move to the =93Internet of =
[Things|Everything]=94 as I
mentioned previously, the industry will soon send some type of =
=93traffic
class indication=94 to the network to help the network optimize itself. =
Until
that day occurs, if you know: 1) NOTHING about the flow, AND 2) but =
believe
it may be a =93real-time flow=94 AND 3) to TCMTF a packet from that flow =
would
add more than a few milliseconds of delay =85 you probably should not =
TCMTF
it.

=20

MAR: =93Real-time=94 is defined here as a packet relating to some human =
response
time type of application (e.g., remote desktop virtualization sent over =
TCP
might be considered =93real-time=94).

=20

2.       And even when a flow is classified, it is possible than that
classification does not identify the delays for that flow.

=20

MAR: Most real-time traffic classifiers DO NOT specify a hard limit on =
the
=93per-hop=94 added delay. But would you delay a TCP flow that said it =
was a
=93Voice packet=94 by 1000 milliseconds by TCMTFing it? Before you think =
that
wouldn=92t ever  happen, there a lot of real time packets sent over TCP =
to get
through firewals after all attempts to send such a packet over UDP =
fails. As
an aside, signature analysis could help in these cases.

=20

MAR: Note that most of my concern is moot when TCMTF is operating on =
high
rate output links =96 as most compressions will result in TCMTF delays =
of less
than a few milliseconds.

=20

Therefore under my opinion (quite similar to Fernando) is that it is
necessary the MUX =93obtain=94 the configuration to know than flow are =
TCMTFed.
In that line, there are three different approaches:

1.       A static configuration (as an initial state)

2.       A policy manager dynamically enforces the option for each new =
flow

3.       The MUX asks for instruction for each =93new=94 flow to an =
=93policy
manager=94 or =93controller=94. This last options is fully compatible =
with the 2
option.

=20

MAR: A =93good TCMTF tunneling function=94 should make an intelligent =
decision
regarding what flows it thinks is acceptable to TCMTF and which it =
should
not. We need to allow room for products to differentiate themselves. =
Thus, I
think we ought to provide some guidance without being overly =
prescriptive. I
think we should error on the side of acknowledging the issue and =
providing
guidance to implementers via a =93SHOULD strength=94 requirement in the =
draft.

=20

And answering the question about open the scope of document B. I agree.=20

=20

Regards,=20

  Manuel N=FA=F1ez

=20

[MAR: Does anyone know how I tell MSFT Outlook that I don=92t want to =
reply in
Spanish =85 it keeps =93correcting=94 my American English reply with =
incorrect
Spanish words!]=20

=20

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de =
Jose
Saldana
Enviado el: martes, 15 de enero de 2013 11:56
Para: tcmtf@ietf.org
Asunto: [tcmtf] TCMTF: Document B discussion: content and charter

=20

Document (B) refers to the informational draft about maximum tolerable
delays, currently in
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/

=20

1.- Content of the Document

=20

Currently, the Document specifies the maximum added delays for different
services.

=20

However, the discussion has set clear that other things should be added,
mainly methods for identifying the flows:

=20

Michael: =93has any detailed thought about how TCMTF might identify =
which
flows it should NOT attempt to compress?

Considering "the Internet of things" (where virtually every device is
connected via IP) ... we can expect a lot of small packets ... but not
necessarily know if we should compress them or not (e.g., FPS packets) =
...
or what the delay bounds on the compression should be.

Should we mention that flows that signal their own traffic class (e.g.,
using "Metadata" describing the flow) is a good thing to differentiate =
on?
Should we suggest signature analysis (a probabilistic guess for the
application based on its time-domain signature characteristics) might =
also
be of utility?=94

=20

Fernando had another opinion: =93On the other hand,  the selection of =
flows to
be potentially TCMTFed could be something undefined at the beginning (it =
may
be statically configured for example), but it is something that will =
NEED to
be defined to be dynamically enforced at the mux from a higher entity
(policy manager). That functionality would be addressed to a different =
draft
in the future, re-chartering the WG.=94

=20

Jose: =93Perhaps a "natural" way could be widening the scope of draft =
(B),
including not only delay limits, but also currently existing traffic
classification methods which could be useful for selecting the packets =
to
multiplex. Does this sound well?=94

=20

Mirko: =93I think there is no need to develop something for traffic
classification in the scope of TCMTF WG. There is a large research =
community
doing traffic classification and some of the already developed =
techniques
can be applied for our need. It may be feasible to present an overview =
of
techniques which could be used by TCMTF in draft B.=94

=20

Luigi: =93There are tons of classification methods out there, developing =
a new
one does not look very useful to me.=94

=20

Michael: =93I agree with Luigi and Mirko ... there are more than enough =
people
working on traffic flow descriptions ... and how to signal/inform =
networks
of their requirements (e.g., per-hop behaviors and the like). (=85) For =
now, I
would recommend a placeholder in the draft that addresses the concern =
and
that TCMTF SHOULD consider the traffic class of the flows when such
information is available.=94

=20

So perhaps the solution could be widening the scope of the Document (B) =
in
order to also include:

                - TCMTF SHOULD consider the traffic class of the flows =
when
such information is available

                - Suggesting traffic classification methods which could =
be
useful in order to do this=20

=20

What do you think? Is everyone ok with this?

=20

=20

=20

2.- Should we include it in the Charter now?

=20

Of course, Document (B) should be included in the Charter.

=20

=20

Best regards,

=20

Jose

=20

=20

Jose Saldana, PhD

Communications Technologies Group (GTC)
Dpt. Electrical Engineering and Communications
EINA, University of Zaragoza.
C/ Mar=EDa de Luna 1, Edif. Ada Byron, D. 2.05
50018 Zaragoza, Spain

Tel: +34 976 76 2698

Ext: 2698

E-mail:  <mailto:jsaldana@unizar.es> jsaldana@unizar.es

 <http://diec.unizar.es/~jsaldana/personal/index.htm>
http://diec.unizar.es/~jsaldana/personal/index.htm

=20

=20

  _____ =20


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


------=_NextPart_000_003C_01CDF3DA.BBD9DDD0
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:"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.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:Consolas;}
span.TextodegloboCar
	{mso-style-name:"Texto de globo Car";
	mso-style-priority:99;
	mso-style-link:"Texto de globo";
	font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.textosinformatocar0
	{mso-style-name:textosinformatocar;
	font-family:"Calibri","sans-serif";}
span.estilocorreo19
	{mso-style-name:estilocorreo19;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.estilocorreo20
	{mso-style-name:estilocorreo20;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EstiloCorreo28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EstiloCorreo31
	{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:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Hi all,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>I think we =
agree on this (if not, please report it):<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 Document =
B has to be in the Charter<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>#2 Document =
B has to specify maximum delays for different =
services<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>#3 Document B has to include some =
recommendations about the use of traffic classification =
methods<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 the =
question is now related to #3:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>How to =
include that recommendations about traffic classification methods: =
putting a SHOULD or not, etc.<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'>But my =
question:<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'>Do we need =
to decide this now? Is this decision necessary in order to write the =
Charter? Perhaps it is not, and we can go ahead with it. My proposal for =
the paragraph about Document (B) in the Charter: =
<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>6. 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 which can be useful in order =
to decide which packet flows can or can not be multiplexed: =
recommendations about the use of available traffic classification =
methods; the maximum delay and jitter to be added to each kind of =
service or application; other recommendations can be included if =
necessary. 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=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'>What do you =
think? Do you like this paragraph for the Charter? Improvement =
suggestions will be welcome.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Best =
reards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Michael =
Ramalho (mramalho) [mailto:mramalho@cisco.com] =
<br><b>Env</b></span><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>iado =
el:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> martes, 15 =
de enero de 2013 19:39<br><b>Para:</b> MANUEL NU=D1EZ SANZ; =
jsaldana@unizar.es; tcmtf@ietf.org<br><b>Asunto:</b> RE: [tcmtf] TCMTF: =
Document B discussion: content and =
charter<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>All,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>My comments =
are in-line below (with &#8220;MAR:&#8220;).<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Michael =
Ramalho<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a =
href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a =
href=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]=
 <b>On Behalf Of </b>MANUEL NU=D1EZ SANZ<br><b>Sent:</b> Tuesday, =
January 15, 2013 7:16 AM<br><b>To:</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>Subject:</b> Re: =
[tcmtf] TCMTF: Document B discussion: content and =
charter<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Hi, </span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>&nbsp;&nbsp;I am going to do one=B4s bit. =
</span><o:p></o:p></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>It is true =
there are tons of classification methods, however the issue is =
that:</span><o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt'><span lang=3DEN-US =
style=3D'color:#1F497D'>1.</span><span lang=3DEN-US =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span><span lang=3DEN-US style=3D'color:#1F497D'>It is not common its =
use, and therefore it is reasonable to suppose a lot of packets/flows =
will not be classified.</span><span =
lang=3DEN-US><o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt'><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'margin-left:0cm'><span lang=3DEN-US =
style=3D'color:#1F497D'>MAR: True. But, given the move to the =
&#8220;Internet of [Things|Everything]&#8221; as I mentioned previously, =
the industry will soon send some type of &#8220;traffic class =
indication&#8221; to the network to help the network optimize itself. =
Until that day occurs, if you know: 1) NOTHING about the flow, AND 2) =
but believe it may be a &#8220;real-time flow&#8221; AND 3) to TCMTF a =
packet from that flow would add more than a few milliseconds of delay =
&#8230; you probably should not TCMTF it.<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'margin-left:0cm'><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'margin-left:0cm'><span lang=3DEN-US =
style=3D'color:#1F497D'>MAR: &#8220;Real-time&#8221; is defined here as =
a packet relating to some human response time type of application (e.g., =
remote desktop virtualization sent over TCP might be considered =
&#8220;real-time&#8221;).<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'margin-left:0cm'><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt'><span =
lang=3DEN-US style=3D'color:#1F497D'>2.</span><span lang=3DEN-US =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span><span lang=3DEN-US style=3D'color:#1F497D'>And even when a flow =
is classified, it is possible than that classification does not identify =
the delays for that flow.</span><span =
lang=3DEN-US><o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:0cm'><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'margin-left:0cm'><span =
style=3D'color:#1F497D'>MAR: Most real-time traffic classifiers DO NOT =
specify a hard limit on the &#8220;per-hop&#8221; added delay. But would =
you delay a TCP flow that said it was a &#8220;Voice packet&#8221; by =
1000 milliseconds by TCMTFing it? Before you think that wouldn&#8217;t =
ever &nbsp;happen, there a lot of real time packets sent over TCP to get =
through firewals after all attempts to send such a packet over UDP =
fails. As an aside, signature analysis could help in these =
cases.<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:0cm'><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'margin-left:0cm'><span =
style=3D'color:#1F497D'>MAR: Note that most of my concern is moot when =
TCMTF is operating on high rate output links &#8211; as most =
compressions will result in TCMTF delays of less than a few =
milliseconds.<o:p></o:p></span></p><p class=3DMsoListParagraph><span =
lang=3DEN-US style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Therefore =
under my opinion (quite similar to Fernando) is that it is necessary the =
MUX &#8220;obtain&#8221; the configuration to know than flow are =
TCMTFed. In that line, there are three different =
approaches:</span><o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:38.25pt;text-indent:-18.0pt'><span lang=3DEN-US =
style=3D'color:#1F497D'>1.</span><span lang=3DEN-US =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span><span lang=3DEN-US style=3D'color:#1F497D'>A static configuration =
(as an initial state)</span><o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:38.25pt;text-indent:-18.0pt'><span lang=3DEN-US =
style=3D'color:#1F497D'>2.</span><span lang=3DEN-US =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span><span lang=3DEN-US style=3D'color:#1F497D'>A policy manager =
dynamically enforces the option for each new =
flow</span><o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:38.25pt;text-indent:-18.0pt'><span lang=3DEN-US =
style=3D'color:#1F497D'>3.</span><span lang=3DEN-US =
style=3D'font-size:7.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span><span lang=3DEN-US style=3D'color:#1F497D'>The MUX asks for =
instruction for each &#8220;new&#8221; flow to an &#8220;policy =
manager&#8221; or &#8220;controller&#8221;. This last options is fully =
compatible with the 2 option.</span><span =
lang=3DEN-US><o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:0cm'><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'margin-left:0cm'><span =
style=3D'color:#1F497D'>MAR: A &#8220;good TCMTF tunneling =
function&#8221; should make an intelligent decision regarding what flows =
it thinks is acceptable to TCMTF and which it should not. We need to =
allow room for products to differentiate themselves. Thus, I think we =
ought to provide some guidance without being overly prescriptive. I =
think we should error on the side of acknowledging the issue and =
providing guidance to implementers via a &#8220;SHOULD strength&#8221; =
requirement in the draft.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>And =
answering the question about open the scope of document B. I agree. =
</span><o:p></o:p></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Regards, =
</span><o:p></o:p></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>&nbsp;&nbsp;Manuel =
N=FA=F1ez</span><o:p></o:p></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'>[MAR: Does =
anyone know how I tell MSFT Outlook that I don&#8217;t want to reply in =
Spanish &#8230; it keeps &#8220;correcting&#8221; my American English =
reply with incorrect Spanish words!]&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a =
href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a =
href=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]=
 <b>En nombre de </b>Jose Saldana<br><b>Enviado el:</b> martes, 15 de =
enero de 2013 11:56<br><b>Para:</b> <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><b>Asunto:</b> =
[tcmtf] TCMTF: Document B discussion: content and =
charter</span><o:p></o:p></p></div></div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>Document (B) refers to the informational draft about =
maximum tolerable delays, currently in <a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a></sp=
an><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>1.- Content of the Document</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>Currently, the Document specifies =
the maximum added delays for different services.</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>However, the discussion has set =
clear that other things should be added, mainly methods for identifying =
the flows:</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'text-indent:35.4pt'><span lang=3DEN-US>Michael: &#8220;has any =
detailed thought about how TCMTF might identify which flows it should =
NOT attempt to compress?</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:35.4pt'><span lang=3DEN-US>Considering &quot;the =
Internet of things&quot; (where virtually every device is connected via =
IP) ... we can expect a lot of small packets ... but not necessarily =
know if we should compress them or not (e.g., FPS packets) ... or what =
the delay bounds on the compression should be.</span><o:p></o:p></p><p =
class=3DMsoNormal style=3D'margin-left:35.4pt'><span lang=3DEN-US>Should =
we mention that flows that signal their own traffic class (e.g., using =
&quot;Metadata&quot; describing the flow) is a good thing to =
differentiate on? Should we suggest signature analysis (a probabilistic =
guess for the application based on its time-domain signature =
characteristics) might also be of =
utility?&#8221;</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Fernando had another =
opinion: &#8220;On the other hand,&nbsp; the selection of flows to be =
potentially TCMTFed could be something undefined at the beginning (it =
may be statically configured for example), but it is something that will =
NEED to be defined to be dynamically enforced at the mux from a higher =
entity (policy manager). That functionality would be addressed to a =
different draft in the future, re-chartering the =
WG.&#8221;</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Jose: &#8220;Perhaps a =
&quot;natural&quot; way could be widening the scope of draft (B), =
including not only delay limits, but also currently existing traffic =
classification methods which could be useful for selecting the packets =
to multiplex. Does this sound well?&#8221;</span><o:p></o:p></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Mirko: &#8220;I think =
there is no need to develop something for traffic classification in the =
scope of TCMTF WG. There is a large research community doing traffic =
classification and some of the already developed techniques can be =
applied for our need. It may be feasible to present an overview of =
techniques which could be used by TCMTF in draft =
B.&#8221;</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Luigi: &#8220;There are =
tons of classification methods out there, developing a new one does not =
look very useful to me.&#8221;</span><o:p></o:p></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Michael: &#8220;I agree =
with Luigi and Mirko ... there are more than enough people working on =
traffic flow descriptions ... and how to signal/inform networks of their =
requirements (e.g., per-hop behaviors and the like). (&#8230;) For now, =
I would recommend a placeholder in the draft that addresses the concern =
and that TCMTF SHOULD consider the traffic class of the flows when such =
information is available.&#8221;</span><o:p></o:p></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US>So perhaps the solution could be widening the scope of the =
Document (B) in order to also include:</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - TCMTF SHOULD consider the traffic class =
of the flows when such information is available</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Suggesting traffic classification =
methods which could be useful in order to do this =
</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US>What do you think? Is everyone ok with =
this?</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US>2.- Should we include it in the Charter =
now?</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>Of course, Document (B) should be included in the =
Charter.</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>Best regards,</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jose</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Jose =
Saldana, PhD</span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Communication=
s Technologies Group (GTC)<br>Dpt. Electrical Engineering and =
Communications<br>EINA, University of Zaragoza.<br></span><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>C/ Mar=EDa =
de Luna 1, Edif. Ada Byron, D. 2.05<br>50018 Zaragoza, =
Spain</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Tel: +34 976 =
76 2698</span><o:p></o:p></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Ext: =
2698</span><o:p></o:p></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>E-mail: =
</span><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><a =
href=3D"mailto:jsaldana@unizar.es"><span =
lang=3DEN-US>jsaldana@unizar.es</span></a></span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><a =
href=3D"http://diec.unizar.es/~jsaldana/personal/index.htm"><span =
lang=3DEN-US>http://diec.unizar.es/~jsaldana/personal/index.htm</span></a=
></span><o:p></o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p></div><p =
class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><span =
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><hr =
size=3D2 width=3D"100%" align=3Dcenter></span></div><p =
class=3DMsoNormal><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br=
>Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico en el enlace situado m=E1s abajo.<br>This message is =
intended exclusively for its addressee. We only send and receive email =
on the basis of the terms set out at:<br><a =
href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/E=
S/PAGINAS/disclaimer.aspx</a></span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p></div></div></body></html>
------=_NextPart_000_003C_01CDF3DA.BBD9DDD0--


From jsaldana@unizar.es  Wed Jan 16 02:18:50 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 780D421F8686 for <tcmtf@ietfa.amsl.com>; Wed, 16 Jan 2013 02:18:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.572
X-Spam-Level: 
X-Spam-Status: No, score=-6.572 tagged_above=-999 required=5 tests=[AWL=0.026,  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 4T+Qrwe4MZ4l for <tcmtf@ietfa.amsl.com>; Wed, 16 Jan 2013 02:18:47 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 6242521F8692 for <tcmtf@ietf.org>; Wed, 16 Jan 2013 02:18:46 -0800 (PST)
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 r0GAId44030981; Wed, 16 Jan 2013 11:18:39 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "Muthu Arul Mozhi Perumal \(mperumal\)" <mperumal@cisco.com>, "Fernando Pascual Blanco" <fpb@tid.es>
Date: Wed, 16 Jan 2013 11:18:43 +0100
Organization: Universidad de Zaragoza
Message-ID: <004601cdf3d2$dd332250$979966f0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0047_01CDF3DB.3EF78A50"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3z0qpuai7heI7oSHWY0AJDN9gmvg==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a de-muxer
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, 16 Jan 2013 10:18:50 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0047_01CDF3DB.3EF78A50
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Fernando, Muthu, everyone,

=20

Since there is no consensus about this, I think we should carry on with =
the
debate. Do you think the mechanism would be very complicated? Any new
ideas?:

=20

- *dynamically establishing, modifying and releasing tunnels*

=20

#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.

=20

There is still no consensus here:

=20

Fernando: =93Regarding #1, to be honest, I am not completely sure of the =
need
to specify a mechanism to discover muxes and demuxes between them. I =
think
those kind of mechanisms have more sense in local environments but I=B4m =
not
sure if it applies here. At least at the beginning this associations can =
be
done manually.=94

=20

Muthu: =93I think it is the opposite -- in local environments you can
provision/associate them manually. However, in a multi-vendor =
environment
over the Internet this should happen automatically.=94=20

=93#1 needs to be specified.=94

=20

=20

Best regards,


Jose

=20

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de =
Jose
Saldana
Enviado el: martes, 15 de enero de 2013 11:56
Para: tcmtf@ietf.org
Asunto: [tcmtf] TCMTF: Document A discussion: content and charter

=20

Document (A) refers to the main TCMTF draft, currently in
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

=20

1.- Content of the Document

=20

Currently it contains the description of the question and the protocols
which could be used on each layer (tunneling, compressing, =
multiplexing). It
says that the signaling issues would be that of each protocol.

=20

There is consensus (I think) about this: we should include some =
signaling
issues. The question is: What should we include in Draft A and what in =
Draft
C?

=20

- *Auto-negotiation* Negotiation mechanisms to decide the options at =
each
layer (compression, multiplexing and tunneling) between mux and demux.
Perhaps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP =
and
IPHC, so the two machines will have to negotiate in order to decide =
which
compression protocol use.

=20

This should be included in (A). I think there is consensus about this:

Juan Antonio: =93The first kind of signaling ("auto-negotiation") is =
needed
from the beginning if we don't want an extremely static protocol and
therefore possibly difficult to get it working, especially when in most =
of
cases the peers belong to different entities/companies.=94

=20

Dan: =93We need that -- it is capabilities negotiation.  It is needed =
because
the protocol will fail if one side mistakenly thinks the other side has
certain functionality, and because we will want to add some fancy new
compression in the year 2020 and will need to negotiate it.=94

=20

Fernando: =93I also agree with the idea of including the mux-demux =
signaling
within the draft A (as Dan said, they are capabilities negotiation). =
This
draft should be able to get two boxes with TCMTF fully working between =
them.
Under my point of view this includes the definition of the capabilities =
in
each node and the negotiation of that capabilities.=94

=20

Does this mean that Document (A) will no longer be a Best Current =
Practice?
I think so.

=20

=20

- *dynamically establishing, modifying and releasing tunnels*

=20

#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.

=20

There is still no consensus here:

=20

Fernando: =93Regarding #1, to be honest, I am not completely sure of the =
need
to specify a mechanism to discover muxes and demuxes between them. I =
think
those kind of mechanisms have more sense in local environments but I=B4m =
not
sure if it applies here. At least at the beginning this associations can =
be
done manually.=94

=20

Muthu: =93I think it is the opposite -- in local environments you can
provision/associate them manually. However, in a multi-vendor =
environment
over the Internet this should happen automatically.=94=20

=93#1 needs to be specified.=94

=20

=20

=20

#2. A mechanism to *elect an optimal muxer and a de-muxer when there are
more than one muxer/de-muxer for a flow*.

=20

We agree: This can wait for Document (C).

=20

                Fernando: =93#2 is more related to the higher entity =
that has
to decide whether a flow should be TCMTFed or not, and under my point of
view it can be addressed in a different draft.=94

                Muthu: =93#2 can be added later.=94

=20

=20

3. A mechanism to *setup/release a tunnel b/w a muxer and a de-muxer*.

=20

We agree: This has to be included in (A).

=20

                Fernando =93#3 I think should be included in the draft =
A,
since it is a mechanism within the TFMTF protocol itself.=94

                Muthu: =93#3 many not require much specification.=94

=20

=20

=20

2.- Should we include it in the Charter now?

=20

Of course, Document (A) should be in the charter.

=20

=20

Best regards,

=20

Jose

=20


------=_NextPart_000_0047_01CDF3DB.3EF78A50
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:"Calibri","sans-serif";}
span.EstiloCorreo19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span =
lang=3DEN-US>Fernando, Muthu, everyone,<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>Since there is no consensus =
about this, I think we should carry on with the debate. Do you think the =
mechanism would be very complicated? Any new =
ideas?:<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>dynamically establishing, modifying and releasing =
tunnels</b>*<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. A *<b>mechanism for a muxer to discover a de-muxer (and =
vice versa)</b>*.<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 is still no consensus here:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.4pt'><span =
lang=3DEN-US>Fernando: &#8220;Regarding #1, to be honest, I am not =
completely sure of the need to specify a mechanism to discover muxes and =
demuxes between them. I think those kind of mechanisms have more sense =
in local environments but I=B4m not sure if it applies here. At least at =
the beginning this associations can be done =
manually.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.4pt'><span lang=3DEN-US>Muthu: &#8220;I think it =
is the opposite -- in local environments you can provision/associate =
them manually. However, in a multi-vendor environment over the Internet =
this should happen automatically.&#8221; <o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:35.4pt;text-indent:35.4pt'><span =
lang=3DEN-US>&#8220;#1 needs to be =
specified.&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Best =
regards,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><br>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'>De:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'> tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] =
<b>En nombre de </b>Jose Saldana<br><b>Enviado el:</b> martes, 15 de =
enero de 2013 11:56<br><b>Para:</b> tcmtf@ietf.org<br><b>Asunto:</b> =
[tcmtf] TCMTF: Document A discussion: content and =
charter<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>Document (A) refers to the main TCMTF draft, currently in =
<a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http:=
//datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></spa=
n></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>1.- Content of the Document<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Currently it contains the =
description of the question and the protocols which could be used on =
each layer (tunneling, compressing, multiplexing). It says that the =
signaling issues would be that of each protocol.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>There is consensus (I think) about =
this: we should include some signaling issues. The question is: What =
should we include in Draft A and what in Draft =
C?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- *<b>Auto-negotiation</b>* Negotiation mechanisms to =
decide the options at each layer (compression, multiplexing and =
tunneling) between mux and demux. Perhaps the mux has ROHC, ECRTP and =
IPHC, and the demux only has ECRTP and IPHC, so the two machines will =
have to negotiate in order to decide which compression protocol =
use.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This should be included in (A). I think there is consensus =
about this:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:35.4pt'><span lang=3DEN-US>Juan Antonio: &#8220;The =
first kind of signaling (&quot;auto-negotiation&quot;) is needed from =
the beginning if we don't want an extremely static protocol and =
therefore possibly difficult to get it working, especially when in most =
of cases the peers belong to different =
entities/companies.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US>Dan: &#8220;We need that -- it is capabilities =
negotiation.&nbsp; It is needed because the protocol will fail if one =
side mistakenly thinks the other side has certain functionality, and =
because we will want to add some fancy new compression in the year 2020 =
and will need to negotiate it.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Fernando: &#8220;I also =
agree with the idea of including the mux-demux signaling within the =
draft A (as Dan said, they are capabilities negotiation). This draft =
should be able to get two boxes with TCMTF fully working between them. =
Under my point of view this includes the definition of the capabilities =
in each node and the negotiation of that =
capabilities.&#8221;<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>Does this mean that Document (A) will no longer be a Best =
Current Practice? I think so.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>- *<b>dynamically establishing, =
modifying and releasing tunnels</b>*<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. A *<b>mechanism for a muxer =
to discover a de-muxer (and vice versa)</b>*.<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 is still no consensus =
here:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.4pt'><span lang=3DEN-US>Fernando: =
&#8220;Regarding #1, to be honest, I am not completely sure of the need =
to specify a mechanism to discover muxes and demuxes between them. I =
think those kind of mechanisms have more sense in local environments but =
I=B4m not sure if it applies here. At least at the beginning this =
associations can be done manually.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.4pt'><span =
lang=3DEN-US>Muthu: &#8220;I think it is the opposite -- in local =
environments you can provision/associate them manually. However, in a =
multi-vendor environment over the Internet this should happen =
automatically.&#8221; <o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.4pt;text-indent:35.4pt'><span =
lang=3DEN-US>&#8220;#1 needs to be =
specified.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>#2. A mechanism to *<b>elect an optimal muxer and a =
de-muxer when there are more than one muxer/de-muxer for a =
flow</b>*.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>We agree: This can wait for Document =
(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>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fernando: &#8220;#2 is more related to =
the higher entity that has to decide whether a flow should be TCMTFed or =
not, and under my point of view it can be addressed in a different =
draft.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu: &#8220;#2 can be added =
later.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>3. A mechanism to *<b>setup/release a tunnel b/w a muxer =
and a de-muxer</b>*.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>We agree: This has to be included in =
(A).<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>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fernando &#8220;#3 I think should be =
included in the draft A, since it is a mechanism within the TFMTF =
protocol itself.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu: &#8220;#3 many not require much =
specification.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>2.- Should we include it in the Charter =
now?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Of course, Document (A) should be in the =
charter.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Best regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_0047_01CDF3DB.3EF78A50--


From fpb@tid.es  Wed Jan 16 02:46:17 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE17521F86E7 for <tcmtf@ietfa.amsl.com>; Wed, 16 Jan 2013 02:46:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.237
X-Spam-Level: 
X-Spam-Status: No, score=-6.237 tagged_above=-999 required=5 tests=[AWL=0.061,  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 RQED4eRTsbf2 for <tcmtf@ietfa.amsl.com>; Wed, 16 Jan 2013 02:46:15 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id DD78521F873C for <tcmtf@ietf.org>; Wed, 16 Jan 2013 02:46:06 -0800 (PST)
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 <0MGP00JU3SKTMJ@tid.hi.inet> for tcmtf@ietf.org; Wed, 16 Jan 2013 11:46:05 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 34.A6.03184.DE486F05; Wed, 16 Jan 2013 11:46:05 +0100 (CET)
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 <0MGP00JTXSKSMJ@tid.hi.inet> for tcmtf@ietf.org; Wed, 16 Jan 2013 11:46:05 +0100 (MET)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.151]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.004; Wed, 16 Jan 2013 11:42:58 +0100
Date: Wed, 16 Jan 2013 10:46:02 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <003b01cdf3d2$5a1304d0$0e390e70$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "'Michael Ramalho (mramalho)'" <mramalho@cisco.com>, =?Windows-1252?Q?MANUEL_NU=D1EZ_SANZ?= <mns@tid.es>
Message-id: <F5EDC35DF914C1428C28E149F10463A26504370A@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_wMF8fGqOb4Z2M+eeRlbSCw)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] TCMTF: Document B discussion: content and charter
Thread-index: Ac3zAd2uYPABnQrZRziFoMS7yxCKNwAEJgsAAA5lTzAAH3tAAAADLZsA
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4068-b7fc06d000000c70-5a-50f684ed39e4
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNKsWRmVeSWpSXmKPExsXCFe/Apfu25VuAwat1XBa7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxtWfv9kLlm1jqpi6rZ2tgfFbD1MXIweHhICJxPaH+l2MnECm mMSFe+vZuhi5OIQENjBK7O9oYgFJCAn8YJToeK8DkdjEKNGycRozSIJFQFVi5dNFTCA2m4CW xOm7q8AahAXcJNbu6GYGWcApYCHRvN0WYoGCxJ9zj1lA5ogIzGaUuPPsJFgNM9Cced8UQWp4 Bbwl7l/exwphC0r8mHwPbCSzQK7EmqVNTBC2uERz602wOKOArMS7+fPB6kUE3CVu777EAmG7 STxv+AYWFxXQk2g7doYd4gYBiSV7zjND2KISLx//Y53AKDYLybpZSNbNQrIOwjaQeH9uPjOE rS2xbOFrKFtfYuOXs4wQtpnE08mHUNQsYORYxShWnFSUmZ5RkpuYmZNuYKiXkamXmZdasokR Eo8ZOxiX71Q5xCjAwajEw3vg7OcAIdbEsuLK3EOMkhxMSqK8jMBoFuJLyk+pzEgszogvKs1J LT7EKMHBrCTCu8weKMebklhZlVqUD5OS4eBQkuAVB2kTLEpNT61Iy8wBJh2YNBMHJ0g7D1A7 L0gNb3FBYm5xZjpE/hSjNkfLge7njBwzJvY8ZxRiycvPS5US5xUFKRUAKc0ozYOb9opRHOhs YV41kCwPMIXCzXkFtIIJaMWmvZ9BVpQkIqSkGhh1zx79/CmYhau9/ceNtt99evufbffQPfYk /cknD/X3u2fMuxF7z0vcJu30tf8FWbyuHHlF/951+i6PqGatbPV2Xsg72zUyb+FE470Xbq2u XLrEfNH8l54Le+KOTAut++toetqzcduSRtH0AuNLf5Z/XTbLZsOEqQYvHt78/WHhmg0mSpc1 PjSbKbEUZyQaajEXFScCAJ8isv1eAwAA
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] TCMTF: Document B discussion: content and charter
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, 16 Jan 2013 10:46:17 -0000

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

Hi Jose,

I think it should be enough. The paragraph address the added delay issue y =
proposes recommendations on how to deal with it. In addition, the sentence =
"available traffic classification methods" is wide enough to let us propose=
 very different suggestions about traffic classification.

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: mi=E9rcoles, 16 de enero de 2013 11:15
To: "'Michael Ramalho (mramalho) '" <mramalho@cisco.com<mailto:mramalho@cis=
co.com>>, "mns@tid.es<mailto:mns@tid.es>" <mns@tid.es<mailto:mns@tid.es>>, =
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: Document B discussion: content and charter

Hi all,

I think we agree on this (if not, please report it):

#1 Document B has to be in the Charter
#2 Document B has to specify maximum delays for different services
#3 Document B has to include some recommendations about the use of traffic =
classification methods


So the question is now related to #3:

How to include that recommendations about traffic classification methods: p=
utting a SHOULD or not, etc.


But my question:

Do we need to decide this now? Is this decision necessary in order to write=
 the Charter? Perhaps it is not, and we can go ahead with it. My proposal f=
or the paragraph about Document (B) in the Charter:

6. 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 Wo=
rking Group will also develop a document (B) with recommendations which can=
 be useful in order to decide which packet flows can or can not be multiple=
xed: recommendations about the use of available traffic classification meth=
ods; the maximum delay and jitter to be added to each kind of service or ap=
plication; other recommendations can be included if necessary. Empirical re=
search studies with real users will be necessary in order to establish this=
 set of recommendations.

What do you think? Do you like this paragraph for the Charter? Improvement =
suggestions will be welcome.

Best reards,

Jose

De: Michael Ramalho (mramalho) [mailto:mramalho@cisco.com]
Enviado el: martes, 15 de enero de 2013 19:39
Para: MANUEL NU=D1EZ SANZ; jsaldana@unizar.es<mailto:jsaldana@unizar.es>; t=
cmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: RE: [tcmtf] TCMTF: Document B discussion: content and charter

All,

My comments are in-line below (with =93MAR:=93).

Michael Ramalho

From:tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-bo=
unces@ietf.org] On Behalf Of MANUEL NU=D1EZ SANZ
Sent: Tuesday, January 15, 2013 7:16 AM
To: jsaldana@unizar.es<mailto:jsaldana@unizar.es>; tcmtf@ietf.org<mailto:tc=
mtf@ietf.org>
Subject: Re: [tcmtf] TCMTF: Document B discussion: content and charter

Hi,
  I am going to do one=B4s bit.

It is true there are tons of classification methods, however the issue is t=
hat:

1.       It is not common its use, and therefore it is reasonable to suppos=
e a lot of packets/flows will not be classified.



MAR: True. But, given the move to the =93Internet of [Things|Everything]=94=
 as I mentioned previously, the industry will soon send some type of =93tra=
ffic class indication=94 to the network to help the network optimize itself=
. Until that day occurs, if you know: 1) NOTHING about the flow, AND 2) but=
 believe it may be a =93real-time flow=94 AND 3) to TCMTF a packet from tha=
t flow would add more than a few milliseconds of delay =85 you probably sho=
uld not TCMTF it.



MAR: =93Real-time=94 is defined here as a packet relating to some human res=
ponse time type of application (e.g., remote desktop virtualization sent ov=
er TCP might be considered =93real-time=94).



2.       And even when a flow is classified, it is possible than that class=
ification does not identify the delays for that flow.



MAR: Most real-time traffic classifiers DO NOT specify a hard limit on the =
=93per-hop=94 added delay. But would you delay a TCP flow that said it was =
a =93Voice packet=94 by 1000 milliseconds by TCMTFing it? Before you think =
that wouldn=92t ever  happen, there a lot of real time packets sent over TC=
P to get through firewals after all attempts to send such a packet over UDP=
 fails. As an aside, signature analysis could help in these cases.



MAR: Note that most of my concern is moot when TCMTF is operating on high r=
ate output links =96 as most compressions will result in TCMTF delays of le=
ss than a few milliseconds.


Therefore under my opinion (quite similar to Fernando) is that it is necess=
ary the MUX =93obtain=94 the configuration to know than flow are TCMTFed. I=
n that line, there are three different approaches:

1.       A static configuration (as an initial state)

2.       A policy manager dynamically enforces the option for each new flow

3.       The MUX asks for instruction for each =93new=94 flow to an =93poli=
cy manager=94 or =93controller=94. This last options is fully compatible wi=
th the 2 option.



MAR: A =93good TCMTF tunneling function=94 should make an intelligent decis=
ion regarding what flows it thinks is acceptable to TCMTF and which it shou=
ld not. We need to allow room for products to differentiate themselves. Thu=
s, I think we ought to provide some guidance without being overly prescript=
ive. I think we should error on the side of acknowledging the issue and pro=
viding guidance to implementers via a =93SHOULD strength=94 requirement in =
the draft.

And answering the question about open the scope of document B. I agree.

Regards,
  Manuel N=FA=F1ez

[MAR: Does anyone know how I tell MSFT Outlook that I don=92t want to reply=
 in Spanish =85 it keeps =93correcting=94 my American English reply with in=
correct Spanish words!]

De:tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-boun=
ces@ietf.org] En nombre de Jose Saldana
Enviado el: martes, 15 de enero de 2013 11:56
Para: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: [tcmtf] TCMTF: Document B discussion: content and charter

Document (B) refers to the informational draft about maximum tolerable dela=
ys, currently in http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-=
tcmtf/

1.- Content of the Document

Currently, the Document specifies the maximum added delays for different se=
rvices.

However, the discussion has set clear that other things should be added, ma=
inly methods for identifying the flows:


Michael: =93has any detailed thought about how TCMTF might identify which f=
lows it should NOT attempt to compress?

Considering "the Internet of things" (where virtually every device is conne=
cted via IP) ... we can expect a lot of small packets ... but not necessari=
ly know if we should compress them or not (e.g., FPS packets) ... or what t=
he delay bounds on the compression should be.
Should we mention that flows that signal their own traffic class (e.g., usi=
ng "Metadata" describing the flow) is a good thing to differentiate on? Sho=
uld we suggest signature analysis (a probabilistic guess for the applicatio=
n based on its time-domain signature characteristics) might also be of util=
ity?=94

Fernando had another opinion: =93On the other hand,  the selection of flows=
 to be potentially TCMTFed could be something undefined at the beginning (i=
t may be statically configured for example), but it is something that will =
NEED to be defined to be dynamically enforced at the mux from a higher enti=
ty (policy manager). That functionality would be addressed to a different d=
raft in the future, re-chartering the WG.=94


Jose: =93Perhaps a "natural" way could be widening the scope of draft (B), =
including not only delay limits, but also currently existing traffic classi=
fication methods which could be useful for selecting the packets to multipl=
ex. Does this sound well?=94



Mirko: =93I think there is no need to develop something for traffic classif=
ication in the scope of TCMTF WG. There is a large research community doing=
 traffic classification and some of the already developed techniques can be=
 applied for our need. It may be feasible to present an overview of techniq=
ues which could be used by TCMTF in draft B.=94



Luigi: =93There are tons of classification methods out there, developing a =
new one does not look very useful to me.=94



Michael: =93I agree with Luigi and Mirko ... there are more than enough peo=
ple working on traffic flow descriptions ... and how to signal/inform netwo=
rks of their requirements (e.g., per-hop behaviors and the like). (=85) For=
 now, I would recommend a placeholder in the draft that addresses the conce=
rn and that TCMTF SHOULD consider the traffic class of the flows when such =
information is available.=94



So perhaps the solution could be widening the scope of the Document (B) in =
order to also include:

                - TCMTF SHOULD consider the traffic class of the flows when=
 such information is available

                - Suggesting traffic classification methods which could be =
useful in order to do this



What do you think? Is everyone ok with this?






2.- Should we include it in the Charter now?

Of course, Document (B) should be included in the Charter.


Best regards,

Jose


Jose Saldana, PhD
Communications Technologies Group (GTC)
Dpt. Electrical Engineering and Communications
EINA, University of Zaragoza.
C/ Mar=EDa de Luna 1, Edif. Ada Byron, D. 2.05
50018 Zaragoza, Spain
Tel: +34 976 76 2698
Ext: 2698
E-mail: jsaldana@unizar.es<mailto:jsaldana@unizar.es>
http://diec.unizar.es/~jsaldana/personal/index.htm


________________________________

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_wMF8fGqOb4Z2M+eeRlbSCw)
Content-id: <243B18968D67324386BC1D1B362C513E@hi.inet>
Content-type: text/html; charset=Windows-1252
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font=
-family:Calibri,sans-serif">
<div>
<div>
<div>Hi Jose,</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>I thin=
k it should be enough. The paragraph address the added delay issue y propos=
es recommendations on how to deal with it. In addition, the sentence &quot;=
available traffic classification methods&quot;
 is wide enough to let us propose very different suggestions about traffic =
classification.</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>mi=E9rcoles, 16 de enero de 2=
013 11:15<br>
<span style=3D"font-weight:bold">To: </span>&quot;'Michael Ramalho (mramalh=
o) '&quot; &lt;<a href=3D"mailto:mramalho@cisco.com">mramalho@cisco.com</a>=
&gt;, &quot;<a href=3D"mailto:mns@tid.es">mns@tid.es</a>&quot; &lt;<a href=
=3D"mailto:mns@tid.es">mns@tid.es</a>&gt;, Fernando Pascual Blanco &lt;<a h=
ref=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: Documen=
t B discussion: content and charter<br>
</div>
<div><br>
</div>
<div><style>
<!--
@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.TextosinformatoCar
	{font-family:Consolas}
span.TextodegloboCar
	{font-family:"Tahoma","sans-serif"}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{margin-right:0cm;
	margin-left:0cm;
	font-size:10.0pt;
	font-family:"Times New Roman","serif"}
p.PlainText, li.PlainText, div.PlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
span.PlainTextChar
	{font-family:Consolas}
span.textosinformatocar0
	{font-family:"Calibri","sans-serif"}
span.estilocorreo19
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.estilocorreo20
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
span.EstiloCorreo28
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
p.BalloonText, li.BalloonText, div.BalloonText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
span.BalloonTextChar
	{font-family:"Tahoma","sans-serif"}
span.EstiloCorreo31
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:72.0pt 72.0pt 72.0pt 72.0pt}
div.WordSection1
	{}
-->
</style>
<div lang=3D"ES">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi all,=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I think=
 we agree on this (if not, please report it):</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 Docu=
ment B has to be in the Charter</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">#2 Docu=
ment B has to specify maximum delays for different services</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">#3 Docu=
ment B has to include some recommendations about the use of traffic classif=
ication methods</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 the =
question is now related to #3:</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">How to =
include that recommendations about traffic classification methods: putting =
a SHOULD or not, etc.</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">But my =
question:</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">Do we n=
eed to decide this now? Is this decision necessary in order to write the Ch=
arter? Perhaps it is not, and we can go ahead with it. My proposal for the =
paragraph about Document (B) in the Charter:
</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">6. 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 wh=
ich can be useful in order to decide which packet flows can or can not be m=
ultiplexed: recommendations about the use of available traffic classificati=
on methods; the maximum delay and
 jitter to be added to each kind of service or application; other recommend=
ations can be included if necessary. Empirical research studies with real u=
sers will be necessary in order to establish this set of recommendations.</=
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">What do=
 you think? Do you like this paragraph for the Charter? Improvement suggest=
ions will be welcome.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Best re=
ards,</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>
<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"> Michael Ramalho (mramalho) [<a=
 href=3D"mailto:mramalho@cisco.com">mailto:mramalho@cisco.com</a>]
<br>
<b>Env</b></span><b><span style=3D"font-size:10pt; font-family:Tahoma,sans-=
serif">iado el:</span></b><span style=3D"font-size:10pt; font-family:Tahoma=
,sans-serif"> martes, 15 de enero de 2013 19:39<br>
<b>Para:</b> MANUEL NU=D1EZ SANZ; <a href=3D"mailto:jsaldana@unizar.es">jsa=
ldana@unizar.es</a>;
<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> RE: [tcmtf] TCMTF: Document B discussion: content and charte=
r</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">All,</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">My comm=
ents are in-line below (with =93MAR:=93).</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">Michael=
 Ramalho</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0c=
m 0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10pt; fon=
t-family:Tahoma,sans-serif">From:</span></b><span lang=3D"EN-US" style=3D"f=
ont-size:10pt; font-family:Tahoma,sans-serif"><a href=3D"mailto:tcmtf-bounc=
es@ietf.org">tcmtf-bounces@ietf.org</a> [<a href=3D"mailto:tcmtf-bounces@ie=
tf.org">mailto:tcmtf-bounces@ietf.org</a>]
<b>On Behalf Of </b>MANUEL NU=D1EZ SANZ<br>
<b>Sent:</b> Tuesday, January 15, 2013 7:16 AM<br>
<b>To:</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>Subject:</b> Re: [tcmtf] TCMTF: Document B discussion: content and chart=
er</span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi, </s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;I am going to do one=B4s bit.
</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">It is t=
rue there are tons of classification methods, however the issue is that:</s=
pan></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt"><span lang=3D"E=
N-US" style=3D"color:#1F497D">1.</span><span lang=3D"EN-US" style=3D"font-s=
ize:7pt; font-family:'Times New Roman',serif; color:rgb(31,73,125)">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span lang=3D"EN-US" style=3D"color:#1F497D">It is not common its us=
e, and therefore it is reasonable to suppose a lot of packets/flows will no=
t be classified.</span><span lang=3D"EN-US"></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt"><span lang=3D"E=
N-US" style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0cm"><span lang=3D"EN-US=
" style=3D"color:#1F497D">MAR: True. But, given the move to the =93Internet=
 of [Things|Everything]=94 as I mentioned previously, the industry will soo=
n send some type of =93traffic class indication=94
 to the network to help the network optimize itself. Until that day occurs,=
 if you know: 1) NOTHING about the flow, AND 2) but believe it may be a =93=
real-time flow=94 AND 3) to TCMTF a packet from that flow would add more th=
an a few milliseconds of delay =85 you
 probably should not TCMTF it.</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0cm"><span lang=3D"EN-US=
" style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0cm"><span lang=3D"EN-US=
" style=3D"color:#1F497D">MAR: =93Real-time=94 is defined here as a packet =
relating to some human response time type of application (e.g., remote desk=
top virtualization sent over TCP might be considered
 =93real-time=94).</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0cm"><span style=3D"colo=
r:#1F497D">&nbsp;</span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt"><span lang=3D"E=
N-US" style=3D"color:#1F497D">2.</span><span lang=3D"EN-US" style=3D"font-s=
ize:7pt; font-family:'Times New Roman',serif; color:rgb(31,73,125)">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span lang=3D"EN-US" style=3D"color:#1F497D">And even when a flow is=
 classified, it is possible than that classification does not identify the =
delays for that flow.</span><span lang=3D"EN-US"></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0cm"><span style=3D"colo=
r:#1F497D">&nbsp;</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0cm"><span style=3D"colo=
r:#1F497D">MAR: Most real-time traffic classifiers DO NOT specify a hard li=
mit on the =93per-hop=94 added delay. But would you delay a TCP flow that s=
aid it was a =93Voice packet=94 by 1000 milliseconds
 by TCMTFing it? Before you think that wouldn=92t ever &nbsp;happen, there =
a lot of real time packets sent over TCP to get through firewals after all =
attempts to send such a packet over UDP fails. As an aside, signature analy=
sis could help in these cases.</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0cm"><span style=3D"colo=
r:#1F497D">&nbsp;</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0cm"><span style=3D"colo=
r:#1F497D">MAR: Note that most of my concern is moot when TCMTF is operatin=
g on high rate output links =96 as most compressions will result in TCMTF d=
elays of less than a few milliseconds.</span></p>
<p class=3D"MsoListParagraph"><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">Therefo=
re under my opinion (quite similar to Fernando) is that it is necessary the=
 MUX =93obtain=94 the configuration to know than flow are TCMTFed. In that =
line, there are three different approaches:</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:38.25pt; text-indent:-18=
.0pt"><span lang=3D"EN-US" style=3D"color:#1F497D">1.</span><span lang=3D"E=
N-US" style=3D"font-size:7pt; font-family:'Times New Roman',serif; color:rg=
b(31,73,125)">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span lang=3D"EN-US" style=3D"color:#1F497D">A static configuration =
(as an initial state)</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:38.25pt; text-indent:-18=
.0pt"><span lang=3D"EN-US" style=3D"color:#1F497D">2.</span><span lang=3D"E=
N-US" style=3D"font-size:7pt; font-family:'Times New Roman',serif; color:rg=
b(31,73,125)">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span lang=3D"EN-US" style=3D"color:#1F497D">A policy manager dynami=
cally enforces the option for each new flow</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:38.25pt; text-indent:-18=
.0pt"><span lang=3D"EN-US" style=3D"color:#1F497D">3.</span><span lang=3D"E=
N-US" style=3D"font-size:7pt; font-family:'Times New Roman',serif; color:rg=
b(31,73,125)">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><span lang=3D"EN-US" style=3D"color:#1F497D">The MUX asks for instru=
ction for each =93new=94 flow to an =93policy manager=94 or =93controller=
=94. This last options is fully compatible with the 2 option.</span><span l=
ang=3D"EN-US"></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0cm"><span style=3D"colo=
r:#1F497D">&nbsp;</span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0cm"><span style=3D"colo=
r:#1F497D">MAR: A =93good TCMTF tunneling function=94 should make an intell=
igent decision regarding what flows it thinks is acceptable to TCMTF and wh=
ich it should not. We need to allow room for
 products to differentiate themselves. Thus, I think we ought to provide so=
me guidance without being overly prescriptive. I think we should error on t=
he side of acknowledging the issue and providing guidance to implementers v=
ia a =93SHOULD strength=94 requirement
 in the draft.</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">And ans=
wering the question about open the scope of document B. I agree.
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regards=
, </span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;&=
nbsp;Manuel N=FA=F1ez</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">[MAR: D=
oes anyone know how I tell MSFT Outlook that I don=92t want to reply in Spa=
nish =85 it keeps =93correcting=94 my American English reply with incorrect=
 Spanish words!]&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0c=
m 0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10pt; font-family:Tahoma=
,sans-serif">De:</span></b><span style=3D"font-size:10pt; font-family:Tahom=
a,sans-serif"><a href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.=
org</a> [<a href=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@iet=
f.org</a>]
<b>En nombre de </b>Jose Saldana<br>
<b>Enviado el:</b> martes, 15 de enero de 2013 11:56<br>
<b>Para:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tcmtf] TCMTF: Document B discussion: content and charter</s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Document (B) refers to the info=
rmational draft about maximum tolerable delays, currently in
<a href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/=
">http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">1.- Content of the Document</sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Currently, the Document specifi=
es the maximum added delays for different services.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">However, the discussion has set=
 clear that other things should be added, mainly methods for identifying th=
e flows:</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"text-indent:35.4pt"><span lang=3D"EN-US"=
>Michael: =93has any detailed thought about how TCMTF might identify which =
flows it should NOT attempt to compress?</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span lang=3D"EN-US"=
>Considering &quot;the Internet of things&quot; (where virtually every devi=
ce is connected via IP) ... we can expect a lot of small packets ... but no=
t necessarily know if we should compress them or
 not (e.g., FPS packets) ... or what the delay bounds on the compression sh=
ould be.</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lang=3D"EN-US">Sh=
ould we mention that flows that signal their own traffic class (e.g., using=
 &quot;Metadata&quot; describing the flow) is a good thing to differentiate=
 on? Should we suggest signature analysis (a probabilistic
 guess for the application based on its time-domain signature characteristi=
cs) might also be of utility?=94</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.25pt"><span lang=3D"EN-US">F=
ernando had another opinion: =93On the other hand,&nbsp; the selection of f=
lows to be potentially TCMTFed could be something undefined at the beginnin=
g (it may be statically configured for example),
 but it is something that will NEED to be defined to be dynamically enforce=
d at the mux from a higher entity (policy manager). That functionality woul=
d be addressed to a different draft in the future, re-chartering the WG.=94=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Jose: =93Perhaps a &quot;natural&quot; way could be widening the scope of=
 draft (B), including not only delay limits, but also currently existing tr=
affic classification methods which could be useful
 for selecting the packets to multiplex. Does this sound well?=94</span></p=
>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Mirko: =93I think there is no need to develop something for traffic class=
ification in the scope of TCMTF WG. There is a large research community doi=
ng traffic classification and some of the
 already developed techniques can be applied for our need. It may be feasib=
le to present an overview of techniques which could be used by TCMTF in dra=
ft B.=94</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Luigi: =93There are tons of classification methods out there, developing =
a new one does not look very useful to me.=94</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Michael: =93I agree with Luigi and Mirko ... there are more than enough p=
eople working on traffic flow descriptions ... and how to signal/inform net=
works of their requirements (e.g., per-hop
 behaviors and the like). (=85) For now, I would recommend a placeholder in=
 the draft that addresses the concern and that TCMTF SHOULD consider the tr=
affic class of the flows when such information is available.=94</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">So perhaps the solution coul=
d be widening the scope of the Document (B) in order to also include:</span=
></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - TCMTF SHOU=
LD consider the traffic class of the flows when such information is availab=
le</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Suggesting=
 traffic classification methods which could be useful in order to do this
</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">What do you think? Is everyo=
ne ok with this?</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">2.- Should we include it in =
the Charter now?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Of course, Document (B) should =
be included in the Charter.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Best regards,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jose</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt; font-f=
amily:Arial,sans-serif">Jose Saldana, PhD</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt; font-f=
amily:Arial,sans-serif">Communications Technologies Group (GTC)<br>
Dpt. Electrical Engineering and Communications<br>
EINA, University of Zaragoza.<br>
</span><span style=3D"font-size:10pt; font-family:Arial,sans-serif">C/ Mar=
=EDa de Luna 1, Edif. Ada Byron, D. 2.05<br>
50018 Zaragoza, Spain</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:Arial,san=
s-serif">Tel: &#43;34 976 76 2698</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt; font-f=
amily:Arial,sans-serif">Ext: 2698</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt; font-f=
amily:Arial,sans-serif">E-mail:
</span><span style=3D"font-size:10.0pt; font-family:&quot;Arial&quot;,&quot=
;sans-serif&quot;"><a href=3D"mailto:jsaldana@unizar.es"><span lang=3D"EN-U=
S">jsaldana@unizar.es</span></a></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;A=
rial&quot;,&quot;sans-serif&quot;"><a href=3D"http://diec.unizar.es/~jsalda=
na/personal/index.htm"><span lang=3D"EN-US">http://diec.unizar.es/~jsaldana=
/personal/index.htm</span></a></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt; font-family:'Times Ne=
w Roman',serif">&nbsp;</span></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-size:12pt; font-family:'Times New Roman',serif">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt; font-family:Arial,sa=
ns-serif; color:gray"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span style=3D"font-size:12pt; font-fa=
mily:'Times New Roman',serif"></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_wMF8fGqOb4Z2M+eeRlbSCw)--

From jsaldana@unizar.es  Wed Jan 16 02:57:21 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9054221F8684 for <tcmtf@ietfa.amsl.com>; Wed, 16 Jan 2013 02:57:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.424
X-Spam-Level: 
X-Spam-Status: No, score=-6.424 tagged_above=-999 required=5 tests=[AWL=-0.125, 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 BZI8mV2GYe4J for <tcmtf@ietfa.amsl.com>; Wed, 16 Jan 2013 02:57:20 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id AF78221F865B for <tcmtf@ietf.org>; Wed, 16 Jan 2013 02:57:19 -0800 (PST)
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 r0GAvBRJ031887; Wed, 16 Jan 2013 11:57:11 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>, "'Dan Wing'" <dwing@cisco.com>,  "=?utf-8?Q?'Mirko_Su=C5=BEnjevi=C4=87'?=" <Mirko.Suznjevic@fer.hr>, "=?utf-8?Q?'Juli=C3=A1n_Fern=C3=A1ndez_Navajas'?=" <navajas@unizar.es>
References: <004c01cddc49$3e7264a0$bb572de0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A265041D90@EX10-MB1-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A265041D90@EX10-MB1-MAD.hi.inet>
Date: Wed, 16 Jan 2013 11:57:16 +0100
Organization: Universidad de Zaragoza
Message-ID: <007401cdf3d8$3f988ca0$bec9a5e0$@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: AQNP+67aoMURUNLh5RkXm1Hlki/L5JVHtnjg
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
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, 16 Jan 2013 10:57:21 -0000

My two cents:

In games and in VoIP the really important thing is RTT:

- Games always measure the RTT (gamers talk about the "ping"): the =
important thing is the delay from a player action to the server reaction =
arriving to the player's machine.
- In VoIP I think it is the same: what matters is the RTT, in order to =
grant interactivity and avoiding cross-talk.

In addition, RTT is easier to measure than OWD, since you don't need =
synchronization.

And regarding Two-way TCMTF, I think we have to think about TCMTF as =
one-way. Otherwise, things would become very complicated. Some services =
have very different client-server and server-client traffic patterns =
(e.g. games). In addition, sometimes the two flows can follow different =
network paths. I think once we talked about a network provider using a =
number of ISPs.

However, using RTT for tuning a one-way TCMTF may not be bad... or is it =
bad? Any other thoughts?

BR,

Jose

> -----Mensaje original-----
> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> Enviado el: martes, 15 de enero de 2013 18:04
> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko Su=C5=BEnjevi=C4=87'; =
Juli=C3=A1n Fern=C3=A1ndez
> Navajas
> CC: tcmtf@ietf.org
> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using =
Tunneling
> Compressed Multiplexed Traffic Flows
>=20
> Hi all,
>=20
>         To re-open that issue, I would suggest that given that the =
delay is so
> sensitive in real time services, we need to find a consensus here.
>=20
>         My opinion is that to apply the first possibility (the static =
multiplexing
> period) we need to suppose that the network conditions are really bad, =
to be
> protected when the network congestion arises. In that case, the =
application
> of the TCMTF optimization will not be optimal, so that would be the =
less
> preferred option, but easier to implement and maintain over the time.
>=20
>         On the other hand, the second possibility would be the =
preferred. It is
> easy to know the delay between the mux and the demux but most of the
> times will not be enough unless mux and demux were really near from =
the
> client and the server respectively. I agree with Jose in the =
possibility of snoop
> RTCP packets in order to adapt the multiplexing period when =
multiplexing
> RTP packets (and RTCP is available). Talking about RTT, I=C2=B4m not =
sure if RTT
> would be useful given that the multiplexing period only affect the one =
way
> delay (OWD). Imagine the following scenario:
>         - Client - Mux/Demux - Demux/Mux - Server (two ways TCMTF,
> TWTCMTF :P)
>         - The OWD from server to client get increased
>         - The OWD from client to server remains equal
>         - Should we use a lower multiplexing period in the client to =
server
> direction? I don=C2=B4t think so=E2=80=A6 because we should use a =
lower multiplexing
> period in the other direction.
>=20
>         My point is that the multiplexing period should only be =
affected by the
> OWD and not by the RTT (or it may be application dependent). How to
> calculate the OWD? I=C2=B4ve been reading something about OWAMP and it
> seems that an specific software has to be implemented in the =
client/server
> side.
> Can we assume that? Unfortunately I cannot contribute so much =
here=E2=80=A6
>         It is possible that for certain services the static (and worst =
case)
> multiplexing period would be the better solution.
>=20
>         What do you think?
>=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 17/12/12 12:25, "Jose Saldana" <jsaldana@unizar.es> wrote:
>=20
> >Hi all,
> >
> >Julian and I have been discussing about this. Some ideas have arisen.
> >This is the summary.
> >
> >This would be the scheme of the system, including mux and demux:
> >
> >Real-time application ------- mux -------- internet --------- demux
> >-------
> >server
> >
> >
> >I think perhaps the draft could say something like:
> >
> >When setting the multiplexing period, there are two possibilities:
> >
> >1.- Static / permanent: At system setup time, network delays are
> >measured, and a multiplexing period is selected and set in the =
multiplexer.
> >
> >2.- Dynamic: A mechanism is used so as to adapt to the evolution of
> >network delays. In this case, different mechanisms can be used in =
order
> >to obtain periodical end-to-end network delay estimations, which =
would
> >be useful in order to set the multiplexing period:
> >
> >- If the traffic is RTP, then RTCP packets containing the estimation
> >could be analyzed in order to extract these values, as Dan suggests.
> >The question
> >is: would that packets travel through the multiplexer?
> >- If the traffic is TCP, perhaps something similar to the RTT
> >estimation of TCP could be useful.
> >- If the traffic is UDP, should the mux use something like OWAMP
> >(http://tools.ietf.org/html/rfc4656) in order to calculate two delays
> >(application to mux, and mux to server) and calculate the sum?
> >
> >
> >I think the draft is only supposed to report the maximum delays
> >normally considered acceptable. Perhaps the additional mechanisms for
> >calculating the RTT could just be suggested.
> >
> >What do you think?
> >
> >Jose
> >
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> >> de Dan Wing Enviado el: viernes, 14 de diciembre de 2012 18:33
> >> Para: jsaldana@unizar.es; 'Mirko Su=C5=BEnjevi=C4=87'
> >> CC: tcmtf@ietf.org
> >> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
> >> Tunneling Compressed Multiplexed Traffic Flows
> >>
> >> > -----Original Message-----
> >> > From: Jose Saldana [mailto:jsaldana@unizar.es]
> >> > Sent: Friday, December 14, 2012 2:58 AM
> >> > To: 'Dan Wing'; 'Mirko Su=C5=BEnjevi=C4=87'
> >> > Cc: tcmtf@ietf.org
> >> > Subject: RE: [tcmtf] Draft: Maximum Tolerable Delays when using
> >> > Tunneling Compressed Multiplexed Traffic Flows
> >> >
> >> > Dan,
> >> >
> >> > Regarding the use of the maximum delay, some days ago we =
discussed
> >> > about
> >> > it:
> >> > the actual OWD of the network should be measured (or estimated) =
in
> >> > order to know the maximum multiplexing period we can set.
> >> >
> >> > We may have this formula, if thinking one-way:
> >> >
> >> > OWD  + Mux period/2  < tolerable_OWD
> >> >
> >> > If we think RTT:
> >> >
> >> > OWD + Mux period/2 + OWD back < 2*tolerable_OWD
> >> >
> >> > I don't know if we should include a mechanism for estimating OWD =
in
> >> > tcmtf. I think this is more an implementation problem, which may =
be
> >> > already solved.
> >>
> >> Yes, it's already solved end-to-end:  RTP with RTCP feedback allows
> >> determining one way delay.
> >>
> >> But if something in the middle is multiplexing several packets
> >> together,
> >we
> >> don't want it to add too much delay.  That thing in the middle =
won't
> >>necessarily know the one way delay seen by the endpoints, unless it
> >>analyzes the RTP and RTCP.  There are devices that do that on the
> >>market,  mostly to diagnose where networks are causing loss/delay =
with
> >>RTP flows.
> >>
> >>
> >> > Another option is using some typical values, e.g. from
> >> > http://ipnetwork.bgtmo.ip.att.net/pws/global_network_avgs.html
> >> >
> >> > The draft includes some preliminary/recommended values for the
> >> > Multiplexing Period. Is this interesting? Should we put the =
formula
> >> > instead?
> >>
> >> It's probably sufficient as-is.
> >>
> >> -d
> >>
> >> > Mirko, another question: in online games, players usually talk
> >> > about the "ping", and I think it means RTT. Don't you think it
> >> > would be better to define a RTT limit instead of a OWD one in =
that case?
> >> >
> >> > What do you think?
> >> >
> >> > Jose
> >> >
> >> > > -----Mensaje original-----
> >> > > De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> > > nombre de Dan Wing Enviado el: jueves, 13 de diciembre de 2012
> >> > > 17:07
> >> > > Para: 'Mirko Su=C5=BEnjevi=C4=87'; tcmtf@ietf.org
> >> > > Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
> >> > > Tunneling Compressed Multiplexed Traffic Flows
> >> > >
> >> > > > -----Original Message-----
> >> > > > From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] =
On
> >> > > > Behalf Of Mirko Su=C5=BEnjevic
> >> > > > Sent: Thursday, December 13, 2012 1:07 AM
> >> > > > To: tcmtf@ietf.org; tsvwg@ietf.org
> >> > > > Subject: [tcmtf] Draft: Maximum Tolerable Delays when using
> >> > > > Tunneling Compressed Multiplexed Traffic Flows
> >> > > >
> >> > > > Hello,
> >> > > >
> >> > > >
> >> > > >
> >> > > > We have just submitted the draft named Maximum Tolerable =
Delays
> >> > > > when using Tunneling Compressed Multiplexed Traffic Flows:
> >> > > > =
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf
> >> > > > /
> >> > >
> >> > > The suggested 400ms for interactive voice is at least 2x too =
high.
> >> > > I
> >> > expect
> >> > > that number does not include the playout jitter buffer (which =
is
> >> > > variable,
> >> > but
> >> > > usually a few samples, so 40-80ms).  200ms end-to-end is the
> >> > > higher end,
> >> > and
> >> > > that includes jitter buffer, codec processing, and so on.
> >> > >
> >> > > But, more importantly:  it seems valuable for endpoints to =
signal
> >> > > their maximum delay somehow.  Or would the TCMTF function
> >> determine
> >> > > the maximum delay, using some heuristic?
> >> > >
> >> > > How does the TCMTF function determine how much of that =
'tolerable
> >> > > latency' budget it can consume?
> >> > >
> >> > > -d
> >> > >
> >> > >
> >> > > > It is an extension of tcmtf
> >> > > > http://datatracker.ietf.org/doc/draft-
> >> > > > saldana-tsvwg-tcmtf/. Since a specific list for tcmtf exists
> >> > > > (tcmtf@ietf.org), the idea is to discuss it there.
> >> > > >
> >> > > >
> >> > > >
> >> > > > The draft contains recommendations for TCMTF multiplexing
> >> > > > period for different real-time services. In order to prevent
> >> > > > QoE degradation of real-time services using TCMTF, a policy
> >> > > > defining a multiplexing period can be employed. Values of
> >> > > > maximum tolerable delays presented in
> >> > > the
> >> > > > draft form the base of such policy.    The recommendations =
are
> >> > presented
> >> > > > for real-time network services in which TCTMF bandwidth
> >> > > > optimization is applicable (i.e., services  which have low
> >> > > > payload to header size ratio which results in high protocol
> overhead).
> >> > > >
> >> > > >
> >> > > >
> >> > > > Your feedback will be welcome. Thank you.
> >> > > >
> >> > > >
> >> > > > Sincerely,
> >> > > >
> >> > > > Mirko Suznjevic
> >> > >
> >> > >
> >> > > _______________________________________________
> >> > > 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


From fpb@tid.es  Wed Jan 16 03:34:02 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D84A421F8727 for <tcmtf@ietfa.amsl.com>; Wed, 16 Jan 2013 03:34:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.393
X-Spam-Level: 
X-Spam-Status: No, score=-6.393 tagged_above=-999 required=5 tests=[AWL=0.205,  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 nc66sVoxEJCO for <tcmtf@ietfa.amsl.com>; Wed, 16 Jan 2013 03:34:01 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 752E821F86BE for <tcmtf@ietf.org>; Wed, 16 Jan 2013 03:33:59 -0800 (PST)
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 <0MGP00JTTUSGMJ@tid.hi.inet> for tcmtf@ietf.org; Wed, 16 Jan 2013 12:33:57 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id B2.58.03184.52096F05; Wed, 16 Jan 2013 12:33:57 +0100 (CET)
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 <0MGP00JZMUSLMJ@tid.hi.inet> for tcmtf@ietf.org; Wed, 16 Jan 2013 12:33:57 +0100 (MET)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.151]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0328.009; Wed, 16 Jan 2013 12:33:56 +0100
Date: Wed, 16 Jan 2013 11:33:56 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <004601cdf3d2$dd332250$979966f0$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
Message-id: <F5EDC35DF914C1428C28E149F10463A265043A0D@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_tT64u2GTCXMSJm+bZc9RxQ)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: RV: [tcmtf] TCMTF: Document A: mechanism for a muxer to discover a de-muxer
Thread-index: Ac3z0qpuai7heI7oSHWY0AJDN9gmvgACrW2A
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4068-b7fc06d000000c70-63-50f690259751
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOKsWRmVeSWpSXmKPExsXCFe/Apas64VuAwaKZUha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxsVbS5gKGtYzVvTMvM/ewLhjGmMXIyeHhICJxNfeLmYIW0zi wr31bF2MXBxCAhsYJbat62aGcH4wSsybcAjKmckocahlJQtIC4uAqsTJqVfYQWw2AS2J03dX gcWFBaIktr86BBbnFLCQmLzvAdQKBYk/5x6D1YgIZEtc7F4IVMPBwQw0Z943RZAwr4C3RN/U jawQtqDEj8n3wMqZBXIlZqw+zAhhi0s0t94EizMCXf391BomiJHREl+vT2GDsI0kNnx/ArZW VEBPou3YGXaIEwQkluw5D3WOqMTLx/9YJzCKzUKybhaSdbOQrIOwDSTen5vPDGFrSyxb+BrK 1pfY+OUsVL2ZxIJz55mQ1Sxg5FjFKFacVJSZnlGSm5iZk25gqJeRqZeZl1qyiRESkxk7GJfv VDnEKMDBqMTDe+Ds5wAh1sSy4srcQ4ySHExKorx5vd8ChPiS8lMqMxKLM+KLSnNSiw8xSnAw K4nwLrMHyvGmJFZWpRblw6RkODiUJHjl+4FSgkWp6akVaZk5wMQDk2bi4ARp5wFqFwap4S0u SMwtzkyHyJ9iVOVoOdD9nFGIJS8/L1VKnPdtH1CRAEhRRmke3JxXjOJABwvzGoCM4AGmTrgJ r4CGMwEN37T3M8jwkkSElFQD46YWw/Nt6zc/1ZGyLj4Sb75DO2ttU+pSpb9Hjsk+PKDypSRb 6WoG29cd2ZHbPvetX3rOS8TkuxvvpLk1n4pqReY/+hn1uez1j9qnEzsfzPjw3+r0xMKiW+/X MgZ0Rj5Mv+F261lAUdMxzYLGN1cyahTy9dq/rAycVPJTWKcmY5aAHv+/+Acq25RYijMSDbWY i4oTASPGRaRaAwAA
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a de-muxer
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, 16 Jan 2013 11:34:03 -0000

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

Hi Jose, Muthu,

I=B4m sure we will find a consensus about that :). What Muthu proposes soun=
ds interesting to me but, to be honest, I think TCMTF establishing should b=
e quite similar to the establishing procedures of tunnels defined in draft =
A (L2TP, GRE=85), actually at network level TCMTF is a tunnel. Once establi=
shed signaling will negotiate upper levels (multiplexing and HC) to perform=
 TCMTF (draft A).

What do you think?

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: mi=E9rcoles, 16 de enero de 2013 11:18
To: "'Muthu Arul Mozhi Perumal (mperumal) '" <mperumal@cisco.com<mailto:mpe=
rumal@cisco.com>>, 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: RV: [tcmtf] TCMTF: Document A: mechanism for a muxer to discover a=
 de-muxer


Fernando, Muthu, everyone,



Since there is no consensus about this, I think we should carry on with the=
 debate. Do you think the mechanism would be very complicated? Any new idea=
s?:



- *dynamically establishing, modifying and releasing tunnels*



#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.



There is still no consensus here:



Fernando: =93Regarding #1, to be honest, I am not completely sure of the ne=
ed to specify a mechanism to discover muxes and demuxes between them. I thi=
nk those kind of mechanisms have more sense in local environments but I=B4m=
 not sure if it applies here. At least at the beginning this associations c=
an be done manually.=94



Muthu: =93I think it is the opposite -- in local environments you can provi=
sion/associate them manually. However, in a multi-vendor environment over t=
he Internet this should happen automatically.=94

=93#1 needs to be specified.=94


Best regards,

Jose

De: tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-bou=
nces@ietf.org] En nombre de Jose Saldana
Enviado el: martes, 15 de enero de 2013 11:56
Para: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: [tcmtf] TCMTF: Document A discussion: content and charter

Document (A) refers to the main TCMTF draft, currently in http://datatracke=
r.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

1.- Content of the Document

Currently it contains the description of the question and the protocols whi=
ch could be used on each layer (tunneling, compressing, multiplexing). It s=
ays that the signaling issues would be that of each protocol.

There is consensus (I think) about this: we should include some signaling i=
ssues. The question is: What should we include in Draft A and what in Draft=
 C?

- *Auto-negotiation* Negotiation mechanisms to decide the options at each l=
ayer (compression, multiplexing and tunneling) between mux and demux. Perha=
ps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP and IPHC,=
 so the two machines will have to negotiate in order to decide which compre=
ssion protocol use.

This should be included in (A). I think there is consensus about this:
Juan Antonio: =93The first kind of signaling ("auto-negotiation") is needed=
 from the beginning if we don't want an extremely static protocol and there=
fore possibly difficult to get it working, especially when in most of cases=
 the peers belong to different entities/companies.=94



Dan: =93We need that -- it is capabilities negotiation.  It is needed becau=
se the protocol will fail if one side mistakenly thinks the other side has =
certain functionality, and because we will want to add some fancy new compr=
ession in the year 2020 and will need to negotiate it.=94



Fernando: =93I also agree with the idea of including the mux-demux signalin=
g within the draft A (as Dan said, they are capabilities negotiation). This=
 draft should be able to get two boxes with TCMTF fully working between the=
m. Under my point of view this includes the definition of the capabilities =
in each node and the negotiation of that capabilities.=94



Does this mean that Document (A) will no longer be a Best Current Practice?=
 I think so.





- *dynamically establishing, modifying and releasing tunnels*



#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.



There is still no consensus here:



Fernando: =93Regarding #1, to be honest, I am not completely sure of the ne=
ed to specify a mechanism to discover muxes and demuxes between them. I thi=
nk those kind of mechanisms have more sense in local environments but I=B4m=
 not sure if it applies here. At least at the beginning this associations c=
an be done manually.=94



Muthu: =93I think it is the opposite -- in local environments you can provi=
sion/associate them manually. However, in a multi-vendor environment over t=
he Internet this should happen automatically.=94

=93#1 needs to be specified.=94







#2. A mechanism to *elect an optimal muxer and a de-muxer when there are mo=
re than one muxer/de-muxer for a flow*.



We agree: This can wait for Document (C).



                Fernando: =93#2 is more related to the higher entity that h=
as to decide whether a flow should be TCMTFed or not, and under my point of=
 view it can be addressed in a different draft.=94

                Muthu: =93#2 can be added later.=94





3. A mechanism to *setup/release a tunnel b/w a muxer and a de-muxer*.



We agree: This has to be included in (A).



                Fernando =93#3 I think should be included in the draft A, s=
ince it is a mechanism within the TFMTF protocol itself.=94

                Muthu: =93#3 many not require much specification.=94





2.- Should we include it in the Charter now?

Of course, Document (A) should be in the charter.


Best regards,

Jose


________________________________

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

--Boundary_(ID_tT64u2GTCXMSJm+bZc9RxQ)
Content-id: <169D7BCBA4B65945BC74A1B6EE880039@hi.inet>
Content-type: text/html; charset=Windows-1252
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font=
-family:Calibri,sans-serif">
<div>
<div>
<div>Hi Jose, Muthu,</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>I=B4m =
sure we will find a consensus about that :). What Muthu proposes sounds int=
eresting to me but, to be honest, I think TCMTF establishing should be quit=
e similar to the establishing procedures
 of tunnels defined in draft A (L2TP, GRE=85), actually at network level TC=
MTF is a tunnel. Once established signaling will negotiate upper levels (mu=
ltiplexing and HC) to perform TCMTF (draft A).</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>What d=
o you think?</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>mi=E9rcoles, 16 de enero de 2=
013 11:18<br>
<span style=3D"font-weight:bold">To: </span>&quot;'Muthu Arul Mozhi Perumal=
 (mperumal) '&quot; &lt;<a href=3D"mailto:mperumal@cisco.com">mperumal@cisc=
o.com</a>&gt;, Fernando Pascual Blanco &lt;<a href=3D"mailto:fpb@tid.es">fp=
b@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>RV: [tcmtf] TCMTF: Documen=
t A: mechanism for a muxer to discover a de-muxer<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: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"}
span.TextosinformatoCar
	{font-family:"Calibri","sans-serif"}
span.EstiloCorreo19
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.EstiloCorreo20
	{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"MsoPlainText"><span lang=3D"EN-US">Fernando, Muthu, everyone,</=
span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Since there is no consensus =
about this, I think we should carry on with the debate. Do you think the me=
chanism would be very complicated? Any new ideas?:</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">- *<b>dynamically establishi=
ng, modifying and releasing tunnels</b>*</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">#1. A *<b>mechanism for a mu=
xer to discover a de-muxer (and vice versa)</b>*.</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">There is still no consensus =
here:</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span lang=3D"EN-US"=
>Fernando: =93Regarding #1, to be honest, I am not completely sure of the n=
eed to specify a mechanism to discover muxes and demuxes between them. I th=
ink those kind of mechanisms have more sense
 in local environments but I=B4m not sure if it applies here. At least at t=
he beginning this associations can be done manually.=94</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span lang=3D"EN-US"=
>Muthu: =93I think it is the opposite -- in local environments you can prov=
ision/associate them manually. However, in a multi-vendor environment over =
the Internet this should happen automatically.=94
</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt; text-indent:35.4pt">=
<span lang=3D"EN-US">=93#1 needs to be specified.=94</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Best regards,</span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><br>
Jose</span></p>
<p class=3D"MsoNormal"><span 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">
<a href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a hr=
ef=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]
<b>En nombre de </b>Jose Saldana<br>
<b>Enviado el:</b> martes, 15 de enero de 2013 11:56<br>
<b>Para:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tcmtf] TCMTF: Document A discussion: content and charter</s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Document (A) refers to the main=
 TCMTF draft, currently in
<a href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http=
://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">1.- Content of the Document</sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Currently it contains the descr=
iption of the question and the protocols which could be used on each layer =
(tunneling, compressing, multiplexing). It says that the signaling issues w=
ould be that of each protocol.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">There is consensus (I think) ab=
out this: we should include some signaling issues. The question is: What sh=
ould we include in Draft A and what in Draft C?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">- *<b>Auto-negotiation</b>* Neg=
otiation mechanisms to decide the options at each layer (compression, multi=
plexing and tunneling) between mux and demux. Perhaps the mux has ROHC, ECR=
TP and IPHC, and the demux only has
 ECRTP and IPHC, so the two machines will have to negotiate in order to dec=
ide which compression protocol use.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">This should be included in (A).=
 I think there is consensus about this:</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lang=3D"EN-US">Ju=
an Antonio: =93The first kind of signaling (&quot;auto-negotiation&quot;) i=
s needed from the beginning if we don't want an extremely static protocol a=
nd therefore possibly difficult to get it working,
 especially when in most of cases the peers belong to different entities/co=
mpanies.=94</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Dan: =93We need that -- it is capabilities negotiation.&nbsp; It is neede=
d because the protocol will fail if one side mistakenly thinks the other si=
de has certain functionality, and because we
 will want to add some fancy new compression in the year 2020 and will need=
 to negotiate it.=94</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">Fernando: =93I also agree with the idea of including the mux-demux signal=
ing within the draft A (as Dan said, they are capabilities negotiation). Th=
is draft should be able to get two boxes
 with TCMTF fully working between them. Under my point of view this include=
s the definition of the capabilities in each node and the negotiation of th=
at capabilities.=94</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Does this mean that Document=
 (A) will no longer be a Best Current Practice? I think so.</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">- *<b>dynamically establishi=
ng, modifying and releasing tunnels</b>*</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">#1. A *<b>mechanism for a mu=
xer to discover a de-muxer (and vice versa)</b>*.</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">There is still no consensus =
here:</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span lang=3D"EN-US"=
>Fernando: =93Regarding #1, to be honest, I am not completely sure of the n=
eed to specify a mechanism to discover muxes and demuxes between them. I th=
ink those kind of mechanisms have more sense
 in local environments but I=B4m not sure if it applies here. At least at t=
he beginning this associations can be done manually.=94</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span lang=3D"EN-US"=
>Muthu: =93I think it is the opposite -- in local environments you can prov=
ision/associate them manually. However, in a multi-vendor environment over =
the Internet this should happen automatically.=94
</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt; text-indent:35.4pt">=
<span lang=3D"EN-US">=93#1 needs to be specified.=94</span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span lang=3D"EN-US=
">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">#2. A mechanism to *<b>elect=
 an optimal muxer and a de-muxer when there are more than one muxer/de-muxe=
r for a flow</b>*.</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">We agree: This can wait for =
Document (C).</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fernando: =
=93#2 is more related to the higher entity that has to decide whether a flo=
w should be TCMTFed or not, and under my point of view it can be addressed =
in a different draft.=94</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu: =93#2=
 can be added later.=94</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">3. A mechanism to *<b>setup/=
release a tunnel b/w a muxer and a de-muxer</b>*.</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">We agree: This has to be inc=
luded in (A).</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fernando =93=
#3 I think should be included in the draft A, since it is a mechanism withi=
n the TFMTF protocol itself.=94</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu: =93#3=
 many not require much specification.=94</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">2.- Should we include it in =
the Charter now?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Of course, Document (A) should =
be in the charter.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Best regards,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jose</span></p>
<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_tT64u2GTCXMSJm+bZc9RxQ)--

From fpb@tid.es  Wed Jan 16 03:51:59 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CF3F21F877B for <tcmtf@ietfa.amsl.com>; Wed, 16 Jan 2013 03:51:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.262
X-Spam-Level: 
X-Spam-Status: No, score=-6.262 tagged_above=-999 required=5 tests=[AWL=0.037,  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 krPyr3AgGGMz for <tcmtf@ietfa.amsl.com>; Wed, 16 Jan 2013 03:51:57 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id A42FA21F8770 for <tcmtf@ietf.org>; Wed, 16 Jan 2013 03:51:55 -0800 (PST)
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 <0MGP00JWZVMGMJ@tid.hi.inet> for tcmtf@ietf.org; Wed, 16 Jan 2013 12:51:54 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 9C.F8.03184.A5496F05; Wed, 16 Jan 2013 12:51:54 +0100 (CET)
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 <0MGP00JZPVMHMJ@tid.hi.inet> for tcmtf@ietf.org; Wed, 16 Jan 2013 12:51:53 +0100 (MET)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.151]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0318.004; Wed, 16 Jan 2013 12:51:53 +0100
Date: Wed, 16 Jan 2013 11:51:53 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <007401cdf3d8$3f988ca0$bec9a5e0$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, 'Dan Wing' <dwing@cisco.com>, =?utf-8?B?J01pcmtvIFN1xb5uamV2acSHJw==?= <Mirko.Suznjevic@fer.hr>, =?utf-8?B?J0p1bGnDoW4gRmVybsOhbmRleiBOYXZhamFzJw==?= <navajas@unizar.es>
Message-id: <F5EDC35DF914C1428C28E149F10463A265043B31@EX10-MB1-MAD.hi.inet>
Content-id: <69E3D03CA1DC9944B5FB247597FB5A6B@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] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
Thread-index: AQHN899xAC2KhZu2o0+MbWmxdLVrNg==
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4068-b7fc06d000000c70-ea-50f6945a5648
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA01SbUgTYRzn2d22c+3inNM9iYEbWSS4FEKkJEwILEHWh8IksbOdu+E27W4O V1+ma0WTMJsmrtSQ9SaIQwhnaZaW4EtlL1/COQ0V0ySCxTTR6M5D3bff8/+9/H/w/DFEERAn YkaLlWIspEkjkaGykhxZWlFjRJc+9R3LehH2gxyQ5/P9FelAkSxbT5mMNoo5cuKSjPb+CILK gAdU1z1uRRzgaz1wAwyDxFHor6PdIIaDCXAy1C1xAxmmIPwAOptGpcJjDcCVrjaR8GgBcDS0 ivIWlEiBy1OvEB5LiFQ4Pt25NY8jKuGt33/EPI4hsmBzzWdUWJEMNz7MoXyQkggCOD7/TMLX QLigtoia1+BEPnSNCV6EyIRhx6BUmMfCNU8IFeSHYGOjWZCooNP1DRWwGt7rcAAeA2I//NXe vhWjJK7AmeutW5uUhBb2NuXy43gO3hiZkArNCOjr/4gIOB4uzf0T3wHQG1XCG1XCu1vCG1XC G1XiIRB3ggS2lDEaaKuZNJoM6Rla2qg1WihrDxC+jg6AJ30HhgCBAY0cf/0+rFOISRtrNw+B fZhIE48n343oFHtLK/R2mmTpEqbKRLFDAGKIRokfbOA4XE/ar1JMxTaVhGEaiLd4OCqWoQxU dZnRxF3LNi3CYni7nLO/4zU4W0maWaNB4MdACjY4f3MRKFBLhYVKVOHlvIjgRXSVZSdnGai4 wnH4U56Vc+e4k7DMhYu48J6BMB9uJXepRAew5aG9594+UNcsymdKyzwFxd0uN/nFxVxb77pd qFa9mV4svl/oG3YnHWAzmzcfodpAVyC4HkH8AyMLzv5Z2+FT9W1h27HVUFr/hfLu4YbZuotu J7kxmftyT9GnkxPNS2eDZxY23R32FOnl47Ur9vzz2p/jtoLs2r56/fPk0woNytJkRirCsOR/ SSTkGUsDAAA=
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jan 2013 11:51:59 -0000

SGkgSm9zZSwNCg0KICAgICAgICBZb3UgYXJlIHJpZ2h0LCBidXQgbXkgcG9pbnQgaGVyZSBpczoN
Cg0KICAgICAgICAgICAgICAgIENsaWVudCAtIE11eCAtIERlbXV4IC0gU2VydmVyDQoNCiAgICAg
ICAgSW1hZ2luZSB0aGF0IHRoZXJlIGlzIGVub3VnaCBwYWNrZXRzIGJldHdlZW4gbXV4IGFuZCBk
ZW11eCB0byBtYWtlIHRoZQ0KYWRkZWQgZGVsYXkgdmVyeSBzbWFsbCAoVENNVEYgaXMgd29ya2lu
ZyB2ZXJ5IHdlbGwgYW5kIHRoZSBtdXggaGFzIG5vdCB0bw0Kd2FpdCB0aGUgbXVsdGlwbGV4aW5n
IHBlcmlvZCB0byBmdWxmaWxsIGEgYmlnIHBhY2tldCBhbmQgc2VuZCBpdCwgc28NCmltYWdpbmUg
YSBtdWx0aXBsZXhpbmcgcGVyaW9kIG9mIDUwIG1zIGFuZCBhIGJpZyBwYWNrZXQgaXMgZnVsZmls
bGVkIGluIDUNCm1zKS4gSWYgdGhlIFJUVCBnZXQgaW5jcmVhc2VkIGJlY2F1c2UgYSBjb25nZXN0
aW9uIGluIHRoZSB3YXkgYmFjayB0byB0aGUNCmNsaWVudCAodGhlcmUgaXMgbm8gVENNVEYgb3B0
aW1pemF0aW9uKSBhbmQgd2UgZGVjcmVhc2UgdGhlIG11bHRpcGxleGluZw0KcGVyaW9kIChldmVu
IGluIHRoZSBleHRyZW1lIHdlIGNhbiBkaXNhYmxlIHRoZSBUQ01URiBvcHRpbWl6YXRpb24pIHRo
ZQ0KaGlnaCBSVFQgd2lsbCByZW1haW4uIEV2ZW4gaWYgdGhlIFRDTVRGIG9wdGltaXphdGlvbiB3
YXMgaGVscGluZyBpbiB0aGUNCmNsaWVudCB0byBzZXJ2ZXIgcGF0aCwgZGlzYWJsaW5nIGl0IG1h
eSBoYXJtLiBEbyB5b3UgdGhpbmsgdGhhdCBzY2VuYXJpbw0Kd291bGQgYmUgcG9zc2libGU/DQoN
CiAgICAgICAgU28gScK0bSBub3Qgc3VyZSBhYm91dCB0aGF0LCBJIHRoaW5rIHdlIG5lZWQgbW9y
ZSBvcGluaW9ucyBoZXJlLg0KDQpSZWdhcmRzLA0KDQpGZXJuYW5kbyBQYXNjdWFsIEJsYW5jbw0K
VGVsZWbDs25pY2EgR2xvYmFsIFJlc291cmNlcw0KTmV0d29yayBBdXRvbWF0aW9uIGFuZCBEeW5h
bWl6YXRpb24NClRFQ0hOT0xPR1kgUEVPUExFIEdST1VQDQpGICszNDkxMzEyODc3OQ0KTSArMzQ2
ODIwMDUxNjgNCmZwYkB0aWQuZXMNCg0KDQoNCg0KT24gMTYvMDEvMTMgMTE6NTcsICJKb3NlIFNh
bGRhbmEiIDxqc2FsZGFuYUB1bml6YXIuZXM+IHdyb3RlOg0KDQo+TXkgdHdvIGNlbnRzOg0KPg0K
PkluIGdhbWVzIGFuZCBpbiBWb0lQIHRoZSByZWFsbHkgaW1wb3J0YW50IHRoaW5nIGlzIFJUVDoN
Cj4NCj4tIEdhbWVzIGFsd2F5cyBtZWFzdXJlIHRoZSBSVFQgKGdhbWVycyB0YWxrIGFib3V0IHRo
ZSAicGluZyIpOiB0aGUNCj5pbXBvcnRhbnQgdGhpbmcgaXMgdGhlIGRlbGF5IGZyb20gYSBwbGF5
ZXIgYWN0aW9uIHRvIHRoZSBzZXJ2ZXIgcmVhY3Rpb24NCj5hcnJpdmluZyB0byB0aGUgcGxheWVy
J3MgbWFjaGluZS4NCj4tIEluIFZvSVAgSSB0aGluayBpdCBpcyB0aGUgc2FtZTogd2hhdCBtYXR0
ZXJzIGlzIHRoZSBSVFQsIGluIG9yZGVyIHRvDQo+Z3JhbnQgaW50ZXJhY3Rpdml0eSBhbmQgYXZv
aWRpbmcgY3Jvc3MtdGFsay4NCj4NCj5JbiBhZGRpdGlvbiwgUlRUIGlzIGVhc2llciB0byBtZWFz
dXJlIHRoYW4gT1dELCBzaW5jZSB5b3UgZG9uJ3QgbmVlZA0KPnN5bmNocm9uaXphdGlvbi4NCj4N
Cj5BbmQgcmVnYXJkaW5nIFR3by13YXkgVENNVEYsIEkgdGhpbmsgd2UgaGF2ZSB0byB0aGluayBh
Ym91dCBUQ01URiBhcw0KPm9uZS13YXkuIE90aGVyd2lzZSwgdGhpbmdzIHdvdWxkIGJlY29tZSB2
ZXJ5IGNvbXBsaWNhdGVkLiBTb21lIHNlcnZpY2VzDQo+aGF2ZSB2ZXJ5IGRpZmZlcmVudCBjbGll
bnQtc2VydmVyIGFuZCBzZXJ2ZXItY2xpZW50IHRyYWZmaWMgcGF0dGVybnMNCj4oZS5nLiBnYW1l
cykuIEluIGFkZGl0aW9uLCBzb21ldGltZXMgdGhlIHR3byBmbG93cyBjYW4gZm9sbG93IGRpZmZl
cmVudA0KPm5ldHdvcmsgcGF0aHMuIEkgdGhpbmsgb25jZSB3ZSB0YWxrZWQgYWJvdXQgYSBuZXR3
b3JrIHByb3ZpZGVyIHVzaW5nIGENCj5udW1iZXIgb2YgSVNQcy4NCj4NCj5Ib3dldmVyLCB1c2lu
ZyBSVFQgZm9yIHR1bmluZyBhIG9uZS13YXkgVENNVEYgbWF5IG5vdCBiZSBiYWQuLi4gb3IgaXMg
aXQNCj5iYWQ/IEFueSBvdGhlciB0aG91Z2h0cz8NCj4NCj5CUiwNCj4NCj5Kb3NlDQo+DQo+PiAt
LS0tLU1lbnNhamUgb3JpZ2luYWwtLS0tLQ0KPj4gRGU6IEZFUk5BTkRPIFBBU0NVQUwgQkxBTkNP
IFttYWlsdG86ZnBiQHRpZC5lc10NCj4+IEVudmlhZG8gZWw6IG1hcnRlcywgMTUgZGUgZW5lcm8g
ZGUgMjAxMyAxODowNA0KPj4gUGFyYToganNhbGRhbmFAdW5pemFyLmVzOyAnRGFuIFdpbmcnOyAn
TWlya28gU3XFvm5qZXZpxIcnOyBKdWxpw6FuDQo+PkZlcm7DoW5kZXoNCj4+IE5hdmFqYXMNCj4+
IENDOiB0Y210ZkBpZXRmLm9yZw0KPj4gQXN1bnRvOiBSZTogW3RjbXRmXSBEcmFmdDogTWF4aW11
bSBUb2xlcmFibGUgRGVsYXlzIHdoZW4gdXNpbmcgVHVubmVsaW5nDQo+PiBDb21wcmVzc2VkIE11
bHRpcGxleGVkIFRyYWZmaWMgRmxvd3MNCj4+DQo+PiBIaSBhbGwsDQo+Pg0KPj4gICAgICAgICBU
byByZS1vcGVuIHRoYXQgaXNzdWUsIEkgd291bGQgc3VnZ2VzdCB0aGF0IGdpdmVuIHRoYXQgdGhl
DQo+PmRlbGF5IGlzIHNvDQo+PiBzZW5zaXRpdmUgaW4gcmVhbCB0aW1lIHNlcnZpY2VzLCB3ZSBu
ZWVkIHRvIGZpbmQgYSBjb25zZW5zdXMgaGVyZS4NCj4+DQo+PiAgICAgICAgIE15IG9waW5pb24g
aXMgdGhhdCB0byBhcHBseSB0aGUgZmlyc3QgcG9zc2liaWxpdHkgKHRoZSBzdGF0aWMNCj4+bXVs
dGlwbGV4aW5nDQo+PiBwZXJpb2QpIHdlIG5lZWQgdG8gc3VwcG9zZSB0aGF0IHRoZSBuZXR3b3Jr
IGNvbmRpdGlvbnMgYXJlIHJlYWxseSBiYWQsDQo+PnRvIGJlDQo+PiBwcm90ZWN0ZWQgd2hlbiB0
aGUgbmV0d29yayBjb25nZXN0aW9uIGFyaXNlcy4gSW4gdGhhdCBjYXNlLCB0aGUNCj4+YXBwbGlj
YXRpb24NCj4+IG9mIHRoZSBUQ01URiBvcHRpbWl6YXRpb24gd2lsbCBub3QgYmUgb3B0aW1hbCwg
c28gdGhhdCB3b3VsZCBiZSB0aGUgbGVzcw0KPj4gcHJlZmVycmVkIG9wdGlvbiwgYnV0IGVhc2ll
ciB0byBpbXBsZW1lbnQgYW5kIG1haW50YWluIG92ZXIgdGhlIHRpbWUuDQo+Pg0KPj4gICAgICAg
ICBPbiB0aGUgb3RoZXIgaGFuZCwgdGhlIHNlY29uZCBwb3NzaWJpbGl0eSB3b3VsZCBiZSB0aGUN
Cj4+cHJlZmVycmVkLiBJdCBpcw0KPj4gZWFzeSB0byBrbm93IHRoZSBkZWxheSBiZXR3ZWVuIHRo
ZSBtdXggYW5kIHRoZSBkZW11eCBidXQgbW9zdCBvZiB0aGUNCj4+IHRpbWVzIHdpbGwgbm90IGJl
IGVub3VnaCB1bmxlc3MgbXV4IGFuZCBkZW11eCB3ZXJlIHJlYWxseSBuZWFyIGZyb20gdGhlDQo+
PiBjbGllbnQgYW5kIHRoZSBzZXJ2ZXIgcmVzcGVjdGl2ZWx5LiBJIGFncmVlIHdpdGggSm9zZSBp
biB0aGUNCj4+cG9zc2liaWxpdHkgb2Ygc25vb3ANCj4+IFJUQ1AgcGFja2V0cyBpbiBvcmRlciB0
byBhZGFwdCB0aGUgbXVsdGlwbGV4aW5nIHBlcmlvZCB3aGVuIG11bHRpcGxleGluZw0KPj4gUlRQ
IHBhY2tldHMgKGFuZCBSVENQIGlzIGF2YWlsYWJsZSkuIFRhbGtpbmcgYWJvdXQgUlRULCBJwrRt
IG5vdCBzdXJlIGlmDQo+PlJUVA0KPj4gd291bGQgYmUgdXNlZnVsIGdpdmVuIHRoYXQgdGhlIG11
bHRpcGxleGluZyBwZXJpb2Qgb25seSBhZmZlY3QgdGhlIG9uZQ0KPj53YXkNCj4+IGRlbGF5IChP
V0QpLiBJbWFnaW5lIHRoZSBmb2xsb3dpbmcgc2NlbmFyaW86DQo+PiAgICAgICAgIC0gQ2xpZW50
IC0gTXV4L0RlbXV4IC0gRGVtdXgvTXV4IC0gU2VydmVyICh0d28gd2F5cyBUQ01URiwNCj4+IFRX
VENNVEYgOlApDQo+PiAgICAgICAgIC0gVGhlIE9XRCBmcm9tIHNlcnZlciB0byBjbGllbnQgZ2V0
IGluY3JlYXNlZA0KPj4gICAgICAgICAtIFRoZSBPV0QgZnJvbSBjbGllbnQgdG8gc2VydmVyIHJl
bWFpbnMgZXF1YWwNCj4+ICAgICAgICAgLSBTaG91bGQgd2UgdXNlIGEgbG93ZXIgbXVsdGlwbGV4
aW5nIHBlcmlvZCBpbiB0aGUgY2xpZW50IHRvDQo+PnNlcnZlcg0KPj4gZGlyZWN0aW9uPyBJIGRv
bsK0dCB0aGluayBzb+KApiBiZWNhdXNlIHdlIHNob3VsZCB1c2UgYSBsb3dlciBtdWx0aXBsZXhp
bmcNCj4+IHBlcmlvZCBpbiB0aGUgb3RoZXIgZGlyZWN0aW9uLg0KPj4NCj4+ICAgICAgICAgTXkg
cG9pbnQgaXMgdGhhdCB0aGUgbXVsdGlwbGV4aW5nIHBlcmlvZCBzaG91bGQgb25seSBiZQ0KPj5h
ZmZlY3RlZCBieSB0aGUNCj4+IE9XRCBhbmQgbm90IGJ5IHRoZSBSVFQgKG9yIGl0IG1heSBiZSBh
cHBsaWNhdGlvbiBkZXBlbmRlbnQpLiBIb3cgdG8NCj4+IGNhbGN1bGF0ZSB0aGUgT1dEPyBJwrR2
ZSBiZWVuIHJlYWRpbmcgc29tZXRoaW5nIGFib3V0IE9XQU1QIGFuZCBpdA0KPj4gc2VlbXMgdGhh
dCBhbiBzcGVjaWZpYyBzb2Z0d2FyZSBoYXMgdG8gYmUgaW1wbGVtZW50ZWQgaW4gdGhlDQo+PmNs
aWVudC9zZXJ2ZXINCj4+IHNpZGUuDQo+PiBDYW4gd2UgYXNzdW1lIHRoYXQ/IFVuZm9ydHVuYXRl
bHkgSSBjYW5ub3QgY29udHJpYnV0ZSBzbyBtdWNoIGhlcmXigKYNCj4+ICAgICAgICAgSXQgaXMg
cG9zc2libGUgdGhhdCBmb3IgY2VydGFpbiBzZXJ2aWNlcyB0aGUgc3RhdGljIChhbmQgd29yc3QN
Cj4+Y2FzZSkNCj4+IG11bHRpcGxleGluZyBwZXJpb2Qgd291bGQgYmUgdGhlIGJldHRlciBzb2x1
dGlvbi4NCj4+DQo+PiAgICAgICAgIFdoYXQgZG8geW91IHRoaW5rPw0KPj4NCj4+IFJlZ2FyZHMs
DQo+Pg0KPj4gRmVybmFuZG8gUGFzY3VhbCBCbGFuY28NCj4+IFRlbGVmw7NuaWNhIEdsb2JhbCBS
ZXNvdXJjZXMNCj4+IE5ldHdvcmsgQXV0b21hdGlvbiBhbmQgRHluYW1pemF0aW9uDQo+PiBURUNI
Tk9MT0dZIFBFT1BMRSBHUk9VUA0KPj4gRiArMzQ5MTMxMjg3NzkNCj4+IE0gKzM0NjgyMDA1MTY4
DQo+PiBmcGJAdGlkLmVzDQo+Pg0KPj4NCj4+DQo+Pg0KPj4gT24gMTcvMTIvMTIgMTI6MjUsICJK
b3NlIFNhbGRhbmEiIDxqc2FsZGFuYUB1bml6YXIuZXM+IHdyb3RlOg0KPj4NCj4+ID5IaSBhbGws
DQo+PiA+DQo+PiA+SnVsaWFuIGFuZCBJIGhhdmUgYmVlbiBkaXNjdXNzaW5nIGFib3V0IHRoaXMu
IFNvbWUgaWRlYXMgaGF2ZSBhcmlzZW4uDQo+PiA+VGhpcyBpcyB0aGUgc3VtbWFyeS4NCj4+ID4N
Cj4+ID5UaGlzIHdvdWxkIGJlIHRoZSBzY2hlbWUgb2YgdGhlIHN5c3RlbSwgaW5jbHVkaW5nIG11
eCBhbmQgZGVtdXg6DQo+PiA+DQo+PiA+UmVhbC10aW1lIGFwcGxpY2F0aW9uIC0tLS0tLS0gbXV4
IC0tLS0tLS0tIGludGVybmV0IC0tLS0tLS0tLSBkZW11eA0KPj4gPi0tLS0tLS0NCj4+ID5zZXJ2
ZXINCj4+ID4NCj4+ID4NCj4+ID5JIHRoaW5rIHBlcmhhcHMgdGhlIGRyYWZ0IGNvdWxkIHNheSBz
b21ldGhpbmcgbGlrZToNCj4+ID4NCj4+ID5XaGVuIHNldHRpbmcgdGhlIG11bHRpcGxleGluZyBw
ZXJpb2QsIHRoZXJlIGFyZSB0d28gcG9zc2liaWxpdGllczoNCj4+ID4NCj4+ID4xLi0gU3RhdGlj
IC8gcGVybWFuZW50OiBBdCBzeXN0ZW0gc2V0dXAgdGltZSwgbmV0d29yayBkZWxheXMgYXJlDQo+
PiA+bWVhc3VyZWQsIGFuZCBhIG11bHRpcGxleGluZyBwZXJpb2QgaXMgc2VsZWN0ZWQgYW5kIHNl
dCBpbiB0aGUNCj4+bXVsdGlwbGV4ZXIuDQo+PiA+DQo+PiA+Mi4tIER5bmFtaWM6IEEgbWVjaGFu
aXNtIGlzIHVzZWQgc28gYXMgdG8gYWRhcHQgdG8gdGhlIGV2b2x1dGlvbiBvZg0KPj4gPm5ldHdv
cmsgZGVsYXlzLiBJbiB0aGlzIGNhc2UsIGRpZmZlcmVudCBtZWNoYW5pc21zIGNhbiBiZSB1c2Vk
IGluIG9yZGVyDQo+PiA+dG8gb2J0YWluIHBlcmlvZGljYWwgZW5kLXRvLWVuZCBuZXR3b3JrIGRl
bGF5IGVzdGltYXRpb25zLCB3aGljaCB3b3VsZA0KPj4gPmJlIHVzZWZ1bCBpbiBvcmRlciB0byBz
ZXQgdGhlIG11bHRpcGxleGluZyBwZXJpb2Q6DQo+PiA+DQo+PiA+LSBJZiB0aGUgdHJhZmZpYyBp
cyBSVFAsIHRoZW4gUlRDUCBwYWNrZXRzIGNvbnRhaW5pbmcgdGhlIGVzdGltYXRpb24NCj4+ID5j
b3VsZCBiZSBhbmFseXplZCBpbiBvcmRlciB0byBleHRyYWN0IHRoZXNlIHZhbHVlcywgYXMgRGFu
IHN1Z2dlc3RzLg0KPj4gPlRoZSBxdWVzdGlvbg0KPj4gPmlzOiB3b3VsZCB0aGF0IHBhY2tldHMg
dHJhdmVsIHRocm91Z2ggdGhlIG11bHRpcGxleGVyPw0KPj4gPi0gSWYgdGhlIHRyYWZmaWMgaXMg
VENQLCBwZXJoYXBzIHNvbWV0aGluZyBzaW1pbGFyIHRvIHRoZSBSVFQNCj4+ID5lc3RpbWF0aW9u
IG9mIFRDUCBjb3VsZCBiZSB1c2VmdWwuDQo+PiA+LSBJZiB0aGUgdHJhZmZpYyBpcyBVRFAsIHNo
b3VsZCB0aGUgbXV4IHVzZSBzb21ldGhpbmcgbGlrZSBPV0FNUA0KPj4gPihodHRwOi8vdG9vbHMu
aWV0Zi5vcmcvaHRtbC9yZmM0NjU2KSBpbiBvcmRlciB0byBjYWxjdWxhdGUgdHdvIGRlbGF5cw0K
Pj4gPihhcHBsaWNhdGlvbiB0byBtdXgsIGFuZCBtdXggdG8gc2VydmVyKSBhbmQgY2FsY3VsYXRl
IHRoZSBzdW0/DQo+PiA+DQo+PiA+DQo+PiA+SSB0aGluayB0aGUgZHJhZnQgaXMgb25seSBzdXBw
b3NlZCB0byByZXBvcnQgdGhlIG1heGltdW0gZGVsYXlzDQo+PiA+bm9ybWFsbHkgY29uc2lkZXJl
ZCBhY2NlcHRhYmxlLiBQZXJoYXBzIHRoZSBhZGRpdGlvbmFsIG1lY2hhbmlzbXMgZm9yDQo+PiA+
Y2FsY3VsYXRpbmcgdGhlIFJUVCBjb3VsZCBqdXN0IGJlIHN1Z2dlc3RlZC4NCj4+ID4NCj4+ID5X
aGF0IGRvIHlvdSB0aGluaz8NCj4+ID4NCj4+ID5Kb3NlDQo+PiA+DQo+PiA+PiAtLS0tLU1lbnNh
amUgb3JpZ2luYWwtLS0tLQ0KPj4gPj4gRGU6IHRjbXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0
bzp0Y210Zi1ib3VuY2VzQGlldGYub3JnXSBFbiBub21icmUNCj4+ID4+IGRlIERhbiBXaW5nIEVu
dmlhZG8gZWw6IHZpZXJuZXMsIDE0IGRlIGRpY2llbWJyZSBkZSAyMDEyIDE4OjMzDQo+PiA+PiBQ
YXJhOiBqc2FsZGFuYUB1bml6YXIuZXM7ICdNaXJrbyBTdcW+bmpldmnEhycNCj4+ID4+IENDOiB0
Y210ZkBpZXRmLm9yZw0KPj4gPj4gQXN1bnRvOiBSZTogW3RjbXRmXSBEcmFmdDogTWF4aW11bSBU
b2xlcmFibGUgRGVsYXlzIHdoZW4gdXNpbmcNCj4+ID4+IFR1bm5lbGluZyBDb21wcmVzc2VkIE11
bHRpcGxleGVkIFRyYWZmaWMgRmxvd3MNCj4+ID4+DQo+PiA+PiA+IC0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+PiA+PiA+IEZyb206IEpvc2UgU2FsZGFuYSBbbWFpbHRvOmpzYWxkYW5hQHVu
aXphci5lc10NCj4+ID4+ID4gU2VudDogRnJpZGF5LCBEZWNlbWJlciAxNCwgMjAxMiAyOjU4IEFN
DQo+PiA+PiA+IFRvOiAnRGFuIFdpbmcnOyAnTWlya28gU3XFvm5qZXZpxIcnDQo+PiA+PiA+IENj
OiB0Y210ZkBpZXRmLm9yZw0KPj4gPj4gPiBTdWJqZWN0OiBSRTogW3RjbXRmXSBEcmFmdDogTWF4
aW11bSBUb2xlcmFibGUgRGVsYXlzIHdoZW4gdXNpbmcNCj4+ID4+ID4gVHVubmVsaW5nIENvbXBy
ZXNzZWQgTXVsdGlwbGV4ZWQgVHJhZmZpYyBGbG93cw0KPj4gPj4gPg0KPj4gPj4gPiBEYW4sDQo+
PiA+PiA+DQo+PiA+PiA+IFJlZ2FyZGluZyB0aGUgdXNlIG9mIHRoZSBtYXhpbXVtIGRlbGF5LCBz
b21lIGRheXMgYWdvIHdlIGRpc2N1c3NlZA0KPj4gPj4gPiBhYm91dA0KPj4gPj4gPiBpdDoNCj4+
ID4+ID4gdGhlIGFjdHVhbCBPV0Qgb2YgdGhlIG5ldHdvcmsgc2hvdWxkIGJlIG1lYXN1cmVkIChv
ciBlc3RpbWF0ZWQpIGluDQo+PiA+PiA+IG9yZGVyIHRvIGtub3cgdGhlIG1heGltdW0gbXVsdGlw
bGV4aW5nIHBlcmlvZCB3ZSBjYW4gc2V0Lg0KPj4gPj4gPg0KPj4gPj4gPiBXZSBtYXkgaGF2ZSB0
aGlzIGZvcm11bGEsIGlmIHRoaW5raW5nIG9uZS13YXk6DQo+PiA+PiA+DQo+PiA+PiA+IE9XRCAg
KyBNdXggcGVyaW9kLzIgIDwgdG9sZXJhYmxlX09XRA0KPj4gPj4gPg0KPj4gPj4gPiBJZiB3ZSB0
aGluayBSVFQ6DQo+PiA+PiA+DQo+PiA+PiA+IE9XRCArIE11eCBwZXJpb2QvMiArIE9XRCBiYWNr
IDwgMip0b2xlcmFibGVfT1dEDQo+PiA+PiA+DQo+PiA+PiA+IEkgZG9uJ3Qga25vdyBpZiB3ZSBz
aG91bGQgaW5jbHVkZSBhIG1lY2hhbmlzbSBmb3IgZXN0aW1hdGluZyBPV0QgaW4NCj4+ID4+ID4g
dGNtdGYuIEkgdGhpbmsgdGhpcyBpcyBtb3JlIGFuIGltcGxlbWVudGF0aW9uIHByb2JsZW0sIHdo
aWNoIG1heSBiZQ0KPj4gPj4gPiBhbHJlYWR5IHNvbHZlZC4NCj4+ID4+DQo+PiA+PiBZZXMsIGl0
J3MgYWxyZWFkeSBzb2x2ZWQgZW5kLXRvLWVuZDogIFJUUCB3aXRoIFJUQ1AgZmVlZGJhY2sgYWxs
b3dzDQo+PiA+PiBkZXRlcm1pbmluZyBvbmUgd2F5IGRlbGF5Lg0KPj4gPj4NCj4+ID4+IEJ1dCBp
ZiBzb21ldGhpbmcgaW4gdGhlIG1pZGRsZSBpcyBtdWx0aXBsZXhpbmcgc2V2ZXJhbCBwYWNrZXRz
DQo+PiA+PiB0b2dldGhlciwNCj4+ID53ZQ0KPj4gPj4gZG9uJ3Qgd2FudCBpdCB0byBhZGQgdG9v
IG11Y2ggZGVsYXkuICBUaGF0IHRoaW5nIGluIHRoZSBtaWRkbGUgd29uJ3QNCj4+ID4+bmVjZXNz
YXJpbHkga25vdyB0aGUgb25lIHdheSBkZWxheSBzZWVuIGJ5IHRoZSBlbmRwb2ludHMsIHVubGVz
cyBpdA0KPj4gPj5hbmFseXplcyB0aGUgUlRQIGFuZCBSVENQLiAgVGhlcmUgYXJlIGRldmljZXMg
dGhhdCBkbyB0aGF0IG9uIHRoZQ0KPj4gPj5tYXJrZXQsICBtb3N0bHkgdG8gZGlhZ25vc2Ugd2hl
cmUgbmV0d29ya3MgYXJlIGNhdXNpbmcgbG9zcy9kZWxheSB3aXRoDQo+PiA+PlJUUCBmbG93cy4N
Cj4+ID4+DQo+PiA+Pg0KPj4gPj4gPiBBbm90aGVyIG9wdGlvbiBpcyB1c2luZyBzb21lIHR5cGlj
YWwgdmFsdWVzLCBlLmcuIGZyb20NCj4+ID4+ID4gaHR0cDovL2lwbmV0d29yay5iZ3Rtby5pcC5h
dHQubmV0L3B3cy9nbG9iYWxfbmV0d29ya19hdmdzLmh0bWwNCj4+ID4+ID4NCj4+ID4+ID4gVGhl
IGRyYWZ0IGluY2x1ZGVzIHNvbWUgcHJlbGltaW5hcnkvcmVjb21tZW5kZWQgdmFsdWVzIGZvciB0
aGUNCj4+ID4+ID4gTXVsdGlwbGV4aW5nIFBlcmlvZC4gSXMgdGhpcyBpbnRlcmVzdGluZz8gU2hv
dWxkIHdlIHB1dCB0aGUgZm9ybXVsYQ0KPj4gPj4gPiBpbnN0ZWFkPw0KPj4gPj4NCj4+ID4+IEl0
J3MgcHJvYmFibHkgc3VmZmljaWVudCBhcy1pcy4NCj4+ID4+DQo+PiA+PiAtZA0KPj4gPj4NCj4+
ID4+ID4gTWlya28sIGFub3RoZXIgcXVlc3Rpb246IGluIG9ubGluZSBnYW1lcywgcGxheWVycyB1
c3VhbGx5IHRhbGsNCj4+ID4+ID4gYWJvdXQgdGhlICJwaW5nIiwgYW5kIEkgdGhpbmsgaXQgbWVh
bnMgUlRULiBEb24ndCB5b3UgdGhpbmsgaXQNCj4+ID4+ID4gd291bGQgYmUgYmV0dGVyIHRvIGRl
ZmluZSBhIFJUVCBsaW1pdCBpbnN0ZWFkIG9mIGEgT1dEIG9uZSBpbiB0aGF0DQo+PmNhc2U/DQo+
PiA+PiA+DQo+PiA+PiA+IFdoYXQgZG8geW91IHRoaW5rPw0KPj4gPj4gPg0KPj4gPj4gPiBKb3Nl
DQo+PiA+PiA+DQo+PiA+PiA+ID4gLS0tLS1NZW5zYWplIG9yaWdpbmFsLS0tLS0NCj4+ID4+ID4g
PiBEZTogdGNtdGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnRjbXRmLWJvdW5jZXNAaWV0Zi5v
cmddIEVuDQo+PiA+PiA+ID4gbm9tYnJlIGRlIERhbiBXaW5nIEVudmlhZG8gZWw6IGp1ZXZlcywg
MTMgZGUgZGljaWVtYnJlIGRlIDIwMTINCj4+ID4+ID4gPiAxNzowNw0KPj4gPj4gPiA+IFBhcmE6
ICdNaXJrbyBTdcW+bmpldmnEhyc7IHRjbXRmQGlldGYub3JnDQo+PiA+PiA+ID4gQXN1bnRvOiBS
ZTogW3RjbXRmXSBEcmFmdDogTWF4aW11bSBUb2xlcmFibGUgRGVsYXlzIHdoZW4gdXNpbmcNCj4+
ID4+ID4gPiBUdW5uZWxpbmcgQ29tcHJlc3NlZCBNdWx0aXBsZXhlZCBUcmFmZmljIEZsb3dzDQo+
PiA+PiA+ID4NCj4+ID4+ID4gPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiA+PiA+
ID4gPiBGcm9tOiB0Y210Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86dGNtdGYtYm91bmNlc0Bp
ZXRmLm9yZ10gT24NCj4+ID4+ID4gPiA+IEJlaGFsZiBPZiBNaXJrbyBTdcW+bmpldmljDQo+PiA+
PiA+ID4gPiBTZW50OiBUaHVyc2RheSwgRGVjZW1iZXIgMTMsIDIwMTIgMTowNyBBTQ0KPj4gPj4g
PiA+ID4gVG86IHRjbXRmQGlldGYub3JnOyB0c3Z3Z0BpZXRmLm9yZw0KPj4gPj4gPiA+ID4gU3Vi
amVjdDogW3RjbXRmXSBEcmFmdDogTWF4aW11bSBUb2xlcmFibGUgRGVsYXlzIHdoZW4gdXNpbmcN
Cj4+ID4+ID4gPiA+IFR1bm5lbGluZyBDb21wcmVzc2VkIE11bHRpcGxleGVkIFRyYWZmaWMgRmxv
d3MNCj4+ID4+ID4gPiA+DQo+PiA+PiA+ID4gPiBIZWxsbywNCj4+ID4+ID4gPiA+DQo+PiA+PiA+
ID4gPg0KPj4gPj4gPiA+ID4NCj4+ID4+ID4gPiA+IFdlIGhhdmUganVzdCBzdWJtaXR0ZWQgdGhl
IGRyYWZ0IG5hbWVkIE1heGltdW0gVG9sZXJhYmxlIERlbGF5cw0KPj4gPj4gPiA+ID4gd2hlbiB1
c2luZyBUdW5uZWxpbmcgQ29tcHJlc3NlZCBNdWx0aXBsZXhlZCBUcmFmZmljIEZsb3dzOg0KPj4g
Pj4gPiA+ID4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1zdXpuamV2aWMt
dHN2d2ctbXRkLXRjbXRmDQo+PiA+PiA+ID4gPiAvDQo+PiA+PiA+ID4NCj4+ID4+ID4gPiBUaGUg
c3VnZ2VzdGVkIDQwMG1zIGZvciBpbnRlcmFjdGl2ZSB2b2ljZSBpcyBhdCBsZWFzdCAyeCB0b28N
Cj4+aGlnaC4NCj4+ID4+ID4gPiBJDQo+PiA+PiA+IGV4cGVjdA0KPj4gPj4gPiA+IHRoYXQgbnVt
YmVyIGRvZXMgbm90IGluY2x1ZGUgdGhlIHBsYXlvdXQgaml0dGVyIGJ1ZmZlciAod2hpY2ggaXMN
Cj4+ID4+ID4gPiB2YXJpYWJsZSwNCj4+ID4+ID4gYnV0DQo+PiA+PiA+ID4gdXN1YWxseSBhIGZl
dyBzYW1wbGVzLCBzbyA0MC04MG1zKS4gIDIwMG1zIGVuZC10by1lbmQgaXMgdGhlDQo+PiA+PiA+
ID4gaGlnaGVyIGVuZCwNCj4+ID4+ID4gYW5kDQo+PiA+PiA+ID4gdGhhdCBpbmNsdWRlcyBqaXR0
ZXIgYnVmZmVyLCBjb2RlYyBwcm9jZXNzaW5nLCBhbmQgc28gb24uDQo+PiA+PiA+ID4NCj4+ID4+
ID4gPiBCdXQsIG1vcmUgaW1wb3J0YW50bHk6ICBpdCBzZWVtcyB2YWx1YWJsZSBmb3IgZW5kcG9p
bnRzIHRvIHNpZ25hbA0KPj4gPj4gPiA+IHRoZWlyIG1heGltdW0gZGVsYXkgc29tZWhvdy4gIE9y
IHdvdWxkIHRoZSBUQ01URiBmdW5jdGlvbg0KPj4gPj4gZGV0ZXJtaW5lDQo+PiA+PiA+ID4gdGhl
IG1heGltdW0gZGVsYXksIHVzaW5nIHNvbWUgaGV1cmlzdGljPw0KPj4gPj4gPiA+DQo+PiA+PiA+
ID4gSG93IGRvZXMgdGhlIFRDTVRGIGZ1bmN0aW9uIGRldGVybWluZSBob3cgbXVjaCBvZiB0aGF0
ICd0b2xlcmFibGUNCj4+ID4+ID4gPiBsYXRlbmN5JyBidWRnZXQgaXQgY2FuIGNvbnN1bWU/DQo+
PiA+PiA+ID4NCj4+ID4+ID4gPiAtZA0KPj4gPj4gPiA+DQo+PiA+PiA+ID4NCj4+ID4+ID4gPiA+
IEl0IGlzIGFuIGV4dGVuc2lvbiBvZiB0Y210Zg0KPj4gPj4gPiA+ID4gaHR0cDovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RvYy9kcmFmdC0NCj4+ID4+ID4gPiA+IHNhbGRhbmEtdHN2d2ctdGNtdGYv
LiBTaW5jZSBhIHNwZWNpZmljIGxpc3QgZm9yIHRjbXRmIGV4aXN0cw0KPj4gPj4gPiA+ID4gKHRj
bXRmQGlldGYub3JnKSwgdGhlIGlkZWEgaXMgdG8gZGlzY3VzcyBpdCB0aGVyZS4NCj4+ID4+ID4g
PiA+DQo+PiA+PiA+ID4gPg0KPj4gPj4gPiA+ID4NCj4+ID4+ID4gPiA+IFRoZSBkcmFmdCBjb250
YWlucyByZWNvbW1lbmRhdGlvbnMgZm9yIFRDTVRGIG11bHRpcGxleGluZw0KPj4gPj4gPiA+ID4g
cGVyaW9kIGZvciBkaWZmZXJlbnQgcmVhbC10aW1lIHNlcnZpY2VzLiBJbiBvcmRlciB0byBwcmV2
ZW50DQo+PiA+PiA+ID4gPiBRb0UgZGVncmFkYXRpb24gb2YgcmVhbC10aW1lIHNlcnZpY2VzIHVz
aW5nIFRDTVRGLCBhIHBvbGljeQ0KPj4gPj4gPiA+ID4gZGVmaW5pbmcgYSBtdWx0aXBsZXhpbmcg
cGVyaW9kIGNhbiBiZSBlbXBsb3llZC4gVmFsdWVzIG9mDQo+PiA+PiA+ID4gPiBtYXhpbXVtIHRv
bGVyYWJsZSBkZWxheXMgcHJlc2VudGVkIGluDQo+PiA+PiA+ID4gdGhlDQo+PiA+PiA+ID4gPiBk
cmFmdCBmb3JtIHRoZSBiYXNlIG9mIHN1Y2ggcG9saWN5LiAgICBUaGUgcmVjb21tZW5kYXRpb25z
IGFyZQ0KPj4gPj4gPiBwcmVzZW50ZWQNCj4+ID4+ID4gPiA+IGZvciByZWFsLXRpbWUgbmV0d29y
ayBzZXJ2aWNlcyBpbiB3aGljaCBUQ1RNRiBiYW5kd2lkdGgNCj4+ID4+ID4gPiA+IG9wdGltaXph
dGlvbiBpcyBhcHBsaWNhYmxlIChpLmUuLCBzZXJ2aWNlcyAgd2hpY2ggaGF2ZSBsb3cNCj4+ID4+
ID4gPiA+IHBheWxvYWQgdG8gaGVhZGVyIHNpemUgcmF0aW8gd2hpY2ggcmVzdWx0cyBpbiBoaWdo
IHByb3RvY29sDQo+PiBvdmVyaGVhZCkuDQo+PiA+PiA+ID4gPg0KPj4gPj4gPiA+ID4NCj4+ID4+
ID4gPiA+DQo+PiA+PiA+ID4gPiBZb3VyIGZlZWRiYWNrIHdpbGwgYmUgd2VsY29tZS4gVGhhbmsg
eW91Lg0KPj4gPj4gPiA+ID4NCj4+ID4+ID4gPiA+DQo+PiA+PiA+ID4gPiBTaW5jZXJlbHksDQo+
PiA+PiA+ID4gPg0KPj4gPj4gPiA+ID4gTWlya28gU3V6bmpldmljDQo+PiA+PiA+ID4NCj4+ID4+
ID4gPg0KPj4gPj4gPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQo+PiA+PiA+ID4gdGNtdGYgbWFpbGluZyBsaXN0DQo+PiA+PiA+ID4gdGNtdGZAaWV0
Zi5vcmcNCj4+ID4+ID4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Rj
bXRmDQo+PiA+Pg0KPj4gPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4+ID4+IHRjbXRmIG1haWxpbmcgbGlzdA0KPj4gPj4gdGNtdGZAaWV0Zi5vcmcN
Cj4+ID4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCj4+ID4N
Cj4+ID5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4g
PnRjbXRmIG1haWxpbmcgbGlzdA0KPj4gPnRjbXRmQGlldGYub3JnDQo+PiA+aHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90Y210Zg0KPj4NCj4+DQo+PiBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPj4NCj4+IEVzdGUgbWVuc2FqZSBzZSBkaXJpZ2UgZXhjbHVz
aXZhbWVudGUgYSBzdSBkZXN0aW5hdGFyaW8uIFB1ZWRlIGNvbnN1bHRhcg0KPj4gbnVlc3RyYSBw
b2zDrXRpY2EgZGUgZW52w61vIHkgcmVjZXBjacOzbiBkZSBjb3JyZW8gZWxlY3Ryw7NuaWNvIGVu
IGVsIGVubGFjZQ0KPj4gc2l0dWFkbyBtw6FzIGFiYWpvLg0KPj4gVGhpcyBtZXNzYWdlIGlzIGlu
dGVuZGVkIGV4Y2x1c2l2ZWx5IGZvciBpdHMgYWRkcmVzc2VlLiBXZSBvbmx5IHNlbmQgYW5kDQo+
PiByZWNlaXZlIGVtYWlsIG9uIHRoZSBiYXNpcyBvZiB0aGUgdGVybXMgc2V0IG91dCBhdDoNCj4+
IGh0dHA6Ly93d3cudGlkLmVzL0VTL1BBR0lOQVMvZGlzY2xhaW1lci5hc3B4DQo+DQo+X19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj50Y210ZiBtYWlsaW5n
IGxpc3QNCj50Y210ZkBpZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vdGNtdGYNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQpFc3Rl
IG1lbnNhamUgc2UgZGlyaWdlIGV4Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRhcmlvLiBQdWVk
ZSBjb25zdWx0YXIgbnVlc3RyYSBwb2zDrXRpY2EgZGUgZW52w61vIHkgcmVjZXBjacOzbiBkZSBj
b3JyZW8gZWxlY3Ryw7NuaWNvIGVuIGVsIGVubGFjZSBzaXR1YWRvIG3DoXMgYWJham8uDQpUaGlz
IG1lc3NhZ2UgaXMgaW50ZW5kZWQgZXhjbHVzaXZlbHkgZm9yIGl0cyBhZGRyZXNzZWUuIFdlIG9u
bHkgc2VuZCBhbmQgcmVjZWl2ZSBlbWFpbCBvbiB0aGUgYmFzaXMgb2YgdGhlIHRlcm1zIHNldCBv
dXQgYXQ6DQpodHRwOi8vd3d3LnRpZC5lcy9FUy9QQUdJTkFTL2Rpc2NsYWltZXIuYXNweA0K

From fpb@tid.es  Thu Jan 17 01:07:39 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B01C21F88A5; Thu, 17 Jan 2013 01:07:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[AWL=0.033,  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 4X36FUFS-BsF; Thu, 17 Jan 2013 01:07:37 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id B556221F8839; Thu, 17 Jan 2013 01:07:33 -0800 (PST)
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 <0MGR008PIIODEV@tid.hi.inet>; Thu, 17 Jan 2013 10:07:32 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id AA.DA.02896.35FB7F05; Thu, 17 Jan 2013 10:07:31 +0100 (CET)
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 <0MGR008Q0IOJEV@tid.hi.inet>; Thu, 17 Jan 2013 10:07:31 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.165]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.004; Thu, 17 Jan 2013 10:04:22 +0100
Date: Thu, 17 Jan 2013 09:07:30 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <A3179A2C9AAEE647BE70AC4C7881D5FB0177608D@sluga.fer.hr>
X-Originating-IP: [10.95.64.115]
To: =?windows-1250?Q?Mirko_Su=9Enjevi=E6?= <Mirko.Suznjevic@fer.hr>, "tcmtf@ietf.org" <tcmtf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A2689C99E8@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_lPGdM2ySRFqk6KCoeI6IZw)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
Thread-index: AQHN9JGjt/1wmNKQnUulDvKsi7PhJg==
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4e69-b7f636d000000b50-de-50f7bf5387ae
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGKsWRmVeSWpSXmKPExsXCFe9nqBu8/3uAwbKpCha7Pm9gtDj25i6b A5PHkiU/mQIYo7hsUlJzMstSi/TtErgyrt+cwVSw9xFjRcuDRSwNjJcPMXYxcnJICJhI3G+7 zgxhi0lcuLeerYuRi0NIYBujxPwNE6Ccp4wSb9tBqkCcTYwSs859ZQFpYRFQldhwYi1YO5uA lsTpu6vA4sICBRKdH76wgticAi4Sd199h1qnIPHn3GMWkEEiAt2MEk3vFoAV8Qp4S7zuegll C0r8mHwPbBCzQK7E2jmHmCFscYnm1ptgcUYBWYl38+eD1YsIFErcb5nLBmHrSfzZux3MFgWy 246dYYdYLCCxZM95qD9FJV4+/sc6gVF0FpJ1s5Csm4Vk3SxGDiDbQOLRPm+IsLbEsoWvmSHC +hK3r2VChM0kelrusyArWcDIsYpRrDipKDM9oyQ3MTMn3cBILyNTLzMvtWQTIyQKM3cwLt+p cohRgINRiYf3wNnPAUKsiWXFlbmHGCU5mJREeT/v+R4gxJeUn1KZkVicEV9UmpNafIhRgoNZ SYRXZR9QjjclsbIqtSgfJiXDwaEkwcsCkhIsSk1PrUjLzAGmGpg0EwcnSDsPUHvKXpD24oLE 3OLMdIj8KUZtjv1P2p8zcsyY2POcUYglLz8vVUqc9xJIqQBIaUZpHty0V4ziQGcL8x4AyfIA EyfcnFdAK5iAVmza+xlkRUkiQkqqgXHXjh7Hr33Vfy6YmPqHLI/JrHVQvt0vsE215+CiHyJ/ I1erFO/1+f5/TuHEQv2Mmu6/GpXiE/pPlJxKPqQaeuWw35KTptJm/YFv7B6HKbfmmq3arVDd 6+qmeMruhteFXN8Nva0pksYXYjZdN43bc6lNWsrmslZ3yPVrO8NVDP6zlS/48XHSaSWW4oxE Qy3mouJEAABrbtJZAwAA
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2013 09:07:39 -0000

--Boundary_(ID_lPGdM2ySRFqk6KCoeI6IZw)
Content-type: text/plain; charset=windows-1250
Content-transfer-encoding: quoted-printable

Hi Mirko,

Thank you for considering that. In addition, one more thing: in section 4, =
the sentence "If a policy defining a multiplexing period is used, then the =
average latency added to each packet will be half the multiplexing period."=
 only applies when there is not enough packet rate to fulfill a big packet =
by multiplexing small ones. When  there is a lot of packets to multiplex, i=
n general, multiplexing period will not be reached, so half the multiplexin=
g period will be the maximum/worse average added delay. In general, and whe=
n TCMTF is working fine, average added delay will be lower.
So, I would rewrite that phrase as: "If a policy defining a multiplexing pe=
riod is used, then the average latency added to each packet will be half th=
e time to fulfill a multiplexed one. In the worse case and if the multiplex=
ing period is reached, the average latency added to each packet will be hal=
f the multiplexing period".

What do you think?

Regards,

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

From: Mirko Su=9Enjevi=E6 <Mirko.Suznjevic@fer.hr<mailto:Mirko.Suznjevic@fe=
r.hr>>
Date: martes, 15 de enero de 2013 16:48
To: Fernando Pascual Blanco <fpb@tid.es<mailto:fpb@tid.es>>, "tcmtf@ietf.or=
g<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ietf.org>>, "tsvwg@i=
etf.org<mailto:tsvwg@ietf.org>" <tsvwg@ietf.org<mailto:tsvwg@ietf.org>>
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling C=
ompressed Multiplexed Traffic Flows

Hello,
Thanks for all the comments, I will briefly respond to them, and include yo=
ur (as well as previous) corrections in a new version of the draft:

  *   I do not understand the sentence "Therefore, we neither take into acc=
ount services using an approach in which all the calculations are deployed =
in the server, which sends a real-time video stream to the client." in sect=
ion 3.
The meaning of this sentence is that we will not be looking at the cloud ba=
sed gaming services such as OnLive or Gaiki as they are focused on performi=
ng all needed calculations of the gamestate on the server, and sending a ve=
ry =93fat=94 video stream to the client which only renders the video. There=
fore they are not suitable for tcmtf. I will change that in order to be mor=
e clear.

  *   In section 3 (Considered Services), I think it could be also interest=
ing to consider non-real time services candidates to be TCMTF optimized. Fo=
r example services like instant messaging, where the bandwidth saving is th=
e main benefit of the TCMTF optimization, should be somehow mentioned, esta=
blishing a kind of delay upper threshold. Related to that, in section 3, wh=
en talking about web browsing, the sentence "there is no need for policy li=
mitations in TCMTF" could be disappointed, because actually there are limit=
ations (ITU-T_G.1010, 10 seconds for web browsing, as in section 4.1 10 sec=
onds are considered for streaming audio).
At first when we were discussing we decided that it will be focused on real=
-time services, but this can be broadened to others non-real-time. I think =
giving such upper limits has a point, although would we even employ tcmtf i=
n cases  in which we will not have enough data to send a packet in 5 or mor=
e seconds? Is that feasible? Maybe in some sensor networks? Maybe I am just=
 looking it the wrong way, maybe we would have a lot of traffic that needs =
to be packed ASAP!

  *   In section 4, I would change the sentence "A number of flows are mult=
iplexed together before being sent through the Internet." for "A number of =
flows are multiplexed together before being sent through the network.", bec=
ause the network could not be necessary the Internet, I would also adapt Fi=
gure 2.
Ok will be done.

  *   Maybe the creation of a section 4.4 talking about non real time servi=
ces could be considered including last comments (acceptable with the recomm=
endation appearing in the last sentence of the section 4.3 "It should be no=
ted that multiplexing periods of about 1 second can be considered as enough=
 for non real time services (e.g., web browsing and streaming audio).")
Ok, seems sound enough. I will write it and see which format looks better.

  *   Table 1 could be included in a separate section (i.e. Section 4.5) as=
 a summary
Ok.

Thanks again for the feedback!
Cheers!
Mirko

From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
Sent: Tuesday, January 15, 2013 3:42 PM
To: Mirko Su=9Enjevi=E6; tcmtf@ietf.org<mailto:tcmtf@ietf.org>; tsvwg@ietf.=
org<mailto:tsvwg@ietf.org>
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling C=
ompressed Multiplexed Traffic Flows

Hi Mirko,

Some comments to the draft:

  *   In the introduction it says "TCTMF", it is "TCMTF".
  *   I do not understand the sentence "Therefore, we neither take into acc=
ount services using an approach in which all the calculations are deployed =
in the server, which sends a real-time video stream to the client." in sect=
ion 3.
  *   In section 3 (Considered Services), I think it could be also interest=
ing to consider non-real time services candidates to be TCMTF optimized. Fo=
r example services like instant messaging, where the bandwidth saving is th=
e main benefit of the TCMTF optimization, should be somehow mentioned, esta=
blishing a kind of delay upper threshold. Related to that, in section 3, wh=
en talking about web browsing, the sentence "there is no need for policy li=
mitations in TCMTF" could be disappointed, because actually there are limit=
ations (ITU-T_G.1010, 10 seconds for web browsing, as in section 4.1 10 sec=
onds are considered for streaming audio).
  *   In section 4, I would change the sentence "A number of flows are mult=
iplexed together before being sent through the Internet." for "A number of =
flows are multiplexed together before being sent through the network.", bec=
ause the network could not be necessary the Internet, I would also adapt Fi=
gure 2.
  *   Maybe the creation of a section 4.4 talking about non real time servi=
ces could be considered including last comments (acceptable with the recomm=
endation appearing in the last sentence of the section 4.3 "It should be no=
ted that multiplexing periods of about 1 second can be considered as enough=
 for non real time services (e.g., web browsing and streaming audio).")
  *   Table 1 could be included in a separate section (i.e. Section 4.5) as=
 a summary
Hope to help!

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: Mirko Su=9Enjevi=E6 <Mirko.Suznjevic@fer.hr<mailto:Mirko.Suznjevic@fe=
r.hr>>
Date: jueves, 13 de diciembre de 2012 10:06
To: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>, "tsvwg@ietf.org<mailto:tsvwg@ietf.org>" <tsvwg@ietf.org<mailto:ts=
vwg@ietf.org>>
Subject: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compr=
essed Multiplexed Traffic Flows

Hello,

We have just submitted the draft named Maximum Tolerable Delays when using =
Tunneling Compressed Multiplexed Traffic Flows: http://datatracker.ietf.org=
/doc/draft-suznjevic-tsvwg-mtd-tcmtf/

It is an extension of tcmtf http://datatracker.ietf.org/doc/draft-saldana-t=
svwg-tcmtf/. Since a specific list for tcmtf exists (tcmtf@ietf.org<mailto:=
tcmtf@ietf.org>), the idea is to discuss it there.

The draft contains recommendations for TCMTF multiplexing period for differ=
ent real-time services. In order to prevent QoE degradation of real-time se=
rvices using TCMTF, a policy defining  a multiplexing period can be employe=
d. Values of maximum tolerable delays presented in the draft form the base =
of such policy.    The recommendations are presented for real-time network =
services in which TCTMF bandwidth optimization is applicable (i.e., service=
s  which have low payload to header size ratio which results in high protoc=
ol overhead).

Your feedback will be welcome. Thank you.

Sincerely,
Mirko Suznjevic

________________________________

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_lPGdM2ySRFqk6KCoeI6IZw)
Content-id: <625E98CBDF52724AB52B80C1DFA280AC@hi.inet>
Content-type: text/html; charset=windows-1250
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
250">
</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 Mirko,</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Thank =
you for considering that. In addition, one more thing: in section 4, the se=
ntence &quot;If a policy defining a multiplexing period is used, then the a=
verage&nbsp;latency added to each packet will
 be half the multiplexing period.&quot; only applies when there is not enou=
gh packet rate to fulfill a big packet by multiplexing small ones. When &nb=
sp;there is a lot of packets to multiplex, in general, multiplexing period =
will not be reached, so half the multiplexing
 period will be the maximum/worse average added delay. In general, and when=
 TCMTF is working fine, average added delay will be lower.</div>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>So, I =
would rewrite that phrase as: &quot;If a policy defining a multiplexing per=
iod is used, then the average&nbsp;latency added to each packet will be hal=
f the time to fulfill a multiplexed one. In the
 worse case and if the multiplexing period is reached, the average latency =
added to each packet will be half the multiplexing period&quot;.</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>What d=
o you think?</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><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>Mirko Su=9Enjevi=E6 &lt;<a hr=
ef=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>martes, 15 de enero de 2013 1=
6:48<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;, &quot;<a href=3D"mailto:tcmt=
f@ietf.org">tcmtf@ietf.org</a>&quot; &lt;<a href=3D"mailto:tcmtf@ietf.org">=
tcmtf@ietf.org</a>&gt;, &quot;<a href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.=
org</a>&quot;
 &lt;<a href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [tcmtf] Draft: Maximum=
 Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows=
<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}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif"}
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.emailstyle17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.EmailStyle19
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
span.BalloonTextChar
	{font-family:"Tahoma","sans-serif"}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:70.85pt 70.85pt 70.85pt 70.85pt}
div.WordSection1
	{}
ol
	{margin-bottom:0cm}
ul
	{margin-bottom:0cm}
-->
</style>
<div lang=3D"HR">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hello,<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks =
for all the comments, I will briefly respond to them, and include your (as =
well as previous) corrections in a new version of the draft:</span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black"><span lang=3D"EN-US" style=3D=
"font-size:10.5pt">I do not understand the sentence &quot;Therefore, we&nbs=
p;neither take into account services using an approach in which all the&nbs=
p;calculations are deployed in the server, which sends
 a real-time&nbsp;video stream to the client.&quot; in section 3.</span></l=
i></ul>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-US" style=3D"color:#1F49=
7D">The meaning of this sentence is that we will not be looking at the clou=
d based gaming services such as OnLive or Gaiki as they are focused on perf=
orming all needed calculations of the gamestate
 on the server, and sending a very =93fat=94 video stream to the client whi=
ch only renders the video. Therefore they are not suitable for tcmtf. I wil=
l change that in order to be more clear.</span><span lang=3D"EN-US" style=
=3D"font-size:10.5pt; color:black"></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black"><span lang=3D"EN-US" style=3D=
"font-size:10.5pt">In section 3 (Considered Services), I think it could be =
also interesting to consider non-real time services candidates to be TCMTF =
optimized. For example services like instant
 messaging, where the bandwidth saving is the main benefit of the TCMTF opt=
imization, should be somehow mentioned, establishing a kind of delay upper =
threshold. Related to that, in section 3, when talking about web browsing, =
the sentence &quot;there is no need for
 policy&nbsp;limitations in TCMTF&quot; could be&nbsp;disappointed, because=
 actually there are limitations (ITU-T_G.1010,&nbsp;10 seconds for web brow=
sing, as in section 4.1 10 seconds are considered for streaming audio).</sp=
an></li></ul>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-US" style=3D"color:#1F49=
7D">At first when we were discussing we decided that it will be focused on =
real-time services, but this can be broadened to others non-real-time. I th=
ink giving such upper limits has a point,
 although would we even employ tcmtf in cases &nbsp;in which we will not ha=
ve enough data to send a packet in 5 or more seconds? Is that feasible? May=
be in some sensor networks? Maybe I am just looking it the wrong way, maybe=
 we would have a lot of traffic that
 needs to be packed ASAP!</span><span lang=3D"EN-US" style=3D"font-size:10.=
5pt; color:black"></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black"><span lang=3D"EN-US" style=3D=
"font-size:10.5pt">In section 4, I would change the sentence &quot;A number=
 of flows are multiplexed&nbsp;together before being sent through the Inter=
net.&quot; for &quot;A number of flows are multiplexed&nbsp;together
 before being sent through the network.&quot;, because the network could no=
t be necessary the Internet, I would also adapt Figure 2.</span></li></ul>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-US" style=3D"color:#1F49=
7D">Ok will be done.</span><span lang=3D"EN-US" style=3D"font-size:10.5pt; =
color:black"></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D""><span lang=3D"EN-US" style=3D"font-size:=
10.5pt; color:black">Maybe the creation of a section 4.4 talking about non =
real time services could be considered including last comments (acceptable =
with the recommendation appearing in the
 last sentence of the section 4.3 &quot;</span><span lang=3D"EN-US">It shou=
ld be noted&nbsp;that multiplexing periods of about 1 second can be conside=
red as&nbsp;enough for non real time services (e.g., web browsing and strea=
ming&nbsp;audio).&quot;)</span><span lang=3D"EN-US" style=3D"font-size:12pt=
; font-family:'Times New Roman',serif"></span></li></ul>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-US" style=3D"color:#1F49=
7D">Ok, seems sound enough. I will write it and see which format looks bett=
er.</span><span lang=3D"EN-US" style=3D"font-size:12pt; font-family:'Times =
New Roman',serif"></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D""><span lang=3D"EN-US">Table 1 could be in=
cluded in a separate section (i.e.&nbsp;Section 4.5) as a summary</span></l=
i></ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Ok.</sp=
an></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 =
again for the feedback!</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Cheers!=
<br>
Mirko</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0c=
m 0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10pt; fon=
t-family:Tahoma,sans-serif">From:</span></b><span lang=3D"EN-US" style=3D"f=
ont-size:10pt; font-family:Tahoma,sans-serif"> FERNANDO PASCUAL BLANCO [<a =
href=3D"mailto:fpb@tid.es">mailto:fpb@tid.es</a>]
<br>
<b>Sent:</b> Tuesday, January 15, 2013 3:42 PM<br>
<b>To:</b> Mirko Su=9Enjevi=E6; <a href=3D"mailto:tcmtf@ietf.org">tcmtf@iet=
f.org</a>; <a href=3D"mailto:tsvwg@ietf.org">
tsvwg@ietf.org</a><br>
<b>Subject:</b> Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunn=
eling Compressed Multiplexed Traffic Flows</span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">Hi Mirko,</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">Some comments to the draft:</span></p>
</div>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black"><span lang=3D"EN-US" style=3D=
"font-size:10.5pt">In the introduction it says &quot;TCTMF&quot;, it is &qu=
ot;TCMTF&quot;.</span></li><li class=3D"MsoNormal" style=3D"color:black"><s=
pan lang=3D"EN-US" style=3D"font-size:10.5pt">I do not understand the sente=
nce &quot;Therefore, we&nbsp;neither take into account services using an ap=
proach in which all the&nbsp;calculations are deployed in the server, which=
 sends
 a real-time&nbsp;video stream to the client.&quot; in section 3.</span></l=
i><li class=3D"MsoNormal" style=3D"color:black"><span lang=3D"EN-US" style=
=3D"font-size:10.5pt">In section 3 (Considered Services), I think it could =
be also interesting to consider non-real time services candidates to be TCM=
TF optimized. For example services like instant
 messaging, where the bandwidth saving is the main benefit of the TCMTF opt=
imization, should be somehow mentioned, establishing a kind of delay upper =
threshold. Related to that, in section 3, when talking about web browsing, =
the sentence &quot;there is no need for
 policy&nbsp;limitations in TCMTF&quot; could be&nbsp;disappointed, because=
 actually there are limitations (ITU-T_G.1010,&nbsp;10 seconds for web brow=
sing, as in section 4.1 10 seconds are considered for streaming audio).</sp=
an></li><li class=3D"MsoNormal" style=3D"color:black"><span lang=3D"EN-US" =
style=3D"font-size:10.5pt">In section 4, I would change the sentence &quot;=
A number of flows are multiplexed&nbsp;together before being sent through t=
he Internet.&quot; for &quot;A number of flows are multiplexed&nbsp;togethe=
r
 before being sent through the network.&quot;, because the network could no=
t be necessary the Internet, I would also adapt Figure 2.</span></li><li cl=
ass=3D"MsoNormal" style=3D""><span lang=3D"EN-US" style=3D"font-size:10.5pt=
; color:black">Maybe the creation of a section 4.4 talking about non real t=
ime services could be considered including last comments (acceptable with t=
he recommendation appearing in the
 last sentence of the section 4.3 &quot;</span><span lang=3D"EN-US">It shou=
ld be noted&nbsp;that multiplexing periods of about 1 second can be conside=
red as&nbsp;enough for non real time services (e.g., web browsing and strea=
ming&nbsp;audio).&quot;)</span><span lang=3D"EN-US" style=3D"font-size:12pt=
; font-family:'Times New Roman',serif"></span></li><li class=3D"MsoNormal" =
style=3D""><span lang=3D"EN-US">Table 1 could be included in a separate sec=
tion (i.e.&nbsp;Section 4.5) as a summary</span></li></ul>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hope to help!</span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">Regards,</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">Fernando Pascual Blanco</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">Telef=F3nica Global Resources</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">Network Automation and Dynamization</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">TECHNOLOGY PEOPLE GROUP</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">F &#43;34913128779</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">M &#43;34682005168</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black"><a href=3D"mailto:fpb@tid.es">fpb@tid.es</a></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r: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 lang=3D"EN-US" style=3D"color:black">From: =
</span></b><span lang=3D"EN-US" style=3D"color:black">Mirko Su=9Enjevi=E6 &=
lt;<a href=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt;=
<br>
<b>Date: </b>jueves, 13 de diciembre de 2012 10:06<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;, &quot;<a hre=
f=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:=
tsvwg@ietf.org">tsvwg@ietf.org</a>&gt;<br>
<b>Subject: </b>[tcmtf] Draft: Maximum Tolerable Delays when using Tunnelin=
g Compressed Multiplexed Traffic Flows</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; colo=
r:black">&nbsp;</span></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">Hello,</s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">We have j=
ust submitted the draft named Maximum Tolerable Delays when using Tunneling=
 Compressed Multiplexed Traffic Flows:
<a href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/=
">http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">It is an =
extension of tcmtf
<a href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http=
://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a>. Since a specifi=
c list for tcmtf exists (<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</=
a>), the idea is to discuss it there.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">The draft=
 contains recommendations for TCMTF multiplexing period for different real-=
time services. In order to prevent QoE degradation of real-time services us=
ing TCMTF, a policy defining&nbsp; a multiplexing
 period can be employed. Values of maximum tolerable delays presented in th=
e draft form the base of such policy.&nbsp;&nbsp;&nbsp; The recommendations=
 are presented for real-time network services in which TCTMF bandwidth opti=
mization is applicable (i.e., services&nbsp; which have
 low payload to header size ratio which results in high protocol overhead).=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">&nbsp;</s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">Your feed=
back will be welcome. Thank you.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black"><br>
Sincerely,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:black">Mirko Suz=
njevic</span></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:12pt; font-f=
amily:'Times New Roman',serif">&nbsp;</span></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 lang=3D"EN-US" style=3D"font-size:12pt; font-family:'Times New Roman',seri=
f">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:7.5pt; font-=
family:Arial,sans-serif; color:gray"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span lang=3D"EN-US" style=3D"font-siz=
e:12pt; font-family:'Times New Roman',serif"></span></p>
</div>
</div>
</div>
</span><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_lPGdM2ySRFqk6KCoeI6IZw)--

From jsaldana@unizar.es  Thu Jan 17 04:17:13 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2B2221F86AF for <tcmtf@ietfa.amsl.com>; Thu, 17 Jan 2013 04:17:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.417
X-Spam-Level: 
X-Spam-Status: No, score=-6.417 tagged_above=-999 required=5 tests=[AWL=-0.118, 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 rcsGnKMGMVsX for <tcmtf@ietfa.amsl.com>; Thu, 17 Jan 2013 04:17:10 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 1E27621F8692 for <tcmtf@ietf.org>; Thu, 17 Jan 2013 04:17:09 -0800 (PST)
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 r0HCGjtD031859; Thu, 17 Jan 2013 13:16:45 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>, "'Dan Wing'" <dwing@cisco.com>,  "=?utf-8?Q?'Mirko_Su=C5=BEnjevi=C4=87'?=" <Mirko.Suznjevic@fer.hr>, "=?utf-8?Q?'Juli=C3=A1n_Fern=C3=A1ndez_Navajas'?=" <navajas@unizar.es>
References: <007401cdf3d8$3f988ca0$bec9a5e0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A265043B31@EX10-MB1-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A265043B31@EX10-MB1-MAD.hi.inet>
Date: Thu, 17 Jan 2013 13:16:51 +0100
Organization: Universidad de Zaragoza
Message-ID: <009701cdf4ac$8af49750$a0ddc5f0$@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: AQHrQdfsjj6QH3f5LLtKl0m4ijj+d5gSzOAw
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
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, 17 Jan 2013 12:17:13 -0000

Fernando,

So you may have this case:
- your multiplexing delay limit is 50 ms
- you have a lot of flows to multiplex, so perhaps the time between =
multiplexed packets will be 5 ms
- you detect an increase in RTT
- the system reacts and reduces multiplexing period
- in fact, the reduction doesn't matter until the period is reduced to =
less than 5 ms

So you only have to make this decision: using tcmtf with 5 ms period or =
not. If RTT is critical you may not be interested on saving bandwidth, =
but on reducing a bit the RTT.

So I think your question is: what happens if the RTT is very big (out of =
limits) and you can save bandwidth using a 5ms multiplexing period?

For example, the maximum RTT for a good quality is 80 ms and your =
network has 120 just now. In this case, perhaps having 125 doesn't =
matter, if you can save bandwidth.

This makes sense, but it is a "extreme" case. However, would it be any =
advantage if OWD is used instead of RTT?

Best regards,

Jose

> -----Mensaje original-----
> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> Enviado el: mi=C3=A9rcoles, 16 de enero de 2013 12:52
> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko Su=C5=BEnjevi=C4=87'; =
'Juli=C3=A1n Fern=C3=A1ndez
> Navajas'
> CC: tcmtf@ietf.org
> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using =
Tunneling
> Compressed Multiplexed Traffic Flows
>=20
> Hi Jose,
>=20
>         You are right, but my point here is:
>=20
>                 Client - Mux - Demux - Server
>=20
>         Imagine that there is enough packets between mux and demux to =
make
> the added delay very small (TCMTF is working very well and the mux has =
not
> to wait the multiplexing period to fulfill a big packet and send it, =
so imagine a
> multiplexing period of 50 ms and a big packet is fulfilled in 5 ms). =
If the RTT
> get increased because a congestion in the way back to the client =
(there is no
> TCMTF optimization) and we decrease the multiplexing period (even in =
the
> extreme we can disable the TCMTF optimization) the high RTT will =
remain.
> Even if the TCMTF optimization was helping in the client to server =
path,
> disabling it may harm. Do you think that scenario would be possible?
>=20
>         So I=C2=B4m not sure about that, I think we need more opinions =
here.
>=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 16/01/13 11:57, "Jose Saldana" <jsaldana@unizar.es> wrote:
>=20
> >My two cents:
> >
> >In games and in VoIP the really important thing is RTT:
> >
> >- Games always measure the RTT (gamers talk about the "ping"): the
> >important thing is the delay from a player action to the server
> >reaction arriving to the player's machine.
> >- In VoIP I think it is the same: what matters is the RTT, in order =
to
> >grant interactivity and avoiding cross-talk.
> >
> >In addition, RTT is easier to measure than OWD, since you don't need
> >synchronization.
> >
> >And regarding Two-way TCMTF, I think we have to think about TCMTF as
> >one-way. Otherwise, things would become very complicated. Some
> services
> >have very different client-server and server-client traffic patterns
> >(e.g. games). In addition, sometimes the two flows can follow =
different
> >network paths. I think once we talked about a network provider using =
a
> >number of ISPs.
> >
> >However, using RTT for tuning a one-way TCMTF may not be bad... or is
> >it bad? Any other thoughts?
> >
> >BR,
> >
> >Jose
> >
> >> -----Mensaje original-----
> >> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]  Enviado el:
> martes,
> >>15 de enero de 2013 18:04
> >> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko Su=C5=BEnjevi=C4=87'; =
Juli=C3=A1n
> >>Fern=C3=A1ndez  Navajas
> >> CC: tcmtf@ietf.org
> >> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
> >>Tunneling  Compressed Multiplexed Traffic Flows
> >>
> >> Hi all,
> >>
> >>         To re-open that issue, I would suggest that given that the
> >>delay is so  sensitive in real time services, we need to find a
> >>consensus here.
> >>
> >>         My opinion is that to apply the first possibility (the =
static
> >>multiplexing
> >> period) we need to suppose that the network conditions are really
> >>bad, to be  protected when the network congestion arises. In that
> >>case, the application  of the TCMTF optimization will not be =
optimal,
> >>so that would be the less  preferred option, but easier to implement
> >>and maintain over the time.
> >>
> >>         On the other hand, the second possibility would be the
> >>preferred. It is  easy to know the delay between the mux and the =
demux
> >>but most of the  times will not be enough unless mux and demux were
> >>really near from the  client and the server respectively. I agree =
with
> >>Jose in the possibility of snoop  RTCP packets in order to adapt the
> >>multiplexing period when multiplexing  RTP packets (and RTCP is
> >>available). Talking about RTT, I=C2=B4m not sure if RTT  would be =
useful
> >>given that the multiplexing period only affect the one way  delay
> >>(OWD). Imagine the following scenario:
> >>         - Client - Mux/Demux - Demux/Mux - Server (two ways TCMTF,
> >>TWTCMTF :P)
> >>         - The OWD from server to client get increased
> >>         - The OWD from client to server remains equal
> >>         - Should we use a lower multiplexing period in the client =
to
> >>server  direction? I don=C2=B4t think so=E2=80=A6 because we should =
use a lower
> >>multiplexing  period in the other direction.
> >>
> >>         My point is that the multiplexing period should only be
> >>affected by the  OWD and not by the RTT (or it may be application
> >>dependent). How to  calculate the OWD? I=C2=B4ve been reading =
something
> >>about OWAMP and it  seems that an specific software has to be
> >>implemented in the client/server  side.
> >> Can we assume that? Unfortunately I cannot contribute so much =
here=E2=80=A6
> >>         It is possible that for certain services the static (and
> >>worst
> >>case)
> >> multiplexing period would be the better solution.
> >>
> >>         What do you think?
> >>
> >> Regards,
> >>
> >> Fernando Pascual Blanco
> >> Telef=C3=B3nica Global Resources
> >> Network Automation and Dynamization
> >> TECHNOLOGY PEOPLE GROUP
> >> F +34913128779
> >> M +34682005168
> >> fpb@tid.es
> >>
> >>
> >>
> >>
> >> On 17/12/12 12:25, "Jose Saldana" <jsaldana@unizar.es> wrote:
> >>
> >> >Hi all,
> >> >
> >> >Julian and I have been discussing about this. Some ideas have =
arisen.
> >> >This is the summary.
> >> >
> >> >This would be the scheme of the system, including mux and demux:
> >> >
> >> >Real-time application ------- mux -------- internet --------- =
demux
> >> >-------
> >> >server
> >> >
> >> >
> >> >I think perhaps the draft could say something like:
> >> >
> >> >When setting the multiplexing period, there are two possibilities:
> >> >
> >> >1.- Static / permanent: At system setup time, network delays are
> >> >measured, and a multiplexing period is selected and set in the
> >>multiplexer.
> >> >
> >> >2.- Dynamic: A mechanism is used so as to adapt to the evolution =
of
> >> >network delays. In this case, different mechanisms can be used in
> >> >order to obtain periodical end-to-end network delay estimations,
> >> >which would be useful in order to set the multiplexing period:
> >> >
> >> >- If the traffic is RTP, then RTCP packets containing the =
estimation
> >> >could be analyzed in order to extract these values, as Dan =
suggests.
> >> >The question
> >> >is: would that packets travel through the multiplexer?
> >> >- If the traffic is TCP, perhaps something similar to the RTT
> >> >estimation of TCP could be useful.
> >> >- If the traffic is UDP, should the mux use something like OWAMP
> >> >(http://tools.ietf.org/html/rfc4656) in order to calculate two
> >> >delays (application to mux, and mux to server) and calculate the =
sum?
> >> >
> >> >
> >> >I think the draft is only supposed to report the maximum delays
> >> >normally considered acceptable. Perhaps the additional mechanisms
> >> >for calculating the RTT could just be suggested.
> >> >
> >> >What do you think?
> >> >
> >> >Jose
> >> >
> >> >> -----Mensaje original-----
> >> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> >> nombre de Dan Wing Enviado el: viernes, 14 de diciembre de 2012
> >> >> 18:33
> >> >> Para: jsaldana@unizar.es; 'Mirko Su=C5=BEnjevi=C4=87'
> >> >> CC: tcmtf@ietf.org
> >> >> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
> >> >> Tunneling Compressed Multiplexed Traffic Flows
> >> >>
> >> >> > -----Original Message-----
> >> >> > From: Jose Saldana [mailto:jsaldana@unizar.es]
> >> >> > Sent: Friday, December 14, 2012 2:58 AM
> >> >> > To: 'Dan Wing'; 'Mirko Su=C5=BEnjevi=C4=87'
> >> >> > Cc: tcmtf@ietf.org
> >> >> > Subject: RE: [tcmtf] Draft: Maximum Tolerable Delays when =
using
> >> >> > Tunneling Compressed Multiplexed Traffic Flows
> >> >> >
> >> >> > Dan,
> >> >> >
> >> >> > Regarding the use of the maximum delay, some days ago we
> >> >> > discussed about
> >> >> > it:
> >> >> > the actual OWD of the network should be measured (or =
estimated)
> >> >> > in order to know the maximum multiplexing period we can set.
> >> >> >
> >> >> > We may have this formula, if thinking one-way:
> >> >> >
> >> >> > OWD  + Mux period/2  < tolerable_OWD
> >> >> >
> >> >> > If we think RTT:
> >> >> >
> >> >> > OWD + Mux period/2 + OWD back < 2*tolerable_OWD
> >> >> >
> >> >> > I don't know if we should include a mechanism for estimating =
OWD
> >> >> > in tcmtf. I think this is more an implementation problem, =
which
> >> >> > may be already solved.
> >> >>
> >> >> Yes, it's already solved end-to-end:  RTP with RTCP feedback
> >> >> allows determining one way delay.
> >> >>
> >> >> But if something in the middle is multiplexing several packets
> >> >> together,
> >> >we
> >> >> don't want it to add too much delay.  That thing in the middle
> >> >>won't necessarily know the one way delay seen by the endpoints,
> >> >>unless it analyzes the RTP and RTCP.  There are devices that do
> >> >>that on the market,  mostly to diagnose where networks are =
causing
> >> >>loss/delay with RTP flows.
> >> >>
> >> >>
> >> >> > Another option is using some typical values, e.g. from
> >> >> > http://ipnetwork.bgtmo.ip.att.net/pws/global_network_avgs.html
> >> >> >
> >> >> > The draft includes some preliminary/recommended values for the
> >> >> > Multiplexing Period. Is this interesting? Should we put the
> >> >> > formula instead?
> >> >>
> >> >> It's probably sufficient as-is.
> >> >>
> >> >> -d
> >> >>
> >> >> > Mirko, another question: in online games, players usually talk
> >> >> > about the "ping", and I think it means RTT. Don't you think it
> >> >> > would be better to define a RTT limit instead of a OWD one in
> >> >> > that
> >>case?
> >> >> >
> >> >> > What do you think?
> >> >> >
> >> >> > Jose
> >> >> >
> >> >> > > -----Mensaje original-----
> >> >> > > De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] =
En
> >> >> > > nombre de Dan Wing Enviado el: jueves, 13 de diciembre de =
2012
> >> >> > > 17:07
> >> >> > > Para: 'Mirko Su=C5=BEnjevi=C4=87'; tcmtf@ietf.org
> >> >> > > Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when =
using
> >> >> > > Tunneling Compressed Multiplexed Traffic Flows
> >> >> > >
> >> >> > > > -----Original Message-----
> >> >> > > > From: tcmtf-bounces@ietf.org =
[mailto:tcmtf-bounces@ietf.org]
> >> >> > > > On Behalf Of Mirko Su=C5=BEnjevic
> >> >> > > > Sent: Thursday, December 13, 2012 1:07 AM
> >> >> > > > To: tcmtf@ietf.org; tsvwg@ietf.org
> >> >> > > > Subject: [tcmtf] Draft: Maximum Tolerable Delays when =
using
> >> >> > > > Tunneling Compressed Multiplexed Traffic Flows
> >> >> > > >
> >> >> > > > Hello,
> >> >> > > >
> >> >> > > >
> >> >> > > >
> >> >> > > > We have just submitted the draft named Maximum Tolerable
> >> >> > > > Delays when using Tunneling Compressed Multiplexed Traffic
> Flows:
> >> >> > > > =
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tc
> >> >> > > > mtf
> >> >> > > > /
> >> >> > >
> >> >> > > The suggested 400ms for interactive voice is at least 2x too
> >>high.
> >> >> > > I
> >> >> > expect
> >> >> > > that number does not include the playout jitter buffer =
(which
> >> >> > > is variable,
> >> >> > but
> >> >> > > usually a few samples, so 40-80ms).  200ms end-to-end is the
> >> >> > > higher end,
> >> >> > and
> >> >> > > that includes jitter buffer, codec processing, and so on.
> >> >> > >
> >> >> > > But, more importantly:  it seems valuable for endpoints to
> >> >> > > signal their maximum delay somehow.  Or would the TCMTF
> >> >> > > function
> >> >> determine
> >> >> > > the maximum delay, using some heuristic?
> >> >> > >
> >> >> > > How does the TCMTF function determine how much of that
> >> >> > > 'tolerable latency' budget it can consume?
> >> >> > >
> >> >> > > -d
> >> >> > >
> >> >> > >
> >> >> > > > It is an extension of tcmtf
> >> >> > > > http://datatracker.ietf.org/doc/draft-
> >> >> > > > saldana-tsvwg-tcmtf/. Since a specific list for tcmtf =
exists
> >> >> > > > (tcmtf@ietf.org), the idea is to discuss it there.
> >> >> > > >
> >> >> > > >
> >> >> > > >
> >> >> > > > The draft contains recommendations for TCMTF multiplexing
> >> >> > > > period for different real-time services. In order to =
prevent
> >> >> > > > QoE degradation of real-time services using TCMTF, a =
policy
> >> >> > > > defining a multiplexing period can be employed. Values of
> >> >> > > > maximum tolerable delays presented in
> >> >> > > the
> >> >> > > > draft form the base of such policy.    The recommendations =
are
> >> >> > presented
> >> >> > > > for real-time network services in which TCTMF bandwidth
> >> >> > > > optimization is applicable (i.e., services  which have low
> >> >> > > > payload to header size ratio which results in high =
protocol
> >> overhead).
> >> >> > > >
> >> >> > > >
> >> >> > > >
> >> >> > > > Your feedback will be welcome. Thank you.
> >> >> > > >
> >> >> > > >
> >> >> > > > Sincerely,
> >> >> > > >
> >> >> > > > Mirko Suznjevic
> >> >> > >
> >> >> > >
> >> >> > > _______________________________________________
> >> >> > > 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 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
> ________________________________
>=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 fpb@tid.es  Thu Jan 17 05:39:02 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E70C521F860A for <tcmtf@ietfa.amsl.com>; Thu, 17 Jan 2013 05:39:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.268
X-Spam-Level: 
X-Spam-Status: No, score=-6.268 tagged_above=-999 required=5 tests=[AWL=0.031,  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 HBZC+jzo6jnx for <tcmtf@ietfa.amsl.com>; Thu, 17 Jan 2013 05:39:01 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 0744221F85D4 for <tcmtf@ietf.org>; Thu, 17 Jan 2013 05:38:59 -0800 (PST)
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 <0MGR00C9PV8TDX@tid.hi.inet> for tcmtf@ietf.org; Thu, 17 Jan 2013 14:38:58 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id E0.63.02896.1FEF7F05; Thu, 17 Jan 2013 14:38:57 +0100 (CET)
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 <0MGR00CALV8WDX@tid.hi.inet> for tcmtf@ietf.org; Thu, 17 Jan 2013 14:38:57 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.165]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0328.009; Thu, 17 Jan 2013 14:38:55 +0100
Date: Thu, 17 Jan 2013 13:38:53 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <009701cdf4ac$8af49750$a0ddc5f0$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, 'Dan Wing' <dwing@cisco.com>, =?utf-8?B?J01pcmtvIFN1xb5uamV2acSHJw==?= <Mirko.Suznjevic@fer.hr>, =?utf-8?B?J0p1bGnDoW4gRmVybsOhbmRleiBOYXZhamFzJw==?= <navajas@unizar.es>
Message-id: <F5EDC35DF914C1428C28E149F10463A2689D3F12@EX10-MB2-MAD.hi.inet>
Content-id: <E4B5FD142FC64241AC9F32836A2098A7@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
Thread-topic: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
Thread-index: AQHN899xAC2KhZu2o0+MbWmxdLVrNphNYIyAgAAntoA=
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4e69-b7f636d000000b50-35-50f7fef121a3
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPKsWRmVeSWpSXmKPExsXCFe9nqPvx3/cAg55lhha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxstF11gL1u1grJi/taCB8cJmxi5GTg4JAROJV7MuQNliEhfu rWfrYuTiEBLYxihxu+8cM4Tzg1Hi6YmfrBDOTKDMklVMIC0sAqoST/68ALPZBLQkTt9dxQJi CwsUSHR++MIKYnMKWEjsOfKUFWKFgsSfc49ZQAaJCNxhlDj9ZCXQPg4OZqBB874pgtTwCnhL /Lm5iBnEZhYwk2jZsIcFIi4o8WPyPRaIcnWJKVNyIUrEJZpbb7JA2IoS0xY1gH3DCPTN91Nr wE4TESiUuN8ylw3CtpJYsOQ02DmiAnoSbcfOsEOcJiCxZM95ZghbVOLl43+sExglZiG5YhaS K2YhXDELyRWzkFyxgJF1FaNYcVJRZnpGSW5iZk66gZFeRqZeZl5qySZGSNxl7mBcvlPlEKMA B6MSD++Bs58DhFgTy4orcw8xSnIwKYnynv7zPUCILyk/pTIjsTgjvqg0J7X4EKMEB7OSCO+H D0A53pTEyqrUonyYlAwHh5IE7+6/QCnBotT01Iq0zBxgcoFJM3FwgrTzALUfBanhLS5IzC3O TIfIn2LU5tj/pP05I0fLge7njEIsefl5qVLivItBSgVASjNK8+CmvWIUBzpbmHcDSJYHmCrh 5rwCWsEEtELkItiKkkSElFQDo+nOeC6TVptukZ7lu2//uidlH+P09FvqLZ3VMjMmX/xaeCvy 755wS7eAR3lbuM+Z2pq5zuWY/f1GktFfyXoBVt619qpPf3ydNfm+7nGey5Oq/m6LS3l/6urx g9r5ayrOtZWWPjuyfv8ljdmzZ+oLSE0tmnRYWW5V47q+jMQc5dZH/iU8LoIbNiqxFGckGmox FxUnAgBz9deuUgMAAA==
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2013 13:39:03 -0000

Sm9zZSwNCg0KICAgICAgICBMZXTCtHMgc2F5IHRoYXQgcGxheWluZyB3aXRoIHRoZSBPV0QgeW91
IGhhdmUgbW9yZSBncmFudWxhcml0eSBpbiBvcmRlciB0bw0Ka25vdyBpbiB3aGljaCBkaXJlY3Rp
b24geW91IG5lZWQgdG8gcmVkdWNlIHRoZSBkZWxheSBieSByZWR1Y2luZyB0aGUNCm11bHRpcGxl
eGluZyBkZWxheS4gQnV0IHBlb3BsZSB3aXRoIG1vcmUga25vd2xlZGdlIGFib3V0IG9ubGluZSBn
YW1lcyB3aWxsDQpwcm92aWRlIHVzIG1vcmUgaW5mb3JtYXRpb24gZm9yIHN1cmUuDQoNClJlZ2Fy
ZHMsDQoNCkZlcm5hbmRvIFBhc2N1YWwgQmxhbmNvDQpUZWxlZsOzbmljYSBHbG9iYWwgUmVzb3Vy
Y2VzDQpOZXR3b3JrIEF1dG9tYXRpb24gYW5kIER5bmFtaXphdGlvbg0KVEVDSE5PTE9HWSBQRU9Q
TEUgR1JPVVANCkYgKzM0OTEzMTI4Nzc5DQpNICszNDY4MjAwNTE2OA0KZnBiQHRpZC5lcw0KDQoN
Cg0KDQpPbiAxNy8wMS8xMyAxMzoxNiwgIkpvc2UgU2FsZGFuYSIgPGpzYWxkYW5hQHVuaXphci5l
cz4gd3JvdGU6DQoNCj5GZXJuYW5kbywNCj4NCj5TbyB5b3UgbWF5IGhhdmUgdGhpcyBjYXNlOg0K
Pi0geW91ciBtdWx0aXBsZXhpbmcgZGVsYXkgbGltaXQgaXMgNTAgbXMNCj4tIHlvdSBoYXZlIGEg
bG90IG9mIGZsb3dzIHRvIG11bHRpcGxleCwgc28gcGVyaGFwcyB0aGUgdGltZSBiZXR3ZWVuDQo+
bXVsdGlwbGV4ZWQgcGFja2V0cyB3aWxsIGJlIDUgbXMNCj4tIHlvdSBkZXRlY3QgYW4gaW5jcmVh
c2UgaW4gUlRUDQo+LSB0aGUgc3lzdGVtIHJlYWN0cyBhbmQgcmVkdWNlcyBtdWx0aXBsZXhpbmcg
cGVyaW9kDQo+LSBpbiBmYWN0LCB0aGUgcmVkdWN0aW9uIGRvZXNuJ3QgbWF0dGVyIHVudGlsIHRo
ZSBwZXJpb2QgaXMgcmVkdWNlZCB0bw0KPmxlc3MgdGhhbiA1IG1zDQo+DQo+U28geW91IG9ubHkg
aGF2ZSB0byBtYWtlIHRoaXMgZGVjaXNpb246IHVzaW5nIHRjbXRmIHdpdGggNSBtcyBwZXJpb2Qg
b3INCj5ub3QuIElmIFJUVCBpcyBjcml0aWNhbCB5b3UgbWF5IG5vdCBiZSBpbnRlcmVzdGVkIG9u
IHNhdmluZyBiYW5kd2lkdGgsDQo+YnV0IG9uIHJlZHVjaW5nIGEgYml0IHRoZSBSVFQuDQo+DQo+
U28gSSB0aGluayB5b3VyIHF1ZXN0aW9uIGlzOiB3aGF0IGhhcHBlbnMgaWYgdGhlIFJUVCBpcyB2
ZXJ5IGJpZyAob3V0IG9mDQo+bGltaXRzKSBhbmQgeW91IGNhbiBzYXZlIGJhbmR3aWR0aCB1c2lu
ZyBhIDVtcyBtdWx0aXBsZXhpbmcgcGVyaW9kPw0KPg0KPkZvciBleGFtcGxlLCB0aGUgbWF4aW11
bSBSVFQgZm9yIGEgZ29vZCBxdWFsaXR5IGlzIDgwIG1zIGFuZCB5b3VyIG5ldHdvcmsNCj5oYXMg
MTIwIGp1c3Qgbm93LiBJbiB0aGlzIGNhc2UsIHBlcmhhcHMgaGF2aW5nIDEyNSBkb2Vzbid0IG1h
dHRlciwgaWYgeW91DQo+Y2FuIHNhdmUgYmFuZHdpZHRoLg0KPg0KPlRoaXMgbWFrZXMgc2Vuc2Us
IGJ1dCBpdCBpcyBhICJleHRyZW1lIiBjYXNlLiBIb3dldmVyLCB3b3VsZCBpdCBiZSBhbnkNCj5h
ZHZhbnRhZ2UgaWYgT1dEIGlzIHVzZWQgaW5zdGVhZCBvZiBSVFQ/DQo+DQo+QmVzdCByZWdhcmRz
LA0KPg0KPkpvc2UNCj4NCj4+IC0tLS0tTWVuc2FqZSBvcmlnaW5hbC0tLS0tDQo+PiBEZTogRkVS
TkFORE8gUEFTQ1VBTCBCTEFOQ08gW21haWx0bzpmcGJAdGlkLmVzXQ0KPj4gRW52aWFkbyBlbDog
bWnDqXJjb2xlcywgMTYgZGUgZW5lcm8gZGUgMjAxMyAxMjo1Mg0KPj4gUGFyYToganNhbGRhbmFA
dW5pemFyLmVzOyAnRGFuIFdpbmcnOyAnTWlya28gU3XFvm5qZXZpxIcnOyAnSnVsacOhbg0KPj5G
ZXJuw6FuZGV6DQo+PiBOYXZhamFzJw0KPj4gQ0M6IHRjbXRmQGlldGYub3JnDQo+PiBBc3VudG86
IFJlOiBbdGNtdGZdIERyYWZ0OiBNYXhpbXVtIFRvbGVyYWJsZSBEZWxheXMgd2hlbiB1c2luZyBU
dW5uZWxpbmcNCj4+IENvbXByZXNzZWQgTXVsdGlwbGV4ZWQgVHJhZmZpYyBGbG93cw0KPj4NCj4+
IEhpIEpvc2UsDQo+Pg0KPj4gICAgICAgICBZb3UgYXJlIHJpZ2h0LCBidXQgbXkgcG9pbnQgaGVy
ZSBpczoNCj4+DQo+PiAgICAgICAgICAgICAgICAgQ2xpZW50IC0gTXV4IC0gRGVtdXggLSBTZXJ2
ZXINCj4+DQo+PiAgICAgICAgIEltYWdpbmUgdGhhdCB0aGVyZSBpcyBlbm91Z2ggcGFja2V0cyBi
ZXR3ZWVuIG11eCBhbmQgZGVtdXggdG8NCj4+bWFrZQ0KPj4gdGhlIGFkZGVkIGRlbGF5IHZlcnkg
c21hbGwgKFRDTVRGIGlzIHdvcmtpbmcgdmVyeSB3ZWxsIGFuZCB0aGUgbXV4IGhhcw0KPj5ub3QN
Cj4+IHRvIHdhaXQgdGhlIG11bHRpcGxleGluZyBwZXJpb2QgdG8gZnVsZmlsbCBhIGJpZyBwYWNr
ZXQgYW5kIHNlbmQgaXQsIHNvDQo+PmltYWdpbmUgYQ0KPj4gbXVsdGlwbGV4aW5nIHBlcmlvZCBv
ZiA1MCBtcyBhbmQgYSBiaWcgcGFja2V0IGlzIGZ1bGZpbGxlZCBpbiA1IG1zKS4gSWYNCj4+dGhl
IFJUVA0KPj4gZ2V0IGluY3JlYXNlZCBiZWNhdXNlIGEgY29uZ2VzdGlvbiBpbiB0aGUgd2F5IGJh
Y2sgdG8gdGhlIGNsaWVudCAodGhlcmUNCj4+aXMgbm8NCj4+IFRDTVRGIG9wdGltaXphdGlvbikg
YW5kIHdlIGRlY3JlYXNlIHRoZSBtdWx0aXBsZXhpbmcgcGVyaW9kIChldmVuIGluIHRoZQ0KPj4g
ZXh0cmVtZSB3ZSBjYW4gZGlzYWJsZSB0aGUgVENNVEYgb3B0aW1pemF0aW9uKSB0aGUgaGlnaCBS
VFQgd2lsbCByZW1haW4uDQo+PiBFdmVuIGlmIHRoZSBUQ01URiBvcHRpbWl6YXRpb24gd2FzIGhl
bHBpbmcgaW4gdGhlIGNsaWVudCB0byBzZXJ2ZXIgcGF0aCwNCj4+IGRpc2FibGluZyBpdCBtYXkg
aGFybS4gRG8geW91IHRoaW5rIHRoYXQgc2NlbmFyaW8gd291bGQgYmUgcG9zc2libGU/DQo+Pg0K
Pj4gICAgICAgICBTbyBJwrRtIG5vdCBzdXJlIGFib3V0IHRoYXQsIEkgdGhpbmsgd2UgbmVlZCBt
b3JlIG9waW5pb25zIGhlcmUuDQo+Pg0KPj4gUmVnYXJkcywNCj4+DQo+PiBGZXJuYW5kbyBQYXNj
dWFsIEJsYW5jbw0KPj4gVGVsZWbDs25pY2EgR2xvYmFsIFJlc291cmNlcw0KPj4gTmV0d29yayBB
dXRvbWF0aW9uIGFuZCBEeW5hbWl6YXRpb24NCj4+IFRFQ0hOT0xPR1kgUEVPUExFIEdST1VQDQo+
PiBGICszNDkxMzEyODc3OQ0KPj4gTSArMzQ2ODIwMDUxNjgNCj4+IGZwYkB0aWQuZXMNCj4+DQo+
Pg0KPj4NCj4+DQo+PiBPbiAxNi8wMS8xMyAxMTo1NywgIkpvc2UgU2FsZGFuYSIgPGpzYWxkYW5h
QHVuaXphci5lcz4gd3JvdGU6DQo+Pg0KPj4gPk15IHR3byBjZW50czoNCj4+ID4NCj4+ID5JbiBn
YW1lcyBhbmQgaW4gVm9JUCB0aGUgcmVhbGx5IGltcG9ydGFudCB0aGluZyBpcyBSVFQ6DQo+PiA+
DQo+PiA+LSBHYW1lcyBhbHdheXMgbWVhc3VyZSB0aGUgUlRUIChnYW1lcnMgdGFsayBhYm91dCB0
aGUgInBpbmciKTogdGhlDQo+PiA+aW1wb3J0YW50IHRoaW5nIGlzIHRoZSBkZWxheSBmcm9tIGEg
cGxheWVyIGFjdGlvbiB0byB0aGUgc2VydmVyDQo+PiA+cmVhY3Rpb24gYXJyaXZpbmcgdG8gdGhl
IHBsYXllcidzIG1hY2hpbmUuDQo+PiA+LSBJbiBWb0lQIEkgdGhpbmsgaXQgaXMgdGhlIHNhbWU6
IHdoYXQgbWF0dGVycyBpcyB0aGUgUlRULCBpbiBvcmRlciB0bw0KPj4gPmdyYW50IGludGVyYWN0
aXZpdHkgYW5kIGF2b2lkaW5nIGNyb3NzLXRhbGsuDQo+PiA+DQo+PiA+SW4gYWRkaXRpb24sIFJU
VCBpcyBlYXNpZXIgdG8gbWVhc3VyZSB0aGFuIE9XRCwgc2luY2UgeW91IGRvbid0IG5lZWQNCj4+
ID5zeW5jaHJvbml6YXRpb24uDQo+PiA+DQo+PiA+QW5kIHJlZ2FyZGluZyBUd28td2F5IFRDTVRG
LCBJIHRoaW5rIHdlIGhhdmUgdG8gdGhpbmsgYWJvdXQgVENNVEYgYXMNCj4+ID5vbmUtd2F5LiBP
dGhlcndpc2UsIHRoaW5ncyB3b3VsZCBiZWNvbWUgdmVyeSBjb21wbGljYXRlZC4gU29tZQ0KPj4g
c2VydmljZXMNCj4+ID5oYXZlIHZlcnkgZGlmZmVyZW50IGNsaWVudC1zZXJ2ZXIgYW5kIHNlcnZl
ci1jbGllbnQgdHJhZmZpYyBwYXR0ZXJucw0KPj4gPihlLmcuIGdhbWVzKS4gSW4gYWRkaXRpb24s
IHNvbWV0aW1lcyB0aGUgdHdvIGZsb3dzIGNhbiBmb2xsb3cgZGlmZmVyZW50DQo+PiA+bmV0d29y
ayBwYXRocy4gSSB0aGluayBvbmNlIHdlIHRhbGtlZCBhYm91dCBhIG5ldHdvcmsgcHJvdmlkZXIg
dXNpbmcgYQ0KPj4gPm51bWJlciBvZiBJU1BzLg0KPj4gPg0KPj4gPkhvd2V2ZXIsIHVzaW5nIFJU
VCBmb3IgdHVuaW5nIGEgb25lLXdheSBUQ01URiBtYXkgbm90IGJlIGJhZC4uLiBvciBpcw0KPj4g
Pml0IGJhZD8gQW55IG90aGVyIHRob3VnaHRzPw0KPj4gPg0KPj4gPkJSLA0KPj4gPg0KPj4gPkpv
c2UNCj4+ID4NCj4+ID4+IC0tLS0tTWVuc2FqZSBvcmlnaW5hbC0tLS0tDQo+PiA+PiBEZTogRkVS
TkFORE8gUEFTQ1VBTCBCTEFOQ08gW21haWx0bzpmcGJAdGlkLmVzXSAgRW52aWFkbyBlbDoNCj4+
IG1hcnRlcywNCj4+ID4+MTUgZGUgZW5lcm8gZGUgMjAxMyAxODowNA0KPj4gPj4gUGFyYToganNh
bGRhbmFAdW5pemFyLmVzOyAnRGFuIFdpbmcnOyAnTWlya28gU3XFvm5qZXZpxIcnOyBKdWxpw6Fu
DQo+PiA+PkZlcm7DoW5kZXogIE5hdmFqYXMNCj4+ID4+IENDOiB0Y210ZkBpZXRmLm9yZw0KPj4g
Pj4gQXN1bnRvOiBSZTogW3RjbXRmXSBEcmFmdDogTWF4aW11bSBUb2xlcmFibGUgRGVsYXlzIHdo
ZW4gdXNpbmcNCj4+ID4+VHVubmVsaW5nICBDb21wcmVzc2VkIE11bHRpcGxleGVkIFRyYWZmaWMg
Rmxvd3MNCj4+ID4+DQo+PiA+PiBIaSBhbGwsDQo+PiA+Pg0KPj4gPj4gICAgICAgICBUbyByZS1v
cGVuIHRoYXQgaXNzdWUsIEkgd291bGQgc3VnZ2VzdCB0aGF0IGdpdmVuIHRoYXQgdGhlDQo+PiA+
PmRlbGF5IGlzIHNvICBzZW5zaXRpdmUgaW4gcmVhbCB0aW1lIHNlcnZpY2VzLCB3ZSBuZWVkIHRv
IGZpbmQgYQ0KPj4gPj5jb25zZW5zdXMgaGVyZS4NCj4+ID4+DQo+PiA+PiAgICAgICAgIE15IG9w
aW5pb24gaXMgdGhhdCB0byBhcHBseSB0aGUgZmlyc3QgcG9zc2liaWxpdHkgKHRoZSBzdGF0aWMN
Cj4+ID4+bXVsdGlwbGV4aW5nDQo+PiA+PiBwZXJpb2QpIHdlIG5lZWQgdG8gc3VwcG9zZSB0aGF0
IHRoZSBuZXR3b3JrIGNvbmRpdGlvbnMgYXJlIHJlYWxseQ0KPj4gPj5iYWQsIHRvIGJlICBwcm90
ZWN0ZWQgd2hlbiB0aGUgbmV0d29yayBjb25nZXN0aW9uIGFyaXNlcy4gSW4gdGhhdA0KPj4gPj5j
YXNlLCB0aGUgYXBwbGljYXRpb24gIG9mIHRoZSBUQ01URiBvcHRpbWl6YXRpb24gd2lsbCBub3Qg
YmUgb3B0aW1hbCwNCj4+ID4+c28gdGhhdCB3b3VsZCBiZSB0aGUgbGVzcyAgcHJlZmVycmVkIG9w
dGlvbiwgYnV0IGVhc2llciB0byBpbXBsZW1lbnQNCj4+ID4+YW5kIG1haW50YWluIG92ZXIgdGhl
IHRpbWUuDQo+PiA+Pg0KPj4gPj4gICAgICAgICBPbiB0aGUgb3RoZXIgaGFuZCwgdGhlIHNlY29u
ZCBwb3NzaWJpbGl0eSB3b3VsZCBiZSB0aGUNCj4+ID4+cHJlZmVycmVkLiBJdCBpcyAgZWFzeSB0
byBrbm93IHRoZSBkZWxheSBiZXR3ZWVuIHRoZSBtdXggYW5kIHRoZSBkZW11eA0KPj4gPj5idXQg
bW9zdCBvZiB0aGUgIHRpbWVzIHdpbGwgbm90IGJlIGVub3VnaCB1bmxlc3MgbXV4IGFuZCBkZW11
eCB3ZXJlDQo+PiA+PnJlYWxseSBuZWFyIGZyb20gdGhlICBjbGllbnQgYW5kIHRoZSBzZXJ2ZXIg
cmVzcGVjdGl2ZWx5LiBJIGFncmVlIHdpdGgNCj4+ID4+Sm9zZSBpbiB0aGUgcG9zc2liaWxpdHkg
b2Ygc25vb3AgIFJUQ1AgcGFja2V0cyBpbiBvcmRlciB0byBhZGFwdCB0aGUNCj4+ID4+bXVsdGlw
bGV4aW5nIHBlcmlvZCB3aGVuIG11bHRpcGxleGluZyAgUlRQIHBhY2tldHMgKGFuZCBSVENQIGlz
DQo+PiA+PmF2YWlsYWJsZSkuIFRhbGtpbmcgYWJvdXQgUlRULCBJwrRtIG5vdCBzdXJlIGlmIFJU
VCAgd291bGQgYmUgdXNlZnVsDQo+PiA+PmdpdmVuIHRoYXQgdGhlIG11bHRpcGxleGluZyBwZXJp
b2Qgb25seSBhZmZlY3QgdGhlIG9uZSB3YXkgIGRlbGF5DQo+PiA+PihPV0QpLiBJbWFnaW5lIHRo
ZSBmb2xsb3dpbmcgc2NlbmFyaW86DQo+PiA+PiAgICAgICAgIC0gQ2xpZW50IC0gTXV4L0RlbXV4
IC0gRGVtdXgvTXV4IC0gU2VydmVyICh0d28gd2F5cyBUQ01URiwNCj4+ID4+VFdUQ01URiA6UCkN
Cj4+ID4+ICAgICAgICAgLSBUaGUgT1dEIGZyb20gc2VydmVyIHRvIGNsaWVudCBnZXQgaW5jcmVh
c2VkDQo+PiA+PiAgICAgICAgIC0gVGhlIE9XRCBmcm9tIGNsaWVudCB0byBzZXJ2ZXIgcmVtYWlu
cyBlcXVhbA0KPj4gPj4gICAgICAgICAtIFNob3VsZCB3ZSB1c2UgYSBsb3dlciBtdWx0aXBsZXhp
bmcgcGVyaW9kIGluIHRoZSBjbGllbnQgdG8NCj4+ID4+c2VydmVyICBkaXJlY3Rpb24/IEkgZG9u
wrR0IHRoaW5rIHNv4oCmIGJlY2F1c2Ugd2Ugc2hvdWxkIHVzZSBhIGxvd2VyDQo+PiA+Pm11bHRp
cGxleGluZyAgcGVyaW9kIGluIHRoZSBvdGhlciBkaXJlY3Rpb24uDQo+PiA+Pg0KPj4gPj4gICAg
ICAgICBNeSBwb2ludCBpcyB0aGF0IHRoZSBtdWx0aXBsZXhpbmcgcGVyaW9kIHNob3VsZCBvbmx5
IGJlDQo+PiA+PmFmZmVjdGVkIGJ5IHRoZSAgT1dEIGFuZCBub3QgYnkgdGhlIFJUVCAob3IgaXQg
bWF5IGJlIGFwcGxpY2F0aW9uDQo+PiA+PmRlcGVuZGVudCkuIEhvdyB0byAgY2FsY3VsYXRlIHRo
ZSBPV0Q/IEnCtHZlIGJlZW4gcmVhZGluZyBzb21ldGhpbmcNCj4+ID4+YWJvdXQgT1dBTVAgYW5k
IGl0ICBzZWVtcyB0aGF0IGFuIHNwZWNpZmljIHNvZnR3YXJlIGhhcyB0byBiZQ0KPj4gPj5pbXBs
ZW1lbnRlZCBpbiB0aGUgY2xpZW50L3NlcnZlciAgc2lkZS4NCj4+ID4+IENhbiB3ZSBhc3N1bWUg
dGhhdD8gVW5mb3J0dW5hdGVseSBJIGNhbm5vdCBjb250cmlidXRlIHNvIG11Y2ggaGVyZeKApg0K
Pj4gPj4gICAgICAgICBJdCBpcyBwb3NzaWJsZSB0aGF0IGZvciBjZXJ0YWluIHNlcnZpY2VzIHRo
ZSBzdGF0aWMgKGFuZA0KPj4gPj53b3JzdA0KPj4gPj5jYXNlKQ0KPj4gPj4gbXVsdGlwbGV4aW5n
IHBlcmlvZCB3b3VsZCBiZSB0aGUgYmV0dGVyIHNvbHV0aW9uLg0KPj4gPj4NCj4+ID4+ICAgICAg
ICAgV2hhdCBkbyB5b3UgdGhpbms/DQo+PiA+Pg0KPj4gPj4gUmVnYXJkcywNCj4+ID4+DQo+PiA+
PiBGZXJuYW5kbyBQYXNjdWFsIEJsYW5jbw0KPj4gPj4gVGVsZWbDs25pY2EgR2xvYmFsIFJlc291
cmNlcw0KPj4gPj4gTmV0d29yayBBdXRvbWF0aW9uIGFuZCBEeW5hbWl6YXRpb24NCj4+ID4+IFRF
Q0hOT0xPR1kgUEVPUExFIEdST1VQDQo+PiA+PiBGICszNDkxMzEyODc3OQ0KPj4gPj4gTSArMzQ2
ODIwMDUxNjgNCj4+ID4+IGZwYkB0aWQuZXMNCj4+ID4+DQo+PiA+Pg0KPj4gPj4NCj4+ID4+DQo+
PiA+PiBPbiAxNy8xMi8xMiAxMjoyNSwgIkpvc2UgU2FsZGFuYSIgPGpzYWxkYW5hQHVuaXphci5l
cz4gd3JvdGU6DQo+PiA+Pg0KPj4gPj4gPkhpIGFsbCwNCj4+ID4+ID4NCj4+ID4+ID5KdWxpYW4g
YW5kIEkgaGF2ZSBiZWVuIGRpc2N1c3NpbmcgYWJvdXQgdGhpcy4gU29tZSBpZGVhcyBoYXZlDQo+
PmFyaXNlbi4NCj4+ID4+ID5UaGlzIGlzIHRoZSBzdW1tYXJ5Lg0KPj4gPj4gPg0KPj4gPj4gPlRo
aXMgd291bGQgYmUgdGhlIHNjaGVtZSBvZiB0aGUgc3lzdGVtLCBpbmNsdWRpbmcgbXV4IGFuZCBk
ZW11eDoNCj4+ID4+ID4NCj4+ID4+ID5SZWFsLXRpbWUgYXBwbGljYXRpb24gLS0tLS0tLSBtdXgg
LS0tLS0tLS0gaW50ZXJuZXQgLS0tLS0tLS0tIGRlbXV4DQo+PiA+PiA+LS0tLS0tLQ0KPj4gPj4g
PnNlcnZlcg0KPj4gPj4gPg0KPj4gPj4gPg0KPj4gPj4gPkkgdGhpbmsgcGVyaGFwcyB0aGUgZHJh
ZnQgY291bGQgc2F5IHNvbWV0aGluZyBsaWtlOg0KPj4gPj4gPg0KPj4gPj4gPldoZW4gc2V0dGlu
ZyB0aGUgbXVsdGlwbGV4aW5nIHBlcmlvZCwgdGhlcmUgYXJlIHR3byBwb3NzaWJpbGl0aWVzOg0K
Pj4gPj4gPg0KPj4gPj4gPjEuLSBTdGF0aWMgLyBwZXJtYW5lbnQ6IEF0IHN5c3RlbSBzZXR1cCB0
aW1lLCBuZXR3b3JrIGRlbGF5cyBhcmUNCj4+ID4+ID5tZWFzdXJlZCwgYW5kIGEgbXVsdGlwbGV4
aW5nIHBlcmlvZCBpcyBzZWxlY3RlZCBhbmQgc2V0IGluIHRoZQ0KPj4gPj5tdWx0aXBsZXhlci4N
Cj4+ID4+ID4NCj4+ID4+ID4yLi0gRHluYW1pYzogQSBtZWNoYW5pc20gaXMgdXNlZCBzbyBhcyB0
byBhZGFwdCB0byB0aGUgZXZvbHV0aW9uIG9mDQo+PiA+PiA+bmV0d29yayBkZWxheXMuIEluIHRo
aXMgY2FzZSwgZGlmZmVyZW50IG1lY2hhbmlzbXMgY2FuIGJlIHVzZWQgaW4NCj4+ID4+ID5vcmRl
ciB0byBvYnRhaW4gcGVyaW9kaWNhbCBlbmQtdG8tZW5kIG5ldHdvcmsgZGVsYXkgZXN0aW1hdGlv
bnMsDQo+PiA+PiA+d2hpY2ggd291bGQgYmUgdXNlZnVsIGluIG9yZGVyIHRvIHNldCB0aGUgbXVs
dGlwbGV4aW5nIHBlcmlvZDoNCj4+ID4+ID4NCj4+ID4+ID4tIElmIHRoZSB0cmFmZmljIGlzIFJU
UCwgdGhlbiBSVENQIHBhY2tldHMgY29udGFpbmluZyB0aGUgZXN0aW1hdGlvbg0KPj4gPj4gPmNv
dWxkIGJlIGFuYWx5emVkIGluIG9yZGVyIHRvIGV4dHJhY3QgdGhlc2UgdmFsdWVzLCBhcyBEYW4g
c3VnZ2VzdHMuDQo+PiA+PiA+VGhlIHF1ZXN0aW9uDQo+PiA+PiA+aXM6IHdvdWxkIHRoYXQgcGFj
a2V0cyB0cmF2ZWwgdGhyb3VnaCB0aGUgbXVsdGlwbGV4ZXI/DQo+PiA+PiA+LSBJZiB0aGUgdHJh
ZmZpYyBpcyBUQ1AsIHBlcmhhcHMgc29tZXRoaW5nIHNpbWlsYXIgdG8gdGhlIFJUVA0KPj4gPj4g
PmVzdGltYXRpb24gb2YgVENQIGNvdWxkIGJlIHVzZWZ1bC4NCj4+ID4+ID4tIElmIHRoZSB0cmFm
ZmljIGlzIFVEUCwgc2hvdWxkIHRoZSBtdXggdXNlIHNvbWV0aGluZyBsaWtlIE9XQU1QDQo+PiA+
PiA+KGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzQ2NTYpIGluIG9yZGVyIHRvIGNhbGN1
bGF0ZSB0d28NCj4+ID4+ID5kZWxheXMgKGFwcGxpY2F0aW9uIHRvIG11eCwgYW5kIG11eCB0byBz
ZXJ2ZXIpIGFuZCBjYWxjdWxhdGUgdGhlDQo+PnN1bT8NCj4+ID4+ID4NCj4+ID4+ID4NCj4+ID4+
ID5JIHRoaW5rIHRoZSBkcmFmdCBpcyBvbmx5IHN1cHBvc2VkIHRvIHJlcG9ydCB0aGUgbWF4aW11
bSBkZWxheXMNCj4+ID4+ID5ub3JtYWxseSBjb25zaWRlcmVkIGFjY2VwdGFibGUuIFBlcmhhcHMg
dGhlIGFkZGl0aW9uYWwgbWVjaGFuaXNtcw0KPj4gPj4gPmZvciBjYWxjdWxhdGluZyB0aGUgUlRU
IGNvdWxkIGp1c3QgYmUgc3VnZ2VzdGVkLg0KPj4gPj4gPg0KPj4gPj4gPldoYXQgZG8geW91IHRo
aW5rPw0KPj4gPj4gPg0KPj4gPj4gPkpvc2UNCj4+ID4+ID4NCj4+ID4+ID4+IC0tLS0tTWVuc2Fq
ZSBvcmlnaW5hbC0tLS0tDQo+PiA+PiA+PiBEZTogdGNtdGYtYm91bmNlc0BpZXRmLm9yZyBbbWFp
bHRvOnRjbXRmLWJvdW5jZXNAaWV0Zi5vcmddIEVuDQo+PiA+PiA+PiBub21icmUgZGUgRGFuIFdp
bmcgRW52aWFkbyBlbDogdmllcm5lcywgMTQgZGUgZGljaWVtYnJlIGRlIDIwMTINCj4+ID4+ID4+
IDE4OjMzDQo+PiA+PiA+PiBQYXJhOiBqc2FsZGFuYUB1bml6YXIuZXM7ICdNaXJrbyBTdcW+bmpl
dmnEhycNCj4+ID4+ID4+IENDOiB0Y210ZkBpZXRmLm9yZw0KPj4gPj4gPj4gQXN1bnRvOiBSZTog
W3RjbXRmXSBEcmFmdDogTWF4aW11bSBUb2xlcmFibGUgRGVsYXlzIHdoZW4gdXNpbmcNCj4+ID4+
ID4+IFR1bm5lbGluZyBDb21wcmVzc2VkIE11bHRpcGxleGVkIFRyYWZmaWMgRmxvd3MNCj4+ID4+
ID4+DQo+PiA+PiA+PiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiA+PiA+PiA+IEZy
b206IEpvc2UgU2FsZGFuYSBbbWFpbHRvOmpzYWxkYW5hQHVuaXphci5lc10NCj4+ID4+ID4+ID4g
U2VudDogRnJpZGF5LCBEZWNlbWJlciAxNCwgMjAxMiAyOjU4IEFNDQo+PiA+PiA+PiA+IFRvOiAn
RGFuIFdpbmcnOyAnTWlya28gU3XFvm5qZXZpxIcnDQo+PiA+PiA+PiA+IENjOiB0Y210ZkBpZXRm
Lm9yZw0KPj4gPj4gPj4gPiBTdWJqZWN0OiBSRTogW3RjbXRmXSBEcmFmdDogTWF4aW11bSBUb2xl
cmFibGUgRGVsYXlzIHdoZW4gdXNpbmcNCj4+ID4+ID4+ID4gVHVubmVsaW5nIENvbXByZXNzZWQg
TXVsdGlwbGV4ZWQgVHJhZmZpYyBGbG93cw0KPj4gPj4gPj4gPg0KPj4gPj4gPj4gPiBEYW4sDQo+
PiA+PiA+PiA+DQo+PiA+PiA+PiA+IFJlZ2FyZGluZyB0aGUgdXNlIG9mIHRoZSBtYXhpbXVtIGRl
bGF5LCBzb21lIGRheXMgYWdvIHdlDQo+PiA+PiA+PiA+IGRpc2N1c3NlZCBhYm91dA0KPj4gPj4g
Pj4gPiBpdDoNCj4+ID4+ID4+ID4gdGhlIGFjdHVhbCBPV0Qgb2YgdGhlIG5ldHdvcmsgc2hvdWxk
IGJlIG1lYXN1cmVkIChvciBlc3RpbWF0ZWQpDQo+PiA+PiA+PiA+IGluIG9yZGVyIHRvIGtub3cg
dGhlIG1heGltdW0gbXVsdGlwbGV4aW5nIHBlcmlvZCB3ZSBjYW4gc2V0Lg0KPj4gPj4gPj4gPg0K
Pj4gPj4gPj4gPiBXZSBtYXkgaGF2ZSB0aGlzIGZvcm11bGEsIGlmIHRoaW5raW5nIG9uZS13YXk6
DQo+PiA+PiA+PiA+DQo+PiA+PiA+PiA+IE9XRCAgKyBNdXggcGVyaW9kLzIgIDwgdG9sZXJhYmxl
X09XRA0KPj4gPj4gPj4gPg0KPj4gPj4gPj4gPiBJZiB3ZSB0aGluayBSVFQ6DQo+PiA+PiA+PiA+
DQo+PiA+PiA+PiA+IE9XRCArIE11eCBwZXJpb2QvMiArIE9XRCBiYWNrIDwgMip0b2xlcmFibGVf
T1dEDQo+PiA+PiA+PiA+DQo+PiA+PiA+PiA+IEkgZG9uJ3Qga25vdyBpZiB3ZSBzaG91bGQgaW5j
bHVkZSBhIG1lY2hhbmlzbSBmb3IgZXN0aW1hdGluZyBPV0QNCj4+ID4+ID4+ID4gaW4gdGNtdGYu
IEkgdGhpbmsgdGhpcyBpcyBtb3JlIGFuIGltcGxlbWVudGF0aW9uIHByb2JsZW0sIHdoaWNoDQo+
PiA+PiA+PiA+IG1heSBiZSBhbHJlYWR5IHNvbHZlZC4NCj4+ID4+ID4+DQo+PiA+PiA+PiBZZXMs
IGl0J3MgYWxyZWFkeSBzb2x2ZWQgZW5kLXRvLWVuZDogIFJUUCB3aXRoIFJUQ1AgZmVlZGJhY2sN
Cj4+ID4+ID4+IGFsbG93cyBkZXRlcm1pbmluZyBvbmUgd2F5IGRlbGF5Lg0KPj4gPj4gPj4NCj4+
ID4+ID4+IEJ1dCBpZiBzb21ldGhpbmcgaW4gdGhlIG1pZGRsZSBpcyBtdWx0aXBsZXhpbmcgc2V2
ZXJhbCBwYWNrZXRzDQo+PiA+PiA+PiB0b2dldGhlciwNCj4+ID4+ID53ZQ0KPj4gPj4gPj4gZG9u
J3Qgd2FudCBpdCB0byBhZGQgdG9vIG11Y2ggZGVsYXkuICBUaGF0IHRoaW5nIGluIHRoZSBtaWRk
bGUNCj4+ID4+ID4+d29uJ3QgbmVjZXNzYXJpbHkga25vdyB0aGUgb25lIHdheSBkZWxheSBzZWVu
IGJ5IHRoZSBlbmRwb2ludHMsDQo+PiA+PiA+PnVubGVzcyBpdCBhbmFseXplcyB0aGUgUlRQIGFu
ZCBSVENQLiAgVGhlcmUgYXJlIGRldmljZXMgdGhhdCBkbw0KPj4gPj4gPj50aGF0IG9uIHRoZSBt
YXJrZXQsICBtb3N0bHkgdG8gZGlhZ25vc2Ugd2hlcmUgbmV0d29ya3MgYXJlIGNhdXNpbmcNCj4+
ID4+ID4+bG9zcy9kZWxheSB3aXRoIFJUUCBmbG93cy4NCj4+ID4+ID4+DQo+PiA+PiA+Pg0KPj4g
Pj4gPj4gPiBBbm90aGVyIG9wdGlvbiBpcyB1c2luZyBzb21lIHR5cGljYWwgdmFsdWVzLCBlLmcu
IGZyb20NCj4+ID4+ID4+ID4gaHR0cDovL2lwbmV0d29yay5iZ3Rtby5pcC5hdHQubmV0L3B3cy9n
bG9iYWxfbmV0d29ya19hdmdzLmh0bWwNCj4+ID4+ID4+ID4NCj4+ID4+ID4+ID4gVGhlIGRyYWZ0
IGluY2x1ZGVzIHNvbWUgcHJlbGltaW5hcnkvcmVjb21tZW5kZWQgdmFsdWVzIGZvciB0aGUNCj4+
ID4+ID4+ID4gTXVsdGlwbGV4aW5nIFBlcmlvZC4gSXMgdGhpcyBpbnRlcmVzdGluZz8gU2hvdWxk
IHdlIHB1dCB0aGUNCj4+ID4+ID4+ID4gZm9ybXVsYSBpbnN0ZWFkPw0KPj4gPj4gPj4NCj4+ID4+
ID4+IEl0J3MgcHJvYmFibHkgc3VmZmljaWVudCBhcy1pcy4NCj4+ID4+ID4+DQo+PiA+PiA+PiAt
ZA0KPj4gPj4gPj4NCj4+ID4+ID4+ID4gTWlya28sIGFub3RoZXIgcXVlc3Rpb246IGluIG9ubGlu
ZSBnYW1lcywgcGxheWVycyB1c3VhbGx5IHRhbGsNCj4+ID4+ID4+ID4gYWJvdXQgdGhlICJwaW5n
IiwgYW5kIEkgdGhpbmsgaXQgbWVhbnMgUlRULiBEb24ndCB5b3UgdGhpbmsgaXQNCj4+ID4+ID4+
ID4gd291bGQgYmUgYmV0dGVyIHRvIGRlZmluZSBhIFJUVCBsaW1pdCBpbnN0ZWFkIG9mIGEgT1dE
IG9uZSBpbg0KPj4gPj4gPj4gPiB0aGF0DQo+PiA+PmNhc2U/DQo+PiA+PiA+PiA+DQo+PiA+PiA+
PiA+IFdoYXQgZG8geW91IHRoaW5rPw0KPj4gPj4gPj4gPg0KPj4gPj4gPj4gPiBKb3NlDQo+PiA+
PiA+PiA+DQo+PiA+PiA+PiA+ID4gLS0tLS1NZW5zYWplIG9yaWdpbmFsLS0tLS0NCj4+ID4+ID4+
ID4gPiBEZTogdGNtdGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnRjbXRmLWJvdW5jZXNAaWV0
Zi5vcmddIEVuDQo+PiA+PiA+PiA+ID4gbm9tYnJlIGRlIERhbiBXaW5nIEVudmlhZG8gZWw6IGp1
ZXZlcywgMTMgZGUgZGljaWVtYnJlIGRlIDIwMTINCj4+ID4+ID4+ID4gPiAxNzowNw0KPj4gPj4g
Pj4gPiA+IFBhcmE6ICdNaXJrbyBTdcW+bmpldmnEhyc7IHRjbXRmQGlldGYub3JnDQo+PiA+PiA+
PiA+ID4gQXN1bnRvOiBSZTogW3RjbXRmXSBEcmFmdDogTWF4aW11bSBUb2xlcmFibGUgRGVsYXlz
IHdoZW4gdXNpbmcNCj4+ID4+ID4+ID4gPiBUdW5uZWxpbmcgQ29tcHJlc3NlZCBNdWx0aXBsZXhl
ZCBUcmFmZmljIEZsb3dzDQo+PiA+PiA+PiA+ID4NCj4+ID4+ID4+ID4gPiA+IC0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+PiA+PiA+PiA+ID4gPiBGcm9tOiB0Y210Zi1ib3VuY2VzQGlldGYu
b3JnIFttYWlsdG86dGNtdGYtYm91bmNlc0BpZXRmLm9yZ10NCj4+ID4+ID4+ID4gPiA+IE9uIEJl
aGFsZiBPZiBNaXJrbyBTdcW+bmpldmljDQo+PiA+PiA+PiA+ID4gPiBTZW50OiBUaHVyc2RheSwg
RGVjZW1iZXIgMTMsIDIwMTIgMTowNyBBTQ0KPj4gPj4gPj4gPiA+ID4gVG86IHRjbXRmQGlldGYu
b3JnOyB0c3Z3Z0BpZXRmLm9yZw0KPj4gPj4gPj4gPiA+ID4gU3ViamVjdDogW3RjbXRmXSBEcmFm
dDogTWF4aW11bSBUb2xlcmFibGUgRGVsYXlzIHdoZW4gdXNpbmcNCj4+ID4+ID4+ID4gPiA+IFR1
bm5lbGluZyBDb21wcmVzc2VkIE11bHRpcGxleGVkIFRyYWZmaWMgRmxvd3MNCj4+ID4+ID4+ID4g
PiA+DQo+PiA+PiA+PiA+ID4gPiBIZWxsbywNCj4+ID4+ID4+ID4gPiA+DQo+PiA+PiA+PiA+ID4g
Pg0KPj4gPj4gPj4gPiA+ID4NCj4+ID4+ID4+ID4gPiA+IFdlIGhhdmUganVzdCBzdWJtaXR0ZWQg
dGhlIGRyYWZ0IG5hbWVkIE1heGltdW0gVG9sZXJhYmxlDQo+PiA+PiA+PiA+ID4gPiBEZWxheXMg
d2hlbiB1c2luZyBUdW5uZWxpbmcgQ29tcHJlc3NlZCBNdWx0aXBsZXhlZCBUcmFmZmljDQo+PiBG
bG93czoNCj4+ID4+ID4+ID4gPiA+IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh
ZnQtc3V6bmpldmljLXRzdndnLW10ZC10Yw0KPj4gPj4gPj4gPiA+ID4gbXRmDQo+PiA+PiA+PiA+
ID4gPiAvDQo+PiA+PiA+PiA+ID4NCj4+ID4+ID4+ID4gPiBUaGUgc3VnZ2VzdGVkIDQwMG1zIGZv
ciBpbnRlcmFjdGl2ZSB2b2ljZSBpcyBhdCBsZWFzdCAyeCB0b28NCj4+ID4+aGlnaC4NCj4+ID4+
ID4+ID4gPiBJDQo+PiA+PiA+PiA+IGV4cGVjdA0KPj4gPj4gPj4gPiA+IHRoYXQgbnVtYmVyIGRv
ZXMgbm90IGluY2x1ZGUgdGhlIHBsYXlvdXQgaml0dGVyIGJ1ZmZlciAod2hpY2gNCj4+ID4+ID4+
ID4gPiBpcyB2YXJpYWJsZSwNCj4+ID4+ID4+ID4gYnV0DQo+PiA+PiA+PiA+ID4gdXN1YWxseSBh
IGZldyBzYW1wbGVzLCBzbyA0MC04MG1zKS4gIDIwMG1zIGVuZC10by1lbmQgaXMgdGhlDQo+PiA+
PiA+PiA+ID4gaGlnaGVyIGVuZCwNCj4+ID4+ID4+ID4gYW5kDQo+PiA+PiA+PiA+ID4gdGhhdCBp
bmNsdWRlcyBqaXR0ZXIgYnVmZmVyLCBjb2RlYyBwcm9jZXNzaW5nLCBhbmQgc28gb24uDQo+PiA+
PiA+PiA+ID4NCj4+ID4+ID4+ID4gPiBCdXQsIG1vcmUgaW1wb3J0YW50bHk6ICBpdCBzZWVtcyB2
YWx1YWJsZSBmb3IgZW5kcG9pbnRzIHRvDQo+PiA+PiA+PiA+ID4gc2lnbmFsIHRoZWlyIG1heGlt
dW0gZGVsYXkgc29tZWhvdy4gIE9yIHdvdWxkIHRoZSBUQ01URg0KPj4gPj4gPj4gPiA+IGZ1bmN0
aW9uDQo+PiA+PiA+PiBkZXRlcm1pbmUNCj4+ID4+ID4+ID4gPiB0aGUgbWF4aW11bSBkZWxheSwg
dXNpbmcgc29tZSBoZXVyaXN0aWM/DQo+PiA+PiA+PiA+ID4NCj4+ID4+ID4+ID4gPiBIb3cgZG9l
cyB0aGUgVENNVEYgZnVuY3Rpb24gZGV0ZXJtaW5lIGhvdyBtdWNoIG9mIHRoYXQNCj4+ID4+ID4+
ID4gPiAndG9sZXJhYmxlIGxhdGVuY3knIGJ1ZGdldCBpdCBjYW4gY29uc3VtZT8NCj4+ID4+ID4+
ID4gPg0KPj4gPj4gPj4gPiA+IC1kDQo+PiA+PiA+PiA+ID4NCj4+ID4+ID4+ID4gPg0KPj4gPj4g
Pj4gPiA+ID4gSXQgaXMgYW4gZXh0ZW5zaW9uIG9mIHRjbXRmDQo+PiA+PiA+PiA+ID4gPiBodHRw
Oi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LQ0KPj4gPj4gPj4gPiA+ID4gc2FsZGFu
YS10c3Z3Zy10Y210Zi8uIFNpbmNlIGEgc3BlY2lmaWMgbGlzdCBmb3IgdGNtdGYgZXhpc3RzDQo+
PiA+PiA+PiA+ID4gPiAodGNtdGZAaWV0Zi5vcmcpLCB0aGUgaWRlYSBpcyB0byBkaXNjdXNzIGl0
IHRoZXJlLg0KPj4gPj4gPj4gPiA+ID4NCj4+ID4+ID4+ID4gPiA+DQo+PiA+PiA+PiA+ID4gPg0K
Pj4gPj4gPj4gPiA+ID4gVGhlIGRyYWZ0IGNvbnRhaW5zIHJlY29tbWVuZGF0aW9ucyBmb3IgVENN
VEYgbXVsdGlwbGV4aW5nDQo+PiA+PiA+PiA+ID4gPiBwZXJpb2QgZm9yIGRpZmZlcmVudCByZWFs
LXRpbWUgc2VydmljZXMuIEluIG9yZGVyIHRvIHByZXZlbnQNCj4+ID4+ID4+ID4gPiA+IFFvRSBk
ZWdyYWRhdGlvbiBvZiByZWFsLXRpbWUgc2VydmljZXMgdXNpbmcgVENNVEYsIGEgcG9saWN5DQo+
PiA+PiA+PiA+ID4gPiBkZWZpbmluZyBhIG11bHRpcGxleGluZyBwZXJpb2QgY2FuIGJlIGVtcGxv
eWVkLiBWYWx1ZXMgb2YNCj4+ID4+ID4+ID4gPiA+IG1heGltdW0gdG9sZXJhYmxlIGRlbGF5cyBw
cmVzZW50ZWQgaW4NCj4+ID4+ID4+ID4gPiB0aGUNCj4+ID4+ID4+ID4gPiA+IGRyYWZ0IGZvcm0g
dGhlIGJhc2Ugb2Ygc3VjaCBwb2xpY3kuICAgIFRoZSByZWNvbW1lbmRhdGlvbnMNCj4+YXJlDQo+
PiA+PiA+PiA+IHByZXNlbnRlZA0KPj4gPj4gPj4gPiA+ID4gZm9yIHJlYWwtdGltZSBuZXR3b3Jr
IHNlcnZpY2VzIGluIHdoaWNoIFRDVE1GIGJhbmR3aWR0aA0KPj4gPj4gPj4gPiA+ID4gb3B0aW1p
emF0aW9uIGlzIGFwcGxpY2FibGUgKGkuZS4sIHNlcnZpY2VzICB3aGljaCBoYXZlIGxvdw0KPj4g
Pj4gPj4gPiA+ID4gcGF5bG9hZCB0byBoZWFkZXIgc2l6ZSByYXRpbyB3aGljaCByZXN1bHRzIGlu
IGhpZ2ggcHJvdG9jb2wNCj4+ID4+IG92ZXJoZWFkKS4NCj4+ID4+ID4+ID4gPiA+DQo+PiA+PiA+
PiA+ID4gPg0KPj4gPj4gPj4gPiA+ID4NCj4+ID4+ID4+ID4gPiA+IFlvdXIgZmVlZGJhY2sgd2ls
bCBiZSB3ZWxjb21lLiBUaGFuayB5b3UuDQo+PiA+PiA+PiA+ID4gPg0KPj4gPj4gPj4gPiA+ID4N
Cj4+ID4+ID4+ID4gPiA+IFNpbmNlcmVseSwNCj4+ID4+ID4+ID4gPiA+DQo+PiA+PiA+PiA+ID4g
PiBNaXJrbyBTdXpuamV2aWMNCj4+ID4+ID4+ID4gPg0KPj4gPj4gPj4gPiA+DQo+PiA+PiA+PiA+
ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+ID4+
ID4+ID4gPiB0Y210ZiBtYWlsaW5nIGxpc3QNCj4+ID4+ID4+ID4gPiB0Y210ZkBpZXRmLm9yZw0K
Pj4gPj4gPj4gPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYN
Cj4+ID4+ID4+DQo+PiA+PiA+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPj4gPj4gPj4gdGNtdGYgbWFpbGluZyBsaXN0DQo+PiA+PiA+PiB0Y210ZkBp
ZXRmLm9yZw0KPj4gPj4gPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90
Y210Zg0KPj4gPj4gPg0KPj4gPj4gPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQo+PiA+PiA+dGNtdGYgbWFpbGluZyBsaXN0DQo+PiA+PiA+dGNtdGZAaWV0
Zi5vcmcNCj4+ID4+ID5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRm
DQo+PiA+Pg0KPj4gPj4NCj4+ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
PiA+Pg0KPj4gPj4gRXN0ZSBtZW5zYWplIHNlIGRpcmlnZSBleGNsdXNpdmFtZW50ZSBhIHN1IGRl
c3RpbmF0YXJpby4gUHVlZGUNCj4+ID4+IGNvbnN1bHRhciBudWVzdHJhIHBvbMOtdGljYSBkZSBl
bnbDrW8geSByZWNlcGNpw7NuIGRlIGNvcnJlbyBlbGVjdHLDs25pY28NCj4+ID4+IGVuIGVsIGVu
bGFjZSBzaXR1YWRvIG3DoXMgYWJham8uDQo+PiA+PiBUaGlzIG1lc3NhZ2UgaXMgaW50ZW5kZWQg
ZXhjbHVzaXZlbHkgZm9yIGl0cyBhZGRyZXNzZWUuIFdlIG9ubHkgc2VuZA0KPj4gPj4gYW5kIHJl
Y2VpdmUgZW1haWwgb24gdGhlIGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQgb3V0IGF0Og0KPj4gPj4g
aHR0cDovL3d3dy50aWQuZXMvRVMvUEFHSU5BUy9kaXNjbGFpbWVyLmFzcHgNCj4+ID4NCj4+ID5f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gPnRjbXRm
IG1haWxpbmcgbGlzdA0KPj4gPnRjbXRmQGlldGYub3JnDQo+PiA+aHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby90Y210Zg0KPj4NCj4+DQo+PiBfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KPj4NCj4+IEVzdGUgbWVuc2FqZSBzZSBkaXJpZ2UgZXhjbHVzaXZhbWVu
dGUgYSBzdSBkZXN0aW5hdGFyaW8uIFB1ZWRlIGNvbnN1bHRhcg0KPj4gbnVlc3RyYSBwb2zDrXRp
Y2EgZGUgZW52w61vIHkgcmVjZXBjacOzbiBkZSBjb3JyZW8gZWxlY3Ryw7NuaWNvIGVuIGVsIGVu
bGFjZQ0KPj4gc2l0dWFkbyBtw6FzIGFiYWpvLg0KPj4gVGhpcyBtZXNzYWdlIGlzIGludGVuZGVk
IGV4Y2x1c2l2ZWx5IGZvciBpdHMgYWRkcmVzc2VlLiBXZSBvbmx5IHNlbmQgYW5kDQo+PiByZWNl
aXZlIGVtYWlsIG9uIHRoZSBiYXNpcyBvZiB0aGUgdGVybXMgc2V0IG91dCBhdDoNCj4+IGh0dHA6
Ly93d3cudGlkLmVzL0VTL1BBR0lOQVMvZGlzY2xhaW1lci5hc3B4DQo+DQoNCg0KX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCg0KRXN0ZSBtZW5zYWplIHNlIGRpcmlnZSBleGNsdXNp
dmFtZW50ZSBhIHN1IGRlc3RpbmF0YXJpby4gUHVlZGUgY29uc3VsdGFyIG51ZXN0cmEgcG9sw610
aWNhIGRlIGVudsOtbyB5IHJlY2VwY2nDs24gZGUgY29ycmVvIGVsZWN0csOzbmljbyBlbiBlbCBl
bmxhY2Ugc2l0dWFkbyBtw6FzIGFiYWpvLg0KVGhpcyBtZXNzYWdlIGlzIGludGVuZGVkIGV4Y2x1
c2l2ZWx5IGZvciBpdHMgYWRkcmVzc2VlLiBXZSBvbmx5IHNlbmQgYW5kIHJlY2VpdmUgZW1haWwg
b24gdGhlIGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQgb3V0IGF0Og0KaHR0cDovL3d3dy50aWQuZXMv
RVMvUEFHSU5BUy9kaXNjbGFpbWVyLmFzcHgNCg==

From jsaldana@unizar.es  Thu Jan 17 05:51:10 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB9021F86EA for <tcmtf@ietfa.amsl.com>; Thu, 17 Jan 2013 05:51:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.411
X-Spam-Level: 
X-Spam-Status: No, score=-6.411 tagged_above=-999 required=5 tests=[AWL=-0.112, 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 Wa3uiI6+A9qC for <tcmtf@ietfa.amsl.com>; Thu, 17 Jan 2013 05:51:06 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 3A95221F86D5 for <tcmtf@ietf.org>; Thu, 17 Jan 2013 05:51:02 -0800 (PST)
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 r0HDooNJ026554; Thu, 17 Jan 2013 14:50:50 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>, "'Dan Wing'" <dwing@cisco.com>,  "=?utf-8?Q?'Mirko_Su=C5=BEnjevi=C4=87'?=" <Mirko.Suznjevic@fer.hr>, "=?utf-8?Q?'Juli=C3=A1n_Fern=C3=A1ndez_Navajas'?=" <navajas@unizar.es>
References: <009701cdf4ac$8af49750$a0ddc5f0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A2689D3F12@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A2689D3F12@EX10-MB2-MAD.hi.inet>
Date: Thu, 17 Jan 2013 14:50:55 +0100
Organization: Universidad de Zaragoza
Message-ID: <009f01cdf4b9$aca39060$05eab120$@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: AQJ038JPflGQCxb71NgVJw2SNPSoj5b/skvQ
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
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, 17 Jan 2013 13:51:10 -0000

In addition, perhaps we are too focused on online games and VoIP =
services. There are other services which are one-way: perhaps M2M =
communications do not require a two way communication. We can think =
about a number of sensors sending their measurements to a central =
server. So perhaps RTT will not even exist in this case.

Jose

> -----Mensaje original-----
> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> Enviado el: jueves, 17 de enero de 2013 14:39
> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko Su=C5=BEnjevi=C4=87'; =
'Juli=C3=A1n Fern=C3=A1ndez
> Navajas'
> CC: tcmtf@ietf.org
> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using =
Tunneling
> Compressed Multiplexed Traffic Flows
>=20
> Jose,
>=20
>         Let=C2=B4s say that playing with the OWD you have more =
granularity in order to
> know in which direction you need to reduce the delay by reducing the
> multiplexing delay. But people with more knowledge about online games =
will
> provide us more information for sure.
>=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 17/01/13 13:16, "Jose Saldana" <jsaldana@unizar.es> wrote:
>=20
> >Fernando,
> >
> >So you may have this case:
> >- your multiplexing delay limit is 50 ms
> >- you have a lot of flows to multiplex, so perhaps the time between
> >multiplexed packets will be 5 ms
> >- you detect an increase in RTT
> >- the system reacts and reduces multiplexing period
> >- in fact, the reduction doesn't matter until the period is reduced =
to
> >less than 5 ms
> >
> >So you only have to make this decision: using tcmtf with 5 ms period =
or
> >not. If RTT is critical you may not be interested on saving =
bandwidth,
> >but on reducing a bit the RTT.
> >
> >So I think your question is: what happens if the RTT is very big (out
> >of
> >limits) and you can save bandwidth using a 5ms multiplexing period?
> >
> >For example, the maximum RTT for a good quality is 80 ms and your
> >network has 120 just now. In this case, perhaps having 125 doesn't
> >matter, if you can save bandwidth.
> >
> >This makes sense, but it is a "extreme" case. However, would it be =
any
> >advantage if OWD is used instead of RTT?
> >
> >Best regards,
> >
> >Jose
> >
> >> -----Mensaje original-----
> >> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]  Enviado el:
> >>mi=C3=A9rcoles, 16 de enero de 2013 12:52
> >> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko Su=C5=BEnjevi=C4=87'; =
'Juli=C3=A1n
> >>Fern=C3=A1ndez  Navajas'
> >> CC: tcmtf@ietf.org
> >> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
> >>Tunneling  Compressed Multiplexed Traffic Flows
> >>
> >> Hi Jose,
> >>
> >>         You are right, but my point here is:
> >>
> >>                 Client - Mux - Demux - Server
> >>
> >>         Imagine that there is enough packets between mux and demux =
to
> >>make  the added delay very small (TCMTF is working very well and the
> >>mux has not  to wait the multiplexing period to fulfill a big packet
> >>and send it, so imagine a  multiplexing period of 50 ms and a big
> >>packet is fulfilled in 5 ms). If the RTT  get increased because a
> >>congestion in the way back to the client (there is no  TCMTF
> >>optimization) and we decrease the multiplexing period (even in the
> >>extreme we can disable the TCMTF optimization) the high RTT will =
remain.
> >> Even if the TCMTF optimization was helping in the client to server
> >>path,  disabling it may harm. Do you think that scenario would be =
possible?
> >>
> >>         So I=C2=B4m not sure about that, I think we need more =
opinions here.
> >>
> >> Regards,
> >>
> >> Fernando Pascual Blanco
> >> Telef=C3=B3nica Global Resources
> >> Network Automation and Dynamization
> >> TECHNOLOGY PEOPLE GROUP
> >> F +34913128779
> >> M +34682005168
> >> fpb@tid.es
> >>
> >>
> >>
> >>
> >> On 16/01/13 11:57, "Jose Saldana" <jsaldana@unizar.es> wrote:
> >>
> >> >My two cents:
> >> >
> >> >In games and in VoIP the really important thing is RTT:
> >> >
> >> >- Games always measure the RTT (gamers talk about the "ping"): the
> >> >important thing is the delay from a player action to the server
> >> >reaction arriving to the player's machine.
> >> >- In VoIP I think it is the same: what matters is the RTT, in =
order
> >> >to grant interactivity and avoiding cross-talk.
> >> >
> >> >In addition, RTT is easier to measure than OWD, since you don't =
need
> >> >synchronization.
> >> >
> >> >And regarding Two-way TCMTF, I think we have to think about TCMTF =
as
> >> >one-way. Otherwise, things would become very complicated. Some
> >> services
> >> >have very different client-server and server-client traffic =
patterns
> >> >(e.g. games). In addition, sometimes the two flows can follow
> >> >different network paths. I think once we talked about a network
> >> >provider using a number of ISPs.
> >> >
> >> >However, using RTT for tuning a one-way TCMTF may not be bad... or
> >> >is it bad? Any other thoughts?
> >> >
> >> >BR,
> >> >
> >> >Jose
> >> >
> >> >> -----Mensaje original-----
> >> >> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]  Enviado el:
> >> martes,
> >> >>15 de enero de 2013 18:04
> >> >> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko =
Su=C5=BEnjevi=C4=87'; Juli=C3=A1n
> >> >>Fern=C3=A1ndez  Navajas
> >> >> CC: tcmtf@ietf.org
> >> >> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
> >> >>Tunneling  Compressed Multiplexed Traffic Flows
> >> >>
> >> >> Hi all,
> >> >>
> >> >>         To re-open that issue, I would suggest that given that =
the
> >> >>delay is so  sensitive in real time services, we need to find a
> >> >>consensus here.
> >> >>
> >> >>         My opinion is that to apply the first possibility (the
> >> >>static multiplexing
> >> >> period) we need to suppose that the network conditions are =
really
> >> >>bad, to be  protected when the network congestion arises. In that
> >> >>case, the application  of the TCMTF optimization will not be
> >> >>optimal, so that would be the less  preferred option, but easier =
to
> >> >>implement and maintain over the time.
> >> >>
> >> >>         On the other hand, the second possibility would be the
> >> >>preferred. It is  easy to know the delay between the mux and the
> >> >>demux but most of the  times will not be enough unless mux and
> >> >>demux were really near from the  client and the server
> >> >>respectively. I agree with Jose in the possibility of snoop  RTCP
> >> >>packets in order to adapt the multiplexing period when =
multiplexing
> >> >>RTP packets (and RTCP is available). Talking about RTT, I=C2=B4m =
not
> >> >>sure if RTT  would be useful given that the multiplexing period
> >> >>only affect the one way  delay (OWD). Imagine the following =
scenario:
> >> >>         - Client - Mux/Demux - Demux/Mux - Server (two ways =
TCMTF,
> >> >>TWTCMTF :P)
> >> >>         - The OWD from server to client get increased
> >> >>         - The OWD from client to server remains equal
> >> >>         - Should we use a lower multiplexing period in the =
client
> >> >>to server  direction? I don=C2=B4t think so=E2=80=A6 because we =
should use a
> >> >>lower multiplexing  period in the other direction.
> >> >>
> >> >>         My point is that the multiplexing period should only be
> >> >>affected by the  OWD and not by the RTT (or it may be application
> >> >>dependent). How to  calculate the OWD? I=C2=B4ve been reading =
something
> >> >>about OWAMP and it  seems that an specific software has to be
> >> >>implemented in the client/server  side.
> >> >> Can we assume that? Unfortunately I cannot contribute so much
> here=E2=80=A6
> >> >>         It is possible that for certain services the static (and
> >> >>worst
> >> >>case)
> >> >> multiplexing period would be the better solution.
> >> >>
> >> >>         What do you think?
> >> >>
> >> >> Regards,
> >> >>
> >> >> Fernando Pascual Blanco
> >> >> Telef=C3=B3nica Global Resources
> >> >> Network Automation and Dynamization TECHNOLOGY PEOPLE GROUP
> F
> >> >> +34913128779 M +34682005168 fpb@tid.es
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On 17/12/12 12:25, "Jose Saldana" <jsaldana@unizar.es> wrote:
> >> >>
> >> >> >Hi all,
> >> >> >
> >> >> >Julian and I have been discussing about this. Some ideas have
> >>arisen.
> >> >> >This is the summary.
> >> >> >
> >> >> >This would be the scheme of the system, including mux and =
demux:
> >> >> >
> >> >> >Real-time application ------- mux -------- internet ---------
> >> >> >demux
> >> >> >-------
> >> >> >server
> >> >> >
> >> >> >
> >> >> >I think perhaps the draft could say something like:
> >> >> >
> >> >> >When setting the multiplexing period, there are two =
possibilities:
> >> >> >
> >> >> >1.- Static / permanent: At system setup time, network delays =
are
> >> >> >measured, and a multiplexing period is selected and set in the
> >> >>multiplexer.
> >> >> >
> >> >> >2.- Dynamic: A mechanism is used so as to adapt to the =
evolution
> >> >> >of network delays. In this case, different mechanisms can be =
used
> >> >> >in order to obtain periodical end-to-end network delay
> >> >> >estimations, which would be useful in order to set the =
multiplexing
> period:
> >> >> >
> >> >> >- If the traffic is RTP, then RTCP packets containing the
> >> >> >estimation could be analyzed in order to extract these values, =
as Dan
> suggests.
> >> >> >The question
> >> >> >is: would that packets travel through the multiplexer?
> >> >> >- If the traffic is TCP, perhaps something similar to the RTT
> >> >> >estimation of TCP could be useful.
> >> >> >- If the traffic is UDP, should the mux use something like =
OWAMP
> >> >> >(http://tools.ietf.org/html/rfc4656) in order to calculate two
> >> >> >delays (application to mux, and mux to server) and calculate =
the
> >>sum?
> >> >> >
> >> >> >
> >> >> >I think the draft is only supposed to report the maximum delays
> >> >> >normally considered acceptable. Perhaps the additional =
mechanisms
> >> >> >for calculating the RTT could just be suggested.
> >> >> >
> >> >> >What do you think?
> >> >> >
> >> >> >Jose
> >> >> >
> >> >> >> -----Mensaje original-----
> >> >> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> >> >> nombre de Dan Wing Enviado el: viernes, 14 de diciembre de =
2012
> >> >> >> 18:33
> >> >> >> Para: jsaldana@unizar.es; 'Mirko Su=C5=BEnjevi=C4=87'
> >> >> >> CC: tcmtf@ietf.org
> >> >> >> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when =
using
> >> >> >> Tunneling Compressed Multiplexed Traffic Flows
> >> >> >>
> >> >> >> > -----Original Message-----
> >> >> >> > From: Jose Saldana [mailto:jsaldana@unizar.es]
> >> >> >> > Sent: Friday, December 14, 2012 2:58 AM
> >> >> >> > To: 'Dan Wing'; 'Mirko Su=C5=BEnjevi=C4=87'
> >> >> >> > Cc: tcmtf@ietf.org
> >> >> >> > Subject: RE: [tcmtf] Draft: Maximum Tolerable Delays when
> >> >> >> > using Tunneling Compressed Multiplexed Traffic Flows
> >> >> >> >
> >> >> >> > Dan,
> >> >> >> >
> >> >> >> > Regarding the use of the maximum delay, some days ago we
> >> >> >> > discussed about
> >> >> >> > it:
> >> >> >> > the actual OWD of the network should be measured (or
> >> >> >> > estimated) in order to know the maximum multiplexing period =
we
> can set.
> >> >> >> >
> >> >> >> > We may have this formula, if thinking one-way:
> >> >> >> >
> >> >> >> > OWD  + Mux period/2  < tolerable_OWD
> >> >> >> >
> >> >> >> > If we think RTT:
> >> >> >> >
> >> >> >> > OWD + Mux period/2 + OWD back < 2*tolerable_OWD
> >> >> >> >
> >> >> >> > I don't know if we should include a mechanism for =
estimating
> >> >> >> > OWD in tcmtf. I think this is more an implementation =
problem,
> >> >> >> > which may be already solved.
> >> >> >>
> >> >> >> Yes, it's already solved end-to-end:  RTP with RTCP feedback
> >> >> >> allows determining one way delay.
> >> >> >>
> >> >> >> But if something in the middle is multiplexing several =
packets
> >> >> >> together,
> >> >> >we
> >> >> >> don't want it to add too much delay.  That thing in the =
middle
> >> >> >>won't necessarily know the one way delay seen by the =
endpoints,
> >> >> >>unless it analyzes the RTP and RTCP.  There are devices that =
do
> >> >> >>that on the market,  mostly to diagnose where networks are
> >> >> >>causing loss/delay with RTP flows.
> >> >> >>
> >> >> >>
> >> >> >> > Another option is using some typical values, e.g. from
> >> >> >> >
> http://ipnetwork.bgtmo.ip.att.net/pws/global_network_avgs.htm
> >> >> >> > l
> >> >> >> >
> >> >> >> > The draft includes some preliminary/recommended values for
> >> >> >> > the Multiplexing Period. Is this interesting? Should we put
> >> >> >> > the formula instead?
> >> >> >>
> >> >> >> It's probably sufficient as-is.
> >> >> >>
> >> >> >> -d
> >> >> >>
> >> >> >> > Mirko, another question: in online games, players usually
> >> >> >> > talk about the "ping", and I think it means RTT. Don't you
> >> >> >> > think it would be better to define a RTT limit instead of a
> >> >> >> > OWD one in that
> >> >>case?
> >> >> >> >
> >> >> >> > What do you think?
> >> >> >> >
> >> >> >> > Jose
> >> >> >> >
> >> >> >> > > -----Mensaje original-----
> >> >> >> > > De: tcmtf-bounces@ietf.org =
[mailto:tcmtf-bounces@ietf.org]
> >> >> >> > > En nombre de Dan Wing Enviado el: jueves, 13 de diciembre
> >> >> >> > > de 2012
> >> >> >> > > 17:07
> >> >> >> > > Para: 'Mirko Su=C5=BEnjevi=C4=87'; tcmtf@ietf.org
> >> >> >> > > Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when
> >> >> >> > > using Tunneling Compressed Multiplexed Traffic Flows
> >> >> >> > >
> >> >> >> > > > -----Original Message-----
> >> >> >> > > > From: tcmtf-bounces@ietf.org
> >> >> >> > > > [mailto:tcmtf-bounces@ietf.org] On Behalf Of Mirko
> >> >> >> > > > Su=C5=BEnjevic
> >> >> >> > > > Sent: Thursday, December 13, 2012 1:07 AM
> >> >> >> > > > To: tcmtf@ietf.org; tsvwg@ietf.org
> >> >> >> > > > Subject: [tcmtf] Draft: Maximum Tolerable Delays when
> >> >> >> > > > using Tunneling Compressed Multiplexed Traffic Flows
> >> >> >> > > >
> >> >> >> > > > Hello,
> >> >> >> > > >
> >> >> >> > > >
> >> >> >> > > >
> >> >> >> > > > We have just submitted the draft named Maximum =
Tolerable
> >> >> >> > > > Delays when using Tunneling Compressed Multiplexed
> >> >> >> > > > Traffic
> >> Flows:
> >> >> >> > > > =
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd
> >> >> >> > > > -tc
> >> >> >> > > > mtf
> >> >> >> > > > /
> >> >> >> > >
> >> >> >> > > The suggested 400ms for interactive voice is at least 2x
> >> >> >> > > too
> >> >>high.
> >> >> >> > > I
> >> >> >> > expect
> >> >> >> > > that number does not include the playout jitter buffer
> >> >> >> > > (which is variable,
> >> >> >> > but
> >> >> >> > > usually a few samples, so 40-80ms).  200ms end-to-end is
> >> >> >> > > the higher end,
> >> >> >> > and
> >> >> >> > > that includes jitter buffer, codec processing, and so on.
> >> >> >> > >
> >> >> >> > > But, more importantly:  it seems valuable for endpoints =
to
> >> >> >> > > signal their maximum delay somehow.  Or would the TCMTF
> >> >> >> > > function
> >> >> >> determine
> >> >> >> > > the maximum delay, using some heuristic?
> >> >> >> > >
> >> >> >> > > How does the TCMTF function determine how much of that
> >> >> >> > > 'tolerable latency' budget it can consume?
> >> >> >> > >
> >> >> >> > > -d
> >> >> >> > >
> >> >> >> > >
> >> >> >> > > > It is an extension of tcmtf
> >> >> >> > > > http://datatracker.ietf.org/doc/draft-
> >> >> >> > > > saldana-tsvwg-tcmtf/. Since a specific list for tcmtf
> >> >> >> > > > exists (tcmtf@ietf.org), the idea is to discuss it =
there.
> >> >> >> > > >
> >> >> >> > > >
> >> >> >> > > >
> >> >> >> > > > The draft contains recommendations for TCMTF =
multiplexing
> >> >> >> > > > period for different real-time services. In order to
> >> >> >> > > > prevent QoE degradation of real-time services using
> >> >> >> > > > TCMTF, a policy defining a multiplexing period can be
> >> >> >> > > > employed. Values of maximum tolerable delays presented =
in
> >> >> >> > > the
> >> >> >> > > > draft form the base of such policy.    The =
recommendations
> >>are
> >> >> >> > presented
> >> >> >> > > > for real-time network services in which TCTMF bandwidth
> >> >> >> > > > optimization is applicable (i.e., services  which have
> >> >> >> > > > low payload to header size ratio which results in high
> >> >> >> > > > protocol
> >> >> overhead).
> >> >> >> > > >
> >> >> >> > > >
> >> >> >> > > >
> >> >> >> > > > Your feedback will be welcome. Thank you.
> >> >> >> > > >
> >> >> >> > > >
> >> >> >> > > > Sincerely,
> >> >> >> > > >
> >> >> >> > > > Mirko Suznjevic
> >> >> >> > >
> >> >> >> > >
> >> >> >> > > _______________________________________________
> >> >> >> > > 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 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
> >>
> >>
> >> ________________________________
> >>
> >> 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
> >
>=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


From Mirko.Suznjevic@fer.hr  Fri Jan 18 02:15:29 2013
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 9577921F88E3; Fri, 18 Jan 2013 02:15:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 JFfXx19-UDM3; Fri, 18 Jan 2013 02:15:19 -0800 (PST)
Received: from mail.zvne.fer.hr (mail.zvne.fer.hr [161.53.66.5]) by ietfa.amsl.com (Postfix) with ESMTP id E137921F8867; Fri, 18 Jan 2013 02:15:16 -0800 (PST)
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.318.4; Fri, 18 Jan 2013 11:15:14 +0100
Received: from sluga.fer.hr ([161.53.66.244]) by munja.zvne.fer.hr with Microsoft SMTPSVC(6.0.3790.4675);	 Fri, 18 Jan 2013 11:15:03 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CDF564.AE14F110"
Date: Fri, 18 Jan 2013 11:15:02 +0100
Message-ID: <A3179A2C9AAEE647BE70AC4C7881D5FB0177615C@sluga.fer.hr>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A2689C99E8@EX10-MB2-MAD.hi.inet>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
Thread-Index: AQHN9JGjt/1wmNKQnUulDvKsi7PhJphO37Iw
References: <A3179A2C9AAEE647BE70AC4C7881D5FB0177608D@sluga.fer.hr> <F5EDC35DF914C1428C28E149F10463A2689C99E8@EX10-MB2-MAD.hi.inet>
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: FERNANDO PASCUAL BLANCO <fpb@tid.es>, <tcmtf@ietf.org>, <tsvwg@ietf.org>
X-OriginalArrivalTime: 18 Jan 2013 10:15:03.0356 (UTC) FILETIME=[AE4EFFC0:01CDF564]
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2013 10:15:29 -0000

------_=_NextPart_001_01CDF564.AE14F110
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

Yes I concur, it is a good notice. I am adding your comment to the =
review list for the next version.


Mirko Suznjevic

=20

From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]=20
Sent: Thursday, January 17, 2013 10:08 AM
To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org; tsvwg@ietf.org
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using =
Tunneling Compressed Multiplexed Traffic Flows

=20

Hi Mirko,

=20

Thank you for considering that. In addition, one more thing: in section =
4, the sentence "If a policy defining a multiplexing period is used, =
then the average latency added to each packet will be half the =
multiplexing period." only applies when there is not enough packet rate =
to fulfill a big packet by multiplexing small ones. When  there is a lot =
of packets to multiplex, in general, multiplexing period will not be =
reached, so half the multiplexing period will be the maximum/worse =
average added delay. In general, and when TCMTF is working fine, average =
added delay will be lower.

So, I would rewrite that phrase as: "If a policy defining a multiplexing =
period is used, then the average latency added to each packet will be =
half the time to fulfill a multiplexed one. In the worse case and if the =
multiplexing period is reached, the average latency added to each packet =
will be half the multiplexing period".

=20

What do you think?

=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: Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr>
Date: martes, 15 de enero de 2013 16:48
To: Fernando Pascual Blanco <fpb@tid.es>, "tcmtf@ietf.org" =
<tcmtf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using =
Tunneling Compressed Multiplexed Traffic Flows

=20

Hello,

Thanks for all the comments, I will briefly respond to them, and include =
your (as well as previous) corrections in a new version of the draft:

*	I do not understand the sentence "Therefore, we neither take into =
account services using an approach in which all the calculations are =
deployed in the server, which sends a real-time video stream to the =
client." in section 3.

The meaning of this sentence is that we will not be looking at the cloud =
based gaming services such as OnLive or Gaiki as they are focused on =
performing all needed calculations of the gamestate on the server, and =
sending a very "fat" video stream to the client which only renders the =
video. Therefore they are not suitable for tcmtf. I will change that in =
order to be more clear.

*	In section 3 (Considered Services), I think it could be also =
interesting to consider non-real time services candidates to be TCMTF =
optimized. For example services like instant messaging, where the =
bandwidth saving is the main benefit of the TCMTF optimization, should =
be somehow mentioned, establishing a kind of delay upper threshold. =
Related to that, in section 3, when talking about web browsing, the =
sentence "there is no need for policy limitations in TCMTF" could be =
disappointed, because actually there are limitations (ITU-T_G.1010, 10 =
seconds for web browsing, as in section 4.1 10 seconds are considered =
for streaming audio).

At first when we were discussing we decided that it will be focused on =
real-time services, but this can be broadened to others non-real-time. I =
think giving such upper limits has a point, although would we even =
employ tcmtf in cases  in which we will not have enough data to send a =
packet in 5 or more seconds? Is that feasible? Maybe in some sensor =
networks? Maybe I am just looking it the wrong way, maybe we would have =
a lot of traffic that needs to be packed ASAP!

*	In section 4, I would change the sentence "A number of flows are =
multiplexed together before being sent through the Internet." for "A =
number of flows are multiplexed together before being sent through the =
network.", because the network could not be necessary the Internet, I =
would also adapt Figure 2.

Ok will be done.

*	Maybe the creation of a section 4.4 talking about non real time =
services could be considered including last comments (acceptable with =
the recommendation appearing in the last sentence of the section 4.3 "It =
should be noted that multiplexing periods of about 1 second can be =
considered as enough for non real time services (e.g., web browsing and =
streaming audio).")

Ok, seems sound enough. I will write it and see which format looks =
better.

*	Table 1 could be included in a separate section (i.e. Section 4.5) as =
a summary

Ok.

=20

Thanks again for the feedback!

Cheers!
Mirko

=20

From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]=20
Sent: Tuesday, January 15, 2013 3:42 PM
To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org; tsvwg@ietf.org
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using =
Tunneling Compressed Multiplexed Traffic Flows

=20

Hi Mirko,

=20

Some comments to the draft:

*	In the introduction it says "TCTMF", it is "TCMTF".
*	I do not understand the sentence "Therefore, we neither take into =
account services using an approach in which all the calculations are =
deployed in the server, which sends a real-time video stream to the =
client." in section 3.
*	In section 3 (Considered Services), I think it could be also =
interesting to consider non-real time services candidates to be TCMTF =
optimized. For example services like instant messaging, where the =
bandwidth saving is the main benefit of the TCMTF optimization, should =
be somehow mentioned, establishing a kind of delay upper threshold. =
Related to that, in section 3, when talking about web browsing, the =
sentence "there is no need for policy limitations in TCMTF" could be =
disappointed, because actually there are limitations (ITU-T_G.1010, 10 =
seconds for web browsing, as in section 4.1 10 seconds are considered =
for streaming audio).
*	In section 4, I would change the sentence "A number of flows are =
multiplexed together before being sent through the Internet." for "A =
number of flows are multiplexed together before being sent through the =
network.", because the network could not be necessary the Internet, I =
would also adapt Figure 2.
*	Maybe the creation of a section 4.4 talking about non real time =
services could be considered including last comments (acceptable with =
the recommendation appearing in the last sentence of the section 4.3 "It =
should be noted that multiplexing periods of about 1 second can be =
considered as enough for non real time services (e.g., web browsing and =
streaming audio).")
*	Table 1 could be included in a separate section (i.e. Section 4.5) as =
a summary

Hope to help!

=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: Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr>
Date: jueves, 13 de diciembre de 2012 10:06
To: "tcmtf@ietf.org" <tcmtf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling =
Compressed Multiplexed Traffic Flows

=20

Hello,

=20

We have just submitted the draft named Maximum Tolerable Delays when =
using Tunneling Compressed Multiplexed Traffic Flows: =
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/

=20

It is an extension of tcmtf =
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/. Since a =
specific list for tcmtf exists (tcmtf@ietf.org), the idea is to discuss =
it there.

=20

The draft contains recommendations for TCMTF multiplexing period for =
different real-time services. In order to prevent QoE degradation of =
real-time services using TCMTF, a policy defining  a multiplexing period =
can be employed. Values of maximum tolerable delays presented in the =
draft form the base of such policy.    The recommendations are presented =
for real-time network services in which TCTMF bandwidth optimization is =
applicable (i.e., services  which have low payload to header size ratio =
which results in high protocol overhead).

=20

Your feedback will be welcome. Thank you.


Sincerely,

Mirko Suznjevic

=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

=20

________________________________


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


------_=_NextPart_001_01CDF564.AE14F110
Content-Type: text/html; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-2">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 12 (filtered medium)"><!--[if =
!mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	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.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
span.emailstyle17
	{mso-style-name:emailstyle17;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.emailstyle19
	{mso-style-name:emailstyle19;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.balloontextchar0
	{mso-style-name:balloontextchar;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle25
	{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 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:204412190;
	mso-list-template-ids:-1276223818;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:1492870025;
	mso-list-template-ids:-1264823850;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2
	{mso-list-id:1530142094;
	mso-list-template-ids:163602884;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3
	{mso-list-id:1534347909;
	mso-list-template-ids:273075542;}
@list l3:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4
	{mso-list-id:1862544740;
	mso-list-template-ids:361497012;}
@list l4:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l5
	{mso-list-id:2030912929;
	mso-list-template-ids:-825095628;}
@list l5:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
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=3DHR link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Yes I concur, it is a good notice. =
I am adding your comment to the review list for the next =
version.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><br>Mirko Suznjevic<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> FERNANDO =
PASCUAL BLANCO [mailto:fpb@tid.es] <br><b>Sent:</b> Thursday, January =
17, 2013 10:08 AM<br><b>To:</b> Mirko Su=BEnjevi=E6; tcmtf@ietf.org; =
tsvwg@ietf.org<br><b>Subject:</b> Re: [tcmtf] Draft: Maximum Tolerable =
Delays when using Tunneling Compressed Multiplexed Traffic =
Flows<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><div><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Hi =
Mirko,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Thank you for considering that. =
In addition, one more thing: in section 4, the sentence &quot;If a =
policy defining a multiplexing period is used, then the =
average&nbsp;latency added to each packet will be half the multiplexing =
period.&quot; only applies when there is not enough packet rate to =
fulfill a big packet by multiplexing small ones. When &nbsp;there is a =
lot of packets to multiplex, in general, multiplexing period will not be =
reached, so half the multiplexing period will be the maximum/worse =
average added delay. In general, and when TCMTF is working fine, average =
added delay will be lower.<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>So, I would rewrite that phrase =
as: &quot;If a policy defining a multiplexing period is used, then the =
average&nbsp;latency added to each packet will be half the time to =
fulfill a multiplexed one. In the worse case and if the multiplexing =
period is reached, the average latency added to each packet will be half =
the multiplexing period&quot;.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>What do you =
think?<o:p></o:p></span></p></div><div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Regards,<o:p></o:p></span></p></di=
v><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Fernando Pascual =
Blanco<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>Telef=F3nica Global =
Resources<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>Network Automation =
and Dynamization<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>TECHNOLOGY PEOPLE =
GROUP<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>F =
+34913128779<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>M =
+34682005168<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US 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><p class=3DMsoNormal><span lang=3DEN-US =
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 lang=3DEN-US =
style=3D'color:black'>From: </span></b><span lang=3DEN-US =
style=3D'color:black'>Mirko Su=BEnjevi=E6 &lt;<a =
href=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt;<br>=
<b>Date: </b>martes, 15 de enero de 2013 16:48<br><b>To: </b>Fernando =
Pascual Blanco &lt;<a href=3D"mailto:fpb@tid.es">fpb@tid.es</a>&gt;, =
&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;, &quot;<a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&gt;<br><b>Subject: =
</b>Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling =
Compressed Multiplexed Traffic Flows<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Hello,</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Thanks for all the comments, I will =
briefly respond to them, and include your (as well as previous) =
corrections in a new version of the draft:</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><ul style=3D'margin-top:0cm' =
type=3Ddisc><li class=3DMsoNormal style=3D'color:black;mso-list:l3 =
level1 lfo1'><span lang=3DEN-US style=3D'font-size:10.5pt'>I do not =
understand the sentence &quot;Therefore, we&nbsp;neither take into =
account services using an approach in which all the&nbsp;calculations =
are deployed in the server, which sends a real-time&nbsp;video stream to =
the client.&quot; in section 3.</span><span =
lang=3DEN-US><o:p></o:p></span></li></ul><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>The meaning of this sentence is =
that we will not be looking at the cloud based gaming services such as =
OnLive or Gaiki as they are focused on performing all needed =
calculations of the gamestate on the server, and sending a very =
&#8220;fat&#8221; video stream to the client which only renders the =
video. Therefore they are not suitable for tcmtf. I will change that in =
order to be more clear.</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><ul style=3D'margin-top:0cm' =
type=3Ddisc><li class=3DMsoNormal style=3D'color:black;mso-list:l0 =
level1 lfo2'><span lang=3DEN-US style=3D'font-size:10.5pt'>In section 3 =
(Considered Services), I think it could be also interesting to consider =
non-real time services candidates to be TCMTF optimized. For example =
services like instant messaging, where the bandwidth saving is the main =
benefit of the TCMTF optimization, should be somehow mentioned, =
establishing a kind of delay upper threshold. Related to that, in =
section 3, when talking about web browsing, the sentence &quot;there is =
no need for policy&nbsp;limitations in TCMTF&quot; could =
be&nbsp;disappointed, because actually there are limitations =
(ITU-T_G.1010,&nbsp;10 seconds for web browsing, as in section 4.1 10 =
seconds are considered for streaming audio).</span><span =
lang=3DEN-US><o:p></o:p></span></li></ul><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>At first when we were discussing we =
decided that it will be focused on real-time services, but this can be =
broadened to others non-real-time. I think giving such upper limits has =
a point, although would we even employ tcmtf in cases &nbsp;in which we =
will not have enough data to send a packet in 5 or more seconds? Is that =
feasible? Maybe in some sensor networks? Maybe I am just looking it the =
wrong way, maybe we would have a lot of traffic that needs to be packed =
ASAP!</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><ul style=3D'margin-top:0cm' =
type=3Ddisc><li class=3DMsoNormal style=3D'color:black;mso-list:l4 =
level1 lfo3'><span lang=3DEN-US style=3D'font-size:10.5pt'>In section 4, =
I would change the sentence &quot;A number of flows are =
multiplexed&nbsp;together before being sent through the Internet.&quot; =
for &quot;A number of flows are multiplexed&nbsp;together before being =
sent through the network.&quot;, because the network could not be =
necessary the Internet, I would also adapt Figure 2.</span><span =
lang=3DEN-US><o:p></o:p></span></li></ul><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Ok will be done.</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p><ul =
style=3D'margin-top:0cm' type=3Ddisc><li class=3DMsoNormal =
style=3D'color:black;mso-list:l1 level1 lfo4'><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Maybe the creation of a section 4.4 talking =
about non real time services could be considered including last comments =
(acceptable with the recommendation appearing in the last sentence of =
the section 4.3 &quot;</span><span lang=3DEN-US>It should be =
noted&nbsp;that multiplexing periods of about 1 second can be considered =
as&nbsp;enough for non real time services (e.g., web browsing and =
streaming&nbsp;audio).&quot;)<o:p></o:p></span></li></ul><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Ok, seems =
sound enough. I will write it and see which format looks =
better.</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><ul style=3D'margin-top:0cm' =
type=3Ddisc><li class=3DMsoNormal style=3D'color:black;mso-list:l5 =
level1 lfo5'><span lang=3DEN-US>Table 1 could be included in a separate =
section (i.e.&nbsp;Section 4.5) as a =
summary<o:p></o:p></span></li></ul><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Ok.</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Thanks again for the =
feedback!</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Cheers!<br>Mirko</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
 FERNANDO PASCUAL BLANCO [<a =
href=3D"mailto:fpb@tid.es">mailto:fpb@tid.es</a>] <br><b>Sent:</b> =
Tuesday, January 15, 2013 3:42 PM<br><b>To:</b> Mirko Su=BEnjevi=E6; <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>; <a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a><br><b>Subject:</b> Re: =
[tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed =
Multiplexed Traffic Flows</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Hi Mirko,</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Some comments to the =
draft:</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><ul =
style=3D'margin-top:0cm' type=3Ddisc><li class=3DMsoNormal =
style=3D'color:black;mso-list:l2 level1 lfo6'><span lang=3DEN-US =
style=3D'font-size:10.5pt'>In the introduction it says =
&quot;TCTMF&quot;, it is &quot;TCMTF&quot;.</span><span =
lang=3DEN-US><o:p></o:p></span></li><li class=3DMsoNormal =
style=3D'color:black;mso-list:l2 level1 lfo6'><span lang=3DEN-US =
style=3D'font-size:10.5pt'>I do not understand the sentence =
&quot;Therefore, we&nbsp;neither take into account services using an =
approach in which all the&nbsp;calculations are deployed in the server, =
which sends a real-time&nbsp;video stream to the client.&quot; in =
section 3.</span><span lang=3DEN-US><o:p></o:p></span></li><li =
class=3DMsoNormal style=3D'color:black;mso-list:l2 level1 lfo6'><span =
lang=3DEN-US style=3D'font-size:10.5pt'>In section 3 (Considered =
Services), I think it could be also interesting to consider non-real =
time services candidates to be TCMTF optimized. For example services =
like instant messaging, where the bandwidth saving is the main benefit =
of the TCMTF optimization, should be somehow mentioned, establishing a =
kind of delay upper threshold. Related to that, in section 3, when =
talking about web browsing, the sentence &quot;there is no need for =
policy&nbsp;limitations in TCMTF&quot; could be&nbsp;disappointed, =
because actually there are limitations (ITU-T_G.1010,&nbsp;10 seconds =
for web browsing, as in section 4.1 10 seconds are considered for =
streaming audio).</span><span lang=3DEN-US><o:p></o:p></span></li><li =
class=3DMsoNormal style=3D'color:black;mso-list:l2 level1 lfo6'><span =
lang=3DEN-US style=3D'font-size:10.5pt'>In section 4, I would change the =
sentence &quot;A number of flows are multiplexed&nbsp;together before =
being sent through the Internet.&quot; for &quot;A number of flows are =
multiplexed&nbsp;together before being sent through the network.&quot;, =
because the network could not be necessary the Internet, I would also =
adapt Figure 2.</span><span lang=3DEN-US><o:p></o:p></span></li><li =
class=3DMsoNormal style=3D'color:black;mso-list:l2 level1 lfo6'><span =
lang=3DEN-US style=3D'font-size:10.5pt'>Maybe the creation of a section =
4.4 talking about non real time services could be considered including =
last comments (acceptable with the recommendation appearing in the last =
sentence of the section 4.3 &quot;</span><span lang=3DEN-US>It should be =
noted&nbsp;that multiplexing periods of about 1 second can be considered =
as&nbsp;enough for non real time services (e.g., web browsing and =
streaming&nbsp;audio).&quot;)<o:p></o:p></span></li><li =
class=3DMsoNormal style=3D'color:black;mso-list:l2 level1 lfo6'><span =
lang=3DEN-US>Table 1 could be included in a separate section =
(i.e.&nbsp;Section 4.5) as a summary<o:p></o:p></span></li></ul><div><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>Hope to =
help!<o:p></o:p></span></p></div><div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Regards,</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Fernando Pascual =
Blanco</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Telef=F3nica Global =
Resources</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Network Automation and =
Dynamization</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>TECHNOLOGY PEOPLE =
GROUP</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>F +34913128779</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>M +34682005168</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><a =
href=3D"mailto:fpb@tid.es">fpb@tid.es</a></span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div></div></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'color:black'>From: </span></b><span lang=3DEN-US =
style=3D'color:black'>Mirko Su=BEnjevi=E6 &lt;<a =
href=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt;<br>=
<b>Date: </b>jueves, 13 de diciembre de 2012 10:06<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;, &quot;<a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&gt;<br><b>Subject: =
</b>[tcmtf] Draft: Maximum Tolerable Delays when using Tunneling =
Compressed Multiplexed Traffic Flows<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>Hello,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>We have just =
submitted the draft named Maximum Tolerable Delays when using Tunneling =
Compressed Multiplexed Traffic Flows: <a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a><o:p=
></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>It is an =
extension of tcmtf <a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http:=
//datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a>. Since a =
specific list for tcmtf exists (<a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>), the idea is to =
discuss it there.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>The draft =
contains recommendations for TCMTF multiplexing period for different =
real-time services. In order to prevent QoE degradation of real-time =
services using TCMTF, a policy defining&nbsp; a multiplexing period can =
be employed. Values of maximum tolerable delays presented in the draft =
form the base of such policy.&nbsp;&nbsp;&nbsp; The recommendations are =
presented for real-time network services in which TCTMF bandwidth =
optimization is applicable (i.e., services&nbsp; which have low payload =
to header size ratio which results in high protocol =
overhead).<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>Your feedback =
will be welcome. Thank you.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'><br>Sincerely,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>Mirko =
Suznjevic<o:p></o:p></span></p></div></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:black'><hr size=3D2 width=3D"100%" =
align=3Dcenter></span></div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br=
>Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico en el enlace situado m=E1s abajo.<br>This message is =
intended exclusively for its addressee. We only send and receive email =
on the basis of the terms set out at:<br><a =
href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/E=
S/PAGINAS/disclaimer.aspx</a></span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
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 =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'><hr size=3D2 =
width=3D"100%" align=3Dcenter></span></div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br=
>Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico en el enlace situado m=E1s abajo.<br>This message is =
intended exclusively for its addressee. We only send and receive email =
on the basis of the terms set out at:<br><a =
href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/E=
S/PAGINAS/disclaimer.aspx</a></span><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p></o:p></span></p></div></body=
></html>
------_=_NextPart_001_01CDF564.AE14F110--

From gorry@erg.abdn.ac.uk  Fri Jan 18 02:25:34 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F112421F88CA for <tcmtf@ietfa.amsl.com>; Fri, 18 Jan 2013 02:25:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ovVaY0i6ekgy for <tcmtf@ietfa.amsl.com>; Fri, 18 Jan 2013 02:25:33 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id DCA5221F88D6 for <tcmtf@ietf.org>; Fri, 18 Jan 2013 02:25:32 -0800 (PST)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id CAE5E2B44B4; Fri, 18 Jan 2013 10:25:31 +0000 (GMT)
Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 29B962B436A for <tcmtf@ietf.org>; Fri, 18 Jan 2013 10:25:28 +0000 (GMT)
Message-ID: <50F92318.30809@erg.abdn.ac.uk>
Date: Fri, 18 Jan 2013 10:25:28 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <009701cdf4ac$8af49750$a0ddc5f0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A2689D3F12@EX10-MB2-MAD.hi.inet> <009f01cdf4b9$aca39060$05eab120$@unizar.es>
In-Reply-To: <009f01cdf4b9$aca39060$05eab120$@unizar.es>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2013 10:25:35 -0000

If this is going to be used in the general Internet, then we need to 
decide whether there is one-way or two-way control connectivity. This 
will determine the constraints from a congestion control perspective. 
RTT and/or control feedback would be really helpful in establishing a 
congestion control or circuit-breaker function to ensure the traffic 
does not cause congestion collapse. Have you thought about this?

Gorry



On 17/01/2013 13:50, Jose Saldana wrote:
> In addition, perhaps we are too focused on online games and VoIP services. There are other services which are one-way: perhaps M2M communications do not require a two way communication. We can think about a number of sensors sending their measurements to a central server. So perhaps RTT will not even exist in this case.
>
> Jose
>
>> -----Mensaje original-----
>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>> Enviado el: jueves, 17 de enero de 2013 14:39
>> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko SuÅ¾njeviÄ‡'; 'JuliÃ¡n FernÃ¡ndez
>> Navajas'
>> CC: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling
>> Compressed Multiplexed Traffic Flows
>>
>> Jose,
>>
>>          LetÂ´s say that playing with the OWD you have more granularity in order to
>> know in which direction you need to reduce the delay by reducing the
>> multiplexing delay. But people with more knowledge about online games will
>> provide us more information for sure.
>>
>> Regards,
>>
>> Fernando Pascual Blanco
>> TelefÃ³nica Global Resources
>> Network Automation and Dynamization
>> TECHNOLOGY PEOPLE GROUP
>> F +34913128779
>> M +34682005168
>> fpb@tid.es
>>
>>
>>
>>
>> On 17/01/13 13:16, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>
>>> Fernando,
>>>
>>> So you may have this case:
>>> - your multiplexing delay limit is 50 ms
>>> - you have a lot of flows to multiplex, so perhaps the time between
>>> multiplexed packets will be 5 ms
>>> - you detect an increase in RTT
>>> - the system reacts and reduces multiplexing period
>>> - in fact, the reduction doesn't matter until the period is reduced to
>>> less than 5 ms
>>>
>>> So you only have to make this decision: using tcmtf with 5 ms period or
>>> not. If RTT is critical you may not be interested on saving bandwidth,
>>> but on reducing a bit the RTT.
>>>
>>> So I think your question is: what happens if the RTT is very big (out
>>> of
>>> limits) and you can save bandwidth using a 5ms multiplexing period?
>>>
>>> For example, the maximum RTT for a good quality is 80 ms and your
>>> network has 120 just now. In this case, perhaps having 125 doesn't
>>> matter, if you can save bandwidth.
>>>
>>> This makes sense, but it is a "extreme" case. However, would it be any
>>> advantage if OWD is used instead of RTT?
>>>
>>> Best regards,
>>>
>>> Jose
>>>
>>>> -----Mensaje original-----
>>>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]  Enviado el:
>>>> miÃ©rcoles, 16 de enero de 2013 12:52
>>>> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko SuÅ¾njeviÄ‡'; 'JuliÃ¡n
>>>> FernÃ¡ndez  Navajas'
>>>> CC: tcmtf@ietf.org
>>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
>>>> Tunneling  Compressed Multiplexed Traffic Flows
>>>>
>>>> Hi Jose,
>>>>
>>>>          You are right, but my point here is:
>>>>
>>>>                  Client - Mux - Demux - Server
>>>>
>>>>          Imagine that there is enough packets between mux and demux to
>>>> make  the added delay very small (TCMTF is working very well and the
>>>> mux has not  to wait the multiplexing period to fulfill a big packet
>>>> and send it, so imagine a  multiplexing period of 50 ms and a big
>>>> packet is fulfilled in 5 ms). If the RTT  get increased because a
>>>> congestion in the way back to the client (there is no  TCMTF
>>>> optimization) and we decrease the multiplexing period (even in the
>>>> extreme we can disable the TCMTF optimization) the high RTT will remain.
>>>> Even if the TCMTF optimization was helping in the client to server
>>>> path,  disabling it may harm. Do you think that scenario would be possible?
>>>>
>>>>          So IÂ´m not sure about that, I think we need more opinions here.
>>>>
>>>> Regards,
>>>>
>>>> Fernando Pascual Blanco
>>>> TelefÃ³nica Global Resources
>>>> Network Automation and Dynamization
>>>> TECHNOLOGY PEOPLE GROUP
>>>> F +34913128779
>>>> M +34682005168
>>>> fpb@tid.es
>>>>
>>>>
>>>>
>>>>
>>>> On 16/01/13 11:57, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>>>
>>>>> My two cents:
>>>>>
>>>>> In games and in VoIP the really important thing is RTT:
>>>>>
>>>>> - Games always measure the RTT (gamers talk about the "ping"): the
>>>>> important thing is the delay from a player action to the server
>>>>> reaction arriving to the player's machine.
>>>>> - In VoIP I think it is the same: what matters is the RTT, in order
>>>>> to grant interactivity and avoiding cross-talk.
>>>>>
>>>>> In addition, RTT is easier to measure than OWD, since you don't need
>>>>> synchronization.
>>>>>
>>>>> And regarding Two-way TCMTF, I think we have to think about TCMTF as
>>>>> one-way. Otherwise, things would become very complicated. Some
>>>> services
>>>>> have very different client-server and server-client traffic patterns
>>>>> (e.g. games). In addition, sometimes the two flows can follow
>>>>> different network paths. I think once we talked about a network
>>>>> provider using a number of ISPs.
>>>>>
>>>>> However, using RTT for tuning a one-way TCMTF may not be bad... or
>>>>> is it bad? Any other thoughts?
>>>>>
>>>>> BR,
>>>>>
>>>>> Jose
>>>>>
>>>>>> -----Mensaje original-----
>>>>>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]  Enviado el:
>>>> martes,
>>>>>> 15 de enero de 2013 18:04
>>>>>> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko SuÅ¾njeviÄ‡'; JuliÃ¡n
>>>>>> FernÃ¡ndez  Navajas
>>>>>> CC: tcmtf@ietf.org
>>>>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
>>>>>> Tunneling  Compressed Multiplexed Traffic Flows
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>>          To re-open that issue, I would suggest that given that the
>>>>>> delay is so  sensitive in real time services, we need to find a
>>>>>> consensus here.
>>>>>>
>>>>>>          My opinion is that to apply the first possibility (the
>>>>>> static multiplexing
>>>>>> period) we need to suppose that the network conditions are really
>>>>>> bad, to be  protected when the network congestion arises. In that
>>>>>> case, the application  of the TCMTF optimization will not be
>>>>>> optimal, so that would be the less  preferred option, but easier to
>>>>>> implement and maintain over the time.
>>>>>>
>>>>>>          On the other hand, the second possibility would be the
>>>>>> preferred. It is  easy to know the delay between the mux and the
>>>>>> demux but most of the  times will not be enough unless mux and
>>>>>> demux were really near from the  client and the server
>>>>>> respectively. I agree with Jose in the possibility of snoop  RTCP
>>>>>> packets in order to adapt the multiplexing period when multiplexing
>>>>>> RTP packets (and RTCP is available). Talking about RTT, IÂ´m not
>>>>>> sure if RTT  would be useful given that the multiplexing period
>>>>>> only affect the one way  delay (OWD). Imagine the following scenario:
>>>>>>          - Client - Mux/Demux - Demux/Mux - Server (two ways TCMTF,
>>>>>> TWTCMTF :P)
>>>>>>          - The OWD from server to client get increased
>>>>>>          - The OWD from client to server remains equal
>>>>>>          - Should we use a lower multiplexing period in the client
>>>>>> to server  direction? I donÂ´t think soâ€¦ because we should use a
>>>>>> lower multiplexing  period in the other direction.
>>>>>>
>>>>>>          My point is that the multiplexing period should only be
>>>>>> affected by the  OWD and not by the RTT (or it may be application
>>>>>> dependent). How to  calculate the OWD? IÂ´ve been reading something
>>>>>> about OWAMP and it  seems that an specific software has to be
>>>>>> implemented in the client/server  side.
>>>>>> Can we assume that? Unfortunately I cannot contribute so much
>> hereâ€¦
>>>>>>          It is possible that for certain services the static (and
>>>>>> worst
>>>>>> case)
>>>>>> multiplexing period would be the better solution.
>>>>>>
>>>>>>          What do you think?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Fernando Pascual Blanco
>>>>>> TelefÃ³nica Global Resources
>>>>>> Network Automation and Dynamization TECHNOLOGY PEOPLE GROUP
>> F
>>>>>> +34913128779 M +34682005168 fpb@tid.es
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 17/12/12 12:25, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Julian and I have been discussing about this. Some ideas have
>>>> arisen.
>>>>>>> This is the summary.
>>>>>>>
>>>>>>> This would be the scheme of the system, including mux and demux:
>>>>>>>
>>>>>>> Real-time application ------- mux -------- internet ---------
>>>>>>> demux
>>>>>>> -------
>>>>>>> server
>>>>>>>
>>>>>>>
>>>>>>> I think perhaps the draft could say something like:
>>>>>>>
>>>>>>> When setting the multiplexing period, there are two possibilities:
>>>>>>>
>>>>>>> 1.- Static / permanent: At system setup time, network delays are
>>>>>>> measured, and a multiplexing period is selected and set in the
>>>>>> multiplexer.
>>>>>>>
>>>>>>> 2.- Dynamic: A mechanism is used so as to adapt to the evolution
>>>>>>> of network delays. In this case, different mechanisms can be used
>>>>>>> in order to obtain periodical end-to-end network delay
>>>>>>> estimations, which would be useful in order to set the multiplexing
>> period:
>>>>>>>
>>>>>>> - If the traffic is RTP, then RTCP packets containing the
>>>>>>> estimation could be analyzed in order to extract these values, as Dan
>> suggests.
>>>>>>> The question
>>>>>>> is: would that packets travel through the multiplexer?
>>>>>>> - If the traffic is TCP, perhaps something similar to the RTT
>>>>>>> estimation of TCP could be useful.
>>>>>>> - If the traffic is UDP, should the mux use something like OWAMP
>>>>>>> (http://tools.ietf.org/html/rfc4656) in order to calculate two
>>>>>>> delays (application to mux, and mux to server) and calculate the
>>>> sum?
>>>>>>>
>>>>>>>
>>>>>>> I think the draft is only supposed to report the maximum delays
>>>>>>> normally considered acceptable. Perhaps the additional mechanisms
>>>>>>> for calculating the RTT could just be suggested.
>>>>>>>
>>>>>>> What do you think?
>>>>>>>
>>>>>>> Jose
>>>>>>>
>>>>>>>> -----Mensaje original-----
>>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>>>>>>>> nombre de Dan Wing Enviado el: viernes, 14 de diciembre de 2012
>>>>>>>> 18:33
>>>>>>>> Para: jsaldana@unizar.es; 'Mirko SuÅ¾njeviÄ‡'
>>>>>>>> CC: tcmtf@ietf.org
>>>>>>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
>>>>>>>> Tunneling Compressed Multiplexed Traffic Flows
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Jose Saldana [mailto:jsaldana@unizar.es]
>>>>>>>>> Sent: Friday, December 14, 2012 2:58 AM
>>>>>>>>> To: 'Dan Wing'; 'Mirko SuÅ¾njeviÄ‡'
>>>>>>>>> Cc: tcmtf@ietf.org
>>>>>>>>> Subject: RE: [tcmtf] Draft: Maximum Tolerable Delays when
>>>>>>>>> using Tunneling Compressed Multiplexed Traffic Flows
>>>>>>>>>
>>>>>>>>> Dan,
>>>>>>>>>
>>>>>>>>> Regarding the use of the maximum delay, some days ago we
>>>>>>>>> discussed about
>>>>>>>>> it:
>>>>>>>>> the actual OWD of the network should be measured (or
>>>>>>>>> estimated) in order to know the maximum multiplexing period we
>> can set.
>>>>>>>>>
>>>>>>>>> We may have this formula, if thinking one-way:
>>>>>>>>>
>>>>>>>>> OWD  + Mux period/2  < tolerable_OWD
>>>>>>>>>
>>>>>>>>> If we think RTT:
>>>>>>>>>
>>>>>>>>> OWD + Mux period/2 + OWD back < 2*tolerable_OWD
>>>>>>>>>
>>>>>>>>> I don't know if we should include a mechanism for estimating
>>>>>>>>> OWD in tcmtf. I think this is more an implementation problem,
>>>>>>>>> which may be already solved.
>>>>>>>>
>>>>>>>> Yes, it's already solved end-to-end:  RTP with RTCP feedback
>>>>>>>> allows determining one way delay.
>>>>>>>>
>>>>>>>> But if something in the middle is multiplexing several packets
>>>>>>>> together,
>>>>>>> we
>>>>>>>> don't want it to add too much delay.  That thing in the middle
>>>>>>>> won't necessarily know the one way delay seen by the endpoints,
>>>>>>>> unless it analyzes the RTP and RTCP.  There are devices that do
>>>>>>>> that on the market,  mostly to diagnose where networks are
>>>>>>>> causing loss/delay with RTP flows.
>>>>>>>>
>>>>>>>>
>>>>>>>>> Another option is using some typical values, e.g. from
>>>>>>>>>
>> http://ipnetwork.bgtmo.ip.att.net/pws/global_network_avgs.htm
>>>>>>>>> l
>>>>>>>>>
>>>>>>>>> The draft includes some preliminary/recommended values for
>>>>>>>>> the Multiplexing Period. Is this interesting? Should we put
>>>>>>>>> the formula instead?
>>>>>>>>
>>>>>>>> It's probably sufficient as-is.
>>>>>>>>
>>>>>>>> -d
>>>>>>>>
>>>>>>>>> Mirko, another question: in online games, players usually
>>>>>>>>> talk about the "ping", and I think it means RTT. Don't you
>>>>>>>>> think it would be better to define a RTT limit instead of a
>>>>>>>>> OWD one in that
>>>>>> case?
>>>>>>>>>
>>>>>>>>> What do you think?
>>>>>>>>>
>>>>>>>>> Jose
>>>>>>>>>
>>>>>>>>>> -----Mensaje original-----
>>>>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org]
>>>>>>>>>> En nombre de Dan Wing Enviado el: jueves, 13 de diciembre
>>>>>>>>>> de 2012
>>>>>>>>>> 17:07
>>>>>>>>>> Para: 'Mirko SuÅ¾njeviÄ‡'; tcmtf@ietf.org
>>>>>>>>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when
>>>>>>>>>> using Tunneling Compressed Multiplexed Traffic Flows
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: tcmtf-bounces@ietf.org
>>>>>>>>>>> [mailto:tcmtf-bounces@ietf.org] On Behalf Of Mirko
>>>>>>>>>>> SuÅ¾njevic
>>>>>>>>>>> Sent: Thursday, December 13, 2012 1:07 AM
>>>>>>>>>>> To: tcmtf@ietf.org; tsvwg@ietf.org
>>>>>>>>>>> Subject: [tcmtf] Draft: Maximum Tolerable Delays when
>>>>>>>>>>> using Tunneling Compressed Multiplexed Traffic Flows
>>>>>>>>>>>
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> We have just submitted the draft named Maximum Tolerable
>>>>>>>>>>> Delays when using Tunneling Compressed Multiplexed
>>>>>>>>>>> Traffic
>>>> Flows:
>>>>>>>>>>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd
>>>>>>>>>>> -tc
>>>>>>>>>>> mtf
>>>>>>>>>>> /
>>>>>>>>>>
>>>>>>>>>> The suggested 400ms for interactive voice is at least 2x
>>>>>>>>>> too
>>>>>> high.
>>>>>>>>>> I
>>>>>>>>> expect
>>>>>>>>>> that number does not include the playout jitter buffer
>>>>>>>>>> (which is variable,
>>>>>>>>> but
>>>>>>>>>> usually a few samples, so 40-80ms).  200ms end-to-end is
>>>>>>>>>> the higher end,
>>>>>>>>> and
>>>>>>>>>> that includes jitter buffer, codec processing, and so on.
>>>>>>>>>>
>>>>>>>>>> But, more importantly:  it seems valuable for endpoints to
>>>>>>>>>> signal their maximum delay somehow.  Or would the TCMTF
>>>>>>>>>> function
>>>>>>>> determine
>>>>>>>>>> the maximum delay, using some heuristic?
>>>>>>>>>>
>>>>>>>>>> How does the TCMTF function determine how much of that
>>>>>>>>>> 'tolerable latency' budget it can consume?
>>>>>>>>>>
>>>>>>>>>> -d
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> It is an extension of tcmtf
>>>>>>>>>>> http://datatracker.ietf.org/doc/draft-
>>>>>>>>>>> saldana-tsvwg-tcmtf/. Since a specific list for tcmtf
>>>>>>>>>>> exists (tcmtf@ietf.org), the idea is to discuss it there.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The draft contains recommendations for TCMTF multiplexing
>>>>>>>>>>> period for different real-time services. In order to
>>>>>>>>>>> prevent QoE degradation of real-time services using
>>>>>>>>>>> TCMTF, a policy defining a multiplexing period can be
>>>>>>>>>>> employed. Values of maximum tolerable delays presented in
>>>>>>>>>> the
>>>>>>>>>>> draft form the base of such policy.    The recommendations
>>>> are
>>>>>>>>> presented
>>>>>>>>>>> for real-time network services in which TCTMF bandwidth
>>>>>>>>>>> optimization is applicable (i.e., services  which have
>>>>>>>>>>> low payload to header size ratio which results in high
>>>>>>>>>>> protocol
>>>>>> overhead).
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Your feedback will be welcome. Thank you.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Sincerely,
>>>>>>>>>>>
>>>>>>>>>>> Mirko Suznjevic
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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 nuestra polÃ­tica de envÃ­o y recepciÃ³n de correo
>>>>>> electrÃ³nico en el enlace situado mÃ¡s abajo.
>>>>>> This message is intended exclusively for its addressee. We only
>>>>>> send and receive email on the basis of the terms set out at:
>>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>>>>>
>>>>> _______________________________________________
>>>>> tcmtf mailing list
>>>>> tcmtf@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> 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
> https://www.ietf.org/mailman/listinfo/tcmtf
>


From mramalho@cisco.com  Fri Jan 18 06:05:27 2013
Return-Path: <mramalho@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAAFD21F889A; Fri, 18 Jan 2013 06:05:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.448
X-Spam-Level: 
X-Spam-Status: No, score=-10.448 tagged_above=-999 required=5 tests=[AWL=-0.151, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
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 qLTGS-m1ZrZb; Fri, 18 Jan 2013 06:05:21 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id BD1B621F883F; Fri, 18 Jan 2013 06:05:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=46971; q=dns/txt; s=iport; t=1358517920; x=1359727520; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=TMYsqVxcK26SvOHBHceBs5sdXQtj8yA/tyCiD1jReio=; b=RWWns5nclJf3vBlwYQDD2E4nmkAEDNlZELn3XD56epQ6NhtdvQ9sURm5 2jfw/Y5k8187AxOKVx2xEXI00xrQxJXrXPNJbqonnUy6N0pjzm9BBN3QL wfvJmBS/il8gUX9LyxMUOj7SjTQGK8JPnpps0JLu7MdWCmDAUz7YsXGhi U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFADBV+VCtJXHA/2dsb2JhbABFgkipOYkMAYkqFnOCHgEBAQQaE0YWAgEIEQMBAQELCwsBAgQHMhQJCAIEARIIiBEMvB2MdgsLeIJUYQOSWYRPjy2CdYFmAQYCFx4
X-IronPort-AV: E=Sophos;i="4.84,492,1355097600";  d="scan'208,217";a="164422137"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-8.cisco.com with ESMTP; 18 Jan 2013 14:05:19 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r0IE5JZ9000549 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Jan 2013 14:05:19 GMT
Received: from xmb-rcd-x12.cisco.com ([169.254.2.163]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Fri, 18 Jan 2013 08:05:18 -0600
From: "Michael Ramalho (mramalho)" <mramalho@cisco.com>
To: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>, "FERNANDO PASCUAL BLANCO" <fpb@tid.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
Thread-Index: AQHN9WTCfb61mh1Pz0K8TME3OxMO+ZhPGtzw
Date: Fri, 18 Jan 2013 14:05:18 +0000
Message-ID: <D21571530BF9644D9A443D6BD95B9103154C4245@xmb-rcd-x12.cisco.com>
References: <A3179A2C9AAEE647BE70AC4C7881D5FB0177608D@sluga.fer.hr> <F5EDC35DF914C1428C28E149F10463A2689C99E8@EX10-MB2-MAD.hi.inet> <A3179A2C9AAEE647BE70AC4C7881D5FB0177615C@sluga.fer.hr>
In-Reply-To: <A3179A2C9AAEE647BE70AC4C7881D5FB0177615C@sluga.fer.hr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.168.119]
Content-Type: multipart/alternative; boundary="_000_D21571530BF9644D9A443D6BD95B9103154C4245xmbrcdx12ciscoc_"
MIME-Version: 1.0
Subject: Re: [tcmtf] [tsvwg] Draft: Maximum Tolerable Delays when using	Tunneling Compressed Multiplexed Traffic Flows
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2013 14:05:27 -0000

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

All,

Strictly speaking, the sentence ""If a policy defining a multiplexing perio=
d is used, then the average latency added to each packet will be half the m=
ultiplexing period."" makes an explicit assumption that the packet arrivals=
 (for TCMTF packets) are random/uniform (or even that the arrival pdf is on=
e sided, with the most of the pdf area/contribution below the mean delay).

Why even go there?

If someone has such a "policy" ... the policy is to define the maximum wors=
t-case TCMTF (encoding) delay. If the TCMTF encoder has not yet built a "ne=
ar-MTU" packet and the worst-case delay timer fires ... push the packet out=
!

The worst-case TCMTF delay we should introduce is determined by the packets=
 we want to multiplex within a TCMTF packet. If we knew their traffic class=
 ... we would have an idea of what the worst case should be. If we didn't, =
but rather made a reasonable assumption (for example, based on signature an=
alysis), then we push when our idea of what the worst case has been met.

Given that the sentence referenced above is not correct (it has an implicit=
 random arrival process assumption) - we need to clarify it if it is decide=
d to keep it.

As Gorry notes in the next email on this thread, some delay-based congestio=
n controls may respond to TCMTF-induced delay as an indication of increasin=
g congestion in their congestion control. Anything we can do to limit the m=
aximum delay (i.e., have a "nice" TCMTF-induced delay distribution) would b=
e appreciated.

Michael Ramalho

From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of M=
irko Su=BEnjevic
Sent: Friday, January 18, 2013 5:15 AM
To: FERNANDO PASCUAL BLANCO; tcmtf@ietf.org; tsvwg@ietf.org
Subject: Re: [tsvwg] [tcmtf] Draft: Maximum Tolerable Delays when using Tun=
neling Compressed Multiplexed Traffic Flows

Yes I concur, it is a good notice. I am adding your comment to the review l=
ist for the next version.

Mirko Suznjevic

From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
Sent: Thursday, January 17, 2013 10:08 AM
To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org; tsvwg@ietf.org
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling C=
ompressed Multiplexed Traffic Flows

Hi Mirko,

Thank you for considering that. In addition, one more thing: in section 4, =
the sentence "If a policy defining a multiplexing period is used, then the =
average latency added to each packet will be half the multiplexing period."=
 only applies when there is not enough packet rate to fulfill a big packet =
by multiplexing small ones. When  there is a lot of packets to multiplex, i=
n general, multiplexing period will not be reached, so half the multiplexin=
g period will be the maximum/worse average added delay. In general, and whe=
n TCMTF is working fine, average added delay will be lower.
So, I would rewrite that phrase as: "If a policy defining a multiplexing pe=
riod is used, then the average latency added to each packet will be half th=
e time to fulfill a multiplexed one. In the worse case and if the multiplex=
ing period is reached, the average latency added to each packet will be hal=
f the multiplexing period".

What do you think?

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: Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr<mailto:Mirko.Suznjevic@fe=
r.hr>>
Date: martes, 15 de enero de 2013 16:48
To: Fernando Pascual Blanco <fpb@tid.es<mailto:fpb@tid.es>>, "tcmtf@ietf.or=
g<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ietf.org>>, "tsvwg@i=
etf.org<mailto:tsvwg@ietf.org>" <tsvwg@ietf.org<mailto:tsvwg@ietf.org>>
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling C=
ompressed Multiplexed Traffic Flows

Hello,
Thanks for all the comments, I will briefly respond to them, and include yo=
ur (as well as previous) corrections in a new version of the draft:

  *   I do not understand the sentence "Therefore, we neither take into acc=
ount services using an approach in which all the calculations are deployed =
in the server, which sends a real-time video stream to the client." in sect=
ion 3.
The meaning of this sentence is that we will not be looking at the cloud ba=
sed gaming services such as OnLive or Gaiki as they are focused on performi=
ng all needed calculations of the gamestate on the server, and sending a ve=
ry "fat" video stream to the client which only renders the video. Therefore=
 they are not suitable for tcmtf. I will change that in order to be more cl=
ear.

  *   In section 3 (Considered Services), I think it could be also interest=
ing to consider non-real time services candidates to be TCMTF optimized. Fo=
r example services like instant messaging, where the bandwidth saving is th=
e main benefit of the TCMTF optimization, should be somehow mentioned, esta=
blishing a kind of delay upper threshold. Related to that, in section 3, wh=
en talking about web browsing, the sentence "there is no need for policy li=
mitations in TCMTF" could be disappointed, because actually there are limit=
ations (ITU-T_G.1010, 10 seconds for web browsing, as in section 4.1 10 sec=
onds are considered for streaming audio).
At first when we were discussing we decided that it will be focused on real=
-time services, but this can be broadened to others non-real-time. I think =
giving such upper limits has a point, although would we even employ tcmtf i=
n cases  in which we will not have enough data to send a packet in 5 or mor=
e seconds? Is that feasible? Maybe in some sensor networks? Maybe I am just=
 looking it the wrong way, maybe we would have a lot of traffic that needs =
to be packed ASAP!

  *   In section 4, I would change the sentence "A number of flows are mult=
iplexed together before being sent through the Internet." for "A number of =
flows are multiplexed together before being sent through the network.", bec=
ause the network could not be necessary the Internet, I would also adapt Fi=
gure 2.
Ok will be done.

  *   Maybe the creation of a section 4.4 talking about non real time servi=
ces could be considered including last comments (acceptable with the recomm=
endation appearing in the last sentence of the section 4.3 "It should be no=
ted that multiplexing periods of about 1 second can be considered as enough=
 for non real time services (e.g., web browsing and streaming audio).")
Ok, seems sound enough. I will write it and see which format looks better.

  *   Table 1 could be included in a separate section (i.e. Section 4.5) as=
 a summary
Ok.

Thanks again for the feedback!
Cheers!
Mirko

From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
Sent: Tuesday, January 15, 2013 3:42 PM
To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org<mailto:tcmtf@ietf.org>; tsvwg@ietf.=
org<mailto:tsvwg@ietf.org>
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling C=
ompressed Multiplexed Traffic Flows

Hi Mirko,

Some comments to the draft:

  *   In the introduction it says "TCTMF", it is "TCMTF".
  *   I do not understand the sentence "Therefore, we neither take into acc=
ount services using an approach in which all the calculations are deployed =
in the server, which sends a real-time video stream to the client." in sect=
ion 3.
  *   In section 3 (Considered Services), I think it could be also interest=
ing to consider non-real time services candidates to be TCMTF optimized. Fo=
r example services like instant messaging, where the bandwidth saving is th=
e main benefit of the TCMTF optimization, should be somehow mentioned, esta=
blishing a kind of delay upper threshold. Related to that, in section 3, wh=
en talking about web browsing, the sentence "there is no need for policy li=
mitations in TCMTF" could be disappointed, because actually there are limit=
ations (ITU-T_G.1010, 10 seconds for web browsing, as in section 4.1 10 sec=
onds are considered for streaming audio).
  *   In section 4, I would change the sentence "A number of flows are mult=
iplexed together before being sent through the Internet." for "A number of =
flows are multiplexed together before being sent through the network.", bec=
ause the network could not be necessary the Internet, I would also adapt Fi=
gure 2.
  *   Maybe the creation of a section 4.4 talking about non real time servi=
ces could be considered including last comments (acceptable with the recomm=
endation appearing in the last sentence of the section 4.3 "It should be no=
ted that multiplexing periods of about 1 second can be considered as enough=
 for non real time services (e.g., web browsing and streaming audio).")
  *   Table 1 could be included in a separate section (i.e. Section 4.5) as=
 a summary
Hope to help!

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: Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr<mailto:Mirko.Suznjevic@fe=
r.hr>>
Date: jueves, 13 de diciembre de 2012 10:06
To: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>, "tsvwg@ietf.org<mailto:tsvwg@ietf.org>" <tsvwg@ietf.org<mailto:ts=
vwg@ietf.org>>
Subject: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compr=
essed Multiplexed Traffic Flows

Hello,

We have just submitted the draft named Maximum Tolerable Delays when using =
Tunneling Compressed Multiplexed Traffic Flows: http://datatracker.ietf.org=
/doc/draft-suznjevic-tsvwg-mtd-tcmtf/

It is an extension of tcmtf http://datatracker.ietf.org/doc/draft-saldana-t=
svwg-tcmtf/. Since a specific list for tcmtf exists (tcmtf@ietf.org<mailto:=
tcmtf@ietf.org>), the idea is to discuss it there.

The draft contains recommendations for TCMTF multiplexing period for differ=
ent real-time services. In order to prevent QoE degradation of real-time se=
rvices using TCMTF, a policy defining  a multiplexing period can be employe=
d. Values of maximum tolerable delays presented in the draft form the base =
of such policy.    The recommendations are presented for real-time network =
services in which TCTMF bandwidth optimization is applicable (i.e., service=
s  which have low payload to header size ratio which results in high protoc=
ol overhead).

Your feedback will be welcome. Thank you.

Sincerely,
Mirko Suznjevic

________________________________

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

--_000_D21571530BF9644D9A443D6BD95B9103154C4245xmbrcdx12ciscoc_
Content-Type: text/html; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
2">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.emailstyle17
	{mso-style-name:emailstyle17;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.emailstyle19
	{mso-style-name:emailstyle19;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.balloontextchar0
	{mso-style-name:balloontextchar;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:204412190;
	mso-list-template-ids:-1276223818;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1492870025;
	mso-list-template-ids:-1264823850;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2
	{mso-list-id:1530142094;
	mso-list-template-ids:163602884;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3
	{mso-list-id:1534347909;
	mso-list-template-ids:273075542;}
@list l3:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4
	{mso-list-id:1862544740;
	mso-list-template-ids:361497012;}
@list l4:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l4:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5
	{mso-list-id:2030912929;
	mso-list-template-ids:-825095628;}
@list l5:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l5:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l5:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">All,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Strictly speaking, the=
 sentence &#8220;</span><span style=3D"font-size:10.5pt;color:black">&quot;=
If a policy defining a multiplexing period is used, then the average&nbsp;l=
atency added to each packet will be half the multiplexing
 period.&quot;</span><span style=3D"color:#1F497D">&#8221; makes an explici=
t assumption that the packet arrivals (for TCMTF packets) are random/unifor=
m (or even that the arrival pdf is one sided, with the most of the pdf area=
/contribution below the mean delay).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Why even go there?<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">If someone has such a =
&#8220;policy&#8221; &#8230; the policy is to define the maximum worst-case=
 TCMTF (encoding) delay. If the TCMTF encoder has not yet built a &#8220;ne=
ar-MTU&#8221; packet and the worst-case delay timer fires &#8230; push the
 packet out!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The worst-case TCMTF d=
elay we should introduce is determined by the packets we want to multiplex =
within a TCMTF packet. If we knew their traffic class &#8230; we would have=
 an idea of what the worst case should be.
 If we didn&#8217;t, but rather made a reasonable assumption (for example, =
based on signature analysis), then we push when our idea of what the worst =
case has been met.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Given that the sentenc=
e referenced above is not correct (it has an implicit random arrival proces=
s assumption) &#8211; we need to clarify it if it is decided to keep it.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">As Gorry notes in the =
next email on this thread, some delay-based congestion controls may respond=
 to TCMTF-induced delay as an indication of increasing congestion in their =
congestion control. Anything we can
 do to limit the maximum delay (i.e., have a &#8220;nice&#8221; TCMTF-induc=
ed delay distribution) would be appreciated.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Michael Ramalho<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tsvwg-bo=
unces@ietf.org [mailto:tsvwg-bounces@ietf.org]
<b>On Behalf Of </b>Mirko Su=BEnjevic<br>
<b>Sent:</b> Friday, January 18, 2013 5:15 AM<br>
<b>To:</b> FERNANDO PASCUAL BLANCO; tcmtf@ietf.org; tsvwg@ietf.org<br>
<b>Subject:</b> Re: [tsvwg] [tcmtf] Draft: Maximum Tolerable Delays when us=
ing Tunneling Compressed Multiplexed Traffic Flows<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Yes I concur, it is a =
good notice. I am adding your comment to the review list for the next versi=
on.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><br>
Mirko Suznjevic<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> FERNANDO=
 PASCUAL BLANCO [mailto:fpb@tid.es]
<br>
<b>Sent:</b> Thursday, January 17, 2013 10:08 AM<br>
<b>To:</b> Mirko Su=BEnjevi=E6; tcmtf@ietf.org; tsvwg@ietf.org<br>
<b>Subject:</b> Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunn=
eling Compressed Multiplexed Traffic Flows<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Mirk=
o,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Thank y=
ou for considering that. In addition, one more thing: in section 4, the sen=
tence &quot;If a policy defining a multiplexing period is used, then the av=
erage&nbsp;latency added to each packet will be
 half the multiplexing period.&quot; only applies when there is not enough =
packet rate to fulfill a big packet by multiplexing small ones. When &nbsp;=
there is a lot of packets to multiplex, in general, multiplexing period wil=
l not be reached, so half the multiplexing
 period will be the maximum/worse average added delay. In general, and when=
 TCMTF is working fine, average added delay will be lower.<o:p></o:p></span=
></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">So, I w=
ould rewrite that phrase as: &quot;If a policy defining a multiplexing peri=
od is used, then the average&nbsp;latency added to each packet will be half=
 the time to fulfill a multiplexed one. In the
 worse case and if the multiplexing period is reached, the average latency =
added to each packet will be half the multiplexing period&quot;.<o:p></o:p>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">What do=
 you think?<o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Regards=
,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Fernand=
o Pascual Blanco<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Telef=
=F3nica Global Resources<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Network=
 Automation and Dynamization<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">TECHNOL=
OGY PEOPLE GROUP<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">F &#43;=
34913128779<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">M &#43;=
34682005168<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><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>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">Mirko Su=BEnjevi=E6 &lt;<a href=3D"mailto:Mirko.Suz=
njevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt;<br>
<b>Date: </b>martes, 15 de enero de 2013 16:48<br>
<b>To: </b>Fernando Pascual Blanco &lt;<a href=3D"mailto:fpb@tid.es">fpb@ti=
d.es</a>&gt;, &quot;<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>&qu=
ot; &lt;<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>&gt;, &quot;<a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&quot; &lt;<a href=3D"mail=
to:tsvwg@ietf.org">tsvwg@ietf.org</a>&gt;<br>
<b>Subject: </b>Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunn=
eling Compressed Multiplexed Traffic Flows<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hello,</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks for all the com=
ments, I will briefly respond to them, and include your (as well as previou=
s) corrections in a new version of the draft:</span><span style=3D"color:bl=
ack"><o:p></o:p></span></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-list:l3 level1 lfo1"><span=
 style=3D"font-size:10.5pt">I do not understand the sentence &quot;Therefor=
e, we&nbsp;neither take into account services using an approach in which al=
l the&nbsp;calculations are deployed in the server, which
 sends a real-time&nbsp;video stream to the client.&quot; in section 3.</sp=
an><o:p></o:p></li></ul>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The meaning of this se=
ntence is that we will not be looking at the cloud based gaming services su=
ch as OnLive or Gaiki as they are focused on performing all needed calculat=
ions of the gamestate on the server,
 and sending a very &#8220;fat&#8221; video stream to the client which only=
 renders the video. Therefore they are not suitable for tcmtf. I will chang=
e that in order to be more clear.</span><span style=3D"color:black"><o:p></=
o:p></span></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-list:l0 level1 lfo2"><span=
 style=3D"font-size:10.5pt">In section 3 (Considered Services), I think it =
could be also interesting to consider non-real time services candidates to =
be TCMTF optimized. For example services
 like instant messaging, where the bandwidth saving is the main benefit of =
the TCMTF optimization, should be somehow mentioned, establishing a kind of=
 delay upper threshold. Related to that, in section 3, when talking about w=
eb browsing, the sentence &quot;there
 is no need for policy&nbsp;limitations in TCMTF&quot; could be&nbsp;disapp=
ointed, because actually there are limitations (ITU-T_G.1010,&nbsp;10 secon=
ds for web browsing, as in section 4.1 10 seconds are considered for stream=
ing audio).</span><o:p></o:p></li></ul>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">At first when we were =
discussing we decided that it will be focused on real-time services, but th=
is can be broadened to others non-real-time. I think giving such upper limi=
ts has a point, although would we even
 employ tcmtf in cases &nbsp;in which we will not have enough data to send =
a packet in 5 or more seconds? Is that feasible? Maybe in some sensor netwo=
rks? Maybe I am just looking it the wrong way, maybe we would have a lot of=
 traffic that needs to be packed ASAP!</span><span style=3D"color:black"><o=
:p></o:p></span></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-list:l4 level1 lfo3"><span=
 style=3D"font-size:10.5pt">In section 4, I would change the sentence &quot=
;A number of flows are multiplexed&nbsp;together before being sent through =
the Internet.&quot; for &quot;A number of flows are multiplexed&nbsp;togeth=
er
 before being sent through the network.&quot;, because the network could no=
t be necessary the Internet, I would also adapt Figure 2.</span><o:p></o:p>=
</li></ul>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Ok will be done.</span=
><span style=3D"color:black"><o:p></o:p></span></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-list:l1 level1 lfo4"><span=
 style=3D"font-size:10.5pt">Maybe the creation of a section 4.4 talking abo=
ut non real time services could be considered including last comments (acce=
ptable with the recommendation appearing
 in the last sentence of the section 4.3 &quot;</span>It should be noted&nb=
sp;that multiplexing periods of about 1 second can be considered as&nbsp;en=
ough for non real time services (e.g., web browsing and streaming&nbsp;audi=
o).&quot;)<o:p></o:p></li></ul>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Ok, seems sound enough=
. I will write it and see which format looks better.</span><span style=3D"c=
olor:black"><o:p></o:p></span></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-list:l5 level1 lfo5">Table=
 1 could be included in a separate section (i.e.&nbsp;Section 4.5) as a sum=
mary<o:p></o:p></li></ul>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Ok.</span><span style=
=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks again for the f=
eedback!</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Cheers!<br>
Mirko</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:black">From:</span></b><span sty=
le=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot=
;;color:black"> FERNANDO PASCUAL BLANCO [<a href=3D"mailto:fpb@tid.es">mail=
to:fpb@tid.es</a>]
<br>
<b>Sent:</b> Tuesday, January 15, 2013 3:42 PM<br>
<b>To:</b> Mirko Su=BEnjevi=E6; <a href=3D"mailto:tcmtf@ietf.org">tcmtf@iet=
f.org</a>; <a href=3D"mailto:tsvwg@ietf.org">
tsvwg@ietf.org</a><br>
<b>Subject:</b> Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunn=
eling Compressed Multiplexed Traffic Flows</span><span style=3D"color:black=
"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Mirk=
o,</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Some co=
mments to the draft:</span><span style=3D"color:black"><o:p></o:p></span></=
p>
</div>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-list:l2 level1 lfo6"><span=
 style=3D"font-size:10.5pt">In the introduction it says &quot;TCTMF&quot;, =
it is &quot;TCMTF&quot;.</span><o:p></o:p></li><li class=3D"MsoNormal" styl=
e=3D"color:black;mso-list:l2 level1 lfo6"><span style=3D"font-size:10.5pt">=
I do not understand the sentence &quot;Therefore, we&nbsp;neither take into=
 account services using an approach in which all the&nbsp;calculations are =
deployed in the server, which
 sends a real-time&nbsp;video stream to the client.&quot; in section 3.</sp=
an><o:p></o:p></li><li class=3D"MsoNormal" style=3D"color:black;mso-list:l2=
 level1 lfo6"><span style=3D"font-size:10.5pt">In section 3 (Considered Ser=
vices), I think it could be also interesting to consider non-real time serv=
ices candidates to be TCMTF optimized. For example services
 like instant messaging, where the bandwidth saving is the main benefit of =
the TCMTF optimization, should be somehow mentioned, establishing a kind of=
 delay upper threshold. Related to that, in section 3, when talking about w=
eb browsing, the sentence &quot;there
 is no need for policy&nbsp;limitations in TCMTF&quot; could be&nbsp;disapp=
ointed, because actually there are limitations (ITU-T_G.1010,&nbsp;10 secon=
ds for web browsing, as in section 4.1 10 seconds are considered for stream=
ing audio).</span><o:p></o:p></li><li class=3D"MsoNormal" style=3D"color:bl=
ack;mso-list:l2 level1 lfo6"><span style=3D"font-size:10.5pt">In section 4,=
 I would change the sentence &quot;A number of flows are multiplexed&nbsp;t=
ogether before being sent through the Internet.&quot; for &quot;A number of=
 flows are multiplexed&nbsp;together
 before being sent through the network.&quot;, because the network could no=
t be necessary the Internet, I would also adapt Figure 2.</span><o:p></o:p>=
</li><li class=3D"MsoNormal" style=3D"color:black;mso-list:l2 level1 lfo6">=
<span style=3D"font-size:10.5pt">Maybe the creation of a section 4.4 talkin=
g about non real time services could be considered including last comments =
(acceptable with the recommendation appearing
 in the last sentence of the section 4.3 &quot;</span>It should be noted&nb=
sp;that multiplexing periods of about 1 second can be considered as&nbsp;en=
ough for non real time services (e.g., web browsing and streaming&nbsp;audi=
o).&quot;)<o:p></o:p></li><li class=3D"MsoNormal" style=3D"color:black;mso-=
list:l2 level1 lfo6">Table 1 could be included in a separate section (i.e.&=
nbsp;Section 4.5) as a summary<o:p></o:p></li></ul>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hope to help!<o:p></o:p>=
</span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Regards=
,</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Fernand=
o Pascual Blanco</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Telef=
=F3nica Global Resources</span><span style=3D"color:black"><o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Network=
 Automation and Dynamization</span><span style=3D"color:black"><o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">TECHNOL=
OGY PEOPLE GROUP</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">F &#43;=
34913128779</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">M &#43;=
34682005168</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><a href=
=3D"mailto:fpb@tid.es">fpb@tid.es</a></span><span style=3D"color:black"><o:=
p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">Mirko Su=BEnjevi=E6 &lt;<a href=3D"mailto:Mirko.Suz=
njevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt;<br>
<b>Date: </b>jueves, 13 de diciembre de 2012 10:06<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;, &quot;<a hre=
f=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&quot; &lt;<a href=3D"mailto:=
tsvwg@ietf.org">tsvwg@ietf.org</a>&gt;<br>
<b>Subject: </b>[tcmtf] Draft: Maximum Tolerable Delays when using Tunnelin=
g Compressed Multiplexed Traffic Flows<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hello,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">We have just submitted t=
he draft named Maximum Tolerable Delays when using Tunneling Compressed Mul=
tiplexed Traffic Flows:
<a href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/=
">http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">It is an extension of tc=
mtf <a href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a>. Since a spe=
cific list for tcmtf exists (<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.o=
rg</a>), the idea is to discuss it there.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">The draft contains recom=
mendations for TCMTF multiplexing period for different real-time services. =
In order to prevent QoE degradation of real-time services using TCMTF, a po=
licy defining&nbsp; a multiplexing period
 can be employed. Values of maximum tolerable delays presented in the draft=
 form the base of such policy.&nbsp;&nbsp;&nbsp; The recommendations are pr=
esented for real-time network services in which TCTMF bandwidth optimizatio=
n is applicable (i.e., services&nbsp; which have low
 payload to header size ratio which results in high protocol overhead).<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Your feedback will be we=
lcome. Thank you.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><br>
Sincerely,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Mirko Suznjevic<o:p></o:=
p></span></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:black">&nbsp;</span><span style=
=3D"color:black"><o:p></o:p></span></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;se=
rif&quot;;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;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;;color:gray"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span style=3D"color:black"><o:p></o:p=
></span></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></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;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;;color:gray"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span style=3D"font-size:10.5pt;color:=
black"><o:p></o:p></span></p>
</div>
</body>
</html>

--_000_D21571530BF9644D9A443D6BD95B9103154C4245xmbrcdx12ciscoc_--

From mperumal@cisco.com  Sun Jan 20 21:40:53 2013
Return-Path: <mperumal@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BFA821F855C for <tcmtf@ietfa.amsl.com>; Sun, 20 Jan 2013 21:40:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tWWEG-Oam-Es for <tcmtf@ietfa.amsl.com>; Sun, 20 Jan 2013 21:40:48 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id A157421F8439 for <tcmtf@ietf.org>; Sun, 20 Jan 2013 21:40:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=38583; q=dns/txt; s=iport; t=1358746846; x=1359956446; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=/9CGprJbLz7O6pScEyZUkzNgg/GvT6ZUBYybhd9I8QQ=; b=ZfF5c+gQxHfoZrLwM7+7lpXfGrzGmbp4mxqD0MY1riHK8ru0J3VnlldH W/egJlaceXQvMK1b8w2ISysTtWhhP3aSVGm9p3nZgizJ5SNyrti1aD6pP AF75S9M7lIpb1pp6ShLgygowPvs3N0E3vfyha0v7lQTS6Gol0OVzjD12S Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkIFAOzT/FCtJV2Z/2dsb2JhbABEgkipPIkMAYknFnOCHgEBAQICLUwQAgEIEQMBAQELFgEGBzIUCQgBAQQBDQUIiBEMuwKNAYNXYQOILIothE+PLYJ1gW81
X-IronPort-AV: E=Sophos;i="4.84,504,1355097600";  d="scan'208,217";a="165380565"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP; 21 Jan 2013 05:40:44 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r0L5eiVJ013875 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 21 Jan 2013 05:40:44 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.64]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Sun, 20 Jan 2013 23:40:44 -0600
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: FERNANDO PASCUAL BLANCO <fpb@tid.es>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Thread-Topic: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a de-muxer
Thread-Index: Ac3z0qpuai7heI7oSHWY0AJDN9gmvgACrW2AAO2IJEA=
Date: Mon, 21 Jan 2013 05:40:44 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE223FD8899@xmb-rcd-x02.cisco.com>
References: <004601cdf3d2$dd332250$979966f0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A265043A0D@EX10-MB1-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A265043A0D@EX10-MB1-MAD.hi.inet>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.142.108.145]
Content-Type: multipart/alternative; boundary="_000_E721D8C6A2E1544DB2DEBC313AF54DE223FD8899xmbrcdx02ciscoc_"
MIME-Version: 1.0
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a de-muxer
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, 21 Jan 2013 05:40:53 -0000

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

Hi Fernando,

| I=B4m sure we will find a consensus about that :).

Sure..

|What Muthu proposes sounds interesting to me but, to be honest, I think TC=
MTF
|establishing should be quite similar to the establishing procedures of tun=
nels
|defined in draft A (L2TP, GRE...),

I agree the procedures for establishing the association b/w the muxer and t=
he de-muxer could be similar to those of establishing a tunnel. However, I =
would like us to avoid two assumptions:
1. The other end of a tunnel is always TCMTF capable. I think this is more =
important when you already have a tunnel (say, IPSec tunnel) and would like=
 to perform TCMTF on the fly.
2. A tunnel is always needed for performing TCMTF. If we aren't doing any c=
ompression, but only multiplexing, the outermost IP header would be intact =
and should suffice for routing the packets. There are satellite networks wh=
ere reducing the packets per second (pps) for VoIP calls is more important =
-- they don't do any compression, but only multiplexing, and don't setup a =
tunnel as well. For e.g:
http://www.cisco.com/web/strategy/docs/gov/aag_c45-697642_v2.pdf
http://www.cisco.com/web/strategy/docs/gov/ip_multiplexing_agensler.pptx

Nevertheless, I think all this go into the signaling doc. If we require cap=
ability negotiation, I think we can combine it with the procedure for estab=
lishing the association b/w the muxer and the de-muxer. If we make capabili=
ty negotiation as optional, we might want to keep those as separate procedu=
res.

Muthu

From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of F=
ERNANDO PASCUAL BLANCO
Sent: Wednesday, January 16, 2013 5:04 PM
To: jsaldana@unizar.es; Muthu Arul Mozhi Perumal (mperumal)
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discov=
er a de-muxer

Hi Jose, Muthu,

I=B4m sure we will find a consensus about that :). What Muthu proposes soun=
ds interesting to me but, to be honest, I think TCMTF establishing should b=
e quite similar to the establishing procedures of tunnels defined in draft =
A (L2TP, GRE...), actually at network level TCMTF is a tunnel. Once establi=
shed signaling will negotiate upper levels (multiplexing and HC) to perform=
 TCMTF (draft A).

What do you think?

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: mi=E9rcoles, 16 de enero de 2013 11:18
To: "'Muthu Arul Mozhi Perumal (mperumal) '" <mperumal@cisco.com<mailto:mpe=
rumal@cisco.com>>, 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: RV: [tcmtf] TCMTF: Document A: mechanism for a muxer to discover a=
 de-muxer


Fernando, Muthu, everyone,



Since there is no consensus about this, I think we should carry on with the=
 debate. Do you think the mechanism would be very complicated? Any new idea=
s?:



- *dynamically establishing, modifying and releasing tunnels*



#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.



There is still no consensus here:



Fernando: "Regarding #1, to be honest, I am not completely sure of the need=
 to specify a mechanism to discover muxes and demuxes between them. I think=
 those kind of mechanisms have more sense in local environments but I=B4m n=
ot sure if it applies here. At least at the beginning this associations can=
 be done manually."



Muthu: "I think it is the opposite -- in local environments you can provisi=
on/associate them manually. However, in a multi-vendor environment over the=
 Internet this should happen automatically."

"#1 needs to be specified."


Best regards,

Jose

De: tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-bou=
nces@ietf.org] En nombre de Jose Saldana
Enviado el: martes, 15 de enero de 2013 11:56
Para: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: [tcmtf] TCMTF: Document A discussion: content and charter

Document (A) refers to the main TCMTF draft, currently in http://datatracke=
r.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

1.- Content of the Document

Currently it contains the description of the question and the protocols whi=
ch could be used on each layer (tunneling, compressing, multiplexing). It s=
ays that the signaling issues would be that of each protocol.

There is consensus (I think) about this: we should include some signaling i=
ssues. The question is: What should we include in Draft A and what in Draft=
 C?

- *Auto-negotiation* Negotiation mechanisms to decide the options at each l=
ayer (compression, multiplexing and tunneling) between mux and demux. Perha=
ps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP and IPHC,=
 so the two machines will have to negotiate in order to decide which compre=
ssion protocol use.

This should be included in (A). I think there is consensus about this:
Juan Antonio: "The first kind of signaling ("auto-negotiation") is needed f=
rom the beginning if we don't want an extremely static protocol and therefo=
re possibly difficult to get it working, especially when in most of cases t=
he peers belong to different entities/companies."



Dan: "We need that -- it is capabilities negotiation.  It is needed because=
 the protocol will fail if one side mistakenly thinks the other side has ce=
rtain functionality, and because we will want to add some fancy new compres=
sion in the year 2020 and will need to negotiate it."



Fernando: "I also agree with the idea of including the mux-demux signaling =
within the draft A (as Dan said, they are capabilities negotiation). This d=
raft should be able to get two boxes with TCMTF fully working between them.=
 Under my point of view this includes the definition of the capabilities in=
 each node and the negotiation of that capabilities."



Does this mean that Document (A) will no longer be a Best Current Practice?=
 I think so.





- *dynamically establishing, modifying and releasing tunnels*



#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.



There is still no consensus here:



Fernando: "Regarding #1, to be honest, I am not completely sure of the need=
 to specify a mechanism to discover muxes and demuxes between them. I think=
 those kind of mechanisms have more sense in local environments but I=B4m n=
ot sure if it applies here. At least at the beginning this associations can=
 be done manually."



Muthu: "I think it is the opposite -- in local environments you can provisi=
on/associate them manually. However, in a multi-vendor environment over the=
 Internet this should happen automatically."

"#1 needs to be specified."







#2. A mechanism to *elect an optimal muxer and a de-muxer when there are mo=
re than one muxer/de-muxer for a flow*.



We agree: This can wait for Document (C).



                Fernando: "#2 is more related to the higher entity that has=
 to decide whether a flow should be TCMTFed or not, and under my point of v=
iew it can be addressed in a different draft."

                Muthu: "#2 can be added later."





3. A mechanism to *setup/release a tunnel b/w a muxer and a de-muxer*.



We agree: This has to be included in (A).



                Fernando "#3 I think should be included in the draft A, sin=
ce it is a mechanism within the TFMTF protocol itself."

                Muthu: "#3 many not require much specification."





2.- Should we include it in the Charter now?

Of course, Document (A) should be in the charter.


Best regards,

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

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	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:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
span.textosinformatocar
	{mso-style-name:textosinformatocar;
	font-family:"Calibri","sans-serif";}
span.estilocorreo19
	{mso-style-name:estilocorreo19;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.estilocorreo20
	{mso-style-name:estilocorreo20;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle26
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hi Fernando,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|</span>
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">I=B4m =
sure we will find a consensus about that :).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Sure..<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|What Muthu proposes sounds interesting to me but, to be h=
onest, I think TCMTF
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|establishing should be quite similar to the establishing =
procedures of tunnels
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|defined in draft A (L2TP, GRE&#8230;),<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">I agree the procedures for establishing the association b/=
w the muxer and the de-muxer could be similar to those of establishing a tu=
nnel. However, I would like us to avoid two assumptions:<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">1. The other end of a tunnel is always TCMTF capable. I th=
ink this is more important when you already have a tunnel (say, IPSec tunne=
l) and would like to perform TCMTF on the fly.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">2. A tunnel is always needed for performing TCMTF. If we a=
ren't doing any compression, but only multiplexing, the outermost IP header=
 would be intact and should suffice for routing
 the packets. There are satellite networks where reducing the packets per s=
econd (pps) for VoIP calls is more important -- they don't do any compressi=
on, but only multiplexing, and don't setup a tunnel as well. For e.g:<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><a href=3D"http://www.cisco.com/web/strategy/docs/gov/aag_=
c45-697642_v2.pdf">http://www.cisco.com/web/strategy/docs/gov/aag_c45-69764=
2_v2.pdf</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><a href=3D"http://www.cisco.com/web/strategy/docs/gov/ip_m=
ultiplexing_agensler.pptx">http://www.cisco.com/web/strategy/docs/gov/ip_mu=
ltiplexing_agensler.pptx</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Nevertheless, I think all this go into the signaling doc. =
If we require capability negotiation, I think we can combine it with the pr=
ocedure for establishing the association b/w the
 muxer and the de-muxer. If we make capability negotiation as optional, we =
might want to keep those as separate procedures.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Muthu<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tcmtf-bo=
unces@ietf.org [mailto:tcmtf-bounces@ietf.org]
<b>On Behalf Of </b>FERNANDO PASCUAL BLANCO<br>
<b>Sent:</b> Wednesday, January 16, 2013 5:04 PM<br>
<b>To:</b> jsaldana@unizar.es; Muthu Arul Mozhi Perumal (mperumal)<br>
<b>Cc:</b> tcmtf@ietf.org<br>
<b>Subject:</b> Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to=
 discover a de-muxer<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Jose=
, Muthu,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I=B4m s=
ure we will find a consensus about that :). What Muthu proposes sounds inte=
resting to me but, to be honest, I think TCMTF establishing should be quite=
 similar to the establishing procedures
 of tunnels defined in draft A (L2TP, GRE&#8230;), actually at network leve=
l TCMTF is a tunnel. Once established signaling will negotiate upper levels=
 (multiplexing and HC) to perform TCMTF (draft A).<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">What do=
 you think?<o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Regards=
,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Fernand=
o Pascual Blanco<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Telef=
=F3nica Global Resources<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Network=
 Automation and Dynamization<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">TECHNOL=
OGY PEOPLE GROUP<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">F &#43;=
34913128779<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">M &#43;=
34682005168<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><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>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span 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>mi=E9rcoles, 16 de enero de 2013 11:18<br>
<b>To: </b>&quot;'Muthu Arul Mozhi Perumal (mperumal) '&quot; &lt;<a href=
=3D"mailto:mperumal@cisco.com">mperumal@cisco.com</a>&gt;, Fernando Pascual=
 Blanco &lt;<a href=3D"mailto:fpb@tid.es">fpb@tid.es</a>&gt;<br>
<b>Cc: </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>RV: [tcmtf] TCMTF: Document A: mechanism for a muxer to dis=
cover a de-muxer<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoPlainText"><span style=3D"color:black">Fernando, Muthu, ever=
yone,</span><span lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Since there is no con=
sensus about this, I think we should carry on with the debate. Do you think=
 the mechanism would be very complicated? Any new ideas?:</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">- *<b>dynamically est=
ablishing, modifying and releasing tunnels</b>*</span><span lang=3D"ES" sty=
le=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">#1. A *<b>mechanism f=
or a muxer to discover a de-muxer (and vice versa)</b>*.</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">There is still no con=
sensus here:</span><span lang=3D"ES" style=3D"color:black"><o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Fernando: &#8220;Regarding #1, to be honest, I am not completely su=
re of the need to specify a mechanism to discover muxes and demuxes between=
 them. I think those kind of mechanisms have
 more sense in local environments but I=B4m not sure if it applies here. At=
 least at the beginning this associations can be done manually.&#8221;</spa=
n><span lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Muthu: &#8220;I think it is the opposite -- in local environments y=
ou can provision/associate them manually. However, in a multi-vendor enviro=
nment over the Internet this should happen automatically.&#8221;
</span><span lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt;text-indent:35.4pt"><=
span style=3D"color:black">&#8220;#1 needs to be specified.&#8221;</span><s=
pan lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">&nbsp;</sp=
an><span lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">&nbsp;</sp=
an><span lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">Best regar=
ds,</span><span lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D"><br>
Jose</span><span lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">&nbsp;</sp=
an><span lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"ES" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">De:</span></b=
><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;=
,&quot;sans-serif&quot;;color:black">
<a href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a hr=
ef=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]
<b>En nombre de </b>Jose Saldana<br>
<b>Enviado el:</b> martes, 15 de enero de 2013 11:56<br>
<b>Para:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tcmtf] TCMTF: Document A discussion: content and charter</s=
pan><span lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:black">&nbsp;<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Document (A) refers to t=
he main TCMTF draft, currently in
<a href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http=
://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a></span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">1.- Content of the Docum=
ent</span><span lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Currently it contains th=
e description of the question and the protocols which could be used on each=
 layer (tunneling, compressing, multiplexing). It says that the signaling i=
ssues would be that of each protocol.</span><span lang=3D"ES" style=3D"colo=
r:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">There is consensus (I th=
ink) about this: we should include some signaling issues. The question is: =
What should we include in Draft A and what in Draft C?</span><span lang=3D"=
ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">- *<b>Auto-negotiation</=
b>* Negotiation mechanisms to decide the options at each layer (compression=
, multiplexing and tunneling) between mux and demux. Perhaps the mux has RO=
HC, ECRTP and IPHC, and the demux only
 has ECRTP and IPHC, so the two machines will have to negotiate in order to=
 decide which compression protocol use.</span><span lang=3D"ES" style=3D"co=
lor:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">This should be included =
in (A). I think there is consensus about this:</span><span lang=3D"ES" styl=
e=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span style=3D"color:bl=
ack">Juan Antonio: &#8220;The first kind of signaling (&quot;auto-negotiati=
on&quot;) is needed from the beginning if we don't want an extremely static=
 protocol and therefore possibly difficult to get it working,
 especially when in most of cases the peers belong to different entities/co=
mpanies.&#8221;</span><span lang=3D"ES" style=3D"color:black"><o:p></o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">Dan: &#8220;We need that -- it is capabilities negotiation.&nbsp; =
It is needed because the protocol will fail if one side mistakenly thinks t=
he other side has certain functionality, and because
 we will want to add some fancy new compression in the year 2020 and will n=
eed to negotiate it.&#8221;</span><span lang=3D"ES" style=3D"color:black"><=
o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">&nbsp;</span><span lang=3D"ES" style=3D"color:black"><o:p></o:p></=
span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">Fernando: &#8220;I also agree with the idea of including the mux-d=
emux signaling within the draft A (as Dan said, they are capabilities negot=
iation). This draft should be able to get two
 boxes with TCMTF fully working between them. Under my point of view this i=
ncludes the definition of the capabilities in each node and the negotiation=
 of that capabilities.&#8221;</span><span lang=3D"ES" style=3D"color:black"=
><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Does this mean that D=
ocument (A) will no longer be a Best Current Practice? I think so.</span><s=
pan lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">- *<b>dynamically est=
ablishing, modifying and releasing tunnels</b>*</span><span lang=3D"ES" sty=
le=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">#1. A *<b>mechanism f=
or a muxer to discover a de-muxer (and vice versa)</b>*.</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">There is still no con=
sensus here:</span><span lang=3D"ES" style=3D"color:black"><o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Fernando: &#8220;Regarding #1, to be honest, I am not completely su=
re of the need to specify a mechanism to discover muxes and demuxes between=
 them. I think those kind of mechanisms have
 more sense in local environments but I=B4m not sure if it applies here. At=
 least at the beginning this associations can be done manually.&#8221;</spa=
n><span lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Muthu: &#8220;I think it is the opposite -- in local environments y=
ou can provision/associate them manually. However, in a multi-vendor enviro=
nment over the Internet this should happen automatically.&#8221;
</span><span lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt;text-indent:35.4pt"><=
span style=3D"color:black">&#8220;#1 needs to be specified.&#8221;</span><s=
pan lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">&nbsp;</span><span lang=3D"ES" style=3D"color:black"><o:p></o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">#2. A mechanism to *<=
b>elect an optimal muxer and a de-muxer when there are more than one muxer/=
de-muxer for a flow</b>*.</span><span lang=3D"ES" style=3D"color:black"><o:=
p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">We agree: This can wa=
it for Document (C).</span><span lang=3D"ES" style=3D"color:black"><o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ferna=
ndo: &#8220;#2 is more related to the higher entity that has to decide whet=
her a flow should be TCMTFed or not, and under my point of view it can be a=
ddressed in a different draft.&#8221;</span><span lang=3D"ES" style=3D"colo=
r:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu=
: &#8220;#2 can be added later.&#8221;</span><span lang=3D"ES" style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">3. A mechanism to *<b=
>setup/release a tunnel b/w a muxer and a de-muxer</b>*.</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">We agree: This has to=
 be included in (A).</span><span lang=3D"ES" style=3D"color:black"><o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ferna=
ndo &#8220;#3 I think should be included in the draft A, since it is a mech=
anism within the TFMTF protocol itself.&#8221;</span><span lang=3D"ES" styl=
e=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu=
: &#8220;#3 many not require much specification.&#8221;</span><span lang=3D=
"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">2.- Should we include=
 it in the Charter now?</span><span lang=3D"ES" style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Of course, Document (A) =
should be in the charter.</span><span lang=3D"ES" style=3D"color:black"><o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Best regards,</span><spa=
n lang=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Jose</span><span lang=3D=
"ES" style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:black">&nbsp;<o:p><=
/o:p></span></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></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;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;;color:gray"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span style=3D"font-size:10.5pt;color:=
black"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--_000_E721D8C6A2E1544DB2DEBC313AF54DE223FD8899xmbrcdx02ciscoc_--

From fpb@tid.es  Mon Jan 21 01:01:42 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F35521F868D for <tcmtf@ietfa.amsl.com>; Mon, 21 Jan 2013 01:01:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KtM4ClMYz5wm for <tcmtf@ietfa.amsl.com>; Mon, 21 Jan 2013 01:01:40 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 06B4121F867E for <tcmtf@ietf.org>; Mon, 21 Jan 2013 01:01:33 -0800 (PST)
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 <0MGY00A56X2FHL@tid.hi.inet> for tcmtf@ietf.org; Mon, 21 Jan 2013 10:01:31 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 91.B5.02896.BE30DF05; Mon, 21 Jan 2013 10:01:31 +0100 (CET)
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 <0MGY00A5VX2IHL@tid.hi.inet> for tcmtf@ietf.org; Mon, 21 Jan 2013 10:01:31 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.165]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0328.009; Mon, 21 Jan 2013 10:01:30 +0100
Date: Mon, 21 Jan 2013 09:01:30 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <E721D8C6A2E1544DB2DEBC313AF54DE223FD8899@xmb-rcd-x02.cisco.com>
X-Originating-IP: [10.95.64.115]
To: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Message-id: <F5EDC35DF914C1428C28E149F10463A2689E2EA9@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_iGJq5BfCq3ibA4gwxbO3fA)"
Content-language: en-US
Accept-Language: en-US
Thread-topic: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a de-muxer
Thread-index: AQHN95nqrakOPrux9Ea8FWSCk7gp5phTfKSA
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4e69-b7f636d000000b50-c6-50fd03eb4f88
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMKsWRmVeSWpSXmKPExsXCFe9nqPua+W+Aweq1Oha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxtTHbxkLFuxhqlgzxaCBcf1kpi5GTg4JAROJvReWsUDYYhIX 7q1nA7GFBLYxSjy5KN3FyAVk/2CUOPpwHxOEM5NR4vzHe8wgVSwCqhL/9v1jBbHZBLQkTt9d BTZJWCBK4suOKWAbOAV8JZbOfgK1TUHiz7nHYDUiAtkSH+/MB9rGwcEMNGfeN0UQk1fAW+Lo GrCJvAKCEj8m3wOrZhbIlWjomsYEYYtLNLfeBIszAt38/dQaJoiJ0RKbv88GmygiYCSxbZIC SFhUQE+i7dgZdogDBCSW7DnPDGGLSrx8/I91AqPYLCTbZiHZNgvJNgjbQOL9ufnMELa2xLKF r6FsfYmNX84yQthmEqsatzMiq1nAyLGKUaw4qSgzPaMkNzEzJ93ASC8jUy8zL7VkEyMkFjN3 MC7fqXKIUYCDUYmH98DZzwFCrIllxZW5hxglOZiURHlZGf4GCPEl5adUZiQWZ8QXleakFh9i lOBgVhLh/TnjT4AQb0piZVVqUT5MSoaDQ0mCdxkTUJtgUWp6akVaZg4w4cCkmTg4Qdp5gNqv MQLV8BYXJOYWZ6ZD5E8xqnK0HOh+zijEkpeflyolzjsdpEgApCijNA9uzitGcaCDhXlPg6zh AaZMuAmvgIYzAQ3nXfwbZHhJIkJKqoGxxZrJfPPNBUuM7kQsucSRN+/45PMZz1NmfPh96dkU 2yWMJguudYlp78nyuBB8X1TtbUVJH2dI0LVg5ULtvS4qnk381aG70qe+jPuvYt3wW2vu9Zbw 9w3unD0cFvdkxEVKrzV5O6u6TRA6XJpcUiLkdDdRI1MnI3grN8Ny7xeLCk9Mvl3AfU2JpTgj 0VCLuag4EQDpobtYVgMAAA==
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a de-muxer
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, 21 Jan 2013 09:01:42 -0000

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

Hi Muthu,

I agree that a tunnel is not always needed. But when you say signaling doc,=
 are you referring finally to the draft A? We agreed on addressing capabili=
ties negotiation on that draft.

Nevertheless, I think we should clarify two thinks:

  1.  The way a mux is instructed with the IP address (for example) of a de=
mux. That procedure could be:
     *   Static (i.e. Configuration within the mux)
     *   Dynamic (i.e. Instructed from a higher entity like a policy manage=
r) and could be (or not) described in draft C
  2.  The capabilities negotiation: once a mux knows the IP address of a de=
mux can negotiate the capabilities of the different layers (tunnel, multipl=
ex and compression). This is also described at the draft A.

Regards,

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

From: "'Muthu Arul Mozhi Perumal (mperumal) '" <mperumal@cisco.com<mailto:m=
perumal@cisco.com>>
Date: lunes, 21 de enero de 2013 06:40
To: Fernando Pascual Blanco <fpb@tid.es<mailto:fpb@tid.es>>, "jsaldana@uniz=
ar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.es<mailto:jsaldana@uniza=
r.es>>
Cc: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Subject: RE: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discov=
er a de-muxer

Hi Fernando,

|I=B4m sure we will find a consensus about that :).

Sure..

|What Muthu proposes sounds interesting to me but, to be honest, I think TC=
MTF
|establishing should be quite similar to the establishing procedures of tun=
nels
|defined in draft A (L2TP, GRE=85),

I agree the procedures for establishing the association b/w the muxer and t=
he de-muxer could be similar to those of establishing a tunnel. However, I =
would like us to avoid two assumptions:
1. The other end of a tunnel is always TCMTF capable. I think this is more =
important when you already have a tunnel (say, IPSec tunnel) and would like=
 to perform TCMTF on the fly.
2. A tunnel is always needed for performing TCMTF. If we aren't doing any c=
ompression, but only multiplexing, the outermost IP header would be intact =
and should suffice for routing the packets. There are satellite networks wh=
ere reducing the packets per second (pps) for VoIP calls is more important =
-- they don't do any compression, but only multiplexing, and don't setup a =
tunnel as well. For e.g:
http://www.cisco.com/web/strategy/docs/gov/aag_c45-697642_v2.pdf
http://www.cisco.com/web/strategy/docs/gov/ip_multiplexing_agensler.pptx

Nevertheless, I think all this go into the signaling doc. If we require cap=
ability negotiation, I think we can combine it with the procedure for estab=
lishing the association b/w the muxer and the de-muxer. If we make capabili=
ty negotiation as optional, we might want to keep those as separate procedu=
res.

Muthu

From: tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-b=
ounces@ietf.org] On Behalf Of FERNANDO PASCUAL BLANCO
Sent: Wednesday, January 16, 2013 5:04 PM
To: jsaldana@unizar.es<mailto:jsaldana@unizar.es>; Muthu Arul Mozhi Perumal=
 (mperumal)
Cc: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discov=
er a de-muxer

Hi Jose, Muthu,

I=B4m sure we will find a consensus about that :). What Muthu proposes soun=
ds interesting to me but, to be honest, I think TCMTF establishing should b=
e quite similar to the establishing procedures of tunnels defined in draft =
A (L2TP, GRE=85), actually at network level TCMTF is a tunnel. Once establi=
shed signaling will negotiate upper levels (multiplexing and HC) to perform=
 TCMTF (draft A).

What do you think?

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: mi=E9rcoles, 16 de enero de 2013 11:18
To: "'Muthu Arul Mozhi Perumal (mperumal) '" <mperumal@cisco.com<mailto:mpe=
rumal@cisco.com>>, 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: RV: [tcmtf] TCMTF: Document A: mechanism for a muxer to discover a=
 de-muxer


Fernando, Muthu, everyone,



Since there is no consensus about this, I think we should carry on with the=
 debate. Do you think the mechanism would be very complicated? Any new idea=
s?:



- *dynamically establishing, modifying and releasing tunnels*



#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.



There is still no consensus here:



Fernando: =93Regarding #1, to be honest, I am not completely sure of the ne=
ed to specify a mechanism to discover muxes and demuxes between them. I thi=
nk those kind of mechanisms have more sense in local environments but I=B4m=
 not sure if it applies here. At least at the beginning this associations c=
an be done manually.=94



Muthu: =93I think it is the opposite -- in local environments you can provi=
sion/associate them manually. However, in a multi-vendor environment over t=
he Internet this should happen automatically.=94

=93#1 needs to be specified.=94


Best regards,

Jose

De:tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-boun=
ces@ietf.org] En nombre de Jose Saldana
Enviado el: martes, 15 de enero de 2013 11:56
Para: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: [tcmtf] TCMTF: Document A discussion: content and charter

Document (A) refers to the main TCMTF draft, currently in http://datatracke=
r.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

1.- Content of the Document

Currently it contains the description of the question and the protocols whi=
ch could be used on each layer (tunneling, compressing, multiplexing). It s=
ays that the signaling issues would be that of each protocol.

There is consensus (I think) about this: we should include some signaling i=
ssues. The question is: What should we include in Draft A and what in Draft=
 C?

- *Auto-negotiation* Negotiation mechanisms to decide the options at each l=
ayer (compression, multiplexing and tunneling) between mux and demux. Perha=
ps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP and IPHC,=
 so the two machines will have to negotiate in order to decide which compre=
ssion protocol use.

This should be included in (A). I think there is consensus about this:
Juan Antonio: =93The first kind of signaling ("auto-negotiation") is needed=
 from the beginning if we don't want an extremely static protocol and there=
fore possibly difficult to get it working, especially when in most of cases=
 the peers belong to different entities/companies.=94



Dan: =93We need that -- it is capabilities negotiation.  It is needed becau=
se the protocol will fail if one side mistakenly thinks the other side has =
certain functionality, and because we will want to add some fancy new compr=
ession in the year 2020 and will need to negotiate it.=94



Fernando: =93I also agree with the idea of including the mux-demux signalin=
g within the draft A (as Dan said, they are capabilities negotiation). This=
 draft should be able to get two boxes with TCMTF fully working between the=
m. Under my point of view this includes the definition of the capabilities =
in each node and the negotiation of that capabilities.=94



Does this mean that Document (A) will no longer be a Best Current Practice?=
 I think so.





- *dynamically establishing, modifying and releasing tunnels*



#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.



There is still no consensus here:



Fernando: =93Regarding #1, to be honest, I am not completely sure of the ne=
ed to specify a mechanism to discover muxes and demuxes between them. I thi=
nk those kind of mechanisms have more sense in local environments but I=B4m=
 not sure if it applies here. At least at the beginning this associations c=
an be done manually.=94



Muthu: =93I think it is the opposite -- in local environments you can provi=
sion/associate them manually. However, in a multi-vendor environment over t=
he Internet this should happen automatically.=94

=93#1 needs to be specified.=94







#2. A mechanism to *elect an optimal muxer and a de-muxer when there are mo=
re than one muxer/de-muxer for a flow*.



We agree: This can wait for Document (C).



                Fernando: =93#2 is more related to the higher entity that h=
as to decide whether a flow should be TCMTFed or not, and under my point of=
 view it can be addressed in a different draft.=94

                Muthu: =93#2 can be added later.=94





3. A mechanism to *setup/release a tunnel b/w a muxer and a de-muxer*.



We agree: This has to be included in (A).



                Fernando =93#3 I think should be included in the draft A, s=
ince it is a mechanism within the TFMTF protocol itself.=94

                Muthu: =93#3 many not require much specification.=94





2.- Should we include it in the Charter now?

Of course, Document (A) should be in the charter.


Best regards,

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font=
-family:Calibri,sans-serif">
<div>
<div>
<div>Hi Muthu,</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>I agre=
e that a tunnel is not always needed. But when you say signaling doc, are y=
ou referring finally to the draft A? We agreed on addressing capabilities n=
egotiation on that draft.&nbsp;</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Nevert=
heless, I think we should clarify two thinks:</div>
<ol>
<li>The way a mux is instructed with the IP address (for example) of a demu=
x. That procedure could be:
<ol>
<li>Static (i.e. Configuration within the mux)</li><li>Dynamic (i.e. Instru=
cted from a higher entity like a policy manager) and could be (or not) desc=
ribed in draft C</li></ol>
</li><li>The capabilities negotiation: once a mux knows the IP address of a=
 demux can negotiate the capabilities of the different layers (tunnel, mult=
iplex and compression). This is also described at the draft A.</li></ol>
<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;'Muthu Arul Mozhi Perum=
al (mperumal) '&quot; &lt;<a href=3D"mailto:mperumal@cisco.com">mperumal@ci=
sco.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>lunes, 21 de enero de 2013 06=
:40<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;, &quot;<a href=3D"mailto:jsal=
dana@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">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] RV: TCMTF: Doc=
ument A: mechanism for a muxer to discover a de-muxer<br>
</div>
<div><br>
</div>
<div><style>
<!--
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Tahoma}
@font-face
	{font-family:Consolas}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif"}
span.apple-tab-span
	{}
span.PlainTextChar
	{font-family:Consolas}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{margin-right:0in;
	margin-left:0in;
	font-size:10.0pt;
	font-family:"Times New Roman","serif"}
span.textosinformatocar
	{font-family:"Calibri","sans-serif"}
span.estilocorreo19
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.estilocorreo20
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
span.BalloonTextChar
	{font-family:"Tahoma","sans-serif"}
span.EmailStyle26
	{font-family:"Courier New";
	color:windowtext}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
	{}
-->
</style>
<div lang=3D"EN-US">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">Hi Fernando,</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">|</span><span style=3D"font-size:10pt; font-family:'Courier New'">I=
=B4m sure we will find a consensus about that :).</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">Sure..</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">|What Muthu proposes sounds interesting to me but, to be honest, I th=
ink TCMTF
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">|establishing should be quite similar to the establishing procedures =
of tunnels
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">|defined in draft A (L2TP, GRE=85),</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">I agree the procedures for establishing the association b/w the muxer=
 and the de-muxer could be similar to those of establishing a tunnel. Howev=
er, I would like us to avoid two assumptions:</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">1. The other end of a tunnel is always TCMTF capable. I think this is=
 more important when you already have a tunnel (say, IPSec tunnel) and woul=
d like to perform TCMTF on the fly.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">2. A tunnel is always needed for performing TCMTF. If we aren't doing=
 any compression, but only multiplexing, the outermost IP header would be i=
ntact and should suffice for routing
 the packets. There are satellite networks where reducing the packets per s=
econd (pps) for VoIP calls is more important -- they don't do any compressi=
on, but only multiplexing, and don't setup a tunnel as well. For e.g:</span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'"><a href=3D"http://www.cisco.com/web/strategy/docs/gov/aag_c45-697642_=
v2.pdf">http://www.cisco.com/web/strategy/docs/gov/aag_c45-697642_v2.pdf</a=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'"><a href=3D"http://www.cisco.com/web/strategy/docs/gov/ip_multiplexing=
_agensler.pptx">http://www.cisco.com/web/strategy/docs/gov/ip_multiplexing_=
agensler.pptx</a></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">Nevertheless, I think all this go into the signaling doc. If we requi=
re capability negotiation, I think we can combine it with the procedure for=
 establishing the association b/w the
 muxer and the de-muxer. If we make capability negotiation as optional, we =
might want to keep those as separate procedures.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">Muthu</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt; font-family:'Courier =
New'">&nbsp;</span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0in 0in 0i=
n 4.0pt">
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10pt; font-family:Tahoma=
,sans-serif">From:</span></b><span style=3D"font-size:10pt; font-family:Tah=
oma,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>On Behalf Of </b>FERNANDO PASCUAL BLANCO<br>
<b>Sent:</b> Wednesday, January 16, 2013 5:04 PM<br>
<b>To:</b> <a href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>; Mu=
thu Arul Mozhi Perumal (mperumal)<br>
<b>Cc:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Subject:</b> Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to=
 discover a de-muxer</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, Muthu,</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">I=B4m =
sure we will find a consensus about that :). What Muthu proposes sounds int=
eresting to me but, to be honest, I think TCMTF establishing should be quit=
e similar to the establishing procedures
 of tunnels defined in draft A (L2TP, GRE=85), actually at network level TC=
MTF is a tunnel. Once established signaling will negotiate upper levels (mu=
ltiplexing and HC) to perform TCMTF (draft A).</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">What d=
o you think?</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 0i=
n 0in 0in">
<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>mi=E9rcoles, 16 de enero de 2013 11:18<br>
<b>To: </b>&quot;'Muthu Arul Mozhi Perumal (mperumal) '&quot; &lt;<a href=
=3D"mailto:mperumal@cisco.com">mperumal@cisco.com</a>&gt;, Fernando Pascual=
 Blanco &lt;<a href=3D"mailto:fpb@tid.es">fpb@tid.es</a>&gt;<br>
<b>Cc: </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>RV: [tcmtf] TCMTF: Document A: mechanism for a muxer to dis=
cover a de-muxer</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 style=3D"color:black">Fernando, Muthu, ever=
yone,</span><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Since there is no con=
sensus about this, I think we should carry on with the debate. Do you think=
 the mechanism would be very complicated? Any new ideas?:</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">- *<b>dynamically est=
ablishing, modifying and releasing tunnels</b>*</span><span lang=3D"ES" sty=
le=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">#1. A *<b>mechanism f=
or a muxer to discover a de-muxer (and vice versa)</b>*.</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">There is still no con=
sensus here:</span><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Fernando: =93Regarding #1, to be honest, I am not completely sure o=
f the need to specify a mechanism to discover muxes and demuxes between the=
m. I think those kind of mechanisms have
 more sense in local environments but I=B4m not sure if it applies here. At=
 least at the beginning this associations can be done manually.=94</span><s=
pan lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Muthu: =93I think it is the opposite -- in local environments you c=
an provision/associate them manually. However, in a multi-vendor environmen=
t over the Internet this should happen automatically.=94
</span><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt; text-indent:35.4pt">=
<span style=3D"color:black">=93#1 needs to be specified.=94</span><span lan=
g=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">&nbsp;</sp=
an><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">&nbsp;</sp=
an><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">Best regar=
ds,</span><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D"><br>
Jose</span><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">&nbsp;</sp=
an><span lang=3D"ES" style=3D"color:black"></span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0in 0in 0i=
n 4.0pt">
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"ES" style=3D"font-size:10pt; font-f=
amily:Tahoma,sans-serif; color:black">De:</span></b><span lang=3D"ES" style=
=3D"font-size:10pt; font-family:Tahoma,sans-serif; color:black"><a href=3D"=
mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a>
 [<a href=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</=
a>] <b>En nombre de
</b>Jose Saldana<br>
<b>Enviado el:</b> martes, 15 de enero de 2013 11:56<br>
<b>Para:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tcmtf] TCMTF: Document A discussion: content and charter</s=
pan><span lang=3D"ES" style=3D"color:black"></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:black">&nbsp;</span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Document (A) refers to t=
he main TCMTF draft, currently in
<a href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http=
://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a></span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">1.- Content of the Docum=
ent</span><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Currently it contains th=
e description of the question and the protocols which could be used on each=
 layer (tunneling, compressing, multiplexing). It says that the signaling i=
ssues would be that of each protocol.</span><span lang=3D"ES" style=3D"colo=
r:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">There is consensus (I th=
ink) about this: we should include some signaling issues. The question is: =
What should we include in Draft A and what in Draft C?</span><span lang=3D"=
ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">- *<b>Auto-negotiation</=
b>* Negotiation mechanisms to decide the options at each layer (compression=
, multiplexing and tunneling) between mux and demux. Perhaps the mux has RO=
HC, ECRTP and IPHC, and the demux only
 has ECRTP and IPHC, so the two machines will have to negotiate in order to=
 decide which compression protocol use.</span><span lang=3D"ES" style=3D"co=
lor:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">This should be included =
in (A). I think there is consensus about this:</span><span lang=3D"ES" styl=
e=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span style=3D"color:bl=
ack">Juan Antonio: =93The first kind of signaling (&quot;auto-negotiation&q=
uot;) is needed from the beginning if we don't want an extremely static pro=
tocol and therefore possibly difficult to get it working,
 especially when in most of cases the peers belong to different entities/co=
mpanies.=94</span><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">Dan: =93We need that -- it is capabilities negotiation.&nbsp; It i=
s needed because the protocol will fail if one side mistakenly thinks the o=
ther side has certain functionality, and because
 we will want to add some fancy new compression in the year 2020 and will n=
eed to negotiate it.=94</span><span lang=3D"ES" style=3D"color:black"></spa=
n></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">&nbsp;</span><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">Fernando: =93I also agree with the idea of including the mux-demux=
 signaling within the draft A (as Dan said, they are capabilities negotiati=
on). This draft should be able to get two
 boxes with TCMTF fully working between them. Under my point of view this i=
ncludes the definition of the capabilities in each node and the negotiation=
 of that capabilities.=94</span><span lang=3D"ES" style=3D"color:black"></s=
pan></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Does this mean that D=
ocument (A) will no longer be a Best Current Practice? I think so.</span><s=
pan lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">- *<b>dynamically est=
ablishing, modifying and releasing tunnels</b>*</span><span lang=3D"ES" sty=
le=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">#1. A *<b>mechanism f=
or a muxer to discover a de-muxer (and vice versa)</b>*.</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">There is still no con=
sensus here:</span><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Fernando: =93Regarding #1, to be honest, I am not completely sure o=
f the need to specify a mechanism to discover muxes and demuxes between the=
m. I think those kind of mechanisms have
 more sense in local environments but I=B4m not sure if it applies here. At=
 least at the beginning this associations can be done manually.=94</span><s=
pan lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Muthu: =93I think it is the opposite -- in local environments you c=
an provision/associate them manually. However, in a multi-vendor environmen=
t over the Internet this should happen automatically.=94
</span><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt; text-indent:35.4pt">=
<span style=3D"color:black">=93#1 needs to be specified.=94</span><span lan=
g=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">&nbsp;</span><span lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">#2. A mechanism to *<=
b>elect an optimal muxer and a de-muxer when there are more than one muxer/=
de-muxer for a flow</b>*.</span><span lang=3D"ES" style=3D"color:black"></s=
pan></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">We agree: This can wa=
it for Document (C).</span><span lang=3D"ES" style=3D"color:black"></span><=
/p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ferna=
ndo: =93#2 is more related to the higher entity that has to decide whether =
a flow should be TCMTFed or not, and under my point of view it can be addre=
ssed in a different draft.=94</span><span lang=3D"ES" style=3D"color:black"=
></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu=
: =93#2 can be added later.=94</span><span lang=3D"ES" style=3D"color:black=
"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">3. A mechanism to *<b=
>setup/release a tunnel b/w a muxer and a de-muxer</b>*.</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">We agree: This has to=
 be included in (A).</span><span lang=3D"ES" style=3D"color:black"></span><=
/p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ferna=
ndo =93#3 I think should be included in the draft A, since it is a mechanis=
m within the TFMTF protocol itself.=94</span><span lang=3D"ES" style=3D"col=
or:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu=
: =93#3 many not require much specification.=94</span><span lang=3D"ES" sty=
le=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;</span><span la=
ng=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">2.- Should we include=
 it in the Charter now?</span><span lang=3D"ES" style=3D"color:black"></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Of course, Document (A) =
should be in the charter.</span><span lang=3D"ES" style=3D"color:black"></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Best regards,</span><spa=
n lang=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;</span><span lang=
=3D"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Jose</span><span lang=3D=
"ES" style=3D"color:black"></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:black">&nbsp;</span=
></p>
</div>
</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; font-family:Arial,sa=
ns-serif; color:gray"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span style=3D"font-size:10.5pt; color=
:black"></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_iGJq5BfCq3ibA4gwxbO3fA)--

From jsaldana@unizar.es  Mon Jan 21 05:33:02 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A253B21F85B8 for <tcmtf@ietfa.amsl.com>; Mon, 21 Jan 2013 05:33:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8dXcMz+IPDEx for <tcmtf@ietfa.amsl.com>; Mon, 21 Jan 2013 05:33:00 -0800 (PST)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3A97D21F85B6 for <tcmtf@ietf.org>; Mon, 21 Jan 2013 05:32:59 -0800 (PST)
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 r0LDWsQj022953; Mon, 21 Jan 2013 14:32:54 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <gorry@erg.abdn.ac.uk>
References: <009701cdf4ac$8af49750$a0ddc5f0$@unizar.es>	<F5EDC35DF914C1428C28E149F10463A2689D3F12@EX10-MB2-MAD.hi.inet>	<009f01cdf4b9$aca39060$05eab120$@unizar.es> <50F92318.30809@erg.abdn.ac.uk>
In-Reply-To: <50F92318.30809@erg.abdn.ac.uk>
Date: Mon, 21 Jan 2013 14:33:02 +0100
Organization: Universidad de Zaragoza
Message-ID: <003601cdf7db$d652edf0$82f8c9d0$@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: AQE0iUS1pqKAqIDkIMIlcU9RBNLUGwJ038JPAikfrYcCMSrOUJlQJs3A
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
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, 21 Jan 2013 13:33:02 -0000

Gorry,

Regarding your question:
> RTT and/or control feedback would be really helpful in establishing a
> congestion control or circuit-breaker function to ensure the traffic =
does not
> cause congestion collapse. Have you thought about this?

If I understand well, you are talking about using RTT or feedback not =
only for selecting an adequate multiplexing period, but also for =
congestion control. Is this true?

The question is that TCMTF is designed for traffic saving, so I think =
the cause of the congestion would not be TCMTF itself, but a high amount =
of flows, or a high bandwidth to aggregate. So perhaps in that case the =
flows which are being multiplexed will have their own end-to-end =
congestion control mechanisms.

An example: you are grouping a lot of TCP flows of an MMORPG game. If a =
bottleneck appears and delays rise, TCP mechanisms will act and reduce =
the rate.

Can we find an example in which interrupting the use of TCMTF and =
sending native packets instead will be necessary? Perhaps this one: if =
you are using TCMTF for reducing pps and not bandwidth. This can happen =
with VoIP in a satellite network: you group packets without header =
compression. You reduce pps and you increase bandwidth. However, I think =
bandwidth increase is really small: 25 bytes for the tunnel header and =
two more bytes for separating each multiplexed packet. If you are =
grouping 10 VoIP packets (20 IP/8 UDP/12 RTP/20 payload), the tunnel =
needs 25 + 10x(2+60)=3D645bytes. Native traffic would need 10x60=3D600 =
bytes. So bandwidth increase is 7.5%. If you group 20 packets, bandwidth =
increase is 1265/1200=3D 5%

Gorry, was this your idea? Are you thinking about other scenarios in =
which interrupting TCMTF can be interesting?

Thanks a lot,

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Gorry Fairhurst
> Enviado el: viernes, 18 de enero de 2013 11:25
> Para: tcmtf@ietf.org
> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using =
Tunneling
> Compressed Multiplexed Traffic Flows
>=20
> If this is going to be used in the general Internet, then we need to =
decide
> whether there is one-way or two-way control connectivity. This will
> determine the constraints from a congestion control perspective.
> RTT and/or control feedback would be really helpful in establishing a
> congestion control or circuit-breaker function to ensure the traffic =
does not
> cause congestion collapse. Have you thought about this?
>=20
> Gorry
>=20
>=20
>=20
> On 17/01/2013 13:50, Jose Saldana wrote:
> > In addition, perhaps we are too focused on online games and VoIP
> services. There are other services which are one-way: perhaps M2M
> communications do not require a two way communication. We can think
> about a number of sensors sending their measurements to a central =
server.
> So perhaps RTT will not even exist in this case.
> >
> > Jose
> >
> >> -----Mensaje original-----
> >> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es] Enviado el: jueves,
> >> 17 de enero de 2013 14:39
> >> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko Su=C5=BEnjevi=C4=87'; =
'Juli=C3=A1n
> >> Fern=C3=A1ndez Navajas'
> >> CC: tcmtf@ietf.org
> >> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
> >> Tunneling Compressed Multiplexed Traffic Flows
> >>
> >> Jose,
> >>
> >>          Let=C2=B4s say that playing with the OWD you have more
> >> granularity in order to know in which direction you need to reduce
> >> the delay by reducing the multiplexing delay. But people with more
> >> knowledge about online games will provide us more information for =
sure.
> >>
> >> Regards,
> >>
> >> Fernando Pascual Blanco
> >> Telef=C3=B3nica Global Resources
> >> Network Automation and Dynamization
> >> TECHNOLOGY PEOPLE GROUP
> >> F +34913128779
> >> M +34682005168
> >> fpb@tid.es
> >>
> >>
> >>
> >>
> >> On 17/01/13 13:16, "Jose Saldana" <jsaldana@unizar.es> wrote:
> >>
> >>> Fernando,
> >>>
> >>> So you may have this case:
> >>> - your multiplexing delay limit is 50 ms
> >>> - you have a lot of flows to multiplex, so perhaps the time =
between
> >>> multiplexed packets will be 5 ms
> >>> - you detect an increase in RTT
> >>> - the system reacts and reduces multiplexing period
> >>> - in fact, the reduction doesn't matter until the period is =
reduced
> >>> to less than 5 ms
> >>>
> >>> So you only have to make this decision: using tcmtf with 5 ms =
period
> >>> or not. If RTT is critical you may not be interested on saving
> >>> bandwidth, but on reducing a bit the RTT.
> >>>
> >>> So I think your question is: what happens if the RTT is very big
> >>> (out of
> >>> limits) and you can save bandwidth using a 5ms multiplexing =
period?
> >>>
> >>> For example, the maximum RTT for a good quality is 80 ms and your
> >>> network has 120 just now. In this case, perhaps having 125 doesn't
> >>> matter, if you can save bandwidth.
> >>>
> >>> This makes sense, but it is a "extreme" case. However, would it be
> >>> any advantage if OWD is used instead of RTT?
> >>>
> >>> Best regards,
> >>>
> >>> Jose
> >>>
> >>>> -----Mensaje original-----
> >>>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]  Enviado el:
> >>>> mi=C3=A9rcoles, 16 de enero de 2013 12:52
> >>>> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko =
Su=C5=BEnjevi=C4=87'; 'Juli=C3=A1n
> >>>> Fern=C3=A1ndez  Navajas'
> >>>> CC: tcmtf@ietf.org
> >>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
> >>>> Tunneling  Compressed Multiplexed Traffic Flows
> >>>>
> >>>> Hi Jose,
> >>>>
> >>>>          You are right, but my point here is:
> >>>>
> >>>>                  Client - Mux - Demux - Server
> >>>>
> >>>>          Imagine that there is enough packets between mux and =
demux
> >>>> to make  the added delay very small (TCMTF is working very well =
and
> >>>> the mux has not  to wait the multiplexing period to fulfill a big
> >>>> packet and send it, so imagine a  multiplexing period of 50 ms =
and
> >>>> a big packet is fulfilled in 5 ms). If the RTT  get increased
> >>>> because a congestion in the way back to the client (there is no
> >>>> TCMTF
> >>>> optimization) and we decrease the multiplexing period (even in =
the
> >>>> extreme we can disable the TCMTF optimization) the high RTT will
> remain.
> >>>> Even if the TCMTF optimization was helping in the client to =
server
> >>>> path,  disabling it may harm. Do you think that scenario would be
> possible?
> >>>>
> >>>>          So I=C2=B4m not sure about that, I think we need more =
opinions here.
> >>>>
> >>>> Regards,
> >>>>
> >>>> Fernando Pascual Blanco
> >>>> Telef=C3=B3nica Global Resources
> >>>> Network Automation and Dynamization TECHNOLOGY PEOPLE GROUP
> F
> >>>> +34913128779 M +34682005168 fpb@tid.es
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On 16/01/13 11:57, "Jose Saldana" <jsaldana@unizar.es> wrote:
> >>>>
> >>>>> My two cents:
> >>>>>
> >>>>> In games and in VoIP the really important thing is RTT:
> >>>>>
> >>>>> - Games always measure the RTT (gamers talk about the "ping"): =
the
> >>>>> important thing is the delay from a player action to the server
> >>>>> reaction arriving to the player's machine.
> >>>>> - In VoIP I think it is the same: what matters is the RTT, in
> >>>>> order to grant interactivity and avoiding cross-talk.
> >>>>>
> >>>>> In addition, RTT is easier to measure than OWD, since you don't
> >>>>> need synchronization.
> >>>>>
> >>>>> And regarding Two-way TCMTF, I think we have to think about =
TCMTF
> >>>>> as one-way. Otherwise, things would become very complicated.
> Some
> >>>> services
> >>>>> have very different client-server and server-client traffic
> >>>>> patterns (e.g. games). In addition, sometimes the two flows can
> >>>>> follow different network paths. I think once we talked about a
> >>>>> network provider using a number of ISPs.
> >>>>>
> >>>>> However, using RTT for tuning a one-way TCMTF may not be bad... =
or
> >>>>> is it bad? Any other thoughts?
> >>>>>
> >>>>> BR,
> >>>>>
> >>>>> Jose
> >>>>>
> >>>>>> -----Mensaje original-----
> >>>>>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]  Enviado el:
> >>>> martes,
> >>>>>> 15 de enero de 2013 18:04
> >>>>>> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko =
Su=C5=BEnjevi=C4=87'; Juli=C3=A1n
> >>>>>> Fern=C3=A1ndez  Navajas
> >>>>>> CC: tcmtf@ietf.org
> >>>>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
> >>>>>> Tunneling  Compressed Multiplexed Traffic Flows
> >>>>>>
> >>>>>> Hi all,
> >>>>>>
> >>>>>>          To re-open that issue, I would suggest that given that
> >>>>>> the delay is so  sensitive in real time services, we need to =
find
> >>>>>> a consensus here.
> >>>>>>
> >>>>>>          My opinion is that to apply the first possibility (the
> >>>>>> static multiplexing
> >>>>>> period) we need to suppose that the network conditions are =
really
> >>>>>> bad, to be  protected when the network congestion arises. In =
that
> >>>>>> case, the application  of the TCMTF optimization will not be
> >>>>>> optimal, so that would be the less  preferred option, but =
easier
> >>>>>> to implement and maintain over the time.
> >>>>>>
> >>>>>>          On the other hand, the second possibility would be the
> >>>>>> preferred. It is  easy to know the delay between the mux and =
the
> >>>>>> demux but most of the  times will not be enough unless mux and
> >>>>>> demux were really near from the  client and the server
> >>>>>> respectively. I agree with Jose in the possibility of snoop  =
RTCP
> >>>>>> packets in order to adapt the multiplexing period when
> >>>>>> multiplexing RTP packets (and RTCP is available). Talking about
> >>>>>> RTT, I=C2=B4m not sure if RTT  would be useful given that the
> >>>>>> multiplexing period only affect the one way  delay (OWD). =
Imagine
> the following scenario:
> >>>>>>          - Client - Mux/Demux - Demux/Mux - Server (two ways
> >>>>>> TCMTF, TWTCMTF :P)
> >>>>>>          - The OWD from server to client get increased
> >>>>>>          - The OWD from client to server remains equal
> >>>>>>          - Should we use a lower multiplexing period in the
> >>>>>> client to server  direction? I don=C2=B4t think so=E2=80=A6 =
because we should
> >>>>>> use a lower multiplexing  period in the other direction.
> >>>>>>
> >>>>>>          My point is that the multiplexing period should only =
be
> >>>>>> affected by the  OWD and not by the RTT (or it may be =
application
> >>>>>> dependent). How to  calculate the OWD? I=C2=B4ve been reading
> >>>>>> something about OWAMP and it  seems that an specific software =
has
> >>>>>> to be implemented in the client/server  side.
> >>>>>> Can we assume that? Unfortunately I cannot contribute so much
> >> here=E2=80=A6
> >>>>>>          It is possible that for certain services the static =
(and
> >>>>>> worst
> >>>>>> case)
> >>>>>> multiplexing period would be the better solution.
> >>>>>>
> >>>>>>          What do you think?
> >>>>>>
> >>>>>> Regards,
> >>>>>>
> >>>>>> Fernando Pascual Blanco
> >>>>>> Telef=C3=B3nica Global Resources
> >>>>>> Network Automation and Dynamization TECHNOLOGY PEOPLE
> GROUP
> >> F
> >>>>>> +34913128779 M +34682005168 fpb@tid.es
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On 17/12/12 12:25, "Jose Saldana" <jsaldana@unizar.es> wrote:
> >>>>>>
> >>>>>>> Hi all,
> >>>>>>>
> >>>>>>> Julian and I have been discussing about this. Some ideas have
> >>>> arisen.
> >>>>>>> This is the summary.
> >>>>>>>
> >>>>>>> This would be the scheme of the system, including mux and
> demux:
> >>>>>>>
> >>>>>>> Real-time application ------- mux -------- internet ---------
> >>>>>>> demux
> >>>>>>> -------
> >>>>>>> server
> >>>>>>>
> >>>>>>>
> >>>>>>> I think perhaps the draft could say something like:
> >>>>>>>
> >>>>>>> When setting the multiplexing period, there are two =
possibilities:
> >>>>>>>
> >>>>>>> 1.- Static / permanent: At system setup time, network delays =
are
> >>>>>>> measured, and a multiplexing period is selected and set in the
> >>>>>> multiplexer.
> >>>>>>>
> >>>>>>> 2.- Dynamic: A mechanism is used so as to adapt to the =
evolution
> >>>>>>> of network delays. In this case, different mechanisms can be
> >>>>>>> used in order to obtain periodical end-to-end network delay
> >>>>>>> estimations, which would be useful in order to set the
> >>>>>>> multiplexing
> >> period:
> >>>>>>>
> >>>>>>> - If the traffic is RTP, then RTCP packets containing the
> >>>>>>> estimation could be analyzed in order to extract these values,
> >>>>>>> as Dan
> >> suggests.
> >>>>>>> The question
> >>>>>>> is: would that packets travel through the multiplexer?
> >>>>>>> - If the traffic is TCP, perhaps something similar to the RTT
> >>>>>>> estimation of TCP could be useful.
> >>>>>>> - If the traffic is UDP, should the mux use something like =
OWAMP
> >>>>>>> (http://tools.ietf.org/html/rfc4656) in order to calculate two
> >>>>>>> delays (application to mux, and mux to server) and calculate =
the
> >>>> sum?
> >>>>>>>
> >>>>>>>
> >>>>>>> I think the draft is only supposed to report the maximum =
delays
> >>>>>>> normally considered acceptable. Perhaps the additional
> >>>>>>> mechanisms for calculating the RTT could just be suggested.
> >>>>>>>
> >>>>>>> What do you think?
> >>>>>>>
> >>>>>>> Jose
> >>>>>>>
> >>>>>>>> -----Mensaje original-----
> >>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >>>>>>>> nombre de Dan Wing Enviado el: viernes, 14 de diciembre de =
2012
> >>>>>>>> 18:33
> >>>>>>>> Para: jsaldana@unizar.es; 'Mirko Su=C5=BEnjevi=C4=87'
> >>>>>>>> CC: tcmtf@ietf.org
> >>>>>>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when =
using
> >>>>>>>> Tunneling Compressed Multiplexed Traffic Flows
> >>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: Jose Saldana [mailto:jsaldana@unizar.es]
> >>>>>>>>> Sent: Friday, December 14, 2012 2:58 AM
> >>>>>>>>> To: 'Dan Wing'; 'Mirko Su=C5=BEnjevi=C4=87'
> >>>>>>>>> Cc: tcmtf@ietf.org
> >>>>>>>>> Subject: RE: [tcmtf] Draft: Maximum Tolerable Delays when
> >>>>>>>>> using Tunneling Compressed Multiplexed Traffic Flows
> >>>>>>>>>
> >>>>>>>>> Dan,
> >>>>>>>>>
> >>>>>>>>> Regarding the use of the maximum delay, some days ago we
> >>>>>>>>> discussed about
> >>>>>>>>> it:
> >>>>>>>>> the actual OWD of the network should be measured (or
> >>>>>>>>> estimated) in order to know the maximum multiplexing period
> we
> >> can set.
> >>>>>>>>>
> >>>>>>>>> We may have this formula, if thinking one-way:
> >>>>>>>>>
> >>>>>>>>> OWD  + Mux period/2  < tolerable_OWD
> >>>>>>>>>
> >>>>>>>>> If we think RTT:
> >>>>>>>>>
> >>>>>>>>> OWD + Mux period/2 + OWD back < 2*tolerable_OWD
> >>>>>>>>>
> >>>>>>>>> I don't know if we should include a mechanism for estimating
> >>>>>>>>> OWD in tcmtf. I think this is more an implementation =
problem,
> >>>>>>>>> which may be already solved.
> >>>>>>>>
> >>>>>>>> Yes, it's already solved end-to-end:  RTP with RTCP feedback
> >>>>>>>> allows determining one way delay.
> >>>>>>>>
> >>>>>>>> But if something in the middle is multiplexing several =
packets
> >>>>>>>> together,
> >>>>>>> we
> >>>>>>>> don't want it to add too much delay.  That thing in the =
middle
> >>>>>>>> won't necessarily know the one way delay seen by the =
endpoints,
> >>>>>>>> unless it analyzes the RTP and RTCP.  There are devices that =
do
> >>>>>>>> that on the market,  mostly to diagnose where networks are
> >>>>>>>> causing loss/delay with RTP flows.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> Another option is using some typical values, e.g. from
> >>>>>>>>>
> >> http://ipnetwork.bgtmo.ip.att.net/pws/global_network_avgs.htm
> >>>>>>>>> l
> >>>>>>>>>
> >>>>>>>>> The draft includes some preliminary/recommended values for
> the
> >>>>>>>>> Multiplexing Period. Is this interesting? Should we put the
> >>>>>>>>> formula instead?
> >>>>>>>>
> >>>>>>>> It's probably sufficient as-is.
> >>>>>>>>
> >>>>>>>> -d
> >>>>>>>>
> >>>>>>>>> Mirko, another question: in online games, players usually =
talk
> >>>>>>>>> about the "ping", and I think it means RTT. Don't you think =
it
> >>>>>>>>> would be better to define a RTT limit instead of a OWD one =
in
> >>>>>>>>> that
> >>>>>> case?
> >>>>>>>>>
> >>>>>>>>> What do you think?
> >>>>>>>>>
> >>>>>>>>> Jose
> >>>>>>>>>
> >>>>>>>>>> -----Mensaje original-----
> >>>>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org]
> En
> >>>>>>>>>> nombre de Dan Wing Enviado el: jueves, 13 de diciembre de
> >>>>>>>>>> 2012
> >>>>>>>>>> 17:07
> >>>>>>>>>> Para: 'Mirko Su=C5=BEnjevi=C4=87'; tcmtf@ietf.org
> >>>>>>>>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when
> >>>>>>>>>> using Tunneling Compressed Multiplexed Traffic Flows
> >>>>>>>>>>
> >>>>>>>>>>> -----Original Message-----
> >>>>>>>>>>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-
> bounces@ietf.org]
> >>>>>>>>>>> On Behalf Of Mirko Su=C5=BEnjevic
> >>>>>>>>>>> Sent: Thursday, December 13, 2012 1:07 AM
> >>>>>>>>>>> To: tcmtf@ietf.org; tsvwg@ietf.org
> >>>>>>>>>>> Subject: [tcmtf] Draft: Maximum Tolerable Delays when =
using
> >>>>>>>>>>> Tunneling Compressed Multiplexed Traffic Flows
> >>>>>>>>>>>
> >>>>>>>>>>> Hello,
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> We have just submitted the draft named Maximum Tolerable
> >>>>>>>>>>> Delays when using Tunneling Compressed Multiplexed Traffic
> >>>> Flows:
> >>>>>>>>>>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd
> >>>>>>>>>>> -tc
> >>>>>>>>>>> mtf
> >>>>>>>>>>> /
> >>>>>>>>>>
> >>>>>>>>>> The suggested 400ms for interactive voice is at least 2x =
too
> >>>>>> high.
> >>>>>>>>>> I
> >>>>>>>>> expect
> >>>>>>>>>> that number does not include the playout jitter buffer =
(which
> >>>>>>>>>> is variable,
> >>>>>>>>> but
> >>>>>>>>>> usually a few samples, so 40-80ms).  200ms end-to-end is =
the
> >>>>>>>>>> higher end,
> >>>>>>>>> and
> >>>>>>>>>> that includes jitter buffer, codec processing, and so on.
> >>>>>>>>>>
> >>>>>>>>>> But, more importantly:  it seems valuable for endpoints to
> >>>>>>>>>> signal their maximum delay somehow.  Or would the TCMTF
> >>>>>>>>>> function
> >>>>>>>> determine
> >>>>>>>>>> the maximum delay, using some heuristic?
> >>>>>>>>>>
> >>>>>>>>>> How does the TCMTF function determine how much of that
> >>>>>>>>>> 'tolerable latency' budget it can consume?
> >>>>>>>>>>
> >>>>>>>>>> -d
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> It is an extension of tcmtf
> >>>>>>>>>>> http://datatracker.ietf.org/doc/draft-
> >>>>>>>>>>> saldana-tsvwg-tcmtf/. Since a specific list for tcmtf =
exists
> >>>>>>>>>>> (tcmtf@ietf.org), the idea is to discuss it there.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> The draft contains recommendations for TCMTF multiplexing
> >>>>>>>>>>> period for different real-time services. In order to =
prevent
> >>>>>>>>>>> QoE degradation of real-time services using TCMTF, a =
policy
> >>>>>>>>>>> defining a multiplexing period can be employed. Values of
> >>>>>>>>>>> maximum tolerable delays presented in
> >>>>>>>>>> the
> >>>>>>>>>>> draft form the base of such policy.    The recommendations
> >>>> are
> >>>>>>>>> presented
> >>>>>>>>>>> for real-time network services in which TCTMF bandwidth
> >>>>>>>>>>> optimization is applicable (i.e., services  which have low
> >>>>>>>>>>> payload to header size ratio which results in high =
protocol
> >>>>>> overhead).
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Your feedback will be welcome. Thank you.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Sincerely,
> >>>>>>>>>>>
> >>>>>>>>>>> Mirko Suznjevic
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> 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 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
> >>>>
> >>>>
> >>>> ________________________________
> >>>>
> >>>> 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
> > https://www.ietf.org/mailman/listinfo/tcmtf
> >
>=20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From jsaldana@unizar.es  Mon Jan 21 05:55:05 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC8B621F84BA for <tcmtf@ietfa.amsl.com>; Mon, 21 Jan 2013 05:55:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=-0.151, 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 h8ZLfQLJ0glq for <tcmtf@ietfa.amsl.com>; Mon, 21 Jan 2013 05:54:58 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id E137821F8487 for <tcmtf@ietf.org>; Mon, 21 Jan 2013 05:54:46 -0800 (PST)
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 r0LDsY8L004413; Mon, 21 Jan 2013 14:54:35 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Michael Ramalho \(mramalho\)'" <mramalho@cisco.com>, "=?iso-8859-2?Q?'Mirko_Su=BEnjevi=E6'?=" <Mirko.Suznjevic@fer.hr>, "'FERNANDO	PASCUAL BLANCO'" <fpb@tid.es>
Date: Mon, 21 Jan 2013 14:54:46 +0100
Organization: Universidad de Zaragoza
Message-ID: <003801cdf7de$df5c7030$9e155090$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0039_01CDF7E7.41240C80"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac332+OsoQuYsWSSQ62+h3AX7t8/Xg==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] [tsvwg] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
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, 21 Jan 2013 13:55:06 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0039_01CDF7E7.41240C80
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

Michael,

=20

In our research studies, we first thought about VoIP. In that case, if
everyone uses the same codec, you just have to wait in order to get a =
packet
from each flow. (This would not be true if silence suppression is =
applied,
however).

=20

But other services, like games, do not have a fixed cadence. If you look =
at
this paper
(http://diec.unizar.es/~jsaldana/personal/commag_nov_2011_jsaldana.pdf) =
, in
which 8 games were analyzed, you may see that each one has a different
inter-packet time histogram.

=20

We thought about different policies for defining which native packet =
goes in
which multiplexed packet:

=20

- Fixed number of packets: Once you have N packets, you send the =
multiplexed
one

- Size limit: Once you reach a size (next to MTU), you send the =
multiplexed
one

- Period: You send a multiplexed packet every Period

- Timeout: (Very similar to "period") When a packet arrives, if a =
timeout
expires, you include it in the bundle and send it

=20

Logically, "period" should be always combined with "size limit": if you =
have
an MTU packet, waiting more would be stupid. So the traffic class or the
signature analysis can give you the maximum period, but you should also =
use
the "size limit".

=20

The question is that we are grouping a number of flows, which may be =
high.
In that case, the assumption of having a uniform distribution is not far
from reality. However, perhaps we could avoid the sentence "If a policy
defining a multiplexing period is used, then the average latency added =
to
each packet will be half the multiplexing period."

=20

The paragraph can begin with the next one: "A tradeoff appears: the =
longer
the multiplexing period, the higher the number of packets which can be
grouped, thus obtaining better bandwidth savings."=20

=20

What do you think?

=20

Jose

=20

De: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] En nombre de
Michael Ramalho (mramalho)
Enviado el: viernes, 18 de enero de 2013 15:05
Para: Mirko Su=BEnjevi=E6; FERNANDO PASCUAL BLANCO; tcmtf@ietf.org;
tsvwg@ietf.org
Asunto: Re: [tsvwg] [tcmtf] Draft: Maximum Tolerable Delays when using
Tunneling Compressed Multiplexed Traffic Flows

=20

All,

=20

Strictly speaking, the sentence ""If a policy defining a multiplexing =
period
is used, then the average latency added to each packet will be half the
multiplexing period."" makes an explicit assumption that the packet =
arrivals
(for TCMTF packets) are random/uniform (or even that the arrival pdf is =
one
sided, with the most of the pdf area/contribution below the mean delay).

=20

Why even go there?

=20

If someone has such a "policy" . the policy is to define the maximum
worst-case TCMTF (encoding) delay. If the TCMTF encoder has not yet =
built a
"near-MTU" packet and the worst-case delay timer fires . push the packet
out!

=20

The worst-case TCMTF delay we should introduce is determined by the =
packets
we want to multiplex within a TCMTF packet. If we knew their traffic =
class .
we would have an idea of what the worst case should be. If we didn't, =
but
rather made a reasonable assumption (for example, based on signature
analysis), then we push when our idea of what the worst case has been =
met.

=20

Given that the sentence referenced above is not correct (it has an =
implicit
random arrival process assumption) - we need to clarify it if it is =
decided
to keep it.

=20

As Gorry notes in the next email on this thread, some delay-based =
congestion
controls may respond to TCMTF-induced delay as an indication of =
increasing
congestion in their congestion control. Anything we can do to limit the
maximum delay (i.e., have a "nice" TCMTF-induced delay distribution) =
would
be appreciated.

=20

Michael Ramalho

=20

From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf =
Of
Mirko Su=BEnjevic
Sent: Friday, January 18, 2013 5:15 AM
To: FERNANDO PASCUAL BLANCO; tcmtf@ietf.org; tsvwg@ietf.org
Subject: Re: [tsvwg] [tcmtf] Draft: Maximum Tolerable Delays when using
Tunneling Compressed Multiplexed Traffic Flows

=20

Yes I concur, it is a good notice. I am adding your comment to the =
review
list for the next version.


Mirko Suznjevic

=20

From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]=20
Sent: Thursday, January 17, 2013 10:08 AM
To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org; tsvwg@ietf.org
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using =
Tunneling
Compressed Multiplexed Traffic Flows

=20

Hi Mirko,

=20

Thank you for considering that. In addition, one more thing: in section =
4,
the sentence "If a policy defining a multiplexing period is used, then =
the
average latency added to each packet will be half the multiplexing =
period."
only applies when there is not enough packet rate to fulfill a big =
packet by
multiplexing small ones. When  there is a lot of packets to multiplex, =
in
general, multiplexing period will not be reached, so half the =
multiplexing
period will be the maximum/worse average added delay. In general, and =
when
TCMTF is working fine, average added delay will be lower.

So, I would rewrite that phrase as: "If a policy defining a multiplexing
period is used, then the average latency added to each packet will be =
half
the time to fulfill a multiplexed one. In the worse case and if the
multiplexing period is reached, the average latency added to each packet
will be half the multiplexing period".

=20

What do you think?

=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: Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr>
Date: martes, 15 de enero de 2013 16:48
To: Fernando Pascual Blanco <fpb@tid.es>, "tcmtf@ietf.org" =
<tcmtf@ietf.org>,
"tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using =
Tunneling
Compressed Multiplexed Traffic Flows

=20

Hello,

Thanks for all the comments, I will briefly respond to them, and include
your (as well as previous) corrections in a new version of the draft:

*	I do not understand the sentence "Therefore, we neither take into
account services using an approach in which all the calculations are
deployed in the server, which sends a real-time video stream to the =
client."
in section 3.

The meaning of this sentence is that we will not be looking at the cloud
based gaming services such as OnLive or Gaiki as they are focused on
performing all needed calculations of the gamestate on the server, and
sending a very "fat" video stream to the client which only renders the
video. Therefore they are not suitable for tcmtf. I will change that in
order to be more clear.

*	In section 3 (Considered Services), I think it could be also
interesting to consider non-real time services candidates to be TCMTF
optimized. For example services like instant messaging, where the =
bandwidth
saving is the main benefit of the TCMTF optimization, should be somehow
mentioned, establishing a kind of delay upper threshold. Related to =
that, in
section 3, when talking about web browsing, the sentence "there is no =
need
for policy limitations in TCMTF" could be disappointed, because actually
there are limitations (ITU-T_G.1010, 10 seconds for web browsing, as in
section 4.1 10 seconds are considered for streaming audio).

At first when we were discussing we decided that it will be focused on
real-time services, but this can be broadened to others non-real-time. I
think giving such upper limits has a point, although would we even =
employ
tcmtf in cases  in which we will not have enough data to send a packet =
in 5
or more seconds? Is that feasible? Maybe in some sensor networks? Maybe =
I am
just looking it the wrong way, maybe we would have a lot of traffic that
needs to be packed ASAP!

*	In section 4, I would change the sentence "A number of flows are
multiplexed together before being sent through the Internet." for "A =
number
of flows are multiplexed together before being sent through the =
network.",
because the network could not be necessary the Internet, I would also =
adapt
Figure 2.

Ok will be done.

*	Maybe the creation of a section 4.4 talking about non real time
services could be considered including last comments (acceptable with =
the
recommendation appearing in the last sentence of the section 4.3 "It =
should
be noted that multiplexing periods of about 1 second can be considered =
as
enough for non real time services (e.g., web browsing and streaming
audio).")

Ok, seems sound enough. I will write it and see which format looks =
better.

*	Table 1 could be included in a separate section (i.e. Section 4.5)
as a summary

Ok.

=20

Thanks again for the feedback!

Cheers!
Mirko

=20

From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]=20
Sent: Tuesday, January 15, 2013 3:42 PM
To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org; tsvwg@ietf.org
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using =
Tunneling
Compressed Multiplexed Traffic Flows

=20

Hi Mirko,

=20

Some comments to the draft:

*	In the introduction it says "TCTMF", it is "TCMTF".
*	I do not understand the sentence "Therefore, we neither take into
account services using an approach in which all the calculations are
deployed in the server, which sends a real-time video stream to the =
client."
in section 3.
*	In section 3 (Considered Services), I think it could be also
interesting to consider non-real time services candidates to be TCMTF
optimized. For example services like instant messaging, where the =
bandwidth
saving is the main benefit of the TCMTF optimization, should be somehow
mentioned, establishing a kind of delay upper threshold. Related to =
that, in
section 3, when talking about web browsing, the sentence "there is no =
need
for policy limitations in TCMTF" could be disappointed, because actually
there are limitations (ITU-T_G.1010, 10 seconds for web browsing, as in
section 4.1 10 seconds are considered for streaming audio).
*	In section 4, I would change the sentence "A number of flows are
multiplexed together before being sent through the Internet." for "A =
number
of flows are multiplexed together before being sent through the =
network.",
because the network could not be necessary the Internet, I would also =
adapt
Figure 2.
*	Maybe the creation of a section 4.4 talking about non real time
services could be considered including last comments (acceptable with =
the
recommendation appearing in the last sentence of the section 4.3 "It =
should
be noted that multiplexing periods of about 1 second can be considered =
as
enough for non real time services (e.g., web browsing and streaming
audio).")
*	Table 1 could be included in a separate section (i.e. Section 4.5)
as a summary

Hope to help!

=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: Mirko Su=BEnjevi=E6 <Mirko.Suznjevic@fer.hr>
Date: jueves, 13 de diciembre de 2012 10:06
To: "tcmtf@ietf.org" <tcmtf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling
Compressed Multiplexed Traffic Flows

=20

Hello,

=20

We have just submitted the draft named Maximum Tolerable Delays when =
using
Tunneling Compressed Multiplexed Traffic Flows:
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/

=20

It is an extension of tcmtf
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/. Since a =
specific
list for tcmtf exists (tcmtf@ietf.org), the idea is to discuss it there.

=20

The draft contains recommendations for TCMTF multiplexing period for
different real-time services. In order to prevent QoE degradation of
real-time services using TCMTF, a policy defining  a multiplexing period =
can
be employed. Values of maximum tolerable delays presented in the draft =
form
the base of such policy.    The recommendations are presented for =
real-time
network services in which TCTMF bandwidth optimization is applicable =
(i.e.,
services  which have low payload to header size ratio which results in =
high
protocol overhead).

=20

Your feedback will be welcome. Thank you.


Sincerely,

Mirko Suznjevic

=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

=20

  _____ =20


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


------=_NextPart_000_0039_01CDF7E7.41240C80
Content-Type: text/html;
	charset="iso-8859-2"
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-2"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><!--[if !mso]><style>v\:* =
{behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML con formato previo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texto de globo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.TextodegloboCar
	{mso-style-name:"Texto de globo Car";
	mso-style-priority:99;
	mso-style-link:"Texto de globo";
	font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.emailstyle17
	{mso-style-name:emailstyle17;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.emailstyle19
	{mso-style-name:emailstyle19;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.balloontextchar0
	{mso-style-name:balloontextchar;
	font-family:"Tahoma","sans-serif";}
span.EstiloCorreo27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EstiloCorreo28
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EstiloCorreo29
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLconformatoprevioCar
	{mso-style-name:"HTML con formato previo Car";
	mso-style-priority:99;
	mso-style-link:"HTML con formato previo";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:204412190;
	mso-list-template-ids:-1276223818;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:1492870025;
	mso-list-template-ids:-1264823850;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2
	{mso-list-id:1530142094;
	mso-list-template-ids:163602884;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3
	{mso-list-id:1534347909;
	mso-list-template-ids:273075542;}
@list l3:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4
	{mso-list-id:1862544740;
	mso-list-template-ids:361497012;}
@list l4:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5
	{mso-list-id:2030912929;
	mso-list-template-ids:-825095628;}
@list l5:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l5:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.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'>Michael,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>In our =
research studies, we first thought about VoIP. In that case, if everyone =
uses the same codec, you just have to wait in order to get a packet from =
each flow. (This would not be true if silence suppression is applied, =
however).<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>But other =
services, like games, do not have a fixed cadence. If you look at this =
paper (<a =
href=3D"http://diec.unizar.es/~jsaldana/personal/commag_nov_2011_jsaldana=
.pdf">http://diec.unizar.es/~jsaldana/personal/commag_nov_2011_jsaldana.p=
df</a>) , in which 8 games were analyzed, you may see that each one has =
a different inter-packet time histogram.<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'>We thought =
about different policies for defining which native packet goes in which =
multiplexed packet:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- Fixed =
number of packets: Once you have N packets, you send the multiplexed =
one<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>- Size limit: Once you reach a size (next to =
MTU), you send the multiplexed one<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- Period: =
You send a multiplexed packet every Period<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- Timeout: =
(Very similar to &#8220;period&#8221;) When a packet arrives, if a =
timeout expires, you include it in the bundle and send =
it<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'>Logically, =
&#8220;period&#8221; should be always combined with &#8220;size =
limit&#8221;: if you have an MTU packet, waiting more would be stupid. =
So the traffic class or the signature analysis can give you the maximum =
period, but you should also use the &#8220;size =
limit&#8221;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>The =
question is that we are grouping a number of flows, which may be high. =
In that case, the assumption of having a uniform distribution is not far =
from reality. However, perhaps we could avoid the sentence </span><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>&quot;If a policy =
defining a multiplexing period is used, then the average&nbsp;latency =
added to each packet will be half the multiplexing =
period.&quot;</span><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><pre =
style=3D'line-height:14.4pt'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The paragraph can begin with the next one:</span><span lang=3DEN-US =
style=3D'font-family:"Calibri","sans-serif";color:#1F497D'> =
&#8220;</span><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'=
>A tradeoff appears: the longer the multiplexing period, the higher the =
number of packets which can be grouped, thus obtaining better bandwidth =
savings</span><span lang=3DEN-US style=3D'color:black'>.&#8221; =
<o:p></o:p></span></pre><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'>What do you =
think?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ie</span><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>tf.org] =
<b>En nombre de </b>Michael Ramalho (mramalho)<br><b>Enviado el:</b> =
viernes, 18 de enero de 2013 15:05<br><b>Para:</b> Mirko Su=BEnjevi=E6; =
FERNANDO PASCUAL BLANCO; tcmtf@ietf.org; =
tsvwg@ietf.org<br><b>Asunto:</b> Re: [tsvwg] [tcmtf] Draft: Maximum =
Tolerable Delays when using Tunneling Compressed Multiplexed Traffic =
Flows<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>All,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Strictly =
speaking, the sentence &#8220;</span><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&quot;If a policy defining a =
multiplexing period is used, then the average&nbsp;latency added to each =
packet will be half the multiplexing period.&quot;</span><span =
lang=3DEN-US style=3D'color:#1F497D'>&#8221; makes an explicit =
assumption that the packet arrivals (for TCMTF packets) are =
random/uniform (or even that the arrival pdf is one sided, with the most =
of the pdf area/contribution below the mean =
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'>Why even go =
there?<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'>If someone =
has such a &#8220;policy&#8221; &#8230; the policy is to define the =
maximum worst-case TCMTF (encoding) delay. If the TCMTF encoder has not =
yet built a &#8220;near-MTU&#8221; packet and the worst-case delay timer =
fires &#8230; push the packet out!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>The =
worst-case TCMTF delay we should introduce is determined by the packets =
we want to multiplex within a TCMTF packet. If we knew their traffic =
class &#8230; we would have an idea of what the worst case should be. If =
we didn&#8217;t, but rather made a reasonable assumption (for example, =
based on signature analysis), then we push when our idea of what the =
worst case has been met.<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'>Given that =
the sentence referenced above is not correct (it has an implicit random =
arrival process assumption) &#8211; we need to clarify it if it is =
decided to keep it.<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'>As Gorry =
notes in the next email on this thread, some delay-based congestion =
controls may respond to TCMTF-induced delay as an indication of =
increasing congestion in their congestion control. Anything we can do to =
limit the maximum delay (i.e., have a &#8220;nice&#8221; TCMTF-induced =
delay distribution) would be appreciated.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Michael =
Ramalho<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a =
href=3D"mailto:tsvwg-bounces@ietf.org">tsvwg-bounces@ietf.org</a> [<a =
href=3D"mailto:tsvwg-bounces@ietf.org">mailto:tsvwg-bounces@ietf.org</a>]=
 <b>On Behalf Of </b>Mirko Su=BEnjevic<br><b>Sent:</b> Friday, January =
18, 2013 5:15 AM<br><b>To:</b> FERNANDO PASCUAL BLANCO; <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>; <a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a><br><b>Subject:</b> Re: =
[tsvwg] [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling =
Compressed Multiplexed Traffic Flows<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Yes I =
concur, it is a good notice. I am adding your comment to the review list =
for the next version.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><br>Mirko =
Suznjevic<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> FERNANDO =
PASCUAL BLANCO [<a href=3D"mailto:fpb@tid.es">mailto:fpb@tid.es</a>] =
<br><b>Sent:</b> Thursday, January 17, 2013 10:08 AM<br><b>To:</b> Mirko =
Su=BEnjevi=E6; <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>; <a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a><br><b>Subject:</b> Re: =
[tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed =
Multiplexed Traffic Flows<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><div><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Hi =
Mirko,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Thank you for considering that. =
In addition, one more thing: in section 4, the sentence &quot;If a =
policy defining a multiplexing period is used, then the =
average&nbsp;latency added to each packet will be half the multiplexing =
period.&quot; only applies when there is not enough packet rate to =
fulfill a big packet by multiplexing small ones. When &nbsp;there is a =
lot of packets to multiplex, in general, multiplexing period will not be =
reached, so half the multiplexing period will be the maximum/worse =
average added delay. In general, and when TCMTF is working fine, average =
added delay will be lower.<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>So, I would rewrite that phrase =
as: &quot;If a policy defining a multiplexing period is used, then the =
average&nbsp;latency added to each packet will be half the time to =
fulfill a multiplexed one. In the worse case and if the multiplexing =
period is reached, the average latency added to each packet will be half =
the multiplexing period&quot;.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>What do you =
think?<o:p></o:p></span></p></div><div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Regards,<o:p></o:p></span></p></di=
v><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Fernando Pascual =
Blanco<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>Telef=F3nica Global =
Resources<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>Network Automation =
and Dynamization<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>TECHNOLOGY PEOPLE =
GROUP<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>F =
+34913128779<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>M =
+34682005168<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US 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><p class=3DMsoNormal><span lang=3DEN-US =
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 lang=3DEN-US =
style=3D'color:black'>From: </span></b><span lang=3DEN-US =
style=3D'color:black'>Mirko Su=BEnjevi=E6 &lt;<a =
href=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt;<br>=
<b>Date: </b>martes, 15 de enero de 2013 16:48<br><b>To: </b>Fernando =
Pascual Blanco &lt;<a href=3D"mailto:fpb@tid.es">fpb@tid.es</a>&gt;, =
&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;, &quot;<a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&gt;<br><b>Subject: =
</b>Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling =
Compressed Multiplexed Traffic Flows<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Hello,</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Thanks for all the comments, I will =
briefly respond to them, and include your (as well as previous) =
corrections in a new version of the draft:</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><ul style=3D'margin-top:0cm' =
type=3Ddisc><li class=3DMsoNormal style=3D'color:black;mso-list:l3 =
level1 lfo1'><span lang=3DEN-US style=3D'font-size:10.5pt'>I do not =
understand the sentence &quot;Therefore, we&nbsp;neither take into =
account services using an approach in which all the&nbsp;calculations =
are deployed in the server, which sends a real-time&nbsp;video stream to =
the client.&quot; in section 3.</span><span =
lang=3DEN-US><o:p></o:p></span></li></ul><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>The meaning of this sentence is =
that we will not be looking at the cloud based gaming services such as =
OnLive or Gaiki as they are focused on performing all needed =
calculations of the gamestate on the server, and sending a very =
&#8220;fat&#8221; video stream to the client which only renders the =
video. Therefore they are not suitable for tcmtf. I will change that in =
order to be more clear.</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><ul style=3D'margin-top:0cm' =
type=3Ddisc><li class=3DMsoNormal style=3D'color:black;mso-list:l0 =
level1 lfo2'><span lang=3DEN-US style=3D'font-size:10.5pt'>In section 3 =
(Considered Services), I think it could be also interesting to consider =
non-real time services candidates to be TCMTF optimized. For example =
services like instant messaging, where the bandwidth saving is the main =
benefit of the TCMTF optimization, should be somehow mentioned, =
establishing a kind of delay upper threshold. Related to that, in =
section 3, when talking about web browsing, the sentence &quot;there is =
no need for policy&nbsp;limitations in TCMTF&quot; could =
be&nbsp;disappointed, because actually there are limitations =
(ITU-T_G.1010,&nbsp;10 seconds for web browsing, as in section 4.1 10 =
seconds are considered for streaming audio).</span><span =
lang=3DEN-US><o:p></o:p></span></li></ul><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>At first when we were discussing we =
decided that it will be focused on real-time services, but this can be =
broadened to others non-real-time. I think giving such upper limits has =
a point, although would we even employ tcmtf in cases &nbsp;in which we =
will not have enough data to send a packet in 5 or more seconds? Is that =
feasible? Maybe in some sensor networks? Maybe I am just looking it the =
wrong way, maybe we would have a lot of traffic that needs to be packed =
ASAP!</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><ul style=3D'margin-top:0cm' =
type=3Ddisc><li class=3DMsoNormal style=3D'color:black;mso-list:l4 =
level1 lfo3'><span lang=3DEN-US style=3D'font-size:10.5pt'>In section 4, =
I would change the sentence &quot;A number of flows are =
multiplexed&nbsp;together before being sent through the Internet.&quot; =
for &quot;A number of flows are multiplexed&nbsp;together before being =
sent through the network.&quot;, because the network could not be =
necessary the Internet, I would also adapt Figure 2.</span><span =
lang=3DEN-US><o:p></o:p></span></li></ul><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Ok will be done.</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p><ul =
style=3D'margin-top:0cm' type=3Ddisc><li class=3DMsoNormal =
style=3D'color:black;mso-list:l1 level1 lfo4'><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Maybe the creation of a section 4.4 talking =
about non real time services could be considered including last comments =
(acceptable with the recommendation appearing in the last sentence of =
the section 4.3 &quot;</span><span lang=3DEN-US>It should be =
noted&nbsp;that multiplexing periods of about 1 second can be considered =
as&nbsp;enough for non real time services (e.g., web browsing and =
streaming&nbsp;audio).&quot;)<o:p></o:p></span></li></ul><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Ok, seems =
sound enough. I will write it and see which format looks =
better.</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><ul style=3D'margin-top:0cm' =
type=3Ddisc><li class=3DMsoNormal style=3D'color:black;mso-list:l5 =
level1 lfo5'><span lang=3DEN-US>Table 1 could be included in a separate =
section (i.e.&nbsp;Section 4.5) as a =
summary<o:p></o:p></span></li></ul><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Ok.</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Thanks again for the =
feedback!</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Cheers!<br>Mirko</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
 FERNANDO PASCUAL BLANCO [<a =
href=3D"mailto:fpb@tid.es">mailto:fpb@tid.es</a>] <br><b>Sent:</b> =
Tuesday, January 15, 2013 3:42 PM<br><b>To:</b> Mirko Su=BEnjevi=E6; <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>; <a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a><br><b>Subject:</b> Re: =
[tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed =
Multiplexed Traffic Flows</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Hi Mirko,</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Some comments to the =
draft:</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><ul =
style=3D'margin-top:0cm' type=3Ddisc><li class=3DMsoNormal =
style=3D'color:black;mso-list:l2 level1 lfo6'><span lang=3DEN-US =
style=3D'font-size:10.5pt'>In the introduction it says =
&quot;TCTMF&quot;, it is &quot;TCMTF&quot;.</span><span =
lang=3DEN-US><o:p></o:p></span></li><li class=3DMsoNormal =
style=3D'color:black;mso-list:l2 level1 lfo6'><span lang=3DEN-US =
style=3D'font-size:10.5pt'>I do not understand the sentence =
&quot;Therefore, we&nbsp;neither take into account services using an =
approach in which all the&nbsp;calculations are deployed in the server, =
which sends a real-time&nbsp;video stream to the client.&quot; in =
section 3.</span><span lang=3DEN-US><o:p></o:p></span></li><li =
class=3DMsoNormal style=3D'color:black;mso-list:l2 level1 lfo6'><span =
lang=3DEN-US style=3D'font-size:10.5pt'>In section 3 (Considered =
Services), I think it could be also interesting to consider non-real =
time services candidates to be TCMTF optimized. For example services =
like instant messaging, where the bandwidth saving is the main benefit =
of the TCMTF optimization, should be somehow mentioned, establishing a =
kind of delay upper threshold. Related to that, in section 3, when =
talking about web browsing, the sentence &quot;there is no need for =
policy&nbsp;limitations in TCMTF&quot; could be&nbsp;disappointed, =
because actually there are limitations (ITU-T_G.1010,&nbsp;10 seconds =
for web browsing, as in section 4.1 10 seconds are considered for =
streaming audio).</span><span lang=3DEN-US><o:p></o:p></span></li><li =
class=3DMsoNormal style=3D'color:black;mso-list:l2 level1 lfo6'><span =
lang=3DEN-US style=3D'font-size:10.5pt'>In section 4, I would change the =
sentence &quot;A number of flows are multiplexed&nbsp;together before =
being sent through the Internet.&quot; for &quot;A number of flows are =
multiplexed&nbsp;together before being sent through the network.&quot;, =
because the network could not be necessary the Internet, I would also =
adapt Figure 2.</span><span lang=3DEN-US><o:p></o:p></span></li><li =
class=3DMsoNormal style=3D'color:black;mso-list:l2 level1 lfo6'><span =
lang=3DEN-US style=3D'font-size:10.5pt'>Maybe the creation of a section =
4.4 talking about non real time services could be considered including =
last comments (acceptable with the recommendation appearing in the last =
sentence of the section 4.3 &quot;</span><span lang=3DEN-US>It should be =
noted&nbsp;that multiplexing periods of about 1 second can be considered =
as&nbsp;enough for non real time services (e.g., web browsing and =
streaming&nbsp;audio).&quot;)<o:p></o:p></span></li><li =
class=3DMsoNormal style=3D'color:black;mso-list:l2 level1 lfo6'><span =
lang=3DEN-US>Table 1 could be included in a separate section =
(i.e.&nbsp;Section 4.5) as a summary<o:p></o:p></span></li></ul><div><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>Hope to =
help!<o:p></o:p></span></p></div><div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Regards,</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Fernando Pascual =
Blanco</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Telef=F3nica Global =
Resources</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Network Automation and =
Dynamization</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>TECHNOLOGY PEOPLE =
GROUP</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>F +34913128779</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>M +34682005168</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><a =
href=3D"mailto:fpb@tid.es">fpb@tid.es</a></span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div></div></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'color:black'>From: </span></b><span lang=3DEN-US =
style=3D'color:black'>Mirko Su=BEnjevi=E6 &lt;<a =
href=3D"mailto:Mirko.Suznjevic@fer.hr">Mirko.Suznjevic@fer.hr</a>&gt;<br>=
<b>Date: </b>jueves, 13 de diciembre de 2012 10:06<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;, &quot;<a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>&gt;<br><b>Subject: =
</b>[tcmtf] Draft: Maximum Tolerable Delays when using Tunneling =
Compressed Multiplexed Traffic Flows<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>Hello,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>We have just =
submitted the draft named Maximum Tolerable Delays when using Tunneling =
Compressed Multiplexed Traffic Flows: <a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a><o:p=
></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>It is an =
extension of tcmtf <a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http:=
//datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a>. Since a =
specific list for tcmtf exists (<a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>), the idea is to =
discuss it there.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>The draft =
contains recommendations for TCMTF multiplexing period for different =
real-time services. In order to prevent QoE degradation of real-time =
services using TCMTF, a policy defining&nbsp; a multiplexing period can =
be employed. Values of maximum tolerable delays presented in the draft =
form the base of such policy.&nbsp;&nbsp;&nbsp; The recommendations are =
presented for real-time network services in which TCTMF bandwidth =
optimization is applicable (i.e., services&nbsp; which have low payload =
to header size ratio which results in high protocol =
overhead).<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>Your feedback =
will be welcome. Thank you.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'><br>Sincerely,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>Mirko =
Suznjevic<o:p></o:p></span></p></div></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:black'><hr size=3D2 width=3D"100%" =
align=3Dcenter></span></div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br=
>Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico en el enlace situado m=E1s abajo.<br>This message is =
intended exclusively for its addressee. We only send and receive email =
on the basis of the terms set out at:<br><a =
href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/E=
S/PAGINAS/disclaimer.aspx</a></span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
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 =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'><hr size=3D2 =
width=3D"100%" align=3Dcenter></span></div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br=
>Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico en el enlace situado m=E1s abajo.<br>This message is =
intended exclusively for its addressee. We only send and receive email =
on the basis of the terms set out at:<br><a =
href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/E=
S/PAGINAS/disclaimer.aspx</a></span><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p></o:p></span></p></div></div>=
</body></html>
------=_NextPart_000_0039_01CDF7E7.41240C80--


From fpb@tid.es  Mon Jan 21 06:09:25 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7850121F8754 for <tcmtf@ietfa.amsl.com>; Mon, 21 Jan 2013 06:09:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DPnS9Y0X70ak for <tcmtf@ietfa.amsl.com>; Mon, 21 Jan 2013 06:09:23 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 5B02921F858E for <tcmtf@ietf.org>; Mon, 21 Jan 2013 06:09:20 -0800 (PST)
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 <0MGZ004LHBBII7@tid.hi.inet> for tcmtf@ietf.org; Mon, 21 Jan 2013 15:09:19 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 30.FF.02896.E0C4DF05; Mon, 21 Jan 2013 15:09:18 +0100 (CET)
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 <0MGZ004LBBBHI7@tid.hi.inet> for tcmtf@ietf.org; Mon, 21 Jan 2013 15:09:18 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.165]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.004; Mon, 21 Jan 2013 15:05:58 +0100
Date: Mon, 21 Jan 2013 14:09:17 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <003601cdf7db$d652edf0$82f8c9d0$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>
Message-id: <F5EDC35DF914C1428C28E149F10463A2689E651F@EX10-MB2-MAD.hi.inet>
Content-id: <09683B462ACA2941B682502B3CB3DCA0@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] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
Thread-index: AQHN9+Bvpcun0yIgIEaNuGu9ltFwnA==
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4e69-b7f636d000000b50-20-50fd4c0ecca9
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCKsWRmVeSWpSXmKPExsXCFe9nqMvn8zfA4NQzXYtdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoEro3fGfeaCY41MFZ93b2VtYPzxi7GLkZNDQsBEYknLIyhbTOLC vfVsXYxcHEIC2xglpp6YD+X8YJSY+XkRlLOJUWL2+T2sIC0sAqoS95adYwGx2QS0JE7fXQVm CwsUSHR++AJWwylgIfFzVSfUCgWJP+ceA9VwcIgIxEkc2+8IYjIDjZn3TRGkglfAW+LGo99g 1cwCZhLHX3xghogLSvyYfI8FolxdYsqUXIgScYnm1pssELaixLRFDWCtjAKyEu/mzwc7QESg UOJ+y1w2CFtPYm7TIbCRokB227Ez7BCHCUgs2XOeGcIWlXj5+B/rBEaJWUiumIXkilkIV8xC csUsJFcsYGRdxShWnFSUmZ5RkpuYmZNuYKSXkamXmZdasokREnWZOxiX71Q5xCjAwajEw3vg 7OcAIdbEsuLK3EOMkhxMSqK85h5/A4T4kvJTKjMSizPii0pzUosPMUpwMCuJ8ArYA+V4UxIr q1KL8mFSMhwcShK8oV5AKcGi1PTUirTMHGBqgUkzcXCCtPMAtW/2BGkvLkjMLc5Mh8ifYjTk 2P+k/TkjR8uBbiA5Y2LPc0Yhlrz8vFQpcV47kKECIA0ZpXlwM18xigMdL8zLApLlASZNuGmv gBYxAS3iXfwbZFFJIkJKqoFx+rvYc6W+89YoTGU3fK4ZftFw67Z/VYrcUy5kzze2fs2dKlvh tS8o2LvAm4VzQc6i45o1cyd/jpsq/kT89/+5jG4JpQwO/2r83GMPhfyLjr8oXBbutpRFzSLV 82D58hlGoSv09qdLrN23LTpompjZ34I7+4uf78mc4dF4PNAhKU+B9b57WJsSS3FGoqEWc1Fx IgDn49WyVwMAAA==
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jan 2013 14:09:25 -0000

SGkgYWxsLA0KDQogICAgICAgIEkgYWxzbyB0aGluayB0aGF0IHRoZSBmbG93cyAoVENQIGluIHRo
YXQgY2FzZSkgd2lsbCBoYXZlIHRoZWlyIG93biBlMmUNCmNvbmdlc3Rpb24gY29udHJvbCwgYW5k
IFRDTVRGIHdpbGwgYmUgc29tZXRoaW5nIGluIHRoZSBtaWRkbGUgbm90IGF3YXJlDQphYm91dCB0
aGF0IG1ldGhvZHMuIEluIGNhc2Ugb2YgY29uZ2VzdGlvbiAodG9vIG11Y2ggdHJhZmZpYyBhdCB0
aGUgbXV4KSwNCmJ5IHBlcmZvcm1pbmcgdGhlIFRDTVRGIHRoZSBzaXR1YXRpb24gY291bGQgYmUg
c29sdmVkLCBpZiBub3QsIHBhY2tldA0KZGVsYXkgd2lsbCBiZSBoaWdoZXIgYW5kIHRoZSBmbG93
IHRyYW5zbWl0dGVyIHdpbGwgZ2VuZXJhdGUgcGFja2V0cyBzbG93ZXIuDQogICAgICAgIFRoZSBw
cm9ibGVtIGlzIHRoYXQgdGhlIGRlbGF5IGludHJvZHVjZWQgYnkgdGhlIFRDTVRGIGZ1bmN0aW9u
IGNvdWxkDQp0cmljayB0aGUgb3JpZ2luIG9mIHRoZSBmbG93LCB0aGlua2luZyB0aGF0IHRoZSBm
bG93IHBhdGggaXMgY29uZ2VzdGVkIGFuZA0KcmVkdWNpbmcgdGhlIHRyYW5zbWlzc2lvbiByYXRl
LiBUaGlzIGlzIHNvbWV0aGluZyB0aGF0IHdpbGwgaGF2ZSB0byBiZQ0KYWRkcmVzc2VkLg0KDQpS
ZWdhcmRzLA0KDQpGZXJuYW5kbyBQYXNjdWFsIEJsYW5jbw0KVGVsZWbDs25pY2EgR2xvYmFsIFJl
c291cmNlcw0KTmV0d29yayBBdXRvbWF0aW9uIGFuZCBEeW5hbWl6YXRpb24NClRFQ0hOT0xPR1kg
UEVPUExFIEdST1VQDQpGICszNDkxMzEyODc3OQ0KTSArMzQ2ODIwMDUxNjgNCmZwYkB0aWQuZXMN
Cg0KDQoNCg0KT24gMjEvMDEvMTMgMTQ6MzMsICJKb3NlIFNhbGRhbmEiIDxqc2FsZGFuYUB1bml6
YXIuZXM+IHdyb3RlOg0KDQo+R29ycnksDQo+DQo+UmVnYXJkaW5nIHlvdXIgcXVlc3Rpb246DQo+
PiBSVFQgYW5kL29yIGNvbnRyb2wgZmVlZGJhY2sgd291bGQgYmUgcmVhbGx5IGhlbHBmdWwgaW4g
ZXN0YWJsaXNoaW5nIGENCj4+IGNvbmdlc3Rpb24gY29udHJvbCBvciBjaXJjdWl0LWJyZWFrZXIg
ZnVuY3Rpb24gdG8gZW5zdXJlIHRoZSB0cmFmZmljDQo+PmRvZXMgbm90DQo+PiBjYXVzZSBjb25n
ZXN0aW9uIGNvbGxhcHNlLiBIYXZlIHlvdSB0aG91Z2h0IGFib3V0IHRoaXM/DQo+DQo+SWYgSSB1
bmRlcnN0YW5kIHdlbGwsIHlvdSBhcmUgdGFsa2luZyBhYm91dCB1c2luZyBSVFQgb3IgZmVlZGJh
Y2sgbm90DQo+b25seSBmb3Igc2VsZWN0aW5nIGFuIGFkZXF1YXRlIG11bHRpcGxleGluZyBwZXJp
b2QsIGJ1dCBhbHNvIGZvcg0KPmNvbmdlc3Rpb24gY29udHJvbC4gSXMgdGhpcyB0cnVlPw0KPg0K
PlRoZSBxdWVzdGlvbiBpcyB0aGF0IFRDTVRGIGlzIGRlc2lnbmVkIGZvciB0cmFmZmljIHNhdmlu
Zywgc28gSSB0aGluayB0aGUNCj5jYXVzZSBvZiB0aGUgY29uZ2VzdGlvbiB3b3VsZCBub3QgYmUg
VENNVEYgaXRzZWxmLCBidXQgYSBoaWdoIGFtb3VudCBvZg0KPmZsb3dzLCBvciBhIGhpZ2ggYmFu
ZHdpZHRoIHRvIGFnZ3JlZ2F0ZS4gU28gcGVyaGFwcyBpbiB0aGF0IGNhc2UgdGhlDQo+Zmxvd3Mg
d2hpY2ggYXJlIGJlaW5nIG11bHRpcGxleGVkIHdpbGwgaGF2ZSB0aGVpciBvd24gZW5kLXRvLWVu
ZA0KPmNvbmdlc3Rpb24gY29udHJvbCBtZWNoYW5pc21zLg0KPg0KPkFuIGV4YW1wbGU6IHlvdSBh
cmUgZ3JvdXBpbmcgYSBsb3Qgb2YgVENQIGZsb3dzIG9mIGFuIE1NT1JQRyBnYW1lLiBJZiBhDQo+
Ym90dGxlbmVjayBhcHBlYXJzIGFuZCBkZWxheXMgcmlzZSwgVENQIG1lY2hhbmlzbXMgd2lsbCBh
Y3QgYW5kIHJlZHVjZQ0KPnRoZSByYXRlLg0KPg0KPkNhbiB3ZSBmaW5kIGFuIGV4YW1wbGUgaW4g
d2hpY2ggaW50ZXJydXB0aW5nIHRoZSB1c2Ugb2YgVENNVEYgYW5kIHNlbmRpbmcNCj5uYXRpdmUg
cGFja2V0cyBpbnN0ZWFkIHdpbGwgYmUgbmVjZXNzYXJ5PyBQZXJoYXBzIHRoaXMgb25lOiBpZiB5
b3UgYXJlDQo+dXNpbmcgVENNVEYgZm9yIHJlZHVjaW5nIHBwcyBhbmQgbm90IGJhbmR3aWR0aC4g
VGhpcyBjYW4gaGFwcGVuIHdpdGggVm9JUA0KPmluIGEgc2F0ZWxsaXRlIG5ldHdvcms6IHlvdSBn
cm91cCBwYWNrZXRzIHdpdGhvdXQgaGVhZGVyIGNvbXByZXNzaW9uLiBZb3UNCj5yZWR1Y2UgcHBz
IGFuZCB5b3UgaW5jcmVhc2UgYmFuZHdpZHRoLiBIb3dldmVyLCBJIHRoaW5rIGJhbmR3aWR0aA0K
PmluY3JlYXNlIGlzIHJlYWxseSBzbWFsbDogMjUgYnl0ZXMgZm9yIHRoZSB0dW5uZWwgaGVhZGVy
IGFuZCB0d28gbW9yZQ0KPmJ5dGVzIGZvciBzZXBhcmF0aW5nIGVhY2ggbXVsdGlwbGV4ZWQgcGFj
a2V0LiBJZiB5b3UgYXJlIGdyb3VwaW5nIDEwIFZvSVANCj5wYWNrZXRzICgyMCBJUC84IFVEUC8x
MiBSVFAvMjAgcGF5bG9hZCksIHRoZSB0dW5uZWwgbmVlZHMgMjUgKw0KPjEweCgyKzYwKT02NDVi
eXRlcy4gTmF0aXZlIHRyYWZmaWMgd291bGQgbmVlZCAxMHg2MD02MDAgYnl0ZXMuIFNvDQo+YmFu
ZHdpZHRoIGluY3JlYXNlIGlzIDcuNSUuIElmIHlvdSBncm91cCAyMCBwYWNrZXRzLCBiYW5kd2lk
dGggaW5jcmVhc2UNCj5pcyAxMjY1LzEyMDA9IDUlDQo+DQo+R29ycnksIHdhcyB0aGlzIHlvdXIg
aWRlYT8gQXJlIHlvdSB0aGlua2luZyBhYm91dCBvdGhlciBzY2VuYXJpb3MgaW4NCj53aGljaCBp
bnRlcnJ1cHRpbmcgVENNVEYgY2FuIGJlIGludGVyZXN0aW5nPw0KPg0KPlRoYW5rcyBhIGxvdCwN
Cj4NCj5Kb3NlDQo+DQo+PiAtLS0tLU1lbnNhamUgb3JpZ2luYWwtLS0tLQ0KPj4gRGU6IHRjbXRm
LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0Y210Zi1ib3VuY2VzQGlldGYub3JnXSBFbiBub21i
cmUgZGUNCj4+IEdvcnJ5IEZhaXJodXJzdA0KPj4gRW52aWFkbyBlbDogdmllcm5lcywgMTggZGUg
ZW5lcm8gZGUgMjAxMyAxMToyNQ0KPj4gUGFyYTogdGNtdGZAaWV0Zi5vcmcNCj4+IEFzdW50bzog
UmU6IFt0Y210Zl0gRHJhZnQ6IE1heGltdW0gVG9sZXJhYmxlIERlbGF5cyB3aGVuIHVzaW5nIFR1
bm5lbGluZw0KPj4gQ29tcHJlc3NlZCBNdWx0aXBsZXhlZCBUcmFmZmljIEZsb3dzDQo+Pg0KPj4g
SWYgdGhpcyBpcyBnb2luZyB0byBiZSB1c2VkIGluIHRoZSBnZW5lcmFsIEludGVybmV0LCB0aGVu
IHdlIG5lZWQgdG8NCj4+ZGVjaWRlDQo+PiB3aGV0aGVyIHRoZXJlIGlzIG9uZS13YXkgb3IgdHdv
LXdheSBjb250cm9sIGNvbm5lY3Rpdml0eS4gVGhpcyB3aWxsDQo+PiBkZXRlcm1pbmUgdGhlIGNv
bnN0cmFpbnRzIGZyb20gYSBjb25nZXN0aW9uIGNvbnRyb2wgcGVyc3BlY3RpdmUuDQo+PiBSVFQg
YW5kL29yIGNvbnRyb2wgZmVlZGJhY2sgd291bGQgYmUgcmVhbGx5IGhlbHBmdWwgaW4gZXN0YWJs
aXNoaW5nIGENCj4+IGNvbmdlc3Rpb24gY29udHJvbCBvciBjaXJjdWl0LWJyZWFrZXIgZnVuY3Rp
b24gdG8gZW5zdXJlIHRoZSB0cmFmZmljDQo+PmRvZXMgbm90DQo+PiBjYXVzZSBjb25nZXN0aW9u
IGNvbGxhcHNlLiBIYXZlIHlvdSB0aG91Z2h0IGFib3V0IHRoaXM/DQo+Pg0KPj4gR29ycnkNCj4+
DQo+Pg0KPj4NCj4+IE9uIDE3LzAxLzIwMTMgMTM6NTAsIEpvc2UgU2FsZGFuYSB3cm90ZToNCj4+
ID4gSW4gYWRkaXRpb24sIHBlcmhhcHMgd2UgYXJlIHRvbyBmb2N1c2VkIG9uIG9ubGluZSBnYW1l
cyBhbmQgVm9JUA0KPj4gc2VydmljZXMuIFRoZXJlIGFyZSBvdGhlciBzZXJ2aWNlcyB3aGljaCBh
cmUgb25lLXdheTogcGVyaGFwcyBNMk0NCj4+IGNvbW11bmljYXRpb25zIGRvIG5vdCByZXF1aXJl
IGEgdHdvIHdheSBjb21tdW5pY2F0aW9uLiBXZSBjYW4gdGhpbmsNCj4+IGFib3V0IGEgbnVtYmVy
IG9mIHNlbnNvcnMgc2VuZGluZyB0aGVpciBtZWFzdXJlbWVudHMgdG8gYSBjZW50cmFsDQo+PnNl
cnZlci4NCj4+IFNvIHBlcmhhcHMgUlRUIHdpbGwgbm90IGV2ZW4gZXhpc3QgaW4gdGhpcyBjYXNl
Lg0KPj4gPg0KPj4gPiBKb3NlDQo+PiA+DQo+PiA+PiAtLS0tLU1lbnNhamUgb3JpZ2luYWwtLS0t
LQ0KPj4gPj4gRGU6IEZFUk5BTkRPIFBBU0NVQUwgQkxBTkNPIFttYWlsdG86ZnBiQHRpZC5lc10g
RW52aWFkbyBlbDoganVldmVzLA0KPj4gPj4gMTcgZGUgZW5lcm8gZGUgMjAxMyAxNDozOQ0KPj4g
Pj4gUGFyYToganNhbGRhbmFAdW5pemFyLmVzOyAnRGFuIFdpbmcnOyAnTWlya28gU3XFvm5qZXZp
xIcnOyAnSnVsacOhbg0KPj4gPj4gRmVybsOhbmRleiBOYXZhamFzJw0KPj4gPj4gQ0M6IHRjbXRm
QGlldGYub3JnDQo+PiA+PiBBc3VudG86IFJlOiBbdGNtdGZdIERyYWZ0OiBNYXhpbXVtIFRvbGVy
YWJsZSBEZWxheXMgd2hlbiB1c2luZw0KPj4gPj4gVHVubmVsaW5nIENvbXByZXNzZWQgTXVsdGlw
bGV4ZWQgVHJhZmZpYyBGbG93cw0KPj4gPj4NCj4+ID4+IEpvc2UsDQo+PiA+Pg0KPj4gPj4gICAg
ICAgICAgTGV0wrRzIHNheSB0aGF0IHBsYXlpbmcgd2l0aCB0aGUgT1dEIHlvdSBoYXZlIG1vcmUN
Cj4+ID4+IGdyYW51bGFyaXR5IGluIG9yZGVyIHRvIGtub3cgaW4gd2hpY2ggZGlyZWN0aW9uIHlv
dSBuZWVkIHRvIHJlZHVjZQ0KPj4gPj4gdGhlIGRlbGF5IGJ5IHJlZHVjaW5nIHRoZSBtdWx0aXBs
ZXhpbmcgZGVsYXkuIEJ1dCBwZW9wbGUgd2l0aCBtb3JlDQo+PiA+PiBrbm93bGVkZ2UgYWJvdXQg
b25saW5lIGdhbWVzIHdpbGwgcHJvdmlkZSB1cyBtb3JlIGluZm9ybWF0aW9uIGZvcg0KPj5zdXJl
Lg0KPj4gPj4NCj4+ID4+IFJlZ2FyZHMsDQo+PiA+Pg0KPj4gPj4gRmVybmFuZG8gUGFzY3VhbCBC
bGFuY28NCj4+ID4+IFRlbGVmw7NuaWNhIEdsb2JhbCBSZXNvdXJjZXMNCj4+ID4+IE5ldHdvcmsg
QXV0b21hdGlvbiBhbmQgRHluYW1pemF0aW9uDQo+PiA+PiBURUNITk9MT0dZIFBFT1BMRSBHUk9V
UA0KPj4gPj4gRiArMzQ5MTMxMjg3NzkNCj4+ID4+IE0gKzM0NjgyMDA1MTY4DQo+PiA+PiBmcGJA
dGlkLmVzDQo+PiA+Pg0KPj4gPj4NCj4+ID4+DQo+PiA+Pg0KPj4gPj4gT24gMTcvMDEvMTMgMTM6
MTYsICJKb3NlIFNhbGRhbmEiIDxqc2FsZGFuYUB1bml6YXIuZXM+IHdyb3RlOg0KPj4gPj4NCj4+
ID4+PiBGZXJuYW5kbywNCj4+ID4+Pg0KPj4gPj4+IFNvIHlvdSBtYXkgaGF2ZSB0aGlzIGNhc2U6
DQo+PiA+Pj4gLSB5b3VyIG11bHRpcGxleGluZyBkZWxheSBsaW1pdCBpcyA1MCBtcw0KPj4gPj4+
IC0geW91IGhhdmUgYSBsb3Qgb2YgZmxvd3MgdG8gbXVsdGlwbGV4LCBzbyBwZXJoYXBzIHRoZSB0
aW1lIGJldHdlZW4NCj4+ID4+PiBtdWx0aXBsZXhlZCBwYWNrZXRzIHdpbGwgYmUgNSBtcw0KPj4g
Pj4+IC0geW91IGRldGVjdCBhbiBpbmNyZWFzZSBpbiBSVFQNCj4+ID4+PiAtIHRoZSBzeXN0ZW0g
cmVhY3RzIGFuZCByZWR1Y2VzIG11bHRpcGxleGluZyBwZXJpb2QNCj4+ID4+PiAtIGluIGZhY3Qs
IHRoZSByZWR1Y3Rpb24gZG9lc24ndCBtYXR0ZXIgdW50aWwgdGhlIHBlcmlvZCBpcyByZWR1Y2Vk
DQo+PiA+Pj4gdG8gbGVzcyB0aGFuIDUgbXMNCj4+ID4+Pg0KPj4gPj4+IFNvIHlvdSBvbmx5IGhh
dmUgdG8gbWFrZSB0aGlzIGRlY2lzaW9uOiB1c2luZyB0Y210ZiB3aXRoIDUgbXMgcGVyaW9kDQo+
PiA+Pj4gb3Igbm90LiBJZiBSVFQgaXMgY3JpdGljYWwgeW91IG1heSBub3QgYmUgaW50ZXJlc3Rl
ZCBvbiBzYXZpbmcNCj4+ID4+PiBiYW5kd2lkdGgsIGJ1dCBvbiByZWR1Y2luZyBhIGJpdCB0aGUg
UlRULg0KPj4gPj4+DQo+PiA+Pj4gU28gSSB0aGluayB5b3VyIHF1ZXN0aW9uIGlzOiB3aGF0IGhh
cHBlbnMgaWYgdGhlIFJUVCBpcyB2ZXJ5IGJpZw0KPj4gPj4+IChvdXQgb2YNCj4+ID4+PiBsaW1p
dHMpIGFuZCB5b3UgY2FuIHNhdmUgYmFuZHdpZHRoIHVzaW5nIGEgNW1zIG11bHRpcGxleGluZyBw
ZXJpb2Q/DQo+PiA+Pj4NCj4+ID4+PiBGb3IgZXhhbXBsZSwgdGhlIG1heGltdW0gUlRUIGZvciBh
IGdvb2QgcXVhbGl0eSBpcyA4MCBtcyBhbmQgeW91cg0KPj4gPj4+IG5ldHdvcmsgaGFzIDEyMCBq
dXN0IG5vdy4gSW4gdGhpcyBjYXNlLCBwZXJoYXBzIGhhdmluZyAxMjUgZG9lc24ndA0KPj4gPj4+
IG1hdHRlciwgaWYgeW91IGNhbiBzYXZlIGJhbmR3aWR0aC4NCj4+ID4+Pg0KPj4gPj4+IFRoaXMg
bWFrZXMgc2Vuc2UsIGJ1dCBpdCBpcyBhICJleHRyZW1lIiBjYXNlLiBIb3dldmVyLCB3b3VsZCBp
dCBiZQ0KPj4gPj4+IGFueSBhZHZhbnRhZ2UgaWYgT1dEIGlzIHVzZWQgaW5zdGVhZCBvZiBSVFQ/
DQo+PiA+Pj4NCj4+ID4+PiBCZXN0IHJlZ2FyZHMsDQo+PiA+Pj4NCj4+ID4+PiBKb3NlDQo+PiA+
Pj4NCj4+ID4+Pj4gLS0tLS1NZW5zYWplIG9yaWdpbmFsLS0tLS0NCj4+ID4+Pj4gRGU6IEZFUk5B
TkRPIFBBU0NVQUwgQkxBTkNPIFttYWlsdG86ZnBiQHRpZC5lc10gIEVudmlhZG8gZWw6DQo+PiA+
Pj4+IG1pw6lyY29sZXMsIDE2IGRlIGVuZXJvIGRlIDIwMTMgMTI6NTINCj4+ID4+Pj4gUGFyYTog
anNhbGRhbmFAdW5pemFyLmVzOyAnRGFuIFdpbmcnOyAnTWlya28gU3XFvm5qZXZpxIcnOyAnSnVs
acOhbg0KPj4gPj4+PiBGZXJuw6FuZGV6ICBOYXZhamFzJw0KPj4gPj4+PiBDQzogdGNtdGZAaWV0
Zi5vcmcNCj4+ID4+Pj4gQXN1bnRvOiBSZTogW3RjbXRmXSBEcmFmdDogTWF4aW11bSBUb2xlcmFi
bGUgRGVsYXlzIHdoZW4gdXNpbmcNCj4+ID4+Pj4gVHVubmVsaW5nICBDb21wcmVzc2VkIE11bHRp
cGxleGVkIFRyYWZmaWMgRmxvd3MNCj4+ID4+Pj4NCj4+ID4+Pj4gSGkgSm9zZSwNCj4+ID4+Pj4N
Cj4+ID4+Pj4gICAgICAgICAgWW91IGFyZSByaWdodCwgYnV0IG15IHBvaW50IGhlcmUgaXM6DQo+
PiA+Pj4+DQo+PiA+Pj4+ICAgICAgICAgICAgICAgICAgQ2xpZW50IC0gTXV4IC0gRGVtdXggLSBT
ZXJ2ZXINCj4+ID4+Pj4NCj4+ID4+Pj4gICAgICAgICAgSW1hZ2luZSB0aGF0IHRoZXJlIGlzIGVu
b3VnaCBwYWNrZXRzIGJldHdlZW4gbXV4IGFuZCBkZW11eA0KPj4gPj4+PiB0byBtYWtlICB0aGUg
YWRkZWQgZGVsYXkgdmVyeSBzbWFsbCAoVENNVEYgaXMgd29ya2luZyB2ZXJ5IHdlbGwgYW5kDQo+
PiA+Pj4+IHRoZSBtdXggaGFzIG5vdCAgdG8gd2FpdCB0aGUgbXVsdGlwbGV4aW5nIHBlcmlvZCB0
byBmdWxmaWxsIGEgYmlnDQo+PiA+Pj4+IHBhY2tldCBhbmQgc2VuZCBpdCwgc28gaW1hZ2luZSBh
ICBtdWx0aXBsZXhpbmcgcGVyaW9kIG9mIDUwIG1zIGFuZA0KPj4gPj4+PiBhIGJpZyBwYWNrZXQg
aXMgZnVsZmlsbGVkIGluIDUgbXMpLiBJZiB0aGUgUlRUICBnZXQgaW5jcmVhc2VkDQo+PiA+Pj4+
IGJlY2F1c2UgYSBjb25nZXN0aW9uIGluIHRoZSB3YXkgYmFjayB0byB0aGUgY2xpZW50ICh0aGVy
ZSBpcyBubw0KPj4gPj4+PiBUQ01URg0KPj4gPj4+PiBvcHRpbWl6YXRpb24pIGFuZCB3ZSBkZWNy
ZWFzZSB0aGUgbXVsdGlwbGV4aW5nIHBlcmlvZCAoZXZlbiBpbiB0aGUNCj4+ID4+Pj4gZXh0cmVt
ZSB3ZSBjYW4gZGlzYWJsZSB0aGUgVENNVEYgb3B0aW1pemF0aW9uKSB0aGUgaGlnaCBSVFQgd2ls
bA0KPj4gcmVtYWluLg0KPj4gPj4+PiBFdmVuIGlmIHRoZSBUQ01URiBvcHRpbWl6YXRpb24gd2Fz
IGhlbHBpbmcgaW4gdGhlIGNsaWVudCB0byBzZXJ2ZXINCj4+ID4+Pj4gcGF0aCwgIGRpc2FibGlu
ZyBpdCBtYXkgaGFybS4gRG8geW91IHRoaW5rIHRoYXQgc2NlbmFyaW8gd291bGQgYmUNCj4+IHBv
c3NpYmxlPw0KPj4gPj4+Pg0KPj4gPj4+PiAgICAgICAgICBTbyBJwrRtIG5vdCBzdXJlIGFib3V0
IHRoYXQsIEkgdGhpbmsgd2UgbmVlZCBtb3JlIG9waW5pb25zDQo+PmhlcmUuDQo+PiA+Pj4+DQo+
PiA+Pj4+IFJlZ2FyZHMsDQo+PiA+Pj4+DQo+PiA+Pj4+IEZlcm5hbmRvIFBhc2N1YWwgQmxhbmNv
DQo+PiA+Pj4+IFRlbGVmw7NuaWNhIEdsb2JhbCBSZXNvdXJjZXMNCj4+ID4+Pj4gTmV0d29yayBB
dXRvbWF0aW9uIGFuZCBEeW5hbWl6YXRpb24gVEVDSE5PTE9HWSBQRU9QTEUgR1JPVVANCj4+IEYN
Cj4+ID4+Pj4gKzM0OTEzMTI4Nzc5IE0gKzM0NjgyMDA1MTY4IGZwYkB0aWQuZXMNCj4+ID4+Pj4N
Cj4+ID4+Pj4NCj4+ID4+Pj4NCj4+ID4+Pj4NCj4+ID4+Pj4gT24gMTYvMDEvMTMgMTE6NTcsICJK
b3NlIFNhbGRhbmEiIDxqc2FsZGFuYUB1bml6YXIuZXM+IHdyb3RlOg0KPj4gPj4+Pg0KPj4gPj4+
Pj4gTXkgdHdvIGNlbnRzOg0KPj4gPj4+Pj4NCj4+ID4+Pj4+IEluIGdhbWVzIGFuZCBpbiBWb0lQ
IHRoZSByZWFsbHkgaW1wb3J0YW50IHRoaW5nIGlzIFJUVDoNCj4+ID4+Pj4+DQo+PiA+Pj4+PiAt
IEdhbWVzIGFsd2F5cyBtZWFzdXJlIHRoZSBSVFQgKGdhbWVycyB0YWxrIGFib3V0IHRoZSAicGlu
ZyIpOiB0aGUNCj4+ID4+Pj4+IGltcG9ydGFudCB0aGluZyBpcyB0aGUgZGVsYXkgZnJvbSBhIHBs
YXllciBhY3Rpb24gdG8gdGhlIHNlcnZlcg0KPj4gPj4+Pj4gcmVhY3Rpb24gYXJyaXZpbmcgdG8g
dGhlIHBsYXllcidzIG1hY2hpbmUuDQo+PiA+Pj4+PiAtIEluIFZvSVAgSSB0aGluayBpdCBpcyB0
aGUgc2FtZTogd2hhdCBtYXR0ZXJzIGlzIHRoZSBSVFQsIGluDQo+PiA+Pj4+PiBvcmRlciB0byBn
cmFudCBpbnRlcmFjdGl2aXR5IGFuZCBhdm9pZGluZyBjcm9zcy10YWxrLg0KPj4gPj4+Pj4NCj4+
ID4+Pj4+IEluIGFkZGl0aW9uLCBSVFQgaXMgZWFzaWVyIHRvIG1lYXN1cmUgdGhhbiBPV0QsIHNp
bmNlIHlvdSBkb24ndA0KPj4gPj4+Pj4gbmVlZCBzeW5jaHJvbml6YXRpb24uDQo+PiA+Pj4+Pg0K
Pj4gPj4+Pj4gQW5kIHJlZ2FyZGluZyBUd28td2F5IFRDTVRGLCBJIHRoaW5rIHdlIGhhdmUgdG8g
dGhpbmsgYWJvdXQgVENNVEYNCj4+ID4+Pj4+IGFzIG9uZS13YXkuIE90aGVyd2lzZSwgdGhpbmdz
IHdvdWxkIGJlY29tZSB2ZXJ5IGNvbXBsaWNhdGVkLg0KPj4gU29tZQ0KPj4gPj4+PiBzZXJ2aWNl
cw0KPj4gPj4+Pj4gaGF2ZSB2ZXJ5IGRpZmZlcmVudCBjbGllbnQtc2VydmVyIGFuZCBzZXJ2ZXIt
Y2xpZW50IHRyYWZmaWMNCj4+ID4+Pj4+IHBhdHRlcm5zIChlLmcuIGdhbWVzKS4gSW4gYWRkaXRp
b24sIHNvbWV0aW1lcyB0aGUgdHdvIGZsb3dzIGNhbg0KPj4gPj4+Pj4gZm9sbG93IGRpZmZlcmVu
dCBuZXR3b3JrIHBhdGhzLiBJIHRoaW5rIG9uY2Ugd2UgdGFsa2VkIGFib3V0IGENCj4+ID4+Pj4+
IG5ldHdvcmsgcHJvdmlkZXIgdXNpbmcgYSBudW1iZXIgb2YgSVNQcy4NCj4+ID4+Pj4+DQo+PiA+
Pj4+PiBIb3dldmVyLCB1c2luZyBSVFQgZm9yIHR1bmluZyBhIG9uZS13YXkgVENNVEYgbWF5IG5v
dCBiZSBiYWQuLi4gb3INCj4+ID4+Pj4+IGlzIGl0IGJhZD8gQW55IG90aGVyIHRob3VnaHRzPw0K
Pj4gPj4+Pj4NCj4+ID4+Pj4+IEJSLA0KPj4gPj4+Pj4NCj4+ID4+Pj4+IEpvc2UNCj4+ID4+Pj4+
DQo+PiA+Pj4+Pj4gLS0tLS1NZW5zYWplIG9yaWdpbmFsLS0tLS0NCj4+ID4+Pj4+PiBEZTogRkVS
TkFORE8gUEFTQ1VBTCBCTEFOQ08gW21haWx0bzpmcGJAdGlkLmVzXSAgRW52aWFkbyBlbDoNCj4+
ID4+Pj4gbWFydGVzLA0KPj4gPj4+Pj4+IDE1IGRlIGVuZXJvIGRlIDIwMTMgMTg6MDQNCj4+ID4+
Pj4+PiBQYXJhOiBqc2FsZGFuYUB1bml6YXIuZXM7ICdEYW4gV2luZyc7ICdNaXJrbyBTdcW+bmpl
dmnEhyc7IEp1bGnDoW4NCj4+ID4+Pj4+PiBGZXJuw6FuZGV6ICBOYXZhamFzDQo+PiA+Pj4+Pj4g
Q0M6IHRjbXRmQGlldGYub3JnDQo+PiA+Pj4+Pj4gQXN1bnRvOiBSZTogW3RjbXRmXSBEcmFmdDog
TWF4aW11bSBUb2xlcmFibGUgRGVsYXlzIHdoZW4gdXNpbmcNCj4+ID4+Pj4+PiBUdW5uZWxpbmcg
IENvbXByZXNzZWQgTXVsdGlwbGV4ZWQgVHJhZmZpYyBGbG93cw0KPj4gPj4+Pj4+DQo+PiA+Pj4+
Pj4gSGkgYWxsLA0KPj4gPj4+Pj4+DQo+PiA+Pj4+Pj4gICAgICAgICAgVG8gcmUtb3BlbiB0aGF0
IGlzc3VlLCBJIHdvdWxkIHN1Z2dlc3QgdGhhdCBnaXZlbiB0aGF0DQo+PiA+Pj4+Pj4gdGhlIGRl
bGF5IGlzIHNvICBzZW5zaXRpdmUgaW4gcmVhbCB0aW1lIHNlcnZpY2VzLCB3ZSBuZWVkIHRvIGZp
bmQNCj4+ID4+Pj4+PiBhIGNvbnNlbnN1cyBoZXJlLg0KPj4gPj4+Pj4+DQo+PiA+Pj4+Pj4gICAg
ICAgICAgTXkgb3BpbmlvbiBpcyB0aGF0IHRvIGFwcGx5IHRoZSBmaXJzdCBwb3NzaWJpbGl0eSAo
dGhlDQo+PiA+Pj4+Pj4gc3RhdGljIG11bHRpcGxleGluZw0KPj4gPj4+Pj4+IHBlcmlvZCkgd2Ug
bmVlZCB0byBzdXBwb3NlIHRoYXQgdGhlIG5ldHdvcmsgY29uZGl0aW9ucyBhcmUgcmVhbGx5DQo+
PiA+Pj4+Pj4gYmFkLCB0byBiZSAgcHJvdGVjdGVkIHdoZW4gdGhlIG5ldHdvcmsgY29uZ2VzdGlv
biBhcmlzZXMuIEluIHRoYXQNCj4+ID4+Pj4+PiBjYXNlLCB0aGUgYXBwbGljYXRpb24gIG9mIHRo
ZSBUQ01URiBvcHRpbWl6YXRpb24gd2lsbCBub3QgYmUNCj4+ID4+Pj4+PiBvcHRpbWFsLCBzbyB0
aGF0IHdvdWxkIGJlIHRoZSBsZXNzICBwcmVmZXJyZWQgb3B0aW9uLCBidXQgZWFzaWVyDQo+PiA+
Pj4+Pj4gdG8gaW1wbGVtZW50IGFuZCBtYWludGFpbiBvdmVyIHRoZSB0aW1lLg0KPj4gPj4+Pj4+
DQo+PiA+Pj4+Pj4gICAgICAgICAgT24gdGhlIG90aGVyIGhhbmQsIHRoZSBzZWNvbmQgcG9zc2li
aWxpdHkgd291bGQgYmUgdGhlDQo+PiA+Pj4+Pj4gcHJlZmVycmVkLiBJdCBpcyAgZWFzeSB0byBr
bm93IHRoZSBkZWxheSBiZXR3ZWVuIHRoZSBtdXggYW5kIHRoZQ0KPj4gPj4+Pj4+IGRlbXV4IGJ1
dCBtb3N0IG9mIHRoZSAgdGltZXMgd2lsbCBub3QgYmUgZW5vdWdoIHVubGVzcyBtdXggYW5kDQo+
PiA+Pj4+Pj4gZGVtdXggd2VyZSByZWFsbHkgbmVhciBmcm9tIHRoZSAgY2xpZW50IGFuZCB0aGUg
c2VydmVyDQo+PiA+Pj4+Pj4gcmVzcGVjdGl2ZWx5LiBJIGFncmVlIHdpdGggSm9zZSBpbiB0aGUg
cG9zc2liaWxpdHkgb2Ygc25vb3AgIFJUQ1ANCj4+ID4+Pj4+PiBwYWNrZXRzIGluIG9yZGVyIHRv
IGFkYXB0IHRoZSBtdWx0aXBsZXhpbmcgcGVyaW9kIHdoZW4NCj4+ID4+Pj4+PiBtdWx0aXBsZXhp
bmcgUlRQIHBhY2tldHMgKGFuZCBSVENQIGlzIGF2YWlsYWJsZSkuIFRhbGtpbmcgYWJvdXQNCj4+
ID4+Pj4+PiBSVFQsIEnCtG0gbm90IHN1cmUgaWYgUlRUICB3b3VsZCBiZSB1c2VmdWwgZ2l2ZW4g
dGhhdCB0aGUNCj4+ID4+Pj4+PiBtdWx0aXBsZXhpbmcgcGVyaW9kIG9ubHkgYWZmZWN0IHRoZSBv
bmUgd2F5ICBkZWxheSAoT1dEKS4gSW1hZ2luZQ0KPj4gdGhlIGZvbGxvd2luZyBzY2VuYXJpbzoN
Cj4+ID4+Pj4+PiAgICAgICAgICAtIENsaWVudCAtIE11eC9EZW11eCAtIERlbXV4L011eCAtIFNl
cnZlciAodHdvIHdheXMNCj4+ID4+Pj4+PiBUQ01URiwgVFdUQ01URiA6UCkNCj4+ID4+Pj4+PiAg
ICAgICAgICAtIFRoZSBPV0QgZnJvbSBzZXJ2ZXIgdG8gY2xpZW50IGdldCBpbmNyZWFzZWQNCj4+
ID4+Pj4+PiAgICAgICAgICAtIFRoZSBPV0QgZnJvbSBjbGllbnQgdG8gc2VydmVyIHJlbWFpbnMg
ZXF1YWwNCj4+ID4+Pj4+PiAgICAgICAgICAtIFNob3VsZCB3ZSB1c2UgYSBsb3dlciBtdWx0aXBs
ZXhpbmcgcGVyaW9kIGluIHRoZQ0KPj4gPj4+Pj4+IGNsaWVudCB0byBzZXJ2ZXIgIGRpcmVjdGlv
bj8gSSBkb27CtHQgdGhpbmsgc2/igKYgYmVjYXVzZSB3ZSBzaG91bGQNCj4+ID4+Pj4+PiB1c2Ug
YSBsb3dlciBtdWx0aXBsZXhpbmcgIHBlcmlvZCBpbiB0aGUgb3RoZXIgZGlyZWN0aW9uLg0KPj4g
Pj4+Pj4+DQo+PiA+Pj4+Pj4gICAgICAgICAgTXkgcG9pbnQgaXMgdGhhdCB0aGUgbXVsdGlwbGV4
aW5nIHBlcmlvZCBzaG91bGQgb25seSBiZQ0KPj4gPj4+Pj4+IGFmZmVjdGVkIGJ5IHRoZSAgT1dE
IGFuZCBub3QgYnkgdGhlIFJUVCAob3IgaXQgbWF5IGJlIGFwcGxpY2F0aW9uDQo+PiA+Pj4+Pj4g
ZGVwZW5kZW50KS4gSG93IHRvICBjYWxjdWxhdGUgdGhlIE9XRD8gScK0dmUgYmVlbiByZWFkaW5n
DQo+PiA+Pj4+Pj4gc29tZXRoaW5nIGFib3V0IE9XQU1QIGFuZCBpdCAgc2VlbXMgdGhhdCBhbiBz
cGVjaWZpYyBzb2Z0d2FyZSBoYXMNCj4+ID4+Pj4+PiB0byBiZSBpbXBsZW1lbnRlZCBpbiB0aGUg
Y2xpZW50L3NlcnZlciAgc2lkZS4NCj4+ID4+Pj4+PiBDYW4gd2UgYXNzdW1lIHRoYXQ/IFVuZm9y
dHVuYXRlbHkgSSBjYW5ub3QgY29udHJpYnV0ZSBzbyBtdWNoDQo+PiA+PiBoZXJl4oCmDQo+PiA+
Pj4+Pj4gICAgICAgICAgSXQgaXMgcG9zc2libGUgdGhhdCBmb3IgY2VydGFpbiBzZXJ2aWNlcyB0
aGUgc3RhdGljIChhbmQNCj4+ID4+Pj4+PiB3b3JzdA0KPj4gPj4+Pj4+IGNhc2UpDQo+PiA+Pj4+
Pj4gbXVsdGlwbGV4aW5nIHBlcmlvZCB3b3VsZCBiZSB0aGUgYmV0dGVyIHNvbHV0aW9uLg0KPj4g
Pj4+Pj4+DQo+PiA+Pj4+Pj4gICAgICAgICAgV2hhdCBkbyB5b3UgdGhpbms/DQo+PiA+Pj4+Pj4N
Cj4+ID4+Pj4+PiBSZWdhcmRzLA0KPj4gPj4+Pj4+DQo+PiA+Pj4+Pj4gRmVybmFuZG8gUGFzY3Vh
bCBCbGFuY28NCj4+ID4+Pj4+PiBUZWxlZsOzbmljYSBHbG9iYWwgUmVzb3VyY2VzDQo+PiA+Pj4+
Pj4gTmV0d29yayBBdXRvbWF0aW9uIGFuZCBEeW5hbWl6YXRpb24gVEVDSE5PTE9HWSBQRU9QTEUN
Cj4+IEdST1VQDQo+PiA+PiBGDQo+PiA+Pj4+Pj4gKzM0OTEzMTI4Nzc5IE0gKzM0NjgyMDA1MTY4
IGZwYkB0aWQuZXMNCj4+ID4+Pj4+Pg0KPj4gPj4+Pj4+DQo+PiA+Pj4+Pj4NCj4+ID4+Pj4+Pg0K
Pj4gPj4+Pj4+IE9uIDE3LzEyLzEyIDEyOjI1LCAiSm9zZSBTYWxkYW5hIiA8anNhbGRhbmFAdW5p
emFyLmVzPiB3cm90ZToNCj4+ID4+Pj4+Pg0KPj4gPj4+Pj4+PiBIaSBhbGwsDQo+PiA+Pj4+Pj4+
DQo+PiA+Pj4+Pj4+IEp1bGlhbiBhbmQgSSBoYXZlIGJlZW4gZGlzY3Vzc2luZyBhYm91dCB0aGlz
LiBTb21lIGlkZWFzIGhhdmUNCj4+ID4+Pj4gYXJpc2VuLg0KPj4gPj4+Pj4+PiBUaGlzIGlzIHRo
ZSBzdW1tYXJ5Lg0KPj4gPj4+Pj4+Pg0KPj4gPj4+Pj4+PiBUaGlzIHdvdWxkIGJlIHRoZSBzY2hl
bWUgb2YgdGhlIHN5c3RlbSwgaW5jbHVkaW5nIG11eCBhbmQNCj4+IGRlbXV4Og0KPj4gPj4+Pj4+
Pg0KPj4gPj4+Pj4+PiBSZWFsLXRpbWUgYXBwbGljYXRpb24gLS0tLS0tLSBtdXggLS0tLS0tLS0g
aW50ZXJuZXQgLS0tLS0tLS0tDQo+PiA+Pj4+Pj4+IGRlbXV4DQo+PiA+Pj4+Pj4+IC0tLS0tLS0N
Cj4+ID4+Pj4+Pj4gc2VydmVyDQo+PiA+Pj4+Pj4+DQo+PiA+Pj4+Pj4+DQo+PiA+Pj4+Pj4+IEkg
dGhpbmsgcGVyaGFwcyB0aGUgZHJhZnQgY291bGQgc2F5IHNvbWV0aGluZyBsaWtlOg0KPj4gPj4+
Pj4+Pg0KPj4gPj4+Pj4+PiBXaGVuIHNldHRpbmcgdGhlIG11bHRpcGxleGluZyBwZXJpb2QsIHRo
ZXJlIGFyZSB0d28NCj4+cG9zc2liaWxpdGllczoNCj4+ID4+Pj4+Pj4NCj4+ID4+Pj4+Pj4gMS4t
IFN0YXRpYyAvIHBlcm1hbmVudDogQXQgc3lzdGVtIHNldHVwIHRpbWUsIG5ldHdvcmsgZGVsYXlz
IGFyZQ0KPj4gPj4+Pj4+PiBtZWFzdXJlZCwgYW5kIGEgbXVsdGlwbGV4aW5nIHBlcmlvZCBpcyBz
ZWxlY3RlZCBhbmQgc2V0IGluIHRoZQ0KPj4gPj4+Pj4+IG11bHRpcGxleGVyLg0KPj4gPj4+Pj4+
Pg0KPj4gPj4+Pj4+PiAyLi0gRHluYW1pYzogQSBtZWNoYW5pc20gaXMgdXNlZCBzbyBhcyB0byBh
ZGFwdCB0byB0aGUgZXZvbHV0aW9uDQo+PiA+Pj4+Pj4+IG9mIG5ldHdvcmsgZGVsYXlzLiBJbiB0
aGlzIGNhc2UsIGRpZmZlcmVudCBtZWNoYW5pc21zIGNhbiBiZQ0KPj4gPj4+Pj4+PiB1c2VkIGlu
IG9yZGVyIHRvIG9idGFpbiBwZXJpb2RpY2FsIGVuZC10by1lbmQgbmV0d29yayBkZWxheQ0KPj4g
Pj4+Pj4+PiBlc3RpbWF0aW9ucywgd2hpY2ggd291bGQgYmUgdXNlZnVsIGluIG9yZGVyIHRvIHNl
dCB0aGUNCj4+ID4+Pj4+Pj4gbXVsdGlwbGV4aW5nDQo+PiA+PiBwZXJpb2Q6DQo+PiA+Pj4+Pj4+
DQo+PiA+Pj4+Pj4+IC0gSWYgdGhlIHRyYWZmaWMgaXMgUlRQLCB0aGVuIFJUQ1AgcGFja2V0cyBj
b250YWluaW5nIHRoZQ0KPj4gPj4+Pj4+PiBlc3RpbWF0aW9uIGNvdWxkIGJlIGFuYWx5emVkIGlu
IG9yZGVyIHRvIGV4dHJhY3QgdGhlc2UgdmFsdWVzLA0KPj4gPj4+Pj4+PiBhcyBEYW4NCj4+ID4+
IHN1Z2dlc3RzLg0KPj4gPj4+Pj4+PiBUaGUgcXVlc3Rpb24NCj4+ID4+Pj4+Pj4gaXM6IHdvdWxk
IHRoYXQgcGFja2V0cyB0cmF2ZWwgdGhyb3VnaCB0aGUgbXVsdGlwbGV4ZXI/DQo+PiA+Pj4+Pj4+
IC0gSWYgdGhlIHRyYWZmaWMgaXMgVENQLCBwZXJoYXBzIHNvbWV0aGluZyBzaW1pbGFyIHRvIHRo
ZSBSVFQNCj4+ID4+Pj4+Pj4gZXN0aW1hdGlvbiBvZiBUQ1AgY291bGQgYmUgdXNlZnVsLg0KPj4g
Pj4+Pj4+PiAtIElmIHRoZSB0cmFmZmljIGlzIFVEUCwgc2hvdWxkIHRoZSBtdXggdXNlIHNvbWV0
aGluZyBsaWtlIE9XQU1QDQo+PiA+Pj4+Pj4+IChodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9y
ZmM0NjU2KSBpbiBvcmRlciB0byBjYWxjdWxhdGUgdHdvDQo+PiA+Pj4+Pj4+IGRlbGF5cyAoYXBw
bGljYXRpb24gdG8gbXV4LCBhbmQgbXV4IHRvIHNlcnZlcikgYW5kIGNhbGN1bGF0ZSB0aGUNCj4+
ID4+Pj4gc3VtPw0KPj4gPj4+Pj4+Pg0KPj4gPj4+Pj4+Pg0KPj4gPj4+Pj4+PiBJIHRoaW5rIHRo
ZSBkcmFmdCBpcyBvbmx5IHN1cHBvc2VkIHRvIHJlcG9ydCB0aGUgbWF4aW11bSBkZWxheXMNCj4+
ID4+Pj4+Pj4gbm9ybWFsbHkgY29uc2lkZXJlZCBhY2NlcHRhYmxlLiBQZXJoYXBzIHRoZSBhZGRp
dGlvbmFsDQo+PiA+Pj4+Pj4+IG1lY2hhbmlzbXMgZm9yIGNhbGN1bGF0aW5nIHRoZSBSVFQgY291
bGQganVzdCBiZSBzdWdnZXN0ZWQuDQo+PiA+Pj4+Pj4+DQo+PiA+Pj4+Pj4+IFdoYXQgZG8geW91
IHRoaW5rPw0KPj4gPj4+Pj4+Pg0KPj4gPj4+Pj4+PiBKb3NlDQo+PiA+Pj4+Pj4+DQo+PiA+Pj4+
Pj4+PiAtLS0tLU1lbnNhamUgb3JpZ2luYWwtLS0tLQ0KPj4gPj4+Pj4+Pj4gRGU6IHRjbXRmLWJv
dW5jZXNAaWV0Zi5vcmcgW21haWx0bzp0Y210Zi1ib3VuY2VzQGlldGYub3JnXSBFbg0KPj4gPj4+
Pj4+Pj4gbm9tYnJlIGRlIERhbiBXaW5nIEVudmlhZG8gZWw6IHZpZXJuZXMsIDE0IGRlIGRpY2ll
bWJyZSBkZSAyMDEyDQo+PiA+Pj4+Pj4+PiAxODozMw0KPj4gPj4+Pj4+Pj4gUGFyYToganNhbGRh
bmFAdW5pemFyLmVzOyAnTWlya28gU3XFvm5qZXZpxIcnDQo+PiA+Pj4+Pj4+PiBDQzogdGNtdGZA
aWV0Zi5vcmcNCj4+ID4+Pj4+Pj4+IEFzdW50bzogUmU6IFt0Y210Zl0gRHJhZnQ6IE1heGltdW0g
VG9sZXJhYmxlIERlbGF5cyB3aGVuIHVzaW5nDQo+PiA+Pj4+Pj4+PiBUdW5uZWxpbmcgQ29tcHJl
c3NlZCBNdWx0aXBsZXhlZCBUcmFmZmljIEZsb3dzDQo+PiA+Pj4+Pj4+Pg0KPj4gPj4+Pj4+Pj4+
IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiA+Pj4+Pj4+Pj4gRnJvbTogSm9zZSBTYWxk
YW5hIFttYWlsdG86anNhbGRhbmFAdW5pemFyLmVzXQ0KPj4gPj4+Pj4+Pj4+IFNlbnQ6IEZyaWRh
eSwgRGVjZW1iZXIgMTQsIDIwMTIgMjo1OCBBTQ0KPj4gPj4+Pj4+Pj4+IFRvOiAnRGFuIFdpbmcn
OyAnTWlya28gU3XFvm5qZXZpxIcnDQo+PiA+Pj4+Pj4+Pj4gQ2M6IHRjbXRmQGlldGYub3JnDQo+
PiA+Pj4+Pj4+Pj4gU3ViamVjdDogUkU6IFt0Y210Zl0gRHJhZnQ6IE1heGltdW0gVG9sZXJhYmxl
IERlbGF5cyB3aGVuDQo+PiA+Pj4+Pj4+Pj4gdXNpbmcgVHVubmVsaW5nIENvbXByZXNzZWQgTXVs
dGlwbGV4ZWQgVHJhZmZpYyBGbG93cw0KPj4gPj4+Pj4+Pj4+DQo+PiA+Pj4+Pj4+Pj4gRGFuLA0K
Pj4gPj4+Pj4+Pj4+DQo+PiA+Pj4+Pj4+Pj4gUmVnYXJkaW5nIHRoZSB1c2Ugb2YgdGhlIG1heGlt
dW0gZGVsYXksIHNvbWUgZGF5cyBhZ28gd2UNCj4+ID4+Pj4+Pj4+PiBkaXNjdXNzZWQgYWJvdXQN
Cj4+ID4+Pj4+Pj4+PiBpdDoNCj4+ID4+Pj4+Pj4+PiB0aGUgYWN0dWFsIE9XRCBvZiB0aGUgbmV0
d29yayBzaG91bGQgYmUgbWVhc3VyZWQgKG9yDQo+PiA+Pj4+Pj4+Pj4gZXN0aW1hdGVkKSBpbiBv
cmRlciB0byBrbm93IHRoZSBtYXhpbXVtIG11bHRpcGxleGluZyBwZXJpb2QNCj4+IHdlDQo+PiA+
PiBjYW4gc2V0Lg0KPj4gPj4+Pj4+Pj4+DQo+PiA+Pj4+Pj4+Pj4gV2UgbWF5IGhhdmUgdGhpcyBm
b3JtdWxhLCBpZiB0aGlua2luZyBvbmUtd2F5Og0KPj4gPj4+Pj4+Pj4+DQo+PiA+Pj4+Pj4+Pj4g
T1dEICArIE11eCBwZXJpb2QvMiAgPCB0b2xlcmFibGVfT1dEDQo+PiA+Pj4+Pj4+Pj4NCj4+ID4+
Pj4+Pj4+PiBJZiB3ZSB0aGluayBSVFQ6DQo+PiA+Pj4+Pj4+Pj4NCj4+ID4+Pj4+Pj4+PiBPV0Qg
KyBNdXggcGVyaW9kLzIgKyBPV0QgYmFjayA8IDIqdG9sZXJhYmxlX09XRA0KPj4gPj4+Pj4+Pj4+
DQo+PiA+Pj4+Pj4+Pj4gSSBkb24ndCBrbm93IGlmIHdlIHNob3VsZCBpbmNsdWRlIGEgbWVjaGFu
aXNtIGZvciBlc3RpbWF0aW5nDQo+PiA+Pj4+Pj4+Pj4gT1dEIGluIHRjbXRmLiBJIHRoaW5rIHRo
aXMgaXMgbW9yZSBhbiBpbXBsZW1lbnRhdGlvbiBwcm9ibGVtLA0KPj4gPj4+Pj4+Pj4+IHdoaWNo
IG1heSBiZSBhbHJlYWR5IHNvbHZlZC4NCj4+ID4+Pj4+Pj4+DQo+PiA+Pj4+Pj4+PiBZZXMsIGl0
J3MgYWxyZWFkeSBzb2x2ZWQgZW5kLXRvLWVuZDogIFJUUCB3aXRoIFJUQ1AgZmVlZGJhY2sNCj4+
ID4+Pj4+Pj4+IGFsbG93cyBkZXRlcm1pbmluZyBvbmUgd2F5IGRlbGF5Lg0KPj4gPj4+Pj4+Pj4N
Cj4+ID4+Pj4+Pj4+IEJ1dCBpZiBzb21ldGhpbmcgaW4gdGhlIG1pZGRsZSBpcyBtdWx0aXBsZXhp
bmcgc2V2ZXJhbCBwYWNrZXRzDQo+PiA+Pj4+Pj4+PiB0b2dldGhlciwNCj4+ID4+Pj4+Pj4gd2UN
Cj4+ID4+Pj4+Pj4+IGRvbid0IHdhbnQgaXQgdG8gYWRkIHRvbyBtdWNoIGRlbGF5LiAgVGhhdCB0
aGluZyBpbiB0aGUgbWlkZGxlDQo+PiA+Pj4+Pj4+PiB3b24ndCBuZWNlc3NhcmlseSBrbm93IHRo
ZSBvbmUgd2F5IGRlbGF5IHNlZW4gYnkgdGhlIGVuZHBvaW50cywNCj4+ID4+Pj4+Pj4+IHVubGVz
cyBpdCBhbmFseXplcyB0aGUgUlRQIGFuZCBSVENQLiAgVGhlcmUgYXJlIGRldmljZXMgdGhhdCBk
bw0KPj4gPj4+Pj4+Pj4gdGhhdCBvbiB0aGUgbWFya2V0LCAgbW9zdGx5IHRvIGRpYWdub3NlIHdo
ZXJlIG5ldHdvcmtzIGFyZQ0KPj4gPj4+Pj4+Pj4gY2F1c2luZyBsb3NzL2RlbGF5IHdpdGggUlRQ
IGZsb3dzLg0KPj4gPj4+Pj4+Pj4NCj4+ID4+Pj4+Pj4+DQo+PiA+Pj4+Pj4+Pj4gQW5vdGhlciBv
cHRpb24gaXMgdXNpbmcgc29tZSB0eXBpY2FsIHZhbHVlcywgZS5nLiBmcm9tDQo+PiA+Pj4+Pj4+
Pj4NCj4+ID4+IGh0dHA6Ly9pcG5ldHdvcmsuYmd0bW8uaXAuYXR0Lm5ldC9wd3MvZ2xvYmFsX25l
dHdvcmtfYXZncy5odG0NCj4+ID4+Pj4+Pj4+PiBsDQo+PiA+Pj4+Pj4+Pj4NCj4+ID4+Pj4+Pj4+
PiBUaGUgZHJhZnQgaW5jbHVkZXMgc29tZSBwcmVsaW1pbmFyeS9yZWNvbW1lbmRlZCB2YWx1ZXMg
Zm9yDQo+PiB0aGUNCj4+ID4+Pj4+Pj4+PiBNdWx0aXBsZXhpbmcgUGVyaW9kLiBJcyB0aGlzIGlu
dGVyZXN0aW5nPyBTaG91bGQgd2UgcHV0IHRoZQ0KPj4gPj4+Pj4+Pj4+IGZvcm11bGEgaW5zdGVh
ZD8NCj4+ID4+Pj4+Pj4+DQo+PiA+Pj4+Pj4+PiBJdCdzIHByb2JhYmx5IHN1ZmZpY2llbnQgYXMt
aXMuDQo+PiA+Pj4+Pj4+Pg0KPj4gPj4+Pj4+Pj4gLWQNCj4+ID4+Pj4+Pj4+DQo+PiA+Pj4+Pj4+
Pj4gTWlya28sIGFub3RoZXIgcXVlc3Rpb246IGluIG9ubGluZSBnYW1lcywgcGxheWVycyB1c3Vh
bGx5IHRhbGsNCj4+ID4+Pj4+Pj4+PiBhYm91dCB0aGUgInBpbmciLCBhbmQgSSB0aGluayBpdCBt
ZWFucyBSVFQuIERvbid0IHlvdSB0aGluayBpdA0KPj4gPj4+Pj4+Pj4+IHdvdWxkIGJlIGJldHRl
ciB0byBkZWZpbmUgYSBSVFQgbGltaXQgaW5zdGVhZCBvZiBhIE9XRCBvbmUgaW4NCj4+ID4+Pj4+
Pj4+PiB0aGF0DQo+PiA+Pj4+Pj4gY2FzZT8NCj4+ID4+Pj4+Pj4+Pg0KPj4gPj4+Pj4+Pj4+IFdo
YXQgZG8geW91IHRoaW5rPw0KPj4gPj4+Pj4+Pj4+DQo+PiA+Pj4+Pj4+Pj4gSm9zZQ0KPj4gPj4+
Pj4+Pj4+DQo+PiA+Pj4+Pj4+Pj4+IC0tLS0tTWVuc2FqZSBvcmlnaW5hbC0tLS0tDQo+PiA+Pj4+
Pj4+Pj4+IERlOiB0Y210Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86dGNtdGYtYm91bmNlc0Bp
ZXRmLm9yZ10NCj4+IEVuDQo+PiA+Pj4+Pj4+Pj4+IG5vbWJyZSBkZSBEYW4gV2luZyBFbnZpYWRv
IGVsOiBqdWV2ZXMsIDEzIGRlIGRpY2llbWJyZSBkZQ0KPj4gPj4+Pj4+Pj4+PiAyMDEyDQo+PiA+
Pj4+Pj4+Pj4+IDE3OjA3DQo+PiA+Pj4+Pj4+Pj4+IFBhcmE6ICdNaXJrbyBTdcW+bmpldmnEhyc7
IHRjbXRmQGlldGYub3JnDQo+PiA+Pj4+Pj4+Pj4+IEFzdW50bzogUmU6IFt0Y210Zl0gRHJhZnQ6
IE1heGltdW0gVG9sZXJhYmxlIERlbGF5cyB3aGVuDQo+PiA+Pj4+Pj4+Pj4+IHVzaW5nIFR1bm5l
bGluZyBDb21wcmVzc2VkIE11bHRpcGxleGVkIFRyYWZmaWMgRmxvd3MNCj4+ID4+Pj4+Pj4+Pj4N
Cj4+ID4+Pj4+Pj4+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiA+Pj4+Pj4+Pj4+
PiBGcm9tOiB0Y210Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86dGNtdGYtDQo+PiBib3VuY2Vz
QGlldGYub3JnXQ0KPj4gPj4+Pj4+Pj4+Pj4gT24gQmVoYWxmIE9mIE1pcmtvIFN1xb5uamV2aWMN
Cj4+ID4+Pj4+Pj4+Pj4+IFNlbnQ6IFRodXJzZGF5LCBEZWNlbWJlciAxMywgMjAxMiAxOjA3IEFN
DQo+PiA+Pj4+Pj4+Pj4+PiBUbzogdGNtdGZAaWV0Zi5vcmc7IHRzdndnQGlldGYub3JnDQo+PiA+
Pj4+Pj4+Pj4+PiBTdWJqZWN0OiBbdGNtdGZdIERyYWZ0OiBNYXhpbXVtIFRvbGVyYWJsZSBEZWxh
eXMgd2hlbiB1c2luZw0KPj4gPj4+Pj4+Pj4+Pj4gVHVubmVsaW5nIENvbXByZXNzZWQgTXVsdGlw
bGV4ZWQgVHJhZmZpYyBGbG93cw0KPj4gPj4+Pj4+Pj4+Pj4NCj4+ID4+Pj4+Pj4+Pj4+IEhlbGxv
LA0KPj4gPj4+Pj4+Pj4+Pj4NCj4+ID4+Pj4+Pj4+Pj4+DQo+PiA+Pj4+Pj4+Pj4+Pg0KPj4gPj4+
Pj4+Pj4+Pj4gV2UgaGF2ZSBqdXN0IHN1Ym1pdHRlZCB0aGUgZHJhZnQgbmFtZWQgTWF4aW11bSBU
b2xlcmFibGUNCj4+ID4+Pj4+Pj4+Pj4+IERlbGF5cyB3aGVuIHVzaW5nIFR1bm5lbGluZyBDb21w
cmVzc2VkIE11bHRpcGxleGVkIFRyYWZmaWMNCj4+ID4+Pj4gRmxvd3M6DQo+PiA+Pj4+Pj4+Pj4+
PiBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXN1em5qZXZpYy10c3Z3Zy1t
dGQNCj4+ID4+Pj4+Pj4+Pj4+IC10Yw0KPj4gPj4+Pj4+Pj4+Pj4gbXRmDQo+PiA+Pj4+Pj4+Pj4+
PiAvDQo+PiA+Pj4+Pj4+Pj4+DQo+PiA+Pj4+Pj4+Pj4+IFRoZSBzdWdnZXN0ZWQgNDAwbXMgZm9y
IGludGVyYWN0aXZlIHZvaWNlIGlzIGF0IGxlYXN0IDJ4IHRvbw0KPj4gPj4+Pj4+IGhpZ2guDQo+
PiA+Pj4+Pj4+Pj4+IEkNCj4+ID4+Pj4+Pj4+PiBleHBlY3QNCj4+ID4+Pj4+Pj4+Pj4gdGhhdCBu
dW1iZXIgZG9lcyBub3QgaW5jbHVkZSB0aGUgcGxheW91dCBqaXR0ZXIgYnVmZmVyICh3aGljaA0K
Pj4gPj4+Pj4+Pj4+PiBpcyB2YXJpYWJsZSwNCj4+ID4+Pj4+Pj4+PiBidXQNCj4+ID4+Pj4+Pj4+
Pj4gdXN1YWxseSBhIGZldyBzYW1wbGVzLCBzbyA0MC04MG1zKS4gIDIwMG1zIGVuZC10by1lbmQg
aXMgdGhlDQo+PiA+Pj4+Pj4+Pj4+IGhpZ2hlciBlbmQsDQo+PiA+Pj4+Pj4+Pj4gYW5kDQo+PiA+
Pj4+Pj4+Pj4+IHRoYXQgaW5jbHVkZXMgaml0dGVyIGJ1ZmZlciwgY29kZWMgcHJvY2Vzc2luZywg
YW5kIHNvIG9uLg0KPj4gPj4+Pj4+Pj4+Pg0KPj4gPj4+Pj4+Pj4+PiBCdXQsIG1vcmUgaW1wb3J0
YW50bHk6ICBpdCBzZWVtcyB2YWx1YWJsZSBmb3IgZW5kcG9pbnRzIHRvDQo+PiA+Pj4+Pj4+Pj4+
IHNpZ25hbCB0aGVpciBtYXhpbXVtIGRlbGF5IHNvbWVob3cuICBPciB3b3VsZCB0aGUgVENNVEYN
Cj4+ID4+Pj4+Pj4+Pj4gZnVuY3Rpb24NCj4+ID4+Pj4+Pj4+IGRldGVybWluZQ0KPj4gPj4+Pj4+
Pj4+PiB0aGUgbWF4aW11bSBkZWxheSwgdXNpbmcgc29tZSBoZXVyaXN0aWM/DQo+PiA+Pj4+Pj4+
Pj4+DQo+PiA+Pj4+Pj4+Pj4+IEhvdyBkb2VzIHRoZSBUQ01URiBmdW5jdGlvbiBkZXRlcm1pbmUg
aG93IG11Y2ggb2YgdGhhdA0KPj4gPj4+Pj4+Pj4+PiAndG9sZXJhYmxlIGxhdGVuY3knIGJ1ZGdl
dCBpdCBjYW4gY29uc3VtZT8NCj4+ID4+Pj4+Pj4+Pj4NCj4+ID4+Pj4+Pj4+Pj4gLWQNCj4+ID4+
Pj4+Pj4+Pj4NCj4+ID4+Pj4+Pj4+Pj4NCj4+ID4+Pj4+Pj4+Pj4+IEl0IGlzIGFuIGV4dGVuc2lv
biBvZiB0Y210Zg0KPj4gPj4+Pj4+Pj4+Pj4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2Rv
Yy9kcmFmdC0NCj4+ID4+Pj4+Pj4+Pj4+IHNhbGRhbmEtdHN2d2ctdGNtdGYvLiBTaW5jZSBhIHNw
ZWNpZmljIGxpc3QgZm9yIHRjbXRmIGV4aXN0cw0KPj4gPj4+Pj4+Pj4+Pj4gKHRjbXRmQGlldGYu
b3JnKSwgdGhlIGlkZWEgaXMgdG8gZGlzY3VzcyBpdCB0aGVyZS4NCj4+ID4+Pj4+Pj4+Pj4+DQo+
PiA+Pj4+Pj4+Pj4+Pg0KPj4gPj4+Pj4+Pj4+Pj4NCj4+ID4+Pj4+Pj4+Pj4+IFRoZSBkcmFmdCBj
b250YWlucyByZWNvbW1lbmRhdGlvbnMgZm9yIFRDTVRGIG11bHRpcGxleGluZw0KPj4gPj4+Pj4+
Pj4+Pj4gcGVyaW9kIGZvciBkaWZmZXJlbnQgcmVhbC10aW1lIHNlcnZpY2VzLiBJbiBvcmRlciB0
byBwcmV2ZW50DQo+PiA+Pj4+Pj4+Pj4+PiBRb0UgZGVncmFkYXRpb24gb2YgcmVhbC10aW1lIHNl
cnZpY2VzIHVzaW5nIFRDTVRGLCBhIHBvbGljeQ0KPj4gPj4+Pj4+Pj4+Pj4gZGVmaW5pbmcgYSBt
dWx0aXBsZXhpbmcgcGVyaW9kIGNhbiBiZSBlbXBsb3llZC4gVmFsdWVzIG9mDQo+PiA+Pj4+Pj4+
Pj4+PiBtYXhpbXVtIHRvbGVyYWJsZSBkZWxheXMgcHJlc2VudGVkIGluDQo+PiA+Pj4+Pj4+Pj4+
IHRoZQ0KPj4gPj4+Pj4+Pj4+Pj4gZHJhZnQgZm9ybSB0aGUgYmFzZSBvZiBzdWNoIHBvbGljeS4g
ICAgVGhlIHJlY29tbWVuZGF0aW9ucw0KPj4gPj4+PiBhcmUNCj4+ID4+Pj4+Pj4+PiBwcmVzZW50
ZWQNCj4+ID4+Pj4+Pj4+Pj4+IGZvciByZWFsLXRpbWUgbmV0d29yayBzZXJ2aWNlcyBpbiB3aGlj
aCBUQ1RNRiBiYW5kd2lkdGgNCj4+ID4+Pj4+Pj4+Pj4+IG9wdGltaXphdGlvbiBpcyBhcHBsaWNh
YmxlIChpLmUuLCBzZXJ2aWNlcyAgd2hpY2ggaGF2ZSBsb3cNCj4+ID4+Pj4+Pj4+Pj4+IHBheWxv
YWQgdG8gaGVhZGVyIHNpemUgcmF0aW8gd2hpY2ggcmVzdWx0cyBpbiBoaWdoIHByb3RvY29sDQo+
PiA+Pj4+Pj4gb3ZlcmhlYWQpLg0KPj4gPj4+Pj4+Pj4+Pj4NCj4+ID4+Pj4+Pj4+Pj4+DQo+PiA+
Pj4+Pj4+Pj4+Pg0KPj4gPj4+Pj4+Pj4+Pj4gWW91ciBmZWVkYmFjayB3aWxsIGJlIHdlbGNvbWUu
IFRoYW5rIHlvdS4NCj4+ID4+Pj4+Pj4+Pj4+DQo+PiA+Pj4+Pj4+Pj4+Pg0KPj4gPj4+Pj4+Pj4+
Pj4gU2luY2VyZWx5LA0KPj4gPj4+Pj4+Pj4+Pj4NCj4+ID4+Pj4+Pj4+Pj4+IE1pcmtvIFN1em5q
ZXZpYw0KPj4gPj4+Pj4+Pj4+Pg0KPj4gPj4+Pj4+Pj4+Pg0KPj4gPj4+Pj4+Pj4+PiBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4gPj4+Pj4+Pj4+PiB0
Y210ZiBtYWlsaW5nIGxpc3QNCj4+ID4+Pj4+Pj4+Pj4gdGNtdGZAaWV0Zi5vcmcNCj4+ID4+Pj4+
Pj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90Y210Zg0KPj4gPj4+
Pj4+Pj4NCj4+ID4+Pj4+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+PiA+Pj4+Pj4+PiB0Y210ZiBtYWlsaW5nIGxpc3QNCj4+ID4+Pj4+Pj4+IHRj
bXRmQGlldGYub3JnDQo+PiA+Pj4+Pj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3RjbXRmDQo+PiA+Pj4+Pj4+DQo+PiA+Pj4+Pj4+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiA+Pj4+Pj4+IHRjbXRmIG1haWxpbmcgbGlz
dA0KPj4gPj4+Pj4+PiB0Y210ZkBpZXRmLm9yZw0KPj4gPj4+Pj4+PiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQo+PiA+Pj4+Pj4NCj4+ID4+Pj4+Pg0KPj4gPj4+
Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiA+Pj4+Pj4NCj4+ID4+Pj4+
PiBFc3RlIG1lbnNhamUgc2UgZGlyaWdlIGV4Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRhcmlv
LiBQdWVkZQ0KPj4gPj4+Pj4+IGNvbnN1bHRhciBudWVzdHJhIHBvbMOtdGljYSBkZSBlbnbDrW8g
eSByZWNlcGNpw7NuIGRlIGNvcnJlbw0KPj4gPj4+Pj4+IGVsZWN0csOzbmljbyBlbiBlbCBlbmxh
Y2Ugc2l0dWFkbyBtw6FzIGFiYWpvLg0KPj4gPj4+Pj4+IFRoaXMgbWVzc2FnZSBpcyBpbnRlbmRl
ZCBleGNsdXNpdmVseSBmb3IgaXRzIGFkZHJlc3NlZS4gV2Ugb25seQ0KPj4gPj4+Pj4+IHNlbmQg
YW5kIHJlY2VpdmUgZW1haWwgb24gdGhlIGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQgb3V0IGF0Og0K
Pj4gPj4+Pj4+IGh0dHA6Ly93d3cudGlkLmVzL0VTL1BBR0lOQVMvZGlzY2xhaW1lci5hc3B4DQo+
PiA+Pj4+Pg0KPj4gPj4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4+ID4+Pj4+IHRjbXRmIG1haWxpbmcgbGlzdA0KPj4gPj4+Pj4gdGNtdGZAaWV0
Zi5vcmcNCj4+ID4+Pj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNt
dGYNCj4+ID4+Pj4NCj4+ID4+Pj4NCj4+ID4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4+ID4+Pj4NCj4+ID4+Pj4gRXN0ZSBtZW5zYWplIHNlIGRpcmlnZSBleGNsdXNpdmFt
ZW50ZSBhIHN1IGRlc3RpbmF0YXJpby4gUHVlZGUNCj4+ID4+Pj4gY29uc3VsdGFyIG51ZXN0cmEg
cG9sw610aWNhIGRlIGVudsOtbyB5IHJlY2VwY2nDs24gZGUgY29ycmVvDQo+PiA+Pj4+IGVsZWN0
csOzbmljbyBlbiBlbCBlbmxhY2Ugc2l0dWFkbyBtw6FzIGFiYWpvLg0KPj4gPj4+PiBUaGlzIG1l
c3NhZ2UgaXMgaW50ZW5kZWQgZXhjbHVzaXZlbHkgZm9yIGl0cyBhZGRyZXNzZWUuIFdlIG9ubHkN
Cj4+ID4+Pj4gc2VuZCBhbmQgcmVjZWl2ZSBlbWFpbCBvbiB0aGUgYmFzaXMgb2YgdGhlIHRlcm1z
IHNldCBvdXQgYXQ6DQo+PiA+Pj4+IGh0dHA6Ly93d3cudGlkLmVzL0VTL1BBR0lOQVMvZGlzY2xh
aW1lci5hc3B4DQo+PiA+Pj4NCj4+ID4+DQo+PiA+Pg0KPj4gPj4gX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCj4+ID4+DQo+PiA+PiBFc3RlIG1lbnNhamUgc2UgZGlyaWdlIGV4Y2x1
c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRhcmlvLiBQdWVkZQ0KPj4gPj4gY29uc3VsdGFyIG51ZXN0
cmEgcG9sw610aWNhIGRlIGVudsOtbyB5IHJlY2VwY2nDs24gZGUgY29ycmVvIGVsZWN0csOzbmlj
bw0KPj4gPj4gZW4gZWwgZW5sYWNlIHNpdHVhZG8gbcOhcyBhYmFqby4NCj4+ID4+IFRoaXMgbWVz
c2FnZSBpcyBpbnRlbmRlZCBleGNsdXNpdmVseSBmb3IgaXRzIGFkZHJlc3NlZS4gV2Ugb25seSBz
ZW5kDQo+PiA+PiBhbmQgcmVjZWl2ZSBlbWFpbCBvbiB0aGUgYmFzaXMgb2YgdGhlIHRlcm1zIHNl
dCBvdXQgYXQ6DQo+PiA+PiBodHRwOi8vd3d3LnRpZC5lcy9FUy9QQUdJTkFTL2Rpc2NsYWltZXIu
YXNweA0KPj4gPg0KPj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KPj4gPiB0Y210ZiBtYWlsaW5nIGxpc3QNCj4+ID4gdGNtdGZAaWV0Zi5vcmcNCj4+
ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby90Y210Zg0KPj4gPg0KPj4N
Cj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiB0
Y210ZiBtYWlsaW5nIGxpc3QNCj4+IHRjbXRmQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQo+DQo+X19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCj50Y210ZiBtYWlsaW5nIGxpc3QNCj50Y210ZkBpZXRm
Lm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCg0KDQpf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQpFc3RlIG1lbnNhamUgc2UgZGlyaWdl
IGV4Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRhcmlvLiBQdWVkZSBjb25zdWx0YXIgbnVlc3Ry
YSBwb2zDrXRpY2EgZGUgZW52w61vIHkgcmVjZXBjacOzbiBkZSBjb3JyZW8gZWxlY3Ryw7NuaWNv
IGVuIGVsIGVubGFjZSBzaXR1YWRvIG3DoXMgYWJham8uDQpUaGlzIG1lc3NhZ2UgaXMgaW50ZW5k
ZWQgZXhjbHVzaXZlbHkgZm9yIGl0cyBhZGRyZXNzZWUuIFdlIG9ubHkgc2VuZCBhbmQgcmVjZWl2
ZSBlbWFpbCBvbiB0aGUgYmFzaXMgb2YgdGhlIHRlcm1zIHNldCBvdXQgYXQ6DQpodHRwOi8vd3d3
LnRpZC5lcy9FUy9QQUdJTkFTL2Rpc2NsYWltZXIuYXNweA0K

From gorry@erg.abdn.ac.uk  Mon Jan 21 06:40:19 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A93AA21F848B for <tcmtf@ietfa.amsl.com>; Mon, 21 Jan 2013 06:40:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, 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 e7sKNuEsZ1q4 for <tcmtf@ietfa.amsl.com>; Mon, 21 Jan 2013 06:40:15 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id AEBCB21F8479 for <tcmtf@ietf.org>; Mon, 21 Jan 2013 06:40:14 -0800 (PST)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id ED3AE2B4400; Mon, 21 Jan 2013 14:40:13 +0000 (GMT)
Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 26F052B41E7; Mon, 21 Jan 2013 14:40:08 +0000 (GMT)
Message-ID: <50FD5347.5000106@erg.abdn.ac.uk>
Date: Mon, 21 Jan 2013 14:40:07 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: jsaldana@unizar.es
References: <009701cdf4ac$8af49750$a0ddc5f0$@unizar.es>	<F5EDC35DF914C1428C28E149F10463A2689D3F12@EX10-MB2-MAD.hi.inet>	<009f01cdf4b9$aca39060$05eab120$@unizar.es> <50F92318.30809@erg.abdn.ac.uk> <003601cdf7db$d652edf0$82f8c9d0$@unizar.es>
In-Reply-To: <003601cdf7db$d652edf0$82f8c9d0$@unizar.es>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jan 2013 14:40:19 -0000

Jose, see below.

Gorry

On 21/01/2013 13:33, Jose Saldana wrote:
> Gorry,
>
> Regarding your question:
>> RTT and/or control feedback would be really helpful in establishing a
>> congestion control or circuit-breaker function to ensure the traffic does not
>> cause congestion collapse. Have you thought about this?
>
> If I understand well, you are talking about using RTT or feedback not only for selecting an adequate multiplexing period, but also for congestion control. Is this true?
>
My query was whether the MUX should implement some rate limit on the 
aggregate multiplexed flow - given this can then result in a higher rate 
flow with different characteristics to the original low-rate flows.

> The question is that TCMTF is designed for traffic saving, so I think the cause of the congestion would not be TCMTF itself, but a high amount of flows, or a high bandwidth to aggregate. So perhaps in that case the flows which are being multiplexed will have their own end-to-end congestion control mechanisms.
>
OK, if all the flows had CC, this would be less of an issue. If each 
flow is individually small without CC (or unlimited by CC, e.g. because 
it sends fewer than one packet per RTT), then aggregating these could 
make a large flow that has little CC. That seems more of an in issue 
than having lots of small flows. The aggregate flow would likely be more 
bursty for instance.

> An example: you are grouping a lot of TCP flows of an MMORPG game. If a bottleneck appears and delays rise, TCP mechanisms will act and reduce the rate.
>
Yes. Especially if the flow has appreciable packets/rtt.

> Can we find an example in which interrupting the use of TCMTF and sending native packets instead will be necessary?
 > Perhaps this one: if you are using TCMTF for reducing pps and not 
bandwidth.
> This can happen with VoIP in a satellite network: you group packets without header compression.
 > You reduce pps and you increase bandwidth.
 >
I would suggest this is a subnetwork problem, not general Internet 
problem - it seems like a form of link encapauslation/HC optimisation.

> However, I think bandwidth increase is really small: 25 bytes for the tunnel header and two more bytes for separating each multiplexed packet.
 > If you are grouping 10 VoIP packets (20 IP/8 UDP/12 RTP/20 payload), 
the tunnel needs 25 + 10x(2+60)=645bytes.
 > > Native traffic would need 10x60=600 bytes. So bandwidth increase is 
7.5%. If you group 20 packets, bandwidth increase is 1265/1200= 5%
>
I think the extra byte overhead is not significant. Tunnel encpas in the 
CORE is common, using GRE, etc and adds more overhead.


> Gorry, was this your idea? Are you thinking about other scenarios in which interrupting TCMTF can be interesting?
>
I'm interested to judging if there are cases where aggregating small 
flows (with minimal or no CC - as in VoIP) can result in an aggregate 
tunnel that competes unfairly with established flows that use CC.

> Thanks a lot,
>
> Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Gorry Fairhurst
>> Enviado el: viernes, 18 de enero de 2013 11:25
>> Para: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling
>> Compressed Multiplexed Traffic Flows
>>
>> If this is going to be used in the general Internet, then we need to decide
>> whether there is one-way or two-way control connectivity. This will
>> determine the constraints from a congestion control perspective.
>> RTT and/or control feedback would be really helpful in establishing a
>> congestion control or circuit-breaker function to ensure the traffic does not
>> cause congestion collapse. Have you thought about this?
>>
>> Gorry
>>
>>
>>
>> On 17/01/2013 13:50, Jose Saldana wrote:
>>> In addition, perhaps we are too focused on online games and VoIP
>> services. There are other services which are one-way: perhaps M2M
>> communications do not require a two way communication. We can think
>> about a number of sensors sending their measurements to a central server.
>> So perhaps RTT will not even exist in this case.
>>>
>>> Jose
>>>
>>>> -----Mensaje original-----
>>>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es] Enviado el: jueves,
>>>> 17 de enero de 2013 14:39
>>>> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko SuÅ¾njeviÄ‡'; 'JuliÃ¡n
>>>> FernÃ¡ndez Navajas'
>>>> CC: tcmtf@ietf.org
>>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
>>>> Tunneling Compressed Multiplexed Traffic Flows
>>>>
>>>> Jose,
>>>>
>>>>           LetÂ´s say that playing with the OWD you have more
>>>> granularity in order to know in which direction you need to reduce
>>>> the delay by reducing the multiplexing delay. But people with more
>>>> knowledge about online games will provide us more information for sure.
>>>>
>>>> Regards,
>>>>
>>>> Fernando Pascual Blanco
>>>> TelefÃ³nica Global Resources
>>>> Network Automation and Dynamization
>>>> TECHNOLOGY PEOPLE GROUP
>>>> F +34913128779
>>>> M +34682005168
>>>> fpb@tid.es
>>>>
>>>>
>>>>
>>>>
>>>> On 17/01/13 13:16, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>>>
>>>>> Fernando,
>>>>>
>>>>> So you may have this case:
>>>>> - your multiplexing delay limit is 50 ms
>>>>> - you have a lot of flows to multiplex, so perhaps the time between
>>>>> multiplexed packets will be 5 ms
>>>>> - you detect an increase in RTT
>>>>> - the system reacts and reduces multiplexing period
>>>>> - in fact, the reduction doesn't matter until the period is reduced
>>>>> to less than 5 ms
>>>>>
>>>>> So you only have to make this decision: using tcmtf with 5 ms period
>>>>> or not. If RTT is critical you may not be interested on saving
>>>>> bandwidth, but on reducing a bit the RTT.
>>>>>
>>>>> So I think your question is: what happens if the RTT is very big
>>>>> (out of
>>>>> limits) and you can save bandwidth using a 5ms multiplexing period?
>>>>>
>>>>> For example, the maximum RTT for a good quality is 80 ms and your
>>>>> network has 120 just now. In this case, perhaps having 125 doesn't
>>>>> matter, if you can save bandwidth.
>>>>>
>>>>> This makes sense, but it is a "extreme" case. However, would it be
>>>>> any advantage if OWD is used instead of RTT?
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Jose
>>>>>
>>>>>> -----Mensaje original-----
>>>>>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]  Enviado el:
>>>>>> miÃ©rcoles, 16 de enero de 2013 12:52
>>>>>> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko SuÅ¾njeviÄ‡'; 'JuliÃ¡n
>>>>>> FernÃ¡ndez  Navajas'
>>>>>> CC: tcmtf@ietf.org
>>>>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
>>>>>> Tunneling  Compressed Multiplexed Traffic Flows
>>>>>>
>>>>>> Hi Jose,
>>>>>>
>>>>>>           You are right, but my point here is:
>>>>>>
>>>>>>                   Client - Mux - Demux - Server
>>>>>>
>>>>>>           Imagine that there is enough packets between mux and demux
>>>>>> to make  the added delay very small (TCMTF is working very well and
>>>>>> the mux has not  to wait the multiplexing period to fulfill a big
>>>>>> packet and send it, so imagine a  multiplexing period of 50 ms and
>>>>>> a big packet is fulfilled in 5 ms). If the RTT  get increased
>>>>>> because a congestion in the way back to the client (there is no
>>>>>> TCMTF
>>>>>> optimization) and we decrease the multiplexing period (even in the
>>>>>> extreme we can disable the TCMTF optimization) the high RTT will
>> remain.
>>>>>> Even if the TCMTF optimization was helping in the client to server
>>>>>> path,  disabling it may harm. Do you think that scenario would be
>> possible?
>>>>>>
>>>>>>           So IÂ´m not sure about that, I think we need more opinions here.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Fernando Pascual Blanco
>>>>>> TelefÃ³nica Global Resources
>>>>>> Network Automation and Dynamization TECHNOLOGY PEOPLE GROUP
>> F
>>>>>> +34913128779 M +34682005168 fpb@tid.es
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 16/01/13 11:57, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>>>>>
>>>>>>> My two cents:
>>>>>>>
>>>>>>> In games and in VoIP the really important thing is RTT:
>>>>>>>
>>>>>>> - Games always measure the RTT (gamers talk about the "ping"): the
>>>>>>> important thing is the delay from a player action to the server
>>>>>>> reaction arriving to the player's machine.
>>>>>>> - In VoIP I think it is the same: what matters is the RTT, in
>>>>>>> order to grant interactivity and avoiding cross-talk.
>>>>>>>
>>>>>>> In addition, RTT is easier to measure than OWD, since you don't
>>>>>>> need synchronization.
>>>>>>>
>>>>>>> And regarding Two-way TCMTF, I think we have to think about TCMTF
>>>>>>> as one-way. Otherwise, things would become very complicated.
>> Some
>>>>>> services
>>>>>>> have very different client-server and server-client traffic
>>>>>>> patterns (e.g. games). In addition, sometimes the two flows can
>>>>>>> follow different network paths. I think once we talked about a
>>>>>>> network provider using a number of ISPs.
>>>>>>>
>>>>>>> However, using RTT for tuning a one-way TCMTF may not be bad... or
>>>>>>> is it bad? Any other thoughts?
>>>>>>>
>>>>>>> BR,
>>>>>>>
>>>>>>> Jose
>>>>>>>
>>>>>>>> -----Mensaje original-----
>>>>>>>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]  Enviado el:
>>>>>> martes,
>>>>>>>> 15 de enero de 2013 18:04
>>>>>>>> Para: jsaldana@unizar.es; 'Dan Wing'; 'Mirko SuÅ¾njeviÄ‡'; JuliÃ¡n
>>>>>>>> FernÃ¡ndez  Navajas
>>>>>>>> CC: tcmtf@ietf.org
>>>>>>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
>>>>>>>> Tunneling  Compressed Multiplexed Traffic Flows
>>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>>           To re-open that issue, I would suggest that given that
>>>>>>>> the delay is so  sensitive in real time services, we need to find
>>>>>>>> a consensus here.
>>>>>>>>
>>>>>>>>           My opinion is that to apply the first possibility (the
>>>>>>>> static multiplexing
>>>>>>>> period) we need to suppose that the network conditions are really
>>>>>>>> bad, to be  protected when the network congestion arises. In that
>>>>>>>> case, the application  of the TCMTF optimization will not be
>>>>>>>> optimal, so that would be the less  preferred option, but easier
>>>>>>>> to implement and maintain over the time.
>>>>>>>>
>>>>>>>>           On the other hand, the second possibility would be the
>>>>>>>> preferred. It is  easy to know the delay between the mux and the
>>>>>>>> demux but most of the  times will not be enough unless mux and
>>>>>>>> demux were really near from the  client and the server
>>>>>>>> respectively. I agree with Jose in the possibility of snoop  RTCP
>>>>>>>> packets in order to adapt the multiplexing period when
>>>>>>>> multiplexing RTP packets (and RTCP is available). Talking about
>>>>>>>> RTT, IÂ´m not sure if RTT  would be useful given that the
>>>>>>>> multiplexing period only affect the one way  delay (OWD). Imagine
>> the following scenario:
>>>>>>>>           - Client - Mux/Demux - Demux/Mux - Server (two ways
>>>>>>>> TCMTF, TWTCMTF :P)
>>>>>>>>           - The OWD from server to client get increased
>>>>>>>>           - The OWD from client to server remains equal
>>>>>>>>           - Should we use a lower multiplexing period in the
>>>>>>>> client to server  direction? I donÂ´t think soâ€¦ because we should
>>>>>>>> use a lower multiplexing  period in the other direction.
>>>>>>>>
>>>>>>>>           My point is that the multiplexing period should only be
>>>>>>>> affected by the  OWD and not by the RTT (or it may be application
>>>>>>>> dependent). How to  calculate the OWD? IÂ´ve been reading
>>>>>>>> something about OWAMP and it  seems that an specific software has
>>>>>>>> to be implemented in the client/server  side.
>>>>>>>> Can we assume that? Unfortunately I cannot contribute so much
>>>> hereâ€¦
>>>>>>>>           It is possible that for certain services the static (and
>>>>>>>> worst
>>>>>>>> case)
>>>>>>>> multiplexing period would be the better solution.
>>>>>>>>
>>>>>>>>           What do you think?
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Fernando Pascual Blanco
>>>>>>>> TelefÃ³nica Global Resources
>>>>>>>> Network Automation and Dynamization TECHNOLOGY PEOPLE
>> GROUP
>>>> F
>>>>>>>> +34913128779 M +34682005168 fpb@tid.es
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 17/12/12 12:25, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> Julian and I have been discussing about this. Some ideas have
>>>>>> arisen.
>>>>>>>>> This is the summary.
>>>>>>>>>
>>>>>>>>> This would be the scheme of the system, including mux and
>> demux:
>>>>>>>>>
>>>>>>>>> Real-time application ------- mux -------- internet ---------
>>>>>>>>> demux
>>>>>>>>> -------
>>>>>>>>> server
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I think perhaps the draft could say something like:
>>>>>>>>>
>>>>>>>>> When setting the multiplexing period, there are two possibilities:
>>>>>>>>>
>>>>>>>>> 1.- Static / permanent: At system setup time, network delays are
>>>>>>>>> measured, and a multiplexing period is selected and set in the
>>>>>>>> multiplexer.
>>>>>>>>>
>>>>>>>>> 2.- Dynamic: A mechanism is used so as to adapt to the evolution
>>>>>>>>> of network delays. In this case, different mechanisms can be
>>>>>>>>> used in order to obtain periodical end-to-end network delay
>>>>>>>>> estimations, which would be useful in order to set the
>>>>>>>>> multiplexing
>>>> period:
>>>>>>>>>
>>>>>>>>> - If the traffic is RTP, then RTCP packets containing the
>>>>>>>>> estimation could be analyzed in order to extract these values,
>>>>>>>>> as Dan
>>>> suggests.
>>>>>>>>> The question
>>>>>>>>> is: would that packets travel through the multiplexer?
>>>>>>>>> - If the traffic is TCP, perhaps something similar to the RTT
>>>>>>>>> estimation of TCP could be useful.
>>>>>>>>> - If the traffic is UDP, should the mux use something like OWAMP
>>>>>>>>> (http://tools.ietf.org/html/rfc4656) in order to calculate two
>>>>>>>>> delays (application to mux, and mux to server) and calculate the
>>>>>> sum?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I think the draft is only supposed to report the maximum delays
>>>>>>>>> normally considered acceptable. Perhaps the additional
>>>>>>>>> mechanisms for calculating the RTT could just be suggested.
>>>>>>>>>
>>>>>>>>> What do you think?
>>>>>>>>>
>>>>>>>>> Jose
>>>>>>>>>
>>>>>>>>>> -----Mensaje original-----
>>>>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>>>>>>>>>> nombre de Dan Wing Enviado el: viernes, 14 de diciembre de 2012
>>>>>>>>>> 18:33
>>>>>>>>>> Para: jsaldana@unizar.es; 'Mirko SuÅ¾njeviÄ‡'
>>>>>>>>>> CC: tcmtf@ietf.org
>>>>>>>>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when using
>>>>>>>>>> Tunneling Compressed Multiplexed Traffic Flows
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Jose Saldana [mailto:jsaldana@unizar.es]
>>>>>>>>>>> Sent: Friday, December 14, 2012 2:58 AM
>>>>>>>>>>> To: 'Dan Wing'; 'Mirko SuÅ¾njeviÄ‡'
>>>>>>>>>>> Cc: tcmtf@ietf.org
>>>>>>>>>>> Subject: RE: [tcmtf] Draft: Maximum Tolerable Delays when
>>>>>>>>>>> using Tunneling Compressed Multiplexed Traffic Flows
>>>>>>>>>>>
>>>>>>>>>>> Dan,
>>>>>>>>>>>
>>>>>>>>>>> Regarding the use of the maximum delay, some days ago we
>>>>>>>>>>> discussed about
>>>>>>>>>>> it:
>>>>>>>>>>> the actual OWD of the network should be measured (or
>>>>>>>>>>> estimated) in order to know the maximum multiplexing period
>> we
>>>> can set.
>>>>>>>>>>>
>>>>>>>>>>> We may have this formula, if thinking one-way:
>>>>>>>>>>>
>>>>>>>>>>> OWD  + Mux period/2  < tolerable_OWD
>>>>>>>>>>>
>>>>>>>>>>> If we think RTT:
>>>>>>>>>>>
>>>>>>>>>>> OWD + Mux period/2 + OWD back < 2*tolerable_OWD
>>>>>>>>>>>
>>>>>>>>>>> I don't know if we should include a mechanism for estimating
>>>>>>>>>>> OWD in tcmtf. I think this is more an implementation problem,
>>>>>>>>>>> which may be already solved.
>>>>>>>>>>
>>>>>>>>>> Yes, it's already solved end-to-end:  RTP with RTCP feedback
>>>>>>>>>> allows determining one way delay.
>>>>>>>>>>
>>>>>>>>>> But if something in the middle is multiplexing several packets
>>>>>>>>>> together,
>>>>>>>>> we
>>>>>>>>>> don't want it to add too much delay.  That thing in the middle
>>>>>>>>>> won't necessarily know the one way delay seen by the endpoints,
>>>>>>>>>> unless it analyzes the RTP and RTCP.  There are devices that do
>>>>>>>>>> that on the market,  mostly to diagnose where networks are
>>>>>>>>>> causing loss/delay with RTP flows.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Another option is using some typical values, e.g. from
>>>>>>>>>>>
>>>> http://ipnetwork.bgtmo.ip.att.net/pws/global_network_avgs.htm
>>>>>>>>>>> l
>>>>>>>>>>>
>>>>>>>>>>> The draft includes some preliminary/recommended values for
>> the
>>>>>>>>>>> Multiplexing Period. Is this interesting? Should we put the
>>>>>>>>>>> formula instead?
>>>>>>>>>>
>>>>>>>>>> It's probably sufficient as-is.
>>>>>>>>>>
>>>>>>>>>> -d
>>>>>>>>>>
>>>>>>>>>>> Mirko, another question: in online games, players usually talk
>>>>>>>>>>> about the "ping", and I think it means RTT. Don't you think it
>>>>>>>>>>> would be better to define a RTT limit instead of a OWD one in
>>>>>>>>>>> that
>>>>>>>> case?
>>>>>>>>>>>
>>>>>>>>>>> What do you think?
>>>>>>>>>>>
>>>>>>>>>>> Jose
>>>>>>>>>>>
>>>>>>>>>>>> -----Mensaje original-----
>>>>>>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org]
>> En
>>>>>>>>>>>> nombre de Dan Wing Enviado el: jueves, 13 de diciembre de
>>>>>>>>>>>> 2012
>>>>>>>>>>>> 17:07
>>>>>>>>>>>> Para: 'Mirko SuÅ¾njeviÄ‡'; tcmtf@ietf.org
>>>>>>>>>>>> Asunto: Re: [tcmtf] Draft: Maximum Tolerable Delays when
>>>>>>>>>>>> using Tunneling Compressed Multiplexed Traffic Flows
>>>>>>>>>>>>
>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-
>> bounces@ietf.org]
>>>>>>>>>>>>> On Behalf Of Mirko SuÅ¾njevic
>>>>>>>>>>>>> Sent: Thursday, December 13, 2012 1:07 AM
>>>>>>>>>>>>> To: tcmtf@ietf.org; tsvwg@ietf.org
>>>>>>>>>>>>> Subject: [tcmtf] Draft: Maximum Tolerable Delays when using
>>>>>>>>>>>>> Tunneling Compressed Multiplexed Traffic Flows
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hello,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> We have just submitted the draft named Maximum Tolerable
>>>>>>>>>>>>> Delays when using Tunneling Compressed Multiplexed Traffic
>>>>>> Flows:
>>>>>>>>>>>>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd
>>>>>>>>>>>>> -tc
>>>>>>>>>>>>> mtf
>>>>>>>>>>>>> /
>>>>>>>>>>>>
>>>>>>>>>>>> The suggested 400ms for interactive voice is at least 2x too
>>>>>>>> high.
>>>>>>>>>>>> I
>>>>>>>>>>> expect
>>>>>>>>>>>> that number does not include the playout jitter buffer (which
>>>>>>>>>>>> is variable,
>>>>>>>>>>> but
>>>>>>>>>>>> usually a few samples, so 40-80ms).  200ms end-to-end is the
>>>>>>>>>>>> higher end,
>>>>>>>>>>> and
>>>>>>>>>>>> that includes jitter buffer, codec processing, and so on.
>>>>>>>>>>>>
>>>>>>>>>>>> But, more importantly:  it seems valuable for endpoints to
>>>>>>>>>>>> signal their maximum delay somehow.  Or would the TCMTF
>>>>>>>>>>>> function
>>>>>>>>>> determine
>>>>>>>>>>>> the maximum delay, using some heuristic?
>>>>>>>>>>>>
>>>>>>>>>>>> How does the TCMTF function determine how much of that
>>>>>>>>>>>> 'tolerable latency' budget it can consume?
>>>>>>>>>>>>
>>>>>>>>>>>> -d
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> It is an extension of tcmtf
>>>>>>>>>>>>> http://datatracker.ietf.org/doc/draft-
>>>>>>>>>>>>> saldana-tsvwg-tcmtf/. Since a specific list for tcmtf exists
>>>>>>>>>>>>> (tcmtf@ietf.org), the idea is to discuss it there.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> The draft contains recommendations for TCMTF multiplexing
>>>>>>>>>>>>> period for different real-time services. In order to prevent
>>>>>>>>>>>>> QoE degradation of real-time services using TCMTF, a policy
>>>>>>>>>>>>> defining a multiplexing period can be employed. Values of
>>>>>>>>>>>>> maximum tolerable delays presented in
>>>>>>>>>>>> the
>>>>>>>>>>>>> draft form the base of such policy.    The recommendations
>>>>>> are
>>>>>>>>>>> presented
>>>>>>>>>>>>> for real-time network services in which TCTMF bandwidth
>>>>>>>>>>>>> optimization is applicable (i.e., services  which have low
>>>>>>>>>>>>> payload to header size ratio which results in high protocol
>>>>>>>> overhead).
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Your feedback will be welcome. Thank you.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Sincerely,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Mirko Suznjevic
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> 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 nuestra polÃ­tica de envÃ­o y recepciÃ³n de correo
>>>>>>>> electrÃ³nico en el enlace situado mÃ¡s abajo.
>>>>>>>> This message is intended exclusively for its addressee. We only
>>>>>>>> send and receive email on the basis of the terms set out at:
>>>>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> tcmtf mailing list
>>>>>>> tcmtf@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>>>>
>>>>>>
>>>>>> ________________________________
>>>>>>
>>>>>> 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
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>


From mperumal@cisco.com  Mon Jan 21 20:34:25 2013
Return-Path: <mperumal@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19E6E11E8097 for <tcmtf@ietfa.amsl.com>; Mon, 21 Jan 2013 20:34:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C8d51S+R+7aV for <tcmtf@ietfa.amsl.com>; Mon, 21 Jan 2013 20:34:18 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 17CC711E80A5 for <tcmtf@ietf.org>; Mon, 21 Jan 2013 20:34:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=50725; q=dns/txt; s=iport; t=1358829258; x=1360038858; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Fm5UdBbVrdesuaBSbv217pNBuVTn/JjHCrZgxKmu1N4=; b=LjW0S+dPPEjdrmjNnGc4Cs4dLfmvsY3qqAo54xu1M7219BzK6iRvvyu7 4B7liZXNJoSJNMbvVvFuxROSzHCxg/RxbBRM+3vS4W73fE0mfbkoc43Xu hmohtCXuKgIsiHKa6fhgh1ya91uMqS9e5D0M77tR2ZHVVXVdLmdRsBmOZ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnUFAH8V/lCtJV2c/2dsb2JhbABDgkipPokMAYkiFnOCHgEBAQICGhNMEAIBCBEBAgEBAQsWAQYHMhQDBggBAQQBDQUIE4d+DKxQjyaMfoNXYQOILIothE+PLYJoDYFvNQ
X-IronPort-AV: E=Sophos;i="4.84,511,1355097600";  d="scan'208,217";a="165907205"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP; 22 Jan 2013 04:34:16 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r0M4YGXl008685 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Jan 2013 04:34:16 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.64]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Mon, 21 Jan 2013 22:34:15 -0600
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: FERNANDO PASCUAL BLANCO <fpb@tid.es>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Thread-Topic: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a de-muxer
Thread-Index: Ac3z0qpuai7heI7oSHWY0AJDN9gmvgACrW2AAO2IJEAAFSw5AAAbQTuQ
Date: Tue, 22 Jan 2013 04:34:14 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE223FDBD73@xmb-rcd-x02.cisco.com>
References: <E721D8C6A2E1544DB2DEBC313AF54DE223FD8899@xmb-rcd-x02.cisco.com> <F5EDC35DF914C1428C28E149F10463A2689E2EA9@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A2689E2EA9@EX10-MB2-MAD.hi.inet>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.142.108.147]
Content-Type: multipart/alternative; boundary="_000_E721D8C6A2E1544DB2DEBC313AF54DE223FDBD73xmbrcdx02ciscoc_"
MIME-Version: 1.0
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a de-muxer
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, 22 Jan 2013 04:34:25 -0000

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

Hi Fernando,

Yes, I was referring to draft A. However, I am now thinking it might be bet=
ter if we devote draft A for the use cases and the protocol stack architect=
ure, and write a new draft A-sig describing the negotiation procedures incl=
uding automatic discovery/association and capability exchange. That way we =
can progress them independently in parallel and potentially explore multipl=
e negotiation procedures (in the form of multiple drafts, if there is suffi=
cient interest). In essence, I think we should separate out the use cases a=
nd architecture from the solutions.

|1. The way a mux is instructed with the IP address (for example) of a demu=
x.
|   That procedure could be:
|   1. Static (i.e. Configuration within the mux)
|   2. Dynamic (i.e. Instructed from a higher entity like a policy manager)
|      and could be (or not) described in draft C

On dynamic, I would also like to add mux discovering the demux through nego=
tiation -- this would be case when the mux sees a number of flows going to =
the same destination but doesn't know if the destination is capable of demu=
xing.

Muthu

From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
Sent: Monday, January 21, 2013 2:32 PM
To: Muthu Arul Mozhi Perumal (mperumal); jsaldana@unizar.es
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discov=
er a de-muxer

Hi Muthu,

I agree that a tunnel is not always needed. But when you say signaling doc,=
 are you referring finally to the draft A? We agreed on addressing capabili=
ties negotiation on that draft.

Nevertheless, I think we should clarify two thinks:

  1.  The way a mux is instructed with the IP address (for example) of a de=
mux. That procedure could be:

     *   Static (i.e. Configuration within the mux)
     *   Dynamic (i.e. Instructed from a higher entity like a policy manage=
r) and could be (or not) described in draft C

  1.  The capabilities negotiation: once a mux knows the IP address of a de=
mux can negotiate the capabilities of the different layers (tunnel, multipl=
ex and compression). This is also described at the draft A.
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: "'Muthu Arul Mozhi Perumal (mperumal) '" <mperumal@cisco.com<mailto:m=
perumal@cisco.com>>
Date: lunes, 21 de enero de 2013 06:40
To: Fernando Pascual Blanco <fpb@tid.es<mailto:fpb@tid.es>>, "jsaldana@uniz=
ar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.es<mailto:jsaldana@uniza=
r.es>>
Cc: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Subject: RE: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discov=
er a de-muxer

Hi Fernando,

|I=B4m sure we will find a consensus about that :).

Sure..

|What Muthu proposes sounds interesting to me but, to be honest, I think TC=
MTF
|establishing should be quite similar to the establishing procedures of tun=
nels
|defined in draft A (L2TP, GRE...),

I agree the procedures for establishing the association b/w the muxer and t=
he de-muxer could be similar to those of establishing a tunnel. However, I =
would like us to avoid two assumptions:
1. The other end of a tunnel is always TCMTF capable. I think this is more =
important when you already have a tunnel (say, IPSec tunnel) and would like=
 to perform TCMTF on the fly.
2. A tunnel is always needed for performing TCMTF. If we aren't doing any c=
ompression, but only multiplexing, the outermost IP header would be intact =
and should suffice for routing the packets. There are satellite networks wh=
ere reducing the packets per second (pps) for VoIP calls is more important =
-- they don't do any compression, but only multiplexing, and don't setup a =
tunnel as well. For e.g:
http://www.cisco.com/web/strategy/docs/gov/aag_c45-697642_v2.pdf
http://www.cisco.com/web/strategy/docs/gov/ip_multiplexing_agensler.pptx

Nevertheless, I think all this go into the signaling doc. If we require cap=
ability negotiation, I think we can combine it with the procedure for estab=
lishing the association b/w the muxer and the de-muxer. If we make capabili=
ty negotiation as optional, we might want to keep those as separate procedu=
res.

Muthu

From: tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-b=
ounces@ietf.org] On Behalf Of FERNANDO PASCUAL BLANCO
Sent: Wednesday, January 16, 2013 5:04 PM
To: jsaldana@unizar.es<mailto:jsaldana@unizar.es>; Muthu Arul Mozhi Perumal=
 (mperumal)
Cc: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discov=
er a de-muxer

Hi Jose, Muthu,

I=B4m sure we will find a consensus about that :). What Muthu proposes soun=
ds interesting to me but, to be honest, I think TCMTF establishing should b=
e quite similar to the establishing procedures of tunnels defined in draft =
A (L2TP, GRE...), actually at network level TCMTF is a tunnel. Once establi=
shed signaling will negotiate upper levels (multiplexing and HC) to perform=
 TCMTF (draft A).

What do you think?

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: mi=E9rcoles, 16 de enero de 2013 11:18
To: "'Muthu Arul Mozhi Perumal (mperumal) '" <mperumal@cisco.com<mailto:mpe=
rumal@cisco.com>>, 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: RV: [tcmtf] TCMTF: Document A: mechanism for a muxer to discover a=
 de-muxer


Fernando, Muthu, everyone,



Since there is no consensus about this, I think we should carry on with the=
 debate. Do you think the mechanism would be very complicated? Any new idea=
s?:



- *dynamically establishing, modifying and releasing tunnels*



#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.



There is still no consensus here:



Fernando: "Regarding #1, to be honest, I am not completely sure of the need=
 to specify a mechanism to discover muxes and demuxes between them. I think=
 those kind of mechanisms have more sense in local environments but I=B4m n=
ot sure if it applies here. At least at the beginning this associations can=
 be done manually."



Muthu: "I think it is the opposite -- in local environments you can provisi=
on/associate them manually. However, in a multi-vendor environment over the=
 Internet this should happen automatically."

"#1 needs to be specified."


Best regards,

Jose

De:tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-boun=
ces@ietf.org] En nombre de Jose Saldana
Enviado el: martes, 15 de enero de 2013 11:56
Para: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: [tcmtf] TCMTF: Document A discussion: content and charter

Document (A) refers to the main TCMTF draft, currently in http://datatracke=
r.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

1.- Content of the Document

Currently it contains the description of the question and the protocols whi=
ch could be used on each layer (tunneling, compressing, multiplexing). It s=
ays that the signaling issues would be that of each protocol.

There is consensus (I think) about this: we should include some signaling i=
ssues. The question is: What should we include in Draft A and what in Draft=
 C?

- *Auto-negotiation* Negotiation mechanisms to decide the options at each l=
ayer (compression, multiplexing and tunneling) between mux and demux. Perha=
ps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP and IPHC,=
 so the two machines will have to negotiate in order to decide which compre=
ssion protocol use.

This should be included in (A). I think there is consensus about this:
Juan Antonio: "The first kind of signaling ("auto-negotiation") is needed f=
rom the beginning if we don't want an extremely static protocol and therefo=
re possibly difficult to get it working, especially when in most of cases t=
he peers belong to different entities/companies."



Dan: "We need that -- it is capabilities negotiation.  It is needed because=
 the protocol will fail if one side mistakenly thinks the other side has ce=
rtain functionality, and because we will want to add some fancy new compres=
sion in the year 2020 and will need to negotiate it."



Fernando: "I also agree with the idea of including the mux-demux signaling =
within the draft A (as Dan said, they are capabilities negotiation). This d=
raft should be able to get two boxes with TCMTF fully working between them.=
 Under my point of view this includes the definition of the capabilities in=
 each node and the negotiation of that capabilities."



Does this mean that Document (A) will no longer be a Best Current Practice?=
 I think so.





- *dynamically establishing, modifying and releasing tunnels*



#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.



There is still no consensus here:



Fernando: "Regarding #1, to be honest, I am not completely sure of the need=
 to specify a mechanism to discover muxes and demuxes between them. I think=
 those kind of mechanisms have more sense in local environments but I=B4m n=
ot sure if it applies here. At least at the beginning this associations can=
 be done manually."



Muthu: "I think it is the opposite -- in local environments you can provisi=
on/associate them manually. However, in a multi-vendor environment over the=
 Internet this should happen automatically."

"#1 needs to be specified."







#2. A mechanism to *elect an optimal muxer and a de-muxer when there are mo=
re than one muxer/de-muxer for a flow*.



We agree: This can wait for Document (C).



                Fernando: "#2 is more related to the higher entity that has=
 to decide whether a flow should be TCMTFed or not, and under my point of v=
iew it can be addressed in a different draft."

                Muthu: "#2 can be added later."





3. A mechanism to *setup/release a tunnel b/w a muxer and a de-muxer*.



We agree: This has to be included in (A).



                Fernando "#3 I think should be included in the draft A, sin=
ce it is a mechanism within the TFMTF protocol itself."

                Muthu: "#3 many not require much specification."





2.- Should we include it in the Charter now?

Of course, Document (A) should be in the charter.


Best regards,

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

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	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:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
span.plaintextchar0
	{mso-style-name:plaintextchar;
	font-family:Consolas;}
span.textosinformatocar
	{mso-style-name:textosinformatocar;
	font-family:"Calibri","sans-serif";}
span.estilocorreo19
	{mso-style-name:estilocorreo19;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.estilocorreo20
	{mso-style-name:estilocorreo20;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.balloontextchar0
	{mso-style-name:balloontextchar;
	font-family:"Tahoma","sans-serif";}
span.emailstyle26
	{mso-style-name:emailstyle26;
	font-family:"Courier New";
	color:windowtext;}
span.EmailStyle29
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:778765105;
	mso-list-template-ids:-1609411884;}
@list l0:level1
	{mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hi Fernando,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Yes, I was referring to draft A. However, I am now thinkin=
g it might be better if we devote draft A for the use cases and the protoco=
l stack architecture, and write a new draft A-sig
 describing the negotiation procedures including automatic discovery/associ=
ation and capability exchange. That way we can progress them independently =
in parallel and potentially explore multiple negotiation procedures (in the=
 form of multiple drafts, if there
 is sufficient interest). In essence, I think we should separate out the us=
e cases and architecture from the solutions.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|1. The way a mux is instructed with the IP address (for e=
xample) of a demux.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|&nbsp; &nbsp;That procedure could be:
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|&nbsp;&nbsp; 1. Static (i.e. Configuration within the mux=
)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|&nbsp;&nbsp; 2. Dynamic (i.e. Instructed from a higher en=
tity like a policy manager)
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and could be (or not) desc=
ribed in draft C<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">On dynamic, I would also like to add mux discovering the d=
emux through negotiation -- this would be case when the mux sees a number o=
f flows going to the same destination but doesn't
 know if the destination is capable of demuxing.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Muthu<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> FERNANDO=
 PASCUAL BLANCO [mailto:fpb@tid.es]
<br>
<b>Sent:</b> Monday, January 21, 2013 2:32 PM<br>
<b>To:</b> Muthu Arul Mozhi Perumal (mperumal); jsaldana@unizar.es<br>
<b>Cc:</b> tcmtf@ietf.org<br>
<b>Subject:</b> Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to=
 discover a de-muxer<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Muth=
u,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I agree=
 that a tunnel is not always needed. But when you say signaling doc, are yo=
u referring finally to the draft A? We agreed on addressing capabilities ne=
gotiation on that draft.&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Neverth=
eless, I think we should clarify two thinks:<o:p></o:p></span></p>
</div>
<ol start=3D"1" type=3D"1">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style=3D"font-size:10.5pt">The way a mux is instructed with the IP ad=
dress (for example) of a demux. That procedure could be:
<o:p></o:p></span></li></ol>
<ol start=3D"1" type=3D"1">
<ol start=3D"1" type=3D"1">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<span style=3D"font-size:10.5pt">Static (i.e. Configuration within the mux)=
<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"color:black;mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<span style=3D"font-size:10.5pt">Dynamic (i.e. Instructed from a higher ent=
ity like a policy manager) and could be (or not) described in draft C<o:p><=
/o:p></span></li></ol>
</ol>
<ol start=3D"2" type=3D"1">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style=3D"font-size:10.5pt">The capabilities negotiation: once a mux k=
nows the IP address of a demux can negotiate the capabilities of the differ=
ent layers (tunnel, multiplex and compression). This is also described at t=
he draft A.<o:p></o:p></span></li></ol>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Regards=
,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Fernand=
o Pascual Blanco<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Telef=
=F3nica Global Resources<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Network=
 Automation and Dynamization<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">TECHNOL=
OGY PEOPLE GROUP<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">F &#43;=
34913128779<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">M &#43;=
34682005168<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><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>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;'Muthu Arul Mozhi Perumal (mperumal) '&quot; =
&lt;<a href=3D"mailto:mperumal@cisco.com">mperumal@cisco.com</a>&gt;<br>
<b>Date: </b>lunes, 21 de enero de 2013 06:40<br>
<b>To: </b>Fernando Pascual Blanco &lt;<a href=3D"mailto:fpb@tid.es">fpb@ti=
d.es</a>&gt;, &quot;<a href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.e=
s</a>&quot; &lt;<a href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a=
>&gt;<br>
<b>Cc: </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>RE: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to=
 discover a de-muxer<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Fernando,</span><span style=3D"color:black"=
><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">|I=B4m sure we will find a consensus about tha=
t :).</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Sure..</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">|What Muthu proposes sounds interesting to me =
but, to be honest, I think TCMTF
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">|establishing should be quite similar to the e=
stablishing procedures of tunnels
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">|defined in draft A (L2TP, GRE&#8230;),</span>=
<span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">I agree the procedures for establishing the as=
sociation b/w the muxer and the de-muxer could be similar to those of estab=
lishing a tunnel. However, I would like us to
 avoid two assumptions:</span><span style=3D"color:black"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">1. The other end of a tunnel is always TCMTF c=
apable. I think this is more important when you already have a tunnel (say,=
 IPSec tunnel) and would like to perform TCMTF
 on the fly.</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">2. A tunnel is always needed for performing TC=
MTF. If we aren't doing any compression, but only multiplexing, the outermo=
st IP header would be intact and should suffice
 for routing the packets. There are satellite networks where reducing the p=
ackets per second (pps) for VoIP calls is more important -- they don't do a=
ny compression, but only multiplexing, and don't setup a tunnel as well. Fo=
r e.g:</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><a href=3D"http://www.cisco.com/web/strategy/d=
ocs/gov/aag_c45-697642_v2.pdf">http://www.cisco.com/web/strategy/docs/gov/a=
ag_c45-697642_v2.pdf</a></span><span style=3D"color:black"><o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><a href=3D"http://www.cisco.com/web/strategy/d=
ocs/gov/ip_multiplexing_agensler.pptx">http://www.cisco.com/web/strategy/do=
cs/gov/ip_multiplexing_agensler.pptx</a></span><span style=3D"color:black">=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Nevertheless, I think all this go into the sig=
naling doc. If we require capability negotiation, I think we can combine it=
 with the procedure for establishing the association
 b/w the muxer and the de-muxer. If we make capability negotiation as optio=
nal, we might want to keep those as separate procedures.</span><span style=
=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Muthu</span><span style=3D"color:black"><o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:black">From:</span></b><span sty=
le=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot=
;;color:black">
<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>On Behalf Of </b>FERNANDO PASCUAL BLANCO<br>
<b>Sent:</b> Wednesday, January 16, 2013 5:04 PM<br>
<b>To:</b> <a href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>; Mu=
thu Arul Mozhi Perumal (mperumal)<br>
<b>Cc:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Subject:</b> Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to=
 discover a de-muxer</span><span style=3D"color:black"><o:p></o:p></span></=
p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Jose=
, Muthu,</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I=B4m s=
ure we will find a consensus about that :). What Muthu proposes sounds inte=
resting to me but, to be honest, I think TCMTF establishing should be quite=
 similar to the establishing procedures
 of tunnels defined in draft A (L2TP, GRE&#8230;), actually at network leve=
l TCMTF is a tunnel. Once established signaling will negotiate upper levels=
 (multiplexing and HC) to perform TCMTF (draft A).</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">What do=
 you think?</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Regards=
,</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Fernand=
o Pascual Blanco</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Telef=
=F3nica Global Resources</span><span style=3D"color:black"><o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Network=
 Automation and Dynamization</span><span style=3D"color:black"><o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">TECHNOL=
OGY PEOPLE GROUP</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">F &#43;=
34913128779</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">M &#43;=
34682005168</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><a href=
=3D"mailto:fpb@tid.es">fpb@tid.es</a></span><span style=3D"color:black"><o:=
p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span 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>mi=E9rcoles, 16 de enero de 2013 11:18<br>
<b>To: </b>&quot;'Muthu Arul Mozhi Perumal (mperumal) '&quot; &lt;<a href=
=3D"mailto:mperumal@cisco.com">mperumal@cisco.com</a>&gt;, Fernando Pascual=
 Blanco &lt;<a href=3D"mailto:fpb@tid.es">fpb@tid.es</a>&gt;<br>
<b>Cc: </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>RV: [tcmtf] TCMTF: Document A: mechanism for a muxer to dis=
cover a de-muxer<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoPlainText"><span style=3D"color:black">Fernando, Muthu, ever=
yone,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Since there is no con=
sensus about this, I think we should carry on with the debate. Do you think=
 the mechanism would be very complicated? Any new ideas?:<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">- *<b>dynamically est=
ablishing, modifying and releasing tunnels</b>*<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">#1. A *<b>mechanism f=
or a muxer to discover a de-muxer (and vice versa)</b>*.<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">There is still no con=
sensus here:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Fernando: &#8220;Regarding #1, to be honest, I am not completely su=
re of the need to specify a mechanism to discover muxes and demuxes between=
 them. I think those kind of mechanisms have
 more sense in local environments but I=B4m not sure if it applies here. At=
 least at the beginning this associations can be done manually.&#8221;<o:p>=
</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Muthu: &#8220;I think it is the opposite -- in local environments y=
ou can provision/associate them manually. However, in a multi-vendor enviro=
nment over the Internet this should happen automatically.&#8221;
<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt;text-indent:35.4pt"><=
span style=3D"color:black">&#8220;#1 needs to be specified.&#8221;<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">&nbsp;</sp=
an><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">&nbsp;</sp=
an><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">Best regar=
ds,</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D"><br>
Jose</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">&nbsp;</sp=
an><span style=3D"color:black"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"ES" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">De:</span></b=
><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;=
,&quot;sans-serif&quot;;color:black"><a href=3D"mailto:tcmtf-bounces@ietf.o=
rg">tcmtf-bounces@ietf.org</a>
 [<a href=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</=
a>] <b>En nombre de
</b>Jose Saldana<br>
<b>Enviado el:</b> martes, 15 de enero de 2013 11:56<br>
<b>Para:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tcmtf] TCMTF: Document A discussion: content and charter</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:black">&nbsp;</span=
><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Document (A) refers to t=
he main TCMTF draft, currently in
<a href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http=
://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">1.- Content of the Docum=
ent<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Currently it contains th=
e description of the question and the protocols which could be used on each=
 layer (tunneling, compressing, multiplexing). It says that the signaling i=
ssues would be that of each protocol.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">There is consensus (I th=
ink) about this: we should include some signaling issues. The question is: =
What should we include in Draft A and what in Draft C?<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">- *<b>Auto-negotiation</=
b>* Negotiation mechanisms to decide the options at each layer (compression=
, multiplexing and tunneling) between mux and demux. Perhaps the mux has RO=
HC, ECRTP and IPHC, and the demux only
 has ECRTP and IPHC, so the two machines will have to negotiate in order to=
 decide which compression protocol use.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">This should be included =
in (A). I think there is consensus about this:<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span style=3D"color:bl=
ack">Juan Antonio: &#8220;The first kind of signaling (&quot;auto-negotiati=
on&quot;) is needed from the beginning if we don't want an extremely static=
 protocol and therefore possibly difficult to get it working,
 especially when in most of cases the peers belong to different entities/co=
mpanies.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">Dan: &#8220;We need that -- it is capabilities negotiation.&nbsp; =
It is needed because the protocol will fail if one side mistakenly thinks t=
he other side has certain functionality, and because
 we will want to add some fancy new compression in the year 2020 and will n=
eed to negotiate it.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">Fernando: &#8220;I also agree with the idea of including the mux-d=
emux signaling within the draft A (as Dan said, they are capabilities negot=
iation). This draft should be able to get two
 boxes with TCMTF fully working between them. Under my point of view this i=
ncludes the definition of the capabilities in each node and the negotiation=
 of that capabilities.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Does this mean that D=
ocument (A) will no longer be a Best Current Practice? I think so.<o:p></o:=
p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">- *<b>dynamically est=
ablishing, modifying and releasing tunnels</b>*<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">#1. A *<b>mechanism f=
or a muxer to discover a de-muxer (and vice versa)</b>*.<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">There is still no con=
sensus here:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Fernando: &#8220;Regarding #1, to be honest, I am not completely su=
re of the need to specify a mechanism to discover muxes and demuxes between=
 them. I think those kind of mechanisms have
 more sense in local environments but I=B4m not sure if it applies here. At=
 least at the beginning this associations can be done manually.&#8221;<o:p>=
</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Muthu: &#8220;I think it is the opposite -- in local environments y=
ou can provision/associate them manually. However, in a multi-vendor enviro=
nment over the Internet this should happen automatically.&#8221;
<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt;text-indent:35.4pt"><=
span style=3D"color:black">&#8220;#1 needs to be specified.&#8221;<o:p></o:=
p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">#2. A mechanism to *<=
b>elect an optimal muxer and a de-muxer when there are more than one muxer/=
de-muxer for a flow</b>*.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">We agree: This can wa=
it for Document (C).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ferna=
ndo: &#8220;#2 is more related to the higher entity that has to decide whet=
her a flow should be TCMTFed or not, and under my point of view it can be a=
ddressed in a different draft.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu=
: &#8220;#2 can be added later.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">3. A mechanism to *<b=
>setup/release a tunnel b/w a muxer and a de-muxer</b>*.<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">We agree: This has to=
 be included in (A).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ferna=
ndo &#8220;#3 I think should be included in the draft A, since it is a mech=
anism within the TFMTF protocol itself.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu=
: &#8220;#3 many not require much specification.&#8221;<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span style=3D"color:black">2.- Should we include=
 it in the Charter now?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Of course, Document (A) =
should be in the charter.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Best regards,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Jose<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:black">&nbsp;</span=
><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></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;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;;color:gray"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span style=3D"color:black"><o:p></o:p=
></span></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></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;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;;color:gray"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span style=3D"font-size:10.5pt;color:=
black"><o:p></o:p></span></p>
</div>
</body>
</html>

--_000_E721D8C6A2E1544DB2DEBC313AF54DE223FDBD73xmbrcdx02ciscoc_--

From jsaldana@unizar.es  Tue Jan 22 00:53:42 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE55621F87CC for <tcmtf@ietfa.amsl.com>; Tue, 22 Jan 2013 00:53:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.523
X-Spam-Level: 
X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=0.075,  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 0xmsylmD9ZEv for <tcmtf@ietfa.amsl.com>; Tue, 22 Jan 2013 00:53:33 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2185E21F87C5 for <tcmtf@ietf.org>; Tue, 22 Jan 2013 00:53:31 -0800 (PST)
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 r0M8rOIn011536; Tue, 22 Jan 2013 09:53:24 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Muthu Arul Mozhi Perumal \(mperumal\)'" <mperumal@cisco.com>, "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>
References: <E721D8C6A2E1544DB2DEBC313AF54DE223FD8899@xmb-rcd-x02.cisco.com> <F5EDC35DF914C1428C28E149F10463A2689E2EA9@EX10-MB2-MAD.hi.inet> <E721D8C6A2E1544DB2DEBC313AF54DE223FDBD73@xmb-rcd-x02.cisco.com>
In-Reply-To: <E721D8C6A2E1544DB2DEBC313AF54DE223FDBD73@xmb-rcd-x02.cisco.com>
Date: Tue, 22 Jan 2013 09:53:33 +0100
Organization: Universidad de Zaragoza
Message-ID: <003e01cdf87d$f5a47a50$e0ed6ef0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_003F_01CDF886.576D9D40"
X-Mailer: Microsoft Outlook 14.0
Content-language: es
Thread-index: AQJND6DQXm3ijoADktMHUl3sOOxwbwERwvh7As0C/xSXN+R0EA==
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a de-muxer
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, 22 Jan 2013 08:53:42 -0000

This is a multipart message in MIME format.

------=_NextPart_000_003F_01CDF886.576D9D40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Muthu,

=20

The approach we were thinking about was:

=20

- A first Document (A), the current draft, including the architecture =
and
the basic signaling issues in order to avoid a too static protocol. I =
think
there was (rough) consensus about this.

Juan Antonio: =93The first kind of signaling ("auto-negotiation") is =
needed
from the beginning if we don't want an extremely static protocol and
therefore possibly difficult to get it working, especially when in most =
of
cases the peers belong to different entities/companies.=94

=20

Dan: =93We need that -- it is capabilities negotiation.  It is needed =
because
the protocol will fail if one side mistakenly thinks the other side has
certain functionality, and because we will want to add some fancy new
compression in the year 2020 and will need to negotiate it.=94

=20

Fernando: =93I also agree with the idea of including the mux-demux =
signaling
within the draft A (as Dan said, they are capabilities negotiation). =
This
draft should be able to get two boxes with TCMTF fully working between =
them.
Under my point of view this includes the definition of the capabilities =
in
each node and the negotiation of that capabilities.=94

=20

- A second Document (C) (=3D A-sig), adding new signaling =
functionalities to
the basic ones.

=20

Document (A) would be included in the Charter, and Document (C) would =
wait
until (A) is ready or almost ready.

=20

This is a bit different from the approach you are proposing, but it may =
also
work. I think this approach is perhaps more =93practical=94: if we =
propose an
architecture and leave signaling for the future, nobody will believe =
this
can work. If we begin with the architecture+basic signaling, we will =
have
something that works from the beginning.

=20

What do you think?

=20

Thanks,

=20

Jose

=20

=20

De: Muthu Arul Mozhi Perumal (mperumal) [mailto:mperumal@cisco.com]=20
Enviado el: martes, 22 de enero de 2013 5:34
Para: FERNANDO PASCUAL BLANCO; jsaldana@unizar.es
CC: tcmtf@ietf.org
Asunto: RE: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to =
discover
a de-muxer

=20

Hi Fernando,

=20

Yes, I was referring to draft A. However, I am now thinking it might be
better if we devote draft A for the use cases and the protocol stack
architecture, and write a new draft A-sig describing the negotiation
procedures including automatic discovery/association and capability
exchange. That way we can progress them independently in parallel and
potentially explore multiple negotiation procedures (in the form of =
multiple
drafts, if there is sufficient interest). In essence, I think we should
separate out the use cases and architecture from the solutions.

=20

|1. The way a mux is instructed with the IP address (for example) of a
demux.=20

|   That procedure could be:=20

|   1. Static (i.e. Configuration within the mux)

|   2. Dynamic (i.e. Instructed from a higher entity like a policy =
manager)=20

|      and could be (or not) described in draft C

=20

On dynamic, I would also like to add mux discovering the demux through
negotiation -- this would be case when the mux sees a number of flows =
going
to the same destination but doesn't know if the destination is capable =
of
demuxing.

=20

Muthu

=20

From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]=20
Sent: Monday, January 21, 2013 2:32 PM
To: Muthu Arul Mozhi Perumal (mperumal); jsaldana@unizar.es
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to
discover a de-muxer

=20

Hi Muthu,

=20

I agree that a tunnel is not always needed. But when you say signaling =
doc,
are you referring finally to the draft A? We agreed on addressing
capabilities negotiation on that draft.=20

=20

Nevertheless, I think we should clarify two thinks:

1.	The way a mux is instructed with the IP address (for example) of a
demux. That procedure could be:=20

1.	Static (i.e. Configuration within the mux)
2.	Dynamic (i.e. Instructed from a higher entity like a policy manager)
and could be (or not) described in draft C

2.	The capabilities negotiation: once a mux knows the IP address of a
demux can negotiate the capabilities of the different layers (tunnel,
multiplex and compression). This is also described at the draft A.

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: "'Muthu Arul Mozhi Perumal (mperumal) '" <mperumal@cisco.com>
Date: lunes, 21 de enero de 2013 06:40
To: Fernando Pascual Blanco <fpb@tid.es>, "jsaldana@unizar.es"
<jsaldana@unizar.es>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: RE: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to
discover a de-muxer

=20

Hi Fernando,

=20

|I=B4m sure we will find a consensus about that :).

=20

Sure..

=20

|What Muthu proposes sounds interesting to me but, to be honest, I think
TCMTF=20

|establishing should be quite similar to the establishing procedures of
tunnels=20

|defined in draft A (L2TP, GRE=85),

=20

I agree the procedures for establishing the association b/w the muxer =
and
the de-muxer could be similar to those of establishing a tunnel. =
However, I
would like us to avoid two assumptions:

1. The other end of a tunnel is always TCMTF capable. I think this is =
more
important when you already have a tunnel (say, IPSec tunnel) and would =
like
to perform TCMTF on the fly.

2. A tunnel is always needed for performing TCMTF. If we aren't doing =
any
compression, but only multiplexing, the outermost IP header would be =
intact
and should suffice for routing the packets. There are satellite networks
where reducing the packets per second (pps) for VoIP calls is more =
important
-- they don't do any compression, but only multiplexing, and don't setup =
a
tunnel as well. For e.g:

http://www.cisco.com/web/strategy/docs/gov/aag_c45-697642_v2.pdf

http://www.cisco.com/web/strategy/docs/gov/ip_multiplexing_agensler.pptx

=20

Nevertheless, I think all this go into the signaling doc. If we require
capability negotiation, I think we can combine it with the procedure for
establishing the association b/w the muxer and the de-muxer. If we make
capability negotiation as optional, we might want to keep those as =
separate
procedures.

=20

Muthu

=20

From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =
Of
FERNANDO PASCUAL BLANCO
Sent: Wednesday, January 16, 2013 5:04 PM
To: jsaldana@unizar.es; Muthu Arul Mozhi Perumal (mperumal)
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to
discover a de-muxer

=20

Hi Jose, Muthu,

=20

I=B4m sure we will find a consensus about that :). What Muthu proposes =
sounds
interesting to me but, to be honest, I think TCMTF establishing should =
be
quite similar to the establishing procedures of tunnels defined in draft =
A
(L2TP, GRE=85), actually at network level TCMTF is a tunnel. Once =
established
signaling will negotiate upper levels (multiplexing and HC) to perform =
TCMTF
(draft A).

=20

What do you think?

=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: mi=E9rcoles, 16 de enero de 2013 11:18
To: "'Muthu Arul Mozhi Perumal (mperumal) '" <mperumal@cisco.com>, =
Fernando
Pascual Blanco <fpb@tid.es>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: RV: [tcmtf] TCMTF: Document A: mechanism for a muxer to =
discover a
de-muxer

=20

Fernando, Muthu, everyone,

=20

Since there is no consensus about this, I think we should carry on with =
the
debate. Do you think the mechanism would be very complicated? Any new
ideas?:

=20

- *dynamically establishing, modifying and releasing tunnels*

=20

#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.

=20

There is still no consensus here:

=20

Fernando: =93Regarding #1, to be honest, I am not completely sure of the =
need
to specify a mechanism to discover muxes and demuxes between them. I =
think
those kind of mechanisms have more sense in local environments but I=B4m =
not
sure if it applies here. At least at the beginning this associations can =
be
done manually.=94

=20

Muthu: =93I think it is the opposite -- in local environments you can
provision/associate them manually. However, in a multi-vendor =
environment
over the Internet this should happen automatically.=94=20

=93#1 needs to be specified.=94

=20

=20

Best regards,


Jose

=20

De:tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de =
Jose
Saldana
Enviado el: martes, 15 de enero de 2013 11:56
Para: tcmtf@ietf.org
Asunto: [tcmtf] TCMTF: Document A discussion: content and charter

=20

Document (A) refers to the main TCMTF draft, currently in
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

=20

1.- Content of the Document

=20

Currently it contains the description of the question and the protocols
which could be used on each layer (tunneling, compressing, =
multiplexing). It
says that the signaling issues would be that of each protocol.

=20

There is consensus (I think) about this: we should include some =
signaling
issues. The question is: What should we include in Draft A and what in =
Draft
C?

=20

- *Auto-negotiation* Negotiation mechanisms to decide the options at =
each
layer (compression, multiplexing and tunneling) between mux and demux.
Perhaps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP =
and
IPHC, so the two machines will have to negotiate in order to decide =
which
compression protocol use.

=20

This should be included in (A). I think there is consensus about this:

Juan Antonio: =93The first kind of signaling ("auto-negotiation") is =
needed
from the beginning if we don't want an extremely static protocol and
therefore possibly difficult to get it working, especially when in most =
of
cases the peers belong to different entities/companies.=94

=20

Dan: =93We need that -- it is capabilities negotiation.  It is needed =
because
the protocol will fail if one side mistakenly thinks the other side has
certain functionality, and because we will want to add some fancy new
compression in the year 2020 and will need to negotiate it.=94

=20

Fernando: =93I also agree with the idea of including the mux-demux =
signaling
within the draft A (as Dan said, they are capabilities negotiation). =
This
draft should be able to get two boxes with TCMTF fully working between =
them.
Under my point of view this includes the definition of the capabilities =
in
each node and the negotiation of that capabilities.=94

=20

Does this mean that Document (A) will no longer be a Best Current =
Practice?
I think so.

=20

=20

- *dynamically establishing, modifying and releasing tunnels*

=20

#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.

=20

There is still no consensus here:

=20

Fernando: =93Regarding #1, to be honest, I am not completely sure of the =
need
to specify a mechanism to discover muxes and demuxes between them. I =
think
those kind of mechanisms have more sense in local environments but I=B4m =
not
sure if it applies here. At least at the beginning this associations can =
be
done manually.=94

=20

Muthu: =93I think it is the opposite -- in local environments you can
provision/associate them manually. However, in a multi-vendor =
environment
over the Internet this should happen automatically.=94=20

=93#1 needs to be specified.=94

=20

=20

=20

#2. A mechanism to *elect an optimal muxer and a de-muxer when there are
more than one muxer/de-muxer for a flow*.

=20

We agree: This can wait for Document (C).

=20

                Fernando: =93#2 is more related to the higher entity =
that has
to decide whether a flow should be TCMTFed or not, and under my point of
view it can be addressed in a different draft.=94

                Muthu: =93#2 can be added later.=94

=20

=20

3. A mechanism to *setup/release a tunnel b/w a muxer and a de-muxer*.

=20

We agree: This has to be included in (A).

=20

                Fernando =93#3 I think should be included in the draft =
A,
since it is a mechanism within the TFMTF protocol itself.=94

                Muthu: =93#3 many not require much specification.=94

=20

=20

=20

2.- Should we include it in the Charter now?

=20

Of course, Document (A) should be in the charter.

=20

=20

Best regards,

=20

Jose

=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

=20

  _____ =20


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


------=_NextPart_000_003F_01CDF886.576D9D40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><!--[if =
!mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@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";}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:Consolas;}
span.TextodegloboCar
	{mso-style-name:"Texto de globo Car";
	mso-style-priority:99;
	mso-style-link:"Texto de globo";
	font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.plaintextchar0
	{mso-style-name:plaintextchar;
	font-family:Consolas;}
span.textosinformatocar0
	{mso-style-name:textosinformatocar;
	font-family:"Calibri","sans-serif";}
span.estilocorreo19
	{mso-style-name:estilocorreo19;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.estilocorreo20
	{mso-style-name:estilocorreo20;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.balloontextchar0
	{mso-style-name:balloontextchar;
	font-family:"Tahoma","sans-serif";}
span.emailstyle26
	{mso-style-name:emailstyle26;
	font-family:"Courier New";
	color:windowtext;}
span.EstiloCorreo33
	{mso-style-type:personal;
	font-family:"Courier New";
	color:windowtext;}
span.EstiloCorreo34
	{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:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:38286162;
	mso-list-template-ids:932094810;}
@list l1
	{mso-list-id:588194996;
	mso-list-template-ids:1887467282;}
@list l1:level1
	{mso-level-start-at:2;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2
	{mso-list-id:778765105;
	mso-list-template-ids:-1609411884;}
@list l2:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3
	{mso-list-id:1521624881;
	mso-list-template-ids:-1956083994;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Muthu,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>The =
approach we were thinking about was:<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'>- A first =
Document (A), the current draft, including the architecture and the =
basic signaling issues in order to avoid a too static protocol. I think =
there was (rough) consensus about this.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:35.4pt'><span lang=3DEN-US>Juan =
Antonio: &#8220;The first kind of signaling =
(&quot;auto-negotiation&quot;) is needed from the beginning if we don't =
want an extremely static protocol and therefore possibly difficult to =
get it working, especially when in most of cases the peers belong to =
different entities/companies.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US>Dan: &#8220;We need that -- it is capabilities =
negotiation.&nbsp; It is needed because the protocol will fail if one =
side mistakenly thinks the other side has certain functionality, and =
because we will want to add some fancy new compression in the year 2020 =
and will need to negotiate it.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Fernando: &#8220;I also =
agree with the idea of including the mux-demux signaling within the =
draft A (as Dan said, they are capabilities negotiation). This draft =
should be able to get two boxes with TCMTF fully working between them. =
Under my point of view this includes the definition of the capabilities =
in each node and the negotiation of that =
capabilities.&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- A second =
Document (C) (=3D A-sig), adding new signaling functionalities to the =
basic ones.<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'>Document =
(A) would be included in the Charter, and Document (C) would wait until =
(A) is ready or almost ready.<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'>This is a =
bit different from the approach you are proposing, but it may also work. =
I think this approach is perhaps more &#8220;practical&#8221;: if we =
propose an architecture and leave signaling for the future, nobody will =
believe this can work. If we begin with the architecture+basic =
signaling, we will have something that works from the =
beginning.<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'>What do you =
think?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><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"'> =
Muthu Arul Mozhi Perumal (mperumal) [mailto:mperumal@cisco.com] =
<br><b>Enviado el:</b> martes, 22 de enero de 2013 5:34<br><b>Para:</b> =
FERNANDO PASCUAL BLANCO; jsaldana@unizar.es<br><b>CC:</b> =
tcmtf@ietf.org<br><b>Asunto:</b> RE: [tcmtf] RV: TCMTF: Document A: =
mechanism for a muxer to discover a =
de-muxer<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'>Hi =
Fernando,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'>Yes, I =
was referring to draft A. However, I am now thinking it might be better =
if we devote draft A for the use cases and the protocol stack =
architecture, and write a new draft A-sig describing the negotiation =
procedures including automatic discovery/association and capability =
exchange. That way we can progress them independently in parallel and =
potentially explore multiple negotiation procedures (in the form of =
multiple drafts, if there is sufficient interest). In essence, I think =
we should separate out the use cases and architecture from the =
solutions.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'>|1. =
The way a mux is instructed with the IP address (for example) of a =
demux. <o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier New"'>|&nbsp; &nbsp;That =
procedure could be: <o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New"'>|&nbsp;&nbsp; 1. Static (i.e. Configuration within the =
mux)<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier New"'>|&nbsp;&nbsp; 2. =
Dynamic (i.e. Instructed from a higher entity like a policy manager) =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and could be (or not) described in =
draft C<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'>On =
dynamic, I would also like to add mux discovering the demux through =
negotiation -- this would be case when the mux sees a number of flows =
going to the same destination but doesn't know if the destination is =
capable of demuxing.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Muthu<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> FERNANDO =
PASCUAL BLANCO [<a href=3D"mailto:fpb@tid.es">mailto:fpb@tid.es</a>] =
<br><b>Sent:</b> Monday, January 21, 2013 2:32 PM<br><b>To:</b> Muthu =
Arul Mozhi Perumal (mperumal); <a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a><br><b>Cc:</b> =
<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><b>Subject:</b> =
Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a =
de-muxer<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><div><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Hi =
Muthu,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>I agree that a tunnel is not =
always needed. But when you say signaling doc, are you referring finally =
to the draft A? We agreed on addressing capabilities negotiation on that =
draft.&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Nevertheless, I think we should =
clarify two thinks:<o:p></o:p></span></p></div><ol start=3D1 =
type=3D1><li class=3DMsoNormal =
style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l2 level1 lfo3'><span lang=3DEN-US =
style=3D'font-size:10.5pt'>The way a mux is instructed with the IP =
address (for example) of a demux. That procedure could be: =
<o:p></o:p></span></li></ol><ol start=3D1 type=3D1><ol start=3D1 =
type=3D1><li class=3DMsoNormal =
style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l2 level2 lfo3'><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Static (i.e. Configuration within the =
mux)<o:p></o:p></span></li><li class=3DMsoNormal =
style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l2 level2 lfo3'><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Dynamic (i.e. Instructed from a higher entity =
like a policy manager) and could be (or not) described in draft =
C<o:p></o:p></span></li></ol></ol><ol start=3D2 type=3D1><li =
class=3DMsoNormal =
style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l2 level1 lfo3'><span lang=3DEN-US =
style=3D'font-size:10.5pt'>The capabilities negotiation: once a mux =
knows the IP address of a demux can negotiate the capabilities of the =
different layers (tunnel, multiplex and compression). This is also =
described at the draft A.<o:p></o:p></span></li></ol><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Regards,<o:p></o:p></span></p></di=
v><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Fernando Pascual =
Blanco<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>Telef=F3nica Global =
Resources<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>Network Automation =
and Dynamization<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>TECHNOLOGY PEOPLE =
GROUP<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>F =
+34913128779<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>M =
+34682005168<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US 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 lang=3DEN-US =
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 lang=3DEN-US =
style=3D'color:black'>From: </span></b><span lang=3DEN-US =
style=3D'color:black'>&quot;'Muthu Arul Mozhi Perumal (mperumal) '&quot; =
&lt;<a =
href=3D"mailto:mperumal@cisco.com">mperumal@cisco.com</a>&gt;<br><b>Date:=
 </b>lunes, 21 de enero de 2013 06:40<br><b>To: </b>Fernando Pascual =
Blanco &lt;<a href=3D"mailto:fpb@tid.es">fpb@tid.es</a>&gt;, &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>Cc: =
</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>RE: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover =
a de-muxer<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p>&nbsp;</o:p></span></p></div>=
<div><div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>Hi =
Fernando,</span><span lang=3DEN-US =
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:"Courier =
New";color:black'>&nbsp;</span><span lang=3DEN-US =
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:"Courier =
New";color:black'>|I=B4m sure we will find a consensus about that =
:).</span><span lang=3DEN-US =
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:"Courier =
New";color:black'>&nbsp;</span><span lang=3DEN-US =
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:"Courier =
New";color:black'>Sure..</span><span lang=3DEN-US =
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:"Courier =
New";color:black'>&nbsp;</span><span lang=3DEN-US =
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:"Courier =
New";color:black'>|What Muthu proposes sounds interesting to me but, to =
be honest, I think TCMTF </span><span lang=3DEN-US =
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:"Courier =
New";color:black'>|establishing should be quite similar to the =
establishing procedures of tunnels </span><span lang=3DEN-US =
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:"Courier =
New";color:black'>|defined in draft A (L2TP, GRE&#8230;),</span><span =
lang=3DEN-US 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:"Courier =
New";color:black'>&nbsp;</span><span lang=3DEN-US =
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:"Courier =
New";color:black'>I agree the procedures for establishing the =
association b/w the muxer and the de-muxer could be similar to those of =
establishing a tunnel. However, I would like us to avoid two =
assumptions:</span><span lang=3DEN-US =
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:"Courier =
New";color:black'>1. The other end of a tunnel is always TCMTF capable. =
I think this is more important when you already have a tunnel (say, =
IPSec tunnel) and would like to perform TCMTF on the fly.</span><span =
lang=3DEN-US 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:"Courier New";color:black'>2. A =
tunnel is always needed for performing TCMTF. If we aren't doing any =
compression, but only multiplexing, the outermost IP header would be =
intact and should suffice for routing the packets. There are satellite =
networks where reducing the packets per second (pps) for VoIP calls is =
more important -- they don't do any compression, but only multiplexing, =
and don't setup a tunnel as well. For e.g:</span><span lang=3DEN-US =
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:"Courier =
New";color:black'><a =
href=3D"http://www.cisco.com/web/strategy/docs/gov/aag_c45-697642_v2.pdf"=
>http://www.cisco.com/web/strategy/docs/gov/aag_c45-697642_v2.pdf</a></sp=
an><span lang=3DEN-US 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:"Courier New";color:black'><a =
href=3D"http://www.cisco.com/web/strategy/docs/gov/ip_multiplexing_agensl=
er.pptx">http://www.cisco.com/web/strategy/docs/gov/ip_multiplexing_agens=
ler.pptx</a></span><span lang=3DEN-US =
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:"Courier =
New";color:black'>&nbsp;</span><span lang=3DEN-US =
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:"Courier =
New";color:black'>Nevertheless, I think all this go into the signaling =
doc. If we require capability negotiation, I think we can combine it =
with the procedure for establishing the association b/w the muxer and =
the de-muxer. If we make capability negotiation as optional, we might =
want to keep those as separate procedures.</span><span lang=3DEN-US =
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:"Courier =
New";color:black'>&nbsp;</span><span lang=3DEN-US =
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:"Courier =
New";color:black'>Muthu</span><span lang=3DEN-US =
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:"Courier =
New";color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></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";color:black'>=
From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
 <a href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> =
[<a =
href=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]=
 <b>On Behalf Of </b>FERNANDO PASCUAL BLANCO<br><b>Sent:</b> Wednesday, =
January 16, 2013 5:04 PM<br><b>To:</b> <a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>; Muthu Arul =
Mozhi Perumal (mperumal)<br><b>Cc:</b> <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><b>Subject:</b> Re: =
[tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a =
de-muxer</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><div><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Hi Jose, Muthu,</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>I=B4m sure we will find a =
consensus about that :). What Muthu proposes sounds interesting to me =
but, to be honest, I think TCMTF establishing should be quite similar to =
the establishing procedures of tunnels defined in draft A (L2TP, =
GRE&#8230;), actually at network level TCMTF is a tunnel. Once =
established signaling will negotiate upper levels (multiplexing and HC) =
to perform TCMTF (draft A).</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>What do you think?</span><span =
lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Regards,</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Fernando Pascual =
Blanco</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Telef=F3nica Global =
Resources</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>Network Automation and =
Dynamization</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>TECHNOLOGY PEOPLE =
GROUP</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>F +34913128779</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>M +34682005168</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><a =
href=3D"mailto:fpb@tid.es">fpb@tid.es</a></span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div></div></div></div><div>=
<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'color:black'>From: </span></b><span lang=3DEN-US =
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>mi=E9rcoles, 16 de enero de 2013 11:18<br><b>To: </b>&quot;'Muthu =
Arul Mozhi Perumal (mperumal) '&quot; &lt;<a =
href=3D"mailto:mperumal@cisco.com">mperumal@cisco.com</a>&gt;, Fernando =
Pascual Blanco &lt;<a =
href=3D"mailto:fpb@tid.es">fpb@tid.es</a>&gt;<br><b>Cc: </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>RV: [tcmtf] TCMTF: Document A: mechanism for a muxer to discover a =
de-muxer<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span =
lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div><div><div><div><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>Fernando, =
Muthu, everyone,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>Since =
there is no consensus about this, I think we should carry on with the =
debate. Do you think the mechanism would be very complicated? Any new =
ideas?:<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>- =
*<b>dynamically establishing, modifying and releasing =
tunnels</b>*<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>#1. A =
*<b>mechanism for a muxer to discover a de-muxer (and vice =
versa)</b>*.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>There is =
still no consensus here:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.4pt'><span lang=3DEN-US =
style=3D'color:black'>Fernando: &#8220;Regarding #1, to be honest, I am =
not completely sure of the need to specify a mechanism to discover muxes =
and demuxes between them. I think those kind of mechanisms have more =
sense in local environments but I=B4m not sure if it applies here. At =
least at the beginning this associations can be done =
manually.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.4pt'><span lang=3DEN-US =
style=3D'color:black'>Muthu: &#8220;I think it is the opposite -- in =
local environments you can provision/associate them manually. However, =
in a multi-vendor environment over the Internet this should happen =
automatically.&#8221; <o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.4pt;text-indent:35.4pt'><span lang=3DEN-US =
style=3D'color:black'>&#8220;#1 needs to be =
specified.&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Best regards,</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><br>Jose</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></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";color:black'>=
De:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
<a href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a =
href=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]=
 <b>En nombre de </b>Jose Saldana<br><b>Enviado el:</b> martes, 15 de =
enero de 2013 11:56<br><b>Para:</b> <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><b>Asunto:</b> =
[tcmtf] TCMTF: Document A discussion: content and charter</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span style=3D'color:black'>&nbsp;</span><span =
lang=3DEN-US style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>Document (A) =
refers to the main TCMTF draft, currently in <a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http:=
//datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></spa=
n></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>1.- Content =
of the Document<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>Currently it =
contains the description of the question and the protocols which could =
be used on each layer (tunneling, compressing, multiplexing). It says =
that the signaling issues would be that of each =
protocol.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>There is =
consensus (I think) about this: we should include some signaling issues. =
The question is: What should we include in Draft A and what in Draft =
C?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>- =
*<b>Auto-negotiation</b>* Negotiation mechanisms to decide the options =
at each layer (compression, multiplexing and tunneling) between mux and =
demux. Perhaps the mux has ROHC, ECRTP and IPHC, and the demux only has =
ECRTP and IPHC, so the two machines will have to negotiate in order to =
decide which compression protocol use.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>This should =
be included in (A). I think there is consensus about =
this:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:35.4pt'><span lang=3DEN-US =
style=3D'color:black'>Juan Antonio: &#8220;The first kind of signaling =
(&quot;auto-negotiation&quot;) is needed from the beginning if we don't =
want an extremely static protocol and therefore possibly difficult to =
get it working, especially when in most of cases the peers belong to =
different entities/companies.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span lang=3DEN-US =
style=3D'color:black'>Dan: &#8220;We need that -- it is capabilities =
negotiation.&nbsp; It is needed because the protocol will fail if one =
side mistakenly thinks the other side has certain functionality, and =
because we will want to add some fancy new compression in the year 2020 =
and will need to negotiate it.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span lang=3DEN-US =
style=3D'color:black'>Fernando: &#8220;I also agree with the idea of =
including the mux-demux signaling within the draft A (as Dan said, they =
are capabilities negotiation). This draft should be able to get two =
boxes with TCMTF fully working between them. Under my point of view this =
includes the definition of the capabilities in each node and the =
negotiation of that capabilities.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>Does this =
mean that Document (A) will no longer be a Best Current Practice? I =
think so.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>- =
*<b>dynamically establishing, modifying and releasing =
tunnels</b>*<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>#1. A =
*<b>mechanism for a muxer to discover a de-muxer (and vice =
versa)</b>*.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>There is =
still no consensus here:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.4pt'><span lang=3DEN-US =
style=3D'color:black'>Fernando: &#8220;Regarding #1, to be honest, I am =
not completely sure of the need to specify a mechanism to discover muxes =
and demuxes between them. I think those kind of mechanisms have more =
sense in local environments but I=B4m not sure if it applies here. At =
least at the beginning this associations can be done =
manually.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.4pt'><span lang=3DEN-US =
style=3D'color:black'>Muthu: &#8220;I think it is the opposite -- in =
local environments you can provision/associate them manually. However, =
in a multi-vendor environment over the Internet this should happen =
automatically.&#8221; <o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.4pt;text-indent:35.4pt'><span lang=3DEN-US =
style=3D'color:black'>&#8220;#1 needs to be =
specified.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>#2. A =
mechanism to *<b>elect an optimal muxer and a de-muxer when there are =
more than one muxer/de-muxer for a flow</b>*.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>We agree: =
This can wait for Document (C).<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fernando: &#8220;#2 is more =
related to the higher entity that has to decide whether a flow should be =
TCMTFed or not, and under my point of view it can be addressed in a =
different draft.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu: &#8220;#2 can be added =
later.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>3. A =
mechanism to *<b>setup/release a tunnel b/w a muxer and a =
de-muxer</b>*.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>We agree: =
This has to be included in (A).<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fernando &#8220;#3 I think =
should be included in the draft A, since it is a mechanism within the =
TFMTF protocol itself.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu: &#8220;#3 many not =
require much specification.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:black'>2.- Should =
we include it in the Charter now?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>Of course, =
Document (A) should be in the charter.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:black'>Best =
regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:black'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:black'>&nbsp;</span><span =
lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div></div></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'>&nbsp;</span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><hr size=3D2 width=3D"100%" =
align=3Dcenter></span></div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br=
>Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico en el enlace situado m=E1s abajo.<br>This message is =
intended exclusively for its addressee. We only send and receive email =
on the basis of the terms set out at:<br><a =
href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/E=
S/PAGINAS/disclaimer.aspx</a></span><span lang=3DEN-US =
style=3D'color:black'><o:p></o:p></span></p></div></div></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
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 =
lang=3DEN-US style=3D'font-size:10.5pt;color:black'><hr size=3D2 =
width=3D"100%" align=3Dcenter></span></div><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br=
>Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico en el enlace situado m=E1s abajo.<br>This message is =
intended exclusively for its addressee. We only send and receive email =
on the basis of the terms set out at:<br><a =
href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/E=
S/PAGINAS/disclaimer.aspx</a></span><span lang=3DEN-US =
style=3D'font-size:10.5pt;color:black'><o:p></o:p></span></p></div></div>=
</body></html>
------=_NextPart_000_003F_01CDF886.576D9D40--


From mperumal@cisco.com  Tue Jan 22 01:37:44 2013
Return-Path: <mperumal@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BAFE21F86AB for <tcmtf@ietfa.amsl.com>; Tue, 22 Jan 2013 01:37:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BwNEICuS4dur for <tcmtf@ietfa.amsl.com>; Tue, 22 Jan 2013 01:37:36 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id A143221F8684 for <tcmtf@ietf.org>; Tue, 22 Jan 2013 01:37:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=64108; q=dns/txt; s=iport; t=1358847455; x=1360057055; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=NkPC355qJk9HvvgZQUEL3ANWQLt1ew6KvKXzjDxYjtg=; b=hR0q8Kokiw7oliSaWzFwioMNXjU8KI5Z1Q57QPaVuUiWzaY4aIMfw/C2 DPisEVvbZIjT48zhoehwvDw2ViWLLNMtPhPHqY2S9YMeOJckyqZQlRA0s LGEW1mxIxaJXhjCJEk25rUpqx8pkQak+3e/lZ91Pya7Pai0cYo8rTHmJ1 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnUFAChd/lCtJXG8/2dsb2JhbABEgkipPIkMAYkjFnOCHgEBAQICGhNMEAIBCBEBAgEBAQsWAQYHMhQDBggCBAENBQgTh34MrESPMIx+g1dhA4gsii2ET48tgnWBbzU
X-IronPort-AV: E=Sophos;i="4.84,513,1355097600";  d="scan'208,217";a="166001601"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-7.cisco.com with ESMTP; 22 Jan 2013 09:37:33 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r0M9bX0r013446 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Jan 2013 09:37:33 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.64]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.02.0318.004; Tue, 22 Jan 2013 03:37:33 -0600
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>
Thread-Topic: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a de-muxer
Thread-Index: Ac3z0qpuai7heI7oSHWY0AJDN9gmvgACrW2AAO2IJEAAFSw5AAAbQTuQABbCS4AAC+W9QA==
Date: Tue, 22 Jan 2013 09:37:32 +0000
Message-ID: <E721D8C6A2E1544DB2DEBC313AF54DE223FDC598@xmb-rcd-x02.cisco.com>
References: <E721D8C6A2E1544DB2DEBC313AF54DE223FD8899@xmb-rcd-x02.cisco.com> <F5EDC35DF914C1428C28E149F10463A2689E2EA9@EX10-MB2-MAD.hi.inet> <E721D8C6A2E1544DB2DEBC313AF54DE223FDBD73@xmb-rcd-x02.cisco.com> <003e01cdf87d$f5a47a50$e0ed6ef0$@unizar.es>
In-Reply-To: <003e01cdf87d$f5a47a50$e0ed6ef0$@unizar.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [173.39.67.39]
Content-Type: multipart/alternative; boundary="_000_E721D8C6A2E1544DB2DEBC313AF54DE223FDC598xmbrcdx02ciscoc_"
MIME-Version: 1.0
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discover a de-muxer
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, 22 Jan 2013 09:37:44 -0000

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

Hi Jose,

|This is a bit different from the approach you are proposing, but
|it may also work.

It would..

|I think this approach is perhaps more "practical":
|if we propose an architecture and leave signaling for the future,
|nobody will believe this can work. If we begin with the architecture+basic
|signaling, we will have something that works from the beginning.

I wasn't suggesting we leave signaling for the future and I agree we should=
 begin with the architecture + basic signaling. I was only suggesting we de=
vote another I-D for signaling (i.e A-sig would include basic signaling). T=
hat way we can progress them independently..for e.g we can WGLC the archite=
cture as soon as it is ready, without having to wait for signaling.

I am a fan of smaller I-Ds than a larger one :)

Muthu

From: Jose Saldana [mailto:jsaldana@unizar.es]
Sent: Tuesday, January 22, 2013 2:24 PM
To: Muthu Arul Mozhi Perumal (mperumal); 'FERNANDO PASCUAL BLANCO'
Cc: tcmtf@ietf.org
Subject: RE: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discov=
er a de-muxer

Muthu,

The approach we were thinking about was:

- A first Document (A), the current draft, including the architecture and t=
he basic signaling issues in order to avoid a too static protocol. I think =
there was (rough) consensus about this.
Juan Antonio: "The first kind of signaling ("auto-negotiation") is needed f=
rom the beginning if we don't want an extremely static protocol and therefo=
re possibly difficult to get it working, especially when in most of cases t=
he peers belong to different entities/companies."



Dan: "We need that -- it is capabilities negotiation.  It is needed because=
 the protocol will fail if one side mistakenly thinks the other side has ce=
rtain functionality, and because we will want to add some fancy new compres=
sion in the year 2020 and will need to negotiate it."



Fernando: "I also agree with the idea of including the mux-demux signaling =
within the draft A (as Dan said, they are capabilities negotiation). This d=
raft should be able to get two boxes with TCMTF fully working between them.=
 Under my point of view this includes the definition of the capabilities in=
 each node and the negotiation of that capabilities."

- A second Document (C) (=3D A-sig), adding new signaling functionalities t=
o the basic ones.

Document (A) would be included in the Charter, and Document (C) would wait =
until (A) is ready or almost ready.

This is a bit different from the approach you are proposing, but it may als=
o work. I think this approach is perhaps more "practical": if we propose an=
 architecture and leave signaling for the future, nobody will believe this =
can work. If we begin with the architecture+basic signaling, we will have s=
omething that works from the beginning.

What do you think?

Thanks,

Jose


De: Muthu Arul Mozhi Perumal (mperumal) [mailto:mperumal@cisco.com]
Enviado el: martes, 22 de enero de 2013 5:34
Para: FERNANDO PASCUAL BLANCO; jsaldana@unizar.es<mailto:jsaldana@unizar.es=
>
CC: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: RE: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discove=
r a de-muxer

Hi Fernando,

Yes, I was referring to draft A. However, I am now thinking it might be bet=
ter if we devote draft A for the use cases and the protocol stack architect=
ure, and write a new draft A-sig describing the negotiation procedures incl=
uding automatic discovery/association and capability exchange. That way we =
can progress them independently in parallel and potentially explore multipl=
e negotiation procedures (in the form of multiple drafts, if there is suffi=
cient interest). In essence, I think we should separate out the use cases a=
nd architecture from the solutions.

|1. The way a mux is instructed with the IP address (for example) of a demu=
x.
|   That procedure could be:
|   1. Static (i.e. Configuration within the mux)
|   2. Dynamic (i.e. Instructed from a higher entity like a policy manager)
|      and could be (or not) described in draft C

On dynamic, I would also like to add mux discovering the demux through nego=
tiation -- this would be case when the mux sees a number of flows going to =
the same destination but doesn't know if the destination is capable of demu=
xing.

Muthu

From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
Sent: Monday, January 21, 2013 2:32 PM
To: Muthu Arul Mozhi Perumal (mperumal); jsaldana@unizar.es<mailto:jsaldana=
@unizar.es>
Cc: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discov=
er a de-muxer

Hi Muthu,

I agree that a tunnel is not always needed. But when you say signaling doc,=
 are you referring finally to the draft A? We agreed on addressing capabili=
ties negotiation on that draft.

Nevertheless, I think we should clarify two thinks:

  1.  The way a mux is instructed with the IP address (for example) of a de=
mux. That procedure could be:

     *   Static (i.e. Configuration within the mux)
     *   Dynamic (i.e. Instructed from a higher entity like a policy manage=
r) and could be (or not) described in draft C

  1.  The capabilities negotiation: once a mux knows the IP address of a de=
mux can negotiate the capabilities of the different layers (tunnel, multipl=
ex and compression). This is also described at the draft A.
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: "'Muthu Arul Mozhi Perumal (mperumal) '" <mperumal@cisco.com<mailto:m=
perumal@cisco.com>>
Date: lunes, 21 de enero de 2013 06:40
To: Fernando Pascual Blanco <fpb@tid.es<mailto:fpb@tid.es>>, "jsaldana@uniz=
ar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.es<mailto:jsaldana@uniza=
r.es>>
Cc: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Subject: RE: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discov=
er a de-muxer

Hi Fernando,

|I=B4m sure we will find a consensus about that :).

Sure..

|What Muthu proposes sounds interesting to me but, to be honest, I think TC=
MTF
|establishing should be quite similar to the establishing procedures of tun=
nels
|defined in draft A (L2TP, GRE...),

I agree the procedures for establishing the association b/w the muxer and t=
he de-muxer could be similar to those of establishing a tunnel. However, I =
would like us to avoid two assumptions:
1. The other end of a tunnel is always TCMTF capable. I think this is more =
important when you already have a tunnel (say, IPSec tunnel) and would like=
 to perform TCMTF on the fly.
2. A tunnel is always needed for performing TCMTF. If we aren't doing any c=
ompression, but only multiplexing, the outermost IP header would be intact =
and should suffice for routing the packets. There are satellite networks wh=
ere reducing the packets per second (pps) for VoIP calls is more important =
-- they don't do any compression, but only multiplexing, and don't setup a =
tunnel as well. For e.g:
http://www.cisco.com/web/strategy/docs/gov/aag_c45-697642_v2.pdf
http://www.cisco.com/web/strategy/docs/gov/ip_multiplexing_agensler.pptx

Nevertheless, I think all this go into the signaling doc. If we require cap=
ability negotiation, I think we can combine it with the procedure for estab=
lishing the association b/w the muxer and the de-muxer. If we make capabili=
ty negotiation as optional, we might want to keep those as separate procedu=
res.

Muthu

From: tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-b=
ounces@ietf.org] On Behalf Of FERNANDO PASCUAL BLANCO
Sent: Wednesday, January 16, 2013 5:04 PM
To: jsaldana@unizar.es<mailto:jsaldana@unizar.es>; Muthu Arul Mozhi Perumal=
 (mperumal)
Cc: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Subject: Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to discov=
er a de-muxer

Hi Jose, Muthu,

I=B4m sure we will find a consensus about that :). What Muthu proposes soun=
ds interesting to me but, to be honest, I think TCMTF establishing should b=
e quite similar to the establishing procedures of tunnels defined in draft =
A (L2TP, GRE...), actually at network level TCMTF is a tunnel. Once establi=
shed signaling will negotiate upper levels (multiplexing and HC) to perform=
 TCMTF (draft A).

What do you think?

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: mi=E9rcoles, 16 de enero de 2013 11:18
To: "'Muthu Arul Mozhi Perumal (mperumal) '" <mperumal@cisco.com<mailto:mpe=
rumal@cisco.com>>, 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: RV: [tcmtf] TCMTF: Document A: mechanism for a muxer to discover a=
 de-muxer


Fernando, Muthu, everyone,



Since there is no consensus about this, I think we should carry on with the=
 debate. Do you think the mechanism would be very complicated? Any new idea=
s?:



- *dynamically establishing, modifying and releasing tunnels*



#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.



There is still no consensus here:



Fernando: "Regarding #1, to be honest, I am not completely sure of the need=
 to specify a mechanism to discover muxes and demuxes between them. I think=
 those kind of mechanisms have more sense in local environments but I=B4m n=
ot sure if it applies here. At least at the beginning this associations can=
 be done manually."



Muthu: "I think it is the opposite -- in local environments you can provisi=
on/associate them manually. However, in a multi-vendor environment over the=
 Internet this should happen automatically."

"#1 needs to be specified."


Best regards,

Jose

De:tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-boun=
ces@ietf.org] En nombre de Jose Saldana
Enviado el: martes, 15 de enero de 2013 11:56
Para: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: [tcmtf] TCMTF: Document A discussion: content and charter

Document (A) refers to the main TCMTF draft, currently in http://datatracke=
r.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

1.- Content of the Document

Currently it contains the description of the question and the protocols whi=
ch could be used on each layer (tunneling, compressing, multiplexing). It s=
ays that the signaling issues would be that of each protocol.

There is consensus (I think) about this: we should include some signaling i=
ssues. The question is: What should we include in Draft A and what in Draft=
 C?

- *Auto-negotiation* Negotiation mechanisms to decide the options at each l=
ayer (compression, multiplexing and tunneling) between mux and demux. Perha=
ps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP and IPHC,=
 so the two machines will have to negotiate in order to decide which compre=
ssion protocol use.

This should be included in (A). I think there is consensus about this:
Juan Antonio: "The first kind of signaling ("auto-negotiation") is needed f=
rom the beginning if we don't want an extremely static protocol and therefo=
re possibly difficult to get it working, especially when in most of cases t=
he peers belong to different entities/companies."



Dan: "We need that -- it is capabilities negotiation.  It is needed because=
 the protocol will fail if one side mistakenly thinks the other side has ce=
rtain functionality, and because we will want to add some fancy new compres=
sion in the year 2020 and will need to negotiate it."



Fernando: "I also agree with the idea of including the mux-demux signaling =
within the draft A (as Dan said, they are capabilities negotiation). This d=
raft should be able to get two boxes with TCMTF fully working between them.=
 Under my point of view this includes the definition of the capabilities in=
 each node and the negotiation of that capabilities."



Does this mean that Document (A) will no longer be a Best Current Practice?=
 I think so.





- *dynamically establishing, modifying and releasing tunnels*



#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.



There is still no consensus here:



Fernando: "Regarding #1, to be honest, I am not completely sure of the need=
 to specify a mechanism to discover muxes and demuxes between them. I think=
 those kind of mechanisms have more sense in local environments but I=B4m n=
ot sure if it applies here. At least at the beginning this associations can=
 be done manually."



Muthu: "I think it is the opposite -- in local environments you can provisi=
on/associate them manually. However, in a multi-vendor environment over the=
 Internet this should happen automatically."

"#1 needs to be specified."







#2. A mechanism to *elect an optimal muxer and a de-muxer when there are mo=
re than one muxer/de-muxer for a flow*.



We agree: This can wait for Document (C).



                Fernando: "#2 is more related to the higher entity that has=
 to decide whether a flow should be TCMTFed or not, and under my point of v=
iew it can be addressed in a different draft."

                Muthu: "#2 can be added later."





3. A mechanism to *setup/release a tunnel b/w a muxer and a de-muxer*.



We agree: This has to be included in (A).



                Fernando "#3 I think should be included in the draft A, sin=
ce it is a mechanism within the TFMTF protocol itself."

                Muthu: "#3 many not require much specification."





2.- Should we include it in the Charter now?

Of course, Document (A) should be in the charter.


Best regards,

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

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	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:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
	{mso-style-name:msochpdefault;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
p.Textosinformato, li.Textosinformato, div.Textosinformato
	{mso-style-name:"Texto sin formato";
	mso-style-link:"Texto sin formato Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:Consolas;}
p.Textodeglobo, li.Textodeglobo, div.Textodeglobo
	{mso-style-name:"Texto de globo";
	mso-style-link:"Texto de globo Car";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.TextodegloboCar
	{mso-style-name:"Texto de globo Car";
	mso-style-priority:99;
	mso-style-link:"Texto de globo";
	font-family:"Tahoma","sans-serif";}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.plaintextchar0
	{mso-style-name:plaintextchar;
	font-family:Consolas;}
span.textosinformatocar0
	{mso-style-name:textosinformatocar;
	font-family:"Calibri","sans-serif";}
span.estilocorreo19
	{mso-style-name:estilocorreo19;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.estilocorreo20
	{mso-style-name:estilocorreo20;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.balloontextchar0
	{mso-style-name:balloontextchar;
	font-family:"Tahoma","sans-serif";}
span.emailstyle26
	{mso-style-name:emailstyle26;
	font-family:"Courier New";
	color:windowtext;}
span.EmailStyle33
	{mso-style-type:personal;
	font-family:"Courier New";
	color:windowtext;}
span.EmailStyle34
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle35
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:326790430;
	mso-list-template-ids:-1609411884;}
@list l1
	{mso-list-id:778765105;
	mso-list-template-ids:-1609411884;}
@list l1:level1
	{mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2
	{mso-list-id:1174030527;
	mso-list-template-ids:-1609411884;}
@list l3
	{mso-list-id:1678072833;
	mso-list-template-ids:-1609411884;}
@list l3:level1
	{mso-level-start-at:2;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hi Jose,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|This is a bit different from the approach you are proposi=
ng, but
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|it may also work.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">It would..<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|I think this approach is perhaps more &quot;practical&quo=
t;:
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|if we propose an architecture and leave signaling for the=
 future,
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|nobody will believe this can work. If we begin with the a=
rchitecture&#43;basic
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|signaling, we will have something that works from the beg=
inning.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">I wasn't suggesting we leave signaling for the future and =
I agree we should begin with the architecture &#43; basic signaling. I was =
only suggesting we devote another I-D for signaling
 (i.e A-sig would include basic signaling). That way we can progress them i=
ndependently..for e.g we can WGLC the architecture as soon as it is ready, =
without having to wait for signaling.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">I am a fan of smaller I-Ds than a larger one :)<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Muthu<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jose Sal=
dana [mailto:jsaldana@unizar.es]
<br>
<b>Sent:</b> Tuesday, January 22, 2013 2:24 PM<br>
<b>To:</b> Muthu Arul Mozhi Perumal (mperumal); 'FERNANDO PASCUAL BLANCO'<b=
r>
<b>Cc:</b> tcmtf@ietf.org<br>
<b>Subject:</b> RE: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to=
 discover a de-muxer<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">Muthu,<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The approach we were t=
hinking about was:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- A first Document (A)=
, the current draft, including the architecture and the basic signaling iss=
ues in order to avoid a too static protocol. I think there was (rough) cons=
ensus about this.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt">Juan Antonio: &#8220;Th=
e first kind of signaling (&quot;auto-negotiation&quot;) is needed from the=
 beginning if we don't want an extremely static protocol and therefore poss=
ibly difficult to get it working, especially when in
 most of cases the peers belong to different entities/companies.&#8221;<o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt">Dan: &#8220;We need=
 that -- it is capabilities negotiation.&nbsp; It is needed because the pro=
tocol will fail if one side mistakenly thinks the other side has certain fu=
nctionality, and because we will want to add some
 fancy new compression in the year 2020 and will need to negotiate it.&#822=
1;<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><o:p>&nbsp;</o:p></=
p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt">Fernando: &#8220;I =
also agree with the idea of including the mux-demux signaling within the dr=
aft A (as Dan said, they are capabilities negotiation). This draft should b=
e able to get two boxes with TCMTF fully working
 between them. Under my point of view this includes the definition of the c=
apabilities in each node and the negotiation of that capabilities.&#8221;<o=
:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- A second Document (C=
) (=3D A-sig), adding new signaling functionalities to the basic ones.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Document (A) would be =
included in the Charter, and Document (C) would wait until (A) is ready or =
almost ready.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">This is a bit differen=
t from the approach you are proposing, but it may also work. I think this a=
pproach is perhaps more &#8220;practical&#8221;: if we propose an architect=
ure and leave signaling for the future, nobody will
 believe this can work. If we begin with the architecture&#43;basic signali=
ng, we will have something that works from the beginning.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">What do you think?<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jose<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"ES" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">De:</span></b><span lang=
=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans=
-serif&quot;"> Muthu Arul Mozhi Perumal (mperumal) [<a href=3D"mailto:mperu=
mal@cisco.com">mailto:mperumal@cisco.com</a>]
<br>
<b>Enviado el:</b> martes, 22 de enero de 2013 5:34<br>
<b>Para:</b> FERNANDO PASCUAL BLANCO; <a href=3D"mailto:jsaldana@unizar.es"=
>jsaldana@unizar.es</a><br>
<b>CC:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> RE: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to =
discover a de-muxer<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hi Fernando,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Yes, I was referring to draft A. However, I am now thinkin=
g it might be better if we devote draft A for the use cases and the protoco=
l stack architecture, and write a new draft A-sig
 describing the negotiation procedures including automatic discovery/associ=
ation and capability exchange. That way we can progress them independently =
in parallel and potentially explore multiple negotiation procedures (in the=
 form of multiple drafts, if there
 is sufficient interest). In essence, I think we should separate out the us=
e cases and architecture from the solutions.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|1. The way a mux is instructed with the IP address (for e=
xample) of a demux.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|&nbsp; &nbsp;That procedure could be:
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|&nbsp;&nbsp; 1. Static (i.e. Configuration within the mux=
)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|&nbsp;&nbsp; 2. Dynamic (i.e. Instructed from a higher en=
tity like a policy manager)
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and could be (or not) desc=
ribed in draft C<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">On dynamic, I would also like to add mux discovering the d=
emux through negotiation -- this would be case when the mux sees a number o=
f flows going to the same destination but doesn't
 know if the destination is capable of demuxing.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Muthu<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> FERNANDO=
 PASCUAL BLANCO [<a href=3D"mailto:fpb@tid.es">mailto:fpb@tid.es</a>]
<br>
<b>Sent:</b> Monday, January 21, 2013 2:32 PM<br>
<b>To:</b> Muthu Arul Mozhi Perumal (mperumal); <a href=3D"mailto:jsaldana@=
unizar.es">
jsaldana@unizar.es</a><br>
<b>Cc:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Subject:</b> Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to=
 discover a de-muxer<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Muth=
u,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I agree=
 that a tunnel is not always needed. But when you say signaling doc, are yo=
u referring finally to the draft A? We agreed on addressing capabilities ne=
gotiation on that draft.&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Neverth=
eless, I think we should clarify two thinks:<o:p></o:p></span></p>
</div>
<ol start=3D"1" type=3D"1">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;mso-list:l1 level1 lfo3">
<span style=3D"font-size:10.5pt">The way a mux is instructed with the IP ad=
dress (for example) of a demux. That procedure could be:
<o:p></o:p></span></li></ol>
<ol start=3D"1" type=3D"1">
<ol start=3D"1" type=3D"1">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;mso-list:l1 level2 lfo3">
<span style=3D"font-size:10.5pt">Static (i.e. Configuration within the mux)=
<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"color:black;mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo3">
<span style=3D"font-size:10.5pt">Dynamic (i.e. Instructed from a higher ent=
ity like a policy manager) and could be (or not) described in draft C<o:p><=
/o:p></span></li></ol>
</ol>
<ol start=3D"2" type=3D"1">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;mso-list:l1 level1 lfo3">
<span style=3D"font-size:10.5pt">The capabilities negotiation: once a mux k=
nows the IP address of a demux can negotiate the capabilities of the differ=
ent layers (tunnel, multiplex and compression). This is also described at t=
he draft A.<o:p></o:p></span></li></ol>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Regards=
,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Fernand=
o Pascual Blanco<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Telef=
=F3nica Global Resources<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Network=
 Automation and Dynamization<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">TECHNOL=
OGY PEOPLE GROUP<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">F &#43;=
34913128779<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">M &#43;=
34682005168<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><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>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">&quot;'Muthu Arul Mozhi Perumal (mperumal) '&quot; =
&lt;<a href=3D"mailto:mperumal@cisco.com">mperumal@cisco.com</a>&gt;<br>
<b>Date: </b>lunes, 21 de enero de 2013 06:40<br>
<b>To: </b>Fernando Pascual Blanco &lt;<a href=3D"mailto:fpb@tid.es">fpb@ti=
d.es</a>&gt;, &quot;<a href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.e=
s</a>&quot; &lt;<a href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a=
>&gt;<br>
<b>Cc: </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>RE: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to=
 discover a de-muxer<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Fernando,</span><span style=3D"color:black"=
><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">|I=B4m sure we will find a consensus about tha=
t :).</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Sure..</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">|What Muthu proposes sounds interesting to me =
but, to be honest, I think TCMTF
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">|establishing should be quite similar to the e=
stablishing procedures of tunnels
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">|defined in draft A (L2TP, GRE&#8230;),</span>=
<span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">I agree the procedures for establishing the as=
sociation b/w the muxer and the de-muxer could be similar to those of estab=
lishing a tunnel. However, I would like us to
 avoid two assumptions:</span><span style=3D"color:black"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">1. The other end of a tunnel is always TCMTF c=
apable. I think this is more important when you already have a tunnel (say,=
 IPSec tunnel) and would like to perform TCMTF
 on the fly.</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">2. A tunnel is always needed for performing TC=
MTF. If we aren't doing any compression, but only multiplexing, the outermo=
st IP header would be intact and should suffice
 for routing the packets. There are satellite networks where reducing the p=
ackets per second (pps) for VoIP calls is more important -- they don't do a=
ny compression, but only multiplexing, and don't setup a tunnel as well. Fo=
r e.g:</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><a href=3D"http://www.cisco.com/web/strategy/d=
ocs/gov/aag_c45-697642_v2.pdf">http://www.cisco.com/web/strategy/docs/gov/a=
ag_c45-697642_v2.pdf</a></span><span style=3D"color:black"><o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><a href=3D"http://www.cisco.com/web/strategy/d=
ocs/gov/ip_multiplexing_agensler.pptx">http://www.cisco.com/web/strategy/do=
cs/gov/ip_multiplexing_agensler.pptx</a></span><span style=3D"color:black">=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Nevertheless, I think all this go into the sig=
naling doc. If we require capability negotiation, I think we can combine it=
 with the procedure for establishing the association
 b/w the muxer and the de-muxer. If we make capability negotiation as optio=
nal, we might want to keep those as separate procedures.</span><span style=
=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Muthu</span><span style=3D"color:black"><o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p>=
</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:black">From:</span></b><span sty=
le=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot=
;;color:black">
<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>On Behalf Of </b>FERNANDO PASCUAL BLANCO<br>
<b>Sent:</b> Wednesday, January 16, 2013 5:04 PM<br>
<b>To:</b> <a href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>; Mu=
thu Arul Mozhi Perumal (mperumal)<br>
<b>Cc:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Subject:</b> Re: [tcmtf] RV: TCMTF: Document A: mechanism for a muxer to=
 discover a de-muxer</span><span style=3D"color:black"><o:p></o:p></span></=
p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi Jose=
, Muthu,</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I=B4m s=
ure we will find a consensus about that :). What Muthu proposes sounds inte=
resting to me but, to be honest, I think TCMTF establishing should be quite=
 similar to the establishing procedures
 of tunnels defined in draft A (L2TP, GRE&#8230;), actually at network leve=
l TCMTF is a tunnel. Once established signaling will negotiate upper levels=
 (multiplexing and HC) to perform TCMTF (draft A).</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">What do=
 you think?</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Regards=
,</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Fernand=
o Pascual Blanco</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Telef=
=F3nica Global Resources</span><span style=3D"color:black"><o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Network=
 Automation and Dynamization</span><span style=3D"color:black"><o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">TECHNOL=
OGY PEOPLE GROUP</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">F &#43;=
34913128779</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">M &#43;=
34682005168</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><a href=
=3D"mailto:fpb@tid.es">fpb@tid.es</a></span><span style=3D"color:black"><o:=
p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span 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>mi=E9rcoles, 16 de enero de 2013 11:18<br>
<b>To: </b>&quot;'Muthu Arul Mozhi Perumal (mperumal) '&quot; &lt;<a href=
=3D"mailto:mperumal@cisco.com">mperumal@cisco.com</a>&gt;, Fernando Pascual=
 Blanco &lt;<a href=3D"mailto:fpb@tid.es">fpb@tid.es</a>&gt;<br>
<b>Cc: </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>RV: [tcmtf] TCMTF: Document A: mechanism for a muxer to dis=
cover a de-muxer<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoPlainText"><span style=3D"color:black">Fernando, Muthu, ever=
yone,<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Since there is no con=
sensus about this, I think we should carry on with the debate. Do you think=
 the mechanism would be very complicated? Any new ideas?:<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">- *<b>dynamically est=
ablishing, modifying and releasing tunnels</b>*<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">#1. A *<b>mechanism f=
or a muxer to discover a de-muxer (and vice versa)</b>*.<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">There is still no con=
sensus here:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Fernando: &#8220;Regarding #1, to be honest, I am not completely su=
re of the need to specify a mechanism to discover muxes and demuxes between=
 them. I think those kind of mechanisms have
 more sense in local environments but I=B4m not sure if it applies here. At=
 least at the beginning this associations can be done manually.&#8221;<o:p>=
</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Muthu: &#8220;I think it is the opposite -- in local environments y=
ou can provision/associate them manually. However, in a multi-vendor enviro=
nment over the Internet this should happen automatically.&#8221;
<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt;text-indent:35.4pt"><=
span style=3D"color:black">&#8220;#1 needs to be specified.&#8221;<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">&nbsp;</sp=
an><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">&nbsp;</sp=
an><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">Best regar=
ds,</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D"><br>
Jose</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:#1F497D">&nbsp;</sp=
an><span style=3D"color:black"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span lang=3D"ES" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black">De:</span></b=
><span lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;=
,&quot;sans-serif&quot;;color:black"><a href=3D"mailto:tcmtf-bounces@ietf.o=
rg">tcmtf-bounces@ietf.org</a>
 [<a href=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</=
a>] <b>En nombre de
</b>Jose Saldana<br>
<b>Enviado el:</b> martes, 15 de enero de 2013 11:56<br>
<b>Para:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tcmtf] TCMTF: Document A discussion: content and charter</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:black">&nbsp;</span=
><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Document (A) refers to t=
he main TCMTF draft, currently in
<a href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http=
://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">1.- Content of the Docum=
ent<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Currently it contains th=
e description of the question and the protocols which could be used on each=
 layer (tunneling, compressing, multiplexing). It says that the signaling i=
ssues would be that of each protocol.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">There is consensus (I th=
ink) about this: we should include some signaling issues. The question is: =
What should we include in Draft A and what in Draft C?<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">- *<b>Auto-negotiation</=
b>* Negotiation mechanisms to decide the options at each layer (compression=
, multiplexing and tunneling) between mux and demux. Perhaps the mux has RO=
HC, ECRTP and IPHC, and the demux only
 has ECRTP and IPHC, so the two machines will have to negotiate in order to=
 decide which compression protocol use.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">This should be included =
in (A). I think there is consensus about this:<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span style=3D"color:bl=
ack">Juan Antonio: &#8220;The first kind of signaling (&quot;auto-negotiati=
on&quot;) is needed from the beginning if we don't want an extremely static=
 protocol and therefore possibly difficult to get it working,
 especially when in most of cases the peers belong to different entities/co=
mpanies.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">Dan: &#8220;We need that -- it is capabilities negotiation.&nbsp; =
It is needed because the protocol will fail if one side mistakenly thinks t=
he other side has certain functionality, and because
 we will want to add some fancy new compression in the year 2020 and will n=
eed to negotiate it.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">Fernando: &#8220;I also agree with the idea of including the mux-d=
emux signaling within the draft A (as Dan said, they are capabilities negot=
iation). This draft should be able to get two
 boxes with TCMTF fully working between them. Under my point of view this i=
ncludes the definition of the capabilities in each node and the negotiation=
 of that capabilities.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">Does this mean that D=
ocument (A) will no longer be a Best Current Practice? I think so.<o:p></o:=
p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">- *<b>dynamically est=
ablishing, modifying and releasing tunnels</b>*<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">#1. A *<b>mechanism f=
or a muxer to discover a de-muxer (and vice versa)</b>*.<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">There is still no con=
sensus here:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Fernando: &#8220;Regarding #1, to be honest, I am not completely su=
re of the need to specify a mechanism to discover muxes and demuxes between=
 them. I think those kind of mechanisms have
 more sense in local environments but I=B4m not sure if it applies here. At=
 least at the beginning this associations can be done manually.&#8221;<o:p>=
</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt"><span style=3D"color=
:black">Muthu: &#8220;I think it is the opposite -- in local environments y=
ou can provision/associate them manually. However, in a multi-vendor enviro=
nment over the Internet this should happen automatically.&#8221;
<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.4pt;text-indent:35.4pt"><=
span style=3D"color:black">&#8220;#1 needs to be specified.&#8221;<o:p></o:=
p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:35.25pt"><span style=3D"colo=
r:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">#2. A mechanism to *<=
b>elect an optimal muxer and a de-muxer when there are more than one muxer/=
de-muxer for a flow</b>*.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">We agree: This can wa=
it for Document (C).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ferna=
ndo: &#8220;#2 is more related to the higher entity that has to decide whet=
her a flow should be TCMTFed or not, and under my point of view it can be a=
ddressed in a different draft.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu=
: &#8220;#2 can be added later.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">3. A mechanism to *<b=
>setup/release a tunnel b/w a muxer and a de-muxer</b>*.<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">We agree: This has to=
 be included in (A).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ferna=
ndo &#8220;#3 I think should be included in the draft A, since it is a mech=
anism within the TFMTF protocol itself.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu=
: &#8220;#3 many not require much specification.&#8221;<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span style=3D"color:black">&nbsp;<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span style=3D"color:black">2.- Should we include=
 it in the Charter now?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Of course, Document (A) =
should be in the charter.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Best regards,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Jose<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"color:black">&nbsp;</span=
><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">&nbsp;<=
/span><span style=3D"color:black"><o:p></o:p></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;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;;color:gray"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span style=3D"color:black"><o:p></o:p=
></span></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></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;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;;color:gray"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/=
ES/PAGINAS/disclaimer.aspx</a></span><span style=3D"font-size:10.5pt;color:=
black"><o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>

--_000_E721D8C6A2E1544DB2DEBC313AF54DE223FDC598xmbrcdx02ciscoc_--

From jsaldana@unizar.es  Tue Jan 22 02:14:01 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FF9021F86D8 for <tcmtf@ietfa.amsl.com>; Tue, 22 Jan 2013 02:14:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.548
X-Spam-Level: 
X-Spam-Status: No, score=-6.548 tagged_above=-999 required=5 tests=[AWL=0.050,  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 VdKYmh8XcVum for <tcmtf@ietfa.amsl.com>; Tue, 22 Jan 2013 02:13:59 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 8CBD221F8644 for <tcmtf@ietf.org>; Tue, 22 Jan 2013 02:13:58 -0800 (PST)
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 r0MADstR015165 for <tcmtf@ietf.org>; Tue, 22 Jan 2013 11:13:55 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Tue, 22 Jan 2013 11:14:04 +0100
Organization: Universidad de Zaragoza
Message-ID: <00c301cdf889$34d03240$9e7096c0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C4_01CDF891.96949A40"
X-Mailer: Microsoft Outlook 14.0
Content-language: es
Thread-index: Ac34e6crrrHSASDNQi6MsL1R3pPzaQ==
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] TCMTF: Document A discussion: content and charter version 2
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, 22 Jan 2013 10:14:01 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00C4_01CDF891.96949A40
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

After the discussion about what to include in Document A, and what signaling
issues we can leave to Document C, I think we could proceed this way:

 

- Document A will only include the things necessary in order to have a
"working" protocol (not too-static, as Juan Antonio says)

- Document C would add new signaling functionalities to TCMTF. It would not
be explicitly included in the Charter now.

 

The content of (A) would be then:

 

1.- Content of the Document

 

Currently it contains the description of the question and the protocols
which could be used on each layer (tunneling, compressing, multiplexing). It
says that the signaling issues would be that of each protocol.

 

There is consensus (I think) about this: we should include some signaling
issues. The question is: What should we include in Draft A and what in Draft
C?

 

- *Auto-negotiation* Negotiation mechanisms to decide the options at each
layer (compression, multiplexing and tunneling) between mux and demux.
Perhaps the mux has ROHC, ECRTP and IPHC, and the demux only has ECRTP and
IPHC, so the two machines will have to negotiate in order to decide which
compression protocol use.

 

This should be included in (A). I think there is consensus about this:

Juan Antonio: "The first kind of signaling ("auto-negotiation") is needed
from the beginning if we don't want an extremely static protocol and
therefore possibly difficult to get it working, especially when in most of
cases the peers belong to different entities/companies."

 

Dan: "We need that -- it is capabilities negotiation.  It is needed because
the protocol will fail if one side mistakenly thinks the other side has
certain functionality, and because we will want to add some fancy new
compression in the year 2020 and will need to negotiate it."

 

Fernando: "I also agree with the idea of including the mux-demux signaling
within the draft A (as Dan said, they are capabilities negotiation). This
draft should be able to get two boxes with TCMTF fully working between them.
Under my point of view this includes the definition of the capabilities in
each node and the negotiation of that capabilities."

 

Does this mean that Document (A) will no longer be a Best Current Practice?
I think so.

 

 

- *dynamically establishing, modifying and releasing tunnels*

 

#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.

 

We can leave this for Document (C)

 

                Muthu: "(.) and I agree we should begin with the
architecture + basic signaling."

Fernando: "I think TCMTF establishing should be quite similar to the
establishing procedures of tunnels defined in draft A (L2TP, GRE.), actually
at network level TCMTF is a tunnel. Once established signaling will
negotiate upper levels (multiplexing and HC) to perform TCMTF (draft A)."

 

#2. A mechanism to *elect an optimal muxer and a de-muxer when there are
more than one muxer/de-muxer for a flow*.

 

We agree: This can wait for Document (C).

 

                Fernando: "#2 is more related to the higher entity that has
to decide whether a flow should be TCMTFed or not, and under my point of
view it can be addressed in a different draft."

                Muthu: "#2 can be added later."

 

 

3. A mechanism to *setup/release a tunnel b/w a muxer and a de-muxer*.

 

We agree: This has to be included in (A).

 

                Fernando "#3 I think should be included in the draft A,
since it is a mechanism within the TFMTF protocol itself."

                Muthu: "#3 many not require much specification."

 

 

 

2.- Should we include it in the Charter now?

 

Of course, Document (A) should be in the charter.

 

 

Best regards,

 

Jose

 


------=_NextPart_000_00C4_01CDF891.96949A40
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:"Calibri","sans-serif";}
span.EstiloCorreo19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>After the discussion about what to include in Document A, =
and what signaling issues we can leave to Document C, I think we could =
proceed this way:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- Document A will only include the things necessary in =
order to have a &#8220;working&#8221; protocol (not too-static, as Juan =
Antonio says)<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- Document C would add new signaling functionalities to =
TCMTF. It would not be explicitly included in the Charter =
now.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>The content of (A) would be then:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>1.- Content of the =
Document<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Currently it contains the description of the question and =
the protocols which could be used on each layer (tunneling, compressing, =
multiplexing). It says that the signaling issues would be that of each =
protocol.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>There is consensus (I think) about this: we should include =
some signaling issues. The question is: What should we include in Draft =
A and what in Draft C?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>- *<b>Auto-negotiation</b>* Negotiation mechanisms to =
decide the options at each layer (compression, multiplexing and =
tunneling) between mux and demux. Perhaps the mux has ROHC, ECRTP and =
IPHC, and the demux only has ECRTP and IPHC, so the two machines will =
have to negotiate in order to decide which compression protocol =
use.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This should be included in (A). I think there is consensus =
about this:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:35.4pt'><span lang=3DEN-US>Juan Antonio: &#8220;The =
first kind of signaling (&quot;auto-negotiation&quot;) is needed from =
the beginning if we don't want an extremely static protocol and =
therefore possibly difficult to get it working, especially when in most =
of cases the peers belong to different =
entities/companies.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US>Dan: &#8220;We need that -- it is capabilities =
negotiation.&nbsp; It is needed because the protocol will fail if one =
side mistakenly thinks the other side has certain functionality, and =
because we will want to add some fancy new compression in the year 2020 =
and will need to negotiate it.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:35.25pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span lang=3DEN-US>Fernando: &#8220;I also =
agree with the idea of including the mux-demux signaling within the =
draft A (as Dan said, they are capabilities negotiation). This draft =
should be able to get two boxes with TCMTF fully working between them. =
Under my point of view this includes the definition of the capabilities =
in each node and the negotiation of that =
capabilities.&#8221;<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>Does this mean that Document (A) will no longer be a Best =
Current Practice? I think so.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>- *<b>dynamically establishing, =
modifying and releasing tunnels</b>*<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. A *<b>mechanism for a muxer =
to discover a de-muxer (and vice versa)</b>*.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>We can leave this for Document =
(C)<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.25pt'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span lang=3DEN-US>Muthu: =
&#8220;(&#8230;) and I agree we should begin with the architecture + =
basic signaling.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:35.4pt'><span lang=3DEN-US>Fernando: &#8220;I think =
TCMTF establishing should be quite similar to the establishing =
procedures of tunnels defined in draft A (L2TP, GRE&#8230;), actually at =
network level TCMTF is a tunnel. Once established signaling will =
negotiate upper levels (multiplexing and HC) to perform TCMTF (draft =
A).&#8221;<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. A mechanism to *<b>elect an optimal muxer and a =
de-muxer when there are more than one muxer/de-muxer for a =
flow</b>*.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>We agree: This can wait for Document =
(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>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fernando: &#8220;#2 is more related to =
the higher entity that has to decide whether a flow should be TCMTFed or =
not, and under my point of view it can be addressed in a different =
draft.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu: &#8220;#2 can be added =
later.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>3. A mechanism to *<b>setup/release a tunnel b/w a muxer =
and a de-muxer</b>*.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>We agree: This has to be included in =
(A).<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>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Fernando &#8220;#3 I think should be =
included in the draft A, since it is a mechanism within the TFMTF =
protocol itself.&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Muthu: &#8220;#3 many not require much =
specification.&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>2.- Should we include it in the Charter =
now?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Of course, Document (A) should be in the =
charter.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Best regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00C4_01CDF891.96949A40--


From jsaldana@unizar.es  Tue Jan 22 02:16:32 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7909A21F85A4 for <tcmtf@ietfa.amsl.com>; Tue, 22 Jan 2013 02:16:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.561
X-Spam-Level: 
X-Spam-Status: No, score=-6.561 tagged_above=-999 required=5 tests=[AWL=0.038,  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 iNUM9XEvMEHp for <tcmtf@ietfa.amsl.com>; Tue, 22 Jan 2013 02:16:32 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id A702821F85AF for <tcmtf@ietf.org>; Tue, 22 Jan 2013 02:16:31 -0800 (PST)
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 r0MAGOEr014657 for <tcmtf@ietf.org>; Tue, 22 Jan 2013 11:16:24 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Tue, 22 Jan 2013 11:16:35 +0100
Organization: Universidad de Zaragoza
Message-ID: <00c801cdf889$8f091ec0$ad1b5c40$@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
Content-language: es
Thread-index: Ac34iYzLof1H6EEYSiCzJylEjVfVOQ==
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf]  TCMTF: Document C discussion: content and charter v2
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, 22 Jan 2013 10:16:32 -0000

Here is the new version of the content of Document C


Document (C) may refer to a new document about signaling

1.- Content of the Document

#1. A *mechanism for a muxer to discover a de-muxer (and vice versa)*.

We agree: This can be deployed in Document C.


#2. A mechanism to *elect an optimal muxer and a de-muxer when there are
more than one muxer/de-muxer for a flow*.

We agree: This can be deployed in Document C.

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Fernando: =93#2 is more =
related to the higher entity that has
to decide whether a flow should be TCMTFed or not, and under my point of
view it can be addressed in a different draft.=94
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Muthu: =93#2 can be added =
later.=94


2.- Should we include it in the Charter now?

I think we shouldn=92t include this in the charter as an objective. It =
can be
included in one of the last paragraphs.

Best regards,

Jose



From mramalho@cisco.com  Tue Jan 22 07:41:34 2013
Return-Path: <mramalho@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74A6621F8A3E for <tcmtf@ietfa.amsl.com>; Tue, 22 Jan 2013 07:41:34 -0800 (PST)
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_SUMOF=5, RCVD_IN_DNSWL_HI=-8]
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 C161DEl4fn9J for <tcmtf@ietfa.amsl.com>; Tue, 22 Jan 2013 07:41:32 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 3FABB21F8945 for <tcmtf@ietf.org>; Tue, 22 Jan 2013 07:41:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=34862; q=dns/txt; s=iport; t=1358869292; x=1360078892; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=MQvqti9NAxs95PJLYUpMymHurUWckfpw/TgVd8LUqzI=; b=FroNgz4VjDYmrs+1mwPOz+v3AR2AZbwnt+jk9dhc7LboJWQzRXB7cjOR y9IJuS2W9M2bbIvrTK77z+vB6ShsAjNzZdiAShpeYeFeQ589BnM5ts/Ro JbfLGTrvRMS9pwIbZrvMn0CFSll2dvUjMsS6sOTMsKeZF95lXCy8fK5Om o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAHuy/lCtJXG8/2dsb2JhbABEDoY3tm9+FnOCHgEBAQMBAQEBFwkROgUGBQcEAgEIEQQBAQECAgYZBAMCAgIlCxQBCAgCBAENBQgTh2wDCQYMqiuCQIZMBYhqgSOLUAsKAYMaMmEDklmET48tgjc+gWYBBgIXHg
X-IronPort-AV: E=Sophos;i="4.84,515,1355097600"; d="scan'208";a="166177299"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-7.cisco.com with ESMTP; 22 Jan 2013 15:41:31 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r0MFfVeI027066 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Jan 2013 15:41:31 GMT
Received: from xmb-rcd-x12.cisco.com ([169.254.2.163]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.02.0318.004; Tue, 22 Jan 2013 09:41:30 -0600
From: "Michael Ramalho (mramalho)" <mramalho@cisco.com>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Thread-Topic: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
Thread-Index: AQHN9+U/YPKPciLAn0KqGVk92auPL5hVehhA
Date: Tue, 22 Jan 2013 15:41:30 +0000
Message-ID: <D21571530BF9644D9A443D6BD95B9103154C52CB@xmb-rcd-x12.cisco.com>
References: <009701cdf4ac$8af49750$a0ddc5f0$@unizar.es> <F5EDC35DF914C1428C28E149F10463A2689D3F12@EX10-MB2-MAD.hi.inet> <009f01cdf4b9$aca39060$05eab120$@unizar.es>	<50F92318.30809@erg.abdn.ac.uk> <003601cdf7db$d652edf0$82f8c9d0$@unizar.es> <50FD5347.5000106@erg.abdn.ac.uk>
In-Reply-To: <50FD5347.5000106@erg.abdn.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.168.119]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Draft: Maximum Tolerable Delays when using Tunneling Compressed Multiplexed Traffic Flows
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 15:41:34 -0000

QWxsLA0KDQpBbHRob3VnaCBpdCBpcyBoYXJkIHRvIHBhcnNlIHdoby1zYWlkLXdoYXQgaW4gdGhl
IHRocmVhZCBiZWxvdyAuLi4gSSB0aGluayBHb3JyeSBhc2tlZCB0aGUgcXVlc3Rpb246DQoNCiIg
SSdtIGludGVyZXN0ZWQgdG8ganVkZ2luZyBpZiB0aGVyZSBhcmUgY2FzZXMgd2hlcmUgYWdncmVn
YXRpbmcgc21hbGwgDQpmbG93cyAod2l0aCBtaW5pbWFsIG9yIG5vIENDIC0gYXMgaW4gVm9JUCkg
Y2FuIHJlc3VsdCBpbiBhbiBhZ2dyZWdhdGUgDQp0dW5uZWwgdGhhdCBjb21wZXRlcyB1bmZhaXJs
eSB3aXRoIGVzdGFibGlzaGVkIGZsb3dzIHRoYXQgdXNlIENDLiINCg0KVG8gbWFrZSB0aGUgYW5z
d2VyIHNpbXBsZSwgY29uc2lkZXIgdGhlIGNhc2Ugd2hlcmUgdGhlcmUgYXJlIG9ubHkgdHdvIHR5
cGVzIG9mIGZsb3dzIC0gVENQIChyZXByZXNlbnRpbmcgYWxsIENDIGZsb3dzIGhlcmUpIGFuZCBW
b0lQIChyZXByZXNlbnRpbmcgQ0JSIG9yIG5vLUNDIGZsb3dzKS4NCg0KTm93IGNvbnNpZGVyIGEg
Ym90dGxlbmVjayBsaW5rIGZpbGxlZCB3aXRoIEFHR1JFR0FURVMgb2YgYm90aCB0eXBlcyBvZiBm
bG93cy4gRGVmaW5lIFN1bV9DQyBhcyB0aGUgc3VtIG9mIHRoZSBhZ2dyZWdhdGVkIFRDUCBmbG93
cyBhbmQgU1VNX1ZvSVAgYXMgdGhlIHN1bSBvZiB0aGUgYWdncmVnYXRlZCBuby1DQyBmbG93cy4N
Cg0KU28gbG9uZyB0aGUgYm90dGxlbmVjayBsaW5rIGhhcyBCVyAoQldfVG90YWwpIGdyZWF0ZXIg
dGhhbiBTVU1fVm9JUCAuLi4gdGhlIGluZGl2aWR1YWwgVENQIGZsb3dzIHdpbGwgZGl2aWRlIHdo
YXQgaXMgbGVmdCBvdmVyLiBOb3RlIHRoYXQgdGhlIGluZGl2aWR1YWwgVm9JUCBmbG93cyBhcmUg
InVuZmFpciIsIHRoZXkgZG9uJ3QgY2FyZSBhYm91dCB0aGVpciBzaGFyZSBvZiB0aGUgYm90dGxl
bmVjayBCVy4NCg0KSWRlYWxseSBlYWNoIFRDUCBmbG93IHdvdWxkIGdldCBbQldfVG90YWwtU1VN
X1ZvSVBdL04sIHdoZW4gdGhlcmUgYXJlIE4gVENQIGZsb3dzIC4uLiBidXQgaXQgZ2V0cyBkaWNl
eSB3aGVuIHRoZSByZW1haW5pbmcgQlcgaXMgc21hbGwgcmVsYXRpdmUgdG8gQldfVG90YWwgKG1h
bnkgYXJlIHN0YXJ2ZWQpLg0KDQpTbyAuLi4gc28gbG9uZyBhcyBTVU1fVm9JUCBpcyBsZXNzIHRo
YW4gdGhlIHN1bSBvZiB0aGUgaW5kaXZpZHVhbCBWb0lQIGZsb3dzICh3ZSBoYWQgY29tcHJlc3Np
b24pIC4uLiB3ZSBoYXZlIG5vdCBtYWRlIHRoZSBzaXR1YXRpb24gd29yc2UgZm9yIHRoZSByZW1h
aW5pbmcgVENQIGZsb3dzIC4uLiBFWENFUFQgdGhhdCB3ZSBoYXZlIGFkZGVkIHNvbWUgZGVsYXkg
dG8gdGhlIFRDUCBmbG93cy4NCg0KQW5kIHRoaXMgb25seSBodXJ0cyB0aGUgVENQIGZsb3dzIHRv
IHRoZSBleHRlbnQgdGhhdCB0aGV5IHdlcmUgY3duZCBsaW1pdGVkIChpLmUuLCBoYWQgZW5vdWdo
IGRhdGEgdG8gc2VuZCBzbyB0aGF0IHRoZWlyIGluZGl2aWR1YWwgQ0Mgd2VyZSBsaW1pdGluZyB0
aGUgaW5kaXZpZHVhbCByYXRlcyAuLi4gdGhpcyBpcyBOT1QgdGhlIHVzdWFsIGNhc2UgZm9yIGdh
bWluZykuDQoNCkkgaG9wZSB0aGlzIGhlbHBzLg0KDQpNaWNoYWVsIFJhbWFsaG8NCg0KLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IHRjbXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0
bzp0Y210Zi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgR29ycnkgRmFpcmh1cnN0DQpT
ZW50OiBNb25kYXksIEphbnVhcnkgMjEsIDIwMTMgOTo0MCBBTQ0KVG86IGpzYWxkYW5hQHVuaXph
ci5lcw0KQ2M6IHRjbXRmQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW3RjbXRmXSBEcmFmdDogTWF4
aW11bSBUb2xlcmFibGUgRGVsYXlzIHdoZW4gdXNpbmcgVHVubmVsaW5nIENvbXByZXNzZWQgTXVs
dGlwbGV4ZWQgVHJhZmZpYyBGbG93cw0KDQpKb3NlLCBzZWUgYmVsb3cuDQoNCkdvcnJ5DQoNCk9u
IDIxLzAxLzIwMTMgMTM6MzMsIEpvc2UgU2FsZGFuYSB3cm90ZToNCj4gR29ycnksDQo+DQo+IFJl
Z2FyZGluZyB5b3VyIHF1ZXN0aW9uOg0KPj4gUlRUIGFuZC9vciBjb250cm9sIGZlZWRiYWNrIHdv
dWxkIGJlIHJlYWxseSBoZWxwZnVsIGluIGVzdGFibGlzaGluZyBhIA0KPj4gY29uZ2VzdGlvbiBj
b250cm9sIG9yIGNpcmN1aXQtYnJlYWtlciBmdW5jdGlvbiB0byBlbnN1cmUgdGhlIHRyYWZmaWMg
DQo+PiBkb2VzIG5vdCBjYXVzZSBjb25nZXN0aW9uIGNvbGxhcHNlLiBIYXZlIHlvdSB0aG91Z2h0
IGFib3V0IHRoaXM/DQo+DQo+IElmIEkgdW5kZXJzdGFuZCB3ZWxsLCB5b3UgYXJlIHRhbGtpbmcg
YWJvdXQgdXNpbmcgUlRUIG9yIGZlZWRiYWNrIG5vdCBvbmx5IGZvciBzZWxlY3RpbmcgYW4gYWRl
cXVhdGUgbXVsdGlwbGV4aW5nIHBlcmlvZCwgYnV0IGFsc28gZm9yIGNvbmdlc3Rpb24gY29udHJv
bC4gSXMgdGhpcyB0cnVlPw0KPg0KTXkgcXVlcnkgd2FzIHdoZXRoZXIgdGhlIE1VWCBzaG91bGQg
aW1wbGVtZW50IHNvbWUgcmF0ZSBsaW1pdCBvbiB0aGUgYWdncmVnYXRlIG11bHRpcGxleGVkIGZs
b3cgLSBnaXZlbiB0aGlzIGNhbiB0aGVuIHJlc3VsdCBpbiBhIGhpZ2hlciByYXRlIGZsb3cgd2l0
aCBkaWZmZXJlbnQgY2hhcmFjdGVyaXN0aWNzIHRvIHRoZSBvcmlnaW5hbCBsb3ctcmF0ZSBmbG93
cy4NCg0KPiBUaGUgcXVlc3Rpb24gaXMgdGhhdCBUQ01URiBpcyBkZXNpZ25lZCBmb3IgdHJhZmZp
YyBzYXZpbmcsIHNvIEkgdGhpbmsgdGhlIGNhdXNlIG9mIHRoZSBjb25nZXN0aW9uIHdvdWxkIG5v
dCBiZSBUQ01URiBpdHNlbGYsIGJ1dCBhIGhpZ2ggYW1vdW50IG9mIGZsb3dzLCBvciBhIGhpZ2gg
YmFuZHdpZHRoIHRvIGFnZ3JlZ2F0ZS4gU28gcGVyaGFwcyBpbiB0aGF0IGNhc2UgdGhlIGZsb3dz
IHdoaWNoIGFyZSBiZWluZyBtdWx0aXBsZXhlZCB3aWxsIGhhdmUgdGhlaXIgb3duIGVuZC10by1l
bmQgY29uZ2VzdGlvbiBjb250cm9sIG1lY2hhbmlzbXMuDQo+DQpPSywgaWYgYWxsIHRoZSBmbG93
cyBoYWQgQ0MsIHRoaXMgd291bGQgYmUgbGVzcyBvZiBhbiBpc3N1ZS4gSWYgZWFjaCBmbG93IGlz
IGluZGl2aWR1YWxseSBzbWFsbCB3aXRob3V0IENDIChvciB1bmxpbWl0ZWQgYnkgQ0MsIGUuZy4g
YmVjYXVzZSBpdCBzZW5kcyBmZXdlciB0aGFuIG9uZSBwYWNrZXQgcGVyIFJUVCksIHRoZW4gYWdn
cmVnYXRpbmcgdGhlc2UgY291bGQgbWFrZSBhIGxhcmdlIGZsb3cgdGhhdCBoYXMgbGl0dGxlIEND
LiBUaGF0IHNlZW1zIG1vcmUgb2YgYW4gaW4gaXNzdWUgdGhhbiBoYXZpbmcgbG90cyBvZiBzbWFs
bCBmbG93cy4gVGhlIGFnZ3JlZ2F0ZSBmbG93IHdvdWxkIGxpa2VseSBiZSBtb3JlIGJ1cnN0eSBm
b3IgaW5zdGFuY2UuDQoNCj4gQW4gZXhhbXBsZTogeW91IGFyZSBncm91cGluZyBhIGxvdCBvZiBU
Q1AgZmxvd3Mgb2YgYW4gTU1PUlBHIGdhbWUuIElmIGEgYm90dGxlbmVjayBhcHBlYXJzIGFuZCBk
ZWxheXMgcmlzZSwgVENQIG1lY2hhbmlzbXMgd2lsbCBhY3QgYW5kIHJlZHVjZSB0aGUgcmF0ZS4N
Cj4NClllcy4gRXNwZWNpYWxseSBpZiB0aGUgZmxvdyBoYXMgYXBwcmVjaWFibGUgcGFja2V0cy9y
dHQuDQoNCj4gQ2FuIHdlIGZpbmQgYW4gZXhhbXBsZSBpbiB3aGljaCBpbnRlcnJ1cHRpbmcgdGhl
IHVzZSBvZiBUQ01URiBhbmQgc2VuZGluZyBuYXRpdmUgcGFja2V0cyBpbnN0ZWFkIHdpbGwgYmUg
bmVjZXNzYXJ5Pw0KID4gUGVyaGFwcyB0aGlzIG9uZTogaWYgeW91IGFyZSB1c2luZyBUQ01URiBm
b3IgcmVkdWNpbmcgcHBzIGFuZCBub3QgYmFuZHdpZHRoLg0KPiBUaGlzIGNhbiBoYXBwZW4gd2l0
aCBWb0lQIGluIGEgc2F0ZWxsaXRlIG5ldHdvcms6IHlvdSBncm91cCBwYWNrZXRzIHdpdGhvdXQg
aGVhZGVyIGNvbXByZXNzaW9uLg0KID4gWW91IHJlZHVjZSBwcHMgYW5kIHlvdSBpbmNyZWFzZSBi
YW5kd2lkdGguDQogPg0KSSB3b3VsZCBzdWdnZXN0IHRoaXMgaXMgYSBzdWJuZXR3b3JrIHByb2Js
ZW0sIG5vdCBnZW5lcmFsIEludGVybmV0IHByb2JsZW0gLSBpdCBzZWVtcyBsaWtlIGEgZm9ybSBv
ZiBsaW5rIGVuY2FwYXVzbGF0aW9uL0hDIG9wdGltaXNhdGlvbi4NCg0KPiBIb3dldmVyLCBJIHRo
aW5rIGJhbmR3aWR0aCBpbmNyZWFzZSBpcyByZWFsbHkgc21hbGw6IDI1IGJ5dGVzIGZvciB0aGUg
dHVubmVsIGhlYWRlciBhbmQgdHdvIG1vcmUgYnl0ZXMgZm9yIHNlcGFyYXRpbmcgZWFjaCBtdWx0
aXBsZXhlZCBwYWNrZXQuDQogPiBJZiB5b3UgYXJlIGdyb3VwaW5nIDEwIFZvSVAgcGFja2V0cyAo
MjAgSVAvOCBVRFAvMTIgUlRQLzIwIHBheWxvYWQpLCB0aGUgdHVubmVsIG5lZWRzIDI1ICsgMTB4
KDIrNjApPTY0NWJ5dGVzLg0KID4gPiBOYXRpdmUgdHJhZmZpYyB3b3VsZCBuZWVkIDEweDYwPTYw
MCBieXRlcy4gU28gYmFuZHdpZHRoIGluY3JlYXNlIGlzIDcuNSUuIElmIHlvdSBncm91cCAyMCBw
YWNrZXRzLCBiYW5kd2lkdGggaW5jcmVhc2UgaXMgMTI2NS8xMjAwPSA1JQ0KPg0KSSB0aGluayB0
aGUgZXh0cmEgYnl0ZSBvdmVyaGVhZCBpcyBub3Qgc2lnbmlmaWNhbnQuIFR1bm5lbCBlbmNwYXMg
aW4gdGhlIENPUkUgaXMgY29tbW9uLCB1c2luZyBHUkUsIGV0YyBhbmQgYWRkcyBtb3JlIG92ZXJo
ZWFkLg0KDQoNCj4gR29ycnksIHdhcyB0aGlzIHlvdXIgaWRlYT8gQXJlIHlvdSB0aGlua2luZyBh
Ym91dCBvdGhlciBzY2VuYXJpb3MgaW4gd2hpY2ggaW50ZXJydXB0aW5nIFRDTVRGIGNhbiBiZSBp
bnRlcmVzdGluZz8NCj4NCkknbSBpbnRlcmVzdGVkIHRvIGp1ZGdpbmcgaWYgdGhlcmUgYXJlIGNh
c2VzIHdoZXJlIGFnZ3JlZ2F0aW5nIHNtYWxsIA0KZmxvd3MgKHdpdGggbWluaW1hbCBvciBubyBD
QyAtIGFzIGluIFZvSVApIGNhbiByZXN1bHQgaW4gYW4gYWdncmVnYXRlIA0KdHVubmVsIHRoYXQg
Y29tcGV0ZXMgdW5mYWlybHkgd2l0aCBlc3RhYmxpc2hlZCBmbG93cyB0aGF0IHVzZSBDQy4NCg0K
PiBUaGFua3MgYSBsb3QsDQo+DQo+IEpvc2UNCj4NCj4+IC0tLS0tTWVuc2FqZSBvcmlnaW5hbC0t
LS0tDQo+PiBEZTogdGNtdGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnRjbXRmLWJvdW5jZXNA
aWV0Zi5vcmddIEVuIG5vbWJyZSBkZQ0KPj4gR29ycnkgRmFpcmh1cnN0DQo+PiBFbnZpYWRvIGVs
OiB2aWVybmVzLCAxOCBkZSBlbmVybyBkZSAyMDEzIDExOjI1DQo+PiBQYXJhOiB0Y210ZkBpZXRm
Lm9yZw0KPj4gQXN1bnRvOiBSZTogW3RjbXRmXSBEcmFmdDogTWF4aW11bSBUb2xlcmFibGUgRGVs
YXlzIHdoZW4gdXNpbmcgVHVubmVsaW5nDQo+PiBDb21wcmVzc2VkIE11bHRpcGxleGVkIFRyYWZm
aWMgRmxvd3MNCj4+DQo+PiBJZiB0aGlzIGlzIGdvaW5nIHRvIGJlIHVzZWQgaW4gdGhlIGdlbmVy
YWwgSW50ZXJuZXQsIHRoZW4gd2UgbmVlZCB0byBkZWNpZGUNCj4+IHdoZXRoZXIgdGhlcmUgaXMg
b25lLXdheSBvciB0d28td2F5IGNvbnRyb2wgY29ubmVjdGl2aXR5LiBUaGlzIHdpbGwNCj4+IGRl
dGVybWluZSB0aGUgY29uc3RyYWludHMgZnJvbSBhIGNvbmdlc3Rpb24gY29udHJvbCBwZXJzcGVj
dGl2ZS4NCj4+IFJUVCBhbmQvb3IgY29udHJvbCBmZWVkYmFjayB3b3VsZCBiZSByZWFsbHkgaGVs
cGZ1bCBpbiBlc3RhYmxpc2hpbmcgYQ0KPj4gY29uZ2VzdGlvbiBjb250cm9sIG9yIGNpcmN1aXQt
YnJlYWtlciBmdW5jdGlvbiB0byBlbnN1cmUgdGhlIHRyYWZmaWMgZG9lcyBub3QNCj4+IGNhdXNl
IGNvbmdlc3Rpb24gY29sbGFwc2UuIEhhdmUgeW91IHRob3VnaHQgYWJvdXQgdGhpcz8NCj4+DQo+
PiBHb3JyeQ0KPj4NCj4+DQo+Pg0KPj4gT24gMTcvMDEvMjAxMyAxMzo1MCwgSm9zZSBTYWxkYW5h
IHdyb3RlOg0KPj4+IEluIGFkZGl0aW9uLCBwZXJoYXBzIHdlIGFyZSB0b28gZm9jdXNlZCBvbiBv
bmxpbmUgZ2FtZXMgYW5kIFZvSVANCj4+IHNlcnZpY2VzLiBUaGVyZSBhcmUgb3RoZXIgc2Vydmlj
ZXMgd2hpY2ggYXJlIG9uZS13YXk6IHBlcmhhcHMgTTJNDQo+PiBjb21tdW5pY2F0aW9ucyBkbyBu
b3QgcmVxdWlyZSBhIHR3byB3YXkgY29tbXVuaWNhdGlvbi4gV2UgY2FuIHRoaW5rDQo+PiBhYm91
dCBhIG51bWJlciBvZiBzZW5zb3JzIHNlbmRpbmcgdGhlaXIgbWVhc3VyZW1lbnRzIHRvIGEgY2Vu
dHJhbCBzZXJ2ZXIuDQo+PiBTbyBwZXJoYXBzIFJUVCB3aWxsIG5vdCBldmVuIGV4aXN0IGluIHRo
aXMgY2FzZS4NCj4+Pg0KPj4+IEpvc2UNCj4+Pg0KPj4+PiAtLS0tLU1lbnNhamUgb3JpZ2luYWwt
LS0tLQ0KPj4+PiBEZTogRkVSTkFORE8gUEFTQ1VBTCBCTEFOQ08gW21haWx0bzpmcGJAdGlkLmVz
XSBFbnZpYWRvIGVsOiBqdWV2ZXMsDQo+Pj4+IDE3IGRlIGVuZXJvIGRlIDIwMTMgMTQ6MzkNCj4+
Pj4gUGFyYToganNhbGRhbmFAdW5pemFyLmVzOyAnRGFuIFdpbmcnOyAnTWlya28gU3XFvm5qZXZp
xIcnOyAnSnVsacOhbg0KPj4+PiBGZXJuw6FuZGV6IE5hdmFqYXMnDQo+Pj4+IENDOiB0Y210ZkBp
ZXRmLm9yZw0KPj4+PiBBc3VudG86IFJlOiBbdGNtdGZdIERyYWZ0OiBNYXhpbXVtIFRvbGVyYWJs
ZSBEZWxheXMgd2hlbiB1c2luZw0KPj4+PiBUdW5uZWxpbmcgQ29tcHJlc3NlZCBNdWx0aXBsZXhl
ZCBUcmFmZmljIEZsb3dzDQo+Pj4+DQo+Pj4+IEpvc2UsDQo+Pj4+DQo+Pj4+ICAgICAgICAgICBM
ZXTCtHMgc2F5IHRoYXQgcGxheWluZyB3aXRoIHRoZSBPV0QgeW91IGhhdmUgbW9yZQ0KPj4+PiBn
cmFudWxhcml0eSBpbiBvcmRlciB0byBrbm93IGluIHdoaWNoIGRpcmVjdGlvbiB5b3UgbmVlZCB0
byByZWR1Y2UNCj4+Pj4gdGhlIGRlbGF5IGJ5IHJlZHVjaW5nIHRoZSBtdWx0aXBsZXhpbmcgZGVs
YXkuIEJ1dCBwZW9wbGUgd2l0aCBtb3JlDQo+Pj4+IGtub3dsZWRnZSBhYm91dCBvbmxpbmUgZ2Ft
ZXMgd2lsbCBwcm92aWRlIHVzIG1vcmUgaW5mb3JtYXRpb24gZm9yIHN1cmUuDQo+Pj4+DQo+Pj4+
IFJlZ2FyZHMsDQo+Pj4+DQo+Pj4+IEZlcm5hbmRvIFBhc2N1YWwgQmxhbmNvDQo+Pj4+IFRlbGVm
w7NuaWNhIEdsb2JhbCBSZXNvdXJjZXMNCj4+Pj4gTmV0d29yayBBdXRvbWF0aW9uIGFuZCBEeW5h
bWl6YXRpb24NCj4+Pj4gVEVDSE5PTE9HWSBQRU9QTEUgR1JPVVANCj4+Pj4gRiArMzQ5MTMxMjg3
NzkNCj4+Pj4gTSArMzQ2ODIwMDUxNjgNCj4+Pj4gZnBiQHRpZC5lcw0KPj4+Pg0KPj4+Pg0KPj4+
Pg0KPj4+Pg0KPj4+PiBPbiAxNy8wMS8xMyAxMzoxNiwgIkpvc2UgU2FsZGFuYSIgPGpzYWxkYW5h
QHVuaXphci5lcz4gd3JvdGU6DQo+Pj4+DQo+Pj4+PiBGZXJuYW5kbywNCj4+Pj4+DQo+Pj4+PiBT
byB5b3UgbWF5IGhhdmUgdGhpcyBjYXNlOg0KPj4+Pj4gLSB5b3VyIG11bHRpcGxleGluZyBkZWxh
eSBsaW1pdCBpcyA1MCBtcw0KPj4+Pj4gLSB5b3UgaGF2ZSBhIGxvdCBvZiBmbG93cyB0byBtdWx0
aXBsZXgsIHNvIHBlcmhhcHMgdGhlIHRpbWUgYmV0d2Vlbg0KPj4+Pj4gbXVsdGlwbGV4ZWQgcGFj
a2V0cyB3aWxsIGJlIDUgbXMNCj4+Pj4+IC0geW91IGRldGVjdCBhbiBpbmNyZWFzZSBpbiBSVFQN
Cj4+Pj4+IC0gdGhlIHN5c3RlbSByZWFjdHMgYW5kIHJlZHVjZXMgbXVsdGlwbGV4aW5nIHBlcmlv
ZA0KPj4+Pj4gLSBpbiBmYWN0LCB0aGUgcmVkdWN0aW9uIGRvZXNuJ3QgbWF0dGVyIHVudGlsIHRo
ZSBwZXJpb2QgaXMgcmVkdWNlZA0KPj4+Pj4gdG8gbGVzcyB0aGFuIDUgbXMNCj4+Pj4+DQo+Pj4+
PiBTbyB5b3Ugb25seSBoYXZlIHRvIG1ha2UgdGhpcyBkZWNpc2lvbjogdXNpbmcgdGNtdGYgd2l0
aCA1IG1zIHBlcmlvZA0KPj4+Pj4gb3Igbm90LiBJZiBSVFQgaXMgY3JpdGljYWwgeW91IG1heSBu
b3QgYmUgaW50ZXJlc3RlZCBvbiBzYXZpbmcNCj4+Pj4+IGJhbmR3aWR0aCwgYnV0IG9uIHJlZHVj
aW5nIGEgYml0IHRoZSBSVFQuDQo+Pj4+Pg0KPj4+Pj4gU28gSSB0aGluayB5b3VyIHF1ZXN0aW9u
IGlzOiB3aGF0IGhhcHBlbnMgaWYgdGhlIFJUVCBpcyB2ZXJ5IGJpZw0KPj4+Pj4gKG91dCBvZg0K
Pj4+Pj4gbGltaXRzKSBhbmQgeW91IGNhbiBzYXZlIGJhbmR3aWR0aCB1c2luZyBhIDVtcyBtdWx0
aXBsZXhpbmcgcGVyaW9kPw0KPj4+Pj4NCj4+Pj4+IEZvciBleGFtcGxlLCB0aGUgbWF4aW11bSBS
VFQgZm9yIGEgZ29vZCBxdWFsaXR5IGlzIDgwIG1zIGFuZCB5b3VyDQo+Pj4+PiBuZXR3b3JrIGhh
cyAxMjAganVzdCBub3cuIEluIHRoaXMgY2FzZSwgcGVyaGFwcyBoYXZpbmcgMTI1IGRvZXNuJ3QN
Cj4+Pj4+IG1hdHRlciwgaWYgeW91IGNhbiBzYXZlIGJhbmR3aWR0aC4NCj4+Pj4+DQo+Pj4+PiBU
aGlzIG1ha2VzIHNlbnNlLCBidXQgaXQgaXMgYSAiZXh0cmVtZSIgY2FzZS4gSG93ZXZlciwgd291
bGQgaXQgYmUNCj4+Pj4+IGFueSBhZHZhbnRhZ2UgaWYgT1dEIGlzIHVzZWQgaW5zdGVhZCBvZiBS
VFQ/DQo+Pj4+Pg0KPj4+Pj4gQmVzdCByZWdhcmRzLA0KPj4+Pj4NCj4+Pj4+IEpvc2UNCj4+Pj4+
DQo+Pj4+Pj4gLS0tLS1NZW5zYWplIG9yaWdpbmFsLS0tLS0NCj4+Pj4+PiBEZTogRkVSTkFORE8g
UEFTQ1VBTCBCTEFOQ08gW21haWx0bzpmcGJAdGlkLmVzXSAgRW52aWFkbyBlbDoNCj4+Pj4+PiBt
acOpcmNvbGVzLCAxNiBkZSBlbmVybyBkZSAyMDEzIDEyOjUyDQo+Pj4+Pj4gUGFyYToganNhbGRh
bmFAdW5pemFyLmVzOyAnRGFuIFdpbmcnOyAnTWlya28gU3XFvm5qZXZpxIcnOyAnSnVsacOhbg0K
Pj4+Pj4+IEZlcm7DoW5kZXogIE5hdmFqYXMnDQo+Pj4+Pj4gQ0M6IHRjbXRmQGlldGYub3JnDQo+
Pj4+Pj4gQXN1bnRvOiBSZTogW3RjbXRmXSBEcmFmdDogTWF4aW11bSBUb2xlcmFibGUgRGVsYXlz
IHdoZW4gdXNpbmcNCj4+Pj4+PiBUdW5uZWxpbmcgIENvbXByZXNzZWQgTXVsdGlwbGV4ZWQgVHJh
ZmZpYyBGbG93cw0KPj4+Pj4+DQo+Pj4+Pj4gSGkgSm9zZSwNCj4+Pj4+Pg0KPj4+Pj4+ICAgICAg
ICAgICBZb3UgYXJlIHJpZ2h0LCBidXQgbXkgcG9pbnQgaGVyZSBpczoNCj4+Pj4+Pg0KPj4+Pj4+
ICAgICAgICAgICAgICAgICAgIENsaWVudCAtIE11eCAtIERlbXV4IC0gU2VydmVyDQo+Pj4+Pj4N
Cj4+Pj4+PiAgICAgICAgICAgSW1hZ2luZSB0aGF0IHRoZXJlIGlzIGVub3VnaCBwYWNrZXRzIGJl
dHdlZW4gbXV4IGFuZCBkZW11eA0KPj4+Pj4+IHRvIG1ha2UgIHRoZSBhZGRlZCBkZWxheSB2ZXJ5
IHNtYWxsIChUQ01URiBpcyB3b3JraW5nIHZlcnkgd2VsbCBhbmQNCj4+Pj4+PiB0aGUgbXV4IGhh
cyBub3QgIHRvIHdhaXQgdGhlIG11bHRpcGxleGluZyBwZXJpb2QgdG8gZnVsZmlsbCBhIGJpZw0K
Pj4+Pj4+IHBhY2tldCBhbmQgc2VuZCBpdCwgc28gaW1hZ2luZSBhICBtdWx0aXBsZXhpbmcgcGVy
aW9kIG9mIDUwIG1zIGFuZA0KPj4+Pj4+IGEgYmlnIHBhY2tldCBpcyBmdWxmaWxsZWQgaW4gNSBt
cykuIElmIHRoZSBSVFQgIGdldCBpbmNyZWFzZWQNCj4+Pj4+PiBiZWNhdXNlIGEgY29uZ2VzdGlv
biBpbiB0aGUgd2F5IGJhY2sgdG8gdGhlIGNsaWVudCAodGhlcmUgaXMgbm8NCj4+Pj4+PiBUQ01U
Rg0KPj4+Pj4+IG9wdGltaXphdGlvbikgYW5kIHdlIGRlY3JlYXNlIHRoZSBtdWx0aXBsZXhpbmcg
cGVyaW9kIChldmVuIGluIHRoZQ0KPj4+Pj4+IGV4dHJlbWUgd2UgY2FuIGRpc2FibGUgdGhlIFRD
TVRGIG9wdGltaXphdGlvbikgdGhlIGhpZ2ggUlRUIHdpbGwNCj4+IHJlbWFpbi4NCj4+Pj4+PiBF
dmVuIGlmIHRoZSBUQ01URiBvcHRpbWl6YXRpb24gd2FzIGhlbHBpbmcgaW4gdGhlIGNsaWVudCB0
byBzZXJ2ZXINCj4+Pj4+PiBwYXRoLCAgZGlzYWJsaW5nIGl0IG1heSBoYXJtLiBEbyB5b3UgdGhp
bmsgdGhhdCBzY2VuYXJpbyB3b3VsZCBiZQ0KPj4gcG9zc2libGU/DQo+Pj4+Pj4NCj4+Pj4+PiAg
ICAgICAgICAgU28gScK0bSBub3Qgc3VyZSBhYm91dCB0aGF0LCBJIHRoaW5rIHdlIG5lZWQgbW9y
ZSBvcGluaW9ucyBoZXJlLg0KPj4+Pj4+DQo+Pj4+Pj4gUmVnYXJkcywNCj4+Pj4+Pg0KPj4+Pj4+
IEZlcm5hbmRvIFBhc2N1YWwgQmxhbmNvDQo+Pj4+Pj4gVGVsZWbDs25pY2EgR2xvYmFsIFJlc291
cmNlcw0KPj4+Pj4+IE5ldHdvcmsgQXV0b21hdGlvbiBhbmQgRHluYW1pemF0aW9uIFRFQ0hOT0xP
R1kgUEVPUExFIEdST1VQDQo+PiBGDQo+Pj4+Pj4gKzM0OTEzMTI4Nzc5IE0gKzM0NjgyMDA1MTY4
IGZwYkB0aWQuZXMNCj4+Pj4+Pg0KPj4+Pj4+DQo+Pj4+Pj4NCj4+Pj4+Pg0KPj4+Pj4+IE9uIDE2
LzAxLzEzIDExOjU3LCAiSm9zZSBTYWxkYW5hIiA8anNhbGRhbmFAdW5pemFyLmVzPiB3cm90ZToN
Cj4+Pj4+Pg0KPj4+Pj4+PiBNeSB0d28gY2VudHM6DQo+Pj4+Pj4+DQo+Pj4+Pj4+IEluIGdhbWVz
IGFuZCBpbiBWb0lQIHRoZSByZWFsbHkgaW1wb3J0YW50IHRoaW5nIGlzIFJUVDoNCj4+Pj4+Pj4N
Cj4+Pj4+Pj4gLSBHYW1lcyBhbHdheXMgbWVhc3VyZSB0aGUgUlRUIChnYW1lcnMgdGFsayBhYm91
dCB0aGUgInBpbmciKTogdGhlDQo+Pj4+Pj4+IGltcG9ydGFudCB0aGluZyBpcyB0aGUgZGVsYXkg
ZnJvbSBhIHBsYXllciBhY3Rpb24gdG8gdGhlIHNlcnZlcg0KPj4+Pj4+PiByZWFjdGlvbiBhcnJp
dmluZyB0byB0aGUgcGxheWVyJ3MgbWFjaGluZS4NCj4+Pj4+Pj4gLSBJbiBWb0lQIEkgdGhpbmsg
aXQgaXMgdGhlIHNhbWU6IHdoYXQgbWF0dGVycyBpcyB0aGUgUlRULCBpbg0KPj4+Pj4+PiBvcmRl
ciB0byBncmFudCBpbnRlcmFjdGl2aXR5IGFuZCBhdm9pZGluZyBjcm9zcy10YWxrLg0KPj4+Pj4+
Pg0KPj4+Pj4+PiBJbiBhZGRpdGlvbiwgUlRUIGlzIGVhc2llciB0byBtZWFzdXJlIHRoYW4gT1dE
LCBzaW5jZSB5b3UgZG9uJ3QNCj4+Pj4+Pj4gbmVlZCBzeW5jaHJvbml6YXRpb24uDQo+Pj4+Pj4+
DQo+Pj4+Pj4+IEFuZCByZWdhcmRpbmcgVHdvLXdheSBUQ01URiwgSSB0aGluayB3ZSBoYXZlIHRv
IHRoaW5rIGFib3V0IFRDTVRGDQo+Pj4+Pj4+IGFzIG9uZS13YXkuIE90aGVyd2lzZSwgdGhpbmdz
IHdvdWxkIGJlY29tZSB2ZXJ5IGNvbXBsaWNhdGVkLg0KPj4gU29tZQ0KPj4+Pj4+IHNlcnZpY2Vz
DQo+Pj4+Pj4+IGhhdmUgdmVyeSBkaWZmZXJlbnQgY2xpZW50LXNlcnZlciBhbmQgc2VydmVyLWNs
aWVudCB0cmFmZmljDQo+Pj4+Pj4+IHBhdHRlcm5zIChlLmcuIGdhbWVzKS4gSW4gYWRkaXRpb24s
IHNvbWV0aW1lcyB0aGUgdHdvIGZsb3dzIGNhbg0KPj4+Pj4+PiBmb2xsb3cgZGlmZmVyZW50IG5l
dHdvcmsgcGF0aHMuIEkgdGhpbmsgb25jZSB3ZSB0YWxrZWQgYWJvdXQgYQ0KPj4+Pj4+PiBuZXR3
b3JrIHByb3ZpZGVyIHVzaW5nIGEgbnVtYmVyIG9mIElTUHMuDQo+Pj4+Pj4+DQo+Pj4+Pj4+IEhv
d2V2ZXIsIHVzaW5nIFJUVCBmb3IgdHVuaW5nIGEgb25lLXdheSBUQ01URiBtYXkgbm90IGJlIGJh
ZC4uLiBvcg0KPj4+Pj4+PiBpcyBpdCBiYWQ/IEFueSBvdGhlciB0aG91Z2h0cz8NCj4+Pj4+Pj4N
Cj4+Pj4+Pj4gQlIsDQo+Pj4+Pj4+DQo+Pj4+Pj4+IEpvc2UNCj4+Pj4+Pj4NCj4+Pj4+Pj4+IC0t
LS0tTWVuc2FqZSBvcmlnaW5hbC0tLS0tDQo+Pj4+Pj4+PiBEZTogRkVSTkFORE8gUEFTQ1VBTCBC
TEFOQ08gW21haWx0bzpmcGJAdGlkLmVzXSAgRW52aWFkbyBlbDoNCj4+Pj4+PiBtYXJ0ZXMsDQo+
Pj4+Pj4+PiAxNSBkZSBlbmVybyBkZSAyMDEzIDE4OjA0DQo+Pj4+Pj4+PiBQYXJhOiBqc2FsZGFu
YUB1bml6YXIuZXM7ICdEYW4gV2luZyc7ICdNaXJrbyBTdcW+bmpldmnEhyc7IEp1bGnDoW4NCj4+
Pj4+Pj4+IEZlcm7DoW5kZXogIE5hdmFqYXMNCj4+Pj4+Pj4+IENDOiB0Y210ZkBpZXRmLm9yZw0K
Pj4+Pj4+Pj4gQXN1bnRvOiBSZTogW3RjbXRmXSBEcmFmdDogTWF4aW11bSBUb2xlcmFibGUgRGVs
YXlzIHdoZW4gdXNpbmcNCj4+Pj4+Pj4+IFR1bm5lbGluZyAgQ29tcHJlc3NlZCBNdWx0aXBsZXhl
ZCBUcmFmZmljIEZsb3dzDQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gSGkgYWxsLA0KPj4+Pj4+Pj4NCj4+
Pj4+Pj4+ICAgICAgICAgICBUbyByZS1vcGVuIHRoYXQgaXNzdWUsIEkgd291bGQgc3VnZ2VzdCB0
aGF0IGdpdmVuIHRoYXQNCj4+Pj4+Pj4+IHRoZSBkZWxheSBpcyBzbyAgc2Vuc2l0aXZlIGluIHJl
YWwgdGltZSBzZXJ2aWNlcywgd2UgbmVlZCB0byBmaW5kDQo+Pj4+Pj4+PiBhIGNvbnNlbnN1cyBo
ZXJlLg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+ICAgICAgICAgICBNeSBvcGluaW9uIGlzIHRoYXQgdG8g
YXBwbHkgdGhlIGZpcnN0IHBvc3NpYmlsaXR5ICh0aGUNCj4+Pj4+Pj4+IHN0YXRpYyBtdWx0aXBs
ZXhpbmcNCj4+Pj4+Pj4+IHBlcmlvZCkgd2UgbmVlZCB0byBzdXBwb3NlIHRoYXQgdGhlIG5ldHdv
cmsgY29uZGl0aW9ucyBhcmUgcmVhbGx5DQo+Pj4+Pj4+PiBiYWQsIHRvIGJlICBwcm90ZWN0ZWQg
d2hlbiB0aGUgbmV0d29yayBjb25nZXN0aW9uIGFyaXNlcy4gSW4gdGhhdA0KPj4+Pj4+Pj4gY2Fz
ZSwgdGhlIGFwcGxpY2F0aW9uICBvZiB0aGUgVENNVEYgb3B0aW1pemF0aW9uIHdpbGwgbm90IGJl
DQo+Pj4+Pj4+PiBvcHRpbWFsLCBzbyB0aGF0IHdvdWxkIGJlIHRoZSBsZXNzICBwcmVmZXJyZWQg
b3B0aW9uLCBidXQgZWFzaWVyDQo+Pj4+Pj4+PiB0byBpbXBsZW1lbnQgYW5kIG1haW50YWluIG92
ZXIgdGhlIHRpbWUuDQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gICAgICAgICAgIE9uIHRoZSBvdGhlciBo
YW5kLCB0aGUgc2Vjb25kIHBvc3NpYmlsaXR5IHdvdWxkIGJlIHRoZQ0KPj4+Pj4+Pj4gcHJlZmVy
cmVkLiBJdCBpcyAgZWFzeSB0byBrbm93IHRoZSBkZWxheSBiZXR3ZWVuIHRoZSBtdXggYW5kIHRo
ZQ0KPj4+Pj4+Pj4gZGVtdXggYnV0IG1vc3Qgb2YgdGhlICB0aW1lcyB3aWxsIG5vdCBiZSBlbm91
Z2ggdW5sZXNzIG11eCBhbmQNCj4+Pj4+Pj4+IGRlbXV4IHdlcmUgcmVhbGx5IG5lYXIgZnJvbSB0
aGUgIGNsaWVudCBhbmQgdGhlIHNlcnZlcg0KPj4+Pj4+Pj4gcmVzcGVjdGl2ZWx5LiBJIGFncmVl
IHdpdGggSm9zZSBpbiB0aGUgcG9zc2liaWxpdHkgb2Ygc25vb3AgIFJUQ1ANCj4+Pj4+Pj4+IHBh
Y2tldHMgaW4gb3JkZXIgdG8gYWRhcHQgdGhlIG11bHRpcGxleGluZyBwZXJpb2Qgd2hlbg0KPj4+
Pj4+Pj4gbXVsdGlwbGV4aW5nIFJUUCBwYWNrZXRzIChhbmQgUlRDUCBpcyBhdmFpbGFibGUpLiBU
YWxraW5nIGFib3V0DQo+Pj4+Pj4+PiBSVFQsIEnCtG0gbm90IHN1cmUgaWYgUlRUICB3b3VsZCBi
ZSB1c2VmdWwgZ2l2ZW4gdGhhdCB0aGUNCj4+Pj4+Pj4+IG11bHRpcGxleGluZyBwZXJpb2Qgb25s
eSBhZmZlY3QgdGhlIG9uZSB3YXkgIGRlbGF5IChPV0QpLiBJbWFnaW5lDQo+PiB0aGUgZm9sbG93
aW5nIHNjZW5hcmlvOg0KPj4+Pj4+Pj4gICAgICAgICAgIC0gQ2xpZW50IC0gTXV4L0RlbXV4IC0g
RGVtdXgvTXV4IC0gU2VydmVyICh0d28gd2F5cw0KPj4+Pj4+Pj4gVENNVEYsIFRXVENNVEYgOlAp
DQo+Pj4+Pj4+PiAgICAgICAgICAgLSBUaGUgT1dEIGZyb20gc2VydmVyIHRvIGNsaWVudCBnZXQg
aW5jcmVhc2VkDQo+Pj4+Pj4+PiAgICAgICAgICAgLSBUaGUgT1dEIGZyb20gY2xpZW50IHRvIHNl
cnZlciByZW1haW5zIGVxdWFsDQo+Pj4+Pj4+PiAgICAgICAgICAgLSBTaG91bGQgd2UgdXNlIGEg
bG93ZXIgbXVsdGlwbGV4aW5nIHBlcmlvZCBpbiB0aGUNCj4+Pj4+Pj4+IGNsaWVudCB0byBzZXJ2
ZXIgIGRpcmVjdGlvbj8gSSBkb27CtHQgdGhpbmsgc2/igKYgYmVjYXVzZSB3ZSBzaG91bGQNCj4+
Pj4+Pj4+IHVzZSBhIGxvd2VyIG11bHRpcGxleGluZyAgcGVyaW9kIGluIHRoZSBvdGhlciBkaXJl
Y3Rpb24uDQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gICAgICAgICAgIE15IHBvaW50IGlzIHRoYXQgdGhl
IG11bHRpcGxleGluZyBwZXJpb2Qgc2hvdWxkIG9ubHkgYmUNCj4+Pj4+Pj4+IGFmZmVjdGVkIGJ5
IHRoZSAgT1dEIGFuZCBub3QgYnkgdGhlIFJUVCAob3IgaXQgbWF5IGJlIGFwcGxpY2F0aW9uDQo+
Pj4+Pj4+PiBkZXBlbmRlbnQpLiBIb3cgdG8gIGNhbGN1bGF0ZSB0aGUgT1dEPyBJwrR2ZSBiZWVu
IHJlYWRpbmcNCj4+Pj4+Pj4+IHNvbWV0aGluZyBhYm91dCBPV0FNUCBhbmQgaXQgIHNlZW1zIHRo
YXQgYW4gc3BlY2lmaWMgc29mdHdhcmUgaGFzDQo+Pj4+Pj4+PiB0byBiZSBpbXBsZW1lbnRlZCBp
biB0aGUgY2xpZW50L3NlcnZlciAgc2lkZS4NCj4+Pj4+Pj4+IENhbiB3ZSBhc3N1bWUgdGhhdD8g
VW5mb3J0dW5hdGVseSBJIGNhbm5vdCBjb250cmlidXRlIHNvIG11Y2gNCj4+Pj4gaGVyZeKApg0K
Pj4+Pj4+Pj4gICAgICAgICAgIEl0IGlzIHBvc3NpYmxlIHRoYXQgZm9yIGNlcnRhaW4gc2Vydmlj
ZXMgdGhlIHN0YXRpYyAoYW5kDQo+Pj4+Pj4+PiB3b3JzdA0KPj4+Pj4+Pj4gY2FzZSkNCj4+Pj4+
Pj4+IG11bHRpcGxleGluZyBwZXJpb2Qgd291bGQgYmUgdGhlIGJldHRlciBzb2x1dGlvbi4NCj4+
Pj4+Pj4+DQo+Pj4+Pj4+PiAgICAgICAgICAgV2hhdCBkbyB5b3UgdGhpbms/DQo+Pj4+Pj4+Pg0K
Pj4+Pj4+Pj4gUmVnYXJkcywNCj4+Pj4+Pj4+DQo+Pj4+Pj4+PiBGZXJuYW5kbyBQYXNjdWFsIEJs
YW5jbw0KPj4+Pj4+Pj4gVGVsZWbDs25pY2EgR2xvYmFsIFJlc291cmNlcw0KPj4+Pj4+Pj4gTmV0
d29yayBBdXRvbWF0aW9uIGFuZCBEeW5hbWl6YXRpb24gVEVDSE5PTE9HWSBQRU9QTEUNCj4+IEdS
T1VQDQo+Pj4+IEYNCj4+Pj4+Pj4+ICszNDkxMzEyODc3OSBNICszNDY4MjAwNTE2OCBmcGJAdGlk
LmVzDQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+DQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gT24g
MTcvMTIvMTIgMTI6MjUsICJKb3NlIFNhbGRhbmEiIDxqc2FsZGFuYUB1bml6YXIuZXM+IHdyb3Rl
Og0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+PiBIaSBhbGwsDQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+PiBKdWxp
YW4gYW5kIEkgaGF2ZSBiZWVuIGRpc2N1c3NpbmcgYWJvdXQgdGhpcy4gU29tZSBpZGVhcyBoYXZl
DQo+Pj4+Pj4gYXJpc2VuLg0KPj4+Pj4+Pj4+IFRoaXMgaXMgdGhlIHN1bW1hcnkuDQo+Pj4+Pj4+
Pj4NCj4+Pj4+Pj4+PiBUaGlzIHdvdWxkIGJlIHRoZSBzY2hlbWUgb2YgdGhlIHN5c3RlbSwgaW5j
bHVkaW5nIG11eCBhbmQNCj4+IGRlbXV4Og0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gUmVhbC10aW1l
IGFwcGxpY2F0aW9uIC0tLS0tLS0gbXV4IC0tLS0tLS0tIGludGVybmV0IC0tLS0tLS0tLQ0KPj4+
Pj4+Pj4+IGRlbXV4DQo+Pj4+Pj4+Pj4gLS0tLS0tLQ0KPj4+Pj4+Pj4+IHNlcnZlcg0KPj4+Pj4+
Pj4+DQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+PiBJIHRoaW5rIHBlcmhhcHMgdGhlIGRyYWZ0IGNvdWxk
IHNheSBzb21ldGhpbmcgbGlrZToNCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+IFdoZW4gc2V0dGluZyB0
aGUgbXVsdGlwbGV4aW5nIHBlcmlvZCwgdGhlcmUgYXJlIHR3byBwb3NzaWJpbGl0aWVzOg0KPj4+
Pj4+Pj4+DQo+Pj4+Pj4+Pj4gMS4tIFN0YXRpYyAvIHBlcm1hbmVudDogQXQgc3lzdGVtIHNldHVw
IHRpbWUsIG5ldHdvcmsgZGVsYXlzIGFyZQ0KPj4+Pj4+Pj4+IG1lYXN1cmVkLCBhbmQgYSBtdWx0
aXBsZXhpbmcgcGVyaW9kIGlzIHNlbGVjdGVkIGFuZCBzZXQgaW4gdGhlDQo+Pj4+Pj4+PiBtdWx0
aXBsZXhlci4NCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+IDIuLSBEeW5hbWljOiBBIG1lY2hhbmlzbSBp
cyB1c2VkIHNvIGFzIHRvIGFkYXB0IHRvIHRoZSBldm9sdXRpb24NCj4+Pj4+Pj4+PiBvZiBuZXR3
b3JrIGRlbGF5cy4gSW4gdGhpcyBjYXNlLCBkaWZmZXJlbnQgbWVjaGFuaXNtcyBjYW4gYmUNCj4+
Pj4+Pj4+PiB1c2VkIGluIG9yZGVyIHRvIG9idGFpbiBwZXJpb2RpY2FsIGVuZC10by1lbmQgbmV0
d29yayBkZWxheQ0KPj4+Pj4+Pj4+IGVzdGltYXRpb25zLCB3aGljaCB3b3VsZCBiZSB1c2VmdWwg
aW4gb3JkZXIgdG8gc2V0IHRoZQ0KPj4+Pj4+Pj4+IG11bHRpcGxleGluZw0KPj4+PiBwZXJpb2Q6
DQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+PiAtIElmIHRoZSB0cmFmZmljIGlzIFJUUCwgdGhlbiBSVENQ
IHBhY2tldHMgY29udGFpbmluZyB0aGUNCj4+Pj4+Pj4+PiBlc3RpbWF0aW9uIGNvdWxkIGJlIGFu
YWx5emVkIGluIG9yZGVyIHRvIGV4dHJhY3QgdGhlc2UgdmFsdWVzLA0KPj4+Pj4+Pj4+IGFzIERh
bg0KPj4+PiBzdWdnZXN0cy4NCj4+Pj4+Pj4+PiBUaGUgcXVlc3Rpb24NCj4+Pj4+Pj4+PiBpczog
d291bGQgdGhhdCBwYWNrZXRzIHRyYXZlbCB0aHJvdWdoIHRoZSBtdWx0aXBsZXhlcj8NCj4+Pj4+
Pj4+PiAtIElmIHRoZSB0cmFmZmljIGlzIFRDUCwgcGVyaGFwcyBzb21ldGhpbmcgc2ltaWxhciB0
byB0aGUgUlRUDQo+Pj4+Pj4+Pj4gZXN0aW1hdGlvbiBvZiBUQ1AgY291bGQgYmUgdXNlZnVsLg0K
Pj4+Pj4+Pj4+IC0gSWYgdGhlIHRyYWZmaWMgaXMgVURQLCBzaG91bGQgdGhlIG11eCB1c2Ugc29t
ZXRoaW5nIGxpa2UgT1dBTVANCj4+Pj4+Pj4+PiAoaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwv
cmZjNDY1NikgaW4gb3JkZXIgdG8gY2FsY3VsYXRlIHR3bw0KPj4+Pj4+Pj4+IGRlbGF5cyAoYXBw
bGljYXRpb24gdG8gbXV4LCBhbmQgbXV4IHRvIHNlcnZlcikgYW5kIGNhbGN1bGF0ZSB0aGUNCj4+
Pj4+PiBzdW0/DQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+IEkgdGhpbmsgdGhlIGRy
YWZ0IGlzIG9ubHkgc3VwcG9zZWQgdG8gcmVwb3J0IHRoZSBtYXhpbXVtIGRlbGF5cw0KPj4+Pj4+
Pj4+IG5vcm1hbGx5IGNvbnNpZGVyZWQgYWNjZXB0YWJsZS4gUGVyaGFwcyB0aGUgYWRkaXRpb25h
bA0KPj4+Pj4+Pj4+IG1lY2hhbmlzbXMgZm9yIGNhbGN1bGF0aW5nIHRoZSBSVFQgY291bGQganVz
dCBiZSBzdWdnZXN0ZWQuDQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+PiBXaGF0IGRvIHlvdSB0aGluaz8N
Cj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+IEpvc2UNCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+PiAtLS0tLU1l
bnNhamUgb3JpZ2luYWwtLS0tLQ0KPj4+Pj4+Pj4+PiBEZTogdGNtdGYtYm91bmNlc0BpZXRmLm9y
ZyBbbWFpbHRvOnRjbXRmLWJvdW5jZXNAaWV0Zi5vcmddIEVuDQo+Pj4+Pj4+Pj4+IG5vbWJyZSBk
ZSBEYW4gV2luZyBFbnZpYWRvIGVsOiB2aWVybmVzLCAxNCBkZSBkaWNpZW1icmUgZGUgMjAxMg0K
Pj4+Pj4+Pj4+PiAxODozMw0KPj4+Pj4+Pj4+PiBQYXJhOiBqc2FsZGFuYUB1bml6YXIuZXM7ICdN
aXJrbyBTdcW+bmpldmnEhycNCj4+Pj4+Pj4+Pj4gQ0M6IHRjbXRmQGlldGYub3JnDQo+Pj4+Pj4+
Pj4+IEFzdW50bzogUmU6IFt0Y210Zl0gRHJhZnQ6IE1heGltdW0gVG9sZXJhYmxlIERlbGF5cyB3
aGVuIHVzaW5nDQo+Pj4+Pj4+Pj4+IFR1bm5lbGluZyBDb21wcmVzc2VkIE11bHRpcGxleGVkIFRy
YWZmaWMgRmxvd3MNCj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQo+Pj4+Pj4+Pj4+PiBGcm9tOiBKb3NlIFNhbGRhbmEgW21haWx0bzpqc2FsZGFuYUB1
bml6YXIuZXNdDQo+Pj4+Pj4+Pj4+PiBTZW50OiBGcmlkYXksIERlY2VtYmVyIDE0LCAyMDEyIDI6
NTggQU0NCj4+Pj4+Pj4+Pj4+IFRvOiAnRGFuIFdpbmcnOyAnTWlya28gU3XFvm5qZXZpxIcnDQo+
Pj4+Pj4+Pj4+PiBDYzogdGNtdGZAaWV0Zi5vcmcNCj4+Pj4+Pj4+Pj4+IFN1YmplY3Q6IFJFOiBb
dGNtdGZdIERyYWZ0OiBNYXhpbXVtIFRvbGVyYWJsZSBEZWxheXMgd2hlbg0KPj4+Pj4+Pj4+Pj4g
dXNpbmcgVHVubmVsaW5nIENvbXByZXNzZWQgTXVsdGlwbGV4ZWQgVHJhZmZpYyBGbG93cw0KPj4+
Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+IERhbiwNCj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+PiBSZWdh
cmRpbmcgdGhlIHVzZSBvZiB0aGUgbWF4aW11bSBkZWxheSwgc29tZSBkYXlzIGFnbyB3ZQ0KPj4+
Pj4+Pj4+Pj4gZGlzY3Vzc2VkIGFib3V0DQo+Pj4+Pj4+Pj4+PiBpdDoNCj4+Pj4+Pj4+Pj4+IHRo
ZSBhY3R1YWwgT1dEIG9mIHRoZSBuZXR3b3JrIHNob3VsZCBiZSBtZWFzdXJlZCAob3INCj4+Pj4+
Pj4+Pj4+IGVzdGltYXRlZCkgaW4gb3JkZXIgdG8ga25vdyB0aGUgbWF4aW11bSBtdWx0aXBsZXhp
bmcgcGVyaW9kDQo+PiB3ZQ0KPj4+PiBjYW4gc2V0Lg0KPj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+
IFdlIG1heSBoYXZlIHRoaXMgZm9ybXVsYSwgaWYgdGhpbmtpbmcgb25lLXdheToNCj4+Pj4+Pj4+
Pj4+DQo+Pj4+Pj4+Pj4+PiBPV0QgICsgTXV4IHBlcmlvZC8yICA8IHRvbGVyYWJsZV9PV0QNCj4+
Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+PiBJZiB3ZSB0aGluayBSVFQ6DQo+Pj4+Pj4+Pj4+Pg0KPj4+
Pj4+Pj4+Pj4gT1dEICsgTXV4IHBlcmlvZC8yICsgT1dEIGJhY2sgPCAyKnRvbGVyYWJsZV9PV0QN
Cj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+PiBJIGRvbid0IGtub3cgaWYgd2Ugc2hvdWxkIGluY2x1
ZGUgYSBtZWNoYW5pc20gZm9yIGVzdGltYXRpbmcNCj4+Pj4+Pj4+Pj4+IE9XRCBpbiB0Y210Zi4g
SSB0aGluayB0aGlzIGlzIG1vcmUgYW4gaW1wbGVtZW50YXRpb24gcHJvYmxlbSwNCj4+Pj4+Pj4+
Pj4+IHdoaWNoIG1heSBiZSBhbHJlYWR5IHNvbHZlZC4NCj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4g
WWVzLCBpdCdzIGFscmVhZHkgc29sdmVkIGVuZC10by1lbmQ6ICBSVFAgd2l0aCBSVENQIGZlZWRi
YWNrDQo+Pj4+Pj4+Pj4+IGFsbG93cyBkZXRlcm1pbmluZyBvbmUgd2F5IGRlbGF5Lg0KPj4+Pj4+
Pj4+Pg0KPj4+Pj4+Pj4+PiBCdXQgaWYgc29tZXRoaW5nIGluIHRoZSBtaWRkbGUgaXMgbXVsdGlw
bGV4aW5nIHNldmVyYWwgcGFja2V0cw0KPj4+Pj4+Pj4+PiB0b2dldGhlciwNCj4+Pj4+Pj4+PiB3
ZQ0KPj4+Pj4+Pj4+PiBkb24ndCB3YW50IGl0IHRvIGFkZCB0b28gbXVjaCBkZWxheS4gIFRoYXQg
dGhpbmcgaW4gdGhlIG1pZGRsZQ0KPj4+Pj4+Pj4+PiB3b24ndCBuZWNlc3NhcmlseSBrbm93IHRo
ZSBvbmUgd2F5IGRlbGF5IHNlZW4gYnkgdGhlIGVuZHBvaW50cywNCj4+Pj4+Pj4+Pj4gdW5sZXNz
IGl0IGFuYWx5emVzIHRoZSBSVFAgYW5kIFJUQ1AuICBUaGVyZSBhcmUgZGV2aWNlcyB0aGF0IGRv
DQo+Pj4+Pj4+Pj4+IHRoYXQgb24gdGhlIG1hcmtldCwgIG1vc3RseSB0byBkaWFnbm9zZSB3aGVy
ZSBuZXR3b3JrcyBhcmUNCj4+Pj4+Pj4+Pj4gY2F1c2luZyBsb3NzL2RlbGF5IHdpdGggUlRQIGZs
b3dzLg0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4gQW5vdGhlciBvcHRpb24g
aXMgdXNpbmcgc29tZSB0eXBpY2FsIHZhbHVlcywgZS5nLiBmcm9tDQo+Pj4+Pj4+Pj4+Pg0KPj4+
PiBodHRwOi8vaXBuZXR3b3JrLmJndG1vLmlwLmF0dC5uZXQvcHdzL2dsb2JhbF9uZXR3b3JrX2F2
Z3MuaHRtDQo+Pj4+Pj4+Pj4+PiBsDQo+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4gVGhlIGRyYWZ0
IGluY2x1ZGVzIHNvbWUgcHJlbGltaW5hcnkvcmVjb21tZW5kZWQgdmFsdWVzIGZvcg0KPj4gdGhl
DQo+Pj4+Pj4+Pj4+PiBNdWx0aXBsZXhpbmcgUGVyaW9kLiBJcyB0aGlzIGludGVyZXN0aW5nPyBT
aG91bGQgd2UgcHV0IHRoZQ0KPj4+Pj4+Pj4+Pj4gZm9ybXVsYSBpbnN0ZWFkPw0KPj4+Pj4+Pj4+
Pg0KPj4+Pj4+Pj4+PiBJdCdzIHByb2JhYmx5IHN1ZmZpY2llbnQgYXMtaXMuDQo+Pj4+Pj4+Pj4+
DQo+Pj4+Pj4+Pj4+IC1kDQo+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+PiBNaXJrbywgYW5vdGhlciBx
dWVzdGlvbjogaW4gb25saW5lIGdhbWVzLCBwbGF5ZXJzIHVzdWFsbHkgdGFsaw0KPj4+Pj4+Pj4+
Pj4gYWJvdXQgdGhlICJwaW5nIiwgYW5kIEkgdGhpbmsgaXQgbWVhbnMgUlRULiBEb24ndCB5b3Ug
dGhpbmsgaXQNCj4+Pj4+Pj4+Pj4+IHdvdWxkIGJlIGJldHRlciB0byBkZWZpbmUgYSBSVFQgbGlt
aXQgaW5zdGVhZCBvZiBhIE9XRCBvbmUgaW4NCj4+Pj4+Pj4+Pj4+IHRoYXQNCj4+Pj4+Pj4+IGNh
c2U/DQo+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4gV2hhdCBkbyB5b3UgdGhpbms/DQo+Pj4+Pj4+
Pj4+Pg0KPj4+Pj4+Pj4+Pj4gSm9zZQ0KPj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+PiAtLS0tLU1l
bnNhamUgb3JpZ2luYWwtLS0tLQ0KPj4+Pj4+Pj4+Pj4+IERlOiB0Y210Zi1ib3VuY2VzQGlldGYu
b3JnIFttYWlsdG86dGNtdGYtYm91bmNlc0BpZXRmLm9yZ10NCj4+IEVuDQo+Pj4+Pj4+Pj4+Pj4g
bm9tYnJlIGRlIERhbiBXaW5nIEVudmlhZG8gZWw6IGp1ZXZlcywgMTMgZGUgZGljaWVtYnJlIGRl
DQo+Pj4+Pj4+Pj4+Pj4gMjAxMg0KPj4+Pj4+Pj4+Pj4+IDE3OjA3DQo+Pj4+Pj4+Pj4+Pj4gUGFy
YTogJ01pcmtvIFN1xb5uamV2acSHJzsgdGNtdGZAaWV0Zi5vcmcNCj4+Pj4+Pj4+Pj4+PiBBc3Vu
dG86IFJlOiBbdGNtdGZdIERyYWZ0OiBNYXhpbXVtIFRvbGVyYWJsZSBEZWxheXMgd2hlbg0KPj4+
Pj4+Pj4+Pj4+IHVzaW5nIFR1bm5lbGluZyBDb21wcmVzc2VkIE11bHRpcGxleGVkIFRyYWZmaWMg
Rmxvd3MNCj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KPj4+Pj4+Pj4+Pj4+PiBGcm9tOiB0Y210Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86
dGNtdGYtDQo+PiBib3VuY2VzQGlldGYub3JnXQ0KPj4+Pj4+Pj4+Pj4+PiBPbiBCZWhhbGYgT2Yg
TWlya28gU3XFvm5qZXZpYw0KPj4+Pj4+Pj4+Pj4+PiBTZW50OiBUaHVyc2RheSwgRGVjZW1iZXIg
MTMsIDIwMTIgMTowNyBBTQ0KPj4+Pj4+Pj4+Pj4+PiBUbzogdGNtdGZAaWV0Zi5vcmc7IHRzdndn
QGlldGYub3JnDQo+Pj4+Pj4+Pj4+Pj4+IFN1YmplY3Q6IFt0Y210Zl0gRHJhZnQ6IE1heGltdW0g
VG9sZXJhYmxlIERlbGF5cyB3aGVuIHVzaW5nDQo+Pj4+Pj4+Pj4+Pj4+IFR1bm5lbGluZyBDb21w
cmVzc2VkIE11bHRpcGxleGVkIFRyYWZmaWMgRmxvd3MNCj4+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+
Pj4+Pj4gSGVsbG8sDQo+Pj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4+
DQo+Pj4+Pj4+Pj4+Pj4+IFdlIGhhdmUganVzdCBzdWJtaXR0ZWQgdGhlIGRyYWZ0IG5hbWVkIE1h
eGltdW0gVG9sZXJhYmxlDQo+Pj4+Pj4+Pj4+Pj4+IERlbGF5cyB3aGVuIHVzaW5nIFR1bm5lbGlu
ZyBDb21wcmVzc2VkIE11bHRpcGxleGVkIFRyYWZmaWMNCj4+Pj4+PiBGbG93czoNCj4+Pj4+Pj4+
Pj4+Pj4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1zdXpuamV2aWMtdHN2
d2ctbXRkDQo+Pj4+Pj4+Pj4+Pj4+IC10Yw0KPj4+Pj4+Pj4+Pj4+PiBtdGYNCj4+Pj4+Pj4+Pj4+
Pj4gLw0KPj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4gVGhlIHN1Z2dlc3RlZCA0MDBtcyBmb3Ig
aW50ZXJhY3RpdmUgdm9pY2UgaXMgYXQgbGVhc3QgMnggdG9vDQo+Pj4+Pj4+PiBoaWdoLg0KPj4+
Pj4+Pj4+Pj4+IEkNCj4+Pj4+Pj4+Pj4+IGV4cGVjdA0KPj4+Pj4+Pj4+Pj4+IHRoYXQgbnVtYmVy
IGRvZXMgbm90IGluY2x1ZGUgdGhlIHBsYXlvdXQgaml0dGVyIGJ1ZmZlciAod2hpY2gNCj4+Pj4+
Pj4+Pj4+PiBpcyB2YXJpYWJsZSwNCj4+Pj4+Pj4+Pj4+IGJ1dA0KPj4+Pj4+Pj4+Pj4+IHVzdWFs
bHkgYSBmZXcgc2FtcGxlcywgc28gNDAtODBtcykuICAyMDBtcyBlbmQtdG8tZW5kIGlzIHRoZQ0K
Pj4+Pj4+Pj4+Pj4+IGhpZ2hlciBlbmQsDQo+Pj4+Pj4+Pj4+PiBhbmQNCj4+Pj4+Pj4+Pj4+PiB0
aGF0IGluY2x1ZGVzIGppdHRlciBidWZmZXIsIGNvZGVjIHByb2Nlc3NpbmcsIGFuZCBzbyBvbi4N
Cj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+IEJ1dCwgbW9yZSBpbXBvcnRhbnRseTogIGl0IHNl
ZW1zIHZhbHVhYmxlIGZvciBlbmRwb2ludHMgdG8NCj4+Pj4+Pj4+Pj4+PiBzaWduYWwgdGhlaXIg
bWF4aW11bSBkZWxheSBzb21laG93LiAgT3Igd291bGQgdGhlIFRDTVRGDQo+Pj4+Pj4+Pj4+Pj4g
ZnVuY3Rpb24NCj4+Pj4+Pj4+Pj4gZGV0ZXJtaW5lDQo+Pj4+Pj4+Pj4+Pj4gdGhlIG1heGltdW0g
ZGVsYXksIHVzaW5nIHNvbWUgaGV1cmlzdGljPw0KPj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4g
SG93IGRvZXMgdGhlIFRDTVRGIGZ1bmN0aW9uIGRldGVybWluZSBob3cgbXVjaCBvZiB0aGF0DQo+
Pj4+Pj4+Pj4+Pj4gJ3RvbGVyYWJsZSBsYXRlbmN5JyBidWRnZXQgaXQgY2FuIGNvbnN1bWU/DQo+
Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+PiAtZA0KPj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4N
Cj4+Pj4+Pj4+Pj4+Pj4gSXQgaXMgYW4gZXh0ZW5zaW9uIG9mIHRjbXRmDQo+Pj4+Pj4+Pj4+Pj4+
IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtDQo+Pj4+Pj4+Pj4+Pj4+IHNh
bGRhbmEtdHN2d2ctdGNtdGYvLiBTaW5jZSBhIHNwZWNpZmljIGxpc3QgZm9yIHRjbXRmIGV4aXN0
cw0KPj4+Pj4+Pj4+Pj4+PiAodGNtdGZAaWV0Zi5vcmcpLCB0aGUgaWRlYSBpcyB0byBkaXNjdXNz
IGl0IHRoZXJlLg0KPj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+Pg0K
Pj4+Pj4+Pj4+Pj4+PiBUaGUgZHJhZnQgY29udGFpbnMgcmVjb21tZW5kYXRpb25zIGZvciBUQ01U
RiBtdWx0aXBsZXhpbmcNCj4+Pj4+Pj4+Pj4+Pj4gcGVyaW9kIGZvciBkaWZmZXJlbnQgcmVhbC10
aW1lIHNlcnZpY2VzLiBJbiBvcmRlciB0byBwcmV2ZW50DQo+Pj4+Pj4+Pj4+Pj4+IFFvRSBkZWdy
YWRhdGlvbiBvZiByZWFsLXRpbWUgc2VydmljZXMgdXNpbmcgVENNVEYsIGEgcG9saWN5DQo+Pj4+
Pj4+Pj4+Pj4+IGRlZmluaW5nIGEgbXVsdGlwbGV4aW5nIHBlcmlvZCBjYW4gYmUgZW1wbG95ZWQu
IFZhbHVlcyBvZg0KPj4+Pj4+Pj4+Pj4+PiBtYXhpbXVtIHRvbGVyYWJsZSBkZWxheXMgcHJlc2Vu
dGVkIGluDQo+Pj4+Pj4+Pj4+Pj4gdGhlDQo+Pj4+Pj4+Pj4+Pj4+IGRyYWZ0IGZvcm0gdGhlIGJh
c2Ugb2Ygc3VjaCBwb2xpY3kuICAgIFRoZSByZWNvbW1lbmRhdGlvbnMNCj4+Pj4+PiBhcmUNCj4+
Pj4+Pj4+Pj4+IHByZXNlbnRlZA0KPj4+Pj4+Pj4+Pj4+PiBmb3IgcmVhbC10aW1lIG5ldHdvcmsg
c2VydmljZXMgaW4gd2hpY2ggVENUTUYgYmFuZHdpZHRoDQo+Pj4+Pj4+Pj4+Pj4+IG9wdGltaXph
dGlvbiBpcyBhcHBsaWNhYmxlIChpLmUuLCBzZXJ2aWNlcyAgd2hpY2ggaGF2ZSBsb3cNCj4+Pj4+
Pj4+Pj4+Pj4gcGF5bG9hZCB0byBoZWFkZXIgc2l6ZSByYXRpbyB3aGljaCByZXN1bHRzIGluIGhp
Z2ggcHJvdG9jb2wNCj4+Pj4+Pj4+IG92ZXJoZWFkKS4NCj4+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+
Pj4+Pj4NCj4+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+Pj4gWW91ciBmZWVkYmFjayB3aWxsIGJl
IHdlbGNvbWUuIFRoYW5rIHlvdS4NCj4+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+
Pj4+Pj4+Pj4gU2luY2VyZWx5LA0KPj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+PiBNaXJrbyBT
dXpuamV2aWMNCj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pj4gX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+Pj4+Pj4+Pj4+PiB0
Y210ZiBtYWlsaW5nIGxpc3QNCj4+Pj4+Pj4+Pj4+PiB0Y210ZkBpZXRmLm9yZw0KPj4+Pj4+Pj4+
Pj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCj4+Pj4+Pj4+
Pj4NCj4+Pj4+Pj4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4+Pj4+Pj4+Pj4gdGNtdGYgbWFpbGluZyBsaXN0DQo+Pj4+Pj4+Pj4+IHRjbXRmQGll
dGYub3JnDQo+Pj4+Pj4+Pj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
dGNtdGYNCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQo+Pj4+Pj4+Pj4gdGNtdGYgbWFpbGluZyBsaXN0DQo+Pj4+Pj4+
Pj4gdGNtdGZAaWV0Zi5vcmcNCj4+Pj4+Pj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3RjbXRmDQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gRXN0ZSBtZW5zYWplIHNl
IGRpcmlnZSBleGNsdXNpdmFtZW50ZSBhIHN1IGRlc3RpbmF0YXJpby4gUHVlZGUNCj4+Pj4+Pj4+
IGNvbnN1bHRhciBudWVzdHJhIHBvbMOtdGljYSBkZSBlbnbDrW8geSByZWNlcGNpw7NuIGRlIGNv
cnJlbw0KPj4+Pj4+Pj4gZWxlY3Ryw7NuaWNvIGVuIGVsIGVubGFjZSBzaXR1YWRvIG3DoXMgYWJh
am8uDQo+Pj4+Pj4+PiBUaGlzIG1lc3NhZ2UgaXMgaW50ZW5kZWQgZXhjbHVzaXZlbHkgZm9yIGl0
cyBhZGRyZXNzZWUuIFdlIG9ubHkNCj4+Pj4+Pj4+IHNlbmQgYW5kIHJlY2VpdmUgZW1haWwgb24g
dGhlIGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQgb3V0IGF0Og0KPj4+Pj4+Pj4gaHR0cDovL3d3dy50
aWQuZXMvRVMvUEFHSU5BUy9kaXNjbGFpbWVyLmFzcHgNCj4+Pj4+Pj4NCj4+Pj4+Pj4gX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+Pj4+Pj4gdGNtdGYg
bWFpbGluZyBsaXN0DQo+Pj4+Pj4+IHRjbXRmQGlldGYub3JnDQo+Pj4+Pj4+IGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCj4+Pj4+Pg0KPj4+Pj4+DQo+Pj4+Pj4g
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+Pj4+Pg0KPj4+Pj4+IEVzdGUgbWVu
c2FqZSBzZSBkaXJpZ2UgZXhjbHVzaXZhbWVudGUgYSBzdSBkZXN0aW5hdGFyaW8uIFB1ZWRlDQo+
Pj4+Pj4gY29uc3VsdGFyIG51ZXN0cmEgcG9sw610aWNhIGRlIGVudsOtbyB5IHJlY2VwY2nDs24g
ZGUgY29ycmVvDQo+Pj4+Pj4gZWxlY3Ryw7NuaWNvIGVuIGVsIGVubGFjZSBzaXR1YWRvIG3DoXMg
YWJham8uDQo+Pj4+Pj4gVGhpcyBtZXNzYWdlIGlzIGludGVuZGVkIGV4Y2x1c2l2ZWx5IGZvciBp
dHMgYWRkcmVzc2VlLiBXZSBvbmx5DQo+Pj4+Pj4gc2VuZCBhbmQgcmVjZWl2ZSBlbWFpbCBvbiB0
aGUgYmFzaXMgb2YgdGhlIHRlcm1zIHNldCBvdXQgYXQ6DQo+Pj4+Pj4gaHR0cDovL3d3dy50aWQu
ZXMvRVMvUEFHSU5BUy9kaXNjbGFpbWVyLmFzcHgNCj4+Pj4+DQo+Pj4+DQo+Pj4+DQo+Pj4+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4+DQo+Pj4+IEVzdGUgbWVuc2FqZSBz
ZSBkaXJpZ2UgZXhjbHVzaXZhbWVudGUgYSBzdSBkZXN0aW5hdGFyaW8uIFB1ZWRlDQo+Pj4+IGNv
bnN1bHRhciBudWVzdHJhIHBvbMOtdGljYSBkZSBlbnbDrW8geSByZWNlcGNpw7NuIGRlIGNvcnJl
byBlbGVjdHLDs25pY28NCj4+Pj4gZW4gZWwgZW5sYWNlIHNpdHVhZG8gbcOhcyBhYmFqby4NCj4+
Pj4gVGhpcyBtZXNzYWdlIGlzIGludGVuZGVkIGV4Y2x1c2l2ZWx5IGZvciBpdHMgYWRkcmVzc2Vl
LiBXZSBvbmx5IHNlbmQNCj4+Pj4gYW5kIHJlY2VpdmUgZW1haWwgb24gdGhlIGJhc2lzIG9mIHRo
ZSB0ZXJtcyBzZXQgb3V0IGF0Og0KPj4+PiBodHRwOi8vd3d3LnRpZC5lcy9FUy9QQUdJTkFTL2Rp
c2NsYWltZXIuYXNweA0KPj4+DQo+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCj4+PiB0Y210ZiBtYWlsaW5nIGxpc3QNCj4+PiB0Y210ZkBpZXRmLm9y
Zw0KPj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCj4+Pg0K
Pj4NCj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
PiB0Y210ZiBtYWlsaW5nIGxpc3QNCj4+IHRjbXRmQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQo+DQoNCl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQp0Y210ZiBtYWlsaW5nIGxpc3QNCnRjbXRmQGll
dGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQo=

From jsaldana@unizar.es  Wed Jan 23 03:58:52 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7E5A21F8732 for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 03:58:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.568
X-Spam-Level: 
X-Spam-Status: No, score=-6.568 tagged_above=-999 required=5 tests=[AWL=0.030,  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 FkPkkmR1zSIN for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 03:58:51 -0800 (PST)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id EE1D721F8A6C for <tcmtf@ietf.org>; Wed, 23 Jan 2013 03:58:50 -0800 (PST)
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 r0NBwi1m015168; Wed, 23 Jan 2013 12:58:44 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 23 Jan 2013 12:58:54 +0100
Organization: Universidad de Zaragoza
Message-ID: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0079_01CDF969.66ACB7D0"
X-Mailer: Microsoft Outlook 14.0
Content-language: es
Thread-index: Ac35YPWFYtkaxKqFS8i6lSjqRjQ45g==
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Wesley Eddy <wes@mti-systems.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 23 Jan 2013 11:58:52 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0079_01CDF969.66ACB7D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello all.

 

After reading the messages in the mailing list, I think we have arrived to a
solution. Each of the documents has been discussed in a separate thread, so
I have tried to take everything into account. Documents (A) and (B) would be
in the Charter. Documents (C) and (D) would only be announced as
possibilities for re-chartering, and Document (E) can wait a little.

 

We can now try to polish this text. If you agree, please report it in the
list.

 

So this is the new charter proposal:

 

*Description of Working Group* v3

 

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 higher when IPv6 is used, since 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 sending collected data in sensor networks).

 

2. In order to improve network efficiency, packets can be grouped when a
number of flows share a path, 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 then necessary at the end of the common path, so as to
rebuild the packets as they were originally sent. PPPMux will be the main
option. Other ones are not discarded.

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

 

3. So the first objective of this group is to develop a document (A) that
will specify the protocol stack for tunneling, compressing and multiplexing
traffic flows (TCMTF). Since other standard protocols are being used, each
layer will use the signaling methods of those protocols. In addition, since
document (A) would include, as one of the options, the current RFC 4170,
this RFC could 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
compressing, multiplexing or tunneling protocols. 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. If a pair multiplexer/de- multiplexer want to establish a tunnel, they
have first to use a mechanism to negotiate which concrete option would they
use in each layer: header compression, multiplexing and tunneling. This will
depend on the protocols each of them implements at each level, and in the
scenario. So document (A) will also include a negotiation mechanism to
decide the options at each layer (header compression, multiplexing and
tunneling) between multiplexer and de-multiplexer, and a mechanism to
setup/release a tunnel between a multiplexer and a de-multiplexer.

 

6. As a counterpart of the bandwidth saving, TCMTF may add some delay and
jitter. This is not a problem for the services which are not sensitive to
delay. However, regarding delay-sensitive services, the Working Group will
also develop a document (B) with useful recommendations in order to decide
which packet flows can or can not be multiplexed and how: the use of
available traffic classification methods; the maximum delay and jitter to be
added to each kind of service or application. Other recommendations will be
included if necessary. Empirical studies will be necessary in order to
establish this set of recommendations.

 

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

 

8. In addition, specific uses of TCMTF, such as wireless and satellite
scenarios could be considered and addressed if some modifications are
required on the protocol.

 

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

 

*Goals and Milestones*

 

Specification of TCMTF protocol stack (A) and signaling mechanisms.

 

Recommendations (B) of using existing traffic classification methods,
maximum delay and jitter to add, depending on the service.

 

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

 

Best regards, and thanks for your wonderful work,

 

Jose 

 


------=_NextPart_000_0079_01CDF969.66ACB7D0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>Hello all.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>After reading the messages in the mailing list, I think we =
have arrived to a solution. Each of the documents has been discussed in =
a separate thread, so I have tried to take everything into account. =
Documents (A) and (B) would be in the Charter. Documents (C) and (D) =
would only be announced as possibilities for re-chartering, and Document =
(E) can wait a little.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>We can now try to polish this text. If you agree, please =
report it in the list.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>So this is the new charter =
proposal:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>*<b>Description of Working Group</b>* =
v3<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>1. 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 higher when =
IPv6 is used, since 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 sending =
collected data in sensor networks).<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>2. In order to improve network =
efficiency, packets can be grouped when a number of flows share a path, =
considering three different layers:<o:p></o:p></span></p><p =
class=3DMsoNormal><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=3DMsoNormal><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 then necessary at the end of =
the common path, so as to rebuild the packets as they were originally =
sent. PPPMux will be the main option. Other ones are not =
discarded.<o:p></o:p></span></p><p class=3DMsoNormal><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=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><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 tunneling, =
compressing and multiplexing traffic flows (TCMTF). Since other standard =
protocols are being used, each layer will use the signaling methods of =
those protocols. In addition, since document (A) would include, as one =
of the options, the current RFC 4170, this RFC could be =
obsoleted.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>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 compressing, multiplexing or tunneling protocols. =
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=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>5. If a pair multiplexer/de- multiplexer want to establish =
a tunnel, they have first to use a mechanism to negotiate which concrete =
option would they use in each layer: header compression, multiplexing =
and tunneling. This will depend on the protocols each of them implements =
at each level, and in the scenario. So document (A) will also include a =
negotiation mechanism to decide the options at each layer (header =
compression, multiplexing and tunneling) between multiplexer and =
de-multiplexer, and a mechanism to setup/release a tunnel between a =
multiplexer and a de-multiplexer.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>6. As a counterpart of the =
bandwidth saving, TCMTF may add some delay and jitter. This is not a =
problem for the services which are not sensitive to delay. However, =
regarding delay-sensitive services, the Working Group will also develop =
a document (B) with useful recommendations in order to decide which =
packet flows can or can not be multiplexed and how: the use of available =
traffic classification methods; the maximum delay and jitter to be added =
to each kind of service or application. Other recommendations will be =
included if necessary. Empirical studies will be necessary in order to =
establish this set of recommendations.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>7. If other interesting features =
are identified, the group would re-charter and include them, e.g., a =
mechanism for a multiplexer to discover a de-multiplexer, and vice =
versa; a mechanism to select an optimal multiplexer and a de-multiplexer =
when there are more than one muxer/de-muxer for a flow; dynamically =
applying TCMTF: a higher entity in charge of deciding when and where, =
applying or not TCMTF, and what kind of TCMTF, and what multiplexing =
period. Additional methods for estimating delay would also be =
required.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>8. In addition, specific uses of TCMTF, such as wireless =
and satellite scenarios could be considered and addressed if some =
modifications are required on the protocol.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>9. 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=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>*<b>Goals and =
Milestones</b>*<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Specification of TCMTF protocol stack (A) and signaling =
mechanisms.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Recommendations (B) of using existing traffic =
classification methods, maximum delay and jitter to add, depending on =
the service.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>------------------------------------<o:p></o:p></span></p><p=
 class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Best regards, and thanks for your =
wonderful work,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-la=
nguage:ES'>Jose <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_0079_01CDF969.66ACB7D0--


From Matteo.Berioli@dlr.de  Wed Jan 23 04:24:29 2013
Return-Path: <Matteo.Berioli@dlr.de>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B16521F8940 for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 04:24:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.248
X-Spam-Level: 
X-Spam-Status: No, score=-10.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 38B+0J1AVV8I for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 04:24:28 -0800 (PST)
Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.32]) by ietfa.amsl.com (Postfix) with ESMTP id BF37121F8933 for <tcmtf@ietf.org>; Wed, 23 Jan 2013 04:24:27 -0800 (PST)
Received: from DLREXHUB02.intra.dlr.de (172.21.152.140) by dlrexedge01.dlr.de (172.21.163.100) with Microsoft SMTP Server (TLS) id 14.2.328.9; Wed, 23 Jan 2013 13:24:01 +0100
Received: from DLREXMBX02.intra.dlr.de ([fe80::8cc6:b83e:ddc1:4e8b]) by dlrexhub02.intra.dlr.de ([::1]) with mapi id 14.02.0328.009; Wed, 23 Jan 2013 13:24:04 +0100
From: <Matteo.Berioli@dlr.de>
To: <jsaldana@unizar.es>, <tcmtf@ietf.org>
Thread-Topic: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
Thread-Index: Ac35YPWFYtkaxKqFS8i6lSjqRjQ45gAA0MtA
Date: Wed, 23 Jan 2013 12:24:04 +0000
Message-ID: <48DB40641BACF54C892EB0A12B4733C10BEEB504@dlrexmbx02.intra.dlr.de>
References: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
In-Reply-To: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.247.173.107]
Content-Type: multipart/alternative; boundary="_000_48DB40641BACF54C892EB0A12B4733C10BEEB504dlrexmbx02intra_"
MIME-Version: 1.0
Cc: wes@mti-systems.com, Gonzalo.Camarillo@ericsson.com, Martin.Stiemerling@neclab.eu
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 23 Jan 2013 12:24:29 -0000

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

Point 8 is ok for us.
Here a slight modification:

8. In addition, specific uses of TCMTF, such as in wireless and satellite s=
cenarios, could be considered, and it will be studied whether modifications=
 or extensions are required on the protocol.

Regards,

Matteo


From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of J=
ose Saldana
Sent: 23 January 2013 12:59
To: tcmtf@ietf.org
Cc: Wesley Eddy; Gonzalo Camarillo; Martin Stiemerling
Subject: [tcmtf] Improved version of the TCMTF Charter proposal (v3)

Hello all.

After reading the messages in the mailing list, I think we have arrived to =
a solution. Each of the documents has been discussed in a separate thread, =
so I have tried to take everything into account. Documents (A) and (B) woul=
d be in the Charter. Documents (C) and (D) would only be announced as possi=
bilities for re-chartering, and Document (E) can wait a little.

We can now try to polish this text. If you agree, please report it in the l=
ist.

So this is the new charter proposal:

*Description of Working Group* v3

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 applicatio=
ns: VoIP, videoconferencing, telemedicine, video vigilance, online gaming, =
etc. Due to the need of interactivity, many of these services use small pac=
kets (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 higher when IPv6 is used, since the basic IPv6 header =
is twice the size of the IPv4 one. In addition, some other services also se=
nd small packets, but they are not delay-sensitive (e.g., instant messaging=
, m2m packets sending collected data in sensor networks).

2. In order to improve network efficiency, packets can be grouped when a nu=
mber of flows share a path, considering three different layers:
- Header compression: Taking into account that real-time applications use d=
ifferent headers (RTP/UDP, UDP or even TCP), different protocols can be use=
d: no compression, ECRTP, IPHC and ROHC.
- Multiplexing a number of payloads into a single packet. If a number of fl=
ows share a path between an origin and a destination, a multiplexer can bui=
ld a bigger packet in which a number of payloads share a common header. A d=
emultiplexer is then necessary at the end of the common path, so as to rebu=
ild the packets as they were originally sent. PPPMux will be the main optio=
n. Other ones are not discarded.
- Tunneling will be used to send the multiplexed packets end-to-end. The op=
tions in this layer are L2TP, GRE and MPLS.

3. So the first objective of this group is to develop a document (A) that w=
ill specify the protocol stack for tunneling, compressing and multiplexing =
traffic flows (TCMTF). Since other standard protocols are being used, each =
layer will use the signaling methods of those protocols. In addition, since=
 document (A) would include, as one of the options, the current RFC 4170, t=
his RFC could be obsoleted.

4. The objective of this first document (A) is to define the different opti=
ons which can be used at each layer, not the definition of new compressing,=
 multiplexing or tunneling protocols. Specific problems caused by the inter=
action between layers will have to be issued, and suitable extensions may h=
ave to be added to the involved protocols.

5. If a pair multiplexer/de- multiplexer want to establish a tunnel, they h=
ave first to use a mechanism to negotiate which concrete option would they =
use in each layer: header compression, multiplexing and tunneling. This wil=
l depend on the protocols each of them implements at each level, and in the=
 scenario. So document (A) will also include a negotiation mechanism to dec=
ide the options at each layer (header compression, multiplexing and tunneli=
ng) between multiplexer and de-multiplexer, and a mechanism to setup/releas=
e a tunnel between a multiplexer and a de-multiplexer.

6. As a counterpart of the bandwidth saving, TCMTF may add some delay and j=
itter. This is not a problem for the services which are not sensitive to de=
lay. However, regarding delay-sensitive services, the Working Group will al=
so develop a document (B) with useful recommendations in order to decide wh=
ich packet flows can or can not be multiplexed and how: the use of availabl=
e traffic classification methods; the maximum delay and jitter to be added =
to each kind of service or application. Other recommendations will be inclu=
ded if necessary. Empirical studies will be necessary in order to establish=
 this set of recommendations.

7. If other interesting features are identified, the group would re-charter=
 and include them, e.g., a mechanism for a multiplexer to discover a de-mul=
tiplexer, and vice versa; a mechanism to select an optimal multiplexer and =
a de-multiplexer when there are more than one muxer/de-muxer for a flow; dy=
namically applying TCMTF: a higher entity in charge of deciding when and wh=
ere, applying or not TCMTF, and what kind of TCMTF, and what multiplexing p=
eriod. Additional methods for estimating delay would also be required.

8. In addition, specific uses of TCMTF, such as wireless and satellite scen=
arios could be considered and addressed if some modifications are required =
on the protocol.

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

*Goals and Milestones*

Specification of TCMTF protocol stack (A) and signaling mechanisms.

Recommendations (B) of using existing traffic classification methods, maxim=
um delay and jitter to add, depending on the service.

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

Best regards, and thanks for your wonderful work,

Jose


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin: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;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Point 8 is ok for us.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Here a slight modifica=
tion:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal">8. In addition, specific uses of TCMTF, such as in w=
ireless and satellite scenarios, could be considered, and it will be studie=
d whether modifications or extensions are required on the protocol.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Matteo<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tcmtf-bo=
unces@ietf.org [mailto:tcmtf-bounces@ietf.org]
<b>On Behalf Of </b>Jose Saldana<br>
<b>Sent:</b> 23 January 2013 12:59<br>
<b>To:</b> tcmtf@ietf.org<br>
<b>Cc:</b> Wesley Eddy; Gonzalo Camarillo; Martin Stiemerling<br>
<b>Subject:</b> [tcmtf] Improved version of the TCMTF Charter proposal (v3)=
<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hello all.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">After reading the messages in the mailing list, I th=
ink we have arrived to a solution. Each of the documents has been discussed=
 in a separate thread, so I have tried to take everything into account. Doc=
uments (A) and (B) would be in the
 Charter. Documents (C) and (D) would only be announced as possibilities fo=
r re-chartering, and Document (E) can wait a little.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We can now try to polish this text. If you agree, pl=
ease report it in the list.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So this is the new charter proposal:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">*<b>Description of Working Group</b>* v3<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">1. In the last years we are witnessing the raise of =
new real-time services that use the Internet for the delivery of interactiv=
e multimedia applications: VoIP, videoconferencing, telemedicine, video vig=
ilance, 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 extre=
me of the communication. Therefore, its overhead is significant, and it bec=
omes even higher when IPv6 is used,
 since 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-sensi=
tive (e.g., instant messaging, m2m packets sending collected data in sensor=
 networks).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">2. In order to improve network efficiency, packets c=
an be grouped when a number of flows share a path, considering three differ=
ent layers:<o:p></o:p></p>
<p class=3D"MsoNormal">- Header compression: Taking into account that real-=
time applications use different headers (RTP/UDP, UDP or even TCP), differe=
nt protocols can be used: no compression, ECRTP, IPHC and ROHC.<o:p></o:p><=
/p>
<p class=3D"MsoNormal">- Multiplexing a number of payloads into a single pa=
cket. 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 sha=
re a common header. A demultiplexer
 is then necessary at the end of the common path, so as to rebuild the pack=
ets as they were originally sent. PPPMux will be the main option. Other one=
s are not discarded.<o:p></o:p></p>
<p class=3D"MsoNormal">- Tunneling will be used to send the multiplexed pac=
kets end-to-end. The options in this layer are L2TP, GRE and MPLS.<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">3. So the first objective of this group is to develo=
p a document (A) that will specify the protocol stack for tunneling, compre=
ssing and multiplexing traffic flows (TCMTF). Since other standard protocol=
s are being used, each layer will
 use the signaling methods of those protocols. In addition, since document =
(A) would include, as one of the options, the current RFC 4170, this RFC co=
uld be obsoleted.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">4. The objective of this first document (A) is to de=
fine the different options which can be used at each layer, not the definit=
ion of new compressing, multiplexing or tunneling protocols. Specific probl=
ems caused by the interaction between
 layers will have to be issued, and suitable extensions may have to be adde=
d to the involved protocols.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">5. If a pair multiplexer/de- multiplexer want to est=
ablish a tunnel, they have first to use a mechanism to negotiate which conc=
rete option would they use in each layer: header compression, multiplexing =
and tunneling. This will depend on
 the protocols each of them implements at each level, and in the scenario. =
So document (A) will also include a negotiation mechanism to decide the opt=
ions at each layer (header compression, multiplexing and tunneling) between=
 multiplexer and de-multiplexer,
 and a mechanism to setup/release a tunnel between a multiplexer and a de-m=
ultiplexer.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">6. As a counterpart of the bandwidth saving, TCMTF m=
ay add some delay and jitter. This is not a problem for the services which =
are not sensitive to delay. However, regarding delay-sensitive services, th=
e Working Group will also develop
 a document (B) with useful recommendations in order to decide which packet=
 flows can or can not be multiplexed and how: the use of available traffic =
classification methods; the maximum delay and jitter to be added to each ki=
nd of service or application. Other
 recommendations will be included if necessary. Empirical studies will be n=
ecessary in order to establish this set of recommendations.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">7. If other interesting features are identified, the=
 group would re-charter and include them, e.g., a mechanism for a multiplex=
er to discover a de-multiplexer, and vice versa; a mechanism to select an o=
ptimal multiplexer and a de-multiplexer
 when there are more than one muxer/de-muxer for a flow; dynamically applyi=
ng TCMTF: a higher entity in charge of deciding when and where, applying or=
 not TCMTF, and what kind of TCMTF, and what multiplexing period. Additiona=
l methods for estimating delay would
 also be required.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">8. In addition, specific uses of TCMTF, such as wire=
less and satellite scenarios could be considered and addressed if some modi=
fications are required on the protocol.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">9. Interactions with other groups can be expected, s=
ince TCMTF uses already defined protocols (ROHC, PPPMux, MPLS, GRE, L2TP).<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">*<b>Goals and Milestones</b>*<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Specification of TCMTF protocol stack (A) and signal=
ing mechanisms.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Recommendations (B) of using existing traffic classi=
fication methods, maximum delay and jitter to add, depending on the service=
.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">------------------------------------<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best regards, and thanks for your wonderful work,<o:=
p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;mso-fareast-language:ES">Jose
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_48DB40641BACF54C892EB0A12B4733C10BEEB504dlrexmbx02intra_--

From diego@tid.es  Wed Jan 23 05:59:43 2013
Return-Path: <diego@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B79821F87BA for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 05:59:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.11
X-Spam-Level: 
X-Spam-Status: No, score=-5.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 vXuCyAjwAtKJ for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 05:59:42 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3A03021F8751 for <tcmtf@ietf.org>; Wed, 23 Jan 2013 05:59:42 -0800 (PST)
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 <0MH30093T07GXB@tid.hi.inet> for tcmtf@ietf.org; Wed, 23 Jan 2013 14:59:41 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id ED.86.03184.CCCEFF05; Wed, 23 Jan 2013 14:59:40 +0100 (CET)
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 <0MH30093M07GXB@tid.hi.inet> for tcmtf@ietf.org; Wed, 23 Jan 2013 14:59:40 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.165]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0328.009; Wed, 23 Jan 2013 14:59:40 +0100
Date: Wed, 23 Jan 2013 13:59:40 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "<jsaldana@unizar.es>" <jsaldana@unizar.es>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A0468D29F3D@EX10-MB2-MAD.hi.inet>
Content-id: <8DFB9D014D5D464EB81BDEF168D89C70@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=Windows-1252
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
Thread-index: Ac35YPWFYtkaxKqFS8i6lSjqRjQ45gACIsyA
X-AuditID: 0a5f4068-b7fc06d000000c70-1d-50ffecccaafd
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHKsWRmVeSWpSXmKPExsXCFe/ApXvmzf8Agw1rTC12fd7A6MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujCPnOpkKOrkqNnbPZ2tgbOHoYuTkkBAwkXiypIsJwhaTuHBv PVsXIxeHkMAGRonW7h+MEM4PRomJ21czQTgzGSXeTJ3LCNLCIqAqsf/YSXYQmw3IftT8G8wW FvCQOHX2BjOIzSlgIfHm6n42iBUKEn/OPWYBsUUE9CVuPAap5+JgFtjKKLFs5jlWkASvgLfE 6pePwBYwC5hJXDp6hB0iLijxY/I9Foi4nsTHP7ehasQlmltvQsW1JZ68uwA2hxHon++n1gBd zQG0zFNi1zFJiL1GEue7brNA3CMgsWTPeWYIW1Ti5eN/YK1CAuYSez99ZpvAKDELyRWzkFwx C8kVs5BcMQvJFQsYWVcxihUnFWWmZ5TkJmbmpBsY6mVk6mXmpZZsYoREXsYOxuU7VQ4xCnAw KvHwVtz5HyDEmlhWXJl7iFGSg0lJlFcFGLdCfEn5KZUZicUZ8UWlOanFhxglOJiVRHhlnwLl eFMSK6tSi/JhUjIcHEoSvHYgbYJFqempFWmZOcD0ApNm4uAEaecBancCqeEtLkjMLc5Mh8if YpSUEucVA0kIgCQySvPgel8xigMdKczrB5LlASZCuK5XQAOZgAbunwU2sCQRISXVwDgr+MK/ bQduR2b8kS3fbhXfnfxyzgz18Pul3qZG57ptzK+/mJRncVqLW/Jc0qtTRya6qfid+R/J9rb3 gfrG6w8+OB9NTRVPKl5SNPO5Uav03muJZRk9/RuPbsqS0D3R4Gb+zFi9ftKxqtL+L9FvT/27 vM726bns5pln3lblL2BQyH21LaJS7o0SS3FGoqEWc1FxIgCaBphgQQMAAA==
References: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
Cc: "<tcmtf@ietf.org>" <tcmtf@ietf.org>, Wesley Eddy <wes@mti-systems.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 23 Jan 2013 13:59:43 -0000

Hi,

I see nothing to object. I'd propose to go for it=85

Be goode,

On 23 Jan 2013, at 12:58 , Jose Saldana wrote:

> Hello all.
>
> After reading the messages in the mailing list, I think we have arrived t=
o a solution. Each of the documents has been discussed in a separate thread=
, so I have tried to take everything into account. Documents (A) and (B) wo=
uld be in the Charter. Documents (C) and (D) would only be announced as pos=
sibilities for re-chartering, and Document (E) can wait a little.
>
> We can now try to polish this text. If you agree, please report it in the=
 list.
>
> So this is the new charter proposal:

--
"Esta vez no fallaremos, Doctor Infierno"

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

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


________________________________

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

From Mirko.Suznjevic@fer.hr  Wed Jan 23 07:06:08 2013
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 4774221F8686 for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 07:06:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 JzfGjfecz23b for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 07:06:04 -0800 (PST)
Received: from mail.zvne.fer.hr (mail.zvne.fer.hr [161.53.66.5]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED5421F867D for <tcmtf@ietf.org>; Wed, 23 Jan 2013 07:05:57 -0800 (PST)
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.318.4; Wed, 23 Jan 2013 16:05:55 +0100
Received: from sluga.fer.hr ([161.53.66.244]) by munja.zvne.fer.hr with Microsoft SMTPSVC(6.0.3790.4675);	 Wed, 23 Jan 2013 16:05:47 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CDF97B.2019C8F0"
Date: Wed, 23 Jan 2013 16:05:48 +0100
Message-ID: <A3179A2C9AAEE647BE70AC4C7881D5FB0177636F@sluga.fer.hr>
In-Reply-To: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
Thread-Index: Ac35YPWFYtkaxKqFS8i6lSjqRjQ45gAGLQlw
References: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: <jsaldana@unizar.es>, <tcmtf@ietf.org>
X-OriginalArrivalTime: 23 Jan 2013 15:05:47.0965 (UTC) FILETIME=[202BD6D0:01CDF97B]
Cc: Wesley Eddy <wes@mti-systems.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 23 Jan 2013 15:06:08 -0000

------_=_NextPart_001_01CDF97B.2019C8F0
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

Hello everybody,

The document seems fine to me.

=20

Only this sentence seems a bit confusing. I had to re-read it a couple =
of times:

"However, regarding delay-sensitive services, the Working Group will =
also develop a document (B) with useful recommendations in order to =
decide which packet flows can or can not be multiplexed and how: the use =
of available traffic classification methods; the maximum delay and =
jitter to be added to each kind of service or application. "=20

=20

Maybe it can be split into multiple sentences?=20

E.g., However, regarding delay-sensitive services, the Working Group =
will also develop a document (B) with useful recommendations in order to =
decide which packet flows can or can not be multiplexed and how. The =
document (B) will present a list of available traffic classification =
methods which can be used for identification of the service or =
application of a particular flow, as well as the recommendations of  the =
maximum delay and jitter to be added depending of the identified service =
or application.

=20

Cheers!

Mirko.

=20

From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf =
Of Jose Saldana
Sent: Wednesday, January 23, 2013 12:59 PM
To: tcmtf@ietf.org
Cc: Wesley Eddy; Gonzalo Camarillo; Martin Stiemerling
Subject: [tcmtf] Improved version of the TCMTF Charter proposal (v3)

=20

Hello all.

=20

After reading the messages in the mailing list, I think we have arrived =
to a solution. Each of the documents has been discussed in a separate =
thread, so I have tried to take everything into account. Documents (A) =
and (B) would be in the Charter. Documents (C) and (D) would only be =
announced as possibilities for re-chartering, and Document (E) can wait =
a little.

=20

We can now try to polish this text. If you agree, please report it in =
the list.

=20

So this is the new charter proposal:

=20

*Description of Working Group* v3

=20

1. In the last years we are witnessing the raise of new real-time =
services that use the Internet for the delivery of interactive =
multimedia applications: VoIP, videoconferencing, telemedicine, video =
vigilance, online gaming, etc. Due to the need of interactivity, many of =
these services use small packets (some tens of bytes), since they have =
to send frequent updates to the other extreme of the communication. =
Therefore, its overhead is significant, and it becomes even higher when =
IPv6 is used, since 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 sending =
collected data in sensor networks).

=20

2. In order to improve network efficiency, packets can be grouped when a =
number of flows share a path, 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 then necessary at the end of the common path, =
so as to rebuild the packets as they were originally sent. PPPMux will =
be the main option. Other ones are not discarded.

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

=20

3. So the first objective of this group is to develop a document (A) =
that will specify the protocol stack for tunneling, compressing and =
multiplexing traffic flows (TCMTF). Since other standard protocols are =
being used, each layer will use the signaling methods of those =
protocols. In addition, since document (A) would include, as one of the =
options, the current RFC 4170, this RFC could be obsoleted.

=20

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 =
compressing, multiplexing or tunneling protocols. Specific problems =
caused by the interaction between layers will have to be issued, and =
suitable extensions may have to be added to the involved protocols.

=20

5. If a pair multiplexer/de- multiplexer want to establish a tunnel, =
they have first to use a mechanism to negotiate which concrete option =
would they use in each layer: header compression, multiplexing and =
tunneling. This will depend on the protocols each of them implements at =
each level, and in the scenario. So document (A) will also include a =
negotiation mechanism to decide the options at each layer (header =
compression, multiplexing and tunneling) between multiplexer and =
de-multiplexer, and a mechanism to setup/release a tunnel between a =
multiplexer and a de-multiplexer.

=20

6. As a counterpart of the bandwidth saving, TCMTF may add some delay =
and jitter. This is not a problem for the services which are not =
sensitive to delay. However, regarding delay-sensitive services, the =
Working Group will also develop a document (B) with useful =
recommendations in order to decide which packet flows can or can not be =
multiplexed and how: the use of available traffic classification =
methods; the maximum delay and jitter to be added to each kind of =
service or application. Other recommendations will be included if =
necessary. Empirical studies will be necessary in order to establish =
this set of recommendations.

=20

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

=20

8. In addition, specific uses of TCMTF, such as wireless and satellite =
scenarios could be considered and addressed if some modifications are =
required on the protocol.

=20

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

=20

*Goals and Milestones*

=20

Specification of TCMTF protocol stack (A) and signaling mechanisms.

=20

Recommendations (B) of using existing traffic classification methods, =
maximum delay and jitter to add, depending on the service.

=20

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

=20

Best regards, and thanks for your wonderful work,

=20

Jose=20

=20


------_=_NextPart_001_01CDF97B.2019C8F0
Content-Type: text/html; charset="iso-8859-2"
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-2"><meta name=3DGenerator content=3D"Microsoft Word =
12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{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=3DHR link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Hello =
everybody,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>The document seems fine to =
me.<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'>Only this =
sentence seems a bit confusing. I had to re-read it a couple of =
times:<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>&#8220;</span><span lang=3DEN-US>However, =
regarding delay-sensitive services, the Working Group will also develop =
a document (B) with useful recommendations in order to decide which =
packet flows can or can not be multiplexed and how: the use of available =
traffic classification methods; the maximum delay and jitter to be added =
to each kind of service or application.</span><span lang=3DEN-US =
style=3D'color:#1F497D'> &#8220; <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'>Maybe it =
can be split into multiple sentences? <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>E.g., =
</span><span lang=3DEN-US>However, regarding delay-sensitive services, =
the Working Group will also develop a document (B) with useful =
recommendations in order to decide which packet flows can or can not be =
multiplexed and how. The document (B) will present a list of available =
traffic classification methods which can be used for identification of =
the service or application of a particular flow, as well as the =
recommendations of=A0 the maximum delay and jitter to be added depending =
of the identified service or application.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Cheers!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Mirko.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] <b>On Behalf Of =
</b>Jose Saldana<br><b>Sent:</b> Wednesday, January 23, 2013 12:59 =
PM<br><b>To:</b> tcmtf@ietf.org<br><b>Cc:</b> Wesley Eddy; Gonzalo =
Camarillo; Martin Stiemerling<br><b>Subject:</b> [tcmtf] Improved =
version of the TCMTF Charter proposal =
(v3)<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Hello all.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>After reading the messages in the mailing list, I think we =
have arrived to a solution. Each of the documents has been discussed in =
a separate thread, so I have tried to take everything into account. =
Documents (A) and (B) would be in the Charter. Documents (C) and (D) =
would only be announced as possibilities for re-chartering, and Document =
(E) can wait a little.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>We can now try to polish this text. If you agree, please =
report it in the list.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>So this is the new charter =
proposal:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>*<b>Description of Working Group</b>* =
v3<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>1. 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 higher when =
IPv6 is used, since 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 sending =
collected data in sensor networks).<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>2. In order to improve network =
efficiency, packets can be grouped when a number of flows share a path, =
considering three different layers:<o:p></o:p></span></p><p =
class=3DMsoNormal><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=3DMsoNormal><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 then necessary at the end of =
the common path, so as to rebuild the packets as they were originally =
sent. PPPMux will be the main option. Other ones are not =
discarded.<o:p></o:p></span></p><p class=3DMsoNormal><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=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><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 tunneling, =
compressing and multiplexing traffic flows (TCMTF). Since other standard =
protocols are being used, each layer will use the signaling methods of =
those protocols. In addition, since document (A) would include, as one =
of the options, the current RFC 4170, this RFC could be =
obsoleted.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>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 compressing, multiplexing or tunneling protocols. =
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=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>5. If a pair multiplexer/de- multiplexer want to establish =
a tunnel, they have first to use a mechanism to negotiate which concrete =
option would they use in each layer: header compression, multiplexing =
and tunneling. This will depend on the protocols each of them implements =
at each level, and in the scenario. So document (A) will also include a =
negotiation mechanism to decide the options at each layer (header =
compression, multiplexing and tunneling) between multiplexer and =
de-multiplexer, and a mechanism to setup/release a tunnel between a =
multiplexer and a de-multiplexer.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>6. As a counterpart of the =
bandwidth saving, TCMTF may add some delay and jitter. This is not a =
problem for the services which are not sensitive to delay. However, =
regarding delay-sensitive services, the Working Group will also develop =
a document (B) with useful recommendations in order to decide which =
packet flows can or can not be multiplexed and how: the use of available =
traffic classification methods; the maximum delay and jitter to be added =
to each kind of service or application. Other recommendations will be =
included if necessary. Empirical studies will be necessary in order to =
establish this set of recommendations.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>7. If other interesting features =
are identified, the group would re-charter and include them, e.g., a =
mechanism for a multiplexer to discover a de-multiplexer, and vice =
versa; a mechanism to select an optimal multiplexer and a de-multiplexer =
when there are more than one muxer/de-muxer for a flow; dynamically =
applying TCMTF: a higher entity in charge of deciding when and where, =
applying or not TCMTF, and what kind of TCMTF, and what multiplexing =
period. Additional methods for estimating delay would also be =
required.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>8. In addition, specific uses of TCMTF, such as wireless =
and satellite scenarios could be considered and addressed if some =
modifications are required on the protocol.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>9. 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=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>*<b>Goals and =
Milestones</b>*<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Specification of TCMTF protocol stack (A) and signaling =
mechanisms.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Recommendations (B) of using existing traffic =
classification methods, maximum delay and jitter to add, depending on =
the service.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>------------------------------------<o:p></o:p></span></p><p=
 class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Best regards, and thanks for your =
wonderful work,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Jose =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------_=_NextPart_001_01CDF97B.2019C8F0--

From fpb@tid.es  Wed Jan 23 09:06:27 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 387F821F8586 for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 09:06:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XBQl6Ujez4ZJ for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 09:06:25 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 25A4C21F874F for <tcmtf@ietf.org>; Wed, 23 Jan 2013 09:06:19 -0800 (PST)
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 <0MH30047W8UCZ8@tid.hi.inet> for tcmtf@ietf.org; Wed, 23 Jan 2013 18:06:14 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 60.2D.03184.68810015; Wed, 23 Jan 2013 18:06:14 +0100 (CET)
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 <0MH3001M08UDQ0@tid.hi.inet> for tcmtf@ietf.org; Wed, 23 Jan 2013 18:06:13 +0100 (MET)
Received: from EX10-HTCAS7-MAD.hi.inet (10.95.73.94) by ex10-htcas4-mad.hi.inet (10.95.73.91) with Microsoft SMTP Server (TLS) id 14.2.328.9; Wed, 23 Jan 2013 18:06:13 +0100
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.165]) by EX10-HTCAS7-MAD.hi.inet ([fe80::4ccc:bab7:84dc:7c6e%15]) with mapi id 14.02.0328.009; Wed, 23 Jan 2013 18:06:13 +0100
Date: Wed, 23 Jan 2013 17:06:13 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A2689ED647@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_4f18qIFBQxr/s31gFf107g)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
Thread-index: Ac35YPWFYtkaxKqFS8i6lSjqRjQ45gAKwYMA
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4068-b7fc06d000000c70-17-510018863543
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA02SbUhTYRTHe/bmdXrjOp07vqyXYV9czpdMDEKEyIw+NKkICtIru+2Otim7 01TCjNTCtJTeZCZLnIoiphJhlin7IGSmQgi6lQaCmooRy3xBrHt3p+3bj/P/n/M/D8/BhLI5 cSRmMFspi5k0qiRSkTQ7XRpXCfuyEtztQan9nm6UjjIdjk2BFl2RntRRRkMhZYlPy5HSbX3T ovyPdaio9fWEuAw9v1WFAjEZEQHff61JOAYiGbrb3YjncJiYecXWpaynG8HaaqOYb9hAMPv7 Mi/0IFjvnA/ghV4EY00yjkXEEfBU1HjrEiIWPn3rEHEcSmTCyOcpIceBRCqsTA76kg/B9tic 1xNGaOFd+ZCXhUQtggZ3NMc4cQ48H6YFPIfAxuMZn8cE9q4tIc8KuFsx7a0jQgmrdju7NMbO PAv9wxH8+CRwDvZ57XJCA5XDowH8CgQ43o8LeZbDj7kdMRtu80uz+aXZ/NJ41sDU0ycSntXQ 2rTs88RB/Y7T50mBF8/Gkb/nJcI6UDiTazHoaauJNBj1CYka2qAxmClrL+L/l+5DbW9jnIjA kCoYL/r6VysTk4VMscmJIjCBSo67wvZlyfbn5umKaZKhsy0FRopxIsCEqjCcRqyG68jiEsqS tytFY5gKcEzBSiEWSk8VXTcY2ZPalQVYINcezLZXhXPtTD5pYgx6Xh9Baqx86MECwurrqheQ TGTOM1ORChyTs1aCs9IF5r1pS0jBrh2K27iwYPZy9+YssRECNmLQxj4IZ6zkfymyDDXfzjna Mi+4NLWcYU6gFmuOb7Y4L9xX6ubPxI91jqatX722kvbo/Owd5cWBRUXXjS+ulMN20airp3Fy oMVxIKaUOFGrfpNx0KO11P90JepHrL2NN2tMQadPKYeTS3Y6jePNiwp3Sqx6qXT7XsGstF9t zkdJxx62bf2JimrIyKxWiRiaTIwVWhjyH9sFhUB2AwAA
Cc: Wesley Eddy <wes@mti-systems.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 23 Jan 2013 17:06:27 -0000

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

It is ok for me too.

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: mi=E9rcoles, 23 de enero de 2013 12:58
To: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Cc: Wesley Eddy <wes@mti-systems.com<mailto:wes@mti-systems.com>>, 'Gonzalo=
 Camarillo' <Gonzalo.Camarillo@ericsson.com<mailto:Gonzalo.Camarillo@ericss=
on.com>>, Martin Stiemerling <Martin.Stiemerling@neclab.eu<mailto:Martin.St=
iemerling@neclab.eu>>
Subject: [tcmtf] Improved version of the TCMTF Charter proposal (v3)

Hello all.

After reading the messages in the mailing list, I think we have arrived to =
a solution. Each of the documents has been discussed in a separate thread, =
so I have tried to take everything into account. Documents (A) and (B) woul=
d be in the Charter. Documents (C) and (D) would only be announced as possi=
bilities for re-chartering, and Document (E) can wait a little.

We can now try to polish this text. If you agree, please report it in the l=
ist.

So this is the new charter proposal:

*Description of Working Group* v3

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 applicatio=
ns: VoIP, videoconferencing, telemedicine, video vigilance, online gaming, =
etc. Due to the need of interactivity, many of these services use small pac=
kets (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 higher when IPv6 is used, since the basic IPv6 header =
is twice the size of the IPv4 one. In addition, some other services also se=
nd small packets, but they are not delay-sensitive (e.g., instant messaging=
, m2m packets sending collected data in sensor networks).

2. In order to improve network efficiency, packets can be grouped when a nu=
mber of flows share a path, considering three different layers:
- Header compression: Taking into account that real-time applications use d=
ifferent headers (RTP/UDP, UDP or even TCP), different protocols can be use=
d: no compression, ECRTP, IPHC and ROHC.
- Multiplexing a number of payloads into a single packet. If a number of fl=
ows share a path between an origin and a destination, a multiplexer can bui=
ld a bigger packet in which a number of payloads share a common header. A d=
emultiplexer is then necessary at the end of the common path, so as to rebu=
ild the packets as they were originally sent. PPPMux will be the main optio=
n. Other ones are not discarded.
- Tunneling will be used to send the multiplexed packets end-to-end. The op=
tions in this layer are L2TP, GRE and MPLS.

3. So the first objective of this group is to develop a document (A) that w=
ill specify the protocol stack for tunneling, compressing and multiplexing =
traffic flows (TCMTF). Since other standard protocols are being used, each =
layer will use the signaling methods of those protocols. In addition, since=
 document (A) would include, as one of the options, the current RFC 4170, t=
his RFC could be obsoleted.

4. The objective of this first document (A) is to define the different opti=
ons which can be used at each layer, not the definition of new compressing,=
 multiplexing or tunneling protocols. Specific problems caused by the inter=
action between layers will have to be issued, and suitable extensions may h=
ave to be added to the involved protocols.

5. If a pair multiplexer/de- multiplexer want to establish a tunnel, they h=
ave first to use a mechanism to negotiate which concrete option would they =
use in each layer: header compression, multiplexing and tunneling. This wil=
l depend on the protocols each of them implements at each level, and in the=
 scenario. So document (A) will also include a negotiation mechanism to dec=
ide the options at each layer (header compression, multiplexing and tunneli=
ng) between multiplexer and de-multiplexer, and a mechanism to setup/releas=
e a tunnel between a multiplexer and a de-multiplexer.

6. As a counterpart of the bandwidth saving, TCMTF may add some delay and j=
itter. This is not a problem for the services which are not sensitive to de=
lay. However, regarding delay-sensitive services, the Working Group will al=
so develop a document (B) with useful recommendations in order to decide wh=
ich packet flows can or can not be multiplexed and how: the use of availabl=
e traffic classification methods; the maximum delay and jitter to be added =
to each kind of service or application. Other recommendations will be inclu=
ded if necessary. Empirical studies will be necessary in order to establish=
 this set of recommendations.

7. If other interesting features are identified, the group would re-charter=
 and include them, e.g., a mechanism for a multiplexer to discover a de-mul=
tiplexer, and vice versa; a mechanism to select an optimal multiplexer and =
a de-multiplexer when there are more than one muxer/de-muxer for a flow; dy=
namically applying TCMTF: a higher entity in charge of deciding when and wh=
ere, applying or not TCMTF, and what kind of TCMTF, and what multiplexing p=
eriod. Additional methods for estimating delay would also be required.

8. In addition, specific uses of TCMTF, such as wireless and satellite scen=
arios could be considered and addressed if some modifications are required =
on the protocol.

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

*Goals and Milestones*

Specification of TCMTF protocol stack (A) and signaling mechanisms.

Recommendations (B) of using existing traffic classification methods, maxim=
um delay and jitter to add, depending on the service.

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

Best regards, and thanks for your wonderful work,

Jose


________________________________

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

--Boundary_(ID_4f18qIFBQxr/s31gFf107g)
Content-id: <08150EB9881CA945A78CA02414A64931@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>It is ok for me too.</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>mi=E9rcoles, 23 de enero de 2=
013 12:58<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">Cc: </span>Wesley Eddy &lt;<a href=3D"mail=
to:wes@mti-systems.com">wes@mti-systems.com</a>&gt;, 'Gonzalo Camarillo' &l=
t;<a href=3D"mailto:Gonzalo.Camarillo@ericsson.com">Gonzalo.Camarillo@erics=
son.com</a>&gt;, Martin Stiemerling &lt;<a href=3D"mailto:Martin.Stiemerlin=
g@neclab.eu">Martin.Stiemerling@neclab.eu</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[tcmtf] Improved version o=
f the TCMTF Charter proposal (v3)<br>
</div>
<div><br>
</div>
<div><style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
span.EstiloCorreo17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
.MsoChpDefault
	{font-size:10.0pt;
	font-family:"Calibri","sans-serif"}
@page WordSection1
	{margin:70.85pt 3.0cm 70.85pt 3.0cm}
div.WordSection1
	{}
-->
</style>
<div lang=3D"ES">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hello all.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">After reading the messages in t=
he mailing list, I think we have arrived to a solution. Each of the documen=
ts has been discussed in a separate thread, so I have tried to take everyth=
ing into account. Documents (A) and
 (B) would be in the Charter. Documents (C) and (D) would only be announced=
 as possibilities for re-chartering, and Document (E) can wait a little.</s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We can now try to polish this t=
ext. If you agree, please report it in the list.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">So this is the new charter prop=
osal:</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">*<b>Description of Working Grou=
p</b>* v3</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">1. In the last years we are wit=
nessing the raise of new real-time services that use the Internet for the d=
elivery of interactive multimedia applications: VoIP, videoconferencing, te=
lemedicine, 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 update=
s to the other extreme of the communication. Therefore, its overhead is sig=
nificant, and it becomes even higher
 when IPv6 is used, since the basic IPv6 header is twice the size of the IP=
v4 one. In addition, some other services also send small packets, but they =
are not delay-sensitive (e.g., instant messaging, m2m packets sending colle=
cted data in sensor networks).</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">2. In order to improve network =
efficiency, packets can be grouped when a number of flows share a path, con=
sidering three different layers:</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">- Header compression: Taking in=
to 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.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">- Multiplexing a number of payl=
oads into a single packet. If a number of flows share a path between an ori=
gin and a destination, a multiplexer can build a bigger packet in which a n=
umber of payloads share a common header.
 A demultiplexer is then necessary at the end of the common path, so as to =
rebuild the packets as they were originally sent. PPPMux will be the main o=
ption. Other ones are not discarded.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">- Tunneling will be used to sen=
d the multiplexed packets end-to-end. The options in this layer are L2TP, G=
RE and MPLS.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">3. So the first objective of th=
is group is to develop a document (A) that will specify the protocol stack =
for tunneling, compressing and multiplexing traffic flows (TCMTF). Since ot=
her standard protocols are being used,
 each layer will use the signaling methods of those protocols. In addition,=
 since document (A) would include, as one of the options, the current RFC 4=
170, this RFC could be obsoleted.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">4. The objective of this first =
document (A) is to define the different options which can be used at each l=
ayer, not the definition of new compressing, multiplexing or tunneling prot=
ocols. 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.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">5. If a pair multiplexer/de- mu=
ltiplexer want to establish a tunnel, they have first to use a mechanism to=
 negotiate which concrete option would they use in each layer: header compr=
ession, multiplexing and tunneling.
 This will depend on the protocols each of them implements at each level, a=
nd in the scenario. So document (A) will also include a negotiation mechani=
sm to decide the options at each layer (header compression, multiplexing an=
d tunneling) between multiplexer
 and de-multiplexer, and a mechanism to setup/release a tunnel between a mu=
ltiplexer and a de-multiplexer.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">6. As a counterpart of the band=
width saving, TCMTF may add some delay and jitter. This is not a problem fo=
r the services which are not sensitive to delay. However, regarding delay-s=
ensitive services, the Working Group
 will also develop a document (B) with useful recommendations in order to d=
ecide which packet flows can or can not be multiplexed and how: the use of =
available traffic classification methods; the maximum delay and jitter to b=
e added to each kind of service
 or application. Other recommendations will be included if necessary. Empir=
ical studies will be necessary in order to establish this set of recommenda=
tions.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">7. If other interesting feature=
s are identified, the group would re-charter and include them, e.g., a mech=
anism for a multiplexer to discover a de-multiplexer, and vice versa; a mec=
hanism to select an optimal multiplexer
 and a de-multiplexer when there are more than one muxer/de-muxer for a flo=
w; dynamically applying TCMTF: a higher entity in charge of deciding when a=
nd where, applying or not TCMTF, and what kind of TCMTF, and what multiplex=
ing period. Additional methods for
 estimating delay would also be required.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">8. In addition, specific uses o=
f TCMTF, such as wireless and satellite scenarios could be considered and a=
ddressed if some modifications are required on the protocol.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">9. Interactions with other grou=
ps can be expected, since TCMTF uses already defined protocols (ROHC, PPPMu=
x, MPLS, GRE, L2TP).</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">*<b>Goals and Milestones</b>*</=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Specification of TCMTF protocol=
 stack (A) and signaling mechanisms.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Recommendations (B) of using ex=
isting traffic classification methods, maximum delay and jitter to add, dep=
ending on the service.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">-------------------------------=
-----</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Best regards, and thanks for yo=
ur wonderful work,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10pt; font-f=
amily:Arial,sans-serif">Jose
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
</div>
</div>
</span><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_4f18qIFBQxr/s31gFf107g)--

From wes@mti-systems.com  Wed Jan 23 21:16:34 2013
Return-Path: <wes@mti-systems.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C02A921F8830 for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 21:16:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lBq9iVHajDG2 for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 21:16:34 -0800 (PST)
Received: from atl4mhob14.myregisteredsite.com (atl4mhob14.myregisteredsite.com [209.17.115.52]) by ietfa.amsl.com (Postfix) with ESMTP id 02D9F21F8518 for <tcmtf@ietf.org>; Wed, 23 Jan 2013 21:16:33 -0800 (PST)
Received: from mailpod.hostingplatform.com (mail.networksolutionsemail.com [205.178.146.50]) by atl4mhob14.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r0O5GXbm014811 for <tcmtf@ietf.org>; Thu, 24 Jan 2013 00:16:33 -0500
Received: (qmail 11281 invoked by uid 0); 24 Jan 2013 05:16:33 -0000
Received: from unknown (HELO ?172.17.89.224?) (wes@mti-systems.com@12.161.62.194) by 0 with ESMTPA; 24 Jan 2013 05:16:33 -0000
Message-ID: <5100C3A4.2010500@mti-systems.com>
Date: Thu, 24 Jan 2013 00:16:20 -0500
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: jsaldana@unizar.es
References: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
In-Reply-To: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: tcmtf@ietf.org, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 24 Jan 2013 05:16:34 -0000

On 1/23/2013 6:58 AM, Jose Saldana wrote:
> Hello all.
> 
>  
> 
> After reading the messages in the mailing list, I think we have arrived
> to a solution. Each of the documents has been discussed in a separate
> thread, so I have tried to take everything into account. Documents (A)
> and (B) would be in the Charter. Documents (C) and (D) would only be
> announced as possibilities for re-chartering, and Document (E) can wait
> a little.
> 
> ...


In my opinion, this is decent, though here are two criticisms:

(1) In my opinion, it focuses too much on documents to be produced,
    rather than fully and clearly motivating why the working group
    is needed (i.e. to solve a problem, not to develop documents),
    how it's scope is delimited (i.e. what it *won't* touch isn't
    clear to me, along with what other areas/WGs need to be
    coordinated with), and what the end-goal is.

(2) There's a focus on defining technical solutions prior to the
    mention of fleshing out and totally defining the use cases /
    requirements.  In my opinion, that appears backwards :).

That said, I'm generally supportive of this work.  In my opinion,
as an AD, we would normally feel better having a BoF before forming
a WG, for two reasons (1) to get other areas (e.g. RAI) to be aware
of what's being proposed, and (2) to vet that there really is a
community of stakeholders that are engaged to do the work.  In this
case, I think the 2nd point is evident from the mailing list, and
I don't have a concern about it at all.  I think the 1st point can
be addressed through the responsible AD coordinating with the IESG
and the directorates or area mailing lists that related areas have.
Since I'm going away as an AD though, what really matters at the
moment is what Martin thinks :).

-- 
Wes Eddy
MTI Systems

From gonzalo.camarillo@ericsson.com  Wed Jan 23 22:12:20 2013
Return-Path: <gonzalo.camarillo@ericsson.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 0542B21F8801 for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 22:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.099
X-Spam-Level: 
X-Spam-Status: No, score=-106.099 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, 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 6b6RwBEoAwp3 for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 22:12:19 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 9997121F8834 for <tcmtf@ietf.org>; Wed, 23 Jan 2013 22:12:18 -0800 (PST)
X-AuditID: c1b4fb25-b7f366d000004d10-d9-5100d0c19e0a
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 79.DE.19728.1C0D0015; Thu, 24 Jan 2013 07:12:17 +0100 (CET)
Received: from [131.160.126.131] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.279.1; Thu, 24 Jan 2013 07:12:16 +0100
Message-ID: <5100D0C0.7030600@ericsson.com>
Date: Thu, 24 Jan 2013 08:12:16 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Wesley Eddy <wes@mti-systems.com>
References: <007801cdf961$04e78c80$0eb6a580$@unizar.es> <5100C3A4.2010500@mti-systems.com>
In-Reply-To: <5100C3A4.2010500@mti-systems.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrELMWRmVeSWpSXmKPExsUyM+Jvre7BCwyBBm/nSFlsOaZn0dF3lc1i 1+cNjBbXv7M7sHgsWfKTyePkqV42jxnHXrJ7LLt6hDmAJYrLJiU1J7MstUjfLoEr49n2G6wF E5krevtbmRsYtzJ1MXJySAiYSJye84ERwhaTuHBvPVsXIxeHkMBJRomV61qZIJy1jBK/frxi 7mLk4OAV0Ja4cykfpIFFQFXi+OonbCA2m4CFxJZb91lAbFGBKIn3V5uYQWxeAUGJkzOfgMVF gOoXTj4CZjMLxEis37WLHcQWFnCQ+Pz4ACuILQTUe3HibLDjOAX0JZ6d2MYCcZykxKJpnVC9 ehJTrrYwQtjyEtvfzmGG6NWWWP6shWUCo9AsJKtnIWmZhaRlASPzKkb23MTMnPRyo02MwHA+ uOW36g7GO+dEDjFKc7AoifOGu14IEBJITyxJzU5NLUgtii8qzUktPsTIxMEp1cCo4mVxW+Hp 45q4QwLnTx3wv/lAVWlXwj9x4xt7dBOOiXX9qzIJfHX3wM7qJQsq2lpOCX0qz5ls+HGB6sPJ XKyL/ny9fLZqzbe8i9kxfSm3co8s9NEO65mdk2LAwLOcv3PFp6qjqzKmFSSteXSr/d107moR pjrGfxcL7zz7E7PV+n8R64H9wldZlViKMxINtZiLihMBNgMUKjUCAAA=
Cc: tcmtf@ietf.org, Martin Stiemerling <Martin.Stiemerling@neclab.eu>, jsaldana@unizar.es
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 24 Jan 2013 06:12:20 -0000

Hi Wes,

> (1) to get other areas (e.g. RAI) to be aware
> of what's being proposed

there are already quite a few RAI people following and participating in
this work. In any case, as an alternative to having a full-blown BOF to
make RAI (in particular) as a whole aware of this effort, I can just
drop an email to the DISPATCH list and will achieve the same results.

Cheers,

Gonzalo


From ggx@gigix.net  Thu Jan 24 01:40:58 2013
Return-Path: <ggx@gigix.net>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBB3221F8481 for <tcmtf@ietfa.amsl.com>; Thu, 24 Jan 2013 01:40:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 pIOzARAuC+5o for <tcmtf@ietfa.amsl.com>; Thu, 24 Jan 2013 01:40:57 -0800 (PST)
Received: from mail-we0-x22f.google.com (we-in-x022f.1e100.net [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 3C59621F8443 for <tcmtf@ietf.org>; Thu, 24 Jan 2013 01:40:57 -0800 (PST)
Received: by mail-we0-f175.google.com with SMTP id z53so2882962wey.6 for <tcmtf@ietf.org>; Thu, 24 Jan 2013 01:40:56 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:message-id:references:to:x-mailer:x-gm-message-state; bh=RXc+E1zm7JmEl8N2pwhLze14EELxIT2du77zwV0Gfv8=; b=hfN5y5S0/BACXz2jSYpP26SIs0ZJ7GFWANA4jBt6BhiFkE6q0sLPyoy15Wv/Km+pXr ZsOC2OdbqdeximpftfFTBjUue11b/CZVyGJjMLsphyxLTeZvw0oWUNdG5so8Ize3r9FS WeVrNCjD8ymtdw0BdIUnRi11Y2w1xTBW469QkCnS+1aM1HH8wRGdQvuBAbMTL4XouVDw iD5ZMHVCx1n7pEyQSkbITMAgRMwEICgNRElWZ5uzyDm0tzTGNz9Bm0oAGQDGZpqbZK4L xn5cxxBumJKO4LjwnBm9pdgclxi65ngFQWc7q1cfsY3nH0sqC5xg21b6bfjt9jDLAem+ eVcA==
X-Received: by 10.180.82.69 with SMTP id g5mr1861513wiy.21.1359020456337; Thu, 24 Jan 2013 01:40:56 -0800 (PST)
Received: from ?IPv6:2001:660:330f:a4:3d5c:94fb:c742:29f9? ([2001:660:330f:a4:3d5c:94fb:c742:29f9]) by mx.google.com with ESMTPS id dm3sm1443152wib.9.2013.01.24.01.40.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Jan 2013 01:40:55 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_E6B480E3-4FAA-44D2-9C7A-1AB52339210E"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
Date: Thu, 24 Jan 2013 10:40:53 +0100
Message-Id: <3F34B089-CB8F-4CBC-B6F8-919E7F00E86A@gigix.net>
References: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
To: jsaldana@unizar.es
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQkIDaOjW6PskNay+hdsFr20lSlVIJZoo7SdGtxf827c+HTyEjpGQCjWzQKqYIU95KYe2io+
Cc: tcmtf@ietf.org, Wesley Eddy <wes@mti-systems.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 24 Jan 2013 09:40:59 -0000

--Apple-Mail=_E6B480E3-4FAA-44D2-9C7A-1AB52339210E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 23 Jan. 2013, at 12:58 , Jose Saldana <jsaldana@unizar.es> wrote:

> Hello all.
> =20
> After reading the messages in the mailing list, I think we have =
arrived to a solution. Each of the documents has been discussed in a =
separate thread, so I have tried to take everything into account. =
Documents (A) and (B) would be in the Charter. Documents (C) and (D) =
would only be announced as possibilities for re-chartering, and Document =
(E) can wait a little.

For the sake of planning, let's consider document (E) as a discussion =
item when re-chartering.

> =20
> We can now try to polish this text. If you agree, please report it in =
the list.
> =20
> So this is the new charter proposal:
> =20
> *Description of Working Group* v3

Looks good to me.

Luigi


> =20
> 1. In the last years we are witnessing the raise of new real-time =
services that use the Internet for the delivery of interactive =
multimedia applications: VoIP, videoconferencing, telemedicine, video =
vigilance, online gaming, etc. Due to the need of interactivity, many of =
these services use small packets (some tens of bytes), since they have =
to send frequent updates to the other extreme of the communication. =
Therefore, its overhead is significant, and it becomes even higher when =
IPv6 is used, since 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 sending =
collected data in sensor networks).
> =20
> 2. In order to improve network efficiency, packets can be grouped when =
a number of flows share a path, 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 then necessary at the end of the common path, =
so as to rebuild the packets as they were originally sent. PPPMux will =
be the main option. Other ones are not discarded.
> - Tunneling will be used to send the multiplexed packets end-to-end. =
The options in this layer are L2TP, GRE and MPLS.
> =20
> 3. So the first objective of this group is to develop a document (A) =
that will specify the protocol stack for tunneling, compressing and =
multiplexing traffic flows (TCMTF). Since other standard protocols are =
being used, each layer will use the signaling methods of those =
protocols. In addition, since document (A) would include, as one of the =
options, the current RFC 4170, this RFC could be obsoleted.
> =20
> 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 =
compressing, multiplexing or tunneling protocols. Specific problems =
caused by the interaction between layers will have to be issued, and =
suitable extensions may have to be added to the involved protocols.
> =20
> 5. If a pair multiplexer/de- multiplexer want to establish a tunnel, =
they have first to use a mechanism to negotiate which concrete option =
would they use in each layer: header compression, multiplexing and =
tunneling. This will depend on the protocols each of them implements at =
each level, and in the scenario. So document (A) will also include a =
negotiation mechanism to decide the options at each layer (header =
compression, multiplexing and tunneling) between multiplexer and =
de-multiplexer, and a mechanism to setup/release a tunnel between a =
multiplexer and a de-multiplexer.
> =20
> 6. As a counterpart of the bandwidth saving, TCMTF may add some delay =
and jitter. This is not a problem for the services which are not =
sensitive to delay. However, regarding delay-sensitive services, the =
Working Group will also develop a document (B) with useful =
recommendations in order to decide which packet flows can or can not be =
multiplexed and how: the use of available traffic classification =
methods; the maximum delay and jitter to be added to each kind of =
service or application. Other recommendations will be included if =
necessary. Empirical studies will be necessary in order to establish =
this set of recommendations.
> =20
> 7. If other interesting features are identified, the group would =
re-charter and include them, e.g., a mechanism for a multiplexer to =
discover a de-multiplexer, and vice versa; a mechanism to select an =
optimal multiplexer and a de-multiplexer when there are more than one =
muxer/de-muxer for a flow; dynamically applying TCMTF: a higher entity =
in charge of deciding when and where, applying or not TCMTF, and what =
kind of TCMTF, and what multiplexing period. Additional methods for =
estimating delay would also be required.
> =20
> 8. In addition, specific uses of TCMTF, such as wireless and satellite =
scenarios could be considered and addressed if some modifications are =
required on the protocol.
> =20
> 9. Interactions with other groups can be expected, since TCMTF uses =
already defined protocols (ROHC, PPPMux, MPLS, GRE, L2TP).
> =20
> *Goals and Milestones*
> =20
> Specification of TCMTF protocol stack (A) and signaling mechanisms.
> =20
> Recommendations (B) of using existing traffic classification methods, =
maximum delay and jitter to add, depending on the service.
> =20
> ------------------------------------
> =20
> Best regards, and thanks for your wonderful work,
> =20
> Jose
> =20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


--Apple-Mail=_E6B480E3-4FAA-44D2-9C7A-1AB52339210E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"><base href=3D"x-msg://16621/"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Hi,<div><br><div><div>On 23 =
Jan. 2013, at 12:58 , 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">Hello =
all.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">After reading the messages in the mailing list, I think =
we have arrived to a solution. Each of the documents has been discussed =
in a separate thread, so I have tried to take everything into account. =
Documents (A) and (B) would be in the Charter. Documents (C) and (D) =
would only be announced as possibilities for re-chartering, and Document =
(E) can wait a little.<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"></div></div></div></blockquote><div><br></div><div>For the sake of =
planning, let's consider document (E) as a discussion item when =
re-chartering.</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">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">We can now try to polish =
this text. If you agree, please report it in the =
list.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">So this is the new charter =
proposal:<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">*<b>Description of Working Group</b>* =
v3</span></div></div></div></blockquote><div><br></div><div>Looks good =
to =
me.</div><div><br></div><div>Luigi</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"><o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">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 higher when IPv6 is used, since 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 sending collected data in sensor =
networks).<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">2. In order to improve network efficiency, packets can be =
grouped when a number of flows share a path, considering three 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 =
lang=3D"EN-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></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-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 then necessary at the end of =
the common path, so as to rebuild the packets as they were originally =
sent. PPPMux will be the main option. Other ones are not =
discarded.<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">- 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></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">3. So the first objective of this group is to develop a =
document (A) that will specify the protocol stack for tunneling, =
compressing and multiplexing traffic flows (TCMTF). Since other standard =
protocols are being used, each layer will use the signaling methods of =
those protocols. In addition, since document (A) would include, as one =
of the options, the current RFC 4170, this RFC could be =
obsoleted.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">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 compressing, multiplexing or tunneling protocols. =
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></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">5. If a pair multiplexer/de- multiplexer want to =
establish a tunnel, they have first to use a mechanism to negotiate =
which concrete option would they use in each layer: header compression, =
multiplexing and tunneling. This will depend on the protocols each of =
them implements at each level, and in the scenario. So document (A) will =
also include a negotiation mechanism to decide the options at each layer =
(header compression, multiplexing and tunneling) between multiplexer and =
de-multiplexer, and a mechanism to setup/release a tunnel between a =
multiplexer and a de-multiplexer.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">6. As a counterpart of the =
bandwidth saving, TCMTF may add some delay and jitter. This is not a =
problem for the services which are not sensitive to delay. However, =
regarding delay-sensitive services, the Working Group will also develop =
a document (B) with useful recommendations in order to decide which =
packet flows can or can not be multiplexed and how: the use of available =
traffic classification methods; the maximum delay and jitter to be added =
to each kind of service or application. Other recommendations will be =
included if necessary. Empirical studies will be necessary in order to =
establish this set of recommendations.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">7. If other interesting =
features are identified, the group would re-charter and include them, =
e.g., a mechanism for a multiplexer to discover a de-multiplexer, and =
vice versa; a mechanism to select an optimal multiplexer and a =
de-multiplexer when there are more than one muxer/de-muxer for a flow; =
dynamically applying TCMTF: a higher entity in charge of deciding when =
and where, applying or not TCMTF, and what kind of TCMTF, and what =
multiplexing period. Additional methods for estimating delay would also =
be required.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">8. In addition, specific uses of TCMTF, such as wireless =
and satellite scenarios could be considered and addressed if some =
modifications are required on the protocol.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">9. Interactions with other =
groups can be expected, since TCMTF uses already defined protocols =
(ROHC, PPPMux, MPLS, GRE, L2TP).<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">*<b>Goals and =
Milestones</b>*<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">Specification of TCMTF protocol stack (A) and signaling =
mechanisms.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">Recommendations (B) of using existing traffic =
classification methods, maximum delay and jitter to add, depending on =
the service.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">------------------------------------<o:p></o:p></span></div=
><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">Best regards, and thanks for =
your wonderful work,<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Arial, sans-serif; =
">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">&nbsp;</span></div></div>__________________________________=
_____________<br>tcmtf mailing list<br><a href=3D"mailto:tcmtf@ietf.org" =
style=3D"color: purple; text-decoration: underline; =
">tcmtf@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color: =
purple; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/tcmtf</a></div></blockquote></div>=
<br></div></body></html>=

--Apple-Mail=_E6B480E3-4FAA-44D2-9C7A-1AB52339210E--

From jsaldana@unizar.es  Thu Jan 24 02:07:52 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D18721F8468 for <tcmtf@ietfa.amsl.com>; Thu, 24 Jan 2013 02:07:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.574
X-Spam-Level: 
X-Spam-Status: No, score=-6.574 tagged_above=-999 required=5 tests=[AWL=0.025,  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 JDfISOvXPKfT for <tcmtf@ietfa.amsl.com>; Thu, 24 Jan 2013 02:07:51 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 8E94F21F8441 for <tcmtf@ietf.org>; Thu, 24 Jan 2013 02:07:51 -0800 (PST)
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 r0OA7ieN023777; Thu, 24 Jan 2013 11:07:44 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Wesley Eddy'" <wes@mti-systems.com>
Date: Thu, 24 Jan 2013 11:07:48 +0100
Organization: Universidad de Zaragoza
Message-ID: <002701cdfa1a$a9c3d650$fd4b82f0$@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: Ac36GoQuk+ZEGqHiTAyL1lZl7Y+DsA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, 'Gonzalo Camarillo' <Gonzalo.Camarillo@ericsson.com>, 'Martin Stiemerling' <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 24 Jan 2013 10:07:52 -0000

Wes and everybody,

Thanks for your feedback and support.

I have rebuilt the Charter (now it is v4, and it is in the next e-mail)
taking into account Mirko's and Matteo's improvements, and the suggestions
of Wes.

Paragraph 10 has been modified according to Matteo's improvements
Paragraph 8 has been modified according to Mirko's improvements

And regarding the suggestions of Wes:

(1) In my opinion, it focuses too much on documents to be produced,
>     rather than fully and clearly motivating why the working group
>     is needed (i.e. to solve a problem, not to develop documents)
I have added paragraphs 2 and 3 in order to set this clear. And now,
paragraph 5 does not talk about documents, but only about the solution

>     how it's scope is delimited (i.e. what it *won't* touch isn't
>     clear to me, along with what other areas/WGs need to be
>     coordinated with), and what the end-goal is.
Paragraph 5 talks about this: "(...) Interactions with the Working Groups
and Areas in which these protocols are developed can be expected. However,
the development of new compressing, multiplexing or tunneling protocols is
not an objective of this Working Group."

> (2) There's a focus on defining technical solutions prior to the
>     mention of fleshing out and totally defining the use cases /
>     requirements.  In my opinion, that appears backwards :).
Paragraph 2 is now about the use cases.



Best regards,

Jose
-------------------
 
> That said, I'm generally supportive of this work.  In my opinion, as an
AD, we
> would normally feel better having a BoF before forming a WG, for two
> reasons (1) to get other areas (e.g. RAI) to be aware of what's being
> proposed, and (2) to vet that there really is a community of stakeholders
that
> are engaged to do the work.  In this case, I think the 2nd point is
evident
> from the mailing list, and I don't have a concern about it at all.  I
think the 1st
> point can be addressed through the responsible AD coordinating with the
> IESG and the directorates or area mailing lists that related areas have.
> Since I'm going away as an AD though, what really matters at the moment is
> what Martin thinks :).
> 
> --
> Wes Eddy
> MTI Systems


From jsaldana@unizar.es  Thu Jan 24 02:09:14 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A088221F884C for <tcmtf@ietfa.amsl.com>; Thu, 24 Jan 2013 02:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.577
X-Spam-Level: 
X-Spam-Status: No, score=-6.577 tagged_above=-999 required=5 tests=[AWL=0.021,  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 xtzcVNcfHpun for <tcmtf@ietfa.amsl.com>; Thu, 24 Jan 2013 02:09:13 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE9421F884B for <tcmtf@ietf.org>; Thu, 24 Jan 2013 02:08:39 -0800 (PST)
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 r0OA8XuG009164; Thu, 24 Jan 2013 11:08:33 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Thu, 24 Jan 2013 11:08:36 +0100
Organization: Universidad de Zaragoza
Message-ID: <002b01cdfa1a$c65cb2f0$531618d0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_002C_01CDFA23.28211AF0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac36GkoMhAtVCd/JRuCAcla+Q3DFeA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Wesley Eddy <wes@mti-systems.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [tcmtf] TCMTF Charter proposal (v4)
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, 24 Jan 2013 10:09:15 -0000

This is a multipart message in MIME format.

------=_NextPart_000_002C_01CDFA23.28211AF0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

According to the suggestions of Wes, Matteo and Mirko, I have built this =
new
version. The explaining is in the previous mail Do you like it?

=20

Thanks a lot,

=20

Jose

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

=20

*Description of Working Group v4*

=20

1. In the last years we are witnessing the raise of new real-time =
services
that use the Internet for the delivery of interactive multimedia
applications: VoIP, videoconferencing, telemedicine, video vigilance, =
online
gaming, etc. Due to the need of interactivity, many of these services =
use
small packets (some tens of bytes), since they have to send frequent =
updates
to the other extreme of the communication. Therefore, its overhead is
significant, and it becomes even higher when IPv6 is used, since 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 sending collected data in sensor networks
using wireless or satellite scenarios).

=20

2. The efficiency cannot be increased by the inclusion of a higher =
number of
samples in a single packet, since this would harm the delay requirements =
of
the service. But there exist some scenarios in which a number of flows =
share
the same path. In this case, packets belonging to different flows can be
grouped together, adding a small multiplexing delay as a counterpart of
bandwidth saving. This delay will have to be maintained under some =
threshold
in order to grant the delay requirements. Some examples of the scenarios
where grouping packets is possible are: aggregation networks of a =
network
operator; a tunnel between two premises of the same company; the access
connection of an Internet Caf=E9 including a high number of VoIP/gaming =
flows;
an agreement between two network operators could allow them to compress =
a
number of flows they are exchanging between a pair of Internet Routers; =
a
satellite connection used for collecting the data of a high number of
sensors; etc.

=20

3. VoIP using RTP is a clear example of a real-time service using small
packets with high overhead. In order to improve efficiency, RFC4170 =
(TCRTP)
defined a method for grouping packets when a number of flows share a =
path,
considering three different layers: header compression by means of =
ECRTP;
multiplexing by means of PPPMux; tunneling by means of L2TPv3.

=20

4. However, in the last years, emerging real-time services which do not =
use
UDP/RTP have become popular: some of them use UDP or even TCP. So there =
is a
need of widening the scope of RFC4170 in order to consider not only =
UDP/RTP
but also other protocols. The same structure of three layers will be
considered:

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

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

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

=20

5. So the first objective of this group is to specify the protocol stack =
for
tunneling, compressing and multiplexing traffic flows (TCMTF). Since
standard protocols are being used at each layer, the signaling methods =
of
those protocols will be used. Interactions with the Working Groups and =
Areas
in which these protocols are developed can be expected. However, the
development of new compressing, multiplexing or tunneling protocols is =
not
an objective of this Working Group. In addition, since the current RFC =
4170
would be considered as one of the options, this RFC could be obsoleted.

=20

6. As a first objective, a document (A) will define the different =
options
which can be used at each layer. Specific problems caused by the =
interaction
between layers will have to be issued, and suitable extensions may have =
to
be added to the involved protocols.

=20

7. If a pair multiplexer/de- multiplexer want to establish a tunnel, =
they
have first to use a mechanism to negotiate which concrete option would =
they
use in each layer: header compression, multiplexing and tunneling. This =
will
depend on the protocols that each extreme implements at each level, and =
in
the scenario. So document (A) will also include a negotiation mechanism =
to
decide the options to use at each layer (header compression, =
multiplexing
and tunneling) between multiplexer and de-multiplexer, and a mechanism =
to
setup/release a tunnel between a multiplexer and a de-multiplexer.

=20

8. As a counterpart of the bandwidth saving, TCMTF may add some delay =
and
jitter. This is not a problem for the services which are not sensitive =
to
delay. However, regarding delay-sensitive services, the Working Group =
will
also develop a document (B) with useful recommendations in order to =
decide
which packet flows can or can not be multiplexed and how. The document =
(B)
will present a list of available traffic classification methods which =
can be
used for identification of the service or application to which a =
particular
flow belongs, as well as recommendations of the maximum delay and jitter =
to
be added depending of the identified service or application.

=20

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

=20

10. In addition, specific uses of TCMTF, such as in wireless and =
satellite
scenarios, could be considered, and it will be studied whether =
modifications
or extensions are required on the protocol.

=20

11. Interactions with other Working Groups can be expected, since TCMTF =
uses
already defined protocols for compression, multiplexing and tunneling =
(ROHC,
PPPMux, MPLS, GRE, L2TP).

=20

*Goals and Milestones*

=20

Specification of TCMTF protocol stack (A) and signaling mechanisms.

=20

Recommendations (B) of using existing traffic classification methods,
maximum delay and jitter to add, depending on the service.

=20


------=_NextPart_000_002C_01CDFA23.28211AF0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.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>According to the suggestions of Wes, Matteo and Mirko, I =
have built this new version. The explaining is in the previous mail Do =
you like it?<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>Thanks a lot,<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></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 =
v4*<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 higher when =
IPv6 is used, since 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 sending =
collected data in sensor networks using wireless or satellite =
scenarios).<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. The efficiency cannot be increased by the inclusion of a =
higher number of samples in a single packet, since this would harm the =
delay requirements of the service. But there exist some scenarios in =
which a number of flows share the same path. In this case, packets =
belonging to different flows can be grouped together, adding a small =
multiplexing delay as a counterpart of bandwidth saving. This delay will =
have to be maintained under some threshold in order to grant the delay =
requirements. Some examples of the scenarios where grouping packets is =
possible are: aggregation networks of a network operator; a tunnel =
between two premises of the same company; the access connection of an =
Internet Caf=E9 including a high number of VoIP/gaming flows; an =
agreement between two network operators could allow them to compress a =
number of flows they are exchanging between a pair of Internet Routers; =
a satellite connection used for collecting the data of a high number of =
sensors; etc.<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. VoIP using RTP is a clear example of a real-time service =
using small packets with high overhead. In order to improve efficiency, =
RFC4170 (TCRTP) defined a method for grouping packets when a number of =
flows share a path, considering three different layers: header =
compression by means of ECRTP; multiplexing by means of PPPMux; =
tunneling by means of L2TPv3.<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. However, in the last years, =
emerging real-time services which do not use UDP/RTP have become =
popular: some of them use UDP or even TCP. So there is a need of =
widening the scope of RFC4170 in order to consider not only UDP/RTP but =
also other protocols. The same structure of three layers will be =
considered:<o:p></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>- =
Multiplexing: If a number of flows share a path between an origin and a =
destination, a multiplexer can build a bigger packet in which a number =
of payloads share a common header. A demultiplexer is then necessary at =
the end of the common path, so as to rebuild the packets as they were =
originally sent. PPPMux will be the main option. Other ones are not =
discarded.<o:p></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>5. So the first objective of this group is to specify the =
protocol stack for tunneling, compressing and multiplexing traffic flows =
(TCMTF). Since standard protocols are being used at each layer, the =
signaling methods of those protocols will be used. Interactions with the =
Working Groups and Areas in which these protocols are developed can be =
expected. However, the development of new compressing, multiplexing or =
tunneling protocols is not an objective of this Working Group. In =
addition, since the current RFC 4170 would be considered as one of the =
options, this RFC could be obsoleted.<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. As a first objective, a =
document (A) will define the different options which can be used at each =
layer. Specific problems caused by the interaction between layers will =
have to be issued, and suitable extensions may have to be added to the =
involved protocols.<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 a pair multiplexer/de- multiplexer want to establish =
a tunnel, they have first to use a mechanism to negotiate which concrete =
option would they use in each layer: header compression, multiplexing =
and tunneling. This will depend on the protocols that each extreme =
implements at each level, and in the scenario. So document (A) will also =
include a negotiation mechanism to decide the options to use at each =
layer (header compression, multiplexing and tunneling) between =
multiplexer and de-multiplexer, and a mechanism to setup/release a =
tunnel between a multiplexer and a =
de-multiplexer.<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. As a counterpart of the bandwidth saving, TCMTF may add =
some delay and jitter. This is not a problem for the services which are =
not sensitive to delay. However, regarding delay-sensitive services, the =
Working Group will also develop a document (B) with useful =
recommendations in order to decide which packet flows can or can not be =
multiplexed and how. The document (B) will present a list of available =
traffic classification methods which can be used for identification of =
the service or application to which a particular flow belongs, as well =
as recommendations of the maximum delay and jitter to be added depending =
of the identified service or application.<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. If other interesting features =
are identified, the group would re-charter and include them, e.g., a =
mechanism for a multiplexer to discover a de-multiplexer, and vice =
versa; a mechanism to select an optimal multiplexer and a de-multiplexer =
when there are more than one muxer/de-muxer for a flow; dynamically =
applying TCMTF: a higher entity in charge of deciding when and where, =
applying or not TCMTF, and what kind of TCMTF, and what multiplexing =
period. Additional methods for estimating delay would also be =
required.<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>10. In addition, specific uses of TCMTF, such as in =
wireless and satellite scenarios, could be considered, and it will be =
studied whether modifications or extensions are required on the =
protocol.<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>11. Interactions with other Working Groups can be expected, =
since TCMTF uses already defined protocols for compression, multiplexing =
and tunneling (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>*Goals and =
Milestones*<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>Specification of TCMTF protocol stack (A) and signaling =
mechanisms.<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>Recommendations (B) of using existing traffic =
classification methods, maximum delay and jitter to add, depending on =
the service.<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_002C_01CDFA23.28211AF0--


From Matteo.Berioli@dlr.de  Tue Jan 29 00:18:09 2013
Return-Path: <Matteo.Berioli@dlr.de>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51FCC21F8A7E for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 00:18:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.248
X-Spam-Level: 
X-Spam-Status: No, score=-10.248 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 IXC5s92YM+ef for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 00:18:08 -0800 (PST)
Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.32]) by ietfa.amsl.com (Postfix) with ESMTP id 414F421F8A77 for <tcmtf@ietf.org>; Tue, 29 Jan 2013 00:18:08 -0800 (PST)
Received: from DLREXHUB01.intra.dlr.de (172.21.152.130) by dlrexedge01.dlr.de (172.21.163.100) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 29 Jan 2013 09:17:43 +0100
Received: from DLREXMBX02.intra.dlr.de ([fe80::8cc6:b83e:ddc1:4e8b]) by dlrexhub01.intra.dlr.de ([::1]) with mapi id 14.02.0328.009; Tue, 29 Jan 2013 09:17:44 +0100
From: <Matteo.Berioli@dlr.de>
To: <wes@mti-systems.com>, <jsaldana@unizar.es>
Thread-Topic: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
Thread-Index: AQHN+fHxYtkaxKqFS8i6lSjqRjQ45phf+xJw
Date: Tue, 29 Jan 2013 08:17:45 +0000
Message-ID: <48DB40641BACF54C892EB0A12B4733C10BEEC8E1@dlrexmbx02.intra.dlr.de>
References: <007801cdf961$04e78c80$0eb6a580$@unizar.es> <5100C3A4.2010500@mti-systems.com>
In-Reply-To: <5100C3A4.2010500@mti-systems.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.247.173.107]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tcmtf@ietf.org, Gonzalo.Camarillo@ericsson.com, Martin.Stiemerling@neclab.eu
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 29 Jan 2013 08:18:09 -0000

Dear all,

I don't have a huge experience in IETF, but feel it is important to express=
 my opinion this time.
I have the feeling building a new WG is a bit premature, considering that w=
e just have an Internet draft.
I also find the discussion a bit documents-driven, rather than problems-dri=
ven.
IMHO we could wait a bit, before creating the WG, to see whether the ideas =
we have really solve real-world problems.

That's it. Hope this helps.

Matteo


-----Original Message-----
From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of W=
esley Eddy
Sent: 24 January 2013 06:16
To: jsaldana@unizar.es
Cc: tcmtf@ietf.org; Gonzalo Camarillo; Martin Stiemerling
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)

On 1/23/2013 6:58 AM, Jose Saldana wrote:
> Hello all.
>=20
> =20
>=20
> After reading the messages in the mailing list, I think we have=20
> arrived to a solution. Each of the documents has been discussed in a=20
> separate thread, so I have tried to take everything into account.=20
> Documents (A) and (B) would be in the Charter. Documents (C) and (D)=20
> would only be announced as possibilities for re-chartering, and=20
> Document (E) can wait a little.
>=20
> ...


In my opinion, this is decent, though here are two criticisms:

(1) In my opinion, it focuses too much on documents to be produced,
    rather than fully and clearly motivating why the working group
    is needed (i.e. to solve a problem, not to develop documents),
    how it's scope is delimited (i.e. what it *won't* touch isn't
    clear to me, along with what other areas/WGs need to be
    coordinated with), and what the end-goal is.

(2) There's a focus on defining technical solutions prior to the
    mention of fleshing out and totally defining the use cases /
    requirements.  In my opinion, that appears backwards :).

That said, I'm generally supportive of this work.  In my opinion, as an AD,=
 we would normally feel better having a BoF before forming a WG, for two re=
asons (1) to get other areas (e.g. RAI) to be aware of what's being propose=
d, and (2) to vet that there really is a community of stakeholders that are=
 engaged to do the work.  In this case, I think the 2nd point is evident fr=
om the mailing list, and I don't have a concern about it at all.  I think t=
he 1st point can be addressed through the responsible AD coordinating with =
the IESG and the directorates or area mailing lists that related areas have=
.
Since I'm going away as an AD though, what really matters at the moment is =
what Martin thinks :).

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

From jsaldana@unizar.es  Tue Jan 29 01:56:21 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F21021F85EA for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 01:56:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.58
X-Spam-Level: 
X-Spam-Status: No, score=-6.58 tagged_above=-999 required=5 tests=[AWL=0.019,  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 nQs2pT9vL61M for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 01:56:20 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 361AE21F85D9 for <tcmtf@ietf.org>; Tue, 29 Jan 2013 01:56:20 -0800 (PST)
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 r0T9u9wX010874; Tue, 29 Jan 2013 10:56:09 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <Matteo.Berioli@dlr.de>, <wes@mti-systems.com>
References: <007801cdf961$04e78c80$0eb6a580$@unizar.es>	<5100C3A4.2010500@mti-systems.com> <48DB40641BACF54C892EB0A12B4733C10BEEC8E1@dlrexmbx02.intra.dlr.de>
In-Reply-To: <48DB40641BACF54C892EB0A12B4733C10BEEC8E1@dlrexmbx02.intra.dlr.de>
Date: Tue, 29 Jan 2013 10:56:19 +0100
Organization: Universidad de Zaragoza
Message-ID: <006201cdfe06$e39bf480$aad3dd80$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: es
Thread-index: AQKEYSXdzhcNp/dyweHUpBdu8HtQhgKIyaT6AdVgqJGW0FanEA==
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, Gonzalo.Camarillo@ericsson.com, Martin.Stiemerling@neclab.eu
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 29 Jan 2013 09:56:21 -0000

Matteo,

Thanks a lot. Well, in this case, I don't agree with you (only in this
case).

The idea with TCMTF was to create a "small" Working Group, the same way as
they are created in other Areas (e.g. RAI). 

As Wes said in November, " In my opinion, it is something a separate WG
should be created to handle, and not something to try to do inside the
TSVWG, since there are already a handful of things TSVWG is wrestling with,
and it creates too much "context switching" to have a lot of unrelated
topics under work there."

The question is that the TSVWG group has a lot of interesting things now,
and it would be better to discuss TCMTF separately. In fact, since the
Summer, we are discussing it in another mailing list. This is good, but in
fact many people from TSVWG have not followed our discussion.

In addition, a lot of time has passed. TCMTF draft was presented in Paris 10
months ago. A lot of people from many institutions have become interested on
it. We have two drafts and three more possibilities.

Neither am I an expert on IETF, but I understand that things have some
"momentum": if you let time go by, people may lose their interest. And
curently interest does exist, as we have seen in the list. So why not now?

In addition, the new version of the Charter is more problem-centered (I
hope).

Thanks and best regards,

Jose


> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
> Matteo.Berioli@dlr.de
> Enviado el: martes, 29 de enero de 2013 9:18
> Para: wes@mti-systems.com; jsaldana@unizar.es
> CC: tcmtf@ietf.org; Gonzalo.Camarillo@ericsson.com;
> Martin.Stiemerling@neclab.eu
> Asunto: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
> 
> Dear all,
> 
> I don't have a huge experience in IETF, but feel it is important to
express my
> opinion this time.
> I have the feeling building a new WG is a bit premature, considering that
we
> just have an Internet draft.
> I also find the discussion a bit documents-driven, rather than problems-
> driven.
> IMHO we could wait a bit, before creating the WG, to see whether the ideas
> we have really solve real-world problems.
> 
> That's it. Hope this helps.
> 
> Matteo
> 
> 
> -----Original Message-----
> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
> Of Wesley Eddy
> Sent: 24 January 2013 06:16
> To: jsaldana@unizar.es
> Cc: tcmtf@ietf.org; Gonzalo Camarillo; Martin Stiemerling
> Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
> 
> On 1/23/2013 6:58 AM, Jose Saldana wrote:
> > Hello all.
> >
> >
> >
> > After reading the messages in the mailing list, I think we have
> > arrived to a solution. Each of the documents has been discussed in a
> > separate thread, so I have tried to take everything into account.
> > Documents (A) and (B) would be in the Charter. Documents (C) and (D)
> > would only be announced as possibilities for re-chartering, and
> > Document (E) can wait a little.
> >
> > ...
> 
> 
> In my opinion, this is decent, though here are two criticisms:
> 
> (1) In my opinion, it focuses too much on documents to be produced,
>     rather than fully and clearly motivating why the working group
>     is needed (i.e. to solve a problem, not to develop documents),
>     how it's scope is delimited (i.e. what it *won't* touch isn't
>     clear to me, along with what other areas/WGs need to be
>     coordinated with), and what the end-goal is.
> 
> (2) There's a focus on defining technical solutions prior to the
>     mention of fleshing out and totally defining the use cases /
>     requirements.  In my opinion, that appears backwards :).
> 
> That said, I'm generally supportive of this work.  In my opinion, as an
AD, we
> would normally feel better having a BoF before forming a WG, for two
> reasons (1) to get other areas (e.g. RAI) to be aware of what's being
> proposed, and (2) to vet that there really is a community of stakeholders
> that are engaged to do the work.  In this case, I think the 2nd point is
> evident from the mailing list, and I don't have a concern about it at all.
I
> think the 1st point can be addressed through the responsible AD
> coordinating with the IESG and the directorates or area mailing lists that
> related areas have.
> Since I'm going away as an AD though, what really matters at the moment is
> what Martin thinks :).
> 
> --
> Wes Eddy
> MTI Systems
> _______________________________________________
> 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  Tue Jan 29 02:13:56 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27E5521F86D8 for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 02:13:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G0V57-xJuejO for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 02:13:55 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 53C2621F86D4 for <tcmtf@ietf.org>; Tue, 29 Jan 2013 02:13:54 -0800 (PST)
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 <0MHD00DCQTR4U0@tid.hi.inet> for tcmtf@ietf.org; Tue, 29 Jan 2013 11:13:52 +0100 (MET)
Received: from tid (mailhost.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 7F.88.03184.0E0A7015; Tue, 29 Jan 2013 11:13:52 +0100 (CET)
Received: from correo.tid.es ([10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MHD001Z5TR499@tid.hi.inet> for tcmtf@ietf.org; Tue, 29 Jan 2013 11:13:52 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.165]) by EX10-HTCAS6-MAD.hi.inet ([fe80::e1e3:e2fc:beda:deb9%15]) with mapi id 14.02.0318.004; Tue, 29 Jan 2013 11:13:52 +0100
Date: Tue, 29 Jan 2013 10:13:52 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <006201cdfe06$e39bf480$aad3dd80$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "Matteo.Berioli@dlr.de" <Matteo.Berioli@dlr.de>, "wes@mti-systems.com" <wes@mti-systems.com>
Message-id: <F5EDC35DF914C1428C28E149F10463A2689F7299@EX10-MB2-MAD.hi.inet>
Content-id: <C6F5BC83F8905942AB8B2EABA5FE4D65@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] Improved version of the TCMTF Charter proposal (v3)
Thread-index: Ac35YPWFYtkaxKqFS8i6lSjqRjQ45gAiJpYAAQHLAoAAA3FBgAACuWCA
user-agent: Microsoft-MacOutlook/14.2.5.121010
X-AuditID: 0a5f4068-b7fc06d000000c70-fc-5107a0e0dc69
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMKsWRmVeSWpSXmKPExsXCFe/ApftgAXugwey/kha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxt32tywFKwwqTjZUNTDeVuti5OCQEDCRuHNHuouRE8gUk7hw bz1bFyMXh5DAVkaJefc+MIIkhASeM0rsueEBkdjEKPFk3Xx2kASLgKrE+WUL2UBsNgEtidN3 V7GA2MICHhKnzt5gBrE5BSwk3s7dzgyxQUHiz7nHLCCDRAT6GSWu3VvICuIwC6xmlJh5YQsb yEm8At4S269WgTQwC5hJ9E6/wgpi8woISvyYfI8FIq4j0fv9GzOELS7R3HoTKq4t8eTdBbB6 RgFZiXfz57OCjBQR8JTYdUwSJCwi4CYxs3sB2M2iAnoSbcfOsEPcJiCxZM95qDtFJV4+/sc6 gVFiFpIrZiG5YhaSK2YhuWIWkisWMLKuYhQrTirKTM8oyU3MzEk3MNTLyNTLzEst2cQIibmM HYzLd6ocYhTgYFTi4f1wjTVQiDWxrLgy9xCjJAeTkihvxlz2QCG+pPyUyozE4oz4otKc1OJD jBIczEoivK61QDnelMTKqtSifJiUDAeHkgTvo/lAKcGi1PTUirTMHGBigUkzcXCCtPMAtQsu AGkvLkjMLc5Mh8ifYjTk2P+k/TkjR8uBbiA5Y2LPc0Yhlrz8vFQpcd6dIEMFQBoySvPgZr5i FAc6Xpj3MUiWB5gy4aa9AlrEBLTIqA1sUUkiQkqqgXH9sV7pXCMblozPancfNO56aOb87EJ1 fVKih+8pD53pQmEdEe2qAXtbup9PFPjy9E98aGxn5kKTdUejjZ+5r4tsD5N7v27OfmFLJ+/r 6/OOZ6+YNs/03bbiPdfN+6ewbHdWeydgOGVmgFhfjW/B6do9+g6McbrTjZ6lL62qEDZ7K/iT T+EorxJLcUaioRZzUXEiAI0dnFxWAwAA
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, "Gonzalo.Camarillo@ericsson.com" <Gonzalo.Camarillo@ericsson.com>, "Martin.Stiemerling@neclab.eu" <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 29 Jan 2013 10:13:56 -0000

Hi all,

        In my opinion the WG is needed. TCMTF discussion have reach enough
interest and enough roadmap to have a room for itself, at least an small
room. As Jose said, there are two enough active drafts and there is
potentially room for three more, and I think this is a justification by
itself.
        On the other hand, I also think that we are problem centered. At le=
ast
being in a network operation feet I find TCMTF useful enough.

Regards,

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




On 29/01/13 10:56, "Jose Saldana" <jsaldana@unizar.es> wrote:

>Matteo,
>
>Thanks a lot. Well, in this case, I don't agree with you (only in this
>case).
>
>The idea with TCMTF was to create a "small" Working Group, the same way as
>they are created in other Areas (e.g. RAI).
>
>As Wes said in November, " In my opinion, it is something a separate WG
>should be created to handle, and not something to try to do inside the
>TSVWG, since there are already a handful of things TSVWG is wrestling
>with,
>and it creates too much "context switching" to have a lot of unrelated
>topics under work there."
>
>The question is that the TSVWG group has a lot of interesting things now,
>and it would be better to discuss TCMTF separately. In fact, since the
>Summer, we are discussing it in another mailing list. This is good, but in
>fact many people from TSVWG have not followed our discussion.
>
>In addition, a lot of time has passed. TCMTF draft was presented in Paris
>10
>months ago. A lot of people from many institutions have become interested
>on
>it. We have two drafts and three more possibilities.
>
>Neither am I an expert on IETF, but I understand that things have some
>"momentum": if you let time go by, people may lose their interest. And
>curently interest does exist, as we have seen in the list. So why not now?
>
>In addition, the new version of the Charter is more problem-centered (I
>hope).
>
>Thanks and best regards,
>
>Jose
>
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Matteo.Berioli@dlr.de
>> Enviado el: martes, 29 de enero de 2013 9:18
>> Para: wes@mti-systems.com; jsaldana@unizar.es
>> CC: tcmtf@ietf.org; Gonzalo.Camarillo@ericsson.com;
>> Martin.Stiemerling@neclab.eu
>> Asunto: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
>>
>> Dear all,
>>
>> I don't have a huge experience in IETF, but feel it is important to
>express my
>> opinion this time.
>> I have the feeling building a new WG is a bit premature, considering
>>that
>we
>> just have an Internet draft.
>> I also find the discussion a bit documents-driven, rather than problems-
>> driven.
>> IMHO we could wait a bit, before creating the WG, to see whether the
>>ideas
>> we have really solve real-world problems.
>>
>> That's it. Hope this helps.
>>
>> Matteo
>>
>>
>> -----Original Message-----
>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
>> Of Wesley Eddy
>> Sent: 24 January 2013 06:16
>> To: jsaldana@unizar.es
>> Cc: tcmtf@ietf.org; Gonzalo Camarillo; Martin Stiemerling
>> Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
>>
>> On 1/23/2013 6:58 AM, Jose Saldana wrote:
>> > Hello all.
>> >
>> >
>> >
>> > After reading the messages in the mailing list, I think we have
>> > arrived to a solution. Each of the documents has been discussed in a
>> > separate thread, so I have tried to take everything into account.
>> > Documents (A) and (B) would be in the Charter. Documents (C) and (D)
>> > would only be announced as possibilities for re-chartering, and
>> > Document (E) can wait a little.
>> >
>> > ...
>>
>>
>> In my opinion, this is decent, though here are two criticisms:
>>
>> (1) In my opinion, it focuses too much on documents to be produced,
>>     rather than fully and clearly motivating why the working group
>>     is needed (i.e. to solve a problem, not to develop documents),
>>     how it's scope is delimited (i.e. what it *won't* touch isn't
>>     clear to me, along with what other areas/WGs need to be
>>     coordinated with), and what the end-goal is.
>>
>> (2) There's a focus on defining technical solutions prior to the
>>     mention of fleshing out and totally defining the use cases /
>>     requirements.  In my opinion, that appears backwards :).
>>
>> That said, I'm generally supportive of this work.  In my opinion, as an
>AD, we
>> would normally feel better having a BoF before forming a WG, for two
>> reasons (1) to get other areas (e.g. RAI) to be aware of what's being
>> proposed, and (2) to vet that there really is a community of
>>stakeholders
>> that are engaged to do the work.  In this case, I think the 2nd point is
>> evident from the mailing list, and I don't have a concern about it at
>>all.
>I
>> think the 1st point can be addressed through the responsible AD
>> coordinating with the IESG and the directorates or area mailing lists
>>that
>> related areas have.
>> Since I'm going away as an AD though, what really matters at the moment
>>is
>> what Martin thinks :).
>>
>> --
>> Wes Eddy
>> MTI Systems
>> _______________________________________________
>> 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 Martin.Stiemerling@neclab.eu  Tue Jan 29 02:39:27 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC90F21F84EB for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 02:39:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.493
X-Spam-Level: 
X-Spam-Status: No, score=-103.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 bGsOq-MXzUeQ for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 02:39:26 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7B3F621F84E3 for <tcmtf@ietf.org>; Tue, 29 Jan 2013 02:39:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id DDA4C102F7B; Tue, 29 Jan 2013 11:39:25 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3BDw-7wk6ECs; Tue, 29 Jan 2013 11:39:25 +0100 (CET)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id C0328102F78; Tue, 29 Jan 2013 11:38:55 +0100 (CET)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 29 Jan 2013 11:38:45 +0100
Message-ID: <5107A6BF.60707@neclab.eu>
Date: Tue, 29 Jan 2013 11:38:55 +0100
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: FERNANDO PASCUAL BLANCO <fpb@tid.es>
References: <F5EDC35DF914C1428C28E149F10463A2689F7299@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A2689F7299@EX10-MB2-MAD.hi.inet>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [10.1.1.190]
Cc: "wes@mti-systems.com" <wes@mti-systems.com>, "tcmtf@ietf.org" <tcmtf@ietf.org>, "Matteo.Berioli@dlr.de" <Matteo.Berioli@dlr.de>, "Gonzalo.Camarillo@ericsson.com" <Gonzalo.Camarillo@ericsson.com>, "jsaldana@unizar.es" <jsaldana@unizar.es>
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 29 Jan 2013 10:39:27 -0000

Hi all,

The BoF deadline for the upcoming meeting was Jan 28.

Further, my understanding is the relevant proponents cannot make it to 
the IETF meeting in March in Orlando, but that there is a plan for the 
IETF meeting in Berlin in July 2013.

   Martin

On 01/29/2013 11:13 AM, FERNANDO PASCUAL BLANCO wrote:
> Hi all,
>
>          In my opinion the WG is needed. TCMTF discussion have reach enough
> interest and enough roadmap to have a room for itself, at least an small
> room. As Jose said, there are two enough active drafts and there is
> potentially room for three more, and I think this is a justification by
> itself.
>          On the other hand, I also think that we are problem centered. At least
> being in a network operation feet I find TCMTF useful enough.
>
> Regards,
>
> Fernando Pascual Blanco
> Telefónica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>
>
>
>
> On 29/01/13 10:56, "Jose Saldana" <jsaldana@unizar.es> wrote:
>
>> Matteo,
>>
>> Thanks a lot. Well, in this case, I don't agree with you (only in this
>> case).
>>
>> The idea with TCMTF was to create a "small" Working Group, the same way as
>> they are created in other Areas (e.g. RAI).
>>
>> As Wes said in November, " In my opinion, it is something a separate WG
>> should be created to handle, and not something to try to do inside the
>> TSVWG, since there are already a handful of things TSVWG is wrestling
>> with,
>> and it creates too much "context switching" to have a lot of unrelated
>> topics under work there."
>>
>> The question is that the TSVWG group has a lot of interesting things now,
>> and it would be better to discuss TCMTF separately. In fact, since the
>> Summer, we are discussing it in another mailing list. This is good, but in
>> fact many people from TSVWG have not followed our discussion.
>>
>> In addition, a lot of time has passed. TCMTF draft was presented in Paris
>> 10
>> months ago. A lot of people from many institutions have become interested
>> on
>> it. We have two drafts and three more possibilities.
>>
>> Neither am I an expert on IETF, but I understand that things have some
>> "momentum": if you let time go by, people may lose their interest. And
>> curently interest does exist, as we have seen in the list. So why not now?
>>
>> In addition, the new version of the Charter is more problem-centered (I
>> hope).
>>
>> Thanks and best regards,
>>
>> Jose
>>
>>
>>> -----Mensaje original-----
>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>>> Matteo.Berioli@dlr.de
>>> Enviado el: martes, 29 de enero de 2013 9:18
>>> Para: wes@mti-systems.com; jsaldana@unizar.es
>>> CC: tcmtf@ietf.org; Gonzalo.Camarillo@ericsson.com;
>>> Martin.Stiemerling@neclab.eu
>>> Asunto: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
>>>
>>> Dear all,
>>>
>>> I don't have a huge experience in IETF, but feel it is important to
>> express my
>>> opinion this time.
>>> I have the feeling building a new WG is a bit premature, considering
>>> that
>> we
>>> just have an Internet draft.
>>> I also find the discussion a bit documents-driven, rather than problems-
>>> driven.
>>> IMHO we could wait a bit, before creating the WG, to see whether the
>>> ideas
>>> we have really solve real-world problems.
>>>
>>> That's it. Hope this helps.
>>>
>>> Matteo
>>>
>>>
>>> -----Original Message-----
>>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
>>> Of Wesley Eddy
>>> Sent: 24 January 2013 06:16
>>> To: jsaldana@unizar.es
>>> Cc: tcmtf@ietf.org; Gonzalo Camarillo; Martin Stiemerling
>>> Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
>>>
>>> On 1/23/2013 6:58 AM, Jose Saldana wrote:
>>>> Hello all.
>>>>
>>>>
>>>>
>>>> After reading the messages in the mailing list, I think we have
>>>> arrived to a solution. Each of the documents has been discussed in a
>>>> separate thread, so I have tried to take everything into account.
>>>> Documents (A) and (B) would be in the Charter. Documents (C) and (D)
>>>> would only be announced as possibilities for re-chartering, and
>>>> Document (E) can wait a little.
>>>>
>>>> ...
>>>
>>>
>>> In my opinion, this is decent, though here are two criticisms:
>>>
>>> (1) In my opinion, it focuses too much on documents to be produced,
>>>      rather than fully and clearly motivating why the working group
>>>      is needed (i.e. to solve a problem, not to develop documents),
>>>      how it's scope is delimited (i.e. what it *won't* touch isn't
>>>      clear to me, along with what other areas/WGs need to be
>>>      coordinated with), and what the end-goal is.
>>>
>>> (2) There's a focus on defining technical solutions prior to the
>>>      mention of fleshing out and totally defining the use cases /
>>>      requirements.  In my opinion, that appears backwards :).
>>>
>>> That said, I'm generally supportive of this work.  In my opinion, as an
>> AD, we
>>> would normally feel better having a BoF before forming a WG, for two
>>> reasons (1) to get other areas (e.g. RAI) to be aware of what's being
>>> proposed, and (2) to vet that there really is a community of
>>> stakeholders
>>> that are engaged to do the work.  In this case, I think the 2nd point is
>>> evident from the mailing list, and I don't have a concern about it at
>>> all.
>> I
>>> think the 1st point can be addressed through the responsible AD
>>> coordinating with the IESG and the directorates or area mailing lists
>>> that
>>> related areas have.
>>> Since I'm going away as an AD though, what really matters at the moment
>>> is
>>> what Martin thinks :).
>>>
>>> --
>>> Wes Eddy
>>> MTI Systems
>>> _______________________________________________
>>> 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 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
>

-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe - Network Research Division NEC Europe Limited
Registered Office: NEC House, 1 Victoria Road, London W3 6BL
Registered in England 283

From jsaldana@unizar.es  Tue Jan 29 02:57:39 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48CBC21F86F8 for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 02:57:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.582
X-Spam-Level: 
X-Spam-Status: No, score=-6.582 tagged_above=-999 required=5 tests=[AWL=0.017,  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 dSDCxWq8qQp6 for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 02:57:38 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id A75D021F86F5 for <tcmtf@ietf.org>; Tue, 29 Jan 2013 02:57:37 -0800 (PST)
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 r0TAvUbe026489; Tue, 29 Jan 2013 11:57:30 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Martin Stiemerling'" <martin.stiemerling@neclab.eu>
References: <F5EDC35DF914C1428C28E149F10463A2689F7299@EX10-MB2-MAD.hi.inet> <5107A6BF.60707@neclab.eu>
In-Reply-To: <5107A6BF.60707@neclab.eu>
Date: Tue, 29 Jan 2013 11:57:40 +0100
Organization: Universidad de Zaragoza
Message-ID: <002801cdfe0f$75763ca0$6062b5e0$@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
Content-language: es
Thread-index: AQFY0DOipV/Pxoa4FNZNDLZw19DjLQHnx4xImTs8twA=
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: wes@mti-systems.com, tcmtf@ietf.org, Gonzalo.Camarillo@ericsson.com
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 29 Jan 2013 10:57:39 -0000

Yes, Martin. The idea is that many interested people may attend IETF =
Berlin
in July: at least I know about interested people from U. Zaragoza, DLR,
Telefonica, U. Zagreb, U. Stuttgart, who could attend that BoF. And also
co-authors from Cisco (Dan, Michael, and perhaps Muthu) may be there. =
Well,
these are the news I have. In addition, Mirko and I would also be able =
to
organize the "online games traffic tutorial there".

So is your idea to have a BoF for discussing the TCMTF WG in Berlin? Do =
you
prefer that possibility instead of the "DISPATCH" option that Gonzalo
suggested? If you confirm that, we would take it into account in order =
to
organize the summer calendar.

Thanks a lot,

Jose
PS: This is the option that Gonzalo suggested to Wes (November 29th):
"Hi Wes,

sure. When the proponents have a charter proposal ready, feel free to =
send
it to the TSVAREA list for comments while informing all the other lists. =
If
you want, I can take care of informing the DISPATCH list pointing to the
relevant message in the TSVAREA list when you send it.

With respect to where discussions should take place, DISPATCH =
participants
will find it easier to send comments on the DISPATCH list.
However, if sending comments requires subscribing to a different list =
and
sending comments to a different crowd, many may not bother commenting. I =
can
monitor the discussions in DISPATCH and send you a summary if needed. =
Since
we are talking about very few lists, it should be relatively easy to =
keep
things under control.

Cheers,

Gonzalo"
> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Martin Stiemerling
> Enviado el: martes, 29 de enero de 2013 11:39
> Para: FERNANDO PASCUAL BLANCO
> CC: wes@mti-systems.com; tcmtf@ietf.org; Matteo.Berioli@dlr.de;
> Gonzalo.Camarillo@ericsson.com; jsaldana@unizar.es
> Asunto: Re: [tcmtf] Improved version of the TCMTF Charter proposal =
(v3)
>=20
> Hi all,
>=20
> The BoF deadline for the upcoming meeting was Jan 28.
>=20
> Further, my understanding is the relevant proponents cannot make it to =
the
> IETF meeting in March in Orlando, but that there is a plan for the =
IETF
> meeting in Berlin in July 2013.
>=20
>    Martin
>=20
> On 01/29/2013 11:13 AM, FERNANDO PASCUAL BLANCO wrote:
> > Hi all,
> >
> >          In my opinion the WG is needed. TCMTF discussion have reach
> > enough interest and enough roadmap to have a room for itself, at =
least
> > an small room. As Jose said, there are two enough active drafts and
> > there is potentially room for three more, and I think this is a
> > justification by itself.
> >          On the other hand, I also think that we are problem =
centered.
> > At least being in a network operation feet I find TCMTF useful =
enough.
> >
> > Regards,
> >
> > Fernando Pascual Blanco
> > Telef=F3nica Global Resources
> > Network Automation and Dynamization
> > TECHNOLOGY PEOPLE GROUP
> > F +34913128779
> > M +34682005168
> > fpb@tid.es
> >
> >
> >
> >
> > On 29/01/13 10:56, "Jose Saldana" <jsaldana@unizar.es> wrote:
> >
> >> Matteo,
> >>
> >> Thanks a lot. Well, in this case, I don't agree with you (only in
> >> this case).
> >>
> >> The idea with TCMTF was to create a "small" Working Group, the same
> >> way as they are created in other Areas (e.g. RAI).
> >>
> >> As Wes said in November, " In my opinion, it is something a =
separate
> >> WG should be created to handle, and not something to try to do =
inside
> >> the TSVWG, since there are already a handful of things TSVWG is
> >> wrestling with, and it creates too much "context switching" to have =
a
> >> lot of unrelated topics under work there."
> >>
> >> The question is that the TSVWG group has a lot of interesting =
things
> >> now, and it would be better to discuss TCMTF separately. In fact,
> >> since the Summer, we are discussing it in another mailing list. =
This
> >> is good, but in fact many people from TSVWG have not followed our
> discussion.
> >>
> >> In addition, a lot of time has passed. TCMTF draft was presented in
> >> Paris
> >> 10
> >> months ago. A lot of people from many institutions have become
> >> interested on it. We have two drafts and three more possibilities.
> >>
> >> Neither am I an expert on IETF, but I understand that things have
> >> some
> >> "momentum": if you let time go by, people may lose their interest.
> >> And curently interest does exist, as we have seen in the list. So =
why
not
> now?
> >>
> >> In addition, the new version of the Charter is more =
problem-centered
> >> (I hope).
> >>
> >> Thanks and best regards,
> >>
> >> Jose
> >>
> >>
> >>> -----Mensaje original-----
> >>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> nombre
> >>> de Matteo.Berioli@dlr.de Enviado el: martes, 29 de enero de 2013
> >>> 9:18
> >>> Para: wes@mti-systems.com; jsaldana@unizar.es
> >>> CC: tcmtf@ietf.org; Gonzalo.Camarillo@ericsson.com;
> >>> Martin.Stiemerling@neclab.eu
> >>> Asunto: Re: [tcmtf] Improved version of the TCMTF Charter proposal
> >>> (v3)
> >>>
> >>> Dear all,
> >>>
> >>> I don't have a huge experience in IETF, but feel it is important =
to
> >> express my
> >>> opinion this time.
> >>> I have the feeling building a new WG is a bit premature, =
considering
> >>> that
> >> we
> >>> just have an Internet draft.
> >>> I also find the discussion a bit documents-driven, rather than
> >>> problems- driven.
> >>> IMHO we could wait a bit, before creating the WG, to see whether =
the
> >>> ideas we have really solve real-world problems.
> >>>
> >>> That's it. Hope this helps.
> >>>
> >>> Matteo
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
> >>> Behalf Of Wesley Eddy
> >>> Sent: 24 January 2013 06:16
> >>> To: jsaldana@unizar.es
> >>> Cc: tcmtf@ietf.org; Gonzalo Camarillo; Martin Stiemerling
> >>> Subject: Re: [tcmtf] Improved version of the TCMTF Charter =
proposal
> >>> (v3)
> >>>
> >>> On 1/23/2013 6:58 AM, Jose Saldana wrote:
> >>>> Hello all.
> >>>>
> >>>>
> >>>>
> >>>> After reading the messages in the mailing list, I think we have
> >>>> arrived to a solution. Each of the documents has been discussed =
in
> >>>> a separate thread, so I have tried to take everything into =
account.
> >>>> Documents (A) and (B) would be in the Charter. Documents (C) and
> >>>> (D) would only be announced as possibilities for re-chartering, =
and
> >>>> Document (E) can wait a little.
> >>>>
> >>>> ...
> >>>
> >>>
> >>> In my opinion, this is decent, though here are two criticisms:
> >>>
> >>> (1) In my opinion, it focuses too much on documents to be =
produced,
> >>>      rather than fully and clearly motivating why the working =
group
> >>>      is needed (i.e. to solve a problem, not to develop =
documents),
> >>>      how it's scope is delimited (i.e. what it *won't* touch isn't
> >>>      clear to me, along with what other areas/WGs need to be
> >>>      coordinated with), and what the end-goal is.
> >>>
> >>> (2) There's a focus on defining technical solutions prior to the
> >>>      mention of fleshing out and totally defining the use cases /
> >>>      requirements.  In my opinion, that appears backwards :).
> >>>
> >>> That said, I'm generally supportive of this work.  In my opinion, =
as
> >>> an
> >> AD, we
> >>> would normally feel better having a BoF before forming a WG, for =
two
> >>> reasons (1) to get other areas (e.g. RAI) to be aware of what's
> >>> being proposed, and (2) to vet that there really is a community of
> >>> stakeholders that are engaged to do the work.  In this case, I =
think
> >>> the 2nd point is evident from the mailing list, and I don't have a
> >>> concern about it at all.
> >> I
> >>> think the 1st point can be addressed through the responsible AD
> >>> coordinating with the IESG and the directorates or area mailing
> >>> lists that related areas have.
> >>> Since I'm going away as an AD though, what really matters at the
> >>> moment is what Martin thinks :).
> >>>
> >>> --
> >>> Wes Eddy
> >>> MTI Systems
> >>> _______________________________________________
> >>> 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
> 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
> >
>=20
> --
> martin.stiemerling@neclab.eu
>=20
> NEC Laboratories Europe - Network Research Division NEC Europe Limited
> Registered Office: NEC House, 1 Victoria Road, London W3 6BL =
Registered in
> England 283 _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From Martin.Stiemerling@neclab.eu  Tue Jan 29 03:54:46 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DED6821F87AB for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 03:54:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.556
X-Spam-Level: 
X-Spam-Status: No, score=-103.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 AKdASLjn--ud for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 03:54:45 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7C4C821F87AA for <tcmtf@ietf.org>; Tue, 29 Jan 2013 03:54:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id DE6C4102F76; Tue, 29 Jan 2013 12:54:44 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id trdEQ+PDSezy; Tue, 29 Jan 2013 12:54:44 +0100 (CET)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id BB685102F75; Tue, 29 Jan 2013 12:54:24 +0100 (CET)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 29 Jan 2013 12:53:54 +0100
Message-ID: <5107B85B.4030908@neclab.eu>
Date: Tue, 29 Jan 2013 12:54:03 +0100
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: <jsaldana@unizar.es>
References: <F5EDC35DF914C1428C28E149F10463A2689F7299@EX10-MB2-MAD.hi.inet> <5107A6BF.60707@neclab.eu> <002801cdfe0f$75763ca0$6062b5e0$@unizar.es>
In-Reply-To: <002801cdfe0f$75763ca0$6062b5e0$@unizar.es>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [10.1.1.190]
Cc: wes@mti-systems.com, tcmtf@ietf.org, Gonzalo.Camarillo@ericsson.com
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
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, 29 Jan 2013 11:54:47 -0000

Hi Jose,

On 01/29/2013 11:57 AM, Jose Saldana wrote:
> Yes, Martin. The idea is that many interested people may attend IETF Berlin
> in July: at least I know about interested people from U. Zaragoza, DLR,
> Telefonica, U. Zagreb, U. Stuttgart, who could attend that BoF. And also
> co-authors from Cisco (Dan, Michael, and perhaps Muthu) may be there. Well,
> these are the news I have. In addition, Mirko and I would also be able to
> organize the "online games traffic tutorial there".

So Berlin is the place to make a BoF.

>
> So is your idea to have a BoF for discussing the TCMTF WG in Berlin? Do you
> prefer that possibility instead of the "DISPATCH" option that Gonzalo
> suggested? If you confirm that, we would take it into account in order to
> organize the summer calendar.

We do not have the DISPATCH option in the Transport Area.

My proposal is to start socializing the idea within the IETF and to aim 
for a BoF in Berlin. Sending the proposal to the TSVAREA list might be a 
good start.

   Martin

>
> Thanks a lot,
>
> Jose
> PS: This is the option that Gonzalo suggested to Wes (November 29th):
> "Hi Wes,
>
> sure. When the proponents have a charter proposal ready, feel free to send
> it to the TSVAREA list for comments while informing all the other lists. If
> you want, I can take care of informing the DISPATCH list pointing to the
> relevant message in the TSVAREA list when you send it.
>
> With respect to where discussions should take place, DISPATCH participants
> will find it easier to send comments on the DISPATCH list.
> However, if sending comments requires subscribing to a different list and
> sending comments to a different crowd, many may not bother commenting. I can
> monitor the discussions in DISPATCH and send you a summary if needed. Since
> we are talking about very few lists, it should be relatively easy to keep
> things under control.
>
> Cheers,
>
> Gonzalo"
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Martin Stiemerling
>> Enviado el: martes, 29 de enero de 2013 11:39
>> Para: FERNANDO PASCUAL BLANCO
>> CC: wes@mti-systems.com; tcmtf@ietf.org; Matteo.Berioli@dlr.de;
>> Gonzalo.Camarillo@ericsson.com; jsaldana@unizar.es
>> Asunto: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
>>
>> Hi all,
>>
>> The BoF deadline for the upcoming meeting was Jan 28.
>>
>> Further, my understanding is the relevant proponents cannot make it to the
>> IETF meeting in March in Orlando, but that there is a plan for the IETF
>> meeting in Berlin in July 2013.
>>
>>     Martin
>>
>> On 01/29/2013 11:13 AM, FERNANDO PASCUAL BLANCO wrote:
>>> Hi all,
>>>
>>>           In my opinion the WG is needed. TCMTF discussion have reach
>>> enough interest and enough roadmap to have a room for itself, at least
>>> an small room. As Jose said, there are two enough active drafts and
>>> there is potentially room for three more, and I think this is a
>>> justification by itself.
>>>           On the other hand, I also think that we are problem centered.
>>> At least being in a network operation feet I find TCMTF useful enough.
>>>
>>> Regards,
>>>
>>> Fernando Pascual Blanco
>>> Telefónica Global Resources
>>> Network Automation and Dynamization
>>> TECHNOLOGY PEOPLE GROUP
>>> F +34913128779
>>> M +34682005168
>>> fpb@tid.es
>>>
>>>
>>>
>>>
>>> On 29/01/13 10:56, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>>
>>>> Matteo,
>>>>
>>>> Thanks a lot. Well, in this case, I don't agree with you (only in
>>>> this case).
>>>>
>>>> The idea with TCMTF was to create a "small" Working Group, the same
>>>> way as they are created in other Areas (e.g. RAI).
>>>>
>>>> As Wes said in November, " In my opinion, it is something a separate
>>>> WG should be created to handle, and not something to try to do inside
>>>> the TSVWG, since there are already a handful of things TSVWG is
>>>> wrestling with, and it creates too much "context switching" to have a
>>>> lot of unrelated topics under work there."
>>>>
>>>> The question is that the TSVWG group has a lot of interesting things
>>>> now, and it would be better to discuss TCMTF separately. In fact,
>>>> since the Summer, we are discussing it in another mailing list. This
>>>> is good, but in fact many people from TSVWG have not followed our
>> discussion.
>>>>
>>>> In addition, a lot of time has passed. TCMTF draft was presented in
>>>> Paris
>>>> 10
>>>> months ago. A lot of people from many institutions have become
>>>> interested on it. We have two drafts and three more possibilities.
>>>>
>>>> Neither am I an expert on IETF, but I understand that things have
>>>> some
>>>> "momentum": if you let time go by, people may lose their interest.
>>>> And curently interest does exist, as we have seen in the list. So why
> not
>> now?
>>>>
>>>> In addition, the new version of the Charter is more problem-centered
>>>> (I hope).
>>>>
>>>> Thanks and best regards,
>>>>
>>>> Jose
>>>>
>>>>
>>>>> -----Mensaje original-----
>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> nombre
>>>>> de Matteo.Berioli@dlr.de Enviado el: martes, 29 de enero de 2013
>>>>> 9:18
>>>>> Para: wes@mti-systems.com; jsaldana@unizar.es
>>>>> CC: tcmtf@ietf.org; Gonzalo.Camarillo@ericsson.com;
>>>>> Martin.Stiemerling@neclab.eu
>>>>> Asunto: Re: [tcmtf] Improved version of the TCMTF Charter proposal
>>>>> (v3)
>>>>>
>>>>> Dear all,
>>>>>
>>>>> I don't have a huge experience in IETF, but feel it is important to
>>>> express my
>>>>> opinion this time.
>>>>> I have the feeling building a new WG is a bit premature, considering
>>>>> that
>>>> we
>>>>> just have an Internet draft.
>>>>> I also find the discussion a bit documents-driven, rather than
>>>>> problems- driven.
>>>>> IMHO we could wait a bit, before creating the WG, to see whether the
>>>>> ideas we have really solve real-world problems.
>>>>>
>>>>> That's it. Hope this helps.
>>>>>
>>>>> Matteo
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
>>>>> Behalf Of Wesley Eddy
>>>>> Sent: 24 January 2013 06:16
>>>>> To: jsaldana@unizar.es
>>>>> Cc: tcmtf@ietf.org; Gonzalo Camarillo; Martin Stiemerling
>>>>> Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal
>>>>> (v3)
>>>>>
>>>>> On 1/23/2013 6:58 AM, Jose Saldana wrote:
>>>>>> Hello all.
>>>>>>
>>>>>>
>>>>>>
>>>>>> After reading the messages in the mailing list, I think we have
>>>>>> arrived to a solution. Each of the documents has been discussed in
>>>>>> a separate thread, so I have tried to take everything into account.
>>>>>> Documents (A) and (B) would be in the Charter. Documents (C) and
>>>>>> (D) would only be announced as possibilities for re-chartering, and
>>>>>> Document (E) can wait a little.
>>>>>>
>>>>>> ...
>>>>>
>>>>>
>>>>> In my opinion, this is decent, though here are two criticisms:
>>>>>
>>>>> (1) In my opinion, it focuses too much on documents to be produced,
>>>>>       rather than fully and clearly motivating why the working group
>>>>>       is needed (i.e. to solve a problem, not to develop documents),
>>>>>       how it's scope is delimited (i.e. what it *won't* touch isn't
>>>>>       clear to me, along with what other areas/WGs need to be
>>>>>       coordinated with), and what the end-goal is.
>>>>>
>>>>> (2) There's a focus on defining technical solutions prior to the
>>>>>       mention of fleshing out and totally defining the use cases /
>>>>>       requirements.  In my opinion, that appears backwards :).
>>>>>
>>>>> That said, I'm generally supportive of this work.  In my opinion, as
>>>>> an
>>>> AD, we
>>>>> would normally feel better having a BoF before forming a WG, for two
>>>>> reasons (1) to get other areas (e.g. RAI) to be aware of what's
>>>>> being proposed, and (2) to vet that there really is a community of
>>>>> stakeholders that are engaged to do the work.  In this case, I think
>>>>> the 2nd point is evident from the mailing list, and I don't have a
>>>>> concern about it at all.
>>>> I
>>>>> think the 1st point can be addressed through the responsible AD
>>>>> coordinating with the IESG and the directorates or area mailing
>>>>> lists that related areas have.
>>>>> Since I'm going away as an AD though, what really matters at the
>>>>> moment is what Martin thinks :).
>>>>>
>>>>> --
>>>>> Wes Eddy
>>>>> MTI Systems
>>>>> _______________________________________________
>>>>> 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
>> 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
>>>
>>
>> --
>> martin.stiemerling@neclab.eu
>>
>> NEC Laboratories Europe - Network Research Division NEC Europe Limited
>> Registered Office: NEC House, 1 Victoria Road, London W3 6BL Registered in
>> England 283 _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>

-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe - Network Research Division NEC Europe Limited
Registered Office: NEC House, 1 Victoria Road, London W3 6BL
Registered in England 283

From Martin.Stiemerling@neclab.eu  Tue Jan 29 07:34:35 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9E421F8903 for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 07:34:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.51
X-Spam-Level: 
X-Spam-Status: No, score=-103.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 IobGs0KzwL5P for <tcmtf@ietfa.amsl.com>; Tue, 29 Jan 2013 07:34:34 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7CFE321F88A9 for <tcmtf@ietf.org>; Tue, 29 Jan 2013 07:34:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id E65C6102F74 for <tcmtf@ietf.org>; Tue, 29 Jan 2013 16:34:33 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8p2cmirsh+3X for <tcmtf@ietf.org>; Tue, 29 Jan 2013 16:34:33 +0100 (CET)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id CD3D0102F45 for <tcmtf@ietf.org>; Tue, 29 Jan 2013 16:34:28 +0100 (CET)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 29 Jan 2013 16:34:20 +0100
Message-ID: <5107EC04.4020705@neclab.eu>
Date: Tue, 29 Jan 2013 16:34:28 +0100
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: <tcmtf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Subject: [tcmtf] Considerations for Having a Successful Birds-of-a-Feather (BOF) Session
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, 29 Jan 2013 15:34:35 -0000

Dear all,

Here is some information about Birds-of-a-Feather (BOF), as some of you 
are considering requesting a BoF for the IETF meeting in Berlin:

Please read RFC 5434 [1] "Considerations for Having a Successful 
Birds-of-a-Feather (BOF) Session".

It is also not bad to check the timing for requesting a BoF:
https://www.ietf.org/meeting/cutoff-dates-2013.html#IETF87

   Martin

[1] http://www.rfc-editor.org/rfc/rfc5434.txt

-- 
IETF Transport Area Director

martin.stiemerling@neclab.eu

NEC Laboratories Europe - Network Research Division NEC Europe Limited
Registered Office: NEC House, 1 Victoria Road, London W3 6BL
Registered in England 283

From jsaldana@unizar.es  Wed Jan 30 09:21:38 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F09821F8569; Wed, 30 Jan 2013 09:21:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.584
X-Spam-Level: 
X-Spam-Status: No, score=-6.584 tagged_above=-999 required=5 tests=[AWL=0.015,  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 ZpkeVvbMBDFn; Wed, 30 Jan 2013 09:21:16 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id AC03221F85B6; Wed, 30 Jan 2013 09:21:14 -0800 (PST)
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 r0UHL6li031987; Wed, 30 Jan 2013 18:21:07 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tsv-area@ietf.org>, <tcmtf@ietf.org>
Date: Wed, 30 Jan 2013 18:21:11 +0100
Organization: Universidad de Zaragoza
Message-ID: <003001cdff0e$33658a50$9a309ef0$@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
Content-language: es
Thread-index: Ac3/DjLNZdfLStP/QW+3XuE3RhqbAA==
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Wesley Eddy <wes@mti-systems.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [tcmtf] About the possibility of having a BOF about TCMTF in IETF87
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, 30 Jan 2013 17:21:38 -0000

Hi all.

With this e-mail I would like to socialize TCMTF (Tunneling, Compressing =
and
Multiplexing Traffic Flows) within the IETF. We have the idea of =
presenting
a BOF proposal for IETF 87 in Berlin (July-August), with the aim of =
creating
a Working Group.

In this message I will talk about the problem we are trying to solve, =
and I
will try to summarize the story of TCMTF within the IETF.

- The main idea (see also the Charter proposal below) is to define a =
method
for saving bandwidth in real-time services which use tiny packets. Some
examples of these services are online games, viceoconference, in =
addition to
VoIP. The overhead of the packets of these services is significant, so =
the
efficiency can be increased when a number of flows share the same path:
packets belonging to different flows can be grouped together, adding a =
small
multiplexing delay as a counterpart. Currently, there exists an =
efficiency
improvement method for VoIP using RTP: RFC4170 (TCRTP). It considers =
header
compression by means of ECRTP; multiplexing by means of PPPMux; and
tunneling by means of L2TPv3. However, in the last years, emerging =
real-time
services which do not use UDP/RTP protocols have become popular: some of
them use UDP or even TCP. In addition, new header compression methods =
have
been defined (ROHC). So widening the scope of RFC4170 in order to =
consider
not only UDP/RTP but also other protocols is seen as convenient. The =
same
three layers would be used: header compression, multiplexing and =
end-to-end
tunneling.

Some examples of the scenarios where grouping packets is possible are:
aggregation networks of a network operator; a tunnel between two =
premises of
the same company; the access connection of an Internet Caf=E9 including =
a high
number of VoIP/gaming flows; an agreement between two network operators
could allow them to compress a number of flows they are exchanging =
between a
pair of Internet Routers; a satellite connection used for collecting the
data of a high number of sensors; etc.=20



- The story:
* A first draft was written with cooperation of some people from =
Transport
and RAI Areas. Dan Wing, one of the authors of RFC4170, is also
participating on TCMTF from the very beginning. This is the first =
version
(Feb 2012) http://tools.ietf.org/id/draft-saldana-tsvwg-tcmtf-00.txt
* It was presented in the TSVWG session (Transport Area) IETF-83, Paris,
March 27th 2012:
http://www.ietf.org/proceedings/83/minutes/minutes-83-tsvwg.txt. The
presentation is here:
http://diec.unizar.es/~jsaldana/personal/present-saldana-tsvwg-tcmtf_v2.p=
df
* A specific mailing list was created (July 10th 2012):
https://www.ietf.org/mailman/listinfo/tcmtf
* A second draft was submitted (Dec 12th 2012), " Maximum Tolerable =
Delays
when using Tunneling Compressed Multiplexed Traffic Flows":
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
* This is the current version of the initial draft:
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/. The number =
of
authors and contributors has been increased.


- Many people have participated in the mailing list, mainly from network
operators, network equipment manufacturers, a Space Agency (DLR) and
Academia.


- And finally, this is the current version of the Charter Proposal. We =
have
discussed and polished it in the list
(http://www.ietf.org/mail-archive/web/tcmtf/current/threads.html), and =
we
have arrived to this agreement:

*Description of Working Group v4*

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 higher when IPv6 is used, since 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 sending collected data in sensor networks
using wireless or satellite scenarios).

2. The efficiency cannot be increased by the inclusion of a higher =
number of
samples in a single packet, since this would harm the delay requirements =
of
the service. But there exist some scenarios in which a number of flows =
share
the same path. In this case, packets belonging to different flows can be
grouped together, adding a small multiplexing delay as a counterpart of
bandwidth saving. This delay will have to be maintained under some =
threshold
in order to grant the delay requirements. Some examples of the scenarios
where grouping packets is possible are: aggregation networks of a =
network
operator; a tunnel between two premises of the same company; the access
connection of an Internet Caf=E9 including a high number of VoIP/gaming =
flows;
an agreement between two network operators could allow them to compress =
a
number of flows they are exchanging between a pair of Internet Routers; =
a
satellite connection used for collecting the data of a high number of
sensors; etc.

3. VoIP using RTP is a clear example of a real-time service using small
packets with high overhead. In order to improve efficiency, RFC4170 =
(TCRTP)
defined a method for grouping packets when a number of flows share a =
path,
considering three different layers: header compression by means of =
ECRTP;
multiplexing by means of PPPMux; tunneling by means of L2TPv3.

4. However, in the last years, emerging real-time services which do not =
use
UDP/RTP have become popular: some of them use UDP or even TCP. So there =
is a
need of widening the scope of RFC4170 in order to consider not only =
UDP/RTP
but also other protocols. The same structure of three layers will be
considered:
- Header compression: Taking into account that real-time applications =
use
different headers (RTP/UDP, UDP or even TCP), different protocols can be
used: no compression, ECRTP, IPHC and ROHC.
- Multiplexing: If a number of flows share a path between an origin and =
a
destination, a multiplexer can build a bigger packet in which a number =
of
payloads share a common header. A demultiplexer is then necessary at the =
end
of the common path, so as to rebuild the packets as they were originally
sent. PPPMux will be the main option. Other ones are not discarded.
- Tunneling will be used to send the multiplexed packets end-to-end. The
options in this layer are L2TP, GRE and MPLS.

5. So the first objective of this group is to specify the protocol stack =
for
tunneling, compressing and multiplexing traffic flows (TCMTF). Since
standard protocols are being used at each layer, the signaling methods =
of
those protocols will be used. Interactions with the Working Groups and =
Areas
in which these protocols are developed can be expected. However, the
development of new compressing, multiplexing or tunneling protocols is =
not
an objective of this Working Group. In addition, since the current RFC =
4170
would be considered as one of the options, this RFC could be obsoleted.

6. As a first objective, a document (A) will define the different =
options
which can be used at each layer. Specific problems caused by the =
interaction
between layers will have to be issued, and suitable extensions may have =
to
be added to the involved protocols.

7. If a pair multiplexer/de- multiplexer want to establish a tunnel, =
they
have first to use a mechanism to negotiate which concrete option would =
they
use in each layer: header compression, multiplexing and tunneling. This =
will
depend on the protocols that each extreme implements at each level, and =
in
the scenario. So document (A) will also include a negotiation mechanism =
to
decide the options to use at each layer (header compression, =
multiplexing
and tunneling) between multiplexer and de-multiplexer, and a mechanism =
to
setup/release a tunnel between a multiplexer and a de-multiplexer.

8. As a counterpart of the bandwidth saving, TCMTF may add some delay =
and
jitter. This is not a problem for the services which are not sensitive =
to
delay. However, regarding delay-sensitive services, the Working Group =
will
also develop a document (B) with useful recommendations in order to =
decide
which packet flows can or can not be multiplexed and how. The document =
(B)
will present a list of available traffic classification methods which =
can be
used for identification of the service or application to which a =
particular
flow belongs, as well as recommendations of the maximum delay and jitter =
to
be added depending of the identified service or application.

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

10. In addition, specific uses of TCMTF, such as in wireless and =
satellite
scenarios, could be considered, and it will be studied whether =
modifications
or extensions are required on the protocol.

11. Interactions with other Working Groups can be expected, since TCMTF =
uses
already defined protocols for compression, multiplexing and tunneling =
(ROHC,
PPPMux, MPLS, GRE, L2TP).
=20

*Goals and Milestones*

 Specification of TCMTF protocol stack (A) and signaling mechanisms.

 Recommendations (B) of using existing traffic classification methods,
maximum delay and jitter to add, depending on the service.

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

Thank you very much,

Jose Saldana




> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Martin Stiemerling
> Enviado el: martes, 29 de enero de 2013 12:54
> Para: jsaldana@unizar.es
> CC: wes@mti-systems.com; tcmtf@ietf.org;
> Gonzalo.Camarillo@ericsson.com
> Asunto: Re: [tcmtf] Improved version of the TCMTF Charter proposal =
(v3)
>=20
> Hi Jose,
>=20
> On 01/29/2013 11:57 AM, Jose Saldana wrote:
> > Yes, Martin. The idea is that many interested people may attend IETF
> > Berlin in July: at least I know about interested people from U.
> > Zaragoza, DLR, Telefonica, U. Zagreb, U. Stuttgart, who could attend
> > that BoF. And also co-authors from Cisco (Dan, Michael, and perhaps
> > Muthu) may be there. Well, these are the news I have. In addition,
> > Mirko and I would also be able to organize the "online games traffic
tutorial
> there".
>=20
> So Berlin is the place to make a BoF.
>=20
> >
> > So is your idea to have a BoF for discussing the TCMTF WG in Berlin?
> > Do you prefer that possibility instead of the "DISPATCH" option that
> > Gonzalo suggested? If you confirm that, we would take it into =
account
> > in order to organize the summer calendar.
>=20
> We do not have the DISPATCH option in the Transport Area.
>=20
> My proposal is to start socializing the idea within the IETF and to =
aim
for a BoF
> in Berlin. Sending the proposal to the TSVAREA list might be a good =
start.
>=20
>    Martin
>=20
> >
> > Thanks a lot,
> >
> > Jose
> > PS: This is the option that Gonzalo suggested to Wes (November =
29th):
> > "Hi Wes,
> >
> > sure. When the proponents have a charter proposal ready, feel free =
to
> > send it to the TSVAREA list for comments while informing all the =
other
> > lists. If you want, I can take care of informing the DISPATCH list
> > pointing to the relevant message in the TSVAREA list when you send =
it.
> >
> > With respect to where discussions should take place, DISPATCH
> > participants will find it easier to send comments on the DISPATCH =
list.
> > However, if sending comments requires subscribing to a different =
list
> > and sending comments to a different crowd, many may not bother
> > commenting. I can monitor the discussions in DISPATCH and send you a
> > summary if needed. Since we are talking about very few lists, it
> > should be relatively easy to keep things under control.
> >
> > Cheers,
> >
> > Gonzalo"
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> >> de Martin Stiemerling Enviado el: martes, 29 de enero de 2013 11:39
> >> Para: FERNANDO PASCUAL BLANCO
> >> CC: wes@mti-systems.com; tcmtf@ietf.org; Matteo.Berioli@dlr.de;
> >> Gonzalo.Camarillo@ericsson.com; jsaldana@unizar.es
> >> Asunto: Re: [tcmtf] Improved version of the TCMTF Charter proposal
> >> (v3)
> >>
> >> Hi all,
> >>
> >> The BoF deadline for the upcoming meeting was Jan 28.
> >>
> >> Further, my understanding is the relevant proponents cannot make it
> >> to the IETF meeting in March in Orlando, but that there is a plan =
for
> >> the IETF meeting in Berlin in July 2013.
> >>
> >>     Martin
> >>
> >> On 01/29/2013 11:13 AM, FERNANDO PASCUAL BLANCO wrote:
> >>> Hi all,
> >>>
> >>>           In my opinion the WG is needed. TCMTF discussion have
> >>> reach enough interest and enough roadmap to have a room for =
itself,
> >>> at least an small room. As Jose said, there are two enough active
> >>> drafts and there is potentially room for three more, and I think
> >>> this is a justification by itself.
> >>>           On the other hand, I also think that we are problem
centered.
> >>> At least being in a network operation feet I find TCMTF useful =
enough.
> >>>
> >>> Regards,
> >>>
> >>> Fernando Pascual Blanco
> >>> Telef=F3nica Global Resources
> >>> Network Automation and Dynamization
> >>> TECHNOLOGY PEOPLE GROUP
> >>> F +34913128779
> >>> M +34682005168
> >>> fpb@tid.es
> >>>
> >>>
> >>>
> >>>
> >>> On 29/01/13 10:56, "Jose Saldana" <jsaldana@unizar.es> wrote:
> >>>
> >>>> Matteo,
> >>>>
> >>>> Thanks a lot. Well, in this case, I don't agree with you (only in
> >>>> this case).
> >>>>
> >>>> The idea with TCMTF was to create a "small" Working Group, the =
same
> >>>> way as they are created in other Areas (e.g. RAI).
> >>>>
> >>>> As Wes said in November, " In my opinion, it is something a
> >>>> separate WG should be created to handle, and not something to try
> >>>> to do inside the TSVWG, since there are already a handful of =
things
> >>>> TSVWG is wrestling with, and it creates too much "context
> >>>> switching" to have a lot of unrelated topics under work there."
> >>>>
> >>>> The question is that the TSVWG group has a lot of interesting
> >>>> things now, and it would be better to discuss TCMTF separately. =
In
> >>>> fact, since the Summer, we are discussing it in another mailing
> >>>> list. This is good, but in fact many people from TSVWG have not
> >>>> followed our
> >> discussion.
> >>>>
> >>>> In addition, a lot of time has passed. TCMTF draft was presented =
in
> >>>> Paris
> >>>> 10
> >>>> months ago. A lot of people from many institutions have become
> >>>> interested on it. We have two drafts and three more =
possibilities.
> >>>>
> >>>> Neither am I an expert on IETF, but I understand that things have
> >>>> some
> >>>> "momentum": if you let time go by, people may lose their =
interest.
> >>>> And curently interest does exist, as we have seen in the list. So
> >>>> why
> > not
> >> now?
> >>>>
> >>>> In addition, the new version of the Charter is more
> >>>> problem-centered (I hope).
> >>>>
> >>>> Thanks and best regards,
> >>>>
> >>>> Jose
> >>>>
> >>>>
> >>>>> -----Mensaje original-----
> >>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> nombre
> >>>>> de Matteo.Berioli@dlr.de Enviado el: martes, 29 de enero de 2013
> >>>>> 9:18
> >>>>> Para: wes@mti-systems.com; jsaldana@unizar.es
> >>>>> CC: tcmtf@ietf.org; Gonzalo.Camarillo@ericsson.com;
> >>>>> Martin.Stiemerling@neclab.eu
> >>>>> Asunto: Re: [tcmtf] Improved version of the TCMTF Charter =
proposal
> >>>>> (v3)
> >>>>>
> >>>>> Dear all,
> >>>>>
> >>>>> I don't have a huge experience in IETF, but feel it is important
> >>>>> to
> >>>> express my
> >>>>> opinion this time.
> >>>>> I have the feeling building a new WG is a bit premature,
> >>>>> considering that
> >>>> we
> >>>>> just have an Internet draft.
> >>>>> I also find the discussion a bit documents-driven, rather than
> >>>>> problems- driven.
> >>>>> IMHO we could wait a bit, before creating the WG, to see whether
> >>>>> the ideas we have really solve real-world problems.
> >>>>>
> >>>>> That's it. Hope this helps.
> >>>>>
> >>>>> Matteo
> >>>>>
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
> >>>>> Behalf Of Wesley Eddy
> >>>>> Sent: 24 January 2013 06:16
> >>>>> To: jsaldana@unizar.es
> >>>>> Cc: tcmtf@ietf.org; Gonzalo Camarillo; Martin Stiemerling
> >>>>> Subject: Re: [tcmtf] Improved version of the TCMTF Charter
> >>>>> proposal
> >>>>> (v3)
> >>>>>
> >>>>> On 1/23/2013 6:58 AM, Jose Saldana wrote:
> >>>>>> Hello all.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> After reading the messages in the mailing list, I think we have
> >>>>>> arrived to a solution. Each of the documents has been discussed
> >>>>>> in a separate thread, so I have tried to take everything into
account.
> >>>>>> Documents (A) and (B) would be in the Charter. Documents (C) =
and
> >>>>>> (D) would only be announced as possibilities for re-chartering,
> >>>>>> and Document (E) can wait a little.
> >>>>>>
> >>>>>> ...
> >>>>>
> >>>>>
> >>>>> In my opinion, this is decent, though here are two criticisms:
> >>>>>
> >>>>> (1) In my opinion, it focuses too much on documents to be =
produced,
> >>>>>       rather than fully and clearly motivating why the working =
group
> >>>>>       is needed (i.e. to solve a problem, not to develop =
documents),
> >>>>>       how it's scope is delimited (i.e. what it *won't* touch =
isn't
> >>>>>       clear to me, along with what other areas/WGs need to be
> >>>>>       coordinated with), and what the end-goal is.
> >>>>>
> >>>>> (2) There's a focus on defining technical solutions prior to the
> >>>>>       mention of fleshing out and totally defining the use cases =
/
> >>>>>       requirements.  In my opinion, that appears backwards :).
> >>>>>
> >>>>> That said, I'm generally supportive of this work.  In my =
opinion,
> >>>>> as an
> >>>> AD, we
> >>>>> would normally feel better having a BoF before forming a WG, for
> >>>>> two reasons (1) to get other areas (e.g. RAI) to be aware of
> >>>>> what's being proposed, and (2) to vet that there really is a
> >>>>> community of stakeholders that are engaged to do the work.  In
> >>>>> this case, I think the 2nd point is evident from the mailing =
list,
> >>>>> and I don't have a concern about it at all.
> >>>> I
> >>>>> think the 1st point can be addressed through the responsible AD
> >>>>> coordinating with the IESG and the directorates or area mailing
> >>>>> lists that related areas have.
> >>>>> Since I'm going away as an AD though, what really matters at the
> >>>>> moment is what Martin thinks :).
> >>>>>
> >>>>> --
> >>>>> Wes Eddy
> >>>>> MTI Systems
> >>>>> _______________________________________________
> >>>>> 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
> >> 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
> >>>
> >>
> >> --
> >> martin.stiemerling@neclab.eu
> >>
> >> NEC Laboratories Europe - Network Research Division NEC Europe
> >> Limited Registered Office: NEC House, 1 Victoria Road, London W3 =
6BL
> >> Registered in England 283
> >> _______________________________________________
> >> tcmtf mailing list
> >> tcmtf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >
>=20
> --
> martin.stiemerling@neclab.eu
>=20
> NEC Laboratories Europe - Network Research Division NEC Europe Limited
> Registered Office: NEC House, 1 Victoria Road, London W3 6BL =
Registered in
> England 283 _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From lars@netapp.com  Wed Jan 30 09:46:18 2013
Return-Path: <lars@netapp.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 D4C0821F8867; Wed, 30 Jan 2013 09:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.066
X-Spam-Level: 
X-Spam-Status: No, score=-10.066 tagged_above=-999 required=5 tests=[AWL=0.533, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 3wXvdInk1Fd7; Wed, 30 Jan 2013 09:46:18 -0800 (PST)
Received: from mx1.netapp.com (mx1.netapp.com [216.240.18.38]) by ietfa.amsl.com (Postfix) with ESMTP id F135521F886C; Wed, 30 Jan 2013 09:46:17 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,569,1355126400"; d="scan'208";a="238526612"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx1-out.netapp.com with ESMTP; 30 Jan 2013 09:45:54 -0800
Received: from vmwexceht03-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.76.241]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0UHjqG1003048; Wed, 30 Jan 2013 09:45:53 -0800 (PST)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.02.0328.009; Wed, 30 Jan 2013 09:45:52 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "<jsaldana@unizar.es>" <jsaldana@unizar.es>
Thread-Topic: About the possibility of having a BOF about TCMTF in IETF87
Thread-Index: Ac3/DjLNZdfLStP/QW+3XuE3RhqbAAARoDYA
Date: Wed, 30 Jan 2013 17:45:52 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F6B1C78@SACEXCMBX01-PRD.hq.netapp.com>
References: <003001cdff0e$33658a50$9a309ef0$@unizar.es>
In-Reply-To: <003001cdff0e$33658a50$9a309ef0$@unizar.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.117]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <BE324780E30DD94CA80C2DF6E03B1438@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 31 Jan 2013 00:30:11 -0800
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] About the possibility of having a BOF about TCMTF in IETF87
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, 30 Jan 2013 17:46:18 -0000

Hi,

On Jan 30, 2013, at 18:21, Jose Saldana <jsaldana@unizar.es> wrote:
> The main idea (see also the Charter proposal below) is to define a method
> for saving bandwidth in real-time services which use tiny packets.
...
> In addition, new header compression methods have
> been defined (ROHC). So widening the scope of RFC4170 in order to conside=
r
> not only UDP/RTP but also other protocols is seen as convenient.

why an extension of 4170 and not new ROHC profiles?

Lars

From jsaldana@unizar.es  Thu Jan 31 00:47:01 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 874B421F85D0; Thu, 31 Jan 2013 00:47:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.585
X-Spam-Level: 
X-Spam-Status: No, score=-6.585 tagged_above=-999 required=5 tests=[AWL=0.014,  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 o4W+-bOSVoaQ; Thu, 31 Jan 2013 00:47:00 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFA121F85CC; Thu, 31 Jan 2013 00:47:00 -0800 (PST)
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 r0V8ksSE017275; Thu, 31 Jan 2013 09:46:55 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Eggert, Lars'" <lars@netapp.com>
References: <003001cdff0e$33658a50$9a309ef0$@unizar.es> <D4D47BCFFE5A004F95D707546AC0D7E91F6B1C78@SACEXCMBX01-PRD.hq.netapp.com>
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F6B1C78@SACEXCMBX01-PRD.hq.netapp.com>
Date: Thu, 31 Jan 2013 09:46:56 +0100
Organization: Universidad de Zaragoza
Message-ID: <002c01cdff8f$88251430$986f3c90$@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: AQH4VYfsQr5DqoVbCGYPdBLd2Eoe0AIPaXGhl/30MgA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, tsv-area@ietf.org
Subject: Re: [tcmtf] About the possibility of having a BOF about TCMTF in IETF87
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, 31 Jan 2013 08:47:01 -0000

Hi,

The idea is not improving header compression techniques here. Of course
improvements in header compression are interesting, but there are other
places for doing that. We only try to put together these three =
"orthogonal
layers":
- Header compression
- Multiplexing
- Tunneling

The question is that when you compress a single flow, you have to do it
hop-by-hop (which implies a lot of processing in every node), or you can =
add
a tunnel in order to do it end-to-end. So if you have a single flow, you =
are
reducing overhead by means of header compression, but the tunnel is =
adding
overhead again.

But there are scenarios where a number of flows share a path, so in that
case you not only compress headers, but also put a number of packets =
into a
single bundle, and then the tunnel overhead is shared by all the =
packets.

Our idea is that RFC4170 can be extended to other services. But RFC4170 =
is
not only header compression but also multiplexing and tunneling. So the =
same
ROHC profiles for that services will be suitable for TCMTF. However, we =
only
want to use existing or new header compression methods. We do not intend =
to
develop new ones here.

In this paper
(http://diec.unizar.es/~jsaldana/personal/ottawa_ICC_2012_in_proc.pdf) =
we
presented some results of the obtained savings. For VoIP (RFC4170) we =
could
save up to 65% of the bandwidth. But for new emerging services, like =
e.g.,
MMORPG games, the saving can be next to 60%
(http://diec.unizar.es/~jsaldana/personal/sergei_SPECTS_2012_in_proc.pdf)=
.
So why not using the same idea in these new services?

Does this answer your question?

Best regards,

Jose

> -----Mensaje original-----
> De: Eggert, Lars [mailto:lars@netapp.com]
> Enviado el: mi=E9rcoles, 30 de enero de 2013 18:46
> Para: <jsaldana@unizar.es>
> CC: tsv-area@ietf.org; tcmtf@ietf.org; Gonzalo Camarillo; Martin
Stiemerling
> Asunto: Re: About the possibility of having a BOF about TCMTF in =
IETF87
>=20
> Hi,
>=20
> On Jan 30, 2013, at 18:21, Jose Saldana <jsaldana@unizar.es> wrote:
> > The main idea (see also the Charter proposal below) is to define a
> > method for saving bandwidth in real-time services which use tiny
packets.
> ...
> > In addition, new header compression methods have been defined =
(ROHC).
> > So widening the scope of RFC4170 in order to consider not only =
UDP/RTP
> > but also other protocols is seen as convenient.
>=20
> why an extension of 4170 and not new ROHC profiles?
>=20
> Lars

