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 ]
Sascha Luck [ml]
aawg at c4inet.net
Fri Mar 22 11:50:35 CET 2019
On Thu, Mar 21, 2019 at 10:46:08PM -0700, Jacob Slater wrote: > >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. In my world, these authorisations are largely informal (phone calls, emails, sometimes personal meetings). The people involved know and trust each other, there is no need for bureaucratic exercises. >Because they have had no valid reason to do so yet. Making it a policy >violation doesn't seem like the right way to encourage them to do so. >It is not the job of the NCC to tell users how to run their network. As >annoying as it is at times, this includes how users choose to authenticate >their announcements. Agreed, and I refuse to accept the NCC's authority to do so. rgds, SL
- 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 ]