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/address-policy-wg@ripe.net/
[address-policy-wg] 2017-01 New Policy Proposal (Publish statistics on Intra-RIR Legacy updates)
- Previous message (by thread): [address-policy-wg] 2017-01 New Policy Proposal (Publish statistics on Intra-RIR Legacy updates)
- Next message (by thread): [address-policy-wg] APWG meeting agenda 0.2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Schmidt
mschmidt at ripe.net
Wed Apr 26 15:20:29 CEST 2017
Dear Hank, On 2017-04-26 07:17:35 CET, Hank Nussbacher wrote: > > why is this true only for legacy space? > Further to this point: can RIPE NCC provide statistics for the past 3 > years of the number of IP resource hijacks that have taken place? > Thank you for your question. We are happy to provide some information here. Firstly, it’s important to note that the following numbers mainly refer to resources that are under a contractual relationship with the RIPE NCC. The RIPE Database contains several thousand parent legacy ranges that are not covered by a contractual relationship. Whoever has access to the maintainer can update all details of the resource object. We would only notice hijacks of these resources if the resource holder reports the hijack or the hijacker asks us to update our internal records. Since 2014, the RIPE NCC has concluded around 300 hijack cases for all types of resources, another 16 cases are still being investigated. We reported on resource hijacking in our 2016 Annual Report. As we mentioned there, legacy resources remain susceptible to hijacks using fraudulently provided statements and several cases are under active investigation. You can find this on page 18 here (PDF): https://www.ripe.net/participate/meetings/gm/meetings/may-2017/supporting-documents/ripe-ncc-annual-report-2016.pdf I hope this clarifies your question. Kind regards, Marco Schmidt Policy Development Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
- Previous message (by thread): [address-policy-wg] 2017-01 New Policy Proposal (Publish statistics on Intra-RIR Legacy updates)
- Next message (by thread): [address-policy-wg] APWG meeting agenda 0.2
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]