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

reverseDNS problem alerts - to be discussed in "Services" or "DNS" WG
by Wilfried Woeber, UniVie/ACOnet 19 Nov '08

19 Nov '08

Dear all, I am following up internally on a couple of (minor) issues related to reverse DNS configuration mechanisms. Amongst others I am looking for clarification regarding: - misleading(?) text in alert messsages, related to IPv6 - selection of master server to transfer zones from - loose ends in config automation for legacy address space What is the appropriate list or WG to raise these issues - the NCC-Services WG or the DNS WG? Thanks, Wilfried PS: I could certainly take this up privately with the NCC's staff, but I guess some of these aspects might be of interest to the community, too.

2 1

RIPE NCC statement on changes in the RIPE NCC Charging Scheme 2009
by Andrew de la Haye 10 Nov '08

10 Nov '08

[Apologies for duplicates] Dear Colleagues, Recent conversations on the RIPE mailing lists and at the recent RIPE NCC General Meeting have highlighted a number of concerns from members concerning the RIPE NCC Charging Scheme 2009. These concerns refer particularly to the changes laid out in RIPE Policy Proposal 2007-01, relating to charges for Direct End User (PI and ASN) assignments. More information on this proposal can be found at: http://www.ripe.net/ripe/policies/proposals/2007-01.html There are three areas in which we believe clarification of the RIPE NCC position would be useful. Area 1: Service Fees -------------------- In drafting the RIPE NCC Charging Scheme 2009, the RIPE NCC Board has made it a priority that the necessary changes have minimal impact on the fees paid by RIPE NCC members. The changes will affect a relatively small number of LIRs who have requested many Direct End User assignments. The Direct End User assignments will now be included in the LIR's total score for the sole purpose of calculating the LIR's billing category, and in a few cases this will mean that the LIR moves up a category (for instance, from Medium to Large). Approximately 80% of RIPE NCC members have Direct End User assigments that are taken into account for their billing score. The likelihood that an LIR will move to a higher billing category is offset, however, by the fact that the new Charging Scheme increases the upper limits of each billing category. This means that the addition of Direct End User assignments to an LIR's total score in most cases does not result in an increase in the LIR's billing category. Area 2: Processes and procedures -------------------------------- In the coming months, the RIPE NCC will develop processes and procedures to facilitate the implementation of these policy changes. This will enable us to support members to contact and update the registration of these resources. The changes will be implemented in two phases: - Phase one will involve the implementation of the new policy in relation to all new requests for PI assignments. This will happen in the first quarter of 2009. - Phase two will be to apply the new policy to existing PI assignments, or those made before the adoption of Policy Proposal 2007-01. A plan for implementation of this phase will be presented at the next RIPE NCC Services Working Group, will be held at the RIPE 58 Meeting in Amsterdam, May 2009. Area 3: Changes to future Charging Scheme ----------------------------------------- The RIPE NCC Charging Scheme is agreed on each year by the membership of the RIPE NCC. All LIRs are encouraged to participate in discussion of the Charging Scheme, and to raise any issues that they feel are important to them or the membership as a whole. These discussions can take place during the RIPE NCC General Meetings, which are held twice a year, adjacent to RIPE Meetings, or on the RIPE NCC Services Working Group mailing list: http://www.ripe.net/ripe/wg/ncc-services/index.html If you have any further questions about any of these issues, you can contact RIPE NCC staff for further information at <contact(a)ripe.net>. Regards, Andrew de la Haye Chief Operations Officer, RIPE NCC

1 0

Re: Fwd: [ncc-services-wg] The new charging sceme
by Flor Paredes 05 Nov '08

05 Nov '08

Dear Max, Indeed in the new Charging Scheme 2009 all assigned Internet Number Resources, IPv4 PI, ASNs and IPv6 PI are taken into account for each members billing score to determine the billing category for that member. In the coming months the RIPE NCC will develop processes and procedures to facilitate the implementation of the new policy 2007-01. This will enable us to support members to contact and update the registration of these resources. Please be reassured that the RIPE NCC will fully support its members and will try to minimize the operational impact of this policy change. Regards, Flor Paredes Registration Services Manager RIPE NCC > > >> From: Max Tulyev <president(a)ukraine.su> >> Date: October 31, 2008 11:04:14 GMT+01:00 >> To: ncc-services-wg(a)ripe.net >> Subject: [ncc-services-wg] The new charging sceme >> >> Hi all, >> >> I see http://www.ripe.net/ripe/docs/charging2009.html is adopted, and >> charging for ancient resources such as PI and AS for third-parties is >> resurrected. >> >> So it means I have to find these guys and say hey, RIPE billing scheme >> is changed, so I want some money and a permanent agreement. >> >> But! As I pass them their mntners, I can't enforce them to do anything. >> How can I enforce them to sign an agreement and pay money? >> >> --WBR, >> Max Tulyev (MT6561-RIPE, 2:463/253@FIDO) >> > > Best regards, > > Alex Le Heux > RIPE NCC IP Resource Analyst > >

2 1

The new charging sceme
by Max Tulyev 31 Oct '08

31 Oct '08

Hi all, I see http://www.ripe.net/ripe/docs/charging2009.html is adopted, and charging for ancient resources such as PI and AS for third-parties is resurrected. So it means I have to find these guys and say hey, RIPE billing scheme is changed, so I want some money and a permanent agreement. But! As I pass them their mntners, I can't enforce them to do anything. How can I enforce them to sign an agreement and pay money? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253@FIDO)

1 0

Planned maintenance for ns.ripe.net, 4 November 08
by Sjoerd Oostdijck 30 Oct '08

30 Oct '08

[Apologies for duplicate emails.] Dear Colleagues, This message concerns people who have ns.ripe.net listed as a secondary DNS server for their reverse DNS zones. In order to improve the quality of our service, we are adding additional servers to our infrastructure. The effect of this change will be that we will perform zone transfers from more then one IP address within the ranges 193.0.0.0/22 and 2001:610:240::/48 as documented at: http://www.ripe.net/rs/reverse/reverse_howto.html On 4 November 2008 at 11:00 UTC, ns.ripe.net will move to a load-balanced solution. No noticeable downtime is expected. If you would like to make sure that we can properly transfer the zone from your server after the change, we recommend that you follow the following steps: - Increase the serial number in your zone's Start of Authority (SOA) record. - Wait for a zone transfer to be initiated from the 193.0.0.0/22 or the IPv6 address range. - Now you can compare the zone serials on your master server and ns.ripe.net. To compare the serials you can use tools like "dig", "drill" or "host -C" to query the SOA record and compare the serials on both servers. If you have any further questions about this message, please contact us at dns-help(a)ripe.net Regards, Sjoerd Oostdijck DNS Services RIPE NCC

1 0

LIR Portal Outage
by Trudy Prins 28 Oct '08

28 Oct '08

[Apologies for duplicate emails] Dear Colleagues, On Monday, 27 October 2008 between 20:33 - 22:38 (UTC) and Tuesday, 28 October between 00:25 - 00:41 (UTC), the LIR Portal was unavailable due to a power outage. We apologise for any inconvenience that this may have caused. Regards, Trudy Prins Manager Business Applications Department RIPE NCC

1 0

Outage Report for RIPE Database Updates
by Agoston Horvath 28 Oct '08

28 Oct '08

[Apologies for duplicate mails] Dear Colleagues, Between approximately 20:05 - 23:14 (UTC) on Monday, 27 October 2008, we experienced an outage in our RIPE Database updates service. During this period, it was not possible to connect to the syncupdates or webupdates services. During the outage, all the messages received by auto-dbm(a)ripe.net were stored on our mail server. If you sent an email update to the RIPE Database during the outage, you will have already received an acknowledgment. There is no need to re-send any update messages. We apologise for any inconvenience that this may have caused. Regards, Agoston Horvath Database Group RIPE NCC

1 0

Deleting unreferenced PERSON objects
by Denis Walker 16 Oct '08

16 Oct '08

[Apologies for duplicate emails] Dear Colleagues, We announced at RIPE 56 that the RIPE NCC would soon start to delete unreferenced PERSON and ROLE objects. This will begin in late November 2008. There are some people involved in the Internet industry who do not directly manage Internet resources but who have PERSON objects in the RIPE Database. If you fall into this category and you believe your PERSON object should not be deleted, you have the option to join the RIPE Database White Pages. This will prevent your PERSON object from being deleted. For further details, please see this web page: http://www.ripe.net/db/support/white-pages-instructions.pdf Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

Maintaining DOMAIN objects
by Denis Walker 16 Oct '08

16 Oct '08

[Apologies for duplicate emails] Dear Colleagues, The RIPE Data Protection Task Force advised the RIPE NCC that all objects in the RIPE Database should be maintained. Maintaining Routing Policy Specification Language (RPSL) objects in the RIPE Database was optional for PERSON, ROLE and DOMAIN objects. All the DOMAIN objects in the RIPE Database are now maintained and protected. As there may have been a possibility to exploit this data if any advance warning had been made, the RIPE NCC did not publicly announce that it was going to add maintainers to unmaintained DOMAIN objects before doing so. For further details of what was done, please see this web page: http://www.ripe.net/db/support/security/domain/syntax.html Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0

Outage report for updates to the RIPE Database
by Denis Walker 13 Oct '08

13 Oct '08

[ Apologies for duplicate mails ] Dear colleagues, >From approximately 19:41 (UTC) to 20:15 (UTC) on Friday, 10 October 2008, some e-mail update messages to the RIPE Database service, auto-dbm(a)ripe.net, were not processed due to a problem with our system. During the same period it was not possible to connect to the syncupdates or webupdates services. All the messages received by auto-dbm(a)ripe.net were stored on our mail server. The problem was resolved on Friday evening. All the saved update messages have been processed. If you sent an e-mail update to the RIPE Database service during this period, you will have already received an acknowledgement message. There is no need to re-send any update messages. We apologise for any inconvenience that this may have caused. Regards, Denis Walker Business Analyst RIPE NCC Database Group

1 0