Anima Bootstrapping for Network Management
draft-nmdt-anima-management-bootstrap-01

Document Type Active Internet-Draft (individual)
Last updated 2018-09-26
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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)
Network Working Group                                            F. Duan
Internet-Draft                                               B. Liu, Ed.
Intended status: Standards Track                                Y. Zhang
Expires: March 30, 2019                              Huawei Technologies
                                                      September 26, 2018

               Anima Bootstrapping for Network Management
                draft-nmdt-anima-management-bootstrap-01

Abstract

   This document points out the gaps of utilizing current Anima
   technologies into a traditional centralized management network.  It
   raises some problems and requirments, based on which, as set of
   solutions are proposed.  (These solutions are called Anima
   Bootstrapping for Network Management.)

Status of This Memo

   This Internet-Draft is submitted 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 https://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 March 30, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Duan, et al.             Expires March 30, 2019                 [Page 1]
Internet-Draft    draft-nmdt-anima-management-bootstrap   September 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Problems and Requirments  . . . . . . . . . . . . . . . . . .   3
   4.  Autonomic Structured Naming . . . . . . . . . . . . . . . . .   4
     4.1.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Name Format and Content . . . . . . . . . . . . . . . . .   5
       4.2.1.  Structured Naming Format  . . . . . . . . . . . . . .   5
       4.2.2.  Naming Content  . . . . . . . . . . . . . . . . . . .   5
     4.3.  Autonomic Naming Approaches . . . . . . . . . . . . . . .   6
       4.3.1.  Received and Self-generated Naming Elements . . . . .   6
       4.3.2.  Naming Metadata Storage . . . . . . . . . . . . . . .   7
   5.  Network Management Server/Controller Discovery  . . . . . . .   7
     5.1.  GRASP Method  . . . . . . . . . . . . . . . . . . . . . .   7
     5.2.  mDNS Method . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Topology Discovery and Collection . . . . . . . . . . . . . .   8
     6.1.  Local Topoloty Discovery  . . . . . . . . . . . . . . . .   8
     6.2.  Topology Collection by NMS/Controller . . . . . . . . . .   9
   7.  Device Names and Topoloty Mapping in the NMS/Controller . . .   9
   8.  Security  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     11.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   One typical usage of ANIMA technologyies is that they serve as a
   stable management channel of the management systems, such as
   controllers or network management system (NMS) hosts.  And These
   cases is also described in section 6 of
   [I-D.ietf-anima-autonomic-control-plane], with the purpose of
   management and controllability of ACP for the controllers or NMS
   hosts.  However, In ANIMA networking, the autonomic nodes in ACP are
   self configurable by default, most configuration of which is learning
   from neighboring nodes in decentralized ways.  While in traditional
   networking, the configuration is got by the top-down ways from the
   centralized devices (such as controller, NMS hosts etc) . These are
   the gaps and differences between the traditional networking and ANIMA
Show full document text