- ncc-services-wg - mailman.ripe.net

Re: [ncc-services-wg] OK, I'm lost...
by Wilfried Woeber, UniVie/ACOnet 18 Aug '04

18 Aug '04

>Peter, if you need to communicate with us, as a non-member, >then ncc(a)ripe.net works, as well as the telephone. Last time when I communicated with ripe-dbm, I think I didn't have to specify my reg.id ;-) Wilfried ( https://cert.aco.net/ ) _________________________________:_____________________________________ 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ...there's no place like 127.0.0.1 (or ::1 ?)

1 0

OK, I'm lost...
by Peter Galbavy 18 Aug '04

18 Aug '04

RIPE-301 (specifically about closed registries) 3.8: "In cases where End Users of an LIR keep the address space assigned to them after the LIR closes, the LIR maintainer in the database objects representing these assignments needs to be removed and replaced by the RIPE NCC maintainer. The LIR should provide the RIPE NCC with a list of relevant database objects agreeing to the RIPE NCC overwriting the current LIR maintainer." OK, I missed this as "my" LIR was closed due to non-payment after my previous "issues". That not-withstanding, the actualy allocations to end-users remain, and should be maintainable, even if very slowly, somehow. RIPE-301 does not (in 4.0) imply that end-user assignments (and ASes) are automatically removed where an LIR is closed by RIPE - in fact it implies the opposite, but doesn't say it explicity. If we get to the situation where the object would have been correctly and timely changed to the NCC maintainer, it appears that the current robot behaviour would still be the same; This page implies that it is *impossible* to communicate with RIPE unless you are an LIR: http://www.ripe.net/ripencc/mem-services/registration/status.html There is a chasm here between RIPE-301 and hostmaster(a)ripe.net etc. Is there a (poublic) solution ? rgds, -- Peter

2 1

RIPE49 - Call for Presentations - NCC-Services WG
by Sanghani, Bijal 05 Aug '04

05 Aug '04

Hi All, For the NCC Services WG at RIPE49 we'd like to see more participation from the members, as well as the general presentation provided by the RIPE NCC. So with that in mind we'd like to ask for you, the members and RIPE Community to come forward and suggest a presentation outlining your experience with the RIPE NCC and its services. This can include anything from experiences you have had with a recent merger or idea's/issues you've had with the LIR Portal that you would like to share. As this Working Group has been set-up explicitly for the RIPE NCC members and the RIPE Community to discuss the services of the RIPE NCC, your active participation is appreciated. Without active involvement of the membership and the RIPE Community it is difficult for the RIPE NCC to gauge our expectations with regards to the services it provides. We would like to encourage anyone that would like to make a presentation or raise a topic for discussion to please contact either Kurtis <kurtis(a)kurtis.pp.se> or myself <bsanghani(a)flagtelecom.com> and we'll arrange a spot in the agenda. Best regards, Bijal Sanghani FLAG Telecom ********************************************************************** 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. You should not copy it or use it for any purpose nor disclose the contents to any other person. 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. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0

RE: [local-ir@ripe.net]Re: AP2005 New Activities
by Wilfried Woeber, UniVie/ACOnet 27 Jul '04

27 Jul '04

>> > 7) Deployment of Anti-SPAM Measures and SPAM Abuse Policies >> > >> > The RIPE NCC will deploy technical facilities to minimise the effect >> > of SPAM and SPAM abuse towards the RIPE NCC and the mailing >>lists it provides for members and the RIPE community. >> >>The abuse-c database work might as well be done under this heading, >>or it might be under its own heading, but as far as I understand, >>it's not listed anywhere here ? Given the current mandate and operational track record of the Anti-Spam WG, I don't think this is the right place to put it (exclusively). While I am aware that a large number of parties tends to equate "abuse" with spam, there are other groups and temas which have a pretty different definition of what network-"abuse" (as opposed to service-/application-abuse) or an "incident" is. >>If RIPE has for some reason choosen to abstain from abuse coordination Abuse (def.?) *coordination* is out of scope for the NCC (as we known it today!) from my point of view. Many years ago there was an attempt to develop such a function in (or alongside) the NCC, which failed miserably - due to lack of support by the RIPE NCC's customer base. Nowadays this niche has been filled in many places, and in different ways, by entities which do not have a close relationship with the NCC or the (registration) services the NCC offers. Trying to retrofit that might prove difficult. >>issues, can you point me into some direction which *does* correlate >>IP to contact information, hopefully under a global scale ? The 4(5) address registries. As long as there is not even consensus to put all relevant registry information into those _central_ repositories for public consumption (rwhois is your enemy ;-), I cannot see how the NCC should try to implement a (reliable?) service on a global scale. As an additional aspect, even within the NCC's service region (or the expanded EU for that matter), there is no uniform framework which satisifies the requirements of both sides in the game: the privacy requirements and the investigative requirements. As an aside, these aspects could be food for thought for the (or a renamed) Anti-Spam WG (and/or the ENISA being set up right now ;-) >>Which is the reason for RIPE to keep away from this ? > >We have not actively decided "to keep away from it", rather we have not >seen strong demand for the RIPE NCC to become active in this area. > >I hope that I have answered your questions sufficiently and look >forward to any further discussion. > >kind regards, > >Axel Pawlik Best regards, Wilfried.

1 0

Re: AP2005 New Activities
by Axel Pawlik 26 Jul '04

26 Jul '04

Dear Colleagues, Thank you for the feedback you have provided to the email announcement of RIPE NCC New Activities for 2005 (sent 12 July 2004). I have provided a response to the queries brought forward in the text below. >>Please find attached a list of new RIPE NCC activities scheduled >>for 2005 and activities that represent a significant change in resource >>allotment from 2004. > >In all sections, can you indicate if the cost includes all components >such as manpower, hardware, software, etc.? Yes. In all cases the full cost such as manpower, hardware, software, etc. are included, and are based on capital expenditure as opposed to yearly depreciation. >1) RIPE NCC Member Service Desk >If today RIPE NCC members contact either a Hostmaster or the >RIPE DBM or some other person, either via email or phone, won't the >level of tickets be reduced for those staff? I ask since it would appear >to me that existing staff can be merely reassigned to handle this new >function with 2-3 PCs, and therefore I don't understand why the financial >impact should be significant. Yes, in principle this service is designed to decrease the load of relevant help queries sent to Hostmaster and RIPE DBM. The financial impact was calculated to include one new FTE plus hardware/software. Other staff needed would re-assigned as you state. A significant amount of the cost brought forward is to cover a new PABX needed to run such a service. It is important to note that this item includes the full capital expenditure of the switch, although it will benefit the entire organisation. >2) Further Deployment of Mirror Instances of the K-root Nameserver > >Why does K root have to pay for this if F root does it all for free: >http://www.isc.org/index.pl?/ops/f-root/sites.php For stability reasons the operation of K global nodes are fully funded by the RIPE NCC. K local nodes are sponsored by the local community. For both classes of nodes the RIPE NCC retains full operational responsibility and control. The global nodes form the core of K-root availability and service. Two of those are currently operational in Europe and two more are planned, most likely one will be deployed in North America and one in Asia. For these nodes long-term operational stability is the primary concern. Long-term contractual arrangements for all operational aspects including facilities management and connectivity are essential to achieve this. Thus for the global nodes all capital and operating expenses are budgeted. In our judgement the expenses budgeted are reasonable to provide the stability of K-root service that is in the interest of the RIPE NCC membership. Should sponsorship opportunities arise that do not compromise the stability goals set out above we will of course pursue them in order to minimise the burden on the RIPE NCC membership. Other root server operators use different ways of deployment and cost recovery. Such diversity is good, because diversity increases the strength of the root server system. > > 3) Improving Data Integrity > > >Will this include some method to cleanup/identify abuse contacts >for spam, attack mitigation etc ? What about some abuse-c tag >for the database ? This issue is currently being discussed in the DB Working Group. We see this as part of the ongoing maintenance and development of the Database and therefore have not listed this as a new activity. > > 7) Deployment of Anti-SPAM Measures and SPAM Abuse Policies > > > > The RIPE NCC will deploy technical facilities to minimise the effect > > of SPAM and SPAM abuse towards the RIPE NCC and the mailing >lists it provides for members and the RIPE community. > >The abuse-c database work might as well be done under this heading, >or it might be under its own heading, but as far as I understand, >it's not listed anywhere here ? > >If RIPE has for some reason choosen to abstain from abuse coordination >issues, can you point me into some direction which *does* correlate >IP to contact information, hopefully under a global scale ? > >Which is the reason for RIPE to keep away from this ? We have not actively decided "to keep away from it", rather we have not seen strong demand for the RIPE NCC to become active in this area. I hope that I have answered your questions sufficiently and look forward to any further discussion. kind regards, Axel Pawlik

1 0

LIR Portal maintenance
by Shane Kerr 19 Jul '04

19 Jul '04

Dear Colleagues, On Monday, 19 July, between 17:00 and 19:00 CEST, there will be maintenance on the RIPE NCC LIR Portal. Expected downtime is two hours. During this period the LIR Portal will be unavailable. We apologise for any inconvenience that this downtime may cause to your operations. Regards, -- Shane Kerr Software Manager RIPE NCC

1 0

RIPE NCC New Activities for 2005
by Axel Pawlik 18 Jul '04

18 Jul '04

Dear Colleagues, [apologies for duplicates] Please find attached a list of new RIPE NCC activities scheduled for 2005 and activities that represent a significant change in resource allotment from 2004. We provide this list as a follow-up to my presentations in the RIPE NCC Services Working Group and at the RIPE NCC General Meeting, in May of this year. By no means is this intended as a representation of the full 2005 Activity Plan or precise associated cost. Instead, this early in the process it is meant primarily to foster discussion and feedback from you to us and the Executive Board to aid our planning and production of the final Activity Plan, Budget and Charging Scheme documents. We envisage a comment period of about four weeks, after which we will commence production of the draft Activity Plan and Budget documents that we will publish in good time prior to the RIPE NCC General Meeting in September (we are aiming for a publication date at the end of August). Based on discussions at the RIPE NCC Services Working Group, the General Meeting, and the respective mailing lists, the Executive Board will formally approve the final Activity Plan and Budget 2005 documents in Q3'2004. According to the revised Articles of Association the members will be formally asked to approve the Charging Scheme 2005 at the General Meeting in September. This document will be published four weeks in advance of the GM according to the formal requirements. I hope personally that the coming weeks will show a further increase in membership involvement in the production of these documents, setting the course for our work over the next year. Regards, Axel Pawlik PS As I am currently on family holidays, my participation in the discussion might be sparse for the next 10 days. ==== New Activities for 2005 For each of the new activities listed below a description is provided as well as an assessment of its financial impact on resources. The following ranges are used to show the financial impact and relative weight of the proposed new activities. Fractional 0 - 50 kEUR Small 50 - 100 kEUR Moderate 100 - 200 kEUR Significant 200 - 400 kEUR Substantial > 400 kEUR 1) RIPE NCC Member Service Desk Feedback received from RIPE NCC Members has revealed a need to consolidate the communication channels members can use to contact the RIPE NCC. To achieve this, the RIPE NCC will create the RIPE NCC Member Service Desk, a convenient single point of contact that will be available through direct email and phone contact. Email will remain the primary means of communication. The aim of the RIPE NCC Member Service Desk is to improve the ease and efficiency with which members can interact with the RIPE NCC. The desk will cover Internet number resource requests and related issues involving RIPE NCC Hostmaster, RIPE Database and RIPE NCC billing queries. This will be in addition to the regular service requests handled by the RIPE NCC Hostmasters and RIPE DBM. The possibility of contacting the RIPE NCC Member Service Desk by both PSTN and IP(VOIP) will be investigated and prepared. Dependent on feedback from RIPE NCC Members, the scope of the RIPE NCC Member Service Desk may be expanded in the long term. Financial Impact: Significant (200 - 400 kEUR) 2) Further Deployment of Mirror Instances of the K-root Nameserver The RIPE NCC will continue to deploy mirror instances of the K-root nameserver. This will further improve the distribution, redundancy and performance of this crucial service as well as its resilience against Denial of Service (DoS) attacks. In 2005 the RIPE NCC will continue deployment of local nodes in the RIPE NCC service region, which will be done on a cost recovery basis. The RIPE NCC will also deploy several (2-3) global nodes in North America and Asia-Pacific. Most of the costs of global node deployment will be covered by the RIPE NCC. Financial Impact: Significant (200 - 400 kEUR) 3) Improving Data Integrity In 2005 the RIPE NCC will focus efforts on improving the accuracy, integrity and consistency of data related to Internet number resources. Mechanisms will be established to ensure higher quality data in the long term, decreasing discrepancies and incorrect contact details and thus increasing the speed at which requests and disputes can be resolved. The improved integrity of data will benefit the Internet community by increasing the reliability of using registration data in the daily operations of LIRs and ISPs. Financial Impact: Moderate (100 - 200 kEUR) 4) Developing New Training Methods To adapt the training offered by the RIPE NCC to the differing needs of the audience, new training methods will be developed, particularly focusing on online training. The intention is to reach a broader audience, particularly those who are unable to attend RIPE NCC training courses due to geographical, financial, scheduling or other constraints. Offering more accessible training will help members to send better-prepared requests to the RIPE NCC Hostmasters. This aims to ensure a more timely completion of allocation requests. In addition, the RIPE NCC will develop new forms of training to specifically target non-traditional audiences such as journalists, politicians and administrators. This is a logical progression of the RIPE NCC's outreach efforts developed over previous years. The aim is to encourage well-informed decisions and to win continued support for the existing RIR framework. Financial Impact: Small (50 - 100 kEUR) 5) Membership Survey The RIPE NCC will commission an independent member and stakeholder survey, similar to the survey conducted by KPMG in 2002. Based on the results of this survey and in close interaction with the members and stakeholders, the RIPE NCC will continue to improve its operational quality and organisational structure. Financial Impact: Small (50 - 100 kEUR) 6) Cross Registry Information Service Protocol (CRISP) Responding to requests from the community for a standard, uniform global view of Internet Number Resources, the RIPE NCC will continue to participate in the IETF process to develop the Cross Registry Information Service Protocol. In 2005, the RIPE NCC will provide server implementation and client tools, while co-ordinating with other server operators, client tool authors, and service providers to encourage use. Financial Impact: Small (50 - 100 kEUR) 7) Deployment of Anti-SPAM Measures and SPAM Abuse Policies The RIPE NCC will deploy technical facilities to minimise the effect of SPAM and SPAM abuse towards the RIPE NCC and the mailing lists it provides for members and the RIPE community. Financial Impact: Fractional (0 - 50 kEUR) --- end

3 2

Re: [dns-wg] Last Warning: Termination of <auto-inaddr@ripe.net>
by Jim Reid 14 Jul '04

14 Jul '04

>>>>> "Olaf" == Olaf M Kolkman <olaf(a)ripe.net> writes: Olaf> As announced previously (e.g. [1]), we will discontinue the Olaf> use of the <auto-inaddr(a)ripe.net> e-mail interface for Olaf> reverse delegation requests as of tomorrow (July 15, 2004). Olaf> From tomorrow, all mails sent to this address will be Olaf> returned to sender. I hope the bounce message tells the sender what email address they should have used or points them at a web page that gives this info.

1 0

Last Warning: Termination of <auto-inaddr@ripe.net>
by Olaf M. Kolkman 14 Jul '04

14 Jul '04

Dear Colleagues, [Apologies for the duplicate messages] As announced previously (e.g. [1]), we will discontinue the use of the <auto-inaddr(a)ripe.net> e-mail interface for reverse delegation requests as of tomorrow (July 15, 2004). From tomorrow, all mails sent to this address will be returned to sender. Reverse delegation requests can only be submitted to the RIPE Whois Database by using the <auto-dbm(a)ripe.net> e-mail interface or by using one of the other update mechanisms such as web-updates[2]. For more information about the authentication mechanism, please see http://www.ripe.net/reverse -- Olaf Kolkman New Projects, RIPE NCC [1] http://www.ripe.net/ripe/mail-archives/dns-wg/2004/msg00042.html [2] Webupdates interface to the RIPE Whois Database. http://www.ripe.net/perl/webupdates.pl If you are reading this or related posts from the archive all occurrences of ripe.net in e-mail addresses have been replaced by localhost -- ---------------------------------| Olaf M. Kolkman ---------------------------------| RIPE NCC

1 0

Registration Deadline - RIPE NCC Regional Meeting, Nairobi 28 - 30 July 2004
by Membership Liaison Officer 12 Jul '04

12 Jul '04

[Apologies for duplicate mails] Dear Colleagues, This is a final reminder that the RIPE NCC Regional Meeting in Nairobi will be held 28 - 30 July 2004 at the Norfolk Hotel in Nairobi, Kenya. Attendance to the RIPE NCC Regional Meeting is free of charge. However, attendees are responsible for covering their own travel and accommodation costs. REGISTRATION Please note that registration for the Regional Meeting closes on 19 July 2004. To register, please see: http://www.ripe.net/cgi-bin/nairobi-reg AGENDA The agenda has recently been updated with more information about speakers and presentations. For the full agenda, please see: http://www.ripe.net/ripencc/regional-meetings/nairobi-2004/agenda.html TRAINING As a part of the Regional Meeting the RIPE NCC will hold a Routing Registry and DNSSec seminar in the afternoon of Thursday, 29 July 2004. In addition, RIPE NCC will be holding an LIR Training Course on Friday 30 July 2004. You can register for the LIR Training Course at: http://www.ripe.net/cgi-bin/trainingform.pl.cgi Information about the contents of the course can be found at: http://www.ripe.net/training/ If you have any questions about the Training Course, please contact us at: <training(a)ripe.net>. MORE INFORMATION More information about the RIPE NCC Regional Meeting, Nairobi is available from: http://www.ripe.net/ripencc/regional-meetings/nairobi-2004/index.html Any further questions can be sent directly to: <contact(a)ripe.net>. Regards, Nathalie Dougall Membership Liaison Officer RIPE NCC

1 0