[Openv6] new APONF charter

<karagian@cs.utwente.nl> Fri, 25 July 2014 12:04 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 E1AC31B27FF for <openv6@ietfa.amsl.com>; Fri, 25 Jul 2014 05:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 0PQajUYOCzzl for <openv6@ietfa.amsl.com>; Fri, 25 Jul 2014 05:04:00 -0700 (PDT)
Received: from out64-ams.mf.surf.net (out64-ams.mf.surf.net [145.0.1.64]) (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 328451B27FE for <openv6@ietf.org>; Fri, 25 Jul 2014 05:04:00 -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 s6PC5S3L031827 for <openv6@ietf.org>; Fri, 25 Jul 2014 14:05:28 +0200
Received: from EXHUB01.ad.utwente.nl (130.89.4.228) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.3.181.6; Fri, 25 Jul 2014 14:04:01 +0200
Received: from EXMBX24.ad.utwente.nl ([169.254.4.146]) by EXHUB01.ad.utwente.nl ([130.89.4.228]) with mapi id 14.03.0181.006; Fri, 25 Jul 2014 14:03:57 +0200
From: <karagian@cs.utwente.nl>
To: <openv6@ietf.org>
Thread-Topic: new APONF charter
Thread-Index: Ac+oAIKX2LG7gbbvSWaLxmIdGEkx9Q==
Date: Fri, 25 Jul 2014 12:03:56 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F5D57C64B@EXMBX24.ad.utwente.nl>
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: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F5D57C64BEXMBX24adutwent_"
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: 0bMuA5sHG - 8f5caac5c839 - 20140725 (trained as not-spam)
X-Scanned-By: CanIt (www . roaringpenguin . com)
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/qR3lngMlcRSIPen9Z3ZCLwnZsPg
Subject: [Openv6] new APONF charter
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 12:04:03 -0000

Dear all,

Based on the comments that we have received we updated the APONF cahrter, see below:

APONF (Application-based Policy for Network Functions) charter

Target Area: OPS 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 and service function interdependencies can be realized using a network service graph. A network service graph is a graph specified by a Network Service Provider that defines how one or more network services are applied to traffic flowing through a set of nodes of the graph, which includes attributes such as:

o) network topology, based on I2RS, SCF based network topologies and represented by a graph of links and nodes

o) service functions (e.g., policing function, NAT, Firewall, DNS, DHCP) and their interdependencies

o) mapping between service function (and their service function interdependencies) and network topology (similar to ALTO mapping)

o) application based policy actions: e.g., steer a traffic flow, prioritize a traffic flow, encapsulate/de-capsulate a traffic flow, block or admit a traffic flow

Network services are enhanced Operational Support System (OSS) services that help a communication service provider to monitor, control, analyze and manage a communication network. In this context, network services can be used to provide the required configuration and application programming interfaces to network service developers. Subsequently, a network service can use the service based demands and possibly update its associated network service graph.

The main goal of APONF is to provide application based policies and means to model and program the abstract view of network infrastructure and service function interdependencies in order to support and feed network management and controlling policies (e.g., dynamic network configuration, SCF classification strategies, I2RS routing strategies).
This can be realized by:

(1) modeling the network service graph, which among others include application based policies, using Yang,

(2) applying Netconf to enable dissemination of up to date (fresh) network service graphs in a secure and efficient manner between network service systems and network management and controlling systems,

(3) providing guidelines on mapping attributes of network service graphs provided by network service systems into specific network management and controlling policies.


Work items related to APONF include:

o) specify the network service graph based on Yang models

o) specify and standardize how Netconf/Yang can be used to securely and efficiently distribute up to date (fresh) network service graphs between network service systems and network management and controlling systems

o) provide guidelines for mechanisms that can dynamically map attributes, including application based policies, of network service graphs into specific network management and controlling policies, such as dynamic network configuration, SCF classification strategies, I2RS routing strategies

o) document how to use Netconf authentication and authorization mechanisms to achieve protection and isolation

The following items are out of the APONF scope:

o) specification of the network management and controlling policies and their associated device configuration models

Milestones:

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

    I-D 'APONF Gap Analysis as an Informational RFC.

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

    I-D 'Mapping network service graphs into specific network management and controlling policies'

    I-D 'APONF Netconf/Yang Protocol Specification' Standards Track RFC.

Best regards,
Georgios