- db-wg - mailman.ripe.net

results on Ripe Database
by Helen Dagerus 08 Sep '97

08 Sep '97

Greetings, This matter may already have been discussed here in the Ripe Database groupe, but I am a new arrival. Ripe´s Database for searching IPaddresses goes fine, but if you (like a LIR) wants to find out if the customer (that requests for address space) already have a range of addresses it´s very difficult to find out. My wish is that you can search for "company name". You can sometimes get a hit on "company name", but it is not often. What we do now is that we save down the database and there we can search for more details, like ompany name, administrative contact and so on. Have you some suggestion about what you can do about this? Kind Regards Helen Dagerus ---------------------------------------------------------- Tele2/SWIPnet NetCom Systems Tel: +46 8 5626 4000 Box 62 Fax: +46 8 5626 4210 S-164 94 Kista Email: dagerus(a)swip.net Sweden http://www.tele2.se/ ----------------------------------------------------------

3 3

Database proposal
by TOB 08 Sep '97

08 Sep '97

Dear Database group At present the RIPE database is quite open, which means that it potentially can be used as a marketing database. My proposal is that only allocations are shown to everyone e.g the 195.41.0.0 /16 below. There is sufficient information to contact the provider in e.g hacker cases. The idea is that only the provider and RIPE(and of course the customer itself) knows the individual assignments. It should be implemented by hiding individual assignments in the RIPE database for everyone. If a provider does not take a proper action in e.g hacker cases RIPE should have the right to identify who the exact user of e.g a /24 is. Best Regards Torben Bajlum Tele Danmark inetnum: 195.41.0.0 - 195.41.255.255 netname: DK-TELEDANMARK-961204 descr: Provider Local Registry descr: Tele Danmark Datacom country: DK admin-c: KBO1-RIPE tech-c: TB15-RIPE tech-c: CIN1-RIPE status: ALLOCATED PA mnt-by: RIPE-NCC-HM-MNT changed: hostmaster(a)ripe.net 961204 source: RIPE route: 195.41.0.0/16 descr: Tele Danmark origin: AS3292 mnt-by: AS3292-MNT changed: Torben.Bajlum(a)datacom.dk400.dk 961204 source: RIPE According to my proposal the information below should NOT be available to everyone: inetnum: 195.41.47.0 - 195.41.47.255 netname: AARHUS-STIFTSTIDENDE-NET descr: Aarhus Stiftstidende descr: Olof Palmesalle 39 descr: 8200 Aarhus N country: DK admin-c: BR286-RIPE tech-c: BR286-RIPE changed: pha(a)datacom.dk400.dk 970418 source: RIPE

3 2

Unsubscribing
by Ruth Guthrie 26 Aug '97

26 Aug '97

I wonder if you can help me unsubscribe my late husband, Dave Guthrie, from the Ripe mailing list. Dave died in March of this year, and in May I sold our shares of Technocom plc to the Easynet Group. Dave's e-mail address was dave(a)technocom.co.uk. Since his death, incoming messages have been routed to me at ruth(a)technocom.co.uk (until the sale of Technocom) and at the.guthries(a)worldnet.att.net (since May). There have also been occasional uses of @technocom.com and @technocom.net, just to confuse the issue further. If you are able to unsubscribe him, I would appreciate it. If not, have you any advice about how I would do so? Many thanks for your help... Ruth Guthrie

1 0

Bug in database software.
by RIPE Database Administration 22 Aug '97

22 Aug '97

Dear Colleagues, This message is to report a bug in the database software. If you send in an update of a route object in the classful net notation (e.g. 193.0.0.0) instead of the classless representation, you will get a warning message indicating that the route was rewritten to 127.255.255.255/24. You should find that you can lookup the original route object in the database. You should also find that you cannot lookup the new spurious route object, 127.255.255.255\24. You should do the following: (1) update your original route object using the classless notation; (2) delete the 127.255.255.255\24 object; you will find it in the acknowledgement you received from the first update. We will fix this problem as soon as possible. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

1 0

Power Tool For Webmasters
by powertools＠cybertools.net 06 Aug '97

06 Aug '97

With over 30 million documents on the Web today, and thousands more being added almost hourly, it is now harder than ever for potential customers to find your place on the Net. Which is why we've developed the Web Promotion Spider for Windows 95 / NT . This amazing new software automatically submits your site to over 250 (the list grows daily) major search engines, directories, and Usenet newsgroups! Not only that, The Web Promotion Spider has the ability to dynamically optimize your website, ensuring maximum visibility on the Internet - at the same time recording all registration data in a built in database. Originally engineered for use by the professional advertising industry, this program is easy and intuitive to use. Beginners will be amazed at how simple it is to take complete control over their search engine and index marketing efforts. But don't be fooled by its simplicity! The Web Promotion Spider is an industrial strength marketing tool and an extremely valuable part of any on-line publicity campaign. With this kind of power, it should come as no surprise that many of our customers have built profitable on-line promotional businesses with this product and their existing Internet connection! But don't just take our word for it. The Web Promotion Spider is available now for FREE immediate download on a limited trial basis (shareware). Visit http://www.cybertools.net/spider /////////////////////////////////////////////////////////////////////////////// If you wish to be removed from future mailings, please reply with the subject "Remove" and this software will automatically block you from future mailings. ////////////////////////////////////////////////////////////////////////////////

1 0

Power Tool For Webmasters
by powertools＠cybertools.net 29 Jul '97

29 Jul '97

With over 30 million documents on the Web today, and thousands more being added almost hourly, it is now harder than ever for potential customers to find your place on the Net. Which is why we've developed the Web Promotion Spider for Windows 95 / NT . This amazing new software automatically submits your site to over 250 (the list grows daily) major search engines, directories, and Usenet newsgroups! Not only that, The Web Promotion Spider has the ability to dynamically optimize your website, ensuring maximum visibility on the Internet - at the same time recording all registration data in a built in database. Originally engineered for use by the professional advertising industry, this program is easy and intuitive to use. Beginners will be amazed at how simple it is to take complete control over their search engine and index marketing efforts. But don't be fooled by its simplicity! The Web Promotion Spider is an industrial strength marketing tool and an extremely valuable part of any on-line publicity campaign. With this kind of power, it should come as no surprise that many of our customers have built profitable on-line promotional businesses with this product and their existing Internet connection! But don't just take our word for it. The Web Promotion Spider is available now for FREE immediate download on a limited trial basis (shareware). Visit http://www.cybertools.net/spider /////////////////////////////////////////////////////////////////////////////// If you wish to be removed from future mailings, please reply with the subject "Remove" and this software will automatically block you from future mailings. ////////////////////////////////////////////////////////////////////////////////

1 0

RIPE Database: New format for reply messages
by Chris Fletcher 21 Jul '97

21 Jul '97

As announced last week the RIPE database mail interface is now using a new format for replies. Please let ripe-dbm(a)ripe.net know of any problems or suggestions. Regards, Chris Fletcher - RIPE NCC

1 0

Is Your Web Site A Secret?
by owl＠owlsnest.com 18 Jul '97

18 Jul '97

Is your web site the best kept secret on the Internet? We'll promote it to 50 search engines and indexes for $85 and complete the job in 2 business days. Satisfaction is guaranteed! If you have a great product, but are not getting many inquiries from your Web site, you may not be adequately listed on the Web's search engines and indexes. Millions of viewers daily use these facilities to find the products and services they are looking for. But if your site is not listed, no one will see it. Listings on most of these services are free. However, locating and filling out the forms required to get a listing can take several days, and most people just don't have the time to do it. That is why we offer a web site promotion service. WHAT'S THE DEAL? We will submit your site to 50 indexes and search engines for $85. We will accept the return of this E-mail, with the form below filled out, as an order. We will bill you upon completion of the promotion. Our terms are net 15 days from date of invoice. Satisfaction guaranteed! HOW LONG WILL IT TAKE? Generally, we complete the submissions within 48 hours of receiving your order. It can take any individual search engine or index up to three weeks to process your submission, although most are much faster. WHAT SEARCH ENGINES AND INDEXES ARE INCLUDED IN THE PROMOTION? The list changes from time to time. This is our current list: Abaweb!, Alta Vista, Been There, BizWeb, Central Source Yellow Pages, Enterpreneurs on the Web, Excite, Four11, Galaxy, I-Network I-Systems Spiral Business Directory, I-World Web Pointer, Infoseek, Inktomi, Innovator's Network Yellow Pages, Internet Mall, Jayde Online Directory, Jumpcity, Jumper Hot Links, Linkmaster, Lycos, Magellan, Mega Mall, Net-Happenings, Net Navigator, Net Mall, NTG's List, NYNEX Big Yellow, One World Plaza, OnLine's WWWeb Index, Rex, Starting Point, Truenorth, URL Tree, Virtual Lynx, Web Point, WebCentral, Web Venture Hotlist, Webcrawler, Websurf, Win Mag/NetGuide Hotspots, WhatUSeek, Worldwide Announce Archive, WWW Business Yellow Pages, World Wide Yellow Pages, WWW Worm, YelloWWWeb. HOW WILL I KNOW THAT YOU HAVE PROMOTED MY SITE? When we have completed the promotion, we will send you an HTML file as an attachment to your E-mail bill. Save this file to your disk, and view it through your Web browser. It provides links to the search engine we submitted your site to, plus any comments we received from them when we did it. ARE THERE ANY GUARANTEES? We do not require prepayment. Your satisfaction is guaranteed or you don't pay the bill. WHO IS OWL'S EYE PRODUCTIONS? We are a web site promotion company located at: Owl's Eye Productions, Inc. 260 E. Main Street Brewster, NY 10509 Phone: (914) 278-4933 Fax: (914) 278-4507 Email: owl(a)owlsnest.com HOW DO I ORDER? The easiest way to order is by e-mail. Just hit the REPLY button on your e-mail program and fill out the following information. (This information will be posted to the search engines/indexes): Your name: Company Name: Address: City: State/Prov: Zip/Postal Code: Telephone: Fax: Email address: URL: http:// Site Title: Description (about 25 words): Key words (maximum of 25, in descending order of importance): Proofs (Where shall we e-mail proofs): If billing a different address, please complete the following: Addressee: Company Name: Address: City: State/Prov: Zip/Postal Code: Telephone: Fax: Email address: We will bill via Email. (7519) Terms: By returning this document via Email, you agree as follows: You have the authority to purchase this service on behalf of your company. Terms are net 15 days. Accounts sent to collections will be liable for collection costs. You agree to protect and indemnify Owl's Eye Productions, Inc. in any claim for libel, copyright violations, plagiarism, or privacy and other suits or claims based on the content or subject matter of your site. WHAT HAPPENS NEXT? When we receive your order, we will input the information into our system, and send you a proof. After we process any corrections, we will run your promotion, capturing any comments from search engines as we go. We will incorporate these into an HTML-formatted report to you, which we will attach to your bill. ===Web Promotions=====Press Releases=====Link Exchanges========= Owl's Eye Productions, Inc. 260 E. Main Street Brewster, NY 10509 Ph: 914-278-4933 Fx: 914-278-4507 E-mail: owlseye(a)owlsnest.com

1 0

New format for notifications from RIPE Database.
by RIPE Database Administration 14 Jul '97

14 Jul '97

Dear Colleagues, To give more time to users who wish to modify scripts, the new format for notification messages from the RIPE Database will be implemented on Monday, 21 July. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

1 0

Cross Notification in the Routing Registry
by Carol Orange 11 Jul '97

11 Jul '97

Dear all, The following describes a mechanism for "Cross Notification in the Routing Registry" to be implemented shortly at the RIPE NCC. The mechanism has been modified to incorporate the feedback received during RIPE 27. Appended is a short history explaining how the proposal reached its current form. If this mechanism is of interest to you, please review the document and send any comments or questions you may have to myself. Unless we hear show stoppers, we will start the implementation in the week of July 21, 1997. Greetings, Carol Orange, RIPE NCC -------------------------------------------------------------------- Cross Notification in the Routing Registry Carol Orange, July 1997 Suppose you register the announcement of a route covering some /24. When you make the announcement, it may be useful to know that the /24 has already been registered as being announced in another AS. Alternatively, if a user of a /24 which is announced by you decides to become multi-homed, it may be of interest to you. Overlapping routes are often unintentionally announced in a single AS, and a mechanism for detecting such errors would certainly be handy. In the following, we propose a simple cross notification mechanism which will allow routing registry users to be notified of overlapping route announcements in the Routing Registry (RR). Consider the route object: route: [mandatory] [single] [primary/look-up key] descr: [mandatory] [multiple] [ ] origin: [mandatory] [single] [primary key] hole: [optional] [multiple] [ ] withdrawn: [optional] [single] [ ] comm-list: [optional] [multiple] [ ] advisory: [optional] [multiple] [ ] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] To address the considerations above, we propose the following notification mechanism be implemented in the Routing Registry: 1. Whenever a route object is added to the routing registry, a check is done to see if the address space overlaps with that in any other route object in the RR. If so, a notification will be sent to the submitter of the route object. This will always happen and is not dependent on any notification attributes described below. 2. A new field called "cross-nfy:" will be added to the route and aut-num objects. This field: a) contains a contact reference, specified as either + a NIC-handle pointing to a person or role object, the email address of which will get the notification; or + a mntner ID referencing the maintainer to be notified; b) is optional; and c) is multiple (so that more than one contact can be notified). This attribute is used to request notifications of the addition or removal of route objects which overlap the address space of the already registered route objects in which this attribute is specified. If the "cross-nfy:" attribute is used in: + a route object, then a notification will be sent for any overlaps with the address space specified in the route object; + an aut-num object, then a notification will be sent for overlaps with the address space specified in each route object in which the given AS number is specified in the "origin:" attribute. The contact in "cross-nfy:" will receive an e-mail whenever: + a route is registered which overlaps this address space; or + a route is removed which overlapped this address space. If all is well, the former will indicate the introduction of multi-homing, and the latter will indicate the cancellation of the multi-homing. It is expected, however, that the former will often indicate an error, and the latter its removal. Either way, it will be useful to know about the registration and elimination of overlapping announcements. Some Important Notes -------------------- 1. At the time of implementation, the notification may take up to 24 hours, due to the current mirroring scheme employed in the RR. This time will be reduced when the mirroring scheme is improved. 2. Exact address space matches will be distinguished from non-exact overlaps in the notification messages. 3. After the implementation of RPSL, it will be useful to allow one or more route-sets to be specified in the "cross-nfy:" attribute in addition to the contact reference. For example, using: cross-nfy: <ContactA> <route-set1> <route-set3> cross-nfy: <ContactB> <route-set2> in an aut-num object would allow ContactA to be notified upon registration and deletion of routes overlapping the address space covered in <route-set1> and <route-set3> and ContactB to be notified with regards to route registrations with address space overlapping that covered in <route-set2>. In this way, a more selective notification scheme can be specified without adding "cross-nfy:" to every route object. Acknowledgements ---------------- Thanks to the RIPE Routing and Database working groups for lively discussions resulting in constructive input on this notification mechanism. Daniel Karrenberg was the first to mention the need for a notification mechanism in the RR. Chris Fletcher, Joachim Schmitz and Wilfried Woeber have all made essential contributions. ------------- ------------- ------------- ------------ ------------- Appendix - Some History At the January meeting of the Routing WG in Amsterdam, various possible hierarchies for authorization in the Routing Registry (RR) were considered. During the discussion, a suggestion was made that "hierarchical notification" would be useful even in cases where authority is not well defined. This suggestion enjoyed strong support of both the Routing WG and the Database WG. At the start of May 1997, a proposal was submitted to the mailing lists of the RIPE Routing and Database WG's describing a notification mechanism designed to meet the stated requirements. During the RIPE meeting in Dublin, it was agreed to that the notification mechanism should be implemented, with the following modifications: 1. Whenever a route object is submitted in the RR, a notification should be generated to the submitter if the address space overlaps with any other route object in the RR. [RIPE27 - Routing WG meeting] 2. The attribute should be named "cross-nfy:" rather than "x-notify:" to avoid any misunderstandings with respect to other conventions. In particular, mailers often interpret "X-field:" to mean "ignore this field". [private discussion Chris Fletcher] 3. If the address space covered in the route object matched the address space in another route object, be sure this is clear in the notification message. [RIPE27 - Routing WG meeting] 4. - Notifications should be sent to the appropriate contact not only if an overlap is introduce, but also when an overlap is eliminated. [RIPE27 - Routing WG meeting] 5. The "cross-nfy:" field should be available for the "aut-num:" object as well as for the routing object. If "cross-nfy:" is in the "aut-num:" object, it applies to all routes with that aut-num as origin. [RIPE27 - Database WG meeting] It has since been suggested that it would be useful if the mechanism would be extensible for the "route-set:" objects defined in RPSL (see draft-ietf-rps-rpsl-02). To make use of the route grouping functionality supplied by the "route-set:" object, we suggest the following extension be considered: 6. In the "aut-num:" object, allow "cross-nfy:" to be a multiple attribute, and in addition to specifying who should be notified, specify for which route-sets. If no route-sets are specified, then the notification will take place for all route objects with the given "aut-num:" as origin. [private discussion Joachim Schmitz]

1 0