IETF Logo Mail Archive

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

"Liushucheng (Will)" <liushucheng@huawei.com> Tue, 10 June 2014 06:35 UTC

Return-Path: <liushucheng@huawei.com>
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 2BD461A03DC for <openv6@ietfa.amsl.com>; Mon, 9 Jun 2014 23:35:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.099
X-Spam-Level: *
X-Spam-Status: No, score=1.099 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_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 g7GHMWrqAJEc for <openv6@ietfa.amsl.com>; Mon, 9 Jun 2014 23:35:45 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CAC51A0402 for <Openv6@ietf.org>; Mon, 9 Jun 2014 23:35:44 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BIG30022; Tue, 10 Jun 2014 06:35:42 +0000 (GMT)
Received: from SZXEMA402-HUB.china.huawei.com (10.82.72.34) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 10 Jun 2014 07:35:39 +0100
Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.3]) by SZXEMA402-HUB.china.huawei.com ([10.82.72.34]) with mapi id 14.03.0158.001; Tue, 10 Jun 2014 14:35:28 +0800
From: "Liushucheng (Will)" <liushucheng@huawei.com>
To: Felix <felix.lu@huawei.com>, Jose Saldana <jsaldana@unizar.es>, "Openv6@ietf.org" <Openv6@ietf.org>
Thread-Topic: [Openv6] 答复: Another question: the name of the functionalities
Thread-Index: AQHPhARDmEVvI/s5XUay20kkZ4V/+5tp49jA
Date: Tue, 10 Jun 2014 06:35:27 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB5FEF75CC@SZXEMA509-MBS.china.huawei.com>
References: <00c901cf83f7$eb70c230$c2524690$@unizar.es> <4B29BA0800EE424E850D442A1A3D180340718BEA@SZXEMA510-MBX.china.huawei.com>
In-Reply-To: <4B29BA0800EE424E850D442A1A3D180340718BEA@SZXEMA510-MBX.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.78.79]
Content-Type: multipart/alternative; boundary="_000_C9B5F12337F6F841B35C404CF0554ACB5FEF75CCSZXEMA509MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/5Co0PIWPdl4J3GZ8vcLsa68Z790
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 06:35:48 -0000

+1
IMHO, this one is appropriate.

Regards,
Will (Shucheng LIU)

From: Openv6 [mailto:openv6-bounces@ietf.org] On Behalf Of Felix
Sent: Tuesday, June 10, 2014 12:39 AM
To: Jose Saldana; Openv6@ietf.org
Subject: [Openv6] 答复: Another question: the name of the functionalities


Hi all,



I prefer "Network capabilities" for grouping these actions.



Best regards!

Felix





________________________________
发件人: 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

v2.23.0 | Report a Bug | By Email