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

Tina TSOU <Tina.Tsou.Zouting@huawei.com> Tue, 19 August 2014 10:01 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 48F5B1A888E for <openv6@ietfa.amsl.com>; Tue, 19 Aug 2014 03:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.958
X-Spam-Level:
X-Spam-Status: No, score=0.958 tagged_above=-999 required=5 tests=[BAYES_50=0.8, CN_BODY_103=0.327, CN_BODY_35=0.339, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] 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 xtmulVW8yzen for <openv6@ietfa.amsl.com>; Tue, 19 Aug 2014 03:01:30 -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 E481D1A888C for <openv6@ietf.org>; Tue, 19 Aug 2014 03:01:28 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BIK04537; Tue, 19 Aug 2014 10:01:21 +0000 (GMT)
Received: from SZXEML419-HUB.china.huawei.com (10.82.67.158) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 19 Aug 2014 11:01:20 +0100
Received: from szxeml557-mbs.china.huawei.com ([169.254.6.44]) by szxeml419-hub.china.huawei.com ([10.82.67.158]) with mapi id 14.03.0158.001; Tue, 19 Aug 2014 18:01:15 +0800
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Ying Cheng <chengying10@chinaunicom.cn>
Thread-Topic: Re: RE: [Openv6] regarding name of our activity and mailing list name
Thread-Index: AQHPusj2XhF7pzdoOUegB/FMIZtzXZvWHHvugAGQo5A=
Date: Tue, 19 Aug 2014 10:01:15 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A8184C860D@szxeml557-mbs.china.huawei.com>
References: <FF1A9612A94D5C4A81ED7DE1039AB80F5D57C50E@EXMBX24.ad.utwente.nl>, <001401cfa7ea$03922910$0ab67b30$@tsinghua.edu.cn>, <34FC9348-2BE1-44AE-828E-C26DBF4A7603@huawei.com>, <FF1A9612A94D5C4A81ED7DE1039AB80F5D57CDDC@EXMBX24.ad.utwente.nl>, <201407311511083630083@chinaunicom.cn>, <000001cfac9b$df207b70$9d617250$@unizar.es>, <492274AF-4404-4E44-BEE1-044B271E18DD@huawei.com>, <201408181742181824567@chinaunicom.cn> <201408181742479153148@chinaunicom.cn>
In-Reply-To: <201408181742479153148@chinaunicom.cn>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.87.91]
Content-Type: multipart/alternative; boundary="_000_C0E0A32284495243BDE0AC8A066631A8184C860Dszxeml557mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/AkOuAFmbNI60JQEjqW33q9IC2wI
Cc: "openv6@ietf.org" <openv6@ietf.org>, "kireeti@juniper.net" <kireeti@juniper.net>, 'Jose Saldana' <jsaldana@unizar.es>, 'Jun Bi' <junbi@tsinghua.edu.cn>, "karagian@cs.utwente.nl" <karagian@cs.utwente.nl>, "spencerdawkins.ietf@gmail.com" <spencerdawkins.ietf@gmail.com>, "andrew.qu@mediatek.com" <andrew.qu@mediatek.com>
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: Tue, 19 Aug 2014 10:01:34 -0000

Dear Ying et al,

Thank you for asking.

As far as I know, the mail administrators are working with Spencer and IETF secretary to create supa@ietf.org<mailto:supa@ietf.org>, auto subscribe everyone in openv6@ietf.org<mailto:openv6@ietf.org> to the new list, and also copy the mail archieves to there. Pls stay tuned.

Regarding the protocol specs, I’m aware that people like Georgios, Luis, Will, Jun, Kireeti, Andrew, Juergen, JF et al are discussing offline about the Network Model for a programmable interface to virtual links:
Describe the network configuration.
Describe the layer 0-7 network topology, including the relationship between intra-layer and inter-layer connections.

It would be good if they could bring some discussion to the mailing list for broader audience.


Thank you,
Tina
________________________________
发件人: Ying Cheng
发送时间: 2014-08-18 17:42:18
收件人: Jun Bi; 'Tina TSOU'; 'Jose Saldana'; 'spencer dawkins'
抄送: kireeti@juniper.net<mailto:kireeti@juniper.net>; andrew.qu@mediatek.com<mailto:andrew.qu@mediatek.com>; openv6@ietf.org<mailto:openv6@ietf.org>; 'Liushucheng (Will)'; karagian@cs.utwente.nl<mailto:karagian@cs.utwente.nl>
主题: Re: RE: [Openv6] regarding name of our activity and mailing list name

Dear all,

I am not sure whether I have captured all the points.

Shall we subscribe the new email reflector supa@ietf.org<mailto:supa@ietf.org>?  Additionally, what are the possible protocol specifications for SUPA?

Thanks and best regards,
Ying



2014-08-18
________________________________
Ying CHENG  程莹
China Unicom Network Technology Research Institute 中国联通网络技术研究院
Tel: +86-10-68799999-7702
Mobile: +86-18601102971
________________________________
发件人: Jun Bi
发送时间: 2014-08-04  15:57:10
收件人: 'Tina TSOU'; 'Jose Saldana'; 'spencer dawkins'
抄送: Ying Cheng(联通集团联通网络技术研究院); kireeti@juniper.net<mailto:kireeti@juniper.net>; andrew.qu@mediatek.com<mailto:andrew.qu@mediatek.com>; openv6@ietf.org<mailto:openv6@ietf.org>; 'Liushucheng (Will)'; karagian@cs.utwente.nl<mailto:karagian@cs.utwente.nl>
主题: RE: [Openv6] regarding name of our activity and mailing list name
Good.

Thanks,
Jun

From: openv6-bounces@ietf.org<mailto:openv6-bounces@ietf.org> [mailto:openv6-bounces@ietf.org] On Behalf Of Tina TSOU
Sent: Monday, August 4, 2014 2:42 PM
To: Jose Saldana; spencer dawkins
Cc: Ying Cheng; kireeti@juniper.net<mailto:kireeti@juniper.net>; andrew.qu@mediatek.com<mailto:andrew.qu@mediatek.com>; openv6@ietf.org<mailto:openv6@ietf.org>; Liushucheng (Will); junbi@tsinghua.edu.cn<mailto:junbi@tsinghua.edu.cn>; karagian@cs.utwente.nl<mailto:karagian@cs.utwente.nl>
Subject: Re: [Openv6] regarding name of our activity and mailing list name

Dear all,

It seems that the consensus is to change openv6@ietf.org<mailto:openv6@ietf.org> to supa@ietf.org<mailto:supa@ietf.org>.


Dear Spencer,

Would you help to get it done?


Thank you,
Tina

On Jul 31, 2014, at 4:46 PM, "Jose Saldana" <jsaldana@unizar.es<mailto:jsaldana@unizar.es>> wrote:
+1

Jose

De: Openv6 [mailto:openv6-bounces@ietf.org] En nombre de Ying Cheng
Enviado el: jueves, 31 de julio de 2014 9:11
Para: Liushucheng (Will); karagian@cs.utwente.nl<mailto:karagian@cs.utwente.nl>; Tina TSOU; junbi@tsinghua.edu.cn<mailto:junbi@tsinghua.edu.cn>
CC: andrew.qu@mediatek.com<mailto:andrew.qu@mediatek.com>; kireeti@juniper.net<mailto:kireeti@juniper.net>; openv6@ietf.org<mailto:openv6@ietf.org>
Asunto: Re: [Openv6] regarding name of our activity and mailing list name

Dear all,

Thanks for Tina's suggestion.

From my personal opinion, SUPA can better reflect our actual work.

BR,
Ying




2014-07-31
________________________________
Ying CHENG  程莹
China Unicom Network Technology Research Institute 中国联通网络技术研究院
Tel: +86-10-68799999-7702
Mobile: +86-18601102971
________________________________
发件人: Liushucheng (Will)
发送时间: 2014-07-29  14:18:01
收件人: karagian@cs.utwente.nl<mailto:karagian@cs.utwente.nl>; Tina TSOU; junbi@tsinghua.edu.cn<mailto:junbi@tsinghua.edu.cn>
抄送: andrew.qu@mediatek.com<mailto:andrew.qu@mediatek.com>; kireeti@juniper.net<mailto:kireeti@juniper.net>; openv6@ietf.org<mailto:openv6@ietf.org>
主题: Re: [Openv6] regarding name of our activity and mailing list name
+1, the shorter, the easier to remember.

Regards,
Will (Shucheng LIU)

From: Openv6 [mailto:openv6-bounces@ietf.org] On Behalf Of karagian@cs.utwente.nl<mailto:karagian@cs.utwente.nl>
Sent: Tuesday, July 29, 2014 2:01 AM
To: Tina TSOU; junbi@tsinghua.edu.cn<mailto:junbi@tsinghua.edu.cn>
Cc: andrew.qu@mediatek.com<mailto:andrew.qu@mediatek.com>; kireeti@juniper.net<mailto:kireeti@juniper.net>; openv6@ietf.org<mailto:openv6@ietf.org>
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 [Tina.Tsou.Zouting@huawei.com<mailto:Tina.Tsou.Zouting@huawei.com>]
Verzonden: maandag 28 juli 2014 5:37
Aan: Jun Bi
CC: Karagiannis, G. (EWI); openv6@ietf.org<mailto:openv6@ietf.org>; andrew.qu@mediatek.com<mailto:andrew.qu@mediatek.com>; kireeti@juniper.net<mailto:kireeti@juniper.net>
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" <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

如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到hqs-spmc@chinaunicom.cn<mailto:hqs-spmc@chinaunicom.cn>,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc@chinaunicom.cn<mailto:hqs-spmc@chinaunicom.cn> if you want to unsubscribe from this mail. We will immediately remove your information from our sending catalogue.

如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到hqs-spmc@chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc@chinaunicom.cn<mailto:hqs-spmc@chinaunicom.cn> if you want to unsubscribe from this mail. We will immediately remove your information from our sending catalogue.