<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.nitinb-i2rs-rib-info-model" target="https://datatracker.ietf.org/doc/html/draft-nitinb-i2rs-rib-info-model-02">
   <front>
      <title>Routing Information Base Info Model</title>
      <author initials="N." surname="Bahadur" fullname="Nitin Bahadur">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="R." surname="Folkes" fullname="Ron Folkes">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="S." surname="Kini" fullname="Sriganesh Kini">
         <organization>Ericsson</organization>
      </author>
      <author initials="J." surname="Medved" fullname="Jan Medved">
         <organization>Cisco</organization>
      </author>
      <date month="August" day="21" year="2013" />
      <abstract>
	 <t>   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 enable defining a standardized data model.  Such
   a data model can be used to define an interface to the RIB from 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-nitinb-i2rs-rib-info-model-02" />
   
</reference>
