RFC 8597: Cooperating Layered Architecture for Software-Defined Networking (CLAS)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8597
- Published
- May 2019
- Authors
- LM. Contreras; CJ. Bernardos; D. Lopez; M. Boucadair; P. Iovanna
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2481A Proposal to add Explicit Congestion Notification (ECN) to IPObsoleted
January 1999
- RFC 2216Network Element Service Specification TemplateCurrent
September 1997
- RFC 1835Architecture of the WHOIS++ serviceCurrent
August 1995
- RFC 1834Whois and Network Information Lookup Service, Whois++Current
August 1995
- RFC 1788ICMP Domain Name MessagesObsoleted
April 1995
- RFC 8517An Inventory of Transport-Centric Functions Provided by Middleboxes: An Operator PerspectiveCurrent
February 2019
- RFC 8921Dynamic Service Negotiation: The Connectivity Provisioning Negotiation Protocol (CPNP)Current
October 2020
- RFC 9228Delivered-To Email Header FieldCurrent
April 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?