11 Apr
2023
11 Apr
'23
8:54 p.m.
On Apr 11, 2023, at 2:39 PM, Thomas DeBellis
<tommytimesharing(a)gmail.com> wrote:
In reverse order, I think the numeric-only concern is addressed easily enough, assuming
you think your own local executor's node data base is up to date.
This is more or less the case on TOMMYT:: and VENTI2::, which download the latest and
greatest from MIM:: on a weekly basis and then use my SETNODE rewrite to compute the set
difference between the current and new definitions in order to change as little as
possible in the monitor's volatile storage.
In short, if the remote node doesn't know, try recovering by asking the local
executor. That seems straightforward.
In your case, the "local executor" would be the NETPHT utility, because
that's the one sending NICE messages to the remote node, right? If the remote node,
the one you're asking for the equivalent of "show node <foo> status",
doesn't know a name for some node number it mentions in the response, it sends just
the address. When processing that response you could indeed supply the name, so if you
want to extend NETPTH to do so that's an option.
The question in my mind is what is
'reasonable' for netpth do to recover if it doesn't get told the next node?
By reasonable, I mean is the process algorithmic (I.E., do this that or the other thing)
or heuristic (I.E., here are some good guesses) ?
Do "show active nodes" and pick up the adjacent node info from the circuit
matching the next-hop circuit in the show node data.
paul