- db-wg - mailman.ripe.net

E-mail Client Testing for S/MIME Compliance
by Denis Walker 09 Jan '04

09 Jan '04

[apologies for duplicate messages] Dear Colleagues, At the RIPE 45 Meeting a proposal was presented to implement an additional form of strong authentication for protecting objects in the RIPE Database and to allow for secure communication by e-mail with the RIPE NCC. This implementation uses the X.509 certificates. A question was raised by some members about how widespread is the compliance of S/MIME within mail clients. The RIPE NCC Software Engineering Department has undertaken a study to evaluate the use of S/MIME by mail clients. The results of this study can be found on our web site at: http://www.ripe.net/ripencc/pub-services/db/mail_client_tests.html Regards, -- Denis Walker Software Engineering Department RIPE NCC

4 5

Domail Clean-up
by RIPE Database Manager 06 Jan '04

06 Jan '04

Dear Colleagues, As of 6 January, 2004, messages concerning inconsistencies between "nserver:" attributes in DOMAIN objects and delegation NS RRs in our zone files will be sent out. The messages will be mailed to various contact addresses for the relevant DOMAIN objects. In addition to the description of the inconsistencies, an indication of the 'default actions' will also be provided. We kindly request data be updated so that the inconsistencies are corrected before 1 March, 2004. About two weeks before 1 March, 2004 we will send a second set of warnings for the remaining inconsistencies. By 1 March, 2004 all remaining inconsistencies will be cleaned by the RIPE NCC, using the 'default actions'. If you receive a warning about inconsistencies we recommend that you fix the data yourself. It may be that you receive multiple mails for multiple domains with multiple inconsistencies. If you want to configure a dedicated mail filter the messages will contain the subject header "Subject: Reverse DNS inconsistencies in the RIPE Database" and originate "From: <ripe-dbm(a)ripe.net>". If you have further questions please contact <ripe-dbm(a)ripe.net>. Background The cleanup is part of the effort to streamline reverse DNS operations [1] and make it easier for network range users to manipulate related DOMAIN objects. The goal of the cleanup [2] is to streamline the contents of DOMAIN objects and zone configuration files so that we can create zone files from the Whois Database. An explanation of the various possible inconsistencies can be found at: http://www.ripe.net/reverse/rdns-project/Cleanup.html. ----- [1]: Original proposal http://www.ripe.net/reverse/proposal.html. Discussion on this proposal has taken place on the RIPE NCC Services WG mailing list and was summarized in: http://www.ripe.net/ripe/mail-archives/ncc-services-wg/2003/msg00361.html [2]: Original cleanup proposal http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00738.html. ----- Can Bican Software Engineering Department Olaf Kolkman New Projects Group RIPE NCC

1 0

creating a mntner
by Randy Bush 29 Dec '03

29 Dec '03

so, i have a clean database, 3.2.0 server running, blah blah blah now i have the old problem of creating a first mntner: i run bin/dbupdate -c conf/rip.config -t -d mntner: MAINT-RGNET descr: RGnet admin-c: RB366 upd-to: rw(a)rg.net auth: NONE override: <cleartext override password> mnt-by: MAINT-RGNET referral-by: MAINT-RGNET changed: randy(a)psg.com 20031217 source: RGNET ^D and it pukes saying Create FAILED: [mntner] MAINT-RGNET ***Info: Syntax check passed mntner: MAINT-RGNET descr: RGnet admin-c: RB366 upd-to: rw(a)rg.net auth: NONE mnt-by: MAINT-RGNET referral-by: MAINT-RGNET changed: randy(a)psg.com 20031217 source: RGNET ***Error: Unknown object referenced and the interesting part of the debug output up_source_commit: entered with operation [UP_CREATE] up_send_object_db: entered, operation [UP_CREATE] up_send_object_db: object to be sent [ mntner: MAINT-RGNET descr: RGnet admin-c: RB366 upd-to: rw(a)rg.net auth: NONE mnt-by: MAINT-RGNET referral-by: MAINT-RGNET changed: randy(a)psg.com 20031217 source: RGNET ] up_get_transaction_id: entered spent 0.00 sec; got 1 rows from [dbrgnet: INSERT INTO tid VALUES(NULL)] up_get_transaction_id: exiting with new id [18] up_send_object_db: transaction ID [18] SK_write = { sockfd=[7], buf=[ADD], count=[3] SK_write = { sockfd=[7], buf=[ ], count=[1] SK_write = { sockfd=[7], buf=[18], count=[2] SK_write = { sockfd=[7], buf=[ ], count=[2] SK_write = { sockfd=[7], buf=[mntner: MAINT-RGNET descr: RGnet admin-c: RB366 upd-to: rw(a)rg.net auth: NONE mnt-by: MAINT-RGNET referral-by: MAINT-RGNET changed: randy(a)psg.com 20031217 source: RGNET ], count=[218] SK_write = { sockfd=[7], buf=[ ], count=[2] SK_write = { sockfd=[7], buf=[ACK ], count=[4] SK_write = { sockfd=[7], buf=[18], count=[2] SK_write = { sockfd=[7], buf=[ ], count=[2] up_send_object_db: send complete up_send_object_db: received from socket [ %ERROR 4 ] up_send_object_db: received from socket [ E[4][1:RB366]:ref integrity: reference cannot be resolved ] up_send_object_db: received from socket [ ] up_send_object_db: received blank line from socket, stop reading Closing socket... 7 up_send_object_db: exiting with value UP_OK up_interpret_ripudb_result: entered, ripupd_result [%ERROR 4 E[4][1:RB366]:ref integrity: reference cannot be resolved clue by four, please randy

4 11

Re: [db-wg] 3.2.0 make_db getvar cores
by Randy Bush 19 Dec '03

19 Dec '03

> Everything seems OK in your config files you've sent. I could not > replicate your problem. My best bet is that, in rip.config > SOURCEFILE /usr/home/whois/conf/sources.config > points to a file which is _not_ the one you've sent. sigh. with that gdb output? puhleeze! (gdb) back #0 0x805087d in ca_parseSrcLine (lineStr=0xbfbff74c "database:\tdbrgnet", srcStructPtr=0x80c8400) at ca_sourceLoader.c:792 #1 0x8050147 in ca_readSources ( sourcesDefFile=0x80c2840 "/usr/home/whois/conf/sources.config", confVars=0x80b1840) at ca_sourceLoader.c:464 #2 0x804faa2 in ca_init (configFile=0xbfbff9b1 "../conf/rip.config") at ca_initFn.c:87 #3 0x804bc2f in main (argc=7, argv=0xbfbff858) at getvar.c:84 let me try to debug by turning on debugging in ca_sourceLoader.c # /usr/home/whois/utils/getvar -s SAMPLE -c /usr/home/whois/conf/rip.config -p dbhost Inside ca_readSources() function. Sources file is: /usr/home/whois/conf/sources.config We are reading a comment or an empty line ..... line:DATABASE SAMPLEDB:End of line Length of line: 17 LINE >>>DATABASE SAMPLEDBEND_OF_LINE Beginning of a database defintion ..... Database name is: SAMPLEDB line:host: localhost:End of line Length of line: 16 LINE >>>host: localhostEND_OF_LINE tokens[0] = host tokens[1] = localhost VarName: host; dbComp: localhost line:port: 3306:End of line Length of line: 11 LINE >>>port: 3306END_OF_LINE tokens[0] = port tokens[1] = 3306 VarName: port; dbComp: 3306 line:trx_support: n:End of line Length of line: 14 LINE >>>trx_support: nEND_OF_LINE tokens[0] = trx_support tokens[1] = n VarName: trx_support; dbComp: n line:user: rip:End of line Length of line: 10 LINE >>>user: ripEND_OF_LINE tokens[0] = user tokens[1] = rip VarName: user; dbComp: rip line:password: secret:End of line Length of line: 19 LINE >>>password: secretEND_OF_LINE tokens[0] = password tokens[1] = secret VarName: password; dbComp: secret line:/DATABASE:End of line Length of line: 9 LINE >>>/DATABASEEND_OF_LINE We have reached the end of a DATABASE definition Testing the population of the db structure: localhost::3306::n::rip::secret:: ^ wowie zowie! no database name ^ the very problem we sought guess what happens when the password is nine characters! .../ripe-dbase-3.2.0# grep -c strcpy ./modules/ca/ca_sourceLoader.c 16 oh wonderful and thanks a million for the debugging help randy

1 0

3.2.0 make_db getvar cores
by Randy Bush 17 Dec '03

17 Dec '03

o freebsd 4.9-stable, quite recent o all ports just rebuilt o wanted to do a clean fresh install of whois 3.2.0, as i could not successfully convert o successful build o successful install conf/rip.config same as used for 3.1.1 excpt did emacs diff merge to get the syntax changes conf/sources.rip same as used for 3.1.1 except added trx_support: n in mysql, i deleted both databases, RIPADMIN and dbrgnet /scripts# ./make_db -c ../conf/rip.config -s RGNET -0 Error: Non-existent database "dbrgnet" referenced !!! died: +792 ca_sourceLoader.c Segmentation fault (core dumped) ************** ERROR *************** *** 05:19:01 unknown source RGNET ************************************ # gdb /usr/local/src/net/ripe-dbase-3.2.0/utils/getvar/getvar getvar.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf Core was generated by `getvar'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/libgthread12.so.3...done. Reading symbols from /usr/local/lib/libglib12.so.3...done. Reading symbols from /usr/local/lib/mysql/libmysqlclient_r.so.10...done. Reading symbols from /usr/lib/libm.so.2...done. Reading symbols from /usr/lib/libcrypt.so.2...done. Reading symbols from /usr/lib/libpam.so.1...done. Reading symbols from /usr/lib/libcipher.so.2...done. Reading symbols from /usr/local/lib/libxml2.so.5...done. Reading symbols from /usr/local/lib/libiconv.so.3...done. Reading symbols from /usr/local/lib/libxslt.so.2...done. Reading symbols from /usr/lib/libc_r.so.4...done. Reading symbols from /usr/lib/libz.so.2...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x805087d in ca_parseSrcLine (lineStr=0xbfbff74c "database:\tdbrgnet", srcStructPtr=0x80c8400) at ca_sourceLoader.c:792 792 die; (gdb) back #0 0x805087d in ca_parseSrcLine (lineStr=0xbfbff74c "database:\tdbrgnet", srcStructPtr=0x80c8400) at ca_sourceLoader.c:792 #1 0x8050147 in ca_readSources ( sourcesDefFile=0x80c2840 "/usr/home/whois/conf/sources.config", confVars=0x80b1840) at ca_sourceLoader.c:464 #2 0x804faa2 in ca_init (configFile=0xbfbff9b1 "../conf/rip.config") at ca_initFn.c:87 #3 0x804bc2f in main (argc=7, argv=0xbfbff858) at getvar.c:84 randy

2 2

Re: [sed] problem updating database to 3.2.0
by Randy Bush 17 Dec '03

17 Dec '03

engin pointed out my stupid, using the admin db as opposed to the whois db. but now i fail on the last set # mysql -ufoo -pbar -Ddbrgnet -e'ALTER TABLE acl ADD COLUMN threshold tinyint(3) unsigned Default '4' NOT NULL after trustpass' $SOURCE ERROR 1146 at line 1: Table 'dbrgnet.acl' doesn't exist # mysql -ufoo -pbar -Ddbrgnet -e'ALTER TABLE acl ADD COLUMN maxconn tinyint(3) unsigned Default '6' NOT NULL after threshold' $SOURCE ERROR 1146 at line 1: Table 'dbrgnet.acl' doesn't exist another clue by four please randy

2 1

problem updating database to 3.2.0
by Randy Bush 16 Dec '03

16 Dec '03

running 3.1.1 and trying to get to 3.2.0 first line of UPDATING fails # mysql -ufoo -pbar -DRIPADMIN -e'ALTER TABLE names DROP PRIMARY KEY' ERROR 1146 at line 1: Table 'RIPADMIN.names' doesn't exist clue-by-four please randy

1 0

Announcement Routing Registry Training Courses
by RIPE NCC Training 16 Dec '03

16 Dec '03

------- Dear Colleagues, [apologies for duplicate postings] As a service to its members the RIPE NCC offers the "Routing Registry Training Course". 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 Routing Registry Training Course is conducted in the English language and is free of charge, since it is covered by the membership fee. More information about the Routing Registry Training Course can be found at: http://www.ripe.net/training/rr/ REGISTRATION: You can register for a Routing Registry Training Course at the following URL: http://www.ripe.net/cgi-bin/trainingform.pl.cgi Or by completing the registration form at the end of this e-mail and replying to <training(a)ripe.net> . In order to register for a Routing Registry Training Course you must be an employee of an LIR and either: - be an LIR contact - be confirmed by an LIR contact LIR contacts are those employees of an LIR who are registered with RIPE NCC as authoritative contact persons. It is expected that most of those interested in the Routing Registry Training Course will not be an authoritative contact person for their LIR, and therefore will be, refused by the course registration "robot". In order to be admitted to the course, a confirmation e-mail must be sent to <training(a)ripe.net>. Please approach the LIR contacts from your organisation personally, since the identity of LIR contacts is confidential, and the RIPE NCC is unable to divulge contact persons for any given LIR. Kind Regards, Training Team RIPE NCC ************************************************************************* COURSE DATES AND VENUES ======================== Date: Friday 6 February 2004 Time: 0900 - 1700 Location: Amsterdam, The Netherlands AND: Date: Tuesday 17 February 2004 Time: 0900 - 1700 Location: Tehran, Iran AND: Date: Friday 5 March 2004 Time: 0900 - 1700 Location: Rome, Italy AND: Date: Friday 23 April 2004 Time: 0900 - 1700 Location: Istanbul, Turkey AND: Date: Friday 14 May 2004 Time: 0900 - 1700 Location: Bratislava, Slovakia AND: Date: Thursday 24 June 2004 Time: 0900 - 1700 Location: Stockholm, Sweden ************************************************************************* REGISTRATION FORM ================= %START PART 1 - Registration 1) Your name Enter First name, Last name in full e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) Your NIC handle (optional) # NICHANDLE [ ] 5) The course you plan to attend (date and location) # COURSE [ ] %END

1 0

RIPE DB missing inetnum referral for 204/8 (and others) to ARIN?
by Daniel Roesen 10 Dec '03

10 Dec '03

Hi, $ whois -h whois.ripe.net 204.152.184.85 [...] inetnum: 0.0.0.0 - 255.255.255.255 netname: IANA-BLK descr: The whole IPv4 address space [...] and nothing else. The referral to ARIN for 204/8 is missing. I've checked a couple of other RIRs /8s which all had the same problem. Was there a deliberate change that I missed? Best regards, Daniel

2 5

Deprecation of "cross-nfy:" and "cross-mnt:" attributes in the RIPE Whois Database
by Katie Petrusha 05 Dec '03

05 Dec '03

[ Apologies for duplicate messages ] Dear colleagues, "cross-nfy:" and "cross-mnt:" attributes will be deprecated in the RIPE Whois Database by 1 February 2004. The RIPE Whois Database previously had a cross notification mechanism. This mechanism used "cross-nfy:" and "cross-mnt:" attributes of route and aut-num objects to notify particular maintainers and contacts when an overlapping route object had been added or removed. In May 2003, this mechanism was deprecated, as it is already covered by Routing Policy System Security functionality. In March 2003, the proposal was circulated to deprecate "cross-nfy:" and "cross-mnt:" attributes in the RIPE Whois Database as they are no longer needed: http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00035.html Approximately 180 aut-num and 620 route objects will be affected by this change. These objects should be modified before 1 February 2003 and the "cross-nfy:" and/or "cross-mnt:" attributes should be removed from them. As soon as these attributes have been deprecated, they will not be accepted in the RIPE Whois Database. Therefore, we encourage everyone to make the necessary modifications in advance. The RIPE Database Administration will update the objects still requiring modifications to change deprecated attributes into "remarks:" attributes. No individual notifications will be sent. Relevant maintainers will be notified via the usual RIPE Whois Database notification mechanism. This information can be found at: http://www.ripe.net/db/cross_nfy_mnt_deprecation.html -- Katie Petrusha Software Engineering Department RIPE NCC

1 0

Announcement: Redirecting reverse DNS updates
by RIPE Database Manager 05 Dec '03

05 Dec '03

Dear Colleagues, From 8 December 2003, as part of the effort to streamline reverse DNS operations, domain updates that contain in-addr.arpa or ip6.arpa type entries sent to <auto-dbm(a)ripe.net> will automatically be forwarded to <auto-inaddr(a)ripe.net> for processing. This will continue until the two processes are combined into one. Such updates will be processed as follows: - If the update contains only domain objects whose "domain:" attributes end with 'in-addr.arpa' or 'ip6.arpa' , it will be redirected to: <auto-inaddr(a)ripe.net> - If the update contains a mixture of domain objects whose "domain:" attributes end with 'in-addr.arpa' or 'ip6.arpa', as well as other types of database objects, the message will be rejected. The user will receive an e-mail requesting that the objects be separated and re-submitted. - All other e-mails will be processed as normal. - It will not be possible to update these domain objects using syncupdates. Please don't hesitate to contact <ripe-dbm(a)ripe.net> for questions, comments or suggestions. Regards, -- Can Bican Software Engineering Department RIPE NCC

1 1

Domain Cleanup Proposal
by RIPE Database Manager 03 Dec '03

03 Dec '03

Dear Colleagues, A. Introduction This proposal is part of the effort to streamline reverse DNS operations [1] and make it easier for network range users to manipulate related domain objects. Local Internet Registries (LIRs) maintain their reverse delegations at the RIPE NCC through the use of domain objects. For several historical reasons there are a number of inconsistencies between the domain objects and the reverse delegation information in the DNS. Since we want to move to a system in which the Whois Database is the authoritative source for data that is published in the DNS (see [1]), there is a need to remove these inconsistencies. In this proposal, we will address the inconsistencies between data represented through the domain objects in the Whois Database and the reverse delegation data in our zone-files. We will also propose solutions to fix these inconsistencies. Note, this proposal is only relevant for domain objects that the RIPE NCC provides reverse delegation services for i.e. networks delegated to it by the Internet Address and Numbering Association (IANA) and networks transferred to the RIPE Database via the Early Registration Transfer (ERX) Project [2]. This proposal is NOT relevant to domains in the e164.arpa space. B. Type of Inconsistencies - Domain objects that have no delegation in the zone configurations: Reverse DNS-related updates to the RIPE database must be sent to <auto-inaddr(a)ripe.net>, otherwise zone configurations can not be updated. There are objects in the RIPE Database created via methods other than by sending an e-mail to <auto-inaddr(a)ripe.net>, causing this type of inconsistency. - Zone configuration entries that do not exist as domain objects in the RIPE Database: When zone files are updated manually, and not by sending an e-mail to <auto-inaddr(a)ripe.net>, this type of inconsistency occurs. - Conflicting entries in the RIPE Database and zone files: A mismatch between the "nserver:" attributes and the NS Resource Records (RRs) in our zone files occurs as a mixture of the first two inconsistencies. The domain object has been added or modified at one point via <auto-inaddr(a)ripe.net>, but then either updated manually or by <auto-dbm(a)ripe.net>. - Invalid domain objects in the RIPE Database: This type of inconsistency occurs in domain objects that can not map to a valid DNS entry. As an example, 8080.80.in-addr.arpa is an invalid entry. Only reverse address space mapping is taken into account. - Invalid "nserver:" attributes in the RIPE Database: "nserver:" attributes must contain hostnames rather than IP entries. This type of inconsistency occurs when one of the "nserver:" attributes does not contain a host name. C. Preventive remedies - Enforcing domain updates to <auto-inaddr(a)ripe.net> We are in the process of integrating <auto-inaddr(a)ripe.net> and <auto-dbm(a)ripe.net>, so that domain updates and other types of updates can be performed from the same source. Until then, in order to prevent further inconsistencies, updates sent to <auto-dbm(a)ripe.net> containing only reverse domain objects will automatically be forwarded to <auto-inaddr(a)ripe.net>. Updates that contain a mixture of domain and other types of objects will be returned to the user unprocessed, warning him/her to split the objects and resend. A separate announcement has already been sent to related mailing lists about this change. D. Clean-up of Inconsistencies The goal of the clean-up is to streamline the contents of domain objects and zone configuration files so that we can create zone files from the Whois Database. If choices have to be made about which data is more accurate , the data in the DNS has prevalence over the data in the Whois Database. The approach followed in the clean-up is to identify inconsistencies, notify the contact persons for the domain objects, provide them with a suggested fix and allow maintainers to fix their objects (details below). After about six weeks the RIPE NCC will send messages about inconsistencies still present in the system. Two weeks after this message has been sent, the RIPE NCC will apply the suggested fix to the domain objects automatically. - Domain objects that do not exist in zone configurations: Contact persons(*) in the domain object will be notified that the object will be deleted by the given deadline unless it is updated. This procedure will be followed even if the domain object contains valid delegation information. Resubmitting the object will ensure that a valid delegation is created in the DNS. - Zone configuration entries that do not exist as domain objects in the RIPE Database: The contact persons(*) in the less specific inetnum object will be notified that, at a given deadline, place holder records in the RIPE Database will be created for these objects. These can be overridden by the maintainer of the inetnum object. The notification contains a suggested domain object that can be modified and submitted before the deadline if the LIR does not want to have a domain object created automatically. - Conflicting entries in the RIPE Database and zone files: Contact persons(*) in the domain object will be notified that the object will be updated to reflect the contents of the delegation NS RR in the reverse zone files by the given deadline. They will be notified that they can fix these entries by updating them. The notification contains a suggested domain object that can be modified and submitted before the deadline if the LIR does not want to have a domain object modified automatically. The clean-up is not meant to solve lame delegation data (e.g. when the NS RRs at the parent side are different from NS RRs at the child side of a zone). Therefore the suggested domain object might not represent the actual set of authoritative nameservers and fail during submission by the maintainer. - Invalid domain objects in the RIPE Database: Contact persons(*) in the domain object will be notified that the object will be deleted by the given deadline. - Invalid "nserver:" attributes in the RIPE Database: Contact persons(*) in the domain object will be notified that the contents of the "nserver:" attributes will be replaced by the entries in zone files if there are any, otherwise the object will be deleted. One IP address may refer to many hostnames, therefore automatically replacing it with its host entry may be erroneous. *: Contact persons are defined by the NIC handles listed in the "admin-c:", "tech-c:", "zone-c:" and the "mnt-by:" attributes of the domain object. E. Timeline - 7/12/2003: Filtering domain updates to <auto-dbm(a)ripe.net>. Domain objects submitted to <auto-dbm(a)ripe.net> are redirected to the <auto-inaddr(a)ripe.net> interface. - 3/12/2003: An announcement will be sent to the Database WG and DNS WG mailing lists - January 2004:Listing inconsistencies and sending notifications to contact persons. - End of February 2004 (announced approximately two weeks before): Cleanup (creation of place holder records and synchronising conflicting entries) This timeline allows for a two month period in which customers are informed and have the opportunity to fix inconsistencies. The end of February milestone is tentative and may extended during the cleanup if unexpected problems are encountered. E. References [1]: Original proposal http://www.ripe.net/reverse/proposal.html. Discussion on this proposal has taken place on the RIPE NCC Services WG mailing list and was summarised in: http://www.ripe.net/ripe/mail-archives/ncc-services-wg/2003/msg00361.html [2]: Early Registration Transfer [ERX] Project http://www.ripe.net/db/erx/erx-ip/ Regards, -- Can Bican Software Engineering Department Olaf Kolkman New Projects Group RIPE NCC

1 0

Re: [db-wg] Proxy abuse
by Thor Kottelin 30 Nov '03

30 Nov '03

> db-wg-request(a)ripe.net wrote: > From: "CMC" <icaliber(a)voicenet.com> > People using proxies on IRC is getting out of hand. On the Undernet as > example, proxy users can abuse a chat channel; be properly banned and > then return with their real hostmasks... > > I realize that the above statement is very general, however if any people > who are channel operators on any IRC chat network have been experiencing > problems with proxies, is there any solutions that the membership can > offer? Channel modes +ikm +s. Bans; if you run out of space, use dynamic, bot-controlled ban lists. On the server level, proxy checks on connect, and K: lines for the worst offenders. (This isn't at all on topic for db-wg, so follow-ups should go elsewhere. Apologies to everyone.) Thor -- http://thorweb.anta.net/

1 0

Proxy abuse
by CMC 30 Nov '03

30 Nov '03

Hi Friends People using proxies on IRC is getting out of hand. On the Undernet as example, proxy users can abuse a chat channel; be properly banned and then return with their real hostmasks... I realize that the above statement is very general, however if any people who are channel operators on any IRC chat network have been experiencing problems with proxies, is there any solutions that the membership can offer? thank you, charles

1 0

RE: [db-wg] ACCESS to INVALID OBJECTS
by Wilfried Woeber, UniVie/ACOnet 28 Nov '03

28 Nov '03

Dear Allen Turner! >Hello, >For some time now we have been expecting to be given direct access to >INVALID OBJECTS via the LIR Portal. Thanks for bringing this to our attention! >This will be a useful tool for a large LIR to run in conjunction with >public Asused. > >Can we be given a realistic date when it's going to be made available? >It's introduction will save time for both LIR's & RIPE NCC. At first glance that seems to be more like an issue for the Services WG? Or are there anything "database technology"-related aspects to be taken care of? >Regards, >Allen Turner >uk.bt LIR Thanks, Wilfried.

1 0

Searching the RIPE Db
by ipmaster＠bt.com 28 Nov '03

28 Nov '03

Hi, When searching the Database using http://www.ripe.net/ripencc/search.html for previous assignments, it returns a list of INETNUM's without the date. I have to open each one individually to check if it has been assigned within the last 12 months. Q: Is their any way to display the changed line without opening each one individually, hopefully Dave Trickett +44 20 7555 8226

2 1

ACCESS to INVALID OBJECTS
by preston.dialip＠bt.com 28 Nov '03

28 Nov '03

Hello, For some time now we have been expecting to be given direct access to INVALID OBJECTS via the LIR Portal. This will be a useful tool for a large LIR to run in conjunction with public Asused. Can we be given a realistic date when it's going to be made available? It's introduction will save time for both LIR's & RIPE NCC. Regards, Allen Turner uk.bt LIR

1 0

Maintenance on RIPE Whois Server, 28 November 2003
by DB-News 27 Nov '03

27 Nov '03

Dear Colleagues, [apologies for duplicate messages] Tomorrow, 28 November 2003, we need to perform a maintenance work on the RIPE Whois Server for hardware replacement. During the maintenance work, - Whois Database updates will be stopped, - all update mails to auto-dbm(a)ripe.net will be queued to be processed later, - Webupdate and syncupdate interfaces will be unavailable, - The whois queries will _not_ be interrupted. The maintenance work will start at 07:00 UTC (08:00 Amsterdam time) on 28 November 2003, Friday, and expected to last 2 to 3 hours. We apologise for the inconvenience caused, and we are sorry for the short notice. Please do not hesitate to contact ripe-dbm(a)ripe.net for any questions. Best regards, -- Engin Gunduz Software Engineering Department RIPE NCC

1 0

Input for DB-WG agenda for Jan.2004 [was: First Call: RIPE 47 Working Group Agendas]
by Wilfried Woeber, UniVie/ACOnet 25 Nov '03

25 Nov '03

Dear DB-WG participants, >To: wg-chairs(a)ripe.net >From: Nick Hyrka <nick(a)ripe.net> >Subject: First Call: RIPE 47 Working Group Agendas >CC: meeting(a)ripe.net >Date: Tue, 25 Nov 2003 12:16:46 +0100 > >Dear RIPE Working Group Chairs, > >RIPE 47 is quickly approaching and we are now seeking your session agendas. Thus: Could you pls. let me know which topics you want to discuss during the Januray 2004 DB-WG meeting in Amsterdam?! Of course I'll work with the NCC and I will add the administrivia, but your input is essential to meet the "real" needs of the RIPE DataBase user community :-) Please forward suggestions to me directly [to keep down noise on the list], or to the list if you think an issue should be discussed in a broader forum starting _now_! TIA for your input, looking forward to see as many of you as possible in Amsterdam, Wilfried. _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Announcement on "mnt-lower" changes in the RIPE Whois Database
by Katie Petrusha 17 Nov '03

17 Nov '03

[ Apologies for duplicate e-mails ] Dear colleagues, The following changes will become effective in the RIPE Whois Database starting from November 26, 2003. These changes are intended to make the database work more consistently, as well as provide an increased level of security and control to users. 1. When creating an inetnum, inet6num or domain object, the "mnt-lower:" attribute in the parent object must authorise the creation. If it is not present, the "mnt-by:" attribute must authorise the creation. This behaviour will allow a more secure hierarchical authorisation scheme in the RIPE Whois Database (similar to RPSS) for those object types. This change is implemented according to the following proposal: Proposed change 2003.0: default to protected inetnum/inet6num/domain http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00478.html RIPE NCC allocations that don't have "mnt-lower:" attribute will be affected by this change as they are maintained by the RIPE NCC. To prevent this, affected inetnum objects have been updated to include a "mnt-lower:" attribute. More details about this project are available at: http://www.ripe.net/db/allocations_mnt-lower_update.html 2. The "mnt-lower:" attribute will become optional for all set object types (as-set, filter-set, peering-set, route-set, and rtr-set). The "mnt-lower:" of the parent object attribute must authorise creation when hierarchical names are used. If it is not present, the "mnt-by:" of the parent object must authorise the creation. This change is implemented according to the following proposal: Proposed change 2003.4: "mnt-lower:" on set objects http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00482.html -- Katie Petrusha Software Engineering Department RIPE NCC

1 0

Announcement Routing Registry Training Courses
by RIPE NCC Training 13 Nov '03

13 Nov '03

------- Dear Colleagues, [apologies for duplicate postings] As a service to its members the RIPE NCC offers the "Routing Registry Training Course". 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 Routing Registry Training Course is conducted in the English language and is free of charge, since it is covered by the membership fee. More information about the Routing Registry Training Course can be found at: http://www.ripe.net/training/rr/ REGISTRATION: You can register for a Routing Registry Training Course at the following URL: http://www.ripe.net/cgi-bin/trainingform.pl.cgi Or by completing the registration form at the end of this e-mail and replying to <training(a)ripe.net> . In order to register for a Routing Registry Training Course you must be an employee of an LIR and either: - be an LIR contact - be confirmed by an LIR contact LIR contacts are those employees of an LIR who are registered with RIPE NCC as authoritative contact persons. It is expected that most of those interested in the Routing Registry Training Course will not be an authoritative contact person for their LIR, and therefore will be, refused by the course registration "robot". In order to be admitted to the course, a confirmation e-mail must be sent to <training(a)ripe.net>. Please approach the LIR contacts from your organisation personally, since the identity of LIR contacts is confidential, and the RIPE NCC is unable to divulge contact persons for any given LIR. Kind Regards, The RIPE NCC Training Team ************************************************************************* COURSE DATES AND VENUES ======================== Date: Friday 12 December 2003 Time: 0900 - 1700 Location: Lisbon, Portugal AND: Date: Friday 9 January 2004 Time: 0900 - 1700 Location: London, United Kingdom AND: Date: Friday 6 February 2004 Time: 0900 - 1700 Location: Amsterdam, The Netherlands AND: Date: Friday 5 March 2004 Time: 0900 - 1700 Location: Rome, Italy ************************************************************************* REGISTRATION FORM ================= %START PART 1 - Registration 1) Your name Enter First name, Last name in full e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) Your NIC handle (optional) # NICHANDLE [ ] 5) The course you plan to attend (date and location) # COURSE [ ] %END

1 0

Novel NetMail users
by Denis Walker 10 Nov '03

10 Nov '03

Dear Colleagues, In the process of testing mail clients for s/mime compatibility I am trying to install Novell NetMail on our linux test box running RedHat 8.0. I have no previous knowledge at all about this product. I have tried several times to install it and can never get past a window asking for the Administrator user name and password. I have included the log of what I did below. Any help from users of this mail client would be very much appreciated. Regards Denis Walker RIPE NCC Software Engineering Department. [root@linux setup]# ./nds-install %% Welcome to the installation of Novell eDirectory 8.7.0 %% The Novell eDirectory (8.7.0) for Linux End User License Agreement will now be displayed. %% Please read the agreement carefully before accepting the terms. %% Press ENTER to continue. %% Do you accept the terms of the Novell eDirectory (8.7.0) license agreement '[y/n/q] ? 'y %% List of Novell eDirectory (8.7.0) components available to install %% 1 Novell eDirectory Server %% 2 Novell eDirectory Administration Utilities %% 3 Management Console for Novell eDirectory (ConsoleOne) %% Select the components you wish to install [?, q] : 1,2,3 %% Enter the path to License File (.nfk): /var %% License file Copied. %% Adding packages... Preparing... ########################################### [100%] 1:NDSmasv ########################################### [100%] Preparing... ########################################### [100%] 1:NDSbase ########################################### [100%] Preparing... ########################################### [100%] 1:NLDAPsdk ########################################### [100%] Preparing... ########################################### [100%] 1:NLDAPbase ########################################### [100%] Preparing... ########################################### [100%] 1:NDScommon ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLpkis ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLpkia ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLpkit ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLsas ########################################### [100%] Preparing... ########################################### [100%] 1:ntls ########################################### [100%] Preparing... ########################################### [100%] 1:NDSserv ########################################### [100%] Preparing... ########################################### [100%] 1:NDSrepair ########################################### [100%] Preparing... ########################################### [100%] 1:NDSimon ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLsnmp ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLsubag ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLnmas ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLembox ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLlmgnt ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLstlog ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLxis ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLice ########################################### [100%] Preparing... ########################################### [100%] 1:NDSdxevnt ########################################### [100%] %% Installing ConsoleOne.... The following is a list of languages that are available to install. 1 English 2 French 3 All Select the languages you wish to install [?,q]: 1 The following are all the available snapins you can choose to install 0 NONE 1 ICE Snapin 2 Index Manager Snapin 3 LDAP Snapin 4 SLP Snapin 5 WAN Manager Snapin 6 PKI Snapin 7 Filtered Replica Snapin 8 All Select the snapin(s) you wish to install [?,q]: 8 Do you wish to install Java Runtime Environment [y,n,q] ? y OpenSLP rpm " openslp-1.0.11-0.fdr.6.rh80 " is already installed. NDSslp will not be installed. %% Adding package IBMJava2-JRE ... Preparing... ########################################### [100%] 1:IBMJava2-JRE ########################################### [100%] %% NDSbase package is already installed. %% NDScommon package is already installed. %% NLDAPsdk package is already installed. %% NLDAPbase package is already installed. %% NOVLxis package is already installed. %% NOVLlmgnt package is already installed. %% NOVLice package is already installed. %% NOVLsas package is already installed. %% NOVLpkia package is already installed. %% NOVLpkis package is already installed. %% Adding package NOVLc1 ... error: Failed dependencies: NDSslp is needed by NOVLc1-1.3.4-1 %% ERROR: Failed to add NOVLc1 (NOVLc1) package. %% Installation of packages failed, not all packages were installed. ucd-snmp package is not installed on your system. Please ensure that you install this package before using any SNMP related features of Novell eDirectory (8.7.0) . Please refer to the admin_guide.pdf for more details. %% Novell eDirectory Server packages successfully installed. %% Novell eDirectory Administration Utilities packages successfully installed. %% Use "ndsconfig" to configure Novell eDirectory Server. %% Please update following environment variables to use LDAP tools from Novell - PATH=/usr/ldaptools/bin:$PATH MANPATH=/usr/ldaptools/man:$MANPATH %% Please go through ../readme.txt carefully before using the product. [root@linux setup]# [root@linux setup]# rpm -i /home/test-receiver/novel/Linux/ConsoleOne/NDSslp-8. 7.0-1.i386.rpm Starting NDS SLP services... Done [root@linux setup]# ./nds-install %% Welcome to the installation of Novell eDirectory 8.7.0 %% The Novell eDirectory (8.7.0) for Linux End User License Agreement will now be displayed. %% Please read the agreement carefully before accepting the terms. %% Press ENTER to continue. %% Do you accept the terms of the Novell eDirectory (8.7.0) license agreement '[y/n/q] ? 'y %% List of Novell eDirectory (8.7.0) components available to install %% 1 Novell eDirectory Server %% 2 Novell eDirectory Administration Utilities %% 3 Management Console for Novell eDirectory (ConsoleOne) %% Select the components you wish to install [?, q] : 1,2,3 %% Enter the path to License File (.nfk): /var %% License file Copied. %% Adding packages... NDSmasv is already installed NDSbase is already installed NLDAPsdk is already installed NLDAPbase is already installed NDScommon is already installed NOVLpkis is already installed NOVLpkia is already installed NOVLpkit is already installed NOVLsas is already installed ntls is already installed NDSserv is already installed NDSrepair is already installed NDSimon is already installed NOVLsnmp is already installed NOVLsubag is already installed NOVLnmas is already installed NOVLembox is already installed NOVLlmgnt is already installed NOVLstlog is already installed NOVLxis is already installed NOVLice is already installed NDSdxevnt is already installed %% Installing ConsoleOne.... The following is a list of languages that are available to install. 1 English 2 French 3 All Select the languages you wish to install [?,q]: 1 The following are all the available snapins you can choose to install 0 NONE 1 ICE Snapin 2 Index Manager Snapin 3 LDAP Snapin 4 SLP Snapin 5 WAN Manager Snapin 6 PKI Snapin 7 Filtered Replica Snapin 8 All Select the snapin(s) you wish to install [?,q]: 8 OpenSLP rpm " openslp-1.0.11-0.fdr.6.rh80 " is already installed. NDSslp will not be installed. %% NDSbase package is already installed. %% NDScommon package is already installed. %% NLDAPsdk package is already installed. %% NLDAPbase package is already installed. %% NOVLxis package is already installed. %% NOVLlmgnt package is already installed. %% NOVLice package is already installed. %% NOVLsas package is already installed. %% NOVLpkia package is already installed. %% NOVLpkis package is already installed. %% Adding package NOVLc1 ... Preparing... ########################################### [100%] 1:NOVLc1 ########################################### [100%] %% Adding package NDSsice ... Preparing... ########################################### [100%] 1:NDSsice ########################################### [100%] %% Adding package NDSsimgr ... Preparing... ########################################### [100%] 1:NDSsimgr ########################################### [100%] %% Adding package NDSsldap ... Preparing... ########################################### [100%] 1:NDSsldap ########################################### [100%] %% Adding package NDSsslp ... Preparing... ########################################### [100%] 1:NDSsslp ########################################### [100%] %% Adding package NDSswan ... Preparing... ########################################### [100%] 1:NDSswan ########################################### [100%] %% Adding package NDSspki ... Preparing... ########################################### [100%] 1:NDSspki ########################################### [100%] %% Adding package NDSsfrep ... Preparing... ########################################### [100%] 1:NDSsfrep ########################################### [100%] %% ConsoleOne Successfully Installed. %% Execute /usr/ConsoleOne/bin/ConsoleOne to run ConsoleOne %% Snapins Successfully Installed. ucd-snmp package is not installed on your system. Please ensure that you install this package before using any SNMP related features of Novell eDirectory (8.7.0) . Please refer to the admin_guide.pdf for more details. %% Novell eDirectory Server packages successfully installed. %% Novell eDirectory Administration Utilities packages successfully installed. %% Use "ndsconfig" to configure Novell eDirectory Server. %% Please update following environment variables to use LDAP tools from Novell - PATH=/usr/ldaptools/bin:$PATH MANPATH=/usr/ldaptools/man:$MANPATH %% Please go through ../readme.txt carefully before using the product. [root@linux setup]# ndsconfig new -t DW_TREE -o 80 -O 443 -a admin.DW Enter the password for admin.DW: Re-enter the password for admin.DW: Enter server context[org]:dw Starting the service 'ndsd'... Done. Configuring eDirectory with following parameters Admin name = admin.DW Tree name = DW_TREE Server Context = dw dibdir path = /var/nds/dib Searching for Duplicate Tree Name in the network. Please wait... Installing Novell eDirectory Server ... Novell eDirectory Server successfully installed on this system. Extending schema... For more details view schema extension logfile: /var/nds/schema.log Schema extended successfully. Configuring SAS service ... Successfully configured SAS service Nov 10 16:56:22 Could not set the preferred server LINUX Configuring LDAP Server with default SSL CertificateDNS certificate Done Restarting ndsd to load the tree key Stopping the service 'ndsd'... Done. Starting the service 'ndsd'... Done. [root@linux setup]# ps -ef | grep ndsd root 27255 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27257 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27258 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27259 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27260 1 9 16:53 ? 00:00:30 /usr/sbin/ndsd root 27261 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27262 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27263 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27264 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27265 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27266 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27267 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27268 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27269 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27270 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27272 1 10 16:53 ? 00:00:32 /usr/sbin/ndsd root 27273 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27275 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27277 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27278 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27279 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27314 1 0 16:54 ? 00:00:00 /usr/sbin/ndsd root 27315 1 0 16:54 ? 00:00:00 /usr/sbin/ndsd root 27430 7667 0 16:58 pts/0 00:00:00 grep ndsd [root@linux novel]# ./pinstall.lin To accept this license agreement, please enter 'Y': y Pervasive not found. Installing it now! Pervasive SQL server 2000 installed. Now installing NetMail 3.1. Please wait while nimsext loads Nov 10 17:04:39 Could not set the preferred server LINUX At this point it asks me to: ************************************************************** Login as the administrator Administrator name: Password: ************************************************************** I enter the user name admin.DW and password that I thought I had set up with the ndsconfig and I get ************************************************************** Login failed, try again? -Yes No ************************************************************** I do not have any other user name and password for an administrator. I tried entering the root password for the linux system and that did not work either. If I select No then it goes into a loop as below and I have to kill it. Assigning Pervasive rights Your installation is now complete. Thank you for using NetMail 3.1! The NetMail team. Starting NetMail Starting NetMail: [root@linux novel]# Nov 10 17:12:56 Could not set the preferred server LINUX DDB: Logged in with 'Public' identity. Functionality may be limited. (This message is OK if the schema has not been extended yet) [root@linux novel]# No agents configured Module rBåÿ¿sZBrB¬åÿ¿Äq(@Pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ died. Restarting. Starting: rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ Load Error: No such file or directory Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ [test-receiver@linux init.d]$ ps -ef | grep ims root 27799 1 0 17:13 ? 00:00:00 /usr/local/nims/bin/ims kill -9 27799

1 0

Should the "e-mail" attribute be mandatory for the "person" object?
by Thor Kottelin 07 Nov '03

07 Nov '03

Folks, Email is the preferred communication medium when troubleshooting internetworking problems. Time and time again, "inetnum" objects with no valid email address cause grief. In the absence of relevant "e-mail" attributes, desperate administrators sometimes send mail to addresses found in "changed" and "notify" attributes. Sometimes the only option left is resorting to telephone calls, regardless of the expenses, time differences and language barriers often involved. I would therefore like to suggest making the "e-mail" attribute mandatory for the "person" object. If this isn't acceptable, then maybe at least one of the "person" or "role" objects referred to by an "inetnum" object should carry an "e-mail" attribute. Additionally, in order to enhance address validity, I would like to suggest performing some kind of validation on these "e-mail" attribute values - perhaps simple syntax checking, or maybe even full round-trip SMTP testing, or something in between. Your comments, please. Thor -- http://thorweb.anta.net/

5 7

Maintenance on RIPE Whois Server, 10 November 2003
by DB-News 07 Nov '03

07 Nov '03

Dear Colleagues, [apologies for duplicate messages] Next Monday, 10 November 2003, we need to perform a maintenance work on the RIPE Whois Server to replace a faulty piece of hardware. During the maintenance work, - Whois Database updates will be stopped, - all update mails to <auto-dbm(a)ripe.net> will be queued to be processed later, - Webupdate and syncupdate interfaces will be unavailable, - The whois queries will _not_ be interrupted. The maintenance work will start at 12:00 UTC (13:00 Amsterdam time) on 10 November 2003 and expected to last 2 to 3 hours. We apologise for the convenience caused. Please do not hesitate to contact <ripe-dbm(a)ripe.net> for any questions. Best regards, -- Engin Gunduz RIPE NCC

1 0

RE: [db-wg] Should the "e-mail" attribute be mandatory for the "p erson" object?
by Titley, Nigel 03 Nov '03

03 Nov '03

Thor Kottelin wrote: > Folks, > > Email is the preferred communication medium when troubleshooting > internetworking problems. Time and time again, "inetnum" > objects with no > valid email address cause grief. In the absence of relevant "e-mail" > attributes, desperate administrators sometimes send mail to > addresses found > in "changed" and "notify" attributes. Sometimes the only > option left is > resorting to telephone calls, regardless of the expenses, > time differences > and language barriers often involved. The argument against making the email attribute mandatory has always been the bootstrapping problem... In the olden days (defined by my children as "when Daddy was young") it was genuinely possible for a person in the RIPE database to not actually have an email address during the setting up phase of a LIR. I would however agree with Thor, that this circumstance no longer exists. Anyone can get a temporary email address, hotmail via the local cybercafe, if nothing else, to tide them over the bootstrapping period. > > I would therefore like to suggest making the "e-mail" > attribute mandatory > for the "person" object. If this isn't acceptable, then maybe > at least one > of the "person" or "role" objects referred to by an "inetnum" > object should > carry an "e-mail" attribute. Additionally, in order to enhance address > validity, I would like to suggest performing some kind of > validation on > these "e-mail" attribute values - perhaps simple syntax > checking, or maybe > even full round-trip SMTP testing, or something in between. > > Your comments, please. > > Thor ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. **********************************************************************

1 0