Re: Extension for an abuse contact in Domain objects?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 30-10-12 07:08, Luis Muñoz schreef:
> 
> On Oct 29, 2012, at 12:58 PM, Christopher Browne wrote:
> 
>>> From a technical ("EPP protocol") perspective, a new contact 
>>> type
>> wouldn't be any different from the existing types.  To make it 
>> useful (e.g. - guaranteeing that the anti-abuse contact is 
>> somehow better than the present technical contact) would require 
>> having a further set of policy to enforce usefulness.
> 
> Yes, ideally there would be a policy layer further clarifying
> this. Is there merit in building this policy along with the
> extension?

And even with a policy, experience shows it does not lead to better
population.
How many of you populate the MNAME field in your zone correctly ?
What's the difference ?

We've had a policy and pre-delegation checks for many years to
populate fields correctly, only to find out that registrars only
populated the fields so they could pass our tests, but still emails to
MNAME's were not replied to (they were sent to dev/null).

Same is true even for registrants.
Many registrars register domains on their legal entity in stead of
their customers because maintaining correct customer data at the
registry is too much hassle or their customers don't want their data
out there. Responding to abuse is a cost, so it is discouraged. They
play by the rules to pass the policy, but not more than that.

- -- 
Antoin Verschuren

Technical Policy Advisor SIDN
Meander 501, PO Box 5022, 6802 EA Arnhem, The Netherlands

P: +31 26 3525500  M: +31 6 23368970
Mailto: [email protected]
XMPP: [email protected]
HTTP://www.sidn.nl/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJQj5XCAAoJEDqHrM883AgnSvsIAKll/mPR5Lu+VenkEQadP6QL
a/RmHx30aU9HzWzigfQDBMBiJqwlX0YaMG+EQowWd79vmHUD7/46k9MHiaiOQZgB
SmvRlhIJxN8MQSmeCdaYkP5al2aKehqBcZO2OhFXfvc3r3kF6Vsi/EILQTmyFxt5
Bx9locMSolvpf59zhZRLXkVQSdUgxk+ByiaPBpmgsiNxEwTEYtPQSeMyRSKCLp2Y
JcSWm+CaS9SuxKzOd1j63yeUa3SGBaCQIbe4BpRlGs7a+udJRBnTo68ZXmmiXr3H
dcm3+P+BPArqBaw/M4CvIN6ozcvpvrSxDhXvvxuq6ghAysRQOO2rP3V/KvS4HJI=
=yTlJ
-----END PGP SIGNATURE-----
_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg