RIPE NCC Procedure Regarding LIR Information in the RIPE Database
Dear Pierre, all, In response to your emails, here is some general information on this matter. The RIPE NCC requests that the LIRs provide the RIPE NCC with truthful information, as well as correctly maintain their registration in the RIPE Database at all times. If an LIR fails to do so, the RIPE NCC will terminate the service agreement with this LIR and deregister the Internet number resources allocated to it. More information about this procedure can be found in the RIPE NCC procedural document "Closure of LIR and Deregistration of Internet Number Resources", available at: https://www.ripe.net/ripe/docs/ripe-517 The RIPE NCC handles abuse complaints sent by third parties. Anyone can send a complaint to abuse@ripe.net. As well as the procedures already in place, the RIPE community recently formed the Abuse Contact Management Task Force (ACM-TF), which is examining policy proposals around the issue of managing the abuse contact field in the RIPE Database. More information about the task force can be found at: https://www.ripe.net/ripe/groups/tf/abuse-contact Hope this clarifies the existing procedures, if you have any further questions, please do not hesitate to contact us. Kind regards, Athina Fragkouli RIPE NCC
-----Original Message----- From: anti-abuse-wg-admin@ripe.net [mailto:anti-abuse-wg- admin@ripe.net] On Behalf Of Athina Fragkouli Sent: Wednesday, July 27, 2011 11:47 AM To: anti-abuse-wg@ripe.net
The RIPE NCC requests that the LIRs provide the RIPE NCC with truthful information, as well as correctly maintain their registration in the RIPE Database at all times. If an LIR fails to do so, the RIPE NCC will terminate the service agreement with this LIR and deregister the Internet number resources allocated to it.
More information about this procedure can be found in the RIPE NCC procedural document "Closure of LIR and Deregistration of Internet Number Resources", available at: https://www.ripe.net/ripe/docs/ripe-517
The RIPE NCC handles abuse complaints sent by third parties. Anyone can send a complaint to abuse@ripe.net.
Can you estimate how many cases of incorrect registration data third parties have reported to the RIPE NCC since RIPE-517 became effective and how the final results of those reports are distributed between e.g. compliance and deregistration? -- Thor Kottelin http://www.anta.net/
And if possible a geographical breakdown of regions from which LIRs were de-registered. On Wed, Jul 27, 2011 at 4:42 PM, Thor Kottelin <thor.kottelin@turvasana.com> wrote:
Can you estimate how many cases of incorrect registration data third parties have reported to the RIPE NCC since RIPE-517 became effective and how the final results of those reports are distributed between e.g. compliance and deregistration?
-- Suresh Ramasubramanian (ops.lists@gmail.com)
I personally find this (By region) segregative. It only can lead to segregation. Againt all concepts of the Internet. If Martians want to access the Internet? Ok! No problem but as long as they behave in a civil manner. Same thing for the "Kinglons" from planet #45067. No single individual has ever been the basic mold for all of us. That was proven false so very often in history. Do not initiate this here please? antispam.report
-----Original Message----- From: ops.lists@gmail.com Sent: Wed, 27 Jul 2011 17:20:44 +0530 To: thor.kottelin@turvasana.com Subject: Re: [anti-abuse-wg] RIPE NCC Procedure Regarding LIR Information in the RIPE Database
And if possible a geographical breakdown of regions from which LIRs were de-registered.
On Wed, Jul 27, 2011 at 4:42 PM, Thor Kottelin <thor.kottelin@turvasana.com> wrote:
Can you estimate how many cases of incorrect registration data third parties have reported to the RIPE NCC since RIPE-517 became effective and how the final results of those reports are distributed between e.g. compliance and deregistration?
-- Suresh Ramasubramanian (ops.lists@gmail.com)
____________________________________________________________ Send any screenshot to your friends in seconds... Works in all emails, instant messengers, blogs, forums and social networks. TRY IM TOOLPACK at http://www.imtoolpack.com/default.aspx?rc=if2 for FREE
I would personnaly expect a number at most. "Who, Where, what region" is to my view, confidential. It was already said by Athina Fragkouli that RIPE just acquired that new bike not so long ago. Got it approved, put licenses plate on it and began to take its first rides on it... What do you expect? 10,000 deregistrations? I don't think that the best one can do just as he receives his brand new care is to ride it top speed. In short, just file well corroborated complaints for filthy registrations to begin with, and let them go! If the weird filthy registration come back over & over even after months that the complaint was forwarded to RIPE, we'll see... But for now... Why wouldn't you give it a little push forward, Hum? antispam.report
-----Original Message----- From: thor.kottelin@turvasana.com Sent: Wed, 27 Jul 2011 14:12:30 +0300 To: anti-abuse-wg@ripe.net Subject: RE: [anti-abuse-wg] RIPE NCC Procedure Regarding LIR Information in the RIPE Database
-----Original Message----- From: anti-abuse-wg-admin@ripe.net [mailto:anti-abuse-wg- admin@ripe.net] On Behalf Of Athina Fragkouli Sent: Wednesday, July 27, 2011 11:47 AM To: anti-abuse-wg@ripe.net
The RIPE NCC requests that the LIRs provide the RIPE NCC with truthful information, as well as correctly maintain their registration in the RIPE Database at all times. If an LIR fails to do so, the RIPE NCC will terminate the service agreement with this LIR and deregister the Internet number resources allocated to it.
More information about this procedure can be found in the RIPE NCC procedural document "Closure of LIR and Deregistration of Internet Number Resources", available at: https://www.ripe.net/ripe/docs/ripe-517
The RIPE NCC handles abuse complaints sent by third parties. Anyone can send a complaint to abuse@ripe.net.
Can you estimate how many cases of incorrect registration data third parties have reported to the RIPE NCC since RIPE-517 became effective and how the final results of those reports are distributed between e.g. compliance and deregistration?
-- Thor Kottelin http://www.anta.net/
____________________________________________________________ Send any screenshot to your friends in seconds... Works in all emails, instant messengers, blogs, forums and social networks. TRY IM TOOLPACK at http://www.imtoolpack.com/default.aspx?rc=if2 for FREE
Thank you so much Dear Athina. You sure made all this very consise. However, I guess that I don't have so many of these "Erroneous" registration datas. Simply because as all societies of homosapiens on planet earth are quite a bit of the same thing: -Most are the "Simple Average" individual. Croocked minds amount to much less than 5% of any given population, at most.. In short, I do not expect to submit more than (1-3) "Request for data update" for any network to whom RIPE would have allocated IP#. More over, before doing so, I would subtanciate my claim in a formal manner so that the claim cannot be denied. The only thing left to do would be to verify the whole. Otherwise, RIPE could be flooded by complaints? And organized abusers would have reasons to flood abuse (at) RIPE? This is why that in my thoughts, I feel it is a good thing that such complaints are signified by peoples who possess a minimal amount of skills within that matter? H owever, I will simply follow the rules as long that there are rules, I am happy! In hope that all Internet IP registration organisms such as RIPE will jump aboard, which may not be the case at present time because of language, I sincerly thank you, Athina. antispam.reporter.
-----Original Message----- From: athina.fragkouli@ripe.net Sent: Wed, 27 Jul 2011 10:46:49 +0200 To: anti-abuse-wg@ripe.net Subject: [anti-abuse-wg] RIPE NCC Procedure Regarding LIR Information in the RIPE Database
Dear Pierre, all,
In response to your emails, here is some general information on this matter.
The RIPE NCC requests that the LIRs provide the RIPE NCC with truthful information, as well as correctly maintain their registration in the RIPE Database at all times. If an LIR fails to do so, the RIPE NCC will terminate the service agreement with this LIR and deregister the Internet number resources allocated to it.
More information about this procedure can be found in the RIPE NCC procedural document "Closure of LIR and Deregistration of Internet Number Resources", available at: https://www.ripe.net/ripe/docs/ripe-517
The RIPE NCC handles abuse complaints sent by third parties. Anyone can send a complaint to abuse@ripe.net.
As well as the procedures already in place, the RIPE community recently formed the Abuse Contact Management Task Force (ACM-TF), which is examining policy proposals around the issue of managing the abuse contact field in the RIPE Database. More information about the task force can be found at: https://www.ripe.net/ripe/groups/tf/abuse-contact
Hope this clarifies the existing procedures, if you have any further questions, please do not hesitate to contact us.
Kind regards, Athina Fragkouli RIPE NCC
____________________________________________________________ Send any screenshot to your friends in seconds... Works in all emails, instant messengers, blogs, forums and social networks. TRY IM TOOLPACK at http://www.imtoolpack.com/default.aspx?rc=if2 for FREE
On Wed, Jul 27, 2011 at 1:46 PM, Athina Fragkouli <athina.fragkouli@ripe.net
wrote:
Dear Pierre, all,
In response to your emails, here is some general information on this matter.
The RIPE NCC requests that the LIRs provide the RIPE NCC with truthful information, as well as correctly maintain their registration in the RIPE Database at all times. If an LIR fails to do so, the RIPE NCC will terminate the service agreement with this LIR and deregister the Internet number resources allocated to it.
What is the procedure to check if the information is valid or not? How RIPE can make a judgement?
More information about this procedure can be found in the RIPE NCC procedural document "Closure of LIR and Deregistration of Internet Number Resources", available at: https://www.ripe.net/ripe/**docs/ripe-517<https://www.ripe.net/ripe/docs/ripe-517>
The RIPE NCC handles abuse complaints sent by third parties. Anyone can send a complaint to abuse@ripe.net.
Never received a positive response from abuse@ripe
As well as the procedures already in place, the RIPE community recently formed the Abuse Contact Management Task Force (ACM-TF), which is examining policy proposals around the issue of managing the abuse contact field in the RIPE Database. More information about the task force can be found at: https://www.ripe.net/ripe/**groups/tf/abuse-contact<https://www.ripe.net/ripe/groups/tf/abuse-contact>
Hope this clarifies the existing procedures, if you have any further questions, please do not hesitate to contact us.
Kind regards, Athina Fragkouli RIPE NCC
Regards, Aftab A. Siddiqui
On 08/08/2011 12:36 AM, abuse@localhost.com wrote: OK, since a lot of posts took place from this account, could you please at least state your name? An abuse@localhost.com can be just about anything. Now, if I understand correctly from your posts, because most of the stuff written is incomprehensible to me, you seem to pose an issue about abuse contacts and validity of contact data in RIPE DB. There is a task force [1] that was created for this reason and we all expect information about its progress and outcome. Regards, Kostas Zorbadelos [1] http://www.ripe.net/ripe/groups/tf/abuse-contact
For the least: An example... What if a few of the email addresses provided to RIPE by a concerned network who was allocated this or that IP Block numbers is wrong? Or simply bounce back for any reason?
...
He seems to have an entirely different issue - of some netblocks being obtained with entirely faked whois records. Like, the physical address for a netblock is an empty lot between two garages, etc. While the abuse contact wg would be good to develop a standard format for noting an abuse contact in RIPE whois, it is hardly the place to deal with netblocks registered with fake contact information, and quite possibly registered with faked justification paperwork. RIPE's existing policies *should* cover this - but there's a notable lack of a formalzed resolution process on the lines of wdprs for domains. thanks suresh On Mon, Aug 8, 2011 at 12:13 PM, Kostas Zorbadelos <kzorba@otenet.gr> wrote:
Now, if I understand correctly from your posts, because most of the stuff written is incomprehensible to me, you seem to pose an issue about abuse contacts and validity of contact data in RIPE DB. There is a task force [1] that was created for this reason and we all expect information about its progress and outcome.
-- Suresh Ramasubramanian (ops.lists@gmail.com)
RIPE's existing policies *should* cover this - but there's a notable lack of a formalzed resolution process on the lines of wdprs for domains.
And it is a problem that has been noted many times by many different people, so abuse@localhost.com is in some way preaching to the choir. That being said, imho the choir needs to get off it's butt and really start taking action on these policies instead of them being just that. Policies without succession. The work is in progress, but progress is, well, s.l.o.w. I've found the RIPE LEA Roundtables are one of the best ways to talk to people directly. Maybe abuse@ could voice his/her concerns there too. +++++++++++++++++++++++++++++++++++++++++++++ Disclaimer Dit e-mailbericht kan vertrouwelijke informatie bevatten of informatie die is beschermd door een beroepsgeheim. Indien dit bericht niet voor u is bestemd, wijzen wij u erop dat elke vorm van verspreiding, vermenigvuldiging of ander gebruik ervan niet is toegestaan. Indien dit bericht blijkbaar bij vergissing bij u terecht is gekomen, verzoeken wij u ons daarvan direct op de hoogte te stellen via tel.nr 070 315 3500 of e-mail mailto:mail@opta.nl en het bericht te vernietigen. Dit e-mailbericht is uitsluitend gecontroleerd op virussen. OPTA aanvaardt geen enkele aansprakelijkheid voor de feitelijke inhoud en juistheid van dit bericht en er kunnen geen rechten aan worden ontleend. This e-mail message may contain confidential information or information protected by professional privilege. If it is not intended for you, you should be aware that any distribution, copying or other form of use of this message is not permitted. If it has apparently reached you by mistake, we urge you to notify us by phone +31 70 315 3500 or e-mail mailto:mail@opta.nl and destroy the message immediately. This e-mail message has only been checked for viruses. The accuracy, relevance, timeliness or completeness of the information provided cannot be guaranteed. OPTA expressly disclaims any responsibility in relation to the information in this e-mail message. No rights can be derived from this message.
Agreed. Policies without teeth, an enforcement mechanism and SOP to follow that mechanism are about as useful as toilet paper is. Maybe less .. On Mon, Aug 8, 2011 at 2:25 PM, Vissers, Pepijn <P.Vissers@opta.nl> wrote:
And it is a problem that has been noted many times by many different people, so abuse@localhost.com is in some way preaching to the choir.
That being said, imho the choir needs to get off it's butt and really start taking action on these policies instead of them being just that. Policies without succession. The work is in progress, but progress is, well, s.l.o.w.
I've found the RIPE LEA Roundtables are one of the best ways to talk to people directly. Maybe abuse@ could voice his/her concerns there too.
-- Suresh Ramasubramanian (ops.lists@gmail.com)
Bwaff! Who care if the abuse email addy is either "Boogaloo-wedoo@domain-name.xxx? I wouldn't have even have any problem if it'd be boulagalou@domain.name.xxx! As long as the email provided to RIPE for the registration of the given IP# numbers allocated by RIPE, who care really? Same thing for the other datas that this or that network owner gave to RIPE, which includes its LIRs. Give any datas you feel like including a country located on planet "Kinglon" but if you stumble on someone who request the verifications, rest assure that RIPE has all reasons to request these to be accurates and that the email address be live just like civic address needs be verifiables. Those againts this principle of "Intellectual Integretity" principle, please signigfy your position. We'll take good note of it. ____________________________
-----Original Message----- From: p.vissers@opta.nl Sent: Mon, 8 Aug 2011 08:55:50 +0000 To: anti-abuse-wg@ripe.net Subject: RE: [anti-abuse-wg] RIPE NCC Procedure Regarding LIR Information in the RIPE Database
RIPE's existing policies *should* cover this - but there's a notable lack of a formalzed resolution process on the lines of wdprs for domains.
And it is a problem that has been noted many times by many different people, so abuse@localhost.com is in some way preaching to the choir.
That being said, imho the choir needs to get off it's butt and really start taking action on these policies instead of them being just that. Policies without succession. The work is in progress, but progress is, well, s.l.o.w.
I've found the RIPE LEA Roundtables are one of the best ways to talk to people directly. Maybe abuse@ could voice his/her concerns there too.
+++++++++++++++++++++++++++++++++++++++++++++ Disclaimer Dit e-mailbericht kan vertrouwelijke informatie bevatten of informatie die is beschermd door een beroepsgeheim. Indien dit bericht niet voor u is bestemd, wijzen wij u erop dat elke vorm van verspreiding, vermenigvuldiging of ander gebruik ervan niet is toegestaan. Indien dit bericht blijkbaar bij vergissing bij u terecht is gekomen, verzoeken wij u ons daarvan direct op de hoogte te stellen via tel.nr 070 315 3500 of e-mail mailto:mail@opta.nl en het bericht te vernietigen. Dit e-mailbericht is uitsluitend gecontroleerd op virussen. OPTA aanvaardt geen enkele aansprakelijkheid voor de feitelijke inhoud en juistheid van dit bericht en er kunnen geen rechten aan worden ontleend.
This e-mail message may contain confidential information or information protected by professional privilege. If it is not intended for you, you should be aware that any distribution, copying or other form of use of this message is not permitted. If it has apparently reached you by mistake, we urge you to notify us by phone +31 70 315 3500 or e-mail mailto:mail@opta.nl and destroy the message immediately. This e-mail message has only been checked for viruses. The accuracy, relevance, timeliness or completeness of the information provided cannot be guaranteed. OPTA expressly disclaims any responsibility in relation to the information in this e-mail message. No rights can be derived from this message.
____________________________________________________________ Send any screenshot to your friends in seconds... Works in all emails, instant messengers, blogs, forums and social networks. TRY IM TOOLPACK at http://www.imtoolpack.com/default.aspx?rc=if2 for FREE
http://wdprs.internic.net/ Yes its not perfect Yes it exists and is actively used On Mon, Aug 8, 2011 at 2:50 PM, Kostas Zorbadelos <kzorba@otenet.gr> wrote:
On 08/08/2011 11:03 AM, Suresh Ramasubramanian wrote:
RIPE's existing policies*should* cover this - but there's a notable lack of a formalzed resolution process on the lines of wdprs for domains.
What exactly is "wdprs" ?
Regards,
Kostas
thanks suresh
-- Suresh Ramasubramanian (ops.lists@gmail.com)
On 8 Aug 2011, at 10:18, Suresh Ramasubramanian wrote:
Yes its not perfect Yes it exists and is actively used
That's a reporting tool - not a policy The policy mandates the annual reminder to registrants to check that their whois data is up to date What you might be thinking about is ICANN's various policies on whois .. which are largely flawed
On Mon, Aug 8, 2011 at 2:50 PM, Kostas Zorbadelos <kzorba@otenet.gr> wrote:
On 08/08/2011 11:03 AM, Suresh Ramasubramanian wrote:
RIPE's existing policies*should* cover this - but there's a notable lack of a formalzed resolution process on the lines of wdprs for domains.
What exactly is "wdprs" ?
Regards,
Kostas
thanks suresh
-- Suresh Ramasubramanian (ops.lists@gmail.com)
Mr Michele Neylon Blacknight Solutions Hosting & Colocation, Brand Protection ICANN Accredited Registrar http://www.blacknight.com/ http://blog.blacknight.com/ http://blacknight.mobi/ http://mneylon.tel Intl. +353 (0) 59 9183072 US: 213-233-1612 UK: 0844 484 9361 Locall: 1850 929 929 Direct Dial: +353 (0)59 9183090 Twitter: http://twitter.com/mneylon ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845
On 8 Aug 2011, at 10:20, Kostas Zorbadelos wrote:
On 08/08/2011 11:03 AM, Suresh Ramasubramanian wrote:
RIPE's existing policies*should* cover this - but there's a notable lack of a formalzed resolution process on the lines of wdprs for domains.
What exactly is "wdprs" ?
Whois data reminder policy
Regards,
Kostas
thanks suresh
Mr Michele Neylon Blacknight Solutions Hosting & Colocation, Brand Protection ICANN Accredited Registrar http://www.blacknight.com/ http://blog.blacknight.com/ http://blacknight.mobi/ http://mneylon.tel Intl. +353 (0) 59 9183072 US: 213-233-1612 UK: 0844 484 9361 Locall: 1850 929 929 Direct Dial: +353 (0)59 9183090 Twitter: http://twitter.com/mneylon ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845
On 08.08.2011 10:03, Suresh Ramasubramanian wrote:
While the abuse contact wg would be good to develop a standard format for noting an abuse contact in RIPE whois, it is hardly the place to deal with netblocks registered with fake contact information, and quite possibly registered with faked justification paperwork.
I'd hope some practical hints proposition to define a workable acceptation of the term "faked" is also on-topic.
RIPE's existing policies *should* cover this - but there's a notable lack of a formalized resolution process on the lines of wdprs for domains.
What is the current policy about the right to anonymity, for Whois Data Problem Reporting System? It is often said that e-commerce sites cannot be anonymous. It should be added that email sites also cannot. In fact, an email site may grant the right to anonymity to its users, but IMHO it needs not be anonymous itself for doing so properly.
On 8 Aug 2011, at 10:26, Alessandro Vesely wrote:
On 08.08.2011 10:03, Suresh Ramasubramanian wrote:
While the abuse contact wg would be good to develop a standard format for noting an abuse contact in RIPE whois, it is hardly the place to deal with netblocks registered with fake contact information, and quite possibly registered with faked justification paperwork.
I'd hope some practical hints proposition to define a workable acceptation of the term "faked" is also on-topic.
+1 "out of date", for example, is not "fake" - it's just not accurate *now* Which is a very different proposition to "faked"
RIPE's existing policies *should* cover this - but there's a notable lack of a formalized resolution process on the lines of wdprs for domains.
What is the current policy about the right to anonymity, for Whois Data Problem Reporting System?
In ICANN? That's one of the many reasons why the WHOIS policy is so badly broken
It is often said that e-commerce sites cannot be anonymous. It should be added that email sites also cannot. In fact, an email site may grant the right to anonymity to its users, but IMHO it needs not be anonymous itself for doing so properly.
Mr Michele Neylon Blacknight Solutions Hosting & Colocation, Brand Protection ICANN Accredited Registrar http://www.blacknight.com/ http://blog.blacknight.com/ http://blacknight.mobi/ http://mneylon.tel Intl. +353 (0) 59 9183072 US: 213-233-1612 UK: 0844 484 9361 Locall: 1850 929 929 Direct Dial: +353 (0)59 9183090 Twitter: http://twitter.com/mneylon ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845
On Mon, Aug 8, 2011 at 2:56 PM, Alessandro Vesely <vesely@tana.it> wrote:
On 08.08.2011 10:03, Suresh Ramasubramanian wrote:
While the abuse contact wg would be good to develop a standard format for noting an abuse contact in RIPE whois, it is hardly the place to deal with netblocks registered with fake contact information, and quite possibly registered with faked justification paperwork.
I'd hope some practical hints proposition to define a workable acceptation of the term "faked" is also on-topic.
http://en.wikipedia.org/wiki/I_know_it_when_I_see_it HTH HAND :) Please also apply the concept of mens rea. Is this behavior associated with, say, hosting botnets and snowshoe spam, when the paperworks ays "GRE tunnels", or "dialup pool", just for example?
There may have been a zelote who drag this thread into the "Faked RIPE registration datas" but that was more of a strategy than anything else. If one discovers that some datas for a a RIPE allocated registration is false and erroneous, the complaining party should simply request RIPE to rectify the erroneous. And check back the validity of the registration datas a little later. Simply. It ain't a matter of "Right to anonymity" since anybody who signed with RIPE had a legal responsability to be aware of RIPE's regulation. If one gets into the Internet business and after this of that amount of time in business, remains unaware that RIPE has regulations... Maybe it could time for that network owner to change his job or get some knowledgable employee (S) ? Simple logic.
-----Original Message----- From: vesely@tana.it Sent: Mon, 08 Aug 2011 11:26:21 +0200 To: anti-abuse-wg@ripe.net Subject: Re: [anti-abuse-wg] RIPE NCC Procedure Regarding LIR Information in the RIPE Database
On 08.08.2011 10:03, Suresh Ramasubramanian wrote:
While the abuse contact wg would be good to develop a standard format for noting an abuse contact in RIPE whois, it is hardly the place to deal with netblocks registered with fake contact information, and quite possibly registered with faked justification paperwork.
I'd hope some practical hints proposition to define a workable acceptation of the term "faked" is also on-topic.
RIPE's existing policies *should* cover this - but there's a notable lack of a formalized resolution process on the lines of wdprs for domains.
What is the current policy about the right to anonymity, for Whois Data Problem Reporting System? It is often said that e-commerce sites cannot be anonymous. It should be added that email sites also cannot. In fact, an email site may grant the right to anonymity to its users, but IMHO it needs not be anonymous itself for doing so properly.
____________________________________________________________ TRY FREE IM TOOLPACK at http://www.imtoolpack.com/default.aspx?rc=if5 Capture screenshots, upload images, edit and send them to your friends through IMs, post on Twitter®, Facebook®, MySpace™, LinkedIn® – FAST!
-----Original Message----- From: ops.lists@gmail.com Sent: Mon, 8 Aug 2011 13:33:27 +0530 To: kzorba@otenet.gr Subject: Re: [anti-abuse-wg] RIPE NCC Procedure Regarding LIR Information in the RIPE Database
He seems to have an entirely different issue - of some netblocks being obtained with entirely faked whois records.
Like, the physical address for a netblock is an empty lot between two garages, etc.
While the abuse contact wg would be good to develop a standard format for noting an abuse contact in RIPE whois, it is hardly the place to deal with netblocks registered with fake contact information, and quite possibly registered with faked justification paperwork.
RIPE's existing policies *should* cover this - but there's a notable lack of a formalzed resolution process on the lines of wdprs for domains.
thanks suresh
SNIP! _________________ Suresh, who else could represent any RIPE authority but a RIPE official? I am not that RIPE authority who mentionned the following:=> Further notes below that RIPE email. _______________________________________
From: athina.fragkouli@ripe.net Sent: Wed, 27 Jul 2011 10:46:49 +0200 To: anti-abuse-wg@ripe.net Subject: [anti-abuse-wg] RIPE NCC Procedure Regarding LIR Information in the RIPE Database
Dear Pierre, all,
In response to your emails, here is some general information on this matter.
The RIPE NCC requests that the LIRs provide the RIPE NCC with truthful information, as well as correctly maintain their registration in the RIPE Database at all times. If an LIR fails to do so, the RIPE NCC will terminate the service agreement with this LIR and deregister the Internet number resources allocated to it.
More information about this procedure can be found in the RIPE NCC procedural document "Closure of LIR and Deregistration of Internet Number Resources", available at: https://www.ripe.net/ripe/docs/ripe-517
The RIPE NCC handles abuse complaints sent by third parties. Anyone can send a complaint to abuse@ripe.net.
As well as the procedures already in place, the RIPE community recently formed the Abuse Contact Management Task Force (ACM-TF), which is examining policy proposals around the issue of managing the abuse contact field in the RIPE Database. More information about the task force can be found at: https://www.ripe.net/ripe/groups/tf/abuse-contact
Hope this clarifies the existing procedures, if you have any further questions, please do not hesitate to contact us.
Kind regards, Athina Fragkouli RIPE NCC
Once this is clear, if anybody blame RIPE to exert such scrupulous such an "Intellect Integrety", why dont anybody who's againts these "Pre-existing" regulation get togheters and prepare any sort of vote so that next year anybody getting allocated IP# block numbers or "LIR" for that matter, can give any weird name of network owner, email addresses and civic location from where the network is based when registering to RIPE! Better yet, since RIPE will become a heap of hoaxed datas, why pay these guys to cumulate hoaxed datas? Let's give them their severance pay! And then, be prepare to deal with organized crime 'coze when there is not authority and no regulation, history has teached humankind where it leads. For now & until official RIPE regulations are changed, bring the right, true factual datas to RIPE when RIPE request registration datas. Thank you in advance. ____________________________________________________________ Publish your photos in seconds for FREE TRY IM TOOLPACK at http://www.imtoolpack.com/default.aspx?rc=if4
participants (9)
-
abuse＠localhost.com -
Aftab Siddiqui -
Alessandro Vesely -
Athina Fragkouli -
Kostas Zorbadelos -
Michele Neylon :: Blacknight -
Suresh Ramasubramanian -
Thor Kottelin -
Vissers, Pepijn