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] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Previous message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Next message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard Clayton
richard at highwayman.com
Tue Mar 19 21:18:47 CET 2019
In message <E1h6E3W-00051F-BF at www-apps-1.ripe.net>, Marco Schmidt <mschmidt at ripe.net> writes >The goal of this proposal is to define that BGP hijacking is not accepted as >normal practice within the RIPE NCC service region. > >You can find the full proposal at: >https://www.ripe.net/participate/policies/proposals/2019-03 <quote> The announcement of unallocated address space to third parties is also considered a policy violation and is evaluated according to the same parameters. </quote> This is going to be somewhat challenging ... since there are a substantial number of well-known (and generally non-abusive entities) who are announcing unallocated address space, and in many cases they have been doing so for years on end. I understand there is a mixture of long term disputes about allocations; failures to keep contact addresses up-to-date (so that allocations are withdrawn) and doubtless also intentional usage of resources that have not been allocated. Geoff Huston publishes a list on a daily basis: http://www.cidr-report.org/as2.0/#Bogons For the avoidance of doubt, I think it is most undesirable that any prefix appears on the list -- but I am pragmatic enough to accept that there are significant difficulties in dealing with the complexities which are behind those announcements. BTW: Geoff Huston's data gathering exercise also identifies the usage of AS numbers that are not currently allocated. Again, much of this usage is very long standing and failure to "grandfather it in" in some manner is likely to cause a substantial workload and the deeming of many legitimate companies to be in breach of RIPE norms -- which is going to tend to make the impact of the policy rather less than might be hoped. That all said -- why does the proposed policy not address the misuse of AS numbers as well as the misuse of prefixes ? -- richard Richard Clayton Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 185 bytes Desc: not available URL: </ripe/mail/archives/anti-abuse-wg/attachments/20190319/86963ba0/attachment.sig>
- Previous message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Next message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]