September 2005 - ncc-services-wg

RIPE NCC Service Interruption
by RIPE NCC Operations 30 Sep '05

30 Sep '05

[apologies for duplicate mails] Dear Colleagues, >From 07:00 until 08:00 GMT, the RIPE NCC experienced an unexpected disruption to services. Although this may have caused delays to updates to the RIPE Whois Database, these updates have been processed normally. The disruption may have also affected some of these RIPE NCC services: - whois.ripe.net - www.ripe.net - lirportal.ripe.net - ns*.ripe.net - ftp.ripe.net - www.aso.icann.org - www.nro.net - k.root-servers.org (Global node at the AMS-IX) - AS112.ripe.net We apologise for any interruption or delay to services. If you have any questions or concerns regarding this issue, please contact <ops(a)ripe.net>. Regards, RIPE NCC Operations

3 2

Re: [ncc-services-wg] Feature request
by Max Tulyev 19 Sep '05

19 Sep '05

> I think I misunderstood what you wanted when we spoke last week. I > thought you were looking for some kind of added granularity to the > maintainer system. However, reading your request again it looks more > like you want to be able to use the RIPE Database to enforce a > contract between you and your customers. Is that correct? Correct, but not exactly RIPE DB. Just have an ability (for example, through letter to Hostmaster) to have general control on the objects I registered. > Can I ask why you'd want to use the RIPE Database to do this rather > than use an alternative, like a debt collection agency, or an order > from a civil court? That's because it is not working fine here... -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

1 0

Feature request
by Max Tulyev 19 Sep '05

19 Sep '05

Hi! As I register a lot of PI/AS, there is a bit problem I often face to. My clients wants to have control on their objects I registered for them (i.e. have their mnt-by). But there is an agreement between us, and sometimes (due to payment problems, violating the agreement, spam, etc.) I need to suspend or even remove objects. Having my mntner inside users' objects is often not acceptable because of users wants to change objects by themself (and do that quickly and transparently). Also there is administrative reason ("Why we can't change our objects, why there is alien mntner?"). How I can shut down objects I registered as LIR, but don't maintain? Is there some special feature? Thank you. -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

7 10

RIPE51 - NCC Services WG - Agenda Items
by Bijal Sanghani 19 Sep '05

19 Sep '05

Dear Colleagues, We are currently working on the draft agenda for the RIPE NCC Services Working Group for RIPE 51. If anyone would like to make a presentation or raise a topic for discussion please contact either Kurtis or myself and we'll arrange a slot on the agenda. Thanks, -bijal

1 0

Re: [ncc-services-wg] Feature request
by Max Tulyev 18 Sep '05

18 Sep '05

> Well, you are not supposed to sell/rent addresses, with the exception of > covering the administrative overhead. Which should be close to NIL if you > do not want to take care of that block (LIR-wise). So a simple approach > would be to hand out the addresses only after a reasonable once-off fee for > obtaining them has been paid. Heh... /22 PI is scored like 4 (FOUR) PA /20 block usually got by LIR at the beginning (but, of course, once). So I don't think it is "close to NIL". Often it is too expensive, especially in eastern Europe, especially to non-profit organization. So it is good to split payment for a chunks, not bill them once. Anyway, is there the deny to bill PI/AS on regular basis (not once)? Where? > Which agreements? As long as you provide connectivity to them, this is an > ISP operational issue. If they don't pay for those services they get > locked/cut. Then the holder of PI is free (by definition) to find another > provider. end story. If I am their service provider (btw, then they got PA) - I can cut their service. And if not? > Boring, yes, but I thought you want to see an on-going flow of money ;-) > What for? Where's the user friendlyness? So RIPE gives me a policy how to deal with my clients? ;) If yes, please show me the documents. If not - let me do that, and be LIR-friendly ;) > There should be a local legal envirnment available to enforce (resonable) > contracts. Yes. But, unfortunally, contracts sometimes violates, so I ask about technical resources to have users to be correct. -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

3 3

Feature request
by Max Tulyev 16 Sep '05

16 Sep '05

> > But there is an agreement between us, and sometimes (due to payment > > problems, violating the agreement, spam, etc.) I need to suspend or even > > remove objects. > ...which means that you want to/have to keep responsibility to maintain the > data in the repository, right? Not right. User is keeping responsibility to maintain the data, so their mnt-by is in the objects. My aim is (at least) to bill user, and it can be done different ways (once, yearly, quarterly, by crediting user for sometime, whatever). And I need the mechanism to let that user have to pay ;) (and not to violate agreements by other ways) and remove objects if it doesn't - but NOT to keep information up to date in RIPE DB. > I don't understand this assertion, as long as there is a contractual > relationship with your LIR, there is no "alien maintainer". Please keep in > mind that an LIR is NOT required to provide PI assignment services. So if > those "customers" don't like your set of rules, they are free to find > another LIR which offers what they want. Ok, but if I want to be more user friendly than others? Or if I bored with making updates of my users' objects? > What you definitely _can_ do is add an _additional_ maintainer for your > user. Then having any credential as listed in _any_ of the maintainers > allows access. Evaluation of the auth: tags is done according to a LOGICAL > OR policy. From the beginning I said about "bad guys". If user really one - he just sends an update to remove my mntner - and I loose control on object completly. > Not to my knowledge. I think I suggested that before - in case you deploy > the multiple maintainer approch, you probably should enable the > notification mechanism(s) [in your maintainer] to each time get an alert > when your customer happens to change registration data. But notification comes a bit later, isn't it? ;) > And you may want to include an explicit provision in your contract that > prevents your customer from removing the link to _your_ maintainer object. If all users always do what is written in the contract - there was no deal about all of that at all. -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

1 0

RIPE NCC Member Update - Issue 8
by Paul Rendek 08 Sep '05

08 Sep '05

Dear Colleagues, The RIPE NCC is pleased to announce the release of the latest edition of the RIPE NCC Member Update. You can find the latest edition of the Member Update at: http://www.ripe.net/membership/newsletter/2005/newsletter8.pdf This edition of the Member Update includes sections on: - A guest article on the report from the Working Group on Internet Governance (WGIG) - The RIPE NCC Membership Survey 2005 - Changes to RIPE NCC Online Payments - New instances of the RIPE NCC operated K-root server - Previous and upcoming RIPE Meetings - RIPE NCC Training Courses and conference calendar If you have any questions, suggestions or comments about the RIPE NCC Member Update, please contact us by e-mail at: <feedback(a)ripe.net> Regards, Paul Rendek Head of Member Services & Communications RIPE NCC

1 0

Final Reminder: RIPE NCC Regional Meeting, Moscow, 15 - 16 September 2005
by Membership Liaison Officer 01 Sep '05

01 Sep '05

[Apologies for duplicate e-mails] Dear Colleagues, This is a final reminder that registration will soon close for the second RIPE NCC Regional Meeting in Moscow. The meeting will be held 15 - 16 September 2005 at the Moscow Marriott Grand Hotel in Moscow, Russia. The deadline for registering is Friday, 9 September 2005. Attendance to the RIPE NCC Regional Meeting is open and free of charge. However, attendees are responsible for covering their own travel and accommodation costs. MEETING VENUE Marriott Grand Hotel 26/1 Tverskaya Street Moscow, 125009 Russian Federation Phone: +7 095 9370000 Fax: +7 095 9370001 More information about the meeting venue can be found at: http://www.ripe.net/meetings/regional/moscow-2005/meeting-venue.html REGISTRATION Registration for the RIPE NCC Regional Meeting is now open. Registration will close on Friday, 9 September 2005. To register, please see: https://lirportal.ripe.net/lirportal/meeting/registration/meeting.html?id=6 AGENDA The agenda for the RIPE NCC Regional Meeting is available at: http://www.ripe.net/meetings/regional/moscow-2005/agenda.html We have reserved space in the agenda for presentations from the local community on current issues affecting the region. If there is a particular presentation or topic you would like included in the agenda, please send your suggestion to: <contact(a)ripe.net> TRAINING SEMINARS The RIPE NCC Regional Meeting will feature training seminars on IP request procedures, DNSSEC and the Routing Registry. More information about these training seminars is available at: http://www.ripe.net/meetings/regional/moscow-2005/agenda.html APPOINTMENTS AVAILABLE WITH RIPE NCC IP RESOURCE ANALYSTS RIPE NCC IP Resource Analysts will be available for consultation during the RIPE NCC Regional Meeting. For more information, and to make an appointment, please see: http://www.ripe.net/meetings/regional/moscow-2005/ip-resource-analysts.html VISA INFORMATION If you will need a visa to attend this meeting, please read the information available at: http://www.ripe.net/meetings/regional/moscow-2005/visa.html MORE INFORMATION More information about the RIPE NCC Regional Meeting in Moscow is available from: http://www.ripe.net/meetings/regional/moscow-2005/index.html If you have any further questions, please send an e-mail to: <contact(a)ripe.net> Regards, Nathalie Dougall Membership Liaison Officer RIPE NCC www.ripe.net

1 0

RIPE Policy Development Process
by Paul Rendek 01 Sep '05

01 Sep '05

Dear Colleagues We are pleased to announce that Rob Blokzijl, RIPE Chair, has published a new RIPE Document, "Policy Development Process in RIPE", (ripe-350). This document formally describes the policy development process. The updated process is operational from today, 1 September 2005. A new RIPE web page describes all the active policy proposals and their status. Each proposal has a page showing its history, status and all supporting documentation. This page can be found at: http://www.ripe.net/ripe/policies/proposals/index.html A new mailing list <policy-announce(a)ripe.net> has been created for announcing policy proposals and tracking them through the policy development process. This is not a discussion list; discussions will continue to take place on relevant RIPE Working Group lists and at RIPE Meetings. You can subscribe to the policy-announce list at: http://www.ripe.net/mailman/listinfo/policy-announce List archives are available at: http://www.ripe.net/ripe/maillists/archives/policy-announce/ Kind regards Paul Rendek Head of Member Services and Communications RIPE NCC

1 0