Network Working Group R. Atarashi
Internet-Draft Internet Initiative Japan Inc.
Expires: January 15, 2006 T. Shimojo
Nara Institute of Science and
Technology/Alaxala Networks, Corp.
Y. Atarashi
M. Kitani
Alaxala Networks, Corp.
July 14, 2005
Netconf Architecture Model
draft-atarashi-netconfmodel-architecture-02
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 15, 2006.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
For the new network configuration concept discussed at NETCONF, we
mention the importance of building new network architecture. We can
not develop and discuss the concept using XML because it is only
Atarashi, et al. Expires January 15, 2006 [Page 1]
Internet-Draft Document July 2005
tools but the concept is confusable. The consensus of architecture
is required to clarify the items and technologies that should be
discussed and standardized at IETF.
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].
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Proposal . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Related Components . . . . . . . . . . . . . . . . . . . . . 5
4. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 7
5. System Architecture . . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . 11
8. Normative References . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . 13
Atarashi, et al. Expires January 15, 2006 [Page 2]
Internet-Draft Document July 2005
1. Introduction
For the new network configuration concept discussed at NETCONF, we
mention the importance of building new network architecture. We can
not develop and discuss the concept using XML because it is only
tools but the concept is confusable. The consensus of architecture
is required to clarify the items and technologies that should be
discussed and standardized at IETF.
Atarashi, et al. Expires January 15, 2006 [Page 3]
Internet-Draft Document July 2005
2. Proposal
In the discussion for XML configuration at NETCONF, a global
architecture SHOULD be developed to arrange the technology components
and make common image for configuration. Since XML is only tool, it
can not be defined concept and architecture. The configuration tool
using XML tag without consideration of architecture may be useful at
once, it will obsolete by new technology and standard.
It is useful for the network operator to configure network equipments
and to see MIB information and network configuration using XML. It
is important to discuss SOAP, MIB, security, and so on as tools for
configuration, but is difficult to share the whole image of
requirements. We need to review the global network architecture to
check and confirm the action item.
XML is only tools based on the concept of metadata and RDF, and have
many possibilities for network architecture. We are required to
understand the concept of XML related technologies and to discuss the
application of these technologies for standard. Since XML
technologies are originally defined for contents and applications, it
is also suitable for contents delivery network. We can describe the
network policy using XML. The Distributed Management Task Force,
inc. Distributed Management Task Force, inc. [1] (DMTF) discuss the
XML mapping tool of Common Information Model (CIM). We develop the
whole architecture by including existing concepts and technologies
related network configuration and management.
The global architecture including next generation Internet
technologies such as IPv6 and QoS also involve the new network
architecture. The Migration strategy is required for the new
architecture. Since XML is developed for contents and application,
it has not been considered to apply to the network control. There
are not tools and implementations for network. It is required to
implement some technologies for network configuration such as tools,
APIs, and so on using XML.
Atarashi, et al. Expires January 15, 2006 [Page 4]
Internet-Draft Document July 2005
3. Related Components
This is the list for related components and technologies that are
available for network configuration. Network configuration
architecture needs many kinds of components for abstraction,
description, implementation, operation and others. It is required to
consider each role of these components and clear the topics to be
open issues. See reference for details.
o Resource Description
* Resource Description Framework Resource Description
Framework [2]
* XML Scheme
* Ontology Language (OWL)
* Metadata work
o Description of network devices of policies
* Distributed Management Task Force, inc. (DMTF), Common
Information Model (CIM)
o Topology
* Visual Design Tool
* Unified Modeling Language (UML) <http://www.omg.org/uml/>
o Configuration Protocol
* SSH
* SOAP
* BEEP
o Security Protection
* ssh
* SSL
* IPsec
Atarashi, et al. Expires January 15, 2006 [Page 5]
Internet-Draft Document July 2005
* XML Signature
o Management and Monitor
* SNMP
* sflow
* netflow
Atarashi, et al. Expires January 15, 2006 [Page 6]
Internet-Draft Document July 2005
4. Architecture
Figure 1 presents a proposed architecture for network configuration
system. Network configuration system consists of two parts. One is
Data model and Description part that manage abstract configuration
information. The other is network monitoring and management based on
SNMP. Netconf datamodel(2) collaborate with netconf datamodel(1).
Atarashi, et al. Expires January 15, 2006 [Page 7]
Internet-Draft Document July 2005
+----------------------------------------------------------------+
| Network +------+ +--------+ Data |
| Configuration |Visual|<----------------->|XML | Model |
| System |Design| +------------+ |Database| and |
| |Tool | |netconf | |(Policy,| Description|
| +--+---+ |datamodel(1)| | rules, | |
| | +------------+ | Device,| |
| | | etc. | |
| | +---+----+ |
| | | |
| | +----------+ | |
| +---->|XML Config|<---------+ |
| |Controller| |
| +-+---+--+-+ |
+-------------------------/-----\--\-----------------------------+
/ \ \ netconf protocol
/ \ \ +-----+
ISP Service +----V--+ \ +--------->/ \
Area |Router/| +V------+ / \
|Switch | |Router/| +---------+
+-------+ |Switch | |Home/SOHO|
^ +----+--+ | -PDA |
| | | -Video |
| +-------+ | | -Devices|
| |Router/| | +---------+
| >Switch | |
| /+---+---+ |
| / | |
| / | |
+----------------------/-------------------------------------+
| | / | | |
| Current +------+++ | +---+----+ |
| Management |BB/ | | |SNMP/MIB| |
| System |PolicyDB| | +---+----+ |
| +--------+ | | |
| | | |
| | +---V----+ |
| +--->| NMS | Monitoring/ |
| +--------+ Observation |
| | |
+---------------------------------------|--------------------+
V
netconf datamodel (2)
Figure 1: netconf architecture model
Atarashi, et al. Expires January 15, 2006 [Page 8]
Internet-Draft Document July 2005
5. System Architecture
Figure 2 shows the system architecture for netconfmodel. XML
technologies can describe not only device, logs, and so on, but also
policies. XML technologies can also describe semantics including
relation. If any things are described by XML and stored in XML
database, it can be applied to make device independent configuration.
The configuration can be converted to device dependent configuration
file using netmod API and custom library provided by the vendor.
+---------------------+
(described by XML) | XML database |
Devices ---> | | <--- Policies
Functions ---> | | <--- State information (MIB)
Logs ---> | |
+---------------------+
|
|<--- Scenarios
|
| Description format
V
+---------------------+
| netmod API/library |
+---------------------+
|
V
Device dependent
netconf file
Figure 2: System Architecture
Atarashi, et al. Expires January 15, 2006 [Page 9]
Internet-Draft Document July 2005
6. IANA Considerations
No action has been requested of IANA.
Atarashi, et al. Expires January 15, 2006 [Page 10]
Internet-Draft Document July 2005
7. Security Considerations
This document discusses motivation and architecture of XML network
management. If implemented as described, it should ask the network
to do nothing that the network has already allowed. If that is the
case, no new security issues should arise from the use of such a
architecture.
8. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[1] <http://www.dmtf.org/>
[2] <http://www.w3.org/RDF/>
Authors' Addresses
Ray S. Atarashi
Internet Initiative Japan Inc.
Jinbocho Mitsui Bldg., 1-105 Kanda Jinbo-cho
Chiyoda-ku, Tokyo 101-0051
JP
Phone: +81-3-5205-6464
Fax: +81-3-5205-6466
Email: ray@iijlab.net
Toshio Shimojo
Nara Institute of Science and Technology/Alaxala Networks, Corp.
8916-5 Takayama
Ikoma, Nara 630-0101
JP
Phone: +81-743-72-5210
Fax: +81-743-72-5291
Email: toshio-s@is.naist.jp, shimojou@alaxala.com
Atarashi, et al. Expires January 15, 2006 [Page 11]
Internet-Draft Document July 2005
Yoshifumi Atarashi
Alaxala Networks, Corp.
Shinkawasaki Mitsui Bldg, West Tower 890
Kashimada, Saiwai, Kawasaki, Kanagawa 212-0058
JP
Phone: +81-44-549-1306
Fax: +81-44-549-1272
Email: atarashi@alaxala.net
Makoto Kitani
Alaxala Networks, Corp.
Shinkawasaki Mitsui Bldg, West Tower 890
Kashimada, Saiwai, Kawasaki, Kanagawa 212-0058
JP
Phone: +81-44-549-1306
Fax: +81-44-549-1272
Email: makoto.kitani@alaxala.com
Atarashi, et al. Expires January 15, 2006 [Page 12]
Internet-Draft Document July 2005
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Atarashi, et al. Expires January 15, 2006 [Page 13]