One document matched: draft-pentikousis-nmrg-andr-00.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
There has to be one entity for each item to be referenced.
An alternate method (rfc include) is described in the references. -->
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY ANDG SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.irtf-nmrg-autonomic-network-definitions.xml">
<!ENTITY ANGaps SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.irtf-nmrg-an-gap-analysis.xml">
<!ENTITY ANCP SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.behringer-autonomic-control-plane.xml">
<!ENTITY SDNT SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.irtf-sdnrg-layer-terminology.xml">
<!ENTITY I2RSProb SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-i2rs-problem-statement.xml">
<!ENTITY SFCProb SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-sfc-problem-statement.xml">
<!ENTITY ABNO SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.farrkingel-pce-abno-architecture.xml">
<!ENTITY SUPA SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.pentikousis-supa-mapping.xml">
<!ENTITY RFC5812 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5812.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
(Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
(using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-pentikousis-nmrg-andr-00">
<!-- category values: std, bcp, info, exp, and historic
ipr values: full3667, noModification3667, noDerivatives3667
you can add the attributes updates="NNNN" and obsoletes="NNNN"
they will automatically be output with "(if approved)" -->
<!-- ***** FRONT MATTER ***** -->
<front>
<!-- The abbreviated title is used in the page header - it is only necessary if the
full title is longer than 39 characters -->
<title abbrev="Autonomic Networking Definitions">Autonomic Networking Definitions Revisited</title>
<!-- add 'role="editor"' below for the editors if appropriate -->
<!-- Another author who claims to be an editor -->
<author fullname="Kostas Pentikousis" initials="K.P." surname="Pentikousis">
<organization abbrev="EICT">EICT GmbH</organization>
<address>
<postal>
<street>EUREF-Campus Haus 13</street>
<street>Torgauer Strasse 12-15</street>
<city>10829 Berlin</city>
<country>Germany</country>
</postal>
<email>k.pentikousis@eict.de</email>
</address>
</author>
<date year="2014" />
<!-- If the month and year are both specified and are the current ones, xml2rfc will fill
in the current day for you. If only the current year is specified, xml2rfc will fill
in the current day and month for you. If the year is not the current one, it is
necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the
purpose of calculating the expiry date). With drafts it is normally sufficient to
specify just the year. -->
<!-- Meta-data Declarations -->
<area>General</area>
<workgroup>Network Working Group</workgroup>
<!-- WG name at the upperleft corner of the doc,
IETF is fine for individual submissions.
If this element is not present, the default is "Network Working Group",
which is used by the RFC Editor as a nod to the history of the IETF. -->
<keyword>Autonomic networking</keyword>
<!-- Keywords will be incorporated into HTML output
files in a meta tag but they have no effect on text or nroff
output. If you submit your draft to the RFC Editor, the
keywords will be used for the search engine. -->
<abstract>
<t>This document revisits the autonomic networking terminology established in peer-reviewed literature, aiming to contribute to the ongoing discussion in the IRTF NMRG about how to move forward with standardizing various autonomic networking aspects.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>The IRTF Network Management Research Group (NMRG) has been working on a set of definitions for autonomic networking. Defining and agreeing on autonomic networking terminology is not an easy task as discussed in <xref target="TAN" />. In general, autonomic operation is associated with a range of properties, such as self-configuration, self-healing, self-optimization, and self-protection <xref target="ACDawn" />. Behringer et al. <xref target="I-D.irtf-nmrg-autonomic-network-definitions" /> describe a set of design goals and non-goals for autonomic networking and introduce a model reference architecture in the context of future IETF standardization a <xref target="I-D.behringer-autonomic-control-plane" />.</t>
<t>Prior to this recent effort at the NMRG, autonomic networking has been the focus of several research projects over the last decade. For example, Bouabene et al. <xref target="ANA" /> detail the autonomic network architecture (ANA). Nguengang et al. <xref target="UMFSpec" /> propose a unified management framework (UMF) which uses autonomics at its core. Chaparadza et al. <xref target="SelfFI" /> introduce an elegant and "standardizable" [sic] generic autonomic networking architecture (GANA) which they propose to be used as a reference model. The latter was indeed further elaborated under the auspices of ETSI as a group specification <xref target="GANA" />. This list of earlier work in only indicative to the breadth of research in this area over the last decade. However, standardization remains an open question and deployment has been limited to specific mechanisms only <xref target="I-D.irtf-nmrg-an-gap-analysis" />.</t>
<t>We concur with Behringer et al. <xref target="I-D.irtf-nmrg-autonomic-network-definitions" /> that for most of the work in IETF it suffices to define autonomic behaviour at the node level. However, recent standardization efforts in the IETF, such as, for example, I2RS <xref target="I-D.ietf-i2rs-problem-statement" />, SFC <xref target="I-D.ietf-sfc-problem-statement" />, ABNO <xref target="I-D.farrkingel-pce-abno-architecture" />, SUPA <xref target="I-D.pentikousis-supa-mapping" />, and LIME to name a few, and new research groups at the IRTF (SDNRG and proposed NFVRG), indicate that one may consider that the NMRG should perhaps dig a bit deeper before finalizing the definitions and goals document. In particular, one could reconsider the aspects of defining node-level autonomicity only.</t>
<t>This document revisits the autonomic networking definitions proposed earlier in the peer-reviewed literature <xref target="defs" /> ,and relates them with such recent developments aiming to assist in the definition of coherent terminology in this emerging area of standardization at the IETF.</t>
<section title="Requirements Language">
<t>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<xref target="RFC2119">RFC 2119</xref>.</t>
</section>
</section>
<section title="Definitions" anchor="defs">
<t>After some thorough analysis and discussion, Schmid et al. <xref target="TAN" /> put forward the following definition, which captures in a concrete and concise manner the essence of autonomicity:
<list style="hanging">
<t>An Autonomic System is a system that operates and serves its purpose by managing its own self without external intervention even in case of environmental changes.</t>
</list>
Note that the authors explicitly define autonomicity at the system level, not at the node level. They go on to list the minimum set of properties that an autonomic system should possess. Namely, an autonomic system is
<list style="symbols">
<t>automatic, i.e. it can "self-control its internal functions and operations"</t>
<t>adaptive, i.e. it can change its "configuration, state and functions", and</t>
<t>aware, i.e. it can "monitor its operational context".</t>
</list></t>
<t>In principle, an autonomic system could wholly replace a non-autonomic one. In practice, however, real-world deployments will include legacy network elements and services as well as new autonomic ones.</t>
<t>A salient paper in the autonomic networking area is <xref target="FOCALE" />, in which Strassner et al. lay the foundation for an autonomic network architecture. We will not delve into the details of FOCALE, but we do note that the authors define three types of managed components depending on their autonomic capabilities. In the remainder of this document we consider that FOCALE "components" equate to network resources as defined in <xref target="I-D.irtf-sdnrg-layer-terminology" />, i.e. each network resource is a "physical or virtual component available within a system", and build on the definitions further.</t>
<t>In this sense, legacy equipment can be seen as autonomically unaware resources, and can only be managed using traditional mechanisms. In practice, field equipment could be upgraded to support certain autonomic features, thus becoming autonomically-aware managed network resources. This type of network element would typically require a mediation layer as suggested in <xref target="FOCALE" /> or at the very least certain system software updates. Finally, a deployment could include fully autonomically-enabled network resources. FOCALE explicitly aims to "accommodate legacy components" and foresees the deployment of an autonomic manager "that orchestrates the behaviour of other autonomic components in the system."</t>
<t><xref target="ANCL" /> illustrates a simple sketch of an autonomic networking control loop, based on Fig. 2 of <xref target="FOCALE" />. In short, an autonomic manager gathers data from the managed resource(s), evaluates the current state, compares it with the desired one, and configures the managed resource as necessary. As illustrated, this simple system possess the minimum set of properties introduced above.</t>
<t><figure title="Simple sketch of an autonomic networking control loop" anchor="ANCL"> <artwork align="center"><![CDATA[
+---------------------+
(Maintenance Loop) | Actual vs. desired | Autonomic manager
+-------------->| state evaluation |
| | and decision making |
| +---------o-----------+
v |
+----------------+ | New configuration
| Data gathering | | (Adjustment Loop)
+----------------+ |
^ v
| +------------------+
+----------------o Managed resource |
+------------------+
]]></artwork></figure></t>
<t>Of course, all three types of network resources (autonomically-unaware, -aware, and -enabled) need to be managed. One viable approach is proposed by Nguengang et al. <xref target="UMFSpec" /> who describe an architecture based on the definition of two types of management systems depending on the capacity of the underlying nodes, namely an Enhanced Legacy Management System (ELMS) or a Future Management System (FMS).</t>
<t>Finally, autonomic properties are highly desirable in the context of new mobile architectures. For example, Barth and Kuehn <xref target="SON4G" /> discuss the need for self-* properties in the context of small cell deployments in 4G/LTE, while Hamalainen et al. <xref target="LTESON" /> and provide a comprehensive guide and handy references to the efforts in 3GPP along these lines.</t>
</section>
<section title="Operational Considerations and Outlook">
<t>This section briefly describes emerging operational considerations what in the author's view should be taken into account as we move forward with autonomic networking standardization in the IETF and IRTF context.</t>
<section title="New Deployment Models">
<t>Strassner et al. <xref target="FOCALE" /> highlight that an important goal of autonomics is "making the life of the user easier by changing the focus from a computer-centric to a task-centric model". Deployment of new network technologies is typically a time-consuming, labour-intensive and cumbersome task. In the past, we have seen that if the newly designed infrastructure cannot be managed satisfactorily adverse results, such as service launch delays, may be inevitable. As we move forward with new deployment models which are oriented towards softwarized and cloudified network functions, autonomic networking principles may prove invaluable.</t>
<t>As per <xref target="TAN" />, autonomic systems are by design programmable, which bodes well with the emerging deployment models which emphasize agility and shorter technology introduction cycles. We argue that autonomic networking definitions, goals and gap analysis within the context of IETF standardization should take this more into consideration. Further, recent initiatives such as SUPA <xref target="I-D.pentikousis-supa-mapping" /> point towards infrastructures which are managed through intent (generic policies), for instance, as opposed to network element specific configuration.</t>
</section>
<section title="Programmable Network Elements and Functions">
<t>Although the development of models such as FoRCES <xref target="RFC5812"/> coincided with the core of the above-mentioned autonomic networking research literature, by and large, the two areas did not cross-pollinate. It appears that as SDN and NFV principles reach a wider audience of researchers and practitioners, fully programmable network elements and functions could be further introduced in autonomic networking architectures. Indeed, moving towards a "task-centric model" relates well with other efforts in IETF such as SFC <xref target="I-D.ietf-sfc-problem-statement" /></t>
</section>
<section title="Autonomic Planes">
<t>Recent work at the SDNRG <xref target="I-D.irtf-sdnrg-layer-terminology" /> highlighted the need for the wider SDN community to think in terms of control, management, and operational planes comprehensiveness and complementarity. As we have seen above, earlier work in autonomic networking has been primarily focusing on management aspects (cf. <xref target="UMFSpec" />), while recent work in NMRG is focusing on standardizing an autonomic networking control plane <xref target="I-D.behringer-autonomic-control-plane" />. A way forward could be to consider autonomics in NMRG in the context of programmable networks and through a more comprehensive manner.</t>
</section>
<section title="DevOps">
<t>John et al. <xref target="NSC" /> elaborate on the concept of continuous network service delivery. In this context, the authors argue for the need of programmable observation points which could be inserted in a dynamic service chain on demand. They expect that future service provider DevOps would require new management technologies "based on the experience from data centers" thus "addressing the challenges of dynamic service chaining". This bodes well with the model illustrated in <xref target="ANCL" /> and we could expect more results in this direction in the future.</t>
</section>
</section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>This document would not have been possible without the stimulating discussion during the NMRG meeting at IETF 90 in Toronto. Many thanks to all participants.</t>
</section>
<!-- Possibly a 'Contributors' section ... -->
<section anchor="IANA" title="IANA Considerations">
<t>This memo includes no request to IANA.</t>
</section>
<section anchor="Security" title="Security Considerations">
<t>This document does not propose a new network architecture or protocol and as such does not have any impact on the security of the Internet.</t>
<t>Autonomic networking introduces a range of opportunities for formal verification techniques which could increase trustworthiness, although this is clearly beyond the scope of this first version of this document. Interested readers should consult <xref target="ACSec" /> for an early exploration of the issues at hand in the context of autonomic computing.</t>
</section>
</middle>
<!-- *****BACK MATTER ***** -->
<back>
<!-- References split into informative and normative -->
<!-- There are 2 ways to insert reference entries from the citation libraries:
1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
(for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")
Both are cited textually in the same manner: by using xref elements.
If you use the PI option, xml2rfc will, by default, try to find included files in the same
directory as the including file. You can also define the XML_LIBRARY environment variable
with a value containing a set of directories to search. These can be either in the local
filing system or remote ones accessed by http (http://domain/dir/... ).-->
<references title="Informative References">
<reference anchor="TAN">
<front>
<title>Towards autonomic networks</title>
<author><organization>Schmid, S., Sifalakis, M., and D. Hutchison</organization></author>
<date year="2006" />
</front>
<seriesInfo name="Proc. Autonomic Networking, LNCS 4195, pp. 1-11" value="Springer"></seriesInfo>
</reference>
<reference anchor="ANA">
<front>
<title>The autonomic network architecture (ANA)</title>
<author><organization>Bouabene, G., Jelger, C., Tschudin, C., Schmid, S., Keller, A., and M. May</organization></author>
<date year="2003" />
</front>
<seriesInfo name="Journal on Selected Areas in Communications, 28(1), 4-14" value="IEEE"></seriesInfo>
</reference>
<reference anchor="ACDawn">
<front>
<title>The dawning of the autonomic computing era</title>
<author><organization>Ganek, A. G., and T. A. Corbi</organization></author>
<date year="2003" />
</front>
<seriesInfo name="IBM systems Journal, 42(1), 5-18" value=""></seriesInfo>
</reference>
<reference anchor="ACSec">
<front>
<title>Security in an autonomic computing environment</title>
<author><organization>Chess, D. M., Palmer, C. C., and S. R. White</organization></author>
<date year="2003" />
</front>
<seriesInfo name="IBM systems Journal, 42(1), 107-118" value=""></seriesInfo>
</reference>
<reference anchor="FOCALE">
<front>
<title>FOCALE: A novel autonomic networking architecture</title>
<author><organization>Strassner, J., Agoulmine, N., and E. Lehtihet</organization></author>
<date month="July" year="2006" />
</front>
<seriesInfo name="Proc. Latin American Autonomic Computing Symposium (LAACS)," value="Campo Grande, Brazil"></seriesInfo>
</reference>
<reference anchor="UMFSpec">
<front>
<title>UMF Specifications, Release 1</title>
<author><organization>Nguengang, G. (ed.), et al.</organization> </author>
<date month="July" year="2011" />
</front>
<seriesInfo name="FP7-UNIVERSELF-Deliverable D2.1" value=""></seriesInfo>
</reference>
<reference anchor="SelfFI">
<front>
<title>Creating a viable Evolution Path towards Self-Managing Future Internet via a Standardizable Reference Model for Autonomic Network Engineering</title>
<author><organization>Chaparadza, R., Papavassiliou, S., et al.</organization> </author>
<date year="2009" />
</front>
<seriesInfo name="Future Internet Assembly (pp. 136-147)" value="IOS Press"></seriesInfo>
</reference>
<reference anchor="GANA">
<front>
<title>Autonomic network engineering for the self-managing Future Internet (AFI): GANA Architectural Reference Model for Autonomic Networking, Cognitive Networking and Self-Management. </title>
<author surname="ETSI GS AFI 002"/>
<date month="April" year="2013"/>
</front>
</reference>
<reference anchor="SON4G">
<front>
<title>Self-organization in 4G mobile networks: Motivation and vision</title>
<author><organization>Barth, U., and E. Kuehn</organization></author>
<date month="September" year="2010" />
</front>
<seriesInfo name="Proc. 7th International Symposium on Wireless Communication Systems (ISWCS), York, UK, pp. 731-735, " value="IEEE"></seriesInfo>
</reference>
<reference anchor="LTESON">
<front>
<title>LTE Self-Organising Networks (SON): Network Management Automation for Operational Efficiency</title>
<author><organization>Hamalainen, S., Sanneck, H., and C. Sartori</organization></author>
<date year="2012" />
</front>
<seriesInfo name="John Wiley & Sons " value=""></seriesInfo>
</reference>
<reference anchor="NSC">
<front>
<title>Research directions in network service chaining</title>
<author><organization>John, W., Pentikousis, K., et al.</organization></author>
<date month="November" year="2013" />
</front>
<seriesInfo name="Proc. SDN for Future Networks and Services (SDN4FNS), Trento, Italy" value="IEEE"></seriesInfo>
</reference>
<!-- Here we use entities that we defined at the beginning. -->
&RFC2119;
&RFC5812;
&ANDG;
&ANGaps;
&ANCP;
&SDNT;
&I2RSProb;
&SFCProb;
&ABNO;
&SUPA;
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 05:44:33 |