RFC 8597 on Cooperating Layered Architecture for Software-Defined Networking (CLAS)
rfc-editor@rfc-editor.org Thu, 16 May 2019 05:00 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFA36120077 for <ietf-announce@ietfa.amsl.com>; Wed, 15 May 2019 22:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KG1-ZqFdpqw8 for <ietf-announce@ietfa.amsl.com>; Wed, 15 May 2019 22:00:20 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07DDB120006 for <ietf-announce@ietf.org>; Wed, 15 May 2019 22:00:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5F866B80627; Wed, 15 May 2019 22:00:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8597 on Cooperating Layered Architecture for Software-Defined Networking (CLAS)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190516050004.5F866B80627@rfc-editor.org>
Date: Wed, 15 May 2019 22:00:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/0m3RwiIFQE4h1_aLg94VtOZI75w>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2019 05:00:23 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8597
Title: Cooperating Layered Architecture for
Software-Defined Networking (CLAS)
Author: LM. Contreras,
CJ. Bernardos,
D. Lopez,
M. Boucadair,
P. Iovanna
Status: Informational
Stream: Independent
Date: May 2019
Mailbox: luismiguel.contrerasmurillo@telefonica.com,
cjbc@it.uc3m.es,
diego.r.lopez@telefonica.com,
mohamed.boucadair@orange.com,
paola.iovanna@ericsson.com
Pages: 21
Characters: 45229
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-contreras-layered-sdn-03.txt
URL: https://www.rfc-editor.org/info/rfc8597
DOI: 10.17487/RFC8597
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.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC