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

<karagian@cs.utwente.nl> Fri, 25 July 2014 08:23 UTC

Return-Path: <karagian@cs.utwente.nl>
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 CC6821B27A2 for <openv6@ietfa.amsl.com>; Fri, 25 Jul 2014 01:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 TiOyV3DZ4bk5 for <openv6@ietfa.amsl.com>; Fri, 25 Jul 2014 01:22:57 -0700 (PDT)
Received: from out66-ams.mf.surf.net (out66-ams.mf.surf.net [145.0.1.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C56D1A00F0 for <openv6@ietf.org>; Fri, 25 Jul 2014 01:22:56 -0700 (PDT)
Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by outgoing3-ams.mf.surf.net (8.14.4/8.14.4/Debian-4) with ESMTP id s6P8ONVG004795; Fri, 25 Jul 2014 10:24:23 +0200
Received: from EXHUB02.ad.utwente.nl (130.89.4.229) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.3.181.6; Fri, 25 Jul 2014 10:22:57 +0200
Received: from EXMBX24.ad.utwente.nl ([169.254.4.146]) by EXHUB02.ad.utwente.nl ([130.89.4.229]) with mapi id 14.03.0181.006; Fri, 25 Jul 2014 10:22:53 +0200
From: karagian@cs.utwente.nl
To: junbi@tsinghua.edu.cn, tom.taylor.stds@gmail.com, openv6@ietf.org
Thread-Topic: [Openv6] new APONF goals based on APONF bar BOF meeting
Thread-Index: AQHPpfGVNYceLq0nTEaarIRZ08CjEZusinSAgAKuWYCAAT4bpQ==
Date: Fri, 25 Jul 2014 08:22:52 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F5D57C529@EXMBX24.ad.utwente.nl>
References: <FF1A9612A94D5C4A81ED7DE1039AB80F5D57BA9B@EXMBX24.ad.utwente.nl> <53CEE501.8020907@gmail.com>, <008201cfa753$1f32a290$5d97e7b0$@tsinghua.edu.cn>
In-Reply-To: <008201cfa753$1f32a290$5d97e7b0$@tsinghua.edu.cn>
Accept-Language: nl-NL, en-US
Content-Language: nl-NL
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [69.46.168.130]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Bayes-Prob: 0.0001 (Score 0, tokens from: utwente-out:default, base:default, @@RPTN)
X-CanIt-Geo: ip=130.89.5.49; country=NL; region=Provincie Overijssel; city=Enschede; latitude=52.2195; longitude=6.8912; http://maps.google.com/maps?q=52.2195,6.8912&z=6
X-CanItPRO-Stream: utwente-out:default (inherits from utwente:default, base:default)
X-Canit-Stats-ID: 0bMuwonhV - 08eb6fde8ee2 - 20140725 (trained as not-spam)
X-Scanned-By: CanIt (www . roaringpenguin . com)
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/w3PZYTWf8b03H3WnjA93gybhZTk
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 08:23:00 -0000

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