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

proposal to maintain all objects
by Denis W 05 Jul '07

05 Jul '07

Hi Wilfried There have been no comments against this proposal and a few in favour of the move. Can the RIPE NCC regard this as a consensus now to implement Stage 1 of the proposal? We will seek further consensus later for the other stages. regards Denis Walker RIPE NCC --------------------------------- New Yahoo! Mail is the ultimate force in competitive emailing. Find out more at the Yahoo! Mail Championships. Plus: play games and win prizes.

1 0

RIS maintenance announcement: 4 July 2007
by Erik Romijn 04 Jul '07

04 Jul '07

[Apologies for duplicates] Dear Colleagues, On Wednesday, 4 July 2007, we will conduct planned maintenance on the Routing Information Service (RIS). This will involve a memory test on our collector connected to LINX (rrc01). Between 17:00 and 19:00 (UTC), we will reboot the collector to run an offline memory test. During this test, the collector will not collect data and the looking glass for this collector will not be available. We thank you for your patience and apologise for any inconvenience this may cause. If you have any questions about this work, please send an e-mail to <ris(a)ripe.net>. Regards, Erik Romijn Information Services RIPE NCC

1 1

IPv6 access to the RIPE Database server is restored
by Katie Petrusha 04 Jul '07

04 Jul '07

[ Apologies for duplicate mails ] Dear Colleagues, IPv6 access to the RIPE Database server has now been restored. The server was unable to respond to queries over IPv6 from 11:12 (UTC), 29 June 2007. Details of this incident are available at: http://www.ripe.net/ripe/maillists/archives/db-wg/2007/msg00118.html We apologise for any inconvenience. If you have any questions or concerns about this, please send an e-mail to <ripe-dbm(a)ripe.net>. Regards, Katie Petrusha Database Department RIPE NCC

1 0

New service idea
by Max Tulyev 03 Jul '07

03 Jul '07

Hi All! To establish a mail list where RIPE NCC Members can offer or ask for connectivity, transit or peering? It is more commerce than technical question, but I think it will be very useful for improving connectivity and communications between members. For example, I'm looking for Turkey and Iran transit to Turkmenistan and Uzbekistan now :) -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

1 0

New test server for "IRT by default" behaviour
by Katie Petrusha 03 Jul '07

03 Jul '07

Dear Colleagues, On 1 August 2007, the RIPE NCC will update the RIPE Database server so that IP queries return IRT objects by default. Details of this change are available here: http://www.ripe.net/ripe/maillists/archives/db-wg/2007/msg00113.html To help ensure a smooth transition, we have set up a test server, which can be accessed at: test-whois-default-irt.ripe.net port 43043 This server runs the updated RIPE Database software, and contains data identical to the RIPE Database. You may use this server to test your tools and queries against the new default behaviour. For command line parameters, use "-h test-whois-default-irt.ripe.net -p 43043 <your_query>". The test server will be decomissioned on 1 August 2007. If you have any questions, please send an e-mail to <ripe-dbm(a)ripe.net>. Regards, -- Katie Petrusha Database Department RIPE NCC

1 0

RIPE DB not accessible over IPv6
by Agoston Horvath 29 Jun '07

29 Jun '07

Dear Colleagues, >From 11:12 on 29 June 2007, the RIPE Database is not able to respond to queries over IPv6. All other services (updates, queries over IPv4) are unaffected. This problem is due to a firewall-related issue in our Juniper routers. We apologise for any inconvenience. If you have any questions or concerns about this, please contact us at: <ripe-dbm(a)ripe.net> Regards, Agoston Horvath Database Group RIPE NCC

1 0

Re: db-wg digest, Vol 1 #520 - 1 msg
by Denis W 26 Jun '07

26 Jun '07

Hi Joao I agree. So lets focus first on a consensus for stage 1. Then we can start work on that while we continue discussions on the other stages and the impacts they will have on work flow of LIRs. regards Denis RIPE NCC Cc: Database WG , ncc-services-wg From: Joao Damas Subject: Re: [db-wg] Proposal - Maintaining person, role and domain objects Date: Mon, 25 Jun 2007 11:00:20 +0200 To: Denis Walker Stage 1 makes a lot of sense to me as it has little consequences to older data while it makes sure new information going into the DB has a better chance of being kept as originally posted by the object creator. The other stages do need a bit more discussion as they may in fact affect a lot of legacy data and have the potential to add a burden to LIR operations. I am in favour of those extra steps, just think that there is a need to repeat the warnings and announcements before and insist on people making an impact analysis on their operations. Joao Damas On 21 Jun 2007, at 14:41, Denis Walker wrote: > [Apologies for duplicate mails] > > Dear Colleagues, > > As a result of discussions during the Database Working Group > session at > RIPE 54, the RIPE NCC has nine proposals and implementation plans to > present to the community. Although most of them are now in the final > stages of preparation, we will send them out one at a time over the > next > few weeks for consideration by the community. > > The first one concerns maintaining all objects in the RIPE > Database, which > followed from a recommendation from the Data Protection Task Force > (DP TF) > (see below). We have already had some preliminary discussions about > this > with the DP TF. They provided the RIPE NCC with some very useful > feedback, > which is incorporated in this proposal. > > Regards > Denis Walker > RIPE NCC > > > > Maintaining person, role and domain objects > ------------------------------------------- > > > Implementation > As with the CRYPT-PW deprecation this will have a staged rollout. > > Stage 1 > > * No new person, role or domain objects can be created without a > "mnt-by:" attribute. > * Any un-maintained person, role or domain object cannot be modified > without adding a "mnt-by:" attribute. > * Any update where objects reference an un-maintained person object, > either directly or through a mntner with such references, will > generate a warning message in the acknowledgement. > > In this stage the acknowledgement message may include these warnings: > > ***WARNING: Un-maintained person object referenced [DW-RIPE] > ***WARNING: Un-maintained person object referenced [DW-RIPE] in > mntner [AARDVARK-MNT] > > Stage 2 > > * Any update where objects reference an un-maintained person object, > either directly or through a mntner with such references, will > generate a warning message in the acknowledgement. > * Any NEW reference to an un-maintained person object or to a mntner > which has such references will generate an error message in the > acknowledgement and the update will fail. > > In this stage the acknowledgement message may include these warnings > and errors: > > ***WARNING: Un-maintained person object referenced [DW-RIPE] > ***WARNING: Un-maintained person object referenced [DW-RIPE] in > mntner [AARDVARK-MNT] > ***ERROR: New reference to un-maintained person object [DW-RIPE] > ***ERROR: New reference to un-maintained person object [DW-RIPE] in > mntner [AARDVARK-MNT] > > Stage 3 > > * Any update where objects reference an un-maintained person object, > either directly or through a mntner with such references, will > generate an error message in the acknowledgement and the update > will fail. > > In this stage the acknowledgement message may include these errors: > > ***ERROR: Un-maintained person object referenced [DW-RIPE] > ***ERROR: Un-maintained person object referenced [DW-RIPE] in mntner > [AARDVARK-MNT] > > > Statistics > ---------- > While not a very statistically valid survey, we looked at a few days > just after the RIPE meeting to see how many new person objects were > created with and without mntner objects. We also queried the new > objects some time after creation to allow for a "mnt-by:" to be added > later. We also noted how many unique person objects were referenced in > any objects in update messages with and without mntner objects. AUTO- > references were ignored in both creations and updates, and multiple > instances of the same person object being referenced many times were > counted as one. > > -------------------------------------------------------- > | Date |Created |Created |Referenced |Referenced | > | |with |without |with |without | > |--------------------------------------------------------| > | 20070515 | 156 | 89 | 925 | 726 | > | 20070516 | 111 | 67 | 1022 | 486 | > | 20070517 | 85 | 48 | 476 | 185 | > | 20070518 | 82 | 18 | 679 | 445 | > -------------------------------------------------------- > End of db-wg Digest --------------------------------- New Yahoo! Mail is the ultimate force in competitive emailing. Find out more at the Yahoo! Mail Championships. Plus: play games and win prizes.

1 0

RIPE NCC Network Maintenance Wednesday 20 June 17:00 to 19:00 UTC/GMT
by Mark Guz 18 Jun '07

18 Jun '07

[apologies for duplicates] Dear Colleagues, On Wednesday 20/06/2007, between 17:00 and 19:00 (UTC), the RIPE NCC will carry out planned maintenance work on our network infrastructure. This may result in brief interruptions to RIPE NCC services during the posted maintenance window. We apologise for any inconvenience that this may cause. This work is due to planned resilience testing of our network. If you have any questions about this, please send an e-mail to: ops(a)ripe.net <mailto:ops@ripe.net>. Regards Mark Guz Senior Engineer RIPE NCC

1 0

LIR Portal ticketing system outage on June 12
by Razvan Oprea 07 Jun '07

07 Jun '07

Dear Colleagues, The RIPE NCC will perform planned maintenance work on Tuesday, June 12, 2007 between 17:00 and 19:00 (UTC). Please note that this is a different maintenance task than the one successfully completed on June 6. During this period the RIPE NCC ticketing system will not be working, meaning that any changes in the status of open tickets will not be reflected in the LIR Portal. Any pending mails will be processed after the maintenance work has been completed. We apologise for any inconvenience that this may cause. If you have any questions about this, please send an e-mail to <ops(a)ripe.net>. Regards, Razvan Oprea Senior Systems Engineer RIPE NCC

1 0

New RIPE Document available: RIPE-411
by RIPE NCC Document Announcement Service 07 Jun '07

07 Jun '07

A new RIPE Document is available from the RIPE Document store. Ref: ripe-411 Title: IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region Author: RIPE NCC Date: June 2007 Format: PDF=82,541 Obsoletes: ripe-405 This document describes the RIPE community¢s current IPv4 address allocation and assignment policies. They were developed through a bottom-up, consensus driven, open policy development process in the RIPE Address Policy Working Group (AP WG). The RIPE Network Coordination Centre (RIPE NCC) facilitates and supports this process. These policies apply to the RIPE NCC and the Local Internet Registries (LIRs) within the RIPE NCC service region. You can find this document at: http://www.ripe.net/docs/ripe-411.html Regards RIPE NCC Webmaster

1 0