Internet DRAFT - draft-jxf-i2rs-im-architecture
draft-jxf-i2rs-im-architecture
Network Working Group X. Ji
Internet-Draft G. Yan
Intended status: Experimental Huawei Technologies
Expires: April 21, 2014 Y. Jin
SJTU
October 21, 2013
An information model atchitecture of network device
draft-jxf-i2rs-im-architecture-01
Abstract
Currently, network equipment already has some Northbound Interfaces,
such as SNMP, NETCONF, TL1; and some languages are also provided to
describe the data model, such as MIB, SCHEMA and even YANG. While
till now, there is not a clear defined information model. In NETCONF
domain, some standards are being defined. In order to reduce the
cost of NMS integration in customer side, a clear defined information
model is necessary, just like the SID in TMF.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
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 April 21, 2014.
Ji, et al. Expires April 21, 2014 [Page 1]
Internet-Draft Network Information Model October 2013
Copyright Notice
Copyright (c) 2013 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
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. The overview of information model of network equipment . . . 3
2.1. The infrastructure plane . . . . . . . . . . . . . . . . 3
2.2. The network service plane . . . . . . . . . . . . . . . . 4
3. The layer . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. System Inventory Objects Layer . . . . . . . . . . . . . 4
3.2. The System Management Layer . . . . . . . . . . . . . . . 4
3.3. The network container layer . . . . . . . . . . . . . . . 4
3.4. The network policy layer . . . . . . . . . . . . . . . . 5
3.5. The network resource layer . . . . . . . . . . . . . . . 5
3.6. The network protocol layer . . . . . . . . . . . . . . . 5
3.7. The network service layer . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
7. Normative References . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
Currently, network equipment already has some Northbound Interfaces,
such as SNMP, NETCONF, TL1; and some languages are also provided to
describe the data model, such as MIB, SCHEMA and even YANG. While
till now, there is not a clear defined information model. In NETCONF
domain, some standards are being defined. In order to reduce the
cost of NMS integration in customer side, a clear defined information
model is necessary, just like the SID in TMF.
In order to understand the difference between information model and
data model, please refer to the RFC3444.
Ji, et al. Expires April 21, 2014 [Page 2]
Internet-Draft Network Information Model October 2013
This document will introduce a set of information models. We hope
this model could help the engineer define the model of network
service described by SCHEMA or YANG.
2. The overview of information model of network equipment
This information model is very important. All interfaces design and
implementation will use this model, such as MIB, Schema and TL1, even
RESTful API.
The following figure illustrates the architecture of this information
model:
P--------------------------------------------------------------------
| Network Service Plane
| L---------------------------------------------------------------
| | Network Service Layer
| L---------------------------------------------------------------
| | Network Protocol Layer
| L---------------------------------------------------------------
| | Network Resource Layer
| L---------------------------------------------------------------
| | Network Policy Layer
| L---------------------------------------------------------------
| | Network Continer Layer
| +---------------------------------------------------------------
P -------------------------------------------------------------------
| Infrastructure Plane
| L---------------------------------------------------------------
| | System Management Layer
| L---------------------------------------------------------------
| | System Inventory Objects Layer (Software and Hardware)
| +---------------------------------------------------------------
| -------------------------------------------------------------------
2.1. The infrastructure plane
The infrastructure plane provides a minimum set of functions to
support the running system, And this plane can be deployed
independently, which will not be affected by upper layer.
This plane also provides the API to operate the hardware and
software, such as software installation, upgrade, and so on.
It has no relation with IP associated service and can be applied to
other embedded system device.
Ji, et al. Expires April 21, 2014 [Page 3]
Internet-Draft Network Information Model October 2013
2.2. The network service plane
The network service plane provides the model definition of all
network communication services, which can be divided into five
layers: Service Layer, Protocol Layer, Resource Layer, Policy Layer
and Container Layer. Based on the interfaces provided by
infrastructure plane, all network services can be distributed on some
deployment units that can be main board, I/O board or one CPU of
multiple CPUs system.
3. The layer
3.1. System Inventory Objects Layer
L--------------------------------------------------------------------------
| System Inventory Objects Layer
| M----------------+ M-------------+ M-------------+ M----------------+
| | Logical System | | Device Mgmt.| | File System | | Component Mgmt.|
| +----------------+ +-------------+ +-------------+ +----------------+
+--------------------------------------------------------------------------
The system inventory Layer provides the model definition to manage
all hardware, logical device or virtual system, it include device
management, file management, the system component management.
3.2. The System Management Layer
L--------------------------------------------------------------------------
| System Management Layer
| M-------------+ M-------------------------+ M---------------------+
| | System Info | | Softwate Install&Update | | Sys Porcess Monitor |
| +-------------+ +-------------------------+ +---------------------+
+--------------------------------------------------------------------------
This layer provides the model of OS, like software installation,
upgrade, like the monitor of system process. The function of some
basic MIB will be placed here, such as the system MIB of RFC1213.
3.3. The network container layer
Ji, et al. Expires April 21, 2014 [Page 4]
Internet-Draft Network Information Model October 2013
L--------------------------------------------------------------------------
| Network Container Layer
| M-------+ M-------+ M------+
| | L3VPN | | L2VPN | | VLAN |
| +-------+ +-------+ +------+
+--------------------------------------------------------------------------
The container layer is defined to support some network level object
and provides the key of network, or virtual network, and some top
level attribute, such as ID, NAME, TYPE, and so on.
3.4. The network policy layer
L--------------------------------------------------------------------------
| Network Policy Layer
| M-----+ M--------------+ M------------+
| | ACL | | Route Policy | | QoS Policy |
| +-----+ +--------------+ +------------+
+--------------------------------------------------------------------------
This layer defines the network security, Quality of Service, Route
policy.
3.5. The network resource layer
L--------------------------------------------------------------------------
| Network Resource Layer
| M-----------------+ M--------------+ M-----------------+ M------+
| | Interface Mgmt. | | Tunnle Mgmt. | | QoS Queue Mgmt. | | Topo |
| +-----------------+ +--------------+ +-----------------+ +------+
+--------------------------------------------------------------------------
The network resource layer manages the resource, such as interface,
tunnel, and topology.
3.6. The network protocol layer
L--------------------------------------------------------------------------
| Network Protocol Layer
| M------------------+ M-------------+ M-------------------------+
| | Routing Protocol | | L2 Protocol | | Management APP Protocol |
| +------------------+ +-------------+ +-------------------------+
+--------------------------------------------------------------------------
Ji, et al. Expires April 21, 2014 [Page 5]
Internet-Draft Network Information Model October 2013
This layer includes the model of almost all functions supported by
current network device, like the routing protocol, L2 protocol, MPLS
and associated protocol, even all management protocol, like SNMP,
Telnet.
3.7. The network service layer
L--------------------------------------------------------------------------
| Network Service Layer
| M----------------------+ M--------------+ M-------------+
| | Built-in Service APP | | SLA TOOL APP | | OM TOOL APP |
| +----------------------+ +--------------+ +-------------+
+--------------------------------------------------------------------------
The network service layer includes the model of service or
application level, like SLA tools application, this application face
the requirement of the end user, not the network protocol. Normally,
this layer is not distributed in the network device, but sometimes,
there are some built-in applications, like NQA.
The module in this layer cannot depend each other and can only depend
on the bottom layer.
4. Security Considerations
NA
5. IANA Considerations
NA
6. Acknowledgements
NA
7. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between
Information Models and Data Models", RFC 3444, January
2003.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010.
Ji, et al. Expires April 21, 2014 [Page 6]
Internet-Draft Network Information Model October 2013
[RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021,
October 2010.
[RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A.
Bierman, "Network Configuration Protocol (NETCONF)", RFC
6241, June 2011.
Authors' Addresses
Xiaofeng Ji
Huawei Technologies
Huawei Bld., No.156 Beiqing Rd.
Beijing 100095
China
Email: jixiaofeng@huawei.com
Yaohui Jin
Shanghai Jiao Tong University
China
Email: jinyh@sjtu.edu.cn
Gang Yan
Huawei Technologies
Huawei Bld., No.156 Beiqing Rd.
Beijing 100095
China
Email: yangang@huawei.com
Ji, et al. Expires April 21, 2014 [Page 7]
