Concerning 192.x.x.x and routing

Just looks like a case of someone believing different DBs in whatever
order they choose. Not sure why it would 'suddenly' manifest, but MCI
is telling it loudly enough for sprint to believe it [appended] and for
it to work. I don't know other 192.x.x.x hit [none were listed], but (one of my customers) seems just peachy from BBN-land.

Fireless smoke or a transient?

Joe Provo
Network Operations Center
UltraNet Communications, Inc.