draft-ietf-teas-actn-framework-10.txt   draft-ietf-teas-actn-framework-11.txt 
TEAS Working Group Daniele Ceccarelli (Ed) TEAS Working Group Daniele Ceccarelli (Ed)
Internet Draft Ericsson Internet Draft Ericsson
Intended status: Informational Young Lee (Ed) Intended status: Informational Young Lee (Ed)
Expires: April 18, 2018 Huawei Expires: April 27, 2018 Huawei
October 18, 2017 October 27, 2017
Framework for Abstraction and Control of Traffic Engineered Networks Framework for Abstraction and Control of Traffic Engineered Networks
draft-ietf-teas-actn-framework-10 draft-ietf-teas-actn-framework-11
Abstract Abstract
Traffic Engineered networks have a variety of mechanisms to Traffic Engineered networks have a variety of mechanisms to
facilitate the separation of the data plane and control plane. They facilitate the separation of the data plane and control plane. They
also have a range of management and provisioning protocols to also have a range of management and provisioning protocols to
configure and activate network resources. These mechanisms configure and activate network resources. These mechanisms
represent key technologies for enabling flexible and dynamic represent key technologies for enabling flexible and dynamic
networking. networking.
skipping to change at page 2, line 7 skipping to change at page 2, line 7
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 18, 2018. This Internet-Draft will expire on April 27, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 13, line 9 skipping to change at page 13, line 5
A Customer Network Controller (CNC) is responsible for communicating A Customer Network Controller (CNC) is responsible for communicating
a customer's VNS requirements to the network provider over the CNC- a customer's VNS requirements to the network provider over the CNC-
MDSC Interface (CMI). It has knowledge of the end-points associated MDSC Interface (CMI). It has knowledge of the end-points associated
with the VNS (expressed as APs), the service policy, and other QoS with the VNS (expressed as APs), the service policy, and other QoS
information related to the service. information related to the service.
As the Customer Network Controller directly interfaces to the As the Customer Network Controller directly interfaces to the
applications, it understands multiple application requirements and applications, it understands multiple application requirements and
their service needs. their service needs.
The capability of a CNC beyond its CMI role is outside the scope of
ACTN and may be implemented in different ways. For example, the CNC
may in fact be a controller or part of a controller in the customer's
domain, or the CNC functionality could also be implemented as part of
a provisioning portal.
3.2. Multi-Domain Service Coordinator 3.2. Multi-Domain Service Coordinator
A Multi-Domain Service Coordinator (MDSC) is a functional block that A Multi-Domain Service Coordinator (MDSC) is a functional block that
implements all of the ACTN functions listed in Section 3 and implements all of the ACTN functions listed in Section 3 and
described further in Section 4.2. The two functions of the MDSC, described further in Section 4.2. The two functions of the MDSC,
namely, multi domain coordination and virtualization/abstraction are namely, multi domain coordination and virtualization/abstraction are
referred to as network-related functions while the other two referred to as network-related functions while the other two
functions, namely, customer mapping/translation and virtual service functions, namely, customer mapping/translation and virtual service
coordination are referred to as service-related functions. The MDSC coordination are referred to as service-related functions. The MDSC
sits at the center of the ACTN model between the CNC that issues sits at the center of the ACTN model between the CNC that issues
 End of changes. 5 change blocks. 
4 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/