Cooperating Layered Architecture for Software-Defined Networking
RFC 8597, “Cooperating Layered Architecture for Software-Defined Networking”, is an Informational document published in May 2019 by LM. Contreras, CJ. Bernardos, D. Lopez, M. Boucadair, P. Iovanna. The canonical text is published by the RFC Editor.
Abstract
Software-Defined Networking (SDN) advocates for the separation of the control plane from the data plane in the network nodes and its logical centralization on one or a set of control entities. Most of the network and/or service intelligence is moved to these control entities. Typically, such an entity is seen as a compendium of interacting control functions in a vertical, tightly integrated fashion. The relocation of the control functions from a number of distributed network nodes to a logical central entity conceptually places together a number of control capabilities with different purposes. As a consequence, the existing solutions do not provide a clear separation between transport control and services that rely upon transport capabilities.
This document describes an approach called Cooperating Layered Architecture for Software-Defined Networking (CLAS), wherein the control functions associated with transport are differentiated from those related to services in such a way that they can be provided and maintained independently and can follow their own evolution path.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8597 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8596 MPLS Transport Encapsulation for the Service Function Chaining Network Service Header
- RFC 8598 Split DNS Configuration for the Internet Key Exchange Protocol Version 2
- RFC 8595 An MPLS-Based Forwarding Plane for Service Function Chaining
- RFC 8599 Push Notification with the Session Initiation Protocol
- RFC 8594 The Sunset HTTP Header Field
- RFC 8600 Using Extensible Messaging and Presence Protocol for Security Information Exchange
- RFC 8593 Video Traffic Models for RTP Congestion Control Evaluations
- RFC 8601 Message Header Field for Indicating Message Authentication Status