[ietf78-tech] 130.129.0.0/16 still lit
Geert Jan de Groot
geertj at psg.com
Thu Jul 1 23:03:46 PDT 2010
One week after the ICANN meeting, 130.129.0.0/16 is still announced
by Skynet/Belgacom. Given that they configured it (the prefix isn't
configured in show networks that drop the prefix when they are shut down
but configured inside the Belgacom network i.e. it stays up),
I fear that it may be "left around" and hamper IETF78.
Should I make a phone call asking Skynet to clean up?
Geert Jan
PS: I'm sorry to report that I don't drive a car and hence cannot help
to get icecream. I'm pretty sure that Sven know how to get it closer
though - perhaps in Maastricht itself.
More information about the ietf78-tech
mailing list