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

"Jun Bi" <junbi@tsinghua.edu.cn> Mon, 28 July 2014 03:44 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 5D1031A0035 for <openv6@ietfa.amsl.com>; Sun, 27 Jul 2014 20:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 VR3MHFFApIh3 for <openv6@ietfa.amsl.com>; Sun, 27 Jul 2014 20:44:21 -0700 (PDT)
Received: from tsinghua.edu.cn (smtp03.tsinghua.edu.cn [166.111.204.32]) by ietfa.amsl.com (Postfix) with ESMTP id 6B92F1A0021 for <openv6@ietf.org>; Sun, 27 Jul 2014 20:44:20 -0700 (PDT)
Received: from junbithinkpadx1 (unknown [221.194.157.104]) by app6 (Coremail) with SMTP id D8xvpgBHKDHyxtVTJSEPAA--.997S2; Mon, 28 Jul 2014 11:43:46 +0800 (CST)
From: Jun Bi <junbi@tsinghua.edu.cn>
To: 'Tina TSOU' <Tina.Tsou.Zouting@huawei.com>
References: <FF1A9612A94D5C4A81ED7DE1039AB80F5D57C50E@EXMBX24.ad.utwente.nl>, <001401cfa7ea$03922910$0ab67b30$@tsinghua.edu.cn> <34FC9348-2BE1-44AE-828E-C26DBF4A7603@huawei.com>
In-Reply-To: <34FC9348-2BE1-44AE-828E-C26DBF4A7603@huawei.com>
Date: Mon, 28 Jul 2014 11:43:40 +0800
Message-ID: <003f01cfaa16$1f7c3570$5e74a050$@tsinghua.edu.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0040_01CFAA59.2DA541D0"
X-Mailer: Microsoft Outlook 15.0
thread-index: AQKdxjkxjd63G3/X0BY6SjptBbiW0gHUUtDXAk2QLnuZ95CcMA==
Content-Language: zh-cn
X-CM-TRANSID: D8xvpgBHKDHyxtVTJSEPAA--.997S2
X-Coremail-Antispam: 1UD129KBjvJXoWxKFy7Jw15tFW5uw4DJr4DCFg_yoW7tr4Dpr WrJrnrCa9rJr1Ikw4kXw10vw1j9rZ5J3y3JwnxJw1DAF98GF18Kryjyw1YvrW5Gry5Jr18 ZFWj9F15Cw1fZrDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUIKb7Iv0xC_Cr1lb4IE77IF4wAFc2x0x2IEx4CE42xK8VAvwI8I cIk0rVWrJVCq3wA2ocxC64kIII0Yj41le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG67 k08I80eVW8JVW5JwAqx4xG6c804VAFz4xC04v7Mc02F40Ew4AK048IF2xKxVWUJVW8JwAq x4xG6xAIxVCFxsxG0wAv7VCjz48v1sIEY20_Kr1UJr1lOx8S6xCaFVCjc4AY6r1j6r4UM4 x0Y48IcxkI7VAKI48JMx8GjcxK6IxK0xIIj40E5I8CrwCY02Avz4vE14v_Gr4l42xK82IY c2Ij64vIr41l42xK82IY6x8ErcxFaVAv8VWkJr1UJwC20s026c02F40E14v26r106r1rMI 8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_JF0_Jw1lIxkGc2Ij64vIr4Uv cSsGvfC2KfnxnUUI43ZEXa7xUUeENUUUUUU==
X-CM-SenderInfo: xmxquxo6wvx0pjkxthxhgxhubq/
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/Fr7e-0nWFgBxKxPI1OJ7DlEPEDk
Cc: andrew.qu@mediatek.com, kireeti@juniper.net, karagian@cs.utwente.nl, 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:44:24 -0000

Both are good for me.

 

Thanks,

Jun

 

From: openv6-bounces@ietf.org [mailto:openv6-bounces@ietf.org] On Behalf Of
Tina TSOU
Sent: Monday, July 28, 2014 11:38 AM
To: Jun Bi
Cc: andrew.qu@mediatek.com; kireeti@juniper.net; karagian@cs.utwente.nl;
openv6@ietf.org
Subject: 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