Hi,
On Tuesday, November 15, 2016 9:46 AM, Tim Bruijnzeels <tim@ripe.net> wrote: Hi Denis, WG,
Another good point. I think this depends on what the WG would consider the least surprising. I am inclined to say that "last-modified:" should be updated because it's an actual user initiated change in content.
If someone was to update all resources "properly" whenever a new Nic-hdl is introduce, it would come to exactly the same, so it would only keep that behavior that is already in place.
Are you saying here that if a user manually sets an "admin-c:" at some point in their network, this manually added value will then be inherited by all the more specific resource objects? The server will then replicate this value in all the more specific objects.
Yes I am suggesting that in a case like:
BIG INETNUM (inherits) - ORG (sets default) MEDIUM INETNUM (overrides) SMALL INETNUM (inherits)
The SMALL INETNUM inherits from the covering MEDIUM INETNUM, and any updates done there. If MEDIUM INETNUM would start to inherit, then the inherited attributes would also propagate to SMALL.
As long as "BIG Inetnum" never can inherit from 0/0. I guess the presence of an Org object reference in a DB object would always override the parent Inetnum's information, then there should be no risk for the resources to inherit from the parent place holders such as 0/0. Object that would easily benefit from the hierarchical inheritance would be: inetnum inet6num domain The link from a less to more specific is easy. Would aut-nums also be included? There the inheritance would only be the fact that an Org is registered in them. This could lead to have any objects where a nic-hdl can be referenced and contains an org reference be eligible for inheritance benefits as well. Cheers, David Hilario