draft-ietf-teas-actn-requirements-02.txt   draft-ietf-teas-actn-requirements-03.txt 
Network Working Group Young Lee (Editor) Network Working Group Young Lee (Editor)
Dhruv Dhody Dhruv Dhody
Internet Draft Huawei Internet Draft Huawei
Intended status: Informational Sergio Belotti Intended status: Informational Sergio Belotti
Alcatel-Lucent Alcatel-Lucent
Expires: October 2016 Expires: January 2017
Khuzema Pithewan Khuzema Pithewan
Infinera Infinera
Daniele Ceccarelli Daniele Ceccarelli
Ericsson Ericsson
April 13, 2016 July 6, 2016
Requirements for Abstraction and Control of TE Networks Requirements for Abstraction and Control of TE Networks
draft-ietf-teas-actn-requirements-02.txt draft-ietf-teas-actn-requirements-03.txt
Abstract Abstract
This draft provides a set of requirements for abstraction and This draft provides a set of requirements for abstraction and
control of TE networks. control of TE networks.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
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 October 13, 2016. This Internet-Draft will expire on January 6, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
skipping to change at page 3, line 14 skipping to change at page 3, line 14
so as to facilitate network programmability, automation, efficient so as to facilitate network programmability, automation, efficient
resource sharing, and end-to-end virtual service aware connectivity resource sharing, and end-to-end virtual service aware connectivity
and network function virtualization services. and network function virtualization services.
These operations are summarized as follows: These operations are summarized as follows:
- Abstraction and coordination of underlying network resources - Abstraction and coordination of underlying network resources
to higher-layer applications and customers, independent of how to higher-layer applications and customers, independent of how
these resources are managed or controlled, so that these these resources are managed or controlled, so that these
higher-layer entities can dynamically control virtual higher-layer entities can dynamically control virtual
networks. Where control includes creating, modifying, networks. Control includes creating, modifying,
monitoring, and deleting virtual networks. monitoring, and deleting virtual networks.
- Multi-domain and multi-tenant virtual network operations via - Multi-domain and multi-tenant virtual network operations via
hierarchical abstraction of TE domains that facilitates hierarchical abstraction of TE domains that facilitates
multi-administration, multi-vendor, and multi-technology multi-administration, multi-vendor, and multi-technology
networks as a single virtualized network. This is achieved by networks as a single virtualized network. This is achieved by
presenting the network domain as an abstracted topology to the presenting the network domain as an abstracted topology to the
customers via open and programmable interfaces. Which allows customers via open and programmable interfaces. Hierarchical
for the recursion of controllers in a customer-provider abstraction allows for the recursion of controllers in a
relationship. customer-provider relationship.
- Orchestration of end-to-end virtual network services and - Orchestration of end-to-end virtual network services and
applications via allocation of network resources to meet applications via allocation of network resources to meet
specific service, application and customer requirements. specific service, application and customer requirements.
- Adaptation of customer requests (made on virtual resources) to - Adaptation of customer requests (made on virtual resources) to
the physical network resources performing the necessary the physical network resources performing the necessary
mapping, translation, isolation and, policy that allows mapping, translation, isolation and, policy that allows
conveying, managing and enforcing customer policies with conveying, managing and enforcing customer policies with
respect to the services by the network to said customer. respect to the services by the network to said customer.
skipping to change at page 4, line 22 skipping to change at page 4, line 22
Ability to build virtual network operation infrastructure based Ability to build virtual network operation infrastructure based
on multi-layer, multi-domain topology abstracted from multiple on multi-layer, multi-domain topology abstracted from multiple
physical network controllers (e.g., GMPLS, OpenFlow, PCE, NMS, physical network controllers (e.g., GMPLS, OpenFlow, PCE, NMS,
etc.) etc.)
Reference: [KLEE], [LOPEZ], [DHODY], [CHENG]. Reference: [KLEE], [LOPEZ], [DHODY], [CHENG].
2. Requirement 2: Policy Enforcement 2. Requirement 2: Policy Enforcement
Ability to provide service requirement/policy (Between Customer Ability to provide service requirement/policy (between Customer
and Network) and mechanism to enforce service level agreement. and Network) and mechanism to enforce service level agreement.
- Endpoint selection policy, routing policy, time-related - Endpoint selection policy, routing policy, time-related
policy, etc. policy, etc.
Reference: [KLEE], [LOPEZ], [SHIN], [DHODY], [FANG]. Reference: [KLEE], [LOPEZ], [SHIN], [DHODY], [FANG].
3. Requirement 3: VN Query 3. Requirement 3: VN Query
Ability to request/respond VN Query (Can you give me VN(s)?) Ability to request/respond VN Query (Can you give me VN(s)?)
skipping to change at page 7, line 10 skipping to change at page 7, line 10
- Service-policy primitives and its parameters - Service-policy primitives and its parameters
Reference: [FANG], [LOPEZ], [SHIN]. Reference: [FANG], [LOPEZ], [SHIN].
9. Requirement 9: Multi-domain & Multi-layer Coordination 9. Requirement 9: Multi-domain & Multi-layer Coordination
Ability to Coordinate multi-domain and multi-layer path Ability to Coordinate multi-domain and multi-layer path
computation and setup operation (network) computation and setup operation (network)
- Computes E2E path across multi-domain (based on abstract - E2E path computation across multi-domain (based on abstract
topology from each domain) topology from each domain)
- Determines the domain sequence - The domain sequence determination
- Request path signaling to each domain controller - Request for path signaling to each domain controller
- Find alternative path if any of the domain controllers cannot - Alternative path computation if any of the domain controllers
find its domain path cannot find its domain path
Reference: [CHENG], [DHODY], [KLEE], [LOPEZ], [SHIN], [SUZUKI]. Reference: [CHENG], [DHODY], [KLEE], [LOPEZ], [SHIN], [SUZUKI].
10. Requirement 10: E2E Path Restoration 10. Requirement 10: E2E Path Restoration
Ability to perform E2E Path Restoration Operation Ability to perform E2E Path Restoration Operation
- Intra-domain recovery - Intra-domain recovery
- Cross-domain recovery - Cross-domain recovery
skipping to change at page 10, line 22 skipping to change at page 10, line 22
and latency for each VN service). and latency for each VN service).
o VN diversity/survivability should be met in physical network o VN diversity/survivability should be met in physical network
mapping. mapping.
o VN confidentiality and sharing constraint should be supported. o VN confidentiality and sharing constraint should be supported.
- [LOPEZ] (ACTN Use-case for Virtual Network Operation for Multiple - [LOPEZ] (ACTN Use-case for Virtual Network Operation for Multiple
Domains in a Single Operator Network) Domains in a Single Operator Network)
o Creation of a global abstraction of network topology: The VNO o Creation of a global abstraction of network topology: The VNO
Coordinator assembles each domain level abstraction of Coordinator assembles each domain level abstraction of
network topology into a global abstraction of the end-to- network topology into a global abstraction of the end-to-end
endnetwork. network.
o End-to-end connection lifecycle management o End-to-end connection lifecycle management
o Invocation of path provisioning request to each domain o Invocation of path provisioning request to each domain
(including optimization requests) (including optimization requests)
o Invocation of path protection/reroute to the affected o Invocation of path protection/reroute to the affected
domain(s) domain(s)
o End-to-end network monitoring and fault management. This could o End-to-end network monitoring and fault management. This could
imply potential KPIs and alarm correlation capabilities. imply potential KPIs and alarm correlation capabilities.
o End-to-end accounting and generation of detailed records for o End-to-end accounting and generation of detailed records for
resource usage resource usage
o End-to-end policy enforcement o End-to-end policy enforcement
- [SHIN] (ACTN Use-case for Mobile Virtual Network Operation for - [SHIN] (ACTN Use-case for Mobile Virtual Network Operation for
Multiple Domains in a Single Operator Network) Multiple Domains in a Single Operator Network)
o Resource abstraction: operational mechanisms in mobile o Resource abstraction: operational mechanisms in mobile
backhaul network to give the current network usage backhaul network to give the current network usage
information for dynamic and elastic applications be information for dynamic and elastic applications to be
provisioned dynamically with QoS guarantee. provisioned dynamically with QoS guarantee.
o Load balancing or for recovery, the selection of core DC o Load balancing or for recovery, the selection of core DC
location from edge constitutes a data center selection location from edge constitutes a data center selection
problem. problem.
o Multi-layer routing and optimization, coordination between o Multi-layer routing and optimization, coordination between
these two layers. these two layers.
- [SUZUKI] (Use-case and Requirements for Multi-domain Operation - [SUZUKI] (Use-case and Requirements for Multi-domain Operation
skipping to change at page 21, line 10 skipping to change at page 21, line 10
path setup/connection failure/degradation/restoration path setup/connection failure/degradation/restoration
11. Service-specific Abstract Topology Update per changes due 11. Service-specific Abstract Topology Update per changes due
to new path setup/connection failure/degradation/restoration to new path setup/connection failure/degradation/restoration
12. Abstraction model of technology-specific topology element 12. Abstraction model of technology-specific topology element
5. References 5. References
5.1. Informative References 5.1. Informative References
[ACTN-Frame] D. Ceccarelli, et al., "Framework for Abstraction and [ACTN-Frame] D. Ceccarelli, et al., "Framework for Abstraction and
Control of Transport Networks", draft-ceccarelli-teas- Control of Transport Networks", draft-ietf-teas-actn-
actn-framework, work in progress. framework, work in progress.
[CHENG] W. Cheng, et. al., "ACTN Use-cases for Packet Transport [CHENG] W. Cheng, et. al., "ACTN Use-cases for Packet Transport
Networks in Mobile Backhaul Networks", draft-cheng-actn- Networks in Mobile Backhaul Networks", draft-cheng-actn-
ptn-requirements, work in progress. ptn-requirements, work in progress.
[DHODY] D. Dhody, et. al., "Packet Optical Integration (POI) Use [DHODY] D. Dhody, et. al., "Packet Optical Integration (POI) Use
Cases for Abstraction and Control of Transport Networks Cases for Abstraction and Control of Transport Networks
(ACTN)", draft-dhody-actn-poi-use-case, work in progress. (ACTN)", draft-dhody-actn-poi-use-case, work in progress.
[FANG] L. Fang, "ACTN Use Case for Multi-domain Data Center [FANG] L. Fang, "ACTN Use Case for Multi-domain Data Center
skipping to change at page 23, line 5 skipping to change at page 23, line 5
Huawei Technologies Huawei Technologies
5340 Legacy Drive 5340 Legacy Drive
Plano, TX 75023, USA Plano, TX 75023, USA
Phone: (469)277-5838 Phone: (469)277-5838
Email: leeyoung@huawei.com Email: leeyoung@huawei.com
Dhruv Dhody Dhruv Dhody
Huawei Technologies Huawei Technologies
Email: dhruv.ietf@gmail.com Email: dhruv.ietf@gmail.com
Sergio Belotti Sergio Belotti
Alcatel Lucent Nokia
Via Trento, 30 Via Trento, 30
Vimercate, Italy Vimercate, Italy
Email: sergio.belotti@alcatel-lucent.com Email: sergio.belotti@nokia.com
Khuzema Pithewan Khuzema Pithewan
Infinera Infinera
Email: kpithewan@infinera.com Email: kpithewan@infinera.com
Daniele Ceccarelli Daniele Ceccarelli
Ericsson Ericsson
Torshamnsgatan,48 Torshamnsgatan,48
Stockholm, Sweden Stockholm, Sweden
Email: daniele.ceccarelli@ericsson.com Email: daniele.ceccarelli@ericsson.com
 End of changes. 17 change blocks. 
22 lines changed or deleted 22 lines changed or added

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