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/anti-abuse-wg@ripe.net/
[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
Fri Mar 22 11:59:12 CET 2019
In message <CAFV686d+rHrTrevDm8sL9h+Nu6TPi8x+jHBv2pL+w- M9gyBgpg at mail.gmail.com>, Jacob Slater <jacob at rezero.org> writes >> First, I'm not sure I either understand or am even aware of these alleged >> "forms of permission for announcement {that} are not documented". So >> perhaps >> Mr. Slater could elaborate upon that, for my benefit, and perhaps also for >> that of others who may also be similarly in the dark about what he's >> talking >> about here. >> > >Route objects are not always required. While route objects are generally >preferred and should be used, letters of authorization are still in use >today. You certainly wouldn't see them in a public database (though you >might see objects which claim to be tied to them). Even if you do, they may >well be stale and no longer accurate. I doubt that all (perhaps any?) anti-DDoS arrangements (which often involve apparent hijacks of blocks of address space) are documented with route objects.... ... although perhaps more so in Europe where I believe that some providers build filtering systems from route objects ? -- 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/20190322/c901b0f7/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 ]