If my assumptions are correct, the point being made here is that the RIPE NCC is being questioned over the use of funds, generated from the LIRs, to support other organisations. In this case the ICANN. While it would be interesting to know the sum paid by the RIPE NCC to ICANN, as outlined in the document below, the matter is already under focus, and the remaining 50% of the contribution is not going to be paid unless the Executive Board says otherwise. If other participants of this forum agree that contributions to ICANN should be suspended, then those people need to voice their opinions to ensure the Executive Board don't change their minds. I, for one, haven't looked closely into the operations of ICANN, but if the general opinion is that, 'the RIRs can fulfil their mission without ICANN.', then I am happy to accept that judgement. The full document for the 29th Meeting of the RIPE NCC Executive Board can be found here: http://www.ripe.net/ripencc/about/board/minutes/twenty-nine.html Financial information relating to ICANN can be found here: http://www.icann.org/financials/ One document that caught my attention was the Report of Expense Reimbursement and Other Payments to ICANN Directors: http://www.icann.org/financials/director-expenses-fye2002.htm Chris -----Original Message----- From: Jim Fleming [mailto:JimFleming@ameritech.net] Sent: 27 November 2002 02:37 To: lir-wg@ripe.net Subject: [lir-wg] "...need to raise funding for first half of 2003..." How much does RIPE currently pay to ICANN ? http://www.dnso.org/clubpublic/council/Arc11/msg00184.html (3) The ICANN budget will not support much funding for the GNSO in first half of 2003, so our budget assumptions are still valid (ie the GNSO will need to raise funding for first half of 2003). ===== ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. **********************************************************************