From noreply at ripe.net Tue Nov 2 13:50:21 2010 From: noreply at ripe.net (Axel Pawlik) Date: Tue, 02 Nov 2010 13:50:21 +0100 Subject: [ncc-services-wg] Draft Document: "Closure of LIR and Deregistration of Internet Number Resources" Message-ID: <4CD0090D.5020106@ripe.net> [Apologies for duplicate emails] Dear colleagues, The RIPE NCC, in consultation with external legal experts, created the draft procedural document, "Closure of LIR and Deregistration of Internet Number Resources". A PDF of the document is available at: http://www.ripe.net/legal/Closure-of-LIR-and-deregistration-of-INRs_final-draft.pdf The text of this document is intended to replace sections in two RIPE Documents that deal with the closure of LIRs and the deregistration of resources: - Sections 3.0 and 4.0 of ripe-301, "Mergers, Acquisitions, Takeovers and Closures of Organisations Operating an LIR". These sections are entitled "Closing an LIR" and "When an LIR is Closed by the RIPE NCC", respectively. The original RIPE Document is available at: http://www.ripe.net/ripe/docs/mergers.html - Section 4.2 of ripe-475, "Independent Internet Number Resources - Contractual Relationship Changes between sponsoring LIR and End User". This section is entitled "Violation of RIPE Policy, Law or Contract". The original RIPE Document is available at: http://www.ripe.net/ripe/docs/ripe-475.html The RIPE NCC would like to receive feedback on this draft document from its members and the RIPE community. The RIPE NCC members and the RIPE community will have the opportunity to discuss the document on the mailing lists and at the RIPE NCC Services Working Group to be held on 17 November at the RIPE 61 Meeting in Rome. Best regards, Axel Pawlik Managing Director RIPE NCC From mir at ripe.net Thu Nov 4 16:33:14 2010 From: mir at ripe.net (Mirjam Kuehne) Date: Thu, 04 Nov 2010 16:33:14 +0100 Subject: [ncc-services-wg] New RIPE Database Prototype - on RIPE Labs Message-ID: <4CD2D23A.8050701@ripe.net> [apologies for duplicates] Dear colleagues, The RIPE NCC is improving the RIPE Database functionality and usability by introducing a trial of an improved service. With this new service it is easier for any user to see which of the data objects they?re looking at are maintained by the RIPE NCC or an Internet resource holder. Please read more on RIPE Labs: http://labs.ripe.net/Members/Paul_P_/a-new-ripe-database-prototype Kind Regards, Mirjam Kuehne RIPE NCC From BSanghani at relianceglobalcom.com Fri Nov 5 11:03:58 2010 From: BSanghani at relianceglobalcom.com (Bijal Sanghani) Date: Fri, 5 Nov 2010 10:03:58 +0000 Subject: [ncc-services-wg] Draft Agenda - NCC Services WG - RIPE 61 Message-ID: <891E52B6F6F62E4F9376CAA357C17C1580970F18@LON-MBX01.RGCOM.COM> Dear All, Please see below the draft agenda for the NCC Services Working Group - DRAFT: Services WG Agenda - RIPE 61 A. Administrative Matters Welcome Select a Scribe Distribute participants list Finalise agenda Approve minutes from RIPE 60 B. RIPE NCC Update - RIPE NCC Senior Management Team (35 min) C. RIPE NCC Processes and IPv4 Address Space End-Game - Andrea Cima (15 min) D. Update on the 2007-1 Project - Arne Kiessling (10 min) E. Resource Certification - Alex Band (15 min) F. LIR Closure and Deregistration Procedure - Athina Fragkouli (15 min) Z. AOB You can also find the agenda here - http://ripe61.ripe.net/programme/meeting-plan/services-agenda/ look forward to seeing you in Rome! Kind regards, Bijal Sanghani The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: From goober at epir.ksp.sk Fri Nov 5 19:24:46 2010 From: goober at epir.ksp.sk (Peter Kosinar) Date: Fri, 5 Nov 2010 19:24:46 +0100 (CET) Subject: [ncc-services-wg] Discrepancy between WHOIS and delegated-ripencc Message-ID: Hello! This might not be the appropriate place for my question; if that is so, I apologize in advance. I've noticed that the data provided by the RIPE WHOIS database is sometimes inconsistent with the data shown in the delegated-ripencc-latest file, available from the ftp://ftp.ripe.net/ripe/stats/ server. For example, consider these two entries: ------------------------------------------------------- $ whois 91.212.135.0/24 inetnum: 91.212.135.0 - 91.212.135.255 netname: YABA-NET descr: YabaMedia Ltd country: RU $ grep 91.212.135.0 delegated-ripencc-latest ripencc|CZ|ipv4|91.212.135.0|256|20090409|assigned ------------------------------------------------------- $ whois 193.105.207.0/24 inetnum: 193.105.207.0 - 193.105.207.255 netname: ALFAHOSTNET descr: Alfa-host LLP. country: KZ $ grep 193.105.207.0 delegated-ripencc-latest ripencc|CZ|ipv4|193.105.207.0|256|20100315|assigned ------------------------------------------------------- As you can see, the data differs in the "country" field -- in both cases, the range is attributed to Czech Republic, while the block is actually assigned to anothers. Since the delegated-ripencc-latest file is used by some reputable and often-used sources (like Team Cymru; http://www.team-cymru.org/Services/ip-to-asn.html), this can sometime result in misleading and completely useless reports (as you can probably guess, it was Czech Republic getting unfair load of hostile sites attributed to it). There are two questions now: 1) What is the source of this discrepancy? 2) If it was caused by some kind of an error, can the databases be put in sync? If it is intentional, which source is more "reliable"? Thanks, Peter -- [Name] Peter Kosinar [Quote] 2B | ~2B = exp(i*PI) [ICQ] 134813278 From denis at ripe.net Fri Nov 5 21:01:22 2010 From: denis at ripe.net (Denis Walker) Date: Fri, 05 Nov 2010 21:01:22 +0100 Subject: [ncc-services-wg] Discrepancy between WHOIS and delegated-ripencc In-Reply-To: References: Message-ID: <4CD46292.1010107@ripe.net> Dear Peter The "country:" attribute in the RIPE Database can be set by the resource Holder to any valid, international country code. It has little meaning to anyone other than the resource Holder. Only they know what they had in mind when they set it. To explain the problem simply, it could be the country where the resource Holder is physically located, or the country of a data centre or the country where the resource is being used. This has been discussed a few times at RIPE Meetings but no consensus has been reached on a strict definition of this attribute. The RIPE NCC has just published an article on RIPE Labs about an idea to separate some of the registration data in the RIPE Database into two parts. A fixed part containing data supplied to the RIPE NCC by the resource Holder and another part with data the resource Holder can change at any time. In the prototype we have included "country:" in both parts of this data. The intention is to have a strict definition of what 'country' means from a registration perspective in the fixed part of the data. https://labs.ripe.net/Members/Paul_P_/a-new-ripe-database-prototype I hope this helps. Regards Denis Walker Business Analyst RIPE NCC Database Group Peter Kosinar wrote: > Hello! > > This might not be the appropriate place for my question; if that is so, I > apologize in advance. > > I've noticed that the data provided by the RIPE WHOIS database is > sometimes inconsistent with the data shown in the > delegated-ripencc-latest file, available from the > ftp://ftp.ripe.net/ripe/stats/ server. For example, consider these two > entries: > > ------------------------------------------------------- > $ whois 91.212.135.0/24 > > inetnum: 91.212.135.0 - 91.212.135.255 > netname: YABA-NET > descr: YabaMedia Ltd > country: RU > > $ grep 91.212.135.0 delegated-ripencc-latest > ripencc|CZ|ipv4|91.212.135.0|256|20090409|assigned > ------------------------------------------------------- > $ whois 193.105.207.0/24 > > inetnum: 193.105.207.0 - 193.105.207.255 > netname: ALFAHOSTNET > descr: Alfa-host LLP. > country: KZ > > $ grep 193.105.207.0 delegated-ripencc-latest > ripencc|CZ|ipv4|193.105.207.0|256|20100315|assigned > ------------------------------------------------------- > > As you can see, the data differs in the "country" field -- in both > cases, the range is attributed to Czech Republic, while the block is > actually assigned to anothers. Since the delegated-ripencc-latest > file is used by some reputable and often-used sources (like Team > Cymru; http://www.team-cymru.org/Services/ip-to-asn.html), this can > sometime result in misleading and completely useless reports (as you > can probably guess, it was Czech Republic getting unfair load of > hostile sites attributed to it). > > There are two questions now: > 1) What is the source of this discrepancy? > > 2) If it was caused by some kind of an error, can the databases be put in > sync? If it is intentional, which source is more "reliable"? > > Thanks, > > Peter > From sergey at devnull.ru Sat Nov 6 00:05:12 2010 From: sergey at devnull.ru (Sergey Myasoedov) Date: Sat, 6 Nov 2010 00:05:12 +0100 Subject: [ncc-services-wg] Discrepancy between WHOIS and delegated-ripencc In-Reply-To: References: Message-ID: <1636307405.20101106000512@devnull.ru> Hi Peter, probably I know the answer. The first network was registered through our LIR, which is located in Czech republic. The regid of LIR is cz.netart. It seems that quoted file contains the value of LIR country as country field. Whois data is more reliable. I told this several times to many GeoIP providers. Friday, November 5, 2010, 7:24:46 PM, you wrote: PK> Hello! PK> This might not be the appropriate place for my question; if that is so, I PK> apologize in advance. PK> I've noticed that the data provided by the RIPE WHOIS database is PK> sometimes inconsistent with the data shown in the delegated-ripencc-latest PK> file, available from the ftp://ftp.ripe.net/ripe/stats/ server. For PK> example, consider these two entries: PK> ------------------------------------------------------- PK> $ whois 91.212.135.0/24 PK> inetnum: 91.212.135.0 - 91.212.135.255 PK> netname: YABA-NET PK> descr: YabaMedia Ltd PK> country: RU PK> $ grep 91.212.135.0 delegated-ripencc-latest PK> ripencc|CZ|ipv4|91.212.135.0|256|20090409|assigned PK> ------------------------------------------------------- PK> $ whois 193.105.207.0/24 PK> inetnum: 193.105.207.0 - 193.105.207.255 PK> netname: ALFAHOSTNET PK> descr: Alfa-host LLP. PK> country: KZ PK> $ grep 193.105.207.0 delegated-ripencc-latest PK> ripencc|CZ|ipv4|193.105.207.0|256|20100315|assigned PK> ------------------------------------------------------- PK> As you can see, the data differs in the "country" field -- in both cases, PK> the range is attributed to Czech Republic, while the block is actually PK> assigned to anothers. Since the delegated-ripencc-latest file is used by PK> some reputable and often-used sources (like Team Cymru; PK> http://www.team-cymru.org/Services/ip-to-asn.html), this can sometime PK> result in misleading and completely useless reports (as you can probably PK> guess, it was Czech Republic getting unfair load of hostile sites PK> attributed to it). PK> There are two questions now: PK> 1) What is the source of this discrepancy? PK> 2) If it was caused by some kind of an error, can the databases be put in PK> sync? If it is intentional, which source is more "reliable"? PK> Thanks, PK> Peter -- Sergey From mir at ripe.net Tue Nov 16 12:22:57 2010 From: mir at ripe.net (Mirjam Kuehne) Date: Tue, 16 Nov 2010 12:22:57 +0100 Subject: [ncc-services-wg] LIR Portal Migration is done Message-ID: <4CE26991.80403@ripe.net> Dear colleagues, In addition to the announcement sent out yesterday, you can find some more information about the new LIR Portal on RIPE Labs: https://labs.ripe.net/Members/mirjam/lir-portal-migration-main-improvements Kind Regards, Mirjam Kuehne RIPE NCC -------- Original Message -------- Subject: [staff] [ncc-announce] LIR Portal Migration is done Date: Mon, 15 Nov 2010 17:18:47 +0100 From: Kaveh Ranjbar Reply-To: kaveh.ranjbar at ripe.net To: ncc-announce at ripe.net Dear RIPE NCC members, We are proud to announce that the LIR Portal migration project is completed. This means we migrated the LIR Portal to a completely new platform that supports the RIPE NCC's modern back-end technologies. We will be able to respond much faster to changes and will be better able to maintain the LIR Portal. Please email if you have any issue or suggestion concerning the LIR Portal. More detailed technical information will be published on RIPE Labs shortly. Kind regards, Kaveh Ranjbar, Senior Software Engineer, Business Applications Department, RIPE NCC From training at ripe.net Tue Nov 16 13:26:24 2010 From: training at ripe.net (Training Mailbox) Date: Tue, 16 Nov 2010 13:26:24 +0100 Subject: [ncc-services-wg] Announcement: RIPE NCC Training Courses Message-ID: <4CE27870.5000405@ripe.net> [Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC invites you to register for one of our upcoming training courses: - The LIR Training Course This course teaches LIRs how to request Internet number resources and interact with the RIPE NCC. A course outline is available at: http://www.ripe.net/training/lir/outline.html - The Routing Registry Training Course This course teaches LIRs how to use the RIPE Database for routing. A course outline is available at: http://www.ripe.net/training/rr/outline.html - The IPv6 Training Course This course teaches LIRs about the need for IPv6 and includes basic information on how to plan your deployment. A course outline is available at: http://www.ripe.net/training/ipv6/outline.html To see the location of upcoming courses and to register, please use the LIR Portal or complete the registration form on our website at: RIPE NCC Upcoming Courses List & Registration https://lirportal.ripe.net/lirportal/training/course-list.html If you have any questions, please do not hesitate to contact us at . Kind regards, Rumy Kanis Training Services Manager RIPE NCC From mir at ripe.net Wed Nov 17 11:11:06 2010 From: mir at ripe.net (Mirjam Kuehne) Date: Wed, 17 Nov 2010 11:11:06 +0100 Subject: [ncc-services-wg] Returning Unannounced Legacy Space Message-ID: <4CE3AA3A.2020208@ripe.net> Dear colleagues, Are you willing to make resources available for reallocation? Read more on RIPE Labs: http://labs.ripe.net/Members/mirjam/returning-unannounced-legacy-ipv4-address-space This will also be presented later today in the NCC Services WG. Kind Regards, Mirjam Kuehne RIPE NCC