On 05/09/2012 22:11, Stuart Henderson wrote:
This is one reason why we should stick with ASDOT format ;-)
2737504257 = 41771.1, 2737504258 = 41771.2
My only gripe is the 'dot' in 'asdot'.
For reasons too long to go into, some time last year I was fooling
around with data featuring both AS numbers in ASDOT form, and RTT values
as seconds.milliseconds.
When you're peering into the abyss of a huge dataset, it's not useful to
have a small percentage of AS numbers printed in ASDOT format alongside
a much larger set of RTT values.
To resolve the headache, I went back and converted all those ASDOTs to
ASPLAINs at an earlier stage in my workflow. Ambiguity is not helpful!
S.
