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

Tina TSOU <> Mon, 28 July 2014 03:38 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 5A3871A0021 for <>; Sun, 27 Jul 2014 20:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dG5RlLcdbhp8 for <>; Sun, 27 Jul 2014 20:38:16 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C646E1A0026 for <>; Sun, 27 Jul 2014 20:38:14 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id BHQ67328; Mon, 28 Jul 2014 03:38:00 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Mon, 28 Jul 2014 04:37:58 +0100
Received: from ([]) by ([]) with mapi id 14.03.0158.001; Mon, 28 Jul 2014 11:37:52 +0800
From: Tina TSOU <>
To: Jun Bi <>
Thread-Topic: [Openv6] regarding name of our activity and mailing list name
Thread-Index: AQHPp96dv95X7zckz0Sl4zUQl6oeEJuv/igAgATcuh4=
Date: Mon, 28 Jul 2014 03:37:52 +0000
Message-ID: <>
References: <>, <001401cfa7ea$03922910$0ab67b30$>
In-Reply-To: <001401cfa7ea$03922910$0ab67b30$>
Accept-Language: en-US, zh-CN
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_34FC93482BE144AE828EC26DBF4A7603huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
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: Mon, 28 Jul 2014 03:38:19 -0000

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