A Day in the Life of an Autonomic Function

Document Type Expired Internet-Draft (individual)
Authors Peloso Pierre  , Laurent Ciavaglia 
Last updated 2016-09-22 (latest revision 2016-03-21)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text xml pdf htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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, inter-operable autonomic functions with homogeneous operations and superior quality, and will have more freedom in their deployment scenarios.


Peloso Pierre (pierre.peloso@nokia.com)
Laurent Ciavaglia (Laurent.Ciavaglia@nokia.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)