Scenarios and Requirements for Layer 2 Autonomic Control Planes
draft-carpenter-anima-l2acp-scenarios-00

Document Type Active Internet-Draft (individual)
Last updated 2019-02-27
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                                       B. Carpenter
Internet-Draft                                         Univ. of Auckland
Intended status: Informational                               B. Liu, Ed.
Expires: September 1, 2019                           Huawei Technologies
                                                       February 28, 2019

    Scenarios and Requirements for Layer 2 Autonomic Control Planes
                draft-carpenter-anima-l2acp-scenarios-00

Abstract

   This document discusses scenarios and requirements for Autonomic
   Control Planes (ACPs) constructed and secured at Layer 2.  These
   would be alternatives to an ACP constructed and secured at the
   network layer.  A secure ACP is required as the substrate for the
   Generic Autonomic Signaling Protocol (GRASP) used by Autonomic
   Service Agents.

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 September 1, 2019.

Copyright Notice

   Copyright (c) 2019 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

Carpenter & Liu         Expires September 1, 2019               [Page 1]
Internet-Draft              L2 ACP Scenarios               February 2019

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Network Scenarios Suitable for a Layer 2 ACP  . . . . . . . .   2
   3.  Requirements for a Layer 2 Technology . . . . . . . . . . . .   3
   4.  Multiple Segments . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Implementation Status [RFC Editor: please remove] . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Appendix A.  Change log [RFC Editor: Please remove] . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   As defined in [I-D.ietf-anima-reference-model], the Autonomic Service
   Agent (ASA) is the atomic entity of an autonomic function, and it is
   instantiated on autonomic nodes.  When ASAs communicate with each
   other, they should use the Generic Autonomic Signaling Protocol
   (GRASP) [I-D.ietf-anima-grasp].  It is essential that such
   communication is strongly secured to avoid malicious interference
   with the Autonomic Infrastructure (ANI).

   For this reason, GRASP must run over a secure substrate that is
   isolated from regular data plane traffic.  This substrate is known as
   the Autonomic Control Plane (ACP).  A method for constructing an ACP
   at the network layer is described in
   [I-D.ietf-anima-autonomic-control-plane].  The present document
   discusses scenarios and requirements for constructing an ACP at layer
   2.

2.  Network Scenarios Suitable for a Layer 2 ACP

   The ANI design is aimed at managed networks, as explained in the
   reference model [I-D.ietf-anima-reference-model].  For a wide area
   network (such as a large campus, a multi-site enterprise network, or
   a carrier network considered as a whole) it is appropriate to
   construct the ACP using network layer techniques and network layer
   security.  and that is the model described in
   [I-D.ietf-anima-autonomic-control-plane], However, in at least two
   cases an ACP covering a smaller geographical area may be appropriate:

Carpenter & Liu         Expires September 1, 2019               [Page 2]
Internet-Draft              L2 ACP Scenarios               February 2019
Show full document text