given "RFC4941 SHOULD (RFC capitalisation) be turned off by default" above, and the general lack of value of privacy extensions being enabled on a server or cloud geust, i really think we should:
a.) turn off privacy extensions on cloud-images for 14.10+
b.) look for a way to disable them by default for 'sever' for 14.10+
note, this has been difficult in the past to set "server specific config". as determining what is a server and what is not is not as straight forward as it may appear.
c.) document how the user can use user-data to customize the file on any ubuntu guest
d.) document how cloud provider can use vendor-data to customize this change this defualt on any ubuntu guest.
e.) change cloud-init metadata requests to IPV6_PREFER_SRC_PUBLIC
f.) consider this change in 14.04 for cloud-images.
given "RFC4941 SHOULD (RFC capitalisation) be turned off by default" above, and the general lack of value of privacy extensions being enabled on a server or cloud geust, i really think we should: SRC_PUBLIC
a.) turn off privacy extensions on cloud-images for 14.10+
b.) look for a way to disable them by default for 'sever' for 14.10+
note, this has been difficult in the past to set "server specific config". as determining what is a server and what is not is not as straight forward as it may appear.
c.) document how the user can use user-data to customize the file on any ubuntu guest
d.) document how cloud provider can use vendor-data to customize this change this defualt on any ubuntu guest.
e.) change cloud-init metadata requests to IPV6_PREFER_
f.) consider this change in 14.04 for cloud-images.