Ladislav, I did just use "FIB" as an example term. I wasn't refering to any RIB-related text. BTW: RFC 1812 provides NOT a definition for "RIB". DEFINITIONS are contained in APPENDIX B. This does not preclude that the RFC contains DESCRIPTIONS of the term, however, you are looking for terminology definitions.
Appropriate references for such terms: Firstly IETF RFCs. Any vendor-specific information may not be referred in my understanding. To Ivan: Cisco was the primary author of RFC 1812, hence I would suspect not any major divergences ...:-) -Albrecht -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ivan Pepelnjak Sent: Mittwoch, 27. Februar 2013 11:32 To: [email protected] Subject: Re: [i2rs] Router Models Actually both RIB and FIB (or "routing table" and "CEF table") on a Cisco router would fit the description from RFC 1812 quoted below. Ivan On 27.02.2013 11:21 , Ladislav Lhotka wrote: > On Feb 27, 2013, at 10:50 AM, "Schwarz, Albrecht (Albrecht)" > <[email protected]> wrote: > >> Any (new) developed terminology by I2RS docs should refer to existing IETF >> RFCs. >> >> E.g., >> FIB >> => initial term definition = RFC 1812, Appendix B, Glossary: >> Forwarding Information Base (FIB) >> The table containing the information necessary to forward IP >> Datagrams, in this document, is called the Forwarding >> Information Base. At minimum, this contains the interface >> identifier and next hop information for each reachable >> destination network prefix. > Right, but note that this is called RIB in Cisco docs: > > http://blog.ioshints.info/2010/09/ribs-and-fibs.html > > This definition also doesn't really answer the question whether FIB contains > only active routes - I assume it does. > > The BGP spec (RFC 4271) seems to imply the following definitions: > > - RIB: data structures internal to each routing protocol instance; > > - routing table: bag of routes obtained from different sources, > possibly with multiple routes for the same prefix; > > - forwarding table = FIB: a cleaned-up table containing only selected active > routes. > > Lada > >> >> BTW: RFC 1812 is still the "default (IPv4) router model". >> >> => initial FIB data model = RFC 2096 (-> RFC 4292) >> >> There are two options for I2RS: >> - already existing definition, Y/N? >> - existing definition sufficient, Y/N? >> IF {Y,Y} THEN just refer >> IF {N,-} THEN develop term definition IF {Y,N} THEN develop derived >> definition (and refer to base term) >> >> Albrecht >> >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On Behalf >> Of Ladislav Lhotka >> Sent: Mittwoch, 27. Februar 2013 10:32 >> To: Russ White; Rob (William) Rice >> Cc: [email protected] >> Subject: Re: [i2rs] Router Models >> >> Russ White <[email protected]> writes: >> >>>> 2. Does the RIB in your diagram include all routes from all sources >>>> or just best routes (those to be used for forwarding)? >>> All the routes from all sources. The RIB would select which routes >>> to present to the FIB based on it's internal policy (such as admin >>> distance). Perhaps the "policy cloud" should really be below the >>> RIB, between the RIB and the FIB. >>> >> It might be useful to have an upfront agreement on the definitions of terms >> like RIB, FIB, routing table and forwarding table. Previously, we had an >> interesting discussion about them in the NETMOD mailing list, see this >> thread: >> >> http://www.ietf.org/mail-archive/web/netmod/current/msg06920.html >> >> It turned ot that each of the two major router vendors uses these terms in a >> somewhat different sense, and neither of them is identical with how they are >> used in IETF documents. >> >> Lada >> >> -- >> Ladislav Lhotka, CZ.NIC Labs >> PGP Key ID: E74E8C0C >> _______________________________________________ >> i2rs mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/i2rs > -- > Ladislav Lhotka, CZ.NIC Labs > PGP Key ID: E74E8C0C > > > > > _______________________________________________ > i2rs mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
