- db-wg - mailman.ripe.net

RIPE 52 Draft Minutes of the DB WG meeting (2nd Draft)
by Nigel Titley 04 May '06

04 May '06

Dear All, Well, I'm quite gratified that people actually read the minutes. Usually I circulate them on the mailing list and get no response at all. I think I've folded in most of the corrections and attach a 2nd version. Thanks to those who have made factual corrections. I published the minutes as quickly as I could so we could get them correct while things were fresh in our minds, hence the somewhat unpolished look. Once we've got the content right I'll do a final polish. All the best Nigel <<DB-minutes.txt>>

1 0

updated RIPE Whois Database User Manual
by Trudy Prins 04 May '06

04 May '06

[Apologies for duplicate e-mails] Dear Colleagues, We are pleased to announce the publication of an updated RIPE Whois Database User Manual. ripe-375 RIPE Whois Database User Manual: Getting Started The content has been revised and updated and we have improved the wording to make it clearer. We have also added extra information about 'webupdates'. You can find the document at: http://www.ripe.net/ripe/docs/db-start.html Regards, Trudy Prins User Support Coordinator Software Engineering Department RIPE NCC

1 0

yet another irrtoolset replacement, 1.0
by md＠Linux.IT 25 Apr '06

25 Apr '06

I released version 1.0 of my routers configuration generator. It can generate the complete BGP configuration (neighbor statements, route maps, prefix and as-path lists) of peering or customer-facing routers using RPSL data, a local configuration file and a configuration template based on the popular Template::Toolkit perl package. Currently I only provide an IOS configuration template, but it should be easy to write one for JUNOS (patches are welcome!). I know that it's being used in production by several ISPs in the RIPE and APNIC region, so if you are not satisfacted by irrtoolset I think it's worth some consideration. It can be downloaded from http://www.linux.it/~md/software/rpsltool-1.0.tgz and is free software released under the terms of the GPL. (I think that I advertised it enough, so future releases will be announced on the project mailing list.) Major changes since the last public release: Modularized and cleaned up the code. Added the routesdiff program (formerly part of my cisco-tools package), to show which routes are actually not being accepted from a peer. Added the testpeerfilter program, to test the effect of a filter on a peer without actually loading it on the router. Added the nagpeer program, to automatically generate reports of bugs in the RPSL objects published by a peer. Added the rpslexpand, to quickly perform RPSL expansion from the command line. Added the findextraobjs program, useful to identify obsolete entries in peers configuration files. Added documentation. -- ciao, Marco

2 2

RIPE52 DB-WG Draft Agenda V3
by Wilfried Woeber, UniVie/ACOnet 25 Apr '06

25 Apr '06

Dear DB-WG folks, Chairpersons, Meeting! Here is the 3rd draft of an agenda for the DB-WG next week at RIPE52 in Istanbul. New since V2: item G. For time slot allocation please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-52/meeting-plan.html Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters - scribe - list of participants - agenda - minutes - "remote participation" coordination (if needed) B. DB Update (N.N., RIPE NCC) [~15 min] C. ENUM delegations (input from DNS-WG, RIPE NCC) [~15 min] D. Proposal to retire CRYPT-PW (Peter K., denic.de + WW144) [~10 min] . PDP proposal E. "48.6 RIPE NCC" (return irt: by default) revisited (RIPE NCC) [~15 min] F. Modify checks for creation of route: (input from Routing-WG) [~10 min] . Brief report on SIDR BoF, IETF65 (tbc, N.N.) G. DB issues when recycling AS Numbers (Leo V., RIPE NCC) [~15 min] H. Client software to use the RoutingRegistry (Rüdiger V., T-Com) [~10 min] . What tools are needed/used to feed router configurations from the databases? Status and perspectives of available software Y. Input from other WGs Z. AOB

2 4

RIPE Database query server is up
by Katie Petrusha 23 Apr '06

23 Apr '06

[Apologies for duplicate mails] Dear colleagues, RIPE Whois Database query server is up. The outage was caused by a flaw in the failover setup of whois servers which we are working on. Sorry for any inconvenience. -- Katie Petrusha RIPE NCC

1 0

Problems with the RIPE Database query server
by Andrei Robachevsky 23 Apr '06

23 Apr '06

Dear Colleagues, At the moment the RIPE whois server is not responding to queries. We are aware of this and working on bringing it back into service. We will keep informing you. Sorry for the inconvenience. Regards, Andrei Robachevsky RIPE NCC

1 0

RIPE52 DB-WG Draft Agenda V34
by Wilfried Woeber, UniVie/ACOnet 20 Apr '06

20 Apr '06

Dear DB-WG folks, Chairpersons, Meeting! Here is the 4th draft of an agenda for the DB-WG next week at RIPE52 in Istanbul. New since V3: reference correct action in item E. to be in line with reality and the minutes. Thanks, Nigel, for pointing this out! For time slot allocation please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-52/meeting-plan.html Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters - scribe - list of participants - agenda - minutes - "remote participation" coordination (if needed) B. DB Update (N.N., RIPE NCC) [~15 min] C. ENUM delegations (input from DNS-WG, RIPE NCC) [~15 min] D. Proposal to retire CRYPT-PW (Peter K., denic.de + WW144) [~10 min] . PDP proposal E. "51.8 RIPE NCC" (return irt: by default) revisited (RIPE NCC) [~15 min] F. Modify checks for creation of route: (input from Routing-WG) [~10 min] . Brief report on SIDR BoF, IETF65 (tbc, N.N.) G. DB issues when recycling AS Numbers (Leo V., RIPE NCC) [~15 min] H. Client software to use the RoutingRegistry (Rüdiger V., T-Com) [~10 min] . What tools are needed/used to feed router configurations from the databases? Status and perspectives of available software Y. Input from other WGs Z. AOB

1 0

RIPE52 DB-WG Draft Agenda V2
by Wilfried Woeber, UniVie/ACOnet 19 Apr '06

19 Apr '06

[apologies for the broken subject line on my previous message .-(] Dear DB-WG folks, Chairs, Meeting! Here is the 2nd draft of an agenda for the DB-WG next week at RIPE52 in Istanbul. For time slot allocation please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-52/meeting-plan.html Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters - scribe - list of participants - agenda - minutes - "remote participation" coordination (if needed) B. DB Update (N.N., RIPE NCC) [~20 min] C. ENUM delegations (input from DNS-WG, RIPE NCC) [~15 min] D. Proposal to retire CRYPT-PW (Peter K., denic.de + WW144) [~10 min] . PDP proposal E. "48.6 RIPE NCC" (return irt: by default) revisited (RIPE NCC) [~15 min] F. Modify checks for creation of route: (input from Routing-WG) [~10 min] . Brief report on SIDR BoF, IETF65 (tbc, N.N.) G. Client software to use the RoutingRegistry (Rüdiger V., T-Com) [~15 min] . What tools are needed/used to feed router configurations from the databases? Status and perspectives of available software Y. Input from other WGs Z. AOB

1 0

[Fwd: [Fwd: [db-wg] RIPE51 DB-WG Draft Agenda V1]]
by Wilfried Woeber, UniVie/ACOnet 19 Apr '06

19 Apr '06

Dear DB-WG folks, Chairs, Meeting! Here is the 1st draft of an agenda for the DB-WG next week at RIPE52 in Istanbul. For time slot allocation please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-52/meeting-plan.html Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters - scribe - list of participants - agenda - minutes - "remote participation" coordination (if needed) B. DB Update (N.N., RIPE NCC) [~20 min] C. ENUM delegations (input from DNS-WG, RIPE NCC) [~15 min] D. Proposal to retire CRYPT-PW (Peter K., denic.de + WW144) [~15 min] . PDP proposal E. "48.6 RIPE NCC" (return irt: by default) revisited (RIPE NCC) [~15 min] F. Modify checks for creation of route: (input from Routing-WG) [~10 min] . brief report on SIDR BoF, IETF65 (tbc, N.N.) Y. Input from other WGs Z. AOB

1 0

Whois Updates down
by Trudy Prins 11 Apr '06

11 Apr '06

[apologies for duplicate mails] Dear Colleagues, >From 11:30 this morning our Whois Update service has been unavailable. Currently, we are investigating what caused this problem. We expect Whois Updates to be available again in approximately 1 hour. We apologise for the inconvenience. If you have any questions or concerns regarding this issue, please contact <ripe-dbm(a)ripe.net>. Regards, -- Trudy Prins RIPE Database Administration

1 3

AW: [db-wg] Adding route objects
by Ihler, Hermann 06 Apr '06

06 Apr '06

Hi Winfried, if OLD-ISP updates his objects as follows it also will work: route: 192.168.231.0/24 descr: Dummy New via old ISP origin: AS1234 mnt-by: OLD-ISP1-MNT mnt-routes: NEW-ISP-MNT source: RIPE # Filtere In this case there is no need for OLD-ISP to insert mnt-by, mnt-routes is sufficient. We often create objects like this. best regards Hermann Ihler _________________________________________ Deutsche Telekom T-Com Headquarters Network Information Center Ammerlaender Heerstrasse 138 DE 26129 Oldenburg +49 441 234 - 4582 (phone) +49 441 234 - 4589 (fax) E-Mail: Hermann.ihler(a)t-com.net -----Ursprüngliche Nachricht----- Von: Winfried Haug [mailto:wh@germany.com] Gesendet: Mittwoch, 5. April 2006 07:40 An: db-wg(a)ripe.net Betreff: [db-wg] Adding route objects Hello, we would like to ask the db-wg working group to change the behavior of adding route objects to the ripe database. I had a discussion with someone from ripe during the routing registry course and he told me that ripe could change the way how route objects can be created but this must be decided by the db-wg. We need route-objects for proper routing via bgp4. As customers may change their upstream they need for a certain amount of time more than one route object. The creating of this new route object failes if the old isp does not respond. Let me give you the following example: inetnum: 192.168.230.0 - 192.168.231.255 netname: DUMMY-NET descr: Customer GmbH country: DE org: ORG-AAAAA-RIPE admin-c: AA1 tech-c: AA1 status: ASSIGNED PI mnt-by: RIPE-NCC-HM-PI-MNT mnt-by: CUSTOMER-MNT mnt-by: NEW-ISP-MNT mnt-lower: RIPE-NCC-HM-PI-MNT mnt-routes: OLD-ISP1-MNT mnt-routes: OLD-ISP2-MNT mnt-routes: NEW-ISP-MNT mnt-domains: OLD-ISP1-MNT mnt-domains: OLD-ISP2-MNT mnt-domains: NEW-ISP-MNT source: RIPE # Filtered route: 192.168.231.0/24 descr: Dummy New via old ISP origin: AS1234 mnt-by: OLD-ISP1-MNT source: RIPE # Filtered we want now add this object parallel to the existing one: route: 192.168.231.0/24 descr: Dummy New via old ISP origin: AS5678 mnt-by: NEW-ISP-MNT source: RIPE # Filtered but fail because: not authenticated by: OLD-ISP1-MNT Thus if OLD-ISP doesnt want for whatever reason help the customer it seems to be that he can block new route objects. This is stupid and can as i know only solved with the help of ripe ncc. It seems to work only if the old isp changed his route object: route: 192.168.231.0/24 descr: Dummy New via old ISP origin: AS1234 mnt-by: OLD-ISP1-MNT source: RIPE # Filtered to route: 192.168.231.0/24 descr: Dummy New via old ISP origin: AS1234 mnt-by: OLD-ISP1-MNT mnt-by: NEW-ISP-MNT source: RIPE # Filtered I think the owner of the network (inetnum object) should be able to create route objects for his IPs. This would solve the problem. Currently he cant do this because the AS does not have his Maintainer i doubt large ISPs want even for a short period customer maintainer in their AS. To avoid abuse, the db should prevent to alter or create route-objects if there is no maintainer in the inetnum object. If the db will accept new route objects created by those who are maintainer in the inetnum object, the customer can do this without help of the old isp or ripe ncc. Could we have some input and comments from the working group ? Winfried Haug --- Headlight Housing Factory | Rechenzentrum: Azenbergstrasse 35 | Neue Bruecke 8 D-70174 Stuttgart | D-70173 Stuttgart Fon: +49 711 2840 0 | e-mail: wh(a)headlight.de Fax: +49 711 2840 999 | http://www.headlight.de

7 6

Adding route objects
by Winfried Haug 06 Apr '06

06 Apr '06

Hello, we would like to ask the db-wg working group to change the behavior of adding route objects to the ripe database. I had a discussion with someone from ripe during the routing registry course and he told me that ripe could change the way how route objects can be created but this must be decided by the db-wg. We need route-objects for proper routing via bgp4. As customers may change their upstream they need for a certain amount of time more than one route object. The creating of this new route object failes if the old isp does not respond. Let me give you the following example: inetnum: 192.168.230.0 - 192.168.231.255 netname: DUMMY-NET descr: Customer GmbH country: DE org: ORG-AAAAA-RIPE admin-c: AA1 tech-c: AA1 status: ASSIGNED PI mnt-by: RIPE-NCC-HM-PI-MNT mnt-by: CUSTOMER-MNT mnt-by: NEW-ISP-MNT mnt-lower: RIPE-NCC-HM-PI-MNT mnt-routes: OLD-ISP1-MNT mnt-routes: OLD-ISP2-MNT mnt-routes: NEW-ISP-MNT mnt-domains: OLD-ISP1-MNT mnt-domains: OLD-ISP2-MNT mnt-domains: NEW-ISP-MNT source: RIPE # Filtered route: 192.168.231.0/24 descr: Dummy New via old ISP origin: AS1234 mnt-by: OLD-ISP1-MNT source: RIPE # Filtered we want now add this object parallel to the existing one: route: 192.168.231.0/24 descr: Dummy New via old ISP origin: AS5678 mnt-by: NEW-ISP-MNT source: RIPE # Filtered but fail because: not authenticated by: OLD-ISP1-MNT Thus if OLD-ISP doesnt want for whatever reason help the customer it seems to be that he can block new route objects. This is stupid and can as i know only solved with the help of ripe ncc. It seems to work only if the old isp changed his route object: route: 192.168.231.0/24 descr: Dummy New via old ISP origin: AS1234 mnt-by: OLD-ISP1-MNT source: RIPE # Filtered to route: 192.168.231.0/24 descr: Dummy New via old ISP origin: AS1234 mnt-by: OLD-ISP1-MNT mnt-by: NEW-ISP-MNT source: RIPE # Filtered I think the owner of the network (inetnum object) should be able to create route objects for his IPs. This would solve the problem. Currently he cant do this because the AS does not have his Maintainer i doubt large ISPs want even for a short period customer maintainer in their AS. To avoid abuse, the db should prevent to alter or create route-objects if there is no maintainer in the inetnum object. If the db will accept new route objects created by those who are maintainer in the inetnum object, the customer can do this without help of the old isp or ripe ncc. Could we have some input and comments from the working group ? Winfried Haug --- Headlight Housing Factory | Rechenzentrum: Azenbergstrasse 35 | Neue Bruecke 8 D-70174 Stuttgart | D-70173 Stuttgart Fon: +49 711 2840 0 | e-mail: wh(a)headlight.de Fax: +49 711 2840 999 | http://www.headlight.de

8 12

AW: [db-wg] Adding route objects
by Ihler, Hermann 31 Mar '06

31 Mar '06

Hi, > But that's winfried's point: the old ISP need to actively enable > creation of the new route object. Yes, you are right, if you have authenticated against the maintainer of the inetnum (mnt-by/mnt-routes) and against the maintainer of the new AS, you should be allowed to create the new route object. But you also have to delete the obsolete old object. And if > The old AS might be bankcrupt, not cooperative, or whatever... you can't, you have to contact RIPE NCC. There is a procedure at RIPE: Ask your customer to send a FAX using the company letterhead paper and signed by one of the responsible contacts of the IP range. The FAX should include the explanation and requesting to remove the route object from the RIPE Database. Submit this FAX to +31 20 535 4341. Ask the customer to include the Ticket Number (if existing) in the FAX. RIPE NCC will remove it then. best regards Hermann Ihler _________________________________________ Deutsche Telekom T-Com Headquarters Network Information Center Ammerlaender Heerstrasse 138 DE 26129 Oldenburg +49 441 234 - 4582 (phone) +49 441 234 - 4589 (fax) E-Mail: Hermann.ihler(a)t-com.net

1 0

Re
by S A 31 Mar '06

31 Mar '06

confirm 352302 --------------------------------- New Yahoo! Messenger with Voice. Call regular phones from your PC for low, low rates.

1 0

Re
by S A 31 Mar '06

31 Mar '06

confirm 352302 --------------------------------- New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.

1 0

WG action 48.6
by md＠Linux.IT 31 Mar '06

31 Mar '06

http://www.ripe.de/ripe/wg/db/minutes/ripe-51.html says: 48.6 RIPE NCC To change DB behaviour to return IRT object [Misunderstanding of requirement, superceded by AP51.8, complete] Can somebody explain this? I tought that everybody agreed that it would be a good idea to always return IRT records for inetnum/inetnum queries, but this is still not happening. I could not find action 51.8 in the draft minutes of the AP WG. -- ciao, Marco

2 1

Call for agenda items, DB-WG Meeting during RIPE52, Istabul
by Wilfried Woeber, UniVie/ACOnet 30 Mar '06

30 Mar '06

Dear DB-WG folks, the RIPE NCC has asked us to submit the draft agendas for the WGs by mid April. Thus, please submit (to the WG list or to me personally) your item requests or suggest topics for discussion to be included in the draft agenda. The DataBase-WG meeting is scheduled for Friday morning, April 28. The overall RIPE meeting outline is available at http://www.ripe.net/ripe/meetings/ripe-52/meeting-plan.html The list of plenary presentations scheduled is available at http://www.ripe.net/ripe/meetings/ripe-52/presentations/ See you in Istanbul, Wilfried.

1 0

Re: [db-wg] Since when does one need 3 nameservers for inverse?
by Ulrich Schmid 28 Mar '06

28 Mar '06

on 8.2.2006 11:10 Uhr Brett Carr wrote: >> -----Original Message----- >> From: db-wg-admin(a)ripe.net On Behalf Of Hank Nussbacher >> Sent: Wednesday, February 08, 2006 10:19 AM >> Cc: rdns-project(a)ripe.net >> Subject: [db-wg] Since when does one need 3 nameservers for inverse? >> >> In the "Reverse Delegation How To": >> http://www.ripe.net/rs/reverse/reverse_howto.html >> it states: >> >> "NS Servers >> Ensure you have at least two nameservers that are >> authoritative for the zone. The resolvable names of these NS >> servers should be in the NS resource records of the zone. The >> nameservers should be on different subnets." >> >> Yet when I submit a request I get: >> ***RDNS: (related to set) ERROR (20 points): At least 3 nameservers >> are required for each properly delegated zone. >> We found only >> 2 in your submission. >> >> In addition the reverse delegation checker at: >> http://www.ripe.net/cgi-bin/delcheck/delcheck2.cgi >> doesn't flag only 2 nameservers as an error. >> >> What gives? >> > > Indeed you are right, something doesn't look quite right here. Thanks for > flagging it I'll take a look. > > Brett > Any news about this item? Changes to the domain objects are still rejected by the delegation checker due to the (wrong) requirement of 3 nameservers and this prevents us to perform simple updates (e.g. contact address changes). Regards Ulrich Schmid

2 1

Re: WHOIS changes
by Hank Hampel 08 Mar '06

08 Mar '06

Hi Marie-Luise, On 4-Mär-2006 Dr. Marie-Luise Hansen wrote: > But how and where do I change the settings? This depends on what whois client you use. If you use the commandline whois client from RIPE you can just use the new flags on the commandline. If you use an other client it may not be able to "understand" the new flags so maybe you should switch to the RIPE client or use the web interface at: http://www.ripe.net/fcgi-bin/whois?form_type=simple&full_query_string=&sear… (this should be one line) Best regards, Hank

4 3

Since when does one need 3 nameservers for inverse?
by Hank Nussbacher 08 Feb '06

08 Feb '06

In the "Reverse Delegation How To": http://www.ripe.net/rs/reverse/reverse_howto.html it states: "NS Servers Ensure you have at least two nameservers that are authoritative for the zone. The resolvable names of these NS servers should be in the NS resource records of the zone. The nameservers should be on different subnets." Yet when I submit a request I get: ***RDNS: (related to set) ERROR (20 points): At least 3 nameservers are required for each properly delegated zone. We found only 2 in your submission. In addition the reverse delegation checker at: http://www.ripe.net/cgi-bin/delcheck/delcheck2.cgi doesn't flag only 2 nameservers as an error. What gives? -Hank

2 1

Announcement Routing Registry Training Courses
by RIPE NCC Training Services 07 Feb '06

07 Feb '06

Dear Colleagues The RIPE NCC Training Services Department invites you to register for one of our upcoming Routing Registry Training Courses: Date: Friday 10 March 2006 Time: 0900 - 1700 Location: Kiev, Ukraine Hosted by: Hosted by EDU Incom And Date: Tuesday 11 April 2006 Time: 0900 - 1700 Location: London, United Kingdom And Date: Friday 5 May 2006 Time: 0900 - 1700 Location: Valletta, Malta And Date: Friday 12 May 2006 Time: 0900 - 1700 Location: Amsterdam, Netherlands And Date: Friday 19 May 2006 Time: 0900 - 1700 Location: Moscow, Russian Federation The main objective of the "Routing Registry Training Course" is to familiarise the LIRs with the features of the Routing Registry, while introducing the relevant tools and services of the RIPE NCC. The course also offers practical exercises. OVERVIEW OF TOPICS COVERED IN THE COURSE: - Routing Registry as a part of the RIPE Whois Database and the Internet Routing Registry (IRR) - Specifying routing policies using (RPSL) Routing Policy Specification Language and the RtConfig tool - IRRToolSet - Routing Information Service (RIS) - Routing Registry Consistency Check Project Please note that this is an advanced course. It will: - NOT teach the basics of routing - NOT teach the basics of RIPE Database operations - NOT describe how to receive Internet resources from the RIPE NCC - NOT describe how to operate a Local Internet Registry (LIR) The target audience of the course are technical staff of LIRs: e.g. network operators, engineers etc. This course is not intended for administrative or management staff (e.g. Hostmasters) . It is assumed that all attendees will be familiar with Border Gateway Protocol routing and with the RIPE Database (i.e. creating/modifying objects). This course is based on interactive exercises in a local network set-up. Please bring your laptops equipped with the following: - A working Ethernet card, - Three meters of Ethernet cable, - A secure connection client, - A web browser. Please be prepared to share your laptop (or at least allow another attendee to "look over your shoulder") if necessary. The course is free of charge. We provide lunch and printed training materials. We do not cover any of your travel expenses or accommodation. We give all of our training courses in English. You can find more information about the course at: http://www.ripe.net/training/rr/ How to register: --------------------- You can register up to two people from your LIR for each course. (If there are places left nearer the time of the course, you can register more people). To register for this course, you can either use the LIR Portal at: https://lirportal.ripe.net/lirportal/training/course-list.html Or the online registration form on our website: http://www.ripe.net/cgi-bin/trainingform.pl.cgi If you have any questions, send an e-mail to <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC __________ RIPE NCC Online Learning...at your own pace in your own space https://e-learning.ripe.net

1 0

Planned maintenance to the Whois server on 19 December 2005
by Shane Kerr 15 Dec '05

15 Dec '05

Dear Colleagues, We will carry out planned maintenance on the Whois server on Monday 19 December from 18:00 to 20:00 CET. During this time, updates to the whois database will not be possible. Updates sent via e-mail will be queued and then processed normally when service returns. Updates via webupdates or syncupdates will fail, and must be re-tried when service returns to normal. During the maintenance we will run hardware diagnostics on the server. We apologise for inconvenience this may cause. If you have any questions, please e-mail: ripe-dbm(a)ripe.net. Regards, Shane Kerr RIPE NCC

1 0

RIPE 50/51 Draft minutes
by Titley, Nigel 01 Dec '05

01 Dec '05

Gentelfolk, In accordance with my action at the last WG meeting, and as there have been no objections to the draft minutes from either RIPE 50 or RIPE 51, I will get them uploaded to the web server. All the best Nigel ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0

Re: db-wg digest, Vol 1 #380 - 4 msgs
by Alexander Yemelyanov 01 Dec '05

01 Dec '05

Dear db-wg(a)ripe.net, dwrrn> From: Carsten Schiefner <ripe-wgs.cs(a)schiefner.de> dwrrn> Hi Dennis, dwrrn> I noted that there seems to be a general replacement rule in place here: dwrrn> +7 0yy xxxxxxx -> +7 4yy xxxxxxx dwrrn> However, this is not the case for Kaliningrad: dwrrn> +7 011 xxxxxxx -> +7 401 xxxxxxx dwrrn> Is that the usual exception to the rule ;-) or a real typo or something? It is an exception. As it appears in the official notice we received from our phone company, code +7 401 does replace code +7 011. Best Regards, Alexander Yemelyanov, Comintern I.S.P.

1 0

Russian Whois Data Changes
by Denis Walker 30 Nov '05

30 Nov '05

Dear Colleagues We have been informed of changes to Russian telephone area codes. One of our Russian members has asked the RIPE NCC to perform a bulk update on the whois data to reflect these changes. The area codes change on 1 December 2005. If we receive no objections, we plan to make this update two weeks later, on 15 December 2005. If anyone changes the code in their own objects, it will not be affected by this update. List of area codes to be changed. Old format New format Region +7 011 xxxxxxx +7 401 xxxxxxx Kaliningrad +7 071 xxxxxxx +7 471 xxxxxxx Kursk +7 072 xxxxxxx +7 472 xxxxxxx Belgorod +7 073 xxxxxxx +7 473 xxxxxxx Voronezh +7 074 xxxxxxx +7 474 xxxxxxx Lipetsk +7 075 xxxxxxx +7 475 xxxxxxx Tambov +7 081 xxxxxxx +7 481 xxxxxxx Smolensk +7 082 xxxxxxx +7 482 xxxxxxx Tver +7 083 xxxxxxx +7 483 xxxxxxx Bryansk +7 084 xxxxxxx +7 484 xxxxxxx Kaluga +7 085 xxxxxxx +7 485 xxxxxxx Yaroslavl +7 086 xxxxxxx +7 486 xxxxxxx Orel (Oryol, Orlovsk) +7 087 xxxxxxx +7 487 xxxxxxx Tula (Tulsk) +7 091 xxxxxxx +7 491 xxxxxxx Ryazan +7 092 xxxxxxx +7 492 xxxxxxx Vladimir +7 093 xxxxxxx +7 493 xxxxxxx Ivanovo +7 094 xxxxxxx +7 494 xxxxxxx Kostroma +7 095 xxxxxxx +7 495 xxxxxxx Moscow +7 096 xxxxxxx +7 496 xxxxxxx Moscow region Regards Denis Walker Software Engineering Department RIPE NCC

3 3