[Teas] Document Action: 'Framework for Abstraction and Control of Traffic Engineered Networks' to Informational RFC (draft-ietf-teas-actn-framework-15.txt)

The IESG <iesg-secretary@ietf.org> Fri, 01 June 2018 19:06 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: teas@ietf.org
Delivered-To: teas@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E57F126B6D; Fri, 1 Jun 2018 12:06:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.81.1
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, db3546@att.com, Vishnu Beeram <vbeeram@juniper.net>, draft-ietf-teas-actn-framework@ietf.org, teas-chairs@ietf.org, teas@ietf.org, vbeeram@juniper.net, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <152787998011.15429.12091807823606460772.idtracker@ietfa.amsl.com>
Date: Fri, 01 Jun 2018 12:06:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/5FTkw07rxDTK2APuxWtoqkeXMMM>
Subject: [Teas] Document Action: 'Framework for Abstraction and Control of Traffic Engineered Networks' to Informational RFC (draft-ietf-teas-actn-framework-15.txt)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 01 Jun 2018 19:06:20 -0000

The IESG has approved the following document:
- 'Framework for Abstraction and Control of Traffic Engineered Networks'
  (draft-ietf-teas-actn-framework-15.txt) as Informational RFC

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

The IESG contact persons are Alvaro Retana, Martin Vigoureux and Deborah
Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-teas-actn-framework/





Technical Summary

   Traffic Engineered 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
   Traffic Engineered Networks (ACTN) to support virtual network
   services and connectivity services.

Working Group Summary

This is part of the initial set of ACTN documents worked on by the
WG. There was considerable debate at various stages of the WG process
on the terminology used in the document and on the various 
operations/functions that fit into the framework. The authors addressed 
all of these concerns by adding relevant text to the document.

Document Quality

 This document has been discussed and reviewed thoroughly by the WG.
While there have been no official statements on implementation of this 
new framework, the authors are from multiple vendors, and implementation 
is expected.

Personnel

   Who is the Document Shepherd for this document?  Vishnu Pavan Beeram
   Who is the Responsible Area Director?  Deborah Brungard