Re: [Openv6] 答复: Another question: the name of the functionalities

<karagian@cs.utwente.nl> Tue, 10 June 2014 20:57 UTC

Return-Path: <karagian@cs.utwente.nl>
X-Original-To: openv6@ietfa.amsl.com
Delivered-To: openv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9122D1A0439 for <openv6@ietfa.amsl.com>; Tue, 10 Jun 2014 13:57:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.351
X-Spam-Level: ***
X-Spam-Status: No, score=3.351 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ntpCLT1TijIF for <openv6@ietfa.amsl.com>; Tue, 10 Jun 2014 13:57:29 -0700 (PDT)
Received: from out45-ams.mf.surf.net (out45-ams.mf.surf.net [145.0.1.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD3C11A02F4 for <Openv6@ietf.org>; Tue, 10 Jun 2014 13:57:28 -0700 (PDT)
Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by outgoing2-ams.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s5AKvPD4008110; Tue, 10 Jun 2014 22:57:25 +0200
Received: from EXHUB01.ad.utwente.nl (130.89.4.228) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.3.181.6; Tue, 10 Jun 2014 22:57:27 +0200
Received: from EXMBX23.ad.utwente.nl ([169.254.3.152]) by EXHUB01.ad.utwente.nl ([130.89.4.228]) with mapi id 14.03.0181.006; Tue, 10 Jun 2014 22:57:25 +0200
From: karagian@cs.utwente.nl
To: jsaldana@unizar.es, Openv6@ietf.org
Thread-Topic: [Openv6] 答复: Another question: the name of the functionalities
Thread-Index: AQHPhAFf83E1b7HQf0OHVP2zV0TTNptpCewzgADVNwCAAOphYA==
Date: Tue, 10 Jun 2014 20:57:24 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F4F47BF5C@EXMBX23.ad.utwente.nl>
References: <00c901cf83f7$eb70c230$c2524690$@unizar.es>, <4B29BA0800EE424E850D442A1A3D180340718BEA@SZXEMA510-MBX.china.huawei.com> <FF1A9612A94D5C4A81ED7DE1039AB80F4F47BA7B@EXMBX23.ad.utwente.nl>, <012b01cf8484$5717c9c0$05475d40$@unizar.es>
In-Reply-To: <012b01cf8484$5717c9c0$05475d40$@unizar.es>
Accept-Language: nl-NL, en-US
Content-Language: nl-NL
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [86.91.134.3]
Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F47BF5CEXMBX23adutwent_"
MIME-Version: 1.0
X-Bayes-Prob: 0.0001 (Score 0, tokens from: utwente-out:default, base:default, @@RPTN)
X-CanIt-Geo: ip=130.89.5.49; country=NL; region=Provincie Overijssel; city=Enschede; latitude=52.2195; longitude=6.8912; http://maps.google.com/maps?q=52.2195,6.8912&z=6
X-CanItPRO-Stream: utwente-out:default (inherits from utwente:default, base:default)
X-Canit-Stats-ID: 0vMcIVpwv - a37f91f050a9 - 20140610 (trained as not-spam)
X-Scanned-By: CanIt (www . roaringpenguin . com)
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/RlWXG-sFZb7mCWTQYGGE1NKx9_A
Subject: Re: [Openv6] 答复: Another question: the name of the functionalities
X-BeenThere: openv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Openv6 discussion list <openv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openv6>, <mailto:openv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/openv6/>
List-Post: <mailto:openv6@ietf.org>
List-Help: <mailto:openv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openv6>, <mailto:openv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 20:57:31 -0000

Hi Jose,



Thank you very much!

I agree with you that the used terminology in all drafts needs to be clear!

A better terminology section will be included in a next version of the problelmet statement draft!

However, please note that what I meant in the previous email is that it is difficult and it is not needed to find only one term/name that incorporates all the capabilities that have an impact on APONF.



In order to be clear we need to list all the capabilities (not only an aggregated one) that have an impact on the mechanisms and solutions that will be worked out by APONF.



Best regards,

Georgios



________________________________
Van: Jose Saldana [jsaldana@unizar.es]
Verzonden: dinsdag 10 juni 2014 10:16
Aan: Karagiannis, G. (EWI); Openv6@ietf.org
Onderwerp: RE: [Openv6] 答复: Another question: the name of the functionalities

Hi, Georgios. My idea is: the IETF is a standardization body, so the terms do matter. One has to be consistent and to clearly establish a “glossary of terms” to be used always the same way.

In addition, it could be a very good exercise to try to summarize the objective of APONF in a single sentence. Something like this (from the draft charter):

“The main goal of APONF is to specify the application-based policy protocol(s), mechanisms and models required  by transport applications to easily, accurately, and efficiently select and use the available communication network capabilities, i.e., network management and/or traffic policies.”

So here Tina talks about “network management and/or traffic policies.”


Jose

De: karagian@cs.utwente.nl [mailto:karagian@cs.utwente.nl]
Enviado el: lunes, 09 de junio de 2014 19:38
Para: jsaldana@unizar.es; Openv6@ietf.org
Asunto: RE: [Openv6] 答复: Another question: the name of the functionalities


Hi Jose,



Thanks for the comments!
It is somehow difficult to find the right name for all these terms, since these capabilities can be network management capabilities, traffic conditioning capabilities, traffic routiong capabilities, etc.



I am not sure if it is needed to find just one name for these terms!



Best regards,

Georgios





________________________________
发件人: Openv6 [openv6-bounces@ietf.org] 代表 Jose Saldana [jsaldana@unizar.es]
发送时间: 2014年6月9日 23:31
收件人: Openv6@ietf.org<mailto:Openv6@ietf.org>
主题: [Openv6] Another question: the name of the functionalities
Hi,

Another question is how to name the set of functionalities you are considering in APONF:

- In the first paragraph, they are called “traffic capabilities”: “ the communication network to apply the following different network management and/or traffic capabilities”

- Later, they are called “traffic policies”: “Examples of such network management and traffic policies that are considered by APONF are the following”


I think that finding a good name grouping these actions is crucial:

Manage dynamically network semantics
Orchestrate dynamically virtualized functions
Permit or Block or Redirect the traffic
Log the traffic
Copy the traffic
Set the traffic
Mark the traffic

Are they traffic policies? Network actions? Network functionalities? Network capabilities? Traffic capabilities? Network management actions?


What do you think?

Jose Saldana