[Teas] RFC 8453 on Framework for Abstraction and Control of TE Networks (ACTN)

rfc-editor@rfc-editor.org Thu, 23 August 2018 22:27 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0EE34130F2B; Thu, 23 Aug 2018 15:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id scgHcWASnLQV; Thu, 23 Aug 2018 15:27:20 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27031128CF2; Thu, 23 Aug 2018 15:27:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 41D58B80E6B; Thu, 23 Aug 2018 15:27:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, teas@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180823222705.41D58B80E6B@rfc-editor.org>
Date: Thu, 23 Aug 2018 15:27:05 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/brru-hPsaywdQZ_n_quJBYj13Ds>
Subject: [Teas] =?utf-8?q?RFC_8453_on_Framework_for_Abstraction_and_Contr?= =?utf-8?q?ol_of_TE_Networks_=28ACTN=29?=
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2018 22:27:22 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8453

        Title:      Framework for Abstraction and Control 
                    of TE Networks (ACTN) 
        Author:     D. Ceccarelli, Ed.,
                    Y. Lee
        Status:     Informational
        Stream:     IETF
        Date:       August 2018
        Mailbox:    daniele.ceccarelli@ericsson.com, 
        Pages:      42
        Characters: 90463
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-teas-actn-framework-15.txt

        URL:        https://www.rfc-editor.org/info/rfc8453

        DOI:        10.17487/RFC8453

Traffic Engineered (TE) networks have a variety of mechanisms to
facilitate the separation of the data plane and control plane.  They
also have a range of management and provisioning protocols to
configure and activate network resources.  These mechanisms represent
key technologies for enabling flexible and dynamic networking.  The
term "Traffic Engineered network" refers to a network that uses any
connection-oriented technology under the control of a distributed or
centralized control plane to support dynamic provisioning of end-to-
end connectivity.

Abstraction of network resources is a technique that can be applied
to a single network domain or across multiple domains to create a
single virtualized network that is under the control of a network
operator or the customer of the operator that actually owns the
network resources.

This document provides a framework for Abstraction and Control of TE
Networks (ACTN) to support virtual network services and connectivity

This document is a product of the Traffic Engineering Architecture and Signaling Working Group of the IETF.

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

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