Routing Information Base Info Model
draft-ietf-i2rs-rib-info-model-17

Document Type Active Internet-Draft (i2rs WG)
Last updated 2018-07-17 (latest revision 2018-05-07)
Replaces draft-nitinb-i2rs-rib-info-model
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Aug 2016 - Request publication ... )
Document shepherd Susan Hares
Shepherd write-up Show (last changed 2018-02-09)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Martin Vigoureux
Send notices to Susan Hares <shares@ndzh.com>
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IC
RFC Editor RFC Editor state RFC-EDITOR
Network Working Group                                    N. Bahadur, Ed.
Internet-Draft                                                      Uber
Intended status: Informational                              S. Kini, Ed.
Expires: November 8, 2018
                                                               J. Medved
                                                                   Cisco
                                                             May 7, 2018

                  Routing Information Base Info Model
                   draft-ietf-i2rs-rib-info-model-17

Abstract

   Routing and routing functions in enterprise and carrier networks are
   typically performed by network devices (routers and switches) using a
   routing information base (RIB).  Protocols and configuration push
   data into the RIB and the RIB manager installs state into the
   hardware for packet forwarding.  This draft specifies an information
   model for the RIB to enable defining a standardized data model, and
   it was used by the IETF's I2RS WG to design the I2RS RIB data model.
   It is being published to record the higher-level informational model
   decisions for RIBs so that other developers of RIBs may benefit from
   the design concepts.

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 November 8, 2018.

Copyright Notice

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

Bahadur, et al.         Expires November 8, 2018                [Page 1]
Internet-Draft     Routing Information Base Info Model          May 2018

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Conventions used in this document  . . . . . . . . . . . .  5
   2.  RIB data . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     2.1.  RIB definition . . . . . . . . . . . . . . . . . . . . . .  6
     2.2.  Routing instance . . . . . . . . . . . . . . . . . . . . .  6
     2.3.  Route  . . . . . . . . . . . . . . . . . . . . . . . . . .  7
     2.4.  Nexthop  . . . . . . . . . . . . . . . . . . . . . . . . .  9
       2.4.1.  Base nexthop . . . . . . . . . . . . . . . . . . . . . 12
       2.4.2.  Derived nexthops . . . . . . . . . . . . . . . . . . . 13
       2.4.3.  Nexthop indirection  . . . . . . . . . . . . . . . . . 15
   3.  Reading from the RIB . . . . . . . . . . . . . . . . . . . . . 15
   4.  Writing to the RIB . . . . . . . . . . . . . . . . . . . . . . 15
   5.  Notifications  . . . . . . . . . . . . . . . . . . . . . . . . 16
   6.  RIB grammar  . . . . . . . . . . . . . . . . . . . . . . . . . 16
     6.1.  Nexthop grammar explained  . . . . . . . . . . . . . . . . 19
   7.  Using the RIB grammar  . . . . . . . . . . . . . . . . . . . . 19
     7.1.  Using route preference . . . . . . . . . . . . . . . . . . 19
     7.2.  Using different nexthops types . . . . . . . . . . . . . . 20
       7.2.1.  Tunnel nexthops  . . . . . . . . . . . . . . . . . . . 20
       7.2.2.  Replication lists  . . . . . . . . . . . . . . . . . . 20
       7.2.3.  Weighted lists . . . . . . . . . . . . . . . . . . . . 21
       7.2.4.  Protection . . . . . . . . . . . . . . . . . . . . . . 21
       7.2.5.  Nexthop chains . . . . . . . . . . . . . . . . . . . . 22
       7.2.6.  Lists of lists . . . . . . . . . . . . . . . . . . . . 23
     7.3.  Performing multicast . . . . . . . . . . . . . . . . . . . 24
   8.  RIB operations at scale  . . . . . . . . . . . . . . . . . . . 25
     8.1.  RIB reads  . . . . . . . . . . . . . . . . . . . . . . . . 25
     8.2.  RIB writes . . . . . . . . . . . . . . . . . . . . . . . . 25
     8.3.  RIB events and notifications . . . . . . . . . . . . . . . 25
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 25
Show full document text