- db-wg - mailman.ripe.net

Bug?
by Max Tulyev 20 Jun '06

20 Jun '06

Hi! I got some troubles with web whois service at www.ripe.net. If my IP is 195.209.50.18 (IPv4) - I can do any queries. But if it is 2a01:d8:0:99:211:11ff:fe1f:bfc9 (IPv6) - I see this error message back to any of my queries (and to non-address queries too): %ERROR:203: address passing not allowed % % Sorry, you are not allowed to pass addresses on the query line. % Please contact us for such permission. For the moment, % continuing this will cause permanent denial of access. Mozilla Firefox tries IPv6 first if there is both addresses and connectivities... Is it a bug or a feature? -- WBR, Maxim V. Tulyev (MT6561-RIPE, 2:463/253@FIDO)

2 1

Maintenance of whois-test.ripe.net
by Agoston Horvath 16 Jun '06

16 Jun '06

[Apologies for duplicate e-mails.] Dear Colleagues, We will carry out maintenance work on flute.ripe.net (also known as whois-test.ripe.net) on Monday, 19 June at 11:00-13:00 (GMT). During this period, you may experience outages when trying to use the following services: - whois-test (queries and updates) - whois queries over ipv6 (including the web interface) - rrcc - dbconstat - surfme We apologise for any inconvenience. If you have any questions please contact: <ripe-dbm(a)ripe.net>. Regards, Agoston Horvath Software Engineering Department RIPE NCC

1 0

Update convention
by Niall O'Reilly 16 Jun '06

16 Jun '06

Begin forwarded message: > domain: 3.5.3.e164.arpa > nserver: ns01.3.5.3.e164.arpa 137.43.132.54 > nserver: ns02.3.5.3.e164.arpa 213.190.149.193 > nserver: enum1.eu.afilias.info > notify: ENUM-353-OPS(a)LISTSERV.HEANET.IE > changed: Niall.oReilly(a)ucd.ie 20060614 > changed: someone(a)comreg.ie 20040323 > changed: hostmaster(a)ripe.net 20041222 > source: RIPE > ***Error: Required attribute "descr" is missing > ***Error: Required attribute "admin-c" is missing > ***Error: Required attribute "tech-c" is missing > ***Error: Required attribute "zone-c" is missing I thought we used to have a convention that attributes to be left unchanged in an existing object could validly be omitted in the update request. Did I miss a considered change, or am I doing some "wishful recollection"? /Niall

2 1

Suggestion: un-necessary error message
by Niall O'Reilly 16 Jun '06

16 Jun '06

Begin forwarded message (extracted from a recent update attempt): > changed: Niall.oReilly(a)ucd.ie 20060614 > changed: oonagh.oreilly(a)comreg.ie 20040323 > changed: hostmaster(a)ripe.net 20041222 > source: RIPE > ***Error: The dates in the changed: attributes should be in > accending order > '20040323' was found after '20060614' Wouldn't it be just as easy to sort the attributes into the correct order as to generate an error message? /Niall

4 5

Request for unsuscription
by Mathias VDB 15 Jun '06

15 Jun '06

_________________________________________________________________ Windows Live Mail : venez tester la version bêta ! http://www.ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0…

1 0

Last Call: Proposal for Returning IRT objects
by Denis Walker 15 Jun '06

15 Jun '06

Dear Colleagues On 16 May 2006, we sent out the latest draft of the proposal for returning IRT objects to the RIPE Whois Database. The main difference between this and the previous draft is the introduction of a two-stage implementation plan. We have received no comments on the draft so far. You can find the proposal in the list archives at: http://www.ripe.net/ripe/maillists/archives/db-wg/2006/msg00087.html This is a last call for feedback. Please send any comments to the Database Working Group mailing list before 30 June 2006. After this date we plan to implement the change, taking into account any final comments from the community. Regards Denis Walker Software Engineering Department RIPE NCC

1 0

Outage of Syncupdate and Webupdate (correction)
by Trudy Prins 12 Jun '06

12 Jun '06

[Apologies for duplicate e-mails] Dear Colleagues, Correction: Please note that the service was restarted on *Sunday, 11 June at 23:53:54 GMT* and not as stated in the previous message. If you have any questions or concerns about this, please e-mail: ripe-dbm(a)ripe.net. Regards, Trudy Prins User Support Coordinator Software Engineering Department ------------------------------------------------------ Previous message: Dear Colleagues, The Syncupdate service and the Webupdate service were unavailable from Sunday, 11 June 15:08:19 GMT until Monday, 12 June 23:53:54 GMT. The services are now available again. We apologise for any inconvenience. If you have any questions or concerns about this, please e-mail: ripe-dbm(a)ripe.net. Regards, Trudy Prins User Support Coordinator Software Engineering Department

1 0

Outage of Syncupdate and Webupdate
by Trudy Prins 12 Jun '06

12 Jun '06

[Apologies for duplicate e-mails] Dear Colleagues, The Syncupdate service and the Webupdate service were unavailable from Sunday, 11 June 15:08:19 GMT until Monday, 12 June 23:53:54 GMT. The services are now available again. We apologise for any inconvenience. If you have any questions or concerns about this, please e-mail: ripe-dbm(a)ripe.net. Regards, Trudy Prins User Support Coordinator Software Engineering Department

1 0

Re: Deprecation of ip6.int scheduled for 1 June 2006
by Andrei Robachevsky 02 Jun '06

02 Jun '06

Dear Colleagues, This is a reminder that from 1 June 2006, reverse delegations in the ip6.int DNS tree corresponding to IPv6 address space allocated by the RIPE NCC will no longer be supported. On 1 June 2006, RIPE NCC delegations will be deleted from the ip6.int zone. Following this we will remove the zones from the authoritative servers and delete the corresponding DOMAIN objects in the RIPE Whois Database. The maintainers of the DOMAIN objects to be deleted will also receive individual notifications 1 week prior to the deletion. This is being coordinated with other RIRs and is based on an IETF Best Current Practice document (RFC 4159). Regards, Andrei Robachevsky Chief Technical Officer RIPE NCC On 14 March 2006 Andrei Robachevsky wrote: > Dear Colleagues > > In August 2005, the IETF published RFC 4159: 'Deprecation of "ip6.int"', > as a Best Current Practice document. The RFC noted that maintenance of > "ip6.int" is no longer needed and called on the Regional Internet > Registries (RIRs) to decide when to stop providing support for the > domain. The RIRs have jointly agreed to do this on 1 June 2006. > > There will be a short presentation on this at the RIPE 52 Meeting in > Istanbul. You can find more information about this meeting at: > > http://www.ripe.net/ripe/meetings/ripe-52/index.html > > Regards > > Andrei Robachevsky > Chief Technical Officer > RIPE NCC > > > > >

1 1

2006-03 New Policy Proposal (LIR-PARTITIONED status for IPv6)
by Filiz Yilmaz 01 Jun '06

01 Jun '06

PDP Number: 2006-03 LIR-PARTITIONED status for IPv6 Dear Colleagues A new RIPE Policy has been proposed and is now available for discussion. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2006-03.html We encourage you to review this proposal and send your comments to <db-wg(a)ripe.net> before 29 June 2006. Regards Filiz Yilmaz RIPE NCC Policy Development Officer

1 0