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

Qiong <bingxuere@gmail.com> Tue, 10 June 2014 10:07 UTC

Return-Path: <bingxuere@gmail.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 8EDB41A04F1 for <openv6@ietfa.amsl.com>; Tue, 10 Jun 2014 03:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 1cVG2OuLNaad for <openv6@ietfa.amsl.com>; Tue, 10 Jun 2014 03:07:07 -0700 (PDT)
Received: from mail-vc0-x230.google.com (mail-vc0-x230.google.com [IPv6:2607:f8b0:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 901B41A0041 for <Openv6@ietf.org>; Tue, 10 Jun 2014 03:07:07 -0700 (PDT)
Received: by mail-vc0-f176.google.com with SMTP id im17so7524659vcb.35 for <Openv6@ietf.org>; Tue, 10 Jun 2014 03:07:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=DHBR+RFWJdPsOy3QF68H8tlrP0SOtxhtoBm9FTPmXJQ=; b=RLpMyUrdC4I9DcIZYztDelSmzOQCARIGmwDxusTGIipSfyuPYNVAsiEVaBJR/IUJ/J iegkdL0PPgGcmgw7xqTKhb7Vnu0c9LqmAQfQo4W5pVCTl0KMecm+zcVzmMjrAChORciM GTSjV/YPFKaJi+B0hv4OeoDaWnDZchkrXJSOLectA/rwoLgMZZ1aBqiA6wFSO9Ux1A8E K+qzTGKslLpAbyR16x5YailtVQk1Ru3EIrv+jwU3LtON88KXTjZJpgG30yDrpS1OKN0Z Zr+yqSjOkAI7RjRwfpydgqF9HCFOfsHHqMx4zpZvcgCfmWBaicu+KlKsycqj6SVHTUUV oq/Q==
X-Received: by 10.52.14.130 with SMTP id p2mr26787550vdc.39.1402394826460; Tue, 10 Jun 2014 03:07:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.7.209 with HTTP; Tue, 10 Jun 2014 03:06:26 -0700 (PDT)
In-Reply-To: <012b01cf8484$5717c9c0$05475d40$@unizar.es>
References: <00c901cf83f7$eb70c230$c2524690$@unizar.es> <4B29BA0800EE424E850D442A1A3D180340718BEA@SZXEMA510-MBX.china.huawei.com> <FF1A9612A94D5C4A81ED7DE1039AB80F4F47BA7B@EXMBX23.ad.utwente.nl> <012b01cf8484$5717c9c0$05475d40$@unizar.es>
From: Qiong <bingxuere@gmail.com>
Date: Tue, 10 Jun 2014 18:06:26 +0800
Message-ID: <CAH3bfAD07ngJ3_PUaeNHozupBh6aHG4TtTujPmXEeJJF=BD7tQ@mail.gmail.com>
To: Jose Saldana <jsaldana@unizar.es>
Content-Type: multipart/alternative; boundary="20cf302d4fc67759df04fb787d78"
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/RhyYN6YnoZ68lnDI22qkdwUAPGY
Cc: karagian@cs.utwente.nl, Openv6@ietf.org
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 10:07:09 -0000

Hi Jose,

Thanks for your comment. I think network capability is a more general work
which can be applied to different scenarios. In APONF, we are focusing more
on traffic-related capabilities, so I prefer the term more specific to
"traffic".

Best wishes

-- 
==============================================
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/
<http://sourceforge.net/projects/laft6/>*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/
<http://sourceforge.net/projects/pcpportsetdemo/> *
===============================================



On Tue, Jun 10, 2014 at 4:16 PM, Jose Saldana <jsaldana@unizar.es> wrote:

> 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
> *主题**:* [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
>
>
>
> _______________________________________________
> Openv6 mailing list
> Openv6@ietf.org
> https://www.ietf.org/mailman/listinfo/openv6
>
>


-- 
==============================================
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/
<http://sourceforge.net/projects/laft6/>*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/
<http://sourceforge.net/projects/pcpportsetdemo/> *
===============================================