Data model for RIB I2RS protocol
draft-wang-i2rs-rib-data-model-00

The information below is for an old version of the document
Document Type Active Internet-Draft (i2rs WG)
Last updated 2015-01-21 (latest revision 2014-12-07)
Replaced by draft-ietf-i2rs-rib-data-model
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to i2rs@ietf.org, i2rs-chairs@ietf.org, draft-wang-i2rs-rib-data-model.all@ietf.org
Network Working Group                                       Lixing. Wang
Internet-Draft                                                    Huawei
Intended status: Standards Track                              Amit. Dass
Expires: June 11, 2015                                          Ericsson
                                                       December 08, 2014

                    Data model for RIB I2RS protocol
                   draft-wang-i2rs-rib-data-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
   collectively push data into RIB and the RIB manager installs state
   information into the hardware; for packet forwarding.  This draft
   specifies a data model for the RIB in order to define and enable a
   standardized data model.  Such a data model can be used to define an
   interface to the RIB by using an entity that may even be external to
   the network device.  This interface can be used to support new use-
   cases being defined by the IETF I2RS WG.

   This document introduces a yang data for I2RS RIB that aligns with
   the I2RS RIB use cases and I2RS RIB infomation model.

Requirements Language

   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 [RFC2119].

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 June 11, 2015.

Wang & Dass               Expires June 11, 2015                 [Page 1]
Internet-Draft                 RIB I2RS DM                 December 2014

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definitions and Acronyms  . . . . . . . . . . . . . . . . . .   3
   3.  Yang Top-level description  . . . . . . . . . . . . . . . . .   3
     3.1.  Capabilities  . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  routing-instance-list . . . . . . . . . . . . . . . . . .   4
     3.3.  Route . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Notifications . . . . . . . . . . . . . . . . . . . . . .   6
     3.5.  NextHops  . . . . . . . . . . . . . . . . . . . . . . . .   9
   4.  Full Yang Top-level description . . . . . . . . . . . . . . .  11
   5.  RIB Yang description  . . . . . . . . . . . . . . . . . . . .  33
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  52
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  52
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  53
     8.1.  Informative References  . . . . . . . . . . . . . . . . .  53
     8.2.  Normative References  . . . . . . . . . . . . . . . . . .  53
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  53

1.  Introduction

   The Interface to the Routing System (I2RS) provides read and write
   access to the information and state within the routing process that
   exists inside the routing elements via protocol message exchange
   between an I2RS Client and an I2RS Agent associated with the routing
   system.  The [I-D.ietf-i2rs-architecture] describes the basic
   interaction procedures of this exchange activity.  One of the
   important functions of this messages exchange is to get the I2RS
   client interact with one or more I2RS agents in order to collect
   information from the network routing systems.

   Protocols and configuration collectively push data into RIB and the
   RIB manager installs state information into the hardware; for packet
Show full document text