- ncc-services-wg - mailman.ripe.net

Upgrade of the reverse DNS provisioning system at 8 September 2008, between 09:00 and 12:00 (UTC)
by Wolfgang Nagele 03 Sep '08

03 Sep '08

[Apologies for duplicate emails] Dear Colleagues, On 8 September 2008, between 09:00 and 12:00 (UTC), the RIPE NCC will upgrade the reverse DNS provisioning system. This change will enable the server ns.ripe.net to perform zone transfers over IPv6. If your reverse zone has a master server with an IPv6 address, this will be used in preference to the IPv4 address after the change. We apologise for any inconvenience this change may cause. If you have any questions or concerns about this, please email <dns-help(a)ripe.net>. Regards, -- Wolfgang Nagele DNS System Engineer RIPE NCC Singel 258 1016 AB Amsterdam Tel: +31 20 535 4444 Fax: +31 20 535 4445

1 0

Planned maintenance on ns.ripe.net, 2 Sept.
by Sjoerd Oostdijck 01 Sep '08

01 Sep '08

[Apologies for duplicate e-mails.] Dear Colleagues, On Tuesday, 2 September 2008, the RIPE NCC will perform maintenance on the ns.ripe.net server between 10:00 and 12:00 (UTC). During this period, it may not be able to answer DNS queries. The aim of this maintenance is to introduce a second server to improve performance of the system. If ns.ripe.net provides secondary DNS name service for your zone, no changes on your side will be required. During the maintenance, other servers in your NS set will take over and no downtime will be visible to the Internet. We apologise for any inconvenience this maintenance may cause. If you have any questions or concerns about this, please email dns-help(a)ripe.net Regards, Sjoerd Oostdijck DNS Services The RIPE NCC

1 0

from Kazakhstan
by Асель Нурушева 26 Aug '08

26 Aug '08

Hello, We have LIR-status (Asia, Kazakhstan). We have address space IPv/19 (see Application 1, described below), DNS and AS-number (ASN-15549 ticket NCC#200073996 for BankNet Data Network). Unfortunately, we did not use address space (Assigned and Allocation) and AS (autonomous system) for a long time. Now we decide to use own address space and to announce (route) it in the Internet. We have all necessary equipment for it (routers, switches, firewalls, servers, workstations). We service all state structures of Kazakhstan Republic, as we need to announce the networks in all cities of country. Please refresh the information about AS-number if it's really. How can we use address space? What will you advise for us? Our specialists (staff) need to learn all LIR-training courses (Local Internet Registry Training Course, DNS for LIRs Training Course, Routing Registry Training Course). Now we are registered on courses in Great Britain on September, 10th, but it is very far and expensive to one-day course. Could we have learning courses in our country (Astana, Kazakhstan). It's very important and urgent for our company. Thanks for information Yours faithfully, Cherepanov Dmitriy the Management director JSC "National Information Technology" www.nitec.kz T: +7 7172 741152 F: +7 7172 741064 E: <domain(a)nitec.kz> If you need more information feel free to contact me. Application 1. Assignment Window History Date Prefix Size Ticket No. 19970724 - 0 19990622 /27 32 NCC#1999063055 Allocations Made by RIPE NCC to kz.banknet Date IP / Prefix Size Status Ticket No. 19970806 195.12.96/19 [Edit Object] 8192 PA Assignments Approved by RIPE NCC Date Size Netname Ticket No. 19970806 /24 (256) IFTC NCC#1997080422 19971209 /24 (256) KISC NCC#1997123015 19971217 /24 (256) GATU NCC#1997112703 19990122 /27 (32) KSISTI NCC#1999016891 19990415 /27 (32) IFTCPETR NCC#1999040390 19990420 /27 (32) IFTCKOST NCC#1999040668 19990622 /27 (32) IFTCPAVL NCC#1999063055 19990705 /28 (16) IFTCTALD NCC#1999063704 19990712 /27 (32) IFTCUSTK NCC#1999073974 19990830 /27 (32) AERUSTK NCC#1999085469 19990913 /26 (64) KIPAVL NCC#1999096599 19990923 /27 (32) IFTCAKMO NCC#1999097029 20000726 /27 (32) IFTCAKTA NCC#2000073813 20000808 /27 (32) IFTCAKTOBE NCC#2000074333 20000829 /27 (32) IFTCATYR NCC#2000085434 20000928 /27 (32) IFTCKARA NCC#2000097312 20001110 /27 (32) IFTCKORDA NCC#2000110878 20001116 /27 (32) IFTCSEMEY NCC#2000111563 20021023 /24 (256) IFTCAKMO NCC#2002101657

2 1

RIPE Database legal documents
by Denis Walker 28 Jul '08

28 Jul '08

Apologies for duplicates] Dear Colleagues, The RIPE Data Protection Task Force (DP TF), working with the RIPE NCC and the company lawyers, has finalised a set of legal documents for the RIPE Database. These documents are: - RIPE Database Terms and Conditions - RIPE Database Acceptable Use Policy - Procedure for the Removal of Personal Contact Details from the RIPE Database They can be seen on the RIPE DP TF web page at this address: http://www.ripe.net/ripe/tf/dp/index.html The documents have been subjected to a final review by the DP TF but they are not yet legally effective. They are now available for review and comments by the wider community. Please let us know if you have any considerations or issues. Please bear in mind that with any documents such as these, the wording can always be changed. However, we would prefer not to make any subjective changes at this stage but only amend anything that is inaccurate. The documents will become legally effective from 1 September 2008 and they will then be available on a new Legal Documents page on the RIPE NCC website. Regards, Denis Walker (on behalf of the RIPE DP TF)

2 1

Locally caching riswhois results
by Laurent Zimmerli 22 Jul '08

22 Jul '08

Hi list I'm making use of the riswhois service and would like to cache queries locally. However, I am not sure whether I can do it the way I want to. My idea is to store the ASN an the corresponding route of each query I execute. Before performing another query I would then check whether I already stored the ASN of a route which contains the IP for which I want to find the AS. Can I do that? Or is then the following case possible: I store an AS an its route -- say ASx, 123.0.0.0/8 -- whose IP range includes another one -- say ASy, 123.100.0.0/16. When I store ASx first and then query an IP of ASy, I will assign ASx to this IP instead of ASy. Is such a case possible? Or is there even another problem with my caching approach? Thanks for your time! Best, Laurent

2 1

IPv6 enabled for email to the RIPE NCC
by Henk Uijterwaal 18 Jul '08

18 Jul '08

Dear Colleagues, On Wednesday, 16 July, the RIPE NCC's new mail servers were enabled. As of this date, it is possible to send mail to the RIPE NCC with IPv6 as a transport medium. This setup has been extensively tested but if you see any problems, please send an e-mail to <ops(a)ripe.net> or phone +31 20 535 4444. Kind regards, The RIPE NCC -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Is one of the choices leaving the office open? Alan Greenspan on the next elections

1 0

Announcing new RIS de-bogon prefixes
by Ruben van Staveren 20 Jun '08

20 Jun '08

[Apologies for duplicate e-mails] Dear Colleagues, As part of our effort to de-bogonise new address blocks, we are now announcing the following prefixes on RRC03: 112.0.0.0/24 113.0.0.0/24 112.50.0.0/21 112.50.0.0/21 112.255.0.0/16 113.255.0.0/16 More information about the Routing Information Service (RIS) De- Bogonising New Address Blocks Project can be found at: http://www.ris.ripe.net/debogon/index.shtml Kind regards, Ruben van Staveren RIPE NCC, Engineer

2 1

Notification message change
by Denis Walker 18 Jun '08

18 Jun '08

[Apologies for duplicates] Dear Colleagues, With most updates to the RIPE Database, notification messages are sent out. Many of these notifications are hitting users' ticketing systems or arriving in mailboxes with auto-responders. The "Reply-to:" address in these notifications was <ripe-dbm(a)ripe.net>. Our help desk ticketing system was receiving hundreds of e-mails a month from these auto-responders. This was causing a serious operational problem for our Customer Services Department. To solve this problem, we have changed the e-mail header in the notification messages we send out. They now have the "From:" and "Reply-to:" addresses set to <unread(a)ripe.net>. As the name suggests, any replies to this address are not read by anyone and they are just dropped from our mail system. We have also made a small change to the introductory text to make it clear that these e-mails are auto-generated. We also clearly show users the e-mail reply address to use if they have an issue with the notification. This change was implemented today. It should not affect any users unless they parse the mail headers or the introductory text in the notification. Examples of the old and new notification messages are shown below. Regards, Denis Walker Business Analyst RIPE NCC Database Group Old notification message ____________________________________________________ To: user(a)somewhere.com From: RIPE Database Notifications <bitbucket(a)ripe.net> Subject: Notification of RIPE Database changes Reply-To: ripe-dbm(a)ripe.net Precedence: bulk Auto-Submitted: auto-generated Dear Colleague, This is to notify you that some object(s) in RIPE database which you either maintain or are listed as to-be-notified have been added, deleted or changed. The update causing these changes had the following mail headers: > From: user(a)somewhereelse.com > Subject: > Date: Tue, 17 Jun 2008 00:00:18 +0200 (CEST) > Reply-To: user(a)somewhereelse.com > MsgId: <2008061622> For assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> New notification message ____________________________________________________ To: user(a)somewhere.com From: RIPE Database Notifications <unread(a)ripe.net> Subject: Notification of RIPE Database changes Reply-To: unread(a)ripe.net Precedence: bulk Auto-Submitted: auto-generated Dear Colleague, This is to notify you that some object(s) in RIPE database which you either maintain or are listed as to-be-notified have been added, deleted or changed. This message is auto-generated. Please DO NOT reply to this message. If you do not understand why we sent you this message, or for assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> The update causing these changes had the following mail headers: > From: user(a)somewhereelse.com > Subject: > Date: Tue, 17 Jun 2008 00:00:18 +0200 (CEST) > Reply-To: user(a)somewhereelse.com > MsgId: <2008061622>

1 0

Emergency Maintenance Announcement
by Gerard Leurs 16 Jun '08

16 Jun '08

[Apologies for duplicates] Dear Colleagues, Today, Monday, 16 June, the RIPE NCC will carry out emergency maintenance work on some of our servers. As a result, the following services will be temporarily unavailable at times over the course of the day: - www.ripe.net - lirportal.ripe.net Delayed response times can also be expected for RIPE NCC Registration Services and Customer Services. We apologise for any inconvenience that this may cause. If you have any questions, please send an e-mail to <ops(a)ripe.net>. Regards, Gerard Leurs Operations Coordinator, RIPE NCC

1 0

Announcement on prefix size change for k.root-servers.net (AS25152)
by Wolfgang Nagele 12 Jun '08

12 Jun '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicates] Dear Colleagues, The RIPE NCC, as operator of k.root-servers.net, will announce the less-specific prefix 193.0.14.0/23 within the next few days. This is due to a change in our traffic engineering policies. Affected locations: *) AMS-IX (NL) *) LINX (UK) *) JP-NAP, DIX-IE (JP) *) NAP (US/FL) *) NIXI (IN) We advise you to check whether you are peering with AS25152 and, if so, to ensure that you are allowing the prefix mentioned above. These are the recommended filter settings for our peerings: Cisco: - ---cut--- ip prefix-list as25152-policy seq 10 permit 193.0.14.0/23 le 24 ip prefix-list as25152-policy seq 20 deny 0.0.0.0/0 le 32 - ---cut--- Juniper: - ---cut--- policy-statement as25152-policy { term accept { from { route-filter 193.0.14.0/23 prefix-length-range /23-/24 accept; } } term reject { then reject; } } - ---cut--- If you have any questions, please contact us at <kroot-ops(a)ripe.net>. Regards, - -- Wolfgang Nagele DNS System Engineer RIPE NCC Singel 258 1016 AB Amsterdam Tel: +31 20 535 4444 Fax: +31 20 535 4445 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIUPLEjO7G63Byy8cRAkUZAJ9/g2kKieUn54sLofkChlPug8+8ZQCeP1P8 HWnbQjvj/g17fOE5MAIXW+c= =Y/z1 -----END PGP SIGNATURE-----

1 0