< draft-wu-model-driven-management-virtualization-02.txt   draft-wu-model-driven-management-virtualization-03.txt >
Networking Working Group Q. Wu Networking Working Group Q. Wu
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Informational M. Boucadair Intended status: Informational M. Boucadair
Expires: September 9, 2019 Orange Expires: September 12, 2019 Orange
Y. Lee Y. Lee
Huawei Huawei
March 8, 2019 March 11, 2019
Framework for Automating Service and Network Management with YANG Framework for Automating Service and Network Management with YANG
draft-wu-model-driven-management-virtualization-02 draft-wu-model-driven-management-virtualization-03
Abstract Abstract
Model driven service and network management provides a programmatic Model driven service and network management provides a programmatic
and standards-based way of representing virtual services or networks and standards-based way of representing virtual services or networks
and configuration to the network device that are used to construct and configuration to the network device that are used to construct
the service. It can be used at various phases of service and network the service. It can be used at various phases of service and network
management life cycle such as service instantiation, service management life cycle such as service instantiation, service
provision, optimization, monitoring, and diagnostic. Also, it can be provision, optimization, monitoring, and diagnostic. Also, it can be
designed to automate network management and provide closed-loop designed to automate network management and provide closed-loop
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 9, 2019. This Internet-Draft will expire on September 12, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 3, line 13 skipping to change at page 3, line 13
7.2. Customer initiated Dynamic Resource Creation . . . . . . 24 7.2. Customer initiated Dynamic Resource Creation . . . . . . 24
8. Security Considerations . . . . . . . . . . . . . . . . . . . 26 8. Security Considerations . . . . . . . . . . . . . . . . . . . 26
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 27 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 27
11. Informative References . . . . . . . . . . . . . . . . . . . 27 11. Informative References . . . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
1. Introduction 1. Introduction
The manage system usually comprise service activation/provision The manage system usually comprises service activation/provision
system and service enforcement system. Tranditional service delivery system and service enforcement system. Tranditional service delivery
work flow, from customer order to practical service provision, the work flow, from customer order to practical service provision, the
work flow process typically involves inputting data sequentially into work flow process typically involves inputting data sequentially into
multiple OSS/BSS applications managed by different departments; Many multiple OSS/BSS applications managed by different departments; Many
of these applications are custom built over the years and operating of these applications are custom built over the years and operating
in silo mode; Lacking of standard data input/output also causes lots in silo mode; Lacking of standard data input/output also causes lots
of challenge in system integration and results in manual data entry; of challenge in system integration and results in manual data entry;
Customer MACD(Move, Add, Change, Delete) will incur the same Customer MACD(Move, Add, Change, Delete) will incur the same
repetitive process in many cases. Secondly traditional service repetitive process in many cases. Secondly traditional service
fulfill system lack a programmatic and standards-based way of writing fulfill system lack a programmatic and standards-based way of writing
skipping to change at page 27, line 8 skipping to change at page 27, line 8
o ...tbc o ...tbc
9. IANA Considerations 9. IANA Considerations
There are no IANA requests or assignments included in this document. There are no IANA requests or assignments included in this document.
10. Contributors 10. Contributors
Shunsuke Homma Shunsuke Homma
NTT
Japan Japan
Email: shunsuke.homma.fp@hco.ntt.co.jp Email: s.homma0718+ietf@gmail.com
11. Informative References 11. Informative References
[I-D.arkko-arch-virtualization] [I-D.arkko-arch-virtualization]
Arkko, J., Tantsura, J., Halpern, J., and B. Varga, Arkko, J., Tantsura, J., Halpern, J., and B. Varga,
"Considerations on Network Virtualization and Slicing", "Considerations on Network Virtualization and Slicing",
draft-arkko-arch-virtualization-01 (work in progress), draft-arkko-arch-virtualization-01 (work in progress),
March 2018. March 2018.
[I-D.asechoud-netmod-diffserv-model] [I-D.asechoud-netmod-diffserv-model]
 End of changes. 7 change blocks. 
7 lines changed or deleted 6 lines changed or added

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