Re: [Openv6] [Aeon] Next step, IETF 90?

Tina TSOU <Tina.Tsou.Zouting@huawei.com> Thu, 03 July 2014 04:08 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 09CE21A0370; Wed, 2 Jul 2014 21:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level:
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 I0ITM9H4sUUu; Wed, 2 Jul 2014 21:08:22 -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 3AAA51A01DD; Wed, 2 Jul 2014 21:08:21 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJN24909; Thu, 03 Jul 2014 04:08:19 +0000 (GMT)
Received: from SZXEML407-HUB.china.huawei.com (10.82.67.94) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 3 Jul 2014 05:08:18 +0100
Received: from szxeml557-mbs.china.huawei.com ([169.254.6.34]) by szxeml407-hub.china.huawei.com ([10.82.67.94]) with mapi id 14.03.0158.001; Thu, 3 Jul 2014 12:08:14 +0800
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Reinaldo Penno <rapenno@gmail.com>
Thread-Topic: [Aeon] Next step, IETF 90?
Thread-Index: Ac+UZitwzhnDUsdiSuWIYkG5NbmJTgBTq+wAABJ+XFH//6wDAP/+070Q
Date: Thu, 3 Jul 2014 04:08:14 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A8183D6C82@szxeml557-mbs.china.huawei.com>
References: <EA4C43BE752A194597B002779DF69BAE23B3DD5C@ESESSMB303.ericsson.se> <00bb01cf95f7$e9ef2b60$bdcd8220$@chinamobile.com> <33687996-B978-4CC8-891C-0917907EC089@huawei.com> <CAKEbE1ZXgxd+ANkrjFeEi5pYTOMcf-tVHmNuKBSK65pzRi=3Kg@mail.gmail.com>
In-Reply-To: <CAKEbE1ZXgxd+ANkrjFeEi5pYTOMcf-tVHmNuKBSK65pzRi=3Kg@mail.gmail.com>
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_C0E0A32284495243BDE0AC8A066631A8183D6C82szxeml557mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/FIBA-IfzfwiJV8tUNIDYFvh10QY
Cc: Szilveszter Nadas <Szilveszter.Nadas@ericsson.com>, "aeon@ietf.org" <aeon@ietf.org>, "Fan, Peng" <fanpeng@chinamobile.com>, "Openv6@ietf.org" <Openv6@ietf.org>
Subject: Re: [Openv6] [Aeon] Next step, IETF 90?
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: Thu, 03 Jul 2014 04:08:28 -0000

Dear Reinaldo, Michael et al,

Good catch!

I just pulled things together into a charter, while talking to the proponents, below was what I understood.

Regarding SFC/SFP in the charter, the original idea was to make use of this concept to describe network topology and traffic path. However, this obviously brought confusion. What APONF needs is, for example, a distributed data center application (traffic engineering between data centers) may need the network topology and traffic path, so it can require the APONF to re-configure the related network nodes of the path to achieve its goal.
Perhaps another version of charter is needed to clarify this.

AECON works on interfaces and mapping between the configuration intent coming from end user applications <=> network configuation & network topology known to the network management application systems (e.g. OSS)

APONF works on interfaces and mapping between network configuation & network topology (known to the network management application systems (e.g.OSS)) <=> network management policies, i.e., device configuration Models.


Thank you,
Tina

From: Reinaldo Penno [mailto:rapenno@gmail.com]
Sent: Thursday, July 03, 2014 1:06 AM
To: Tina TSOU
Cc: Fan, Peng; Szilveszter Nadas; aeon@ietf.org; Openv6@ietf.org
Subject: Re: [Aeon] Next step, IETF 90?

To the untrained eye there is a lot of overlap unless I'm not reading correctly.

"b) Specify a new NSLP (NSIS Signaling Layer Protocol), similar to the NAT/Firewall NSLP and QoS NSLP that can be applied and support the APONF use cases. "

"
o) specify extensions to the IETF NSIS protocol to distribute the SFP based network configuration and network topology models between network management applications (e.g., OSS applications) and e.g., the network management system, the routing controlling system or other controlling systems. The IETF Next Steps in Signaling (NSIS) protocol may be extended in two ways to support this interface:
a) Extend NSIS GIST to be used for off-path support"


I believe the more fragmented these initiatives are, more confusion to IESG. The paragraphs above would be enough confusion to anyone.
SFC WG has both data plane and control plane work in the charter. Nothing preclude to have modeling of services policies as one of the charter items in AEON



On Wed, Jul 2, 2014 at 7:06 AM, Tina TSOU <Tina.Tsou.Zouting@huawei.com<mailto:Tina.Tsou.Zouting@huawei.com>> wrote:
Dear Peng, Szilveszter, et al,

There is a connection between AECON and APONF, but no overlapping.

See below the current APONF draft charter.

From: Openv6 [mailto:openv6-bounces@ietf.org] On Behalf Of Tina TSOU
Sent: Monday, June 30, 2014 5:51 PM
To: karagian@cs.utwente.nl<mailto:karagian@cs.utwente.nl>; jsaldana@unizar.es<mailto:jsaldana@unizar.es>; Openv6@ietf.org<mailto:Openv6@ietf.org>
Subject: Re: [Openv6] Is there a draft charter for APONF?

Dear all,

Based on everybody’s feedback, here comes the 3rd version of the charter.

Hope it is more precise and concrete for you to comment on.

------------------------------------
APONF (Application-based Policy for Network Functions) charter

Target Area: Operations and Management Area

Description of Working Group:

Today network operators are challenged to create an abstract view of their network infrastructure and help service developers on using and programming this abstraction rather than  manipulating individual devices. An abstract view of a network infrastructure can be realized using  a network configuration model, that provides a declarative configuration and a network topology model that describes a multi-layer network. Network management applications are Operational Support System (OSS) like applications that help a communication service provider to monitor, control, analyze and manage a communication network.
In this context, network management applications can be used to provide the required configuration and application programming interfaces to such service developers. Subsequently, a network management application can use the application based demands and possibly update its associated network configuration and/or network topology model. Examples of network management applications that can modify the network configuration and/or network topology models are for example, virtual network function services, Distributed Data Center Application, IPv6 transitions, streaming and IoT applications, need to change the network infrastructure configuration.
The updated network configuration and network topology model needs to be communicated to e.g., the network management system, the routing controlling system or other controlling systems, to map the network configuration and network topology models into specific device level configuration models.

Currently, there are no IETF standard mechanisms or modeling languages that can directly be applied to model the network configuration nor the network topology. IETF has however, created the IETF SFC WG to document a new approach to service delivery and operation, where one of its goals is to realize an abstract view of a network by using a service graph denoted as the Service Function Path (SFP). This will enable the development of suitable models for network configuration and network topology.
Furthermore, there are currently no IETF solutions that can be used to provide the necessary configuration interfaces to service developers to program the abstract view of a network infrastructure. Currently, the Application Enabled Collaborative Network (AECON) activity can provide these necessary solutions.

Moreover, there are no IETF solutions that can directly be used to (1) enable the streaming transfer of bulk-variable/data of network configuration and network topology models between network management application systems and e.g., the network management system, the routing controlling system or other controlling systems, and (2) map the network configuration and network topology models into specific device level configuration models. The APONF activity can provide a solution to this challenge.

The main goal of APONF is to:
o) enable the streaming transfer of bulk-variable/data of the up to date SFP based network configuration and network topology models between network management application systems and e.g., the network management system, the routing controlling system or other controlling systems, by using and extending the IETF Next Steps in Signaling Protocol (NSIS).
o) map the SFP based network configuration and network topology models into specific device level configuration models.

The APONF requirements/objectives are:

o) monitor and verify the freshness of the SFP based network configuration and network topology models

o) extend the IETF NSIS protocol to securely and efficiently distribute the SFP based network configuration and network topology models between network management applications (e.g., OSS applications) and e.g., the network management system, the routing controlling system or other controlling systems

o) use application based demands generated by network management applications to map the SFP based network configuration and network topology models into specific device level configuration models. Such application based demands are:

a) Encapsulating, de-encapsulating packets associated with a flow into a tunnel (for example, VPN service, IPv6 transition service need to manage the network function to do that):

b) blocking, or dropping packets associated with a flow in (the edge of) the network element when the network security service is aware of the attack (for example, SAVI service, Anti-DoS service need to manage the network function to do that).

c) configure and dynamically reconfigure data centers to the steer and reroute traffic associated with a specific flow

d) configure and dynamically reconfigure data centers to  change priorities of different types of traffic associated with a specific flow

e) Logging the traffic associated with a flow for network security service, optimization of the traffic in network for IETF ALTO service

f) other actions defined by the administrator

o) specify the Authentication Authorization and Accounting (AAA) method

Work items related to APONF include:
o) specify the problem statement and use cases

o) specify the APONF architecture

o) specify extensions to the IETF NSIS protocol to distribute the SFP based network configuration and network topology models between network management applications (e.g., OSS applications) and e.g., the network management system, the routing controlling system or other controlling systems. The IETF Next Steps in Signaling (NSIS) protocol may be extended in two ways to support this interface:
a) Extend NSIS GIST to be used for off-path support

b) Specify a new NSLP (NSIS Signaling Layer Protocol), similar to the NAT/Firewall NSLP and QoS NSLP that can be applied and support the APONF use cases.

o) map the SFP based network configuration and network topology models into specific device level configuration models

o) specify the AAA method.

Milestones:

I-D 'Problem Statement and Use Cases' as an Informational RFC.

I-D 'APONF Architecture' as an Informational RFC.

I-D 'Mapping SFP based models into specific device level configuration models' as an Informational RFC.

I-D 'APONF based NSIS Protocol Specification' Standards Track RFC.
--------------------------------------


Thank you,
Tina
-----------

Thank you,
Tina

On Jul 2, 2014, at 9:17 PM, "Fan, Peng" <fanpeng@chinamobile.com<mailto:fanpeng@chinamobile.com>> wrote:
Hi all,

As you may noticed there is not a BOF this time at IETF90. We will be presenting on Tuesday during the IETF week to the IESG and IAB to address concerns and questions in regard to AECON and APONF, and have a barBOF/side meeting sometime after that.

We will update the information as soon as possible. Thank you all for making this list fruitful.

Best regards,
Peng

From: Aeon [mailto:aeon-bounces@ietf.org] On Behalf Of Szilveszter Nadas
Sent: Monday, June 30, 2014 9:21 PM
To: aeon@ietf.org<mailto:aeon@ietf.org>
Subject: [Aeon] Next step, IETF 90?

Hi All,

I have seen that the BoF was not approved for IETF 90. Did you receive a more detailed explanation of the reasons?

What is the next step? Will there be a Bar BoF at Toronto?

Best Regards,
Szilveszter

_______________________________________________
Aeon mailing list
Aeon@ietf.org<mailto:Aeon@ietf.org>
https://www.ietf.org/mailman/listinfo/aeon