Re: [tcmtf] TCMTF BOF description
Martin Stiemerling <martin.stiemerling@neclab.eu> Thu, 06 June 2013 08:56 UTC
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
- [tcmtf] TCMTF BOF description Jose Saldana
- Re: [tcmtf] TCMTF BOF description Julián Fernández-Navajas
- Re: [tcmtf] TCMTF BOF description Martin Stiemerling
- Re: [tcmtf] TCMTF BOF description Jose Saldana