On 3/14/13 10:44 AM, "Russ White" <[email protected]> wrote:
> >No, but I did try to address at least a partial list in one of the use >cases draft. I think this would really entail building a data model for >"the entity officially known as the rib." Is the current YANG model a >good solution to the question? It seems like we should answer that >question before writing another one. There is a current YANG draft trying to cover the most basic of a routing table http://datatracker.ietf.org/doc/draft-ietf-netmod-routing-cfg/?include_text =1 > >I suspect we'll need either need to extend an existing ones to get where >we want? > > >I think the right place to start might be to explicitly include the >objects that need to be manipulated in each use case. > >Maybe we need a "standard set" of things that need to be included in each >use case? > > >Thoughts? "Cast a wide net for every possible use case" and "Narrow requirements to bite sized chunks" The same principal can be used to define the RIB as well.:-) Start with a vanilla RIB definition consisting of basic common objects, but allow it to be extended for fancy applications. Yi > > >:-) > >Russ > > ><>< >[email protected] >[email protected] > >On Mar 14, 2013, at 10:34 AM, Robert Raszuk <[email protected]> wrote: > >> Hi Scott, >> >>> Why do we need to go beyond defining an interface to the RIB to make >>>your >>> use case work? >> >> I am talking precise about that definition of RIB interface. Not how >> the RIB works in given vendor of network element. That is >> implementation detail. >> >> Basically a list of values one can write or read to/from RIB. Have you >> seen any document with such list yet ? >> >> Cheers, >> R. >> _______________________________________________ >> 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
