spec: don't collide with VM's metadata svc

While the spec only indicates that the concrete IP is "by convention", I think it's best to use 169.254.169.255 to avoid colliding with EC2's (and such) metadata svc. This also matches the implementation since it currently does not proxy to the cloud-providers metadata svc.