Autonomic Control Plane challenges for Layer-Two Switched Networks
draft-richardson-anima-l2-friendly-acp-00
anima Working Group M. Richardson
Internet-Draft Sandelman Software Works
Intended status: Standards Track J. Yang
Expires: 25 January 2021 Huawei Technologies Co., Ltd.
24 July 2020
Autonomic Control Plane challenges for Layer-Two Switched Networks
draft-richardson-anima-l2-friendly-acp-00
Abstract
This document details the challenges with building an Autonomic
Control Plane on Campus/Enterprise networks which are built out of
layer-two (Ethernet) switched technologies.
This document does not propose a specific solution as yet, but
details a number of possibilities, and what it would take to
standardize each possibility.
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 25 January 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Richardson & Yang Expires 25 January 2021 [Page 1]
Internet-Draft l2-friendly-acp July 2020
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 the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Functional Requirements . . . . . . . . . . . . . . . . . . . 3
3. Nice to have Functionality . . . . . . . . . . . . . . . . . 4
4. Possibilities . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Just use special destination . . . . . . . . . . . . . . 4
4.2. Use another EtherType . . . . . . . . . . . . . . . . . . 5
4.3. Do something with EAPoL . . . . . . . . . . . . . . . . . 5
5. Privacy Considerations . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
9. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . . 5
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
10.1. Normative References . . . . . . . . . . . . . . . . . . 5
10.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
The creation and maintenance of the Autonomic Control Plane described
in [I-D.ietf-anima-autonomic-control-plane] requires creation of hop-
by-hop discovery of adjacent systems. There are Campus L2 systems
that are not broadcast safe until they have been connected to their
Software Defined Networking (SDN) controller. The use of the stable
connectivity provided by [RFC8368] can provide the SDN connectivity
required.
There is a bootstrap interlocking problem: the network may be unsafe
for ACP discovery broadcasts without the support of Spanning Tree
Protocol (STP) or similar mechanisms until configured, yet it can not
be automatically configured until the ACP discovery (and onboarding
process) is done. Meantime, because of STP complicated topological
calculations, the convergence can be very slow for larger networks.
This can delay on-boarding.
Richardson & Yang Expires 25 January 2021 [Page 2]
Internet-Draft l2-friendly-acp July 2020
In addition, forming a campus-wide network by default and using
enabling STP does not work. STP is not secure and could be easily
spoofed by malicious or untrusted devices. On manually configured
networks today, STP is turned off on "access" ports, and enabled only
Show full document text