Use Cases for SF Aware Topology Models
draft-bryskin-teas-use-cases-sf-aware-topo-model-02
Network Working Group I. Bryskin
Internet-Draft Huawei Technologies
Intended status: Informational X. Liu
Expires: September 3, 2018 Jabil
J. Guichard
Y. Lee
Huawei Technologies
L. Contreras
Telefonica
D. Ceccarelli
Ericsson
March 2, 2018
Use Cases for SF Aware Topology Models
draft-bryskin-teas-use-cases-sf-aware-topo-model-02
Abstract
This document describes some use cases that benefit from the network
topology models that are service and network function aware.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 3, 2018.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Bryskin, et al. Expires September 3, 2018 [Page 1]
Internet-Draft Use Cases for SF Aware Topo Models March 2018
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Exporting SF/NF Information to Network Clients and Other
Network SDN Controllers . . . . . . . . . . . . . . . . . . . 4
4. Flat End-to-end SFCs Managed on Multi-domain Networks . . . 5
5. Managing SFCs with TE Constraints . . . . . . . . . . . . . . 6
6. SFC Protection and Load Balancing . . . . . . . . . . . . . . 7
7. Network Clock Synchronization . . . . . . . . . . . . . . . . 10
8. Client - Provider Network Slicing Interface . . . . . . . . . 10
9. Dynamic Assignment of Regenerators for L0 Services . . . . . 10
10. Dynamic Assignment of OAM Functions for L1 Services . . . . . 12
11. SFC Abstraction and Scaling . . . . . . . . . . . . . . . . . 13
12. Dynamic Compute/VM/Storage Resource Assignment . . . . . . . 13
13. Application-aware Resource Operations and Management . . . . 14
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
15. Security Considerations . . . . . . . . . . . . . . . . . . . 15
16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
17.1. Normative References . . . . . . . . . . . . . . . . . . 15
17.2. Informative References . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
Normally network connectivity services are discussed as a means to
inter-connect various abstract or physical network topological
elements, such as ports, link termination points and nodes
[I-D.ietf-teas-yang-te-topo] [I-D.ietf-teas-yang-te]. However, the
connectivity services, strictly speaking, interconnect not the
network topology elements per-se, rather, located on/associated with
the various network and service functions [RFC7498] [RFC7665]. In
many scenarios it is beneficial to decouple the service/network
functions from the network topology elements hosting them, describe
them in some unambiguous and identifiable way (so that it would be
Show full document text