Section 2.2 b. Interface_list and router-id: For a functioning routing-instance, can't think of a routing-instance without either of those defined. So, either the optionality aspect needs to be changed to "required" or specify how a routing-instance would work with either missing.
NB> A routing instance can contain a RIB that has next-hops to other RIBs. That is the reason interface-list and router-id are optional. I can add text that clarification in. NB> Text that was added: "A routing instance may be created purely for the purposes of packet processing and may not have any interfaces associated with it. For example, an incoming packet in routing instance A might have a nexthop of routing instance B and after packet processing in B, the nexthop might be routing instance C. Thus, routing instance B is not associated with any interface. And given that this routing instance does not do any control plane interaction with other network devices, a ROUTER_ID is also not needed."
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
