An Architecture for the Interface to the Routing System
RFC 7921

Document Type RFC - Informational (June 2016; No errata)
Last updated 2016-06-30
Replaces draft-atlas-i2rs-architecture
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Mach Chen
Shepherd write-up Show (last changed 2016-02-29)
IESG IESG state RFC 7921 (Informational)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
Internet Engineering Task Force (IETF)                          A. Atlas
Request for Comments: 7921                              Juniper Networks
Category: Informational                                       J. Halpern
ISSN: 2070-1721                                                 Ericsson
                                                                S. Hares
                                                                  Huawei
                                                                 D. Ward
                                                           Cisco Systems
                                                               T. Nadeau
                                                                 Brocade
                                                               June 2016

        An Architecture for the Interface to the Routing System

Abstract

   This document describes the IETF architecture for a standard,
   programmatic interface for state transfer in and out of the Internet
   routing system.  It describes the high-level architecture, the
   building blocks of this high-level architecture, and their
   interfaces, with particular focus on those to be standardized as part
   of the Interface to the Routing System (I2RS).

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7921.

Atlas, et al.                 Informational                     [Page 1]
RFC 7921                    I2RS Architecture                  June 2016

Copyright Notice

   Copyright (c) 2016 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.

Atlas, et al.                 Informational                     [Page 2]
RFC 7921                    I2RS Architecture                  June 2016

Table of Contents

   1. Introduction ....................................................4
      1.1. Drivers for the I2RS Architecture ..........................5
      1.2. Architectural Overview .....................................6
   2. Terminology ....................................................11
   3. Key Architectural Properties ...................................13
      3.1. Simplicity ................................................13
      3.2. Extensibility .............................................14
      3.3. Model-Driven Programmatic Interfaces ......................14
   4. Security Considerations ........................................15
      4.1. Identity and Authentication ...............................17
      4.2. Authorization .............................................18
      4.3. Client Redundancy .........................................19
      4.4. I2RS in Personal Devices ..................................19
   5. Network Applications and I2RS Client ...........................19
      5.1. Example Network Application: Topology Manager .............20
   6. I2RS Agent Role and Functionality ..............................20
      6.1. Relationship to Its Routing Element .......................20
      6.2. I2RS State Storage ........................................21
           6.2.1. I2RS Agent Failure .................................21
           6.2.2. Starting and Ending ................................22
           6.2.3. Reversion ..........................................23
      6.3. Interactions with Local Configuration .....................23
           6.3.1. Examples of Local Configuration vs. I2RS
                  Ephemeral Configuration ............................24
      6.4. Routing Components and Associated I2RS Services ...........26
           6.4.1. Routing and Label Information Bases ................28
           6.4.2. IGPs, BGP, and Multicast Protocols .................28
           6.4.3. MPLS ...............................................29
Show full document text