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/routing-wg@ripe.net/
[routing-wg] Hijacking
- Previous message (by thread): [routing-wg] Hijacking
- Next message (by thread): [routing-wg] Hijacking
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jacob Slater
jacob at rezero.org
Tue Jun 26 23:42:53 CEST 2018
> > When it comes to issues of routing, e.g. the gibberish currently coming > out of AS3266, I think that it is already well and widely understood that > the the one and only "enforcement" mechanism that exists is what might > simply be called "peer pressure". > Apologies for misinterpreting your original point. In short, I don't think that it takes all that much in the way of mental > gymnastics to tease apart the intent and spirit of a contractual term > and its enforcement. These are clearly two separate things. In contrast, I think that it is a reasonable assumption to say that > very nearly 100% of all RIPE members do at least glance over the > contracts they sign with RIPE before they sign them. > Are you suggesting that the NCC should include a statement in the LIR account agreement (discouraging hijacking) that they will subsequently not intend to enforce (in most if not all cases)? While the threat of legal action might scare some off, I don't feel like it will convince the majority of hijackers to cease, less so if it is known that the NCC is unlikely to enforce it. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20180626/a85c57e0/attachment.html>
- Previous message (by thread): [routing-wg] Hijacking
- Next message (by thread): [routing-wg] Hijacking
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]