draft-ietf-teas-actn-framework-12.txt   draft-ietf-teas-actn-framework-13.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: October 3, 2018 Huawei Expires: October 3, 2018 Huawei
April 3, 2018 April 3, 2018
Framework for Abstraction and Control of Traffic Engineered Networks Framework for Abstraction and Control of Traffic Engineered Networks
draft-ietf-teas-actn-framework-12 draft-ietf-teas-actn-framework-13
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 represent configure and activate network resources. These mechanisms represent
key technologies for enabling flexible and dynamic networking. The key technologies for enabling flexible and dynamic networking. The
term "Traffic Engineered network" refers to a network that uses any term "Traffic Engineered network" refers to a network that uses any
connection-oriented technology under the control of a distributed or connection-oriented technology under the control of a distributed or
skipping to change at page 5, line 26 skipping to change at page 5, line 26
The ACTN framework described in this document facilitates: The ACTN framework described in this document facilitates:
. Abstraction of the underlying network resources to higher-layer . Abstraction of the underlying network resources to higher-layer
applications and customers [RFC7926]. applications and customers [RFC7926].
. Virtualization of particular underlying resources, whose . Virtualization of particular underlying resources, whose
selection criterion is the allocation of those resources to a selection criterion is the allocation of those resources to a
particular customer, application or service [ONF-ARCH]. particular customer, application or service [ONF-ARCH].
. Network slicing of infrastructure to meet specific customers' . TE Network slicing of infrastructure to meet specific customers'
service requirements. service requirements.
. Creation of an abstract environment allowing operators to view . Creation of an abstract environment allowing operators to view
and control multi-domain networks as a single abstract network. and control multi-domain networks as a single abstract network.
. The presentation to customers of networks as a virtual network . The presentation to customers of networks as a virtual network
via open and programmable interfaces. via open and programmable interfaces.
2.1. Terminology 2.1. Terminology
skipping to change at page 6, line 24 skipping to change at page 6, line 24
. Node: A node is a vertex on the graph representation of a TE . Node: A node is a vertex on the graph representation of a TE
topology. In a physical network topology, a node corresponds topology. In a physical network topology, a node corresponds
to a physical network element (NE) such as a router. In an to a physical network element (NE) such as a router. In an
abstract network topology, a node (sometimes called an abstract abstract network topology, a node (sometimes called an abstract
node) is a representation as a single vertex of one or more node) is a representation as a single vertex of one or more
physical NEs and their connecting physical connections. The physical NEs and their connecting physical connections. The
concept of a node represents the ability to connect from any concept of a node represents the ability to connect from any
access to the node (a link end) to any other access to that access to the node (a link end) to any other access to that
node, although "limited cross-connect capabilities" may also be node, although "limited cross-connect capabilities" may also be
defined to restrict this functionality. Network abstraction defined to restrict this functionality. Network abstraction
may be applied recursively, so a node in one topology may be created by applying abstraction to the nodes in the underlying topology. may be applied recursively, so a node in one topology may be
created by applying abstraction to the nodes in the underlying
topology.
. Link: A link is an edge on the graph representation of a TE . Link: A link is an edge on the graph representation of a TE
topology. Two nodes connected by a link are said to be topology. Two nodes connected by a link are said to be
"adjacent" in the TE topology. In a physical network topology, "adjacent" in the TE topology. In a physical network topology,
a link corresponds to a physical connection. In an abstract a link corresponds to a physical connection. In an abstract
network topology, a link (sometimes called an abstract link) is network topology, a link (sometimes called an abstract link) is
a representation of the potential to connect a pair of points a representation of the potential to connect a pair of points
with certain TE parameters (see [RFC7926] for details). with certain TE parameters (see [RFC7926] for details).
Network abstraction may be applied recursively, so a link in Network abstraction may be applied recursively, so a link in
one topology may be created by applying abstraction to the one topology may be created by applying abstraction to the
 End of changes. 3 change blocks. 
3 lines changed or deleted 5 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/