From president at ukraine.su Tue Jul 3 21:05:37 2007 From: president at ukraine.su (Max Tulyev) Date: Tue, 03 Jul 2007 22:05:37 +0300 Subject: [ncc-services-wg] New service idea Message-ID: <468A9E01.5010407@ukraine.su> 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 at FIDO) From katie at ripe.net Tue Jul 3 15:45:02 2007 From: katie at ripe.net (Katie Petrusha) Date: Tue, 3 Jul 2007 15:45:02 +0200 Subject: [ncc-services-wg] New test server for "IRT by default" behaviour Message-ID: <20070703134502.GA16101@ripe.net> 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 ". The test server will be decomissioned on 1 August 2007. If you have any questions, please send an e-mail to . Regards, -- Katie Petrusha Database Department RIPE NCC From katie at ripe.net Wed Jul 4 14:01:18 2007 From: katie at ripe.net (Katie Petrusha) Date: Wed, 4 Jul 2007 14:01:18 +0200 Subject: [ncc-services-wg] IPv6 access to the RIPE Database server is restored Message-ID: <20070704120118.GB22098@ripe.net> [ 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 . Regards, Katie Petrusha Database Department RIPE NCC From eromijn at ripe.net Wed Jul 4 18:25:38 2007 From: eromijn at ripe.net (Erik Romijn) Date: Wed, 4 Jul 2007 18:25:38 +0200 Subject: [ncc-services-wg] RIS maintenance announcement: 4 July 2007 In-Reply-To: References: Message-ID: <0B25EAC7-F269-48DA-9B8C-781DEEC66C75@ripe.net> [Apologies for duplicates] Dear Colleagues, On Jun 28, 2007, at 2:05 PM, Erik Romijn wrote: > 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). This work has been cancelled due to unforeseen circumstances. We will reschedule it and send a notification once a new date has been planned. Regards, Erik Romijn Information Services RIPE NCC From eromijn at ripe.net Thu Jul 5 16:26:00 2007 From: eromijn at ripe.net (Erik Romijn) Date: Thu, 5 Jul 2007 16:26:00 +0200 Subject: [ncc-services-wg] RIS maintenance announcement: 11 July 2007 Message-ID: <02D6B200-278E-4A13-9382-E5240DFDDAE5@ripe.net> [Apologies for duplicates] Dear Colleagues, On Wednesday, 11 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 . Regards, Erik Romijn Information Services RIPE NCC From denis_on_vacation at yahoo.co.uk Thu Jul 5 16:17:23 2007 From: denis_on_vacation at yahoo.co.uk (Denis W) Date: Thu, 5 Jul 2007 15:17:23 +0100 (BST) Subject: [ncc-services-wg] proposal to maintain all objects Message-ID: <584815.84887.qm@web27205.mail.ukl.yahoo.com> 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ripe.net Mon Jul 9 16:24:34 2007 From: brian at ripe.net (Brian Riddle) Date: Mon, 09 Jul 2007 16:24:34 +0200 Subject: [ncc-services-wg] RIPE NCC Service Outage 09/07/2007 Message-ID: <46924522.9040107@ripe.net> Dear Colleagues, Due to a network switch problem, RIPE NCC experienced a temporary loss of service between 11:41 and 12:15 (UTC) today. This affected our layer2 network and our services were therefore unreachable during this period. We would like to apologise for any inconvenience this may have caused. Regards, Brian Riddle IT Manager RIPE NCC From brian at ripe.net Mon Jul 9 16:24:34 2007 From: brian at ripe.net (Brian Riddle) Date: Mon, 09 Jul 2007 16:24:34 +0200 Subject: [ncc-services-wg] [ncc-announce] RIPE NCC Service Outage 09/07/2007 Message-ID: <46924522.9040107@ripe.net> Dear Colleagues, Due to a network switch problem, RIPE NCC experienced a temporary loss of service between 11:41 and 12:15 (UTC) today. This affected our layer2 network and our services were therefore unreachable during this period. We would like to apologise for any inconvenience this may have caused. Regards, Brian Riddle IT Manager RIPE NCC From Woeber at CC.UniVie.ac.at Tue Jul 10 16:16:17 2007 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Tue, 10 Jul 2007 14:16:17 +0000 Subject: [ncc-services-wg] Re: [db-wg] Proposal - Maintaining person, role and domain objects In-Reply-To: <467A7205.7030504@ripe.net> References: <467A7205.7030504@ripe.net> Message-ID: <469394B1.1060105@CC.UniVie.ac.at> Denis Walker wrote: [....] > > 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. 2 question regarding implementation details... [...] > New startup > Send an update message to dbupdate to create a person object and a > mntner object. These must be the first two objects in an update > message, in any order. 1) This sentence, and the explanation that follows, implies that exactly *two* objects are required here and supported. It should work, even for the cases where admin-c: and tech-c: are (to be) different. Just double-checking. 2) I suppose the use of auto-X instead of an explicit handle would be supported here as well, as in similar chicken and egg situations? > The references to each other must also be in > place. The database software will accommodate this. > > person: Den is > address: RIPE Network Coordination Centre (NCC) > address: Singel 258 > address: 1016 AB Amsterdam > address: The Netherlands > phone: +31 20 535 4444 > nic-hdl: DW-RIPE > mnt-by: aardvark-mnt > notify: denis at ripe.net > changed: denis at ripe.net 20040318 > source: RIPE > > mntner: AARDVARK-MNT > descr: Mntner for denis' objects. > admin-c: DW-RIPE > tech-c: DW-RIPE > upd-to: denis at ripe.net > auth: X509-1 > notify: denis at ripe.net > mnt-by: AARDVARK-MNT > referral-by: RIPE-DBM-MNT > changed: denis at ripe.net 20040225 > source: RIPE > > The update software will recognise that the first person/mntner object > references a non-existent mntner/person object. It will check that this > referenced object is next in the update message. If it is, the "mnt- > by:" attribute will be removed from the person object. The person and > mntner objects will be created, and then the person object will be > modified to add back the "mnt-by:" attribute. > > The objects are now fully configured and can be used. The person object > can be referenced by any other object where a nic-hdl is referenced. It > can also be linked to the white pages. The mntner can be used to > protect any data in the database. > > If the non-existent referenced object is not next in the update message > then an error message will be generated and the update will fail. This > is the current behaviour. Wilfried. From denis at ripe.net Tue Jul 10 16:37:36 2007 From: denis at ripe.net (Denis Walker) Date: Tue, 10 Jul 2007 16:37:36 +0200 Subject: [ncc-services-wg] Re: [db-wg] Proposal - Maintaining person, role and domain objects In-Reply-To: <469394B1.1060105@CC.UniVie.ac.at> References: <467A7205.7030504@ripe.net> <469394B1.1060105@CC.UniVie.ac.at> Message-ID: <469399B0.3060509@ripe.net> Wilfried Woeber, UniVie/ACOnet wrote: > Denis Walker wrote: > [....] > >> 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. >> > > 2 question regarding implementation details... > > [...] > >> New startup >> Send an update message to dbupdate to create a person object and a >> mntner object. These must be the first two objects in an update >> message, in any order. >> > > 1) > This sentence, and the explanation that follows, implies that exactly > *two* objects are required here and supported. It should work, even > for the cases where admin-c: and tech-c: are (to be) different. Just > double-checking. > Not quite right. My view is that these two mutually referencing objects must be the FIRST two in an update message. There can be other objects in the message also, but unrelated to this 'startup procedure'. To avoid over complicating the code we want to keep it simple and only have 2 objects with the mutual reference for the new creation. If you want a different admin-c and tech-c in the new mntner, none of which currently exist, first create the new mntner/person pair using the one person as both admin-c and tech-c. Then create the second person and modify the mntner. > 2) > I suppose the use of auto-X instead of an explicit handle would be > supported here as well, as in similar chicken and egg situations? > Yes....I should have used AUTO- in the examples to make that clearer. regards Denis Walker RIPE NCC > >> The references to each other must also be in >> place. The database software will accommodate this. >> >> person: Den is >> address: RIPE Network Coordination Centre (NCC) >> address: Singel 258 >> address: 1016 AB Amsterdam >> address: The Netherlands >> phone: +31 20 535 4444 >> nic-hdl: DW-RIPE >> mnt-by: aardvark-mnt >> notify: denis at ripe.net >> changed: denis at ripe.net 20040318 >> source: RIPE >> >> mntner: AARDVARK-MNT >> descr: Mntner for denis' objects. >> admin-c: DW-RIPE >> tech-c: DW-RIPE >> upd-to: denis at ripe.net >> auth: X509-1 >> notify: denis at ripe.net >> mnt-by: AARDVARK-MNT >> referral-by: RIPE-DBM-MNT >> changed: denis at ripe.net 20040225 >> source: RIPE >> >> The update software will recognise that the first person/mntner object >> references a non-existent mntner/person object. It will check that this >> referenced object is next in the update message. If it is, the "mnt- >> by:" attribute will be removed from the person object. The person and >> mntner objects will be created, and then the person object will be >> modified to add back the "mnt-by:" attribute. >> >> The objects are now fully configured and can be used. The person object >> can be referenced by any other object where a nic-hdl is referenced. It >> can also be linked to the white pages. The mntner can be used to >> protect any data in the database. >> >> If the non-existent referenced object is not next in the update message >> then an error message will be generated and the update will fail. This >> is the current behaviour. >> > > Wilfried. > From Woeber at CC.UniVie.ac.at Wed Jul 11 09:20:28 2007 From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet) Date: Wed, 11 Jul 2007 07:20:28 +0000 Subject: [ncc-services-wg] Re: [db-wg] Proposal - Maintaining person, role and domain objects In-Reply-To: <469399B0.3060509@ripe.net> References: <467A7205.7030504@ripe.net> <469394B1.1060105@CC.UniVie.ac.at> <469399B0.3060509@ripe.net> Message-ID: <469484BC.6040701@CC.UniVie.ac.at> Denis Walker wrote: [...] >>1) >>This sentence, and the explanation that follows, implies that exactly >>*two* objects are required here and supported. It should work, even >>for the cases where admin-c: and tech-c: are (to be) different. Just >>double-checking. >> > > > Not quite right. My view is that these two mutually referencing objects > must be the FIRST two in an update message. There can be other objects > in the message also, but unrelated to this 'startup procedure'. > > To avoid over complicating the code we want to keep it simple and only > have 2 objects with the mutual reference for the new creation. If you > want a different admin-c and tech-c in the new mntner, none of which > currently exist, first create the new mntner/person pair using the one > person as both admin-c and tech-c. Then create the second person and > modify the mntner. Yep, that's how I read it, too. And I agree. But it should be made explicit in any documentation that goes with this, that for this case an additional step is necessary. No big deal... Wilfried. From brian at ripe.net Tue Jul 17 16:11:05 2007 From: brian at ripe.net (Brian Riddle) Date: Tue, 17 Jul 2007 16:11:05 +0200 Subject: [ncc-services-wg] RIPE NCC Service Outage 17/07/2007 In-Reply-To: <46924522.9040107@ripe.net> References: <46924522.9040107@ripe.net> Message-ID: <469CCDF9.3040302@ripe.net> [Apologies for duplicate e-mails.] Dear Colleagues, Due to a fibre cut, some of our users may have experienced problems accessing RIPE NCC services between 12:20 and 12:49 (UTC) today. The problem has now been fixed and we would like to apologise for any inconvenience this may have caused. Regards, Brian Riddle IT Manager RIPE NCC From brian at ripe.net Tue Jul 17 16:11:05 2007 From: brian at ripe.net (Brian Riddle) Date: Tue, 17 Jul 2007 16:11:05 +0200 Subject: [ncc-services-wg] [ncc-announce] RIPE NCC Service Outage 17/07/2007 In-Reply-To: <46924522.9040107@ripe.net> References: <46924522.9040107@ripe.net> Message-ID: <469CCDF9.3040302@ripe.net> [Apologies for duplicate e-mails.] Dear Colleagues, Due to a fibre cut, some of our users may have experienced problems accessing RIPE NCC services between 12:20 and 12:49 (UTC) today. The problem has now been fixed and we would like to apologise for any inconvenience this may have caused. Regards, Brian Riddle IT Manager RIPE NCC From trudy at ripe.net Wed Jul 25 11:49:13 2007 From: trudy at ripe.net (Trudy Prins) Date: Wed, 25 Jul 2007 11:49:13 +0200 Subject: [ncc-services-wg] LIR Portal maintenance announcement Message-ID: <46A71C99.1000208@ripe.net> Dear Colleagues, The RIPE NCC will perform a software upgrade on the LIR Portal between 17:00 and 20:00 (UTC), Monday, 30 July 2007. The LIR Portal and related services, such as meeting and training registration, will be unavailable during this period. We apologise for any inconvenience this may cause. If you have any questions, please send an e-mail to . Regards, Trudy Prins Business Applications Manager, RIPE NCC From trudy at ripe.net Wed Jul 25 11:49:13 2007 From: trudy at ripe.net (Trudy Prins) Date: Wed, 25 Jul 2007 11:49:13 +0200 Subject: [ncc-services-wg] [ncc-announce] LIR Portal maintenance announcement Message-ID: <46A71C99.1000208@ripe.net> Dear Colleagues, The RIPE NCC will perform a software upgrade on the LIR Portal between 17:00 and 20:00 (UTC), Monday, 30 July 2007. The LIR Portal and related services, such as meeting and training registration, will be unavailable during this period. We apologise for any inconvenience this may cause. If you have any questions, please send an e-mail to . Regards, Trudy Prins Business Applications Manager, RIPE NCC From alexlh at ripe.net Mon Jul 30 14:49:40 2007 From: alexlh at ripe.net (Alex Le Heux) Date: Mon, 30 Jul 2007 14:49:40 +0200 Subject: [ncc-services-wg] 2006-02 Implementation: IPv6 Address Allocation and Assignment Policy Message-ID: <1F7A7961-30B5-4AF8-ACC3-618B7B29D745@ripe.net> [Apologies for duplicate emails] Dear Colleagues, We are pleased to announce that the policy proposed in 2006-02 "IPv6 Address Allocation and Assignment Policy" has been implemented. The RIPE NCC is now ready to accept requests for IPv6 address space under the new policy. The archived proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2006-02.html The updated "IPv6 Address Allocation and Assignment Policy" is available at: http://www.ripe.net/ripe/docs/ripe-412.html The following RIPE documents have also been updated to reflect this policy implementation: Supporting Notes for the IPv6 First Allocation Request Form http://ripe.net/ripe/docs/ripe-413.html IPv6 First Allocation Request Form http://ripe.net/ripe/docs/ripe-414.html Best regards, Alex Le Heux RIPE NCC Policy Implementation Co-ordinator From alexlh at ripe.net Mon Jul 30 14:49:40 2007 From: alexlh at ripe.net (Alex Le Heux) Date: Mon, 30 Jul 2007 14:49:40 +0200 Subject: [ncc-services-wg] [ncc-announce] 2006-02 Implementation: IPv6 Address Allocation and Assignment Policy Message-ID: <1F7A7961-30B5-4AF8-ACC3-618B7B29D745@ripe.net> [Apologies for duplicate emails] Dear Colleagues, We are pleased to announce that the policy proposed in 2006-02 "IPv6 Address Allocation and Assignment Policy" has been implemented. The RIPE NCC is now ready to accept requests for IPv6 address space under the new policy. The archived proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2006-02.html The updated "IPv6 Address Allocation and Assignment Policy" is available at: http://www.ripe.net/ripe/docs/ripe-412.html The following RIPE documents have also been updated to reflect this policy implementation: Supporting Notes for the IPv6 First Allocation Request Form http://ripe.net/ripe/docs/ripe-413.html IPv6 First Allocation Request Form http://ripe.net/ripe/docs/ripe-414.html Best regards, Alex Le Heux RIPE NCC Policy Implementation Co-ordinator