IETF Logo Mail Archive

Re: [tcmtf] Improved version of the tmctf Draft charter (v6)

Mirko Sužnjević <Mirko.Suznjevic@fer.hr> Wed, 26 June 2013 08:35 UTC

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

I am maybe a little late, but i agree with this terminology.
Mirko

-----Original Message-----
From: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] On Behalf Of José Ruiz
Sent: Monday, June 17, 2013 12:39 PM
To: tcmtf@ietf.org
Subject: Re: [tcmtf] Improved version of the tmctf Draft charter (v6)

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
>>>
>>>

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

v2.8.7 | Report a Bug | By Email