[Search] [txt|pdf|bibtex] [Tracker] [Email] [Nits]

Versions: 00 01 02 03                                                   
Network Working Group                                        R. Atarashi
Internet-Draft                            Internet Initiative Japan Inc.
Expires: January 10, 2005                                     T. Shimojo
                                           Nara Institute of Science and
                                                              Technology
                                                             Y. Atarashi
                                                               M. Kitani
                                                          Hitachi, Ltd.,
                                                                F. Baker
                                                           Cisco Systems
                                                           July 12, 2004


                       Netconf Architecture Model
              draft-atarashi-netconfmodel-architecture-00

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   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 10, 2005.

Copyright Notice

   Copyright (C) The Internet Society (2004).  All Rights Reserved.

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
   tools but the concept is confusable.  The consensus of architecture



Atarashi, et al.        Expires January 10, 2005                [Page 1]


Internet-Draft                  Document                       July 2004


   is required to clarify the items and technologies that should be
   discussed and standardized at IETF.

















































Atarashi, et al.        Expires January 10, 2005                [Page 2]


Internet-Draft                  Document                       July 2004


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.

   As such, we will make specific recommendations for all applications.
   In doing so, we will use the language described in RFC 2119 [1].  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 [1].





































Atarashi, et al.        Expires January 10, 2005                [Page 3]


Internet-Draft                  Document                       July 2004


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.  [2] (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 10, 2005                [Page 4]


Internet-Draft                  Document                       July 2004


3.  Current Tools

   This is the list for current tools and technologies that is available
   for network configuration.  See reference for details.

   o  Resource Description
      *  Resource Description Framework Resource Description Framework
         [3]
      *  XML Scheme
      *  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) Unified Modeling Language [4]
   o  Configuration Protocol
      *  SOAP
      *  BEEP
   o  Security Protection
      *  ssh
      *  SSL
      *  IPsec
      *  XML Signature



























Atarashi, et al.        Expires January 10, 2005                [Page 5]


Internet-Draft                  Document                       July 2004


4.  Architecture

   Figure 1 presents a proposed architecture for network configuration
   using XML and related concepts and technologies.



   +------------------------------------------------------------+
   | XML           +------+               +--------+ Data       |
   | Configuration |Visual|<------------->|XML     | Model      |
   | System        |Design| +--------+    |Database| and        |
   |               |Tool  | |RDF     |    |(Policy,| Description|
   |               +--+---+ |Metadata|    | rules, |            |
   |                  |     +--------+    | Device,|            |
   |                  |                   | etc.   |            |
   |                  |                   +---+----+            |
   |                  |                       |                 |
   |                  |     +----------+      |                 |
   |                  +---->|XML Config|<-----+                 |
   |                        |Controller|                        |
   |                        +-+---+--+-+                        |
   +-------------------------/-----\--\-------------------------+
                            /       \  \ Config by
                           /         \  \ XML        +-----+
     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   |
   +------------------------------------------------------------+




Atarashi, et al.        Expires January 10, 2005                [Page 6]


Internet-Draft                  Document                       July 2004


   Figure 1: netconf architecture model


















































Atarashi, et al.        Expires January 10, 2005                [Page 7]


Internet-Draft                  Document                       July 2004


5.  Deployment Story

   The deployment story is required to deploy the architecture.  This is
   our proposal.

   o  Phase 1: router and switch conf for ISP/career.
   o  Phase 1.5: router and switch conf for enterprise.
   o  Phase 2: SOHO home router and appliance control.
   o  Phase 3: mobile application and so on.










































Atarashi, et al.        Expires January 10, 2005                [Page 8]


Internet-Draft                  Document                       July 2004


6.  IANA Considerations

   No action has been requested of IANA.
















































Atarashi, et al.        Expires January 10, 2005                [Page 9]


Internet-Draft                  Document                       July 2004


7.  Security Considerations

   This document discusses motivation and architecture of XML network
   management.  If implemented as described, it should ask the network
   to do nathing that the network has already allowd.  If that is the
   case, no new security issues should arise from the use of such a
   architecture.

8  References

   [1]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

   [2]  <http://www.dmtf.org/>

   [3]  <http://www.w3.org/RDF/>

   [4]  <http://www.omg.org/uml/>


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
   8916-5 Takayama
   Ikoma, Nara  630-0101
   JP

   Phone: +81-743-72-5210
   Fax:   +81-743-72-5291
   EMail: toshio-s@is.aist-nara.ac.jp









Atarashi, et al.        Expires January 10, 2005               [Page 10]


Internet-Draft                  Document                       July 2004


   Yoshifumi Atarashi
   Hitachi, Ltd.,
   1 Horiyamashita
   Hadano, Kanagawa  259-1392
   JP

   Phone: +81-463-87-7496
   Fax:   +81-463-88-8062
   EMail: atarashi@ebina.hitachi.co.jp


   Makoto Kitani
   Hitachi, Ltd.,
   1 Horiyamashita
   Hadano, Kanagawa  259-1392
   JP

   Phone: +81-463-87-7496
   Fax:   +81-463-88-8062
   EMail: makoto.kitani@itg.hitachi.co.jp


   Fred Baker
   Cisco Systems
   1121 Via Del Rey
   Santa Barbara, CA  93117
   US

   Phone: +1-408-526-4257
   Fax:   +1-413-473-2403
   EMail: fred@cisco.com




















Atarashi, et al.        Expires January 10, 2005               [Page 11]


Internet-Draft                  Document                       July 2004


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   intellectual property 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; neither does it represent that it
   has made any effort to identify any such rights.  Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11.  Copies of
   claims of rights made available for publication 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 implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard.  Please address the information to the IETF Executive
   Director.


Full Copyright Statement

   Copyright (C) The Internet Society (2004).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assignees.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION



Atarashi, et al.        Expires January 10, 2005               [Page 12]


Internet-Draft                  Document                       July 2004


   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.











































Atarashi, et al.        Expires January 10, 2005               [Page 13]