Re: [Openv6] new APONF goals based on APONF bar BOF meeting
"Jun Bi" <junbi@tsinghua.edu.cn> Fri, 25 July 2014 09:21 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 DFA981A010C for <openv6@ietfa.amsl.com>; Fri, 25 Jul 2014 02:21:24 -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 q-6WNSLsxv4j for <openv6@ietfa.amsl.com>; Fri, 25 Jul 2014 02:21:22 -0700 (PDT)
Received: from tsinghua.edu.cn (smtp04.tsinghua.edu.cn [166.111.204.33]) by ietfa.amsl.com (Postfix) with ESMTP id DF3BB1A008B for <openv6@ietf.org>; Fri, 25 Jul 2014 02:21:21 -0700 (PDT)
Received: from junbithinkpadx1 (unknown [206.47.221.210]) by app3 (Coremail) with SMTP id DMxvpgDnl6iEIdJTK3mDAA--.13353S2; Fri, 25 Jul 2014 17:21:11 +0800 (CST)
From: Jun Bi <junbi@tsinghua.edu.cn>
To: karagian@cs.utwente.nl, tom.taylor.stds@gmail.com, openv6@ietf.org
References: <FF1A9612A94D5C4A81ED7DE1039AB80F5D57BA9B@EXMBX24.ad.utwente.nl> <53CEE501.8020907@gmail.com>, <008201cfa753$1f32a290$5d97e7b0$@tsinghua.edu.cn> <FF1A9612A94D5C4A81ED7DE1039AB80F5D57C529@EXMBX24.ad.utwente.nl>
In-Reply-To: <FF1A9612A94D5C4A81ED7DE1039AB80F5D57C529@EXMBX24.ad.utwente.nl>
Date: Fri, 25 Jul 2014 05:21:06 -0400
Message-ID: <001301cfa7e9$c56653f0$5032fbd0$@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/dlSnVNiZwte13bgJjgIjTAeTdw1ICT1RVVJwZ9hEQ
Content-Language: zh-cn
X-CM-TRANSID: DMxvpgDnl6iEIdJTK3mDAA--.13353S2
X-Coremail-Antispam: 1UD129KBjvJXoWxCFWrCw45WrW3uw15CFy3Arb_yoWrXw1xpF WrJrn7Ca9rGr10kw4kX3WF9w1j9FZ7G3y5JwnxXw1DA3s8GF18KryUtw1YvrZ8Gry3Ar18 ZFWj9Fy5uwn5ZrDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU2ab7Iv0xC_Cr1lb4IE77IF4wAFc2x0x2IEx4CE42xK8VAvwI8I cIk0rVWrJVCq3wA2ocxC64kIII0Yj41le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG64 xvF2IEw4CE5I8CrVC2j2WlYx0E74AGY7Cv6cx26w4UJr1UMcvjeVCFs4IE7xkEbVWUJVW8 JwACjcxG0xvY0x0EwIxGrwCY02Avz4vE174l42xK82IYc2Ij64vIr41l42xK82IY6x8Erc xFaVAv8VWkJr1UJwC20s026c02F40E14v26r1j6r18MI8I3I0E7480Y4vE14v26r106r1r MI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij64vIr4UvcSsGvfC2KfnxnUUI43ZEXa7xUU eRrUUUUUU==
X-CM-SenderInfo: xmxquxo6wvx0pjkxthxhgxhubq/
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/Sb1EQ3PSP2H8AMKRrv6dnX0qIZA
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: Fri, 25 Jul 2014 09:21:25 -0000
Thank you very much! Jun -----Original Message----- From: openv6-bounces@ietf.org [mailto:openv6-bounces@ietf.org] On Behalf Of karagian@cs.utwente.nl Sent: Friday, July 25, 2014 4:23 AM To: junbi@tsinghua.edu.cn; tom.taylor.stds@gmail.com; openv6@ietf.org Subject: Re: [Openv6] new APONF goals based on APONF bar BOF meeting Hi Ji, Than ks for your suggestions! We will change the following terms: Network Management Application" to "Network Service" Network Management Application System" to "Network Service System" Best regards, Georgios ________________________________________ Van: Jun Bi [junbi@tsinghua.edu.cn] Verzonden: donderdag 24 juli 2014 17:22 Aan: 'Tom Taylor'; Karagiannis, G. (EWI); openv6@ietf.org Onderwerp: 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: 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 _______________________________________________ Openv6 mailing list Openv6@ietf.org https://www.ietf.org/mailman/listinfo/openv6
- [Openv6] new APONF goals based on APONF bar BOF m… karagian
- Re: [Openv6] new APONF goals based on APONF bar B… Tom Taylor
- Re: [Openv6] new APONF goals based on APONF bar B… Jun Bi
- Re: [Openv6] new APONF goals based on APONF bar B… Jun Bi
- Re: [Openv6] new APONF goals based on APONF bar B… Jun Bi
- Re: [Openv6] new APONF goals based on APONF bar B… karagian
- Re: [Openv6] new APONF goals based on APONF bar B… Jun Bi