[Openv6] FW: New Version Notification for draft-karagiannis-aponf-problem-statement-03.txt

<karagian@cs.utwente.nl> Mon, 21 July 2014 12:38 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 51C2F1B2D44 for <openv6@ietfa.amsl.com>; Mon, 21 Jul 2014 05:38:28 -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 zb0TLSqUbLqb for <openv6@ietfa.amsl.com>; Mon, 21 Jul 2014 05:38:26 -0700 (PDT)
Received: from out42-ams.mf.surf.net (out42-ams.mf.surf.net [145.0.1.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B38671B296F for <openv6@ietf.org>; Mon, 21 Jul 2014 05:38:24 -0700 (PDT)
Received: from EXEDGE01.ad.utwente.nl (exedge01.ad.utwente.nl [130.89.5.48]) by outgoing2-ams.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s6LCcJ6a024362; Mon, 21 Jul 2014 14:38:19 +0200
Received: from EXHUB02.ad.utwente.nl (130.89.4.229) by EXEDGE01.ad.utwente.nl (130.89.5.48) with Microsoft SMTP Server (TLS) id 14.3.181.6; Mon, 21 Jul 2014 14:38:20 +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; Mon, 21 Jul 2014 14:38:19 +0200
From: <karagian@cs.utwente.nl>
To: <openv6@ietf.org>
Thread-Topic: New Version Notification for draft-karagiannis-aponf-problem-statement-03.txt
Thread-Index: AQHPpN8OW4cDq373Y0ameTQCjNENPZuqdS58
Date: Mon, 21 Jul 2014 12:38:18 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F5D5773F6@EXMBX24.ad.utwente.nl>
References: <20140721122649.22063.60120.idtracker@ietfa.amsl.com>
In-Reply-To: <20140721122649.22063.60120.idtracker@ietfa.amsl.com>
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.48; 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: 0vMt0CjUT - be5ba1a23d46 - 20140721 (trained as not-spam)
X-Scanned-By: CanIt (www . roaringpenguin . com)
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/APy1CriVFDVB6LvvtdHH72pLCXE
Cc: sob@harvard.edu
Subject: [Openv6] FW: New Version Notification for draft-karagiannis-aponf-problem-statement-03.txt
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, 21 Jul 2014 12:38:28 -0000

Dear all,

A new version (03) of the APONF problem statement draft has just been posted, see below:

  http://www.ietf.org/internet-drafts/draft-karagiannis-aponf-problem-statement-03.txt

The main changes between version 02 and version 03 are:

o) a more detailed description  of the network service graph is provided

o) The information that was refering to the IETF NSIS protocol has been removed. This is due to the conclusions provided bt the APONF gap analysis draft. 

o) the figure proposed by Tom has been included into the draft.

o) description of the relations between APONF with other IETF activities has been updated and extended (AECON, ACTN, NFVcon, UCAN)

More details on the chnages can be found via:
   http://www.ietf.org/rfcdiff?url2=draft-karagiannis-aponf-problem-statement-03


See you today at the APONF Bar BOF meeting at 20:30 in room Quebec!

Best regards,
Georgios






________________________________________
Van: internet-drafts@ietf.org [internet-drafts@ietf.org]
Verzonden: maandag 21 juli 2014 14:26
Aan: Qiong Sun; Karagiannis, G. (EWI); Qiong Sun; Tina Tsou; Will Liu; Tina Tsou; Diego R. Lopez; Diego Lopez; Karagiannis, G. (EWI); Shucheng LIU (Will)
Onderwerp: New Version Notification for draft-karagiannis-aponf-problem-statement-03.txt

A new version of I-D, draft-karagiannis-aponf-problem-statement-03.txt
has been successfully submitted by Georgios Karagiannis and posted to the
IETF repository.

Name:           draft-karagiannis-aponf-problem-statement
Revision:       03
Title:          Problem Statement for Application Policy on Network Functions (APONF)
Document date:  2014-07-21
Group:          Individual Submission
Pages:          12
URL:            http://www.ietf.org/internet-drafts/draft-karagiannis-aponf-problem-statement-03.txt

Status:         https://datatracker.ietf.org/doc/draft-karagiannis-aponf-problem-statement/
Htmlized:       http://tools.ietf.org/html/draft-karagiannis-aponf-problem-statement-03
Diff:           http://www.ietf.org/rfcdiff?url2=draft-karagiannis-aponf-problem-statement-03


Abstract:
   As more and more modern network management applications grow in scale
   and complexity, their demands and requirements on the supporting
   communication network will increase.
   In particular, 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. In this context, network management
   applications can be used to provide the required configuration and
   application programming interfaces to such service developers. The
   main goal of APONF is to (1) communicate the up to date abstract view
   of the network between the network management application systems and
   network management and controlling systems and (2) map the abstract
   view of the network into specific network management policies, i.e.,
   device level configuration models.





Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat