Re: [Openv6] regarding name of our activity and mailing list name

Ying Cheng <> Thu, 31 July 2014 07:13 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 8BA801A0380 for <>; Thu, 31 Jul 2014 00:13:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 4.057
X-Spam-Level: ****
X-Spam-Status: No, score=4.057 tagged_above=-999 required=5 tests=[BAYES_50=0.8, CN_BODY_103=0.327, CN_BODY_35=0.339, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_SBL=0.141, RP_MATCHES_RCVD=-0.001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xufn1H_ldKV4 for <>; Thu, 31 Jul 2014 00:13:35 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EAC771A0375 for <>; Thu, 31 Jul 2014 00:13:33 -0700 (PDT)
Received: from ( by M10-HQ-MLOUT02.cnc.intra ( with Microsoft SMTP Server id; Thu, 31 Jul 2014 15:13:45 +0800
X-AuditID: 0a000f24-b7f7e6d000005bde-eb-53d9ec15a59e
Received: from m10-cen-mlhub03.cnc.intra ( []) by (Symantec Messaging Gateway) with SMTP id B6.44.23518.51CE9D35; Thu, 31 Jul 2014 15:11:17 +0800 (HKT)
Received: from M10-HQ-MLCH02.hq.cnc.intra ( by m10-cen-mlhub03.cnc.intra ( with Microsoft SMTP Server (TLS) id; Thu, 31 Jul 2014 15:11:17 +0800
Received: from YingCheng-PC ( by M10-HQ-MLCH02.hq.cnc.intra ( with Microsoft SMTP Server id; Thu, 31 Jul 2014 15:11:16 +0800
Date: Thu, 31 Jul 2014 15:11:08 +0800
From: Ying Cheng <>
To: "Liushucheng (Will)" <>, "" <>, Tina TSOU <>, "" <>
References: <>, <001401cfa7ea$03922910$0ab67b30$>, <>, <>
Message-ID: <>
X-mailer: Foxmail 6, 15, 201, 26 [cn]
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=====003_Dragon571561707456_====="
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCKsWRmVeSWpSXmKPExsXCxXBAW3fWm5vBBlN2KVrsX/iP3WL2sn2M FpNmbma1+LFjE7vF9ovvmS3OLVnDbHH091pWB3aPH6/Xs3q0HHnL6rFkyU8mj+tNV9k9Wk7u Z/E4/vktcwBbVJ1NYl5efkliSapCSmpxsq1ScGZ6XmJJaVGqgn9pSVJ+aV6KkkJmiq2SsZJC QU5icmpual6JrVJiQUEqUMaOSwED2ACVZeYppOYl56dk5qXbKoWGuOlaKNk9Xdb0bN6cZ00r Xk6Z+WL9+md9S59N2ZZwhSVj0QvOgh/rmCr6Zt1laWD8t4ypi5GTQ0LARKLzVzM7hC0mceHe erYuRi4OIYG9jBIn9/cwgySEBLYwSmxcVAGRWMooMaFnEwtIgkVAVeL/su9AHRwcbAK6Er3r jUBqRASOM0qs7poANolZoJtRYvPEXUwQ3b8YJdbf/A42VljAT6L/SDvYJF4BI4nvR+awQtyh KnG1rY8JYoObxP97LUwQNYISJ2c+AatnFgiW6GnfywyyWUhAXWL5LbsJjIKzkFTNQlIFYWtJ zGv4zQRhK0pM6X7IDmFrSlyZfIgdWXwBI9sqRolgJ3cLYwsDXXO95IzMvMTSvMzk/Fy95LxN jOA0wq+yg/HcKbtDjAIcjEo8vAqhZ4OFWBPLiitzDzFKcDArifC2X7sZLMSbklhZlVqUH19U mpNafIgxGeinicxSosn5wBSXVxJvaGxhYW5sbGpibGRsRpqwkjjvxH6gFQLpwHSVnZpakFoE s4WJg1OqgXH6qRq1OesXHGgOqni84Lx0zK6kD3MdxXRe9XT3z87qNNbruV3q1v2Ke2pHZ99H iehT+VPb4/ptjz7c1ert+bp3oVSnS82JdM9z2xc5/2c/smh3kqq2UWOjYtDmG6qT9HYbXD2+ bJf5xRdy3Ok7N81m5d6Zz/df07/n1pm5TALVJVLdl5842SuxFGckGmoxFxUnAgC3moB/ZwMA AA==
Cc: "" <>, "" <>, "" <>
Subject: Re: [Openv6] regarding name of our activity and mailing list name
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Openv6 discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 31 Jul 2014 07:13:38 -0000

Dear all,

Thanks for Tina's suggestion.

From my personal opinion, SUPA can better reflect our actual work.



Ying CHENG  程莹
China Unicom Network Technology Research Institute 中国联通网络技术研究院
Tel: +86-10-68799999-7702
Mobile: +86-18601102971

发件人: Liushucheng (Will) 
发送时间: 2014-07-29  14:18:01 
收件人:; Tina TSOU; 
主题: Re: [Openv6] regarding name of our activity and mailing list name 
+1, the shorter, the easier to remember.
Will (Shucheng LIU)
From: Openv6 [] On Behalf Of
Sent: Tuesday, July 29, 2014 2:01 AM
To: Tina TSOU;
Subject: Re: [Openv6] regarding name of our activity and mailing list name
Deae Tina, Dear all,
Thank you very much!
I would perefer the name SUPA, since it is representing our activity more accurately than what the name PANAMA is representing.
Best regards,

Van: Tina TSOU []
Verzonden: maandag 28 juli 2014 5:37
Aan: Jun Bi
CC: Karagiannis, G. (EWI);;;
Onderwerp: Re: [Openv6] regarding name of our activity and mailing list name
Dear Jun, Georgios et al,
How about
Shared Unified Policy Automation
Polices for Application-based Network Administration & Management Automation
Thank you,

On Jul 25, 2014, at 5:23 PM, "Jun Bi" <> wrote:
Then let's propose a new name of the WG.

-----Original Message-----
From: [] On Behalf Of
Sent: Friday, July 25, 2014 4:01 AM
Subject: [Openv6] regarding name of our activity and mailing list name

Hi Jin, Hi all,

Thank you very much for your suggestion!
There are two possible paths that we could follow:

1) Keep the name APONF and create a new mailing list with name:
Drawback: the name contains the words "Network Functions" which might be

2) Create a new name that represents the goal of this activity more
accurately than APONF and also a new mailing list that uses this new name.
Some time ago the name PANAMA had been proposed!

Please express your opinion on which of the two options we should choose?

Best regards,
Van: Openv6 [] namens Jun Bi []
Verzonden: vrijdag 25 juli 2014 1:28
Onderwerp: Re: [Openv6] new APONF goals based on APONF bar BOF meeting

BTW, shall we change the name of mailing-list to ?


-----Original Message-----
From: Jun Bi []
Sent: Thursday, July 24, 2014 7:27 PM
To: ''
Subject: RE: [Openv6] new APONF goals based on APONF bar BOF meeting

One example to use APONF for SAVI (source address validation improvements).



-----Original Message-----
From: Jun Bi []
Sent: Thursday, July 24, 2014 11:23 AM
To: 'Tom Taylor'; ''.nl'; ''
Subject: RE: [Openv6] new APONF goals based on APONF bar BOF meeting

I have a suggestion to change the terminology.

For figure 1 on page 4, the "end user application" is not a good term.

I noticed that the figure in the latest PPT from Georgios and Tina, " end
user application" was changed to "network service". I think it is good.

So one page 5 of APONF problem statement draft:

"Network Management Application: Operational Support System (OSS) like
applications that help a communication service provider to monitor, control,
analyze and manage a communication network."

Could we change " Network Management Application" to "Network Service", to
be consist with the latest figure ?

In addition, may I propose we also change "Network Management Application
System" to "Network Service System" ?

Change the definition "Network management application systems: Systems or
platforms that run the network management application."
"Network Service Systems: Systems or platforms that run the network

Best Regards,
Jun Bi

-----Original Message-----
From: [] On Behalf Of
Tom Taylor
Sent: Tuesday, July 22, 2014 6:26 PM
Subject: Re: [Openv6] new APONF goals based on APONF bar BOF meeting

Follow-up below, expressing my understanding of further details agreed last

On 14-07-22 05:13 PM, wrote:

Hi all,
To be informed!
Please note that this version is modified based on the comments that 
we received yesterday during the bar BOF meeting.

Procedurally: when a new service is defined, the Network Management (NM)
Application function downloads an initial network service graph to the NM
Control function. The data includes triggers for NM Control to feed back
updates to the graph. When one of these triggers is engaged, NM Control
sends back a refreshed network service graph.

Discussion Point 1: I am trying to relate this to SFC as a service. The
starting point is the Service Function Chain. This has to be translated into
one or more instances of a Service Function Path, which get passed to the
Service Classifier. Path derivation is logically something NM Control would
be responsible for. Which APONF function would be responsible for
distributing the path information to the Classifier(s)?

Discussion Point 2: to do its mapping between information gathered from
Network Elements (NE) and the network service graphs, NM Control needs a
database associating NE-provided attributes with service-specific labels.
Would downloading of such a dictionary be part of APONF responsibilities, or
would we leave creation of the database to be an operator-specific matter?

I stand to be corrected on my basic understanding of APONF operation, and
welcome comments on the discussion points.

Tom Taylor

Openv6 mailing list

Openv6 mailing list
Openv6 mailing list

Openv6 mailing list

If you have received this email in error please notify us immediately by e-mail. Please reply to if you want to unsubscribe from this mail. We will immediately remove your information from our sending catalogue.