This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[anti-abuse-wg] 2017-02 Policy Proposal (Regular abuse-c Validation)
- Previous message (by thread): [anti-abuse-wg] New on RIPE Labs: TLS Security and Data Centre Monitoring
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
herve.clement at orange.com
herve.clement at orange.com
Mon Oct 23 13:11:03 CEST 2017
Hello all, We (Grégory and I) are working on a new version of the "regular abuse-c validation" trying to take into account the various remarks held by the community during the discussion phase. The new version first includes a reference to ARC and specifies the limits of ARC reviews that are not able to cover the validation of Abuse-c contact points. It clarifies what a validation procedure should be, specifying what a validated answer is after RIPE NCC first attempt of contact and defining two validation periods. The first one covers the timeline the RIPE NCC is supposed to receive an answer after its first request and a second one is dedicated to the efforts made by the two parties to solve the issue in case of no validated answer during the first period. We recall that additional operational validation details (including RIPE NCC work load) will be part of the Impact Analysis. There is finally a clear reference to the ripe-676 "Closure of Members, Deregistration of Internet Resources..." underlining what are the ultimate cases a closure or deregistration could occur. The discussion with regard to these updates will be on the agenda for the Anti Abuse WG meeting on Wednesday. Regards Greg and Hervé _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/anti-abuse-wg/attachments/20171023/87952170/attachment.html>
- Previous message (by thread): [anti-abuse-wg] New on RIPE Labs: TLS Security and Data Centre Monitoring
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]