i-abuse-wg] 2017-02 Review Phase (Regular abuse-c Validation)
Dear colleagues,
Policy proposal 2017-02, "Regular abuse-c Validation" is now in the Review
Phase.
The goal of this proposal is to give the RIPE NCC a mandate to regularly
validate "abuse-c:" information a
On Thu, Jan 18, 2018 at 12:22:28PM +0100, Marco Schmidt wrote:
The RIPE NCC has prepared an impact analysis on this latest proposal version to
support the community???s discussion. You can find the full proposal and impact
analysis at:
"You may say I'm a dreamerBut I'm not the only oneI hope some day you'll join usAnd the world will be as one" - John Lennon
Original Message
Subject: Re: [anti-abuse-wg] 2017-02 Review Phase (Regular abuse-c
Validation)
From: Chris Hills <c...@chaz6.com>
Date:
I support this proposal. I would also like an escalation mechanism whereby
abuse issues can be escalated to RIPE if a satisfactory response is not
received from the designated contact address (for instance, if the email
bounces back and is not delivered).
Sent via RIPE Forum --
Marco,
Thanks for this. It very clearly sets out what the NCC plan to do.
There has been an amount of discussion already (which is great!), but I
would especially encourage those who have previously spoken against this
proposal to comment on this latest information.
Thanks,
Brian
Co-Chair,
I support the proposal.
Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
We support the proposal.
--
Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
https://www.blacknight.com/
http://blacknight.blog/
Intl. +353 (0) 59 9183072
Direct Dial: +353 (0)59 9183090
Personal blog: https://michele.blog/
Some thoughts: https://ceo.hosting/
Dear colleagues,
Policy proposal 2017-02, "Regular abuse-c Validation" is now in the Review
Phase.
The goal of this proposal is to give the RIPE NCC a mandate to regularly
validate "abuse-c:" information and to follow up in cases where the attribute
is deemed to be incorrect.
This proposal
