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. 

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
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs

Reply via email to