
From jsaldana@unizar.es  Wed Jun  5 03:34:26 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D954321F9A15 for <tcmtf@ietfa.amsl.com>; Wed,  5 Jun 2013 03:34:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.109
X-Spam-Level: 
X-Spam-Status: No, score=-5.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tmB0G-WKgE6d for <tcmtf@ietfa.amsl.com>; Wed,  5 Jun 2013 03:34:21 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 9105A21F99F0 for <tcmtf@ietf.org>; Wed,  5 Jun 2013 03:34:17 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r55AYCcQ014061; Wed, 5 Jun 2013 12:34:12 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 5 Jun 2013 12:34:15 +0200
Organization: Universidad de Zaragoza
Message-ID: <004201ce61d8$3a1c81a0$ae5584e0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0043_01CE61E8.FDA551A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5h11nCtybtZzlXTxaECdvitMM1KQ==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: 'Spencer Dawkins' <spencerdawkins.ietf@gmail.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [tcmtf] TCMTF BOF proposal: outline of the session
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2013 10:34:27 -0000

This is a multipart message in MIME format.

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

Hi all,

 

After a coordination conf-call we had yesterday, we think we could slightly
modify the order of the presentations. The presentation of the WG charter
should be the last one. The idea is that we should first explain what we
want to do, and in the end we should summarize everything in the Charter.
Otherwise people could start to discuss the charter in the beginning, and we
can get stuck on that.

 

 

1- Teaser presentation: describing the problem and the need for
standardization. Dan Wing, Cisco

 

2- Draft "TCMTF Stack": Explaining the current TCMTF proposal. Jose Saldana,
University of Zaragoza

 

3- Draft "TCMTF Recommendations": Explaining the content of the draft about
delay requirements, classification methods, etc. Mirko Suznjevic, University
of Zagreb

 

(4-  Specific uses of TCMTF in wireless and satellite scenarios) To be
confirmed by DLR

 

5- Charter: Documents to be generated within this potential WG. Diego R.
Lopez, Telefonica

 

 

 

Any comments?

 

Best regards and thanks,

 

Jose 

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>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 a coordination conf-call we had yesterday, we think =
we could slightly modify the order of the presentations. The =
presentation of the WG charter should be the last one. The idea is that =
we should first explain what we want to do, and in the end we should =
summarize everything in the Charter. Otherwise people could start to =
discuss the charter in the beginning, and we can get stuck on =
that.<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- Teaser presentation: describing the problem and the need =
for standardization. Dan Wing, Cisco<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>2- Draft &#8220;TCMTF Stack&#8221;: =
Explaining the current TCMTF proposal. Jose Saldana, University of =
Zaragoza<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>3- Draft &#8220;TCMTF Recommendations&#8221;: Explaining =
the content of the draft about delay requirements, classification =
methods, etc. Mirko Suznjevic, University of =
Zagreb<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- &nbsp;Specific uses of TCMTF in wireless and satellite =
scenarios) To be confirmed by DLR<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- Charter: Documents to be =
generated within this potential WG. Diego R. Lopez, =
Telefonica<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><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Any comments?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Best regards and =
thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-fareast-language:ES'>Jose =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_0043_01CE61E8.FDA551A0--


From jsaldana@unizar.es  Wed Jun  5 03:56:40 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7156521F9A5A; Wed,  5 Jun 2013 03:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.854
X-Spam-Level: 
X-Spam-Status: No, score=-5.854 tagged_above=-999 required=5 tests=[AWL=0.745,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KnXIUDgwxC3E; Wed,  5 Jun 2013 03:56:34 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 3316121F9A40; Wed,  5 Jun 2013 03:56:34 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r55AuLHR002590; Wed, 5 Jun 2013 12:56:26 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 5 Jun 2013 12:56:24 +0200
Organization: Universidad de Zaragoza
Message-ID: <004d01ce61db$55415480$ffc3fd80$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5h2eb/R9lrIRTzTmSkhKAFyvT4WQ==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tsv-area@ietf.org, spencerdawkins.ietf@gmail.com, 'ken carlberg' <carlberg@g11.org.uk>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [tcmtf] TCMTF: Documents to be generated. Small modification
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2013 10:56:40 -0000

In the conf-call of yesterday it was also clear that for the IETF it is
better to split Document A into two documents:

- The "TCMTF reference model" (1): the protocol stack and scenarios. It
should be said that each protocol at each layer will use its own =
signaling
mechanisms.

- The "TCMTF-specific signaling": there are some things we will need to
deploy:
	- a negotiation mechanism (2) to decide the options to use at each
layer (e.g. a mux and demux agree on using ROHC+PPPMux+GRE)
	- a mechanism to setup/release a TCMTF tunnel (3)between a
multiplexer and a de-multiplexer


The current draft is the TCMTF "reference model", since it does not talk
about specific signaling issues.

By now, we don't have to propose the "TCMTF specific signaling". It =
would be
something to be deployed if the Working Group is created.

This same idea was proposed by Ken Carlberg in February. The advantages =
of
this new distribution of the documents are (quoting Ken):

> One thing to keep in mind is that it is possible that (2) and (3)
> (below) can change over time and yet (1) (the reference model) does =
not,
> then it may be best to separate (1) from the other items.

> a more encompassing architecture or framework that would include =
sample
> scenarios upon which your deliverables A & B are aimed at?  My =
impression
> is that you may want to point the reader of documents A & B to the =
same
> reference model, and instead of repeating the same text, it may be
> helpful to separate this into a separate document.


Once discussed, I would create a new charter proposal including these
changes.


Do you like these short names for the documents?

- "TCMTF reference model".
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/=20

- "TCMTF-specific signaling". Future work

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


Your feedback will be welcome. Thanks!

Jose

> -----Mensaje original-----
> De: ken carlberg [mailto:carlberg@g11.org.uk]
> Enviado el: martes, 05 de marzo de 2013 17:07
> Para: jsaldana@unizar.es
> CC: 'ken carlberg'; tcmtf@ietf.org; tsv-area@ietf.org
> Asunto: Re: [tcmtf] About the possibility of having a BOF about TCMTF =
in
> IETF87
>=20
> Hola Jose,
>=20
> Thanks for the expanded explanation, and again, apologies for the =
tardy
> repsonse.  Its helpful to understand that document A and B are =
sequential
to
> each other.  One thing to keep in mind is that if its possible that 2 =
and
3
> (below) can change over time and yet 1 (the reference model) does not,
> then it may be best to separate 1 from the other items.
>=20
> as for what you outline as a discussion point for future work, it =
seems
fine.  I
> just have a personal bias that if you have a clear idea of the things
you'd like
> to accomplish in the future, then having a requirements document would =
be
> helpful to focus those thoughts without having to have one particular
> solution.  But that's a discussion point that could be brought up =
during
the
> BoF, or sometime afterwards.
>=20
> cheers,
>=20
> -ken
>=20
>=20
> > A main document (A) in which we explain the method, the scenarios =
and
> > the minimum signaling issues in order to make it work. The idea is
> > that document
> > (A) would be self-contained. Since we are not defining new protocols
(i.e.
> > already existing compressing, multiplexing and tunneling protocols =
are
> > to be used), we understand that this can be done in a single =
document.
> > It would
> > include:
> >
> > 1- Protocol stack (it would be the "reference model")
> > 2- a negotiation mechanism to decide the options to use at each =
layer
> > 3- a mechanism to setup/release a tunnel between a multiplexer and a
> > de-multiplexer
> >
> > Of course, another approach could be separating 1 from 2&3. However,
> > we think this is not necessary since the method is not too =
complicated.
> >
> >
> > Document (B) would only contain recommendations of how to better use
> > the method proposed in document (A), i.e., classification and =
maximum
> delays.
> >
> > So clearly document (B) would totally depend on the reference model =
of
> > document (A).
> >
> >
> > The idea of point 9 is to talk about some other interesting ideas
> > which are considered as "future work":
> > - a mechanism for a multiplexer to discover a de-multiplexer
> > - mechanism to select an optimal multiplexer and a de-multiplexer =
when
> > there are more than one muxer/de-muxer for a flow
> > - dynamically applying TCMTF
> > - etc.
> >
> > What do you think?
> >
> > Thanks again for your feedback. Thinking and explaining things is
> > always a good exercise!
> >
> > Jose
> >
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> >> de ken carlberg Enviado el: mi=E9rcoles, 27 de febrero de 2013 =
16:23
> >> Para: jsaldana@unizar.es
> >> CC: tcmtf@ietf.org; tsv-area@ietf.org
> >> Asunto: Re: [tcmtf] About the possibility of having a BOF about =
TCMTF
> >> in
> >> IETF87
> >>
> >> Hola Jose,
> >>
> >> sorry for the tardy reply.  The altered text below is helpful, =
thanks.
> >>
> >> With respect to your candidate deliverables, it appears that you =
have
> > listed
> >> two for the proposed group: (A) a document that describes options =
and
> >> negotiation mechanisms, and (B) a document describing
> recommendations
> >> of which packet types should be multiplexed and a list fo traffic
> > classification
> >> methods.  Have you considered a third document that presents a more
> >> encompassing architecture or framework that would include sample
> >> scenarios upon which your deliverables A & B are aimed at?  My
> >> impression
> > is
> >> that you may want to point the reader of documents A & B to the =
same
> >> reference model, and instead of repeating the same text, it may be
> >> helpful to separate this into a separate document.
> >>
> >> Also, would section 9 of your proposed charter lead one to consider =
a
> >> requirements document?  Many times, new groups start with a
> >> requirements document, but since you have a good focus of what you
> >> want to accomplish, perhaps your last deliverable could be a
> >> requirements document that would guide any future work.
> >>
> >> -ken
> >>
> >> ps, I don't want to advocate more work, but rather just have you
> >> consider other possibilities (and feel free to shoot them down :-)
> >>
> >>
> >> On Feb 22, 2013, at 5:39 AM, Jose Saldana <jsaldana@unizar.es> =
wrote:
> >>
> >>> Hi Ken,
> >>>
> >>> Sorry for the delay. I think you are talking about Paragraph 5:
> >>>
> >>> 5. So the first objective of this group is to specify the protocol
> >>> stack for tunneling, compressing and multiplexing traffic flows
> >>> (TCMTF). Since standard protocols are being used at each layer, =
the
> >>> signaling methods of those protocols will be used. Interactions =
with
> >>> the Working Groups and Areas in which these protocols are =
developed
> >>> can be expected. However, the development of new compressing,
> >>> multiplexing or tunneling protocols is not an objective of this
> >>> Working Group. In addition, since the current RFC 4170 would be
> >> considered as one of the options, this RFC could be obsoleted.
> >>>
> >>> Perhaps this is a bit confusing. When we say "at each layer", we =
are
> >>> talking about "tunneling, compressing and multiplexing" layers.
> >>> Perhaps this can be a bit confusing. What about this?:
> >>>
> >>> 5. So the first objective of this group is to specify the protocol
> >>> stack for tunneling, compressing and multiplexing traffic flows
> >>> (TCMTF). Since standard protocols are being used for tunneling,
> >>> compressing and multiplexing layers, the signaling methods of =
those
> >> protocols will be used.
> >>> Interactions with the Working Groups and Areas in which these
> >>> protocols are developed can be expected. However, the development
> of
> >>> new compressing, multiplexing or tunneling protocols is not an
> >>> objective of this Working Group. In addition, since the current =
RFC
> >>> 4170 would be considered as one of the options, this RFC could be
> >> obsoleted.
> >>>
> >>> Is this what you were asking?
> >>>
> >>> Thanks for your feedback.
> >>>
> >>> Jose
> >>>
> >>>> -----Mensaje original-----
> >>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >>>> nombre de ken carlberg Enviado el: martes, 19 de febrero de 2013
> >>>> 14:17
> >>>> Para: jsaldana@unizar.es
> >>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
> >>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about
> >>>> TCMTF in
> >>>> IETF87
> >>>>
> >>>> Hola Jose,
> >>>>
> >>>> could you expand a bit more on your text in the proposed charter
> >>>> regarding "signaling methods".  Are you speaking in the more
> >>>> general context of information stored in headers of various
> >>>> protocol up and down the stack
> >>> (ie,
> >>>> layers 3, 4, and 5/app)?  Or, are you  speaking of concurrent
> >>>> resource signaling protocols like RSVP/RSVP-TE, or path
> >>>> establishment protocols
> >>> like
> >>>> MPLS?  Or, some combination of both?
> >>>>
> >>>> -ken
> >>>>
> >>>> _______________________________________________
> >>>> tcmtf mailing list
> >>>> tcmtf@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>>
> >>
> >> _______________________________________________
> >> tcmtf mailing list
> >> tcmtf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >



From jsaldana@unizar.es  Wed Jun  5 04:17:45 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 781BC21F997A for <tcmtf@ietfa.amsl.com>; Wed,  5 Jun 2013 04:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.226
X-Spam-Level: 
X-Spam-Status: No, score=-6.226 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwltIg5zFKTD for <tcmtf@ietfa.amsl.com>; Wed,  5 Jun 2013 04:17:40 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 280D921F9808 for <tcmtf@ietf.org>; Wed,  5 Jun 2013 04:17:39 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r55BHYQF026115; Wed, 5 Jun 2013 13:17:35 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 5 Jun 2013 13:17:37 +0200
Organization: Universidad de Zaragoza
Message-ID: <004e01ce61de$493b4c60$dbb1e520$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_004F_01CE61EF.0CC4B8A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5h3d0x+SPiW8w0QECcCizQC6sh6A==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: spencerdawkins.ietf@gmail.com, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [tcmtf] TCMTF BOF description
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2013 11:17:45 -0000

This is a multipart message in MIME format.

------=_NextPart_000_004F_01CE61EF.0CC4B8A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

 

I have just built this BOF description for
<http://trac.tools.ietf.org/bof/trac/wiki>
http://trac.tools.ietf.org/bof/trac/wiki. It summarizes the draft charter:

 

 

Some emerging interactive services (VoIP, videoconferencing, telemedicine,
video vigilance, online gaming, etc.) use small packets in order to send
frequent updates to the other extreme of the communication. Therefore, its
overhead is significant. In addition, some other services also send small
packets, although they are not delay-sensitive (e.g., instant messaging, m2m
packets sending collected data in sensor networks using wireless or
satellite scenarios).

 

When a number of small-packet flows share the same path, bandwidth can be
saved by multiplexing packets belonging to different flows, adding a small
multiplexing delay as a counterpart. This delay has to be maintained under
some threshold in order to grant the delay requirements. Some examples of
the scenarios where grouping packets is possible are: aggregation networks
of a network operator; a tunnel between two premises of the same company; a
satellite connection used for collecting the data of a high number of
sensors.

 

RFC4170 <http://tools.ietf.org/html/rfc4170>  (TCRTP) defined a method for
grouping VoIP packets considering three different layers: header compression
by means of ECRTP; multiplexing by means of PPPMux; tunneling by means of
L2TPv3. However, in the last years, emerging real-time services which do not
use UDP/RTP have become popular: some of them use UDP or even TCP. In
addition, new header compression methods have been defined (ROHC). So there
is a need of widening the scope of RFC4170 in order to consider not only
UDP/RTP but also other protocols. The same structure of three layers will be
considered: header compression, multiplexing and tunneling.

 

The BOF aims for 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 (TCMTF). 

 

 

Do you like it?

 

 

Another thing: in the section Relevant I-Ds of the web page, the
"recommendations" draft could also be included:

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

 

 

Best regards,

 

Jose 

 


------=_NextPart_000_004F_01CE61EF.0CC4B8A0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>I have just built this BOF description for </span><a =
href=3D"http://trac.tools.ietf.org/bof/trac/wiki"><span =
lang=3DEN-US>http://trac.tools.ietf.org/bof/trac/wiki</span></a><span =
lang=3DEN-US>. It summarizes the draft charter:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'text-align:justify'><span =
lang=3DEN-US>Some emerging interactive services (VoIP, =
videoconferencing, telemedicine, video vigilance, online gaming, etc.) =
use small packets in order to send frequent updates to the other extreme =
of the communication. Therefore, its overhead is significant. In =
addition, some other services also send small packets, although they are =
not delay-sensitive (e.g., instant messaging, m2m packets sending =
collected data in sensor networks using wireless or satellite =
scenarios).<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'text-align:justify'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'text-align:justify'><span lang=3DEN-US>When a number of =
small-packet flows share the same path, bandwidth can be saved by =
multiplexing packets belonging to different flows, adding a small =
multiplexing delay as a counterpart. This delay has to be maintained =
under some threshold in order to grant the delay requirements. Some =
examples of the scenarios where grouping packets is possible are: =
aggregation networks of a network operator; a tunnel between two =
premises of the same company; a satellite connection used for collecting =
the data of a high number of sensors.<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'text-align:justify'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'text-align:justify'><span lang=3DEN-US><a =
href=3D"http://tools.ietf.org/html/rfc4170">RFC4170</a> (TCRTP) defined =
a method for grouping VoIP packets considering three different layers: =
header compression by means of ECRTP; multiplexing by means of PPPMux; =
tunneling by means of L2TPv3. However, in the last years, emerging =
real-time services which do not use UDP/RTP have become popular: some of =
them use UDP or even TCP. In addition, new header compression methods =
have been defined (ROHC). So there is a need of widening the scope of =
RFC4170 in order to consider not only UDP/RTP but also other protocols. =
The same structure of three layers will be considered: header =
compression, multiplexing and tunneling.<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'text-align:justify'><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'text-align:justify'><span lang=3DEN-US>The BOF aims for 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 (TCMTF). =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Do you like it?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Another thing: in the section =
Relevant I-Ds of the web page, the &#8220;recommendations&#8221; draft =
could also be included:<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><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 style=3D'mso-fareast-language:ES'>Jose =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_004F_01CE61EF.0CC4B8A0--


From navajas@unizar.es  Thu Jun  6 01:08:00 2013
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A520B21F934B for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 01:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFJ3QH4avUeJ for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 01:07:50 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2A0C621F9310 for <tcmtf@ietf.org>; Thu,  6 Jun 2013 01:07:49 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5687fO2024048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Thu, 6 Jun 2013 10:07:46 +0200
Message-ID: <51B0434D.9030205@unizar.es>
Date: Thu, 06 Jun 2013 10:07:41 +0200
From: =?ISO-8859-15?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <004e01ce61de$493b4c60$dbb1e520$@unizar.es>
In-Reply-To: <004e01ce61de$493b4c60$dbb1e520$@unizar.es>
Content-Type: multipart/alternative; boundary="------------000401050300070902000606"
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] TCMTF BOF description
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 08:08:01 -0000

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

Hi all,
I'd like to make a remark.
I feel that the charter is only oriented to network operator. Perhaps it 
is good strengthen the idea that TCMTF is also beneficial for the 
development of end-to-end aplications.
Julián


El 05/06/2013 13:17, Jose Saldana escribió:
>
> Hi,
>
> I have just built this BOF description for 
> http://trac.tools.ietf.org/bof/trac/wiki. It summarizes the draft charter:
>
> Some emerging interactive services (VoIP, videoconferencing, 
> telemedicine, video vigilance, online gaming, etc.) use small packets 
> in order to send frequent updates to the other extreme of the 
> communication. Therefore, its overhead is significant. In addition, 
> some other services also send small packets, although they are not 
> delay-sensitive (e.g., instant messaging, m2m packets sending 
> collected data in sensor networks using wireless or satellite scenarios).
>
> When a number of small-packet flows share the same path, bandwidth can 
> be saved by multiplexing packets belonging to different flows, adding 
> a small multiplexing delay as a counterpart. This delay has to be 
> maintained under some threshold in order to grant the delay 
> requirements. Some examples of the scenarios where grouping packets is 
> possible are: aggregation networks of a network operator; a tunnel 
> between two premises of the same company; a satellite connection used 
> for collecting the data of a high number of sensors.
>
> RFC4170 <http://tools.ietf.org/html/rfc4170> (TCRTP) defined a method 
> for grouping VoIP packets considering three different layers: header 
> compression by means of ECRTP; multiplexing by means of PPPMux; 
> tunneling by means of L2TPv3. However, in the last years, emerging 
> real-time services which do not use UDP/RTP have become popular: some 
> of them use UDP or even TCP. In addition, new header compression 
> methods have been defined (ROHC). So there is a need of widening the 
> scope of RFC4170 in order to consider not only UDP/RTP but also other 
> protocols. The same structure of three layers will be considered: 
> header compression, multiplexing and tunneling.
>
> The BOF aims for 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 (TCMTF).
>
> Do you like it?
>
> Another thing: in the section Relevant I-Ds of the web page, the 
> "recommendations" draft could also be included:
>
> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>
> Best regards,
>
> Jose
>
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-15"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi all,<br>
      I'd like to make a remark.<br>
      I feel that the charter is only oriented to network operator.
      Perhaps it is good strengthen the idea that TCMTF is also
      beneficial for the development of end-to-end aplications. <br>
      Julián<br>
      <br>
      <br>
      El 05/06/2013 13:17, Jose Saldana escribió:<br>
    </div>
    <blockquote cite="mid:004e01ce61de$493b4c60$dbb1e520$@unizar.es"
      type="cite">
      <meta http-equiv="Context-Type" content="text/html;
        charset=us-ascii">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <div class="WordSection1">
        <p class="MsoNormal">Hi,</p>
        <p class="MsoNormal"> </p>
        <p class="MsoNormal"><span lang="EN-US">I have just built this
            BOF description for </span><a moz-do-not-send="true"
            href="http://trac.tools.ietf.org/bof/trac/wiki"><span
              lang="EN-US">http://trac.tools.ietf.org/bof/trac/wiki</span></a><span
            lang="EN-US">. It summarizes the draft charter:</span></p>
        <p class="MsoNormal"><span lang="EN-US"> </span></p>
        <p class="MsoNormal"><span lang="EN-US"> </span></p>
        <p class="MsoPlainText"><span lang="EN-US">Some emerging
            interactive services (VoIP, videoconferencing, telemedicine,
            video vigilance, online gaming, etc.) use small packets in
            order to send frequent updates to the other extreme of the
            communication. Therefore, its overhead is significant. In
            addition, some other services also send small packets,
            although they are not delay-sensitive (e.g., instant
            messaging, m2m packets sending collected data in sensor
            networks using wireless or satellite scenarios).</span></p>
        <p class="MsoPlainText"><span lang="EN-US"> </span></p>
        <p class="MsoPlainText"><span lang="EN-US">When a number of
            small-packet flows share the same path, bandwidth can be
            saved by multiplexing packets belonging to different flows,
            adding a small multiplexing delay as a counterpart. This
            delay has to be maintained under some threshold in order to
            grant the delay requirements. Some examples of the scenarios
            where grouping packets is possible are: aggregation networks
            of a network operator; a tunnel between two premises of the
            same company; a satellite connection used for collecting the
            data of a high number of sensors.</span></p>
        <p class="MsoPlainText"><span lang="EN-US"> </span></p>
        <p class="MsoPlainText"><span lang="EN-US"><a
              moz-do-not-send="true"
              href="http://tools.ietf.org/html/rfc4170">RFC4170</a>
            (TCRTP) defined a method for grouping VoIP packets
            considering three different layers: header compression by
            means of ECRTP; multiplexing by means of PPPMux; tunneling
            by means of L2TPv3. However, in the last years, emerging
            real-time services which do not use UDP/RTP have become
            popular: some of them use UDP or even TCP. In addition, new
            header compression methods have been defined (ROHC). So
            there is a need of widening the scope of RFC4170 in order to
            consider not only UDP/RTP but also other protocols. The same
            structure of three layers will be considered: header
            compression, multiplexing and tunneling.</span></p>
        <p class="MsoPlainText"><span lang="EN-US"> </span></p>
        <p class="MsoPlainText"><span lang="EN-US">The BOF aims for 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 (TCMTF). </span></p>
        <p class="MsoNormal"><span lang="EN-US"> </span></p>
        <p class="MsoNormal"><span lang="EN-US"> </span></p>
        <p class="MsoNormal"><span lang="EN-US">Do you like it?</span></p>
        <p class="MsoNormal"><span lang="EN-US"> </span></p>
        <p class="MsoNormal"><span lang="EN-US"> </span></p>
        <p class="MsoNormal"><span lang="EN-US">Another thing: in the
            section Relevant I-Ds of the web page, the &#8220;recommendations&#8221;
            draft could also be included:</span></p>
        <p class="MsoNormal"><a moz-do-not-send="true"
            href="http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"><span
              lang="EN-US">http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</span></a><span
            lang="EN-US"></span></p>
        <p class="MsoNormal"><span lang="EN-US"> </span></p>
        <p class="MsoNormal"><span lang="EN-US"> </span></p>
        <p class="MsoNormal"><span lang="EN-US">Best regards,</span></p>
        <p class="MsoNormal"><span lang="EN-US"> </span></p>
        <p class="MsoNormal"><span lang="EN-US">Jose </span></p>
        <p class="MsoNormal"><span lang="EN-US"> </span></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
tcmtf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tcmtf">https://www.ietf.org/mailman/listinfo/tcmtf</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------000401050300070902000606--

From Martin.Stiemerling@neclab.eu  Thu Jun  6 01:56:57 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C261F21F888F for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 01:56:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ZrqDv5qB8Mm for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 01:56:53 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 331B921F880F for <tcmtf@ietf.org>; Thu,  6 Jun 2013 01:56:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 53AEC1043E9; Thu,  6 Jun 2013 10:56:39 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0DMmWYTR-dJU; Thu,  6 Jun 2013 10:56:39 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 38124104330; Thu,  6 Jun 2013 10:56:24 +0200 (CEST)
Received: from [10.1.99.64] (10.1.99.64) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 6 Jun 2013 10:56:37 +0200
Message-ID: <51B04EC4.8070203@neclab.eu>
Date: Thu, 6 Jun 2013 10:56:36 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: <jsaldana@unizar.es>, <tcmtf@ietf.org>
References: <004e01ce61de$493b4c60$dbb1e520$@unizar.es>
In-Reply-To: <004e01ce61de$493b4c60$dbb1e520$@unizar.es>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [10.1.99.64]
Cc: spencerdawkins.ietf@gmail.com
Subject: Re: [tcmtf] TCMTF BOF description
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 08:56:57 -0000

Hi all,

I have uploaded it to the wiki. The BOF description is now complete.

For your information:
The IAB and the IESG will discuss the BOF proposals on call on June 20th.
The decision whether the BOF proposal is accepted or not is made during 
this call.

   Martin

On 06/05/2013 01:17 PM, Jose Saldana wrote:
> Hi,
>
> I have just built this BOF description for
> http://trac.tools.ietf.org/bof/trac/wiki. It summarizes the draft charter:
>
> Some emerging interactive services (VoIP, videoconferencing,
> telemedicine, video vigilance, online gaming, etc.) use small packets in
> order to send frequent updates to the other extreme of the
> communication. Therefore, its overhead is significant. In addition, some
> other services also send small packets, although they are not
> delay-sensitive (e.g., instant messaging, m2m packets sending collected
> data in sensor networks using wireless or satellite scenarios).
>
> When a number of small-packet flows share the same path, bandwidth can
> be saved by multiplexing packets belonging to different flows, adding a
> small multiplexing delay as a counterpart. This delay has to be
> maintained under some threshold in order to grant the delay
> requirements. Some examples of the scenarios where grouping packets is
> possible are: aggregation networks of a network operator; a tunnel
> between two premises of the same company; a satellite connection used
> for collecting the data of a high number of sensors.
>
> RFC4170 <http://tools.ietf.org/html/rfc4170> (TCRTP) defined a method
> for grouping VoIP packets considering three different layers: header
> compression by means of ECRTP; multiplexing by means of PPPMux;
> tunneling by means of L2TPv3. However, in the last years, emerging
> real-time services which do not use UDP/RTP have become popular: some of
> them use UDP or even TCP. In addition, new header compression methods
> have been defined (ROHC). So there is a need of widening the scope of
> RFC4170 in order to consider not only UDP/RTP but also other protocols.
> The same structure of three layers will be considered: header
> compression, multiplexing and tunneling.
>
> The BOF aims for 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 (TCMTF).
>
> Do you like it?
>
> Another thing: in the section Relevant I-Ds of the web page, the
> “recommendations” draft could also be included:
>
> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>
> Best regards,
>
> Jose
>

-- 
IETF Transport Area Director

martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From Mirko.Suznjevic@fer.hr  Thu Jun  6 02:45:51 2013
Return-Path: <Mirko.Suznjevic@fer.hr>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0258F21F973A for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 02:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6xMjCNrZPudg for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 02:45:45 -0700 (PDT)
Received: from mail.fer.hr (mail5.fer.hr [161.53.72.235]) by ietfa.amsl.com (Postfix) with ESMTP id 75CE121F93B9 for <tcmtf@ietf.org>; Thu,  6 Jun 2013 02:45:34 -0700 (PDT)
Received: from MAIL4.fer.hr ([2002:a135:48ea::a135:48ea]) by MAIL5.fer.hr ([2002:a135:48eb::a135:48eb]) with mapi id 14.02.0342.003; Thu, 6 Jun 2013 11:45:32 +0200
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] TCMTF BOF proposal: outline of the session
Thread-Index: Ac5h11nCtybtZzlXTxaECdvitMM1KQAwvJtQ
Date: Thu, 6 Jun 2013 09:45:31 +0000
Message-ID: <E004A7C54DE04F4BB87DB9F32308DA5C0BFFEE@MAIL4.fer.hr>
References: <004201ce61d8$3a1c81a0$ae5584e0$@unizar.es>
In-Reply-To: <004201ce61d8$3a1c81a0$ae5584e0$@unizar.es>
Accept-Language: en-US, hr-HR
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.53.19.114]
Content-Type: multipart/alternative; boundary="_000_E004A7C54DE04F4BB87DB9F32308DA5C0BFFEEMAIL4ferhr_"
MIME-Version: 1.0
Subject: Re: [tcmtf] TCMTF BOF proposal: outline of the session
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 09:45:51 -0000

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

Hello,
I concur with this. It is important to make that discussion be the pinnacle=
 of BoF. It should not be done before other stuff has been discussed, and b=
efore the people have had the chance to hear the presentations regarding th=
e drafts!
Mirko

From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of J=
ose Saldana
Sent: Wednesday, June 5, 2013 12:34 PM
To: tcmtf@ietf.org
Cc: 'Spencer Dawkins'; Martin Stiemerling
Subject: [tcmtf] TCMTF BOF proposal: outline of the session

Hi all,

After a coordination conf-call we had yesterday, we think we could slightly=
 modify the order of the presentations. The presentation of the WG charter =
should be the last one. The idea is that we should first explain what we wa=
nt to do, and in the end we should summarize everything in the Charter. Oth=
erwise people could start to discuss the charter in the beginning, and we c=
an get stuck on that.


1- Teaser presentation: describing the problem and the need for standardiza=
tion. Dan Wing, Cisco

2- Draft "TCMTF Stack": Explaining the current TCMTF proposal. Jose Saldana=
, University of Zaragoza

3- Draft "TCMTF Recommendations": Explaining the content of the draft about=
 delay requirements, classification methods, etc. Mirko Suznjevic, Universi=
ty of Zagreb

(4-  Specific uses of TCMTF in wireless and satellite scenarios) To be conf=
irmed by DLR

5- Charter: Documents to be generated within this potential WG. Diego R. Lo=
pez, Telefonica



Any comments?

Best regards and thanks,

Jose


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
2">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"HR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Hello,<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">I concu=
r with this. It is important to make that discussion be the pinnacle of BoF=
. It should not be done before other stuff has been discussed, and before t=
he people have had the chance to hear
 the presentations regarding the drafts!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Mirko<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" 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-GB" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org=
]
<b>On Behalf Of </b>Jose Saldana<br>
<b>Sent:</b> Wednesday, June 5, 2013 12:34 PM<br>
<b>To:</b> tcmtf@ietf.org<br>
<b>Cc:</b> 'Spencer Dawkins'; Martin Stiemerling<br>
<b>Subject:</b> [tcmtf] TCMTF BOF proposal: outline of the session<o:p></o:=
p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Hi all,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">After a coordination conf-call =
we had yesterday, we think we could slightly modify the order of the presen=
tations. The presentation of the WG charter should be the last one. The ide=
a is that we should first explain what
 we want to do, and in the end we should summarize everything in the Charte=
r. Otherwise people could start to discuss the charter in the beginning, an=
d we can get stuck on that.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">1- Teaser presentation: describ=
ing the problem and the need for standardization. Dan Wing, Cisco<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">2- Draft &#8220;TCMTF Stack&#82=
21;: Explaining the current TCMTF proposal. Jose Saldana, University of Zar=
agoza<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">3- Draft &#8220;TCMTF Recommend=
ations&#8221;: Explaining the content of the draft about delay requirements=
, classification methods, etc. Mirko Suznjevic, University of Zagreb<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">(4- &nbsp;Specific uses of TCMT=
F in wireless and satellite scenarios) To be confirmed by DLR<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">5- Charter: Documents to be gen=
erated within this potential WG. Diego R. Lopez, Telefonica<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Any comments?<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Best regards and thanks,<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Jose <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_E004A7C54DE04F4BB87DB9F32308DA5C0BFFEEMAIL4ferhr_--

From Mirko.Suznjevic@fer.hr  Thu Jun  6 02:51:21 2013
Return-Path: <Mirko.Suznjevic@fer.hr>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8DBE21F9635 for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 02:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.554
X-Spam-Level: 
X-Spam-Status: No, score=-1.554 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FADk1gxmUI9t for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 02:51:17 -0700 (PDT)
Received: from mail.fer.hr (mail.fer.hr [161.53.72.233]) by ietfa.amsl.com (Postfix) with ESMTP id DDE3021F93B9 for <tcmtf@ietf.org>; Thu,  6 Jun 2013 02:51:09 -0700 (PDT)
Received: from MAIL4.fer.hr ([2002:a135:48ea::a135:48ea]) by MAIL.fer.hr ([2002:a135:48e9::a135:48e9]) with mapi id 14.02.0342.003; Thu, 6 Jun 2013 11:51:06 +0200
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: TCMTF: Documents to be generated. Small modification
Thread-Index: Ac5h2eb/R9lrIRTzTmSkhKAFyvT4WQAwM8mgAAAmDdA=
Date: Thu, 6 Jun 2013 09:51:04 +0000
Message-ID: <E004A7C54DE04F4BB87DB9F32308DA5C0C0012@MAIL4.fer.hr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.53.19.114]
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small modification
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 09:51:22 -0000

Hello,
I think these names are ok. Maybe we should discuss the second one in more =
detail.
Perhaps include negotiation in the name of the draft so its purpose is evid=
ent from the title? As the purpose of that draft is to establish which part=
icular parameters will be used.=20
My suggestions are:
TCMTF - negotiation signalling
TCMTF - negotiation process
TCMTF - parameter signalling
Or something along those lines?
Mirko

-----Original Message-----
From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of J=
ose Saldana
Sent: Wednesday, June 5, 2013 12:56 PM
To: tcmtf@ietf.org
Cc: tsv-area@ietf.org; spencerdawkins.ietf@gmail.com; 'ken carlberg'; Marti=
n Stiemerling
Subject: [tcmtf] TCMTF: Documents to be generated. Small modification

In the conf-call of yesterday it was also clear that for the IETF it is bet=
ter to split Document A into two documents:

- The "TCMTF reference model" (1): the protocol stack and scenarios. It sho=
uld be said that each protocol at each layer will use its own signaling mec=
hanisms.

- The "TCMTF-specific signaling": there are some things we will need to
deploy:
	- a negotiation mechanism (2) to decide the options to use at each layer (=
e.g. a mux and demux agree on using ROHC+PPPMux+GRE)
	- a mechanism to setup/release a TCMTF tunnel (3)between a multiplexer and=
 a de-multiplexer


The current draft is the TCMTF "reference model", since it does not talk ab=
out specific signaling issues.

By now, we don't have to propose the "TCMTF specific signaling". It would b=
e something to be deployed if the Working Group is created.

This same idea was proposed by Ken Carlberg in February. The advantages of =
this new distribution of the documents are (quoting Ken):

> One thing to keep in mind is that it is possible that (2) and (3)
> (below) can change over time and yet (1) (the reference model) does=20
> not, then it may be best to separate (1) from the other items.

> a more encompassing architecture or framework that would include=20
> sample scenarios upon which your deliverables A & B are aimed at?  My=20
> impression is that you may want to point the reader of documents A & B=20
> to the same reference model, and instead of repeating the same text,=20
> it may be helpful to separate this into a separate document.


Once discussed, I would create a new charter proposal including these chang=
es.


Do you like these short names for the documents?

- "TCMTF reference model".
https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/=20

- "TCMTF-specific signaling". Future work

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


Your feedback will be welcome. Thanks!

Jose

> -----Mensaje original-----
> De: ken carlberg [mailto:carlberg@g11.org.uk] Enviado el: martes, 05=20
> de marzo de 2013 17:07
> Para: jsaldana@unizar.es
> CC: 'ken carlberg'; tcmtf@ietf.org; tsv-area@ietf.org
> Asunto: Re: [tcmtf] About the possibility of having a BOF about TCMTF=20
> in
> IETF87
>=20
> Hola Jose,
>=20
> Thanks for the expanded explanation, and again, apologies for the=20
> tardy repsonse.  Its helpful to understand that document A and B are=20
> sequential
to
> each other.  One thing to keep in mind is that if its possible that 2=20
> and
3
> (below) can change over time and yet 1 (the reference model) does not,=20
> then it may be best to separate 1 from the other items.
>=20
> as for what you outline as a discussion point for future work, it=20
> seems
fine.  I
> just have a personal bias that if you have a clear idea of the things
you'd like
> to accomplish in the future, then having a requirements document would=20
> be helpful to focus those thoughts without having to have one=20
> particular solution.  But that's a discussion point that could be=20
> brought up during
the
> BoF, or sometime afterwards.
>=20
> cheers,
>=20
> -ken
>=20
>=20
> > A main document (A) in which we explain the method, the scenarios=20
> > and the minimum signaling issues in order to make it work. The idea=20
> > is that document
> > (A) would be self-contained. Since we are not defining new protocols
(i.e.
> > already existing compressing, multiplexing and tunneling protocols=20
> > are to be used), we understand that this can be done in a single docume=
nt.
> > It would
> > include:
> >
> > 1- Protocol stack (it would be the "reference model")
> > 2- a negotiation mechanism to decide the options to use at each=20
> > layer
> > 3- a mechanism to setup/release a tunnel between a multiplexer and a=20
> > de-multiplexer
> >
> > Of course, another approach could be separating 1 from 2&3. However,=20
> > we think this is not necessary since the method is not too complicated.
> >
> >
> > Document (B) would only contain recommendations of how to better use=20
> > the method proposed in document (A), i.e., classification and=20
> > maximum
> delays.
> >
> > So clearly document (B) would totally depend on the reference model=20
> > of document (A).
> >
> >
> > The idea of point 9 is to talk about some other interesting ideas=20
> > which are considered as "future work":
> > - a mechanism for a multiplexer to discover a de-multiplexer
> > - mechanism to select an optimal multiplexer and a de-multiplexer=20
> > when there are more than one muxer/de-muxer for a flow
> > - dynamically applying TCMTF
> > - etc.
> >
> > What do you think?
> >
> > Thanks again for your feedback. Thinking and explaining things is=20
> > always a good exercise!
> >
> > Jose
> >
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En=20
> >> nombre de ken carlberg Enviado el: mi=E9rcoles, 27 de febrero de 2013
> >> 16:23
> >> Para: jsaldana@unizar.es
> >> CC: tcmtf@ietf.org; tsv-area@ietf.org
> >> Asunto: Re: [tcmtf] About the possibility of having a BOF about=20
> >> TCMTF in
> >> IETF87
> >>
> >> Hola Jose,
> >>
> >> sorry for the tardy reply.  The altered text below is helpful, thanks.
> >>
> >> With respect to your candidate deliverables, it appears that you=20
> >> have
> > listed
> >> two for the proposed group: (A) a document that describes options=20
> >> and negotiation mechanisms, and (B) a document describing
> recommendations
> >> of which packet types should be multiplexed and a list fo traffic
> > classification
> >> methods.  Have you considered a third document that presents a more=20
> >> encompassing architecture or framework that would include sample=20
> >> scenarios upon which your deliverables A & B are aimed at?  My=20
> >> impression
> > is
> >> that you may want to point the reader of documents A & B to the=20
> >> same reference model, and instead of repeating the same text, it=20
> >> may be helpful to separate this into a separate document.
> >>
> >> Also, would section 9 of your proposed charter lead one to consider=20
> >> a requirements document?  Many times, new groups start with a=20
> >> requirements document, but since you have a good focus of what you=20
> >> want to accomplish, perhaps your last deliverable could be a=20
> >> requirements document that would guide any future work.
> >>
> >> -ken
> >>
> >> ps, I don't want to advocate more work, but rather just have you=20
> >> consider other possibilities (and feel free to shoot them down :-)
> >>
> >>
> >> On Feb 22, 2013, at 5:39 AM, Jose Saldana <jsaldana@unizar.es> wrote:
> >>
> >>> Hi Ken,
> >>>
> >>> Sorry for the delay. I think you are talking about Paragraph 5:
> >>>
> >>> 5. So the first objective of this group is to specify the protocol=20
> >>> stack for tunneling, compressing and multiplexing traffic flows=20
> >>> (TCMTF). Since standard protocols are being used at each layer,=20
> >>> the signaling methods of those protocols will be used.
> >>> Interactions with the Working Groups and Areas in which these=20
> >>> protocols are developed can be expected. However, the development=20
> >>> of new compressing, multiplexing or tunneling protocols is not an=20
> >>> objective of this Working Group. In addition, since the current=20
> >>> RFC 4170 would be
> >> considered as one of the options, this RFC could be obsoleted.
> >>>
> >>> Perhaps this is a bit confusing. When we say "at each layer", we=20
> >>> are talking about "tunneling, compressing and multiplexing" layers.
> >>> Perhaps this can be a bit confusing. What about this?:
> >>>
> >>> 5. So the first objective of this group is to specify the protocol=20
> >>> stack for tunneling, compressing and multiplexing traffic flows=20
> >>> (TCMTF). Since standard protocols are being used for tunneling,=20
> >>> compressing and multiplexing layers, the signaling methods of=20
> >>> those
> >> protocols will be used.
> >>> Interactions with the Working Groups and Areas in which these=20
> >>> protocols are developed can be expected. However, the development
> of
> >>> new compressing, multiplexing or tunneling protocols is not an=20
> >>> objective of this Working Group. In addition, since the current=20
> >>> RFC
> >>> 4170 would be considered as one of the options, this RFC could be
> >> obsoleted.
> >>>
> >>> Is this what you were asking?
> >>>
> >>> Thanks for your feedback.
> >>>
> >>> Jose
> >>>
> >>>> -----Mensaje original-----
> >>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En=20
> >>>> nombre de ken carlberg Enviado el: martes, 19 de febrero de 2013
> >>>> 14:17
> >>>> Para: jsaldana@unizar.es
> >>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
> >>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about=20
> >>>> TCMTF in
> >>>> IETF87
> >>>>
> >>>> Hola Jose,
> >>>>
> >>>> could you expand a bit more on your text in the proposed charter=20
> >>>> regarding "signaling methods".  Are you speaking in the more=20
> >>>> general context of information stored in headers of various=20
> >>>> protocol up and down the stack
> >>> (ie,
> >>>> layers 3, 4, and 5/app)?  Or, are you  speaking of concurrent=20
> >>>> resource signaling protocols like RSVP/RSVP-TE, or path=20
> >>>> establishment protocols
> >>> like
> >>>> MPLS?  Or, some combination of both?
> >>>>
> >>>> -ken
> >>>>
> >>>> _______________________________________________
> >>>> tcmtf mailing list
> >>>> tcmtf@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>>
> >>
> >> _______________________________________________
> >> tcmtf mailing list
> >> tcmtf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >


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

From fpb@tid.es  Thu Jun  6 04:53:13 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BD9421F9986 for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 04:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2a3Pc3S-Kc6V for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 04:53:09 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 49CD821F9942 for <tcmtf@ietf.org>; Thu,  6 Jun 2013 04:53:03 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MNY00FZSZO5HT@tid.hi.inet> for tcmtf@ietf.org; Thu, 06 Jun 2013 13:53:00 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 7C.6C.05654.C1870B15; Thu, 06 Jun 2013 13:53:00 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MNY00F13ZOCHT@tid.hi.inet> for tcmtf@ietf.org; Thu, 06 Jun 2013 13:53:00 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS7-MAD.hi.inet ([::1]) with mapi id 14.02.0342.003; Thu, 06 Jun 2013 13:52:59 +0200
Date: Thu, 06 Jun 2013 11:52:59 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <E004A7C54DE04F4BB87DB9F32308DA5C0C0012@MAIL4.fer.hr>
X-Originating-IP: [10.95.64.115]
To: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A29C8A2F7E@EX10-MB2-MAD.hi.inet>
Content-id: <7BBEF7638F1E33408D140CC2246D58B8@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-2
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] TCMTF: Documents to be generated. Small modification
Thread-index: Ac5h2eb/R9lrIRTzTmSkhKAFyvT4WQAwM8mgAAAmDdAABErmAA==
user-agent: Microsoft-MacOutlook/14.3.2.130206
X-AuditID: 0a5f4e69-b7f4b6d000001616-27-51b0781ce0e0
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJLMWRmVeSWpSXmKPExsXCFe9nqCtTsSHQYP5TFYtdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoEr4/7Rw2wFLTEVWx8eZ2tgbPfqYuTkkBAwkdjy8zYjhC0mceHe erYuRi4OIYHtjBK7l25mh3B+Mkps3H+KGcKZxiix78QqFpAWFgFViW2fHjGD2GwCWhKn70LE hQU8JW7+fckEYnMKOEl8vHUAaoWCxJ9zj8FqRATSJCb8nsgGYvMKeEtMPHcczGYWMJP40/aH FSIuKPFj8j2geg6guI7E10kRECXiEs2tN1kgbG2JJ+8ugJUzCshKvJs/nxVivJfE1E9/2SFs J4k9s56D1YsK6EncPNPCCnGOgMSSPeeZIWxRiZeP/7FOYBSfheSKWUiumIVwxSwkV8xCcsUC RtZVjGLFSUWZ6RkluYmZOekGRnoZmXqZeaklmxgh0ZW5g3H5TpVDjAIcjEo8vAd81wcKsSaW FVfmHmKU4GBWEuHd5bMhUIg3JbGyKrUoP76oNCe1+BAjEwenVAPjrIXuGXd3KIdv+5Vg7WiU mRDbGWB++knA5oxnE1dcvhi2fPmFBPnDF8UOfm94u/llvmJHq+iD54mGxtx3ReJit8vbbry8 VJr/v6Vd88W1wXNi/t9gfbKbpZXv81MRPf0dlx5HzF3yW8iG4Zyyz6bIivt6O+XUdnpX7O46 3pB3/fa+csb8n9duKbEUZyQaajEXFScCAM5El3+MAgAA
Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small modification
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 11:53:13 -0000

And what about:

TCMTF - negotiation protocol

Do you found it more descriptive?

Regards,

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




On 06/06/13 11:51, "Mirko Su=BEnjevi=E6" <Mirko.Suznjevic@fer.hr> wrote:

>Hello,
>I think these names are ok. Maybe we should discuss the second one in
>more detail.
>Perhaps include negotiation in the name of the draft so its purpose is
>evident from the title? As the purpose of that draft is to establish
>which particular parameters will be used.
>My suggestions are:
>TCMTF - negotiation signalling
>TCMTF - negotiation process
>TCMTF - parameter signalling
>Or something along those lines?
>Mirko
>
>-----Original Message-----
>From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of
>Jose Saldana
>Sent: Wednesday, June 5, 2013 12:56 PM
>To: tcmtf@ietf.org
>Cc: tsv-area@ietf.org; spencerdawkins.ietf@gmail.com; 'ken carlberg';
>Martin Stiemerling
>Subject: [tcmtf] TCMTF: Documents to be generated. Small modification
>
>In the conf-call of yesterday it was also clear that for the IETF it is
>better to split Document A into two documents:
>
>- The "TCMTF reference model" (1): the protocol stack and scenarios. It
>should be said that each protocol at each layer will use its own
>signaling mechanisms.
>
>- The "TCMTF-specific signaling": there are some things we will need to
>deploy:
>       - a negotiation mechanism (2) to decide the options to use at each =
layer
>(e.g. a mux and demux agree on using ROHC+PPPMux+GRE)
>       - a mechanism to setup/release a TCMTF tunnel (3)between a multiple=
xer
>and a de-multiplexer
>
>
>The current draft is the TCMTF "reference model", since it does not talk
>about specific signaling issues.
>
>By now, we don't have to propose the "TCMTF specific signaling". It would
>be something to be deployed if the Working Group is created.
>
>This same idea was proposed by Ken Carlberg in February. The advantages
>of this new distribution of the documents are (quoting Ken):
>
>> One thing to keep in mind is that it is possible that (2) and (3)
>> (below) can change over time and yet (1) (the reference model) does
>> not, then it may be best to separate (1) from the other items.
>
>> a more encompassing architecture or framework that would include
>> sample scenarios upon which your deliverables A & B are aimed at?  My
>> impression is that you may want to point the reader of documents A & B
>> to the same reference model, and instead of repeating the same text,
>> it may be helpful to separate this into a separate document.
>
>
>Once discussed, I would create a new charter proposal including these
>changes.
>
>
>Do you like these short names for the documents?
>
>- "TCMTF reference model".
>https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>
>- "TCMTF-specific signaling". Future work
>
>- "TCMTF recommendations".
>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>
>
>Your feedback will be welcome. Thanks!
>
>Jose
>
>> -----Mensaje original-----
>> De: ken carlberg [mailto:carlberg@g11.org.uk] Enviado el: martes, 05
>> de marzo de 2013 17:07
>> Para: jsaldana@unizar.es
>> CC: 'ken carlberg'; tcmtf@ietf.org; tsv-area@ietf.org
>> Asunto: Re: [tcmtf] About the possibility of having a BOF about TCMTF
>> in
>> IETF87
>>
>> Hola Jose,
>>
>> Thanks for the expanded explanation, and again, apologies for the
>> tardy repsonse.  Its helpful to understand that document A and B are
>> sequential
>to
>> each other.  One thing to keep in mind is that if its possible that 2
>> and
>3
>> (below) can change over time and yet 1 (the reference model) does not,
>> then it may be best to separate 1 from the other items.
>>
>> as for what you outline as a discussion point for future work, it
>> seems
>fine.  I
>> just have a personal bias that if you have a clear idea of the things
>you'd like
>> to accomplish in the future, then having a requirements document would
>> be helpful to focus those thoughts without having to have one
>> particular solution.  But that's a discussion point that could be
>> brought up during
>the
>> BoF, or sometime afterwards.
>>
>> cheers,
>>
>> -ken
>>
>>
>> > A main document (A) in which we explain the method, the scenarios
>> > and the minimum signaling issues in order to make it work. The idea
>> > is that document
>> > (A) would be self-contained. Since we are not defining new protocols
>(i.e.
>> > already existing compressing, multiplexing and tunneling protocols
>> > are to be used), we understand that this can be done in a single
>>document.
>> > It would
>> > include:
>> >
>> > 1- Protocol stack (it would be the "reference model")
>> > 2- a negotiation mechanism to decide the options to use at each
>> > layer
>> > 3- a mechanism to setup/release a tunnel between a multiplexer and a
>> > de-multiplexer
>> >
>> > Of course, another approach could be separating 1 from 2&3. However,
>> > we think this is not necessary since the method is not too
>>complicated.
>> >
>> >
>> > Document (B) would only contain recommendations of how to better use
>> > the method proposed in document (A), i.e., classification and
>> > maximum
>> delays.
>> >
>> > So clearly document (B) would totally depend on the reference model
>> > of document (A).
>> >
>> >
>> > The idea of point 9 is to talk about some other interesting ideas
>> > which are considered as "future work":
>> > - a mechanism for a multiplexer to discover a de-multiplexer
>> > - mechanism to select an optimal multiplexer and a de-multiplexer
>> > when there are more than one muxer/de-muxer for a flow
>> > - dynamically applying TCMTF
>> > - etc.
>> >
>> > What do you think?
>> >
>> > Thanks again for your feedback. Thinking and explaining things is
>> > always a good exercise!
>> >
>> > Jose
>> >
>> >> -----Mensaje original-----
>> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> >> nombre de ken carlberg Enviado el: mi=E9rcoles, 27 de febrero de 2013
>> >> 16:23
>> >> Para: jsaldana@unizar.es
>> >> CC: tcmtf@ietf.org; tsv-area@ietf.org
>> >> Asunto: Re: [tcmtf] About the possibility of having a BOF about
>> >> TCMTF in
>> >> IETF87
>> >>
>> >> Hola Jose,
>> >>
>> >> sorry for the tardy reply.  The altered text below is helpful,
>>thanks.
>> >>
>> >> With respect to your candidate deliverables, it appears that you
>> >> have
>> > listed
>> >> two for the proposed group: (A) a document that describes options
>> >> and negotiation mechanisms, and (B) a document describing
>> recommendations
>> >> of which packet types should be multiplexed and a list fo traffic
>> > classification
>> >> methods.  Have you considered a third document that presents a more
>> >> encompassing architecture or framework that would include sample
>> >> scenarios upon which your deliverables A & B are aimed at?  My
>> >> impression
>> > is
>> >> that you may want to point the reader of documents A & B to the
>> >> same reference model, and instead of repeating the same text, it
>> >> may be helpful to separate this into a separate document.
>> >>
>> >> Also, would section 9 of your proposed charter lead one to consider
>> >> a requirements document?  Many times, new groups start with a
>> >> requirements document, but since you have a good focus of what you
>> >> want to accomplish, perhaps your last deliverable could be a
>> >> requirements document that would guide any future work.
>> >>
>> >> -ken
>> >>
>> >> ps, I don't want to advocate more work, but rather just have you
>> >> consider other possibilities (and feel free to shoot them down :-)
>> >>
>> >>
>> >> On Feb 22, 2013, at 5:39 AM, Jose Saldana <jsaldana@unizar.es> wrote:
>> >>
>> >>> Hi Ken,
>> >>>
>> >>> Sorry for the delay. I think you are talking about Paragraph 5:
>> >>>
>> >>> 5. So the first objective of this group is to specify the protocol
>> >>> stack for tunneling, compressing and multiplexing traffic flows
>> >>> (TCMTF). Since standard protocols are being used at each layer,
>> >>> the signaling methods of those protocols will be used.
>> >>> Interactions with the Working Groups and Areas in which these
>> >>> protocols are developed can be expected. However, the development
>> >>> of new compressing, multiplexing or tunneling protocols is not an
>> >>> objective of this Working Group. In addition, since the current
>> >>> RFC 4170 would be
>> >> considered as one of the options, this RFC could be obsoleted.
>> >>>
>> >>> Perhaps this is a bit confusing. When we say "at each layer", we
>> >>> are talking about "tunneling, compressing and multiplexing" layers.
>> >>> Perhaps this can be a bit confusing. What about this?:
>> >>>
>> >>> 5. So the first objective of this group is to specify the protocol
>> >>> stack for tunneling, compressing and multiplexing traffic flows
>> >>> (TCMTF). Since standard protocols are being used for tunneling,
>> >>> compressing and multiplexing layers, the signaling methods of
>> >>> those
>> >> protocols will be used.
>> >>> Interactions with the Working Groups and Areas in which these
>> >>> protocols are developed can be expected. However, the development
>> of
>> >>> new compressing, multiplexing or tunneling protocols is not an
>> >>> objective of this Working Group. In addition, since the current
>> >>> RFC
>> >>> 4170 would be considered as one of the options, this RFC could be
>> >> obsoleted.
>> >>>
>> >>> Is this what you were asking?
>> >>>
>> >>> Thanks for your feedback.
>> >>>
>> >>> Jose
>> >>>
>> >>>> -----Mensaje original-----
>> >>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> >>>> nombre de ken carlberg Enviado el: martes, 19 de febrero de 2013
>> >>>> 14:17
>> >>>> Para: jsaldana@unizar.es
>> >>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
>> >>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about
>> >>>> TCMTF in
>> >>>> IETF87
>> >>>>
>> >>>> Hola Jose,
>> >>>>
>> >>>> could you expand a bit more on your text in the proposed charter
>> >>>> regarding "signaling methods".  Are you speaking in the more
>> >>>> general context of information stored in headers of various
>> >>>> protocol up and down the stack
>> >>> (ie,
>> >>>> layers 3, 4, and 5/app)?  Or, are you  speaking of concurrent
>> >>>> resource signaling protocols like RSVP/RSVP-TE, or path
>> >>>> establishment protocols
>> >>> like
>> >>>> MPLS?  Or, some combination of both?
>> >>>>
>> >>>> -ken
>> >>>>
>> >>>> _______________________________________________
>> >>>> tcmtf mailing list
>> >>>> tcmtf@ietf.org
>> >>>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>
>> >>
>> >> _______________________________________________
>> >> tcmtf mailing list
>> >> tcmtf@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/tcmtf
>> >
>
>
>_______________________________________________
>tcmtf mailing list
>tcmtf@ietf.org
>https://www.ietf.org/mailman/listinfo/tcmtf
>_______________________________________________
>tcmtf mailing list
>tcmtf@ietf.org
>https://www.ietf.org/mailman/listinfo/tcmtf


________________________________

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

From Mirko.Suznjevic@fer.hr  Thu Jun  6 05:31:55 2013
Return-Path: <Mirko.Suznjevic@fer.hr>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8348221F8E6E for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 05:31:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.927
X-Spam-Level: 
X-Spam-Status: No, score=-1.927 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t8B1C8FLJvYJ for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 05:31:51 -0700 (PDT)
Received: from mail.fer.hr (mail5.fer.hr [161.53.72.235]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA5921F8B07 for <tcmtf@ietf.org>; Thu,  6 Jun 2013 05:31:41 -0700 (PDT)
Received: from POSTAR.fer.hr (2002:a135:48ed::a135:48ed) by MAIL5.fer.hr (2002:a135:48eb::a135:48eb) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 6 Jun 2013 14:31:39 +0200
Received: from MAIL4.fer.hr ([2002:a135:48ea::a135:48ea]) by POSTAR.fer.hr ([2002:a135:48ed::a135:48ed]) with mapi id 14.02.0247.003; Thu, 6 Jun 2013 14:31:39 +0200
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: FERNANDO PASCUAL BLANCO <fpb@tid.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] TCMTF: Documents to be generated. Small modification
Thread-Index: Ac5h2eb/R9lrIRTzTmSkhKAFyvT4WQAwM8mgAAAmDdAABErmAAABUBCA
Date: Thu, 6 Jun 2013 12:31:37 +0000
Message-ID: <E004A7C54DE04F4BB87DB9F32308DA5C0C0123@MAIL4.fer.hr>
References: <E004A7C54DE04F4BB87DB9F32308DA5C0C0012@MAIL4.fer.hr> <F5EDC35DF914C1428C28E149F10463A29C8A2F7E@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A29C8A2F7E@EX10-MB2-MAD.hi.inet>
Accept-Language: en-US, hr-HR
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.53.19.114]
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small modification
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 12:31:55 -0000

Yes i think that is better.
Mirko

-----Original Message-----
From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]=20
Sent: Thursday, June 6, 2013 1:53 PM
To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small modification

And what about:

TCMTF - negotiation protocol

Do you found it more descriptive?

Regards,

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




On 06/06/13 11:51, "Mirko Su=BEnjevi=E6" <Mirko.Suznjevic@fer.hr> wrote:

>Hello,
>I think these names are ok. Maybe we should discuss the second one in=20
>more detail.
>Perhaps include negotiation in the name of the draft so its purpose is=20
>evident from the title? As the purpose of that draft is to establish=20
>which particular parameters will be used.
>My suggestions are:
>TCMTF - negotiation signalling
>TCMTF - negotiation process
>TCMTF - parameter signalling
>Or something along those lines?
>Mirko
>
>-----Original Message-----
>From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf=20
>Of Jose Saldana
>Sent: Wednesday, June 5, 2013 12:56 PM
>To: tcmtf@ietf.org
>Cc: tsv-area@ietf.org; spencerdawkins.ietf@gmail.com; 'ken carlberg';=20
>Martin Stiemerling
>Subject: [tcmtf] TCMTF: Documents to be generated. Small modification
>
>In the conf-call of yesterday it was also clear that for the IETF it is=20
>better to split Document A into two documents:
>
>- The "TCMTF reference model" (1): the protocol stack and scenarios. It=20
>should be said that each protocol at each layer will use its own=20
>signaling mechanisms.
>
>- The "TCMTF-specific signaling": there are some things we will need to
>deploy:
>       - a negotiation mechanism (2) to decide the options to use at=20
>each layer (e.g. a mux and demux agree on using ROHC+PPPMux+GRE)
>       - a mechanism to setup/release a TCMTF tunnel (3)between a=20
>multiplexer and a de-multiplexer
>
>
>The current draft is the TCMTF "reference model", since it does not=20
>talk about specific signaling issues.
>
>By now, we don't have to propose the "TCMTF specific signaling". It=20
>would be something to be deployed if the Working Group is created.
>
>This same idea was proposed by Ken Carlberg in February. The advantages=20
>of this new distribution of the documents are (quoting Ken):
>
>> One thing to keep in mind is that it is possible that (2) and (3)
>> (below) can change over time and yet (1) (the reference model) does=20
>> not, then it may be best to separate (1) from the other items.
>
>> a more encompassing architecture or framework that would include=20
>> sample scenarios upon which your deliverables A & B are aimed at?  My=20
>> impression is that you may want to point the reader of documents A &=20
>> B to the same reference model, and instead of repeating the same=20
>> text, it may be helpful to separate this into a separate document.
>
>
>Once discussed, I would create a new charter proposal including these=20
>changes.
>
>
>Do you like these short names for the documents?
>
>- "TCMTF reference model".
>https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>
>- "TCMTF-specific signaling". Future work
>
>- "TCMTF recommendations".
>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>
>
>Your feedback will be welcome. Thanks!
>
>Jose
>
>> -----Mensaje original-----
>> De: ken carlberg [mailto:carlberg@g11.org.uk] Enviado el: martes, 05=20
>> de marzo de 2013 17:07
>> Para: jsaldana@unizar.es
>> CC: 'ken carlberg'; tcmtf@ietf.org; tsv-area@ietf.org
>> Asunto: Re: [tcmtf] About the possibility of having a BOF about TCMTF=20
>> in
>> IETF87
>>
>> Hola Jose,
>>
>> Thanks for the expanded explanation, and again, apologies for the=20
>> tardy repsonse.  Its helpful to understand that document A and B are=20
>> sequential
>to
>> each other.  One thing to keep in mind is that if its possible that 2=20
>> and
>3
>> (below) can change over time and yet 1 (the reference model) does=20
>> not, then it may be best to separate 1 from the other items.
>>
>> as for what you outline as a discussion point for future work, it=20
>> seems
>fine.  I
>> just have a personal bias that if you have a clear idea of the things
>you'd like
>> to accomplish in the future, then having a requirements document=20
>> would be helpful to focus those thoughts without having to have one=20
>> particular solution.  But that's a discussion point that could be=20
>> brought up during
>the
>> BoF, or sometime afterwards.
>>
>> cheers,
>>
>> -ken
>>
>>
>> > A main document (A) in which we explain the method, the scenarios=20
>> > and the minimum signaling issues in order to make it work. The idea=20
>> > is that document
>> > (A) would be self-contained. Since we are not defining new=20
>> > protocols
>(i.e.
>> > already existing compressing, multiplexing and tunneling protocols=20
>> > are to be used), we understand that this can be done in a single
>>document.
>> > It would
>> > include:
>> >
>> > 1- Protocol stack (it would be the "reference model")
>> > 2- a negotiation mechanism to decide the options to use at each=20
>> > layer
>> > 3- a mechanism to setup/release a tunnel between a multiplexer and=20
>> > a de-multiplexer
>> >
>> > Of course, another approach could be separating 1 from 2&3.=20
>> > However, we think this is not necessary since the method is not too
>>complicated.
>> >
>> >
>> > Document (B) would only contain recommendations of how to better=20
>> > use the method proposed in document (A), i.e., classification and=20
>> > maximum
>> delays.
>> >
>> > So clearly document (B) would totally depend on the reference model=20
>> > of document (A).
>> >
>> >
>> > The idea of point 9 is to talk about some other interesting ideas=20
>> > which are considered as "future work":
>> > - a mechanism for a multiplexer to discover a de-multiplexer
>> > - mechanism to select an optimal multiplexer and a de-multiplexer=20
>> > when there are more than one muxer/de-muxer for a flow
>> > - dynamically applying TCMTF
>> > - etc.
>> >
>> > What do you think?
>> >
>> > Thanks again for your feedback. Thinking and explaining things is=20
>> > always a good exercise!
>> >
>> > Jose
>> >
>> >> -----Mensaje original-----
>> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En=20
>> >> nombre de ken carlberg Enviado el: mi=E9rcoles, 27 de febrero de=20
>> >> 2013
>> >> 16:23
>> >> Para: jsaldana@unizar.es
>> >> CC: tcmtf@ietf.org; tsv-area@ietf.org
>> >> Asunto: Re: [tcmtf] About the possibility of having a BOF about=20
>> >> TCMTF in
>> >> IETF87
>> >>
>> >> Hola Jose,
>> >>
>> >> sorry for the tardy reply.  The altered text below is helpful,
>>thanks.
>> >>
>> >> With respect to your candidate deliverables, it appears that you=20
>> >> have
>> > listed
>> >> two for the proposed group: (A) a document that describes options=20
>> >> and negotiation mechanisms, and (B) a document describing
>> recommendations
>> >> of which packet types should be multiplexed and a list fo traffic
>> > classification
>> >> methods.  Have you considered a third document that presents a=20
>> >> more encompassing architecture or framework that would include=20
>> >> sample scenarios upon which your deliverables A & B are aimed at? =20
>> >> My impression
>> > is
>> >> that you may want to point the reader of documents A & B to the=20
>> >> same reference model, and instead of repeating the same text, it=20
>> >> may be helpful to separate this into a separate document.
>> >>
>> >> Also, would section 9 of your proposed charter lead one to=20
>> >> consider a requirements document?  Many times, new groups start=20
>> >> with a requirements document, but since you have a good focus of=20
>> >> what you want to accomplish, perhaps your last deliverable could=20
>> >> be a requirements document that would guide any future work.
>> >>
>> >> -ken
>> >>
>> >> ps, I don't want to advocate more work, but rather just have you=20
>> >> consider other possibilities (and feel free to shoot them down :-)
>> >>
>> >>
>> >> On Feb 22, 2013, at 5:39 AM, Jose Saldana <jsaldana@unizar.es> wrote:
>> >>
>> >>> Hi Ken,
>> >>>
>> >>> Sorry for the delay. I think you are talking about Paragraph 5:
>> >>>
>> >>> 5. So the first objective of this group is to specify the=20
>> >>> protocol stack for tunneling, compressing and multiplexing=20
>> >>> traffic flows (TCMTF). Since standard protocols are being used at=20
>> >>> each layer, the signaling methods of those protocols will be used.
>> >>> Interactions with the Working Groups and Areas in which these=20
>> >>> protocols are developed can be expected. However, the development=20
>> >>> of new compressing, multiplexing or tunneling protocols is not an=20
>> >>> objective of this Working Group. In addition, since the current=20
>> >>> RFC 4170 would be
>> >> considered as one of the options, this RFC could be obsoleted.
>> >>>
>> >>> Perhaps this is a bit confusing. When we say "at each layer", we=20
>> >>> are talking about "tunneling, compressing and multiplexing" layers.
>> >>> Perhaps this can be a bit confusing. What about this?:
>> >>>
>> >>> 5. So the first objective of this group is to specify the=20
>> >>> protocol stack for tunneling, compressing and multiplexing=20
>> >>> traffic flows (TCMTF). Since standard protocols are being used=20
>> >>> for tunneling, compressing and multiplexing layers, the signaling=20
>> >>> methods of those
>> >> protocols will be used.
>> >>> Interactions with the Working Groups and Areas in which these=20
>> >>> protocols are developed can be expected. However, the development
>> of
>> >>> new compressing, multiplexing or tunneling protocols is not an=20
>> >>> objective of this Working Group. In addition, since the current=20
>> >>> RFC
>> >>> 4170 would be considered as one of the options, this RFC could be
>> >> obsoleted.
>> >>>
>> >>> Is this what you were asking?
>> >>>
>> >>> Thanks for your feedback.
>> >>>
>> >>> Jose
>> >>>
>> >>>> -----Mensaje original-----
>> >>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En=20
>> >>>> nombre de ken carlberg Enviado el: martes, 19 de febrero de 2013
>> >>>> 14:17
>> >>>> Para: jsaldana@unizar.es
>> >>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
>> >>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about=20
>> >>>> TCMTF in
>> >>>> IETF87
>> >>>>
>> >>>> Hola Jose,
>> >>>>
>> >>>> could you expand a bit more on your text in the proposed charter=20
>> >>>> regarding "signaling methods".  Are you speaking in the more=20
>> >>>> general context of information stored in headers of various=20
>> >>>> protocol up and down the stack
>> >>> (ie,
>> >>>> layers 3, 4, and 5/app)?  Or, are you  speaking of concurrent=20
>> >>>> resource signaling protocols like RSVP/RSVP-TE, or path=20
>> >>>> establishment protocols
>> >>> like
>> >>>> MPLS?  Or, some combination of both?
>> >>>>
>> >>>> -ken
>> >>>>
>> >>>> _______________________________________________
>> >>>> tcmtf mailing list
>> >>>> tcmtf@ietf.org
>> >>>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>
>> >>
>> >> _______________________________________________
>> >> tcmtf mailing list
>> >> tcmtf@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/tcmtf
>> >
>
>
>_______________________________________________
>tcmtf mailing list
>tcmtf@ietf.org
>https://www.ietf.org/mailman/listinfo/tcmtf
>_______________________________________________
>tcmtf mailing list
>tcmtf@ietf.org
>https://www.ietf.org/mailman/listinfo/tcmtf


________________________________

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

From jsaldana@unizar.es  Thu Jun  6 06:05:25 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C620421F99A5 for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 06:05:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PVT11f4lgFaq for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 06:05:21 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 57B3E21F99A9 for <tcmtf@ietf.org>; Thu,  6 Jun 2013 06:05:19 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r56D5DaP020490; Thu, 6 Jun 2013 15:05:13 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "=?iso-8859-2?Q?'Mirko_Su=BEnjevi=E6'?=" <Mirko.Suznjevic@fer.hr>, "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>
References: <E004A7C54DE04F4BB87DB9F32308DA5C0C0012@MAIL4.fer.hr>	<F5EDC35DF914C1428C28E149F10463A29C8A2F7E@EX10-MB2-MAD.hi.inet> <E004A7C54DE04F4BB87DB9F32308DA5C0C0123@MAIL4.fer.hr>
In-Reply-To: <E004A7C54DE04F4BB87DB9F32308DA5C0C0123@MAIL4.fer.hr>
Date: Thu, 6 Jun 2013 15:05:17 +0200
Organization: Universidad de Zaragoza
Message-ID: <00a501ce62b6$7e2cd3c0$7a867b40$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIvoD89gWUXtE92F4lsPmTNp5lNyQFP/SVlAfcfpwOYS/KL8A==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small modification
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 13:05:25 -0000

One question:

The new second draft should include:

- The negotiation
- The setup/release a TCMTF tunnel between a mux and a demux

Do you think "TCMTF - negotiation protocol" also includes the second =
idea?

Would it be better "TCMTF - negotiation and setup" ?

Thanks!

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Mirko Su=BEnjevic
> Enviado el: jueves, 06 de junio de 2013 14:32
> Para: FERNANDO PASCUAL BLANCO; tcmtf@ietf.org
> Asunto: Re: [tcmtf] TCMTF: Documents to be generated. Small =
modification
>=20
> Yes i think that is better.
> Mirko
>=20
> -----Original Message-----
> From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> Sent: Thursday, June 6, 2013 1:53 PM
> To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org
> Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small =
modification
>=20
> And what about:
>=20
> TCMTF - negotiation protocol
>=20
> Do you found it more descriptive?
>=20
> Regards,
>=20
> Fernando Pascual Blanco
> Telef=F3nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>=20
>=20
>=20
>=20
> On 06/06/13 11:51, "Mirko Su=BEnjevi=E6" <Mirko.Suznjevic@fer.hr> =
wrote:
>=20
> >Hello,
> >I think these names are ok. Maybe we should discuss the second one in
> >more detail.
> >Perhaps include negotiation in the name of the draft so its purpose =
is
> >evident from the title? As the purpose of that draft is to establish
> >which particular parameters will be used.
> >My suggestions are:
> >TCMTF - negotiation signalling
> >TCMTF - negotiation process
> >TCMTF - parameter signalling
> >Or something along those lines?
> >Mirko
> >
> >-----Original Message-----
> >From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On =
Behalf
> >Of Jose Saldana
> >Sent: Wednesday, June 5, 2013 12:56 PM
> >To: tcmtf@ietf.org
> >Cc: tsv-area@ietf.org; spencerdawkins.ietf@gmail.com; 'ken carlberg';
> >Martin Stiemerling
> >Subject: [tcmtf] TCMTF: Documents to be generated. Small modification
> >
> >In the conf-call of yesterday it was also clear that for the IETF it =
is
> >better to split Document A into two documents:
> >
> >- The "TCMTF reference model" (1): the protocol stack and scenarios. =
It
> >should be said that each protocol at each layer will use its own
> >signaling mechanisms.
> >
> >- The "TCMTF-specific signaling": there are some things we will need =
to
> >deploy:
> >       - a negotiation mechanism (2) to decide the options to use at
> >each layer (e.g. a mux and demux agree on using ROHC+PPPMux+GRE)
> >       - a mechanism to setup/release a TCMTF tunnel (3)between a
> >multiplexer and a de-multiplexer
> >
> >
> >The current draft is the TCMTF "reference model", since it does not
> >talk about specific signaling issues.
> >
> >By now, we don't have to propose the "TCMTF specific signaling". It
> >would be something to be deployed if the Working Group is created.
> >
> >This same idea was proposed by Ken Carlberg in February. The =
advantages
> >of this new distribution of the documents are (quoting Ken):
> >
> >> One thing to keep in mind is that it is possible that (2) and (3)
> >> (below) can change over time and yet (1) (the reference model) does
> >> not, then it may be best to separate (1) from the other items.
> >
> >> a more encompassing architecture or framework that would include
> >> sample scenarios upon which your deliverables A & B are aimed at?  =
My
> >> impression is that you may want to point the reader of documents A =
&
> >> B to the same reference model, and instead of repeating the same
> >> text, it may be helpful to separate this into a separate document.
> >
> >
> >Once discussed, I would create a new charter proposal including these
> >changes.
> >
> >
> >Do you like these short names for the documents?
> >
> >- "TCMTF reference model".
> >https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
> >
> >- "TCMTF-specific signaling". Future work
> >
> >- "TCMTF recommendations".
> >http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
> >
> >
> >Your feedback will be welcome. Thanks!
> >
> >Jose
> >
> >> -----Mensaje original-----
> >> De: ken carlberg [mailto:carlberg@g11.org.uk] Enviado el: martes, =
05
> >> de marzo de 2013 17:07
> >> Para: jsaldana@unizar.es
> >> CC: 'ken carlberg'; tcmtf@ietf.org; tsv-area@ietf.org
> >> Asunto: Re: [tcmtf] About the possibility of having a BOF about =
TCMTF
> >> in
> >> IETF87
> >>
> >> Hola Jose,
> >>
> >> Thanks for the expanded explanation, and again, apologies for the
> >> tardy repsonse.  Its helpful to understand that document A and B =
are
> >> sequential
> >to
> >> each other.  One thing to keep in mind is that if its possible that =
2
> >> and
> >3
> >> (below) can change over time and yet 1 (the reference model) does
> >> not, then it may be best to separate 1 from the other items.
> >>
> >> as for what you outline as a discussion point for future work, it
> >> seems
> >fine.  I
> >> just have a personal bias that if you have a clear idea of the =
things
> >you'd like
> >> to accomplish in the future, then having a requirements document
> >> would be helpful to focus those thoughts without having to have one
> >> particular solution.  But that's a discussion point that could be
> >> brought up during
> >the
> >> BoF, or sometime afterwards.
> >>
> >> cheers,
> >>
> >> -ken
> >>
> >>
> >> > A main document (A) in which we explain the method, the scenarios
> >> > and the minimum signaling issues in order to make it work. The =
idea
> >> > is that document
> >> > (A) would be self-contained. Since we are not defining new
> >> > protocols
> >(i.e.
> >> > already existing compressing, multiplexing and tunneling =
protocols
> >> > are to be used), we understand that this can be done in a single
> >>document.
> >> > It would
> >> > include:
> >> >
> >> > 1- Protocol stack (it would be the "reference model")
> >> > 2- a negotiation mechanism to decide the options to use at each
> >> > layer
> >> > 3- a mechanism to setup/release a tunnel between a multiplexer =
and
> >> > a de-multiplexer
> >> >
> >> > Of course, another approach could be separating 1 from 2&3.
> >> > However, we think this is not necessary since the method is not =
too
> >>complicated.
> >> >
> >> >
> >> > Document (B) would only contain recommendations of how to better
> >> > use the method proposed in document (A), i.e., classification and
> >> > maximum
> >> delays.
> >> >
> >> > So clearly document (B) would totally depend on the reference =
model
> >> > of document (A).
> >> >
> >> >
> >> > The idea of point 9 is to talk about some other interesting ideas
> >> > which are considered as "future work":
> >> > - a mechanism for a multiplexer to discover a de-multiplexer
> >> > - mechanism to select an optimal multiplexer and a de-multiplexer
> >> > when there are more than one muxer/de-muxer for a flow
> >> > - dynamically applying TCMTF
> >> > - etc.
> >> >
> >> > What do you think?
> >> >
> >> > Thanks again for your feedback. Thinking and explaining things is
> >> > always a good exercise!
> >> >
> >> > Jose
> >> >
> >> >> -----Mensaje original-----
> >> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> >> nombre de ken carlberg Enviado el: mi=E9rcoles, 27 de febrero de
> >> >> 2013
> >> >> 16:23
> >> >> Para: jsaldana@unizar.es
> >> >> CC: tcmtf@ietf.org; tsv-area@ietf.org
> >> >> Asunto: Re: [tcmtf] About the possibility of having a BOF about
> >> >> TCMTF in
> >> >> IETF87
> >> >>
> >> >> Hola Jose,
> >> >>
> >> >> sorry for the tardy reply.  The altered text below is helpful,
> >>thanks.
> >> >>
> >> >> With respect to your candidate deliverables, it appears that you
> >> >> have
> >> > listed
> >> >> two for the proposed group: (A) a document that describes =
options
> >> >> and negotiation mechanisms, and (B) a document describing
> >> recommendations
> >> >> of which packet types should be multiplexed and a list fo =
traffic
> >> > classification
> >> >> methods.  Have you considered a third document that presents a
> >> >> more encompassing architecture or framework that would include
> >> >> sample scenarios upon which your deliverables A & B are aimed =
at?
> >> >> My impression
> >> > is
> >> >> that you may want to point the reader of documents A & B to the
> >> >> same reference model, and instead of repeating the same text, it
> >> >> may be helpful to separate this into a separate document.
> >> >>
> >> >> Also, would section 9 of your proposed charter lead one to
> >> >> consider a requirements document?  Many times, new groups start
> >> >> with a requirements document, but since you have a good focus of
> >> >> what you want to accomplish, perhaps your last deliverable could
> >> >> be a requirements document that would guide any future work.
> >> >>
> >> >> -ken
> >> >>
> >> >> ps, I don't want to advocate more work, but rather just have you
> >> >> consider other possibilities (and feel free to shoot them down =
:-)
> >> >>
> >> >>
> >> >> On Feb 22, 2013, at 5:39 AM, Jose Saldana <jsaldana@unizar.es>
> wrote:
> >> >>
> >> >>> Hi Ken,
> >> >>>
> >> >>> Sorry for the delay. I think you are talking about Paragraph 5:
> >> >>>
> >> >>> 5. So the first objective of this group is to specify the
> >> >>> protocol stack for tunneling, compressing and multiplexing
> >> >>> traffic flows (TCMTF). Since standard protocols are being used =
at
> >> >>> each layer, the signaling methods of those protocols will be =
used.
> >> >>> Interactions with the Working Groups and Areas in which these
> >> >>> protocols are developed can be expected. However, the
> development
> >> >>> of new compressing, multiplexing or tunneling protocols is not =
an
> >> >>> objective of this Working Group. In addition, since the current
> >> >>> RFC 4170 would be
> >> >> considered as one of the options, this RFC could be obsoleted.
> >> >>>
> >> >>> Perhaps this is a bit confusing. When we say "at each layer", =
we
> >> >>> are talking about "tunneling, compressing and multiplexing" =
layers.
> >> >>> Perhaps this can be a bit confusing. What about this?:
> >> >>>
> >> >>> 5. So the first objective of this group is to specify the
> >> >>> protocol stack for tunneling, compressing and multiplexing
> >> >>> traffic flows (TCMTF). Since standard protocols are being used
> >> >>> for tunneling, compressing and multiplexing layers, the =
signaling
> >> >>> methods of those
> >> >> protocols will be used.
> >> >>> Interactions with the Working Groups and Areas in which these
> >> >>> protocols are developed can be expected. However, the
> development
> >> of
> >> >>> new compressing, multiplexing or tunneling protocols is not an
> >> >>> objective of this Working Group. In addition, since the current
> >> >>> RFC
> >> >>> 4170 would be considered as one of the options, this RFC could =
be
> >> >> obsoleted.
> >> >>>
> >> >>> Is this what you were asking?
> >> >>>
> >> >>> Thanks for your feedback.
> >> >>>
> >> >>> Jose
> >> >>>
> >> >>>> -----Mensaje original-----
> >> >>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> >>>> nombre de ken carlberg Enviado el: martes, 19 de febrero de =
2013
> >> >>>> 14:17
> >> >>>> Para: jsaldana@unizar.es
> >> >>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
> >> >>>> Asunto: Re: [tcmtf] About the possibility of having a BOF =
about
> >> >>>> TCMTF in
> >> >>>> IETF87
> >> >>>>
> >> >>>> Hola Jose,
> >> >>>>
> >> >>>> could you expand a bit more on your text in the proposed =
charter
> >> >>>> regarding "signaling methods".  Are you speaking in the more
> >> >>>> general context of information stored in headers of various
> >> >>>> protocol up and down the stack
> >> >>> (ie,
> >> >>>> layers 3, 4, and 5/app)?  Or, are you  speaking of concurrent
> >> >>>> resource signaling protocols like RSVP/RSVP-TE, or path
> >> >>>> establishment protocols
> >> >>> like
> >> >>>> MPLS?  Or, some combination of both?
> >> >>>>
> >> >>>> -ken
> >> >>>>
> >> >>>> _______________________________________________
> >> >>>> tcmtf mailing list
> >> >>>> tcmtf@ietf.org
> >> >>>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>
> >> >>
> >> >> _______________________________________________
> >> >> tcmtf mailing list
> >> >> tcmtf@ietf.org
> >> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >
> >
> >
> >_______________________________________________
> >tcmtf mailing list
> >tcmtf@ietf.org
> >https://www.ietf.org/mailman/listinfo/tcmtf
> >_______________________________________________
> >tcmtf mailing list
> >tcmtf@ietf.org
> >https://www.ietf.org/mailman/listinfo/tcmtf
>=20
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar
> nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en =
el enlace
> situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send =
and
> receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From jsaldana@unizar.es  Thu Jun  6 06:14:41 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0DBC21F99D6 for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 06:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3tjNFOLaeId for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 06:14:36 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id F242721F99E8 for <tcmtf@ietf.org>; Thu,  6 Jun 2013 06:14:35 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r56DEVvd021383; Thu, 6 Jun 2013 15:14:31 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "=?iso-8859-1?Q?'Juli=E1n_Fern=E1ndez-Navajas'?=" <navajas@unizar.es>
References: <004e01ce61de$493b4c60$dbb1e520$@unizar.es> <51B0434D.9030205@unizar.es>
In-Reply-To: <51B0434D.9030205@unizar.es>
Date: Thu, 6 Jun 2013 15:14:35 +0200
Organization: Universidad de Zaragoza
Message-ID: <00a601ce62b7$cab85ba0$602912e0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A7_01CE62C8.8E421600"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH89Zpm5dXVUh4MU7tK1R0BvtFGwgIOZAL/mLsOyDA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF BOF description
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 13:14:41 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00A7_01CE62C8.8E421600
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Perhaps we could modify the second paragraph, including some bullets for =
the
scenarios:

When a number of small-packet flows share the same path, bandwidth can =
be
saved by multiplexing packets belonging to different flows, adding a =
small
multiplexing delay as a counterpart. This delay has to be maintained =
under
some threshold in order to grant the delay requirements. Some examples =
of
the scenarios where grouping packets is possible are:

- aggregation networks of a network operator

- an end-to-end tunnel between appliances located in two different =
offices
of the same company

- a satellite connection used for collecting the data of a high number =
of
sensors.

=20

Do you like this?

=20

Jose

=20

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
Juli=E1n Fern=E1ndez-Navajas
Enviado el: jueves, 06 de junio de 2013 10:08
Para: tcmtf@ietf.org
Asunto: Re: [tcmtf] TCMTF BOF description

=20

Hi all,
I'd like to make a remark.
I feel that the charter is only oriented to network operator. Perhaps it =
is
good strengthen the idea that TCMTF is also beneficial for the =
development
of end-to-end aplications.=20
Juli=E1n


El 05/06/2013 13:17, Jose Saldana escribi=F3:

Hi,

=20

I have just built this BOF description for
<http://trac.tools.ietf.org/bof/trac/wiki>
http://trac.tools.ietf.org/bof/trac/wiki. It summarizes the draft =
charter:

=20

=20

Some emerging interactive services (VoIP, videoconferencing, =
telemedicine,
video vigilance, online gaming, etc.) use small packets in order to send
frequent updates to the other extreme of the communication. Therefore, =
its
overhead is significant. In addition, some other services also send =
small
packets, although they are not delay-sensitive (e.g., instant messaging, =
m2m
packets sending collected data in sensor networks using wireless or
satellite scenarios).

=20

When a number of small-packet flows share the same path, bandwidth can =
be
saved by multiplexing packets belonging to different flows, adding a =
small
multiplexing delay as a counterpart. This delay has to be maintained =
under
some threshold in order to grant the delay requirements. Some examples =
of
the scenarios where grouping packets is possible are: aggregation =
networks
of a network operator; a tunnel between two premises of the same =
company; a
satellite connection used for collecting the data of a high number of
sensors.

=20

RFC4170 <http://tools.ietf.org/html/rfc4170>  (TCRTP) defined a method =
for
grouping VoIP packets considering three different layers: header =
compression
by means of ECRTP; multiplexing by means of PPPMux; tunneling by means =
of
L2TPv3. However, in the last years, emerging real-time services which do =
not
use UDP/RTP have become popular: some of them use UDP or even TCP. In
addition, new header compression methods have been defined (ROHC). So =
there
is a need of widening the scope of RFC4170 in order to consider not only
UDP/RTP but also other protocols. The same structure of three layers =
will be
considered: header compression, multiplexing and tunneling.

=20

The BOF aims for 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 (TCMTF).=20

=20

=20

Do you like it?

=20

=20

Another thing: in the section Relevant I-Ds of the web page, the
=93recommendations=94 draft could also be included:

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

=20

=20

Best regards,

=20

Jose=20

=20






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

=20


------=_NextPart_000_00A7_01CE62C8.8E421600
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML con formato previo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:Consolas;
	color:black;}
span.HTMLconformatoprevioCar
	{mso-style-name:"HTML con formato previo Car";
	mso-style-priority:99;
	mso-style-link:"HTML con formato previo";
	font-family:Consolas;
	color:black;}
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 bgcolor=3Dwhite lang=3DES =
link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Perhaps we could modify the second paragraph, including some bullets =
for the scenarios:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'text-align:justify'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>When a number of small-packet flows share the same path, bandwidth =
can be saved by multiplexing packets belonging to different flows, =
adding a small multiplexing delay as a counterpart. This delay has to be =
maintained under some threshold in order to grant the delay =
requirements. Some examples of the scenarios where grouping packets is =
possible are:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'text-align:justify'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>- aggregation networks of a network operator<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'text-align:justify'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>- an end-to-end tunnel between appliances located in two different =
offices of the same company<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'text-align:justify'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>- a satellite connection used for collecting the data of a high =
number of sensors.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Do you like this?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jose<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'>De:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'> tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] <b>En =
nombre de </b>Juli=E1n Fern=E1ndez-Navajas<br><b>Enviado el:</b> jueves, =
06 de junio de 2013 10:08<br><b>Para:</b> =
tcmtf@ietf.org<br><b>Asunto:</b> Re: [tcmtf] TCMTF BOF =
description<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Hi =
all,<br>I'd like to make a remark.<br>I feel that the charter is only =
oriented to network operator. Perhaps it is good strengthen the idea =
that TCMTF is also beneficial for the development of end-to-end =
aplications. <br>Juli=E1n<br><br><br>El 05/06/2013 13:17, Jose Saldana =
escribi=F3:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi,<o:p></o:=
p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>I have just built this BOF description for </span><a =
href=3D"http://trac.tools.ietf.org/bof/trac/wiki"><span =
lang=3DEN-US>http://trac.tools.ietf.org/bof/trac/wiki</span></a><span =
lang=3DEN-US>. It summarizes the draft charter:</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US>Some emerging interactive services (VoIP, =
videoconferencing, telemedicine, video vigilance, online gaming, etc.) =
use small packets in order to send frequent updates to the other extreme =
of the communication. Therefore, its overhead is significant. In =
addition, some other services also send small packets, although they are =
not delay-sensitive (e.g., instant messaging, m2m packets sending =
collected data in sensor networks using wireless or satellite =
scenarios).</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US>When a number of small-packet flows share the same path, =
bandwidth can be saved by multiplexing packets belonging to different =
flows, adding a small multiplexing delay as a counterpart. This delay =
has to be maintained under some threshold in order to grant the delay =
requirements. Some examples of the scenarios where grouping packets is =
possible are: aggregation networks of a network operator; a tunnel =
between two premises of the same company; a satellite connection used =
for collecting the data of a high number of =
sensors.</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US><a href=3D"http://tools.ietf.org/html/rfc4170">RFC4170</a> =
(TCRTP) defined a method for grouping VoIP packets considering three =
different layers: header compression by means of ECRTP; multiplexing by =
means of PPPMux; tunneling by means of L2TPv3. However, in the last =
years, emerging real-time services which do not use UDP/RTP have become =
popular: some of them use UDP or even TCP. In addition, new header =
compression methods have been defined (ROHC). So there is a need of =
widening the scope of RFC4170 in order to consider not only UDP/RTP but =
also other protocols. The same structure of three layers will be =
considered: header compression, multiplexing and =
tunneling.</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US>The BOF aims for 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 (TCMTF). </span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>Do you like it?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>Another thing: in the section Relevant I-Ds of the web =
page, the &#8220;recommendations&#8221; draft could also be =
included:</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><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><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>Best regards,</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>Jose </span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-US>&nbsp;</span><o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><br><o:p></o:p></p><pre>_______________________=
________________________<o:p></o:p></pre><pre>tcmtf mailing =
list<o:p></o:p></pre><pre><a =
href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><o:p></o:p></pre><pre><a=
 =
href=3D"https://www.ietf.org/mailman/listinfo/tcmtf">https://www.ietf.org=
/mailman/listinfo/tcmtf</a><o:p></o:p></pre></blockquote><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_00A7_01CE62C8.8E421600--


From diego@tid.es  Thu Jun  6 06:15:40 2013
Return-Path: <diego@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D92F021F99D0 for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 06:15:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6CKCalS14YVy for <tcmtf@ietfa.amsl.com>; Thu,  6 Jun 2013 06:15:36 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 7217621F99D6 for <tcmtf@ietf.org>; Thu,  6 Jun 2013 06:15:34 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MNZ00H5W3HX5F@tid.hi.inet> for tcmtf@ietf.org; Thu, 06 Jun 2013 15:15:33 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 61.BE.05654.57B80B15; Thu, 06 Jun 2013 15:15:33 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MNZ00H5L3HW5F@tid.hi.inet> for tcmtf@ietf.org; Thu, 06 Jun 2013 15:15:33 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Thu, 06 Jun 2013 15:14:36 +0200
Date: Thu, 06 Jun 2013 13:15:21 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <00a501ce62b6$7e2cd3c0$7a867b40$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "<jsaldana@unizar.es>" <jsaldana@unizar.es>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A049CCD3A98@EX10-MB2-MAD.hi.inet>
Content-id: <367D9ECC7C12F64BA432B95B8C23DD89@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-2
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] TCMTF: Documents to be generated. Small modification
Thread-index: Ac5h2eb/R9lrIRTzTmSkhKAFyvT4WQAwM8mgAAAmDdAABErmAAABUBCA///n/4CAAALPAA==
X-AuditID: 0a5f4e69-b7f4b6d000001616-27-51b08b754055
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42Lhivcz1C3t3hBo0PuM22LX5w2MDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKWHyjnb1gYUFFW9NX5gbG9pguRk4OCQETiTVLTzFD2GISF+6t ZwOxhQS2M0q0bdDtYuQCsn8ySqy4cpcRwpnGKDGnZysLSBWLgKrE4b5PTCA2G5D9qPk3O4gt LOApcfPvS7A4p4CFxJ3GyYwQGxQk/px7DNYrIqAvceMxSD0XB7NAH6PE6//PwM7gFfCWeHnk MJjNLGAmcXLBO0aIuKDEj8n3gJo5gOI6El8nRUCUiEs0t95kgbC1JZ68u8AKYjMKyEq8mz+f FWKXl8TUT3/ZIewIiSPn97JA3CMgsWTPeajvRSVePv7HCvHkS0aJnn0XWCcwSsxCcsYsJGfM QjhjFpIzZiE5YwEj6ypGseKkosz0jJLcxMycdAMjvYxMvcy81JJNjJC4y9zBuHynyiFGAQ5G JR7eA77rA4VYE8uKK3MPMUpwMCuJ8L7p3BAoxJuSWFmVWpQfX1Sak1p8iJGJg1OqgfFgY0yU 5WQhx7/8OrZGUedubiv9HLj5n8WWW4Y92m/v6LqVFnR9r3j9KfwS4499Ue/lV9Q663dEVUXr P8+8n/ZF4puu84p3Tx8envXRRPznO5fSSYe28j7rcyp8v2jvoYvzrHesSW24K2nK9XfWU5ag 3zpe87v+GrOJnGZ4XHG291fnwZ2S2iZKLMUZiYZazEXFiQC0BN6fmQIAAA==
References: <E004A7C54DE04F4BB87DB9F32308DA5C0C0012@MAIL4.fer.hr> <F5EDC35DF914C1428C28E149F10463A29C8A2F7E@EX10-MB2-MAD.hi.inet> <E004A7C54DE04F4BB87DB9F32308DA5C0C0123@MAIL4.fer.hr> <00a501ce62b6$7e2cd3c0$7a867b40$@unizar.es>
Cc: "<tcmtf@ietf.org>" <tcmtf@ietf.org>, =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>, FERNANDO PASCUAL BLANCO <fpb@tid.es>
Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small modification
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2013 13:15:41 -0000

Hmmm... The necessary outcome of the negotiation is the setup. I'd keep the=
 shorter name.

Be goode,

On 6 Jun 2013, at 15:05 , Jose Saldana wrote:

> One question:
>
> The new second draft should include:
>
> - The negotiation
> - The setup/release a TCMTF tunnel between a mux and a demux
>
> Do you think "TCMTF - negotiation protocol" also includes the second idea=
?
>
> Would it be better "TCMTF - negotiation and setup" ?
>
> Thanks!
>
> Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Mirko Su=BEnjevic
>> Enviado el: jueves, 06 de junio de 2013 14:32
>> Para: FERNANDO PASCUAL BLANCO; tcmtf@ietf.org
>> Asunto: Re: [tcmtf] TCMTF: Documents to be generated. Small modification
>>
>> Yes i think that is better.
>> Mirko
>>
>> -----Original Message-----
>> From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>> Sent: Thursday, June 6, 2013 1:53 PM
>> To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org
>> Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small modificatio=
n
>>
>> And what about:
>>
>> TCMTF - negotiation protocol
>>
>> Do you found it more descriptive?
>>
>> Regards,
>>
>> Fernando Pascual Blanco
>> Telef=F3nica Global Resources
>> Network Automation and Dynamization
>> TECHNOLOGY PEOPLE GROUP
>> F +34913128779
>> M +34682005168
>> fpb@tid.es
>>
>>
>>
>>
>> On 06/06/13 11:51, "Mirko Su=BEnjevi=E6" <Mirko.Suznjevic@fer.hr> wrote:
>>
>>> Hello,
>>> I think these names are ok. Maybe we should discuss the second one in
>>> more detail.
>>> Perhaps include negotiation in the name of the draft so its purpose is
>>> evident from the title? As the purpose of that draft is to establish
>>> which particular parameters will be used.
>>> My suggestions are:
>>> TCMTF - negotiation signalling
>>> TCMTF - negotiation process
>>> TCMTF - parameter signalling
>>> Or something along those lines?
>>> Mirko
>>>
>>> -----Original Message-----
>>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf
>>> Of Jose Saldana
>>> Sent: Wednesday, June 5, 2013 12:56 PM
>>> To: tcmtf@ietf.org
>>> Cc: tsv-area@ietf.org; spencerdawkins.ietf@gmail.com; 'ken carlberg';
>>> Martin Stiemerling
>>> Subject: [tcmtf] TCMTF: Documents to be generated. Small modification
>>>
>>> In the conf-call of yesterday it was also clear that for the IETF it is
>>> better to split Document A into two documents:
>>>
>>> - The "TCMTF reference model" (1): the protocol stack and scenarios. It
>>> should be said that each protocol at each layer will use its own
>>> signaling mechanisms.
>>>
>>> - The "TCMTF-specific signaling": there are some things we will need to
>>> deploy:
>>>      - a negotiation mechanism (2) to decide the options to use at
>>> each layer (e.g. a mux and demux agree on using ROHC+PPPMux+GRE)
>>>      - a mechanism to setup/release a TCMTF tunnel (3)between a
>>> multiplexer and a de-multiplexer
>>>
>>>
>>> The current draft is the TCMTF "reference model", since it does not
>>> talk about specific signaling issues.
>>>
>>> By now, we don't have to propose the "TCMTF specific signaling". It
>>> would be something to be deployed if the Working Group is created.
>>>
>>> This same idea was proposed by Ken Carlberg in February. The advantages
>>> of this new distribution of the documents are (quoting Ken):
>>>
>>>> One thing to keep in mind is that it is possible that (2) and (3)
>>>> (below) can change over time and yet (1) (the reference model) does
>>>> not, then it may be best to separate (1) from the other items.
>>>
>>>> a more encompassing architecture or framework that would include
>>>> sample scenarios upon which your deliverables A & B are aimed at?  My
>>>> impression is that you may want to point the reader of documents A &
>>>> B to the same reference model, and instead of repeating the same
>>>> text, it may be helpful to separate this into a separate document.
>>>
>>>
>>> Once discussed, I would create a new charter proposal including these
>>> changes.
>>>
>>>
>>> Do you like these short names for the documents?
>>>
>>> - "TCMTF reference model".
>>> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>>>
>>> - "TCMTF-specific signaling". Future work
>>>
>>> - "TCMTF recommendations".
>>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>>>
>>>
>>> Your feedback will be welcome. Thanks!
>>>
>>> Jose
>>>
>>>> -----Mensaje original-----
>>>> De: ken carlberg [mailto:carlberg@g11.org.uk] Enviado el: martes, 05
>>>> de marzo de 2013 17:07
>>>> Para: jsaldana@unizar.es
>>>> CC: 'ken carlberg'; tcmtf@ietf.org; tsv-area@ietf.org
>>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about TCMTF
>>>> in
>>>> IETF87
>>>>
>>>> Hola Jose,
>>>>
>>>> Thanks for the expanded explanation, and again, apologies for the
>>>> tardy repsonse.  Its helpful to understand that document A and B are
>>>> sequential
>>> to
>>>> each other.  One thing to keep in mind is that if its possible that 2
>>>> and
>>> 3
>>>> (below) can change over time and yet 1 (the reference model) does
>>>> not, then it may be best to separate 1 from the other items.
>>>>
>>>> as for what you outline as a discussion point for future work, it
>>>> seems
>>> fine.  I
>>>> just have a personal bias that if you have a clear idea of the things
>>> you'd like
>>>> to accomplish in the future, then having a requirements document
>>>> would be helpful to focus those thoughts without having to have one
>>>> particular solution.  But that's a discussion point that could be
>>>> brought up during
>>> the
>>>> BoF, or sometime afterwards.
>>>>
>>>> cheers,
>>>>
>>>> -ken
>>>>
>>>>
>>>>> A main document (A) in which we explain the method, the scenarios
>>>>> and the minimum signaling issues in order to make it work. The idea
>>>>> is that document
>>>>> (A) would be self-contained. Since we are not defining new
>>>>> protocols
>>> (i.e.
>>>>> already existing compressing, multiplexing and tunneling protocols
>>>>> are to be used), we understand that this can be done in a single
>>>> document.
>>>>> It would
>>>>> include:
>>>>>
>>>>> 1- Protocol stack (it would be the "reference model")
>>>>> 2- a negotiation mechanism to decide the options to use at each
>>>>> layer
>>>>> 3- a mechanism to setup/release a tunnel between a multiplexer and
>>>>> a de-multiplexer
>>>>>
>>>>> Of course, another approach could be separating 1 from 2&3.
>>>>> However, we think this is not necessary since the method is not too
>>>> complicated.
>>>>>
>>>>>
>>>>> Document (B) would only contain recommendations of how to better
>>>>> use the method proposed in document (A), i.e., classification and
>>>>> maximum
>>>> delays.
>>>>>
>>>>> So clearly document (B) would totally depend on the reference model
>>>>> of document (A).
>>>>>
>>>>>
>>>>> The idea of point 9 is to talk about some other interesting ideas
>>>>> which are considered as "future work":
>>>>> - a mechanism for a multiplexer to discover a de-multiplexer
>>>>> - mechanism to select an optimal multiplexer and a de-multiplexer
>>>>> when there are more than one muxer/de-muxer for a flow
>>>>> - dynamically applying TCMTF
>>>>> - etc.
>>>>>
>>>>> What do you think?
>>>>>
>>>>> Thanks again for your feedback. Thinking and explaining things is
>>>>> always a good exercise!
>>>>>
>>>>> Jose
>>>>>
>>>>>> -----Mensaje original-----
>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>>>>>> nombre de ken carlberg Enviado el: mi=E9rcoles, 27 de febrero de
>>>>>> 2013
>>>>>> 16:23
>>>>>> Para: jsaldana@unizar.es
>>>>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
>>>>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about
>>>>>> TCMTF in
>>>>>> IETF87
>>>>>>
>>>>>> Hola Jose,
>>>>>>
>>>>>> sorry for the tardy reply.  The altered text below is helpful,
>>>> thanks.
>>>>>>
>>>>>> With respect to your candidate deliverables, it appears that you
>>>>>> have
>>>>> listed
>>>>>> two for the proposed group: (A) a document that describes options
>>>>>> and negotiation mechanisms, and (B) a document describing
>>>> recommendations
>>>>>> of which packet types should be multiplexed and a list fo traffic
>>>>> classification
>>>>>> methods.  Have you considered a third document that presents a
>>>>>> more encompassing architecture or framework that would include
>>>>>> sample scenarios upon which your deliverables A & B are aimed at?
>>>>>> My impression
>>>>> is
>>>>>> that you may want to point the reader of documents A & B to the
>>>>>> same reference model, and instead of repeating the same text, it
>>>>>> may be helpful to separate this into a separate document.
>>>>>>
>>>>>> Also, would section 9 of your proposed charter lead one to
>>>>>> consider a requirements document?  Many times, new groups start
>>>>>> with a requirements document, but since you have a good focus of
>>>>>> what you want to accomplish, perhaps your last deliverable could
>>>>>> be a requirements document that would guide any future work.
>>>>>>
>>>>>> -ken
>>>>>>
>>>>>> ps, I don't want to advocate more work, but rather just have you
>>>>>> consider other possibilities (and feel free to shoot them down :-)
>>>>>>
>>>>>>
>>>>>> On Feb 22, 2013, at 5:39 AM, Jose Saldana <jsaldana@unizar.es>
>> wrote:
>>>>>>
>>>>>>> Hi Ken,
>>>>>>>
>>>>>>> Sorry for the delay. I think you are talking about Paragraph 5:
>>>>>>>
>>>>>>> 5. So the first objective of this group is to specify the
>>>>>>> protocol stack for tunneling, compressing and multiplexing
>>>>>>> traffic flows (TCMTF). Since standard protocols are being used at
>>>>>>> each layer, the signaling methods of those protocols will be used.
>>>>>>> Interactions with the Working Groups and Areas in which these
>>>>>>> protocols are developed can be expected. However, the
>> development
>>>>>>> of new compressing, multiplexing or tunneling protocols is not an
>>>>>>> objective of this Working Group. In addition, since the current
>>>>>>> RFC 4170 would be
>>>>>> considered as one of the options, this RFC could be obsoleted.
>>>>>>>
>>>>>>> Perhaps this is a bit confusing. When we say "at each layer", we
>>>>>>> are talking about "tunneling, compressing and multiplexing" layers.
>>>>>>> Perhaps this can be a bit confusing. What about this?:
>>>>>>>
>>>>>>> 5. So the first objective of this group is to specify the
>>>>>>> protocol stack for tunneling, compressing and multiplexing
>>>>>>> traffic flows (TCMTF). Since standard protocols are being used
>>>>>>> for tunneling, compressing and multiplexing layers, the signaling
>>>>>>> methods of those
>>>>>> protocols will be used.
>>>>>>> Interactions with the Working Groups and Areas in which these
>>>>>>> protocols are developed can be expected. However, the
>> development
>>>> of
>>>>>>> new compressing, multiplexing or tunneling protocols is not an
>>>>>>> objective of this Working Group. In addition, since the current
>>>>>>> RFC
>>>>>>> 4170 would be considered as one of the options, this RFC could be
>>>>>> obsoleted.
>>>>>>>
>>>>>>> Is this what you were asking?
>>>>>>>
>>>>>>> Thanks for your feedback.
>>>>>>>
>>>>>>> Jose
>>>>>>>
>>>>>>>> -----Mensaje original-----
>>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>>>>>>>> nombre de ken carlberg Enviado el: martes, 19 de febrero de 2013
>>>>>>>> 14:17
>>>>>>>> Para: jsaldana@unizar.es
>>>>>>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
>>>>>>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about
>>>>>>>> TCMTF in
>>>>>>>> IETF87
>>>>>>>>
>>>>>>>> Hola Jose,
>>>>>>>>
>>>>>>>> could you expand a bit more on your text in the proposed charter
>>>>>>>> regarding "signaling methods".  Are you speaking in the more
>>>>>>>> general context of information stored in headers of various
>>>>>>>> protocol up and down the stack
>>>>>>> (ie,
>>>>>>>> layers 3, 4, and 5/app)?  Or, are you  speaking of concurrent
>>>>>>>> resource signaling protocols like RSVP/RSVP-TE, or path
>>>>>>>> establishment protocols
>>>>>>> like
>>>>>>>> MPLS?  Or, some combination of both?
>>>>>>>>
>>>>>>>> -ken
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> tcmtf mailing list
>>>>>>>> tcmtf@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> tcmtf mailing list
>>>>>> tcmtf@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>>>
>>>
>>>
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>
>>
>> ________________________________
>>
>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>> 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


--
"Esta vez no fallaremos, Doctor Infierno"

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

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


________________________________

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

From jsaldana@unizar.es  Fri Jun  7 00:37:35 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4F8F21F9310 for <tcmtf@ietfa.amsl.com>; Fri,  7 Jun 2013 00:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17zEDX5ES758 for <tcmtf@ietfa.amsl.com>; Fri,  7 Jun 2013 00:37:30 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8689121F9248 for <tcmtf@ietf.org>; Fri,  7 Jun 2013 00:37:29 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r577bNQi031185; Fri, 7 Jun 2013 09:37:23 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Diego R. Lopez'" <diego@tid.es>, "=?iso-8859-2?Q?'Mirko_Su=BEnjevi=E6'?=" <Mirko.Suznjevic@fer.hr>, "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>
References: <E004A7C54DE04F4BB87DB9F32308DA5C0C0012@MAIL4.fer.hr>	<F5EDC35DF914C1428C28E149F10463A29C8A2F7E@EX10-MB2-MAD.hi.inet>	<E004A7C54DE04F4BB87DB9F32308DA5C0C0123@MAIL4.fer.hr>	<00a501ce62b6$7e2cd3c0$7a867b40$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CCD3A98@EX10-MB2-MAD.hi.inet>
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A049CCD3A98@EX10-MB2-MAD.hi.inet>
Date: Fri, 7 Jun 2013 09:37:26 +0200
Organization: Universidad de Zaragoza
Message-ID: <001b01ce6351$dbd4a4d0$937dee70$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Content-Language: es
Thread-Index: AQIvoD89gWUXtE92F4lsPmTNp5lNyQFP/SVlAfcfpwMCSN/+GwGNf6mImC50D+A=
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small modification
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2013 07:37:36 -0000

Ok then.

We can use these document names in the new version of the Charter (I =
will
try to rewrite it by Tuesday):

- TCMTF - reference model:
	the protocol stack and scenarios. It should be said that each
protocol at each layer will use its own signaling mechanisms.
	https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/


- TCMTF - negotiation protocol:
	- a mechanism to setup/release a TCMTF tunnel between a multiplexer
and a de-multiplexer, including the negotiation mechanism to decide the
options to use at each layer
=09

- TCMTF - recommendations:=20
	useful recommendations in order to decide which packet flows can or
can not be multiplexed and how. 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.
	http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/


Any comments?

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Diego R. Lopez
> Enviado el: jueves, 06 de junio de 2013 15:15
> Para: <jsaldana@unizar.es>
> CC: <tcmtf@ietf.org>; Mirko Su=BEnjevi=E6; FERNANDO PASCUAL BLANCO
> Asunto: Re: [tcmtf] TCMTF: Documents to be generated. Small =
modification
>=20
> Hmmm... The necessary outcome of the negotiation is the setup. I'd =
keep
> the shorter name.
>=20
> Be goode,
>=20
> On 6 Jun 2013, at 15:05 , Jose Saldana wrote:
>=20
> > One question:
> >
> > The new second draft should include:
> >
> > - The negotiation
> > - The setup/release a TCMTF tunnel between a mux and a demux
> >
> > Do you think "TCMTF - negotiation protocol" also includes the second
idea?
> >
> > Would it be better "TCMTF - negotiation and setup" ?
> >
> > Thanks!
> >
> > Jose
> >
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> >> de Mirko Su=BEnjevic Enviado el: jueves, 06 de junio de 2013 14:32
> >> Para: FERNANDO PASCUAL BLANCO; tcmtf@ietf.org
> >> Asunto: Re: [tcmtf] TCMTF: Documents to be generated. Small
> >> modification
> >>
> >> Yes i think that is better.
> >> Mirko
> >>
> >> -----Original Message-----
> >> From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> >> Sent: Thursday, June 6, 2013 1:53 PM
> >> To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org
> >> Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small
> >> modification
> >>
> >> And what about:
> >>
> >> TCMTF - negotiation protocol
> >>
> >> Do you found it more descriptive?
> >>
> >> Regards,
> >>
> >> Fernando Pascual Blanco
> >> Telef=F3nica Global Resources
> >> Network Automation and Dynamization
> >> TECHNOLOGY PEOPLE GROUP
> >> F +34913128779
> >> M +34682005168
> >> fpb@tid.es
> >>
> >>
> >>
> >>
> >> On 06/06/13 11:51, "Mirko Su=BEnjevi=E6" <Mirko.Suznjevic@fer.hr> =
wrote:
> >>
> >>> Hello,
> >>> I think these names are ok. Maybe we should discuss the second one
> >>> in more detail.
> >>> Perhaps include negotiation in the name of the draft so its =
purpose
> >>> is evident from the title? As the purpose of that draft is to
> >>> establish which particular parameters will be used.
> >>> My suggestions are:
> >>> TCMTF - negotiation signalling
> >>> TCMTF - negotiation process
> >>> TCMTF - parameter signalling
> >>> Or something along those lines?
> >>> Mirko
> >>>
> >>> -----Original Message-----
> >>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
> >>> Behalf Of Jose Saldana
> >>> Sent: Wednesday, June 5, 2013 12:56 PM
> >>> To: tcmtf@ietf.org
> >>> Cc: tsv-area@ietf.org; spencerdawkins.ietf@gmail.com; 'ken
> >>> carlberg'; Martin Stiemerling
> >>> Subject: [tcmtf] TCMTF: Documents to be generated. Small
> >>> modification
> >>>
> >>> In the conf-call of yesterday it was also clear that for the IETF =
it
> >>> is better to split Document A into two documents:
> >>>
> >>> - The "TCMTF reference model" (1): the protocol stack and =
scenarios.
> >>> It should be said that each protocol at each layer will use its =
own
> >>> signaling mechanisms.
> >>>
> >>> - The "TCMTF-specific signaling": there are some things we will =
need
> >>> to
> >>> deploy:
> >>>      - a negotiation mechanism (2) to decide the options to use at
> >>> each layer (e.g. a mux and demux agree on using ROHC+PPPMux+GRE)
> >>>      - a mechanism to setup/release a TCMTF tunnel (3)between a
> >>> multiplexer and a de-multiplexer
> >>>
> >>>
> >>> The current draft is the TCMTF "reference model", since it does =
not
> >>> talk about specific signaling issues.
> >>>
> >>> By now, we don't have to propose the "TCMTF specific signaling". =
It
> >>> would be something to be deployed if the Working Group is created.
> >>>
> >>> This same idea was proposed by Ken Carlberg in February. The
> >>> advantages of this new distribution of the documents are (quoting
Ken):
> >>>
> >>>> One thing to keep in mind is that it is possible that (2) and (3)
> >>>> (below) can change over time and yet (1) (the reference model) =
does
> >>>> not, then it may be best to separate (1) from the other items.
> >>>
> >>>> a more encompassing architecture or framework that would include
> >>>> sample scenarios upon which your deliverables A & B are aimed at?
> >>>> My impression is that you may want to point the reader of =
documents
> >>>> A & B to the same reference model, and instead of repeating the
> >>>> same text, it may be helpful to separate this into a separate
document.
> >>>
> >>>
> >>> Once discussed, I would create a new charter proposal including
> >>> these changes.
> >>>
> >>>
> >>> Do you like these short names for the documents?
> >>>
> >>> - "TCMTF reference model".
> >>> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
> >>>
> >>> - "TCMTF-specific signaling". Future work
> >>>
> >>> - "TCMTF recommendations".
> >>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
> >>>
> >>>
> >>> Your feedback will be welcome. Thanks!
> >>>
> >>> Jose
> >>>
> >>>> -----Mensaje original-----
> >>>> De: ken carlberg [mailto:carlberg@g11.org.uk] Enviado el: martes,
> >>>> 05 de marzo de 2013 17:07
> >>>> Para: jsaldana@unizar.es
> >>>> CC: 'ken carlberg'; tcmtf@ietf.org; tsv-area@ietf.org
> >>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about
> >>>> TCMTF in
> >>>> IETF87
> >>>>
> >>>> Hola Jose,
> >>>>
> >>>> Thanks for the expanded explanation, and again, apologies for the
> >>>> tardy repsonse.  Its helpful to understand that document A and B
> >>>> are sequential
> >>> to
> >>>> each other.  One thing to keep in mind is that if its possible =
that
> >>>> 2 and
> >>> 3
> >>>> (below) can change over time and yet 1 (the reference model) does
> >>>> not, then it may be best to separate 1 from the other items.
> >>>>
> >>>> as for what you outline as a discussion point for future work, it
> >>>> seems
> >>> fine.  I
> >>>> just have a personal bias that if you have a clear idea of the
> >>>> things
> >>> you'd like
> >>>> to accomplish in the future, then having a requirements document
> >>>> would be helpful to focus those thoughts without having to have =
one
> >>>> particular solution.  But that's a discussion point that could be
> >>>> brought up during
> >>> the
> >>>> BoF, or sometime afterwards.
> >>>>
> >>>> cheers,
> >>>>
> >>>> -ken
> >>>>
> >>>>
> >>>>> A main document (A) in which we explain the method, the =
scenarios
> >>>>> and the minimum signaling issues in order to make it work. The
> >>>>> idea is that document
> >>>>> (A) would be self-contained. Since we are not defining new
> >>>>> protocols
> >>> (i.e.
> >>>>> already existing compressing, multiplexing and tunneling =
protocols
> >>>>> are to be used), we understand that this can be done in a single
> >>>> document.
> >>>>> It would
> >>>>> include:
> >>>>>
> >>>>> 1- Protocol stack (it would be the "reference model")
> >>>>> 2- a negotiation mechanism to decide the options to use at each
> >>>>> layer
> >>>>> 3- a mechanism to setup/release a tunnel between a multiplexer =
and
> >>>>> a de-multiplexer
> >>>>>
> >>>>> Of course, another approach could be separating 1 from 2&3.
> >>>>> However, we think this is not necessary since the method is not
> >>>>> too
> >>>> complicated.
> >>>>>
> >>>>>
> >>>>> Document (B) would only contain recommendations of how to better
> >>>>> use the method proposed in document (A), i.e., classification =
and
> >>>>> maximum
> >>>> delays.
> >>>>>
> >>>>> So clearly document (B) would totally depend on the reference
> >>>>> model of document (A).
> >>>>>
> >>>>>
> >>>>> The idea of point 9 is to talk about some other interesting =
ideas
> >>>>> which are considered as "future work":
> >>>>> - a mechanism for a multiplexer to discover a de-multiplexer
> >>>>> - mechanism to select an optimal multiplexer and a =
de-multiplexer
> >>>>> when there are more than one muxer/de-muxer for a flow
> >>>>> - dynamically applying TCMTF
> >>>>> - etc.
> >>>>>
> >>>>> What do you think?
> >>>>>
> >>>>> Thanks again for your feedback. Thinking and explaining things =
is
> >>>>> always a good exercise!
> >>>>>
> >>>>> Jose
> >>>>>
> >>>>>> -----Mensaje original-----
> >>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >>>>>> nombre de ken carlberg Enviado el: mi=E9rcoles, 27 de febrero =
de
> >>>>>> 2013
> >>>>>> 16:23
> >>>>>> Para: jsaldana@unizar.es
> >>>>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
> >>>>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about
> >>>>>> TCMTF in
> >>>>>> IETF87
> >>>>>>
> >>>>>> Hola Jose,
> >>>>>>
> >>>>>> sorry for the tardy reply.  The altered text below is helpful,
> >>>> thanks.
> >>>>>>
> >>>>>> With respect to your candidate deliverables, it appears that =
you
> >>>>>> have
> >>>>> listed
> >>>>>> two for the proposed group: (A) a document that describes =
options
> >>>>>> and negotiation mechanisms, and (B) a document describing
> >>>> recommendations
> >>>>>> of which packet types should be multiplexed and a list fo =
traffic
> >>>>> classification
> >>>>>> methods.  Have you considered a third document that presents a
> >>>>>> more encompassing architecture or framework that would include
> >>>>>> sample scenarios upon which your deliverables A & B are aimed =
at?
> >>>>>> My impression
> >>>>> is
> >>>>>> that you may want to point the reader of documents A & B to the
> >>>>>> same reference model, and instead of repeating the same text, =
it
> >>>>>> may be helpful to separate this into a separate document.
> >>>>>>
> >>>>>> Also, would section 9 of your proposed charter lead one to
> >>>>>> consider a requirements document?  Many times, new groups start
> >>>>>> with a requirements document, but since you have a good focus =
of
> >>>>>> what you want to accomplish, perhaps your last deliverable =
could
> >>>>>> be a requirements document that would guide any future work.
> >>>>>>
> >>>>>> -ken
> >>>>>>
> >>>>>> ps, I don't want to advocate more work, but rather just have =
you
> >>>>>> consider other possibilities (and feel free to shoot them down
> >>>>>> :-)
> >>>>>>
> >>>>>>
> >>>>>> On Feb 22, 2013, at 5:39 AM, Jose Saldana <jsaldana@unizar.es>
> >> wrote:
> >>>>>>
> >>>>>>> Hi Ken,
> >>>>>>>
> >>>>>>> Sorry for the delay. I think you are talking about Paragraph =
5:
> >>>>>>>
> >>>>>>> 5. So the first objective of this group is to specify the
> >>>>>>> protocol stack for tunneling, compressing and multiplexing
> >>>>>>> traffic flows (TCMTF). Since standard protocols are being used
> >>>>>>> at each layer, the signaling methods of those protocols will =
be
used.
> >>>>>>> Interactions with the Working Groups and Areas in which these
> >>>>>>> protocols are developed can be expected. However, the
> >> development
> >>>>>>> of new compressing, multiplexing or tunneling protocols is not
> >>>>>>> an objective of this Working Group. In addition, since the
> >>>>>>> current RFC 4170 would be
> >>>>>> considered as one of the options, this RFC could be obsoleted.
> >>>>>>>
> >>>>>>> Perhaps this is a bit confusing. When we say "at each layer", =
we
> >>>>>>> are talking about "tunneling, compressing and multiplexing"
layers.
> >>>>>>> Perhaps this can be a bit confusing. What about this?:
> >>>>>>>
> >>>>>>> 5. So the first objective of this group is to specify the
> >>>>>>> protocol stack for tunneling, compressing and multiplexing
> >>>>>>> traffic flows (TCMTF). Since standard protocols are being used
> >>>>>>> for tunneling, compressing and multiplexing layers, the
> >>>>>>> signaling methods of those
> >>>>>> protocols will be used.
> >>>>>>> Interactions with the Working Groups and Areas in which these
> >>>>>>> protocols are developed can be expected. However, the
> >> development
> >>>> of
> >>>>>>> new compressing, multiplexing or tunneling protocols is not an
> >>>>>>> objective of this Working Group. In addition, since the =
current
> >>>>>>> RFC
> >>>>>>> 4170 would be considered as one of the options, this RFC could
> >>>>>>> be
> >>>>>> obsoleted.
> >>>>>>>
> >>>>>>> Is this what you were asking?
> >>>>>>>
> >>>>>>> Thanks for your feedback.
> >>>>>>>
> >>>>>>> Jose
> >>>>>>>
> >>>>>>>> -----Mensaje original-----
> >>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >>>>>>>> nombre de ken carlberg Enviado el: martes, 19 de febrero de
> >>>>>>>> 2013
> >>>>>>>> 14:17
> >>>>>>>> Para: jsaldana@unizar.es
> >>>>>>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
> >>>>>>>> Asunto: Re: [tcmtf] About the possibility of having a BOF =
about
> >>>>>>>> TCMTF in
> >>>>>>>> IETF87
> >>>>>>>>
> >>>>>>>> Hola Jose,
> >>>>>>>>
> >>>>>>>> could you expand a bit more on your text in the proposed
> >>>>>>>> charter regarding "signaling methods".  Are you speaking in =
the
> >>>>>>>> more general context of information stored in headers of
> >>>>>>>> various protocol up and down the stack
> >>>>>>> (ie,
> >>>>>>>> layers 3, 4, and 5/app)?  Or, are you  speaking of concurrent
> >>>>>>>> resource signaling protocols like RSVP/RSVP-TE, or path
> >>>>>>>> establishment protocols
> >>>>>>> like
> >>>>>>>> MPLS?  Or, some combination of both?
> >>>>>>>>
> >>>>>>>> -ken
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> tcmtf mailing list
> >>>>>>>> tcmtf@ietf.org
> >>>>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> tcmtf mailing list
> >>>>>> tcmtf@ietf.org
> >>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> tcmtf mailing list
> >>> tcmtf@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>> _______________________________________________
> >>> tcmtf mailing list
> >>> tcmtf@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>
> >>
> >> ________________________________
> >>
> >> Este mensaje se dirige exclusivamente a su destinatario. Puede
> >> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico
> >> en el enlace situado m=E1s abajo.
> >> This message is intended exclusively for its addressee. We only =
send
> >> and receive email on the basis of the terms set out at:
> >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >> _______________________________________________
> >> tcmtf mailing list
> >> tcmtf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >
> > _______________________________________________
> > tcmtf mailing list
> > tcmtf@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcmtf
>=20
>=20
> --
> "Esta vez no fallaremos, Doctor Infierno"
>=20
> Dr Diego R. Lopez
> Telefonica I+D
> http://people.tid.es/diego.lopez/
>=20
> e-mail: diego@tid.es
> Tel:    +34 913 129 041
> Mobile: +34 682 051 091
> -----------------------------------------
>=20
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar
> nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en =
el enlace
> situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send =
and
> receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From fpb@tid.es  Fri Jun  7 00:56:20 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF7D721F91BF for <tcmtf@ietfa.amsl.com>; Fri,  7 Jun 2013 00:56:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q6uoLmXLLcdW for <tcmtf@ietfa.amsl.com>; Fri,  7 Jun 2013 00:56:15 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id C948021F9285 for <tcmtf@ietf.org>; Fri,  7 Jun 2013 00:56:13 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MO0009XBJDM2R@tid.hi.inet> for tcmtf@ietf.org; Fri, 07 Jun 2013 09:56:10 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 3E.5E.05654.A1291B15; Fri, 07 Jun 2013 09:56:10 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MO0009X6JDL2R@tid.hi.inet> for tcmtf@ietf.org; Fri, 07 Jun 2013 09:56:10 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS6-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Fri, 07 Jun 2013 09:56:07 +0200
Date: Fri, 07 Jun 2013 07:56:06 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <001b01ce6351$dbd4a4d0$937dee70$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "Diego R. Lopez" <diego@tid.es>, =?iso-8859-2?Q?=27Mirko_Su=BEnjevi=E6=27?= <Mirko.Suznjevic@fer.hr>
Message-id: <F5EDC35DF914C1428C28E149F10463A29C8A3442@EX10-MB2-MAD.hi.inet>
Content-id: <98A70CB9A0266E488BF8AC004D4A9785@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-2
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] TCMTF: Documents to be generated. Small modification
Thread-index: Ac5h2eb/R9lrIRTzTmSkhKAFyvT4WQAwM8mgAAAmDdAABErmAAABUBCA///n/4CAAALPAIABM+wAgAAmvYA=
user-agent: Microsoft-MacOutlook/14.3.2.130206
X-AuditID: 0a5f4e69-b7f4b6d000001616-22-51b1921a7782
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42Lhivcz1JWatDHQYOY+SYtdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoEro33ReZaC2f2MFTsfvmduYHxX3MXIySEhYCLx6EknC4QtJnHh 3nq2LkYuDiGB7YwSWz4cZoZwfjJKfD74C8qZxiix98g1ZpAWFgFViYtf5rOC2GwCWhKn764C GyUs4Clx8+9LJhCbU8BC4mzzBkaIFQoSf849ZgEZJCIwlVFi28xDQAkODmagQfO+KYLU8Ap4 S0yY08UGYjMLmElcmbKJESIuKPFj8j0WiHIdia+TIiBKxCWaW2+yQNjaEk/eXQA7h1FAVuLd fIjTRAS8JKZ++ssOYadIrLh1G2ykqICexM0zLawQpwlILNlznhnCFpV4+fgf6wRGiVlIrpiF 5IpZCFfMQnLFLCRXLGBkXcUoVpxUlJmeUZKbmJmTbmCkl5Gpl5mXWrKJERJ3mTsYl+9UOcQo wMGoxMP7Y9WGQCHWxLLiytxDjBIczEoivOvTNgYK8aYkVlalFuXHF5XmpBYfYmTi4JRqYCzz ig35dMi4pT10aVtD1oOHKzfdvt1RxxqlJHnze40qS1r1jLZzV1hUVGJnJ/x9u/bh0rXaV9fO kH4WvGGp4m3nhLems8+ynyk6wh3Gd+STWty069Le22UVL2YGVe7W7nAv4vz28jrHhq8a1o4z n8cnJd64M2Enc9WTPzO11e4v2mZ9cdsvPXklluKMREMt5qLiRAAbnfdlmQIAAA==
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small modification
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2013 07:56:21 -0000

Hi Jose,

        I have doubts about the description of the second document, why are=
 you
focusing the description on the tunneling layer? I understand that there
will be two options: a dialog (protocol) to negotiate every option at each
layer or three dialogs to negotiate each layer, but in that case the
tunnel layer will not be different from others. What do you think about a
description less tunnel oriented?

Regards,

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




On 07/06/13 09:37, "Jose Saldana" <jsaldana@unizar.es> wrote:

>Ok then.
>
>We can use these document names in the new version of the Charter (I will
>try to rewrite it by Tuesday):
>
>- TCMTF - reference model:
>       the protocol stack and scenarios. It should be said that each
>protocol at each layer will use its own signaling mechanisms.
>       https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>
>
>- TCMTF - negotiation protocol:
>       - a mechanism to setup/release a TCMTF tunnel between a multiplexer
>and a de-multiplexer, including the negotiation mechanism to decide the
>options to use at each layer
>
>
>- TCMTF - recommendations:
>       useful recommendations in order to decide which packet flows can or
>can not be multiplexed and how. 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.
>       http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>
>
>Any comments?
>
>Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Diego R. Lopez
>> Enviado el: jueves, 06 de junio de 2013 15:15
>> Para: <jsaldana@unizar.es>
>> CC: <tcmtf@ietf.org>; Mirko Su=BEnjevi=E6; FERNANDO PASCUAL BLANCO
>> Asunto: Re: [tcmtf] TCMTF: Documents to be generated. Small modification
>>
>> Hmmm... The necessary outcome of the negotiation is the setup. I'd keep
>> the shorter name.
>>
>> Be goode,
>>
>> On 6 Jun 2013, at 15:05 , Jose Saldana wrote:
>>
>> > One question:
>> >
>> > The new second draft should include:
>> >
>> > - The negotiation
>> > - The setup/release a TCMTF tunnel between a mux and a demux
>> >
>> > Do you think "TCMTF - negotiation protocol" also includes the second
>idea?
>> >
>> > Would it be better "TCMTF - negotiation and setup" ?
>> >
>> > Thanks!
>> >
>> > Jose
>> >
>> >> -----Mensaje original-----
>> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>> >> de Mirko Su=BEnjevic Enviado el: jueves, 06 de junio de 2013 14:32
>> >> Para: FERNANDO PASCUAL BLANCO; tcmtf@ietf.org
>> >> Asunto: Re: [tcmtf] TCMTF: Documents to be generated. Small
>> >> modification
>> >>
>> >> Yes i think that is better.
>> >> Mirko
>> >>
>> >> -----Original Message-----
>> >> From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>> >> Sent: Thursday, June 6, 2013 1:53 PM
>> >> To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org
>> >> Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small
>> >> modification
>> >>
>> >> And what about:
>> >>
>> >> TCMTF - negotiation protocol
>> >>
>> >> Do you found it more descriptive?
>> >>
>> >> Regards,
>> >>
>> >> Fernando Pascual Blanco
>> >> Telef=F3nica Global Resources
>> >> Network Automation and Dynamization
>> >> TECHNOLOGY PEOPLE GROUP
>> >> F +34913128779
>> >> M +34682005168
>> >> fpb@tid.es
>> >>
>> >>
>> >>
>> >>
>> >> On 06/06/13 11:51, "Mirko Su=BEnjevi=E6" <Mirko.Suznjevic@fer.hr> wro=
te:
>> >>
>> >>> Hello,
>> >>> I think these names are ok. Maybe we should discuss the second one
>> >>> in more detail.
>> >>> Perhaps include negotiation in the name of the draft so its purpose
>> >>> is evident from the title? As the purpose of that draft is to
>> >>> establish which particular parameters will be used.
>> >>> My suggestions are:
>> >>> TCMTF - negotiation signalling
>> >>> TCMTF - negotiation process
>> >>> TCMTF - parameter signalling
>> >>> Or something along those lines?
>> >>> Mirko
>> >>>
>> >>> -----Original Message-----
>> >>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
>> >>> Behalf Of Jose Saldana
>> >>> Sent: Wednesday, June 5, 2013 12:56 PM
>> >>> To: tcmtf@ietf.org
>> >>> Cc: tsv-area@ietf.org; spencerdawkins.ietf@gmail.com; 'ken
>> >>> carlberg'; Martin Stiemerling
>> >>> Subject: [tcmtf] TCMTF: Documents to be generated. Small
>> >>> modification
>> >>>
>> >>> In the conf-call of yesterday it was also clear that for the IETF it
>> >>> is better to split Document A into two documents:
>> >>>
>> >>> - The "TCMTF reference model" (1): the protocol stack and scenarios.
>> >>> It should be said that each protocol at each layer will use its own
>> >>> signaling mechanisms.
>> >>>
>> >>> - The "TCMTF-specific signaling": there are some things we will need
>> >>> to
>> >>> deploy:
>> >>>      - a negotiation mechanism (2) to decide the options to use at
>> >>> each layer (e.g. a mux and demux agree on using ROHC+PPPMux+GRE)
>> >>>      - a mechanism to setup/release a TCMTF tunnel (3)between a
>> >>> multiplexer and a de-multiplexer
>> >>>
>> >>>
>> >>> The current draft is the TCMTF "reference model", since it does not
>> >>> talk about specific signaling issues.
>> >>>
>> >>> By now, we don't have to propose the "TCMTF specific signaling". It
>> >>> would be something to be deployed if the Working Group is created.
>> >>>
>> >>> This same idea was proposed by Ken Carlberg in February. The
>> >>> advantages of this new distribution of the documents are (quoting
>Ken):
>> >>>
>> >>>> One thing to keep in mind is that it is possible that (2) and (3)
>> >>>> (below) can change over time and yet (1) (the reference model) does
>> >>>> not, then it may be best to separate (1) from the other items.
>> >>>
>> >>>> a more encompassing architecture or framework that would include
>> >>>> sample scenarios upon which your deliverables A & B are aimed at?
>> >>>> My impression is that you may want to point the reader of documents
>> >>>> A & B to the same reference model, and instead of repeating the
>> >>>> same text, it may be helpful to separate this into a separate
>document.
>> >>>
>> >>>
>> >>> Once discussed, I would create a new charter proposal including
>> >>> these changes.
>> >>>
>> >>>
>> >>> Do you like these short names for the documents?
>> >>>
>> >>> - "TCMTF reference model".
>> >>> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>> >>>
>> >>> - "TCMTF-specific signaling". Future work
>> >>>
>> >>> - "TCMTF recommendations".
>> >>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>> >>>
>> >>>
>> >>> Your feedback will be welcome. Thanks!
>> >>>
>> >>> Jose
>> >>>
>> >>>> -----Mensaje original-----
>> >>>> De: ken carlberg [mailto:carlberg@g11.org.uk] Enviado el: martes,
>> >>>> 05 de marzo de 2013 17:07
>> >>>> Para: jsaldana@unizar.es
>> >>>> CC: 'ken carlberg'; tcmtf@ietf.org; tsv-area@ietf.org
>> >>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about
>> >>>> TCMTF in
>> >>>> IETF87
>> >>>>
>> >>>> Hola Jose,
>> >>>>
>> >>>> Thanks for the expanded explanation, and again, apologies for the
>> >>>> tardy repsonse.  Its helpful to understand that document A and B
>> >>>> are sequential
>> >>> to
>> >>>> each other.  One thing to keep in mind is that if its possible that
>> >>>> 2 and
>> >>> 3
>> >>>> (below) can change over time and yet 1 (the reference model) does
>> >>>> not, then it may be best to separate 1 from the other items.
>> >>>>
>> >>>> as for what you outline as a discussion point for future work, it
>> >>>> seems
>> >>> fine.  I
>> >>>> just have a personal bias that if you have a clear idea of the
>> >>>> things
>> >>> you'd like
>> >>>> to accomplish in the future, then having a requirements document
>> >>>> would be helpful to focus those thoughts without having to have one
>> >>>> particular solution.  But that's a discussion point that could be
>> >>>> brought up during
>> >>> the
>> >>>> BoF, or sometime afterwards.
>> >>>>
>> >>>> cheers,
>> >>>>
>> >>>> -ken
>> >>>>
>> >>>>
>> >>>>> A main document (A) in which we explain the method, the scenarios
>> >>>>> and the minimum signaling issues in order to make it work. The
>> >>>>> idea is that document
>> >>>>> (A) would be self-contained. Since we are not defining new
>> >>>>> protocols
>> >>> (i.e.
>> >>>>> already existing compressing, multiplexing and tunneling protocols
>> >>>>> are to be used), we understand that this can be done in a single
>> >>>> document.
>> >>>>> It would
>> >>>>> include:
>> >>>>>
>> >>>>> 1- Protocol stack (it would be the "reference model")
>> >>>>> 2- a negotiation mechanism to decide the options to use at each
>> >>>>> layer
>> >>>>> 3- a mechanism to setup/release a tunnel between a multiplexer and
>> >>>>> a de-multiplexer
>> >>>>>
>> >>>>> Of course, another approach could be separating 1 from 2&3.
>> >>>>> However, we think this is not necessary since the method is not
>> >>>>> too
>> >>>> complicated.
>> >>>>>
>> >>>>>
>> >>>>> Document (B) would only contain recommendations of how to better
>> >>>>> use the method proposed in document (A), i.e., classification and
>> >>>>> maximum
>> >>>> delays.
>> >>>>>
>> >>>>> So clearly document (B) would totally depend on the reference
>> >>>>> model of document (A).
>> >>>>>
>> >>>>>
>> >>>>> The idea of point 9 is to talk about some other interesting ideas
>> >>>>> which are considered as "future work":
>> >>>>> - a mechanism for a multiplexer to discover a de-multiplexer
>> >>>>> - mechanism to select an optimal multiplexer and a de-multiplexer
>> >>>>> when there are more than one muxer/de-muxer for a flow
>> >>>>> - dynamically applying TCMTF
>> >>>>> - etc.
>> >>>>>
>> >>>>> What do you think?
>> >>>>>
>> >>>>> Thanks again for your feedback. Thinking and explaining things is
>> >>>>> always a good exercise!
>> >>>>>
>> >>>>> Jose
>> >>>>>
>> >>>>>> -----Mensaje original-----
>> >>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> >>>>>> nombre de ken carlberg Enviado el: mi=E9rcoles, 27 de febrero de
>> >>>>>> 2013
>> >>>>>> 16:23
>> >>>>>> Para: jsaldana@unizar.es
>> >>>>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
>> >>>>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about
>> >>>>>> TCMTF in
>> >>>>>> IETF87
>> >>>>>>
>> >>>>>> Hola Jose,
>> >>>>>>
>> >>>>>> sorry for the tardy reply.  The altered text below is helpful,
>> >>>> thanks.
>> >>>>>>
>> >>>>>> With respect to your candidate deliverables, it appears that you
>> >>>>>> have
>> >>>>> listed
>> >>>>>> two for the proposed group: (A) a document that describes options
>> >>>>>> and negotiation mechanisms, and (B) a document describing
>> >>>> recommendations
>> >>>>>> of which packet types should be multiplexed and a list fo traffic
>> >>>>> classification
>> >>>>>> methods.  Have you considered a third document that presents a
>> >>>>>> more encompassing architecture or framework that would include
>> >>>>>> sample scenarios upon which your deliverables A & B are aimed at?
>> >>>>>> My impression
>> >>>>> is
>> >>>>>> that you may want to point the reader of documents A & B to the
>> >>>>>> same reference model, and instead of repeating the same text, it
>> >>>>>> may be helpful to separate this into a separate document.
>> >>>>>>
>> >>>>>> Also, would section 9 of your proposed charter lead one to
>> >>>>>> consider a requirements document?  Many times, new groups start
>> >>>>>> with a requirements document, but since you have a good focus of
>> >>>>>> what you want to accomplish, perhaps your last deliverable could
>> >>>>>> be a requirements document that would guide any future work.
>> >>>>>>
>> >>>>>> -ken
>> >>>>>>
>> >>>>>> ps, I don't want to advocate more work, but rather just have you
>> >>>>>> consider other possibilities (and feel free to shoot them down
>> >>>>>> :-)
>> >>>>>>
>> >>>>>>
>> >>>>>> On Feb 22, 2013, at 5:39 AM, Jose Saldana <jsaldana@unizar.es>
>> >> wrote:
>> >>>>>>
>> >>>>>>> Hi Ken,
>> >>>>>>>
>> >>>>>>> Sorry for the delay. I think you are talking about Paragraph 5:
>> >>>>>>>
>> >>>>>>> 5. So the first objective of this group is to specify the
>> >>>>>>> protocol stack for tunneling, compressing and multiplexing
>> >>>>>>> traffic flows (TCMTF). Since standard protocols are being used
>> >>>>>>> at each layer, the signaling methods of those protocols will be
>used.
>> >>>>>>> Interactions with the Working Groups and Areas in which these
>> >>>>>>> protocols are developed can be expected. However, the
>> >> development
>> >>>>>>> of new compressing, multiplexing or tunneling protocols is not
>> >>>>>>> an objective of this Working Group. In addition, since the
>> >>>>>>> current RFC 4170 would be
>> >>>>>> considered as one of the options, this RFC could be obsoleted.
>> >>>>>>>
>> >>>>>>> Perhaps this is a bit confusing. When we say "at each layer", we
>> >>>>>>> are talking about "tunneling, compressing and multiplexing"
>layers.
>> >>>>>>> Perhaps this can be a bit confusing. What about this?:
>> >>>>>>>
>> >>>>>>> 5. So the first objective of this group is to specify the
>> >>>>>>> protocol stack for tunneling, compressing and multiplexing
>> >>>>>>> traffic flows (TCMTF). Since standard protocols are being used
>> >>>>>>> for tunneling, compressing and multiplexing layers, the
>> >>>>>>> signaling methods of those
>> >>>>>> protocols will be used.
>> >>>>>>> Interactions with the Working Groups and Areas in which these
>> >>>>>>> protocols are developed can be expected. However, the
>> >> development
>> >>>> of
>> >>>>>>> new compressing, multiplexing or tunneling protocols is not an
>> >>>>>>> objective of this Working Group. In addition, since the current
>> >>>>>>> RFC
>> >>>>>>> 4170 would be considered as one of the options, this RFC could
>> >>>>>>> be
>> >>>>>> obsoleted.
>> >>>>>>>
>> >>>>>>> Is this what you were asking?
>> >>>>>>>
>> >>>>>>> Thanks for your feedback.
>> >>>>>>>
>> >>>>>>> Jose
>> >>>>>>>
>> >>>>>>>> -----Mensaje original-----
>> >>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> >>>>>>>> nombre de ken carlberg Enviado el: martes, 19 de febrero de
>> >>>>>>>> 2013
>> >>>>>>>> 14:17
>> >>>>>>>> Para: jsaldana@unizar.es
>> >>>>>>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
>> >>>>>>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about
>> >>>>>>>> TCMTF in
>> >>>>>>>> IETF87
>> >>>>>>>>
>> >>>>>>>> Hola Jose,
>> >>>>>>>>
>> >>>>>>>> could you expand a bit more on your text in the proposed
>> >>>>>>>> charter regarding "signaling methods".  Are you speaking in the
>> >>>>>>>> more general context of information stored in headers of
>> >>>>>>>> various protocol up and down the stack
>> >>>>>>> (ie,
>> >>>>>>>> layers 3, 4, and 5/app)?  Or, are you  speaking of concurrent
>> >>>>>>>> resource signaling protocols like RSVP/RSVP-TE, or path
>> >>>>>>>> establishment protocols
>> >>>>>>> like
>> >>>>>>>> MPLS?  Or, some combination of both?
>> >>>>>>>>
>> >>>>>>>> -ken
>> >>>>>>>>
>> >>>>>>>> _______________________________________________
>> >>>>>>>> tcmtf mailing list
>> >>>>>>>> tcmtf@ietf.org
>> >>>>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>>>>>
>> >>>>>>
>> >>>>>> _______________________________________________
>> >>>>>> tcmtf mailing list
>> >>>>>> tcmtf@ietf.org
>> >>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>>>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> tcmtf mailing list
>> >>> tcmtf@ietf.org
>> >>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>> _______________________________________________
>> >>> tcmtf mailing list
>> >>> tcmtf@ietf.org
>> >>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >>
>> >>
>> >> ________________________________
>> >>
>> >> Este mensaje se dirige exclusivamente a su destinatario. Puede
>> >> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo elect=
r=F3nico
>> >> en el enlace situado m=E1s abajo.
>> >> This message is intended exclusively for its addressee. We only send
>> >> and receive email on the basis of the terms set out at:
>> >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> >> _______________________________________________
>> >> tcmtf mailing list
>> >> tcmtf@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/tcmtf
>> >
>> > _______________________________________________
>> > tcmtf mailing list
>> > tcmtf@ietf.org
>> > https://www.ietf.org/mailman/listinfo/tcmtf
>>
>>
>> --
>> "Esta vez no fallaremos, Doctor Infierno"
>>
>> Dr Diego R. Lopez
>> Telefonica I+D
>> http://people.tid.es/diego.lopez/
>>
>> e-mail: diego@tid.es
>> Tel:    +34 913 129 041
>> Mobile: +34 682 051 091
>> -----------------------------------------
>>
>>
>> ________________________________
>>
>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>> nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en 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
>


________________________________

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

From jsaldana@unizar.es  Fri Jun  7 01:52:09 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCE7B21F8D10 for <tcmtf@ietfa.amsl.com>; Fri,  7 Jun 2013 01:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qNMKCPXUiVwg for <tcmtf@ietfa.amsl.com>; Fri,  7 Jun 2013 01:51:55 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 71C5721F89EB for <tcmtf@ietf.org>; Fri,  7 Jun 2013 01:51:54 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r578pmqb020145; Fri, 7 Jun 2013 10:51:48 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>, "'Diego R. Lopez'" <diego@tid.es>, "=?iso-8859-2?Q?'Mirko_Su=BEnjevi=E6'?=" <Mirko.Suznjevic@fer.hr>
References: <001b01ce6351$dbd4a4d0$937dee70$@unizar.es> <F5EDC35DF914C1428C28E149F10463A29C8A3442@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A29C8A3442@EX10-MB2-MAD.hi.inet>
Date: Fri, 7 Jun 2013 10:51:51 +0200
Organization: Universidad de Zaragoza
Message-ID: <002f01ce635c$411d3fa0$c357bee0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Content-Language: es
Thread-Index: AQJH9jSrqxzpiuv0ZHAXEaVXFk7D4Jg2yhOg
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small modification
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2013 08:52:10 -0000

You are right, Fernando. The question is that in the end everything =
travels
in a tunnel. But this may sound confusing, since tunneling is just one =
of
the layers. What about this?

We can talk about a "TCMTF session" or a "TCMTF communication" instead =
of
"TCMTF tunnel".

I prefer "TCMTF session":

- TCMTF - negotiation protocol:
	- a mechanism to setup/release a *TCMTF session* between a
multiplexer and a de-multiplexer, including the negotiation mechanism to
decide the options to use at each layer (header compression, =
multiplexing
and tunneling)

Which one do you prefer? Other names?

Thanks!

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> FERNANDO PASCUAL BLANCO
> Enviado el: viernes, 07 de junio de 2013 9:56
> Para: jsaldana@unizar.es; Diego R. Lopez; 'Mirko Su=BEnjevi=E6'
> CC: tcmtf@ietf.org
> Asunto: Re: [tcmtf] TCMTF: Documents to be generated. Small =
modification
>=20
> Hi Jose,
>=20
>         I have doubts about the description of the second document, =
why
are
> you focusing the description on the tunneling layer? I understand that
there
> will be two options: a dialog (protocol) to negotiate every option at =
each
> layer or three dialogs to negotiate each layer, but in that case the
tunnel
> layer will not be different from others. What do you think about a
description
> less tunnel oriented?
>=20
> Regards,
>=20
> Fernando Pascual Blanco
> Telef=F3nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>=20
>=20
>=20
>=20
> On 07/06/13 09:37, "Jose Saldana" <jsaldana@unizar.es> wrote:
>=20
> >Ok then.
> >
> >We can use these document names in the new version of the Charter (I
> >will try to rewrite it by Tuesday):
> >
> >- TCMTF - reference model:
> >       the protocol stack and scenarios. It should be said that each
> >protocol at each layer will use its own signaling mechanisms.
> >       https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
> >
> >
> >- TCMTF - negotiation protocol:
> >       - a mechanism to setup/release a TCMTF tunnel between a
> >multiplexer and a de-multiplexer, including the negotiation mechanism
> >to decide the options to use at each layer
> >
> >
> >- TCMTF - recommendations:
> >       useful recommendations in order to decide which packet flows =
can
> >or can not be multiplexed and how. 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.
> >       =
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
> >
> >
> >Any comments?
> >
> >Jose
> >
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> >> de Diego R. Lopez Enviado el: jueves, 06 de junio de 2013 15:15
> >> Para: <jsaldana@unizar.es>
> >> CC: <tcmtf@ietf.org>; Mirko Su=BEnjevi=E6; FERNANDO PASCUAL BLANCO
> >> Asunto: Re: [tcmtf] TCMTF: Documents to be generated. Small
> >> modification
> >>
> >> Hmmm... The necessary outcome of the negotiation is the setup. I'd
> >> keep the shorter name.
> >>
> >> Be goode,
> >>
> >> On 6 Jun 2013, at 15:05 , Jose Saldana wrote:
> >>
> >> > One question:
> >> >
> >> > The new second draft should include:
> >> >
> >> > - The negotiation
> >> > - The setup/release a TCMTF tunnel between a mux and a demux
> >> >
> >> > Do you think "TCMTF - negotiation protocol" also includes the
> >> > second
> >idea?
> >> >
> >> > Would it be better "TCMTF - negotiation and setup" ?
> >> >
> >> > Thanks!
> >> >
> >> > Jose
> >> >
> >> >> -----Mensaje original-----
> >> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >> >> nombre de Mirko Su=BEnjevic Enviado el: jueves, 06 de junio de =
2013
> >> >> 14:32
> >> >> Para: FERNANDO PASCUAL BLANCO; tcmtf@ietf.org
> >> >> Asunto: Re: [tcmtf] TCMTF: Documents to be generated. Small
> >> >> modification
> >> >>
> >> >> Yes i think that is better.
> >> >> Mirko
> >> >>
> >> >> -----Original Message-----
> >> >> From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> >> >> Sent: Thursday, June 6, 2013 1:53 PM
> >> >> To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org
> >> >> Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small
> >> >> modification
> >> >>
> >> >> And what about:
> >> >>
> >> >> TCMTF - negotiation protocol
> >> >>
> >> >> Do you found it more descriptive?
> >> >>
> >> >> Regards,
> >> >>
> >> >> Fernando Pascual Blanco
> >> >> Telef=F3nica Global Resources
> >> >> Network Automation and Dynamization TECHNOLOGY PEOPLE GROUP
> F
> >> >> +34913128779 M +34682005168 fpb@tid.es
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On 06/06/13 11:51, "Mirko Su=BEnjevi=E6" =
<Mirko.Suznjevic@fer.hr>
> wrote:
> >> >>
> >> >>> Hello,
> >> >>> I think these names are ok. Maybe we should discuss the second
> >> >>> one in more detail.
> >> >>> Perhaps include negotiation in the name of the draft so its
> >> >>> purpose is evident from the title? As the purpose of that draft
> >> >>> is to establish which particular parameters will be used.
> >> >>> My suggestions are:
> >> >>> TCMTF - negotiation signalling
> >> >>> TCMTF - negotiation process
> >> >>> TCMTF - parameter signalling
> >> >>> Or something along those lines?
> >> >>> Mirko
> >> >>>
> >> >>> -----Original Message-----
> >> >>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
> >> >>> Behalf Of Jose Saldana
> >> >>> Sent: Wednesday, June 5, 2013 12:56 PM
> >> >>> To: tcmtf@ietf.org
> >> >>> Cc: tsv-area@ietf.org; spencerdawkins.ietf@gmail.com; 'ken
> >> >>> carlberg'; Martin Stiemerling
> >> >>> Subject: [tcmtf] TCMTF: Documents to be generated. Small
> >> >>> modification
> >> >>>
> >> >>> In the conf-call of yesterday it was also clear that for the =
IETF
> >> >>> it is better to split Document A into two documents:
> >> >>>
> >> >>> - The "TCMTF reference model" (1): the protocol stack and
scenarios.
> >> >>> It should be said that each protocol at each layer will use its
> >> >>> own signaling mechanisms.
> >> >>>
> >> >>> - The "TCMTF-specific signaling": there are some things we will
> >> >>> need to
> >> >>> deploy:
> >> >>>      - a negotiation mechanism (2) to decide the options to use
> >> >>> at each layer (e.g. a mux and demux agree on using
> ROHC+PPPMux+GRE)
> >> >>>      - a mechanism to setup/release a TCMTF tunnel (3)between a
> >> >>> multiplexer and a de-multiplexer
> >> >>>
> >> >>>
> >> >>> The current draft is the TCMTF "reference model", since it does
> >> >>> not talk about specific signaling issues.
> >> >>>
> >> >>> By now, we don't have to propose the "TCMTF specific =
signaling".
> >> >>> It would be something to be deployed if the Working Group is
> created.
> >> >>>
> >> >>> This same idea was proposed by Ken Carlberg in February. The
> >> >>> advantages of this new distribution of the documents are =
(quoting
> >Ken):
> >> >>>
> >> >>>> One thing to keep in mind is that it is possible that (2) and
> >> >>>> (3)
> >> >>>> (below) can change over time and yet (1) (the reference model)
> >> >>>> does not, then it may be best to separate (1) from the other
items.
> >> >>>
> >> >>>> a more encompassing architecture or framework that would =
include
> >> >>>> sample scenarios upon which your deliverables A & B are aimed =
at?
> >> >>>> My impression is that you may want to point the reader of
> >> >>>> documents A & B to the same reference model, and instead of
> >> >>>> repeating the same text, it may be helpful to separate this =
into
> >> >>>> a separate
> >document.
> >> >>>
> >> >>>
> >> >>> Once discussed, I would create a new charter proposal including
> >> >>> these changes.
> >> >>>
> >> >>>
> >> >>> Do you like these short names for the documents?
> >> >>>
> >> >>> - "TCMTF reference model".
> >> >>> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
> >> >>>
> >> >>> - "TCMTF-specific signaling". Future work
> >> >>>
> >> >>> - "TCMTF recommendations".
> >> >>> =
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
> >> >>>
> >> >>>
> >> >>> Your feedback will be welcome. Thanks!
> >> >>>
> >> >>> Jose
> >> >>>
> >> >>>> -----Mensaje original-----
> >> >>>> De: ken carlberg [mailto:carlberg@g11.org.uk] Enviado el:
> >> >>>> martes,
> >> >>>> 05 de marzo de 2013 17:07
> >> >>>> Para: jsaldana@unizar.es
> >> >>>> CC: 'ken carlberg'; tcmtf@ietf.org; tsv-area@ietf.org
> >> >>>> Asunto: Re: [tcmtf] About the possibility of having a BOF =
about
> >> >>>> TCMTF in
> >> >>>> IETF87
> >> >>>>
> >> >>>> Hola Jose,
> >> >>>>
> >> >>>> Thanks for the expanded explanation, and again, apologies for
> >> >>>> the tardy repsonse.  Its helpful to understand that document A
> >> >>>> and B are sequential
> >> >>> to
> >> >>>> each other.  One thing to keep in mind is that if its possible
> >> >>>> that
> >> >>>> 2 and
> >> >>> 3
> >> >>>> (below) can change over time and yet 1 (the reference model)
> >> >>>> does not, then it may be best to separate 1 from the other =
items.
> >> >>>>
> >> >>>> as for what you outline as a discussion point for future work,
> >> >>>> it seems
> >> >>> fine.  I
> >> >>>> just have a personal bias that if you have a clear idea of the
> >> >>>> things
> >> >>> you'd like
> >> >>>> to accomplish in the future, then having a requirements =
document
> >> >>>> would be helpful to focus those thoughts without having to =
have
> >> >>>> one particular solution.  But that's a discussion point that
> >> >>>> could be brought up during
> >> >>> the
> >> >>>> BoF, or sometime afterwards.
> >> >>>>
> >> >>>> cheers,
> >> >>>>
> >> >>>> -ken
> >> >>>>
> >> >>>>
> >> >>>>> A main document (A) in which we explain the method, the
> >> >>>>> scenarios and the minimum signaling issues in order to make =
it
> >> >>>>> work. The idea is that document
> >> >>>>> (A) would be self-contained. Since we are not defining new
> >> >>>>> protocols
> >> >>> (i.e.
> >> >>>>> already existing compressing, multiplexing and tunneling
> >> >>>>> protocols are to be used), we understand that this can be =
done
> >> >>>>> in a single
> >> >>>> document.
> >> >>>>> It would
> >> >>>>> include:
> >> >>>>>
> >> >>>>> 1- Protocol stack (it would be the "reference model")
> >> >>>>> 2- a negotiation mechanism to decide the options to use at =
each
> >> >>>>> layer
> >> >>>>> 3- a mechanism to setup/release a tunnel between a =
multiplexer
> >> >>>>> and a de-multiplexer
> >> >>>>>
> >> >>>>> Of course, another approach could be separating 1 from 2&3.
> >> >>>>> However, we think this is not necessary since the method is =
not
> >> >>>>> too
> >> >>>> complicated.
> >> >>>>>
> >> >>>>>
> >> >>>>> Document (B) would only contain recommendations of how to
> >> >>>>> better use the method proposed in document (A), i.e.,
> >> >>>>> classification and maximum
> >> >>>> delays.
> >> >>>>>
> >> >>>>> So clearly document (B) would totally depend on the reference
> >> >>>>> model of document (A).
> >> >>>>>
> >> >>>>>
> >> >>>>> The idea of point 9 is to talk about some other interesting
> >> >>>>> ideas which are considered as "future work":
> >> >>>>> - a mechanism for a multiplexer to discover a de-multiplexer
> >> >>>>> - mechanism to select an optimal multiplexer and a
> >> >>>>> de-multiplexer when there are more than one muxer/de-muxer
> for
> >> >>>>> a flow
> >> >>>>> - dynamically applying TCMTF
> >> >>>>> - etc.
> >> >>>>>
> >> >>>>> What do you think?
> >> >>>>>
> >> >>>>> Thanks again for your feedback. Thinking and explaining =
things
> >> >>>>> is always a good exercise!
> >> >>>>>
> >> >>>>> Jose
> >> >>>>>
> >> >>>>>> -----Mensaje original-----
> >> >>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] =
En
> >> >>>>>> nombre de ken carlberg Enviado el: mi=E9rcoles, 27 de =
febrero de
> >> >>>>>> 2013
> >> >>>>>> 16:23
> >> >>>>>> Para: jsaldana@unizar.es
> >> >>>>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
> >> >>>>>> Asunto: Re: [tcmtf] About the possibility of having a BOF
> >> >>>>>> about TCMTF in
> >> >>>>>> IETF87
> >> >>>>>>
> >> >>>>>> Hola Jose,
> >> >>>>>>
> >> >>>>>> sorry for the tardy reply.  The altered text below is =
helpful,
> >> >>>> thanks.
> >> >>>>>>
> >> >>>>>> With respect to your candidate deliverables, it appears that
> >> >>>>>> you have
> >> >>>>> listed
> >> >>>>>> two for the proposed group: (A) a document that describes
> >> >>>>>> options and negotiation mechanisms, and (B) a document
> >> >>>>>> describing
> >> >>>> recommendations
> >> >>>>>> of which packet types should be multiplexed and a list fo
> >> >>>>>> traffic
> >> >>>>> classification
> >> >>>>>> methods.  Have you considered a third document that presents =
a
> >> >>>>>> more encompassing architecture or framework that would
> include
> >> >>>>>> sample scenarios upon which your deliverables A & B are =
aimed
> at?
> >> >>>>>> My impression
> >> >>>>> is
> >> >>>>>> that you may want to point the reader of documents A & B to
> >> >>>>>> the same reference model, and instead of repeating the same
> >> >>>>>> text, it may be helpful to separate this into a separate
document.
> >> >>>>>>
> >> >>>>>> Also, would section 9 of your proposed charter lead one to
> >> >>>>>> consider a requirements document?  Many times, new groups
> >> >>>>>> start with a requirements document, but since you have a =
good
> >> >>>>>> focus of what you want to accomplish, perhaps your last
> >> >>>>>> deliverable could be a requirements document that would =
guide
> any future work.
> >> >>>>>>
> >> >>>>>> -ken
> >> >>>>>>
> >> >>>>>> ps, I don't want to advocate more work, but rather just have
> >> >>>>>> you consider other possibilities (and feel free to shoot =
them
> >> >>>>>> down
> >> >>>>>> :-)
> >> >>>>>>
> >> >>>>>>
> >> >>>>>> On Feb 22, 2013, at 5:39 AM, Jose Saldana =
<jsaldana@unizar.es>
> >> >> wrote:
> >> >>>>>>
> >> >>>>>>> Hi Ken,
> >> >>>>>>>
> >> >>>>>>> Sorry for the delay. I think you are talking about =
Paragraph 5:
> >> >>>>>>>
> >> >>>>>>> 5. So the first objective of this group is to specify the
> >> >>>>>>> protocol stack for tunneling, compressing and multiplexing
> >> >>>>>>> traffic flows (TCMTF). Since standard protocols are being
> >> >>>>>>> used at each layer, the signaling methods of those =
protocols
> >> >>>>>>> will be
> >used.
> >> >>>>>>> Interactions with the Working Groups and Areas in which =
these
> >> >>>>>>> protocols are developed can be expected. However, the
> >> >> development
> >> >>>>>>> of new compressing, multiplexing or tunneling protocols is
> >> >>>>>>> not an objective of this Working Group. In addition, since
> >> >>>>>>> the current RFC 4170 would be
> >> >>>>>> considered as one of the options, this RFC could be =
obsoleted.
> >> >>>>>>>
> >> >>>>>>> Perhaps this is a bit confusing. When we say "at each =
layer",
> >> >>>>>>> we are talking about "tunneling, compressing and =
multiplexing"
> >layers.
> >> >>>>>>> Perhaps this can be a bit confusing. What about this?:
> >> >>>>>>>
> >> >>>>>>> 5. So the first objective of this group is to specify the
> >> >>>>>>> protocol stack for tunneling, compressing and multiplexing
> >> >>>>>>> traffic flows (TCMTF). Since standard protocols are being
> >> >>>>>>> used for tunneling, compressing and multiplexing layers, =
the
> >> >>>>>>> signaling methods of those
> >> >>>>>> protocols will be used.
> >> >>>>>>> Interactions with the Working Groups and Areas in which =
these
> >> >>>>>>> protocols are developed can be expected. However, the
> >> >> development
> >> >>>> of
> >> >>>>>>> new compressing, multiplexing or tunneling protocols is not
> >> >>>>>>> an objective of this Working Group. In addition, since the
> >> >>>>>>> current RFC
> >> >>>>>>> 4170 would be considered as one of the options, this RFC
> >> >>>>>>> could be
> >> >>>>>> obsoleted.
> >> >>>>>>>
> >> >>>>>>> Is this what you were asking?
> >> >>>>>>>
> >> >>>>>>> Thanks for your feedback.
> >> >>>>>>>
> >> >>>>>>> Jose
> >> >>>>>>>
> >> >>>>>>>> -----Mensaje original-----
> >> >>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org]
> >> >>>>>>>> En nombre de ken carlberg Enviado el: martes, 19 de =
febrero
> >> >>>>>>>> de
> >> >>>>>>>> 2013
> >> >>>>>>>> 14:17
> >> >>>>>>>> Para: jsaldana@unizar.es
> >> >>>>>>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
> >> >>>>>>>> Asunto: Re: [tcmtf] About the possibility of having a BOF
> >> >>>>>>>> about TCMTF in
> >> >>>>>>>> IETF87
> >> >>>>>>>>
> >> >>>>>>>> Hola Jose,
> >> >>>>>>>>
> >> >>>>>>>> could you expand a bit more on your text in the proposed
> >> >>>>>>>> charter regarding "signaling methods".  Are you speaking =
in
> >> >>>>>>>> the more general context of information stored in headers =
of
> >> >>>>>>>> various protocol up and down the stack
> >> >>>>>>> (ie,
> >> >>>>>>>> layers 3, 4, and 5/app)?  Or, are you  speaking of
> >> >>>>>>>> concurrent resource signaling protocols like RSVP/RSVP-TE,
> >> >>>>>>>> or path establishment protocols
> >> >>>>>>> like
> >> >>>>>>>> MPLS?  Or, some combination of both?
> >> >>>>>>>>
> >> >>>>>>>> -ken
> >> >>>>>>>>
> >> >>>>>>>> _______________________________________________
> >> >>>>>>>> tcmtf mailing list
> >> >>>>>>>> tcmtf@ietf.org
> >> >>>>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>>>>>
> >> >>>>>>
> >> >>>>>> _______________________________________________
> >> >>>>>> tcmtf mailing list
> >> >>>>>> tcmtf@ietf.org
> >> >>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>>>>
> >> >>>
> >> >>>
> >> >>> _______________________________________________
> >> >>> tcmtf mailing list
> >> >>> tcmtf@ietf.org
> >> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>> _______________________________________________
> >> >>> tcmtf mailing list
> >> >>> tcmtf@ietf.org
> >> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >>
> >> >>
> >> >> ________________________________
> >> >>
> >> >> Este mensaje se dirige exclusivamente a su destinatario. Puede
> >> >> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo
> >> >> electr=F3nico en el enlace situado m=E1s abajo.
> >> >> This message is intended exclusively for its addressee. We only
> >> >> send and receive email on the basis of the terms set out at:
> >> >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >> >> _______________________________________________
> >> >> tcmtf mailing list
> >> >> tcmtf@ietf.org
> >> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >> >
> >> > _______________________________________________
> >> > tcmtf mailing list
> >> > tcmtf@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/tcmtf
> >>
> >>
> >> --
> >> "Esta vez no fallaremos, Doctor Infierno"
> >>
> >> Dr Diego R. Lopez
> >> Telefonica I+D
> >> http://people.tid.es/diego.lopez/
> >>
> >> e-mail: diego@tid.es
> >> Tel:    +34 913 129 041
> >> Mobile: +34 682 051 091
> >> -----------------------------------------
> >>
> >>
> >> ________________________________
> >>
> >> Este mensaje se dirige exclusivamente a su destinatario. Puede
> >> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico
> >> en el enlace situado m=E1s abajo.
> >> This message is intended exclusively for its addressee. We only =
send
> >> and receive email on the basis of the terms set out at:
> >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >> _______________________________________________
> >> tcmtf mailing list
> >> tcmtf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >
>=20
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar
> nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en =
el enlace
> situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send =
and
> receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From fpb@tid.es  Fri Jun  7 01:54:48 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDFEA21F8C4C for <tcmtf@ietfa.amsl.com>; Fri,  7 Jun 2013 01:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kBpGOWw2w8xd for <tcmtf@ietfa.amsl.com>; Fri,  7 Jun 2013 01:54:43 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 85C7B21F8F2F for <tcmtf@ietf.org>; Fri,  7 Jun 2013 01:54:41 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MO000HI1M2WI4@tid.hi.inet> for tcmtf@ietf.org; Fri, 07 Jun 2013 10:54:40 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 4C.BE.03066.FCF91B15; Fri, 07 Jun 2013 10:54:40 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MO000HIWM33I4@tid.hi.inet> for tcmtf@ietf.org; Fri, 07 Jun 2013 10:54:39 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Fri, 07 Jun 2013 10:53:52 +0200
Date: Fri, 07 Jun 2013 08:54:38 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <002f01ce635c$411d3fa0$c357bee0$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "Diego R. Lopez" <diego@tid.es>, =?iso-8859-2?Q?=27Mirko_Su=BEnjevi=E6=27?= <Mirko.Suznjevic@fer.hr>
Message-id: <F5EDC35DF914C1428C28E149F10463A29C8A37D8@EX10-MB2-MAD.hi.inet>
Content-id: <58CDCE9DC9E90943AA09C9DDD13DBB2D@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-2
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] TCMTF: Documents to be generated. Small modification
Thread-index: Ac5h2eb/R9lrIRTzTmSkhKAFyvT4WQAwM8mgAAAmDdAABErmAAABUBCA///n/4CAAALPAIABM+wAgAAmvYD//+4OgIAAIk+A
user-agent: Microsoft-MacOutlook/14.3.2.130206
X-AuditID: 0a5f4068-b7fe16d000000bfa-a7-51b19fcf9ebb
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42Lhinfg0r0wf2OgwXFti12fNzA6MHosWfKT KYAxissmJTUnsyy1SN8ugSvj5fUljAWrVzFWvP5wmbWBcU4HYxcjJ4eEgInEvCsHmSFsMYkL 99azdTFycQgJbGSUeH36GzOE84NR4urEzSwQzjRGiVeLjrGBtLAIqEo0NG8Es9kEtCRO313F AmILC3hK3Pz7kgnE5hSwkHj/5hEbxAoFiT/nHoMNEhGYyiixbeYhoDs4OJiBBs37pghSwyvg LbF82yewOcwCZhITN/5hg4gLSvyYfI8FolxH4uukCIgScYnm1ptQ5doST95dYAWxGQVkJd7N nw9miwh4SUz99Jcdwi6Q+L+4BywuKqAncfNMCyvEaQISS/ach4aEqMTLx/9YJzBKzEJyxSwk V8xCuGIWkitmIbliASPrKkax4qSizPSMktzEzJx0A0O9jEy9zLzUkk2MkLjL2MG4fKfKIUYB DkYlHt4fqzYECrEmlhVX5h5ilOBgVhLhfTlrY6AQb0piZVVqUX58UWlOavEhRiYOTqkGRk+p KnkJzcawWI2lfwT+rIrT2n2wy2ld1zM7AyY959q8HZuFJib0pC9o2yHjW7nGY4eQPo9IztrW JdeSPxZu+Rc14/691tg1Xbf37qnl+KihIcS78e6CSXq1qraxi0pTZn0qK7NlvWV8tH/CbnnB RKagn1eEdorkJEgHT5JKEJ5tnVEe8fKXEktxRqKhFnNRcSIAnSDaNpkCAAA=
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small modification
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2013 08:54:49 -0000

It sounds very good!

Saludos,

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




On 07/06/13 10:51, "Jose Saldana" <jsaldana@unizar.es> wrote:

>You are right, Fernando. The question is that in the end everything
>travels
>in a tunnel. But this may sound confusing, since tunneling is just one of
>the layers. What about this?
>
>We can talk about a "TCMTF session" or a "TCMTF communication" instead of
>"TCMTF tunnel".
>
>I prefer "TCMTF session":
>
>- TCMTF - negotiation protocol:
>       - a mechanism to setup/release a *TCMTF session* between a
>multiplexer and a de-multiplexer, including the negotiation mechanism to
>decide the options to use at each layer (header compression, multiplexing
>and tunneling)
>
>Which one do you prefer? Other names?
>
>Thanks!
>
>Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> FERNANDO PASCUAL BLANCO
>> Enviado el: viernes, 07 de junio de 2013 9:56
>> Para: jsaldana@unizar.es; Diego R. Lopez; 'Mirko Su=BEnjevi=E6'
>> CC: tcmtf@ietf.org
>> Asunto: Re: [tcmtf] TCMTF: Documents to be generated. Small modification
>>
>> Hi Jose,
>>
>>         I have doubts about the description of the second document, why
>are
>> you focusing the description on the tunneling layer? I understand that
>there
>> will be two options: a dialog (protocol) to negotiate every option at
>>each
>> layer or three dialogs to negotiate each layer, but in that case the
>tunnel
>> layer will not be different from others. What do you think about a
>description
>> less tunnel oriented?
>>
>> Regards,
>>
>> Fernando Pascual Blanco
>> Telef=F3nica Global Resources
>> Network Automation and Dynamization
>> TECHNOLOGY PEOPLE GROUP
>> F +34913128779
>> M +34682005168
>> fpb@tid.es
>>
>>
>>
>>
>> On 07/06/13 09:37, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>
>> >Ok then.
>> >
>> >We can use these document names in the new version of the Charter (I
>> >will try to rewrite it by Tuesday):
>> >
>> >- TCMTF - reference model:
>> >       the protocol stack and scenarios. It should be said that each
>> >protocol at each layer will use its own signaling mechanisms.
>> >       https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>> >
>> >
>> >- TCMTF - negotiation protocol:
>> >       - a mechanism to setup/release a TCMTF tunnel between a
>> >multiplexer and a de-multiplexer, including the negotiation mechanism
>> >to decide the options to use at each layer
>> >
>> >
>> >- TCMTF - recommendations:
>> >       useful recommendations in order to decide which packet flows can
>> >or can not be multiplexed and how. 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.
>> >       http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>> >
>> >
>> >Any comments?
>> >
>> >Jose
>> >
>> >> -----Mensaje original-----
>> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>> >> de Diego R. Lopez Enviado el: jueves, 06 de junio de 2013 15:15
>> >> Para: <jsaldana@unizar.es>
>> >> CC: <tcmtf@ietf.org>; Mirko Su=BEnjevi=E6; FERNANDO PASCUAL BLANCO
>> >> Asunto: Re: [tcmtf] TCMTF: Documents to be generated. Small
>> >> modification
>> >>
>> >> Hmmm... The necessary outcome of the negotiation is the setup. I'd
>> >> keep the shorter name.
>> >>
>> >> Be goode,
>> >>
>> >> On 6 Jun 2013, at 15:05 , Jose Saldana wrote:
>> >>
>> >> > One question:
>> >> >
>> >> > The new second draft should include:
>> >> >
>> >> > - The negotiation
>> >> > - The setup/release a TCMTF tunnel between a mux and a demux
>> >> >
>> >> > Do you think "TCMTF - negotiation protocol" also includes the
>> >> > second
>> >idea?
>> >> >
>> >> > Would it be better "TCMTF - negotiation and setup" ?
>> >> >
>> >> > Thanks!
>> >> >
>> >> > Jose
>> >> >
>> >> >> -----Mensaje original-----
>> >> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> >> >> nombre de Mirko Su=BEnjevic Enviado el: jueves, 06 de junio de 201=
3
>> >> >> 14:32
>> >> >> Para: FERNANDO PASCUAL BLANCO; tcmtf@ietf.org
>> >> >> Asunto: Re: [tcmtf] TCMTF: Documents to be generated. Small
>> >> >> modification
>> >> >>
>> >> >> Yes i think that is better.
>> >> >> Mirko
>> >> >>
>> >> >> -----Original Message-----
>> >> >> From: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>> >> >> Sent: Thursday, June 6, 2013 1:53 PM
>> >> >> To: Mirko Su=BEnjevi=E6; tcmtf@ietf.org
>> >> >> Subject: Re: [tcmtf] TCMTF: Documents to be generated. Small
>> >> >> modification
>> >> >>
>> >> >> And what about:
>> >> >>
>> >> >> TCMTF - negotiation protocol
>> >> >>
>> >> >> Do you found it more descriptive?
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> Fernando Pascual Blanco
>> >> >> Telef=F3nica Global Resources
>> >> >> Network Automation and Dynamization TECHNOLOGY PEOPLE GROUP
>> F
>> >> >> +34913128779 M +34682005168 fpb@tid.es
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> On 06/06/13 11:51, "Mirko Su=BEnjevi=E6" <Mirko.Suznjevic@fer.hr>
>> wrote:
>> >> >>
>> >> >>> Hello,
>> >> >>> I think these names are ok. Maybe we should discuss the second
>> >> >>> one in more detail.
>> >> >>> Perhaps include negotiation in the name of the draft so its
>> >> >>> purpose is evident from the title? As the purpose of that draft
>> >> >>> is to establish which particular parameters will be used.
>> >> >>> My suggestions are:
>> >> >>> TCMTF - negotiation signalling
>> >> >>> TCMTF - negotiation process
>> >> >>> TCMTF - parameter signalling
>> >> >>> Or something along those lines?
>> >> >>> Mirko
>> >> >>>
>> >> >>> -----Original Message-----
>> >> >>> From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On
>> >> >>> Behalf Of Jose Saldana
>> >> >>> Sent: Wednesday, June 5, 2013 12:56 PM
>> >> >>> To: tcmtf@ietf.org
>> >> >>> Cc: tsv-area@ietf.org; spencerdawkins.ietf@gmail.com; 'ken
>> >> >>> carlberg'; Martin Stiemerling
>> >> >>> Subject: [tcmtf] TCMTF: Documents to be generated. Small
>> >> >>> modification
>> >> >>>
>> >> >>> In the conf-call of yesterday it was also clear that for the IETF
>> >> >>> it is better to split Document A into two documents:
>> >> >>>
>> >> >>> - The "TCMTF reference model" (1): the protocol stack and
>scenarios.
>> >> >>> It should be said that each protocol at each layer will use its
>> >> >>> own signaling mechanisms.
>> >> >>>
>> >> >>> - The "TCMTF-specific signaling": there are some things we will
>> >> >>> need to
>> >> >>> deploy:
>> >> >>>      - a negotiation mechanism (2) to decide the options to use
>> >> >>> at each layer (e.g. a mux and demux agree on using
>> ROHC+PPPMux+GRE)
>> >> >>>      - a mechanism to setup/release a TCMTF tunnel (3)between a
>> >> >>> multiplexer and a de-multiplexer
>> >> >>>
>> >> >>>
>> >> >>> The current draft is the TCMTF "reference model", since it does
>> >> >>> not talk about specific signaling issues.
>> >> >>>
>> >> >>> By now, we don't have to propose the "TCMTF specific signaling".
>> >> >>> It would be something to be deployed if the Working Group is
>> created.
>> >> >>>
>> >> >>> This same idea was proposed by Ken Carlberg in February. The
>> >> >>> advantages of this new distribution of the documents are (quoting
>> >Ken):
>> >> >>>
>> >> >>>> One thing to keep in mind is that it is possible that (2) and
>> >> >>>> (3)
>> >> >>>> (below) can change over time and yet (1) (the reference model)
>> >> >>>> does not, then it may be best to separate (1) from the other
>items.
>> >> >>>
>> >> >>>> a more encompassing architecture or framework that would include
>> >> >>>> sample scenarios upon which your deliverables A & B are aimed
>>at?
>> >> >>>> My impression is that you may want to point the reader of
>> >> >>>> documents A & B to the same reference model, and instead of
>> >> >>>> repeating the same text, it may be helpful to separate this into
>> >> >>>> a separate
>> >document.
>> >> >>>
>> >> >>>
>> >> >>> Once discussed, I would create a new charter proposal including
>> >> >>> these changes.
>> >> >>>
>> >> >>>
>> >> >>> Do you like these short names for the documents?
>> >> >>>
>> >> >>> - "TCMTF reference model".
>> >> >>> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>> >> >>>
>> >> >>> - "TCMTF-specific signaling". Future work
>> >> >>>
>> >> >>> - "TCMTF recommendations".
>> >> >>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>> >> >>>
>> >> >>>
>> >> >>> Your feedback will be welcome. Thanks!
>> >> >>>
>> >> >>> Jose
>> >> >>>
>> >> >>>> -----Mensaje original-----
>> >> >>>> De: ken carlberg [mailto:carlberg@g11.org.uk] Enviado el:
>> >> >>>> martes,
>> >> >>>> 05 de marzo de 2013 17:07
>> >> >>>> Para: jsaldana@unizar.es
>> >> >>>> CC: 'ken carlberg'; tcmtf@ietf.org; tsv-area@ietf.org
>> >> >>>> Asunto: Re: [tcmtf] About the possibility of having a BOF about
>> >> >>>> TCMTF in
>> >> >>>> IETF87
>> >> >>>>
>> >> >>>> Hola Jose,
>> >> >>>>
>> >> >>>> Thanks for the expanded explanation, and again, apologies for
>> >> >>>> the tardy repsonse.  Its helpful to understand that document A
>> >> >>>> and B are sequential
>> >> >>> to
>> >> >>>> each other.  One thing to keep in mind is that if its possible
>> >> >>>> that
>> >> >>>> 2 and
>> >> >>> 3
>> >> >>>> (below) can change over time and yet 1 (the reference model)
>> >> >>>> does not, then it may be best to separate 1 from the other
>>items.
>> >> >>>>
>> >> >>>> as for what you outline as a discussion point for future work,
>> >> >>>> it seems
>> >> >>> fine.  I
>> >> >>>> just have a personal bias that if you have a clear idea of the
>> >> >>>> things
>> >> >>> you'd like
>> >> >>>> to accomplish in the future, then having a requirements document
>> >> >>>> would be helpful to focus those thoughts without having to have
>> >> >>>> one particular solution.  But that's a discussion point that
>> >> >>>> could be brought up during
>> >> >>> the
>> >> >>>> BoF, or sometime afterwards.
>> >> >>>>
>> >> >>>> cheers,
>> >> >>>>
>> >> >>>> -ken
>> >> >>>>
>> >> >>>>
>> >> >>>>> A main document (A) in which we explain the method, the
>> >> >>>>> scenarios and the minimum signaling issues in order to make it
>> >> >>>>> work. The idea is that document
>> >> >>>>> (A) would be self-contained. Since we are not defining new
>> >> >>>>> protocols
>> >> >>> (i.e.
>> >> >>>>> already existing compressing, multiplexing and tunneling
>> >> >>>>> protocols are to be used), we understand that this can be done
>> >> >>>>> in a single
>> >> >>>> document.
>> >> >>>>> It would
>> >> >>>>> include:
>> >> >>>>>
>> >> >>>>> 1- Protocol stack (it would be the "reference model")
>> >> >>>>> 2- a negotiation mechanism to decide the options to use at each
>> >> >>>>> layer
>> >> >>>>> 3- a mechanism to setup/release a tunnel between a multiplexer
>> >> >>>>> and a de-multiplexer
>> >> >>>>>
>> >> >>>>> Of course, another approach could be separating 1 from 2&3.
>> >> >>>>> However, we think this is not necessary since the method is not
>> >> >>>>> too
>> >> >>>> complicated.
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> Document (B) would only contain recommendations of how to
>> >> >>>>> better use the method proposed in document (A), i.e.,
>> >> >>>>> classification and maximum
>> >> >>>> delays.
>> >> >>>>>
>> >> >>>>> So clearly document (B) would totally depend on the reference
>> >> >>>>> model of document (A).
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> The idea of point 9 is to talk about some other interesting
>> >> >>>>> ideas which are considered as "future work":
>> >> >>>>> - a mechanism for a multiplexer to discover a de-multiplexer
>> >> >>>>> - mechanism to select an optimal multiplexer and a
>> >> >>>>> de-multiplexer when there are more than one muxer/de-muxer
>> for
>> >> >>>>> a flow
>> >> >>>>> - dynamically applying TCMTF
>> >> >>>>> - etc.
>> >> >>>>>
>> >> >>>>> What do you think?
>> >> >>>>>
>> >> >>>>> Thanks again for your feedback. Thinking and explaining things
>> >> >>>>> is always a good exercise!
>> >> >>>>>
>> >> >>>>> Jose
>> >> >>>>>
>> >> >>>>>> -----Mensaje original-----
>> >> >>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>> >> >>>>>> nombre de ken carlberg Enviado el: mi=E9rcoles, 27 de febrero =
de
>> >> >>>>>> 2013
>> >> >>>>>> 16:23
>> >> >>>>>> Para: jsaldana@unizar.es
>> >> >>>>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
>> >> >>>>>> Asunto: Re: [tcmtf] About the possibility of having a BOF
>> >> >>>>>> about TCMTF in
>> >> >>>>>> IETF87
>> >> >>>>>>
>> >> >>>>>> Hola Jose,
>> >> >>>>>>
>> >> >>>>>> sorry for the tardy reply.  The altered text below is helpful,
>> >> >>>> thanks.
>> >> >>>>>>
>> >> >>>>>> With respect to your candidate deliverables, it appears that
>> >> >>>>>> you have
>> >> >>>>> listed
>> >> >>>>>> two for the proposed group: (A) a document that describes
>> >> >>>>>> options and negotiation mechanisms, and (B) a document
>> >> >>>>>> describing
>> >> >>>> recommendations
>> >> >>>>>> of which packet types should be multiplexed and a list fo
>> >> >>>>>> traffic
>> >> >>>>> classification
>> >> >>>>>> methods.  Have you considered a third document that presents a
>> >> >>>>>> more encompassing architecture or framework that would
>> include
>> >> >>>>>> sample scenarios upon which your deliverables A & B are aimed
>> at?
>> >> >>>>>> My impression
>> >> >>>>> is
>> >> >>>>>> that you may want to point the reader of documents A & B to
>> >> >>>>>> the same reference model, and instead of repeating the same
>> >> >>>>>> text, it may be helpful to separate this into a separate
>document.
>> >> >>>>>>
>> >> >>>>>> Also, would section 9 of your proposed charter lead one to
>> >> >>>>>> consider a requirements document?  Many times, new groups
>> >> >>>>>> start with a requirements document, but since you have a good
>> >> >>>>>> focus of what you want to accomplish, perhaps your last
>> >> >>>>>> deliverable could be a requirements document that would guide
>> any future work.
>> >> >>>>>>
>> >> >>>>>> -ken
>> >> >>>>>>
>> >> >>>>>> ps, I don't want to advocate more work, but rather just have
>> >> >>>>>> you consider other possibilities (and feel free to shoot them
>> >> >>>>>> down
>> >> >>>>>> :-)
>> >> >>>>>>
>> >> >>>>>>
>> >> >>>>>> On Feb 22, 2013, at 5:39 AM, Jose Saldana <jsaldana@unizar.es>
>> >> >> wrote:
>> >> >>>>>>
>> >> >>>>>>> Hi Ken,
>> >> >>>>>>>
>> >> >>>>>>> Sorry for the delay. I think you are talking about Paragraph
>>5:
>> >> >>>>>>>
>> >> >>>>>>> 5. So the first objective of this group is to specify the
>> >> >>>>>>> protocol stack for tunneling, compressing and multiplexing
>> >> >>>>>>> traffic flows (TCMTF). Since standard protocols are being
>> >> >>>>>>> used at each layer, the signaling methods of those protocols
>> >> >>>>>>> will be
>> >used.
>> >> >>>>>>> Interactions with the Working Groups and Areas in which these
>> >> >>>>>>> protocols are developed can be expected. However, the
>> >> >> development
>> >> >>>>>>> of new compressing, multiplexing or tunneling protocols is
>> >> >>>>>>> not an objective of this Working Group. In addition, since
>> >> >>>>>>> the current RFC 4170 would be
>> >> >>>>>> considered as one of the options, this RFC could be obsoleted.
>> >> >>>>>>>
>> >> >>>>>>> Perhaps this is a bit confusing. When we say "at each layer",
>> >> >>>>>>> we are talking about "tunneling, compressing and
>>multiplexing"
>> >layers.
>> >> >>>>>>> Perhaps this can be a bit confusing. What about this?:
>> >> >>>>>>>
>> >> >>>>>>> 5. So the first objective of this group is to specify the
>> >> >>>>>>> protocol stack for tunneling, compressing and multiplexing
>> >> >>>>>>> traffic flows (TCMTF). Since standard protocols are being
>> >> >>>>>>> used for tunneling, compressing and multiplexing layers, the
>> >> >>>>>>> signaling methods of those
>> >> >>>>>> protocols will be used.
>> >> >>>>>>> Interactions with the Working Groups and Areas in which these
>> >> >>>>>>> protocols are developed can be expected. However, the
>> >> >> development
>> >> >>>> of
>> >> >>>>>>> new compressing, multiplexing or tunneling protocols is not
>> >> >>>>>>> an objective of this Working Group. In addition, since the
>> >> >>>>>>> current RFC
>> >> >>>>>>> 4170 would be considered as one of the options, this RFC
>> >> >>>>>>> could be
>> >> >>>>>> obsoleted.
>> >> >>>>>>>
>> >> >>>>>>> Is this what you were asking?
>> >> >>>>>>>
>> >> >>>>>>> Thanks for your feedback.
>> >> >>>>>>>
>> >> >>>>>>> Jose
>> >> >>>>>>>
>> >> >>>>>>>> -----Mensaje original-----
>> >> >>>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org]
>> >> >>>>>>>> En nombre de ken carlberg Enviado el: martes, 19 de febrero
>> >> >>>>>>>> de
>> >> >>>>>>>> 2013
>> >> >>>>>>>> 14:17
>> >> >>>>>>>> Para: jsaldana@unizar.es
>> >> >>>>>>>> CC: tcmtf@ietf.org; tsv-area@ietf.org
>> >> >>>>>>>> Asunto: Re: [tcmtf] About the possibility of having a BOF
>> >> >>>>>>>> about TCMTF in
>> >> >>>>>>>> IETF87
>> >> >>>>>>>>
>> >> >>>>>>>> Hola Jose,
>> >> >>>>>>>>
>> >> >>>>>>>> could you expand a bit more on your text in the proposed
>> >> >>>>>>>> charter regarding "signaling methods".  Are you speaking in
>> >> >>>>>>>> the more general context of information stored in headers of
>> >> >>>>>>>> various protocol up and down the stack
>> >> >>>>>>> (ie,
>> >> >>>>>>>> layers 3, 4, and 5/app)?  Or, are you  speaking of
>> >> >>>>>>>> concurrent resource signaling protocols like RSVP/RSVP-TE,
>> >> >>>>>>>> or path establishment protocols
>> >> >>>>>>> like
>> >> >>>>>>>> MPLS?  Or, some combination of both?
>> >> >>>>>>>>
>> >> >>>>>>>> -ken
>> >> >>>>>>>>
>> >> >>>>>>>> _______________________________________________
>> >> >>>>>>>> tcmtf mailing list
>> >> >>>>>>>> tcmtf@ietf.org
>> >> >>>>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >> >>>>>>>
>> >> >>>>>>
>> >> >>>>>> _______________________________________________
>> >> >>>>>> tcmtf mailing list
>> >> >>>>>> tcmtf@ietf.org
>> >> >>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >> >>>>>
>> >> >>>
>> >> >>>
>> >> >>> _______________________________________________
>> >> >>> tcmtf mailing list
>> >> >>> tcmtf@ietf.org
>> >> >>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >> >>> _______________________________________________
>> >> >>> tcmtf mailing list
>> >> >>> tcmtf@ietf.org
>> >> >>> https://www.ietf.org/mailman/listinfo/tcmtf
>> >> >>
>> >> >>
>> >> >> ________________________________
>> >> >>
>> >> >> Este mensaje se dirige exclusivamente a su destinatario. Puede
>> >> >> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo
>> >> >> electr=F3nico en el enlace situado m=E1s abajo.
>> >> >> This message is intended exclusively for its addressee. We only
>> >> >> send and receive email on the basis of the terms set out at:
>> >> >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> >> >> _______________________________________________
>> >> >> tcmtf mailing list
>> >> >> tcmtf@ietf.org
>> >> >> https://www.ietf.org/mailman/listinfo/tcmtf
>> >> >
>> >> > _______________________________________________
>> >> > tcmtf mailing list
>> >> > tcmtf@ietf.org
>> >> > https://www.ietf.org/mailman/listinfo/tcmtf
>> >>
>> >>
>> >> --
>> >> "Esta vez no fallaremos, Doctor Infierno"
>> >>
>> >> Dr Diego R. Lopez
>> >> Telefonica I+D
>> >> http://people.tid.es/diego.lopez/
>> >>
>> >> e-mail: diego@tid.es
>> >> Tel:    +34 913 129 041
>> >> Mobile: +34 682 051 091
>> >> -----------------------------------------
>> >>
>> >>
>> >> ________________________________
>> >>
>> >> Este mensaje se dirige exclusivamente a su destinatario. Puede
>> >> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo elect=
r=F3nico
>> >> en el enlace situado m=E1s abajo.
>> >> This message is intended exclusively for its addressee. We only send
>> >> and receive email on the basis of the terms set out at:
>> >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> >> _______________________________________________
>> >> 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
>


________________________________

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

From Mirko.Suznjevic@fer.hr  Sun Jun  9 12:38:50 2013
Return-Path: <Mirko.Suznjevic@fer.hr>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3B9721F9485 for <tcmtf@ietfa.amsl.com>; Sun,  9 Jun 2013 12:38:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0PJaXdpQPhbn for <tcmtf@ietfa.amsl.com>; Sun,  9 Jun 2013 12:38:40 -0700 (PDT)
Received: from mail.fer.hr (mail.fer.hr [161.53.72.233]) by ietfa.amsl.com (Postfix) with ESMTP id 26CA721F9425 for <tcmtf@ietf.org>; Sun,  9 Jun 2013 12:38:39 -0700 (PDT)
Received: from MAIL4.fer.hr ([2002:a135:48ea::a135:48ea]) by MAIL.fer.hr ([2002:a135:48e9::a135:48e9]) with mapi id 14.02.0342.003; Sun, 9 Jun 2013 21:38:37 +0200
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: New version of TCMTF reccomendations draft
Thread-Index: Ac5lSO8sBb23s6R4QWOCzxUjaNJPCA==
Date: Sun, 9 Jun 2013 19:38:36 +0000
Message-ID: <E004A7C54DE04F4BB87DB9F32308DA5C0C068D@MAIL4.fer.hr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [88.207.34.67]
Content-Type: multipart/alternative; boundary="_000_E004A7C54DE04F4BB87DB9F32308DA5C0C068DMAIL4ferhr_"
MIME-Version: 1.0
Subject: [tcmtf] New version of TCMTF reccomendations draft
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jun 2013 19:38:50 -0000

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

Hello everybody,
I am creating a new version of the TCMTF - recommendations document. In thi=
s mail I will include all the changes which I am including in this version =
of the document. These changes were suggested on this mailing list as well =
as by some other sources.
Please if anyone has anything more to add say so now! Or wait till the next=
 version ;) I will submit the new version by 15.6.

Major changes:

1)      Briefly describe traffic flow identification problem (i.e., which f=
lows should be TCMTFed) and possible solutions

2)      Addition of  available traffic classification methods which can be =
used by TCMTF (i.e., when we know which flow can be TCMTFed assigning it to=
 a proper multiplexing period)

3)      Addition of limitations for non-real time services such as Web brow=
sing

4)      Description of the policies for multiplexing period and possible wa=
ys to measure delay

5)      Inclusion of the discussion regarding jitter buffers for VoIP and a=
s well to codec delay

6)      Modifying the suggested values for VoIP based on a user acceptance =
level, jitter buffers, and codec delay

7)      Addition of the summary section

Moderate changes:

1)      Improved definition of the multiplexing period

2)      Clarification of the latency values that can be added with TCMTF

Minor changes:

1)      Noting that these recommendations are mostly focused on low speed l=
inks as on high speed links the added delay should be only few ms

2)      Clarification of sentence: "Therefore, we neither take into account=
 services using an approach in which all the calculations are deployed in t=
he server, which sends a real-time video stream to the client."  In a way t=
hat it more clearly reflects the fact that we are not addressing the cloud =
based gaming services which basically stream video which has large packets

3)      Replacing "priority" with "delay sensitive class"

4)      Properly formalizing some terms: replacing "jitter" with "delay var=
iation" as defined in RFC 5481, and using the definition of QoE from RFC 63=
90
Also some other minor changes and typo corrections.

Thanks again to everyone who provided feedback!
Best regards,
Mirko Suznjevic


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
2">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* 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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:44111526;
	mso-list-type:hybrid;
	mso-list-template-ids:2036392930 68812817 68812825 68812827 68812815 68812=
825 68812827 68812815 68812825 68812827;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:756632370;
	mso-list-type:hybrid;
	mso-list-template-ids:1176549492 68812817 68812825 68812827 68812815 68812=
825 68812827 68812815 68812825 68812827;}
@list l1:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2
	{mso-list-id:1980838587;
	mso-list-type:hybrid;
	mso-list-template-ids:1306146518 68812817 68812825 68812827 68812815 68812=
825 68812827 68812815 68812825 68812827;}
@list l2:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"HR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Hello everybody,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">I am creating a new version of =
the TCMTF &#8211; recommendations document. In this mail I will include all=
 the changes which I am including in this version of the document. These ch=
anges were suggested on this mailing list
 as well as by some other sources.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Please if anyone has anything m=
ore to add say so now! Or wait till the next version ;) I will submit the n=
ew version by 15.6.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Major changes:<o:p></o:p></span=
></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">1)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Briefly describe traffi=
c flow identification problem (i.e., which flows should be TCMTFed) and pos=
sible solutions<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">2)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Addition of&nbsp; avail=
able traffic classification methods which can be used by TCMTF (i.e., when =
we know which flow can be TCMTFed assigning it to a proper multiplexing per=
iod)<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">3)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Addition of limitations=
 for non-real time services such as Web browsing<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">4)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Description of the poli=
cies for multiplexing period and possible ways to measure delay<o:p></o:p><=
/span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">5)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Inclusion of the discus=
sion regarding jitter buffers for VoIP and as well to codec delay<o:p></o:p=
></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">6)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Modifying the suggested=
 values for VoIP based on a user acceptance level, jitter buffers, and code=
c delay<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">7)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Addition of the summary=
 section<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Moderate changes:<o:p></o:p></s=
pan></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo4"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">1)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Improved definition of =
the multiplexing period<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo4"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">2)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Clarification of the la=
tency values that can be added with TCMTF<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Minor changes:<o:p></o:p></span=
></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo6"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">1)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Noting that these recom=
mendations are mostly focused on low speed links as on high speed links the=
 added delay should be only few ms<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo6"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">2)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Clarification of senten=
ce: &quot;Therefore, we neither take into account services using an approac=
h in which all the calculations are deployed in the server, which sends a r=
eal-time video stream to the client.&quot;&nbsp;
 In a way that it more clearly reflects the fact that we are not addressing=
 the cloud based gaming services which basically stream video which has lar=
ge packets<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo6"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">3)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Replacing &#8220;priori=
ty&#8221; with &#8220;delay sensitive class&#8221;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo6"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">4)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Properly formalizing so=
me terms: replacing &#8220;jitter&#8221; with &#8220;delay variation&#8221;=
 as defined in RFC 5481, and using the definition of QoE from RFC 6390<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Also some other minor changes a=
nd typo corrections.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Thanks again to everyone who pr=
ovided feedback!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Best regards,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Mirko Suznjevic<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_E004A7C54DE04F4BB87DB9F32308DA5C0C068DMAIL4ferhr_--

From navajas@unizar.es  Mon Jun 10 08:01:25 2013
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA39F21F9643 for <tcmtf@ietfa.amsl.com>; Mon, 10 Jun 2013 08:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sZpttjQgrxNd for <tcmtf@ietfa.amsl.com>; Mon, 10 Jun 2013 08:01:21 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id E3C3D21F966B for <tcmtf@ietf.org>; Mon, 10 Jun 2013 08:01:10 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5AF0hx7002652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Mon, 10 Jun 2013 17:00:44 +0200
Message-ID: <51B5EA1C.20209@unizar.es>
Date: Mon, 10 Jun 2013 17:00:44 +0200
From: =?ISO-8859-15?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <E004A7C54DE04F4BB87DB9F32308DA5C0C068D@MAIL4.fer.hr>
In-Reply-To: <E004A7C54DE04F4BB87DB9F32308DA5C0C068D@MAIL4.fer.hr>
Content-Type: multipart/alternative; boundary="------------030103080603090202070501"
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] New version of TCMTF reccomendations draft
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 15:01:25 -0000

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

Mirko,
I thank you for the changes scheme. I have seen better the improvements.
I agree with these changes.

Julián Fernández-Navajas

  El 09/06/2013 21:38, Mirko Su¸njevic' escribió:
>
> Hello everybody,
>
> I am creating a new version of the TCMTF -- recommendations document. 
> In this mail I will include all the changes which I am including in 
> this version of the document. These changes were suggested on this 
> mailing list as well as by some other sources.
>
> Please if anyone has anything more to add say so now! Or wait till the 
> next version ;) I will submit the new version by 15.6.
>
> Major changes:
>
> 1)Briefly describe traffic flow identification problem (i.e., which 
> flows should be TCMTFed) and possible solutions
>
> 2)Addition of  available traffic classification methods which can be 
> used by TCMTF (i.e., when we know which flow can be TCMTFed assigning 
> it to a proper multiplexing period)
>
> 3)Addition of limitations for non-real time services such as Web browsing
>
> 4)Description of the policies for multiplexing period and possible 
> ways to measure delay
>
> 5)Inclusion of the discussion regarding jitter buffers for VoIP and as 
> well to codec delay
>
> 6)Modifying the suggested values for VoIP based on a user acceptance 
> level, jitter buffers, and codec delay
>
> 7)Addition of the summary section
>
> Moderate changes:
>
> 1)Improved definition of the multiplexing period
>
> 2)Clarification of the latency values that can be added with TCMTF
>
> Minor changes:
>
> 1)Noting that these recommendations are mostly focused on low speed 
> links as on high speed links the added delay should be only few ms
>
> 2)Clarification of sentence: "Therefore, we neither take into account 
> services using an approach in which all the calculations are deployed 
> in the server, which sends a real-time video stream to the client."  
> In a way that it more clearly reflects the fact that we are not 
> addressing the cloud based gaming services which basically stream 
> video which has large packets
>
> 3)Replacing "priority" with "delay sensitive class"
>
> 4)Properly formalizing some terms: replacing "jitter" with "delay 
> variation" as defined in RFC 5481, and using the definition of QoE 
> from RFC 6390
>
> Also some other minor changes and typo corrections.
>
> Thanks again to everyone who provided feedback!
>
> Best regards,
>
> Mirko Suznjevic
>
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-15"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Mirko,<br>
      I thank you for the changes scheme. I have seen better the
      improvements.<br>
      I agree with these changes.<br>
      <br>
      Julián Fernández-Navajas<br>
      <br>
       El 09/06/2013 21:38, Mirko Su¸njevi&#263; escribió:<br>
    </div>
    <blockquote
      cite="mid:E004A7C54DE04F4BB87DB9F32308DA5C0C068D@MAIL4.fer.hr"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-15">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* 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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:44111526;
	mso-list-type:hybrid;
	mso-list-template-ids:2036392930 68812817 68812825 68812827 68812815 68812825 68812827 68812815 68812825 68812827;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:756632370;
	mso-list-type:hybrid;
	mso-list-template-ids:1176549492 68812817 68812825 68812827 68812815 68812825 68812827 68812815 68812825 68812827;}
@list l1:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2
	{mso-list-id:1980838587;
	mso-list-type:hybrid;
	mso-list-template-ids:1306146518 68812817 68812825 68812827 68812815 68812825 68812827 68812815 68812825 68812827;}
@list l2:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span lang="EN-GB">Hello everybody,<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB">I am creating a new
            version of the TCMTF &#8211; recommendations document. In this
            mail I will include all the changes which I am including in
            this version of the document. These changes were suggested
            on this mailing list as well as by some other sources.<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB">Please if anyone has
            anything more to add say so now! Or wait till the next
            version ;) I will submit the new version by 15.6.<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB">Major changes:<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l2 level1 lfo2"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">1)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Briefly
            describe traffic flow identification problem (i.e., which
            flows should be TCMTFed) and possible solutions<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l2 level1 lfo2"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">2)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Addition
            of  available traffic classification methods which can be
            used by TCMTF (i.e., when we know which flow can be TCMTFed
            assigning it to a proper multiplexing period)<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l2 level1 lfo2"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">3)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Addition
            of limitations for non-real time services such as Web
            browsing<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l2 level1 lfo2"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">4)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Description
            of the policies for multiplexing period and possible ways to
            measure delay<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l2 level1 lfo2"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">5)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Inclusion
            of the discussion regarding jitter buffers for VoIP and as
            well to codec delay<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l2 level1 lfo2"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">6)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Modifying
            the suggested values for VoIP based on a user acceptance
            level, jitter buffers, and codec delay<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l2 level1 lfo2"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">7)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Addition
            of the summary section<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB">Moderate changes:<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo4"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">1)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Improved
            definition of the multiplexing period<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo4"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">2)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Clarification
            of the latency values that can be added with TCMTF<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB">Minor changes:<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l1 level1 lfo6"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">1)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Noting
            that these recommendations are mostly focused on low speed
            links as on high speed links the added delay should be only
            few ms<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l1 level1 lfo6"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">2)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Clarification
            of sentence: "Therefore, we neither take into account
            services using an approach in which all the calculations are
            deployed in the server, which sends a real-time video stream
            to the client."  In a way that it more clearly reflects the
            fact that we are not addressing the cloud based gaming
            services which basically stream video which has large
            packets<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l1 level1 lfo6"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">3)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Replacing
            &#8220;priority&#8221; with &#8220;delay sensitive class&#8221;<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l1 level1 lfo6"><!--[if !supportLists]--><span
            lang="EN-GB"><span style="mso-list:Ignore">4)<span
                style="font:7.0pt &quot;Times New Roman&quot;">     
              </span></span></span><!--[endif]--><span lang="EN-GB">Properly
            formalizing some terms: replacing &#8220;jitter&#8221; with &#8220;delay
            variation&#8221; as defined in RFC 5481, and using the definition
            of QoE from RFC 6390<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB">Also some other minor
            changes and typo corrections.<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB">Thanks again to everyone
            who provided feedback!<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB">Best regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB">Mirko Suznjevic<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
tcmtf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tcmtf">https://www.ietf.org/mailman/listinfo/tcmtf</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------030103080603090202070501--

From jsaldana@unizar.es  Tue Jun 11 02:21:15 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 058AD21F949F for <tcmtf@ietfa.amsl.com>; Tue, 11 Jun 2013 02:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2bEA+0TUKXXo for <tcmtf@ietfa.amsl.com>; Tue, 11 Jun 2013 02:21:09 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 4E0A321F949D for <tcmtf@ietf.org>; Tue, 11 Jun 2013 02:21:03 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5B9Kqau028182; Tue, 11 Jun 2013 11:20:53 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "=?iso-8859-2?Q?'Mirko_Su=BEnjevi=E6'?=" <Mirko.Suznjevic@fer.hr>
References: <E004A7C54DE04F4BB87DB9F32308DA5C0C068D@MAIL4.fer.hr>
In-Reply-To: <E004A7C54DE04F4BB87DB9F32308DA5C0C068D@MAIL4.fer.hr>
Date: Tue, 11 Jun 2013 11:21:00 +0200
Organization: Universidad de Zaragoza
Message-ID: <00b701ce6684$fd5d7600$f8186200$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B8_01CE6695.C0E64600"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH8xWpOcmsXCuK0qvisrv7U5MFiCpjTfRYw
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] New version of TCMTF reccomendations draft
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jun 2013 09:21:15 -0000

This is a multipart message in MIME format.

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

Mirko,

=20

I agree with your suggestions (great job!)

=20

Just a minor comment:

=20

Are you considering the idea of multiplexing ACKs flows? As we =
discussed,
when you are e.g. downloading a file, a laptop may send 125 ACks per =
second.
And they have a lot of redundant headers. Perhaps we could just announce =
the
idea. Of course, ACKs of a download are not "real-time", but if you add =
too
much delay, the throughput can be reduced. This idea was suggested by
Michael some weeks ago:
<http://www.ietf.org/mail-archive/web/tcmtf/current/msg00235.html>
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00235.html

=20

We could perhaps announce this in "Addition of limitations for non-real =
time
services such as Web browsing": we could also talk about the problem of
additional delays in the ACKs when you are downloading a file, not only =
in
web browsing.

=20

What do you think?

=20

Jose

=20

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
Mirko Su=BEnjevic
Enviado el: domingo, 09 de junio de 2013 21:39
Para: tcmtf@ietf.org
Asunto: [tcmtf] New version of TCMTF reccomendations draft

=20

Hello everybody,

I am creating a new version of the TCMTF - recommendations document. In =
this
mail I will include all the changes which I am including in this version =
of
the document. These changes were suggested on this mailing list as well =
as
by some other sources.

Please if anyone has anything more to add say so now! Or wait till the =
next
version ;) I will submit the new version by 15.6.

=20

Major changes:

1)      Briefly describe traffic flow identification problem (i.e., =
which
flows should be TCMTFed) and possible solutions

2)      Addition of  available traffic classification methods which can =
be
used by TCMTF (i.e., when we know which flow can be TCMTFed assigning it =
to
a proper multiplexing period)

3)      Addition of limitations for non-real time services such as Web
browsing

4)      Description of the policies for multiplexing period and possible
ways to measure delay

5)      Inclusion of the discussion regarding jitter buffers for VoIP =
and as
well to codec delay

6)      Modifying the suggested values for VoIP based on a user =
acceptance
level, jitter buffers, and codec delay

7)      Addition of the summary section

=20

Moderate changes:

1)      Improved definition of the multiplexing period

2)      Clarification of the latency values that can be added with TCMTF

=20

Minor changes:

1)      Noting that these recommendations are mostly focused on low =
speed
links as on high speed links the added delay should be only few ms

2)      Clarification of sentence: "Therefore, we neither take into =
account
services using an approach in which all the calculations are deployed in =
the
server, which sends a real-time video stream to the client."  In a way =
that
it more clearly reflects the fact that we are not addressing the cloud =
based
gaming services which basically stream video which has large packets

3)      Replacing "priority" with "delay sensitive class"

4)      Properly formalizing some terms: replacing "jitter" with "delay
variation" as defined in RFC 5481, and using the definition of QoE from =
RFC
6390

Also some other minor changes and typo corrections.

=20

Thanks again to everyone who provided feedback!

Best regards,

Mirko Suznjevic

=20


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-2"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EstiloCorreo18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:44111526;
	mso-list-type:hybrid;
	mso-list-template-ids:2036392930 68812817 68812825 68812827 68812815 =
68812825 68812827 68812815 68812825 68812827;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:756632370;
	mso-list-type:hybrid;
	mso-list-template-ids:1176549492 68812817 68812825 68812827 68812815 =
68812825 68812827 68812815 68812825 68812827;}
@list l1:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2
	{mso-list-id:1980838587;
	mso-list-type:hybrid;
	mso-list-template-ids:1306146518 68812817 68812825 68812827 68812815 =
68812825 68812827 68812815 68812825 68812827;}
@list l2:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Mirko,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>I agree =
with your suggestions (great job!)<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'>Just a =
minor comment:<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'>Are you =
considering the idea of multiplexing ACKs flows? As we discussed, when =
you are e.g. downloading a file, a laptop may send 125 ACks per second. =
And they have a lot of redundant headers. Perhaps we could just announce =
the idea. Of course, ACKs of a download are not &#8220;real-time&#8221;, =
but if you add too much delay, the throughput can be reduced. This idea =
was suggested by Michael some weeks ago: </span><a =
href=3D"http://www.ietf.org/mail-archive/web/tcmtf/current/msg00235.html"=
><span =
lang=3DEN-US>http://www.ietf.org/mail-archive/web/tcmtf/current/msg00235.=
html</span></a><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>We could =
perhaps announce this in &#8220;Addition of limitations for non-real =
time services such as Web browsing&#8221;: we could also talk about the =
problem of additional delays in the ACKs when you are downloading a =
file, not only in web browsing.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>What do you =
think?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] <b>En nombre de =
</b>Mirko Su=BEnjevic<br><b>Enviado el:</b> domingo, 09 de junio de 2013 =
21:39<br><b>Para:</b> tcmtf@ietf.org<br><b>Asunto:</b> [tcmtf] New =
version of TCMTF reccomendations =
draft<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-GB>Hello everybody,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB>I am creating a new version of the =
TCMTF &#8211; recommendations document. In this mail I will include all =
the changes which I am including in this version of the document. These =
changes were suggested on this mailing list as well as by some other =
sources.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB>Please if anyone has anything more to add say so now! Or =
wait till the next version ;) I will submit the new version by =
15.6.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB>Major changes:<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l2 level1 =
lfo2'><![if !supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>1)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Briefly describe =
traffic flow identification problem (i.e., which flows should be =
TCMTFed) and possible solutions<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l2 level1 =
lfo2'><![if !supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>2)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Addition of&nbsp; =
available traffic classification methods which can be used by TCMTF =
(i.e., when we know which flow can be TCMTFed assigning it to a proper =
multiplexing period)<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if =
!supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>3)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Addition of =
limitations for non-real time services such as Web =
browsing<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if =
!supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>4)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Description of the =
policies for multiplexing period and possible ways to measure =
delay<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if =
!supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>5)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Inclusion of the =
discussion regarding jitter buffers for VoIP and as well to codec =
delay<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if =
!supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>6)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Modifying the =
suggested values for VoIP based on a user acceptance level, jitter =
buffers, and codec delay<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l2 level1 =
lfo2'><![if !supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>7)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Addition of the =
summary section<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB>Moderate changes:<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo4'><![if !supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>1)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Improved definition of =
the multiplexing period<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo4'><![if =
!supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>2)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Clarification of the =
latency values that can be added with TCMTF<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB>Minor =
changes:<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l1 level1 lfo6'><![if =
!supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>1)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Noting that these =
recommendations are mostly focused on low speed links as on high speed =
links the added delay should be only few ms<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l1 level1 =
lfo6'><![if !supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>2)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Clarification of =
sentence: &quot;Therefore, we neither take into account services using =
an approach in which all the calculations are deployed in the server, =
which sends a real-time video stream to the client.&quot;&nbsp; In a way =
that it more clearly reflects the fact that we are not addressing the =
cloud based gaming services which basically stream video which has large =
packets<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l1 level1 lfo6'><![if =
!supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>3)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Replacing =
&#8220;priority&#8221; with &#8220;delay sensitive =
class&#8221;<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l1 level1 lfo6'><![if =
!supportLists]><span lang=3DEN-GB><span =
style=3D'mso-list:Ignore'>4)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-GB>Properly formalizing =
some terms: replacing &#8220;jitter&#8221; with &#8220;delay =
variation&#8221; as defined in RFC 5481, and using the definition of QoE =
from RFC 6390<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB>Also some other minor changes and typo =
corrections.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB>Thanks again to everyone who provided =
feedback!<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-GB>Best regards,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB>Mirko =
Suznjevic<o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><p class=3DMsoNormal><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_00B8_01CE6695.C0E64600--


From Mirko.Suznjevic@fer.hr  Tue Jun 11 03:58:07 2013
Return-Path: <Mirko.Suznjevic@fer.hr>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB81521F9458 for <tcmtf@ietfa.amsl.com>; Tue, 11 Jun 2013 03:58:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.05
X-Spam-Level: 
X-Spam-Status: No, score=-2.05 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-qyD7tLTXtD for <tcmtf@ietfa.amsl.com>; Tue, 11 Jun 2013 03:58:03 -0700 (PDT)
Received: from mail.fer.hr (mail.fer.hr [161.53.72.233]) by ietfa.amsl.com (Postfix) with ESMTP id 47FDF21F93B9 for <tcmtf@ietf.org>; Tue, 11 Jun 2013 03:58:01 -0700 (PDT)
Received: from MAIL4.fer.hr ([2002:a135:48ea::a135:48ea]) by MAIL.fer.hr ([2002:a135:48e9::a135:48e9]) with mapi id 14.02.0342.003; Tue, 11 Jun 2013 12:57:57 +0200
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: "jsaldana@unizar.es" <jsaldana@unizar.es>
Thread-Topic: [tcmtf] New version of TCMTF reccomendations draft
Thread-Index: Ac5lSO8sBb23s6R4QWOCzxUjaNJPCABK0nkAAAdx7AA=
Date: Tue, 11 Jun 2013 10:57:56 +0000
Message-ID: <E004A7C54DE04F4BB87DB9F32308DA5C0C0831@MAIL4.fer.hr>
References: <E004A7C54DE04F4BB87DB9F32308DA5C0C068D@MAIL4.fer.hr> <00b701ce6684$fd5d7600$f8186200$@unizar.es>
In-Reply-To: <00b701ce6684$fd5d7600$f8186200$@unizar.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.53.19.114]
Content-Type: multipart/alternative; boundary="_000_E004A7C54DE04F4BB87DB9F32308DA5C0C0831MAIL4ferhr_"
MIME-Version: 1.0
Cc: "tcmtf@ietf.org" <tcmtf@ietf.org>
Subject: Re: [tcmtf] New version of TCMTF reccomendations draft
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jun 2013 10:58:07 -0000

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

Hey all,
I have not considered adding anything regarding multiplexing ACKs for this =
version, because when i was rereading all the mails in the list it seemed t=
o me that the ACK problem was not completely resolved and that consensus wa=
s not created on this issue.
But i think we can do something regarding that as well! And yes that sectio=
n could be good for ACKs problem.
Cheers!
Mirko

From: Jose Saldana [mailto:jsaldana@unizar.es]
Sent: Tuesday, June 11, 2013 11:21 AM
To: Mirko Su=BEnjevi=E6
Cc: tcmtf@ietf.org
Subject: RE: [tcmtf] New version of TCMTF reccomendations draft

Mirko,

I agree with your suggestions (great job!)

Just a minor comment:

Are you considering the idea of multiplexing ACKs flows? As we discussed, w=
hen you are e.g. downloading a file, a laptop may send 125 ACks per second.=
 And they have a lot of redundant headers. Perhaps we could just announce t=
he idea. Of course, ACKs of a download are not "real-time", but if you add =
too much delay, the throughput can be reduced. This idea was suggested by M=
ichael some weeks ago: http://www.ietf.org/mail-archive/web/tcmtf/current/m=
sg00235.html

We could perhaps announce this in "Addition of limitations for non-real tim=
e services such as Web browsing": we could also talk about the problem of a=
dditional delays in the ACKs when you are downloading a file, not only in w=
eb browsing.

What do you think?

Jose

De: tcmtf-bounces@ietf.org<mailto:tcmtf-bounces@ietf.org> [mailto:tcmtf-bou=
nces@ietf.org] En nombre de Mirko Su=BEnjevic
Enviado el: domingo, 09 de junio de 2013 21:39
Para: tcmtf@ietf.org<mailto:tcmtf@ietf.org>
Asunto: [tcmtf] New version of TCMTF reccomendations draft

Hello everybody,
I am creating a new version of the TCMTF - recommendations document. In thi=
s mail I will include all the changes which I am including in this version =
of the document. These changes were suggested on this mailing list as well =
as by some other sources.
Please if anyone has anything more to add say so now! Or wait till the next=
 version ;) I will submit the new version by 15.6.

Major changes:

1)      Briefly describe traffic flow identification problem (i.e., which f=
lows should be TCMTFed) and possible solutions

2)      Addition of  available traffic classification methods which can be =
used by TCMTF (i.e., when we know which flow can be TCMTFed assigning it to=
 a proper multiplexing period)

3)      Addition of limitations for non-real time services such as Web brow=
sing

4)      Description of the policies for multiplexing period and possible wa=
ys to measure delay

5)      Inclusion of the discussion regarding jitter buffers for VoIP and a=
s well to codec delay

6)      Modifying the suggested values for VoIP based on a user acceptance =
level, jitter buffers, and codec delay

7)      Addition of the summary section

Moderate changes:

1)      Improved definition of the multiplexing period

2)      Clarification of the latency values that can be added with TCMTF

Minor changes:

1)      Noting that these recommendations are mostly focused on low speed l=
inks as on high speed links the added delay should be only few ms

2)      Clarification of sentence: "Therefore, we neither take into account=
 services using an approach in which all the calculations are deployed in t=
he server, which sends a real-time video stream to the client."  In a way t=
hat it more clearly reflects the fact that we are not addressing the cloud =
based gaming services which basically stream video which has large packets

3)      Replacing "priority" with "delay sensitive class"

4)      Properly formalizing some terms: replacing "jitter" with "delay var=
iation" as defined in RFC 5481, and using the definition of QoE from RFC 63=
90
Also some other minor changes and typo corrections.

Thanks again to everyone who provided feedback!
Best regards,
Mirko Suznjevic


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
2">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:44111526;
	mso-list-type:hybrid;
	mso-list-template-ids:2036392930 68812817 68812825 68812827 68812815 68812=
825 68812827 68812815 68812825 68812827;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:756632370;
	mso-list-type:hybrid;
	mso-list-template-ids:1176549492 68812817 68812825 68812827 68812815 68812=
825 68812827 68812815 68812825 68812827;}
@list l1:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2
	{mso-list-id:1980838587;
	mso-list-type:hybrid;
	mso-list-template-ids:1306146518 68812817 68812825 68812827 68812815 68812=
825 68812827 68812815 68812825 68812827;}
@list l2:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"HR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Hey all=
,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">I have =
not considered adding anything regarding multiplexing ACKs for this version=
, because when i was rereading all the mails in the list it seemed to me th=
at the ACK problem was not completely
 resolved and that consensus was not created on this issue.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">But i t=
hink we can do something regarding that as well! And yes that section could=
 be good for ACKs problem.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Cheers!=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Mirko<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" 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-GB" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Jose Saldana [mailto:jsaldana@unizar.es]
<br>
<b>Sent:</b> Tuesday, June 11, 2013 11:21 AM<br>
<b>To:</b> Mirko Su=BEnjevi=E6<br>
<b>Cc:</b> tcmtf@ietf.org<br>
<b>Subject:</b> RE: [tcmtf] New version of TCMTF reccomendations draft<o:p>=
</o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Mirko,<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">I agree=
 with your suggestions (great job!)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Just a =
minor comment:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Are you=
 considering the idea of multiplexing ACKs flows? As we discussed, when you=
 are e.g. downloading a file, a laptop may send 125 ACks per second. And th=
ey have a lot of redundant headers. Perhaps
 we could just announce the idea. Of course, ACKs of a download are not &#8=
220;real-time&#8221;, but if you add too much delay, the throughput can be =
reduced. This idea was suggested by Michael some weeks ago:
</span><span lang=3D"EN-GB"><a href=3D"http://www.ietf.org/mail-archive/web=
/tcmtf/current/msg00235.html">http://www.ietf.org/mail-archive/web/tcmtf/cu=
rrent/msg00235.html</a><span style=3D"color:#1F497D"><o:p></o:p></span></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">We coul=
d perhaps announce this in &#8220;Addition of limitations for non-real time=
 services such as Web browsing&#8221;: we could also talk about the problem=
 of additional delays in the ACKs when you are downloading
 a file, not only in web browsing.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">What do=
 you think?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Jose<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" 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-GB" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">De:</span></b><span la=
ng=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;">
<a href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a hr=
ef=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]
<b>En nombre de </b>Mirko Su=BEnjevic<br>
<b>Enviado el:</b> domingo, 09 de junio de 2013 21:39<br>
<b>Para:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tcmtf] New version of TCMTF reccomendations draft<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Hello everybody,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">I am creating a new version of =
the TCMTF &#8211; recommendations document. In this mail I will include all=
 the changes which I am including in this version of the document. These ch=
anges were suggested on this mailing list
 as well as by some other sources.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Please if anyone has anything m=
ore to add say so now! Or wait till the next version ;) I will submit the n=
ew version by 15.6.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Major changes:<o:p></o:p></span=
></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">1)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Briefly describe traffi=
c flow identification problem (i.e., which flows should be TCMTFed) and pos=
sible solutions<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">2)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Addition of&nbsp; avail=
able traffic classification methods which can be used by TCMTF (i.e., when =
we know which flow can be TCMTFed assigning it to a proper multiplexing per=
iod)<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">3)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Addition of limitations=
 for non-real time services such as Web browsing<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">4)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Description of the poli=
cies for multiplexing period and possible ways to measure delay<o:p></o:p><=
/span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">5)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Inclusion of the discus=
sion regarding jitter buffers for VoIP and as well to codec delay<o:p></o:p=
></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">6)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Modifying the suggested=
 values for VoIP based on a user acceptance level, jitter buffers, and code=
c delay<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l2 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">7)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Addition of the summary=
 section<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Moderate changes:<o:p></o:p></s=
pan></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo4"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">1)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Improved definition of =
the multiplexing period<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo4"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">2)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Clarification of the la=
tency values that can be added with TCMTF<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Minor changes:<o:p></o:p></span=
></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo6"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">1)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Noting that these recom=
mendations are mostly focused on low speed links as on high speed links the=
 added delay should be only few ms<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo6"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">2)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Clarification of senten=
ce: &quot;Therefore, we neither take into account services using an approac=
h in which all the calculations are deployed in the server, which sends a r=
eal-time video stream to the client.&quot;&nbsp;
 In a way that it more clearly reflects the fact that we are not addressing=
 the cloud based gaming services which basically stream video which has lar=
ge packets<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo6"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">3)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Replacing &#8220;priori=
ty&#8221; with &#8220;delay sensitive class&#8221;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo6"><![if !supportLists]><span lang=3D"EN-GB"><span style=3D"mso-list:=
Ignore">4)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB">Properly formalizing so=
me terms: replacing &#8220;jitter&#8221; with &#8220;delay variation&#8221;=
 as defined in RFC 5481, and using the definition of QoE from RFC 6390<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Also some other minor changes a=
nd typo corrections.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Thanks again to everyone who pr=
ovided feedback!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Best regards,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Mirko Suznjevic<o:p></o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</body>
</html>

--_000_E004A7C54DE04F4BB87DB9F32308DA5C0C0831MAIL4ferhr_--

From jsaldana@unizar.es  Wed Jun 12 06:10:39 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E7C721F9C51 for <tcmtf@ietfa.amsl.com>; Wed, 12 Jun 2013 06:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.519
X-Spam-Level: 
X-Spam-Status: No, score=-5.519 tagged_above=-999 required=5 tests=[AWL=-0.780, BAYES_20=-0.74, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d9nBAe2YtjGx for <tcmtf@ietfa.amsl.com>; Wed, 12 Jun 2013 06:10:34 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5F00921F9994 for <tcmtf@ietf.org>; Wed, 12 Jun 2013 06:10:33 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5CDAS4m006268; Wed, 12 Jun 2013 15:10:28 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 12 Jun 2013 15:10:37 +0200
Organization: Universidad de Zaragoza
Message-ID: <008101ce676e$3b4675e0$b1d361a0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0082_01CE677E.FECFBB10"
X-Mailer: Microsoft Outlook 14.0
Content-language: es
Thread-index: Ac5nbdr6vwKz99hGQMmbbC1me/s+Qw==
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
Subject: [tcmtf] =?iso-8859-2?q?A_terminological_question=3A_=22small-pack?= =?iso-8859-2?q?et_flows=22?=
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2013 13:10:39 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0082_01CE677E.FECFBB10
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: 7bit

Hi all.

 

Mirko and I are working on an improved version of the "TCMTF -
recommendations" document. Since TCMTF is not only suitable for real-time
services, but also for non real-time ones (M2M, flows of ACKs, instant
messaging), one possibility is using the term "small-packet flows".

 

The advantages are clear:

 

- It is more generic.

- It includes the characteristics of TCMTF-able packets:

- low payload-to-header ratio

- long-term flows

 

This term is also being used in some technical documents:
www.huawei.com/ilink/en/download/HW_193034. 

 

What do you think? Any other proposals?

 

Jose 

 


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

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-2">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi =
all.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><span lang=3DEN-US>Mirko and I are working on an =
improved version of the &#8220;TCMTF &#8211; recommendations&#8221; =
document. Since TCMTF is not only suitable for real-time services, but =
also for non real-time ones (M2M, flows of ACKs, instant messaging), one =
possibility is using the term &#8220;small-packet =
flows&#8221;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>The advantages are clear:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- It is more =
generic.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US> =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>- It =
includes the characteristics of TCMTF-able =
packets:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-indent:35.4pt'><span lang=3DEN-US>- low payload-to-header =
ratio<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-indent:35.4pt'><span lang=3DEN-US>- long-term =
flows<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 term is also being used in some technical documents: =
<a =
href=3D"http://www.huawei.com/ilink/en/download/HW_193034">www.huawei.com=
/ilink/en/download/HW_193034</a>. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>What do you think? Any other =
proposals?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-fareast-language:ES'>Jose =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_0082_01CE677E.FECFBB10--


From dwing@cisco.com  Wed Jun 12 08:34:33 2013
Return-Path: <dwing@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05A1D21F9923 for <tcmtf@ietfa.amsl.com>; Wed, 12 Jun 2013 08:34:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.523
X-Spam-Level: 
X-Spam-Status: No, score=-110.523 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wBNYcFuLuB-D for <tcmtf@ietfa.amsl.com>; Wed, 12 Jun 2013 08:34:28 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 7327F21F949D for <tcmtf@ietf.org>; Wed, 12 Jun 2013 08:34:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7961; q=dns/txt; s=iport; t=1371051266; x=1372260866; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=fobU40vKo1BORN1LRR2noEF2+8stV4mLO1dOuFntb3Q=; b=Pu3S7da6FO/8l6UuY4WXgJK3RtIJIV359XhCQaYtBDqYCBDC4qsV3Y/P 0gaGrwm4mxL2A+3oQfrvwaB0sfKtBdhs5s9dUvgQCzCca8EFVmqzlKNLg Hf46E9r995w4RyCp8i9u8KjYHKUBq13APH1IbcDzg4Sfmk7RLUyooo9dO I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvYIAIGUuFGrRDoI/2dsb2JhbABagkVEMIM9hW21ZoEDFnSCIwEBAQMBAQEBARwESgsFCwtDAycwBgoJiAgFDag/DJE2jz8EBxaCNzJhA4kgjiCRQoMvHA
X-IronPort-AV: E=Sophos;i="4.87,853,1363132800"; d="scan'208,217";a="83364628"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 12 Jun 2013 15:34:14 +0000
Received: from sjc-vpn6-1614.cisco.com (sjc-vpn6-1614.cisco.com [10.21.126.78]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r5CFYDgd026134; Wed, 12 Jun 2013 15:34:13 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_3B597ECE-7FA6-4E4E-8BE5-5252BBA2F3B8"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <008101ce676e$3b4675e0$b1d361a0$@unizar.es>
Date: Wed, 12 Jun 2013 08:34:13 -0700
Message-Id: <299BCC41-7095-40D2-A36A-B5DAB9790D93@cisco.com>
References: <008101ce676e$3b4675e0$b1d361a0$@unizar.es>
To: <jsaldana@unizar.es>
X-Mailer: Apple Mail (2.1508)
Cc: tcmtf@ietf.org, =?utf-8?Q?Mirko_Su=C5=BEnjevi=C4=87?= <Mirko.Suznjevic@fer.hr>
Subject: Re: [tcmtf] A terminological question: "small-packet flows"
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2013 15:34:33 -0000

--Apple-Mail=_3B597ECE-7FA6-4E4E-8BE5-5252BBA2F3B8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1250


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

> Hi all.
> =20
> Mirko and I are working on an improved version of the =93TCMTF =96 =
recommendations=94 document. Since TCMTF is not only suitable for =
real-time services, but also for non real-time ones (M2M, flows of ACKs, =
instant messaging), one possibility is using the term =93small-packet =
flows=94.

I agree TCMTF is suitable for small packets. =20

But by saying "small packet flow", it implies that the *entire flow* has =
to be small packets for TCMTF to kick in.  But TCMTF is useful if the =
flow is a mix of small and large packets, and useful if the flow began =
with lots of large packets (TLS or SSH handshake followed by a file =
transfer, or an HTTP GET (with a 4KB cookie) followed by a file =
transfer).

I like the term "small-packet flows" and it is concise, but when =
initially defined it would be useful to explain the flow does not have =
to always be small packets for the lifetime of the flow.

-d



> =20
> The advantages are clear:
> =20
> - It is more generic.
> - It includes the characteristics of TCMTF-able packets:
> - low payload-to-header ratio
> - long-term flows
> =20
> This term is also being used in some technical =
documents:www.huawei.com/ilink/en/download/HW_193034.
> =20
> What do you think? Any other proposals?
> =20
> Jose
> =20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


--Apple-Mail=_3B597ECE-7FA6-4E4E-8BE5-5252BBA2F3B8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1250

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1250"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jun 12, 2013, at 6:10 AM, Jose Saldana &lt;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div lang=3D"ES" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">Hi all.<o:p></o:p></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">Mirko and I are working on an improved version of the =
=93TCMTF =96 recommendations=94 document. Since TCMTF is not only =
suitable for real-time services, but also for non real-time ones (M2M, =
flows of ACKs, instant messaging), one possibility is using the term =
=93small-packet =
flows=94.</span></div></div></div></blockquote><div><br></div><div>I =
agree TCMTF is suitable for small packets. =
&nbsp;</div><div><br></div><div>But by saying "small packet flow", it =
implies that the *entire flow* has to be small packets for TCMTF to kick =
in. &nbsp;But TCMTF is useful if the flow is a mix of small and large =
packets, and useful if the flow began with lots of large packets (TLS or =
SSH handshake followed by a file transfer, or an HTTP GET (with a 4KB =
cookie) followed by a file transfer).</div><div><br></div><div>I like =
the term "small-packet flows" and it is concise, but when initially =
defined it would be useful to explain the flow does not have to always =
be small packets for the lifetime of the =
flow.</div><div><br></div><div>-d</div><div><br></div><div><br></div><br><=
blockquote type=3D"cite"><div lang=3D"ES" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US"><o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">The advantages are =
clear:<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">- It is more generic.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US"><o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">- It includes the =
characteristics of TCMTF-able packets:<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; text-indent: 35.4pt; "><span lang=3D"EN-US">- low =
payload-to-header ratio<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
text-indent: 35.4pt; "><span lang=3D"EN-US">- long-term =
flows<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">This term is also being used in some technical =
documents:<a href=3D"http://www.huawei.com/ilink/en/download/HW_193034" =
style=3D"color: purple; text-decoration: underline; =
">www.huawei.com/ilink/en/download/HW_193034</a>.<o:p></o:p></span></div><=
div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">What do you think? Any other =
proposals?<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">Jose<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div></div>__________________________________=
_____________<br>tcmtf mailing list<br><a href=3D"mailto:tcmtf@ietf.org" =
style=3D"color: purple; text-decoration: underline; =
">tcmtf@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color: =
purple; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/tcmtf</a><br></div></blockquote></=
div><br></body></html>=

--Apple-Mail=_3B597ECE-7FA6-4E4E-8BE5-5252BBA2F3B8--

From gorry@erg.abdn.ac.uk  Wed Jun 12 08:54:47 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A4FE21F9A63 for <tcmtf@ietfa.amsl.com>; Wed, 12 Jun 2013 08:54:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EOqSJoBtTr50 for <tcmtf@ietfa.amsl.com>; Wed, 12 Jun 2013 08:54:38 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 53A4821F99AF for <tcmtf@ietf.org>; Wed, 12 Jun 2013 08:54:35 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 8DB582B41E9; Wed, 12 Jun 2013 16:54:32 +0100 (BST)
Received: from 139.133.204.42 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Wed, 12 Jun 2013 16:54:32 +0100
Message-ID: <5b0ced243ea27ff5d78b7b3e959faf75.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <008101ce676e$3b4675e0$b1d361a0$@unizar.es>
References: <008101ce676e$3b4675e0$b1d361a0$@unizar.es>
Date: Wed, 12 Jun 2013 16:54:32 +0100
From: gorry@erg.abdn.ac.uk
To: jsaldana@unizar.es
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: tcmtf@ietf.org, =?iso-8859-1?Q?=22Mirko_Su=BEnjevi=E6=22?= <mirko.suznjevic@fer.hr>
Subject: Re: [tcmtf] A terminological question: "small-packet flows"
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2013 15:54:47 -0000

If you're talking about TCP ACKs RFC 3449 could be relevant.

Gorry

> Hi all.
>
>
>
> Mirko and I are working on an improved version of the "TCMTF -
> recommendations" document. Since TCMTF is not only suitable for real-time
> services, but also for non real-time ones (M2M, flows of ACKs, instant
> messaging), one possibility is using the term "small-packet flows".
>
>
>
> The advantages are clear:
>
>
>
> - It is more generic.
>
> - It includes the characteristics of TCMTF-able packets:
>
> - low payload-to-header ratio
>
> - long-term flows
>
>
>
> This term is also being used in some technical documents:
> www.huawei.com/ilink/en/download/HW_193034.
>
>
>
> What do you think? Any other proposals?
>
>
>
> Jose
>
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>



From jsaldana@unizar.es  Wed Jun 12 09:03:23 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D53B721F9986 for <tcmtf@ietfa.amsl.com>; Wed, 12 Jun 2013 09:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.318
X-Spam-Level: 
X-Spam-Status: No, score=-6.318 tagged_above=-999 required=5 tests=[AWL=0.280,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PJeX6eKMdyFj for <tcmtf@ietfa.amsl.com>; Wed, 12 Jun 2013 09:03:19 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id AF7F421F9AAB for <tcmtf@ietf.org>; Wed, 12 Jun 2013 09:03:18 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5CG389g021556; Wed, 12 Jun 2013 18:03:08 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Dan Wing'" <dwing@cisco.com>
References: <008101ce676e$3b4675e0$b1d361a0$@unizar.es> <299BCC41-7095-40D2-A36A-B5DAB9790D93@cisco.com>
In-Reply-To: <299BCC41-7095-40D2-A36A-B5DAB9790D93@cisco.com>
Date: Wed, 12 Jun 2013 18:03:18 +0200
Organization: Universidad de Zaragoza
Message-ID: <00ea01ce6786$5b198200$114c8600$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00EB_01CE6797.1EA25200"
X-Mailer: Microsoft Outlook 14.0
Content-language: es
Thread-index: AQFbWNGeasK9gJiAVLdN29QxUaAJagGL/Vx/mgv4g+A=
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, =?iso-8859-2?Q?'Mirko_Su=BEnjevi=E6'?= <Mirko.Suznjevic@fer.hr>
Subject: Re: [tcmtf] A terminological question: "small-packet flows"
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2013 16:03:23 -0000

This is a multipart message in MIME format.

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

You are right, Dan:

=20

We are considering the use of a "period" policy, which sends a =
multiplexed
packet at the end of each interval. However, this policy should be =
combined
with a "MTU size limit" policy, which triggers the packet as soon as a =
"next
to MTU" multiplexed packet is sent, even if the period has not expired.

=20

In addition, if a single packet is to be multiplexed, it will be better =
to
send it in its native form. We don't need the tunnel in that case.

=20

So let's suppose we have identified a "small packet flow" and in a =
certain
moment it generates a burst of big packets. In that case, TCMTF still =
works.
If we use the "period+MTU size limit" policy, then big packets will be =
sent
alone as soon as they arrive to the multiplexer.

=20

So, as you say, when initially defining "small-packet flows", it would =
be
useful to explain that the flow does not have to always be small packets =
for
the lifetime of the flow. We can say that in a "small-packet flow" the =
vast
majority of the packets are small.

=20

Thanks!

=20

Jose

=20

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de =
Dan
Wing
Enviado el: mi=E9rcoles, 12 de junio de 2013 17:34
Para: jsaldana@unizar.es
CC: tcmtf@ietf.org; Mirko Su=BEnjevi=E6
Asunto: Re: [tcmtf] A terminological question: "small-packet flows"

=20

=20

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





Hi all.

=20

Mirko and I are working on an improved version of the "TCMTF -
recommendations" document. Since TCMTF is not only suitable for =
real-time
services, but also for non real-time ones (M2M, flows of ACKs, instant
messaging), one possibility is using the term "small-packet flows".

=20

I agree TCMTF is suitable for small packets. =20

=20

But by saying "small packet flow", it implies that the *entire flow* has =
to
be small packets for TCMTF to kick in.  But TCMTF is useful if the flow =
is a
mix of small and large packets, and useful if the flow began with lots =
of
large packets (TLS or SSH handshake followed by a file transfer, or an =
HTTP
GET (with a 4KB cookie) followed by a file transfer).

=20

I like the term "small-packet flows" and it is concise, but when =
initially
defined it would be useful to explain the flow does not have to always =
be
small packets for the lifetime of the flow.

=20

-d

=20

=20





=20

The advantages are clear:

=20

- It is more generic.

- It includes the characteristics of TCMTF-able packets:

- low payload-to-header ratio

- long-term flows

=20

This term is also being used in some technical documents:
<http://www.huawei.com/ilink/en/download/HW_193034>
www.huawei.com/ilink/en/download/HW_193034.

=20

What do you think? Any other proposals?

=20

Jose

=20

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

=20


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-2"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>You are right, Dan:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We are considering the use of a &#8220;period&#8221; policy, which =
sends a multiplexed packet at the end of each interval. However, this =
policy should be combined with a &#8220;MTU size limit&#8221; policy, =
which triggers the packet as soon as a &#8220;next to MTU&#8221; =
multiplexed packet is sent, even if the period has not =
expired.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>In addition, if a single packet is to be multiplexed, it will be =
better to send it in its native form. We don&#8217;t need the tunnel in =
that case.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>So let&#8217;s suppose we have identified a &#8220;small packet =
flow&#8221; and in a certain moment it generates a burst of big packets. =
In that case, TCMTF still works. If we use the &#8220;period+MTU size =
limit&#8221; policy, then big packets will be sent alone as soon as they =
arrive to the multiplexer.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>So, as you say, when initially defining &#8220;small-packet =
flows&#8221;, it would be useful to explain that the flow does not have =
to always be small packets for the lifetime of the flow. We can say that =
in a &#8220;small-packet flow&#8221; the vast majority of the packets =
are small.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks!<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jose<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tcmtf-bounces@ietf.org [mailto:tcmtf-boun</span><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>ces@ietf.org=
] <b>En nombre de </b>Dan Wing<br><b>Enviado el:</b> mi=E9rcoles, 12 de =
junio de 2013 17:34<br><b>Para:</b> jsaldana@unizar.es<br><b>CC:</b> =
tcmtf@ietf.org; Mirko Su=BEnjevi=E6<br><b>Asunto:</b> Re: [tcmtf] A =
terminological question: &quot;small-packet =
flows&quot;<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Jun 12, 2013, at 6:10 AM, Jose Saldana &lt;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt; =
wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hi =
all.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p>=
</o:p></span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Mirko and =
I are working on an improved version of the &#8220;TCMTF &#8211; =
recommendations&#8221; document. Since TCMTF is not only suitable for =
real-time services, but also for non real-time ones (M2M, flows of ACKs, =
instant messaging), one possibility is using the term =
&#8220;small-packet flows&#8221;.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
agree TCMTF is suitable for small packets. =
&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>But by saying &quot;small packet flow&quot;, it =
implies that the *entire flow* has to be small packets for TCMTF to kick =
in. &nbsp;But TCMTF is useful if the flow is a mix of small and large =
packets, and useful if the flow began with lots of large packets (TLS or =
SSH handshake followed by a file transfer, or an HTTP GET (with a 4KB =
cookie) followed by a file transfer).<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
like the term &quot;small-packet flows&quot; and it is concise, but when =
initially defined it would be useful to explain the flow does not have =
to always be small packets for the lifetime of the =
flow.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>-d<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The =
advantages are clear:</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>- It is =
more generic.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>- It =
includes the characteristics of TCMTF-able packets:</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal =
style=3D'text-indent:35.4pt'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>- low =
payload-to-header ratio</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal =
style=3D'text-indent:35.4pt'><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>- =
long-term flows</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>This term =
is also being used in some technical documents:<a =
href=3D"http://www.huawei.com/ilink/en/download/HW_193034"><span =
style=3D'color:purple'>www.huawei.com/ilink/en/download/HW_193034</span><=
/a>.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>What do =
you think? Any other proposals?</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Jose</span>=
<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><p class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>_________=
______________________________________<br>tcmtf mailing list<br><a =
href=3D"mailto:tcmtf@ietf.org"><span =
style=3D'color:purple'>tcmtf@ietf.org</span></a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/tcmtf"><span =
style=3D'color:purple'>https://www.ietf.org/mailman/listinfo/tcmtf</span>=
</a><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_00EB_01CE6797.1EA25200--


From jsaldana@unizar.es  Wed Jun 12 09:20:21 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4210721E804B for <tcmtf@ietfa.amsl.com>; Wed, 12 Jun 2013 09:20:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.359
X-Spam-Level: 
X-Spam-Status: No, score=-6.359 tagged_above=-999 required=5 tests=[AWL=0.240,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2McH-VPrFn2Z for <tcmtf@ietfa.amsl.com>; Wed, 12 Jun 2013 09:20:16 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF3B11E80E1 for <tcmtf@ietf.org>; Wed, 12 Jun 2013 09:20:16 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5CGK8EN009807; Wed, 12 Jun 2013 18:20:08 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <gorry@erg.abdn.ac.uk>
References: <008101ce676e$3b4675e0$b1d361a0$@unizar.es> <5b0ced243ea27ff5d78b7b3e959faf75.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <5b0ced243ea27ff5d78b7b3e959faf75.squirrel@www.erg.abdn.ac.uk>
Date: Wed, 12 Jun 2013 18:20:18 +0200
Organization: Universidad de Zaragoza
Message-ID: <010201ce6788$bb0ba9c0$3122fd40$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Content-language: es
Thread-index: AQFbWNGeasK9gJiAVLdN29QxUaAJagIWQdJ+mgeq6oA=
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, =?iso-8859-1?Q?'=22Mirko_Su=BEnjevi=E6=22'?= <mirko.suznjevic@fer.hr>
Subject: Re: [tcmtf] A terminological question: "small-packet flows"
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2013 16:20:21 -0000

Gorry,

Thanks for the suggestion.

Some ACK flows generate a lot of pps:

- A file download may easily generate 100 ACKs per second from a =
computer to
the file server.
- TCP-based games also generate ACKs (maybe 10 pps)

Which delays would impair an ACK flow, according to RFC 3449? The idea I
have in mind is using multiplexing periods between 50 and 100 ms.

There is another problem, related to TCP Friendly Rate Control (TFRC, =
RFC
5348): if you add too much delay, the throughput can be reduced. This =
idea
was suggested by Michael some weeks ago:
http://www.ietf.org/mail-archive/web/tcmtf/current/msg00235.html

Thanks!

Jose

> -----Mensaje original-----
> De: gorry@erg.abdn.ac.uk [mailto:gorry@erg.abdn.ac.uk]
> Enviado el: mi=E9rcoles, 12 de junio de 2013 17:55
> Para: jsaldana@unizar.es
> CC: tcmtf@ietf.org; "Mirko Su=BEnjevi=E6"
> Asunto: Re: [tcmtf] A terminological question: "small-packet flows"
>=20
> If you're talking about TCP ACKs RFC 3449 could be relevant.
>=20
> Gorry
>=20
> > Hi all.
> >
> >
> >
> > Mirko and I are working on an improved version of the "TCMTF -
> > recommendations" document. Since TCMTF is not only suitable for
> > real-time services, but also for non real-time ones (M2M, flows of
> > ACKs, instant messaging), one possibility is using the term
"small-packet
> flows".
> >
> >
> >
> > The advantages are clear:
> >
> >
> >
> > - It is more generic.
> >
> > - It includes the characteristics of TCMTF-able packets:
> >
> > - low payload-to-header ratio
> >
> > - long-term flows
> >
> >
> >
> > This term is also being used in some technical documents:
> > www.huawei.com/ilink/en/download/HW_193034.
> >
> >
> >
> > What do you think? Any other proposals?
> >
> >
> >
> > Jose
> >
> >
> >
> > _______________________________________________
> > tcmtf mailing list
> > tcmtf@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcmtf
> >



From gorry@erg.abdn.ac.uk  Wed Jun 12 09:32:51 2013
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43D2B21F9964 for <tcmtf@ietfa.amsl.com>; Wed, 12 Jun 2013 09:32:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SziCCXNqmyQG for <tcmtf@ietfa.amsl.com>; Wed, 12 Jun 2013 09:32:46 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 9894321F996C for <tcmtf@ietf.org>; Wed, 12 Jun 2013 09:32:46 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id B40E72B41E9; Wed, 12 Jun 2013 17:32:45 +0100 (BST)
Received: from 139.133.204.42 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Wed, 12 Jun 2013 17:32:45 +0100
Message-ID: <0ffb9f6fbd94eec2170b9506b2bfcfd6.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <010201ce6788$bb0ba9c0$3122fd40$@unizar.es>
References: <008101ce676e$3b4675e0$b1d361a0$@unizar.es> <5b0ced243ea27ff5d78b7b3e959faf75.squirrel@www.erg.abdn.ac.uk> <010201ce6788$bb0ba9c0$3122fd40$@unizar.es>
Date: Wed, 12 Jun 2013 17:32:45 +0100
From: gorry@erg.abdn.ac.uk
To: jsaldana@unizar.es
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: gorry@erg.abdn.ac.uk, tcmtf@ietf.org, =?iso-8859-1?Q?=22'Mirko_Su=BEnjevi=E6=22'=22=22?= <mirko.suznjevic@fer.hr>
Subject: Re: [tcmtf] A terminological question: "small-packet flows"
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2013 16:32:51 -0000

See below,

Gorry

> Gorry,
>
> Thanks for the suggestion.
>
> Some ACK flows generate a lot of pps:
>
> - A file download may easily generate 100 ACKs per second from a computer
> to
> the file server.
> - TCP-based games also generate ACKs (maybe 10 pps)
>
> Which delays would impair an ACK flow, according to RFC 3449? The idea I
> have in mind is using multiplexing periods between 50 and 100 ms.
>
RFC 3449 gives BCP guidance on how to manage compression of the TCP ACK
stream and things to do and things to avoid.

For example, you may well be aware that bunching ACKs by sending them all
in one burst **IS** likely something that would need to be examined in
detail, since this impacts the flow dynamics and can therefore modify the
congestion behaviour across the network.

I'm just suggesting that your charter should be clear about about the set
of topics the group is currently addressing (e.g. TCP changes) so that
people understand whether they support or have issues with the proposed
scope of the work.

> There is another problem, related to TCP Friendly Rate Control (TFRC, RFC
> 5348): if you add too much delay, the throughput can be reduced. This idea
> was suggested by Michael some weeks ago:
> http://www.ietf.org/mail-archive/web/tcmtf/current/msg00235.html
>
That's also true - but I am not sure Michael was actually talking about
looking at TFRC, more as I saw it, he was talking about the sort of  TCP
rate you should expect based on the throughput equation (i.e. as a
function of loss and RTT).

> Thanks!
>
> Jose
>
>> -----Mensaje original-----
>> De: gorry@erg.abdn.ac.uk [mailto:gorry@erg.abdn.ac.uk]
>> Enviado el: miércoles, 12 de junio de 2013 17:55
>> Para: jsaldana@unizar.es
>> CC: tcmtf@ietf.org; "Mirko Su¾njeviæ"
>> Asunto: Re: [tcmtf] A terminological question: "small-packet flows"
>>
>> If you're talking about TCP ACKs RFC 3449 could be relevant.
>>
>> Gorry
>>
>> > Hi all.
>> >
>> >
>> >
>> > Mirko and I are working on an improved version of the "TCMTF -
>> > recommendations" document. Since TCMTF is not only suitable for
>> > real-time services, but also for non real-time ones (M2M, flows of
>> > ACKs, instant messaging), one possibility is using the term
> "small-packet
>> flows".
>> >
>> >
>> >
>> > The advantages are clear:
>> >
>> >
>> >
>> > - It is more generic.
>> >
>> > - It includes the characteristics of TCMTF-able packets:
>> >
>> > - low payload-to-header ratio
>> >
>> > - long-term flows
>> >
>> >
>> >
>> > This term is also being used in some technical documents:
>> > www.huawei.com/ilink/en/download/HW_193034.
>> >
>> >
>> >
>> > What do you think? Any other proposals?
>> >
>> >
>> >
>> > Jose
>> >
>> >
>> >
>> > _______________________________________________
>> > tcmtf mailing list
>> > tcmtf@ietf.org
>> > https://www.ietf.org/mailman/listinfo/tcmtf
>> >
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>



From jsaldana@unizar.es  Thu Jun 13 01:38:02 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0572421F9A97; Thu, 13 Jun 2013 01:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.389
X-Spam-Level: 
X-Spam-Status: No, score=-6.389 tagged_above=-999 required=5 tests=[AWL=0.210,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id smx6NEDvfzzz; Thu, 13 Jun 2013 01:37:57 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC4621F9A7A; Thu, 13 Jun 2013 01:37:56 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5D8bj49003891; Thu, 13 Jun 2013 10:37:46 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>, <tsv-area@ietf.org>
Date: Thu, 13 Jun 2013 10:37:51 +0200
Organization: Universidad de Zaragoza
Message-ID: <006401ce6811$4af07b50$e0d171f0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5oEUJh6X32UcmxT3KmocW8KKc14Q==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] Improved version of the tmctf Draft charter (v6)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jun 2013 08:38:02 -0000

This is the new proposal, adapted to the new distribution of the =
documents.
I explain the changes in another e-mail.
It is also here, in a formatted version:
http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf


TCMTF charter draft v6

Description of Working Group

1. In the last years we are witnessing the raise of new real-time =
services
that use the Internet for the delivery of interactive multimedia
applications: VoIP, videoconferencing, telemedicine, video vigilance, =
online
gaming, etc. Due to the need of interactivity, many of these services =
use
small packets (some tens of bytes), since they have to send frequent =
updates
between the extremes of the communication. In addition, some other =
services
also send small packets, but they are not delay-sensitive (e.g., instant
messaging, m2m packets sending collected data in sensor networks using
wireless or satellite scenarios). For both the delay-sensitive and
delay-insensitive applications, their small data payloads incur =
significant
overhead, and it becomes even higher when IPv6 is used, since the basic =
IPv6
header is twice the size of the IPv4 one.

2. The efficiency cannot be increased by the inclusion of a higher =
number of
samples in a single packet, since this would harm the delay requirements =
of
the service. But there exist some scenarios in which a number of flows =
share
the same path. In this case, packets belonging to different flows can be
grouped together, adding a small multiplexing delay as a counterpart of
bandwidth saving. This delay will have to be maintained under some =
threshold
in order to grant the delay requirements. Some examples of the scenarios
where grouping packets is possible are:

- aggregation networks of a network operator;
- an end-to-end tunnel between appliances located in two different =
offices
of the same company;
- the access connection of an Internet Caf=E9 including a high number of
VoIP/gaming flows;
- an agreement between two network operators could allow them to =
compress a
number of flows they are exchanging between a pair of Internet Routers;
- a satellite connection used for collecting the data of a high number =
of
sensors.

3. VoIP using RTP is a clear example of a real-time service using small
packets with high overhead. In order to improve efficiency, RFC4170 =
(TCRTP)
defined a method for grouping packets when a number of flows share a =
path,
considering three different layers: header compression by means of =
ECRTP;
multiplexing by means of PPPMux; tunneling by means of L2TPv3.

4. However, in the last years, emerging real-time services which do not =
use
UDP/RTP have become popular: some of them use UDP or even TCP. In =
addition,
new header compression methods have been defined (ROHC). So there is a =
need
of widening the scope of RFC4170 in order to consider not only UDP/RTP =
but
also other protocols. The same structure of three layers will be =
considered:

- Header compression: Taking into account that real-time applications =
use
different headers (RTP/UDP, UDP or even TCP), different protocols can be
used: no compression, ECRTP, IPHC and ROHC.
- Multiplexing: If a number of flows share a path between an origin and =
a
destination, a multiplexer can build a bigger packet in which a number =
of
payloads share a common header. A demultiplexer is then necessary at the =
end
of the common path, so as to rebuild the packets as they were originally
sent. PPPMux will be the main option. Other ones are not discarded.
- Tunneling will be used to send the multiplexed packets end-to-end. The
options in this layer are L2TP, GRE and MPLS.

5. So the first objective of this group is to specify the protocol stack =
for
tunneling, compressing and multiplexing traffic flows (TCMTF). Since
standard protocols are being used at each layer, the signaling methods =
of
those protocols will be used. Interactions with the Working Groups and =
Areas
in which these protocols are developed can be expected. However, the
development of new compressing, multiplexing or tunneling protocols is =
not
an objective of this Working Group. In addition, since the current RFC =
4170
would be considered as one of the options, this RFC could be obsoleted.

6. As a first objective, a document (TCMTF - reference model) will =
define
the different options which can be used at each layer. Specific problems
caused by the interaction between layers will have to be issued, and
suitable extensions may have to be added to the involved protocols.

7. If a pair multiplexer/de-multiplexer want to establish a TCMTF =
session,
they have first to use a mechanism to negotiate which concrete option =
would
they use in each layer: header compression, multiplexing and tunneling. =
This
will depend on the protocols that each extreme implements at each level, =
and
in the scenario. So another document (TCMTF - negotiation protocol) will
include:

- a mechanism to setup/release a TCMTF session between a multiplexer and =
a
de-multiplexer, also including:
- a negotiation mechanism to decide the options to use at each layer =
(header
compression, multiplexing and tunneling) between multiplexer and
de-multiplexer,=20

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

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

10. In addition, specific uses of TCMTF, such as in wireless and =
satellite
scenarios, could be considered, and it will be studied whether =
modifications
or extensions are required on the protocol.

11. Interactions with other Working Groups can be expected, since TCMTF =
uses
already defined protocols for compression, multiplexing and tunneling =
(ROHC,
PPPMux, MPLS, GRE, L2TP).=20

Goals and Milestones

Specification of TCMTF  reference model.

Specification of TCMTF negotiation protocol.

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


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

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


Best regards,

Jose



From jsaldana@unizar.es  Thu Jun 13 01:43:08 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DD1221F99B2; Thu, 13 Jun 2013 01:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.412
X-Spam-Level: 
X-Spam-Status: No, score=-6.412 tagged_above=-999 required=5 tests=[AWL=0.187,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IsqlzWQkamJw; Thu, 13 Jun 2013 01:43:03 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 21A5B21F8930; Thu, 13 Jun 2013 01:43:02 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5D8gx0o008469; Thu, 13 Jun 2013 10:43:00 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>, <tsv-area@ietf.org>
References: <006401ce6811$4af07b50$e0d171f0$@unizar.es>
In-Reply-To: <006401ce6811$4af07b50$e0d171f0$@unizar.es>
Date: Thu, 13 Jun 2013 10:43:05 +0200
Organization: Universidad de Zaragoza
Message-ID: <006501ce6812$060676b0$12136410$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH8N/Xy9eDz5XZCFkPyyAOW2cIPWpjXstnw
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jun 2013 08:43:08 -0000

These are the main changes included in the draft charter v6 (ordered by
paragraphs):

1. I have moved the sentence about the overhead to the end of the =
paragraph,
in order to say that =93For both the delay-sensitive and =
delay-insensitive
applications, their small data payloads incur significant overhead=94=20

2. I have put the scenarios in bullets, and I have improved some of the
descriptions a bit.

6. I have changed the name of the document: instead of =93document A=94 =
it is
now =93TCMTF =96 reference model=94.

7. Now we are talking about another document =93TCMTF =96 negotiation =
protocol=94.
In addition, I have put the two signaling functionalities in bullets.

7. As discussed in the list, we would talk about =93setup/release a =
TCMTF
session=94.

8. I have changed the name of the document, from =93document B=94 to =
=93TCMTF
recommendations=94

8. According to Gorry=92s suggestion, I have added this sentence: =93The
eventual impact of multiplexing on protocol dynamics (e.g. when =
multiplexing
TCP flows) will also have to be addressed.=94

Jose=20


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


From jsaldana@unizar.es  Thu Jun 13 01:47:21 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2802B21F9A73 for <tcmtf@ietfa.amsl.com>; Thu, 13 Jun 2013 01:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.431
X-Spam-Level: 
X-Spam-Status: No, score=-6.431 tagged_above=-999 required=5 tests=[AWL=0.168,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KEK9hBFXPqr9 for <tcmtf@ietfa.amsl.com>; Thu, 13 Jun 2013 01:47:08 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id D62FA21F8AF7 for <tcmtf@ietf.org>; Thu, 13 Jun 2013 01:47:07 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5D8l2u7012182; Thu, 13 Jun 2013 10:47:02 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <gorry@erg.abdn.ac.uk>
References: <008101ce676e$3b4675e0$b1d361a0$@unizar.es>	<5b0ced243ea27ff5d78b7b3e959faf75.squirrel@www.erg.abdn.ac.uk>	<010201ce6788$bb0ba9c0$3122fd40$@unizar.es> <0ffb9f6fbd94eec2170b9506b2bfcfd6.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <0ffb9f6fbd94eec2170b9506b2bfcfd6.squirrel@www.erg.abdn.ac.uk>
Date: Thu, 13 Jun 2013 10:47:07 +0200
Organization: Universidad de Zaragoza
Message-ID: <006601ce6812$9676ef40$c364cdc0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFbWNGeasK9gJiAVLdN29QxUaAJagIWQdJ+ATYyFbQCkMQN/pnqiWfA
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, =?iso-8859-1?Q?'=22'Mirko_Su=BEnjevi=E6=22'=22=22'?= <mirko.suznjevic@fer.hr>
Subject: Re: [tcmtf] A terminological question: "small-packet flows"
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jun 2013 08:47:21 -0000

Gorry,

Thanks for the suggestion. I have included it in the end of Paragraph 8 =
of
the charter draft v6:

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

I think we should study this in the TCMTF - recommendations document. Do =
you
agree?

Thanks,

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> gorry@erg.abdn.ac.uk
> Enviado el: mi=E9rcoles, 12 de junio de 2013 18:33
> Para: jsaldana@unizar.es
> CC: gorry@erg.abdn.ac.uk; tcmtf@ietf.org; "'Mirko Su=BEnjevi=E6"'""
> Asunto: Re: [tcmtf] A terminological question: "small-packet flows"
>=20
> See below,
>=20
> Gorry
>=20
> > Gorry,
> >
> > Thanks for the suggestion.
> >
> > Some ACK flows generate a lot of pps:
> >
> > - A file download may easily generate 100 ACKs per second from a
> > computer to the file server.
> > - TCP-based games also generate ACKs (maybe 10 pps)
> >
> > Which delays would impair an ACK flow, according to RFC 3449? The =
idea
> > I have in mind is using multiplexing periods between 50 and 100 ms.
> >
> RFC 3449 gives BCP guidance on how to manage compression of the TCP =
ACK
> stream and things to do and things to avoid.
>=20
> For example, you may well be aware that bunching ACKs by sending them =
all
> in one burst **IS** likely something that would need to be examined in
> detail, since this impacts the flow dynamics and can therefore modify =
the
> congestion behaviour across the network.
>=20
> I'm just suggesting that your charter should be clear about about the =
set
of
> topics the group is currently addressing (e.g. TCP changes) so that =
people
> understand whether they support or have issues with the proposed scope =
of
> the work.
>=20
> > There is another problem, related to TCP Friendly Rate Control =
(TFRC,
> > RFC
> > 5348): if you add too much delay, the throughput can be reduced. =
This
> > idea was suggested by Michael some weeks ago:
> > http://www.ietf.org/mail-archive/web/tcmtf/current/msg00235.html
> >
> That's also true - but I am not sure Michael was actually talking =
about
looking
> at TFRC, more as I saw it, he was talking about the sort of  TCP rate =
you
> should expect based on the throughput equation (i.e. as a function of =
loss
> and RTT).
>=20
> > Thanks!
> >
> > Jose
> >
> >> -----Mensaje original-----
> >> De: gorry@erg.abdn.ac.uk [mailto:gorry@erg.abdn.ac.uk] Enviado el:
> >> mi=E9rcoles, 12 de junio de 2013 17:55
> >> Para: jsaldana@unizar.es
> >> CC: tcmtf@ietf.org; "Mirko Su=BEnjevi=E6"
> >> Asunto: Re: [tcmtf] A terminological question: "small-packet flows"
> >>
> >> If you're talking about TCP ACKs RFC 3449 could be relevant.
> >>
> >> Gorry
> >>
> >> > Hi all.
> >> >
> >> >
> >> >
> >> > Mirko and I are working on an improved version of the "TCMTF -
> >> > recommendations" document. Since TCMTF is not only suitable for
> >> > real-time services, but also for non real-time ones (M2M, flows =
of
> >> > ACKs, instant messaging), one possibility is using the term
> > "small-packet
> >> flows".
> >> >
> >> >
> >> >
> >> > The advantages are clear:
> >> >
> >> >
> >> >
> >> > - It is more generic.
> >> >
> >> > - It includes the characteristics of TCMTF-able packets:
> >> >
> >> > - low payload-to-header ratio
> >> >
> >> > - long-term flows
> >> >
> >> >
> >> >
> >> > This term is also being used in some technical documents:
> >> > www.huawei.com/ilink/en/download/HW_193034.
> >> >
> >> >
> >> >
> >> > What do you think? Any other proposals?
> >> >
> >> >
> >> >
> >> > Jose
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > tcmtf mailing list
> >> > tcmtf@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/tcmtf
> >> >
> >
> >
> > _______________________________________________
> > tcmtf mailing list
> > tcmtf@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcmtf
> >
>=20
>=20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From navajas@unizar.es  Fri Jun 14 01:45:20 2013
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 447A221F9BB6 for <tcmtf@ietfa.amsl.com>; Fri, 14 Jun 2013 01:45:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d1jPcXeUNQDz for <tcmtf@ietfa.amsl.com>; Fri, 14 Jun 2013 01:45:14 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id AC91021F9B9D for <tcmtf@ietf.org>; Fri, 14 Jun 2013 01:45:13 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5E8j9fo019189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Fri, 14 Jun 2013 10:45:09 +0200
Message-ID: <51BAD816.2000300@unizar.es>
Date: Fri, 14 Jun 2013 10:45:10 +0200
From: =?UTF-8?B?SnVsacOhbiBGZXJuw6FuZGV6LU5hdmFqYXM=?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <006401ce6811$4af07b50$e0d171f0$@unizar.es> <006501ce6812$060676b0$12136410$@unizar.es>
In-Reply-To: <006501ce6812$060676b0$12136410$@unizar.es>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jun 2013 08:45:20 -0000

Jose and Gorry and all,
In order to clarify the delay-sensitive application term, i think that 
there are more than two options: sensitive and nonsensitive. I'd prefer 
say delay-very-sensitive's application, delay-sensitive, 
delay-some-sensitive, delay-nonsensitive or something similar
JuliÃ¡n

El 13/06/2013 10:43, Jose Saldana escribiÃ³:
> These are the main changes included in the draft charter v6 (ordered by
> paragraphs):
>
> 1. I have moved the sentence about the overhead to the end of the paragraph,
> in order to say that â€œFor both the delay-sensitive and delay-insensitive
> applications, their small data payloads incur significant overheadâ€�
>
> 2. I have put the scenarios in bullets, and I have improved some of the
> descriptions a bit.
>
> 6. I have changed the name of the document: instead of â€œdocument Aâ€� it is
> now â€œTCMTF â€“ reference modelâ€�.
>
> 7. Now we are talking about another document â€œTCMTF â€“ negotiation protocolâ€�.
> In addition, I have put the two signaling functionalities in bullets.
>
> 7. As discussed in the list, we would talk about â€œsetup/release a TCMTF
> sessionâ€�.
>
> 8. I have changed the name of the document, from â€œdocument Bâ€� to â€œTCMTF
> recommendationsâ€�
>
> 8. According to Gorryâ€™s suggestion, I have added this sentence: â€œThe
> eventual impact of multiplexing on protocol dynamics (e.g. when multiplexing
> TCP flows) will also have to be addressed.â€�
>
> Jose
>
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Jose Saldana
>> Enviado el: jueves, 13 de junio de 2013 10:38
>> Para: tcmtf@ietf.org; tsv-area@ietf.org
>> Asunto: [tcmtf] Improved version of the tmctf Draft charter (v6)
>>
>> This is the new proposal, adapted to the new distribution of the
> documents.
>> I explain the changes in another e-mail.
>> It is also here, in a formatted version:
>> http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf
>>
>>
>> TCMTF charter draft v6
>>
>> Description of Working Group
>>
>> 1. In the last years we are witnessing the raise of new real-time services
> that
>> use the Internet for the delivery of interactive multimedia
>> applications: VoIP, videoconferencing, telemedicine, video vigilance,
> online
>> gaming, etc. Due to the need of interactivity, many of these services use
>> small packets (some tens of bytes), since they have to send frequent
>> updates between the extremes of the communication. In addition, some
>> other services also send small packets, but they are not delay-sensitive
> (e.g.,
>> instant messaging, m2m packets sending collected data in sensor networks
>> using wireless or satellite scenarios). For both the delay-sensitive and
> delay-
>> insensitive applications, their small data payloads incur significant
> overhead,
>> and it becomes even higher when IPv6 is used, since the basic IPv6 header
> is
>> twice the size of the IPv4 one.
>>
>> 2. The efficiency cannot be increased by the inclusion of a higher number
> of
>> samples in a single packet, since this would harm the delay requirements
> of
>> the service. But there exist some scenarios in which a number of flows
> share
>> the same path. In this case, packets belonging to different flows can be
>> grouped together, adding a small multiplexing delay as a counterpart of
>> bandwidth saving. This delay will have to be maintained under some
>> threshold in order to grant the delay requirements. Some examples of the
>> scenarios where grouping packets is possible are:
>>
>> - aggregation networks of a network operator;
>> - an end-to-end tunnel between appliances located in two different offices
>> of the same company;
>> - the access connection of an Internet CafÃ© including a high number of
>> VoIP/gaming flows;
>> - an agreement between two network operators could allow them to
>> compress a number of flows they are exchanging between a pair of Internet
>> Routers;
>> - a satellite connection used for collecting the data of a high number of
>> sensors.
>>
>> 3. VoIP using RTP is a clear example of a real-time service using small
> packets
>> with high overhead. In order to improve efficiency, RFC4170 (TCRTP)
> defined
>> a method for grouping packets when a number of flows share a path,
>> considering three different layers: header compression by means of ECRTP;
>> multiplexing by means of PPPMux; tunneling by means of L2TPv3.
>>
>> 4. However, in the last years, emerging real-time services which do not
> use
>> UDP/RTP have become popular: some of them use UDP or even TCP. In
>> addition, new header compression methods have been defined (ROHC). So
>> there is a need of widening the scope of RFC4170 in order to consider not
>> only UDP/RTP but also other protocols. The same structure of three layers
>> will be considered:
>>
>> - Header compression: Taking into account that real-time applications use
>> different headers (RTP/UDP, UDP or even TCP), different protocols can be
>> used: no compression, ECRTP, IPHC and ROHC.
>> - Multiplexing: If a number of flows share a path between an origin and a
>> destination, a multiplexer can build a bigger packet in which a number of
>> payloads share a common header. A demultiplexer is then necessary at the
>> end of the common path, so as to rebuild the packets as they were
> originally
>> sent. PPPMux will be the main option. Other ones are not discarded.
>> - Tunneling will be used to send the multiplexed packets end-to-end. The
>> options in this layer are L2TP, GRE and MPLS.
>>
>> 5. So the first objective of this group is to specify the protocol stack
> for
>> tunneling, compressing and multiplexing traffic flows (TCMTF). Since
>> standard protocols are being used at each layer, the signaling methods of
>> those protocols will be used. Interactions with the Working Groups and
> Areas
>> in which these protocols are developed can be expected. However, the
>> development of new compressing, multiplexing or tunneling protocols is not
>> an objective of this Working Group. In addition, since the current RFC
> 4170
>> would be considered as one of the options, this RFC could be obsoleted.
>>
>> 6. As a first objective, a document (TCMTF - reference model) will define
> the
>> different options which can be used at each layer. Specific problems
> caused
>> by the interaction between layers will have to be issued, and suitable
>> extensions may have to be added to the involved protocols.
>>
>> 7. If a pair multiplexer/de-multiplexer want to establish a TCMTF session,
>> they have first to use a mechanism to negotiate which concrete option
> would
>> they use in each layer: header compression, multiplexing and tunneling.
> This
>> will depend on the protocols that each extreme implements at each level,
>> and in the scenario. So another document (TCMTF - negotiation protocol)
> will
>> include:
>>
>> - a mechanism to setup/release a TCMTF session between a multiplexer and
>> a de-multiplexer, also including:
>> - a negotiation mechanism to decide the options to use at each layer
> (header
>> compression, multiplexing and tunneling) between multiplexer and de-
>> multiplexer,
>>
>> 8. As a counterpart of the bandwidth saving, TCMTF may add some delay and
>> jitter. This is not a problem for the services which are not sensitive to
> delay.
>> However, regarding delay-sensitive services, the Working Group will also
>> develop a document (TCMTF - recommendations) with useful
>> recommendations in order to decide which packet flows can or can not be
>> multiplexed and how. The document will present a list of available traffic
>> classification methods which can be used for identification of the service
> or
>> application to which a particular flow belongs, as well as recommendations
> of
>> the maximum delay and jitter to be added depending of the identified
>> service or application. The eventual impact of multiplexing on protocol
>> dynamics (e.g., when multiplexing TCP flows) will also have to be
> addressed.
>> 9. If other interesting features are identified, the group would
> re-charter and
>> include them, e.g., a mechanism for a multiplexer to discover a de-
>> multiplexer, and vice versa; a mechanism to select an optimal multiplexer
>> and a de-multiplexer when there are more than one muxer/de-muxer for a
>> flow; dynamically applying TCMTF: a higher entity in charge of deciding
> when
>> and where, applying or not TCMTF, and what kind of TCMTF, and what
>> multiplexing period. Additional methods for estimating delay would also be
>> required.
>>
>> 10. In addition, specific uses of TCMTF, such as in wireless and satellite
>> scenarios, could be considered, and it will be studied whether
> modifications
>> or extensions are required on the protocol.
>>
>> 11. Interactions with other Working Groups can be expected, since TCMTF
>> uses already defined protocols for compression, multiplexing and tunneling
>> (ROHC, PPPMux, MPLS, GRE, L2TP).
>>
>> Goals and Milestones
>>
>> Specification of TCMTF  reference model.
>>
>> Specification of TCMTF negotiation protocol.
>>
>> Specification of TCMTF recommendations of using existing traffic
>> classification methods, maximum delay and jitter to add, depending on the
>> service.
>>
>>
>> Current version of Document (TCMTF - reference model):
>> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>>
>> Current version of Document (TCMTF - recommendations):
>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>>
>>
>> Best regards,
>>
>> Jose
>>
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>
>


From jsaldana@unizar.es  Fri Jun 14 03:52:30 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 363FF21F9C64 for <tcmtf@ietfa.amsl.com>; Fri, 14 Jun 2013 03:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.446
X-Spam-Level: 
X-Spam-Status: No, score=-6.446 tagged_above=-999 required=5 tests=[AWL=0.152,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mRS2i8epqtb0 for <tcmtf@ietfa.amsl.com>; Fri, 14 Jun 2013 03:52:25 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id F258121F9C65 for <tcmtf@ietf.org>; Fri, 14 Jun 2013 03:52:24 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5EAqGbe015146; Fri, 14 Jun 2013 12:52:16 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Fri, 14 Jun 2013 12:52:23 +0200
Organization: Universidad de Zaragoza
Message-ID: <005e01ce68ed$406f58e0$c14e0aa0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005F_01CE68FE.03F89E10"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5o7Ey0jEmmWNZQT7yEwL/TdHe2Dw==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Dan Wing <dwing@cisco.com>
Subject: [tcmtf] Improved description of the BOF proposal
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jun 2013 10:52:30 -0000

This is a multipart message in MIME format.

------=_NextPart_000_005F_01CE68FE.03F89E10
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all.

 

After talking with Dan, we have improved the BOF description. This is the
new proposal:

 

The interactivity requirements of some emerging services (VoIP,
videoconferencing, telemedicine, video vigilance, online gaming, etc.) make
them send high rates of small packets, in order to transmit frequent updates
between the two extremes of the communication. They also demand small
network delays. In addition, some other services also use small packets,
although they are not delay-sensitive (e.g., instant messaging, m2m packets
sending collected data in sensor networks using wireless or satellite
scenarios). For both the delay-sensitive and delay-insensitive applications,
their small data payloads incur significant overhead.

 

When a number of small-packet flows share the same path, bandwidth can be
saved by multiplexing packets belonging to different flows. If a
transmission queue has not already been formed but multiplexing is desired,
it is necessary to add a multiplexing delay, which has to be maintained
under some threshold in order to grant the delay requirements. Some examples
of the scenarios where grouping packets is possible are: 

- aggregation networks of a network operator

- an end-to-end tunnel between appliances located in two different offices
of the same company

- a satellite connection used for collecting the data of a high number of
sensors.

 

 <http://tools.ietf.org/html/rfc4170> RFC4170 (TCRTP) defined a method for
grouping VoIP packets considering three different layers: header compression
by means of ECRTP; multiplexing by means of PPPMux; tunneling by means of
L2TPv3. However, in the last years, emerging real-time services which do not
use UDP/RTP have become popular: some of them use UDP or even TCP. In
addition, new header compression methods have been defined (ROHC). So there
is a need of widening the scope of RFC4170 in order to consider not only
UDP/RTP but also other protocols. The same structure of three layers will be
considered: header compression, multiplexing and tunneling.

 

The BOF aims for 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 (TCMTF).

 

 

Jose 

 


------=_NextPart_000_005F_01CE68FE.03F89E10
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:"Times New Roman","serif";
	color:black;
	mso-fareast-language:ES;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><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 talking with Dan, we have =
improved the BOF description. This is the new =
proposal:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span lang=3DEN-US>The interactivity =
requirements of some emerging services (VoIP, videoconferencing, =
telemedicine, video vigilance, online gaming, etc.) make them send high =
rates of small packets, in order to transmit frequent updates between =
the two extremes of the communication. They also demand small network =
delays. In addition, some other services also use small packets, =
although they are not delay-sensitive (e.g., instant messaging, m2m =
packets sending collected data in sensor networks using wireless or =
satellite scenarios). For both the delay-sensitive and delay-insensitive =
applications, their small data payloads incur significant =
overhead.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span lang=3DEN-US>When a number of =
small-packet flows share the same path, bandwidth can be saved by =
multiplexing packets belonging to different flows. If a transmission =
queue has not already been formed but multiplexing is desired, it is =
necessary to add a multiplexing delay, which has to be maintained under =
some threshold in order to grant the delay requirements. Some examples =
of the scenarios where grouping packets is possible are: =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span lang=3DEN-US>- aggregation networks =
of a network operator<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span lang=3DEN-US>- an end-to-end tunnel =
between appliances located in two different offices of the same =
company<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span lang=3DEN-US>- a satellite connection =
used for collecting the data of a high number of =
sensors.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span lang=3DEN-US><a =
href=3D"http://tools.ietf.org/html/rfc4170"><span =
style=3D'color:purple'>RFC4170</span></a><span =
class=3Dapple-converted-space>&nbsp;</span>(TCRTP) defined a method for =
grouping VoIP packets considering three different layers: header =
compression by means of ECRTP; multiplexing by means of PPPMux; =
tunneling by means of L2TPv3. However, in the last years, emerging =
real-time services which do not use UDP/RTP have become popular: some of =
them use UDP or even TCP. In addition, new header compression methods =
have been defined (ROHC). So there is a need of widening the scope of =
RFC4170 in order to consider not only UDP/RTP but also other protocols. =
The same structure of three layers will be considered: header =
compression, multiplexing and tunneling.</span><span =
lang=3DEN-US><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span lang=3DEN-US>&nbsp;</span><span =
lang=3DEN-US><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-align:justify'><span lang=3DEN-US>The BOF aims for 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 =
(TCMTF).</span><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 =
style=3D'mso-fareast-language:ES'>Jose <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_005F_01CE68FE.03F89E10--


From Mirko.Suznjevic@fer.hr  Fri Jun 14 04:54:13 2013
Return-Path: <Mirko.Suznjevic@fer.hr>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7DA521F9C56; Fri, 14 Jun 2013 04:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.112
X-Spam-Level: 
X-Spam-Status: No, score=-2.112 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03-oMvmB6cMs; Fri, 14 Jun 2013 04:54:09 -0700 (PDT)
Received: from mail.fer.hr (mail.fer.hr [161.53.72.233]) by ietfa.amsl.com (Postfix) with ESMTP id A761D21F9BFE; Fri, 14 Jun 2013 04:54:08 -0700 (PDT)
Received: from MAIL4.fer.hr ([2002:a135:48ea::a135:48ea]) by MAIL.fer.hr ([2002:a135:48e9::a135:48e9]) with mapi id 14.02.0342.003; Fri, 14 Jun 2013 13:54:06 +0200
From: =?iso-8859-2?Q?Mirko_Su=BEnjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: "tcmtf@ietf.org" <tcmtf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: New version of draft-suznjevic-tsvwg-mtd-tcmtf
Thread-Index: Ac5o9d5YwCnm2ioUSW+hBpRYjidpfg==
Date: Fri, 14 Jun 2013 11:54:05 +0000
Message-ID: <E004A7C54DE04F4BB87DB9F32308DA5C0C0E13@MAIL4.fer.hr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.53.19.114]
Content-Type: multipart/alternative; boundary="_000_E004A7C54DE04F4BB87DB9F32308DA5C0C0E13MAIL4ferhr_"
MIME-Version: 1.0
Subject: [tcmtf] New version of draft-suznjevic-tsvwg-mtd-tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jun 2013 11:54:13 -0000

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

Hello,
We have just submitted the new version of draft  draft-suznjevic-tsvwg-mtd-=
tcmtf-01 renamed Delay Limits and Multiplexing Policies to be employed with=
 Tunneling Compressed Multiplexed Traffic Flows http://tools.ietf.org/html/=
draft-suznjevic-tsvwg-mtd-tcmtf-01.
It is an extension of tcmtf http://datatracker.ietf.org/doc/draft-saldana-t=
svwg-tcmtf/. Since a specific list for tcmtf exists (tcmtf@ietf.org<mailto:=
tcmtf@ietf.org>), the idea is to discuss it there.
The draft contains recommendations for TCMTF multiplexing period for differ=
ent network services as well as description of several policies required in=
 the process of packet multiplexing.
We are discussing to revise the draft once more before the IETF meeting in =
Berlin so your feedback will be very welcome. Thank you.
Sincerely,
Mirko Suznjevic


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
2">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"HR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hello,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We have just submitted the new =
version of draft &nbsp;draft-suznjevic-tsvwg-mtd-tcmtf-01 renamed Delay Lim=
its and Multiplexing Policies to be employed with Tunneling Compressed Mult=
iplexed Traffic Flows
</span><a href=3D"http://tools.ietf.org/html/draft-suznjevic-tsvwg-mtd-tcmt=
f-01">http://tools.ietf.org/html/draft-suznjevic-tsvwg-mtd-tcmtf-01</a><spa=
n lang=3D"EN-US">.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">It is an extension of tcmtf <a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a>. Since a spe=
cific list for tcmtf exists (<a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.o=
rg</a>), the idea is to discuss it there.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The draft contains recommendati=
ons for TCMTF multiplexing period for different network services as well as=
 description of several policies required in the process of packet multiple=
xing.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We are discussing to revise the=
 draft once more before the IETF meeting in Berlin so your feedback will be=
 very welcome. Thank you.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Sincerely,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Mirko Suznjevic<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_E004A7C54DE04F4BB87DB9F32308DA5C0C0E13MAIL4ferhr_--

From fpb@tid.es  Fri Jun 14 12:29:42 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C27D21F871D; Fri, 14 Jun 2013 12:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6ViPPO-AW6q; Fri, 14 Jun 2013 12:29:38 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 66BF921F8643; Fri, 14 Jun 2013 12:29:36 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MOE00FAAE58XH@tid.hi.inet>; Fri, 14 Jun 2013 21:29:32 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 8F.9A.03066.C1F6BB15; Fri, 14 Jun 2013 21:29:32 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MOE00FA6E58XH@tid.hi.inet>; Fri, 14 Jun 2013 21:29:32 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Fri, 14 Jun 2013 21:28:39 +0200
Date: Fri, 14 Jun 2013 19:28:38 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <006501ce6812$060676b0$12136410$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A29C8AA7DC@EX10-MB2-MAD.hi.inet>
Content-id: <0A6647B983828C4BB64FAFFCE42D79B9@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Improved version of the tmctf Draft charter (v6)
Thread-index: Ac5oEUJh6X32UcmxT3KmocW8KKc14f//3/+AgAJobQA=
user-agent: Microsoft-MacOutlook/14.3.2.130206
X-AuditID: 0a5f4068-b7fe16d000000bfa-5d-51bb6f1c7cda
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPLMWRmVeSWpSXmKPExsXCFe/ApSuTvzvQ4OdMVYtdnzcwWix4s5jZ gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZGzresRWciq2Y9ryTqYGxzaeLkZNDQsBE4ueNT6wQ tpjEhXvr2boYuTiEBDYySsy4d48NJCEk8JRRou9pMURiGqNEw7JH7CAJFgFVicPbP4J1swlo SZy+u4oFxBYWcJX48PEHWDOngIVE24x97BAbFCT+nHsMViMiUC0xd8EGsBpeAW+J9/cPM4LY zAJmEh9uroCKC0r8mHyPBSKuI9H7/RszhC0u0dx6EyquLfHk3QWwGxgFZCXezZ/PCjHfTeLT hCNQtpXEm9erwHpFBfQkbp5pgfpYQGLJnvPMELaoxMvH/1gnMIrPQnLGLCRnzEJyxiwkZ8xC csYCRtZVjGLFSUWZ6RkluYmZOekGhnoZmXqZeaklmxghkZaxg3H5TpVDjAIcjEo8vBPUdgcK sSaWFVfmHmKU4GBWEuG9qwoU4k1JrKxKLcqPLyrNSS0+xMjEwSnVwLh9ytRvETrux1XUveba WYtZPuEV8JoW+Z4zNplNtONkT8DLl9pXuTyF90jmfhaduVC63MZj9bXcOX9suzonlITxxd9o mWOade2woq2ZUGlNcIDmlbA16u8v3OJPf7Xi8oLrz8vObKiKtFy1b4fzy/1+DZMNrt2bat+8 +c/Fy9fvmyilTrwn463EUpyRaKjFXFScCACm2BnPkgIAAA==
Subject: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jun 2013 19:29:42 -0000

Hi Jose,

        I like all your changes, they all enrich the WG description.

        Nevertheless I wanted to mention, after read carefully the text, th=
at
when we talk about layers, we always use the three terms (tunneling,
multiplexing and compression) and I think it is ok.
        When we talk about the elements in charge of apply the TCMTF protoc=
ol we
have call them multiplexers and demultiplexers, and that may be a little
confusing, given that they use the name of the middle protocol layer, but
I understand that we have not found a better name (I include myself here)
and maybe multiplexing is the most representative layer, so it could be ok.
        But in paragraph 8 we talk about multiplexing flows and the impact =
of
multiplexing in protocol dynamics, and I think that may be confusing,
given that using "multiplexing" we are referring to apply the whole TCMTF
protocol or not and not only to apply the multiplexing layer or not. I=B4m
just saying that this term here may be confusing and someone could get a
bad interpretation from the text. I see three option: a) we pre-define the
term "multiplexing" as the application of the TCMTF protocol itself, b) we
invent the verb "to TCMTF" and use the participle "TCMTFed" when something
is passed trough our protocol stack or c) (and maybe the most convenient
we use the long form "the TCMTF protocol can be applied to that flow" or
"the impact of TCMTF protocol on protocol dynamics". My suggestion is to
use option c).

        What do you think?

        Thank you for your great effort!

Best,

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




On 13/06/13 10:43, "Jose Saldana" <jsaldana@unizar.es> wrote:

>These are the main changes included in the draft charter v6 (ordered by
>paragraphs):
>
>1. I have moved the sentence about the overhead to the end of the
>paragraph,
>in order to say that =B3For both the delay-sensitive and delay-insensitive
>applications, their small data payloads incur significant overhead=B2
>
>2. I have put the scenarios in bullets, and I have improved some of the
>descriptions a bit.
>
>6. I have changed the name of the document: instead of =B3document A=B2 it=
 is
>now =B3TCMTF =AD reference model=B2.
>
>7. Now we are talking about another document =B3TCMTF =AD negotiation
>protocol=B2.
>In addition, I have put the two signaling functionalities in bullets.
>
>7. As discussed in the list, we would talk about =B3setup/release a TCMTF
>session=B2.
>
>8. I have changed the name of the document, from =B3document B=B2 to =B3TC=
MTF
>recommendations=B2
>
>8. According to Gorry=B9s suggestion, I have added this sentence: =B3The
>eventual impact of multiplexing on protocol dynamics (e.g. when
>multiplexing
>TCP flows) will also have to be addressed.=B2
>
>Jose
>
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Jose Saldana
>> Enviado el: jueves, 13 de junio de 2013 10:38
>> Para: tcmtf@ietf.org; tsv-area@ietf.org
>> Asunto: [tcmtf] Improved version of the tmctf Draft charter (v6)
>>
>> This is the new proposal, adapted to the new distribution of the
>documents.
>> I explain the changes in another e-mail.
>> It is also here, in a formatted version:
>> http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf
>>
>>
>> TCMTF charter draft v6
>>
>> Description of Working Group
>>
>> 1. In the last years we are witnessing the raise of new real-time
>>services
>that
>> use the Internet for the delivery of interactive multimedia
>> applications: VoIP, videoconferencing, telemedicine, video vigilance,
>online
>> gaming, etc. Due to the need of interactivity, many of these services
>>use
>> small packets (some tens of bytes), since they have to send frequent
>> updates between the extremes of the communication. In addition, some
>> other services also send small packets, but they are not delay-sensitive
>(e.g.,
>> instant messaging, m2m packets sending collected data in sensor networks
>> using wireless or satellite scenarios). For both the delay-sensitive and
>delay-
>> insensitive applications, their small data payloads incur significant
>overhead,
>> and it becomes even higher when IPv6 is used, since the basic IPv6
>>header
>is
>> twice the size of the IPv4 one.
>>
>> 2. The efficiency cannot be increased by the inclusion of a higher
>>number
>of
>> samples in a single packet, since this would harm the delay requirements
>of
>> the service. But there exist some scenarios in which a number of flows
>share
>> the same path. In this case, packets belonging to different flows can be
>> grouped together, adding a small multiplexing delay as a counterpart of
>> bandwidth saving. This delay will have to be maintained under some
>> threshold in order to grant the delay requirements. Some examples of the
>> scenarios where grouping packets is possible are:
>>
>> - aggregation networks of a network operator;
>> - an end-to-end tunnel between appliances located in two different
>>offices
>> of the same company;
>> - the access connection of an Internet Caf=E9 including a high number of
>> VoIP/gaming flows;
>> - an agreement between two network operators could allow them to
>> compress a number of flows they are exchanging between a pair of
>>Internet
>> Routers;
>> - a satellite connection used for collecting the data of a high number
>>of
>> sensors.
>>
>> 3. VoIP using RTP is a clear example of a real-time service using small
>packets
>> with high overhead. In order to improve efficiency, RFC4170 (TCRTP)
>defined
>> a method for grouping packets when a number of flows share a path,
>> considering three different layers: header compression by means of
>>ECRTP;
>> multiplexing by means of PPPMux; tunneling by means of L2TPv3.
>>
>> 4. However, in the last years, emerging real-time services which do not
>use
>> UDP/RTP have become popular: some of them use UDP or even TCP. In
>> addition, new header compression methods have been defined (ROHC). So
>> there is a need of widening the scope of RFC4170 in order to consider
>>not
>> only UDP/RTP but also other protocols. The same structure of three
>>layers
>> will be considered:
>>
>> - Header compression: Taking into account that real-time applications
>>use
>> different headers (RTP/UDP, UDP or even TCP), different protocols can be
>> used: no compression, ECRTP, IPHC and ROHC.
>> - Multiplexing: If a number of flows share a path between an origin and
>>a
>> destination, a multiplexer can build a bigger packet in which a number
>>of
>> payloads share a common header. A demultiplexer is then necessary at the
>> end of the common path, so as to rebuild the packets as they were
>originally
>> sent. PPPMux will be the main option. Other ones are not discarded.
>> - Tunneling will be used to send the multiplexed packets end-to-end. The
>> options in this layer are L2TP, GRE and MPLS.
>>
>> 5. So the first objective of this group is to specify the protocol stack
>for
>> tunneling, compressing and multiplexing traffic flows (TCMTF). Since
>> standard protocols are being used at each layer, the signaling methods
>>of
>> those protocols will be used. Interactions with the Working Groups and
>Areas
>> in which these protocols are developed can be expected. However, the
>> development of new compressing, multiplexing or tunneling protocols is
>>not
>> an objective of this Working Group. In addition, since the current RFC
>4170
>> would be considered as one of the options, this RFC could be obsoleted.
>>
>> 6. As a first objective, a document (TCMTF - reference model) will
>>define
>the
>> different options which can be used at each layer. Specific problems
>caused
>> by the interaction between layers will have to be issued, and suitable
>> extensions may have to be added to the involved protocols.
>>
>> 7. If a pair multiplexer/de-multiplexer want to establish a TCMTF
>>session,
>> they have first to use a mechanism to negotiate which concrete option
>would
>> they use in each layer: header compression, multiplexing and tunneling.
>This
>> will depend on the protocols that each extreme implements at each level,
>> and in the scenario. So another document (TCMTF - negotiation protocol)
>will
>> include:
>>
>> - a mechanism to setup/release a TCMTF session between a multiplexer and
>> a de-multiplexer, also including:
>> - a negotiation mechanism to decide the options to use at each layer
>(header
>> compression, multiplexing and tunneling) between multiplexer and de-
>> multiplexer,
>>
>> 8. As a counterpart of the bandwidth saving, TCMTF may add some delay
>>and
>> jitter. This is not a problem for the services which are not sensitive
>>to
>delay.
>> However, regarding delay-sensitive services, the Working Group will also
>> develop a document (TCMTF - recommendations) with useful
>> recommendations in order to decide which packet flows can or can not be
>> multiplexed and how. The document will present a list of available
>>traffic
>> classification methods which can be used for identification of the
>>service
>or
>> application to which a particular flow belongs, as well as
>>recommendations
>of
>> the maximum delay and jitter to be added depending of the identified
>> service or application. The eventual impact of multiplexing on protocol
>> dynamics (e.g., when multiplexing TCP flows) will also have to be
>addressed.
>>
>> 9. If other interesting features are identified, the group would
>re-charter and
>> include them, e.g., a mechanism for a multiplexer to discover a de-
>> multiplexer, and vice versa; a mechanism to select an optimal
>>multiplexer
>> and a de-multiplexer when there are more than one muxer/de-muxer for a
>> flow; dynamically applying TCMTF: a higher entity in charge of deciding
>when
>> and where, applying or not TCMTF, and what kind of TCMTF, and what
>> multiplexing period. Additional methods for estimating delay would also
>>be
>> required.
>>
>> 10. In addition, specific uses of TCMTF, such as in wireless and
>>satellite
>> scenarios, could be considered, and it will be studied whether
>modifications
>> or extensions are required on the protocol.
>>
>> 11. Interactions with other Working Groups can be expected, since TCMTF
>> uses already defined protocols for compression, multiplexing and
>>tunneling
>> (ROHC, PPPMux, MPLS, GRE, L2TP).
>>
>> Goals and Milestones
>>
>> Specification of TCMTF  reference model.
>>
>> Specification of TCMTF negotiation protocol.
>>
>> Specification of TCMTF recommendations of using existing traffic
>> classification methods, maximum delay and jitter to add, depending on
>>the
>> service.
>>
>>
>> Current version of Document (TCMTF - reference model):
>> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>>
>> Current version of Document (TCMTF - recommendations):
>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>>
>>
>> Best regards,
>>
>> Jose
>>
>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>
>_______________________________________________
>tcmtf mailing list
>tcmtf@ietf.org
>https://www.ietf.org/mailman/listinfo/tcmtf


________________________________

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

From jsaldana@unizar.es  Mon Jun 17 00:32:31 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4EDC21F9AA2; Mon, 17 Jun 2013 00:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.459
X-Spam-Level: 
X-Spam-Status: No, score=-6.459 tagged_above=-999 required=5 tests=[AWL=0.140,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3o-1K9J-WY7M; Mon, 17 Jun 2013 00:32:25 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4E3A721F9A79; Mon, 17 Jun 2013 00:32:23 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5H7VmAl023833; Mon, 17 Jun 2013 09:31:57 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'FERNANDO PASCUAL BLANCO'" <fpb@tid.es>, <tcmtf@ietf.org>, <tsv-area@ietf.org>
References: <006501ce6812$060676b0$12136410$@unizar.es> <F5EDC35DF914C1428C28E149F10463A29C8AA7DC@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A29C8AA7DC@EX10-MB2-MAD.hi.inet>
Date: Mon, 17 Jun 2013 09:31:49 +0200
Organization: Universidad de Zaragoza
Message-ID: <004a01ce6b2c$c640ed80$52c2c880$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQCxHvivfYQiVdXTBQska4oYY5UEFpt0F+mg
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2013 07:32:31 -0000

Hi, Fernando.

I agree with you. We are talking about standards so precision is =
important.

I don't think we should use the "verb" "to TCMTF" nor "TCMTFing" nor
"TCMTFed". We cannot invent new English verbs.

What about "optimization"?. This concept summarizes the three layers. We =
can
use it this way:

- A TCMTF optimizer

- A packet optimized by means of TCMTF
- A flow optimized by means of TCMTF
- An optimized packet
- An optimized flow
- A TCMTF-optimized packet
- A TCMTF-optimized flow
- A TCMTF packet
- A TCMTF flow

- the TCMTF optimization can be applied to that flow
- the impact of TCMTF optimization on protocol dynamics

I have another question here: could we use only TCM instead of TCMTF?
Remember that TF means "traffic flows", so a TCMTF flow would be a
"tunneling compressed multiplexed traffic flows flow". Perhaps a TCM =
flow
would be enough in those cases. TCM does not have another related =
meaning
and it is shorter than TCMTF (http://www.acronymfinder.com/TCM.html)

- A TCM optimizer
- A TCM-optimized flow
- A TCM flow

What do you think?

Jose

> -----Mensaje original-----
> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
> Enviado el: viernes, 14 de junio de 2013 21:29
> Para: jsaldana@unizar.es; tcmtf@ietf.org; tsv-area@ietf.org
> Asunto: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
>=20
> Hi Jose,
>=20
>         I like all your changes, they all enrich the WG description.
>=20
>         Nevertheless I wanted to mention, after read carefully the =
text,
that
> when we talk about layers, we always use the three terms (tunneling,
> multiplexing and compression) and I think it is ok.
>         When we talk about the elements in charge of apply the TCMTF
protocol
> we have call them multiplexers and demultiplexers, and that may be a
little
> confusing, given that they use the name of the middle protocol layer, =
but
I
> understand that we have not found a better name (I include myself =
here)
> and maybe multiplexing is the most representative layer, so it could =
be
ok.
>         But in paragraph 8 we talk about multiplexing flows and the =
impact
of
> multiplexing in protocol dynamics, and I think that may be confusing,
given
> that using "multiplexing" we are referring to apply the whole TCMTF
protocol
> or not and not only to apply the multiplexing layer or not. I=B4m just
saying that
> this term here may be confusing and someone could get a bad =
interpretation
> from the text. I see three option: a) we pre-define the term
"multiplexing"
> as the application of the TCMTF protocol itself, b) we invent the verb =
"to
> TCMTF" and use the participle "TCMTFed" when something is passed =
trough
> our protocol stack or c) (and maybe the most convenient we use the =
long
> form "the TCMTF protocol can be applied to that flow" or "the impact =
of
> TCMTF protocol on protocol dynamics". My suggestion is to use option =
c).
>=20
>         What do you think?
>=20
>         Thank you for your great effort!
>=20
> Best,
>=20
> Fernando Pascual Blanco
> Telef=F3nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>=20
>=20
>=20
>=20
> On 13/06/13 10:43, "Jose Saldana" <jsaldana@unizar.es> wrote:
>=20
> >These are the main changes included in the draft charter v6 (ordered =
by
> >paragraphs):
> >
> >1. I have moved the sentence about the overhead to the end of the
> >paragraph, in order to say that =B3For both the delay-sensitive and
> >delay-insensitive applications, their small data payloads incur
> >significant overhead=B2
> >
> >2. I have put the scenarios in bullets, and I have improved some of =
the
> >descriptions a bit.
> >
> >6. I have changed the name of the document: instead of =B3document =
A=B2 it
> >is now =B3TCMTF =AD reference model=B2.
> >
> >7. Now we are talking about another document =B3TCMTF =AD negotiation
> >protocol=B2.
> >In addition, I have put the two signaling functionalities in bullets.
> >
> >7. As discussed in the list, we would talk about =B3setup/release a =
TCMTF
> >session=B2.
> >
> >8. I have changed the name of the document, from =B3document B=B2 to
> =B3TCMTF
> >recommendations=B2
> >
> >8. According to Gorry=B9s suggestion, I have added this sentence: =
=B3The
> >eventual impact of multiplexing on protocol dynamics (e.g. when
> >multiplexing TCP flows) will also have to be addressed.=B2
> >
> >Jose
> >
> >
> >> -----Mensaje original-----
> >> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En =
nombre
> >> de Jose Saldana Enviado el: jueves, 13 de junio de 2013 10:38
> >> Para: tcmtf@ietf.org; tsv-area@ietf.org
> >> Asunto: [tcmtf] Improved version of the tmctf Draft charter (v6)
> >>
> >> This is the new proposal, adapted to the new distribution of the
> >documents.
> >> I explain the changes in another e-mail.
> >> It is also here, in a formatted version:
> >> =
http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf
> >>
> >>
> >> TCMTF charter draft v6
> >>
> >> Description of Working Group
> >>
> >> 1. In the last years we are witnessing the raise of new real-time
> >>services
> >that
> >> use the Internet for the delivery of interactive multimedia
> >> applications: VoIP, videoconferencing, telemedicine, video =
vigilance,
> >online
> >> gaming, etc. Due to the need of interactivity, many of these =
services
> >>use  small packets (some tens of bytes), since they have to send
> >>frequent  updates between the extremes of the communication. In
> >>addition, some  other services also send small packets, but they are
> >>not delay-sensitive
> >(e.g.,
> >> instant messaging, m2m packets sending collected data in sensor
> >> networks using wireless or satellite scenarios). For both the
> >> delay-sensitive and
> >delay-
> >> insensitive applications, their small data payloads incur =
significant
> >overhead,
> >> and it becomes even higher when IPv6 is used, since the basic IPv6
> >>header
> >is
> >> twice the size of the IPv4 one.
> >>
> >> 2. The efficiency cannot be increased by the inclusion of a higher
> >>number
> >of
> >> samples in a single packet, since this would harm the delay
> >> requirements
> >of
> >> the service. But there exist some scenarios in which a number of
> >> flows
> >share
> >> the same path. In this case, packets belonging to different flows =
can
> >> be grouped together, adding a small multiplexing delay as a
> >> counterpart of bandwidth saving. This delay will have to be
> >> maintained under some threshold in order to grant the delay
> >> requirements. Some examples of the scenarios where grouping packets =
is
> possible are:
> >>
> >> - aggregation networks of a network operator;
> >> - an end-to-end tunnel between appliances located in two different
> >>offices  of the same company;
> >> - the access connection of an Internet Caf=E9 including a high =
number
> >>of  VoIP/gaming flows;
> >> - an agreement between two network operators could allow them to
> >>compress a number of flows they are exchanging between a pair of
> >>Internet  Routers;
> >> - a satellite connection used for collecting the data of a high
> >>number of  sensors.
> >>
> >> 3. VoIP using RTP is a clear example of a real-time service using
> >> small
> >packets
> >> with high overhead. In order to improve efficiency, RFC4170 (TCRTP)
> >defined
> >> a method for grouping packets when a number of flows share a path,
> >>considering three different layers: header compression by means of
> >>ECRTP;  multiplexing by means of PPPMux; tunneling by means of =
L2TPv3.
> >>
> >> 4. However, in the last years, emerging real-time services which do
> >> not
> >use
> >> UDP/RTP have become popular: some of them use UDP or even TCP. In
> >>addition, new header compression methods have been defined (ROHC).
> So
> >>there is a need of widening the scope of RFC4170 in order to =
consider
> >>not  only UDP/RTP but also other protocols. The same structure of
> >>three layers  will be considered:
> >>
> >> - Header compression: Taking into account that real-time =
applications
> >>use  different headers (RTP/UDP, UDP or even TCP), different =
protocols
> >>can be
> >> used: no compression, ECRTP, IPHC and ROHC.
> >> - Multiplexing: If a number of flows share a path between an origin
> >>and a  destination, a multiplexer can build a bigger packet in which =
a
> >>number of  payloads share a common header. A demultiplexer is then
> >>necessary at the  end of the common path, so as to rebuild the =
packets
> >>as they were
> >originally
> >> sent. PPPMux will be the main option. Other ones are not discarded.
> >> - Tunneling will be used to send the multiplexed packets =
end-to-end.
> >> The options in this layer are L2TP, GRE and MPLS.
> >>
> >> 5. So the first objective of this group is to specify the protocol
> >> stack
> >for
> >> tunneling, compressing and multiplexing traffic flows (TCMTF). =
Since
> >>standard protocols are being used at each layer, the signaling =
methods
> >>of  those protocols will be used. Interactions with the Working =
Groups
> >>and
> >Areas
> >> in which these protocols are developed can be expected. However, =
the
> >>development of new compressing, multiplexing or tunneling protocols =
is
> >>not  an objective of this Working Group. In addition, since the
> >>current RFC
> >4170
> >> would be considered as one of the options, this RFC could be =
obsoleted.
> >>
> >> 6. As a first objective, a document (TCMTF - reference model) will
> >>define
> >the
> >> different options which can be used at each layer. Specific =
problems
> >caused
> >> by the interaction between layers will have to be issued, and
> >> suitable extensions may have to be added to the involved protocols.
> >>
> >> 7. If a pair multiplexer/de-multiplexer want to establish a TCMTF
> >>session,  they have first to use a mechanism to negotiate which
> >>concrete option
> >would
> >> they use in each layer: header compression, multiplexing and =
tunneling.
> >This
> >> will depend on the protocols that each extreme implements at each
> >> level, and in the scenario. So another document (TCMTF - =
negotiation
> >> protocol)
> >will
> >> include:
> >>
> >> - a mechanism to setup/release a TCMTF session between a =
multiplexer
> >> and a de-multiplexer, also including:
> >> - a negotiation mechanism to decide the options to use at each =
layer
> >(header
> >> compression, multiplexing and tunneling) between multiplexer and =
de-
> >> multiplexer,
> >>
> >> 8. As a counterpart of the bandwidth saving, TCMTF may add some =
delay
> >>and  jitter. This is not a problem for the services which are not
> >>sensitive to
> >delay.
> >> However, regarding delay-sensitive services, the Working Group will
> >>also  develop a document (TCMTF - recommendations) with useful
> >>recommendations in order to decide which packet flows can or can not
> >>be  multiplexed and how. The document will present a list of =
available
> >>traffic  classification methods which can be used for identification
> >>of the service
> >or
> >> application to which a particular flow belongs, as well as
> >>recommendations
> >of
> >> the maximum delay and jitter to be added depending of the =
identified
> >> service or application. The eventual impact of multiplexing on
> >> protocol dynamics (e.g., when multiplexing TCP flows) will also =
have
> >> to be
> >addressed.
> >>
> >> 9. If other interesting features are identified, the group would
> >re-charter and
> >> include them, e.g., a mechanism for a multiplexer to discover a de-
> >>multiplexer, and vice versa; a mechanism to select an optimal
> >>multiplexer  and a de-multiplexer when there are more than one
> >>muxer/de-muxer for a  flow; dynamically applying TCMTF: a higher
> >>entity in charge of deciding
> >when
> >> and where, applying or not TCMTF, and what kind of TCMTF, and what
> >>multiplexing period. Additional methods for estimating delay would
> >>also be  required.
> >>
> >> 10. In addition, specific uses of TCMTF, such as in wireless and
> >>satellite  scenarios, could be considered, and it will be studied
> >>whether
> >modifications
> >> or extensions are required on the protocol.
> >>
> >> 11. Interactions with other Working Groups can be expected, since
> >>TCMTF  uses already defined protocols for compression, multiplexing
> >>and tunneling  (ROHC, PPPMux, MPLS, GRE, L2TP).
> >>
> >> Goals and Milestones
> >>
> >> Specification of TCMTF  reference model.
> >>
> >> Specification of TCMTF negotiation protocol.
> >>
> >> Specification of TCMTF recommendations of using existing traffic
> >>classification methods, maximum delay and jitter to add, depending =
on
> >>the  service.
> >>
> >>
> >> Current version of Document (TCMTF - reference model):
> >> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
> >>
> >> Current version of Document (TCMTF - recommendations):
> >> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
> >>
> >>
> >> Best regards,
> >>
> >> Jose
> >>
> >>
> >> _______________________________________________
> >> tcmtf mailing list
> >> tcmtf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tcmtf
> >
> >_______________________________________________
> >tcmtf mailing list
> >tcmtf@ietf.org
> >https://www.ietf.org/mailman/listinfo/tcmtf
>=20
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar
> nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en =
el enlace
> situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send =
and
> receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx


From navajas@unizar.es  Mon Jun 17 02:03:01 2013
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13FD821F9ADA for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 02:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ribT6niFbMCS for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 02:02:56 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6859321F9B2D for <tcmtf@ietf.org>; Mon, 17 Jun 2013 02:02:51 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5H92L2u005856 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Mon, 17 Jun 2013 11:02:27 +0200
Message-ID: <51BED09F.1010807@unizar.es>
Date: Mon, 17 Jun 2013 11:02:23 +0200
From: =?UTF-8?B?SnVsacOhbiBGZXJuw6FuZGV6LU5hdmFqYXM=?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <006501ce6812$060676b0$12136410$@unizar.es> <F5EDC35DF914C1428C28E149F10463A29C8AA7DC@EX10-MB2-MAD.hi.inet> <004a01ce6b2c$c640ed80$52c2c880$@unizar.es>
In-Reply-To: <004a01ce6b2c$c640ed80$52c2c880$@unizar.es>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2013 09:03:02 -0000

I agree with Fernando too, no invent new English verb.
In relation with duplicating flow word, i think that it is fine to use 
"TCM flow" instead of "TCMTF flow".
JuliÃ¡n

El 17/06/2013 9:31, Jose Saldana escribiÃ³:
> Hi, Fernando.
>
> I agree with you. We are talking about standards so precision is important.
>
> I don't think we should use the "verb" "to TCMTF" nor "TCMTFing" nor
> "TCMTFed". We cannot invent new English verbs.
>
> What about "optimization"?. This concept summarizes the three layers. We can
> use it this way:
>
> - A TCMTF optimizer
>
> - A packet optimized by means of TCMTF
> - A flow optimized by means of TCMTF
> - An optimized packet
> - An optimized flow
> - A TCMTF-optimized packet
> - A TCMTF-optimized flow
> - A TCMTF packet
> - A TCMTF flow
>
> - the TCMTF optimization can be applied to that flow
> - the impact of TCMTF optimization on protocol dynamics
>
> I have another question here: could we use only TCM instead of TCMTF?
> Remember that TF means "traffic flows", so a TCMTF flow would be a
> "tunneling compressed multiplexed traffic flows flow". Perhaps a TCM flow
> would be enough in those cases. TCM does not have another related meaning
> and it is shorter than TCMTF (http://www.acronymfinder.com/TCM.html)
>
> - A TCM optimizer
> - A TCM-optimized flow
> - A TCM flow
>
> What do you think?
>
> Jose
>
>> -----Mensaje original-----
>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>> Enviado el: viernes, 14 de junio de 2013 21:29
>> Para: jsaldana@unizar.es; tcmtf@ietf.org; tsv-area@ietf.org
>> Asunto: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
>>
>> Hi Jose,
>>
>>          I like all your changes, they all enrich the WG description.
>>
>>          Nevertheless I wanted to mention, after read carefully the text,
> that
>> when we talk about layers, we always use the three terms (tunneling,
>> multiplexing and compression) and I think it is ok.
>>          When we talk about the elements in charge of apply the TCMTF
> protocol
>> we have call them multiplexers and demultiplexers, and that may be a
> little
>> confusing, given that they use the name of the middle protocol layer, but
> I
>> understand that we have not found a better name (I include myself here)
>> and maybe multiplexing is the most representative layer, so it could be
> ok.
>>          But in paragraph 8 we talk about multiplexing flows and the impact
> of
>> multiplexing in protocol dynamics, and I think that may be confusing,
> given
>> that using "multiplexing" we are referring to apply the whole TCMTF
> protocol
>> or not and not only to apply the multiplexing layer or not. IÂ´m just
> saying that
>> this term here may be confusing and someone could get a bad interpretation
>> from the text. I see three option: a) we pre-define the term
> "multiplexing"
>> as the application of the TCMTF protocol itself, b) we invent the verb "to
>> TCMTF" and use the participle "TCMTFed" when something is passed trough
>> our protocol stack or c) (and maybe the most convenient we use the long
>> form "the TCMTF protocol can be applied to that flow" or "the impact of
>> TCMTF protocol on protocol dynamics". My suggestion is to use option c).
>>
>>          What do you think?
>>
>>          Thank you for your great effort!
>>
>> Best,
>>
>> Fernando Pascual Blanco
>> TelefÃ³nica Global Resources
>> Network Automation and Dynamization
>> TECHNOLOGY PEOPLE GROUP
>> F +34913128779
>> M +34682005168
>> fpb@tid.es
>>
>>
>>
>>
>> On 13/06/13 10:43, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>
>>> These are the main changes included in the draft charter v6 (ordered by
>>> paragraphs):
>>>
>>> 1. I have moved the sentence about the overhead to the end of the
>>> paragraph, in order to say that Â³For both the delay-sensitive and
>>> delay-insensitive applications, their small data payloads incur
>>> significant overheadÂ²
>>>
>>> 2. I have put the scenarios in bullets, and I have improved some of the
>>> descriptions a bit.
>>>
>>> 6. I have changed the name of the document: instead of Â³document AÂ² it
>>> is now Â³TCMTF Â­ reference modelÂ².
>>>
>>> 7. Now we are talking about another document Â³TCMTF Â­ negotiation
>>> protocolÂ².
>>> In addition, I have put the two signaling functionalities in bullets.
>>>
>>> 7. As discussed in the list, we would talk about Â³setup/release a TCMTF
>>> sessionÂ².
>>>
>>> 8. I have changed the name of the document, from Â³document BÂ² to
>> Â³TCMTF
>>> recommendationsÂ²
>>>
>>> 8. According to GorryÂ¹s suggestion, I have added this sentence: Â³The
>>> eventual impact of multiplexing on protocol dynamics (e.g. when
>>> multiplexing TCP flows) will also have to be addressed.Â²
>>>
>>> Jose
>>>
>>>
>>>> -----Mensaje original-----
>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>>>> de Jose Saldana Enviado el: jueves, 13 de junio de 2013 10:38
>>>> Para: tcmtf@ietf.org; tsv-area@ietf.org
>>>> Asunto: [tcmtf] Improved version of the tmctf Draft charter (v6)
>>>>
>>>> This is the new proposal, adapted to the new distribution of the
>>> documents.
>>>> I explain the changes in another e-mail.
>>>> It is also here, in a formatted version:
>>>> http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf
>>>>
>>>>
>>>> TCMTF charter draft v6
>>>>
>>>> Description of Working Group
>>>>
>>>> 1. In the last years we are witnessing the raise of new real-time
>>>> services
>>> that
>>>> use the Internet for the delivery of interactive multimedia
>>>> applications: VoIP, videoconferencing, telemedicine, video vigilance,
>>> online
>>>> gaming, etc. Due to the need of interactivity, many of these services
>>>> use  small packets (some tens of bytes), since they have to send
>>>> frequent  updates between the extremes of the communication. In
>>>> addition, some  other services also send small packets, but they are
>>>> not delay-sensitive
>>> (e.g.,
>>>> instant messaging, m2m packets sending collected data in sensor
>>>> networks using wireless or satellite scenarios). For both the
>>>> delay-sensitive and
>>> delay-
>>>> insensitive applications, their small data payloads incur significant
>>> overhead,
>>>> and it becomes even higher when IPv6 is used, since the basic IPv6
>>>> header
>>> is
>>>> twice the size of the IPv4 one.
>>>>
>>>> 2. The efficiency cannot be increased by the inclusion of a higher
>>>> number
>>> of
>>>> samples in a single packet, since this would harm the delay
>>>> requirements
>>> of
>>>> the service. But there exist some scenarios in which a number of
>>>> flows
>>> share
>>>> the same path. In this case, packets belonging to different flows can
>>>> be grouped together, adding a small multiplexing delay as a
>>>> counterpart of bandwidth saving. This delay will have to be
>>>> maintained under some threshold in order to grant the delay
>>>> requirements. Some examples of the scenarios where grouping packets is
>> possible are:
>>>> - aggregation networks of a network operator;
>>>> - an end-to-end tunnel between appliances located in two different
>>>> offices  of the same company;
>>>> - the access connection of an Internet CafÃ© including a high number
>>>> of  VoIP/gaming flows;
>>>> - an agreement between two network operators could allow them to
>>>> compress a number of flows they are exchanging between a pair of
>>>> Internet  Routers;
>>>> - a satellite connection used for collecting the data of a high
>>>> number of  sensors.
>>>>
>>>> 3. VoIP using RTP is a clear example of a real-time service using
>>>> small
>>> packets
>>>> with high overhead. In order to improve efficiency, RFC4170 (TCRTP)
>>> defined
>>>> a method for grouping packets when a number of flows share a path,
>>>> considering three different layers: header compression by means of
>>>> ECRTP;  multiplexing by means of PPPMux; tunneling by means of L2TPv3.
>>>>
>>>> 4. However, in the last years, emerging real-time services which do
>>>> not
>>> use
>>>> UDP/RTP have become popular: some of them use UDP or even TCP. In
>>>> addition, new header compression methods have been defined (ROHC).
>> So
>>>> there is a need of widening the scope of RFC4170 in order to consider
>>>> not  only UDP/RTP but also other protocols. The same structure of
>>>> three layers  will be considered:
>>>>
>>>> - Header compression: Taking into account that real-time applications
>>>> use  different headers (RTP/UDP, UDP or even TCP), different protocols
>>>> can be
>>>> used: no compression, ECRTP, IPHC and ROHC.
>>>> - Multiplexing: If a number of flows share a path between an origin
>>>> and a  destination, a multiplexer can build a bigger packet in which a
>>>> number of  payloads share a common header. A demultiplexer is then
>>>> necessary at the  end of the common path, so as to rebuild the packets
>>>> as they were
>>> originally
>>>> sent. PPPMux will be the main option. Other ones are not discarded.
>>>> - Tunneling will be used to send the multiplexed packets end-to-end.
>>>> The options in this layer are L2TP, GRE and MPLS.
>>>>
>>>> 5. So the first objective of this group is to specify the protocol
>>>> stack
>>> for
>>>> tunneling, compressing and multiplexing traffic flows (TCMTF). Since
>>>> standard protocols are being used at each layer, the signaling methods
>>>> of  those protocols will be used. Interactions with the Working Groups
>>>> and
>>> Areas
>>>> in which these protocols are developed can be expected. However, the
>>>> development of new compressing, multiplexing or tunneling protocols is
>>>> not  an objective of this Working Group. In addition, since the
>>>> current RFC
>>> 4170
>>>> would be considered as one of the options, this RFC could be obsoleted.
>>>>
>>>> 6. As a first objective, a document (TCMTF - reference model) will
>>>> define
>>> the
>>>> different options which can be used at each layer. Specific problems
>>> caused
>>>> by the interaction between layers will have to be issued, and
>>>> suitable extensions may have to be added to the involved protocols.
>>>>
>>>> 7. If a pair multiplexer/de-multiplexer want to establish a TCMTF
>>>> session,  they have first to use a mechanism to negotiate which
>>>> concrete option
>>> would
>>>> they use in each layer: header compression, multiplexing and tunneling.
>>> This
>>>> will depend on the protocols that each extreme implements at each
>>>> level, and in the scenario. So another document (TCMTF - negotiation
>>>> protocol)
>>> will
>>>> include:
>>>>
>>>> - a mechanism to setup/release a TCMTF session between a multiplexer
>>>> and a de-multiplexer, also including:
>>>> - a negotiation mechanism to decide the options to use at each layer
>>> (header
>>>> compression, multiplexing and tunneling) between multiplexer and de-
>>>> multiplexer,
>>>>
>>>> 8. As a counterpart of the bandwidth saving, TCMTF may add some delay
>>>> and  jitter. This is not a problem for the services which are not
>>>> sensitive to
>>> delay.
>>>> However, regarding delay-sensitive services, the Working Group will
>>>> also  develop a document (TCMTF - recommendations) with useful
>>>> recommendations in order to decide which packet flows can or can not
>>>> be  multiplexed and how. The document will present a list of available
>>>> traffic  classification methods which can be used for identification
>>>> of the service
>>> or
>>>> application to which a particular flow belongs, as well as
>>>> recommendations
>>> of
>>>> the maximum delay and jitter to be added depending of the identified
>>>> service or application. The eventual impact of multiplexing on
>>>> protocol dynamics (e.g., when multiplexing TCP flows) will also have
>>>> to be
>>> addressed.
>>>> 9. If other interesting features are identified, the group would
>>> re-charter and
>>>> include them, e.g., a mechanism for a multiplexer to discover a de-
>>>> multiplexer, and vice versa; a mechanism to select an optimal
>>>> multiplexer  and a de-multiplexer when there are more than one
>>>> muxer/de-muxer for a  flow; dynamically applying TCMTF: a higher
>>>> entity in charge of deciding
>>> when
>>>> and where, applying or not TCMTF, and what kind of TCMTF, and what
>>>> multiplexing period. Additional methods for estimating delay would
>>>> also be  required.
>>>>
>>>> 10. In addition, specific uses of TCMTF, such as in wireless and
>>>> satellite  scenarios, could be considered, and it will be studied
>>>> whether
>>> modifications
>>>> or extensions are required on the protocol.
>>>>
>>>> 11. Interactions with other Working Groups can be expected, since
>>>> TCMTF  uses already defined protocols for compression, multiplexing
>>>> and tunneling  (ROHC, PPPMux, MPLS, GRE, L2TP).
>>>>
>>>> Goals and Milestones
>>>>
>>>> Specification of TCMTF  reference model.
>>>>
>>>> Specification of TCMTF negotiation protocol.
>>>>
>>>> Specification of TCMTF recommendations of using existing traffic
>>>> classification methods, maximum delay and jitter to add, depending on
>>>> the  service.
>>>>
>>>>
>>>> Current version of Document (TCMTF - reference model):
>>>> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>>>>
>>>> Current version of Document (TCMTF - recommendations):
>>>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> Jose
>>>>
>>>>
>>>> _______________________________________________
>>>> tcmtf mailing list
>>>> tcmtf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>
>> ________________________________
>>
>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>> nuestra polÃ­tica de envÃ­o y recepciÃ³n de correo electrÃ³nico en el enlace
>> situado mÃ¡s abajo.
>> This message is intended exclusively for its addressee. We only send and
>> receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>
>


From fpb@tid.es  Mon Jun 17 02:13:34 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A53221F9B34 for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 02:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.337
X-Spam-Level: 
X-Spam-Status: No, score=-6.337 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nbi4cDCzsi0v for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 02:13:29 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id E38ED21F9B3C for <tcmtf@ietf.org>; Mon, 17 Jun 2013 02:13:15 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MOJ00GT85M2DY@tid.hi.inet> for tcmtf@ietf.org; Mon, 17 Jun 2013 11:13:14 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 4B.ED.03066.A23DEB15; Mon, 17 Jun 2013 11:13:14 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MOJ00GT45M2DY@tid.hi.inet> for tcmtf@ietf.org; Mon, 17 Jun 2013 11:13:14 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS8-MAD.hi.inet ([fe80::41c8:e965:8a6:de67%11]) with mapi id 14.02.0328.009; Mon, 17 Jun 2013 11:13:14 +0200
Date: Mon, 17 Jun 2013 09:12:17 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <51BED09F.1010807@unizar.es>
X-Originating-IP: [10.95.64.115]
To: =?utf-8?B?SnVsacOhbiBGZXJuw6FuZGV6LU5hdmFqYXM=?= <navajas@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A29C8ABCAE@EX10-MB2-MAD.hi.inet>
Content-id: <6AD89B7A3EEE12469CE8A4A0F2E18192@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Improved version of the tmctf Draft charter (v6)
Thread-index: Ac5oEUJh6X32UcmxT3KmocW8KKc14f//3/+AgAJobQCAA8z8gIAAGU6AgAAkjIA=
user-agent: Microsoft-MacOutlook/14.3.2.130206
X-AuditID: 0a5f4068-b7fe16d000000bfa-77-51bed32a670d
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJLMWRmVeSWpSXmKPExsXCFe/Apat1eV+gwcKFqha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxswPm1gKjq1krDjf1MfUwDhjKWMXIyeHhICJxOKJDVC2mMSF e+vZQGwhgY2MEj/vMXUxcgHZPxglHl/sZ4dIbGCU2N9bAmKzCKhKbLm5GSzOJqAlcfruKhYQ W1jAVeLDxx9ggzgFNCV2/Wxih1igIPHn3GOwGhGBXIlbp5vB4rwC3hLnd9xjBrGZBcwkHh0/ xAoRF5T4MfkeUD0HUFxdYsqUXIgScYnm1pssELaixLRFEPczCshKvJs/nxVivJvEpwlHoGw/ if2/HoHZogJ6EjfPtLBCnCMgsWTPeWYIW1Ti5eN/rBMYxWchuWIWkitmIVwxC8kVs5BcsYCR dRWjWHFSUWZ6RkluYmZOuoGhXkamXmZeaskmRkh0ZexgXL5T5RCjAAejEg/vhup9gUKsiWXF lbmHGCU4mJVEeGMnAoV4UxIrq1KL8uOLSnNSiw8xMnFwSjUwhtx4eFnimlfa7rtzrX6ZrQ6M evvsulXVjQBLuXPNIWbv6z6u/7qN49LpLrnrV7dNurTjImNsxOHg1/H7Hna+5klTPzNjX+zt iq2r05bpsbE9CP3y57VGw5RD+bEXLnkGfDi4J/fGzVlrGpdUf9ja/nZbmXil+GfN3251sZsf Jd8O3rGjrCvik7sSS3FGoqEWc1FxIgCzJUWFjAIAAA==
Subject: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2013 09:13:34 -0000

SGkgSm9zZSwgSnVsaWFuLA0KDQogICAgICAgIFllcywgIlRDTSBvcHRpbWl6ZXJzIiBhbmQgIlRD
TSBmbG93IiBhcmUgcGVyZmVjdCBmb3IgbWUgdG9vLg0KDQpCZXN0LA0KDQpGZXJuYW5kbyBQYXNj
dWFsIEJsYW5jbw0KVGVsZWbDs25pY2EgR2xvYmFsIFJlc291cmNlcw0KTmV0d29yayBBdXRvbWF0
aW9uIGFuZCBEeW5hbWl6YXRpb24NClRFQ0hOT0xPR1kgUEVPUExFIEdST1VQDQpGICszNDkxMzEy
ODc3OQ0KTSArMzQ2ODIwMDUxNjgNCmZwYkB0aWQuZXMNCg0KDQoNCg0KT24gMTcvMDYvMTMgMTE6
MDIsICJKdWxpw6FuIEZlcm7DoW5kZXotTmF2YWphcyIgPG5hdmFqYXNAdW5pemFyLmVzPiB3cm90
ZToNCg0KPkkgYWdyZWUgd2l0aCBGZXJuYW5kbyB0b28sIG5vIGludmVudCBuZXcgRW5nbGlzaCB2
ZXJiLg0KPkluIHJlbGF0aW9uIHdpdGggZHVwbGljYXRpbmcgZmxvdyB3b3JkLCBpIHRoaW5rIHRo
YXQgaXQgaXMgZmluZSB0byB1c2UNCj4iVENNIGZsb3ciIGluc3RlYWQgb2YgIlRDTVRGIGZsb3ci
Lg0KPkp1bGnDoW4NCj4NCj5FbCAxNy8wNi8yMDEzIDk6MzEsIEpvc2UgU2FsZGFuYSBlc2NyaWJp
w7M6DQo+PiBIaSwgRmVybmFuZG8uDQo+Pg0KPj4gSSBhZ3JlZSB3aXRoIHlvdS4gV2UgYXJlIHRh
bGtpbmcgYWJvdXQgc3RhbmRhcmRzIHNvIHByZWNpc2lvbiBpcw0KPj5pbXBvcnRhbnQuDQo+Pg0K
Pj4gSSBkb24ndCB0aGluayB3ZSBzaG91bGQgdXNlIHRoZSAidmVyYiIgInRvIFRDTVRGIiBub3Ig
IlRDTVRGaW5nIiBub3INCj4+ICJUQ01URmVkIi4gV2UgY2Fubm90IGludmVudCBuZXcgRW5nbGlz
aCB2ZXJicy4NCj4+DQo+PiBXaGF0IGFib3V0ICJvcHRpbWl6YXRpb24iPy4gVGhpcyBjb25jZXB0
IHN1bW1hcml6ZXMgdGhlIHRocmVlIGxheWVycy4NCj4+V2UgY2FuDQo+PiB1c2UgaXQgdGhpcyB3
YXk6DQo+Pg0KPj4gLSBBIFRDTVRGIG9wdGltaXplcg0KPj4NCj4+IC0gQSBwYWNrZXQgb3B0aW1p
emVkIGJ5IG1lYW5zIG9mIFRDTVRGDQo+PiAtIEEgZmxvdyBvcHRpbWl6ZWQgYnkgbWVhbnMgb2Yg
VENNVEYNCj4+IC0gQW4gb3B0aW1pemVkIHBhY2tldA0KPj4gLSBBbiBvcHRpbWl6ZWQgZmxvdw0K
Pj4gLSBBIFRDTVRGLW9wdGltaXplZCBwYWNrZXQNCj4+IC0gQSBUQ01URi1vcHRpbWl6ZWQgZmxv
dw0KPj4gLSBBIFRDTVRGIHBhY2tldA0KPj4gLSBBIFRDTVRGIGZsb3cNCj4+DQo+PiAtIHRoZSBU
Q01URiBvcHRpbWl6YXRpb24gY2FuIGJlIGFwcGxpZWQgdG8gdGhhdCBmbG93DQo+PiAtIHRoZSBp
bXBhY3Qgb2YgVENNVEYgb3B0aW1pemF0aW9uIG9uIHByb3RvY29sIGR5bmFtaWNzDQo+Pg0KPj4g
SSBoYXZlIGFub3RoZXIgcXVlc3Rpb24gaGVyZTogY291bGQgd2UgdXNlIG9ubHkgVENNIGluc3Rl
YWQgb2YgVENNVEY/DQo+PiBSZW1lbWJlciB0aGF0IFRGIG1lYW5zICJ0cmFmZmljIGZsb3dzIiwg
c28gYSBUQ01URiBmbG93IHdvdWxkIGJlIGENCj4+ICJ0dW5uZWxpbmcgY29tcHJlc3NlZCBtdWx0
aXBsZXhlZCB0cmFmZmljIGZsb3dzIGZsb3ciLiBQZXJoYXBzIGEgVENNDQo+PmZsb3cNCj4+IHdv
dWxkIGJlIGVub3VnaCBpbiB0aG9zZSBjYXNlcy4gVENNIGRvZXMgbm90IGhhdmUgYW5vdGhlciBy
ZWxhdGVkDQo+Pm1lYW5pbmcNCj4+IGFuZCBpdCBpcyBzaG9ydGVyIHRoYW4gVENNVEYgKGh0dHA6
Ly93d3cuYWNyb255bWZpbmRlci5jb20vVENNLmh0bWwpDQo+Pg0KPj4gLSBBIFRDTSBvcHRpbWl6
ZXINCj4+IC0gQSBUQ00tb3B0aW1pemVkIGZsb3cNCj4+IC0gQSBUQ00gZmxvdw0KPj4NCj4+IFdo
YXQgZG8geW91IHRoaW5rPw0KPj4NCj4+IEpvc2UNCj4+DQo+Pj4gLS0tLS1NZW5zYWplIG9yaWdp
bmFsLS0tLS0NCj4+PiBEZTogRkVSTkFORE8gUEFTQ1VBTCBCTEFOQ08gW21haWx0bzpmcGJAdGlk
LmVzXQ0KPj4+IEVudmlhZG8gZWw6IHZpZXJuZXMsIDE0IGRlIGp1bmlvIGRlIDIwMTMgMjE6MjkN
Cj4+PiBQYXJhOiBqc2FsZGFuYUB1bml6YXIuZXM7IHRjbXRmQGlldGYub3JnOyB0c3YtYXJlYUBp
ZXRmLm9yZw0KPj4+IEFzdW50bzogUmU6IFt0Y210Zl0gSW1wcm92ZWQgdmVyc2lvbiBvZiB0aGUg
dG1jdGYgRHJhZnQgY2hhcnRlciAodjYpDQo+Pj4NCj4+PiBIaSBKb3NlLA0KPj4+DQo+Pj4gICAg
ICAgICAgSSBsaWtlIGFsbCB5b3VyIGNoYW5nZXMsIHRoZXkgYWxsIGVucmljaCB0aGUgV0cgZGVz
Y3JpcHRpb24uDQo+Pj4NCj4+PiAgICAgICAgICBOZXZlcnRoZWxlc3MgSSB3YW50ZWQgdG8gbWVu
dGlvbiwgYWZ0ZXIgcmVhZCBjYXJlZnVsbHkgdGhlDQo+Pj50ZXh0LA0KPj4gdGhhdA0KPj4+IHdo
ZW4gd2UgdGFsayBhYm91dCBsYXllcnMsIHdlIGFsd2F5cyB1c2UgdGhlIHRocmVlIHRlcm1zICh0
dW5uZWxpbmcsDQo+Pj4gbXVsdGlwbGV4aW5nIGFuZCBjb21wcmVzc2lvbikgYW5kIEkgdGhpbmsg
aXQgaXMgb2suDQo+Pj4gICAgICAgICAgV2hlbiB3ZSB0YWxrIGFib3V0IHRoZSBlbGVtZW50cyBp
biBjaGFyZ2Ugb2YgYXBwbHkgdGhlIFRDTVRGDQo+PiBwcm90b2NvbA0KPj4+IHdlIGhhdmUgY2Fs
bCB0aGVtIG11bHRpcGxleGVycyBhbmQgZGVtdWx0aXBsZXhlcnMsIGFuZCB0aGF0IG1heSBiZSBh
DQo+PiBsaXR0bGUNCj4+PiBjb25mdXNpbmcsIGdpdmVuIHRoYXQgdGhleSB1c2UgdGhlIG5hbWUg
b2YgdGhlIG1pZGRsZSBwcm90b2NvbCBsYXllciwNCj4+PmJ1dA0KPj4gSQ0KPj4+IHVuZGVyc3Rh
bmQgdGhhdCB3ZSBoYXZlIG5vdCBmb3VuZCBhIGJldHRlciBuYW1lIChJIGluY2x1ZGUgbXlzZWxm
IGhlcmUpDQo+Pj4gYW5kIG1heWJlIG11bHRpcGxleGluZyBpcyB0aGUgbW9zdCByZXByZXNlbnRh
dGl2ZSBsYXllciwgc28gaXQgY291bGQgYmUNCj4+IG9rLg0KPj4+ICAgICAgICAgIEJ1dCBpbiBw
YXJhZ3JhcGggOCB3ZSB0YWxrIGFib3V0IG11bHRpcGxleGluZyBmbG93cyBhbmQgdGhlDQo+Pj5p
bXBhY3QNCj4+IG9mDQo+Pj4gbXVsdGlwbGV4aW5nIGluIHByb3RvY29sIGR5bmFtaWNzLCBhbmQg
SSB0aGluayB0aGF0IG1heSBiZSBjb25mdXNpbmcsDQo+PiBnaXZlbg0KPj4+IHRoYXQgdXNpbmcg
Im11bHRpcGxleGluZyIgd2UgYXJlIHJlZmVycmluZyB0byBhcHBseSB0aGUgd2hvbGUgVENNVEYN
Cj4+IHByb3RvY29sDQo+Pj4gb3Igbm90IGFuZCBub3Qgb25seSB0byBhcHBseSB0aGUgbXVsdGlw
bGV4aW5nIGxheWVyIG9yIG5vdC4gScK0bSBqdXN0DQo+PiBzYXlpbmcgdGhhdA0KPj4+IHRoaXMg
dGVybSBoZXJlIG1heSBiZSBjb25mdXNpbmcgYW5kIHNvbWVvbmUgY291bGQgZ2V0IGEgYmFkDQo+
Pj5pbnRlcnByZXRhdGlvbg0KPj4+IGZyb20gdGhlIHRleHQuIEkgc2VlIHRocmVlIG9wdGlvbjog
YSkgd2UgcHJlLWRlZmluZSB0aGUgdGVybQ0KPj4gIm11bHRpcGxleGluZyINCj4+PiBhcyB0aGUg
YXBwbGljYXRpb24gb2YgdGhlIFRDTVRGIHByb3RvY29sIGl0c2VsZiwgYikgd2UgaW52ZW50IHRo
ZSB2ZXJiDQo+Pj4idG8NCj4+PiBUQ01URiIgYW5kIHVzZSB0aGUgcGFydGljaXBsZSAiVENNVEZl
ZCIgd2hlbiBzb21ldGhpbmcgaXMgcGFzc2VkIHRyb3VnaA0KPj4+IG91ciBwcm90b2NvbCBzdGFj
ayBvciBjKSAoYW5kIG1heWJlIHRoZSBtb3N0IGNvbnZlbmllbnQgd2UgdXNlIHRoZSBsb25nDQo+
Pj4gZm9ybSAidGhlIFRDTVRGIHByb3RvY29sIGNhbiBiZSBhcHBsaWVkIHRvIHRoYXQgZmxvdyIg
b3IgInRoZSBpbXBhY3Qgb2YNCj4+PiBUQ01URiBwcm90b2NvbCBvbiBwcm90b2NvbCBkeW5hbWlj
cyIuIE15IHN1Z2dlc3Rpb24gaXMgdG8gdXNlIG9wdGlvbg0KPj4+YykuDQo+Pj4NCj4+PiAgICAg
ICAgICBXaGF0IGRvIHlvdSB0aGluaz8NCj4+Pg0KPj4+ICAgICAgICAgIFRoYW5rIHlvdSBmb3Ig
eW91ciBncmVhdCBlZmZvcnQhDQo+Pj4NCj4+PiBCZXN0LA0KPj4+DQo+Pj4gRmVybmFuZG8gUGFz
Y3VhbCBCbGFuY28NCj4+PiBUZWxlZsOzbmljYSBHbG9iYWwgUmVzb3VyY2VzDQo+Pj4gTmV0d29y
ayBBdXRvbWF0aW9uIGFuZCBEeW5hbWl6YXRpb24NCj4+PiBURUNITk9MT0dZIFBFT1BMRSBHUk9V
UA0KPj4+IEYgKzM0OTEzMTI4Nzc5DQo+Pj4gTSArMzQ2ODIwMDUxNjgNCj4+PiBmcGJAdGlkLmVz
DQo+Pj4NCj4+Pg0KPj4+DQo+Pj4NCj4+PiBPbiAxMy8wNi8xMyAxMDo0MywgIkpvc2UgU2FsZGFu
YSIgPGpzYWxkYW5hQHVuaXphci5lcz4gd3JvdGU6DQo+Pj4NCj4+Pj4gVGhlc2UgYXJlIHRoZSBt
YWluIGNoYW5nZXMgaW5jbHVkZWQgaW4gdGhlIGRyYWZ0IGNoYXJ0ZXIgdjYgKG9yZGVyZWQNCj4+
Pj5ieQ0KPj4+PiBwYXJhZ3JhcGhzKToNCj4+Pj4NCj4+Pj4gMS4gSSBoYXZlIG1vdmVkIHRoZSBz
ZW50ZW5jZSBhYm91dCB0aGUgb3ZlcmhlYWQgdG8gdGhlIGVuZCBvZiB0aGUNCj4+Pj4gcGFyYWdy
YXBoLCBpbiBvcmRlciB0byBzYXkgdGhhdCDCs0ZvciBib3RoIHRoZSBkZWxheS1zZW5zaXRpdmUg
YW5kDQo+Pj4+IGRlbGF5LWluc2Vuc2l0aXZlIGFwcGxpY2F0aW9ucywgdGhlaXIgc21hbGwgZGF0
YSBwYXlsb2FkcyBpbmN1cg0KPj4+PiBzaWduaWZpY2FudCBvdmVyaGVhZMKyDQo+Pj4+DQo+Pj4+
IDIuIEkgaGF2ZSBwdXQgdGhlIHNjZW5hcmlvcyBpbiBidWxsZXRzLCBhbmQgSSBoYXZlIGltcHJv
dmVkIHNvbWUgb2YNCj4+Pj50aGUNCj4+Pj4gZGVzY3JpcHRpb25zIGEgYml0Lg0KPj4+Pg0KPj4+
PiA2LiBJIGhhdmUgY2hhbmdlZCB0aGUgbmFtZSBvZiB0aGUgZG9jdW1lbnQ6IGluc3RlYWQgb2Yg
wrNkb2N1bWVudCBBwrIgaXQNCj4+Pj4gaXMgbm93IMKzVENNVEYgwq0gcmVmZXJlbmNlIG1vZGVs
wrIuDQo+Pj4+DQo+Pj4+IDcuIE5vdyB3ZSBhcmUgdGFsa2luZyBhYm91dCBhbm90aGVyIGRvY3Vt
ZW50IMKzVENNVEYgwq0gbmVnb3RpYXRpb24NCj4+Pj4gcHJvdG9jb2zCsi4NCj4+Pj4gSW4gYWRk
aXRpb24sIEkgaGF2ZSBwdXQgdGhlIHR3byBzaWduYWxpbmcgZnVuY3Rpb25hbGl0aWVzIGluIGJ1
bGxldHMuDQo+Pj4+DQo+Pj4+IDcuIEFzIGRpc2N1c3NlZCBpbiB0aGUgbGlzdCwgd2Ugd291bGQg
dGFsayBhYm91dCDCs3NldHVwL3JlbGVhc2UgYQ0KPj4+PlRDTVRGDQo+Pj4+IHNlc3Npb27Csi4N
Cj4+Pj4NCj4+Pj4gOC4gSSBoYXZlIGNoYW5nZWQgdGhlIG5hbWUgb2YgdGhlIGRvY3VtZW50LCBm
cm9tIMKzZG9jdW1lbnQgQsKyIHRvDQo+Pj4gwrNUQ01URg0KPj4+PiByZWNvbW1lbmRhdGlvbnPC
sg0KPj4+Pg0KPj4+PiA4LiBBY2NvcmRpbmcgdG8gR29ycnnCuXMgc3VnZ2VzdGlvbiwgSSBoYXZl
IGFkZGVkIHRoaXMgc2VudGVuY2U6IMKzVGhlDQo+Pj4+IGV2ZW50dWFsIGltcGFjdCBvZiBtdWx0
aXBsZXhpbmcgb24gcHJvdG9jb2wgZHluYW1pY3MgKGUuZy4gd2hlbg0KPj4+PiBtdWx0aXBsZXhp
bmcgVENQIGZsb3dzKSB3aWxsIGFsc28gaGF2ZSB0byBiZSBhZGRyZXNzZWQuwrINCj4+Pj4NCj4+
Pj4gSm9zZQ0KPj4+Pg0KPj4+Pg0KPj4+Pj4gLS0tLS1NZW5zYWplIG9yaWdpbmFsLS0tLS0NCj4+
Pj4+IERlOiB0Y210Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86dGNtdGYtYm91bmNlc0BpZXRm
Lm9yZ10gRW4gbm9tYnJlDQo+Pj4+PiBkZSBKb3NlIFNhbGRhbmEgRW52aWFkbyBlbDoganVldmVz
LCAxMyBkZSBqdW5pbyBkZSAyMDEzIDEwOjM4DQo+Pj4+PiBQYXJhOiB0Y210ZkBpZXRmLm9yZzsg
dHN2LWFyZWFAaWV0Zi5vcmcNCj4+Pj4+IEFzdW50bzogW3RjbXRmXSBJbXByb3ZlZCB2ZXJzaW9u
IG9mIHRoZSB0bWN0ZiBEcmFmdCBjaGFydGVyICh2NikNCj4+Pj4+DQo+Pj4+PiBUaGlzIGlzIHRo
ZSBuZXcgcHJvcG9zYWwsIGFkYXB0ZWQgdG8gdGhlIG5ldyBkaXN0cmlidXRpb24gb2YgdGhlDQo+
Pj4+IGRvY3VtZW50cy4NCj4+Pj4+IEkgZXhwbGFpbiB0aGUgY2hhbmdlcyBpbiBhbm90aGVyIGUt
bWFpbC4NCj4+Pj4+IEl0IGlzIGFsc28gaGVyZSwgaW4gYSBmb3JtYXR0ZWQgdmVyc2lvbjoNCj4+
Pj4+IGh0dHA6Ly9kaWVjLnVuaXphci5lcy9+anNhbGRhbmEvcGVyc29uYWwvaWV0Zi90Y210Zl9j
aGFydGVyX2RyYWZ0LnBkZg0KPj4+Pj4NCj4+Pj4+DQo+Pj4+PiBUQ01URiBjaGFydGVyIGRyYWZ0
IHY2DQo+Pj4+Pg0KPj4+Pj4gRGVzY3JpcHRpb24gb2YgV29ya2luZyBHcm91cA0KPj4+Pj4NCj4+
Pj4+IDEuIEluIHRoZSBsYXN0IHllYXJzIHdlIGFyZSB3aXRuZXNzaW5nIHRoZSByYWlzZSBvZiBu
ZXcgcmVhbC10aW1lDQo+Pj4+PiBzZXJ2aWNlcw0KPj4+PiB0aGF0DQo+Pj4+PiB1c2UgdGhlIElu
dGVybmV0IGZvciB0aGUgZGVsaXZlcnkgb2YgaW50ZXJhY3RpdmUgbXVsdGltZWRpYQ0KPj4+Pj4g
YXBwbGljYXRpb25zOiBWb0lQLCB2aWRlb2NvbmZlcmVuY2luZywgdGVsZW1lZGljaW5lLCB2aWRl
byB2aWdpbGFuY2UsDQo+Pj4+IG9ubGluZQ0KPj4+Pj4gZ2FtaW5nLCBldGMuIER1ZSB0byB0aGUg
bmVlZCBvZiBpbnRlcmFjdGl2aXR5LCBtYW55IG9mIHRoZXNlIHNlcnZpY2VzDQo+Pj4+PiB1c2Ug
IHNtYWxsIHBhY2tldHMgKHNvbWUgdGVucyBvZiBieXRlcyksIHNpbmNlIHRoZXkgaGF2ZSB0byBz
ZW5kDQo+Pj4+PiBmcmVxdWVudCAgdXBkYXRlcyBiZXR3ZWVuIHRoZSBleHRyZW1lcyBvZiB0aGUg
Y29tbXVuaWNhdGlvbi4gSW4NCj4+Pj4+IGFkZGl0aW9uLCBzb21lICBvdGhlciBzZXJ2aWNlcyBh
bHNvIHNlbmQgc21hbGwgcGFja2V0cywgYnV0IHRoZXkgYXJlDQo+Pj4+PiBub3QgZGVsYXktc2Vu
c2l0aXZlDQo+Pj4+IChlLmcuLA0KPj4+Pj4gaW5zdGFudCBtZXNzYWdpbmcsIG0ybSBwYWNrZXRz
IHNlbmRpbmcgY29sbGVjdGVkIGRhdGEgaW4gc2Vuc29yDQo+Pj4+PiBuZXR3b3JrcyB1c2luZyB3
aXJlbGVzcyBvciBzYXRlbGxpdGUgc2NlbmFyaW9zKS4gRm9yIGJvdGggdGhlDQo+Pj4+PiBkZWxh
eS1zZW5zaXRpdmUgYW5kDQo+Pj4+IGRlbGF5LQ0KPj4+Pj4gaW5zZW5zaXRpdmUgYXBwbGljYXRp
b25zLCB0aGVpciBzbWFsbCBkYXRhIHBheWxvYWRzIGluY3VyIHNpZ25pZmljYW50DQo+Pj4+IG92
ZXJoZWFkLA0KPj4+Pj4gYW5kIGl0IGJlY29tZXMgZXZlbiBoaWdoZXIgd2hlbiBJUHY2IGlzIHVz
ZWQsIHNpbmNlIHRoZSBiYXNpYyBJUHY2DQo+Pj4+PiBoZWFkZXINCj4+Pj4gaXMNCj4+Pj4+IHR3
aWNlIHRoZSBzaXplIG9mIHRoZSBJUHY0IG9uZS4NCj4+Pj4+DQo+Pj4+PiAyLiBUaGUgZWZmaWNp
ZW5jeSBjYW5ub3QgYmUgaW5jcmVhc2VkIGJ5IHRoZSBpbmNsdXNpb24gb2YgYSBoaWdoZXINCj4+
Pj4+IG51bWJlcg0KPj4+PiBvZg0KPj4+Pj4gc2FtcGxlcyBpbiBhIHNpbmdsZSBwYWNrZXQsIHNp
bmNlIHRoaXMgd291bGQgaGFybSB0aGUgZGVsYXkNCj4+Pj4+IHJlcXVpcmVtZW50cw0KPj4+PiBv
Zg0KPj4+Pj4gdGhlIHNlcnZpY2UuIEJ1dCB0aGVyZSBleGlzdCBzb21lIHNjZW5hcmlvcyBpbiB3
aGljaCBhIG51bWJlciBvZg0KPj4+Pj4gZmxvd3MNCj4+Pj4gc2hhcmUNCj4+Pj4+IHRoZSBzYW1l
IHBhdGguIEluIHRoaXMgY2FzZSwgcGFja2V0cyBiZWxvbmdpbmcgdG8gZGlmZmVyZW50IGZsb3dz
IGNhbg0KPj4+Pj4gYmUgZ3JvdXBlZCB0b2dldGhlciwgYWRkaW5nIGEgc21hbGwgbXVsdGlwbGV4
aW5nIGRlbGF5IGFzIGENCj4+Pj4+IGNvdW50ZXJwYXJ0IG9mIGJhbmR3aWR0aCBzYXZpbmcuIFRo
aXMgZGVsYXkgd2lsbCBoYXZlIHRvIGJlDQo+Pj4+PiBtYWludGFpbmVkIHVuZGVyIHNvbWUgdGhy
ZXNob2xkIGluIG9yZGVyIHRvIGdyYW50IHRoZSBkZWxheQ0KPj4+Pj4gcmVxdWlyZW1lbnRzLiBT
b21lIGV4YW1wbGVzIG9mIHRoZSBzY2VuYXJpb3Mgd2hlcmUgZ3JvdXBpbmcgcGFja2V0cw0KPj4+
Pj5pcw0KPj4+IHBvc3NpYmxlIGFyZToNCj4+Pj4+IC0gYWdncmVnYXRpb24gbmV0d29ya3Mgb2Yg
YSBuZXR3b3JrIG9wZXJhdG9yOw0KPj4+Pj4gLSBhbiBlbmQtdG8tZW5kIHR1bm5lbCBiZXR3ZWVu
IGFwcGxpYW5jZXMgbG9jYXRlZCBpbiB0d28gZGlmZmVyZW50DQo+Pj4+PiBvZmZpY2VzICBvZiB0
aGUgc2FtZSBjb21wYW55Ow0KPj4+Pj4gLSB0aGUgYWNjZXNzIGNvbm5lY3Rpb24gb2YgYW4gSW50
ZXJuZXQgQ2Fmw6kgaW5jbHVkaW5nIGEgaGlnaCBudW1iZXINCj4+Pj4+IG9mICBWb0lQL2dhbWlu
ZyBmbG93czsNCj4+Pj4+IC0gYW4gYWdyZWVtZW50IGJldHdlZW4gdHdvIG5ldHdvcmsgb3BlcmF0
b3JzIGNvdWxkIGFsbG93IHRoZW0gdG8NCj4+Pj4+IGNvbXByZXNzIGEgbnVtYmVyIG9mIGZsb3dz
IHRoZXkgYXJlIGV4Y2hhbmdpbmcgYmV0d2VlbiBhIHBhaXIgb2YNCj4+Pj4+IEludGVybmV0ICBS
b3V0ZXJzOw0KPj4+Pj4gLSBhIHNhdGVsbGl0ZSBjb25uZWN0aW9uIHVzZWQgZm9yIGNvbGxlY3Rp
bmcgdGhlIGRhdGEgb2YgYSBoaWdoDQo+Pj4+PiBudW1iZXIgb2YgIHNlbnNvcnMuDQo+Pj4+Pg0K
Pj4+Pj4gMy4gVm9JUCB1c2luZyBSVFAgaXMgYSBjbGVhciBleGFtcGxlIG9mIGEgcmVhbC10aW1l
IHNlcnZpY2UgdXNpbmcNCj4+Pj4+IHNtYWxsDQo+Pj4+IHBhY2tldHMNCj4+Pj4+IHdpdGggaGln
aCBvdmVyaGVhZC4gSW4gb3JkZXIgdG8gaW1wcm92ZSBlZmZpY2llbmN5LCBSRkM0MTcwIChUQ1JU
UCkNCj4+Pj4gZGVmaW5lZA0KPj4+Pj4gYSBtZXRob2QgZm9yIGdyb3VwaW5nIHBhY2tldHMgd2hl
biBhIG51bWJlciBvZiBmbG93cyBzaGFyZSBhIHBhdGgsDQo+Pj4+PiBjb25zaWRlcmluZyB0aHJl
ZSBkaWZmZXJlbnQgbGF5ZXJzOiBoZWFkZXIgY29tcHJlc3Npb24gYnkgbWVhbnMgb2YNCj4+Pj4+
IEVDUlRQOyAgbXVsdGlwbGV4aW5nIGJ5IG1lYW5zIG9mIFBQUE11eDsgdHVubmVsaW5nIGJ5IG1l
YW5zIG9mDQo+Pj4+PkwyVFB2My4NCj4+Pj4+DQo+Pj4+PiA0LiBIb3dldmVyLCBpbiB0aGUgbGFz
dCB5ZWFycywgZW1lcmdpbmcgcmVhbC10aW1lIHNlcnZpY2VzIHdoaWNoIGRvDQo+Pj4+PiBub3QN
Cj4+Pj4gdXNlDQo+Pj4+PiBVRFAvUlRQIGhhdmUgYmVjb21lIHBvcHVsYXI6IHNvbWUgb2YgdGhl
bSB1c2UgVURQIG9yIGV2ZW4gVENQLiBJbg0KPj4+Pj4gYWRkaXRpb24sIG5ldyBoZWFkZXIgY29t
cHJlc3Npb24gbWV0aG9kcyBoYXZlIGJlZW4gZGVmaW5lZCAoUk9IQykuDQo+Pj4gU28NCj4+Pj4+
IHRoZXJlIGlzIGEgbmVlZCBvZiB3aWRlbmluZyB0aGUgc2NvcGUgb2YgUkZDNDE3MCBpbiBvcmRl
ciB0byBjb25zaWRlcg0KPj4+Pj4gbm90ICBvbmx5IFVEUC9SVFAgYnV0IGFsc28gb3RoZXIgcHJv
dG9jb2xzLiBUaGUgc2FtZSBzdHJ1Y3R1cmUgb2YNCj4+Pj4+IHRocmVlIGxheWVycyAgd2lsbCBi
ZSBjb25zaWRlcmVkOg0KPj4+Pj4NCj4+Pj4+IC0gSGVhZGVyIGNvbXByZXNzaW9uOiBUYWtpbmcg
aW50byBhY2NvdW50IHRoYXQgcmVhbC10aW1lIGFwcGxpY2F0aW9ucw0KPj4+Pj4gdXNlICBkaWZm
ZXJlbnQgaGVhZGVycyAoUlRQL1VEUCwgVURQIG9yIGV2ZW4gVENQKSwgZGlmZmVyZW50DQo+Pj4+
PnByb3RvY29scw0KPj4+Pj4gY2FuIGJlDQo+Pj4+PiB1c2VkOiBubyBjb21wcmVzc2lvbiwgRUNS
VFAsIElQSEMgYW5kIFJPSEMuDQo+Pj4+PiAtIE11bHRpcGxleGluZzogSWYgYSBudW1iZXIgb2Yg
Zmxvd3Mgc2hhcmUgYSBwYXRoIGJldHdlZW4gYW4gb3JpZ2luDQo+Pj4+PiBhbmQgYSAgZGVzdGlu
YXRpb24sIGEgbXVsdGlwbGV4ZXIgY2FuIGJ1aWxkIGEgYmlnZ2VyIHBhY2tldCBpbiB3aGljaA0K
Pj4+Pj5hDQo+Pj4+PiBudW1iZXIgb2YgIHBheWxvYWRzIHNoYXJlIGEgY29tbW9uIGhlYWRlci4g
QSBkZW11bHRpcGxleGVyIGlzIHRoZW4NCj4+Pj4+IG5lY2Vzc2FyeSBhdCB0aGUgIGVuZCBvZiB0
aGUgY29tbW9uIHBhdGgsIHNvIGFzIHRvIHJlYnVpbGQgdGhlDQo+Pj4+PnBhY2tldHMNCj4+Pj4+
IGFzIHRoZXkgd2VyZQ0KPj4+PiBvcmlnaW5hbGx5DQo+Pj4+PiBzZW50LiBQUFBNdXggd2lsbCBi
ZSB0aGUgbWFpbiBvcHRpb24uIE90aGVyIG9uZXMgYXJlIG5vdCBkaXNjYXJkZWQuDQo+Pj4+PiAt
IFR1bm5lbGluZyB3aWxsIGJlIHVzZWQgdG8gc2VuZCB0aGUgbXVsdGlwbGV4ZWQgcGFja2V0cyBl
bmQtdG8tZW5kLg0KPj4+Pj4gVGhlIG9wdGlvbnMgaW4gdGhpcyBsYXllciBhcmUgTDJUUCwgR1JF
IGFuZCBNUExTLg0KPj4+Pj4NCj4+Pj4+IDUuIFNvIHRoZSBmaXJzdCBvYmplY3RpdmUgb2YgdGhp
cyBncm91cCBpcyB0byBzcGVjaWZ5IHRoZSBwcm90b2NvbA0KPj4+Pj4gc3RhY2sNCj4+Pj4gZm9y
DQo+Pj4+PiB0dW5uZWxpbmcsIGNvbXByZXNzaW5nIGFuZCBtdWx0aXBsZXhpbmcgdHJhZmZpYyBm
bG93cyAoVENNVEYpLiBTaW5jZQ0KPj4+Pj4gc3RhbmRhcmQgcHJvdG9jb2xzIGFyZSBiZWluZyB1
c2VkIGF0IGVhY2ggbGF5ZXIsIHRoZSBzaWduYWxpbmcNCj4+Pj4+bWV0aG9kcw0KPj4+Pj4gb2Yg
IHRob3NlIHByb3RvY29scyB3aWxsIGJlIHVzZWQuIEludGVyYWN0aW9ucyB3aXRoIHRoZSBXb3Jr
aW5nDQo+Pj4+Pkdyb3Vwcw0KPj4+Pj4gYW5kDQo+Pj4+IEFyZWFzDQo+Pj4+PiBpbiB3aGljaCB0
aGVzZSBwcm90b2NvbHMgYXJlIGRldmVsb3BlZCBjYW4gYmUgZXhwZWN0ZWQuIEhvd2V2ZXIsIHRo
ZQ0KPj4+Pj4gZGV2ZWxvcG1lbnQgb2YgbmV3IGNvbXByZXNzaW5nLCBtdWx0aXBsZXhpbmcgb3Ig
dHVubmVsaW5nIHByb3RvY29scw0KPj4+Pj5pcw0KPj4+Pj4gbm90ICBhbiBvYmplY3RpdmUgb2Yg
dGhpcyBXb3JraW5nIEdyb3VwLiBJbiBhZGRpdGlvbiwgc2luY2UgdGhlDQo+Pj4+PiBjdXJyZW50
IFJGQw0KPj4+PiA0MTcwDQo+Pj4+PiB3b3VsZCBiZSBjb25zaWRlcmVkIGFzIG9uZSBvZiB0aGUg
b3B0aW9ucywgdGhpcyBSRkMgY291bGQgYmUNCj4+Pj4+b2Jzb2xldGVkLg0KPj4+Pj4NCj4+Pj4+
IDYuIEFzIGEgZmlyc3Qgb2JqZWN0aXZlLCBhIGRvY3VtZW50IChUQ01URiAtIHJlZmVyZW5jZSBt
b2RlbCkgd2lsbA0KPj4+Pj4gZGVmaW5lDQo+Pj4+IHRoZQ0KPj4+Pj4gZGlmZmVyZW50IG9wdGlv
bnMgd2hpY2ggY2FuIGJlIHVzZWQgYXQgZWFjaCBsYXllci4gU3BlY2lmaWMgcHJvYmxlbXMNCj4+
Pj4gY2F1c2VkDQo+Pj4+PiBieSB0aGUgaW50ZXJhY3Rpb24gYmV0d2VlbiBsYXllcnMgd2lsbCBo
YXZlIHRvIGJlIGlzc3VlZCwgYW5kDQo+Pj4+PiBzdWl0YWJsZSBleHRlbnNpb25zIG1heSBoYXZl
IHRvIGJlIGFkZGVkIHRvIHRoZSBpbnZvbHZlZCBwcm90b2NvbHMuDQo+Pj4+Pg0KPj4+Pj4gNy4g
SWYgYSBwYWlyIG11bHRpcGxleGVyL2RlLW11bHRpcGxleGVyIHdhbnQgdG8gZXN0YWJsaXNoIGEg
VENNVEYNCj4+Pj4+IHNlc3Npb24sICB0aGV5IGhhdmUgZmlyc3QgdG8gdXNlIGEgbWVjaGFuaXNt
IHRvIG5lZ290aWF0ZSB3aGljaA0KPj4+Pj4gY29uY3JldGUgb3B0aW9uDQo+Pj4+IHdvdWxkDQo+
Pj4+PiB0aGV5IHVzZSBpbiBlYWNoIGxheWVyOiBoZWFkZXIgY29tcHJlc3Npb24sIG11bHRpcGxl
eGluZyBhbmQNCj4+Pj4+dHVubmVsaW5nLg0KPj4+PiBUaGlzDQo+Pj4+PiB3aWxsIGRlcGVuZCBv
biB0aGUgcHJvdG9jb2xzIHRoYXQgZWFjaCBleHRyZW1lIGltcGxlbWVudHMgYXQgZWFjaA0KPj4+
Pj4gbGV2ZWwsIGFuZCBpbiB0aGUgc2NlbmFyaW8uIFNvIGFub3RoZXIgZG9jdW1lbnQgKFRDTVRG
IC0gbmVnb3RpYXRpb24NCj4+Pj4+IHByb3RvY29sKQ0KPj4+PiB3aWxsDQo+Pj4+PiBpbmNsdWRl
Og0KPj4+Pj4NCj4+Pj4+IC0gYSBtZWNoYW5pc20gdG8gc2V0dXAvcmVsZWFzZSBhIFRDTVRGIHNl
c3Npb24gYmV0d2VlbiBhIG11bHRpcGxleGVyDQo+Pj4+PiBhbmQgYSBkZS1tdWx0aXBsZXhlciwg
YWxzbyBpbmNsdWRpbmc6DQo+Pj4+PiAtIGEgbmVnb3RpYXRpb24gbWVjaGFuaXNtIHRvIGRlY2lk
ZSB0aGUgb3B0aW9ucyB0byB1c2UgYXQgZWFjaCBsYXllcg0KPj4+PiAoaGVhZGVyDQo+Pj4+PiBj
b21wcmVzc2lvbiwgbXVsdGlwbGV4aW5nIGFuZCB0dW5uZWxpbmcpIGJldHdlZW4gbXVsdGlwbGV4
ZXIgYW5kIGRlLQ0KPj4+Pj4gbXVsdGlwbGV4ZXIsDQo+Pj4+Pg0KPj4+Pj4gOC4gQXMgYSBjb3Vu
dGVycGFydCBvZiB0aGUgYmFuZHdpZHRoIHNhdmluZywgVENNVEYgbWF5IGFkZCBzb21lIGRlbGF5
DQo+Pj4+PiBhbmQgIGppdHRlci4gVGhpcyBpcyBub3QgYSBwcm9ibGVtIGZvciB0aGUgc2Vydmlj
ZXMgd2hpY2ggYXJlIG5vdA0KPj4+Pj4gc2Vuc2l0aXZlIHRvDQo+Pj4+IGRlbGF5Lg0KPj4+Pj4g
SG93ZXZlciwgcmVnYXJkaW5nIGRlbGF5LXNlbnNpdGl2ZSBzZXJ2aWNlcywgdGhlIFdvcmtpbmcg
R3JvdXAgd2lsbA0KPj4+Pj4gYWxzbyAgZGV2ZWxvcCBhIGRvY3VtZW50IChUQ01URiAtIHJlY29t
bWVuZGF0aW9ucykgd2l0aCB1c2VmdWwNCj4+Pj4+IHJlY29tbWVuZGF0aW9ucyBpbiBvcmRlciB0
byBkZWNpZGUgd2hpY2ggcGFja2V0IGZsb3dzIGNhbiBvciBjYW4gbm90DQo+Pj4+PiBiZSAgbXVs
dGlwbGV4ZWQgYW5kIGhvdy4gVGhlIGRvY3VtZW50IHdpbGwgcHJlc2VudCBhIGxpc3Qgb2YNCj4+
Pj4+YXZhaWxhYmxlDQo+Pj4+PiB0cmFmZmljICBjbGFzc2lmaWNhdGlvbiBtZXRob2RzIHdoaWNo
IGNhbiBiZSB1c2VkIGZvciBpZGVudGlmaWNhdGlvbg0KPj4+Pj4gb2YgdGhlIHNlcnZpY2UNCj4+
Pj4gb3INCj4+Pj4+IGFwcGxpY2F0aW9uIHRvIHdoaWNoIGEgcGFydGljdWxhciBmbG93IGJlbG9u
Z3MsIGFzIHdlbGwgYXMNCj4+Pj4+IHJlY29tbWVuZGF0aW9ucw0KPj4+PiBvZg0KPj4+Pj4gdGhl
IG1heGltdW0gZGVsYXkgYW5kIGppdHRlciB0byBiZSBhZGRlZCBkZXBlbmRpbmcgb2YgdGhlIGlk
ZW50aWZpZWQNCj4+Pj4+IHNlcnZpY2Ugb3IgYXBwbGljYXRpb24uIFRoZSBldmVudHVhbCBpbXBh
Y3Qgb2YgbXVsdGlwbGV4aW5nIG9uDQo+Pj4+PiBwcm90b2NvbCBkeW5hbWljcyAoZS5nLiwgd2hl
biBtdWx0aXBsZXhpbmcgVENQIGZsb3dzKSB3aWxsIGFsc28gaGF2ZQ0KPj4+Pj4gdG8gYmUNCj4+
Pj4gYWRkcmVzc2VkLg0KPj4+Pj4gOS4gSWYgb3RoZXIgaW50ZXJlc3RpbmcgZmVhdHVyZXMgYXJl
IGlkZW50aWZpZWQsIHRoZSBncm91cCB3b3VsZA0KPj4+PiByZS1jaGFydGVyIGFuZA0KPj4+Pj4g
aW5jbHVkZSB0aGVtLCBlLmcuLCBhIG1lY2hhbmlzbSBmb3IgYSBtdWx0aXBsZXhlciB0byBkaXNj
b3ZlciBhIGRlLQ0KPj4+Pj4gbXVsdGlwbGV4ZXIsIGFuZCB2aWNlIHZlcnNhOyBhIG1lY2hhbmlz
bSB0byBzZWxlY3QgYW4gb3B0aW1hbA0KPj4+Pj4gbXVsdGlwbGV4ZXIgIGFuZCBhIGRlLW11bHRp
cGxleGVyIHdoZW4gdGhlcmUgYXJlIG1vcmUgdGhhbiBvbmUNCj4+Pj4+IG11eGVyL2RlLW11eGVy
IGZvciBhICBmbG93OyBkeW5hbWljYWxseSBhcHBseWluZyBUQ01URjogYSBoaWdoZXINCj4+Pj4+
IGVudGl0eSBpbiBjaGFyZ2Ugb2YgZGVjaWRpbmcNCj4+Pj4gd2hlbg0KPj4+Pj4gYW5kIHdoZXJl
LCBhcHBseWluZyBvciBub3QgVENNVEYsIGFuZCB3aGF0IGtpbmQgb2YgVENNVEYsIGFuZCB3aGF0
DQo+Pj4+PiBtdWx0aXBsZXhpbmcgcGVyaW9kLiBBZGRpdGlvbmFsIG1ldGhvZHMgZm9yIGVzdGlt
YXRpbmcgZGVsYXkgd291bGQNCj4+Pj4+IGFsc28gYmUgIHJlcXVpcmVkLg0KPj4+Pj4NCj4+Pj4+
IDEwLiBJbiBhZGRpdGlvbiwgc3BlY2lmaWMgdXNlcyBvZiBUQ01URiwgc3VjaCBhcyBpbiB3aXJl
bGVzcyBhbmQNCj4+Pj4+IHNhdGVsbGl0ZSAgc2NlbmFyaW9zLCBjb3VsZCBiZSBjb25zaWRlcmVk
LCBhbmQgaXQgd2lsbCBiZSBzdHVkaWVkDQo+Pj4+PiB3aGV0aGVyDQo+Pj4+IG1vZGlmaWNhdGlv
bnMNCj4+Pj4+IG9yIGV4dGVuc2lvbnMgYXJlIHJlcXVpcmVkIG9uIHRoZSBwcm90b2NvbC4NCj4+
Pj4+DQo+Pj4+PiAxMS4gSW50ZXJhY3Rpb25zIHdpdGggb3RoZXIgV29ya2luZyBHcm91cHMgY2Fu
IGJlIGV4cGVjdGVkLCBzaW5jZQ0KPj4+Pj4gVENNVEYgIHVzZXMgYWxyZWFkeSBkZWZpbmVkIHBy
b3RvY29scyBmb3IgY29tcHJlc3Npb24sIG11bHRpcGxleGluZw0KPj4+Pj4gYW5kIHR1bm5lbGlu
ZyAgKFJPSEMsIFBQUE11eCwgTVBMUywgR1JFLCBMMlRQKS4NCj4+Pj4+DQo+Pj4+PiBHb2FscyBh
bmQgTWlsZXN0b25lcw0KPj4+Pj4NCj4+Pj4+IFNwZWNpZmljYXRpb24gb2YgVENNVEYgIHJlZmVy
ZW5jZSBtb2RlbC4NCj4+Pj4+DQo+Pj4+PiBTcGVjaWZpY2F0aW9uIG9mIFRDTVRGIG5lZ290aWF0
aW9uIHByb3RvY29sLg0KPj4+Pj4NCj4+Pj4+IFNwZWNpZmljYXRpb24gb2YgVENNVEYgcmVjb21t
ZW5kYXRpb25zIG9mIHVzaW5nIGV4aXN0aW5nIHRyYWZmaWMNCj4+Pj4+IGNsYXNzaWZpY2F0aW9u
IG1ldGhvZHMsIG1heGltdW0gZGVsYXkgYW5kIGppdHRlciB0byBhZGQsIGRlcGVuZGluZyBvbg0K
Pj4+Pj4gdGhlICBzZXJ2aWNlLg0KPj4+Pj4NCj4+Pj4+DQo+Pj4+PiBDdXJyZW50IHZlcnNpb24g
b2YgRG9jdW1lbnQgKFRDTVRGIC0gcmVmZXJlbmNlIG1vZGVsKToNCj4+Pj4+IGh0dHBzOi8vZGF0
YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXNhbGRhbmEtdHN2d2ctdGNtdGYvDQo+Pj4+Pg0K
Pj4+Pj4gQ3VycmVudCB2ZXJzaW9uIG9mIERvY3VtZW50IChUQ01URiAtIHJlY29tbWVuZGF0aW9u
cyk6DQo+Pj4+PiBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXN1em5qZXZp
Yy10c3Z3Zy1tdGQtdGNtdGYvDQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+IEJlc3QgcmVnYXJkcywNCj4+
Pj4+DQo+Pj4+PiBKb3NlDQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4+PiB0Y210ZiBtYWlsaW5nIGxpc3QNCj4+
Pj4+IHRjbXRmQGlldGYub3JnDQo+Pj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3RjbXRmDQo+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+Pj4+IHRjbXRmIG1haWxpbmcgbGlzdA0KPj4+PiB0Y210ZkBpZXRmLm9yZw0K
Pj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQo+Pj4NCj4+
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+DQo+Pj4gRXN0ZSBtZW5zYWpl
IHNlIGRpcmlnZSBleGNsdXNpdmFtZW50ZSBhIHN1IGRlc3RpbmF0YXJpby4gUHVlZGUNCj4+PmNv
bnN1bHRhcg0KPj4+IG51ZXN0cmEgcG9sw610aWNhIGRlIGVudsOtbyB5IHJlY2VwY2nDs24gZGUg
Y29ycmVvIGVsZWN0csOzbmljbyBlbiBlbA0KPj4+ZW5sYWNlDQo+Pj4gc2l0dWFkbyBtw6FzIGFi
YWpvLg0KPj4+IFRoaXMgbWVzc2FnZSBpcyBpbnRlbmRlZCBleGNsdXNpdmVseSBmb3IgaXRzIGFk
ZHJlc3NlZS4gV2Ugb25seSBzZW5kDQo+Pj5hbmQNCj4+PiByZWNlaXZlIGVtYWlsIG9uIHRoZSBi
YXNpcyBvZiB0aGUgdGVybXMgc2V0IG91dCBhdDoNCj4+PiBodHRwOi8vd3d3LnRpZC5lcy9FUy9Q
QUdJTkFTL2Rpc2NsYWltZXIuYXNweA0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4+IHRjbXRmIG1haWxpbmcgbGlzdA0KPj4gdGNtdGZAaWV0Zi5v
cmcNCj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCj4+DQo+
Pg0KPg0KPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
dGNtdGYgbWFpbGluZyBsaXN0DQo+dGNtdGZAaWV0Zi5vcmcNCj5odHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3RjbXRmDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCg0KRXN0ZSBtZW5zYWplIHNlIGRpcmlnZSBleGNsdXNpdmFtZW50ZSBhIHN1IGRlc3Rp
bmF0YXJpby4gUHVlZGUgY29uc3VsdGFyIG51ZXN0cmEgcG9sw610aWNhIGRlIGVudsOtbyB5IHJl
Y2VwY2nDs24gZGUgY29ycmVvIGVsZWN0csOzbmljbyBlbiBlbCBlbmxhY2Ugc2l0dWFkbyBtw6Fz
IGFiYWpvLg0KVGhpcyBtZXNzYWdlIGlzIGludGVuZGVkIGV4Y2x1c2l2ZWx5IGZvciBpdHMgYWRk
cmVzc2VlLiBXZSBvbmx5IHNlbmQgYW5kIHJlY2VpdmUgZW1haWwgb24gdGhlIGJhc2lzIG9mIHRo
ZSB0ZXJtcyBzZXQgb3V0IGF0Og0KaHR0cDovL3d3dy50aWQuZXMvRVMvUEFHSU5BUy9kaXNjbGFp
bWVyLmFzcHgNCg==

From navajas@unizar.es  Mon Jun 17 03:14:17 2013
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4162621F935A for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 03:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rvgpdxMAbM5Y for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 03:14:09 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 011B021F9B89 for <tcmtf@ietf.org>; Mon, 17 Jun 2013 03:12:11 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5HABCWY017580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Mon, 17 Jun 2013 12:11:27 +0200
Message-ID: <51BEE0C0.5070808@unizar.es>
Date: Mon, 17 Jun 2013 12:11:12 +0200
From: =?ISO-8859-15?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <E004A7C54DE04F4BB87DB9F32308DA5C0C0E13@MAIL4.fer.hr>
In-Reply-To: <E004A7C54DE04F4BB87DB9F32308DA5C0C0E13@MAIL4.fer.hr>
Content-Type: multipart/alternative; boundary="------------060604080701080901080104"
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] New version of draft-suznjevic-tsvwg-mtd-tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2013 10:14:19 -0000

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

Hi all,
I think the specific list for tcmtf is the ideal place to discuss this 
draft.
Thanks Mirko for the work in this draft.
Julián

El 14/06/2013 13:54, Mirko Su¸njevic' escribió:
>
> Hello,
>
> We have just submitted the new version of draft 
>  draft-suznjevic-tsvwg-mtd-tcmtf-01 renamed Delay Limits and 
> Multiplexing Policies to be employed with Tunneling Compressed 
> Multiplexed Traffic Flows 
> http://tools.ietf.org/html/draft-suznjevic-tsvwg-mtd-tcmtf-01.
>
> It is an extension of tcmtf 
> http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/ 
> <http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/>. Since a 
> specific list for tcmtf exists (tcmtf@ietf.org 
> <mailto:tcmtf@ietf.org>), the idea is to discuss it there.
>
> The draft contains recommendations for TCMTF multiplexing period for 
> different network services as well as description of several policies 
> required in the process of packet multiplexing.
>
> We are discussing to revise the draft once more before the IETF 
> meeting in Berlin so your feedback will be very welcome. Thank you.
>
> Sincerely,
>
> Mirko Suznjevic
>
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-15"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi all,<br>
      I think the specific list for tcmtf is the ideal place to discuss
      this draft.<br>
      Thanks Mirko for the work in this draft.<br>
      Julián<br>
      <br>
      El 14/06/2013 13:54, Mirko Su¸njevi&#263; escribió:<br>
    </div>
    <blockquote
      cite="mid:E004A7C54DE04F4BB87DB9F32308DA5C0C0E13@MAIL4.fer.hr"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-15">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span lang="EN-US">Hello,<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">We have just submitted
            the new version of draft  draft-suznjevic-tsvwg-mtd-tcmtf-01
            renamed Delay Limits and Multiplexing Policies to be
            employed with Tunneling Compressed Multiplexed Traffic Flows
          </span><a moz-do-not-send="true"
            href="http://tools.ietf.org/html/draft-suznjevic-tsvwg-mtd-tcmtf-01">http://tools.ietf.org/html/draft-suznjevic-tsvwg-mtd-tcmtf-01</a><span
            lang="EN-US">.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">It is an extension of
            tcmtf <a moz-do-not-send="true"
              href="http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">
              http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a>.
            Since a specific list for tcmtf exists (<a
              moz-do-not-send="true" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>),
            the idea is to discuss it there.<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">The draft contains
            recommendations for TCMTF multiplexing period for different
            network services as well as description of several policies
            required in the process of packet multiplexing.<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">We are discussing to
            revise the draft once more before the IETF meeting in Berlin
            so your feedback will be very welcome. Thank you.<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">Sincerely,<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">Mirko Suznjevic<o:p></o:p></span></p>
        <p class="MsoNormal"><o:p> </o:p></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
tcmtf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tcmtf">https://www.ietf.org/mailman/listinfo/tcmtf</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------060604080701080901080104--

From navajas@unizar.es  Mon Jun 17 03:15:44 2013
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D7C821F8CDD for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 03:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j47WQMDM2uoM for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 03:15:35 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id BEE0121F8605 for <tcmtf@ietf.org>; Mon, 17 Jun 2013 03:14:56 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5HAEYPm014027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Mon, 17 Jun 2013 12:14:51 +0200
Message-ID: <51BEE18A.2070907@unizar.es>
Date: Mon, 17 Jun 2013 12:14:34 +0200
From: =?ISO-8859-15?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] New version of draft-suznjevic-tsvwg-mtd-tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2013 10:15:44 -0000

Hi all,
I think the specific list for tcmtf is the ideal place to discuss this 
draft.
Thanks Mirko for the work in this draft.
Julián

From navajas@unizar.es  Mon Jun 17 03:15:48 2013
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D58A21F8605 for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 03:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EopWWBueHPQZ for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 03:15:40 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6A96421F85EB for <tcmtf@ietf.org>; Mon, 17 Jun 2013 03:15:00 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5HAElcT014256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Mon, 17 Jun 2013 12:14:59 +0200
Message-ID: <51BEE198.3080809@unizar.es>
Date: Mon, 17 Jun 2013 12:14:48 +0200
From: =?ISO-8859-15?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <E004A7C54DE04F4BB87DB9F32308DA5C0C0E13@MAIL4.fer.hr>
In-Reply-To: <E004A7C54DE04F4BB87DB9F32308DA5C0C0E13@MAIL4.fer.hr>
Content-Type: multipart/alternative; boundary="------------070200040607020701080609"
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] New version of draft-suznjevic-tsvwg-mtd-tcmtf
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2013 10:15:48 -0000

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

Hi all,
I think the specific list for tcmtf is the ideal place to discuss this 
draft.
Thanks Mirko for the work in this draft.
Julián

El 14/06/2013 13:54, Mirko Su¸njevic' escribió:
>
> Hello,
>
> We have just submitted the new version of draft 
>  draft-suznjevic-tsvwg-mtd-tcmtf-01 renamed Delay Limits and 
> Multiplexing Policies to be employed with Tunneling Compressed 
> Multiplexed Traffic Flows 
> http://tools.ietf.org/html/draft-suznjevic-tsvwg-mtd-tcmtf-01.
>
> It is an extension of tcmtf 
> http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/ 
> <http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/>. Since a 
> specific list for tcmtf exists (tcmtf@ietf.org 
> <mailto:tcmtf@ietf.org>), the idea is to discuss it there.
>
> The draft contains recommendations for TCMTF multiplexing period for 
> different network services as well as description of several policies 
> required in the process of packet multiplexing.
>
> We are discussing to revise the draft once more before the IETF 
> meeting in Berlin so your feedback will be very welcome. Thank you.
>
> Sincerely,
>
> Mirko Suznjevic
>
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-15"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi all,<br>
      I think the specific list for tcmtf is the ideal place to discuss
      this draft.<br>
      Thanks Mirko for the work in this draft.<br>
      Julián<br>
      <br>
      El 14/06/2013 13:54, Mirko Su¸njevi&#263; escribió:<br>
    </div>
    <blockquote
      cite="mid:E004A7C54DE04F4BB87DB9F32308DA5C0C0E13@MAIL4.fer.hr"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-15">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span lang="EN-US">Hello,<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">We have just submitted
            the new version of draft  draft-suznjevic-tsvwg-mtd-tcmtf-01
            renamed Delay Limits and Multiplexing Policies to be
            employed with Tunneling Compressed Multiplexed Traffic Flows
          </span><a moz-do-not-send="true"
            href="http://tools.ietf.org/html/draft-suznjevic-tsvwg-mtd-tcmtf-01">http://tools.ietf.org/html/draft-suznjevic-tsvwg-mtd-tcmtf-01</a><span
            lang="EN-US">.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">It is an extension of
            tcmtf <a moz-do-not-send="true"
              href="http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">
              http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a>.
            Since a specific list for tcmtf exists (<a
              moz-do-not-send="true" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>),
            the idea is to discuss it there.<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">The draft contains
            recommendations for TCMTF multiplexing period for different
            network services as well as description of several policies
            required in the process of packet multiplexing.<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">We are discussing to
            revise the draft once more before the IETF meeting in Berlin
            so your feedback will be very welcome. Thank you.<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">Sincerely,<o:p></o:p></span></p>
        <p class="MsoNormal"><span lang="EN-US">Mirko Suznjevic<o:p></o:p></span></p>
        <p class="MsoNormal"><o:p> </o:p></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
tcmtf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tcmtf">https://www.ietf.org/mailman/listinfo/tcmtf</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------070200040607020701080609--

From jruiz@unizar.es  Mon Jun 17 03:39:55 2013
Return-Path: <jruiz@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5AF921F8201 for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 03:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2hZqpShMCM2F for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 03:39:47 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 9F25221F9ADA for <tcmtf@ietf.org>; Mon, 17 Jun 2013 03:38:18 -0700 (PDT)
Received: from [127.0.0.1] (tele2.cps.unizar.es [155.210.156.38]) (authenticated bits=0) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5HAbGSg016027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Mon, 17 Jun 2013 12:37:20 +0200
Message-ID: <51BEE6E6.90208@unizar.es>
Date: Mon, 17 Jun 2013 12:37:26 +0200
From: =?UTF-8?B?Sm9zw6kgUnVpeg==?= <jruiz@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <F5EDC35DF914C1428C28E149F10463A29C8ABCAE@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A29C8ABCAE@EX10-MB2-MAD.hi.inet>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 130616-1, 16/06/2013), Outbound message
X-Antivirus-Status: Clean
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2013 10:39:56 -0000

Hi all,

I agree with you. "TCM optimizers" and "TCM flow" would be enough,

Pepe

El 17/06/2013 11:12, FERNANDO PASCUAL BLANCO escribiÃ³:
> Hi Jose, Julian,
>
>          Yes, "TCM optimizers" and "TCM flow" are perfect for me too.
>
> Best,
>
> Fernando Pascual Blanco
> TelefÃ³nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>
>
>
>
> On 17/06/13 11:02, "JuliÃ¡n FernÃ¡ndez-Navajas" <navajas@unizar.es> wrote:
>
>> I agree with Fernando too, no invent new English verb.
>> In relation with duplicating flow word, i think that it is fine to use
>> "TCM flow" instead of "TCMTF flow".
>> JuliÃ¡n
>>
>> El 17/06/2013 9:31, Jose Saldana escribiÃ³:
>>> Hi, Fernando.
>>>
>>> I agree with you. We are talking about standards so precision is
>>> important.
>>>
>>> I don't think we should use the "verb" "to TCMTF" nor "TCMTFing" nor
>>> "TCMTFed". We cannot invent new English verbs.
>>>
>>> What about "optimization"?. This concept summarizes the three layers.
>>> We can
>>> use it this way:
>>>
>>> - A TCMTF optimizer
>>>
>>> - A packet optimized by means of TCMTF
>>> - A flow optimized by means of TCMTF
>>> - An optimized packet
>>> - An optimized flow
>>> - A TCMTF-optimized packet
>>> - A TCMTF-optimized flow
>>> - A TCMTF packet
>>> - A TCMTF flow
>>>
>>> - the TCMTF optimization can be applied to that flow
>>> - the impact of TCMTF optimization on protocol dynamics
>>>
>>> I have another question here: could we use only TCM instead of TCMTF?
>>> Remember that TF means "traffic flows", so a TCMTF flow would be a
>>> "tunneling compressed multiplexed traffic flows flow". Perhaps a TCM
>>> flow
>>> would be enough in those cases. TCM does not have another related
>>> meaning
>>> and it is shorter than TCMTF (http://www.acronymfinder.com/TCM.html)
>>>
>>> - A TCM optimizer
>>> - A TCM-optimized flow
>>> - A TCM flow
>>>
>>> What do you think?
>>>
>>> Jose
>>>
>>>> -----Mensaje original-----
>>>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>>>> Enviado el: viernes, 14 de junio de 2013 21:29
>>>> Para: jsaldana@unizar.es; tcmtf@ietf.org; tsv-area@ietf.org
>>>> Asunto: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
>>>>
>>>> Hi Jose,
>>>>
>>>>           I like all your changes, they all enrich the WG description.
>>>>
>>>>           Nevertheless I wanted to mention, after read carefully the
>>>> text,
>>> that
>>>> when we talk about layers, we always use the three terms (tunneling,
>>>> multiplexing and compression) and I think it is ok.
>>>>           When we talk about the elements in charge of apply the TCMTF
>>> protocol
>>>> we have call them multiplexers and demultiplexers, and that may be a
>>> little
>>>> confusing, given that they use the name of the middle protocol layer,
>>>> but
>>> I
>>>> understand that we have not found a better name (I include myself here)
>>>> and maybe multiplexing is the most representative layer, so it could be
>>> ok.
>>>>           But in paragraph 8 we talk about multiplexing flows and the
>>>> impact
>>> of
>>>> multiplexing in protocol dynamics, and I think that may be confusing,
>>> given
>>>> that using "multiplexing" we are referring to apply the whole TCMTF
>>> protocol
>>>> or not and not only to apply the multiplexing layer or not. IÂ´m just
>>> saying that
>>>> this term here may be confusing and someone could get a bad
>>>> interpretation
>>>> from the text. I see three option: a) we pre-define the term
>>> "multiplexing"
>>>> as the application of the TCMTF protocol itself, b) we invent the verb
>>>> "to
>>>> TCMTF" and use the participle "TCMTFed" when something is passed trough
>>>> our protocol stack or c) (and maybe the most convenient we use the long
>>>> form "the TCMTF protocol can be applied to that flow" or "the impact of
>>>> TCMTF protocol on protocol dynamics". My suggestion is to use option
>>>> c).
>>>>
>>>>           What do you think?
>>>>
>>>>           Thank you for your great effort!
>>>>
>>>> Best,
>>>>
>>>> Fernando Pascual Blanco
>>>> TelefÃ³nica Global Resources
>>>> Network Automation and Dynamization
>>>> TECHNOLOGY PEOPLE GROUP
>>>> F +34913128779
>>>> M +34682005168
>>>> fpb@tid.es
>>>>
>>>>
>>>>
>>>>
>>>> On 13/06/13 10:43, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>>>
>>>>> These are the main changes included in the draft charter v6 (ordered
>>>>> by
>>>>> paragraphs):
>>>>>
>>>>> 1. I have moved the sentence about the overhead to the end of the
>>>>> paragraph, in order to say that Â³For both the delay-sensitive and
>>>>> delay-insensitive applications, their small data payloads incur
>>>>> significant overheadÂ²
>>>>>
>>>>> 2. I have put the scenarios in bullets, and I have improved some of
>>>>> the
>>>>> descriptions a bit.
>>>>>
>>>>> 6. I have changed the name of the document: instead of Â³document AÂ² it
>>>>> is now Â³TCMTF Â­ reference modelÂ².
>>>>>
>>>>> 7. Now we are talking about another document Â³TCMTF Â­ negotiation
>>>>> protocolÂ².
>>>>> In addition, I have put the two signaling functionalities in bullets.
>>>>>
>>>>> 7. As discussed in the list, we would talk about Â³setup/release a
>>>>> TCMTF
>>>>> sessionÂ².
>>>>>
>>>>> 8. I have changed the name of the document, from Â³document BÂ² to
>>>> Â³TCMTF
>>>>> recommendationsÂ²
>>>>>
>>>>> 8. According to GorryÂ¹s suggestion, I have added this sentence: Â³The
>>>>> eventual impact of multiplexing on protocol dynamics (e.g. when
>>>>> multiplexing TCP flows) will also have to be addressed.Â²
>>>>>
>>>>> Jose
>>>>>
>>>>>
>>>>>> -----Mensaje original-----
>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>>>>>> de Jose Saldana Enviado el: jueves, 13 de junio de 2013 10:38
>>>>>> Para: tcmtf@ietf.org; tsv-area@ietf.org
>>>>>> Asunto: [tcmtf] Improved version of the tmctf Draft charter (v6)
>>>>>>
>>>>>> This is the new proposal, adapted to the new distribution of the
>>>>> documents.
>>>>>> I explain the changes in another e-mail.
>>>>>> It is also here, in a formatted version:
>>>>>> http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf
>>>>>>
>>>>>>
>>>>>> TCMTF charter draft v6
>>>>>>
>>>>>> Description of Working Group
>>>>>>
>>>>>> 1. In the last years we are witnessing the raise of new real-time
>>>>>> services
>>>>> that
>>>>>> use the Internet for the delivery of interactive multimedia
>>>>>> applications: VoIP, videoconferencing, telemedicine, video vigilance,
>>>>> online
>>>>>> gaming, etc. Due to the need of interactivity, many of these services
>>>>>> use  small packets (some tens of bytes), since they have to send
>>>>>> frequent  updates between the extremes of the communication. In
>>>>>> addition, some  other services also send small packets, but they are
>>>>>> not delay-sensitive
>>>>> (e.g.,
>>>>>> instant messaging, m2m packets sending collected data in sensor
>>>>>> networks using wireless or satellite scenarios). For both the
>>>>>> delay-sensitive and
>>>>> delay-
>>>>>> insensitive applications, their small data payloads incur significant
>>>>> overhead,
>>>>>> and it becomes even higher when IPv6 is used, since the basic IPv6
>>>>>> header
>>>>> is
>>>>>> twice the size of the IPv4 one.
>>>>>>
>>>>>> 2. The efficiency cannot be increased by the inclusion of a higher
>>>>>> number
>>>>> of
>>>>>> samples in a single packet, since this would harm the delay
>>>>>> requirements
>>>>> of
>>>>>> the service. But there exist some scenarios in which a number of
>>>>>> flows
>>>>> share
>>>>>> the same path. In this case, packets belonging to different flows can
>>>>>> be grouped together, adding a small multiplexing delay as a
>>>>>> counterpart of bandwidth saving. This delay will have to be
>>>>>> maintained under some threshold in order to grant the delay
>>>>>> requirements. Some examples of the scenarios where grouping packets
>>>>>> is
>>>> possible are:
>>>>>> - aggregation networks of a network operator;
>>>>>> - an end-to-end tunnel between appliances located in two different
>>>>>> offices  of the same company;
>>>>>> - the access connection of an Internet CafÃ© including a high number
>>>>>> of  VoIP/gaming flows;
>>>>>> - an agreement between two network operators could allow them to
>>>>>> compress a number of flows they are exchanging between a pair of
>>>>>> Internet  Routers;
>>>>>> - a satellite connection used for collecting the data of a high
>>>>>> number of  sensors.
>>>>>>
>>>>>> 3. VoIP using RTP is a clear example of a real-time service using
>>>>>> small
>>>>> packets
>>>>>> with high overhead. In order to improve efficiency, RFC4170 (TCRTP)
>>>>> defined
>>>>>> a method for grouping packets when a number of flows share a path,
>>>>>> considering three different layers: header compression by means of
>>>>>> ECRTP;  multiplexing by means of PPPMux; tunneling by means of
>>>>>> L2TPv3.
>>>>>>
>>>>>> 4. However, in the last years, emerging real-time services which do
>>>>>> not
>>>>> use
>>>>>> UDP/RTP have become popular: some of them use UDP or even TCP. In
>>>>>> addition, new header compression methods have been defined (ROHC).
>>>> So
>>>>>> there is a need of widening the scope of RFC4170 in order to consider
>>>>>> not  only UDP/RTP but also other protocols. The same structure of
>>>>>> three layers  will be considered:
>>>>>>
>>>>>> - Header compression: Taking into account that real-time applications
>>>>>> use  different headers (RTP/UDP, UDP or even TCP), different
>>>>>> protocols
>>>>>> can be
>>>>>> used: no compression, ECRTP, IPHC and ROHC.
>>>>>> - Multiplexing: If a number of flows share a path between an origin
>>>>>> and a  destination, a multiplexer can build a bigger packet in which
>>>>>> a
>>>>>> number of  payloads share a common header. A demultiplexer is then
>>>>>> necessary at the  end of the common path, so as to rebuild the
>>>>>> packets
>>>>>> as they were
>>>>> originally
>>>>>> sent. PPPMux will be the main option. Other ones are not discarded.
>>>>>> - Tunneling will be used to send the multiplexed packets end-to-end.
>>>>>> The options in this layer are L2TP, GRE and MPLS.
>>>>>>
>>>>>> 5. So the first objective of this group is to specify the protocol
>>>>>> stack
>>>>> for
>>>>>> tunneling, compressing and multiplexing traffic flows (TCMTF). Since
>>>>>> standard protocols are being used at each layer, the signaling
>>>>>> methods
>>>>>> of  those protocols will be used. Interactions with the Working
>>>>>> Groups
>>>>>> and
>>>>> Areas
>>>>>> in which these protocols are developed can be expected. However, the
>>>>>> development of new compressing, multiplexing or tunneling protocols
>>>>>> is
>>>>>> not  an objective of this Working Group. In addition, since the
>>>>>> current RFC
>>>>> 4170
>>>>>> would be considered as one of the options, this RFC could be
>>>>>> obsoleted.
>>>>>>
>>>>>> 6. As a first objective, a document (TCMTF - reference model) will
>>>>>> define
>>>>> the
>>>>>> different options which can be used at each layer. Specific problems
>>>>> caused
>>>>>> by the interaction between layers will have to be issued, and
>>>>>> suitable extensions may have to be added to the involved protocols.
>>>>>>
>>>>>> 7. If a pair multiplexer/de-multiplexer want to establish a TCMTF
>>>>>> session,  they have first to use a mechanism to negotiate which
>>>>>> concrete option
>>>>> would
>>>>>> they use in each layer: header compression, multiplexing and
>>>>>> tunneling.
>>>>> This
>>>>>> will depend on the protocols that each extreme implements at each
>>>>>> level, and in the scenario. So another document (TCMTF - negotiation
>>>>>> protocol)
>>>>> will
>>>>>> include:
>>>>>>
>>>>>> - a mechanism to setup/release a TCMTF session between a multiplexer
>>>>>> and a de-multiplexer, also including:
>>>>>> - a negotiation mechanism to decide the options to use at each layer
>>>>> (header
>>>>>> compression, multiplexing and tunneling) between multiplexer and de-
>>>>>> multiplexer,
>>>>>>
>>>>>> 8. As a counterpart of the bandwidth saving, TCMTF may add some delay
>>>>>> and  jitter. This is not a problem for the services which are not
>>>>>> sensitive to
>>>>> delay.
>>>>>> However, regarding delay-sensitive services, the Working Group will
>>>>>> also  develop a document (TCMTF - recommendations) with useful
>>>>>> recommendations in order to decide which packet flows can or can not
>>>>>> be  multiplexed and how. The document will present a list of
>>>>>> available
>>>>>> traffic  classification methods which can be used for identification
>>>>>> of the service
>>>>> or
>>>>>> application to which a particular flow belongs, as well as
>>>>>> recommendations
>>>>> of
>>>>>> the maximum delay and jitter to be added depending of the identified
>>>>>> service or application. The eventual impact of multiplexing on
>>>>>> protocol dynamics (e.g., when multiplexing TCP flows) will also have
>>>>>> to be
>>>>> addressed.
>>>>>> 9. If other interesting features are identified, the group would
>>>>> re-charter and
>>>>>> include them, e.g., a mechanism for a multiplexer to discover a de-
>>>>>> multiplexer, and vice versa; a mechanism to select an optimal
>>>>>> multiplexer  and a de-multiplexer when there are more than one
>>>>>> muxer/de-muxer for a  flow; dynamically applying TCMTF: a higher
>>>>>> entity in charge of deciding
>>>>> when
>>>>>> and where, applying or not TCMTF, and what kind of TCMTF, and what
>>>>>> multiplexing period. Additional methods for estimating delay would
>>>>>> also be  required.
>>>>>>
>>>>>> 10. In addition, specific uses of TCMTF, such as in wireless and
>>>>>> satellite  scenarios, could be considered, and it will be studied
>>>>>> whether
>>>>> modifications
>>>>>> or extensions are required on the protocol.
>>>>>>
>>>>>> 11. Interactions with other Working Groups can be expected, since
>>>>>> TCMTF  uses already defined protocols for compression, multiplexing
>>>>>> and tunneling  (ROHC, PPPMux, MPLS, GRE, L2TP).
>>>>>>
>>>>>> Goals and Milestones
>>>>>>
>>>>>> Specification of TCMTF  reference model.
>>>>>>
>>>>>> Specification of TCMTF negotiation protocol.
>>>>>>
>>>>>> Specification of TCMTF recommendations of using existing traffic
>>>>>> classification methods, maximum delay and jitter to add, depending on
>>>>>> the  service.
>>>>>>
>>>>>>
>>>>>> Current version of Document (TCMTF - reference model):
>>>>>> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>>>>>>
>>>>>> Current version of Document (TCMTF - recommendations):
>>>>>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>>>>>>
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> Jose
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> tcmtf mailing list
>>>>>> tcmtf@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>>> _______________________________________________
>>>>> tcmtf mailing list
>>>>> tcmtf@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>> ________________________________
>>>>
>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede
>>>> consultar
>>>> nuestra polÃ­tica de envÃ­o y recepciÃ³n de correo electrÃ³nico en el
>>>> enlace
>>>> situado mÃ¡s abajo.
>>>> This message is intended exclusively for its addressee. We only send
>>>> and
>>>> receive email on the basis of the terms set out at:
>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>
>>>
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
>
> ________________________________
>
> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra polÃ­tica de envÃ­o y recepciÃ³n de correo electrÃ³nico en el enlace situado mÃ¡s abajo.
> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>
>


From jruiz@unizar.es  Mon Jun 17 03:40:53 2013
Return-Path: <jruiz@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4553E21F9B9A for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 03:40:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DIWsJs8WAcq6 for <tcmtf@ietfa.amsl.com>; Mon, 17 Jun 2013 03:40:35 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2ED21F9BEB for <tcmtf@ietf.org>; Mon, 17 Jun 2013 03:39:04 -0700 (PDT)
Received: from [127.0.0.1] (tele2.cps.unizar.es [155.210.156.38]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5HAcwEZ008321 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Mon, 17 Jun 2013 12:38:58 +0200
Message-ID: <51BEE74B.7080104@unizar.es>
Date: Mon, 17 Jun 2013 12:39:07 +0200
From: =?UTF-8?B?Sm9zw6kgUnVpeg==?= <jruiz@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <F5EDC35DF914C1428C28E149F10463A29C8ABCAE@EX10-MB2-MAD.hi.inet>
In-Reply-To: <F5EDC35DF914C1428C28E149F10463A29C8ABCAE@EX10-MB2-MAD.hi.inet>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 130616-1, 16/06/2013), Outbound message
X-Antivirus-Status: Clean
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2013 10:40:53 -0000

Hi all,

I agree with you. "TCM optimizers" and "TCM flow" would be enough,

Pepe

El 17/06/2013 11:12, FERNANDO PASCUAL BLANCO escribiÃ³:
> Hi Jose, Julian,
>
>          Yes, "TCM optimizers" and "TCM flow" are perfect for me too.
>
> Best,
>
> Fernando Pascual Blanco
> TelefÃ³nica Global Resources
> Network Automation and Dynamization
> TECHNOLOGY PEOPLE GROUP
> F +34913128779
> M +34682005168
> fpb@tid.es
>
>
>
>
> On 17/06/13 11:02, "JuliÃ¡n FernÃ¡ndez-Navajas" <navajas@unizar.es> wrote:
>
>> I agree with Fernando too, no invent new English verb.
>> In relation with duplicating flow word, i think that it is fine to use
>> "TCM flow" instead of "TCMTF flow".
>> JuliÃ¡n
>>
>> El 17/06/2013 9:31, Jose Saldana escribiÃ³:
>>> Hi, Fernando.
>>>
>>> I agree with you. We are talking about standards so precision is
>>> important.
>>>
>>> I don't think we should use the "verb" "to TCMTF" nor "TCMTFing" nor
>>> "TCMTFed". We cannot invent new English verbs.
>>>
>>> What about "optimization"?. This concept summarizes the three layers.
>>> We can
>>> use it this way:
>>>
>>> - A TCMTF optimizer
>>>
>>> - A packet optimized by means of TCMTF
>>> - A flow optimized by means of TCMTF
>>> - An optimized packet
>>> - An optimized flow
>>> - A TCMTF-optimized packet
>>> - A TCMTF-optimized flow
>>> - A TCMTF packet
>>> - A TCMTF flow
>>>
>>> - the TCMTF optimization can be applied to that flow
>>> - the impact of TCMTF optimization on protocol dynamics
>>>
>>> I have another question here: could we use only TCM instead of TCMTF?
>>> Remember that TF means "traffic flows", so a TCMTF flow would be a
>>> "tunneling compressed multiplexed traffic flows flow". Perhaps a TCM
>>> flow
>>> would be enough in those cases. TCM does not have another related
>>> meaning
>>> and it is shorter than TCMTF (http://www.acronymfinder.com/TCM.html)
>>>
>>> - A TCM optimizer
>>> - A TCM-optimized flow
>>> - A TCM flow
>>>
>>> What do you think?
>>>
>>> Jose
>>>
>>>


From diego@tid.es  Mon Jun 17 06:40:38 2013
Return-Path: <diego@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB91921F91CE; Mon, 17 Jun 2013 06:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BAOd9aZAUMIR; Mon, 17 Jun 2013 06:40:35 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 50D7C21F8E8C; Mon, 17 Jun 2013 06:40:33 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MOJ00I1MHZILH@tid.hi.inet>; Mon, 17 Jun 2013 15:40:31 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id BA.1A.05654.FC11FB15; Mon, 17 Jun 2013 15:40:31 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MOJ00I1PHZJLH@tid.hi.inet>; Mon, 17 Jun 2013 15:40:31 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS8-MAD.hi.inet ([fe80::41c8:e965:8a6:de67%11]) with mapi id 14.02.0328.009; Mon, 17 Jun 2013 15:40:30 +0200
Date: Mon, 17 Jun 2013 13:39:35 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <004a01ce6b2c$c640ed80$52c2c880$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "<jsaldana@unizar.es>" <jsaldana@unizar.es>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A049CCE340F@EX10-MB2-MAD.hi.inet>
Content-id: <0D78D1ED9A64DA4096C16C0A820445EE@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Improved version of the tmctf Draft charter (v6)
Thread-index: Ac5oEUJh6X32UcmxT3KmocW8KKc14f//3/+AgAJobQCAA8z8gIAANnKA
X-AuditID: 0a5f4e69-b7f4b6d000001616-bc-51bf11cf2ae6
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupmkeLIzCtJLcpLzFFi42Lhivcz1D0vuD/Q4EWPmMWuzxsYLRa8Wczs wOSxZMlPpgDGKC6blNSczLLUIn27BK6Mx7c+sBf0VFQ8nv6YqYFxTmIXIyeHhICJxIT7n1kg bDGJC/fWs4HYQgLbGSVa31lB2M8YJVats+9i5AKyNzBKzN+xjR0kwSKgKtHw8hsTiM0GZD9q /g0WFxZwlfjw8QfYIE4BC4nJ9w8zQyxQkPhz7jHYMhEBfYkbjyHqmQWqJPZs3c8IYvMKeEus vvKDESJuJnF33392iLigxI/J91gg4joSvd+/MUPY4hLNrTeh4toST95dYAWxGQVkJd7Nn88K sctN4tOEI3D2psu32CDuEZBYsuc81G2iEi8f/2OFeHI5o8TWtp2MExglZiG5YxaSO2YhuWMW kjtmIbljASPrKkax4qSizPSMktzEzJx0AyO9jEy9zLzUkk2MkAjM3MG4fKfKIUYBDkYlHl6O un2BQqyJZcWVuYcYJTiYlUR4YycChXhTEiurUovy44tKc1KLDzEycXBKNTCyHTGMvxN1zSO+ 8dfLswsfi/uf+mU73yZDnNFocVzczzlMLNx+k87VH55uql29dPnxKods3eglyXdWHmg7/5aF uykkdFLUsiUfWdwvXrvwfuLLf39sEx6qnTLZ9ENns+yH5b9+c7TmHJw5qWOZh/Grd1dE720M 2VxszD3pl+XcraYFyzJr8s8tUWIpzkg01GIuKk4EANGeGBKeAgAA
References: <006501ce6812$060676b0$12136410$@unizar.es> <F5EDC35DF914C1428C28E149F10463A29C8AA7DC@EX10-MB2-MAD.hi.inet> <004a01ce6b2c$c640ed80$52c2c880$@unizar.es>
Cc: "<tcmtf@ietf.org>" <tcmtf@ietf.org>, "<tsv-area@ietf.org>" <tsv-area@ietf.org>, FERNANDO PASCUAL BLANCO <fpb@tid.es>
Subject: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2013 13:40:39 -0000

Hi Jose,

I like your latter proposal. TCM-* should be enough: TCMTF technology is pr=
ovided (and leveraged) by TCM-* elements.

Only a comment on your first statement: we *can* invent new English verbs. =
English does not have stupid institutions like our Academy, but this is a c=
ompletely different discussion...

Be goode,

On 17 Jun 2013, at 09:31 , Jose Saldana wrote:

> Hi, Fernando.
>
> I agree with you. We are talking about standards so precision is importan=
t.
>
> I don't think we should use the "verb" "to TCMTF" nor "TCMTFing" nor
> "TCMTFed". We cannot invent new English verbs.
>
> What about "optimization"?. This concept summarizes the three layers. We =
can
> use it this way:
>
> - A TCMTF optimizer
>
> - A packet optimized by means of TCMTF
> - A flow optimized by means of TCMTF
> - An optimized packet
> - An optimized flow
> - A TCMTF-optimized packet
> - A TCMTF-optimized flow
> - A TCMTF packet
> - A TCMTF flow
>
> - the TCMTF optimization can be applied to that flow
> - the impact of TCMTF optimization on protocol dynamics
>
> I have another question here: could we use only TCM instead of TCMTF?
> Remember that TF means "traffic flows", so a TCMTF flow would be a
> "tunneling compressed multiplexed traffic flows flow". Perhaps a TCM flow
> would be enough in those cases. TCM does not have another related meaning
> and it is shorter than TCMTF (http://www.acronymfinder.com/TCM.html)
>
> - A TCM optimizer
> - A TCM-optimized flow
> - A TCM flow
>
> What do you think?
>
> Jose
>
>> -----Mensaje original-----
>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es]
>> Enviado el: viernes, 14 de junio de 2013 21:29
>> Para: jsaldana@unizar.es; tcmtf@ietf.org; tsv-area@ietf.org
>> Asunto: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
>>
>> Hi Jose,
>>
>>        I like all your changes, they all enrich the WG description.
>>
>>        Nevertheless I wanted to mention, after read carefully the text,
> that
>> when we talk about layers, we always use the three terms (tunneling,
>> multiplexing and compression) and I think it is ok.
>>        When we talk about the elements in charge of apply the TCMTF
> protocol
>> we have call them multiplexers and demultiplexers, and that may be a
> little
>> confusing, given that they use the name of the middle protocol layer, bu=
t
> I
>> understand that we have not found a better name (I include myself here)
>> and maybe multiplexing is the most representative layer, so it could be
> ok.
>>        But in paragraph 8 we talk about multiplexing flows and the impac=
t
> of
>> multiplexing in protocol dynamics, and I think that may be confusing,
> given
>> that using "multiplexing" we are referring to apply the whole TCMTF
> protocol
>> or not and not only to apply the multiplexing layer or not. I=B4m just
> saying that
>> this term here may be confusing and someone could get a bad interpretati=
on
>> from the text. I see three option: a) we pre-define the term
> "multiplexing"
>> as the application of the TCMTF protocol itself, b) we invent the verb "=
to
>> TCMTF" and use the participle "TCMTFed" when something is passed trough
>> our protocol stack or c) (and maybe the most convenient we use the long
>> form "the TCMTF protocol can be applied to that flow" or "the impact of
>> TCMTF protocol on protocol dynamics". My suggestion is to use option c).
>>
>>        What do you think?
>>
>>        Thank you for your great effort!
>>
>> Best,
>>
>> Fernando Pascual Blanco
>> Telef=F3nica Global Resources
>> Network Automation and Dynamization
>> TECHNOLOGY PEOPLE GROUP
>> F +34913128779
>> M +34682005168
>> fpb@tid.es
>>
>>
>>
>>
>> On 13/06/13 10:43, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>
>>> These are the main changes included in the draft charter v6 (ordered by
>>> paragraphs):
>>>
>>> 1. I have moved the sentence about the overhead to the end of the
>>> paragraph, in order to say that =B3For both the delay-sensitive and
>>> delay-insensitive applications, their small data payloads incur
>>> significant overhead=B2
>>>
>>> 2. I have put the scenarios in bullets, and I have improved some of the
>>> descriptions a bit.
>>>
>>> 6. I have changed the name of the document: instead of =B3document A=B2=
 it
>>> is now =B3TCMTF =AD reference model=B2.
>>>
>>> 7. Now we are talking about another document =B3TCMTF =AD negotiation
>>> protocol=B2.
>>> In addition, I have put the two signaling functionalities in bullets.
>>>
>>> 7. As discussed in the list, we would talk about =B3setup/release a TCM=
TF
>>> session=B2.
>>>
>>> 8. I have changed the name of the document, from =B3document B=B2 to
>> =B3TCMTF
>>> recommendations=B2
>>>
>>> 8. According to Gorry=B9s suggestion, I have added this sentence: =B3Th=
e
>>> eventual impact of multiplexing on protocol dynamics (e.g. when
>>> multiplexing TCP flows) will also have to be addressed.=B2
>>>
>>> Jose
>>>
>>>
>>>> -----Mensaje original-----
>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre
>>>> de Jose Saldana Enviado el: jueves, 13 de junio de 2013 10:38
>>>> Para: tcmtf@ietf.org; tsv-area@ietf.org
>>>> Asunto: [tcmtf] Improved version of the tmctf Draft charter (v6)
>>>>
>>>> This is the new proposal, adapted to the new distribution of the
>>> documents.
>>>> I explain the changes in another e-mail.
>>>> It is also here, in a formatted version:
>>>> http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf
>>>>
>>>>
>>>> TCMTF charter draft v6
>>>>
>>>> Description of Working Group
>>>>
>>>> 1. In the last years we are witnessing the raise of new real-time
>>>> services
>>> that
>>>> use the Internet for the delivery of interactive multimedia
>>>> applications: VoIP, videoconferencing, telemedicine, video vigilance,
>>> online
>>>> gaming, etc. Due to the need of interactivity, many of these services
>>>> use  small packets (some tens of bytes), since they have to send
>>>> frequent  updates between the extremes of the communication. In
>>>> addition, some  other services also send small packets, but they are
>>>> not delay-sensitive
>>> (e.g.,
>>>> instant messaging, m2m packets sending collected data in sensor
>>>> networks using wireless or satellite scenarios). For both the
>>>> delay-sensitive and
>>> delay-
>>>> insensitive applications, their small data payloads incur significant
>>> overhead,
>>>> and it becomes even higher when IPv6 is used, since the basic IPv6
>>>> header
>>> is
>>>> twice the size of the IPv4 one.
>>>>
>>>> 2. The efficiency cannot be increased by the inclusion of a higher
>>>> number
>>> of
>>>> samples in a single packet, since this would harm the delay
>>>> requirements
>>> of
>>>> the service. But there exist some scenarios in which a number of
>>>> flows
>>> share
>>>> the same path. In this case, packets belonging to different flows can
>>>> be grouped together, adding a small multiplexing delay as a
>>>> counterpart of bandwidth saving. This delay will have to be
>>>> maintained under some threshold in order to grant the delay
>>>> requirements. Some examples of the scenarios where grouping packets is
>> possible are:
>>>>
>>>> - aggregation networks of a network operator;
>>>> - an end-to-end tunnel between appliances located in two different
>>>> offices  of the same company;
>>>> - the access connection of an Internet Caf=E9 including a high number
>>>> of  VoIP/gaming flows;
>>>> - an agreement between two network operators could allow them to
>>>> compress a number of flows they are exchanging between a pair of
>>>> Internet  Routers;
>>>> - a satellite connection used for collecting the data of a high
>>>> number of  sensors.
>>>>
>>>> 3. VoIP using RTP is a clear example of a real-time service using
>>>> small
>>> packets
>>>> with high overhead. In order to improve efficiency, RFC4170 (TCRTP)
>>> defined
>>>> a method for grouping packets when a number of flows share a path,
>>>> considering three different layers: header compression by means of
>>>> ECRTP;  multiplexing by means of PPPMux; tunneling by means of L2TPv3.
>>>>
>>>> 4. However, in the last years, emerging real-time services which do
>>>> not
>>> use
>>>> UDP/RTP have become popular: some of them use UDP or even TCP. In
>>>> addition, new header compression methods have been defined (ROHC).
>> So
>>>> there is a need of widening the scope of RFC4170 in order to consider
>>>> not  only UDP/RTP but also other protocols. The same structure of
>>>> three layers  will be considered:
>>>>
>>>> - Header compression: Taking into account that real-time applications
>>>> use  different headers (RTP/UDP, UDP or even TCP), different protocols
>>>> can be
>>>> used: no compression, ECRTP, IPHC and ROHC.
>>>> - Multiplexing: If a number of flows share a path between an origin
>>>> and a  destination, a multiplexer can build a bigger packet in which a
>>>> number of  payloads share a common header. A demultiplexer is then
>>>> necessary at the  end of the common path, so as to rebuild the packets
>>>> as they were
>>> originally
>>>> sent. PPPMux will be the main option. Other ones are not discarded.
>>>> - Tunneling will be used to send the multiplexed packets end-to-end.
>>>> The options in this layer are L2TP, GRE and MPLS.
>>>>
>>>> 5. So the first objective of this group is to specify the protocol
>>>> stack
>>> for
>>>> tunneling, compressing and multiplexing traffic flows (TCMTF). Since
>>>> standard protocols are being used at each layer, the signaling methods
>>>> of  those protocols will be used. Interactions with the Working Groups
>>>> and
>>> Areas
>>>> in which these protocols are developed can be expected. However, the
>>>> development of new compressing, multiplexing or tunneling protocols is
>>>> not  an objective of this Working Group. In addition, since the
>>>> current RFC
>>> 4170
>>>> would be considered as one of the options, this RFC could be obsoleted=
.
>>>>
>>>> 6. As a first objective, a document (TCMTF - reference model) will
>>>> define
>>> the
>>>> different options which can be used at each layer. Specific problems
>>> caused
>>>> by the interaction between layers will have to be issued, and
>>>> suitable extensions may have to be added to the involved protocols.
>>>>
>>>> 7. If a pair multiplexer/de-multiplexer want to establish a TCMTF
>>>> session,  they have first to use a mechanism to negotiate which
>>>> concrete option
>>> would
>>>> they use in each layer: header compression, multiplexing and tunneling=
.
>>> This
>>>> will depend on the protocols that each extreme implements at each
>>>> level, and in the scenario. So another document (TCMTF - negotiation
>>>> protocol)
>>> will
>>>> include:
>>>>
>>>> - a mechanism to setup/release a TCMTF session between a multiplexer
>>>> and a de-multiplexer, also including:
>>>> - a negotiation mechanism to decide the options to use at each layer
>>> (header
>>>> compression, multiplexing and tunneling) between multiplexer and de-
>>>> multiplexer,
>>>>
>>>> 8. As a counterpart of the bandwidth saving, TCMTF may add some delay
>>>> and  jitter. This is not a problem for the services which are not
>>>> sensitive to
>>> delay.
>>>> However, regarding delay-sensitive services, the Working Group will
>>>> also  develop a document (TCMTF - recommendations) with useful
>>>> recommendations in order to decide which packet flows can or can not
>>>> be  multiplexed and how. The document will present a list of available
>>>> traffic  classification methods which can be used for identification
>>>> of the service
>>> or
>>>> application to which a particular flow belongs, as well as
>>>> recommendations
>>> of
>>>> the maximum delay and jitter to be added depending of the identified
>>>> service or application. The eventual impact of multiplexing on
>>>> protocol dynamics (e.g., when multiplexing TCP flows) will also have
>>>> to be
>>> addressed.
>>>>
>>>> 9. If other interesting features are identified, the group would
>>> re-charter and
>>>> include them, e.g., a mechanism for a multiplexer to discover a de-
>>>> multiplexer, and vice versa; a mechanism to select an optimal
>>>> multiplexer  and a de-multiplexer when there are more than one
>>>> muxer/de-muxer for a  flow; dynamically applying TCMTF: a higher
>>>> entity in charge of deciding
>>> when
>>>> and where, applying or not TCMTF, and what kind of TCMTF, and what
>>>> multiplexing period. Additional methods for estimating delay would
>>>> also be  required.
>>>>
>>>> 10. In addition, specific uses of TCMTF, such as in wireless and
>>>> satellite  scenarios, could be considered, and it will be studied
>>>> whether
>>> modifications
>>>> or extensions are required on the protocol.
>>>>
>>>> 11. Interactions with other Working Groups can be expected, since
>>>> TCMTF  uses already defined protocols for compression, multiplexing
>>>> and tunneling  (ROHC, PPPMux, MPLS, GRE, L2TP).
>>>>
>>>> Goals and Milestones
>>>>
>>>> Specification of TCMTF  reference model.
>>>>
>>>> Specification of TCMTF negotiation protocol.
>>>>
>>>> Specification of TCMTF recommendations of using existing traffic
>>>> classification methods, maximum delay and jitter to add, depending on
>>>> the  service.
>>>>
>>>>
>>>> Current version of Document (TCMTF - reference model):
>>>> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>>>>
>>>> Current version of Document (TCMTF - recommendations):
>>>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> Jose
>>>>
>>>>
>>>> _______________________________________________
>>>> tcmtf mailing list
>>>> tcmtf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>
>>
>> ________________________________
>>
>> 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


--
"Esta vez no fallaremos, Doctor Infierno"

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

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


________________________________

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

From jsaldana@unizar.es  Tue Jun 18 04:04:28 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAE4821F9B7A for <tcmtf@ietfa.amsl.com>; Tue, 18 Jun 2013 04:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.47
X-Spam-Level: 
X-Spam-Status: No, score=-6.47 tagged_above=-999 required=5 tests=[AWL=0.129,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lq9as34f4stg for <tcmtf@ietfa.amsl.com>; Tue, 18 Jun 2013 04:04:21 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 660DE21F8831 for <tcmtf@ietf.org>; Tue, 18 Jun 2013 04:04:20 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5IB4G9c015294 for <tcmtf@ietf.org>; Tue, 18 Jun 2013 13:04:17 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Tue, 18 Jun 2013 13:04:18 +0200
Organization: Universidad de Zaragoza
Message-ID: <004101ce6c13$9438c550$bcaa4ff0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5sEOGjjRpMkCRdS0mDI8loAlISGA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] Glossary of TCMTF terms
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 11:04:29 -0000

Hi,

Mirko and I included an "index term" at the beginning of the TCMTF -
recommendations draft. Perhaps we could consider the possibility of also
including one TCMTF - reference model draft.

Here go some definition proposals, which can of course be improved:

TCM-optimizer / TCMTF-optimizer

   The host where TCM optimization (also TCMTF optimization) is =
deployed.
It corresponds to both  the
   ingress and the egress of the tunnel where native packets are =
included.

   If the optimizer  compresses headers, multiplexes packets and creates =
the
tunnel, it behaves as a "TCM-ingress optimizer".
 =20
   If it decompresses headers, demultiplexes packets and extracts =
packets
from the tunnel, it behaves as a "TCM-egress optimizer".

policy manager

   A network entity which makes the decisions about TCMTF parameters:
   multiplexing period; flows to be multiplexed together, depending on
   their IP addresses, ports, etc.  It is connected with a number of
   TCMTF multiplexers and demultiplexers, and orchestrates the
   optimization that takes place between them.

native packet

   A packet sent by an application, belonging to a flow that can be
   optimized by means of TCMTF.

native flow

   A flow of native packets.

TCM packet / optimized packet / TCM-optimized packet

   A packet including a number of multiplexed and header-compressed
   native ones, and also a tunneling header.

TCM flow / optimized flow / TCM-optimized flow

   A flow of TCM packets.


Best regards,

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de
> Diego R. Lopez
> Enviado el: lunes, 17 de junio de 2013 15:40
> Para: <jsaldana@unizar.es>
> CC: <tcmtf@ietf.org>; <tsv-area@ietf.org>; FERNANDO PASCUAL BLANCO
> Asunto: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
>=20
> Hi Jose,
>=20
> I like your latter proposal. TCM-* should be enough: TCMTF technology =
is
> provided (and leveraged) by TCM-* elements.
>=20
> Only a comment on your first statement: we *can* invent new English =
verbs.
> English does not have stupid institutions like our Academy, but this =
is a
> completely different discussion...
>=20
> Be goode,
>=20
> On 17 Jun 2013, at 09:31 , Jose Saldana wrote:
>=20
> > Hi, Fernando.
> >
> > I agree with you. We are talking about standards so precision is
important.
> >
> > I don't think we should use the "verb" "to TCMTF" nor "TCMTFing" nor
> > "TCMTFed". We cannot invent new English verbs.
> >
> > What about "optimization"?. This concept summarizes the three =
layers.
> > We can use it this way:
> >
> > - A TCMTF optimizer
> >
> > - A packet optimized by means of TCMTF
> > - A flow optimized by means of TCMTF
> > - An optimized packet
> > - An optimized flow
> > - A TCMTF-optimized packet
> > - A TCMTF-optimized flow
> > - A TCMTF packet
> > - A TCMTF flow
> >
> > - the TCMTF optimization can be applied to that flow
> > - the impact of TCMTF optimization on protocol dynamics
> >
> > I have another question here: could we use only TCM instead of =
TCMTF?
> > Remember that TF means "traffic flows", so a TCMTF flow would be a
> > "tunneling compressed multiplexed traffic flows flow". Perhaps a TCM
> > flow would be enough in those cases. TCM does not have another =
related
> > meaning and it is shorter than TCMTF
> > (http://www.acronymfinder.com/TCM.html)
> >
> > - A TCM optimizer
> > - A TCM-optimized flow
> > - A TCM flow
> >
> > What do you think?
> >
> > Jose
> >
> >> -----Mensaje original-----
> >> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es] Enviado el:
> viernes,
> >> 14 de junio de 2013 21:29
> >> Para: jsaldana@unizar.es; tcmtf@ietf.org; tsv-area@ietf.org
> >> Asunto: Re: [tcmtf] Improved version of the tmctf Draft charter =
(v6)
> >>
> >> Hi Jose,
> >>
> >>        I like all your changes, they all enrich the WG description.
> >>
> >>        Nevertheless I wanted to mention, after read carefully the
> >> text,
> > that
> >> when we talk about layers, we always use the three terms =
(tunneling,
> >> multiplexing and compression) and I think it is ok.
> >>        When we talk about the elements in charge of apply the TCMTF
> > protocol
> >> we have call them multiplexers and demultiplexers, and that may be =
a
> > little
> >> confusing, given that they use the name of the middle protocol =
layer,
> >> but
> > I
> >> understand that we have not found a better name (I include myself
> >> here) and maybe multiplexing is the most representative layer, so =
it
> >> could be
> > ok.
> >>        But in paragraph 8 we talk about multiplexing flows and the
> >> impact
> > of
> >> multiplexing in protocol dynamics, and I think that may be =
confusing,
> > given
> >> that using "multiplexing" we are referring to apply the whole TCMTF
> > protocol
> >> or not and not only to apply the multiplexing layer or not. I=B4m =
just
> > saying that
> >> this term here may be confusing and someone could get a bad
> >> interpretation from the text. I see three option: a) we pre-define
> >> the term
> > "multiplexing"
> >> as the application of the TCMTF protocol itself, b) we invent the
> >> verb "to TCMTF" and use the participle "TCMTFed" when something is
> >> passed trough our protocol stack or c) (and maybe the most =
convenient
> >> we use the long form "the TCMTF protocol can be applied to that =
flow"
> >> or "the impact of TCMTF protocol on protocol dynamics". My =
suggestion
is
> to use option c).
> >>
> >>        What do you think?
> >>
> >>        Thank you for your great effort!
> >>
> >> Best,
> >>
> >> Fernando Pascual Blanco
> >> Telef=F3nica Global Resources
> >> Network Automation and Dynamization
> >> TECHNOLOGY PEOPLE GROUP
> >> F +34913128779
> >> M +34682005168
> >> fpb@tid.es
> >>
> >>
> >>
> >>
> >> On 13/06/13 10:43, "Jose Saldana" <jsaldana@unizar.es> wrote:
> >>
> >>> These are the main changes included in the draft charter v6 =
(ordered
> >>> by
> >>> paragraphs):
> >>>
> >>> 1. I have moved the sentence about the overhead to the end of the
> >>> paragraph, in order to say that =B3For both the delay-sensitive =
and
> >>> delay-insensitive applications, their small data payloads incur
> >>> significant overhead=B2
> >>>
> >>> 2. I have put the scenarios in bullets, and I have improved some =
of
> >>> the descriptions a bit.
> >>>
> >>> 6. I have changed the name of the document: instead of =B3document =
A=B2
> >>> it is now =B3TCMTF =AD reference model=B2.
> >>>
> >>> 7. Now we are talking about another document =B3TCMTF =AD =
negotiation
> >>> protocol=B2.
> >>> In addition, I have put the two signaling functionalities in =
bullets.
> >>>
> >>> 7. As discussed in the list, we would talk about =B3setup/release =
a
> >>> TCMTF session=B2.
> >>>
> >>> 8. I have changed the name of the document, from =B3document B=B2 =
to
> >> =B3TCMTF
> >>> recommendations=B2
> >>>
> >>> 8. According to Gorry=B9s suggestion, I have added this sentence: =
=B3The
> >>> eventual impact of multiplexing on protocol dynamics (e.g. when
> >>> multiplexing TCP flows) will also have to be addressed.=B2
> >>>
> >>> Jose
> >>>
> >>>
> >>>> -----Mensaje original-----
> >>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
> >>>> nombre de Jose Saldana Enviado el: jueves, 13 de junio de 2013
> >>>> 10:38
> >>>> Para: tcmtf@ietf.org; tsv-area@ietf.org
> >>>> Asunto: [tcmtf] Improved version of the tmctf Draft charter (v6)
> >>>>
> >>>> This is the new proposal, adapted to the new distribution of the
> >>> documents.
> >>>> I explain the changes in another e-mail.
> >>>> It is also here, in a formatted version:
> >>>> =
http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.p
> >>>> df
> >>>>
> >>>>
> >>>> TCMTF charter draft v6
> >>>>
> >>>> Description of Working Group
> >>>>
> >>>> 1. In the last years we are witnessing the raise of new real-time
> >>>> services
> >>> that
> >>>> use the Internet for the delivery of interactive multimedia
> >>>> applications: VoIP, videoconferencing, telemedicine, video
> >>>> vigilance,
> >>> online
> >>>> gaming, etc. Due to the need of interactivity, many of these
> >>>> services use  small packets (some tens of bytes), since they have
> >>>> to send frequent  updates between the extremes of the
> >>>> communication. In addition, some  other services also send small
> >>>> packets, but they are not delay-sensitive
> >>> (e.g.,
> >>>> instant messaging, m2m packets sending collected data in sensor
> >>>> networks using wireless or satellite scenarios). For both the
> >>>> delay-sensitive and
> >>> delay-
> >>>> insensitive applications, their small data payloads incur
> >>>> significant
> >>> overhead,
> >>>> and it becomes even higher when IPv6 is used, since the basic =
IPv6
> >>>> header
> >>> is
> >>>> twice the size of the IPv4 one.
> >>>>
> >>>> 2. The efficiency cannot be increased by the inclusion of a =
higher
> >>>> number
> >>> of
> >>>> samples in a single packet, since this would harm the delay
> >>>> requirements
> >>> of
> >>>> the service. But there exist some scenarios in which a number of
> >>>> flows
> >>> share
> >>>> the same path. In this case, packets belonging to different flows
> >>>> can be grouped together, adding a small multiplexing delay as a
> >>>> counterpart of bandwidth saving. This delay will have to be
> >>>> maintained under some threshold in order to grant the delay
> >>>> requirements. Some examples of the scenarios where grouping
> packets
> >>>> is
> >> possible are:
> >>>>
> >>>> - aggregation networks of a network operator;
> >>>> - an end-to-end tunnel between appliances located in two =
different
> >>>> offices  of the same company;
> >>>> - the access connection of an Internet Caf=E9 including a high =
number
> >>>> of  VoIP/gaming flows;
> >>>> - an agreement between two network operators could allow them to
> >>>> compress a number of flows they are exchanging between a pair of
> >>>> Internet  Routers;
> >>>> - a satellite connection used for collecting the data of a high
> >>>> number of  sensors.
> >>>>
> >>>> 3. VoIP using RTP is a clear example of a real-time service using
> >>>> small
> >>> packets
> >>>> with high overhead. In order to improve efficiency, RFC4170 =
(TCRTP)
> >>> defined
> >>>> a method for grouping packets when a number of flows share a =
path,
> >>>> considering three different layers: header compression by means =
of
> >>>> ECRTP;  multiplexing by means of PPPMux; tunneling by means of
> L2TPv3.
> >>>>
> >>>> 4. However, in the last years, emerging real-time services which =
do
> >>>> not
> >>> use
> >>>> UDP/RTP have become popular: some of them use UDP or even TCP. In
> >>>> addition, new header compression methods have been defined
> (ROHC).
> >> So
> >>>> there is a need of widening the scope of RFC4170 in order to
> >>>> consider not  only UDP/RTP but also other protocols. The same
> >>>> structure of three layers  will be considered:
> >>>>
> >>>> - Header compression: Taking into account that real-time
> >>>> applications use  different headers (RTP/UDP, UDP or even TCP),
> >>>> different protocols can be
> >>>> used: no compression, ECRTP, IPHC and ROHC.
> >>>> - Multiplexing: If a number of flows share a path between an =
origin
> >>>> and a  destination, a multiplexer can build a bigger packet in
> >>>> which a number of  payloads share a common header. A =
demultiplexer
> >>>> is then necessary at the  end of the common path, so as to =
rebuild
> >>>> the packets as they were
> >>> originally
> >>>> sent. PPPMux will be the main option. Other ones are not =
discarded.
> >>>> - Tunneling will be used to send the multiplexed packets =
end-to-end.
> >>>> The options in this layer are L2TP, GRE and MPLS.
> >>>>
> >>>> 5. So the first objective of this group is to specify the =
protocol
> >>>> stack
> >>> for
> >>>> tunneling, compressing and multiplexing traffic flows (TCMTF).
> >>>> Since standard protocols are being used at each layer, the
> >>>> signaling methods of  those protocols will be used. Interactions
> >>>> with the Working Groups and
> >>> Areas
> >>>> in which these protocols are developed can be expected. However,
> >>>> the development of new compressing, multiplexing or tunneling
> >>>> protocols is not  an objective of this Working Group. In =
addition,
> >>>> since the current RFC
> >>> 4170
> >>>> would be considered as one of the options, this RFC could be
> obsoleted.
> >>>>
> >>>> 6. As a first objective, a document (TCMTF - reference model) =
will
> >>>> define
> >>> the
> >>>> different options which can be used at each layer. Specific
> >>>> problems
> >>> caused
> >>>> by the interaction between layers will have to be issued, and
> >>>> suitable extensions may have to be added to the involved =
protocols.
> >>>>
> >>>> 7. If a pair multiplexer/de-multiplexer want to establish a TCMTF
> >>>> session,  they have first to use a mechanism to negotiate which
> >>>> concrete option
> >>> would
> >>>> they use in each layer: header compression, multiplexing and
> tunneling.
> >>> This
> >>>> will depend on the protocols that each extreme implements at each
> >>>> level, and in the scenario. So another document (TCMTF -
> >>>> negotiation
> >>>> protocol)
> >>> will
> >>>> include:
> >>>>
> >>>> - a mechanism to setup/release a TCMTF session between a
> >>>> multiplexer and a de-multiplexer, also including:
> >>>> - a negotiation mechanism to decide the options to use at each
> >>>> layer
> >>> (header
> >>>> compression, multiplexing and tunneling) between multiplexer and
> >>>> de- multiplexer,
> >>>>
> >>>> 8. As a counterpart of the bandwidth saving, TCMTF may add some
> >>>> delay and  jitter. This is not a problem for the services which =
are
> >>>> not sensitive to
> >>> delay.
> >>>> However, regarding delay-sensitive services, the Working Group =
will
> >>>> also  develop a document (TCMTF - recommendations) with useful
> >>>> recommendations in order to decide which packet flows can or can
> >>>> not be  multiplexed and how. The document will present a list of
> >>>> available traffic  classification methods which can be used for
> >>>> identification of the service
> >>> or
> >>>> application to which a particular flow belongs, as well as
> >>>> recommendations
> >>> of
> >>>> the maximum delay and jitter to be added depending of the
> >>>> identified service or application. The eventual impact of
> >>>> multiplexing on protocol dynamics (e.g., when multiplexing TCP
> >>>> flows) will also have to be
> >>> addressed.
> >>>>
> >>>> 9. If other interesting features are identified, the group would
> >>> re-charter and
> >>>> include them, e.g., a mechanism for a multiplexer to discover a =
de-
> >>>> multiplexer, and vice versa; a mechanism to select an optimal
> >>>> multiplexer  and a de-multiplexer when there are more than one
> >>>> muxer/de-muxer for a  flow; dynamically applying TCMTF: a higher
> >>>> entity in charge of deciding
> >>> when
> >>>> and where, applying or not TCMTF, and what kind of TCMTF, and =
what
> >>>> multiplexing period. Additional methods for estimating delay =
would
> >>>> also be  required.
> >>>>
> >>>> 10. In addition, specific uses of TCMTF, such as in wireless and
> >>>> satellite  scenarios, could be considered, and it will be studied
> >>>> whether
> >>> modifications
> >>>> or extensions are required on the protocol.
> >>>>
> >>>> 11. Interactions with other Working Groups can be expected, since
> >>>> TCMTF  uses already defined protocols for compression, =
multiplexing
> >>>> and tunneling  (ROHC, PPPMux, MPLS, GRE, L2TP).
> >>>>
> >>>> Goals and Milestones
> >>>>
> >>>> Specification of TCMTF  reference model.
> >>>>
> >>>> Specification of TCMTF negotiation protocol.
> >>>>
> >>>> Specification of TCMTF recommendations of using existing traffic
> >>>> classification methods, maximum delay and jitter to add, =
depending
> >>>> on the  service.
> >>>>
> >>>>
> >>>> Current version of Document (TCMTF - reference model):
> >>>> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
> >>>>
> >>>> Current version of Document (TCMTF - recommendations):
> >>>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
> >>>>
> >>>>
> >>>> Best regards,
> >>>>
> >>>> Jose
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> tcmtf mailing list
> >>>> tcmtf@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>>
> >>> _______________________________________________
> >>> tcmtf mailing list
> >>> tcmtf@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/tcmtf
> >>
> >>
> >> ________________________________
> >>
> >> Este mensaje se dirige exclusivamente a su destinatario. Puede
> >> consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico
> >> en el enlace situado m=E1s abajo.
> >> This message is intended exclusively for its addressee. We only =
send
> >> and receive email on the basis of the terms set out at:
> >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> >
> > _______________________________________________
> > tcmtf mailing list
> > tcmtf@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcmtf
>=20
>=20
> --
> "Esta vez no fallaremos, Doctor Infierno"
>=20
> Dr Diego R. Lopez
> Telefonica I+D
> http://people.tid.es/diego.lopez/
>=20
> e-mail: diego@tid.es
> Tel:    +34 913 129 041
> Mobile: +34 682 051 091
> -----------------------------------------
>=20
>=20
> ________________________________
>=20
> Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar
> nuestra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en =
el enlace
> situado m=E1s abajo.
> This message is intended exclusively for its addressee. We only send =
and
> receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From navajas@unizar.es  Wed Jun 19 01:15:23 2013
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E78B121F9F88 for <tcmtf@ietfa.amsl.com>; Wed, 19 Jun 2013 01:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dWdJAZCNfCOg for <tcmtf@ietfa.amsl.com>; Wed, 19 Jun 2013 01:15:16 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id BD10B21F9F7B for <tcmtf@ietf.org>; Wed, 19 Jun 2013 01:15:12 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5J8F8gM014880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Wed, 19 Jun 2013 10:15:09 +0200
Message-ID: <51C16886.6010108@unizar.es>
Date: Wed, 19 Jun 2013 10:15:02 +0200
From: =?UTF-8?B?SnVsacOhbiBGZXJuw6FuZGV6LU5hdmFqYXM=?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <004101ce6c13$9438c550$bcaa4ff0$@unizar.es>
In-Reply-To: <004101ce6c13$9438c550$bcaa4ff0$@unizar.es>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Glossary of TCMTF terms
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 08:15:24 -0000

Excellent work, Mirko and Jose
A suggestion, in the policy manager definition is used the term TCMTF 
multiplexers and demultiplexers, perhaps would be better to use 
TCMTF-optimizer term.
Thanks
JuliÃ¡n

El 18/06/2013 13:04, Jose Saldana escribiÃ³:
> Hi,
>
> Mirko and I included an "index term" at the beginning of the TCMTF -
> recommendations draft. Perhaps we could consider the possibility of also
> including one TCMTF - reference model draft.
>
> Here go some definition proposals, which can of course be improved:
>
> TCM-optimizer / TCMTF-optimizer
>
>     The host where TCM optimization (also TCMTF optimization) is deployed.
> It corresponds to both  the
>     ingress and the egress of the tunnel where native packets are included.
>
>     If the optimizer  compresses headers, multiplexes packets and creates the
> tunnel, it behaves as a "TCM-ingress optimizer".
>    
>     If it decompresses headers, demultiplexes packets and extracts packets
> from the tunnel, it behaves as a "TCM-egress optimizer".
>
> policy manager
>
>     A network entity which makes the decisions about TCMTF parameters:
>     multiplexing period; flows to be multiplexed together, depending on
>     their IP addresses, ports, etc.  It is connected with a number of
>     TCMTF multiplexers and demultiplexers, and orchestrates the
>     optimization that takes place between them.
>
> native packet
>
>     A packet sent by an application, belonging to a flow that can be
>     optimized by means of TCMTF.
>
> native flow
>
>     A flow of native packets.
>
> TCM packet / optimized packet / TCM-optimized packet
>
>     A packet including a number of multiplexed and header-compressed
>     native ones, and also a tunneling header.
>
> TCM flow / optimized flow / TCM-optimized flow
>
>     A flow of TCM packets.
>
>
> Best regards,
>
> Jose
>
>> -----Mensaje original-----
>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
>> Diego R. Lopez
>> Enviado el: lunes, 17 de junio de 2013 15:40
>> Para: <jsaldana@unizar.es>
>> CC: <tcmtf@ietf.org>; <tsv-area@ietf.org>; FERNANDO PASCUAL BLANCO
>> Asunto: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
>>
>> Hi Jose,
>>
>> I like your latter proposal. TCM-* should be enough: TCMTF technology is
>> provided (and leveraged) by TCM-* elements.
>>
>> Only a comment on your first statement: we *can* invent new English verbs.
>> English does not have stupid institutions like our Academy, but this is a
>> completely different discussion...
>>
>> Be goode,
>>
>> On 17 Jun 2013, at 09:31 , Jose Saldana wrote:
>>
>>> Hi, Fernando.
>>>
>>> I agree with you. We are talking about standards so precision is
> important.
>>> I don't think we should use the "verb" "to TCMTF" nor "TCMTFing" nor
>>> "TCMTFed". We cannot invent new English verbs.
>>>
>>> What about "optimization"?. This concept summarizes the three layers.
>>> We can use it this way:
>>>
>>> - A TCMTF optimizer
>>>
>>> - A packet optimized by means of TCMTF
>>> - A flow optimized by means of TCMTF
>>> - An optimized packet
>>> - An optimized flow
>>> - A TCMTF-optimized packet
>>> - A TCMTF-optimized flow
>>> - A TCMTF packet
>>> - A TCMTF flow
>>>
>>> - the TCMTF optimization can be applied to that flow
>>> - the impact of TCMTF optimization on protocol dynamics
>>>
>>> I have another question here: could we use only TCM instead of TCMTF?
>>> Remember that TF means "traffic flows", so a TCMTF flow would be a
>>> "tunneling compressed multiplexed traffic flows flow". Perhaps a TCM
>>> flow would be enough in those cases. TCM does not have another related
>>> meaning and it is shorter than TCMTF
>>> (http://www.acronymfinder.com/TCM.html)
>>>
>>> - A TCM optimizer
>>> - A TCM-optimized flow
>>> - A TCM flow
>>>
>>> What do you think?
>>>
>>> Jose
>>>
>>>> -----Mensaje original-----
>>>> De: FERNANDO PASCUAL BLANCO [mailto:fpb@tid.es] Enviado el:
>> viernes,
>>>> 14 de junio de 2013 21:29
>>>> Para: jsaldana@unizar.es; tcmtf@ietf.org; tsv-area@ietf.org
>>>> Asunto: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
>>>>
>>>> Hi Jose,
>>>>
>>>>         I like all your changes, they all enrich the WG description.
>>>>
>>>>         Nevertheless I wanted to mention, after read carefully the
>>>> text,
>>> that
>>>> when we talk about layers, we always use the three terms (tunneling,
>>>> multiplexing and compression) and I think it is ok.
>>>>         When we talk about the elements in charge of apply the TCMTF
>>> protocol
>>>> we have call them multiplexers and demultiplexers, and that may be a
>>> little
>>>> confusing, given that they use the name of the middle protocol layer,
>>>> but
>>> I
>>>> understand that we have not found a better name (I include myself
>>>> here) and maybe multiplexing is the most representative layer, so it
>>>> could be
>>> ok.
>>>>         But in paragraph 8 we talk about multiplexing flows and the
>>>> impact
>>> of
>>>> multiplexing in protocol dynamics, and I think that may be confusing,
>>> given
>>>> that using "multiplexing" we are referring to apply the whole TCMTF
>>> protocol
>>>> or not and not only to apply the multiplexing layer or not. IÂ´m just
>>> saying that
>>>> this term here may be confusing and someone could get a bad
>>>> interpretation from the text. I see three option: a) we pre-define
>>>> the term
>>> "multiplexing"
>>>> as the application of the TCMTF protocol itself, b) we invent the
>>>> verb "to TCMTF" and use the participle "TCMTFed" when something is
>>>> passed trough our protocol stack or c) (and maybe the most convenient
>>>> we use the long form "the TCMTF protocol can be applied to that flow"
>>>> or "the impact of TCMTF protocol on protocol dynamics". My suggestion
> is
>> to use option c).
>>>>         What do you think?
>>>>
>>>>         Thank you for your great effort!
>>>>
>>>> Best,
>>>>
>>>> Fernando Pascual Blanco
>>>> TelefÃ³nica Global Resources
>>>> Network Automation and Dynamization
>>>> TECHNOLOGY PEOPLE GROUP
>>>> F +34913128779
>>>> M +34682005168
>>>> fpb@tid.es
>>>>
>>>>
>>>>
>>>>
>>>> On 13/06/13 10:43, "Jose Saldana" <jsaldana@unizar.es> wrote:
>>>>
>>>>> These are the main changes included in the draft charter v6 (ordered
>>>>> by
>>>>> paragraphs):
>>>>>
>>>>> 1. I have moved the sentence about the overhead to the end of the
>>>>> paragraph, in order to say that Â³For both the delay-sensitive and
>>>>> delay-insensitive applications, their small data payloads incur
>>>>> significant overheadÂ²
>>>>>
>>>>> 2. I have put the scenarios in bullets, and I have improved some of
>>>>> the descriptions a bit.
>>>>>
>>>>> 6. I have changed the name of the document: instead of Â³document AÂ²
>>>>> it is now Â³TCMTF Â­ reference modelÂ².
>>>>>
>>>>> 7. Now we are talking about another document Â³TCMTF Â­ negotiation
>>>>> protocolÂ².
>>>>> In addition, I have put the two signaling functionalities in bullets.
>>>>>
>>>>> 7. As discussed in the list, we would talk about Â³setup/release a
>>>>> TCMTF sessionÂ².
>>>>>
>>>>> 8. I have changed the name of the document, from Â³document BÂ² to
>>>> Â³TCMTF
>>>>> recommendationsÂ²
>>>>>
>>>>> 8. According to GorryÂ¹s suggestion, I have added this sentence: Â³The
>>>>> eventual impact of multiplexing on protocol dynamics (e.g. when
>>>>> multiplexing TCP flows) will also have to be addressed.Â²
>>>>>
>>>>> Jose
>>>>>
>>>>>
>>>>>> -----Mensaje original-----
>>>>>> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En
>>>>>> nombre de Jose Saldana Enviado el: jueves, 13 de junio de 2013
>>>>>> 10:38
>>>>>> Para: tcmtf@ietf.org; tsv-area@ietf.org
>>>>>> Asunto: [tcmtf] Improved version of the tmctf Draft charter (v6)
>>>>>>
>>>>>> This is the new proposal, adapted to the new distribution of the
>>>>> documents.
>>>>>> I explain the changes in another e-mail.
>>>>>> It is also here, in a formatted version:
>>>>>> http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.p
>>>>>> df
>>>>>>
>>>>>>
>>>>>> TCMTF charter draft v6
>>>>>>
>>>>>> Description of Working Group
>>>>>>
>>>>>> 1. In the last years we are witnessing the raise of new real-time
>>>>>> services
>>>>> that
>>>>>> use the Internet for the delivery of interactive multimedia
>>>>>> applications: VoIP, videoconferencing, telemedicine, video
>>>>>> vigilance,
>>>>> online
>>>>>> gaming, etc. Due to the need of interactivity, many of these
>>>>>> services use  small packets (some tens of bytes), since they have
>>>>>> to send frequent  updates between the extremes of the
>>>>>> communication. In addition, some  other services also send small
>>>>>> packets, but they are not delay-sensitive
>>>>> (e.g.,
>>>>>> instant messaging, m2m packets sending collected data in sensor
>>>>>> networks using wireless or satellite scenarios). For both the
>>>>>> delay-sensitive and
>>>>> delay-
>>>>>> insensitive applications, their small data payloads incur
>>>>>> significant
>>>>> overhead,
>>>>>> and it becomes even higher when IPv6 is used, since the basic IPv6
>>>>>> header
>>>>> is
>>>>>> twice the size of the IPv4 one.
>>>>>>
>>>>>> 2. The efficiency cannot be increased by the inclusion of a higher
>>>>>> number
>>>>> of
>>>>>> samples in a single packet, since this would harm the delay
>>>>>> requirements
>>>>> of
>>>>>> the service. But there exist some scenarios in which a number of
>>>>>> flows
>>>>> share
>>>>>> the same path. In this case, packets belonging to different flows
>>>>>> can be grouped together, adding a small multiplexing delay as a
>>>>>> counterpart of bandwidth saving. This delay will have to be
>>>>>> maintained under some threshold in order to grant the delay
>>>>>> requirements. Some examples of the scenarios where grouping
>> packets
>>>>>> is
>>>> possible are:
>>>>>> - aggregation networks of a network operator;
>>>>>> - an end-to-end tunnel between appliances located in two different
>>>>>> offices  of the same company;
>>>>>> - the access connection of an Internet CafÃ© including a high number
>>>>>> of  VoIP/gaming flows;
>>>>>> - an agreement between two network operators could allow them to
>>>>>> compress a number of flows they are exchanging between a pair of
>>>>>> Internet  Routers;
>>>>>> - a satellite connection used for collecting the data of a high
>>>>>> number of  sensors.
>>>>>>
>>>>>> 3. VoIP using RTP is a clear example of a real-time service using
>>>>>> small
>>>>> packets
>>>>>> with high overhead. In order to improve efficiency, RFC4170 (TCRTP)
>>>>> defined
>>>>>> a method for grouping packets when a number of flows share a path,
>>>>>> considering three different layers: header compression by means of
>>>>>> ECRTP;  multiplexing by means of PPPMux; tunneling by means of
>> L2TPv3.
>>>>>> 4. However, in the last years, emerging real-time services which do
>>>>>> not
>>>>> use
>>>>>> UDP/RTP have become popular: some of them use UDP or even TCP. In
>>>>>> addition, new header compression methods have been defined
>> (ROHC).
>>>> So
>>>>>> there is a need of widening the scope of RFC4170 in order to
>>>>>> consider not  only UDP/RTP but also other protocols. The same
>>>>>> structure of three layers  will be considered:
>>>>>>
>>>>>> - Header compression: Taking into account that real-time
>>>>>> applications use  different headers (RTP/UDP, UDP or even TCP),
>>>>>> different protocols can be
>>>>>> used: no compression, ECRTP, IPHC and ROHC.
>>>>>> - Multiplexing: If a number of flows share a path between an origin
>>>>>> and a  destination, a multiplexer can build a bigger packet in
>>>>>> which a number of  payloads share a common header. A demultiplexer
>>>>>> is then necessary at the  end of the common path, so as to rebuild
>>>>>> the packets as they were
>>>>> originally
>>>>>> sent. PPPMux will be the main option. Other ones are not discarded.
>>>>>> - Tunneling will be used to send the multiplexed packets end-to-end.
>>>>>> The options in this layer are L2TP, GRE and MPLS.
>>>>>>
>>>>>> 5. So the first objective of this group is to specify the protocol
>>>>>> stack
>>>>> for
>>>>>> tunneling, compressing and multiplexing traffic flows (TCMTF).
>>>>>> Since standard protocols are being used at each layer, the
>>>>>> signaling methods of  those protocols will be used. Interactions
>>>>>> with the Working Groups and
>>>>> Areas
>>>>>> in which these protocols are developed can be expected. However,
>>>>>> the development of new compressing, multiplexing or tunneling
>>>>>> protocols is not  an objective of this Working Group. In addition,
>>>>>> since the current RFC
>>>>> 4170
>>>>>> would be considered as one of the options, this RFC could be
>> obsoleted.
>>>>>> 6. As a first objective, a document (TCMTF - reference model) will
>>>>>> define
>>>>> the
>>>>>> different options which can be used at each layer. Specific
>>>>>> problems
>>>>> caused
>>>>>> by the interaction between layers will have to be issued, and
>>>>>> suitable extensions may have to be added to the involved protocols.
>>>>>>
>>>>>> 7. If a pair multiplexer/de-multiplexer want to establish a TCMTF
>>>>>> session,  they have first to use a mechanism to negotiate which
>>>>>> concrete option
>>>>> would
>>>>>> they use in each layer: header compression, multiplexing and
>> tunneling.
>>>>> This
>>>>>> will depend on the protocols that each extreme implements at each
>>>>>> level, and in the scenario. So another document (TCMTF -
>>>>>> negotiation
>>>>>> protocol)
>>>>> will
>>>>>> include:
>>>>>>
>>>>>> - a mechanism to setup/release a TCMTF session between a
>>>>>> multiplexer and a de-multiplexer, also including:
>>>>>> - a negotiation mechanism to decide the options to use at each
>>>>>> layer
>>>>> (header
>>>>>> compression, multiplexing and tunneling) between multiplexer and
>>>>>> de- multiplexer,
>>>>>>
>>>>>> 8. As a counterpart of the bandwidth saving, TCMTF may add some
>>>>>> delay and  jitter. This is not a problem for the services which are
>>>>>> not sensitive to
>>>>> delay.
>>>>>> However, regarding delay-sensitive services, the Working Group will
>>>>>> also  develop a document (TCMTF - recommendations) with useful
>>>>>> recommendations in order to decide which packet flows can or can
>>>>>> not be  multiplexed and how. The document will present a list of
>>>>>> available traffic  classification methods which can be used for
>>>>>> identification of the service
>>>>> or
>>>>>> application to which a particular flow belongs, as well as
>>>>>> recommendations
>>>>> of
>>>>>> the maximum delay and jitter to be added depending of the
>>>>>> identified service or application. The eventual impact of
>>>>>> multiplexing on protocol dynamics (e.g., when multiplexing TCP
>>>>>> flows) will also have to be
>>>>> addressed.
>>>>>> 9. If other interesting features are identified, the group would
>>>>> re-charter and
>>>>>> include them, e.g., a mechanism for a multiplexer to discover a de-
>>>>>> multiplexer, and vice versa; a mechanism to select an optimal
>>>>>> multiplexer  and a de-multiplexer when there are more than one
>>>>>> muxer/de-muxer for a  flow; dynamically applying TCMTF: a higher
>>>>>> entity in charge of deciding
>>>>> when
>>>>>> and where, applying or not TCMTF, and what kind of TCMTF, and what
>>>>>> multiplexing period. Additional methods for estimating delay would
>>>>>> also be  required.
>>>>>>
>>>>>> 10. In addition, specific uses of TCMTF, such as in wireless and
>>>>>> satellite  scenarios, could be considered, and it will be studied
>>>>>> whether
>>>>> modifications
>>>>>> or extensions are required on the protocol.
>>>>>>
>>>>>> 11. Interactions with other Working Groups can be expected, since
>>>>>> TCMTF  uses already defined protocols for compression, multiplexing
>>>>>> and tunneling  (ROHC, PPPMux, MPLS, GRE, L2TP).
>>>>>>
>>>>>> Goals and Milestones
>>>>>>
>>>>>> Specification of TCMTF  reference model.
>>>>>>
>>>>>> Specification of TCMTF negotiation protocol.
>>>>>>
>>>>>> Specification of TCMTF recommendations of using existing traffic
>>>>>> classification methods, maximum delay and jitter to add, depending
>>>>>> on the  service.
>>>>>>
>>>>>>
>>>>>> Current version of Document (TCMTF - reference model):
>>>>>> https://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
>>>>>>
>>>>>> Current version of Document (TCMTF - recommendations):
>>>>>> http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
>>>>>>
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> Jose
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> tcmtf mailing list
>>>>>> tcmtf@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>>> _______________________________________________
>>>>> tcmtf mailing list
>>>>> tcmtf@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>>>
>>>> ________________________________
>>>>
>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede
>>>> consultar nuestra polÃ­tica de envÃ­o y recepciÃ³n de correo electrÃ³nico
>>>> en el enlace situado mÃ¡s abajo.
>>>> This message is intended exclusively for its addressee. We only send
>>>> and receive email on the basis of the terms set out at:
>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>>> _______________________________________________
>>> tcmtf mailing list
>>> tcmtf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcmtf
>>
>> --
>> "Esta vez no fallaremos, Doctor Infierno"
>>
>> Dr Diego R. Lopez
>> Telefonica I+D
>> http://people.tid.es/diego.lopez/
>>
>> e-mail: diego@tid.es
>> Tel:    +34 913 129 041
>> Mobile: +34 682 051 091
>> -----------------------------------------
>>
>>
>> ________________________________
>>
>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>> nuestra polÃ­tica de envÃ­o y recepciÃ³n de correo electrÃ³nico en el enlace
>> situado mÃ¡s abajo.
>> This message is intended exclusively for its addressee. We only send and
>> receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>> _______________________________________________
>> tcmtf mailing list
>> tcmtf@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcmtf
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>
>


From jsaldana@unizar.es  Wed Jun 19 07:28:57 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 830BD21F9C32 for <tcmtf@ietfa.amsl.com>; Wed, 19 Jun 2013 07:28:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.478
X-Spam-Level: 
X-Spam-Status: No, score=-6.478 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xW2MZcAYphyq for <tcmtf@ietfa.amsl.com>; Wed, 19 Jun 2013 07:28:52 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 388C721F9C35 for <tcmtf@ietf.org>; Wed, 19 Jun 2013 07:28:51 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5JESgtN013154; Wed, 19 Jun 2013 16:28:42 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Wed, 19 Jun 2013 16:28:48 +0200
Organization: Universidad de Zaragoza
Message-ID: <002801ce6cf9$500feac0$f02fc040$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0029_01CE6D0A.13995700"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5s978oBaw7NG94S9C/A9wEOusDMQ==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: Tomaso.deCola@dlr.de, 'Spencer Dawkins' <spencerdawkins.ietf@gmail.com>, Matteo.Berioli@dlr.de, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: [tcmtf] Other potential specific uses of TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 14:28:57 -0000

This is a multipart message in MIME format.

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

Hi all,

 

As you may know, if we get the BOF approved, we will have to discuss the WG
charter there. Currently these drafts are included in the WG charter (
<http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf>
http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf):

 

1- Draft "TCM-TF reference model": the different options which can be used
at each layer. 

2- Draft "TCM-TF negotiation protocol": setup/release a TCMTF session
including a negotiation mechanism to decide the options to use at each
layer.

3- Draft "TCM-TF recommendations": recommendations in order to decide which
packet flows can or can not be multiplexed and how.

 

For the charter discussion, it would be useful to have in mind (and perhaps
to mention) other potential specific uses of TCM-TF *that might contribute
unique requirements*.

 

- First of all, I think on the idea proposed by Tomaso and Matteo (DLR), as
said in n.10 of the current draft charter: "specific uses of TCMTF, such as
in wireless and satellite scenarios, could be considered, and it will be
studied whether modifications or extensions are required on the protocol".
It presents different and specific requirements.

 

- Do you think that instant messaging presents unique requirements with
respect to the normal use of TCM-TF? I don't think so, but perhaps someone
won't agree on this. In fact, instant messaging is already included in the
"TCM-TF recommendations" draft.

 

 

Any other ideas?

 

Jose

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=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>As you may know, if we get the BOF approved, we will have =
to discuss the WG charter there. Currently these drafts are included in =
the WG charter (</span><a =
href=3D"http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft=
.pdf"><span =
lang=3DEN-US>http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_=
draft.pdf</span></a><span 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=3DMsoPlainText><span lang=3DEN-US>1- Draft &#8220;TCM-TF reference =
model&#8221;: the different options which can be used at each layer. =
<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US>2- =
Draft &#8220;TCM-TF negotiation protocol&#8221;: setup/release a TCMTF =
session including a negotiation mechanism to decide the options to use =
at each layer.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>3- Draft &#8220;TCM-TF recommendations&#8221;: =
recommendations in order to decide which packet flows can or can not be =
multiplexed and how.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US>For the charter discussion, it would be useful to have in =
mind (and perhaps to mention) other potential specific uses of TCM-TF =
*that might contribute unique requirements*.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>- First of all, I think on the =
idea proposed by Tomaso and Matteo (DLR), as said in n.10 of the current =
draft charter: &#8220;specific uses of TCMTF, such as in wireless and =
satellite scenarios, could be considered, and it will be studied whether =
modifications or extensions are required on the protocol&#8221;. It =
presents different and specific requirements.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>- Do you think that instant =
messaging presents unique requirements with respect to the normal use of =
TCM-TF? I don&#8217;t think so, but perhaps someone won&#8217;t agree on =
this. In fact, instant messaging is already included in the =
&#8220;TCM-TF recommendations&#8221; draft.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US>Any other =
ideas?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'mso-fareast-language:ES'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_0029_01CE6D0A.13995700--


From diego@tid.es  Wed Jun 19 07:41:35 2013
Return-Path: <diego@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCB3421F9B87 for <tcmtf@ietfa.amsl.com>; Wed, 19 Jun 2013 07:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BtCsaDPx71SZ for <tcmtf@ietfa.amsl.com>; Wed, 19 Jun 2013 07:41:32 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id AF11121F8F29 for <tcmtf@ietf.org>; Wed, 19 Jun 2013 07:41:30 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MON006I8A541H@tid.hi.inet> for tcmtf@ietf.org; Wed, 19 Jun 2013 16:41:28 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 4C.42.05654.813C1C15; Wed, 19 Jun 2013 16:41:28 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MON006I0A541H@tid.hi.inet> for tcmtf@ietf.org; Wed, 19 Jun 2013 16:41:28 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS6-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Wed, 19 Jun 2013 16:41:28 +0200
Date: Wed, 19 Jun 2013 14:40:31 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <002801ce6cf9$500feac0$f02fc040$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "<jsaldana@unizar.es>" <jsaldana@unizar.es>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A049CCE874D@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_NVcJOSiRtk5ykHv1NC0RqQ)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Other potential specific uses of TCM-TF
Thread-index: Ac5s978oBaw7NG94S9C/A9wEOusDMf//5SMA
X-AuditID: 0a5f4e69-b7f4b6d000001616-dd-51c1c318dc4b
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsXCFe9nqCtx+GCgwY+/Rha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxruLexgLPkZX9Cy8y9rA+C6gi5GTQ0LARGJyz2NWCFtM4sK9 9WxdjFwcQgLbGSVaVz9mhnB+Mkr8vH+WHcKZxigx78dppi5GDg4WAVWJVz3aIN1sQOaj5t/s ILawgI3EoWtHWEBsTgELiSk9/WwQGxQk/px7DBYXEdCXuPH4N9hMZoHvjBJ/Ln1gBknwCnhL PDjwnxXCFpT4MfkeWAOzQK7E2q0/WCFscYnm1ptgcUYBWYl38+ezQgy1lWhd9x5qgZHEnKf7 oF4TkFiy5zwzhC0q8fLxP7C4kIC5xNS9exgnMIrNQrJuFpJ1s5Csg7ANJN6fm88MYWtLLFv4 GsrWl9j45SwjhG0m0ftzLyOymgWMHKsYxYqTijLTM0pyEzNz0g2M9DIy9TLzUks2MUIiMnMH 4/KdKocYBTgYlXh4G1YeCBRiTSwrrsw9xCjBwawkwtu162CgEG9KYmVValF+fFFpTmrxIUYm Dk6pBsaZy45se5SSIJe6zfDnlIPiVm56iy0Onznicc74p/KRwy6256yWH/13YqlGpL67O5Pf 9pOTvUtesf7f+/Xq5gCW+Hq+Hm3h0k2rr9bxFXDmGG04Pt18Icv8AsNitZZ5ZjsWrDjnpVh7 IHD1Z/H3PK3lqzY9ipKz+xgwgcWN+cnM8AM7LolO9XikxFKckWioxVxUnAgAwJ+r7aYCAAA=
References: <002801ce6cf9$500feac0$f02fc040$@unizar.es>
Cc: "<tcmtf@ietf.org>" <tcmtf@ietf.org>, "<Matteo.Berioli@dlr.de>" <Matteo.Berioli@dlr.de>, "<Tomaso.deCola@dlr.de>" <Tomaso.deCola@dlr.de>, Spencer Dawkins <spencerdawkins.ietf@gmail.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] Other potential specific uses of TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 14:41:36 -0000

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

Hi,

I think it could be better to mention the study of specific requirements on=
 TCMTF by particular use cases, and consider the inclusion of such document=
s in a future rechartering, rather than committing to have one document (or=
 even several of them) in an issue that we'll have to clarify once the basi=
c framework is in place.

Be goode,

On 19 Jun 2013, at 16:28 , Jose Saldana wrote:

Hi all,

As you may know, if we get the BOF approved, we will have to discuss the WG=
 charter there. Currently these drafts are included in the WG charter (http=
://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf):

1- Draft =93TCM-TF reference model=94: the different options which can be u=
sed at each layer.
2- Draft =93TCM-TF negotiation protocol=94: setup/release a TCMTF session i=
ncluding a negotiation mechanism to decide the options to use at each layer=
.
3- Draft =93TCM-TF recommendations=94: recommendations in order to decide w=
hich packet flows can or can not be multiplexed and how.

For the charter discussion, it would be useful to have in mind (and perhaps=
 to mention) other potential specific uses of TCM-TF *that might contribute=
 unique requirements*.

- First of all, I think on the idea proposed by Tomaso and Matteo (DLR), as=
 said in n.10 of the current draft charter: =93specific uses of TCMTF, such=
 as in wireless and satellite scenarios, could be considered, and it will b=
e studied whether modifications or extensions are required on the protocol=
=94. It presents different and specific requirements.

- Do you think that instant messaging presents unique requirements with res=
pect to the normal use of TCM-TF? I don=92t think so, but perhaps someone w=
on=92t agree on this. In fact, instant messaging is already included in the=
 =93TCM-TF recommendations=94 draft.


Any other ideas?

Jose

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


--
"Esta vez no fallaremos, Doctor Infierno"

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

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


________________________________

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

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<base href=3D"">
</head>
<body style=3D"word-wrap:break-word">
Hi,
<div><br>
</div>
<div>I think it could be better to mention the study of specific requiremen=
ts on TCMTF by particular use cases, and consider the inclusion of such doc=
uments in a future rechartering, rather than committing to have one documen=
t (or even several of them) in an
 issue that we'll have to clarify once the basic framework is in place.</di=
v>
<div><br>
</div>
<div>Be goode,</div>
<div><br>
<div>
<div>On 19 Jun 2013, at 16:28 , Jose Saldana wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse:separate; font-family:Helvetica; font-style:normal; font-variant:n=
ormal; font-weight:normal; letter-spacing:normal; line-height:normal; orpha=
ns:2; text-indent:0px; text-transform:none; white-space:normal; widows:2; w=
ord-spacing:0px; font-size:medium">
<div lang=3D"ES">
<div class=3D"WordSection1" style=3D"">
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">Hi all,</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">As you may know, if we get the BOF approved, we will h=
ave to discuss the WG charter there. Currently these drafts are included in=
 the WG charter (</span><a href=3D"http://diec.unizar.es/~jsaldana/personal=
/ietf/tcmtf_charter_draft.pdf" style=3D"color:blue; text-decoration:underli=
ne"><span lang=3D"EN-US">http://diec.unizar.es/~jsaldana/personal/ietf/tcmt=
f_charter_draft.pdf</span></a><span lang=3D"EN-US">):</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">1- Draft =93TCM-TF reference model=94: the different o=
ptions which can be used at each layer.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">2- Draft =93TCM-TF negotiation protocol=94: setup/rele=
ase a TCMTF session including a negotiation mechanism to decide the options=
 to use at each layer.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">3- Draft =93TCM-TF recommendations=94: recommendations=
 in order to decide which packet flows can or can not be multiplexed and ho=
w.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">For the charter discussion, it would be useful to have=
 in mind (and perhaps to mention) other potential specific uses of TCM-TF *=
that might contribute unique requirements*.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">- First of all, I think on the idea proposed by Tomaso=
 and Matteo (DLR), as said in n.10 of the current draft charter: =93specifi=
c uses of TCMTF, such as in wireless and satellite scenarios, could be cons=
idered, and it will be studied whether
 modifications or extensions are required on the protocol=94. It presents d=
ifferent and specific requirements.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">- Do you think that instant messaging presents unique =
requirements with respect to the normal use of TCM-TF? I don=92t think so, =
but perhaps someone won=92t agree on this. In fact, instant messaging is al=
ready included in the =93TCM-TF recommendations=94
 draft.</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">Any other ideas?</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">Jose</span></div>
<div style=3D"margin-top:0cm; margin-right:0cm; margin-left:0cm; margin-bot=
tom:0.0001pt; font-size:11pt; font-family:Calibri,sans-serif">
<span lang=3D"EN-US">&nbsp;</span></div>
</div>
_______________________________________________<br>
tcmtf mailing list<br>
<a href=3D"mailto:tcmtf@ietf.org" style=3D"color:blue; text-decoration:unde=
rline">tcmtf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcmtf" style=3D"color:blue=
; text-decoration:underline">https://www.ietf.org/mailman/listinfo/tcmtf</a=
><br>
</div>
</span></blockquote>
</div>
<br>
<div><span class=3D"Apple-style-span" style=3D"border-collapse:separate; co=
lor:rgb(0,0,0); font-family:Helvetica; font-style:normal; font-variant:norm=
al; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:=
2; text-indent:0px; text-transform:none; white-space:normal; widows:2; word=
-spacing:0px; font-size:medium"><span class=3D"Apple-style-span" style=3D"b=
order-collapse:separate; color:rgb(0,0,0); font-family:Helvetica; font-styl=
e:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; l=
ine-height:normal; orphans:2; text-indent:0px; text-transform:none; white-s=
pace:normal; widows:2; word-spacing:0px; font-size:medium">
<div style=3D"word-wrap:break-word"><span class=3D"Apple-style-span" style=
=3D"border-collapse:separate; color:rgb(0,0,0); font-family:Helvetica; font=
-style:normal; font-variant:normal; font-weight:normal; letter-spacing:norm=
al; line-height:normal; orphans:2; text-indent:0px; text-transform:none; wh=
ite-space:normal; widows:2; word-spacing:0px; font-size:medium">
<div style=3D"word-wrap:break-word"><br>
--<br>
&quot;Esta vez no fallaremos, Doctor Infierno&quot;<br>
<br>
Dr Diego R. Lopez<br>
Telefonica I&#43;D</div>
<div style=3D"word-wrap:break-word"><a href=3D"http://people.tid.es/diego.l=
opez/">http://people.tid.es/diego.lopez/</a><br>
<br>
e-mail: diego@tid.es<br>
Tel: &nbsp; &nbsp;&#43;34 913 129 041<br>
Mobile: &#43;34 682 051 091<br>
-----------------------------------------</div>
</span></div>
</span></span></div>
<br>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_NVcJOSiRtk5ykHv1NC0RqQ)--

From jsaldana@unizar.es  Wed Jun 19 07:54:45 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BCDA21F9BC9 for <tcmtf@ietfa.amsl.com>; Wed, 19 Jun 2013 07:54:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.486
X-Spam-Level: 
X-Spam-Status: No, score=-6.486 tagged_above=-999 required=5 tests=[AWL=0.112,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xKDu+UYPniCW for <tcmtf@ietfa.amsl.com>; Wed, 19 Jun 2013 07:54:41 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6756421F9B80 for <tcmtf@ietf.org>; Wed, 19 Jun 2013 07:54:40 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5JEsWMb024460; Wed, 19 Jun 2013 16:54:33 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Diego R. Lopez'" <diego@tid.es>
References: <002801ce6cf9$500feac0$f02fc040$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CCE874D@EX10-MB2-MAD.hi.inet>
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A049CCE874D@EX10-MB2-MAD.hi.inet>
Date: Wed, 19 Jun 2013 16:54:37 +0200
Organization: Universidad de Zaragoza
Message-ID: <005501ce6cfc$eb6e5d00$c24b1700$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0056_01CE6D0D.AEF86580"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGRblH9Zk4V+XD8Q7oln4gH4yvd3wHAKZFamakZc3A=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, Matteo.Berioli@dlr.de, Tomaso.deCola@dlr.de, 'Spencer Dawkins' <spencerdawkins.ietf@gmail.com>, 'Martin Stiemerling' <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] Other potential specific uses of TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 14:54:45 -0000

This is a multipart message in MIME format.

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

Yes, Diego. I think the idea is having these three =93basic=94 drafts, =
and also
to have in mind some potential ones which could be addressed by
re-chartering. We have to first build the basic things, and then go to
specific uses. In fact, the current draft charter (n.9) already includes
some of that additional ideas:

=20

9. If other interesting features are identified, the group would =
re-charter
and include them, e.g., a=20

mechanism for a multiplexer to discover a de-multiplexer, and vice =
versa; a
mechanism to select an=20

optimal multiplexer and a de-multiplexer when there are more than one
muxer/de-muxer for a flow;=20

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

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

would also be required.

=20

I think that in the BOF we should also mention (only mention) the =
potential
work to be addressed if the WG is created, and the interest on it.

=20

However, there is something dangerous: if we =93open=94 too many things, =
we may
widen the discussion too much, and the BOF may become unfocused.

=20

What do you think?

=20

Jose

=20

De: Diego R. Lopez [mailto:diego@tid.es]=20
Enviado el: mi=E9rcoles, 19 de junio de 2013 16:41
Para: <jsaldana@unizar.es>
CC: <tcmtf@ietf.org>; <Tomaso.deCola@dlr.de>; Spencer Dawkins;
<Matteo.Berioli@dlr.de>; Martin Stiemerling
Asunto: Re: [tcmtf] Other potential specific uses of TCM-TF

=20

Hi,=20

=20

I think it could be better to mention the study of specific requirements =
on
TCMTF by particular use cases, and consider the inclusion of such =
documents
in a future rechartering, rather than committing to have one document =
(or
even several of them) in an issue that we'll have to clarify once the =
basic
framework is in place.

=20

Be goode,

=20

On 19 Jun 2013, at 16:28 , Jose Saldana wrote:





Hi all,

=20

As you may know, if we get the BOF approved, we will have to discuss the =
WG
charter there. Currently these drafts are included in the WG charter (
<http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf>
http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft.pdf):

=20

1- Draft =93TCM-TF reference model=94: the different options which can =
be used
at each layer.

2- Draft =93TCM-TF negotiation protocol=94: setup/release a TCMTF =
session
including a negotiation mechanism to decide the options to use at each
layer.

3- Draft =93TCM-TF recommendations=94: recommendations in order to =
decide which
packet flows can or can not be multiplexed and how.

=20

For the charter discussion, it would be useful to have in mind (and =
perhaps
to mention) other potential specific uses of TCM-TF *that might =
contribute
unique requirements*.

=20

- First of all, I think on the idea proposed by Tomaso and Matteo (DLR), =
as
said in n.10 of the current draft charter: =93specific uses of TCMTF, =
such as
in wireless and satellite scenarios, could be considered, and it will be
studied whether modifications or extensions are required on the =
protocol=94.
It presents different and specific requirements.

=20

- Do you think that instant messaging presents unique requirements with
respect to the normal use of TCM-TF? I don=92t think so, but perhaps =
someone
won=92t agree on this. In fact, instant messaging is already included in =
the
=93TCM-TF recommendations=94 draft.

=20

=20

Any other ideas?

=20

Jose

=20

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

=20


--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D

http://people.tid.es/diego.lopez/

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

=20

=20

  _____ =20


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


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

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><!--[if =
!mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Yes, Diego. I think the idea is having these three =
&#8220;basic&#8221; drafts, and also to have in mind some potential ones =
which could be addressed by re-chartering. We have to first build the =
basic things, and then go to specific uses. In fact, the current draft =
charter (n.9) already includes some of that additional =
ideas:<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>9. If other interesting features are identified, the group would =
re-charter and include them, e.g., a <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>mechanism for a multiplexer to discover a de-multiplexer, and vice =
versa; a mechanism to select an <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>optimal multiplexer and a de-multiplexer when there are more than one =
muxer/de-muxer for a flow; <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>dynamically applying TCMTF: a higher entity in charge of deciding =
when and where, applying or not <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>TCMTF, and what kind of TCMTF, and what multiplexing period. =
Additional methods for estimating delay <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>would also be required.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I think that in the BOF we should also mention (only mention) the =
potential work to be addressed if the WG is created, and the interest on =
it.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>However, there is something dangerous: if we &#8220;open&#8221; too =
many things, we may widen the discussion too much, and the BOF may =
become unfocused.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>What do you think?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jose<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Diego R. Lopez [mailto:diego@tid.es] <br><b>Enviado el:</b> mi=E9rcoles, =
19 de junio de 2013 16:41<br><b>Para:</b> =
&lt;jsaldana@unizar.es&gt;<br><b>CC:</b> &lt;tcmtf@ietf.org&gt;; =
&lt;Tomaso.deCola@dlr.de&gt;; Spencer Dawkins; =
&lt;Matteo.Berioli@dlr.de&gt;; Martin Stiemerling<br><b>Asunto:</b> Re: =
[tcmtf] Other potential specific uses of =
TCM-TF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Hi, =
<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
think it could be better to mention the study of specific requirements =
on TCMTF by particular use cases, and consider the inclusion of such =
documents in a future rechartering, rather than committing to have one =
document (or even several of them) in an issue that we'll have to =
clarify once the basic framework is in =
place.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Be goode,<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
19 Jun 2013, at 16:28 , Jose Saldana wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hi =
all,</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>As you may =
know, if we get the BOF approved, we will have to discuss the WG charter =
there. Currently these drafts are included in the WG charter =
(</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><a =
href=3D"http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_draft=
.pdf"><span =
lang=3DEN-US>http://diec.unizar.es/~jsaldana/personal/ietf/tcmtf_charter_=
draft.pdf</span></a></span><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>):</span><s=
pan =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>1- Draft =
&#8220;TCM-TF reference model&#8221;: the different options which can be =
used at each layer.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>2- Draft =
&#8220;TCM-TF negotiation protocol&#8221;: setup/release a TCMTF session =
including a negotiation mechanism to decide the options to use at each =
layer.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>3- Draft =
&#8220;TCM-TF recommendations&#8221;: recommendations in order to decide =
which packet flows can or can not be multiplexed and how.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>For the =
charter discussion, it would be useful to have in mind (and perhaps to =
mention) other potential specific uses of TCM-TF *that might contribute =
unique requirements*.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>- First of =
all, I think on the idea proposed by Tomaso and Matteo (DLR), as said in =
n.10 of the current draft charter: &#8220;specific uses of TCMTF, such =
as in wireless and satellite scenarios, could be considered, and it will =
be studied whether modifications or extensions are required on the =
protocol&#8221;. It presents different and specific =
requirements.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>- Do you =
think that instant messaging presents unique requirements with respect =
to the normal use of TCM-TF? I don&#8217;t think so, but perhaps someone =
won&#8217;t agree on this. In fact, instant messaging is already =
included in the &#8220;TCM-TF recommendations&#8221; draft.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Any other =
ideas?</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Jose</span>=
<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p></div></div><p class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>_________=
______________________________________<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">https://www.ietf.org=
/mailman/listinfo/tcmtf</a><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif";color:blac=
k'><br>--<br>&quot;Esta vez no fallaremos, Doctor =
Infierno&quot;<br><br>Dr Diego R. Lopez<br>Telefonica =
I+D<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif";color:blac=
k'><a =
href=3D"http://people.tid.es/diego.lopez/">http://people.tid.es/diego.lop=
ez/</a><br><br>e-mail: <a =
href=3D"mailto:diego@tid.es">diego@tid.es</a><br>Tel: &nbsp; &nbsp;+34 =
913 129 041<br>Mobile: +34 682 051 =
091<br>-----------------------------------------<o:p></o:p></span></p></d=
iv></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><hr size=3D2 width=3D"100%" =
align=3Dcenter></div><p class=3DMsoNormal><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br=
>Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico en el enlace situado m=E1s abajo.<br>This message is =
intended exclusively for its addressee. We only send and receive email =
on the basis of the terms set out at:<br><a =
href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/E=
S/PAGINAS/disclaimer.aspx</a></span><o:p></o:p></p></div></div></body></h=
tml>
------=_NextPart_000_0056_01CE6D0D.AEF86580--


From jsaldana@unizar.es  Thu Jun 20 00:23:28 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 154C621E80DF for <tcmtf@ietfa.amsl.com>; Thu, 20 Jun 2013 00:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.493
X-Spam-Level: 
X-Spam-Status: No, score=-6.493 tagged_above=-999 required=5 tests=[AWL=0.105,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vvxRA+MfczwC for <tcmtf@ietfa.amsl.com>; Thu, 20 Jun 2013 00:23:22 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id B4B9B21E80CB for <tcmtf@ietf.org>; Thu, 20 Jun 2013 00:23:21 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5K7NIBd010586 for <tcmtf@ietf.org>; Thu, 20 Jun 2013 09:23:18 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Thu, 20 Jun 2013 09:23:20 +0200
Organization: Universidad de Zaragoza
Message-ID: <00e401ce6d87$0abe4fa0$203aeee0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E5_01CE6D97.CE471FA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5thYCCEbR1J90FTvOEaRghIoqCAg==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] What about TCM-Optimizer --- TCM-Rebuilder?
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 07:23:28 -0000

This is a multipart message in MIME format.

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

I was thinking on how should we call the pair of entities performing TCM
optimization. It has been set clear that if we call them mux/demux, it is
not exact, since we forget the tunnel and compressing layers.

 

Last Monday I proposed "TCM-ingress optimizer" and "TCM-egress optimizer".
However, I think these are too long names.

 

I received a suggestion about TCM-optimizer / TCM-deoptimizer. But, who
would buy a "deoptimizer"?

 

So I have a better proposal:

 

What about TCM optimizer <-----------------> TCM rebuilder?

 

The egress entity "rebuilds" the packets to their native form. It is its
main task: to deliver a packet exactly as it was at the ingress of the
tunnel.

 

"TCM reconstructor" could also be ok, but it is longer.

 

Do you like it?

 

Jose

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>I was thinking on how should we call the pair of entities =
performing TCM optimization. It has been set clear that if we call them =
mux/demux, it is not exact, since we forget the tunnel and compressing =
layers.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Last Monday I proposed &#8220;TCM-ingress optimizer&#8221; =
and &#8220;TCM-egress optimizer&#8221;. However, I think these are too =
long names.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>I received a suggestion about TCM-optimizer / =
TCM-deoptimizer. But, who would buy a =
&#8220;deoptimizer&#8221;?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>So I have a better =
proposal:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>What about TCM optimizer &lt;-----------------&gt; TCM =
rebuilder?<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 egress entity &#8220;rebuilds&#8221; the packets to =
their native form. It is its main task: to deliver a packet exactly as =
it was at the ingress of the tunnel.<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>&#8220;TCM reconstructor&#8221; =
could also be ok, but it is longer.<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>Do you like =
it?<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'mso-fareast-language:ES'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_00E5_01CE6D97.CE471FA0--


From navajas@unizar.es  Thu Jun 20 01:04:49 2013
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A4AA21E80B0 for <tcmtf@ietfa.amsl.com>; Thu, 20 Jun 2013 01:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ynskrbU6vS3 for <tcmtf@ietfa.amsl.com>; Thu, 20 Jun 2013 01:04:43 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id A6A4C11E810E for <tcmtf@ietf.org>; Thu, 20 Jun 2013 01:04:37 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5K84RUS026825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Thu, 20 Jun 2013 10:04:28 +0200
Message-ID: <51C2B780.5000302@unizar.es>
Date: Thu, 20 Jun 2013 10:04:16 +0200
From: =?ISO-8859-15?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <002801ce6cf9$500feac0$f02fc040$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CCE874D@EX10-MB2-MAD.hi.inet> <005501ce6cfc$eb6e5d00$c24b1700$@unizar.es>
In-Reply-To: <005501ce6cfc$eb6e5d00$c24b1700$@unizar.es>
Content-Type: multipart/alternative; boundary="------------000609050809060300010303"
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Other potential specific uses of TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 08:04:49 -0000

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

Hi all,
I like to add a potencial new idea which could be addressed by 
re-chartering. What about the security on the tunnel?. It is possible to 
add security to TCMTF because it is inherent in the tunnels. And not 
only consider encryption, but also the digital signature which 
represents much loss of efficiency in the case of small packages.
Someone have more knowledge about this issue?
Julián

El 19/06/2013 16:54, Jose Saldana escribió:
> which could be addressed by re-chartering


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-15"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi all,<br>
      I like to add a potencial new idea which could be addressed by
      re-chartering. What about the security on the tunnel?. It is
      possible to add security to TCMTF because it is inherent in the
      tunnels. And not only consider encryption, but also the digital
      signature which represents much loss of efficiency in the case of
      small packages.<br>
      Someone have more knowledge about this issue?<br>
      Julián<br>
      <br>
      El 19/06/2013 16:54, Jose Saldana escribió:<br>
    </div>
    <blockquote cite="mid:005501ce6cfc$eb6e5d00$c24b1700$@unizar.es"
      type="cite"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
        lang="EN-US">which could be addressed by re-chartering</span></blockquote>
    <br>
  </body>
</html>

--------------000609050809060300010303--

From Martin.Stiemerling@neclab.eu  Thu Jun 20 01:13:22 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB84111E810B for <tcmtf@ietfa.amsl.com>; Thu, 20 Jun 2013 01:13:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.42
X-Spam-Level: 
X-Spam-Status: No, score=-103.42 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id svp6RXJlWuk6 for <tcmtf@ietfa.amsl.com>; Thu, 20 Jun 2013 01:13:17 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 34CD521E80B0 for <tcmtf@ietf.org>; Thu, 20 Jun 2013 01:13:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 451521045CB for <tcmtf@ietf.org>; Thu, 20 Jun 2013 10:12:55 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sBl4ueUKFmJw for <tcmtf@ietf.org>; Thu, 20 Jun 2013 10:12:55 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 298991045CA for <tcmtf@ietf.org>; Thu, 20 Jun 2013 10:12:50 +0200 (CEST)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 20 Jun 2013 10:13:11 +0200
Message-ID: <51C2B996.2060904@neclab.eu>
Date: Thu, 20 Jun 2013 10:13:10 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: "tcmtf@ietf.org" <tcmtf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Subject: [tcmtf] Security Threat: Compression Ratio Info-leak Made Easy (CRIME)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 08:13:22 -0000

Hi all,

My fellow Security AD just pointed me to the following security threat 
that might also applicable in the case of tcmtf:
Compression Ratio Info-leak Made Easy (CRIME), see [1].

Just to let you know for your considerations.

   Martin

[1] http://en.wikipedia.org/wiki/CRIME_%28security_exploit%29


-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From fpb@tid.es  Thu Jun 20 01:20:54 2013
Return-Path: <fpb@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D408D21F9C68 for <tcmtf@ietfa.amsl.com>; Thu, 20 Jun 2013 01:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.479
X-Spam-Level: 
X-Spam-Status: No, score=-6.479 tagged_above=-999 required=5 tests=[AWL=0.119,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4VUNfiuZJYzP for <tcmtf@ietfa.amsl.com>; Thu, 20 Jun 2013 01:20:47 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 3DFF711E8111 for <tcmtf@ietf.org>; Thu, 20 Jun 2013 01:20:44 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MOO00397N6IBG@tid.hi.inet> for tcmtf@ietf.org; Thu, 20 Jun 2013 10:20:42 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 43.59.05654.A5BB2C15; Thu, 20 Jun 2013 10:20:42 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MOO00392N6IBG@tid.hi.inet> for tcmtf@ietf.org; Thu, 20 Jun 2013 10:20:42 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS6-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Thu, 20 Jun 2013 10:20:42 +0200
Date: Thu, 20 Jun 2013 08:19:44 +0000
From: FERNANDO PASCUAL BLANCO <fpb@tid.es>
In-reply-to: <00e401ce6d87$0abe4fa0$203aeee0$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <F5EDC35DF914C1428C28E149F10463A29C8AE04D@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_UvrwcR6Ytr5a/F7VMwU5zQ)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] What about TCM-Optimizer --- TCM-Rebuilder?
Thread-index: Ac5thYCCEbR1J90FTvOEaRghIoqCAgACYrsA
user-agent: Microsoft-MacOutlook/14.3.2.130206
X-AuditID: 0a5f4e69-b7f4b6d000001616-fa-51c2bb5a7e13
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmplkeLIzCtJLcpLzFFi42Lhivcz1I3afSjQ4NxEU4tdnzcwOjB6LFny kymAMYrLJiU1J7MstUjfLoEr4/3d5+wFk+wqvk+dydjAuMSsi5GTQ0LARGLH4RVsELaYxIV7 64FsLg4hge2MEq17jzNCOD8ZJXZP+sEE4UxjlPhxoZ0FpIVFQFXi3dl2sHY2AS2J03dXgcWF BRwk2u6tZgexOQUsJK61r2WHWKEg8efcY7AaEYEAid0tB8BsXgFviabzN5kgbEGJH5PvAcU5 OJgFciV6XxmDhJkFxCWaW2+ClTMKyEq8mz+fFWKMo8SNLQeYIGwjiUXPN4KtEhXQk7h5poUV Yq2AxJI955khbFGJl4//sU5gFJ2FZNsshG2zkGyDsA0k3p+bzwxha0ssW/gaytaX2PjlLCOE bSax68NqRmQ1Cxg5VjGKFScVZaZnlOQmZuakGxjpZWTqZeallmxihERd5g7G5TtVDjEKcDAq 8fBqXz4YKMSaWFZcmXuIUYKDWUmEN3XOoUAh3pTEyqrUovz4otKc1OJDjEwcnFINjCvq5j9Z 4Cdb/7bvOK/HK7ZzRRfnPwhn91X5/O/0/3/OHgyJbg9Uc7eaVFvyhGQe9WtjlevQ9AgU7uDZ KXXnwdWpVY9qVvkY7rtenqAQL5/ZkJrBZ+xTkN+lzl3zV+5Qy4mbd5ltNPkEd5Z93C66RPrZ S52QcndF3Uvx0lvsxdIFVf5ET65VYinOSDTUYi4qTgQAYhYCy5gCAAA=
Subject: Re: [tcmtf] What about TCM-Optimizer --- TCM-Rebuilder?
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 08:20:54 -0000

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

Hi Jose,

I=B4m not sure about that. Optimizer and rebuilder make me think in very di=
fferent things, and actually they should be very similar. I like "TCM-ingre=
ss optimizer" and "TCM-egress optimizer", couldn=B4t we use an acronym here=
?

"TCM-ingress optimizer": TCM-IO
"TCM-egress optimizer": TCM-EO

Regards,

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

From: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.es<m=
ailto:jsaldana@unizar.es>>
Organization: Universidad de Zaragoza
Reply-To: "jsaldana@unizar.es<mailto:jsaldana@unizar.es>" <jsaldana@unizar.=
es<mailto:jsaldana@unizar.es>>
Date: jueves, 20 de junio de 2013 09:23
To: "tcmtf@ietf.org<mailto:tcmtf@ietf.org>" <tcmtf@ietf.org<mailto:tcmtf@ie=
tf.org>>
Subject: [tcmtf] What about TCM-Optimizer --- TCM-Rebuilder?

I was thinking on how should we call the pair of entities performing TCM op=
timization. It has been set clear that if we call them mux/demux, it is not=
 exact, since we forget the tunnel and compressing layers.

Last Monday I proposed =93TCM-ingress optimizer=94 and =93TCM-egress optimi=
zer=94. However, I think these are too long names.

I received a suggestion about TCM-optimizer / TCM-deoptimizer. But, who wou=
ld buy a =93deoptimizer=94?

So I have a better proposal:

What about TCM optimizer <-----------------> TCM rebuilder?

The egress entity =93rebuilds=94 the packets to their native form. It is it=
s main task: to deliver a packet exactly as it was at the ingress of the tu=
nnel.

=93TCM reconstructor=94 could also be ok, but it is longer.

Do you like it?

Jose


________________________________

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

--Boundary_(ID_UvrwcR6Ytr5a/F7VMwU5zQ)
Content-id: <03DACA8DA72A874A96C25F9FEF64EF4A@hi.inet>
Content-type: text/html; charset=Windows-1252
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font=
-family:Calibri,sans-serif">
<div>
<div>
<div>Hi Jose,</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>I=B4m =
not sure about that. Optimizer and rebuilder make me think in very differen=
t things, and actually they should be very similar. I like &quot;TCM-ingres=
s optimizer&quot; and &quot;TCM-egress optimizer&quot;, couldn=B4t
 we use an acronym here?</div>
<div><br>
</div>
<div>&quot;TCM-ingress optimizer&quot;: TCM-IO</div>
<div>&quot;TCM-egress optimizer&quot;: TCM-EO</div>
<div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Fernando Pascual Blancouse&nbsp;</div>
<div>Telef=F3nica Global Resources</div>
<div>Network Automation and Dynamization</div>
<div>TECHNOLOGY PEOPLE GROUP</div>
<div>F &#43;34913128779</div>
<div>M &#43;34682005168</div>
<div>fpb@tid.es</div>
</div>
</div>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; border-bottom:medium none; border-left:medium none; padding-bottom:0i=
n; padding-left:0in; padding-right:0in; border-top:#b5c4df 1pt solid; borde=
r-right:medium none; padding-top:3pt">
<span style=3D"font-weight:bold">From: </span>&quot;<a href=3D"mailto:jsald=
ana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsaldana@=
unizar.es">jsaldana@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Organization: </span>Universidad de Zarago=
za<br>
<span style=3D"font-weight:bold">Reply-To: </span>&quot;<a href=3D"mailto:j=
saldana@unizar.es">jsaldana@unizar.es</a>&quot; &lt;<a href=3D"mailto:jsald=
ana@unizar.es">jsaldana@unizar.es</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>jueves, 20 de junio de 2013 0=
9:23<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:tcmtf@i=
etf.org">tcmtf@ietf.org</a>&quot; &lt;<a href=3D"mailto:tcmtf@ietf.org">tcm=
tf@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[tcmtf] What about TCM-Opt=
imizer --- TCM-Rebuilder?<br>
</div>
<div><br>
</div>
<div><style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
span.EstiloCorreo17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
.MsoChpDefault
	{font-family:"Calibri","sans-serif"}
@page WordSection1
	{margin:70.85pt 3.0cm 70.85pt 3.0cm}
div.WordSection1
	{}
-->
</style>
<div lang=3D"ES">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">I was thinking on how should we=
 call the pair of entities performing TCM optimization. It has been set cle=
ar that if we call them mux/demux, it is not exact, since we forget the tun=
nel and compressing layers.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Last Monday I proposed =93TCM-i=
ngress optimizer=94 and =93TCM-egress optimizer=94. However, I think these =
are too long names.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I received a suggestion about T=
CM-optimizer / TCM-deoptimizer. But, who would buy a =93deoptimizer=94?</sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">So I have a better proposal:</s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">What about TCM optimizer &lt;--=
---------------&gt; TCM rebuilder?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The egress entity =93rebuilds=
=94 the packets to their native form. It is its main task: to deliver a pac=
ket exactly as it was at the ingress of the tunnel.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=93TCM reconstructor=94 could a=
lso be ok, but it is longer.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Do you like it?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"">Jose</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
</div>
</div>
</span><br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_UvrwcR6Ytr5a/F7VMwU5zQ)--

From jsaldana@unizar.es  Thu Jun 20 06:47:50 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0385021F9CD3 for <tcmtf@ietfa.amsl.com>; Thu, 20 Jun 2013 06:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.5
X-Spam-Level: 
X-Spam-Status: No, score=-6.5 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QpT5Bans8PUP for <tcmtf@ietfa.amsl.com>; Thu, 20 Jun 2013 06:47:45 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4B23021F9CCD for <tcmtf@ietf.org>; Thu, 20 Jun 2013 06:47:44 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5KDldRk015799; Thu, 20 Jun 2013 15:47:39 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Martin Stiemerling'" <martin.stiemerling@neclab.eu>, <tcmtf@ietf.org>
References: <51C2B996.2060904@neclab.eu>
In-Reply-To: <51C2B996.2060904@neclab.eu>
Date: Thu, 20 Jun 2013 15:47:42 +0200
Organization: Universidad de Zaragoza
Message-ID: <014301ce6dbc$bd0b0ba0$372122e0$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFrMO3VStiEqwQ1NQm/OS19NisibpoFFjoA
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Security Threat: Compression Ratio Info-leak Made Easy	(CRIME)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 13:47:50 -0000

Hi, Martin.

I have been reading about the CRIME security exploit, but I think it only
affects if you compress the payload of the packet. What we are planning in
TCMTF is compressing headers in a certain network segment. After that, the
packet is rebuilt to its native form, so the packet arriving to the server
(or to the web browser) will have the same header it had when it was sent.
If you change the header, the packet does not arrive there.

Today we have discussed some security issues here. I hope we will send some
ideas to the list soon.

Thanks!

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
> Martin Stiemerling
> Enviado el: jueves, 20 de junio de 2013 10:13
> Para: tcmtf@ietf.org
> Asunto: [tcmtf] Security Threat: Compression Ratio Info-leak Made Easy
> (CRIME)
> 
> Hi all,
> 
> My fellow Security AD just pointed me to the following security threat
that
> might also applicable in the case of tcmtf:
> Compression Ratio Info-leak Made Easy (CRIME), see [1].
> 
> Just to let you know for your considerations.
> 
>    Martin
> 
> [1] http://en.wikipedia.org/wiki/CRIME_%28security_exploit%29
> 
> 
> --
> martin.stiemerling@neclab.eu
> 
> NEC Laboratories Europe
> NEC Europe Limited
> Registered Office:
> Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
> Registered in England 2832014
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From Martin.Stiemerling@neclab.eu  Thu Jun 20 13:13:39 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C751121E805E for <tcmtf@ietfa.amsl.com>; Thu, 20 Jun 2013 13:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.45
X-Spam-Level: 
X-Spam-Status: No, score=-103.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IHjNt+rpPFLs for <tcmtf@ietfa.amsl.com>; Thu, 20 Jun 2013 13:13:34 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 9AA6F21E80D3 for <tcmtf@ietf.org>; Thu, 20 Jun 2013 13:13:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id AA9751045ED; Thu, 20 Jun 2013 22:13:11 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mGE2evIp8fgG; Thu, 20 Jun 2013 22:13:11 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 8D8861045EC; Thu, 20 Jun 2013 22:12:51 +0200 (CEST)
Received: from [10.7.0.105] (10.7.0.105) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 20 Jun 2013 22:11:35 +0200
Message-ID: <51C36257.8020406@neclab.eu>
Date: Thu, 20 Jun 2013 22:13:11 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: <tcmtf@ietf.org>
References: <002801ce6cf9$500feac0$f02fc040$@unizar.es>
In-Reply-To: <002801ce6cf9$500feac0$f02fc040$@unizar.es>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.7.0.105]
Cc: Tomaso.deCola@dlr.de, Matteo.Berioli@dlr.de, jsaldana@unizar.es
Subject: [tcmtf] TCMTF BOF approved for IETF-87 in Berlon
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 20:13:39 -0000

Dear all,

The TCMTF BOF has been approved for the IETF-87 meeting in Berlin.

The chairs for the BOF will be announced shortly.

   Martin

-- 
IETF Transport Area Director

martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From jsaldana@unizar.es  Fri Jun 21 00:08:52 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B42D11E813D for <tcmtf@ietfa.amsl.com>; Fri, 21 Jun 2013 00:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.505
X-Spam-Level: 
X-Spam-Status: No, score=-6.505 tagged_above=-999 required=5 tests=[AWL=0.094,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xQmmG4hVScMi for <tcmtf@ietfa.amsl.com>; Fri, 21 Jun 2013 00:08:47 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 64F0F11E8136 for <tcmtf@ietf.org>; Fri, 21 Jun 2013 00:08:46 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5L78hnJ016563; Fri, 21 Jun 2013 09:08:43 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Martin Stiemerling'" <martin.stiemerling@neclab.eu>
References: <002801ce6cf9$500feac0$f02fc040$@unizar.es> <51C36257.8020406@neclab.eu>
In-Reply-To: <51C36257.8020406@neclab.eu>
Date: Fri, 21 Jun 2013 09:08:46 +0200
Organization: Universidad de Zaragoza
Message-ID: <006901ce6e4e$2c341bc0$849c5340$@unizar.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: es
Thread-index: AQGRblH9Zk4V+XD8Q7oln4gH4yvd3wF5KvHJma318XA=
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] TCMTF BOF approved for IETF-87 in Berlon
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 07:08:52 -0000

Thanks a lot, Martin! This is really good news indeed.

Now, we have to work hard for preparing it.

Thanks to you and to everybody,

Jose

> -----Mensaje original-----
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
> Martin Stiemerling
> Enviado el: jueves, 20 de junio de 2013 22:13
> Para: tcmtf@ietf.org
> CC: Tomaso.deCola@dlr.de; Matteo.Berioli@dlr.de; jsaldana@unizar.es
> Asunto: [tcmtf] TCMTF BOF approved for IETF-87 in Berlon
> 
> Dear all,
> 
> The TCMTF BOF has been approved for the IETF-87 meeting in Berlin.
> 
> The chairs for the BOF will be announced shortly.
> 
>    Martin
> 
> --
> IETF Transport Area Director
> 
> martin.stiemerling@neclab.eu
> 
> NEC Laboratories Europe
> NEC Europe Limited
> Registered Office:
> Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
> Registered in England 2832014
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


From diego@tid.es  Sun Jun 23 08:39:58 2013
Return-Path: <diego@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFF3421F9A3F for <tcmtf@ietfa.amsl.com>; Sun, 23 Jun 2013 08:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.704
X-Spam-Level: 
X-Spam-Status: No, score=-5.704 tagged_above=-999 required=5 tests=[AWL=-0.895, BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i9KqCllJSuNd for <tcmtf@ietfa.amsl.com>; Sun, 23 Jun 2013 08:39:54 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id A393421F9302 for <tcmtf@ietf.org>; Sun, 23 Jun 2013 08:39:53 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MOU00M6LRIGRD@tid.hi.inet> for tcmtf@ietf.org; Sun, 23 Jun 2013 17:39:52 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 9B.A4.03142.8C617C15; Sun, 23 Jun 2013 17:39:52 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MOU00M6HRIGRD@tid.hi.inet> for tcmtf@ietf.org; Sun, 23 Jun 2013 17:39:52 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Sun, 23 Jun 2013 17:38:52 +0200
Date: Sun, 23 Jun 2013 15:38:51 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <51C2B780.5000302@unizar.es>
X-Originating-IP: [10.95.64.115]
To: =?iso-8859-1?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A049CCEE78E@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_9LehshkNAMef93XZ3vveFQ)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] Other potential specific uses of TCM-TF
Thread-index: Ac5s978oBaw7NG94S9C/A9wEOusDMf//5SMAgAADrYCAAR+uAIAFNkgA
X-AuditID: 0a5f4068-b7f128e000000c46-6a-51c716c84025
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprAIsWRmVeSWpSXmKPExsXCFe/ApXtC7HigwaX5Uha7Pm9gdGD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRtey0IK15hUz15o1MJ7W72Lk5JAQMJH4MmEeK4QtJnHh3no2 EFtIYCOjxKqLZl2MXED2D0aJGee2skI40xglHn7/ygxSxSKgKjH560swmw3IftT8mx3EFhaw kTh07QgLiM0poCmx8v4ZNogNChJ/zj0Gi4sIuEoce7iRCcRmFlCXWPNvE1gNr4C3ROOVuywQ tqDEj8n3WCBqciV+Hn4GVS8u0dx6EyzOKCAr8W7+fFaImbYSreveQ813k1gwdRM7xF4BiSV7 zjND2KISLx//Y4X48gijxKENohMYxWYhWTcLybpZSNZB2HoSN6ZOYYOwtSWWLXzNDGHrSsz4 dwiqxkzi277VTMhqFjByrGIUK04qykzPKMlNzMxJNzDUy8jUy8xLLdnECInFjB2My3eqHGIU 4GBU4uE9kHokUIg1say4MvcQowQHs5II74ZrxwKFeFMSK6tSi/Lji0pzUosPMTJxcEo1MBre Uea6tGZ7P9fxGTYbpvH4zuPh3uWy9VixSubcRw4SlXOm6t9vvsre/uEGc2rlB5GWosxzl78U zHOSbT/Pbaguu/KoGov2ckkXB7atPDeLnvov2eHgWF3VWGPaqsz5p8HjyefIaE7lVSmxdWW6 Ao7PFq1e92DRpaNth13lWl+XFu+Ovd28VImlOCPRUIu5qDgRAEGeWh+jAgAA
References: <002801ce6cf9$500feac0$f02fc040$@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CCE874D@EX10-MB2-MAD.hi.inet> <005501ce6cfc$eb6e5d00$c24b1700$@unizar.es> <51C2B780.5000302@unizar.es>
Cc: "<tcmtf@ietf.org>" <tcmtf@ietf.org>
Subject: Re: [tcmtf] Other potential specific uses of TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Jun 2013 15:39:58 -0000

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

Hi Julian,

I definitely think you have a point here. We can consider different securit=
y contexts for different tunnels, according to some policy agreed by both e=
nd-points at a given tunnel.
The security contexts would define encryption, authentication, or both. We'=
d have to go into more detail to evaluate potential savings, but I have the=
 feeling they could be worth considering.

The point is that if we go for these different security contexts, we must c=
onsider how they can be established by mutual authentication of the tunnel =
end-points, and this opens additional issues regarding configuration and cr=
ypto material exchange, as well as the possibility of user-initiated authen=
tication by means of protocols like OAuth.

I'd keep this in the list of the "soon-to-open" issues, focusing on the thr=
ee main docs we have been discussing so far.

Be goode,

On 20 Jun 2013, at 10:04 , Juli=E1n Fern=E1ndez-Navajas wrote:

Hi all,
I like to add a potencial new idea which could be addressed by re-charterin=
g. What about the security on the tunnel?. It is possible to add security t=
o TCMTF because it is inherent in the tunnels. And not only consider encryp=
tion, but also the digital signature which represents much loss of efficien=
cy in the case of small packages.
Someone have more knowledge about this issue?
Juli=E1n

El 19/06/2013 16:54, Jose Saldana escribi=F3:
which could be addressed by re-chartering

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


--
"Esta vez no fallaremos, Doctor Infierno"

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

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


________________________________

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

--Boundary_(ID_9LehshkNAMef93XZ3vveFQ)
Content-id: <743946CEB336864EABEC221877607C9A@hi.inet>
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap:break-word">
Hi Julian,
<div><br>
</div>
<div>I definitely think you have a point here. We can consider different se=
curity contexts for different tunnels, according to some policy agreed by b=
oth end-points at a given tunnel.&nbsp;</div>
<div>The security contexts would define encryption, authentication, or both=
. We'd have to go into more detail to evaluate potential savings, but I hav=
e the feeling they could be worth considering.</div>
<div><br>
</div>
<div>The point is that if we go for these different security contexts, we m=
ust consider how they can be established by mutual authentication of the tu=
nnel end-points, and this opens additional issues regarding configuration a=
nd crypto material exchange, as
 well as the possibility of user-initiated authentication by means of proto=
cols like OAuth.</div>
<div><br>
</div>
<div>I'd keep this in the list of the &quot;soon-to-open&quot; issues, focu=
sing on the three main docs we have been discussing so far.</div>
<div><br>
</div>
<div>Be goode,</div>
<div>&nbsp;</div>
<div>
<div>
<div>On 20 Jun 2013, at 10:04 , Juli=E1n Fern=E1ndez-Navajas wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div bgcolor=3D"#FFFFFF">
<div class=3D"moz-cite-prefix">Hi all,<br>
I like to add a potencial new idea which could be addressed by re-charterin=
g. What about the security on the tunnel?. It is possible to add security t=
o TCMTF because it is inherent in the tunnels. And not only consider encryp=
tion, but also the digital signature
 which represents much loss of efficiency in the case of small packages.<br=
>
Someone have more knowledge about this issue?<br>
Juli=E1n<br>
<br>
El 19/06/2013 16:54, Jose Saldana escribi=F3:<br>
</div>
<blockquote type=3D"cite"><span lang=3D"EN-US" style=3D"font-size:11.0pt; f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">which=
 could be addressed by re-chartering</span></blockquote>
<br>
</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<br>
</blockquote>
</div>
<br>
<div><span class=3D"Apple-style-span" style=3D"border-collapse:separate; co=
lor:rgb(0,0,0); font-family:Helvetica; font-style:normal; font-variant:norm=
al; font-weight:normal; letter-spacing:normal; line-height:normal; orphans:=
2; text-indent:0px; text-transform:none; white-space:normal; widows:2; word=
-spacing:0px; font-size:medium"><span class=3D"Apple-style-span" style=3D"b=
order-collapse:separate; color:rgb(0,0,0); font-family:Helvetica; font-styl=
e:normal; font-variant:normal; font-weight:normal; letter-spacing:normal; l=
ine-height:normal; orphans:2; text-indent:0px; text-transform:none; white-s=
pace:normal; widows:2; word-spacing:0px; font-size:medium">
<div style=3D"word-wrap:break-word"><span class=3D"Apple-style-span" style=
=3D"border-collapse:separate; color:rgb(0,0,0); font-family:Helvetica; font=
-style:normal; font-variant:normal; font-weight:normal; letter-spacing:norm=
al; line-height:normal; orphans:2; text-indent:0px; text-transform:none; wh=
ite-space:normal; widows:2; word-spacing:0px; font-size:medium">
<div style=3D"word-wrap:break-word"><br>
--<br>
&quot;Esta vez no fallaremos, Doctor Infierno&quot;<br>
<br>
Dr Diego R. Lopez<br>
Telefonica I&#43;D</div>
<div style=3D"word-wrap:break-word"><a href=3D"http://people.tid.es/diego.l=
opez/">http://people.tid.es/diego.lopez/</a><br>
<br>
e-mail: diego@tid.es<br>
Tel: &nbsp; &nbsp;&#43;34 913 129 041<br>
Mobile: &#43;34 682 051 091<br>
-----------------------------------------</div>
</span></div>
</span></span></div>
<br>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_9LehshkNAMef93XZ3vveFQ)--

From jsaldana@unizar.es  Mon Jun 24 00:44:34 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F25A021E80CA for <tcmtf@ietfa.amsl.com>; Mon, 24 Jun 2013 00:44:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.36
X-Spam-Level: 
X-Spam-Status: No, score=-6.36 tagged_above=-999 required=5 tests=[AWL=-0.062,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PU4LmwkOWZ9D for <tcmtf@ietfa.amsl.com>; Mon, 24 Jun 2013 00:44:26 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id B73D521F9D7D for <tcmtf@ietf.org>; Mon, 24 Jun 2013 00:44:22 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5O7iFFR007033; Mon, 24 Jun 2013 09:44:15 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'Diego R. Lopez'" <diego@tid.es>, "=?iso-8859-1?Q?'Juli=E1n_Fern=E1ndez-Navajas'?=" <navajas@unizar.es>
References: <002801ce6cf9$500feac0$f02fc040$@unizar.es>	<E6D8B95470ED0845B3376F61DCAB1A049CCE874D@EX10-MB2-MAD.hi.inet>	<005501ce6cfc$eb6e5d00$c24b1700$@unizar.es>	<51C2B780.5000302@unizar.es> <E6D8B95470ED0845B3376F61DCAB1A049CCEE78E@EX10-MB2-MAD.hi.inet>
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A049CCEE78E@EX10-MB2-MAD.hi.inet>
Date: Mon, 24 Jun 2013 09:44:17 +0200
Organization: Universidad de Zaragoza
Message-ID: <00bc01ce70ae$a35d6370$ea182a50$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BD_01CE70BF.66E63370"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGRblH9Zk4V+XD8Q7oln4gH4yvd3wHAKZFaAiNmO5QCxDuZPwISYHSBmXiuoXA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Other potential specific uses of TCM-TF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 07:44:35 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00BD_01CE70BF.66E63370
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Regarding security, we have identified at least one scenario with =
security
issues:

=20

- We have N flows which are traveling through a =93dangerous=94 network =
segment
(e.g. the =93public=94 Internet).

- Instead of adding security to each flow (e.g. using IPSec for each =
flow),
can we multiplex them and use a single security tunnel instead of N =
security
tunnels.

- It would save bandwidth, since it would avoid N-1 additional security
headers.

=20

1

2

=85   ---->TCM-ingress ------> non secure network segment ---------->
TCM-egress ----> flows rebuilt to their native forms

N

=20

=20

The questions are:

=20

Does this scenario exist? i.e. a number of flows traveling through a
=93dangerous=94 network segment. (perhaps a tunnel between appliances =
connecting
remote offices of a company)

=20

Would this be valid for IPSec in tunnel mode? I would avoid N-1 tunnel
headers.

=20

Would this be valid for IPSec in transport mode? I would avoid N-1 times =
the
=93Authentication header=94 or the =93Encapsulation Security Header=94.

=20

Which would be the best way for adding security to TCM?. Perhaps IPSec =
added
to the tunneling header would be the most straightforward solution.

=20

=20

Jose

=20

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
Diego R. Lopez
Enviado el: domingo, 23 de junio de 2013 17:39
Para: Juli=E1n Fern=E1ndez-Navajas
CC: <tcmtf@ietf.org>
Asunto: Re: [tcmtf] Other potential specific uses of TCM-TF

=20

Hi Julian,=20

=20

I definitely think you have a point here. We can consider different =
security
contexts for different tunnels, according to some policy agreed by both
end-points at a given tunnel.=20

The security contexts would define encryption, authentication, or both. =
We'd
have to go into more detail to evaluate potential savings, but I have =
the
feeling they could be worth considering.

=20

The point is that if we go for these different security contexts, we =
must
consider how they can be established by mutual authentication of the =
tunnel
end-points, and this opens additional issues regarding configuration and
crypto material exchange, as well as the possibility of user-initiated
authentication by means of protocols like OAuth.

=20

I'd keep this in the list of the "soon-to-open" issues, focusing on the
three main docs we have been discussing so far.

=20

Be goode,

=20

On 20 Jun 2013, at 10:04 , Juli=E1n Fern=E1ndez-Navajas wrote:





Hi all,
I like to add a potencial new idea which could be addressed by
re-chartering. What about the security on the tunnel?. It is possible to =
add
security to TCMTF because it is inherent in the tunnels. And not only
consider encryption, but also the digital signature which represents =
much
loss of efficiency in the case of small packages.
Someone have more knowledge about this issue?
Juli=E1n

El 19/06/2013 16:54, Jose Saldana escribi=F3:

which could be addressed by re-chartering

=20

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

=20


--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D

http://people.tid.es/diego.lopez/

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

=20

=20

  _____ =20


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


------=_NextPart_000_00BD_01CE70BF.66E63370
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:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><!--[if =
!mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>Regarding security, we have identified at least one =
scenario with security issues:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- We have N flows which are =
traveling through a &#8220;dangerous&#8221; network segment (e.g. the =
&#8220;public&#8221; Internet).<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>- Instead of adding security to =
each flow (e.g. using IPSec for each flow), can we multiplex them and =
use a single security tunnel instead of N security =
tunnels.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>- =
It would save bandwidth, since it would avoid N-1 additional security =
headers.<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<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>2<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>&#8230;=A0=A0 ----&gt;TCM-ingress ------&gt; non secure =
network segment ----------&gt; TCM-egress ----&gt; flows rebuilt to =
their native forms<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>N<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 questions 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>Does this scenario exist? i.e. a =
number of flows traveling through a &#8220;dangerous&#8221; network =
segment. (perhaps a tunnel between appliances connecting remote offices =
of a company)<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>Would this be valid for IPSec in tunnel mode? I would avoid =
N-1 tunnel headers.<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>Would this be valid for IPSec in transport mode? I would =
avoid N-1 times the &#8220;Authentication header&#8221; or the =
&#8220;Encapsulation Security Header&#8221;.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Which would be the best way for =
adding security to TCM?. Perhaps IPSec added to the tunneling header =
would be the most straightforward solution.<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>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></=
b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] <b>En nombre de =
</b>Diego R. Lopez<br><b>Enviado el:</b> domingo, 23 de junio de 2013 =
17:39<br><b>Para:</b> Juli=E1n Fern=E1ndez-Navajas<br><b>CC:</b> =
&lt;tcmtf@ietf.org&gt;<br><b>Asunto:</b> Re: [tcmtf] Other potential =
specific uses of TCM-TF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Hi Julian, =
<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
definitely think you have a point here. We can consider different =
security contexts for different tunnels, according to some policy agreed =
by both end-points at a given tunnel.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>The security contexts would define encryption, =
authentication, or both. We'd have to go into more detail to evaluate =
potential savings, but I have the feeling they could be worth =
considering.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The point is that if we go for these different =
security contexts, we must consider how they can be established by =
mutual authentication of the tunnel end-points, and this opens =
additional issues regarding configuration and crypto material exchange, =
as well as the possibility of user-initiated authentication by means of =
protocols like OAuth.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>I'd keep this in the list of the =
&quot;soon-to-open&quot; issues, focusing on the three main docs we have =
been discussing so far.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Be goode,<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><div><div><p =
class=3DMsoNormal>On 20 Jun 2013, at 10:04 , Juli=E1n =
Fern=E1ndez-Navajas wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal>Hi all,<br>I like to add a potencial new idea which =
could be addressed by re-chartering. What about the security on the =
tunnel?. It is possible to add security to TCMTF because it is inherent =
in the tunnels. And not only consider encryption, but also the digital =
signature which represents much loss of efficiency in the case of small =
packages.<br>Someone have more knowledge about this =
issue?<br>Juli=E1n<br><br>El 19/06/2013 16:54, Jose Saldana =
escribi=F3:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>which could be addressed by =
re-chartering</span><o:p></o:p></p></blockquote><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p =
class=3DMsoNormal>_______________________________________________<br>tcmt=
f 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">https://www.ietf.org=
/mailman/listinfo/tcmtf</a><o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif";color:blac=
k'><br>--<br>&quot;Esta vez no fallaremos, Doctor =
Infierno&quot;<br><br>Dr Diego R. Lopez<br>Telefonica =
I+D<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif";color:blac=
k'><a =
href=3D"http://people.tid.es/diego.lopez/">http://people.tid.es/diego.lop=
ez/</a><br><br>e-mail: <a =
href=3D"mailto:diego@tid.es">diego@tid.es</a><br>Tel: &nbsp; &nbsp;+34 =
913 129 041<br>Mobile: +34 682 051 =
091<br>-----------------------------------------<o:p></o:p></span></p></d=
iv></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><hr size=3D2 width=3D"100%" =
align=3Dcenter></div><p class=3DMsoNormal><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'><br=
>Este mensaje se dirige exclusivamente a su destinatario. Puede =
consultar nuestra pol=EDtica de env=EDo y recepci=F3n de correo =
electr=F3nico en el enlace situado m=E1s abajo.<br>This message is =
intended exclusively for its addressee. We only send and receive email =
on the basis of the terms set out at:<br><a =
href=3D"http://www.tid.es/ES/PAGINAS/disclaimer.aspx">http://www.tid.es/E=
S/PAGINAS/disclaimer.aspx</a></span><o:p></o:p></p></div></div></body></h=
tml>
------=_NextPart_000_00BD_01CE70BF.66E63370--


From jsaldana@unizar.es  Mon Jun 24 04:00:22 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2634411E80FB for <tcmtf@ietfa.amsl.com>; Mon, 24 Jun 2013 04:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.507
X-Spam-Level: 
X-Spam-Status: No, score=-6.507 tagged_above=-999 required=5 tests=[AWL=0.091,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i3aQUSiFAYKe for <tcmtf@ietfa.amsl.com>; Mon, 24 Jun 2013 04:00:14 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 25E9011E8128 for <tcmtf@ietf.org>; Mon, 24 Jun 2013 04:00:10 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5OB03bN023304 for <tcmtf@ietf.org>; Mon, 24 Jun 2013 13:00:07 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Mon, 24 Jun 2013 13:00:05 +0200
Organization: Universidad de Zaragoza
Message-ID: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_007F_01CE70DA.C1A328C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5wycGHbApylKz/RhmtAnL3dgONFw==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 11:00:22 -0000

This is a multipart message in MIME format.

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

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

 

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

 

Thanks!

 

Jose

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>I would like to start a thread about possible questions =
people may ask in the BOF. Obviously, we also need answers, so we should =
cooperate.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This is different from the &#8220;questions to ask in the =
BOF&#8221;. This will be discussed separately.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Thanks!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:ES'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_000_007F_01CE70DA.C1A328C0--


From jsaldana@unizar.es  Mon Jun 24 04:21:19 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8E2621E80DC for <tcmtf@ietfa.amsl.com>; Mon, 24 Jun 2013 04:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.511
X-Spam-Level: 
X-Spam-Status: No, score=-6.511 tagged_above=-999 required=5 tests=[AWL=0.087,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wB7Ywn+85JZM for <tcmtf@ietfa.amsl.com>; Mon, 24 Jun 2013 04:21:02 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id EFAFB21F9D47 for <tcmtf@ietf.org>; Mon, 24 Jun 2013 04:20:57 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5OBKplr012487; Mon, 24 Jun 2013 13:20:52 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <jsaldana@unizar.es>, <tcmtf@ietf.org>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
In-Reply-To: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
Date: Mon, 24 Jun 2013 13:20:55 +0200
Organization: Universidad de Zaragoza
Message-ID: <009601ce70cc$e4e73500$aeb59f00$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0097_01CE70DD.A870C850"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHxl5HfJe4XxEPJrqhURPk2/vEH5pj+ZmlQ
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 11:21:20 -0000

This is a multipart message in MIME format.

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

Question: Why Transport Area?

 

Answer:

 

There are three possibilities: RAI, Internet and Transport Area. These are
some of the protocols to be used:

 

L2TPv3: Internet Area (RFC 3931, March 2005)

PPPMux: Internet Area (RFC 3153, August 2001)

ECRTP: RAI Area (RFC 3545, July 2003)

ROHC: Transport Area, although it can also compress RTP (RFC 5795, March
2010)

 

1) RAI

TCM-TF is about real-time services. In fact, it would update RFC4170, which
was developed within the RAI Area.

 

However, we are proposing to go towards a more generic scheme. RAI area is
mainly focused on RTP, and TCM-TF only considers RTP as one of the
possibilities. Bare UDP or even TCP flows can be compressed, multiplexed and
tunneled.

 

 

2) Internet Area or Transport Area?

 

RFC 1122 defines the layers as:

 

- Transport Layer: "The transport layer provides *end-to-end* communication
services for applications".

 

- Internet Layer: "All Internet transport protocols use the Internet
Protocol (IP) to carry data from source host to destination host. IP is a
connectionless or datagram internetwork service, providing *no end-to-end*
delivery guarantees".

 

 

TCMTF is an *end-to-end* solution, requiring some knowledge of the traffic
to multiplex, and a synchronization of the context on both sides.

 

So it is clear that it fits in the Transport Area.

 

Jose

 

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

 

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

 

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

 

Thanks!

 

Jose

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Question: Why Transport =
Area?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Answer:<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'>There are =
three possibilities: RAI, Internet and Transport Area. These are some of =
the protocols to be used:<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'>L2TPv3: =
Internet Area (RFC 3931, March 2005)<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>PPPMux: =
Internet Area (RFC 3153, August 2001)<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>ECRTP: RAI =
Area (RFC 3545, July 2003)<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>ROHC: =
Transport Area, although it can also compress RTP (RFC 5795, March =
2010)<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>1) =
RAI<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>TCM-TF is about real-time services. In fact, it =
would update RFC4170, which was developed within the RAI =
Area.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>However, we =
are proposing to go towards a more generic scheme. RAI area is mainly =
focused on RTP, and TCM-TF only considers RTP as one of the =
possibilities. Bare UDP or even TCP flows can be compressed, multiplexed =
and tunneled.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>2) Internet =
Area or Transport Area?<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'>RFC 1122 =
defines the layers as:<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'>- Transport =
Layer: &#8220;The transport layer provides *<b>end-to-end</b>* =
communication services for applications&#8221;.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- Internet =
Layer: &#8220;All Internet transport protocols use the Internet Protocol =
(IP) to carry data from source host to destination host. IP is a =
connectionless or datagram internetwork service, providing *<b>no =
end-to-end</b>* delivery guarantees&#8221;.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>TCMTF is an =
*<b>end-to-end</b>* solution, requiring some knowledge of the traffic to =
multiplex, and a synchronization of the context on both =
sides.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>So it is =
clear that it fits in the Transport Area.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'>De:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'> tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] =
<b>En nombre de </b>Jose Saldana<br><b>Enviado el:</b> lunes, 24 de =
junio de 2013 13:00<br><b>Para:</b> tcmtf@ietf.org<br><b>Asunto:</b> =
[tcmtf] Answers to possible questions in the =
BOF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>I would like to start a thread about possible questions =
people may ask in the BOF. Obviously, we also need answers, so we should =
cooperate.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This is different from the &#8220;questions to ask in the =
BOF&#8221;. This will be discussed separately.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Thanks!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:ES'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_0097_01CE70DD.A870C850--


From jsaldana@unizar.es  Mon Jun 24 04:31:17 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 927ED21E80DC for <tcmtf@ietfa.amsl.com>; Mon, 24 Jun 2013 04:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.515
X-Spam-Level: 
X-Spam-Status: No, score=-6.515 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o5mniopBY4IC for <tcmtf@ietfa.amsl.com>; Mon, 24 Jun 2013 04:31:11 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2B49211E8129 for <tcmtf@ietf.org>; Mon, 24 Jun 2013 04:31:10 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5OBV6Qq019940; Mon, 24 Jun 2013 13:31:06 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <jsaldana@unizar.es>, <tcmtf@ietf.org>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
In-Reply-To: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
Date: Mon, 24 Jun 2013 13:31:10 +0200
Organization: Universidad de Zaragoza
Message-ID: <00a401ce70ce$53435aa0$f9ca0fe0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A5_01CE70DF.16CC2AA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHxl5HfJe4XxEPJrqhURPk2/vEH5pj+arnQ
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 11:31:17 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00A5_01CE70DF.16CC2AA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Question 2: Why creating a Working Group? Why not doing this inside the
tsvwg?

 

Answer:

 

This was our first idea, one year ago. But it has become clear that a
specific WG is required for this. 

 

This in it is something a separate WG should be created to handle, and not
something to try to do inside the TSVWG, since there are already a handful
of things TSVWG is wrestling with, and it creates too much "context
switching" to have a lot of unrelated topics under work there.

 

The question is that the TSVWG group has a lot of interesting things now,
and it would be better to discuss TCMTF separately.

 

 

Any comments?

 

Jose

 

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

 

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

 

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

 

Thanks!

 

Jose

 


------=_NextPart_000_00A5_01CE70DF.16CC2AA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.EstiloCorreo17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-priority:99;
	mso-style-link:"Texto sin formato";
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Question 2: Why creating a Working =
Group? Why not doing this inside the tsvwg?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Answer:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>This was =
our first idea, one year ago. But it has become clear that a specific WG =
is required for this. <o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>This in it =
is something a separate WG should be created to handle, and not =
something to try to do inside the TSVWG, since there are already a =
handful of things TSVWG is wrestling with, and it creates too much =
&quot;context switching&quot; to have a lot of unrelated topics under =
work there.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US style=3D'color:#1F497D'>The =
question is that the TSVWG group has a lot of interesting things now, =
and it would be better to discuss TCMTF =
separately.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Any =
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'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'>De:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'> tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] =
<b>En nombre de </b>Jose Saldana<br><b>Enviado el:</b> lunes, 24 de =
junio de 2013 13:00<br><b>Para:</b> tcmtf@ietf.org<br><b>Asunto:</b> =
[tcmtf] Answers to possible questions in the =
BOF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>I would like to start a thread about possible questions =
people may ask in the BOF. Obviously, we also need answers, so we should =
cooperate.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This is different from the &#8220;questions to ask in the =
BOF&#8221;. This will be discussed separately.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Thanks!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:ES'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_00A5_01CE70DF.16CC2AA0--


From navajas@unizar.es  Mon Jun 24 07:19:39 2013
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA1DD21E8102 for <tcmtf@ietfa.amsl.com>; Mon, 24 Jun 2013 07:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sonOeCulYcJ6 for <tcmtf@ietfa.amsl.com>; Mon, 24 Jun 2013 07:19:34 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 87E4821E811D for <tcmtf@ietf.org>; Mon, 24 Jun 2013 07:19:33 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5OEJTn4002882 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Mon, 24 Jun 2013 16:19:29 +0200
Message-ID: <51C85565.3030703@unizar.es>
Date: Mon, 24 Jun 2013 16:19:17 +0200
From: =?ISO-8859-15?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <00a401ce70ce$53435aa0$f9ca0fe0$@unizar.es>
In-Reply-To: <00a401ce70ce$53435aa0$f9ca0fe0$@unizar.es>
Content-Type: multipart/alternative; boundary="------------070000080201090605000807"
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jun 2013 14:19:40 -0000

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

I agree with Jose about the group TSVWG has a lot of interesting things 
now, and it would be best to discuss TCMTF separately.
Julián

El 24/06/2013 13:31, Jose Saldana escribió:
> TSVWG group has a lot of interesting things now, and it would be 
> better to discuss TCMTF separately.


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-15"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">I agree with Jose about the group TSVWG
      has a lot of interesting things now, and it would be best to
      discuss TCMTF separately.<br>
      Julián<br>
      <br>
      El 24/06/2013 13:31, Jose Saldana escribió:<br>
    </div>
    <blockquote cite="mid:00a401ce70ce$53435aa0$f9ca0fe0$@unizar.es"
      type="cite"><span style="color:#1F497D" lang="EN-US"> TSVWG group
        has a lot of interesting things now, and it would be better to
        discuss TCMTF separately.</span></blockquote>
    <br>
  </body>
</html>

--------------070000080201090605000807--

From jsaldana@unizar.es  Tue Jun 25 01:26:59 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6C6821F91A5 for <tcmtf@ietfa.amsl.com>; Tue, 25 Jun 2013 01:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.519
X-Spam-Level: 
X-Spam-Status: No, score=-6.519 tagged_above=-999 required=5 tests=[AWL=0.079,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NEiQyeIK0pjq for <tcmtf@ietfa.amsl.com>; Tue, 25 Jun 2013 01:26:50 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id EB74021F8D10 for <tcmtf@ietf.org>; Tue, 25 Jun 2013 01:26:49 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5P8Qevv022912 for <tcmtf@ietf.org>; Tue, 25 Jun 2013 10:26:45 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
In-Reply-To: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
Date: Tue, 25 Jun 2013 10:26:42 +0200
Organization: Universidad de Zaragoza
Message-ID: <003a01ce717d$bc286e20$34794a60$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_003B_01CE718E.7FB13E20"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHxl5HfJe4XxEPJrqhURPk2/vEH5pj/xyyg
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2013 08:26:59 -0000

This is a multipart message in MIME format.

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

Question 3: You are talking about real-time services (VoIP, online games,
remote desktop). *Why adding a new (multiplexing) delay?* Would it harm the
user's experience with the service?

 

Answer

 

1) We have had that question in mind from the very beginning. We want to
save bandwidth and pps, but always preserving subjective quality. In fact, a
specific draft has been written including a set of recommendations of the
maximum delays that can be tolerated by users of different services. The
draft includes references to studies where subjective quality has been
evaluated with real people.

 

 

2) In addition, our idea is that TCM-TF can be something to be used
dynamically when required. Some examples:

 

- I am in the rush hour and I notice a lot of traffic in my network. In
order to avoid the collapse, I optimize traffic. I add a small delay, but
the bandwidth savings can make it possible that the service still works.

 

- I am an online games provider and I am releasing a new title. The first
days, a lot of people will want to play. So, how can I dimension my network?
Should I dimension it for the worst case?

 

TCM-TF provides flexibility: there is a tradeoff: a small additional delay
as the price for maintaining the service. It should be taken into account
that for certain services the bandwidth savings are 50 or even 60%.

 

 

3) If I have a high number of flows, I can achieve significant bandwidth
savings while adding small delays. Some examples:

- 10 VoIP flows G729 can be optimized including one packet from each flow
(average additional delay 10ms) and 50% of bandwidth can be saved

- if I have 100 flows of a TCP-based online game, I can achieve 45%
bandwidth saving with a multiplexing period of 30 ms (average additional
delay 15ms)

 

 

4) TCM-TF is not only for real-time services. Other small-packet services
can be optimized, and in this case the additional delay would not be
significant.

 

 

Any other thoughts?

 

Jose

 

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

 

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

 

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

 

Thanks!

 

Jose

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Question 3: You are talking about =
real-time services (VoIP, online games, remote desktop). *<b>Why adding =
a new (multiplexing) delay?</b>* Would it harm the user&#8217;s =
experience with the service?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Answer<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>1) We have =
had that question in mind from the very beginning. We want to save =
bandwidth and pps, but always preserving subjective quality. In fact, a =
specific draft has been written including a set of recommendations of =
the maximum delays that can be tolerated by users of different services. =
The draft includes references to studies where subjective quality has =
been evaluated with real people.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>2) In =
addition, our idea is that TCM-TF can be something to be used =
dynamically when required. Some examples:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- I am in =
the rush hour and I notice a lot of traffic in my network. In order to =
avoid the collapse, I optimize traffic. I add a small delay, but the =
bandwidth savings can make it possible that the service still =
works.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- I am an =
online games provider and I am releasing a new title. The first days, a =
lot of people will want to play. So, how can I dimension my network? =
Should I dimension it for the worst case?<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'>TCM-TF =
provides flexibility: there is a tradeoff: a small additional delay as =
the price for maintaining the service. It should be taken into account =
that for certain services the bandwidth savings are 50 or even =
60%.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>3) If I =
have a high number of flows, I can achieve significant bandwidth savings =
while adding small delays. Some examples:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>- 10 VoIP =
flows G729 can be optimized including one packet from each flow (average =
additional delay 10ms) and 50% of bandwidth can be =
saved<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>- if I have 100 flows of a TCP-based online =
game, I can achieve 45% bandwidth saving with a multiplexing period of =
30 ms (average additional delay 15ms)<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>4) TCM-TF =
is not only for real-time services. Other small-packet services can be =
optimized, and in this case the additional delay would not be =
significant.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Any other =
thoughts?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'>De:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'> tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] =
<b>En nombre de </b>Jose Saldana<br><b>Enviado el:</b> lunes, 24 de =
junio de 2013 13:00<br><b>Para:</b> tcmtf@ietf.org<br><b>Asunto:</b> =
[tcmtf] Answers to possible questions in the =
BOF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>I would like to start a thread about possible questions =
people may ask in the BOF. Obviously, we also need answers, so we should =
cooperate.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This is different from the &#8220;questions to ask in the =
BOF&#8221;. This will be discussed separately.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Thanks!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:ES'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_003B_01CE718E.7FB13E20--


From Mirko.Suznjevic@fer.hr  Wed Jun 26 01:35:37 2013
Return-Path: <Mirko.Suznjevic@fer.hr>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04AF121F848A for <tcmtf@ietfa.amsl.com>; Wed, 26 Jun 2013 01:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hQyBxk3SyNP1 for <tcmtf@ietfa.amsl.com>; Wed, 26 Jun 2013 01:35:32 -0700 (PDT)
Received: from mail.fer.hr (mail5.fer.hr [161.53.72.235]) by ietfa.amsl.com (Postfix) with ESMTP id 724C721F8E77 for <tcmtf@ietf.org>; Wed, 26 Jun 2013 01:35:30 -0700 (PDT)
Received: from POSTAR.fer.hr (2002:a135:48ed::a135:48ed) by MAIL5.fer.hr (2002:a135:48eb::a135:48eb) with Microsoft SMTP Server (TLS) id 14.2.342.3; Wed, 26 Jun 2013 10:35:28 +0200
Received: from MAIL4.fer.hr ([2002:a135:48ea::a135:48ea]) by POSTAR.fer.hr ([2002:a135:48ed::a135:48ed]) with mapi id 14.02.0342.003; Wed, 26 Jun 2013 10:35:28 +0200
From: =?utf-8?B?TWlya28gU3XFvm5qZXZpxIc=?= <Mirko.Suznjevic@fer.hr>
To: "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] Improved version of the tmctf Draft charter (v6)
Thread-Index: Ac5oEUJh6X32UcmxT3KmocW8KKc14f//3/+AgAJobQCAA8z8gIAAGU6AgAAkjID///Z7gP/x3DGA
Date: Wed, 26 Jun 2013 08:35:26 +0000
Message-ID: <E004A7C54DE04F4BB87DB9F32308DA5C0C1C09@MAIL4.fer.hr>
References: <F5EDC35DF914C1428C28E149F10463A29C8ABCAE@EX10-MB2-MAD.hi.inet> <51BEE74B.7080104@unizar.es>
In-Reply-To: <51BEE74B.7080104@unizar.es>
Accept-Language: en-US, hr-HR
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [85.114.38.130]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 08:35:37 -0000

SSBhbSBtYXliZSBhIGxpdHRsZSBsYXRlLCBidXQgaSBhZ3JlZSB3aXRoIHRoaXMgdGVybWlub2xv
Z3kuDQpNaXJrbw0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogdGNtdGYtYm91
bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnRjbXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBP
ZiBKb3PDqSBSdWl6DQpTZW50OiBNb25kYXksIEp1bmUgMTcsIDIwMTMgMTI6MzkgUE0NClRvOiB0
Y210ZkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFt0Y210Zl0gSW1wcm92ZWQgdmVyc2lvbiBvZiB0
aGUgdG1jdGYgRHJhZnQgY2hhcnRlciAodjYpDQoNCkhpIGFsbCwNCg0KSSBhZ3JlZSB3aXRoIHlv
dS4gIlRDTSBvcHRpbWl6ZXJzIiBhbmQgIlRDTSBmbG93IiB3b3VsZCBiZSBlbm91Z2gsDQoNClBl
cGUNCg0KRWwgMTcvMDYvMjAxMyAxMToxMiwgRkVSTkFORE8gUEFTQ1VBTCBCTEFOQ08gZXNjcmli
acOzOg0KPiBIaSBKb3NlLCBKdWxpYW4sDQo+DQo+ICAgICAgICAgIFllcywgIlRDTSBvcHRpbWl6
ZXJzIiBhbmQgIlRDTSBmbG93IiBhcmUgcGVyZmVjdCBmb3IgbWUgdG9vLg0KPg0KPiBCZXN0LA0K
Pg0KPiBGZXJuYW5kbyBQYXNjdWFsIEJsYW5jbw0KPiBUZWxlZsOzbmljYSBHbG9iYWwgUmVzb3Vy
Y2VzDQo+IE5ldHdvcmsgQXV0b21hdGlvbiBhbmQgRHluYW1pemF0aW9uDQo+IFRFQ0hOT0xPR1kg
UEVPUExFIEdST1VQDQo+IEYgKzM0OTEzMTI4Nzc5DQo+IE0gKzM0NjgyMDA1MTY4DQo+IGZwYkB0
aWQuZXMNCj4NCj4NCj4NCj4NCj4gT24gMTcvMDYvMTMgMTE6MDIsICJKdWxpw6FuIEZlcm7DoW5k
ZXotTmF2YWphcyIgPG5hdmFqYXNAdW5pemFyLmVzPiB3cm90ZToNCj4NCj4+IEkgYWdyZWUgd2l0
aCBGZXJuYW5kbyB0b28sIG5vIGludmVudCBuZXcgRW5nbGlzaCB2ZXJiLg0KPj4gSW4gcmVsYXRp
b24gd2l0aCBkdXBsaWNhdGluZyBmbG93IHdvcmQsIGkgdGhpbmsgdGhhdCBpdCBpcyBmaW5lIHRv
IA0KPj4gdXNlICJUQ00gZmxvdyIgaW5zdGVhZCBvZiAiVENNVEYgZmxvdyIuDQo+PiBKdWxpw6Fu
DQo+Pg0KPj4gRWwgMTcvMDYvMjAxMyA5OjMxLCBKb3NlIFNhbGRhbmEgZXNjcmliacOzOg0KPj4+
IEhpLCBGZXJuYW5kby4NCj4+Pg0KPj4+IEkgYWdyZWUgd2l0aCB5b3UuIFdlIGFyZSB0YWxraW5n
IGFib3V0IHN0YW5kYXJkcyBzbyBwcmVjaXNpb24gaXMgDQo+Pj4gaW1wb3J0YW50Lg0KPj4+DQo+
Pj4gSSBkb24ndCB0aGluayB3ZSBzaG91bGQgdXNlIHRoZSAidmVyYiIgInRvIFRDTVRGIiBub3Ig
IlRDTVRGaW5nIiBub3IgDQo+Pj4gIlRDTVRGZWQiLiBXZSBjYW5ub3QgaW52ZW50IG5ldyBFbmds
aXNoIHZlcmJzLg0KPj4+DQo+Pj4gV2hhdCBhYm91dCAib3B0aW1pemF0aW9uIj8uIFRoaXMgY29u
Y2VwdCBzdW1tYXJpemVzIHRoZSB0aHJlZSBsYXllcnMuDQo+Pj4gV2UgY2FuDQo+Pj4gdXNlIGl0
IHRoaXMgd2F5Og0KPj4+DQo+Pj4gLSBBIFRDTVRGIG9wdGltaXplcg0KPj4+DQo+Pj4gLSBBIHBh
Y2tldCBvcHRpbWl6ZWQgYnkgbWVhbnMgb2YgVENNVEYNCj4+PiAtIEEgZmxvdyBvcHRpbWl6ZWQg
YnkgbWVhbnMgb2YgVENNVEYNCj4+PiAtIEFuIG9wdGltaXplZCBwYWNrZXQNCj4+PiAtIEFuIG9w
dGltaXplZCBmbG93DQo+Pj4gLSBBIFRDTVRGLW9wdGltaXplZCBwYWNrZXQNCj4+PiAtIEEgVENN
VEYtb3B0aW1pemVkIGZsb3cNCj4+PiAtIEEgVENNVEYgcGFja2V0DQo+Pj4gLSBBIFRDTVRGIGZs
b3cNCj4+Pg0KPj4+IC0gdGhlIFRDTVRGIG9wdGltaXphdGlvbiBjYW4gYmUgYXBwbGllZCB0byB0
aGF0IGZsb3cNCj4+PiAtIHRoZSBpbXBhY3Qgb2YgVENNVEYgb3B0aW1pemF0aW9uIG9uIHByb3Rv
Y29sIGR5bmFtaWNzDQo+Pj4NCj4+PiBJIGhhdmUgYW5vdGhlciBxdWVzdGlvbiBoZXJlOiBjb3Vs
ZCB3ZSB1c2Ugb25seSBUQ00gaW5zdGVhZCBvZiBUQ01URj8NCj4+PiBSZW1lbWJlciB0aGF0IFRG
IG1lYW5zICJ0cmFmZmljIGZsb3dzIiwgc28gYSBUQ01URiBmbG93IHdvdWxkIGJlIGEgDQo+Pj4g
InR1bm5lbGluZyBjb21wcmVzc2VkIG11bHRpcGxleGVkIHRyYWZmaWMgZmxvd3MgZmxvdyIuIFBl
cmhhcHMgYSBUQ00gDQo+Pj4gZmxvdyB3b3VsZCBiZSBlbm91Z2ggaW4gdGhvc2UgY2FzZXMuIFRD
TSBkb2VzIG5vdCBoYXZlIGFub3RoZXIgDQo+Pj4gcmVsYXRlZCBtZWFuaW5nIGFuZCBpdCBpcyBz
aG9ydGVyIHRoYW4gVENNVEYgDQo+Pj4gKGh0dHA6Ly93d3cuYWNyb255bWZpbmRlci5jb20vVENN
Lmh0bWwpDQo+Pj4NCj4+PiAtIEEgVENNIG9wdGltaXplcg0KPj4+IC0gQSBUQ00tb3B0aW1pemVk
IGZsb3cNCj4+PiAtIEEgVENNIGZsb3cNCj4+Pg0KPj4+IFdoYXQgZG8geW91IHRoaW5rPw0KPj4+
DQo+Pj4gSm9zZQ0KPj4+DQo+Pj4NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCnRjbXRmIG1haWxpbmcgbGlzdA0KdGNtdGZAaWV0Zi5vcmcNCmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdGNtdGYNCg==

From navajas@unizar.es  Wed Jun 26 02:24:25 2013
Return-Path: <navajas@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13E6B21E811E for <tcmtf@ietfa.amsl.com>; Wed, 26 Jun 2013 02:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EStJOr6w32JE for <tcmtf@ietfa.amsl.com>; Wed, 26 Jun 2013 02:24:20 -0700 (PDT)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0529121E8122 for <tcmtf@ietf.org>; Wed, 26 Jun 2013 02:24:18 -0700 (PDT)
Received: from [155.210.156.37] (tele3.cps.unizar.es [155.210.156.37]) (authenticated bits=0) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5Q9OAOB016138 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <tcmtf@ietf.org>; Wed, 26 Jun 2013 11:24:15 +0200
Message-ID: <51CAB328.5090300@unizar.es>
Date: Wed, 26 Jun 2013 11:23:52 +0200
From: =?ISO-8859-15?Q?Juli=E1n_Fern=E1ndez-Navajas?= <navajas@unizar.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: tcmtf@ietf.org
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <003a01ce717d$bc286e20$34794a60$@unizar.es>
In-Reply-To: <003a01ce717d$bc286e20$34794a60$@unizar.es>
Content-Type: multipart/alternative; boundary="------------080605080605030603060501"
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 09:24:25 -0000

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

Another answer for this question is that if you reduce the pps in the 
network it is possible that the delay also reduces, because the nodes 
have minor charge of work.
Julián

El 25/06/2013 10:26, Jose Saldana escribió:
>
> Question 3: You are talking about real-time services (VoIP, online 
> games, remote desktop). **Why adding a new (multiplexing) delay?** 
> Would it harm the user's experience with the service?
>
> Answer
>
> 1) We have had that question in mind from the very beginning. We want 
> to save bandwidth and pps, but always preserving subjective quality. 
> In fact, a specific draft has been written including a set of 
> recommendations of the maximum delays that can be tolerated by users 
> of different services. The draft includes references to studies where 
> subjective quality has been evaluated with real people.
>
> 2) In addition, our idea is that TCM-TF can be something to be used 
> dynamically when required. Some examples:
>
> - I am in the rush hour and I notice a lot of traffic in my network. 
> In order to avoid the collapse, I optimize traffic. I add a small 
> delay, but the bandwidth savings can make it possible that the service 
> still works.
>
> - I am an online games provider and I am releasing a new title. The 
> first days, a lot of people will want to play. So, how can I dimension 
> my network? Should I dimension it for the worst case?
>
> TCM-TF provides flexibility: there is a tradeoff: a small additional 
> delay as the price for maintaining the service. It should be taken 
> into account that for certain services the bandwidth savings are 50 or 
> even 60%.
>
> 3) If I have a high number of flows, I can achieve significant 
> bandwidth savings while adding small delays. Some examples:
>
> - 10 VoIP flows G729 can be optimized including one packet from each 
> flow (average additional delay 10ms) and 50% of bandwidth can be saved
>
> - if I have 100 flows of a TCP-based online game, I can achieve 45% 
> bandwidth saving with a multiplexing period of 30 ms (average 
> additional delay 15ms)
>
> 4) TCM-TF is not only for real-time services. Other small-packet 
> services can be optimized, and in this case the additional delay would 
> not be significant.
>
> Any other thoughts?
>
> Jose
>
> *De:*tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] *En nombre 
> de *Jose Saldana
> *Enviado el:* lunes, 24 de junio de 2013 13:00
> *Para:* tcmtf@ietf.org
> *Asunto:* [tcmtf] Answers to possible questions in the BOF
>
> I would like to start a thread about possible questions people may ask 
> in the BOF. Obviously, we also need answers, so we should cooperate.
>
> This is different from the "questions to ask in the BOF". This will be 
> discussed separately.
>
> Thanks!
>
> Jose
>
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-15"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Another answer for this question is
      that if you reduce the pps in the network it is possible that the
      delay also reduces, because the nodes have minor charge of work.<br>
      Julián<br>
      <br>
      El 25/06/2013 10:26, Jose Saldana escribió:<br>
    </div>
    <blockquote cite="mid:003a01ce717d$bc286e20$34794a60$@unizar.es"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-15">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Question
            3: You are talking about real-time services (VoIP, online
            games, remote desktop). *<b>Why adding a new (multiplexing)
              delay?</b>* Would it harm the user&#8217;s experience with the
            service?<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Answer<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">1)
            We have had that question in mind from the very beginning.
            We want to save bandwidth and pps, but always preserving
            subjective quality. In fact, a specific draft has been
            written including a set of recommendations of the maximum
            delays that can be tolerated by users of different services.
            The draft includes references to studies where subjective
            quality has been evaluated with real people.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">2)
            In addition, our idea is that TCM-TF can be something to be
            used dynamically when required. Some examples:<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">-
            I am in the rush hour and I notice a lot of traffic in my
            network. In order to avoid the collapse, I optimize traffic.
            I add a small delay, but the bandwidth savings can make it
            possible that the service still works.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">-
            I am an online games provider and I am releasing a new
            title. The first days, a lot of people will want to play.
            So, how can I dimension my network? Should I dimension it
            for the worst case?<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">TCM-TF
            provides flexibility: there is a tradeoff: a small
            additional delay as the price for maintaining the service.
            It should be taken into account that for certain services
            the bandwidth savings are 50 or even 60%.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">3)
            If I have a high number of flows, I can achieve significant
            bandwidth savings while adding small delays. Some examples:<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">-
            10 VoIP flows G729 can be optimized including one packet
            from each flow (average additional delay 10ms) and 50% of
            bandwidth can be saved<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">-
            if I have 100 flows of a TCP-based online game, I can
            achieve 45% bandwidth saving with a multiplexing period of
            30 ms (average additional delay 15ms)<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">4)
            TCM-TF is not only for real-time services. Other
            small-packet services can be optimized, and in this case the
            additional delay would not be significant.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Any
            other thoughts?<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US">Jose<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D" lang="EN-US"><o:p> </o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0cm
          0cm 0cm 4.0pt">
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0cm 0cm 0cm">
              <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ES">De:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ES">
                  <a class="moz-txt-link-abbreviated" href="mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]
                  <b>En nombre de </b>Jose Saldana<br>
                  <b>Enviado el:</b> lunes, 24 de junio de 2013 13:00<br>
                  <b>Para:</b> <a class="moz-txt-link-abbreviated" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
                  <b>Asunto:</b> [tcmtf] Answers to possible questions
                  in the BOF<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><span lang="EN-US">I would like to start
              a thread about possible questions people may ask in the
              BOF. Obviously, we also need answers, so we should
              cooperate.<o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">This is different from
              the &#8220;questions to ask in the BOF&#8221;. This will be discussed
              separately.<o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US">Thanks!<o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
          <p class="MsoNormal"><span style="mso-fareast-language:ES"
              lang="EN-US">Jose<o:p></o:p></span></p>
          <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
tcmtf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tcmtf@ietf.org">tcmtf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/tcmtf">https://www.ietf.org/mailman/listinfo/tcmtf</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------080605080605030603060501--

From Mirko.Suznjevic@fer.hr  Wed Jun 26 02:36:28 2013
Return-Path: <Mirko.Suznjevic@fer.hr>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4719811E80CC for <tcmtf@ietfa.amsl.com>; Wed, 26 Jun 2013 02:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lYsU1D5xRjcA for <tcmtf@ietfa.amsl.com>; Wed, 26 Jun 2013 02:36:22 -0700 (PDT)
Received: from mail.fer.hr (mail.fer.hr [161.53.72.233]) by ietfa.amsl.com (Postfix) with ESMTP id F11D321F93D4 for <tcmtf@ietf.org>; Wed, 26 Jun 2013 02:35:52 -0700 (PDT)
Received: from MAIL4.fer.hr ([2002:a135:48ea::a135:48ea]) by MAIL.fer.hr ([2002:a135:48e9::a135:48e9]) with mapi id 14.02.0342.003; Wed, 26 Jun 2013 11:35:48 +0200
From: =?windows-1250?Q?Mirko_Su=9Enjevi=E6?= <Mirko.Suznjevic@fer.hr>
To: "tcmtf@ietf.org" <tcmtf@ietf.org>
Thread-Topic: [tcmtf] Answers to possible questions in the BOF
Thread-Index: Ac5wycGHbApylKz/RhmtAnL3dgONFwAozNkAADiR09A=
Date: Wed, 26 Jun 2013 09:35:47 +0000
Message-ID: <E004A7C54DE04F4BB87DB9F32308DA5C0C1C7A@MAIL4.fer.hr>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <003a01ce717d$bc286e20$34794a60$@unizar.es>
In-Reply-To: <003a01ce717d$bc286e20$34794a60$@unizar.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [85.114.38.130]
Content-Type: multipart/alternative; boundary="_000_E004A7C54DE04F4BB87DB9F32308DA5C0C1C7AMAIL4ferhr_"
MIME-Version: 1.0
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 09:36:28 -0000

--_000_E004A7C54DE04F4BB87DB9F32308DA5C0C1C7AMAIL4ferhr_
Content-Type: text/plain; charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

Hello all,
Here i have just a small addition:
By using TCM-TF we aim maintain the QoE of the service, or at least minimiz=
e the degradation.

1)      Recommended limits of multiplexing period are given in order not do=
 significantly degrade the service (on applicable applications and studies =
we aimed at MOS over 4).

2)      1st example of a dynamic scenarios TCMTF is actually reducing laten=
cy by preventing congestion (rush hour scenario)

2)      2nd example of the launch of the game scenario TCM-TF provides sign=
ificant savings, and increase of the QoE as service unavailability is much =
much more QoE degrading for gamers than slight latency increase
Also i would emphasize that the added delay is very minimal on links with h=
igh packet rate, and that the maximal introduced delay can be controlled wi=
th the multiplexing period depending on how much tradeoff is needed or allo=
wed.
Cheers!
Mirko
From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of J=
ose Saldana
Sent: Tuesday, June 25, 2013 10:27 AM
To: tcmtf@ietf.org
Subject: Re: [tcmtf] Answers to possible questions in the BOF

Question 3: You are talking about real-time services (VoIP, online games, r=
emote desktop). *Why adding a new (multiplexing) delay?* Would it harm the =
user=92s experience with the service?

Answer

1) We have had that question in mind from the very beginning. We want to sa=
ve bandwidth and pps, but always preserving subjective quality. In fact, a =
specific draft has been written including a set of recommendations of the m=
aximum delays that can be tolerated by users of different services. The dra=
ft includes references to studies where subjective quality has been evaluat=
ed with real people.


2) In addition, our idea is that TCM-TF can be something to be used dynamic=
ally when required. Some examples:

- I am in the rush hour and I notice a lot of traffic in my network. In ord=
er to avoid the collapse, I optimize traffic. I add a small delay, but the =
bandwidth savings can make it possible that the service still works.

- I am an online games provider and I am releasing a new title. The first d=
ays, a lot of people will want to play. So, how can I dimension my network?=
 Should I dimension it for the worst case?

TCM-TF provides flexibility: there is a tradeoff: a small additional delay =
as the price for maintaining the service. It should be taken into account t=
hat for certain services the bandwidth savings are 50 or even 60%.


3) If I have a high number of flows, I can achieve significant bandwidth sa=
vings while adding small delays. Some examples:
- 10 VoIP flows G729 can be optimized including one packet from each flow (=
average additional delay 10ms) and 50% of bandwidth can be saved
- if I have 100 flows of a TCP-based online game, I can achieve 45% bandwid=
th saving with a multiplexing period of 30 ms (average additional delay 15m=
s)


4) TCM-TF is not only for real-time services. Other small-packet services c=
an be optimized, and in this case the additional delay would not be signifi=
cant.


Any other thoughts?

Jose

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

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

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

Thanks!

Jose


--_000_E004A7C54DE04F4BB87DB9F32308DA5C0C1C7AMAIL4ferhr_
Content-Type: text/html; charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
250">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:450243252;
	mso-list-type:hybrid;
	mso-list-template-ids:-142578728 68812817 68812825 68812827 68812815 68812=
825 68812827 68812815 68812825 68812827;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:864173852;
	mso-list-type:hybrid;
	mso-list-template-ids:242932694 68812817 68812825 68812827 68812815 688128=
25 68812827 68812815 68812825 68812827;}
@list l1:level1
	{mso-level-start-at:2;
	mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"HR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Hello a=
ll,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Here i =
have just a small addition:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">By usin=
g TCM-TF we aim maintain the QoE of the service, or at least minimize the d=
egradation.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span lang=3D"EN-GB" style=3D"color:#1F497D">=
<span style=3D"mso-list:Ignore">1)<span style=3D"font:7.0pt &quot;Times New=
 Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB" style=3D"color:#1F497D"=
>Recommended limits of multiplexing period are given in order not do signif=
icantly degrade the service (on applicable applications and studies we aime=
d at MOS over 4).<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span lang=3D"EN-GB" style=3D"color:#1F497D">=
<span style=3D"mso-list:Ignore">2)<span style=3D"font:7.0pt &quot;Times New=
 Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB" style=3D"color:#1F497D"=
>1<sup>st</sup> example of a dynamic scenarios TCMTF is actually reducing l=
atency by preventing congestion (rush hour scenario)<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-GB" style=3D"color:#1F497D">=
<span style=3D"mso-list:Ignore">2)<span style=3D"font:7.0pt &quot;Times New=
 Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-GB" style=3D"color:#1F497D"=
>2<sup>nd</sup> example of the launch of the game scenario TCM-TF provides =
significant savings, and increase of the QoE as service unavailability is m=
uch much more QoE degrading for gamers
 than slight latency increase<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Also i =
would emphasize that the added delay is very minimal on links with high pac=
ket rate, and that the maximal introduced delay can be controlled with the =
multiplexing period depending on how much
 tradeoff is needed or allowed.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Cheers!=
<br>
Mirko&nbsp;&nbsp;&nbsp; <o:p></o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-GB" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org=
]
<b>On Behalf Of </b>Jose Saldana<br>
<b>Sent:</b> Tuesday, June 25, 2013 10:27 AM<br>
<b>To:</b> tcmtf@ietf.org<br>
<b>Subject:</b> Re: [tcmtf] Answers to possible questions in the BOF<o:p></=
o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Questio=
n 3: You are talking about real-time services (VoIP, online games, remote d=
esktop). *<b>Why adding a new (multiplexing) delay?</b>* Would it harm the =
user=92s experience with the service?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Answer<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">1) We h=
ave had that question in mind from the very beginning. We want to save band=
width and pps, but always preserving subjective quality. In fact, a specifi=
c draft has been written including a set
 of recommendations of the maximum delays that can be tolerated by users of=
 different services. The draft includes references to studies where subject=
ive quality has been evaluated with real people.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">2) In a=
ddition, our idea is that TCM-TF can be something to be used dynamically wh=
en required. Some examples:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">- I am =
in the rush hour and I notice a lot of traffic in my network. In order to a=
void the collapse, I optimize traffic. I add a small delay, but the bandwid=
th savings can make it possible that the
 service still works.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">- I am =
an online games provider and I am releasing a new title. The first days, a =
lot of people will want to play. So, how can I dimension my network? Should=
 I dimension it for the worst case?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">TCM-TF =
provides flexibility: there is a tradeoff: a small additional delay as the =
price for maintaining the service. It should be taken into account that for=
 certain services the bandwidth savings
 are 50 or even 60%.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">3) If I=
 have a high number of flows, I can achieve significant bandwidth savings w=
hile adding small delays. Some examples:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">- 10 Vo=
IP flows G729 can be optimized including one packet from each flow (average=
 additional delay 10ms) and 50% of bandwidth can be saved<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">- if I =
have 100 flows of a TCP-based online game, I can achieve 45% bandwidth savi=
ng with a multiplexing period of 30 ms (average additional delay 15ms)<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">4) TCM-=
TF is not only for real-time services. Other small-packet services can be o=
ptimized, and in this case the additional delay would not be significant.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Any oth=
er thoughts?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D">Jose<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"color:#1F497D"><o:p>&n=
bsp;</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-GB" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">De:</span></b><span la=
ng=3D"EN-GB" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;">
<a href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a hr=
ef=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]
<b>En nombre de </b>Jose Saldana<br>
<b>Enviado el:</b> lunes, 24 de junio de 2013 13:00<br>
<b>Para:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tcmtf] Answers to possible questions in the BOF<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">I would like to start a thread =
about possible questions people may ask in the BOF. Obviously, we also need=
 answers, so we should cooperate.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">This is different from the =93q=
uestions to ask in the BOF=94. This will be discussed separately.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Thanks!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Jose<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</body>
</html>

--_000_E004A7C54DE04F4BB87DB9F32308DA5C0C1C7AMAIL4ferhr_--

From jsaldana@unizar.es  Wed Jun 26 03:49:28 2013
Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06EBE11E81B0 for <tcmtf@ietfa.amsl.com>; Wed, 26 Jun 2013 03:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VMOzEZFZBqaT for <tcmtf@ietfa.amsl.com>; Wed, 26 Jun 2013 03:49:23 -0700 (PDT)
Received: from isuela.unizar.es (isuela.unizar.es [155.210.1.53]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB6B11E81AF for <tcmtf@ietf.org>; Wed, 26 Jun 2013 03:49:22 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by isuela.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5QAnEPc020711 for <tcmtf@ietf.org>; Wed, 26 Jun 2013 12:49:19 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
In-Reply-To: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es>
Date: Wed, 26 Jun 2013 12:49:17 +0200
Organization: Universidad de Zaragoza
Message-ID: <009901ce725a$d1623360$74269a20$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_009A_01CE726B.94EB9FA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHxl5HfJe4XxEPJrqhURPk2/vEH5pkBfNvw
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jsaldana@unizar.es
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 10:49:28 -0000

This is a multipart message in MIME format.

------=_NextPart_000_009A_01CE726B.94EB9FA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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

 

Answer:

 

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

 

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

 

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

www.huawei.com/ilink/en/download/HW_193034

 

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

 

- Wireless and satellite scenarios.

 

 

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

 

 

Jose

 

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

 

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

 

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

 

Thanks!

 

Jose

 


------=_NextPart_000_009A_01CE726B.94EB9FA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Question 4: Is TCM-TF interesting =
for the Industry? Should the IETF standardize =
this?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>Answer:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>1) TCM-TF =
intends to update RFC4170, which optimizes RTP VoIP traffic. So if =
RFC4170 was interesting, why not updating it?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>2) TCM-TF =
can be useful in order to save bandwidth in many =
cases:<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'>- =
Aggregation network of *<b>network operators</b>*: We are saving =
bandwidth by optimizing and putting together traffic flows. Is this =
interesting for a network operator? What about overprovisioning? The =
idea is that there are places and moments in which a number of flows =
based on small packets are in the same place and at the same moment. =
Then, TCM-TF can be applied in order to provide flexibility. We are not =
optimizing the overall Internet traffic, we are optimizing specific =
flows with very tight delay requirements, which network operators have =
to take care of in a special way.<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:#009933;=
background:white'><a =
href=3D"http://www.huawei.com/ilink/en/download/HW_193034">www.huawei.com=
/ilink/en/download/HW_193034</a><o:p></o:p></span></p><p =
class=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'>- *<b>End =
to end</b>* optimization: Nowadays, many appliances are used to connect =
remote offices of the same company (creating a VPN). So if a tunnel =
exists, why not optimizing this traffic when possible? We would save =
bandwidth in the access network, where it can be =
scarce.<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'>- Wireless =
and satellite scenarios.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Any other =
thoughts? Any other scenarios in mind? Potential beneficiaries? =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'>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";mso-fareast-l=
anguage:ES'>De:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'> tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] =
<b>En nombre de </b>Jose Saldana<br><b>Envia</b></span><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'>do el:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ES'> lunes, 24 de junio de 2013 13:00<br><b>Para:</b> =
tcmtf@ietf.org<br><b>Asunto:</b> [tcmtf] Answers to possible questions =
in the BOF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>I would like to start a thread about possible questions =
people may ask in the BOF. Obviously, we also need answers, so we should =
cooperate.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>This is different from the &#8220;questions to ask in the =
BOF&#8221;. This will be discussed separately.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Thanks!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:ES'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_009A_01CE726B.94EB9FA0--


From dflorez@tid.es  Wed Jun 26 06:14:14 2013
Return-Path: <dflorez@tid.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4297F21E8126 for <tcmtf@ietfa.amsl.com>; Wed, 26 Jun 2013 06:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r+3CMQH3SI6h for <tcmtf@ietfa.amsl.com>; Wed, 26 Jun 2013 06:14:10 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 807ED21E80D7 for <tcmtf@ietf.org>; Wed, 26 Jun 2013 06:14:05 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MP0003TQ4RAHL@tid.hi.inet> for tcmtf@ietf.org; Wed, 26 Jun 2013 15:14:04 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 43.67.03142.B19EAC15; Wed, 26 Jun 2013 15:14:04 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MP0003AT4RFCD@tid.hi.inet> for tcmtf@ietf.org; Wed, 26 Jun 2013 15:14:03 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.38]) by EX10-HTCAS8-MAD.hi.inet ([fe80::41c8:e965:8a6:de67%11]) with mapi id 14.02.0328.009; Wed, 26 Jun 2013 15:14:03 +0200
Date: Wed, 26 Jun 2013 13:13:00 +0000
From: DAVID FLOREZ RODRIGUEZ <dflorez@tid.es>
In-reply-to: <009901ce725a$d1623360$74269a20$@unizar.es>
X-Originating-IP: [10.95.64.115]
To: "jsaldana@unizar.es" <jsaldana@unizar.es>, "tcmtf@ietf.org" <tcmtf@ietf.org>
Message-id: <DB1D666A7A799C4EA9B8D31FFB919BB252A25B68@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_gNxRfo+THhb6tpQCNEBrHA)"
Content-language: es-ES
Accept-Language: es-ES, en-US
Thread-topic: [tcmtf] Answers to possible questions in the BOF
Thread-index: Ac5wycGHbApylKz/RhmtAnL3dgONFwBgEj+AAAkHEbA=
X-AuditID: 0a5f4068-b7f128e000000c46-30-51cae91bdfd1
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsXCFe/ApSvz8lSgwQU3i12fNzA6MHosWfKT KYAxissmJTUnsyy1SN8ugSujv/kIS8H3yYwVPSceMjUwTm1m7GLk5JAQMJE4c+Q3lC0mceHe erYuRi4OIYGNjBKvL35hhHB+MEqc75rPDOFsYJTY8fk2O0gLi4CqRO+x+0wgNpuArsS8PbNZ QGxhAVuJFY+esoHYnAIWElcuQdgSAgoSf849BqsREQiQ2N1yAMzmFfCWaF4+hQnCFpT4Mfke WJxZIFfi+LR7jBC2uMScXxNZQWxGAVmJledPM0LMsZOYvm0j1EwriW9PdrJA7BKQWLLnPDOE LSrx8vE/sF4hgVSJ/XMOM09gFJ2FZN0sJOtmIVkHYetJ3Jg6hQ3C1pZYtvA1M4StKzHj3yEW ZPEFjOyrGMWKk4oy0zNKchMzc9INDPUyMvUy81JLNjFCYixjB+PynSqHGAU4GJV4eE9sOhko xJpYVlyZe4hRgoNZSYT3zfxTgUK8KYmVValF+fFFpTmpxYcYmTg4pRoYG6rUhWYUb2X8V7Wl WPZapvatqWVhhllS84UP6RslTr44122zW3POu5qsmuXGC/7WcmflbEzetOHjtuBQSSm20hte hrPPXnyz54q7Zr2LzNkHb5x6mm6lM9yQdcpmyJvdKNm4w8S0O+GbO7P79vP/i3cGvH8n37tg 6Wy5Rwl7xD/P8Q67eVtaiaU4I9FQi7moOBEABnQmW48CAAA=
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es>
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 13:14:14 -0000

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

Howdy,

Regarding the industry, specially operators' interest. I think that part of=
 the case relies on the assumption that TCMT could help operators to cope w=
ith surges of traffic, either local or global.

The case of traffic surges would have also the advantage that the interacti=
vity requirement could be relaxed, since there would be more packets to pro=
cess in the first time, and most importantly, that the application point of=
 the algorithms could be shallow or deep in the network, according to traff=
ic status.

Best Regards,

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

David Fl=F3rez Rodr=EDguez
Phome: 34+913129618
Backup Phone: 34+913128842
e-mail: dflorez@tid.es<mailto:dflorez@tid.es>
Network Optimisation and Dynamisation Initiative
Telefonica I+D

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

As if my life were shaven
and fitted to a frame
and could not breathe without a key
and 'twas like midnight, some,
when everything that ticked has stopped
and space stares all around
or grisly frost, first autumn morns,
repeal the beating ground
but most like chaos, stopless, cool
without a chance or spar
or even a report of land
to justify dispair

              Emily Dickinson

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

De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de Jos=
e Saldana
Enviado el: mi=E9rcoles, 26 de junio de 2013 12:49
Para: tcmtf@ietf.org
Asunto: Re: [tcmtf] Answers to possible questions in the BOF

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

Answer:

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

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

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

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

- Wireless and satellite scenarios.


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


Jose

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

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

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

Thanks!

Jose


________________________________

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style>
<!--
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif"}
span.EstiloCorreo17
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.EstiloCorreo18
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
span.TextodegloboCar
	{font-family:"Tahoma","sans-serif"}
span.EstiloCorreo21
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:70.85pt 3.0cm 70.85pt 3.0cm}
div.WordSection1
	{}
-->
</style>
</head>
<body lang=3D"ES" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Howdy,<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regardi=
ng the industry, specially operators&#8217; interest. I think that part of =
the case relies on the assumption that TCMT could help operators to cope wi=
th surges of traffic, either local or global.
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">The cas=
e of traffic surges would have also the advantage that the interactivity re=
quirement could be relaxed, since there would be more packets to process in=
 the first time, and most importantly,
 that the application point of the algorithms could be shallow or deep in t=
he network, according to traffic status.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Best Re=
gards,</span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">----------=
--------------------------------------------------------</span><span lang=
=3D"EN-US" style=3D"color:#1F497D"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">David Fl=
=F3rez Rodr=EDguez</span><span lang=3D"EN-US" style=3D"color:#1F497D"></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">Phome: 34&=
#43;913129618</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">Backup Pho=
ne: 34&#43;913128842</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">e-mail:
<a href=3D"mailto:dflorez@tid.es">dflorez@tid.es</a></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">Network Op=
timisation and Dynamisation Initiative</span><span lang=3D"EN-US" style=3D"=
color:#1F497D"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">Telefonica=
 I&#43;D</span><span lang=3D"EN-US" style=3D"color:#1F497D"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">----------=
--------------------------------------------------------</span><span lang=
=3D"EN-US" style=3D"color:#1F497D"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">As if my l=
ife were shaven</span><span lang=3D"EN-US" style=3D"color:#1F497D"></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">and fitted=
 to a frame</span><span lang=3D"EN-US" style=3D"color:#1F497D"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">and could =
not breathe without a key</span><span lang=3D"EN-US" style=3D"color:#1F497D=
"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">and 'twas =
like midnight, some,</span><span lang=3D"EN-US" style=3D"color:#1F497D"></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">when every=
thing that ticked has stopped</span><span lang=3D"EN-US" style=3D"color:#1F=
497D"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">and space =
stares all around</span><span lang=3D"EN-US" style=3D"color:#1F497D"></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">or grisly =
frost, first autumn morns,</span><span lang=3D"EN-US" style=3D"color:#1F497=
D"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">repeal the=
 beating ground</span><span lang=3D"EN-US" style=3D"color:#1F497D"></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">but most l=
ike chaos, stopless, cool</span><span lang=3D"EN-US" style=3D"color:#1F497D=
"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">without a =
chance or spar</span><span lang=3D"EN-US" style=3D"color:#1F497D"></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">or even a =
report of land</span><span lang=3D"EN-US" style=3D"color:#1F497D"></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">to justify=
 dispair</span><span lang=3D"EN-US" style=3D"color:#1F497D"></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<b>Emily Dickinson</b></span><span lang=3D"EN-US" style=3D"color:#1F497D"><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#1F497D">----------=
-------------------------------------------------------</span><span lang=3D=
"EN-US" style=3D"color:#1F497D"></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0c=
m 0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt; font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">De:</span></b><span style=3D"font-si=
ze:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tcmtf-bo=
unces@ietf.org [mailto:tcmtf-bounces@ietf.org]
<b>En nombre de </b>Jose Saldana<br>
<b>Enviado el:</b> mi=E9rcoles, 26 de junio de 2013 12:49<br>
<b>Para:</b> tcmtf@ietf.org<br>
<b>Asunto:</b> Re: [tcmtf] Answers to possible questions in the BOF</span><=
/p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Questio=
n 4: Is TCM-TF interesting for the Industry? Should the IETF standardize th=
is?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Answer:=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">1) TCM-=
TF intends to update RFC4170, which optimizes RTP VoIP traffic. So if RFC41=
70 was interesting, why not updating it?</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">2) TCM-=
TF can be useful in order to save bandwidth in many cases:</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">- Aggre=
gation network of *<b>network operators</b>*: We are saving bandwidth by op=
timizing and putting together traffic flows. Is this interesting for a netw=
ork operator? What about overprovisioning?
 The idea is that there are places and moments in which a number of flows b=
ased on small packets are in the same place and at the same moment. Then, T=
CM-TF can be applied in order to provide flexibility. We are not optimizing=
 the overall Internet traffic, we
 are optimizing specific flows with very tight delay requirements, which ne=
twork operators have to take care of in a special way.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt; font=
-family:&quot;Arial&quot;,&quot;sans-serif&quot;; color:#009933; background=
:white"><a href=3D"http://www.huawei.com/ilink/en/download/HW_193034">www.h=
uawei.com/ilink/en/download/HW_193034</a></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">- *<b>E=
nd to end</b>* optimization: Nowadays, many appliances are used to connect =
remote offices of the same company (creating a VPN). So if a tunnel exists,=
 why not optimizing this traffic when
 possible? We would save bandwidth in the access network, where it can be s=
carce.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">- Wirel=
ess and satellite scenarios.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Any oth=
er thoughts? Any other scenarios in mind? Potential beneficiaries?
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Jose</s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&nbsp;<=
/span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0cm 0cm 0c=
m 4.0pt">
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0c=
m 0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt; f=
ont-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">De:</span></b><span l=
ang=3D"EN-US" style=3D"font-size:10.0pt; font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;">
<a href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> [<a hr=
ef=3D"mailto:tcmtf-bounces@ietf.org">mailto:tcmtf-bounces@ietf.org</a>]
<b>En nombre de </b>Jose Saldana<br>
<b>Envia</b></span><b><span style=3D"font-size:10.0pt; font-family:&quot;Ta=
homa&quot;,&quot;sans-serif&quot;">do el:</span></b><span style=3D"font-siz=
e:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> lunes, 24=
 de junio de 2013 13:00<br>
<b>Para:</b> <a href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b> [tcmtf] Answers to possible questions in the BOF</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I would like to start a thread =
about possible questions people may ask in the BOF. Obviously, we also need=
 answers, so we should cooperate.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">This is different from the &#82=
20;questions to ask in the BOF&#8221;. This will be discussed separately.</=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks!</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"">Jose</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
</div>
<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_gNxRfo+THhb6tpQCNEBrHA)--

From dwing@cisco.com  Wed Jun 26 13:13:54 2013
Return-Path: <dwing@cisco.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEAFC11E81F5 for <tcmtf@ietfa.amsl.com>; Wed, 26 Jun 2013 13:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aLIxW3WK4EgW for <tcmtf@ietfa.amsl.com>; Wed, 26 Jun 2013 13:13:50 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 9A00D11E81F7 for <tcmtf@ietf.org>; Wed, 26 Jun 2013 13:13:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15005; q=dns/txt; s=iport; t=1372277630; x=1373487230; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=Wfx5TqQAoE/hf+rfEEHV7phZeZF4sKM0NkQM8iyGsgg=; b=CSYwQvO5tRu5B47dqZqMSWAIRbWnb94whd8kWnBanw0uwhjPH/41SwIE VEDUXJlePCSID+KZ0LdxTR2GshenAwx0239hGNXRsVUdwpLJCpG/hpaB3 i6OsvyW4b7wAQtVWJmL+vk9OJd2BZZHR3/2qBQ11DCjPl4+w+JGjB2OqF c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAHBKy1GrRDoH/2dsb2JhbABbgkVEMQG/RYEEFnSCIwEBAQMBAQEBRiULBQsLPwcnHxEGExoEh2oFDbl7jX6BTQYBgwJhA4kiilGDUoYhiySDMRw
X-IronPort-AV: E=Sophos;i="4.87,946,1363132800"; d="scan'208,217";a="84437661"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 26 Jun 2013 20:13:47 +0000
Received: from [10.32.240.195] ([10.32.240.195]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r5QKDkQm023427; Wed, 26 Jun 2013 20:13:46 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_DE18961D-A275-4E13-A3AE-46172E3E1092"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <009901ce725a$d1623360$74269a20$@unizar.es>
Date: Wed, 26 Jun 2013 13:13:46 -0700
Message-Id: <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es>
To: <jsaldana@unizar.es>
X-Mailer: Apple Mail (2.1508)
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 26 Jun 2013 20:13:54 -0000

--Apple-Mail=_DE18961D-A275-4E13-A3AE-46172E3E1092
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


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

> Question 4: Is TCM-TF interesting for the Industry? Should the IETF =
standardize this?
> =20
> Answer:
> =20
> 1) TCM-TF intends to update RFC4170, which optimizes RTP VoIP traffic. =
So if RFC4170 was interesting, why not updating it?
> =20
> 2) TCM-TF can be useful in order to save bandwidth in many cases:
> =20
> - Aggregation network of *network operators*: We are saving bandwidth =
by optimizing and putting together traffic flows. Is this interesting =
for a network operator? What about overprovisioning? The idea is that =
there are places and moments in which a number of flows based on small =
packets are in the same place and at the same moment. Then, TCM-TF can =
be applied in order to provide flexibility. We are not optimizing the =
overall Internet traffic, we are optimizing specific flows with very =
tight delay requirements, which network operators have to take care of =
in a special way.
> www.huawei.com/ilink/en/download/HW_193034
> =20
> - *End to end* optimization: Nowadays, many appliances are used to =
connect remote offices of the same company (creating a VPN). So if a =
tunnel exists, why not optimizing this traffic when possible? We would =
save bandwidth in the access network, where it can be scarce.
> =20
> - Wireless and satellite scenarios.

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



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

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

-d



> =20
> =20
> Jose
> =20
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre =
de Jose Saldana
> Enviado el: lunes, 24 de junio de 2013 13:00
> Para: tcmtf@ietf.org
> Asunto: [tcmtf] Answers to possible questions in the BOF
> =20
> I would like to start a thread about possible questions people may ask =
in the BOF. Obviously, we also need answers, so we should cooperate.
> =20
> This is different from the =93questions to ask in the BOF=94. This =
will be discussed separately.
> =20
> Thanks!
> =20
> Jose
> =20
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf


--Apple-Mail=_DE18961D-A275-4E13-A3AE-46172E3E1092
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; =
"><br><div><div>On Jun 26, 2013, at 3:49 AM, Jose Saldana &lt;<a =
href=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div lang=3D"ES" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"color: rgb(31, 73, =
125); ">Question 4: Is TCM-TF interesting for the Industry? Should the =
IETF standardize this?<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" 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); ">Answer:<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"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); ">1) TCM-TF intends to update RFC4170, =
which optimizes RTP VoIP traffic. So if RFC4170 was interesting, why not =
updating it?<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" style=3D"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); ">2) TCM-TF can be useful in order to =
save bandwidth in many cases:<o:p></o:p></span></div><div style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span lang=3D"EN-US" style=3D"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); ">- Aggregation network of *<b>network =
operators</b>*: We are saving bandwidth by optimizing and putting =
together traffic flows. Is this interesting for a network operator? What =
about overprovisioning? The idea is that there are places and moments in =
which a number of flows based on small packets are in the same place and =
at the same moment. Then, TCM-TF can be applied in order to provide =
flexibility. We are not optimizing the overall Internet traffic, we are =
optimizing specific flows with very tight delay requirements, which =
network operators have to take care of in a special =
way.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-size: 10.5pt; font-family: Arial, sans-serif; color: =
rgb(0, 153, 51); background-color: white; background-position: initial =
initial; background-repeat: initial initial; "><a =
href=3D"http://www.huawei.com/ilink/en/download/HW_193034" style=3D"color:=
 purple; text-decoration: underline; =
">www.huawei.com/ilink/en/download/HW_193034</a><o:p></o:p></span></div><d=
iv 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); ">- *<b>End to end</b>* optimization: =
Nowadays, many appliances are used to connect remote offices of the same =
company (creating a VPN). So if a tunnel exists, why not optimizing this =
traffic when possible? We would save bandwidth in the access network, =
where it can be scarce.<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US" style=3D"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); ">- Wireless and satellite =
scenarios.</span></div></div></div></blockquote><div><br></div><div>"Cisco=
 adds IP multiplexing to mobile satellite package", April 2012,&nbsp;<a =
href=3D"http://www.networkworld.com/news/2012/040912-cisco-ip-multiplexing=
-258082.html">http://www.networkworld.com/news/2012/040912-cisco-ip-multip=
lexing-258082.html</a></div><div><br></div><div><br></div><br><blockquote =
type=3D"cite"><div lang=3D"ES" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"color: rgb(31, 73, =
125); "><o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"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); ">&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); ">Any other thoughts? Any other =
scenarios in mind? Potential =
beneficiaries?</span></div></div></div></blockquote><div><br></div><div>So=
me networks, today, use cRTP (RFC2508) on their access links. &nbsp;This =
gives bandwidth savings on the access link, but consumes considerable =
CPU horsepower on the aggregation router (to perform cRTP), but provides =
no bandwidth savings across the network core. &nbsp;If, instead, the =
bandwidth could be saved on the access link, across the core, and on the =
far-end access link -- all without the CPU impact on the aggregation =
router -- it is a considerable =
win.</div><div><br></div><div>-d</div><div><br></div><div><br></div><br><b=
lockquote type=3D"cite"><div lang=3D"ES" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"color: rgb(31, 73, =
125); "><o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"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); ">&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<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US" style=3D"color: rgb(31, 73, =
125); ">&nbsp;</span></div><div style=3D"border-style: none none none =
solid; border-left-width: 1.5pt; border-left-color: blue; padding: 0cm =
0cm 0cm 4pt; "><div><div style=3D"border-style: solid none none; =
border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: =
3pt 0cm 0cm; "><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; "><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; =
">De:</span></b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a> =
[mailto:tcmtf-<a =
href=3D"mailto:bounces@ietf.org">bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b>En nombre de<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Jose =
Saldana<br><b>Envia</b></span><b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif; ">do el:</span></b><span =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span>lunes, 24 de junio de 2013 =
13:00<br><b>Para:</b><span class=3D"Apple-converted-space">&nbsp;</span><a=
 href=3D"mailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br><b>Asunto:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>[tcmtf] Answers to possible =
questions in the BOF<o:p></o:p></span></div></div></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">I would like to start a thread about possible questions =
people may ask in the BOF. Obviously, we also need answers, so we should =
cooperate.<o:p></o:p></span></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 is different from the =93questions to ask in the =
BOF=94. This will be discussed separately.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span lang=3D"EN-US">&nbsp;</span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span =
lang=3D"EN-US">Thanks!<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">Jose<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
lang=3D"EN-US">&nbsp;</span></div></div></div>____________________________=
___________________<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></body></html>=

--Apple-Mail=_DE18961D-A275-4E13-A3AE-46172E3E1092--

From Tomaso.deCola@dlr.de  Thu Jun 27 02:53:51 2013
Return-Path: <Tomaso.deCola@dlr.de>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDF1021F9CC9 for <tcmtf@ietfa.amsl.com>; Thu, 27 Jun 2013 02:53:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKbOV6Ft6-wR for <tcmtf@ietfa.amsl.com>; Thu, 27 Jun 2013 02:53:47 -0700 (PDT)
Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.33]) by ietfa.amsl.com (Postfix) with ESMTP id D947921F9A90 for <tcmtf@ietf.org>; Thu, 27 Jun 2013 02:53:46 -0700 (PDT)
Received: from DLREXHUB01.intra.dlr.de (172.21.152.130) by dlrexedge02.dlr.de (172.21.163.101) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 27 Jun 2013 11:53:38 +0200
Received: from DLREXMBX01.intra.dlr.de ([fe80::d198:77e5:d411:fccd]) by dlrexhub01.intra.dlr.de ([::1]) with mapi id 14.02.0342.003; Thu, 27 Jun 2013 11:53:43 +0200
From: <Tomaso.deCola@dlr.de>
To: <dwing@cisco.com>
Thread-Topic: [tcmtf] Answers to possible questions in the BOF
Thread-Index: Ac5wycGHbApylKz/RhmtAnL3dgONFwBgEj+AABO24AAAIL56MA==
Date: Thu, 27 Jun 2013 09:53:43 +0000
Message-ID: <1A39DCC13AF3C14B83CD74124D4DCFC316F8EFAC@DLREXMBX01.intra.dlr.de>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>
In-Reply-To: <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>
Accept-Language: it-IT, de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.247.173.215]
Content-Type: multipart/alternative; boundary="_000_1A39DCC13AF3C14B83CD74124D4DCFC316F8EFACDLREXMBX01intra_"
MIME-Version: 1.0
Cc: tcmtf@ietf.org, jsaldana@unizar.es
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 09:53:51 -0000

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

Hi Dan,

Would it be possible to have more info on this CISCO product?

Actually, nowadays satellite technology already implements multiplexing cap=
abilities to better exploit the satellite capacity. In this respect it woul=
d be interesting to understand the interaction of the CISCO multiplexing-en=
abled router and the functions already available in satellite terminals.

Thanks in advance

Regards,

Tomaso

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

From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of D=
an Wing
Sent: Wednesday, June 26, 2013 10:14 PM
To: jsaldana@unizar.es
Cc: tcmtf@ietf.org
Subject: Re: [tcmtf] Answers to possible questions in the BOF


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


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

Answer:

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

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

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

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

- Wireless and satellite scenarios.

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






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

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

-d






Jose

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

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

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

Thanks!

Jose

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


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Dan,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Would it be possible to h=
ave more info on this CISCO product?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Actually, nowadays satell=
ite technology already implements multiplexing capabilities to better explo=
it the satellite capacity. In this respect it would be interesting
 to understand the interaction of the CISCO multiplexing-enabled router and=
 the functions already available in satellite terminals.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks in advance<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Tomaso<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;;color:dimgray">&#8212;&#8212;&#8212;&#8212;&#8212;&#8212=
;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#82=
12;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</span><span style=3D"c=
olor:#1F497D">
<br>
</span><b><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&qu=
ot;sans-serif&quot;;color:dimgray">Deutsches Zentrum f=FCr Luft- und Raumfa=
hrt</span></b><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;=
,&quot;sans-serif&quot;;color:dimgray"> (DLR)</span><span style=3D"color:#1=
F497D">
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:dimgray">German Aerospace Center</span><span style=
=3D"color:#1F497D">
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:dimgray">Institute of Communications and Navigation =
| Satellite Networks | Oberpfaffenhofen | 82234 Wessling | Germany</span><s=
pan style=3D"color:#1F497D">
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:dimgray">Tomaso de Cola, Ph.D.</s=
pan></b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1F497D">
<br>
</span><span lang=3D"DE" style=3D"font-size:10.0pt;font-family:&quot;Arial&=
quot;,&quot;sans-serif&quot;;color:dimgray">Telefon &#43;49 8153 28-2156 | =
Telefax&nbsp; &#43;49 8153 28-2844 |</span><span lang=3D"DE" style=3D"font-=
size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1F4=
97D">
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D"><a href=3D"mailto:sandro.scalise@dlr.de">=
<span lang=3D"DE" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&=
quot;sans-serif&quot;">tomaso.decola@dlr.de</span></a></span><span lang=3D"=
DE" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;;color:#1F497D">
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;=
sans-serif&quot;;color:#1F497D"><a href=3D"http://www.dlr.de/kn/institut/ab=
teilungen/san"><span lang=3D"DE">http://www.dlr.de/kn/institut/abteilungen/=
san</span></a></span><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D">
<span lang=3D"DE"><o:p></o:p></span></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"DE" style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</=
o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> tcmtf-bo=
unces@ietf.org [mailto:tcmtf-bounces@ietf.org]
<b>On Behalf Of </b>Dan Wing<br>
<b>Sent:</b> Wednesday, June 26, 2013 10:14 PM<br>
<b>To:</b> jsaldana@unizar.es<br>
<b>Cc:</b> tcmtf@ietf.org<br>
<b>Subject:</b> Re: [tcmtf] Answers to possible questions in the BOF<o:p></=
o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On Jun 26, 2013, at 3:49 AM, Jose Saldana &lt;<a hre=
f=3D"mailto:jsaldana@unizar.es">jsaldana@unizar.es</a>&gt; wrote:<o:p></o:p=
></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Question 4: Is TCM-TF int=
eresting for the Industry? Should the IETF standardize this?</span><span la=
ng=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Answer:</span><span lang=
=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">1) TCM-TF intends to upda=
te RFC4170, which optimizes RTP VoIP traffic. So if RFC4170 was interesting=
, why not updating it?</span><span lang=3D"ES" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">2) TCM-TF can be useful i=
n order to save bandwidth in many cases:</span><span lang=3D"ES" style=3D"f=
ont-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">- Aggregation network of =
*<b>network operators</b>*: We are saving bandwidth by optimizing and putti=
ng together traffic flows. Is this interesting for a network
 operator? What about overprovisioning? The idea is that there are places a=
nd moments in which a number of flows based on small packets are in the sam=
e place and at the same moment. Then, TCM-TF can be applied in order to pro=
vide flexibility. We are not optimizing
 the overall Internet traffic, we are optimizing specific flows with very t=
ight delay requirements, which network operators have to take care of in a =
special way.</span><span lang=3D"ES" style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;;color:#009933;background:white"><a href=3D=
"http://www.huawei.com/ilink/en/download/HW_193034"><span style=3D"color:pu=
rple">www.huawei.com/ilink/en/download/HW_193034</span></a></span><span lan=
g=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">- *<b>End to end</b>* opt=
imization: Nowadays, many appliances are used to connect remote offices of =
the same company (creating a VPN). So if a tunnel exists,
 why not optimizing this traffic when possible? We would save bandwidth in =
the access network, where it can be scarce.</span><span lang=3D"ES" style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">- Wireless and satellite =
scenarios.</span><span lang=3D"ES" style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;Cisco adds IP multiplexing to mobile satellite=
 package&quot;, April 2012,&nbsp;<a href=3D"http://www.networkworld.com/new=
s/2012/040912-cisco-ip-multiplexing-258082.html">http://www.networkworld.co=
m/news/2012/040912-cisco-ip-multiplexing-258082.html</a><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Any other thoughts? Any o=
ther scenarios in mind? Potential beneficiaries?</span><span lang=3D"ES" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Some networks, today, use cRTP (RFC2508) on their ac=
cess links. &nbsp;This gives bandwidth savings on the access link, but cons=
umes considerable CPU horsepower on the aggregation router (to perform cRTP=
), but provides no bandwidth savings across
 the network core. &nbsp;If, instead, the bandwidth could be saved on the a=
ccess link, across the core, and on the far-end access link -- all without =
the CPU impact on the aggregation router -- it is a considerable win.<o:p><=
/o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">-d<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Jose</span><span lang=3D"=
ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;"><o:p></o:p></span></p>
</div>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De:</span></b><span class=3D"apple-co=
nverted-space"><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quo=
t;,&quot;sans-serif&quot;">&nbsp;</span></span><span style=3D"font-size:10.=
0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"><a href=3D"mailt=
o:tcmtf-bounces@ietf.org">tcmtf-bounces@ietf.org</a>
 [mailto:tcmtf-<a href=3D"mailto:bounces@ietf.org">bounces@ietf.org</a>]<sp=
an class=3D"apple-converted-space">&nbsp;</span><b>En nombre de<span class=
=3D"apple-converted-space">&nbsp;</span></b>Jose Saldana<br>
<b>Envia</b></span><b><span lang=3D"ES" style=3D"font-size:10.0pt;font-fami=
ly:&quot;Tahoma&quot;,&quot;sans-serif&quot;">do el:</span></b><span class=
=3D"apple-converted-space"><span lang=3D"ES" style=3D"font-size:10.0pt;font=
-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">&nbsp;</span></span><spa=
n lang=3D"ES" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quo=
t;sans-serif&quot;">lunes,
 24 de junio de 2013 13:00<br>
<b>Para:</b><span class=3D"apple-converted-space">&nbsp;</span><a href=3D"m=
ailto:tcmtf@ietf.org">tcmtf@ietf.org</a><br>
<b>Asunto:</b><span class=3D"apple-converted-space">&nbsp;</span>[tcmtf] An=
swers to possible questions in the BOF</span><span lang=3D"ES" style=3D"fon=
t-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>=
</o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">I would like to start a thread about po=
ssible questions people may ask in the BOF. Obviously, we also need answers=
, so we should cooperate.</span><span lang=3D"ES" style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;</span><span lang=3D"ES" style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">This is different from the &#8220;quest=
ions to ask in the BOF&#8221;. This will be discussed separately.</span><sp=
an lang=3D"ES" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;</span><span lang=3D"ES" style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Thanks!</span><span lang=3D"ES" style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;</span><span lang=3D"ES" style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Jose</span><span lang=3D"ES" style=3D"f=
ont-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;</span><span lang=3D"ES" style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><=
o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"ES" style=3D"font-size:13.5pt;font-fam=
ily:&quot;Helvetica&quot;,&quot;sans-serif&quot;">_________________________=
______________________<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">https://www.ietf.or=
g/mailman/listinfo/tcmtf</a><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_1A39DCC13AF3C14B83CD74124D4DCFC316F8EFACDLREXMBX01intra_--

From jltornos@unizar.es  Fri Jun 28 01:58:13 2013
Return-Path: <jltornos@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D10D321F842A for <tcmtf@ietfa.amsl.com>; Fri, 28 Jun 2013 01:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.714
X-Spam-Level: 
X-Spam-Status: No, score=-3.714 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JEdbO-Ez0n7X for <tcmtf@ietfa.amsl.com>; Fri, 28 Jun 2013 01:58:01 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) by ietfa.amsl.com (Postfix) with ESMTP id E6DE021F9E3F for <tcmtf@ietf.org>; Fri, 28 Jun 2013 01:57:47 -0700 (PDT)
Received: from unizar.es (piedra.unizar.es [155.210.1.18]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id r5S8vVAE023902; Fri, 28 Jun 2013 10:57:36 +0200
Received: from gtc1pc6.cps.unizar.es (gtc1pc6.cps.unizar.es [155.210.158.29]) by webmail.unizar.es (Horde MIME library) with HTTP; Fri, 28 Jun 2013 10:57:25 +0200
Message-ID: <20130628105725.lmag0xgqsgogggww@webmail.unizar.es>
Date: Fri, 28 Jun 2013 10:57:25 +0200
From: jltornos@unizar.es
To: Dan Wing <dwing@cisco.com>
References: <007e01ce70c9$fe1a0aa0$fa4e1fe0$@unizar.es> <009901ce725a$d1623360$74269a20$@unizar.es> <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>
In-Reply-To: <2543ED38-A2FF-49D7-85E0-4790A31415BC@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Internet Messaging Program (IMP) H3 (4.1.3)
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Cc: tcmtf@ietf.org, jsaldana@unizar.es
Subject: Re: [tcmtf] Answers to possible questions in the BOF
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jun 2013 08:58:14 -0000

Hi all,

Few days ago Julian talked about TCM-TF's security and now I've read =20
in the link included by Dan, saying that the gain obtained when =20
multiplexing Ipsec-encrypted packets is 20-to-1. We have been looking =20
for more information about this issue and thinking about a way to =20
reduce the needed  bandwidth in IPsec flows.

The main idea is to find a way to change the authentication of the =20
individual packets and merge all of them in a unique authentication. =20
Thus, instead of using 20 IPsec tunnels, we would have a single tunnel =20
including 20 flows. Is this something similar than how Cisco gets the =20
improvement?

Jos=E9 Luis



Dan Wing <dwing@cisco.com> ha escrito:

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



