- db-wg - mailman.ripe.net

Data Protection Task Force - Ref: RIPE53 DB-WG Draft Agenda V3. item C
by Wilfried Woeber, UniVie/ACOnet 04 Oct '06

04 Oct '06

Dear Community, the logistical infrastructure for the Data Protection Task Force has been set up by the NCC. It is available at http://www.ripe.net/ripe/tf/index.html We are trying to get together a reasonably diverse mix of people for this task force, representing the various roles, activities and types of interest. The TF will be presented and discussed on Fr. morning in the DB-WG session where we will try to collect the initial population. If you can't make it to the DB-WG meeting, please indicate your interest by personal mail to Jochem de Ruig and myself. Please read up on the TF's mandate, the goals and logistics, and consider stepping forward to *actively* contribute! Thank you. See you Friday morning, Wilfried.

2 1

Re: [address-policy-wg] 2006-04 Draft Document will be produced (Contact e-mail Address Requirements)
by Denis Walker 27 Sep '06

27 Sep '06

Wilfried Woeber, UniVie/ACOnet wrote: > Denis Walker wrote: > > [...] > >> ... If you feel this >> should have a higher priority then you may raise the issue on the Database >> Working Group or Antispam Working Group or Address Policy Working Group >> mailing lists." >> > > My feeling is that the only appropriate one is the AP-WG - if at all. > we can easily change this if the AP-WG is considered to be the best place to raise such issues. > Anti-Spam seems to be a niche market, looking at the number of different > abusive behaviour patterns, and DB-WG usually looks at issues regarding > the tools and the registration machinery. > > In particular, DB-WG is very reluctant to get drawn into (human) resource > allocation (i.e. money :-) ) discussions... > > Wilfried. > > PS: I know I am not making new friends with the following text, but still: > Spam is not a network or addressing problem - it is an application and > socio-economic problem. Now shoot - you know where to find me :-) > I think we are confusing two seperate issues here. Spam itself is a socio-economic-political problem. How to stop spam is outside the scope of network operations and addressing policy issues. But the issue here is if I can identify an individual spammer who is causing me problems who should I contact to try to have this person/organisation disconnected? This ties into the whole discussion on the irt object and abuse-mailbox: attributes. Even if we get this part exactly right, if the final email address we present to someone is invalid then the whole system breaks down. This brings us back to the question of how to enforce a policy that says everyone should keep their contact details up to date. I know it is a difficult question, but until it is addressed the whole policy on abuse handling fails. regards Denis Walker Software Engineering Department RIPE NCC

1 0

org-type: NON-REGISTRY (was: New Documents available: RIPE-384, RIPE-385)
by Niall O'Reilly 18 Sep '06

18 Sep '06

[ WG Co-Chair hat on ] On 4 Sep 2006, at 13:26, Antoin Verschuren wrote: > I have some sentimental issues with the new ENUM request forms as I > found out when I had to use them last week. I'm pretty sure that, in English, "sentimental" is the wrong word and is likely to lead to confusion. I think I know what you mean. > The new ENUM registrations ask to register an Organisation holding the > registration. > > This "Organisation" template, has a "org-type:" field. > RIPE tells me to fill in "NON-REGISTRY" in this field. > > I'm aware that we are not an RIR, LIR or NIR as in the RIR world, > but I > do feel the term "NON-REGISTRY" a bit degrading as we are the registry > for .nl and soon hopefully for ENUM. > > Can we invent a new term to use for official ENUM tier-1 registries > here > ? The "optics" do indeed seem non-intuitive. 8-) If some ENUM tier-1 registry would take the initiative to put a proposal on the table, and a few sister organizations gave support, we could have consensus in the ENUM-WG in time to feed into the DB-WG agenda item: Y. Input from other WGs I think we have "all the ducks lined up", as the saying goes; we just need a proposal. Best regards, Niall O'Reilly Co-Chair, RIPE ENUM Working Group

1 0

RIPE53 DB-WG Draft Agenda V3
by Wilfried Woeber, UniVie/ACOnet 18 Sep '06

18 Sep '06

Dear DB-WG folks, Chairpersons, Meeting-Role! This is the 3rd draft of an agenda for the DB-WG at RIPE52 in Amsterdam - 1st week of October 2006. Changes since V12: item Y, iinput from ENUM-WG (t.b.c.) For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-53/meeting-plan.html Please note that, for our convenience, the time slot map becomes clickable for those sessions which have already submitted a (draft) agenda. Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters - scribe (Nigel T.) - list of participants - agenda - approval of minutes - review of action list - "remote participation" coordination (if needed) B. Data Base Update (N.N., RIPE NCC) [~30 min] . major developments like the IRT changes,... . DB support for glue records and ENUM delegations . ASN32, etc. C. Task-Force on Data Protection Issues (Jochen d. R. RIPE NCC) [~15 min] D. Proposal to retire CRYPT-PW (Peter K., denic.de + WW144) [~15 min] E. Review irt: e-mail/abuse-mailbox (Philippe B., CyberAbuse) [~15 min] F. Update on the Poetry Object (Nigel T.) [~10 min] . Processes for updating Poetic forms Y. Input from other WGs . ENUM-WG: on (new?) organisation type for Database Object [t.b.c.] Z. AOB

1 0

Call for agenda items, DB-WG Meeting during RIPE53, Amsterdam
by Wilfried Woeber, UniVie/ACOnet 15 Sep '06

15 Sep '06

Dear DB-WG folks, the RIPE NCC has asked us to submit the draft agendas for the WGs within the next few days. Thus, please submit (to the WG list or to me personally) your item requests or suggest topics for discussion to be included in the draft agenda. The DataBase-WG meeting is scheduled for Friday morning, October 6, 2006. The overall RIPE meeting outline is available at http://www.ripe.net/ripe/meetings/ripe-53/meeting-plan.html The list of plenary presentations scheduled may become available at http://www.ripe.net/ripe/meetings/ripe-53/presentations/ (empty right now) See you in Amsterdam, Wilfried.

4 4

RIPE53 DB-WG Draft Agenda V2
by Wilfried Woeber, UniVie/ACOnet 15 Sep '06

15 Sep '06

Dear DB-WG folks, Chairpersons, Meeting-Role! This is the 2nd draft of an agenda for the DB-WG at RIPE52 in Amsterdam - 1st week of October 2006. Changes since V1: item E, irt stuff, E in V1 becoming F For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-53/meeting-plan.html Please note that, for our convenience, the time slot map becomes clickable for those sessions which have already submitted a (draft) agenda. Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters - scribe (Nigel T.) - list of participants - agenda - approval of minutes - review of action list - "remote participation" coordination (if needed) B. Data Base Update (N.N., RIPE NCC) [~30 min] . major developments like the IRT changes,... . DB support for glue records and ENUM delegations . ASN32, etc. C. Task-Force on Data Protection Issues (Jochen d. R. RIPE NCC) [~15 min] D. Proposal to retire CRYPT-PW (Peter K., denic.de + WW144) [~15 min] E. Review irt: e-mail/abuse-mailbox (Philippe B., CyberAbuse) [~15 min] F. Update on the Poetry Object (Nigel T.) [~10 min] . Processes for updating Poetic forms Y. Input from other WGs Z. AOB

1 0

Suggestions to improve the IRT object
by Philippe Bourcier 15 Sep '06

15 Sep '06

Hi, The -c flag which is going to be implemented soon for any standard IP query to the RIPE whois is a good thing. But since most IRT objects returned don't have an abuse-mailbox field, the result is pretty useless (no e-mail will be returned). Developers will keep using -B in their tools so that they can send their abuse reports somewhere... Facts ===== The e-mail field of an IRT object is hidden until you use the -B flag. Most IRT objects have been created without an abuse-mailbox field. For the IRT object, the e-mail field is mandatory, but the abuse-mailbox is optional. The e-mail field of an IRT object is by definition an abuse-mailbox. Proposal ======== One of the easiest way to make the -c flag really useful without -B is to have all IRT objects return an abuse-mailbox. Thus, the abuse-mailbox field should be mandatory and for all IRT objects which don't have one, the e-mail field should be copied to it. (To be logical, the e-mail attribute should be set to optional.) More Thoughts ============= Another issue is to deploy the IRT object (or even the abuse-mailbox...) on a huge number of inetnum's. If we wait for people to modify all their inetnum objects so that they have an abuse-mailbox or irt-mnt attribute, it will take ages. A standard IP query to the RIPE whois now gives one "origin" attribute (or more). Maybe the mnt-irt of that aut-num could be displayed in the default output... A company not owning the AS announcing their prefix, and willing to use its own IRT object (or abuse-mailbox) could use the mnt-irt in their inetnum('s) to specify a "more specific" one. RFD === What do people think about these 2 ideas ? Sincerely, Philippe Bourcier

2 1

RIPE53 DB-WG Draft Agenda V1
by Wilfried Woeber, UniVie/ACOnet 14 Sep '06

14 Sep '06

Dear DB-WG folks, Chairpersons, Meeting-Role! This is the 1st draft of an agenda for the DB-WG at RIPE52 in Amsterdam - 1st week of October 2006. Changes since V.: ---. For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-53/meeting-plan.html Please note that, for our convenience, the time slot map becomes clickable for those sessions which have already submitted a (draft) agenda. Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters - scribe (Nigel T.) - list of participants - agenda - approval of minutes - review of action list - "remote participation" coordination (if needed) B. Data Base Update (N.N., RIPE NCC) [~30 min] . major developments like the IRT changes,... . DB support for glue records and ENUM delegations . ASN32, etc. C. Task-Force on Data Protection Issues (Jochen d. R. RIPE NCC) [~15 min] D. Proposal to retire CRYPT-PW (Peter K., denic.de + WW144) [~15 min] E. Update on the Poetry Object (Nigel T.) [~10 min] . Processes for updating Poetic forms Y. Input from other WGs Z. AOB

1 0

Announcement Routing Registry Training Courses
by RIPE NCC Training Services 29 Aug '06

29 Aug '06

Dear Colleagues The RIPE NCC Training Services Department invites you to register for one of our upcoming Routing Registry Training Courses: Date: Friday 1 September 2006 Time: 0900 - 1700 Location: Reykjavik, Iceland AND Date: Thursday 26 October 2006 Time: 0900 - 1700 Location: London, United Kingdom AND Date: Friday 4 November 2006 Time: 0900 - 1700 Location: Amsterdam, Netherlands AND Date: Monday 27 November 2006 Time: 0900 - 1700 Location: Rome, Italy Hosted by: CASPUR http://www.caspur.it/ Hosted by: NAMEX http://www.namex.it/ The main objective of the "Routing Registry Training Course" is to familiarise the LIRs with the features of the Routing Registry, while introducing the relevant tools and services of the RIPE NCC. The course also offers practical exercises. OVERVIEW OF TOPICS COVERED IN THE COURSE: - Routing Registry as a part of the RIPE Whois Database and the Internet Routing Registry (IRR) - Specifying routing policies using (RPSL) Routing Policy Specification Language and the RtConfig tool - IRRToolSet - Routing Information Service (RIS) - Routing Registry Consistency Check Project Please note that this is an advanced course. It will: - NOT teach the basics of routing - NOT teach the basics of RIPE Database operations - NOT describe how to receive Internet resources from the RIPE NCC - NOT describe how to operate a Local Internet Registry (LIR) The target audience of the course are technical staff of LIRs: e.g. network operators, engineers etc. This course is not intended for administrative or management staff (e.g. Hostmasters) . It is assumed that all attendees will be familiar with Border Gateway Protocol routing and with the RIPE Database (i.e. creating/modifying objects). This course is based on interactive exercises in a local network set-up. Please bring your laptops equipped with the following: - A working Ethernet card, - Three meters of Ethernet cable, - A secure connection client, - A web browser. Please be prepared to share your laptop (or at least allow another attendee to "look over your shoulder") if necessary. The course is free of charge. We provide lunch and printed training materials. We do not cover any of your travel expenses or accommodation. We give all of our training courses in English. You can find more information about the course at: http://www.ripe.net/training/rr/ How to register: --------------------- You can register up to two people from your LIR for each course. (If there are places left nearer the time of the course, you can register more people). To register for this course, you can either use the LIR Portal at: https://lirportal.ripe.net/lirportal/training/course-list.html Or the online registration form on our website: http://www.ripe.net/cgi-bin/trainingform.pl.cgi If you have any questions, send an e-mail to <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0

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

The RIPE Database and DNS management system has been updated
by Katie Petrusha 03 Aug '06

03 Aug '06

Dear Colleagues, We have updated the RIPE Database and DNS management system to implement several new features. The change in the RIPE Database: - There is a new syntax for the "nserver:" attribute in the DOMAIN object to support IPv4 and IPv6 glue name servers. The changes in the DNS management system: - The management of DNS delegation in the e164.arpa (ENUM) zone has been brought under the same provisioning system as reverse DNS management. - The Delegation Checker has been updated to support glue name servers for IPv4 and IPv6 - The Web Zone Delegation Checker has also been updated You can find more details about the proposal for implementation at: http://www.ripe.net/ripe/maillists/archives/dns-wg/2006/msg00128.html -- Katie Petrusha RIPE NCC

1 0

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

Re: [db-wg] crypted password
by Max Tulyev 25 Jul '06

25 Jul '06

Markus Werner wrote: > Migration steps. > > - Move all auth: MD5-PW to a new md5-pw object and reference them. > > - At some day it is possible to say that md5-pw are obsolet and deny > creation of new objects. So new users get forced to use a other method. > > - After time you can force users to update the auth method everytime > they need to edit an object. Nice. But seems too soft, and it takes a long time to migrate... My view: - Implement md5-pw object in database - Autocreate md5-pw objects for all existing md5 passwords - Autochange hashed passwords with md5-pw objects - Include "remark: see http://... for what's happened" in chaned objects Like it was in person/org objects when russian area phone codes was changed. -- WBR, Maxim V. Tulyev (MT6561-RIPE, 2:463/253@FIDO)

3 2

crypted password
by Max Tulyev 25 Jul '06

25 Jul '06

Hi! Why not to hide crypted password in mntner objects from public queries? It is so easy to crack now. -- WBR, Maxim V. Tulyev (MT6561-RIPE, 2:463/253@FIDO)

6 10

Proposal to change the syntax of "nserver:" attribute
by Katie Petrusha 11 Jul '06

11 Jul '06

[Apologies for duplicate mails] Motivation: We plan to automate management of DNS delegation in the e164.arpa zone (ENUM). The provisioning system, with the RIPE Database as a front end, must support IPv6 glue records. It must also implement complete and consistent IPv4 glue record support. This will mean making changes to the RIPE Database syntax so that it specifies the glue record and update the delegation checks. This proposal covers that syntax. Proposal: We suggest changing the syntax of the "nserver:" attribute in DOMAIN objects as follows: nserver: [domain_name] /or/ nserver: [domain_name] [ipv4_address] /or/ nserver: [domain_name] [ipv6_address] where [domain_name] is the fully qualified DNS name of the name server without a trailing "." [ipv4_address] is an IPv4 address of the name server [ipv6_address] is an IPv6 address of the name server If [domain_name] is followed by an IP address, it must be inside the zone that is being delegated. Any level of a glue name is supported within the valid domain name syntax. Multiple name server lines will need to be used to specify multiple IP addresses for the same hostname. Examples: The following values would be allowed: domain: example.com nserver: ns1.test.net 168.0.0.1 nserver: ns1.test.net 0::0 nserver: ns1.example.com nserver: ns1.d1.example.com All other variants of the values will be rejected. End-of-line comments starting with '#' will be still allowed. Consequences for existing objects: We will not automatically modify any existing objects. Instead we suggest notifying the maintainers of objects that do not comply with the proposed syntax. This will cover around 150 objects. Consequences for the delegation checks: DNS checks applicable to glue records will be added to the Zone Delegation Checker (http://www.ripe.net/rs/reverse/delcheck/delcheck_descr.html) -- Katie Petrusha RIPE NCC

10 16

Re: Need help with ripe-dbase-2.3
by Denis Walker 10 Jul '06

10 Jul '06

Dear Alex Unfortunately version 2 of the RIPE Database code was taken out of production more than 5 years ago. We have archives of the code but no one at the RIPE NCC works on it now. I am sorry but we are unable to assist you with this problem. I have copied this email to the Database Working Group in case some one in the community can assist you. Maybe there are others still running this version of the code. Regards Denis Walker Software Engineering Department RIPE NCC Alex Moura wrote: > Hello, > > We have been using the ripe-dbase-2.3 sucessfully on a server with > perl-5.00503, but now we are having problems to make it run on a new > server with perl-5.8.8. > The server runs, but dies after sucessfully replying a query, > recording only this error message: > > File: (...)/db-root/log/err/errlog > Fatal error: accept failed: No child processes PID: 98560 > > I'd like to know if this code would work with perl-5.8. I will try to > run it with perl-5.6.2, as it seem to be the oldest version od perl > available at the FreeBSD ports. > > We know this code is old, but I'm hopeful to have some answer about > this issue, once we have made some customizations to fufill our > organization needs, and we'd like to avoid - at least for now - having > to port these customizations to the most recent ripe-dbase code. > > Thank you in advance, > > Alex

1 0

2006-03 Policy Proposal Withdrawn (LIR-PARTITIONED status for IPv6)
by Filiz Yilmaz 06 Jul '06

06 Jul '06

PDP Number: 2006-03 LIR-PARTITIONED status for IPv6 Dear Colleagues The proposal 2006-03, LIR-PARTITIONED status for IPv6 has been withdrawn. The proposer decided that the proposal was no longer necessary. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/archive/ Regards Filiz Yilmaz RIPE NCC Policy Development Officer

1 0

Yet another ipv6 bug ;)
by Max Tulyev 03 Jul '06

03 Jul '06

Hi! If I go to www.ripe.net right now and ask for ORG-RL14-RIPE in whois from IP 2a01:d8:0:99:211:11ff:fe1f:bfc9 - I get %ERROR:208: connection refused From IP 195.209.61.241 everything seems to be fine. What is it? -- WBR, Maxim V. Tulyev (MT6561-RIPE, 2:463/253@FIDO)

2 1

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

Yesterday, 21 June, from 12:54 - 13:29 (CET), the RIPE NCC experienced a,network outage.
by Brian Riddle 22 Jun '06

22 Jun '06

[Apologies for duplicate e-mails.] Dear Colleagues, Yesterday, 21 June, from 12:54 - 13:29 (CET), the RIPE NCC experienced a network outage. The outage was caused by a firewall failure during the implementation of our new network infrastructure. We are currently working with Juniper to investigate the problem. We have scheduled maintenance today, 22 June, from 18:00 - 21:00 (CET) to resolve this. During this time, there will be some interruption to services. We apologise for any inconvenience caused by yesterday's outages and today's scheduled maintenance. If you have any questions, please e-mail: <ops(a)ripe.net> Regards, Brian Riddle IT Manager RIPE NCC -- Brian Riddle RIPE Network Coordination Center IT Manager Singel 258 Amsterdam NL http://www.ripe.net +31 20 535 4444 GPG Key fingerprint = 0EBA E8BA 236A D4CD B7A8 C679 A353 054D 2D35 9BE9

1 0

Bug report
by Max Tulyev 22 Jun '06

22 Jun '06

Hi! I can access to Crypt CGI interface at https://www.ripe.net/cgi-bin/crypt.cgi from 195.209.50.18 (IPv4), but from 2a01:d8:0:99:211:11ff:fe1f:bfc9 (IPv6) I can't. I can see http://www.ripe.net (not https probably?) from both addresses. -- WBR, Maxim V. Tulyev (MT6561-RIPE, 2:463/253@FIDO)

1 0

RIPE NCC (AS3333) Maintenance 18:00 - 21:00 (CEST) Today, June 21.
by James Aldridge 21 Jun '06

21 Jun '06

[Apologies for duplicate e-mails.] Dear Colleagues, The RIPE NCC will carry out emergency network maintenance today, June 21, between 18:00 and 21:00 (CEST). During this time, there will be some interruption to our peerings. This work is part of a programme of ongoing network upgrades. We apologise for any inconvenience that this may cause. If you have any questions, please contact: <ops(a)ripe.net> Regards, James -- James Aldridge, Systems & Network Engineer, RIPE NCC Operations Group Tel: +31 20 535 4444 / Fax: +31 20 535 4445

1 0

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