Re: [Openv6] new APONF goals based on APONF bar BOF meeting

"Jun Bi" <junbi@tsinghua.edu.cn> Thu, 24 July 2014 15:25 UTC

Return-Path: <junbi@tsinghua.edu.cn>
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 CC07B1A02E6 for <openv6@ietfa.amsl.com>; Thu, 24 Jul 2014 08:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 JnfPv-8dSKLt for <openv6@ietfa.amsl.com>; Thu, 24 Jul 2014 08:25:27 -0700 (PDT)
Received: from tsinghua.edu.cn (smtp01.tsinghua.edu.cn [166.111.204.30]) by ietfa.amsl.com (Postfix) with ESMTP id E58571A0444 for <openv6@ietf.org>; Thu, 24 Jul 2014 08:22:59 -0700 (PDT)
Received: from junbithinkpadx1 (unknown [31.133.165.28]) by app1 (Coremail) with SMTP id CsxvpgCH54TCJNFTGjmTAA--.11882S2; Thu, 24 Jul 2014 23:22:46 +0800 (CST)
From: "Jun Bi" <junbi@tsinghua.edu.cn>
To: "'Tom Taylor'" <tom.taylor.stds@gmail.com>, <karagian@cs.utwente.nl>, <openv6@ietf.org>
References: <FF1A9612A94D5C4A81ED7DE1039AB80F5D57BA9B@EXMBX24.ad.utwente.nl> <53CEE501.8020907@gmail.com>
In-Reply-To: <53CEE501.8020907@gmail.com>
Date: Thu, 24 Jul 2014 11:22:41 -0400
Message-ID: <008201cfa753$1f32a290$5d97e7b0$@tsinghua.edu.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQGAj+dtDMhzBk/dlSnVNiZwte13bgJjgIjTnDpnXMA=
Content-Language: zh-cn
X-CM-TRANSID: CsxvpgCH54TCJNFTGjmTAA--.11882S2
X-Coremail-Antispam: 1UD129KBjvJXoWxWFy7uFW5Zw43ZFW3tFy8AFb_yoW5AFW8pF WrGFn7Ga9rGr1I9w48X3Wruw1S9Fs3C3y5AwnxXw1DA3s8GF10gry3tw1YvrWDGrWfAr18 Zayj9Fy5uwn5Z3DanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU7Gb7Iv0xC_Zr1lb4IE77IF4wAFc2x0x2IEx4CE42xK8VAvwI8I cIk0rVWrJVCq3wA2ocxC64kIII0Yj41le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG64 xvF2IEw4CE5I8CrVC2j2WlYx0E74AGY7Cv6cx26w4UJr1UMcvjeVCFs4IE7xkEbVWUJVW8 JwACjcxG0xvY0x0EwIxGrwCF04k20xvY0x0EwIxGrwCF04k20xvE74AGY7Cv6cx26w4UJr 1UMI8I3I0E5I8CrVAFwI0_Jr0_Jr4lx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF 67AKxVWUXVWUAwCIc40Y0x0EwIxGrbIYCTnIWIevJa73UjIFyTuYvj7UU6C7UUUUU
X-CM-SenderInfo: xmxquxo6wvx0pjkxthxhgxhubq/
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/ZuQYVHOZTSfbYor9wUo66XBVV24
Subject: Re: [Openv6] new APONF goals based on APONF bar BOF meeting
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: Thu, 24 Jul 2014 15:25:31 -0000

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: openv6-bounces@ietf.org [mailto:openv6-bounces@ietf.org] On Behalf Of
Tom Taylor
Sent: Tuesday, July 22, 2014 6:26 PM
To: karagian@cs.utwente.nl; openv6@ietf.org
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, karagian@cs.utwente.nl 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@ietf.org
https://www.ietf.org/mailman/listinfo/openv6