From henk at ripe.net Fri Jul 18 15:27:51 2008 From: henk at ripe.net (Henk Uijterwaal) Date: Fri, 18 Jul 2008 15:27:51 +0200 Subject: [ncc-services-wg] IPv6 enabled for email to the RIPE NCC Message-ID: <48809A57.8040201@ripe.net> Dear Colleagues, On Wednesday, 16 July, the RIPE NCC's new mail servers were enabled. As of this date, it is possible to send mail to the RIPE NCC with IPv6 as a transport medium. This setup has been extensively tested but if you see any problems, please send an e-mail to or phone +31 20 535 4444. Kind regards, The RIPE NCC -- ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Is one of the choices leaving the office open? Alan Greenspan on the next elections From laurentz at student.ethz.ch Mon Jul 21 13:28:38 2008 From: laurentz at student.ethz.ch (Laurent Zimmerli) Date: Mon, 21 Jul 2008 13:28:38 +0200 Subject: [ncc-services-wg] Locally caching riswhois results Message-ID: Hi list I'm making use of the riswhois service and would like to cache queries locally. However, I am not sure whether I can do it the way I want to. My idea is to store the ASN an the corresponding route of each query I execute. Before performing another query I would then check whether I already stored the ASN of a route which contains the IP for which I want to find the AS. Can I do that? Or is then the following case possible: I store an AS an its route -- say ASx, 123.0.0.0/8 -- whose IP range includes another one -- say ASy, 123.100.0.0/16. When I store ASx first and then query an IP of ASy, I will assign ASx to this IP instead of ASy. Is such a case possible? Or is there even another problem with my caching approach? Thanks for your time! Best, Laurent -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhma at mcvax.org Tue Jul 22 12:22:52 2008 From: jhma at mcvax.org (James Aldridge) Date: Tue, 22 Jul 2008 12:22:52 +0200 Subject: [ncc-services-wg] Locally caching riswhois results In-Reply-To: References: Message-ID: <4C7D97C8C499AB55C38165EF@james-macbook-pro.ripe.net> --On 21 July 2008 13:28:38 +0200 Laurent Zimmerli wrote: > I'm making use of the riswhois service and would like to cache queries > locally. However, I am not sure whether I can do it the way I want to. My > idea is to store the ASN an the corresponding route of each query I > execute. Before performing another query I would then check whether I > already stored the ASN of a route which contains the IP for which I want > to find the AS. > Can I do that? Or is then the following case possible: I store an AS an > its route -- say ASx, 123.0.0.0/8 -- whose IP range includes another one > -- say ASy, 123.100.0.0/16. When I store ASx first and then query an IP > of ASy, I will assign ASx to this IP instead of ASy. Is such a case > possible? Or is there even another problem with my caching approach? Yes, overlapping prefixes originating from different autonomous systems do exist in the wild. The problem I see is that when you find a matching prefix in your cache from one particular AS you would return that (or what's the point of the cache) and won't know whether there is a more specific (longer) prefix originating from a different AS which a query to riswhois would return. I can't really see a way around this problem except to use a local copy of the RIS RIB dumps in the same way that riswhois does. James From denis at ripe.net Mon Jul 28 11:48:28 2008 From: denis at ripe.net (Denis Walker) Date: Mon, 28 Jul 2008 11:48:28 +0200 Subject: [ncc-services-wg] RIPE Database legal documents Message-ID: <488D95EC.90600@ripe.net> Apologies for duplicates] Dear Colleagues, The RIPE Data Protection Task Force (DP TF), working with the RIPE NCC and the company lawyers, has finalised a set of legal documents for the RIPE Database. These documents are: - RIPE Database Terms and Conditions - RIPE Database Acceptable Use Policy - Procedure for the Removal of Personal Contact Details from the RIPE Database They can be seen on the RIPE DP TF web page at this address: http://www.ripe.net/ripe/tf/dp/index.html The documents have been subjected to a final review by the DP TF but they are not yet legally effective. They are now available for review and comments by the wider community. Please let us know if you have any considerations or issues. Please bear in mind that with any documents such as these, the wording can always be changed. However, we would prefer not to make any subjective changes at this stage but only amend anything that is inaccurate. The documents will become legally effective from 1 September 2008 and they will then be available on a new Legal Documents page on the RIPE NCC website. Regards, Denis Walker (on behalf of the RIPE DP TF) From ripe-wgs.cs at schiefner.de Mon Jul 28 22:49:49 2008 From: ripe-wgs.cs at schiefner.de (Carsten Schiefner) Date: Mon, 28 Jul 2008 22:49:49 +0200 Subject: [ncc-services-wg] Re: RIPE Database legal documents In-Reply-To: <488D95EC.90600@ripe.net> References: <488D95EC.90600@ripe.net> Message-ID: <488E30ED.2010800@schiefner.de> Denis, Denis Walker wrote: > The documents will become legally effective from 1 September 2008 and > they will then be available on a new Legal Documents page on the RIPE > NCC website. will they also become RIPE documents? If not, why (not)? Best, Carsten