draft-ietf-teas-actn-requirements-01.txt   draft-ietf-teas-actn-requirements-02.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: April 2016 Expires: October 2016
Khuzema Pithewan Khuzema Pithewan
Infinera Infinera
Daniele Ceccarelli Daniele Ceccarelli
Ericsson Ericsson
October 1, 2015 April 13, 2016
Requirements for Abstraction and Control of TE Networks Requirements for Abstraction and Control of TE Networks
draft-ietf-teas-actn-requirements-01.txt draft-ietf-teas-actn-requirements-02.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 1, 2016. This Internet-Draft will expire on October 13, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 2, line 31 skipping to change at page 2, line 31
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................2
2. High-level ACTN requirements...................................4 2. High-level ACTN requirements...................................4
3. ACTN Use-Cases.................................................8 3. ACTN Use-Cases.................................................8
3.1. Two categories of requirements...........................11 3.1. Two categories of requirements...........................11
4. ACTN interfaces requirements..................................15 4. ACTN interfaces requirements..................................15
4.1. CMI Interface Requirements...............................16 4.1. CMI Requirements.........................................16
4.2. MPI (MDSC-PNC Interface).................................18 4.2. MPI Requirements.........................................18
5. References....................................................21 5. References....................................................21
5.1. Informative References...................................21 5.1. Informative References...................................21
6. Contributors..................................................22 6. Contributors..................................................22
Contributors' Addresses..........................................22 Contributors' Addresses..........................................22
Authors' Addresses...............................................22 Authors' Addresses...............................................22
1. Introduction 1. Introduction
This draft provides a set of requirements for Abstraction and This draft provides a set of requirements for Abstraction and
Control of TE Networks (ACTN) identified in various use-cases of Control of TE Networks (ACTN) identified in various use-cases of
skipping to change at page 16, line 4 skipping to change at page 16, line 4
abstraction. abstraction.
4. ACTN interfaces requirements 4. ACTN interfaces requirements
This section provides detailed ACTN interface requirements for the This section provides detailed ACTN interface requirements for the
two interfaces that are within the ACTN scope based on [ACTN-Frame] two interfaces that are within the ACTN scope based on [ACTN-Frame]
and the use-cases referenced in this document. and the use-cases referenced in this document.
. CMI: CNC-MDSC Interface . CMI: CNC-MDSC Interface
. MPI: MDSC-PNC Interface . MPI: MDSC-PNC Interface
4.1. CMI Interface Requirements 4.1. CMI Requirements
Requirement Requirement
1. Security/Policy Negotiation (Who are you?) (Between CNC and 1. Security/Policy Negotiation (Who are you?) (Between CNC and
MDSC) MDSC)
- Configured vs. Discovered - Configured vs. Discovered
- Trust domain verification (External Entity vs. Internal - Trust domain verification (External Entity vs. Internal
Service Department) Service Department)
- Push/Pull support (for policy) - Push/Pull support (for policy)
2. VN Topology Query (Can you give me VN?) (From CNC to MDSC) 2. VN Topology Query (Can you give me VN?) (From CNC to MDSC)
- VN end-points (CE end) - VN end-points (CE end)
skipping to change at page 18, line 23 skipping to change at page 18, line 23
8. VN lifecycle management/operation 8. VN lifecycle management/operation
- Create (same as VN instantiate Request) - Create (same as VN instantiate Request)
- Delete - Delete
- Modify - Modify
- Update (VN level OAM Monitoring) under policy agreement - Update (VN level OAM Monitoring) under policy agreement
9. Coordination of multi-destination service requirement/policy 9. Coordination of multi-destination service requirement/policy
to support dynamic applications such as VM migration, to support dynamic applications such as VM migration,
disaster recovery, load balancing, etc. disaster recovery, load balancing, etc.
- Service-policy primitives and its parameters - Service-policy primitives and its parameters
4.2. MPI (MDSC-PNC Interface) 4.2. MPI Requirements
Requirement Requirement
1. Security/Policy negotiation (who are you?) 1. Security/Policy negotiation (who are you?)
- Exchange of key, etc. - Exchange of key, etc.
- Domain preference + local policy exchange - Domain preference + local policy exchange
- Push/Pull support - Push/Pull support
- Preferred peering points - Preferred peering points
- Preferred route - Preferred route
- Reroute policy - Reroute policy
- End-point mobility (for multi-destination) - End-point mobility (for multi-destination)
 End of changes. 7 change blocks. 
8 lines changed or deleted 8 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/