A Day in the Life of an Autonomic Function
draft-peloso-anima-autonomic-function-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-10-19
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ANIMA                                                          P. Peloso
Internet-Draft                                              L. Ciavaglia
Intended status: Standards Track                          Alcatel-Lucent
Expires: April 21, 2016                                 October 19, 2015

               A Day in the Life of an Autonomic Function
                draft-peloso-anima-autonomic-function-00

Abstract

   While autonomic functions are often pre-installed and integrated with
   the network elements they manage, this is not a mandatory condition.
   Allowing autonomic functions to be dynamically installed and to
   control resources remotely enables more versatile deployment
   approaches and enlarges the application scope to virtually any legacy
   equipment.  The analysis of autonomic functions deployment schemes
   through the installation, instantiation and operation phases allows
   constructing a unified life-cycle and identifying new required
   functionality.  Thus, the introduction of autonomic technologies will
   be facilitated, the adoption much more rapid and broad.  Operators
   will benefit from multi-vendor, interoperable autonomic functions
   with homogeneous operations and superior quality, and will have more
   freedom in their deployment scenarios.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 21, 2016.

Peloso & Ciavaglia       Expires April 21, 2016                 [Page 1]
Internet-Draft             Autonomic Function               October 2015

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.

   This document may not be modified, and derivative works of it may not
   be created, except to format it for publication as an RFC or to
   translate it into languages other than English.

Table of Contents

   1.  Problem statement . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Motivations from an operator viewpoint  . . . . . . . . . . .   4
     2.1.  Illustration of increasingly constraining operator's
           objectives  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Deployment scenarios of autonomic functions . . . . . . .   5
     2.3.  Operator's requirements with regards to autonomic
           functions . . . . . . . . . . . . . . . . . . . . . . . .   9
   3.  Installation phase  . . . . . . . . . . . . . . . . . . . . .  10
     3.1.  Operator's goal . . . . . . . . . . . . . . . . . . . . .  10
     3.2.  Installation phase inputs and outputs . . . . . . . . . .  11
   4.  Instantiation phase . . . . . . . . . . . . . . . . . . . . .  12
     4.1.  Operator's goal . . . . . . . . . . . . . . . . . . . . .  12
     4.2.  Instantiation phase inputs and outputs  . . . . . . . . .  13
     4.3.  Instantiation phase requirements  . . . . . . . . . . . .  13
   5.  Operation phase . . . . . . . . . . . . . . . . . . . . . . .  14
   6.  Autonomic Function Agent specifications . . . . . . . . . . .  15
     6.1.  Life-cycle  . . . . . . . . . . . . . . . . . . . . . . .  15
     6.2.  AFA Class Manifest  . . . . . . . . . . . . . . . . . . .  16
     6.3.  AFA Instance Mandate  . . . . . . . . . . . . . . . . . .  17
     6.4.  AFA Instance Manifest . . . . . . . . . . . . . . . . . .  18
   7.  Implication for other ANIMA components  . . . . . . . . . . .  19
     7.1.  Additional entities for ANIMA ecosystem . . . . . . . . .  19
     7.2.  Requirements for GRASP and ACP messages . . . . . . . . .  20
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  20
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  21
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  21
Show full document text