Cisco IOS router_object/id element should be nillable

[wmunyan]

The <router_object> defines the <id> element, which is noted as an “int”, however, in some of my configurations for the various routers and protocols, I am seeing router sections configured as:
router eigrp foo
and
router rip

alongside others which seem to match the “int” definition of the field:
router ospf 1
and
router bgp 1

My question then becomes, what do we collect in the first cases? For the router eigrp foo case, I cannot collect foo as the <id> for obvious reasons. For the router rip case, would the <id> be marked as “does not exist”? If there’s the potential to not have an <id> element collected in the system characteristics, how can that be defined in the <router_object>, since a value for <id> is required in the object. Is the xsi:nil allowed in this case? How would I create the <router_object> to collect “router rip”?

Does the schema need to change to allow either a “string” or and “int” value for the <id> field, and should the xsi:nil=true be allowed as well?

Response to the above questions, from Panos were:

I think when updating the Cisco schemata we indeed were focusing on router process ids used in the
 config (like BGP, EIGRP etc that you showed). We didn’t pay attention to instances like rip or
 pseudonames for eigrp. I don’t think these configs are used often, but someone that wants to be able to
 collect such system characteristics would indeed need a schema update.
 
Rgs,
Panos

Cheers,
-Bill M (CIS)

[zport]

Issue moved to OVAL-Community/OVAL #28 via ZenHub