Hi,
Both the RIB info and data model mentions nexthop-id, but neither specifies who
manages/assigns the ID. Can the specs point that out?
It seems that it could be both ways - the IDs could be allocated by routers
(servers) or could be allocated by clients. Different ID spaces would be used
depending on who allocates the IDs.
Related to the above, a specific question on the data model:
grouping nexthop {
leaf nexthop-id {
mandatory true;
type uint32;
}
choice nexthop-type {
...
case nexthop-protection {
list nexthop-protection-list {
key "nexthop-protection-id";
leaf nexthop-protection-id {
mandatory true;
type uint32;
}
leaf nexthop-preference {
...
}
leaf nexthop {
mandatory true;
type nexthop-ref;
}
}
}
Here a nexthop-protection is a list. Being a list it requires a key and we
defined this uint32 nexthop-protection-id, which I assume the controller needs
to assign and both the controller and the router needs to remember. The list
entry has a member "nexthop" which is a nexthop-ref, which is a nexthop-id:
typedef nexthop-ref {
type leafref {
path "/i2rs-rib:routing-instance/i2rs-rib:rib-list" +
"/i2rs-rib:route-list/i2rs-rib:nexthop/i2rs-rib:nexthop-id";
}
}
So - why can't we use the nexthop-id itself as the key?
Thanks.
Jeffrey
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
