Re: [tcmtf] TCMTF-Feedback about a possible BoF in London

FERNANDO PASCUAL BLANCO <> Thu, 09 January 2014 17:50 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 59BB31AE2B9; Thu, 9 Jan 2014 09:50:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.025
X-Spam-Status: No, score=-4.025 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, ONE_TIME=0.714, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iUK2WIdAV5gc; Thu, 9 Jan 2014 09:50:19 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 869471ADF6D; Thu, 9 Jan 2014 09:50:15 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet []) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MZ500HNEAVCXV@tid.hi.inet>; Thu, 09 Jan 2014 18:50:00 +0100 (MET)
Received: from vanvan (vanvan.hi.inet []) by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id AD.2F.02810.841EEC25; Thu, 09 Jan 2014 18:50:00 +0100 (CET)
Received: from (mailhost.hi.inet []) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MZ500HMYAVBXV@tid.hi.inet>; Thu, 09 Jan 2014 18:50:00 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([]) by EX10-HTCAS7-MAD.hi.inet ([::1]) with mapi id 14.03.0158.001; Thu, 09 Jan 2014 18:49:59 +0100
Date: Thu, 09 Jan 2014 17:49:59 +0000
In-reply-to: <>
X-Originating-IP: []
To: Jose Saldana <>
Message-id: <>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_g8g+2DCVqy5h+Mk75LOgvw)"
Content-language: en-US
Accept-Language: en-US, es-ES
Thread-topic: [tcmtf] TCMTF-Feedback about a possible BoF in London
Thread-index: Ac79ZUO9+o1eWvDOTZW4bKGOX0YCWwLjYMDQAPUFvwAAAVukgAAjn8+A
X-AuditID: 0a5f4e69-b7f9b8e000000afa-e0-52cee148b833
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGIsWRmVeSWpSXmKPExsXCFe9nqOvx8FyQwbbvvBa7Pm9gtFjwZjGz A5PHkiU/mQIYo7hsUlJzMstSi/TtErgyVix8yF7w7xFTxbs7QQ2M63cwdTFycEgImEg865To YuQEMsUkLtxbzwZiCwlsY5R4eFMAwn7KKLFlh1EXIxeQPZNRovf4dSaQBIuAqsSk5Q+ZQWw2 AS2J03dXsYDYwgJOEsseP2ABmc8pYCfxb0YpxHwFiT/nHoOViAC1Lj37mwlkJrPAR0aJ/rPX GUESvAKWErt2vWGCsAUlfky+B9bALBAtcWX6NChbXKK59SaYzSggK/Fu/nxWiKHOEicPvmEG 2Ssi4CZx/rc5xF4BiSV7zjND2KISLx//Y4X45TajxO7p75knMIrNQrJuFpJ1s5Csg7ANJN6f m88MYWtLLFv4GsrWl9j45SwjhG0msa1zB4qaBYwcqxjFipOKMtMzSnITM3PSDYz0MjL1MvNS SzYxQuIycwfj8p0qhxgFOBiVeHhXFJ8NEmJNLCuuzD3EKMHBrCTCu+biuSAh3pTEyqrUovz4 otKc1OJDjEwcnFINjHZek58LnHU+pClq+C/6+JbA8m+vzGaKKTXMWVB3pVzPqdC1+PRUPi6x v/+1V4TsPrYnwWNJjcu7AM4nh2RXz/Vu/8C+gsnrkkTkwqQvt+Ovx+m+DG8s1gm5/71Q0P/W b+Xmjw3VfxYmeUzb42QT9fu9+THp36ue3a0QnHOdd0LSlBdJhxcIVyixFGckGmoxFxUnAgC/ rr2uqQIAAA==
References: <00c401cefd65$6e8ef570$4bace050$> <> <004701cf0ccf$4d5826a0$e80873e0$> <>
Cc: "" <>, Tina TSOU <>, "Black, David" <>, "" <>, Luigi Iannone <>, Martin Stiemerling <>
Subject: Re: [tcmtf] TCMTF-Feedback about a possible BoF in London
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 Jan 2014 17:50:26 -0000

Hi all,

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


On 09/01/2014, at 01:49, Tina TSOU <<>> wrote:

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

Due to the need of interactivity, many of these services use small packets (some tens of bytes), since they have to send frequent updates between the extremes of the communication. Their small data payloads 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.

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

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

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

As a result, the next objectives can be achieved:

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

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

Thank you,

On Jan 8, 2014, at 4:11 PM, "Jose Saldana" <<>> wrote:

Hi all.

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

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

These are the improvements of version 10 with respect to v9 (

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



De: Black, David []
Enviado el: sábado, 04 de enero de 2014 4:05
Para: Jose Saldana;<>;<>
CC: Martin Stiemerling; Black, David
Asunto: RE: TCMTF-Feedback about a possible BoF in London

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

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

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

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

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

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

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

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


From: tsv-area [] On Behalf Of Jose Saldana
Sent: Friday, December 20, 2013 4:26 AM
Cc: Martin Stiemerling
Subject: TCMTF-Feedback about a possible BoF in London

Hi all,

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

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

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

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

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

The new charter is here:
This is the old one (presented in Berlin):

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

The main improvements are:

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

- The improvements of the charter are summarized here:

Best regards,


tcmtf mailing list<>


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: