Routing Information Base Info Model
draft-nitinb-i2rs-rib-info-model-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-06-25
Replaced by draft-ietf-i2rs-rib-info-model
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                    N. Bahadur, Ed.
Internet-Draft                                            R. Folkes, Ed.
Intended status: Informational                    Juniper Networks, Inc.
Expires: December 27, 2013                                       S. Kini
                                                                Ericsson
                                                           June 25, 2013

                  Routing Information Base Info Model
                  draft-nitinb-i2rs-rib-info-model-00

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 install state into the
   hardware; for packet forwarding.  This draft specifies an information
   model for the RIB, to build a standardized RIB model, using which an
   external entity (external to the network device) can read and write
   information from/to the RIB.

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 December 27, 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

Bahadur, et al.         Expires December 27, 2013               [Page 1]
Internet-Draft     Routing Information Base Info Model         June 2013

   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 . . . . . . . . . . . . . . . . . . . . . .  5
     2.2.  Routing tables . . . . . . . . . . . . . . . . . . . . . .  6
     2.3.  Route  . . . . . . . . . . . . . . . . . . . . . . . . . .  7
     2.4.  Nexthop  . . . . . . . . . . . . . . . . . . . . . . . . .  8
       2.4.1.  Nexthop types  . . . . . . . . . . . . . . . . . . . .  9
       2.4.2.  Nexthop list attributes  . . . . . . . . . . . . . . . 10
       2.4.3.  Nexthop content  . . . . . . . . . . . . . . . . . . . 10
       2.4.4.  Nexthop attributes . . . . . . . . . . . . . . . . . . 11
       2.4.5.  Special nexthops . . . . . . . . . . . . . . . . . . . 11
   3.  Reading from the RIB . . . . . . . . . . . . . . . . . . . . . 11
   4.  Writing to the RIB . . . . . . . . . . . . . . . . . . . . . . 12
   5.  Events and Notifications . . . . . . . . . . . . . . . . . . . 12
   6.  RIB grammar  . . . . . . . . . . . . . . . . . . . . . . . . . 13
   7.  Using the RIB grammar  . . . . . . . . . . . . . . . . . . . . 15
     7.1.  Using route preference and metric  . . . . . . . . . . . . 15
     7.2.  Using different nexthops types . . . . . . . . . . . . . . 16
       7.2.1.  Tunnel nexthops  . . . . . . . . . . . . . . . . . . . 16
       7.2.2.  Replication lists  . . . . . . . . . . . . . . . . . . 16
       7.2.3.  Weighted lists . . . . . . . . . . . . . . . . . . . . 16
       7.2.4.  Protection lists . . . . . . . . . . . . . . . . . . . 17
       7.2.5.  Nexthop chains . . . . . . . . . . . . . . . . . . . . 17
       7.2.6.  Lists of lists . . . . . . . . . . . . . . . . . . . . 18
     7.3.  Solving optimized exit control . . . . . . . . . . . . . . 18
   8.  RIB operations at scale  . . . . . . . . . . . . . . . . . . . 19
     8.1.  RIB reads  . . . . . . . . . . . . . . . . . . . . . . . . 19
     8.2.  RIB writes . . . . . . . . . . . . . . . . . . . . . . . . 19
     8.3.  RIB events and notifications . . . . . . . . . . . . . . . 19
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 19
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 19
Show full document text