PCE for Network High Availability
draft-chen-pce-ctr-availability-01
Network Working Group H. Chen
Internet-Draft Futurewei
Intended status: Standards Track A. Wang
Expires: March 13, 2021 China Telecom
L. Liu
Fujitsu
X. Liu
Volta Networks
September 9, 2020
PCE for Network High Availability
draft-chen-pce-ctr-availability-01
Abstract
This document describes extensions to Path Computation Element (PCE)
communication Protocol (PCEP) for improving the reliability or
availability of a network controlled by a controller cluster.
Requirements Language
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 RFC 2119 [RFC2119].
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 13, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Chen, et al. Expires March 13, 2021 [Page 1]
Internet-Draft PCE for Network HA September 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
2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 3
3. PCE for Controller Cluster Reliability . . . . . . . . . . . 3
3.1. Overview of Mechanism . . . . . . . . . . . . . . . . . . 3
3.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Extensions to PCEP . . . . . . . . . . . . . . . . . . . . . 6
4.1. Capability . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Controllers Object . . . . . . . . . . . . . . . . . . . 7
5. Recovery Procedure . . . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
9.1. Normative References . . . . . . . . . . . . . . . . . . 12
9.2. Informative References . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
More and more networks are controlled by central controllers or
controller clusters. A controller cluster is a single controller
externally. It normally consists of two or more controllers
internally working together as a single controller externally to
control a network, i.e., every network element (NE) in the network.
The reliability or availability of a network is heavily dependent on
its controller cluster. The issues or failures in the controller
cluster may impact the reliability or availability of the network
greatly.
For a controller cluster comprising two or more controllers (i.e.,
primary controller, secondary controller, and so on), the failures in
the cluster may split the cluster into a few of separated controller
groups. These groups do not know each other and may be out of
synchronization. Two or more groups may be elected as primary groups
to control the network at the same time, which may cause some issues.
Chen, et al. Expires March 13, 2021 [Page 2]
Show full document text