- db-wg - mailman.ripe.net

Changes for abuse
by dfoley 15 Jul '05

15 Jul '05

This document is very confusing. The section : "(3) Adding 'abuse output' Option " describes the changes to the result returned for "$ whois 10.0.0.10". However the result displayed is actually the result before the change. This is followed by a description of the result of "$ whois -b 10.0.0.10". The result includes "e-mail:" attributes but no "abuse-mailbox:" attribute. So which request do I use to obtain the "abuse-mailbox:" attibute? . In your examples it is only returned with the "$ whois -L 10.0.0.10". And yet I am supposed to use the "$ whois -b 10.0.0.10" to get the abuse contacts. Should I expect to ignore the attributes and treat any email address returned with the "whois -b" request as an abuse contact? I have tried using the "whois -b" and I have yet to get a result without ERROR appearing.

2 1

Status of 'org' attribute
by MarcoH 13 Jul '05

13 Jul '05

[appologies for cross-posting this] Hi all, Maybe I missed out on something, but accoording to various templates in the ripe-databese, the org-attribute is optional. Apparently the hostmaster mailrobot things otherwise and refuses requests with an error because of the org-attribute not being present. I just ran into it on a ASN request, but I recall having problems before with this. Can anybody tell me who is right, the database template or the robot ? In fact, the database reference (http://www.ripe.net/ripe/docs/databaseref-manual.html#1.2.3) doesn't list it all. Grtx, MarcoH

2 2

RE: [db-wg] Trouble inserting inetnum inetnum object.
by Ramarajan, Arvind, ALABS 12 Jul '05

12 Jul '05

Tobias, Yup, that was the problem. ALLOCMNT in rip.config was not pointing to the wrong mntner. Regarding allocating a /25, I had the same problem even allocating 10/8. Thanks to all who responded. Thanx --> Arvind. -----Original Message----- From: Tobias Cremer [mailto:tcremer@de.cw.net] Sent: Tuesday, July 12, 2005 4:12 AM To: Ramarajan, Arvind, ALABS; db-wg(a)ripe.net Subject: Re: [db-wg] Trouble inserting inetnum inetnum object. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Arvind, Daniel Roesen wrote: > On Mon, Jul 11, 2005 at 02:10:52PM -0500, Ramarajan, Arvind, ALABS wrote: >>***Error: ALLOCATED inetnum objects require the RIPE NCC maintainer > > Make this status "ASSIGNED PA". correct - however, if you really want to create a ALLOCATED PA object (which is rather unlikely for a /25 :-) ), you have to use the mntner that is defined in rip.config to be allowed to created allocation objects. Have a look there for the ALLOCMNT section. Regards: Tobias - -- Tobias Cremer M.A. IP Admin Engineer Cable & Wireless Telecommunication Services GmbH Landsbergerstr. 155 80687 Muenchen Germany Tel +49 89 926 99 0 -- FAX +49 89 926 99 180 -- COMNET 7 49 9169 www.cw.com/de - -- Every message GnuPG signed -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFC03tfhC6y11CNwvcRAuv4AKCO9mghpONbgXmldjcGYs3N5IA5iwCfTu3i P3rdrbFnUgkHEVx/8JnT0Qs= =2V6/ -----END PGP SIGNATURE-----

2 1

Trouble inserting inetnum inetnum object.
by Ramarajan, Arvind, ALABS 12 Jul '05

12 Jul '05

Hi, I have an internal RIPE DB instance to which 'am not able to add a new inetnum object. Following the e-mail reply I get after submitting a e-mail request: SUMMARY OF UPDATE: Number of objects found: 1 Number of objects processed successfully: 0 Create: 0 Modify: 0 Delete: 0 No Operation: 0 Number of objects processed with errors: 1 Create: 1 Modify: 0 Delete: 0 Syntax Errors: 0 DETAILED EXPLANATION: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following object(s) were found to have ERRORS: --- Create FAILED: [inetnum] 10.122.0.0 - 10.122.0.127 ***Info: Syntax check passed inetnum: 10.122.0.0 - 10.122.0.127 netname: SUBNET1-LOOPBACK0 descr: Loopback0 addresses country: US admin-c: AR1-ATTIR tech-c: HK1-ATTIR status: ALLOCATED PA notify: aramarajan(a)att.com mnt-by: MNT-ATTIR mnt-lower: MNT-ATTIR changed: aramarajan(a)att.com source: ATTIR ***Warning: Date '20050711' added to changed: attribute 'aramarajan(a)att.com' ***Error: ALLOCATED inetnum objects require the RIPE NCC maintainer The person (AR1-ATTIR and HK1-ATTIR), role and mntner (MNT-ATTIR) refereffed above have already been loaded using make_db from a flat file similar to sample.db.gz. Any help appreciated. Thanx --> Arvind.

4 3

DNSSEC deployment on the reverse tree.
by Olaf M. Kolkman 06 Jul '05

06 Jul '05

[Apologies for duplicates] Dear Colleagues The RIPE NCC has been involved with the development of the DNSSEC protocol. Now that the protocol has become available, we plan to implement DNSSEC on our domains in the reverse DNS tree. The deployment of DNSSEC is the second and last phase of the Reverse DNS restructuring project. You can find more information about this project at: http://www.ripe.net/rs/reverse/dnssec/index.html To implement DNSSEC, we propose extending the policy for Policy for Reverse Address Delegation of IPv4 and IPv6 Address Space in the RIPE NCC Service Region. You can find the proposed policy at: http://www.ripe.net/rs/reverse/dnssec/draft-dnssec-policy.html. We welcome your feedback on this poposal before 1 August 2005. Please send your comments to the DNS Working Group Mailing List. We are also introducing two new procedures: "DNSSEC Key Maintenance Procedure" http://www.ripe.net/rs/reverse/dnssec/key-maintenance-procedure.html and "Procedure for Requesting DNSSEC Delegations" http://www.ripe.net/rs/reverse/dnssec/registry-procedure.html Your feedback on these drafts is also welcome, again please send this to the DNS Working Group Mailing List. As part of the "Procedure for Requesting DNSSEC Delegations" we plan to add a "ds-rdata:" attribute to DOMAIN objects. Regards Olaf M Kolkman New Projects, RIPE NCC.

2 1

Proposed changes for object ordering
by Imro San 05 Jul '05

05 Jul '05

When will the new proposal be available and how? Licensed Sygate User

1 0

RIPE51: EOF Stream/Plenary presentations from the DB-WG Camp
by Wilfried Woeber, UniVie/ACOnet 01 Jul '05

01 Jul '05

Dear DB-WG subscribers! We expect the next RIPE Meeting (RIPE51 @ AMS) to be structured very much like RIPE50 (aka the "new format" :-) At the end of August 05, the Chair of RIPE and the meeting planners, together with the WG chairs, would like to review (the better part of) the EOF/Plenary Stream contributions. In order to avoid being paralized by many people being out of office during summer, I'd like to distribute this call for presentations for the Plenary from the DB-WG environment. If you intend to offer a presentation, or would like to see a particular presentation at RIPE51, please spaek up now - either to me directly or to the WG list. This is just an early warning, please expect a formal call for contributions. Thanks, and have a nice summer and relaxing vaction period! Wilfried.

1 0

mnt-routes bugs
by Daniel Roesen 29 Jun '05

29 Jun '05

Hi, instead of spending developer time on poem/limerick objects, could we please get all the mnt-routes and other authorization bugs fixed, like: http://www.ripe.net/bugzilla/show_bug.cgi?id=118 http://www.ripe.net/bugzilla/show_bug.cgi?id=136 http://www.ripe.net/bugzilla/show_bug.cgi?id=137 and today I might have found a possible bug that is similar to 118, but IPv6: ***Warning: The parent [route6] 2001:5000::/21AS1273 has invalid prefix ranges in "mnt-routes:" attribute(s): 2001:5001:103::/48 The object has: route6: 2001:5000::/21 ... mnt-routes: CLUE-MNT {2001:5001:103::/48} I'm trying to create route6 2001:5001:103::/48. Is the mnt-routes syntax used wrong? Best regards, Daniel -- CLUE-RIPE -- Jabber: dr(a)cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0

2 1

whois lookup limits
by Hank Nussbacher 28 Jun '05

28 Jun '05

What are the current limits on whois lookups and how does one get a specific IP changed? I have someone getting "ERROR:202: access control limit reached for x.x.x.x" Thanks, Hank

2 2

Re: The Cidr Report
by Hank Nussbacher 22 Jun '05

22 Jun '05

On Wed, 22 Jun 2005, Geoff Huston wrote: One potential problem: ERX data. I am looking at all the Israeli entries for example, from 192.114.x.x-192.118.x.x You will find it in RIPE whois, but you won't find it in the RIPE stats file since the block was ERXed as were probably many others. Not sure how you can handle that. Regards, Hank > cleared up BUT changed in one important respect: > > If an entry isin the RIPE whois database but NOT in the RIPE stats file I'm > marking it as potentially bogus. I would like to see the RIPE stats file be > an accurate picture of RIPE managed address space, and the database is > completely unreliable :-( > > Geoff > > > > At 01:08 AM 18/06/2005, Hank Nussbacher wrote: > > >I was hoping the report would be cleaned up by now but it hasn't so sorry > >for the multiple list post. The Bogon section is IMHO, broken. > > > >Taking just the 1st line as an example: > >Prefix Origin AS AS Description Unallocated block > >3.0.0.0/8 AS80 GE-CRD - General Electric Company 0.0.0.0 - 3.0.0.0 > > > >3.0.0.0/8 is allocated, as is AS80. I suspect the algorithm, which > >determines the unallocated block of 0.0.0.0 - 3.0.0.0 to be somewhat > >broken. > > > >There are thousands of lines like that. > > > >The bogus AS section also appears to be broken. > > > >-Hank > > > > +++++++++++++++++++++++++++++++++++++++++++ > This Mail Was Scanned By Mail-seCure System > at the Tel-Aviv University CC. >

3 3