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 ]
Ronald F. Guilmette
rfg at tristatelogic.com
Sat Mar 23 00:02:52 CET 2019
In message <CAFV686d+rHrTrevDm8sL9h+Nu6TPi8x+jHBv2pL+w-M9gyBgpg at mail.gmail.com>, Jacob Slater <jacob at rezero.org> 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. Well, one could view such situations as being analogous to placing an ad in the personals section of Craigslist which only says that one is "into rough encounters". If some Craigslist editor/moderator or some third party comes along and asks you to explain exactly what you meant by that, well then (a) explaning your meaning seems like a very tiny burden to bear and also (b) it doesn't seem like an unfair or undue burden, given that you could pretty easily have made your intentions clear from the outset. (And likewise, it is apparently pretty easy for anyone to register a route object in the RIPE DB.) >I agree that it may be presumptuous to guess at how much time will be >wasted without any justification. That said, I have seen a significant >number of recent reports on various mailing lists of accused hijackers. >While some of them have been accurate, some of them definitively jump to >premature conclusions. In the process of explaining the problem, you may very well have put forward its solution also. Perhaps somebody... I won't suggest who... should set up a mailing list to allow anybody and everybody to present and pre-discusss allegations of hijacking, with an eye toward providing a gentle and helpful education to those folks who may misjudge certain specific situations. It's just an idea. Probably worth what you paid for it. My hope and belief is that reasonable persons of good will can and will discuss allegations and seek the facts and clarity, eevn if left to themselves to do so on a privately run mailing list. Are any of the mailing lists you have referred to already appropriate for such early discussions? Are any of them already open to the general public? Regards, rfg
- 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 ]