Paul Gear

I won't be posting here any more; see you over at

[Paul Gear @paulgear1]

More on #AWS microsecond-accurate time https://t.co/LL0Ds7BNhc - my adventures in #Linux timekeeping with #NTP & #KVM

[Paul Gear @paulgear1]

Latest in my one-man crusade to debunk the "never run an #NTP server in a #VM" myth. https://t.co/MXQ6lnz4xv #linux #kvm

[Paul Gear @paulgear1]

How I run my #NTP pool infrastructure: https://t.co/M4m9T6HiRs #linux #ntppool

[Paul Gear @paulgear1]

And a whole series on time sync in public clouds https://t.co/MqQjVfV43M

[Paul Gear @paulgear1]

Getting a bit sick of people questioning the possibility of accurate time sync in VMs, so I've been doing a bit of data collection and writing it up. https://t.co/MqQjVfV43M https://t.co/9ytptkoeSt

[Paul Gear @paulgear1]

@mipsytipsy Where can I get a sticker for my laptop with this on it? https://t.co/erLcqDS7sr (Happy to use a DIY place, as long as the image is free to use...)

[John Dickson @johnpauldickson]

For what they're worth, in 2 mins here are my simple thoughts about this week's Australian referendum on the Indigenous Voice to Parliament. Thanks for listening.

[Paul Gear @paulgear1]

Please help Christopher Hawker respond to a frivolous defamation lawsuit as a result of the successful campaign to amend the @apnic by-laws to prevent takeover by corporate influences. https://t.co/oWfq1CO5kI

[Paul Gear @paulgear1]

@forwardingplane @ipv6buzz @ehorley @ipv6tom @SCOTTHOGG The scenario I was pondering is: RFC6724 requires IPv4 to be represented as a mapped address; is your draft proposing that these are put below all IPv6? Won't the only way to get to them be via link-local? Or does the absence of a route to ::ffff:0:0/96 fix this?

[Paul Gear @paulgear1]

@ipv6buzz @ehorley @ipv6tom @SCOTTHOGG @forwardingplane A few follow-ups on https://t.co/bCh8tlLheE - would like to hear your thoughts... 1. One gap I was surprised you didn't address: if IPv4 is being preferenced below ALL IPv6, what does that mean for link local addresses? ...

[Paul Gear @paulgear1]

4. And one minor quibble: It would be great if the episode notes linked directly to @forwardingplane's draft.

[Paul Gear @paulgear1]

@ipv6buzz @ehorley @ipv6tom @SCOTTHOGG @forwardingplane Where are the dissenting voices saying: Actually, we need to find a way through the small site multihoming issue without needing renumbering?

[Paul Gear @paulgear1]

@lystena Isn't the likelihood of both 100%?

[Paul Gear @paulgear1]

@forwardingplane @noIPv6 @ipv6buzz @ipv6tom @ehorley @SCOTTHOGG I was more thinking of the small site multihoming draft. Not sure if https://t.co/NdkH6bag6R is the definitive location now?

[Paul Gear @paulgear1]

@ipv6buzz @ipv6tom @ehorley @SCOTTHOGG @forwardingplane I feel like I could have offered an equally-weighty counterpoint for nearly every pro and con you mentioned in this episode.

[Paul Gear @paulgear1]

@ipv6buzz @ipv6tom @ehorley @scotthogg I love your advocacy for IPv6 adoption, but this episode really felt like it was putting up straw men and not tackling both the advantages of NAT and the issues with IPv6 only that @forwardingplane & friends have been working on...