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

["Liushucheng (Will)" <[e-mail]>]

+1, the shorter, the easier to remember.

Regards,
Will (Shucheng LIU)

From: Openv6 [mailto:[e-mail]] On Behalf Of [e-mail]
Sent: Tuesday, July 29, 2014 2:01 AM
To: Tina TSOU; [e-mail]
Cc: [e-mail]; [e-mail]; [e-mail]
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,

Georgios







________________________________
Van: Tina TSOU [[e-mail]]
Verzonden: maandag 28 juli 2014 5:37
Aan: Jun Bi
CC: Karagiannis, G. (EWI); [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Onderwerp: Re: [Openv6] regarding name of our activity and mailing list name
Dear Jun, Georgios et al,

How about

SUPA:
Shared Unified Policy Automation

or

PANAMA:
Polices for Application-based Network Administration & Management Automation

?


Thank you,
Tina

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



-----Original Message-----
From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] On Behalf Of
[e-mail]<mailto:[e-mail]>
Sent: Friday, July 25, 2014 4:01 AM
To: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
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:
[e-mail]<mailto:[e-mail]>
Drawback: the name contains the words "Network Functions" which might be
misleiding

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,
Georgios
________________________________________
Van: Openv6 [[e-mail]<mailto:[e-mail]>] namens Jun Bi [[e-mail]<mailto:[e-mail]>]
Verzonden: vrijdag 25 juli 2014 1:28
Aan: [e-mail]<mailto:[e-mail]>
Onderwerp: Re: [Openv6] new APONF goals based on APONF bar BOF meeting

BTW, shall we change the name of mailing-list to [e-mail]<mailto:[e-mail]> ?

Thanks,
Jun

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

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

Thanks!

Jun

-----Original Message-----
From: Jun Bi [mailto:[e-mail]]
Sent: Thursday, July 24, 2014 11:23 AM
To: 'Tom Taylor'; '[e-mail]<mailto:[e-mail]>'; '[e-mail]<mailto:[e-mail]>'
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."
To
"Network Service Systems: Systems or platforms that run the network
service."

Best Regards,
Jun Bi



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

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


On 14-07-22 05:13 PM, [e-mail]<mailto:[e-mail]> 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
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/openv6


_______________________________________________
Openv6 mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/openv6
_______________________________________________
Openv6 mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/openv6


_______________________________________________
Openv6 mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/openv6