[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00 01 02

I2RS                                                              D. Liu
Internet-Draft                                                 Hui. Deng
Intended status: Informational                              China Mobile
Expires: August 5, 2013                                         Feb 2013


                    Architecture Discussion of I2RS
                     draft-liu-i2rs-architecture-00

Abstract

   This document discusses the high level architecture of I2RS.

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 August 5, 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.







Liu & Deng               Expires August 5, 2013                 [Page 1]


Internet-Draft              i2rs architecture                   Feb 2013


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Conventions used in this document . . . . . . . . . . . . . . . 4
   3.  Architecture of I2RS  . . . . . . . . . . . . . . . . . . . . . 4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 5
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 5







































Liu & Deng               Expires August 5, 2013                 [Page 2]


Internet-Draft              i2rs architecture                   Feb 2013


1.  Introduction

   This document discusses the high level architecture of I2RS.  As
   illustrated in figure 1, the I2RS architecture is composed by three
   types of building blocks.  The first type of the building block is
   the user of I2RS interface.  The users could be network controllers,
   network management functions, other user applications etc.  The user
   application uses the I2RS interface interacts with the routing
   system.  The second type of the building block is management
   functions.  This include configuration management function and
   security managment function.  The configuration management function
   is used to configure the I2RS interface.  The security function is
   used to enforce the security polices of the I2RS interface.  The
   third type of the building block is routing function.  This build
   block includes routing information base, IP forwarding table etc.
   The routing information base could be accessed by the I2RS users
   using the I2RS interface.

   Figure 1 architecture of I2RS


     +------------------+  +------------------+  +-----------------+
     |Network Controller|  |Network Management|  | User Application|..
     +------------------+  +------------------+  +-----------------+
                 |               | |                     |
                 \---------------| |--------------------/
                                 | | I2RS Interface
     +----------------------+    | |     +------------------+
     |Configuration Function|----| |-----|Security Function |
     +----------------------+    | |     +------------------+
                                 | |
                                 | |                  Routing Function
     +---------------------------| |--------------------------------+
     |                           | |                                |
     |   +------------+          | |             +-----------+      |
     |   |OSPF process|          | |             |BGP process| ...  |
     |   +------------+          | |             +-----------+      |
     |          |                | |                   |            |
     |          |     +------------------------+       |            |
     |          +-----|Routing Information Base|-------+            |
     |                +------------------------+                    |
     |                            |                                 |
     |                   +--------------------+                     |
     |                   | IP Forwarding Table|                     |
     |                   +--------------------+                     |
     |                                                              |
     +--------------------------------------------------------------+




Liu & Deng               Expires August 5, 2013                 [Page 3]


Internet-Draft              i2rs architecture                   Feb 2013


                                 Figure 1


2.  Conventions used in this document

   RIB: Routing Information Base

   I2RS: Interface to Routing System


3.  Architecture of I2RS

   This section discusses the function of the building block of the I2RS
   architecture.

   1.  I2RS user application

   The I2RS user application communicate with the routing information
   base using the I2RS interface.  The user application can read the
   routing information from the routing information base, it can also
   inject polices, routing information etc into the routing information
   base.  The I2RS interface could be RESTful API or websocket etc.
   There should be an authentication mechanism in the I2RS architecture
   that only allow the authorized application communicate with the
   routing system.

   2.  Configuration function

   The I2RS interface could be configured by the configuration function.
   The I2RS user application could customize the I2RS interface function
   and set the I2RS interface parameters by the configuration function.

   3.  Security function

   Security function is an important building block of the I2RS
   architecture.  It will ensure only authorized application can use the
   I2RS interface and communicate with the routing system.  There could
   be different level of authorization.  For example, the security
   function can allow some application only read from the routing system
   while other application can both read and inject polices into the
   routing system.

   4.  Routing function

   The routing function is composed of routing informatio base, IP
   forwarding table and the routing processes.  The I2RS application
   could communicate with the routing information base using the I2RS
   interface.  It can read or inject routing information into the



Liu & Deng               Expires August 5, 2013                 [Page 4]


Internet-Draft              i2rs architecture                   Feb 2013


   routing information base.  The routing processes can also inject
   routing information into the routing information base.


4.  Security Considerations

   Security function is very important for the I2RS architecture.  It
   should provide authenticatin mechanism and data protection mechanism
   to protect critical routing information.


5.  IANA Considerations

   No IANA action is required.


6.  Acknowledgments


7.  References

7.1.  Normative References

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

7.2.  Informative References

   [RFC2328]  Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.

   [RFC4271]  Rekhter, Y., Li, T., and S. Hares, "A Border Gateway
              Protocol 4 (BGP-4)", RFC 4271, January 2006.


Authors' Addresses

   Dapeng Liu
   China Mobile
   Unit2, 28 Xuanwumenxi Ave,Xuanwu District
   Beijing 100053
   China

   Email: liudapeng@chinamobile.com








Liu & Deng               Expires August 5, 2013                 [Page 5]


Internet-Draft              i2rs architecture                   Feb 2013


   Hui Deng
   China Mobile
   Unit2, 28 Xuanwumenxi Ave,Xuanwu District
   Beijing 100053
   China

   Email: denghui@chinamobile.com












































Liu & Deng               Expires August 5, 2013                 [Page 6]


Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/