
From david.black@emc.com  Fri Jan  3 19:05:33 2014
Return-Path: <david.black@emc.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 536001AE033; Fri,  3 Jan 2014 19:05:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level: 
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wfpgcsz16lUo; Fri,  3 Jan 2014 19:05:29 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 5F7F11AE04A; Fri,  3 Jan 2014 19:05:29 -0800 (PST)
Received: from maildlpprd51.lss.emc.com (maildlpprd51.lss.emc.com [10.106.48.155]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0435ILq009213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jan 2014 22:05:19 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s0435ILq009213
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1388804719; bh=4343WqqOrPIjSi3bgycoA21UMss=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=eJk93ynU7WXjZGvW532ocg5acIHPxqu3AawoXE0v9xOhfwsvqehjyTDY0IrG+ol0+ AP/h0SpfmBw1DO4MMh+i1+1Tx8tgdNG+KR7eiyDasdavQQLxAf/nQRmC5JSa2yUYPY IDzI59sZU9BcKEW97bx1ELYu+Bncq+w1kS1GgdK0=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s0435ILq009213
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd51.lss.emc.com (RSA Interceptor); Fri, 3 Jan 2014 22:05:01 -0500
Received: from mxhub09.corp.emc.com (mxhub09.corp.emc.com [10.254.92.104]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s04350YW015161 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 3 Jan 2014 22:05:01 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub09.corp.emc.com ([10.254.92.104]) with mapi; Fri, 3 Jan 2014 22:05:00 -0500
From: "Black, David" <david.black@emc.com>
To: Jose Saldana <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
Date: Fri, 3 Jan 2014 22:04:58 -0500
Thread-Topic: TCMTF-Feedback about a possible BoF in London
Thread-Index: Ac79ZUO9+o1eWvDOTZW4bKGOX0YCWwLjYMDQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026EF2FF8F@MX15A.corp.emc.com>
References: <00c401cefd65$6e8ef570$4bace050$@unizar.es>
In-Reply-To: <00c401cefd65$6e8ef570$4bace050$@unizar.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8D3D17ACE214DC429325B2B98F3AE712026EF2FF8FMX15Acorpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
X-Mailman-Approved-At: Sat, 04 Jan 2014 02:45:09 -0800
Cc: Martin Stiemerling <mls.ietf@googlemail.com>, "Black, David" <david.black@emc.com>
Subject: Re: [tcmtf] TCMTF-Feedback about a possible BoF in London
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf/>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jan 2014 03:05:33 -0000

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

A second BoF has the explicit goal of forming a WG, as a third BoF
is not permitted.  In that regard, the new charter seems long and
somewhat lacking in focus.  Two key things I look for in a proposed
charter are what problem (or problems) the proposed WG is looking to
solve and an initial approach to the problem or problems.

In the new draft charter, the problem statement appears to be in
paragraph 4 with paragraph 1 providing important background.  The
focus of the work appears to be on extending TCRTP (RFC 4170) to
UDP and to include new compression protocols.  In contrast, I have
a hard time discerning the initial approach from the new draft charter.

In light of this, there are a few things that I wish the new
draft charter had definitive proposals for:

      a) Whether to replace RFC 4170 vs. write a new RFC (could be
            UDP-only or UDP + RTP/UDP) as a complement to RFC 4170.
      b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC (RFC 2507 ?).
            Non-use of ECRTP would be a major change to 4170, and I
wonder about IPHC, as opposed to the ROHCv2 profiles.
      c) Analogies to b) for the Mux and Tunnel layers of the stack.

Overall, it looks like the first task of the WG is to select the protocol
stack to standardize - I have misgivings about that, and would prefer to
see a concrete proposal in a crisp charter that ran along the following
lines, naming the protocols to be used:

1) RFC 4170 does X, and needs the following changes/additions: X, Y, Z.
2) The WG will replace RFC 4170 with a new RFC that contains: A, B, C.

A specific proposal or proposals for the protocol stack or stacks
would also narrow the scope of item 9 in the charter on the negotiation
mechanism.  I also don't see a goal/milestone listed for an extension to
or replacement for RFC 4170.

I'd prefer to see a much shorter more focused draft charter.  There's a
bunch of background material that does not seem crucial to the charter,
starting w/paragraphs 2 and 3.

Thanks,
--David

From: tsv-area [mailto:tsv-area-bounces@ietf.org] On Behalf Of Jose Saldana
Sent: Friday, December 20, 2013 4:26 AM
To: tcmtf@ietf.org; tsv-area@ietf.org
Cc: Martin Stiemerling
Subject: TCMTF-Feedback about a possible BoF in London

Hi all,

After the feedback received in the BoF in Berlin, we have updated the TCM-T=
F charter and the two drafts. We have tried to solve all the problems raise=
d during the session.

Our plan is to request a new BoF in London next March, so we would like to =
know your opinion about these two questions:


1.  Is the new, reduced scope of TCM-TF suitable to form a working group?


2. We would like to kindly ask people who think that a TCM-TF Working group=
 should be formed, to come forward and send an e-mail to the tsv-area@ietf.=
org<mailto:tsv-area@ietf.org>  mailing list stating it.


This feedback will allow us to get a better idea of the convenience of a Bo=
F.

The new charter is here: http://www.ietf.org/mail-archive/web/tcmtf/current=
/msg00465.html
This is the old one (presented in Berlin): http://www.ietf.org/mail-archive=
/web/tcmtf/current/msg00368.html

In these links you can see the differences between the new versions of the =
drafts and the old ones:
http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&url2=
=3Ddraft-saldana-tsvwg-tcmtf-05.txt
http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.txt=
&url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt


The main improvements are:

- TCP optimization has been removed
- The classification of the scenarios has been refined and improved. Some o=
f them have been removed
- A section about energy consumption has been added to the main draft
- A reference to the potential problem of the MTU and packet loss has been =
added
- The problem of the added delays is studied in detail in the second draft

- The improvements of the charter are summarized here: http://www.ietf.org/=
mail-archive/web/tcmtf/current/msg00466.html


Best regards,

Jose


--_000_8D3D17ACE214DC429325B2B98F3AE712026EF2FF8FMX15Acorpemcc_
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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:70.85pt 85.05pt 70.85pt 85.05pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>A second BoF has the=
 explicit goal of forming a WG, as a third BoF<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";col=
or:black'>is not permitted.&nbsp; In that regard, the new charter seems lon=
g and<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10=
.0pt;font-family:"Courier New";color:black'>somewhat lacking in focus.&nbsp=
; Two key things I look for in a proposed<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:bl=
ack'>charter are what problem (or problems) the proposed WG is looking to<o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fo=
nt-family:"Courier New";color:black'>solve and an initial approach to the p=
roblem or problems.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:=
p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fami=
ly:"Courier New";color:black'>In the new draft charter, the problem stateme=
nt appears to be in<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New";color:black'>paragraph 4 wit=
h paragraph 1 providing important background.&nbsp; The<o:p></o:p></span></=
p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier=
 New";color:black'>focus of the work appears to be on extending TCRTP (RFC =
4170) to<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:10.0pt;font-family:"Courier New";color:black'>UDP and to include new compr=
ession protocols.&nbsp; In contrast, I have<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:black'>a hard time discerning the initial approach from the new draft cha=
rter.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10=
.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New"=
;color:black'>In light of this, there are a few things that I wish the new<=
o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;f=
ont-family:"Courier New";color:black'>draft charter had definitive proposal=
s for:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:1=
0.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New=
";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Whether to replace RFC 417=
0 vs. write a new RFC (could be<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UDP-only or U=
DP + RTP/UDP) as a complement to RFC 4170.<o:p></o:p></span></p><p class=3D=
MsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:b=
lack'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Whether to use ECRTP, ROHCv2 (RFC 5=
225) and/or IPHC (RFC 2507 ?).<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Non-use of ECR=
TP would be a major change to 4170, and I<o:p></o:p></span></p><p class=3DM=
soNormal style=3D'margin-left:.5in;text-indent:.5in'><span style=3D'font-si=
ze:10.0pt;font-family:"Courier New";color:black'>wonder about IPHC, as oppo=
sed to the ROHCv2 profiles.<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; c) Analogies to b) for the Mux and Tunnel layers of t=
he stack.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>Overall, it looks like the first task of the WG is to sel=
ect the protocol<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>stack to standardize=
 - I have misgivings about that, and would prefer to<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier Ne=
w";color:black'>see a concrete proposal in a crisp charter that ran along t=
he following<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:10.0pt;font-family:"Courier New";color:black'>lines, naming the protoc=
ols to be used:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Co=
urier New";color:black'>1) RFC 4170 does X, and needs the following changes=
/additions: X, Y, Z.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New";color:black'>2) The WG will =
replace RFC 4170 with a new RFC that contains: A, B, C.<o:p></o:p></span></=
p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier=
 New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span s=
tyle=3D'font-size:10.0pt;font-family:"Courier New";color:black'>A specific =
proposal or proposals for the protocol stack or stacks<o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>would also narrow the scope of item 9 in the charter on t=
he negotiation<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:10.0pt;font-family:"Courier New";color:black'>mechanism.&nbsp; I als=
o don&#8217;t see a goal/milestone listed for an extension to<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"C=
ourier New";color:black'>or replacement for RFC 4170.<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:10.0pt;font-family:"Courier New";color:black'>I&#8217;d pre=
fer to see a much shorter more focused draft charter.&nbsp; There&#8217;s a=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;=
font-family:"Courier New";color:black'>bunch of background material that do=
es not seem crucial to the charter,<o:p></o:p></span></p><p class=3DMsoNorm=
al><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>s=
tarting w/paragraphs 2 and 3.<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&n=
bsp;</o:p></span></p><div><div><p class=3DMsoNormal><span style=3D'font-siz=
e:10.0pt;font-family:"Courier New";color:black'>Thanks,<br>--David</span><s=
pan style=3D'font-family:"Courier New";color:black'><o:p></o:p></span></p><=
/div></div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family=
:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><div style=3D'borde=
r:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div st=
yle=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in=
'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Taho=
ma","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-fami=
ly:"Tahoma","sans-serif"'> tsv-area [mailto:tsv-area-bounces@ietf.org] <b>O=
n Behalf Of </b>Jose Saldana<br><b>Sent:</b> Friday, December 20, 2013 4:26=
 AM<br><b>To:</b> tcmtf@ietf.org; tsv-area@ietf.org<br><b>Cc:</b> Martin St=
iemerling<br><b>Subject:</b> TCMTF-Feedback about a possible BoF in London<=
o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p>=
<p class=3DMsoNormal><span lang=3DES>Hi all,<o:p></o:p></span></p><p class=
=3DMsoNormal><span lang=3DES><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorm=
al>After the feedback received in the BoF in Berlin, we have updated the TC=
M-TF charter and the two drafts. We have tried to solve all the problems ra=
ised during the session.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:=
p></p><p class=3DMsoNormal>Our plan is to request a new BoF in London next =
March, so we would like to know your opinion about these two questions:<o:p=
></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p><p class=3DMsoNormal>1. &nbsp;Is the new, reduced scope=
 of TCM-TF suitable to form a working group?<o:p></o:p></p><p class=3DMsoNo=
rmal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p clas=
s=3DMsoNormal>2. We would like to kindly ask people who think that a TCM-TF=
 Working group should be formed, to come forward and send an e-mail to the =
<a href=3D"mailto:tsv-area@ietf.org">tsv-area@ietf.org</a> &nbsp;mailing li=
st stating it.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>This feedback wi=
ll allow us to get a better idea of the convenience of a BoF.<o:p></o:p></p=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The new cha=
rter is here: <a href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current=
/msg00465.html">http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465=
.html</a><o:p></o:p></p><p class=3DMsoNormal>This is the old one (presented=
 in Berlin): <a href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/=
msg00368.html">http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.=
html</a><o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>In these links you can see the differences between the new ver=
sions of the drafts and the old ones:<o:p></o:p></p><p class=3DMsoNormal><s=
pan lang=3DES><a href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana=
-tsvwg-tcmtf-06.txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt"><span lang=
=3DEN-US>http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.=
txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt</span></a></span><o:p></o:p=
></p><p class=3DMsoNormal><a href=3D"http://tools.ietf.org/rfcdiff?url1=3Dd=
raft-suznjevic-tsvwg-mtd-tcmtf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-=
tcmtf-01.txt">http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mt=
d-tcmtf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt</a><o:p></=
o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p><p class=3DMsoNormal>The main improvements are:<o:p></o:p>=
</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>- TCP op=
timization has been removed<o:p></o:p></p><p class=3DMsoNormal>- The classi=
fication of the scenarios has been refined and improved. Some of them have =
been removed<o:p></o:p></p><p class=3DMsoNormal>- A section about energy co=
nsumption has been added to the main draft<o:p></o:p></p><p class=3DMsoNorm=
al>- A reference to the potential problem of the MTU and packet loss has be=
en added<o:p></o:p></p><p class=3DMsoNormal>- The problem of the added dela=
ys is studied in detail in the second draft<o:p></o:p></p><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>- The improvements of the cha=
rter are summarized here: <a href=3D"http://www.ietf.org/mail-archive/web/t=
cmtf/current/msg00466.html">http://www.ietf.org/mail-archive/web/tcmtf/curr=
ent/msg00466.html</a><o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Best rega=
rds,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMso=
Normal>Jose<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><=
/div></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE712026EF2FF8FMX15Acorpemcc_--

From jsaldana@unizar.es  Sun Jan  5 10:47:50 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D3821AF432; Sun,  5 Jan 2014 10:47:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.839
X-Spam-Level: 
X-Spam-Status: No, score=-2.839 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xYt7BGvIti5T; Sun,  5 Jan 2014 10:47:45 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 8F16A1AF431; Sun,  5 Jan 2014 10:47:44 -0800 (PST)
Received: from jsaldanapc (126.Red-88-4-241.dynamicIP.rima-tde.net [88.4.241.126]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id s05IlL8a014472; Sun, 5 Jan 2014 19:47:26 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Black, David'" <david.black@emc.com>, <tcmtf@ietf.org>, <tsv-area@ietf.org>
References: <00c401cefd65$6e8ef570$4bace050$@unizar.es> <8D3D17ACE214DC429325B2B98F3AE712026EF2FF8F@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712026EF2FF8F@MX15A.corp.emc.com>
Date: Sun, 5 Jan 2014 19:47:24 +0100
Message-ID: <005101cf0a46$95ca10f0$c15e32d0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0052_01CF0A4E.F7935AF0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKm4iuy1T4jUNWcvPCI8e0mPkHF7QHB3wddmLi5h+A=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: 'Martin Stiemerling' <mls.ietf@googlemail.com>
Subject: Re: [tcmtf] TCMTF-Feedback about a possible BoF in London
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf/>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Jan 2014 18:47:50 -0000

This is a multipart message in MIME format.

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

David,

=20

Thanks for your valuable comments!

=20

I will improve the charter according to your suggestions and release a =
new
version.

=20

Thanks again,

=20

Jose

=20

De: Black, David [mailto:david.black@emc.com]=20
Enviado el: s=E1bado, 04 de enero de 2014 4:05
Para: Jose Saldana; tcmtf@ietf.org; tsv-area@ietf.org
CC: Martin Stiemerling; Black, David
Asunto: RE: TCMTF-Feedback about a possible BoF in London

=20

A second BoF has the explicit goal of forming a WG, as a third BoF

is not permitted.  In that regard, the new charter seems long and

somewhat lacking in focus.  Two key things I look for in a proposed

charter are what problem (or problems) the proposed WG is looking to

solve and an initial approach to the problem or problems.

=20

In the new draft charter, the problem statement appears to be in

paragraph 4 with paragraph 1 providing important background.  The

focus of the work appears to be on extending TCRTP (RFC 4170) to

UDP and to include new compression protocols.  In contrast, I have

a hard time discerning the initial approach from the new draft charter.

=20

In light of this, there are a few things that I wish the new

draft charter had definitive proposals for:

=20

      a) Whether to replace RFC 4170 vs. write a new RFC (could be

            UDP-only or UDP + RTP/UDP) as a complement to RFC 4170.

      b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC (RFC 2507 =
?).

            Non-use of ECRTP would be a major change to 4170, and I

wonder about IPHC, as opposed to the ROHCv2 profiles.

      c) Analogies to b) for the Mux and Tunnel layers of the stack.

=20

Overall, it looks like the first task of the WG is to select the =
protocol

stack to standardize - I have misgivings about that, and would prefer to

see a concrete proposal in a crisp charter that ran along the following

lines, naming the protocols to be used:

=20

1) RFC 4170 does X, and needs the following changes/additions: X, Y, Z.

2) The WG will replace RFC 4170 with a new RFC that contains: A, B, C.

=20

A specific proposal or proposals for the protocol stack or stacks

would also narrow the scope of item 9 in the charter on the negotiation

mechanism.  I also don=92t see a goal/milestone listed for an extension =
to

or replacement for RFC 4170.

=20

I=92d prefer to see a much shorter more focused draft charter.  =
There=92s a

bunch of background material that does not seem crucial to the charter,

starting w/paragraphs 2 and 3.

=20

Thanks,
--David

=20

From: tsv-area [mailto:tsv-area-bounces@ietf.org] On Behalf Of Jose =
Saldana
Sent: Friday, December 20, 2013 4:26 AM
To: tcmtf@ietf.org; tsv-area@ietf.org
Cc: Martin Stiemerling
Subject: TCMTF-Feedback about a possible BoF in London

=20

Hi all,

=20

After the feedback received in the BoF in Berlin, we have updated the =
TCM-TF
charter and the two drafts. We have tried to solve all the problems =
raised
during the session.

=20

Our plan is to request a new BoF in London next March, so we would like =
to
know your opinion about these two questions:

=20

=20

1.  Is the new, reduced scope of TCM-TF suitable to form a working =
group?

=20

=20

2. We would like to kindly ask people who think that a TCM-TF Working =
group
should be formed, to come forward and send an e-mail to the
tsv-area@ietf.org  mailing list stating it.

=20

=20

This feedback will allow us to get a better idea of the convenience of a
BoF.

=20

The new charter is here:
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html

This is the old one (presented in Berlin):
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.html

=20

In these links you can see the differences between the new versions of =
the
drafts and the old ones:

=20
<http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&ur=
l2=3Ddr
aft-saldana-tsvwg-tcmtf-05.txt>
http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&url=
2=3Ddra
ft-saldana-tsvwg-tcmtf-05.txt

http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.t=
xt
<http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.=
txt&u
rl2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt>
&url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt

=20

=20

The main improvements are:

=20

- TCP optimization has been removed

- The classification of the scenarios has been refined and improved. =
Some of
them have been removed

- A section about energy consumption has been added to the main draft

- A reference to the potential problem of the MTU and packet loss has =
been
added

- The problem of the added delays is studied in detail in the second =
draft

=20

- The improvements of the charter are summarized here:
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.html

=20

=20

Best regards,

=20

Jose

=20


------=_NextPart_000_0052_01CF0A4E.F7935AF0
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";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texto de globo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EstiloCorreo17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo18
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
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.EstiloCorreo21
	{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'color:#1F497D'>David,<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'>Thanks for =
your valuable comments!<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 will =
improve the charter according to your suggestions and release a new =
version.<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,<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"'> Black, =
David [mailto:david.black@emc.com] <br><b>Enviado el:</b> s=E1bado, 04 =
de enero de 2014 4:05<br><b>Para:</b> Jose Saldana; tcmtf@ietf.org; =
tsv-area@ietf.org<br><b>CC:</b> Martin Stiemerling; Black, =
David<br><b>Asunto:</b> RE: TCMTF-Feedback about a possible BoF in =
London<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'font-size:10.0pt;font-family:"Courier =
New";color:black'>A second BoF has the explicit goal of forming a WG, as =
a third BoF<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'>is not =
permitted.&nbsp; In that regard, the new charter seems long =
and<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'>somewhat lacking in focus.&nbsp; Two key things I look =
for in a proposed<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'>charter are what problem (or problems) the proposed WG =
is looking to<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'>solve and an initial approach to the problem or =
problems.<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>In the new draft charter, the problem statement =
appears to be in<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'>paragraph 4 with paragraph 1 providing important =
background.&nbsp; The<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'>focus of the work appears to be on extending TCRTP =
(RFC 4170) to<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'>UDP and to include new compression protocols.&nbsp; In =
contrast, I have<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 hard time discerning the initial approach from the =
new draft charter.<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>In light of this, there are a few things that I wish =
the new<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'>draft =
charter had definitive proposals for:<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Whether to replace =
RFC 4170 vs. write a new RFC (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";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; UDP-only or UDP + RTP/UDP) as a complement to RFC =
4170.<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;&nbsp;&nbsp;&nbsp;&nbsp; b) Whether to use =
ECRTP, ROHCv2 (RFC 5225) and/or IPHC (RFC 2507 =
?).<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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; Non-use of ECRTP would be a major change to 4170, and =
I<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:36.0pt;text-indent:36.0pt'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>wonder =
about IPHC, as opposed to the ROHCv2 profiles.<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;&nbsp;&nbsp;&nbsp;&nbsp; c) Analogies to b) for =
the Mux and Tunnel layers of the stack.<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>Overall, it looks like the first task of the WG is to =
select the protocol<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'>stack to standardize - I have misgivings about that, =
and would prefer to<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'>see a concrete proposal in a crisp charter that ran =
along the following<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'>lines, naming the protocols to be =
used:<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>1) RFC 4170 does X, and needs the following =
changes/additions: X, Y, Z.<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) The =
WG will replace RFC 4170 with a new RFC that contains: A, B, =
C.<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>A specific proposal or proposals for the protocol =
stack or stacks<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'>would also narrow the scope of item 9 in the charter =
on the negotiation<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'>mechanism.&nbsp; I also don&#8217;t see a =
goal/milestone listed for an extension to<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'>or =
replacement for RFC 4170.<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>I&#8217;d prefer to see a much shorter more focused =
draft charter.&nbsp; There&#8217;s a<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'>bunch =
of background material that does not seem crucial to the =
charter,<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'>starting w/paragraphs 2 and 3.<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'><o:p>&nbsp;</o:p></span></p><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>Thanks,<br>--David</span><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'><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"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> tsv-area =
[<a =
href=3D"mailto:tsv-area-bounces@ietf.org">mailto:tsv-area-bounces@ietf.or=
g</a>] <b>On Behalf Of </b>Jose Saldana<br><b>Sent:</b> Friday, December =
20, 2013 4:26 AM<br><b>To:</b> <a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>; <a =
href=3D"mailto:tsv-area@ietf.org">tsv-area@ietf.org</a><br><b>Cc:</b> =
Martin Stiemerling<br><b>Subject:</b> TCMTF-Feedback about a possible =
BoF in London<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>Hi all,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>After the feedback received in the BoF in Berlin, we have =
updated the TCM-TF charter and the two drafts. We have tried to solve =
all the problems raised during the session.<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>Our plan is to request a new BoF in =
London next March, so we would like to know your opinion about these two =
questions:<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>1. &nbsp;Is the new, reduced scope of TCM-TF suitable to =
form a 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><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>2. We would like to kindly ask people who think that a =
TCM-TF Working group should be formed, to come forward and send an =
e-mail to the <a href=3D"mailto:tsv-area@ietf.org">tsv-area@ietf.org</a> =
&nbsp;mailing list stating it.<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>This feedback will allow us to get =
a better idea of the convenience of a BoF.<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 new charter is here: <a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html"=
>http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html</a><o:p=
></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>This is the =
old one (presented in Berlin): <a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.html"=
>http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.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>In these links you can see the differences between the new =
versions of the drafts and the old ones:<o:p></o:p></span></p><p =
class=3DMsoNormal><a =
href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06=
.txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt"><span =
lang=3DEN-US>http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcm=
tf-06.txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt</span></a><span =
lang=3DEN-US><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><a =
href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tc=
mtf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt">http://tool=
s.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.txt&amp;url2=
=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt</a><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>The main improvements =
are:<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>- TCP optimization has been removed<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- The classification of the =
scenarios has been refined and improved. Some of them have been =
removed<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>- A =
section about energy consumption has been added to the main =
draft<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>- A =
reference to the potential problem of the MTU and packet loss has been =
added<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>- The =
problem of the added delays is studied in detail in the second =
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>- The improvements of the charter are summarized here: <a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.html"=
>http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.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><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></div></div></body></html>
------=_NextPart_000_0052_01CF0A4E.F7935AF0--


From ggx@gigix.net  Mon Jan  6 02:41:47 2014
Return-Path: <ggx@gigix.net>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A3D81ADFB1 for <tcmtf@ietfa.amsl.com>; Mon,  6 Jan 2014 02:41:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YygV4i7n9lYX for <tcmtf@ietfa.amsl.com>; Mon,  6 Jan 2014 02:41:45 -0800 (PST)
Received: from mail-wg0-f48.google.com (mail-wg0-f48.google.com [74.125.82.48]) by ietfa.amsl.com (Postfix) with ESMTP id 07A571ADF63 for <tcmtf@ietf.org>; Mon,  6 Jan 2014 02:41:44 -0800 (PST)
Received: by mail-wg0-f48.google.com with SMTP id z12so15356125wgg.3 for <tcmtf@ietf.org>; Mon, 06 Jan 2014 02:41:36 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=HO7gDKepFh5nA6RxluoO0U+q9p1OP7DzlrYI3y6XKgY=; b=Ula26BI3sijuR4jKS6VOWdG6KAL1MlDa2F2Nvz/ODmupUH4DpT4uyTMQ0z6F/I4h50 YnoZ8ohoiIXVNSqTZWIOcn8WyKLUW7daZU3TY8/zAHYiak1JJ7RJ+Os++QWhbAAnPn/C cN540pQyxv7vpptiJWk3Z4UFYJbPlyCreC68kwGROvPsgOiR/v8HjW9p39F6tPReIGEd HSqTKDsRiqZlVf/IcSoh/+059Kxv2hZOwvpbWnj1LCl5WG44oLL/Tvcc7yfNG7gF3jd9 bsTv/16SoLf0o2x2+IfZ2H8fCy9VPg8FiFTLNJ3caltoeSGEcF5dbNgo3y4ig2az6e3J OiPg==
X-Gm-Message-State: ALoCoQnUU++QgwX+q+9dmeInQRK48eApdGWNLKnjqiIC0yss4/bjBQyamcaizZZoBdo7JhL6UO9j
X-Received: by 10.180.77.72 with SMTP id q8mr11997421wiw.12.1389004896052; Mon, 06 Jan 2014 02:41:36 -0800 (PST)
Received: from dhcp164-05.enst.fr (dhcp164-05.enst.fr. [137.194.165.5]) by mx.google.com with ESMTPSA id z2sm17207115wiy.11.2014.01.06.02.41.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 Jan 2014 02:41:34 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_AB370AEC-61EC-4AB9-ACA3-AF09FF7D0D6B"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712026EF2FF8F@MX15A.corp.emc.com>
Date: Mon, 6 Jan 2014 11:41:32 +0100
Message-Id: <77C9FEE1-9EB2-4BE6-8D57-FF04F472EA57@gigix.net>
References: <00c401cefd65$6e8ef570$4bace050$@unizar.es> <8D3D17ACE214DC429325B2B98F3AE712026EF2FF8F@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1827)
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, Martin Stiemerling <mls.ietf@googlemail.com>, "tsv-area@ietf.org" <tsv-area@ietf.org>, Jose Saldana <jsaldana@unizar.es>
Subject: Re: [tcmtf] TCMTF-Feedback about a possible BoF in London
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Jan 2014 10:41:47 -0000

--Apple-Mail=_AB370AEC-61EC-4AB9-ACA3-AF09FF7D0D6B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi All,

I agree with David that the charter is a bit prolix.

IMHO it can be shortened in the following way:

- Merge abd reduce paragraphs 2 and 3. I think that the main message =
that the new paragraph should deliver is =93RFC4170 does not cover new =
emerging scenarios=94, which will be completed by the current paragraph =
4.

- Shorten paragraph 5. The charter should (IMHO) offer a list of sample =
scenarios where bandwidth saving is desirable but the analysis of such =
scenarios has to be done elsewhere. In the current form there is too =
much details.=20

- Paragraph 6: I am not sure if we really need to keep such precise =
figures in a charter. If people prefer to keep the text it should appear =
earlier on in the charter (in the new second paragraph ???) to provide =
motivation on using TCM solutions.=20

Having said that, I support the formation of the WG.

ciao

Luigi


On 4 Jan. 2014, at 04:04 , Black, David <david.black@emc.com> wrote:

> A second BoF has the explicit goal of forming a WG, as a third BoF
> is not permitted.  In that regard, the new charter seems long and
> somewhat lacking in focus.  Two key things I look for in a proposed
> charter are what problem (or problems) the proposed WG is looking to
> solve and an initial approach to the problem or problems.
> =20
> In the new draft charter, the problem statement appears to be in
> paragraph 4 with paragraph 1 providing important background.  The
> focus of the work appears to be on extending TCRTP (RFC 4170) to
> UDP and to include new compression protocols.  In contrast, I have
> a hard time discerning the initial approach from the new draft =
charter.
> =20
> In light of this, there are a few things that I wish the new
> draft charter had definitive proposals for:
> =20
>       a) Whether to replace RFC 4170 vs. write a new RFC (could be
>             UDP-only or UDP + RTP/UDP) as a complement to RFC 4170.
>       b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC (RFC 2507 =
?).
>             Non-use of ECRTP would be a major change to 4170, and I
> wonder about IPHC, as opposed to the ROHCv2 profiles.
>       c) Analogies to b) for the Mux and Tunnel layers of the stack.
> =20
> Overall, it looks like the first task of the WG is to select the =
protocol
> stack to standardize - I have misgivings about that, and would prefer =
to
> see a concrete proposal in a crisp charter that ran along the =
following
> lines, naming the protocols to be used:
> =20
> 1) RFC 4170 does X, and needs the following changes/additions: X, Y, =
Z.
> 2) The WG will replace RFC 4170 with a new RFC that contains: A, B, C.
> =20
> A specific proposal or proposals for the protocol stack or stacks
> would also narrow the scope of item 9 in the charter on the =
negotiation
> mechanism.  I also don=92t see a goal/milestone listed for an =
extension to
> or replacement for RFC 4170.
> =20
> I=92d prefer to see a much shorter more focused draft charter.  =
There=92s a
> bunch of background material that does not seem crucial to the =
charter,
> starting w/paragraphs 2 and 3.
> =20
> Thanks,
> --David
> =20
> From: tsv-area [mailto:tsv-area-bounces@ietf.org] On Behalf Of Jose =
Saldana
> Sent: Friday, December 20, 2013 4:26 AM
> To: tcmtf@ietf.org; tsv-area@ietf.org
> Cc: Martin Stiemerling
> Subject: TCMTF-Feedback about a possible BoF in London
> =20
> Hi all,
> =20
> After the feedback received in the BoF in Berlin, we have updated the =
TCM-TF charter and the two drafts. We have tried to solve all the =
problems raised during the session.
> =20
> Our plan is to request a new BoF in London next March, so we would =
like to know your opinion about these two questions:
> =20
> =20
> 1.  Is the new, reduced scope of TCM-TF suitable to form a working =
group?
> =20
> =20
> 2. We would like to kindly ask people who think that a TCM-TF Working =
group should be formed, to come forward and send an e-mail to the =
tsv-area@ietf.org  mailing list stating it.
> =20
> =20
> This feedback will allow us to get a better idea of the convenience of =
a BoF.
> =20
> The new charter is here: =
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html
> This is the old one (presented in Berlin): =
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.html
> =20
> In these links you can see the differences between the new versions of =
the drafts and the old ones:
> =
http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&url2=
=3Ddraft-saldana-tsvwg-tcmtf-05.txt
> =
http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.tx=
t&url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt
> =20
> =20
> The main improvements are:
> =20
> - TCP optimization has been removed
> - The classification of the scenarios has been refined and improved. =
Some of them have been removed
> - A section about energy consumption has been added to the main draft
> - A reference to the potential problem of the MTU and packet loss has =
been added
> - The problem of the added delays is studied in detail in the second =
draft
> =20
> - The improvements of the charter are summarized here: =
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.html
> =20
> =20
> Best regards,
> =20
> Jose
> =20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


--Apple-Mail=_AB370AEC-61EC-4AB9-ACA3-AF09FF7D0D6B
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"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi =
All,<div><br></div><div>I agree with David that the charter is a bit =
prolix.</div><div><br></div><div>IMHO it can be shortened in the =
following way:</div><div><br></div><div>- Merge abd reduce paragraphs 2 =
and 3. I think that the main message that the new paragraph should =
deliver is =93RFC4170 does not cover new emerging scenarios=94, which =
will be completed by the current paragraph 4.</div><div><br></div><div>- =
Shorten paragraph 5. The charter should (IMHO) offer a list of sample =
scenarios where bandwidth saving is desirable but the analysis of such =
scenarios has to be done elsewhere. In the current form there is too =
much details.&nbsp;</div><div><br></div><div>- Paragraph 6: I am not =
sure if we really need to keep such precise figures in a charter. If =
people prefer to keep the text it should appear earlier on in the =
charter (in the new second paragraph ???) to provide motivation on using =
TCM solutions.&nbsp;</div><div><br></div><div>Having said that, I =
support the formation of the =
WG.</div><div><br></div><div>ciao</div><div><br></div><div>Luigi</div><div=
><br></div><div><br><div><div>On 4 Jan. 2014, at 04:04 , Black, David =
&lt;<a href=3D"mailto:david.black@emc.com">david.black@emc.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;"><div class=3D"WordSection1" =
style=3D"page: WordSection1;"><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">A second BoF has =
the explicit goal of forming a WG, as a third =
BoF<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">is not =
permitted.&nbsp; In that regard, the new charter seems long =
and<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">somewhat lacking =
in focus.&nbsp; Two key things I look for in a =
proposed<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">charter are what =
problem (or problems) the proposed WG is looking =
to<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">solve and an =
initial approach to the problem or problems.<o:p></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><span style=3D"font-size: 10pt; font-family: =
'Courier New';">&nbsp;</span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">In the new draft =
charter, the problem statement appears to be =
in<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">paragraph 4 with =
paragraph 1 providing important background.&nbsp; =
The<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">focus of the work =
appears to be on extending TCRTP (RFC 4170) =
to<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">UDP and to =
include new compression protocols.&nbsp; In contrast, I =
have<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">a hard time =
discerning the initial approach from the new draft =
charter.<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier =
New';">&nbsp;</span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">In light of this, =
there are a few things that I wish the new<o:p></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><span style=3D"font-size: 10pt; font-family: =
'Courier New';">draft charter had definitive proposals =
for:<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier =
New';">&nbsp;</span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier =
New';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Whether to replace RFC 4170 vs. =
write a new RFC (could be<o:p></o:p></span></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 10pt; font-family: 'Courier =
New';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
UDP-only or UDP + RTP/UDP) as a complement to RFC =
4170.<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier =
New';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Whether to use ECRTP, ROHCv2 =
(RFC 5225) and/or IPHC (RFC 2507 ?).<o:p></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><span style=3D"font-size: 10pt; font-family: =
'Courier =
New';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Non-use of ECRTP would be a major change to 4170, and =
I<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt 0.5in; =
font-size: 11pt; font-family: Calibri, sans-serif; text-indent: =
0.5in;"><span style=3D"font-size: 10pt; font-family: 'Courier =
New';">wonder about IPHC, as opposed to the ROHCv2 =
profiles.<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier =
New';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c) Analogies to b) for the Mux and =
Tunnel layers of the stack.<o:p></o:p></span></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><span style=3D"font-size: 10pt; font-family: 'Courier =
New';">&nbsp;</span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">Overall, it looks =
like the first task of the WG is to select the =
protocol<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">stack to =
standardize - I have misgivings about that, and would prefer =
to<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">see a concrete =
proposal in a crisp charter that ran along the =
following<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">lines, naming the =
protocols to be used:<o:p></o:p></span></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier =
New';">&nbsp;</span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">1) RFC 4170 does =
X, and needs the following changes/additions: X, Y, =
Z.<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">2) The WG will =
replace RFC 4170 with a new RFC that contains: A, B, =
C.<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier =
New';">&nbsp;</span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">A specific =
proposal or proposals for the protocol stack or =
stacks<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">would also narrow =
the scope of item 9 in the charter on the =
negotiation<o:p></o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">mechanism.&nbsp; =
I also don=92t see a goal/milestone listed for an extension =
to<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">or replacement =
for RFC 4170.<o:p></o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier =
New';">&nbsp;</span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">I=92d prefer to =
see a much shorter more focused draft charter.&nbsp; There=92s =
a<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">bunch of =
background material that does not seem crucial to the =
charter,<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier New';">starting =
w/paragraphs 2 and 3.<o:p></o:p></span></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier =
New';">&nbsp;</span></div><div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier =
New';">Thanks,<br>--David</span><span style=3D"font-family: 'Courier =
New';"><o:p></o:p></span></div></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
style=3D"font-size: 10pt; font-family: 'Courier =
New';">&nbsp;</span></div><div style=3D"border-style: none none none =
solid; border-left-color: blue; border-left-width: 1.5pt; padding: 0in =
0in 0in 4pt;"><div><div style=3D"border-style: solid none none; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: =
3pt 0in 0in;"><div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif;">From:</span></b><span =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;"><span =
class=3D"Apple-converted-space">&nbsp;</span>tsv-area [<a =
href=3D"mailto:tsv-area-bounces@ietf.org">mailto:tsv-area-bounces@ietf.org=
</a>]<span class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Jose =
Saldana<br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Friday, December 20, 2013 =
4:26 AM<br><b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span><a=
 href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>; <a =
href=3D"mailto:tsv-area@ietf.org">tsv-area@ietf.org</a><br><b>Cc:</b><span=
 class=3D"Apple-converted-space">&nbsp;</span>Martin =
Stiemerling<br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>TCMTF-Feedback about a =
possible BoF in London<o:p></o:p></span></div></div></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
lang=3D"ES">Hi all,<o:p></o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
lang=3D"ES">&nbsp;</span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;">After the feedback =
received in the BoF in Berlin, we have updated the TCM-TF charter and =
the two drafts. We have tried to solve all the problems raised during =
the session.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Our plan =
is to request a new BoF in London next March, so we would like to know =
your opinion about these two questions:<o:p></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">1. =
&nbsp;Is the new, reduced scope of TCM-TF suitable to form a working =
group?<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">2. We =
would like to kindly ask people who think that a TCM-TF Working group =
should be formed, to come forward and send an e-mail to the<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:tsv-area@ietf.org" style=3D"color: purple; =
text-decoration: underline;">tsv-area@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>&nbsp;mailing list stating =
it.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif;">&nbsp;<o:p></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">This =
feedback will allow us to get a better idea of the convenience of a =
BoF.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif;"><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;">The new charter is here:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html" =
style=3D"color: purple; text-decoration: =
underline;">http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.ht=
ml</a><o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;">This is the old one =
(presented in Berlin):<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.html" =
style=3D"color: purple; text-decoration: =
underline;">http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.ht=
ml</a><o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">In these =
links you can see the differences between the new versions of the drafts =
and the old ones:<o:p></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span =
lang=3D"ES"><a =
href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.=
txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt" style=3D"color: purple; =
text-decoration: underline;"><span =
lang=3D"EN-US">http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tc=
mtf-06.txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt</span></a></span><o=
:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><a =
href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcm=
tf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt" =
style=3D"color: purple; text-decoration: =
underline;">http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd=
-tcmtf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt</a><o:p></=
o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;"><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">The =
main improvements are:<o:p></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">- TCP =
optimization has been removed<o:p></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">- The =
classification of the scenarios has been refined and improved. Some of =
them have been removed<o:p></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">- A =
section about energy consumption has been added to the main =
draft<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif;">- A reference to the potential =
problem of the MTU and packet loss has been added<o:p></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;">- The problem of the added delays is studied in =
detail in the second draft<o:p></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">- The =
improvements of the charter are summarized here:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.html" =
style=3D"color: purple; text-decoration: =
underline;">http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.ht=
ml</a><o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Best =
regards,<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;">Jose<o:p></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif;"><o:p>&nbsp;</o:p></div></div></div>__________________________=
_____________________<br>tcmtf mailing list<br><a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/tcmtf</div></blockquote></div><br></div></body></html>=

--Apple-Mail=_AB370AEC-61EC-4AB9-ACA3-AF09FF7D0D6B--

From jsaldana@unizar.es  Wed Jan  8 03:22:50 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8E91AE2A1; Wed,  8 Jan 2014 03:22:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.624
X-Spam-Level: 
X-Spam-Status: No, score=-2.624 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=0.001, ONE_TIME=0.714, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xRDTlMV0sE7Z; Wed,  8 Jan 2014 03:22:46 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id A2F7A1AE18B; Wed,  8 Jan 2014 03:22:45 -0800 (PST)
Received: from jsaldanapc ([195.76.232.154]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id s08BMPhi019651; Wed, 8 Jan 2014 12:22:27 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>, <tsv-area@ietf.org>
Date: Wed, 8 Jan 2014 12:22:25 +0100
Message-ID: <001b01cf0c63$ea240b00$be6c2100$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01CF0C6C.4BECDFD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8MUTJEFfBaeFLER7ezjsW9Se+pLw==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Martin Stiemerling <mls.ietf@googlemail.com>
Subject: [tcmtf] Next version (v10) of TCM-TF charter draft
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 08 Jan 2014 11:22:51 -0000

This is a multipart message in MIME format.

------=_NextPart_000_001C_01CF0C6C.4BECDFD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Tunneling Compressed Multiplexed Traffic Flows (TCM-TF) charter draft v10

 

Description of Working Group

 

1. RFC4170 (TCRTP) defines a method for grouping packets when a number of
UDP/RTP VoIP flows share a common path, considering three different layers:
ECRTP header compression; PPPMux multiplexing; L2TPv3 tunneling. TCRTP
optimizes the traffic, increasing the bandwidth efficiency of VoIP and
reduces the amount of packets per second at the same time.

 

2. However, in the last years, emerging real-time services which use bare
UDP instead of UDP/RTP have become popular. Due to the need of
interactivity, many of these services use small packets (some tens of
bytes). Some other services also send small packets, but they are not
delay-sensitive (e.g., instant messaging, m2m packets in sensor networks).
In addition, a significant effort has been devoted to the deployment of new
header compression methods with improved robustness (ROHC).

 

3. So there is a need of replacing RFC4170 with an extended solution able to
optimize these new flows, also using improved compression methods. The same
structure of three layers will be considered:

 

* Header compression: different protocols can be used: no compression,
ECRTP, IPHC and ROHC.

* Multiplexing: PPPMux will be the option.

* Tunneling: the options in this layer are L2TP, GRE and MPLS.

 

4. New scenarios where bandwidth savings are desirable have been identified,
in addition to those considered in RFC4170. In these scenarios, there are
moments or places where network capacity gets scarce, so allocating more
bandwidth is a possible solution, but it implies a recurring cost. However,
the inclusion of a pair of boxes able to optimize the traffic when/where
required is a one-time investment. These scenarios can be classified into:

 

* Multidomain, the TCMT-TF tunnel goes all the way from one network edge to
another, and can therefore cross several domains.

* Single Domain, TCM-TF is only activated inside an ISP, from the edge to
border inside the network operator. 

* Private Solutions. TCM-TF is used to connect private networks
geographically apart (e.g. corporation headquarters and subsidiaries),
without the ISP being aware or having to manage those flows.

* Mixed Scenarios, any combination of the previous ones.

 

5. Since standard protocols are being used at each layer, the signaling
methods of those protocols will be used. Thus, 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 would
be obsoleted.

 

6. A first document (TCM-TF - reference model) will define the different
options which can be used at each layer. It will include a detailed
specification of the scenarios of interest. 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. The impact on other
protocols will also be studied.

 

7. Taking into account that different options will be considered, when a
pair of TCM-TF optimizers want to establish a session, they have first to
negotiate which concrete option would they use in each layer. This will
depend on the protocols that each extreme implements at each level, and in
the scenario. So another document (TCM-TF - negotiation protocol) will
include:

 

* a mechanism to setup/release a TCM-TF session between an ingress and an
egress-optimizer, also including:

* a negotiation mechanism to decide the options to use at each layer .

 

8. As a counterpart of the bandwidth saving, TCM-TF may add some delay and
jitter. This is not a problem for the services which are not sensitive to
delay. However, regarding delay-sensitive services, the Working Group will
also develop a document (TCM-TF - recommendations) with useful
recommendations in order to decide which packet flows can or can not be
multiplexed and how. The document will present a list of available traffic
classification methods which can be used for identification of the service
or application to which a particular flow belongs, as well as
recommendations of the maximum delay and jitter to be added depending of the
identified service or application. The eventual impact of multiplexing on
protocol dynamics (e.g. the loss of a multiplexed packet, MTU-related
issues) will also have to be addressed.

 

9. The working group may identify additional deliverables that are
necessary/useful, e.g., a mechanism for a TCM-ingress optimizer to discover
an egress optimizer, and vice versa. The working group would re-charter to
add them before working on them.

 

10. Interactions with other Working Groups can be expected, since TCM-TF
uses already defined protocols for compression, multiplexing and tunneling
(ROHC, PPPMux, MPLS, GRE, L2TP). 

 

Goals and Milestones

 

Specification of TCM-TF reference model and the scenarios of interest. This
would obsolete RFC4170.

 

Specification of TCM-TF negotiation protocol.

 

Specification of TCM-TF recommendations of using existing traffic
classification methods, maximum delay and jitter to add, depending on the
service.

 

 

Current version of Document (TCM-TF - reference model):

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

 

Current version of Document (TCM-TF - recommendations):

 <http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/>
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/


------=_NextPart_000_001C_01CF0C6C.4BECDFD0
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>Tunneling Compressed Multiplexed Traffic Flows (TCM-TF) =
charter draft v10<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>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. RFC4170 (TCRTP) defines a method =
for grouping packets when a number of UDP/RTP VoIP flows share a common =
path, considering three different layers: ECRTP header compression; =
PPPMux multiplexing; L2TPv3 tunneling. TCRTP optimizes the traffic, =
increasing the bandwidth efficiency of VoIP and reduces the amount of =
packets per second at the same time.<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. However, in the last years, =
emerging real-time services which use bare UDP instead of UDP/RTP have =
become popular. Due to the need of interactivity, many of these services =
use small packets (some tens of bytes). Some other services also send =
small packets, but they are not delay-sensitive (e.g., instant =
messaging, m2m packets in sensor networks). In addition, a significant =
effort has been devoted to the deployment of new header compression =
methods with improved robustness (ROHC).<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 there is a need of replacing =
RFC4170 with an extended solution able to optimize these new flows, also =
using improved compression methods. The same structure of three layers =
will 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>* Header compression: 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: PPPMux will be the =
option.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>* =
Tunneling: 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>4. New scenarios where bandwidth savings are desirable have =
been identified, in addition to those considered in RFC4170. In these =
scenarios, there are moments or places where network capacity gets =
scarce, so allocating more bandwidth is a possible solution, but it =
implies a recurring cost. However, the inclusion of a pair of boxes able =
to optimize the traffic when/where required is a one-time investment. =
These scenarios can be classified into:<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>* Multidomain, the TCMT-TF tunnel =
goes all the way from one network edge to another, and can therefore =
cross several domains.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>* Single Domain, TCM-TF is only activated inside an ISP, =
from the edge to border inside the network operator. =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>* Private =
Solutions. TCM-TF is used to connect private networks geographically =
apart (e.g. corporation headquarters and subsidiaries), without the ISP =
being aware or having to manage those flows.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>* Mixed Scenarios, any combination =
of the previous ones.<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. Since standard protocols are being used at each layer, =
the signaling methods of those protocols will be used. Thus, =
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 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>6. A first document (TCM-TF - reference model) will define =
the different options which can be used at each layer. It will include a =
detailed specification of the scenarios of interest. 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. The =
impact on other protocols will also be studied.<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. Taking into account that =
different options will be considered, when a pair of TCM-TF optimizers =
want to establish a session, they have first to negotiate which concrete =
option would they use in each layer. This will depend on the protocols =
that each extreme implements at each level, and in the scenario. So =
another document (TCM-TF - negotiation protocol) will =
include:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>* a mechanism to setup/release a TCM-TF session between an =
ingress and an egress-optimizer, also including:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>* a negotiation mechanism to decide =
the options to use at each layer .<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. As a counterpart of the =
bandwidth saving, TCM-TF may add some delay and jitter. This is not a =
problem for the services which are not sensitive to delay. However, =
regarding delay-sensitive services, the Working Group will also develop =
a document (TCM-TF - recommendations) with useful recommendations in =
order to decide which packet flows can or can not be multiplexed and =
how. The document will present a list of available traffic =
classification methods which can be used for identification of the =
service or application to which a particular flow belongs, as well as =
recommendations of the maximum delay and jitter to be added depending of =
the identified service or application. The eventual impact of =
multiplexing on protocol dynamics (e.g. the loss of a multiplexed =
packet, MTU-related issues) will also have to be =
addressed.<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. The working group may identify additional deliverables =
that are necessary/useful, e.g., a mechanism for a TCM-ingress optimizer =
to discover an egress optimizer, and vice versa. The working group would =
re-charter to add them before working on them.<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>10. Interactions with other Working =
Groups can be expected, since TCM-TF uses already defined protocols for =
compression, multiplexing and tunneling (ROHC, PPPMux, MPLS, GRE, L2TP). =
<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>Goals and Milestones<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 TCM-TF reference =
model and the scenarios of interest. This would obsolete =
RFC4170.<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 TCM-TF negotiation =
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>Specification of TCM-TF recommendations 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>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Current version of Document (TCM-TF =
- reference model):<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><a =
href=3D"https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http=
s://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></s=
pan></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Current version of Document (TCM-TF - =
recommendations):<o:p></o:p></span></p><p class=3DMsoNormal><a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
><span =
lang=3DEN-US>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tc=
mtf/</span></a><span =
lang=3DEN-US><o:p></o:p></span></p></div></body></html>
------=_NextPart_000_001C_01CF0C6C.4BECDFD0--


From jsaldana@unizar.es  Wed Jan  8 03:23:59 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 587771AE24D; Wed,  8 Jan 2014 03:23:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.738
X-Spam-Level: 
X-Spam-Status: No, score=-4.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UWEmN4Wu9bBe; Wed,  8 Jan 2014 03:23:57 -0800 (PST)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 456FB1AE190; Wed,  8 Jan 2014 03:23:57 -0800 (PST)
Received: from jsaldanapc ([195.76.232.154]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id s08BNbsE004756; Wed, 8 Jan 2014 12:23:39 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>, <tsv-area@ietf.org>
Date: Wed, 8 Jan 2014 12:23:35 +0100
Message-ID: <002001cf0c64$16febd50$44fc37f0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0021_01CF0C6C.78C4ABF0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8MUDMHI8WArDtQT76g60VDH0LMNw==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Martin Stiemerling <mls.ietf@googlemail.com>
Subject: [tcmtf] TCM-TF current drafts
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 08 Jan 2014 11:23:59 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0021_01CF0C6C.78C4ABF0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all, these are the current versions of the two drafts related to TCM-TF:

 

Current version of Document (TCM-TF - reference model):

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

 

Current version of Document (TCM-TF - recommendations):

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

 

Best regards,

 

Jose


------=_NextPart_000_0021_01CF0C6C.78C4ABF0
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, these are the current versions of the two drafts =
related to TCM-TF:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Current version of Document (TCM-TF - reference =
model):<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US><a =
href=3D"https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http=
s://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></s=
pan></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Current version of Document (TCM-TF - =
recommendations):<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><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>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_0021_01CF0C6C.78C4ABF0--


From david.black@emc.com  Wed Jan  8 06:34:16 2014
Return-Path: <david.black@emc.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10B001AE3D8; Wed,  8 Jan 2014 06:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.824
X-Spam-Level: 
X-Spam-Status: No, score=-1.824 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, ONE_TIME=0.714, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z9lijvikoFey; Wed,  8 Jan 2014 06:34:12 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 90F961AE3C1; Wed,  8 Jan 2014 06:34:00 -0800 (PST)
Received: from maildlpprd54.lss.emc.com (maildlpprd54.lss.emc.com [10.106.48.158]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s08EXklQ029135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Jan 2014 09:33:48 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s08EXklQ029135
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1389191628; bh=QIQsRoEUiSNSwTbHjPy+sLtfDNE=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=HlTm7k0ZBqINjkCiSrm6VMKBpb5bbHCihEqkToPnmIM6EC7AJfvFHn2Sm2RmrAqTL IBqZbZ5T6gGDPz+LiKMEPhdrX1lrK0xviXTZ2lclb/3xqQKUnlEDpNeeOs4Hhe8BOE dxfIAVUjEqYaDe3IB3EcL9MKy39RdIHgufTpR9Lk=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s08EXklQ029135
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd54.lss.emc.com (RSA Interceptor); Wed, 8 Jan 2014 09:33:28 -0500
Received: from mxhub01.corp.emc.com (mxhub01.corp.emc.com [10.254.141.103]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s08EXR3c013868 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 8 Jan 2014 09:33:28 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub01.corp.emc.com ([10.254.141.103]) with mapi; Wed, 8 Jan 2014 09:33:27 -0500
From: "Black, David" <david.black@emc.com>
To: Jose Saldana <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
Date: Wed, 8 Jan 2014 09:33:26 -0500
Thread-Topic: Next version (v10) of TCM-TF charter draft
Thread-Index: Ac8MUTJEFfBaeFLER7ezjsW9Se+pLwALH/ig
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026EF3043D@MX15A.corp.emc.com>
References: <001b01cf0c63$ea240b00$be6c2100$@unizar.es>
In-Reply-To: <001b01cf0c63$ea240b00$be6c2100$@unizar.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8D3D17ACE214DC429325B2B98F3AE712026EF3043DMX15Acorpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: DLM_1, public
Cc: Martin Stiemerling <mls.ietf@googlemail.com>
Subject: Re: [tcmtf] Next version (v10) of TCM-TF charter draft
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 08 Jan 2014 14:34:16 -0000

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

Jose,

This version is definitely improved.

I would suggest moving the signaling material from paragraph 5 into paragra=
ph 7 so that the existing signaling protocols and the new TCM-TF negotiatio=
n protocol (including their intended relationship/interaction) are discusse=
d in one place. The rest of paragraph 5 could then be merged into paragraph=
 6.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
david.black@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------

From: tsv-area [mailto:tsv-area-bounces@ietf.org] On Behalf Of Jose Saldana
Sent: Wednesday, January 08, 2014 6:22 AM
To: tcmtf@ietf.org; tsv-area@ietf.org
Cc: Martin Stiemerling
Subject: Next version (v10) of TCM-TF charter draft

Tunneling Compressed Multiplexed Traffic Flows (TCM-TF) charter draft v10

Description of Working Group

1. RFC4170 (TCRTP) defines a method for grouping packets when a number of U=
DP/RTP VoIP flows share a common path, considering three different layers: =
ECRTP header compression; PPPMux multiplexing; L2TPv3 tunneling. TCRTP opti=
mizes the traffic, increasing the bandwidth efficiency of VoIP and reduces =
the amount of packets per second at the same time.

2. However, in the last years, emerging real-time services which use bare U=
DP instead of UDP/RTP have become popular. Due to the need of interactivity=
, many of these services use small packets (some tens of bytes). Some other=
 services also send small packets, but they are not delay-sensitive (e.g., =
instant messaging, m2m packets in sensor networks). In addition, a signific=
ant effort has been devoted to the deployment of new header compression met=
hods with improved robustness (ROHC).

3. So there is a need of replacing RFC4170 with an extended solution able t=
o optimize these new flows, also using improved compression methods. The sa=
me structure of three layers will be considered:

* Header compression: different protocols can be used: no compression, ECRT=
P, IPHC and ROHC.
* Multiplexing: PPPMux will be the option.
* Tunneling: the options in this layer are L2TP, GRE and MPLS.

4. New scenarios where bandwidth savings are desirable have been identified=
, in addition to those considered in RFC4170. In these scenarios, there are=
 moments or places where network capacity gets scarce, so allocating more b=
andwidth is a possible solution, but it implies a recurring cost. However, =
the inclusion of a pair of boxes able to optimize the traffic when/where re=
quired is a one-time investment. These scenarios can be classified into:

* Multidomain, the TCMT-TF tunnel goes all the way from one network edge to=
 another, and can therefore cross several domains.
* Single Domain, TCM-TF is only activated inside an ISP, from the edge to b=
order inside the network operator.
* Private Solutions. TCM-TF is used to connect private networks geographica=
lly apart (e.g. corporation headquarters and subsidiaries), without the ISP=
 being aware or having to manage those flows.
* Mixed Scenarios, any combination of the previous ones.

5. Since standard protocols are being used at each layer, the signaling met=
hods of those protocols will be used. Thus, interactions with the Working G=
roups and Areas in which these protocols are developed can be expected. How=
ever, the development of new compressing, multiplexing or tunneling protoco=
ls is not an objective of this Working Group. In addition, since the curren=
t RFC 4170 would be considered as one of the options, this RFC would be obs=
oleted.

6. A first document (TCM-TF - reference model) will define the different op=
tions which can be used at each layer. It will include a detailed specifica=
tion of the scenarios of interest. Specific problems caused by the interact=
ion between layers will have to be issued, and suitable extensions may have=
 to be added to the involved protocols. The impact on other protocols will =
also be studied.

7. Taking into account that different options will be considered, when a pa=
ir of TCM-TF optimizers want to establish a session, they have first to neg=
otiate which concrete option would they use in each layer. This will depend=
 on the protocols that each extreme implements at each level, and in the sc=
enario. So another document (TCM-TF - negotiation protocol) will include:

* a mechanism to setup/release a TCM-TF session between an ingress and an e=
gress-optimizer, also including:
* a negotiation mechanism to decide the options to use at each layer .

8. As a counterpart of the bandwidth saving, TCM-TF may add some delay and =
jitter. This is not a problem for the services which are not sensitive to d=
elay. However, regarding delay-sensitive services, the Working Group will a=
lso develop a document (TCM-TF - recommendations) with useful recommendatio=
ns in order to decide which packet flows can or can not be multiplexed and =
how. The document will present a list of available traffic classification m=
ethods which can be used for identification of the service or application t=
o which a particular flow belongs, as well as recommendations of the maximu=
m delay and jitter to be added depending of the identified service or appli=
cation. The eventual impact of multiplexing on protocol dynamics (e.g. the =
loss of a multiplexed packet, MTU-related issues) will also have to be addr=
essed.

9. The working group may identify additional deliverables that are necessar=
y/useful, e.g., a mechanism for a TCM-ingress optimizer to discover an egre=
ss optimizer, and vice versa. The working group would re-charter to add the=
m before working on them.

10. Interactions with other Working Groups can be expected, since TCM-TF us=
es already defined protocols for compression, multiplexing and tunneling (R=
OHC, PPPMux, MPLS, GRE, L2TP).

Goals and Milestones

Specification of TCM-TF reference model and the scenarios of interest. This=
 would obsolete RFC4170.

Specification of TCM-TF negotiation protocol.

Specification of TCM-TF recommendations of using existing traffic classific=
ation methods, maximum delay and jitter to add, depending on the service.


Current version of Document (TCM-TF - reference model):
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/

Current version of Document (TCM-TF - recommendations):
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/

--_000_8D3D17ACE214DC429325B2B98F3AE712026EF3043DMX15Acorpemcc_
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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:70.85pt 85.05pt 70.85pt 85.05pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>Jose,<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Co=
urier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>This v=
ersion is definitely improved.<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&=
nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;=
font-family:"Courier New";color:black'>I would suggest moving the signaling=
 material from paragraph 5 into paragraph 7 so that the existing signaling =
protocols and the new TCM-TF negotiation protocol (including their intended=
 relationship/interaction) are discussed in one place. The rest of paragrap=
h 5 could then be merged into paragraph 6.<o:p></o:p></span></p><p class=3D=
MsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:b=
lack'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span style=3D'=
font-size:10.0pt;font-family:"Courier New";color:black'>Thanks,<br>--David<=
br>----------------------------------------------------<br>David L. Black, =
Distinguished Engineer<br>EMC Corporation, 176 South St., Hopkinton, MA&nbs=
p; 01748<br>+1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; FAX: +1 (508) 293-7786<br>david.black@emc.com&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile: +1 (978) 394-7754<br>------=
----------------------------------------------</span><span style=3D'font-fa=
mily:"Courier New";color:black'><o:p></o:p></span></p></div><p class=3DMsoN=
ormal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black=
'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:solid b=
lue 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=3DMsoNormal><b>=
<span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</s=
pan></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>=
 tsv-area [mailto:tsv-area-bounces@ietf.org] <b>On Behalf Of </b>Jose Salda=
na<br><b>Sent:</b> Wednesday, January 08, 2014 6:22 AM<br><b>To:</b> tcmtf@=
ietf.org; tsv-area@ietf.org<br><b>Cc:</b> Martin Stiemerling<br><b>Subject:=
</b> Next version (v10) of TCM-TF charter draft<o:p></o:p></span></p></div>=
</div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Tunnel=
ing Compressed Multiplexed Traffic Flows (TCM-TF) charter draft v10<o:p></o=
:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Descr=
iption of Working Group<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p><p class=3DMsoNormal>1. RFC4170 (TCRTP) defines a method for grouping =
packets when a number of UDP/RTP VoIP flows share a common path, considerin=
g three different layers: ECRTP header compression; PPPMux multiplexing; L2=
TPv3 tunneling. TCRTP optimizes the traffic, increasing the bandwidth effic=
iency of VoIP and reduces the amount of packets per second at the same time=
.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNor=
mal>2. However, in the last years, emerging real-time services which use ba=
re UDP instead of UDP/RTP have become popular. Due to the need of interacti=
vity, many of these services use small packets (some tens of bytes). Some o=
ther services also send small packets, but they are not delay-sensitive (e.=
g., instant messaging, m2m packets in sensor networks). In addition, a sign=
ificant effort has been devoted to the deployment of new header compression=
 methods with improved robustness (ROHC).<o:p></o:p></p><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>3. So there is a need of replac=
ing RFC4170 with an extended solution able to optimize these new flows, als=
o using improved compression methods. The same structure of three layers wi=
ll be considered:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><=
p class=3DMsoNormal>* Header compression: different protocols can be used: =
no compression, ECRTP, IPHC and ROHC.<o:p></o:p></p><p class=3DMsoNormal>* =
Multiplexing: PPPMux will be the option.<o:p></o:p></p><p class=3DMsoNormal=
>* Tunneling: the options in this layer are L2TP, GRE and MPLS.<o:p></o:p><=
/p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>4. New sc=
enarios where bandwidth savings are desirable have been identified, in addi=
tion to those considered in RFC4170. In these scenarios, there are moments =
or places where network capacity gets scarce, so allocating more bandwidth =
is a possible solution, but it implies a recurring cost. However, the inclu=
sion of a pair of boxes able to optimize the traffic when/where required is=
 a one-time investment. These scenarios can be classified into:<o:p></o:p><=
/p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>* Multido=
main, the TCMT-TF tunnel goes all the way from one network edge to another,=
 and can therefore cross several domains.<o:p></o:p></p><p class=3DMsoNorma=
l>* Single Domain, TCM-TF is only activated inside an ISP, from the edge to=
 border inside the network operator. <o:p></o:p></p><p class=3DMsoNormal>* =
Private Solutions. TCM-TF is used to connect private networks geographicall=
y apart (e.g. corporation headquarters and subsidiaries), without the ISP b=
eing aware or having to manage those flows.<o:p></o:p></p><p class=3DMsoNor=
mal>* Mixed Scenarios, any combination of the previous ones.<o:p></o:p></p>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>5. Since sta=
ndard protocols are being used at each layer, the signaling methods of thos=
e protocols will be used. Thus, interactions with the Working Groups and Ar=
eas in which these protocols are developed can be expected. However, the de=
velopment of new compressing, multiplexing or tunneling protocols is not an=
 objective of this Working Group. In addition, since the current RFC 4170 w=
ould be considered as one of the options, this RFC would be obsoleted.<o:p>=
</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>6.=
 A first document (TCM-TF - reference model) will define the different opti=
ons which can be used at each layer. It will include a detailed specificati=
on of the scenarios of interest. Specific problems caused by the interactio=
n between layers will have to be issued, and suitable extensions may have t=
o be added to the involved protocols. The impact on other protocols will al=
so be studied.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p c=
lass=3DMsoNormal>7. Taking into account that different options will be cons=
idered, when a pair of TCM-TF optimizers want to establish a session, they =
have first to negotiate which concrete option would they use in each layer.=
 This will depend on the protocols that each extreme implements at each lev=
el, and in the scenario. So another document (TCM-TF - negotiation protocol=
) will include:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>* a mechanism to setup/release a TCM-TF session between a=
n ingress and an egress-optimizer, also including:<o:p></o:p></p><p class=
=3DMsoNormal>* a negotiation mechanism to decide the options to use at each=
 layer .<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>8. As a counterpart of the bandwidth saving, TCM-TF may add so=
me delay and jitter. This is not a problem for the services which are not s=
ensitive to delay. However, regarding delay-sensitive services, the Working=
 Group will also develop a document (TCM-TF - recommendations) with useful =
recommendations in order to decide which packet flows can or can not be mul=
tiplexed and how. The document will present a list of available traffic cla=
ssification 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 ser=
vice or application. The eventual impact of multiplexing on protocol dynami=
cs (e.g. the loss of a multiplexed packet, MTU-related issues) will also ha=
ve to be addressed.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
><p class=3DMsoNormal>9. The working group may identify additional delivera=
bles that are necessary/useful, e.g., a mechanism for a TCM-ingress optimiz=
er to discover an egress optimizer, and vice versa. The working group would=
 re-charter to add them before working on them.<o:p></o:p></p><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>10. Interactions with oth=
er Working Groups can be expected, since TCM-TF uses already defined protoc=
ols for compression, multiplexing and tunneling (ROHC, PPPMux, MPLS, GRE, L=
2TP). <o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DM=
soNormal>Goals and Milestones<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp=
;</o:p></p><p class=3DMsoNormal>Specification of TCM-TF reference model and=
 the scenarios of interest. This would obsolete RFC4170.<o:p></o:p></p><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Specification of=
 TCM-TF negotiation protocol.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp=
;</o:p></p><p class=3DMsoNormal>Specification of TCM-TF recommendations of =
using existing traffic classification methods, maximum delay and jitter to =
add, depending on the service.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>=
Current version of Document (TCM-TF - reference model):<o:p></o:p></p><p cl=
ass=3DMsoNormal><a href=3D"https://datatracker.ietf.org/doc/draft-saldana-t=
svwg-tcmtf/">https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a=
><o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNor=
mal>Current version of Document (TCM-TF - recommendations):<o:p></o:p></p><=
p class=3DMsoNormal><span lang=3DES><a href=3D"http://datatracker.ietf.org/=
doc/draft-suznjevic-tsvwg-mtd-tcmtf/"><span lang=3DEN-US>http://datatracker=
.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</span></a></span><o:p></o:p>=
</p></div></div></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE712026EF3043DMX15Acorpemcc_--

From jsaldana@unizar.es  Wed Jan  8 16:11:53 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B81F1ACCEC; Wed,  8 Jan 2014 16:11:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.738
X-Spam-Level: 
X-Spam-Status: No, score=-4.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HE97BzjnAT92; Wed,  8 Jan 2014 16:11:48 -0800 (PST)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8A1C91ADEA7; Wed,  8 Jan 2014 16:11:41 -0800 (PST)
Received: from jsaldanapc ([107.19.188.169]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id s090B1fQ014219; Thu, 9 Jan 2014 01:11:08 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Black, David'" <david.black@emc.com>, <tcmtf@ietf.org>, <tsv-area@ietf.org>, "Luigi Iannone" <ggx@gigix.net>
References: <00c401cefd65$6e8ef570$4bace050$@unizar.es> <8D3D17ACE214DC429325B2B98F3AE712026EF2FF8F@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712026EF2FF8F@MX15A.corp.emc.com>
Date: Thu, 9 Jan 2014 01:10:48 +0100
Message-ID: <004701cf0ccf$4d5826a0$e80873e0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0048_01CF0CD7.AF212280"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKm4iuy1T4jUNWcvPCI8e0mPkHF7QHB3wddmLzCScA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: 'Martin Stiemerling' <mls.ietf@googlemail.com>
Subject: Re: [tcmtf] TCMTF-Feedback about a possible BoF in London
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Jan 2014 00:11:53 -0000

This is a multipart message in MIME format.

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

Hi all.

=20

First of all, thanks to David and Luigi for their valuable comments.

=20

I will wait for a while in order to include David=92s comments (perhaps =
some
other people has more suggestions).

=20

These are the improvements of version 10 with respect to v9 (
<http://www.ietf.org/mail-archive/web/tcmtf/current/msg00486.html>
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00486.html)

=20

- I have shortened paragraph 1.

- I have shortened and merged paragraphs 2 and 3.

- I have moved paragraph 4 to the third place, in order to set clearer =
what
we want: replacing RFC4170 with a widened proposal. As David suggested, =
I
have also shortened the text and it is now more straightforward.

- I have clearly stated which protocols will be used on each layer. The
negotiation mechanism is still necessary, since different options are
considered e.g. for header compression. The one to be used will depend =
on
the scenario and the processing capacity of the two optimizers.

- I have significantly shortened the description of the scenarios.

- I have removed paragraph 6, which included the savings figures.

- I have included the replacement of RFC4170 in the first milestone.

=20

Thanks!

=20

Jose

=20

De: Black, David [ <mailto:david.black@emc.com> =
mailto:david.black@emc.com]=20
Enviado el: s=E1bado, 04 de enero de 2014 4:05
Para: Jose Saldana;  <mailto:tcmtf@ietf.org> tcmtf@ietf.org;
<mailto:tsv-area@ietf.org> tsv-area@ietf.org
CC: Martin Stiemerling; Black, David
Asunto: RE: TCMTF-Feedback about a possible BoF in London

=20

A second BoF has the explicit goal of forming a WG, as a third BoF

is not permitted.  In that regard, the new charter seems long and

somewhat lacking in focus.  Two key things I look for in a proposed

charter are what problem (or problems) the proposed WG is looking to

solve and an initial approach to the problem or problems.

=20

In the new draft charter, the problem statement appears to be in

paragraph 4 with paragraph 1 providing important background.  The

focus of the work appears to be on extending TCRTP (RFC 4170) to

UDP and to include new compression protocols.  In contrast, I have

a hard time discerning the initial approach from the new draft charter.

=20

In light of this, there are a few things that I wish the new

draft charter had definitive proposals for:

=20

      a) Whether to replace RFC 4170 vs. write a new RFC (could be

            UDP-only or UDP + RTP/UDP) as a complement to RFC 4170.

      b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC (RFC 2507 =
?).

            Non-use of ECRTP would be a major change to 4170, and I

wonder about IPHC, as opposed to the ROHCv2 profiles.

      c) Analogies to b) for the Mux and Tunnel layers of the stack.

=20

Overall, it looks like the first task of the WG is to select the =
protocol

stack to standardize - I have misgivings about that, and would prefer to

see a concrete proposal in a crisp charter that ran along the following

lines, naming the protocols to be used:

=20

1) RFC 4170 does X, and needs the following changes/additions: X, Y, Z.

2) The WG will replace RFC 4170 with a new RFC that contains: A, B, C.

=20

A specific proposal or proposals for the protocol stack or stacks

would also narrow the scope of item 9 in the charter on the negotiation

mechanism.  I also don=92t see a goal/milestone listed for an extension =
to

or replacement for RFC 4170.

=20

I=92d prefer to see a much shorter more focused draft charter.  =
There=92s a

bunch of background material that does not seem crucial to the charter,

starting w/paragraphs 2 and 3.

=20

Thanks,
--David

=20

From: tsv-area [ <mailto:tsv-area-bounces@ietf.org>
mailto:tsv-area-bounces@ietf.org] On Behalf Of Jose Saldana
Sent: Friday, December 20, 2013 4:26 AM
To:  <mailto:tcmtf@ietf.org> tcmtf@ietf.org;  <mailto:tsv-area@ietf.org>
tsv-area@ietf.org
Cc: Martin Stiemerling
Subject: TCMTF-Feedback about a possible BoF in London

=20

Hi all,

=20

After the feedback received in the BoF in Berlin, we have updated the =
TCM-TF
charter and the two drafts. We have tried to solve all the problems =
raised
during the session.

=20

Our plan is to request a new BoF in London next March, so we would like =
to
know your opinion about these two questions:

=20

=20

1.  Is the new, reduced scope of TCM-TF suitable to form a working =
group?

=20

=20

2. We would like to kindly ask people who think that a TCM-TF Working =
group
should be formed, to come forward and send an e-mail to the
<mailto:tsv-area@ietf.org> tsv-area@ietf.org  mailing list stating it.

=20

=20

This feedback will allow us to get a better idea of the convenience of a
BoF.

=20

The new charter is here:
<http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html>
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html

This is the old one (presented in Berlin):
<http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.html>
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.html

=20

In these links you can see the differences between the new versions of =
the
drafts and the old ones:

=20
<http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&ur=
l2=3Ddr
aft-saldana-tsvwg-tcmtf-05.txt>
http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&url=
2=3Ddra
ft-saldana-tsvwg-tcmtf-05.txt

=20
<http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.=
txt&u
rl2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt>
http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.t=
xt&ur
l2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt

=20

=20

The main improvements are:

=20

- TCP optimization has been removed

- The classification of the scenarios has been refined and improved. =
Some of
them have been removed

- A section about energy consumption has been added to the main draft

- A reference to the potential problem of the MTU and packet loss has =
been
added

- The problem of the added delays is studied in detail in the second =
draft

=20

- The improvements of the charter are summarized here:
<http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.html>
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.html

=20

=20

Best regards,

=20

Jose

=20


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texto de globo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","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.EstiloCorreo19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo20
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EstiloCorreo21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>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'>First of =
all, thanks to David and Luigi for their valuable =
comments.<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 will wait =
for a while in order to include David&#8217;s comments (perhaps some =
other people has more suggestions).<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'>These are =
the improvements of version 10 with respect to v9 (</span><a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00486.html"=
><span =
lang=3DEN-US>http://www.ietf.org/mail-archive/web/tcmtf/current/msg00486.=
html</span></a><span lang=3DEN-US>)</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><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- I have =
shortened paragraph 1.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>- I have shortened and merged =
paragraphs 2 and 3.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>- I have moved paragraph 4 to the =
third place, in order to set clearer what we want: replacing RFC4170 =
with a widened proposal. As David suggested, I have also shortened the =
text and it is now more straightforward.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- I have =
clearly stated which protocols will be used on each layer. The =
negotiation mechanism is still necessary, since different options are =
considered e.g. for header compression. The one to be used will depend =
on the scenario and the processing capacity of the two =
optimizers.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>- I have significantly shortened the description =
of the scenarios.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>- I have removed paragraph 6, which =
included the savings figures.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- I have =
included the replacement of RFC4170 in the first =
milestone.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Thanks!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span 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"'> Black, =
David [</span><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><a =
href=3D"mailto:david.black@emc.com"><span =
lang=3DEN-US>mailto:david.black@emc.com</span></a></span><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>] =
<br><b>Enviado el:</b> s=E1bado, 04 de enero de 2014 =
4:05<br><b>Para:</b> Jose Saldana; </span><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><a =
href=3D"mailto:tcmtf@ietf.org"><span =
lang=3DEN-US>tcmtf@ietf.org</span></a></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>; =
</span><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><a =
href=3D"mailto:tsv-area@ietf.org"><span =
lang=3DEN-US>tsv-area@ietf.org</span></a></span><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br><b>CC:</=
b> Martin Stiemerling; Black, David<br><b>Asunto:</b> RE: TCMTF-Feedback =
about a possible BoF in London<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'font-size:10.0pt;font-family:"Courier New";color:black'>A =
second BoF has the explicit goal of forming a WG, as a third =
BoF<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'>is not =
permitted.&nbsp; In that regard, the new charter seems long =
and<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'>somewhat lacking in focus.&nbsp; Two key things I look =
for in a proposed<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'>charter are what problem (or problems) the proposed WG =
is looking to<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'>solve and an initial approach to the problem or =
problems.<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>In the new draft charter, the problem statement =
appears to be in<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'>paragraph 4 with paragraph 1 providing important =
background.&nbsp; The<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'>focus of the work appears to be on extending TCRTP =
(RFC 4170) to<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'>UDP and to include new compression protocols.&nbsp; In =
contrast, I have<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 hard time discerning the initial approach from the =
new draft charter.<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>In light of this, there are a few things that I wish =
the new<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'>draft =
charter had definitive proposals for:<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Whether to replace =
RFC 4170 vs. write a new RFC (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";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; UDP-only or UDP + RTP/UDP) as a complement to RFC =
4170.<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;&nbsp;&nbsp;&nbsp;&nbsp; b) Whether to use =
ECRTP, ROHCv2 (RFC 5225) and/or IPHC (RFC 2507 =
?).<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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; Non-use of ECRTP would be a major change to 4170, and =
I<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:36.0pt;text-indent:36.0pt'><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>wonder =
about IPHC, as opposed to the ROHCv2 profiles.<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;&nbsp;&nbsp;&nbsp;&nbsp; c) Analogies to b) for =
the Mux and Tunnel layers of the stack.<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>Overall, it looks like the first task of the WG is to =
select the protocol<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'>stack to standardize - I have misgivings about that, =
and would prefer to<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'>see a concrete proposal in a crisp charter that ran =
along the following<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'>lines, naming the protocols to be =
used:<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>1) RFC 4170 does X, and needs the following =
changes/additions: X, Y, Z.<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) The =
WG will replace RFC 4170 with a new RFC that contains: A, B, =
C.<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>A specific proposal or proposals for the protocol =
stack or stacks<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'>would also narrow the scope of item 9 in the charter =
on the negotiation<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'>mechanism.&nbsp; I also don&#8217;t see a =
goal/milestone listed for an extension to<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'>or =
replacement for RFC 4170.<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'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>I&#8217;d prefer to see a much shorter more focused =
draft charter.&nbsp; There&#8217;s a<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'>bunch =
of background material that does not seem crucial to the =
charter,<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'>starting w/paragraphs 2 and 3.<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'><o:p>&nbsp;</o:p></span></p><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>Thanks,<br>--David</span><span lang=3DEN-US =
style=3D'font-family:"Courier =
New";color:black'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'><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"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> tsv-area =
[</span><a href=3D"mailto:tsv-area-bounces@ietf.org"><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>mailto:tsv-a=
rea-bounces@ietf.org</span></a><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>] <b>On =
Behalf Of </b>Jose Saldana<br><b>Sent:</b> Friday, December 20, 2013 =
4:26 AM<br><b>To:</b> </span><a href=3D"mailto:tcmtf@ietf.org"><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>tcmtf@ietf.o=
rg</span></a><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>; </span><a =
href=3D"mailto:tsv-area@ietf.org"><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>tsv-area@iet=
f.org</span></a><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br><b>Cc:</=
b> Martin Stiemerling<br><b>Subject:</b> TCMTF-Feedback about a possible =
BoF in London<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>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>After the feedback received in the =
BoF in Berlin, we have updated the TCM-TF charter and the two drafts. We =
have tried to solve all the problems raised during the =
session.<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>Our plan is to request a new BoF in London next March, so =
we would like to know your opinion about these two =
questions:<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>1. &nbsp;Is the new, reduced scope of TCM-TF suitable to =
form a 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><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>2. We would like to kindly ask people who think that a =
TCM-TF Working group should be formed, to come forward and send an =
e-mail to the </span><a href=3D"mailto:tsv-area@ietf.org"><span =
lang=3DEN-US>tsv-area@ietf.org</span></a><span lang=3DEN-US> =
&nbsp;mailing list stating it.<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>This feedback will allow us to get =
a better idea of the convenience of a BoF.<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 new charter is here: </span><a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html"=
><span =
lang=3DEN-US>http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.=
html</span></a><span lang=3DEN-US><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>This is the old one (presented in =
Berlin): </span><a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.html"=
><span =
lang=3DEN-US>http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.=
html</span></a><span lang=3DEN-US><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>In these links you can see the =
differences between the new versions of the drafts and the old =
ones:<o:p></o:p></span></p><p class=3DMsoNormal><a =
href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06=
.txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt"><span =
lang=3DEN-US>http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcm=
tf-06.txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt</span></a><span =
lang=3DEN-US><o:p></o:p></span></p><p class=3DMsoNormal><a =
href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tc=
mtf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt"><span =
lang=3DEN-US>http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-m=
td-tcmtf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt</span><=
/a><span lang=3DEN-US><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>The main improvements are:<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>- TCP optimization has been =
removed<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>- =
The classification of the scenarios has been refined and improved. Some =
of them have been removed<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- A section about energy =
consumption has been added to the main draft<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- A reference to the potential =
problem of the MTU and packet loss has been =
added<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>- The =
problem of the added delays is studied in detail in the second =
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>- The improvements of the charter are summarized here: =
</span><a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.html"=
><span =
lang=3DEN-US>http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.=
html</span></a><span lang=3DEN-US><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><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></div></body></html>
------=_NextPart_000_0048_01CF0CD7.AF212280--


From Tina.Tsou.Zouting@huawei.com  Wed Jan  8 16:50:04 2014
Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25DDE1ADF26; Wed,  8 Jan 2014 16:50:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.024
X-Spam-Level: 
X-Spam-Status: No, score=-4.024 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, ONE_TIME=0.714, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sAOaze_iiw2y; Wed,  8 Jan 2014 16:50:00 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id E34511ADEA0; Wed,  8 Jan 2014 16:49:57 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCH61343; Thu, 09 Jan 2014 00:49:47 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Jan 2014 00:49:12 +0000
Received: from SJCEML702-CHM.china.huawei.com (10.212.94.48) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Jan 2014 00:49:46 +0000
Received: from SJCEML701-CHM.china.huawei.com ([169.254.3.228]) by SJCEML702-CHM.china.huawei.com ([169.254.4.68]) with mapi id 14.03.0158.001; Wed, 8 Jan 2014 16:49:41 -0800
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Jose Saldana <jsaldana@unizar.es>
Thread-Topic: [tcmtf] TCMTF-Feedback about a possible BoF in London
Thread-Index: AQKm4iuy1T4jUNWcvPCI8e0mPkHF7QHB3wddmLzCScCAARPDxw==
Date: Thu, 9 Jan 2014 00:49:41 +0000
Message-ID: <B180C070-CA16-47BE-9A43-1F10546426DA@huawei.com>
References: <00c401cefd65$6e8ef570$4bace050$@unizar.es> <8D3D17ACE214DC429325B2B98F3AE712026EF2FF8F@MX15A.corp.emc.com>, <004701cf0ccf$4d5826a0$e80873e0$@unizar.es>
In-Reply-To: <004701cf0ccf$4d5826a0$e80873e0$@unizar.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_B180C070CA1647BE9A431F10546426DAhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, Luigi Iannone <ggx@gigix.net>, "Black, David" <david.black@emc.com>, "tsv-area@ietf.org" <tsv-area@ietf.org>, Martin Stiemerling <mls.ietf@googlemail.com>
Subject: Re: [tcmtf] TCMTF-Feedback about a possible BoF in London
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Jan 2014 00:50:04 -0000

--_000_B180C070CA1647BE9A431F10546426DAhuaweicom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Dear all,
I'm in favor of having a BoF in London, as the following problem statement =
seems valid and needs protocol work in IETF.
---
In addition to VoIP, in the last years we are witnessing the raise of new r=
eal-time services e.g. videoconferencing, telemedicine, video vigilance, on=
line gaming, etc.

Due to the need of interactivity, many of these services use small packets =
(some tens of bytes), since they have to send frequent updates between the =
extremes of the communication. Their small data payloads incur significant =
overhead, and it becomes even higher when IPv6 is used, since the basic IPv=
6 header is twice the size of the IPv4 one.

In the moments or places where network capacity gets scarce, allocating mor=
e bandwidth is a possible solution, but it implies a recurring cost. Howeve=
r, the inclusion of a pair of boxes able to optimize the traffic (reducing =
bandwidth and packets per second) when/where required is a one-time investm=
ent. We can do these three things:

a) header compression algorithms (e.g. ROHC) can be used for reducing the o=
verhead of each flow;
b) at the same time, tunneling can be used in order to allow the header-com=
pressed packets to travel end-to-end
c) compressed packets belonging to different flows can be multiplexed toget=
her, in order to share the tunnel overhead.

These emerging real-time services which use bare UDP instead of UDP/RTP hav=
e become popular. In addition, a significant effort has been devoted to the=
 deployment of new header compression methods with improved robustness (ROH=
C). So there is a need of widening the scope of RFC4170 in order to conside=
r these new header compression methods, and also UDP in addition to UDP/RTP=
.

As a result, the next objectives can be achieved:

* Significant bandwidth reductions (as an example, bandwidth savings of 55%=
 can be obtained for VoIP if IPv4 is used, and 65% using IPv6. For certain =
online games, 33% of the bandwidth can be saved for IPv4, and 55% when usin=
g IPv6).

* A reduction of the amount of packets per second managed by the network. A=
 reduction factor of 10 or 20 can easily be achieved. This can be translate=
d into smaller processing delays and energy savings in intermediate routers=
.
---

Thank you,
Tina

On Jan 8, 2014, at 4:11 PM, "Jose Saldana" <jsaldana@unizar.es<mailto:jsald=
ana@unizar.es>> wrote:

Hi all.

First of all, thanks to David and Luigi for their valuable comments.

I will wait for a while in order to include David=92s comments (perhaps som=
e other people has more suggestions).

These are the improvements of version 10 with respect to v9 (http://www.iet=
f.org/mail-archive/web/tcmtf/current/msg00486.html)

- I have shortened paragraph 1.
- I have shortened and merged paragraphs 2 and 3.
- I have moved paragraph 4 to the third place, in order to set clearer what=
 we want: replacing RFC4170 with a widened proposal. As David suggested, I =
have also shortened the text and it is now more straightforward.
- I have clearly stated which protocols will be used on each layer. The neg=
otiation mechanism is still necessary, since different options are consider=
ed e.g. for header compression. The one to be used will depend on the scena=
rio and the processing capacity of the two optimizers.
- I have significantly shortened the description of the scenarios.
- I have removed paragraph 6, which included the savings figures.
- I have included the replacement of RFC4170 in the first milestone.

Thanks!

Jose

De: Black, David [mailto:david.black@emc.com]
Enviado el: s=E1bado, 04 de enero de 2014 4:05
Para: Jose Saldana; tcmtf@ietf.org<mailto:tcmtf@ietf.org>; tsv-area@ietf.or=
g<mailto:tsv-area@ietf.org>
CC: Martin Stiemerling; Black, David
Asunto: RE: TCMTF-Feedback about a possible BoF in London

A second BoF has the explicit goal of forming a WG, as a third BoF
is not permitted.  In that regard, the new charter seems long and
somewhat lacking in focus.  Two key things I look for in a proposed
charter are what problem (or problems) the proposed WG is looking to
solve and an initial approach to the problem or problems.

In the new draft charter, the problem statement appears to be in
paragraph 4 with paragraph 1 providing important background.  The
focus of the work appears to be on extending TCRTP (RFC 4170) to
UDP and to include new compression protocols.  In contrast, I have
a hard time discerning the initial approach from the new draft charter.

In light of this, there are a few things that I wish the new
draft charter had definitive proposals for:

      a) Whether to replace RFC 4170 vs. write a new RFC (could be
            UDP-only or UDP + RTP/UDP) as a complement to RFC 4170.
      b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC (RFC 2507 ?).
            Non-use of ECRTP would be a major change to 4170, and I
wonder about IPHC, as opposed to the ROHCv2 profiles.
      c) Analogies to b) for the Mux and Tunnel layers of the stack.

Overall, it looks like the first task of the WG is to select the protocol
stack to standardize - I have misgivings about that, and would prefer to
see a concrete proposal in a crisp charter that ran along the following
lines, naming the protocols to be used:

1) RFC 4170 does X, and needs the following changes/additions: X, Y, Z.
2) The WG will replace RFC 4170 with a new RFC that contains: A, B, C.

A specific proposal or proposals for the protocol stack or stacks
would also narrow the scope of item 9 in the charter on the negotiation
mechanism.  I also don=92t see a goal/milestone listed for an extension to
or replacement for RFC 4170.

I=92d prefer to see a much shorter more focused draft charter.  There=92s a
bunch of background material that does not seem crucial to the charter,
starting w/paragraphs 2 and 3.

Thanks,
--David

From: tsv-area [mailto:tsv-area-bounces@ietf.org] On Behalf Of Jose Saldana
Sent: Friday, December 20, 2013 4:26 AM
To: tcmtf@ietf.org<mailto:tcmtf@ietf.org>; tsv-area@ietf.org<mailto:tsv-are=
a@ietf.org>
Cc: Martin Stiemerling
Subject: TCMTF-Feedback about a possible BoF in London

Hi all,

After the feedback received in the BoF in Berlin, we have updated the TCM-T=
F charter and the two drafts. We have tried to solve all the problems raise=
d during the session.

Our plan is to request a new BoF in London next March, so we would like to =
know your opinion about these two questions:


1.  Is the new, reduced scope of TCM-TF suitable to form a working group?


2. We would like to kindly ask people who think that a TCM-TF Working group=
 should be formed, to come forward and send an e-mail to the tsv-area@ietf.=
org<mailto:tsv-area@ietf.org>  mailing list stating it.


This feedback will allow us to get a better idea of the convenience of a Bo=
F.

The new charter is here: http://www.ietf.org/mail-archive/web/tcmtf/current=
/msg00465.html
This is the old one (presented in Berlin): http://www.ietf.org/mail-archive=
/web/tcmtf/current/msg00368.html

In these links you can see the differences between the new versions of the =
drafts and the old ones:
http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&url2=
=3Ddraft-saldana-tsvwg-tcmtf-05.txt
http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.txt=
&url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt


The main improvements are:

- TCP optimization has been removed
- The classification of the scenarios has been refined and improved. Some o=
f them have been removed
- A section about energy consumption has been added to the main draft
- A reference to the potential problem of the MTU and packet loss has been =
added
- The problem of the added delays is studied in detail in the second draft

- The improvements of the charter are summarized here: http://www.ietf.org/=
mail-archive/web/tcmtf/current/msg00466.html


Best regards,

Jose


--_000_B180C070CA1647BE9A431F10546426DAhuaweicom_
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 dir=3D"auto">
<div style=3D"-webkit-text-size-adjust: auto;"><span style=3D"font-size: 13=
pt;">Dear all,</span></div>
<div style=3D"-webkit-text-size-adjust: auto;">I'm in favor of having a BoF=
 in London, as the following problem statement seems valid and needs protoc=
ol work in IETF.</div>
<div style=3D"-webkit-text-size-adjust: auto;">---</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">In addition to VoIP, in the last years we are wit=
nessing the raise of new real-time services
 e.g. videoconferencing, telemedicine, video vigilance, online gaming, etc.=
<o:p></o:p></font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">&nbsp;</font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">Due to the need of interactivity, many of these s=
ervices use small packets (some tens of bytes),
 since they have to&nbsp;</font></span><span style=3D"font-family: UICTFont=
TextStyleBody; font-size: medium; background-color: rgba(255, 255, 255, 0);=
 -webkit-text-size-adjust: auto;">send frequent updates between the extreme=
s of the communication. Their small data
 payloads incur significant overhead, and it becomes even higher when IPv6 =
is used, since the basic IPv6 header is twice the size of the IPv4 one.</sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">&nbsp;</font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">In the moments or places where network capacity g=
ets scarce, allocating more bandwidth is a
 possible solution, but it implies a recurring cost. However, the inclusion=
 of a pair of boxes able to optimize the traffic (reducing bandwidth and pa=
ckets per second) when/where required is a one-time investment. We can do t=
hese three things:<o:p></o:p></font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">&nbsp;</font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">a) header compression algorithms (e.g. ROHC) can =
be used for reducing the overhead of each
 flow;<o:p></o:p></font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">b) at the same time, tunneling can be used in ord=
er to allow the header-compressed packets
 to travel end-to-end<o:p></o:p></font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">c) compressed packets belonging to different flow=
s can be multiplexed together, in order to
 share the tunnel overhead.<o:p></o:p></font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">&nbsp;</font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">These emerging real-time services which use bare =
UDP instead of UDP/RTP have become popular.
 In addition, a significant&nbsp;</font></span><span style=3D"font-family: =
UICTFontTextStyleBody; font-size: medium; background-color: rgba(255, 255, =
255, 0); -webkit-text-size-adjust: auto;">effort has been devoted to the de=
ployment of new header compression methods
 with improved robustness (ROHC). So there is a need of widening the scope =
of RFC4170 in order to consider these new header compression methods, and a=
lso UDP in addition to UDP/RTP.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">&nbsp;</font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">As a result, the next objectives can be achieved:=
<o:p></o:p></font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">&nbsp;</font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">* Significant bandwidth reductions (as an example=
, bandwidth savings of 55% can be obtained
 for VoIP if IPv4 is used, and 65% using IPv6. For certain online games, 33=
% of the bandwidth can be saved for IPv4, and 55% when using IPv6).<o:p></o=
:p></font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">&nbsp;</font></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"-webkit-text-size-adju=
st: auto; background-color: rgba(255, 255, 255, 0);"><font face=3D"UICTFont=
TextStyleBody" size=3D"3">* A reduction of the amount of packets per second=
 managed by the network. A reduction factor
 of 10 or 20 can easily be achieved. This can be translated into smaller pr=
ocessing delays and energy savings in intermediate routers.<o:p></o:p></fon=
t></span></p>
<p class=3D"MsoNormal">---</p>
<div style=3D"-webkit-text-size-adjust: auto;"><br>
</div>
<div style=3D"-webkit-text-size-adjust: auto;">Thank you,</div>
<div style=3D"-webkit-text-size-adjust: auto;">Tina</div>
</div>
<div style=3D"-webkit-text-size-adjust: auto;"><br>
On Jan 8, 2014, at 4:11 PM, &quot;Jose Saldana&quot; &lt;<a href=3D"mailto:=
jsaldana@unizar.es">jsaldana@unizar.es</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite" style=3D"-webkit-text-size-adjust: auto;">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texto de globo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","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.EstiloCorreo19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo20
	{mso-style-type:personal;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EstiloCorreo21
	{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]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi all.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">First o=
f all, thanks to David and Luigi for their valuable comments.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I will =
wait for a while in order to include David=92s comments (perhaps some other=
 people has more suggestions).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">These a=
re the improvements of version 10 with respect to v9 (</span><a href=3D"htt=
p://www.ietf.org/mail-archive/web/tcmtf/current/msg00486.html"><span lang=
=3D"EN-US">http://www.ietf.org/mail-archive/web/tcmtf/current/msg00486.html=
</span></a><span lang=3D"EN-US">)</span><span lang=3D"EN-US" style=3D"color=
:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">- I hav=
e shortened paragraph 1.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">- I hav=
e shortened and merged paragraphs 2 and 3.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">- I hav=
e moved paragraph 4 to the third place, in order to set clearer what we wan=
t: replacing RFC4170 with a widened proposal. As David suggested, I have al=
so shortened the text and it is now more
 straightforward.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">- I hav=
e clearly stated which protocols will be used on each layer. The negotiatio=
n mechanism is still necessary, since different options are considered e.g.=
 for header compression. The one to be
 used will depend on the scenario and the processing capacity of the two op=
timizers.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">- I hav=
e significantly shortened the description of the scenarios.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">- I hav=
e removed paragraph 6, which included the savings figures.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">- I hav=
e included the replacement of RFC4170 in the first milestone.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thanks!=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Jose<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></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 lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">De:</span></b><span la=
ng=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;"> Black, David [</span><span style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"><a href=3D"mailto:davi=
d.black@emc.com"><span lang=3D"EN-US">mailto:david.black@emc.com</span></a>=
</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tah=
oma&quot;,&quot;sans-serif&quot;">]
<br>
<b>Enviado el:</b> s=E1bado, 04 de enero de 2014 4:05<br>
<b>Para:</b> Jose Saldana; </span><span style=3D"font-size:10.0pt;font-fami=
ly:&quot;Tahoma&quot;,&quot;sans-serif&quot;"><a href=3D"mailto:tcmtf@ietf.=
org"><span lang=3D"EN-US">tcmtf@ietf.org</span></a></span><span lang=3D"EN-=
US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-ser=
if&quot;">;
</span><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;"><a href=3D"mailto:tsv-area@ietf.org"><span lang=3D"EN-US=
">tsv-area@ietf.org</span></a></span><span lang=3D"EN-US" style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"><br>
<b>CC:</b> Martin Stiemerling; Black, David<br>
<b>Asunto:</b> RE: TCMTF-Feedback about a possible BoF in London<o:p></o:p>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">A second BoF has the explicit g=
oal of forming a WG, as a third BoF<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">is not permitted.&nbsp; In that=
 regard, the new charter seems long and<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">somewhat lacking in focus.&nbsp=
; Two key things I look for in a proposed<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">charter are what problem (or pr=
oblems) the proposed WG is looking to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">solve and an initial approach t=
o the problem or problems.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">In the new draft charter, the p=
roblem statement appears to be in<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">paragraph 4 with paragraph 1 pr=
oviding important background.&nbsp; The<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">focus of the work appears to be=
 on extending TCRTP (RFC 4170) to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">UDP and to include new compress=
ion protocols.&nbsp; In contrast, I have<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">a hard time discerning the init=
ial approach from the new draft charter.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">In light of this, there are a f=
ew things that I wish the new<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">draft charter had definitive pr=
oposals for:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
a) Whether to replace RFC 4170 vs. write a new RFC (could be<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UDP-only or UDP &#43; RTP/UDP) as a com=
plement to RFC 4170.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC (RFC 2507 ?).<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Non-use of ECRTP would be a major chang=
e to 4170, and I<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt;text-indent:36.0pt"><spa=
n lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Courier New&qu=
ot;;color:black">wonder about IPHC, as opposed to the ROHCv2 profiles.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
c) Analogies to b) for the Mux and Tunnel layers of the stack.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Overall, it looks like the firs=
t task of the WG is to select the protocol<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">stack to standardize - I have m=
isgivings about that, and would prefer to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">see a concrete proposal in a cr=
isp charter that ran along the following<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">lines, naming the protocols to =
be used:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">1) RFC 4170 does X, and needs t=
he following changes/additions: X, Y, Z.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">2) The WG will replace RFC 4170=
 with a new RFC that contains: A, B, C.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">A specific proposal or proposal=
s for the protocol stack or stacks<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">would also narrow the scope of =
item 9 in the charter on the negotiation<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">mechanism.&nbsp; I also don=92t=
 see a goal/milestone listed for an extension to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">or replacement for RFC 4170.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">I=92d prefer to see a much shor=
ter more focused draft charter.&nbsp; There=92s a<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">bunch of background material th=
at does not seem crucial to the charter,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">starting w/paragraphs 2 and 3.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black">Thanks,<br>
--David</span><span lang=3D"EN-US" style=3D"font-family:&quot;Courier New&q=
uot;;color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;color:black"><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=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> tsv-area [</span><a href=3D"mailto:tsv-area-bounces@i=
etf.org"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;T=
ahoma&quot;,&quot;sans-serif&quot;">mailto:tsv-area-bounces@ietf.org</span>=
</a><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma=
&quot;,&quot;sans-serif&quot;">]
<b>On Behalf Of </b>Jose Saldana<br>
<b>Sent:</b> Friday, December 20, 2013 4:26 AM<br>
<b>To:</b> </span><a href=3D"mailto:tcmtf@ietf.org"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quo=
t;">tcmtf@ietf.org</span></a><span lang=3D"EN-US" style=3D"font-size:10.0pt=
;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">;
</span><a href=3D"mailto:tsv-area@ietf.org"><span lang=3D"EN-US" style=3D"f=
ont-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">tsv-=
area@ietf.org</span></a><span lang=3D"EN-US" style=3D"font-size:10.0pt;font=
-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"><br>
<b>Cc:</b> Martin Stiemerling<br>
<b>Subject:</b> TCMTF-Feedback about a possible BoF in London<o:p></o:p></s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi all,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">After the feedback received in =
the BoF in Berlin, we have updated the TCM-TF charter and the two drafts. W=
e have tried to solve all the problems raised during the session.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Our plan is to request a new Bo=
F in London next March, so we would like to know your opinion about these t=
wo questions:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">1. &nbsp;Is the new, reduced sc=
ope of TCM-TF suitable to form a working group?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">2. We would like to kindly ask =
people who think that a TCM-TF Working group should be formed, to come forw=
ard and send an e-mail to the
</span><a href=3D"mailto:tsv-area@ietf.org"><span lang=3D"EN-US">tsv-area@i=
etf.org</span></a><span lang=3D"EN-US"> &nbsp;mailing list stating it.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">This feedback will allow us to =
get a better idea of the convenience of a BoF.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The new charter is here: </span=
><a href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.htm=
l"><span lang=3D"EN-US">http://www.ietf.org/mail-archive/web/tcmtf/current/=
msg00465.html</span></a><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">This is the old one (presented =
in Berlin):
</span><a href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg003=
68.html"><span lang=3D"EN-US">http://www.ietf.org/mail-archive/web/tcmtf/cu=
rrent/msg00368.html</span></a><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">In these links you can see the =
differences between the new versions of the drafts and the old ones:<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraf=
t-saldana-tsvwg-tcmtf-06.txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt"><=
span lang=3D"EN-US">http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvw=
g-tcmtf-06.txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt</span></a><span =
lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><a href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraf=
t-suznjevic-tsvwg-mtd-tcmtf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcm=
tf-01.txt"><span lang=3D"EN-US">http://tools.ietf.org/rfcdiff?url1=3Ddraft-=
suznjevic-tsvwg-mtd-tcmtf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf=
-01.txt</span></a><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The main improvements are:<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">- TCP optimization has been rem=
oved<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">- The classification of the sce=
narios has been refined and improved. Some of them have been removed<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">- A section about energy consum=
ption has been added to the main draft<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">- A reference to the potential =
problem of the MTU and packet loss has been added<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">- The problem of the added dela=
ys is studied in detail in the second draft<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">- The improvements of the chart=
er are summarized here:
</span><a href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg004=
66.html"><span lang=3D"EN-US">http://www.ietf.org/mail-archive/web/tcmtf/cu=
rrent/msg00466.html</span></a><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Best regards,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jose<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</blockquote>
<blockquote type=3D"cite" style=3D"-webkit-text-size-adjust: auto;">
<div></div>
</blockquote>
</body>
</html>

--_000_B180C070CA1647BE9A431F10546426DAhuaweicom_--


From fpb@tid.es  Thu Jan  9 09:50:26 2014
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59BB31AE2B9; Thu,  9 Jan 2014 09:50:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.025
X-Spam-Level: 
X-Spam-Status: No, score=-4.025 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, ONE_TIME=0.714, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iUK2WIdAV5gc; Thu,  9 Jan 2014 09:50:19 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 869471ADF6D; Thu,  9 Jan 2014 09:50: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 <0MZ500HNEAVCXV@tid.hi.inet>; Thu, 09 Jan 2014 18:50:00 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id AD.2F.02810.841EEC25; Thu, 09 Jan 2014 18:50: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 <0MZ500HMYAVBXV@tid.hi.inet>; Thu, 09 Jan 2014 18:50:00 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.204]) by EX10-HTCAS7-MAD.hi.inet ([::1]) with mapi id 14.03.0158.001; Thu, 09 Jan 2014 18:49:59 +0100
Date: Thu, 09 Jan 2014 17:49:59 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <B180C070-CA16-47BE-9A43-1F10546426DA@huawei.com>
X-Originating-IP: [10.95.64.115]
To: Jose Saldana <jsaldana@unizar.es>
Message-id: <19613893-ECE3-4CB5-A159-4E9D61788408@tid.es>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_g8g+2DCVqy5h+Mk75LOgvw)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] TCMTF-Feedback about a possible BoF in London
Thread-index: Ac79ZUO9+o1eWvDOTZW4bKGOX0YCWwLjYMDQAPUFvwAAAVukgAAjn8+A
X-AuditID: 0a5f4e69-b7f9b8e000000afa-e0-52cee148b833
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGIsWRmVeSWpSXmKPExsXCFe9nqOvx8FyQwbbvvBa7Pm9gtFjwZjGz A5PHkiU/mQIYo7hsUlJzMstSi/TtErgyVix8yF7w7xFTxbs7QQ2M63cwdTFycEgImEg865To YuQEMsUkLtxbzwZiCwlsY5R4eFMAwn7KKLFlh1EXIxeQPZNRovf4dSaQBIuAqsSk5Q+ZQWw2 AS2J03dXsYDYwgJOEsseP2ABmc8pYCfxb0YpxHwFiT/nHoOViAC1Lj37mwlkJrPAR0aJ/rPX GUESvAKWErt2vWGCsAUlfky+B9bALBAtcWX6NChbXKK59SaYzSggK/Fu/nxWiKHOEicPvmEG 2Ssi4CZx/rc5xF4BiSV7zjND2KISLx//Y4X45TajxO7p75knMIrNQrJuFpJ1s5Csg7ANJN6f m88MYWtLLFv4GsrWl9j45SwjhG0msa1zB4qaBYwcqxjFipOKMtMzSnITM3PSDYz0MjL1MvNS SzYxQuIycwfj8p0qhxgFOBiVeHhXFJ8NEmJNLCuuzD3EKMHBrCTCu+biuSAh3pTEyqrUovz4 otKc1OJDjEwcnFINjHZek58LnHU+pClq+C/6+JbA8m+vzGaKKTXMWVB3pVzPqdC1+PRUPi6x v/+1V4TsPrYnwWNJjcu7AM4nh2RXz/Vu/8C+gsnrkkTkwqQvt+Ovx+m+DG8s1gm5/71Q0P/W b+Xmjw3VfxYmeUzb42QT9fu9+THp36ue3a0QnHOdd0LSlBdJhxcIVyixFGckGmoxFxUnAgC/ rr2uqQIAAA==
References: <00c401cefd65$6e8ef570$4bace050$@unizar.es> <8D3D17ACE214DC429325B2B98F3AE712026EF2FF8F@MX15A.corp.emc.com> <004701cf0ccf$4d5826a0$e80873e0$@unizar.es> <B180C070-CA16-47BE-9A43-1F10546426DA@huawei.com>
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "Black, David" <david.black@emc.com>, "tsv-area@ietf.org" <tsv-area@ietf.org>, Luigi Iannone <ggx@gigix.net>, Martin Stiemerling <mls.ietf@googlemail.com>
Subject: Re: [tcmtf] TCMTF-Feedback about a possible BoF in London
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Jan 2014 17:50:26 -0000

--Boundary_(ID_g8g+2DCVqy5h+Mk75LOgvw)
Content-type: text/plain; charset=Windows-1252
Content-transfer-encoding: quoted-printable

Hi all,

Just to say that I also completely support the creation of the WG. There is=
 no doubt that network protocols have evolved, and not always as we thought=
, and TCRTP needs to be wider.

Regards,
Fernando


On 09/01/2014, at 01:49, Tina TSOU <Tina.Tsou.Zouting@huawei.com<mailto:Tin=
a.Tsou.Zouting@huawei.com>> wrote:

Dear all,
I'm in favor of having a BoF in London, as the following problem statement =
seems valid and needs protocol work in IETF.
---
In addition to VoIP, in the last years we are witnessing the raise of new r=
eal-time services e.g. videoconferencing, telemedicine, video vigilance, on=
line gaming, etc.

Due to the need of interactivity, many of these services use small packets =
(some tens of bytes), since they have to send frequent updates between the =
extremes of the communication. Their small data payloads incur significant =
overhead, and it becomes even higher when IPv6 is used, since the basic IPv=
6 header is twice the size of the IPv4 one.

In the moments or places where network capacity gets scarce, allocating mor=
e bandwidth is a possible solution, but it implies a recurring cost. Howeve=
r, the inclusion of a pair of boxes able to optimize the traffic (reducing =
bandwidth and packets per second) when/where required is a one-time investm=
ent. We can do these three things:

a) header compression algorithms (e.g. ROHC) can be used for reducing the o=
verhead of each flow;
b) at the same time, tunneling can be used in order to allow the header-com=
pressed packets to travel end-to-end
c) compressed packets belonging to different flows can be multiplexed toget=
her, in order to share the tunnel overhead.

These emerging real-time services which use bare UDP instead of UDP/RTP hav=
e become popular. In addition, a significant effort has been devoted to the=
 deployment of new header compression methods with improved robustness (ROH=
C). So there is a need of widening the scope of RFC4170 in order to conside=
r these new header compression methods, and also UDP in addition to UDP/RTP=
.

As a result, the next objectives can be achieved:

* Significant bandwidth reductions (as an example, bandwidth savings of 55%=
 can be obtained for VoIP if IPv4 is used, and 65% using IPv6. For certain =
online games, 33% of the bandwidth can be saved for IPv4, and 55% when usin=
g IPv6).

* A reduction of the amount of packets per second managed by the network. A=
 reduction factor of 10 or 20 can easily be achieved. This can be translate=
d into smaller processing delays and energy savings in intermediate routers=
.
---

Thank you,
Tina

On Jan 8, 2014, at 4:11 PM, "Jose Saldana" <jsaldana@unizar.es<mailto:jsald=
ana@unizar.es>> wrote:

Hi all.

First of all, thanks to David and Luigi for their valuable comments.

I will wait for a while in order to include David=92s comments (perhaps som=
e other people has more suggestions).

These are the improvements of version 10 with respect to v9 (http://www.iet=
f.org/mail-archive/web/tcmtf/current/msg00486.html)

- I have shortened paragraph 1.
- I have shortened and merged paragraphs 2 and 3.
- I have moved paragraph 4 to the third place, in order to set clearer what=
 we want: replacing RFC4170 with a widened proposal. As David suggested, I =
have also shortened the text and it is now more straightforward.
- I have clearly stated which protocols will be used on each layer. The neg=
otiation mechanism is still necessary, since different options are consider=
ed e.g. for header compression. The one to be used will depend on the scena=
rio and the processing capacity of the two optimizers.
- I have significantly shortened the description of the scenarios.
- I have removed paragraph 6, which included the savings figures.
- I have included the replacement of RFC4170 in the first milestone.

Thanks!

Jose

De: Black, David [mailto:david.black@emc.com]
Enviado el: s=E1bado, 04 de enero de 2014 4:05
Para: Jose Saldana; tcmtf@ietf.org<mailto:tcmtf@ietf.org>; tsv-area@ietf.or=
g<mailto:tsv-area@ietf.org>
CC: Martin Stiemerling; Black, David
Asunto: RE: TCMTF-Feedback about a possible BoF in London

A second BoF has the explicit goal of forming a WG, as a third BoF
is not permitted.  In that regard, the new charter seems long and
somewhat lacking in focus.  Two key things I look for in a proposed
charter are what problem (or problems) the proposed WG is looking to
solve and an initial approach to the problem or problems.

In the new draft charter, the problem statement appears to be in
paragraph 4 with paragraph 1 providing important background.  The
focus of the work appears to be on extending TCRTP (RFC 4170) to
UDP and to include new compression protocols.  In contrast, I have
a hard time discerning the initial approach from the new draft charter.

In light of this, there are a few things that I wish the new
draft charter had definitive proposals for:

      a) Whether to replace RFC 4170 vs. write a new RFC (could be
            UDP-only or UDP + RTP/UDP) as a complement to RFC 4170.
      b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC (RFC 2507 ?).
            Non-use of ECRTP would be a major change to 4170, and I
wonder about IPHC, as opposed to the ROHCv2 profiles.
      c) Analogies to b) for the Mux and Tunnel layers of the stack.

Overall, it looks like the first task of the WG is to select the protocol
stack to standardize - I have misgivings about that, and would prefer to
see a concrete proposal in a crisp charter that ran along the following
lines, naming the protocols to be used:

1) RFC 4170 does X, and needs the following changes/additions: X, Y, Z.
2) The WG will replace RFC 4170 with a new RFC that contains: A, B, C.

A specific proposal or proposals for the protocol stack or stacks
would also narrow the scope of item 9 in the charter on the negotiation
mechanism.  I also don=92t see a goal/milestone listed for an extension to
or replacement for RFC 4170.

I=92d prefer to see a much shorter more focused draft charter.  There=92s a
bunch of background material that does not seem crucial to the charter,
starting w/paragraphs 2 and 3.

Thanks,
--David

From: tsv-area [mailto:tsv-area-bounces@ietf.org] On Behalf Of Jose Saldana
Sent: Friday, December 20, 2013 4:26 AM
To: tcmtf@ietf.org<mailto:tcmtf@ietf.org>; tsv-area@ietf.org<mailto:tsv-are=
a@ietf.org>
Cc: Martin Stiemerling
Subject: TCMTF-Feedback about a possible BoF in London

Hi all,

After the feedback received in the BoF in Berlin, we have updated the TCM-T=
F charter and the two drafts. We have tried to solve all the problems raise=
d during the session.

Our plan is to request a new BoF in London next March, so we would like to =
know your opinion about these two questions:


1.  Is the new, reduced scope of TCM-TF suitable to form a working group?


2. We would like to kindly ask people who think that a TCM-TF Working group=
 should be formed, to come forward and send an e-mail to the tsv-area@ietf.=
org<mailto:tsv-area@ietf.org>  mailing list stating it.


This feedback will allow us to get a better idea of the convenience of a Bo=
F.

The new charter is here: http://www.ietf.org/mail-archive/web/tcmtf/current=
/msg00465.html
This is the old one (presented in Berlin): http://www.ietf.org/mail-archive=
/web/tcmtf/current/msg00368.html

In these links you can see the differences between the new versions of the =
drafts and the old ones:
http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&url2=
=3Ddraft-saldana-tsvwg-tcmtf-05.txt
http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.txt=
&url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt


The main improvements are:

- TCP optimization has been removed
- The classification of the scenarios has been refined and improved. Some o=
f them have been removed
- A section about energy consumption has been added to the main draft
- A reference to the potential problem of the MTU and packet loss has been =
added
- The problem of the added delays is studied in detail in the second draft

- The improvements of the charter are summarized here: http://www.ietf.org/=
mail-archive/web/tcmtf/current/msg00466.html


Best regards,

Jose

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


________________________________

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

--Boundary_(ID_g8g+2DCVqy5h+Mk75LOgvw)
Content-id: <E019B84AAF282E4A812AAB1EDDD48823@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">
Hi all,
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Just t=
o say that I also completely support the creation of the WG. There is no do=
ubt that network protocols have evolved, and not always as we thought, and =
TCRTP needs to be wider.<br>
<div>
<div>
<div style=3D"color:rgb(0,0,0); letter-spacing:normal; orphans:auto; text-a=
lign:start; text-indent:0px; text-transform:none; white-space:normal; widow=
s:auto; word-spacing:0px; word-wrap:break-word">
<div style=3D"color:rgb(0,0,0); font-family:Helvetica; font-size:12px; font=
-style:normal; font-variant:normal; font-weight:normal; letter-spacing:norm=
al; line-height:normal; orphans:auto; text-align:start; text-indent:0px; te=
xt-transform:none; white-space:normal; widows:auto; word-spacing:0px; margi=
n:0cm 0cm 0.0001pt">
<br class=3D"Apple-interchange-newline">
Regards,
<div>Fernando</div>
<br>
</div>
</div>
</div>
<br>
<div>
<div>On 09/01/2014, at 01:49, Tina TSOU &lt;<a href=3D"mailto:Tina.Tsou.Zou=
ting@huawei.com">Tina.Tsou.Zouting@huawei.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div dir=3D"auto" style=3D"font-family:Helvetica; font-size:12px; font-styl=
e:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; l=
ine-height:normal; orphans:auto; text-align:start; text-indent:0px; text-tr=
ansform:none; white-space:normal; widows:auto; word-spacing:0px">
<div><span style=3D"font-size:13pt">Dear all,</span></div>
<div>I'm in favor of having a BoF in London, as the following problem state=
ment seems valid and needs protocol work in IETF.</div>
<div>---</div>
<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 face=3D"UICTFontTextStyleBody" size=
=3D"3">In addition to VoIP, in the last years we are witnessing the raise o=
f new real-time services e.g. videoconferencing, telemedicine, video vigila=
nce, online gaming, etc.</font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; fo=
nt-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">&nbsp;</font></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">Due to the need of interactivity, many of these services use small p=
ackets (some tens of bytes), since they have to&nbsp;</font></span><span st=
yle=3D"font-family:UICTFontTextStyleBody; font-size:12px">send
 frequent updates between the extremes of the communication. Their small da=
ta payloads incur significant overhead, and it becomes even higher when IPv=
6 is used, since the basic IPv6 header is twice the size of the IPv4 one.</=
span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; fo=
nt-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">&nbsp;</font></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">In the moments or places where network capacity gets scarce, allocat=
ing more bandwidth is a possible solution, but it implies a recurring cost.=
 However, the inclusion of a pair of boxes
 able to optimize the traffic (reducing bandwidth and packets per second) w=
hen/where required is a one-time investment. We can do these three things:<=
/font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; fo=
nt-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">&nbsp;</font></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">a) header compression algorithms (e.g. ROHC) can be used for reducin=
g the overhead of each flow;</font></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 face=3D"UICTFontTextStyleBody" size=
=3D"3">b) at the same time, tunneling can be used in order to allow the hea=
der-compressed packets to travel end-to-end</font></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 face=3D"UICTFontTextStyleBody" size=
=3D"3">c) compressed packets belonging to different flows can be multiplexe=
d together, in order to share the tunnel overhead.</font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; fo=
nt-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">&nbsp;</font></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">These emerging real-time services which use bare UDP instead of UDP/=
RTP have become popular. In addition, a significant&nbsp;</font></span><spa=
n style=3D"font-family:UICTFontTextStyleBody; font-size:12px">effort
 has been devoted to the deployment of new header compression methods with =
improved robustness (ROHC). So there is a need of widening the scope of RFC=
4170 in order to consider these new header compression methods, and also UD=
P in addition to UDP/RTP.</span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; fo=
nt-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">&nbsp;</font></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">As a result, the next objectives can be achieved:</font></span></div=
>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; fo=
nt-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">&nbsp;</font></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">* Significant bandwidth reductions (as an example, bandwidth savings=
 of 55% can be obtained for VoIP if IPv4 is used, and 65% using IPv6. For c=
ertain online games, 33% of the bandwidth
 can be saved for IPv4, and 55% when using IPv6).</font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; fo=
nt-family:Calibri,sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">&nbsp;</font></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US" style=3D""><font face=3D"UICTFontTextStyleBody" size=
=3D"3">* A reduction of the amount of packets per second managed by the net=
work. A reduction factor of 10 or 20 can easily be achieved. This can be tr=
anslated into smaller processing delays and
 energy savings in intermediate routers.</font></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
---</div>
<div><br>
</div>
<div>Thank you,</div>
<div>Tina</div>
</div>
<div><br>
On Jan 8, 2014, at 4:11 PM, &quot;Jose Saldana&quot; &lt;<a href=3D"mailto:=
jsaldana@unizar.es" style=3D"color:purple; text-decoration:underline">jsald=
ana@unizar.es</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div class=3D"WordSection1" style=3D"">
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US" style=3D"color:rgb(31,73,125)">Hi all.</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"color:rgb(31,73,125)">&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"color:rgb(31,73,125)">First of all, thanks to=
 David and Luigi for their valuable comments.</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"color:rgb(31,73,125)">&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"color:rgb(31,73,125)">I will wait for a while=
 in order to include David=92s comments (perhaps some other people has more=
 suggestions).</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"color:rgb(31,73,125)">&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"color:rgb(31,73,125)">These are the improveme=
nts of version 10 with respect to v9 (</span><a href=3D"http://www.ietf.org=
/mail-archive/web/tcmtf/current/msg00486.html" style=3D"color:purple; text-=
decoration:underline"><span lang=3D"EN-US">http://www.ietf.org/mail-archive=
/web/tcmtf/current/msg00486.html</span></a><span lang=3D"EN-US">)</span><sp=
an lang=3D"EN-US" style=3D"color:rgb(31,73,125)"></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"color:rgb(31,73,125)">&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"color:rgb(31,73,125)">- I have shortened para=
graph 1.</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"color:rgb(31,73,125)">- I have shortened and =
merged paragraphs 2 and 3.</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"color:rgb(31,73,125)">- I have moved paragrap=
h 4 to the third place, in order to set clearer what we want: replacing RFC=
4170 with a widened proposal. As David suggested, I have also shortened the=
 text and it is now more straightforward.</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"color:rgb(31,73,125)">- I have clearly stated=
 which protocols will be used on each layer. The negotiation mechanism is s=
till necessary, since different options are considered e.g. for header comp=
ression. The one to be used will depend
 on the scenario and the processing capacity of the two optimizers.</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"color:rgb(31,73,125)">- I have significantly =
shortened the description of the scenarios.</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"color:rgb(31,73,125)">- I have removed paragr=
aph 6, which included the savings figures.</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"color:rgb(31,73,125)">- I have included the r=
eplacement of RFC4170 in the first milestone.</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"color:rgb(31,73,125)">&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"color:rgb(31,73,125)">Thanks!</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"color:rgb(31,73,125)">&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"color:rgb(31,73,125)">Jose</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"color:rgb(31,73,125)">&nbsp;</span></div>
<div>
<div style=3D"border-style:solid none none; border-top-color:rgb(181,196,22=
3); border-top-width:1pt; padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<b><span lang=3D"EN-US" style=3D"font-size:10pt; font-family:Tahoma,sans-se=
rif">De:</span></b><span lang=3D"EN-US" style=3D"font-size:10pt; font-famil=
y:Tahoma,sans-serif"><span class=3D"Apple-converted-space">&nbsp;</span>Bla=
ck, David [</span><span style=3D"font-size:10pt; font-family:Tahoma,sans-se=
rif"><a href=3D"mailto:david.black@emc.com" style=3D"color:purple; text-dec=
oration:underline"><span lang=3D"EN-US">mailto:david.black@emc.com</span></=
a></span><span lang=3D"EN-US" style=3D"font-size:10pt; font-family:Tahoma,s=
ans-serif">]<span class=3D"Apple-converted-space">&nbsp;</span><br>
<b>Enviado el:</b><span class=3D"Apple-converted-space">&nbsp;</span>s=E1ba=
do, 04 de enero de 2014 4:05<br>
<b>Para:</b><span class=3D"Apple-converted-space">&nbsp;</span>Jose Saldana=
;<span class=3D"Apple-converted-space">&nbsp;</span></span><span style=3D"f=
ont-size:10pt; font-family:Tahoma,sans-serif"><a href=3D"mailto:tcmtf@ietf.=
org" style=3D"color:purple; text-decoration:underline"><span lang=3D"EN-US"=
>tcmtf@ietf.org</span></a></span><span lang=3D"EN-US" style=3D"font-size:10=
pt; font-family:Tahoma,sans-serif">;<span class=3D"Apple-converted-space">&=
nbsp;</span></span><span style=3D"font-size:10pt; font-family:Tahoma,sans-s=
erif"><a href=3D"mailto:tsv-area@ietf.org" style=3D"color:purple; text-deco=
ration:underline"><span lang=3D"EN-US">tsv-area@ietf.org</span></a></span><=
span lang=3D"EN-US" style=3D"font-size:10pt; font-family:Tahoma,sans-serif"=
><br>
<b>CC:</b><span class=3D"Apple-converted-space">&nbsp;</span>Martin Stiemer=
ling; Black, David<br>
<b>Asunto:</b><span class=3D"Apple-converted-space">&nbsp;</span>RE: TCMTF-=
Feedback about a possible BoF in London</span></div>
</div>
</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:'Courier New'">A =
second BoF has the explicit goal of forming a WG, as a third BoF</span></di=
v>
<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:'Courier New'">is=
 not permitted.&nbsp; In that regard, the new charter seems long and</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:'Courier New'">so=
mewhat lacking in focus.&nbsp; Two key things I look for in a proposed</spa=
n></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:'Courier New'">ch=
arter are what problem (or problems) the proposed WG is looking to</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:'Courier New'">so=
lve and an initial approach to the problem or problems.</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:'Courier New'">&n=
bsp;</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:'Courier New'">In=
 the new draft charter, the problem statement appears to be in</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:'Courier New'">pa=
ragraph 4 with paragraph 1 providing important background.&nbsp; The</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:'Courier New'">fo=
cus of the work appears to be on extending TCRTP (RFC 4170) to</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:'Courier New'">UD=
P and to include new compression protocols.&nbsp; In contrast, I have</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:'Courier New'">a =
hard time discerning the initial approach from the new draft charter.</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:'Courier New'">&n=
bsp;</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:'Courier New'">In=
 light of this, there are a few things that I wish the new</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:'Courier New'">dr=
aft charter had definitive proposals for:</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:'Courier New'">&n=
bsp;</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:'Courier New'">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Whether to replace RFC 4170 vs. write a new=
 RFC (could be</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:'Courier New'">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UDP-only o=
r UDP &#43; RTP/UDP) as a complement to RFC 4170.</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:'Courier New'">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; b) Whether to use ECRTP, ROHCv2 (RFC 5225) and=
/or IPHC (RFC 2507 ?).</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:'Courier New'">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Non-use of=
 ECRTP would be a major change to 4170, and I</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt 36pt; font-size:11pt; font-family:Cal=
ibri,sans-serif; text-indent:36pt">
<span lang=3D"EN-US" style=3D"font-size:10pt; font-family:'Courier New'">wo=
nder about IPHC, as opposed to the ROHCv2 profiles.</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:'Courier New'">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; c) Analogies to b) for the Mux and Tunnel laye=
rs of the stack.</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:'Courier New'">&n=
bsp;</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:'Courier New'">Ov=
erall, it looks like the first task of the WG is to select the protocol</sp=
an></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:'Courier New'">st=
ack to standardize - I have misgivings about that, and would prefer to</spa=
n></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:'Courier New'">se=
e a concrete proposal in a crisp charter that ran along the following</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:'Courier New'">li=
nes, naming the protocols to be used:</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:'Courier New'">&n=
bsp;</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:'Courier New'">1)=
 RFC 4170 does X, and needs the following changes/additions: X, Y, Z.</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:'Courier New'">2)=
 The WG will replace RFC 4170 with a new RFC that contains: A, B, C.</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:'Courier New'">&n=
bsp;</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:'Courier New'">A =
specific proposal or proposals for the protocol stack or stacks</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:'Courier New'">wo=
uld also narrow the scope of item 9 in the charter on the negotiation</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:'Courier New'">me=
chanism.&nbsp; I also don=92t see a goal/milestone listed for an extension =
to</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:'Courier New'">or=
 replacement for RFC 4170.</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:'Courier New'">&n=
bsp;</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:'Courier New'">I=
=92d prefer to see a much shorter more focused draft charter.&nbsp; There=
=92s a</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:'Courier New'">bu=
nch of background material that does not seem crucial to the charter,</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:'Courier New'">st=
arting w/paragraphs 2 and 3.</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:'Courier New'">&n=
bsp;</span></div>
<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:'Courier New'">Th=
anks,<br>
--David</span><span lang=3D"EN-US" style=3D"font-family:'Courier New'"></sp=
an></div>
</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:'Courier New'">&n=
bsp;</span></div>
<div style=3D"border-style:none none none solid; border-left-color:blue; bo=
rder-left-width:1.5pt; padding:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-style:solid none none; border-top-color:rgb(181,196,22=
3); border-top-width:1pt; padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<b><span lang=3D"EN-US" style=3D"font-size:10pt; font-family:Tahoma,sans-se=
rif">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10pt; font-fam=
ily:Tahoma,sans-serif"><span class=3D"Apple-converted-space">&nbsp;</span>t=
sv-area [</span><a href=3D"mailto:tsv-area-bounces@ietf.org" style=3D"color=
:purple; text-decoration:underline"><span lang=3D"EN-US" style=3D"font-size=
:10pt; font-family:Tahoma,sans-serif">mailto:tsv-area-bounces@ietf.org</spa=
n></a><span lang=3D"EN-US" style=3D"font-size:10pt; font-family:Tahoma,sans=
-serif">]<span class=3D"Apple-converted-space">&nbsp;</span><b>On
 Behalf Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Jose Salda=
na<br>
<b>Sent:</b><span class=3D"Apple-converted-space">&nbsp;</span>Friday, Dece=
mber 20, 2013 4:26 AM<br>
<b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span></span><a href=
=3D"mailto:tcmtf@ietf.org" style=3D"color:purple; text-decoration:underline=
"><span lang=3D"EN-US" style=3D"font-size:10pt; font-family:Tahoma,sans-ser=
if">tcmtf@ietf.org</span></a><span lang=3D"EN-US" style=3D"font-size:10pt; =
font-family:Tahoma,sans-serif">;<span class=3D"Apple-converted-space">&nbsp=
;</span></span><a href=3D"mailto:tsv-area@ietf.org" style=3D"color:purple; =
text-decoration:underline"><span lang=3D"EN-US" style=3D"font-size:10pt; fo=
nt-family:Tahoma,sans-serif">tsv-area@ietf.org</span></a><span lang=3D"EN-U=
S" style=3D"font-size:10pt; font-family:Tahoma,sans-serif"><br>
<b>Cc:</b><span class=3D"Apple-converted-space">&nbsp;</span>Martin Stiemer=
ling<br>
<b>Subject:</b><span class=3D"Apple-converted-space">&nbsp;</span>TCMTF-Fee=
dback about a possible BoF in London</span></div>
</div>
</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">Hi all,</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 the feedback received in the BoF in Berlin, we h=
ave updated the TCM-TF charter and the two drafts. We have tried to solve a=
ll the problems raised during the session.</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">Our plan is to request a new BoF in London next March,=
 so we would like to know your opinion about these two questions:</span></d=
iv>
<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">&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. &nbsp;Is the new, reduced scope of TCM-TF suitable =
to form a working group?</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">&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. We would like to kindly ask people who think that a=
 TCM-TF Working group should be formed, to come forward and send an e-mail =
to the<span class=3D"Apple-converted-space">&nbsp;</span></span><a href=3D"=
mailto:tsv-area@ietf.org" style=3D"color:purple; text-decoration:underline"=
><span lang=3D"EN-US">tsv-area@ietf.org</span></a><span lang=3D"EN-US"><spa=
n class=3D"Apple-converted-space">&nbsp;</span>&nbsp;mailing
 list stating it.</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">&nbsp;</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US">This feedback will allow us to get a better idea of th=
e convenience of a BoF.</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">The new charter is here:<span class=3D"Apple-converted=
-space">&nbsp;</span></span><a href=3D"http://www.ietf.org/mail-archive/web=
/tcmtf/current/msg00465.html" style=3D"color:purple; text-decoration:underl=
ine"><span lang=3D"EN-US">http://www.ietf.org/mail-archive/web/tcmtf/curren=
t/msg00465.html</span></a><span lang=3D"EN-US"></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US">This is the old one (presented in Berlin):<span class=
=3D"Apple-converted-space">&nbsp;</span></span><a href=3D"http://www.ietf.o=
rg/mail-archive/web/tcmtf/current/msg00368.html" style=3D"color:purple; tex=
t-decoration:underline"><span lang=3D"EN-US">http://www.ietf.org/mail-archi=
ve/web/tcmtf/current/msg00368.html</span></a><span lang=3D"EN-US"></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">In these links you can see the differences between the=
 new versions of the drafts and the old ones:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<a href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-0=
6.txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt" style=3D"color:purple; t=
ext-decoration:underline"><span lang=3D"EN-US">http://tools.ietf.org/rfcdif=
f?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&amp;url2=3Ddraft-saldana-tsvwg-tc=
mtf-05.txt</span></a><span lang=3D"EN-US"></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<a href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-t=
cmtf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt" style=3D"col=
or:purple; text-decoration:underline"><span lang=3D"EN-US">http://tools.iet=
f.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.txt&amp;url2=3Ddraf=
t-suznjevic-tsvwg-mtd-tcmtf-01.txt</span></a><span lang=3D"EN-US"></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">&nbsp;</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US">The main improvements are:</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">- TCP optimization has been removed</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US">- The classification of the scenarios has been refined=
 and improved. Some of them have been removed</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US">- A section about energy consumption has been added to=
 the main draft</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US">- A reference to the potential problem of the MTU and =
packet loss has been added</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US">- The problem of the added delays is studied in detail=
 in the second draft</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">- The improvements of the charter are summarized here:=
<span class=3D"Apple-converted-space">&nbsp;</span></span><a href=3D"http:/=
/www.ietf.org/mail-archive/web/tcmtf/current/msg00466.html" style=3D"color:=
purple; text-decoration:underline"><span lang=3D"EN-US">http://www.ietf.org=
/mail-archive/web/tcmtf/current/msg00466.html</span></a><span lang=3D"EN-US=
"></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">&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,</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt; font-size:11pt; font-family:Calibri,=
sans-serif">
<span lang=3D"EN-US">Jose</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>
<blockquote type=3D"cite">
<div></div>
</blockquote>
_______________________________________________<br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org" style=3D"color:purple; text-decoration:un=
derline">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color:purp=
le; text-decoration:underline">https://www.ietf.org/mailman/listinfo/tcmtf<=
/a></div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_g8g+2DCVqy5h+Mk75LOgvw)--


From wes@mti-systems.com  Thu Jan  9 10:04:02 2014
Return-Path: <wes@mti-systems.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD0111AE057 for <tcmtf@ietfa.amsl.com>; Thu,  9 Jan 2014 10:04:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YY2rJNHTQ5l8 for <tcmtf@ietfa.amsl.com>; Thu,  9 Jan 2014 10:04:01 -0800 (PST)
Received: from atl4mhob08.myregisteredsite.com (atl4mhob08.myregisteredsite.com [209.17.115.46]) by ietfa.amsl.com (Postfix) with ESMTP id 1F5D41AE04C for <tcmtf@ietf.org>; Thu,  9 Jan 2014 10:04:01 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.203]) by atl4mhob08.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s09I3o19005537 for <tcmtf@ietf.org>; Thu, 9 Jan 2014 13:03:50 -0500
Received: (qmail 8367 invoked by uid 0); 9 Jan 2014 18:03:50 -0000
X-TCPREMOTEIP: 107.46.60.198
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@107.46.60.198) by 0 with ESMTPA; 9 Jan 2014 18:03:49 -0000
Message-ID: <52CEE47E.5020804@mti-systems.com>
Date: Thu, 09 Jan 2014 13:03:42 -0500
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>, Jose Saldana <jsaldana@unizar.es>
References: <00c401cefd65$6e8ef570$4bace050$@unizar.es> <8D3D17ACE214DC429325B2B98F3AE712026EF2FF8F@MX15A.corp.emc.com>, <004701cf0ccf$4d5826a0$e80873e0$@unizar.es> <B180C070-CA16-47BE-9A43-1F10546426DA@huawei.com>
In-Reply-To: <B180C070-CA16-47BE-9A43-1F10546426DA@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, Luigi Iannone <ggx@gigix.net>, "Black, David" <david.black@emc.com>, "tsv-area@ietf.org" <tsv-area@ietf.org>, Martin Stiemerling <mls.ietf@googlemail.com>
Subject: Re: [tcmtf] TCMTF-Feedback about a possible BoF in London
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Jan 2014 18:04:02 -0000

On 1/8/2014 7:49 PM, Tina TSOU wrote:
> Dear all,
> I'm in favor of having a BoF in London, as the following problem
> statement seems valid and needs protocol work in IETF.
> ...

I'm in agreement as well.  Parts of the problem statement and the
scope of the work might still be tweakable, but I think that
overall there is important work for the IETF to do in this area.

Due to the things Tina described very well, there will be (and are)
products available that attempt to optimize traffic in poorly
documented and often poorly conceived ways.  These can do more harm
and have other mysterious effects on traffic than whatever this
working group would create, since it would provide open specifications
that could be developed and tested against the concerns of relevant
layers and other IETF protocols, and problems and concerns could be
addressed.

If there are people willing to write the specs *and* people are
also able to express interest in writing/deploying/selling code and
products that use those specs, then we should certainly be doing
this work in the IETF.

This will allow:
- multiple vendor boxes to interoperate on different sides of a
  challenged network/link (currently this is beyond the state of
  the art!)
- simplified/standardized management of such boxes
- well-understood behavior profiles of such middleboxes and their
  protocols algorithms

If the IETF does not do this work, then I don't believe any of those
three benefits/results are likely at all, and the (poor) status quo
will continue.

-- 
Wes Eddy
MTI Systems

From jsaldana@unizar.es  Wed Jan 15 01:47:05 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97C5F1ADBD1; Wed, 15 Jan 2014 01:47:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.024
X-Spam-Level: 
X-Spam-Status: No, score=-4.024 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, ONE_TIME=0.714, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nGYqbEJXm0X6; Wed, 15 Jan 2014 01:47:02 -0800 (PST)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB541ADF88; Wed, 15 Jan 2014 01:47:01 -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 s0F9kfZJ011143; Wed, 15 Jan 2014 10:46:41 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tsv-area@ietf.org>, <tcmtf@ietf.org>
Date: Wed, 15 Jan 2014 10:46:52 +0100
Message-ID: <0a5c01cf11d6$b7f08320$27d18960$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0A5D_01CF11DF.19B64AB0"
X-Mailer: Microsoft Outlook 14.0
Content-language: es
Thread-index: Ac8R1lQ09Tz0qQTzQqu6k/HdxtLbAg==
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Martin Stiemerling <mls.ietf@gmail.com>
Subject: [tcmtf] Next version (v11) of TCM-TF charter draft
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 15 Jan 2014 09:47:05 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0A5D_01CF11DF.19B64AB0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

According to the comments of David, I have moved the signaling sentences
from 5 to 7, and merged the rest of 5 with 6. So this is the new version
(Thanks again, David!):
 
Tunneling Compressed Multiplexed Traffic Flows (TCM-TF) charter draft v11
 
Description of Working Group
 
1. RFC4170 (TCRTP) defines a method for grouping packets when a number of
UDP/RTP VoIP flows share a common path, considering three different layers:
ECRTP header compression; PPPMux multiplexing; L2TPv3 tunneling. TCRTP
optimizes the traffic, increasing the bandwidth efficiency of VoIP and
reduces the amount of packets per second at the same time.
2. However, in the last years, emerging real-time services which use bare
UDP instead of UDP/RTP have become popular. Due to the need of
interactivity, many of these services use small packets (some tens of
bytes). Some other services also send small packets, but they are not
delay-sensitive (e.g., instant messaging, m2m packets in sensor networks).
In addition, a significant effort has been devoted to the deployment of new
header compression methods with improved robustness (ROHC).
3. So there is a need of replacing RFC4170 with an extended solution able to
optimize these new flows, also using improved compression methods. The same
structure of three layers will be considered:
* Header compression: different protocols can be used: no compression,
ECRTP, IPHC and ROHC.
* Multiplexing: PPPMux will be the option.
* Tunneling: the options in this layer are L2TP, GRE and MPLS.
4. New scenarios where bandwidth savings are desirable have been identified,
in addition to those considered in RFC4170. In these scenarios, there are
moments or places where network capacity gets scarce, so allocating more
bandwidth is a possible solution, but it implies a recurring cost. However,
the inclusion of a pair of boxes able to optimize the traffic when/where
required is a one-time investment. These scenarios can be classified into:
* Multidomain, the TCMT-TF tunnel goes all the way from one network edge to
another, and can therefore cross several domains.
* Single Domain, TCM-TF is only activated inside an ISP, from the edge to
border inside the network operator. 
* Private Solutions. TCM-TF is used to connect private networks
geographically apart (e.g. corporation headquarters and subsidiaries),
without the ISP being aware or having to manage those flows.
* Mixed Scenarios, any combination of the previous ones.
5. A first document (TCM-TF - reference model) will define the different
options which can be used at each layer. It will include a detailed
specification of the scenarios of interest. 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. The impact on other
protocols will also be studied. 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 would be obsoleted.
6. Since standard protocols are being considered at each layer, the
signaling methods of those protocols will be used. Thus, interactions with
the Working Groups and Areas in which these protocols are developed can be
expected. Taking into account that different options will be considered when
a pair of TCM-TF optimizers want to establish a session, they will have
first to negotiate which concrete option would they use in each layer. This
will depend on the protocols that each extreme implements at each level, and
in the scenario. So another document (TCM-TF - negotiation protocol) will
include:
* a mechanism to setup/release a TCM-TF session between an ingress and an
egress-optimizer, also including:
* a negotiation mechanism to decide the options to use at each layer .
7. As a counterpart of the bandwidth saving, TCM-TF may add some delay and
jitter. This is not a problem for the services which are not sensitive to
delay. However, regarding delay-sensitive services, the Working Group will
also develop a document (TCM-TF - recommendations) with useful
recommendations in order to decide which packet flows can or can not be
multiplexed and how. The document will present a list of available traffic
classification methods which can be used for identification of the service
or application to which a particular flow belongs, as well as
recommendations of the maximum delay and jitter to be added depending of the
identified service or application. The eventual impact of multiplexing on
protocol dynamics (e.g. the loss of a multiplexed packet, MTU-related
issues) will also have to be addressed.
8. The working group may identify additional deliverables that are
necessary/useful, e.g., a mechanism for a TCM-ingress optimizer to discover
an egress optimizer, and vice versa. The working group would re-charter to
add them before working on them.
9. Interactions with other Working Groups can be expected, since TCM-TF uses
already defined protocols for compression, multiplexing and tunneling (ROHC,
PPPMux, MPLS, GRE, L2TP). 
 
Goals and Milestones
Specification of TCM-TF reference model and the scenarios of interest. This
would obsolete RFC4170.
Specification of TCM-TF negotiation protocol.
Specification of TCM-TF recommendations of using existing traffic
classification methods, maximum delay and jitter to add, depending on the
service.
 
Current version of Document (TCM-TF - reference model):
 <https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/>
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
 
Current version of Document (TCM-TF - recommendations):
 <http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/>
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
 

------=_NextPart_000_0A5D_01CF11DF.19B64AB0
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=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CF11DF.18A6FD90"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:HyphenationZone>21</w:HyphenationZone>
<w:EnvelopeVis/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>ES</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1107305727 0 0 415 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:"Arial Narrow";
	panose-1:2 11 6 6 2 2 2 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:647 2048 0 0 159 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:windowtext;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Texto sin formato";
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Tabla normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[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 style=3D'tab-interval:35.4pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>According to the comments of David, I =
have moved the signaling sentences from 5 to 7, and merged the rest of 5 =
with 6. So this is the new version (Thanks again, =
David!):<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:14.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
Tunneling Compressed Multiplexed Traffic Flows (TCM-TF) charter draft =
v11<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:14.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'font-size:14.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
Description of Working Group<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
1. RFC4170 (TCRTP) defines a method for grouping packets when a number =
of UDP/RTP VoIP flows share a common path, considering three different =
layers: ECRTP header compression; PPPMux multiplexing; L2TPv3 tunneling. =
TCRTP optimizes the traffic, increasing the bandwidth efficiency of VoIP =
and reduces the amount of packets per second at the same =
time.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
2. However, in the last years, emerging real-time services which use =
bare UDP instead of UDP/RTP have become popular. Due to the need of =
interactivity, many of these services use small packets (some tens of =
bytes). Some other services also send small packets, but they are not =
delay-sensitive (e.g., instant messaging, m2m packets in sensor =
networks). In addition, a significant effort has been devoted to the =
deployment of new header compression methods with improved robustness =
(ROHC).<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
3. So there is a need of replacing RFC4170 with an extended solution =
able to optimize these new flows, also using improved compression =
methods. The same structure of three layers will be =
considered:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
* Header compression: different protocols can be used: no compression, =
ECRTP, IPHC and ROHC.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
* Multiplexing: PPPMux will be the option.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
* Tunneling: the options in this layer are L2TP, GRE and =
MPLS.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
4. New scenarios where bandwidth savings are desirable have been =
identified, in addition to those considered in RFC4170. In these =
scenarios, there are moments or places where network capacity gets =
scarce, so allocating more bandwidth is a possible solution, but it =
implies a recurring cost. However, the inclusion of a pair of boxes able =
to optimize the traffic when/where required is a one-time investment. =
These scenarios can be classified into:<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
* <span class=3DSpellE>Multidomain</span>, the TCMT-TF tunnel goes all =
the way from one network edge to another, and can therefore cross =
several domains.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
* Single Domain, TCM-TF is only activated inside an ISP, from the edge =
to border inside the network operator. <o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
* Private Solutions. TCM-TF is used to connect private networks =
geographically apart (e.g. corporation headquarters and subsidiaries), =
without the ISP being aware or having to manage those =
flows.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
* Mixed Scenarios, any combination of the previous =
ones.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
5. A first document (TCM-TF - reference model) will define the different =
options which can be used at each layer. It will include a detailed =
specification of the scenarios of interest. 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. The impact on =
other protocols will also be studied. 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 would be =
obsoleted.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
6. Since standard protocols are being considered at each layer, the =
signaling methods of those protocols will be used. Thus, interactions =
with the Working Groups and Areas in which these protocols are developed =
can be expected. Taking into account that different options will be =
considered when a pair of TCM-TF optimizers want to establish a session, =
they will have first to negotiate which concrete option would they use =
in each layer. This will depend on the protocols that each extreme =
implements at each level, and in the scenario. So another document =
(TCM-TF - negotiation protocol) will include:<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
* a mechanism to setup/release a TCM-TF session between an ingress and =
an egress-optimizer, also including:<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
* a negotiation mechanism to decide the options to use at each layer =
.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
7. As a counterpart of the bandwidth saving, TCM-TF may add some delay =
and jitter. This is not a problem for the services which are not =
sensitive to delay. However, regarding delay-sensitive services, the =
Working Group will also develop a document (TCM-TF - recommendations) =
with useful recommendations in order to decide which packet flows can or =
<span class=3DSpellE>can not</span> be multiplexed and how. The document =
will present a list of available traffic classification methods which =
can be used for identification of the service or application to which a =
particular flow belongs, as well as recommendations of the maximum delay =
and jitter to be added depending of the identified service or =
application. The eventual impact of multiplexing on protocol dynamics =
(e.g. the loss of a multiplexed packet, MTU-related issues) will also =
have to be addressed.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
8. The working group may identify additional deliverables that are =
necessary/useful, e.g., a mechanism for a TCM-ingress optimizer to =
discover an egress optimizer, and vice versa. The working group would =
re-charter to add them before working on them.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
9. Interactions with other Working Groups can be expected, since TCM-TF =
uses already defined protocols for compression, multiplexing and =
tunneling (ROHC, PPPMux, MPLS, GRE, L2TP). <o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-bottom:6.0pt'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt'><span lang=3DEN-US =
style=3D'font-size:14.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
Goals and Milestones</span><span lang=3DEN-US =
style=3D'font-size:16.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
Specification of TCM-TF reference model and the scenarios of interest. =
This would obsolete RFC4170.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
Specification of TCM-TF negotiation protocol.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:6.0pt;text-align:justify'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
Specification of TCM-TF recommendations of using existing traffic =
classification methods, maximum delay and jitter to add, depending on =
the service.</span><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-bottom:6.0pt'><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:6.0pt'><span lang=3DEN-US =
style=3D'font-size:10.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
Current version of Document (</span><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
TCM-TF - reference model</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
):<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:6.0pt'><a =
href=3D"https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/"><spa=
n lang=3DEN-US =
style=3D'font-size:10.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</span></a><sp=
an lang=3DEN-US =
style=3D'font-size:10.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:6.0pt'><span lang=3DEN-US =
style=3D'font-size:10.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:6.0pt'><span lang=3DEN-US =
style=3D'font-size:10.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
Current version of Document (</span><span lang=3DEN-US =
style=3D'font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
TCM-TF - recommendations</span><span lang=3DEN-US =
style=3D'font-size:10.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
):<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:6.0pt'><a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
><span lang=3DEN-US =
style=3D'font-size:10.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</span></=
a><span lang=3DEN-US =
style=3D'font-size:10.0pt;mso-bidi-font-size:11.0pt;font-family:"Arial =
Narrow","sans-serif";mso-bidi-font-family:Arial;mso-ansi-language:EN-US'>=
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p></div></bod=
y></html>
------=_NextPart_000_0A5D_01CF11DF.19B64AB0--



From jsaldana@unizar.es  Wed Jan 15 07:04:45 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96C191AE38A for <tcmtf@ietfa.amsl.com>; Wed, 15 Jan 2014 07:04:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.038
X-Spam-Level: 
X-Spam-Status: No, score=-2.038 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ya4EBmfeapkD for <tcmtf@ietfa.amsl.com>; Wed, 15 Jan 2014 07:04:43 -0800 (PST)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6661AE389 for <tcmtf@ietf.org>; Wed, 15 Jan 2014 07:04:41 -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 s0FF4RfD021986 for <tcmtf@ietf.org>; Wed, 15 Jan 2014 16:04:27 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 15 Jan 2014 16:04:38 +0100
Message-ID: <0bd101cf1203$1c4353d0$54c9fb70$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0BD2_01CF120B.7E087F20"
X-Mailer: Microsoft Outlook 14.0
Content-language: es
Thread-index: Ac8SAoKfUnlOLNRuRZCBxfcIw+imbA==
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] Emergency networks: can TCM be useful there?
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 15 Jan 2014 15:04:45 -0000

This is a multipart message in MIME format.

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

Hi all,
 
The Government of the USA is developing FirstNet, which will "provide
emergency responders with the first nationwide, high-speed network dedicated
to public safety". http://www.ntia.doc.gov/page/about-firstnet
 
Do you think TCM-TF can be useful in these situations? I mean, during an
emergency the traffic may be dramatically increased, so systems may include
TCM as a possibility to be activated when a traffic rush occurs.
 
Do you think this scenario can be interesting for TCM-TF?
 
Jose

------=_NextPart_000_0BD2_01CF120B.7E087F20
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=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CF120B.7D065160"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:HyphenationZone>21</w:HyphenationZone>
<w:EnvelopeVis/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>ES</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1107305727 0 0 415 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-alt:Calibri;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:windowtext;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Tabla normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[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 style=3D'tab-interval:35.4pt'><div =
class=3DWordSection1><p class=3DMsoNormal>Hi <span =
class=3DSpellE>all</span>,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>The Government of the USA =
is developing <span class=3DSpellE>FirstNet</span>, which will =
&#8220;</span><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white;mso-ansi-language:EN-US'>provide emergency responders =
with the first nationwide, high-speed network dedicated to public =
safety&#8221;. <a =
href=3D"http://www.ntia.doc.gov/page/about-firstnet">http://www.ntia.doc.=
gov/page/about-firstnet</a><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white;mso-ansi-language:EN-US'>Do you think TCM-TF can be =
useful in these situations? I mean, during an emergency the traffic may =
be dramatically increased, so systems may include TCM as a possibility =
to be activated when a traffic rush occurs.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white;mso-ansi-language:EN-US'>Do you think this scenario can =
be interesting for TCM-TF?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt;font-family:"Arial","sans-serif";color:black;ba=
ckground:white;mso-ansi-language:EN-US'>Jose</span><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p></o:p></span></p></div></body></ht=
ml>
------=_NextPart_000_0BD2_01CF120B.7E087F20--


From jsaldana@unizar.es  Fri Jan 17 03:16:22 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35A961ADFE2; Fri, 17 Jan 2014 03:16:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.024
X-Spam-Level: 
X-Spam-Status: No, score=-4.024 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, ONE_TIME=0.714, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aJIL-4QqQe3m; Fri, 17 Jan 2014 03:16:18 -0800 (PST)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 491A61ADFC4; Fri, 17 Jan 2014 03:16:16 -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 s0HBFsqg010380; Fri, 17 Jan 2014 12:15:54 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>, <tsv-area@ietf.org>
Date: Fri, 17 Jan 2014 12:15:57 +0100
Message-ID: <000701cf1375$7ef87ff0$7ce97fd0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0008_01CF137D.E0BEBCB0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8TdVYE9YMe4pjTRem/emPLysEdLg==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] TCM-TF BoF requested for London
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 17 Jan 2014 11:16:22 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0008_01CF137D.E0BEBCB0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi all,
=20
A second BoF with the aim of creating a WG has been requested for =
London. You can find the details here: =
http://trac.tools.ietf.org/bof/trac/wiki#Transport
=20
Best regards,
=20
Jose
*	Long name and abbreviation: Tunneling Compressed Multiplexed Traffic =
Flows (TCMTF)
*	Status: WG Forming, 2nd attempt (1st was IETF-87 in Berlin)
*	Description:
 <http://tools.ietf.org/html/rfc4170> RFC4170 (TCRTP) defines a method =
for grouping packets when a number of UDP/RTP VoIP flows share a common =
path, considering three different layers: ECRTP header compression; =
PPPMux multiplexing; L2TPv3 tunneling. TCRTP optimizes the traffic, =
increasing the bandwidth efficiency of VoIP and reduces the amount of =
packets per second at the same time. However, in the last years, =
emerging real-time services which use bare UDP instead of UDP/RTP have =
become popular. Due to the need of interactivity, many of these services =
use small packets (some tens of bytes). Some other services also send =
small packets, but they are not delay-sensitive (e.g., instant =
messaging, m2m packets in sensor networks). In addition, a significant =
effort has been devoted to the deployment of new header compression =
methods with improved robustness (ROHC).
So there is a need of replacing  <http://tools.ietf.org/html/rfc4170> =
RFC4170 with an extended solution able to optimize these new flows, also =
using improved compression methods. The same structure of three layers =
(header compression, multiplexing and tunneling) will be considered.
New scenarios where bandwidth savings are desirable have been =
identified, in addition to those considered in  =
<http://tools.ietf.org/html/rfc4170> RFC4170. In these scenarios, there =
are moments or places where network capacity gets scarce, so allocating =
more bandwidth is a possible solution, but it implies a recurring cost. =
However, the inclusion of a pair of boxes able to optimize the traffic =
when/where required is a one-time investment. These scenarios can be =
classified into:
*	Multidomain, the TCMT-TF tunnel goes all the way from one network edge =
to another, and can therefore cross several domains.
*	Single Domain, TCM-TF is only activated inside an ISP, from the edge =
to border inside the network operator.
*	Private Solutions. TCM-TF is used to connect private networks =
geographically apart (e.g. corporation headquarters and subsidiaries), =
without the ISP being aware or having to manage those flows.
*	Mixed Scenarios, any combination of the previous ones.
The BOF will discuss the proposed charter, with the aim of the creation =
of a Working Group in order to specify the protocol stack, signaling =
mechanisms and maximum added delay recommendations for tunneling, =
compressing and multiplexing traffic flows (TCM-TF). This BoF is =
intended to form a WG.
*	The responsible Area Director (AD): Martin Stiemerling, Spencer =
Dawkins
*	BoF Chairs (or the ADs as placeholders): Martin Stiemerling, Spencer =
Dawkins
*	Number of people expected to attend: 80
*	Length of session: 1 hour
*	Conflicts to avoid (Whole area and/or WGs): All TSV WGs, TSVAREA, =
6lowpan, avtcore, avtext, rtcweb, mmusic, l2vpn, l3vpn, softwire
*	Does it require WebEX?: No
*	Does it require Meetecho?: Yes, will have a number of remote =
participants
Links to the mailing list, draft charter if any, relevant =
Internet-Drafts, etc.:
Mailing List:  <https://www.ietf.org/mailman/listinfo/tcmtf> =
=E2=80=8Bhttps://www.ietf.org/mailman/listinfo/tcmtf
Draft charter: =E2=80=8B =
<http://www.ietf.org/mail-archive/web/tcmtf/current/msg00493.html> =
=E2=80=8Bhttp://www.ietf.org/mail-archive/web/tcmtf/current/msg00493.html=

Relevant I-Ds: =E2=80=8B =
<https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/> =
=E2=80=8Bhttps://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
=E2=80=8B =
<http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/> =
=E2=80=8Bhttp://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/=

=20

------=_NextPart_000_0008_01CF137D.E0BEBCB0
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dutf-8">
<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=3DProgId =
content=3DWord.Document><meta name=3DGenerator content=3D"Microsoft Word =
14"><meta name=3DOriginator content=3D"Microsoft Word 14"><link =
rel=3DFile-List href=3D"cid:filelist.xml@01CF137D.DF977AC0"><!--[if gte =
mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:HyphenationZone>21</w:HyphenationZone>
<w:EnvelopeVis/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>ES</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:1;
	mso-generic-font-family:roman;
	mso-font-format:other;
	mso-font-pitch:variable;
	mso-font-signature:0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:"Times New Roman";}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:windowtext;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;
	mso-style-unhide:no;}
span.icon
	{mso-style-name:icon;
	mso-style-unhide:no;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1104766861;
	mso-list-template-ids:-891937164;}
@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-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1728214898;
	mso-list-template-ids:1347057420;}
@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-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2
	{mso-list-id:1972050726;
	mso-list-template-ids:-1971566844;}
@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-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Tabla normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[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 style=3D'tab-interval:35.4pt'><div =
class=3DWordSection1><p class=3DMsoNormal>Hi <span =
class=3DSpellE>all</span>,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>A second <span =
class=3DSpellE>BoF</span> with the aim of creating a WG has been =
requested for London. You can find the details here: <a =
href=3D"http://trac.tools.ietf.org/bof/trac/wiki#Transport">http://trac.t=
ools.ietf.org/bof/trac/wiki#Transport</a><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Best regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Jose<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:l2 level1 lfo1;tab-stops:list 36.0pt;background:white'><span =
lang=3DEN-US style=3D'font-size:11.5pt;mso-ansi-language:EN-US'>Long =
name and abbreviation: Tunneling Compressed Multiplexed Traffic Flows =
(TCMTF)<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 level1 lfo1;tab-stops:list 36.0pt;background:white'><span =
lang=3DEN-US style=3D'font-size:11.5pt;mso-ansi-language:EN-US'>Status: =
WG Forming, 2nd attempt (1st was IETF-87 in =
Berlin)<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 level1 lfo1;tab-stops:list 36.0pt;background:white'><span =
class=3DSpellE><span =
style=3D'font-size:11.5pt'>Description</span></span><span =
style=3D'font-size:11.5pt'>:<o:p></o:p></span></li></ul><p =
style=3D'background:white;orphans: auto;text-align:start;widows: =
auto;-webkit-text-stroke-width: 0px;word-spacing:0px'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US'><a =
href=3D"http://tools.ietf.org/html/rfc4170"><span =
style=3D'color:windowtext;text-decoration:none;text-underline:none'>RFC41=
70</span></a>&nbsp;(TCRTP) defines a method for grouping packets when a =
number of UDP/RTP VoIP flows share a common path, considering three =
different layers: ECRTP header compression; PPPMux multiplexing; L2TPv3 =
tunneling. TCRTP optimizes the traffic, increasing the bandwidth =
efficiency of VoIP and reduces the amount of packets per second at the =
same time. However, in the last years, emerging real-time services which =
use bare UDP instead of UDP/RTP have become popular. Due to the need of =
interactivity, many of these services use small packets (some tens of =
bytes). Some other services also send small packets, but they are not =
delay-sensitive (e.g., instant messaging, m2m packets in sensor =
networks). In addition, a significant effort has been devoted to the =
deployment of new header compression methods with improved robustness =
(ROHC).<o:p></o:p></span></p><p style=3D'background:white;orphans: =
auto;text-align:start;widows: auto;-webkit-text-stroke-width: =
0px;word-spacing:0px'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US'>So there is a =
need of replacing&nbsp;<a =
href=3D"http://tools.ietf.org/html/rfc4170"><span =
style=3D'color:windowtext;text-decoration:none;text-underline:none'>RFC41=
70</span></a>&nbsp;with an extended solution able to optimize these new =
flows, also using improved compression methods. The same structure of =
three layers (header compression, multiplexing and tunneling) will be =
considered.<o:p></o:p></span></p><p style=3D'background:white;orphans: =
auto;text-align:start;widows: auto;-webkit-text-stroke-width: =
0px;word-spacing:0px'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US'>New scenarios =
where bandwidth savings are desirable have been identified, in addition =
to those considered in&nbsp;<a =
href=3D"http://tools.ietf.org/html/rfc4170"><span =
style=3D'color:windowtext;text-decoration:none;text-underline:none'>RFC41=
70</span></a>. In these scenarios, there are moments or places where =
network capacity gets scarce, so allocating more bandwidth is a possible =
solution, but it implies a recurring cost. However, the inclusion of a =
pair of boxes able to optimize the traffic when/where required is a =
one-time investment. <span class=3DSpellE>These</span> <span =
class=3DSpellE>scenarios</span> can be <span =
class=3DSpellE>classified</span> <span =
class=3DSpellE>into</span>:<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 lfo2;tab-stops:list 36.0pt;background:white'><span =
class=3DSpellE><span lang=3DEN-US =
style=3D'font-size:11.5pt;mso-ansi-language:EN-US'>Multidomain</span></sp=
an><span lang=3DEN-US =
style=3D'font-size:11.5pt;mso-ansi-language:EN-US'>, the TCMT-TF tunnel =
goes all the way from one network edge to another, and can therefore =
cross several domains.<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 lfo2;tab-stops:list 36.0pt;background:white'><span =
lang=3DEN-US style=3D'font-size:11.5pt;mso-ansi-language:EN-US'>Single =
Domain, TCM-TF is only activated inside an ISP, from the edge to border =
inside the network operator.<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 lfo2;tab-stops:list 36.0pt;background:white'><span =
lang=3DEN-US style=3D'font-size:11.5pt;mso-ansi-language:EN-US'>Private =
Solutions. TCM-TF is used to connect private networks geographically =
apart (e.g. corporation headquarters and subsidiaries), without the ISP =
being aware or having to manage those flows.<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 lfo2;tab-stops:list 36.0pt;background:white'><span =
lang=3DEN-US style=3D'font-size:11.5pt;mso-ansi-language:EN-US'>Mixed =
Scenarios, any combination of the previous =
ones.<o:p></o:p></span></li></ul><p style=3D'background:white;orphans: =
auto;text-align:start;widows: auto;-webkit-text-stroke-width: =
0px;word-spacing:0px'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:Calibri;mso-bidi-font-family:"Times New =
Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US'>The BOF will =
discuss the proposed charter, with the aim of the creation of a Working =
Group in order to specify the protocol stack, signaling mechanisms and =
maximum added delay recommendations for tunneling, compressing and =
multiplexing traffic flows (TCM-TF). <span class=3DSpellE>This</span> =
<span class=3DSpellE>BoF</span> <span class=3DSpellE>is</span> <span =
class=3DSpellE>intended</span> to <span class=3DSpellE>form</span> a =
WG.<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:l0 level1 lfo3;tab-stops:list 36.0pt;background:white'><span =
lang=3DEN-US style=3D'font-size:11.5pt;mso-ansi-language:EN-US'>The =
responsible Area Director (AD): Martin <span =
class=3DSpellE>Stiemerling</span>, Spencer =
Dawkins<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:l0 level1 lfo3;tab-stops:list 36.0pt;background:white'><span =
class=3DSpellE><span lang=3DEN-US =
style=3D'font-size:11.5pt;mso-ansi-language:EN-US'>BoF</span></span><span=
 lang=3DEN-US style=3D'font-size:11.5pt;mso-ansi-language:EN-US'> Chairs =
(or the ADs as placeholders): Martin <span =
class=3DSpellE>Stiemerling</span>, Spencer =
Dawkins<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:l0 level1 lfo3;tab-stops:list 36.0pt;background:white'><span =
lang=3DEN-US style=3D'font-size:11.5pt;mso-ansi-language:EN-US'>Number =
of people expected to attend: 80<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:l0 level1 lfo3;tab-stops:list 36.0pt;background:white'><span =
class=3DSpellE><span =
style=3D'font-size:11.5pt'>Length</span></span><span =
style=3D'font-size:11.5pt'> of <span class=3DSpellE>session</span>: 1 =
<span class=3DSpellE>hour</span><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:l0 level1 lfo3;tab-stops:list 36.0pt;background:white'><span =
lang=3DEN-US =
style=3D'font-size:11.5pt;mso-ansi-language:EN-US'>Conflicts to avoid =
(Whole area and/or WGs): All TSV WGs, TSVAREA, 6lowpan, <span =
class=3DSpellE>avtcore</span>, <span class=3DSpellE>avtext</span>, <span =
class=3DSpellE>rtcweb</span>, <span class=3DSpellE>mmusic</span>, l2vpn, =
l3vpn, <span class=3DSpellE>softwire</span><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:l0 level1 lfo3;tab-stops:list 36.0pt;background:white'><span =
class=3DSpellE><span style=3D'font-size:11.5pt'>Does</span></span><span =
style=3D'font-size:11.5pt'> <span class=3DSpellE>it</span> <span =
class=3DSpellE>require</span> <span class=3DSpellE>WebEX</span>?: =
No<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:l0 level1 lfo3;tab-stops:list 36.0pt;background:white'><span =
lang=3DEN-US style=3D'font-size:11.5pt;mso-ansi-language:EN-US'>Does it =
require <span class=3DSpellE>Meetecho</span>?: Yes, will have a number =
of remote participants<o:p></o:p></span></li></ul><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;background:wh=
ite'><span lang=3DEN-US =
style=3D'font-size:11.5pt;color:black;mso-ansi-language:EN-US'>Links to =
the mailing list, draft charter if any, relevant Internet-Drafts, =
etc.:<o:p></o:p></span></p><p style=3D'background:white;orphans: =
auto;text-align:start;widows: auto;-webkit-text-stroke-width: =
0px;word-spacing:0px'><span lang=3DEN-US =
style=3D'font-size:11.5pt;color:black;mso-ansi-language:EN-US'>Mailing =
List:<span class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:11.5pt;color:black'><a =
href=3D"https://www.ietf.org/mailman/listinfo/tcmtf"><span =
class=3Dicon><span lang=3DEN-US =
style=3D'color:#440088;mso-ansi-language:EN-US'>=E2=80=8B</span></span><s=
pan lang=3DEN-US =
style=3D'color:#440088;mso-ansi-language:EN-US'>https://www.ietf.org/mail=
man/listinfo/tcmtf</span></a></span><span lang=3DEN-US =
style=3D'font-size:11.5pt;color:black;mso-ansi-language:EN-US'><o:p></o:p=
></span></p><p style=3D'background:white;orphans: =
auto;text-align:start;widows: auto;-webkit-text-stroke-width: =
0px;word-spacing:0px'><span lang=3DEN-US =
style=3D'font-size:11.5pt;color:black;mso-ansi-language:EN-US'>Draft =
charter: =E2=80=8B</span><span style=3D'font-size:11.5pt;color:black'><a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00493.html"=
><span class=3Dicon><span lang=3DEN-US =
style=3D'color:#440088;mso-ansi-language:EN-US'>=E2=80=8B</span></span><s=
pan lang=3DEN-US =
style=3D'color:#440088;mso-ansi-language:EN-US'>http://www.ietf.org/mail-=
archive/web/tcmtf/current/msg00493.html</span></a></span><span =
lang=3DEN-US =
style=3D'font-size:11.5pt;color:black;mso-ansi-language:EN-US'><o:p></o:p=
></span></p><p style=3D'background:white;orphans: =
auto;text-align:start;widows: auto;-webkit-text-stroke-width: =
0px;word-spacing:0px'><span lang=3DEN-US =
style=3D'font-size:11.5pt;color:black;mso-ansi-language:EN-US'>Relevant =
I-Ds: =E2=80=8B</span><span style=3D'font-size:11.5pt;color:black'><a =
href=3D"https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/"><spa=
n class=3Dicon><span lang=3DEN-US =
style=3D'color:#440088;mso-ansi-language:EN-US'>=E2=80=8B</span></span><s=
pan lang=3DEN-US =
style=3D'color:#440088;mso-ansi-language:EN-US'>https://datatracker.ietf.=
org/doc/draft-saldana-tsvwg-tcmtf/</span></a></span><span lang=3DEN-US =
style=3D'font-size:11.5pt;color:black;mso-ansi-language:EN-US'><o:p></o:p=
></span></p><p style=3D'background:white;orphans: =
auto;text-align:start;widows: auto;-webkit-text-stroke-width: =
0px;word-spacing:0px'><span lang=3DEN-US =
style=3D'font-size:11.5pt;color:black;mso-ansi-language:EN-US'>=E2=80=8B<=
/span><span style=3D'font-size:11.5pt;color:black'><a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
><span class=3Dicon><span lang=3DEN-US =
style=3D'color:#440088;mso-ansi-language:EN-US'>=E2=80=8B</span></span><s=
pan lang=3DEN-US =
style=3D'color:#440088;mso-ansi-language:EN-US'>http://datatracker.ietf.o=
rg/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</span></a></span><span =
lang=3DEN-US =
style=3D'font-size:11.5pt;color:black;mso-ansi-language:EN-US'><o:p></o:p=
></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p></div></bod=
y></html>
------=_NextPart_000_0008_01CF137D.E0BEBCB0--



From jsaldana@unizar.es  Thu Jan 23 02:17:04 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA8F81A0362; Thu, 23 Jan 2014 02:17:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.035
X-Spam-Level: 
X-Spam-Status: No, score=-2.035 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNvspA3Ap1aO; Thu, 23 Jan 2014 02:17:02 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 655CD1A024C; Thu, 23 Jan 2014 02:17:01 -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 s0NAGttZ011848; Thu, 23 Jan 2014 11:16:55 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Thu, 23 Jan 2014 11:17:00 +0100
Message-ID: <00b101cf1824$41224d10$c366e730$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B2_01CF182C.A2E77860"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8YJD87lgl01q8ARx6DhheMRKhZ7g==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tsv-area@ietf.org
Subject: [tcmtf] TCM-TF 2nd BoF approved
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Jan 2014 10:17:05 -0000

This is a multipart message in MIME format.

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

Hi all,
 
As you may know, the second TCM-TF BoF has been approved, and it will be
held in London next March.
 
http://trac.tools.ietf.org/bof/trac/wiki#Transport
 
We will work in the next weeks in order to prepare it well.
 
Best regards and thanks,
 
Jose 
 

------=_NextPart_000_00B2_01CF182C.A2E77860
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=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CF182C.A154A360"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:HyphenationZone>21</w:HyphenationZone>
<w:EnvelopeVis/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>ES</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1107305727 0 0 415 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:windowtext;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Tabla normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[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 style=3D'tab-interval:35.4pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Hi all,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>As you may know, the second TCM-TF =
<span class=3DSpellE>BoF</span> has been approved, and it will be held =
in London next March.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><a =
href=3D"http://trac.tools.ietf.org/bof/trac/wiki#Transport">http://trac.t=
ools.ietf.org/bof/trac/wiki#Transport</a><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>We will work in the next weeks in =
order to prepare it well.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Best regards and =
thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-font-family:"Times New =
Roman";mso-bidi-font-family:Arial;mso-ansi-language:EN-US;mso-fareast-lan=
guage:ES;mso-no-proof:yes'>Jose </span><span =
style=3D'mso-fareast-font-family:"Times New =
Roman";mso-bidi-font-family:Arial;mso-fareast-language:ES;mso-no-proof:ye=
s'><o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00B2_01CF182C.A2E77860--


From mehmetkrc@sabanciuniv.edu  Thu Jan 23 07:05:44 2014
Return-Path: <mehmetkrc@sabanciuniv.edu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F17B1A0014 for <tcmtf@ietfa.amsl.com>; Thu, 23 Jan 2014 07:05:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.436
X-Spam-Level: *
X-Spam-Status: No, score=1.436 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, ONE_TIME=0.714, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y7U3WBorB6gM for <tcmtf@ietfa.amsl.com>; Thu, 23 Jan 2014 07:05:40 -0800 (PST)
Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com [209.85.223.174]) by ietfa.amsl.com (Postfix) with ESMTP id CF2291A001C for <tcmtf@ietf.org>; Thu, 23 Jan 2014 07:05:38 -0800 (PST)
Received: by mail-ie0-f174.google.com with SMTP id tp5so1240398ieb.33 for <tcmtf@ietf.org>; Thu, 23 Jan 2014 07:05:37 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=TFtLkNj9E5o6lJjWnBMa3lGWT6C6Fix+Rw29/T5fq+Q=; b=K8mPsSgjKi06E0yMdUWsUzvdKfAMlHXjCuLMZWV0/vxINFKbpyIvKPOITKOE4EZIb4 6a7WELAFdmAmbjrbiXRhP686xCPBqcDuZO0V6Tp8e4c3crHlA4r/HBdj/scV+KOpLHKE vN3Q9ssU4d6D55HXMgHk+RHSsbkUdA8N83uVqnI6Frg7yps9h3PO8Ok7Bj9iWMEL/Abe 8VjFZRSKhqkhVU3R28hQrOTSqIwf+cpKM8sXQG2hA3eUYKuOWwlaCsR3JmhGRcCtipcX SCF/ft0Dn4Ph0MZwHZY7dpwhZs2F6NFzllr6FyLLITb8NUNuVLooEENwPsAyMCN1Y60T FAQg==
X-Gm-Message-State: ALoCoQkQnhQ1oJyt+y4lwptRdOYoW3wVEqIIO+XBbIK9ptdR9KsmAw0ftIOgnJz/A4zF2iceoAro
MIME-Version: 1.0
X-Received: by 10.43.52.65 with SMTP id vl1mr934374icb.86.1390489537734; Thu, 23 Jan 2014 07:05:37 -0800 (PST)
Received: by 10.42.98.143 with HTTP; Thu, 23 Jan 2014 07:05:37 -0800 (PST)
In-Reply-To: <19613893-ECE3-4CB5-A159-4E9D61788408@tid.es>
References: <00c401cefd65$6e8ef570$4bace050$@unizar.es> <8D3D17ACE214DC429325B2B98F3AE712026EF2FF8F@MX15A.corp.emc.com> <004701cf0ccf$4d5826a0$e80873e0$@unizar.es> <B180C070-CA16-47BE-9A43-1F10546426DA@huawei.com> <19613893-ECE3-4CB5-A159-4E9D61788408@tid.es>
Date: Thu, 23 Jan 2014 17:05:37 +0200
Message-ID: <CAKonK3RXQKQyjwDacJo4HoKSznLVD_3AaVT62C3+ihYCBokTxg@mail.gmail.com>
From: "Mehmet Karaca (Alumni)" <mehmetkrc@sabanciuniv.edu>
To: FERNANDO PASCUAL BLANCO <fpb@tid.es>
Content-Type: multipart/alternative; boundary=bcaec52e5f41f61cc404f0a492fc
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "Black, David" <david.black@emc.com>, Jose Saldana <jsaldana@unizar.es>, "tsv-area@ietf.org" <tsv-area@ietf.org>, Luigi Iannone <ggx@gigix.net>, Martin Stiemerling <mls.ietf@googlemail.com>
Subject: Re: [tcmtf] TCMTF-Feedback about a possible BoF in London
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Jan 2014 15:05:44 -0000

--bcaec52e5f41f61cc404f0a492fc
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Dear All,

I completely support the formation of the WG for TCMMF.  I believe that
such protocols in TCMMF will be also  beneficial from  MAC layer point of
view since whenever QoS is required and traffic is not tagged at MAC layer
(in cases where 802.11e is not supported or traffic is not tagged at the
source), traffic classification at  higher layer (Layer 3 or above) will be
very crucial for some level of  QoS at MAC layer.

Best Regards and  thanks!

Mehmet.


On Thu, Jan 9, 2014 at 7:49 PM, FERNANDO PASCUAL BLANCO <fpb@tid.es> wrote:

>  Hi all,
>
>  Just to say that I also completely support the creation of the WG. There
> is no doubt that network protocols have evolved, and not always as we
> thought, and TCRTP needs to be wider.
>
> Regards,
> Fernando
>
>
>  On 09/01/2014, at 01:49, Tina TSOU <Tina.Tsou.Zouting@huawei.com> wrote:
>
>  Dear all,
> I'm in favor of having a BoF in London, as the following problem statemen=
t
> seems valid and needs protocol work in IETF.
> ---
>  In addition to VoIP, in the last years we are witnessing the raise of
> new real-time services e.g. videoconferencing, telemedicine, video
> vigilance, online gaming, etc.
>
>
>  Due to the need of interactivity, many of these services use small
> packets (some tens of bytes), since they have to send frequent updates
> between the extremes of the communication. Their small data payloads incu=
r
> significant overhead, and it becomes even higher when IPv6 is used, since
> the basic IPv6 header is twice the size of the IPv4 one.
>
>
>  In the moments or places where network capacity gets scarce, allocating
> more bandwidth is a possible solution, but it implies a recurring cost.
> However, the inclusion of a pair of boxes able to optimize the traffic
> (reducing bandwidth and packets per second) when/where required is a
> one-time investment. We can do these three things:
>
>
>  a) header compression algorithms (e.g. ROHC) can be used for reducing
> the overhead of each flow;
>  b) at the same time, tunneling can be used in order to allow the
> header-compressed packets to travel end-to-end
>  c) compressed packets belonging to different flows can be multiplexed
> together, in order to share the tunnel overhead.
>
>
>  These emerging real-time services which use bare UDP instead of UDP/RTP
> have become popular. In addition, a significant effort has been devoted
> to the deployment of new header compression methods with improved
> robustness (ROHC). So there is a need of widening the scope of RFC4170 in
> order to consider these new header compression methods, and also UDP in
> addition to UDP/RTP.
>
>
>  As a result, the next objectives can be achieved:
>
>
>  * Significant bandwidth reductions (as an example, bandwidth savings of
> 55% can be obtained for VoIP if IPv4 is used, and 65% using IPv6. For
> certain online games, 33% of the bandwidth can be saved for IPv4, and 55%
> when using IPv6).
>
>
>  * A reduction of the amount of packets per second managed by the
> network. A reduction factor of 10 or 20 can easily be achieved. This can =
be
> translated into smaller processing delays and energy savings in
> intermediate routers.
>  ---
>
>  Thank you,
> Tina
>
> On Jan 8, 2014, at 4:11 PM, "Jose Saldana" <jsaldana@unizar.es> wrote:
>
>   Hi all.
>
>  First of all, thanks to David and Luigi for their valuable comments.
>
>  I will wait for a while in order to include David=92s comments (perhaps
> some other people has more suggestions).
>
>  These are the improvements of version 10 with respect to v9 (
> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00486.html)
>
>  - I have shortened paragraph 1.
>  - I have shortened and merged paragraphs 2 and 3.
>  - I have moved paragraph 4 to the third place, in order to set clearer
> what we want: replacing RFC4170 with a widened proposal. As David
> suggested, I have also shortened the text and it is now more
> straightforward.
>  - I have clearly stated which protocols will be used on each layer. The
> negotiation mechanism is still necessary, since different options are
> considered e.g. for header compression. The one to be used will depend on
> the scenario and the processing capacity of the two optimizers.
>  - I have significantly shortened the description of the scenarios.
>  - I have removed paragraph 6, which included the savings figures.
>  - I have included the replacement of RFC4170 in the first milestone.
>
>  Thanks!
>
>  Jose
>
>   *De:* Black, David [mailto:david.black@emc.com <david.black@emc.com>]
> *Enviado el:* s=E1bado, 04 de enero de 2014 4:05
> *Para:* Jose Saldana; tcmtf@ietf.org; tsv-area@ietf.org
> *CC:* Martin Stiemerling; Black, David
> *Asunto:* RE: TCMTF-Feedback about a possible BoF in London
>
>  A second BoF has the explicit goal of forming a WG, as a third BoF
>  is not permitted.  In that regard, the new charter seems long and
>  somewhat lacking in focus.  Two key things I look for in a proposed
>  charter are what problem (or problems) the proposed WG is looking to
>  solve and an initial approach to the problem or problems.
>
>  In the new draft charter, the problem statement appears to be in
>  paragraph 4 with paragraph 1 providing important background.  The
>  focus of the work appears to be on extending TCRTP (RFC 4170) to
>  UDP and to include new compression protocols.  In contrast, I have
>  a hard time discerning the initial approach from the new draft charter.
>
>  In light of this, there are a few things that I wish the new
>  draft charter had definitive proposals for:
>
>        a) Whether to replace RFC 4170 vs. write a new RFC (could be
>              UDP-only or UDP + RTP/UDP) as a complement to RFC 4170.
>        b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC (RFC 2507
> ?).
>              Non-use of ECRTP would be a major change to 4170, and I
>  wonder about IPHC, as opposed to the ROHCv2 profiles.
>        c) Analogies to b) for the Mux and Tunnel layers of the stack.
>
>  Overall, it looks like the first task of the WG is to select the protoco=
l
>  stack to standardize - I have misgivings about that, and would prefer to
>  see a concrete proposal in a crisp charter that ran along the following
>  lines, naming the protocols to be used:
>
>  1) RFC 4170 does X, and needs the following changes/additions: X, Y, Z.
>  2) The WG will replace RFC 4170 with a new RFC that contains: A, B, C.
>
>  A specific proposal or proposals for the protocol stack or stacks
>  would also narrow the scope of item 9 in the charter on the negotiation
>  mechanism.  I also don=92t see a goal/milestone listed for an extension =
to
>  or replacement for RFC 4170.
>
>  I=92d prefer to see a much shorter more focused draft charter.  There=92=
s a
>  bunch of background material that does not seem crucial to the charter,
>  starting w/paragraphs 2 and 3.
>
>  Thanks,
> --David
>
>   *From:* tsv-area [mailto:tsv-area-bounces@ietf.org<tsv-area-bounces@iet=
f.org>
> ] *On Behalf Of *Jose Saldana
> *Sent:* Friday, December 20, 2013 4:26 AM
> *To:* tcmtf@ietf.org; tsv-area@ietf.org
> *Cc:* Martin Stiemerling
> *Subject:* TCMTF-Feedback about a possible BoF in London
>
>  Hi all,
>
>  After the feedback received in the BoF in Berlin, we have updated the
> TCM-TF charter and the two drafts. We have tried to solve all the problem=
s
> raised during the session.
>
>  Our plan is to request a new BoF in London next March, so we would like
> to know your opinion about these two questions:
>
>
>  1.  Is the new, reduced scope of TCM-TF suitable to form a working group=
?
>
>
>  2. We would like to kindly ask people who think that a TCM-TF Working
> group should be formed, to come forward and send an e-mail to the
> tsv-area@ietf.org  mailing list stating it.
>
>
>  This feedback will allow us to get a better idea of the convenience of a
> BoF.
>
>  The new charter is here:
> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html
>  This is the old one (presented in Berlin):
> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.html
>
>  In these links you can see the differences between the new versions of
> the drafts and the old ones:
>
> http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&url=
2=3Ddraft-saldana-tsvwg-tcmtf-05.txt
>
> http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.t=
xt&url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt
>
>
>  The main improvements are:
>
>  - TCP optimization has been removed
>  - The classification of the scenarios has been refined and improved.
> Some of them have been removed
>  - A section about energy consumption has been added to the main draft
>  - A reference to the potential problem of the MTU and packet loss has
> been added
>  - The problem of the added delays is studied in detail in the second
> draft
>
>  - The improvements of the charter are summarized here:
> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.html
>
>
>  Best regards,
>
>  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
>
>

--bcaec52e5f41f61cc404f0a492fc
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear All,<br><div><br>I completely support the formation o=
f the WG for TCMMF.=A0 I believe=20
that such protocols in TCMMF will be also=A0 beneficial from=A0 MAC layer
 point of view since whenever QoS is required and traffic is not tagged=20
at MAC layer (in cases where 802.11e is not supported or traffic is not tag=
ged at the source), traffic classification at=A0 higher layer (Layer 3 or a=
bove)
 will be very crucial for some level of=A0 QoS at MAC layer.<br>
<br>Best Regards and=A0 thanks!<br><br></div><div>Mehmet.<br></div></div><d=
iv class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Jan 9, =
2014 at 7:49 PM, FERNANDO PASCUAL BLANCO <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:fpb@tid.es" target=3D"_blank">fpb@tid.es</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word">
Hi all,
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>Just to say that I also co=
mpletely support the creation of the WG. There is no doubt that network pro=
tocols have evolved, and not always as we thought, and TCRTP needs to be wi=
der.<br>

<div>
<div>
<div style=3D"text-indent:0px;letter-spacing:normal;text-align:start;text-t=
ransform:none;white-space:normal;word-wrap:break-word;word-spacing:0px">
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:start;font-style:normal;font-weight:normal;line-height:normal;text-=
transform:none;font-size:12px;white-space:normal;margin:0cm 0cm 0.0001pt;fo=
nt-family:Helvetica;word-spacing:0px">

<br>
Regards,
<div>Fernando</div>
<br>
</div>
</div>
</div>
<br>
<div><div><div class=3D"h5">
<div>On 09/01/2014, at 01:49, Tina TSOU &lt;<a href=3D"mailto:Tina.Tsou.Zou=
ting@huawei.com" target=3D"_blank">Tina.Tsou.Zouting@huawei.com</a>&gt; wro=
te:</div>
<br>
</div></div><blockquote type=3D"cite">
<div dir=3D"auto" style=3D"font-family:Helvetica;font-size:12px;font-style:=
normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-he=
ight:normal;text-align:start;text-indent:0px;text-transform:none;white-spac=
e:normal;word-spacing:0px">
<div><div class=3D"h5">
<div><span style=3D"font-size:13pt">Dear all,</span></div>
<div>I&#39;m in favor of having a BoF in London, as the following problem s=
tatement seems valid and needs protocol work in IETF.</div>
<div>---</div>
<div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">In add=
ition to VoIP, in the last years we are witnessing the raise of new real-ti=
me services e.g. videoconferencing, telemedicine, video vigilance, online g=
aming, etc.</font></span></div>

<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">Due to=
 the need of interactivity, many of these services use small packets (some =
tens of bytes), since they have to=A0</font></span><span style=3D"font-fami=
ly:UICTFontTextStyleBody;font-size:12px">send
 frequent updates between the extremes of the communication. Their small da=
ta payloads incur significant overhead, and it becomes even higher when IPv=
6 is used, since the basic IPv6 header is twice the size of the IPv4 one.</=
span></div>

<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">In the=
 moments or places where network capacity gets scarce, allocating more band=
width is a possible solution, but it implies a recurring cost. However, the=
 inclusion of a pair of boxes
 able to optimize the traffic (reducing bandwidth and packets per second) w=
hen/where required is a one-time investment. We can do these three things:<=
/font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">a) hea=
der compression algorithms (e.g. ROHC) can be used for reducing the overhea=
d of each flow;</font></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">b) at =
the same time, tunneling can be used in order to allow the header-compresse=
d packets to travel end-to-end</font></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">c) com=
pressed packets belonging to different flows can be multiplexed together, i=
n order to share the tunnel overhead.</font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">These =
emerging real-time services which use bare UDP instead of UDP/RTP have beco=
me popular. In addition, a significant=A0</font></span><span style=3D"font-=
family:UICTFontTextStyleBody;font-size:12px">effort
 has been devoted to the deployment of new header compression methods with =
improved robustness (ROHC). So there is a need of widening the scope of RFC=
4170 in order to consider these new header compression methods, and also UD=
P in addition to UDP/RTP.</span></div>

<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">As a r=
esult, the next objectives can be achieved:</font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">* Sign=
ificant bandwidth reductions (as an example, bandwidth savings of 55% can b=
e obtained for VoIP if IPv4 is used, and 65% using IPv6. For certain online=
 games, 33% of the bandwidth
 can be saved for IPv4, and 55% when using IPv6).</font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font face=3D"UICTFontTextStyleBody" size=3D"3">* A re=
duction of the amount of packets per second managed by the network. A reduc=
tion factor of 10 or 20 can easily be achieved. This can be translated into=
 smaller processing delays and
 energy savings in intermediate routers.</font></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
---</div>
<div><br>
</div>
<div>Thank you,</div>
<div>Tina</div>
</div>
<div><br>
On Jan 8, 2014, at 4:11 PM, &quot;Jose Saldana&quot; &lt;<a href=3D"mailto:=
jsaldana@unizar.es" style=3D"color:purple;text-decoration:underline" target=
=3D"_blank">jsaldana@unizar.es</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">Hi all.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">First of all, thanks to=
 David and Luigi for their valuable comments.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">I will wait for a while=
 in order to include David=92s comments (perhaps some other people has more=
 suggestions).</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">These are the improveme=
nts of version 10 with respect to v9 (</span><a href=3D"http://www.ietf.org=
/mail-archive/web/tcmtf/current/msg00486.html" style=3D"color:purple;text-d=
ecoration:underline" target=3D"_blank"><span lang=3D"EN-US">http://www.ietf=
.org/mail-archive/web/tcmtf/current/msg00486.html</span></a><span lang=3D"E=
N-US">)</span><span style=3D"color:rgb(31,73,125)" lang=3D"EN-US"></span></=
div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have shortened para=
graph 1.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have shortened and =
merged paragraphs 2 and 3.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have moved paragrap=
h 4 to the third place, in order to set clearer what we want: replacing RFC=
4170 with a widened proposal. As David suggested, I have also shortened the=
 text and it is now more straightforward.</span></div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have clearly stated=
 which protocols will be used on each layer. The negotiation mechanism is s=
till necessary, since different options are considered e.g. for header comp=
ression. The one to be used will depend
 on the scenario and the processing capacity of the two optimizers.</span><=
/div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have significantly =
shortened the description of the scenarios.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have removed paragr=
aph 6, which included the savings figures.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have included the r=
eplacement of RFC4170 in the first milestone.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">Thanks!</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">Jose</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div>
<div style=3D"border-style:solid none none;border-top-color:rgb(181,196,223=
);border-top-width:1pt;padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-=
US">De:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-ser=
if" lang=3D"EN-US"><span>=A0</span>Black, David [</span><span style=3D"font=
-size:10pt;font-family:Tahoma,sans-serif"><a href=3D"mailto:david.black@emc=
.com" style=3D"color:purple;text-decoration:underline" target=3D"_blank"><s=
pan lang=3D"EN-US">mailto:david.black@emc.com</span></a></span><span style=
=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">]<span>=A0=
</span><br>

<b>Enviado el:</b><span>=A0</span>s=E1bado, 04 de enero de 2014 4:05<br>
<b>Para:</b><span>=A0</span>Jose Saldana;<span>=A0</span></span><span style=
=3D"font-size:10pt;font-family:Tahoma,sans-serif"><a href=3D"mailto:tcmtf@i=
etf.org" style=3D"color:purple;text-decoration:underline" target=3D"_blank"=
><span lang=3D"EN-US">tcmtf@ietf.org</span></a></span><span style=3D"font-s=
ize:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">;<span>=A0</span></s=
pan><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif"><a href=3D=
"mailto:tsv-area@ietf.org" style=3D"color:purple;text-decoration:underline"=
 target=3D"_blank"><span lang=3D"EN-US">tsv-area@ietf.org</span></a></span>=
<span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US"=
><br>

<b>CC:</b><span>=A0</span>Martin Stiemerling; Black, David<br>
<b>Asunto:</b><span>=A0</span>RE: TCMTF-Feedback about a possible BoF in Lo=
ndon</span></div>
</div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">A second BoF has the explicit goal of forming a WG, as a third BoF</sp=
an></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">is not permitted.=A0 In that regard, the new charter seems long and</s=
pan></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">somewhat lacking in focus.=A0 Two key things I look for in a proposed<=
/span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">charter are what problem (or problems) the proposed WG is looking to</=
span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">solve and an initial approach to the problem or problems.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">In the new draft charter, the problem statement appears to be in</span=
></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">paragraph 4 with paragraph 1 providing important background.=A0 The</s=
pan></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">focus of the work appears to be on extending TCRTP (RFC 4170) to</span=
></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">UDP and to include new compression protocols.=A0 In contrast, I have</=
span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">a hard time discerning the initial approach from the new draft charter=
.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">In light of this, there are a few things that I wish the new</span></d=
iv>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">draft charter had definitive proposals for:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0 a) Whether to replace RFC 4170 vs. write a new RFC (co=
uld be</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 UDP-only or UDP + RTP/UDP) as a comp=
lement to RFC 4170.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0 b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC=
 (RFC 2507 ?).</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Non-use of ECRTP would be a major ch=
ange to 4170, and I</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt 36pt;font-size:11pt;font-family:Calib=
ri,sans-serif;text-indent:36pt">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">wonder about IPHC, as opposed to the ROHCv2 profiles.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0 c) Analogies to b) for the Mux and Tunnel layers of th=
e stack.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">Overall, it looks like the first task of the WG is to select the proto=
col</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">stack to standardize - I have misgivings about that, and would prefer =
to</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">see a concrete proposal in a crisp charter that ran along the followin=
g</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">lines, naming the protocols to be used:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">1) RFC 4170 does X, and needs the following changes/additions: X, Y, Z=
.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">2) The WG will replace RFC 4170 with a new RFC that contains: A, B, C.=
</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">A specific proposal or proposals for the protocol stack or stacks</spa=
n></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">would also narrow the scope of item 9 in the charter on the negotiatio=
n</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">mechanism.=A0 I also don=92t see a goal/milestone listed for an extens=
ion to</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">or replacement for RFC 4170.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">I=92d prefer to see a much shorter more focused draft charter.=A0 Ther=
e=92s a</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">bunch of background material that does not seem crucial to the charter=
,</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">starting w/paragraphs 2 and 3.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">Thanks,<br>
--David</span><span style=3D"font-family:&#39;Courier New&#39;" lang=3D"EN-=
US"></span></div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"border-style:none none none solid;border-left-color:blue;bord=
er-left-width:1.5pt;padding:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-style:solid none none;border-top-color:rgb(181,196,223=
);border-top-width:1pt;padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-=
US">From:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-s=
erif" lang=3D"EN-US"><span>=A0</span>tsv-area [</span><a href=3D"mailto:tsv=
-area-bounces@ietf.org" style=3D"color:purple;text-decoration:underline" ta=
rget=3D"_blank"><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif=
" lang=3D"EN-US">mailto:tsv-area-bounces@ietf.org</span></a><span style=3D"=
font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">]<span>=A0</sp=
an><b>On
 Behalf Of<span>=A0</span></b>Jose Saldana<br>
<b>Sent:</b><span>=A0</span>Friday, December 20, 2013 4:26 AM<br>
<b>To:</b><span>=A0</span></span><a href=3D"mailto:tcmtf@ietf.org" style=3D=
"color:purple;text-decoration:underline" target=3D"_blank"><span style=3D"f=
ont-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">tcmtf@ietf.org<=
/span></a><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=
=3D"EN-US">;<span>=A0</span></span><a href=3D"mailto:tsv-area@ietf.org" sty=
le=3D"color:purple;text-decoration:underline" target=3D"_blank"><span style=
=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">tsv-area@i=
etf.org</span></a><span style=3D"font-size:10pt;font-family:Tahoma,sans-ser=
if" lang=3D"EN-US"><br>

<b>Cc:</b><span>=A0</span>Martin Stiemerling<br>
<b>Subject:</b><span>=A0</span>TCMTF-Feedback about a possible BoF in Londo=
n</span></div>
</div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">Hi all,</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">After the feedback received in the BoF in Berlin, we h=
ave updated the TCM-TF charter and the two drafts. We have tried to solve a=
ll the problems raised during the session.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">Our plan is to request a new BoF in London next March,=
 so we would like to know your opinion about these two questions:</span></d=
iv>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">1. =A0Is the new, reduced scope of TCM-TF suitable to =
form a working group?</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">2. We would like to kindly ask people who think that a=
 TCM-TF Working group should be formed, to come forward and send an e-mail =
to the<span>=A0</span></span><a href=3D"mailto:tsv-area@ietf.org" style=3D"=
color:purple;text-decoration:underline" target=3D"_blank"><span lang=3D"EN-=
US">tsv-area@ietf.org</span></a><span lang=3D"EN-US"><span>=A0</span>=A0mai=
ling
 list stating it.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">This feedback will allow us to get a better idea of th=
e convenience of a BoF.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">The new charter is here:<span>=A0</span></span><a href=
=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html" style=
=3D"color:purple;text-decoration:underline" target=3D"_blank"><span lang=3D=
"EN-US">http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html</s=
pan></a><span lang=3D"EN-US"></span></div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">This is the old one (presented in Berlin):<span>=A0</s=
pan></span><a href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/ms=
g00368.html" style=3D"color:purple;text-decoration:underline" target=3D"_bl=
ank"><span lang=3D"EN-US">http://www.ietf.org/mail-archive/web/tcmtf/curren=
t/msg00368.html</span></a><span lang=3D"EN-US"></span></div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">In these links you can see the differences between the=
 new versions of the drafts and the old ones:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<a href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-0=
6.txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt" style=3D"color:purple;te=
xt-decoration:underline" target=3D"_blank"><span lang=3D"EN-US">http://tool=
s.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&amp;url2=3Ddraft=
-saldana-tsvwg-tcmtf-05.txt</span></a><span lang=3D"EN-US"></span></div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<a href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-t=
cmtf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt" style=3D"col=
or:purple;text-decoration:underline" target=3D"_blank"><span lang=3D"EN-US"=
>http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.tx=
t&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt</span></a><span lang=3D=
"EN-US"></span></div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">The main improvements are:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- TCP optimization has been removed</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- The classification of the scenarios has been refined=
 and improved. Some of them have been removed</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- A section about energy consumption has been added to=
 the main draft</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- A reference to the potential problem of the MTU and =
packet loss has been added</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- The problem of the added delays is studied in detail=
 in the second draft</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- The improvements of the charter are summarized here:=
<span>=A0</span></span><a href=3D"http://www.ietf.org/mail-archive/web/tcmt=
f/current/msg00466.html" style=3D"color:purple;text-decoration:underline" t=
arget=3D"_blank"><span lang=3D"EN-US">http://www.ietf.org/mail-archive/web/=
tcmtf/current/msg00466.html</span></a><span lang=3D"EN-US"></span></div>

<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">Best regards,</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">Jose</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
</div>
</div>
</blockquote>
<blockquote type=3D"cite">
<div></div>
</blockquote></div></div>
_______________________________________________<div class=3D"im"><br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org" style=3D"color:purple;text-decoration:und=
erline" target=3D"_blank">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color:purp=
le;text-decoration:underline" target=3D"_blank">https://www.ietf.org/mailma=
n/listinfo/tcmtf</a></div></div>
</blockquote>
</div>
<br>
</div>
</div><div class=3D"im">
<br>
<hr>
<font color=3D"Gray" face=3D"Arial" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
<a href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx" target=3D"_blank">=
http://www.tid.es/ES/PAGINAS/disclaimer.aspx</a><br>
</font>
</div></div>

<br>_______________________________________________<br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/tcmtf</a><br>
<br></blockquote></div><br></div>

--bcaec52e5f41f61cc404f0a492fc--


From ece.gelal@airties.com  Thu Jan 23 09:33:58 2014
Return-Path: <ece.gelal@airties.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FE421A0109 for <tcmtf@ietfa.amsl.com>; Thu, 23 Jan 2014 09:33:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.079
X-Spam-Level: 
X-Spam-Status: No, score=-0.079 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZAAEPFhGoDrc for <tcmtf@ietfa.amsl.com>; Thu, 23 Jan 2014 09:33:53 -0800 (PST)
Received: from mail-we0-f179.google.com (mail-we0-f179.google.com [74.125.82.179]) by ietfa.amsl.com (Postfix) with ESMTP id 1A4C31A007C for <tcmtf@ietf.org>; Thu, 23 Jan 2014 09:33:50 -0800 (PST)
Received: by mail-we0-f179.google.com with SMTP id w62so1510006wes.24 for <tcmtf@ietf.org>; Thu, 23 Jan 2014 09:33:49 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=FalQqdfmYMMfmkJYx+X/03LVvL5b8Ek6rOyjGrrAPEs=; b=iDXUvN078+ZUZoi58SRGZqp7yHL8aarvHu43HsjDeBdC7X5WhFlMYTdwFUusUS+mD1 bkB3Q6ZPUDO4aUNDlwURzHNIHe8BO6AwXLgjnY3eeV9AtxMyXK+vkSdu1TTN27OphoUq TkMLT+1fw49TKdEJ+SW3X1U2NP6ObS3SEcDWvziFigmHF3Jm2bAT7HhS0G32SCT/zCKo NdQrxz9wpJ2fPKKI8RLaiMgXRvPEv5ypFdQ5yh7I0NBLY5TdgxVCeldh0pgEYoczHMrG /qQPYhed9c6ChJo5JjEvcclGANMPljlHKkwwgzV6ABIol8Rieky6CoRsQJBYZJI3n489 IKmA==
X-Gm-Message-State: ALoCoQkqX4aNNxvjDDZE8JvA1msuq5k2yX6oYNp/nHqoZ4yBEDeDCd2mHjdz6/0BjTLJsThJFCpwBSZOP+3/dGEAGKEhqgH2hQ==
MIME-Version: 1.0
X-Received: by 10.180.102.42 with SMTP id fl10mr165391wib.42.1390498429654; Thu, 23 Jan 2014 09:33:49 -0800 (PST)
Received: by 10.180.6.230 with HTTP; Thu, 23 Jan 2014 09:33:49 -0800 (PST)
In-Reply-To: <52CEE47E.5020804@mti-systems.com>
References: <00c401cefd65$6e8ef570$4bace050$@unizar.es> <8D3D17ACE214DC429325B2B98F3AE712026EF2FF8F@MX15A.corp.emc.com> <004701cf0ccf$4d5826a0$e80873e0$@unizar.es> <B180C070-CA16-47BE-9A43-1F10546426DA@huawei.com> <52CEE47E.5020804@mti-systems.com>
Date: Thu, 23 Jan 2014 19:33:49 +0200
Message-ID: <CALeeKiDuFCHvYYxWS1RrWxoJMqjxHsJJ5rV9PkGag62mCN+7iw@mail.gmail.com>
From: Ece Gelal <ece.gelal@airties.com>
To: Wesley Eddy <wes@mti-systems.com>
Content-Type: multipart/alternative; boundary=90e6ba18132af5f2b504f0a6a4eb
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "Black, David" <david.black@emc.com>, Jose Saldana <jsaldana@unizar.es>, "tsv-area@ietf.org" <tsv-area@ietf.org>, Luigi Iannone <ggx@gigix.net>, Martin Stiemerling <mls.ietf@googlemail.com>
Subject: Re: [tcmtf] TCMTF-Feedback about a possible BoF in London
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Jan 2014 17:33:58 -0000

--90e6ba18132af5f2b504f0a6a4eb
Content-Type: text/plain; charset=US-ASCII

*>> If there are people willing to write the specs *and* people are also
able to express interest in writing/deploying/selling code and products
that use those specs, then we should certainly be doingthis work in the
IETF.*

To follow up on Wesley's comment above, as AirTies we *are* interested in
writing/deploying code and selling products including this code. We believe
that significant performance improvements in the home network can be
achieved by multiplexing small-payload packets into a greater one. In
particular in the wireless environment where nodes contend for channel
access, even multiplexing two packets reduces the effort for accessing the
channel by half. We think that any company that is focused on improving the
Wi-Fi performance for various applications would be excited about TCM-TF.

Regards,
Ece


On Thu, Jan 9, 2014 at 8:03 PM, Wesley Eddy <wes@mti-systems.com> wrote:

> On 1/8/2014 7:49 PM, Tina TSOU wrote:
> > Dear all,
> > I'm in favor of having a BoF in London, as the following problem
> > statement seems valid and needs protocol work in IETF.
> > ...
>
> I'm in agreement as well.  Parts of the problem statement and the
> scope of the work might still be tweakable, but I think that
> overall there is important work for the IETF to do in this area.
>
> Due to the things Tina described very well, there will be (and are)
> products available that attempt to optimize traffic in poorly
> documented and often poorly conceived ways.  These can do more harm
> and have other mysterious effects on traffic than whatever this
> working group would create, since it would provide open specifications
> that could be developed and tested against the concerns of relevant
> layers and other IETF protocols, and problems and concerns could be
> addressed.
>
> If there are people willing to write the specs *and* people are
> also able to express interest in writing/deploying/selling code and
> products that use those specs, then we should certainly be doing
> this work in the IETF.
>
> This will allow:
> - multiple vendor boxes to interoperate on different sides of a
>   challenged network/link (currently this is beyond the state of
>   the art!)
> - simplified/standardized management of such boxes
> - well-understood behavior profiles of such middleboxes and their
>   protocols algorithms
>
> If the IETF does not do this work, then I don't believe any of those
> three benefits/results are likely at all, and the (poor) status quo
> will continue.
>
> --
> Wes Eddy
> MTI Systems
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>



-- 

Ece Gelal, PhD

Product Manager

AirTies Wireless Networks (www.airties.com)



M: +90 (533) 431 2773

E: ece.gelal@airties.com





Information in this email including any attachments may be privileged,
confidential and is intended exclusively for the addressee. The views
expressed may not be official policy, but the personal views of the
originator. If you have received it in error, please notify the sender by
return e-mail and delete it from your system. You should not reproduce,
distribute, store, retransmit, use or disclose its contents to anyone.

-- 

Information in this email including any attachments may be privileged, 
confidential and is intended exclusively for the addressee. The views 
expressed may not be official policy, but the personal views of the 
originator. If you have received it in error, please notify the sender by 
return e-mail and delete it from your system. You should not reproduce, 
distribute, store, retransmit, use or disclose its contents to anyone.

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

<div dir=3D"ltr"><i><span style=3D"font-family:arial,sans-serif;font-size:1=
2.727272033691406px">&gt;&gt; If there are people willing to write the spec=
s *and* people are=A0</span><span style=3D"font-family:arial,sans-serif;fon=
t-size:12.727272033691406px">also able to express interest in writing/deplo=
ying/selling code and=A0</span><span style=3D"font-family:arial,sans-serif;=
font-size:12.727272033691406px">products that use those specs, then we shou=
ld certainly be doing</span><br style=3D"font-family:arial,sans-serif;font-=
size:12.727272033691406px">
<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>this work in the IETF.</span></i><br><div><i><span style=3D"font-family:ar=
ial,sans-serif;font-size:12.727272033691406px"><br></span></i></div><div><f=
ont face=3D"arial, sans-serif">To follow up on Wesley&#39;s comment above, =
as AirTies we <u>are</u>=A0interested in writing/deploying code and selling=
 products including this code. We believe that significant performance impr=
ovements in the home network can be achieved by multiplexing small-payload =
packets into a greater one. In particular in the wireless environment where=
 nodes contend for channel access, even multiplexing two packets reduces th=
e effort for accessing the channel by half. We think that any company that =
is focused on improving the Wi-Fi performance for various applications woul=
d be excited about TCM-TF.=A0</font></div>
<div><font face=3D"arial, sans-serif"><br></font></div><div><font face=3D"a=
rial, sans-serif">Regards,</font></div><div><font face=3D"arial, sans-serif=
">Ece</font></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gm=
ail_quote">
On Thu, Jan 9, 2014 at 8:03 PM, Wesley Eddy <span dir=3D"ltr">&lt;<a href=
=3D"mailto:wes@mti-systems.com" target=3D"_blank">wes@mti-systems.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">On 1/8/2014 7:49 PM, Tina TSOU wrote:<br>
&gt; Dear all,<br>
&gt; I&#39;m in favor of having a BoF in London, as the following problem<b=
r>
&gt; statement seems valid and needs protocol work in IETF.<br>
</div>&gt; ...<br>
<br>
I&#39;m in agreement as well. =A0Parts of the problem statement and the<br>
scope of the work might still be tweakable, but I think that<br>
overall there is important work for the IETF to do in this area.<br>
<br>
Due to the things Tina described very well, there will be (and are)<br>
products available that attempt to optimize traffic in poorly<br>
documented and often poorly conceived ways. =A0These can do more harm<br>
and have other mysterious effects on traffic than whatever this<br>
working group would create, since it would provide open specifications<br>
that could be developed and tested against the concerns of relevant<br>
layers and other IETF protocols, and problems and concerns could be<br>
addressed.<br>
<br>
If there are people willing to write the specs *and* people are<br>
also able to express interest in writing/deploying/selling code and<br>
products that use those specs, then we should certainly be doing<br>
this work in the IETF.<br>
<br>
This will allow:<br>
- multiple vendor boxes to interoperate on different sides of a<br>
=A0 challenged network/link (currently this is beyond the state of<br>
=A0 the art!)<br>
- simplified/standardized management of such boxes<br>
- well-understood behavior profiles of such middleboxes and their<br>
=A0 protocols algorithms<br>
<br>
If the IETF does not do this work, then I don&#39;t believe any of those<br=
>
three benefits/results are likely at all, and the (poor) status quo<br>
will continue.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Wes Eddy<br>
MTI Systems<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5">_____________________=
__________________________<br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/tcmtf</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div dir=3D"ltr"><span style=3D"border-collapse:collapse"><p style=3D"margi=
n:0px"><span style=3D"font-family:Arial,sans-serif"><font>Ece Gelal, PhD</f=
ont></span></p>
<p style=3D"color:rgb(34,34,34);margin:0px"><span style=3D"color:rgb(0,0,0)=
;font-family:Arial,sans-serif"><font>Product Manager</font></span></p><p st=
yle=3D"color:rgb(34,34,34);margin:0px"><font><span style=3D"color:rgb(0,0,0=
);font-family:Arial,sans-serif">AirTies Wireless Networks (</span><span sty=
le=3D"font-family:Arial,sans-serif;background-color:rgb(255,255,255);color:=
rgb(192,0,0)"><a href=3D"http://www.airties.com/" style=3D"font-family:Aria=
l,sans-serif;background-color:rgb(255,255,255);color:rgb(17,85,204)" target=
=3D"_blank">www.airties.com</a>)</span></font></p>
<p style=3D"color:rgb(34,34,34);margin:0px"><span style=3D"background-color=
:rgb(255,255,255);font-family:Arial,sans-serif"><font>=A0</font></span></p>=
<p style=3D"color:rgb(34,34,34);margin:0px"><font><span style=3D"color:rgb(=
0,0,0);font-family:Arial,sans-serif">M:</span><span style=3D"background-col=
or:rgb(255,255,255);color:rgb(31,73,125);font-family:Arial,sans-serif">=A0<=
/span>+90 (533) 431 2773</font></p>
<p style=3D"margin:0px;background-color:rgb(255,255,255)"><span lang=3D"EN-=
GB" style=3D"font-family:Arial,sans-serif"><span lang=3D"EN-US"><font><font=
 color=3D"#000000">E:=A0</font><a href=3D"mailto:ece.gelal@airties.com" sty=
le=3D"color:rgb(17,85,204)" target=3D"_blank">ece.gelal@airties.com</a></fo=
nt></span></span></p>
<p style=3D"margin:0px;background-color:rgb(255,255,255)"><font><span style=
=3D"font-family:Arial,sans-serif;color:rgb(31,73,125)">=A0</span><span lang=
=3D"EN-GB" style=3D"font-family:Arial,sans-serif"></span></font></p><font s=
ize=3D"1"><br>
</font><p style=3D"margin:0px;background-color:rgb(255,255,255)"><span styl=
e=3D"font-family:Arial,sans-serif"><font size=3D"1">=A0</font></span></p><p=
 style=3D"margin:0px;background-color:rgb(255,255,255)"><span lang=3D"TR" s=
tyle=3D"font-family:Arial,sans-serif;color:gray"><font size=3D"1">Informati=
on in this email including any attachments may be privileged, confidential =
and is intended exclusively for the addressee. The views expressed may not =
be official policy, but the personal views of the originator. If you have r=
eceived it in error, please notify the sender by return e-mail and delete i=
t from your system. You should not reproduce, distribute, store, retransmit=
, use or disclose its contents to anyone.</font></span></p>
<p></p><p></p></span></div>
</div>

<br>
<div style=3D"text-align:left"><span style=3D"background-color:rgb(255,255,=
255);color:rgb(128,128,128);font-family:Verdana;font-size:x-small"><br></sp=
an></div><div style=3D"text-align:left"><span style=3D"background-color:rgb=
(255,255,255);color:rgb(128,128,128);font-family:Verdana;font-size:x-small"=
>Information in this email including any attachments may be privileged, con=
fidential and is intended exclusively for the addressee. The views expresse=
d may not be official policy, but the personal views of the originator. If =
you have received it in error, please notify the sender by return e-mail an=
d delete it from your system. You should not reproduce, distribute, store, =
retransmit, use or disclose its contents to anyone.</span></div>
--90e6ba18132af5f2b504f0a6a4eb--

From oloo6382@gmail.com  Thu Jan 23 22:24:14 2014
Return-Path: <oloo6382@gmail.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE3371A012A for <tcmtf@ietfa.amsl.com>; Thu, 23 Jan 2014 22:24:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.665
X-Spam-Level: *
X-Spam-Status: No, score=1.665 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, ONE_TIME=0.714, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-BjIlamQJEV for <tcmtf@ietfa.amsl.com>; Thu, 23 Jan 2014 22:24:11 -0800 (PST)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id BDB921A0097 for <tcmtf@ietf.org>; Thu, 23 Jan 2014 22:24:10 -0800 (PST)
Received: by mail-qa0-f49.google.com with SMTP id w8so3377408qac.22 for <tcmtf@ietf.org>; Thu, 23 Jan 2014 22:24:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=EUtrlkcGF1ZPNJyVlsMf2yGtEoz1FKpQsGfE82vcDo4=; b=FdEKi11TEHGONj9cQDII0PJcivQdtyQHvNH7bxE/xWABFxfRZuzwHTYIgES8AKf7sC cRNweSraSYNglFS2fygjRtxasckwHRJs0iTHM4rqi6Ax9wXlemg1R5TZWOPI5JUnewci v55KFjg1CVBkNPZR2ZuazqMxON4aqA5shu3Jtqlg+C1FHvV9K9qgLdKg36vi7mi3SvcS dJrFchp+BL1DxDmoTNEuYinzYw/7GnZ1Fh/+ckVugS7e2mm/vjznUIzf6VmO+TU2vVa5 eaFKH2s7yKaj9lJVDiV1F4MLsABMxqYwrOygXZF5RqqTOgvaP/p+o5w1Uii4Gh8ULZAt 04RQ==
MIME-Version: 1.0
X-Received: by 10.140.33.198 with SMTP id j64mr16771396qgj.14.1390544649358; Thu, 23 Jan 2014 22:24:09 -0800 (PST)
Received: by 10.96.178.101 with HTTP; Thu, 23 Jan 2014 22:24:09 -0800 (PST)
In-Reply-To: <mailman.1126.1390489545.2325.tcmtf@ietf.org>
References: <mailman.1126.1390489545.2325.tcmtf@ietf.org>
Date: Fri, 24 Jan 2014 09:24:09 +0300
Message-ID: <CABGLsFgkQt-TxFx_LotTdARZPD0DkM3bmx6yL+gsW1f2ZfMWdw@mail.gmail.com>
From: Charles Oloo <oloo6382@gmail.com>
To: tcmtf@ietf.org
Content-Type: multipart/alternative; boundary=001a1139b400de92bf04f0b167f1
Subject: Re: [tcmtf] tcmtf Digest, Vol 19, Issue 11
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 24 Jan 2014 06:24:15 -0000

--001a1139b400de92bf04f0b167f1
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Dear All

I wish to convey support the creation of the TCM-TF WG in totality as it
will mostly benefit the communities in developing countries where the
internet and bandwidth if expensive, especially here in Kenya where
internet usage is growing at tremendous speeds. The current gov plans for
free laptops for primary schools will further increase the need for more
bandwidth hence there is need to start looking at opportunities and means
to avail and sustain the ambitious program. This is a challenge for some of
us who can undertake initiatives to provide solutions for the communities.

Regards
Charles Oloo


On Thu, Jan 23, 2014 at 6:05 PM, <tcmtf-request@ietf.org> wrote:

> Send tcmtf mailing list submissions to
>         tcmtf@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.ietf.org/mailman/listinfo/tcmtf
> or, via email, send a message with subject or body 'help' to
>         tcmtf-request@ietf.org
>
> You can reach the person managing the list at
>         tcmtf-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of tcmtf digest..."
>
> Today's Topics:
>
>    1. TCM-TF 2nd BoF approved (Jose Saldana)
>    2. Re: TCMTF-Feedback about a possible BoF in London
>       (Mehmet Karaca (Alumni))
>
>
> ---------- Forwarded message ----------
> From: "Jose Saldana" <jsaldana@unizar.es>
> To: <tcmtf@ietf.org>
> Cc: tsv-area@ietf.org
> Date: Thu, 23 Jan 2014 11:17:00 +0100
> Subject: [tcmtf] TCM-TF 2nd BoF approved
>
> Hi all,
>
>
>
> As you may know, the second TCM-TF BoF has been approved, and it will be
> held in London next March.
>
>
>
> http://trac.tools.ietf.org/bof/trac/wiki#Transport
>
>
>
> We will work in the next weeks in order to prepare it well.
>
>
>
> Best regards and thanks,
>
>
>
> Jose
>
>
>
>
> ---------- Forwarded message ----------
> From: "Mehmet Karaca (Alumni)" <mehmetkrc@sabanciuniv.edu>
> To: FERNANDO PASCUAL BLANCO <fpb@tid.es>
> Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, Tina TSOU <
> Tina.Tsou.Zouting@huawei.com>, "Black, David" <david.black@emc.com>, Jose
> Saldana <jsaldana@unizar.es>, "tsv-area@ietf.org" <tsv-area@ietf.org>,
> Luigi Iannone <ggx@gigix.net>, Martin Stiemerling <mls.ietf@googlemail.co=
m
> >
> Date: Thu, 23 Jan 2014 17:05:37 +0200
> Subject: Re: [tcmtf] TCMTF-Feedback about a possible BoF in London
> Dear All,
>
> I completely support the formation of the WG for TCMMF.  I believe that
> such protocols in TCMMF will be also  beneficial from  MAC layer point of
> view since whenever QoS is required and traffic is not tagged at MAC laye=
r
> (in cases where 802.11e is not supported or traffic is not tagged at the
> source), traffic classification at  higher layer (Layer 3 or above) will =
be
> very crucial for some level of  QoS at MAC layer.
>
> Best Regards and  thanks!
>
> Mehmet.
>
>
> On Thu, Jan 9, 2014 at 7:49 PM, FERNANDO PASCUAL BLANCO <fpb@tid.es>wrote=
:
>
>>  Hi all,
>>
>>  Just to say that I also completely support the creation of the WG.
>> There is no doubt that network protocols have evolved, and not always as=
 we
>> thought, and TCRTP needs to be wider.
>>
>> Regards,
>> Fernando
>>
>>
>>  On 09/01/2014, at 01:49, Tina TSOU <Tina.Tsou.Zouting@huawei.com> wrote=
:
>>
>>   Dear all,
>> I'm in favor of having a BoF in London, as the following problem
>> statement seems valid and needs protocol work in IETF.
>> ---
>>  In addition to VoIP, in the last years we are witnessing the raise of
>> new real-time services e.g. videoconferencing, telemedicine, video
>> vigilance, online gaming, etc.
>>
>>
>>  Due to the need of interactivity, many of these services use small
>> packets (some tens of bytes), since they have to send frequent updates
>> between the extremes of the communication. Their small data payloads inc=
ur
>> significant overhead, and it becomes even higher when IPv6 is used, sinc=
e
>> the basic IPv6 header is twice the size of the IPv4 one.
>>
>>
>>  In the moments or places where network capacity gets scarce, allocating
>> more bandwidth is a possible solution, but it implies a recurring cost.
>> However, the inclusion of a pair of boxes able to optimize the traffic
>> (reducing bandwidth and packets per second) when/where required is a
>> one-time investment. We can do these three things:
>>
>>
>>  a) header compression algorithms (e.g. ROHC) can be used for reducing
>> the overhead of each flow;
>>  b) at the same time, tunneling can be used in order to allow the
>> header-compressed packets to travel end-to-end
>>  c) compressed packets belonging to different flows can be multiplexed
>> together, in order to share the tunnel overhead.
>>
>>
>>  These emerging real-time services which use bare UDP instead of UDP/RTP
>> have become popular. In addition, a significant effort has been devoted
>> to the deployment of new header compression methods with improved
>> robustness (ROHC). So there is a need of widening the scope of RFC4170 i=
n
>> order to consider these new header compression methods, and also UDP in
>> addition to UDP/RTP.
>>
>>
>>  As a result, the next objectives can be achieved:
>>
>>
>>  * Significant bandwidth reductions (as an example, bandwidth savings of
>> 55% can be obtained for VoIP if IPv4 is used, and 65% using IPv6. For
>> certain online games, 33% of the bandwidth can be saved for IPv4, and 55=
%
>> when using IPv6).
>>
>>
>>  * A reduction of the amount of packets per second managed by the
>> network. A reduction factor of 10 or 20 can easily be achieved. This can=
 be
>> translated into smaller processing delays and energy savings in
>> intermediate routers.
>>  ---
>>
>>  Thank you,
>> Tina
>>
>> On Jan 8, 2014, at 4:11 PM, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>
>>   Hi all.
>>
>>  First of all, thanks to David and Luigi for their valuable comments.
>>
>>  I will wait for a while in order to include David=92s comments (perhaps
>> some other people has more suggestions).
>>
>>  These are the improvements of version 10 with respect to v9 (
>> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00486.html)
>>
>>  - I have shortened paragraph 1.
>>  - I have shortened and merged paragraphs 2 and 3.
>>  - I have moved paragraph 4 to the third place, in order to set clearer
>> what we want: replacing RFC4170 with a widened proposal. As David
>> suggested, I have also shortened the text and it is now more
>> straightforward.
>>  - I have clearly stated which protocols will be used on each layer. The
>> negotiation mechanism is still necessary, since different options are
>> considered e.g. for header compression. The one to be used will depend o=
n
>> the scenario and the processing capacity of the two optimizers.
>>  - I have significantly shortened the description of the scenarios.
>>  - I have removed paragraph 6, which included the savings figures.
>>  - I have included the replacement of RFC4170 in the first milestone.
>>
>>  Thanks!
>>
>>  Jose
>>
>>   *De:* Black, David [mailto:david.black@emc.com <david.black@emc.com>]
>> *Enviado el:* s=E1bado, 04 de enero de 2014 4:05
>> *Para:* Jose Saldana; tcmtf@ietf.org; tsv-area@ietf.org
>> *CC:* Martin Stiemerling; Black, David
>> *Asunto:* RE: TCMTF-Feedback about a possible BoF in London
>>
>>  A second BoF has the explicit goal of forming a WG, as a third BoF
>>  is not permitted.  In that regard, the new charter seems long and
>>  somewhat lacking in focus.  Two key things I look for in a proposed
>>  charter are what problem (or problems) the proposed WG is looking to
>>  solve and an initial approach to the problem or problems.
>>
>>  In the new draft charter, the problem statement appears to be in
>>  paragraph 4 with paragraph 1 providing important background.  The
>>  focus of the work appears to be on extending TCRTP (RFC 4170) to
>>  UDP and to include new compression protocols.  In contrast, I have
>>  a hard time discerning the initial approach from the new draft charter.
>>
>>  In light of this, there are a few things that I wish the new
>>  draft charter had definitive proposals for:
>>
>>        a) Whether to replace RFC 4170 vs. write a new RFC (could be
>>              UDP-only or UDP + RTP/UDP) as a complement to RFC 4170.
>>        b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC (RFC 2507
>> ?).
>>              Non-use of ECRTP would be a major change to 4170, and I
>>  wonder about IPHC, as opposed to the ROHCv2 profiles.
>>        c) Analogies to b) for the Mux and Tunnel layers of the stack.
>>
>>  Overall, it looks like the first task of the WG is to select the
>> protocol
>>  stack to standardize - I have misgivings about that, and would prefer t=
o
>>  see a concrete proposal in a crisp charter that ran along the following
>>  lines, naming the protocols to be used:
>>
>>  1) RFC 4170 does X, and needs the following changes/additions: X, Y, Z.
>>  2) The WG will replace RFC 4170 with a new RFC that contains: A, B, C.
>>
>>  A specific proposal or proposals for the protocol stack or stacks
>>  would also narrow the scope of item 9 in the charter on the negotiation
>>  mechanism.  I also don=92t see a goal/milestone listed for an extension=
 to
>>  or replacement for RFC 4170.
>>
>>  I=92d prefer to see a much shorter more focused draft charter.  There=
=92s a
>>  bunch of background material that does not seem crucial to the charter,
>>  starting w/paragraphs 2 and 3.
>>
>>  Thanks,
>> --David
>>
>>   *From:* tsv-area [mailto:tsv-area-bounces@ietf.org<tsv-area-bounces@ie=
tf.org>
>> ] *On Behalf Of *Jose Saldana
>> *Sent:* Friday, December 20, 2013 4:26 AM
>> *To:* tcmtf@ietf.org; tsv-area@ietf.org
>> *Cc:* Martin Stiemerling
>> *Subject:* TCMTF-Feedback about a possible BoF in London
>>
>>  Hi all,
>>
>>  After the feedback received in the BoF in Berlin, we have updated the
>> TCM-TF charter and the two drafts. We have tried to solve all the proble=
ms
>> raised during the session.
>>
>>  Our plan is to request a new BoF in London next March, so we would like
>> to know your opinion about these two questions:
>>
>>
>>  1.  Is the new, reduced scope of TCM-TF suitable to form a working
>> group?
>>
>>
>>  2. We would like to kindly ask people who think that a TCM-TF Working
>> group should be formed, to come forward and send an e-mail to the
>> tsv-area@ietf.org  mailing list stating it.
>>
>>
>>  This feedback will allow us to get a better idea of the convenience of
>> a BoF.
>>
>>  The new charter is here:
>> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html
>>  This is the old one (presented in Berlin):
>> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.html
>>
>>  In these links you can see the differences between the new versions of
>> the drafts and the old ones:
>>
>> http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&ur=
l2=3Ddraft-saldana-tsvwg-tcmtf-05.txt
>>
>> http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.=
txt&url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt
>>
>>
>>  The main improvements are:
>>
>>  - TCP optimization has been removed
>>  - The classification of the scenarios has been refined and improved.
>> Some of them have been removed
>>  - A section about energy consumption has been added to the main draft
>>  - A reference to the potential problem of the MTU and packet loss has
>> been added
>>  - The problem of the added delays is studied in detail in the second
>> draft
>>
>>  - The improvements of the charter are summarized here:
>> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.html
>>
>>
>>  Best regards,
>>
>>  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 e=
l 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
>
>


--=20
Charles Oloo
WEBMASTER
Tel: +254 721 909757

--001a1139b400de92bf04f0b167f1
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Dear All<br><br>I wish to convey support the cre=
ation of the <span lang=3D"EN-US">TCM-TF</span> WG in totality as it will m=
ostly benefit the communities in developing countries where the internet an=
d bandwidth if expensive, especially here in Kenya where internet usage is =
growing at tremendous speeds. The current gov plans for free laptops for pr=
imary schools will further increase the need for more bandwidth hence there=
 is need to start looking at opportunities and means to avail and sustain t=
he ambitious program. This is a challenge for some of us who can undertake =
initiatives to provide solutions for the communities.<br>
<br></div>Regards<br></div>Charles Oloo<br></div><div class=3D"gmail_extra"=
><br><br><div class=3D"gmail_quote">On Thu, Jan 23, 2014 at 6:05 PM,  <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:tcmtf-request@ietf.org" target=3D"_blank=
">tcmtf-request@ietf.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Send tcmtf mailing list submissions to<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=A0 =A0 =A0 =A0 <a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/tcmtf</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:tcmtf-request@ietf.org">tcmtf-request@iet=
f.org</a><br>
<br>
You can reach the person managing the list at<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:tcmtf-owner@ietf.org">tcmtf-owner@ietf.or=
g</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of tcmtf digest...&quot;<br>
<br>Today&#39;s Topics:<br>
<br>
=A0 =A01. TCM-TF 2nd BoF approved (Jose Saldana)<br>
=A0 =A02. Re: TCMTF-Feedback about a possible BoF in London<br>
=A0 =A0 =A0 (Mehmet Karaca (Alumni))<br>
<br><br>---------- Forwarded message ----------<br>From:=A0&quot;Jose Salda=
na&quot; &lt;<a href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&g=
t;<br>To:=A0&lt;<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>&gt;<br=
>Cc:=A0<a href=3D"mailto:tsv-area@ietf.org">tsv-area@ietf.org</a><br>
Date:=A0Thu, 23 Jan 2014 11:17:00 +0100<br>Subject:=A0[tcmtf] TCM-TF 2nd Bo=
F approved<br><div link=3D"blue" vlink=3D"purple" lang=3D"ES"><div><p class=
=3D"MsoNormal"><span lang=3D"EN-US">Hi all,<u></u><u></u></span></p><p clas=
s=3D"MsoNormal">
<span lang=3D"EN-US"><u></u>=A0<u></u></span></p><p class=3D"MsoNormal"><sp=
an lang=3D"EN-US">As you may know, the second TCM-TF <span>BoF</span> has b=
een approved, and it will be held in London next March.<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=A0<u></u></span></p><p =
class=3D"MsoNormal"><span lang=3D"EN-US"><a href=3D"http://trac.tools.ietf.=
org/bof/trac/wiki#Transport" target=3D"_blank">http://trac.tools.ietf.org/b=
of/trac/wiki#Transport</a><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=A0<u></u></span></p><p =
class=3D"MsoNormal"><span lang=3D"EN-US">We will work in the next weeks in =
order to prepare it well.<u></u><u></u></span></p><p class=3D"MsoNormal"><s=
pan lang=3D"EN-US"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Best regards and thanks,<u></u>=
<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=A0<u>=
</u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">Jose </span><spa=
n><u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></div><br><br>---------- =
Forwarded message ----------<br>From:=A0&quot;Mehmet Karaca (Alumni)&quot; =
&lt;<a href=3D"mailto:mehmetkrc@sabanciuniv.edu">mehmetkrc@sabanciuniv.edu<=
/a>&gt;<br>
To:=A0FERNANDO PASCUAL BLANCO &lt;<a href=3D"mailto:fpb@tid.es">fpb@tid.es<=
/a>&gt;<br>Cc:=A0&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;, Tina T=
SOU &lt;<a href=3D"mailto:Tina.Tsou.Zouting@huawei.com">Tina.Tsou.Zouting@h=
uawei.com</a>&gt;, &quot;Black, David&quot; &lt;<a href=3D"mailto:david.bla=
ck@emc.com">david.black@emc.com</a>&gt;, Jose Saldana &lt;<a href=3D"mailto=
:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt;, &quot;<a href=3D"mailto:ts=
v-area@ietf.org">tsv-area@ietf.org</a>&quot; &lt;<a href=3D"mailto:tsv-area=
@ietf.org">tsv-area@ietf.org</a>&gt;, Luigi Iannone &lt;<a href=3D"mailto:g=
gx@gigix.net">ggx@gigix.net</a>&gt;, Martin Stiemerling &lt;<a href=3D"mail=
to:mls.ietf@googlemail.com">mls.ietf@googlemail.com</a>&gt;<br>
Date:=A0Thu, 23 Jan 2014 17:05:37 +0200<br>Subject:=A0Re: [tcmtf] TCMTF-Fee=
dback about a possible BoF in London<br><div dir=3D"ltr">Dear All,<br><div>=
<br>I completely support the formation of the WG for TCMMF.=A0 I believe=20
that such protocols in TCMMF will be also=A0 beneficial from=A0 MAC layer
 point of view since whenever QoS is required and traffic is not tagged=20
at MAC layer (in cases where 802.11e is not supported or traffic is not tag=
ged at the source), traffic classification at=A0 higher layer (Layer 3 or a=
bove)
 will be very crucial for some level of=A0 QoS at MAC layer.<br>
<br>Best Regards and=A0 thanks!<br><br></div><div>Mehmet.<br></div></div><d=
iv class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Jan 9, =
2014 at 7:49 PM, FERNANDO PASCUAL BLANCO <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:fpb@tid.es" target=3D"_blank">fpb@tid.es</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word">
Hi all,
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>Just to say that I also co=
mpletely support the creation of the WG. There is no doubt that network pro=
tocols have evolved, and not always as we thought, and TCRTP needs to be wi=
der.<br>


<div>
<div>
<div style=3D"text-indent:0px;letter-spacing:normal;text-align:start;text-t=
ransform:none;white-space:normal;word-wrap:break-word;word-spacing:0px">
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:start;font-style:normal;font-weight:normal;line-height:normal;text-=
transform:none;font-size:12px;white-space:normal;margin:0cm 0cm 0.0001pt;fo=
nt-family:Helvetica;word-spacing:0px">


<br>
Regards,
<div>Fernando</div>
<br>
</div>
</div>
</div>
<br>
<div><div><div>
<div>On 09/01/2014, at 01:49, Tina TSOU &lt;<a href=3D"mailto:Tina.Tsou.Zou=
ting@huawei.com" target=3D"_blank">Tina.Tsou.Zouting@huawei.com</a>&gt; wro=
te:</div>
<br>
</div></div><blockquote type=3D"cite">
<div dir=3D"auto" style=3D"font-family:Helvetica;font-size:12px;font-style:=
normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-he=
ight:normal;text-align:start;text-indent:0px;text-transform:none;white-spac=
e:normal;word-spacing:0px">

<div><div>
<div><span style=3D"font-size:13pt">Dear all,</span></div>
<div>I&#39;m in favor of having a BoF in London, as the following problem s=
tatement seems valid and needs protocol work in IETF.</div>
<div>---</div>
<div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">In add=
ition to VoIP, in the last years we are witnessing the raise of new real-ti=
me services e.g. videoconferencing, telemedicine, video vigilance, online g=
aming, etc.</font></span></div>


<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">Due to=
 the need of interactivity, many of these services use small packets (some =
tens of bytes), since they have to=A0</font></span><span style=3D"font-fami=
ly:UICTFontTextStyleBody;font-size:12px">send
 frequent updates between the extremes of the communication. Their small da=
ta payloads incur significant overhead, and it becomes even higher when IPv=
6 is used, since the basic IPv6 header is twice the size of the IPv4 one.</=
span></div>


<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">In the=
 moments or places where network capacity gets scarce, allocating more band=
width is a possible solution, but it implies a recurring cost. However, the=
 inclusion of a pair of boxes
 able to optimize the traffic (reducing bandwidth and packets per second) w=
hen/where required is a one-time investment. We can do these three things:<=
/font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">a) hea=
der compression algorithms (e.g. ROHC) can be used for reducing the overhea=
d of each flow;</font></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">b) at =
the same time, tunneling can be used in order to allow the header-compresse=
d packets to travel end-to-end</font></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">c) com=
pressed packets belonging to different flows can be multiplexed together, i=
n order to share the tunnel overhead.</font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">These =
emerging real-time services which use bare UDP instead of UDP/RTP have beco=
me popular. In addition, a significant=A0</font></span><span style=3D"font-=
family:UICTFontTextStyleBody;font-size:12px">effort
 has been devoted to the deployment of new header compression methods with =
improved robustness (ROHC). So there is a need of widening the scope of RFC=
4170 in order to consider these new header compression methods, and also UD=
P in addition to UDP/RTP.</span></div>


<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">As a r=
esult, the next objectives can be achieved:</font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">* Sign=
ificant bandwidth reductions (as an example, bandwidth savings of 55% can b=
e obtained for VoIP if IPv4 is used, and 65% using IPv6. For certain online=
 games, 33% of the bandwidth
 can be saved for IPv4, and 55% when using IPv6).</font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">* A re=
duction of the amount of packets per second managed by the network. A reduc=
tion factor of 10 or 20 can easily be achieved. This can be translated into=
 smaller processing delays and
 energy savings in intermediate routers.</font></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
---</div>
<div><br>
</div>
<div>Thank you,</div>
<div>Tina</div>
</div>
<div><br>
On Jan 8, 2014, at 4:11 PM, &quot;Jose Saldana&quot; &lt;<a href=3D"mailto:=
jsaldana@unizar.es" style=3D"color:purple;text-decoration:underline" target=
=3D"_blank">jsaldana@unizar.es</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">Hi all.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">First of all, thanks to=
 David and Luigi for their valuable comments.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">I will wait for a while=
 in order to include David=92s comments (perhaps some other people has more=
 suggestions).</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">These are the improveme=
nts of version 10 with respect to v9 (</span><a href=3D"http://www.ietf.org=
/mail-archive/web/tcmtf/current/msg00486.html" style=3D"color:purple;text-d=
ecoration:underline" target=3D"_blank"><span lang=3D"EN-US">http://www.ietf=
.org/mail-archive/web/tcmtf/current/msg00486.html</span></a><span lang=3D"E=
N-US">)</span><span style=3D"color:rgb(31,73,125)" lang=3D"EN-US"></span></=
div>


<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have shortened para=
graph 1.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have shortened and =
merged paragraphs 2 and 3.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have moved paragrap=
h 4 to the third place, in order to set clearer what we want: replacing RFC=
4170 with a widened proposal. As David suggested, I have also shortened the=
 text and it is now more straightforward.</span></div>


<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have clearly stated=
 which protocols will be used on each layer. The negotiation mechanism is s=
till necessary, since different options are considered e.g. for header comp=
ression. The one to be used will depend
 on the scenario and the processing capacity of the two optimizers.</span><=
/div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have significantly =
shortened the description of the scenarios.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have removed paragr=
aph 6, which included the savings figures.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have included the r=
eplacement of RFC4170 in the first milestone.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">Thanks!</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">Jose</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div>
<div style=3D"border-style:solid none none;border-top-color:rgb(181,196,223=
);border-top-width:1pt;padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-=
US">De:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-ser=
if" lang=3D"EN-US"><span>=A0</span>Black, David [</span><span style=3D"font=
-size:10pt;font-family:Tahoma,sans-serif"><a href=3D"mailto:david.black@emc=
.com" style=3D"color:purple;text-decoration:underline" target=3D"_blank"><s=
pan lang=3D"EN-US">mailto:david.black@emc.com</span></a></span><span style=
=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">]<span>=A0=
</span><br>


<b>Enviado el:</b><span>=A0</span>s=E1bado, 04 de enero de 2014 4:05<br>
<b>Para:</b><span>=A0</span>Jose Saldana;<span>=A0</span></span><span style=
=3D"font-size:10pt;font-family:Tahoma,sans-serif"><a href=3D"mailto:tcmtf@i=
etf.org" style=3D"color:purple;text-decoration:underline" target=3D"_blank"=
><span lang=3D"EN-US">tcmtf@ietf.org</span></a></span><span style=3D"font-s=
ize:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">;<span>=A0</span></s=
pan><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif"><a href=3D=
"mailto:tsv-area@ietf.org" style=3D"color:purple;text-decoration:underline"=
 target=3D"_blank"><span lang=3D"EN-US">tsv-area@ietf.org</span></a></span>=
<span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US"=
><br>


<b>CC:</b><span>=A0</span>Martin Stiemerling; Black, David<br>
<b>Asunto:</b><span>=A0</span>RE: TCMTF-Feedback about a possible BoF in Lo=
ndon</span></div>
</div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">A second BoF has the explicit goal of forming a WG, as a third BoF</sp=
an></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">is not permitted.=A0 In that regard, the new charter seems long and</s=
pan></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">somewhat lacking in focus.=A0 Two key things I look for in a proposed<=
/span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">charter are what problem (or problems) the proposed WG is looking to</=
span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">solve and an initial approach to the problem or problems.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">In the new draft charter, the problem statement appears to be in</span=
></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">paragraph 4 with paragraph 1 providing important background.=A0 The</s=
pan></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">focus of the work appears to be on extending TCRTP (RFC 4170) to</span=
></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">UDP and to include new compression protocols.=A0 In contrast, I have</=
span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">a hard time discerning the initial approach from the new draft charter=
.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">In light of this, there are a few things that I wish the new</span></d=
iv>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">draft charter had definitive proposals for:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0 a) Whether to replace RFC 4170 vs. write a new RFC (co=
uld be</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 UDP-only or UDP + RTP/UDP) as a comp=
lement to RFC 4170.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0 b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC=
 (RFC 2507 ?).</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Non-use of ECRTP would be a major ch=
ange to 4170, and I</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt 36pt;font-size:11pt;font-family:Calib=
ri,sans-serif;text-indent:36pt">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">wonder about IPHC, as opposed to the ROHCv2 profiles.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0 c) Analogies to b) for the Mux and Tunnel layers of th=
e stack.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">Overall, it looks like the first task of the WG is to select the proto=
col</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">stack to standardize - I have misgivings about that, and would prefer =
to</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">see a concrete proposal in a crisp charter that ran along the followin=
g</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">lines, naming the protocols to be used:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">1) RFC 4170 does X, and needs the following changes/additions: X, Y, Z=
.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">2) The WG will replace RFC 4170 with a new RFC that contains: A, B, C.=
</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">A specific proposal or proposals for the protocol stack or stacks</spa=
n></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">would also narrow the scope of item 9 in the charter on the negotiatio=
n</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">mechanism.=A0 I also don=92t see a goal/milestone listed for an extens=
ion to</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">or replacement for RFC 4170.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">I=92d prefer to see a much shorter more focused draft charter.=A0 Ther=
e=92s a</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">bunch of background material that does not seem crucial to the charter=
,</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">starting w/paragraphs 2 and 3.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">Thanks,<br>
--David</span><span style=3D"font-family:&#39;Courier New&#39;" lang=3D"EN-=
US"></span></div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"border-style:none none none solid;border-left-color:blue;bord=
er-left-width:1.5pt;padding:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-style:solid none none;border-top-color:rgb(181,196,223=
);border-top-width:1pt;padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-=
US">From:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-s=
erif" lang=3D"EN-US"><span>=A0</span>tsv-area [</span><a href=3D"mailto:tsv=
-area-bounces@ietf.org" style=3D"color:purple;text-decoration:underline" ta=
rget=3D"_blank"><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif=
" lang=3D"EN-US">mailto:tsv-area-bounces@ietf.org</span></a><span style=3D"=
font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">]<span>=A0</sp=
an><b>On
 Behalf Of<span>=A0</span></b>Jose Saldana<br>
<b>Sent:</b><span>=A0</span>Friday, December 20, 2013 4:26 AM<br>
<b>To:</b><span>=A0</span></span><a href=3D"mailto:tcmtf@ietf.org" style=3D=
"color:purple;text-decoration:underline" target=3D"_blank"><span style=3D"f=
ont-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">tcmtf@ietf.org<=
/span></a><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=
=3D"EN-US">;<span>=A0</span></span><a href=3D"mailto:tsv-area@ietf.org" sty=
le=3D"color:purple;text-decoration:underline" target=3D"_blank"><span style=
=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">tsv-area@i=
etf.org</span></a><span style=3D"font-size:10pt;font-family:Tahoma,sans-ser=
if" lang=3D"EN-US"><br>


<b>Cc:</b><span>=A0</span>Martin Stiemerling<br>
<b>Subject:</b><span>=A0</span>TCMTF-Feedback about a possible BoF in Londo=
n</span></div>
</div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">Hi all,</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">After the feedback received in the BoF in Berlin, we h=
ave updated the TCM-TF charter and the two drafts. We have tried to solve a=
ll the problems raised during the session.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">Our plan is to request a new BoF in London next March,=
 so we would like to know your opinion about these two questions:</span></d=
iv>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">1. =A0Is the new, reduced scope of TCM-TF suitable to =
form a working group?</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">2. We would like to kindly ask people who think that a=
 TCM-TF Working group should be formed, to come forward and send an e-mail =
to the<span>=A0</span></span><a href=3D"mailto:tsv-area@ietf.org" style=3D"=
color:purple;text-decoration:underline" target=3D"_blank"><span lang=3D"EN-=
US">tsv-area@ietf.org</span></a><span lang=3D"EN-US"><span>=A0</span>=A0mai=
ling
 list stating it.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">This feedback will allow us to get a better idea of th=
e convenience of a BoF.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">The new charter is here:<span>=A0</span></span><a href=
=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html" style=
=3D"color:purple;text-decoration:underline" target=3D"_blank"><span lang=3D=
"EN-US">http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html</s=
pan></a><span lang=3D"EN-US"></span></div>


<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">This is the old one (presented in Berlin):<span>=A0</s=
pan></span><a href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/ms=
g00368.html" style=3D"color:purple;text-decoration:underline" target=3D"_bl=
ank"><span lang=3D"EN-US">http://www.ietf.org/mail-archive/web/tcmtf/curren=
t/msg00368.html</span></a><span lang=3D"EN-US"></span></div>


<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">In these links you can see the differences between the=
 new versions of the drafts and the old ones:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<a href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-0=
6.txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt" style=3D"color:purple;te=
xt-decoration:underline" target=3D"_blank"><span lang=3D"EN-US">http://tool=
s.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&amp;url2=3Ddraft=
-saldana-tsvwg-tcmtf-05.txt</span></a><span lang=3D"EN-US"></span></div>


<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<a href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-t=
cmtf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt" style=3D"col=
or:purple;text-decoration:underline" target=3D"_blank"><span lang=3D"EN-US"=
>http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.tx=
t&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt</span></a><span lang=3D=
"EN-US"></span></div>


<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">The main improvements are:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- TCP optimization has been removed</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- The classification of the scenarios has been refined=
 and improved. Some of them have been removed</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- A section about energy consumption has been added to=
 the main draft</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- A reference to the potential problem of the MTU and =
packet loss has been added</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- The problem of the added delays is studied in detail=
 in the second draft</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- The improvements of the charter are summarized here:=
<span>=A0</span></span><a href=3D"http://www.ietf.org/mail-archive/web/tcmt=
f/current/msg00466.html" style=3D"color:purple;text-decoration:underline" t=
arget=3D"_blank"><span lang=3D"EN-US">http://www.ietf.org/mail-archive/web/=
tcmtf/current/msg00466.html</span></a><span lang=3D"EN-US"></span></div>


<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">Best regards,</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">Jose</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
</div>
</div>
</blockquote>
<blockquote type=3D"cite">
<div></div>
</blockquote></div></div>
_______________________________________________<div><br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org" style=3D"color:purple;text-decoration:und=
erline" target=3D"_blank">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color:purp=
le;text-decoration:underline" target=3D"_blank">https://www.ietf.org/mailma=
n/listinfo/tcmtf</a></div></div>
</blockquote>
</div>
<br>
</div>
</div><div>
<br>
<hr>
<font color=3D"Gray" size=3D"1" face=3D"Arial"><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" target=3D"_blank">=
http://www.tid.es/ES/PAGINAS/disclaimer.aspx</a><br>
</font>
</div></div>

<br>_______________________________________________<br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org" target=3D"_blank">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/tcmtf</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/tcmtf</a><br>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br>Charles Oloo<br>WEB=
MASTER<br>Tel: +254 721 909757<br>=A0=A0=A0 =A0=A0 <br><input type=3D"hidde=
n"><input type=3D"hidden"><div></div><input type=3D"hidden"><input type=3D"=
hidden"><div></div>

</div>

--001a1139b400de92bf04f0b167f1--

From mehmet.karaca@airties.com  Fri Jan 24 01:00:32 2014
Return-Path: <mehmet.karaca@airties.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93E321A01DD for <tcmtf@ietfa.amsl.com>; Fri, 24 Jan 2014 01:00:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.635
X-Spam-Level: 
X-Spam-Status: No, score=0.635 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, ONE_TIME=0.714, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YMcPUiX6AeT for <tcmtf@ietfa.amsl.com>; Fri, 24 Jan 2014 01:00:27 -0800 (PST)
Received: from mail-ee0-f42.google.com (mail-ee0-f42.google.com [74.125.83.42]) by ietfa.amsl.com (Postfix) with ESMTP id ED1B51A0199 for <tcmtf@ietf.org>; Fri, 24 Jan 2014 01:00:26 -0800 (PST)
Received: by mail-ee0-f42.google.com with SMTP id e49so828367eek.1 for <tcmtf@ietf.org>; Fri, 24 Jan 2014 01:00:25 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=NfhHTOChefrGG2UvWLuAgpbQXh8T7WXEvVNQJJANg7w=; b=OP0UAHS9ph/JeO6+qn8wUrwVAmRD9ouXuB0BEbruyNy1zl94LZfTbgXunCQ6TBNB3K Z3wLeBxsoKI7khfWD7RA1owW5fswjmD+nfz6e7PYodrRGs8G2HJvjprCYQwM2cJUOZjd +HJhk/N90N0xerAOdN4TjJ5Kkc91rusUepuNoWGzzIsjeY8bL+PpM1tL5wDB5IE8pyM6 bep12ZdtvFhSKfUeMg4ryn30hklE6+cKbRIxzl/05LZfnuCT4VLLxfSEhgSRtk/lbDwu +rWr7ViLE1X8S74eIQl4akEAWObPEjzZyuLu31v2oSEUtbh2uJEYXsHaaylvIx7TJv0u Johw==
X-Gm-Message-State: ALoCoQmO/TpFYflP2lhg1Cpn5QBz1lRcOiN1mVNDj06YBSuumrFTdbjM4KrAi0JIMGK5bgQHsQyEzv0Bwz1iKL8JKzTNgTM1Rw==
MIME-Version: 1.0
X-Received: by 10.15.109.196 with SMTP id cf44mr11325284eeb.12.1390554025416;  Fri, 24 Jan 2014 01:00:25 -0800 (PST)
Received: by 10.14.4.130 with HTTP; Fri, 24 Jan 2014 01:00:25 -0800 (PST)
In-Reply-To: <mailman.1540.1390544655.2325.tcmtf@ietf.org>
References: <mailman.1540.1390544655.2325.tcmtf@ietf.org>
Date: Fri, 24 Jan 2014 11:00:25 +0200
Message-ID: <CAMEqBMHAtStgKuGXLKpEsMvwaMJWUkmwJdLmLxRYeYmY4Hq_1w@mail.gmail.com>
From: Mehmet Karaca <mehmet.karaca@airties.com>
To: tcmtf@ietf.org
Content-Type: multipart/alternative; boundary=089e016814ccb9eb3b04f0b396b7
Subject: Re: [tcmtf] tcmtf Digest, Vol 19, Issue 13
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
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, 24 Jan 2014 09:00:32 -0000

--089e016814ccb9eb3b04f0b396b7
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Dear All,
Sorry for re-sending this message,

I completely support the formation of the WG for TCM-TF.  I believe that
such protocols in TCMMF will be also  beneficial from  MAC layer point of
view since whenever QoS is required and traffic is not tagged at MAC layer
(in cases where 802.11e is not supported or traffic is not tagged at the
source), traffic classification at  higher layer (Layer 3 or above) will be
very crucial for some level of  QoS at MAC layer.

Best Regards and  thanks!


Mehmet.


On Fri, Jan 24, 2014 at 8:24 AM, <tcmtf-request@ietf.org> wrote:

> Send tcmtf mailing list submissions to
>         tcmtf@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.ietf.org/mailman/listinfo/tcmtf
> or, via email, send a message with subject or body 'help' to
>         tcmtf-request@ietf.org
>
> You can reach the person managing the list at
>         tcmtf-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of tcmtf digest..."
>
> Today's Topics:
>
>    1. Re: tcmtf Digest, Vol 19, Issue 11 (Charles Oloo)
>
>
> ---------- Forwarded message ----------
> From: Charles Oloo <oloo6382@gmail.com>
> To: tcmtf@ietf.org
> Cc:
> Date: Fri, 24 Jan 2014 09:24:09 +0300
> Subject: Re: [tcmtf] tcmtf Digest, Vol 19, Issue 11
> Dear All
>
> I wish to convey support the creation of the TCM-TF WG in totality as it
> will mostly benefit the communities in developing countries where the
> internet and bandwidth if expensive, especially here in Kenya where
> internet usage is growing at tremendous speeds. The current gov plans for
> free laptops for primary schools will further increase the need for more
> bandwidth hence there is need to start looking at opportunities and means
> to avail and sustain the ambitious program. This is a challenge for some =
of
> us who can undertake initiatives to provide solutions for the communities=
.
>
> Regards
> Charles Oloo
>
>
> On Thu, Jan 23, 2014 at 6:05 PM, <tcmtf-request@ietf.org> wrote:
>
>> Send tcmtf mailing list submissions to
>>         tcmtf@ietf.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         https://www.ietf.org/mailman/listinfo/tcmtf
>> or, via email, send a message with subject or body 'help' to
>>         tcmtf-request@ietf.org
>>
>> You can reach the person managing the list at
>>         tcmtf-owner@ietf.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of tcmtf digest..."
>>
>> Today's Topics:
>>
>>    1. TCM-TF 2nd BoF approved (Jose Saldana)
>>    2. Re: TCMTF-Feedback about a possible BoF in London
>>       (Mehmet Karaca (Alumni))
>>
>>
>> ---------- Forwarded message ----------
>> From: "Jose Saldana" <jsaldana@unizar.es>
>> To: <tcmtf@ietf.org>
>> Cc: tsv-area@ietf.org
>> Date: Thu, 23 Jan 2014 11:17:00 +0100
>> Subject: [tcmtf] TCM-TF 2nd BoF approved
>>
>> Hi all,
>>
>>
>>
>> As you may know, the second TCM-TF BoF has been approved, and it will be
>> held in London next March.
>>
>>
>>
>> http://trac.tools.ietf.org/bof/trac/wiki#Transport
>>
>>
>>
>> We will work in the next weeks in order to prepare it well.
>>
>>
>>
>> Best regards and thanks,
>>
>>
>>
>> Jose
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: "Mehmet Karaca (Alumni)" <mehmetkrc@sabanciuniv.edu>
>> To: FERNANDO PASCUAL BLANCO <fpb@tid.es>
>> Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>, Tina TSOU <
>> Tina.Tsou.Zouting@huawei.com>, "Black, David" <david.black@emc.com>,
>> Jose Saldana <jsaldana@unizar.es>, "tsv-area@ietf.org" <tsv-area@ietf.or=
g>,
>> Luigi Iannone <ggx@gigix.net>, Martin Stiemerling <
>> mls.ietf@googlemail.com>
>> Date: Thu, 23 Jan 2014 17:05:37 +0200
>> Subject: Re: [tcmtf] TCMTF-Feedback about a possible BoF in London
>> Dear All,
>>
>> I completely support the formation of the WG for TCMMF.  I believe that
>> such protocols in TCMMF will be also  beneficial from  MAC layer point o=
f
>> view since whenever QoS is required and traffic is not tagged at MAC lay=
er
>> (in cases where 802.11e is not supported or traffic is not tagged at the
>> source), traffic classification at  higher layer (Layer 3 or above) will=
 be
>> very crucial for some level of  QoS at MAC layer.
>>
>> Best Regards and  thanks!
>>
>> Mehmet.
>>
>>
>> On Thu, Jan 9, 2014 at 7:49 PM, FERNANDO PASCUAL BLANCO <fpb@tid.es>wrot=
e:
>>
>>>  Hi all,
>>>
>>>  Just to say that I also completely support the creation of the WG.
>>> There is no doubt that network protocols have evolved, and not always a=
s we
>>> thought, and TCRTP needs to be wider.
>>>
>>> Regards,
>>> Fernando
>>>
>>>
>>>  On 09/01/2014, at 01:49, Tina TSOU <Tina.Tsou.Zouting@huawei.com>
>>> wrote:
>>>
>>>   Dear all,
>>> I'm in favor of having a BoF in London, as the following problem
>>> statement seems valid and needs protocol work in IETF.
>>> ---
>>>  In addition to VoIP, in the last years we are witnessing the raise of
>>> new real-time services e.g. videoconferencing, telemedicine, video
>>> vigilance, online gaming, etc.
>>>
>>>
>>>  Due to the need of interactivity, many of these services use small
>>> packets (some tens of bytes), since they have to send frequent updates
>>> between the extremes of the communication. Their small data payloads in=
cur
>>> significant overhead, and it becomes even higher when IPv6 is used, sin=
ce
>>> the basic IPv6 header is twice the size of the IPv4 one.
>>>
>>>
>>>  In the moments or places where network capacity gets scarce,
>>> allocating more bandwidth is a possible solution, but it implies a
>>> recurring cost. However, the inclusion of a pair of boxes able to optim=
ize
>>> the traffic (reducing bandwidth and packets per second) when/where requ=
ired
>>> is a one-time investment. We can do these three things:
>>>
>>>
>>>  a) header compression algorithms (e.g. ROHC) can be used for reducing
>>> the overhead of each flow;
>>>  b) at the same time, tunneling can be used in order to allow the
>>> header-compressed packets to travel end-to-end
>>>  c) compressed packets belonging to different flows can be multiplexed
>>> together, in order to share the tunnel overhead.
>>>
>>>
>>>  These emerging real-time services which use bare UDP instead of
>>> UDP/RTP have become popular. In addition, a significant effort has been
>>> devoted to the deployment of new header compression methods with improv=
ed
>>> robustness (ROHC). So there is a need of widening the scope of RFC4170 =
in
>>> order to consider these new header compression methods, and also UDP in
>>> addition to UDP/RTP.
>>>
>>>
>>>  As a result, the next objectives can be achieved:
>>>
>>>
>>>  * Significant bandwidth reductions (as an example, bandwidth savings
>>> of 55% can be obtained for VoIP if IPv4 is used, and 65% using IPv6. Fo=
r
>>> certain online games, 33% of the bandwidth can be saved for IPv4, and 5=
5%
>>> when using IPv6).
>>>
>>>
>>>  * A reduction of the amount of packets per second managed by the
>>> network. A reduction factor of 10 or 20 can easily be achieved. This ca=
n be
>>> translated into smaller processing delays and energy savings in
>>> intermediate routers.
>>>  ---
>>>
>>>  Thank you,
>>> Tina
>>>
>>> On Jan 8, 2014, at 4:11 PM, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>>
>>>   Hi all.
>>>
>>>  First of all, thanks to David and Luigi for their valuable comments.
>>>
>>>  I will wait for a while in order to include David=92s comments (perhap=
s
>>> some other people has more suggestions).
>>>
>>>  These are the improvements of version 10 with respect to v9 (
>>> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00486.html)
>>>
>>>  - I have shortened paragraph 1.
>>>  - I have shortened and merged paragraphs 2 and 3.
>>>  - I have moved paragraph 4 to the third place, in order to set clearer
>>> what we want: replacing RFC4170 with a widened proposal. As David
>>> suggested, I have also shortened the text and it is now more
>>> straightforward.
>>>  - I have clearly stated which protocols will be used on each layer.
>>> The negotiation mechanism is still necessary, since different options a=
re
>>> considered e.g. for header compression. The one to be used will depend =
on
>>> the scenario and the processing capacity of the two optimizers.
>>>  - I have significantly shortened the description of the scenarios.
>>>  - I have removed paragraph 6, which included the savings figures.
>>>  - I have included the replacement of RFC4170 in the first milestone.
>>>
>>>  Thanks!
>>>
>>>  Jose
>>>
>>>   *De:* Black, David [mailto:david.black@emc.com <david.black@emc.com>]
>>> *Enviado el:* s=E1bado, 04 de enero de 2014 4:05
>>> *Para:* Jose Saldana; tcmtf@ietf.org; tsv-area@ietf.org
>>> *CC:* Martin Stiemerling; Black, David
>>> *Asunto:* RE: TCMTF-Feedback about a possible BoF in London
>>>
>>>  A second BoF has the explicit goal of forming a WG, as a third BoF
>>>  is not permitted.  In that regard, the new charter seems long and
>>>  somewhat lacking in focus.  Two key things I look for in a proposed
>>>  charter are what problem (or problems) the proposed WG is looking to
>>>  solve and an initial approach to the problem or problems.
>>>
>>>  In the new draft charter, the problem statement appears to be in
>>>  paragraph 4 with paragraph 1 providing important background.  The
>>>  focus of the work appears to be on extending TCRTP (RFC 4170) to
>>>  UDP and to include new compression protocols.  In contrast, I have
>>>  a hard time discerning the initial approach from the new draft charter=
.
>>>
>>>  In light of this, there are a few things that I wish the new
>>>  draft charter had definitive proposals for:
>>>
>>>        a) Whether to replace RFC 4170 vs. write a new RFC (could be
>>>              UDP-only or UDP + RTP/UDP) as a complement to RFC 4170.
>>>        b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC (RFC 2507
>>> ?).
>>>              Non-use of ECRTP would be a major change to 4170, and I
>>>  wonder about IPHC, as opposed to the ROHCv2 profiles.
>>>        c) Analogies to b) for the Mux and Tunnel layers of the stack.
>>>
>>>  Overall, it looks like the first task of the WG is to select the
>>> protocol
>>>  stack to standardize - I have misgivings about that, and would prefer
>>> to
>>>  see a concrete proposal in a crisp charter that ran along the followin=
g
>>>  lines, naming the protocols to be used:
>>>
>>>  1) RFC 4170 does X, and needs the following changes/additions: X, Y, Z=
.
>>>  2) The WG will replace RFC 4170 with a new RFC that contains: A, B, C.
>>>
>>>  A specific proposal or proposals for the protocol stack or stacks
>>>  would also narrow the scope of item 9 in the charter on the negotiatio=
n
>>>  mechanism.  I also don=92t see a goal/milestone listed for an extensio=
n
>>> to
>>>  or replacement for RFC 4170.
>>>
>>>  I=92d prefer to see a much shorter more focused draft charter.  There=
=92s a
>>>  bunch of background material that does not seem crucial to the charter=
,
>>>  starting w/paragraphs 2 and 3.
>>>
>>>  Thanks,
>>> --David
>>>
>>>   *From:* tsv-area [mailto:tsv-area-bounces@ietf.org<tsv-area-bounces@i=
etf.org>
>>> ] *On Behalf Of *Jose Saldana
>>> *Sent:* Friday, December 20, 2013 4:26 AM
>>> *To:* tcmtf@ietf.org; tsv-area@ietf.org
>>> *Cc:* Martin Stiemerling
>>> *Subject:* TCMTF-Feedback about a possible BoF in London
>>>
>>>  Hi all,
>>>
>>>  After the feedback received in the BoF in Berlin, we have updated the
>>> TCM-TF charter and the two drafts. We have tried to solve all the probl=
ems
>>> raised during the session.
>>>
>>>  Our plan is to request a new BoF in London next March, so we would
>>> like to know your opinion about these two questions:
>>>
>>>
>>>  1.  Is the new, reduced scope of TCM-TF suitable to form a working
>>> group?
>>>
>>>
>>>  2. We would like to kindly ask people who think that a TCM-TF Working
>>> group should be formed, to come forward and send an e-mail to the
>>> tsv-area@ietf.org  mailing list stating it.
>>>
>>>
>>>  This feedback will allow us to get a better idea of the convenience of
>>> a BoF.
>>>
>>>  The new charter is here:
>>> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html
>>>  This is the old one (presented in Berlin):
>>> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00368.html
>>>
>>>  In these links you can see the differences between the new versions of
>>> the drafts and the old ones:
>>>
>>> http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&u=
rl2=3Ddraft-saldana-tsvwg-tcmtf-05.txt
>>>
>>> http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02=
.txt&url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt
>>>
>>>
>>>  The main improvements are:
>>>
>>>  - TCP optimization has been removed
>>>  - The classification of the scenarios has been refined and improved.
>>> Some of them have been removed
>>>  - A section about energy consumption has been added to the main draft
>>>  - A reference to the potential problem of the MTU and packet loss has
>>> been added
>>>  - The problem of the added delays is studied in detail in the second
>>> draft
>>>
>>>  - The improvements of the charter are summarized here:
>>> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00466.html
>>>
>>>
>>>  Best regards,
>>>
>>>  Jose
>>>
>>>
>>>   _______________________________________________
>>>
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>
>>>
>>>
>>> ------------------------------
>>>
>>> Este mensaje se dirige exclusivamente a su destinatario. Puede consulta=
r
>>> 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 an=
d
>>> 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
>>
>>
>
>
> --
> Charles Oloo
> WEBMASTER
> Tel: +254 721 909757
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>
>


--=20
--=20

Mehmet Karaca, PhD

System Engineer, CTO Office

AirTies Wireless Networks (www.airties.com)



M: +90 (554) 718  9009

E: mehmet.karaca@airties.com <ece.gelal@airties.com>

--=20

Information in this email including any attachments may be privileged,=20
confidential and is intended exclusively for the addressee. The views=20
expressed may not be official policy, but the personal views of the=20
originator. If you have received it in error, please notify the sender by=
=20
return e-mail and delete it from your system. You should not reproduce,=20
distribute, store, retransmit, use or disclose its contents to anyone.

--089e016814ccb9eb3b04f0b396b7
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear All,<br><div class=3D"gmail_quote"><div dir=3D"ltr">S=
orry for re-sending this message,<br><br>I completely support the formation=
 of the WG for TCM-TF.=A0 I believe that such protocols in TCMMF will be al=
so=A0 beneficial from=A0 MAC layer point of view since whenever QoS is requ=
ired and traffic is not tagged at MAC layer (in cases where 802.11e is not =
supported or traffic is not tagged at the source), traffic classification a=
t=A0 higher layer (Layer 3 or above) will be very crucial for some level of=
=A0 QoS at MAC layer.<br>
<br>Best Regards and=A0 thanks!<font color=3D"#888888"><br><div><div><br><b=
r></div><div>Mehmet.</div></div></font></div></div><div class=3D"gmail_extr=
a"><br><br><div class=3D"gmail_quote">On Fri, Jan 24, 2014 at 8:24 AM,  <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:tcmtf-request@ietf.org" target=3D"_bla=
nk">tcmtf-request@ietf.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Send tcmtf mailing list submissions to<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=A0 =A0 =A0 =A0 <a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/tcmtf</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:tcmtf-request@ietf.org">tcmtf-request@iet=
f.org</a><br>
<br>
You can reach the person managing the list at<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:tcmtf-owner@ietf.org">tcmtf-owner@ietf.or=
g</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of tcmtf digest...&quot;<br>
<br>Today&#39;s Topics:<br>
<br>
=A0 =A01. Re: tcmtf Digest, Vol 19, Issue 11 (Charles Oloo)<br>
<br><br>---------- Forwarded message ----------<br>From:=A0Charles Oloo &lt=
;<a href=3D"mailto:oloo6382@gmail.com">oloo6382@gmail.com</a>&gt;<br>To:=A0=
<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>Cc:=A0<br>Date:=A0F=
ri, 24 Jan 2014 09:24:09 +0300<br>
Subject:=A0Re: [tcmtf] tcmtf Digest, Vol 19, Issue 11<br><div dir=3D"ltr"><=
div><div>Dear All<br><br>I wish to convey support the creation of the <span=
 lang=3D"EN-US">TCM-TF</span> WG in totality as it will mostly benefit the =
communities in developing countries where the internet and bandwidth if exp=
ensive, especially here in Kenya where internet usage is growing at tremend=
ous speeds. The current gov plans for free laptops for primary schools will=
 further increase the need for more bandwidth hence there is need to start =
looking at opportunities and means to avail and sustain the ambitious progr=
am. This is a challenge for some of us who can undertake initiatives to pro=
vide solutions for the communities.<br>

<br></div>Regards<br></div>Charles Oloo<br></div><div class=3D"gmail_extra"=
><br><br><div class=3D"gmail_quote">On Thu, Jan 23, 2014 at 6:05 PM,  <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:tcmtf-request@ietf.org" target=3D"_blank=
">tcmtf-request@ietf.org</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Send tcmtf mailing list submissions to<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:tcmtf@ietf.org" target=3D"_blank">tcmtf@i=
etf.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=A0 =A0 =A0 =A0 <a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/tcmtf</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:tcmtf-request@ietf.org" target=3D"_blank"=
>tcmtf-request@ietf.org</a><br>
<br>
You can reach the person managing the list at<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:tcmtf-owner@ietf.org" target=3D"_blank">t=
cmtf-owner@ietf.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of tcmtf digest...&quot;<br>
<br>Today&#39;s Topics:<br>
<br>
=A0 =A01. TCM-TF 2nd BoF approved (Jose Saldana)<br>
=A0 =A02. Re: TCMTF-Feedback about a possible BoF in London<br>
=A0 =A0 =A0 (Mehmet Karaca (Alumni))<br>
<br><br>---------- Forwarded message ----------<br>From:=A0&quot;Jose Salda=
na&quot; &lt;<a href=3D"mailto:jsaldana@unizar.es" target=3D"_blank">jsalda=
na@unizar.es</a>&gt;<br>To:=A0&lt;<a href=3D"mailto:tcmtf@ietf.org" target=
=3D"_blank">tcmtf@ietf.org</a>&gt;<br>
Cc:=A0<a href=3D"mailto:tsv-area@ietf.org" target=3D"_blank">tsv-area@ietf.=
org</a><br>
Date:=A0Thu, 23 Jan 2014 11:17:00 +0100<br>Subject:=A0[tcmtf] TCM-TF 2nd Bo=
F approved<br><div link=3D"blue" vlink=3D"purple" lang=3D"ES"><div><p class=
=3D"MsoNormal"><span lang=3D"EN-US">Hi all,<u></u><u></u></span></p><p clas=
s=3D"MsoNormal">

<span lang=3D"EN-US"><u></u>=A0<u></u></span></p><p class=3D"MsoNormal"><sp=
an lang=3D"EN-US">As you may know, the second TCM-TF <span>BoF</span> has b=
een approved, and it will be held in London next March.<u></u><u></u></span=
></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=A0<u></u></span></p><p =
class=3D"MsoNormal"><span lang=3D"EN-US"><a href=3D"http://trac.tools.ietf.=
org/bof/trac/wiki#Transport" target=3D"_blank">http://trac.tools.ietf.org/b=
of/trac/wiki#Transport</a><u></u><u></u></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=A0<u></u></span></p><p =
class=3D"MsoNormal"><span lang=3D"EN-US">We will work in the next weeks in =
order to prepare it well.<u></u><u></u></span></p><p class=3D"MsoNormal"><s=
pan lang=3D"EN-US"><u></u>=A0<u></u></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US">Best regards and thanks,<u></u>=
<u></u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=A0<u>=
</u></span></p><p class=3D"MsoNormal"><span lang=3D"EN-US">Jose </span><spa=
n><u></u><u></u></span></p>

<p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></div><br><br>---------- =
Forwarded message ----------<br>From:=A0&quot;Mehmet Karaca (Alumni)&quot; =
&lt;<a href=3D"mailto:mehmetkrc@sabanciuniv.edu" target=3D"_blank">mehmetkr=
c@sabanciuniv.edu</a>&gt;<br>

To:=A0FERNANDO PASCUAL BLANCO &lt;<a href=3D"mailto:fpb@tid.es" target=3D"_=
blank">fpb@tid.es</a>&gt;<br>Cc:=A0&quot;<a href=3D"mailto:tcmtf@ietf.org" =
target=3D"_blank">tcmtf@ietf.org</a>&quot; &lt;<a href=3D"mailto:tcmtf@ietf=
.org" target=3D"_blank">tcmtf@ietf.org</a>&gt;, Tina TSOU &lt;<a href=3D"ma=
ilto:Tina.Tsou.Zouting@huawei.com" target=3D"_blank">Tina.Tsou.Zouting@huaw=
ei.com</a>&gt;, &quot;Black, David&quot; &lt;<a href=3D"mailto:david.black@=
emc.com" target=3D"_blank">david.black@emc.com</a>&gt;, Jose Saldana &lt;<a=
 href=3D"mailto:jsaldana@unizar.es" target=3D"_blank">jsaldana@unizar.es</a=
>&gt;, &quot;<a href=3D"mailto:tsv-area@ietf.org" target=3D"_blank">tsv-are=
a@ietf.org</a>&quot; &lt;<a href=3D"mailto:tsv-area@ietf.org" target=3D"_bl=
ank">tsv-area@ietf.org</a>&gt;, Luigi Iannone &lt;<a href=3D"mailto:ggx@gig=
ix.net" target=3D"_blank">ggx@gigix.net</a>&gt;, Martin Stiemerling &lt;<a =
href=3D"mailto:mls.ietf@googlemail.com" target=3D"_blank">mls.ietf@googlema=
il.com</a>&gt;<br>

Date:=A0Thu, 23 Jan 2014 17:05:37 +0200<br>Subject:=A0Re: [tcmtf] TCMTF-Fee=
dback about a possible BoF in London<br><div dir=3D"ltr">Dear All,<br><div>=
<br>I completely support the formation of the WG for TCMMF.=A0 I believe=20
that such protocols in TCMMF will be also=A0 beneficial from=A0 MAC layer
 point of view since whenever QoS is required and traffic is not tagged=20
at MAC layer (in cases where 802.11e is not supported or traffic is not tag=
ged at the source), traffic classification at=A0 higher layer (Layer 3 or a=
bove)
 will be very crucial for some level of=A0 QoS at MAC layer.<br>
<br>Best Regards and=A0 thanks!<br><br></div><div>Mehmet.<br></div></div><d=
iv class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Jan 9, =
2014 at 7:49 PM, FERNANDO PASCUAL BLANCO <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:fpb@tid.es" target=3D"_blank">fpb@tid.es</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word">
Hi all,
<div><br>
</div>
<div><span style=3D"white-space:pre-wrap"></span>Just to say that I also co=
mpletely support the creation of the WG. There is no doubt that network pro=
tocols have evolved, and not always as we thought, and TCRTP needs to be wi=
der.<br>



<div>
<div>
<div style=3D"text-indent:0px;letter-spacing:normal;text-align:start;text-t=
ransform:none;white-space:normal;word-wrap:break-word;word-spacing:0px">
<div style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;tex=
t-align:start;font-style:normal;font-weight:normal;line-height:normal;text-=
transform:none;font-size:12px;white-space:normal;margin:0cm 0cm 0.0001pt;fo=
nt-family:Helvetica;word-spacing:0px">



<br>
Regards,
<div>Fernando</div>
<br>
</div>
</div>
</div>
<br>
<div><div><div>
<div>On 09/01/2014, at 01:49, Tina TSOU &lt;<a href=3D"mailto:Tina.Tsou.Zou=
ting@huawei.com" target=3D"_blank">Tina.Tsou.Zouting@huawei.com</a>&gt; wro=
te:</div>
<br>
</div></div><blockquote type=3D"cite">
<div dir=3D"auto" style=3D"font-family:Helvetica;font-size:12px;font-style:=
normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-he=
ight:normal;text-align:start;text-indent:0px;text-transform:none;white-spac=
e:normal;word-spacing:0px">


<div><div>
<div><span style=3D"font-size:13pt">Dear all,</span></div>
<div>I&#39;m in favor of having a BoF in London, as the following problem s=
tatement seems valid and needs protocol work in IETF.</div>
<div>---</div>
<div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">In add=
ition to VoIP, in the last years we are witnessing the raise of new real-ti=
me services e.g. videoconferencing, telemedicine, video vigilance, online g=
aming, etc.</font></span></div>



<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">Due to=
 the need of interactivity, many of these services use small packets (some =
tens of bytes), since they have to=A0</font></span><span style=3D"font-fami=
ly:UICTFontTextStyleBody;font-size:12px">send
 frequent updates between the extremes of the communication. Their small da=
ta payloads incur significant overhead, and it becomes even higher when IPv=
6 is used, since the basic IPv6 header is twice the size of the IPv4 one.</=
span></div>



<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">In the=
 moments or places where network capacity gets scarce, allocating more band=
width is a possible solution, but it implies a recurring cost. However, the=
 inclusion of a pair of boxes
 able to optimize the traffic (reducing bandwidth and packets per second) w=
hen/where required is a one-time investment. We can do these three things:<=
/font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">a) hea=
der compression algorithms (e.g. ROHC) can be used for reducing the overhea=
d of each flow;</font></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">b) at =
the same time, tunneling can be used in order to allow the header-compresse=
d packets to travel end-to-end</font></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">c) com=
pressed packets belonging to different flows can be multiplexed together, i=
n order to share the tunnel overhead.</font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">These =
emerging real-time services which use bare UDP instead of UDP/RTP have beco=
me popular. In addition, a significant=A0</font></span><span style=3D"font-=
family:UICTFontTextStyleBody;font-size:12px">effort
 has been devoted to the deployment of new header compression methods with =
improved robustness (ROHC). So there is a need of widening the scope of RFC=
4170 in order to consider these new header compression methods, and also UD=
P in addition to UDP/RTP.</span></div>



<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">As a r=
esult, the next objectives can be achieved:</font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">* Sign=
ificant bandwidth reductions (as an example, bandwidth savings of 55% can b=
e obtained for VoIP if IPv4 is used, and 65% using IPv6. For certain online=
 games, 33% of the bandwidth
 can be saved for IPv4, and 55% when using IPv6).</font></span></div>
<p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font=
-family:Calibri,sans-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">=A0</f=
ont></span></p>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US"><font size=3D"3" face=3D"UICTFontTextStyleBody">* A re=
duction of the amount of packets per second managed by the network. A reduc=
tion factor of 10 or 20 can easily be achieved. This can be translated into=
 smaller processing delays and
 energy savings in intermediate routers.</font></span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
---</div>
<div><br>
</div>
<div>Thank you,</div>
<div>Tina</div>
</div>
<div><br>
On Jan 8, 2014, at 4:11 PM, &quot;Jose Saldana&quot; &lt;<a href=3D"mailto:=
jsaldana@unizar.es" style=3D"color:purple;text-decoration:underline" target=
=3D"_blank">jsaldana@unizar.es</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">Hi all.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">First of all, thanks to=
 David and Luigi for their valuable comments.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">I will wait for a while=
 in order to include David=92s comments (perhaps some other people has more=
 suggestions).</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">These are the improveme=
nts of version 10 with respect to v9 (</span><a href=3D"http://www.ietf.org=
/mail-archive/web/tcmtf/current/msg00486.html" style=3D"color:purple;text-d=
ecoration:underline" target=3D"_blank"><span lang=3D"EN-US">http://www.ietf=
.org/mail-archive/web/tcmtf/current/msg00486.html</span></a><span lang=3D"E=
N-US">)</span><span style=3D"color:rgb(31,73,125)" lang=3D"EN-US"></span></=
div>



<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have shortened para=
graph 1.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have shortened and =
merged paragraphs 2 and 3.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have moved paragrap=
h 4 to the third place, in order to set clearer what we want: replacing RFC=
4170 with a widened proposal. As David suggested, I have also shortened the=
 text and it is now more straightforward.</span></div>



<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have clearly stated=
 which protocols will be used on each layer. The negotiation mechanism is s=
till necessary, since different options are considered e.g. for header comp=
ression. The one to be used will depend
 on the scenario and the processing capacity of the two optimizers.</span><=
/div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have significantly =
shortened the description of the scenarios.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have removed paragr=
aph 6, which included the savings figures.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">- I have included the r=
eplacement of RFC4170 in the first milestone.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">Thanks!</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">Jose</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"color:rgb(31,73,125)" lang=3D"EN-US">=A0</span></div>
<div>
<div style=3D"border-style:solid none none;border-top-color:rgb(181,196,223=
);border-top-width:1pt;padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-=
US">De:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-ser=
if" lang=3D"EN-US"><span>=A0</span>Black, David [</span><span style=3D"font=
-size:10pt;font-family:Tahoma,sans-serif"><a href=3D"mailto:david.black@emc=
.com" style=3D"color:purple;text-decoration:underline" target=3D"_blank"><s=
pan lang=3D"EN-US">mailto:david.black@emc.com</span></a></span><span style=
=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">]<span>=A0=
</span><br>



<b>Enviado el:</b><span>=A0</span>s=E1bado, 04 de enero de 2014 4:05<br>
<b>Para:</b><span>=A0</span>Jose Saldana;<span>=A0</span></span><span style=
=3D"font-size:10pt;font-family:Tahoma,sans-serif"><a href=3D"mailto:tcmtf@i=
etf.org" style=3D"color:purple;text-decoration:underline" target=3D"_blank"=
><span lang=3D"EN-US">tcmtf@ietf.org</span></a></span><span style=3D"font-s=
ize:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">;<span>=A0</span></s=
pan><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif"><a href=3D=
"mailto:tsv-area@ietf.org" style=3D"color:purple;text-decoration:underline"=
 target=3D"_blank"><span lang=3D"EN-US">tsv-area@ietf.org</span></a></span>=
<span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US"=
><br>



<b>CC:</b><span>=A0</span>Martin Stiemerling; Black, David<br>
<b>Asunto:</b><span>=A0</span>RE: TCMTF-Feedback about a possible BoF in Lo=
ndon</span></div>
</div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">A second BoF has the explicit goal of forming a WG, as a third BoF</sp=
an></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">is not permitted.=A0 In that regard, the new charter seems long and</s=
pan></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">somewhat lacking in focus.=A0 Two key things I look for in a proposed<=
/span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">charter are what problem (or problems) the proposed WG is looking to</=
span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">solve and an initial approach to the problem or problems.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">In the new draft charter, the problem statement appears to be in</span=
></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">paragraph 4 with paragraph 1 providing important background.=A0 The</s=
pan></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">focus of the work appears to be on extending TCRTP (RFC 4170) to</span=
></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">UDP and to include new compression protocols.=A0 In contrast, I have</=
span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">a hard time discerning the initial approach from the new draft charter=
.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">In light of this, there are a few things that I wish the new</span></d=
iv>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">draft charter had definitive proposals for:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0 a) Whether to replace RFC 4170 vs. write a new RFC (co=
uld be</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 UDP-only or UDP + RTP/UDP) as a comp=
lement to RFC 4170.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0 b) Whether to use ECRTP, ROHCv2 (RFC 5225) and/or IPHC=
 (RFC 2507 ?).</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Non-use of ECRTP would be a major ch=
ange to 4170, and I</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt 36pt;font-size:11pt;font-family:Calib=
ri,sans-serif;text-indent:36pt">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">wonder about IPHC, as opposed to the ROHCv2 profiles.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0=A0=A0=A0=A0 c) Analogies to b) for the Mux and Tunnel layers of th=
e stack.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">Overall, it looks like the first task of the WG is to select the proto=
col</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">stack to standardize - I have misgivings about that, and would prefer =
to</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">see a concrete proposal in a crisp charter that ran along the followin=
g</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">lines, naming the protocols to be used:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">1) RFC 4170 does X, and needs the following changes/additions: X, Y, Z=
.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">2) The WG will replace RFC 4170 with a new RFC that contains: A, B, C.=
</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">A specific proposal or proposals for the protocol stack or stacks</spa=
n></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">would also narrow the scope of item 9 in the charter on the negotiatio=
n</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">mechanism.=A0 I also don=92t see a goal/milestone listed for an extens=
ion to</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">or replacement for RFC 4170.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">I=92d prefer to see a much shorter more focused draft charter.=A0 Ther=
e=92s a</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">bunch of background material that does not seem crucial to the charter=
,</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">starting w/paragraphs 2 and 3.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">Thanks,<br>
--David</span><span style=3D"font-family:&#39;Courier New&#39;" lang=3D"EN-=
US"></span></div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span style=3D"font-size:10pt;font-family:&#39;Courier New&#39;" lang=3D"EN=
-US">=A0</span></div>
<div style=3D"border-style:none none none solid;border-left-color:blue;bord=
er-left-width:1.5pt;padding:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-style:solid none none;border-top-color:rgb(181,196,223=
);border-top-width:1pt;padding:3pt 0cm 0cm">
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-=
US">From:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-s=
erif" lang=3D"EN-US"><span>=A0</span>tsv-area [</span><a href=3D"mailto:tsv=
-area-bounces@ietf.org" style=3D"color:purple;text-decoration:underline" ta=
rget=3D"_blank"><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif=
" lang=3D"EN-US">mailto:tsv-area-bounces@ietf.org</span></a><span style=3D"=
font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">]<span>=A0</sp=
an><b>On
 Behalf Of<span>=A0</span></b>Jose Saldana<br>
<b>Sent:</b><span>=A0</span>Friday, December 20, 2013 4:26 AM<br>
<b>To:</b><span>=A0</span></span><a href=3D"mailto:tcmtf@ietf.org" style=3D=
"color:purple;text-decoration:underline" target=3D"_blank"><span style=3D"f=
ont-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">tcmtf@ietf.org<=
/span></a><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=
=3D"EN-US">;<span>=A0</span></span><a href=3D"mailto:tsv-area@ietf.org" sty=
le=3D"color:purple;text-decoration:underline" target=3D"_blank"><span style=
=3D"font-size:10pt;font-family:Tahoma,sans-serif" lang=3D"EN-US">tsv-area@i=
etf.org</span></a><span style=3D"font-size:10pt;font-family:Tahoma,sans-ser=
if" lang=3D"EN-US"><br>



<b>Cc:</b><span>=A0</span>Martin Stiemerling<br>
<b>Subject:</b><span>=A0</span>TCMTF-Feedback about a possible BoF in Londo=
n</span></div>
</div>
</div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">Hi all,</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">After the feedback received in the BoF in Berlin, we h=
ave updated the TCM-TF charter and the two drafts. We have tried to solve a=
ll the problems raised during the session.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">Our plan is to request a new BoF in London next March,=
 so we would like to know your opinion about these two questions:</span></d=
iv>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">1. =A0Is the new, reduced scope of TCM-TF suitable to =
form a working group?</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">2. We would like to kindly ask people who think that a=
 TCM-TF Working group should be formed, to come forward and send an e-mail =
to the<span>=A0</span></span><a href=3D"mailto:tsv-area@ietf.org" style=3D"=
color:purple;text-decoration:underline" target=3D"_blank"><span lang=3D"EN-=
US">tsv-area@ietf.org</span></a><span lang=3D"EN-US"><span>=A0</span>=A0mai=
ling
 list stating it.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">This feedback will allow us to get a better idea of th=
e convenience of a BoF.</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">The new charter is here:<span>=A0</span></span><a href=
=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html" style=
=3D"color:purple;text-decoration:underline" target=3D"_blank"><span lang=3D=
"EN-US">http://www.ietf.org/mail-archive/web/tcmtf/current/msg00465.html</s=
pan></a><span lang=3D"EN-US"></span></div>



<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">This is the old one (presented in Berlin):<span>=A0</s=
pan></span><a href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/ms=
g00368.html" style=3D"color:purple;text-decoration:underline" target=3D"_bl=
ank"><span lang=3D"EN-US">http://www.ietf.org/mail-archive/web/tcmtf/curren=
t/msg00368.html</span></a><span lang=3D"EN-US"></span></div>



<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">In these links you can see the differences between the=
 new versions of the drafts and the old ones:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<a href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-0=
6.txt&amp;url2=3Ddraft-saldana-tsvwg-tcmtf-05.txt" style=3D"color:purple;te=
xt-decoration:underline" target=3D"_blank"><span lang=3D"EN-US">http://tool=
s.ietf.org/rfcdiff?url1=3Ddraft-saldana-tsvwg-tcmtf-06.txt&amp;url2=3Ddraft=
-saldana-tsvwg-tcmtf-05.txt</span></a><span lang=3D"EN-US"></span></div>



<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<a href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-t=
cmtf-02.txt&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt" style=3D"col=
or:purple;text-decoration:underline" target=3D"_blank"><span lang=3D"EN-US"=
>http://tools.ietf.org/rfcdiff?url1=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-02.tx=
t&amp;url2=3Ddraft-suznjevic-tsvwg-mtd-tcmtf-01.txt</span></a><span lang=3D=
"EN-US"></span></div>



<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">The main improvements are:</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- TCP optimization has been removed</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- The classification of the scenarios has been refined=
 and improved. Some of them have been removed</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- A section about energy consumption has been added to=
 the main draft</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- A reference to the potential problem of the MTU and =
packet loss has been added</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- The problem of the added delays is studied in detail=
 in the second draft</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">- The improvements of the charter are summarized here:=
<span>=A0</span></span><a href=3D"http://www.ietf.org/mail-archive/web/tcmt=
f/current/msg00466.html" style=3D"color:purple;text-decoration:underline" t=
arget=3D"_blank"><span lang=3D"EN-US">http://www.ietf.org/mail-archive/web/=
tcmtf/current/msg00466.html</span></a><span lang=3D"EN-US"></span></div>



<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">Best regards,</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">Jose</span></div>
<div style=3D"margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sa=
ns-serif">
<span lang=3D"EN-US">=A0</span></div>
</div>
</div>
</blockquote>
<blockquote type=3D"cite">
<div></div>
</blockquote></div></div>
_______________________________________________<div><br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org" style=3D"color:purple;text-decoration:und=
erline" target=3D"_blank">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color:purp=
le;text-decoration:underline" target=3D"_blank">https://www.ietf.org/mailma=
n/listinfo/tcmtf</a></div></div>
</blockquote>
</div>
<br>
</div>
</div><div>
<br>
<hr>
<font color=3D"Gray" size=3D"1" face=3D"Arial"><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" target=3D"_blank">=
http://www.tid.es/ES/PAGINAS/disclaimer.aspx</a><br>
</font>
</div></div>

<br>_______________________________________________<br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org" target=3D"_blank">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/tcmtf</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org" target=3D"_blank">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/tcmtf</a><br>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br>Charles Oloo<br>WEB=
MASTER<br>Tel: <a href=3D"tel:%2B254%20721%20909757" value=3D"+254721909757=
" target=3D"_blank">+254 721 909757</a><br>=A0=A0=A0 =A0=A0 <br><input type=
=3D"hidden"><input type=3D"hidden"><div>
</div><input type=3D"hidden"><input type=3D"hidden"><div></div>

</div>
<br>_______________________________________________<br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/tcmtf</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div dir=
=3D"ltr"><font size=3D"1">-- <br></font><font size=3D"1"><span style=3D"bor=
der-collapse:collapse"><p style=3D"margin:0px">

<span style=3D"font-family:Arial,sans-serif">Mehmet Karaca, PhD</span></p><=
p style=3D"color:rgb(34,34,34);margin:0px"><span style=3D"color:rgb(0,0,0);=
font-family:Arial,sans-serif">System Engineer, CTO Office</span></p>


<p style=3D"color:rgb(34,34,34);margin:0px"><span style=3D"color:rgb(0,0,0)=
;font-family:Arial,sans-serif">AirTies Wireless Networks (</span><span styl=
e=3D"color:rgb(192,0,0);font-family:Arial,sans-serif"><a href=3D"http://www=
.airties.com/" style=3D"color:rgb(17,85,204);font-family:Arial,sans-serif" =
target=3D"_blank">www.airties.com</a>)</span></p>



<p style=3D"color:rgb(34,34,34);margin:0px"><span style=3D"font-family:Aria=
l,sans-serif">=A0</span></p><p style=3D"color:rgb(34,34,34);margin:0px"><sp=
an style=3D"color:rgb(31,73,125);font-family:Arial,sans-serif">M:=A0</span>=
<a value=3D"+905334312773">+90 (554) 718=A0 9009</a></p>



<p style=3D"margin:0px"><span style=3D"font-family:Arial,sans-serif"><font =
color=3D"#cc0000">E: </font></span><span style=3D"font-family:Arial,sans-se=
rif;color:rgb(192,0,0)" lang=3D"EN-GB"><span style=3D"color:rgb(192,0,0)" l=
ang=3D"EN-US"><a href=3D"mailto:ece.gelal@airties.com" style=3D"color:rgb(1=
7,85,204)" target=3D"_blank">mehmet.karaca@airties.com</a></span></span></p=
>
</span></font></div>
</div></div>

<br>
<div style=3D"text-align:left"><span style=3D"background-color:rgb(255,255,=
255);color:rgb(128,128,128);font-family:Verdana;font-size:x-small"><br></sp=
an></div><div style=3D"text-align:left"><span style=3D"background-color:rgb=
(255,255,255);color:rgb(128,128,128);font-family:Verdana;font-size:x-small"=
>Information in this email including any attachments may be privileged, con=
fidential and is intended exclusively for the addressee. The views expresse=
d may not be official policy, but the personal views of the originator. If =
you have received it in error, please notify the sender by return e-mail an=
d delete it from your system. You should not reproduce, distribute, store, =
retransmit, use or disclose its contents to anyone.</span></div>
--089e016814ccb9eb3b04f0b396b7--
