Re: [Openv6] regarding name of our activity and mailing list name
Tina TSOU <Tina.Tsou.Zouting@huawei.com> Mon, 28 July 2014 03:38 UTC
Return-Path: <Tina.Tsou.Zouting@huawei.com>
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 5A3871A0021 for <openv6@ietfa.amsl.com>; Sun, 27 Jul 2014 20:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dG5RlLcdbhp8 for <openv6@ietfa.amsl.com>; Sun, 27 Jul 2014 20:38:16 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C646E1A0026 for <openv6@ietf.org>; Sun, 27 Jul 2014 20:38:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BHQ67328; Mon, 28 Jul 2014 03:38:00 +0000 (GMT)
Received: from SZXEML460-HUB.china.huawei.com (10.82.67.203) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 28 Jul 2014 04:37:58 +0100
Received: from szxeml557-mbs.china.huawei.com ([169.254.6.34]) by szxeml460-hub.china.huawei.com ([10.82.67.203]) with mapi id 14.03.0158.001; Mon, 28 Jul 2014 11:37:52 +0800
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Jun Bi <junbi@tsinghua.edu.cn>
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: <34FC9348-2BE1-44AE-828E-C26DBF4A7603@huawei.com>
References: <FF1A9612A94D5C4A81ED7DE1039AB80F5D57C50E@EXMBX24.ad.utwente.nl>, <001401cfa7ea$03922910$0ab67b30$@tsinghua.edu.cn>
In-Reply-To: <001401cfa7ea$03922910$0ab67b30$@tsinghua.edu.cn>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_34FC93482BE144AE828EC26DBF4A7603huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/FxlWWehsixAwkyuEfHTXacoF_to
Cc: "andrew.qu@mediatek.com" <andrew.qu@mediatek.com>, "kireeti@juniper.net" <kireeti@juniper.net>, "karagian@cs.utwente.nl" <karagian@cs.utwente.nl>, "openv6@ietf.org" <openv6@ietf.org>
Subject: Re: [Openv6] regarding name of our activity and mailing list name
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: Mon, 28 Jul 2014 03:38:19 -0000
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" <junbi@tsinghua.edu.cn<mailto:junbi@tsinghua.edu.cn>> wrote: Then let's propose a new name of the WG. -----Original Message----- From: openv6-bounces@ietf.org<mailto:openv6-bounces@ietf.org> [mailto:openv6-bounces@ietf.org] On Behalf Of karagian@cs.utwente.nl<mailto:karagian@cs.utwente.nl> Sent: Friday, July 25, 2014 4:01 AM To: junbi@tsinghua.edu.cn<mailto:junbi@tsinghua.edu.cn>; openv6@ietf.org<mailto:openv6@ietf.org> 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: aponf@ietf.org<mailto:aponf@ietf.org> 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 [openv6-bounces@ietf.org<mailto:openv6-bounces@ietf.org>] namens Jun Bi [junbi@tsinghua.edu.cn<mailto:junbi@tsinghua.edu.cn>] Verzonden: vrijdag 25 juli 2014 1:28 Aan: openv6@ietf.org<mailto:openv6@ietf.org> Onderwerp: Re: [Openv6] new APONF goals based on APONF bar BOF meeting BTW, shall we change the name of mailing-list to aponf@ietf.org<mailto:aponf@ietf.org> ? Thanks, Jun -----Original Message----- From: Jun Bi [mailto:junbi@tsinghua.edu.cn] Sent: Thursday, July 24, 2014 7:27 PM To: 'openv6@ietf.org<mailto:openv6@ietf.org>' 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:junbi@tsinghua.edu.cn] Sent: Thursday, July 24, 2014 11:23 AM To: 'Tom Taylor'; 'karagian@cs.utwente.nl<mailto:karagian@cs.utwente.nl>'; 'openv6@ietf.org<mailto:openv6@ietf.org>' 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: openv6-bounces@ietf.org<mailto: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<mailto:karagian@cs.utwente.nl>; openv6@ietf.org<mailto: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<mailto: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<mailto:Openv6@ietf.org> https://www.ietf.org/mailman/listinfo/openv6 _______________________________________________ Openv6 mailing list Openv6@ietf.org<mailto:Openv6@ietf.org> https://www.ietf.org/mailman/listinfo/openv6 _______________________________________________ Openv6 mailing list Openv6@ietf.org<mailto:Openv6@ietf.org> https://www.ietf.org/mailman/listinfo/openv6 _______________________________________________ Openv6 mailing list Openv6@ietf.org<mailto:Openv6@ietf.org> https://www.ietf.org/mailman/listinfo/openv6
- [Openv6] regarding name of our activity and maili… karagian
- Re: [Openv6] regarding name of our activity and m… Jun Bi
- Re: [Openv6] regarding name of our activity and m… Tina TSOU
- Re: [Openv6] regarding name of our activity and m… Jun Bi
- Re: [Openv6] regarding name of our activity and m… karagian
- Re: [Openv6] regarding name of our activity and m… Liushucheng (Will)
- Re: [Openv6] regarding name of our activity and m… Ying Cheng
- Re: [Openv6] regarding name of our activity and m… Jose Saldana
- Re: [Openv6] regarding name of our activity and m… Jose Saldana
- Re: [Openv6] regarding name of our activity and m… Tina TSOU
- Re: [Openv6] regarding name of our activity and m… Jun Bi
- Re: [Openv6] regarding name of our activity and m… Ying Cheng
- Re: [Openv6] regarding name of our activity and m… Tina TSOU