Actually, several folks talked at lunch, and defining the data model first might be precisely the wrong thing to do... Let me just throw it out for discussion--
Is it better to define the information needed to forward a packet as a data model, so we simply leave the problem of defining a "rib," etc., as something we can ignore? In other words, if we start from the packet end, do we simplify our problem in a major way? :-) Russ <>< [email protected] On Mar 14, 2013, at 11:24 AM, Robert Raszuk <[email protected]> wrote: >> Vlan, I think, might fit into a table ID... ?? > > Well it depends who binds this VLAN to a table ID on the network element. > >> MPLS tag I would include under next hop in general (take out IP)... ? > > Well for transport MPLS analogy yes, but for application MPLS label > (example VPN label) this is not really a next hop property. > > 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
