<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style></style></head><body lang=EN-IN link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-GB>When it becomes possible to commit rape or murder on an ASN or prefix we can continue this interesting thought experiment I am sure .. but till then can we please confine ourselves to the bounds of reality? Thanks.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:12.0pt;color:black'>From: </span></b><span style='font-size:12.0pt;color:black'>anti-abuse-wg <anti-abuse-wg-bounces@ripe.net> on behalf of Lu Heng <h.lu@anytimechinese.com><br><b>Date: </b>Saturday, 23 March 2019 at 3:34 PM<br><b>To: </b>ac <ac@main.me><br><b>Cc: </b>"anti-abuse-wg@ripe.net" <anti-abuse-wg@ripe.net><br><b>Subject: </b>Re: [anti-abuse-wg] 2019-03 and over-reach<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>Nick are making good point.<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>How about murder is a policy violation?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>How about rape is a policy violation?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Putting RIPE NCC in a juridical position just not what RIPE NCC is.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>And start using the threat “if you do bad thing(whatever that is) we will take your IP number back” just simply a bad thing both for community as well as for the registry.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>It’s very much like electricity company tell you if you do something bad we will cut you off and stop supply electricity.and yes, they will cut you if you stop paying them, but that doesn’t mean they can make themselve self juridical court in any bad thing happen in this world.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Internet, or registry, are starting if not already is, become part of base infrastructure of the society, but that does not give us any rights in the society to become the supreme court of the society, just like your water company or electricity company won’t judge you for what you use water or electricity for.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Sat, Mar 23, 2019 at 16:54 ac <<a href="mailto:ac@main.me">ac@main.me</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal style='margin-bottom:12.0pt'><br>ugh, english. I do not mean external as in outside I meant external as in not<br>allocated.<br><br>for example: complaint received about <a href="http://147g8oobra912cx47.com" target="_blank">147g8oobra912cx47.com</a><br><br>versus a HIJACKING complaint received about <a href="http://apple.com" target="_blank">apple.com</a><br><br>my argument would be that; as 147Goobra912cX.com is not allocated, any<br>complaints about such a resource is outside the scope of any<br>administrative authority - and ianal, but, some of what Nick Hilliard<br>said, may apply. Same as abuse BY a resource, when what Nick Hilliard<br>said, may also apply.<br><br>The main point is that;<br><br>Because: "hijacking" of a domain name (or any resource) is a direct<br>administrative issue (this is factual - as per my previous post)<br><br>BUT<br><br>abuse BY a domain name (or any resource) is not necessarily an<br>administrative issue at all (this is debatable/opinion) - as you said<br>"some" TLD responds some do not...and RIPE NCC is not the Internet<br>Police....<br><br>So, anyway, as 2019-03 deals with hijacking, this entire over reach<br>argument is factually not relevant at all<br><br>and, more so: 2019-03 not proceeding would be counter to the ethical<br>administration of resources, a dereliction of responsibility and a breach <br>of trust implied in any such administration (as well as administrative authority)<br><br><br>On Sat, 23 Mar 2019 08:20:01 +0000<br>Suresh Ramasubramanian <<a href="mailto:ops.lists@gmail.com" target="_blank">ops.lists@gmail.com</a>> wrote:<br><br>> They either find out for themselves or someone else points it out to<br>> them. In either case their responsibility continues if what you say<br>> holds good<br>> <br>> --srs<br>> <br>> ________________________________<br>> From: anti-abuse-wg <<a href="mailto:anti-abuse-wg-bounces@ripe.net" target="_blank">anti-abuse-wg-bounces@ripe.net</a>> on behalf of ac<br>> <<a href="mailto:ac@main.me" target="_blank">ac@main.me</a>> Sent: Saturday, March 23, 2019 1:44 PM<br>> To: <a href="mailto:anti-abuse-wg@ripe.net" target="_blank">anti-abuse-wg@ripe.net</a><br>> Subject: Re: [anti-abuse-wg] 2019-03 and over-reach<br>> <br>> <br>> some of what the wg discusses are opinions and some things are<br>> scientific facts.<br>> <br>> scientific facts may change as environments and other variables<br>> change, but currently it is so that;<br>> <br>> there is NO TLD registry that will allow the ongoing random hijacking<br>> of domain names (under that TLD of course)<br>> <br>> as, this would mean that the TLD does not need to exist at all and/or<br>> it will not have any trust/value.<br>> <br>> RIPE NCC though, is factually a resource administrative authority.<br>> <br>> As such, it does need to administer resources and an integral part of<br>> that resource administration is the core responsibility implied by<br>> such administration itself and the balance of exercising such<br>> authority with the implied and direct responsibility of any such<br>> administration.<br>> <br>> Factually, the authority to allocate (or not) is administrative.<br>> <br>> I think (my opinion) is that the confusion arises due to whether a<br>> resource (whether it be a domain name, ip number, etc) is allocated,<br>> or not. When resources are allocated the administrative responsibility<br>> is not degraded, in fact a very strong argument could be made that the<br>> inverse is true: Allocated resources increases the level of<br>> administrative authority, responsibility and all of the administration<br>> aspects themselves.<br>> <br>> Now, TLD (or RIPE NCC) managing **"external"** complaints about direct<br>> abuse, is, imho, outside the scope of an administrative authority and<br>> would be the scenario Nick Hilliard refers to. Then again, this is my<br>> opinion, so I may be completely wrong (or not) :)<br>> <br>> On Sat, 23 Mar 2019 07:27:40 +0000<br>> Suresh Ramasubramanian <<a href="mailto:ops.lists@gmail.com" target="_blank">ops.lists@gmail.com</a>> wrote:<br>> <br>> > There's also the interesting comparison of how some TLD registries -<br>> > many of them - act on canceling spam and phish domains while others<br>> > go to every extreme not to do so.<br>> ><br>> > --srs<br>> ><br>> > ________________________________<br>> > From: anti-abuse-wg <<a href="mailto:anti-abuse-wg-bounces@ripe.net" target="_blank">anti-abuse-wg-bounces@ripe.net</a>> on behalf of ac<br>> > <<a href="mailto:ac@main.me" target="_blank">ac@main.me</a>> Sent: Saturday, March 23, 2019 11:16 AM<br>> > To: <a href="mailto:anti-abuse-wg@ripe.net" target="_blank">anti-abuse-wg@ripe.net</a><br>> > Subject: Re: [anti-abuse-wg] 2019-03 and over-reach<br>> ><br>> > On Fri, 22 Mar 2019 17:13:20 +0000<br>> > Nick Hilliard <<a href="mailto:nick@foobar.org" target="_blank">nick@foobar.org</a>> wrote: <br>> > > Regarding over-reach, the RIPE NCC was instituted as a numbering<br>> > > registry and as a supporting organisation for the RIPE Community,<br>> > > whose terms of reference are described in the RIPE-1 document. The<br>> > > terms of reference make it clear that the purpose of the RIPE<br>> > > Community and the RIPE NCC is internet co-ordination and -<br>> > > pointedly<br>> > > - not enforcement. Proposal 2019-03 goes well outside the scope of<br>> > > what the RIPE Community and the RIPE NCC were constituted to do,<br>> > > and I do not believe that the Anti Abuse working group has the<br>> > > authority to override this.<br>> > > <br>> > the wg is not overriding anything. 2019-03 is about removing<br>> > resources, in much the same way as same resources would have been<br>> > removed for payment. (RIPE NCC accounts person would "judge" that<br>> > there was no payment and resources would be affected)<br>> ><br>> > Just because there is a decision it does not mean that such a<br>> > decision<br>> ><br>> > is "law enforcement" or judicial.<br>> ><br>> > 2019-03 is administrative<br>> ><br>> > and not legal/law/judicial<br>> > <br>> > > The second point relates to the long term consequences of the<br>> > > proposal. If the RIPE Community were to pass this policy, then it<br>> > > would direct the RIPE NCC to act as both a judiciary and policing<br>> > > agency for internet abuse. Judgement and enforcement of behaviour<br>> > > are the competence of national governments, courts and law <br>> ><br>> > No. You are saying the same thing, though eloquently, in a different<br>> > way and trying to link it to some future potential hijacking by gov<br>> > of RIR.<br>> ><br>> > It is not much of a decision that RIPE NCC has to make either as:<br>> ><br>> > 1. There was hijacking<br>> ><br>> > OR<br>> ><br>> > 2. There was no hijacking<br>> ><br>> > Whether it was accidental, ongoing for long period of time and all<br>> > the other technical and scientific facts, this may require some<br>> > sort of interpretation of facts.<br>> ><br>> > But, not whether it actually happened or not.<br>> > <br>> > ><br>> > > But, this is not how to handle the problem of BGP hijacking. Even<br>> > > if it had the slightest possibility of making any difference at a<br>> > > technical level (which it won't), the proposal would set the RIPE<br>> > > Community and the RIPE NCC down a road which I believe would be<br>> > > extremely unwise to take from a legal and political point of view,<br>> > > and which would be difficult, if not impossible to manoeuver out<br>> > > of. <br>> > ianal, NCC legal will surely evaluate the legal aspects, but<br>> > practically every new shell company that has to deal with compliance<br>> > and other issues is just another layer in the onion.<br>> ><br>> ><br>> ><br>> ><br>> > <br>> <br>> <br><br><o:p></o:p></p></blockquote></div></div><p class=MsoNormal>-- <o:p></o:p></p><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>--<br>Kind regards.<br>Lu<o:p></o:p></p></div></div></div></div></body></html>