-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I have yet to see a reason to agree to this proposal in current form, if
theare are no mechanisms to make sure that the data field
a) won't get populated by existing members
b) won't get updated and validated on a regular basis.
If the (b) is part of the policy, then I am all for it.
This actually brings up the question why is there no effort to validate
whois information, and as Mark Foster pointed out - those of us with
.com domains seems to get that on a regular interval.. I don't see a
reason it can't be the same for IP/ASN resources.
- -gaurab
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iEYEARECAAYFAktlcAoACgkQSo7fU26F3X02qACg3V63aN1j+9RfoR7ockrwS+00
tk4AoIqor7vq6Y3A5Ik5A5h6BEtRAyaq
=3uxp
-----END PGP SIGNATURE-----