IETF Logo Mail Archive

Re: [tcmtf] What about TCM-Optimizer --- TCM-Rebuilder?

FERNANDO PASCUAL BLANCO <fpb@tid.es> Thu, 20 June 2013 08:20 UTC

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

Hi Jose,

I´m not sure about that. Optimizer and rebuilder make me think in very different things, and actually they should be very similar. I like "TCM-ingress optimizer" and "TCM-egress optimizer", couldn´t we use an acronym here?

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

Regards,

Fernando Pascual Blancouse
Telefónica 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<mailto: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@ietf.org>>
Subject: [tcmtf] What about TCM-Optimizer --- TCM-Rebuilder?

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


________________________________

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

v2.8.7 | Report a Bug | By Email