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

re: Proposal for returning IRT objects
by Denis Walker 17 Aug '06

17 Aug '06

[Apologies for duplicate mails] Dear Colleagues, The RIPE NCC has re-implemented the way IRT objects are returned in RIPE Database query results. The proposal can be found at: http://www.ripe.net/ripe/maillists/archives/db-wg/2006/msg00087.html The first stage of this implementation as described in the proposal is now complete. The main objectives were to: - Increase the availability of the IRT information to users - Promote the use of the IRT object - Make it easier for third party tool writers to find the correct contacts New Behaviour ------------------------ The behaviour of the "-c" flag and the "-rc" flag is as follows: A standard query for address space including the "-c" query flag returns the queried INETNUM and related objects. This also includes an IRT object referenced by the queried INETNUM object or the closest, less specific INETNUM object, if one exists. It will also still include any ROUTE objects. By using the "-rc" flags, the related personal objects are filtered out. The IRT object will still be returned together with any ROUTE objects. An additional consequence of this change is the way the "-b" flag works. The "-b" flag will always return the primary key of any address space object queried. It also returns the "abuse-mailbox:" attributes from the address space object and any related IRT objects. The RIPE Database Query webpage has also been updated: http://www.ripe.net/fcgi-bin/whois For all address space queries made via this webpage, the "-c" flag will be added, making it the default. This only occurs if no other address space query flags (lLmMxbc) are present. A link has also been added to enable users to switch between the test and production databases. This makes it easier to query the RIPE Test Database. Regards Denis Walker Software Engineering Department RIPE NCC

1 0

New Documents available: RIPE-384, RIPE-385
by RIPE NCC Document Announcement Service 16 Aug '06

16 Aug '06

New RIPE Document Announcement -------------------------------------- Two new documents are available from the RIPE document store. Ref: ripe-384 Title: ENUM Request Form Author: RIPE NCC Date: 15 August 2006 Format: PDF=98364 TXT=1255 Obsoletes: ripe-327 Ref: ripe-385 Title: Supporting Notes for the ENUM Request Form Author: RIPE NCC Date: 15 August 2006 Format: PDF=87011 TXT=5672 Obsoletes: ripe-327 Short content description ------------------------- The "ENUM Request Form" and "Supporting Notes for the ENUM Request Form" documents replace ripe-327: "Draft Request Form for Delegation of a Zone Under e164.arpa". The new documents feature: * improved language and readability, * better examples and a step-by-step guide * the use of the "organisation" object for this type of request Accessing the RIPE document store --------------------------------- You can access the RIPE documents in HTML format via our website at the following URLs: http://www.ripe.net/ripe/docs/enum-request.html http://www.ripe.net/ripe/docs/enumrequest-support.html The RIPE Document Store is also available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-384.pdf PDF version ftp://ftp.ripe.net/ripe/docs/ripe-384.txt plain text version ftp://ftp.ripe.net/ripe/docs/ripe-385.pdf PDF version ftp://ftp.ripe.net/ripe/docs/ripe-385.txt plain text version

1 0

object-type: poem?
by Tiberiu Ungureanu 16 Aug '06

16 Aug '06

while looking for something else, i tripped and fell over this: $ whois -t poem poem: [mandatory] [single] [primary/look-up key] descr: [optional] [multiple] [ ] form: [mandatory] [single] [inverse key] text: [mandatory] [multiple] [ ] admin-c: [mandatory] [multiple] [inverse key] author: [mandatory] [multiple] [inverse key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] should i take it that RIPE database allow the creative ones to store their own poems (as in... poetry?). can anyone point me to the document explaining this object ? thanks. -- Tiberiu "the difference between a BOLD and a STUPID action is just a matter of result" Ungureanu

2 1

DNSMON.RIPE.NET Maintenance Today
by Ruben van Staveren 08 Aug '06

08 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Colleagues, [Apologies for duplicate e-mails] We are currently upgrading the memory and disk space on dnsmon.ripe.net. During this maintenance work the following service will not be available: http://dnsmon.ripe.net/ Maintenance is scheduled to finish at 16:00 (UTC). No data will be lost and we will clear any backlog when the upgrade is complete. It might take some time for the service to return to normal. Measurements on the DNSMON probes are not affected by the downtime. We apologise for any inconvenience this may cause. If you have any questions or concerns about this, please send an e- mail to: ops(a)ripe.net Regards, Ruben van Staveren RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (Darwin) iD8DBQFE2GkWkQhJ4tr8JxsRAiBfAKDlHWtbVCmaQJ4S0kphLI+YTnfDtACeL+0Y Ah8Te7gWYjsSvOtD/E4PczU= =wrV2 -----END PGP SIGNATURE-----

1 1

RIPE Database maintenance
by Denis Walker 03 Aug '06

03 Aug '06

Dear Colleagues, We will carry out maintenance work on the RIPE Database update server, cello.ripe.net, on Friday, 4 August 2006 between 09:00-10:00 (UTC). During this period, you may experience outages when trying to use the following services: - RIPE Database updates (including the web interface and synchronous interface) - Queries to our mirrored databases (using -a query flag) Any updates sent to the mail interface will be queued and processed later. We apologise for any inconvenience. If you have any questions, please contact: ripe-dbm(a)ripe.net. Regards, Denis Walker Software Engineering Department RIPE NCC

1 0

Scheduled maintenance of mailing list server (lists.ripe.net)
by Marcin Deranek 05 Jul '06

05 Jul '06

[Apologies for duplicate e-mails.] Dear Colleagues, On 10 July 2006 we will carry out maintenance work on lists.ripe.net (Mailing lists server) between 10:00 and 10:30 UTC. During this period you might not be able to access Mailman's web interface (http://www.ripe.net/mailman/) and messages sent to all mailing lists might be delayed. We apologise for any inconvenience this may cause. Kind regards, Marcin Deranek Systems Engineer RIPE NCC

1 0

Improved wording for request forms
by Laura Cobley 04 Jul '06

04 Jul '06

[Apologies for duplicate e-mails] Dear Colleagues, We are pleased to announce the publication of two updated RIPE Documents: ripe-381 Provider Aggregatable (PA) Assignment Request Form http://www.ripe.net/docs/iprequestform.html ripe-382 Supporting Notes for the Provider Aggregatable (PA) Assignment Request Form http://www.ripe.net/docs/iprequestsupport.html We have improved the wording of these documents to make the request forms easier to use. You can still complete the request forms using the previous layout as the content of the forms has not changed. These changes are the final part of a project to improve the wording of all request forms and supporting notes. Best Regards, Laura Cobley Registration Services RIPE NCC

1 0

Emergency Network Maintenance today RIPE NCC
by Brian Riddle 04 Jul '06

04 Jul '06

[Apologies for duplicate e-mails] Dear Colleagues, Due to the instability of our network over the last week, we will perform emergency maintenance today, 4 July 2006, from 16:00 - 19:00 (GMT). During this maintenance there will be disruption to the RIPE NCC network and its services. The instability is due to a problem with our firewalls. Our supplier is working to resolve the issues. We will remove the affected firewalls from our network until we are confident that these issues have been fully resolved. This will prevent any further related network outages. We apologise for any inconvenience this may cause. Regards, Brian Riddle IT Manager RIPE NCC

1 0

IPv6 access to ftp.ripe.net
by James Aldridge 28 Jun '06

28 Jun '06

[Apologies for duplicate e-mails] Dear Colleagues, IPv6 access to ftp.ripe.net is currently not possible. IPv4 access is unaffected. The current ScreenOS firewall software is unable to support extended passive-mode FTP. We have therefore temporarily removed the AAAA record for ftp.ripe.net from the DNS. We hope to restore IPv6 access as quickly as possible and will inform you when this occurs. We apologise for any inconvenience. Regards, James Aldridge Systems & Network Engineer RIPE NCC Operations Group

1 0

Network Upgrade
by Brian Riddle 27 Jun '06

27 Jun '06

[Apologies for duplicate e-mails] Dear Colleagues, I am pleased to announce that the network is now stable following the recent problems we experienced during last week's network upgrade. We have identified two key issues responsible for the instability. 1. Our current firewalls have been chosen to generously accommodate all previously experienced traffic levels. This is an IPv6 related issue which does not affect the stability of the network. 2. We have agreed with Juniper that this high CPU utilisation is an abnormal state which must be addressed. We have open tickets with our suppliers concerning these issues. The network upgrade has been a long-term project with many carefully planned and implemented steps. It is great to see the end of the tunnel appearing and we thank you for your patience and support in this matter. Regards, Brian Riddle IT Manager RIPE NCC

1 0