[tcmtf] New version (v7) of TCM-TF draft

"Jose Saldana" <jsaldana@unizar.es> Tue, 10 June 2014 08:38 UTC

Return-Path: <jsaldana@unizar.es>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id B2FFF1A0329; Tue, 10 Jun 2014 01:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id MDeAaI0g9iCF; Tue, 10 Jun 2014 01:38:44 -0700 (PDT)
Received: from ortiz.unizar.es (ortiz.unizar.es []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B54CE1A0291; Tue, 10 Jun 2014 01:38:43 -0700 (PDT)
Received: from usuarioPC (gtc1pc12.cps.unizar.es []) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id s5A8ca37026081; Tue, 10 Jun 2014 10:38:36 +0200
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tcmtf@ietf.org>
Date: Tue, 10 Jun 2014 10:38:42 +0200
Message-ID: <014d01cf8487$62adea50$2809bef0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_014E_01CF8498.26386800"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac+Eh2GI8HW2AgRVTj+g1lvK0tUNGA==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Archived-At: http://mailarchive.ietf.org/arch/msg/tcmtf/r0nte72U2n0tppbmBvqE0G6C8EE
Cc: Martin Stiemerling <mls.ietf@gmail.com>, tsv-area@ietf.org, 'Spencer Dawkins' <spencerdawkins.ietf@gmail.com>, tsvwg@ietf.org
Subject: [tcmtf] New version (v7) of TCM-TF draft
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf/>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 08:38:46 -0000

Hi all.
A new version (v7) of the main TCM-TF draft has been submitted to the IETF
web page.
Tunneling Compressed Multiplexed Traffic Flows (TCM-TF) Reference Model,
Some of the improvements are:
- Stating that TCM-TF must keep backwards compatibility with RFC4170. Some
people suggested it on the last BoF, because some devices already implement
- Adding some new information about Community Networks.
- Adding the possibility of optimizing UDP traffic of Constrained RESTful
Environments (http://datatracker.ietf.org/wg/core/).
- Adding three new references.
- Slightly improving some figures.
Your comments will be welcome.
Best regards,
Jose Saldana
A new version of I-D, draft-saldana-tsvwg-tcmtf-07.txt has been successfully
submitted by Jose Saldana and posted to the IETF repository.
Name:             draft-saldana-tsvwg-tcmtf
Revision:         07
Title:                Tunneling Compressed Multiplexed Traffic Flows
(TCM-TF) Reference Model
Document date:         2014-06-10
Group:             Individual Submission
Pages:                        26
Htmlized:        <http://tools.ietf.org/html/draft-saldana-tsvwg-tcmtf-07>
   Tunneling Compressed and Multiplexed Traffic Flows (TCM-TF) is a
   method for improving the bandwidth utilization of network segments
   that carry multiple flows in parallel sharing a common path.  The
   method combines standard protocols for header compression,
   multiplexing, and tunneling over a network path for the purpose of
   reducing the bandwidth.  The amount of packets per second can also be
   This document describes the TCM-TF framework and the different
   options which can be used for each layer (header compression,
   multiplexing and tunneling).

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat